Peloton workflow possibly struggling with duplicate items
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start in peloton/update_project.py around lines 1331-1333 and inspect how the issues_discussions dataframe is built and consumed. Run the Peloton workflow or examine its query results for duplicate issue, pull request, or discussion IDs. Done means the workflow reliably prevents duplicate items from reaching downstream handling, with the behavior checked against a representative duplicate case.
Written by the indexing model from the issue text.
Description
Have seen a couple of runs this weekend where the Peloton workflow has attempted to add the same item to the project twice in the same query. GitHub handles this but our workflow cannot handle it downstream. I was unable to replicate the problem this morning. If it materialises again we might consider adding something after this line:
The issues_discussions dataframe uses the ID of the issue/pr/discussion as the index. We can enforce this to be unique (it is certainly expected to be).
- Dominant language
- Python
- Stars
- 3
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SciTools/.github
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Pixi template Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in SciTools/.github
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100