route: fix address parsing of messages on Darwin #220

hurricanehrndz · 2024-08-29T19:37:35Z

sizeofSockaddrInet is 16, but first byte of sockaddr specifies actual
size of sockaddr.

Although, 16 works for most cases, it fails for Netmasks addresses. On
Darwin only the significant bits of the netmask are in the msg.

Take this route message as an example

// rt_msg_hdr
88 00 05 01 00 00 00 00
41 08 00 00 07 00 00 00
92 7b 00 00 01 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00

// metrics
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00

// SOCKADDRS - DST  (100.113.0.0)
10 02 00 00 64 71 00 00
00 00 00 00 00 00 00 00

// GW  utun4319
14 12 21 00 01 08 00 00
75 74 75 6e 34 33 31 39
00 00 00 00

// NETMASK 255.255.0.0
06 02 00 00 ff ff

// NULL
00 00

i.e. ipv4

06 02 00 00 ff ff

The above byte sequence is for a sockaddr that is 6 bytes long
representing an ipv4 for address that is 255.255.0.0.

i.e. ipv6 netmask

0e 1e 00 00 00 00 00 00 ff ff ff ff ff ff 00 00

The above is /48 netmask that should also be parsed using b[0] of the
sockaddr that contains the length.

Confirmed by using route monitor.

sources:
https://github.com/apple/darwin-xnu/blob/main/bsd/net/route.h
https://github.com/apple/darwin-xnu/blob/main/bsd/sys/socket.h#L603

Fixes golang/go#44740

gopherbot · 2024-08-29T19:47:04Z

This PR (HEAD: 04c61e3) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/net/+/609577.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-29T19:54:18Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-29T19:54:18Z

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://go.dev/s/release
for more details.

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-29T20:01:12Z

Message from Ian Lance Taylor:

Patch Set 1:

(4 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-03T19:40:36Z

Message from Carlos Hernandez:

Patch Set 1:

(4 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-04T22:31:49Z

This PR (HEAD: 38e2e94) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/net/+/609577.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-04T22:38:38Z

Message from Carlos Hernandez:

Patch Set 1:

(4 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-04T22:45:16Z

Message from Ian Lance Taylor:

Patch Set 2: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-04T22:45:20Z

This PR (HEAD: af83adb) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/net/+/609577.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-04T22:51:48Z

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-04T22:37:34Z","revision":"88bd07d0a1f4211495b6cbdbe45b8b1cfe16e46c"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-04T22:51:48Z

Message from Ian Lance Taylor:

Patch Set 2: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-04T22:51:49Z

Message from Go LUCI:

Patch Set 2:

This CL has failed the run. Reason:

Tryjob golang/try/x_net-gotip-linux-arm64 has failed with summary (view all results):

go on master (commit a2891ae)
net on master (change 609577)

Build or test failure, click here for results.

To reproduce, try gomote repro 8737686880807786401.

Additional links for debugging:

Output for test golang.org/x/net module

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-04T22:51:49Z

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-04T22:58:14Z

Message from Brad Fitzpatrick:

Patch Set 2:

(4 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-04T22:58:14Z

Message from Brad Fitzpatrick:

Patch Set 3:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-05T20:38:58Z

This PR (HEAD: 9f85924) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/net/+/609577.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-05T20:45:40Z

Message from Carlos Hernandez:

Patch Set 3:

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-05T21:20:22Z

Message from Ian Lance Taylor:

Patch Set 4: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-05T21:20:22Z

Message from Go LUCI:

Patch Set 4:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-05T21:10:29Z","revision":"094d0537c7b3bd91237b7cc72f7b4e645827ec12"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-05T21:20:23Z

Message from Ian Lance Taylor:

Patch Set 4: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-05T21:20:24Z

Message from Go LUCI:

Patch Set 4:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-05T21:20:24Z

Message from Go LUCI:

Patch Set 4: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-05T21:27:07Z

Message from Ian Lance Taylor:

Patch Set 4:

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-05T21:53:55Z

This PR (HEAD: 614ebc1) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/net/+/609577.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-05T22:00:50Z

This PR (HEAD: 2fa5526) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/net/+/609577.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

sizeofSockaddrInet is 16, but first byte of sockaddr specifies actual size of sockaddr. Although, 16 works for most cases, it fails for Netmasks addresses. On Darwin only the significant bits of the netmask are in the msg. Take this route message as an example ``` // rt_msg_hdr 88 00 05 01 00 00 00 00 41 08 00 00 07 00 00 00 92 7b 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 // metrics 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 // SOCKADDRS - DST (100.113.0.0) 10 02 00 00 64 71 00 00 00 00 00 00 00 00 00 00 // GW utun4319 14 12 21 00 01 08 00 00 75 74 75 6e 34 33 31 39 00 00 00 00 // NETMASK 255.255.0.0 06 02 00 00 ff ff // NULL 00 00 ``` i.e. ipv4 ``` 06 02 00 00 ff ff ``` The above byte sequence is for a sockaddr that is 6 bytes long representing an ipv4 for address that is 255.255.0.0. i.e. ipv6 netmask ``` 0e 1e 00 00 00 00 00 00 ff ff ff ff ff ff 00 00 ``` The above is `/48` netmask that should also be parsed using `b[0]` of the sockaddr that contains the length. Confirmed by using `route monitor`. Fixes golang/go#44740 sources: https://github.com/apple/darwin-xnu/blob/main/bsd/net/route.h https://github.com/apple/darwin-xnu/blob/main/bsd/sys/socket.h#L603

gopherbot · 2024-09-05T22:28:21Z

This PR (HEAD: f7b9253) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/net/+/609577.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-06T16:00:05Z

Message from Carlos Hernandez:

Patch Set 10:

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-06T18:06:26Z

Message from Ian Lance Taylor:

Patch Set 10:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-06T18:06:27Z

Message from Ian Lance Taylor:

Patch Set 10: Auto-Submit+1 Code-Review+2 Commit-Queue+1

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-06T18:06:27Z

Message from Go LUCI:

Patch Set 10:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-06T17:56:22Z","revision":"1a5ca0ed7214537e1210590e29051351ac0e673c"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-06T18:13:12Z

Message from Ian Lance Taylor:

Patch Set 10: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-06T18:13:13Z

Message from Go LUCI:

Patch Set 10:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-06T18:13:14Z

Message from Go LUCI:

Patch Set 10: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609577.
After addressing review feedback, remember to publish your drafts!

sizeofSockaddrInet is 16, but first byte of sockaddr specifies actual size of sockaddr. Although, 16 works for most cases, it fails for Netmasks addresses. On Darwin only the significant bits of the netmask are in the msg. Take this route message as an example ``` // rt_msg_hdr 88 00 05 01 00 00 00 00 41 08 00 00 07 00 00 00 92 7b 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 // metrics 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 // SOCKADDRS - DST (100.113.0.0) 10 02 00 00 64 71 00 00 00 00 00 00 00 00 00 00 // GW utun4319 14 12 21 00 01 08 00 00 75 74 75 6e 34 33 31 39 00 00 00 00 // NETMASK 255.255.0.0 06 02 00 00 ff ff // NULL 00 00 ``` i.e. ipv4 ``` 06 02 00 00 ff ff ``` The above byte sequence is for a sockaddr that is 6 bytes long representing an ipv4 for address that is 255.255.0.0. i.e. ipv6 netmask ``` 0e 1e 00 00 00 00 00 00 ff ff ff ff ff ff 00 00 ``` The above is `/48` netmask that should also be parsed using `b[0]` of the sockaddr that contains the length. Confirmed by using `route monitor`. sources: https://github.com/apple/darwin-xnu/blob/main/bsd/net/route.h https://github.com/apple/darwin-xnu/blob/main/bsd/sys/socket.h#L603 Fixes golang/go#44740 Change-Id: I8153130d02d0a5e547fbf60a85762d3889e1d08c GitHub-Last-Rev: f7b9253 GitHub-Pull-Request: #220 Reviewed-on: https://go-review.googlesource.com/c/net/+/609577 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Ian Lance Taylor <iant@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com>

gopherbot · 2024-09-06T18:33:23Z

This PR is being closed because golang.org/cl/609577 has been merged.

hurricanehrndz force-pushed the fix_af_route_inetadd_parsing branch from 04c61e3 to 38e2e94 Compare September 4, 2024 22:26

hurricanehrndz force-pushed the fix_af_route_inetadd_parsing branch from 38e2e94 to af83adb Compare September 4, 2024 22:42

hurricanehrndz force-pushed the fix_af_route_inetadd_parsing branch from af83adb to 9f85924 Compare September 5, 2024 20:35

hurricanehrndz force-pushed the fix_af_route_inetadd_parsing branch from 9f85924 to 614ebc1 Compare September 5, 2024 21:49

hurricanehrndz force-pushed the fix_af_route_inetadd_parsing branch 2 times, most recently from 65ec374 to 2fa5526 Compare September 5, 2024 21:56

hurricanehrndz added 2 commits September 5, 2024 16:13

route: Test trimmed netmask parsing on Darwin

f7b9253

hurricanehrndz force-pushed the fix_af_route_inetadd_parsing branch from 2fa5526 to f7b9253 Compare September 5, 2024 22:26

hurricanehrndz changed the title ~~On Darwin Fix address parsing of route msgs~~ route: fix address parsing of messages on Darwin Sep 6, 2024

gopherbot closed this Sep 6, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

route: fix address parsing of messages on Darwin #220

route: fix address parsing of messages on Darwin #220

hurricanehrndz commented Aug 29, 2024 •

edited

Loading

gopherbot commented Aug 29, 2024

gopherbot commented Aug 29, 2024

gopherbot commented Aug 29, 2024

gopherbot commented Aug 29, 2024

gopherbot commented Sep 3, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

route: fix address parsing of messages on Darwin #220

route: fix address parsing of messages on Darwin #220

Conversation

hurricanehrndz commented Aug 29, 2024 • edited Loading

gopherbot commented Aug 29, 2024

gopherbot commented Aug 29, 2024

gopherbot commented Aug 29, 2024

gopherbot commented Aug 29, 2024

gopherbot commented Sep 3, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 4, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

hurricanehrndz commented Aug 29, 2024 •

edited

Loading