neume-network / neume-network/data
In yet another case, the continuous crawl produced a duplicate
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- https://github.com/neume-network/data/actions/runs/3013761088
- I'm now upping the last crawled block number by 1 to see if repeatedly crawling the same block feeds into the issue: https://github.com/neume-network/data/commit/3344fc355d5914d01252214bb52c8d05373a0685#diff-843ccc105c6ba40946d18c600738af2bb2f2182a8e4e051f0f31817434dffd2bR3
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.
Research direction
Start with the linked GitHub Actions run 3013761088 and the referenced commit diff at line 3. Reproduce the continuous crawl and compare results when the last crawled block is incremented by 1, then identify why the same block produces a duplicate. Done means the duplicate no longer occurs and the behavior is covered by an appropriate check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100