-
-
Notifications
You must be signed in to change notification settings - Fork 232
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: Unauthorized Error (401) When Creating Insight via POST /v2/workspaces/{id}/insights #3985
Comments
Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label. To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please comment on this issue. For full info on how to contribute, please check out our contributors guide. |
If this issue is valid and the organization is looking to fix it, I would like to work on it. @jpmcb @nickytonline , could you please take a look? |
I'm not able to reproduce this: can you give us abit more information?
|
Yes i have attached the video for your reference: screen-capture.28.webm |
@jpmcb it seems to be an issue just on beta. |
I believe this is an API issue where the |
Just asking out of curiosity, is the backend of OpenSauced not open source? 🙂 |
Good question! Not currently: we closed sourced it earlier this year as we were working on some more special proprietary bits. This has been fixed in the beta API and will land in prod soon! |
No problem, @jpmc. Actually, I have worked with backend development as well and was looking to learn from here by contributing. That's why I asked. |
Describe the bug
When a user selects repositories from the workspace and clicks "Add to Insight" followed by "Create Insight," the page freezes for an extended period. Eventually, the site crashes and throws an error:
I tested the endpoint using Swagger with a valid payload, and it returned a 401 Unauthorized error.
Proposed Solution:
a fallback function to handle cases where the API fails to return the desired response, preventing the site from crashing.
Steps to reproduce
The text was updated successfully, but these errors were encountered: