Skip to content

Check _cleanupTimer is not null when disposing (backport fix/4818 to 6.x) #5530

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

Merged
merged 1 commit into from
Apr 8, 2021

Conversation

bdchris
Copy link

@bdchris bdchris commented Apr 7, 2021

Backporting fix for #4818
This commit checks that _cleanupTimer is not null when disposing, which it may be if no requests have been made.

Fixes #5529

Backporting fix for elastic#4818
This commit checks that _cleanupTimer is not null when disposing, which it may be if no requests have been made.

Fixes elastic#5529
@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@bdchris bdchris changed the title Check _cleanupTimer is not null when disposing Check _cleanupTimer is not null when disposing (backport fix/4818 to 6.x) Apr 7, 2021
@bdchris bdchris marked this pull request as draft April 7, 2021 19:59
@bdchris bdchris marked this pull request as ready for review April 7, 2021 20:01
Copy link
Contributor

@stevejgordon stevejgordon left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@stevejgordon
Copy link
Contributor

Thanks for contributing @bdchris. Some of the tests timed out but the key ones have passed. I'll merge this in and run the tests again locally.

@stevejgordon stevejgordon merged commit c72b3de into elastic:6.x Apr 8, 2021
@bdchris
Copy link
Author

bdchris commented Apr 8, 2021

@stevejgordon is there a page or other media that shows schedule for v6.8.8 ?

@stevejgordon
Copy link
Contributor

stevejgordon commented Apr 8, 2021

@bdchris - There's no specific schedule for patch releases. My plan right now is to target the next release within the next 8-10 business days.

@bdchris
Copy link
Author

bdchris commented Apr 8, 2021

sounds good @stevejgordon - thanks much!

@stevejgordon
Copy link
Contributor

@bdchris I've released 6.8.8 of the client this morning which includes your bug fix.

cdonnellytx pushed a commit to cdonnellytx/elasticsearch-net that referenced this pull request Jun 14, 2021
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.

3 participants