3 ms·
We merged a fix for this that'll go out in the ~next release. Also, for clarification, this bug was only impacting the display of numbers in the TUI, not what
by amorriscode 11mo ago
We merged a fix for this that'll go out in the ~next release.
Also, for clarification, this bug was only impacting the display of numbers in the TUI, not what the model sees. The model sees raw results from bash.
- rrwright 11mo agoThis symptom was affecting display of numbers in the TUI, but the real bug/design flaw is using jq or JSON as a transport mechanism between components or between tools. JSON's number range is famously poor and it even architecture-dependent. So if you use jq or JSON to connect components or tools, you will have this same problem silently occurring elsewhere without visibility in the UI. This is a bigger deal than it seems like! A confidence-inducing fix would include a blog post describing a top-to-bottom audit of jq/JSON used as a transport layer between tools and components. Not just a patch to the most visible problem.