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

Hot code replace error box "Details button" bug #489

Open
SougandhS opened this issue Sep 11, 2024 · 14 comments
Open

Hot code replace error box "Details button" bug #489

SougandhS opened this issue Sep 11, 2024 · 14 comments

Comments

@SougandhS
Copy link
Contributor

I tried the error cases for Hot code replace functionality. On every fail the pop up shows additional "Details >>" button, On clicking the button it shows the same message as provided in the parent box ("Reason" line)

image

Please advice whether we should keep this button or not ?

@SougandhS
Copy link
Contributor Author

@jukzi @iloveeclipse any suggestions ?

@jukzi
Copy link
Contributor

jukzi commented Sep 12, 2024

maybe in other situations it displays more information? i don't know.

@SougandhS
Copy link
Contributor Author

SougandhS commented Sep 12, 2024

I think its same

image image image

@SougandhS
Copy link
Contributor Author

For obsolete methods error box we dont have that details button

image

@SougandhS
Copy link
Contributor Author

While HCR fails the detailMessage generated is used for both reason and details button

image

and StackTrace is also not available for the exceptions

image

@SougandhS SougandhS changed the title Hot code replace error box "Details button" Hot code replace error box "Details button" bug Sep 18, 2024
@iloveeclipse
Copy link
Member

I could only guess that original IBM JVM (J9) may provide more info, but I haven't looked at the code if there is additional handling of the "details" content and if that is coming from another source as the visible part of the message.

If that is feed with the same data, then the "details" part is obviously wasting space, if not, it should be kept.

@SougandhS
Copy link
Contributor Author

I could only guess that original IBM JVM (J9) may provide more info, but I haven't looked at the code if there is additional handling of the "details" content and if that is coming from another source as the visible part of the message.

If that is feed with the same data, then the "details" part is obviously wasting space, if not, it should be kept.

Went through it again and found for some selected JDWP error codes throw UnsupportedOperationException with a fixed string message, and this same message is used in "details" section

image image image

@SougandhS
Copy link
Contributor Author

SougandhS commented Oct 18, 2024

Checked with other few scenarios having other than unsupported exception, Only showing exception classes

image
image
image

@SougandhS
Copy link
Contributor Author

SougandhS commented Oct 21, 2024

Hi @iloveeclipse, @jukzi shall we include the exception class details in "Details" for unsupported [ADD,DELETE etc] ones similar to the other exceptions ?
we can then avoid same text showing in both.

@SougandhS
Copy link
Contributor Author

SougandhS commented Oct 29, 2024

Hi @iloveeclipse, @jukzi shall we include the exception class details in "Details" for unsupported [ADD,DELETE etc] ones similar to the other exceptions ? we can then avoid same text showing in both.

How about including corresponding error code + unsupported exception class name ?
As error codes are common for all JVMs

@jukzi
Copy link
Contributor

jukzi commented Oct 29, 2024

I am not interested in the topic of hot code replace failures. But if you show after/before screenshots of changes that might make sense then i might take a look.

@SougandhS
Copy link
Contributor Author

SougandhS commented Oct 29, 2024

I am not interested in the topic of hot code replace failures. But if you show after/before screenshots of changes that might make sense then i might take a look.

before it used to show this
[Details section shows same as shown in reason]
image

my proposal -
image

@jukzi
Copy link
Contributor

jukzi commented Oct 29, 2024

looks good.

@SougandhS
Copy link
Contributor Author

looks good.

Thanks

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

3 participants