-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vscode: fix libdbusmenu on kde #210593
vscode: fix libdbusmenu on kde #210593
Conversation
Thanks :) can you fix the two typos in the commit messages? @ofborg test vscode |
To be honest I don't understand how/why this fix works, but that's probably just a lack of knowledge on my side. If you could briefly explain why this works and the previous version didn't, that would be great. Or else another reviewer could approve before I merge. Also, can you fix the typos in the PR title? |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review/3032/1819 |
Can you fix the typos in the commit messages?
This is important so one can later quickly search for commits using Otherwise, this PR is looking good :) |
@ofborg test vscode |
@ofborg test vscodium |
Why are all the tests broken? |
Seems that |
Oh wow, it seems like that's a bug I introduced 3 years ago and noone noticed...? But maybe it's also got to do with the unfree license somehow... |
When did you introduce it? Maybe I can reverse it. |
Should I remove the tests passthru? It seems in |
@ofborg test vscodium.xorg |
We test vscodium on vscode changes since Not sure if it is a good idea to force use the portal, since the test provides a scenario where the file chooser may no longer open with the changes (I guess?) 🤔 |
I believe the idea is that there should be no tests for vscode because we can't run unfree software on CI, but the tests for vscodium have to remain. I'll fix that separately. |
See #216278 |
08c16bf
to
b177184
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
assuming test runs through
@@ -225,6 +228,10 @@ in | |||
--replace "/bin/bash" "${bash}/bin/bash" | |||
rm -rf "$packed" | |||
|
|||
# this fixes "Node Debugger:Attach to process" | |||
substituteInPlace resources/app/extensions/ms-vscode.js-debug/src/extension.js \ | |||
--replace-fail "/bin/ps" "${procps}/bin/ps" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That no longer matches and I can't find it in https://github.com/search?q=repo%3Amicrosoft%2Fvscode-js-debug%20%2Fbin%2Fps&type=code
@ofborg build vscode |
Description of changes
Fix #65680 and also a bug that broke attaching the node debugger to an already running process
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes