jiebi/CodeConvo huggingface dataset:
Code change:
Project description WebUI service for Large Language Models Video demonstration by : .. basically self-hostable ChatGPT-like service Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Additional info Follow-up on for open-webui nixos module. There seems to be an ongoing work on the subject by and on Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Relevant Merge Request:
Just for reference / workaround here's another nix package:
Thanks for that reference. That pdm tool workaround looks a lot more maintainable for the Python backend. Maybe i'll have time to try another PR in the next weeks. In the meantime and as a much simpler UI i packaged as part of PR It would be great if someone could review it.
I would like to mention that in the latest release switched to , I am not sure of any straightforward way to do this while packaging it for .
I just tested your flake, it's impressive, especially the nice UI at the end showing all the processes ! Regarding open-webui, it would be so nice to have that in !!!
Thank you, planning to have more UIs and devShell integration (for CLI tools that interact with ollama). I would love that too! Although there are a few challenges (like the one I pointed above regarding ), I am willing to contribute here. Also, maintainers are quick to respond, in case we need any upstream contributions to make it happen.

Related discussion:
text: <ins> { lib, ... }: let mainPort = "8080"; in { name = "open-webui"; meta = with lib.maintainers; { maintainers = [ shivaraj-bh ]; }; nodes = { machine = { ... }: { services.open-webui = { enable = true; environment = { # Requires network connection RAG_EMBEDDING_MODEL = ""; }; }; }; }; testScript = '' machine.start() machine.wait_for_unit("open-webui.service") machine.wait_for_open_port(${mainPort}) machine.succeed("curl http://127.0.0.1:${mainPort}") ''; } </ins>
Code change:
If you have: During evaluation I get this error , pointing to the line Steps to reproduce the behavior: As described above I think this is because here The pairs are made using the , while here: It is trying to use the vhostName. So I think it should be Also, maybe this could be a problem as well, however I am not sure: I would submit a MR, but embarrassingly, I couldn't figure out how to test a patched nixpkgs lib in a flake without having my whole system rebuilt. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Broken by . Fixed by .

Related discussion:
text: # The acme-challenge location doesn't need to be added if we are not using any automated # certificate provisioning and can also be omitted when we use a certificate obtained via a DNS-01 challenge <del> acmeName = if vhost.useACMEHost != null then vhost.useACMEHost else vhostName; </del> <ins> acmeName = if vhost.useACMEHost != null then vhost.useACMEHost else vhost.serverName; </ins> acmeLocation = optionalString ((vhost.enableACME || vhost.useACMEHost != null) && config.security.acme.certs.${acmeName}.dnsProvider == null) # Rule for legitimate ACME Challenge requests (like /.well-known/acme-challenge/xxxxxxxxx) # We use ^~ here, so that we don't check any regexes (which could
Code change:
If you have: During evaluation I get this error , pointing to the line Steps to reproduce the behavior: As described above I think this is because here The pairs are made using the , while here: It is trying to use the vhostName. So I think it should be Also, maybe this could be a problem as well, however I am not sure: I would submit a MR, but embarrassingly, I couldn't figure out how to test a patched nixpkgs lib in a flake without having my whole system rebuilt. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Broken by . Fixed by .

Related discussion:
text: serverAliases = [ "${server}-wildcard-alias.example.test" ]; useACMEHost = "example.test"; }; <del> }; </del> <ins> } // (lib.optionalAttrs (server == "nginx") { # The nginx module supports using a different key than the hostname different-key = vhostBaseData // { serverName = "${server}-different-key.example.test"; serverAliases = [ "${server}-different-key-alias.example.test" ]; enableACME = true; }; }); </ins> }; # Used to determine if service reload was triggered
Code change:
If you have: During evaluation I get this error , pointing to the line Steps to reproduce the behavior: As described above I think this is because here The pairs are made using the , while here: It is trying to use the vhostName. So I think it should be Also, maybe this could be a problem as well, however I am not sure: I would submit a MR, but embarrassingly, I couldn't figure out how to test a patched nixpkgs lib in a flake without having my whole system rebuilt. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Broken by . Fixed by .

Related discussion:
text: webserver.succeed("systemctl restart caddy.service") check_connection_key_bits(client, "a.example.test", "384") <del> domains = ["http", "dns", "wildcard"] for server, logsrc in [ ("nginx", "journalctl -n 30 -u nginx.service"), ("httpd", "tail -n 30 /var/log/httpd/*.log"), </del> <ins> common_domains = ["http", "dns", "wildcard"] for server, logsrc, domains in [ ("nginx", "journalctl -n 30 -u nginx.service", common_domains + ["different-key"]), ("httpd", "tail -n 30 /var/log/httpd/*.log", common_domains), </ins> ]: wait_for_server = lambda: webserver.wait_for_unit(f"{server}.service") with subtest(f"Works with {server}"): try: switch_to(webserver, server) <del> # Skip wildcard domain for this check ([:-1]) for domain in domains[:-1]: webserver.wait_for_unit( f"acme-finished-{server}-{domain}.example.test.target" ) </del> <ins> for domain in domains: if domain != "wildcard": webserver.wait_for_unit( f"acme-finished-{server}-{domain}.example.test.target" ) </ins> except Exception as err: _, output = webserver.execute( f"{logsrc} && ls -al /var/lib/acme/acme-challenge"
Code change:
If you have: During evaluation I get this error , pointing to the line Steps to reproduce the behavior: As described above I think this is because here The pairs are made using the , while here: It is trying to use the vhostName. So I think it should be Also, maybe this could be a problem as well, however I am not sure: I would submit a MR, but embarrassingly, I couldn't figure out how to test a patched nixpkgs lib in a flake without having my whole system rebuilt. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Broken by . Fixed by .

Related discussion:
text: wait_for_server() <del> for domain in domains[:-1]: check_issuer(webserver, f"{server}-{domain}.example.test", "pebble") </del> <ins> for domain in domains: if domain != "wildcard": check_issuer(webserver, f"{server}-{domain}.example.test", "pebble") </ins> for domain in domains: check_connection(client, f"{server}-{domain}.example.test") check_connection(client, f"{server}-{domain}-alias.example.test")
Code change:
The patched version of Ardour in nixpkgs is not able to open VST2 audio plugins also installed from nixpkgs. All VST2 plugins are detected, but say they can’t be opened by Ardour. For example, having installed the ardour and lsp-plugins nixpkgs packages, the Ardour plugin manager shows the status “Error”: ! The error given for one of the VST2 plugins is: Steps to reproduce the behavior: Ardour and some VST2 plugins from nixpkgs (e.g. "ardour" and "lsp-plugins" packages) Ardour and scan for plugins The plugins are detected and can be used. I'm running NixOS 23.11 and installing these things declaratively with home-manager. i.e.: <!-- 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]:
I suspect is not actually a plugin, but a shared library used by the plugins in the same directory like which loads fine for me: Are you sure the actual plugins are affected? !
I tested with and and I was able to see both of those, but I'm able to reproduce other vst2 plugins (like LSP) not showing. Could it be that they're not in ardour's vst2 scan path? !
nixpkgs patches Ardour to find other plugin types, but I think i've to the plugin search path manually.
Hi guys, thanks for taking the time to look into this issue. You're right about the shared library not being a plugin - this was a red herring that was stopping me from understanding the problem. I just to my plugin search path and everything I was missing has now loaded in successfully. Thank you! To prevent other users from experiencing this problem (and possibly me if I change systems and forget this fix), can this path be to the list that the nixpkgs patch adds to ardour?

Related discussion:
text: lxvst_path = "/usr/local/lib64/lxvst:/usr/local/lib/lxvst:/usr/lib64/lxvst:/usr/lib/lxvst:" "/usr/local/lib64/linux_vst:/usr/local/lib/linux_vst:/usr/lib64/linux_vst:/usr/lib/linux_vst:" -			"/usr/lib/vst:/usr/local/lib/vst"; <del> +			"/usr/lib/vst:/usr/local/lib/vst:" </del> <ins> +			"/usr/lib/vst:/usr/local/lib/vst:$HOME/.nix-profile/lib/vst:" </ins> +			"$HOME/.lxvst:$HOME/.nix-profile/lib/lxvst:/run/current-system/sw/lib/lxvst:/etc/profiles/per-user/$USER/lib/lxvst"; }
Code change:
looking over broken python packages for ZHF and pixel-font-builder is missing a python module and needs a dependency relaxed. Steps to reproduce the behavior: *pixel-font-builder" pcffont not part of nixpkgs would add it but no longer a maintainer <!-- 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]:

Related discussion:
text: python312Packages.buildPythonPackage rec { pname = "ark-pixel-font"; <del> version = "2024.04.05"; </del> <ins> version = "2024.05.12"; </ins> src = fetchFromGitHub { owner = "TakWolf"; <del> repo = pname; rev = version; hash = "sha256-G34cu/mSt/p8UPJt+Q1T2qy6d9LGgT1Jslt9syRz5eo="; </del> <ins> repo = "ark-pixel-font"; rev = "refs/tags/${version}"; hash = "sha256-PGhhKWHDpvOqa3vaI40wuIsAEdWGb62cN7QJeHQqiss="; </ins> }; format = "other";
Code change:
looking over broken python packages for ZHF and pixel-font-builder is missing a python module and needs a dependency relaxed. Steps to reproduce the behavior: *pixel-font-builder" pcffont not part of nixpkgs would add it but no longer a maintainer <!-- 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]:

Related discussion:
text: buildPythonPackage rec { pname = "bdffont"; <del> version = "0.0.20"; </del> <ins> version = "0.0.24"; </ins> disabled = pythonOlder "3.11"; src = fetchPypi { inherit pname version; <del> hash = "sha256-T0gTtudsZmL0VZ3a3+C/v+dWAwbXUgf0PEdNtkxWROw="; </del> <ins> hash = "sha256-3HJwtBV78zsMUlmwJrPj74Vd5cru1zflvies5mNGcy4="; </ins> }; format = "pyproject";
Code change:
looking over broken python packages for ZHF and pixel-font-builder is missing a python module and needs a dependency relaxed. Steps to reproduce the behavior: *pixel-font-builder" pcffont not part of nixpkgs would add it but no longer a maintainer <!-- 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]:

Related discussion:
text: <ins> { lib , buildPythonPackage , fetchFromGitHub , hatchling , bdffont , pytestCheckHook , nix-update-script }: buildPythonPackage rec { pname = "pcffont"; version = "0.0.11"; pyproject = true; src = fetchFromGitHub { owner = "TakWolf"; repo = "pcffont"; rev = "refs/tags/${version}"; hash = "sha256-gu9niWxYTw3rcA++z8B+MdKp5XaqAGjmvd+PdSDosfg="; }; build-system = [ hatchling ]; dependencies = [ bdffont ]; nativeCheckInputs = [ pytestCheckHook ]; pythonImportsCheck = [ "pcffont" ]; passthru.updateScript = nix-update-script { }; meta = { description = "Library for manipulating Portable Compiled Format (PCF) fonts"; homepage = "https://github.com/TakWolf/pcffont"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ ]; }; } </ins>
Code change:
looking over broken python packages for ZHF and pixel-font-builder is missing a python module and needs a dependency relaxed. Steps to reproduce the behavior: *pixel-font-builder" pcffont not part of nixpkgs would add it but no longer a maintainer <!-- 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]:

Related discussion:
text: , brotli , fonttools , pypng <ins> , pcffont , pythonRelaxDepsHook </ins> }: buildPythonPackage rec { pname = "pixel-font-builder"; <del> version = "0.0.19"; </del> <ins> version = "0.0.24"; pyproject = true; </ins> disabled = pythonOlder "3.11"; src = fetchPypi { pname = "pixel_font_builder"; inherit version; <del> hash = "sha256-f38DyM5hojHfv8k/W6kcHxbOjz43hHW6i4Scm6NbHiQ="; </del> <ins> hash = "sha256-hBlTTIPx4TRgeXapVnSaKPUwseR3uYT0gcgKLGmmSZI="; </ins> }; <del> format = "pyproject"; </del> <ins> pythonRelaxDeps = [ "fonttools" ]; </ins> nativeBuildInputs = [ <ins> pythonRelaxDepsHook ]; build-system = [ </ins> hatch-vcs hatchling ];
Code change:
looking over broken python packages for ZHF and pixel-font-builder is missing a python module and needs a dependency relaxed. Steps to reproduce the behavior: *pixel-font-builder" pcffont not part of nixpkgs would add it but no longer a maintainer <!-- 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]:

Related discussion:
text: pypng ]; <del> propagatedBuildInputs = [ </del> <ins> dependencies = [ </ins> bdffont brotli fonttools <ins> pcffont </ins> ]; passthru.updateScript = nix-update-script { };
Code change:
looking over broken python packages for ZHF and pixel-font-builder is missing a python module and needs a dependency relaxed. Steps to reproduce the behavior: *pixel-font-builder" pcffont not part of nixpkgs would add it but no longer a maintainer <!-- 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]:

Related discussion:
text: paddlepaddle = callPackage ../development/python-modules/paddlepaddle { }; <ins> pcffont = callPackage ../development/python-modules/pcffont { }; </ins> pueblo = callPackage ../development/python-modules/pueblo { }; pulumi = callPackage ../development/python-modules/pulumi { inherit (pkgs) pulumi; };
Code change:
Project description Utility to activate iPhones Metadata homepage URL: source URL: license: lgpl-2.1, GPL-3.0 platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: githubId = 199180; name = "Claes Wallin"; }; <ins> clebs = { email = "borja.clemente@gmail.com"; github = "clebs"; githubId = 1059661; name = "Borja Clemente"; keys = [{ fingerprint = "C4E1 58BD FD33 3C77 B6C7  178E 2539 757E F64C 60DD"; }]; }; </ins> cleeyv = { email = "cleeyv@riseup.net"; github = "cleeyv";
Code change:
Project description Utility to activate iPhones Metadata homepage URL: source URL: license: lgpl-2.1, GPL-3.0 platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <ins> { stdenv, fetchFromGitHub, lib, pkg-config, automake, autoreconfHook, libtool, libplist, libimobiledevice, libxml2, curl, usbmuxd, }: stdenv.mkDerivation (finalAttrs: { pname = "libideviceactivation"; version = "1.1.1"; src = fetchFromGitHub { owner = "libimobiledevice"; repo = "libideviceactivation"; rev = "refs/tags/${finalAttrs.version}"; hash = "sha256-owcQpCN4+A785oy9pCboJIyfpgZ6X+8PRzqGtWpYl2w="; }; nativeBuildInputs = [ pkg-config automake autoreconfHook ]; buildInputs = [ libtool libplist libimobiledevice libxml2 curl usbmuxd ]; installFlags = [ "PREFIX=$(out)" ]; meta = { description = "A library to manage the activation process of Apple iOS devices."; homepage = "https://libimobiledevice.org"; license = with lib.licenses; [ lgpl21 gpl3 ]; mainProgram = "ideviceactivation"; platforms = lib.platforms.linux; maintainers = with lib.maintainers; [ clebs ]; }; }) </ins>
Code change:
Open a C++ project in vscode with the extension installed and see the following in the Extension Host output window: Steps to reproduce the behavior: a C++ project in vscode with the extension installed how autocompletion etc. features do not activate. to the output window and select the Extension Host and you will see the following: The extension should work ! Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I'm wondering if that should be 0555 instead of 0444.
Adding to got me around this particular issue but now I'm running into which should be resolved by moving to 1.20.5
Moving to 1.20.5 doesn't fix the startup issue
I'm replying to your comment here I can reproduce this with the following: Attached is the flake I end up with. My system packages are the following:
After changing the permission of this is what I get: If instead I run through manually I make some progress (it's looking for in my home directory) and it exits.
This is most likely

Related discussion:
text: stdenv.cc.cc.lib ]; <ins> dontAutoPatchelf = true; </ins> postPatch = '' mv ./package.json ./package_orig.json
Code change:
Open a C++ project in vscode with the extension installed and see the following in the Extension Host output window: Steps to reproduce the behavior: a C++ project in vscode with the extension installed how autocompletion etc. features do not activate. to the output window and select the Extension Host and you will see the following: The extension should work ! Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I'm wondering if that should be 0555 instead of 0444.
Adding to got me around this particular issue but now I'm running into which should be resolved by moving to 1.20.5
Moving to 1.20.5 doesn't fix the startup issue
I'm replying to your comment here I can reproduce this with the following: Attached is the flake I end up with. My system packages are the following:
After changing the permission of this is what I get: If instead I run through manually I make some progress (it's looking for in my home directory) and it exits.
This is most likely

Related discussion:
text: touch "./install.lock" # Clang-format from nix package. <del> mv ./LLVM/ ./LLVM_orig </del> <ins> rm -rf ./LLVM </ins> mkdir "./LLVM/" find "${clang-tools}" -mindepth 1 -maxdepth 1 | xargs ln -s -t "./LLVM" # Patching binaries <del> chmod +x bin/cpptools bin/cpptools-srv bin/cpptools-wordexp debugAdapters/bin/OpenDebugAD7 </del> <ins> chmod +x bin/cpptools bin/cpptools-srv bin/cpptools-wordexp bin/libc.so debugAdapters/bin/OpenDebugAD7 </ins> patchelf --replace-needed liblttng-ust.so.0 liblttng-ust.so.1 ./debugAdapters/bin/libcoreclrtraceptprovider.so ''; <del> postFixup = lib.optionalString gdbUseFixed '' wrapProgram $out/share/vscode/extensions/ms-vscode.cpptools/debugAdapters/bin/OpenDebugAD7 --prefix PATH : ${lib.makeBinPath [ gdb ]} ''; </del> <ins> postFixup = '' autoPatchelf $out/share/vscode/extensions/ms-vscode.cpptools/debugAdapters # cpptools* are distributed by the extension and need to be run through the distributed musl interpretter patchelf --set-interpreter $out/share/vscode/extensions/ms-vscode.cpptools/bin/libc.so $out/share/vscode/extensions/ms-vscode.cpptools/bin/cpptools patchelf --set-interpreter $out/share/vscode/extensions/ms-vscode.cpptools/bin/libc.so $out/share/vscode/extensions/ms-vscode.cpptools/bin/cpptools-srv patchelf --set-interpreter $out/share/vscode/extensions/ms-vscode.cpptools/bin/libc.so $out/share/vscode/extensions/ms-vscode.cpptools/bin/cpptools-wordexp '' + lib.optionalString gdbUseFixed '' wrapProgram $out/share/vscode/extensions/ms-vscode.cpptools/debugAdapters/bin/OpenDebugAD7 --prefix PATH : ${lib.makeBinPath [ gdb ]} ''; </ins> meta = { description = "The C/C++ extension adds language support for C/C++ to Visual Studio Code, including features such as IntelliSense and debugging.";
Code change:
The following example in the python docs does not work since on the second line is supposed to be the interpreter and is for the packages: The fix is simply: System: 18.03pre118631. Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: 18.03pre118631. Sandboxing enabled: false

Related discussion:
text: ```py #! /usr/bin/env nix-shell <del> #! nix-shell -i 'python3.withPackages(ps: [ps.numpy])' </del> <ins> #! nix-shell -i python3 -p 'python3.withPackages(ps: [ps.numpy])' </ins> import numpy
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: , fetchFromGitHub , fetchpatch , installShellFiles <ins> , wrapGAppsNoGuiHook , gobject-introspection </ins> , libcdio-paranoia , cdrdao , libsndfile <ins> , glib </ins> , flac , sox , util-linux
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: nativeBuildInputs = with python3.pkgs; [ installShellFiles <ins> wrapGAppsNoGuiHook gobject-introspection </ins> setuptools-scm docutils
Code change:
When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

Related discussion:
text: setuptools ]; <del> buildInputs = [ libsndfile ]; </del> <ins> buildInputs = [ libsndfile glib ]; </ins> nativeCheckInputs = with python3.pkgs; [ twisted