Insider trading readers subtract a day from explicit FileDate timestamps
@quantconnect-kronos is already working on this.
Since Nov 17, 2026.
- #19 by @quantconnect-kronos — open
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 90/100
Research direction
Start with the parsing expressions in QuiverInsiderTrading.cs and QuiverInsiderTradingUniverse.cs, then check the downloader serialization noted in the issue. Add regression coverage for both readers using the supplied rows; update the existing compact-format assertion. Done means explicitly supplied FileDate timestamps are preserved in both readers and the tests pass.
Written by the indexing model from the issue text.
Description
Problem
QuiverInsiderTrading.Reader and QuiverInsiderTradingUniverse.Reader subtract one day from FileDate even when the CSV explicitly supplies the filing timestamp. This makes the reported filing time one day earlier than the stored value, affecting filters and intervals based on FileDate.
This is present on master at b9f250fc550bf963b71a0b0050000f17d23f0c0b; it is independent of legacy column-count handling.
Synthetic reproduction
With a read date of 2026-05-08, parse these current-layout rows using the corresponding readers:
20260508,20260507093000,20260507,P,150.25,100,500,A,D,Example Person,CEO,T,T,F,
AAPL R735QTJ8XC9X,AAPL,20260507093000,20260507,P,150.25,100,500,A,D,Example Person,CEO,T,T,F,
For the per-ticker reader, use an AAPL SubscriptionDataConfig; the universe reader accepts a null config.
Both readers return:
Expected FileDate: 2026-05-07 09:30:00
Actual FileDate: 2026-05-06 09:30:00
Verified with two local NUnit cases against the base readers: both fail with exactly that expected/actual difference.
Cause and required outcome
QuiverInsiderTrading.cs:167andQuiverInsiderTradingUniverse.cs:150on the cited commit apply.AddDays(-1)to the result of the entire parse-or-fallback expression.DataProcessing/QuiverInsiderTradingDataDownloader.cs:119–124serializes a non-omitted filing timestamp directly, without a compensating day offset.FileDateis documented as the time the transaction was filed and became publicly available. The separateTime/EndTimeconvention does not require altering this supplied timestamp.
Preserve explicitly supplied filing timestamps in both readers and add regression coverage. Existing compact-format coverage currently asserts the shifted per-ticker value and will need to reflect the corrected behavior. Suggestion: apply any intended fallback adjustment only to the missing-value branch, not to an explicit timestamp.
Priority is P2 because the verified impact is limited to this metadata field; evidence of broader user impact would raise it.
- Dominant language
- C#
- Stars
- 0
- Forks
- 3
- Avg merge
- 39m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from QuantConnect/Lean.DataSource.QuiverQuant
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
priority:P2
Difficulty 4/5 3-5 days Newbie friendliness 49/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
All issues in QuantConnect/Lean.DataSource.QuiverQuant
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
approved area: ui bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day