Skip to content

fix(ai): drain queued catch-ups and preserve ranges and local time - #1291

Merged
cj-vana merged 1 commit into
feature/conversation-catch-upfrom
fix/catch-up-queue-scope-time
Oct 17, 2026
Merged

cj-vana merged 1 commit into
feature/conversation-catch-upfrom
fix/catch-up-queue-scope-time

Conversation

@cj-vana

@cj-vana cj-vana commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

Fixes the three reported Catch up follow-ups: waiting summaries now start automatically after the active job finishes, regeneration retains each conversation's selected range, and transcript times explicitly identify the user's local timezone.

  • Serialize summaries across engines and conversations through actual stream/worker completion. Keep cancellation and deadlines active after endpoint acknowledgement, skip cancelled waiting jobs, and invalidate queued work on configuration changes or teardown. Start each deadline when its queue slot opens and wait for bundled worker cleanup before advancing.
  • Keep range selections in session state across conversation, tab and protocol switches. Restore custom-hour controls with the saved value.
  • Include local dates, IANA timezone and UTC offsets in prompts, including midnight, daylight-saving fallback and fractional-hour offsets. Existing prompt-size bounds still apply.

This is a stacked follow-up to #1277, targeting feature/conversation-catch-up because the underlying feature has not merged into main.

Validation: env -u RUST_LOG pnpm run check:pr passed full lint, typechecks and 16,477 tests (5 skipped). Normal commit hooks passed policy checks and 1,208 related tests. Focused coverage includes FIFO completion/error/cancellation/timeout, stale configuration/teardown, cancelled worker cleanup, per-conversation scope restoration across all protocols/platform settings, and local timezone/DST formatting. No sidecar paths changed.

The main CI workflows only auto-trigger for PRs targeting main, so CI Build and Tests were manually dispatched against commit cf7e2421e03937f977b5add319668f74a809cd06; both are in progress. CI and CodeRabbit feedback will be monitored and actionable failures addressed.

@coderabbitai

coderabbitai Bot commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Repository: Colorado-Mesh/mesh-client/.coderabbit.yaml
  • Review profile: QUIET
  • Plan: Advanced
  • Run ID: a059a308-61ff-4029-8f87-8e6312971be3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the bug Something isn't working as expected label Oct 17, 2026
@cj-vana
cj-vana merged commit cf7e242 into feature/conversation-catch-up Oct 17, 2026
23 checks passed
@cj-vana
cj-vana deleted the fix/catch-up-queue-scope-time branch October 17, 2026 19:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working as expected

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant