jiebi/CodeConvo huggingface dataset:
Code change:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.

Related discussion:
text: gnome-menus gnome.gnome-bluetooth_1_0 gnome.gnome-settings-daemon <ins> gnome.mutter </ins> gnome.zenity graphene gtk3
Code change:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.

Related discussion:
text: , budgie-desktop-view , glib , gsettings-desktop-schemas <del> , magpie </del> <ins> , gnome </ins> , mate , nixos-artwork , nixos-background-light ? nixos-artwork.wallpapers.nineish
Code change:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.

Related discussion:
text: budgie-desktop budgie-desktop-view gsettings-desktop-schemas <del> magpie </del> <ins> gnome.mutter </ins> ] ++ extraGSettingsOverridePackages; in
Code change:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.

Related discussion:
text: "-Degl_device=true" "-Dprofiler=true" "-Ddocs=true" <del> "-Dwith_shared_components=true" </del> ]; propagatedBuildInputs = [
Code change:
After the upgrade to 0.68.0 fsautocomplete no longer attach properly to NixVim (neovim). Steps to reproduce the behavior: a minimal NixVim config enable fsautocomplete and Ionide-vim a .fsx file the LspInfo command a see the missing id The clients get associated with an id as before. Version 0.67.0 ! Version 0.68.0 ! I haven't explored if the problem persists outside NixVim, but I would strongly suspect it does, as there haven't been any major changes in NixVim lately. <!-- 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 can confirm you findings. It's an issue with 0.68.0. I'll do some more investigation before filing an issue upstream. for now, you can pin you fsautocomplete to 0.67.0
I've just been testing it a bit as well and came to the same conclusion that it is an upstream problem. I reconfigured my nixvim to build the from the nuget package and that one has the same issue. How do I pin in nixvim?
sorry I am not familiar with nixvim, my neovim just calls fsautocomplete from PATH. So I've just installed an old version via thats the commit just before 0.68.0 update
are you able to test ?
Working on it.

Related discussion:
text: <del> { lib, buildDotnetModule, fetchFromGitHub, dotnetCorePackages, stdenv }: </del> <ins> { lib, buildDotnetModule, fetchFromGitHub, dotnetCorePackages }: </ins> let <del> inherit (dotnetCorePackages) combinePackages sdk_6_0 sdk_7_0; </del> <ins> inherit (dotnetCorePackages) sdk_7_0; </ins> in buildDotnetModule rec { pname = "fsautocomplete";
Code change:
After the upgrade to 0.68.0 fsautocomplete no longer attach properly to NixVim (neovim). Steps to reproduce the behavior: a minimal NixVim config enable fsautocomplete and Ionide-vim a .fsx file the LspInfo command a see the missing id The clients get associated with an id as before. Version 0.67.0 ! Version 0.68.0 ! I haven't explored if the problem persists outside NixVim, but I would strongly suspect it does, as there haven't been any major changes in NixVim lately. <!-- 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 can confirm you findings. It's an issue with 0.68.0. I'll do some more investigation before filing an issue upstream. for now, you can pin you fsautocomplete to 0.67.0
I've just been testing it a bit as well and came to the same conclusion that it is an upstream problem. I reconfigured my nixvim to build the from the nuget package and that one has the same issue. How do I pin in nixvim?
sorry I am not familiar with nixvim, my neovim just calls fsautocomplete from PATH. So I've just installed an old version via thats the commit just before 0.68.0 update
are you able to test ?
Working on it.

Related discussion:
text: --replace TargetFrameworks TargetFramework  ''; <del> dotnet-sdk = combinePackages [ sdk_7_0 sdk_6_0 ]; dotnet-runtime = sdk_6_0; </del> <ins> dotnet-sdk = sdk_7_0; dotnet-runtime = sdk_7_0; </ins> projectFile = "src/FsAutoComplete/FsAutoComplete.fsproj"; executables = [ "fsautocomplete" ];
Code change:
After the upgrade to 0.68.0 fsautocomplete no longer attach properly to NixVim (neovim). Steps to reproduce the behavior: a minimal NixVim config enable fsautocomplete and Ionide-vim a .fsx file the LspInfo command a see the missing id The clients get associated with an id as before. Version 0.67.0 ! Version 0.68.0 ! I haven't explored if the problem persists outside NixVim, but I would strongly suspect it does, as there haven't been any major changes in NixVim lately. <!-- 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 can confirm you findings. It's an issue with 0.68.0. I'll do some more investigation before filing an issue upstream. for now, you can pin you fsautocomplete to 0.67.0
I've just been testing it a bit as well and came to the same conclusion that it is an upstream problem. I reconfigured my nixvim to build the from the nuget package and that one has the same issue. How do I pin in nixvim?
sorry I am not familiar with nixvim, my neovim just calls fsautocomplete from PATH. So I've just installed an old version via thats the commit just before 0.68.0 update
are you able to test ?
Working on it.

Related discussion:
text: (fetchNuGet { pname = "McMaster.NETCore.Plugins"; version = "1.4.0"; sha256 = "1k2qz0qnf2b1kfwbzcynivy93jm7dcwl866d0fl7qlgq5vql7niy"; }) (fetchNuGet { pname = "MessagePack"; version = "2.5.108"; sha256 = "0cnaz28lhrdmavnxjkakl9q8p2yv8mricvp1b0wxdfnz8v41gwzs"; }) (fetchNuGet { pname = "MessagePack.Annotations"; version = "2.5.108"; sha256 = "0nb1fx8dwl7304kw0bc375bvlhb7pg351l4cl3vqqd7d8zqjwx5v"; }) <ins> (fetchNuGet { pname = "Microsoft.AspNetCore.App.Ref"; version = "6.0.24"; sha256 = "0lriw4f48f0q2vyagbngnffshdismn3msn7d6dj0lb2xdkzsz1f1"; }) (fetchNuGet { pname = "Microsoft.AspNetCore.App.Runtime.linux-arm64"; version = "6.0.24"; sha256 = "08670zhn2ywkwy0d7sj89rikxccy5qg0vsjwpbypvzndawng0bb9"; }) (fetchNuGet { pname = "Microsoft.AspNetCore.App.Runtime.linux-x64"; version = "6.0.24"; sha256 = "0knx6lhlqxn3lkgakpab0663788q0si00m9ga7wdn2mzqq0s9yx0"; }) </ins> (fetchNuGet { pname = "Microsoft.Bcl.AsyncInterfaces"; version = "7.0.0"; sha256 = "1waiggh3g1cclc81gmjrqbh128kwfjky3z79ma4bd2ms9pa3gvfm"; }) (fetchNuGet { pname = "Microsoft.Bcl.HashCode"; version = "1.1.0"; sha256 = "1ggsadahlp76zcn1plapszd5v5ja8rh479fwrahqd3knql4dfnr0"; }) (fetchNuGet { pname = "Microsoft.Build"; version = "17.2.0"; sha256 = "09hs74nr0kv83wc1way9x7vq3nmxbr2s4vdy99hx78kj25pylcr7"; })
Code change:
After the upgrade to 0.68.0 fsautocomplete no longer attach properly to NixVim (neovim). Steps to reproduce the behavior: a minimal NixVim config enable fsautocomplete and Ionide-vim a .fsx file the LspInfo command a see the missing id The clients get associated with an id as before. Version 0.67.0 ! Version 0.68.0 ! I haven't explored if the problem persists outside NixVim, but I would strongly suspect it does, as there haven't been any major changes in NixVim lately. <!-- 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 can confirm you findings. It's an issue with 0.68.0. I'll do some more investigation before filing an issue upstream. for now, you can pin you fsautocomplete to 0.67.0
I've just been testing it a bit as well and came to the same conclusion that it is an upstream problem. I reconfigured my nixvim to build the from the nuget package and that one has the same issue. How do I pin in nixvim?
sorry I am not familiar with nixvim, my neovim just calls fsautocomplete from PATH. So I've just installed an old version via thats the commit just before 0.68.0 update
are you able to test ?
Working on it.

Related discussion:
text: (fetchNuGet { pname = "Microsoft.NET.StringTools"; version = "17.4.0"; sha256 = "1smx30nq22plrn2mw4wb5vfgxk6hyx12b60c4wabmpnr81lq3nzv"; }) (fetchNuGet { pname = "Microsoft.NET.StringTools"; version = "17.6.3"; sha256 = "0g5jdg0jp844a2ygwlm04igsxkrihqcq2rpmfx722nrv3vrk0r0z"; }) (fetchNuGet { pname = "Microsoft.NET.Test.Sdk"; version = "17.4.1"; sha256 = "02p1j9fncd4fb2hyp51kw49d0dz30vvazhzk24c9f5ccc00ijpra"; }) <ins> (fetchNuGet { pname = "Microsoft.NETCore.App.Host.linux-arm64"; version = "6.0.24"; sha256 = "1vyy01i4w2wcx82mrjjsbp98v9sjn1cwhdvkhrw8yrrb04lcxbir"; }) (fetchNuGet { pname = "Microsoft.NETCore.App.Host.linux-x64"; version = "6.0.24"; sha256 = "02l6javfqwsaialkimmpsq3v4dhb1j4sxy19yvr5w5sdjmq1jh5y"; }) (fetchNuGet { pname = "Microsoft.NETCore.App.Ref"; version = "6.0.24"; sha256 = "1fy1hr14igy4lix4vmwkjj13cbyjjfhx8izch9cd9hc4f1y25767"; }) (fetchNuGet { pname = "Microsoft.NETCore.App.Runtime.linux-arm64"; version = "6.0.24"; sha256 = "1zcn4px94z67j60cidynm5ab8cln1rrxabv7c24mlajqnkfw14sb"; }) (fetchNuGet { pname = "Microsoft.NETCore.App.Runtime.linux-x64"; version = "6.0.24"; sha256 = "0rylvdvdc5rdmw2vcqi0fdzmiwwa1pwlqiavqnb2pslhhq8qg4mh"; }) </ins> (fetchNuGet { pname = "Microsoft.NETCore.Platforms"; version = "7.0.4"; sha256 = "0afmivk3m0hmwsiqnl87frzi7g57aiv5fwnjds0icl66djpb6zsm"; }) (fetchNuGet { pname = "Microsoft.NETCore.Targets"; version = "5.0.0"; sha256 = "0z3qyv7qal5irvabc8lmkh58zsl42mrzd1i0sssvzhv4q4kl3cg6"; }) (fetchNuGet { pname = "Microsoft.NETFramework.ReferenceAssemblies"; version = "1.0.3"; sha256 = "0hc4d4d4358g5192mf8faijwk0bpf9pjwcfd3h85sr67j0zhj6hl"; })
Code change:
Project description <!-- Describe the project a little: --I've recently watched the videos on norg and found the plugin very code. At some point though I had an error because my system was missing this treesitter grammar: It doesn't seem packaged yet (I checked unstable). Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: tree-sitter-nickel = lib.importJSON ./tree-sitter-nickel.json; tree-sitter-nix = lib.importJSON ./tree-sitter-nix.json; tree-sitter-norg = lib.importJSON ./tree-sitter-norg.json; <ins> tree-sitter-norg-meta = lib.importJSON ./tree-sitter-norg-meta.json; </ins> tree-sitter-nu = lib.importJSON ./tree-sitter-nu.json; tree-sitter-ocaml = lib.importJSON ./tree-sitter-ocaml.json; tree-sitter-org-nvim = lib.importJSON ./tree-sitter-org-nvim.json;
Code change:
Project description <!-- Describe the project a little: --I've recently watched the videos on norg and found the plugin very code. At some point though I had an error because my system was missing this treesitter grammar: It doesn't seem packaged yet (I checked unstable). Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <ins> { "url": "https://github.com/nvim-neorg/tree-sitter-norg-meta", "rev": "a479d1ca05848d0b51dd25bc9f71a17e0108b240", "date": "2023-05-28T19:01:42+02:00", "path": "/nix/store/7yp5rzpmdvyhhl38brhz0vl3gd9qv03y-tree-sitter-norg-meta", "sha256": "1vvl39m41wgsq7xkfi523zx6nza03dkzgk6izc39igmwx5hsdl7f", "hash": "sha256-7tCmYem8vpgG+9HM92cbQH1r+h+iRDf7wfrxQGoadO8=", "fetchLFS": false, "fetchSubmodules": false, "deepClone": false, "leaveDotGit": false } </ins>
Code change:
Project description <!-- Describe the project a little: --I've recently watched the videos on norg and found the plugin very code. At some point though I had an error because my system was missing this treesitter grammar: It doesn't seem packaged yet (I checked unstable). Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: "tree-sitter-agda" # abandoned "tree-sitter-fluent" <ins> # to unblock my update "csharp-tree-sitter" </ins> ]; ignoredTreeSitterOrgReposJson = jsonFile "ignored-tree-sitter-org-repos" ignoredTreeSitterOrgRepos;
Code change:
Project description <!-- Describe the project a little: --I've recently watched the videos on norg and found the plugin very code. At some point though I had an error because my system was missing this treesitter grammar: It doesn't seem packaged yet (I checked unstable). Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: orga = "nvim-neorg"; repo = "tree-sitter-norg"; }; <ins> "tree-sitter-norg-meta" = { orga = "nvim-neorg"; repo = "tree-sitter-norg-meta"; }; </ins> "tree-sitter-commonlisp" = { orga = "thehamsta"; repo = "tree-sitter-commonlisp";
Code change:
Package name: ticktick Latest released version: 2.0.0 Current version on the unstable channel: 1.0.80 Notify maintainers Please update to the latest version. Thanks

Related discussion:
text: }: stdenv.mkDerivation (finalAttrs: { pname = "ticktick"; <del> version = "1.0.80"; </del> <ins> version = "2.0.0"; </ins> src = fetchurl { url = "https://d2atcrkye2ik4e.cloudfront.net/download/linux/linux_deb_x64/${finalAttrs.pname}-${finalAttrs.version}-amd64.deb"; <del> hash = "sha256-EK+8NFEim2gcFj9t6AGYdGVlyFj9Yq7NaOia3XKy3cc="; </del> <ins> hash = "sha256-LOllYdte+Y+pbjXI2zOQrwptmUo4Ck6OyYoEX6suY08="; </ins> }; nativeBuildInputs = [
Code change:
Steps to reproduce the behavior: spotdl I just tried to install it, doing it from or gives the same result. Let me know if I can provide more useful information.

Related discussion:
text: python = python3; in python.pkgs.buildPythonApplication rec { pname = "spotdl"; <del> version = "4.2.1"; format = "pyproject"; </del> <ins> version = "4.2.2"; pyproject = true; </ins> src = fetchFromGitHub { owner = "spotDL"; repo = "spotify-downloader"; rev = "refs/tags/v${version}"; <del> hash = "sha256-xKas3WO3uigY1iFfxIN3+d+5U31vM7cLv08oMef8trc="; </del> <ins> hash = "sha256-pJr0OGUI3OcFsmvn9eqkvpFeF1EkHDdNoWc91s8h9O8="; </ins> }; nativeBuildInputs = with python.pkgs; [
Code change:
Steps to reproduce the behavior: spotdl I just tried to install it, doing it from or gives the same result. Let me know if I can provide more useful information.

Related discussion:
text: # require networking "tests/test_init.py" "tests/test_matching.py" <ins> "tests/providers/lyrics" "tests/types" "tests/utils/test_github.py" </ins> "tests/utils/test_m3u.py" "tests/utils/test_metadata.py" "tests/utils/test_search.py"
Code change:
Upon login, Fcitx5 presents a popup notification telling me to unset and . This is specifically in the Plasma 6 (alpha) Wayland session. The environment variables appear to be set in the Fcitx5 NixOS module. also for ibus. I'm not sure if the other IMEs are supposed to work on Wayland at all. (nixos-unstable with Plasma 6 alpha from nix-community/kde2nix)
It's mostly impossible to detect if the user is currently using the plasma wayland session (unless with some custom profile scripts). Maybe we should add an option allowing disabling the automatic configuration of these environment variables.
FWIW Plasma 6 defaults the "plasma" session to wayland. The X11 session is renamed to "plasmax11". At least Plasma has some startup script generated by nix, I think at that point it might be known whether it is Wayland or not?
But users can still choose the session to use upon login right? However the current fcitx5 nixos module unconditionally sets these variables, without a runtime detection mechanism.
Is that possible to detect that at runtime, with something like ?
Well that's the part. But I'd rather let the users decide than trying to act smart. There are both pros and cons of using the immodules or not.
That's why I pointed out the startup script from the plasma module.
I mean it's not a must (or even should, IMO) that you unset and for the wayland session. The input method story is very complicated, with different applications/compositors/input methods supporting different protocols of varying compatibility and functionality. Setting these variables by default in most cases, won't worsen the situation. You may read https://fcitx- for some background.
Hmm, I see. Maybe they could be set with so users or other modules can easily override them?
Reasonable, but empty string and unset do have different meaning regarding these variables. So I think a blanket option to unset then entirely is more desirable.
Is there any temporary workaround? I can't find out how to unset it, I don't think there is way besides making it blank which might work? I am confused as to how to get IME to work on Hyprland or Wayland at all though, if I can't get Japanese IME to work it's a complete deal breaker for me personally Edit, this worked for me personally. Using Fcitx on GTK crashes my Hyprland, but seems the QT one works fine? I am super confused now. But glad to see that IME support seems to be baked into Wayland itself somewhat I just hope it makes it work just as well as Windows in the far future: Also you will need this at the top of your file where you set it
If hyprland crashes, that's a hyprland issue, the fcitx5 gtk immodule works fine on most other platforms, such as sway.

Related discussion:
text: Enabled Fcitx5 addons. ''; }; <ins> waylandFrontend = mkOption { type = types.bool; default = false; description = lib.mdDoc '' Use the Wayland input method frontend. See [Using Fcitx 5 on Wayland](https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland). ''; }; </ins> quickPhrase = mkOption { type = with types; attrsOf str; default = { };
Code change:
Upon login, Fcitx5 presents a popup notification telling me to unset and . This is specifically in the Plasma 6 (alpha) Wayland session. The environment variables appear to be set in the Fcitx5 NixOS module. also for ibus. I'm not sure if the other IMEs are supposed to work on Wayland at all. (nixos-unstable with Plasma 6 alpha from nix-community/kde2nix)
It's mostly impossible to detect if the user is currently using the plasma wayland session (unless with some custom profile scripts). Maybe we should add an option allowing disabling the automatic configuration of these environment variables.
FWIW Plasma 6 defaults the "plasma" session to wayland. The X11 session is renamed to "plasmax11". At least Plasma has some startup script generated by nix, I think at that point it might be known whether it is Wayland or not?
But users can still choose the session to use upon login right? However the current fcitx5 nixos module unconditionally sets these variables, without a runtime detection mechanism.
Is that possible to detect that at runtime, with something like ?
Well that's the part. But I'd rather let the users decide than trying to act smart. There are both pros and cons of using the immodules or not.
That's why I pointed out the startup script from the plasma module.
I mean it's not a must (or even should, IMO) that you unset and for the wayland session. The input method story is very complicated, with different applications/compositors/input methods supporting different protocols of varying compatibility and functionality. Setting these variables by default in most cases, won't worsen the situation. You may read https://fcitx- for some background.
Hmm, I see. Maybe they could be set with so users or other modules can easily override them?
Reasonable, but empty string and unset do have different meaning regarding these variables. So I think a blanket option to unset then entirely is more desirable.
Is there any temporary workaround? I can't find out how to unset it, I don't think there is way besides making it blank which might work? I am confused as to how to get IME to work on Hyprland or Wayland at all though, if I can't get Japanese IME to work it's a complete deal breaker for me personally Edit, this worked for me personally. Using Fcitx on GTK crashes my Hyprland, but seems the QT one works fine? I am super confused now. But glad to see that IME support seems to be baked into Wayland itself somewhat I just hope it makes it work just as well as Windows in the far future: Also you will need this at the top of your file where you set it
If hyprland crashes, that's a hyprland issue, the fcitx5 gtk immodule works fine on most other platforms, such as sway.

Related discussion:
text: ]; environment.variables = { <del> GTK_IM_MODULE = "fcitx"; QT_IM_MODULE = "fcitx"; </del> XMODIFIERS = "@im=fcitx"; QT_PLUGIN_PATH = [ "${fcitx5Package}/${pkgs.qt6.qtbase.qtPluginPrefix}" ]; <ins> } // lib.optionalAttrs (!cfg.waylandFrontend) { GTK_IM_MODULE = "fcitx"; QT_IM_MODULE = "fcitx"; </ins> } // lib.optionalAttrs cfg.ignoreUserConfig { SKIP_FCITX_USER_PATH = "1"; };