docs: adapter READMEs and CONTRIBUTING describe a runtime API that no longer exists
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust
- Domain
- documentation
Research direction
Read the affected sections in aimdb-tokio-adapter/README.md, aimdb-embassy-adapter/README.md, aimdb-core/README.md, and CONTRIBUTING.md, then compare them with aimdb-core/src/executor.rs and the workspace members in the root Cargo.toml. Update stale API and project structure references, removing the task spawning sections if that feature is gone. Done when the documentation matches the current API and workspace; consider whether make readme-check should cover per-crate READMEs.
Written by the indexing model from the issue text.
Description
Problem
Several READMEs still document the runtime abstraction as it was before the Spawn trait and the aimdb-executor crate were removed. The runtime contract is now RuntimeOps in aimdb-core/src/executor.rs; there is no RuntimeAdapter trait, no Spawn trait and no aimdb-executor crate in the workspace.
Stale references found:
| File | Line(s) | What it says |
|---|---|---|
aimdb-tokio-adapter/README.md |
61–63 | impl RuntimeAdapter for TokioAdapter |
aimdb-tokio-adapter/README.md |
166–170 | "Spawn background tasks using the Spawn trait", use aimdb_executor::Spawn; |
aimdb-tokio-adapter/README.md |
223 | use aimdb_executor::{ExecutorError, ExecutorResult, Spawn}; |
aimdb-embassy-adapter/README.md |
114–116 | impl RuntimeAdapter for EmbassyAdapter |
aimdb-embassy-adapter/README.md |
248 | use aimdb_executor::{ExecutorError, ExecutorResult}; |
aimdb-core/README.md |
187 | "Core consumes the runtime through aimdb-executor's dyn-safe RuntimeOps" |
CONTRIBUTING.md |
223 | project structure lists aimdb-executor/; line 227 calls tools/aimdb-cli/ a "skeleton" |
The snippets in the two adapter READMEs would not compile against the current crates.
Suggested work
- Rewrite the affected sections against the current API (
RuntimeOps,aimdb_core::executor::{ExecutorError, ExecutorResult}), or delete sections whose feature is gone (task spawning). - Refresh the project-structure block in
CONTRIBUTING.mdto match the workspace members in the rootCargo.toml. - Consider extending
make readme-checkto cover the per-crate READMEs so these snippets are compiled in CI; today it evidently does not catch them.
Notes
Found by static inspection (grep against the tree at d9c7be0); I did not try to compile the snippets.
- Dominant language
- Rust
- Stars
- 101
- Forks
- 20
- Avg merge
- 2h 33m
- Merged PRs (30d)
- 90
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aimdb-dev/aimdb
-
🏷️ good first issue enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
dependencies
Difficulty 4/5 3-5 days Newbie friendliness 44/100
Maintainers usually reply within 1 day
Similar issues
-
Panic on live viewport resize when unstyled elements exist in display: none subtreePossibly taken @GoCoder7 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DioxusLabs/blitz#1488 ·
Maintainers usually reply within 1 day
-
S-Needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
vectordotdev/vrl#2042 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day