Skip to content

[DO NOT MERGE] Issue #288 : Port RntbdRequestTimer memory leak fix from V4#289

Closed
David-Noble-at-work wants to merge 37 commits into
masterfrom
issue/#288/port-from-v4
Closed

[DO NOT MERGE] Issue #288 : Port RntbdRequestTimer memory leak fix from V4#289
David-Noble-at-work wants to merge 37 commits into
masterfrom
issue/#288/port-from-v4

Conversation

@David-Noble-at-work

@David-Noble-at-work David-Noble-at-work commented Nov 9, 2019

Copy link
Copy Markdown

PLEASE DO NOT REVIEW UNTIL PR #287 IS COMPLETE

See #288 and Azure/azure-sdk-for-java#6251

David.Noble@microsoft.com added 30 commits October 9, 2019 14:38
… caused the status code to be set incorrectly
… and added DocumentClientExceptionTest.statusCodeIsCorrect

The latter resulted in moving DocuemntClientExceptionTest from commons to direct-impl. Without the move commons would need to take a dependency on direct-impl which seems undesirable.
…into danoble/issue-263/retry-not-happening
@David-Noble-at-work David-Noble-at-work changed the title DRAFT: Issue #288: Port RntbdRequestTimer memory leak fix from V4 [DO NOT MERGE] Issue #288: Port RntbdRequestTimer memory leak fix from V4 Dec 13, 2019
@David-Noble-at-work David-Noble-at-work changed the title [DO NOT MERGE] Issue #288: Port RntbdRequestTimer memory leak fix from V4 [DO NOT MERGE] Issue #288 : Port RntbdRequestTimer memory leak fix from V4 Dec 13, 2019
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.

1 participant