jiebi/CodeConvo huggingface dataset:
Code change:
Project description A Mir-based Wayland compositor like , but tiling instead of floating. ! More Mir testers, more better. Requesting this from myself so I don't forget about this. Needs a very new Mir, newer than we currently provide (depends on ). Metadata homepage URL: source URL: license: gpl3+ platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <ins> { stdenv, lib, fetchFromGitHub, gitUpdater, nixosTests, boost, cmake, glib, glm, gtest, libevdev, libglvnd, libnotify, libuuid, libxkbcommon, mesa, mir, nlohmann_json, pcre2, pkg-config, yaml-cpp, }: stdenv.mkDerivation (finalAttrs: { pname = "miracle-wm"; version = "0.3.0"; src = fetchFromGitHub { owner = "mattkae"; repo = "miracle-wm"; rev = "v${finalAttrs.version}"; hash = "sha256-Ss93yI33e+XFjbKedbBjmYHkjPeWUWxEStwNTgTszA4="; }; postPatch = '' substituteInPlace session/usr/local/share/wayland-sessions/miracle-wm.desktop.in  --replace-fail '@CMAKE_INSTALL_FULL_BINDIR@/miracle-wm' 'miracle-wm' '' + lib.optionalString (!finalAttrs.finalPackage.doCheck) '' substituteInPlace CMakeLists.txt  --replace-fail 'add_subdirectory(tests/)' "" ''; strictDeps = true; # Source has a path "session/usr/local/...", don't break references to that dontFixCmake = true; nativeBuildInputs = [ cmake pkg-config ]; buildInputs = [ boost glib glm libevdev libglvnd libnotify libuuid libxkbcommon mesa # gbm.h mir nlohmann_json pcre2 yaml-cpp ]; checkInputs = [ gtest ]; doCheck = stdenv.buildPlatform.canExecute stdenv.hostPlatform; checkPhase = '' runHook preCheck ./bin/miracle-wm-tests runHook postCheck ''; passthru = { updateScript = gitUpdater { rev-prefix = "v"; }; providedSessions = [ "miracle-wm" ]; tests.vm = nixosTests.miracle-wm; }; meta = with lib; { description = "Tiling Wayland compositor based on Mir"; longDescription = '' miracle-wm is a Wayland compositor based on Mir. It features a tiling window manager at its core, very much in the style of i3 and sway. The intention is to build a compositor that is flashier and more feature-rich than either of those compositors, like swayfx. See the user guide for info on how to use miracle-wm: https://github.com/mattkae/miracle-wm/blob/v${finalAttrs.version}/USERGUIDE.md ''; homepage = "https://github.com/mattkae/miracle-wm"; license = licenses.gpl3Only; mainProgram = "miracle-wm"; maintainers = with maintainers; [ OPNA2608 ]; platforms = platforms.linux; }; }) </ins>
Code change:
Recently, after updating my HA instance that is running on NixOS, I get when I start HA and I cannot use the SmartThings integration. Steps to reproduce the behavior: HA on NixOS SmartThings set up to whatever version caused it (I haven't been able to determine what version it was that broke) I expect the SmartThings integration to successfully run and connect to the devices it should and be usable, instead I get an entirely non-functional integration. I do not think this is an HA wide issue after doing some Google searching with the issue, I think it is NixOS related, but someone can correct me if I'm wrong. Can't tell exactly who to ping here, but I think at least Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Please post a complete traceback if available, so we can determine what exactly requires .
Thank you!

Related discussion:
text: { lib , buildPythonPackage , fetchPypi <ins> , setuptools </ins> , setuptools-scm , pycryptodome , requests , six <ins> , pytestCheckHook </ins> }: buildPythonPackage rec { pname = "httpsig"; version = "1.3.0"; <del> format = "setuptools"; </del> <ins> pyproject = true; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "1rkc3zwsq53rjsmc47335m4viljiwdbmw3y2zry4z70j8q1dbmki"; </del> <ins> hash = "sha256-cdbVAkYSnE98/sIPXlfjUdK4SS1jHMKqlnkUrPkfbOY="; </ins> }; <del> buildInputs = [ </del> <ins> build-system = [ setuptools </ins> setuptools-scm ]; <del> propagatedBuildInputs = [ </del> <ins> dependencies = [ </ins> pycryptodome requests six <ins> setuptools ]; nativeCheckInputs = [ pytestCheckHook </ins> ]; pythonImportsCheck = [ "httpsig" ];
Code change:
Steps to reproduce the behavior: ollama service the model dir Ollama should work, files and directories have rw permissions for anyone and the file system is not read-only. It used to work before an update. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Could you try manually renaming the file to see if you get the same error? If you still get the error, the problem is probably with your system config. If you don't get the error, the problem could be with the ollama binary, or with the service config. Maybe try it as root as well to see if there's a difference. By the way, the reason it's trying to rename the files is due to a change in .
Renaming files solves the problem of starting ollama, but does not solve the overall problem. I can't install a new model, for example.
I found what the problem is. The ollama service has set, which creates a new user for the service and enables some sandboxing that includes making most of the filesystem read-only. I'm not sure at the moment the best way to fix this without compromising on security, so I'll do some more research on how systemd works, and any relevant systemd options. At worst, I should be able to create a nixos option that disables this sandboxing entirely. If you have any suggestions, I'd be happy to hear them.
In the meantime, a temporary workaround that I think should work is this nixos config:

Related discussion:
text: example = "/home/foo"; description = '' The home directory that the ollama service is started in. <ins> See also `services.ollama.writablePaths` and `services.ollama.sandbox`. </ins> ''; }; models = lib.mkOption {
Code change:
Steps to reproduce the behavior: ollama service the model dir Ollama should work, files and directories have rw permissions for anyone and the file system is not read-only. It used to work before an update. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Could you try manually renaming the file to see if you get the same error? If you still get the error, the problem is probably with your system config. If you don't get the error, the problem could be with the ollama binary, or with the service config. Maybe try it as root as well to see if there's a difference. By the way, the reason it's trying to rename the files is due to a change in .
Renaming files solves the problem of starting ollama, but does not solve the overall problem. I can't install a new model, for example.
I found what the problem is. The ollama service has set, which creates a new user for the service and enables some sandboxing that includes making most of the filesystem read-only. I'm not sure at the moment the best way to fix this without compromising on security, so I'll do some more research on how systemd works, and any relevant systemd options. At worst, I should be able to create a nixos option that disables this sandboxing entirely. If you have any suggestions, I'd be happy to hear them.
In the meantime, a temporary workaround that I think should work is this nixos config:

Related discussion:
text: example = "/path/to/ollama/models"; description = '' The directory that the ollama service will read models from and download new models to. <ins> See also `services.ollama.writablePaths` and `services.ollama.sandbox` if downloading models or other mutation of the filesystem is required. ''; }; sandbox = lib.mkOption { type = types.bool; default = true; example = false; description = '' Whether to enable systemd's sandboxing capabilities. This sets [`DynamicUser`]( https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#DynamicUser= ), which runs the server as a unique user with read-only access to most of the filesystem. See also `services.ollama.writablePaths`. ''; }; writablePaths = lib.mkOption { type = types.listOf types.str; default = [ ]; example = [ "/home/foo" "/mnt/foo" ]; description = '' Paths that the server should have write access to. This sets [`ReadWritePaths`]( https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#ReadWritePaths= ), which allows specified paths to be written to through the default sandboxing. See also `services.ollama.sandbox`. </ins> ''; }; listenAddress = lib.mkOption {
Code change:
Steps to reproduce the behavior: ollama service the model dir Ollama should work, files and directories have rw permissions for anyone and the file system is not read-only. It used to work before an update. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Could you try manually renaming the file to see if you get the same error? If you still get the error, the problem is probably with your system config. If you don't get the error, the problem could be with the ollama binary, or with the service config. Maybe try it as root as well to see if there's a difference. By the way, the reason it's trying to rename the files is due to a change in .
Renaming files solves the problem of starting ollama, but does not solve the overall problem. I can't install a new model, for example.
I found what the problem is. The ollama service has set, which creates a new user for the service and enables some sandboxing that includes making most of the filesystem read-only. I'm not sure at the moment the best way to fix this without compromising on security, so I'll do some more research on how systemd works, and any relevant systemd options. At worst, I should be able to create a nixos option that disables this sandboxing entirely. If you have any suggestions, I'd be happy to hear them.
In the meantime, a temporary workaround that I think should work is this nixos config:

Related discussion:
text: type = types.attrsOf types.str; default = { }; example = { <del> HOME = "/tmp"; </del> OLLAMA_LLM_LIBRARY = "cpu"; <ins> HIP_VISIBLE_DEVICES = "0,1"; </ins> }; description = '' Set arbitrary environment variables for the ollama service.
Code change:
Steps to reproduce the behavior: ollama service the model dir Ollama should work, files and directories have rw permissions for anyone and the file system is not read-only. It used to work before an update. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Could you try manually renaming the file to see if you get the same error? If you still get the error, the problem is probably with your system config. If you don't get the error, the problem could be with the ollama binary, or with the service config. Maybe try it as root as well to see if there's a difference. By the way, the reason it's trying to rename the files is due to a change in .
Renaming files solves the problem of starting ollama, but does not solve the overall problem. I can't install a new model, for example.
I found what the problem is. The ollama service has set, which creates a new user for the service and enables some sandboxing that includes making most of the filesystem read-only. I'm not sure at the moment the best way to fix this without compromising on security, so I'll do some more research on how systemd works, and any relevant systemd options. At worst, I should be able to create a nixos option that disables this sandboxing entirely. If you have any suggestions, I'd be happy to hear them.
In the meantime, a temporary workaround that I think should work is this nixos config:

Related discussion:
text: ExecStart = "${lib.getExe ollamaPackage} serve"; WorkingDirectory = cfg.home; StateDirectory = [ "ollama" ]; <del> DynamicUser = true; </del> <ins> DynamicUser = cfg.sandbox; ReadWritePaths = cfg.writablePaths; </ins> }; };
Code change:
Steps to reproduce the behavior: kvmfr <!-- 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: src = looking-glass-client.src; sourceRoot = "${looking-glass-client.src.name}/module"; <del> patches = lib.optional (kernel.kernelAtLeast "6.4") [ ./linux-6-4-compat.patch ]; </del> hardeningDisable = [ "pic" "format" ]; nativeBuildInputs = kernel.moduleBuildDependencies;
Code change:
Steps to reproduce the behavior: kvmfr <!-- 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: <del> diff --git a/kvmfr.c b/kvmfr.c index 121aae5b..2f4c9e1a 100644 --- a/kvmfr.c +++ b/kvmfr.c @@ -539,7 +539,11 @@ static int __init kvmfr_module_init(void) if (kvmfr->major < 0) goto out_free; +#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 4, 0) kvmfr->pClass = class_create(THIS_MODULE, KVMFR_DEV_NAME); +#else +  kvmfr->pClass = class_create(KVMFR_DEV_NAME); +#endif if (IS_ERR(kvmfr->pClass)) goto out_unreg; </del>
Code change:
Steps to reproduce the behavior: x3270 on darwin fails due to missing macOs dependencies (libiconv/Security) The are a few things missing that are need to get this to work on macOS use & link iconv use Security package for headers disable x3270 build (the other unix builds are fine) Please run and paste the result. I have a fixed package for this that I can open a PR for

Related discussion:
text: <del> { lib, stdenv, fetchurl, m4, expat , libX11, libXt, libXaw, libXmu, bdftopcf, mkfontdir , fontadobe100dpi, fontadobeutopia100dpi, fontbh100dpi , fontbhlucidatypewriter100dpi, fontbitstream100dpi </del> <ins> { stdenv , darwin , lib , libiconv , fetchurl , m4 , expat , libX11 , libXt , libXaw , libXmu , bdftopcf , mkfontdir , fontadobe100dpi , fontadobeutopia100dpi , fontbh100dpi , fontbhlucidatypewriter100dpi , fontbitstream100dpi </ins> , tcl <del> , ncurses }: </del> <ins> , ncurses }: </ins> let majorVersion = "4"; <del> minorVersion = "0"; versionSuffix = "ga9"; in stdenv.mkDerivation rec { </del> <ins> minorVersion = "3"; versionSuffix = "ga8"; in stdenv.mkDerivation rec { </ins> pname = "x3270"; version = "${majorVersion}.${minorVersion}${versionSuffix}"; src = fetchurl { <del> url = "http://x3270.bgp.nu/download/0${majorVersion}.0${minorVersion}/suite3270-${version}-src.tgz"; sha256 = "0km24rgll0s4ji6iz8lvy5ra76ds162s95y33w5px6697cwqkp9j"; </del> <ins> url = "http://x3270.bgp.nu/download/0${majorVersion}.0${minorVersion}/suite3270-${version}-src.tgz"; sha256 = "sha256-gcC6REfZentIPEDhGznUSYu8mvVfpPeMz/Bks+N43Fk="; </ins> }; <del> buildFlags = [ "unix" ]; </del> <ins> buildFlags = lib.optional stdenv.isLinux "unix"; configureFlags = lib.optionals stdenv.isDarwin [ "--enable-c3270" "--enable-pr3270" "--enable-s3270" "--enable-tcl3270" ]; </ins> <del> postConfigure = '' pushd c3270 ; ./configure ; popd </del> <ins> postBuild = '' make install.man </ins> ''; <ins> pathsToLink = [ "/share/man" ]; </ins> nativeBuildInputs = [ m4 ]; buildInputs = [ expat <del> libX11 libXt libXaw libXmu bdftopcf mkfontdir fontadobe100dpi fontadobeutopia100dpi fontbh100dpi fontbhlucidatypewriter100dpi fontbitstream100dpi </del> <ins> libX11 libXt libXaw libXmu bdftopcf mkfontdir fontadobe100dpi fontadobeutopia100dpi fontbh100dpi fontbhlucidatypewriter100dpi fontbitstream100dpi </ins> tcl ncurses expat <del> ]; </del> <ins> ] ++ lib.optionals stdenv.isDarwin [ libiconv darwin.apple_sdk.frameworks.Security ]; </ins> meta = with lib; { description = "IBM 3270 terminal emulator for the X Window System";
Code change:
Package name: i3bar-river Latest released version: 0.1.7 <!-- Search your package here: --- Current version on the unstable channel: 0.1.6 Current version on the stable/release channel: 0.1.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]:
I looked into this a couple days ago. The problem is that 0.1.7 makes use of a features introduced in Rust 1.77. NixOS isn't there yet, so I don't think this package can be updated just yet.

Related discussion:
text: rustPlatform.buildRustPackage rec { pname = "i3bar-river"; <del> version = "0.1.6"; </del> <ins> version = "0.1.7"; </ins> src = fetchFromGitHub { owner = "MaxVerevkin"; repo = "i3bar-river"; rev = "v${version}"; <del> hash = "sha256-wtyC8cGK408KZYpWniW2y4XI1ScTSBZJJlUt6b2Z5KA="; </del> <ins> hash = "sha256-mLRB4o8FR/R9QUpRkcNppiE2XcWFWE05wPxuKdxG18M="; </ins> }; <del> cargoHash = "sha256-PdSMDsV3yFy3kSNS6OBxFdrZsIn70gXOTd2AhyU4a9o="; </del> <ins> cargoHash = "sha256-INjuI3XTSzAjLqk/P+cd7rMhXsOBDSqMaZZN9kFyreg="; </ins> nativeBuildInputs = [ pkg-config ]; buildInputs = [ pango ];
Code change:
Project description ab-av1 is a VMAF-based reencoding frontend for ffmpeg, primarily for av1 but works well with x265 and other encoders. It is a rust project and requires ffmpeg newer than git-2022-02-24 with libsvtav1, libvmaf, libopus enabled. Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin, windows Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <ins> { lib, rustPlatform, fetchFromGitHub, installShellFiles }: rustPlatform.buildRustPackage rec { pname = "ab-av1"; version = "0.7.14"; src = fetchFromGitHub { owner = "alexheretic"; repo = "ab-av1"; rev = "v${version}"; hash = "sha256-cDabGXNzusVnp4exINqUitEL1HnzSgpcRtYXU5pSRhY="; }; cargoHash = "sha256-sW/673orvK+mIUqTijpNh4YGd9ZrgSveGT6F1O5OYfI="; nativeBuildInputs = [ installShellFiles ]; postInstall = '' installShellCompletion --cmd ab-av1  --bash <($out/bin/ab-av1 print-completions bash)  --fish <($out/bin/ab-av1 print-completions fish)  --zsh <($out/bin/ab-av1 print-completions zsh) ''; meta = with lib; { description = "AV1 re-encoding using ffmpeg, svt-av1 & vmaf"; homepage = "https://github.com/alexheretic/ab-av1"; changelog = "https://github.com/alexheretic/ab-av1/blob/${src.rev}/CHANGELOG.md"; license = licenses.mit; maintainers = [ maintainers.marsam ]; mainProgram = "ab-av1"; }; } </ins>
Code change:
A clear and concise description of what the bug is. The integration seem to require the missing python module and currently fails with this error message: is provided by python . Adding to in the . Maybe this missing dependency could be resolved in pyowm as well. I would appreciate some input from somebody with more experience. Steps to reproduce the behavior: home-assistant with openweathermap component No Error message and working openweathermap component <!-- 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]:
PR
Please post the full stacktrace.
There also was an upstream issue that may be related:
The fix is to add to pyowm's dependencies.
ok. Thanks for your help. I will create another PR later

Related discussion:
text: <del> { lib , buildPythonPackage , fetchFromGitHub , geojson , pysocks , pythonOlder , requests , pytestCheckHook , pythonRelaxDepsHook </del> <ins> { lib, buildPythonPackage, fetchFromGitHub, geojson, pysocks, pythonOlder, requests, setuptools, pytestCheckHook, pythonRelaxDepsHook, </ins> }: buildPythonPackage rec { pname = "pyowm"; version = "3.3.0"; <del> format = "setuptools"; </del> <ins> pyproject = true; </ins> disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "csparpa"; <del> repo = pname; rev = version; </del> <ins> repo = "pyowm"; rev = "refs/tags/${version}"; </ins> hash = "sha256-cSOhm3aDksLBChZzgw1gjUjLQkElR2/xGFMOb9K9RME="; }; <del> pythonRelaxDeps = [ "geojson" ]; </del> <ins> pythonRelaxDeps = [ "geojson" ]; </ins> <del> nativeBuildInputs = [ pythonRelaxDepsHook ]; </del> <ins> build-system = [ setuptools ]; nativeBuildInputs = [ pythonRelaxDepsHook ]; </ins> <del> propagatedBuildInputs = [ </del> <ins> dependencies = [ </ins> geojson pysocks requests <ins> setuptools </ins> ]; <del> nativeCheckInputs = [ pytestCheckHook ]; </del> <ins> nativeCheckInputs = [ pytestCheckHook ]; </ins> # Run only tests which don't require network access <del> pytestFlagsArray = [ "tests/unit" ]; </del> <ins> pytestFlagsArray = [ "tests/unit" ]; </ins> <del> pythonImportsCheck = [ "pyowm" ]; </del> <ins> pythonImportsCheck = [ "pyowm" ]; </ins> meta = with lib; { description = "Python wrapper around the OpenWeatherMap web API"; homepage = "https://pyowm.readthedocs.io/"; <ins> changelog = "https://github.com/csparpa/pyowm/releases/tag/${version}"; </ins> license = licenses.mit; maintainers = with maintainers; [ fab ]; };
Code change:
OAuth2 Proxy's Nginx plugin used to forward and headers to downstream programs. This stopped working after I updated on unstable channel, which is potentially related to or . Steps to reproduce the behavior: up OAuth2 Proxy + Nginx up of header name . does not recognize the session More simply: up OAuth2 Proxy + Nginx or something similar the headers — and used to be present, but not anymore and are passed to downstream servers under Nginx. I have I went on upgrade of nixpkgs unstable from sometime late January to a few hours ago, which is what led me to the two PRs mentioned above. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
are you able to play around a bit and confirm if the changes mentioned introduced this regression?
yes. I can't really pin-point to what exactly since there were a lot of changes. Instead, I just have a local fork from (prior to the changes mentioned in the PRs above).
I have a pretty good idea what it could be.
Can you give a try? I didn't test it yet, so it could completely break everything and be completely insecure, just as warning.
fantastic work please let us know how it goes ‍
Sorry for the late reply, I haven't been able to have time to test it out. Now that I do, it seems like has been converted to . This won't be an easy find-and-replace for me to try in my setup, so I will have to find some time to do proper cleanup.

Related discussion:
text: } ++ (lib.mapAttrsToList (vhost: conf: { virtualHosts.${vhost} = { locations = { <ins> "/".extraConfig = '' # pass information via X-User and X-Email headers to backend, requires running with --set-xauthrequest flag proxy_set_header X-User  $user; proxy_set_header X-Email $email; # if you enabled --cookie-refresh, this is needed for it to work with auth_request add_header Set-Cookie $auth_cookie; ''; </ins> "/oauth2/auth" = let maybeQueryArg = name: value: if value == null then null