Missing workflow returns 500 from workflow type endpoint
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #8398 by @VuMartin — closed without merging
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Start the local development stack, authenticate, and reproduce GET /api/workflow/type/2147483647. Trace the endpoint through workflowDao.fetchOneByWid and verify the missing workflow case; done means the same request returns HTTP 404 rather than 500 for both regular and admin users.
Written by the indexing model from the issue text.
Description
What happened?
The workflow type endpoint dereferences a missing DAO result. An authenticated request for a workflow ID that does not exist returns 500 instead of 404.
Before: missing workflow returns 500
After: missing workflow returns 404
How to reproduce?
- Start the local development stack.
- Sign in as a regular or admin user.
- Send
GET /api/workflow/type/2147483647.
The local response was 500:
{"code":500,"message":"There was an error processing your request."}
Version/Branch
1.3.0-incubating-SNAPSHOT (main)
Commit Hash (Optional)
7d57cd6ef1
Relevant log output
The request reaches workflowDao.fetchOneByWid, receives null, and then calls workflow.getIsPublic.
- Dominant language
- Scala
- Stars
- 316
- Forks
- 192
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 131
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 apache/texera
-
inner.py carries an ASF header over MIT third-party code and is missing from LICENSEPossibly taken @mengw15 claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/texera#8775 · 1 comment ·
Maintainers usually reply within 1 day
-
Search bar autocomplete stops working after a model appears in the suggestionsPossibly taken @aglinxinyuan claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/texera#8700 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
apache/texera#8682 · 5 comments ·
Maintainers usually reply within 1 day
-
JSONL File Scan reads a JSON null as the text "null"Possibly taken @CaroFernando claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
apache/texera#8674 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
Similar issues
-
area:expressions area:ffi bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
apache/datafusion-comet#6592 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
chipsalliance/chisel#5504 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Homebrew formula 2.1.26: 'cs completions bash' fails (exit 127) because bin/cs is not executableOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
smart-data-lake/smart-data-lake#1166 ·
Maintainers usually reply within 1 day