Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Thousands separator for progress stats
See original GitHub issueRight now, progress stat line (EC.TLC_PROGRESS_STATS) looks like this:
Progress(32) at 2019-02-19 20:28:11: 516608828 states generated (432,270 s/min), 19621926 distinct states found (14,277 ds/min), 1433419 states left on queue.
There are some huge numbers that need thousands separators for readability. I propose it to look like this:
Progress(32) at 2019-02-19 20:28:11: 516,608,828 states generated (432,270 s/min), 19,621,926 distinct states found (14,277 ds/min), 1,433,419 states left on queue.
I’m happy to implement this change, but I wanted to first check with you whether you see any issues with this enhancement.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@philipmw A patch will be accepted if a) it uses the system’s locale to select the thousands delimiter b) the Toolbox’s parser - which reads TLC’s output - does not break or gets changed correspondingly
To work around b) it might be acceptable to only print a thousands delimiter in TLC’s non-Tool mode
@philipmw Please reopen if you ever have time to work on the idea outlined in the second paragraph of my previous comment.