DirectProviderBackend deprecation-shim: eligibility check now that attractor's compat window is closed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Start by reading DESIGN-worker-registry-core-split.md Phase 4 and the attractor HISTORY-MAP.md, then inspect the DirectProviderBackend shim and its eligibility checks. Re-run the stated repository and lockfile checks against the listed main branches; done means recording any outstanding condition and whether the shim can be retired.
Written by the indexing model from the issue text.
Description
Filed from microsoft/amplifier-bundle-attractor PR #346 (the P4 slim, attractor-28x), which deleted this repo's twelve compat-window module copies from attractor. That deletion was the stated precondition for reviewing the DirectProviderBackend deprecation shim here.
Ask: re-run the shim's own eligibility criteria now that no consumer resolves the engine from amplifier-bundle-attractor any more. The pre-flight gate on that PR verified, from fresh --depth 1 clones of amplifier-app-actions, amplifier-resolve, amplifier-resolver-dot-graph, and amplifier-app-wiki-weaver at their main tips, that zero live install references to attractor modules remain; the only two uv.lock mentions left are stale transitive entries that contradict their own repo's pyproject.toml at the same commit (uv lock --check reports the lockfile out of date).
If the shim's retirement condition was 'once the old source is gone', it has fired. If it was something narrower, this issue is the place to say so and record what is still outstanding.
Context: DESIGN-worker-registry-core-split.md Phase 4; attractor HISTORY-MAP.md.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 microsoft/amplifier-bundle-dot-runner
-
ready:spec
Difficulty 3/5 1-2 days Newbie friendliness 74/100
microsoft/amplifier-bundle-dot-runner#85 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/amplifier-bundle-dot-runner#77 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/amplifier-bundle-dot-runner#61 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/amplifier-bundle-dot-runner#35 ·
Maintainers usually reply within 1 day
All issues in microsoft/amplifier-bundle-dot-runner
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NVIDIA/flare-local-inference#90 ·
Maintainers usually reply within 1 day
-
area/streaming comp/gateway P2 platform/telegram type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#144897 ·
Maintainers usually reply within 1 day
-
request-theme
Difficulty 1/5 Under an hour Newbie friendliness 66/100
LizardByte/ThemerrDB#9575 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
acl-org/acl-anthology#10599 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zilliztech/memsearch#818 ·
Maintainers usually reply within 1 day