Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[24.11] update nixpkgs 2024 12 10 #1196

Merged

Conversation

osnyx
Copy link
Member

@osnyx osnyx commented Dec 10, 2024

@flyingcircusio/release-managers

Release process

  • targets a development branch for an unreleased platform version -> fewer QA requirements
  • gitlab asset building os going to be fixed later on

PhilTaken and others added 8 commits December 4, 2024 10:15
The default monitoring check relied on varnish to run on a specific
address.
Since this address can be changed, the Sensu check needs to be adjusted
to correctly infer the host and port that varnish is running on

The listen address can only be reliably queried at runtime
(without reimplementing Varnishd's command line parsing logic in nix)
hence why multiple checks - one per address - are not possible.
This action is part of the update-nixpkgs workflow in fc-nixos-release-tools.
It requires access to this repository's events, so it needs to be located here.

PL-133100
This is to support the update-nixpkgs workflow without a devenv shell.
…-flake

move package-, version update scripts to flake apps
Pull upstream NixOS changes, security fixes and package updates:

- cacert: 3.104 -> 3.107
- cacert: 3.104 -> 3.107, (#358220)
- chromium: remove ofborg maintainer ping workaround, use CODEOWNERS
- chromium: resolve ref to rev for blink version string
- curl: backport netrc regression fix
- curl: backport netrc regression fix (#356660)
- curl: backport other netrc regression fix
- github-runner: fix test execution on build
- gitlab-runner: Try fixing #356717
- gitlab: 17.3.7 -> 17.5.2
- keycloak: 26.0.5 -> 26.0.6
- mastodon: 4.3.1 -> 4.3.2
- matrix-synapse: 1.119.0 -> 1.120.2
- nginx: fix compatibility with zlib-ng
- nodejs_20: 20.18.0 -> 20.18.1
- nss_latest: 3.106 -> 3.107
- openssh: add initrd-network-ssh nixos test to passthru.tests
- percona-server: 8.4.0-1 -> 8.4.2-2
- php81: 8.1.30 -> 8.1.31
- php82: 8.2.25 -> 8.2.26
- php83: 8.3.13 -> 8.3.14
- postgresql: drop build-time dependency on GHC
- postgresql_16: 16.4 -> 16.5
- ruby_3_2: 3.2.5 -> 3.2.6
- sudo: 1.9.16 -> 1.9.16p2
- systemd: 256.7 -> 256.8
- systemd: revert boot-breaking systemd-boot change
- xorg.libX11: Fix spurious Xerror when running synchronized
- xorg.libX11: Fix spurious Xerror when running synchronized (#356033)

PL-os-2411update-20241210
@osnyx osnyx changed the base branch from fc-24.05-dev to fc-24.11-dev December 10, 2024 19:55
@ctheune
Copy link
Member

ctheune commented Dec 11, 2024

Da ist das gitlab-assets mit nem OOM ausgestiegen?



<--- Last few GCs --->

[2348:0x30a2680]  1948800 ms: Scavenge (reduce) 4488.6 (5150.8) -> 4488.6 (5151.1) MB, 4.57 / 0.00 ms  (average mu = 0.269, current mu = 0.257) allocation failure; 
[2348:0x30a2680]  1948806 ms: Scavenge (reduce) 4489.1 (5151.1) -> 4489.1 (5151.3) MB, 4.86 / 0.00 ms  (average mu = 0.269, current mu = 0.257) allocation failure; 
[2348:0x30a2680]  1948812 ms: Scavenge (reduce) 4489.5 (5151.3) -> 4489.4 (5151.6) MB, 4.87 / 0.00 ms  (average mu = 0.269, current mu = 0.257) allocation failure; 


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0xab52d0 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [webpack]
 2: 0xe7ea10 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack]
 3: 0xe7edf4 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack]
 4: 0x10ae4b7  [webpack]
 5: 0x10ae549  [webpack]
 6: 0x10c60e0 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [webpack]
 7: 0x10c6c17 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack]
 8: 0x109fc97 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
 9: 0x10a08d4 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
10: 0x107ec34 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [webpack]
11: 0x1070e2b v8::internal::FactoryBase<v8::internal::Factory>::NewRawTwoByteString(int, v8::internal::AllocationType) [webpack]
12: 0x1546c05 v8::internal::IncrementalStringBuilder::Extend() [webpack]
13: 0x11ed524 v8::internal::JsonStringifier::SerializeString(v8::internal::Handle<v8::internal::String>) [webpack]
14: 0x11ef26b  [webpack]
15: 0x11f29ea v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<true>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [webpack]
16: 0x11efe73  [webpack]
17: 0x11f0406 v8::internal::JsonStringifier::Stringify(v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>) [webpack]
18: 0x11f04da v8::internal::JsonStringify(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>) [webpack]
19: 0xf17430 v8::internal::Builtin_JsonStringify(int, unsigned long*, v8::internal::Isolate*) [webpack]
20: 0x18f7df6  [webpack]
error Command failed with signal "SIGABRT".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Unable to compile webpack production bundle.

@osnyx osnyx marked this pull request as ready for review December 11, 2024 09:30
@osnyx osnyx merged commit 0dcdf86 into fc-24.11-dev Dec 11, 2024
1 check failed
@osnyx osnyx deleted the PL-os-2411update-20241210-update-nixpkgs-2024-12-10 branch December 11, 2024 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants