-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8263055: hsdb Command Line Debugger does not properly direct output for some commands #2887
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
…e right place when the two are not the same.
👋 Welcome back cjplummer! A progress list of the required criteria for merging this PR into |
@plummercj The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
@plummercj This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 73 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Thanks, Yasumasa and Alex! |
/integrate |
@plummercj Since your change was applied there have been 87 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit b2f7c58. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
I ran the hsdb Command Line Debugger (Windows -> Console menu item) and tried the class and classes commands, and neither appeared to produce any output. Other commands seemed to work as expected. I then went back to the terminal window I used to launch hsdb, and notice all the output from class and classes commands went there instead. The reason is because these commands are using System.out.println instead of out.println. "out" is a PrintStream field of the CommandProcessor instance, and should be used for all output other than error output, which can use "err".
We have no test for this, but I did run the hsdb GUI, brought up the Command Line Debugger, and confirmed that
class
andclasses
now properly show the output there. We do have clhsdb tests that also exercise this CommandProcessor code, but clhsdb directs all the output to System.out, soout.println
andSystem.out.println
end up being the same, thus the issue was not noticed.Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2887/head:pull/2887
$ git checkout pull/2887