jiebi/CodeConvo huggingface dataset:
Change:
is currently an alias for , which is on PyPI. However, there's another completely unrelated package named on PyPI, which Nixpkgs doesn't package at the moment. I think should refer to that one (or be removed to avoid confusion). Steps to reproduce the behavior: The import succeeds and can be used to access the module. If applicable, add screenshots to help explain your problem. I ran into this while trying to package something that depends on pyjson5 (), and was very confused why pyjson5 wasn't being found even though it was in my . <!-- 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:
<ins> { lib, buildPythonPackage, cython, fetchFromGitHub, pythonOlder, setuptools, wheel, }: buildPythonPackage rec { pname = "pyjson5"; version = "1.6.6"; pyproject = true; disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "Kijewski"; repo = "pyjson5"; rev = "refs/tags/v${version}"; hash = "sha256-LNcz9JEOw6HO9eIf71w4NJdPOB4yixBfBeD7B/NLbfE="; fetchSubmodules = true; }; build-system = [ cython setuptools wheel ]; # Module has no tests doCheck = false; pythonImportsCheck = [ "pyjson5" ]; meta = with lib; { description = "A JSON5 serializer and parser library"; homepage = "https://github.com/Kijewski/pyjson5"; changelog = "https://github.com/Kijewski/pyjson5/blob/${version}/CHANGELOG.md"; license = licenses.asl20; maintainers = with maintainers; [ fab ]; }; } </ins>

pyialarmxr = pyialarmxr-homeassistant; # added 2022-06-07 pyialarmxr-homeassistant = throw "The package was removed together with the component support in home-assistant 2022.7.0"; # added 2022-07-07 PyICU = pyicu; # Added 2022-12-22 <del> pyjson5 = json5; # added 2022-08-28 </del> pyhs100 = throw "pyhs100 has been removed in favor of python-kasa."; # added 2024-01-05 pylibgen = throw "pylibgen is unmaintained upstreamed, and removed from nixpkgs"; # added 2020-06-20 PyLD = pyld; # added 2022-06-22

pyjnius = callPackage ../development/python-modules/pyjnius { }; <ins> pyjson5 = callPackage ../development/python-modules/pyjson5 { }; </ins> pyjsparser = callPackage ../development/python-modules/pyjsparser { }; pyjwkest = callPackage ../development/python-modules/pyjwkest { };
Change:
Right now ipfs module puts in a into However if other modules also make use of fuse, how would these settings be resolved? Should there be an option for fuse settings, that all modules make use of, and can alert errors if there are conflicting entries? We need to have a centralised option for configuring the usable by all services like IPFS or SSHFS or S3FS... etc.
Sounds good. (But perhaps also have an "extraConfig" option as escape hatch.)
Was there any PR being open relating to this issue? Maybe rephrasing an issue to sound more like a feature request then a question, would be better. Also it wouldn't hurt bringing this up on the mailing list.
No PR that I know of. But yea I think there should be a new option in NixOS for this.
Do I understand correctly that there are only two options that could be specified in ? ( and )
Yeah, I can't get fuse to read my file. Is there a workaround or any progress on a final solution? I'm trying to get fuse to respect , but I can't find any way at the moment.
See The fix has been to and .
Is this issue finally resolved? Is there nixos options to set this config?
Not yet, but I've just created a PR () as it seems to become quite relevant.

Discussion:
./programs/firejail.nix ./programs/fish.nix ./programs/freetds.nix <ins> ./programs/fuse.nix </ins> ./programs/gnome-disks.nix ./programs/gnome-documents.nix ./programs/gpaste.nix

<ins> { config, lib, ... }: with lib; let cfg = config.programs.fuse; in { meta.maintainers = with maintainers; [ primeos ]; options.programs.fuse = { mountMax = mkOption { # In the C code it's an "int" (i.e. signed and at least 16 bit), but # negative numbers obviously make no sense: type = types.ints.between 0 32767; # 2^15 - 1 default = 1000; description = '' Set the maximum number of FUSE mounts allowed to non-root users. ''; }; userAllowOther = mkOption { type = types.bool; default = false; description = '' Allow non-root users to specify the allow_other or allow_root mount options, see mount.fuse3(8). ''; }; }; config =  { environment.etc."fuse.conf".text = '' ${optionalString (!cfg.userAllowOther) "#"}user_allow_other mount_max = ${toString cfg.mountMax} ''; }; } </ins>

config = mkIf cfg.enable { environment.systemPackages = [ wrapped ]; <del> environment.etc."fuse.conf" = mkIf cfg.autoMount { text = '' user_allow_other ''; }; </del> <ins> programs.fuse = mkIf cfg.autoMount { userAllowOther = true; }; </ins> users.users = mkIf (cfg.user == "ipfs") { ipfs = {
Change:
Steps to reproduce the behavior: font-manager-0.8.8 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]:
The same issue currently keeps my system from building

Discussion:
, gtk3 , gnome , desktop-file-utils <ins> , fetchpatch2 </ins> , wrapGAppsHook3 , gobject-introspection # withWebkit enables the "webkit" feature, also known as Google Fonts

hash = "sha256-M13Q9d2cKhc0tudkvw0zgqPAFTlmXwK+LltXeuDPWxo="; }; <ins> patches = [ # see https://github.com/FontManager/font-manager/issues/355 # should be removed on next release (fetchpatch2 { name = "fix-build-with-newer-vala.patch"; url = "https://github.com/FontManager/font-manager/commit/600f498946c3904064b4e4fdf96e5841f6a827e4.patch"; hash = "sha256-DC9+pvG88t+PPdGQ2oemeEYK9PaD0C2yWBYYCh4Wn9g="; }) ]; </ins> nativeBuildInputs = [ pkg-config meson
Change:
On MacOS Sonoma 14.4.1 on an M1 Macbook Pro, with nixpkgs pinned at , building fails when compiling : , but here's an excerpt of the failures from the command: I pin nixpkgs in the flake user registry, and reference it in my darwin configuration. Previously I had it pinned to , and on this same computer, building against that commit still works I didn't do a full bisect, but I also can verify that the following pinned commit also works: Maintainers from : Recent committers not already included: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Technically not a build failure of ffmpeg but we should get libdevil out of the closure if it's broken.
The offending package should be a rather easy workaround via but I currently do not have access to a mac.
Apologies for mislabeling the report, and thank you for (a) correcting it, (b) the quick response. If you give me a command to run, I can help by running it and telling you if it works!
Setting in the mkDerivation call of the package should do it.
sorry, I'm not that experienced with Nix, can you share a snippet of code doing it? Do I need to do it for ffmpeg-full, or just for libdevil? Do I do this in my flake that says to install ffmpeg-full somehow? If it's easier to just fix it yourself without me, feel free to ignore. Thanks again for the quick response by merging
OK, seems to work with this overlay on :

Discussion:
configureFlags = [ "--enable-ILU" "--enable-ILUT" ]; <ins> CXXFLAGS = lib.optionalString stdenv.cc.isClang "-Wno-register"; </ins> preConfigure = '' sed -i 's, -std=gnu99,,g' configure sed -i 's,malloc.h,stdlib.h,g' src-ILU/ilur/ilur.c
Change:
This is a quote from : This looks like a todo item, but I couldn't find an issue for it, so I'm creating that issue here. I also have a question: Does this mean you have to restart Nginx the first time to ACME certs arrive, or every time they renew? And do I understand correctly that this recurring manual task kind of defeats the purpose of using ACME while this issue is still open? (Should we update the manual in the meantime to clarify that the ACME feature isn't really usable yet?)
As far as I'm aware and this includes me using ACME a lot, this no longer is necessary, can you open a PR removing that line?
Sure thing
Thanks for the doc fixes!
I just had had a case where the LE certificate was renewed but the change was not picked up by nginx (until I manually restarted nginx) (few weeks old 17.09). Seems like this is still necessary.
Just to be sure, are you letting Nix generate the relevant nginx config (via setting the option)? I ask because I had that problem for a while because I didn't know you had to do that, and enabling this seems to be what's supposed to cause nginx to reload when certs arrive.
Yup, nginx config is generated with and enableAcme is true for all 3 vhosts. All the acme stuff seems to be working fine and according to the logs nginx was reloaded: (please ignore the unusual formatting as this is extracted from Graylog as the original journal entry was no longer available due to log rotation) I can see no error/warning of any kind. Just a moment after nginx reload is completed the acme unit startup is completed so it looks ok but nginx was still using the old certificates. According to some quick research it should be sufficient to send SIGHUP to nginx which is exactly what is done at so I have no idea why it is not working. This is the 2nd time this has happened to me. I dismissed the first one as I was unsure of the circumstances. It is quite hard to debug as one usually only notices the issue days(weeks) later when the certificate is expired.

Discussion:
}; } </programlisting> <del> <para>At the moment you still have to restart Nginx after the ACME certs arrive.</para> </del> </section> </chapter>
Change:
Trying to use Steps to reproduce the behavior: command exits with status 1 with the following error: A shell is opened. In this shell, returns a 0 exit code, like it is with python3.10. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. ping Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
aren't in the repo. You need to use or
Seems to exist just fine. Anyway, as the error says, 3.9 isn't supported for the package that throws said error, so you'll have to use a newer python. 3.9 is only getting security fixes anyway atm, so it's probably not suitable for normal use.
We have the following package sets available, but as of 23.11, only the python310 and python311 package sets are actively maintained.
My use case is to provide several dev shell for a python lib I develop. That's why I care for python39 while it is not EOL. I think we need to use an older debugpy for python39. Does nixpkgs provides this kind of facility?
You can use or git history to find a suitable nixpkgs commit from which to base the shell
It is impossible to maintain them on the main line due to lack of time, but if you submit a PR, I will be happy to review it.

Discussion:
stdenv, buildPythonPackage, pythonOlder, <ins> pythonAtLeast, </ins> fetchFromGitHub, substituteAll, gdb,

} )''; <ins> # Disable tests for unmaintained versions of python doCheck = pythonAtLeast "3.11"; </ins> nativeCheckInputs = [ ## Used to run the tests: pytestCheckHook
Change:
Steps to reproduce the behavior: llvm on like this Broken on 14, 15, 16, 17, 18 and git versions. Likely broken by See also <!-- 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]:
in package should be fine I guess

Discussion:
, sysctl , buildLlvmTools , debugVersion ? false <del> , doCheck ? (if lib.versionOlder release_version "15" then stdenv.isLinux else true) </del> <ins> , doCheck ? !stdenv.isAarch32 && (if lib.versionOlder release_version "15" then stdenv.isLinux else true) </ins> && (!stdenv.isx86_32 /* TODO: why */) && (!stdenv.hostPlatform.isMusl) && (stdenv.hostPlatform == stdenv.buildPlatform) , enableManpages ? false
Change:
When I try to open the warp-terminal on wayland it crashes without opening any window and get the following logs: Steps to reproduce the behavior: to open warp-terminal happens It should open the warp-terminal window and prompt. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Might be helpful:
Fixed in , I tried running () on KDE Wayland and everything works as expected
A warp-terminal dev has stated that wayland support is explicitly still experimental and off by default for this reason. Please do not open issues concerning configurations that are explicitly unsupported by upstream.
Sorry, I didn't know it was explicitly unsupported by the upstream since it was working before just fine on Wayland. Thanks a lot anyway!

Discussion:
homepage = "https://www.warp.dev"; license = licenses.unfree; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; <del> maintainers = with maintainers; [ emilytrau Enzime imadnyc ]; </del> <ins> maintainers = with maintainers; [ emilytrau Enzime imadnyc donteatoreo ]; </ins> platforms = platforms.darwin ++ [ "x86_64-linux" ]; };

{ "darwin": { <del> "hash": "sha256-oIRZtj1BZWioO1ucEXnJQoz/FfDNHWLdYLExuLk+aJk=", "version": "0.2024.04.23.08.01.stable_03" </del> <ins> "hash": "sha256-Ky5JyocpI9JKvhmmhk0Cg/Eo7icmo6FQAT639cGIGrA=", "version": "0.2024.05.07.08.02.stable_02" </ins> }, "linux": { <del> "hash": "sha256-R9//eoelQkH8OAhoU0ux+o1EpQozWhRJwCTTSY9LBGU=", "version": "0.2024.04.23.08.01.stable_03" </del> <ins> "hash": "sha256-zUbWNgiupBoFWoN3I726FejGtGne9dctaiGlPBbj5KU=", "version": "0.2024.05.07.08.02.stable_02" </ins> } }
Change:
Steps to reproduce the behavior: Home-Assistant service It started failing yesterday. It built fine a day before. It looks like for some reason 1.10.14 is dragged in as dependency event though 2.6.3 is now the default. I don't know Nix or Python well enough to figure out what exactly goes wrong. It looks like it's required for HACS (Home-Assistant Community Store) add-on, probably others as well. <!-- 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]:
nixpkgs . Perhaps it's because ..? I'm not really sure since it does seem to build fine with pydantic 2 here.
This won't really get maintainer attention unless they are tagged:
aiogithubapi pins sigstore<2, but that was unpinned in .

Discussion:
}; }); <ins> # newer sigstore version transitivevly require pydantic>=2 sigstore = super.sigstore.overridePythonAttrs (oldAttrs: rec { version = "1.1.2"; src = fetchFromGitHub { owner = "sigstore"; repo = "sigstore-python"; rev = "refs/tags/v${version}"; hash = "sha256-QqY5GOBS75OkbSaF5Ua5jnJAhsYfVRuWLUoWDxX8Ino="; }; dependencies = with self; [ appdirs cryptography id pydantic pyjwt pyopenssl requests securesystemslib sigstore-protobuf-specs tuf ]; doCheck = false; # pytest too new }); sigstore-protobuf-specs = super.sigstore-protobuf-specs.overridePythonAttrs { version = "0.1.0"; src = fetchPypi { pname = "sigstore-protobuf-specs"; version = "0.1.0"; hash = "sha256-YistIxYToo7T5mYKzYeBhnW06DSG9JoPDBmKxUdfy4E="; }; nativeBuildInputs = with self; [ flit-core pythonRelaxDepsHook ]; pythonRelaxDeps = [ "betterproto" ]; }; </ins> tesla-powerwall = super.tesla-powerwall.overridePythonAttrs (oldAttrs: rec { version = "0.5.1"; src = fetchFromGitHub {

}; }); <ins> tuf = super.tuf.overridePythonAttrs rec { version = "2.1.0"; src = fetchFromGitHub { owner = "theupdateframework"; repo = "python-tuf"; rev = "refs/tags/v${version}"; hash = "sha256-MdPctAZuKn/YAwpMJ5gWU7PXJD3iK7bYprLXV52wNQQ="; }; disabledTests = [ "test_sign_failures" ]; }; </ins> versioningit = super.versioningit.overridePythonAttrs { doCheck = false; };

buildPythonPackage rec { pname = "homeassistant-stubs"; <del> version = "2024.5.1"; </del> <ins> version = "2024.5.2"; </ins> format = "pyproject"; disabled = python.version != home-assistant.python.version;

owner = "KapJI"; repo = "homeassistant-stubs"; rev = "refs/tags/${version}"; <del> hash = "sha256-lYoYU39/ayZb8Ue25a7uSN5x8tihzjj5mGaVKWPfa1w="; </del> <ins> hash = "sha256-bgXHEz8YuHcdGYzLpM7H8IVXixFC8Bz0i4SaatA49Qo="; </ins> }; nativeBuildInputs = [
Change:
As title says, openrazer-daemon no longer work after update. Steps to reproduce the behavior: system -daemon fail to start. Openrazer-daemon start on boot. If applicable, add screenshots to help explain your problem. Manually calling openrazer-daemon -Fv print me this: <!-- 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]:
overlay fix for anyone who have this issue.
This overlay fix worked for me, thank you!

Discussion:
, fetchFromGitHub , fetchpatch , installShellFiles <ins> , wrapGAppsNoGuiHook , gobject-introspection </ins> , libcdio-paranoia , cdrdao , libsndfile <ins> , glib </ins> , flac , sox , util-linux

nativeBuildInputs = with python3.pkgs; [ installShellFiles <ins> wrapGAppsNoGuiHook gobject-introspection </ins> setuptools-scm docutils

setuptools ]; <del> buildInputs = [ libsndfile ]; </del> <ins> buildInputs = [ libsndfile glib ]; </ins> nativeCheckInputs = with python3.pkgs; [ twisted

makeWrapperArgs = [ "--prefix" "PATH" ":" (lib.makeBinPath bins) <ins> "${gappsWrapperArgs[@]}" </ins> ]; <ins> dontWrapGApps = true; </ins> outputs = [ "out" "man" ]; postBuild = '' make -C man

setuptools, wrapGAppsNoGuiHook, notify2, <ins> glib </ins> }: let

--replace-fail "plugdev" "openrazer" ''; <del> nativeBuildInputs = [ setuptools wrapGAppsNoGuiHook ]; </del> <ins> nativeBuildInputs = [ setuptools wrapGAppsNoGuiHook gobject-introspection ]; buildInputs = [ glib gtk3 ]; </ins> propagatedBuildInputs = [ daemonize dbus-python <del> gobject-introspection gtk3 </del> pygobject3 pyudev setproctitle

<del> { lib, stdenv, fetchFromGitHub, meson, ninja, pkg-config </del> <ins> { lib, stdenv, fetchFromGitHub, meson, ninja, pkg-config, wrapGAppsNoGuiHook, gobject-introspection </ins> , glib, systemd, udev, libevdev, gitMinimal, check, valgrind, swig, python3 , json-glib, libunistring }:

}; nativeBuildInputs = [ <del> meson ninja pkg-config gitMinimal swig check valgrind </del> <ins> meson ninja pkg-config gitMinimal swig check valgrind wrapGAppsNoGuiHook gobject-introspection </ins> ]; buildInputs = [

<del> { lib, python3, fetchFromGitHub, nixosTests }: </del> <ins> { lib, python3, fetchFromGitHub, nixosTests, wrapGAppsNoGuiHook, gobject-introspection, glib }: </ins> python3.pkgs.buildPythonApplication rec { pname = "targetcli";

hash = "sha256-9QYo7jGk9iWr26j0qPQCqYsJ+vLXAsO4Xs7+7VT9/yc="; }; <del> propagatedBuildInputs = with python3.pkgs; [ configshell rtslib ]; </del> <ins> nativeBuildInputs = [ wrapGAppsNoGuiHook gobject-introspection ]; buildInputs = [ glib ]; propagatedBuildInputs = with python3.pkgs; [ configshell rtslib pygobject3 ]; </ins> postInstall = '' install -D targetcli.8 -t $out/share/man/man8/
Change:
Steps to reproduce the behavior: to NixOS config Successfully start. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
, fetchpatch , python3Packages , asciidoc <del> , makeWrapper </del> <ins> , wrapGAppsNoGuiHook </ins> , iw }:

nativeBuildInputs = [ asciidoc <del> makeWrapper </del> <ins> wrapGAppsNoGuiHook </ins> python3Packages.wrapPython ]; <ins> dontWrapGApps = true; </ins> checkInputs = with python3Packages; [ dbus-python iw

doCheck = true; <ins> preFixup = '' makeWrapperArgs+=(  "''${gappsWrapperArgs[@]}"  --prefix PATH : "${lib.makeBinPath [ iw ]}"  ) ''; </ins> postFixup = '' wrapPythonPrograms <del> wrapProgram $out/bin/networkd-dispatcher --prefix PATH : ${lib.makeBinPath [ iw ]} </del> ''; meta = with lib; {
Change:
Project description A fast and customizable music and podcast downloader. Metadata homepage URL: source URL: license: zlib platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
githubId = 25644444; name = "Ben C"; }; <ins> bwkam = { email = "beshoykamel391@gmail.com"; github = "bwkam"; githubId = 91009118; name = "Beshoy Kamel"; }; </ins> bwlang = { email = "brad@langhorst.com"; github = "bwlang";

<ins> { fetchFromGitHub, python3Packages, lib, }: python3Packages.buildPythonApplication rec { pname = "zotify"; version = "0.6.13"; pyproject = true; src = fetchFromGitHub { owner = "zotify-dev"; repo = "zotify"; # repository has no version tags # https://github.com/zotify-dev/zotify/issues/124 rev = "5da27d32a1f522e80a3129c61f939b1934a0824a"; hash = "sha256-KA+Q4sk+riaFTybRQ3aO5lgPg4ECZE6G+By+x2uP/VM="; }; build-system = [ python3Packages.setuptools ]; nativeBuildInputs = [ python3Packages.pythonRelaxDepsHook ]; pythonRelaxDeps = [ "protobuf" ]; dependencies = with python3Packages; [ ffmpy music-tag pillow tabulate tqdm librespot pwinput protobuf ]; pythonImportsCheck = [ "zotify" ]; meta = { description = "Fast and customizable music and podcast downloader"; homepage = "https://github.com/zotify-dev/zotify"; license = lib.licenses.zlib; mainProgram = "zotify"; maintainers = with lib.maintainers; [ bwkam ]; }; } </ins>

<ins> { buildPythonPackage, fetchPypi, setuptools, lib, pythonOlder, }: buildPythonPackage rec { pname = "pwinput"; version = "1.0.3"; pyproject = true; disabled = pythonOlder "3.7"; src = fetchPypi { inherit version; pname = "pwinput"; hash = "sha256-yhqL0G4ohy11Hb1BMthjcSfCW0COo6NJN3MUpUkUJvM="; }; build-system = [ setuptools ]; pythonImportsCheck = [ "pwinput" ]; # Requires graphical environment to use pyautogui doCheck = false; meta = { description = "Python module that masks password input"; homepage = "https://github.com/asweigart/pwinput"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ bwkam ]; }; } </ins>

pyaprilaire = callPackage ../development/python-modules/pyaprilaire { }; <ins> pwinput = callPackage ../development/python-modules/pwinput { }; </ins> pybars3 = callPackage ../development/python-modules/pybars3 { }; pymeta3 = callPackage ../development/python-modules/pymeta3 { };