Specify all entities which can't be linked to a collection on a create/attach/detach call.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing the server-side create, attach, and detach handling and the database-error path described in the issue. Done means that, when at least one conflict exists, the response identifies all missing, already-attached, or unattached entities while preserving the existing happy path.
Written by the indexing model from the issue text.
Description
The current implementation relies on the database errors to specify if something can not be (un)linked to a study. This is useful because there is less overhead in the happy-path. However, when some entities don't exist, or are already attached (for attach) or are not attached (for detach), then only the first such conflict is provided by the database error. This means that a user that tries to attach multiple entities at once, with multiple conflicts at once, can only resolve the conflicts one-by-one (or they have to collect the study/tasks/runs themselves, then do the matching). It would be good to do this check serverside only if we already establish there is already at least one conflict.
- Dominant language
- Python
- Stars
- 16
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 openml/server-api
-
behavior
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
openml/server-api#337 · 1 comment ·
-
Redesign POST /data/untag for v2Possibly taken @omosola claimed this 27 days ago. Openproposal
openml/server-api#375 · 2 comments · 1 assignee ·
-
Redesign POST /data/tag for v2Possibly taken @omosola claimed this 27 days ago. Open
openml/server-api#374 · 2 comments · 1 assignee ·
-
Redesign POST /data/qualities/unprocessed/{data_engine_id}/{order} for v2Possibly taken @omosola claimed this 27 days ago. Open
openml/server-api#373 · 1 assignee ·
-
Redesign POST /data/qualities for v2Possibly taken @omosola claimed this 27 days ago. Open
openml/server-api#372 · 1 assignee ·
All issues in openml/server-api
Similar issues
-
bug status/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
prowler-cloud/prowler#12887 · 1 comment ·
Maintainers usually reply within 1 day
-
area: desktop platform: macos priority: p3 status: ready type: enhancement
Difficulty 1/5 Under an hour Newbie friendliness 92/100
use-agent-os/agent-os#3484 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
open-telemetry/opentelemetry-python-contrib#5113 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
external
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/docs#6255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day