Ensure behavior is reasonable when paths can't be generated
We need to make sure we don't loop forever if we find ourselves in a situation where we can't generate any paths.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Nick Mathewson changed milestone to %Arti 1.0.0: Ready for production use
changed milestone to %Arti 1.0.0: Ready for production use
- Nick Mathewson added Backlog label
added Backlog label
- Gaba added 1 deleted label
added 1 deleted label
- Gaba added Sponsor 119 label and removed 1 deleted label
added Sponsor 119 label and removed 1 deleted label
- Contributor
Is this the same idea explained for
MAX_CIRCID_ATTEMPT
inget_unique_circ_id_by_chan()
in C-tor? Collapse replies - Author Owner
Like, insert a maximum number of attempts that we'll make to generate a path before we give up? That's one option, though I hope we can make things even better by building our code cautiously to avoid this kind of infinite
loop{}
entirely.
- Author Owner
See also #311 (closed) and #329 (closed).
- Nick Mathewson added Roadmap::Future label and removed Backlog label
added Roadmap::Future label and removed Backlog label
- Nick Mathewson assigned to @nickm
assigned to @nickm
- Nick Mathewson added Q2 label
added Q2 label
- Nick Mathewson added Backlog label and removed Roadmap::Future label
added Backlog label and removed Roadmap::Future label
- Nick Mathewson added Doing label and removed Backlog label
- Author Owner
This is handled by our arti-testing cases where we put all the relays in the same family and/or give all the exits an exit-policy of "reject *".
- Nick Mathewson closed
closed