Skip to content

Conversation

kuhe
Copy link
Contributor

@kuhe kuhe commented Sep 29, 2025

Issue

#7382

Description

In the reported issue, a pseudo-file reporting an incorrect file length conflicts with our validation. Allowing user input for the byte count would work around this edge case.

Testing

Added unit tests

Checklist

  • If the PR is a feature, add integration tests (*.integ.spec.ts).
  • If you wrote E2E tests, are they resilient to concurrent I/O?
  • If adding new public functions, did you add the @public tag and enable doc generation on the package?
  • use start and end properties if available, like util-body-length-node
  • differentiate whether totalBytes was given by caller or automatically

@kuhe kuhe requested a review from a team as a code owner September 29, 2025 16:30
@kuhe kuhe marked this pull request as draft September 29, 2025 17:58
@kuhe kuhe marked this pull request as ready for review September 29, 2025 20:17
@kuhe kuhe merged commit 45d5730 into main Sep 29, 2025
7 checks passed
@kuhe kuhe deleted the fix/lib-storage branch September 29, 2025 21:36
smilkuri pushed a commit that referenced this pull request Oct 2, 2025
…lable (#7385)

* fix(lib-storage): use input parameter object size information if available

# Conflicts:
#	lib/lib-storage/src/Upload.ts

* fix(lib-storage): use only ContentLength

* fix: import ordering

* fix: byteLengthSource

* fix: add error message
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants