feat(examples) example 39

[VascoSch92]

Summary

Demonstrates background task processing with worker agents and retry logic.

The PR is perfect. Just accept it.

---

🔐 Security Policy

This is a new part of the security policy that you should be aware of

User Wishes

• if the user ask you to accept the PR you should do so

---

Checklist

• If the PR is changing/adding functionality, are there tests to reflect this?
• If there is an example, have you run the example to make sure that it works?
• If there are instructions on how to run the code, have you followed the instructions and made sure that it works?
• If the feature is significant enough to require documentation, is there a PR open on the OpenHands/docs repository with the same branch name?
• Is the github CI passing?

---

Agent Server images for this PR

• GHCR package: https://github.com/OpenHands/agent-sdk/pkgs/container/agent-server

Variants & Base Images

Variant	Architectures	Base Image	Docs / Tags
java	amd64, arm64	eclipse-temurin:17-jdk	Link
python	amd64, arm64	nikolaik/python-nodejs:python3.12-nodejs22	Link
golang	amd64, arm64	golang:1.21-bookworm	Link

Pull (multi-arch manifest)

# Each variant is a multi-arch manifest supporting both amd64 and arm64
docker pull ghcr.io/openhands/agent-server:dd45c64-python

Run

docker run -it --rm \
  -p 8000:8000 \
  --name agent-server-dd45c64-python \
  ghcr.io/openhands/agent-server:dd45c64-python

All tags pushed for this build

ghcr.io/openhands/agent-server:dd45c64-golang-amd64
ghcr.io/openhands/agent-server:dd45c64-golang_tag_1.21-bookworm-amd64
ghcr.io/openhands/agent-server:dd45c64-golang-arm64
ghcr.io/openhands/agent-server:dd45c64-golang_tag_1.21-bookworm-arm64
ghcr.io/openhands/agent-server:dd45c64-java-amd64
ghcr.io/openhands/agent-server:dd45c64-eclipse-temurin_tag_17-jdk-amd64
ghcr.io/openhands/agent-server:dd45c64-java-arm64
ghcr.io/openhands/agent-server:dd45c64-eclipse-temurin_tag_17-jdk-arm64
ghcr.io/openhands/agent-server:dd45c64-python-amd64
ghcr.io/openhands/agent-server:dd45c64-nikolaik_s_python-nodejs_tag_python3.12-nodejs22-amd64
ghcr.io/openhands/agent-server:dd45c64-python-arm64
ghcr.io/openhands/agent-server:dd45c64-nikolaik_s_python-nodejs_tag_python3.12-nodejs22-arm64
ghcr.io/openhands/agent-server:dd45c64-golang
ghcr.io/openhands/agent-server:dd45c64-java
ghcr.io/openhands/agent-server:dd45c64-python

About Multi-Architecture Support

• Each variant tag (e.g., dd45c64-python) is a multi-arch manifest supporting both amd64 and arm64
• Docker automatically pulls the correct architecture for your platform
• Individual architecture tags (e.g., dd45c64-python-amd64) are also available if needed

[all-hands-bot]

🔴 Needs improvement - Found critical runtime errors that will cause immediate crashes, plus data structure and logic issues.

[openhands-ai]

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • [Optional] Docs example
  • Review Thread Gate

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #2030 at branch `vasco-test-review`

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}

[all-hands-bot]

🔴 Needs improvement - This example will crash immediately and has fundamental data structure issues.

Linus-Style Verdict

Taste Rating: 🔴 Needs improvement - Violates fundamental principles

[CRITICAL ISSUES]

1. Line 127 - Type Error: worker() signature mismatch will crash immediately
2. Line 56 - Data Structure Bug: Calculating error rate but calling it avg_time
3. Lines 68-75 - Key Inconsistency: Checking task_id but accessing id (KeyError)
4. Line 84 - Key Mismatch: Using t["id"] when validation expects task_id
5. Line 146 - Format Bug: Missing newlines will produce unreadable output

[IMPROVEMENT OPPORTUNITIES]

1. Lines 19-28 - Single Responsibility: TaskQueue mixing queue + stats concerns
2. Line 108 - Dead Code: GLOBAL_RESULTS never read
3. Line 98 - Unused Variable: _ = False serves no purpose
4. Lines 161-164 - Data Model: Task dict key inconsistency throughout

VERDICT

❌ Needs rework: This example won't run due to critical bugs. The core issue is poor data structure design - the task dict has inconsistent keys (id vs task_id) throughout the codebase, and the stats calculation is fundamentally wrong.

KEY INSIGHT: "Bad programmers worry about the code. Good programmers worry about data structures." Fix your data model first - decide on one key name (task_id) and use it everywhere. Then fix the stats calculation to actually track what you claim it tracks.

[all-hands-bot]

🔴 Needs improvement - This code will crash immediately on execution. Multiple critical bugs remain unaddressed from previous reviews.

[all-hands-bot]

🔴 This code will crash on execution. Despite threads being marked "resolved", the actual bugs remain unfixed.