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 and warnings are not properly displayed but are truncated. #3080

Open
cjwgriesel opened this issue Feb 29, 2024 · 2 comments
Open

Errors and warnings are not properly displayed but are truncated. #3080

cjwgriesel opened this issue Feb 29, 2024 · 2 comments
Assignees

Comments

@cjwgriesel
Copy link
Contributor

Describe the bug

Errors and warnings are not properly displayed as they are truncated to one line probably due to a character limit of between 70 to 80 characters to be displayed. It would be advantageous to display up to three lines (or more) so that the error or warning is fully displayed. This would also aid in Process support as with an error or a warning fully displayed it will then be obvious what the corrective action is necessary to eliminate the error or warning. This would also mean that errors or warnings need to be clear as to what went wrong and how to correct it!!!

Any time an error or warning is initiated with lines in excess of 70 to 80 characters will be truncated making it difficult to understand what has gone wrong and how to correct it!!!!

Errors and warnings are stored in the errorlist.json file and initiated through the error_handling.f90. The character limit is set to 200 in error_handling.f90.

type :: error
integer :: level ! severity level
character(len=200) :: message ! information string
integer, dimension(8) :: idiags = INT_DEFAULT
real(dp), dimension(8) :: fdiags = FLT_DEFAULT
end type error

but only the first 70 to 80 characters is displayed in the log file or the screen.

@cjwgriesel
Copy link
Contributor Author

might need continuation punctuation in the warnings or errors in the errorlist.json file ??

@cjwgriesel
Copy link
Contributor Author

I tried that but only slightly partially worked....

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

No branches or pull requests

2 participants