Unify error codes for trying to access private data (?)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
For private datasets, trying to access different meta-data without the rights gives different error responses. I think it would be much cleaner if all return the same error, probably either 112 or 275.
https://www.openml.org/api/v1/xml/data/features/45
https://www.openml.org/api/v1/xml/data/qualities/45
https://www.openml.org/api/v1/xml/data/45
On that note, why are there different error codes for fetching meta-data of datasets which don't exist?
https://www.openml.org/api/v1/xml/data/12345678945
https://www.openml.org/api/v1/xml/data/features/12345678945
https://www.openml.org/api/v1/xml/data/qualities/12345678945
Contributor 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.
Research direction
Compare the responses from the six dataset, features, and qualities API endpoints listed in the issue for both private and nonexistent datasets. Trace where their error responses are generated, then determine the intended common error behavior and verify that all cases return it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100