The baseline time field is incorrect.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.7k
- Forks
- 285
- Avg merge
- 9d 5h
- Merged PRs (30d)
- 2
Description
Describe the bug
The time field of the baseline sometimes goes wrong.
After decoding, in some cases, the time of the first record of the baseline object in the second session is the sum of the start and duration of the last record of the baseline field in the first session. I suspect whether the value of the baseline is not initialized when updating the session.
Furthermore, in the sessions where the baseline time was incorrect, the time field of the first record was greater than that of the second record. As shown in the screenshot below.
Please spare your precious time to take a look at this issue for me. I would be very grateful.
Screenshots
Browser info:
- OS: Windows
- Browser: Chrome
Contributor guide
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 reproducing the reported two-session baseline decoding scenario described in the issue, comparing the last record of the first session with the first record of the second. Trace where the baseline time is initialized or updated, then verify that the second session does not inherit the prior session's value and that its first record time is ordered correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100