Add known issue for Java SDK #2604
Conversation
docs-ref-services/latest/storage.md
Outdated
|
|
||
| | Client library | Versions impacted | Minimum safe version | Recommended action | | ||
| | --- | --- | --- | --- | | ||
| | Azure File Share | 12.15.0 to 12.25.0 | 12.26.0-beta.1 | [Update to latest version or minimum 12.26.0-beta.1](https://mvnrepository.com/artifact/com.azure/azure-storage-file-share) | |
There was a problem hiding this comment.
we should call out 12.16.0 as the minimum safe version. We can't realistically expect customers to upgrade to a beta release
There was a problem hiding this comment.
Done. Updated to 12.26.0
There was a problem hiding this comment.
Let's change this to 12.25.1, the release today is a patch release.
There was a problem hiding this comment.
Updated to 12.25.1 - thx for clarifying.
|
Learn Build status updates of commit 454c400:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs-ref-services/latest/storage.md | View (azure-java-stable) | Details |
docs-ref-services/latest/storage.md
- Line 7, Column 13: [Warning: ms-service-subservice-invalid - See documentation]
Invalid value for 'ms.service': 'storage'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
|
Learn Build status updates of commit 45557b4: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
docs-ref-services/latest/storage.md
Outdated
|
|
||
| #### Issue description | ||
|
|
||
| In the **azure-storage-file-share** package, the `ShareFileClient.downloadToFile()` method can write incorrect data to a file when more than 5 retries occur due to partial network responses while streaming data. The maximum number of retries is unintentionally higher (up to a maximum of 15), which can result in writing to incorrect positions in the file when the operation is retried more than 5 times. The data in Storage is still correct. |
There was a problem hiding this comment.
The data in Storage is still correct.
Maybe we should say "This issue does not affect data in the Storage service, only the data being written to the local filesystem."
|
Learn Build status updates of commit 1f9cc51: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
No description provided.