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

Re: [tor-bugs] #8005 [Stem]: stem parse_file errors when using descriptor_type='server-descriptor 1.0'



#8005: stem parse_file errors when using descriptor_type='server-descriptor 1.0'
-------------------------+--------------------------------------------------
 Reporter:  cypherpunks  |          Owner:  atagar
     Type:  defect       |         Status:  new   
 Priority:  normal       |      Milestone:        
Component:  Stem         |        Version:        
 Keywords:               |         Parent:        
   Points:               |   Actualpoints:        
-------------------------+--------------------------------------------------

Comment(by amj703):

 > > "ValueError: Line contains invalid characters: @downloaded-at
 2012-09-17 17:44:50"
 >
 > Hmmm, I'm not entirely sure about that one. Please attach a file that's
 causing this and the call you're using.

 Attached as tst-descriptors.

 > > "ValueError: The 'router' entry can only appear once in a descriptor"
 >
 > When I get the descriptor_type argument I'm treating it like a metrics
 archive. Maybe I should just drop the 'there's only one descriptor' check
 entirely. Please attach a small descriptor file that exemplifies this
 issue for me to use in the tests.

 Attached as tst-descriptors.2. Again, I want to be able to parse files
 containing multiple descriptors in, say, a the cached-descriptors format
 (although better would be that, given a descriptor_type, parse_file just
 goes ahead and tries to parse as many router entries as exist) even though
 it is not named cached-descriptors. I want to do that because I'm writing
 a simulator that is operating over a series of effective cached-
 descriptors representing the changing state of the network over time.

 Thanks!

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