jiebi/CodeConvo huggingface dataset:
Code change:
After updating to the latest NixOS unstable channel, when running , the process will fail when building fcitx-libpinyin. Can repro this in a fresh installed NixOS using , adding the following lines: channel: : process will fail when building .....-fcitx-libpinyin- with exit code 2. The rebuild process should succeed without failure. !
Updating to 0.5.4 seems to fix it:

Related discussion:
text: stdenv.mkDerivation rec { pname = "fcitx-libpinyin"; <del> version = "0.5.3"; </del> <ins> version = "0.5.4"; </ins> src = fetchurl { url = "http://download.fcitx-im.org/fcitx-libpinyin/${pname}-${version}.tar.xz"; <del> sha256 = "196c229ckib3xvafkk4n3n3jk9rpksfcjsbbwka6a9k2f34qrjj6"; </del> <ins> sha256 = "1wvsc21imbgq3chlxfw4aycmkb2vi1bkjj9frvhga2m5b5pq82k5"; </ins> }; nativeBuildInputs = [ cmake pkg-config  ];
Code change:
Blender 2.93.5 Hallo When I start Blender now and set under “Render Properties” → “Cycles” Blender crashes completely. Also when I go to “Edit” → “Preferences” → “System” Blender crashes immediately with this Error: What does that tell me now? My GPU configuration in the clinfo: nix run -c nix-info -m:
I think this might be the same issue as described in

Related discussion:
text: , zlib , debugVersion ? false , enableManpages ? false <del> , enableSharedLibraries ? !stdenv.hostPlatform.isStatic </del> <ins> , enableSharedLibraries ? false </ins> , version , src
Code change:
Blender 2.93.5 Hallo When I start Blender now and set under “Render Properties” → “Cycles” Blender crashes completely. Also when I go to “Edit” → “Preferences” → “System” Blender crashes immediately with this Error: What does that tell me now? My GPU configuration in the clinfo: nix run -c nix-info -m:
I think this might be the same issue as described in

Related discussion:
text: "-DSPHINX_WARNINGS_AS_ERRORS=OFF" ]; <del> postPatch = '' </del> <ins> postPatch = lib.optional enableSharedLibraries '' </ins> substitute '${./outputs.patch}' ./outputs.patch --subst-var lib patch -p1 < ./outputs.patch '';
Code change:
Blender 2.93.5 Hallo When I start Blender now and set under “Render Properties” → “Cycles” Blender crashes completely. Also when I go to “Edit” → “Preferences” → “System” Blender crashes immediately with this Error: What does that tell me now? My GPU configuration in the clinfo: nix run -c nix-info -m:
I think this might be the same issue as described in

Related discussion:
text: "-DLLVM_TARGETS_TO_BUILD="AMDGPU;X86"" ]; <del> # The comgr build tends to link against the static LLVM libraries # *and* the dynamic library. Linking against both causes errors # about command line options being registered twice. This patch # removes the static library linking. patchPhase = '' sed -e '/^llvm_map_components_to_libnames/,/[[:space:]]*Symbolize)/d'  -i CMakeLists.txt ''; </del> passthru.updateScript = writeScript "update.sh" '' #!/usr/bin/env nix-shell #!nix-shell -i bash -p curl jq common-updater-scripts
Code change:
I found a disappointing issue with NixOS on AWS EC2 - absence of support for Enhanced Networking (SRI/OV) out of box. See docs at Here are separate issues: is outdated on 16.03 (less then recommended 2.14). Amazon Linux AMI is better then NixOS here amis are built without --sriov flag. Because of 1) this makes starting spot instances with --sriov trickier As I'm not an expert in AMI creating, instance management or kernel module packaging, I won't do pull requests on this topic. But I'd like to share some success with others. Here is the ixgbevf-3.1.2 kernel module package. it And here is extract from config to enable this module: My instance started and ssh works. Now I have this: Ping
Thanks, I wasn't aware of Enhanced Networking. I'll look into it.
Added the driver to the Amazon config: , . Will need to rebuild the AMIs though (and make NixOps enable Enhanced Networking automatically), and add the driver for instances.

Related discussion:
text: # TODO add plugins having various licenses, see http://www.vamp-plugins.org/download.html <del> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo, libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate, libsndfile, makeWrapper, pulseaudio, qt4, redland, rubberband, vampSDK </del> <ins> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo , libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate , libsndfile, makeWrapper, pkgconfig, pulseaudio, qt4, redland , rubberband, vampSDK </ins> }: <del> stdenv.mkDerivation { name = "sonic-visualiser-1.8"; </del> <ins> stdenv.mkDerivation rec { name = "sonic-visualiser-${version}"; version = "1.9"; </ins> src = fetchurl { <del> url = http://downloads.sourceforge.net/sv1/sonic-visualiser-1.8.tar.gz; sha256 = "16ik6q9n92wljvnqcv7hyzb9v3yp3ixxp6df9kasf53fii973dh7"; </del> <ins> url = "http://code.soundsoftware.ac.uk/attachments/download/194/${name}.tar.gz"; sha256 = "00igf7j6s8xfyxnlkbqma0yby9pknxqzy8cmh0aw95ix80cw56fq"; </ins> }; buildInputs = [ libsndfile qt4 fftw /* should be fftw3f ??*/ bzip2 librdf rubberband libsamplerate vampSDK alsaLib librdf_raptor librdf_rasqal redland <ins> pkgconfig </ins> # optional jackaudio # portaudio
Code change:
I found a disappointing issue with NixOS on AWS EC2 - absence of support for Enhanced Networking (SRI/OV) out of box. See docs at Here are separate issues: is outdated on 16.03 (less then recommended 2.14). Amazon Linux AMI is better then NixOS here amis are built without --sriov flag. Because of 1) this makes starting spot instances with --sriov trickier As I'm not an expert in AMI creating, instance management or kernel module packaging, I won't do pull requests on this topic. But I'd like to share some success with others. Here is the ixgbevf-3.1.2 kernel module package. it And here is extract from config to enable this module: My instance started and ssh works. Now I have this: Ping
Thanks, I wasn't aware of Enhanced Networking. I'll look into it.
Added the driver to the Amazon config: , . Will need to rebuild the AMIs though (and make NixOps enable Enhanced Networking automatically), and add the driver for instances.

Related discussion:
text: description = "View and analyse contents of music audio files"; homepage = http://www.sonicvisualiser.org/; license = "GPLv2"; <del> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </del> <ins> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </ins> platforms = stdenv.lib.platforms.linux; }; }
Code change:
While going through the documentation I came about a that explicitly requires matplotlib with the TkAgg backend. I tried to generate a nix-shell with matplotlib and tcl/tk and tkinter. However, the script does not execute and instead I get the following error message: In a simplified form: Start nix-shell:Start Python:Try to import matplotlib, configure the backend, and import parts of Tk:Observe the following error message:System: NixPkgs on openSuse 13.2 (Harlequin) (x86_64) Nix version: nix-env (Nix) 1.10 Nixpkgs version: "16.09pre83147." Matplotlib Maintainer:
Judging from the matplotlib expression we don't build against tcl/tk.
I made an attempt to build matplotlib against tcl/tk with the following patch: Unfortunately, compilation fails with the following error message: The linker cannot find the tcl/tk libraries. The linker flags are quite off: They include and the like. This must be due to matplotlib's own build script, as no such flags are set in my bash environment and is executed with the flag anyway.

Related discussion:
text: <ins> diff --git a/setup.cfg b/setup.cfg new file mode 100644 index 0000000..6f81985 --- /dev/null +++ b/setup.cfg @@ -0,0 +1,2 @@ +[directories] +basedirlist = . </ins>
Code change:
While going through the documentation I came about a that explicitly requires matplotlib with the TkAgg backend. I tried to generate a nix-shell with matplotlib and tcl/tk and tkinter. However, the script does not execute and instead I get the following error message: In a simplified form: Start nix-shell:Start Python:Try to import matplotlib, configure the backend, and import parts of Tk:Observe the following error message:System: NixPkgs on openSuse 13.2 (Harlequin) (x86_64) Nix version: nix-env (Nix) 1.10 Nixpkgs version: "16.09pre83147." Matplotlib Maintainer:
Judging from the matplotlib expression we don't build against tcl/tk.
I made an attempt to build matplotlib against tcl/tk with the following patch: Unfortunately, compilation fails with the following error message: The linker cannot find the tcl/tk libraries. The linker flags are quite off: They include and the like. This must be due to matplotlib's own build script, as no such flags are set in my bash environment and is executed with the flag anyway.

Related discussion:
text: , enableGhostscript ? false, ghostscript ? null, gtk3 , enableGtk2 ? false, pygtk ? null, gobjectIntrospection , enableGtk3 ? false, cairo <ins> , enableTk ? false, tcl ? null, tk ? null, tkinter ? null, libX11 ? null </ins> , Cocoa, Foundation, CoreData, cf-private, libobjc, libcxx }: assert enableGhostscript -> ghostscript != null; assert enableGtk2 -> pygtk != null; <ins> assert enableTk -> (tcl != null) && (tk != null) && (tkinter != null) && (libX11 != null) ; </ins> buildPythonPackage rec { name = "matplotlib-${version}";
Code change:
While going through the documentation I came about a that explicitly requires matplotlib with the TkAgg backend. I tried to generate a nix-shell with matplotlib and tcl/tk and tkinter. However, the script does not execute and instead I get the following error message: In a simplified form: Start nix-shell:Start Python:Try to import matplotlib, configure the backend, and import parts of Tk:Observe the following error message:System: NixPkgs on openSuse 13.2 (Harlequin) (x86_64) Nix version: nix-env (Nix) 1.10 Nixpkgs version: "16.09pre83147." Matplotlib Maintainer:
Judging from the matplotlib expression we don't build against tcl/tk.
I made an attempt to build matplotlib against tcl/tk with the following patch: Unfortunately, compilation fails with the following error message: The linker cannot find the tcl/tk libraries. The linker flags are quite off: They include and the like. This must be due to matplotlib's own build script, as no such flags are set in my bash environment and is executed with the flag anyway.

Related discussion:
text: libpng pkgconfig mock pytz ] ++ stdenv.lib.optional enableGtk2 pygtk <del> ++ stdenv.lib.optionals enableGtk3 [ cairo pycairo gtk3 gobjectIntrospection pygobject3 ]; </del> <ins> ++ stdenv.lib.optionals enableGtk3 [ cairo pycairo gtk3 gobjectIntrospection pygobject3 ] ++ stdenv.lib.optionals enableTk [ tcl tk tkinter libX11 ]; </ins> <del> patches = stdenv.lib.optionals stdenv.isDarwin [ ./darwin-stdenv.patch ]; </del> <ins> patches = [ ./basedirlist.patch ] ++ stdenv.lib.optionals stdenv.isDarwin [ ./darwin-stdenv.patch ]; # Matplotlib tries to find Tcl/Tk by opening a Tk window and asking the # corresponding interpreter object for its library paths. This fails if # `$DISPLAY` is not set. The fallback option assumes that Tcl/Tk are both # installed under the same path which is not true in Nix. # With the following patch we just hard-code these paths into the install # script. postPatch = let inherit (stdenv.lib.strings) substring; tcl_tk_cache = ''"${tk}/lib", "${tcl}/lib", "${substring 0 3 tk.version}"''; in stdenv.lib.optionalString enableTk "sed -i '/self.tcl_tk_cache = None/s|None|${tcl_tk_cache}|' setupext.py"; </ins> checkPhase = '' ${python.interpreter} tests.py
Code change:
I would like to use the following option in in : When running the command I get following error: This is because are appended after the option. It would be better if we switch the order of these. Steps to reproduce the behavior: following configuration to execute the command will fail with following error: The program should be exectued with accepting all

Related discussion:
text: then value else { executable = value; profile = null; extraArgs = []; }; args = lib.escapeShellArgs ( <del> (optional (opts.profile != null) "--profile=${toString opts.profile}") ++ opts.extraArgs </del> <ins> opts.extraArgs ++ (optional (opts.profile != null) "--profile=${toString opts.profile}") </ins> ); in ''
Code change:
, CVSSv3=9.1 (nixos-21.11, nixos-unstable) CVSSv3=9.1 (nixos-21.11, nixos-unstable) CVSSv3=7.5 (nixos-21.11, nixos-unstable) An issue was discovered in the DNS proxy in Connman through 1.40. The TCP server reply implementation lacks a check for the presence of sufficient Header Data, leading to an out-of-bounds read. An issue was discovered in the DNS proxy in Connman through 1.40. forwarddnsreply mishandles a strnlen call, leading to an out-of-bounds read. An issue was discovered in the DNS proxy in Connman through 1.40. The TCP server reply implementation has an infinite loop if no data is received. Scanned versions: nixos-21.11: ; nixos-unstable: . Cc
Unstable - 11 -

Related discussion:
text: stdenv.mkDerivation rec { pname = "connman"; <del> version = "1.40"; </del> <ins> version = "1.41"; </ins> src = fetchurl { url = "mirror://kernel/linux/network/connman/${pname}-${version}.tar.xz"; <del> sha256 = "sha256-GleufOI0qjoXRKrDvlwhIdmNzpmUQO+KucxO39XtyxI="; </del> <ins> sha256 = "sha256-eftA9P3VUwxFqo5ZL7Froj02dPOpjPELiaZXbxmN5Yk="; </ins> }; patches = lib.optionals stdenv.hostPlatform.isMusl [
Code change:
, CVSSv3=7.8 (nixos-21.11, nixos-unstable) CVSSv3=6.5 (nixos-21.11, nixos-unstable) CVSSv3=5.5 (nixos-21.11, nixos-unstable) CVSSv3=5.5 (nixos-21.11, nixos-unstable) CVSSv3=5.5 (nixos-21.11, nixos-unstable) There is an Assertion `scalinglistpredmatrixiddelta==1' failed at in libde265 v1.0.8 when decoding file, which allows attackers to cause a Denial of Service (DoS) by running the application with a crafted file or possibly have unspecified other impact. An Incorrect Access Control vulnerability exists in libde265 v1.0.8 due to a SEGV in An issue was discovered in libde265 v1.0.8.There is a Heap-use-after-free in intrapred.h when decoding file using . A stack-buffer-overflow exists in libde265 v1.0.8 via fallback- in function putepelhvfallback when running program . An issue has been found in libde265 v1.0.8 due to incorrect access control. A SEGV caused by a READ memory access in function derive_boundaryStrength of has occurred. The vulnerability causes a segmentation fault and application crash, which leads to remote denial of service. Scanned versions: nixos-21.11: ; nixos-unstable: . Cc
See

Related discussion:
text: <del> { lib, stdenv, fetchFromGitHub, fetchpatch, autoreconfHook, pkg-config }: </del> <ins> { lib, stdenv, fetchFromGitHub, autoreconfHook, pkg-config }: </ins> stdenv.mkDerivation rec { <del> version = "1.0.8"; </del> <ins> version = "1.0.9"; </ins> pname = "libde265"; src = fetchFromGitHub { owner = "strukturag"; repo = "libde265"; rev = "v${version}"; <del> sha256 = "1dzflqbk248lz5ws0ni5acmf32b3rmnq5gsfaz7691qqjxkl1zml"; </del> <ins> sha256 = "sha256-OpiQapppuKCR27tIG5OW+KiNMP9ysv7CaobiBOW6VUI="; </ins> }; <del> patches = [ (fetchpatch { name = "CVE-2022-1253.patch"; url = "https://github.com/strukturag/libde265/commit/8e89fe0e175d2870c39486fdd09250b230ec10b8.patch"; sha256 = "sha256-F1BOWFx9oXR2trM22atyD3AJ5x6vVfURQ/PTlYP2Ibg="; }) ]; </del> nativeBuildInputs = [ autoreconfHook pkg-config ]; enableParallelBuilding = true;
Code change:
, CVSSv3=6.5 (nixos-21.11, nixos-unstable) A NULL pointer dereference issue was found in the block mirror layer of QEMU in versions prior to 6.2.0. The pointer is dereferenced in mirrorwaiton_conflicts() without ensuring that it's not NULL. A malicious unprivileged user within the guest could use this flaw to crash the QEMU process on the host when writing data reaches the threshold of mirroring node. Scanned versions: nixos-21.11: ; nixos-unstable: . Cc Cc
This is fixed on master since we have QEMU 6.2.0. It's not included in 6.1.1 though, so needs to be fixed on stable. Probably after since it'd be a merge conflict.

Related discussion:
text: sha256 = "09xz06g57wxbacic617pq9c0qb7nly42gif0raplldn5lw964xl2"; revert = true; }) <ins> (fetchpatch { name = "CVE-2021-4145.patch"; url = "https://gitlab.com/qemu-project/qemu/-/commit/66fed30c9cd11854fc878a4eceb507e915d7c9cd.patch"; sha256 = "10za2nag51y4fhc8z7fzw3dfhj37zx8rwg0xcmw5kzmb0gyvvz70"; }) </ins> ] ++ lib.optional nixosTestRunner ./force-uid0-on-9p.patch ++ lib.optionals stdenv.hostPlatform.isMusl [ ./sigrtminmax.patch
Code change:
I want to use (providing ) for it's Debug Adapter support. Particularly it seems like Helix can utilize it with some early debugging support. However, it doesn't seem to work. After adding that to my nix shell, and entering it, and trying to run it, I get:
cc: since I'm running your latest PR bumping this.
I suspect that vscode-lldb's fork of lldb needs to be updated?
Oh yeah, that would be because the adapter is patched-inline in the extension process and the unwrapped, useless, adapter is passed thru instead.
I have some work that fixes this: just uses regular lldb now, we can drop the "fork" with the "rust-enabled" check tries to exec-itself in certain scenarios and must be patched so that it properly calls its wrapped version But most of all, it seems like is ... just built as part of already. I'm not even sure if there's a huge point in bothering with and in general. I really wish this were less messy. was a hassle to figure out, has a bad name, the repo that you find online is old and says darwin-only. yeesh.
i got hit by this, but now it says
Actually only resolves the issue. The original issue of missing still exists somewhat. Yet a working binary can be found after that PR at Help is wanted to resolve the path issue of the adapter sub package :smilingfacewith_tear:
why was this closed? I don't think it's fixed.

Related discussion:
text: "--bin=codelldb" ]; <ins> postFixup = '' mkdir -p $out/share # codelldb expects libcodelldb.so to be in the same # directory as the executable, and can't find it in $out/lib. # To make codelldb executable as a standalone, # we put all files in $out/share, and then wrap the binary in $out/bin. mv $out/bin/* $out/share cp $out/lib/* $out/share ln -s ${lldb.lib} $out/lldb makeWrapper $out/share/codelldb $out/bin/codelldb  --set-default LLDB_DEBUGSERVER_PATH "${lldb.out}/bin/lldb-server" ''; </ins> patches = [ ./adapter-output-shared_object.patch ]; # Tests are linked to liblldb but it is not available here.
Code change:
I want to use (providing ) for it's Debug Adapter support. Particularly it seems like Helix can utilize it with some early debugging support. However, it doesn't seem to work. After adding that to my nix shell, and entering it, and trying to run it, I get:
cc: since I'm running your latest PR bumping this.
I suspect that vscode-lldb's fork of lldb needs to be updated?
Oh yeah, that would be because the adapter is patched-inline in the extension process and the unwrapped, useless, adapter is passed thru instead.
I have some work that fixes this: just uses regular lldb now, we can drop the "fork" with the "rust-enabled" check tries to exec-itself in certain scenarios and must be patched so that it properly calls its wrapped version But most of all, it seems like is ... just built as part of already. I'm not even sure if there's a huge point in bothering with and in general. I really wish this were less messy. was a hassle to figure out, has a bad name, the repo that you find online is old and says darwin-only. yeesh.
i got hit by this, but now it says
Actually only resolves the issue. The original issue of missing still exists somewhat. Yet a working binary can be found after that PR at Help is wanted to resolve the path issue of the adapter sub package :smilingfacewith_tear:
why was this closed? I don't think it's fixed.

Related discussion:
text: mkdir -p $ext/{adapter,formatters} mv -t $ext vsix-extracted/extension/* <del> cp -t $ext/adapter ${adapter}/{bin,lib}/* </del> <ins> cp -t $ext/adapter ${adapter}/share/* </ins> cp -r ../adapter/scripts $ext/adapter wrapProgram $ext/adapter/codelldb  --set-default LLDB_DEBUGSERVER_PATH "${lldb.out}/bin/lldb-server"
Code change:
pivy fails to build due to being unable to find some files Steps to reproduce the behavior: try to build pivy from nixpkgs HEAD

Related discussion:
text: doCheck = false; postPatch = '' <del> substituteInPlace CMakeLists.txt --replace $'{SoQt_INCLUDE_DIRS}'  </del> <ins> substituteInPlace distutils_cmake/CMakeLists.txt --replace $'{SoQt_INCLUDE_DIRS}'  </ins> $'{Coin_INCLUDE_DIR}';$'{SoQt_INCLUDE_DIRS}' '';
Code change:
I am encountering the following error after launching Pinta 2.0.2. I thought initially that it was a problem in the Adwaita theme itself, but whatever the GTK theme I use, I always have the problem. I tried on two different machines and had the same problem with both. NixOS with unstable channel Ubuntu + Nix 2.5.1 with unstable channel I did not have this problem in the last packaged version of Pinta. Maybe it is there since the 2.0.2 upgrade? Pinta should launch without this error. ! Please run and paste the result.
This looks like exactly the same problem discussed on Except that it should be fixed. Not sure what is happening here, and I don't have access to a Linux machine right now to debug. Maybe can help?
I also have this issue. It also causes the toolbar on the left to not appear.
Can someone show me the contents of the directory inside the package? It should have a directory/file somewhere, inside the icons directory (I don't remember the exact path). If this is missing, this is probably the issue.
It is missing:
Huh... I think I can blindly patch this issue, however someone will need to test on the PR.
Wait, I was wrong, it is there, but not in :
It shouldn't be in , it should be in . This is the issue. This can be probably fixed later correctly by setting some setting on , but since I don't have access to a Linux system for now I will just duplicate the assets for now. Later on I can do a proper fix.
Can someone test this PR please:
Waouh that was fast. Thanks a lot, both of you for your reactivity!

Related discussion:
text: # Rename the binary mv "$out/bin/Pinta" "$out/bin/pinta" <ins> # Copy runtime icons mkdir -p $out/share/icons/hicolor/16x16/ cp -r Pinta.Resources/icons/hicolor/16x16/* $out/share/icons/hicolor/16x16/ </ins> # Install dotnet build installer/linux/install.proj  -target:Install
Code change:
From Currently nixpkgs has as an . We should either have as a nix list of enums, or just a string to allow the user to specify a zsh array.

Related discussion:
text: </listitem> <listitem> <para> <ins> <literal>programs.zsh.autosuggestions.strategy</literal> now takes a list of strings instead of a string. </para> </listitem> <listitem> <para> </ins> The <literal>services.unifi.openPorts</literal> option default value of <literal>true</literal> is now deprecated and will be changed to <literal>false</literal> in 22.11. Configurations
Code change:
From Currently nixpkgs has as an . We should either have as a nix list of enums, or just a string to allow the user to specify a zsh array.

Related discussion:
text: combined `influxdb2` package is still provided in this release for backwards compatibilty, but will be removed at a later date. <ins> - `programs.zsh.autosuggestions.strategy` now takes a list of strings instead of a string. </ins> - The `services.unifi.openPorts` option default value of `true` is now deprecated and will be changed to `false` in 22.11. Configurations using this default will print a warning when rebuilt.