Amaury Chamayou comments

Results 254 comments of


                                            Amaury Chamayou

LeakSanitiser break on some shutdowns in Daily build

Addressed in #1776

LeakSanitiser break on some shutdowns in Daily build

Much less frequent outside docker, but happened again in https://dev.azure.com/MSRC-CCF/CCF/_build/results?buildId=14777&view=logs&j=88dd69b5-c778-5f1c-f9ac-1398f4203929&t=f18b20af-6d89-55d5-5278-1002871723a4 45: Tracer caught signal 11: addr=0x0 pc=0x4f46b0 sp=0x7feb2c010d30 45: ==3229==LeakSanitizer has encountered a fatal error. 45: ==3229==HINT: For debugging, try...

CCF node should reply with a timeout error if a request takes too long to execute

@olgavrou no it doesn't, the node that does the forwarding still needs to decide the response isn't coming back and tell the client.

CCF node should reply with a timeout error if a request takes too long to execute

This is an important quality of life issue to be solved in 3.x, and depends on the re-thinking of forwarding.

A malicious host could cause a denial of service by manipulating tick()

We think implementation of the `PreVote` extension to Raft (https://web.stanford.edu/~ouster/cgi-bin/papers/OngaroPhD.pdf 9.6, ticketed in #2577 ) will mitigate this problem without requiring an expensive busy-wait.

Support `make_read_only_endpoint` to be used with historical query adapter

@letmaik that's a good point, we could have `read_only_adapter_v1` and `write_only_adapter_v1` I suppose?

Generic performance testing driver

https://github.com/WillAllmeida/performance_client

Initial end-to-end tests simulating host tampering, impact on historical queries

@eddyashton that does seem especially good to have with the file copy/management changes we've discussed coming up.

Support bare keys in JWKS for JWT auth

@letmaik is this a blocker for a particular use case?

Test AMD pool

/azp run