jiebi/CodeConvo huggingface dataset:
Code change:
wants = [ "network-online.target" ]; after = [ "network-online.target" ]; environment = { <del> STRONGSWAN_CONF = strongswanConf { inherit setup connections ca secretsFile managePlugins enabledPlugins; }; </del> <ins> STRONGSWAN_CONF = strongswanConf { inherit setup connections ca managePlugins enabledPlugins; secretsFile = "/etc/ipsec.secrets"; }; </ins> }; serviceConfig = { ExecStart  = "${pkgs.strongswan}/sbin/ipsec start --nofork";

Related discussion:
text: 111 charon[2059]: 04[ENC] generating INFORMATIONALV1 request [ N(INVALKE) ] charon[2059]: 04[NET] sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (56 bytes) NetworkManager[2277]: initiating Main Mode IKESA -ebef-4658-8991-[1] to 123.111.111.111 NetworkManager[2277]: generating IDPROT request 0 [ SA V V V V V ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (304 bytes) NetworkManager[2277]: received packet: from 123.111.111.111[500] to 192.168.1.11[500] (204 bytes) NetworkManager[2277]: parsed IDPROT response 0 [ SA V V V V V V ] NetworkManager[2277]: received NAT-T (RFC 3947) vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-03 vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-02n vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-02 vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-00 vendor ID NetworkManager[2277]: received DPD vendor ID NetworkManager[2277]: selected proposal: IKE:AESCBC128/HMACSHA196/PRFHMACSHA1/MODP2048 NetworkManager[2277]: generating IDPROT request 0 [ KE No NAT-D NAT-D ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (372 bytes) NetworkManager[2277]: received packet: from 123.111.111.111[500] to 192.168.1.11[500] (356 bytes) NetworkManager[2277]: parsed IDPROT response 0 [ KE No NAT-D NAT-D ] NetworkManager[2277]: no shared key found for 192.168.1.11 - 123.111.111.
Code change:
wants = [ "network-online.target" ]; after = [ "network-online.target" ]; environment = { <del> STRONGSWAN_CONF = strongswanConf { inherit setup connections ca secretsFile managePlugins enabledPlugins; }; </del> <ins> STRONGSWAN_CONF = strongswanConf { inherit setup connections ca managePlugins enabledPlugins; secretsFile = "/etc/ipsec.secrets"; }; </ins> }; serviceConfig = { ExecStart  = "${pkgs.strongswan}/sbin/ipsec start --nofork";

Related discussion:
text: 111 NetworkManager[2277]: generating INFORMATIONALV1 request [ N(INVALKE) ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (56 bytes) NetworkManager[2277]: establishing connection '-ebef-4658-8991-' failed NetworkManager[2283]: Stopping strongSwan IPsec. charon[2059]: 00[DMN] signal of type SIGINT received. Shutting down ipsecstarter[2058]: child 2059 (charon) has quit (exit code 0) ipsecstarter[2058]: ipsecstarter[2058]: charon stopped after 200 ms ipsecstarter[2058]: ipsec starter stopped nm-l2tp-service[2039]: gdbusmethodinvocationtake_error: assertion 'error != NULL' failed NetworkManager[954]: <warn[.6803] vpn-connection[0x24c60a0,-ebef-4658-8991-,"my-l2tp-vpn",0]: VPN connection: failed to connect: 'Message recipient disconnected from message bus without replying' .nm-applet-wrap[1470]: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files </pre</code</detailsRunning the following command fixed my error and allowed me to connect: The networking part of my only has .
This still appears relevant in 21.11. Adding this (as mentioned above) to my config appears to get an L2TP and IPSec VPN working with NetworkManager:
Still relevant in 22.05. I am confirming that with a clean install, trying to set up L2TP/IPsec VPNs fail with the following indicator: fixed the issue for me straight away as well.
Fix in
Code change:
clang_38 = llvmPackages_38.clang; clang_37 = llvmPackages_37.clang; clang_35 = wrapCC llvmPackages_35.clang; <del> clang_34 = wrapCC llvmPackages_34.clang; </del> <ins> clang_34 = (wrapCC llvmPackages_34.clang).override { # Default cc-wrapper's hardening flags don't work with clang-3.4, # so just remove it entirely for this wrapper. extraBuildCommands = '' :> $out/nix-support/add-hardening.sh ''; }; </ins> clang-tools = callPackage ../development/tools/clang-tools { };

Related discussion:
text: Hardening gives old Clang flags that it cannot handle and fails. A same problem, I imagine, would arise with old GCC versions. A possible solution is to list somewhere what hardening methods are supported and use the list when deciding what hardening to apply. For example: a file : an error. Nixpkgs version: (run ) Sandboxing enabled: (run ) yes
Code change:
version = "0.2.0"; sha256  = "0ic5b9djhnb1bs2bz3zdprgy3r55dng09xgc4d9l9fyp85g2amaz"; }; <ins> wavefront = { owner   = "spaceapegames"; repo    = "terraform-provider-wavefront"; version = "2.1.0"; sha256  = "1ir2wkg5mfng7h5544kar1arkjb5ffjhki5qr25a5x0rpwlg99sx"; }; </ins> }

Related discussion:
text: Project description Wavefront is VMWare product and, per their website, is an "Enterprise-grade cloud monitoring and analytics at over 4 million data points per second." The service can be provisioned via Terraform -- there's an OS Terraform provider available here: It should be included amongst the set of existing Terraform providers that already contains. Metadata homepage URL: source URL: license: apl2 platforms: linux
Code change:
sha256 = "0gha8dfdf54rx8fv3yfikbgdg6lqq6l883lhg7q68ybvkjx9bwbs"; }; <del> buildInputs = [ gtk3 ibus libhangul python3 ]; </del> <ins> patches = [ (substituteAll { src = ./fix-paths.patch; libhangul = "${libhangul}/lib/libhangul.so.1"; }) ]; </ins> <del> nativeBuildInputs = [ intltool pkgconfig python3.pkgs.wrapPython ]; </del> <ins> nativeBuildInputs = [ intltool pkgconfig python3.pkgs.wrapPython wrapGAppsHook ]; </ins> <del> postFixup = "wrapPythonPrograms"; </del> <ins> buildInputs = [ gtk3 ibus libhangul (python3.withPackages (pypkgs: with pypkgs; [ pygobject3 (toPythonModule ibus) ])) ]; </ins> meta = with stdenv.lib; { isIbusEngine = true; <del> description  = "Ibus Hangul engine"; homepage     = https://github.com/choehwanjin/ibus-hangul; license      = licenses.gpl2; platforms    = platforms.linux; maintainers  = with maintainers; [ ericsagnes ]; </del> <ins> description = "Ibus Hangul engine"; homepage = https://github.com/choehwanjin/ibus-hangul; license = licenses.gpl2; maintainers = with maintainers; [ ericsagnes ]; platforms = platforms.linux; </ins> }; }

Related discussion:
text: In executing ibus-setup-hangul, got this error message: .nix -rebuild switch ibus-setup-hangul in a shell System: NixOS 17.03.1584. (Gorilla) Nix version: 1.11.11 Nixpkgs version: 17.03.1584. Sandboxing enabled: build-use-sandbox = false
Might be due to . What was the reason to remove from dependencies?
I think that was because I noticed that it is propagated from some other package, but looking at this now it doesn't seem to be the case. I'll investigate this today!
This seems more deep than I thought. The bug is two-fold: script is not patched as needed for Python scripts; should be propagated from . However, only its output is propagated, so it's not as a Python library. I can fix the first one but not sure what to do about the second -- maybe we should change behaviour of this propagation in some way.
The same problem appears with anthy, and directly adding the same pyEnv to buildInputs like did in ibus definitely fixes the build fails (tested with both anthy and hangul), but the python environment isn't propagated by itself.
Code change:
config = mkIf config.services.pcscd.enable { environment.etc."reader.conf".source = cfgFile; <del> environment.systemPackages = [ package.out ]; systemd.packages = [ (getBin package) ]; </del> <ins> environment.systemPackages = [ package ]; systemd.packages = [ package ]; </ins> services.pcscd.plugins = [ pkgs.ccid ];

Related discussion:
text: uses two actions and do get necessary authorization via . but these actions are not properly registed, leading to error: (It can be verified that these actions don't exist by using ) This breaks and . I tried both pcsclite 1.9.5 and 2.0.1 ending up with the same error. Steps to reproduce the behavior: and in , configure your smartcard (yubikey) to use yubikey error There actions are registered correctly and usable. Please run and paste the result. I'm using flakes (no channels). Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
correct description of your effect, i am not able to use my yubikey with gpg.
This can be solved by
this works, thanks! but this is really unintuitive, given that is already adding the package to : I am leaving this open as I believe a proper fix should be provided in the module itself.
Same issue here. It was working approx. last Dec. I don't have a specific commit hash. Adding to works for me.
Looks like a regression in () - is implying to me that polkit actions get included in the output, however: isn't included, which explains why adding to fixes the issue. Solution ideas: Add to . Not sure about this one? seems to also contain some libraries that probably don't need to be installed. Install polkit actions to instead of . IMO this one makes the most sense, especially as it seems to have been the previous behaviour before this change.
I was bitten by this when attempting to update over the weekend as well. In my case it prevented login because I use smartcards for user login which made debugging difficult due to the number of reboots required. I tend to agree with that going back to having the polkit actions file in the output instead of makes the most sense. That will mean that of the pcsc module will again result in the polkit action file being to the system configuration.
Cc: ()
I also think the location should be fine, the files are also there.
I ran into this issue when I couldn't access my yubikey anymore via pcsc for commits. The above solution worked for me.
Code change:
config = mkIf config.services.pcscd.enable { environment.etc."reader.conf".source = cfgFile; <del> environment.systemPackages = [ package.out ]; systemd.packages = [ (getBin package) ]; </del> <ins> environment.systemPackages = [ package ]; systemd.packages = [ package ]; </ins> services.pcscd.plugins = [ pkgs.ccid ];

Related discussion:
text: I'm going to add some comments for SEO so this is easier to find
I think you have found the right culprit that caused the issue, but I suppose the issue has more to do with the itself, where it only includes if . This has been rectified in from what it seems. For now the proper solution seems to enabling polkit with .
I think that makes more sense based on the existing file structure but maybe we just switch bin to out, so it is the default and move the libs to lib instead of being in out.
I've created to make the outputs a lot more expected by moving the udev file and the systemd service to the out output and the libraries to the lib output: I didn't test it yet, so it is still in draft. If someone could verify that it doesn't break security keys again, that would be great and then please undraft it, otherwise I do it in the evening.
I do not think I can fully test this due to the amount of rebuilds, so please chime in for reviews and find the one mistake I might have done (which I hope I didn't)
Tried to build but it fails on my machine:
I've xdist to dulwich here . Let me see if we can just disable some tests as a speed up from 66s to 9s is quite good.
This should be a lot better with . I did a lot of rebuilds locally on a low and high core machine and didn't encounter any failures anymore.
This was fixed in , works fine for me.
Code change:
owner = "rust-skia"; repo = "skia"; # see rust-skia:skia-bindings/Cargo.toml#package.metadata skia <del> rev = "m119-0.67.3"; sha256 = "sha256-U75NuJnQa5+SNlOrsBmdlvflGdjo3el63EeIsbnE7ms="; </del> <ins> rev = "m124-0.72.3"; sha256 = "sha256-zlHUJUXukE4CsXwwmVl3KHf9mnNPT8lC/ETEE15Gb4s="; </ins> }; # The externals for skia are taken from skia/DEPS externals = linkFarm "skia-externals" (lib.mapAttrsToList

Related discussion:
text: Package name: neovide Latest released version: 0.13.0 <!-- Search your package here: --- Current version on the unstable channel: 0.12.2 Current version on the stable/release channel: 0.11.2 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --- Note for maintainers: Please tag this issue in your PR. As an additional note, I am currently working on updating Neovide myself. Part of my plans this summer are to begin giving at least two contributions to Nix/NixOS/Nixpkgs each week. I intend to begin maintaining Neovide as part of this goal. Gotta figure out how to A.) apply as a maintainer and B.) figure out if I'm even eligible. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
For future issues/prs/etc. where should I add an additional summary/context if I have any? I've sandwiched it between the Note for maintainers... and Add a reaction... sections in this issue.
Code change:
inherit (lib) mkOption mkIf singleton; <del> inherit (pkgs) heimdal; </del> <ins> inherit (pkgs) heimdalFull; </ins> stateDir = "/var/heimdal"; in

Related discussion:
text: I to and I return I got:
cc (I had to look through essentially old SVN history to find a reference -- this service is untouched for a long time).
I don't use this service anymore. BTW I've fixed its evaluation in the PR .
Let's not close this unless fix hits master.
can you please test the fix and see if there are any more problems with the service?
Code change:
zktree = callPackage ../applications/misc/zktree {}; <ins> zrythm = callPackage ../applications/audio/zrythm { inherit (plasma5Packages) breeze-icons; }; </ins> zthrottle = callPackage ../tools/misc/zthrottle { }; }

Related discussion:
text: Project description A highly automated and intuitive digital audio workstation. Metadata homepage URL: source URL: license: AGPLv3+ platforms: linux
This is a stub of a derivative for ZRythm:
Did you see It's for an older version, and I haven't compared it to your gist, but maybe you would like to do that?
I marked this as stale due to inactivity. &rarr;
Still relevant.
Code change:
--data-dir $STATE_DIRECTORY  --download-dir $STATE_DIRECTORY  --uri ${options.uri}  <ins> --device ${options.device}  </ins> --model ${options.model}  --language ${options.language}  --beam-size ${options.beamSize} ${options.extraArgs}

Related discussion:
text: After setting up faster-whisper for my Home Assistant instance, I learned that my CPU (i5-6500) isn't quite as fast as I'd like for this, so I am now trying to test a GPU (NVIDIA Quadro M2000). My configuration for it is the following: I expected it to then run on my GPU using CUDA, but unless my GPU and CPU are continually equally performant, it is not working. (Also, no processes are shown in ) Steps to reproduce the behavior: NVIDIA GPU, and then configure it accordingly in , add , , , and to faster-whisper in configuration, configure it to work with device = "cuda" for STT to be faster, instead same speed I'm not totally sure what to expect because this is my first time using this, but I expected a Python3 process to appear in and for my STT to be quicker. My config is the following: The following (seemingly) NVIDIA related items are at /dev/ ! ! works, but I am not totally sure that my CUDA is configured correctly, for all I know possibly CUDA isn't configured properly, but I think I have everything correct.
I eyeballed CUDA support, but have no hardware to test or reproduce. I appreciate help in fixing the module to make it work with CUDA.
I am not overly proficient in Nix or anything like this, but I would be willing to help if you have ideas.
Well, for one we're not passing in . Can you try setting ?
Ok, I that and now when looking at the logs, I get this: It then exits.
That looks actionable. We did indeed not build ctranslate2 with CUDA support. I can try to set that up, but it won't be the default, because that would make the package unfree. We possibly need multiple ctranslate2 attributes.
Is it possible to have the package be free unless an option is passed that enables CUDA and then makes it unfree, or would two different packages be needed. There could be a package, I think that could work.
Yeah, that would also work.
If you want to try and build it with CUDA support, I can test it out and report back.
fixes the module, so it passes as expected. It also adds CUDA support to .
Code change:
--data-dir $STATE_DIRECTORY  --download-dir $STATE_DIRECTORY  --uri ${options.uri}  <ins> --device ${options.device}  </ins> --model ${options.model}  --language ${options.language}  --beam-size ${options.beamSize} ${options.extraArgs}

Related discussion:
text: Check the description of the PR on how to opt into CUDA support in nixpkgs.
Hi Just to clarify, you only need in your (or in your 's ) if you're setting up a development environment to write cuda programs. If you only want to use packages with cuda support enabled, you just use them directly (e.g. ), no need to add anywhere manually. If you want to enable cuda in every package that supports it, you can set in your (nb: this triggers a massive rebuild). Instead of adding , you want to use (this way if you switch e.g. -, you'd be still using for the correct kernel), but also instead of you can take (keeps working if you switch e.g. -) Sorry we didn't get this documented yet
Wow, thank you! I assume I still need in my , right? About enabling , I've already enabled that and let it go through that whole process, so I think I'll just leave it enabled. About changing the , how is that to be done exactly? Do I just swap for in the exact same spot?
Also, is there an easy way for me to test out this updated package before it gets merged?
Depends on how you deploy your machine and what nixos version you are on.
I'm on Unstable and use Flakes.
You could replace your nixpkgs input with a fork of nixos-unstable and pick the commits from that PR on top. I'm sure there is a better solution, but I'm not well versed in flakes.
No, is the old version of , and you don't need it in Yes, except it's just , without at the end. This refers to "whatever graphics driver is in use". But also you can just remove this if you use and (both options are badly named, they're not really specific to neither of opengl or x11)
I have , but I don't have xserver enabled because this is a headless server. Do I even need nvidia_x11 if it's headless with no DE?
is where comes from; I don't recall now if it's ok to use on a headless machine, but if you like to just be explicit, you can keep P.S.
Code change:
--data-dir $STATE_DIRECTORY  --download-dir $STATE_DIRECTORY  --uri ${options.uri}  <ins> --device ${options.device}  </ins> --model ${options.model}  --language ${options.language}  --beam-size ${options.beamSize} ${options.extraArgs}

Related discussion:
text: Discourse and NixOS matrix channels provide venues for Q&A discussions
With the changes made to ctranslate2, and the fixes to th , I fully expect this could work. If not, please get back to me with some error messages, e.g. the hardening of the systemd unit might cause problems.
No problem. I attempted to use just the new packages, but it became a little difficult because my old nixpkgs didn't think that ctranslate2 could have CUDA enabled, so I'll just wait for master to get pushed to NixOS-Unstable (Hopefully soon!)
The package now fails with . My system may not be correctly configured for CUDA support, or the SystemD Service is not passing through the NVIDIA device correctly. Just a reminder, the following devices are available at : (I'm not sure if is an NVIDIA thing, but it exists if that's of importance.)
Then we're at least missing . What's the content of ? nix DeviceAllow = if [ "cuda" "auto" ] then [ # "/dev/nvidia1" "/dev/nvidia2" "/dev/nvidia3" "/dev/nvidia4" "/dev/nvidia-caps/nvidia-cap1" "/dev/nvidia-caps/nvidia-cap2" "/dev/nvidiactl" "/dev/nvidia-modeset" "/dev/nvidia-uvm" "/dev/nvidia-uvm-tools" ] else "";
I modified the SystemD service to include , and it didn't help at all. The contents of are . Also, I just discovered something new. When running I get So possibly updating this system now broke NVIDIA support and it just so happened to be at the same time I tried to get Whisper working.
Did you also check which is in ? There are two things you need to maintain: 1) your driver should be newer than the cuda libraries used to build your program, 2) your should come from the same (version of) package as the kernel modules (in other words, currently you have to reboot if you update your nixos and get a newer - the new kernel module is only loaded on the next boot)
shows the following for Also, I just rebooted and is working.
from what I listed is accessible from , should my system have functional CUDA support? I tried using some testing parts from , but it seems to be out of date.
Code change:
--data-dir $STATE_DIRECTORY  --download-dir $STATE_DIRECTORY  --uri ${options.uri}  <ins> --device ${options.device}  </ins> --model ${options.model}  --language ${options.language}  --beam-size ${options.beamSize} ${options.extraArgs}

Related discussion:
text: PS: Should this conversation be continued somewhere else, or is it fine to continue it here because it is somewhat pertinent to the issue?
Yes please, e.g. in or , or on You can just post the final update here once you get things to work, for discoverability purposes. Thanks!
Code change:
{ "darwin": { <del> "hash": "sha256-oIRZtj1BZWioO1ucEXnJQoz/FfDNHWLdYLExuLk+aJk=", "version": "0.2024.04.23.08.01.stable_03" </del> <ins> "hash": "sha256-Ky5JyocpI9JKvhmmhk0Cg/Eo7icmo6FQAT639cGIGrA=", "version": "0.2024.05.07.08.02.stable_02" </ins> }, "linux": { <del> "hash": "sha256-R9//eoelQkH8OAhoU0ux+o1EpQozWhRJwCTTSY9LBGU=", "version": "0.2024.04.23.08.01.stable_03" </del> <ins> "hash": "sha256-zUbWNgiupBoFWoN3I726FejGtGne9dctaiGlPBbj5KU=", "version": "0.2024.05.07.08.02.stable_02" </ins> } }

Related discussion:
text: When I try to open the warp-terminal on wayland it crashes without opening any window and get the following logs: Steps to reproduce the behavior: to open warp-terminal happens It should open the warp-terminal window and prompt. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Might be helpful:
Fixed in , I tried running () on KDE Wayland and everything works as expected
A warp-terminal dev has stated that wayland support is explicitly still experimental and off by default for this reason. Please do not open issues concerning configurations that are explicitly unsupported by upstream.
Sorry, I didn't know it was explicitly unsupported by the upstream since it was working before just fine on Wayland. Thanks a lot anyway!