Chris, thanks so much for the tool (which I re-discovered only yesterday, after first seeing it in 2015 then losing track of it--my loss). But as I was exploring it, I am finding that the key-based commands (q for quit, p for pause, h for help, or the more powerful d, s, and others) are not responding immediately. Indeed, at first I thought they were not responding at all. Then I realized what's happening (for me, at least): **the commands are only processed when a new Apache/httpd request is run** (and thus logged, thus triggering your tool to detect that I suppose). Does that make sense to you? Has anyone else experienced it? I happened to be testing it in a dev box where I had only occasional requests I was running. And I really do mean, for instance, that if I opened the tool and it displayed its lines of output, if I hit q it would not even quit. (I'd have to use ctrl-c.) And all other key-based commands also would just not respond. I only discovered what I did by accident, when I had hit the q, switched away to run a request to see its impact on the UI, and then came back and found it HAD quit. Then I proved this was the case with all other keys, like h and p, etc. If it helps to hear, this is on Apache/2.4.41, running on Ubuntu 20.04.6. (And if it may matter, I do happen to be running that within a WSL-based container.) If you may confirm it happens on whatever platform you run, I suppose it could be that you/others maybe only ever had it running against an Apache that was more active. :-) But since some may well test it on such a local/dev env first, I'd think others must have experienced it, but I don't see it discussed in closed issues. Again, I really appreciate your effort with the tool, and I apologize in advance if somehow you/we discover that this is some unique environmental matter on my end. I was tempted to take the time to create a real vm (without WSL), and perhaps with a later Ubuntu or other distro. But I thought I may as well take my chances and offer this here, again if it may help someone else (even if they may find it as a closed issue that could not be reproduced by anyone else.)
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by carehart and has received 3 comments.