jiebi/CodeConvo huggingface dataset:
Change:
, mock , sqlalchemy , pytestCheckHook <ins> , pythonOlder </ins> }: buildPythonPackage rec { <del> pname = "Flask-SQLAlchemy"; version = "3.0.2"; </del> <ins> pname = "flask-sqlalchemy"; version = "3.0.3"; </ins> format = "pyproject"; <ins> disabled = pythonOlder "3.9"; </ins> src = fetchPypi { <del> inherit pname version; hash = "sha256-FhmfWz3ftp4N8vUq5Mdq7b/sgjRiNJ2rshobLgorZek="; </del> <ins> pname = "Flask-SQLAlchemy"; inherit version; hash = "sha256-J2QzXzydfr3J7WBEr6+Yqun6UNegdM71Xd4wfslZA+w="; </ins> }; nativeBuildInputs = [

Discussion:
This also breaks the build of which relies on this package. () Please run and paste the result.
Are you using ihatemoney on unstable? I was considering dropping it as very often breaks with the new versions of its dependencies.
I wouldn't mind using ihatemoney from stable, but I'm using unstable by default on my system, and didn't manage to create a working overlay for overriding ihatemoney's version (a python-specific overlay is required, and then IIRC I got an error because ihatemoney is not a python module).
tbh I'm only maintaining it on stable. Overlaying all dependencies to make it work is time consuming so I'm only doing just before a release. If you want to have a try, here is how it can look like:
Change:
{ lib }: rec { <del> version = "1.27.0"; </del> <ins> version = "1.34.1"; </ins> <del> srcHash = "sha256-F6n3LQY4a5sO6c8SMQF9YjjgOS+v2SH+UQPwhg2EX7Q="; </del> <ins> srcHash = "sha256-jbwG3Xyb/rEyz7aR51/pfc+bU/KY9k6BsByZg6KDY5s="; </ins> # submodule dependencies # these are fetched so we:

Discussion:
Package name: Latest released version: 1.34.0 <!-- Search your package here: --- Current version on the unstable channel: 1.27.0 Current version on the stable/release channel: 1.27.0 <!-- 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.
Note: the update script isn't working on my system, I assume that's why has not uploaded any updates.
Ill take a look tomorrow :)
Change:
<ins> diff --git a/src/test/java/nl/altindag/crip/command/FileBaseTest.java b/src/test/java/nl/altindag/crip/command/FileBaseTest.java index 674ca10..f140601 100644 --- a/src/test/java/nl/altindag/crip/command/FileBaseTest.java +++ b/src/test/java/nl/altindag/crip/command/FileBaseTest.java @@ -26,7 +26,7 @@ import java.util.stream.Collectors; public class FileBaseTest extends BaseTest { -    protected static final Path TEMP_DIRECTORY = Paths.get(System.getProperty("user.home"), "certificate-ripper-temp"); +    protected static final Path TEMP_DIRECTORY = Paths.get(System.getenv("TMP"), "certificate-ripper-temp"); @BeforeEach void createTempDirAndClearConsoleCaptor() throws IOException { </ins>

Discussion:
A CLI tool to extract server certificates. Homepage: Source: License: Apache License 2.0 Platforms: Linux, macOS, Windows Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
makeWrapper $out/{Applications/$APP_NAME.app/Contents/MacOS,bin}/$APP_NAME ''; <ins> preFixup = '' qtWrapperArgs+=("''${gappsWrapperArgs[@]}") ''; </ins> meta = with lib; { description = "Featureful free software BitTorrent client"; homepage = "https://www.qbittorrent.org";

Discussion:
I encountered this error when attempting to open files from qBittorrent: It's working fine on . Steps to reproduce the behavior: Run nix shell nixpkgs#qbittorrent. Open qBittorrent. Navigate to Files -Add torrent files. The app crashes. It should open my File Manager. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Seems to be a case of the first error in the . Would you mind trying out
Change:
The password hash of user "${user.name}" may be invalid. You must set a valid hash or the user will be locked out of their account. Please check the value of option `users.users."${user.name}".hashedPassword`.'' <del> else null )); </del> <ins> else null) ++ flip mapAttrsToList cfg.users (name: user: if user.passwordFile != null then ''The option `users.users."${name}".passwordFile' has been renamed '' + ''to `users.users."${name}".hashedPasswordFile'.'' else null) ); </ins> }; }

Discussion:
Password hashes, while less sensitive than unhashed passwords, are secrets. We should therefore have a option in that avoids both placing the hashes in the store world-readable and storing the password unhashed.
This is a common misunderstanding due to the bad naming of these options: → string of plaintext password → string of password hash → file containing password hash So, what you want already exists and it's .
Oh wow, indeed. Thanks! Given that the option is named so confusingly and that its description starts with "The full path to a file that contains the user's password." I think we should keep the issue, pending an option rename and a documentation improvement.
Change:
python3Packages.pyqt5 ] ++ lib.optional (stdenv.hostPlatform.isi686 || stdenv.hostPlatform.isx86_64) vc; <del> NIX_CFLAGS_COMPILE = [ "-I${ilmbase.dev}/include/OpenEXR" ]; </del> <ins> NIX_CFLAGS_COMPILE = [ "-I${ilmbase.dev}/include/OpenEXR" ] ++ lib.optional stdenv.cc.isGNU "-Wno-deprecated-copy"; </ins> cmakeFlags = [ "-DPYQT5_SIP_DIR=${python3Packages.pyqt5}/share/sip/PyQt5"

Discussion:
Describe the bug The krita build on hydra fails since gcc 9.0 was introduced, because of the log size. Expected behavior Krita should be available on Additional context Krita builds: First failing build: Last log line: Probably introduced through these commits (use gcc 9 by default): I guess silencing some warnings could fix this. Maintainer information: cc
Change:
, fetchurl , pkgconfig <ins> , cmake </ins> , zlib , libjpeg

Discussion:
Describe the bug I am trying to build for . is one giving me difficulty. Originally I filed an issue on : But the issue is instead with the libpng inside freeimage: Basically, libpng applies an incorrect ARM optimization to aarch64 that isn't actually available. From briefly looking at in nixpkgs, it seems that we patch with patches (and skimming that, it looks like it has a relevant aarch64 patch). So, my goal is to patch the vendored inside FreeImage, similar to how we patch itself. So far I've not had luck. I've tried with both the CRLF and LF patches from the 'apng' project and the regular patch used from the 'libpng-apng' project that is used in nixpkg's libpng. They all fail to apply and some complain about line endings, regardless of if I pipe the patch through dos2unix (or unix2dos) or not.
I seem to have fixed this by patching libpng inside of the freeimage source using the same patch as the derivation.. I'm just debating whether or not to allow it to be toggle-able as it is in the libpng derivation.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
still important to me
I marked this as stale due to inactivity. &rarr;
still important to me
You can close this I think
Change:
${concatStringsSep " n" ([ "-f qcow2" ] ++ optional (cfg.useBootLoader && cfg.useDefaultFilesystems) "-F qcow2 -b ${systemImage}/nixos.qcow2" ++ optional (!(cfg.useBootLoader && cfg.useDefaultFilesystems)) "-o size=${toString config.virtualisation.diskSize}M" <del> ++ [ "$NIX_DISK_IMAGE" ])} </del> <ins> ++ [ ''"$NIX_DISK_IMAGE"'' ])} </ins> echo "Virtualisation disk image created." fi

Discussion:
The script defined in contains a if it does not yet exist. The file name of the disk image is stored in the bash variable which is when creating the disk image. Thus, if contains a space, the disk image creation fails. The following is an easy way to reproduce the problem under macOS with a recent nixpkgs; not sure about a Linux example, but anything that triggers a VM creation via in the current directory should do the trick. and enter a folder with a space in its name: a VM via nix, e.g., (a recent builder VM for macOS). (will ask for sudo password for key setup) image creation is triggered and fails with the following output: The builder disk image for the VM should be created and the VM should be started. (Also seems like there is a minor typo in the error message: "Disk image does not exist, …".)
Good point, can you send a PR?
Sure, here it is. As far as I could see this seems the online place in the script where the variable was not properly escaped. A quick test via from a folder containing spaces worked as expected.
Change:
, iconv , protobuf_21 , pythonSupport ? true <del> }: </del> <ins> , cudaSupport ? config.cudaSupport , cudaPackages ? {} }@inputs: </ins> let <ins> version = "1.16.3"; stdenv = throw "Use effectiveStdenv instead"; effectiveStdenv = if cudaSupport then cudaPackages.backendStdenv else inputs.stdenv; cudaCapabilities = cudaPackages.cudaFlags.cudaCapabilities; # E.g. [ "80" "86" "90" ] cudaArchitectures = (builtins.map cudaPackages.cudaFlags.dropDot cudaCapabilities); cudaArchitecturesString = lib.strings.concatStringsSep ";" cudaArchitectures; </ins> howard-hinnant-date = fetchFromGitHub { owner = "HowardHinnant"; repo = "date";

Discussion:
Project description ONNX Runtime: cross-platform, high performance ML inferencing and training accelerator . Onnxruntime is already packaged. I would like to have the version with gpu support to be able to package obs-backgroundremoval with gpu support (). Related: Metadata homepage URL: source URL: license: mit platforms: linux
Obs-backgroundremoval includes tensorrtproviderfactory.h to build
need it, too
Is it possible to add gpu support to the obs-backgroundremoval as this issue is closed?
It may be possible. If anyone wants to open a PR for that, please base it on the current update PR
Change:
, mesa , libtiff , cups <ins> , udev </ins> , xorg <del> , steam-run </del> , makeWrapper , useChineseVersion ? false }:

Discussion:
Describe the bug When open any component of wps office, it shows an dialog "An error has occurred in WPS" and crash. No logs found, but it works by using steam-run. To Reproduce Steps to reproduce the behavior: package pkgs.wpsoffice it in terminal or click office logo shows an error dialog, self-restart repeatedly and exit. Screenshots ! Notify maintainers Metadata `` Maintainer information:
Confirmed this error on my nixos
Change:
<del> { stdenv, lib, fetchurl, glibc, zlib </del> <ins> { lib, stdenv, fetchurl, glibc, zlib </ins> , enableStatic ? stdenv.hostPlatform.isStatic <ins> , enableSCP ? false </ins> , sftpPath ? "/run/current-system/sw/libexec/sftp-server" }: <ins> let # NOTE: DROPBEAR_PATH_SSH_PROGRAM is only necessary when enableSCP is true, # but it is enabled here always anyways for consistency dflags = { SFTPSERVER_PATH = sftpPath; DROPBEAR_PATH_SSH_PROGRAM = "${placeholder "out"}/bin/dbclient"; }; in </ins> stdenv.mkDerivation rec { pname = "dropbear"; version = "2020.81";

Discussion:
is already packaged, but I needed the following to be able to correctly build the utility: I would propose adding an option , which adds to the default list , and also modifies to include the fix of . It might be a good idea to also mark as to prevent accidental conflicts with .
What about opening a PR yourself?
I marked this as stale due to inactivity. &rarr;
still wanted
Change:
"surfboard" "tor" "unifi" <ins> "unifi-poller" </ins> "varnish" "wireguard" ] (name:

Discussion:
Project description Collect ALL UniFi Controller, Site, Device & Client Data Nixpkg currently has which is not developed anymore. Corresponding NixOS module may have to be updated. Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin
Change:
./fix-curses.patch ]; <del> # Should I be using pygtk's propogated build inputs? </del> <ins> # Should I be using pygtk's propagated build inputs? </ins> # !!! Should use makeWrapper. postPatch = '' # We don't have "python2".

Discussion:
These are definitely not intentional: &q=propogatedBuildInputs&type=Code
I wonder: would that be from a Dvorak user?
Change:
# Avoid GLIBCXX mismatch with other cuda-enabled python packages preConfigure = '' <ins> # Ensure that the build process uses the requested number of cores export MAX_JOBS="$NIX_BUILD_CORES" </ins> # Upstream's setup.py tries to write cache somewhere in ~/ export HOME=$(mktemp -d)

Discussion:
On my 20 core machine with 32 GB of RAM, the above build gets killed by the OOM killer. It seems, that upstream triton (40 in my case) build jobs unless the environment variable is set. You can verify this by running the above command and using // to see that some of the / processes under are running with (the exact number may be different depending on the number of cores your machine has). I am not 100% sure what is the idiomatic nixpkgs way to fix this, but I am guessing that the derivation should be changed to correctly take into account the value of the environment variable. I was able to successfully build triton by adding to . seem to indicate that for a machine with 32 GB of RAM, is an appropriate amount of jobs, so it's possible that even setting may be too many jobs by default. For a broader discussion of this kind of issue, see my . If you have any ideas/suggestion on how we can improve the situation so that stuff like this doesn't happen or gets caught earlier, please let me know. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
For triton specifically, consider opening a PR setting : I suppose it's technically a "bug" that the derivation doesn't currently respect . I suppose it wouldn't hurt much to do something like But also let's not unless we find issues with . Also, thanks for the research you've done
Change:
weechat = callPackage ../applications/networking/irc/weechat { inherit (darwin) libobjc; inherit (darwin) libresolv; <ins> guile = guile_2_0; </ins> }; westonLite = callPackage ../applications/window-managers/weston {

Discussion:
, present on 17.03, is missing from master since guile was upgraded to 2.2 (). At least for now we have this issue to document it; nobody seems to be missing it (yet!). (on master)
This is probably because of the plugin split in . However, since then I submitted which enables all plugins by default, so it should work. Is your nixpkgs up to date?
By the looks of it, you're not using nix. This is the nix packages collection repo, and only issues specific to nixpkgs should be reported here.
Change:
buildInputs = with pkgs; [ lensfun gexiv2 ]; installPhase = " <del> installPlugins gimp-lensfun </del> <ins> installPlugin gimp-lensfun </ins> "; meta = {

Discussion:
Describe the bug I'm adding gimp like this in 20.09: However the fourier plugin is not being recognized. It should add: Filters/Generic/Forward FFT Filters/Generic/Inverse FFT But these filters are missing. Expected behavior FFT plugin should be recognized by gimp. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. Maintainer information:
I'm not sure about these specific plugins, but gimp-with-plugins comes with G'MIC, which includes a FFT filter under Filters -G'MIC Qt... -Available Filters -Frequency -Fourier transform
Change:
LDD="$(ldd $BIN)" || continue LIBS="$(echo "$LDD" | awk '{print $3}' | sed '/^$/d')" for LIB in $LIBS; do <del> [ ! -f "$out/lib/$(basename $LIB)" ] && cp -pdv $LIB $out/lib while [ "$(readlink $LIB)" != "" ]; do LINK="$(readlink $LIB)" if [ "''${LINK:0:1}" != "/" ]; then LINK="$(dirname $LIB)/$LINK" fi LIB="$LINK" [ ! -f "$out/lib/$(basename $LIB)" ] && cp -pdv $LIB $out/lib done </del> <ins> TGT="$out/lib/$(basename $LIB)" if [ ! -f "$TGT" ]; then SRC="$(readlink -e $LIB)" cp -pdv "$SRC" "$TGT" fi </ins> done done

Discussion:
Enabling plymouth causes a build failure in the stage-1 boot utils. No error message is produced from the builder. The builder fails while copying libraries. System: Nix version: 1.12pre4523_3b81b26 CC:
I've just returned from a trip and hack on now -- will look during the next week.
Cannot reproduce on current master (). Tested with , with this configuration:
That configuration fails to build with the following log:
I sense hidden parameters D: To make sure we are on the same page: try commit (tested it right now, latest master ATM). Do you have ?
The build still fails at that commit with . :frowning:
Let's try some good old debugging: apply and check what happens. EDIT: A better idea which occurred to me only now would be to add .
Here is the error from the last iteration of with : It looks to me like the call to is failing which causes to fail because of .
Unfortunately, that thing is not related to this bug :frowning:
Change:
enableUserService = true; environment = { LIVEBOOK_PORT = 20123; <del> LIVEBOOK_COOKIE = "chocolate chip"; LIVEBOOK_TOKEN_ENABLED = true; </del> }; environmentFile = pkgs.writeText "livebook.env" '' LIVEBOOK_PASSWORD = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Discussion:
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.
Change:
stdenv.mkDerivation rec { pname = "nasc"; <del> version = "0.7.5"; </del> <ins> version = "0.8.0"; </ins> src = fetchFromGitHub { owner = "parnold-x"; repo = pname; rev = version; <del> sha256 = "kSRc5RLkI6SBJirUYw6swZi8IJhaL3y74b2Zw8kh2XA="; </del> <ins> sha256 = "02b9a59a9fzsb6nn3ycwwbcbv04qfzm6x7csq2addpzx5wak6dd8"; </ins> fetchSubmodules = true; }; <del> patches = [ # fix compilation with gcc10 (fetchpatch { url = "https://github.com/parnold-x/libqalculate/commit/4fa8f2cceada128ef19f82407226b2c230b780d5.patch"; extraPrefix = "subprojects/libqalculate/"; stripLen = "1"; sha256 = "0kbff623zl0s6yx5avx068f2apwzxzvihjahja4qhlkqkhhzj9dm"; }) ]; </del> nativeBuildInputs = [ glib # post_install.py gtk3 # post_install.py

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: nasc <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.7.5 desired version: 0.8.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: myself, lol Flatpack packaging so no real update. just to have the latest version
Change:
"gnome" "lxqt" "qt5ct" <ins> "kde" </ins> ]; example = "gnome"; relatedPackages = [

Discussion:
The reason why I didn't open a PR, is described in . I'm aware of four platforms for Qt's themes right now: Using GTK themes through + ; Using GNOME themes through + ; Using Qt themes, with the non-KDE solution , which uses ; Using Plasma-targeted Qt themes, with as , as done natively in a plasma session, using the theme's colorscheme. Steps to reproduce the behavior:  and it does not provide ; equivalent to  providing ; , then add some Pasma-target themes like , then adjust envvars , set the theme in or with , you'll get the right theme with the proper color scheme. should provide (or ) as an option, it should add only the required packages to the system, and set the proper envvars. (or maybe rename it, since qt6 also uses the same variables and envvars) qbittorrent + breeze + + dark: ! qbittorrent + breeze + + dark: ! qbittorrent + (ignored my theme): ! qbittorrent + (also ignored my theme): ! I tried to discover what package that is being when evaluating provides this platform-theme, but I failed miserably. stated as maintainers of plasma-integration: stated as maintainer of qt5ct: qt5 module contributors: cc Please run and paste the result.
Not exactly your bug, but we should remove and integrate it with configs instead.
is another QT platform theme that can be integrated into config.