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(browser): Set :
as a part of gecko protocol regex group.
#4153
Conversation
size-limit report
|
We can cut a beta and test this - no need to enforce that it needs to be part of the next immediate release. Also, we only tested latest firefox back when we were using BrowserStack regularly, I think as long as we can validate with playwright that this doesn't break anything, we should be good! sentry-javascript/packages/browser/test/integration/browsers.js Lines 123 to 130 in 20d5fa7
|
I'm going to set this as blocked, let's get the e2e tests in first, and then try to merge this in. |
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
@onurtemizkan can we rebase and add an integration test for this now? |
fd20fd0
to
2490499
Compare
packages/integration-tests/suites/stacktraces/protocol_containing_fn_identifiers/test.ts
Outdated
Show resolved
Hide resolved
3c1f04d
to
537da47
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.
Looks pretty good! My feedback is mostly just making sure things are clearer for the reader.
packages/integration-tests/suites/stacktraces/protocol_containing_fn_identifiers/test.ts
Outdated
Show resolved
Hide resolved
@onurtemizkan is it possible to re-create this PR when you get some time? The stacktrace parsing logic has moved, so probably not worth it to rebase the PR. |
537da47
to
3220b92
Compare
size-limit report 📦
|
f68450d
to
b17ad68
Compare
@onurtemizkan - just so we can finally close the loop on this. Mind rebasing this for a final time? Let's get it merged in! |
49cfc13
to
b17ad68
Compare
b17ad68
to
d2e0cc4
Compare
@onurtemizkan mind rebasing this PR? We had to fix some NextJS test failures with #5484 |
^ Bump to rebase this, let's get it merged in! |
…ing_fn_identifiers/test.ts Co-authored-by: Katie Byers <lobsterkatie@gmail.com>
d2e0cc4
to
61ea3f6
Compare
On it! |
d8e8e98
to
61ea3f6
Compare
Fixes: #4138
The original issue about
file
keyword also happens for everything in that group, such ashttp
,blob
and so on. And the problem originates from :.*
between that group and:
. It seems that:
follows those keywords without anything in between, as far as I have seen from the tests.Removing that from the regex solved the issue without breaking any tests other than
safari-extension
andsafari-web-extension
, which are special-cased here, adding those two to the matching group also solved the issue of an extra:
coming from there.