MarshalJSON for type timeutil.TimeStamp: The system cannot find the path specified [Windows] #150

Closed
opened 2020-03-06 00:23:09 +00:00 by plague69 · 9 comments

vikunja-master-windows-4.0-amd64.exe

Error
2020-03-06T11:10:45.4329312+11:00: ERROR ▶ handler/ReadAllWeb 004 json: error calling MarshalJSON for type timeutil.TimeStamp: The system cannot find the path specified.
json: error calling MarshalJSON for type timeutil.TimeStamp: The system cannot find the path specified.

System
Windows 10
Nginx running frontend

Symptoms
Web interface error 500 on nearly all actions. Sometimes performs the action and still error.

eg.

  • register: after filling in everything and clicking 'register', error 500 but creates the account
  • create namespace: error 500 and no namespace is created
vikunja-master-windows-4.0-amd64.exe **Error** 2020-03-06T11:10:45.4329312+11:00: ERROR ▶ handler/ReadAllWeb 004 json: error calling MarshalJSON for type timeutil.TimeStamp: The system cannot find the path specified. json: error calling MarshalJSON for type timeutil.TimeStamp: The system cannot find the path specified. **System** Windows 10 Nginx running frontend **Symptoms** Web interface error 500 on nearly all actions. Sometimes performs the action and still error. eg. - register: after filling in everything and clicking 'register', error 500 but creates the account - create namespace: error 500 and no namespace is created
plague69 started working 2020-03-06 01:59:02 +00:00
plague69 stopped working 2020-03-06 01:59:05 +00:00
3s
Owner

What did you configure as time zone?

What did you configure as time zone?
Author

GMT+10

Not sure what format it should be. I since set it back to the default as per the sample file "GMT", but still has the same issue.

Windows Server 2016 and Windows 10 tested if that helps

> GMT+10 Not sure what format it should be. I since set it back to the default as per the sample file "GMT", but still has the same issue. Windows Server 2016 and Windows 10 tested if that helps
Owner

It seems this is an issue in Go itself: https://github.com/golang/go/issues/21881

As a workaround until we have a better solution, you could try to install go on your machine (not a good workaround at all, I know). I'll try to workaround into Vikunja in the meantime.

It seems this is an issue in Go itself: https://github.com/golang/go/issues/21881 As a workaround until we have a better solution, you could try to install go on your machine (not a good workaround at all, I know). I'll try to workaround into Vikunja in the meantime.
Owner
I'll try to use https://github.com/leighmcculloch/go-tz
Owner

I've merged a possible fix in 4472020ee9, please test to see if the error still persists. A release should be available in about 45min.

(Unfortunatly, I can't really test this since I don't have a windows machine, sorry for that)

I've merged a possible fix in https://kolaente.dev/vikunja/api/commit/4472020ee9d1ed8abfef8c2550878339da96eb85, please test to see if the error still persists. A release should be available in about 45min. (Unfortunatly, I can't really test this since I don't have a windows machine, sorry for that)
konrad reopened this issue 2020-03-09 22:42:47 +00:00
Author

Thank you. I will test new release once available

Thank you. I will test new release once available
Owner

A new one is available: https://dl.vikunja.io/api/master/

A new one is available: https://dl.vikunja.io/api/master/
Author

Confirmed issue no longer exists on Windows Server 2016. Didn't have time to recompile frontend for the Windows 10 machine.

On a side note, frontend; I guess the config.json data is purly for the compiler and not runtime.

Confirmed issue no longer exists on Windows Server 2016. Didn't have time to recompile frontend for the Windows 10 machine. On a side note, frontend; I guess the config.json data is purly for the compiler and not runtime.
Owner

Great to hear it was fixed.

The config.json is currently only compile time, yes. That's something which needs to be fixed, but I need to find a good way to do this yet.

Closing this as resolved.

Great to hear it was fixed. The `config.json` is currently only compile time, yes. That's something which needs to be fixed, but I need to find a good way to do this yet. Closing this as resolved.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#150
No description provided.