jiebi/CodeConvo huggingface dataset:
Change:
# pkgs.coolFunction Description of what `coolFunction` does. <ins> ## Inputs </ins> `coolFunction` expects a single argument which should be an attribute set, with the following possible attributes: `name` (String)

Discussion:
While working on some documentation on Nixpkgs, I noticed that there doesn't seem to be a convention for showing shell commands and their outputs. prepends to the command prompt, and output as a normal, not-indented line. adds a comment above the command prompt showing what the output is. uses two different code blocks, one with the command, the other with the output. Additionally, there are other code blocks to show expressions and their result inside the nix repl: prepends to the (error) output. And prepends to the output. Note that the proposal below was written just to have some starting proposal, but not much thought has been given to other alternatives yet. My current proposal is to adopt the following convention: For shell commands and outputs, prepend to any lines that are part of the command, and put outputs in their own lines as-is. If the command has line continuations, don't prepend , but add some indentation to keep it from looking like an output. For example: For nix repl expressions, prepend to any lines part of an expression, and put outputs in their own lines as-is. <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Talked about this in the docs team meeting, I think this is a good idea! If you make a PR to describe this convention in the I could review/merge it. I guess very generally, the convention is to use the format as you'd see it in the REPL.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
postPatch = '' substituteInPlace setup.py  <del> --replace-fail "self.install_libbase" '"${placeholder "out"}/${python3.sitePackages}"' </del> <ins> --replace-fail "self.install_libbase" '"${placeholder "out"}/${python3Packages.python.sitePackages}"' </ins> ''; build-system = [

Discussion:
Steps to reproduce the behavior: pymol 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]:
Note: This seems to be failure of test check. With no check (doCheck=false;), the package builds and runs as expected.
Change:
<ins> { lib, buildGoModule, fetchFromGitHub, bash }: buildGoModule rec { pname = "kubectl-neat"; version = "2.0.3"; src = fetchFromGitHub { owner = "itaysk"; repo = "kubectl-neat"; rev = "v${version}"; hash = "sha256-j8v0zJDBqHzmLamIZPW9UvMe9bv/m3JUQKY+wsgMTFk="; }; vendorHash = "sha256-vGXoYR0DT9V1BD/FN/4szOal0clsLlqReTFkAd2beMw="; postBuild = '' # Replace path to bash in a script # Without this change, there's a problem when running tests sed 's,#!/bin/bash,#!${bash}/bin/bash,' -i test/kubectl-stub ''; meta = with lib; { description = "Clean up Kubernetes yaml and json output to make it readable"; homepage = "https://github.com/itaysk/kubectl-neat"; changelog = "https://github.com/itaysk/kubectl-neat/releases/tag/v${version}"; license = licenses.asl20; maintainers = [ maintainers.koralowiec ]; }; } </ins>

Discussion:
Project description <!-- Describe the project a little: --kubectl plugin to remove clutter from Kubernetes manifests to make them more readable. Metadata homepage URL: source URL: license: Apache License 2.0 platforms: linux, darwin
Change:
stdenv.mkDerivation rec { pname = "connman"; <del> version = "1.40"; </del> <ins> version = "1.41"; </ins> src = fetchurl { url = "mirror://kernel/linux/network/connman/${pname}-${version}.tar.xz"; <del> sha256 = "sha256-GleufOI0qjoXRKrDvlwhIdmNzpmUQO+KucxO39XtyxI="; </del> <ins> sha256 = "sha256-eftA9P3VUwxFqo5ZL7Froj02dPOpjPELiaZXbxmN5Yk="; </ins> }; patches = lib.optionals stdenv.hostPlatform.isMusl [

Discussion:
, CVSSv3=9.1 (nixos-21.11, nixos-unstable) CVSSv3=9.1 (nixos-21.11, nixos-unstable) CVSSv3=7.5 (nixos-21.11, nixos-unstable) An issue was discovered in the DNS proxy in Connman through 1.40. The TCP server reply implementation lacks a check for the presence of sufficient Header Data, leading to an out-of-bounds read. An issue was discovered in the DNS proxy in Connman through 1.40. forwarddnsreply mishandles a strnlen call, leading to an out-of-bounds read. An issue was discovered in the DNS proxy in Connman through 1.40. The TCP server reply implementation has an infinite loop if no data is received. Scanned versions: nixos-21.11: ; nixos-unstable: . Cc
Unstable - 11 -
Change:
requests ]; <del> preCheck = lib.optionalString (stdenv.isDarwin && stdenv.isAarch64) '' </del> <ins> preCheck = '' # Scale default timeouts by a factor of 4 to avoid flaky builds # https://github.com/microsoft/debugpy/pull/1286 if merged would # allow us to disable the timeouts altogether export DEBUGPY_PROCESS_SPAWN_TIMEOUT=60 export DEBUGPY_PROCESS_EXIT_TIMEOUT=20 '' + lib.optionalString (stdenv.isDarwin && stdenv.isAarch64) '' </ins> # https://github.com/python/cpython/issues/74570#issuecomment-1093748531 export no_proxy='*'; '';

Discussion:
fails to build on right now. The first bad commit is .
so interestingly builds for me but master fails ... either its flaky tests or something else happening
ok, my conclusion is flaky tests, they pass eventually
Oh yep! It seems like it's flaking on a timeout. It doesn't look like you can disable them, so I submitted a PR to scale the defaults by a factor of 4 on tests:
This is preventing from succeeding if the user requests the package.
Change:
# > The following imported targets are referenced, but are missing: # > SPIRV-Tools-opt ./cmakelists.patch <ins> # Remove on next release # https://github.com/cemu-project/Cemu/pull/1076 (fetchpatch { url = "https://github.com/cemu-project/Cemu/commit/72aacbdcecc064ea7c3b158c433e4803496ac296.patch"; hash = "sha256-x+ZVqXgGRSv0VYwJAX35C1p7PnmCHS7iEO+4k8j0/ug="; }) </ins> ]; nativeBuildInputs = [

Discussion:
Steps to reproduce the behavior: the following : the flake: cc Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Oddly enough, (the original PR ) actually fails as well. Result of run on x86_64-linux <details<summary1 package failed to build:</summary<ul<licemu</li</ul</details
Change:
''; nativeBuildInputs = [ <del> cmake ninja pkgconfig jre swig wrapGAppsHook </del> <ins> cmake ninja pkgconfig jre swig wrapGAppsHook </ins> ]; buildInputs = [ <del> gtk3 gtkmm3 libX11 antlr4_7.runtime.cpp python2 mysql libxml2 libmysqlconnectorcpp vsqlite gdal boost libssh openssl libiodbc pcre cairo libuuid libzip libsecret libsigcxx proj </del> <ins> gtk3 gtkmm3 libX11 antlr4_7.runtime.cpp python2 mysql libxml2 libmysqlconnectorcpp vsqlite gdal boost libssh openssl rapidjson libiodbc pcre cairo libuuid libzip libsecret libsigcxx proj </ins> # python dependencies: <del> paramiko pycairo pyodbc # sqlanydb </del> <ins> paramiko pycairo pyodbc # TODO: package sqlanydb and add it here </ins> # transitive dependencies: <del> libpthreadstubs libXdmcp libxkbcommon epoxy at-spi2-core dbus </del> <ins> libpthreadstubs libXdmcp libxkbcommon epoxy at-spi2-core dbus </ins> ]; postPatch = '' patchShebangs tools/get_wb_version.sh ''; <del> # error: 'OGRErr OGRSpatialReference::importFromWkt(char**)' is deprecated </del> <ins> # error: 'OGRErr OGRSpatialReference::importFromWkt(char**)' is deprecated </ins> NIX_CFLAGS_COMPILE = "-Wno-error=deprecated-declarations"; cmakeFlags = [ "-DMySQL_CONFIG_PATH=${mysql}/bin/mysql_config" "-DIODBC_CONFIG_PATH=${libiodbc}/bin/iodbc-config" "-DWITH_ANTLR_JAR=${antlr4_7.jarLocation}" <ins> # mysql-workbench 8.0.19 depends on libmysqlconnectorcpp 1.1.8. # Newer versions of connector still provide the legacy library when enabled # but the headers are in a different location. "-DMySQLCppConn_INCLUDE_DIR=${libmysqlconnectorcpp}/include/jdbc" </ins> ]; # There is already an executable and a wrapper in bindir

Discussion:
Describe the bug On , fails to build because there are lots of compiler warnings and those are treated as errors. To Reproduce Steps to reproduce the behavior: out the branch of the repo's root directory, run Expected behavior Build succeeds and a symlink is created pointing to the build result. Observed behavior <details<summaryBuild fails with the following output (click to expand)</summary</detailsand with exit code . Screenshots n/a Additional context n/a Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(das-g): nixpkgs: Maintainer information:
Change:
pdfreader = mkKodiPlugin rec { plugin = "pdfreader"; namespace = "plugin.image.pdf"; <del> version = "1.0.2"; </del> <ins> version = "2.0.2"; </ins> <del> src = fetchFromGitHub rec { name = plugin + "-" + version + ".tar.gz"; owner = "teeedubb"; repo = owner + "-xbmc-repo"; rev = "0a405b95208ced8a1365ad3193eade8d1c2117ce"; sha256 = "1iv7d030z3xvlflvp4p5v3riqnwg9g0yvzxszy63v1a6x5kpjkqa"; </del> <ins> src = fetchFromGitHub { owner = "i96751414"; repo = "plugin.image.pdfreader"; rev = "v${version}"; sha256 = "0nkqhlm1gyagq6xpdgqvd5qxyr2ngpml9smdmzfabc8b972mwjml"; </ins> }; meta = { homepage = "https://forum.kodi.tv/showthread.php?tid=187421"; description = "A comic book reader"; maintainers = with maintainers; [ edwtjo ]; <del> broken = true; # requires port to python3 </del> }; };

Discussion:
It seems to me that pdfreader 1.02 in nixos doesn't work with nixos 20.03 kodi version. It apears as disabled and I can't enable it. When I install version 2.01 over zip file, it's visible but when I try to start it it crashes because no PIL support in python. When I then add: to my systempackages, it doesn't change anything. I can't also "from PIL import Image" the paths are probably not correctly set.
how do you install ? I'm guessing something like ... Can you try this: :thinking:
Yes I do it like that but doesn't help, I tried to updated to kodi 20.09 just now didn't change anything. I think part of the problem is that kodi version of pdfreader is 1.02 instead of the current version 2.01 (or whatever is currently the latest), so 1.02 does not work with other reasons and when I install "manual" over zip file the 2.01 your dependency get's not correctly installed for that package. Even in unstable is still 1.02 while 2.01 is current:
I haven't had a chance to test this plugin yet but I'm working on updates:
I was able to run from NixOS , and then imperatively install the from inside with this configuration: When I tried to load a with images I ran into the following error, though: This doesn't really look to be NixOS related, though... :thinking:
again the 1.02 version of this plugin is I think from 2014 or so, the 2.01 is from 2020, I didn't remember what is changed in this versions 1 thing is python 3.x support which is what 2.01 introduced but don't remember what 2.x did, but I think it fixed stuff that likely cause this errors. This version might just be incompatible with current kodi versions period. Even if it would be theoretically still functional I just find it a wasted time to try to fix the old one if 2.0 is a "complete rewrite" with "multiple improvements and fixes".
I'll revisit this plugin before goes stable with their next major version, under the assumption the author of this plugin will have released a compatible version.

Well I tested the plugin it's pretty useless, you have to type in the pdf name in a file open dialog with full path... that's not more than a proof of concept plugin, don't waste your time to get it working. My workaround that worked for some stuff was to convert pdf to images and then watch the images in a folder. The conversion with text seemed not to work reliable but that is no kodi problem.
Change:
extraConfig = flip concatMapStrings vlanIfs (n: '' subnet 192.168.${toString n}.0 netmask 255.255.255.0 { option routers 192.168.${toString n}.1; <del> range 192.168.${toString n}.2 192.168.${toString n}.254; </del> <ins> range 192.168.${toString n}.3 192.168.${toString n}.254; </ins> } '') ;

Discussion:
Describe the bug fails. To Reproduce It will not fail immediately, but it will eventually, and it should not take long at all (see e.g for a ). Additional context Couldn't find an interesting commit in the git log since the last successful test: Notify maintainers ?
Works for me locally (1/1 attempt). I restarted the job.
BTW, the big channels are now mainly blocked by
Hmmm... Didn't work for me in the first attempt among 3.
Maybe it's still worth looking into reliability of the test but occasional restarts don't seem such a huge burden, as someone has to watch for breakages anyway.
The test is blocking nixos-unstable again. Edit: wrong link.
It was just a single attempt on Hydra and the second one succeeded. Locally it succeeded 1/1 again; perhaps it's more prone to fail on a loaded system. Well, my last comment still holds.
When I run the test locally, it fails (or rather gets stuck) once in five tries or so: It will fail eventually, as said.
Seems like this is caused by two different interfaces getting the same IP via DHCP. From the : Both and have IP , so fails. looks like this: Here, has IP as it is supposed to.
It failed again: Could somebody please look at ?
We should probably either make the test reliable or delete the test.
It passed. We should probably open a new issue if it fails again, with a focus on trying to stabilize the test .
I believe fixes it. Not sure why nobody wants to merge it. Am I shadowbanned? :)
Change:
[ bash coreutils <ins> diffutils </ins> file findutils gawk gnugrep <ins> gnupatch </ins> gnused gnutar gzip

Discussion:
Nix's version of bazel has custom patches to make bazel more hermetic when used with nix. One of those is limiting the default environment of Bash: However, this default environment is insufficient because lots of programs rely on being in the path like buildifier, golangci-lint, and other things since golang diff implementations aren't very good. Ideally we'd include "diffutils" as part of this list for rules that assume the presence of "diff" and don't allow nice knobs to configure otherwise. Steps to reproduce the behavior: up workspace with to run the test. It will complain about missing "diff" Expected to find diff.
I think with the assumption is that you'll specify the you need yourself. The built in one is unlikely to have all the binaries you need in all your actions. We add the ones that the actions in bazel itself and the external repositories it includes need so you can use it out of the box, but ideally that list would be as small as possible.
Do you have references to open source rule sets or code that depends on diff being in the action path? To have an idea of how widely used they are.
I noted , for and various analyzers if you want to include them for use with nogo (For example, you can use the repo for nogo analyzers, which implements the analyzer, which uses as a subprocess under the hood as well).
TIL about , seems close enough to bazel that we'd want to support it out of the box. Yeah let's add it. Can you put up a PR?
I have recently come across a target that needs and found this issue. It's neat to add , but is there a nice way to add arbitrary paths to a specific Bazel invocation? I have a build script (GMP, pulled in as a dependency of the crate), which expects . I don't expect this to be a Bazel dependency, but I need to make available to this dependency. Having some environment variable like or whatever would be helpful here.
So, I found this workaround to this Essentially instead of using , which hardcodes , we specify our own . We accomplish this using a shell hook and loading the generated file in the .bazelrc: It's more flexible than modifying this every time.

One thing to note is that Bazel has a bug around setting environments in actions and some actions hard code the PATH to /usr/bin (rulesgo for example), and in those instances, it will fail to find the proper binaries. You can work around this there as well if you use rulesnixpkgs, by adding these deps to your go toolchain.
Change:
<del> { stdenv, fetchurl, pkgconfig, cairo, harfbuzz </del> <ins> { stdenv, fetchurl, fetchpatch, pkgconfig, cairo, harfbuzz </ins> , libintl, gobject-introspection, darwin, fribidi, gnome3 , gtk-doc, docbook_xsl, docbook_xml_dtd_43, makeFontsConf, freefont_ttf , meson, ninja, glib

Discussion:
Describe the bug I'm trying to build Nixos using a raspberry-pi-like system. It seems that there's a mismatch on pango which is preventing my build from succeeding. I am using unstable. To Reproduce Steps to reproduce the behavior: -rebuild switch --upgrade --fast (and some binary-caches options) Expected behavior build succeeds Screenshots Additional context complete output: Metadata cc since you authored on
I can verify the hash of the patch changed
Not sure how we want to deal with this for master. If is ready we should merge it to staging-next. Otherwise just updating the hash would be most sensible.
For now I suggest updating the hash and sending it to staging. And use !
BTW, the reason the hash changed is because includes the server's version of in the patch comment, and they upgraded from to . correctly strips this comment and avoids the issue; thanks for the fix!
You're welcome. I think I forgot to close this issue :smile:
Change:
nativeBuildInputs = [ pkg-config rustPlatform.bindgenHook ]; <del> buildInputs = [ alsa-lib openssl ] ++ lib.optionals withTTS [ speechd ]; </del> <ins> buildInputs = [ openssl ] ++ lib.optionals (withTTS && stdenv.isLinux) [ speechd ] ++ lib.optionals stdenv.isLinux [ alsa-lib ] ++ lib.optionals (withTTS && stdenv.isDarwin) [ AVFoundation AppKit ] ++ lib.optionals stdenv.isDarwin [ CoreAudio AudioUnit ]; </ins> checkFlags = let

Discussion:
Steps to reproduce the behavior: blightmud on arm64-darwin (unsupported system) command: full 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I submitted a blightmud issue prior to this one Let me know if there's anything I can do to help
If you'd like to submit patches to add additional OS/arch support I would be willing to try and review, but as mentioned on I won't be able to drive the effort from my end.
Should be working now, could you please test it? or if you don't have checked out:
Hey this worked for me. Thanks for the fix!
Change:
{ lib , python3 , fetchFromGitHub <ins> , fetchpatch </ins> , enableGoogle ? false , enableAWS ? false , enableAzure ? false

Discussion:
The dvc package is on version 0.24, but PyPI has version 0.87 with a bunch of new features. The old version can't handle new dvc files.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Dunno if you are interested yet, but it is a hell of a dependency-chasing to compile it. I have four libraries to Python packages, and now I found my first transitive dependency.
Change:
wrapGAppsHook ]; <del> propagatedBuildInputs = with python3.pkgs; [ pygobject3 </del> <ins> propagatedBuildInputs = [ python3.pkgs.pygobject3 killall </ins> ]; # has no tests

Discussion:
is missing command dependency and will fail to update wallpaper without it. Steps to reproduce the behavior: a system without , any background is not changed. on stdout A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. 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.
Change:
"docker inspect ${pkgs.dockerTools.examples.cross.imageName} " + "| ${pkgs.jq}/bin/jq -r .[].Architecture" ).strip() <del> == "${if pkgs.system == "aarch64-linux" then "amd64" else "arm64v8"}" </del> <ins> == "${if pkgs.system == "aarch64-linux" then "amd64" else "arm64"}" </ins> ) ''; })

Discussion:
Describe the bug It seems generates images with the wrong architecture set. ( began setting these values, but the values before were also wrong) To Reproduce Compared to the current version of : If you actually run the image on arm, Docker complains. Expected behavior Architectures embedded in the image configuration should match those generated by Docker. Additional context The warning message printed by Docker if the running platform doesn't match the image's platform. The operating system, architecture, and variant are determined by and . (If the image's architecture is "arm" and the variant is empty, as it almost always is, it is normalized to "v7", see ) Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(terin): nixpkgs: Maintainer information:
The specification is a bit loose, but the examples given all follow and . If we take a look at the specification, the fields should be and . Every officiall and semi-official image I've looked at, included the pre-multiarch manifest "legacy" images referenced at follow this pattern.
Change:
sha512 = "/2HA0Ec70TvQnXdzynFffkjA6XN+1e2pEv/uKS5Ulca40g2L7KuOE3riasHoNVHOsFD5KKZgDsMk1CP3Tw9s+A=="; }; }; <ins> "rollup-2.51.1" = { name = "rollup"; packageName = "rollup"; version = "2.51.1"; src = fetchurl { url = "https://registry.npmjs.org/rollup/-/rollup-2.51.1.tgz"; sha512 = "8xfDbAtBleXotb6qKEHWuo/jkn94a9dVqGc7Rwl3sqspCVlnCfbRek7ldhCARSi7h32H0xR4QThm1t9zHN+3uw=="; }; }; </ins> "rollup-2.56.0" = { name = "rollup"; packageName = "rollup";

Discussion:
The extension fails to activate. Steps to reproduce the behavior: the extension via home-manager to activate it by opening VS Code to a Rust project For the extension to activate successfully. Logs: Maintainer information:
Note: rolling back to fixes the issue.
Hello, I've been looking at this since yesterday. I think we need to pin rollup to 2.51 and/or update plugin-commonjs to 19 to avoid / - I am presently regenerating node- to test this fix. I think you are right that my 08-02 update introduced the regression. I apologize, ~can cut a revert PR later today if my fix doesn't work and if this would be desirable.~ The fix seems to work!