jiebi/CodeConvo huggingface dataset:
Code change:
])); RemoveIPC = true; RestrictAddressFamilies = [ <del> "AF_UNIX"  # for sd_notify() call </del> <ins> "AF_UNIX" </ins> "AF_INET" "AF_INET6" <ins> "AF_NETLINK" </ins> ]; RestrictNamespaces = true; RestrictRealtime = true;

Related discussion:
text: lists a listener option called that can be used to listen for incoming network connections only on the specified interface. Unfortunately does not accept this option. Steps to reproduce the behavior: This should evaluate cleanly. Incidentally, that assertion message drops the component in the attribute path, it might be nice to fix that.
Code change:
{ lib , buildGoModule , fetchFromGitHub <ins> , fetchYarnDeps , fixup_yarn_lock </ins> , grafana-agent , nixosTests <ins> , nodejs </ins> , stdenv , systemd , testers <ins> , yarn </ins> }: buildGoModule rec {

Related discussion:
text: I started grafana-agent in flow mode, and tried to access the http API at http://localhost:. Unfortunately, instead of providing a web interface to debug the current list of components, I get a "404 page not found". Steps to reproduce the behavior: grafana-agent in flow mode. port via HTTP I'd expect grafana-agent to ship with the web interface. Please run and paste the result.
It looks like is what's building the frontend. Unfortunately, the web interface seems managed by yarn (and has a ), so we'd need to first provide a . I tried to have resolve the dependency, but it seems it's not able to:
I manually patched things in to bump to a more recent version, compatible with the react version that's mentioned in , but ugh, I'm not really sure why it's that way. I'll ask upstream.
yeah, sorry, I don't use flow mode (yet?) and the nixos module does not support it either, as far as I am aware. I can try looking into it as well, first, before you raise an issue upstream. While the nixos module might lack support for it (for now?), I believe we should try fix it nonetheless :)
Yeah, we should probably have a second NixOS module for flow mode, it's very different and the existing config structure doesn't make much sense - for now I just did ship my own custom systemd unit for it: But yeah, without the web ui it's quite annoying to debug, so we should probably get that sorted out first, before providing a module and getting more people to use it.
fyi
I tried to move it over, but still seems to be terribly slow when trying to resolve deps and not being able to, so I guess we should stay with yarn.
We should prefer yarn simply due to upstream having an instead of a :) ^
Code change:
buildInputs = [ nss nspr libqb ] ++ optional enableDbus dbus <del> ++ optional enableInfiniBandRdma [ librdmacm libibverbs ] </del> <ins> ++ optional enableInfiniBandRdma rdma-core </ins> ++ optional enableMonitoring libstatgrab ++ optional enableSnmp net_snmp;

Related discussion:
text: The packages and are outdated () and have been replaced by the package (). To update a derivation just replace those two packages by as a build input. The following packages depend on and/or : [x] openmpi (fixed in ) [x] (does not find librdmacm in the configure phase when compiled against rdma-core) [x] (infiniband support seems to be defunct. configure does not check for IB libs and it is not linked against any of the required libs, libibverbs or librdmacm) [x] (RDMA support was removed from )
Code change:
{ lib , buildPythonPackage , fetchFromGitHub <del> , setuptools </del> , apispec , boto3 , cachetools

Related discussion:
text: Steps to reproduce the behavior: localstack (from unstable) (version 3.2.0) localstack 2.3.0 works and so does (tagged because you bumped the version) (the channel is slightly messed up. I am using 23.11 but with flakes) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The new version requires too many dependencies to package up in a reasonable time frame and even includes circular ones. contains a revert to 3.0.0 which builds for me and shows the usage. Can you take a look if that works for you?
Sorry for the delay! Yes, the revert works well for me! Thank you!
Code change:
<ins> { lib , mkYarnPackage , fetchFromGitHub , fetchYarnDeps }: let pname = "ember-cli"; version = "5.3.0"; src = fetchFromGitHub { owner = "ember-cli"; repo = "ember-cli"; rev = "v${version}"; hash = "sha256-xkMsPE+iweIV14m4kE4ytEp4uHMJW6gr+n9oJblr4VQ="; }; in mkYarnPackage { inherit pname version src; offlineCache = fetchYarnDeps { yarnLock = src + "/yarn.lock"; hash = "sha256-QgT2JFvMupJo+pJc13n2lmHMZkROJRJWoozCho3E6+c="; }; packageJSON = ./package.json; meta = with lib; { homepage = "https://github.com/ember-cli/ember-cli"; description = "The Ember.js command line utility"; license = licenses.mit; maintainers = with maintainers; [ jfvillablanca ]; platforms = platforms.all; mainProgram = "ember"; }; } </ins>

Related discussion:
text: ember-cli nodePackage The command line utility. If someone could give us some pointers we might actually have a crack at it ourselves ... Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
Code change:
mongoaudit = callPackage ../tools/security/mongoaudit { }; <del> mongodb-compass = callPackage ../tools/misc/mongodb-compass { }; </del> mongodb-tools = callPackage ../tools/misc/mongodb-tools { }; moosefs = callPackage ../tools/filesystems/moosefs { };

Related discussion:
text: Package name: mongodb-compass Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 1.43.0 Current version on the stable/release channel: 1.43.2 <!-- 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]:
Code change:
buildInputs = [ gmp ]; enableParallelBuilding = true; <del> preConfigure = '' cd src ''; </del> <ins> cmakeDir = "../src"; # Running the tests is required to build the *.olean files for the core # library. doCheck = true; postPatch = "patchShebangs ."; </ins> postInstall = stdenv.lib.optionalString stdenv.isDarwin '' substituteInPlace $out/bin/leanpkg 

Related discussion:
text: Describe the bug For some reason neither of nix-env, nix-build or nix-shell compile Lean standard library, i.e. there are no .olean files. This results in abysmal performance even on trivial code, because every time it needs to recompile entire library in memory. Also, there is no leanstatic.a installed. To Reproduce Steps to reproduce the behavior: Expected behavior There should be compiled .olean files. Additional context Building Lean manually using compiles standard_library by default without issues. Also, there was no such issue on older NixOS. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Turned out that compiling standard_lib was included in tests. Adding should fix the issue.
Except that 39 tests have failed :disappointed:
This patch fixes all remaining issues, which proves that in NixOS 20.09 expression for Lean is broken:
Code change:
index 3616104..e9bbfda 100755 --- a/setup.py +++ b/setup.py <del> @@ -112,7 +112,7 @@ class InstallAndUpdateDataDirectory(DistUtilsExtra.auto.install_auto): DistUtilsExtra.auto.install_auto.run(self) target_data = '/' + os.path.relpath(self.install_data, self.root) + '/' </del> <ins> @@ -94,7 +94,7 @@ # Root is undefined if not installing into an alternate root root = self.root or "/" target_data = '/' + os.path.relpath(self.install_data, root) + '/' </ins> -        target_pkgdata = target_data + 'share/ulauncher/' +        target_pkgdata = '@out@/share/ulauncher/' target_scripts = '/' + os.path.relpath(self.install_scripts, <del> self.root) + '/' </del> <ins> root) + '/' </ins>

Related discussion:
text: Describe the bug I'm unsure what the error is, but it seems to relate to ulauncher being unable to find the project path, whatever that may be. To Reproduce Steps to reproduce the behavior: Expected behavior For Ulauncher to start normally Additional context This is the error message I get: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(miyuki): nixpkgs: Maintainer information:
See the PR linked above. The issue is that the ulauncher package must be installed via , , , or something similar. Using does not work (for reasons explained in the patch). The PR both updates ulauncher and adds a note to explain what's going on to Nix users trying out the package. I think it would be a good idea to create a NixOS module for Ulauncher. I might be able to do this after I finish exams in a couple weeks.
Alright guys, the real solution here is to just use rofi. With a little work you can make it look pretty good and with a little extra work one could easily make it look similar to ulauncher. Here is my config I tried to fix this issue up but it seemed to work for maintainers thus it was the end of that story
Hello ulauncher package maintainer here. This definitely shouldn't be the end of the story. I do want to get these issues fixed. The problem is that ulauncher wants to store paths to its assets in a config file within . Typically we'd just let it use paths for everything, but that would cause ulauncher to break if we update the derivation then garbage-collect the old paths in . I also use Rofi right now, and it works. But I really want the plugin ecosystem of Ulauncher, so I'm motivated to fix this situation. Perhaps we could modify the current package to allow decoratively specifying the file contents (like ), which would allow the package to be used without messing with system state? Maybe we could even create something like and a NixOS module?
Perhaps this is a good fit for a home-manager module?
Code change:
index 3616104..e9bbfda 100755 --- a/setup.py +++ b/setup.py <del> @@ -112,7 +112,7 @@ class InstallAndUpdateDataDirectory(DistUtilsExtra.auto.install_auto): DistUtilsExtra.auto.install_auto.run(self) target_data = '/' + os.path.relpath(self.install_data, self.root) + '/' </del> <ins> @@ -94,7 +94,7 @@ # Root is undefined if not installing into an alternate root root = self.root or "/" target_data = '/' + os.path.relpath(self.install_data, root) + '/' </ins> -        target_pkgdata = target_data + 'share/ulauncher/' +        target_pkgdata = '@out@/share/ulauncher/' target_scripts = '/' + os.path.relpath(self.install_scripts, <del> self.root) + '/' </del> <ins> root) + '/' </ins>

Related discussion:
text: In any case, this issue can probably be closed once is merged. Maybe a new issue should be opened to track the addition of an unlauncher module?
I marked this as stale due to inactivity. &rarr;
bad bot
I installed (rev ) through . Unfortunately, I get this error message on launch anyway.
same issue here
Code change:
rustPlatform.buildRustPackage rec { pname = "pastel"; <del> version = "0.8.0"; </del> <ins> version = "0.8.1"; </ins> src = fetchFromGitHub { owner = "sharkdp"; repo = pname; rev = "v${version}"; <del> sha256 = "00xxrssa3gbr5w2jsqlf632jlzc0lc2rpybnbv618ndy5lxidnw0"; </del> <ins> sha256 = "12n1a9j61r4spx0zi2kk85nslv11j1s510asxqvj92ggqhr2s3sq"; </ins> }; <del> cargoSha256 = "0kkhj58q1lgsyj7hpy3sxg1jva9q51m0i7j60zfzhnjnirwcd0h8"; </del> <ins> cargoSha256 = "12zachbg78ajx1n1mqp53rd00dzcss5cqhsq0119lalzc8b5zkrn"; </ins> buildInputs = lib.optional stdenv.isDarwin Security;

Related discussion:
text: Describe the bug Doesn't build. To Reproduce Steps to reproduce the behavior: Expected behavior Screenshots Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Code change:
qtdeclarative = [ ./qtdeclarative.patch ]; qtscript = [ ./qtscript.patch ]; qtserialport = [ ./qtserialport.patch ]; <del> qtwebengine = [ ] </del> <ins> qtwebengine = [ # Fix build with bison-3.7: https://code.qt.io/cgit/qt/qtwebengine-chromium.git/commit/?id=1a53f599 (fetchpatch { name = "qtwebengine-bison-3.7-build.patch"; url = "https://code.qt.io/cgit/qt/qtwebengine-chromium.git/patch/?id=1a53f599"; sha256 = "1nqpyn5fq37q7i9nasag6i14lnz0d7sld5ikqhlm8qwq9d7gbmjy"; stripLen = 1; extraPrefix = "src/3rdparty/"; }) ] </ins> ++ optional stdenv.isDarwin ./qtwebengine-darwin-no-platform-check.patch; qtwebkit = [ ./qtwebkit.patch ] ++ optionals stdenv.isDarwin [

Related discussion:
text: Describe the bug qtwebengine fails just after successfully configuring with error message To Reproduce ` Expected behavior should compile Notify maintainers Metadata
Pull request works on my machine. Thx.
Code change:
<ins> { lib , stdenv , fetchFromGitHub , patsh }: stdenv.mkDerivation rec { pname = "csvquote"; version = "0.1.5"; src = fetchFromGitHub { owner = "dbro"; repo = "csvquote"; rev = "v${version}"; hash = "sha256-847JAoDEfA9K4LB8z9cqSw+GTImqmITBylB/4odLDb0="; }; patches = [ # patch csvheader to use csvquote from the derivation ./csvquote-path.patch ]; nativeBuildInputs = [ patsh ]; makeFlags = [ "BINDIR=$(out)/bin" ]; preInstall = '' mkdir -p "$out/bin" ''; postInstall = '' substituteAllInPlace $out/bin/csvheader patsh $out/bin/csvheader -fs ${builtins.storeDir} ''; meta = with lib; { description = "Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines"; homepage = "https://github.com/dbro/csvquote"; license = licenses.mit; maintainers = with maintainers; [ figsoda ]; platforms = platforms.all; }; } </ins>

Related discussion:
text: Project description Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
Code change:
grep -l -r '/bin/bash' --null | xargs -0 sed -i -e "s!/bin/bash!${bash}/bin/bash!g" ''; <del> buildInputs = [ jdk ant python2 watchman python2Packages.pywatchman ]; nativeBuildInputs = [ makeWrapper ]; </del> <ins> nativeBuildInputs = [ makeWrapper python3 jdk11 ant watchman ]; </ins> buildPhase = '' <ins> # Set correct version, see https://github.com/facebook/buck/issues/2607 echo v${version} > .buckrelease </ins> ant PYTHONDONTWRITEBYTECODE=true ./bin/buck build -c buck.release_version=${version} buck ''; installPhase = '' <del> install -D -m755 buck-out/gen/programs/buck.pex $out/bin/buck </del> <ins> install -D -m755 buck-out/gen/*/programs/buck.pex $out/bin/buck </ins> wrapProgram $out/bin/buck  <del> --prefix PYTHONPATH : $PYTHONPATH  --prefix PATH : "${lib.makeBinPath [jdk watchman]}" </del> <ins> --prefix PATH : "${lib.makeBinPath [ jdk11 watchman python3 ]}" </ins> ''; meta = with lib; {

Related discussion:
text: Buck as installed via nix reports with an older release version than the one listed in its nixpkgs My guess is that is probably the correct version. The issue here is that IIRC buck Expected behavior 's output should match the version rerefenced in the build file. Notify maintainers
I did try to investigate by bumping buck to its latest release that should be Python3 compatible but didn't get very far as I am unfamiliar with the build system. But maybe the patch helps With this I encountered a failure at the end of the build
buck now generates a hash for build outputs
Code change:
<del> [Nemo Action] Active=true Name=Open in Pulsar Comment=Open in Pulsar #%U is the current selected file, this will also work on current directory Exec=pulsar -n %U Icon-Name=pulsar Selection=any Extensions=any </del>

Related discussion:
text: Package name: pulsar Latest released version: 1.117.0 Current version on the unstable channel: 1.114.0 Current version on the stable/release channel: 1.117.0 Notify maintainers
Code change:
"tests/" ]; <del> # See https://github.com/google/jax/issues/9705. disabledTests = lib.optionals usingMKL [ "test_custom_root_with_aux" ]; </del> <ins> # See #  * https://github.com/google/jax/issues/9705 #  * https://discourse.nixos.org/t/getting-different-results-for-the-same-build-on-two-equally-configured-machines/17921 #  * https://github.com/NixOS/nixpkgs/issues/161960 disabledTests = lib.optionals usingMKL [ "test_custom_linear_solve_cholesky" "test_custom_root_with_aux" "testEigvalsGrad_shape" ]; </ins> pythonImportsCheck = [ "jax"

Related discussion:
text: Build of failed on x86_64-linux as of . Maintainer cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
Code change:
<ins> #!/usr/bin/env nix-shell #!nix-shell -i bash -p curl gojq nix-prefetch-github common-updater-scripts set -eou pipefail pkg_dir="$(dirname "$0")" gh-curl () { curl --silent ${GITHUB_TOKEN:+-u ":$GITHUB_TOKEN"} "$1" } version="$(gh-curl "https://api.github.com/repos/ente-io/ente/releases" | gojq 'map(select(.draft == false and .prerelease == false and (.tag_name | startswith("auth-v")))) | first | .tag_name' --raw-output)" short_version="${version:6}" if [[ "$short_version" == "$UPDATE_NIX_OLD_VERSION" ]]; then echo "ente-auth is already up-to-date: $short_version" exit 0 fi echo "Updating to $short_version" # Subtree needed for lockfile and icons auth_tree="$(gh-curl "https://api.github.com/repos/ente-io/ente/git/trees/$version" | gojq '.tree[] | select(.path == "auth") | .url' --raw-output)" # Get lockfile, filter out incompatible sqlite dependency and convert to JSON echo "Updating lockfile" pubspec_lock="$(gh-curl "$auth_tree" | gojq '.tree[] | select(.path == "pubspec.lock") | .url' --raw-output)" gh-curl "$pubspec_lock" | gojq '.content | @base64d' --raw-output | gojq --yaml-input 'del(.packages.sqlite3_flutter_libs)' > "$pkg_dir/pubspec.lock.json" # Get rev and hash of simple-icons submodule echo "Updating icons" assets_tree="$(gh-curl "$auth_tree" | gojq '.tree[] | select(.path == "assets") | .url' --raw-output)" simple_icons_rev="$(gh-curl "$assets_tree" | gojq '.tree[] | select(.path == "simple-icons") | .sha' --raw-output)" nix-prefetch-github --rev "$simple_icons_rev" simple-icons simple-icons > "$pkg_dir/simple-icons.json" # Update package version and hash echo "Updating package source" update-source-version ente-auth "$short_version" --file="$pkg_dir/package.nix" </ins>

Related discussion:
text: Project description Ente's 2FA app. An end-to-end encrypted, cross platform and free app for storing your 2FA codes with cloud backups. Works offline. You can even use it without signing up for an account if you don't want the cloud backups or multi-device sync. Metadata homepage URL: source URL: license: AGPL-3.0 license platforms: linux, windows, android, ios, apple silicon macOS, web Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
sha256 = "0pnva72f2w4jcgnl1y7nw5rdly4ipx3hji4c9yc9s0hna1n2ijxn"; }; <del> buildInputs = [ libxml2 postgresql geos proj gdal json_c protobufc ]; </del> <ins> buildInputs = [ libxml2 postgresql geos proj gdal json_c protobufc ] ++ stdenv.lib.optional stdenv.isDarwin libiconv; </ins> nativeBuildInputs = [ perl pkgconfig ]; dontDisableStatic = true;

Related discussion:
text: Describe the bug has , preventing it from being used on other platforms, particularly Darwin in my case. To Reproduce nix-shell to get this error: error: Package ‘postgis-2.5.2’ in is not supported on ‘x8664-darwin’, refusing to evaluate. Expected behavior Produce a postgresql-and-plugins package with postgis available. Additional context Simply allowing doesn't work immediately because PostGIS' build system is quirky. There was some relevant-looking discussion on . Metadata system: host os: multi-user?: sandbox: version: channels(lukeworth): nixpkgs:
Code change:
necessary, but outside the scope of the Mailman module. </para> </section> <ins> <section xml:id="module-services-mailman-other-mtas"> <title>Using with other MTAs</title> <para> Mailman also supports other MTA, though with a little bit more configuration. For example, to use Mailman with Exim, you can use the following settings: <programlisting>{ config, ... }: { services = { mailman = { enable = true; siteOwner = "mailman@example.org"; <link linkend="opt-services.mailman.enablePostfix">enablePostfix</link> = false; settings.mta = { incoming = "mailman.mta.exim4.LMTP"; outgoing = "mailman.mta.deliver.deliver"; lmtp_host = "localhost"; lmtp_port = "8024"; smtp_host = "localhost"; smtp_port = "25"; configuration = "python:mailman.config.exim4"; }; }; exim = { enable = true; # You can configure Exim in a separate file to reduce configuration.nix clutter config = builtins.readFile ./exim.conf; }; }; }</programlisting> </para> <para> The exim config needs some special additions to work with Mailman. Currently NixOS can't manage Exim config with such granularity. Please refer to <link xlink:href="https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html">Mailman documentation</link> for more info on configuring Mailman for working with Exim. </para> </section> </ins> </chapter>

Related discussion:
text: Describe the bug Mailman module in NixOS requires postfix enabled and has no way to configure Mailman to work with other MTAs supported by both NixOS and mailman upstream. To Reproduce Steps to reproduce the behavior: postfix mailman the evaluation with an assertion Expected behavior The Mailman module allows to select an MTA of choice (or even adapts to the currently enabled MTA) Screenshots n/a Additional context Notify maintainers cc Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(vika): nixpkgs: Maintainer information:
It looks like exim's configuration should be RFC42-ised first if we want to inject Mailman-related settings into Exim config, which is a requirement (Mailman requires a custom Exim router and transport).
Yes, the module is currently quite opinionated. If you're willing to contribute exim support that's great.
I see how I could make it work, but the first version of it will require manual editing of Exim's config files (because RFC42-ising Exim will be a pain, even though I have some drafts on how to translate Nix into the syntax that's required), and I'm not sure if it will be merge-worthy enough :3
Exim config is complicated enough as is, I'm not sure adding an intermediate layer from nix will help that much. I also don't really see this integrating well with existing or other exim config. I'm honestly kind of surprised this works for postfix.
Code change:
usb-devices = callPackage ../development/python-modules/usb-devices { }; <ins> usb-monitor = callPackage ../development/python-modules/usb-monitor { }; </ins> usbrelay-py = callPackage ../os-specific/linux/usbrelay/python.nix { }; usbtmc = callPackage ../development/python-modules/usbtmc { };

Related discussion:
text: Project description As discussed in is now EOL and the dev's have moved their effort to . As per the in order for it to work specific need to be set up. We can probably do something similar to what we do for the expression: Metadata homepage URL: source URL: license: GPL3 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
For people who subscribed to this issue: I opened to add streamcontroller