jiebi/CodeConvo huggingface dataset:
Change:
serviceConfig = { Type = "oneshot"; Restart = "no"; <del> # `core` and `cache` are both intentionally set to `cfg.coreOffset` as according to the undervolt docs: # #     Core or Cache offsets have no effect. It is not possible to set different offsets for #     CPU Core and Cache. The CPU will take the smaller of the two offsets, and apply that to #     both CPU and Cache. A warning message will be displayed if you attempt to set different offsets. ExecStart = '' ${pkgs.undervolt}/bin/undervolt  ${optionalString cfg.verbose "--verbose"}  ${optionalString (cfg.coreOffset != null) "--core ${cfg.coreOffset}"}  ${optionalString (cfg.coreOffset != null) "--cache ${cfg.coreOffset}"}  ${optionalString (cfg.gpuOffset != null) "--gpu ${cfg.gpuOffset}"}  ${optionalString (cfg.uncoreOffset != null) "--uncore ${cfg.uncoreOffset}"}  ${optionalString (cfg.analogioOffset != null) "--analogio ${cfg.analogioOffset}"}  ${optionalString (cfg.temp != null) "--temp ${cfg.temp}"}  ${optionalString (cfg.tempAc != null) "--temp-ac ${cfg.tempAc}"}  ${optionalString (cfg.tempBat != null) "--temp-bat ${cfg.tempBat}"} ''; </del> <ins> ExecStart = "${pkgs.undervolt}/bin/undervolt ${cliArgs}"; </ins> }; };

Discussion:
Describe the bug The undervolt module is potentially damaging to hardware when misconfigured. The module description needs an appropriate warning informing users that they are taking a risk when enabling it (even though I think it's fairly obvious that's the case). Maintainer information: cc
It would also be nice if the options' description specified what units are expected for the "amount of voltage". And I don't know how feasible it is but if the options accept a floating point number as per their documenation they should perhaps be of a numeric type as well.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
Still relevant.
Change:
<ins> { borgbackup, coreutils, lib, python3Packages, systemd }: python3Packages.buildPythonApplication rec { pname = "borgmatic"; version = "1.5.12"; src = python3Packages.fetchPypi { inherit pname version; sha256 = "sha256-XLbBJvNRmH8W9SnOjF7zUbazRYFCMW6SEO2wKN/2VTY="; }; checkInputs = with python3Packages; [ flexmock pytestCheckHook pytest-cov ]; # - test_borgmatic_version_matches_news_version # The file NEWS not available on the pypi source, and this test is useless # - test_collect_configuration_run_summary_logs_outputs_merged_json_results # Upstream fixed in the next version, see # https://github.com/witten/borgmatic/commit/ea6cd53067435365a96786b006aec391714501c4 disabledTests = [ "test_borgmatic_version_matches_news_version" "test_collect_configuration_run_summary_logs_outputs_merged_json_results" ]; propagatedBuildInputs = with python3Packages; [ borgbackup colorama pykwalify ruamel_yaml requests setuptools ]; postInstall = '' mkdir -p $out/lib/systemd/system cp sample/systemd/borgmatic.timer $out/lib/systemd/system/ substitute sample/systemd/borgmatic.service  $out/lib/systemd/system/borgmatic.service  --replace /root/.local/bin/borgmatic $out/bin/borgmatic  --replace systemd-inhibit ${systemd}/bin/systemd-inhibit  --replace sleep ${coreutils}/bin/sleep ''; meta = with lib; { description = "Simple, configuration-driven backup software for servers and workstations"; homepage = "https://torsion.org/borgmatic/"; license = licenses.gpl3Plus; platforms = platforms.linux; maintainers = with maintainers; [ imlonghao ]; }; } </ins>

Discussion:
borgmatic is simple, configuration-driven backup software for servers and workstations. Protect your files with client-side encryption. Backup your databases too. Monitor it all with integrated third-party services. Homepage: Source: License: GPL v3 () Platforms: UNIX, Linux, Darwin (I guess anywhere Python is supported)
I marked this as stale due to inactivity. &rarr;
Up!
Change:
''; }; <ins> networking.hostConf = lib.mkOption { type = types.lines; default = "multi on"; example = '' multi on reorder on trim lan ''; description = '' The contents of <filename>/etc/host.conf</filename>. See also <citerefentry><refentrytitle>host.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>. ''; }; </ins> networking.dnsSingleRequest = lib.mkOption { type = types.bool; default = false;

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:
name = "${pname}-${version}"; url = "http://language.moe.gov.tw/001/Upload/Files/site_content/M0001/MoeLI-3.0.zip"; <del> sha256 = "0vpmm2qb429npng0aqkafwgs7cjibq8a3f7bbn9hysbm2lndwxwd"; </del> <ins> sha256 = "0b4kjdk0h0hx446swi0wzawia0mf16qh9b6v4h4nqg8qx0p2sd3c"; </ins> }; installPhase = ''

Discussion:
Hydra fails to fetch when ran on darwin, blocks even linux builds as is a fixed-output derivation: (linux failure: ) I think it's the following suspicious UTF-8 path: darwin and linux should both be able to fetch the same tarball.
The issue with fetching the tarball on macOS was discovered in , and we believe this is a fetchzip bug on macOS. However, until now, it wasn't an actual issue for users because macOS users would use the fixed-output derivation downloaded on Linux and cached by Hydras (see ). Now, it seems like Hydras caches failures as well (it's a new thing, isn't it? Or we were just lucky previously that the Linux fetching would have happened before the macOS one?) and that because of this, a failure to download the source on Darwin is affecting everyone! I don't really have any solution to propose except: as a workaround is it possible to remove the cached failure and retrigger the build on Linux? fetchzip needs to be fixed to handle UTF-8 file names properly. Even if Coq was modified to not include these file names in its source archive anymore, this wouldn't resolve the issue with already released versions. One last workaround idea to the fetchzip issue would be to make the fixed-output derivation not the direct result of fetching the tarball, but something that would fetch it and fix the divergent paths (e.g., by removing the corresponding tests). But I wouldn't even know how to implement this.
I've seen this in a couple other packages already. It's... not nice but fortunately not a very common problem (perhaps partly due to some linux getting it faster or on a retry).
Do you think works correctly on linux? I find -translation as very odd. Is it broken too?
Unpacking is locale-dependent: LANG=C -(bad) LANG=C.UTF-8 -(ok)
My guess the mismatch happens because macos supports UTF-8 locales as is (and mossibly musl as well?). While does not unless is pulled into unzip. I think we have 2 routes: make work on linux (and break a bunch of fixed-output derivations that contain UTF-8), should be a matter of pulling into 's hook (did not test yet). make ASCII-only everywhere by using in 's . It will start consistently mangle non-ASCII for everyone.

Confirmed failure on as well:
WDYT of proposed fix? Once it's in we can fix and friends.
Thanks a lot for digging into and figuring out the cause of this issue! I find your proposed fix as the best (most principled) solution, even if it will require some work to fix past fix-output derivations.
Change:
import ./make-test-python.nix ({ lib, pkgs, ... }: let testId = "7CFNTQM-IMTJBHJ-3UWRDIU-ZGQJFR6-VCXZ3NB-XUH3KZO-N52ITXR-LAIYUAU"; <del> testName = "testDevice foo'bar"; </del> in { name = "syncthing-init";

Discussion:
if a folder is a substring of another folder, we don't delete it even if we have overrideFolders and the substring id got removed from the config. Steps to reproduce the behavior: a folder with id "xxx" a folder with id "yyyzzzxxx"; folder with id "xxx" from config never gets removed folder "xxx" should have been removed after removing it from config <!-- 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.
Thanks for spotting the issue and reporting :) It sounds to me like a issue not being accurate... Maybe only the 1st commit in does the job?
yes, the first commit solves the issue with substring ids. the second commit solves the issue with ids like "hello/world". I tried escaping the id to send a DELETE request but couldn't find out how to correctly escape the / in the id
I'd never imagine someone would do that LOL. What if we'd impose a check in the module that would prevent such ids? Is it even supported upstream?
well it works in the webinterface. so it seems supported? also the default value for the id in our nixos module is the key, which also is the path. I usually do something like so all those ids are broken. as a workaround we could replace all / in the id, but that would break interaction with non nixos setups. PUTing the config seems to not have that issue. Were there any problems with PUTing the config if we want to override folders and devices anyway?
Could you perhaps give more context? I don't understand what kind of a json object is passed to the commands when you do that. I also observed in the below code that "/" are taken care of in a special way? As I in , I don't like how the code diverges in the , and it seems to me it doesn't handle the case where you want to delete a stale folder, and you don't .
yeah the PR sadly isn't complete, I just used it as a test for my local systems where I just override everything. I guess we need to handle individual overrides better, but not sure how. setting wold result in a nixos configuration of when I initially wrote this module this seemed unique enough and like a sane default.

I thought about hashing the key for the id, but this would have ended in unnecessary long keys.
I see. I think that using such IDs for folders and devices is very uniqe usage... I tend towards suggesting to take the 1st commit of the PR, and a message when evaluating the script, in case the folders' IDs contain "/", and is true. However, that would not solve your particular, usage. Perhaps we can talk with upstream about it? They are rather responsive from my experience.
that sounds like an idea. I'm busy the next couple of days, but you can cherry pick the first commit from my PR and close it and we will continue with this once we have some better idea how to handle things and we maybe have an answer from upstream?
Change:
"NEWS" ]; }) <ins> ] ++ lib.optionals (lib.versions.majorMinor php.version == "8.1") [ # Backport of PHP_LIBXML_IGNORE_DEPRECATIONS_START and PHP_LIBXML_IGNORE_DEPRECATIONS_END ../development/interpreters/php/php81-fix-libxml2-2.13-compatibility.patch # Fix build with libxml2 2.13+. Has to be applied after libxml2 2.12 patch. (fetchpatch { url = "https://github.com/php/php-src/commit/9b4f6b09d58a4e54ee60443bf9a8b166852c03e0.patch"; hash = "sha256-YC3I0BQi3o3+VmRu/UqpqPpaSC+ekPqzbORTHftbPvY="; }) </ins> ] ++ lib.optionals (lib.versions.majorMinor php.version == "8.2" && lib.versionOlder php.version "8.2.22") [ # Fixes compatibility with libxml2 2.13. Part of 8.3.10RC1+, 8.2.22RC1+ (fetchpatch {

Discussion:
Steps to reproduce the behavior: php-simplexml-8.1.2 This happen after latest flake update Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hydra build : and seem fine: Probably related: (fixes for 8.2 and 8.3 with same error) 1 is out of active support, so there was no backport for from upstream PS you did not ping any maintainers for that package, so they would need to notice this issue (which is unlikely)
Also causes an lsp-plugins build failure. Gonna ping maintainers.
this is fixed in master
forgive my ignorance, but what needs to happen for the fix on master to make its way to the unstable channel? I would love to be able to rebuild my system soon
fixed "lsp-plugins build failure" (it does not depend on php 8.1 version now) If your system update depends on in some other way it won't help. does not build on current master as of (2024-07-30T19:50:23Z)
Well if you only need to rebuild your system again and you don't necessarily care about the updates you're missing out on, you can try using a previous version of your file
Change:
# external apps shipped with linux-mint hexchat gnome-calculator <ins> gnome-calendar </ins> gnome-screenshot ] config.environment.cinnamon.excludePackages; })

Discussion:
I have 2 clear bugs for cinnamon that I can't find a way to solve 1- not working due to missing of 2- doesn't show events due to missing of both of the issues related to Steps to reproduce the behavior: in any of the bugged apps
Change:
MediaAccessibility      = [ CF CoreGraphics CoreText QuartzCore ]; MediaToolbox            = [ AudioToolbox AudioUnit CF CoreMedia ]; Metal                   = []; <ins> MetalKit                = [ ModelIO Metal ]; ModelIO                 = [ ]; </ins> NetFS                   = [ CF ]; OSAKit                  = [ Carbon ]; OpenAL                  = [];

Discussion:
We are currently stuck on qt 5.11 on darwin/macOS. To get things consistent, this should update to qt 5.12 (or even 5.13) soon. Please run and paste the results.
If qt512 builds on darwin we should change the default version:
is currently broken:
Fixed in

When running the provided by the package, it complains about not finding the tool, which is provided by . I have not found a suitable workaround, since it seems like the location of the scanner is hardcoded inside Invoke on a project using Qt. How to use this tool is explained here: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(raskolnikov): nixpkgs:
The error is as follows:
Hi I tried withyour latestchanges from . The fact that Qt 5.12 now works on Darwin again is great news! However, this issue seems to not be resolved. Now the does not bail out inmmediately as it did before. It does indeed do something for a while, but then later I get: Maybe there is some other part of the code where it is missing the path correction? Thanks a lot!
My bad, I was actually using the old one by mistake... I am getting new errors though: I will investigate...
I think I found the issue. The problem is this line: is returning , which is incorrect. I think lines 1258-1260 can be discarded altogether since without the tool is still correctly using , which is a better way of passing the import paths, since inside Nix we actually need multiple import paths anyways due to the modularized Qt installation. Would you be happy to extend the patch with such a modification?
Ok... I have further investigated and I was wrong... One must indeed pass to to really make it work. One can indeed pass multiple times, and probably we shall do it for every entry in . Probably this can be patched... but it seems like we are getting into non trivial patching territory...
Thanks Mathew for reopening the issue. I opened a corresponding issue on Qt:
I marked this as stale due to inactivity. &rarr;
Actually this still stands and it'd be nice to have it fixed some day. There are other issues that are blocking me on Mac these days though, like .
I marked this as stale due to inactivity. &rarr;
Change:
layan-gtk-theme = callPackage ../data/themes/layan-gtk-theme { }; <ins> layan-kde = callPackage ../data/themes/layan-kde { }; </ins> lato = callPackage ../data/fonts/lato {}; league-of-moveable-type = callPackage ../data/fonts/league-of-moveable-type {};

Discussion:
Project description Layan kde is a flat Design theme for KDE Plasma desktop. In this repository you'll find: Aurorae Themes Kvantum Themes Plasma Color Schemes Plasma Desktop Themes Plasma Look-and-Feel Themes Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
angband = callPackage ../games/angband { }; <del> anki = python2Packages.callPackage ../games/anki { }; </del> <ins> anki = python3Packages.callPackage ../games/anki { }; </ins> armagetronad = callPackage ../games/armagetronad { };

Discussion:
With the current packaged version of Anki, downloading addons fails with an SSLCERTIFICATEVERIFYFAILED. Download any addon from the Ankiweb library. I used , but any addon causes the issue. Go to to enter the ID. Then this error shows up in a dialog box: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
The update to anki 2.1 () will close this issue, according to my testing. (Add-on downloads work perfectly.)
(oops, I'll keep it open until that PR is merged)
Given that some useful addons don't support Anki 2.1, I'd like this to be fixed for 2.0. OTOH I'm not sure how this can be done.
You can still manually install addons by dropping the files in . An example is described .
Change:
./patches/15.9-kcl_str.patch ./patches/15.9-mtrr.patch ./patches/15.9-preempt.patch <del> ./patches/15.9-sep_printf.patch ]; </del> <ins> ./patches/15.9-sep_printf.patch ] ++ optionals ( kernel != null && (builtins.compareVersions kernel.version "4.6") >= 0 ) [ ./patches/kernel-4.6-get_user_pages.patch ./patches/kernel-4.6-page_cache_release-put_page.patch ]; </ins> buildInputs = [ xorg.libXrender xorg.libXext xorg.libX11 xorg.libXinerama xorg.libSM

Discussion:
Two compilation errors are seen. I have a fix at , but I expect that it needs to be variablized to only apply these two new patches if building against a 4.6 (or greater) kernel, and I don't know how to do that. add'l keywords: ati_unfree
Compiler output:
You can add a simple conditional, e.g. similar to
Excellent, thanks for the pointer! Reworked and created a pull req.
Change:
habanero = callPackage ../development/python-modules/habanero { }; <ins> i3ipc = callPackage ../development/python-modules/i3ipc { }; </ins> intelhex = callPackage ../development/python-modules/intelhex { }; lmtpd = callPackage ../development/python-modules/lmtpd { };

Discussion:
i3ipc python package exists in pypy but not in nixpackages. It would be great if we could use it. Link for reference: Thanks. I'm probably up for writing the nix package definition if someone can point me in the right direction,
for future reference, what mistakes did I make? It's my first week of nix (and I'm loving it).
Python packages are part of the attribute of the interpreter, so is the reference to the package. While it is now possible to use the supported solution is The other one typically works, but not always because is not always propagated and thus unavailable. Also, guarantees that you will have the Python that is "connected" to the package, and not accidentally the one that was in your . Good to hear!
Thanks! Interesting to see the differences.
Just wanted to let you know that I finally got my i3 setup working near perfectly on nixos! Loving it (Thank you all)
Change:
else if mysqlLocal then "localhost:/run/mysqld/mysqld.sock" else "localhost"; defaultText = "localhost"; <ins> example = "localhost:5000"; </ins> description = lib.mdDoc '' <del> Database host or socket path. </del> <ins> Database host (+port) or socket path. </ins> If [](#opt-services.nextcloud.database.createLocally) is true and [](#opt-services.nextcloud.config.dbtype) is either `pgsql` or `mysql`, defaults to the correct Unix socket instead. ''; }; <del> dbport = mkOption { type = with types; nullOr (either int str); default = null; description = lib.mdDoc "Database port."; }; </del> dbtableprefix = mkOption { type = types.nullOr types.str; default = null;

Discussion:
The configuration is ignored by when setting up the database as it is a configuration no longer used in the latest versions of See Steps to reproduce the behavior: up "dbhost" to "/run/postgresql", and "dbport" to anything else than 5432 (default pgsql port), let's say 5435 for example -setup.service will fail saying the file is not found In , the value should be set as instead, any field is ignored (and should then be deleted)
FYI
Change:
let <del> version = "1.43_4"; </del> <ins> version = "1.43_5"; </ins> # Updated according to https://github.com/patjak/bcwc_pcie/pull/81/files

Discussion:
I don't really know why my system configuration for an XPS 13 is pulling this in, either: EDIT: I had set in my system configuration, thus causing me to (fail to) build .
I have the same problem on 3 laptops As mentioned in above post issue is related to enableAllFirmware = true; Chnaging to enableRedistributableFirmware = true; fixed the issue for now another example
cc maintainers:
I think, the new url could be found on this page
I'll try to find time over the weekend to update new offsets and hashes for the new download path. In the meantime, facetimehd users can extract the firmware from their OSX partition with this override: ``
See
Change:
reaper = callPackage ../applications/audio/reaper { jackLibrary = libjack2; # Another option is "pipewire.jack". <ins> ffmpeg = ffmpeg_4-headless; </ins> }; recapp = callPackage ../applications/video/recapp { };

Discussion:
reaper can't export video (wrong ffmpeg version) in nixos 23.05 Steps to reproduce the behavior: the package reaper -Render : "Video (ffmpeg/libav encoder)" is missing There should be an option in the list where you can use ffmpeg as encoder If you override the ffmpeg dependency with: (reaper.override { ffmpeg = pkgs.ffmpeg_4-full; }) then it works.
Change:
rabbitmq-c = callPackage ../development/libraries/rabbitmq-c {}; <ins> raft-canonical = callPackage ../development/libraries/raft-canonical { }; </ins> range-v3 = callPackage ../development/libraries/range-v3 {}; rabbitmq-java-client = callPackage ../development/libraries/rabbitmq-java-client {};

Discussion:
Describe the bug I'm not able to start any (freshly created) container in lxd. To Reproduce Steps to reproduce the behavior: Expected behavior Container starts without issues. Additional context Log gathered via Regarding the not enough space, I'm quiet sure that the report is wrong: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs: Maintainer information:
Maybe updating helps? I started working on a PR, though I depend on a which fails to build.
tested with merged on top inside a nogui VM
Wrong commit?
yip