Mark Dascher

After some additional research, we've determined that the log4j2 JSON situation boils down to this: * `compact=false` (default) results in Papertrail receiving JSON messages split up into multiple lines *...

Confirmed with @TAiS46 that the latest release [v0.20-beta2](https://github.com/papertrail/remote_syslog2/releases/tag/v0.20-beta2) pre-release also solves this problem, by periodically checking for stale files.

Would you be willing to try the latest pre-release listed [here](https://github.com/papertrail/remote_syslog2/releases), currently v0.21-beta1? It's only a pre-release due to how new it is. Once it's been out for a bit,...

We've just added token support in #239. There aren't many examples yet, but basically you'll just start with a regular config, but then replace the `destination` section with: ```yml destination:...

You can coax it a bit higher too, by bumping up the OS stack size first: ``` ulimit -s hard NODE_DEBUG=module node --stack-size=64512 node_modules/.bin/jest ``` Still isn't enough, even though...

What actually worked for me was to edit `node_modules/@jest/reporters/build/DefaultReporter.js` and short-circuit the `_clearStatus` and `_printStatus` functions. Guessing the infinite recursion looked something like: Module load triggers debug message Output triggers...

This seems to also result in false positives, since Infer sometimes guesses at the size each time you memcpy into it: ```c char foo[] = "foo"; char foobar[] = "foobar";...

Just a guess, but could these 301 redirects be handled here? https://github.com/aws/aws-sdk-ruby/blob/cfd0f0d05ad5e56cb00eee1dc81a244ca4c695f4/gems/aws-sdk-s3/lib/aws-sdk-s3/plugins/s3_signer.rb#L118-L122 I've noticed that the SDK already figures out the correct region automatically, with some exceptions. Maybe choking on...

That could be a logical decision, given that there is a workaround. The confusing bits are: * Some redirects are handled automatically, while others aren't. That s3_signer.rb code automatically redirects...