Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:39:50Zhttps://gitlab.torproject.org/legacy/trac/-/issues/29897Refactor handle_get_next_bandwidth() to use connection_dir_buf_add()2020-06-13T15:39:50ZteorRefactor handle_get_next_bandwidth() to use connection_dir_buf_add()After #21377 merges, we want to refactor handle_get_next_bandwidth() to use connection_dir_buf_add().
If we backport this refactor to 0.4.0 or earlier, we'll also need #29896 for the connection_dir_buf_add() backport.After #21377 merges, we want to refactor handle_get_next_bandwidth() to use connection_dir_buf_add().
If we backport this refactor to 0.4.0 or earlier, we'll also need #29896 for the connection_dir_buf_add() backport.Tor: 0.4.0.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/28223Unparseable microdescriptor on public relay2020-06-13T15:33:25ZteorUnparseable microdescriptor on public relayA relay operator reported this error:
```
Get this at my exit relay since yesterday:
# head /tmp/warn.log
Oct 23 23:30:17.000 [notice] Tor 0.3.5.3-alpha opening new log file.
Oct 23 23:30:33.000 [warn] parse error: internal NUL characte...A relay operator reported this error:
```
Get this at my exit relay since yesterday:
# head /tmp/warn.log
Oct 23 23:30:17.000 [notice] Tor 0.3.5.3-alpha opening new log file.
Oct 23 23:30:33.000 [warn] parse error: internal NUL character.
Oct 23 23:30:33.000 [warn] Unparseable microdescriptor
Oct 23 23:30:33.000 [warn] parse error: internal NUL character.
Oct 23 23:30:33.000 [warn] Unparseable microdescriptor
even with log level "debug" there seems to be no more information.
Anything I should worry about?
```
https://lists.torproject.org/pipermail/tor-relays/2018-October/date.htmlTor: 0.4.0.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/26770Implement proposal 293: "Other ways for relays to know when to publish"2020-06-13T15:27:56ZNick MathewsonImplement proposal 293: "Other ways for relays to know when to publish"Tor: 0.4.0.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/21377DirAuths should expose bwauth bandwidth files2022-02-16T21:12:43ZTom Rittertom@ritter.vgDirAuths should expose bwauth bandwidth filesCurrently, DirAuths that vote on bwauth files do not expose the raw voting file they used. This data would be good to archive for debugging and transparency purposes.Currently, DirAuths that vote on bwauth files do not expose the raw voting file they used. This data would be good to archive for debugging and transparency purposes.Tor: 0.4.0.x-finaljugajuga