esp-idf icon indicating copy to clipboard operation
esp-idf copied to clipboard

Make esp_mbedtls_server_session_create async compatible (IDFGH-13606)

Open thetek42 opened this issue 1 year ago • 2 comments

This makes esp_mbedtls_server_session_create async-friendly by splitting up the function into two parts. This change was originally proposed here in order to make an asynchronous TLS server possible: https://github.com/esp-rs/esp-idf-svc/pull/368#discussion_r1512376482

thetek42 avatar Sep 03 '24 11:09 thetek42

CLA assistant check
All committers have signed the CLA.

CLAassistant avatar Sep 03 '24 11:09 CLAassistant

Messages
:book: 🎉 Good Job! All checks are passing!

👋 Hello thetek42, 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.
- 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 via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

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 synchronize it into our internal git repository.
4. In the internal git repository 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.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by :no_entry_sign: dangerJS against 083b39640524dc96d5bccffc396667f5f3a616f3

github-actions[bot] avatar Sep 03 '24 11:09 github-actions[bot]

@AdityaHPatwardhan I updated the function names and also ported them to both WolfSSL and esp-tls.

thetek42 avatar Oct 07 '24 10:10 thetek42

@thetek42 Actually, if it is fine with you, I can take over the PR. Please squash your changes in one commit. I will update my changes on a separate commit so your contribution would still be visible.

AdityaHPatwardhan avatar Oct 16 '24 14:10 AdityaHPatwardhan

PR updated. Thanks!

thetek42 avatar Oct 16 '24 15:10 thetek42

sha=083b39640524dc96d5bccffc396667f5f3a616f3

AdityaHPatwardhan avatar Oct 16 '24 17:10 AdityaHPatwardhan