Open
Milestone
sbws: 1.1.x-final
All issues for this milestone are closed. You may close this milestone now.
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
65
- Test net keys expired
- Maybe vote on the relays that have few or close measurements
- Check that relay_recent_measurement_attempt_count and relay_recent_priority_list_count are correc
- Compare sbws and Torflow
- Scale exactly as torflow does?
- For relays that change ip, only the measurements with the last ip are kept
- Relays without descriptors are not scaled, but still added to the bwlines without vote=0
- sbws measures some relays 100x lower than Torflow
- Migrate to gitlab.tpo
- Correct the relays to keep after retrieving new consensuses
- Document that bwauths should checkout stable versions when installing sbws from git
- Is sbws weighting some relays too high?
- Fix lint error after merging #30733
- Check changes related to descriptors in a bandwidth file created by a bwauth before next release
- Deploy sbws in the rest of bwauths
- Check that consensus timestamp lists is initialied and has at list one item
- sbws stuck thinking a destination is dead
- sbws bandwidth scans should require a minimum exit bandwidth
- sbws consensus timestamp updates incorrectly use the current time
- race condition: new_relays_dict is modified during iteration
- Maybe monitoring values in the state file should be reset when sbws is restarted
- Remove division when logging "last days"
- Include the commit hash in the sbws version
- Unclear check for skipping scaling due to missing bandwidths or missing descriptors
- Work out which relays are ignored by all sbws instances
- sbws does not detect changes in descriptor bandwidth values
- Make sbws vote for all measured relays, even if they are not Running / not in the consensus
- Missing relay keys in bandwidth file spec
- Does "success" record relay measurements older than 5 days?
- Work out why relay_in_recent_consensus_count is 13 days for some relays
- Work out why no measurements are excluded because they are too old
- Work out why 90% of sbws measurements fail
- Do not scale relays' bandwidth when there is not descriptor
- Work out what sbws is doing in its measurement threads
- Document that there is now stable branch
- Minor fixes from observed behaviour in the public network
- Missing diagnostic keys in relay lines, but the data is in the header
- sbws should show relays for diagnostics, even when MIN_REPORT has not been reached
- Document the new bandwidth file keys added in sbws 1.1.0
- Create debian package for last 1.1.0 version
- Create 1.1.0 release
- Deprecate torflow
- Create a blog post about work done and future work
- Document next steps and/or tickets remaining
- Document that authorities are not measured
- Add KeyValues to monitor relays that are not measured
- Recover a destination when it stops failing
- Include scanner country and Web server country in the bandwidth file header
- Help 2-3 dirauths to deploy sbws
- Measure first relays with the lowest number of attempts first.
- Work out how long it takes sbws to measure the network
- sbws keeps the number of AsyncResults less than the number of threads
- sbws AsyncResults have no timeout
- Try enabling predicted circuits in sbws
- When CircuitPadding is implemented in Tor, set it to 0 in sbws
- sbws stops accumulating, silently
- When sbws stops making progress, log a warning
- After several days, most of the circuits timeout
-
Report relays that sbws wants to test, but the test doesn't work
#28567 changes-version-minor component::core tor/sbws milestone::sbws: 1.1.x-final owner::juga parent::28547 points::1 priority::medium resolution::implemented reviewer::nickm sbws-1.0-must-moved-20181128 sbws-110-proposed sbws-11x-final-removed-20190312 severity::normal status::closed tor-bwauth type::defect
- Report relays that sbws sees in the consensus, but never chooses to test
-
Report excluded results in a relay's bandwidth line
#28565 changes-version-minor component::core tor/sbws milestone::sbws: 1.1.x-final owner::juga parent::28547 points::1 priority::medium resolution::implemented reviewer::teor sbws-1.0-must-moved-20181128 sbws-110-proposed sbws-11x-final-removed-20190312 severity::normal status::closed tor-bwauth type::defect
-
Work out how sbws can report excluded relays in the bandwidth file
#28563 changes-version-minor component::core tor/sbws milestone::sbws: 1.1.x-final owner::juga parent::28547 priority::medium resolution::implemented reviewer::nickm sbws-1.0-must-moved-20181128 sbws-110-proposed sbws-11x-final-removed-20190312 severity::normal status::closed tor-bwauth type::defect
- Monitor relays that are not measured by each sbws instance
- Disable measurement timing rules on sbws by default
- Monitor dirauth running sbws in production
Loading
Loading