Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Changed the status code from 500 to 404 for ODIM and Plugin manager if data is not present in the system #1305

Merged
merged 7 commits into from
Sep 5, 2023
Merged

Changed the status code from 500 to 404 for ODIM and Plugin manager if data is not present in the system #1305

merged 7 commits into from
Sep 5, 2023

Conversation

salonisrivastava12
Copy link
Contributor

requested resource actually does not exists in the system so it should return 404 error

@salonisrivastava12 salonisrivastava12 changed the title Resolved bug 7888 : if data is not present error status should be 404 Changed the status code from 500 to 404- for ODIM and Plugin manager if data is not present in the system Sep 4, 2023
@salonisrivastava12 salonisrivastava12 changed the title Changed the status code from 500 to 404- for ODIM and Plugin manager if data is not present in the system Changed the status code from 500 to 404 for ODIM and Plugin manager if data is not present in the system Sep 4, 2023
@salonisrivastava12 salonisrivastava12 added type:bug This tag is attached to 'bug' issue during creation prio:normal normal priority, can be taken up after high priority issues are addressed status:in-progress issue has been accepted previously and now taken up for implementation labels Sep 4, 2023
@jeevan-kamkar jeevan-kamkar merged commit a64c111 into ODIM-Project:development Sep 5, 2023
5 checks passed
@jeevan-kamkar jeevan-kamkar deleted the ODIM-7888 branch September 5, 2023 08:47
@jeevan-kamkar jeevan-kamkar added status:confirmed Issue is accepted and implementation will be taken up at the earliest subject to priorities status:resolved issue is completed and confirmed to be working as expected and removed status:in-progress issue has been accepted previously and now taken up for implementation status:confirmed Issue is accepted and implementation will be taken up at the earliest subject to priorities labels Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jeevan-kamkar jeevan-kamkar jeevan-kamkar approved these changes

@chauberahul1993 chauberahul1993 chauberahul1993 approved these changes

@kavyamani596 kavyamani596 Awaiting requested review from kavyamani596

@sriteja-sabbineni sriteja-sabbineni Awaiting requested review from sriteja-sabbineni

@mohamed-shahid-afrid mohamed-shahid-afrid Awaiting requested review from mohamed-shahid-afrid

@annu-mishraa annu-mishraa Awaiting requested review from annu-mishraa

@akshata-s-banoshi akshata-s-banoshi Awaiting requested review from akshata-s-banoshi

Assignees
No one assigned
Labels
prio:normal normal priority, can be taken up after high priority issues are addressed status:resolved issue is completed and confirmed to be working as expected type:bug This tag is attached to 'bug' issue during creation
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@salonisrivastava12 @jeevan-kamkar @chauberahul1993