reduce reqwest timeout to 5s #557
Sem revisor
Etiquetas
Nenhum rótulo
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Sem marco
Sem projeto
Sem responsáveis
2 participantes
Notificações
Data limite
Não há data limite definida.
Dependências
Não há dependências definidas.
Referência: Plume/Plume#557
Carregando…
Adicionar tabela
Referência em uma nova issue
Nenhuma descrição fornecida.
Excluir branch "reduce-timeout"
Apagar um branch é permanente. Ainda que o branch apagado possa continuar a existir por um breve período antes de ser realmente apagado, isso NÃO PODE ser desfeito na maioria dos casos. Continuar?
Current timeout is 30s, this add a second kind of timeout : if connection to remote can't be established in 5s, the remote is considered down, so that a thread don't stall for too long for no reason (and also make some unit test much faster to run)
It makes me think: couldn't we have a unique client (in a
lazy_static!
or something like that). I think reqwest keep connections for a certain time if the client is not dropped, and it probably caches DNS too.Otherwise, it looks good to me, so if the CI is happy you can merge.
Codecov Report
maybe not a unique client (if we have multiple request to do at the same time they will be queued), but we could probably make some kind of pool of clients. I'll keep the idea somewhere for when I have spare time to spend