asicrs build
- Repo stars 28
- License Apache-2.0
- Author repo proto-fleet
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @block · Apache-2.0
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Linux · Docker
- Runtime requirements
- Docker
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# asicrs-build
`just build-plugins` and `just test-contract` rebuild ASIC-rs only when its
freshness check (mtime against the `BIN` plus a `find -newer` over
`plugin/asicrs sdk/rust server/sdk/v1/pb`) trips. That check is robust for
typical edits but skips when the binary mtime is newer than the source —
which is true after a clean checkout or when switching branches.
## What to do
1. After editing any source under `plugin/asicrs/`, `sdk/rust/`, or
`server/sdk/v1/pb/`, force a rebuild:
- Local development: `just rebuild-plugin asicrs`
- Docker dev runtime (Linux ARM64): same command — it sets
`_asicrs-build-docker` after removing the platform marker.
2. Run `just test-contract` if the change affects miner-driver behavior.
3. If switching between native and Docker runtimes, expect a full rebuild
the first time — the `.asicrs-platform` marker is what disambiguates.
## What to avoid
- Don't hand-edit `server/plugins/asicrs-config.yaml` to make tests pass —
the contract harness rewrites it per suite, and your edits will be
overwritten.
Sections and files
Listed in source order.
sections -> What to do → What to avoid
terms -> No English key terms available
files/cmd -> just build-plugins · just test-contract · BIN · find -newer · plugin/asicrs sdk/rust server/sdk/v1/pb · plugin/asicrs/ · sdk/rust/ · server/sdk/v1/pb/
body sha256 -> cb974c79335a
What to do
After editing any source under
plugin/asicrs/,sdk/rust/, orserver/sdk/v1/pb/, force a rebuild: Local development:just rebuild-plugin asicrsDocker dev runtime (Linux ARM64): same command — it sets_asicrs-build-dockerafter removing the platform marker.What to avoid
Don't hand-edit
server/plugins/asicrs-config.yamlto make tests pass — the contract harness rewrites it per suite, and your edits will be overwritten.