Skip to content
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: error while creating new Contributor Insight #4120

Open
shubhamchasing opened this issue Sep 23, 2024 · 3 comments
Open

Bug: error while creating new Contributor Insight #4120

shubhamchasing opened this issue Sep 23, 2024 · 3 comments
Labels
🐛 bug Something isn't working 👀 needs triage

Comments

@shubhamchasing
Copy link
Contributor

shubhamchasing commented Sep 23, 2024

Describe the bug

Getting "An error has occurred, Try again" while creating a new Contributor Insight from the past 20 hours
This is in the prod

Steps to reproduce

  1. Go to workspace
  2. click on Create under Contributor Insight from the sidebar
  3. Add contributors and click Create Insight
  4. See the toast message "An error has occurred, Try again"
    Screenshot from 2024-09-23 18-26-03
@shubhamchasing shubhamchasing added 🐛 bug Something isn't working 👀 needs triage labels Sep 23, 2024
Copy link
Contributor

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.

@jpmcb
Copy link
Member

jpmcb commented Sep 23, 2024

I'm not able to reproduce this: @shubhamchasing - can you include what responses from api.opensauced.pizza are included in the network tab of your dev tools when you run this? That will help us see if there are API failures or timeouts

@shubhamchasing
Copy link
Contributor Author

@jpmcb I checked in dev tools, and it was 401: unauthorized, sorry I could not capture the response.
Maybe due to cache, it was showing me as logged in.
I cannot understand why it was showing me as logged in in the first place even though I refreshed the page multiple times.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working 👀 needs triage
Projects
None yet
Development

No branches or pull requests

2 participants