FRB Fix CI

Note: Check your user-level remote-testing rules before running commands. Tests and codegen may require remote execution.

Overview

CI failures in flutter_rust_bridge often have simple fixes. Try the appropriate approach below before deep investigation.

Core principle: Start with lazy fixes (re-run, copy diff, --fix) before expensive investigation.

Symptom	Fix
Flaky test (passes sometimes)	`gh run rerun --failed`
Git diff shown in CI	`git apply` OR regenerate
Lint/format errors	Add `--fix` flag
Can't reproduce locally	Use same `./frb_internal` command from CI

Sometimes CI fails due to timing issues, not real bugs. Rerun only failed jobs:

bash

gh run rerun --failed

If it passes on retry → flaky, not your bug.

When CI shows a diff, you have two options:

Option A: git apply (faster)

CI already ran the generator. Just apply what it computed:

bash

# Copy the diff from CI, then:
pbpaste | git apply   # macOS

Option B: Regenerate (slower but more "proper")

bash

./frb_internal precommit-generate

After codegen: Check your user-level remote-testing rules. If codegen was run remotely, pull changes back to local.

Both are correct. Option A is faster; Option B is more thorough.

For clippy, dart analyze, or format errors, use --fix:

bash

./frb_internal lint --fix

This runs:

CI shows the command it ran. Run the same command:

bash

# CI shows: ./frb_internal test-dart --package frb_example/pure_dart
./frb_internal test-dart --package frb_example/pure_dart