Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

all_routers disappearing after NEWCONSENSUS? #203

Closed
meejah opened this issue Jan 20, 2017 · 3 comments
Closed

all_routers disappearing after NEWCONSENSUS? #203

meejah opened this issue Jan 20, 2017 · 3 comments
Labels

Comments

@meejah
Copy link
Owner

meejah commented Jan 20, 2017

It seems in latest txtorcon that the all_routers list in TorState becomes empty after a NEWCONSENSUS. Needs investigation.

@meejah
Copy link
Owner Author

meejah commented Jan 31, 2017

This does appear to be true, and I have a (small) fix but I still don't understand the actual problem exactly :/

@meejah meejah added the bug label Jan 31, 2017
@meejah
Copy link
Owner Author

meejah commented Feb 17, 2017

Early-return problem in f2a18c6

@meejah meejah closed this as completed Feb 17, 2017
meejah added a commit that referenced this issue Feb 17, 2017
@evilaliv3
Copy link
Contributor

thank you @meejah for fixing this so proactively!

i was just about to open this ticket and fix with the same patch :)

a good suggestion for all users of previous versions is to use state.routers.values() instead of state.all_routers().

this in the real could be an alternative that you could evaluate instead of keeping an additional list, it has a minor overhead due to the .values() call at runtime but due to the size of the object is really a minor thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants