Skip to content

supabase's error is not retried #2287

@Xuanwo

Description

@Xuanwo
Context:
    response: Parts { status: 504, version: HTTP/2.0, headers: {"date": "Mon, 22 May 2023 15:16:08 GMT", "content-type": "text/html", "content-length": "132", "cf-ray": "7cb6034b794e0a0f-IAD", "access-control-allow-origin": "*", "strict-transport-security": "max-age=2592000; includeSubDomains", "cf-cache-status": "DYNAMIC", "sb-gateway-mode": "direct", "sb-gateway-version": "1", "server": "cloudflare", "alt-svc": "h3=\":443\"; ma=86400, h3-29=\":443\"; ma=86400"} }
    service: supabase
    path: a111a626-dbab-48ad-bc51-964195e47c36/

    at core/src/layers/logging.rs:244

thread 'services_supabase::write_test_read_with_dir_path' panicked at 'write must succeed: Unexpected (persistent) at create_dir => <html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
</body>
</html>

This error should be retryable but it's not. We should check the error implementations.

Originally posted by @Xuanwo in #2279 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions