jiebi/CodeConvo huggingface dataset:
Code change:
According to the 3.5 life-cycle () , the final release has already occurred and is now considered EOL. The jump from 3.5 to 3.6 has already happened in the majority of python packages and should not be a similar situation in which we had to extend python2's life long after its official EOL date.

Related discussion:
text: <del> { lib , stdenv , buildPythonPackage , fetchPypi , pythonOlder # Build dependencies , glibcLocales # Test dependencies , nose , pygments # Runtime dependencies , jedi , decorator , pickleshare , traitlets , prompt_toolkit , pexpect , appnope , backcall , fetchpatch }: buildPythonPackage rec { pname = "ipython"; version = "7.9.0"; src = fetchPypi { inherit pname version; sha256 = "103jkw18z7fnwdal1mdbijjxi1fndzn31g887lmj7ddpf2r07lyz"; }; prePatch = lib.optionalString stdenv.isDarwin '' substituteInPlace setup.py --replace "'gnureadline'" " " ''; buildInputs = [ glibcLocales ]; checkInputs = [ nose pygments ]; propagatedBuildInputs = [ jedi decorator pickleshare traitlets prompt_toolkit pygments pexpect backcall ] ++ lib.optionals stdenv.isDarwin [appnope]; LC_ALL="en_US.UTF-8"; doCheck = false; # Circular dependency with ipykernel checkPhase = '' nosetests ''; pythonImportsCheck = [ "IPython" ]; meta = with lib; { description = "IPython: Productive Interactive Computing"; homepage = "http://ipython.org/"; license = licenses.bsd3; maintainers = with maintainers; [ bjornfor ]; }; } </del>
Code change:
According to the 3.5 life-cycle () , the final release has already occurred and is now considered EOL. The jump from 3.5 to 3.6 has already happened in the majority of python packages and should not be a similar situation in which we had to extend python2's life long after its official EOL date.

Related discussion:
text: python2Full = python2.override{x11Support=true;}; python27Full = python27.override{x11Support=true;}; python3Full = python3.override{x11Support=true;}; <del> python35Full = python35.override{x11Support=true;}; </del> python36Full = python36.override{x11Support=true;}; python37Full = python37.override{x11Support=true;}; python38Full = python38.override{x11Support=true;};
Code change:
According to the 3.5 life-cycle () , the final release has already occurred and is now considered EOL. The jump from 3.5 to 3.6 has already happened in the majority of python packages and should not be a similar situation in which we had to extend python2's life long after its official EOL date.

Related discussion:
text: python3Packages = python3.pkgs; pythonInterpreters = callPackage ./../development/interpreters/python {}; <del> inherit (pythonInterpreters) python27 python35 python36 python37 python38 python39 python3Minimal pypy27 pypy36; </del> <ins> inherit (pythonInterpreters) python27 python36 python37 python38 python39 python3Minimal pypy27 pypy36; </ins> # Python package sets. python27Packages = lib.hiPrioSet (recurseIntoAttrs python27.pkgs); <del> python35Packages = python35.pkgs; </del> python36Packages = python36.pkgs; python37Packages = recurseIntoAttrs python37.pkgs; python38Packages = recurseIntoAttrs python38.pkgs;
Code change:
According to the 3.5 life-cycle () , the final release has already occurred and is now considered EOL. The jump from 3.5 to 3.6 has already happened in the majority of python packages and should not be a similar situation in which we had to extend python2's life long after its official EOL date.

Related discussion:
text: ipython = if isPy27 then callPackage ../development/python-modules/ipython/5.nix { } <del> else if isPy35 then callPackage ../development/python-modules/ipython/7.9.nix { } </del> else callPackage ../development/python-modules/ipython { };
Code change:
According to the 3.5 life-cycle () , the final release has already occurred and is now considered EOL. The jump from 3.5 to 3.6 has already happened in the majority of python packages and should not be a similar situation in which we had to extend python2's life long after its official EOL date.

Related discussion:
text: ) super.ocaml-ng; python27 = super.python27.override { static = true; }; <del> python35 = super.python35.override { static = true; }; </del> python36 = super.python36.override { static = true; }; python37 = super.python37.override { static = true; }; python38 = super.python38.override { static = true; };
Code change:
I am building nixos against the latest head and I get this warning message when running my Makefile command in my configuration It seems like it warns you about the obsolete option even after you've removed it from your configuration.
That's because it's used internally
It should be fine now, I believe. Thanks.

Related discussion:
text: {stdenv, fetchurl}: stdenv.mkDerivation rec { <del> name = "ncompress-4.2.4.3"; </del> <ins> name = "ncompress-4.2.4.4"; </ins> builder = ./builder.sh;
Code change:
I am building nixos against the latest head and I get this warning message when running my Makefile command in my configuration It seems like it warns you about the obsolete option even after you've removed it from your configuration.
That's because it's used internally
It should be fine now, I believe. Thanks.

Related discussion:
text: src = fetchurl { url = "mirror://sourceforge/project/ncompress/${name}.tar.gz"; <del> sha256 = "1y44ixc1w2vfvj1lm4dkcljlwv882ynrvm5i6l0lg1gf883j246l"; </del> <ins> sha256 = "0yjiwv1hwb253x3m6r1dq2k7m5c9nz0ib2j7fnm3hark7y6s42xh"; </ins> }; meta = {
Code change:
Describe the bug After fixing the the evaluation of the in I realized that it occasionally breaks with the following error: node1: output: PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. --- 10.0.0.2 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4085ms error: Traceback (most recent call last): File "/nix/store/b6m9jif1kib2dqc6fy2ym31vzs4f7hhd-nixos-test-", line 830, in run_tests exec(tests, globals()) File "<string", line 1, in <moduleFile "<string", line 8, in <moduleFile "/nix/store/b6m9jif1kib2dqc6fy2ym31vzs4f7hhd-nixos-test-", line 363, in succeed raise Exception( Exception: command failed (exit code 1) cleaning up killing node1 (pid 6) killing node2 (pid 18) error: --- Error
nix-build error: --- Error --- nix-daemon builder for '/nix/store/g14icd814yvak6syxjimgc6g8y459ki1-vm-test-run-' failed with exit code 1 Please note that the functionality isn't broken per se, on I managed to successfully build it as . Notify maintainers cc
I'm guessing that having the pings be would resolve this, unless we want to assert that actually ensures that the peers are fully connected?
No it doesn't, I already tried this out, the command times out then. I guess that sometimes the isn't configured properly.
The issue is coming from the private key (/run/wg-priv), for some reason, it looks like networkd is sometimes trying to load it to wireguard before the systemd tmpfile gets linked.

Related discussion:
text: virtualisation.vlans = [ 1 ]; environment.systemPackages = with pkgs; [ wireguard-tools ]; boot.extraModulePackages = [ config.boot.kernelPackages.wireguard ]; <del> systemd.tmpfiles.rules = [ "f /run/wg_priv 0640 root systemd-network - ${privk}" ]; </del> systemd.network = { enable = true; netdevs = { "90-wg0" = { netdevConfig = { Kind = "wireguard"; Name = "wg0"; }; wireguardConfig = { <del> PrivateKeyFile = "/run/wg_priv"; </del> <ins> # NOTE: we're storing the wireguard private key in the #       store for this test. Do not do this in the real #       world. Keep in mind the nix store is #       world-readable. PrivateKeyFile = pkgs.writeText "wg0-priv" privk; </ins> ListenPort = 51820; FirewallMark = 42; };
Code change:
Describe the bug The last several Hydra trunk-combined runs have been blocked by (among other problems) a , which was recently back(?) to release-combined in (). When I run the test locally it sometimes succeeds and sometimes hangs forever. To Reproduce Steps to reproduce the behavior: it succeeded, clear the result with (is there a better way to do that?) and try again. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(anders): nixpkgs: Maintainer information:
We have a lot of channel blockers currently, so I recommend to also purpose revert this one. Though it sounds like it's only with issues, so perhaps comment it linking to this issue. We can always re-add it.

Related discussion:
text: (onFullSupported "nixos.tests.networking.networkd.dhcpSimple") (onFullSupported "nixos.tests.networking.networkd.link") (onFullSupported "nixos.tests.networking.networkd.loopback") <del> (onFullSupported "nixos.tests.networking.networkd.macvlan") </del> <ins> # Fails nondeterministically (https://github.com/NixOS/nixpkgs/issues/96709) #(onFullSupported "nixos.tests.networking.networkd.macvlan") </ins> (onFullSupported "nixos.tests.networking.networkd.privacy") (onFullSupported "nixos.tests.networking.networkd.routes") (onFullSupported "nixos.tests.networking.networkd.sit")
Code change:
, CVSSv3=7.7 (nixos-unstable) CVSSv3=7.5 (nixos-unstable) CVSSv3=7.1 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) Scanned versions: nixos-unstable: . Cc Cc

Related discussion:
text: buildGoPackage rec { pname = "etcd"; <del> version = "3.3.22"; </del> <ins> version = "3.3.25"; </ins> goPackagePath = "github.com/coreos/etcd";
Code change:
, CVSSv3=7.7 (nixos-unstable) CVSSv3=7.5 (nixos-unstable) CVSSv3=7.1 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) Scanned versions: nixos-unstable: . Cc Cc

Related discussion:
text: owner = "etcd-io"; repo = "etcd"; rev = "v${version}"; <del> sha256 = "1rd390qfx9k20j9gh1wp1g9ygc571f2kv1dg2wvqij3kwydhymcj"; </del> <ins> sha256 = "10cyy6jr2xzmla5yyn850cv323ixrk70fjpk8lxjjjvy0ffmb6hj"; </ins> }; buildPhase = ''
Code change:
, CVSSv3=7.7 (nixos-unstable) CVSSv3=7.5 (nixos-unstable) CVSSv3=7.1 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) CVSSv3=6.5 (nixos-unstable) Scanned versions: nixos-unstable: . Cc Cc

Related discussion:
text: install -Dm755 bin/* bin/functional/cmd/* -t $out/bin ''; <del> passthru.tests = with nixosTests; { etcd = etcd; etcd-cluster = etcd-cluster; }; </del> <ins> passthru.tests = { inherit (nixosTests) etcd etcd-cluster; }; </ins> meta = with lib; { description = "Distributed reliable key-value store for the most critical data of a distributed system";
Code change:
If you want root access to an NFS share secured with Kerberos, you need to modify the default . Currently, I override the source, because NixOS has no options to modify : The text is mostly copied from the default NixOS . The only changes are This solution is brittle, and requires manual intervention if the default ever changes. I'm not sure exactly what the NixOS options should look like, but there should be mechanisms to modify in NixOS. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
what about an option like so you can easily override/append values as you see fit?
That looks great. I'm a big fan of RFC 42 :) Just one question though. Can you remove an option, such as ?
Good question. can we bug you for some advice on how you can remove values from a option?
There's nothing builtin for that. The best that can be done is to just filter out values during string generation. Though in INI's case, is also a valid value in INI files, so that might not be a great idea. There is that adds a way to "unset" values, though I haven't looked into it much.
Thanks for mentioning without the ability to remove values would this not work?
I did a double-check on , and it looks like and are actually separate, but related. defaults to the value of . Also, the default value of is already , so removing it in my configuration had no effect. On that note, we may consider removing , as that is already the default. Regardless, your RFC 42 solution should work, even without the ability to remove values.
are you interested in opening a PR? Feel free to use the branch I posted.
I can open a pull request. Just one question: is there a reason the option and variables are called instead of ?
Typo
pull request is up. I fixed the typo and a syntax error.

Related discussion:
text: rpcMountpoint = "${nfsStateDir}/rpc_pipefs"; <del> idmapdConfFile = pkgs.writeText "idmapd.conf" '' [General] Pipefs-Directory = ${rpcMountpoint} ${optionalString (config.networking.domain != null) "Domain = ${config.networking.domain}"} [Mapping] Nobody-User = nobody Nobody-Group = nogroup [Translation] Method = nsswitch ''; </del> <ins> format = pkgs.formats.ini {}; idmapdConfFile = format.generate "idmapd.conf" cfg.idmapd.settings; </ins> nfsConfFile = pkgs.writeText "nfs.conf" cfg.extraConfig; requestKeyConfFile = pkgs.writeText "request-key.conf" '' create id_resolver * * ${pkgs.nfs-utils}/bin/nfsidmap -t 600 %k %d
Code change:
If you want root access to an NFS share secured with Kerberos, you need to modify the default . Currently, I override the source, because NixOS has no options to modify : The text is mostly copied from the default NixOS . The only changes are This solution is brittle, and requires manual intervention if the default ever changes. I'm not sure exactly what the NixOS options should look like, but there should be mechanisms to modify in NixOS. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
what about an option like so you can easily override/append values as you see fit?
That looks great. I'm a big fan of RFC 42 :) Just one question though. Can you remove an option, such as ?
Good question. can we bug you for some advice on how you can remove values from a option?
There's nothing builtin for that. The best that can be done is to just filter out values during string generation. Though in INI's case, is also a valid value in INI files, so that might not be a great idea. There is that adds a way to "unset" values, though I haven't looked into it much.
Thanks for mentioning without the ability to remove values would this not work?
I did a double-check on , and it looks like and are actually separate, but related. defaults to the value of . Also, the default value of is already , so removing it in my configuration had no effect. On that note, we may consider removing , as that is already the default. Regardless, your RFC 42 solution should work, even without the ability to remove values.
are you interested in opening a PR? Feel free to use the branch I posted.
I can open a pull request. Just one question: is there a reason the option and variables are called instead of ?
Typo
pull request is up. I fixed the typo and a syntax error.

Related discussion:
text: options = { services.nfs = { <ins> idmapd.settings = mkOption { type = format.type; default = {}; description = '' libnfsidmap configuration. Refer to <link xlink:href="https://linux.die.net/man/5/idmapd.conf"/> for details. ''; example = literalExample '' { Translation = { GSS-Methods = "static,nsswitch"; }; Static = { "root/hostname.domain.com@REALM.COM" = "root"; }; } ''; }; </ins> extraConfig = mkOption { type = types.lines; default = "";
Code change:
If you want root access to an NFS share secured with Kerberos, you need to modify the default . Currently, I override the source, because NixOS has no options to modify : The text is mostly copied from the default NixOS . The only changes are This solution is brittle, and requires manual intervention if the default ever changes. I'm not sure exactly what the NixOS options should look like, but there should be mechanisms to modify in NixOS. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
what about an option like so you can easily override/append values as you see fit?
That looks great. I'm a big fan of RFC 42 :) Just one question though. Can you remove an option, such as ?
Good question. can we bug you for some advice on how you can remove values from a option?
There's nothing builtin for that. The best that can be done is to just filter out values during string generation. Though in INI's case, is also a valid value in INI files, so that might not be a great idea. There is that adds a way to "unset" values, though I haven't looked into it much.
Thanks for mentioning without the ability to remove values would this not work?
I did a double-check on , and it looks like and are actually separate, but related. defaults to the value of . Also, the default value of is already , so removing it in my configuration had no effect. On that note, we may consider removing , as that is already the default. Regardless, your RFC 42 solution should work, even without the ability to remove values.
are you interested in opening a PR? Feel free to use the branch I posted.
I can open a pull request. Just one question: is there a reason the option and variables are called instead of ?
Typo
pull request is up. I fixed the typo and a syntax error.

Related discussion:
text: services.rpcbind.enable = true; <ins> services.nfs.idmapd.settings = { General = mkMerge [ { Pipefs-Directory = rpcMountpoint; } (mkIf (config.networking.domain != null) { Domain = config.networking.domain; }) ]; Mapping = { Nobody-User = "nobody"; Nobody-Group = "nogroup"; }; Translation = { Method = "nsswitch"; }; }; </ins> system.fsPackages = [ pkgs.nfs-utils ]; boot.initrd.kernelModules = mkIf inInitrd [ "nfs" ];
Code change:
The package takes a long time to build the individual glyphs using . See also Other distros simply use the release tarball (e.g. AUR ) which already has the resulting 13 MB file prebuilt. Should we do this as well, given that it's a font? CC maintainer:
I'm conflicted: on one hand NixOS is a source based distribution and building from source makes it possible to apply patches and whatnot, but on the other it's just a font without any executable stuff and 1.5 hours is a lot. I guess it depends on how valuable build time is?
It seems quite common for fonts in nixpkgs to use the upstream-release-provided font files; examples I picked randomly by clicking around in : Some fonts are generated by a call to , for example , but there doesn't seem to be a requirement for that. So I propose to make one of the former category.
EDIT: confused with
Ow. Well, that's a good enough reason to switch I guess :) I'll open a pr. edit: or I could Increase the timeout :)
cc
I have a sentiment for source builds but no rational arguments. The above arguments for building from source are reasonable. We also have package for a bitmap version of the font (using build system from Noto). That artefact is not available upstream so we need to build it ourselves, unless we want to depend on Fedora.
Yeah, I'm similar (at least for fonts, outside fonts there's many rational arguments :rofl: ). And I think considering how it times out... It's the best choice for now as there's not a ton of benefit to argue. Though doesn't seem to be incredibly difficult to do :frowning_face.
I think in practice this is still not going to address the root issue that the calling of inkscape is highly inefficient. Hehe, I bet nix being content addressed would make a lot of us much happier with not having to rebuild stuff pointlessly.
I'm sorry, I confused the two packages. It's apparently the other one that's timing out on Hydra:
Even with the 5x speedup I found in it'd still take 20 minutes to build it though. If somebody goes through the effort of fixing it upstream, we may want to consider switching back to fully-from-source. But there are 1000s of open-source tasks higher than this on my list :)
Can relate. (says ever opensource contributor ever while submitting 10x README PRs in a day :grin: )

Related discussion:
text: stdenv.mkDerivation rec { pname = "twemoji-color-font"; <del> version = "12.0.1"; </del> <ins> version = "13.0.1"; </ins> # We fetch the prebuilt font because building it takes 1.5 hours on hydra. # Relevant issue: https://github.com/NixOS/nixpkgs/issues/97871 src = fetchurl { url = "https://github.com/eosrei/twemoji-color-font/releases/download/v${version}/TwitterColorEmoji-SVGinOT-Linux-${version}.tar.gz"; <del> sha256 = "1kdy2k7b1k7sjp2l8g10lp2v000iwk8i3wcwgkhqfbwrrj7dg1kq"; </del> <ins> sha256 = "1mn2cb6a3v0q8i81s9a8bk49nbwxq91n6ki7827i7rhjkncb0mbn"; </ins> }; dontBuild = true;
Code change:
Project description DeepSpeech is an open source Speech-To-Text engine, using a model trained by machine learning techniques based on Baidu's Deep Speech research paper. Project DeepSpeech uses Google's TensorFlow to make the implementation easier. Metadata homepage URL: source URL: license: Mozilla Public License platforms: Unsure
I already tried this with a local clone of deepspeech: But I get this error for unknown reasons:
I guess pip is searching for a python package named sox.
That one doesn't seem to be in nixpkgs, is that right?
Doesn't look like it, you might want to package that as well looks like this would need packaged as well
There is .
I marked this as stale due to inactivity. &rarr;
:(
I binary package in , which works fine for my use case (linking to it from Rust). The binary itself works fine as well

Related discussion:
text: <ins> { stdenv, lib, fetchurl, autoPatchelfHook }: stdenv.mkDerivation rec { pname = "deepspeech"; version = "0.9.3"; src = fetchurl { url = "https://github.com/mozilla/DeepSpeech/releases/download/v${version}/native_client.amd64.cpu.linux.tar.xz"; sha256 = "1qy2gspprcxi76jk06ljp028xl0wkk1m3mqaxyf5qbhhfbvvpfap"; }; setSourceRoot = "sourceRoot=`pwd`"; nativeBuildInputs = [ autoPatchelfHook ]; buildInputs = [ stdenv.cc.cc.lib ]; installPhase = '' install -D deepspeech $out/bin/deepspeech install -D deepspeech.h $out/include/deepspeech.h install -D libdeepspeech.so $out/lib/libdeepspeech.so ''; meta = with lib; { homepage = https://github.com/mozilla/DeepSpeech; description = "Open source embedded (offline, on-device) speech-to-text engine, which can run in real time on broad range of devices"; license = licenses.mpl20; platforms = [ "x86_64-linux" ]; maintainers = with maintainers; [ rvolosatovs ]; }; } </ins>
Code change:
Project description DeepSpeech is an open source Speech-To-Text engine, using a model trained by machine learning techniques based on Baidu's Deep Speech research paper. Project DeepSpeech uses Google's TensorFlow to make the implementation easier. Metadata homepage URL: source URL: license: Mozilla Public License platforms: Unsure
I already tried this with a local clone of deepspeech: But I get this error for unknown reasons:
I guess pip is searching for a python package named sox.
That one doesn't seem to be in nixpkgs, is that right?
Doesn't look like it, you might want to package that as well looks like this would need packaged as well
There is .
I marked this as stale due to inactivity. &rarr;
:(
I binary package in , which works fine for my use case (linking to it from Rust). The binary itself works fine as well

Related discussion:
text: dbus-map = callPackage ../tools/misc/dbus-map { }; <ins> deepspeech = callPackage ../misc/deepspeech { }; </ins> dell-530cdn = callPackage ../misc/drivers/dell-530cdn {}; demjson = with python3Packages; toPythonApplication demjson;
Code change:
Describe the bug To Reproduce Expected behavior It should give me a shell Additional context I can fix it with which is based off 20.09-beta but I don't seem to be able to use HEAD (it breaks for another reason). Notify maintainers Metadata Maintainer information:

Related discussion:
text: ]; prePatch = lib.optionalString stdenv.isDarwin '' <del> substituteInPlace configure --replace "-install_name libR.dylib" "-install_name $out/lib/R/lib/libR.dylib" </del> <ins> substituteInPlace configure  --replace "-install_name libRblas.dylib" "-install_name $out/lib/R/lib/libRblas.dylib"  --replace "-install_name libRlapack.dylib" "-install_name $out/lib/R/lib/libRlapack.dylib"  --replace "-install_name libR.dylib" "-install_name $out/lib/R/lib/libR.dylib" </ins> ''; dontDisableStatic = static;