What's the deal with +2800 time zone? #1385

mcepl · 2025-04-28T12:52:51Z

mcepl
Apr 28, 2025

I am trying to make configuration for git-bug on Sourcehut CI and tests fail to pass with this mysterious errors:

=== RUN   TestBugCommentNew
    bug_comment_add_test.go:17: 
        	Error Trace:	/home/build/git-bug/commands/bug/bug_comment_test.go:94
        	            				/home/build/git-bug/commands/bug/bug_comment_test.go:56
        	            				/home/build/git-bug/commands/bug/bug_comment_test.go:139
        	            				/home/build/git-bug/commands/bug/bug_comment_add_test.go:17
        	Error:      	Received unexpected error:
        	            	parsing time "Mon Apr 28 10:11:15 2025 +2800": time zone offset hour out of range
        	Test:       	TestBugCommentNew
--- FAIL: TestBugCommentNew (0.00s)
=== RUN   TestBugCommentEdit
    bug_comment_edit_test.go:22: 
        	Error Trace:	/home/build/git-bug/commands/bug/bug_comment_test.go:94
        	            				/home/build/git-bug/commands/bug/bug_comment_test.go:56
        	            				/home/build/git-bug/commands/bug/bug_comment_test.go:139
        	            				/home/build/git-bug/commands/bug/bug_comment_edit_test.go:22
        	Error:      	Received unexpected error:
        	            	parsing time "Mon Apr 28 10:11:15 2025 +2800": time zone offset hour out of range
        	Test:       	TestBugCommentEdit
--- FAIL: TestBugCommentEdit (0.00s)
=== RUN   TestBugComment
    bug_comment_test.go:24: 
        	Error Trace:	/home/build/git-bug/commands/bug/bug_comment_test.go:94
        	            				/home/build/git-bug/commands/bug/bug_comment_test.go:56
        	            				/home/build/git-bug/commands/bug/bug_comment_test.go:139
        	            				/home/build/git-bug/commands/bug/bug_comment_test.go:24
        	Error:      	Received unexpected error:
        	            	parsing time "Mon Apr 28 10:11:15 2025 +2800": time zone offset hour out of range
        	Test:       	TestBugComment
--- FAIL: TestBugComment (0.00s)

I have to admit that +2800 time zone baffles me a bit, moreover when I cannot find anywhere in the code where such time would be set. Is it something about setting TZ variable, locale, or something? Anybody any idea?

Thank you in advance for any response

Answered by sudoforge

Apr 29, 2025

first off: thanks for creating this -- i was pretty sure it was an upstream bug, or an issue due to my own environment. you posting this (with a failure at HEAD) provided confirmation that it was a bug.

the issue was caused by an invalid format string being used in calls to time.Time.Format(). i left additional context on the pull request that provides a fix: #1388

i created an issue from this discussion -- odd that github doesn't show that in the UI: #1387

View full answer

sudoforge · 2025-04-28T14:26:22Z

sudoforge
Apr 28, 2025

i ran into this recently as well when attempting to do an upgrade of golang.org/x/net:

=== RUN   TestBugCommentNew
    bug_comment_add_test.go:17: 
        	Error Trace:	/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:94
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:56
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:139
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_add_test.go:17
        	Error:      	Received unexpected error:
        	            	parsing time "Fri Apr 25 17:09:38 2025 +2500": time zone offset hour out of range
        	Test:       	TestBugCommentNew
--- FAIL: TestBugCommentNew (0.02s)
=== RUN   TestBugCommentEdit
    bug_comment_edit_test.go:22: 
        	Error Trace:	/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:94
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:56
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:139
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_edit_test.go:22
        	Error:      	Received unexpected error:
        	            	parsing time "Fri Apr 25 17:09:38 2025 +2500": time zone offset hour out of range
        	Test:       	TestBugCommentEdit
--- FAIL: TestBugCommentEdit (0.02s)
=== RUN   TestBugComment
    bug_comment_test.go:24: 
        	Error Trace:	/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:94
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:56
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:139
        	            				/home/runner/work/git-bug/git-bug/commands/bug/bug_comment_test.go:24
        	Error:      	Received unexpected error:
        	            	parsing time "Fri Apr 25 17:09:38 2025 +[250](https://github.com/git-bug/git-bug/actions/runs/14669369252/job/41173444306#step:5:251)0": time zone offset hour out of range
        	Test:       	TestBugComment

but i couldn't reproduce it at HEAD, so i made the assumption it was an upstream bug and filed it away as a Future Me Problem™.

it looks like in your repo that you're just building off of HEAD with some the hut-specific CI changes, though, right?

2 replies

sudoforge Apr 28, 2025

note: i did look into this so far as to verify that the weird and nonsensical offset is indeed what i was getting back from time.Time()

mcepl Apr 28, 2025
Author

it looks like in your repo that you're just building off of HEAD with some the hut-specific CI changes, though, right?

Yes, you can see here. HEAD^ is https://github.com/git-bug/git-bug@master here.

sudoforge · 2025-04-29T00:03:41Z

sudoforge
Apr 29, 2025

first off: thanks for creating this -- i was pretty sure it was an upstream bug, or an issue due to my own environment. you posting this (with a failure at HEAD) provided confirmation that it was a bug.

the issue was caused by an invalid format string being used in calls to time.Time.Format(). i left additional context on the pull request that provides a fix: #1388

i created an issue from this discussion -- odd that github doesn't show that in the UI: #1387

1 reply

mcepl Apr 29, 2025
Author

Thank you, CI now passes https://builds.sr.ht/~mcepl/job/1480335 \o/!

Navigation Menu

Repository navigation

What's the deal with +2800 time zone? #1385

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 3 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

What's the deal with +2800 time zone? #1385

Uh oh!

mcepl Apr 28, 2025

Replies: 2 comments · 3 replies

Uh oh!

sudoforge Apr 28, 2025

Uh oh!

sudoforge Apr 28, 2025

Uh oh!

Uh oh!

mcepl Apr 28, 2025 Author

Uh oh!

Uh oh!

sudoforge Apr 29, 2025

Uh oh!

mcepl Apr 29, 2025 Author

mcepl
Apr 28, 2025

Replies: 2 comments 3 replies

sudoforge
Apr 28, 2025

mcepl Apr 28, 2025
Author

sudoforge
Apr 29, 2025

mcepl Apr 29, 2025
Author