Mark Dascher
Mark Dascher
If anyone can find documentation fully describing `…`, `…`, and `x-amz-bucket-region` or these new endpoint/bucket/region data members, please let me know. I've managed to get something working, but it still...
This is caused by a missing [RB_GC_GUARD](https://github.com/ruby/ruby/blob/master/doc/extension.rdoc#appendix-e-rb_gc_guard-to-protect-from-premature-gc-) combined with some more aggressive gcc optimizations. `-fno-caller-saves` seems to help sometimes, but I think that's just lucky register shuffling. The same flag...
Is this fully fixed now in v23? https://github.com/moby/moby/pull/43622 and https://github.com/docker/cli/pull/3627 seem to address the recent comment.
I think my issues were gone after the initial fixes somewhere around v18, so I'm probably not the best judge. (But for what it's worth, I haven't seen any issues...
It sounds like rotation would still be tricky, because of [this issue](https://github.com/golang/go/issues/32088#issuecomment-526414485). The producer of the log file would have to rename the log file prior to deleting it, or...
Ah, looks like this happens when building it manually too. Looking through the build log, I found this: ``` lib/gentagtbl.sh: line 74: gawk: command not found ``` I edited `lib/CMakeLists.txt`...
I managed to workaround this issue by removing the preferred AEAD algorithms from the public key. Not sure if there's an better way to do it, but the `setpref` subcommand...
It should definitely work in winston 2.1.1, and I just tested that exact version. No problems using `new winston.transports.Papertrail`. And [this](https://github.com/kenperkins/winston-papertrail/blob/v1.0.2/lib/winston-papertrail.js#L241-L245) has been there from the beginning, so even an...
Winston v3 includes pretty thorough built-in syslog support. Try using [these instructions](https://www.papertrail.com/help/configuring-centralized-logging-from-nodejs-apps/) to switch to one of the new transports (either Syslog or Http).
Not that I'm aware of. Winston v3 broke backward compatibility due to this bug, which doesn't seem like it'll ever be fixed: https://github.com/winstonjs/winston-transport/issues/27 That's why we've started recommending the v3...