[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #16276 [Onionoo]: bug in onionoo's family set detection
#16276: bug in onionoo's family set detection
-----------------------------+--------------------------
Reporter: cypherpunks | Owner:
Type: enhancement | Status: needs_review
Priority: normal | Milestone:
Component: Onionoo | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-----------------------------+--------------------------
Comment (by leeroy):
> Speaking of, I think I'll have to revise that branch and put the part
back where the node indexer computes effective families itself.
Otherwise, it'll require a coordinated update of hourly updater and
server.
What do you mean by coordinated update? The node indexer checks the store
for update time then rebuilds itself. The only thing that changed is that
previously Onionoo got the declared family from the store, made a copy in
index, computed effective, and retained effective family in index. Now the
effective family is computed during document write, after updating the
store, and during index the effective family is copied.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16276#comment:29>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs