jiebi/CodeConvo huggingface dataset:
Change:
# Disable YAMA by default to allow easy debugging. boot.kernel.sysctl."kernel.yama.ptrace_scope" = mkDefault 0; <ins> # Improve compatibility with applications that allocate # a lot of memory, like modern games boot.kernel.sysctl."vm.max_map_count" = mkDefault 1048576; </ins> }; }

Discussion:
Applications are starting to allocate more times than allowed by the default value of vm.maxmapcount, . For instance, this situation arises in applications such as Ryujinx () and newer Windows games like Hogwarts Legacy (). SteamOS has already addressed this matter by augmenting the aforementioned value, while Fedora intends to implement the same modification in Fedora 39 (, ).
Please feel free to send PRs, it's hard to track those issues as you don't mention any owner.
The line to add is: The questions are: How big should n be? ? ? In which file should I add it? At the bottom of
You mentioned other distros were thinking about bumping it, let's follow Fedora lead In the relevant file, a quick grep shows indeed that sysctl is one of the best candidate. :)
For the policy discussion: I'm all in favor of doing this soon(m). It is not really dangerous and as people have explained to me the previous default has been there for historical reasons and 32 bit systems.
Change:
def assemble_qemu_flags(): flags = "-cpu max" ${if system == "x86_64-linux" <del> then ''flags += " -m 768"'' else ''flags += " -m 512 -enable-kvm -machine virt,gic-version=host"'' </del> <ins> then ''flags += " -m 1024"'' else ''flags += " -m 768 -enable-kvm -machine virt,gic-version=host"'' </ins> } return flags

Discussion:
Describe the bug seems to be failing consistently on master now by timing out. I wasn’t able to figure out where this problem was introduced, since it fails locally for me in the same way even on commits where Hydra has marked it successful. To Reproduce Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
On the other hand I can't reproduce this locally at all. I can see the number of VM cores was increased from 1 to 8 about 2 weeks ago. Could be some kind of race condition?
I've tried two attempts and both kept hanging, probably the same way as on Hydra.
I've tested it 3 times with the latest master and it worked every single time. One thing I noticed though is that I don't see "Passphrase for" (which the test successfully waits for) anywhere in the log. Not in failed hydra logs or successful local runs. So it looks like it's not printing everything to the build log. When I changed the passphrase so it was incorrect, the test hanged just like on Hydra. It should at least show an error message that the passphrase is incorrect. How come we're not getting the complete output log? My best guess is that it failed to unlock the partition for some unknown reason (e.g. maybe the device is not available yet), but it's eating the error message so we have no idea why.
Although the latest Hydra build , a local build on the same commit () still fails. This provides further evidence for the race condition theory, and that we haven’t seen the last of this bug. I’m on a Ryzen 7 1800X (8 cores/16 threads). To test the number-of-cores theory, I tried this patch, and it succeeded:
Could you try adding before and see if that helps?
No, that did not help: <details(hangs forever) </detailsEdit: Of course that doesn’t work, since needs a shell first. But doesn’t work either: <details(hangs forever) </details
I tried to run the test and ran into a different problem: Further investigation shows this Python shell to be severely broken: This seems to be caused by prompt-toolkit/ptpython.
Well that's unfortunate.

Though looking at it looks like it shouldn't be a problem to move those variables into the function itself as they don't seem to be used by any other functions.
I think I found a better workaround for the ptpython problem: .
With , and doing before starting (to work around another bug where the test assumes that is in the current directory), I was able to observe the real error: ! “Not enough available memory to open a keyslot.”
And this succeeds: Opened .
Change:
makeFlags = optionalString stdenv.isDarwin "CFLAGS=-D_FORTIFY_SOURCE=0"; <del> postFixup = ""; # FIXME: remove on next mass rebuild </del> meta = { homepage = http://www.gnu.org/software/coreutils/; description = "The basic file, shell and text manipulation utilities of the GNU operating system";

Discussion:
When trying to copy a file with extended attributes, the attributes don't get copied. When forcing to copy the attributes, it reports: The issue was probably introduced with multiple outputs support. Previously, would find libs&headers while building, propagated through . But now, only the libs propagate and not , so can't find the header and disables support. Not sure if coreutils should just list as a (when is) or if should somehow signal that its output should propagate too. System: Nix version: Nixpkgs version:
By default, the output should be propagated and it should propagate libs and some others in turn. I'll re-check all this later (if noone else is faster).
Hmm, as far as I can tell from the git logs, at least explicitly didn't propagate .
When I tested 16.03 it doesn't have xattr support there either. But anyway, enables it.
I'm pretty sure it used to work at some point, but it might have been a few years ago :) Thanks!
Change:
{ lib , stdenv , fetchurl <del> , electron_28 </del> <ins> , electron </ins> , makeWrapper }:

Discussion:
Steps to reproduce the behavior: mattermost-desktop Electron 28 and has it as an explicit dependency: I patched it in my own fork of nixpkgs to just use instead of hardcoding the version and that seems to work fine. Is there a reason why it is pinned to a specific electron version? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
$DB['PORT'] = '${toString cfg.database.port}'; $DB['DATABASE'] = '${cfg.database.name}'; $DB['USER'] = '${cfg.database.user}'; <del> $DB['PASSWORD'] = ${if cfg.database.passwordFile != null then "file_get_contents('${cfg.database.passwordFile}')" else "''"}; </del> <ins> # NOTE: file_get_contents adds newline at the end of returned string $DB['PASSWORD'] = ${if cfg.database.passwordFile != null then "trim(file_get_contents('${cfg.database.passwordFile}'), "rn")" else "''"}; </ins> // Schema name. Used for IBM DB2 and PostgreSQL. $DB['SCHEMA'] = '''; $ZBX_SERVER = '${cfg.server.address}';

Discussion:
Nix tells ZabbixWeb to use filegetcontents function for retrieving DB password from file. And seems that it adds a newline symbol to a password string so auth failing. [root nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Thanks for reporting this. I'll take a look when I get a chance. If actually you're connecting to localhost (as opposed to using localhost as a simple and reproducible example) I would really suggest using socket authentication which is more secure and doesn't require a password.
Oh... I reviewed the code: You mean that you put a newline in your password file? Just remove the newline in the password file.
Of course not. Newline is by filegetcontents I assume. Why do we need such an obscure way of configuration? Why we can't just add a 'password' option instead of passwordFile?
Your password ends up in the nix store and is readable by any user on the OS. Then you commit your configuration to github and the situation worsens. Unfortunately we must avoid options in NixOS.
I'll whip up a PR.
It's up to end user to decide. I'd use blocks like this for example: Otherwise you'll end up with over engineered costructions with nix functions generating php functions, etc. It's pretty annoying to debug.
I agree, the user should be given a footgun in this scenario. What you're looking for is: I bet it was. I'm sorry this issue exists and you ran into it :disappointed:. PR incoming. Unfortunate (from your perspective, fortunate from other persons perspective) people who commit NixOS module generally agree that adding options is a bad idea. The very first post of includes a number of links if you're interested in hearing the arguments.
Change:
, openssl , libusb1 , AppKit <ins> , git </ins> , openssh <ins> , testers , radicle-cli </ins> }: rustPlatform.buildRustPackage rec {

Discussion:
Steps to reproduce the behavior: . This issue has been reported in , but it was pointed out (by that the package's maintainer ( solved it via starting . However, I still get the above error. Please run and paste the result.
Thanks for the report, fix is in
Change:
sha256 = "144r4py9b8w9ycsg6fggjg05kwvymh003qsb3h6apgpch5y3zgnv"; }; <del> nativeBuildInputs = [ meson ninja pkgconfig libxml2 gettext python3 wrapGAppsHook desktop-file-utils ]; </del> <ins> nativeBuildInputs = [ meson ninja pkgconfig libxml2 gettext python3 wrapGAppsHook desktop-file-utils ]; </ins> buildInputs = [ glib-networking shared-mime-info libexif gtk exempi libnotify libselinux <del> tracker tracker-miners gnome-desktop gexiv2 libseccomp </del> <ins> tracker tracker-miners gexiv2 libseccomp bubblewrap </ins> gnome3.adwaita-icon-theme gnome3.gsettings-desktop-schemas ];

Discussion:
Thumbnails do not get generated for files. Instead, a 1x1 png file gets written to Here's the relevant terminal output: I'm guessing this is caused by and . Open nautilus in a folder containing images. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Fixed in
I think the fix wasn't sufficient on 3.30 :/ I'm able to reproduce on master at least. IIRC I only checked the fix worked with 3.28.
It seems that patch may need to be applied directly to Nautilus too as it now seems to bundle that code? -
Change:
srcs = import ./srcs.nix { inherit fetchurl; inherit mirror; }; patches = { <del> qtbase = [ ./qtbase.patch ] ++ optional stdenv.isDarwin ./qtbase-darwin.patch; </del> <ins> qtbase = [ ./qtbase.patch ] ++ optionals stdenv.isDarwin [ ./qtbase-darwin.patch ./restore-pc-files.patch ]; </ins> qtdeclarative = [ ./qtdeclarative.patch ]; qtscript = [ ./qtscript.patch ]; qtserialport = [ ./qtserialport.patch ];

Discussion:
QT5 for MacOS is not installing the correct files for pkg-config to work: macos: linux: /cc
Change:
pythonPackages.wrapPython wrapGAppsHook ]; <del> buildInputs = [ bluez gtk3 pythonPackages.python libnotify librsvg hicolor-icon-theme ] </del> <ins> buildInputs = [ bluez gtk3 pythonPackages.python librsvg gnome3.adwaita-icon-theme iproute libappindicator ] </ins> ++ pythonPath <del> ++ lib.optional withPulseAudio libpulseaudio; </del> <ins> ++ lib.optional withPulseAudio libpulseaudio ++ lib.optional withNetworkManager networkmanager; </ins> postPatch = lib.optionalString withPulseAudio '' sed -i 's,CDLL(",CDLL("${libpulseaudio.out}/lib/,g' blueman/main/PulseAudioUtils.py ''; <del> pythonPath = with pythonPackages; [ dbus-python pygobject3 pycairo ]; </del> <ins> pythonPath = with pythonPackages; [ pygobject3 pycairo ]; </ins> propagatedUserEnvPkgs = [ obex_data_server ]; <del> configureFlags = [ (lib.enableFeature withPulseAudio "pulseaudio") ]; </del> <ins> configureFlags = [ "--with-systemdsystemunitdir=${placeholder "out"}/lib/systemd/system" "--with-systemduserunitdir=${placeholder "out"}/lib/systemd/user" (lib.enableFeature withPulseAudio "pulseaudio") ]; </ins> postFixup = '' makeWrapperArgs="--prefix PATH ':' ${binPath}"

Discussion:
Blueman package cannot just be used from when installing it from user. It is expected to be an OS level service. See: We should have a NixOS module for it: . Try installing blueman using nix-env and then run .
should work when is enabled. Have you tried it?
When did this happen? I had the same problem as rycee/home-manager
Where does this mention blueman?
Change:
{ lib, stdenv, fetchurl, pkg-config, libsamplerate, libsndfile, fftw <ins> , lv2, jdk </ins> , vamp-plugin-sdk, ladspaH, meson, ninja, darwin }: stdenv.mkDerivation rec { pname = "rubberband"; <del> version = "3.1.0"; </del> <ins> version = "3.3.0"; </ins> src = fetchurl { url = "https://breakfastquay.com/files/releases/${pname}-${version}.tar.bz2"; <del> sha256 = "sha256-uVp22lzbOWZ3DGARXs2Dj4QGESD4hMO/3JBPdZMeyao="; </del> <ins> hash = "sha256-2e+J4rjvn4WxOsPC+uww4grPLJ86nIxFzmN/K8leV2w="; </ins> }; <del> nativeBuildInputs = [ pkg-config meson ninja ]; buildInputs = [ libsamplerate libsndfile fftw vamp-plugin-sdk ladspaH ] ++ lib.optionals stdenv.isDarwin </del> <ins> nativeBuildInputs = [ pkg-config meson ninja jdk ]; buildInputs = [ libsamplerate libsndfile fftw vamp-plugin-sdk ladspaH lv2 ] ++ lib.optionals stdenv.isDarwin </ins> (with darwin.apple_sdk.frameworks; [Accelerate CoreGraphics CoreVideo]); makeFlags = [ "AR:=$(AR)" ]; <ins> # TODO: package boost-test, so we can run the test suite. (Currently it fails # to find libboost_unit_test_framework.a.) mesonFlags = [ "-Dtests=disabled" ]; doCheck = false; </ins> meta = with lib; { description = "High quality software library for audio time-stretching and pitch-shifting"; homepage = "https://breakfastquay.com/rubberband/";

Discussion:
Package name: rubberband Latest released version: 3.3.0 Current version on the unstable channel: 3.1.0 Current version on the stable/release channel: 3.1.0 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Change:
buildPythonPackage rec { pname = "pynndescent"; version = "0.5.11"; <del> format = "setuptools"; </del> <ins> pyproject = true; </ins> disabled = pythonOlder "3.6";

Discussion:
Steps to reproduce the behavior: pythonPackages.pynndescent Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
ExecStart = "${pkgs.sssd}/libexec/sssd/sssd_kcm --uid 0 --gid 0"; }; restartTriggers = [ <del> config.environment.etc."sssd/sssd.conf".source </del> <ins> settingsFileUnsubstituted </ins> ]; }; systemd.sockets.sssd-kcm = {

Discussion:
The SSSD config file location was changed as a result of , but sudo (and possibly other programs, but none I'm aware of) relies on its exact location when the system is configured to get sudo rules from FreeIPA. This happens with nixos 22.11 or newer. Steps to reproduce the behavior: sudo with withSssd set to true the following to to authenticate with sssd over sudo (this might only work if a rule is supplied to sudo via SSSD that contains a netgroup) logs will contain a line that matches but the short hostname will be in the first field in the parenthesis instead of the full hostname sudo should be able to find the ipa_hostname via the SSSD config This is probably best resolved by symlinking to in case there are other programs that rely on reading the sssd config. Also I noticed in the code that there's still a stray in the configuration in that should probably be settingsFileUnsubstituted
partially addresses the issue mentioned here.
Related:
Change:
${cfg.extraHosts} ''; <ins> # /etc/host.conf: resolver configuration file "host.conf".text = cfg.hostConf; </ins> # /etc/resolvconf.conf: Configuration for openresolv. "resolvconf.conf".text = ''

Discussion:
When localhost is mapped to both and in , getaddrinfo(3) still only returns . It should be returning both with ipv6 first. Run the following program as On gentoo, OSX and arch the program returns something like: Whereas on nixos, it returns: System: (NixOS: , Ubuntu/Fedora: , ...) (Gorilla) Nix version: (run ) nix-env (Nix) 1.11.4 Nixpkgs version: (run )
There is also no in nixos.
On Ubuntu 14.04.4 LTS, compiling your code with nix's gcc: The machine has those entries in file. (I compiled with gcc from the latest unstable channel, as your nixpkgs version seems to be unreachable from official branches.)
FWIW neither adding from Arch or stopping (a shot in the dark) fixed this.
The same issue can be demonstrated with . Note that it works in a docker archlinux container on NixOS (using ), which means that the network stack itself is not the problem since the container shares the network stack with the host.
Found the issue: The difference is in the file . On archlinux, this file contains the following line: NixOS doesn't use a non-default , so is set to its default value, which is off. From :
Should be a easy fix then right?
Following other popular distros is probably the way to go, perhaps with a config option to opt out.
Change:
<del> {lib, stdenv, fetchurl, pkg-config}: stdenv.mkDerivation rec { pname = "quvi-scripts"; version="0.9.20131130"; src = fetchurl { url = "mirror://sourceforge/quvi/libquvi-scripts-${version}.tar.xz"; sha256 = "1qvp6z5k1qgcys7vf7jd6fm0g07xixmciwj14ypn1kqhmjgizwhp"; }; nativeBuildInputs = [ pkg-config ]; meta = { description = "Web video downloader"; homepage = "http://quvi.sf.net"; license = lib.licenses.lgpl21Plus; platforms = lib.platforms.linux; maintainers = [ ]; broken = true; # missing glibc-2.34 support, no upstream activity }; } </del>

Discussion:
installs but is unusable. System: Nix version: Nixpkgs version:
I just tried to look at this a bunch and effectively got nowhere fast. Made both the lib and the tool use Lua 5.1 and the 5.1 sockets lib. Oddly in Googling around it there seems to be others elsewhere having issues with this particular combination.
Are there any updates on this issue, please?
While I'm not sure whether this solves this issue in its entirety, two things brought me a bit closer fixing it: Adding to the : Using instead of . In : I don't have any experience with Lua, though, so there might be a better solution. After doing this, I get a very different error which I had not yet the time to investigate (and which is why I didn't open a PR yet):
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 .
This issue persists exactly as originally described. Unfortunately, I did not get around to investigating any further than as described by my last comment.
I marked this as stale due to inactivity. &rarr;
Change:
owner = "karlstav"; repo = "cava"; rev = version; <del> sha256 = "1c5gl8ghmd89f6097rjd2dzrgh1z4i4v9m4vn5wkpnnm68b96yyc"; </del> <ins> sha256 = "01maaq5pfd4a7zilgarwr1nl7jbqyrvir6w7ikchggsckrlk23wr"; </ins> }; nativeBuildInputs = [ autoreconfHook ]; postConfigure = '' <del> substituteInPlace Makefile  </del> <ins> substituteInPlace Makefile.am  </ins> --replace "-L/usr/local/lib -Wl,-rpath /usr/local/lib" "" <ins> substituteInPlace configure.ac  --replace "/usr/share/consolefonts" "$out/share/consolefonts" </ins> ''; meta = with stdenv.lib; {

Discussion:
There have been a few releases since the 0.4.2 release that is currently in nixpkgs. I have tried to update the version number to 0.6.0 and the sha256 to Unfortunately that results in a compilation failure: The cava package comes from github: And is defined by the nix package:
Maybe you can test my PR to see if the application works for you.
Hi, your PR works correctly. Thank you!
Change:
<ins> { lib, python3, fetchFromGitHub }: python3.pkgs.buildPythonApplication rec { pname = "pdfannots"; version = "0.4"; pyproject = true; src = fetchFromGitHub { owner = "0xabu"; repo = "pdfannots"; rev = "v${version}"; hash = "sha256-C0Ss6kZvPx0hHnpBKquEolxeuTfjshhSBSIDXcCKtM8="; }; nativeBuildInputs = [ python3.pkgs.setuptools ]; propagatedBuildInputs = [ python3.pkgs.pdfminer-six ]; pythonImportsCheck = [ "pdfannots" ]; meta = with lib; { description = "Extracts and formats text annotations from a PDF file"; homepage = "https://github.com/0xabu/pdfannots"; license = licenses.mit; maintainers = [ maintainers.marsam ]; mainProgram = "pdfannots"; }; } </ins>

Discussion:
Project description <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Assuming you're referring to ... Homepage: Source: License: MIT Platforms: All supported by Python and PDFMiner
Yes that's right. I just saw that my message was mostly blank. I'm not sure what happened but had included a description as well. Here is the description: A convenient utility for generating markdown files that include the highlighted text and notes saved in PDF files, streamlining the research process.
Change:
# included in `buildInputs` such as libX11. cmakeFlags = [ "-DWITH_EXAMPLES=OFF" ]; <del> # single output, otherwise cmake and .pc files point to the wrong directory # outputs = [ "out" "dev" ]; </del> buildInputs = [ zlib openssl libsodium ]; nativeBuildInputs = [ cmake pkg-config ]; <ins> postFixup = '' substituteInPlace $dev/lib/cmake/libssh/libssh-config.cmake  --replace-fail "set(_IMPORT_PREFIX "$out")" "set(_IMPORT_PREFIX "$dev")" ''; </ins> passthru.tests = { inherit ffmpeg sshping wireshark; };

Discussion:
Package name: libssh Latest released version: 0.11.1 <!-- Search your package here: --- Current version on the unstable channel: 0.10.6 Current version on the stable/release channel: 0.10.6 <!-- 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 Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
# Tools to create / manipulate filesystems. pkgs.ntfsprogs # for resizing NTFS partitions pkgs.dosfstools <ins> pkgs.mtools </ins> pkgs.xfsprogs.bin pkgs.jfsutils pkgs.f2fs-tools

Discussion:
Describe the bug GParted in the installation ISO images cannot create, resize, move and do other operations on many filesystems such as FAT32. This problem is due to absence of related (optional) run-time dependencies such as and (in the case of FAT32). in live session doesn't solve the problem. The supports to filesystems other than ext4 is important especially when you need to operate on the EFI System Partition (ESP), NTFS for Windows, HFS for Mac, and BTRFS used by some other Linux distributions. Possible solution includes: all the run-time dependencies required for GParted to operate on those filesystems in the list in . a new package, , and show it in . Replace with 'gparted-full' in list in . To Reproduce Steps to reproduce the behavior: Go to and download the 64bit Plasma Desktop ISO image, which is the image after burning it to a USB stick or attaching to a virtual machine. sure that there is a FAT32 partition on your machine. Most computers have EFI System Partition, which is usually FAT32. If there isn't any, an USB stick with a FAT32 partition can be attachede GParted and right-click on the FAT32 partition, it can be noticed that some options including are grayed out. -click on an un-allocated space, click , and it can be seen that many options including FAT32 have been grayed out. Expected behavior GParted on the ISO installation image can operate on all or most of the supported file systems. Screenshots If applicable, add screenshots to help explain your problem. Additional context Filesystems supported by GParted: 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 had the same issue now.
Related