jiebi/CodeConvo huggingface dataset:
Code change:
Describe the bug Upon enabling docker via sysctl.d is not updated to allow IP forwarding which is required by containers to communicate with outside world. To Reproduce Steps to reproduce the behavior: This will get up and running with set to which in my understanding is set by the itself. to re-apply system-wide sysctl settings and check By now your bridge-mode docker containers lost connectivity. Expected behavior I expect to override relevant values. Something like this: Additional context I discovered this problem when applying other sysctl values on a running system without a reboot. Notify maintainers Metadata
Hi, I stumbled into the same issue. I had to manually run to regain container internet access.

Related discussion:
text: # Must match version 4 times to ensure client and server git commits and versions are correct docker.succeed('[ $(docker version | grep ${pkgs.docker.version} | wc -l) = "4" ]') <ins> docker.succeed("systemctl restart systemd-sysctl") docker.succeed("grep 1 /proc/sys/net/ipv4/conf/all/forwarding") docker.succeed("grep 1 /proc/sys/net/ipv4/conf/default/forwarding") </ins> ''; })
Code change:
name: current version: desired version: latest version: maintainers: Please tag this issue in your PR.
You'll have to package pydeck as well
Here's my hack to get things working: And WIP:
I can PR this for you if you accept maintaining the dependency.
ping

Related discussion:
text: <del> {   lib, buildPythonApplication, fetchPypi , altair, astor, base58, blinker, boto3, botocore, click, enum-compat , future, pillow, protobuf, requests, toml, tornado_5, tzlocal, validators, watchdog , jinja2, setuptools </del> <ins> { # Nix lib, buildPythonApplication, fetchPypi, # Build inputs altair, astor, base58, blinker, boto3, botocore, click, cachetools, enum-compat, future, GitPython, jinja2, pillow, pyarrow, pydeck, pympler, protobuf, requests, setuptools, toml, tornado, tzlocal, validators, watchdog, </ins> }: <del> buildPythonApplication rec { </del> <ins> let click_7 = click.overridePythonAttrs(old: rec { version = "7.1.2"; src = old.src.override { inherit version; sha256 = "d2b5255c7c6349bc1bd1e59e08cd12acbbd63ce649f2588755783aa94dfb6b1a"; }; }); in buildPythonApplication rec { </ins> pname = "streamlit"; <del> version = "0.50.2"; </del> <ins> version = "1.2.0"; </ins> format = "wheel"; # the only distribution available src = fetchPypi { inherit pname version format; <del> sha256 = "1wymv7qckafs0p2jdjlxjaf1xrhm3iyd185jkldanbb0na5n3ndz"; </del> <ins> sha256 = "1dzb68a8n8wvjppcmqdaqnh925b2dg6rywv51ac9q09zjxb6z11n"; </ins> }; propagatedBuildInputs = [ <del> altair astor base58 blinker boto3 botocore click enum-compat future pillow protobuf requests toml tornado_5 tzlocal validators watchdog jinja2 setuptools </del> <ins> altair astor base58 blinker boto3 botocore cachetools click_7 enum-compat future GitPython jinja2 pillow protobuf pyarrow pydeck pympler requests setuptools toml tornado tzlocal validators watchdog </ins> ]; postInstall = ''
Code change:
name: current version: desired version: latest version: maintainers: Please tag this issue in your PR.
You'll have to package pydeck as well
Here's my hack to get things working: And WIP:
I can PR this for you if you accept maintaining the dependency.
ping

Related discussion:
text: maintainers = with maintainers; [ yrashk ]; license = licenses.asl20; }; }
Code change:
Describe the bug Postgres already exists as a nix package () bundled with some packages (). Postgres itself has built-in support for Python, but it needs to be enabled during the build process () via the configure flag. The current implementation of postgres in nix does not enable python support, and it also doesn't seem to perform any detection whether python support should be offered. There is already some form of conditional feature support (for example via the attribute. It could be possible to add a attribute that enables python. My knowledge of nix is clearly lacking in this regard, but I hope the idea makes sense. To Reproduce Steps to reproduce the behavior: via then use to initialize and start a server instance psql to enter the postgres instance 'create extension plpython3u;' ! Expected behavior The ability to enable the plpython3u extension. Screenshots This is a screenshot of the current configureFlags of postgres (). Somehow it should be possible to get into this list. ! Additional context I am trying to get a nix-shell working that has a postgresql12 with python support. I am not trying to get a working configuration in NixOS. It should be possible to use to explicitly add support for plpython. I am still exploring this possibility. Others have done something similar for other postgres extensions (). There is a nix pill that describes how to override packages here () and here (). However, it looks like this can get complicated (). More examples of overriding can be found here: Another approach for overriding packages is via overlays (). By including support for python in the derivation itself, it may be easier for new users to get started. attempted to add support for multicorn (), which is implemented using python (), but this doesn't use plpython3u, and is thus not directly related to this issue. Just mentioning it here for others that are trying to figure out how to get python in their database backend. The author of the following article shows how to configure postgres using : I can imagine a solution that may look like this: . Another possibility, is to have something like (see etc.). Notify maintainers Can you recommend a way to get plpython3u enabled in the nix build of postgres? Metadata Please run and paste the result. Maintainer information:
The following extract seems to work so far:
I marked this as stale due to inactivity. &rarr;
I'm interested in using this but not sure when I'd be able to pick it up.

Related discussion:
text: , nukeReferences, patchelf, llvmPackages , makeRustPlatform, buildPgxExtension, cargo, rustc <ins> # PL/Python , pythonSupport ? false , python3 </ins> # detection of crypt fails when using llvm stdenv, so we add it manually # for <13 (where it got removed: https://github.com/postgres/postgres/commit/c45643d618e35ec2fe91438df15abd4f3c0d85ca) , libxcrypt
Code change:
Describe the bug Postgres already exists as a nix package () bundled with some packages (). Postgres itself has built-in support for Python, but it needs to be enabled during the build process () via the configure flag. The current implementation of postgres in nix does not enable python support, and it also doesn't seem to perform any detection whether python support should be offered. There is already some form of conditional feature support (for example via the attribute. It could be possible to add a attribute that enables python. My knowledge of nix is clearly lacking in this regard, but I hope the idea makes sense. To Reproduce Steps to reproduce the behavior: via then use to initialize and start a server instance psql to enter the postgres instance 'create extension plpython3u;' ! Expected behavior The ability to enable the plpython3u extension. Screenshots This is a screenshot of the current configureFlags of postgres (). Somehow it should be possible to get into this list. ! Additional context I am trying to get a nix-shell working that has a postgresql12 with python support. I am not trying to get a working configuration in NixOS. It should be possible to use to explicitly add support for plpython. I am still exploring this possibility. Others have done something similar for other postgres extensions (). There is a nix pill that describes how to override packages here () and here (). However, it looks like this can get complicated (). More examples of overriding can be found here: Another approach for overriding packages is via overlays (). By including support for python in the derivation itself, it may be easier for new users to get started. attempted to add support for multicorn (), which is implemented using python (), but this doesn't use plpython3u, and is thus not directly related to this issue. Just mentioning it here for others that are trying to figure out how to get python in their database backend. The author of the following article shows how to configure postgres using : I can imagine a solution that may look like this: . Another possibility, is to have something like (see etc.). Notify maintainers Can you recommend a way to get plpython3u enabled in the nix build of postgres? Metadata Please run and paste the result. Maintainer information:
The following extract seems to work so far:
I marked this as stale due to inactivity. &rarr;
I'm interested in using this but not sure when I'd be able to pick it up.

Related discussion:
text: ++ lib.optionals lz4Enabled [ lz4 ] ++ lib.optionals zstdEnabled [ zstd ] ++ lib.optionals enableSystemd [ systemd ] <ins> ++ lib.optionals pythonSupport [ python3 ] </ins> ++ lib.optionals gssSupport [ libkrb5 ] ++ lib.optionals stdenv'.isLinux [ linux-pam ] ++ lib.optionals (!stdenv'.isDarwin) [ libossp_uuid ];
Code change:
Describe the bug Postgres already exists as a nix package () bundled with some packages (). Postgres itself has built-in support for Python, but it needs to be enabled during the build process () via the configure flag. The current implementation of postgres in nix does not enable python support, and it also doesn't seem to perform any detection whether python support should be offered. There is already some form of conditional feature support (for example via the attribute. It could be possible to add a attribute that enables python. My knowledge of nix is clearly lacking in this regard, but I hope the idea makes sense. To Reproduce Steps to reproduce the behavior: via then use to initialize and start a server instance psql to enter the postgres instance 'create extension plpython3u;' ! Expected behavior The ability to enable the plpython3u extension. Screenshots This is a screenshot of the current configureFlags of postgres (). Somehow it should be possible to get into this list. ! Additional context I am trying to get a nix-shell working that has a postgresql12 with python support. I am not trying to get a working configuration in NixOS. It should be possible to use to explicitly add support for plpython. I am still exploring this possibility. Others have done something similar for other postgres extensions (). There is a nix pill that describes how to override packages here () and here (). However, it looks like this can get complicated (). More examples of overriding can be found here: Another approach for overriding packages is via overlays (). By including support for python in the derivation itself, it may be easier for new users to get started. attempted to add support for multicorn (), which is implemented using python (), but this doesn't use plpython3u, and is thus not directly related to this issue. Just mentioning it here for others that are trying to figure out how to get python in their database backend. The author of the following article shows how to configure postgres using : I can imagine a solution that may look like this: . Another possibility, is to have something like (see etc.). Notify maintainers Can you recommend a way to get plpython3u enabled in the nix build of postgres? Metadata Please run and paste the result. Maintainer information:
The following extract seems to work so far:
I marked this as stale due to inactivity. &rarr;
I'm interested in using this but not sure when I'd be able to pick it up.

Related discussion:
text: ] ++ lib.optionals lz4Enabled [ "--with-lz4" ] ++ lib.optionals zstdEnabled [ "--with-zstd" ] ++ lib.optionals gssSupport [ "--with-gssapi" ] <ins> ++ lib.optionals pythonSupport [ "--with-python" ] </ins> ++ lib.optionals stdenv'.hostPlatform.isRiscV [ "--disable-spinlocks" ] ++ lib.optionals jitSupport [ "--with-llvm" ] ++ lib.optionals stdenv'.isLinux [ "--with-pam" ];
Code change:
Describe the bug Library is not found when linking on macos. To Reproduce Execute resulting in following output: Expected behavior Deno builds without errors on macos. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(suraj): nixpkgs: Maintainer information:

Related discussion:
text: , rust , rustPlatform , installShellFiles <ins> , libiconv </ins> , libobjc , Security , CoreServices
Code change:
Describe the bug Library is not found when linking on macos. To Reproduce Execute resulting in following output: Expected behavior Deno builds without errors on macos. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(suraj): nixpkgs: Maintainer information:

Related discussion:
text: # Install completions post-install nativeBuildInputs = [ installShellFiles ]; <del> buildInputs = lib.optionals stdenv.isDarwin [ libobjc Security CoreServices Metal Foundation ]; </del> <ins> buildInputs = lib.optionals stdenv.isDarwin [ libiconv libobjc Security CoreServices Metal Foundation ]; </ins> # The rusty_v8 package will try to download a `librusty_v8.a` release at build time to our read-only filesystem # To avoid this we pre-download the file and place it in the locations it will require it in advance
Code change:
Describe the bug For sandboxed builds on my mac, any python tests which ultimately import will fail with this error: To Reproduce Somewhat tricky to reproduce since it only affects downstream dependees, and a recent commit disabled the dask tests, hiding this issue. See for an example. Additional context Dask.dataframes infers an optimal chunk size using a package to get the amount of available memory and CPUs. This non-determinism breaks the build. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Metadata This is not valid since I am building from master of nixpkgs. system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:
That's a clear upstream bug; apparently their value is not given.

Related discussion:
text: { lib , bokeh , buildPythonPackage <ins> , fetchpatch </ins> , fetchFromGitHub , fsspec , pytestCheckHook
Code change:
Describe the bug For sandboxed builds on my mac, any python tests which ultimately import will fail with this error: To Reproduce Somewhat tricky to reproduce since it only affects downstream dependees, and a recent commit disabled the dask tests, hiding this issue. See for an example. Additional context Dask.dataframes infers an optimal chunk size using a package to get the amount of available memory and CPUs. This non-determinism breaks the build. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Metadata This is not valid since I am building from master of nixpkgs. system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:
That's a clear upstream bug; apparently their value is not given.

Related discussion:
text: distributed ]; <del> doCheck = false; </del> <ins> doCheck = true; </ins> checkInputs = [ pytestCheckHook
Code change:
Describe the bug For sandboxed builds on my mac, any python tests which ultimately import will fail with this error: To Reproduce Somewhat tricky to reproduce since it only affects downstream dependees, and a recent commit disabled the dask tests, hiding this issue. See for an example. Additional context Dask.dataframes infers an optimal chunk size using a package to get the amount of available memory and CPUs. This non-determinism breaks the build. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Metadata This is not valid since I am building from master of nixpkgs. system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:
That's a clear upstream bug; apparently their value is not given.

Related discussion:
text: dontUseSetuptoolsCheck = true; <ins> patches = [ # dask dataframe cannot be imported in sandboxed builds # See https://github.com/dask/dask/pull/7601 (fetchpatch { url = "https://github.com/dask/dask/commit/9ce5b0d258cecb3ef38fd844135ad1f7ac3cea5f.patch"; sha256 = "sha256-1EVRYwAdTSEEH9jp+UOnrijzezZN3iYR6q6ieYJM3kY="; name = "fix-dask-dataframe-imports-in-sandbox.patch"; }) ]; </ins> postPatch = '' # versioneer hack to set version of github package echo "def get_versions(): return {'dirty': False, 'error': None, 'full-revisionid': None, 'version': '${version}'}" > dask/_version.py
Code change:
Describe the bug For sandboxed builds on my mac, any python tests which ultimately import will fail with this error: To Reproduce Somewhat tricky to reproduce since it only affects downstream dependees, and a recent commit disabled the dask tests, hiding this issue. See for an example. Additional context Dask.dataframes infers an optimal chunk size using a package to get the amount of available memory and CPUs. This non-determinism breaks the build. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Metadata This is not valid since I am building from master of nixpkgs. system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:
That's a clear upstream bug; apparently their value is not given.

Related discussion:
text: disabledTests = [ "test_annotation_pack_unpack" "test_annotations_blockwise_unpack" <ins> # this test requires features of python3Packages.psutil that are # blocked in sandboxed-builds "test_auto_blocksize_csv" </ins> ]; <ins> pythonImportsCheck = [ "dask.dataframe" "dask" "dask.array" ]; </ins> meta = with lib; { description = "Minimal task scheduling abstraction"; homepage = "https://dask.org/";
Code change:
Describe the bug For sandboxed builds on my mac, any python tests which ultimately import will fail with this error: To Reproduce Somewhat tricky to reproduce since it only affects downstream dependees, and a recent commit disabled the dask tests, hiding this issue. See for an example. Additional context Dask.dataframes infers an optimal chunk size using a package to get the amount of available memory and CPUs. This non-determinism breaks the build. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Metadata This is not valid since I am building from master of nixpkgs. system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:
That's a clear upstream bug; apparently their value is not given.

Related discussion:
text: options = { isoImage.isoName = mkOption { <del> default = "${config.isoImage.isoName}.iso"; </del> <ins> default = "${config.isoImage.isoBaseName}.iso"; </ins> description = '' Name of the generated ISO image file. '';
Code change:
, CVSSv3=8.8 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also:

Related discussion:
text: branch = "3.4.8"; sha256 = "1d0r4yja2dkkyhdwx1migq46gsrcbajiv66263a5sq5bfr9dqkch"; darwinFrameworks = [ Cocoa CoreMedia ]; <ins> knownVulnerabilities = [ "CVE-2021-30123" ]; </ins> } // args)
Code change:
, CVSSv3=2.7 (nixos-unstable) Scanned versions: nixos-unstable: . Cc

Related discussion:
text: stdenv.mkDerivation rec { pname = "jasper"; <del> version = "2.0.28"; </del> <ins> version = "2.0.32"; </ins> src = fetchFromGitHub { owner = "jasper-software"; repo = pname; rev = "version-${version}"; <del> hash = "sha256-f3UG5w8GbwZcsFBaQN6v8kdEkKIGgizcAgaVZtKwS78="; </del> <ins> hash = "sha256-Uwgtex0MWC/pOmEr8itHMIa4wxd97c/tsTzcLgV8D0I="; </ins> }; nativeBuildInputs = [
Code change:
, CVSSv3=2.7 (nixos-unstable) Scanned versions: nixos-unstable: . Cc

Related discussion:
text: stdenv.mkDerivation rec { pname = "libnbd"; <del> version = "1.7.5"; </del> <ins> version = "1.7.7"; </ins> src = fetchurl { url = "https://download.libguestfs.org/libnbd/${lib.versions.majorMinor version}-development/${pname}-${version}.tar.gz"; <del> sha256 = "sha256-UxQx/wnKnCB3uC9xEfq1F0l3kHAJjp9GzbeRugKyFsk="; </del> <ins> hash = "sha256-fNeu1qx+EbKitv2I8nJAmGMF5jxN2RZGPR/LJYnOjG8="; </ins> }; nativeBuildInputs = [
Code change:
Describe the bug Trying to run a nautilus-python extension (syncstate-) fails with ImportError: could not import gobject (error was: ModuleNotFoundError("No module named 'gi'")) To Reproduce gnome3 and install nextcloud-client nautilus from terminal with something like Expected behavior python should find gi. Additional context I think it is part of pygobject3 which is in buildInputs therefore I think it is a problem of a wrong NIXPYTHONPATH Notify maintainers Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
I am not sure if it ever worked. The shared module links against pygobject but that still does not have to mean the gi module will be available on Python side. Maybe we need something like the following: At least until we have .
Yes this works, thank you!
hmmm I just tried with the new nautilus-python, but the nautilus python extensions still fail due to missing gi. Is there a reason that you tried to load gi in nautilus-python and not add the prefix arg as in your comment?
Did you make sure is updated? It worked for me with gsconnect extension. I chose that method because pygobject is really nautilus-python dependency, not nautilus one.
nevermind it works now (also with nextcloud), I forgot the in the overlay where I overwrote the package from master. Thanks for fixing it!

Related discussion:
text: <del> { lib, stdenv </del> <ins> { stdenv , lib , substituteAll </ins> , fetchurl , pkg-config , which
Code change:
Describe the bug Trying to run a nautilus-python extension (syncstate-) fails with ImportError: could not import gobject (error was: ModuleNotFoundError("No module named 'gi'")) To Reproduce gnome3 and install nextcloud-client nautilus from terminal with something like Expected behavior python should find gi. Additional context I think it is part of pygobject3 which is in buildInputs therefore I think it is a problem of a wrong NIXPYTHONPATH Notify maintainers Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
I am not sure if it ever worked. The shared module links against pygobject but that still does not have to mean the gi module will be available on Python side. Maybe we need something like the following: At least until we have .
Yes this works, thank you!
hmmm I just tried with the new nautilus-python, but the nautilus python extensions still fail due to missing gi. Is there a reason that you tried to load gi in nautilus-python and not add the prefix arg as in your comment?
Did you make sure is updated? It worked for me with gsconnect extension. I chose that method because pygobject is really nautilus-python dependency, not nautilus one.
nevermind it works now (also with nextcloud), I forgot the in the overlay where I overwrote the package from master. Thanks for fixing it!

Related discussion:
text: sha256 = "161050sx3sdxqcpjkjcpf6wl4kx0jydihga7mcvrj9c2f8ly0g07"; }; <ins> patches = [ # Make PyGObject’s gi library available. (substituteAll { src = ./fix-paths.patch; pythonPaths = lib.concatMapStringsSep ", " (pkg: "'${pkg}/${python3.sitePackages}'") [ python3.pkgs.pygobject3 ]; }) ]; </ins> nativeBuildInputs = [ pkg-config which