[tor-bugs] #9264 [BridgeDB]: Problem with transport lines in BridgeDB's bridge pool assignment files

[Tor Bug Tracker & Wiki]

#9264: Problem with transport lines in BridgeDB's bridge pool assignment files
----------------------+-----------------------------------------------------
 Reporter:  karsten   |          Owner:              
     Type:  defect    |         Status:  needs_review
 Priority:  major     |      Milestone:              
Component:  BridgeDB  |        Version:              
 Keywords:            |         Parent:              
   Points:            |   Actualpoints:              
----------------------+-----------------------------------------------------

Comment(by aagbsn):

 Replying to [ticket:9264 karsten]:
 > Also, I saw Isis mention this the other day, but I'm not sure if there's
 already a ticket for it:
 >
 > {{{
 > 1093d197b5eab404f30806948367483ad5c7482e email ip=4 flag=stable
 > 112f02b648f19502831103fa50715ce31f8a4a2e email ip=4 flag=stable port=443
 > 112f02b648f19502831103fa50715ce31f8a4a2e email ip=4 flag=stable port=443
 transport=obfs3,obfs2
 > 11b3a235c05843fbc57f29a848dee6dc6a6be118 unallocated
 > }}}
 >
 > Note the duplicate entry for `112f02b648f19502831103fa50715ce31f8a4a2e`.
 The first line shouldn't be there, I guess.
 >
 > Setting priority to major, because the currently produced bridge pool
 assignments won't be useful for analysis.

 Are those entries adjacent? Or was this output produced with {{{sort}}}? I
 noticed that for each assignment period a line is written 3 times for each
 bridge (but the lines are not consecutive). That suggests that the bug
 might have something to do with the function
 BridgeSplitter.dumpAssignments() in Bridges.py:923 ... but it isn't clear
 to me why that occurs yet.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9264#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online