Time Zone Localization

[Domo929]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When I run my test suite, whether by clicking the "Run all tests" button or by letting it detect changes and run, it shows the most recent test run as "4 hours ago".

Expected Behavior

When I run a test, the most recent listing is shown as "Now" or "1 Minute Ago"

Steps To Reproduce

1. Run WSL2 on Windows
2. Navigate to a Go Project saved on a WSL2
3. Run gokiburi
4. Open http://127.0.0.1:9393/
5. Let it run test suites, or trigger a run automatically
6. Observe time since last test

Environment

- OS: 
Edition	Windows 11 Enterprise
Version	22H2
OS build	22621.1555
- Architecture: amd64
- Gokiburi: v0.1.0
- Browser: Firefox 13.0

Anything else?

I'm currently in the EDT time zone, which is 4 hours off of UTC, so that is likely the culprit.

I ran date in my WSL2 shell and confirmed that the WSL2 time matches my Windows/IRL time.

[michenriksen]

Hi there, thanks for reporting!

I tried setting my system time to be in EDT to reproduce the issue in Firefox, but I was unfortunately not able to. I also tried with Chrome DevTool's location simulation, but that didn't trigger it either. 😕

Do you have any privacy extensions or similar installed that could be doing trickery with the browser's datetime for anti-fingerprinting or something like that?

It's also possible that it's a Windows-specific issue.

I'm marking the issue as not reproducible for now, but I would greatly appreciate any additional information that could help me resolve the issue.

Also, since you're on a Windows machine, please feel free to report any bugs or weirdness, as I have been developing this tool exclusively on Mac. 🙇

[Domo929]

Hey! Happy to help.

Do you have any privacy extensions or similar installed that could be doing trickery with the browser's datetime for anti-fingerprinting or something like that?

I run Ghostery and uBlock Origin, but neither of them reported changing anything. When I disabled both of them and reloaded the page / restarted the CL app, I had the same issue.

Is there some specific place you'd like me to snoop with the browser debugging tools? I'm not a JS developer myself but I'm happy to look wherever I can for more information.

Besides the timing issues, it seems to run pretty great on WSL! Been enjoying this tool a lot.