trufnetwork / trufnetwork/adapters
Bug: FMP historical ingestion inserts duplicate boundary
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 3
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 1
Description
It should try to fetch last before a date, but it ends up including the lower boundary date point even if it was just inserted, every time it checks a stream again
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
No file, test, or entry point is named. Start by locating the FMP historical ingestion path and reproduce checking the same stream repeatedly around a date boundary. Done means the lower boundary point is not inserted again when it was already inserted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100