router icon indicating copy to clipboard operation
router copied to clipboard

A configurable, high-performance routing runtime for Apollo Federation 🚀

Results 667 router issues
Sort by recently updated
recently updated
newest added

**Is your feature request related to a problem? Please describe.** The router currently fails closed if the coprocessor is unavailable/erroring/etc, which leads to situations where a router may be marked...

raised by user

## **Is your feature request related to a problem? Please describe.** I want to allow introspection on my supergraph but I do not want to keep it open for attackers...

raised by user

In order to tag a metric or span that has been cancelled or dropped it would be great to have a specific selector for this. It would imply implementing Drop...

component/open-telemetry
story/observability

`format_response` is a procedure that takes in the original GraphQL query as well as the federated response, and filters and reorders the response based on the input query. It does...

raised by user

The test axum_factory::tests::test_supergraph_timeout does not use an ephemeral port, so `cargo test` fails if port 4000 is in use (for example, if you just happen to be running a router...

raised by user

**Describe the bug** The AuthZ plugin will strip parts of a query when possible, but as it does so, it will not strip arguments defined in the top-level query, meaning...

raised by user

*Description here* Fixes #**issue_number** --- **Checklist** Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review. - [ ] Changes are compatible[^1] - [ ] Documentation[^2] completed...

**Describe the bug** In my subgraph I have a field with Int! type but backend retuns `float` number (1.1 for example) (by mistake in code) ```graphql type FreeDeliveries { freeDeliveriesSavedMoneySum:...

raised by user

OTEL spans for coprocessors currently appear as one giant span for the entire lifetime of the request. This is confusing when looking at metrics as it is unclear how long...

raised by user

**Describe the bug** Issue was reported by @bonnici in Slack: https://apollograph.slack.com/archives/C02UX05LF4K/p1710991184963719 Here is example of requests producing invalid responses: ``` json { "operationName": "", "query": "query ExampleQuery { me {...

raised by user