Matthew Nibecker

Thanks @trotzig. I hear you on staying on top of an open source project. This is a useful module! We've just been having issues with building this module in node...

@philrz I would say the spec is incorrect here.

TODOs: - [x] Test and observe this actually helps the live ingest case. - [x] Recover when an error occurs whilst compacting/scanning a pool. - [x] Respond/readjust to events handler...

@philrz I'm not an XDG expert but I've seen other projects following XDG place config in `$HOME/.config` and data in `$HOME/.local/share`.

This came up here https://github.com/brimdata/brim/issues/2284

Still pending before I take this out of draft mode: - [x] Write a more comprehensive test suite for these changes - [x] Update documentation- remove references to range syntax...

The problem with implementing either 1 or 2 is we have no way of finding out the pool where a random ksuid belongs if it doesn't belong to the pool...

We need logging for the forthcoming manage monitor command, so I thought now is a time to centralize log related flags for easier use.

I love it. As far as I'm aware with electron 11 so this should be possible. A couple of points: - Not sure GitHub actions will have arm macOS runners...

PutIfNoExist should not need this since it uses the O_EXCL flag meaning it will produce an error if the file already exists.