Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Arti Arti
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 230
    • Issues 230
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • ArtiArti
  • Issues
  • #50
Closed
Open
Issue created Dec 14, 2020 by Nick Mathewson@nickm🌻Owner

Circmgr needs a significant backend revision

The existing circmgr implementation doesn't always do the right thing. It keeps circuits and pending circuits in the same data structure. When a pending circuit is done, everything that was waiting for it is notified... but other streams that were waiting for a different port which the same circuit happens to handle are not notified.

We should have a new implementation that keeps a list of waiting requests, and launches circuits as appropriate to meet those streams' needs. When a circuit is done, it should notify every request that would be satisfied by it.

This doesn't have to be done for milestone A1, thankfully.

Assignee
Assign to
Time tracking