Skip to content

Remove LATEST_OFFSET which isn't handle by server#312

Merged
luoyuxia merged 2 commits intoapache:mainfrom
leekeiabstraction:latestoffset
Feb 14, 2026
Merged

Remove LATEST_OFFSET which isn't handle by server#312
luoyuxia merged 2 commits intoapache:mainfrom
leekeiabstraction:latestoffset

Conversation

@leekeiabstraction
Copy link
Contributor

Purpose

Fix issue where subscribing using LATEST_OFFSET causes API error returned by server cause it isn't a recognised / handled constant on server side

@leekeiabstraction
Copy link
Contributor Author

@fresh-borzoni Would appreciate a review here

Copy link
Contributor

@fresh-borzoni fresh-borzoni left a comment

Choose a reason for hiding this comment

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

@leekeiabstraction Ty for the PR
LGTM

Copy link
Contributor

@luoyuxia luoyuxia left a comment

Choose a reason for hiding this comment

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

@leekeiabstraction Thanks. But the ci fails

@leekeiabstraction
Copy link
Contributor Author

Updated to address CI (formatting/clippy) failure

@luoyuxia luoyuxia merged commit c6b63ed into apache:main Feb 14, 2026
13 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.

3 participants