Skip to content
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

\Sentry\init(['dns' => '']) triggers HttpTransport::delaySendingUntilShutdown deprecated error #884

Closed
Kleingeld opened this issue Sep 23, 2019 · 5 comments · Fixed by #885

Comments

@Kleingeld
Copy link

After upgrading to Sentry 2.2.0 the application started sending this error:

Delaying the sending of the events using the "Sentry\Transport\HttpTransport" class is deprecated since version 2.2 and will not work in 3.0.

Only problem is the transport is initialized by Sentry itself after calling:
\Sentry\init(['dsn' => '_PUBLIC_DSN_']);

The default of delaySendingUntilShutdown = true, but I see no way to overwrite it from within sentry::init.

So sentry is triggering itself to send errors about this to sentry.io.

Any idea how to fix the sentry::init to stop this issue, for now i commented out the

@trigger_error(sprintf('Delaying the sending of the events using the...

line to stop the application from floading sentry.io

@Kleingeld
Copy link
Author

Kleingeld commented Sep 23, 2019

Changes to come to this error are in this commit: 5dfc0ed

@PVGrad
Copy link

PVGrad commented Sep 23, 2019

For now you can only freeze the version in composer.json
"sentry/sentry": "2.1.3"
And wait for a fix then

@HazAT
Copy link
Member

HazAT commented Sep 23, 2019

We are already working on the fix, 2.2.1 is minutes away, we will update the issue.

@Kleingeld
Copy link
Author

@HazAT thank you!

@HazAT
Copy link
Member

HazAT commented Sep 23, 2019

2.2.1 has been released containing the fix, sorry for the inconvenience and thanks for reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants