Skip to content

Conversation

@hcldan
Copy link
Contributor

@hcldan hcldan commented May 23, 2025

Closes #2942

JonathanMcCormickJr and others added 7 commits March 16, 2025 12:29
- Update `gen_certs.sh`
  - Generate client cert as well by default
  - Set expiration to 10 years to match other certs
  - Set subject to match expected values in testbench test
- Update testbench `mtls` to ignore key hash value, and only check issuer
  and subject.
commit 9fcc529
Author: Cormac Relf <[email protected]>
Date:   Mon Apr 14 17:36:07 2025 +1000

    Improve db_pools init: do not crash if DB unavailable during startup

    ## Why?

    When using `Pool::connect[_with]`, sqlx attempts to connect to the given
    database immediately, and the fairing will fail if there are any
    problems in that attempt (beyond obvious configuration problems that are
    found before hitting the network), e.g.:

    - the database is unavailable; or
    - the username/password is incorrect; or
    - the ssl configuration is invalid; or
    - any other connection issue.

    There are a few pros and cons to this approach:

    Pros:

    - In development, configuration errors are surfaced slightly faster

    Cons:

    - Databases are expected to be unavailable sometimes. It does not
      normally crash a server if one becomes unavailable after startup,
      so why should it prevent a server from starting at all? See
      [deadpool's justification]{https://docs.rs/deadpool} for not crashing.
    - In production/testing, slower to debug configuration or networking
      errors as your edit-test loop now involves restarting an application
      rather than refreshing a page or trying a request again.
    - Causes database or configuration issues to appear as "failed
      deployments" in standard deployment scenarios.
    - Introduces hard ordering constraints on operator actions during
      database recovery, requiring reboots to follow a functioning database
      or applications not to be restarted at certain times

    ## Effect of change

    The sqlx backend now behaves like the deadpool backend: no connection
    issues are surfaced during startup. You will not see them until you
    attempt to get a connection from the pool. That means rocket will launch
    and you can find problems like these in smoke tests.
commit 74f884d
Author: Dan Fego <[email protected]>
Date:   Sat Mar 29 00:11:16 2025 -0400

    Added test for new config values

commit 0212e88
Author: Dan Fego <[email protected]>
Date:   Sat Mar 29 00:03:01 2025 -0400

    Fix 'Config' made defaults consistent with docs
commit 599d5ee
Author: Paul Adenot <[email protected]>
Date:   Wed Jan 1 18:21:18 2025 +0100

    Fix Dockerfile example in "Deploying" chapter

    This now matches the layout of a typical project, instead of erroring out.
- Based on rwf2#2930
- Populates value from hyper version
- Adds method to override version for local requests
Rust now warns when it determines that an elided lifetime has a name. This
commit updates all of these cases to use the named lifetime instead.
@hcldan hcldan changed the title expose the sni server name. expose the sni, if any. May 23, 2025
@hcldan hcldan force-pushed the sni branch 6 times, most recently from d9ed0b9 to 90935db Compare May 23, 2025 20:14
@@ -0,0 +1,8 @@
root = true
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not strictly related to the change, but I ran into some annoying check_style issues and it wasn't immediately clear how to properly run the checks on my machine.

This should help with general file formatting, trailing whitespace, and line endings at the end of files for those who use an editorconfig editor plugin. I highly recommend it!

@hcldan
Copy link
Contributor Author

hcldan commented Jun 3, 2025

@the10thWiz Could you please review this?

@hcldan
Copy link
Contributor Author

hcldan commented Nov 4, 2025

@SergioBenitez would you like any other changes in order to get this into master?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

HTTP spec compliance with TLS handshake

6 participants