Paul Coccoli

Also, a friendly reminder that there's a unit test for autocomplete in tests/test_completion.py - you should add these cases first and see them fail, then implement the change until the...

The first 3 cases look correct to me. 1. `DISP ` should suggest all vairables, which in this case is `conns` and the built-in `_`. It *also* suggests `TIMESTAMPED` because...

That's a possibility. Most of the work is probably done already in module `firepit.deref` function `auto_deref`. That will return the list of joins and a projection. I think you could...

I like the meta package idea. Though one thing to consider - if the vast majority of users will want to use Kestrel via Jupyter, then why not make the...

Whatever happened to this? From a threat hunting perspective, having a unique process ID similar to Windows' ProcessGUID would be immensely helpful.

https://github.com/sysflow-telemetry also appears to handle this, I think. See https://sysflow.readthedocs.io/en/latest/spec.html#object-id Though I still think something native to audit would be nice.

Same problem here: 1.1.2 fails; 1.1.1 succeeds. Red Hat Enterprise Linux 8.7 Python 3.9.2

FWIW the error looks the same as #2227 and #2245 except the signal number is different in those; presumably it's because those are Windows and this is a Linux.

While still not implemented, PostgreSQL support is now an "extra" which can be installed via `firepit[postgres]` or `firepit[async-postgres]`

I agree the stack trace is confusing, but `grp_conns` is an aggregate and therefore cannot be used with `TIMESTAMPED`. That transform needs to join the private `__contains` table and the...