jiebi/CodeConvo huggingface dataset:
Code change:
{ runCommand, lib, writeText, writeScriptBin, stdenv, ruby } : <del> { env, runScript ? "bash", extraBindMounts ? [], extraInstallCommands ? "", importMeta ? {} } : </del> <ins> { env, runScript ? "bash", extraBindMounts ? [], extraInstallCommands ? "", meta ? {}, passthru ? {} } : </ins> let name = env.pname;

Related discussion:
text: This weekend I tried these games, all deadlocked in the menu or character selection. Nyheim Oh...Sir! The Insult Simulator Reigns Unturned (free to play) You don't have to be worried to waste money in case you want to test a game. I have had no problem when requesting refunds, just go to I have played these games and found no issues with them: Dota 2 Counter-Strike TIS-100 World of goo Faster Than Light You Must Build a Boat Risk of Rain System: (NixOS: , Ubuntu/Fedora: , ...) 03pre99759. (Gorilla) Nix version: (run ) nix-env (Nix) 1.11.6 Nixpkgs version: (run ) "17.03pre99759." Integrated graphics card, 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
This is normal with steam on nixos unfortunately. There are many steam games that don't work for various reasons, unfortunately many linux steam game developers only make sure their games run on ubuntu and don't really care about relying only on dependencies from the steam runtime. Some games don't play nice with certain graphics cards or drivers as well. If you want to get a particular game working (I can list 150 games that work under nixos with nvidia card and drivers at least) then you'll need to do some work, or at least post any relevant logs from the game/steam so people can actually help you solve the problem. That is assuming that they own the game. :)
There's a slowly-growing list of extra dependencies in the Steam package. If you can figure out what's missing, you can add it there; e.g. as in
I don't have enough motivation to actually buy games for the sole purpose of fixing them and then refunding, sorry. Nevertheless, I'm happy to help if you can post logs and/or s -- those two are the most helpful for determining FHS-related problems.
Code change:
# https://github.com/OpenNMT/CTranslate2/blob/54810350e662ebdb01ecbf8e4a746f02aeff1dd7/python/tools/prepare_build_environment_linux.sh#L53 # https://github.com/OpenNMT/CTranslate2/blob/59d223abcc7e636c1c2956e62482bc3299cc7766/python/tools/prepare_build_environment_macos.sh#L12 "-DOPENMP_RUNTIME=COMP" <ins> "-DWITH_CUDA=${cmakeBool withCUDA}" "-DWITH_CUDNN=${cmakeBool withCuDNN}" </ins> "-DWITH_DNNL=${cmakeBool withOneDNN}" "-DWITH_OPENBLAS=${cmakeBool withOpenblas}" "-DWITH_RUY=${cmakeBool withRuy}"

Related discussion:
text: After setting up faster-whisper for my Home Assistant instance, I learned that my CPU (i5-6500) isn't quite as fast as I'd like for this, so I am now trying to test a GPU (NVIDIA Quadro M2000). My configuration for it is the following: I expected it to then run on my GPU using CUDA, but unless my GPU and CPU are continually equally performant, it is not working. (Also, no processes are shown in ) Steps to reproduce the behavior: NVIDIA GPU, and then configure it accordingly in , add , , , and to faster-whisper in configuration, configure it to work with device = "cuda" for STT to be faster, instead same speed I'm not totally sure what to expect because this is my first time using this, but I expected a Python3 process to appear in and for my STT to be quicker. My config is the following: The following (seemingly) NVIDIA related items are at /dev/ ! ! works, but I am not totally sure that my CUDA is configured correctly, for all I know possibly CUDA isn't configured properly, but I think I have everything correct.
I eyeballed CUDA support, but have no hardware to test or reproduce. I appreciate help in fixing the module to make it work with CUDA.
I am not overly proficient in Nix or anything like this, but I would be willing to help if you have ideas.
Well, for one we're not passing in . Can you try setting ?
Ok, I that and now when looking at the logs, I get this: It then exits.
That looks actionable. We did indeed not build ctranslate2 with CUDA support. I can try to set that up, but it won't be the default, because that would make the package unfree. We possibly need multiple ctranslate2 attributes.
Is it possible to have the package be free unless an option is passed that enables CUDA and then makes it unfree, or would two different packages be needed. There could be a package, I think that could work.
Yeah, that would also work.
If you want to try and build it with CUDA support, I can test it out and report back.
fixes the module, so it passes as expected. It also adds CUDA support to .
Code change:
# https://github.com/OpenNMT/CTranslate2/blob/54810350e662ebdb01ecbf8e4a746f02aeff1dd7/python/tools/prepare_build_environment_linux.sh#L53 # https://github.com/OpenNMT/CTranslate2/blob/59d223abcc7e636c1c2956e62482bc3299cc7766/python/tools/prepare_build_environment_macos.sh#L12 "-DOPENMP_RUNTIME=COMP" <ins> "-DWITH_CUDA=${cmakeBool withCUDA}" "-DWITH_CUDNN=${cmakeBool withCuDNN}" </ins> "-DWITH_DNNL=${cmakeBool withOneDNN}" "-DWITH_OPENBLAS=${cmakeBool withOpenblas}" "-DWITH_RUY=${cmakeBool withRuy}"

Related discussion:
text: Check the description of the PR on how to opt into CUDA support in nixpkgs.
Hi Just to clarify, you only need in your (or in your 's ) if you're setting up a development environment to write cuda programs. If you only want to use packages with cuda support enabled, you just use them directly (e.g. ), no need to add anywhere manually. If you want to enable cuda in every package that supports it, you can set in your (nb: this triggers a massive rebuild). Instead of adding , you want to use (this way if you switch e.g. -, you'd be still using for the correct kernel), but also instead of you can take (keeps working if you switch e.g. -) Sorry we didn't get this documented yet
Wow, thank you! I assume I still need in my , right? About enabling , I've already enabled that and let it go through that whole process, so I think I'll just leave it enabled. About changing the , how is that to be done exactly? Do I just swap for in the exact same spot?
Also, is there an easy way for me to test out this updated package before it gets merged?
Depends on how you deploy your machine and what nixos version you are on.
I'm on Unstable and use Flakes.
You could replace your nixpkgs input with a fork of nixos-unstable and pick the commits from that PR on top. I'm sure there is a better solution, but I'm not well versed in flakes.
No, is the old version of , and you don't need it in Yes, except it's just , without at the end. This refers to "whatever graphics driver is in use". But also you can just remove this if you use and (both options are badly named, they're not really specific to neither of opengl or x11)
I have , but I don't have xserver enabled because this is a headless server. Do I even need nvidia_x11 if it's headless with no DE?
is where comes from; I don't recall now if it's ok to use on a headless machine, but if you like to just be explicit, you can keep P.S.
Code change:
# https://github.com/OpenNMT/CTranslate2/blob/54810350e662ebdb01ecbf8e4a746f02aeff1dd7/python/tools/prepare_build_environment_linux.sh#L53 # https://github.com/OpenNMT/CTranslate2/blob/59d223abcc7e636c1c2956e62482bc3299cc7766/python/tools/prepare_build_environment_macos.sh#L12 "-DOPENMP_RUNTIME=COMP" <ins> "-DWITH_CUDA=${cmakeBool withCUDA}" "-DWITH_CUDNN=${cmakeBool withCuDNN}" </ins> "-DWITH_DNNL=${cmakeBool withOneDNN}" "-DWITH_OPENBLAS=${cmakeBool withOpenblas}" "-DWITH_RUY=${cmakeBool withRuy}"

Related discussion:
text: Discourse and NixOS matrix channels provide venues for Q&A discussions
With the changes made to ctranslate2, and the fixes to th , I fully expect this could work. If not, please get back to me with some error messages, e.g. the hardening of the systemd unit might cause problems.
No problem. I attempted to use just the new packages, but it became a little difficult because my old nixpkgs didn't think that ctranslate2 could have CUDA enabled, so I'll just wait for master to get pushed to NixOS-Unstable (Hopefully soon!)
The package now fails with . My system may not be correctly configured for CUDA support, or the SystemD Service is not passing through the NVIDIA device correctly. Just a reminder, the following devices are available at : (I'm not sure if is an NVIDIA thing, but it exists if that's of importance.)
Then we're at least missing . What's the content of ? nix DeviceAllow = if [ "cuda" "auto" ] then [ # "/dev/nvidia1" "/dev/nvidia2" "/dev/nvidia3" "/dev/nvidia4" "/dev/nvidia-caps/nvidia-cap1" "/dev/nvidia-caps/nvidia-cap2" "/dev/nvidiactl" "/dev/nvidia-modeset" "/dev/nvidia-uvm" "/dev/nvidia-uvm-tools" ] else "";
I modified the SystemD service to include , and it didn't help at all. The contents of are . Also, I just discovered something new. When running I get So possibly updating this system now broke NVIDIA support and it just so happened to be at the same time I tried to get Whisper working.
Did you also check which is in ? There are two things you need to maintain: 1) your driver should be newer than the cuda libraries used to build your program, 2) your should come from the same (version of) package as the kernel modules (in other words, currently you have to reboot if you update your nixos and get a newer - the new kernel module is only loaded on the next boot)
shows the following for Also, I just rebooted and is working.
from what I listed is accessible from , should my system have functional CUDA support? I tried using some testing parts from , but it seems to be out of date.
Code change:
# https://github.com/OpenNMT/CTranslate2/blob/54810350e662ebdb01ecbf8e4a746f02aeff1dd7/python/tools/prepare_build_environment_linux.sh#L53 # https://github.com/OpenNMT/CTranslate2/blob/59d223abcc7e636c1c2956e62482bc3299cc7766/python/tools/prepare_build_environment_macos.sh#L12 "-DOPENMP_RUNTIME=COMP" <ins> "-DWITH_CUDA=${cmakeBool withCUDA}" "-DWITH_CUDNN=${cmakeBool withCuDNN}" </ins> "-DWITH_DNNL=${cmakeBool withOneDNN}" "-DWITH_OPENBLAS=${cmakeBool withOpenblas}" "-DWITH_RUY=${cmakeBool withRuy}"

Related discussion:
text: PS: Should this conversation be continued somewhere else, or is it fine to continue it here because it is somewhat pertinent to the issue?
Yes please, e.g. in or , or on You can just post the final update here once you get things to work, for discoverability purposes. Thanks!
Code change:
patches = [ ./languages-use-the-hardcoded-path-to-python-binaries.patch ./hook-tmpl.patch <ins> ./pygrep-pythonpath.patch </ins> ]; propagatedBuildInputs = [

Related discussion:
text: hooks with work by . This fails because is a plain binary that doesn’t have in its environment. Steps to reproduce the behavior:
A workaround is to use the binary from instead.
It seems the above fix is insufficient. While works correctly, the hook installed into doesn't have the Python environment with the pygrep package. tested on:
Still same problem...
If you pull in the above mentioned into your environment, it should work. For best results, I recommend putting it into your (& use direnv) or systemPackages.
Potential fix which doesn't require changing the python provided in the nix shell:
Code change:
{ stdenv, fetchurl, pkgconfig, e19, zlib, libspectre, gstreamer, gst_plugins_base, gst_ffmpeg, gst_plugins_good, poppler, librsvg, libraw }: stdenv.mkDerivation rec { name = "evas_generic_loaders-${version}"; <del> version = "1.11.2"; </del> <ins> version = "1.12.0"; </ins> src = fetchurl { url = "http://download.enlightenment.org/rel/libs/evas_generic_loaders/${name}.tar.gz"; <del> sha256 = "03p6v7l2fxvldiymqk16pqnbm9llygp6i19qhn3rmrqy1hkjkry6"; </del> <ins> sha256 = "0viph73wv83xw9g6rgjhhiav9n896m0ixnz2m27cnmmn8llchcf5"; </ins> }; buildInputs = [ pkgconfig e19.efl zlib libspectre gstreamer gst_plugins_base gst_ffmpeg gst_plugins_good poppler librsvg libraw ]; meta = {

Related discussion:
text: Possible, because X11/xkb/rules/*.lst [0] are somewhere 'hidden' in the /nix/store. [0]
Fixed, just let me do some updating on E19 libraries and I will make a pull request.
Code change:
systool = sysfsutils; # added 2018-04-25 tahoelafs = tahoe-lafs; # added 2018-03-26 tangogps = foxtrotgps; # added 2020-01-26 <ins> tdm = throw "tdm has been removed because nobody can figure out how to fix OpenAL integration. Use precompiled binary and `steam-run` instead."; </ins> telepathy_farstream = telepathy-farstream; # added 2018-02-25 telepathy_gabble = telepathy-gabble; # added 2018-02-25 telepathy_glib = telepathy-glib; # added 2018-02-25

Related discussion:
text: Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: tdmupdater tdm Expected behavior tdm starts. Actual behaviour tdm starts with a black error and has stderr errors such as: Additional context It looks like the problem might be that and the assets downloaded via tdmupdater are different versions: Workaround (Steam isn't actually used for this. This is just a lazy way to run FHS programs.) Notify maintainers Metadata** Maintainer information:
There's a version update in master. I don't know when it'll land in unstable (maybe it already did?) or stable.
Is it possible to have NixOS stable not break when upstream changes? Either: (a) NixOS stable should include the TDM assets (in which case tdm_update is not needed) (b) becomes solely a shim to grab assets from the TDM assets, so it doesn't matter which version of is used.
require patching the path to ELF interpreter, along with worrying about lib dependencies. complicated: TDM players are accustomed to dowloading extra missions, which requires a writable directory to hold the data. Do you have a proposal how to do this securely? Hardlinking the default install to /home would break if /home is on a different FS. Suid wrappers smell. World-writable bits in /nix smell too.
Surely the engine supports multiple asset directories, so we can load the assets from the nix store in addition to whatever was installed manually into a local directory.
The comments on suggest The Dark Mod stores save games in its installation directory. tracks this issue.
I have another issue that seem to be related. Running tdm via the ` work however. The relevent line are: When it doesn't work and with the second option
I poked around - and I don't have any ideas why OpenAL might not be finding hardware. Right now, it seems that the best course of action is to remove TDM from repos (to avoid creating false expectations), and run it with steam-run. and do you agree?
Code change:
githubId = 92817635; name = "Sanskar Gurdasani"; }; <ins> sarahec = { email = "sarahec@nextquestion.net"; github = "sarahec"; githubId = 11277967; name = "Sarah Clark"; }; </ins> sarcasticadmin = { email = "rob@sarcasticadmin.com"; github = "sarcasticadmin";

Related discussion:
text: Project description Scalene is a high-performance CPU, GPU and memory profiler for Python that does a number of things that other Python profilers do not and cannot do. It runs orders of magnitude faster than many other profilers while delivering far more detailed information. It is also incorporates AI-powered optimization suggestions. Metadata homepage URL: source URL: license: Apache 2 platforms: unix, linux, darwin, windows Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
sha256 = "wfLO7kf2iXESItcgWvKj/npKnYwy5OCyStZviN9qR9M="; }; <ins> patches = [ # https://nmbug.notmuchmail.org/nmweb/show/87o84iza9r.fsf%40starbuck.i-did-not-set--mail-host-address--so-tickle-me ./test-fix-support-for-gpgsm-in-gnupg-2.3.patch ]; </ins> nativeBuildInputs = [ pkg-config doxygen                   # (optional) api docs

Related discussion:
text: The build is failing on master; it has been reproduced at . An example of the failure is below: There is a new release () which also doesn't pass, so I didn't send the PR as it'd fail on CI. Steps to reproduce the behavior:
Those aren't the failing tests (BROKEN means they are known to fail). These are the real failures: Looks like a broken test directory setup in the build environment.
fixed in the next point release I think
prior work
Code change:
# include terraform-provider-segment ajbosco/terraform-provider-segment <ins> # include terraform-provider-wavefront spaceapegames/terraform-provider-wavefront </ins>

Related discussion:
text: Project description Wavefront is VMWare product and, per their website, is an "Enterprise-grade cloud monitoring and analytics at over 4 million data points per second." The service can be provisioned via Terraform -- there's an OS Terraform provider available here: It should be included amongst the set of existing Terraform providers that already contains. Metadata homepage URL: source URL: license: apl2 platforms: linux
Code change:
}; extraUpFlags = mkOption { <del> description = "Extra flags to pass to {command}`tailscale up`."; </del> <ins> description = '' Extra flags to pass to {command}`tailscale up`. Only applied if `authKeyFile` is specified."; ''; </ins> type = types.listOf types.str; default = []; example = ["--ssh"]; }; <ins> extraSetFlags = mkOption { description = "Extra flags to pass to {command}`tailscale set`."; type = types.listOf types.str; default = []; example = ["--advertise-exit-node"]; }; </ins> extraDaemonFlags = mkOption { description = "Extra flags to pass to {command}`tailscaled`."; type = types.listOf types.str;

Related discussion:
text: Tailscale package is not using the unless is set. Steps to reproduce the behavior: tailscale and set a flag ==no flags are used Flags are used If applicable, add screenshots to help explain your problem. Code reference: extraUpFlags is only used inside the if of auth key not being null check. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This caught me out too - could just be as simple as a warning/error when setting without ?
I don’t think that is adequate as you can run tail scale as server just fine without argument. An is only valid for up to 90 days.
Sure, but it would be a good start to alert users to the current behavior.
I was managing personal nixpkgs only because of this issue... (simply patching package doesn't seem to work for modules) Created PR for this. Hope someone can review this.
Code change:
<ins> commit 1e8fdf3f90fd142c5ddd63e44ca1e5c172dbfb7f Author: Simon Gardling <titaniumtown@proton.me> Date:   Tue Aug 27 12:45:14 2024 -0400 use locally downloaded embeddings index 27f3f5d9..9e25528a 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -90,6 +90,7 @@ elseif (APPLE) endif() # Embedding model +#[[ set(LOCAL_EMBEDDING_MODEL "nomic-embed-text-v1.5.f16.gguf") set(LOCAL_EMBEDDING_MODEL_MD5 "a5401e7f7e46ed9fcaed5b60a281d547") set(LOCAL_EMBEDDING_MODEL_PATH "${CMAKE_BINARY_DIR}/resources/${LOCAL_EMBEDDING_MODEL}") @@ -104,6 +105,7 @@ if (APPLE) list(APPEND CHAT_EXE_RESOURCES "${LOCAL_EMBEDDING_MODEL_PATH}") endif() +]] qt_add_executable(chat main.cpp @@ -383,11 +385,13 @@ endif() endif() +#[[ if (NOT APPLE) install(FILES "${CMAKE_BINARY_DIR}/resources/${LOCAL_EMBEDDING_MODEL}" DESTINATION resources COMPONENT ${COMPONENT_NAME_MAIN}) endif() +]] set(CPACK_GENERATOR "IFW") set(CPACK_VERBATIM_VARIABLES YES) --- a/embllm.cpp +++ b/embllm.cpp @@ -84,7 +84,7 @@ bool EmbeddingLLMWorker::loadModel() QString filePath = embPathFmt.arg(QCoreApplication::applicationDirPath(), LOCAL_EMBEDDING_MODEL); if (!QFileInfo::exists(filePath)) { -        qWarning() << "embllm WARNING: Local embedding model not found"; +        qWarning() << "embllm WARNING: Local embedding model not found: " << filePath; return false; } </ins>

Related discussion:
text: Package name: gpt4all Latest released version: 3.2.1 <!-- Search your package here: --- Current version on the unstable channel: 2.8.0 Current version on the stable/release channel: 2.7.5 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, I don't maintain GPT4All any longer, I switched to some other technologies (Open-WebUI).
haha, maybe i'll give that one a try then :) ty for all your hard work
Code change:
"tests" ]; <del> disabledTests = [ "test_datafile_download" ]; </del> <ins> # Disable tests that are problematic with pytest # Check NixOS/nixpkgs#333019 for more info about these disabledTests = [ "test_datafile_download" "test_display_get_input_str" "test_display_get_y_n" ]; </ins> pythonImportsCheck = [ "castero"

Related discussion:
text: Steps to reproduce the behavior: status: status: status: This was discovered via pr <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It seems like some tests have began to fail. When testing, the traceback shows the following tests fail because they don't initialize the module correctly (with ). - These tests don't undermine the functionality of when building from source, so I'm inclined to believe that the culprit is itself. Looking further, throws various deprecation warnings when the tests run. I fear that the more NixOS receives updates to , the more the tests will become more deprecated. It's unclear how NixOS feels about packages and their tests (particularly whether it's necessary for a maintainer to maintain package tests), but the current workaround is to disable these tests. Adding the tests to the field produces the result package, and continues to work as normal. I'd like some input on how to approach as this does feel pretty hacky.
We could override pytest back to a previous working version. I looked to the upstream package and it hasn't been updated in a year, to which was just a readme update.
Wouldn't this affect newer packages (assuming they use as a unit test framework) who utilize newer features of ? Though hacky, the solution I've suggested gets the job done. As mention previously, the failure of the tests don't influence 's functionality.
Disabling problematic tests is done a lot across nixpkgs. Since we know its still working when they are disabled it should be fine.
Code change:
glom = callPackage ../development/python-modules/glom { }; <ins> glueviz = callPackage ../development/python-modules/glueviz { }; </ins> glymur = callPackage ../development/python-modules/glymur { }; gmpy2 = callPackage ../development/python-modules/gmpy2 { };

Related discussion:
text: Project description Glue is a python project to link visualizations of scientific datasets across many files. Click on the image for a quick demo: ! Metadata homepage URL: source URL: license: BSD Linux, BSD
Code change:
<ins> { lib, python3Packages, fetchPypi }: python3Packages.buildPythonApplication rec { pname = "konsave"; version = "2.2.0"; src = fetchPypi { inherit version; pname = "Konsave"; hash = "sha256-tWarqT2jFgCuSsa2NwMHRaR3/wj0khiRHidvRNMwM8M="; }; nativeBuildInputs = with python3Packages; [ setuptools-scm ]; propagatedBuildInputs = with python3Packages; [ pyyaml setuptools ]; preCheck = '' export HOME=$(mktemp -d) ''; meta = with lib; { description = "Save Linux Customization"; maintainers = with maintainers; [ MoritzBoehme ]; homepage = "https://github.com/Prayag2/konsave"; license = licenses.gpl3; platforms = platforms.linux; }; } </ins>

Related discussion:
text: Project description A CLI program that will let you save and apply your Linux customizations with just one command! It officially supports KDE Plasma but it can be used on all other desktop environments too! Metadata homepage URL: source URL: license: gpl3 platforms: linux