Skip to content

Harden Kalshi contract against transient runner 403 responses #32

Description

@stefan-jansen

A public provider contract on commit a835a55 failed because Kalshi returned an HTML 403 response to one GitHub-hosted runner:

https://github.com/ml4t/data/actions/runs/31269497728

The same Kalshi contract passed locally immediately afterward, and the exact workflow rerun passed. This indicates intermittent CDN or runner-IP rejection rather than a deterministic provider or library failure.

Follow-up:

  • determine whether Kalshi documents restrictions affecting GitHub-hosted runner addresses
  • distinguish an HTML edge-layer 403 from a structured API authorization failure
  • if appropriate, add one bounded retry for this unauthenticated public contract without masking persistent provider failures

Severity: low. The exact-commit release contract has successful evidence.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions