cmd/go: make -coverpkg properly ignore special directories #66171

matthewhughes934 · 2024-03-07T20:06:31Z

This change fixes "go test -coverpkg" to properly ignore
special directories that are typically ignored by the "go" command
for example directories beginnning with "." or "_" or "testdata"

Fixes #66038

gopherbot · 2024-03-07T20:16:34Z

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

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

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-03-07T20:23:12Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-03-07T20:23:13Z

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/569895.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-03-07T20:36:23Z

Message from Than McIntosh:

Patch Set 1:

(4 comments)

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

gopherbot · 2024-03-07T20:36:24Z

Message from Than McIntosh:

Patch Set 1: Commit-Queue+1

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

gopherbot · 2024-03-07T20:42:53Z

Message from Go LUCI:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-03-07T20:26:10Z","revision":"d5dac6a21a14a19b1eb45dfacf35bdc8488894bc"}

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

gopherbot · 2024-03-07T20:42:54Z

Message from Than McIntosh:

Patch Set 1: -Commit-Queue

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

gopherbot · 2024-03-07T20:42:54Z

Message from Go LUCI:

Patch Set 1:

This CL has failed the run. Reason:

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

FAILURE

go on master (change 569895)
tools on master (commit b3a5e0b)

Error:
failed to run "test golang.org/x/tools module": exit status 1
failed to run "test golang.org/x/tools/gopls module": exit status 1

Links:

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

gopherbot · 2024-03-07T20:42:55Z

Message from Go LUCI:

Patch Set 1: LUCI-TryBot-Result-1

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

gopherbot · 2024-03-07T21:03:16Z

Message from Matthew Hughes:

Patch Set 1:

(4 comments)

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

gopherbot · 2024-03-07T21:03:17Z

Message from Matthew Hughes:

Patch Set 2:

(1 comment)

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

gopherbot · 2024-03-07T21:03:24Z

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

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

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-03-07T21:09:59Z

Message from Than McIntosh:

Patch Set 2: Commit-Queue+1

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

gopherbot · 2024-03-07T21:10:00Z

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-03-07T20:57:14Z","revision":"88466b937d61663e96ed462c4b285d1f36287a49"}

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

gopherbot · 2024-03-07T21:10:00Z

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result-1

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

gopherbot · 2024-03-08T14:33:14Z

Message from Than McIntosh:

Patch Set 3:

(2 comments)

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

gopherbot · 2024-03-08T15:01:00Z

Message from Emmanuel Odeke:

Patch Set 3: Hold+1

(4 comments)

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

gopherbot · 2024-03-08T21:27:53Z

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

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

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-03-19T18:51:50Z

Message from Matthew Hughes:

Patch Set 4:

(5 comments)

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

gopherbot · 2024-03-19T19:11:06Z

Message from Emmanuel Odeke:

Patch Set 4: -Hold Code-Review+1 Commit-Queue+1 Run-TryBot+1

(3 comments)

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

gopherbot · 2024-03-19T19:11:06Z

Message from Go LUCI:

Patch Set 4:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-03-19T18:58:12Z","revision":"4f35b335166bbf175ec73f9b1b1f0e54251f0fd9"}

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

gopherbot · 2024-03-19T19:11:07Z

Message from Gopher Robot:

Patch Set 4:

(1 comment)

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

gopherbot · 2024-03-19T19:17:34Z

Message from Matthew Hughes:

Patch Set 4:

(2 comments)

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

gopherbot · 2024-03-19T19:17:43Z

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

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

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-03-19T19:24:17Z

Message from Gopher Robot:

Patch Set 4:

(1 comment)

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

gopherbot · 2024-03-19T19:24:17Z

Message from Gopher Robot:

Patch Set 4: TryBot-Result-1

(1 comment)

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

gopherbot · 2024-03-24T23:19:36Z

Message from Matthew Hughes:

Patch Set 6:

(1 comment)

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

gopherbot · 2024-03-24T23:31:05Z

Message from Emmanuel Odeke:

Patch Set 7: Code-Review+1 Commit-Queue+1 Run-TryBot+1

(1 comment)

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

gopherbot · 2024-03-24T23:31:06Z

Message from Go LUCI:

Patch Set 7:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-03-24T23:24:53Z","revision":"64b6014edf67e7c3c4e19511f628a30f5a17298e"}

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

gopherbot · 2024-03-24T23:31:06Z

Message from Gopher Robot:

Patch Set 7:

(1 comment)

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

gopherbot · 2024-03-24T23:48:25Z

Message from Emmanuel Odeke:

Patch Set 7: -Commit-Queue

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

gopherbot · 2024-03-24T23:48:25Z

Message from Go LUCI:

Patch Set 7:

This CL has failed the run. Reason:

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

FAILURE

go on master (change 569895)

Tests failed. See all test results.

Error:
shard 1: failed to run "go tool dist test -json": exit status 1

Links:

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

gopherbot · 2024-03-24T23:48:26Z

Message from Gopher Robot:

Patch Set 7: TryBot-Result+1

(1 comment)

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

gopherbot · 2024-03-24T23:54:14Z

Message from Go LUCI:

Patch Set 7: LUCI-TryBot-Result-1

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

gopherbot · 2024-03-25T15:54:46Z

Message from Michael Matloob:

Patch Set 7:

(1 comment)

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

gopherbot · 2024-04-10T21:00:59Z

Message from Matthew Hughes:

Patch Set 7:

(1 comment)

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

gopherbot · 2024-04-11T19:13:00Z

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

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

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-04-11T19:19:25Z

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

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

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-04-11T19:44:14Z

Message from Matthew Hughes:

Patch Set 9:

(1 comment)

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

gopherbot · 2024-04-15T12:58:57Z

Message from Than McIntosh:

Patch Set 9: Commit-Queue+1

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

gopherbot · 2024-04-15T12:58:58Z

Message from Go LUCI:

Patch Set 9:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-04-15T12:49:58Z","revision":"dfc007b2baa838f2713d400bc183480a81b2d778"}

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

gopherbot · 2024-04-15T13:19:35Z

Message from Than McIntosh:

Patch Set 9: -Commit-Queue

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

gopherbot · 2024-04-15T13:19:36Z

Message from Go LUCI:

Patch Set 9:

This CL has passed the run

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

gopherbot · 2024-04-15T13:19:36Z

Message from Go LUCI:

Patch Set 9: LUCI-TryBot-Result+1

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

gopherbot · 2024-05-28T17:40:09Z

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

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

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-07-14T19:50:27Z

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

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

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-07-14T20:49:09Z

Message from Funda Secgin:

Patch Set 11: Code-Review+1

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

gopherbot · 2024-07-22T20:06:05Z

Message from Funda Secgin:

Patch Set 11:

(2 comments)

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

The pattern passed to `-coverpkg` when running `go test` would not ignore directories usually ignored by the `go` command, i.e. those beginning with "." or "_" are ignored by the go tool, as are directories named "testdata". Fix this by adding an explicit check for these (by following a similar check in `src/cmd/doc/dirs.go`[1]) allowing us to ignore them. The scope of the change is limted to package matching to only the -coverpkg flag of `go test` to avoid impacting -gcflags and the other per package flags, e.g. we don't want to change behaviour for a user building something that imports a leading dot package who wants to set gcflags for it See linked issue for a reproduction. Fixes golang#66038 [1] https://go.googlesource.com/go/+/16e5d24480dca7ddcbdffb78a8ed5de3e5155dec/src/cmd/doc/dirs.go#136

gopherbot · 2025-04-09T20:04:37Z

Message from Matthew Hughes:

Patch Set 11:

(1 comment)

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

gopherbot · 2025-04-09T20:04:50Z

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

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

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.

matthewhughes934 mentioned this pull request Mar 7, 2024

cmd/go: coverpkg doesn't ignore directories starting with '.' #66038

Open

matthewhughes934 force-pushed the fix-coverpkg-not-ignoring-special-directories branch from 63eb9f4 to 9396509 Compare March 7, 2024 20:50

matthewhughes934 changed the title ~~cmd/go: fix -coverpkg not ignoring special directories~~ cmd/go: make -coverpkg properly ignore special directories Mar 8, 2024

matthewhughes934 force-pushed the fix-coverpkg-not-ignoring-special-directories branch from 4ba4bea to 7093c8e Compare March 19, 2024 19:16

matthewhughes934 force-pushed the fix-coverpkg-not-ignoring-special-directories branch from 29c8bd9 to 84888c7 Compare April 11, 2024 19:11

matthewhughes934 force-pushed the fix-coverpkg-not-ignoring-special-directories branch from 84888c7 to 09944b0 Compare April 11, 2024 19:15

matthewhughes934 force-pushed the fix-coverpkg-not-ignoring-special-directories branch from 09944b0 to f48bd17 Compare May 28, 2024 17:34

matthewhughes934 force-pushed the fix-coverpkg-not-ignoring-special-directories branch from f48bd17 to 1c0d215 Compare July 14, 2024 19:45

matthewhughes934 force-pushed the fix-coverpkg-not-ignoring-special-directories branch from 1c0d215 to c541b18 Compare April 9, 2025 19:58

cmd/go: make -coverpkg properly ignore special directories #66171

Are you sure you want to change the base?

cmd/go: make -coverpkg properly ignore special directories #66171

Conversation

matthewhughes934 commented Mar 7, 2024 • edited Loading

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 7, 2024

gopherbot commented Mar 8, 2024

gopherbot commented Mar 8, 2024

gopherbot commented Mar 8, 2024

gopherbot commented Mar 19, 2024

gopherbot commented Mar 19, 2024

gopherbot commented Mar 19, 2024

gopherbot commented Mar 19, 2024

gopherbot commented Mar 19, 2024

gopherbot commented Mar 19, 2024

gopherbot commented Mar 19, 2024

gopherbot commented Mar 19, 2024

gopherbot commented Mar 24, 2024

gopherbot commented Mar 24, 2024

gopherbot commented Mar 24, 2024

gopherbot commented Mar 24, 2024

gopherbot commented Mar 24, 2024

gopherbot commented Mar 24, 2024

gopherbot commented Mar 24, 2024

gopherbot commented Mar 24, 2024

gopherbot commented Mar 25, 2024

gopherbot commented Apr 10, 2024

gopherbot commented Apr 11, 2024

gopherbot commented Apr 11, 2024

gopherbot commented Apr 11, 2024

gopherbot commented Apr 15, 2024

gopherbot commented Apr 15, 2024

gopherbot commented Apr 15, 2024

gopherbot commented Apr 15, 2024

gopherbot commented Apr 15, 2024

gopherbot commented May 28, 2024

gopherbot commented Jul 14, 2024

gopherbot commented Jul 14, 2024

gopherbot commented Jul 22, 2024

gopherbot commented Apr 9, 2025

gopherbot commented Apr 9, 2025

matthewhughes934 commented Mar 7, 2024 •

edited

Loading