Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:58:30Zhttps://gitlab.torproject.org/legacy/trac/-/issues/19325controller: getinfo to get status of cpuworker queues2020-06-13T14:58:30ZNick Mathewsoncontroller: getinfo to get status of cpuworker queuesTor: unspecifiedYawning AngelYawning Angelhttps://gitlab.torproject.org/legacy/trac/-/issues/19326Examine fine-grained connection detail; expose via control API2020-06-13T14:58:30ZNick MathewsonExamine fine-grained connection detail; expose via control APIconnections have lots of fields on them, and not all are currently exposed via getinfo. For testing, it might be useful to list more.connections have lots of fields on them, and not all are currently exposed via getinfo. For testing, it might be useful to list more.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/19328Try not to log from inside functions called from inside log functions2020-06-13T14:58:32ZNick MathewsonTry not to log from inside functions called from inside log functionsOur logging code is technically recursive now. Logging asks what the time is and tries to format it. Formatting the time can fail. Failures can log.Our logging code is technically recursive now. Logging asks what the time is and tries to format it. Formatting the time can fail. Failures can log.Tor: 0.3.5.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/19329Integrate callgraph complexity measures into our regular process2020-06-13T14:58:33ZNick MathewsonIntegrate callgraph complexity measures into our regular processUnless we track the size of the largest cycles in our code, big cycles may returnUnless we track the size of the largest cycles in our code, big cycles may returnTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/19361Improve coverage on compat_*threads and workqueue2020-06-13T14:58:35ZNick MathewsonImprove coverage on compat_*threads and workqueueSee my branch `thread_coverage`. It solves some but not all of #16798See my branch `thread_coverage`. It solves some but not all of #16798Tor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/19421test-network-all target does not work with out-of-tree builds2020-06-13T14:58:41Zcypherpunkstest-network-all target does not work with out-of-tree buildsThis is caused by assuming the test-driver script is the build directory. The Automake variable `LOG_DRIVER` contains the correct path.This is caused by assuming the test-driver script is the build directory. The Automake variable `LOG_DRIVER` contains the correct path.Tor: 0.2.9.x-finalcypherpunkscypherpunkshttps://gitlab.torproject.org/legacy/trac/-/issues/19428tv_mdiff rounds incorrectly2020-06-13T14:58:42ZNick Mathewsontv_mdiff rounds incorrectlySee XXXX lines in the unit tests I added in f05a213fe1706ce3ba76e12dc8e6f36f74c92794 : those lines fail, because of the rules for C negative division. The fix is trivial.See XXXX lines in the unit tests I added in f05a213fe1706ce3ba76e12dc8e6f36f74c92794 : those lines fail, because of the rules for C negative division. The fix is trivial.Tor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/19552Provide mechanism to find dirconns associated with a download_status_t, and e...2020-06-13T14:59:10ZAndrea ShepardProvide mechanism to find dirconns associated with a download_status_t, and expose active download attempts in GETINFO responseIt's hairy and complicated and different for every download status type to find out if / how many active attempts there are; we can do better.It's hairy and complicated and different for every download status type to find out if / how many active attempts there are; we can do better.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/19699Remove almost all functionality from Tor's test-network.sh2020-06-13T15:06:47ZteorRemove almost all functionality from Tor's test-network.shAll that we'll need is a stub that exists to locate chutney's test-network.sh.
The parts of the script that need to be deleted will be clearly marked as part of #19698.All that we'll need is a stub that exists to locate chutney's test-network.sh.
The parts of the script that need to be deleted will be clearly marked as part of #19698.Tor: 0.3.0.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/19701Allow tor and tor-gencert to be specified on the chutney command-line2020-06-13T13:29:47ZteorAllow tor and tor-gencert to be specified on the chutney command-lineAs well as being specified via the CHUTNEY_TOR and CHUTNEY_TOR_GENCERT environmental variables.As well as being specified via the CHUTNEY_TOR and CHUTNEY_TOR_GENCERT environmental variables.teorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/20041Test failure when running with --debug2020-06-13T15:00:57ZNick MathewsonTest failure when running with --debugOne of the tortls unit tests fails if you run the tests at debug.One of the tortls unit tests fails if you run the tests at debug.Tor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/20042Always log BUG messages from the unit tests2020-06-13T15:00:57ZNick MathewsonAlways log BUG messages from the unit testsOur log_test_helpers.c code is great, but it suppresses log messages that we would like to see!
Also, we should always see BUG messages unless we're specifically suppressing them.
This could be sponsorS (testing) or sponsorU (since I n...Our log_test_helpers.c code is great, but it suppresses log messages that we would like to see!
Also, we should always see BUG messages unless we're specifically suppressing them.
This could be sponsorS (testing) or sponsorU (since I need it to test the link handshake improvements of #15555)Tor: 0.2.9.x-finalNick MathewsonNick Mathewson