jiebi/CodeConvo huggingface dataset:
Code change:
{ mkDerivation, lib, cmake, xorg, plasma-framework, plasma-wayland-protocols, fetchFromGitLab <del> , extra-cmake-modules, karchive, kwindowsystem, qtx11extras, qtwayland, kcrash, knewstuff, wayland }: </del> <ins> , extra-cmake-modules, karchive, kwindowsystem, qtx11extras, qtwayland, kcrash, knewstuff , wayland, plasma-workspace }: </ins> mkDerivation rec { pname = "latte-dock"; <del> version = "unstable-2022-09-06"; </del> <ins> version = "unstable-2023-03-31"; </ins> src = fetchFromGitLab { domain = "invent.kde.org"; owner = "plasma"; repo = "latte-dock"; <del> rev = "cd36798a61a37652eb549d7dfcdf06d2028eddc4"; sha256 = "sha256-X2PzI2XJje4DpPh7gTtYnMIwerR1IDY53HImvEtFmF4="; </del> <ins> rev = "4f93251d8c635c6150483ecb321eb276f34d4280"; sha256 = "sha256-oEfKfsVIAmYgQ7+WyBEQfVpI4IndWhYXWBsJE8bNNyI="; </ins> }; <del> buildInputs = [ plasma-framework plasma-wayland-protocols qtwayland xorg.libpthreadstubs xorg.libXdmcp xorg.libSM wayland ]; </del> <ins> buildInputs = [ plasma-framework plasma-wayland-protocols qtwayland xorg.libpthreadstubs xorg.libXdmcp xorg.libSM wayland plasma-workspace ]; </ins> nativeBuildInputs = [ extra-cmake-modules cmake karchive kwindowsystem qtx11extras kcrash knewstuff ];

Related discussion:
text: My config is pretty generic too, especially in the VM, I installed NixOS with KDE Plasma, latte-dock in system packages and not much more. I actually switched channel to unstable to try with plasma 5.27, but apart from that I'm basically on default nix config. I did slightly more configuration on my main NixOS install, 22.11, but get same behavior in both cases. Debug symbols seems painful on NixOS. Unsure if I will do that now. Thank you for the help. I use X11 too.
Ok, so after reading the suggested , I enabled and followed the instructions of the option I have and The part for plasma-workspace seems to work fine, but the one for qt5 givers this:
To reproduce the bug described in this issue, a simple way is this: the official NixOS virtualbox ova from (22.11.2939. at the date of writing this) it in VirtualBox the vm konsole will segfault will run latte-dock and you will see that clicking on items in the dock does nothing
I also tried to update the vm to unstable still segfaults, only that the version shown is 5.27.2 still nothing happens when clicking on items in the dock
Again, this seems like a Plasma bug, possibly due to VirtualBox video drivers or something.
Code change:
<del> { lib , stdenv , fetchFromGitHub , emptyDirectory , writeText , makeWrapper , gradle , jdk21 , llvmPackages }: let gradleInit = writeText "init.gradle" '' logger.lifecycle 'Replacing Maven repositories with empty directory...' gradle.projectsLoaded { rootProject.allprojects { buildscript { repositories { clear() maven { url '${emptyDirectory}' } } } repositories { clear() maven { url '${emptyDirectory}' } } } } settingsEvaluated { settings -> settings.pluginManagement { repositories { maven { url '${emptyDirectory}' } } } } ''; in stdenv.mkDerivation { pname = "jextract"; version = "unstable-2023-11-27"; src = fetchFromGitHub { owner = "openjdk"; repo = "jextract"; rev = "8730fcf05c229d035b0db52ee6bd82622e9d03e9"; # Update jextract 21 with latest fixes hash = "sha256-Wct/yx5C0EjDtDyXNYDH5LRmrfq7islXbPVIGBR6x5Y="; }; nativeBuildInputs = [ gradle makeWrapper ]; env = { ORG_GRADLE_PROJECT_llvm_home = llvmPackages.libclang.lib; ORG_GRADLE_PROJECT_jdk21_home = jdk21; }; buildPhase = '' runHook preBuild export GRADLE_USER_HOME=$(mktemp -d) gradle --console plain --init-script "${gradleInit}" assemble runHook postBuild ''; doCheck = true; checkPhase = '' runHook preCheck gradle --console plain --init-script "${gradleInit}" verify runHook postCheck ''; installPhase = '' runHook preInstall mkdir -p $out/opt/ cp -r ./build/jextract $out/opt/jextract runHook postInstall ''; postFixup = '' makeWrapper "$out/opt/jextract/bin/jextract" "$out/bin/jextract" ''; meta = with lib; { description = "A tool which mechanically generates Java bindings from a native library headers"; mainProgram = "jextract"; homepage = "https://github.com/openjdk/jextract"; license = licenses.gpl2Only; maintainers = with maintainers; [ sharzy ]; }; } </del>

Related discussion:
text: And now that Panama/FF&M is final, I'm hoping it will be possible to use jextract 22 to build headers for JDK 23+. Newer versions of jextract might offer improvements, but headers generated for JDK 22 should work wth JDK 23+ (I don't know what guarantees the JDK makes for that, but this seems a reasonable conclusion given a stable API.)
Nice to hear that, and thanks for your work! IMO, I think it's worth. The point is that JDK 21 is a LTS version, some downstreams prefer to use a LTS version of JDK to develop their projects. For them, if we don't keep JDK 21's , this will be unavailable to them unless they give up on choosing LTS and do some extra effort - porting their project to a newer version of JDK.
I agree. But I also strongly encourage new projects to start with JDK 22 and existing projects to migrate as quickly as possible. Having to make sure "preview mode" is set in the compiler and at runtime can cause various problems with tools and the output of the latest is significantly improved. In general, it's much better to be using a non-LTS JDK with a non-preview feature than and LTS JDK with a preview feature. I migrated my project recently and wish I had migrated to JDK 22 much earlier.
PR has been merged. I gave it a quick test on macOS/aarch64 and it seems to be working. (I used it to build which uses JDK 22 and Panama via Gradle's Java toolchains)
Code change:
<ins> { lib , stdenv , fetchFromGitHub , libaio }: stdenv.mkDerivation rec { pname = "stressapptest"; version = "1.0.9"; src = fetchFromGitHub { owner = pname; repo = pname; rev = "v${version}"; sha256 = "1qzj6h6adx042rb9aiz916jna269whibvj5ys4p5nwdp17fqh922"; }; buildInputs = [ libaio ]; meta = with lib; { description = "Userspace memory and IO stress test tool"; homepage = "https://github.com/stressapptest/stressapptest"; license = with licenses; [ asl20 ]; maintainers = with lib.maintainers; [ fab ]; platforms = platforms.unix; }; } </ins>

Related discussion:
text: Stressful Application Test (or stressapptest, its unix name) is a memory interface test. It tries to maximize randomized traffic to memory from processor and I/O, with the intent of creating a realistic high load situation in order to test the existing hardware devices in a computer. It has been used at Google for some time [...] In my experience it's an absolute monster in finding random memory errors that don't show up over weeks of real world usage. Until ECC is commonplace, running this software is necessary. Metadata source URL: license: Apache 2.0 platforms: linux
could you please give a try?
worked no problem, thanks a lot!
Code change:
ln -sfv "${nodejs}/include" "$HOME/.node-gyp/${nodejs.version}" export npm_config_nodedir=${nodejs} <del> pushd redisinsight </del> # Build the sqlite3 package. <ins> pushd redisinsight </ins> npm_config_node_gyp="${buildPackages.nodejs}/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" npm rebuild --verbose --sqlite=${sqlite.dev} sqlite3 popd <ins> # Build node-sass LIBSASS_EXT=auto npm rebuild --verbose node-sass </ins> substituteInPlace redisinsight/api/config/default.ts  <del> --replace "process['resourcesPath']" ""$out/share/redisinsight""  </del> <ins> --replace-fail "process['resourcesPath']" ""$out/share/redisinsight""  # has irrelevant files rm -r resources/app </ins> runHook postConfigure ''; buildPhase = '' runHook preBuild <del> yarn config --offline set yarn-offline-mirror $offlineCache pushd node_modules/node-sass LIBSASS_EXT=auto yarn run build --offline popd </del> <ins> yarn config --offline set yarn-offline-mirror ${finalAttrs.offlineCache} </ins> yarn --offline build:prod yarn --offline electron-builder  <del> --dir ${if stdenv.isDarwin then "--macos" else "--linux"} ${if stdenv.hostPlatform.isAarch64 then "--arm64" else "--x64"}  </del> <ins> --dir  </ins> -c.electronDist=${electron}/libexec/electron  -c.electronVersion=${electron.version}

Related discussion:
text: Steps to reproduce the behavior: -shell -p redisinsight Multiple of these errors Full log - Add any other context about the problem here. <!-- 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]:
Code change:
<ins> { lib, stdenv, fetchurl, fetchFromGitHub, jdk17_headless, jre17_minimal, gradle_7, bash, coreutils, substituteAll, nixosTests, fetchpatch, writeText, }: let gradle = gradle_7; jdk = jdk17_headless; # Reduce closure size jre = jre17_minimal.override { modules = [ "java.base" "java.logging" "java.naming" "java.sql" "java.desktop" "java.management" ]; jdk = jdk17_headless; }; version = "01497"; freenet_ext = fetchurl { url = "https://github.com/freenet/fred/releases/download/build01495/freenet-ext.jar"; sha256 = "sha256-MvKz1r7t9UE36i+aPr72dmbXafCWawjNF/19tZuk158="; }; seednodes = fetchFromGitHub { name = "freenet-seednodes"; owner = "hyphanet"; repo = "seedrefs"; rev = "9df1bf93ab64aba634bdfc5f4d0e960571ce4ba5"; hash = "sha256-nvwJvKw5IPhItPe4k/jnOGaa8H4DtOi8XxKFOKFMAuY="; postFetch = '' cat $out/* > $out/seednodes.fref ''; }; patches = [ # gradle 7 support # https://github.com/freenet/fred/pull/827 (fetchpatch { url = "https://github.com/freenet/fred/commit/8991303493f2c0d9933f645337f0a7a5a979e70a.patch"; sha256 = "sha256-T1zymxRTADVhhwp2TyB+BC/J4gZsT/CUuMrT4COlpTY="; }) ]; in stdenv.mkDerivation rec { pname = "freenet"; inherit version patches; src = fetchFromGitHub { owner = "freenet"; repo = "fred"; rev = "refs/tags/build${version}"; hash = "sha256-pywNPekofF/QotNVF28McojqK7c1Zzucds5rWV0R7BQ="; }; postPatch = '' rm gradle/verification-{keyring.keys,metadata.xml} ''; nativeBuildInputs = [ gradle jdk ]; wrapper = substituteAll { src = ./freenetWrapper; inherit bash coreutils jre seednodes ; }; mitmCache = gradle.fetchDeps { inherit pname; data = ./deps.json; }; # using reproducible archives breaks the build gradleInitScript = writeText "empty-init-script.gradle" ""; gradleFlags = [ "-Dorg.gradle.java.home=${jdk}" ]; gradleBuildTask = "jar"; installPhase = '' runHook preInstall install -Dm644 build/libs/freenet.jar $out/share/freenet/freenet.jar ln -s ${freenet_ext} $out/share/freenet/freenet-ext.jar mkdir -p $out/bin install -Dm755 ${wrapper} $out/bin/freenet export CLASSPATH="$(find ${mitmCache} -name "*.jar"| sort | grep -v bcprov-jdk15on-1.48.jar|tr $'n' :):$out/share/freenet/freenet-ext.jar:$out/share/freenet/freenet.jar" substituteInPlace $out/bin/freenet  --subst-var-by CLASSPATH "$CLASSPATH" runHook postInstall ''; passthru.tests = { inherit (nixosTests) freenet; }; meta = { description = "Decentralised and censorship-resistant network"; homepage = "https://freenetproject.org/"; sourceProvenance = with lib.sourceTypes; [ binaryBytecode ]; license = lib.licenses.gpl2Plus; maintainers = with lib.maintainers; [ nagy ]; platforms = with lib.platforms; linux; changelog = "https://github.com/freenet/fred/blob/build${version}/NEWS.md"; }; } </ins>

Related discussion:
text: Freenet installs successfully but fails to run for both the service and the package with Steps to reproduce the behavior: Failure with Or alternatively with the service = true; to config For Freenet to start and be able to access setup wizard on 127.0.0.1:8888 Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
fi if [ -z "$crossConfig" ]; then <del> export CC=@real_cc@ export CXX=@real_cxx@ </del> <ins> ENV_PREFIX="" </ins> else <del> export BUILD_CC=@real_cc@ export BUILD_CXX=@real_cxx@ </del> <ins> ENV_PREFIX="BUILD_" </ins> fi <ins> export NIX_${ENV_PREFIX}CC=@out@ export ${ENV_PREFIX}CC=@named_cc@ export ${ENV_PREFIX}CXX=@named_cxx@ for CMD in  cpp  ar as nm objcopy ranlib strip strings size ld windres do if PATH=$_PATH type -p "@binPrefix@$CMD" > /dev/null then export "${ENV_PREFIX}${CMD^^}=@binPrefix@${CMD}"; fi done # No local scope available for sourced files unset ENV_PREFIX </ins>

Related discussion:
text: Optipng crashes with a segmentation fault on current as of . points to the library used to throw/catch exceptions. relevant source: Automatic points to being the first bad revision. However, I don't have enough knowledge of this piece of nix to understand why it causes optipng to fail in the . System: nixos-master Nix version: 1.11.11 Nixpkgs version: Sandboxing enabled: yes CC
Reading into the causing commit's comments made me try which seems to work around the issue. However, I'm hesitant to commit this as a fix without understanding the issue here.
So some packages use the C compiler instead of linker directly to link. Nixpkgs's cc-wrapper is aware of this, for example, with separate and environment variables. Classic make builtin rules however only have , , , and , so then either in a configure script or make itself they seem to default to , but manually specifying breaks this. Manually specifying , however, avoids that pitfall, and, unlike , will also work for cross compilation.
Here's a blurb from optipng's script: If I understand your comment, it looks like optipng's build system is doing precisely what you describe: So when isn't set, it defaults to configuring the such that it uses as the linker, and I suppose the theory is that they depend on behavior available when invoking through e.g. (though I don't know precisely what that may be). It would seem reasonable take the (on a per package basis) approach as a solution. I think this can safely be considered a bug in the upstream packages' build systems.
Probably the use of to pass actual ld flags, e.g. .
I implemented the workaround in . Feel free to reopen this if you don't think the fix to be adequate.
Code change:
fi if [ -z "$crossConfig" ]; then <del> export CC=@real_cc@ export CXX=@real_cxx@ </del> <ins> ENV_PREFIX="" </ins> else <del> export BUILD_CC=@real_cc@ export BUILD_CXX=@real_cxx@ </del> <ins> ENV_PREFIX="BUILD_" </ins> fi <ins> export NIX_${ENV_PREFIX}CC=@out@ export ${ENV_PREFIX}CC=@named_cc@ export ${ENV_PREFIX}CXX=@named_cxx@ for CMD in  cpp  ar as nm objcopy ranlib strip strings size ld windres do if PATH=$_PATH type -p "@binPrefix@$CMD" > /dev/null then export "${ENV_PREFIX}${CMD^^}=@binPrefix@${CMD}"; fi done # No local scope available for sourced files unset ENV_PREFIX </ins>

Related discussion:
text: gcc5 and the dependant gfortran5 packages are failing as of 31 July Failures: ] ] Building either package using or fails. System: (MacOS 10.11.6 and MacOS 10.12.6, both nix-multiuser install) Nix version: (1.11.13) Nixpkgs version: (17.09pre-git) Sandboxing enabled: (relaxed)
has been looking into this but it seems pretty mysterious so far
git-bisect is pretty neat
cc
This is also needed to fix things that depend on gcc
Code change:
nativeBuildInputs = [ cmake curl ]; buildInputs = [ <del> aws-crt-cpp </del> curl openssl zlib ] ++ lib.optionals (stdenv.isDarwin && ((builtins.elem "text-to-speech" apis) ||

Related discussion:
text: When I update nix I can't copy to our binay cache anymore. All I get is I bisected nixpkgs and found that the bug was introduced by . Run The parent commit works: This error here is fine because our cache has a different name of course. Please run and paste the result.
Just wondered if here is the right place for the issue but I’m quite lost on this. Maybe this is a nix bug?
No you're correct to open this here, this is a good place to start. I'll try to bisect further to see which aws-sdk-cpp commit broke this functionality, hopefully that will tell us more about how to proceed.
Bisected to , but unfortunately the commit is very large so I don't see an obvious cause. Maybe it's best to take this upstream to the Nix repo now.
Thanks for reporting, and sorry if this broke your workflow. I've bookmarked this issue and I'm going to look into adding an installCheck regression test to ensure s3 stays functional on future updates.
Thank you all for the quick response. This was a really sneaky one. Luckily nix allows rollbacks. That would be great. I’m sorry I cannot think of anything better than checking the error message of . When I do I let you know.
Code change:
let pname = "ollama"; # don't forget to invalidate all hashes each update <del> version = "0.1.38"; </del> <ins> version = "0.1.39"; </ins> src = fetchFromGitHub { <del> owner = "jmorganca"; </del> <ins> owner = "ollama"; </ins> repo = "ollama"; rev = "v${version}"; <del> hash = "sha256-9HHR48gqETYVJgIaDH8s/yHTrDPEmHm80shpDNS+6hY="; </del> <ins> hash = "sha256-OYWHpPvnIgdjDjpcV8BKnr5cq6eJzBsAOGZmaVBBalQ="; </ins> fetchSubmodules = true; }; <del> vendorHash = "sha256-zOQGhNcGNlQppTqZdPfx+y4fUrxH0NOUl38FN8J6ffE="; </del> <ins> vendorHash = "sha256-bomHpEcoHG/xUGgzrFXB9D3np0ainTX066SCMY+NdnA="; </ins> # ollama's patches of llama.cpp's example server # `ollama/llm/generate/gen_common.sh` -> "apply temporary patches until fix is upstream" # each update, these patches should be synchronized with the contents of `ollama/llm/patches/` llamacppPatches = [ <ins> (preparePatch "01-load-progress.diff" "sha256-3QxyKX1n5NeMLU8d7wI/96wCM1Cvb5X5sQL5CFhMFo4=") </ins> (preparePatch "02-clip-log.diff" "sha256-rMWbl3QgrPlhisTeHwD7EnGRJyOhLB4UeS7rqa0tdXM=") <del> (preparePatch "03-load_exception.diff" "sha256-1DfNahFYYxqlx4E4pwMKQpL+XR0bibYnDFGt6dCL4TM=") </del> <ins> (preparePatch "03-load_exception.diff" "sha256-0XfMtMyg17oihqSFDBakBtAF0JwhsR188D+cOodgvDk=") </ins> (preparePatch "04-metal.diff" "sha256-Ne8J9R8NndUosSK0qoMvFfKNwqV5xhhce1nSoYrZo7Y=") <del> (preparePatch "05-clip-fix.diff" "sha256-rCc3xNuJR11OkyiXuau8y46hb+KYk40ZqH1Llq+lqWc=") </del> <ins> (preparePatch "05-default-pretokenizer.diff" "sha256-8ffYnl9kMHEZ05e5CqryYJLdJ6/EEQJSlW6e/IgaU2Q=") </ins> ]; preparePatch = patch: hash: fetchpatch {

Related discussion:
text: Package name: Latest released version: 0.1.39 <!-- Search your package here: --- Current version on the unstable channel: 0.1.38 Current version on the stable/release channel: 0.1.28 <!-- 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 (sorry!) Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
--set-default MONO_GC_PARAMS "nursery-size=64m"  --add-flags "$out/lib/mono/msbuild/15.0/bin/MSBuild.dll" <del> ln -s $(find ${dotnet-sdk} -name libhostfxr.so) $out/lib/mono/msbuild/Current/bin/SdkResolvers/Microsoft.DotNet.MSBuildSdkResolver/ </del> <ins> ln -s $(find ${dotnet-sdk} -name libhostfxr${sharedLibrary}) $out/lib/mono/msbuild/Current/bin/SdkResolvers/Microsoft.DotNet.MSBuildSdkResolver/ </ins> ''; doInstallCheck = true;

Related discussion:
text: Steps to reproduce the behavior: msbuild Trying to build msbuild on a mac fails. <!-- 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.
Code change:
if test -n "$compressImage"; then echo "Compressing image..." <del> zstd -T$NIX_BUILD_CORES $out/iso/$isoName </del> <ins> zstd -T$NIX_BUILD_CORES --rm $out/iso/$isoName </ins> fi mkdir -p $out/nix-support

Related discussion:
text: Describe the bug Size of aarch64 sd_image has suddenly blown up a lot. whereas on commit it was To Reproduce Hydra: - - This blocks the channel ATM.
It seems this is caused by my PR here: We switched to , but does not erase the original file, while does. I created PR which hopefully fixes this by passing to .
Code change:
# Requires network access (actually some data is loaded via `skimage._shared.testing.fetch` in the global scope, which calls `pytest.skip` when a network is unaccessible, leading to a pytest collection error). "${installedPackageRoot}/skimage/filters/rank/tests/test_rank.py" ]; <del> pytestFlagsArray = [ "${installedPackageRoot}" "--pyargs" "skimage" ] ++ builtins.map (testid: "--deselect=" + testid) [ </del> <ins> pytestFlagsArray = [ "${installedPackageRoot}" "--pyargs" "skimage" ] ++ builtins.map (testid: "--deselect=" + testid) ([ </ins> # These tests require network access "skimage/data/test_data.py::test_skin" "skimage/data/tests/test_data.py::test_skin" "skimage/io/tests/test_io.py::test_imread_http_url" "skimage/restoration/tests/test_rolling_ball.py::test_ndim" <del> ]; </del> <ins> ] ++ lib.optionals stdenv.isDarwin [ # Matplotlib tests are broken inside darwin sandbox "skimage/feature/tests/test_util.py::test_plot_matches" "skimage/filters/tests/test_thresholding.py::TestSimpleImage::test_try_all_threshold" "skimage/io/tests/test_mpl_imshow.py::" ]); </ins> # Check cythonized modules pythonImportsCheck = [

Related discussion:
text: On with , the tests fails with the following error: Steps to reproduce the behavior: -shell -p python3Packages.scikitimage The tests run without errors. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- system: host os: multi-user?: sandbox: version: channels(smaret): nixpkgs: