jiebi/CodeConvo huggingface dataset:
Change:
]; # this will most likely need to be updated when azuredatastudio's version changes <del> sqltoolsservicePath = "${targetPath}/resources/app/extensions/mssql/sqltoolsservice/Linux/4.7.1.6"; </del> <ins> sqltoolsservicePath = "${targetPath}/resources/app/extensions/mssql/sqltoolsservice/Linux/4.11.1.1"; </ins> rpath = lib.concatStringsSep ":" [ (lib.makeLibraryPath [

Discussion:
The src URL () for Azure Data Studio redirects to latest version (1.48.1), not the specified version (1.44.1), leading to build failure due to hash mismatch. i.e. redirects to . Steps to reproduce the behavior: Specified version of Azure Data Studio should be downloaded, verified and installed. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
''; }; <ins> localNetworkGameTransfers.openFirewall = mkOption { type = types.bool; default = false; description = lib.mdDoc '' Open ports in the firewall for Steam Local Network Game Transfers. ''; }; </ins> gamescopeSession = mkOption { description = mdDoc "Run a GameScope driven Steam session from your display-manager"; default = {};

Discussion:
Valve has the ability to send game installs from one machine to another on the same network. This newer functionality requires port /TCP to be open on the host machine. describes the feature and mentions the port. Steps to reproduce the behavior: two computers running Steam. host Steam on NixOS needs to have the game fully downloaded. client Steam needs to be on the same network as the host. network transfer feature has to be enabled on both machines. downloading the game on the client that is downloaded on the host. tries to establish the transfer but never sends data. Either enabling Steam via should open this new port automatically or a new setting of = true; should be created to open the port.
I did some testing and it seems that it requires at least one other Steam TCP/UDP port to be open besides the /TCP, as just opening that port had the same transfer failure. I ended up opening ports: TCP , - UDP 3478, 4379-4380, - It works with those ports open. I will try to find which other port is required for it to function.
The following makes local transfers work on my machine: The port was taken from this Steam community comment:
Change:
[[package]] name = "zed" <del> version = "0.149.3" </del> <ins> version = "0.149.5" </ins> dependencies = [ "activity_indicator", "anyhow",

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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]:
Change:
the-powder-toy = callPackage ../games/the-powder-toy { lua = lua5_1; <ins> inherit (darwin.apple_sdk.frameworks) Cocoa; </ins> }; tbe = libsForQt5.callPackage ../games/the-butterfly-effect { };

Discussion:
the-powder-toy segfaults when trying to execute it on aarch64-darwin. It should run and launch the game.
It is fixed upstream from snapshot-231. Should we bump the version or make a patch?
fix (update to latest commit) in
Change:
fi # A place to drop temporary stuff. <ins> tmpdir="$(mktemp -d -p $mountPoint)" </ins> trap "rm -rf $tmpdir" EXIT <del> tmpdir="$(mktemp -d)" </del> <ins> # store temporary files on target filesystem by default export TMPDIR=${TMPDIR:-$tmpdir} </ins> sub="auto?trusted=1"

Discussion:
Describe the bug Each run of leaves a temporary directory in $TMPDIR. To Reproduce Use , then a new temporary directory is in $TMPDIR. Expected behavior The temporary directory is removed. Additional context This code is likely wrong: The reference should be escaped or defined before the .
Change:
}: let dep = { pname, version, hash, rev ? "v${version}", buildInputs ? [ ] }: stdenv.mkDerivation { inherit pname version;

Discussion:
Package name: dbus-broker Latest released version: v33 <!-- Search your package here: --- Current version on the unstable channel: v32 Current version on the stable/release channel: v32 <!-- 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 Thanks :) <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
Change:
, "less-plugin-clean-css" , "live-server" , "livedown" <ins> , "localtunnel" </ins> , "lodash" , "lua-fmt" , "lv_font_conv"

Discussion:
Project description Localtunnel allows you to easily share a web service on your local development machine without messing with DNS and firewall settings. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, nodejs
Change:
buildPythonPackage rec { pname = "databricks-connect"; <del> version = "11.3.6"; </del> <ins> version = "11.3.26"; </ins> format = "setuptools"; disabled = pythonOlder "3.7"; src = fetchPypi { inherit pname version; <del> hash = "sha256-kAUBA9V1st5UxXihrXQjyk+1ahsum/VEcNfDK1he/Pc="; </del> <ins> hash = "sha256-YjUY4i8PtXc+fWcGjvnRbZkiINprKcS1K9HT5+86E8c="; </ins> }; sourceRoot = ".";

Discussion:
Steps to reproduce the behavior: 3Packages.databricks-connect 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]:
Seems like that version is removed from pypi: Next not yet yanked version is 11.3.25:
thank you for you response, do you use nixpkgs and databricks-connect ?
Not using it myself. But I thought it might be worth commenting that other than updating version to currently existing one on pypi there is not much that can be done (and regularly do check/update, probably manually because of unfree license). Because pypi allows direct removal of versions and as you can see from "release history" there are a lot of versions that databricks removed.
I might try to get 11.3.25 working, otherwise without any users/maintainers interest it will be just marked as broken
Change:
passthru.updateScript = nix-update-script { }; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "Implementation of the Stateless OpenPGP Command Line Interface using Sequoia"; homepage = "https://docs.sequoia-pgp.org/sqop/"; <del> license = licenses.gpl2Plus; maintainers = with maintainers; [ doronbehar ]; </del> <ins> license = lib.licenses.gpl2Plus; maintainers = with lib.maintainers; [ doronbehar ]; </ins> mainProgram = "sqop"; }; }

Discussion:
Steps to reproduce the behavior: Observed: Full checkPhase log (copied from Garnix): 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. --- system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The checkPhase still fails with this PR applied, but it is a different error: Error: While creating /homeless- Caused by: Permission denied (os error 13)
Thanks for the report (I thought I rebuilt it successfully before I opened the PR). Now should be ready now (the failing test is skipped, and an upstream issue was created).
Change:
# Security settings dolibarr_main_prod = true; <del> dolibarr_main_force_https = vhostCfg.forceSSL; </del> <ins> dolibarr_main_force_https = vhostCfg.forceSSL or false; </ins> dolibarr_main_restrict_os_commands = "${pkgs.mariadb}/bin/mysqldump, ${pkgs.mariadb}/bin/mysql"; dolibarr_nocsrfcheck = false; dolibarr_main_instance_unique_id = ''

Discussion:
I would like to use the dolibarr module without nginx. I plan to use caddy instead. In my NixOS configuration, I have . All the nginx-related settings in the dolibarr module are ignored if which is good. However, this line is not: I get the following output: This happens with simply adding to my config.
Opened for the fix, as I do not use any other web server beyond NGINX, I have no plan to maintain advanced integrations of other web servers, if you are interested into this, I will need another co-maintainer :).
Change:
{ runCommand, fetchFromGitHub, git }: let <del> version = "2016-03-10"; rev = "5e78a14c1b82522e019586687f7dbfd36ce67fa5"; </del> <ins> version = "2016-03-22"; rev = "f28cdedb698cf76f513fb4514b5ed2892ec89b2f"; </ins> src = fetchFromGitHub { inherit rev; owner = "rust-lang"; repo = "crates.io-index"; <del> sha256 = "0hzhfhlv8qbqb5nm9id36dlzvhalhlrh2k82ks67ap4mdcs3c650"; </del> <ins> sha256 = "05j43pgdlf554y9r781xdc5la55anwiq6k7vml9icak699ywfxqq"; </ins> }; in

Discussion:
To make sure that we are on the same page: Kernel: (run ) 4.5.0 System: (NixOS: , Ubuntu/Fedora: , ...) (Flounder) Nix version: (run ) 1.11.2 Nixpkgs version: (run ) During testing of I managed to get at least two different hashes for . After some discussion with it seems that this derivation can produce non-deterministic output. Hashes of outputs are always the same. They are not. Build several times.
How would one work around that? It basically means the system cannot be rebuild :cry:
cc
You can work around it by updating SHA checksum in the affected package locally.
:confused: Is there any documentation you could point me too. I know how I would to it for packages that I install as a user: out nixpkgs repo the last commit that build for unstable on hydra that out the exa's file 5 run But I think it's also possible to override it in a nix expression, like the one in , since I installed it as a systems package. The thing is that all ressources I find either explain how to do it for that they link to
I changed my to include that: but to no avail :confused:
Sadly we don't have a mechanism to override (it needs to be supported). However, you can rebuild your whole NixOS from a modified repository:
Another way to do it is to call patched nixpkgs from your :
Thanks for your help! I really appreciate it. I tried your last suggestions, but that leads to: It looks like some network hick up, but I tried it multiple times and I opened the github repository from the same machine and it loads fine. Maybe it has something to do with this line: ?
Hm, unfortunately I have no idea what's going on -- you've fixed the hash, so it seems like another problem in .
Still thanks for the help. I learned a lot!
depends on a git repository in which doesn't work with
maybe fetchcargo could take an argument to pin git-based dependencies on a certain commit?
I can confirm that this is still an issue when building : through AUR/exa-git. cc
Are there any updates on this issue, please?
Should be fixed.
Change:
{ "invidious": { <del> "rev": "99a5e9cbc44daa4555f36b43bc4b7246aee454c9", "hash": "sha256-ep/umuNxTvdPXtJgI3KNt0h5xc1O38wQz1+OsVYOzfE=", "version": "0.20.1-unstable-2024-03-08" </del> <ins> "rev": "08390acd0c17875fddb84cabba54197a5b5740e4", "hash": "sha256-75C/ImX/PYikVdSO4rZM/aYyEgx6pU90BHNeRFfcsDM=", "version": "0.20.1-unstable-2024-03-31" </ins> }, "videojs": { "hash": "sha256-jED3zsDkPN8i6GhBBJwnsHujbuwlHdsVpVqa1/pzSH4="

Discussion:
Package name: invidious Latest released version: 0.20.1-unstable-2024-03-31 Current version on the unstable channel: 0.20.1-unstable-2024-03-08 Current version on the stable/release channel: 0.20.1-unstable-2024-03-08 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
As invidious in the old version is broken as it cannot fetch videos anymore, please update to latest version and latest commit: Relevant issue:
Here's an overlay with the fix until then:
Change:
fi '') ] ++ [ <del> "--chdir" "${unwrapped}/lib/libreoffice/program" </del> "--inherit-argv0" ] ++ extraMakeWrapperArgs ); in runCommand "${unwrapped.name}-wrapped" { inherit (unwrapped) meta; paths = [ unwrapped ]; <del> nativeBuildInputs = [ makeWrapper ]; </del> <ins> nativeBuildInputs = [ makeWrapper xorg.lndir ]; </ins> passthru = { inherit unwrapped; # For backwards compatibility:

Discussion:
i can no longer use libreoffice headlessly i suspect this is due to the rewrite of the wrapper additionally, the binary is no longer provided, only etc, which are supposed to be usable headlessly too and maybe more impactful, attempting to launch the GUI with doesn't work either Steps to reproduce the behavior: -, -for a known working .odt file or project using the headless feature, see (already amended to attempt to use instead of ) to open libreoffice with the appropriate sub-app with that file open to open libreoffice writer with that file open to yield to yield error window on ! due to , the wrapper rewrite which seems to have introduced this issue
Aish... didn't realize this usage would break when I the flag to ... As a workaround, you can run the unwrapped executables in the meantime, this should work (works for me): I'm a bit confused though, which revision are you evaluating exactly? which is used in your report is before the wrapper rewrite.
I don't experience other issues you mention on current branch .
oh right, i had this issue on up-to-date yesterday on my laptop i filed the issue on my desktop
i'm unclear about what issues you don't experience on current on the branch, there's no
My bad :sweat_smile: My wasn't updated at all! Adding won't be that hard, but fixing the issue is harder...
Change:
config = mkMerge [ (mkIf cfg.enable { <ins> assertions = flip mapAttrsToList cfg.networks (name: cfg: { assertion = cfg.psk == null || cfg.pskRaw == null; message = ''networking.wireless."${name}".psk and networking.wireless."${name}".pskRaw are mutually exclusive''; }); </ins> environment.systemPackages =  [ pkgs.wpa_supplicant ]; services.dbus.packages = [ pkgs.wpa_supplicant ];

Discussion:
has two forms of input for the field. and . I personally use the latter as it is the output of and better than having cleartext passphrases. (This also works with a random AES key - so long that it is shared) The current implementation lacks the distinction and only works with passphrases. I believe this should be .
Change:
rm 7z 7z.so ln -s ${p7zip}/bin/7z 7z <del> ln -s ${p7zip}/lib/p7zip/7z.so 7z.so </del> <ins> ln -s ${lib.getLib p7zip}/lib/p7zip/7z.so 7z.so </ins> popd '';

Discussion:
p7zip source is gone try to build without substituters cc
What commit are you having the issue from? it works for me at
Current master, that is sets to . There is no such tag at
Maybe the fork cleared the tags by force pushing?
Hmm, I wonder if all the changes got merged into with the fork then rebasing and force-pushing…
Yeah, looks like it. A bunch of jinfeihan57's commits are now in the commit history I'll change it to point back to p7zip-project's copy now
Change:
parallel-rust = callPackage ../tools/misc/parallel-rust { }; <ins> pueue = callPackage ../applications/misc/pueue { }; </ins> pyCA = python3Packages.callPackage ../applications/video/pyca {}; pyznap = python3Packages.callPackage ../tools/backup/pyznap {};

Discussion:
Project description Pueue is a command line queue management tool for sequential and parallel execution of long running tasks.  Installation Vector This package is conventionally installed through or , so it should be packaged like other Python programs. Metadata homepage URL: source URL: license: MIT platforms: Unix
Hey. Maintainer from pueue here. Pueue has been rewritten in Rust. It can now easily be deployed via binary or clean installed via cargo.
Hi great to hear from you! And it's nice to hear that Pueue has been rewritten in Rust. It would be easier to package if it had an upstream file. Would you be willing to provide one?
Hey Sorry for the delay, I wanted to release a new version that fixes some things before pinging you. is .
Wow, thanks much appreciated. Here's the expression I'm using: When I build it I get a build failure in the dependency of all things: It looks like CI is red for this build too, but for a different reason: Is this error familiar to you? If not it might be something about how works in Nix. My main hunch is that I'm implicitly using a that does not meet the Rust=1.39 constraint of .
Travis' pipeline failed on the old python version :D Totally forgot this still existed. The Github Actions pipeline is working for both rust stable and nightly (just a badge to the Readme) I just looked at the Nixpkg rust section and it looks like there is an option to set the Rust version: Also looked at the error you got there. It's indeed another feature that got stablilized in Rust v1.39. Thanks for packaging this for NixOs. I'm kind of honored :)
Aha, I just used so that I got the channel instead of NixOS 19.09. This works!
Change:
allowing code to be developed that will work with both libraries. It was developed initially for the openpyxl project but is now a standalone module. <del> The code was written by Elias Rabel as part of the Python Düsseldorf openpyxl sprint in September 2014. </del> ''; <del> homepage = "https://pypi.python.org/pypi/et_xmlfile"; </del> <ins> homepage = "https://foss.heptapod.net/openpyxl/et_xmlfile"; </ins> license = licenses.mit; maintainers = with maintainers; [ ]; }; }

Discussion:
Package name: et_xmlfile Latest released version: 1.1.0 <!-- Search your package here: --- Current version on the unstable channel: 1.0.1 Current version on the stable/release channel: 1.0.1 <!-- 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.
Looks like I'm not the maintainer of this package, but if you make a PR updating it feel free to ping me for review.
Change:
buildInputs = [ alsa-lib nss <ins> lz4 libgcrypt </ins> libthai ] ++ (with libsForQt5; [ qt5.qtvirtualkeyboard ]);

Discussion:
Steps to reproduce the behavior: Eventually nixos-rebuild fails and exits with the last few lines regarding the package build fail: Please run and paste the result. Could you please check it? Can this be related to the following . By the way - the latest available version seems to be - could you please upgrade to it and possibly it will resolve it?
Thanks for the heads-up, I will fix it when I am upgrading my nixpkgs fork, soon.
Please test and upvote:
Change:
</listitem> <listitem> <para> <del> Add option <literal>services.nginx.enableSandbox</literal> to starting Nginx web server with additional sandbox/hardening options. By default, write access to <literal>services.nginx.stateDir</literal> is allowed. To allow writing to other folders, </del> <ins> Nginx web server now starting with additional sandbox/hardening options. By default, write access to <literal>services.nginx.stateDir</literal> is allowed. To allow writing to other folders, </ins> use <literal>systemd.services.nginx.serviceConfig.ReadWritePaths</literal> <programlisting> systemd.services.nginx.serviceConfig.ReadWritePaths = [ "/var/www" ];

Discussion:
ping It was agreed that should be removed before . It was generally accepted that an option isn't a great idea and was to the module temporarily for ease of testing. It is important to remove this because other people have seen this option and started believing this is an accepted design pattern for NixOS modules - we don't want people getting the wrong idea and having more options like this slip in. can you please file a PR removing this option and the entry from the release notes?
Change:
WebInterface ${if cfg.webInterface then "Yes" else "No"} <ins> LogLevel ${cfg.logLevel} </ins> ${cfg.extraConf} '';

Discussion:
The documentation for the option suggests that it can b used to set the . However, the initial value of also includes , overriding the value potentially given by the user. Try setting and be surprised when produces no more output than it did previously. Examine and find that in the initial value of appears after the overridden value.
Change:
<del> { callPackage, fetchpatch, ... } @ args: callPackage ./generic.nix (args // rec { version = "2.4.0"; branch = "2.4"; revision = "v${version}"; sha256 = "143dvy5g6v6129lzvl0r8mrgva2fppkn0zl099qmi9yi9l9h7yyf"; extraFlags = [ "-DOPENJPEG_INSTALL_INCLUDE_DIR=${placeholder "dev"}/include/openjpeg-${branch}" "-DOPENJPEG_INSTALL_PACKAGE_DIR=${placeholder "dev"}/lib/openjpeg-${branch}" ]; patches = [ ./fix-cmake-config-includedir.patch (fetchpatch { url = "https://patch-diff.githubusercontent.com/raw/uclouvain/openjpeg/pull/1321.patch"; sha256 = "1cjpr76nf9g65nqkfnxnjzi3bv7ifbxpc74kxxibh58pzjlp6al8"; }) ]; }) </del>

Discussion:
, CVSSv3=7.8 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also: ,
Change:
cargoBuildFlags = [ "-p" "cargo-nextest" ]; cargoTestFlags = [ "-p" "cargo-nextest" ]; <ins> # TODO: investigate some more why these tests fail in nix checkFlags = [ "--skip=tests_integration::test_list" "--skip=tests_integration::test_relocated_run" "--skip=tests_integration::test_run" ]; </ins> meta = with lib; { description = "Next-generation test runner for Rust projects"; homepage = "https://github.com/nextest-rs/nextest";

Discussion:
Steps to reproduce the behavior: cargo-nextest also on hydra I guess this is caused by in which nextest-runner upgraded its dependency to , while in the integration test the version is left locked as . Maybe the vendor stage failed to pack two versions of into the archive? <!-- 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.
Change:
stdenv.mkDerivation rec { pname = "jsonnet"; version = "0.20.0"; <del> outputs = ["out" "doc"]; </del> <ins> outputs = [ "out" "doc" ]; </ins> src = fetchFromGitHub { rev = "v${version}";

Discussion:
I cannot install on my Apple M1 PowerBook any more (potentially due to ?) I'm tracking (commit ) Steps to reproduce the behavior: Here's the output of
I'm afraid I don't have a Mac around to test with, but from glancing at the build log it appears the problem may go away if you remove from in the jsonnet derivation, or make it conditional on stdenv.hostPlatform.isStatic as suggested in .
I can confirm this issue. We worked around this in our own overlay by reverting to the last known (to us) NixPkgs version for the Jsonnet package only (i.e. we overlayed the derivation with one that is basically . No idea what exactly causes the problem, though.
didn't fix this, I still can't build jsonnet on Darwin.
This is fixed in , PTAL.
Change:
, curl }: let <del> version = "2020.1.1"; </del> <ins> version = "2020.1.3"; </ins> shortVersion = builtins.substring 0 6 version; in stdenv.mkDerivation rec {

Discussion:
Describe the bug Trying to build fails To Reproduce Additional context Apparently it was already broken here: Maybe it makes sense to update to recently released version 2020.1. Notify maintainers
I'll try and fix by updating.