khalibloo
khalibloo
Explore posts from servers
RRailway
Created by khalibloo on 2/29/2024 in #✋|help
NodeJS Nixpack - GLIBC_2.38 not found
pnpm install fails on some packages such as @sentry/cli and aws-crt while running their install scripts. It says /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.38' not found. Here is a snippet from the logs ``` #10 11.74 Progress: resolved 1554, reused 0, downloaded 1553, added 1554, done #10 12.22 .../[email protected]/node_modules/aws-crt install$ node ./scripts/install.js #10 12.28 .../node_modules/@sentry/cli install$ node ./scripts/install.js #10 12.34 .../[email protected]/node_modules/aws-crt install: node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.38' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6) #10 12.34 .../[email protected]/node_modules/aws-crt install: node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.36' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6) #10 12.34 .../[email protected]/node_modules/aws-crt install: Failed #10 12.34  ELIFECYCLE  Command failed with exit code 1. #10 12.34 .../node_modules/@sentry/cli install: node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.38' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6) #10 12.34 .../node_modules/@sentry/cli install: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6) #10 12.34 .../node_modules/@sentry/cli install: Failed #10 ERROR: process "/bin/bash -ol pipefail -c pnpm i --frozen-lockfile" did not complete successfully: exit code: 1 ```
11 replies
RRefine
Created by eastern-cyan on 11/30/2022 in #ask-any-question
Invalidating the service worker cache
After using useUpdate to modify a resource, the list view resends the GET request, but it still gets intercepted by the service worker, causing the UI to remain unchanged until I perform a full refresh. Even manually using useInvalidate doesn't get around the service worker. Any ideas on how to work around this?
5 replies