Skip to content

Conversation

kapyaar
Copy link
Contributor

@kapyaar kapyaar commented Jul 11, 2025

if (!Update.begin(SPIFFS.totalBytes(), U_SPIFFS)) {

throws an error "Update error: Bad Size Given". Changing to

if (!Update.begin(UPDATE_SIZE_UNKNOWN, U_SPIFFS)) {

fixes #9967. Submitting a PR as per #9967 (comment)

 if (!Update.begin(SPIFFS.totalBytes(), U_SPIFFS)) { 

throws an error "Update error: Bad Size Given". Changing to 

if (!Update.begin(UPDATE_SIZE_UNKNOWN, U_SPIFFS)) {

fixes espressif#9967
@kapyaar kapyaar requested a review from a team as a code owner July 11, 2025 17:01
@CLAassistant
Copy link

CLAassistant commented Jul 11, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

github-actions bot commented Jul 11, 2025

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message "Update HTTPUpdateServer.h":
    • summary looks empty
    • type/action looks empty
  • the commit message "fix(HTTPUpdateServer): Remove SPIFFS.h include":
    • scope/component should be lowercase without whitespace, allowed special characters are _ / . , * - .

Please fix these commit messages - here are some basic tips:

  • follow Conventional Commits style
  • correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue
  • allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test
  • sufficiently descriptive message summary should be between 10 to 72 characters and start with upper case letter
  • avoid Jira references in commit messages (unavailable/irrelevant for our customers)

TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

👋 Hello kapyaar, we appreciate your contribution to this project!


📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against b977457

@Jason2866
Copy link
Collaborator

Jason2866 commented Jul 13, 2025

@me-no-dev is it planned to replace the dead horse spiffs with LittleFS in HTTPUpdateServer?

@me-no-dev
Copy link
Member

Actually here the size of the FS partition should be read and used. Code can be abstracted to flash any FS type, instead of just SPIFFS

@kapyaar
Copy link
Contributor Author

kapyaar commented Jul 14, 2025

If there is a better approach to handle this, Please update or let me know, I can do another PR. One way or the other, It would be great to get this fixed, as at this point, with each release (for backward compatibility), a manual update of this file is the only way out.

@me-no-dev me-no-dev added the Status: Pending Merge Pull Request is ready to be merged label Sep 16, 2025
Copy link
Contributor

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

MemoryFLASH [bytes]FLASH [%]RAM [bytes]RAM [%]
TargetDECINCDECINCDECINCDECINC
ESP32C5💚 -9K0💚 -0.850.00💚 -320💚 -0.060.00
ESP32P4💚 -9K0💚 -1.020.00💚 -160💚 -0.050.00
ESP32S3💚 -6K0💚 -0.670.00💚 -320💚 -0.070.00
ESP32S2💚 -7K0💚 -0.720.00💚 -320💚 -0.070.00
ESP32C3💚 -9K0💚 -0.900.00💚 -320💚 -0.080.00
ESP32C6💚 -9K0💚 -0.890.00💚 -240💚 -0.050.00
ESP32💚 -6K0💚 -0.650.00💚 -240💚 -0.050.00
Click to expand the detailed deltas report [usage change in BYTES]
TargetESP32C5ESP32P4ESP32S3ESP32S2ESP32C3ESP32C6ESP32
ExampleFLASHRAMFLASHRAMFLASHRAMFLASHRAMFLASHRAMFLASHRAMFLASHRAM
libraries/HTTPUpdateServer/examples/WebUpdater💚 -9K💚 -32💚 -9K💚 -16💚 -6K💚 -32💚 -7K💚 -32💚 -9K💚 -32💚 -9K💚 -24💚 -6K💚 -24

@me-no-dev me-no-dev merged commit 54154c7 into espressif:master Sep 16, 2025
38 checks passed
@me-no-dev
Copy link
Member

Sorry for the delay! Will be part of 3.3.1 tomorrrow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Merge Pull Request is ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

httpupdateserver filesystem update "Update error: Bad Size Given" for 8MB version of ESP32
4 participants