jiebi/CodeConvo huggingface dataset:
Change:
Hello there, I recently installed a wordpress theme named nebula on my wordpress site, using the the nixos options in services.wordpress. Anyways, when I tried to activate the nebula plugin it threw a bunch of errors, which I fixed with the extraConfig option: define('FS_METHOD', 'direct'); but, I keep on getting another error message: [Nebula] Directory indexing not disabled (at the time last checked). Visitors may be able to see file listings of directories such as the Includes URL or Content URL (and/or others)! Run an audit to re-scan » In order to try and fix this I tried some wordpress plugins that automatically disable directory indexing, but they can't find the .htaccess file in the /nix/store/ ? Any tips on how to fix this issue declaratively using the nixos options? Note, when other plugins are activate this directory indexing error is not thrown, so I'm not even sure if this is a security issue or not? Activate the Nebula plugin. Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
I think we should set this in the module by default. Because then as far as I remember the FTP upload dialog doesn't show and as it's readonly anyways that's just more logical for the user. Would need to test if it actually does directory indexes currently but we should probably set It's readonly anyways so that doesn't work. Most plugins probably don't check that. P.S.: The wordpress module is really broken see
Reviewing the module it looks like you want something like this: Please try that and let me know how it goes. But also keep in mind...
, Thanks! I tried out the configuration you mentioned and no error is being thrown anymore, which is great. But, that also caused another error to be thrown: Fatal error: Uncaught Error: arraydiff(): Argument ($array) must be of type array, bool given in /nix/store/7rip1dbvilj25rf4j9hn3az9q6mscfj3-wordpress- on line 197, Call stack: arraydiff() wp-content/themes/nebula- Nebula::dashboardnebulaataglance() wp- dometaboxes() wp- wp_dashboard() wp- I'm not sure if this error has to do with the configuration to disable directory indexing, or if it's an issue with the Nebula theme itself? Anyways, at least some good progress has been made with this issue. Thanks again for the help!
blind guess but maybe the plugin is not compatible with php8 yet
are we good to close this issue?
I think we should disable directory indexing in our module by default
are you able to make a PR for that?

Discussion:
DirectoryIndex index.php Require all granted <del> Options +FollowSymLinks </del> <ins> Options +FollowSymLinks -Indexes </ins> </Directory> # https://wordpress.org/support/article/hardening-wordpress/#securing-wp-config-php
Change:
During systemd-boot update step attempts to touch EFI variables, even when is set to . Steps to reproduce the behavior: NixOS 21.05 with systemd-boot and to NixOS 21.11 () switch fails with: An error is just an indication of update trying to touch EFI variables. (I have EFI vars touching disabled on that system because of some unrelated firmware breakage) Manually running properly finishes, further switches work fine. systemd-boot update should not touch EFI variables during upgrade. <!-- 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. Maintainer information:
I had a similar issue which I fixed by running "sudo nixos-rebuild --install-bootloader switch"
The fix for this got reverted in

Discussion:
if installed_version < available_version: print("updating systemd-boot from %s to %s" % (installed_version, available_version)) <del> subprocess.check_call(["@systemd@/bin/bootctl", "--esp-path=@efiSysMountPoint@", "update"]) </del> <ins> subprocess.check_call(["@systemd@/bin/bootctl", "--esp-path=@efiSysMountPoint@"] + bootctl_flags + ["update"]) </ins> os.makedirs("@efiSysMountPoint@/efi/nixos", exist_ok=True) os.makedirs("@efiSysMountPoint@/loader/entries", exist_ok=True)
Change:
<!-- 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: zk <!-- 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.8.0 desired version: 0.9.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
buildGoModule rec { pname = "zk"; <del> version = "0.8.0"; </del> <ins> version = "0.9.0"; </ins> src = fetchFromGitHub { owner = "mickael-menu"; repo = "zk"; rev = "v${version}"; <del> sha256 = "sha256-lTg5jB3krZWmCn3wWoAwzqBji1AyTTTVf/BphC7Mr5s="; </del> <ins> sha256 = "sha256-AXKIi70evf581lMwfbfxm8hFCzsnhKRQgnIEZQFS75A="; </ins> }; vendorSha256 = "sha256-m7QGv8Vx776TsN7QHXtO+yl3U1D573UMZVyg1B4UeIk=";
Change:
Project description Vim syntax highlight and indent definition for Coconut Metadata homepage URL: source URL: license: none platforms: vim
Blocked by
there shouldn't be any blocking anymore

Discussion:
meta.homepage = "https://github.com/neoclide/coc.nvim/"; }; <ins> coconut-vim = buildVimPluginFrom2Nix { pname = "coconut.vim"; version = "2017-10-10"; src = fetchFromGitHub { owner = "manicmaniac"; repo = "coconut.vim"; rev = "cea47739aab9f163d240d1609e7eea326fd55072"; sha256 = "03rq3lpplgywvm620jzx085l74180163q8gls4gjrad2fgm9n96n"; }; meta.homepage = "https://github.com/manicmaniac/coconut.vim/"; }; </ins> codi-vim = buildVimPluginFrom2Nix { pname = "codi.vim"; version = "2022-04-30";

https://github.com/coc-extensions/coc-svelte/,, https://github.com/iamcco/coc-tailwindcss/,, https://github.com/neoclide/coc.nvim/,release, <ins> https://github.com/manicmaniac/coconut.vim/,HEAD, </ins> https://github.com/metakirby5/codi.vim/,, https://github.com/tjdevries/colorbuddy.nvim/,, https://github.com/lilydjwg/colorizer/,,
Change:
does not build in nixpkgs-unstable, nixos-21.11 and master. The test phase fails with python import errors for emoji data. Thus gajim seems broken in current NixOS and branches. Steps to reproduce the behavior: (current head of nixos-21.11) Gajim builds without any errors. Possibly introduced by Please run and paste the result. Maintainer information:
Looks like it builds now in and
I confirm that after updating I got Gajim back.
Yup, can confirm. Works again, now.

Discussion:
<del> { lib, fetchurl, gettext, wrapGAppsHook </del> <ins> { lib, fetchurl, fetchFromGitLab, gettext, wrapGAppsHook </ins> # Native dependencies , python3, gtk3, gobject-introspection, gnome

gettext wrapGAppsHook ]; <ins> # Workaround for https://dev.gajim.org/gajim/gajim/-/issues/10719. # We don't use plugin release URL because it's updated in place. plugins = fetchFromGitLab { domain = "dev.gajim.org"; owner = "gajim"; repo = "gajim-plugins"; rev = "fea522e4360cec6ceacbf1df92644ab3343d4b99"; sha256 = "sha256-CmwEiLsdldoOfgHfWL/5hf/dp0HEDNAIlc5N0Np20KE="; }; postPatch = '' mkdir -p gajim/data/plugins cp -r $plugins/plugin_installer gajim/data/plugins ''; </ins> dontWrapGApps = true; preFixup = ''

checkPhase = '' xvfb-run dbus-run-session  --config-file=${dbus.daemon}/share/dbus-1/session.conf  <del> ${python3.interpreter} setup.py test </del> <ins> ${python3.interpreter} -m unittest discover -s test/unit -v ${python3.interpreter} -m unittest discover -s test/no_gui -v </ins> ''; # necessary for wrapGAppsHook
Change:
The documentation for states that setting the option to should cause a directory of fonts to be generated. However, this option is set on my system, but the system does not have a fonts directory: Enable in . Rebuild system. Observe lack of directory.System: (NixOS: , Ubuntu/Fedora: , ...) [twey nixos-version 16.09pre82105. (Flounder) Nix version: (run ) [twey nix-env --version nix-env (Nix) 1.11.2 Nixpkgs version: (run ) [twey nix-instantiate --eval '<nixpkgs' -A lib.nixpkgsVersion "16.09pre82105."
I can reproduce the issue
:+1:, same here, for a loooong time now (sorry for not reporting earlier).
BTW, what's this option good for?
It gives a place to point applications that want to know about fonts (e.g. LuaTeX). On 7 May 2016 11:20, Vladimír Čunát wrote:BTW, what's this option good for? —You are receiving this because you authored the thread.Reply to this email directly or view it on GitHub
I assumed everything uses fontconfig nowadays, but there may be some exceptions...
Could you please write this in (and not in as you said in the issue description)? Do you have the directory now?
I have this in and no directory.
I believe this is fixed by I don't use nor really care about this feature, though, so I have no idea whether linking into really does anything useful ...

Discussion:
let <del> fontDirs = config.fonts.fonts; localDefs = with pkgs.builderDefs; pkgs.builderDefs.passthru.function rec { src = "";/* put a fetchurl here */ buildInputs = [pkgs.xorg.mkfontdir pkgs.xorg.mkfontscale]; inherit fontDirs; installPhase = fullDepEntry (" list=''; for i in ${toString fontDirs} ; do if [ -d $i/ ]; then list="$list $i"; fi; done list=$(find $list -name fonts.dir -o -name '*.ttf' -o -name '*.otf'); fontDirs=''; for i in $list ; do fontDirs="$fontDirs $(dirname $i)"; done; mkdir -p $out/share/X11-fonts/; find $fontDirs -type f -o -type l | while read i; do j="${i##*/}" if ! test -e "$out/share/X11-fonts/${j}"; then ln -s "$i" "$out/share/X11-fonts/${j}"; fi; done; cd $out/share/X11-fonts/ rm fonts.dir rm fonts.scale rm fonts.alias mkfontdir mkfontscale cat $( find ${pkgs.xorg.fontalias}/ -name fonts.alias) >fonts.alias ") ["minInit" "addInputs"]; }; x11Fonts = with localDefs; stdenv.mkDerivation rec { name = "X11-fonts"; builder = writeScript (name + "-builder") (textClosure localDefs [installPhase doForceShare doPropagate]); }; </del> <ins> x11Fonts = pkgs.runCommand "X11-fonts" { } '' mkdir -p "$out/share/X11-fonts" find ${toString config.fonts.fonts}  ( -name fonts.dir -o -name '*.ttf' -o -name '*.otf' )  -exec ln -sf -t "$out/share/X11-fonts" '{}' ; cd "$out/share/X11-fonts" rm -f fonts.dir fonts.scale fonts.alias ${pkgs.xorg.mkfontdir}/bin/mkfontdir ${pkgs.xorg.mkfontscale}/bin/mkfontscale cat $(find ${pkgs.xorg.fontalias}/ -name fonts.alias) >fonts.alias ''; </ins> in

environment.systemPackages = [ x11Fonts ]; <ins> environment.pathsToLink = [ "/share/X11-fonts" ]; </ins> }; }
Change:
When enabling transcoding via NVENC I get the error below (see screenshots) I looked further into the transcoding logs and found that ffmpeg is erroring with this message: . I remember NVENC transcoding in the past. Steps to reproduce the behavior: jellyfin NVENC playback transcoding a video which requires transcoding Playback working with transcoding happening on the GPU instead of the CPU. ! ! I have an Nvidia GTX 950. output: (see screenshots:
I have the same issue, I tried to run the exact same command that jellyfin uses, using , but it works fine, so I don't know what's causing this
See my comment here: It is something with the systemd hardening we apply in nixpkgs for that module.
Thanks, I'll disable it on my system to make it work
Okay, for everyone waiting for this to be fixed ~upstream~, add this in your to fix NVDEC and NVENC:
Is this an upstream issue, though? It seems like only our hardening is at fault. (In case this sounds rude: I couldn't find a better way to word this, and my apologies.)
No, you're right I wrongly used the word "upstream", I meant "in nixos" Though in this case , but it only affect debian AFAIK, but they will probably have the same issues as us
can you please try the PR and confirm it solves the issue please?
I left

Discussion:
PrivateDevices = true; PrivateUsers = true; <del> ProtectClock = true; </del> <ins> # Disabled as it does not allow Jellyfin to interface with CUDA devices # ProtectClock = true; </ins> ProtectControlGroups = true; ProtectHostname = true; ProtectKernelLogs = true;

RestrictNamespaces = true; # AF_NETLINK needed because Jellyfin monitors the network connection <del> RestrictAddressFamilies = [ "AF_NETLINK" "AF_INET" "AF_INET6" ]; </del> <ins> RestrictAddressFamilies = [ "AF_NETLINK" "AF_INET" "AF_INET6" "AF_UNIX" ]; </ins> RestrictRealtime = true; RestrictSUIDSGID = true;
Change:
With the following nix channels: I see the following outputs: This causes a custom z3 build script I have that tries to install via to fail with: this might be related to ? But I'm not 100% sure <!-- 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.
My current hypothesis is that it has something to do with -- any ideas?
I think the problem was introduced by Fixed in

Discussion:
export CAML_LD_LIBRARY_PATH="''${CAML_LD_LIBRARY_PATH-}''${CAML_LD_LIBRARY_PATH:+:}''$1/lib/ocaml/${ocaml.version}/site-lib/stublibs" fi } <del> createOcamlDestDir () { </del> <ins> exportOcamlDestDir () { </ins> export OCAMLFIND_DESTDIR="''$out/lib/ocaml/${ocaml.version}/site-lib/" <ins> } createOcamlDestDir () { </ins> if test -n "''${createFindlibDestdir-}"; then mkdir -p $OCAMLFIND_DESTDIR fi } <ins> # run for every buildInput </ins> addEnvHooks "$targetOffset" addOCamlPath <del> preConfigureHooks+=(createOcamlDestDir) </del> <ins> # run before installPhase, even without buildInputs, and not in nix-shell preInstallHooks+=(createOcamlDestDir) # run even in nix-shell, and even without buildInputs addEnvHooks "$hostOffset" exportOcamlDestDir </ins> ''; meta = {
Change:
does not build aarch64-darwin as of . Steps to reproduce the behavior: out . on aarch64-darwin The build to succeed or the package to be marked as broken. n/a Full build log: <!-- 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.
Can you try with ?
Ah didn't realize this was a jemalloc failure at first. Sure, here's the result on Overriding with gives me a more substantial failure: Full build log:
From : LLVM 10.x is not compatible with aarch64-darwin and we can't use LLVM 11.x or later because of this upstream bug. So this issue is blocked until the upstream fixes
ISTM there is another issue present as aarch64-darwin as well, wrong detection of - see - adding to seems to help to build jemalloc with newer LLVM, but I am still getting test failures on aarch64-darwin.

Discussion:
{ lib , stdenv , fetchurl <ins> , fetchpatch </ins> # By default, jemalloc puts a je_ prefix onto all its symbols on OSX, which # then stops downstream builds (mariadb in particular) from detecting it. This # option should remove the prefix and give us a working jemalloc.

sha256 = "sha256-LbgtHnEZ3z5xt2QCGbbf6EeJvAU3mDw7esT3GJrs/qo="; }; <ins> patches = [ # fix tests under --with-jemalloc-prefix=, see https://github.com/jemalloc/jemalloc/pull/2340 (fetchpatch { url = "https://github.com/jemalloc/jemalloc/commit/d00ecee6a8dfa90afcb1bbc0858985c17bef6559.patch"; hash = "sha256-N5i4IxGJ4SSAgFiq5oGRnrNeegdk2flw9Sh2mP0yl4c="; }) ]; </ins> # see the comment on stripPrefix configureFlags = [] ++ lib.optional stripPrefix "--with-jemalloc-prefix="

jbigkit = callPackage ../development/libraries/jbigkit { }; <del> jemalloc = callPackage ../development/libraries/jemalloc { # tests fail with LLVM 11+ # https://github.com/jemalloc/jemalloc/issues/2091 stdenv = if stdenv.cc.isClang then llvmPackages_10.stdenv else stdenv; }; </del> <ins> jemalloc = callPackage ../development/libraries/jemalloc { }; </ins> jose = callPackage ../development/libraries/jose { };
Change:
I got this error message when running , as well as OpenCL hello-world programs with mesa (restored in ), and it fails to compile OpenCL kernels. Steps to reproduce the behavior: OpenCL by setting . . The error message shows up. The error shoudn't be shown, and compiling OpenCL kernels should work. It seems that it tried to find that file, but the path is ill-formatted. See the repeated path in the strace below. <details<summarystrace output</summary</detailsThe path is hardcoded in . <details<summaryxxd output</summary</detailsThe wrong include directory is the , which is generated by . I'm not knowledgeable enough to fix it, but I think this is close to the root of the problem. I'm using flakes on nixos-21.11. The command fails so it's not included.

Discussion:
nativeBuildInputs = [ cmake ninja python3 ]; buildInputs = [ llvm clang-unwrapped ]; strictDeps = true; <ins> cmakeFlags = [ "-DCMAKE_INSTALL_INCLUDEDIR=include" ]; </ins> meta = with lib; { homepage = "http://libclc.llvm.org/";
Change:
Steps to reproduce the behavior: xanmod kernel to upgrade system Clean upgrade As far as I can see, the issue is that xanmod kernel config has it set to built-in, whereas the common kernel config has it set to a module.
Also the fix needs to be backported to 21.11, as it's blocking upgrades.

Discussion:
# Graysky's additional CPU optimizations CC_OPTIMIZE_FOR_PERFORMANCE_O3 = yes; <del> # Android Ashmem and Binder IPC Driver as module for Anbox ASHMEM = module; ANDROID = yes; ANDROID_BINDER_IPC = module; ANDROID_BINDERFS = module; ANDROID_BINDER_DEVICES = freeform "binder,hwbinder,vndbinder"; </del> # Futex WAIT_MULTIPLE implementation for Wine / Proton Fsync. FUTEX = yes; FUTEX_PI = yes; <ins> # WineSync driver for fast kernel-backed Wine WINESYNC = module; </ins> }; extraMeta = {
Change:
Since the PR which I am unable to build Octoprint on my raspberrypi 4. Steps to reproduce the behavior: Use either or Octoprint builds successfully. This is the output of : This is the output of Octoprint maintainers: PR author: Original issue author: Please run and paste the result.
Can confirm this, I wasn't originally sure whether it is caused by my config, as I am cross compiling with binfmt+qemu.
Some further information: doesn't build on aarch64-linux either: notice the same path.. When looking at sarge I noticed a version bump from 0.1.7 to 0.1.7.post1 not long ago. Updating sarge locally enables me build sarge, as well as octoprint. I'll post a PR later on today with an updated sarge.
Short follow up: The reason the test fail, are a strict timeout setting (first for an echo command, second for a timeout test). Increasing the timeout make the test pass on raspberry pi and with binfmt/qemu.

Discussion:
buildPythonPackage rec { pname = "sarge"; <del> version = "0.1.7"; </del> <ins> version = "0.1.7.post1"; </ins> format = "setuptools"; src = fetchFromGitHub { owner = "vsajip"; repo = pname; rev = version; <del> sha256 = "sha256-E1alSDXj0oeyB6dN5PAtN62FPpMsCKb4R9DpfWdFtn0="; </del> <ins> sha256 = "sha256-bT1DbcQi+SbeRBsL7ILuQbSnAj3BBB4+FNl+Zek5xU4="; </ins> }; checkInputs = [ pytestCheckHook ]; <ins> disabledTests = [ # Aarch64-linux times out for these tests, so they need to be disabled. "test_timeout" "test_feeder" ]; </ins> pythonImportsCheck = [ "sarge" ];
Change:
has been broken on since with build log failures that look like (excerpting from ): Another patch , fixed a related issue but did not fix the keytar dependency on Darwin. Fortunately, adding the necessary frameworks as conditional-on-darwin nativeBuildInputs in a manner similar to the way that is by fixes things here too. (PR incoming once I finish writing it up.) (and as a courtesy, though I know she has recently stepped down from maintaining the vscode extension)

Discussion:
, esbuild , pkg-config , libsecret <ins> , stdenv , darwin </ins> , setDefaultServerPath ? true }:

jq moreutils esbuild # Required by `keytar`, which is a dependency of `vsce`. pkg-config libsecret <ins> ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.AppKit darwin.apple_sdk.frameworks.Security </ins> ]; # Follows https://github.com/rust-analyzer/rust-analyzer/blob/41949748a6123fd6061eb984a47f4fe780525e63/xtask/src/dist.rs#L39-L65
Change:
When searching on for "plasma integration" there are 2 different packages : and . Looking further to try and find a distinction, there's additionally a requires What are all these packages? Are they related? Aliases? Copies? would probably know more. I don't know if allows adding a description, but that or a comment in the files would be greatly appreciated.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Even if I have plasma-browser-integration in my , it seems that librewolf is not able to connect to the host ! EDIT: seems to work in mainline firefox. So it's a different issue. Sorry.
Old issue, but these all have congruent kde packages: The naming in Nixpkgs is simply mirroring the KDE naming convention.
It would be great if they had descriptions. Maybe I'll find some time to add it unless somebody beats me to the punch :)

Discussion:
pname = "kwayland-integration"; nativeBuildInputs = [ extra-cmake-modules wayland-scanner ]; buildInputs = [ kguiaddons kidletime kwindowsystem kwayland qtbase wayland-protocols wayland ]; <ins> meta = { description = "Integration plugins for various KDE frameworks for the Wayland windowing system"; homepage = "https://invent.kde.org/plasma/kwayland-integration"; }; </ins> }

kactivities plasma-workspace ]; <ins> meta = { description = "Components necessary to integrate browsers into the Plasma Desktop"; homepage = "https://community.kde.org/Plasma/Browser_Integration"; }; </ins> }

wayland-protocols plasma-wayland-protocols ]; <ins> meta = { description = "A set of plugins responsible for better integration of Qt applications when running on a KDE Plasma workspace"; homepage = "https://invent.kde.org/plasma/plasma-integration"; }; </ins> }
Change:
defines a package option, but does not use it in the service definition. Steps to reproduce the behavior: an alternative package to use system is ignored As there is an option to set an alternative package, this setting should be honored. The current version of pkgs.pgmanage is broken, which was the motivation to actually use the package option.

Discussion:
serviceConfig = { User         = pgmanage; Group        = pgmanage; <del> ExecStart    = "${pkgs.pgmanage}/sbin/pgmanage -c ${confFile}" + </del> <ins> ExecStart    = "${cfg.package}/sbin/pgmanage -c ${confFile}" + </ins> optionalString cfg.localOnly " --local-only=true"; }; };
Change:
<!-- 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: gvm-libs <!-- 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: 21.4.2 desired version: 21.4.3 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
stdenv.mkDerivation rec { pname = "gvm-libs"; <del> version = "21.4.2"; </del> <ins> version = "21.4.3"; </ins> src = fetchFromGitHub { owner = "greenbone"; repo = pname; rev = "v${version}"; <del> sha256 = "14v7z8ynd20s4pkhp2nc19n6gbmbh8yrn39yi2fbfm7gj28b52sx"; </del> <ins> sha256 = "sha256-1NVLGyUDUnOy3GYDtVyhGTvWOYoWp95EbkgTlFWuxE8="; </ins> }; nativeBuildInputs = [

zlib ]; <ins> cmakeFlags = [ "-DGVM_RUN_DIR=$out/run/gvm" ]; </ins> meta = with lib; { description = "Libraries module for the Greenbone Vulnerability Management Solution"; homepage = "https://github.com/greenbone/gvm-libs";