-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Bug]: Failed to load log: TypeError: fetch failed while first login to scalr extension #27
Comments
@lonesurvivor84 Thank you for the report. I suspect there may be issues with the API permissions required by VS Code. I’ve reduced some API calls and added better error handling. Please try again with the next release. |
Hi, @lonesurvivor84. Thanks for the report, the new version 0.0.4 with a fix is released. Please update your extension and try to login again. |
Hi @emocharnik , unfortunately still an issue with v0.0.4. |
@lonesurvivor84 Thank you for the report. I've reopened the issue for investigating. |
@lonesurvivor84 Could you share the name of the account that you tried to log in? |
@lonesurvivor84 can we have a live session to troubleshoot your issue? If so, please open a request at https://support.scalr.com with an email and I'll send you an invite in the Google Calendar. |
@lonesurvivor84 do you have a chance to troubleshoot the issue? |
Describe the bug
When trying to login to the scalr VS code, the following message appears:
Failed to load log: TypeError: fetch failed
To Reproduce
Steps to reproduce the behavior:
Failed to load log: TypeError: fetch failed
Expected behavior
Expecting to Login.
Screenshots
Extension Version (please complete the following information):
VSCode Version:
Version: 1.93.0 (system setup)
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:02:38.431Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: