The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-08-14T17:07:23Zhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41239Reverse DNS for IPv6 not working for gnt-dal cluster2023-08-14T17:07:23ZJérôme Charaouilavamind@torproject.orgReverse DNS for IPv6 not working for gnt-dal clusterWhile adding a new host to DNSwl, I noticed that our IPv6 reverse DNS records were not resolving for machines in the gnt-dal cluster.
```
$ dig -x 2620:7:6002:0:3eec:efff:fed5:6b2a
; <<>> DiG 9.16.37-Debian <<>> -x 2620:7:6002:0:3eec:e...While adding a new host to DNSwl, I noticed that our IPv6 reverse DNS records were not resolving for machines in the gnt-dal cluster.
```
$ dig -x 2620:7:6002:0:3eec:efff:fed5:6b2a
; <<>> DiG 9.16.37-Debian <<>> -x 2620:7:6002:0:3eec:efff:fed5:6b2a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60083
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;a.2.b.6.5.d.e.f.f.f.f.e.c.e.e.3.0.0.0.0.2.0.0.6.7.0.0.0.0.2.6.2.ip6.arpa. IN PTR
;; AUTHORITY SECTION:
0.0.0.0.2.0.0.6.7.0.0.0.0.2.6.2.ip6.arpa. 1 IN SOA ns1.torproject.org. anarcat.torproject.org. 2023021017 900 600 86400 3600
;; Query time: 132 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun 21 10:41:33 EDT 2023
;; MSG SIZE rcvd: 163
;; Query time: 132 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun 21 10:41:33 EDT 2023
;; MSG SIZE rcvd: 163
```anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41238Retire forum-test-012023-06-28T15:59:55ZJérôme Charaouilavamind@torproject.orgRetire forum-test-01This machine was used for prototyping Discourse hosting that was deployed as part of https://gitlab.torproject.org/tpo/tpa/team/-/issues/41063
1. ~~[ ] announcement~~ (N/A)
2. [x] nagios
3. [x] retire the host in fabric
4. [x] remov...This machine was used for prototyping Discourse hosting that was deployed as part of https://gitlab.torproject.org/tpo/tpa/team/-/issues/41063
1. ~~[ ] announcement~~ (N/A)
2. [x] nagios
3. [x] retire the host in fabric
4. [x] remove from LDAP with `ldapvi`
5. [x] power-grep
6. [x] remove from tor-passwords
7. ~~[ ] remove from DNSwl~~ (N/A)
8. [x] remove from docs
9. ~~[ ] remove from racks~~ (N/A)
10. [x] remove from reverse DNSJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/core/arti/-/issues/913Questions for an expert on hidden services2023-12-11T21:03:52ZIan Jacksoniwj@torproject.orgQuestions for an expert on hidden services(**Note** It's probably best to start a separate reply thread for each question (or set of related questions), or we'll become totally lost.)
We (Arti folks) have a number of questions that we would like an expert on onion services to h...(**Note** It's probably best to start a separate reply thread for each question (or set of related questions), or we'll become totally lost.)
We (Arti folks) have a number of questions that we would like an expert on onion services to have an opinion about. They're all about what the client behaviour should be:
1. How long should an HS client circuit, that is not currently being used, be retained?
2. After having received INTRODUCE_ACK, is it OK to tear down the introduction circuit immediately, or should we wait for rendezvous completion?
3. HS descriptor downloading: currently, for each HS, Arti tries one hsdir at a time. How important is it to parallelise these attempts?
4. Introduction/rendezvous: currently, Arti tries one introduction point at a time. Again, how important is it to parallelise these attemnpts?
5. Rendezvous circuit construction: currently Arti tries to maintain a pool of circuits ready for use as rendezvous, but if many HS connections are made at once, that pool will become depleted. Then, Arti would *serialise* building a new rendezvous circuit, with the building of the introduction circuit. How much does this matter?
6. Arti currently serialises (i) the RENDEZVOUS exchange with (ii) building the introduction circuit and sending INTRODUCE1, even though in principle they could be paralellised. Does this matter?
7. Descriptor lifetime. Revision numbers vs expiry times. Currently, once Arti has successfully obtained an HS descriptor, it retains it until it has expired according to its declared lifetime. After its declared lifetime, Arti will unconditionally discard it (and attempt to obtain a new descriptor). Arti ignores the revision counter. Is this right? Should rendezvous failures prompt descriptor re-download? When?
8. We have a number of timeouts and retry counters which we're not sure we have the right values for:
```
// For descriptor downloading
// TODO HS are these right? make configurable? get from netdir?
// TODO HS should we even have MAX_TOTAL_ATTEMPTS or should we just try each one once?
/// Maxmimum number of hsdir connection and retrieval attempts we'll make
const MAX_TOTAL_ATTEMPTS: usize = 6;
/// Limit on the duration of each retrieval attempt
const EACH_TIMEOUT: Duration = Duration::from_secs(10);
// For introduction and rendezvous
// TODO HS are these right? make configurable? get from netdir?
// TODO HS should we even have this or should we just try each one once?
/// Maxmimum number of rendezvous/introduction attempts we'll make
const MAX_TOTAL_ATTEMPTS: usize = 6;
/// Limit on the duration of each attempt to establishg a rendezvous point
const REND_TIMEOUT: Duration = Duration::from_secs(10);
/// Limit on the duration of each attempt to negotiate with an introduction point
const INTRO_TIMEOUT: Duration = Duration::from_secs(10);
/// Limit on the duration of each attempt for activities involving both RPT and IPT
const RPT_IPT_TIMEOUT: Duration = Duration::from_secs(10);
```
CC @dgouletArti: Onion service supportNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41237Archive tor-talk mailing list2023-06-28T14:37:52ZGusArchive tor-talk mailing listAs TPA is now self-hosting the Tor Forum, it's time to archive the tor-talk mailing list: https://lists.torproject.org/pipermail/tor-talk/
I'll send the announcement this week and then you can archive the mailing list.
Ref: https://gi...As TPA is now self-hosting the Tor Forum, it's time to archive the tor-talk mailing list: https://lists.torproject.org/pipermail/tor-talk/
I'll send the announcement this week and then you can archive the mailing list.
Ref: https://gitlab.torproject.org/tpo/community/support/-/issues/40057Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/329Review support entries for Tor Browser 12.5 release2023-06-23T14:57:09ZGusReview support entries for Tor Browser 12.5 releasechampionquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/community/support/-/issues/40115Review user support templates for Tor Browser 12.5 release2023-06-28T14:05:23ZGusReview user support templates for Tor Browser 12.5 releasechampionquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/network-health/metrics/descriptorParser/-/issues/42More clean-up in descriptor parser code2023-06-26T14:11:22ZGeorg KoppenMore clean-up in descriptor parser codeWhile going over !22 I realized we might want to fix up more in ExtraDescriptorParser.java while we are at it. This will happen in this ticket to not pollute !22 with unrelated stuff we should not forget, though.While going over !22 I realized we might want to fix up more in ExtraDescriptorParser.java while we are at it. This will happen in this ticket to not pollute !22 with unrelated stuff we should not forget, though.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/core/arti/-/issues/903keymgr: Implement key bundles2023-10-03T18:47:38Zgabi-250keymgr: Implement key bundles[key-management.md](https://gitlab.torproject.org/tpo/core/arti/-/blob/d75b4af0f1ea6d1f43bcb626cc2f4b4e231a8413/doc/dev/notes/key-management.md) talks about "key bundles" and why we need them.
While the arti keystore already has a `has_...[key-management.md](https://gitlab.torproject.org/tpo/core/arti/-/blob/d75b4af0f1ea6d1f43bcb626cc2f4b4e231a8413/doc/dev/notes/key-management.md) talks about "key bundles" and why we need them.
While the arti keystore already has a `has_key_bundle` function, it's actually just an implementation stub.
We need to:
* come up with a more precise definition for "key bundles"
* implement key bundles in `ArtiNativeKeyStore`Arti: Onion service supportgabi-250gabi-250https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41854Download Spam Protection cannot be overridden to allow legitimate downloads2023-10-05T12:50:33ZdonutsDownload Spam Protection cannot be overridden to allow legitimate downloadsA user has reported the following issue with file downloads on 12.0.7 [on the forum](https://forum.torproject.net/t/download-bug-in-tor-browser-12-0-7/8043):
> I’m on Linux, with Tor Browser 12.0.7
>
> I’m trying to download (PDF) file...A user has reported the following issue with file downloads on 12.0.7 [on the forum](https://forum.torproject.net/t/download-bug-in-tor-browser-12-0-7/8043):
> I’m on Linux, with Tor Browser 12.0.7
>
> I’m trying to download (PDF) files from a site i’ve downloaded from many times before.
>
> - Get a yellow triangle on downloads icon.
> - open it and it says “Downloads blocked from ”
> - click Show more information
> - says “ attempted to automatically download multiple files. The site could be broken or trying to store spam files on your device.”
>
> Options to “Allow Download” or “Remove Files” don’t seem to do anything or change the behavior.
>
> Each time I click a link to download a file from this site I get another message like this. (it worked the first time)
At least [two other users on reddit](https://old.reddit.com/r/TOR/comments/146ge44/download_bug_in_tor_browser_1207/) have reported the same bug. However it's seemingly not an issue in 12.5a7 [according to the original reporter](https://forum.torproject.net/t/download-bug-in-tor-browser-12-0-7/8043).ma1ma1https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40275Bump verison of snowflake to v2.6.02023-06-20T18:48:10ZCecylia BocovichBump verison of snowflake to v2.6.0Let's do a library version bump and update the version shipped in Tor BrowserLet's do a library version bump and update the version shipped in Tor BrowserCecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41236gitolite: Redirect tor.git to Gitlab2023-06-26T16:15:35ZDavid Gouletdgoulet@torproject.orggitolite: Redirect tor.git to GitlabHello,
Network team is ready to have `tor.git` on Gitolite to be redirected to Gitlab and thus become canonical repository:
https://gitweb.torproject.org/tor.git -> https://gitlab.torproject.org/tpo/core/tor
Thanks!Hello,
Network team is ready to have `tor.git` on Gitolite to be redirected to Gitlab and thus become canonical repository:
https://gitweb.torproject.org/tor.git -> https://gitlab.torproject.org/tpo/core/tor
Thanks!legacy Git infrastructure retirement (TPA-RFC-36)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41235Redirect and destroy stem.git gitolite to Gitlab2023-06-26T16:15:01ZjugaRedirect and destroy stem.git gitolite to GitlabWe've just migrated stem to gitlab (https://gitlab.torproject.org/tpo/network-health/team/-/issues/307), so you can now destroy the one at https://gitweb.torproject.org/stem.git and redirect it to https://gitlab.torproject.org/tpo/networ...We've just migrated stem to gitlab (https://gitlab.torproject.org/tpo/network-health/team/-/issues/307), so you can now destroy the one at https://gitweb.torproject.org/stem.git and redirect it to https://gitlab.torproject.org/tpo/network-health/stem.git
Thanks!legacy Git infrastructure retirement (TPA-RFC-36)https://gitlab.torproject.org/tpo/tpa/team/-/issues/41234Need more memory on metricsdb-012023-06-27T04:13:59ZHiroNeed more memory on metricsdb-01I have noticed we might need more memory on metricsdb-01. I have seen VM being restarted with oom errors. I have topped the highest amount of memory that the java parser can use to 8GB, but I think we would be better of with 10 more GB o...I have noticed we might need more memory on metricsdb-01. I have seen VM being restarted with oom errors. I have topped the highest amount of memory that the java parser can use to 8GB, but I think we would be better of with 10 more GB of ram available.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/network-health/team/-/issues/307Move stem from git.tpo to gitlab.tpo2024-02-07T17:52:58ZjugaMove stem from git.tpo to gitlab.tpoSince TPA'll remove git.tpo and tpo/core/tor depends on it.Since TPA'll remove git.tpo and tpo/core/tor depends on it.jugajugahttps://gitlab.torproject.org/tpo/network-health/metrics/descriptorParser/-/issues/41Parser runs out of memory we should use some memory management algorithm when...2023-06-16T06:01:07ZHiroParser runs out of memory we should use some memory management algorithm when we load itNoticed the parser runs out of memory when processing many descriptors. We should use a memory management algorithm of those available with Java like we did with other services.
Ex this is what we use on the website:
```
java -XX:+UseSh...Noticed the parser runs out of memory when processing many descriptors. We should use a memory management algorithm of those available with Java like we did with other services.
Ex this is what we use on the website:
```
java -XX:+UseShenandoahGC -Xms32m -XX:+UnlockExperimentalVMOptions -XX:ShenandoahUncommitDelay=1000 -XX:ShenandoahGuaranteedGCInterval=10000 -Xmx10g
```HiroHirohttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41232gitolite: Redirect or close several projects for Network Team2023-06-26T16:14:38ZDavid Gouletdgoulet@torproject.orggitolite: Redirect or close several projects for Network TeamGreetings,
The following can simply be **closed** without any redirections:
- https://gitweb.torproject.org/testnet.git/
- https://gitweb.torproject.org/tor-rust-dependencies.git/
The following should be **redirected**:
- https://git...Greetings,
The following can simply be **closed** without any redirections:
- https://gitweb.torproject.org/testnet.git/
- https://gitweb.torproject.org/tor-rust-dependencies.git/
The following should be **redirected**:
- https://gitweb.torproject.org/fallback-scripts.git/ -> https://gitlab.torproject.org/tpo/core/fallback-scripts
- https://gitweb.torproject.org/chutney.git/ -> https://gitlab.torproject.org/tpo/core/chutney
- https://gitweb.torproject.org/fuzzing-corpora.git/ -> https://gitlab.torproject.org/tpo/core/fuzzing-corpora
- https://gitweb.torproject.org/trunnel.git/ -> https://gitlab.torproject.org/tpo/core/trunnellegacy Git infrastructure retirement (TPA-RFC-36)https://gitlab.torproject.org/tpo/network-health/team/-/issues/306New round of contacting operators for DNS issues and badexiting problematic r...2023-07-04T11:27:31ZGeorg KoppenNew round of contacting operators for DNS issues and badexiting problematic relays (06/12/2023)We got a bunch of exits with DNS issues from this weeks scan on Monday:
```
Relay 014326416058DCFD0965167026CBEF647409A000 failed DNS check 5/5 times
Relay 034ED155E6DA8277BC7F294896BFD7013D7BD7B0 failed DNS check 5/5 times
Relay 0A180D2...We got a bunch of exits with DNS issues from this weeks scan on Monday:
```
Relay 014326416058DCFD0965167026CBEF647409A000 failed DNS check 5/5 times
Relay 034ED155E6DA8277BC7F294896BFD7013D7BD7B0 failed DNS check 5/5 times
Relay 0A180D2D5E2F4925DE30E7DE7B822FAF672A4AAC failed DNS check 5/5 times
Relay 0A97C6889F8BB21B02BDFD25BE1455D0E4B80D29 failed DNS check 5/5 times
Relay 0DF4CB956237DB411A19DF0935B322F75E69533D failed DNS check 5/5 times
Relay 3ED8870AA9CC036CEC47805A66D7DA09617B66D9 failed DNS check 5/5 times
Relay 5F0AB128C9C6F1D9F01708F1A066C6E2A22D8D49 failed DNS check 1/1 times
Relay 8855F15DD749176F285636182C3959DB54D21185 failed DNS check 2/2 times
Relay A0B5B5906EB13F213D7CA9AFEC91934BE3A5930F failed DNS check 5/5 times
Relay B891CB6370CF7C51C6FB24D80947AFB7ED463D00 failed DNS check 5/5 times
Relay C7A51E46740C15DEC0535AF5560A1919CE6E5758 failed DNS check 5/5 times
Relay E4DCE273C7EDD26766B4CE54382CBC2711AE415C failed DNS check 5/5 times
Relay F59D3D313A027703E51DC7DF793F2ED106C2E372 failed DNS check 5/5 times
```Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41231Please add juga to the doctor and exitmap groups and let them access carinatum2023-07-10T08:39:20ZGeorg KoppenPlease add juga to the doctor and exitmap groups and let them access carinatum```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please add juga to the doctor and exitmap groups and get them access to
carinatum so they can help with network-health work.
Thanks!
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEV+B...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please add juga to the doctor and exitmap groups and get them access to
carinatum so they can help with network-health work.
Thanks!
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEV+BCWXPceMSRn284y3isMjDqp+oFAmSK7UYACgkQy3isMjDq
p+pJRg//ZTHVDJIceAcNwTiF7AuG9QqfLqPdqq2UDHKUrjU1ziXrrOBJ2PbvS6ht
91sp6tzTEPBY1ouywtRG1CSNYFCDVDcObB9TroXUamQP7yCzYaq24qCBxMGlIkOm
7w3kx6cwXvnrJoIl0wa1BjPPVKukbKYok1uK9RWjHilpLRNLARFrDF8KVCqOwRUO
SvLfL3dOCPHyMWHPmsk9zddWmqZrQjtfpvdy4zb4N4lTFhVgS9WFlQxvU+29oFD5
sCf0pxRVr3ILeDg8xbUN4Aue6/I+TlVCNr9RfDt2z5nv3+Ha4jwxPVwCbH8XNqR6
3rDycfLvmZ3mTZquLSIDpXnbKTNNY8EeQqGe0FuSsJASatcY9iPlk7VrkAH0Clgo
AeewX4+bUtqNh/0zcJVIPejBCe3vf1kp2GfXotIEfZccpNRVGEO6VWLcuJaGE3XD
RGfdYx9M6itbDr80erCczHzEPglrjrQ046BojMcJ/k36lLs/dKnODEFwS+ji7Gbs
pWyApQssCWi2ySznpDJMKgodPpQ+wjTmsolg56pUsCTGohJOIfct6gsSg22ofJKn
YkIy+0S9R1LPazaMX2qbi5WLIixwlrrOK3qQTPVGkB91l7x55wBmEevD45SKodxC
QEbf+Z+hcP4wgc9maAgzZcW4hLsDR6HXYynT7vhj6hd2AKwJNA4=
=lDLz
-----END PGP SIGNATURE-----
```
/cc @jugahttps://gitlab.torproject.org/tpo/core/tor/-/issues/40811conflux_launch_leg infinite loop2023-07-05T21:32:13ZRoger Dingledineconflux_launch_leg infinite loopI finally got a proper core from the seg fault that my tor has been hitting periodically.
The seg fault seems to happen because my stack has thousands of entries on it, presumably because we are calling functions that call themselves in...I finally got a proper core from the seg fault that my tor has been hitting periodically.
The seg fault seems to happen because my stack has thousands of entries on it, presumably because we are calling functions that call themselves in a circle and it keeps stacking deeper.
It happens in practice when my Tor is minding its own business (not actively being used) but then my wifi goes away.
Here is a sample of the 'where' output from gdb
```
#69 0x000055a2356ef88a in circuit_establish_circuit_conflux (
conflux_nonce=conflux_nonce@entry=0x7ffc342cc320 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,M\320\323\325<\242U",
purpose=purpose@entry=25 '\031', exit_ei=exit_ei@entry=0x55a236878cd0,
flags=flags@entry=70) at src/core/or/circuitbuild.c:547
#70 0x000055a23571aae7 in conflux_launch_leg (
nonce=nonce@entry=0x7ffc342cc320 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,M\320\323\325<\242U")
at src/core/or/conflux_pool.c:1110
#71 0x000055a23571bcb7 in unlinked_circuit_closed (circ=0x55a23cd5d3d0)
at src/core/or/conflux_pool.c:1426
#72 conflux_circuit_has_closed (circ=circ@entry=0x55a23cd5d3d0)
at src/core/or/conflux_pool.c:1632
#73 0x000055a2356f6875 in circuit_mark_for_close_ (circ=0x55a23cd5d3d0,
reason=0, line=line@entry=547,
file=file@entry=0x55a23582f102 "src/core/or/circuitbuild.c")
at src/core/or/circuitlist.c:2262
#74 0x000055a2356ef88a in circuit_establish_circuit_conflux (
conflux_nonce=conflux_nonce@entry=0x7ffc342cc450 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,MP\305\325<\242U",
purpose=purpose@entry=25 '\031', exit_ei=exit_ei@entry=0x55a236878cd0,
flags=flags@entry=70) at src/core/or/circuitbuild.c:547
#75 0x000055a23571aae7 in conflux_launch_leg (
nonce=nonce@entry=0x7ffc342cc450 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,MP\305\325<\242U")
at src/core/or/conflux_pool.c:1110
#76 0x000055a23571bcb7 in unlinked_circuit_closed (circ=0x55a23cd5c550)
at src/core/or/conflux_pool.c:1426
#77 conflux_circuit_has_closed (circ=circ@entry=0x55a23cd5c550)
at src/core/or/conflux_pool.c:1632
#78 0x000055a2356f6875 in circuit_mark_for_close_ (circ=0x55a23cd5c550,
reason=0, line=line@entry=547,
file=file@entry=0x55a23582f102 "src/core/or/circuitbuild.c")
at src/core/or/circuitlist.c:2262
#79 0x000055a2356ef88a in circuit_establish_circuit_conflux (
conflux_nonce=conflux_nonce@entry=0x7ffc342cc580 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,Mж\325<\242U",
purpose=purpose@entry=25 '\031', exit_ei=exit_ei@entry=0x55a236878cd0,
flags=flags@entry=70) at src/core/or/circuitbuild.c:547
#80 0x000055a23571aae7 in conflux_launch_leg (
nonce=nonce@entry=0x7ffc342cc580 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,Mж\325<\242U")
at src/core/or/conflux_pool.c:1110
#81 0x000055a23571bcb7 in unlinked_circuit_closed (circ=0x55a23cd5b6d0)
at src/core/or/conflux_pool.c:1426
#82 conflux_circuit_has_closed (circ=circ@entry=0x55a23cd5b6d0)
at src/core/or/conflux_pool.c:1632
#83 0x000055a2356f6875 in circuit_mark_for_close_ (circ=0x55a23cd5b6d0,
reason=0, line=line@entry=547,
file=file@entry=0x55a23582f102 "src/core/or/circuitbuild.c")
at src/core/or/circuitlist.c:2262
#84 0x000055a2356ef88a in circuit_establish_circuit_conflux (
conflux_nonce=conflux_nonce@entry=0x7ffc342cc6b0 "\215Oĩaa8\307R\325\035\344C\304_2\020\205\354\347&O\213\221\300D\251\301g\343,MP\250\325<\242U",
purpose=purpose@entry=25 '\031', exit_ei=exit_ei@entry=0x55a236878cd0,
flags=flags@entry=70) at src/core/or/circuitbuild.c:547
```
I still have the core, but my internet for the next days is pretty crappy so I will try to respond as I can. :)
This is Tor running from git commit d5306e107f. I can't easily trigger it, or I would try a git bisect. It's been happening since before the Tor 0.4.8.1-alpha release. I am just a client.Tor: 0.4.8.x-stableMike PerryMike Perryhttps://gitlab.torproject.org/tpo/network-health/metrics/descriptorParser/-/issues/40Bug with how intervals are being calculated2023-06-22T06:30:09ZHiroBug with how intervals are being calculatedI found a bug regarding intervals being negative and producing negative bandwidth values.I found a bug regarding intervals being negative and producing negative bandwidth values.HiroHiro