#25573: Track half-closed stream IDs ------------------------------------------------+-------------------------- Reporter: mikeperry | Owner: (none) Type: defect | Status: | merge_ready Priority: Medium | Milestone: Tor: | 0.3.4.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: guard-discovery-stats 034-backport | Actual Points: Parent ID: #25574 | Points: Reviewer: teor | Sponsor: | SponsorV-can ------------------------------------------------+--------------------------
Comment (by mikeperry): Ok. I have renamed the 034 branch to ticket25573-034. It is 0 delta to ticket25573-v2 and ticket25573-v2-squashed3. It lives at: https://github.com/torproject/tor/pull/299 I created a merge commit to master from that branch as ticket25573-master: https://github.com/torproject/tor/pull/298 Let me know if that merge commit to master is how we want to do things. This is my first merge across the reorg border. If anyone wants further changes, please advise how you want me to manage the branches/merge commits (ie fixups on the merge commit, or on the previous commits, or squashed or rebased or not, etc). As for 034 backport, I guess the key question is: are any of these things "Smaller bugs that significantly impact user experience", as per https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases. If vanguards usage counts as user experience, then I think yes. The stream id data corruption issue that this branch fixes might count, too, but it's probably rare in practice. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25573#comment:22> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs