Steven Soroka

this happens every time the org create db call is hit, but it might be only outside of a request transaction

how does this look when rendered?

I don't see any performance impact to this. I've been using this in production for a year and a half at this point. Maybe someone could pick it up, update...

I'd actually like to make Body optional, and I think it might make sense to make both Body and Headers optional. I don't think it'd be too confusing to intuit...

I'd happily pay the cost of write amplification and the inability to replay events from before the subscription. Considering this, what's required to support wildcard subjects? (channels?)

This would be great for: 1. executing queries and then streaming results to the UI for live queries. 1b. executing really huge queries and seeing results instantly in the UI...

Would love 1.9 support :)

@appleboy this is way off my radar (it's been 2 years and I've switched to huma). Feel free to take the change over and apply it in a new PR.

Hey @kozlovic. Thanks for responding. yes, it was a `msgs.x.dat` file (I just checked the Kibana logs). For whatever reason, restarting the node didn't resolve the issue, as it would...

@googlebot I signed it!