-
Notifications
You must be signed in to change notification settings - Fork 596
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
tagfocus issues with size #153
Comments
This was referenced Jul 14, 2017
@nolanmar511 Is this issue still relevant? |
It's still not resolved, but I think it should be fixed when/by adding units to tags. |
@nolanmar511 Should we mark this issue as fixed now? |
I think so. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(again, silly zipped profile for github naming)
Now let's try to filter to some of these. Each of the below queries should match exactly one entry and do (this is good)
But this matches everything:
Note that
524288 bytes = 512kb
. But for some reason when we have a non-empty range that breaks. That's a flat bug.:1kb
seems to work, otoh, as does1kb:4kb
.A slightly different problem is that there's no easy way to specify request ranges without having to write out full numbers. I'd be very happy if I could specify, say:
-tagfocus=/request/256kb:512kb
to mean "I want to see a tag, whose name matches "request", whose value is between 256kb and 512kb.
heapz.zip
The text was updated successfully, but these errors were encountered: