-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
Fix electron crash when using file chooser dialog #55057
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
Fix electron crash when using file chooser dialog #55057
Conversation
58b4325
to
4fc1758
Compare
How does this relate to electron apps? Is |
#58273 is fixed by this as well, I think? |
@jtojnar wrote:
Some packages like riot-desktop, which is affected by the issue solved by this PR, launch the |
Right.. Lots of checkboxes to tick to merge this... I'll see when I have a chance.. Unless anyone could help ticking them on? :) |
Are all of them mandatory? I only have nixos on my machines running - no osx around.. |
They serve mainly to let reviewers know what you already did and that you are familiar with the contributing guidelines. Like many things around Nix, the individual checkboxes are left for PR authors to decide if they need them.
This should be done almost every time always every time, since without it, author cannot know if the change works. Sandboxing is also important to rule out accidental impurities that would break build for other people (most importantly, Hydra builds with sandboxing enabled).
This ties in to the first check mark. It is mostly to let the reviewers know where, you are certain, the change works. The more platforms are verified the better but we do not require user to check platforms they do not have access to.
Here the applicability is described directly.
This would be very nice to have but the command is often very resource intensive, therefore some people are unable to run it. For that reason, we do not mandate it. Also not that nox is somewhat abandoned and many people use nix-review instead.
This is also a good idea to make sure everything works as expected. If you are very certain your change does not affect the binaries, then you can skip it. For libraries, I usually just verify that the apps that use them still link and at least one of them can be run. Generally, if you update an application nothing depends on, checking if it starts is probably enough; for widely used libraries (e.g. GTK) you should be more diligent.
This one would be nice to have for any update but I only ever bother when I change the set of dependencies. There might be a size creep in a release without dependency changes but that is probably extremely rare.
This is very important but discovering all relevant docs can be hard. You should try
This is probably the only hard requirement. You can decide to ignore some points from there if you have a good reason, but that is better left for experienced maintainers. |
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.
The solution looks good from GTK point of view but I did not test it.
wow. thanks @jtojnar for the explanation! - I think we could even extend the github PR template with your text :) re sandbox, I read this is the default, but to be sure I also checked with |
woah excellent tool!
|
4fc1758
to
bf36d56
Compare
reworded commit message as per contributing doc |
thanks for approving @jtojnar just to check what are the next steps for this pr? or just wait? :) |
This is what upstream uses as well
This is now provided by electron itself.
Just tested this with rambox |
Motivation for this change
#50985
Thanks @jtojnar for the solution!
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)