jiebi/CodeConvo huggingface dataset:
Change:
diskSize = "auto"; additionalSpace = "0M"; # Defaults to 512M. copyChannel = false; <ins> memSize = 2048; # Qemu VM memory size in megabytes. Defaults to 1024M. </ins> } ```

Discussion:
Building an Amazon AMI with zfs root fails with inside the vm getting an error trying to allocate memory partway through building the new store. It isn’t surprising that a zfs-using system needs more memory when doing intensive filesystem writes. Unfortunately I don't know how to adjust the config (other than globally in a nixpkgs fork) for how much memory to give the vm. $ nix-build -A amazonImageZfs.x8664-linux … error: reading directory '/nix/store/4l99mg8j2c3bqjlc10ncdfcq5vaazxb9-nixos-22.11pre130979.gfedcba/nixos/pkgs/tools/misc/tagref': Cannot allocate memory (the specific package or failure point varies a little on each run based on random timings and resource usage) system: host os: multi-user?: sandbox: version: channels(root): channels(dan): nixpkgs:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
''; }; <ins> systemd.sleep.extraConfig = mkOption { default = ""; type = types.lines; example = "HibernateDelaySec=1h"; description = '' Extra config options for systemd sleep state logic. See sleep.conf.d(5) man page for available options. ''; }; </ins> systemd.user.extraConfig = mkOption { default = ""; type = types.lines;

Discussion:
Describe the bug Cannot configure systemd sleep settings. After my last upgrade my laptop started poweroff at nights.. where I only wanted it to suspend. I suspect this is because of the default systemd settings... but I cannot change them? To Reproduce Steps to reproduce the behavior: Expected behavior I should be able to set config values Maintainer information:
actually.. I tried with it gets two [Sleep] sections now.. but maybe it'll help :)
to add. the actual issue of the laptop powering down was apparently related to the firmware.. it was working perfectly for more than a year.. and one day, suddenly, some bit flipped. I've updated bios, firmwares etc and it helped. laptop is back from the suspend mode as earlier having said that, I think the issue here is still relevant - having a way to nicely override values is a good thing (my workaround is also seemingly working, so probably a low priority thing?)
I think a very low-effort change here would be to add an option that simply appends lines to the config. Would you want to make a PR for that?
Change:
<del> { stdenv, fetchurl, ncurses, pcre }: </del> <ins> { stdenv, fetchurl, ncurses, pcre, fetchpatch }: </ins> let version = "5.6";

Discussion:
type "setxkbmap" then try to trigger completion with <tabPlease run and paste the results. system: host os: multi-user?: sandbox: version: nixpkgs:
I can reproduce it on with ZSH 5.6 (and inside which shouldn't be relevant). I just had a short look through the commit log of and the code is quit old, did it work before for you? (I'm just using in some personal shell scripts and quite rarely directly, so I can't tell if the completionactually worked). However the code of the completion in my seems quite broken for NixOS as it tries to search directories, a behavior that should be patched accordingly. I can try to fix it (didn't find further related issues ATM, let's see)...
I just managed to get it working by adding to the hook of the ZSH package locally. I'm not sure though if it's the best solution. Let me think if there's something better to do, otherwise I'd file a patch :)
would you mind having a look at this patch: Will file it tomorrow, but I'm not sure, why not sure if there's a better way (don't like to manually specify in the derivation).
yep it seems to have fixed it :)
Change:
flex = flex_2_5_35; }; <del> crawl = callPackage ../games/crawl { lua = lua5; }; </del> <ins> crawlTiles = callPackage ../games/crawl { }; crawl = callPackage ../games/crawl { tileMode = false; }; </ins> cv = callPackage ../tools/misc/cv { };

Discussion:
Here is the output from nixos-rebuild: I'm not sure if this is a known issue or not, but I made sure to upgrade as well and it is still failing.
Change:
patches = [ ./support-db2x.patch <ins> (fetchurl { url = https://github.com/lxc/lxc/commit/b31d62b847a3ee013613795094cce4acc12345ef.patch; sha256 = "0j4ch22l81b20m03l818442ra47hw4k6zyizsn3a0q3gv6mq5h7x"; }) </ins> ]; postPatch = ''

Discussion:
Describe the bug A clear and concise description of what the bug is. When you try to run the session-manager, the container-manager fails to create the container. Anbox itself does not provide any useful info when errors occur but after you find out where tf it logs to after an hour or two, you can scour for an error: To Reproduce Steps to reproduce the behavior: on 20.03 Expected behavior A clear and concise description of what you expected to happen. It should run the session-manager. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. This bug has been fixed in but this fix just barely didn't make it into lxc-3.2.1 which 20.03 is currently on. lxc-4.0.0 is the first release with the fix and Anbox works in nixos-unstable because it has lxc-4.0.2. 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. system: host os: multi-user?: sandbox: version: channels(root): channels(atemu): nixpkgs: Maintainer information:
Change:
# Remove Dead Interfaces ip link show "${n}" >/dev/null 2>&1 && ip link delete "${n}" ip link add link "${v.interface}" name "${n}" type vlan id "${toString v.id}" <del> ip link set "${n}" up </del> <ins> # We try to bring up the logical VLAN interface. If the master # interface the logical interface is dependent upon is not up yet we will # fail to immediately bring up the logical interface. The resulting logical # interface will brought up later when the master interface is up. ip link set "${n}" up || true </ins> ''; postStop = '' ip link delete "${n}" || true

Discussion:
VLAN interfaces created by no longer works properly after a reboot. The VLAN interface service fails with the error "RTNETLINK answers: Network is down". This is a regression from NixOS 17.03. I don't know when this functionality broke. The following was reproduced in a VM with a single interface named "ens32". The same issue is present on different hardware. Added to When switching to this config, the interface "testvlan" comes up. After rebooting the interface is not created (when it should be): Starting the service manually after having booted gets the interface up. System: 17.09pre113138. Nix version: 1.11.13 Nixpkgs version: 17.09pre113138. Sandboxing enabled: Yes
Thanks! I can confirm this fixed the issue.
Awesome! Thanks for testing!
I am still experiencing this issue. I have a fairly complex networking setup with several vlan interfaces attached to a single physical interface. More often than not the system fails to bring up some of the vlan interfaces. It seems as if it tries to bring up the vlan interface before the physical interface is completely up and running. This is what it often looks like in the journal: The complete nixos configuration for a system with this issue can be found here: I am running NixOS 18.03.. (Impala) on a physical machine. I would be happy to assist in troubleshooting this issue.
I too am having issues once more on 18.03, booting with VLAN interfaces is very unreliable. I have not taken the time to look into it but I can also try to assist.
Could you perhaps reopen this issue, or would it be better to create a new one?
I'm experiencing random failure during boot on NixOS 18.03 Please review my PR
The issue is intermittent for me, so it's difficult to say for sure. I can reboot 5 times in a row successfully and then fail 3 times in a row, which is roughly what happened when I tried to reproduce this now. With applied to NixOS 18.03 it worked every time, when rebooting about 10 times... today anyway. Rolling back pre-patch I got it to fail again after just a couple of attempts.

Given all the hassle with our networking scripts, should we enable the networkd backend for the module by default?
I'm currently working on making that a reality for 18.09.
Cool, is there an issue tracking that somewhere? How to try it, is it networking.useNetworkd, or both? Shouldn't this issue be reopened? The issue as it's described in the first comment is still true, only harder to reproduce. Update: I guess it's .
Change:
<ins> { stdenv , cargo , rustc , fetchFromGitHub , glib , gtk4 , libadwaita , rustPlatform , openssl , pkg-config , lib , wrapGAppsHook4 , meson , ninja , gdk-pixbuf , cmake , desktop-file-utils , gettext , blueprint-compiler , appstream-glib }: stdenv.mkDerivation rec { pname = "geopard"; version = "1.4.0"; src = fetchFromGitHub { owner = "ranfdev"; repo = pname; rev = version; hash = "sha256-elHxtFEGkdhEPHxuJtcMYwWnvo6vDaHiOyN51EOzym0="; }; cargoDeps = rustPlatform.importCargoLock { lockFile = ./Cargo.lock; }; nativeBuildInputs = [ openssl gettext glib # for glib-compile-schemas meson ninja pkg-config wrapGAppsHook4 cmake blueprint-compiler desktop-file-utils appstream-glib blueprint-compiler cargo rustc rustPlatform.cargoSetupHook ]; buildInputs = [ desktop-file-utils gdk-pixbuf glib gtk4 libadwaita openssl ]; meta = with lib; { homepage = "https://github.com/ranfdev/Geopard"; description = "Colorful, adaptive gemini browser"; maintainers = with maintainers; [ jfvillablanca ]; license = licenses.gpl3Plus; platforms = platforms.linux; mainProgram = "geopard"; }; } </ins>

Discussion:
Project description Colorful, adaptive gemini browser <!-- Describe the project a little: --Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
}; }; <del> closed = closeModules (modules ++ [ internalModule ]) { inherit config options; lib = import ./.; }; </del> <ins> closed = closeModules (modules ++ [ internalModule ]) (specialArgs // { inherit config options; lib = import ./.; }); </ins> # Note: the list of modules is reversed to maintain backward # compatibility with the old module system.  Not sure if this is

Discussion:
I'm thinking of bringing this line back: and getting rid of nixos/modules/misc/extra- Does anyone have objections? I fully buy the ability to pass arguments in the module system using , but if it doesn't work (and breaks in a horrible way) for the most common use case ( in imports), that seems bad and the cost of restoring the old way seems pretty low. Anyone have objections? I can make the change if nobody objects. Ideally, I'd like it in 15.06, since it's getting in the way of some work I'm trying to squeeze into 15.06. cc
IMO our only choices are to do this or to set as a prerequisite (perhaps enforced using ) that points there. No strong preference either way.
Yeah, this is probably the best solution.
Cool! Do any of you know of VM tests that would suitably make sure I don't break anything too obvious by making that change? I'd obviously rather not make the change and then discover a week from now that I broke someone's key use case :smile: I'll be making the change this evening at this rate.
Any thoughts on having set using scopedImport? That way stays NixOS-independent. But not a huge difference IMO.
I don't see how adding back could break anything.
Famous last words! :grinning: But I agree, as long as it evaluates at all it's almost certainly fine.
That sounds more complicated than the one-liner suggested by
Change:
{ lib , python3Packages , fetchPypi <ins> , qt5 </ins> }: python3Packages.buildPythonApplication rec { pname = "graph-cli"; <del> version = "0.1.18"; </del> <ins> version = "0.1.19"; </ins> src = fetchPypi { inherit version; pname = "graph_cli"; <del> sha256 = "sha256-0mxOc8RJ3GNgSbppLylIViqfYf6zwJ49pltnsyQUpSA="; </del> <ins> hash = "sha256-AOfUgeVgcTtuf5IuLYy1zFTBCjWZxu0OiZzUVXDIaSc="; </ins> }; <ins> nativeBuildInputs = [ qt5.wrapQtAppsHook ]; dontWrapQtApps = true; preFixup = '' makeWrapperArgs+=("''${qtWrapperArgs[@]}") ''; </ins> propagatedBuildInputs = with python3Packages; [ numpy pandas <del> matplotlib </del> <ins> (matplotlib.override { enableQt = true; }) </ins> ]; # does not contain tests despite reference in Makefile

Discussion:
The package (binary ) is unusable at runtime: it always crashes. Steps to reproduce the behavior: results in an error: The application works. N/A. Add any other context about the problem here. Maybe ? As they committed a version upgrade Please run and paste the result.
The error appears to be caused by . Replacing it with resolves the error, but results in the following messages: It seems to be a wrapping issue in .
try adding to
I just tried and I still get the exact output as (except I don't have the Wayland error):
cc (as maintainers of )
You'll also need a for the entry point exectables.
Possibly, python executables need to be wrapped manually like
Thank you your last message was correct! I have opened with that fix, it works on my machine now
Change:
fusionInventory = callPackage ../servers/monitoring/fusion-inventory { }; <ins> gamehub = callPackage ../games/gamehub { }; </ins> gatling = callPackage ../servers/http/gatling { }; gitlab-pages = callPackage ../servers/http/gitlab-pages { };

Discussion:
repo: originally mentioned at
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 . on the on .
still important to me
I marked this as stale due to inactivity. &rarr;
Still important to me
Any progress on this?
There is a PR open at
The PR has sadly been closed :(
I marked this as stale due to inactivity. &rarr;
Change:
src = nushell.src; <del> cargoHash = "sha256-8iUqOdGWm2kDW72ptlCBIqqe4zjckN09MOQD77kCf5Y="; </del> <ins> cargoHash = "sha256-xyty3GfI+zNkuHs7LYHBctqXUHZ4/MNNcnnfYvI18do="; </ins> buildInputs = lib.optionals stdenv.isDarwin [ IOKit CoreFoundation ];

Discussion:
Steps to reproduce the behavior: / / All plugins show the same error with a different hash when building, I only included the log from : The es were updated with but the plugins fail with a hash mismatch on two machines I tried it on. Both are x86_64 machines running NixOS unstable. I can make a PR to update the hashes, but I want to make sure I'm not missing something. Please run and paste the result.
I've just opened a PR to fix this, if you have time to review, it would be great, otherwise no worries. I won't wait too long before merging since everything is broken.
Looks good to me, those are the same hashes I got.
Change:
bind = mkOption { type = with types; nullOr str; <del> default = null; # All interfaces description = "The IP interface to bind to."; example = "127.0.0.1"; </del> <ins> default = "127.0.0.1"; description = '' The IP interface to bind to. <literal>null</literal> means "all interfaces". ''; example = "192.0.2.1"; </ins> }; unixSocket = mkOption {

Discussion:
The redis service module listens on all interfaces by default (I found it via which inherits nixpkgs' default): I think that is bad, because that is an insecure configuration. Because many people get owned by that, Redis has a protection against it; without further configuration, connecting to the listening port via TCP, it outputs: But it's still listening on the port. This has been that way for 7 yeas since the module was in by I think many NixOS modules that define services which are usually used unauthenticated by now make them only listen to by default. So I think we should do that with the module as well. CC recent service module committers CC contributors
Evindence that pretty much all other DB servers listen to by default in NixOS:
Fix in PR .
Change:
buildDotnetModule rec { pname = "OpenTabletDriver"; <del> version = "0.6.1"; </del> <ins> version = "0.6.2.0"; </ins> src = fetchFromGitHub { owner = "OpenTabletDriver"; repo = "OpenTabletDriver"; rev = "v${version}"; <del> sha256 = "sha256-9C6rtq+1WTinlAs0SJs1/J1QRnKm5pGNDSbLQ0kRUXY="; </del> <ins> sha256 = "sha256-D1/DGvSBgG8wZMmyJ7QAHDcsMjC1YgSpxmSYzs6ntJg="; </ins> }; debPkg = fetchurl {

Discussion:
Package name: opentabletdriver Latest released version: 0.6.2 Current version on the unstable channel: 0.6.1 Current version on the stable/release channel: 0.6.0.4 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Change:
services.openssh.enable = false; services.lshd.enable = true; programs.ssh.startAgent = false; <del> services.xserver.startGnuPGAgent = true; </del> # TODO: GNU dico. # TODO: GNU Inetutils' inetd.

Discussion:
Commit from updated the default version of the GNU Privacy Guard a.k.a. GPG to version 2.1. Unfortunately, this update broke the gpg-related tests of , , apparently because there is some subtle change in the behavior of the GPG 1.x compatibility layer (git-annex relies on rather than using gpg2 directly). To remedy that issue, I fixed to use version 2.0 in . This is no good solution, unfortunately, because now people who rely on `gnupg1' end up having a version of GnuPG 2.0 in their profile that cannot talk to the gpg-agent from version 2.1, which happens to be the one that's installed in the system by default. In it's current state, gpg1 does not work reliably in NIxOS. To work around this issue, I would suggest that we revert to version 2.0 until we've had time to figure out what exactly has changed between versions 2.1 and 2.0 and why this affects .
FYI: Another thing I came across, due to a broken clawsmail pgp, was that the handling of gpg-agent differs from version 2.0 . GnuPG 2.1 do not use GPGAGENTINFO anymore. Instead it search for the gpg-agent socket in
For now at least, setting GPGAGENTINFO to $ seems to make claws-mail work.
Change:
<del> diff --git a/Cargo.lock b/Cargo.lock index fb17c7e..ef157e5 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -2332,10 +2332,10 @@ dependencies = [ [[package]] name = "magnum-opus" version = "0.4.0" -source = "git+https://github.com/open-trade/magnum-opus#3c3d0b86ae95c84930bebffe4bcb03b3bd83342b" +source = "git+https://github.com/TheRadioGuy/magnum-opus#171e1d021004626f7444d1e39b98f50bc3cb2604" dependencies = [ - "bindgen", - "target_build_utils", + "libc", + "opusic-sys", ] [[package]] @@ -2796,6 +2796,16 @@ version = "0.1.5" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "ff011a302c396a5197692431fc1948019154afc178baf7d8e37367442a4601cf" +[[package]] +name = "opusic-sys" +version = "0.3.6" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "5eace752ce07a037241dba8f02c654799f051e431b27028056bcb480e83b54f5" +dependencies = [ + "cmake", + "libc", +] + [[package]] name = "os_str_bytes" version = "6.0.0" </del> diff --git a/Cargo.toml b/Cargo.toml index 1b715bd..960e8da 100644 --- a/Cargo.toml

Discussion:
Steps to reproduce the behavior: rustdesk None
Should be fixed in , thanks if you can test it.
tested and it works! Will close once it gets merged lands on unstable.
Change:
owner = "singularityware"; repo = "singularity"; rev = version; <del> sha256 = "1i029qs6dfpyirhbdz0nrx2sh5fddysk4wqkjqj5m60kxs4x8a3d"; </del> <ins> sha256 = "09wv8xagr5fjfhra5vyig0f1frfp97g99baqkh4avbzpg296q933"; </ins> }; nativeBuildInputs = [ autoreconfHook makeWrapper ];

Discussion:
I get the following collision: What I don't understand is why this collision is happening in the first place? I'm installing this package into an empty profile!
That's a multiple-output problem. The derivation creates two of them, both containing the file. When installing into user profiles, currently the semantics is that all outputs are installed, so this creates the collision.
Vladimír Čunát writes: What's the reason for these semantics? I would expect only 'out' to get installed by default.
Well, as for build inputs, we normally want all to be available, because you need include, lib and possibly others. should know details. It hasn't been used much yet, so I suppose we still have to figure out how to do these best (and have the most usual setup as the default).
What I haven't figured out in these cases: why installing attempts to install both and .
I am getting this same error message. Fresh install of Nix 16. Could it have regressed? This happens when I run nix-env -iA nixos.openjdk but not when I dun nix-env -iA Though those both say they point to openjdk-8
Change:
<del> { lib, buildPythonApplication, fetchFromGitHub }: buildPythonApplication rec { pname = "pyprof2calltree"; version = "1.4.4"; # Fetch from GitHub because the PyPi packaged version does not # include all test files. src = fetchFromGitHub { owner = "pwaller"; repo = "pyprof2calltree"; rev = "v" + version; sha256 = "1vrip41ib7nmkwa8rjny1na1wyp7nvvgvm0h9bd21i262kbm4nqx"; }; meta = with lib; { description = "Help visualize profiling data from cProfile with kcachegrind and qcachegrind"; homepage = https://pypi.python.org/pypi/pyprof2calltree/; license = licenses.mit; maintainers = with maintainers; [ sfrijters ]; }; } </del>

Discussion:
Describe the bug Not really a "bug", but pyprof2calltree is hard-coded to and fails for Python 3 profile results with This can be fixed by changing the expression to . Not sure what to do here, move the program to since Python 2 will be EOL anyway?
Pinging the maintainer,
As can also be used as a library it would make sense to move it into and let the default attribute be Python 3.
My PR has been merged, does this solve the issue for you?