-
-
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
[Plan] Version 6 #1279
Comments
Please, drop faraday. As utility library you shouldn't set any gem your client may be using. Right now I have to "upgrade" my farady to migrate from |
@dlibanori the version requirement on |
This issue 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 🥀 |
Update Faraday to version 2? |
@AlexWayfer Faraday is no longer the SDK's dependency after version 5. |
Sorry, my bad, there left other dependencies after 4→5 update. |
Hi, any dates on when |
Looks like this was scheduled for removal in |
async
-async
option will be dropped. #1522linecache
- I guess no one is using this. if you do, please let me know your use caseexclude_loggers
- this only works withsentry_logger
breadcrumb logger. given that probably not many people use the logger, there should be even fewer (or no) people use this option.Event#to_hash
only returns a string key hash.#to_json_compatible
. But#to_hash
returns a symbol key hash. So it can be confusing to users when dealing with events in callbacks.hub
argument fromTransaction#finish
attempt_threshold
- Only start reporting after thenth
retry failed - The number of attempts before notifications will be sent. #1632reportable_retries
- Only report a number of times for retry failures - Suppress notifications on Sidekiq retries #1570(feel free to add your feedback/request)
The text was updated successfully, but these errors were encountered: