intent: a create-from without fromStatus answers 200 on a missing or unknown source id (no 400/404)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Read Generate.java.template around lines 129–175, then compare its response handling with Transition.java.template and the guarded create-from path. Check how missing and unknown source IDs set HTTP status, and run the relevant endpoint tests if available. Done means missing IDs return 400 and unknown IDs return 404 for every create-from path.
Written by the indexing model from the issue text.
Description
Problem
A generates create-from (<Name>Generate/run) without a from-status guard answers 200 with {"error": "source <Entity> not found"} for an id no row has. A missing id answers 200 with {"error": "missing source id"}. A client or test that branches on the status (the generated action button, an apptest flow, a probe) reads both as success. The same endpoint answers 404 when the intent declares fromStatus: / sourceStatus:, because the guard path sets the status, and the transition endpoint answers 400 / 404.
Where (release commit 862f6d1a, 14.93.0)
Generate.java.template ~L129-L175:
if (req == null || req.id == null) { return "{\"error\": \"missing source id\"}"; }has noResponse.setStatus(400);if (saved == null) { return "{\"error\": \"source ... not found\"}"; }has noResponse.setStatus(404)(only the#if(guard)branch sets 404).
Note: an earlier report said an unknown id gives a 500 because findById throws. That is not the case on 14.88.0 or 14.93.0: JavaEntityStore.findById returns null (findOne(...).orElse(null)). The defect is the missing status.
Expected
400 for a missing id and 404 for an unknown source on every create-from, matching the guarded path and Transition.java.template.
🤖 Generated with Claude Code
- Dominant language
- Java
- Stars
- 278
- Forks
- 97
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 242
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 eclipse-dirigible/dirigible
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
eclipse-dirigible/dirigible#7958 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
eclipse-dirigible/dirigible#7891 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
eclipse-dirigible/dirigible#6538 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
eclipse-dirigible/dirigible#4812 ·
Maintainers usually reply within 1 day
-
bug component-ide efforts-medium priority-medium usability web-ide
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
eclipse-dirigible/dirigible#2920 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in eclipse-dirigible/dirigible
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuicksilverMC/Argentum#31 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
navikt/mock-oauth2-server#1129 ·
Maintainers usually reply within 1 day
-
bug main ui
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openhab/openhab-webui#4600 ·
Maintainers usually reply within 4 days
-
26.4 area: tags enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
`DeepSeekChatModel` streaming returns no content when chunks have no `id`Possibly taken @lejuho claimed this today. Openstatus: waiting-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spring-projects/spring-ai#7214 ·
Maintainers usually reply within 2 days