Dotan Simha
Dotan Simha
Any update on this one? seems like pinning 0.2.87 causes issues when trying to use other crates that already got updated (for example `tracing`/`tracing-opentelemetry`)
Totally agree. We are using `js-yaml` and I think it's already supported. Have you tried it? It should work...
Hi @hediet, thank you for opening this issue. I think source map might do the trick, but I never tried to generated those before. We might add the feature in...
I assume this is something to do with `isUsingTypes` method. PRs are welcome :D
Thank you for reporting this @doomsower . Can you please share a live reproduction of that issue?
@simPod can you please elaborate more on your use-case? I understand the question, but I'm not sure why overriding a specific field is helpful? You can override scalars with the...
That's a good point @simPod , I think it's a more broad topic around type safety and using branded primitive types. I think it might be worth considering changing the...
Thanks @sudhirj . I noticed a few more places where we bind explicitly for IPv4. Fix seems to be simple (I guess by either binding to both as you suggested,...
@lutter I checked and it seems like binding to IPv6 **only** might be an issue for Linux environments, which needs some extra env configuration (`IPV6_V6ONLY`) for making both available. I...
> @dotansimha I noticed mix usage of minitrace and tokio-tracing in [Conductor](https://github.com/the-guild-org/conductor), would the compatible layer help? At the moment we are using `tracing` only for logging and some performance...