Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #3518

Closed (moved)
(moved)
Open
Created Jul 01, 2011 by Nick Mathewson@nickm🍬

Update circuit-launch and predictive circuit-launch logic for prop 171

Once we implement stream isolation correctly (#3517 (moved)), we will need to revise our code that launches circuits for predicted streams and our code that launches circuits for unhandled streams.

Right now (first approximation), we launch circuits until every unhandled stream has at least one in-progress circuit that it could attach to. But prop 171 breaks that behavior, since just because in-progress circuit C could handle stream A or handle stream B, it does not follow that it could handle A and B simultaneously.

There are similar issues with predicted circuits; we should analyze them in more depth too.

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