You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Revert to collectList approach with proper byte limiting for structured messages
The streaming approach had issues with buffer consumption. Reverted to collecting
buffers first but with proper byte limiting (560 bytes default) to ensure at least
one segment completes before interruption. This properly tests smart retry from
segment boundaries.
Co-authored-by: gunjansingh-msft <[email protected]>
Copy file name to clipboardExpand all lines: sdk/storage/azure-storage-common/src/test-shared/java/com/azure/storage/common/test/shared/policy/MockPartialResponsePolicy.java
+48-44Lines changed: 48 additions & 44 deletions
Original file line number
Diff line number
Diff line change
@@ -68,51 +68,55 @@ public Mono<HttpResponse> process(HttpPipelineCallContext context, HttpPipelineN
68
68
returnMono.just(response);
69
69
} else {
70
70
this.tries -= 1;
71
-
// Simulate partial response by limiting the amount of data returned from the stream
72
-
// before throwing an IOException to simulate a network interruption.
73
-
// This tests smart retry behavior where downloads should resume from the last
74
-
// complete segment boundary after each interruption.
0 commit comments