Skip to content

pgadmin4: 9.14 -> 9.18 - #569309

Merged
gador merged 2 commits into
NixOS:masterfrom
gador:pgadmin-9.18
Oct 12, 2026
Merged

gador merged 2 commits into
NixOS:masterfrom
gador:pgadmin-9.18

Conversation

@gador

@gador gador commented Oct 2, 2026

Copy link
Copy Markdown
Member

Long wait, due to several yarn-berry updates (mostly documented at #555729).
Release notes: https://www.pgadmin.org/docs/pgadmin4/latest/release_notes_9_18.html
Diff: pgadmin-org/pgadmin4@REL-9_14...REL-9_18
Fixes: #569095
Fixes: #553627
Closes: #533864

Things done

Signed-off-by: Florian Brandes <florian.brandes@posteo.de>
@nixpkgs-ci nixpkgs-ci Bot added 2.status: merge-bot eligible This PR can be merged by commenting "@NixOS/nixpkgs-merge-bot merge". 8.has: package (update) This PR updates a package to a newer version 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 11.by: package-maintainer This PR was created by a maintainer of all the package it changes. 9.needs: reviewer This PR currently has no reviewers requested and needs attention. labels Oct 2, 2026
@ToBinio

ToBinio commented Oct 2, 2026

Copy link
Copy Markdown
Member

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 569309
Commit: 358e8afb65e8a3084fb2767b8e9df185a0b89756


x86_64-linux

✅ 2 packages built:
  • pgadmin4-desktopmode
  • pgadmin4

@ToBinio

ToBinio commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

This very well could be me, but when trying to access pgadmin4-desktopmode via the browser, it always errors with

Content-Security-Policy: The page’s settings blocked a JavaScript eval (script-src) from being executed because it violates the following directive: “script-src 'self' 'nonce-AL_Gq2IDJ3HOaFLVjN6hSw'” (Missing 'unsafe-eval')

seems to be related to pgadmin-org/pgadmin4#10308

edit:
Based on what I can tell, this is caused by webpack not being built in production mode

using NODE_ENV=production yarn webpacker seems to fix the problem

should be enabled in production anyway
and fixes NixOS#569309 (comment)

Signed-off-by: Florian Brandes <florian.brandes@posteo.de>
@gador

gador commented Oct 2, 2026

Copy link
Copy Markdown
Member Author

This very well could be me, but when trying to access pgadmin4-desktopmode via the browser, it always errors with

Content-Security-Policy: The page’s settings blocked a JavaScript eval (script-src) from being executed because it violates the following directive: “script-src 'self' 'nonce-AL_Gq2IDJ3HOaFLVjN6hSw'” (Missing 'unsafe-eval')

seems to be related to pgadmin-org/pgadmin4#10308

edit: Based on what I can tell, this is caused by webpack not being built in production mode

using NODE_ENV=production yarn webpacker seems to fix the problem

Thanks. Please give it a try.

@ToBinio ToBinio left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nixpkgs-ci nixpkgs-ci Bot added 12.approvals: 1 This PR was reviewed and approved by one person. and removed 9.needs: reviewer This PR currently has no reviewers requested and needs attention. labels Oct 2, 2026
@alfarelcynthesis

Copy link
Copy Markdown
Contributor

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 569309
Commit: 17e20b84b7344b7afd4fb2fc9a1d3cd4b80353fe


x86_64-linux

✅ 2 packages built:
  • pgadmin4
  • pgadmin4-desktopmode

@alfarelcynthesis

Copy link
Copy Markdown
Contributor

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 569309
Commit: 17e20b84b7344b7afd4fb2fc9a1d3cd4b80353fe


x86_64-linux

❌ 2 packages failed to build:
  • pgadmin4
  • pgadmin4-desktopmode

pgadmin4
92% [0] sealing ...rocessing CopyPlugin

92% [0] sealing ...ocessing ...erPlugin
<--- Last few GCs --->

[1904:0x5555592e6000] 93333 ms: Mark-Compact 2031.4 (2062.1) -> 2025.1 (2062.6) MB, pooled: 4 MB, 834.54 / 0.00 ms (average mu = 0.187, current mu = 0.051) allocation failure; scavenge might not succeed
[1904:0x5555592e6000] 94103 ms: Mark-Compact (reduce) 2032.7 (2062.9) -> 2027.5 (2049.9) MB, pooled: 0 MB, 673.06 / 0.00 ms (+ 1.3 ms in 9 steps since start of marking, biggest step 1.1 ms, walltime since start of marking 680 ms) (average mu = 0.160,
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0x5555559c6298 [webpack]
2: 0x55555575692a node::OOMErrorHandler(char const*, v8::OOMDetails const&) [webpack]
3: 0x555555d92c08 [webpack]
4: 0x5555560a2147 [webpack]
5: 0x5555560ba61a [webpack]
6: 0x555556080d91 [webpack]
7: 0x555556052249 [webpack]
8: 0x555556614d7d [webpack]
9: 0x7fffd3e769b6

pgadmin4-desktopmode
92% [0] sealing asset processing

92% [0] sealing ...rocessing CopyPlugin

92% [0] sealing ...ocessing ...erPlugin
<--- Last few GCs --->

[2019:0x5555592e6000] 92259 ms: Mark-Compact 2024.8 (2056.8) -> 2019.1 (2076.1) MB, pooled: 0 MB, 814.17 / 0.00 ms (average mu = 0.320, current mu = 0.201) allocation failure; scavenge might not succeed
[2019:0x5555592e6000] 93229 ms: Mark-Compact (reduce) 2029.3 (2076.1) -> 2025.7 (2051.1) MB, pooled: 0 MB, 248.19 / 0.00 ms (+ 529.2 ms in 153 steps since start of marking, biggest step 6.0 ms, walltime since start of marking 852 ms) (average mu = 0.2
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0x5555559c6298 [webpack]
2: 0x55555575692a node::OOMErrorHandler(char const*, v8::OOMDetails const&) [webpack]
3: 0x555555d92c08 [webpack]
4: 0x5555560a2147 [webpack]
5: 0x5555560ba61a [webpack]
6: 0x555555fd2ec5 [webpack]
7: 0x55555661486f [webpack]
8: 0x7fffd3e769b6

@alfarelcynthesis

Copy link
Copy Markdown
Contributor

The failures are consistent on my weaker hardware (a laptop), with the following OOM error:

error: builder for '/nix/store/j4big61zdmzr5w1r83j5gypprnk5wsqy-pgadmin-9.18.drv' failed with exit code 1;
       last 25 log lines:
       > ➤ YN0000: │ ttf2woff2@npm:4.0.5 STDERR gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
       > ➤ YN0000: │ ttf2woff2@npm:4.0.5 STDERR gyp info ok
       > ➤ YN0000: └ Completed in 23s 854ms
       > ➤ YN0000: · Done with warnings in 25s 108ms
       > finished yarnBerryConfigHook
       > Browserslist: browsers data (caniuse-lite) is 7 months old. Please run:
       >   npx update-browserslist-db@latest
       >   Why you should do it regularly: https://github.com/browserslist/update-db#readme

       > <--- Last few GCs --->
       >
       > [1904:0x5555592e6000]    93333 ms: Mark-Compact 2031.4 (2062.1) -> 2025.1 (2062.6) MB, pooled: 4 MB, 834.54 / 0.00 ms  (average mu = 0.187, current mu = 0.051) allocation failure; scavenge might not succeed
       > [1904:0x5555592e6000]    94103 ms: Mark-Compact (reduce) 2032.7 (2062.9) -> 2027.5 (2049.9) MB, pooled: 0 MB, 673.06 / 0.00 ms  (+ 1.3 ms in 9 steps since start of marking, biggest step 1.1 ms, walltime since start of marking 680 ms) (average mu = 0.160,
       > FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
       > ----- Native stack trace -----
       >
       >  1: 0x5555559c6298  [webpack]
       >  2: 0x55555575692a node::OOMErrorHandler(char const*, v8::OOMDetails const&) [webpack]
       >  3: 0x555555d92c08  [webpack]
       >  4: 0x5555560a2147  [webpack]
       >  5: 0x5555560ba61a  [webpack]
       >  6: 0x555556080d91  [webpack]
       >  7: 0x555556052249  [webpack]
       >  8: 0x555556614d7d  [webpack]
       >  9: 0x7fffd3e769b6

This failure may not be relevant/may already be present in previous versions.
The system does still have memory remaining (~11/14.5GiB actual RAM used, with SWAP space remaining as well).

If this is irrelevant, feel free to disregard.

@gador

gador commented Oct 4, 2026

Copy link
Copy Markdown
Member Author

The failures are consistent on my weaker hardware (a laptop), with the following OOM error:

error: builder for '/nix/store/j4big61zdmzr5w1r83j5gypprnk5wsqy-pgadmin-9.18.drv' failed with exit code 1;
       last 25 log lines:
       > ➤ YN0000: │ ttf2woff2@npm:4.0.5 STDERR gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
       > ➤ YN0000: │ ttf2woff2@npm:4.0.5 STDERR gyp info ok
       > ➤ YN0000: └ Completed in 23s 854ms
       > ➤ YN0000: · Done with warnings in 25s 108ms
       > finished yarnBerryConfigHook
       > Browserslist: browsers data (caniuse-lite) is 7 months old. Please run:
       >   npx update-browserslist-db@latest
       >   Why you should do it regularly: https://github.com/browserslist/update-db#readme

       > <--- Last few GCs --->
       >
       > [1904:0x5555592e6000]    93333 ms: Mark-Compact 2031.4 (2062.1) -> 2025.1 (2062.6) MB, pooled: 4 MB, 834.54 / 0.00 ms  (average mu = 0.187, current mu = 0.051) allocation failure; scavenge might not succeed
       > [1904:0x5555592e6000]    94103 ms: Mark-Compact (reduce) 2032.7 (2062.9) -> 2027.5 (2049.9) MB, pooled: 0 MB, 673.06 / 0.00 ms  (+ 1.3 ms in 9 steps since start of marking, biggest step 1.1 ms, walltime since start of marking 680 ms) (average mu = 0.160,
       > FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
       > ----- Native stack trace -----
       >
       >  1: 0x5555559c6298  [webpack]
       >  2: 0x55555575692a node::OOMErrorHandler(char const*, v8::OOMDetails const&) [webpack]
       >  3: 0x555555d92c08  [webpack]
       >  4: 0x5555560a2147  [webpack]
       >  5: 0x5555560ba61a  [webpack]
       >  6: 0x555556080d91  [webpack]
       >  7: 0x555556052249  [webpack]
       >  8: 0x555556614d7d  [webpack]
       >  9: 0x7fffd3e769b6

This failure may not be relevant/may already be present in previous versions. The system does still have memory remaining (~11/14.5GiB actual RAM used, with SWAP space remaining as well).

If this is irrelevant, feel free to disregard.

Good question about the relevance. I haven't seen this error before.
Right now I would argue that if hydra builds it, it doesn't matter for weaker hardware (and my hardware isn't powerful by any means).
If this continues to happen we'll need to investigate further

Relms12345 pushed a commit to Relms12345/nixpkgs that referenced this pull request Oct 8, 2026
should be enabled in production anyway
and fixes NixOS#569309 (comment)

Signed-off-by: Florian Brandes <florian.brandes@posteo.de>
Relms12345 pushed a commit to Relms12345/nixpkgs that referenced this pull request Oct 10, 2026
should be enabled in production anyway
and fixes NixOS#569309 (comment)

Signed-off-by: Florian Brandes <florian.brandes@posteo.de>
@ToBinio

ToBinio commented Oct 11, 2026

Copy link
Copy Markdown
Member

Hi, is anything blocking this from being merged?
I think we waited long enough for people to review

@gador
gador added this pull request to the merge queue Oct 12, 2026
@gador

gador commented Oct 12, 2026

Copy link
Copy Markdown
Member Author

Sure, I don't see anything blocking it and I believe there was enough time for feedback

Merged via the queue into NixOS:master with commit bc08f5a Oct 12, 2026
29 checks passed
@gador
gador deleted the pgadmin-9.18 branch October 12, 2026 07:07
Relms12345 pushed a commit to Relms12345/nixpkgs that referenced this pull request Oct 12, 2026
Signed-off-by: Florian Brandes <florian.brandes@posteo.de>

pgadmin4: use NODE_ENV production

should be enabled in production anyway
and fixes NixOS#569309 (comment)

Signed-off-by: Florian Brandes <florian.brandes@posteo.de>
Relms12345 pushed a commit to Relms12345/nixpkgs that referenced this pull request Oct 12, 2026
Signed-off-by: Florian Brandes <florian.brandes@posteo.de>

pgadmin4: use NODE_ENV production

should be enabled in production anyway
and fixes NixOS#569309 (comment)

Signed-off-by: Florian Brandes <florian.brandes@posteo.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2.status: merge-bot eligible This PR can be merged by commenting "@NixOS/nixpkgs-merge-bot merge". 8.has: package (update) This PR updates a package to a newer version 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 11.by: package-maintainer This PR was created by a maintainer of all the package it changes. 12.approvals: 1 This PR was reviewed and approved by one person.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build failure: pgadmin4-desktopmode Update Request: pgadmin4 9.14 → 9.17

3 participants