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

ui: Fix start key printed on range debug page #17843

Merged
merged 1 commit into from
Aug 23, 2017

Conversation

a-robinson
Copy link
Contributor

It was mistakenly printing the end key twice.

@a-robinson a-robinson requested review from BramGruneir and a team August 23, 2017 15:40
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@BramGruneir
Copy link
Member

:lgtm:

Nice catch!


Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, some commit checks pending.


Comments from Reviewable

It was mistakenly printing the end key twice.
@a-robinson a-robinson merged commit e8a1b41 into cockroachdb:master Aug 23, 2017
bdarnell added a commit to bdarnell/cockroach that referenced this pull request Sep 6, 2017
A screenshot in
cockroachdb#17524 (comment)
made me think we might have an off-by-one error here (because it
showed the range starting with NodeLivenessKeyMax using an
expiration-based lease), but it was a false alarm caused by a bug in
the range debug page (cockroachdb#17843). In any case, it's good to test here.
@a-robinson a-robinson deleted the fixkey branch May 18, 2018 20:31
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