jiebi/CodeConvo huggingface dataset:
Change:
config = removeAttrs m ["key" "_file" "require" "imports"]; }; <del> applyIfFunction = f: arg@{ config, options, lib }: if isFunction f then </del> <ins> applyIfFunction = f: arg@{ config, options, lib, ... }: if isFunction f then </ins> let # Module arguments are resolved in a strict manner when attribute set # deconstruction is used.  As the arguments are now defined with the

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:
sha256 = "sha256-qNaljtuA5E/QaLJ9QILPRQCqOvKmX4ZGq/0z5unA8KA="; }; <ins> patches = [ # Fix build with meson 0.61, can be removed on next update. # https://github.com/NixOS/nixpkgs/issues/167584 (fetchpatch { url = "https://github.com/maoschanz/drawing/commit/6dd271089af76b69322500778e3ad6615a117dcc.patch"; sha256 = "sha256-4pKWm3LYstVxZ4+gGsZDfM4K+7WBY8EYjylzc/CQZmo="; includes = [ "data/meson.build" "help/meson.build" ]; }) ]; </ins> nativeBuildInputs = [ appstream-glib desktop-file-utils

Discussion:
A clear and concise description of what the bug is. See log gotten from : Steps to reproduce the behavior: to in your or to rebuild A clear and concise description of what you expected to happen. Build successfully <!-- 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.
Yeah is for 0.8.5 and 1.0.0 () breaks the build for meson 0.61 again...
Change:
parameterized ]; <del> # antlr4 issue prevents us from running the tests # https://github.com/antlr/antlr4/issues/4041 doCheck = false; </del> <ins> # FAILED tests/test_event_loops.py::TwistedEventLoopTest::test_run - AssertionError: 'callback called with future outcome: True' not found in ['... doCheck = !stdenv.isDarwin; </ins> <del> # pythonImportsCheck = [ #   "pyfx" # ]; </del> <ins> pythonImportsCheck = [ "pyfx" ]; </ins> meta = with lib; { description = "Module to view JSON in a TUI"; <del> mainProgram = "pyfx"; </del> homepage = "https://github.com/cielong/pyfx"; changelog = "https://github.com/cielong/pyfx/releases/tag/v${version}"; license = with licenses; [ mit ]; maintainers = with maintainers; [ fab ]; <ins> mainProgram = "pyfx"; </ins> }; }

Discussion:
python-fx fails at runtime, while doing its initial imports. Steps to reproduce the behavior: (hash is of as-of-writing nixpkgs-unstable) pyfx tui opens. Doesn't happen when e.g. installing current python-fx with pip on arch linux. (I considered packaging instead, but only found more breakage there. Anyway, I wouldn't be terribly sad if the answer to this is "Package abandonned, will be removed".) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have not used the TUI as so far only served as dependency for . Looks like
I poked around and I don't think that's the same issue at all. (It's the same cause, an old generated file is lying around, but it's a different old generated file.) The prePatch is pretty fishy, it first removes the antlr-related files and then invokes antlr. Fixing that runs into a few type errors, which can be fixed: Now you'd think those type errors are due to the new antler version, but that's only partially true? Downgrading still requires some patching. If I have time I'll submit a PR fixing this, but just patching out the type checks from the feels wrong, so I might consult with upstream first.
Change:
} {}; sublime-merge-dev = common { <del> buildVersion = "2011"; sha256 = "0r5qqappaiicc4srk08az2vx42m7b6a75yn2ji5pv4w4085hlrzp"; </del> <ins> buildVersion = "2022"; sha256 = "0fhxz6nx24wbspn7vfli3pvfv6fdbd591m619pvivig3scpidj61"; </ins> dev = true; } {}; }

Discussion:
Describe the bug When using Sublime-Merge, pushing to remote results in an error message: To Reproduce Steps to reproduce the behavior: both sublime-merge and git. a repository. something, so that the local master is ahead of the remote. a push. Expected behavior A password prompt appears, and the push continues as normal. Additional context Some earlier discussion occurred in on the Sublime team's own github. We eventually found that the for sublime-merge seems to build, patch, and then discard a copy of . This may be the source of the issue. 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. Output: Maintainer information:
Hi Thanks for letting me know, I've never tried entering a SSH passphrase directly through Sublime Merge before so I've never run into this issue, my ssh-agent just always handles it. I can say that the binary IS being included by the nix package and that the executable is finding and executing it properly (I confirmed this with strace), however for whatever reason the executable is just not creating the popup to ask for the passphrase and I don't understand why. I've followed up with the Sublime Merge team in , hopefully they will get back to me with some context about what the executable is looking for so that we can update the package to provide that.
So after discussing this with the helpful folks on the Sublime Merge repository, I was able to figure out what the problem is, it is happening because the functionality for actually depends on passing a special value as the to the executable. However the file that is trying to pass the to is actually a wrapper script that calls to run the actual binary after setting up the proper environment variables. There doesn't appear to be any way for the bash script to detect the argv[0] that was passed to bash as $0 is overwritten with the path to the bash script. I'm not sure how we will resolve this issue but at least we know what is causing it now. Maybe we can create a wrapper for the script that helps it execute the call properly against the un-wrapped binary or something.
Howdy , I created that should fix this issue. Would you be able to try this fix out yourself to see if it works for you?
Change:
firefox-beta = buildMozillaMach rec { pname = "firefox-beta"; <del> version = "130.0b2"; </del> <ins> version = "131.0b2"; </ins> applicationName = "Mozilla Firefox Beta"; src = fetchurl { url = "mirror://mozilla/firefox/releases/${version}/source/firefox-${version}.source.tar.xz"; <del> sha512 = "bfba17643923ec10686df7d0047e0fcba7716f96a645722869cc472f68bb42415e63ce37905a7d41f1bb3aa139ee7d336ac838bbbff105b3785eb522ebcb7eb0"; </del> <ins> sha512 = "1716b4189600d5eea9957c1ad2325a635f1f1178fb6e836bc9fe07d3ee2a71d5186af9511ad3e494403023834b58f7acb0b2716ee2acd5300797e2e8680b7cb8"; </ins> }; meta = {

Discussion:
Steps to reproduce the behavior: firefox-[beta/devedition]-unwrapped-130.0b2 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It seems that the relevant error from the logs is : The source file () is erroneous on 130.0b2, but also in b3 and b4. It seems to be fixed since 130.0b5
Should be fixed by
Change:
{ stdenv, callPackage }: callPackage ./generic.nix { <del> shortVersion = "2016-02-22"; </del> <ins> shortVersion = "2016-03-22"; </ins> isRelease = false; forceBundledLLVM = true; <del> srcRev = "d1f422ec280b881b8236c5d173103bc799e1590e"; srcSha = "b0753045ae438c0869d37f429fe84451dcacc4b2ab9413d34bf29fde94fde462"; </del> <ins> srcRev = "6cc502c986d42da407e26a49d4f09f21d3072fcb"; srcSha = "096lsc8irh9a7w494yaji28kzy9frs2myqrfyj0fzbxkvs3yfhzz"; </ins> /* Rust is bootstrapped from an earlier built version. We need to fetch these earlier versions, which vary per platform.

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

Discussion:
not working in lxc containers. But sysctl command works fine and /proc/sys/ is writable. This nix option seems to finally take effect via . And the look like this: This looks fine, So I tried to manually run the command in , and it takes effect! But this looks even weirder. Through , I got: There is an unusual . It looks like this: Obviously, there is not is NixOS. So won't run at all. I looked it up on the internet and found out it's from distrobuilder: So maybe we should just patch it? Steps to reproduce the behavior: a privilege container with NixOS in it. something to and rebuild the system , and there is no effect should run and takes effect. <!-- 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]:
Are you able to you reproduce this with unstable? There are some improvements post 23.11 to the use of the lxc generator.
Yes, I'm already on latest unstable channel. The channel information in metadata tab is incorrect because I'm using flakes. There are many hard-coded FHS paths in distrobuilder. Such as this line, that causes this problem:
can you test this change?
It works fine for me. But I don’t know if there are any problems caused by other hard-coded paths in distrobuilder. And I don’t know whether using sysctl on an unprivileged container will cause the service to fail to start, and whether the startup failure will cause problems. But it seems that sets , so there should be no problem?
Thanks for testing! There shouldn't be, since we patch and wrap the distrobuilder lxc generator. I audited it again after updating the patch for this fix. You can always see the resulting file by building . The PR has tests which should cover unprivileged containers. I've just updated them to add a check verifying systemd-sysctl successfully started.
Change:
evolution-data-server glib glib-networking <ins> # Needed for GtkMediaStream creation with success.ogg, see #311295. gst_all_1.gst-plugins-base gst_all_1.gst-plugins-good </ins> gtk4 gtksourceview5 gxml

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: Planify 4.7.2 a task a task by clicking the checkbox Planify crashing A clear and concise description of what you expected to happen. Planify does not crash eenshots to help explain your problem. Add any other context about the problem here. Here's the last line of logging: And the backtrace: It seems that Planify is trying to play a sound on completion ( in 4.7, so this could have been introduced by ), but fails because it's missing a part of GStreamer. & system: host os: multi-user?: sandbox: version: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Going to "Preferences Task Settings" and disabling "Task Complete Tone" does prevent the app from crashing.
Thanks for the issue. Looks like it crashes when doing .
Change:
<ins> { lib , stdenv , fetchFromGitHub , fetchYarnDeps , makeWrapper , nodejs , prefetch-yarn-deps , yarn }: stdenv.mkDerivation (finalAttrs: { pname = "node-hp-scan-to"; version = "1.4.2"; src = fetchFromGitHub { owner = "manuc66"; repo = "node-hp-scan-to"; rev = "v${finalAttrs.version}"; hash = "sha256-/aoR2ccDYTkdmcj4k2zf8VJydQufZ2ucqyZ1OH9jRt0="; }; offlineCache = fetchYarnDeps { yarnLock = "${finalAttrs.src}/yarn.lock"; hash = "sha256-Mhlw/3js35TOVDADsPScE9kfv9rmF+u1LzDmKkzunM0="; }; nativeBuildInputs = [ makeWrapper nodejs prefetch-yarn-deps yarn ]; configurePhase = '' runHook preConfigure export HOME=$(mktemp -d) yarn config --offline set yarn-offline-mirror $offlineCache fixup-yarn-lock yarn.lock yarn --offline --frozen-lockfile --ignore-platform --ignore-scripts --no-progress --non-interactive install patchShebangs node_modules runHook postConfigure ''; buildPhase = '' runHook preBuild yarn --offline build runHook postBuild ''; installPhase = '' runHook preInstall yarn --offline --production install mkdir -p "$out/lib/node_modules/node-hp-scan-to" cp -r dist node_modules package.json "$out/lib/node_modules/node-hp-scan-to" makeWrapper "${nodejs}/bin/node" "$out/bin/node-hp-scan-to"  --add-flags "$out/lib/node_modules/node-hp-scan-to/dist/index.js" runHook postInstall ''; meta = { changelog = "https://github.com/manuc66/node-hp-scan-to/releases/tag/${finalAttrs.src.rev}"; description = "Allow to send scan from device to computer for some HP All-in-One Printers"; homepage = "https://github.com/manuc66/node-hp-scan-to"; license = lib.licenses.mit; mainProgram = "node-hp-scan-to"; maintainers = with lib.maintainers; [ jonas-w ]; }; }) </ins>

Discussion:
Project description Allow to send scan from device to computer for some HP All-in-One Printers. Useful to directly put scans into paperless-ngx, from the scanner itself. Metadata homepage URL: source URL: license: MIT platforms: Linux, Windows, macOS, Docker Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
in buildFHSEnv { <del> inherit pname version; </del> <ins> inherit (decent-sampler) pname version; </ins> targetPkgs = pkgs: [ alsa-lib

Discussion:
Decent Sampler is supposed to have a standalone app, a VST2 plugin and a VST3 plugin. The package decent-sampler installs only the standalone app. The downloaded archive contains also which is the VST2 plugin and the directory which is the VST3 plugin. Steps to reproduce the behavior: decent-sampler. for the VST plugins 't find them. The VST3 plugin should be installed in of the package and the VST2 plugin too should be in the package, but I don't know where exactly. <!-- 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. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
bluez-tools cinnamon.xapp gnome.gnome-bluetooth_1_0 <ins> libnotify </ins> python3Packages.python util-linux ];

Discussion:
I get an error message when trying to exectute the autostart dektop file . Steps to reproduce the behavior: results Desktop file should be runnable without any problem. I ran into this because I wanted to autostart all my applications that follow the xdg-autostart specification. For this, I used the program dex. When it tried to autostart all the applications following xdg-autostart, it got this error when it tried to start everything. Additional thoughts Should the two autostart files really be enabled by default, without any option to turn them off? Maybe add a NixOS module with the option to enable the two desktop file separately and default to have them disabled? Because I do not think installing a package should automatically autostart a program, just because the system is following xdg-autostart. <!-- 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. `
Should have been fixed by
Change:
homepage = "https://github.com/tillson/git-hound"; license = with licenses; [ mit ]; maintainers = with maintainers; [ fab ]; <del> broken = true; # vendor isn't reproducible with go > 1.17: nix-build -A $name.goModules --check </del> <ins> mainProgram = "git-hound"; </ins> }; }

Discussion:
Package name: git-hound Latest released version: 1.7.2 <!-- Search your package here: --- Current version on the unstable channel: 1.4 Current version on the stable/release channel: 1.4 <!-- 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. Try to check if it solves the current broken build. Can the update be applied also on stable repository? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> { lib, buildPythonPackage, fetchFromGitHub, backoff, httpx, idna, langchain, llama-index, openai, packaging, poetry-core, pydantic, pythonRelaxDepsHook, wrapt, }: buildPythonPackage rec { pname = "langfuse"; version = "2.33.1"; pyproject = true; src = fetchFromGitHub { owner = "langfuse"; repo = "langfuse-python"; rev = "refs/tags/v${version}"; hash = "sha256-ZPCL3Xle4qEw2pNIcja252meep26W/RbVEk2suzywYI="; }; build-system = [ poetry-core ]; nativeBuildInputs = [ pythonRelaxDepsHook ]; pythonRelaxDeps = [ "packaging" ]; dependencies = [ backoff httpx idna packaging pydantic wrapt ]; optional-dependencies = { langchain = [ langchain ]; llama-index = [ llama-index ]; openai = [ openai ]; }; pythonImportsCheck = [ "langfuse" ]; # tests require network access and openai api key doCheck = false; meta = { description = "Instrument your LLM app with decorators or low-level SDK and get detailed tracing/observability"; homepage = "https://github.com/langfuse/langfuse-python"; changelog = "https://github.com/langfuse/langfuse-python/releases/tag/${src.rev}"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ natsukium ]; }; } </ins>

Discussion:
Project description Instrument your LLM app with decorators or low-level SDK and get detailed tracing/observability. Works with any LLM or framework <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
appdirs attrs click <ins> colorama </ins> mypy-extensions pathspec regex toml <del> typed-ast typing-extensions ] ++ lib.optional (pythonOlder "3.7") dataclasses; </del> <ins> typed-ast # required for tests and python2 extra uvloop ] ++ lib.optional (pythonOlder "3.7") dataclasses ++ lib.optional (pythonOlder "3.8") typing-extensions; </ins> meta = with lib; { description = "The uncompromising Python code formatter"; <del> homepage    = "https://github.com/psf/black"; changelog   = "https://github.com/psf/black/blob/${version}/CHANGES.md"; license     = licenses.mit; </del> <ins> homepage = "https://github.com/psf/black"; changelog = "https://github.com/psf/black/blob/${version}/CHANGES.md"; license = licenses.mit; </ins> maintainers = with maintainers; [ sveitser ]; }; }

Discussion:
Describe the bug Fails during tests on unstable channel: Seems to be caused by To Reproduce Steps to reproduce the behavior: Expected behavior Build succeeds. Notify maintainers Metadata Maintainer information:
May be hitting this:
Simply adding makes the test pass and the build succeed.
Change:
<ins> --- a/Cargo.lock +++ b/Cargo.lock @@ -1,5 +1,7 @@ # This file is automatically @generated by Cargo. # It is not intended for manual editing. +version = 3 + [[package]] name = "adler32" version = "1.2.0" @@ -530,13 +532,13 @@ checksum = "830d08ce1d1d941e6b30645f1a0eb5643013d835ce3779a5fc208261dbe10f55" [[package]] name = "lexical-core" -version = "0.7.4" +version = "0.7.6" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "db65c6da02e61f55dae90a0ae427b2a5f6b3e8db09f58d10efab23af92592616" +checksum = "6607c62aa161d23d17a9072cc5da0be67cdfc89d3afb1e8d9c842bebc2525ffe" dependencies = [ "arrayvec", "bitflags 1.2.1", - "cfg-if 0.1.10", + "cfg-if 1.0.0", "ryu", "static_assertions", ] </ins>

Discussion:
this is due to supertag using an old version of lexical-core which is incompatible with new versions of rust, which is fixed upstream in rust-lexical , but supertag hasn't updated its dependencies and made a new release yet A easy fix would be to patch its to use a newer version of lexical-core if anyone is interested
Change:
, lib , numpy , pytestCheckHook <ins> , tensorflow , tensorflow-datasets </ins> }: buildPythonPackage rec { pname = "optax"; <del> # As of 2022-01-06, the latest stable version (0.1.0) has broken tests that are fixed # in https://github.com/deepmind/optax/commit/d6633365d84eb6f2c0df0c52b630481a349ce562 version = "unstable-2022-01-05"; </del> <ins> version = "0.1.1"; </ins> src = fetchFromGitHub { owner = "deepmind"; repo = pname; <del> rev = "5ec5541b3486224b22e950480ff639ceaf5098f7"; sha256 = "1q8cxc42a5xais2ll1l238cnn3l7w28savhgiz0lg01ilz2ysbli"; </del> <ins> rev = "v${version}"; hash = "sha256-s/BcqzhdfWzR61MStusUPQtuT4+t8NcC5gBGiGggFqw="; </ins> }; buildInputs = [ jaxlib ];

Discussion:
Build of failed on x86_64-linux as of . Maintainer cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag: