jiebi/CodeConvo huggingface dataset:
Code change:
miniupnpd = callPackage ../tools/networking/miniupnpd { }; <ins> miniupnpd-nftables = callPackage ../tools/networking/miniupnpd { firewall = "nftables"; }; </ins> miniball = callPackage ../development/libraries/miniball { }; minijail = callPackage ../tools/system/minijail { };

Related discussion:
text: We already have in , but only with iptables support. It would be nice to have the nftables version available as well.
Being worked on in , I'm trying to test myself but couldn't make it to work yet.
I think the PR is ready now, testing welcome!
Maybe add an option for will be better?
Code change:
linux_5_15_hardened = hardenedKernelFor kernels.linux_5_15 { }; linux_6_1_hardened = hardenedKernelFor kernels.linux_6_1 { }; linux_6_5_hardened = hardenedKernelFor kernels.linux_6_5 { }; <ins> linux_6_6_hardened = hardenedKernelFor kernels.linux_6_6 { }; </ins> } // lib.optionalAttrs config.allowAliases { linux_4_9 = throw "linux 4.9 was removed because it will reach its end of life within 22.11";

Related discussion:
text: Project description Hardened patchset got released for Linux 6.6. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, created the following merge request. Would appreciate a review.
will try to check that tomorrow's morning if my ibs allows me to, thanks
Code change:
<del> { stdenv, buildPythonPackage, fetchPypi, isPy3k , Mako, packaging, pysocks, pygments, ROPGadget , capstone, paramiko, pip, psutil , pyelftools, pyserial, dateutil , requests, tox, unicorn, intervaltree, fetchpatch }: </del> <ins> { stdenv , buildPythonPackage , fetchPypi , isPy3k , Mako , packaging , pysocks , pygments , ROPGadget , capstone , paramiko , pip , psutil , pyelftools , pyserial , dateutil , requests , tox , unicorn , intervaltree , fetchpatch }: </ins> buildPythonPackage rec { <del> version = "4.1.1"; </del> <ins> version = "4.2.1"; </ins> pname = "pwntools"; src = fetchPypi { inherit pname version; <del> sha256 = "694ce7a6cfca0ad40eae36c1d2663c44eb953f84785c63daa9752b4dfa7f39d8"; </del> <ins> sha256 = "1fh7sq9wrcfvn44qryln9cyg99pilvyq9bp80758lgdd6ss6hdqd"; </ins> }; <del> propagatedBuildInputs = [ Mako packaging pysocks pygments ROPGadget capstone paramiko pip psutil pyelftools pyserial dateutil requests tox unicorn intervaltree ]; </del> <ins> # Upstream has set an upper bound on unicorn because of https://github.com/Gallopsled/pwntools/issues/1538, # but since that is a niche use case and it requires extra work to get unicorn 1.0.2rc3 to work we relax # the bound here. Check if this is still necessary when updating! postPatch = '' sed -i 's/unicorn>=1.0.2rc1,<1.0.2rc4/unicorn>=1.0.2rc1/' setup.py ''; propagatedBuildInputs = [ Mako packaging pysocks pygments ROPGadget capstone paramiko pip psutil pyelftools pyserial dateutil requests tox unicorn intervaltree ]; </ins> doCheck = false; # no setuptools tests for the package

Related discussion:
text: Describe the bug building the package fails. To Reproduce Steps to reproduce the behavior: and wait Expected behavior Successfully building python37Packages.pwntools to be used. Notify maintainers Maintainer: Metadata Error
Will be fixed via
lol, I didn't see this issue, I started fixing it today because I recently noticed it was broken as well :D
Code change:
<del> { cmake , cudaPackages , fetchFromGitHub , lib , ninja , pkgs , python3Packages ? { } , pythonSupport ? false , stdenv , symlinkJoin , which }: let </del> <ins> { cmake, cudaPackages, fetchFromGitHub, lib, ninja, python3Packages ? {}, pythonSupport ? false, stdenv, symlinkJoin, which, }: let </ins> inherit (lib) lists strings; inherit (cudaPackages) backendStdenv cudaFlags; cuda-common-redist = with cudaPackages; [ <ins> cuda_cudart # cuda_runtime.h </ins> libcublas # cublas_v2.h libcusolver # cusolverDn.h libcusparse # cusparse.h

Related discussion:
text: Originally spotted by (thank you!). Steps to reproduce the behavior (assuming and are both ): The environment variable contains semicolons and must be quoted, otherwise bash will interpret the semicolons as command separators.
- Hey, I am not sure how to clean up the mess I just made on . Really embarrassed. I intended to rebase and hit merge instead, which pulled in 10k changes.
No worries, Happens to everyone at some point :) Personally, I'd just open a new PR.
Here it is: . Does the commit history look clean enough? I'll try to rebase it later, but I am concerned about retagging all of those folks.
I'd say don't worry about it -- as far as best practice goes, I'm actually not sure what's recommended for commits. do we recommend squashing before merge? I know I typically just do force pushes to avoid any commit history :l
I went ahead and squashed, and I'll post a nixpkgs-review when it's finished.
I don't think we have an official stance on this. Contributors use their best judgement for whatever keeps the commit history simplest and easiest to use
Code change:
]; buildInputs = [ <del> alsa-lib </del> fluidsynth glib iir1

Related discussion:
text: Steps to reproduce the behavior: dosbox-staging on darwin Complaining that alsa-lib not available on darwin I suggest referencing the derivation of in which use to opt-in dependencies P.S. wonder why the maintenance of this package is separated from and Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I don't have a Darwin machine. Nice. A full log would be nicer of course, but nice nonetheless. Wonder why they should be maintained by the same people.
Code change:
LIBRARY_PATH = if nativeComp then "${lib.getLib stdenv.cc.libc}/lib" else ""; <del> nativeBuildInputs = [ pkgconfig makeWrapper ] </del> <ins> nativeBuildInputs = [ pkgconfig makeWrapper nukeReferences ] </ins> ++ lib.optionals srcRepo [ autoreconfHook texinfo ] ++ lib.optional (withX && (withGTK3 || withXwidgets)) wrapGAppsHook;

Related discussion:
text: Describe the bug In NixOS 20.09, Emacs now has the output of gtk+ in its closure, which in turn causes it to pull in stuff like mesa-drivers (424 MiB): This caused the closure size of Emacs to increase from 339 MiB in NixOS 20.03 to 1324 MiB in 20.09. Metadata NixOS 20.09..
cc
This was reverted in
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Code change:
[ "-rtlib=compiler-rt" "-Wno-unused-command-line-argument" "-B${targetLlvmLibraries.compiler-rt}/lib" <del> # Combat "__cxxabi_config.h not found". Maybe this could be fixed by # copying these headers into libcxx? Note that building libcxx # outside of monorepo isn't supported anymore, might be related to # https://github.com/llvm/llvm-project/issues/55632 # ("16.0.3 libcxx, libcxxabi: circular build dependencies") # Looks like the machinery changed in https://reviews.llvm.org/D120727. "-I${lib.getDev targetLlvmLibraries.libcxx.cxxabi}/include/c++/v1" </del> ] ++ lib.optional (!stdenv.targetPlatform.isWasm) "--unwindlib=libunwind" ++ lib.optional

Related discussion:
text: Clang's wrapper does not set as an include path. Compiling files with since <cxxabi.hrequires is present in the aforementioned path I created the environment using this minimal mkShell expression Adding to
Proposed solution seems reasonable to me. See also started by
Please can you also include the nixpkgs commit hash in the repro (sorry if it's there and I missed it).
Oh thank you, that makes so much sense, I was also looking at how the monorepo handles things as well as their tests on finding the system include headers and what you said is probably the correct reason. Ah, it was the nixpkgs-unstable revision updated just then. Sorry I do not have that, but you can reproduce it with the current master as well.
Code change:
, profile ? "/etc/g810-led/profile" }: <del> stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "g810-led"; version = "0.4.3"; src = fetchFromGitHub { owner = "MatMoul"; <del> repo = pname; rev = "refs/tags/v${version}"; </del> <ins> repo = "g810-led"; rev = "refs/tags/v${finalAttrs.version}"; </ins> hash = "sha256-GKHtQ7DinqfhclDdPO94KtTLQhhonAoWS4VOvs6CMhY="; };

Related discussion:
text: Steps to reproduce the behavior: g810-led Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
Rosalie's Mupen GUI is a free and open-source mupen64plus front-end written in C++. It offers a simple-to-use user interface. ''; <del> license = licenses.gpl3; </del> <ins> license = if withAngrylionRdpPlus then licenses.unfree else licenses.gpl3Only; </ins> platforms = platforms.linux; mainProgram = "RMG"; maintainers = with maintainers; [ slam-bert ];

Related discussion:
text: There is a license violation in the package. The package contains the code for under the old MAME license which is non-commercial and incompatible with the GPL code in the rest of the program. I tried to notify upstream, but that didn't seem to go well...
Hello! It seems that upstream actually an option to disable in version of . , from my testing, gives me an error when I try to run it. You can find more info in this . So, i think merging the pull request linked to this issue is the best option right now.
Code change:
}; }; <ins> pid = buildPythonPackage rec { name = "pid-${version}"; version = "2.0.1"; src = pkgs.fetchurl { url = "https://pypi.python.org/packages/source/p/pid/${name}.tar.gz"; sha256 = "0cylj8p25nwkdfgy4pzai21wyzmrxdqlwwbzqag9gb5qcjfdwk05"; }; meta = { description = "Pidfile featuring stale detection and file-locking"; homepage = https://github.com/trbs/pid/; license = licenses.asl20; }; }; </ins> pydns = buildPythonPackage rec { name = "pydns-2.3.6"; disabled = isPy3k;

Related discussion:
text: To make sure that we are on the same page: Kernel: System: Nix version: Nixpkgs version: broke legacy packages (only tested with the -set). Multiple options to solve this: revert the commit (an update will eventually have to be done) make sure no-one depends on sqlalchemy legacy versions (this would be the best choice, but can require a big amount of work) re-introduce an outdated version only used by legacy version (I’ll prepare a PR shortly that follows this path) cc
To be complete, the build problem is a test failure: I also checked, we cannot downgrade sqlite only for few pythonPackages, the entire python (and package set) have to be changed. Any preferred way to go?
(We should check if we still need this version, have it removed locally for virtmanager, virtinst as it isn't used, but haven't had the time to push that)
Yes, this is the preferred way to go. I began that but did not finish it yet, and it impacts some important parts (it causes xen to fail) I would prefer not to break because of unsufficient testing from me. This is in progress but could require some time to complete.
FYI xen already fails on
FYI: I switched away from sqlalchemy7 in yesterday.
Apart from virtinst, acd_cli, beaker, coilmq, and geeknote are the only revdeps of sqlalchemy7, as far as I can tell.
I openned to do some cleanup on sqlalchemy7. There still is that explicitly require . The same work will have to be done for and .
This should have remained open.
Using an older version of sqlite requires overriding the derivations of the interpreters.
See
Code change:
csvkit = callPackage ../tools/text/csvkit { }; <ins> csvquote = callPackage ../tools/text/csvquote { }; </ins> csvtool = callPackage ../development/ocaml-modules/csv/csvtool.nix { }; csv2latex = callPackage ../tools/misc/csv2latex { };

Related discussion:
text: Project description Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
Code change:
webstorm = buildWebStorm rec { name = "webstorm-${version}"; <del> version = "2019.3.4"; /* updated by script */ </del> <ins> version = "2020.1"; /* updated by script */ </ins> description = "Professional IDE for Web and JavaScript development"; license = stdenv.lib.licenses.unfree; src = fetchurl { url = "https://download.jetbrains.com/webstorm/WebStorm-${version}.tar.gz"; <del> sha256 = "0q3595r4m22wf5r5zyncr1zv7yap5przbzjnyf75y51mqwl1g61i"; /* updated by script */ </del> <ins> sha256 = "1c68li5jxsjml0macdb0s04llwwq1hni5z8vq2zdfcn5zm3xwpif"; /* updated by script */ </ins> }; wmClass = "jetbrains-webstorm"; update-channel = "WebStorm RELEASE";

Related discussion:
text: Please update Goland to a current version. The Current Version is now 2020.1 Thx and Greetz
Code change:
inherit version; sha256 = "1vn1db2akw98ybnpns92qi11v94hydwp130s8753k6ikby95883j"; }; <ins> patches = oldAttrs.patches or [] ++ [ # Don't raise import error on non-linux os. Remove after upgrading to distro≥1.2.0 (fetchpatch { url = "https://github.com/nir0s/distro/commit/25aa3f8c5934346dc838387fc081ce81baddeb95.patch"; sha256 = "0m09ldf75gacazh2kr04cifgsqfxg670vk4ypl62zv7fp3nyd5dc"; }) ]; </ins> }); node-semver = super.node-semver.overridePythonAttrs (oldAttrs: rec { version = "0.6.1";

Related discussion:
text: Description Attempting to install conan with nix-env on Mac OS X errors out with the following message: To Reproduce Steps to reproduce the behavior: Expected behavior As Mac OS X is a supported platform for conan, it's expected that it would install. Additional context This appears to be due to conan's dependency on the python3-distro package, which only compiles on Linux architectures. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(tclemons): channels(root): nixpkgs:
Code change:
package = mkPackageOption pkgs "navidrome" { }; settings = mkOption { <del> type = settingsFormat.type; default = { Address = "127.0.0.1"; Port = 4533; </del> <ins> type = submodule { freeformType = settingsFormat.type; options = { Address = mkOption { default = "127.0.0.1"; description = "Address to run Navidrome on."; type = str; }; Port = mkOption { default = 4533; description = "Port to run Navidrome on."; type = port; }; }; </ins> }; example = { MusicFolder = "/mnt/music";

Related discussion:
text: Evaluation failure when setting and . Moreover setting any will "remove" the default values for and your system with these options: the failure: System builds, firewall is opened for the default 4533 port. This bug happens because the rather than for each individual setting. <!-- 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 Issue here is the option being null, you can use these options together if is supplied. if you encountered a different eval failure to this please attach it. Yes this is because those options values are supplied as apart of one default of as a whole, I am not aware of a nice way to give them a default independent of the rest of the settings being set or not. would giving this port value a catch for being null be an alright solution? e.g.. if is not set, then use the upstream default ( of 4533 I believe ) I don't really want to separate out these values from the . option so this wont address the removal of default values when setting them yourself to something different, I think this is expected enough* behavior. I think fixing this eval failure condition with simply supplying the default port where isn't supplied is reasonable enough, as anyone who wasnt going to set that in the first place is unlikely to care if its the same value in function either way. In fact i may just remove the default entirely and simply handle the case of no supplied value by assuming the default port (of 4533 ) in the openFirewall rule. I'll PR these changes once I get the time
Code change:
buildInputs = with self; [ nose sphinx numpydoc ]; <del> # Failing test on Python 3.x postPatch = '''' + optionalString isPy3k '' </del> <ins> # Failing test on Python 3.x and Darwin postPatch = '''' + optionalString (isPy3k || stdenv.isDarwin) '' </ins> sed -i -e '70,84d' joblib/test/test_format_stack.py # test_nested_parallel_warnings: ValueError: Non-zero return code: -9. # Not sure why but it's nix-specific. Try removing for new joblib releases.

Related discussion:
text: I'm trying to install joblib for python 2.7 on a Mac, but the threading and multiprocessing tests fail. System: Darwin Kernel Version 13.4.0 Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: "16.09pre83147."
As I mentioned in you're not supposed to install Python libraries like that. Even so, the error is still a bug. Unfortunately I'm not using OSX myself so I can't be much of help I'm afraid. I do know there are issues with multiprocessing on OSX with Apple vecLib / Accelerate.
Ok, now I know you have to use nix-shell to load python libraries. Just adding here that gives the same error.
Code change:
source = "${nvidia_x11.bin}/share/nvidia/nvidia-application-profiles-rc"; }; <ins> # 'nvidia_x11' installs it's files to /run/opengl-driver/... environment.etc."egl/egl_external_platform.d".source = "/run/opengl-driver/share/egl/egl_external_platform.d/"; </ins> hardware.opengl.package = mkIf (!offloadCfg.enable) nvidia_x11.out; hardware.opengl.package32 = mkIf (!offloadCfg.enable) nvidia_x11.lib32; hardware.opengl.extraPackages = optional offloadCfg.enable nvidia_x11.out;

Related discussion:
text: Yes. We have a package which is what I tried, but since it’s a thin wrapper around it’s possible that it’s still not built with the right options. Also I’ve noticed these messages from : does not show the extension, and GLX applications fail to start. Originally posted by in I probably merged , too early. I'm not totally sure this is working properly.
This is pretty much a help wanted because I lack the depth of knowledge and hardware to help anymore with Nvidia things. My goal with finishing was that it could be possible and improved upon. i.e packages are built with the capability etc.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
The last few evenings, I have tinkered around a bit. I was not successful so far. Here are my findings: I have set the following options: This page says that there is no acceleration support for xwayland and nvidia yet but glxgears fails to start, so I think this is another issue There are multiple versions of : One from the egl-wayland package, the other from nvidia-x11 package. As the one in is loaded, I tried to replace it with the one from egl-wayland. Though, the result is the same with both. When starting an application, which would use acceleration, I can observe this line in the kernel log: Using , I can see that is accessed, though one of the calls fails: one more thing: looking at , gnome-shell is listed. Maybe it has working acceleration? Edit: Got a bit further: Found a reference to an additional directory, which is used to look up libraries: Creating a file in there: with the file in /run/opengl-driver/lib/libnvidia-egl- being replaced by the one from egl-wayland package. Now the error in xwayland is just a warning: I can run a wayland native terminal, but still fails If you have any suggestions, what to try next, I would be glad to give it a try.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant.
Code change:
source = "${nvidia_x11.bin}/share/nvidia/nvidia-application-profiles-rc"; }; <ins> # 'nvidia_x11' installs it's files to /run/opengl-driver/... environment.etc."egl/egl_external_platform.d".source = "/run/opengl-driver/share/egl/egl_external_platform.d/"; </ins> hardware.opengl.package = mkIf (!offloadCfg.enable) nvidia_x11.out; hardware.opengl.package32 = mkIf (!offloadCfg.enable) nvidia_x11.lib32; hardware.opengl.extraPackages = optional offloadCfg.enable nvidia_x11.out;

Related discussion:
text: This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
I'm trying to get this working as well. However I can't even get the session chooser in GDM in 20.09. Is it only working in unstable? Any tips? Here's my config
With this overlay and the 470.42.01 driver, nvidia is usable with xwayland. :tada: , unigene-valley and so far every game I started on Steam. Only issues I have so far are that chrome does not start properly Workaround is to start it with some options: and in CSGO there is noticeable input delay.
I've updated to the latest nixos-unstable () which includes updated & , but I'm still facing issues. While it's generally working I have problems with some apps. : : : Additionally in my system logs I can see: & are both working. My relevant config: I also tried using an overlay to apply the new meson flags from overlay: Is there anything else I need to set up?
also fails with
I have a very similar setup as and am experiencing precisely the same errors. I'm not sure whether it's an issue with gnome, my particular config, or what. Things work fine when running in an X session.
:thinking: I don't see anything missing with your config . I have updated my config to and removed the overlay. and are producing the same errors, and chrome won't function properly unless started with and are working for me, as well as and and . Note: Seam is installed via but this should only be relevant for running games inside steam, not steam itself.