| 19 Jan 2025 |
macaroniskengz | Redacted or Malformed Event | 02:34:45 |
symphorien | is it possible to use the !secret syntax in the config option of the home assistant nixos module ? | 15:22:58 |
@hexa:lossy.network | yep | 15:23:10 |
@hexa:lossy.network | if you pass a string of the format "!secret foobar" then we'll unescape it for you | 15:23:35 |
symphorien | ah there is a special case | 15:23:45 |
symphorien | thank you | 15:23:48 |
@hexa:lossy.network | I call it post-processing 😄 | 15:24:08 |
@hexa:lossy.network | sed -i -e "s/'\!\([a-z_]\+\) \(.*\)'/\!\1 \2/;s/^\!\!/\!/;" $out
| 15:24:25 |
symphorien | beautiful | 15:25:40 |
| @number42:matrix.rezel.net joined the room. | 16:18:01 |
| 20 Jan 2025 |
@hexa:lossy.network | spacekitteh: https://discourse.nixos.org/t/thread-border-router-on-nixos/57909 https://github.com/NixOS/nixpkgs/pull/332296 | 02:02:36 |
@hexa:lossy.network | wondering if you planned to upstream what you have | 02:02:46 |
@hexa:lossy.network | cc newam | 02:03:14 |
@hexa:lossy.network | the module spacekitteh created | 02:04:22 |
spacekitteh | @hexa:lossy.network: I do plan to, it's still WIP tho | 02:32:43 |
@hexa:lossy.network | feel free to appear in that discourse thread then | 02:33:13 |
@hexa:lossy.network | maybe more eyes will do good, given that otbr seems to be so complex | 02:33:27 |
spacekitteh | I'll try to have a look at it this evening | 02:34:36 |
ibizaman | What prompted you to add auth_oidc to home-assistant? Just for the sake of it or do you have plans of integrating oauth into the NixOS module? I'm curious because I planned to get to it (in the future, someday). | 22:24:20 |
ibizaman | * What prompted you to add auth_oidc to nixpkgs? Just for the sake of it or do you have plans of integrating oauth into the NixOS module? I'm curious because I planned to get to it (in the future, someday). | 22:24:31 |
@hexa:lossy.network | maybe I want to play with it | 22:26:31 |
| 22 Jan 2025 |
Ekleog | This is interesting; I'm hitting the same issue that custom components seem not to be loaded; but I don't actually have the fourth "manage resources" line when clicking this button (assuming it's in the top-right corner when editing the dashboard).
Did something change with 2025.01.2? | 02:21:40 |
| 21 Jan 2025 |
| oak 🏳️🌈♥️ changed their profile picture. | 22:36:02 |
| 22 Jan 2025 |
@hexa:lossy.network | @leo:gaspard.ninjaWhat is your Lovelace config in nix? | 07:04:02 |
| 21 Jan 2025 |
| oak 🏳️🌈♥️ changed their profile picture. | 22:37:29 |
| 22 Jan 2025 |
K900 | Works fine here FWIW | 07:06:23 |
K900 | The custom components that is | 07:06:27 |
K900 | At least on mobile though I really don't think it should matter | 07:07:04 |
uep | staging merge blew up whisper | 10:33:32 |
uep | trace: evaluation warning: getExe: Package "wyoming-faster-whisper-2.4.0" does not have the meta.mainProgram attribute. We'll assume that the main program has the same name for now, but this behavior is deprecated, because it leads to surprising errors when the assumption does not hold. If the package has a main program, please set `meta.mainProgram` in its definition to make this warning go away. Otherwise, if the package does not have a main program, or if you don't control its definition, use getExe' to specify the name to the program, such as lib.getExe' foo "bar".
error:
… while calling the 'head' builtin
at /nix/store/irknf7niks2djxz4csh7sr44wwrs082y-source/lib/attrsets.nix:1574:11:
1573| || pred here (elemAt values 1) (head values) then
1574| head values
| ^
1575| else
… while evaluating the attribute 'value'
at /nix/store/irknf7niks2djxz4csh7sr44wwrs082y-source/lib/modules.nix:846:9:
845| in warnDeprecation opt //
846| { value = addErrorContext "while evaluating the option `${showOption loc}':" value;
| ^
847| inherit (res.defsFinal') highestPrio;
(stack trace truncated; use '--show-trace' to show the full trace)
error: expected a list but found the partially applied built-in function 'concatMap': «partially applied primop concatMap»
| 10:34:14 |