fix: avoid postgres 100-argument limit in schedule, volume backup and port queries - #4931
Merged
Merged
Conversation
dosubot
Bot
added
size:S
windinternet
added a commit
to windinternet/dokploy
that referenced
this pull request
Jul 29, 2026
Brings in the upstream/canary HEAD (5df820a) as an ancestor of this branch using -s ours, matching the 2026-07-15 sync policy. The merge content is intentionally empty; this commit only records that every cherry-picked upstream commit has been reviewed and either integrated or explicitly rejected: - 32 security fixes (Dokploy#4855-Dokploy#4875): all integrated - 8 bug fixes (Dokploy#4626, Dokploy#4847, Dokploy#4876, Dokploy#4877, Dokploy#4911, Dokploy#4924, Dokploy#4929, Dokploy#4931): all integrated - 2 AI custom provider (Dokploy#4882): integrated - 1 icon management (Dokploy#4932): integrated with serviceNetworks stripped (Dokploy#3774 not picked) - SOS / Redis-removal / multi-language cleanup: rejected After this commit, GitHub will no longer list these upstream commits as 'ahead/behind' pending sync. Future upstream changes still need to be re-evaluated per docs/design-docs/2026-07-29-upstream-sync-policy.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4926
Migration 0175 took the
applicationtable to 101 columns, so any Drizzle relational query that hydrates the full table now exceeds Postgres'FUNC_MAX_ARGS = 100limit injson_build_array()and fails with error 54023. This brokefinPortById,findScheduleByIdandfindVolumeBackupById— schedules and volume backups silently stopped running, and ports could not be read or edited.Same fix as #4257 and #4924: narrow each nested
applicationselection to the columns its consumers actually read (applicationId,appName,serverId), keeping theenvironment → projectnesting where the org-id resolution needs it.Also fixes two call sites not listed in the issue: both
initializeJobsqueries inapps/schedules/src/utils.tshydrateapplication → server(102 arguments), so the cloud worker would fail to initialize schedules and volume backups on startup.Verified against a local dev database: all five fixed queries execute correctly, while the previous shape still reproduces the 54023 failure.