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: filter is not working on Create Contributor Insight page #4161

Open
shubhamchasing opened this issue Oct 12, 2024 · 5 comments
Open

Bug: filter is not working on Create Contributor Insight page #4161

shubhamchasing opened this issue Oct 12, 2024 · 5 comments
Labels
🐛 bug Something isn't working 👀 needs triage

Comments

@shubhamchasing
Copy link
Contributor

Describe the bug

I am not sure if this is the behavior we want but the filter is not filtering. See below recording

Screencast.from.12-10-24.06.03.31.AM.IST.webm

Steps to reproduce

  1. Create contributor insights from the sidebar
  2. Click Add contributors
  3. Click Sync from GitHub following
  4. Now filter contributors and clear it
@shubhamchasing shubhamchasing added 🐛 bug Something isn't working 👀 needs triage labels Oct 12, 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.

@njayman
Copy link

njayman commented Oct 15, 2024

.take

Copy link
Contributor

The issue you are trying to assign yourself is blocked until it can be triaged or by another label on the issue.

@nickytonline
Copy link
Member

@brandonroberts, I think this is maybe because we're not falling back on the API and only leaning on the GitHub API or did we get that sorted a while back?

@brandonroberts
Copy link
Contributor

It could be, its likely the rate limit from GitHub kicked in. If you check the network tab you will probably see some 403s in there

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

4 participants