Skip to content

/info/ endpoints rely on implicit transactions #768

Closed
@pjenvey

Description

These endpoints lack a collection so transaction_http doesn't call locking methods for them, leaving the implicit transaction code to create their transactions in a blocking manner.

We can't add a quick fix of begin(false).await? to their handlers to solve this as the precondition check's extract_resource is now called from inside transaction_http, which implicitly starts the transaction.

Probably the easiest alternative is to create a read_transaction_http and write_transaction_http. For the case of no collection these would call begin(...) w/ either false or true.

Somewhat related to #581

Metadata

Assignees

No one assigned

    Labels

    3Estimate - m - This is a small change, but there's some uncertainty.bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions