jiebi/CodeConvo huggingface dataset:
Change:
let # Keep these separate so the update script can regex them <del> rpcs3GitVersion = "15726-ebf48800e"; rpcs3Version = "0.0.29-15726-ebf48800e"; rpcs3Revision = "ebf48800e6bf2569fa0a59974ab2daaeb3a92f23"; rpcs3Hash = "sha256-HJQ+DCZy8lwMCfq0N9StKD8bP1hCBxGMAucbQ9esy/I="; </del> <ins> rpcs3GitVersion = "16271-4ecf8ecd0"; rpcs3Version = "0.0.31-16271-4ecf8ecd0"; rpcs3Revision = "4ecf8ecd06c15f0557e1d9243f31e4c2d7baebe2"; rpcs3Hash = "sha256-y7XLYo1qYYiNE4TXVxfUTCmyGkthpj3IU1gdKTgb8KY="; </ins> inherit (qt6Packages) qtbase qtmultimedia wrapQtAppsHook qtwayland; in

Discussion:
Steps to reproduce the behavior: rpcs3 <!-- 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]:
Wrong Zane - see
Change:
<xi:include href="option-def.xml" /> <xi:include href="assertions.xml" /> <xi:include href="meta-attributes.xml" /> <ins> <xi:include href="importing-modules.xml" /> </ins> <xi:include href="replace-modules.xml" /> </chapter>

Discussion:
references , and sticks the import of the specified file into a list. This means you can only have one extra module inside of . Is this intentional? The name of makes me think it just got messed up at some point. I was expecting to need to supply a path to a file like with a list of modules. This would work if the import wasn't being wrapped in a list, like it originally was:
with a being:
Are you saying that should work? I'm also unable to do more than import a single module, but maybe I'm missing something.
I just look at the code, and the earliest version using the environment variable probably never worked because this would imply getting a list out of an environment variable, which returns a string. The example I gave was just a way to show that if you have a the ability to load a single module, then you can load any number of modules that you want.
Ah, I misunderstood how works. Thanks!
Change:
<ins> { config, lib, pkgs, ... }: let cfg = config.programs.qdmr; in { meta.maintainers = [ lib.maintainers.janik ]; options = { programs.qdmr = { enable = lib.mkEnableOption (lib.mdDoc "QDMR - a GUI application and command line tool for programming DMR radios"); package = lib.mkPackageOptionMD pkgs "qdmr" { }; }; }; config = lib.mkIf cfg.enable { environment.systemPackages = [ cfg.package ]; services.udev.packages = [ cfg.package ]; users.groups.wireshark = {}; }; } </ins>

Discussion:
Project description a program for managing several popular DMR hand held radios Metadata homepage URL: source URL: license: gpl3 platforms: linux, macos
Change:
source 'https://rubygems.org' gem 'jekyll' <ins> gem 'jekyll-feed' </ins> gem 'jekyll-paginate' gem 'rdiscount' gem 'RedCloth' <ins> gem 'minima' </ins>

Discussion:
One uses to create a new tree of files for generating a web site. So the intent is to edit those files. But the files produced are read-only, so user must do a before each new file can be edited. I haven't looked at the source yet, but I imagine this is because jekyll copies the site template out of an installed gem or something, and all the files there are 444 (read-only) because it's in the Nix store. System: NixOS 16.09.1600. (Flounder) Nix version: nix-env (Nix) 1.11.6 Nixpkgs version: 16.09.1698.
Have you tried reporting this upstream?
I have not. Will consider that – it seems that a fix would be a one-liner after to do or so. But I'm not able to test easily if that's all that would be needed – the nixpkgs expression is quite behind, carrying jekyll 3.0.1 when current release is 3.4.1. I tried updating too, but ran into bundler problems, and I don't know much about ruby.
You seem to have idea how to fix it. Should really bring this up with upstream. I don't know much about ruby, but nixpkgs manual has a step by step guide: Turned out to be very easy:
So I ran into bundler problems)
Ok, I've pushed a workaround for that
Change:
<del> { lib, stdenv, fetchurl, meson, pkg-config, ninja, wayland </del> <ins> { lib, stdenv, fetchFromSourcehut, meson, pkg-config, ninja, wayland </ins> , wayland-protocols }:

Discussion:
Describe the bug Sources from archives from fail to download with hash mismatches. To Reproduce Expected behavior The hash should match and the source should download. Additional context It sounds like , causing changes to all generated archives (to come in-line with GNU gzip). I've determined some packages which this affects (listed in "Maintainer information") by . I'm happy to have a go making a PR for all of these packages with the following process: archive from cache (by with subsituters) archive from both and confirm tar files are identical hash according to newly retrieved archive But if there's a better process, please let me know :) Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Sounds good
I think it is preferable to switch all affected derivations to fetchzip. This should prevent this from happening again, if the actual content of the tarball is the same. Even better, you could add a fetchFromSourceHut function which uses fetchzip under the hood, like fetchFromGitHub and fetchFromGitLab. This would encourage people not to use fetchurl to fetch procedurally generated tarballs from sourcehut.
From a quick look at the ticket, this is supposed to be a one-time change to make the hash the same as in other forges though
I think getting the new hashes with e.g. should be enough (fetches securely via HTTPS and we should be able to trust that the contents remain unchanged). +1, that seems like the best (long-term) solution. Edit: And IMO we should keep using archives (e.g. because it's consistent with the GitHub and GitLab fetchers) and should indeed be fine now:
the point is: with fetchzip, we don't have to trust this pinky promise (I mean, I'm sure that they intend to keep it, but it could break unwillingly). That's exactly why fetchzip exists in the first place. So on fixes keeping fetchurl.
oh, my bad, I didn't read your comment carefully enough :o I thought you've meant vs. (which didn't make much sense) but realized now that it was vs. . :+1: for that then :)
Hah, same. too then
is merged now so you could submit a PR to switch the affected attributes/packages to the new (s. ). I can also take care of it if you want.
Change:
# Create device nodes in /dev. @preDeviceCommands@ echo "running udev..." <ins> ln -sfn /proc/self/fd /dev/fd </ins> mkdir -p /etc/systemd ln -sfn @linkUnits@ /etc/systemd/network mkdir -p /etc/udev

Discussion:
Describe the bug It's easiest to see in this picture: ! To Reproduce Steps to reproduce the behavior: system with nixpkgs at how init complains about /dev/fd/62 Expected behavior No error pertaining to /dev/fd/62. Screenshots See above. Additional context I don't actually remember when this started, because the boot logging scrolls so fast I missed it a few times (and I might have updated nixos-unstable-small at some point). The problematic line is: According to the blame, that hasn't been touched in 5 years, so I don't know why this would start cropping up now. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Why I think we should block on this: there should be no scary pointless outputs in the init script in nixos. Same if the activation script was being loud and scary for no reason.
So, I attempted to bisect this, but due to build failures (and the size of some builds) I was unable to pinpoint. However, I've now set up a machine that I can use for those huge builds, and will try to go further sometime soon. For anybody interested, below is my ( and ):
OK, I re-bisected (by removing all the skipped commits and building them on a machine) and got this result: cc What are the chances this is an issue with the package/one of our patches and not with upstream? New bisect log, for the curious:
did this happen in a VM, or on your real machine as well? What's with the `chown: invalid user" in there? Is this related?
I can reproduce in a VM and on my machine. Ignore everything below the fd error -- screenshot was taken from another issue, before I was able to build a VM myself. (EDIT: I've uploaded my own screenshot sans the JSON and errors, to make things clearer.) I'm going to try to bisect systemd soon, but it'll probably take a while, especially given how many patches there are that could fail to apply :P
OK, maybe the stuff is a red herring?

I d the entire call and got the following log: <details<summarystrace output</summary</detailsCan't interpret this now, but maybe it will give somebody an idea. Most interesting part to me:
Alright, thanks to my Google-fu, I found a diff that fixes the issue: According to , one of the articles that turned up, this might be caused by udev missing?
Change:
rm -rf $TMP_TURSES ''; <del> patchPhase = '' </del> <ins> postPatch = '' </ins> sed -i -e 's|urwid==1.3.0|urwid==${getVersion urwid}|' setup.py sed -i -e "s|future==0.14.3|future==${getVersion future}|" setup.py sed -i -e "s|tweepy==3.3.0|tweepy==${getVersion tweepy}|" setup.py

Discussion:
If you start without a config file, then it starts fine. But when later you exit it and start again, then it crashes with: This error was fixed in but it's not part of tool official releases. (Note that the original upstream repo no longer exists; so we should switch to fork of it. -env -f . -i python3.6-turses it with "q". Please run and paste the results.
Change:
<ins> diff --git a/CMakeLists.txt b/CMakeLists.txt index a407271b4..593628e0f 100755 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -310,7 +310,7 @@ if(GCC) endif() check_cxx_compiler_flag(-mstackrealign CC_HAS_STACK_REALIGN) if (CC_HAS_STACK_REALIGN) -        add_definitions(-mstackrealign) +        add_compile_options($<$<COMPILE_LANGUAGE:CXX>:-mstackrealign>) endif() # Disable exceptions. Reduce executable size, increase compability. check_cxx_compiler_flag(-fno-exceptions CC_HAS_FNO_EXCEPTIONS_FLAG) @@ -545,7 +545,7 @@ if((MSVC_IDE OR XCODE OR GCC) AND ENABLE_ASSEMBLY) list(APPEND ASM_OBJS ${ASM}.${SUFFIX}) add_custom_command( OUTPUT ${ASM}.${SUFFIX} -                COMMAND ${CMAKE_CXX_COMPILER} +                COMMAND ${CMAKE_ASM_COMPILER} ARGS ${ARM_ARGS} -c ${ASM_SRC} -o ${ASM}.${SUFFIX} DEPENDS ${ASM_SRC}) endforeach() diff --git a/common/CMakeLists.txt b/common/CMakeLists.txt index 12b643ad5..876f3543d 100644 --- a/common/CMakeLists.txt +++ b/common/CMakeLists.txt @@ -16,6 +16,7 @@ endif(EXTRA_LIB) if(ENABLE_ASSEMBLY) set_source_files_properties(threading.cpp primitives.cpp pixel.cpp PROPERTIES COMPILE_FLAGS -DENABLE_ASSEMBLY=1) list(APPEND VFLAGS "-DENABLE_ASSEMBLY=1") +    enable_language(ASM) endif(ENABLE_ASSEMBLY) if(ENABLE_ASSEMBLY AND X86) </ins>

Discussion:
Steps to reproduce the behavior: 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]:
Change:
<del> { stdenv, buildGo110Package, fetchFromGitHub }: </del> <ins> { stdenv, buildGoModule, fetchFromGitHub }: </ins> <del> buildGo110Package rec { name = "gomuks-${version}"; version = "2018-07-10"; </del> <ins> buildGoModule rec { pname = "gomuks"; version = "2019-06-28"; </ins> goPackagePath = "maunium.net/go/gomuks"; src = fetchFromGitHub { owner = "tulir"; <del> repo = "gomuks"; rev = "68db26bcace31297471641fe95f8882e301f5699"; sha256 = "0dagdvsvn8nwqsvjbqk1c6gg2q1m40869nayrkwm3ndg2xkfdpm6"; </del> <ins> repo = pname; rev = "37df8eb454088e61db7a14f382851205bc1806ad"; sha256 = "1hr15d9sbq6mddaxv3pwz86qp1hhzssgrvakfpc49xl4h04dq33g"; </ins> }; <ins> modSha256 = "1qrqgzzsxqvmy4m9shypa94bzw34mc941jhmyccip9grk9fzsxws"; </ins> meta = with stdenv.lib; { <del> homepage = https://maunium.net/go/gomuks/; </del> <ins> homepage = "https://maunium.net/go/gomuks/"; </ins> description = "A terminal based Matrix client written in Go"; license = licenses.gpl3; maintainers = with maintainers; [ tilpner ];

Discussion:
Looks like the current is 9+ months old. I took a crack at just updating the rev and sha256, but it looks like it might need a bit more attention (maybe just switching the derivation over to using the Go module functionality?). Leaving this mostly as a reminder to come back and look at this again soon. Please run and paste the results.
Change:
''CFLAGS=-DMOBILE_BROADBAND_PROVIDER_INFO="${mobile_broadband_provider_info}/share/mobile-broadband-provider-info/serviceproviders.xml"'' ]; <del> preFixup = '' rm $out/share/glib-2.0/schemas/gschemas.compiled''; </del> postInstall = '' mkdir -p $out/etc/NetworkManager/VPN ln -s ${networkmanager_openvpn}/etc/NetworkManager/VPN/nm-openvpn-service.name $out/etc/NetworkManager/VPN/nm-openvpn-service.name

Discussion:
the nm-applet from current channel-nixos errors out with (.nm-applet-wrapped:4399): GLib-GIO-ERROR **: Settings schema '' is not installed zsh: trace trap nm-applet there is a open pull request which also wants to fix schemas. might this address the same problem? cheers, jonas
Unfortunately the schemas problem needs to be addressed per-package (we can't have one global directory containing all schemas in the system). I don't understand this case, as everything seems fine. The schemas are in , they are compiled, and is wrapped to have them in search path.
Same issue here - I just rolled back for the moment.
the culprit is pull request . strace shows that only compiled schemas are consulted and the pull request deleted those in preFixup (under the surmise of it being caches). pull request including a partial revert follows shortly.
Change:
<ins> commit a9c556ccad819869a6a5d932aac0a75a99372f08 Author: Barry Warsaw <barry@python.org> Date:   Wed Sep 17 19:32:43 2014 +0300 _init_completion: Handle cword < 0 (LP: #1289597) Previously only bash 4.3 seemed to provoke this, but now with the empty command consistency tweak it occurs with earlier as well. diff --git a/bash_completion b/bash_completion index 7e01ae4..3bb4bc2 100644 --- a/bash_completion +++ b/bash_completion @@ -727,7 +727,7 @@ _init_completion() fi done -    [[ $cword -eq 0 ]] && return 1 +    [[ $cword -le 0 ]] && return 1 prev=${words[cword-1]} [[ ${split-} ]] && _split_longopt && split=true </ins>

Discussion:
Everytime I press TAB in an empty command prompt I get the error: I think this is related to
Note, that NixOS 14.12 is affected by this bug too. In bash-completion git repository there is commit that fixes this issue.
Needs bash-completion from master branch
Change:
, lndir , git , which <del> }@args: </del> <ins> }: </ins> let engineArtifactDirectory =

Discussion:
The provides a function to allow customized Flutter derivations to be made. Internally, however, it uses a function that calls with URLs generated from the given version number. Patches are also used internally, but there is no way (that I know of) to access these externally. I propose that and / attributes get to the attribute set along with , to make it easier to create custom Flutter derivations.
I was actually just about to file a bug about which produces this error instead of building, wonder if it's related, since it's breaking on flutter? cc
Sounds good
Change:
# FHS sys dirs presumably only have stuff for the build platform noSysDirs = (stdenv.targetPlatform != stdenv.hostPlatform) || noSysDirs; }; <ins> binutils-unwrapped-all-targets = callPackage ../development/tools/misc/binutils { autoreconfHook = if targetPlatform.isiOS then autoreconfHook269 else autoreconfHook; # FHS sys dirs presumably only have stuff for the build platform noSysDirs = (stdenv.targetPlatform != stdenv.hostPlatform) || noSysDirs; withAllTargets = true; }; </ins> binutils = wrapBintoolsWith { bintools = binutils-unwrapped; };

Discussion:
Describe the bug I am trying to get binutils to support all targets by overriding the withAllTargets argument. But I get the following error message: To Reproduce Steps to reproduce the behavior: nix-shell Expected behavior A shell environment containing binutils with all targets enabled. Additional context The higher-level goal is to obtain a version of that supports and targets. I need to copy a 32-bit PE object file to a 64-bit one. If there is a better way to accomplish this goal, I'd appreciate guidance. Metadata Please run and paste the result. Maintainer information:
Setting as well seems to be working fine. Is this expected? Then maybe the error message should somehow reflect that, if possible.
/cc
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. 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 .
Maybe i am completely wrong about this, but I think since this works with the issue most likely comes from .
I marked this as stale due to inactivity. &rarr;
I'm experiencing the same issue with .
Still a problem. I think the trigger is the use of in , but I don't understand why it matter for override. CLI reproducer:
Proposed the fix (and a new explicit attribute) as
Change:
(fetchNuGet { pname = "HidSharpCore"; version = "1.2.1.1"; sha256 = "1zkndglmz0s8rblfhnqcvv90rkq2i7lf4bc380g7z8h1avf2ikll"; }) (fetchNuGet { pname = "MessagePack"; version = "2.1.194"; sha256 = "1v2gyd9sd6hppfhlzngmzzhnpr39b95rwrqq0r9zzp480b6vzaj0"; }) (fetchNuGet { pname = "MessagePack.Annotations"; version = "2.1.194"; sha256 = "1jkhq3hiy4brvzsywl4p4jb9jrnzs3vmgr3s8fxpb1dzafadw8b0"; }) <del> (fetchNuGet { pname = "Microsoft.AspNetCore.App.Ref"; version = "5.0.0"; sha256 = "0d7sjr89zwq0wxirf8la05hfalv9nhvlczg1c7a508k8aw79jvfg"; }) (fetchNuGet { pname = "Microsoft.AspNetCore.App.Runtime.linux-arm64"; version = "5.0.17"; sha256 = "183xgqzlwd5lhacxdwcjl8vcq7r7xypv0hddps9k32mmmwf83d8h"; }) (fetchNuGet { pname = "Microsoft.AspNetCore.App.Runtime.linux-x64"; version = "5.0.17"; sha256 = "066fwdlssbv556zd9w1x87x1j8j4kafj9rxyy0692bssdb4gcyc8"; }) </del> (fetchNuGet { pname = "Microsoft.Bcl.AsyncInterfaces"; version = "1.1.1"; sha256 = "0a1ahssqds2ympr7s4xcxv5y8jgxs7ahd6ah6fbgglj4rki1f1vw"; }) (fetchNuGet { pname = "Microsoft.CodeCoverage"; version = "16.9.4"; sha256 = "11wiyy3ykgk1sa9amy3lgcsg2v7d1sz59ggw647vx8ibpjxijjpp"; }) (fetchNuGet { pname = "Microsoft.CSharp"; version = "4.0.1"; sha256 = "0zxc0apx1gcx361jlq8smc9pfdgmyjh6hpka8dypc9w23nlsh6yj"; })

Discussion:
Package name: opentabletdriver Latest released version: 0.6.1 <!-- Search your package here: --- Current version on the unstable channel: 0.6.0.4 Current version on the stable/release channel: 0.6.0.4 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
Change:
maintainers = with maintainers; [ lovek323 ]; platforms   = stdenv.lib.platforms.unix; }; <del> # t/swamp/{0,perl-without-extension} are datafiles for the test # t/ack-show-types.t, but the perl generic builder confuses them # for scripts and purifies them, making the test fail. preCheck = "sed -i '1s,.*,#!/usr/bin/perl -w,' t/swamp/0 t/swamp/perl-without-extension"; </del> <ins> # tests fails on nixos and hydra because of different purity issues doCheck = false; </ins> }; AlgorithmAnnotate = buildPerlPackage {

Discussion:
isso fails to install following the update to 0.13.0; Its test suite fails as detailed below (since you were the last one to update the package) Please run and paste the result.
Closing as fixed - automation failed
Change:
nodePackages.lodash ]; <ins> postPatch = '' # this is API change in glob >9 substituteInPlace helpers/generate-font-glyphs.js  --replace "require('glob').sync" "require('glob').globSync" ''; </ins> buildPhase = '' runHook preBuild

Discussion:
or on master (or unstable channel) Likely candidate for breakage is the bump in & the problematic usage have recently been dropped by upstream in favour of (), might make sense to avoid messing with this and just bump the package to the latest commit?
Change:
<ins> diff --git a/pyproject.toml b/pyproject.toml index 2c93a39..6c800e2 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -24,3 +24,7 @@ isort = "^4.3" [tool.black] line-length = 120 + +[build-system] +requires = ["poetry_core>=1.0.0"] +build-backend = "poetry.core.masonry.api" </ins>

Discussion:
Project description Generate architecture diagrams with python code. Allows for rapid iteration. Metadata homepage URL: source URL: license: mit platforms: linux, darwin This library requires graphviz (both native and the python library).
Change:
}).overrideAttrs (old: { # workaround the error: Permission denied: '/homeless-shelter' # backblaze-b2 fails to create a 'b2' directory under the XDG config path <del> HOME = "$(mktemp -d)"; </del> <ins> preHook = '' export HOME=$(mktemp -d) ''; </ins> }); meta = with lib; {

Discussion:
Steps to reproduce the behavior: on <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- I don't have a machine, the failure is discovered by ofborg. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Closed by
No, that fixes runtime issue . Darwin still has failing tests