Open jpreynat opened 6 years ago
:exclamation: No coverage uploaded for pull request base (
master@9357749
). Click here to learn what that means. The diff coverage isn/a
.
@@ Coverage Diff @@
## master #30 +/- ##
=======================================
Coverage ? 100%
=======================================
Files ? 1
Lines ? 25
Branches ? 0
=======================================
Hits ? 25
Misses ? 0
Partials ? 0
Impacted Files | Coverage Δ | |
---|---|---|
lib/index.js | 100% <ø> (ø) |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 9357749...289e8b9. Read the comment docs.
https://github.com/getsentry/raven-js/releases/tag/3.24.2 was released - let's get that one?
Looks like the failure in CircleCI was related to rate-limited use of saucelabs for browser testing:
Uh oh, you've run out of minutes!
Please visit https://saucelabs.com/pricing to purchase a subscription.
Can someone with auth trigger a rebuild? Would love to see this get pushed through. Many older .NET projects can't use the current v3.17.0
Sentry integration version due to 'use strict'
causing FireFox and IE to throw exceptions because many old .NET libraries use arguments.callee
.
Any update on getting the latest SDK from Sentry into Segment?
This PR was made mainly to take advantage of getsentry/raven-js#1253 when parsing non-Error like Objects that is a big improvement for errors debugging in Sentry.