Bug: Invalid date on folders

[wraithy]

What happened?

The "creation date" and "last updated" dates show as "invalid date" on the list view and "NaN years ago" in the grid view.

List View

Grid View

Version

upstream (ghcr.io/diced/zipline:trunk)

What browser(s) are you seeing the problem on?

No response

Zipline Logs

No response

Browser Logs

No response

Additional Info

No response

[TacticalTechJay]

Try ghcr.io/diced/zipline:trunk for the docker image if you're using ghcr.io/diced/zipline or ghcr.io/diced/zipline:latest. It may already be fixed in the recommended image.

[wraithy]

Try ghcr.io/diced/zipline:trunk for the docker image if you're using ghcr.io/diced/zipline or ghcr.io/diced/zipline:latest. It may already be fixed in the recommended image.

I switched my docker image to ghcr.io/diced/zipline:trunk yesterday and I get the same thing (even when making new folders).

[TacticalTechJay]

Do the folders have a valid date when checking with the database? If you're using postgres with docker, you can use this:
docker compose exec postgres psql -U postgres -d postgres -c "SELECT * FROM \"Folder\";"

[TacticalTechJay]

Alternatively, you can use the API to check the date. You can either use curl with your token in the header or use the browser you're logged into zipline on. The endpoint is /api/user/folders

[wraithy]

Alternatively, you can use the API to check the date. You can either use curl with your token in the header or use the browser you're logged into zipline on. The endpoint is /api/user/folders

Looks like they do have valid dates when checking the database.

EDIT: Actually I think the issue is that they are not whole seconds and have a decimal at the end which is resulting in it being an invalid date.

[TacticalTechJay]

Hmmm, it could be. How is /api/user/folders? Does it show the right date?

[wraithy]

Hmmm, it could be. How is /api/user/folders? Does it show the right date?

Dates look good to me via the endpoint

[wraithy]

I also tried removing the decimal and the numbers after in the database however they are just set to 0 when I fetch the info from the API.

[TacticalTechJay]

Honestly got no clue what's causing this 😔
What browser @wraithdotcat? And is the issue still happening

[wraithy]

Honestly got no clue what's causing this 😔 What browser @wraithdotcat? And is the issue still happening

I am using Chrome and yea it is still happening :/

[TacticalTechJay]

What version?

[wraithy]

Trunk although I am using my fork (which is exactly the same just without the video thumbnails)

[TacticalTechJay]

Chrome version?

[wraithy]

Version 115.0.5790.102 (Official Build) (64-bit)

[TacticalTechJay]

Do you currently use any extensions like an adblocker?

[wraithy]

I do however I have tried other browsers and running in incognito and I get the same result

[diced]

If you don't mind me asking, what country do you live in? If you are able to get the locale it could help us see if the problem is with your locale's way of parsing dates.

[wraithy]

If you don't mind me asking, what country do you live in? If you are able to get the locale it could help us see if the problem is with your locale's way of parsing dates.

I live in the UK however my instance is hosted in Ashburn, Virginia in the US. I assume that the times are based on the server time rather than the client but I could be wrong so I thought I would include both.

[TacticalTechJay]

Seems like that was it. Doesn't seem to enjoy other format for time

[TacticalTechJay]

@diced 🫡

[diced]

hopefully the commit above fixes this issue for good, but i'll still leave this issue open until we hear back from @wraithdotcat

[wraithy]

The dates are fixed now thanks!

however now the images don't load :/

the image source is domain.tld/r/image.png?compress=false and when I go directly to that url I get the following

{"statusCode":500,"code":"ENOENT","error":"Internal Server Error","message":"ENOENT: no such file or directory, open './mimes.json'"}

[TacticalTechJay]

Doesn't seem to have been caused by me ¯\_(ツ)_/¯
@diced I think you managed to exclude mimes.json from the docker image somewhere down the line...

[TacticalTechJay]

So, with the issue at the beginning resolved I'll be closing this. Open a new one with your new problem for organization purposes.