windows/registry: correct KeyInfo.ModTime calculation by gremat · Pull Request #251 · golang/sys

gremat · 2025-06-20T11:15:00Z

Filetime.Nanoseconds() has a major drawback: the returned int64 is too small to
represent Filetime's zero value (January 1, 1601, [1]) in terms of nanoseconds
since Epoch (00:00:00 UTC, January 1, 1970); MinInt64 [2] only dates back to
year 1677.

This has real-life implications, e.g., some Windows sub systems (Perflib, to
name one) create registry keys with the last write time property set to
zero (see note below). In this case, ModTime() reports an underflow-affected
value of 2185-07-22T00:34:33.709551+01:00.

This commit drops usage of Nanoseconds() in favor of a conversion that converts
first to seconds and nanoseconds before gauging thus is capable to cover the
full range of Filetime values.

A note on last write time values: lastWriteTime is not exposed in the UI
(say, regedit) or in PowerShell (Get-ItemProperty), you need to query
RegQueryInfoKeyA [3] explicitly in some way [4] or another [5]. The source of
the latter is offline by now but can be found elsewhere [6] and provides a
quick way to show the value.

[1] https://learn.microsoft.com/en-us/windows/win32/api/minwinbase/ns-minwinbase-filetime
[2] https://pkg.go.dev/math#pkg-constants
[3] https://learn.microsoft.com/en-us/windows/win32/api/winreg/nf-winreg-regqueryinfokeya?redirectedfrom=MSDN
[4] https://learn.microsoft.com/en-us/windows/win32/sysinfo/retrieving-the-last-write-time
[5] https://learn-powershell.net/2014/12/18/retrieving-a-registry-key-lastwritetime-using-powershell/
[6] https://github.com/wxrdnx/GetRegistryKeyLastWriteTimeAndClassName

Fixes golang/go#74335.

gopherbot · 2025-06-20T11:23:12Z

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

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

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-06-20T11:30:02Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

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

gopherbot · 2025-06-20T11:30:03Z

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

gopherbot · 2025-06-23T06:35:47Z

Message from Alex Brainman:

Patch Set 1:

(2 comments)

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

gopherbot · 2025-06-23T07:26:29Z

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

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

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-06-23T07:41:31Z

Message from Gregor Matura:

Patch Set 2:

(1 comment)

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

gopherbot · 2025-06-23T08:03:46Z

Message from Alex Brainman:

Patch Set 2:

(2 comments)

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

gopherbot · 2025-06-23T08:26:33Z

Message from Gregor Matura:

Patch Set 2:

(1 comment)

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

gopherbot · 2025-06-23T08:33:40Z

Message from Gregor Matura:

Patch Set 2:

(1 comment)

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

gopherbot · 2025-06-23T08:40:44Z

Message from Gregor Matura:

Patch Set 3:

(1 comment)

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

gopherbot · 2025-06-23T08:54:36Z

Message from Gregor Matura:

Patch Set 3:

(1 comment)

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

gopherbot · 2025-06-23T15:12:56Z

Message from Gregor Matura:

Patch Set 4:

(1 comment)

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

gopherbot · 2025-06-24T05:15:50Z

Message from Alex Brainman:

Patch Set 5:

(2 comments)

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

gopherbot · 2025-07-01T14:27:58Z

Message from Gregor Matura:

Patch Set 5:

(2 comments)

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

gopherbot · 2025-08-10T02:04:30Z

Message from Alex Brainman:

Patch Set 5:

(6 comments)

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

gopherbot · 2025-10-02T10:20:27Z

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

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

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-10-02T10:28:30Z

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

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

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-10-02T11:08:05Z

Message from Gregor Matura:

Patch Set 8:

(4 comments)

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

gopherbot · 2026-02-25T08:19:54Z

Message from Alex Brainman:

Patch Set 8: Commit-Queue+1

(5 comments)

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

gopherbot · 2026-02-25T08:29:31Z

Message from Go LUCI:

Patch Set 8:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-02-25T08:12:34Z","revision":"bed02f8dd686bf04ed1c40130fc648c751bfbbda"}

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

gopherbot · 2026-02-25T08:29:32Z

Message from Alex Brainman:

Patch Set 8: -Commit-Queue

(Performed by <GERRIT_ACCOUNT_60063> on behalf of <GERRIT_ACCOUNT_5070>)

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

gopherbot · 2026-02-25T08:29:33Z

Message from Go LUCI:

Patch Set 8:

This CL has passed the run

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

gopherbot · 2026-02-25T08:29:33Z

Message from Go LUCI:

Patch Set 8: LUCI-TryBot-Result+1

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

gopherbot · 2026-02-25T08:29:44Z

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

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

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 · 2026-02-25T09:24:09Z

Message from Gregor Matura:

Patch Set 10:

(4 comments)

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

gopherbot · 2026-02-26T00:53:00Z

Message from Alex Brainman:

Patch Set 10:

(8 comments)

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

gopherbot · 2026-02-26T07:53:30Z

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

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

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 · 2026-02-26T08:03:33Z

Message from Gregor Matura:

Patch Set 10:

(2 comments)

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

gopherbot · 2026-02-27T00:04:40Z

Message from Alex Brainman:

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

(1 comment)

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

gopherbot · 2026-02-27T00:13:37Z

Message from Go LUCI:

Patch Set 11:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-02-26T23:53:49Z","revision":"50e14a6492566fe058a5d4fcef85d390e94839fe"}

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

gopherbot · 2026-02-27T00:13:38Z

Message from Alex Brainman:

Patch Set 11: -Commit-Queue

(Performed by <GERRIT_ACCOUNT_60063> on behalf of <GERRIT_ACCOUNT_5070>)

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

gopherbot · 2026-02-27T00:13:39Z

Message from Go LUCI:

Patch Set 11:

This CL has passed the run

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

gopherbot · 2026-02-27T00:13:39Z

Message from Go LUCI:

Patch Set 11: LUCI-TryBot-Result+1

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

gopherbot · 2026-02-27T00:22:35Z

Message from Alex Brainman:

Patch Set 11:

(1 comment)

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

gopherbot · 2026-02-28T04:27:50Z

Message from David Chase:

Patch Set 11: Code-Review+1

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

gopherbot · 2026-02-28T11:05:12Z

Message from Russ Cox:

Patch Set 11:

(2 comments)

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

gopherbot · 2026-02-28T11:05:13Z

Message from Russ Cox:

Patch Set 11: Code-Review+1

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

gopherbot · 2026-03-01T02:10:29Z

Message from Alex Brainman:

Patch Set 11:

(1 comment)

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

Filetime.Nanoseconds() has a major drawback: the returned int64 is too small to represent Filetime's zero value (January 1, 1601) in terms of nanoseconds since Epoch (00:00:00 UTC, January 1, 1970); MinInt64 only dates back to year 1677. This has real-life implications, e.g., some Windows sub systems (Perflib, to name one) create registry keys with the last write time property set to zero. In this case, ModTime() reports an underflow-affected value of 2185-07-22T00:34:33.709551+01:00. This commit drops usage of Nanoseconds() in favor of a conversion that converts first to seconds and nanoseconds before gauging thus is capable to cover the full range of Filetime values. Fixes golang/go#74335

gopherbot · 2026-03-02T08:57:16Z

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

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

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 · 2026-03-02T09:06:46Z

Message from Gregor Matura:

Patch Set 11:

(2 comments)

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

Filetime.Nanoseconds() has a major drawback: the returned int64 is too small to represent Filetime's zero value (January 1, 1601, [1]) in terms of nanoseconds since Epoch (00:00:00 UTC, January 1, 1970); MinInt64 [2] only dates back to year 1677. This has real-life implications, e.g., some Windows sub systems (Perflib, to name one) create registry keys with the last write time property set to zero (see note below). In this case, ModTime() reports an underflow-affected value of 2185-07-22T00:34:33.709551+01:00. This commit drops usage of Nanoseconds() in favor of a conversion that converts first to seconds and nanoseconds before gauging thus is capable to cover the full range of Filetime values. A note on last write time values: `lastWriteTime` is not exposed in the UI (say, `regedit`) or in PowerShell (`Get-ItemProperty`), you need to query `RegQueryInfoKeyA` [3] explicitly in some way [4] or another [5]. The source of the latter is offline by now but can be found elsewhere [6] and provides a quick way to show the value. [1] https://learn.microsoft.com/en-us/windows/win32/api/minwinbase/ns-minwinbase-filetime [2] https://pkg.go.dev/math#pkg-constants [3] https://learn.microsoft.com/en-us/windows/win32/api/winreg/nf-winreg-regqueryinfokeya?redirectedfrom=MSDN [4] https://learn.microsoft.com/en-us/windows/win32/sysinfo/retrieving-the-last-write-time [5] https://learn-powershell.net/2014/12/18/retrieving-a-registry-key-lastwritetime-using-powershell/ [6] https://github.com/wxrdnx/GetRegistryKeyLastWriteTimeAndClassName Fixes golang/go#74335. Change-Id: I83dc1d6b5e0c581bfb53d58ee08a21ed9c166b0f GitHub-Last-Rev: 0073d1d GitHub-Pull-Request: #251 Reviewed-on: https://go-review.googlesource.com/c/sys/+/682816 Reviewed-by: Alex Brainman <alex.brainman@gmail.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>

gopherbot · 2026-03-03T01:55:06Z

Message from Alex Brainman:

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

(1 comment)

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

gopherbot · 2026-03-03T02:03:51Z

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

gremat force-pushed the windows/fix-filetime-conversions-and-deprecate-nanoseconds branch from 5c27ec0 to 4bc759a Compare June 23, 2025 07:25

gremat force-pushed the windows/fix-filetime-conversions-and-deprecate-nanoseconds branch 2 times, most recently from 933c73d to 8443a7e Compare October 2, 2025 10:18

gremat force-pushed the windows/fix-filetime-conversions-and-deprecate-nanoseconds branch from 8443a7e to 933af5e Compare October 2, 2025 10:25

gremat force-pushed the windows/fix-filetime-conversions-and-deprecate-nanoseconds branch from 933af5e to 1748322 Compare February 25, 2026 08:29

gremat changed the title ~~windows: fix filetime conversions and deprecate Nanoseconds~~ windows/registry: correct KeyInfo.ModTime calculation Feb 25, 2026

gremat force-pushed the windows/fix-filetime-conversions-and-deprecate-nanoseconds branch from 1748322 to 8fb08ee Compare February 26, 2026 07:47

gremat force-pushed the windows/fix-filetime-conversions-and-deprecate-nanoseconds branch from 8fb08ee to 0073d1d Compare March 2, 2026 08:51

gopherbot closed this Mar 3, 2026

Conversation

gremat commented Jun 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gopherbot commented Jun 20, 2025

Uh oh!

gopherbot commented Jun 20, 2025

Uh oh!

gopherbot commented Jun 20, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 23, 2025

Uh oh!

gopherbot commented Jun 24, 2025

Uh oh!

gopherbot commented Jul 1, 2025

Uh oh!

gopherbot commented Aug 10, 2025

Uh oh!

gopherbot commented Oct 2, 2025

Uh oh!

gopherbot commented Oct 2, 2025

Uh oh!

gopherbot commented Oct 2, 2025

Uh oh!

gopherbot commented Feb 25, 2026

Uh oh!

gopherbot commented Feb 25, 2026

Uh oh!

gopherbot commented Feb 25, 2026

Uh oh!

gopherbot commented Feb 25, 2026

Uh oh!

gopherbot commented Feb 25, 2026

Uh oh!

gopherbot commented Feb 25, 2026

Uh oh!

gopherbot commented Feb 25, 2026

Uh oh!

gopherbot commented Feb 26, 2026

Uh oh!

gopherbot commented Feb 26, 2026

Uh oh!

gopherbot commented Feb 26, 2026

Uh oh!

gopherbot commented Feb 27, 2026

Uh oh!

gopherbot commented Feb 27, 2026

Uh oh!

gopherbot commented Feb 27, 2026

Uh oh!

gopherbot commented Feb 27, 2026

Uh oh!

gopherbot commented Feb 27, 2026

Uh oh!

gopherbot commented Feb 27, 2026

Uh oh!

gopherbot commented Feb 28, 2026

Uh oh!

gopherbot commented Feb 28, 2026

Uh oh!

gopherbot commented Feb 28, 2026

Uh oh!

gopherbot commented Mar 1, 2026

Uh oh!

gremat commented Jun 20, 2025 •

edited

Loading