[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #6505 [Tor Client]: GETINFO dir/status-vote/current/consensus returns "Unrecognized key" if no consensus available

#6505: GETINFO dir/status-vote/current/consensus returns "Unrecognized key" if no
consensus available
------------------------+---------------------------------------------------
 Reporter:  zwol        |          Owner:  zwol              
     Type:  defect      |         Status:  needs_revision    
 Priority:  normal      |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Client  |        Version:  Tor: 0.2.3.19-rc  
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by nickm):

  * milestone:  Tor: 0.2.3.x-final => Tor: 0.2.4.x-final


Comment:

 Hm.  If we're going to add a new error code here though (say, "452 data
 not available"), we probably want to use it for other cases that currently
 yield "552 unrecognized key" too.  And doing that might well break other
 controllers.

 I think for 0.2.3 the right answer is that we should fix pytorctl. For
 0.2.4, we can figure out which kind of change would be least disruptive to
 the other controllers.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6505#comment:4>
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