docs/api-guide.md: "an actor occupies its whole worker" contradicts multi-actor workers
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go
- Domain
- documentation
Research direction
Read docs/api-guide.md around line 141 and compare its wording with docs/api-guide.md lines 66-67 and docs/glossary.md lines 48-50. Check cmd/ateom-gvisor/main.go and cmd/ateapi/internal/scheduling/scheduling.go for the current worker and scheduling behavior. Done means the documentation no longer contradicts multi-actor workers and accurately describes how requests are treated.
Written by the indexing model from the issue text.
Description
docs/api-guide.md line 141 (v0.3.0) says: "requests are not consulted today (an actor occupies its whole worker)."
Since v0.2.0 (#1836), a worker hosts several actors at once: --max-actors defaults to 1000 (cmd/ateom-gvisor/main.go:83), and the scheduler places actors by remaining CPU and memory (cmd/ateapi/internal/scheduling/scheduling.go:153). docs/api-guide.md lines 66-67 and docs/glossary.md lines 48-50 already say so. On a v0.3.0 kind install with a two-replica gVisor WorkerPool, kubectl ate get actors showed two running actors on one worker pod at once.
The parenthetical at line 141 reads as the current placement rule and contradicts the other two passages. Suggest removing it, or restating it as how requests are treated now.
- Dominant language
- Go
- Stars
- 4.4k
- Forks
- 515
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 258
Getting set up
- 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 agent-substrate/substrate
-
[Bug]: e2e script flag parsing is brokenPossibly taken @ericcurtin claimed this today. Openarea/dev-infra area/tests kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agent-substrate/substrate#2217 · 1 comment ·
Maintainers usually reply within 1 day
-
Reject trailing YAML documents in actor-template create manifestsPossibly taken @ericcurtin claimed this 3 days ago. Openarea/cli kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
agent-substrate/substrate#2156 · 1 comment ·
Maintainers usually reply within 1 day
-
area/storage kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
agent-substrate/substrate#2155 · 1 comment ·
Maintainers usually reply within 1 day
-
Delete final-round GCS compose inputs after successful uploadsPossibly taken A pull request linked to this issue is open or already merged. Openarea/storage kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
agent-substrate/substrate#2154 ·
Maintainers usually reply within 1 day
-
area/gvisor area/node kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
agent-substrate/substrate#2035 ·
Maintainers usually reply within 1 day
All issues in agent-substrate/substrate
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#3873 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
pion/interceptor#479 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
yetone/magpie#1035 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
slavakurilyak/awesome-ai-agents#710 ·
Maintainers usually reply within 1 day
-
`renderLinkedIssues` overshoots its byte budget: unresolved and omitted lists are never boundedOpenagent-butler-finding agent-research-recommend bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jordansmall/spindrift#4614 · 1 comment ·
Maintainers usually reply within 1 day