John-John Tedro
John-John Tedro
Support a documentation to a declaration like this: ``` /// The foo type /// /// # Examples /// /// {{ json_example(Foo) }} type Foo { #[example(value = "Some Value")] field:...
Currently `MetricBackend`s will fetch the data for an entire series and range at once, which requires that an entire range fits into memory up until it reaches the configured or...
This feature would extend the query capabilities so that one can limit or extend which data nodes the query should be sent out to. This is used when testing new...
See: https://github.com/spotify/heroic/blob/master/heroic-dist/src/test/java/com/spotify/heroic/GrpcClusterQueryIT.java#L15 For some reason, the calculated cardinality is incorrect when used over gRPC. This could be related to `grpc` having less predictive ordering when recombining the results than the...
It was discovered after implementing a more comprehensive test suite for metadata backends that `findTags(...)` requests do _not appear to work_ in KV. See: https://github.com/spotify/heroic/blob/master/metadata/elasticsearch/src/test/java/com/spotify/heroic/metadata/elasticsearch/MetadataBackendKVIT.java#L39
This is used in the [`Parse` impl for `Arm`](https://github.com/dtolnay/syn/blob/80c6889684da7e0a30ef5d0b03e9d73fa6160541/src/expr.rs#L2586), and would be useful when building custom parsing inside and around match statements. CC: udoprog/genco#12
This is currently being passed in here: https://github.com/udoprog/OxidizeBot/blob/master/bot/src/player.rs#L185 And it's a bit of an issue to untangle, since the API clients are shared in two different places, one which is...
Due to legacy reasons, we currently fetch each token one-at-a-time through the `api/connections/?format=meta` endpoint. This can be improved by fetching all tokens through `api/connections?format=meta`, but would require minor re-architecting in...