-
Notifications
You must be signed in to change notification settings - Fork 655
Labels
component/pluginsThis issue or PR relates to pluginsThis issue or PR relates to pluginsseverity/p1This bug affects functionality or significantly affect uxThis bug affects functionality or significantly affect uxtype/bugThis issue is a bugThis issue is a bug
Milestone
Description
Search before asking
- I had searched in the issues and found no similar issues.
What happened
The Github GraphQL collector repeatedly fails on issue collection when it encounters an issue that has been transferred to another repository.
task-53475-3-2-github_graphql.log
In the above example, the error is Could not resolve to an Issue with the number of 17617. The issue with that number was transferred to another repository.
What do you expect to happen
The collector ignores issues that have been transferred, deleting them from the dataset or marking them as closed.
How to reproduce
- Create a Github issue in repository A
- Run the pipeline that includes repository A
- Transfer the previously created issue to repository B
- Re-run the pipeline that includes repository A
Anything else
No response
Version
v1.0.1-beta7
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
dosubot
Metadata
Metadata
Assignees
Labels
component/pluginsThis issue or PR relates to pluginsThis issue or PR relates to pluginsseverity/p1This bug affects functionality or significantly affect uxThis bug affects functionality or significantly affect uxtype/bugThis issue is a bugThis issue is a bug