Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fix(hash): add selective build option for Hash, WebServer dependency#11854

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
lucasssvaz merged 2 commits intoespressif:masterfromfill1890:master
Sep 20, 2025

Conversation

@fill1890
Copy link
Contributor

The Hash library introduced in version v3.3.1 doesn't have an option to be included in a selective build, and in a selective build it defaults to not included. As the WebServer library depends on the Hash library, selective builds that include WebServer break as the dependency is not satisfied.

This PR adds an appropriate option to Kconfig, and adds the WebServer → Hash dependency.

Tested on a selective build using the Arduino core as an ESP-IDF component on an ESP32-S3. As far as I know the aren't any open issues for this.

@CLAassistant
Copy link

CLAassistant commentedSep 18, 2025
edited
Loading

CLA assistant check
All committers have signed the CLA.

@github-actions
Copy link
Contributor

github-actionsbot commentedSep 18, 2025
edited
Loading

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message"Add missing Hash selection":
    • summary looks empty
    • type/action looks empty

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

  • followConventional Commits style
  • correct format of commit message should be:<type/action>(<scope/component>): <summary>, for examplefix(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 theConventional Precommit Linter).

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


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

🖊️ Please also make sure you haveread and signed theContributor License Agreement for this project.

Click to see more instructions ...


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

DangerJS is triggered with eachpush 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 isnot 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 manuallyretry these Danger checks, please navigate to theActions 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 against85bd436

@me-no-dev
Copy link
Member

@lucasssvaz PTAL

@lucasssvazlucasssvaz added Area: LibrariesIssue is related to Library support. Status: Pending MergePull Request is ready to be merged labelsSep 18, 2025
@lucasssvazlucasssvaz merged commit393834b intoespressif:masterSep 20, 2025
34 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@lucasssvazlucasssvazlucasssvaz approved these changes

@SuGliderSuGliderAwaiting requested review from SuGliderSuGlider is a code owner

@me-no-devme-no-devAwaiting requested review from me-no-devme-no-dev is a code owner

Assignees

No one assigned

Labels

Area: LibrariesIssue is related to Library support.Status: Pending MergePull Request is ready to be merged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@fill1890@CLAassistant@me-no-dev@lucasssvaz

[8]ページ先頭

©2009-2025 Movatter.jp