Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • argonaut argonaut
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectory
  • argonautargonaut
  • Issues
  • #4629
Closed
Open
Created Mar 17, 2016 by Côme Chilliet@cchillietReporter

Better handling of timeouts

It seems argonaut client timeout is 10 in JSON::RPC::Client code and we can’t change it. We should find a way to change this and make sure client timeout is always longer than server timeout.

Argonaut server state cache may be activated again thanks to these changes (see #2426 )

Edited Jan 03, 2021 by bmortier
Assignee
Assign to
Time tracking