jiebi/CodeConvo huggingface dataset:
Change:
, CVSSv3=8.6 (nixos-21.05, nixos-unstable) Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. A vulnerability in versions prior to 11.5.0, 12.1.0, and 13.3.0 allows a sandboxed renderer to request a "thumbnail" image of an arbitrary file on the user's system. The thumbnail can potentially include significant parts of the original file, including textual data in many cases. Versions 15.0.0-alpha.10, 14.0.0, 13.3.0, 12.1.0, and 11.5.0 all contain a fix for the vulnerability. Two workarounds aside from upgrading are available. One may make the vulnerability significantly more difficult for an attacker to exploit by enabling in one's app. One may also disable the functionality of the API if one does not need it. Scanned versions: nixos-21.05: ; nixos-unstable: . Cc Cc Cc
Fix in

Discussion:
maintainers = with maintainers; [ travisbhartwell manveru prusnak ]; platforms = [ "x86_64-darwin" "x86_64-linux" "i686-linux" "armv7l-linux" "aarch64-linux" ] ++ optionals (versionAtLeast version "11.0.0") [ "aarch64-darwin" ]; <del> knownVulnerabilities = optional (versionOlder version "6.0.0") "Electron version ${version} is EOL"; </del> <ins> knownVulnerabilities = optional (versionOlder version "12.0.0") "Electron version ${version} is EOL"; </ins> }; fetcher = vers: tag: hash: fetchurl {
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: gajim <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.3.2 desired version: 1.3.3 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
python3.pkgs.buildPythonApplication rec { pname = "gajim"; <del> version = "1.3.2"; </del> <ins> version = "1.3.3"; </ins> src = fetchurl { url = "https://gajim.org/downloads/${lib.versions.majorMinor version}/gajim-${version}.tar.gz"; <del> sha256 = "1vjzv8zg9s393xw81klcgbkn4h6j2blzla9iil5kqfrw7wmldskh"; </del> <ins> sha256 = "1337qkpcv7j0fgws9scnk82mn2l7s17060vmrbh3ihinmxmbxg6x"; </ins> }; buildInputs = [

checkInputs = [ xvfb-run dbus.daemon ]; checkPhase = '' <del> # https://dev.gajim.org/gajim/gajim/-/issues/10478 rm test/lib/gajim_mocks.py test/unit/test_gui_interface.py </del> xvfb-run dbus-run-session  --config-file=${dbus.daemon}/share/dbus-1/session.conf  ${python3.interpreter} setup.py test

buildPythonPackage rec { pname = "nbxmpp"; <del> version = "2.0.3"; </del> <ins> version = "2.0.4"; </ins> disabled = pythonOlder "3.7";

owner = "gajim"; repo = "python-nbxmpp"; rev = "nbxmpp-${version}"; <del> sha256 = "0gzyd25sja7n49f1ihyg6gch1b0r409r0p3qpwn8w8xy7jgn6ysc"; </del> <ins> sha256 = "1c2ncx1k93gxndaw183x0vlqgjnippl3v6sknklj3z2yjcj0l1ks"; </ins> }; buildInputs = [
Change:
After , dunst now crashes with . () Steps to reproduce the behavior: Use a nixpkgs with merged. Configure dunst with . Observe and A clear and concise description of what you expected to happen. fixes this but I don't want to immediately jump to a PR in case others have stuff to say. cc Please run and paste the result. Maintainer information:
How do you run dunst (e.g. as systemd user service)? I get followed by a core dump when running dunst manually from the command line.. it works fine from a user service setup.
Same here, I've just been letting home-manager handle it for me; perhaps it depends on the configuration Dunst is using.
running from command line: ah the double free happens somewhere from I think
Ok, so from the command line I can avoid the core dump if I pass a option. But thats odd, because the home manager module also passed it I think.
Ah the issue is . If XDGCONFIGDIRS is set, which is then freed twice, once as right in the next line and once as in line 88. indeed running does not segfault.. weird enough I can reproduce the segfault precisely if the length of $XDGCONFIGDIRS exceeds 23 characters.. but maybe it's just that glibc can only catch the double free if the length is large enough?
Can you check if something like fixes your problem?
proper pr is here:
That didn't convince it. I'd guess probably doesn't set it if it's an empty string since that might seem "redundant". Commented on it.

Discussion:
<del> { stdenv, lib, fetchFromGitHub, makeWrapper </del> <ins> { stdenv, lib, fetchFromGitHub, makeWrapper, fetchpatch </ins> , pkg-config, which, perl, libXrandr , cairo, dbus, systemd, gdk-pixbuf, glib, libX11, libXScrnSaver , wayland, wayland-protocols

sha256 = "sha256-BWbvGetXXCXbfPRY+u6gEfzBmX8PLSnI6a5vfCByiC0="; }; <ins> patches = [ (fetchpatch { # fixes double free (https://github.com/dunst-project/dunst/issues/957) url = "https://github.com/dunst-project/dunst/commit/dc8efbbaff0e9ba881fa187a01bfe5c033fbdcf9.patch"; sha256 = "sha256-xuODOFDP9Eqr3g8OtNnaMmTihhurfj2NLeZPr0TF4vY="; }) ]; </ins> nativeBuildInputs = [ perl pkg-config which systemd makeWrapper ]; buildInputs = [
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: gh <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2.1.0 desired version: 2.2.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
buildGoModule rec { pname = "gh"; <del> version = "2.1.0"; </del> <ins> version = "2.2.0"; </ins> src = fetchFromGitHub { owner = "cli"; repo = "cli"; rev = "v${version}"; <del> sha256 = "sha256-70FmFN76azRqnAZ9SLgr/V8moqkWoBbDB6IdSXM7Vmg="; </del> <ins> sha256 = "sha256-/czexUqpdsFQAteZ75ur2SFibrtZWffHpPBEPlLQXSY="; </ins> }; <del> vendorSha256 = "sha256-004TspNwjCWnrD86HEf5wGpt8OCP5qIrTwlGWSRNUmg="; </del> <ins> vendorSha256 = "sha256-slMl5dCyyVNBgDbpYECfYUbpJJ7sWuSGSutYR3rTzj0="; </ins> nativeBuildInputs = [ installShellFiles ];
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: gping <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.2.1 desired version: 1.2.6 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
rustPlatform.buildRustPackage rec { pname = "gping"; <del> version = "1.2.1"; </del> <ins> version = "1.2.6"; </ins> src = fetchFromGitHub { owner = "orf"; repo = "gping"; <del> rev = "v${version}"; sha256 = "sha256-lApm1JLXNjDKLj6zj25OaZDVp7lLW3qyrDsvJrudl8I="; </del> <ins> rev = "gping-v${version}"; sha256 = "sha256-Sxmwuf+iTBTlpfMFCEUp6JyEaoHgmLIKB/gws2KY/xc="; </ins> }; <del> cargoSha256 = "sha256-d1NjPwT3YDp1U9JWeUejpWDbJonFlt5lYbUf7p3jVT0="; </del> <ins> cargoSha256 = "sha256-xEASs6r5zxYJXS+at6aX5n0whGp5qwuNwq6Jh0GM+/4="; </ins> buildInputs = lib.optional stdenv.isDarwin libiconv;
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: pinentry <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2020-07-17 () desired version: 1.2.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
pinentryMkDerivation rec { pname = "pinentry"; <del> version = "1.1.0"; </del> <ins> version = "1.2.0"; </ins> src = fetchurl { url = "mirror://gnupg/pinentry/${pname}-${version}.tar.bz2"; <del> sha256 = "0w35ypl960pczg5kp6km3dyr000m1hf0vpwwlh72jjkjza36c1v8"; </del> <ins> sha256 = "sha256-EAcgRaPgQ9BYH5HNVnb8rH/+6VehZjat7apPWDphZHA="; </ins> }; nativeBuildInputs = [ pkg-config autoreconfHook ]
Change:
The integrated keyboard on my Acer Chromebook R11 does not work with NixOS' Linux kernel. Steps to reproduce the behavior: NixOS on an Acer Chromebook R11, from either a live USB or installation. The integrated keyboard should work. From dmesg: After looking around, I think this is probably because CONFIGPINCTRLCHERRYVIEW is built as a kernel module instead of being built into the kernel: I would modify my kernel configuration and test this, but the Chromebook is too underpowered to compile the kernel. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
From , I think that it needs to be built in. I've verified that doesn't resolve the issue.
I assumed it was stuck in , I don't see why I assumed this. I guess enabling it is okay... Though I don't like how this seems to be an issue that is becoming more and more common, drivers either working only built-in, or only as modules, due to misbehaviour. Enabling it would be done . With the reasoning behind enabling as built-in. , no need to gate behind specific kernel versions I suppose.

Discussion:
NET_FC             = yes; # Fibre Channel driver support # GPIO on Intel Bay Trail, for some Chromebook internal eMMC disks PINCTRL_BAYTRAIL   = yes; <ins> # GPIO for Braswell and Cherryview devices # Needs to be built-in to for integrated keyboards to function properly PINCTRL_CHERRYVIEW = yes; </ins> # 8 is default. Modern gpt tables on eMMC may go far beyond 8. MMC_BLOCK_MINORS   = freeform "32";
Change:
I upgraded Zynaddsubfx (latest unstable), and was surprised to discover the new amazing interface (whooa)... and that I had no more loaded instrument (empty bank). I solved that problem by removing the user zynaddsubfx configuration and bank cache (I think the problem is the bank cache): and indeed, once you reload zynaddsubfx, you can see that the instruments are back. Also, a new file is created, and the bank path is hardcoded, like: I guess that in other distributions this path does not change when zynaddsubfx is updated, but with nix the bank path changes on upgrade, so the user needs to manually clear the cache on each upgrade. I'm not sure what's the best way to solve this problem. I was thinking that the best solution may be to add a small wrapper around zynaddsubfx which clears the cache if it detects in a path to another nix executable. The other possibility may be to use instead of the one, but it won't work outside of NixOs. If these options are not working, at least it would be nice to document that bank cache should be cleared on upgrades. Steps to reproduce the behavior: zynaddsubfx and potentially garbage collect the old version zynaddsubfx: instruments may disapear
Yeah it's really nice :blush: It was a lot of work to get it built. I'm not sure if any other distro even uses the new Zyn-Fusion interface, because it's not the default UI when building from source. I also noticed this problem before between upgrading & running . I tried working on a patch to avoid dumping the default paths into the config, but I never finished it. I'll try looking into it again!
I marked this as stale due to inactivity. &rarr;
still relevant, just haven't gotten around to fixing it
I think this issue should not be closed as for now it is based on a non-accepted PR , so I'll re-open waiting for the changes to be merged upstream.

Discussion:
, stdenv , fetchFromGitHub , callPackage <ins> , fetchpatch </ins> # Required build tools , cmake

outputs = [ "out" "doc" ]; <ins> patches = [ # Hardcode system installed banks & presets (fetchpatch { url = "https://patch-diff.githubusercontent.com/raw/zynaddsubfx/zynaddsubfx/pull/295.patch"; hash = "sha256-UN62i9/JBs7uWTmHDKk3lkAxUXsVmIs6+6avOcL1NBg="; }) ]; </ins> postPatch = '' patchShebangs rtosc/test/test-port-checker.rb src/Tests/check-ports.rb <del> substituteInPlace src/Misc/Config.cpp --replace /usr $out </del> ''; nativeBuildInputs = [ cmake makeWrapper pkg-config ];

++ lib.optionals (guiModule == "ntk") [ ntk cairo libXpm ] ++ lib.optionals (guiModule == "zest") [ libGL libX11 ]; <del> cmakeFlags = [ "-DGuiModule=${guiModule}" ] </del> <ins> cmakeFlags = [ "-DGuiModule=${guiModule}" "-DZYN_DATADIR=${placeholder "out"}/share/zynaddsubfx" ] </ins> # OSS library is included in glibc. # Must explicitly disable if support is not wanted. ++ lib.optional (!ossSupport) "-DOssEnable=OFF"
Change:
I upgraded Zynaddsubfx (latest unstable), and was surprised to discover the new amazing interface (whooa)... and that I had no more loaded instrument (empty bank). I solved that problem by removing the user zynaddsubfx configuration and bank cache (I think the problem is the bank cache): and indeed, once you reload zynaddsubfx, you can see that the instruments are back. Also, a new file is created, and the bank path is hardcoded, like: I guess that in other distributions this path does not change when zynaddsubfx is updated, but with nix the bank path changes on upgrade, so the user needs to manually clear the cache on each upgrade. I'm not sure what's the best way to solve this problem. I was thinking that the best solution may be to add a small wrapper around zynaddsubfx which clears the cache if it detects in a path to another nix executable. The other possibility may be to use instead of the one, but it won't work outside of NixOs. If these options are not working, at least it would be nice to document that bank cache should be cleared on upgrades. Steps to reproduce the behavior: zynaddsubfx and potentially garbage collect the old version zynaddsubfx: instruments may disapear
Yeah it's really nice :blush: It was a lot of work to get it built. I'm not sure if any other distro even uses the new Zyn-Fusion interface, because it's not the default UI when building from source. I also noticed this problem before between upgrading & running . I tried working on a patch to avoid dumping the default paths into the config, but I never finished it. I'll try looking into it again!
I marked this as stale due to inactivity. &rarr;
still relevant, just haven't gotten around to fixing it
I think this issue should not be closed as for now it is based on a non-accepted PR , so I'll re-open waiting for the changes to be merged upstream.

Discussion:
outputs = [ "out" "doc" ]; patches = [ <del> # Hardcode system installed banks & presets </del> <ins> # Lazily expand ZYN_DATADIR to fix builtin banks across updates </ins> (fetchpatch { <del> url = "https://patch-diff.githubusercontent.com/raw/zynaddsubfx/zynaddsubfx/pull/295.patch"; hash = "sha256-UN62i9/JBs7uWTmHDKk3lkAxUXsVmIs6+6avOcL1NBg="; </del> <ins> url = "https://github.com/zynaddsubfx/zynaddsubfx/commit/853aa03f4f92a180b870fa62a04685d12fca55a7.patch"; hash = "sha256-4BsRZ9keeqKopr6lCQJznaZ3qWuMgD1/mCrdMiskusg="; </ins> }) ];
Change:
Project description OTel-CLI is a command-line application to enhance existing shell based applications with instrumentation and observability via OTLP and OpenTelemetry Metadata homepage URL: source URL: license: ASL2.0 platforms: linux
I marked this as stale due to inactivity. &rarr;
not stale, pr

Discussion:
githubId = 1365692; name = "Will Fancher"; }; <ins> emattiza = { email = "nix@mattiza.dev"; github = "emattiza"; githubId = 11719476; name = "Evan Mattiza"; }; </ins> emmabastas = { email = "emma.bastas@protonmail.com"; matrix = "@emmabastas:matrix.org";

<ins> { lib, bash, buildGoModule, fetchFromGitHub, getent, stdenv }: buildGoModule rec { pname = "otel-cli"; version = "0.0.20"; src = fetchFromGitHub { owner = "equinix-labs"; repo = pname; rev = "v${version}"; hash = "sha256-bWdkuw0uEE75l9YCo2Dq1NpWXuMH61RQ6p7m65P1QCE="; }; vendorHash = "sha256-IJ2Gq5z1oNvcpWPh+BMs46VZMN1lHyE+M7kUinTSRr8="; preCheck = '' ln -s $GOPATH/bin/otel-cli . '' + lib.optionalString (!stdenv.isDarwin) '' substituteInPlace main_test.go  --replace 'const minimumPath = `/bin:/usr/bin`' 'const minimumPath = `${lib.makeBinPath [ getent ]}`' ''; meta = with lib; { homepage = "https://github.com/equinix-labs/otel-cli"; description = "A command-line tool for sending OpenTelemetry traces"; changelog = "https://github.com/equinix-labs/otel-cli/releases/tag/v${version}"; license = licenses.asl20; maintainers = with lib.maintainers; [ emattiza urandom ]; }; } </ins>

ostree = callPackage ../tools/misc/ostree { }; <ins> otel-cli = callPackage ../tools/misc/otel-cli {}; </ins> otfcc = callPackage ../tools/misc/otfcc { }; otpclient = callPackage ../applications/misc/otpclient { };
Change:
After upgrading my nixpkgs from the branch to the branch my wordpress enabled apache server crashes with the following error message: Line 68 of :
I thought the error was caused because can't be found in the RPATH of so I tried patching the RPATH using: but that still causes the error: I'm confused about this error message because seems to be in : What's the best way to debug this?
This will be fixed once is merged into .

Discussion:
}; mysql = { <del> configureFlags = throw "MySQL support in PHP is broken! (See https://github.com/NixOS/nixpkgs/issues/14351.)"; #["--with-mysql=${mysql.lib}"]; </del> <ins> configureFlags = ["--with-mysql=${mysql.lib}"]; </ins> buildInputs = [ mysql.lib ]; };

imapSupport = config.php.imap or true; ldapSupport = config.php.ldap or true; mhashSupport = config.php.mhash or true; <del> mysqlSupport = (!php7) && (config.php.mysql or false); mysqliSupport = config.php.mysqli or false; pdo_mysqlSupport = config.php.pdo_mysql or false; </del> <ins> mysqlSupport = (!php7) && (config.php.mysql or true); mysqliSupport = config.php.mysqli or true; pdo_mysqlSupport = config.php.pdo_mysql or true; </ins> libxml2Support = config.php.libxml2 or true; apxs2Support = config.php.apxs2 or true; bcmathSupport = config.php.bcmath or true;
Change:
After upgrading my nixpkgs from the branch to the branch my wordpress enabled apache server crashes with the following error message: Line 68 of :
I thought the error was caused because can't be found in the RPATH of so I tried patching the RPATH using: but that still causes the error: I'm confused about this error message because seems to be in : What's the best way to debug this?
This will be fixed once is merged into .

Discussion:
# 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

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; }; }