jiebi/CodeConvo huggingface dataset:
Change:
quickemu ''; <del> nativeBuildInputs = [ makeWrapper installShellFiles ]; </del> <ins> patches = [ # reduces windows vm ram requirements to 4G, to match microsoft recommendations # TODO: remove on next release (fetchpatch2 { name = "decrease-windows-ram-requirements.patch"; url = "https://github.com/quickemu-project/quickemu/commit/f51697593a4650c5486661292e2febe1d16f8c71.patch"; hash = "sha256-J5hIvQGtkufOcjk2FZN65iox/W2zkLlg+Veg9TF11Fs="; }) ]; nativeBuildInputs = [ makeWrapper installShellFiles ]; </ins> installPhase = '' runHook preInstall

Discussion:
Unable to run windows after this update, Using the older version solves the problem. Originally posted by in
How much ram did you allocate?
4GB
Change:
{ lib, stdenv <ins> , fetchFromGitHub </ins> , coreutils , makeWrapper , sway-unwrapped

Discussion:
User-contributed scripts are being moved over to this repository: I just adopted the use of and couldn't build grimshot: I could build my nixosconfiguration before when I was using . I guess nixpkgs-wayland is slightly ahead, and we'll have this problem when nixos-unstable updates sway.
i don't think github notifies issue subscribers of linked PRs so: i've opened to fix this
Yes, that's a nixpkgs-wayland problem/regression/bug. Nixpkgs is still fine. We just have to update the package before the next Sway update but it might indeed be best to do this in advance.
Change:
<del> { buildGoModule, fetchFromGitHub, lib, installShellFiles, testers, cue }: </del> <ins> { buildGoModule , fetchFromGitHub , fetchpatch , lib , installShellFiles , testers , cue }: </ins> buildGoModule rec { pname = "cue";

Discussion:
Steps to reproduce the behavior: in the latest . Failed some tests during the build. Please run and paste the result.
cc. This breaks bootspec and thus lanzaboote on the latest
Only if you enable validation but yeah.
Change:
subPackages = [ "." ]; <del> ldflags = [ "-s" "-w" "-X github.com/helmfile/helmfile/pkg/app/version.Version=${version}" ]; </del> <ins> ldflags = [ "-s" "-w" "-X go.szostok.io/version.version=v${version}" ]; </ins> nativeBuildInputs = [ installShellFiles ];

Discussion:
reports the wrong version This is a problem because it causes issues with file e.g. from the version number is wrong version should be set using the git version tag The version path changed from to in commit
thanks for reporting! and thanks again to for the patch!
Change:
vue-cli = self."@vue/cli"; # added 2023-08-18 vue-language-server = self.vls; # added 2023-08-20 inherit (pkgs) web-ext; # added 2023-08-20 <ins> inherit (pkgs) wrangler; # added 2024-07-01 </ins> inherit (pkgs) write-good; # added 2023-08-20 inherit (pkgs) yaml-language-server; # added 2023-09-05 inherit (pkgs) yo; # added 2023-08-20

Discussion:
Steps to reproduce the behavior: nixos flake build, with nixpkgs/master, which worked yesterday and doesn't today fails on workerd fixed derivation that is pulled from npm may relate to based on commit histor <!-- 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. I do have a bunch of experimental flags enabled, they could impact something.. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
can you please review
Change:
description = "Userspace utilities for linux-erofs file system"; changelog = "https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git/tree/ChangeLog?h=v${version}"; license = with licenses; [ gpl2Plus ]; <del> maintainers = with maintainers; [ ehmry nikstur ]; </del> <ins> maintainers = with maintainers; [ ehmry nikstur jmbaur ]; </ins> platforms = platforms.unix; }; <del> } </del> <ins> }) </ins>

Discussion:
Build log: Update PR: Revert PR: This blocked the channel. It seems most likely to be an upstream regression. There’s nothing obvious in . Probably we’ll have to report it upstream and/or peruse the . cc
I cannot parse the log in the link above or reproduce locally, could someone give some hints what happens or a reproducable way?
Hi, sorry about that! If you have Nix installed on a Linux machine, or a NixOS VM handy, should reproduce the test failure. However, I realize that’s not terribly convenient. The , (Sorry, no, that’s of course part of , so I really don’t have any idea why the erofs-utils upgrade caused us issues. I know we use erofs inside our VM and testing machinery, but I don’t know exactly where. Most likely whatever is hanging actually comes after the call.) We don’t currently have any idea why this happens for this specific test, but we know that it happens reliably and across multiple platforms. None of this is very digestible or easy to debug for someone who isn’t experienced with Nix(OS), so I was hoping one of our contributors would be able to make a more minimal reproducer to be able to send upstream, or even figure out the bug. I just put this issue up as we were having to revert the upgrade in a hurry to unblock updates for users and I didn’t want it to be forgotten about. I don’t have the time myself to try and make a minimal reproducer, but please let me know if there’s anything else I could do that would be helpful.
It almost certainly comes from this invocation of : I'll hopefully have time to look at this in more detail soon.
The log doesn’t contain “Creating Nix store image...”, FWIW. Not sure if that’s relevant to whether that code is being invoked or not.
I haven't pinpointed what is to blame, but it appears the way prints progress may have changed between 1.7.1 and 1.8.1, which is causing the issues. When telling the tooling to not print any progress, image creation occurs much more quickly (though still quite slow as the machine closures with gitlab are large).

I assume it's something on our side that's to blame since I don't actually see the progress being printed during the timeouts, so I assume something is eating the output.
Oh, I know. Since erofs-utils 1.8, we unify and the usual mkfs logic, so also prints progress too. And yes, if that is not expected, is preferred to match erofs-utils 1.7.1...
thank you for tracking this!
Change:
{ <del> beta = { deps = { gn = { rev = "811d332bd90551342c5cbd39e133aa276022d7f8"; hash = "sha256-WCq+PNkWxWpssUOQyQbAZ5l6k+hg+qGMsoaMG0Ybj0o="; url = "https://gn.googlesource.com/gn"; version = "2023-08-01"; }; }; hash = "sha256-spzY2u5Wk52BrKCk9aQOEp/gbppaGVLCQxXa+3JuajA="; hash_deb_amd64 = "sha256-eTeEeNa4JuCW81+SUAyrKi3S0/TJNTAoTktWQ0JsgYc="; version = "117.0.5938.22"; }; dev = { deps = { gn = { rev = "cc56a0f98bb34accd5323316e0292575ff17a5d4"; hash = "sha256-SwlET5h5xtDlQvlt8wbG73ZfUWJr4hlWc+uQsBH5x9M="; url = "https://gn.googlesource.com/gn"; version = "2023-08-10"; }; }; hash = "sha256-W0fZuvv9jz03ibQqB6MG45aw2zPklfxoFzZzr+kRuJk="; hash_deb_amd64 = "sha256-XWxRFLFxBqnvKcoB5HErwVbtHCGYRteLeTv44zVMwIc="; version = "118.0.5966.0"; }; </del> stable = { chromedriver = { hash_darwin = "sha256-ugsxRhIPtDD7Y4/PsIc8Apqrtyo4uiVKoLmtRvQaJ3k=";

Discussion:
Package name: google-chrome Latest released version: 116.0.5845.187 Current version on the unstable channel: 116.0.5845.179 Current version on the stable/release channel: 116.0.5845.179 Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Please note a new version of Chrome is now available to address an exploited-in-the-wild zero-day vulnerability in the WebP image parsing code in the Chrome browser. This vulnerability could allow arbitrary code execution when a specially crafted image is viewed. Please update as soon as possible. For more information on the vulnerability, tracked as CVE-2023-4863, refer to this disclosure from Google: Note for maintainers: Please tag this issue in your PR.
I'm seeing on both 23.05 and unstable. Per chromium/google-chrome was one of the first things that was patched.
Those versions are released on both channels but on stable updates for google-chrome-dev and google-chrome-beta are missing
Change:
nerdctl = callPackage ../applications/networking/cluster/nerdctl { }; netdata = callPackage ../tools/system/netdata { <del> inherit (darwin.apple_sdk.frameworks) CoreFoundation IOKit; </del> protobuf = protobuf_21; }; netdataCloud = netdata.override {

Discussion:
Steps to reproduce the behavior: netdata Add any other context about the problem here. <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Created a PR to fix the build, can you try it out ?
Change:
function(generate_pkgconfig'  --replace '$'{prefix}/'$'{CMAKE_INSTALL_LIBDIR} '$'{CMAKE_INSTALL_FULL_LIBDIR}  --replace '$'{prefix}/'$'{CMAKE_INSTALL_INCLUDEDIR} '$'{CMAKE_INSTALL_FULL_INCLUDEDIR} <ins> '' + lib.optionalString (stdenv.isDarwin && stdenv.isAarch64) '' sed -i "/vptr/d" test/CMakeLists.txt </ins> ''; meta = with lib; {

Discussion:
Please run and paste the result. Maintainer information:
Maybe compiler-rt-libc is missing some files on the arm platform?
I marked this as stale due to inactivity. &rarr;
Change:
<del> { lib , python3 , fetchFromGitHub , godot3-server }: let python = python3.override { packageOverrides = self: super: { lark = super.lark.overridePythonAttrs (old: rec { # gdtoolkit needs exactly this lark version version = "0.8.0"; src = fetchFromGitHub { owner = "lark-parser"; repo = "lark"; rev = version; hash = "sha256-KN9buVlH8hJ8t0ZP5yefeYM5vH5Gg7a7TEDGKJYpozs="; fetchSubmodules = true; }; patches = [ ]; }); }; }; in python.pkgs.buildPythonApplication rec { pname = "gdtoolkit"; version = "3.3.1"; # If we try to get using fetchPypi it requires GeoIP (but the package dont has that dep!?) src = fetchFromGitHub { owner = "Scony"; repo = "godot-gdscript-toolkit"; rev = version; sha256 = "13nnpwy550jf5qnm9ixpxl1bwfnhhbiys8vqfd25g3aim4bm3gnn"; }; disabled = python.pythonOlder "3.7"; propagatedBuildInputs = with python.pkgs; [ docopt lark pyyaml setuptools ]; doCheck = true; nativeCheckInputs = with python.pkgs; [ pytestCheckHook hypothesis godot3-server ]; preCheck = let godotServerMajorVersion = lib.versions.major godot3-server.version; gdtoolkitMajorVersion = lib.versions.major version; msg = '' gdtoolkit major version ${gdtoolkitMajorVersion} does not match godot-server major version ${godotServerMajorVersion}! gdtoolkit needs a matching godot-server for its tests. If you see this error, you can either: - disable doCheck for gdtoolkit, or - provide a compatible godot-server version to gdtoolkit" ''; in lib.throwIf (godotServerMajorVersion != gdtoolkitMajorVersion) msg '' # The tests want to run the installed executables export PATH=$out/bin:$PATH # gdtoolkit tries to write cache variables to $HOME/.cache export HOME=$TMP # Work around https://github.com/godotengine/godot/issues/20503 # Without this, Godot will complain about a missing project file touch project.godot # Remove broken test case # (hard to skip via disabledTests since the test name contains an absolute path) rm tests/potential-godot-bugs/multiline-subscription-expression.gd ''; pythonImportsCheck = [ "gdtoolkit" "gdtoolkit.formatter" "gdtoolkit.linter" "gdtoolkit.parser" ]; meta = with lib; { description = "Independent set of tools for working with Godot's GDScript - parser, linter and formatter"; homepage = "https://github.com/Scony/godot-gdscript-toolkit"; license = licenses.mit; maintainers = with maintainers; [ shiryel tmarkus ]; }; } </del>

Discussion:
Package name: gdtoolkit Latest released version: 4.1.0 <!-- Search your package here: --- Current version on the unstable channel: 3.3.1 Current version on the stable/release channel: 3.3.1 <!-- 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 It's a bit of an odd situation because both Godot 3 and 4 are in use, so maybe this one should be renamed to gdtoolkit3 or the opposite for the time being. Haven't had any success yet trying to override the package on my own. <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
Change:
with lib; let <del> tg_owt = callPackage ../tdesktop/tg_owt.nix {}; </del> <ins> tg_owt = callPackage ./tg_owt.nix {}; </ins> in mkDerivation rec { pname = "kotatogram-desktop"; version = "1.4.1";

Discussion:
, CVSSv3=5.3 (nixos-21.05, nixos-unstable) A reordering issue exists in Telegram before 7.8.1 for Android, Telegram before 7.8.3 for iOS, and Telegram Desktop before 2.8.8. An attacker can cause the server to receive messages in a different order than they were sent a client. Scanned versions: nixos-21.05: ; nixos-unstable: . Cc Cc Cc
Change:
stdenv.mkDerivation { pname = "qrcode"; <del> version = "unstable-2022-01-10"; </del> <ins> version = "unstable-2023-12-02"; </ins> src = fetchFromGitHub { owner = "qsantos"; repo = "qrcode"; <del> rev = "f4475866bbf963ad118db936060f606eedc224d5"; hash = "sha256-IbWYSAc0PvSWcxKaPUXDldGDCK/lPZjptepYtLppPmA="; </del> <ins> rev = "96fac69ad3e4f616ce75c0e3ef4ed0574cfab315"; hash = "sha256-Aesjys6FchB6qcLRWJNGfcEZRlO3stw3+IM8Xe2pF+Q="; </ins> }; <del> env.NIX_CFLAGS_COMPILE = "-Wno-error=unused-result"; </del> makeFlags = [ "CC=${stdenv.cc.targetPrefix}cc" ]; installPhase = ''

Discussion:
Steps to reproduce the behavior: (tested only on Darwin) (e.g. ) The hints were useful and this short patch indeed did the trick: This looks like it hints at differences in compiler strictness across different OSs, so I'm opening this issue in case it's useful to fix a potential underlying issue! Thanks for nixpkgs!
Ouch. OK, on Linux it breaks with too, at least (not with default or or yet)… If you tag me in a PR that applies that patch, I will definitely merge it (after letting OfBorg builds pass just to be sure I am not missing something); getting around to pushing your patch myself will take longer… (given I only use Linux, am DataMatrix-biased, and mostly use ZXing for QR-codes), but hopefully eventually I will get around to it.
Change:
, webkitgtk , wrapGAppsHook <ins> # check inputs , xvfb-run , nose , flake8 </ins> # python dependencies , dbus-python , distro

Discussion:
<!-- 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: lutris-unwrapped <!-- 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: 0.5.8.4 desired version: 0.5.9 <!-- 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.
Change:
let inherit (self) callPackage; <del> inherit (python.passthru) isPy27 isPy37 isPy38 isPy39 isPy310 isPy311 isPy3k isPyPy pythonAtLeast pythonOlder; </del> namePrefix = python.libPrefix + "-";

Discussion:
Since , was moved to top level, and and are aliases of from the top level To find the usages of these aliases, you can search for in the repository Note that there are false positives (e.g. when used in overlays) and this also might not include all usages (let inherit)
Change:
pyopenssl ]; pyopenssl = [ <ins> cryptography </ins> pyopenssl ]; reauth = [

Discussion:
Package name: Latest released version: 2.27.0 <!-- Search your package here: --- Current version on the unstable channel: 2.21.0 Current version on the stable/release channel: 2.21.0 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
# To help debug the transient error in # https://trac.sagemath.org/ticket/23087 when it next occurs. ./patches/configurationpy-error-verbose.patch <ins> # https://trac.sagemath.org/ticket/33907 (fetchSageDiff { name = "interfaces-expectpy-intermittent.patch"; base = "9.8.beta6"; rev = "6f5c1c2fc8bcfb5e6555716d05ce70511795ffa1"; sha256 = "sha256-z8FQxtrk62MHzPjrUTad+fMAE6XV8GTsLWKgGOM3zBg="; }) </ins> ]; # Patches needed because of package updates. We could just pin the versions of

Discussion:
Sage does not build anymore since a few days (2023-01-14), while it was building fine before. Hydra job: Seems to be because of some failing tests, notably caused by deprecated stuff: or I also saw one Steps to reproduce the behavior: sage or sageWithDoc
Thanks for the report! This should have been fixed by , but some Sage tests fail intermittently once in a while and one of those tests, , failed during the last build attempt (). This particular test has been made robust in Sage 9.8, so I will take this opportunity to backport the fix.
Status update: The follow-up intermittent test fix reached nixos-unstable yesterday.
Thanks a lot!
Change:
# This file is autogenerated from update.sh in the same directory. <del> # VHASH: 545cfbcd1fc31d037d1e6b5382995075d2a875a51d181cc26851e49dbd2227d8 </del> <ins> # VHASH: c9500486764a2433d0f059134a981eb9adccd3546a6f779bc0e05cdcb26d2ae6 </ins> { dev = { <del> version = "22.0.1207.1"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-22.0.1207.1.tar.bz2"; sha256 = "1kzzaaczz1mwsfw7fn8la6h4yls2wy537ypabqgwyim01jhfmilp"; </del> <ins> version = "22.0.1221.1"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-22.0.1221.1.tar.bz2"; sha256 = "08cx2im0ng1dg83mk8jlx4in7v8f5vsf9y2ild0i22jb20c7h31s"; </ins> }; beta = { <del> version = "21.0.1180.41"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-21.0.1180.41.tar.bz2"; sha256 = "1225ny7y5msyk44lb5dspd4aq0yiaawsb5xi9g8iimiv80j4h34a"; </del> <ins> version = "21.0.1180.57"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-21.0.1180.57.tar.bz2"; sha256 = "0idimvkrhs09x93hl8p7rddyb0ymk9f8i5jm6m3lg6ga959aj6ri"; </ins> }; stable = { <del> version = "20.0.1132.57"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-20.0.1132.57.tar.bz2"; sha256 = "06v4ybvaj3gx1v4visfyfzbq2q3xasa8xlf05f4wi2bf62vcc98j"; </del> <ins> version = "21.0.1180.57"; url = "http://commondatastorage.googleapis.com/chromium-browser-official/chromium-21.0.1180.57.tar.bz2"; sha256 = "0idimvkrhs09x93hl8p7rddyb0ymk9f8i5jm6m3lg6ga959aj6ri"; </ins> }; }

Discussion:
Describe the bug when using , only gets set on linux. This seems to be done very much on purpose, so I don't know if there's some good reason for it: This causes problems for instance when cross-compiling to windows and then using pkgsStatic, some packages wrongly think they are not compiling statically. I can't remember what packages I've encountered this in, and right now I'm encountering it in a change that I'm trying to make, not something that already exists. To Reproduce Steps to reproduce the behavior: Expected behavior would be true on all platforms if using Notify maintainers seems to have this code / created Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(qolen): nixpkgs: Maintainer information:
Change:
owner = "aws"; repo = "aws-lambda-python-runtime-interface-client"; rev = "refs/tags/${version}"; <del> sha256 = "sha256-9DiUpgeL4bY7G3b5R06FjpN0st03F84fj0bhp70moKo="; </del> <ins> sha256 = "sha256-FHZ7ZTCOzElW/DM07TScp6bfOOFe4b307q/ALVX1fWQ="; </ins> }; <del> patches = [ (fetchpatch { # https://github.com/aws/aws-lambda-python-runtime-interface-client/pull/58 url = "https://github.com/aws/aws-lambda-python-runtime-interface-client/commit/162c3c0051bb9daa92e4a2a4af7e90aea60ee405.patch"; sha256 = "09qqq5x6npc9jw2qbhzifqn5sqiby4smiin1aw30psmlp21fv7j8"; }) ]; postPatch = '' substituteInPlace requirements/base.txt  --replace 'simplejson==3' 'simplejson~=3' ''; </del> propagatedBuildInputs = [ simplejson ]; nativeBuildInputs = [

Discussion:
Steps to reproduce the behavior: python311Packages.awslambdaric e.g.: I'm using a flake to build a docker image with awslambdaric to deploy in a AWS Lambda. I'm on NixOS unstable. I attempted to override doChecks to false but that did not help. There is a where the simplejson version changed. More recently, upstream has relaxed the version requirements: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks, should fix it.
Change:
<ins> { lib, fetchPypi, buildPythonPackage, hatchling, hatch-vcs, numpy, scipy, matplotlib, pandas, multiprocess, pathos, }: let finalAttrs = { pname = "salib"; version = "1.5.1"; pyproject = true; src = fetchPypi { inherit (finalAttrs) pname version; hash = "sha256-5KnDGbjdAplajcmD9XxFLLflttvUPnt4VskMtqMyu18="; }; build-system = [ hatchling hatch-vcs ]; dependencies = [ numpy scipy matplotlib pandas multiprocess ]; optional-dependencies = { distributed = [ pathos ]; }; # There are no tests in the pypi package doCheck = false; pythonImportsCheck = [ "SALib" "SALib.analyze" "SALib.plotting" "SALib.sample" "SALib.test_functions" "SALib.util" ]; meta = { changelog = "https://github.com/SALib/SALib/releases"; description = "Python implementations of commonly used sensitivity analysis methods, useful in systems modeling to calculate the effects of model inputs or exogenous factors on outputs of interest"; homepage = "https://github.com/SALib/SALib"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ theobori ]; mainProgram = "salib"; }; }; in buildPythonPackage finalAttrs </ins>

Discussion:
Project description Python implementations of commonly used sensitivity analysis methods. Useful in systems modeling to calculate the effects of model inputs or exogenous factors on outputs of interest. Metadata homepage URL: & source URL: license: mit. platforms: any platform with python/pip Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
dontWrapQtApps = true; <del> # HACK `propagatedSandboxProfile` does not appear to actually propagate the sandbox profile from `qtbase` sandboxProfile = toString qtbase.__propagatedSandboxProfile or null; </del> cmakeFlags = [ "-DBUILD_WITH_QT6=${if lib.versions.major qtbase.version == "6" then "ON" else "OFF"}" "-DQT_TRANSLATIONS_DIR=share/qt/translations"

Discussion:
While working on , I attempted to use in the derivation. Unfortunately, it did not appear to propagate to qtpass or other Qt-using packages that would require the profile. They still experienced the error until I manually sandbox profiles to the other packages. Steps to reproduce the behavior: a to a package for something it needs (e.g., ). that package as a or to another package (e.g., qtpass). the other package. The build should succeed (allowing whatever is permitted by the profile), but it fails (due to the lack of the sandbox profile). n/a This requires the sandbox on Darwin to be set to or . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --