Skip to content

pyrefly report nondeterministic JSON order #3639

Closed

Description

@jorenham

Running pyrefly[ coverage] report twice (almost always) results in different order. It's not the end of the world, but it's annoying when manually inspecting the output (e.g. when debugging), and requires an additional processing step when displaying the results on the typestats dashboard.

Activity

  1. jorenham commented on Jun 2, 2026

    @jorenham
    CollaboratorAuthor

    FYI, I'm planning to work on this one (as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions