Re: [tor-bugs] #22172 [Core Tor/Tor]: prop140: What to do when a diff fails to apply?

[Tor Bug Tracker & Wiki]

#22172: prop140: What to do when a diff fails to apply?
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor4
--+
Changes (by nickm):

 * status:  needs_information => closed
 * resolution:   => worksforme


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #22172 [Core Tor/Tor]: prop140: What to do when a diff fails to apply?

[Tor Bug Tracker & Wiki]

#22172: prop140: What to do when a diff fails to apply?
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor4
--+
Changes (by nickm):

 * parent:  #13339 =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #22172 [Core Tor/Tor]: prop140: What to do when a diff fails to apply?

[Tor Bug Tracker & Wiki]

#22172: prop140: What to do when a diff fails to apply?
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #13339| Points:
 Reviewer:|Sponsor:  Sponsor4
--+
Changes (by nickm):

 * status:  accepted => needs_information


Comment:

 Putting this into needs_information. I want to keep an eye on this as we
 try it in practice, but I think that the current approach will likely turn
 out to be okay.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #22172 [Core Tor/Tor]: prop140: What to do when a diff fails to apply?

[Tor Bug Tracker & Wiki]

#22172: prop140: What to do when a diff fails to apply?
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #13339| Points:
 Reviewer:|Sponsor:  Sponsor4
--+

Comment (by nickm):

 I think we can treat a non-applying diff as if we had downloaded a bogus
 consensus. Rationale: we provided the source SHA3 digest that the diff is
 supposed to apply to; if it doesn't apply, then the cache is deeply
 confused, or we are.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #22172 [Core Tor/Tor]: prop140: What to do when a diff fails to apply?

[Tor Bug Tracker & Wiki]

#22172: prop140: What to do when a diff fails to apply?
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #13339| Points:
 Reviewer:|Sponsor:  Sponsor4
--+
Changes (by nickm):

 * owner:   => nickm
 * status:  new => accepted


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #22172 [Core Tor/Tor]: prop140: What to do when a diff fails to apply?

[Tor Bug Tracker & Wiki]

#22172: prop140: What to do when a diff fails to apply?
--+
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #13339
   Points:|   Reviewer:
  Sponsor:  Sponsor4  |
--+
 Right now, we treat failures to apply a consensus diff as if the consensus
 download had failed.  Is this what we should be doing?

 (Formerly part of #22148)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs