Don’t prettify exceptions written to the stack #5868
Conversation
In unisonweb#5661, exceptions were made much prettier, but also accidentally double-prettified in cases where they were written to then read back off the stack. This reverts that double-prettification. Fixes unisonweb#5864.
ef36bb6 to
f7c4c1a
Compare
|
NB: This switches back to @unison/runtime-tests/releases/0.0.3, which isn’t ideal, but I think the lesser of two evils. I’m not sure what to do about release/0.0.4, though – is there a way to deprecate a release? I.e., it’d still be there, but latest would be 0.0.3. |
|
I re-ran the failing transcript job, but it’s failing on the issue that is fixed by #5869 (the PR that depends on this one). |
That's okay — I assume we'd need to release a 0.0.5? What was the difference between 0.0.3 and 0.0.4 that should be deprecated? |
Yeah – can that just be cut from 0.0.3, or does it need a new contribution?
The formatting of some error messages that were written to, then read from the Unison stack. It’s an unfortunate reversion, but I don’t know how to fix this issue (as well as #5869) while keeping those. I think reverting is the lesser of two evils. |
In #5661, exceptions were made much prettier, but also accidentally double-prettified in cases where they were written to then read back off the stack. This reverts that double-prettification.
Fixes #5864.