immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-28 19:08:20 +03:00
Code Issues 783 Packages Projects Releases 12 Wiki Activity

[PR #6117] [CLOSED] fix(web): allow future timebuckets #11085

New Issue
Closed
opened 2026-02-05 14:33:15 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 14:33:15 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/immich-app/immich/pull/6117
Author: @m1yon
Created: 1/2/2024
Status: ❌ Closed

Base: main ← Head: fix/future-timestamps

📝 Commits (2)

  • 4b9e28f fix(web): adjust asset query so future timestamps that are valid are returned
  • cb669cf chore: rebase and gen sql

📊 Changes

2 files changed (+6 additions, -6 deletions)

View changed files

📝 server/src/infra/repositories/asset.repository.ts (+1 -1)
📝 server/src/infra/sql/asset.repository.sql (+5 -5)

📄 Description

fixes #5578

The original cause of the issue was a fix (#4540) intended for #4264 and #4538, which are Postgres "Time zone displacement out of range" errors caused by invalid dates.

Postgres only supports date values from 4713 BC to 5874897 AD.

I'm having a hard time replicating the original issues because using any date past 9999 AD in the .xmp files seems to reset the postgres date to the current date.

I've tested a smaller date range here though, and it works as expected.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/immich-app/immich/pull/6117 **Author:** [@m1yon](https://github.com/m1yon) **Created:** 1/2/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/future-timestamps` --- ### 📝 Commits (2) - [`4b9e28f`](https://github.com/immich-app/immich/commit/4b9e28f2cc46e706dc67930f53c19fb321a88d56) fix(web): adjust asset query so future timestamps that are valid are returned - [`cb669cf`](https://github.com/immich-app/immich/commit/cb669cf625c116cbc0edcac3a60a09c674fc2719) chore: rebase and gen sql ### 📊 Changes **2 files changed** (+6 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `server/src/infra/repositories/asset.repository.ts` (+1 -1) 📝 `server/src/infra/sql/asset.repository.sql` (+5 -5) </details> ### 📄 Description fixes #5578 The original cause of the issue was a fix (#4540) intended for #4264 and #4538, which are Postgres "Time zone displacement out of range" errors caused by invalid dates. [Postgres only supports date values from 4713 BC to 5874897 AD.](https://www.prisma.io/dataguide/postgresql/date-types#:~:text=The%20range%20of%20values%20for,in%20PostgreSQL%20for%20inserting%20data.) I'm having a hard time replicating the original issues because using any date past 9999 AD in the `.xmp` files seems to reset the postgres date to the current date. I've tested a smaller date range here though, and it works as expected. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-05 14:33:15 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#11085
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?