jiebi/CodeConvo huggingface dataset:
Code change:
Describe the bug addon in chromium does not work. After install addon show errors: "Failed to connect to the main process." "Verify the installation of the plasma-browser-integration package. The running environment of the Plasma desktop environment must be at least version 5.13." "Specified native messaging host not found." Manually run from console not help. To Reproduce Steps to reproduce the behavior: Add to : Expected behavior No errors. Additional context I found issue Everything looks like the same problem but in chromium 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 nix-shell -p nix-info --run "nix-info -m" and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Try adding the following line to your configuration:
now And also does not work. Maybe I need to reboot?
That issue is actually unrelated, it has to do with a patch only in our source build of firefox.
I make test with: in . The same error.
I can't reproduce this issue. I just tested in a vm using with this configuration: Are you using plasma5?
Yes plasma5. Looks like it worked for me too. Now all errors are gone. Thanks !
Why are we adding to systemPackages when using the chromium program module? It does this for you.
Just an oversight on my part. You're right, adding chromium to systemPackages is not necessary.
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 .
Thanks - the fix worked for me! Can you please comment on what's the role of package that you install?
I marked this as stale due to inactivity. &rarr;
Proposed fix in

Related discussion:
text: [ExtensionInstallForcelist](https://cloud.google.com/docs/chrome-enterprise/policies/?policy=ExtensionInstallForcelist) for additional details. ''; <del> default = []; </del> <ins> default = null; </ins> example = literalExpression '' [ "chlffgpmiacpedhhbkiomidkjlcfhogd" # pushbullet
Code change:
Describe the bug addon in chromium does not work. After install addon show errors: "Failed to connect to the main process." "Verify the installation of the plasma-browser-integration package. The running environment of the Plasma desktop environment must be at least version 5.13." "Specified native messaging host not found." Manually run from console not help. To Reproduce Steps to reproduce the behavior: Add to : Expected behavior No errors. Additional context I found issue Everything looks like the same problem but in chromium 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 nix-shell -p nix-info --run "nix-info -m" and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Try adding the following line to your configuration:
now And also does not work. Maybe I need to reboot?
That issue is actually unrelated, it has to do with a patch only in our source build of firefox.
I make test with: in . The same error.
I can't reproduce this issue. I just tested in a vm using with this configuration: Are you using plasma5?
Yes plasma5. Looks like it worked for me too. Now all errors are gone. Thanks !
Why are we adding to systemPackages when using the chromium program module? It does this for you.
Just an oversight on my part. You're right, adding chromium to systemPackages is not necessary.
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 .
Thanks - the fix worked for me! Can you please comment on what's the role of package that you install?
I marked this as stale due to inactivity. &rarr;
Proposed fix in

Related discussion:
text: "PasswordManagerEnabled" = false; "SpellcheckEnabled" = true; "SpellcheckLanguage" = [ <del> "de" "en-US" ]; </del> <ins> "de" "en-US" ]; </ins> } ''; };
Code change:
Describe the bug addon in chromium does not work. After install addon show errors: "Failed to connect to the main process." "Verify the installation of the plasma-browser-integration package. The running environment of the Plasma desktop environment must be at least version 5.13." "Specified native messaging host not found." Manually run from console not help. To Reproduce Steps to reproduce the behavior: Add to : Expected behavior No errors. Additional context I found issue Everything looks like the same problem but in chromium 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 nix-shell -p nix-info --run "nix-info -m" and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Try adding the following line to your configuration:
now And also does not work. Maybe I need to reboot?
That issue is actually unrelated, it has to do with a patch only in our source build of firefox.
I make test with: in . The same error.
I can't reproduce this issue. I just tested in a vm using with this configuration: Are you using plasma5?
Yes plasma5. Looks like it worked for me too. Now all errors are gone. Thanks !
Why are we adding to systemPackages when using the chromium program module? It does this for you.
Just an oversight on my part. You're right, adding chromium to systemPackages is not necessary.
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 .
Thanks - the fix worked for me! Can you please comment on what's the role of package that you install?
I marked this as stale due to inactivity. &rarr;
Proposed fix in

Related discussion:
text: system.userActivationScripts.plasmaSetup = activationScript; programs.firefox.nativeMessagingHosts.packages = [ pkgs.plasma5Packages.plasma-browser-integration ]; <ins> programs.chromium.enablePlasmaBrowserIntegration = true; </ins> }) (mkIf (cfg.kwinrc != {}) {
Code change:
To Reproduce Additional context I am building the package on an x8664 machine via distributed build, if that makes any difference. I have also tried to build with llvmPackages8 through 10 and I got the same result. Notify maintainers Metadata Maintainer information:
This looks just like Unsure why it's reoccurring.
Caused by
This is native linux i868? Interesting, it is deciding to build nothing but headers, and then only the dev output is present. I am curious what it decided to build before that filled .
Ah! I bet it was auto-detecting and that gave it something to build, but now the correct arch is manually specified.
I can confirm that reverting fixed this issue.
hopefully fixed in
I'm seeing something similar for 32-bit arm on recent master () , ([build log][]). Do we need to make a version of for ? [build log]:
I suspect that since (and previously ) on i686 is really only building the bare minimum: whereas on : Missing are asan, ubsan related libs and much more. I should probably open a new issue for this.

Related discussion:
text: # can build this. If we didn't do it, basically the entire nixpkgs on Darwin would have an unfree dependency and we'd # get no binary cache for the entire platform. If you really find yourself wanting the TSAN, make this controllable by # a flag and turn the flag off during the stdenv build. <del> postPatch = stdenv.lib.optionalString stdenv.isDarwin '' </del> <ins> postPatch = '' substituteInPlace cmake/builtin-config-ix.cmake  --replace 'set(X86 i386)' 'set(X86 i386 i486 i586 i686)' '' + stdenv.lib.optionalString stdenv.isDarwin '' </ins> substituteInPlace cmake/config-ix.cmake  --replace 'set(COMPILER_RT_HAS_TSAN TRUE)' 'set(COMPILER_RT_HAS_TSAN FALSE)' '' + stdenv.lib.optionalString (useLLVM) ''
Code change:
Project description is already packaged in nixpkgs, but the upstream project has been taken over by new maintainers who have ported it to Python 3 and are continuing development. As far as I know this new version is also used by Debian/Ubuntu (it has python3 dependencies in those distros). I have a local attempt at a new derivation and it Works For Me, but it has a patch in it which I don't think it should need. Also, maybe the original maintainer may want to do the update? If desired I can open a PR with my current state of affairs. Metadata homepage URL: license: GPL2 platforms: Linux
I have limited spare time these days (months), so please be my guest

Related discussion:
text: <del> { stdenv, fetchurl, python2, keybinder3, intltool, file, gtk3, gobject-introspection , libnotify, wrapGAppsHook, vte </del> <ins> { stdenv , fetchFromGitHub , python , keybinder3 , intltool , file , gtk3 , gobject-introspection , libnotify , wrapGAppsHook , vte </ins> }: <del> python2.pkgs.buildPythonApplication rec { </del> <ins> python.pkgs.buildPythonApplication rec { </ins> name = "terminator-${version}"; <del> version = "1.91"; </del> <ins> version = "1.92"; </ins> <del> src = fetchurl { url = "https://launchpad.net/terminator/gtk3/${version}/+download/${name}.tar.gz"; sha256 = "95f76e3c0253956d19ceab2f8da709a496f1b9cf9b1c5b8d3cd0b6da3cc7be69"; </del> <ins> src = fetchFromGitHub { owner = "gnome-terminator"; repo = "terminator"; rev = "bb24273eb40dc5eac97de74064488701fa40a743"; sha256 = "105f660wzf9cpn24xzwaaa09igg5h3qhchafv190v5nqck6g1ssh"; </ins> }; <del> nativeBuildInputs = [ file intltool wrapGAppsHook gobject-introspection ]; buildInputs = [ gtk3 vte libnotify keybinder3 </del> <ins> nativeBuildInputs = [ file intltool gobject-introspection wrapGAppsHook ]; buildInputs = [ gtk3 </ins> gobject-introspection # Temporary fix, see https://github.com/NixOS/nixpkgs/issues/56943 <ins> keybinder3 libnotify python vte ]; propagatedBuildInputs = with python.pkgs; [ configobj dbus-python pygobject3 psutil pycairo </ins> ]; <del> propagatedBuildInputs = with python2.pkgs; [ pygobject3 psutil pycairo ]; </del> postPatch = '' patchShebangs . <ins> # dbus-python is correctly passed in propagatedBuildInputs, but for some reason setup.py complains. # The wrapped terminator has the correct path added, so ignore this. substituteInPlace setup.py --replace "'dbus-python'," "" </ins> ''; checkPhase = ''
Code change:
Project description is already packaged in nixpkgs, but the upstream project has been taken over by new maintainers who have ported it to Python 3 and are continuing development. As far as I know this new version is also used by Debian/Ubuntu (it has python3 dependencies in those distros). I have a local attempt at a new derivation and it Works For Me, but it has a patch in it which I don't think it should need. Also, maybe the original maintainer may want to do the update? If desired I can open a PR with my current state of affairs. Metadata homepage URL: license: GPL2 platforms: Linux
I have limited spare time these days (months), so please be my guest

Related discussion:
text: quadkonsole, etc. in that the main focus is arranging terminals in grids (tabs is the most common default method, which Terminator also supports). ''; <del> homepage = "https://gnometerminator.blogspot.no/p/introduction.html"; </del> <ins> homepage = "https://github.com/gnome-terminator/terminator"; </ins> license = licenses.gpl2; maintainers = with maintainers; [ bjornfor ]; platforms = platforms.linux;
Code change:
Project description is already packaged in nixpkgs, but the upstream project has been taken over by new maintainers who have ported it to Python 3 and are continuing development. As far as I know this new version is also used by Debian/Ubuntu (it has python3 dependencies in those distros). I have a local attempt at a new derivation and it Works For Me, but it has a patch in it which I don't think it should need. Also, maybe the original maintainer may want to do the update? If desired I can open a PR with my current state of affairs. Metadata homepage URL: license: GPL2 platforms: Linux
I have limited spare time these days (months), so please be my guest

Related discussion:
text: terminal-notifier = callPackage ../applications/misc/terminal-notifier {}; <del> terminator = callPackage ../applications/misc/terminator { }; </del> <ins> terminator = callPackage ../applications/misc/terminator { python = python3; }; </ins> terminus = callPackage ../applications/misc/terminus { };
Code change:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. &rarr;
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

Related discussion:
text: fsNeededForBoot = fs: fs.neededForBoot || elem fs.mountPoint pathsNeededForBoot; # Check whenever `b` depends on `a` as a fileSystem <del> fsBefore = a: b: a.mountPoint == b.device || hasPrefix "${a.mountPoint}${optionalString (!(hasSuffix "/" a.mountPoint)) "/"}" b.mountPoint; </del> <ins> fsBefore = a: b: let # normalisePath adds a slash at the end of the path if it didn't already # have one. # # The reason slashes are added at the end of each path is to prevent `b` # from accidentally depending on `a` in cases like #    a = { mountPoint = "/aaa"; ... } #    b = { device     = "/aaaa"; ... } # Here a.mountPoint *is* a prefix of b.device even though a.mountPoint is # *not* a parent of b.device. If we add a slash at the end of each string, # though, this is not a problem: "/aaa/" is not a prefix of "/aaaa/". normalisePath = path: "${path}${optionalString (!(hasSuffix "/" path)) "/"}"; normalise = mount: mount // { device = normalisePath mount.device; mountPoint = normalisePath mount.mountPoint; depends = map normalisePath mount.depends; }; a' = normalise a; b' = normalise b; in hasPrefix a'.mountPoint b'.device || hasPrefix a'.mountPoint b'.mountPoint || any (hasPrefix a'.mountPoint) b'.depends; </ins> # Escape a path according to the systemd rules, e.g. /dev/xyzzy # becomes dev-xyzzy.  FIXME: slow.
Code change:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. &rarr;
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

Related discussion:
text: "upperdir=/nix/.rw-store/store" "workdir=/nix/.rw-store/work" ]; <ins> depends = [ "/nix/.ro-store" "/nix/.rw-store/store" "/nix/.rw-store/work" ]; </ins> }; boot.initrd.availableKernelModules = [ "squashfs" "iso9660" "uas" "overlay" ];
Code change:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. &rarr;
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

Related discussion:
text: "upperdir=/nix/.rw-store/store" "workdir=/nix/.rw-store/work" ]; <ins> depends = [ "/nix/.ro-store" "/nix/.rw-store/store" "/nix/.rw-store/work" ]; </ins> }; boot.initrd.availableKernelModules = [ "squashfs" "overlay" ];
Code change:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. &rarr;
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

Related discussion:
text: specialFSTypes = [ "proc" "sysfs" "tmpfs" "ramfs" "devtmpfs" "devpts" ]; <ins> nonEmptyWithoutTrailingSlash = addCheckDesc "non-empty without trailing slash" types.str (s: isNonEmpty s && (builtins.match ".+/" s) == null); </ins> coreFileSystemOpts = { name, config, ... }: { options = { mountPoint = mkOption { example = "/mnt/usb"; <del> type = addCheckDesc "non-empty without trailing slash" types.str (s: isNonEmpty s && (builtins.match ".+/" s) == null); </del> <ins> type = nonEmptyWithoutTrailingSlash; </ins> description = "Location of the mounted the file system."; };
Code change:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. &rarr;
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:

Related discussion:
text: type = types.listOf nonEmptyStr; }; <ins> depends = mkOption { default = [ ]; example = [ "/persist" ]; type = types.listOf nonEmptyWithoutTrailingSlash; description = '' List of paths that should be mounted before this one. This filesystem's <option>device</option> and <option>mountPoint</option> are always checked and do not need to be included explicitly. If a path is added to this list, any other filesystem whose mount point is a parent of the path will be mounted before this filesystem. The paths do not need to actually be the <option>mountPoint</option> of some other filesystem. ''; }; </ins> }; config = {