Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search handles prefix longer than allowed UUIDs #3138

Merged
merged 2 commits into from
Aug 30, 2017
Merged

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Aug 30, 2017

This PR fixes an issue in which the Search endpoint would error if the
prefix was longer than the allowed 36 characters of a UUID.

Fixes #3134

This PR fixes an issue in which the Search endpoint would error if the
prefix was longer than the allowed 36 characters of a UUID.

Fixes #3134
@chelseakomlo
Copy link
Contributor

Looks good!

@dadgar dadgar merged commit 98bb9a2 into master Aug 30, 2017
@dadgar dadgar deleted the b-status-length branch August 30, 2017 20:32
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

nomad status <LONG_JOBID> hits go-memdb's limitation UUID have 36 characters
2 participants