Skip to content

Conversation

@JoshuaXOng
Copy link
Contributor

@JoshuaXOng JoshuaXOng commented Sep 24, 2024

Following up on, #42395. Have just added the SSL/TLS flags to the debug control flow. fastapi cli does not have SSL flags, but it is a thin wrapper around uvicorn.run (https://github.com/fastapi/fastapi-cli/blob/main/src/fastapi_cli/cli.py#L92)

Have created the Appendable test utility to declare files/filepaths in pytest.mark.parametrize that are to be relative tmp_path. Lmk if it is a bit weird / not good. Or whether it should be separated out into a different PR.

There are some CI failures, not too sure atm if it is because of uvicorn[standard]>=0.15.0 or flakiness. Between fa4239a and ba2fec5 same checks did not fail (barring mypy). Other PRs that trigger the same checks seem to sometimes error too (though error message is a bit different). Atm, the only failing CI check looks to be resolved as a part of #42500.
fastapi[standard]>=0.112.2 itself requires uvicorn[standard]>=0.15.0, wondering though whether since uvicorn is no longer a transitive dependency the tests fail.

related: #42359


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@JoshuaXOng JoshuaXOng closed this Sep 24, 2024
@JoshuaXOng JoshuaXOng reopened this Sep 25, 2024
@JoshuaXOng JoshuaXOng force-pushed the main branch 4 times, most recently from a052d0e to c41e1c9 Compare September 26, 2024 06:22
@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Nov 17, 2024
@pierrejeambrun
Copy link
Member

up

@pierrejeambrun pierrejeambrun removed the stale Stale PRs per the .github/workflows/stale.yml policy file label Nov 18, 2024
@github-actions
Copy link

github-actions bot commented Jan 3, 2025

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Jan 3, 2025
@pierrejeambrun
Copy link
Member

up

@pierrejeambrun pierrejeambrun removed the stale Stale PRs per the .github/workflows/stale.yml policy file label Jan 6, 2025
@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Feb 21, 2025
@github-actions github-actions bot closed this Feb 26, 2025
@pierrejeambrun
Copy link
Member

I don't think that's needed anymore. (ssl/tls on debug mode).

We can always come back to this if people ask for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:CLI stale Stale PRs per the .github/workflows/stale.yml policy file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants