meejah
I'm seeing this traceback in an `@eliot.twisted.inline_callbacks`-decorated method .. I'm not sure exactly what is happening yet and some initial attempts to re-create the error with a smaller test-case hasn't...
I'm not entirely sure what's going on here, but on a GitHub Actions windows runner, I'm seeing this from `eliot-tree`: ``` Traceback (most recent call last): File "c:\hostedtoolcache\windows\python\3.8.10\x64\lib\runpy.py", line 194,...
If a stream with a purpose starting with DIR_ is proposed for attachment, we shouldn't do that (i.e. we should let Tor attach it).
At least `cuv diff` doesn't nicely report to the user that there's no .coverage file
It turns out there are two options to the Pygments lexers that must be set to `False` or it will silently drop leading whitespace-lines. Also, since we "do Pygments lexer...
There's a bunch of duplicate code in all the "commands" that should be factored out and re-used; this includes all the filtering stuff, matching code, etc. Probably this also wants...
With `cuv lessopen`, if I `print('...'.encode('utf8')` then `less -R` works properly (i.e. shows colours) but if I `click.echo('...')` then the colours don't work with less. Don't know why. ..and in...
I don't have a good way to place the text in the histogram from `cuv hist`: there doesn't seem to be a good way to "know" how wide text is...
If a `DecodedURL` with a username/password in it is passed to a treq API, an error results about encoding a colon character (and the password is removed). (I can followup...
The continuous-integration (CI) provider Travis is gone. Upgrade our CI to use something that works (probably "github actions" is the easiest, here). If anyone is feeling ambitious, I'd love to...