runtime: use futexes with 64-bit time on Linux #75306

orangecms · 2025-09-08T00:23:17Z

Linux introduced new syscalls to fix the year 2038 issue.
To still be able to use the old ones, the Kconfig option
COMPAT_32BIT_TIME would be necessary.

Use the new syscall with 64-bit values for futex by default.
Define _ENOSYS for detecting if it's not available.
Add a fallback to use the older syscall in case the new one is
not available, since Go runs on Linux from 2.6.32 on, per
https://go.dev/wiki/MinimumRequirements.

Updates #75133

gopherbot · 2025-09-08T00:27:29Z

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

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

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-09-08T00:35:02Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

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

gopherbot · 2025-09-08T00:42:33Z

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

gopherbot · 2025-09-08T01:12:17Z

Message from Jorropo:

Patch Set 1: Commit-Queue+1

(5 comments)

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

gopherbot · 2025-09-08T01:12:17Z

Message from Go LUCI:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-08T01:01:27Z","revision":"f2e24150d377c634503bc9f7e5f3157a01d7a57d"}

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

gopherbot · 2025-09-08T01:20:03Z

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

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

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-09-08T01:27:31Z

Message from Jorropo:

Patch Set 1: -Commit-Queue

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

gopherbot · 2025-09-08T01:27:31Z

Message from Go LUCI:

Patch Set 1:

This CL has failed the run. Reason:

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

go on master (change 701615)

To reproduce, try gomote repro 8704338145488906337.

Additional links for debugging:

go tool dist test -json output [shard 1]

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

gopherbot · 2025-09-08T01:27:32Z

Message from Go LUCI:

Patch Set 1: LUCI-TryBot-Result-1

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

gopherbot · 2025-09-08T02:27:49Z

Message from Daniel Maslowski:

Patch Set 2:

(6 comments)

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

gopherbot · 2025-09-08T03:47:33Z

Message from Jorropo:

Patch Set 3:

(2 comments)

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

gopherbot · 2025-09-08T04:02:46Z

Message from Jorropo:

Patch Set 3:

(1 comment)

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

gopherbot · 2025-09-09T13:05:04Z

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

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

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-09-09T13:23:22Z

Message from Jorropo:

Patch Set 4:

(3 comments)

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

gopherbot · 2025-09-09T14:57:04Z

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

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

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-09-09T16:36:41Z

Message from Daniel Maslowski:

Patch Set 5:

(5 comments)

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

gopherbot · 2025-09-09T16:36:48Z

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

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

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-09-09T18:22:25Z

Message from Jorropo:

Patch Set 6:

(1 comment)

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

gopherbot · 2025-09-11T17:47:42Z

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

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

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-09-11T17:55:20Z

Message from Daniel Maslowski:

Patch Set 6:

(4 comments)

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

gopherbot · 2025-09-11T19:42:26Z

Message from Daniel Maslowski:

Patch Set 7:

(1 comment)

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

gopherbot · 2025-09-11T20:33:54Z

Message from Jorropo:

Patch Set 7:

(1 comment)

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

gopherbot · 2025-09-11T21:08:24Z

Message from Daniel Maslowski:

Patch Set 7:

(1 comment)

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

gopherbot · 2025-09-11T21:16:29Z

Message from Daniel Maslowski:

Patch Set 7:

(1 comment)

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

gopherbot · 2025-09-11T21:16:38Z

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

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

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-09-18T12:25:26Z

Message from Jorropo:

Patch Set 20:

(3 comments)

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

gopherbot · 2025-09-18T12:25:27Z

Message from Jorropo:

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

(1 comment)

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

gopherbot · 2025-09-18T12:34:17Z

Message from Go LUCI:

Patch Set 20:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-18T12:17:55Z","revision":"8b1aeabd4e891ec27f9826c0a0116d0db1335096"}

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

gopherbot · 2025-09-18T12:34:18Z

Message from Jorropo:

Patch Set 20: -Commit-Queue

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

gopherbot · 2025-09-18T12:34:18Z

Message from Go LUCI:

Patch Set 20:

This CL has failed the run. Reason:

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

go on master (change 701615)

To reproduce, try gomote repro 8703389615584658993.

Additional links for debugging:

make.bash output [shard 1]

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

gopherbot · 2025-09-18T12:34:19Z

Message from Go LUCI:

Patch Set 20: LUCI-TryBot-Result-1

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

gopherbot · 2025-09-18T13:10:20Z

Message from Daniel Maslowski:

Patch Set 20:

(2 comments)

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

gopherbot · 2025-09-18T13:28:34Z

Message from Jorropo:

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

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

gopherbot · 2025-09-18T13:28:35Z

Message from Go LUCI:

Patch Set 21:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-18T13:10:21Z","revision":"c946ac4e1630f6904fec87d437106675fec65503"}

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

gopherbot · 2025-09-18T13:28:35Z

Message from Go LUCI:

Patch Set 21: LUCI-TryBot-Result-1

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

gopherbot · 2025-09-18T13:47:01Z

Message from Jorropo:

Patch Set 23: Code-Review+2

(7 comments)

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

gopherbot · 2025-09-18T13:56:02Z

Message from Jorropo:

Patch Set 23:

(4 comments)

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

Linux introduced new syscalls to fix the year 2038 issue. To still be able to use the old ones, the Kconfig option COMPAT_32BIT_TIME would be necessary. Use the new syscall with 64-bit values for futexwakeup by default. Define _ENOSYS for detecting if it's not available. Add a fallback to use the older syscall in case the new one is not available, since Go runs on Linux from 2.6.32 on, per https://go.dev/wiki/MinimumRequirements. Fixes golang#75133

gopherbot · 2025-09-18T15:43:46Z

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

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

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-09-18T15:52:25Z

Message from Daniel Maslowski:

Patch Set 23:

(7 comments)

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

gopherbot · 2025-09-18T19:24:54Z

Message from Jorropo:

Patch Set 24:

(1 comment)

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

gopherbot · 2025-09-18T19:32:55Z

Message from Jorropo:

Patch Set 24: Commit-Queue+1

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

gopherbot · 2025-09-18T19:32:55Z

Message from Jorropo:

Patch Set 24: Code-Review+2

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

gopherbot · 2025-09-18T19:32:56Z

Message from Go LUCI:

Patch Set 24:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-18T19:18:21Z","revision":"14f79d5b79d510aea467f2daf020535236fc9b28"}

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

gopherbot · 2025-09-18T19:40:55Z

Message from Jorropo:

Patch Set 24: -Commit-Queue

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

gopherbot · 2025-09-18T19:40:55Z

Message from Go LUCI:

Patch Set 24:

This CL has passed the run

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

gopherbot · 2025-09-18T19:40:56Z

Message from Go LUCI:

Patch Set 24: LUCI-TryBot-Result+1

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

gopherbot · 2025-09-18T19:40:56Z

Message from Jorropo:

Patch Set 24:

(1 comment)

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

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

Message from Michael Knyszek:

Patch Set 24: Code-Review+2

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

gopherbot · 2025-09-18T20:37:19Z

Message from Mark Freeman:

Patch Set 24: Code-Review+1

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

gopherbot · 2025-09-19T02:42:53Z

Message from Jorropo:

Patch Set 24:

(1 comment)

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

Linux introduced new syscalls to fix the year 2038 issue. To still be able to use the old ones, the Kconfig option COMPAT_32BIT_TIME would be necessary. Use the new syscall with 64-bit values for futex by default. Define _ENOSYS for detecting if it's not available. Add a fallback to use the older syscall in case the new one is not available, since Go runs on Linux from 2.6.32 on, per https://go.dev/wiki/MinimumRequirements. Updates #75133 Change-Id: I65daff0a3d06b55440ff05d8f5a9aa1c07eb201d GitHub-Last-Rev: 96dd1bd GitHub-Pull-Request: #75306 Reviewed-on: https://go-review.googlesource.com/c/go/+/701615 Reviewed-by: Michael Knyszek <mknyszek@google.com> Reviewed-by: Mark Freeman <markfreeman@google.com> Reviewed-by: Jorropo <jorropo.pgm@gmail.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>

gopherbot · 2025-09-19T04:10:38Z

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

orangecms force-pushed the futex32 branch from 3484e2b to 5962a6a Compare September 8, 2025 01:19

austinderek mentioned this pull request Sep 8, 2025

runtime/linux: 32-bit futex fallback PullRequestInc/go#68

Closed

orangecms changed the title ~~runtime/linux: 32-bit futex fallback~~ runtime: fall back to 32-bit futex on Linux Sep 8, 2025

orangecms force-pushed the futex32 branch from 5962a6a to 8ad50b5 Compare September 9, 2025 13:00

orangecms force-pushed the futex32 branch from e6236ba to 695bde7 Compare September 11, 2025 17:44

orangecms force-pushed the futex32 branch from 4251a01 to 96dd1bd Compare September 18, 2025 15:42

gopherbot closed this Sep 19, 2025

runtime: use futexes with 64-bit time on Linux #75306

runtime: use futexes with 64-bit time on Linux #75306

Uh oh!

Conversation

orangecms commented Sep 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 8, 2025

Uh oh!

gopherbot commented Sep 9, 2025

Uh oh!

gopherbot commented Sep 9, 2025

Uh oh!

gopherbot commented Sep 9, 2025

Uh oh!

gopherbot commented Sep 9, 2025

Uh oh!

gopherbot commented Sep 9, 2025

Uh oh!

gopherbot commented Sep 9, 2025

Uh oh!

gopherbot commented Sep 11, 2025

Uh oh!

gopherbot commented Sep 11, 2025

Uh oh!

gopherbot commented Sep 11, 2025

Uh oh!

gopherbot commented Sep 11, 2025

Uh oh!

gopherbot commented Sep 11, 2025

Uh oh!

gopherbot commented Sep 11, 2025

Uh oh!

gopherbot commented Sep 11, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

orangecms commented Sep 8, 2025 •

edited

Loading