Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #32020
Closed (moved) (moved)
Open
Issue created Oct 09, 2019 by David Goulet@dgoulet🐼

hsv3: Client do not report failing circuit back into HS subsystem

This is a subtask of the bigger larger problem in #25882 (moved).

A v2 client does report intro point failures within circuit_about_to_free() but not v3.

Actually, any HS circuit client side is not looked at. The hs_circ_cleanup() was intended for this as the entry point in the HS subsystem but only the service uses it.

Intro circuit failure needs to be noted in the failure cache (hs_cache_client_intro_state_note()).

Rendezvous circuit need to be also somehow handled. If the RP circuit keeps closing on us, we might want to stop trying maybe?

Same goes for HSDir circuit, if they close, client needs to be notified and launch a refetch.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking