Skip to content

Fixes fate ranged lock encoding#6350

Merged
keith-turner merged 2 commits intoapache:mainfrom
keith-turner:fix-fate-lock
Apr 30, 2026
Merged

Fixes fate ranged lock encoding#6350
keith-turner merged 2 commits intoapache:mainfrom
keith-turner:fix-fate-lock

Conversation

@keith-turner
Copy link
Copy Markdown
Contributor

Encoding the fate ranged lock to store in zookeeper was using standard Base64 which could include a '/'. When this happened the code would go into an infinite loop. Changed to using base64 URL encoding and added a few checks to make the fate lock encoding/decoding more strict.

Encoding the fate ranged lock to store in zookeeper was using standard
Base64 which could include a '/'. When this happened the code would go
into an infinite loop.  Changed to using base64 URL encoding and added a
few checks to make the fate lock encoding/decoding more strict.
@keith-turner keith-turner added this to the 4.0.0 milestone Apr 30, 2026
@keith-turner
Copy link
Copy Markdown
Contributor Author

Discovered this bug while testing #6351 and making splits with random bytes in them.

@keith-turner keith-turner merged commit 224104d into apache:main Apr 30, 2026
9 checks passed
@keith-turner keith-turner deleted the fix-fate-lock branch April 30, 2026 17:53
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