Skip to content
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

Change notification to be transient (notify-send) #11733

Merged
merged 6 commits into from
Feb 25, 2022

Conversation

BudgieInWA
Copy link
Contributor

Summary

Under GNOME Shell, using --notify (especially with --watch) floods the notification UI with unnecessary persistent copies of each notification that is raised. This PR aims to close #8773.

Test plan

I have only tested this under GNOME shell on Ubuntu. Run jest --notify or jest --watch --notify and observe that the raised notifications are not added to the notification area.

Judging by the use of the existing usage of the actions argument to require('node-notifier').notify, it is safe to pass this argument on all platforms, but I have not tested it.

Under GNOME Shell, using `--notify` (especially with `--watch`) floods the notification UI with unnecessary persistent copies of each notification that is raised. See jestjs#8773.

This change uses [the `notify-send` `hint` option](https://www.npmjs.com/package/node-notifier#usage-notifysend) [`int:transient:1`](https://askubuntu.com/a/1185741) to make the notification transient.
@facebook-github-bot
Copy link
Contributor

Hi @BudgieInWA!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@SimenB
Copy link
Member

SimenB commented Aug 13, 2021

Thanks for the PR!

@mikaelbr does this look correct?

@SimenB
Copy link
Member

SimenB commented Feb 24, 2022

@mikaelbr would love a confirmation 🙏

@mikaelbr
Copy link
Contributor

This seems reasonable to me! Haven't been able to test it out on a UNIX box my self now (no immediate access), but from docs and examples, this makes sense.

@SimenB
Copy link
Member

SimenB commented Feb 25, 2022

Great, thanks @mikaelbr!

Copy link
Member

@SimenB SimenB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@SimenB SimenB merged commit ce9f711 into jestjs:main Feb 25, 2022
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2022
@BudgieInWA BudgieInWA deleted the transient-notifications branch March 28, 2022 07:48
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid watch-notification flood in NotifySend
4 participants