https://mage.github.io/mage ・https://medium.com/mage-framework ・ https://twitter.com/mageframework
(in any case, I made an issue)
where error codes are defined
https://github.com/couchbase/libcouchbase/blob/master/include/libcouchbase/error.h#L56 Seem to be what you are getting?
Could it be an auth error somehow?
the bucket gets created :)
on an auth failure, that would be quite something ;)
```> c.errors
{ success: 0,
authContinue: 1,
authError: 2,
{ success: 0,
authContinue: 1,
authError: 2,
it does look like an auth error though
what could happen is that it may give you an auth error if the bucket is not yet created entirely?
waitForSet does (re?)open the bucket itself to do the check
You can try to add the error here: https://github.com/mage/mage/blob/master/lib/archivist/vaults/couchbase/couchbaseHelpers.js#L66
so that it would be ignored - it should be safe enough to ignore, given that we know our auth credentials are valid at this point
Seems to be pointing in that direction
You'll want to try that out on your project to see if it fixes the issue
(mind you, CB runs in a docker container)
false alarm, I have it on Mac too
npx mage create my-gameproject [--typescript]
Feedback welcome!
@stelcheck re. this mage-console issue: https://github.com/mage/mage-console/blob/master/index.js#L281
that was fixed in Node 8.9.4: https://nodejs.org/en/blog/release/v8.9.4/
https://github.com/mage/mage-console/blob/master/index.js#L291 is the line that will eventually go away
the function itself is necessary
in fact, going by the issue thread, it seems that process.on('SIGWINCH', () => {}); should do the trick too
calling the function manually will mean the call will be called twice, but at least we can see that it will call it at least once