This release was yanked by @leostera. Installing it should be treated as unsupported, even though the package page remains available for reference.

riot-fix

v0.0.1

Linting and auto-fix pipeline

Repository Open docs Open in playground

Install

riot add riot-fix

riot.toml

riot-fix = "0.0.1"

Last release: Apr 2, 2026
License: Apache-2.0
Dependencies: 4
Dependents: 3
Installs: 1
Published versions: 1
Owner: @leostera

README Expand

riot-fix

riot-fix is Riot's linting and safe-fix pipeline for OCaml code.

It is built on top of syn:

Ceibo provides exact lossless syntax and spans
Syn.Cst provides typed structure for clean parses
fixme provides the shared rule-authoring surface

Current model

The pipeline is:

parse each file once with syn
keep parse diagnostics separate from lint diagnostics
run enabled rules against the red tree plus optional typed CST
apply only safe, package-owned fixes
report remaining issues in text or JSON

Rules can be built in or provided by workspace packages. Package-provided rules are compiled into a generated fixme-runner under _build, so riot-fix does not spawn one subprocess per rule.

Rule ids

Rules are keyed by rule id:

built-in rules are shown as riot:<id>
package rules keep their package-qualified ids such as std:no-stdlib

The CLI exposes that same surface consistently:

--list-rules lists rules
--list-diagnostics lists the currently loaded diagnostics
--explain RULE_ID explains a rule

Explain text lives with the rule definition, not in a central registry package.

CLI

Typical usage:

# check a path without modifying files
riot run riot -- fix --check packages/syn

# stop early after surfacing a small number of diagnostics
riot run riot -- fix --check --limit 10 packages/syn

# apply safe fixes
riot run riot -- fix --apply packages/riot-fix

# inspect the currently loaded rule and diagnostic surfaces
riot run riot -- fix --list-rules
riot run riot -- fix --list-diagnostics

# explain a rule
riot run riot -- fix --explain riot:snake-case-type-names
riot run riot -- fix --explain std:no-stdlib

Rule authoring

Rules are defined with fixme and run against:

the file path
the optional typed CST for clean parses
the Ceibo red tree for exact source traversal

At a high level:

let make () =
  Rule.make
    ~id:"snake-case-type-names"
    ~description:"Type names should use snake_case instead of camelCase"
    ~explain:"Prefer snake_case type names so declarations read consistently."
    ~run:(fun context red_root ->
      ignore context;
      ignore red_root;
      [])
    ()

The important constraints are:

keep rules small and specific
prefer typed Syn.Cst structure when the grammar has already been lifted
push structural parser assumptions down into syn instead of re-encoding grammar in every rule
only emit fixes that are clearly safe

Configuration

Rules are enabled and disabled through riot.toml. Built-in Riot rules are enabled by default unless they are explicitly disabled in config.

Package-provided rules keep their package-qualified ids, for example:

riot:snake-case-type-names
riot:descriptive-type-variables
std:no-stdlib

Validation

The usual checks are:

timeout 30 riot build riot-fix
timeout 180 riot test riot-fix:runner_tests
riot run riot -- fix --list-rules
riot run riot -- fix --list-diagnostics
riot run riot -- fix --check --limit 10 packages/riot-fix

README

riot-fix

riot-fix is Riot's linting and safe-fix pipeline for OCaml code.

It is built on top of syn:

Ceibo provides exact lossless syntax and spans
Syn.Cst provides typed structure for clean parses
fixme provides the shared rule-authoring surface

Current model

The pipeline is:

parse each file once with syn
keep parse diagnostics separate from lint diagnostics
run enabled rules against the red tree plus optional typed CST
apply only safe, package-owned fixes
report remaining issues in text or JSON

Rules can be built in or provided by workspace packages. Package-provided rules are compiled into a generated fixme-runner under _build, so riot-fix does not spawn one subprocess per rule.

Rule ids

Rules are keyed by rule id:

built-in rules are shown as riot:<id>
package rules keep their package-qualified ids such as std:no-stdlib

The CLI exposes that same surface consistently:

--list-rules lists rules
--list-diagnostics lists the currently loaded diagnostics
--explain RULE_ID explains a rule

Explain text lives with the rule definition, not in a central registry package.

CLI

Typical usage:

# check a path without modifying files
riot run riot -- fix --check packages/syn

# stop early after surfacing a small number of diagnostics
riot run riot -- fix --check --limit 10 packages/syn

# apply safe fixes
riot run riot -- fix --apply packages/riot-fix

# inspect the currently loaded rule and diagnostic surfaces
riot run riot -- fix --list-rules
riot run riot -- fix --list-diagnostics

# explain a rule
riot run riot -- fix --explain riot:snake-case-type-names
riot run riot -- fix --explain std:no-stdlib

Rule authoring

Rules are defined with fixme and run against:

the file path
the optional typed CST for clean parses
the Ceibo red tree for exact source traversal

At a high level:

let make () =
  Rule.make
    ~id:"snake-case-type-names"
    ~description:"Type names should use snake_case instead of camelCase"
    ~explain:"Prefer snake_case type names so declarations read consistently."
    ~run:(fun context red_root ->
      ignore context;
      ignore red_root;
      [])
    ()

The important constraints are:

keep rules small and specific
prefer typed Syn.Cst structure when the grammar has already been lifted
push structural parser assumptions down into syn instead of re-encoding grammar in every rule
only emit fixes that are clearly safe

Configuration

Rules are enabled and disabled through riot.toml. Built-in Riot rules are enabled by default unless they are explicitly disabled in config.

Package-provided rules keep their package-qualified ids, for example:

riot:snake-case-type-names
riot:descriptive-type-variables
std:no-stdlib

Validation

The usual checks are:

timeout 30 riot build riot-fix
timeout 180 riot test riot-fix:runner_tests
riot run riot -- fix --list-rules
riot run riot -- fix --list-diagnostics
riot run riot -- fix --check --limit 10 packages/riot-fix

Installs

Downloads over the last 30 days, stacked by release.

Total installs

Downloads over the last 30 days

v0.0.11

Package status

Submission, indexing, and post-publish processing milestones for this release.

Submitted

Pending

Indexed

Apr 14, 01:59 PM

Searchable

Apr 14, 01:59 PM

Docs ready

Pending

Completed

Pending

Submitted

Pending

Indexed

Apr 14, 01:59 PM

Searchable

Apr 14, 01:59 PM

Docs ready

Pending

Completed

Pending

Dependencies

Dependencies declared for this release.

Show 4 dependencies Expand

std *
syn *
riot-model *
fixme *

std *
syn *
riot-model *
fixme *

Dependents

Packages that currently depend on riot-fix.

Show 3 dependents Expand

Recent activity

Latest publication, indexing, and post-publish pipeline events recorded for this package.

Open full activity

Show 12 recent events Expand

Apr 14, 01:59 PM Indexed

riot-fix 0.0.1 latest 0.0.1 · artifact daf68d45cda3

Details

When: Apr 14, 2026, 01:59:28 PM
Event: Indexed
Package: riot-fix
Version: 0.0.1

Facts

latest 0.0.1 artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "latest": "0.0.1",
  "package_index_key": "index/v1/ri/ot/riot-fix.json",
  "package_index_url": "https://cdn.pkgs.ml/index/v1/ri/ot/riot-fix.json",
  "changed": true
}

Apr 14, 01:59 PM Searchable

riot-fix 0.0.1 latest 0.0.1 · artifact daf68d45cda3

Details

When: Apr 14, 2026, 01:59:28 PM
Event: Searchable
Package: riot-fix
Version: 0.0.1

Facts

latest 0.0.1 artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "latest": "0.0.1",
  "package_index_key": "index/v1/ri/ot/riot-fix.json",
  "package_index_url": "https://cdn.pkgs.ml/index/v1/ri/ot/riot-fix.json",
  "changed": true
}

Apr 14, 01:59 PM

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 14, 2026, 01:59:28 PM
Event
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "yanked_at": "2026-04-14T13:59:28.596Z",
  "yanked_by_github_login": "leostera"
}

Apr 5, 06:58 PM Blocked

riot-fix 0.0.1 attempt 24 · artifact daf68d45cda3

Details

When: Apr 5, 2026, 06:58:14 PM
Event: Blocked
Package: riot-fix
Version: 0.0.1

Facts

attempt 24 artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "blocked",
  "attempt_count": 24,
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 5, 06:58 PM Processing

riot-fix 0.0.1 attempt 24 · artifact daf68d45cda3

Details Hide
When

Apr 5, 2026, 06:58:05 PM

Event

Processing

Package

riot-fix

Version

0.0.1

Facts

attempt 24 artifact daf68d45cda3
Payload
```
{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "processing",
  "attempt_count": 24
}
```

Apr 5, 06:36 PM Requeued

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 5, 2026, 06:36:32 PM
Event: Requeued
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "pending",
  "next_attempt_at": "2026-04-05T18:41:32.906Z",
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 5, 06:36 PM Processing

riot-fix 0.0.1 attempt 23 · artifact daf68d45cda3

Details Hide
When

Apr 5, 2026, 06:36:25 PM

Event

Processing

Package

riot-fix

Version

0.0.1

Facts

attempt 23 artifact daf68d45cda3
Payload
```
{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "processing",
  "attempt_count": 23
}
```

Apr 5, 06:15 PM Requeued

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 5, 2026, 06:15:33 PM
Event: Requeued
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "pending",
  "next_attempt_at": "2026-04-05T18:20:33.936Z",
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 5, 06:15 PM Processing

riot-fix 0.0.1 attempt 22 · artifact daf68d45cda3

Details Hide
When

Apr 5, 2026, 06:15:26 PM

Event

Processing

Package

riot-fix

Version

0.0.1

Facts

attempt 22 artifact daf68d45cda3
Payload
```
{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "processing",
  "attempt_count": 22
}
```

Apr 5, 05:54 PM Requeued

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 5, 2026, 05:54:47 PM
Event: Requeued
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "pending",
  "next_attempt_at": "2026-04-05T17:59:47.730Z",
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 5, 05:54 PM Processing

riot-fix 0.0.1 attempt 21 · artifact daf68d45cda3

Details Hide
When

Apr 5, 2026, 05:54:40 PM

Event

Processing

Package

riot-fix

Version

0.0.1

Facts

attempt 21 artifact daf68d45cda3
Payload
```
{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "processing",
  "attempt_count": 21
}
```

Apr 5, 05:33 PM Requeued

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 5, 2026, 05:33:19 PM
Event: Requeued
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "pending",
  "next_attempt_at": "2026-04-05T17:38:19.826Z",
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 14, 01:59 PM Indexed

riot-fix 0.0.1 latest 0.0.1 · artifact daf68d45cda3

Details

When: Apr 14, 2026, 01:59:28 PM
Event: Indexed
Package: riot-fix
Version: 0.0.1

Facts

latest 0.0.1 artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "latest": "0.0.1",
  "package_index_key": "index/v1/ri/ot/riot-fix.json",
  "package_index_url": "https://cdn.pkgs.ml/index/v1/ri/ot/riot-fix.json",
  "changed": true
}

Apr 14, 01:59 PM Searchable

riot-fix 0.0.1 latest 0.0.1 · artifact daf68d45cda3

Details

When: Apr 14, 2026, 01:59:28 PM
Event: Searchable
Package: riot-fix
Version: 0.0.1

Facts

latest 0.0.1 artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "latest": "0.0.1",
  "package_index_key": "index/v1/ri/ot/riot-fix.json",
  "package_index_url": "https://cdn.pkgs.ml/index/v1/ri/ot/riot-fix.json",
  "changed": true
}

Apr 14, 01:59 PM

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 14, 2026, 01:59:28 PM
Event
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "yanked_at": "2026-04-14T13:59:28.596Z",
  "yanked_by_github_login": "leostera"
}

Apr 5, 06:58 PM Blocked

riot-fix 0.0.1 attempt 24 · artifact daf68d45cda3

Details

When: Apr 5, 2026, 06:58:14 PM
Event: Blocked
Package: riot-fix
Version: 0.0.1

Facts

attempt 24 artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "blocked",
  "attempt_count": 24,
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 5, 06:58 PM Processing

riot-fix 0.0.1 attempt 24 · artifact daf68d45cda3

Details Hide
When

Apr 5, 2026, 06:58:05 PM

Event

Processing

Package

riot-fix

Version

0.0.1

Facts

attempt 24 artifact daf68d45cda3
Payload
```
{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "processing",
  "attempt_count": 24
}
```

Apr 5, 06:36 PM Requeued

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 5, 2026, 06:36:32 PM
Event: Requeued
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "pending",
  "next_attempt_at": "2026-04-05T18:41:32.906Z",
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 5, 06:36 PM Processing

riot-fix 0.0.1 attempt 23 · artifact daf68d45cda3

Details Hide
When

Apr 5, 2026, 06:36:25 PM

Event

Processing

Package

riot-fix

Version

0.0.1

Facts

attempt 23 artifact daf68d45cda3
Payload
```
{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "processing",
  "attempt_count": 23
}
```

Apr 5, 06:15 PM Requeued

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 5, 2026, 06:15:33 PM
Event: Requeued
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "pending",
  "next_attempt_at": "2026-04-05T18:20:33.936Z",
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 5, 06:15 PM Processing

riot-fix 0.0.1 attempt 22 · artifact daf68d45cda3

Details Hide
When

Apr 5, 2026, 06:15:26 PM

Event

Processing

Package

riot-fix

Version

0.0.1

Facts

attempt 22 artifact daf68d45cda3
Payload
```
{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "processing",
  "attempt_count": 22
}
```

Apr 5, 05:54 PM Requeued

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 5, 2026, 05:54:47 PM
Event: Requeued
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "pending",
  "next_attempt_at": "2026-04-05T17:59:47.730Z",
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}

Apr 5, 05:54 PM Processing

riot-fix 0.0.1 attempt 21 · artifact daf68d45cda3

Details Hide
When

Apr 5, 2026, 05:54:40 PM

Event

Processing

Package

riot-fix

Version

0.0.1

Facts

attempt 21 artifact daf68d45cda3
Payload
```
{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "processing",
  "attempt_count": 21
}
```

Apr 5, 05:33 PM Requeued

riot-fix 0.0.1 artifact daf68d45cda3

Details

When: Apr 5, 2026, 05:33:19 PM
Event: Requeued
Package: riot-fix
Version: 0.0.1

Facts

artifact daf68d45cda3

Payload

{
  "artifact_sha256": "daf68d45cda3bfd2e28fd3a70eb878b39b7de4be2ffcb8a43a95fa018f4b2585",
  "status": "pending",
  "next_attempt_at": "2026-04-05T17:38:19.826Z",
  "error": "container runner returned 500: Failed to start container: Maximum number of running container instances exceeded. Try again later, or try configuring a higher value for max_instances"
}