Gamemaker studio 2: Modified files have modification time as "59 minutes from now" #2257

New Issue

2025-11-02T04:29:49-06:00

GiteaMirror commented

2025-11-02 04:29:49 -06:00

Originally created by @CoderReece on GitHub (Aug 27, 2018).

Gitea version (or commit ref): Latest Release from current date.
Git version: 2.18.0
Operating system: Windows 10
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:
No logs at the moment.

Description

I believe this is a software compatibility issue. I've been using gitea for some time now since Gamemaker studio 2 forced me over from svn. I like git it's helpful.

This issue is that after pushing a commit to the repo the modified files say "59 minutes from now" as the modification date. I've tried applying commits for other projects not using gamemaker studio and the time is correct.

Screenshots

Screenshot is 6 minutes after the issue. effected files are "53 minutes from now"

Originally created by @CoderReece on GitHub (Aug 27, 2018). - Gitea version (or commit ref): Latest Release from current date. - Git version: 2.18.0 - Operating system: Windows 10 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: No logs at the moment. ## Description I believe this is a software compatibility issue. I've been using gitea for some time now since Gamemaker studio 2 forced me over from svn. I like git it's helpful. This issue is that after pushing a commit to the repo the modified files say "59 minutes from now" as the modification date. I've tried applying commits for other projects not using gamemaker studio and the time is correct. ## Screenshots Screenshot is 6 minutes after the issue. effected files are "53 minutes from now" ![timeissue](https://user-images.githubusercontent.com/8761891/44677473-e6f70a00-aa2d-11e8-8500-fe5e156f0355.PNG)

GiteaMirror closed this issue

2025-11-02 04:29:49 -06:00

GiteaMirror commented

2025-11-02 04:29:51 -06:00

@SagePtr commented on GitHub (Aug 27, 2018):

Does "git log" command run from local repo prints correct time or shifted by 59 minutes too?
If shifted, this is issue with software you are making commits with, looks like wrong timezone setting.

@SagePtr commented on GitHub (Aug 27, 2018): Does "git log" command run from local repo prints correct time or shifted by 59 minutes too? If shifted, this is issue with software you are making commits with, looks like wrong timezone setting.

GiteaMirror commented

2025-11-02 04:29:51 -06:00

@CoderReece commented on GitHub (Aug 27, 2018):

Date: Mon Aug 27 19:09:55 2018 +0100

It looks correct however i am unsure of what "+0100" is. could that be an offset?

@CoderReece commented on GitHub (Aug 27, 2018): > Date: Mon Aug 27 19:09:55 2018 +0100 It looks correct however i am unsure of what "+0100" is. could that be an offset?

GiteaMirror commented

2025-11-02 04:29:51 -06:00

@CoderReece commented on GitHub (Aug 27, 2018):

I can't find anything in the git documentation on how to change the repo time.

@CoderReece commented on GitHub (Aug 27, 2018): I can't find anything in the git documentation on how to change the repo time.

GiteaMirror commented

2025-11-02 04:29:51 -06:00

@SagePtr commented on GitHub (Aug 27, 2018):

+0100 is timezone (UTC+1)

@SagePtr commented on GitHub (Aug 27, 2018): +0100 is timezone (UTC+1)

GiteaMirror commented

2025-11-02 04:29:52 -06:00

@CoderReece commented on GitHub (Aug 27, 2018):

I know that i just don't know how to apply that to the git i'm very new to git

@CoderReece commented on GitHub (Aug 27, 2018): I know that i just don't know how to apply that to the git i'm very new to git

GiteaMirror commented

2025-11-02 04:29:52 -06:00

@SagePtr commented on GitHub (Aug 27, 2018):

And another question: does http://time.is/ shows right time or it detects clock wrong?

@SagePtr commented on GitHub (Aug 27, 2018): And another question: does http://time.is/ shows right time or it detects clock wrong?

GiteaMirror commented

2025-11-02 04:29:52 -06:00

@CoderReece commented on GitHub (Aug 27, 2018):

it shows the correct time and says it's 0.5 seconds ahead.

@CoderReece commented on GitHub (Aug 27, 2018): it shows the correct time and says it's 0.5 seconds ahead.

GiteaMirror commented

2025-11-02 04:29:53 -06:00

@SagePtr commented on GitHub (Aug 27, 2018):

Then computer time seems to be correct, and what about server time on which your gitea instance is installed? You can check it with developer tools of any browser, open Network tab, reload page with your remote repo and look "Date" response header.

@SagePtr commented on GitHub (Aug 27, 2018): Then computer time seems to be correct, and what about server time on which your gitea instance is installed? You can check it with developer tools of any browser, open Network tab, reload page with your remote repo and look "Date" response header.

GiteaMirror commented

2025-11-02 04:29:54 -06:00

@CoderReece commented on GitHub (Aug 27, 2018):

Hmm the response header date is behind the current time, right now the time is 00:34
Date: Mon, 27 Aug 2018 22:34:39 GMT

@CoderReece commented on GitHub (Aug 27, 2018): Hmm the response header date is behind the current time, right now the time is 00:34 Date: Mon, 27 Aug 2018 22:34:39 GMT

GiteaMirror commented

2025-11-02 04:29:54 -06:00

@SagePtr commented on GitHub (Aug 27, 2018):

So it's problem with server clock then, ask server administrator to adjust it

@SagePtr commented on GitHub (Aug 27, 2018): So it's problem with server clock then, ask server administrator to adjust it

GiteaMirror commented

2025-11-02 04:29:54 -06:00

@CoderReece commented on GitHub (Aug 27, 2018):

This is strange the server time is now wrong and the webserver also reports a different time however the commits are 10 seconds off, in which i can live with.

It might be because I've got it going through an apache reverse proxy.

Although do you know why this wasn't happening with my previous projects outside of gamemaker?

@CoderReece commented on GitHub (Aug 27, 2018): This is strange the server time is now wrong and the webserver also reports a different time however the commits are 10 seconds off, in which i can live with. It might be because I've got it going through an apache reverse proxy. Although do you know why this wasn't happening with my previous projects outside of gamemaker?

GiteaMirror commented

2025-11-02 04:29:55 -06:00

@SagePtr commented on GitHub (Aug 28, 2018):

No, it doesn't matter whenever server is behind reverse proxy or not. Probably time synchronization is not configured on server and someone switched DST manually.
Other projects probably don't print wrong time because you push to them through web-interface and all commits are marked with wrong-timezoned time which looks correct but has wrong timezone offset, if you clone such project to your local machine and look commit history with any git client - you will see wrong time there.

@SagePtr commented on GitHub (Aug 28, 2018): No, it doesn't matter whenever server is behind reverse proxy or not. Probably time synchronization is not configured on server and someone switched DST manually. Other projects probably don't print wrong time because you push to them through web-interface and all commits are marked with wrong-timezoned time which looks correct but has wrong timezone offset, if you clone such project to your local machine and look commit history with any git client - you will see wrong time there.

GiteaMirror commented

2025-11-02 04:29:55 -06:00