lidofinance / lidofinance/validator-ejector
S3 pagination never terminates after the first truncated page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 19
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 7
Description
Locations
Summary
The S3 message backend cannot finish enumerating a bucket containing more than one ListObjectsV2 page.
Root cause
read sets isTruncated when a response is truncated but never resets it when the terminal response returns IsTruncated = false. The previous continuation token is consequently reused indefinitely, while keys from the terminal page continue accumulating in memory.
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 reading validator-ejector/src/services/s3-store/service.ts:41-59, especially the read method and its ListObjectsV2 pagination handling. Reproduce or inspect enumeration across multiple S3 pages, then verify that a terminal response stops the loop and that accumulated keys are returned without repeated requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100