jiebi/CodeConvo huggingface dataset:
Change:
}; <ins> discord-screenaudio = qt6.callPackage ../applications/networking/instant-messengers/discord-screenaudio { }; </ins> discordo = callPackage ../applications/networking/discordo/default.nix { }; golden-cheetah = libsForQt5.callPackage ../applications/misc/golden-cheetah { };

Discussion:
I found this bug while trying to create a package for (mentioned in ), but it seems all qtwebengine-based browsers like Qutebrowser and Falkon have the same issue. These browsers are able to pick up my microphone just fine, but any virtual devices created via pipewire do not show up. discord-screenaudio creates a virtual source to pipe desktop audio through, which then is meant to be detected as an audio input inside a qtwebengine window linked to Creating virtual devices manually via (following ) also doesn't work, as they do not show up in Qutebrowser or Falkon. They do show up in Firefox, Chromium, and the native Discord client, however. pipewire running as the audio server a virtual audio device using to on Falkon or Qutebrowser and see that does not show up in the input list. does show up in Falkon or Qutebrowser One final difference I see is within the Helvum program, where I can see how audio devices are connected. When Firefox, Chromium and Discord use my microphone a connection is made in Helvum, but when Qutebrowser, Falkon, or discord-screenaudio do no connection is visible. To me it seems that qtwebengine-based browsers must not be connecting to pipewire or pipewire-pulse at all, but talking to the audio devices directly somehow. (qtwebengine) Please run and paste the result.
I'm unsure if I should also mention the maintainers of Falkon and Qutebrowser here since it seems the issue lies with qtwebengine
You should, I think it's safe to say qtwebengine is pretty much maintained for qutebrowser alone. I don't use pipewire/pulse but I think does.
Alright then: falkon's maintainer is other qutebrowser maintainers that have not been mentioned yet are
I do use pipewire, but not virtual audio devices. Have you ensured that you have xdg-desktop-portal-wlr setup correctly? I have to run this sequence of commands in order to get screensharing to work, for example: Where is set to Of course, if you are not using wayland then you'd want instead of
Weird. I'm on X11, not wayland.

I both wireplumber and xdg-desktop-portal via the nixos configuration options and it still doesn't make a difference, even when running those commands before running these browsers
Is xdg-desktop-portal required for pipewire audio support in qtwebengine?
I don't think so since the mic was working even when video capture is not (and the later does requre it). However there appears to have been a regression recently, I just bumped my pin just yesterday and now my mic is not working at all in qutebrowser.
Can you paste the code for creating the package you have so far?
This still seems like an issue, see further attempts at packaging discord-screenaudio in .
The issue has indeed been fixed!

Project description A custom discord client that supports streaming with audio on Linux Metadata homepage/source URL: license: GPL-3.0 platforms: linux
Change:
libtoggl qxtglobalshortcut qtbase <del> qtwebkit </del> <ins> qtwebengine </ins> qt-oauth-lib qtx11extras libX11

Discussion:
fails to build. The build error is in an internal dependency, . The nix derivation uses the upstream version from Github but Toggl is actually using a vendored internal version that has a number of fixes in it. The build error is due to using the discontinued library. Toggl's internal version uses . This problem has been noted in .
cc
Fixed in (tagged ). See for Nixpkgs PR.
Change:
, stdenv , fetchFromGitHub , fetchpatch <ins> , pkg-config # needed to find minizip </ins> , SDL2 , SDL2_image , SDL2_mixer , SDL2_net , SDL2_ttf <del> , boost </del> , cmake , curl , doxygen

Discussion:
name: widelands current version: 1.0 desired version: 1.1 maintainers: The widelands devs sent us an email about the release. I think this is a first for me.
I'm working on a PR for this (and once I figure out the github UI, I'll assign it to myself)..
Closing since fixes this. Please reopen if I'm wrong.
Change:
, shared-mime-info , wrapGAppsHook4 , meson <del> , gjs </del> , gtk4 , gst_all_1 , libGL , libadwaita <del> , appstream-glib , libsoup </del> <ins> , libsoup_3 , vala , cmake , libmicrodns </ins> }: <del> stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "clapper"; <del> version = "0.5.2"; </del> <ins> version = "0.6.0"; </ins> src = fetchFromGitHub { owner  = "Rafostar"; <del> repo   = pname; rev    = version; sha256 = "sha256-s+qdTq3/pHHstwr1W3Hs2Zje++iJFHM6hQTFoZD43bY="; </del> <ins> repo   = "clapper"; rev    = finalAttrs.version; hash = "sha256-5fD1OnVcY3ZC+QfoFqe2jV43/J36r85SpLUYF2ti7dY="; </ins> }; nativeBuildInputs = [ <del> appstream-glib desktop-file-utils # for update-desktop-database glib </del> gobject-introspection meson <ins> cmake </ins> ninja makeWrapper pkg-config <del> python3 shared-mime-info # for update-mime-database </del> wrapGAppsHook4 # for gsettings <ins> desktop-file-utils # for update-desktop-database shared-mime-info # for update-mime-database vala </ins> ]; buildInputs = [ <del> gjs </del> gst_all_1.gstreamer gst_all_1.gst-plugins-base gst_all_1.gst-plugins-good

Discussion:
Package name: clapper Latest released version: 0.6.0 Current version on the unstable channel: 0.5.2 Current version on the stable/release channel: 0.5.2 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
./services/misc/logkeys.nix ./services/misc/leaps.nix ./services/misc/lidarr.nix <ins> ./services/misc/libreddit.nix </ins> ./services/misc/lifecycled.nix ./services/misc/mame.nix ./services/misc/matrix-appservice-discord.nix

Discussion:
Project description 10 second pitch: Libreddit is a portmanteau of "libre" (meaning freedom) and "Reddit". It is a private front-end like Invidious but for Reddit. Browse the coldest takes of r/unpopularopinion without being tracked. Demo: Metadata homepage URL: source URL: license: agpl3 platforms: unix, linux, darwin, ...
could you please give a try? Thanks
That's just the package, but not a service (like ) right?
Yes, it's only the package for the moment.
There seems to be a bug present in the latest release. I opened a feature request () which could improve the service. Sorry, it will take some time till we can finish this.
Change:
${if c.dbhost != null then "--database-host" else null} = ''"${c.dbhost}"''; ${if c.dbport != null then "--database-port" else null} = ''"${toString c.dbport}"''; ${if c.dbuser != null then "--database-user" else null} = ''"${c.dbuser}"''; <del> "--database-pass" = "$${dbpass.arg}"; </del> <ins> "--database-pass" = ""$${dbpass.arg}""; </ins> "--admin-user" = ''"${c.adminuser}"''; <del> "--admin-pass" = "$${adminpass.arg}"; </del> <ins> "--admin-pass" = ""$${adminpass.arg}""; </ins> "--data-dir" = ''"${datadir}/data"''; }); in ''

Discussion:
If the admin password stored in contains spaces, the generated script won't escape them when passing them to : Steps to reproduce the behavior: to a file containing spaces. existing Nextcloud configuration (e.g., ) and rebuild with . that the rebuild fails due to . The rebuild succeeded. Please run and paste the result.
Change:
<del> { lib, stdenv, fetchurl, buildInputs, sha512, version, libelf, url }: </del> <ins> { lib, stdenv, fetchurl, buildInputs, sha512, version, libelf, url, knownVulnerabilities }: </ins> stdenv.mkDerivation rec { pname = "libdwarf";

Discussion:
The following security vulnerability in libdwarf has been published. We have two vulnerable versions: 0.4.0 The patch we need to apply is: Maintainer: Please reference the CVE id with in the commit message.
PTAL.
We cannot easily apply the patch provided by the upstream to the default version because the code base directory layout changes
Could you take a look at , please?
, I wonder how you noticed this vulnerability. Is there certain vulnerability workflow that ensures that every CVE in any package would be addressed or at least marked as .
I tried to find out how I first heard of this vulnerability, but I can't find the source anymore. It was neither an email nor on IRC. We have a coordination channel for security issue triage on Matrix. It's .
Thank you for the information.
Change:
"test_multi_outpath" "test_mmhint" "test_otf" <ins> # flaky tests (see https://github.com/adobe-type-tools/psautohint/issues/385) "test_hashmap_old_version" "test_hashmap_no_version" </ins> ]; passthru.tests = {

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: Updated my (flake based on ). Expected packages to build properly. 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.
Cannot reproduce on current master (). Seems like the test has been fixed since.
Yeah, I agree. I updated my and I can no longer reproduce after .
This seems to be a flaky test, as it's triggering again for me on nixos-unstable dispite nothing seeming to have been updated since 2022 about the package according to a pr search /cc
Checked the history of the package, and the most recent update was Jan 26th of this year to do a tree-wide change. Nothing since, which makes me think it's definately a flaky test, might be worth disabling it
Can you give more details? On that nixpkgs revision psautohint builds and is in cache.
It's not cached for some reason on my machines, when pulled in via noto-fonts-emoji from I'm not touching any of it's dependencies I don't think so I'm not sure why it would be rebuilding?
Please provide a minimal reproducer for the issue – I won't dig through that massive repo trying to figure out what interactions of what parts may or may not cause an issue. You haven't even mentioned what platform this happens on (I assumed x86_64-linux same as the original issue for now). For what it's worth in the last week no platform has exhibited a build failure for psautohint in nixpkgs, so you can just try updating your channel.
I filed a PR () to just disable that test, and now another, as it seems to be intermittently failing. It appears in their issue tracker, so I see no reason we shouldn't just disable it so that it can build always in nixos.
Change:
libstartup_notification = "${libstartup_notification}/lib/libstartup-notification-1.so"; }) ] ++ stdenv.lib.optionals stdenv.isDarwin [ <ins> (fetchpatch { name = "macos-symlink-1"; url = https://github.com/kovidgoyal/kitty/commit/bdeec612667f6976109247fe1750b10dda9c24c0.patch; sha256 = "1d18x260w059qag80kgb2cgi2h4rricvqhwpbrw79s8yxzs7jhxk"; }) (fetchpatch { # fixup of previous patch name = "macos-symlink-2"; url = https://github.com/kovidgoyal/kitty/commit/af2c9a49b1ad31e94242295d88598591623fbf11.patch; sha256 = "0k3dmgbvmh66j8k3h8dw6la6ma6f20fng6jjypy982kxvracsnl5"; }) </ins> ./macos-10.11.patch ./no-lto.patch ./no-werror.patch

Discussion:
Due to MacOS oddities does not work when executed as symlink() and hence, the wrapper installed via cannot work on MacOS. In fact, is unusable on MacOS whatever the content is. Any idea what could be done about this? Should we remove the directory altogether from the build output to prevent confusion?
I think the best thing to do here is just remove the symlink and use
If you wish to use a symlink, use one that points to kitty-deref-symlink
Change:
makeWrapper $out/lib/slack/slack $out/bin/slack  --prefix XDG_DATA_DIRS : $GSETTINGS_SCHEMAS_PATH  --suffix PATH : ${lib.makeBinPath [xdg-utils]}  <del> --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}" </del> <ins> --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}"  --add-flags "''${WAYLAND_DISPLAY:+--enable-features=WebRTCPipeWireCapturer}" </ins> # Fix the desktop link substituteInPlace $out/share/applications/slack.desktop 

Discussion:
crashes with option activated Steps to reproduce the behavior: slack with option a call screensharing and select a desktop crashes with Screensharing starts. Log output Even if Slack is started with this command it crashes.
I just tested it again with the following command and what should I write... it now works as expected and is stable :tada: overlay to make it more convenient.
I've came across the issue yesterday and made a PR for it, also I can't reproduce the problem issue of this issue anymore so when merged I would like to going forward, closing this? :)
Change:
sha256 = "11ixlqmvbb37abksdysg5r4lkbwzr486lkc0ssl3wca4iiy3mhgf"; }; <ins> nativeBuildInputs = [ removeReferencesTo ]; </ins> buildInputs = [ icu zlib gmp perl ]; configureScript = "perl ./Configure.pl"; configureFlags = [

Discussion:
Describe the bug Rakudo depends on gcc unwrapped noticeably increasing closure size To Reproduce Steps to reproduce the behavior: rakudo Expected behavior Rakudo shouldn't depend on gcc. However, currently it does depend on gcc which causes closure bloat. Additional context Add any other context about the problem here. 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 Please run and paste the result. Maintainer information:
I marked this as stale due to inactivity. &rarr;
Change:
buildRustPackage rec { name = "exa-${version}"; <del> version = "2016-02-15"; </del> <ins> version = "2016-03-22"; </ins> <del> depsSha256 = "1925nhpfph82wn755zf2nmad24f1hzbxq60gpva9sic6rnap4c1x"; </del> <ins> depsSha256 = "18anwh235kzziq6z7md8f3rl2xl4l9d4ivsqw9grkb7yivd5j0jk"; </ins> src = fetchFromGitHub { owner = "ogham"; repo = "exa"; <del> rev = "252eba484476369bb966fb1af7f739732b968fc0"; sha256 = "1smyy32z44zgmhyhlbjaxcgfnlbcwz7am9225yppqfdsiqqgdybf"; </del> <ins> rev = "8805ce9e3bcd4b56f8811a686dd56c47202cdbab"; sha256 = "0dkvk0rsf068as6zcd01p7959rdjzm26mlkpid6z0j168gp4kh4q"; </ins> }; nativeBuildInputs = [ cmake ];

Discussion:
To make sure that we are on the same page: Kernel: (run ) 4.5.0 System: (NixOS: , Ubuntu/Fedora: , ...) (Flounder) Nix version: (run ) 1.11.2 Nixpkgs version: (run ) During testing of I managed to get at least two different hashes for . After some discussion with it seems that this derivation can produce non-deterministic output. Hashes of outputs are always the same. They are not. Build several times.
How would one work around that? It basically means the system cannot be rebuild :cry:
cc
You can work around it by updating SHA checksum in the affected package locally.
:confused: Is there any documentation you could point me too. I know how I would to it for packages that I install as a user: out nixpkgs repo the last commit that build for unstable on hydra that out the exa's file 5 run But I think it's also possible to override it in a nix expression, like the one in , since I installed it as a systems package. The thing is that all ressources I find either explain how to do it for that they link to
I changed my to include that: but to no avail :confused:
Sadly we don't have a mechanism to override (it needs to be supported). However, you can rebuild your whole NixOS from a modified repository:
Another way to do it is to call patched nixpkgs from your :
Thanks for your help! I really appreciate it. I tried your last suggestions, but that leads to: It looks like some network hick up, but I tried it multiple times and I opened the github repository from the same machine and it loads fine. Maybe it has something to do with this line: ?
Hm, unfortunately I have no idea what's going on -- you've fixed the hash, so it seems like another problem in .
Still thanks for the help. I learned a lot!
depends on a git repository in which doesn't work with
maybe fetchcargo could take an argument to pin git-based dependencies on a certain commit?
I can confirm that this is still an issue when building : through AUR/exa-git. cc
Are there any updates on this issue, please?
Should be fixed.
Change:
githubId = 2472678; name = "Lucas Desgouilles"; }; <ins> ldprg = { email = "lukas_4dr@gmx.at"; matrix = "@ldprg:matrix.org"; github = "LDprg"; githubId = 71488985; name = "LDprg"; }; </ins> league = { email = "league@contrapunctus.net"; github = "league";

Discussion:
Project description Runs as a daemon and records statistics about usage of programs using Markov chains; files of more frequently-used programs are, during a computer's spare time, loaded into memory. Metadata homepage URL: source URL: license: gpl2 platforms: linux
Same here! Preload can really help out when using Linux on older hardware or when using programs that generally take long to start.
Change:
kernelPatches = [ kernelPatches.bridge_stp_helper kernelPatches.request_key_helper <del> kernelPatches.dell_xps_regression </del> ]; };

Discussion:
/dev/nvme0 becomes unavailable and causes / to unmount leading to an unresponsive system. <details<summarySmartctl output</summary</detailsNVMe + 6.5 kernel (either on main branch, staging-next branch, or staging-next + gnome branch) Not like this UnU <details<summaryError messages before rebooting</summary! ! </detailsRelated to Related to Related to Related to Related to <!-- 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. hw-probe: https://linux-
Already reported on NixOS discourse:
It's annoying to capture but finally managed to get more info ! !
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Should we revert the patch mentioned here or wait for a new upstream kernel release?
Seems like 6.5.6-rc1 fixed the issue for me, still doing some testing. Besides the revert already on nixos there are 2 commits regarding nvme: a null pointer dereference, and something around no NUMA nodes and NVMe
nvm still crashing
Hey they fixed this one already. I believe y'all have a different bug. What machine is this on?
hw-probe: https://linux- 6 does seem like it did fix it.
Ok yes it's definitely a different bug (no realtek devices, no possible way it could be my bug). But I'm glad it's fixed I guess.
Still happens to me on 6.5.6. ! Symptoms are the same as reported by root filesystem is remounted as read-only, applications crash and system becomes unresponsive. PC must be forcefully shut down with the power button. This happens at least daily, and almost always while I'm away from the PC for a while, which makes the message "Does your device have a faulty power saving mode enabled?" sound like it's probably onto something. <details<summary<code$ nix-shell -p smartmontools --run "sudo smartctl -a /dev/nvme0"</code</summary</details
which machine is this?

I expect it's a firmware bug in the motherboard most likely.
My motherboard is: . I tried booting with the kernel parameters suggested in the error log now, hopefully that does something.
If you are using LUKS something that helped me reduce the frequency of errors (mitigation) was enabling triming (fstrim) in NixOS options Also, it seems like a relative new drive but has a very high warning temperature time; errors might be thermal related.
I don't use LUKS. The temperature warnings must be old, because I haven't caught the SSD go above 36 celsius in the current PC location, so I don't think the errors are temperature related. I let the PC sit over night with the suggested kernel parameters, and it hasn't crashed yet :crossed_fingers:
Change:
else matchAttrs patterns; predicates = mapAttrs (_: matchAnyAttrs) patterns; <ins> # these patterns are to be matched against the entire # {host,build,target}Platform structure; they include a `parsed={}` marker so # that `lib.meta.availableOn` can distinguish them from the patterns which # apply only to the `parsed` field. platformPatterns = mapAttrs (_: p: { parsed = {}; } // p) { isStatic = { isStatic = true; }; }; </ins> }

Discussion:
I am working on this bug. First reported . The root cause of the problem is that there is no "pattern" (see ) representation for . It is special, unlike all the other platform predicates. It is this way because exists, and because ... in other words, "static-ness" is not represented in the triple for a platform. Right now we try to pretend that you can reconstruct all the pattern-representable aspects of a from its . That isn't really true, because of and , and it's getting more untrue as time goes on. The long-term solution is to stop pretending. I have a possible short-term fix that I'm testing.
Change:
in stdenv.mkDerivation rec { name = "gitkraken-${version}"; <del> version = "4.0.2"; </del> <ins> version = "4.0.5"; </ins> src = fetchurl { <del> url = "https://release.gitkraken.com/linux/v${version}.deb"; sha256 = "0dnckd75fcgc9wa4ivbnw2djmk4phzzr891snhxpsvb1dhlc7rgx"; </del> <ins> url = "https://release.axocdn.com/linux/GitKraken-v${version}.deb"; sha256 = "15wxcahlnz2k3331wqv30d5gq38fqh178hv87xky9b9vyh8qpcvz"; </ins> }; libPath = makeLibraryPath [

Discussion:
The .nix for Gitkraken specifies a like , which now seems to give me a 404. Their links to files like fwiw, but I'm not yet sure where the pinned versions might not be hosted... install gitkraken using nixpkgs
New version and moved url, the correct url seems to be
Change:
lrzsz = callPackage ../tools/misc/lrzsz { }; <del> lsp-plugins = callPackage ../applications/audio/lsp-plugins { php = php81; }; </del> <ins> lsp-plugins = callPackage ../applications/audio/lsp-plugins { php = php82; }; </ins> ltex-ls = callPackage ../tools/text/ltex-ls { };

Discussion:
Steps to reproduce the behavior: nixpkgs to home manager (assume installation method is irrelevant) None. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Maybe this is related to
Can you post the error logs please?
A gist of the build log is linked in the template, are there other logs you need?
Yes, I didn't see it while replying with the phone. Thank you.
Change:
''; postFixup = let <del> path = "PATH=${makeBinPath [ coreutils gawk gnused gnugrep util-linux smartmontools sysstat ]}:$PATH"; </del> <ins> path = "PATH=${makeBinPath [ coreutils gawk gnused gnugrep util-linux smartmon sysstat ]}:$PATH"; </ins> in '' for i in $out/libexec/zfs/zpool.d/*; do sed -i '2i${path}' $i

Discussion:
Describe the bug On a ZFS-enabled 20.03 system: IMHO zed does not need the ability to send email by default. Also mariadb-connector should have a separate -dev output so that its doesn't end up in the system closure.
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 .
Seems still important: And: And:
Adjusted to milestone 21.03. BTW, If someone wants to backport the fix it shouldn't cause any issues.
Took a stab at this in