Arnaud Gourlay
Arnaud Gourlay
**Is your feature request related to a problem? Please describe.** A quick profiling session on a heavy write workload shows that Snappy can take up to 2% of CPU time....
**Is your feature request related to a problem? Please describe.** In order to improve the latency we have introduced pooling for gRPC channels in https://github.com/qdrant/qdrant/issues/518 This first approach uses a...
**Is your feature request related to a problem? Please describe.** Currently every HTTP request processed is logged. e.g. for successful queries ``` [2022-03-01T15:50:13Z INFO actix_web::middleware::logger] 127.0.0.1 "PUT /collections/stress_collection/points HTTP/1.1" 200...
``` Crate: memmap Version: 0.7.0 Warning: unmaintained Title: memmap is unmaintained Date: 2020-12-02 ID: RUSTSEC-2020-0077 URL: https://rustsec.org/advisories/RUSTSEC-2020-0077 Dependency tree: memmap 0.7.0 ``` switch to https://github.com/RazrFalcon/memmap2-rs
Cargo audit reports a vulnerability in time 0.1.43 ``` Crate: time Version: 0.1.43 Title: Potential segfault in the time crate Date: 2020-11-18 ID: RUSTSEC-2020-0071 URL: https://rustsec.org/advisories/RUSTSEC-2020-0071 Solution: Upgrade to >=0.2.23...
**Is your feature request related to a problem? Please describe.** Currently the system is a blackbox for users while it is running. Improving observability would enable users to understand what...
Using `0.20.0-M5` blaze-server via the `BlazeServerBuilder`. On shutdown I can find the following entries in my logs. ``` ERROR org.http4s.blaze.channel.nio1.NIO1HeadStage - Abnormal NIO1HeadStage termination java.nio.channels.ShutdownChannelGroupException at org.http4s.blaze.channel.nio1.SelectorLoop.killSelector(SelectorLoop.scala:224) at org.http4s.blaze.channel.nio1.SelectorLoop.org$http4s$blaze$channel$nio1$SelectorLoop$$runLoop(SelectorLoop.scala:184) at...
Getting the `content_length` of a HEAD `Response`always returns `Some(0)` after updating to [0.10.4](https://github.com/seanmonstar/reqwest/releases/tag/v0.10.4). I am performing a simple HEAD request using the async client and I can see the header...
Investigation for https://github.com/agourlay/cornichon/issues/676 In this PR the `MatcherResolver` does not assume anymore any particular ordering for the corresponding `JsonPath`. Also `findAllPathWithValue` was greatly simplified, it should run much faster.
context #391