-
Notifications
You must be signed in to change notification settings - Fork 1.3k
another typo that appears when monitoring the java process via JMX #913
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
Conversation
|
LGTM, though we will need to check if these strings are consumed through any APIs so that we don't end up breaking backward/API compatibilies |
|
When I've made the changed I've looked through all the files for the text and found no match but it's better to test first . |
|
LGTM, based on a set of tests that I run on this branch (which I rebased myself first): Result: And: Result: Someone else please review the code. |
|
valid English replacement of strings I see @bhaisaab 's point in his comment but had eclipse check java references to the call and is never made. It must be implemented as on override of an interface method. LGTM ( @remibergsma ) |
another typo that appears when monitoring the java process via JMXStatus : in preogress instead of in progress and some other small typos . * pr/913: another typo that appears when monitoring the java process via JMX Signed-off-by: Remi Bergsma <[email protected]>
* migratewizard: Display error and unfreeze form when api call fails * migratewizard: Fix fetching jobid from api response Signed-off-by: Rohit Yadav <[email protected]>
Status : in preogress instead of in progress and some other small typos .