| 30 Jan 2024 |
 Lily Foster | ohh yeah it did fail to load config | 00:46:03 |
| Lily Foster | i can't read. am tired | 00:46:08 |
 hexa | ❯ CRYPTPAD_CONFIG=$(pwd)/config/config.js ./result/bin/cryptpad-server
/nix/store/h0iylf7szzwl1yvpcxgs350w5ribv12a-cryptpad-5.6.0/lib/node_modules/cryptpad/lib/log.js:102
throw err;
^
[Error: EROFS: read-only file system, mkdir '/nix/store/h0iylf7szzwl1yvpcxgs350w5ribv12a-cryptpad-5.6.0/lib/node_modules/cryptpad/data'] {
errno: -30,
code: 'EROFS',
syscall: 'mkdir',
path: '/nix/store/h0iylf7szzwl1yvpcxgs350w5ribv12a-cryptpad-5.6.0/lib/node_modules/cryptpad/data'
}
Node.js v20.11.0
| 00:46:14 |
| hexa | it uses relative paths through the example config | 00:46:47 |
| hexa | and relative always mean relative to the package, not to my cwd | 00:47:01 |
| hexa | and no common base path o_O | 00:47:45 |
| Lily Foster | what's in your config.js? | 00:48:00 |
| hexa | https://github.com/cryptpad/cryptpad/blob/5.6.0/config/config.example.js | 00:48:21 |
| hexa | all default for now | 00:48:24 |
| Lily Foster | ohhhh i see what you're saying | 00:48:25 |
| Lily Foster | yeah | 00:48:32 |
| Lily Foster | that, uh, does sound silly | 00:48:40 |
| hexa | ok, it is up, doesn't even log startup things | 00:52:05 |
| hexa | wild. | 00:52:13 |
| hexa | https://github.com/NixOS/nixpkgs/pull/251687 hmm | 00:53:34 |
| hexa | I think I am now uniquely qualified to review that existing PR | 00:53:46 |
| Lily Foster | In reply to @hexa:lossy.network
and relative always mean relative to the package, not to my cwd i can't tell how or why this would be the case, by some quick looking through the code on mobile 👀 | 00:55:41 |
| hexa | ugh, mobile 😄 | 00:55:54 |
| hexa | don' | 00:55:55 |
| hexa | * don't do that | 00:55:57 |
| Lily Foster | In reply to @hexa:lossy.network
don' (it is, uh, hurting to use gh's search for this on mobile, yeah...) | 00:56:41 |
| hexa | https://github.com/NixOS/nixpkgs/pull/251687/files#diff-0484e02777f32406a41a22e3f48f96f437ec183b1d3d3f9533d67370e6fb0620R49-R63 | 00:57:30 |
| hexa | this hurts as well 😄 | 00:57:33 |
| hexa | that whole installPhase is wild | 00:58:22 |
 Marie | I can't get npm to write a non broken lockfile for me, any ideas?
I tried with npm 9.8.1, 10.2.4 and 1.4.0 on different systems and all don't add integrity and resolved fields for a few dependencies
I tried running npm-lockfile-fix but this also seems to break the lockfile | 09:32:03 |
| Marie | * I can't get npm to write a non broken lockfile for me, any ideas?
I tried with npm 9.8.1, 10.2.4 and 10.4.0 on different systems and all don't add integrity and resolved fields for a few dependencies
I tried running npm-lockfile-fix but this also seems to break the lockfile | 09:32:12 |
| Marie | I also deleted node_modules, package-lock.json and the npm cache before running npm install | 09:33:06 |
 Wanja Hentze | In reply to @marie:marie.cologne
I can't get npm to write a non broken lockfile for me, any ideas?
I tried with npm 9.8.1, 10.2.4 and 10.4.0 on different systems and all don't add integrity and resolved fields for a few dependencies
I tried running npm-lockfile-fix but this also seems to break the lockfile are these peer deps by any chance? | 10:10:23 |
| Marie | no, but the project is a workspace and the dependencies with issues seem to be used in different versions across workspace packages | 10:11:09 |
| Wanja Hentze | oh, I've seen that with workspaces too, but sadly don't remember the fix :/ | 10:18:57 |
