Skip to content

fix: do not emit time spacer tokens twice in unfused mode#7

Closed
brettbj wants to merge 1 commit into
masterfrom
fix/unfused-duplicate-spacer
Closed

fix: do not emit time spacer tokens twice in unfused mode#7
brettbj wants to merge 1 commit into
masterfrom
fix/unfused-duplicate-spacer

Conversation

@brettbj

@brettbj brettbj commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

get_pretokenized wraps the event token list in
concat_list(t_spacer, ); the unfused branch's inner list also began with t_spacer, so every non-null spacer appeared twice in the timeline, e.g. [TIME//1h-2h, TIME//1h-2h, LAB//x, Q3]. Drop t_spacer from the inner list; the outer concat_list already provides it for both modes.

get_pretokenized wraps the event token list in
concat_list(t_spacer, <inner>); the unfused branch's inner list also began
with t_spacer, so every non-null spacer appeared twice in the timeline,
e.g. [TIME//1h-2h, TIME//1h-2h, LAB//x, Q3]. Drop t_spacer from the inner
list; the outer concat_list already provides it for both modes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes duplicate emission of time spacer tokens in unfused tokenization mode by ensuring t_spacer is only added once to the to_tokenize list (via the outer pl.concat_list(...)), matching the already-correct fused behavior.

Changes:

  • Remove t_spacer from the unfused branch’s inner pl.concat_list(...) to prevent duplicate spacer tokens in the output timeline.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@brettbj brettbj closed this Jun 10, 2026
@burkh4rt
burkh4rt deleted the fix/unfused-duplicate-spacer branch June 10, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants