-
-
Notifications
You must be signed in to change notification settings - Fork 494
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
WIP: 3.0. #613
Closed
Closed
WIP: 3.0. #613
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nateberkopec
force-pushed
the
binding-of-caller
branch
from
December 16, 2016 19:01
3a03add
to
b0b2e02
Compare
nateberkopec
force-pushed
the
binding-of-caller
branch
from
January 3, 2017 21:51
b0b2e02
to
53c5bca
Compare
nateberkopec
changed the title
WIP: 3.0. Local variables, performance, refactor.
WIP: 3.0.
Mar 22, 2017
Ultimately I decided not to include local variable capture - it's too unstable and buggy and could never be used in production, so the use case is too limited. |
nateberkopec
force-pushed
the
binding-of-caller
branch
from
March 22, 2017 13:30
53c5bca
to
fa7489b
Compare
Just realized we'll need a 2.x series release where |
nateberkopec
force-pushed
the
binding-of-caller
branch
from
April 26, 2017 19:32
fa7489b
to
55494dd
Compare
nateberkopec
force-pushed
the
binding-of-caller
branch
from
May 10, 2017 20:41
f7a6f43
to
0fb65bf
Compare
Remove “capture” methods on Raven::Event, which no one should have been using directly anyway because those methods didn’t “capture” anything, only converted strings/exceptions into Events. I’m not going to do a deprecation cycle for this because no one should have been using these aliases anyway, and they were only used in our tests. I do recognize that from_exception is now changed so that it no longer checks Raven::Error or excluded exception (that’s now in capture_allowed?), so this will trigger a major release.
+ Config can be passed variables during init + Spec -> Minitest + Bad encoding raises ArgumentError + ResolveHostname - fix bug where FQDN was not resolved + Note bug where module exclusion doesn’t work properly
nateberkopec
force-pushed
the
binding-of-caller
branch
2 times, most recently
from
May 10, 2017 21:09
24c65cc
to
04bd6ed
Compare
This was referenced Jun 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
transport_failure_callback
gives no information on failure reason #661Raven.configuration
global exists.