Bryn Cooke

Closing as the LRU cache prevents unconstrained memory usage in the case of long running requests, `@defer` comes to mind.

I think these features are coming in apollo-rs if they are not available already. Currently at least some of our validation is performed in deno during query planning via graphql.js....

Going to close this in favor of [#3226](https://github.com/apollographql/router/issues/3226)

We should think about this when doing #2113

I'm actually not sure this is possible. Spans go through tracing and then to otel, so I don't think this can ever be truly independent.

Possibly, but not sure that adding a layer if indirection (plus config) would actually make things simpler. The existing env prefix stuff is pretty simple, so would be tempted to...

This is implemented already. Users can insert `apollo_telemetry::studio::exclude` into context to disable metrics for a particular request. Note that this does not affect operation count.

I updated the example and did a little investigation. I think the issue is that RefValidator doesn't contain a custom implementation of apply, so any `PartialApplication` information from down stream...

As length validation has been removed in #2508 would that make a difference to allowing slices in 1.x? The `ValidLen` trait is documented as: `/// Restrictions on `ValueSet` lengths were...

I've also hit this issue, and came up with something that seems to work for spans and events: https://crates.io/crates/tracing_dynamic It's really just a proof of concept until someone tries it...