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: Throw errors on failed insight creation #4144

Closed
zeucapua opened this issue Sep 27, 2024 · 3 comments · Fixed by #4145
Closed

Bug: Throw errors on failed insight creation #4144

zeucapua opened this issue Sep 27, 2024 · 3 comments · Fixed by #4145

Comments

@zeucapua
Copy link
Contributor

Describe the bug

Currently, no errors are thrown when a user encounters an error when creating a Repository or Contributor Insight.

Steps to reproduce

N/A

@zeucapua zeucapua added 🐛 bug Something isn't working 👀 needs triage labels Sep 27, 2024
@zeucapua zeucapua self-assigned this Sep 27, 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.

Copy link
Contributor

open-sauced bot commented Sep 30, 2024

🎉 This issue has been resolved in version 2.63.1-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Copy link
Contributor

open-sauced bot commented Oct 22, 2024

🎉 This issue has been resolved in version 2.64.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@open-sauced open-sauced bot added the released label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant