jiebi/CodeConvo huggingface dataset:
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: }; strategy = mkOption { <del> type = types.enum [ "history" "match_prev_cmd" ]; default = "history"; </del> <ins> type = types.listOf (types.enum [ "history" "completion" "match_prev_cmd" ]); default = [ "history" ]; </ins> description = '' <del> Set ZSH_AUTOSUGGEST_STRATEGY to choose the strategy for generating suggestions. There are currently two to choose from: </del> <ins> `ZSH_AUTOSUGGEST_STRATEGY` is an array that specifies how suggestions should be generated. The strategies in the array are tried successively until a suggestion is found. There are currently three built-in strategies to choose from: </ins> <del> * history: Chooses the most recent match. * match_prev_cmd: Chooses the most recent match whose preceding history item matches the most recently executed command (more info). Note that this strategy won't work as expected with ZSH options that don't preserve the history order such as HIST_IGNORE_ALL_DUPS or HIST_EXPIRE_DUPS_FIRST. </del> <ins> - `history`: Chooses the most recent match from history. - `completion`: Chooses a suggestion based on what tab-completion would suggest. (requires `zpty` module) - `match_prev_cmd`: Like `history`, but chooses the most recent match whose preceding history item matches the most recently executed command. Note that this strategy won't work as expected with ZSH options that don't preserve the history order such as `HIST_IGNORE_ALL_DUPS` or `HIST_EXPIRE_DUPS_FIRST`. </ins> ''; };
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: source ${pkgs.zsh-autosuggestions}/share/zsh-autosuggestions/zsh-autosuggestions.zsh export ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE="${cfg.highlightStyle}" <del> export ZSH_AUTOSUGGEST_STRATEGY=("${cfg.strategy}") </del> <ins> export ZSH_AUTOSUGGEST_STRATEGY=(${concatStringsSep " " cfg.strategy}) </ins> ${optionalString (!cfg.async) "unset ZSH_AUTOSUGGEST_USE_ASYNC"} ${concatStringsSep "n" (mapAttrsToList (key: value: ''export ${key}="${value}"'') cfg.extraConfig)}
Code change:
Project description Cider is an open-source and community-oriented Apple Music client. Metadata homepage URL: source URL: license: GNU Affero General Public License v3.0 platforms: linux, darwin
They ship an AppImage which I use in my own config packaged as follows:

Related discussion:
text: <ins> { appimageTools, lib, fetchurl }: appimageTools.wrapType2 rec { pname = "cider"; version = "1.3.1308"; src = fetchurl { url = "https://1308-429851205-gh.circle-artifacts.com/0/%7E/Cider/dist/artifacts/Cider-${version}.AppImage"; sha256 = "1lbyvn1c8155p039qfzx7jwad7km073phkmrzjm0w3ahdpwz3wgi"; }; extraInstallCommands = let contents = appimageTools.extract { inherit pname version src; }; in '' mv $out/bin/${pname}-${version} $out/bin/${pname} install -m 444 -D ${contents}/${pname}.desktop -t $out/share/applications substituteInPlace $out/share/applications/${pname}.desktop  --replace 'Exec=AppRun' 'Exec=${pname}' cp -r ${contents}/usr/share/icons $out/share ''; meta = with lib; { description = "A new look into listening and enjoying Apple Music in style and performance."; homepage = "https://github.com/ciderapp/Cider"; license = licenses.agpl3; maintainers = [ maintainers.cigrainger ]; platforms = [ "x86_64-linux" ]; }; } </ins>
Code change:
Project description Cider is an open-source and community-oriented Apple Music client. Metadata homepage URL: source URL: license: GNU Affero General Public License v3.0 platforms: linux, darwin
They ship an AppImage which I use in my own config packaged as follows:

Related discussion:
text: stdenv = gcc9Stdenv; }; <ins> cider = callPackage ../applications/audio/cider { }; </ins> isolyzer = callPackage ../tools/cd-dvd/isolyzer { }; isomd5sum = callPackage ../tools/cd-dvd/isomd5sum { };
Code 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 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: element-web <!-- The current version can be found easily with the same process as 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.10.4 desired version: 1.10.6 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Myself i am waiting for an , ... please keep an eye on the release.

Related discussion:
text: "name": "element-desktop", "productName": "Element", "main": "lib/electron-main.js", <del> "version": "1.10.4", </del> <ins> "version": "1.10.6", </ins> "description": "A feature-rich client for Matrix.org", "author": "Element", "repository": {
Code 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 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: element-web <!-- The current version can be found easily with the same process as 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.10.4 desired version: 1.10.6 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Myself i am waiting for an , ... please keep an eye on the release.

Related discussion:
text: "app-builder-lib": "^22.14.10", "asar": "^2.0.1", "chokidar": "^3.5.2", <del> "electron": "^15.3.5", </del> <ins> "electron": "^17", </ins> "electron-builder": "22.11.4", "electron-builder-squirrel-windows": "22.11.4", "electron-devtools-installer": "^3.1.1",
Code 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 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: element-web <!-- The current version can be found easily with the same process as 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.10.4 desired version: 1.10.6 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Myself i am waiting for an , ... please keep an eye on the release.

Related discussion:
text: { <del> "version": "1.10.4", "desktopSrcHash": "cuMo0wRMC6+un3BQK0+Ecnjvs6HugNk71yElNJarlyc=", "desktopYarnHash": "0llnqwgiqggfcgjyaar2h2r1pyw8m14icfb1pcdphqxrah9gpsar", "webHash": "0vf8npddbx4dmq9c1ghak97jn28b18ssblbrq5smdhlzsnxlpm3l" </del> <ins> "version": "1.10.6", "desktopSrcHash": "TJGYavawLDLbP9Sg7HxIcOkr7hcTfAwk4fyOOEv4KhI=", "desktopYarnHash": "038rqg26dn8chzscck5mlhnw2viy6gr8pjb7zrcmi7ipx9h038a0", "webHash": "1wax4h5gfcq4giyq1igsix748cngky487kwvf69zb1gz95hjds9r" </ins> }
Code change:
I just found out about wrapGAppsHook by examining a gnome package, but there really should be documentation about this in the Nixpkgs User Guide (a section about Gnome would be nice, which would show the right way to package GTK3 / GTK2 glib based apps). Also, perhaps there are other things I missed that one should know when packaging Gnome Applications or GTK3/2 apps? /cc Gnome maintainers
I'd like to know as well. Currently receiving this error: On one of the packages I'm trying to put into nixpkgs. Apparently sometimes you need for buildInputs. So apparently all you need to do to use this is:
The error occurs when you do not have any directory containing in variable. One of the things does is (which usually contains the aforementioned file) of dependencies to . (Actually this happens in cooperation with via variable.) Icon themes work in the same vein, only is used and it is populated by which is propagated to (). (XDG fallback theme) should be probably to any GTK application that uses icons (I think that is every GTK applicaton nowadays due to CSD) but some applications require Adwaita because they use icons not in hicolor. Not sure if this functions correctly though, at least it should not according to my mental model of how icon theme selection works; I will need to read the relevant XDG spec before I can finish the documentation.
Just thought I'd leave this comment here for future reference: if you get an error like for python gtk applications, try adding to propogatedBuildInputs!
It should go to , though. But be wary of

Related discussion:
text: <xi:include href="beam.xml" /> <xi:include href="bower.xml" /> <xi:include href="coq.xml" /> <ins> <xi:include href="gnome.xml" /> </ins> <xi:include href="go.xml" /> <xi:include href="haskell.section.xml" /> <xi:include href="idris.section.xml" />
Code change:
I just found out about wrapGAppsHook by examining a gnome package, but there really should be documentation about this in the Nixpkgs User Guide (a section about Gnome would be nice, which would show the right way to package GTK3 / GTK2 glib based apps). Also, perhaps there are other things I missed that one should know when packaging Gnome Applications or GTK3/2 apps? /cc Gnome maintainers
I'd like to know as well. Currently receiving this error: On one of the packages I'm trying to put into nixpkgs. Apparently sometimes you need for buildInputs. So apparently all you need to do to use this is:
The error occurs when you do not have any directory containing in variable. One of the things does is (which usually contains the aforementioned file) of dependencies to . (Actually this happens in cooperation with via variable.) Icon themes work in the same vein, only is used and it is populated by which is propagated to (). (XDG fallback theme) should be probably to any GTK application that uses icons (I think that is every GTK applicaton nowadays due to CSD) but some applications require Adwaita because they use icons not in hicolor. Not sure if this functions correctly though, at least it should not according to my mental model of how icon theme selection works; I will need to read the relevant XDG spec before I can finish the documentation.
Just thought I'd leave this comment here for future reference: if you get an error like for python gtk applications, try adding to propogatedBuildInputs!
It should go to , though. But be wary of

Related discussion:
text: </para> </listitem> </varlistentry> <del> <varlistentry> </del> <ins> <varlistentry xml:id="var-passthru-updateScript"> </ins> <term> <varname>passthru.updateScript</varname> </term>
Code change:
I just found out about wrapGAppsHook by examining a gnome package, but there really should be documentation about this in the Nixpkgs User Guide (a section about Gnome would be nice, which would show the right way to package GTK3 / GTK2 glib based apps). Also, perhaps there are other things I missed that one should know when packaging Gnome Applications or GTK3/2 apps? /cc Gnome maintainers
I'd like to know as well. Currently receiving this error: On one of the packages I'm trying to put into nixpkgs. Apparently sometimes you need for buildInputs. So apparently all you need to do to use this is:
The error occurs when you do not have any directory containing in variable. One of the things does is (which usually contains the aforementioned file) of dependencies to . (Actually this happens in cooperation with via variable.) Icon themes work in the same vein, only is used and it is populated by which is propagated to (). (XDG fallback theme) should be probably to any GTK application that uses icons (I think that is every GTK applicaton nowadays due to CSD) but some applications require Adwaita because they use icons not in hicolor. Not sure if this functions correctly though, at least it should not according to my mental model of how icon theme selection works; I will need to read the relevant XDG spec before I can finish the documentation.
Just thought I'd leave this comment here for future reference: if you get an error like for python gtk applications, try adding to propogatedBuildInputs!
It should go to , though. But be wary of

Related discussion:
text: </varlistentry> <varlistentry> <term> <del> GStreamer </del> <ins> GNOME platform </ins> </term> <listitem> <para> <del> Adds the GStreamer plugins subdirectory of each build input to the <envar>GST_PLUGIN_SYSTEM_PATH_1_0</envar> or <envar>GST_PLUGIN_SYSTEM_PATH</envar> environment variable. </del> <ins> Hooks related to GNOME platform and related libraries like GLib, GTK and GStreamer are described in <xref linkend="sec-language-gnome" />. </ins> </para> </listitem> </varlistentry>
Code change:
Project description Layan kde is a flat Design theme for KDE Plasma desktop. In this repository you'll find: Aurorae Themes Kvantum Themes Plasma Color Schemes Plasma Desktop Themes Plasma Look-and-Feel Themes Metadata homepage URL: source URL: license: gpl3 platforms: linux

Related discussion:
text: <ins> { stdenv , lib , fetchFromGitHub , gitUpdater }: stdenv.mkDerivation rec { pname = "layan-kde"; version = "2022-02-13"; src = fetchFromGitHub { owner = "vinceliuice"; repo = pname; rev = version; sha256 = "09z90g13l26v23nwr8n5bapwldp3hhdrdikynvm4vvb7qsvb4vrp"; }; postPatch = '' patchShebangs install.sh substituteInPlace install.sh  --replace '$HOME/.local' $out  --replace '$HOME/.config' $out/share ''; installPhase = '' runHook preInstall name= ./install.sh --dest $out/share/themes mkdir -p $out/share/sddm/themes cp -a sddm/Layan* $out/share/sddm/themes/ runHook postInstall ''; passthru.updateScript = gitUpdater {inherit pname version; }; meta = with lib; { description = "A flat Design theme for KDE Plasma desktop"; homepage = "https://github.com/vinceliuice/Layan-kde"; license = licenses.gpl3Only; platforms = platforms.all; maintainers = [ maintainers.romildo ]; }; } </ins>
Code change:
Project description Layan kde is a flat Design theme for KDE Plasma desktop. In this repository you'll find: Aurorae Themes Kvantum Themes Plasma Color Schemes Plasma Desktop Themes Plasma Look-and-Feel Themes Metadata homepage URL: source URL: license: gpl3 platforms: linux

Related discussion:
text: layan-gtk-theme = callPackage ../data/themes/layan-gtk-theme { }; <ins> layan-kde = callPackage ../data/themes/layan-kde { }; </ins> lato = callPackage ../data/fonts/lato {}; league-of-moveable-type = callPackage ../data/fonts/league-of-moveable-type {};
Code change:
When attempting to install , installation fails with the following error: As noted in , the call to is incorrectly using a capital B in the flag. It should be . The error coming from the matches the error when running the same command by itself: I searched for an existing issue which reports this, but didn't find any (aside from the comment linked earlier). Slack is installed successfully. N/A N/A <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
Can you make a pr fixing it? I can merge.
I made a commit to do that in my fork here: However it still fails during the , this time with . This was also reported in but only on . However it seems the same issue is also present on and I'm not sure where to go from here on fixing it. I can run the same command from my terminal successfully. Is there anything different about running during the that might cause this?
I think I figured out the problem. writes to , but this isn't accessible to the user running the script (). I'm able to reproduce the problem now if I try to run the command as that user. Is there some way to make this file writable by the user as part of the ? I'll try to do some research on how other packages set property list attributes on darwin to see if there's some other workaround.

Related discussion:
text: runHook preInstall mkdir -p $out/Applications/Slack.app cp -R . $out/Applications/Slack.app <del> '' + lib.optionalString (!stdenv.isAarch64) '' # on aarch64-darwin we get: Could not write domain com.tinyspeck.slackmacgap; exiting /usr/bin/defaults write com.tinyspeck.slackmacgap SlackNoAutoUpdates -Bool YES '' + '' </del> runHook postInstall ''; };
Code 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 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: blender <!-- The current version can be found easily with the same process as 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.93.5 desired version: 3.1 <!-- 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.

Related discussion:
text: { config, stdenv, lib, fetchurl, fetchzip, boost, cmake, ffmpeg, gettext, glew , ilmbase, libXi, libX11, libXext, libXrender , libjpeg, libpng, libsamplerate, libsndfile <del> , libtiff, libGLU, libGL, openal, opencolorio, openexr, openimagedenoise, openimageio2, openjpeg, python39Packages </del> <ins> , libtiff, libGLU, libGL, openal, opencolorio, openexr, openimagedenoise, openimageio2, openjpeg, python310Packages </ins> , openvdb, libXxf86vm, tbb, alembic <del> , zlib, fftw, opensubdiv, freetype, jemalloc, ocl-icd, addOpenGLRunpath </del> <ins> , zlib, zstd, fftw, opensubdiv, freetype, jemalloc, ocl-icd, addOpenGLRunpath </ins> , jackaudioSupport ? false, libjack2 <del> , cudaSupport ? config.cudaSupport or false, cudatoolkit </del> <ins> , cudaSupport ? config.cudaSupport or false, cudatoolkit_11 </ins> , colladaSupport ? true, opencollada , spaceNavSupport ? stdenv.isLinux, libspnav , makeWrapper
Code 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 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: blender <!-- The current version can be found easily with the same process as 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.93.5 desired version: 3.1 <!-- 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.

Related discussion:
text: with lib; let <del> python = python39Packages.python; </del> <ins> python = python310Packages.python; </ins> optix = fetchzip { <del> url = "https://developer.download.nvidia.com/redist/optix/v7.0/OptiX-7.0.0-include.zip"; sha256 = "1b3ccd3197anya2bj3psxdrvrpfgiwva5zfv2xmyrl73nb2dvfr7"; </del> <ins> # url taken from the archlinux blender PKGBUILD url = "https://developer.download.nvidia.com/redist/optix/v7.3/OptiX-7.3.0-Include.zip"; sha256 = "0max1j4822mchj0xpz9lqzh91zkmvsn4py0r174cvqfz8z8ykjk8"; </ins> }; in stdenv.mkDerivation rec { pname = "blender"; <del> version = "2.93.5"; </del> <ins> version = "3.1.0"; </ins> src = fetchurl { url = "https://download.blender.org/source/${pname}-${version}.tar.xz"; <del> sha256 = "1fsw8w80h8k5w4zmy659bjlzqyn5i198hi1kbpzfrdn8psxg2bfj"; </del> <ins> sha256 = "1d0476bzcz86lwdnyjn7hyzkmhfiqh47ls5h09jlbm7v7k9x69hw"; </ins> }; patches = lib.optional stdenv.isDarwin ./darwin.patch; <del> nativeBuildInputs = [ cmake makeWrapper python39Packages.wrapPython llvmPackages.llvm.dev ] </del> <ins> nativeBuildInputs = [ cmake makeWrapper python310Packages.wrapPython llvmPackages.llvm.dev ] </ins> ++ optionals cudaSupport [ addOpenGLRunpath ]; buildInputs = [ boost ffmpeg gettext glew ilmbase freetype libjpeg libpng libsamplerate libsndfile libtiff <del> opencolorio openexr openimagedenoise openimageio2 openjpeg python zlib fftw jemalloc </del> <ins> opencolorio openexr openimagedenoise openimageio2 openjpeg python zlib zstd fftw jemalloc </ins> alembic (opensubdiv.override { inherit cudaSupport; }) tbb
Code 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 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: blender <!-- The current version can be found easily with the same process as 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.93.5 desired version: 3.1 <!-- 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.

Related discussion:
text: llvmPackages.openmp SDL Cocoa CoreGraphics ForceFeedback OpenAL OpenGL ]) ++ optional jackaudioSupport libjack2 <del> ++ optional cudaSupport cudatoolkit </del> <ins> ++ optional cudaSupport cudatoolkit_11 </ins> ++ optional colladaSupport opencollada ++ optional spaceNavSupport libspnav; <del> pythonPath = with python39Packages; [ numpy requests ]; </del> <ins> pythonPath = with python310Packages; [ numpy requests ]; </ins> postPatch = '' # allow usage of dynamically linked embree