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

Don't ignore nil clients #65

Merged
merged 1 commit into from
Apr 9, 2019
Merged

Don't ignore nil clients #65

merged 1 commit into from
Apr 9, 2019

Conversation

Aceeri
Copy link
Contributor

@Aceeri Aceeri commented Aug 25, 2018

Not panicking is fine, but visibility into what the problem is would be nice.

Copy link
Member

@arbll arbll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks for the contribution @Aceeri!

@arbll arbll merged commit 5d622b6 into DataDog:master Apr 9, 2019
@truthbk truthbk added this to the 2.2 milestone Apr 11, 2019
@asf-stripe
Copy link
Contributor

Hrm, this broke some of our tests - they expected a nil error when sending to a nil statsd client (that was the only way we had to work around #88 so far); I think this would be fine if we could get a singleton error value (that our tests can assert for) rather than a newly-allocated error.

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 this pull request may close these issues.

4 participants