GitLab reviewer and refiner never post on a local Agent Server
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start with _remove_checkout() in skills/gitlab-mr-reviewer/scripts/common.py and compare its behavior with _release_checkout() in the gitlab-issue-to-mr code path, which the issue says already logs and continues. Check how paths outside the current WORKSPACE_BASE are handled, then verify that skipping such a checkout leaves it on disk while allowing the note and record update to proceed.
Written by the indexing model from the issue text.
Description
What happens
On a local Agent Canvas, the GitLab MR reviewer starts a review, the review conversation finishes, but the review note is never posted to the merge request. The work item refiner shares the same code path, so its notes don't appear either.
Cause
On a local Agent Canvas each automation run gets its own WORKSPACE_BASE (.../workspaces/automation-runs/<run-id>). The reviewer and refiner start a conversation in one run and publish its result in a later one.
When they publish, _remove_checkout() in skills/gitlab-mr-reviewer/scripts/common.py resolves the checkout root from the current run's WORKSPACE_BASE. The earlier run's checkout is outside that root, so it raises:
ValueError: Refusing to remove a workspace outside GitLab review checkouts
This happens before the note is posted and before the record is updated, so every later run fails the same way.
gitlab-issue-to-mr uses the same layout, but its _release_checkout() logs "Refusing to remove …" and continues.
Proposed fix
Do the same in _remove_checkout(): skip a path outside the current root with a warning instead of raising. Nothing outside the root is deleted. A checkout skipped this way stays on disk under its own run's directory.
Environment
Local Agent Canvas (Docker), openhands-agent-server 1.62.0, extensions main at cfd1d0f. Found together with #969.
- Dominant language
- Python
- Stars
- 184
- Forks
- 137
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 60
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 OpenHands/extensions
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#969 ·
Maintainers usually reply within 1 day
-
Add a `maven` skill: agents install Debian's `maven` package, which can't load plugins built for Java 17+Possibly taken @sumitvairagar claimed this 1 day ago. Openpriority:medium ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
OpenHands/extensions#963 ·
Maintainers usually reply within 1 day
-
agent-readiness-report: scan_build_env.sh misses lowercase `justfile` and `just` build commandsPossibly taken @austinchennn claimed this today. Openpriority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#955 · 1 comment ·
Maintainers usually reply within 1 day
-
Update Slack MCP integration to Slack's official hosted MCP server (replace zencoderai/slack-mcp-server)Possibly taken @all-hands-bot claimed this 13 days ago. Opencustomer-support enhancement priority:medium ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenHands/extensions#900 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenHands/extensions#887 ·
Maintainers usually reply within 1 day
All issues in OpenHands/extensions
Similar issues
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 74/100
BrainLesion/BraTS#200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
rl-institut/enetra#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/datasets#9100 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/garak#2486 · 1 comment ·
Maintainers usually reply within 2 days
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
O-X-L/ansible-opnsense#520 ·
Maintainers usually reply within 2 days