Skip to content

provision_merchant swallows the underlying error (no logging) #125

Description

@Darkdruce

Summary

On DB failure the handler maps the error to a generic 500 via map_err(|_| ...), discarding the cause, unlike the AppError path which logs.

Location

  • src/api/mod.rs:145-152 vs src/api/payments.rs:45-54 (From<anyhow::Error> logs)

Details & impact

Provisioning failures are undiagnosable from logs.

Suggested fix

Log the error (reuse AppError) before returning 500.

Acceptance criteria

  • Provisioning failures are logged with context.

Metadata

Metadata

Assignees

No one assigned

    Labels

    GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26apiHTTP API surface and handlersbugSomething isn't workingobservability

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions