Bug - Not A Bug Tables in the gCLI mutliplying
- Thread starter wrldwzrd89
- Start date
Captain Kirk
Member
So the 1.7 version I am using is it work, and due to the fact that we use it as a plugin for web browsers, I can't really downgrade it from u65 to u55. If this is a java bug, did anyone report it? Or has the function in java changed for some reason?
I just installed both JDK 1.7.0_55 and 1.7.0_65 and I can switch between them at will.
I'll see if I can code up a standalone program which will generate an HTML table and display it the way KoLmafia displays tables in the gCLI. If it works correctly in version 55 and fails in version 65, I'll submit it with a Java bug report. Hopefully, that will give it a chance to be fixed, as opposed to saying "we have a large Java program with 100s of source files and we see this problem."
Code:
bash-3.2$ setjdk 1.7.0_65
bash-3.2$ java -version
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
bash-3.2$ setjdk 1.7.0_55
bash-3.2$ java -version
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)
Bale
Minion
That is a wonderful idea.
I know exactly how much time they'd spend considering a bug reported that way. Goodbye!
I know exactly how much time they'd spend considering a bug reported that way. Goodbye!
xKiv
Active member
Got it.
Code:
bash-3.2$ setjdk 1.7.0_55
bash-3.2$ ant
Buildfile: /src/java-html/build.xml
init:
compile:
jar:
BUILD SUCCESSFUL
Total time: 0 seconds
bash-3.2$ java -jar java-html.jar
Code:
bash-3.2setjdk 1.7.0_65
bash-3.2$ ant
Buildfile: /src/java-html/build.xml
init:
compile:
jar:
BUILD SUCCESSFUL
Total time: 0 seconds
bash-3.2$ java -jar java-html.jar
Well done, indeed!
Bale
Minion
I'm just going to add a link to the place where this bug report continues:
https://bugs.openjdk.java.net/browse/JDK-8054018
https://bugs.openjdk.java.net/browse/JDK-8054018
Huh. When I submitted the bug report, they gave me a temporary number to refer to it by and said it'd be given a real number if it was reviewed and found to be legitimate and entered into the system. They didn't tell me when that happened.
I'm disappointed to see that the formatting was gone from my sample program.
When I filed the bug report, I had to choose an OS; there was no place to say "this happens on all platforms". Not that I could have confirmed that, but I think it will be clear to them that the affected code is not in a platform-specific package.
I'm disappointed to see that the formatting was gone from my sample program.
When I filed the bug report, I had to choose an OS; there was no place to say "this happens on all platforms". Not that I could have confirmed that, but I think it will be clear to them that the affected code is not in a platform-specific package.
Bale
Minion
I just took a look at the progress java has made on this issue. This bug has been handed off to three different people so far. It was even marked "Closed, Won't Fix" for most of a day before it got reopened. No idea what that was about. Fortunately there is some good news:
The second person assigned to this finally identified the bug fix that caused the regression and passed it to the person responsible so he could correct his own error. That was yesterday!
The second person assigned to this finally identified the bug fix that caused the regression and passed it to the person responsible so he could correct his own error. That was yesterday!
Last edited: