Chore/update sentry #16223
Chore/update sentry #16223
Conversation
| }, | ||
| // If Tor is enabled but not running, don't send the event but put it in a queue. | ||
| // Queue can be inspected in @trezor/suite-desktop/sentry/queue folder. | ||
| shouldSend: () => !(store.getTorSettings().running && torStatus !== TorStatus.Enabled), |
There was a problem hiding this comment.
API change, see documentation.
There was a problem hiding this comment.
Sorry for troubles I didn't expect it could affect desktop and TS won't even complain
| levels: ['error'], | ||
| }), | ||
| new Dedupe(), |
There was a problem hiding this comment.
Enabled by default, see documentation.
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat are wildcard dependencies?Package has a dependency with a floating version range. This can cause issues if the dependency publishes a new major version. Packages should specify properly semver ranges to avoid version conflicts. What is shell access?This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code. Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
|
🚀 Expo preview is ready!
|
komret
force-pushed
the
chore/update-sentry
branch
from
9be74c4 to
5a2adab
Compare
…nd @sentry/electron
komret
force-pushed
the
chore/update-sentry
branch
from
5a2adab to
0a001c8
Compare
Description
Update Sentry to fix the discrepancy between mobile and desktop which resulted in logs not being collected from desktop. Originated here.