jiebi/CodeConvo huggingface dataset:
Change:
Project description Catamaran sans is a font for tamil language Metadata homepage URL: source URL: license: OFL platforms: ? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
<ins> { stdenvNoCC, lib, fetchzip, }: stdenvNoCC.mkDerivation rec { pname = "catamaran"; version = "0-unstable-2024-03-02"; src = fetchzip { url = "https://www.1001fonts.com/download/catamaran.zip"; stripRoot = false; hash = "sha256-9s11lZSS4pYJZwl8Uk7qtdwfZ2bkoZkSIf1MkQlv7H4="; }; stripRoot = false; installPhase = '' runHook preInstall mkdir -p $out/share/fonts/truetype mv *.ttf $out/share/fonts/truetype/ runHook postInstall ''; meta = with lib; { homepage = "https://fonts.google.com/specimen/Catamaran"; description = "A stylish sans-serif Tamil and Latin typeface"; longDescription = '' Catamaran is a Unicode-compliant Latin and Tamil text type family designed for the digital age. The Tamil is monolinear and was designed alongside the sans serif Latin and Devanagari family Palanquin. It currently comprises of 9 text weights, making it a versatile family that strikes a balance between typographic conventions and that bit of sparkle. (A catamaran is a multihulled vessel consisting of two parallel hulls of equal size. The catamaran concept is a relative newcomer for Western boat designers, been used since time immemorial among the Dravidian people, in South India.) ''; license = licenses.ofl; platforms = platforms.all; maintainers = with maintainers; [wyred50]; }; } </ins>
Change:
Project description Chainsaw is a tool developed to run end to end tests in Kubernetes clusters. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
license is Apache V2, we support linux mac and windows (amd and arm versions). You could also list chainsaw adopters if it helps.

Discussion:
githubId = 1153271; name = "Sander van der Burg"; }; <ins> Sanskarzz = { email = "sanskar.gur@gmail.com"; github = "Sanskarzz"; githubId = 92817635; name = "Sanskar Gurdasani"; }; </ins> sarcasticadmin = { email = "rob@sarcasticadmin.com"; github = "sarcasticadmin";

<ins> { lib, buildGoModule, fetchFromGitHub }: buildGoModule rec { pname = "kyverno-chainsaw"; version = "0.1.7"; src = fetchFromGitHub { owner = "kyverno"; repo = "chainsaw"; rev = "v${version}"; hash = "sha256-v71qAJSpnbHd+jkPkR34IVNvwWLhm04TrPzduB6ZOgA="; }; vendorHash = "sha256-lHV5Ik/L/Svn9AvcKZupq778ektEsbxfOkCts4Ocx9g="; ldflags = [ "-s" "-w" "-X github.com/kyverno/chainsaw/pkg/version.BuildVersion=v${version}" "-X github.com/kyverno/chainsaw/pkg/version.BuildHash=${version}" "-X github.com/kyverno/chainsaw/pkg/version.BuildTime=1970-01-01_00:00:00" ]; doCheck = false; # requires running kubernetes meta = { changelog = "https://github.com/kyverno/chainsaw/releases/tag/v${version}"; description = "Declarative approach to test Kubernetes operators and controllers"; homepage = "https://kyverno.github.io/chainsaw/"; license = lib.licenses.asl20; longDescription = '' Chainsaw is meant to test Kubernetes operators work as expected by running a sequence of test steps for: * Creating resources * Asserting operators react (or not) the way they should ''; mainProgram = "chainsaw"; maintainers = with lib.maintainers; [ Sanskarzz ]; }; } </ins>
Change:
Steps to reproduce the behavior: Upscayl failed to build due to hash mismatch during (I'm nix beginner, I hope to that I write this bug report in right place.) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Strange! I wonder why I did not get that hash mismatch when I reviewed the PR. Upcoming PR!

Discussion:
src = fetchurl { url = "https://github.com/upscayl/upscayl/releases/download/v${version}/upscayl-${version}-linux.AppImage"; <del> hash = "sha256-33jJRMvRQxL7rPJ6VigEKcDhge46CAA0jJUOhzEyWzA="; </del> <ins> hash = "sha256-EoTFvlLsXQYZldXfEHhP3/bHygm+NdeDsf+p138mM8w"; </ins> }; appimageContents = appimageTools.extractType2 {
Change:
Steps to reproduce the behavior: build drawio version 22.1.18 built successfully for me. This failure happens on drawio version 22.0.3. <!-- 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]:
Hello, could you please check if the issue is still occurring in the latest version (see or just run )?
Unfortunately, this fails with the same error: Logs: PS: Thanks for the tip with

Discussion:
, copyDesktopItems , prefetch-yarn-deps , makeWrapper <ins> , autoSignDarwinBinariesHook </ins> , nodejs , yarn , electron

hash = "sha256-+TCnVXcmAEpa7MiL0dyeoh2aUfIIO8eze9pEaHgKnME="; }; <ins> # `@electron/fuses` tries to run `codesign` and fails. Disable and use autoSignDarwinBinariesHook instead postPatch = '' sed -i -e 's/resetAdHocDarwinSignature:.*/resetAdHocDarwinSignature: false,/' build/fuses.js ''; </ins> offlineCache = fetchYarnDeps { yarnLock = src + "/yarn.lock"; hash = "sha256-QS0bkDDQq3sn79TQ+pTZsmbmXgMccyLmlPLTsko7eGg=";

yarn ] ++ lib.optionals (!stdenv.isDarwin) [ copyDesktopItems <ins> ] ++ lib.optionals stdenv.isDarwin [ autoSignDarwinBinariesHook </ins> ]; ELECTRON_SKIP_BINARY_DOWNLOAD = true;

drawing = callPackage ../applications/graphics/drawing { }; <del> drawio = callPackage ../applications/graphics/drawio { }; </del> <ins> drawio = callPackage ../applications/graphics/drawio { inherit (darwin) autoSignDarwinBinariesHook; }; </ins> drawio-headless = callPackage ../applications/graphics/drawio/headless.nix { }; drawpile = libsForQt5.callPackage ../applications/graphics/drawpile { };
Change:
logging config doesn't seem to be applied to the invocation of Steps to reproduce the behavior: the following : info-level logs coming through (despite the config) No info-level logs appear in the service log, config is applied. I suspect the final is overriding all previous log configs, going off how and this appears to then . Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I see this more as an issue with the . Their are clear, it should work: I do see your issue and I'm wondering if it would be better to leave out the directive (since we specified all others).
Thanks yes I'm thinking the final directive is overriding all the others, so I guess it is a quirk of the upstream. I like the idea of leaving it out, or we could have it at the start of the , which will allow configuration of an level, with the ability to override it for specific areas, as subsequent arguments. Wdyt? (although having said that, I guess we always pass the other areas, so perhaps dropping is simpler, leaving the nixos config to default each area) I'm happy to make the PR if you'd be ok with either of those approaches
go ahead and make the PR, you can tag me as reviewer! Thx a lot.

Discussion:
"--port=${toString cfg.port}" "--configpath=${cfg.configpath}" "--scanconfig=${cfg.scanconfig}" <ins> "--log=all:${cfg.logs.all}" </ins> "--log=main:${cfg.logs.main}" "--log=network:${cfg.logs.network}" "--log=bus:${cfg.logs.bus}" "--log=update:${cfg.logs.update}" "--log=other:${cfg.logs.other}" <del> "--log=all:${cfg.logs.all}" </del> ] ++ lib.optionals cfg.readonly [ "--readonly" ] ++ lib.optionals cfg.mqtt.enable [
Change:
Minimal flake to reproduce the issue: : : Disabling install checks using fixes the issue. If you uncomment the commented overlay in the minimal flake I provided, the build will succeed and the package will work properly.
+1 Same issue with same log. (tagging, as you are in maintainers list)
Looks like a bug upstream:
As per the Biopython issue linked, Debian sid is failing in the same way. Specifically, converting two annotated sequence files (one in EMBL format, one in Genbank format) into SeqXML format and then attempting to read this XML file back fails. Narrower tests from that issue: File expected is here (with .txt to the filename): This seems to fail (but shouldn't): This appears to be something breaking via the XML SAX expat parser. Can you see anything relevant which has changed on your platform to help narrow this down?
Hi, I tracked this issue down to a upgrade from 2.5.0 to 2.6.1 from Debian testing to sid. [Debian CI] suggests this could also cause regression in Python tests. Is this consistent with what you observe on Nix? If so, I strongly believe the root cause of the Biopython issue is ingrained in a bad interaction between the newer expat version and the Python interpreter, notably: [Debian CI]: In hope this helps, Étienne.
I can confirm that latest 1.84-dev works. We have to wait for update to be tagged. Until then, you can modify on to use
We have a few NumPy 2.0 test incompatibilities to fix (due to their scalar repr changes), and then we want to release Biopython 1.84 which would include the libexpat fix (moving a close earlier):

Discussion:
<ins> diff --git a/Bio/SeqIO/SeqXmlIO.py b/Bio/SeqIO/SeqXmlIO.py index 8fe75ebb728..6758317d05f 100644 --- a/Bio/SeqIO/SeqXmlIO.py +++ b/Bio/SeqIO/SeqXmlIO.py @@ -498,11 +498,12 @@ def iterate(self, handle): if not text: break parser.feed(text) +        # Closing the parser ensures that all XML data fed into it are processed +        parser.close() # We have reached the end of the XML file; # send out the remaining records yield from records records.clear() -        parser.close() class SeqXmlWriter(SequenceWriter): </ins>

<del> { lib , buildPythonPackage , fetchPypi , pythonOlder , setuptools , numpy </del> <ins> { lib, buildPythonPackage, fetchPypi, pythonOlder, setuptools, numpy, </ins> }: buildPythonPackage rec {

hash = "sha256-eOa/t43mMDQDev01/nfLbgqeW2Jwa+z3in2SKxbtg/c="; }; <del> nativeBuildInputs = [ setuptools </del> <ins> patches = [ # cherry-picked from https://github.com/biopython/biopython/commit/3f9bda7ef44f533dadbaa0de29ac21929bc0b2f1 # fixes SeqXMLIO parser to process all data. remove on next update ./close_parser_on_time.patch </ins> ]; <del> propagatedBuildInputs = [ numpy ]; </del> <ins> build-system = [ setuptools ]; </ins> <del> pythonImportsCheck = [ "Bio" ]; </del> <ins> dependencies = [ numpy ]; pythonImportsCheck = [ "Bio" ]; </ins> checkPhase = '' runHook preCheck
Change:
Steps to reproduce the behavior: Broken from , worked in . Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
If I'm reading the log correctly, this fails already when building the glibc dependency, doesn't it? After some experimentation, I came up with the changes in
Very cool, that solves it! Thank you :)

Discussion:
<del> { lib, stdenv, fetchurl, glibc, zlib, libxcrypt , enableStatic ? stdenv.hostPlatform.isStatic </del> <ins> { lib, stdenv, fetchurl, zlib, libxcrypt </ins> , enableSCP ? false , sftpPath ? "/run/current-system/sw/libexec/sftp-server" }:

sha256 = "sha256-vFoSH/vJS1FxrV6+Ab5CdG1Qqnl8lUmkY5iUoWdJRDs="; }; <del> dontDisableStatic = enableStatic; configureFlags = lib.optional enableStatic "LDFLAGS=-static"; </del> CFLAGS = lib.pipe (lib.attrNames dflags) [ (builtins.map (name: "-D${name}="${dflags.${name}}"")) (lib.concatStringsSep " ")

./pass-path.patch ]; <del> buildInputs = [ zlib libxcrypt ] ++ lib.optionals enableStatic [ glibc.static zlib.static ]; </del> <ins> buildInputs = [ zlib libxcrypt ]; </ins> meta = with lib; { description = "A small footprint implementation of the SSH 2 protocol";
Change:
Package name: hyprland Latest released version: 0.36.0 <!-- Search your package here: --- Current version on the unstable channel: 0.35.0 Current version on the stable/release channel: 0.32.3 <!-- 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]: The 035.0 has a bug that makes my system crash very often (nullptr when monitor is disconnected) the issue is supposed to be fixed in 0.36.0.

Discussion:
, cairo , git , hyprland-protocols <ins> , hyprlang </ins> , jq , libGL , libdrm

, debug ? false , enableXWayland ? true , legacyRenderer ? false <del> , withSystemd ? true </del> <ins> , withSystemd ? lib.meta.availableOn stdenv.hostPlatform systemd </ins> , wrapRuntimeDeps ? true # deprecated flags , nvidiaPatches ? false

assert lib.assertMsg (!hidpiXWayland) "The option `hidpiXWayland` has been removed. Please refer https://wiki.hyprland.org/Configuring/XWayland"; stdenv.mkDerivation (finalAttrs: { pname = "hyprland" + lib.optionalString debug "-debug"; <del> version = "0.35.0"; </del> <ins> version = "0.36.0"; </ins> src = fetchFromGitHub { owner = "hyprwm"; repo = finalAttrs.pname; rev = "v${finalAttrs.version}"; <del> hash = "sha256-dU5m6Cd4+WQZal2ICDVf1kww/dNzo1YUWRxWeCctEig="; </del> <ins> hash = "sha256-oZe4k6jtO/0govmERGcbeyvE9EfTvXY5bnyIs6AsL9U="; </ins> }; patches = [

cairo git hyprland-protocols <ins> hyprlang </ins> libGL libdrm libinput

mesonAutoFeatures = "disabled"; <del> mesonFlags = builtins.concatLists [ (lib.optional enableXWayland "-Dxwayland=enabled") (lib.optional legacyRenderer "-Dlegacy_renderer=enabled") (lib.optional withSystemd "-Dsystemd=enabled") </del> <ins> mesonFlags = [ (lib.mesonEnable "xwayland" enableXWayland) (lib.mesonEnable "legacy_renderer" legacyRenderer) (lib.mesonEnable "systemd" withSystemd) </ins> ]; postInstall = ''

hy3 = { fetchFromGitHub, cmake, hyprland }: mkHyprlandPlugin rec { pluginName = "hy3"; <del> version = "0.35.0"; </del> <ins> version = "unstable-2024-02-23"; </ins> src = fetchFromGitHub { owner = "outfoxxed"; repo = "hy3"; <del> rev = "hl${version}"; hash = "sha256-lFe7Lf0K5ePTh4gflnvBohOGH4ayGDtNkbg/XtoNqRo="; </del> <ins> rev = "029a2001361d2a4cbbe7447968dee5d1b1880298"; hash = "sha256-8LKCXwNU6wA8o6O7s9T2sLWbYNHaI1tYU4YMjHkNLZQ="; </ins> }; nativeBuildInputs = [ cmake ];

domain = "gitlab.freedesktop.org"; owner = "wlroots"; repo = "wlroots"; <del> rev = "00b869c1a96f300a8f25da95d624524895e0ddf2"; hash = "sha256-5HUTG0p+nCJv3cn73AmFHRZdfRV5AD5N43g8xAePSKM="; </del> <ins> rev = "0cb091f1a2d345f37d2ee445f4ffd04f7f4ec9e5"; hash = "sha256-Mz6hCtommq7RQfcPnxLINigO4RYSNt23HeJHC6mVmWI="; </ins> }; patches = [ ]; # don't inherit old.patches
Change:
Plasma 6 installation module is missing qt6.qtimageformats by default, which causes default image viewer, Gwenview, to not display some image formats. Steps to reproduce the behavior: a system with to open .webp file in Gwenview gives an error that format is not supported, which is (Gwenview was presumably updated to use qt6) Gwenview is a standard image viewer of KDE, and it's expected to support as much formats as it can.  Installing qt6.imageformats in environment.systemPackages fixes this issue, and I don't know of reason to not include it into standard installation. <!-- 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]:

Discussion:
mkKdeDerivation, qtsvg, qtwayland, <ins> qtimageformats, </ins> pkg-config, cfitsio, exiv2,

extraBuildInputs = [ qtsvg qtwayland <ins> # adds support for webp and other image formats qtimageformats </ins> cfitsio exiv2
Change:
Steps to reproduce the behavior: out current unstable: citrix-workspace: This also affects citrixworkspace23090 and citrixworkspace23070. system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Yeah, I ran into the same, unfortunately opencv is a massive expression, and the diff for the recent change was also massive, so inlining and overriding are IMO out. I ended up pulling opencv from a working commit ().
I observed the same issue yesterday and reached the same conclusion as Unfortunately, there is no newer version of Citrix Workspace available, leaving us with the November 2023 release that requires OpenCV 4.7. I attempted to use to enable compatibility with OpenCV 4.9, but alas without success. For now, it seems I will have to mark these packages as broken.
for anyone who has not had to mix nixpkgs versions before.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Discussion:
ln -sf $out/lib/libssl.so $out/lib/libssl.so.1.0.0 ''; }; <ins> opencv4' = symlinkJoin { name = "opencv4-compat"; nativeBuildInputs = [ makeWrapper ]; paths = [ opencv4 ]; postBuild = '' for so in ${opencv4}/lib/*.so; do ln -s "$so" $out/lib/$(basename "$so").407 done ''; }; </ins> in stdenv.mkDerivation rec {

mesa nspr nss <del> opencv4 </del> <ins> opencv4' </ins> openssl' pango speex
Change:
fcitx5-qt from libsForQt5 tries to download a nonsensical package from a non-existent repository Steps to reproduce the behavior: try to install/update libsForQt5.fcitx5-qt this workaround works. are you in control of those repositories and planning to update them to actually match what is in nixpkgs ? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The issue is me wrongfully using in place of , would fix soon.

Discussion:
src = fetchFromGitHub { owner = "fcitx"; <del> repo = pname; </del> <ins> repo = "fcitx5-qt"; </ins> rev = version; sha256 = "sha256-bVH2US/uEZGERslnAh/fyUbzR9fK1UfG4J+mOmrIE8Y="; };
Change:
vamp-plugin-sdk's repository doesn't contain the releases linked on nixpkgs this repository actually still has the releases. the metadata in nixpkgs is Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
version = "2.10"; src = fetchFromGitHub { <del> owner = "c4dm"; </del> <ins> owner = "vamp-plugins"; </ins> repo = "vamp-plugin-sdk"; rev = "vamp-plugin-sdk-v${version}"; <del> sha256 = "1lhmskcyk7qqfikmasiw7wjry74gc8g5q6a3j1iya84yd7ll0cz6"; </del> <ins> hash = "sha256-5jNA6WmeIOVjkEMZXB5ijxyfJT88alVndBif6dnUFdI="; </ins> }; nativeBuildInputs = [ pkg-config ];
Change:
Japanese input no longer works on 17.09 beta whereas it did on 17.03 stable. Add the following to your nixos configuration file: Note the output: System: 17.09beta487. (Hummingbird) Nix version: nix-env (Nix) 1.11.14 Nixpkgs version: "17.09beta487." Sandboxing enabled: build-use-sandbox = false
You need to install like python27.pygobject2/3 I believe.

Discussion:
configureFlags = [ "--with-anthy-zipcode=${anthy}/share/anthy/zipcode.t" ]; buildInputs = [ <del> anthy glib gobjectIntrospection gtk3 ibus python3 </del> <ins> anthy glib gobjectIntrospection gtk3 ibus (python3.withPackages (ps: [ps.pygobject3])) </ins> ]; nativeBuildInputs = [ intltool pkgconfig python3.pkgs.wrapPython ];
Change:
It seems that has no effect, even when using . the following to and : to rebuild locatedb (assuming you have the nixpkgs repo somewher) Expected: Files in directories are pruned. Actual: Files in directories are present in the result. I was able to work around the issue by using instead of using ; that seems to work as expected. From brief experiments running directly, it seems that the env var doesn't do anything (contrary to the documentation), so this may be an upstream bug. System: 17.03.1820. (Gorilla) Nix version: nix-env (Nix) 1.11.14 Nixpkgs version: "17.03.1820." Sandboxing enabled: false

Discussion:
Whether not to index bind mounts ''; }; }; config = mkIf cfg.enable {

systemd.services.update-locatedb = { description = "Update Locate Database"; path = mkIf (!isMLocate) [ pkgs.su ]; <ins> # mlocate's updatedb takes flags via a configuration file or # on the command line, but not by environment variable. </ins> script = <ins> if isMLocate then let toFlags = x: optional (cfg.${x} != []) "--${lib.toLower x} '${concatStringsSep " " cfg.${x}}'"; args = concatLists (map toFlags ["pruneFS" "pruneNames" "prunePaths"]); in '' exec ${cfg.locate}/bin/updatedb  --output ${toString cfg.output} ${concatStringsSep " " args}  --prune-bind-mounts ${if cfg.pruneBindMounts then "yes" else "no"}  ${concatStringsSep " " cfg.extraFlags} </ins> '' <ins> else '' </ins> exec ${cfg.locate}/bin/updatedb  ${optionalString (cfg.localuser != null && ! isMLocate) ''--localuser=${cfg.localuser}''}  --output=${toString cfg.output} ${concatStringsSep " " cfg.extraFlags} ''; <del> environment = { </del> <ins> environment = optionalAttrs (!isMLocate) { </ins> PRUNEFS = concatStringsSep " " cfg.pruneFS; PRUNEPATHS = concatStringsSep " " cfg.prunePaths; PRUNENAMES = concatStringsSep " " cfg.pruneNames;
Change:
Setting nixos option to null, which is legal according to typechecks results in an invalid disk size value passed to Launching the script, aka system build attribute , will throw an error at the disk creation stage mentioning an invalid argument for the size parameter. Steps to reproduce the behavior: new flake output attribute with value of basic nixosSystem option attribute ./result Launching ./result will create a qcow disk and launch qemu with the machine configuration. I found this bug through changes in nixos-generators. I've created an issue in their repo first, but their changes might be technically correct. REF; No maintainers list within that nixos module file. Pinging as last change author on the type of virtualisation.disksize. <!-- 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]:
I don't remember why I've set this option to . From the commit that it () it's clear that null is not handled, so it's probably a mistake.
Just stumbled upon this issue and agree with the analysis here. PR at

Discussion:
virtualisation.diskSize = mkOption { <del> type = types.nullOr types.ints.positive; </del> <ins> type = types.ints.positive; </ins> default = 1024; description = '' The disk size in megabytes of the virtual machine.