go/types, types2: ensure deterministic output when reporting an init cycle #71264

wingrez · 2025-01-14T06:07:30Z

Fixes #71254

gopherbot · 2025-01-14T06:14:29Z

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

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

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 · 2025-01-14T06:22:40Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

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

gopherbot · 2025-01-14T06:30:50Z

Message from Shengwei Zhao:

Patch Set 1:

(1 comment)

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

gopherbot · 2025-01-14T06:30:57Z

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

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

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 · 2025-01-14T12:38:06Z

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

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

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 · 2025-01-14T14:19:13Z

Message from Robert Findley:

Patch Set 4:

(2 comments)

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

gopherbot · 2025-01-14T15:03:56Z

Message from Alan Donovan:

Patch Set 4:

(3 comments)

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

gopherbot · 2025-01-14T15:04:03Z

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

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

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 · 2025-01-14T15:30:03Z

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

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

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 · 2025-01-14T15:39:04Z

Message from Robert Findley:

Patch Set 6:

(1 comment)

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

gopherbot · 2025-01-14T15:56:22Z

Message from Shengwei Zhao:

Patch Set 6:

(4 comments)

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

gopherbot · 2025-01-14T15:56:30Z

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

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

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 · 2025-01-14T16:05:22Z

Message from Robert Findley:

Patch Set 6:

(1 comment)

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

gopherbot · 2025-01-14T16:05:22Z

Message from Shengwei Zhao:

Patch Set 7:

(1 comment)

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

gopherbot · 2025-01-14T16:30:55Z

Message from Mateusz Poliwczak:

Patch Set 7:

(1 comment)

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

gopherbot · 2025-01-14T16:47:56Z

Message from Shengwei Zhao:

Patch Set 7:

(1 comment)

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

gopherbot · 2025-01-14T17:04:37Z

Message from Mateusz Poliwczak:

Patch Set 7:

(1 comment)

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

gopherbot · 2025-01-14T17:13:04Z

Message from Robert Griesemer:

Patch Set 7:

(6 comments)

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

gopherbot · 2025-01-14T18:46:31Z

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

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

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 · 2025-01-14T19:05:16Z

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

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

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 · 2025-01-14T19:13:59Z

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

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

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 · 2025-01-14T19:48:30Z

Message from Robert Findley:

Patch Set 10:

(1 comment)

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

gopherbot · 2025-01-14T19:57:09Z

Message from Robert Griesemer:

Patch Set 10:

(4 comments)

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

gopherbot · 2025-01-15T00:43:01Z

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

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

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 · 2025-01-15T01:06:37Z

Message from Shengwei Zhao:

Patch Set 11:

(5 comments)

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

gopherbot · 2025-01-15T01:30:45Z

Message from Robert Griesemer:

Patch Set 11: Commit-Queue+1

(1 comment)

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

gopherbot · 2025-01-15T01:38:42Z

Message from Go LUCI:

Patch Set 11:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-01-15T01:21:11Z","revision":"d79a3c600e043636165d1191365be44a9311a297"}

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

gopherbot · 2025-01-15T01:38:43Z

Message from Robert Griesemer:

Patch Set 11: -Commit-Queue

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

gopherbot · 2025-01-15T01:38:43Z

Message from Go LUCI:

Patch Set 11:

This CL has failed the run. Reason:

Failed Tryjobs:

golang/try/gotip-linux-amd64. Summary (view all results):

go on master (change 642396)

Build or test failure, click here for results.

To reproduce, try gomote repro 8725717787426042769.

Additional links for debugging:

Output for go tool dist test -json [shard 1]

golang/try/gotip-linux-amd64-newinliner. Summary (view all results):

go on master (change 642396)

Build or test failure, click here for results.

To reproduce, try gomote repro 8725717787426042705.

Additional links for debugging:

Output for go tool dist test -json [shard 1]

golang/try/gotip-linux-amd64-typesalias. Summary (view all results):

go on master (change 642396)

Build or test failure, click here for results.

To reproduce, try gomote repro 8725717787426042673.

Additional links for debugging:

Output for go tool dist test -json [shard 1]

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

gopherbot · 2025-01-15T01:38:44Z

Message from Go LUCI:

Patch Set 11: LUCI-TryBot-Result-1

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

gopherbot · 2025-01-15T01:46:53Z

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

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

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 · 2025-01-15T01:55:08Z

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

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

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 · 2025-01-15T02:03:09Z

Message from Shengwei Zhao:

Patch Set 13:

(1 comment)

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

gopherbot · 2025-01-15T17:14:01Z

Message from Robert Griesemer:

Patch Set 13:

(2 comments)

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

gopherbot · 2025-01-16T00:25:20Z

Message from Shengwei Zhao:

Patch Set 13:

(1 comment)

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

gopherbot · 2025-01-16T15:22:07Z

Message from Shengwei Zhao:

Patch Set 13:

(1 comment)

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

gopherbot · 2025-01-16T20:57:55Z

Message from Robert Griesemer:

Patch Set 13:

(3 comments)

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

gopherbot · 2025-01-17T00:39:02Z

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

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

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 · 2025-01-17T01:00:58Z

Message from Shengwei Zhao:

Patch Set 14:

(2 comments)

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

gopherbot · 2025-01-17T01:10:05Z

Message from Shengwei Zhao:

Patch Set 14:

(1 comment)

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

gopherbot · 2025-01-17T16:09:15Z

Message from Robert Findley:

Patch Set 14: Code-Review+1

(1 comment)

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

gopherbot · 2025-01-17T16:09:16Z

Message from Robert Griesemer:

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

(1 comment)

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

gopherbot · 2025-01-17T16:09:16Z

Message from Go LUCI:

Patch Set 14:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-01-17T15:59:21Z","revision":"340a94e7ceb5fed23fedfadb765141ed41693031"}

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

…cycle Fixes #71254 Change-Id: Ie3bad281403c8ff6215e03d92760b9a378714cee GitHub-Last-Rev: 9b804a7 GitHub-Pull-Request: #71264 Reviewed-on: https://go-review.googlesource.com/c/go/+/642396 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Robert Griesemer <[email protected]> Reviewed-by: Robert Findley <[email protected]> Auto-Submit: Robert Griesemer <[email protected]>

…cycle Fixes #71254 Change-Id: Ie3bad281403c8ff6215e03d92760b9a378714cee GitHub-Last-Rev: 9b804a7842421dca6a97c57ce18523b593b0817d GitHub-Pull-Request: golang/go#71264 Reviewed-on: https://go-review.googlesource.com/c/go/+/642396 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Robert Griesemer <[email protected]> Reviewed-by: Robert Findley <[email protected]> Auto-Submit: Robert Griesemer <[email protected]>

wingrez force-pushed the master branch from c061e6f to 8c49d8f Compare January 14, 2025 12:31

wingrez force-pushed the master branch from 8c49d8f to f4404dc Compare January 14, 2025 14:55

wingrez changed the title ~~types2: ensure that the reportCycle has a deterministic output~~ go/types, types2: ensure that the reportCycle has a deterministic output Jan 14, 2025

wingrez force-pushed the master branch from f4404dc to eb16b9b Compare January 14, 2025 15:23

wingrez force-pushed the master branch from eb16b9b to 04de0fb Compare January 14, 2025 15:53

wingrez force-pushed the master branch from 04de0fb to 04617ea Compare January 14, 2025 18:45

wingrez changed the title ~~go/types, types2: ensure that the reportCycle has a deterministic output~~ go/types, types2: ensure deterministic output when reporting an init cycle Jan 14, 2025

wingrez force-pushed the master branch from 04617ea to 410967c Compare January 14, 2025 18:57

wingrez force-pushed the master branch from 410967c to efadb95 Compare January 14, 2025 19:07

wingrez force-pushed the master branch from efadb95 to ec630ca Compare January 15, 2025 00:38

wingrez force-pushed the master branch from ec630ca to 72d3374 Compare January 15, 2025 01:41

wingrez force-pushed the master branch from 72d3374 to 88622ef Compare January 15, 2025 01:50

wingrez force-pushed the master branch from 88622ef to 9b804a7 Compare January 17, 2025 00:36

wingrez closed this Jan 17, 2025

wingrez force-pushed the master branch from 9b804a7 to 87023bb Compare January 17, 2025 16:26

go/types, types2: ensure deterministic output when reporting an init cycle #71264

go/types, types2: ensure deterministic output when reporting an init cycle #71264

Uh oh!

Conversation

wingrez commented Jan 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 14, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 15, 2025

Uh oh!

gopherbot commented Jan 16, 2025

Uh oh!

gopherbot commented Jan 16, 2025

Uh oh!

gopherbot commented Jan 16, 2025

wingrez commented Jan 14, 2025 •

edited

Loading