Trevor O

@tbpg Not sure how something outside this package could call that directly; the handler is private to this package. It's totally possible I'm missing something :) Another solution that compliments...

I'm pretty sure that under the hood it's just using an `io.Writer` to satisfy the `Out` member of a writer interface. In other words, you should be able to set...

There are two things I do normally. 1. I set the `zerolog.ErrorStackMarshaler = pkgerrors.MarshalStack` 2. In my recovery code do whatever clean up you want and then do something like...

We've ran into this issue at work and bumping node to v18.15 seems to have addressed the issue. I suspect it's related to [this changelog item](https://github.com/trpc/trpc/pull/2085#issuecomment-1479950912) or some combination of...

Ah you are indeed correct. This is a pretty old issue, actually as it appears to have been introduced when there was a change to the way that node address...

@tatethurston Did the CLI get removed in the latest npm published package? I cannot find any concept of a CLI or executable in there but this issue references one existing....

Hey Aaron, Thats quite strange; it seems as though something else is listening on port `1153` as well. Can you check to see if that's the case? Otherwise I'm not...

Oh I had something bad in my repo; will take a look! Great find.

I was running into this and was sort of confused as to what was going on. It turns out that because I created my initial migrations with `pg_dump` it had...