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.

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

Errors #1952

Open
cstarcher opened this issue Aug 6, 2024 · 3 comments
Open

Errors #1952

cstarcher opened this issue Aug 6, 2024 · 3 comments
Labels

Comments

@cstarcher
Copy link
Collaborator

Describe the bug
Errors seem to be reported through the UI and support emails that cannot be attributed to errors in functionality in the system.

Expected behavior
An error should only be reported when an actual error in the system occurs.

Additional context
I've constructed this issue to be broadly defined to consolidate potential related error reporting issues in case it may be advantageous to address them all at the same time. Please add any examples of the described behavior above in the comments.

@cstarcher cstarcher added the bug label Aug 6, 2024
@cstarcher
Copy link
Collaborator Author

cstarcher commented Aug 6, 2024

Related #1882
Related #1838

@cstarcher
Copy link
Collaborator Author

cstarcher commented Aug 8, 2024

Examples of errors reported by TDL:

  • channel: submission/get-one/undefined/action-logs
    message: (400)

Comment from TDL: We see from many different Vireos...my guess is this would be either a spurious error, or it is having trouble displaying the action log? For this error there is no submission number so I can't link it to any other errors.

  • channel: submission/25269/PRIMARY/upload-file
    message: (502)

Comment from TDL: This I'm pretty sure is a connection problem when someone is uploading. For quite a few of these I've then gotten on the Vireo, looked at the submission and didn't see the file I expected. This seems like a real error.

  • channel: submission/2925/update-field-value/223
    message: (500)

Comment from TDL: These almost always deal with a field of some sort, not always update, but sometimes remove etc. If this is real, maybe someone trying to modify keywords or something else multiple maybe.

  • channel: submission/25216/validate-field-value/176
    message: (400)

Comment from TDL: But validate is always a 400 and not a 500.

  • channel: submission/25187/change-status/Needs Correction
    message: (500)

Comment from TDL: Anything related to status is always a 500 error.

@cstarcher
Copy link
Collaborator Author

More examples from TDL:

  • channel: submission/25364/validate-field-value/173
    message: (-1)

Comment from TDL: That one was odd because of the -1.

  • channel: submission-list/add-filter-criterion
    message: (500) query did not return a unique result: 2; nested exception is javax.persistence.NonUniqueResultException: query did not return a unique result: 2

Comment from TDL: I got this one twice from Baylor, and is one of the very rare ones with so much explanation for a 500 error.

  • channel: settings/controlled-vocabulary/compare/Departments
    message: (-1)

channel: submission/get-one/25302
message: Submission not found

  • channel: submission/delete/25309
    message: (404) SubmissionRepoImpl with id 25309 not found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant