Skip to content

Record unblocked reads in channel_read_latest_decision (#416) - #417

Merged
mattloose merged 7 commits into
LooseLab:mainfrom
andrew-gavin:issue416
Oct 29, 2026
Merged

mattloose merged 7 commits into
LooseLab:mainfrom
andrew-gavin:issue416

Conversation

@andrew-gavin

Copy link
Copy Markdown
Contributor

Fixes #416

RUClient.unblock_read_batch overrides the base method without calling self.channel_read_latest_decision.update(reads), so chunks of an unblocked read that arrive before the unblock takes effect are processed again, even though a decision has already been made.
This adds the missing call, so it is now matching stop_receiving_batch.

@mattloose mattloose 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.

With the positioning of this, the only issue I can see is that reads which do not unblock for some reason will then be sequenced to full length. We believe this is rare, but we aren't 100% certain.

mattloose
mattloose previously approved these changes Oct 26, 2026
@hiruna72

Copy link
Copy Markdown

Enabling read-until logger (#390) would show how often unblocks fail?

@mattloose
mattloose marked this pull request as draft October 27, 2026 14:28
@mattloose

Copy link
Copy Markdown
Contributor

Prior to approving this, please can you formally remove python 3.8 from the list of supported python versions in pyrpoject.toml etc

@andrew-gavin
andrew-gavin marked this pull request as ready for review October 27, 2026 14:49
@mattloose
mattloose merged commit dd5ea5d into LooseLab:main Oct 29, 2026
9 checks passed
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.

Should RUClient.unblock_read_batch also update channel_read_latest_decision?

4 participants