-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
keycloak: CRC errors on keycloak 17.0.1 #170539
Comments
Hm, I'm able to reproduce the tests, trying on the target server to understand better. EDIT: can reproduce the test on the server too… |
Minimized the issue to the missing parameters This can be reproduced with: https://clbin.com/bMYYg by doing |
Here's a more complete stacktrace with
|
I'm not able to reproduce this in |
@talyz I confirm I still run into this bug. |
Okay, with what nixpkgs commit? Can you update the reproducer config to trigger the failure once again? |
I will try to minimize the issue again, but I tried quickly, to no avail recently so for now, I will try the zlib patch. |
Okay, it does look like the zlib patch fixes the issue, though I cannot build the closure, I have failures on… some derivation, which is difficult to read due to the way nix-build output logs. FIX: that was a temporary issue due to resource exhaustion, it completely fixes my issue. |
Okay, great! Can you prepare a PR applying the patch? |
Starting zlib 1.2.12, CRC validation has became stricter. This broke Keycloak ≥ 17 in certain situations, for details, see: - keycloak/keycloak#11316 ; - NixOS#170539 This patch makes the CRC validation comprehensive with respect to older or already existing checksums out there.
Starting zlib 1.2.12, CRC validation has became stricter. This broke Keycloak ≥ 17 in certain situations, for details, see: - keycloak/keycloak#11316 ; - #170539 This patch makes the CRC validation comprehensive with respect to older or already existing checksums out there. (cherry picked from commit 8335c46)
Starting zlib 1.2.12, CRC validation has became stricter. This broke Keycloak ≥ 17 in certain situations, for details, see: - keycloak/keycloak#11316 ; - #170539 This patch makes the CRC validation comprehensive with respect to older or already existing checksums out there. (cherry picked from commit 8335c46)
Closed in #177053 and its backports variants. |
Starting zlib 1.2.12, CRC validation has became stricter. This broke Keycloak ≥ 17 in certain situations, for details, see: - keycloak/keycloak#11316 ; - NixOS#170539 This patch makes the CRC validation comprehensive with respect to older or already existing checksums out there.
Starting zlib 1.2.12, CRC validation has became stricter. This broke Keycloak ≥ 17 in certain situations, for details, see: - keycloak/keycloak#11316 ; - NixOS#170539 This patch makes the CRC validation comprehensive with respect to older or already existing checksums out there.
Starting zlib 1.2.12, CRC validation has became stricter. This broke Keycloak ≥ 17 in certain situations, for details, see: - keycloak/keycloak#11316 ; - NixOS#170539 This patch makes the CRC validation comprehensive with respect to older or already existing checksums out there.
Starting zlib 1.2.12, CRC validation has became stricter. This broke Keycloak ≥ 17 in certain situations, for details, see: - keycloak/keycloak#11316 ; - NixOS#170539 This patch makes the CRC validation comprehensive with respect to older or already existing checksums out there.
Starting zlib 1.2.12, CRC validation has became stricter. This broke Keycloak ≥ 17 in certain situations, for details, see: - keycloak/keycloak#11316 ; - NixOS#170539 This patch makes the CRC validation comprehensive with respect to older or already existing checksums out there.
Describe the bug
It is impossible to enable Keycloak ≥ 17.0.1 at the moment with the NixOS module, as the
confFile
seems to introduce CRC errors after Quarkus augmentation process.Steps To Reproduce
Steps to reproduce the behavior:
services.keycloak.enable = true;
nixos-rebuild switch
Expected behavior
Building Keycloak with the configuration file should not introduce CRC errors.
Screenshots
is quite precise.
Additional context
This might be related to some JRE runtimes issues with some precise Java versions, I'm trying the "default" one on nixpkgs-unstable-small and adoptjdk-open-jre (v11), and will try more in the future.
Notify maintainers
@talyz
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Not relevant to this problem as this is on a target server, the right nixpkgs revision is:
7f4a8f37d4621b27fc0c4eeb3880ecf1cb055371
The text was updated successfully, but these errors were encountered: