!BNzCLICNIgvxBJqcKM:nixos.dev

nixos.dev meta discussions

49 Members
Make sure your GitHub Organisation membership is public as otherwise the login will not work.7 Servers

Load older messages


SenderMessageTime
22 Nov 2021
@andir:nixos.devAndreas Rammhold
In reply to @nixinator:nixos.dev
anyone having trouble joining rooms, specifically https://chat.nixos.dev/#/room/#dream2nix:nixos.org
works for me. Anything specific that doesn't work for you?
07:03:44
@mic92:nixos.dev@mic92:nixos.devI am also in this channel without issues.09:06:47
28 Nov 2021
@nixinator:nixos.devnixinatorit is now resolved. with a web refresh22:28:16
3 Dec 2021
@qyliss:fairydust.space@qyliss:fairydust.space joined the room.11:51:31
4 Dec 2021
@lassulus:nixos.dev@lassulus:nixos.devthere was snow falling in my element web18:13:38
@lassulus:nixos.dev@lassulus:nixos.devwhere is that coming from? is that just a feature everybody got?18:13:56
@0x4a6f:matrix.org[0x4A6F]with `/snowfall`18:14:54
@lassulus:nixos.dev@lassulus:nixos.devtesting18:15:18
@lassulus:nixos.dev@lassulus:nixos.devso everybody gets snowfall then? :D18:15:41
@lassulus:nixos.dev@lassulus:nixos.devweird features18:15:46
@andi:kack.itandi-test18:19:49
@andi:kack.itandi-Wow18:19:53
@0x4a6f:matrix.org[0x4A6F]I've turned it off. -> Show chat effects (animations when receiving e.g. confetti)18:33:16
13 Dec 2021
@lourkeur:nixos.dev@lourkeur:nixos.devElement Web needs a security update on the server side https://matrix.org/blog/2021/12/13/disclosure-buffer-overflow-in-libolm-and-matrix-js-sdk15:37:46
@andi:kack.itandi-Do we have a PR in nixpkgs already?15:48:44
@andi:kack.itandi-Doesn't look like it15:49:53
@andi:kack.itandi- We are just using their binary distribution anyway: https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/instant-messengers/element/element-web.nix#L16 /o\ 15:52:53
@andi:kack.itandi-I'll spent a few minutes on a "proper" source build before just bumping the version and hashsum...15:58:26
@lourkeur:nixos.dev@lourkeur:nixos.devOnly an issue so far https://github.com/NixOS/nixpkgs/issues/15055216:02:16
@andi:kack.itandi-How does anyone us Nix >=2.4... it is utterly useless. The build logs are silent by default even on the "legacy" (stable) commands... Yesterday it was unable to verify store integrity as it is too strict while doing that and tripped over itself.... Please hold the line while I scream for a second before continuing with the work.16:09:49
@andi:kack.itandi- instead of it streaming me the build log I've to use the nix log thing which doesn't work well with tools that constantly rewrite the same line. 😱 16:11:26
@andi:kack.itandi-
Downloading Jitsi script                                                                                                                                                                                                                                                                                                                                                              (node:122) UnhandledPromiseRejectionWarning: FetchError: request to https://jitsi.riot.im/libs/external_api.min.js failed, reason: getaddrinfo ENOTFOUND jitsi.riot.im                                                                                                                                                                                                                    at ClientRequest.<anonymous> (/build/source/node_modules/node-fetch/lib/index.js:1483:11)                                                                                                                                                                                                                                                                                             at ClientRequest.emit (events.js:400:28)                                                                                                                                                                                                                                                                                                                                              at TLSSocket.socketErrorListener (_http_client.js:475:9)                                                                                                                                                                                                                                                                                                                              at TLSSocket.emit (events.js:400:28)                                                                                                                                                                                                                                                                                                                                                  at emitErrorNT (internal/streams/destroy.js:106:8)                                                                                                                                                                                                                                                                                                                                    at emitErrorCloseNT (internal/streams/destroy.js:74:3)                                                                                                                                                                                                                                                                                                                                at processTicksAndRejections (internal/process/task_queues.js:82:21)                                                                                                                                                                                                                                                                                                              (Use `node --trace-warnings ...` to show where the warning was created)

there goes the idea of doing a proper source build.

16:12:55
@andi:kack.itandi- At least the cinny upgrade was just a npins update cinny for a new source build. 16:16:49
@andir:nixos.devAndreas RammholdDeployed a new cinny and element-web version.16:23:53
@mic92:nixos.dev@mic92:nixos.dev andi-: nix build -L is actually quite nice because it also shows the package that the log line is associated with. 16:44:40
@mic92:nixos.dev@mic92:nixos.dev I think nix build -L should be default because it's better than both nix build and nix-build 16:45:09
@andi:kack.itandi-but if I build a single attribute and a single derivation I'd like to be able to see the log like it used to be.16:45:14
@mic92:nixos.dev@mic92:nixos.devYou can also use it for a single derivation, but often enough even a single derivation can trigger the build of another derivation i.e. fetching source16:45:49
@andi:kack.itandi-And I am no longer willing to open issues on the Nix repo or PRs. It just doesn't have any impact on the development.16:45:56
@mic92:nixos.dev@mic92:nixos.devI this one was quite needed: https://github.com/NixOS/nix/pull/574716:46:53

Show newer messages


Back to Room ListRoom Version: 6