gopls/internal/undeclaredname: add missing colon when appropriate #545

xzbdmw · 2024-11-20T07:42:46Z

This CL improves the undeclared-variable quick fix
by adding the missing colon when appropriate, that is:

When the first occurrence of undefined ident's parent within
function is an AssignStmt, and it sits in the left hand side;
Its Tok is set to token.ASSIGN (=);
Ident must not be self assignment.

Prior to this CL:

the new generated one simply sits above
the cursor position, while this CL insert it before the first
undefined ident with the same name.
It results in a syntax error, as stated in https://go-review.googlesource.com/c/tools/+/623156/comment/09944936_9d2835c2/,
so this CL also adds a default value derived from its type.

Fixes golang/go#69980

gopherbot · 2024-11-20T07:55:53Z

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

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

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-11-20T08:03:40Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-11-20T08:03:44Z

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

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

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-11-20T08:19:37Z

Message from xxx Lulu:

Patch Set 2:

(2 comments)

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

gopherbot · 2024-11-20T08:19:38Z

Message from xxx Lulu:

Patch Set 2:

(1 comment)

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

gopherbot · 2024-11-21T10:15:35Z

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

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

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-11-21T10:23:54Z

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

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

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-11-21T16:19:26Z

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

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

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-11-21T16:28:09Z

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

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

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-11-21T18:22:53Z

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

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

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-11-22T07:26:13Z

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

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

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-11-22T18:14:52Z

Message from Robert Findley:

Patch Set 9:

(10 comments)

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

gopherbot · 2024-11-22T18:50:41Z

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

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

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-11-22T19:06:06Z

Message from xxx Lulu:

Patch Set 10:

(8 comments)

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

gopherbot · 2024-11-27T01:05:31Z

Message from Robert Findley:

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

(2 comments)

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

gopherbot · 2024-11-27T01:05:31Z

Message from Go LUCI:

Patch Set 10:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-11-27T00:51:17Z","revision":"a25811c8b3a69970453aef84b1d582430bb88ea4"}

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

gopherbot · 2024-11-27T01:05:32Z

Message from Robert Findley:

Patch Set 10: -Commit-Queue

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

gopherbot · 2024-11-27T01:05:32Z

Message from Go LUCI:

Patch Set 10:

This CL has failed the run. Reason:

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

go on master (commit eab49f6)
tools on master (change 629895)

Build or test failure, click here for results.

To reproduce, try gomote repro 8730158920409970049.

Additional links for debugging:

Output for test golang.org/x/tools/gopls module

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

gopherbot · 2024-11-27T01:05:33Z

Message from Go LUCI:

Patch Set 10: LUCI-TryBot-Result-1

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

gopherbot · 2024-11-27T01:05:33Z

Message from Robert Findley:

Patch Set 10:

(1 comment)

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

gopherbot · 2024-11-27T02:08:07Z

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

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

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-11-27T02:22:35Z

Message from xxx Lulu:

Patch Set 11:

(1 comment)

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

gopherbot · 2024-11-27T02:22:35Z

Message from xxx Lulu:

Patch Set 12:

(1 comment)

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

gopherbot · 2024-11-27T02:29:45Z

Message from xxx Lulu:

Patch Set 12:

(1 comment)

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

gopherbot · 2024-11-27T13:36:27Z

Message from Robert Findley:

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

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

gopherbot · 2024-11-27T13:44:12Z

Message from Go LUCI:

Patch Set 12:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-11-27T13:29:23Z","revision":"7a4d9261161bb05001aa311e2fbf837d01a97c31"}

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

gopherbot · 2024-11-27T14:00:40Z

Message from Robert Findley:

Patch Set 12: -Commit-Queue

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

gopherbot · 2024-11-27T14:00:41Z

Message from Go LUCI:

Patch Set 12:

This CL has passed the run

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

gopherbot · 2024-11-27T14:00:41Z

Message from Go LUCI:

Patch Set 12: LUCI-TryBot-Result+1

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

gopherbot · 2024-11-27T15:44:41Z

Message from Veronica Silina:

Patch Set 12:

(1 comment)

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

gopherbot · 2024-11-27T15:53:42Z

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

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

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-11-27T16:03:52Z

Message from xxx Lulu:

Patch Set 12:

(1 comment)

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

gopherbot · 2024-11-27T16:03:53Z

Message from xxx Lulu:

Patch Set 12:

(1 comment)

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

gopherbot · 2024-11-27T16:03:58Z

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

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

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-11-27T16:12:39Z

Message from Robert Findley:

Patch Set 13: Code-Review+2 Commit-Queue+1

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

gopherbot · 2024-11-27T16:12:39Z

Message from Go LUCI:

Patch Set 13:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-11-27T15:54:25Z","revision":"0f34dbddca5ed2118559a3ad4d5a610f05f2d406"}

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

gopherbot · 2024-11-27T16:12:40Z

Message from Go LUCI:

Patch Set 13: LUCI-TryBot-Result-1

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

gopherbot · 2024-11-27T16:21:21Z

Message from Robert Findley:

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

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

gopherbot · 2024-11-27T16:21:22Z

Message from Go LUCI:

Patch Set 14:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-11-27T16:04:54Z","revision":"e07482eab0be7223c4b2189f2c5a1c8d9ac0c0f0"}

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

gopherbot · 2024-11-27T16:39:48Z

Message from Robert Findley:

Patch Set 14: -Commit-Queue

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

gopherbot · 2024-11-27T16:39:48Z

Message from Go LUCI:

Patch Set 14:

This CL has passed the run

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

gopherbot · 2024-11-27T16:39:49Z

Message from Go LUCI:

Patch Set 14: LUCI-TryBot-Result+1

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

This CL improves the undeclared-variable quick fix by adding the missing colon when appropriate, that is: 1) When the first occurrence of undefined ident's parent within function is an AssignStmt, and it sits in the left hand side; 2) Its Tok is set to token.ASSIGN (=); 3) Ident must not be self assignment. Prior to this CL: 1) the new generated one simply sits above the cursor position, while this CL insert it before the first undefined ident with the same name. 2) It results in a syntax error, as stated in https://go-review.googlesource.com/c/tools/+/623156/comment/09944936_9d2835c2/, so this CL also adds a default value derived from its type. Fixes golang/go#69980 Change-Id: I4ccad852f89bc60034ade856ad5b1490686fc1e8 GitHub-Last-Rev: 378bdfd GitHub-Pull-Request: #545 Reviewed-on: https://go-review.googlesource.com/c/tools/+/629895 Auto-Submit: Robert Findley <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Robert Findley <[email protected]> Reviewed-by: Veronica Silina <[email protected]>

gopherbot · 2024-11-27T19:02:14Z

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

xzbdmw force-pushed the col branch from 593ee32 to cfb4da6 Compare November 20, 2024 07:59

xzbdmw changed the title ~~gopls/internal/undeclaredname: CodeAction: Add missing colon when appropriate~~ gopls/internal/undeclaredname: add missing colon when appropriate Nov 20, 2024

xzbdmw force-pushed the col branch from cfb4da6 to e55a4db Compare November 21, 2024 10:14

xzbdmw force-pushed the col branch from e55a4db to 7fa8370 Compare November 21, 2024 10:21

xzbdmw force-pushed the col branch 2 times, most recently from baf803d to 6d673ec Compare November 21, 2024 16:16

xzbdmw force-pushed the col branch from 6d673ec to bf9874e Compare November 21, 2024 16:19

xzbdmw force-pushed the col branch from bf9874e to d79fe44 Compare November 21, 2024 18:16

xzbdmw force-pushed the col branch from d79fe44 to baf639f Compare November 22, 2024 07:21

xzbdmw force-pushed the col branch from baf639f to 977eb21 Compare November 22, 2024 18:49

xzbdmw force-pushed the col branch from 977eb21 to ee19f4d Compare November 27, 2024 02:07

xzbdmw force-pushed the col branch from ee19f4d to 5821588 Compare November 27, 2024 15:47

xzbdmw force-pushed the col branch from 5821588 to 2aaf0b4 Compare November 27, 2024 15:55

add missing column

378bdfd

xzbdmw force-pushed the col branch from 2aaf0b4 to 378bdfd Compare November 27, 2024 16:01

gopherbot closed this Nov 27, 2024

gopls/internal/undeclaredname: add missing colon when appropriate #545

gopls/internal/undeclaredname: add missing colon when appropriate #545

Conversation

xzbdmw commented Nov 20, 2024

gopherbot commented Nov 20, 2024

gopherbot commented Nov 20, 2024

gopherbot commented Nov 20, 2024

gopherbot commented Nov 20, 2024

gopherbot commented Nov 20, 2024

gopherbot commented Nov 21, 2024

gopherbot commented Nov 21, 2024

gopherbot commented Nov 21, 2024

gopherbot commented Nov 21, 2024

gopherbot commented Nov 21, 2024

gopherbot commented Nov 22, 2024

gopherbot commented Nov 22, 2024

gopherbot commented Nov 22, 2024

gopherbot commented Nov 22, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024

gopherbot commented Nov 27, 2024