[tor-bugs] #7713 [Stem]: Stem should invalidate GETCONF cache
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu May 16 03:46:39 UTC 2013
#7713: Stem should invalidate GETCONF cache
-----------------------------+----------------------------------------------
Reporter: atagar | Owner: atagar
Type: defect | Status: needs_revision
Priority: minor | Milestone:
Component: Stem | Version:
Keywords: controller easy | Parent:
Points: | Actualpoints:
-----------------------------+----------------------------------------------
Comment(by atagar):
> I've also noticed that CONF_CHANGED events with the following config are
being sent to the listener.
>
> {'NodeFamily': 'mno,tuv,wxyz'}
> {'NodeFamily': None}
That seems really odd. Do you know where that second one is coming from?
Please try connecting to a tor instance with telnet and seeing what raw
CONF_CHANGED events that tor provides in response to that SETCONF. We
might be uncovering a tor bug here. ;)
> One way to make the test work would be to set an option for not updating
the cache in the test and then check it in the listener.
If the cache ever disagrees with what 'GETCONF' provides then that is a
stem bug. Disabling the cache for the test would simply mask the issue.
> I also modified the test to check if the cache is updated when another
controller changes the config.
https://github.com/lucyd/stem/commit/78da5aece13701d2b6b3d509d2aaeb8cdb70a040
Thanks! Please add this as its own test (there's no need to bundle it with
another).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7713#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list