Merged
Conversation
…with X-OBP-Version-Served header
…— REST/SOAP-only endpoints never touch the pool
long_endpoint_timeout prop (default 55 s, same as v6)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unmigrated /obp/v7.0.0/... paths that no http4s handler claims are transparently rewritten to /obp/v6.0.0/... by the Lift bridge. The response carries
X-OBP-Version-Served: v6.0.0 so load testers can observe when fallback fired. Fallback version is configurable via http4s.v700.fallback.version prop.
withBusinessDBTransaction no longer borrows a Hikari connection upfront. Instead it installs a Deferred-backed once-only acquisition IO into
RequestScopeConnection.requestLazyAcquire. The connection is borrowed only on the first actual DB call (fromFuture → ensureProxy → acquireOnce).
REST/SOAP-only endpoints never touch the pool.
ResourceDocMiddleware wraps every endpoint in IO.timeoutTo(endpointTimeoutMs.millis, ...). The timeout value comes from
Constant.longEndpointTimeoutInMillis, which is the same long_endpoint_timeout prop that drives FutureUtil.defaultTimeout in v6 — one setting controls
both stacks. Default is 55 s. A timed-out request returns 504 with a JSON error body.