Some transaction entries are created with created_at in the past
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 30
- Forks
- 13
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 8
Description
Further investigation is needed to determine why some created_at values are in the past when records are created in the transaction table. Related code:
https://github.com/closeio/sync-engine/blob/a4d313ccb1a4163f11d36b7e73b025af689533ec/inbox/models/transaction.py#L104-L112
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 models/transaction.py at lines 104-112 and trace how transaction records receive their created_at values. Investigate why some values predate record creation, then confirm the root cause and the appropriate correction with a reproducible case or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100