Fielding Johnston
Fielding Johnston
@CoenraadS, just wanted to clarify, but you are wanting to be able to specify the path for cli usage, yeah? #2 added support for specifying a path(s) when using git2json...
Excellent. I have completed that implementation and will submit the PR once #11 is merged. Since #11 seemed to be well received, I cheated and based the PR for this...
Just wanted to jump in and support @whwright's hypothesis. I was backing up my organizations and noticed the same thing, it is indeed case sensitive and matching how github shows...
could you check and see if https://github.com/nats-io/nats.py/pull/675 helps at all?
Sorry meant to open as a draft. I will address the build failure issues then mark as ready.
I rebased this on top of current main since it's been a while. Using it live in some of our projects.
Crap, I just realized this was still open, I will take a look in a bit at what the conflicts are now that it is approved
I'm experiencing the same issue. Particularly in any combination of the following: - Run for extended periods - Experience intermittent network issues - Need to recover automatically from temporary disconnections...
I'm going to leave this as a draft until I can get some concrete data from my own testing in the wild or from others who might be having similar...
My own concerns with this: - **Performance Overhead**: Timeouts and health checks add slight overhead. For high-throughput applications, this could be noticeable. Consider profiling under load. This is my main...