cowprotocol / cowprotocol/dune-sync
Check how a block range is used in the order rewards sql query
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
After struggling to make an integration test work in PR #94, I decided to open this issue to revisit the way we handle the block range in the order rewards query.
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 by reviewing PR #94 and the order rewards SQL query, then trace how its block range is provided and consumed. Reproduce the integration-test difficulty described in the issue and confirm the block range handling is consistent and the order rewards query works as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100