You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to test a simple query, I got: Error: cannot enable long stack traces after promises have been created
This exception was thrown by bluebird because my app created a promise before calling into node-redshift.
I eventually figured out I could work around this by passing { longStackTraces: false }, but I think that shouldn't be necessary - it's not uncommon for apps to be using promises elsewhere. I suggest making the default value of longStackTracesfalse, or removing it as an option altogether (library consumers can call Promise.config themselves if desired).
The text was updated successfully, but these errors were encountered:
When trying to test a simple query, I got:
Error: cannot enable long stack traces after promises have been created
This exception was thrown by
bluebird
because my app created a promise before calling intonode-redshift
.I eventually figured out I could work around this by passing
{ longStackTraces: false }
, but I think that shouldn't be necessary - it's not uncommon for apps to be using promises elsewhere. I suggest making the default value oflongStackTraces
false
, or removing it as an option altogether (library consumers can callPromise.config
themselves if desired).The text was updated successfully, but these errors were encountered: