jiebi/CodeConvo huggingface dataset:
Change:
Project description Fastapi-email package is needed for fastapi projects. Metadata homepage URL: source license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...

Discussion:
<ins> { lib , aiosmtpd , buildPythonPackage , fetchFromGitHub , fetchpatch , hypothesis , poetry-core , pytest-asyncio , pytestCheckHook , pythonOlder }: buildPythonPackage rec { pname = "aiosmtplib"; version = "1.1.6"; format = "pyproject"; disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "cole"; repo = pname; rev = "v${version}"; hash = "sha256-bo+u3I+ZX95UYkEam2TB6d6rvbYKa5Qu/9oNX5le478="; }; nativeBuildInputs = [ poetry-core ]; checkInputs = [ aiosmtpd hypothesis pytest-asyncio pytestCheckHook ]; patches = [ # Switch to poetry-core, https://github.com/cole/aiosmtplib/pull/183 (fetchpatch { name = "switch-to-poetry-core.patch"; url = "https://github.com/cole/aiosmtplib/commit/3aba1c132d9454e05d4281f4c8aa618b4e1b783d.patch"; hash = "sha256-KlA46gD6swfJ/3OLO3xWZWa66Gx1/izmUMQ60PQy0po="; }) ]; pythonImportsCheck = [ "aiosmtplib" ]; meta = with lib; { description = "Module which provides a SMTP client"; homepage = "https://github.com/cole/aiosmtplib"; license = with licenses; [ mit ]; maintainers = with maintainers; [ fab ]; }; } </ins>

<ins> { lib , aioredis , aiosmtplib , blinker , buildPythonPackage , email_validator , fakeredis , fastapi , fetchFromGitHub , httpx , jinja2 , poetry-core , pydantic , pytest-asyncio , pytestCheckHook , python-multipart , pythonOlder }: buildPythonPackage rec { pname = "fastapi-mail"; version = "1.0.8"; format = "pyproject"; disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "sabuhish"; repo = pname; rev = version; hash = "sha256-PkA7qkdDUd7mrtvb6IbCzFRq6X0M3iKY+FKuNConJ5A="; }; nativeBuildInputs = [ poetry-core ]; propagatedBuildInputs = [ aioredis aiosmtplib blinker email_validator fakeredis fastapi httpx jinja2 pydantic python-multipart ]; checkInputs = [ pytest-asyncio pytestCheckHook ]; disabledTests = [ # Tests require access to /etc/resolv.conf "test_default_checker" "test_redis_checker" ]; pythonImportsCheck = [ "fastapi_mail" ]; meta = with lib; { description = "Module for sending emails and attachments"; homepage = "https://github.com/sabuhish/fastapi-mail"; license = with licenses; [ mit ]; maintainers = with maintainers; [ fab ]; }; } </ins>

aiosmtpd = callPackage ../development/python-modules/aiosmtpd { }; <ins> aiosmtplib = callPackage ../development/python-modules/aiosmtplib { }; </ins> aiosqlite = callPackage ../development/python-modules/aiosqlite { }; aiosteamist = callPackage ../development/python-modules/aiosteamist { };

fastapi = callPackage ../development/python-modules/fastapi { }; <ins> fastapi-mail = callPackage ../development/python-modules/fastapi-mail { }; </ins> fastavro = callPackage ../development/python-modules/fastavro { }; fastbencode = callPackage ../development/python-modules/fastbencode { };
Change:
On NixOS 22.05, getting financial quotes in gnucash no longer works because the helper scripts are now binary wrappers, but gnucash calls so this fails. Commit suggests that should avoid this, but for some reason the scripts still get wrapped with binaries. NixOS 22.05..
I can reproduce this on my machine from nixpkgs/master, so it's not a 22.05 problem. Interestingly, when I backport GnuCash's derivation from nixpkgs/master back to a known-good commit (), things appear ok. I'll continue digging.
... I see you yourself as a maintainer. Any interest in taking a stab at this? Per I think we're being broken by a change somewhere related to .
... I see you yourself as a maintainer. Any interest in taking a stab at this? still getting my head together after a bad bout of covid, not sure I'll be able to work on anything serious any time soon
I worked around this on my nixos config by adding a patch () to execute the helpers directly without calling out to perl. It seems to work for me. Will this break anything? If desired, I can submit a PR with this patch. Also, the perl helpers seem to be getting wrapped explicitly () is this not the reason the perl helpers are getting wrapped with binary executables?

Discussion:
<ins> diff --git a/gnucash/price-quotes.scm b/gnucash/price-quotes.scm index 8e3ff255f..a6b805fa5 100644 --- a/gnucash/price-quotes.scm +++ b/gnucash/price-quotes.scm @@ -44,7 +44,7 @@ (define (start-program) (set! program (gnc-spawn-process-async -         (list "perl" "-w" gnc:*finance-quote-check*) #t))) +         (list gnc:*finance-quote-check*) #t))) (define (get-sources) (when program @@ -119,7 +119,7 @@ (define (start-quoter) (set! quoter -        (gnc-spawn-process-async (list "perl" "-w" gnc:*finance-quote-helper*) #t))) +        (gnc-spawn-process-async (list gnc:*finance-quote-helper*) #t))) (define (get-quotes) (when quoter </ins>

./0002-disable-gnc-fq-update.patch # this patch prevents the building of gnucash-valgrind ./0003-remove-valgrind.patch <ins> # this patch makes gnucash exec the Finance::Quote helpers directly ./0004-exec-fq-helpers.patch </ins> ]; # this needs to be an environment variable and not a cmake flag to suppress
Change:
The version is called . That seems to be older than which is the first version with a fix for Can't we use ? cc
Would be nice if we could push issues like this upstream and have them fix it. Our tooling is nice and all we would have to do is backport the bump that our bot automatically creates. Any idea if upstream has addressed this? I can probably look later tonight when I'm at a computer.
That's the problem with such tooling. You only get security updates after upstream notices them, if ever. Thus at least one more indirection.
I guess I'm just spoiled by our (nixpkgs) tooling because all this comment made me think is that upstream could really benefit from using this type of tooling too
Is there a way to override specific plugins? There wouldn't be much to maintain if you just use .
Straight libs generally won't work as packaging does a little wrapping. Certainly we could replicate this... but that would come at a bit of a maintenance cost too.
We'll have to do either that or update upstream asap.
I'm out for the day and my android phone can't read files so I can't check if upstream has fixed this or not. Manually running the would let us know... if you have the capacity.
How do I run it? EDIT:
Doesn't change anything.
Where are these add-ons maintained upstream?
Looks like . It seems like developers pull upstream code right into their tree and then make a few minor additions for packaging as seen .

Discussion:
<del> { lib, buildKodiAddon, fetchzip, addonUpdateScript }: </del> <ins> { lib, buildKodiAddon, fetchFromGitHub, addonUpdateScript }: </ins> buildKodiAddon rec { pname = "urllib3"; namespace = "script.module.urllib3"; <del> version = "1.26.4+matrix.1"; </del> <ins> version = "1.26.8+matrix.1"; </ins> <del> src = fetchzip { url = "https://mirrors.kodi.tv/addons/matrix/${namespace}/${namespace}-${version}.zip"; sha256 = "1d2k6gbsnhdadcl1xc7igz4m71z2fcnpln5ppfjv455cmkk110vf"; </del> <ins> # temporarily fetching from a PR because of CVE-2021-33503 # see https://github.com/xbmc/repo-scripts/pull/2193 for details src = fetchFromGitHub { owner = "xbmc"; repo = "repo-scripts"; rev = "f0bfacab4732e33c5669bedd1a86319fa9e38338"; sha256 = "sha256-UEMLrIvuuPARGHMsz6dOZrOuHIYVSpi0gBy2lK1Y2sk="; </ins> }; <ins> sourceRoot = "source/script.module.urllib3"; </ins> passthru = { pythonPath = "lib"; <del> updateScript = addonUpdateScript { attrPath = "kodi.packages.urllib3"; }; </del> }; meta = with lib; {
Change:
snowsql-connector-python needs setuptools python package dependency Steps to reproduce the behavior: -shell -p python3Packages.snowflake-connector-python --run "python -m snowflake.connector" python interpreter imports package without any errors snowflake-connector-python shows as a dependency <!-- 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.

Discussion:
, pythonOlder , pytz , requests <ins> , setuptools </ins> }: buildPythonPackage rec {

pyopenssl pytz requests <ins> setuptools </ins> ]; postPatch = ''
Change:
Likely caused by build failure of . : I am really sorry I didn't test this in and seems like this is one of channel blockers left. Firefox maintainer also cc
FWIW I think you can just remove the and it'll typecheck fine.
Agreed, the yield does not yield anything and is only used to interrupt the function calls.

Discussion:
@contextmanager <del> def audio_recording(machine: Machine) -> None: </del> <ins> def record_audio(machine: Machine): </ins> """ Perform actions while recording the machine audio output.

machine.systemctl("stop audio-recorder") <del> def wait_for_sound(machine: Machine) -> None: </del> <ins> def wait_for_sound(machine: Machine): </ins> """ Wait until any sound has been emitted. """

machine.sleep(40) with subtest("Check whether Firefox can play sound"): <del> with audio_recording(machine): </del> <ins> with record_audio(machine): </ins> machine.succeed( "firefox file://${pkgs.sound-theme-freedesktop}/share/sounds/freedesktop/stereo/phone-incoming-call.oga >&2 &" )
Change:
<!-- 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 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: reaper <!-- The current version can be found easily with the same process as 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: 6.47 desired version: 6.59 <!-- 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.

Discussion:
stdenv.mkDerivation rec { pname = "reaper"; <del> version = "6.47"; </del> <ins> version = "6.61"; </ins> src = fetchurl { url = "https://www.reaper.fm/files/${lib.versions.major version}.x/reaper${builtins.replaceStrings ["."] [""] version}_linux_${stdenv.hostPlatform.qemuArch}.tar.xz"; hash = { <del> x86_64-linux = "sha256-31HmIx/ohbrzu5uj8KOOZiHNCmXwng9h+fIGaJfYyqA="; aarch64-linux = "sha256-CMmcBpaZ6BEZJ1144aQhOJ/o2NrGD7/8aq+ObLVMXYE="; </del> <ins> x86_64-linux = "sha256-Lp2EVky1+ruc86LdMmvhZIisoYl0OxdkVnN3h/u09IQ="; aarch64-linux = "sha256-sPLCMA//xAdWXjY7++R6eLWS56Zi0u+9ju7JlICGvVc="; </ins> }.${stdenv.hostPlatform.system}; };
Change:
cannot access my devices. Here's an example log: I'm almost certain, that the issue is an empty , as the service runs fine without it, but I'd like a second opinion before sending a PR. Steps to reproduce the behavior: and set [Optional] Override DeviceAllow list: The service will work now. should run without errors. Adding has the same issue, overriding fixes it aswell. Possible offending code: Not sure why the override is not working, though: <!-- 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.
What does your resulting systemd unit look like? Also default priority is 1000, so overriding it with priority 100 should work.
I agree, it should work, here is the before and after (created with systemctl cat) Stock nixpkgs: With my changes: Evaluating results in for me.
Yup, that looks like the problem. That would mean they share the same priority, so we should likely try going down to 50 with the override.
I'm not sure if [the wiki][1] is up to date, but 100 seems to be the default, 1000 is the default for defaults. It might be more future-proof to change to , but it's probably more disruptive for the other modules. Overriding with 50 seems to be the smarter option. [1]: I could assemble a PR, seems like a very small fix
Feel free!
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Discussion:
"CAP_SYS_ADMIN" ]; DevicePolicy = "closed"; <del> DeviceAllow = lib.mkOverride 100 ( </del> <ins> DeviceAllow = lib.mkOverride 50 ( </ins> if cfg.devices != [] then cfg.devices else [
Change:
Project description fastfetch is a [neofetch] like tool for fetching system information and displaying them in a pretty way. It is written in c to achieve much better performance, Metadata source URL: license: mit, bsd, gpl2+ ,: mit platforms: unix, linux, darwin, : linux
Please review and check if it works.

Discussion:
fingerprint = "D0CF 440A A703 E0F9 73CB  A078 82BB 70D5 41AE 2DB4"; }]; }; <ins> gerg-l = { email = "gregleyda@proton.me"; github = "Gerg-L"; githubId = 88247690; name = "Greg Leyda"; }; </ins> geri1701 = { email = "geri@sdf.org"; github = "geri1701";

<ins> { lib , stdenv , fetchFromGitHub , chafa , cmake , dbus , dconf , glib , imagemagick_light , libglvnd , libpulseaudio , libxcb , libXrandr , makeBinaryWrapper , networkmanager , nix-update-script , ocl-icd , opencl-headers , pciutils , pkg-config , rpm , sqlite , testers , vulkan-loader , wayland , xfce , zlib , AppKit , Cocoa , CoreDisplay , CoreVideo , CoreWLAN , DisplayServices , Foundation , IOBluetooth , MediaRemote , OpenCL , moltenvk }: stdenv.mkDerivation (finalAttrs: { pname = "fastfetch"; version = "1.12.2"; src = fetchFromGitHub { owner = "fastfetch-cli"; repo = "fastfetch"; rev = finalAttrs.version; hash = "sha256-l9fIm7+dBsOqGoFUYtpYESAjDy3496rDTUDQjbNU4U0="; }; nativeBuildInputs = [ cmake makeBinaryWrapper pkg-config ]; buildInputs = [ chafa imagemagick_light sqlite ] ++ lib.optionals stdenv.isLinux [ dbus dconf glib libglvnd libpulseaudio libxcb libXrandr networkmanager ocl-icd opencl-headers pciutils rpm vulkan-loader wayland xfce.xfconf zlib ] ++ lib.optionals stdenv.isDarwin [ AppKit Cocoa CoreDisplay CoreVideo CoreWLAN DisplayServices Foundation IOBluetooth MediaRemote OpenCL moltenvk ]; cmakeFlags = [ "-DCMAKE_INSTALL_SYSCONFDIR=${placeholder "out"}/etc" ]; postInstall = '' wrapProgram $out/bin/fastfetch  --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath finalAttrs.buildInputs}" wrapProgram $out/bin/flashfetch  --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath finalAttrs.buildInputs}" ''; passthru = { updateScript = nix-update-script { }; tests.version = testers.testVersion { package = finalAttrs.finalPackage; command = "fastfetch -v | cut -d '(' -f 1"; version = "fastfetch ${finalAttrs.version}"; }; }; meta = { description = "Like neofetch, but much faster because written in C"; inherit (finalAttrs.src.meta) homepage; license = lib.licenses.mit; maintainers = with lib.maintainers; [ gerg-l khaneliman ]; platforms = lib.platforms.all; mainProgram = "fastfetch"; }; }) </ins>

etlegacy = callPackage ../games/etlegacy { lua = lua5_4; }; <ins> fastfetch = darwin.apple_sdk_11_0.callPackage ../tools/misc/fastfetch { inherit (darwin.apple_sdk_11_0.frameworks) AppKit Cocoa CoreDisplay CoreVideo CoreWLAN DisplayServices Foundation IOBluetooth MediaRemote OpenCL; inherit (darwin) moltenvk; }; </ins> fscan = callPackage ../tools/security/fscan { }; copier = callPackage ../tools/misc/copier { };
Change:
Steps to reproduce the behavior: vendor fish completions provided by Nixpkgs by adding to (nixos-22.05) (see also ) Additional fish-configurations: *
One of your packages isn't a derivation? Weird but I suppose there's no rule against it. Should be fairly easy to fix, give me a little.
Thanks :) It only happened after I upgraded to the nixos-22.05 channel.
Could you test ?
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Discussion:
preferLocalBuild = true; allowSubstitutes = false; }; <del> generateCompletions = package: pkgs.runCommand "${package.name}_fish-completions" ( { inherit package; preferLocalBuild = true; allowSubstitutes = false; } // optionalAttrs (package ? meta.priority) { meta.priority = package.meta.priority; } ) </del> <ins> generateCompletions = package: pkgs.runCommandLocal ( with lib.strings; let storeLength = stringLength storeDir + 34; # Nix' StorePath::HashLen + 2 for the separating slash and dash pathName = substring storeLength (stringLength package - storeLength) package; in (package.name or pathName) + "_fish-completions") ( { inherit package; } // optionalAttrs (package ? meta.priority) { meta.priority = package.meta.priority; }) </ins> '' mkdir -p $out if [ -d $package/share/man ]; then
Change:
When services.dovecot2.mailUser and services.dovecot2.mailGroup is not set, nixos-rebuild terminates with the type error "cannot coerce null to a string", when services.dovecot2.sieveScripts is set. The reason for it is in line 257 of the dovecot module: mailUser and mailGroup default to null. One way to solve this could be to default to the dovecot user and group when no virtual mail user was set. Set services.dovecot2.mailUser or services.dovecot2.mailGroup to the default and then set services.dovecot2.sieveScripts to anything other than {}. System: 16.09pre / Master Nix version: 1.11.2 Nixpkgs version: 16.09pre
I was looking in to fixing this. It looks like mailUser / mailGroup could default to and I don't know why they are separate. Anyone know if that works?
I don't know if that works tbh. If not, it would suffice to just add another assertion that requires mailUser and mailGroup to be defined when sieveScripts is set.

Discussion:
{ assertion = cfg.showPAMFailure -> cfg.enablePAM; message = "dovecot is configured with showPAMFailure while enablePAM is disabled"; } <ins> { assertion = (cfg.sieveScripts != {}) -> ((cfg.mailUser != null) && (cfg.mailGroup != null)); message = "dovecot requires mailUser and mailGroup to be set when sieveScripts is set"; } </ins> ]; };
Change:
Steps to reproduce the behavior: 's my config: I got the error while upgrading to nixpkgs A successful system rebuild
is not allowed in path literals. try quoting the paths
Well, I can't, it's autogenerated in replace- module
oh, i see :(

Discussion:
read ref_path if [ "$ref_path" != "$path" ] then <del> echo "    (builtins.storePath $ref_path)" </del> <ins> echo "    (builtins.storePath (/. + "$ref_path"))" </ins> fi count=$(($count - 1)) done
Change:
The following security vulnerability in libdwarf has been published. We have two vulnerable versions: 0.4.0 The patch we need to apply is: Maintainer: Please reference the CVE id with in the commit message.
PTAL.
We cannot easily apply the patch provided by the upstream to the default version because the code base directory layout changes
Could you take a look at , please?
, I wonder how you noticed this vulnerability. Is there certain vulnerability workflow that ensures that every CVE in any package would be addressed or at least marked as .
I tried to find out how I first heard of this vulnerability, but I can't find the source anymore. It was neither an email nor on IRC. We have a coordination channel for security issue triage on Matrix. It's .
Thank you for the information.

Discussion:
{ callPackage, zlib }: callPackage ./common.nix rec { <del> version = "0.4.0"; </del> <ins> version = "0.4.1"; </ins> url = "https://www.prevanders.net/libdwarf-${version}.tar.xz"; <del> sha512 = "30e5c6c1fc95aa28a014007a45199160e1d9ba870b196d6f98e6dd21a349e9bb31bba1bd6817f8ef9a89303bed0562182a7d46fcbb36aedded76c2f1e0052e1e"; </del> <ins> sha512 = "793fe487de80fe6878f022b90f49ec334a0d7db071ff22a11902db5e3457cc7f3f853945a9ac74de2c40f7f388277f21c5b2e62745bca92d2bb55c51e9577693"; </ins> buildInputs = [ zlib ]; <ins> knownVulnerabilities = []; </ins> }

<del> { lib, stdenv, fetchurl, buildInputs, sha512, version, libelf, url }: </del> <ins> { lib, stdenv, fetchurl, buildInputs, sha512, version, libelf, url, knownVulnerabilities }: </ins> stdenv.mkDerivation rec { pname = "libdwarf";

platforms = lib.platforms.unix; license = lib.licenses.lgpl21Plus; maintainers = [ lib.maintainers.atry ]; <ins> inherit knownVulnerabilities; </ins> }; }

url = "https://www.prevanders.net/libdwarf-${version}.tar.gz"; sha512 = "e0f9c88554053ee6c1b1333960891189e7820c4a4ddc302b7e63754a4cdcfc2acb1b4b6083a722d1204a75e994fff3401ecc251b8c3b24090f8cb4046d90f870"; buildInputs = [ zlib libelf ]; <ins> knownVulnerabilities = [ "CVE-2022-32200" ]; </ins> }
Change:
Steps to reproduce the behavior: to latest 22.05 -shell -p dmd Build should work, or be marked as broken.
Here is the relevant failing test and its error: Looks like the gdb output has changed slightly so this grep doesn't work anymore.
Just in case this wasn't obvious, bisected failure to the gdb bump . . I also tested the current bump PR and a local bump to the latest but the error persists. Only thing that fixes it is reverting . We should either remove or fix the affected test on our end and inform upstream about this.

Discussion:
rm dmd/test/runnable/gdb15729.sh rm dmd/test/runnable/gdb4149.d rm dmd/test/runnable/gdb4181.d <ins> # Grep'd string changed with gdb 12 substituteInPlace druntime/test/exceptions/Makefile  --replace 'in D main (' 'in _Dmain (' </ins> '' + lib.optionalString stdenv.isLinux ''
Change:
In I Backblaze B2's Terraform provider. When running the plugin before I ran into I have now been able to troubleshoot this and realise the plugin is currently broken. Running Terraform with , I find the culprit: It seems that this is some Go specific error message, related to its packaging imports. As I'm not familiar with Go, I don't know where to troubleshoot this or how to fix this in Nix. I am reporting this in the hopes that similar issues have been resolved before, or that someone familiar with Go can pinpoint the issue. Steps to reproduce the behavior: a minimal nix environment with Terraform and the b2 provider: for any plan using the b2 Terraform provider. I expect the Terraform provider to work and to provision my resources. <!-- 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.
Likely to be this: The overrides that we will need to use to build this in with our current provider model will be rather non-trivial and make it the most complicated provider that we package. TBH I'd rather remove the from and point people to as an alternative. cc
agreed, let's remove it

Discussion:
removed = name: date: throw "the ${name} terraform provider removed from nixpkgs on ${date}"; in lib.optionalAttrs config.allowAliases { <ins> b2 = removed "b2" "2022/06"; </ins> opc = archived "opc" "2022/05"; oraclepaas = archived "oraclepaas" "2022/05"; template = archived "template" "2022/05";

"vendorSha256": null, "version": "0.10.0" }, <del> "b2": { "owner": "Backblaze", "provider-source-address": "registry.terraform.io/Backblaze/b2", "repo": "terraform-provider-b2", "rev": "v0.8.0", "sha256": "sha256-2yyAKrDO7X5yujfrHhYuvXbuKk3yY1sCXRZ8U/9OnrM=", "vendorSha256": "sha256-f5bvk0p7AU1i/xeapxyVRXIUARju6mNQokejaDnT/GI=", "version": "0.8.0" }, </del> "baiducloud": { "deleteVendor": true, "owner": "baidubce",