jiebi/CodeConvo huggingface dataset:
Code change:
Ansel installs well, and can be launch from console with … but it does not appear in Gnome’s application menu, nor it cannot be find in Gnome launcher search Steps to reproduce the behavior: to from channel 24.05 or from unstable to launch it or to find it in applications menu Like every other application (and Darktable), I expect to find Ansel in the application menu, launcher search, and so on
I don't know anything about gnome, but there's definitely a desktop file in the correct spot: also, is a bot, FYI Probably try rebooting or something.
The desktop file is broken: Sounds like the upstream build system is broken – see
Good catch, thanks. I've sent a PR

Related discussion:
text: fetchSubmodules = true; }; <ins> patches = [ # don't use absolute paths to binary or icon - see https://github.com/NixOS/nixpkgs/issues/308324 ./fix-desktop-file.patch ]; </ins> strictDeps = true; nativeBuildInputs = [
Code change:
I believe converted the following generated line of Bash: into: , so it's , and is the empty string; but when escaped, it became . The result is that the passthru does not generate a lockfile. After I manually change the two into in the definitions of and , I successfully start getting a NuGet restore. Failing passthru: Add any other context about the problem here. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hm, that is weird. Note that cannot be null.
This should be (plural). Introduced in .
I even checked the implementation of and discovered that it's secretly a function rather than as documented, and didn't make the connection. I clearly need to go to sleep.

Related discussion:
text: else ''$(mktemp -t "${pname}-deps-XXXXXX.nix")''; storeSrc = srcOnly args; <del> projectFileStr = lib.escapeShellArg projectFiles; testProjectFileStr = lib.escapeShellArg testProjectFiles; </del> <ins> projectFileStr = lib.escapeShellArgs projectFiles; testProjectFileStr = lib.escapeShellArgs testProjectFiles; </ins> path = lib.makeBinPath [ coreutils runtimeShellPackage
Code change:
Package name: wasm-pack Latest released version: 0.13.0 <!-- Search your package here: --- Current version on the unstable channel: 0.12.1 Current version on the stable/release channel: 0.12.1 <!-- 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. I just tried to make a PR with the change, but I got when I tried to build (while compiling ), and used all of my RAM while running (it did not finish). I'm using a x86-64 machine with Debian.
I encountered that error too. After reading I tried this: That resulted in a new error log. I don't know what to do but I thought I'll leave it here in the case that I could be useful to someone else

Related discussion:
text: <del> { lib , stdenv , fetchFromGitHub , rustPlatform , darwin </del> <ins> { lib, stdenv, fetchFromGitHub, rustPlatform, darwin, cmake, pkg-config, zstd, </ins> }: rustPlatform.buildRustPackage rec { pname = "wasm-pack"; <del> version = "0.12.1"; </del> <ins> version = "0.13.0"; </ins> src = fetchFromGitHub { owner = "rustwasm"; repo = "wasm-pack"; rev = "refs/tags/v${version}"; <del> hash = "sha256-L4mCgUPG4cgTUpCoaIUOTONBOggXn5vMyPKj48B3MMk="; </del> <ins> hash = "sha256-NEujk4ZPQ2xHWBCVjBCD7H6f58P4KrwCNoDHKa0d5JE="; </ins> }; <del> cargoHash = "sha256-mqQRQXaUW6mreE7UUEA0zhhaaGGKLRUngH9QLxcaIdY="; </del> <ins> cargoHash = "sha256-pFKGQcWW1/GaIIWMyWBzts4w1hMu27hTG/uUMjkfDMo="; </ins> <del> buildInputs = lib.optional stdenv.isDarwin darwin.apple_sdk.frameworks.Security; </del> <ins> nativeBuildInputs = [ cmake pkg-config ]; buildInputs = lib.optional stdenv.isDarwin darwin.apple_sdk.frameworks.Security ++ [ zstd ]; </ins> # Most tests rely on external resources and build artifacts. # Disabling check here to work with build sandboxing.
Code change:
Package name: wasm-pack Latest released version: 0.13.0 <!-- Search your package here: --- Current version on the unstable channel: 0.12.1 Current version on the stable/release channel: 0.12.1 <!-- 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. I just tried to make a PR with the change, but I got when I tried to build (while compiling ), and used all of my RAM while running (it did not finish). I'm using a x86-64 machine with Debian.
I encountered that error too. After reading I tried this: That resulted in a new error log. I don't know what to do but I thought I'll leave it here in the case that I could be useful to someone else

Related discussion:
text: description = "Utility that builds rust-generated WebAssembly package"; mainProgram = "wasm-pack"; homepage = "https://github.com/rustwasm/wasm-pack"; <del> license = with licenses; [ asl20 /* or */ mit ]; </del> <ins> license = with licenses; [ asl20 # or mit ]; </ins> maintainers = [ maintainers.dhkl ]; }; }
Code change:
Package name: Latest released version: 1.4.3 Current version on the unstable channel: 1.4.2-1-unstable-2024-07-10 Current version on the stable/release channel: none 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]:

Related discussion:
text: meta.homepage = "https://github.com/mkasa/lushtags/"; }; <del> lz-n = buildNeovimPlugin { pname = "lz.n"; version = "2024-07-10"; src = fetchFromGitHub { owner = "nvim-neorocks"; repo = "lz.n"; rev = "3d36b6848fc67f6a13d2a52cf4f96fd3403c0c43"; sha256 = "11ic8hylck3dvlp6d9kzblingbi167j2kcid155x4hpc2hhqf2aj"; }; meta.homepage = "https://github.com/nvim-neorocks/lz.n/"; }; </del> magma-nvim-goose = buildVimPlugin { pname = "magma-nvim-goose"; version = "2023-07-04";
Code change:
Package name: Latest released version: 1.4.3 Current version on the unstable channel: 1.4.2-1-unstable-2024-07-10 Current version on the stable/release channel: none 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]:

Related discussion:
text: dependencies = with self; [ luaPackages.jsregexp ]; }; <ins> lz-n = neovimUtils.buildNeovimPlugin { luaAttr = "lz-n"; }; </ins> magma-nvim-goose = buildVimPlugin { pname = "magma-nvim-goose"; version = "2023-03-13";
Code change:
Package name: Latest released version: 1.4.3 Current version on the unstable channel: 1.4.2-1-unstable-2024-07-10 Current version on the stable/release channel: none 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]:

Related discussion:
text: https://github.com/alvarosevilla95/luatab.nvim/,, https://github.com/rktjmp/lush.nvim/,, https://github.com/mkasa/lushtags/,, <del> https://github.com/nvim-neorocks/lz.n/,, </del> https://github.com/WhiteBlackGoose/magma-nvim-goose/,HEAD, https://github.com/winston0410/mark-radar.nvim/,HEAD, https://github.com/iamcco/markdown-preview.nvim/,,
Code change:
doesn't seem to work as a module Steps to reproduce the behavior: livebook service any env variables or use environment file with any variables first of all, its systemd unit does not appear to start by default. so i did and but it doesn't work, i can't access it either by IP or by domain, which is set up in my nginx configuration as a reverse proxy. some strange things happen while the unit is active [1st screenshot]. also there's nothing in the journal except info messages about the unit itself as i see it, livebook fails to start, but the service is active because something is going on with inside this wrapper script i tried to make it work several different ways: from using option instead of my environment file to writing my very own systemd unit in NixOS configuration file, also using home-manager like so: but that doesn't work too. surely i tried starting livebook manually - and it works as expected [2nd screenshot] module/service works and is accessible systemd livebook unit works and is accessible |
---------------| NixOS 24.05.3214. (Uakari) x86_64 running on a VPS cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you for reporting this issue. I am ashamed to admit that I have actually known about this for a while now, without doing anything about it. Now that someone else is having problems with the service, I'll prioritize getting something done soon. I'm not actually sure what's going wrong, but it seems like the service hangs in the command. As far as I remember it ends up using 100% cpu and just loop forever. I'll try to take a look at it later this week.
Perhaps you have encountered this issue as well?
I've seen this before and I think it was because livebook was trying to generate a in some weird way. This is my current configuration which works: Could you try manually setting a in your service setup, please?
a screenshot from filtering cpu usage ! not so much is used i've tried setting up a cookie and you can see it works - :pleading_face: thanks!!!! ~<
The issue seems to have been described and debugged here: The solution is to set in the systemd service configuration. I'll mint a PR.

Related discussion:
text: githubId = 11587657; keys = [ { fingerprint = "E173 237A C782 296D 98F5  ADAC E13D FD4B 4712 7951"; } ]; }; <ins> scvalex = { name = "Alexandru Scvorțov"; email = "github@abstractbinary.org"; github = "scvalex"; githubId = 2588; }; </ins> sdaqo = { name = "sdaqo"; email = "sdaqo.dev@protonmail.com";
Code change:
doesn't seem to work as a module Steps to reproduce the behavior: livebook service any env variables or use environment file with any variables first of all, its systemd unit does not appear to start by default. so i did and but it doesn't work, i can't access it either by IP or by domain, which is set up in my nginx configuration as a reverse proxy. some strange things happen while the unit is active [1st screenshot]. also there's nothing in the journal except info messages about the unit itself as i see it, livebook fails to start, but the service is active because something is going on with inside this wrapper script i tried to make it work several different ways: from using option instead of my environment file to writing my very own systemd unit in NixOS configuration file, also using home-manager like so: but that doesn't work too. surely i tried starting livebook manually - and it works as expected [2nd screenshot] module/service works and is accessible systemd livebook unit works and is accessible |
---------------| NixOS 24.05.3214. (Uakari) x86_64 running on a VPS cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you for reporting this issue. I am ashamed to admit that I have actually known about this for a while now, without doing anything about it. Now that someone else is having problems with the service, I'll prioritize getting something done soon. I'm not actually sure what's going wrong, but it seems like the service hangs in the command. As far as I remember it ends up using 100% cpu and just loop forever. I'll try to take a look at it later this week.
Perhaps you have encountered this issue as well?
I've seen this before and I think it was because livebook was trying to generate a in some weird way. This is my current configuration which works: Could you try manually setting a in your service setup, please?
a screenshot from filtering cpu usage ! not so much is used i've tried setting up a cookie and you can see it works - :pleading_face: thanks!!!! ~<
The issue seems to have been described and debugged here: The solution is to set in the systemd service configuration. I'll mint a PR.

Related discussion:
text: EnvironmentFile = cfg.environmentFile; ExecStart = "${cfg.package}/bin/livebook start"; KillMode = "mixed"; <ins> # Fix for the issue described here: # https://github.com/livebook-dev/livebook/issues/2691 # # Without this, the livebook service fails to start and gets # stuck running a `cat /dev/urandom | tr | fold` pipeline. IgnoreSIGPIPE = false; </ins> }; environment = mapAttrs (name: value: if isBool value then boolToString value else toString value)
Code change:
doesn't seem to work as a module Steps to reproduce the behavior: livebook service any env variables or use environment file with any variables first of all, its systemd unit does not appear to start by default. so i did and but it doesn't work, i can't access it either by IP or by domain, which is set up in my nginx configuration as a reverse proxy. some strange things happen while the unit is active [1st screenshot]. also there's nothing in the journal except info messages about the unit itself as i see it, livebook fails to start, but the service is active because something is going on with inside this wrapper script i tried to make it work several different ways: from using option instead of my environment file to writing my very own systemd unit in NixOS configuration file, also using home-manager like so: but that doesn't work too. surely i tried starting livebook manually - and it works as expected [2nd screenshot] module/service works and is accessible systemd livebook unit works and is accessible |
---------------| NixOS 24.05.3214. (Uakari) x86_64 running on a VPS cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you for reporting this issue. I am ashamed to admit that I have actually known about this for a while now, without doing anything about it. Now that someone else is having problems with the service, I'll prioritize getting something done soon. I'm not actually sure what's going wrong, but it seems like the service hangs in the command. As far as I remember it ends up using 100% cpu and just loop forever. I'll try to take a look at it later this week.
Perhaps you have encountered this issue as well?
I've seen this before and I think it was because livebook was trying to generate a in some weird way. This is my current configuration which works: Could you try manually setting a in your service setup, please?
a screenshot from filtering cpu usage ! not so much is used i've tried setting up a cookie and you can see it works - :pleading_face: thanks!!!! ~<
The issue seems to have been described and debugged here: The solution is to set in the systemd service configuration. I'll mint a PR.

Related discussion:
text: }; }; <del> meta.doc = ./livebook.md; </del> <ins> meta = { doc = ./livebook.md; maintainers = with lib.maintainers; [ munksgaard scvalex ]; }; </ins> }
Code change:
doesn't seem to work as a module Steps to reproduce the behavior: livebook service any env variables or use environment file with any variables first of all, its systemd unit does not appear to start by default. so i did and but it doesn't work, i can't access it either by IP or by domain, which is set up in my nginx configuration as a reverse proxy. some strange things happen while the unit is active [1st screenshot]. also there's nothing in the journal except info messages about the unit itself as i see it, livebook fails to start, but the service is active because something is going on with inside this wrapper script i tried to make it work several different ways: from using option instead of my environment file to writing my very own systemd unit in NixOS configuration file, also using home-manager like so: but that doesn't work too. surely i tried starting livebook manually - and it works as expected [2nd screenshot] module/service works and is accessible systemd livebook unit works and is accessible |
---------------| NixOS 24.05.3214. (Uakari) x86_64 running on a VPS cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you for reporting this issue. I am ashamed to admit that I have actually known about this for a while now, without doing anything about it. Now that someone else is having problems with the service, I'll prioritize getting something done soon. I'm not actually sure what's going wrong, but it seems like the service hangs in the command. As far as I remember it ends up using 100% cpu and just loop forever. I'll try to take a look at it later this week.
Perhaps you have encountered this issue as well?
I've seen this before and I think it was because livebook was trying to generate a in some weird way. This is my current configuration which works: Could you try manually setting a in your service setup, please?
a screenshot from filtering cpu usage ! not so much is used i've tried setting up a cookie and you can see it works - :pleading_face: thanks!!!! ~<
The issue seems to have been described and debugged here: The solution is to set in the systemd service configuration. I'll mint a PR.

Related discussion:
text: enableUserService = true; environment = { LIVEBOOK_PORT = 20123; <del> LIVEBOOK_COOKIE = "chocolate chip"; LIVEBOOK_TOKEN_ENABLED = true; </del> }; environmentFile = pkgs.writeText "livebook.env" '' LIVEBOOK_PASSWORD = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
Code change:
doesn't seem to work as a module Steps to reproduce the behavior: livebook service any env variables or use environment file with any variables first of all, its systemd unit does not appear to start by default. so i did and but it doesn't work, i can't access it either by IP or by domain, which is set up in my nginx configuration as a reverse proxy. some strange things happen while the unit is active [1st screenshot]. also there's nothing in the journal except info messages about the unit itself as i see it, livebook fails to start, but the service is active because something is going on with inside this wrapper script i tried to make it work several different ways: from using option instead of my environment file to writing my very own systemd unit in NixOS configuration file, also using home-manager like so: but that doesn't work too. surely i tried starting livebook manually - and it works as expected [2nd screenshot] module/service works and is accessible systemd livebook unit works and is accessible |
---------------| NixOS 24.05.3214. (Uakari) x86_64 running on a VPS cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you for reporting this issue. I am ashamed to admit that I have actually known about this for a while now, without doing anything about it. Now that someone else is having problems with the service, I'll prioritize getting something done soon. I'm not actually sure what's going wrong, but it seems like the service hangs in the command. As far as I remember it ends up using 100% cpu and just loop forever. I'll try to take a look at it later this week.
Perhaps you have encountered this issue as well?
I've seen this before and I think it was because livebook was trying to generate a in some weird way. This is my current configuration which works: Could you try manually setting a in your service setup, please?
a screenshot from filtering cpu usage ! not so much is used i've tried setting up a cookie and you can see it works - :pleading_face: thanks!!!! ~<
The issue seems to have been described and debugged here: The solution is to set in the systemd service configuration. I'll mint a PR.

Related discussion:
text: machine.succeed("loginctl enable-linger alice") machine.wait_until_succeeds("${sudo} systemctl --user is-active livebook.service") <del> machine.wait_for_open_port(20123) </del> <ins> machine.wait_for_open_port(20123, timeout=10) </ins> machine.succeed("curl -L localhost:20123 | grep 'Type password'") '';
Code change:
doesn't seem to work as a module Steps to reproduce the behavior: livebook service any env variables or use environment file with any variables first of all, its systemd unit does not appear to start by default. so i did and but it doesn't work, i can't access it either by IP or by domain, which is set up in my nginx configuration as a reverse proxy. some strange things happen while the unit is active [1st screenshot]. also there's nothing in the journal except info messages about the unit itself as i see it, livebook fails to start, but the service is active because something is going on with inside this wrapper script i tried to make it work several different ways: from using option instead of my environment file to writing my very own systemd unit in NixOS configuration file, also using home-manager like so: but that doesn't work too. surely i tried starting livebook manually - and it works as expected [2nd screenshot] module/service works and is accessible systemd livebook unit works and is accessible |
---------------| NixOS 24.05.3214. (Uakari) x86_64 running on a VPS cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you for reporting this issue. I am ashamed to admit that I have actually known about this for a while now, without doing anything about it. Now that someone else is having problems with the service, I'll prioritize getting something done soon. I'm not actually sure what's going wrong, but it seems like the service hangs in the command. As far as I remember it ends up using 100% cpu and just loop forever. I'll try to take a look at it later this week.
Perhaps you have encountered this issue as well?
I've seen this before and I think it was because livebook was trying to generate a in some weird way. This is my current configuration which works: Could you try manually setting a in your service setup, please?
a screenshot from filtering cpu usage ! not so much is used i've tried setting up a cookie and you can see it works - :pleading_face: thanks!!!! ~<
The issue seems to have been described and debugged here: The solution is to set in the systemd service configuration. I'll mint a PR.

Related discussion:
text: license = licenses.asl20; homepage = "https://livebook.dev/"; description = "Automate code & data workflows with interactive Elixir notebooks"; <del> maintainers = with maintainers; [ munksgaard ]; </del> <ins> maintainers = with maintainers; [ munksgaard scvalex ]; </ins> platforms = platforms.unix; }; }
Code change:
Switcheroo fails with the error in the title. This does not happen in the Flatpak version (tested). (the formats might not matter, but I've specified them just in case) Steps to reproduce the behavior: a PNG file in Switcheroo to a JPEG file. the output filename. should happen. The image should convert without any errors. ! 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]:
Oops, I had in my path when I originally packaged and tested this. I have it as a dependency in and tested it with this time. Thank you for trying the flatpak and reporting it here first instead of upstream :slightlysmilingface:

Related discussion:
text: , fetchFromGitLab , glib , gtk4 <ins> , imagemagick </ins> , libadwaita , meson , ninja