jiebi/CodeConvo huggingface dataset:
Code change:
}; enableSuid = mkOption { type = types.bool; <del> default = true; </del> <ins> # SingularityCE requires SETUID for most things. Apptainer prefers user # namespaces, e.g. `apptainer exec --nv` would fail if built # `--with-suid`: # > `FATAL: nvidia-container-cli not allowed in setuid mode` default = cfg.package.projectName != "apptainer"; defaultText = literalExpression ''config.services.singularity.package.projectName != "apptainer"''; </ins> example = false; description = mdDoc '' Whether to enable the SUID support of Singularity/Apptainer.

Related discussion:
text: Meanwhile, in my config I'm still abusing You probably already have guessed, but singularity in nixpkgs is configured to read this config from the package-specific directory, rather than from the global . You could in principle override this behaviour, but there maybe isn't much value in supporting that
I tried to enable the use of external sysconfdir (), but have encountered issue trying to specify a directory under with the NixOS module ().
Have you tried to apply both at the same time?
The SingularityCE Admin Guide says If the value of nvidia-container-cli path is empty, SingularityCE will look for the binary on $PATH at runtime. It should work as long as is found in the run-time , even when is not set. As nvidia-container-cli is alredy included in the PATH-prefixing wrapper, we shouldn't have to set the .
Update: I found a bug in the prefixed PATH of the wrapper introduced in . The prefixing should be specified as (in Bash) I forgot to add , causing the trailing to be missing.
The statement in the SingularityCE Admin Guide turns out to be wrong / irrelevant. The source code clearly states that nvidia-container-cli will only be read from the configuration.
(we need to patch nvidia-container-cli, for many reasons )
Eh, actually, closed semi-automatically. Apptainer with is fixed (on NixOS), but not with . The fix doesn't concern singularity-ce either, unfortunately. Shouldn't be hard to make this work with singularity too, but I'm out of bandwidth
Hi folks, I've been trying to get apptainer to run this (which I've done previously successfully with a slight ldconfig hack -- that doesn't work anymore -- on NixOS 22.11), that will make use of the machine's Tesla V100 to do some simulation stuff. The machine is running NixOS 23.11. Using the workaround from 9th of May post further up, I was able to get past the ldconfig issue, but now I'm getting an error saying the driver and CUDA are not in sync.
Code change:
}; enableSuid = mkOption { type = types.bool; <del> default = true; </del> <ins> # SingularityCE requires SETUID for most things. Apptainer prefers user # namespaces, e.g. `apptainer exec --nv` would fail if built # `--with-suid`: # > `FATAL: nvidia-container-cli not allowed in setuid mode` default = cfg.package.projectName != "apptainer"; defaultText = literalExpression ''config.services.singularity.package.projectName != "apptainer"''; </ins> example = false; description = mdDoc '' Whether to enable the SUID support of Singularity/Apptainer.

Related discussion:
text: Before I start posting any details (I don't want to re-open this issue, but I'm also not sure if I'm just doing something wrong) I was wondering if the current implementation of singularity/apptainer on NixOS is expected to work, and I'm just being an idiot, or if there are known breaking issues? I've seen the other issues about singularity/apptainer here, but I'm not knowledgeable enough to make a judgement call if they are responsible for my problem or not. Thanks very much in advance!
(If I understood the message correctly) That usually means you need a reboot, and you should experience the same issue outside the container
No, the reboot didn't help either. For some reason, though, after upgrading to 24.05, everything "just works[tm]" again. So, whatever the issue was, thanks for fixing it (probably)! :)
Thanks to Nixpkgs 24.05 includes GPU-related changes/fixes to the package and the module.
Well more like thanks to ShamrockLee
Code change:
echo "Adding contents..." for item in $contents; do echo "Adding $item" <del> rsync -a $item/ layer/ </del> <ins> rsync -ak $item/ layer/ </ins> done else echo "No contents to add to layer."

Related discussion:
text: dockerTools.buildImage fails with: System: 17.03pre95306. (Gorilla) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: "17.03pre95306."
Code change:
abuild = callPackage ../development/tools/abuild { }; <ins> actiona = libsForQt5.callPackage ../applications/misc/actiona { }; </ins> actionlint = callPackage ../development/tools/analysis/actionlint { }; adreaper = callPackage ../tools/security/adreaper { };

Related discussion:
text: Project description mouse macro Actiona is a task automation tool. It allows you to create and execute action lists. You don't need to know any programming language to use it: its intuitive interface allows you to create action lists (scripts) using drag & drop. Advanced users can use JavaScript (EcmaScript) to extend its functionality. Actiona is free software and runs under Windows and GNU/Linux. Binaries are available for Windows and Ubuntu for both 32 and 64 bits. The program is developed in C++ and uses the Qt framework. Metadata homepage URL: source URL: license: gpl3 platforms: cross-platform
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 .
Code change:
<del> diff --git a/core/base/inc/ROOT/StringConv.hxx b/core/base/inc/ROOT/StringConv.hxx index 629fc18..4efa54a 100644 --- a/core/base/inc/ROOT/StringConv.hxx +++ b/core/base/inc/ROOT/StringConv.hxx @@ -89,7 +89,7 @@ EFromHumanReadableSize FromHumanReadableSize(std::string_view str, T &value) size_t size = str.size(); size_t cur; // Parse leading numeric factor -      const double coeff = stod(str, &cur); +      const double coeff = stod(static_cast<std::string>(str), &cur); // Skip any intermediate white space while (cur<size && isspace(str[cur])) ++cur; </del> diff --git a/core/metacling/src/TCling.cxx b/core/metacling/src/TCling.cxx index d71cb74..076facb 100644 --- a/core/metacling/src/TCling.cxx

Related discussion:
text: I have a system without Command Line Tools or XCode and nix'es cmake can't find headers and tries to pick up system frameworks. Try to build this: On my system I get: System: Darwin Nix version: nix-env (Nix) 1.11.9 Nixpkgs version: 17.09pre-git () Sandboxing enabled: no
Related to
Code change:
}; pythonPath = with pythonPackages; <del> [ setuptools eventlet greenlet gflags netaddr sqlalchemy7 carrot routes </del> <ins> [ setuptools eventlet greenlet gflags netaddr carrot routes </ins> PasteDeploy m2crypto ipy twisted sqlalchemy_migrate distutils_extra simplejson readline glanceclient cheetah lockfile httplib2 # !!! should libvirt be a build-time dependency?  Note that

Related discussion:
text: To make sure that we are on the same page: Kernel: System: Nix version: Nixpkgs version: broke legacy packages (only tested with the -set). Multiple options to solve this: revert the commit (an update will eventually have to be done) make sure no-one depends on sqlalchemy legacy versions (this would be the best choice, but can require a big amount of work) re-introduce an outdated version only used by legacy version (I’ll prepare a PR shortly that follows this path) cc
To be complete, the build problem is a test failure: I also checked, we cannot downgrade sqlite only for few pythonPackages, the entire python (and package set) have to be changed. Any preferred way to go?
(We should check if we still need this version, have it removed locally for virtmanager, virtinst as it isn't used, but haven't had the time to push that)
Yes, this is the preferred way to go. I began that but did not finish it yet, and it impacts some important parts (it causes xen to fail) I would prefer not to break because of unsufficient testing from me. This is in progress but could require some time to complete.
FYI xen already fails on
FYI: I switched away from sqlalchemy7 in yesterday.
Apart from virtinst, acd_cli, beaker, coilmq, and geeknote are the only revdeps of sqlalchemy7, as far as I can tell.
I openned to do some cleanup on sqlalchemy7. There still is that explicitly require . The same work will have to be done for and .
This should have remained open.
Using an older version of sqlite requires overriding the derivations of the interpreters.
See
Code change:
RUSTC_BOOTSTRAP = 1; meta = { <del> description = "ElKowars wacky widgets"; </del> <ins> description = "A widget system made in Rust to create widgets for any WM"; longDescription = '' Eww (ElKowar's Wacky Widgets) is a widget system made in Rust which lets you create your own widgets similarly to how you can in AwesomeWM. The key difference: It is independent of your window manager! It can be configured in yuck and themed using CSS, is very easy to customize and provides all the flexibility you need! ''; </ins> homepage = "https://github.com/elkowar/eww"; license = lib.licenses.mit; <del> maintainers = with lib.maintainers; [ coffeeispower eclairevoyant figsoda lom w-lfchen ]; </del> <ins> maintainers = with lib.maintainers; [ coffeeispower eclairevoyant figsoda lom w-lfchen ]; </ins> mainProgram = "eww"; broken = stdenv.isDarwin; };

Related discussion:
text: After upgrading to eww 0.6.0 from unstable I've got problems showing some strings in some of my widgets, one that shows the hour and another the minutes using two digits each one, i.e. : "09 : 10". When using eww 0.6.0 the string shown is like this: "... : ..." In eww's github repo I can see that there is a commit after version 0.6.0: And cloning eww repo with that commit, compiling it and using a local eww executable the problem explained before disappears for me. There's also another problem, asking eww-0.6.0 for version number shows it's 0.5.0: unstable eww 0.6.0 some string truncation (I think this is the problem) see "..." where a two char string with the hour should appear. eww should work as expected. Cloning eww repo with latest commit after v0.6.0 was published solves the problem for me.
~The current package for eww is . How did you install 0.6.0 from nixpkgs?~ ~As for the outdated 0.5.0 version in nixpkgs, there are three maintainers for eww in nixpkgs so it probably will be updated shortly, perhaps fetching a commit with the solution to the string truncation problem you describe.~ EDIT: i was wrong, see comment below.
I got it installed today from unstable when upgrading my system: But, as you say, if I look for it into unstable () it shows version 0.5.0...I can't understand very well this...I'm relatively new to nixos. Ok, I'll wait then. Thanks for your interest in this.
Oh sorry, you're right! There is eww 0.6.0 in master, although it didn't make it into unstable yet. I built the package and, indeed, truncation is broken the version is incorrectly reported So the truncation was fixed, as you mention, after the release, and the reported version . That . If you can't wait, for it, i'd recommend you use the package output from the eww flake.
Code change:
RUSTC_BOOTSTRAP = 1; meta = { <del> description = "ElKowars wacky widgets"; </del> <ins> description = "A widget system made in Rust to create widgets for any WM"; longDescription = '' Eww (ElKowar's Wacky Widgets) is a widget system made in Rust which lets you create your own widgets similarly to how you can in AwesomeWM. The key difference: It is independent of your window manager! It can be configured in yuck and themed using CSS, is very easy to customize and provides all the flexibility you need! ''; </ins> homepage = "https://github.com/elkowar/eww"; license = lib.licenses.mit; <del> maintainers = with lib.maintainers; [ coffeeispower eclairevoyant figsoda lom w-lfchen ]; </del> <ins> maintainers = with lib.maintainers; [ coffeeispower eclairevoyant figsoda lom w-lfchen ]; </ins> mainProgram = "eww"; broken = stdenv.isDarwin; };

Related discussion:
text: I personally have been using it for a while and it works correctly (let me know if you need help, i'm on the matrix server with the same username). For now, I guess this issue can be closed because both are upstream bugs and the fixes will make it into a future release.
I think I we can backport the changes using patches. I'll send a PR.
Still I don't know how this 0.6.0 version was pulled from unstable into my system...I'm in my way learning nixos. Flakes! my never ending story :). I'll try to use it and if I have problems I'll try to ping you on the matrix server. Thx!
Since 0.6.0 reached unstable, of course, and you updated your channels/inputs. BTW the search can be out-of-date, so don't expect 100% accuracy from it.
Yep, that makes sense to me and seems to be the missing piece that confused me: how could it be possible that in the search appeared version 0.5 and I had installed v 0.6. thanks for clarifying it for me and for your work in Nixos.
Code change:
# fix up this call: # https://github.com/kaldi-asr/kaldi/blob/c9d8b9ad3fef89237ba5517617d977b7d70a7ed5/cmake/VersionHelper.cmake#L8 echo 0 <ins> elif [[ "$1" == "rev-parse" ]]; then echo ${openfst.rev} echo 0 </ins> fi true EOF

Related discussion:
text: cc
Bisected to
This is an error when calling . We should fix git wrapper.
Code change:
{ stdenv , lib , fetchFromGitHub <ins> , removeReferencesTo </ins> , makeWrapper , which , writeTextFile

Related discussion:
text: Describe the bug dmd keeps references to boostrap compiler. To Reproduce Steps to reproduce the behavior: Expected behavior dmd has no references to boostrap compiler Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(symphorien): nixpkgs: Maintainer information: Note: to prevent future regressions, it would be nice to add to the derivation ()
I marked this as stale due to inactivity. &rarr;
Still an issue
I marked this as stale due to inactivity. &rarr;
Code change:
runtimeEnv = { efiMountPoint = config.boot.loader.efi.efiSysMountPoint; }; <ins> # We disable SC2016 because we don't want to expand the regexes in the sed commands. excludeShellChecks = [ "SC2016" ]; </ins> text = builtins.readFile ./xen-boot-builder.sh; }; in

Related discussion:
text: The final merged version of isn't building. Just build with the initial configuration that would give on a UEFI machine, along with: Build successfully and boot into Dom0 on next reboot. <img width="1201" alt="image" src=""During the progress of , the issue isn't happening as of . Might be a regression happened in the last few commits before it's merged. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Whoops. That's my bad. Will make a PR in a few.
Code change:
}; # put packages that needs to be overridden in the py package scope <del> py = import ./python-packages.nix { inherit stdenv src version python3 fetchPypi; }; </del> <ins> py = callPackage ./python-packages.nix { inherit src version; }; </ins> in py.pkgs.toPythonApplication (py.pkgs.buildAzureCliPackage {

Related discussion:
text: Steps to reproduce the behavior: azure-cli 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.
For now, changing python used to seems to fix the build:
Made a PR that fixes the failure.
Will investigate this failure and try to fix it (by using Python 3.11), but the build was working before (We may temporarily fix it using as a workaround), some dependencies must have been changed, from before, not sure which one is causing this failure, I'd need to bisect commits on master branch, I guess...
The failure is because of python3.11, the tests didn't work properly on 3.11. Upstream fixed those tests for a future release. For now we can either rollback the python used to 3.10, or back port the tests fixed. From what I tested, nothing is broken on 3.11 except for those tests.
Thanks a lot for those clarifications and appreciating a lot your help in fixing all this However, we can't really make sure that those tests won't break again, unless we pin a patch on those ? And this is what you've done in your fix PR. I'll be trying the latest release 2.53.1 with the dependencies cleanup.
Code change:
<del> { stdenv, buildPackages, fetchurl, perl, buildLinux, modDirVersionArg ? null, ... } @ args: with stdenv.lib; buildLinux (args // rec { version = "5.8"; # modDirVersion needs to be x.y.z, will automatically add .0 if needed modDirVersion = if (modDirVersionArg == null) then concatStringsSep "." (take 3 (splitVersion "${version}.0")) else modDirVersionArg; # branchVersion needs to be x.y extraMeta.branch = versions.majorMinor version; src = fetchurl { url = "mirror://kernel/linux/kernel/v5.x/linux-${version}.tar.xz"; sha256 = "1xgibkwb1yfl6qdlbxyagai0qc1pk5ark7giz1512hh6ma353xz7"; }; } // (args.argsOverride or {})) </del>

Related discussion:
text: Describe the bug The is failing. I bisected this problem to “linux: Init 5.8”. The error message matches , which points to both a workaround of recompiling systemd against Linux 5.8 headers, and an upstream systemd patch (systemd/systemd) that’s in systemd 246 () and was backported in 245.7 as systemd/systemd-stable To Reproduce Steps to reproduce the behavior: Notify maintainers Cc Metadata Please run and paste the result. Maintainer information:
My PR wasn't merged, Linux 5.8 ended up being by someone else.
Linking for visibility: that PR was
The PR bumping systemd to 245.7 is at
Is it really helpful to send systemd 245.7 to given that will be unable to advance without it? Or are you thinking we also want to revert the bump in for now?
Maybe we should revert in master, and re-revert it in staging again. I let and decide about this, they've been doing the staging rounds.
Hey all, question: How do you spot which tests block the channels? I always track and every few days I notice nixos-unstable doesn't progress. When it don't I see an issue with the "channel blocker" label and I always wonder..
Click on the “Hydra job for tests” link and go to the “Constituents” tab.
Code change:
}; nativeBuildInputs = [ makeWrapper ]; <del> buildInputs = [ jre8 which gawk ]; </del> installPhase = '' mkdir -p "$out/share/neo4j"

Related discussion:
text: Describe the bug Neo4j does not start because it cannot locate a Java Runtime. To Reproduce On my system, I installed with: Then, running shows: "The operation couldn’t be completed. Unable to locate a Java Runtime." Expected behavior Neo4j should start. Additional context Note that shows Note the line that sets to . 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:
Code change:
ln -sfT ${cfg.package}/modules ${cfg.dataDir}/modules if [ "$(id -u)" = 0 ]; then chown -R elasticsearch ${cfg.dataDir}; fi ''; <del> postStart = mkBefore '' until ${pkgs.curl.bin}/bin/curl -s -o /dev/null ${cfg.listenAddress}:${toString cfg.port}; do sleep 1 done ''; </del> }; environment.systemPackages = [ cfg.package ];

Related discussion:
text: The postStart script of elasticsearch fails when a special values like or ( ) is used for services.elasticsearch.listenAddress as the script expects an IP or a hostname. Using an ip as listenAddress ist not always a viable option especially when generating NixOS images upfront for a dynamic deployment (e.g. on Azure or EC2) I am not sure how to address this issue. Perhaps one shall check netstat output to find out which ip was bound to? /cc
Yes i agree, we should implement another option for es url, I'm fine even with removing postStart. You can create pull request if you need fix asoap, I will put it on to-do.
Code change:
mod = callPackage ../development/tools/mod { }; <ins> mongosh = callPackage ../development/tools/mongosh { }; </ins> mysql-shell = callPackage ../development/tools/mysql-shell { inherit (darwin) cctools developer_cmds DarwinTools; inherit (darwin.apple_sdk.frameworks) CoreServices;

Related discussion:
text: Project description The MongoDB Shell Metadata homepage URL: source URL: license: APACHE LICENSE, VERSION 2.0 platforms: linux, darwin
I will like to have it on too but fyi there is a NUR package.
Thanks, I haven't searched in NUR
Code change:
mesonAutoFeatures = "disabled"; <del> mesonFlags = builtins.concatLists [ (lib.optional enableXWayland "-Dxwayland=enabled") (lib.optional legacyRenderer "-Dlegacy_renderer=enabled") (lib.optional withSystemd "-Dsystemd=enabled") </del> <ins> mesonFlags = [ (lib.mesonEnable "xwayland" enableXWayland) (lib.mesonEnable "legacy_renderer" legacyRenderer) (lib.mesonEnable "systemd" withSystemd) </ins> ]; postInstall = ''

Related discussion:
text: Package name: hyprland Latest released version: 0.36.0 <!-- Search your package here: --- Current version on the unstable channel: 0.35.0 Current version on the stable/release channel: 0.32.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]: The 035.0 has a bug that makes my system crash very often (nullptr when monitor is disconnected) the issue is supposed to be fixed in 0.36.0.