jiebi/CodeConvo huggingface dataset:
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: makeWrapperArgs = [ "--prefix" "PATH" ":" (lib.makeBinPath bins) <ins> "${gappsWrapperArgs[@]}" </ins> ]; <ins> dontWrapGApps = true; </ins> outputs = [ "out" "man" ]; postBuild = '' make -C man
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: setuptools, wrapGAppsNoGuiHook, notify2, <ins> glib </ins> }: let
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: --replace-fail "plugdev" "openrazer" ''; <del> nativeBuildInputs = [ setuptools wrapGAppsNoGuiHook ]; </del> <ins> nativeBuildInputs = [ setuptools wrapGAppsNoGuiHook gobject-introspection ]; buildInputs = [ glib gtk3 ]; </ins> propagatedBuildInputs = [ daemonize dbus-python <del> gobject-introspection gtk3 </del> pygobject3 pyudev setproctitle
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: <del> { lib, stdenv, fetchFromGitHub, meson, ninja, pkg-config </del> <ins> { lib, stdenv, fetchFromGitHub, meson, ninja, pkg-config, wrapGAppsNoGuiHook, gobject-introspection </ins> , glib, systemd, udev, libevdev, gitMinimal, check, valgrind, swig, python3 , json-glib, libunistring }:
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: }; nativeBuildInputs = [ <del> meson ninja pkg-config gitMinimal swig check valgrind </del> <ins> meson ninja pkg-config gitMinimal swig check valgrind wrapGAppsNoGuiHook gobject-introspection </ins> ]; buildInputs = [
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: <del> { lib, python3, fetchFromGitHub, nixosTests }: </del> <ins> { lib, python3, fetchFromGitHub, nixosTests, wrapGAppsNoGuiHook, gobject-introspection, glib }: </ins> python3.pkgs.buildPythonApplication rec { pname = "targetcli";
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: hash = "sha256-9QYo7jGk9iWr26j0qPQCqYsJ+vLXAsO4Xs7+7VT9/yc="; }; <del> propagatedBuildInputs = with python3.pkgs; [ configshell rtslib ]; </del> <ins> nativeBuildInputs = [ wrapGAppsNoGuiHook gobject-introspection ]; buildInputs = [ glib ]; propagatedBuildInputs = with python3.pkgs; [ configshell rtslib pygobject3 ]; </ins> postInstall = '' install -D targetcli.8 -t $out/share/man/man8/
Code change:
a TUI-like CLI tool to manage the features of a Rust project Metadata homepage URL: source URL: license: mit platforms: everything that Rust supports Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <ins> { lib, rustPlatform, fetchFromGitHub, }: rustPlatform.buildRustPackage rec { pname = "cargo-features-manager"; version = "0.8.0"; src = fetchFromGitHub { owner = "ToBinio"; repo = "cargo-features-manager"; rev = "v${version}"; hash = "sha256-ez8WIDHV6/f0Kk6cvzB25LoYBPT+JTzmOWrSxXXzpBc="; }; cargoHash = "sha256-G1MBH4c9b/h87QgCleTMnndjWc70KZI+6W4KWaxk28o="; meta = { description = "A command-line tool for managing Architectural Decision Records"; homepage = "https://github.com/ToBinio/cargo-features-manager"; changelog = "https://github.com/ToBinio/cargo-features-manager/blob/v${version}/CHANGELOG.md"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ luftmensch-luftmensch ]; mainProgram = "cargo-features-manager"; }; } </ins>
Code change:
When configuring notifypush for nextcloud the service almost always fails the first time after rebooting the system and requires to be restarted in order to be started successfully. It seems the problem is that notifypush has not finished starting before nextcloud-notifypush-post-start is executed, resulting in a missing or not connected . Steps to reproduce the behavior: notifypush the system (un)lucky and watch nextcloud-notifypush.service` fail service (done automatically) The service starts successfully the first time. Relevant log lines: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have noticed a similar behavior when the module it was introduced. But i was so far happy with the restart situation. I have played a bit with the situation. I am currently applying the following additional configs to my nextcloud. I think the problem is, that notify_push creates the used socket at start, and we are to early executing the ExecStartPost command to configure. When we let systemd take care for the socket, i could mitigate that and after that i had problems that my acme certificate reload was running in the mean time. After adding nginx-config-reload it was able to run on first try after reboot. You could check if that is also helping on your end and if yes we could check what make sense to use in the module.
I am not sure if this is a good idea since existing Unix sockets are on server startup (and shutdown), possibly interfering with the socket management of SystemD. I don't know why the connection succeeds after restart or when the socket provided by SystemD is replaced by another socket by notifypush, but I think a more robust way to implement this is to set which would delay the execution of until the server signals that it is ready. However something like this would require support by upstream, I could work on a pull request. Edit: After doing some testing it seems that for notifying SystemD to work notify_push has to be the main process of the service, which can be arranged easily by using in the start script.
Doesn't have the program call sdnotify for that to work? I did not find something like that on the code base. here the notify section claims something like that. Tho I fully agree that the socket is likely not a good idea when notifypush nukes the socket file. Edit: NVM you mentioned a upstream pr for such a function , which I seem to have over read when reading my mail notification.

Related discussion:
text: export DATABASE_PASSWORD="$(<"${cfg.dbpassFile}")" '' + '' export DATABASE_URL="${dbUrl}" <del> ${cfg.package}/bin/notify_push '${cfgN.datadir}/config/config.php' </del> <ins> exec ${cfg.package}/bin/notify_push '${cfgN.datadir}/config/config.php' </ins> ''; serviceConfig = { User = "nextcloud";
Code change:
When configuring notifypush for nextcloud the service almost always fails the first time after rebooting the system and requires to be restarted in order to be started successfully. It seems the problem is that notifypush has not finished starting before nextcloud-notifypush-post-start is executed, resulting in a missing or not connected . Steps to reproduce the behavior: notifypush the system (un)lucky and watch nextcloud-notifypush.service` fail service (done automatically) The service starts successfully the first time. Relevant log lines: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have noticed a similar behavior when the module it was introduced. But i was so far happy with the restart situation. I have played a bit with the situation. I am currently applying the following additional configs to my nextcloud. I think the problem is, that notify_push creates the used socket at start, and we are to early executing the ExecStartPost command to configure. When we let systemd take care for the socket, i could mitigate that and after that i had problems that my acme certificate reload was running in the mean time. After adding nginx-config-reload it was able to run on first try after reboot. You could check if that is also helping on your end and if yes we could check what make sense to use in the module.
I am not sure if this is a good idea since existing Unix sockets are on server startup (and shutdown), possibly interfering with the socket management of SystemD. I don't know why the connection succeeds after restart or when the socket provided by SystemD is replaced by another socket by notifypush, but I think a more robust way to implement this is to set which would delay the execution of until the server signals that it is ready. However something like this would require support by upstream, I could work on a pull request. Edit: After doing some testing it seems that for notifying SystemD to work notify_push has to be the main process of the service, which can be arranged easily by using in the start script.
Doesn't have the program call sdnotify for that to work? I did not find something like that on the code base. here the notify section claims something like that. Tho I fully agree that the socket is likely not a good idea when notifypush nukes the socket file. Edit: NVM you mentioned a upstream pr for such a function , which I seem to have over read when reading my mail notification.

Related discussion:
text: RuntimeDirectory = [ "nextcloud-notify_push" ]; Restart = "on-failure"; RestartSec = "5s"; <ins> Type = "notify"; </ins> }; };
Code change:
Hey all, not sure which template is most appropriate for this, apologies if the format is incorrect. It looks like this package no longer exists upstream--the repository owner seems to have deleted or renamed their account. I'm not aware of any maintained forks of this project, so I think this package is completely dead, and should be removed from . Note: while searching for forks, I noted that 1Password appears to . Without access to the original package, I can't say for sure they are equivalent, but may be worth investigating for any affected users. Package name: Latest released version: GONE <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <del> { lib, buildGoModule, fetchFromGitHub }: buildGoModule rec { pname = "git-credential-1password"; version = "1.2.1"; src = fetchFromGitHub { owner = "develerik"; repo = pname; rev = "v${version}"; sha256 = "sha256-8qdUOJ0MOk/xVvp3kDuxNRo3lMEJhLeI3Fle0tuZez0="; }; vendorHash = "sha256-B6BlVnUX4XLT+9EpL63Ht4S8Wo84RsmY99CL+srQfpw="; meta = with lib; { description = "A git credential helper for 1Password"; homepage = "https://github.com/develerik/git-credential-1password"; changelog = "https://github.com/develerik/git-credential-1password/releases/tag/v${version}"; license = licenses.isc; maintainers = [ maintainers.ivankovnatsky ]; mainProgram = "git-credential-1password"; }; } </del>
Code change:
Hey all, not sure which template is most appropriate for this, apologies if the format is incorrect. It looks like this package no longer exists upstream--the repository owner seems to have deleted or renamed their account. I'm not aware of any maintained forks of this project, so I think this package is completely dead, and should be removed from . Note: while searching for forks, I noted that 1Password appears to . Without access to the original package, I can't say for sure they are equivalent, but may be worth investigating for any affected users. Package name: Latest released version: GONE <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: ghostwriter = libsForQt5.kdeGear.ghostwriter; # Added 2023-03-18 go-dependency-manager = throw "'go-dependency-manager' is unmaintained and the go community now uses 'go.mod' mostly instead"; # Added 2023-10-04 gotktrix = throw "'gotktrix' has been removed, as it was broken and unmaintained"; # Added 2023-12-06 <ins> git-credential-1password = throw "'git-credential-1password' has been removed, as the upstream project is deleted."; # Added 2024-05-20 </ins> git-subset = throw "'git-subset' has been removed in favor of 'git-filter-repo'"; # Added 2023-01-13 gitAndTools = self // {
Code change:
Hey all, not sure which template is most appropriate for this, apologies if the format is incorrect. It looks like this package no longer exists upstream--the repository owner seems to have deleted or renamed their account. I'm not aware of any maintained forks of this project, so I think this package is completely dead, and should be removed from . Note: while searching for forks, I noted that 1Password appears to . Without access to the original package, I can't say for sure they are equivalent, but may be worth investigating for any affected users. Package name: Latest released version: GONE <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: git-crecord = callPackage ../applications/version-management/git-crecord { }; <del> git-credential-1password = callPackage ../applications/version-management/git-credential-1password { }; </del> git-credential-keepassxc = darwin.apple_sdk_11_0.callPackage ../applications/version-management/git-credential-keepassxc { inherit (darwin.apple_sdk.frameworks) DiskArbitration Foundation; };
Code change:
A clear and concise description of what the bug is. Steps to reproduce the behavior: Mac Silicon, Utilizing with nix-darwin, i've the folllowing : always get qemu-system-aarch64 as qemu binary and then an aarch64 linux builder uname -a should give x86-64_linux Qemu binary program in () should not be forced to hostPlatform system for this linux builder case If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Did not find any issues related to this qemu program choice.
I think the qemu binary is set correctly in the builders, in this file: I was also having this problem, and found this issue while looking into it. But I realized the result is being caused by these lines in nix-darwin: () That looks fine, but the builder package we're trying to use is also created using override! So the in nix-darwin is overriding the in nixpkgs, making the resulting package have the default hostPlatform. You can work around this by setting that value in your nix darwin config, like this: I've opened a pull request to make this work the way we expected it to: Thank you for this issue, it confirmed that I wasn't the only person having this problem, and led me to find the cause.
Thanks a lot !

Related discussion:
text: x@{builderDefsPackage , gnome, gtk, glib, libxml2, pkgconfig, libvirt, gtkvnc, cyrus_sasl, libtasn1 <del> , gnupg, libgcrypt, perl, nettle, yajl </del> <ins> , gnupg, libgcrypt, perl, nettle, yajl, libcap_ng </ins> , ...}: builderDefsPackage (a :
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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 /cc <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <del> From: Jack Baldry <jack.baldry@grafana.com> Date: Tue, 15 Nov 2022 15:40:31 -0400 Subject: [PATCH] Remove circular definition of AUDIT_FILTER_EXCLUDE https://github.com/osquery/osquery/issues/6551 Signed-off-by: Jack Baldry <jack.baldry@grafana.com> --- libraries/cmake/source/libaudit/src/lib/libaudit.h | 1 - 1 file changed, 1 deletion(-) diff --git a/libraries/cmake/source/libaudit/src/lib/libaudit.h b/libraries/cmake/source/libaudit/src/libaudit.h --- a/libraries/cmake/source/libaudit/src/lib/libaudit.h +++ b/libraries/cmake/source/libaudit/src/lib/libaudit.h @@ -260,7 +260,6 @@ extern "C" { #define AUDIT_KEY_SEPARATOR 0x01 /* These are used in filter control */ -#define AUDIT_FILTER_EXCLUDE	AUDIT_FILTER_TYPE #define AUDIT_FILTER_MASK	0x07	/* Mask to get actual filter */ #define AUDIT_FILTER_UNSET	0x80	/* This value means filter is unset */ -- 2.38.1 </del>
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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 /cc <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <del> diff --git a/libraries/cmake/source/augeas/gnulib/generated/linux/aarch64/lib/locale.h b/libraries/cmake/source/augeas/gnulib/generated/linux/aarch64/lib/locale.h index 4f9baece2..afe947956 100644 --- a/libraries/cmake/source/augeas/gnulib/generated/linux/aarch64/lib/locale.h +++ b/libraries/cmake/source/augeas/gnulib/generated/linux/aarch64/lib/locale.h @@ -48,9 +48,9 @@ /* NetBSD 5.0 mis-defines NULL.  */ #include <stddef.h> -/* Mac OS X 10.5 defines the locale_t type in <xlocale.h>.  */ +/* Mac OS X 10.5 defines the locale_t type in <locale.h>.  */ #if 1 -# include <xlocale.h> +# include <locale.h> #endif /* The definitions of _GL_FUNCDECL_RPL etc. are copied here.  */ diff --git a/libraries/cmake/source/augeas/gnulib/generated/linux/x86_64/lib/locale.h b/libraries/cmake/source/augeas/gnulib/generated/linux/x86_64/lib/locale.h index 4f9baece2..afe947956 100644 --- a/libraries/cmake/source/augeas/gnulib/generated/linux/x86_64/lib/locale.h +++ b/libraries/cmake/source/augeas/gnulib/generated/linux/x86_64/lib/locale.h @@ -48,9 +48,9 @@ /* NetBSD 5.0 mis-defines NULL.  */ #include <stddef.h> -/* Mac OS X 10.5 defines the locale_t type in <xlocale.h>.  */ +/* Mac OS X 10.5 defines the locale_t type in <locale.h>.  */ #if 1 -# include <xlocale.h> +# include <locale.h> #endif /* The definitions of _GL_FUNCDECL_RPL etc. are copied here.  */ </del>