Issue #1910: API call newRepo with non existing tag should returns an error - koji

koji

#1910 API call newRepo with non existing tag should returns an error

Closed: Fixed 4 years ago by tkopecek. Opened 4 years ago by jcupova.

Steps to Reproduce:

Run newRepo(non_exist_tag)

Actual result:

The API call is running without an error message.
Web UI: Task newRepo failed with error:
An error has occurred while processing your request.
NameMapper.NotFound: cannot find 'id' while searching for 'tag.id'
Full tracebacks disabled

Expected result:

API call should returns an error message.

Metadata Update from @julian8628:
- Custom field Size adjusted to None
- Issue set to the milestone: 1.21
- Issue tagged with: easyfix, usability

4 years ago

julian8628 commented 4 years ago

PR #1911

julian8628 commented 4 years ago

@tkopecek should we fix the web UI error? That might not be the only case as unknown tag

tkopecek commented 4 years ago

@julian8628 - I don't thinks so - there are tons of such "unhandled" messages. I think it could wait for new web which we were talking about in last community meeting.

Metadata Update from @jcupova:
- Issue tagged with: testing-done

4 years ago

tkopecek commented 4 years ago

Commit dbef6d2 fixes this issue

tkopecek commented 4 years ago

Commit 810dfe5 fixes this issue

Metadata

Assignee

None

Tags

Blocking

None

Depending on

None

Priority

Normal

Milestone

1.21

Size

None

Attachments 1

Screenshot_from_2020-01-06_08-06-24.png

Attached 4 years ago View Comment

Related Pull Requests

#1911 Merged 4 years ago

koji

Source Code

Documentation

#1910 API call newRepo with non existing tag should returns an error Closed: Fixed 4 years ago by tkopecek. Opened 4 years ago by jcupova.

Metadata

easyfix usability testing-done

Attachments 1

Related Pull Requests

#1910 API call newRepo with non existing tag should returns an error

Closed: Fixed 4 years ago by tkopecek. Opened 4 years ago by jcupova.