issue 386 - handle cluster token overlap issue gracefully #387
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
msmygit
force-pushed
the
feat/handle_cluster_token_overlap_gracefully.md
branch
2 times, most recently
from
7a29abd to
3c609dd
Compare
msmygit
force-pushed
the
feat/handle_cluster_token_overlap_gracefully.md
branch
from
3c609dd to
e632182
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does: Handle cluster token overlap issues more gracefully and educates users on potential fixes and provides clarity
Which issue(s) this PR fixes:
Fixes #386
Checklist: