Request for Feedback on Production Upgrade Needs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go
- Domain
- documentation
Research direction
Read the upgrade and architecture discussions in issues #430 and #464 to understand the changes that could affect existing deployments. The issue asks users to report production upgrade needs; done means affected users have shared that feedback. This is a request for feedback, not a code change.
Written by the indexing model from the issue text.
Description
AgentCube is still at an early stage. We expect substantial changes, including the architectural changes discussed in #430 and the agent-sandbox 1.0.x upgrade tracked in #464. These changes may break compatibility with existing deployments.
Before investing in migration paths and backward compatibility, we’d like to know whether anyone is currently running AgentCube in production and expects to upgrade an existing deployment. If that applies to you, please let us know.
Until we hear from users with those needs, we may prioritize rapid iteration over compatibility with earlier versions. This is a consideration for the project’s early stage, not a long-term approach: as the architecture and core capabilities mature, we intend to establish clearer compatibility expectations and provide upgrade guidance.
- Dominant language
- Go
- Stars
- 175
- Forks
- 96
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 9
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 volcano-sh/agentcube
-
Flaky TestGetPrivateKeyPEM in pkg/router due to direct deep equal assertion on rsa.PrivateKeyPossibly taken @0xA8hinav claimed this 183 days ago. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
volcano-sh/agentcube#348 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 10/100
volcano-sh/agentcube#513 ·
Maintainers usually reply within 1 day
-
router: Start returns before graceful shutdown finishes, so in-flight requests are cut off on SIGTERMPossibly taken @Paramveersingh-S claimed this 3 days ago. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
volcano-sh/agentcube#508 ·
Maintainers usually reply within 1 day
-
Add error-path tests for handleDeleteSandbox to verify Kubernetes and store consistencyPossibly taken @SoumaCloud claimed this 10 days ago. Open
volcano-sh/agentcube#500 · 6 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
PicoD subprocess execution does not respect incoming HTTP request cancellationPossibly taken @SoumaCloud claimed this 10 days ago. Openkind/bug
volcano-sh/agentcube#499 · 7 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in volcano-sh/agentcube
Similar issues
-
0.kind: bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Judgment-Pack/judgment-pack-runtime#390 ·
Maintainers usually reply within 1 day
-
triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cozystack/cozystack#5300 · 1 reaction ·
Maintainers usually reply within 2 days
-
bug go
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
teradata-labs/loom#665 ·
Maintainers usually reply within 1 day
-
Improve DB UIOpenenhancement ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
jbigler/railswitch#222 ·
Maintainers usually reply within 1 day