jiebi/CodeConvo huggingface dataset:
Code change:
Steps to reproduce the behavior: cryptowatch-desktop download url redirects to a blog Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
As of September the 30th 2023, Cryptowatch was sunset and users were advised to use their parent companies offering Kraken Pro. I'll create a pull request to remove cryptowatch from nixpkgs as there aren't any archives available that contain it that are reliable

Related discussion:
text: composable_kernel = throw "'composable_kernel' has been replaced with 'rocmPackages.composable_kernel'"; # Added 2023-10-08 cpp-ipfs-api = cpp-ipfs-http-client; # Project has been renamed. Added 2022-05-15 crispyDoom = crispy-doom; # Added 2023-05-01 <ins> cryptowatch-desktop = throw "Cryptowatch Desktop was sunset on September 30th 2023 and has been removed from nixpkgs"; # Added 2023-12-22 </ins> clash = throw "'clash' has been removed, upstream gone. Consider using 'clash-meta' instead."; # added 2023-11-10 clasp = clingo; # added 2022-12-22 claws-mail-gtk3 = claws-mail; # Added 2021-07-10
Code change:
Steps to reproduce the behavior: cryptowatch-desktop download url redirects to a blog Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
As of September the 30th 2023, Cryptowatch was sunset and users were advised to use their parent companies offering Kraken Pro. I'll create a pull request to remove cryptowatch from nixpkgs as there aren't any archives available that contain it that are reliable

Related discussion:
text: crow-translate = libsForQt5.callPackage ../applications/misc/crow-translate { }; <del> cryptowatch-desktop = callPackage ../applications/finance/cryptowatch { }; </del> dae = callPackage ../tools/networking/dae { }; darling = callPackage ../applications/emulators/darling { };
Code change:
While working on some documentation on Nixpkgs, I noticed that there doesn't seem to be a convention for showing shell commands and their outputs. prepends to the command prompt, and output as a normal, not-indented line. adds a comment above the command prompt showing what the output is. uses two different code blocks, one with the command, the other with the output. Additionally, there are other code blocks to show expressions and their result inside the nix repl: prepends to the (error) output. And prepends to the output. Note that the proposal below was written just to have some starting proposal, but not much thought has been given to other alternatives yet. My current proposal is to adopt the following convention: For shell commands and outputs, prepend to any lines that are part of the command, and put outputs in their own lines as-is. If the command has line continuations, don't prepend , but add some indentation to keep it from looking like an output. For example: For nix repl expressions, prepend to any lines part of an expression, and put outputs in their own lines as-is. <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Talked about this in the docs team meeting, I think this is a good idea! If you make a PR to describe this convention in the I could review/merge it. I guess very generally, the convention is to use the format as you'd see it in the REPL.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Related discussion:
text: In an effort to keep the Nixpkgs manual in a consistent style, please follow the conventions below, unless they prevent you from properly documenting something. In that case, please open an issue about the particular documentation convention and tag it with a "needs: documentation" label. <ins> When needed, each convention explain why it exists, so you can make a decision whether to follow it or not based on your particular case. Note that these conventions are about the **structure** of the manual (and its source files), not about the content that goes in it. You, as the writer of documentation, are still in charge of its content. </ins> - Put each sentence in its own line. This makes reviews and suggestions much easier, since GitHub's review system is based on lines.
Code change:
While working on some documentation on Nixpkgs, I noticed that there doesn't seem to be a convention for showing shell commands and their outputs. prepends to the command prompt, and output as a normal, not-indented line. adds a comment above the command prompt showing what the output is. uses two different code blocks, one with the command, the other with the output. Additionally, there are other code blocks to show expressions and their result inside the nix repl: prepends to the (error) output. And prepends to the output. Note that the proposal below was written just to have some starting proposal, but not much thought has been given to other alternatives yet. My current proposal is to adopt the following convention: For shell commands and outputs, prepend to any lines that are part of the command, and put outputs in their own lines as-is. If the command has line continuations, don't prepend , but add some indentation to keep it from looking like an output. For example: For nix repl expressions, prepend to any lines part of an expression, and put outputs in their own lines as-is. <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Talked about this in the docs team meeting, I think this is a good idea! If you make a PR to describe this convention in the I could review/merge it. I guess very generally, the convention is to use the format as you'd see it in the REPL.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Related discussion:
text: # pkgs.coolFunction Description of what `coolFunction` does. <ins> ## Inputs </ins> `coolFunction` expects a single argument which should be an attribute set, with the following possible attributes: `name` (String)
Code change:
Project description A tool to help efficiently focus windows in Sway inspired by i3-easyfocus: basically you press a key and hints ("q", "w", ...) popup on the titlebars, you can then press "q" to focus the window matching the "q" key. Metadata homepage URL: source URL: license: mit platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <ins> { lib , rustPlatform , fetchFromGitHub , pkg-config , wrapGAppsHook , atk , cairo , gdk-pixbuf , glib , gtk3 , pango , gtk-layer-shell }: rustPlatform.buildRustPackage rec { pname = "sway-easyfocus"; version = "unstable-2023-11-05"; src = fetchFromGitHub { owner = "edzdez"; repo = "sway-easyfocus"; rev = "4c70f6728dbfc859e60505f0a7fd82f5a90ed42c"; hash = "sha256-WvYXhf13ZCoa+JAF4bYgi5mI22i9pZLtbIhF1odqaTU="; }; cargoHash = "sha256-9cN0ervcU8JojwG7J250fprbCD2rB9kh9TbRU+wCE/Y="; nativeBuildInputs = [ pkg-config wrapGAppsHook ]; buildInputs = [ atk cairo gdk-pixbuf glib gtk3 gtk-layer-shell pango ]; meta = { description = "A tool to help efficiently focus windows in Sway, inspired by i3-easyfocus"; homepage = "https://github.com/edzdez/sway-easyfocus"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ eclairevoyant ]; mainProgram = "sway-easyfocus"; }; } </ins>
Code change:
DaVinci Resolve Studio is missing a entry for application launchers Steps to reproduce the behavior: should contain a entry for application launchers If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
See

Related discussion:
text: desktopItems = [ (makeDesktopItem { <del> name = "davinci-resolve"; desktopName = "Davinci Resolve"; </del> <ins> name = "davinci-resolve${lib.optionalString studioVariant "-studio"}"; desktopName = "Davinci Resolve${lib.optionalString studioVariant " Studio"}"; </ins> genericName = "Video Editor"; <del> exec = "resolve"; # icon = "DV_Resolve"; </del> <ins> exec = "davinci-resolve${lib.optionalString studioVariant "-studio"}"; icon = "davinci-resolve${lib.optionalString studioVariant "-studio"}"; </ins> comment = "Professional video editing, color, effects and audio post-processing"; categories = [ "AudioVideo"
Code change:
DaVinci Resolve Studio is missing a entry for application launchers Steps to reproduce the behavior: should contain a entry for application launchers If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
See

Related discussion:
text: '' }"; <ins> extraInstallCommands = '' mkdir -p $out/share/applications $out/share/icons/hicolor/128x128/apps ln -s ${davinci}/share/applications/*.desktop $out/share/applications/ ln -s ${davinci}/graphics/DV_Resolve.png $out/share/icons/hicolor/128x128/apps/davinci-resolve${lib.optionalString studioVariant "-studio"}.png ''; </ins> passthru = { inherit davinci; updateScript = lib.getExe (writeShellApplication {
Code change:
DaVinci Resolve Studio is missing a entry for application launchers Steps to reproduce the behavior: should contain a entry for application launchers If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
See

Related discussion:
text: maintainers = with maintainers; [ amarshall jshcmpbll orivej ]; platforms = [ "x86_64-linux" ]; sourceProvenance = with sourceTypes; [ binaryNativeCode ]; <del> mainProgram = "davinci-resolve"; </del> <ins> mainProgram = "davinci-resolve${lib.optionalString studioVariant "-studio"}"; </ins> }; }
Code change:
New version of the invidious module gives an error on old system state versions with the following message: Config option doesn’t seem to exist and doesn’t do anything when set. Manually setting gets config to build, but service still doesn’t start with permission error, even after running the suggested reassign command: database seems to be correctly owned by the user: Steps to reproduce the behavior: invidious with local database on system state before 24.05: an error message, try to perform suggested fix. Find out that the suggested setting doesn’t exist and use instead: as suggested by the error message. to start . permission error. Service should successfully start after applying suggested fixes. Error message shouldn’t refer to non-existent options. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The correct configuration should look like this if your state version is before 24.05: Looks like there is a mistake in the error message ( and are both specified and only the former is correct). Can you please try again with set to ?
Yes, I’ve tried this (steps 2+ of reproduction). I’ve mistakenly wrote in my initial issue, sorry, I’ve tried setting . It gets config to build, but it doesn’t start with the error described in the first post. I’ll amend the issue text now.
Can you show us the output of
Sure! I see the problem now. I’ve tried to run the command without selecting the database first. After running it with database selected, service starts successfully. Thanks!
Super. Can you please look at the PR and tell me if the improved language would have solved your issue?
Yeah, thanks, that would’ve been clear!

Related discussion:
text: to  work, the username used to connect to PostgreSQL must match the database name, that is services.invidious.settings.db.user must match services.invidious.settings.db.dbname. This is the default since NixOS 24.05. For older systems, it is normally safe to manually set <del> services.invidious.database.user to "invidious" as the new user will be created with permissions for the existing database. `REASSIGN OWNED BY kemal TO invidious;` may also be needed. </del> <ins> the user to "invidious" as the new user will be created with permissions for the existing database. `REASSIGN OWNED BY kemal TO invidious;` may also be needed, it can be run as `sudo -u postgres env psql --user=postgres --dbname=invidious -c 'reassign OWNED BY kemal to invidious;'`. </ins> ''; } ];
Code change:
labwc-tweaks failes to start no matter what I do I get this error message if I try to open it in terminal: Error opening file: No such file or directory Run labwc-tweaks in the terminal labwc-tweaks starting Please run and paste the result. these 4 paths will be fetched (0.03 MiB download, 0.17 MiB unpacked): /nix/store/1alqjnr40dsk7cl15l5sn5y2zdxidc1v-binutils-wrapper-2.40 /nix/store/4dr83a4wn25zkb5pvsq2y3q3v586jzs9-expand-response-params /nix/store/90h6k8ylkgn81k10190v5c9ldyjpzgl9-gcc-wrapper-12.3.0 /nix/store/wr08yanv2bjrphhi5aai12hf2qz5kvic-stdenv-linux copying path '/nix/store/4dr83a4wn25zkb5pvsq2y3q3v586jzs9-expand-response-params' from ''... copying path '/nix/store/1alqjnr40dsk7cl15l5sn5y2zdxidc1v-binutils-wrapper-2.40' from ''... copying path '/nix/store/90h6k8ylkgn81k10190v5c9ldyjpzgl9-gcc-wrapper-12.3.0' from ''... copying path '/nix/store/wr08yanv2bjrphhi5aai12hf2qz5kvic-stdenv-linux' from ''... system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The issue might be related to this hard coded path: it seems like that xkeyboard_config provides this file
Until recently the keyboard related files were available in . Fixed in

Related discussion:
text: , pkg-config , gtk3 , libxml2 <ins> , xkeyboard_config </ins> , wrapGAppsHook <ins> , unstableGitUpdater </ins> }: stdenv.mkDerivation (finalAttrs: { pname = "labwc-tweaks"; <del> version = "unstable-2023-12-08"; </del> <ins> version = "unstable-2024-01-04"; </ins> src = fetchFromGitHub { owner = "labwc"; <del> repo = finalAttrs.pname; rev = "1c79d6a5ee3ac3d1a6140a1a98ae89674ef36635"; hash = "sha256-RD1VCKVoHsoY7SezY7tjZzomikMgA7N6B5vaYkIo9Es="; </del> <ins> repo = "labwc-tweaks"; rev = "1604f64cc62e4800ee04a6e1c323a48ee8140d83"; hash = "sha256-xFvc+Y03HjSvj846o84Wpk5tEXI49z8xkILSX2oas8A="; </ins> }; nativeBuildInputs = [
Code change:
labwc-tweaks failes to start no matter what I do I get this error message if I try to open it in terminal: Error opening file: No such file or directory Run labwc-tweaks in the terminal labwc-tweaks starting Please run and paste the result. these 4 paths will be fetched (0.03 MiB download, 0.17 MiB unpacked): /nix/store/1alqjnr40dsk7cl15l5sn5y2zdxidc1v-binutils-wrapper-2.40 /nix/store/4dr83a4wn25zkb5pvsq2y3q3v586jzs9-expand-response-params /nix/store/90h6k8ylkgn81k10190v5c9ldyjpzgl9-gcc-wrapper-12.3.0 /nix/store/wr08yanv2bjrphhi5aai12hf2qz5kvic-stdenv-linux copying path '/nix/store/4dr83a4wn25zkb5pvsq2y3q3v586jzs9-expand-response-params' from ''... copying path '/nix/store/1alqjnr40dsk7cl15l5sn5y2zdxidc1v-binutils-wrapper-2.40' from ''... copying path '/nix/store/90h6k8ylkgn81k10190v5c9ldyjpzgl9-gcc-wrapper-12.3.0' from ''... copying path '/nix/store/wr08yanv2bjrphhi5aai12hf2qz5kvic-stdenv-linux' from ''... system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The issue might be related to this hard coded path: it seems like that xkeyboard_config provides this file
Until recently the keyboard related files were available in . Fixed in

Related discussion:
text: strictDeps = true; postPatch = '' <del> substituteInPlace stack-lang.c --replace /usr/share /run/current-system/sw/share sed -i '/{ NULL, "/usr/share" },/i { NULL, "/run/current-system/sw/share" },' theme.c </del> <ins> substituteInPlace stack-lang.c --replace /usr/share/X11/xkb ${xkeyboard_config}/share/X11/xkb substituteInPlace theme.c --replace /usr/share /run/current-system/sw/share </ins> ''; <ins> passthru.updateScript = unstableGitUpdater { }; </ins> meta = { homepage = "https://github.com/labwc/labwc-tweaks"; description = "Configuration gui app for labwc"; mainProgram = "labwc-tweaks"; <del> license = lib.licenses.gpl2Plus; </del> <ins> license = lib.licenses.gpl2Only; </ins> platforms = lib.platforms.unix; <del> maintainers = with lib.maintainers; [ romildo ]; </del> <ins> maintainers = with lib.maintainers; [ AndersonTorres romildo ]; </ins> }; })
Code change:
Project description Command line program which provides a suite of tools to create shopping lists and maintain recipes. Metadata homepage URL: source URL: license: mit platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
A nix-shell script here () which provides a decent starting point. cc

Related discussion:
text: githubId = 428026; name = "embr"; }; <ins> emilioziniades = { email = "emilioziniades@protonmail.com"; github = "emilioziniades"; githubId = 75438244; name = "Emilio Ziniades"; }; </ins> emily = { email = "nixpkgs@emily.moe"; github = "emilazy";
Code change:
Project description Command line program which provides a suite of tools to create shopping lists and maintain recipes. Metadata homepage URL: source URL: license: mit platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
A nix-shell script here () which provides a decent starting point. cc

Related discussion:
text: <ins> { lib , stdenv , fetchFromGitHub , buildNpmPackage , rustPlatform , pkg-config , openssl , darwin }: rustPlatform.buildRustPackage rec { pname = "cook-cli"; version = "0.7.1"; src = fetchFromGitHub { owner = "cooklang"; repo = "cookcli"; rev = "v${version}"; hash = "sha256-3gLVsk6GCxOG24Md7E9fk28Vnc4kVDdwyZUD/GtSwFE="; }; cargoHash = "sha256-6lnURuE1cgNAniHl5ozXo1W3cLYYje7er+ZhvZDKdVg="; nativeBuildInputs = [ pkg-config openssl ]; buildInputs = [ openssl ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.SystemConfiguration ]; postPatch = '' rm -rf "ui/public" ln -s ${passthru.ui} "ui/public" ''; OPENSSL_NO_VENDOR = 1; passthru.ui = buildNpmPackage { name = "ui"; src = "${src}/ui"; npmDepsHash = "sha256-uMyOAYLVHhY4ytvEFvVzdoQ7ExzQ4sH+ZtDrEacu5bk="; makeCacheWritable = true; npmFlags = [ "--legacy-peer-deps" ]; installPhase = '' runHook preInstall mv public/ $out runHook postInstall ''; }; meta = with lib; { changelog = "https://github.com/cooklang/cookcli/releases/tag/v${version}"; description = "A suite of tools to create shopping lists and maintain recipes"; homepage = "https://cooklang.org/"; license = [ licenses.mit ]; mainProgram = "cook"; maintainers = [ maintainers.emilioziniades ]; platforms = platforms.linux ++ platforms.darwin; }; } </ins>
Code change:
Package name: solana-cli Latest released version: 1.16.27 <!-- Search your package here: --- Current version on the unstable channel: 1.14.23 Current version on the stable/release channel: 1.14.23 <!-- 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]:
Hello I was able make the building script work so solana-cli is updated to 1.16.27 expect solana has bug in a which doesn't let me compile. The issue was already reported back back in 22 november 2023: solana-labs/solana So until is fixed I can't do anything more, as soon as it is fixed I will post my pr
Thanks , did you manage to build it for the current version? () On the master of nixpkgs I couldn't even build the existing version of Solana due a rocksdb issue I also found this commit on homebrew PRs. Seems like they patched this part in order to make the build work:
Hello I didn't test it and I don't think I need since I made it able to compile 1.16.27 I appreciate the citation, with the patch used by them I was able to fix it, appreciate your help

Related discussion:
text: githubId = 4732885; name = "Ivan Jager"; }; <ins> aikooo7 = { name = "Diogo Fernandes"; email = "prozinhopro1973@gmail.com"; matrix = "@aikoo7:matrix.org"; github = "aikooo7"; githubId = 79667753; keys = [{ fingerprint = "B0D7 2955 235F 6AB5 ACFA  1619 8C7F F5BB 1ADE F191"; }]; }; </ins> aiotter = { email = "git@aiotter.com"; github = "aiotter";
Code change:
Package name: solana-cli Latest released version: 1.16.27 <!-- Search your package here: --- Current version on the unstable channel: 1.14.23 Current version on the stable/release channel: 1.14.23 <!-- 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]:
Hello I was able make the building script work so solana-cli is updated to 1.16.27 expect solana has bug in a which doesn't let me compile. The issue was already reported back back in 22 november 2023: solana-labs/solana So until is fixed I can't do anything more, as soon as it is fixed I will post my pr
Thanks , did you manage to build it for the current version? () On the master of nixpkgs I couldn't even build the existing version of Solana due a rocksdb issue I also found this commit on homebrew PRs. Seems like they patched this part in order to make the build work:
Hello I didn't test it and I don't think I need since I made it able to compile 1.16.27 I appreciate the citation, with the patch used by them I was able to fix it, appreciate your help

Related discussion:
text: <ins> diff --git a/sdk/program/src/account_info.rs b/sdk/program/src/account_info.rs index 372370d0e15a0f2877b02ad29586e5b352438b24..3db3e9839b6535786e60be5602c03d0c909bf937 100644 --- a/sdk/program/src/account_info.rs +++ b/sdk/program/src/account_info.rs @@ -182,6 +182,7 @@ impl<'a> AccountInfo<'a> { Ok(()) } +    #[rustversion::attr(since(1.72), allow(invalid_reference_casting))] pub fn assign(&self, new_owner: &Pubkey) { // Set the non-mut owner field unsafe { </ins>