Ian Grayson

This is the docker-compose health-check that worked for me: ```yaml healthcheck: test: [ "CMD", "tctl", "--address", "temporal:7233", "workflow", "list" ] interval: 1s timeout: 5s retries: 30 ``` My temporal service...

@yunspace have you had a chance to test it out?

@MiguelAngelVM just an FYI: jcenter should not be turned off on Feb 1, 2022. (see [update](https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/)). It will not be possible for react-native-qr-scanner to push new versions until it moves...

We've worked around this with: ```ts // NOTE: while updating "rules", you must comment out "ignoreChanges" setting. // see https://github.com/pulumi/pulumi-aws/issues/1423 new aws.wafv2.WebAcl("xxx", { rules: [ ... ], ... }, {...

Ultimately we're not blocked by this. We [don't want to](https://github.com/uptrace/opentelemetry-go-extra/issues/65) log fully unredacted SQL, so we won't enable gorm's Logger in production — and we don't really need tracing in...

Another way to mitigate this: change otelzap to always add `trace_id` to zap.Logger calls, if it's available — even if the span is no longer recording. This seems like a...

> I'd assume trace id to be zero if span is not recording. It remains available. Before I tried otelzap, we had a small hook to add it without checking...

See https://github.com/dependents/node-filing-cabinet/pull/103

I haven't looked at this library in depth, but I can tell you that CWL itself advises against multiple producers for a single stream. The CWL API requires a token...

This would be really great!