gopls: report semantic tokens of top-level type constructor modifiers #511

xzbdmw · 2024-08-25T01:10:53Z

These new semantic type modifiers will be reported in places of type definition,
type embedding, type alias, variable definition, parameter type,
return type and comments link.

Fixes golang/go#68975

gopherbot · 2024-08-25T01:17:01Z

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

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

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-25T01:23:37Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-08-25T01:30:14Z

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.

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

gopherbot · 2024-08-25T01:37:01Z

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

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

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-25T02:35:49Z

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

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

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-25T02:42:21Z

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

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

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-25T03:18:21Z

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

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

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-25T03:38:38Z

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

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

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-25T03:45:20Z

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

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

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-25T04:47:15Z

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

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

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-27T20:23:20Z

Message from Alan Donovan:

Patch Set 9:

(11 comments)

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

gopherbot · 2024-08-28T09:19:26Z

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

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

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-28T09:40:13Z

Message from xxx Lulu:

Patch Set 10:

(12 comments)

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

gopherbot · 2024-08-28T15:06:49Z

Message from Alan Donovan:

Patch Set 10:

(5 comments)

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

gopherbot · 2024-08-28T15:28:44Z

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

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

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-28T15:42:52Z

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

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

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-28T15:50:03Z

Message from xxx Lulu:

Patch Set 10:

(3 comments)

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

gopherbot · 2024-08-28T15:57:01Z

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

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

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-28T17:34:02Z

Message from Go LUCI:

Patch Set 14: LUCI-TryBot-Result-1

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

gopherbot · 2024-08-28T17:34:03Z

Message from Robert Findley:

Patch Set 14:

(1 comment)

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

gopherbot · 2024-08-28T18:02:28Z

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

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

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-28T18:09:32Z

Message from xxx Lulu:

Patch Set 14:

(2 comments)

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

gopherbot · 2024-08-28T18:23:50Z

Message from xxx Lulu:

Patch Set 15:

(1 comment)

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

gopherbot · 2024-08-28T18:30:51Z

Message from Alan Donovan:

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

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

gopherbot · 2024-08-28T18:37:53Z

Message from Go LUCI:

Patch Set 15:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-08-28T18:21:16Z","revision":"4380b1531cbdab83d721b793de2df1eafe16aeee"}

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

gopherbot · 2024-08-28T18:37:54Z

Message from Alan Donovan:

Patch Set 15: -Commit-Queue

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

gopherbot · 2024-08-28T18:37:54Z

Message from Go LUCI:

Patch Set 15:

This CL has failed the run. Reason:

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

go on master (commit fe63d48)
tools on master (change 608156)

Build or test failure, click here for results.

To reproduce, try gomote repro 8738337180952240385.

Additional links for debugging:

Output for test golang.org/x/tools module

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

gopherbot · 2024-08-28T18:37:55Z

Message from Go LUCI:

Patch Set 15: LUCI-TryBot-Result-1

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

gopherbot · 2024-08-28T18:45:12Z

Message from Alan Donovan:

Patch Set 15: Commit-Queue+1

(1 comment)

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

gopherbot · 2024-08-28T18:45:13Z

Message from Go LUCI:

Patch Set 15:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-08-28T18:32:01Z","revision":"4380b1531cbdab83d721b793de2df1eafe16aeee"}

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

gopherbot · 2024-08-28T18:45:13Z

Message from Alan Donovan:

Patch Set 15: -Commit-Queue

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

gopherbot · 2024-08-28T18:45:14Z

Message from Go LUCI:

Patch Set 15:

This CL has failed the run. Reason:

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

go on master (commit fe63d48)
tools on master (change 608156)

Build or test failure, click here for results.

To reproduce, try gomote repro 8738336505872171905.

Additional links for debugging:

Output for test golang.org/x/tools module

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

… constructor of each symbol These new semantic type modifiers will report in type definition, type embedding, type alias, variable definition like `var foo Bar`'s `Bar', parameter type and return type

gopherbot · 2024-08-28T20:09:08Z

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

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

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-28T20:16:29Z

Message from xxx Lulu:

Patch Set 15:

(1 comment)

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

gopherbot · 2024-08-28T20:37:07Z

Message from Robert Findley:

Patch Set 16: Code-Review+1 Commit-Queue+1

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

gopherbot · 2024-08-28T20:37:07Z

Message from Go LUCI:

Patch Set 16:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-08-28T20:25:38Z","revision":"2aa017935c1d1c9e910d1e5d01caa142cc47285c"}

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

These new semantic type modifiers will be reported in places of type definition, type embedding, type alias, variable definition, parameter type, return type and comments link. Fixes golang/go#68975 Change-Id: I21ebd758351ee4c6e7bd7a0d34a093b3a6ad4ac8 GitHub-Last-Rev: f825f8a GitHub-Pull-Request: #511 Reviewed-on: https://go-review.googlesource.com/c/tools/+/608156 Reviewed-by: Alan Donovan <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Robert Findley <[email protected]> Auto-Submit: Robert Findley <[email protected]>

gopherbot · 2024-08-28T20:57:30Z

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

xzbdmw changed the title ~~gopls: semantic tokens should report modifiers for the top-level type…~~ gopls: report semantic tokens of top-level type constructor modifiers Aug 25, 2024

xzbdmw force-pushed the semantic branch from 648bb1e to afd37c8 Compare August 25, 2024 01:36

xzbdmw force-pushed the semantic branch from afd37c8 to 174ba9f Compare August 25, 2024 02:31

xzbdmw force-pushed the semantic branch from 174ba9f to f457334 Compare August 25, 2024 02:39

xzbdmw force-pushed the semantic branch from f457334 to 0ef01b9 Compare August 25, 2024 03:12

xzbdmw force-pushed the semantic branch 2 times, most recently from 9d811e9 to b37e520 Compare August 25, 2024 03:38

xzbdmw force-pushed the semantic branch from b37e520 to 33b1585 Compare August 25, 2024 03:38

xzbdmw force-pushed the semantic branch 2 times, most recently from 0e1e842 to 01c46c0 Compare August 25, 2024 04:42

xzbdmw force-pushed the semantic branch 2 times, most recently from dbb42a8 to 302c11d Compare August 28, 2024 15:53

xzbdmw added 8 commits August 29, 2024 04:01

gopls: semantic tokens should report modifiers for the top-level type…

d424795

… constructor of each symbol These new semantic type modifiers will report in type definition, type embedding, type alias, variable definition like `var foo Bar`'s `Bar', parameter type and return type

release and internal documentation change

346466e

change signature from underlineType to appendTypeModifiers

42b8bd1

simplify number type check

f4c9855

(document) add Oxford comma and drop count

0cb1da4

(document) add features/passive.md

77e897a

fixup! (document) add features/passive.md

9386ba5

update new test

f825f8a

xzbdmw force-pushed the semantic branch from 8bde036 to f825f8a Compare August 28, 2024 20:03

gopherbot closed this Aug 28, 2024

gopls: report semantic tokens of top-level type constructor modifiers #511

gopls: report semantic tokens of top-level type constructor modifiers #511

Conversation

xzbdmw commented Aug 25, 2024 • edited Loading

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 25, 2024

gopherbot commented Aug 27, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

gopherbot commented Aug 28, 2024

xzbdmw commented Aug 25, 2024 •

edited

Loading