Tasktype endpoint should gracefully handle malformed api_constraints values

Open

#273 opened on Mar 14, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 48/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Stale
Tech stack: python
Domain: api, backend

Research direction

Start in src/routers/openml/tasktype.py at the GET /tasktype/{task_type_id} entry point and inspect how api_constraints is parsed. Reproduce the endpoint with malformed JSON, a dict-like value, and valid JSON without data_type. Done means the endpoint returns a stable response, accepts string and dict values, and includes input[].data_type only when available.

Written by the indexing model from the issue text.

Description

enhancement

Describe the bug
The /tasktype/{task_type_id} endpoint is not robust to unexpected api_constraints values.
In src/routers/openml/tasktype.py, the current parsing assumes a valid JSON string containing data_type. If api_constraints is malformed JSON, already a dict, or missing data_type, the endpoint may fail or behave inconsistently.

To Reproduce
Minimal reproducible setup (data-level reproduction):

Ensure a task type exists with at least one input row in the DB.
Set api_constraints for that input to malformed JSON, for example:
- "{bad json"
Call:
- GET /tasktype/<task_type_id>

Also test with:

api_constraints already stored as a dict/object-like value (if DB layer returns dict)
api_constraints valid JSON but without data_type, e.g. {"foo":"bar"}

Expected behavior

The endpoint should return a stable response and should not crash.
It should accept both legacy JSON strings and dict-like values.
It should include input[].data_type only when data_type is present.
Malformed JSON in api_constraints should be ignored gracefully for that field.

Additional context
Proposed fix is to make parsing defensive:

parse string values via json.loads inside try/except json.JSONDecodeError
accept dict values directly
set data_type conditionally using safe lookup

Dominant language: Python
Stars: 16
Forks: 50
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

validate-structure inspecte challenge/work/.terraform et rend faux les labs qui ont un provider en cache Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

stephrobert/dsoxlab#238 · Opened Sep 24, 2026
Uniform probability densities use the upper bound as an interval width Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

nasa/fmdtools#40 · Opened Sep 24, 2026
_common_folder() treats a single file as the common folder; single-file archives can't be installed (4.2.8) / crash (master) Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

sublimehq/package_control#1780 · Opened Sep 24, 2026
Set 'Sample' input in 'autorun.py' to utilize 'Sample' Tab in eLog Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

pcdshub/mfx#309 · 2 comments · Opened Sep 24, 2026
niri config file addition does not respect existing optional include Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

nwg-piotr/nwg-displays#145 · Opened Sep 24, 2026

More Python issues