Skip to content

[backport camel-4.14.x] CAMEL-24343: camel-google-calendar - stop the stream consumer from skipping events - #25385

Merged
davsclaus merged 1 commit into
camel-4.14.xfrom
backport/CAMEL-24343-4.14.x
Aug 6, 2026
Merged

[backport camel-4.14.x] CAMEL-24343: camel-google-calendar - stop the stream consumer from skipping events#25385
davsclaus merged 1 commit into
camel-4.14.xfrom
backport/CAMEL-24343-4.14.x

Conversation

@davsclaus

Copy link
Copy Markdown
Contributor

Backport of #25352 (merged on main) and #25380 (merged on camel-4.18.x) to camel-4.14.x.

The google-calendar-stream consumer moved its updatedMin cursor to the local clock on a poll that
returned nothing — skipping every event modified in between — and one second past the newest event
otherwise, dropping anything modified within that second. The cursor is now the update time of the
newest event actually delivered, with the ids seen at that instant remembered so the inclusive
updatedMin filter does not deliver them twice. Also replaces the unbounded return poll()
recursion on an invalid sync token with a single full re-sync, and guards a null item list.

Cherry-picked cleanly from camel-4.18.x.

Claude Code on behalf of davsclaus

🤖 Generated with Claude Code

…ipping events

The stream consumer moved its updatedMin cursor to the local clock on an empty
poll, skipping events modified in between, and one second past the newest event
otherwise, dropping anything modified within that second. The cursor is now the
update time of the newest event actually delivered, with the ids seen at that
instant remembered so the inclusive filter does not deliver them twice. Also
replaces the unbounded self-recursion on an invalid sync token with a single
full re-sync, and guards a null item list.

Closes #25380

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@davsclaus
davsclaus merged commit e54cc8a into camel-4.14.x Aug 6, 2026
3 checks passed
@davsclaus
davsclaus deleted the backport/CAMEL-24343-4.14.x branch August 6, 2026 12:11
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