-
-
Notifications
You must be signed in to change notification settings - Fork 718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Unleash Repository error #608
Comments
I agree, this should not be there. I assume this is in connection with the hosted offering? Would you mind reaching out on slack? |
(Based in the error message, I assume you are using the Node.js SDK. It could actually be the "Node.js 502 Bad Gateway Issues" you are facing. If you are using node 10 please make sure you are at |
We're on Node 10.15.3 so presumably it's not due to our Node version? I'll go ahead and email support. Thanks! |
closing this as it is being followed up in the support system. |
feat: create and edit feature screen (NEW)
Looking through our logs (both local development as well as live production), we seem to be seeing lots of the following error:
Error: Unleash Repository error: Response was not statusCode 2XX, but was 502
It's not clear if this is causing any issue per se but we'd love to figure out what's going on so we can remove the noise from our logs. We see the message several times a day, usually spaced apart by a few hours.
Any idea what's happening here?
The text was updated successfully, but these errors were encountered: