jiebi/CodeConvo huggingface dataset:
Code change:
Package name: ms-vscode.cpptools Latest released version: 1.20.2 <!-- Search your package here: --- Current version on the unstable channel: 1.17.3 Current version on the stable/release channel: 1.17.3 <!-- 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: gdbDefaultsTo = if gdbUseFixed then "${gdb}/bin/gdb" else "gdb"; supported = { x86_64-linux = { <del> hash = "sha256-4mKCBqUCOndKEfsJqTIsfwEt+0CZI8QAhBj3Y4+wKlg="; </del> <ins> hash = "sha256-p8WFmkQKdzXF0FTWHabyeFMkwXa2RkDRM9SvvkBIOLY="; </ins> arch = "linux-x64"; }; aarch64-linux = { <del> hash = "sha256-Kjl8mEpayA1xMHEAMJ5k3Ctk3l48KlUBU5w3dL4pGWM="; </del> <ins> hash = "sha256-HISE8/M9IpeI8iX0mmw9owExnpgiwpesE7YG/+QFYgc="; </ins> arch = "linux-arm64"; }; };
Code change:
Package name: ms-vscode.cpptools Latest released version: 1.20.2 <!-- Search your package here: --- Current version on the unstable channel: 1.17.3 Current version on the stable/release channel: 1.17.3 <!-- 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: mktplcRef = base // { name = "cpptools"; publisher = "ms-vscode"; <del> version = "1.17.3"; </del> <ins> version = "1.20.2"; </ins> }; nativeBuildInputs = [
Code change:
Steps to reproduce the behavior: python311Packages.dulwich Package recently updated and maintainer used the wrong source tarball path Used but should be Please run and paste the result. system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: src = fetchFromGitHub { owner = "jelmer"; repo = "dulwich"; <del> rev = "refs/tags/${version}"; </del> <ins> rev = "refs/tags/${pname}-${version}"; </ins> hash = "sha256-bf3ZUMX4afpdTBpFnx0HMyzCNG6V/p4eOl36djxGbtk="; };
Code change:
No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same problem, same message, with the following system. WM: sway
Attempted hacky workaround from This changes error to Progress?

Related discussion:
text: services.portunus.ldap.package = pkgs.openldap.override { libxcrypt = pkgs.libxcrypt-legacy; }; ``` <ins> - The `tracy` package no longer works on X11, since it's moved to Wayland support, which is the intended default behavior by Tracy maintainers. X11 users have to switch to the new package `tracy-x11`. </ins> ## Other Notable Changes {#sec-release-24.11-notable-changes} <!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. -->
Code change:
No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same problem, same message, with the following system. WM: sway
Attempted hacky workaround from This changes error to Progress?

Related discussion:
text: <ins> diff --git a/profiler/build/unix/legacy.mk b/profiler/build/unix/legacy.mk index 24765f1a..8baffb68 100644 --- a/profiler/build/unix/legacy.mk +++ b/profiler/build/unix/legacy.mk @@ -16,7 +16,7 @@ else UNAME := $(shell uname -s) ifeq ($(UNAME),Darwin) SRC3 += ../../../nfd/nfd_cocoa.m -		LIBS +=  -framework CoreFoundation -framework AppKit -framework UniformTypeIdentifiers +		LIBS +=  -framework CoreFoundation -framework AppKit else ifdef TRACY_GTK_FILESELECTOR SRC += ../../../nfd/nfd_gtk.cpp </ins>
Code change:
No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same problem, same message, with the following system. WM: sway
Attempted hacky workaround from This changes error to Progress?

Related discussion:
text: <del> diff --git a/profiler/build/unix/legacy.mk b/profiler/build/unix/legacy.mk index 24765f1a..8baffb68 100644 --- a/profiler/build/unix/legacy.mk +++ b/profiler/build/unix/legacy.mk @@ -16,7 +16,7 @@ else UNAME := $(shell uname -s) ifeq ($(UNAME),Darwin) SRC3 += ../../../nfd/nfd_cocoa.m -		LIBS +=  -framework CoreFoundation -framework AppKit -framework UniformTypeIdentifiers +		LIBS +=  -framework CoreFoundation -framework AppKit else ifdef TRACY_GTK_FILESELECTOR SRC += ../../../nfd/nfd_gtk.cpp </del>
Code change:
No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same problem, same message, with the following system. WM: sway
Attempted hacky workaround from This changes error to Progress?

Related discussion:
text: tracker = callPackage ../development/libraries/tracker { }; <del> tracy = callPackage ../development/tools/tracy { }; </del> <ins> tracy-x11 = callPackage ../by-name/tr/tracy/package.nix { withWayland = false; }; </ins> trivy = callPackage ../tools/admin/trivy { };
Code change:
A clear and concise description of what the bug is. In , XDGSESSIONTYPE is now set to wayland by default for Hyprland users. However, SDDM will crash when this env var is set. Steps to reproduce the behavior: SDDM with Set under . SDDM greet will never show, and the screen will be black. These two lines can be seen in journalctl, and they are not present for boots from older generations. SDDM does not crash. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Did you enable wayland support for SDDM? ()
Thanks, enabling that option fixed the issue! Would be nice if there is an config assertion for this.
Haven't checked the implications but maybe sddm should just enable by default?
enabling wayland for SDDM, makes it impossible for me to start X11 only sessions (eg Pantheon) Is this expected, or is there a way to use SDDM with wayland and X11 sessions?
Same issue here, workaround mentioned in worked for me. I found the following stacktrace in the logs, not sure if/ how this might be helpful.
The proper workaround for now would be to set . Those are envvars that should be set only when the hyprland session starts, not categorically set.
Thanks, this worked for me. I can now start X11 sessions again :)
Same problem here using Hyprland with Budgie as a second desktop. Thanks for solution :+1: works!

Related discussion:
text: xwayland.enable = mkEnableOption ("XWayland") // { default = true; }; <del> envVars.enable = mkEnableOption null // { default = true; example = false; description = '' Set environment variables for Hyprland to work properly. Enabled by default. ''; }; </del> systemd.setPath.enable = mkEnableOption null // { default = true; example = false;
Code change:
A clear and concise description of what the bug is. In , XDGSESSIONTYPE is now set to wayland by default for Hyprland users. However, SDDM will crash when this env var is set. Steps to reproduce the behavior: SDDM with Set under . SDDM greet will never show, and the screen will be black. These two lines can be seen in journalctl, and they are not present for boots from older generations. SDDM does not crash. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Did you enable wayland support for SDDM? ()
Thanks, enabling that option fixed the issue! Would be nice if there is an config assertion for this.
Haven't checked the implications but maybe sddm should just enable by default?
enabling wayland for SDDM, makes it impossible for me to start X11 only sessions (eg Pantheon) Is this expected, or is there a way to use SDDM with wayland and X11 sessions?
Same issue here, workaround mentioned in worked for me. I found the following stacktrace in the logs, not sure if/ how this might be helpful.
The proper workaround for now would be to set . Those are envvars that should be set only when the hyprland session starts, not categorically set.
Thanks, this worked for me. I can now start X11 sessions again :)
Same problem here using Hyprland with Budgie as a second desktop. Thanks for solution :+1: works!

Related discussion:
text: configPackages = mkDefault [ cfg.finalPackage ]; }; <del> environment.sessionVariables = mkIf cfg.envVars.enable { XDG_CURRENT_DESKTOP = "Hyprland"; XDG_SESSION_DESKTOP = "Hyprland"; XDG_SESSION_TYPE = "wayland"; GDK_BACKEND = "wayland,x11"; QT_QPA_PLATFORM = "wayland;xcb"; _JAVA_AWT_WM_NONREPARENTING = "1"; # Fix for Java applications on tiling window managers }; </del> systemd = mkIf cfg.systemd.setPath.enable { user.extraConfig = '' DefaultEnvironment="PATH=$PATH:/run/current-system/sw/bin:/etc/profiles/per-user/%u/bin:/run/wrappers/bin"
Code change:
Package name: LLVM Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 18.1.4 Current version on the stable/release channel: 18.1.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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Want to submit a PR? The last upgrade was very straightforward:
I'll give it a shot

Related discussion:
text: #   rev-version = /* human readable version; i.e. "unstable-2022-26-07" */; #   sha256 = /* checksum for this release, can omit if specifying your own `monorepoSrc` */; # } <del> , officialRelease ? { version = "18.1.4"; sha256 = "sha256-LyQEb4ZJXm2hkPOM9XITIploMT2VKIQWxUFio7SXrc0="; } </del> <ins> , officialRelease ? { version = "18.1.5"; sha256 = "0n44chqn96xsa00ryhwk8g0vv3zx908xjakkgjsa14sjr9mcsq8q"; } </ins> # i.e.: # { #   version = /* i.e. "15.0.0" */;
Code change:
For Intel dGPUs, requires in order to access GPU utilization. Steps to reproduce the behavior: an Intel dGPU, such as the Arc A380 and the following relevant logs: This error should not happen, and should be able to read GPU utilization. ! As you can see, GPU utilization information is not being displayed. N.A. CC Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi It looks like there's an upstream issue tracking this: I'll look into this more to see how we can get this working, but I don't think this is something we can solve directly in the mangohud package. We'll need to use a separate NixOS module for since it'll require a security wrapper to enable . After creating a intel-gpu-tools module that sets the capabilities, I'm pretty sure we'll be able to get it working through something like this: but this would need to be used in addition to installing mangohud. Installing mangohud by itself wouldn't be enough.
Was able to get this working : Before | After ----------|--------- ! | ! Now just need to add this to a new module.

Related discussion:
text: - [Monado](https://monado.freedesktop.org/), an open source XR runtime. Available as [services.monado](#opt-services.monado.enable). <ins> - [intel-gpu-tools](https://drm.pages.freedesktop.org/igt-gpu-tools), tools for development and testing of the Intel DRM driver. Available as [hardware.intel-gpu-tools](#opt-hardware.intel-gpu-tools.enable) </ins> - [Pretix](https://pretix.eu/about/en/), an open source ticketing software for events. Available as [services.pretix](#opt-services.pretix.enable). - [microsocks](https://github.com/rofl0r/microsocks), a tiny, portable SOCKS5 server with very moderate resource usage. Available as [services.microsocks](#opt-services.microsocks.enable).
Code change:
For Intel dGPUs, requires in order to access GPU utilization. Steps to reproduce the behavior: an Intel dGPU, such as the Arc A380 and the following relevant logs: This error should not happen, and should be able to read GPU utilization. ! As you can see, GPU utilization information is not being displayed. N.A. CC Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi It looks like there's an upstream issue tracking this: I'll look into this more to see how we can get this working, but I don't think this is something we can solve directly in the mangohud package. We'll need to use a separate NixOS module for since it'll require a security wrapper to enable . After creating a intel-gpu-tools module that sets the capabilities, I'm pretty sure we'll be able to get it working through something like this: but this would need to be used in addition to installing mangohud. Installing mangohud by itself wouldn't be enough.
Was able to get this working : Before | After ----------|--------- ! | ! Now just need to add this to a new module.

Related discussion:
text: <ins> { config, lib, pkgs, ... }: let cfg = config.hardware.intel-gpu-tools; in { options = { hardware.intel-gpu-tools = { enable = lib.mkEnableOption "a setcap wrapper for intel-gpu-tools"; }; }; config = lib.mkIf cfg.enable { security.wrappers.intel_gpu_top = { owner = "root"; group = "root"; source = "${pkgs.intel-gpu-tools}/bin/intel_gpu_top"; capabilities = "cap_perfmon+ep"; }; }; meta = { maintainers = with lib.maintainers; [ kira-bruneau ]; }; } </ins>
Code change:
For Intel dGPUs, requires in order to access GPU utilization. Steps to reproduce the behavior: an Intel dGPU, such as the Arc A380 and the following relevant logs: This error should not happen, and should be able to read GPU utilization. ! As you can see, GPU utilization information is not being displayed. N.A. CC Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi It looks like there's an upstream issue tracking this: I'll look into this more to see how we can get this working, but I don't think this is something we can solve directly in the mangohud package. We'll need to use a separate NixOS module for since it'll require a security wrapper to enable . After creating a intel-gpu-tools module that sets the capabilities, I'm pretty sure we'll be able to get it working through something like this: but this would need to be used in addition to installing mangohud. Installing mangohud by itself wouldn't be enough.
Was able to get this working : Before | After ----------|--------- ! | ! Now just need to add this to a new module.

Related discussion:
text: ./hardware/video/bumblebee.nix ./hardware/video/capture/mwprocapture.nix ./hardware/video/displaylink.nix <ins> ./hardware/video/intel-gpu-tools.nix </ins> ./hardware/video/nvidia.nix ./hardware/video/switcheroo-control.nix ./hardware/video/uvcvideo/default.nix
Code change:
Steps to reproduce the behavior: blackbox-terminal blackbox uses vte with , this change probably broke it Please run and paste the result. but that's irrelevant as i'm trying to build the latest master. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: rev = "3c8f66be867aca6656e4109ce880b6ea7431b895"; hash = "sha256-vz9ircmPy2Q4fxNnjurkgJtuTSS49rBq/m61p1B43eU="; }; <ins> postPatch = (old.postPatch or "") + '' patchShebangs src/box_drawing_generate.sh ''; </ins> } // lib.optionalAttrs sixelSupport { buildInputs = old.buildInputs ++ [ libsixel ]; mesonFlags = old.mesonFlags ++ [ "-Dsixel=true" ];
Code change:
Steps to reproduce the behavior: blackbox-terminal blackbox uses vte with , this change probably broke it Please run and paste the result. but that's irrelevant as i'm trying to build the latest master. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: , systemd , systemdSupport ? lib.meta.availableOn stdenv.hostPlatform systemd , nixosTests <ins> , blackbox-terminal </ins> }: stdenv.mkDerivation (finalAttrs: {
Code change:
Steps to reproduce the behavior: blackbox-terminal blackbox uses vte with , this change probably broke it Please run and paste the result. but that's irrelevant as i'm trying to build the latest master. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: }; tests = { inherit (nixosTests.terminal-emulators) gnome-terminal lxterminal mlterm roxterm sakura stupidterm terminator termite xfce4-terminal; <ins> blackbox-terminal = blackbox-terminal.override { sixelSupport = true; }; </ins> }; };
Code change:
Project Description An actively maintained picom fork that adds extended animation support. Metadata homepage URL: source URL: license: mit, mpl-2.0 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
One minute, I need to push the right branch
has been done, please react onto the pr so that it is marked as being more important. Have a very nice day
Thanks a lot! Added the reaction to the PR too.
Is this working? I have changed my picom configuration to use this package but none of the new options work.
It should be working, at least it does in my configuration, which includes the package before I ported it to nixpkgs. If you could state what problem you are having, that would be nice. Unfortunately I won't have much of a way to help you because the IC of my Linux laptop is fried, meaning that currently I have no way of being on Linux right now to test anything.

Related discussion:
text: <ins> { picom, lib, fetchFromGitHub, pcre }: picom.overrideAttrs (previousAttrs: { pname = "picom-pijulius"; version = "8.2-unstable-2024-04-30"; src = fetchFromGitHub { owner = "pijulius"; repo = "picom"; rev = "e7b14886ae644aaa657383f7c4f44be7797fd5f6"; hash = "sha256-YQVp5HicO+jbvCYSY+hjDTnXCU6aS3aCvbux6NFcJ/Y="; }; buildInputs = (previousAttrs.buildInputs or [ ]) ++ [ pcre ]; meta = { inherit (previousAttrs.meta) license platforms mainProgram longDescription ; description = "Pijulius's picom fork with extensive animation support"; homepage = "https://github.com/pijulius/picom"; maintainers = with lib.maintainers; [ YvesStraten ]; }; }) </ins>
Code change:
Project description WebUI service for Large Language Models Video demonstration by : .. basically self-hostable ChatGPT-like service Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Additional info Follow-up on for open-webui nixos module. There seems to be an ongoing work on the subject by and on Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Relevant Merge Request:
Just for reference / workaround here's another nix package:
Thanks for that reference. That pdm tool workaround looks a lot more maintainable for the Python backend. Maybe i'll have time to try another PR in the next weeks. In the meantime and as a much simpler UI i packaged as part of PR It would be great if someone could review it.
I would like to mention that in the latest release switched to , I am not sure of any straightforward way to do this while packaging it for .
I just tested your flake, it's impressive, especially the nice UI at the end showing all the processes ! Regarding open-webui, it would be so nice to have that in !!!
Thank you, planning to have more UIs and devShell integration (for CLI tools that interact with ollama). I would love that too! Although there are a few challenges (like the one I pointed above regarding ), I am willing to contribute here. Also, maintainers are quick to respond, in case we need any upstream contributions to make it happen.

Related discussion:
text: ./services/misc/octoprint.nix ./services/misc/ollama.nix ./services/misc/ombi.nix <ins> ./services/misc/open-webui.nix </ins> ./services/misc/osrm.nix ./services/misc/owncast.nix ./services/misc/packagekit.nix
Code change:
Project description WebUI service for Large Language Models Video demonstration by : .. basically self-hostable ChatGPT-like service Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Additional info Follow-up on for open-webui nixos module. There seems to be an ongoing work on the subject by and on Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Relevant Merge Request:
Just for reference / workaround here's another nix package:
Thanks for that reference. That pdm tool workaround looks a lot more maintainable for the Python backend. Maybe i'll have time to try another PR in the next weeks. In the meantime and as a much simpler UI i packaged as part of PR It would be great if someone could review it.
I would like to mention that in the latest release switched to , I am not sure of any straightforward way to do this while packaging it for .
I just tested your flake, it's impressive, especially the nice UI at the end showing all the processes ! Regarding open-webui, it would be so nice to have that in !!!
Thank you, planning to have more UIs and devShell integration (for CLI tools that interact with ollama). I would love that too! Although there are a few challenges (like the one I pointed above regarding ), I am willing to contribute here. Also, maintainers are quick to respond, in case we need any upstream contributions to make it happen.

Related discussion:
text: outline = handleTest ./outline.nix {}; image-contents = handleTest ./image-contents.nix {}; openvscode-server = handleTest ./openvscode-server.nix {}; <ins> open-webui = runTest ./open-webui.nix; </ins> orangefs = handleTest ./orangefs.nix {}; os-prober = handleTestOn ["x86_64-linux"] ./os-prober.nix {}; osquery = handleTestOn ["x86_64-linux"] ./osquery.nix {};