| 22 Nov 2021 |
 Andreas 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 |
 Jörg Thalheim | I am also in this channel without issues. | 09:06:47 |
| 28 Nov 2021 |
 nixinator | it is now resolved. with a web refresh | 22:28:16 |
| 3 Dec 2021 |
|  Alyssa Ross joined the room. | 11:51:31 |
| 4 Dec 2021 |
 lassulus | there was snow falling in my element web | 18:13:38 |
| lassulus | where is that coming from? is that just a feature everybody got? | 18:13:56 |
 [0x4A6F] | with `/snowfall` | 18:14:54 |
| lassulus | testing | 18:15:18 |
| lassulus | so everybody gets snowfall then? :D | 18:15:41 |
| lassulus | weird features | 18:15:46 |
 andi- | test | 18:19:49 |
| andi- | Wow | 18:19:53 |
| [0x4A6F] | I've turned it off. -> Show chat effects (animations when receiving e.g. confetti) | 18:33:16 |
| 13 Dec 2021 |
 lourkeur (nix btw) | Element Web needs a security update on the server side https://matrix.org/blog/2021/12/13/disclosure-buffer-overflow-in-libolm-and-matrix-js-sdk | 15:37:46 |
| andi- | Do we have a PR in nixpkgs already? | 15:48:44 |
| andi- | Doesn't look like it | 15:49:53 |
| andi- | 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- | I'll spent a few minutes on a "proper" source build before just bumping the version and hashsum... | 15:58:26 |
| lourkeur (nix btw) | Only an issue so far https://github.com/NixOS/nixpkgs/issues/150552 | 16:02:16 |
| andi- | 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- | 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- | 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- | At least the cinny upgrade was just a npins update cinny for a new source build. | 16:16:49 |
| Andreas Rammhold | Deployed a new cinny and element-web version. | 16:23:53 |
| Jörg Thalheim | andi-: nix build -L is actually quite nice because it also shows the package that the log line is associated with. | 16:44:40 |
| Jörg Thalheim | I think nix build -L should be default because it's better than both nix build and nix-build | 16:45:09 |
| andi- | 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 |
| Jörg Thalheim | You 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 source | 16:45:49 |
| andi- | 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 |
| Jörg Thalheim | I this one was quite needed: https://github.com/NixOS/nix/pull/5747 | 16:46:53 |
