From duke at openjdk.java.net Sat Jan 1 00:33:47 2022 From: duke at openjdk.java.net (Martin Skarsaune) Date: Sat, 1 Jan 2022 00:33:47 GMT Subject: RFR: 7455: Add support for jolokia JMX service connection [v7] In-Reply-To: References: Message-ID: > Setting back for review. The azure problem requires a fix in Jolokia. > > Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol. Martin Skarsaune has updated the pull request incrementally with one additional commit since the last revision: Review corrections: Javadoc and refactoring attempt to use local operation info ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/332/files - new: https://git.openjdk.java.net/jmc/pull/332/files/955e3f8a..800a31d5 Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=332&range=06 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=332&range=05-06 Stats: 77 lines in 7 files changed: 38 ins; 17 del; 22 mod Patch: https://git.openjdk.java.net/jmc/pull/332.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/332/head:pull/332 PR: https://git.openjdk.java.net/jmc/pull/332 From duke at openjdk.java.net Sat Jan 1 11:26:19 2022 From: duke at openjdk.java.net (Michael =?UTF-8?B?U8O8ZGthbXA=?=) Date: Sat, 1 Jan 2022 11:26:19 GMT Subject: RFR: 7439: Introduced IConstantPoolExtension for Constant Pools [v6] In-Reply-To: References: Message-ID: On Wed, 29 Dec 2021 21:23:43 GMT, Jean-Philippe Bempel wrote: >> Jean-Philippe Bempel has updated the pull request incrementally with one additional commit since the last revision: >> >> remove unused import > > is your stacktrace for the error similar to: > > java.lang.StringIndexOutOfBoundsException: String index out of range: -11 > at java.base/java.lang.String.substring(String.java:1841) > at org.openjdk.jmc.flightrecorder.internal.parser.v1.StructTypes$JfrJavaClass.convertNames(StructTypes.java:331) > at org.openjdk.jmc.flightrecorder.internal.parser.v1.StructTypes$JfrJavaClass.getFullName(StructTypes.java:315) > at org.openjdk.jmc.flightrecorder.internal.parser.v1.StructTypes$JfrJavaClass.hashCode(StructTypes.java:341) > at java.base/java.util.Objects.hashCode(Objects.java:116) > at org.openjdk.jmc.flightrecorder.internal.parser.v1.StructTypes$JfrMethod.hashCode(StructTypes.java:625) > at org.openjdk.jmc.flightrecorder.stacktrace.graph.AggregatableFrame.hashCode(AggregatableFrame.java:90) > at java.base/java.util.HashMap.hash(HashMap.java:339) > at java.base/java.util.HashMap.get(HashMap.java:552) > > ? > in that case it's because you have changed the class name but not the package name associated. > Then when referencing a class or a method, package name & class name are not the same, which is not expected. > > in your example to fix the issue: > > > private static Deobfuscator createFooDeobfuscator() { > Map obfuscatorClassMap = new HashMap(); // obfuscated class -> class > obfuscatorClassMap.put("se/hirt/jmc/tutorial/hotmethods/HotMethods", "de/docware/ms/foo/Foo"); > Map obfuscatorPackageMap = new HashMap(); // obfuscated package -> package > +++ obfuscatorPackageMap.put("se/hirt/jmc/tutorial/hotmethods", "de/docware/ms/foo"); > Map> obfuscatorClassMethodsMap = new HashMap>(); // (class, obfuscated method) -> method > return new Deobfuscator(obfuscatorClassMap, obfuscatorPackageMap, obfuscatorClassMethodsMap); > } @jpbempel A happy new to year to you and everyone of the JMC team :-) Yes, that's very obvious, once I replaced the package too, the error was gone and I could see the replacement effect inside JMC. I should now be able to complete my code. I will provide a new PR for review in a while. Thanks a lot! ------------- PR: https://git.openjdk.java.net/jmc/pull/333 From duke at openjdk.java.net Sun Jan 2 17:57:12 2022 From: duke at openjdk.java.net (Michael =?UTF-8?B?U8O8ZGthbXA=?=) Date: Sun, 2 Jan 2022 17:57:12 GMT Subject: RFR: 7439: Introduced IConstantPoolExtension for Constant Pools [v6] In-Reply-To: References: Message-ID: On Fri, 26 Nov 2021 20:46:41 GMT, Jean-Philippe Bempel wrote: >> Add extension methods when constants are read, referenced, resolved, constant pools fully resolved and parsing finished to be able for example: >> >> * track constant pool usage inside events >> * replace or translate symbols, method names, etc... like >> de-obfuscations of stack traces > > Jean-Philippe Bempel has updated the pull request incrementally with one additional commit since the last revision: > > remove unused import Back to my real deobfuscation mapping, I found that of course I DID handle the package remapping there, but using real Proguard obfuscation mapping the situation is more complex (or real) than the demo I provided. When I debugged one of these StringIndexOutOfBoundsExceptions, I have this situation in StructTypes.convertNames() **name**=de.docware.apps.etk.base.db.cache.EtkDbsCacheElems, **getPackageName()**=de.docware.apps.etk.base.db.AbstractRevisionChangeSet And these are the relevant entries from the Proguard mapping file. de.docware.apps.etk.base.db.cache.EtkDbsCacheElems -> de.docware.apps.etk.base.d.a.e: de.docware.apps.etk.base.db.AbstractRevisionChangeSet -> de.docware.apps.etk.base.d.a: What I do obviously (or maybe naively) when I find a hit for ""de.docware.apps.etk.base.d.a.e", I assume "de.docware.apps.etk.base.d.a" to be the package name. But as you can see Proguard uses this String for another class mapping. I can only guess but I think this can only work because Proguard obfuscates on byte code level. I haven't observed this problem with my existing deobfuscation solution on formatting level. Probably I was just interested in class and methods, and packages had no importance so far - that's why it worked there. When I return to work I will discuss this with a smart colleague, but maybe we are stuck here. ------------- PR: https://git.openjdk.java.net/jmc/pull/333 From duke at openjdk.java.net Sun Jan 2 21:00:19 2022 From: duke at openjdk.java.net (Martin Skarsaune) Date: Sun, 2 Jan 2022 21:00:19 GMT Subject: RFR: 7455: Add support for jolokia JMX service connection [v7] In-Reply-To: References: Message-ID: On Thu, 11 Nov 2021 09:11:21 GMT, Martin Skarsaune wrote: >> Martin Skarsaune has updated the pull request incrementally with one additional commit since the last revision: >> >> Review corrections: Javadoc and refactoring attempt to use local operation info > > application/org.openjdk.jmc.jolokia/pom.xml line 64: > >> 62: >> 63: >> 64: org.apache.maven.plugins > > Sooo .... I am not sure about the preferred way to pull in external dependencies. I can add that both jolokia libraries come as shaded jars with some OSGi packaging, but I do not know enough about that to say whether that would be a workable or better solution. These are quite new components, so we can probably modify the OSGI packaging in Jolokia going forwards if needed. > POM: https://github.com/rhuss/jolokia/blob/556b58e63a125fb79d516d7f7833e22270f591b0/client/jmx-adapter/pom.xml#L129 > Artifact: https://repo1.maven.org/maven2/org/jolokia/jolokia-jmx-adapter/1.7.0/jolokia-jmx-adapter-1.7.0-standalone.jar I'm working in a separate branch to expose the dependencies via releng/thirdparty, but have not been able to make it work yet. ------------- PR: https://git.openjdk.java.net/jmc/pull/332 From schaturvedi at openjdk.java.net Wed Jan 5 19:21:38 2022 From: schaturvedi at openjdk.java.net (Suchita Chaturvedi) Date: Wed, 5 Jan 2022 19:21:38 GMT Subject: RFR: 7493: Update versions and copyright on Update site pages Message-ID: This PR updates the copyright year and Eclipse pre-requisite version. ------------- Commit messages: - 7493: Update versions and copyright on Update site pages - 7493: Update versions and copyright on Update site pages Changes: https://git.openjdk.java.net/jmc/pull/346/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=346&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7493 Stats: 9 lines in 4 files changed: 1 ins; 0 del; 8 mod Patch: https://git.openjdk.java.net/jmc/pull/346.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/346/head:pull/346 PR: https://git.openjdk.java.net/jmc/pull/346 From hirt at openjdk.java.net Wed Jan 5 21:54:21 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Wed, 5 Jan 2022 21:54:21 GMT Subject: RFR: 7493: Update versions and copyright on Update site pages In-Reply-To: References: Message-ID: On Wed, 5 Jan 2022 19:15:52 GMT, Suchita Chaturvedi wrote: > This PR updates the copyright year and Eclipse pre-requisite version. Marked as reviewed by hirt (Lead). ------------- PR: https://git.openjdk.java.net/jmc/pull/346 From schaturvedi at openjdk.java.net Wed Jan 5 22:44:56 2022 From: schaturvedi at openjdk.java.net (Suchita Chaturvedi) Date: Wed, 5 Jan 2022 22:44:56 GMT Subject: git: openjdk/jmc: 7493: Update versions and copyright on Update site pages Message-ID: <70d87b4e-5a85-403b-99e0-c43e70e7fc83@openjdk.org> Changeset: f077a406 Author: Suchita Chaturvedi Date: 2022-01-05 22:44:29 +0000 URL: https://git.openjdk.java.net/jmc/commit/f077a406946ccab1ca1f3a09e36ace76cda3243c 7493: Update versions and copyright on Update site pages Reviewed-by: hirt ! application/org.openjdk.jmc.updatesite.ide/src/main/resources/index.html ! application/org.openjdk.jmc.updatesite.ide/src/main/resources/run-on-jdk-instructions/index.html ! application/org.openjdk.jmc.updatesite.ide/src/main/resources/update-site-instructions/index.html ! application/org.openjdk.jmc.updatesite.rcp/src/main/resources/index.html From duke at openjdk.java.net Sun Jan 9 15:08:45 2022 From: duke at openjdk.java.net (Alex Ciminian) Date: Sun, 9 Jan 2022 15:08:45 GMT Subject: RFR: 7494: Unable to view JMC Help Contents Message-ID: This PR fixes a problem that makes all JMC help pages fail. We use the eclipse help plugin, it plugin starts a web server which renders the XML content in the docs plugin via JSP. When the user clicks help in the JMC UI they are sent to the browser, which tries to render one of these JSP pages. In #306 we introduced new dependencies on multiple Jetty packages so we can run a websocket server inside JMC. After these changes we notice that the help pages fail to render with the following error: javax.servlet.ServletException: non-HTTP request or response at javax.servlet.http.HttpServlet.service(HttpServlet.java:578) at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:308) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:508) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) This is the code that throws the exception: @Override public void service(ServletRequest req, ServletResponse res) throws ServletException, IOException { HttpServletRequest request; HttpServletResponse response; if (!(req instanceof HttpServletRequest && res instanceof HttpServletResponse)) { throw new ServletException("non-HTTP request or response"); } request = (HttpServletRequest) req; response = (HttpServletResponse) res; service(request, response); } The help plugin has Jetty as a transitive dependency so it's likely this error is caused by the new `servlet-api` dependency that we've introduced. Using the debugger, we can set a breakpoint before the exception is thrown and we can inspect `req` and `res` to see why the `instanceof` check fails. The result of this is very strange: Screenshot 2022-01-08 at 18 05 43 I don't understand why this fails here, since we can see with reflection that `req` implements the expected `javax.servlet.http.HttpServletRequest` interface. It's likely this is because we have two `servlet-api` bundles loaded, `org.eclipse.jetty.servlet-api` (explicit dependency of `flightrecorder.ui`) and `jakarta.servlet-api` (transitive dependency of the help plugin). I also don't understand if it's possible that `instanceof` fails because it tries to compare `javax.servlet.http.HttpServletRequest` loaded from the different bundles, given that the package and interface names are identical. Regardless of the root cause, removing the explicit dependency on `org.eclipse.jetty.servlet-api` from the target platform and depending on `jakarta.servlet-api` in the `flightrecorder.ui` manifest fixes the issue. Now help pages load successfully and the websocket server works as before. ------------- Commit messages: - Remove dependency on jetty.servlet-api, use jakarta instead Changes: https://git.openjdk.java.net/jmc/pull/347/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=347&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7494 Stats: 6 lines in 6 files changed: 0 ins; 5 del; 1 mod Patch: https://git.openjdk.java.net/jmc/pull/347.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/347/head:pull/347 PR: https://git.openjdk.java.net/jmc/pull/347 From hirt at openjdk.java.net Sun Jan 9 17:53:30 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Sun, 9 Jan 2022 17:53:30 GMT Subject: RFR: 7494: Unable to view JMC Help Contents In-Reply-To: References: Message-ID: On Sun, 9 Jan 2022 15:04:38 GMT, Alex Ciminian wrote: > This PR fixes a problem that makes all JMC help pages fail. > > We use the eclipse help plugin, it plugin starts a web server which renders the XML content in the docs plugin via JSP. When the user clicks help in the JMC UI they are sent to the browser, which tries to render one of these JSP pages. > > In #306 we introduced new dependencies on multiple Jetty packages so we can run a websocket server inside JMC. After these changes we notice that the help pages fail to render with the following error: > > > javax.servlet.ServletException: non-HTTP request or response > at javax.servlet.http.HttpServlet.service(HttpServlet.java:578) > at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:308) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:508) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) > > > This is the code that throws the exception: > > > @Override > public void service(ServletRequest req, ServletResponse res) throws ServletException, IOException { > HttpServletRequest request; > HttpServletResponse response; > > if (!(req instanceof HttpServletRequest && res instanceof HttpServletResponse)) { > throw new ServletException("non-HTTP request or response"); > } > > request = (HttpServletRequest) req; > response = (HttpServletResponse) res; > > service(request, response); > } > > > The help plugin has Jetty as a transitive dependency so it's likely this error is caused by the new `servlet-api` dependency that we've introduced. Using the debugger, we can set a breakpoint before the exception is thrown and we can inspect `req` and `res` to see why the `instanceof` check fails. The result of this is very strange: > > Screenshot 2022-01-08 at 18 05 43 > > I don't understand why this fails here, since we can see with reflection that `req` implements the expected `javax.servlet.http.HttpServletRequest` interface. It's likely this is because we have two `servlet-api` bundles loaded, `org.eclipse.jetty.servlet-api` (explicit dependency of `flightrecorder.ui`) and `jakarta.servlet-api` (transitive dependency of the help plugin). > > I also don't understand if it's possible that `instanceof` fails because it tries to compare `javax.servlet.http.HttpServletRequest` loaded from the different bundles, given that the package and interface names are identical. > > Regardless of the root cause, removing the explicit dependency on `org.eclipse.jetty.servlet-api` from the target platform and depending on `jakarta.servlet-api` in the `flightrecorder.ui` manifest fixes the issue. Now help pages load successfully and the websocket server works as before. Marked as reviewed by hirt (Lead). ------------- PR: https://git.openjdk.java.net/jmc/pull/347 From duke at openjdk.java.net Sun Jan 9 21:48:01 2022 From: duke at openjdk.java.net (Martin Skarsaune) Date: Sun, 9 Jan 2022 21:48:01 GMT Subject: RFR: 7455: Add support for jolokia JMX service connection [v8] In-Reply-To: References: Message-ID: > Setting back for review. The azure problem requires a fix in Jolokia. > > Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol. Martin Skarsaune has updated the pull request incrementally with two additional commits since the last revision: - Merge pull request #1 from skarsaune/jolokia-dependencies-via-thirdparty JMC-7455: Use third party to pull inn Jolokia modules - JMC-7455: Use third party to pull inn Jolokia modules ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/332/files - new: https://git.openjdk.java.net/jmc/pull/332/files/800a31d5..d64cb38a Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=332&range=07 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=332&range=06-07 Stats: 91 lines in 10 files changed: 30 ins; 57 del; 4 mod Patch: https://git.openjdk.java.net/jmc/pull/332.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/332/head:pull/332 PR: https://git.openjdk.java.net/jmc/pull/332 From duke at openjdk.java.net Mon Jan 10 11:01:32 2022 From: duke at openjdk.java.net (Alex Ciminian) Date: Mon, 10 Jan 2022 11:01:32 GMT Subject: RFR: 7494: Unable to view JMC Help Contents In-Reply-To: References: Message-ID: On Sun, 9 Jan 2022 15:04:38 GMT, Alex Ciminian wrote: > This PR fixes a problem that makes all JMC help pages fail. > > We use the eclipse help plugin, it plugin starts a web server which renders the XML content in the docs plugin via JSP. When the user clicks help in the JMC UI they are sent to the browser, which tries to render one of these JSP pages. > > In #306 we introduced new dependencies on multiple Jetty packages so we can run a websocket server inside JMC. After these changes we notice that the help pages fail to render with the following error: > > > javax.servlet.ServletException: non-HTTP request or response > at javax.servlet.http.HttpServlet.service(HttpServlet.java:578) > at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:308) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:508) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) > > > This is the code that throws the exception: > > > @Override > public void service(ServletRequest req, ServletResponse res) throws ServletException, IOException { > HttpServletRequest request; > HttpServletResponse response; > > if (!(req instanceof HttpServletRequest && res instanceof HttpServletResponse)) { > throw new ServletException("non-HTTP request or response"); > } > > request = (HttpServletRequest) req; > response = (HttpServletResponse) res; > > service(request, response); > } > > > The help plugin has Jetty as a transitive dependency so it's likely this error is caused by the new `servlet-api` dependency that we've introduced. Using the debugger, we can set a breakpoint before the exception is thrown and we can inspect `req` and `res` to see why the `instanceof` check fails. The result of this is very strange: > > Screenshot 2022-01-08 at 18 05 43 > > I don't understand why this fails here, since we can see with reflection that `req` implements the expected `javax.servlet.http.HttpServletRequest` interface. It's likely this is because we have two `servlet-api` bundles loaded, `org.eclipse.jetty.servlet-api` (explicit dependency of `flightrecorder.ui`) and `jakarta.servlet-api` (transitive dependency of the help plugin). > > I also don't understand if it's possible that `instanceof` fails because it tries to compare `javax.servlet.http.HttpServletRequest` loaded from the different bundles, given that the package and interface names are identical. > > Regardless of the root cause, removing the explicit dependency on `org.eclipse.jetty.servlet-api` from the target platform and depending on `jakarta.servlet-api` in the `flightrecorder.ui` manifest fixes the issue. Now help pages load successfully and the websocket server works as before. Since the ticket mentioned the help pages didn't work if we run JMC with JDK 17, I tried it out. I could reproduce it, here is the error: org.apache.jasper.JasperException: PWC6033: Error in Javac compilation for JSP PWC6197: An error occurred at line: 41 in the jsp file: /index.jsp PWC6199: Generated servlet error: System cannot be resolved at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:129) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:299) at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:392) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:453) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:625) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374) I didn't know how to open the jsp in eclipse so I couldn't play with it there, but looking [at the source](https://git.eclipse.org/c/platform/eclipse.platform.ua.git/tree/org.eclipse.help.webapp/index.jsp) it seems that because of the `System.getProperty` call the JSP fails to compile. Searching online for similar problems, I found [this issue](https://github.com/OpenLiberty/open-liberty/issues/18043) which suggests upgrading JDT (and specifically the eclipse compiler) might fix it. ------------- PR: https://git.openjdk.java.net/jmc/pull/347 From aptmac at openjdk.java.net Mon Jan 10 15:37:32 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Mon, 10 Jan 2022 15:37:32 GMT Subject: RFR: 7494: Unable to view JMC Help Contents In-Reply-To: References: Message-ID: On Sun, 9 Jan 2022 15:04:38 GMT, Alex Ciminian wrote: > This PR fixes a problem that makes all JMC help pages fail. > > We use the eclipse help plugin, it plugin starts a web server which renders the XML content in the docs plugin via JSP. When the user clicks help in the JMC UI they are sent to the browser, which tries to render one of these JSP pages. > > In #306 we introduced new dependencies on multiple Jetty packages so we can run a websocket server inside JMC. After these changes we notice that the help pages fail to render with the following error: > > > javax.servlet.ServletException: non-HTTP request or response > at javax.servlet.http.HttpServlet.service(HttpServlet.java:578) > at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:308) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:508) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) > > > This is the code that throws the exception: > > > @Override > public void service(ServletRequest req, ServletResponse res) throws ServletException, IOException { > HttpServletRequest request; > HttpServletResponse response; > > if (!(req instanceof HttpServletRequest && res instanceof HttpServletResponse)) { > throw new ServletException("non-HTTP request or response"); > } > > request = (HttpServletRequest) req; > response = (HttpServletResponse) res; > > service(request, response); > } > > > The help plugin has Jetty as a transitive dependency so it's likely this error is caused by the new `servlet-api` dependency that we've introduced. Using the debugger, we can set a breakpoint before the exception is thrown and we can inspect `req` and `res` to see why the `instanceof` check fails. The result of this is very strange: > > Screenshot 2022-01-08 at 18 05 43 > > I don't understand why this fails here, since we can see with reflection that `req` implements the expected `javax.servlet.http.HttpServletRequest` interface. It's likely this is because we have two `servlet-api` bundles loaded, `org.eclipse.jetty.servlet-api` (explicit dependency of `flightrecorder.ui`) and `jakarta.servlet-api` (transitive dependency of the help plugin). > > I also don't understand if it's possible that `instanceof` fails because it tries to compare `javax.servlet.http.HttpServletRequest` loaded from the different bundles, given that the package and interface names are identical. > > Regardless of the root cause, removing the explicit dependency on `org.eclipse.jetty.servlet-api` from the target platform and depending on `jakarta.servlet-api` in the `flightrecorder.ui` manifest fixes the issue. Now help pages load successfully and the websocket server works as before. Marked as reviewed by aptmac (Committer). ------------- PR: https://git.openjdk.java.net/jmc/pull/347 From aptmac at openjdk.java.net Mon Jan 10 15:42:34 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Mon, 10 Jan 2022 15:42:34 GMT Subject: RFR: 7494: Unable to view JMC Help Contents In-Reply-To: References: Message-ID: On Mon, 10 Jan 2022 10:57:37 GMT, Alex Ciminian wrote: > I didn't know how to open the jsp in eclipse so I couldn't play with it there, but looking [at the source](https://git.eclipse.org/c/platform/eclipse.platform.ua.git/tree/org.eclipse.help.webapp/index.jsp) it seems that because of the `System.getProperty` call the JSP fails to compile. Searching online for similar problems, I found [this issue](https://github.com/OpenLiberty/open-liberty/issues/18043) which suggests upgrading JDT (and specifically the eclipse compiler) might fix it. Guru had opened an Eclipse bug for JDT explaining our issue [[0]](https://bugs.eclipse.org/bugs/show_bug.cgi?id=574937), there hasn't been a lot of comments on it recently though. Interesting that the update to JDT 3.26.0 fixed the issue for open-library, we're currently consuming 3.18 via 2021-06 [[1]](https://download.eclipse.org/releases/2021-06/202106161001/features/) (and it looks like even through to 2021-12 the same version will be used). [0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=574937 [1] https://download.eclipse.org/releases/2021-06/202106161001/features/ ------------- PR: https://git.openjdk.java.net/jmc/pull/347 From aptmac at openjdk.java.net Mon Jan 10 16:03:54 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Mon, 10 Jan 2022 16:03:54 GMT Subject: RFR: 7473: Unable to view constants in constant pool page. Message-ID: <0DhRaAeNY4K2yS-M-joSEw6s8rokuzw3JIA3xfCdra4=.4276607c-f0cd-43e0-b1dd-b9421859bb8e@github.com> This PR addresses JMC-7473 [[0]](https://bugs.openjdk.java.net/browse/JMC-7473), in which the Constant Pools page throws an exception and does not display. The issue here is in ParserStats, and happens if the stacktrace object doesn't have any frames - but there is a retrieval for the first frame. Before: ![2022-01-10-105031_790x151_scrot](https://user-images.githubusercontent.com/10425301/148796099-b32c4802-7b12-4489-ab09-0aa65a73cea9.png) After: ![2022-01-10-105044_668x458_scrot](https://user-images.githubusercontent.com/10425301/148796118-d066f332-d0a3-4982-9502-b26efd2ef01b.png) ------------- Commit messages: - 7473: Unable to view constants in constant pool page Changes: https://git.openjdk.java.net/jmc/pull/348/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=348&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7473 Stats: 9 lines in 1 file changed: 3 ins; 0 del; 6 mod Patch: https://git.openjdk.java.net/jmc/pull/348.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/348/head:pull/348 PR: https://git.openjdk.java.net/jmc/pull/348 From aptmac at openjdk.java.net Mon Jan 10 16:26:02 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Mon, 10 Jan 2022 16:26:02 GMT Subject: RFR: 7473: Unable to view constants in constant pool page. [v2] In-Reply-To: <0DhRaAeNY4K2yS-M-joSEw6s8rokuzw3JIA3xfCdra4=.4276607c-f0cd-43e0-b1dd-b9421859bb8e@github.com> References: <0DhRaAeNY4K2yS-M-joSEw6s8rokuzw3JIA3xfCdra4=.4276607c-f0cd-43e0-b1dd-b9421859bb8e@github.com> Message-ID: > This PR addresses JMC-7473 [[0]](https://bugs.openjdk.java.net/browse/JMC-7473), in which the Constant Pools page throws an exception and does not display. The issue here is in ParserStats, and happens if the stacktrace object doesn't have any frames - but there is a retrieval for the first frame. > > Before: > ![2022-01-10-105031_790x151_scrot](https://user-images.githubusercontent.com/10425301/148796099-b32c4802-7b12-4489-ab09-0aa65a73cea9.png) > > After: > ![2022-01-10-105044_668x458_scrot](https://user-images.githubusercontent.com/10425301/148796118-d066f332-d0a3-4982-9502-b26efd2ef01b.png) Alex Macdonald has updated the pull request incrementally with one additional commit since the last revision: spotless ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/348/files - new: https://git.openjdk.java.net/jmc/pull/348/files/80e49e19..b21b4f4c Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=348&range=01 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=348&range=00-01 Stats: 2 lines in 1 file changed: 1 ins; 0 del; 1 mod Patch: https://git.openjdk.java.net/jmc/pull/348.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/348/head:pull/348 PR: https://git.openjdk.java.net/jmc/pull/348 From aptmac at openjdk.java.net Mon Jan 10 16:55:35 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Mon, 10 Jan 2022 16:55:35 GMT Subject: RFR: 7482: Confusing display of stack traces when selecting event types with no events In-Reply-To: References: Message-ID: <2al9RiLiuBTl0ZC8-_2mzhmQ2oVdyScRdXBF_yhj2mk=.f2f7c2ff-9d05-47a4-9cd1-e7299ad54858@github.com> On Wed, 29 Dec 2021 16:48:22 GMT, Jean-Philippe Bempel wrote: > ?th no events > > In EventBrowser page, when there is no selection all events are > considered but if there is a selection we filtered events based on > this selection event if there is no events Marked as reviewed by aptmac (Committer). ------------- PR: https://git.openjdk.java.net/jmc/pull/344 From duke at openjdk.java.net Mon Jan 10 17:30:33 2022 From: duke at openjdk.java.net (Alex Ciminian) Date: Mon, 10 Jan 2022 17:30:33 GMT Subject: Integrated: 7494: Unable to view JMC Help Contents In-Reply-To: References: Message-ID: On Sun, 9 Jan 2022 15:04:38 GMT, Alex Ciminian wrote: > This PR fixes a problem that makes all JMC help pages fail. > > We use the eclipse help plugin, it plugin starts a web server which renders the XML content in the docs plugin via JSP. When the user clicks help in the JMC UI they are sent to the browser, which tries to render one of these JSP pages. > > In #306 we introduced new dependencies on multiple Jetty packages so we can run a websocket server inside JMC. After these changes we notice that the help pages fail to render with the following error: > > > javax.servlet.ServletException: non-HTTP request or response > at javax.servlet.http.HttpServlet.service(HttpServlet.java:578) > at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:308) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:508) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) > > > This is the code that throws the exception: > > > @Override > public void service(ServletRequest req, ServletResponse res) throws ServletException, IOException { > HttpServletRequest request; > HttpServletResponse response; > > if (!(req instanceof HttpServletRequest && res instanceof HttpServletResponse)) { > throw new ServletException("non-HTTP request or response"); > } > > request = (HttpServletRequest) req; > response = (HttpServletResponse) res; > > service(request, response); > } > > > The help plugin has Jetty as a transitive dependency so it's likely this error is caused by the new `servlet-api` dependency that we've introduced. Using the debugger, we can set a breakpoint before the exception is thrown and we can inspect `req` and `res` to see why the `instanceof` check fails. The result of this is very strange: > > Screenshot 2022-01-08 at 18 05 43 > > I don't understand why this fails here, since we can see with reflection that `req` implements the expected `javax.servlet.http.HttpServletRequest` interface. It's likely this is because we have two `servlet-api` bundles loaded, `org.eclipse.jetty.servlet-api` (explicit dependency of `flightrecorder.ui`) and `jakarta.servlet-api` (transitive dependency of the help plugin). > > I also don't understand if it's possible that `instanceof` fails because it tries to compare `javax.servlet.http.HttpServletRequest` loaded from the different bundles, given that the package and interface names are identical. > > Regardless of the root cause, removing the explicit dependency on `org.eclipse.jetty.servlet-api` from the target platform and depending on `jakarta.servlet-api` in the `flightrecorder.ui` manifest fixes the issue. Now help pages load successfully and the websocket server works as before. This pull request has now been integrated. Changeset: b65e3512 Author: Alex Ciminian Committer: Marcus Hirt URL: https://git.openjdk.java.net/jmc/commit/b65e3512c86ed1f59e26c08fc817079532d10752 Stats: 6 lines in 6 files changed: 0 ins; 5 del; 1 mod 7494: Unable to view JMC Help Contents Reviewed-by: hirt, aptmac ------------- PR: https://git.openjdk.java.net/jmc/pull/347 From hirt at openjdk.java.net Mon Jan 10 19:44:32 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Mon, 10 Jan 2022 19:44:32 GMT Subject: RFR: 7482: Confusing display of stack traces when selecting event types with no events In-Reply-To: References: Message-ID: On Wed, 29 Dec 2021 16:48:22 GMT, Jean-Philippe Bempel wrote: > ?th no events > > In EventBrowser page, when there is no selection all events are > considered but if there is a selection we filtered events based on > this selection event if there is no events @jpbempel - this is ready to integrate - @aptmac is a reviewer now. :) ------------- PR: https://git.openjdk.java.net/jmc/pull/344 From jpbempel at openjdk.java.net Mon Jan 10 21:45:33 2022 From: jpbempel at openjdk.java.net (Jean-Philippe Bempel) Date: Mon, 10 Jan 2022 21:45:33 GMT Subject: RFR: 7473: Unable to view constants in constant pool page. [v2] In-Reply-To: References: <0DhRaAeNY4K2yS-M-joSEw6s8rokuzw3JIA3xfCdra4=.4276607c-f0cd-43e0-b1dd-b9421859bb8e@github.com> Message-ID: On Mon, 10 Jan 2022 16:26:02 GMT, Alex Macdonald wrote: >> This PR addresses JMC-7473 [[0]](https://bugs.openjdk.java.net/browse/JMC-7473), in which the Constant Pools page throws an exception and does not display. The issue here is in ParserStats, and happens if the stacktrace object doesn't have any frames - but there is a retrieval for the first frame. >> >> Before: >> ![2022-01-10-105031_790x151_scrot](https://user-images.githubusercontent.com/10425301/148796099-b32c4802-7b12-4489-ab09-0aa65a73cea9.png) >> >> After: >> ![2022-01-10-105044_668x458_scrot](https://user-images.githubusercontent.com/10425301/148796118-d066f332-d0a3-4982-9502-b26efd2ef01b.png) > > Alex Macdonald has updated the pull request incrementally with one additional commit since the last revision: > > spotless Marked as reviewed by jpbempel (Committer). ------------- PR: https://git.openjdk.java.net/jmc/pull/348 From jpbempel at openjdk.java.net Mon Jan 10 21:47:32 2022 From: jpbempel at openjdk.java.net (Jean-Philippe Bempel) Date: Mon, 10 Jan 2022 21:47:32 GMT Subject: Integrated: 7482: Confusing display of stack traces when selecting event types with no events In-Reply-To: References: Message-ID: On Wed, 29 Dec 2021 16:48:22 GMT, Jean-Philippe Bempel wrote: > ?th no events > > In EventBrowser page, when there is no selection all events are > considered but if there is a selection we filtered events based on > this selection event if there is no events This pull request has now been integrated. Changeset: ce10e3f9 Author: Jean-Philippe Bempel URL: https://git.openjdk.java.net/jmc/commit/ce10e3f99d7644f14099bde14be7cff74e5f8b85 Stats: 29 lines in 2 files changed: 28 ins; 0 del; 1 mod 7482: Confusing display of stack traces when selecting event types with no events Reviewed-by: aptmac ------------- PR: https://git.openjdk.java.net/jmc/pull/344 From duke at openjdk.java.net Tue Jan 11 05:33:01 2022 From: duke at openjdk.java.net (Martin Skarsaune) Date: Tue, 11 Jan 2022 05:33:01 GMT Subject: RFR: 7455: Add support for jolokia JMX service connection [v9] In-Reply-To: References: Message-ID: > Setting back for review. The azure problem requires a fix in Jolokia. > > Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol. Martin Skarsaune has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 12 commits: - JMC-7455: Use third party to pull inn Jolokia modules - Review corrections: Javadoc and refactoring attempt to use local operation info - Removed -XstartOnFirstThread as it is not valid for some JVMs - Used spotbugs to format more code - Used spotbugs to format according to convention - json.simple is needed by kubernetes plugin downstream - Adding test plugin for Jolokia - Revert unwanted change unrelated to new plugins - Added copyright notices. Removed author tag and meaningless comments - No reason more than Java 8 should be required - ... and 2 more: https://git.openjdk.java.net/jmc/compare/f077a406...da30ca75 ------------- Changes: https://git.openjdk.java.net/jmc/pull/332/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=332&range=08 Stats: 3140 lines in 53 files changed: 3140 ins; 0 del; 0 mod Patch: https://git.openjdk.java.net/jmc/pull/332.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/332/head:pull/332 PR: https://git.openjdk.java.net/jmc/pull/332 From duke at openjdk.java.net Tue Jan 11 05:41:48 2022 From: duke at openjdk.java.net (Martin Skarsaune) Date: Tue, 11 Jan 2022 05:41:48 GMT Subject: RFR: 7455: Add support for jolokia JMX service connection [v10] In-Reply-To: References: Message-ID: > Setting back for review. The azure problem requires a fix in Jolokia. > > Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol. Martin Skarsaune has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 12 commits: - JMC-7455: Use third party to pull inn Jolokia modules - Review corrections: Javadoc and refactoring attempt to use local operation info - Removed -XstartOnFirstThread as it is not valid for some JVMs - Used spotbugs to format more code - Used spotbugs to format according to convention - json.simple is needed by kubernetes plugin downstream - Adding test plugin for Jolokia - Revert unwanted change unrelated to new plugins - Added copyright notices. Removed author tag and meaningless comments - No reason more than Java 8 should be required - ... and 2 more: https://git.openjdk.java.net/jmc/compare/ce10e3f9...eb20109f ------------- Changes: https://git.openjdk.java.net/jmc/pull/332/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=332&range=09 Stats: 3140 lines in 53 files changed: 3140 ins; 0 del; 0 mod Patch: https://git.openjdk.java.net/jmc/pull/332.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/332/head:pull/332 PR: https://git.openjdk.java.net/jmc/pull/332 From schaturvedi at openjdk.java.net Tue Jan 11 21:34:47 2022 From: schaturvedi at openjdk.java.net (Suchita Chaturvedi) Date: Tue, 11 Jan 2022 21:34:47 GMT Subject: RFR: 7485: JMC Application, Plugins and License Copyright year requires update Message-ID: This PR addresses the copyright update task for JMC 8.2 release. ------------- Commit messages: - 7485: JMC Application, Plugins and License Copyright year requires update Changes: https://git.openjdk.java.net/jmc/pull/350/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=350&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7485 Stats: 575 lines in 311 files changed: 0 ins; 0 del; 575 mod Patch: https://git.openjdk.java.net/jmc/pull/350.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/350/head:pull/350 PR: https://git.openjdk.java.net/jmc/pull/350 From hirt at openjdk.java.net Wed Jan 12 02:55:33 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Wed, 12 Jan 2022 02:55:33 GMT Subject: RFR: 7485: JMC Application, Plugins and License Copyright year requires update In-Reply-To: References: Message-ID: On Tue, 11 Jan 2022 21:29:26 GMT, Suchita Chaturvedi wrote: > This PR addresses the copyright update task for JMC 8.2 release. Changes requested by hirt (Lead). application/org.openjdk.jmc.browser.jdp/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.browser/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.console.ui.mbeanbrowser/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.console.ui.notification/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.console.ui.subscriptions/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.console.ui/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.docs/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.flightrecorder.controlpanel.ui/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.flightrecorder.pde/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.flightrecorder.ui/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.ide.jdt/plugin.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2022, Oracle and/or its affiliates. All rights reserved. This file didn't change, hence the copyright year should not change. application/org.openjdk.jmc.ide.ui/html/img_text/open_method_context_01.htm line 4: > 2: "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > 3: This bug is closed, does that means it's again broken. ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From duke at openjdk.java.net Thu Jan 20 18:11:54 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Thu, 20 Jan 2022 18:11:54 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v5] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Thu, 20 Jan 2022 18:01:08 GMT, Brice Dutheil wrote: >> Johannes Bechberger has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains four commits: >> >> - Add JDK 17 to CI >> - Fix --add-exports >> >> Multiple --add-exports seem to require a flag like -version >> in between. >> It maybe related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=544016 >> - Update p2-maven-plugin >> - Bump mockito to run --installCore on JDK 17 > > application/org.openjdk.jmc.browser.attach/pom.xml line 58: > >> 56: --add-exports >> 57: jdk.attach/sun.tools.attach=ALL-UNNAMED >> 58: -version > > This bug is closed, does that means it's again broken. Seems so, but I did not have the time to look into this further. ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From marcus.hirt at datadoghq.com Thu Jan 20 18:26:02 2022 From: marcus.hirt at datadoghq.com (Marcus Hirt) Date: Thu, 20 Jan 2022 19:26:02 +0100 Subject: Remove platforms not supporting AARCH64? In-Reply-To: <032f01d80b9a$47f160a0$d7d421e0$@hirt.se> References: <032f01d80b9a$47f160a0$d7d421e0$@hirt.se> Message-ID: Hi all, Since no one seems to have a problem with this, I'll go ahead with the PR. See: https://github.com/openjdk/jmc/pull/361 Kind regards, Marcus On Mon, Jan 17, 2022 at 1:04 PM Marcus Hirt wrote: > > Hi all (especially vendors), > > > > I'd like to remove the old platforms (not supporting AARCH64). This would > unfortunately mean an exception to our usual support for (at least) the last 4 > Eclipse releases. The old platforms, however, are not really properly > supported today anyways, as you'd need to manually remove the AARCH64 > environment from the main pom to make them build. The simplest would simply be > to remove the platform definitions for <= 2021-03, meaning we'd support > 2021-06, 2021-09 and 2021-12, with 2022-03 being a little bit over a month > away. > > What do you think? Just remove them? Is there any vendor relying on 2021-03 > (or earlier) being available? > > > See: [JMC-7477] JMC8.2 does not build with eclipse 4.19 (21-03) - Java Bug > System > > > > Kind regards, > > Marcus > From hirt at openjdk.java.net Thu Jan 20 20:41:07 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 20:41:07 GMT Subject: RFR: 7477: JMC8.2 does not build with eclipse 4.19 (21-03) [v2] In-Reply-To: References: Message-ID: > This would be a change from our stated intention to support the last four releases, so we may want to hold off until 2021-03 to take this. Marcus Hirt has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: - Merge master - 7477: Removing old platforms ------------- Changes: https://git.openjdk.java.net/jmc/pull/361/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=361&range=01 Stats: 448 lines in 10 files changed: 0 ins; 448 del; 0 mod Patch: https://git.openjdk.java.net/jmc/pull/361.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/361/head:pull/361 PR: https://git.openjdk.java.net/jmc/pull/361 From aptmac at openjdk.java.net Thu Jan 20 20:50:56 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Thu, 20 Jan 2022 20:50:56 GMT Subject: RFR: 7477: JMC8.2 does not build with eclipse 4.19 (21-03) [v2] In-Reply-To: References: Message-ID: On Thu, 20 Jan 2022 20:41:07 GMT, Marcus Hirt wrote: >> This would be a change from our stated intention to support the last four releases, so we may want to hold off until 2021-03 to take this. > > Marcus Hirt has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: > > - Merge master > - 7477: Removing old platforms Marked as reviewed by aptmac (Reviewer). ------------- PR: https://git.openjdk.java.net/jmc/pull/361 From hirt at openjdk.java.net Thu Jan 20 21:34:50 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 21:34:50 GMT Subject: RFR: 7477: JMC8.2 does not build with eclipse 4.19 (21-03) [v2] In-Reply-To: References: Message-ID: On Thu, 20 Jan 2022 20:41:07 GMT, Marcus Hirt wrote: >> This would be a change from our stated intention to support the last four releases, so we may want to hold off until 2021-03 to take this. > > Marcus Hirt has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: > > - Merge master > - 7477: Removing old platforms Hm. It didn't run all checks. I'll redo the merge and see if it happens again. ------------- PR: https://git.openjdk.java.net/jmc/pull/361 From hirt at openjdk.java.net Thu Jan 20 22:21:57 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 22:21:57 GMT Subject: RFR: 7477: JMC8.2 does not build with eclipse 4.19 (21-03) [v2] In-Reply-To: References: Message-ID: On Thu, 20 Jan 2022 20:41:07 GMT, Marcus Hirt wrote: >> This would be a change from our stated intention to support the last four releases, so we may want to hold off until 2021-03 to take this. > > Marcus Hirt has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: > > - Merge master > - 7477: Removing old platforms Something is funny with the workflow. Moving this to #367 instead, and closing this. ------------- PR: https://git.openjdk.java.net/jmc/pull/361 From hirt at openjdk.java.net Thu Jan 20 22:21:57 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 22:21:57 GMT Subject: Withdrawn: 7477: JMC8.2 does not build with eclipse 4.19 (21-03) In-Reply-To: References: Message-ID: On Sun, 16 Jan 2022 14:35:20 GMT, Marcus Hirt wrote: > This would be a change from our stated intention to support the last four releases, so we may want to hold off until 2021-03 to take this. This pull request has been closed without being integrated. ------------- PR: https://git.openjdk.java.net/jmc/pull/361 From hirt at openjdk.java.net Thu Jan 20 22:22:09 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 22:22:09 GMT Subject: RFR: 7477: JMC8.2 does not build with eclipse 4.19 (21-03) Message-ID: Something funny is happening with the workflow. Trying in a separate PR to see if it can be reproduced. ------------- Commit messages: - 7477: Remove old platforms Changes: https://git.openjdk.java.net/jmc/pull/367/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=367&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7477 Stats: 448 lines in 10 files changed: 0 ins; 448 del; 0 mod Patch: https://git.openjdk.java.net/jmc/pull/367.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/367/head:pull/367 PR: https://git.openjdk.java.net/jmc/pull/367 From duke at openjdk.java.net Thu Jan 20 23:33:07 2022 From: duke at openjdk.java.net (mohno007) Date: Thu, 20 Jan 2022 23:33:07 GMT Subject: RFR: 7417: Fix incorrect identifier in result for biased locking revocation rule Message-ID: This PR fixes a wrong placeholder in `BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND_LONG`. `BiasedLockingRevocationRule.java` used `{revokedClasses}` for placeholder identifier but `messages.properties` used `{revokedTypes}`. ------------- Commit messages: - Fix wrong placeholder in BiasedLockingRevocationRule Changes: https://git.openjdk.java.net/jmc/pull/309/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=309&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7417 Stats: 4 lines in 2 files changed: 0 ins; 0 del; 4 mod Patch: https://git.openjdk.java.net/jmc/pull/309.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/309/head:pull/309 PR: https://git.openjdk.java.net/jmc/pull/309 From aptmac at openjdk.java.net Thu Jan 20 23:33:09 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Thu, 20 Jan 2022 23:33:09 GMT Subject: RFR: 7417: Fix incorrect identifier in result for biased locking revocation rule In-Reply-To: References: Message-ID: On Mon, 20 Sep 2021 06:40:14 GMT, mohno007 wrote: > This PR fixes a wrong placeholder in `BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND_LONG`. > > `BiasedLockingRevocationRule.java` used `{revokedClasses}` for placeholder identifier but `messages.properties` used `{revokedTypes}`. Marked as reviewed by aptmac (Reviewer). ------------- PR: https://git.openjdk.java.net/jmc/pull/309 From duke at openjdk.java.net Thu Jan 20 23:33:11 2022 From: duke at openjdk.java.net (mohno007) Date: Thu, 20 Jan 2022 23:33:11 GMT Subject: RFR: 7420: Update Japanese translation for rules Message-ID: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> This PR updates/improves Japanese translation of rules and its descriptions. ## Update * Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. * Support a new placeholder format introduced in `Rule 2.0`. * Use Markdown style link. * Add translations for newly added texts. * Update texts for translation correctness and understandability. * Fix some wordings for understandability. Especially usage of Japanese particle. * Add [Japanese counter word (???)](https://en.wikipedia.org/wiki/Japanese_counter_word) for numeric value. You can see decoded version of `messages_ja` using this script: native2ascii -reverse core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties ------------- Commit messages: - fix copyright text - Update Japanese translation for rules Changes: https://git.openjdk.java.net/jmc/pull/308/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=308&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7420 Stats: 290 lines in 1 file changed: 89 ins; 4 del; 197 mod Patch: https://git.openjdk.java.net/jmc/pull/308.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/308/head:pull/308 PR: https://git.openjdk.java.net/jmc/pull/308 From hirt at openjdk.java.net Thu Jan 20 23:33:10 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 23:33:10 GMT Subject: RFR: 7417: Fix incorrect identifier in result for biased locking revocation rule In-Reply-To: References: Message-ID: On Mon, 20 Sep 2021 06:40:14 GMT, mohno007 wrote: > This PR fixes a wrong placeholder in `BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND_LONG`. > > `BiasedLockingRevocationRule.java` used `{revokedClasses}` for placeholder identifier but `messages.properties` used `{revokedTypes}`. Looks good @mohno007! Please follow the instructions of the bot to get your OCA status set straight. Hi @mohno007! Just checking on how things are going with the OCA. Can I help? @mohno007 / @robilad - any news on the OCA? Hi @robilad & @mohno007 - how is that application coming along? We're starting to ramp down 8.2.0 now. ------------- PR: https://git.openjdk.java.net/jmc/pull/309 From hirt at openjdk.java.net Thu Jan 20 23:33:13 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 23:33:13 GMT Subject: RFR: 7420: Update Japanese translation for rules In-Reply-To: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: On Mon, 20 Sep 2021 04:55:25 GMT, mohno007 wrote: > This PR updates/improves Japanese translation of rules and its descriptions. > > ## Update > > * Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. > * Support a new placeholder format introduced in `Rule 2.0`. > * Use Markdown style link. > * Add translations for newly added texts. > * Update texts for translation correctness and understandability. > * Fix some wordings for understandability. Especially usage of Japanese particle. > * Add [Japanese counter word (???)](https://en.wikipedia.org/wiki/Japanese_counter_word) for numeric value. > > You can see decoded version of `messages_ja` using this script: > > > native2ascii -reverse core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties Thanks @mohno007! Let me know if you need any help with verifying the OCA status! Meanwhile, I've asked a friend in Japan to verify the texts. Hi @davidbuckjp! Any chance you could take a look at this? core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2019, 2020, 2021 Oracle and/or its affiliates. All rights reserved. Only the first and the last year in the range should be in the copyright header. In this case the text should be: Copyright (c) 2018, 2021, Oracle and/or its affiliates. All rights reserved. Note the comma after the end year as well. ------------- PR: https://git.openjdk.java.net/jmc/pull/308 From hdafgard at openjdk.java.net Thu Jan 20 23:33:11 2022 From: hdafgard at openjdk.java.net (Henrik =?UTF-8?B?RGFmZ8OlcmQ=?=) Date: Thu, 20 Jan 2022 23:33:11 GMT Subject: RFR: 7417: Fix incorrect identifier in result for biased locking revocation rule In-Reply-To: References: Message-ID: On Mon, 20 Sep 2021 06:40:14 GMT, mohno007 wrote: > This PR fixes a wrong placeholder in `BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND_LONG`. > > `BiasedLockingRevocationRule.java` used `{revokedClasses}` for placeholder identifier but `messages.properties` used `{revokedTypes}`. Please edit the title to refer to [JMC-7417](https://bugs.openjdk.java.net/browse/JMC-7417) by adding changing the title to "7417:Fix incorrect identifier in result for biased locking revocation rule". And when the OCA status is fixed I'll be happy to approve this PR. ------------- PR: https://git.openjdk.java.net/jmc/pull/309 From duke at openjdk.java.net Thu Jan 20 23:33:14 2022 From: duke at openjdk.java.net (mohno007) Date: Thu, 20 Jan 2022 23:33:14 GMT Subject: RFR: 7420: Update Japanese translation for rules In-Reply-To: References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: On Tue, 21 Sep 2021 22:59:14 GMT, Marcus Hirt wrote: > Let me know if you need any help with verifying the OCA status! I run into a problem with OCA. I submitted the OCA application once but I wanted to change my email address, so I withdrew it and changed my email address. Then I tried to submit the OCA application again, but I got an error which says the GitHub username is already in use. I have already contacted Oracle Support by email and currently waiting for a response. > I've asked a friend in Japan to verify the texts. Thank you. I write Java code but I'm not very familiar with Java internals and its translation, so it would be very helpful if someone could check this translation. > core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties line 2: > >> 1: # >> 2: # Copyright (c) 2018, 2019, 2020, 2021 Oracle and/or its affiliates. All rights reserved. > > Only the first and the last year in the range should be in the copyright header. In this case the text should be: > Copyright (c) 2018, 2021, Oracle and/or its affiliates. All rights reserved. > > Note the comma after the end year as well. I fixed it in 48d36d496f8085da84b434a6842da6009b72bfe1 ------------- PR: https://git.openjdk.java.net/jmc/pull/308 From hirt at openjdk.java.net Thu Jan 20 23:33:15 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 23:33:15 GMT Subject: RFR: 7420: Update Japanese translation for rules In-Reply-To: References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: On Wed, 22 Sep 2021 17:35:03 GMT, mohno007 wrote: > I run into a problem with OCA. > I submitted the OCA application once but I wanted to change my email address, so I withdrew it and changed my email address. > Then I tried to submit the OCA application again, but I got an error which says the GitHub username is already in use. @edvbld - can you help? What's the best way to help @mohno007 proceed with his application? > I run into a problem with OCA. I submitted the OCA application once but I wanted to change my email address, so I withdrew it and changed my email address. Then I tried to submit the OCA application again, but I got an error which says the GitHub username is already in use. > > I have already contacted Oracle Support by email and currently waiting for a response. Have you heard back from Oracle Support yet? Hi @mohno007! Just checking to see how things are going. Did you see @robilad's message? ------------- PR: https://git.openjdk.java.net/jmc/pull/308 From robilad at openjdk.java.net Thu Jan 20 23:33:15 2022 From: robilad at openjdk.java.net (Dalibor Topic) Date: Thu, 20 Jan 2022 23:33:15 GMT Subject: RFR: 7420: Update Japanese translation for rules In-Reply-To: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: On Mon, 20 Sep 2021 04:55:25 GMT, mohno007 wrote: > This PR updates/improves Japanese translation of rules and its descriptions. > > ## Update > > * Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. > * Support a new placeholder format introduced in `Rule 2.0`. > * Use Markdown style link. > * Add translations for newly added texts. > * Update texts for translation correctness and understandability. > * Fix some wordings for understandability. Especially usage of Japanese particle. > * Add [Japanese counter word (???)](https://en.wikipedia.org/wiki/Japanese_counter_word) for numeric value. > > You can see decoded version of `messages_ja` using this script: > > > native2ascii -reverse core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties Hi, please send me an e-Mail at dalibor.topic at oracle.com and I can try to assist you to find a resolution for the OCA issue. ------------- PR: https://git.openjdk.java.net/jmc/pull/308 From duke at openjdk.java.net Thu Jan 20 23:33:17 2022 From: duke at openjdk.java.net (mohno007) Date: Thu, 20 Jan 2022 23:33:17 GMT Subject: RFR: 7420: Update Japanese translation for rules In-Reply-To: References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: <6ebO-oLWnkxTkaYvWRYZjR48Mpol9kCMr9mDkFA1p2A=.802fff76-156e-4259-a30e-f3b5d302056f@github.com> On Mon, 4 Oct 2021 09:12:28 GMT, Marcus Hirt wrote: >>> Let me know if you need any help with verifying the OCA status! >> >> I run into a problem with OCA. >> I submitted the OCA application once but I wanted to change my email address, so I withdrew it and changed my email address. >> Then I tried to submit the OCA application again, but I got an error which says the GitHub username is already in use. >> >> I have already contacted Oracle Support by email and currently waiting for a response. >> >>> I've asked a friend in Japan to verify the texts. >> >> Thank you. >> I write Java code but I'm not very familiar with Java internals and its translation, so it would be very helpful if someone could check this translation. > > Hi @mohno007! Just checking to see how things are going. Did you see @robilad's message? @thegreystone > Hi @mohno007! Just checking to see how things are going. Did you see @robilad's message? Thank you for the notice and sorry for the late reply, I just realized it and send a email. ------------- PR: https://git.openjdk.java.net/jmc/pull/308 From hirt at openjdk.java.net Thu Jan 20 23:33:18 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 23:33:18 GMT Subject: RFR: 7420: Update Japanese translation for rules In-Reply-To: References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: On Fri, 1 Oct 2021 19:36:08 GMT, Dalibor Topic wrote: >> This PR updates/improves Japanese translation of rules and its descriptions. >> >> ## Update >> >> * Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. >> * Support a new placeholder format introduced in `Rule 2.0`. >> * Use Markdown style link. >> * Add translations for newly added texts. >> * Update texts for translation correctness and understandability. >> * Fix some wordings for understandability. Especially usage of Japanese particle. >> * Add [Japanese counter word (???)](https://en.wikipedia.org/wiki/Japanese_counter_word) for numeric value. >> >> You can see decoded version of `messages_ja` using this script: >> >> >> native2ascii -reverse core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties > > Hi, please send me an e-Mail at dalibor.topic at oracle.com and I can try to assist you to find a resolution for the OCA issue. Hi @robilad & @mohno007 - how is that application coming along? We're starting to ramp down 8.2.0 now. ------------- PR: https://git.openjdk.java.net/jmc/pull/308 From duke at openjdk.java.net Thu Jan 20 23:34:14 2022 From: duke at openjdk.java.net (mohno007) Date: Thu, 20 Jan 2022 23:34:14 GMT Subject: RFR: 7421: Update Japanese translation for pages Message-ID: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> This PR updates/improves Japanese translation for pages. Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. You can see decoded version of `messages_ja` using this script: native2ascii -reverse application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties ------------- Commit messages: - Update Japanese translation for pages Changes: https://git.openjdk.java.net/jmc/pull/310/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=310&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7421 Stats: 73 lines in 1 file changed: 61 ins; 2 del; 10 mod Patch: https://git.openjdk.java.net/jmc/pull/310.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/310/head:pull/310 PR: https://git.openjdk.java.net/jmc/pull/310 From aptmac at openjdk.java.net Thu Jan 20 23:34:16 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Thu, 20 Jan 2022 23:34:16 GMT Subject: RFR: 7421: Update Japanese translation for pages In-Reply-To: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> References: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> Message-ID: On Mon, 20 Sep 2021 12:56:50 GMT, mohno007 wrote: > This PR updates/improves Japanese translation for pages. > > Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. > > You can see decoded version of `messages_ja` using this script: > > > native2ascii -reverse application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties Marked as reviewed by aptmac (Reviewer). application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties line 514: > 512: ThreadsPage_EDIT_LANES=\u30B9\u30EC\u30C3\u30C9\u30FB\u30EC\u30FC\u30F3\u306E\u7DE8\u96C6 > 513: ThreadsPage_FOLD_CHART_TOOLTIP=\u30C1\u30E3\u30FC\u30C8\u3092\u6298\u308A\u305F\u305F\u3080 > 514: ThreadsPage_FOLD_TABLE_TOOLTIP=\u30C6\u30FC\u30D6\u30EB\u3092\u6298\u308A\u305F\u305F\u3080 Out of curiosity, how come this string uses "????" for table instead of "?" ? ------------- PR: https://git.openjdk.java.net/jmc/pull/310 From hirt at openjdk.java.net Thu Jan 20 23:34:17 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Thu, 20 Jan 2022 23:34:17 GMT Subject: RFR: 7421: Update Japanese translation for pages In-Reply-To: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> References: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> Message-ID: <5Xuq57P5Lxv9KlEEYwZ_OB2em03K3_i6_rcmkwFshCM=.268aae9c-9e83-41e8-8e25-0567159c9e59@github.com> On Mon, 20 Sep 2021 12:56:50 GMT, mohno007 wrote: > This PR updates/improves Japanese translation for pages. > > Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. > > You can see decoded version of `messages_ja` using this script: > > > native2ascii -reverse application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties Hi @davidbuckjp! Any chance you could take a look at this? Hi @robilad & @mohno007 - how is that application coming along? We're starting to ramp down 8.2.0 now. Hi @davidbuckjp, any chance you can take a look at this whilst the OCA problems are being looked at? Hi @robilad, @davidbuckjp & @edvbld! Is there anything that can be done to help @mohno007 get his OCA through? We're entering RDP2 for JMC 8.2.0, and I'd really like to take these PRs. Hi @robilad! Any chance the OCA will be processed soon? ------------- PR: https://git.openjdk.java.net/jmc/pull/310 From clanger at openjdk.java.net Fri Jan 21 07:49:50 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Fri, 21 Jan 2022 07:49:50 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v5] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Thu, 20 Jan 2022 18:08:08 GMT, Johannes Bechberger wrote: >> application/org.openjdk.jmc.browser.attach/pom.xml line 58: >> >>> 56: --add-exports >>> 57: jdk.attach/sun.tools.attach=ALL-UNNAMED >>> 58: -version >> >> This bug is closed, does that means it's again broken. > > Seems so, but I did not have the time to look into this further. This is really weird. I'm struggling with the add-eports setting in my build attempts as well. I'm using JDK11. I also find that there's a difference in behavior between maven versions. E.g. maven 3.8.1 behaves slightly better than 3.8.4. But I have to do this kind of changes in several pom files until I get the build to go through. What's your maven versions? ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From duke at openjdk.java.net Fri Jan 21 08:01:52 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 08:01:52 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v5] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Fri, 21 Jan 2022 07:46:34 GMT, Christoph Langer wrote: >> Seems so, but I did not have the time to look into this further. > > This is really weird. I'm struggling with the add-eports setting in my build attempts as well. I'm using JDK11. I also find that there's a difference in behavior between maven versions. E.g. maven 3.8.1 behaves slightly better than 3.8.4. But I have to do this kind of changes in several pom files until I get the build to go through. > What's your maven versions? My version is 3.8.4 which is the current version of maven. But it works for me with JDK 11. So the culprit (in my opinion) is the p2-maven-plugin, which is the only other thing I changed besides the JDK version, or of course, the JDK itself, but this seems to be unlikely. ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From duke at openjdk.java.net Fri Jan 21 08:01:52 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 08:01:52 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v5] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Fri, 21 Jan 2022 07:56:24 GMT, Johannes Bechberger wrote: >> This is really weird. I'm struggling with the add-eports setting in my build attempts as well. I'm using JDK11. I also find that there's a difference in behavior between maven versions. E.g. maven 3.8.1 behaves slightly better than 3.8.4. But I have to do this kind of changes in several pom files until I get the build to go through. >> What's your maven versions? > > My version is 3.8.4 which is the current version of maven. But it works for me with JDK 11. So the culprit (in my opinion) is the p2-maven-plugin, which is the only other thing I changed besides the JDK version, or of course, the JDK itself, but this seems to be unlikely. I have to test the new p2-maven-plugin version with JDK 11. ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From reinhapa at openjdk.java.net Fri Jan 21 08:16:55 2022 From: reinhapa at openjdk.java.net (Patrick Reinhart) Date: Fri, 21 Jan 2022 08:16:55 GMT Subject: RFR: 7537: Build script assumes that Darwin always targets x86_64 In-Reply-To: <2P2V8rPVYzaQKk43iAkOX4GRdpkHiLMX9RBoS7-_3LY=.e6267ea2-f1bb-44cb-849e-dafe0c345ad7@github.com> References: <2P2V8rPVYzaQKk43iAkOX4GRdpkHiLMX9RBoS7-_3LY=.e6267ea2-f1bb-44cb-849e-dafe0c345ad7@github.com> Message-ID: On Thu, 20 Jan 2022 10:38:35 GMT, Johannes Bechberger wrote: > Tested on Mac M1. @thegreystone should we also open an issue for the Windows build script? ------------- PR: https://git.openjdk.java.net/jmc/pull/366 From duke at openjdk.java.net Fri Jan 21 08:23:48 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 08:23:48 GMT Subject: RFR: 7537: Build script assumes that Darwin always targets x86_64 In-Reply-To: <2P2V8rPVYzaQKk43iAkOX4GRdpkHiLMX9RBoS7-_3LY=.e6267ea2-f1bb-44cb-849e-dafe0c345ad7@github.com> References: <2P2V8rPVYzaQKk43iAkOX4GRdpkHiLMX9RBoS7-_3LY=.e6267ea2-f1bb-44cb-849e-dafe0c345ad7@github.com> Message-ID: On Thu, 20 Jan 2022 10:38:35 GMT, Johannes Bechberger wrote: > Tested on Mac M1. my take on it: it is highly unlikely that someone is running a windows on this architecture, as it only seems to be possible inside a VM. ------------- PR: https://git.openjdk.java.net/jmc/pull/366 From duke at openjdk.java.net Fri Jan 21 11:18:55 2022 From: duke at openjdk.java.net (Brice Dutheil) Date: Fri, 21 Jan 2022 11:18:55 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v5] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Fri, 21 Jan 2022 07:58:54 GMT, Johannes Bechberger wrote: >> My version is 3.8.4 which is the current version of maven. But it works for me with JDK 11. So the culprit (in my opinion) is the p2-maven-plugin, which is the only other thing I changed besides the JDK version, or of course, the JDK itself, but this seems to be unlikely. > > It's weird: the problem does not occur on JDK 11 with the newer p2-maven-plugin. So it might the JDK itself? Could it be a tycho issue, again. Tycho overrides many lifecycle of Maven: https://github.com/eclipse/tycho/blob/5c83ecd968eae37aa328020d228c8f03b2a3168c/tycho-maven-plugin/src/main/resources/META-INF/plexus/components.xml#L27-L29 org.eclipse.tycho:tycho-compiler-plugin:${project.version}:compile _By the way tycho 2.6.0 seems to be [around the corner](https://github.com/eclipse/tycho/releases/tag/tycho-2.6.0), I haven't checked the changelog though._ It can't be `p2-maven-plugin` anyway as it is only used to generate a p2 repository (that is used in the `.target` files), and it is only used in `releng/third-party`. ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From hirt at openjdk.java.net Fri Jan 21 11:59:07 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 11:59:07 GMT Subject: RFR: 7538: Check in launcher for JVMKeepAlive Message-ID: Helpful for new developers. ------------- Commit messages: - 7538: Check in launcher for JVMKeepAlive Changes: https://git.openjdk.java.net/jmc/pull/368/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=368&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7538 Stats: 19 lines in 1 file changed: 19 ins; 0 del; 0 mod Patch: https://git.openjdk.java.net/jmc/pull/368.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/368/head:pull/368 PR: https://git.openjdk.java.net/jmc/pull/368 From duke at openjdk.java.net Fri Jan 21 12:03:19 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 12:03:19 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v6] In-Reply-To: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: > Tested on Java 11 x86 and aarch64 (azul, but only builds), and on Java 17 x86 and aarch64. Johannes Bechberger has updated the pull request incrementally with one additional commit since the last revision: Add another -version ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/363/files - new: https://git.openjdk.java.net/jmc/pull/363/files/019a32d3..7a77eef1 Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=363&range=05 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=363&range=04-05 Stats: 1 line in 1 file changed: 1 ins; 0 del; 0 mod Patch: https://git.openjdk.java.net/jmc/pull/363.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/363/head:pull/363 PR: https://git.openjdk.java.net/jmc/pull/363 From duke at openjdk.java.net Fri Jan 21 12:06:25 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 12:06:25 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v7] In-Reply-To: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: > Tested on Java 11 x86 and aarch64 (azul, but only builds), and on Java 17 x86 and aarch64. Johannes Bechberger has updated the pull request incrementally with one additional commit since the last revision: Bump javadoc version ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/363/files - new: https://git.openjdk.java.net/jmc/pull/363/files/7a77eef1..db52a27b Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=363&range=06 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=363&range=05-06 Stats: 2 lines in 2 files changed: 0 ins; 0 del; 2 mod Patch: https://git.openjdk.java.net/jmc/pull/363.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/363/head:pull/363 PR: https://git.openjdk.java.net/jmc/pull/363 From hirt at openjdk.java.net Fri Jan 21 12:13:48 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 12:13:48 GMT Subject: RFR: 7421: Update Japanese translation for pages In-Reply-To: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> References: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> Message-ID: On Mon, 20 Sep 2021 12:56:50 GMT, mohno007 wrote: > This PR updates/improves Japanese translation for pages. > > Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. > > You can see decoded version of `messages_ja` using this script: > > > native2ascii -reverse application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties Changes requested by hirt (Lead). application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2021, Oracle and/or its affiliates. All rights reserved. Should update copyright year. ------------- PR: https://git.openjdk.java.net/jmc/pull/310 From hirt at openjdk.java.net Fri Jan 21 12:14:55 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 12:14:55 GMT Subject: RFR: 7417: Fix incorrect identifier in result for biased locking revocation rule In-Reply-To: References: Message-ID: On Mon, 20 Sep 2021 06:40:14 GMT, mohno007 wrote: > This PR fixes a wrong placeholder in `BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND_LONG`. > > `BiasedLockingRevocationRule.java` used `{revokedClasses}` for placeholder identifier but `messages.properties` used `{revokedTypes}`. Changes requested by hirt (Lead). core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/java/org/openjdk/jmc/flightrecorder/rules/jdk/latency/BiasedLockingRevocationRule.java line 116: > 114: MAX_NUMBER_OF_CLASSES_TO_REPORT, FILTERED_CLASSES); > 115: > 116: public static final TypedCollectionResult REVOKED_CLASSES = new TypedCollectionResult<>("revokedClasses", //$NON-NLS-1$ Need to update copyright year. core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages.properties line 77: > 75: BiasedLockingRevocationRule_TEXT_OK=No classes were disabled from participating in biased locking > 76: BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND=Fully revoked classes found. > 77: BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND_LONG=The following classes were disabled from using biased locking: {revokedClasses} Need to update copyright year. ------------- PR: https://git.openjdk.java.net/jmc/pull/309 From duke at openjdk.java.net Fri Jan 21 12:26:55 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 12:26:55 GMT Subject: RFR: 7538: Check in launcher for JVMKeepAlive In-Reply-To: References: Message-ID: <_nGuGqJQDqfO8ShFP8cgB-3tw1Fd8JKsRRgTkYJHLv8=.c3036df6-d866-415c-a228-fa806a5d67c8@github.com> On Fri, 21 Jan 2022 11:54:10 GMT, Marcus Hirt wrote: > Helpful for new developers. Please add a remark to the devguide on when and how to use it. ------------- PR: https://git.openjdk.java.net/jmc/pull/368 From clanger at openjdk.java.net Fri Jan 21 14:21:38 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Fri, 21 Jan 2022 14:21:38 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v7] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Fri, 21 Jan 2022 12:06:25 GMT, Johannes Bechberger wrote: >> Tested on Java 11 x86 and aarch64 (azul, but only builds), and on Java 17 x86 and aarch64. > > Johannes Bechberger has updated the pull request incrementally with one additional commit since the last revision: > > Bump javadoc version The version bumps seem good. I think the GHA workflow has some issues still. I'll continue my investigations regarding the tycho compiler... .github/workflows/validate.yml line 15: > 13: - uses: actions/setup-java at v1 > 14: with: > 15: java-version: {{ matrix.jdk }} Did you see that the workflow seems to have some issues still? (https://github.com/parttimenerd/jmc/actions/runs/1728551346) ------------- Changes requested by clanger (Author). PR: https://git.openjdk.java.net/jmc/pull/363 From clanger at openjdk.java.net Fri Jan 21 14:21:44 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Fri, 21 Jan 2022 14:21:44 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v7] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Fri, 21 Jan 2022 11:13:36 GMT, Brice Dutheil wrote: >> It's weird: the problem does not occur on JDK 11 with the newer p2-maven-plugin. So it might the JDK itself? > > Could it be a tycho issue, again. Tycho overrides many lifecycle of Maven: > > https://github.com/eclipse/tycho/blob/5c83ecd968eae37aa328020d228c8f03b2a3168c/tycho-maven-plugin/src/main/resources/META-INF/plexus/components.xml#L27-L29 > > > > org.eclipse.tycho:tycho-compiler-plugin:${project.version}:compile > > > > _By the way tycho 2.6.0 seems to be [around the corner](https://github.com/eclipse/tycho/releases/tag/tycho-2.6.0), I haven't checked the changelog though._ > > It can't be `p2-maven-plugin` anyway as it is only used to generate a p2 repository (that is used in the `.target` files), and it is only used in `releng/third-party`. I played around with it further. tycho uses JDT under the covers. And it seems to be an issue between Tycho JDT and JDK17. mvn -X shows nice parameters were passed to JDT but I didn't look into it. I will try to see what happens when switching the tycho compiler to javac. Don't know whether that's possible/a good idea... ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From schaturvedi at openjdk.java.net Fri Jan 21 14:49:32 2022 From: schaturvedi at openjdk.java.net (Suchita Chaturvedi) Date: Fri, 21 Jan 2022 14:49:32 GMT Subject: Integrated: 7493: Update versions and copyright on Update site pages In-Reply-To: References: Message-ID: <56-yAuv76aBaKRCyar57ruk7dgEdARdPwJNBtts3zks=.ce88f819-68fe-48b5-b014-9db2c439bb7e@github.com> On Wed, 5 Jan 2022 19:15:52 GMT, Suchita Chaturvedi wrote: > This PR updates the copyright year and Eclipse pre-requisite version. This pull request has now been integrated. Changeset: f077a406 Author: Suchita Chaturvedi URL: https://git.openjdk.java.net/jmc/commit/f077a406946ccab1ca1f3a09e36ace76cda3243c Stats: 9 lines in 4 files changed: 1 ins; 0 del; 8 mod 7493: Update versions and copyright on Update site pages Reviewed-by: hirt ------------- PR: https://git.openjdk.java.net/jmc/pull/346 From duke at openjdk.java.net Fri Jan 21 14:53:06 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 14:53:06 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments Message-ID: Only run broadcasting related tests when supported. Tested on Mac M1 with and without VPN. ------------- Commit messages: - Formatting, again - Update copyright years - Use try-with-resources - Reformat changes - Only run broadcasting related tests when supported Changes: https://git.openjdk.java.net/jmc/pull/369/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=369&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7539 Stats: 48 lines in 3 files changed: 45 ins; 0 del; 3 mod Patch: https://git.openjdk.java.net/jmc/pull/369.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/369/head:pull/369 PR: https://git.openjdk.java.net/jmc/pull/369 From clanger at openjdk.java.net Fri Jan 21 14:53:10 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Fri, 21 Jan 2022 14:53:10 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 14:25:16 GMT, Johannes Bechberger wrote: > Only run broadcasting related tests when supported. > Tested on Mac M1 with and without VPN. You also need to update the copyright years. I'll test this later with my VPN. core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 72: > 70: } > 71: TEST_MULTICAST_ADDRESS = tmp; > 72: BROADCASTING_SUPPORTED = isBroadcastingSupported(); Hm, I'm wondering whether this broadcasting check should be done in the static initialization of the class... maybe not. Rather do it lazily when calling isBroadcastingSupported()? There are a few tests which don't need this... core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 165: > 163: int multiCastPort = 7711; > 164: Thread thread = new Thread(() -> { > 165: try { you can use a try-with resources here: `try (MulticastSocket ssocket = new MulticastSocket(multiCastPort)) {` That way, the socket will also be closed in the end. core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 178: > 176: }); > 177: thread.start(); > 178: try { Same here, try-with resources. The thread.interrupt() can then be done in the `finally` clause. ------------- Changes requested by clanger (Author). PR: https://git.openjdk.java.net/jmc/pull/369 From duke at openjdk.java.net Fri Jan 21 14:53:11 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 14:53:11 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 14:33:15 GMT, Christoph Langer wrote: >> Only run broadcasting related tests when supported. >> Tested on Mac M1 with and without VPN. > > core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 165: > >> 163: int multiCastPort = 7711; >> 164: Thread thread = new Thread(() -> { >> 165: try { > > you can use a try-with resources here: `try (MulticastSocket ssocket = new MulticastSocket(multiCastPort)) {` That way, the socket will also be closed in the end. you're right, I forgot it. ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From hirt at openjdk.java.net Fri Jan 21 14:57:51 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 14:57:51 GMT Subject: RFR: 7420: Update Japanese translation for rules In-Reply-To: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: On Mon, 20 Sep 2021 04:55:25 GMT, mohno007 wrote: > This PR updates/improves Japanese translation of rules and its descriptions. > > ## Update > > * Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. > * Support a new placeholder format introduced in `Rule 2.0`. > * Use Markdown style link. > * Add translations for newly added texts. > * Update texts for translation correctness and understandability. > * Fix some wordings for understandability. Especially usage of Japanese particle. > * Add [Japanese counter word (???)](https://en.wikipedia.org/wiki/Japanese_counter_word) for numeric value. > > You can see decoded version of `messages_ja` using this script: > > > native2ascii -reverse core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties Needs an updated copyright year. core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties line 2: > 1: # > 2: # Copyright (c) 2018, 2021, Oracle and/or its affiliates. All rights reserved. Copyright needs to be updated. ------------- Changes requested by hirt (Lead). PR: https://git.openjdk.java.net/jmc/pull/308 From duke at openjdk.java.net Fri Jan 21 15:01:47 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 15:01:47 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 14:49:51 GMT, Christoph Langer wrote: >> Only run broadcasting related tests when supported. >> Tested on Mac M1 with and without VPN. > > core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 72: > >> 70: } >> 71: TEST_MULTICAST_ADDRESS = tmp; >> 72: BROADCASTING_SUPPORTED = isBroadcastingSupported(); > > Hm, I'm wondering whether this broadcasting check should be done in the static initialization of the class... maybe not. Rather do it lazily when calling isBroadcastingSupported()? There are a few tests which don't need this... The class is only used in this package and half of the test classes in this package need to functionality for their test. There are 4 test classes overall. ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From duke at openjdk.java.net Fri Jan 21 15:04:15 2022 From: duke at openjdk.java.net (mohno007) Date: Fri, 21 Jan 2022 15:04:15 GMT Subject: RFR: 7417: Fix incorrect identifier in result for biased locking revocation rule [v2] In-Reply-To: References: Message-ID: > This PR fixes a wrong placeholder in `BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND_LONG`. > > `BiasedLockingRevocationRule.java` used `{revokedClasses}` for placeholder identifier but `messages.properties` used `{revokedTypes}`. mohno007 has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: - Update copyright year - Fix wrong placeholder in BiasedLockingRevocationRule ------------- Changes: https://git.openjdk.java.net/jmc/pull/309/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=309&range=01 Stats: 6 lines in 2 files changed: 0 ins; 0 del; 6 mod Patch: https://git.openjdk.java.net/jmc/pull/309.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/309/head:pull/309 PR: https://git.openjdk.java.net/jmc/pull/309 From duke at openjdk.java.net Fri Jan 21 15:04:18 2022 From: duke at openjdk.java.net (mohno007) Date: Fri, 21 Jan 2022 15:04:18 GMT Subject: RFR: 7417: Fix incorrect identifier in result for biased locking revocation rule [v2] In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 12:11:00 GMT, Marcus Hirt wrote: >> mohno007 has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: >> >> - Update copyright year >> - Fix wrong placeholder in BiasedLockingRevocationRule > > core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/java/org/openjdk/jmc/flightrecorder/rules/jdk/latency/BiasedLockingRevocationRule.java line 115: > >> 113: private static final List> CONFIG_ATTRIBUTES = Arrays.> asList(WARNING_LIMIT, >> 114: MAX_NUMBER_OF_CLASSES_TO_REPORT, FILTERED_CLASSES); >> 115: > > Need to update copyright year. Thank you for your advice. I fixed it in ecb74c7. > core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages.properties line 77: > >> 75: BiasedLockingRevocationRule_TEXT_OK=No classes were disabled from participating in biased locking >> 76: BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND=Fully revoked classes found. >> 77: BiasedLockingRevocationRule_TEXT_REVOKED_CLASSES_FOUND_LONG=The following classes were disabled from using biased locking: {revokedClasses} > > Need to update copyright year. Thank you for your advice. I fixed it in ecb74c7. ------------- PR: https://git.openjdk.java.net/jmc/pull/309 From aptmac at openjdk.java.net Fri Jan 21 15:12:50 2022 From: aptmac at openjdk.java.net (Alex Macdonald) Date: Fri, 21 Jan 2022 15:12:50 GMT Subject: RFR: 7477: JMC8.2 does not build with eclipse 4.19 (21-03) In-Reply-To: References: Message-ID: On Thu, 20 Jan 2022 22:16:09 GMT, Marcus Hirt wrote: > Something funny is happening with the workflow. Trying in a separate PR to see if it can be reproduced. Marked as reviewed by aptmac (Reviewer). ------------- PR: https://git.openjdk.java.net/jmc/pull/367 From hirt at openjdk.java.net Fri Jan 21 15:14:49 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 15:14:49 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 14:25:16 GMT, Johannes Bechberger wrote: > Only run broadcasting related tests when supported. > Tested on Mac M1 with and without VPN. I think it would be better to have the test provide information about how to properly configure the machine to properly run the tests than to automatically skip the tests. Perhaps we could also add a system property check or something to make it easy to skip the test from the command line, if someone truly can't get it to work. But then it should be a conscious choice, not something happening automatically to avoid having to fix the setup. Here is for example one possible scenario if we go with automated skipping: 1. Images used for our automated testing change their configuration, no longer providing a route for local multicast. 2. Tests are automatically skipped. 3. JDP changes and breaks. 4. We are never the wiser (until some JDP using person complains post release). We shouldn't automatically skip tests without a very strong reason. It's better to inform the runner of the test how to fix their config. ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From duke at openjdk.java.net Fri Jan 21 15:20:51 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 15:20:51 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 14:25:16 GMT, Johannes Bechberger wrote: > Only run broadcasting related tests when supported. > Tested on Mac M1 with and without VPN. An option could be to log a warning if we skip a test. ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From clanger at openjdk.java.net Fri Jan 21 15:24:50 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Fri, 21 Jan 2022 15:24:50 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 15:12:30 GMT, Marcus Hirt wrote: > I think it would be better to have the test provide information about how to properly configure the machine to properly run the tests than to automatically skip the tests. Perhaps we could also add a system property check or something to make it easy to skip the test from the command line, if someone truly can't get it to work. But then it should be a conscious choice, not something happening automatically to avoid having to fix the setup. > > Here is for example one possible scenario if we go with automated skipping: > > 1. Images used for our automated testing change their configuration, no longer providing a route for local multicast. > 2. Tests are automatically skipped. > 3. JDP changes and breaks. > 4. We are never the wiser (until some JDP using person complains post release). > > We shouldn't automatically skip tests without a very strong reason. It's better to inform the runner of the test how to fix their config. I agree - we should catch the failure and then log something like: This test failed. Please check if your multicast is working or you are running in a VPN configuration. If this can't be fixed, build with `mvn -DskipJDPMulticastTests=true ...`. And then check for this property when deciding whether to run the test. ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From hirt at openjdk.java.net Fri Jan 21 15:31:49 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 15:31:49 GMT Subject: RFR: 7537: Build script assumes that Darwin always targets x86_64 In-Reply-To: <2P2V8rPVYzaQKk43iAkOX4GRdpkHiLMX9RBoS7-_3LY=.e6267ea2-f1bb-44cb-849e-dafe0c345ad7@github.com> References: <2P2V8rPVYzaQKk43iAkOX4GRdpkHiLMX9RBoS7-_3LY=.e6267ea2-f1bb-44cb-849e-dafe0c345ad7@github.com> Message-ID: On Thu, 20 Jan 2022 10:38:35 GMT, Johannes Bechberger wrote: > Tested on Mac M1. Marked as reviewed by hirt (Lead). Olga helped verify this! ------------- PR: https://git.openjdk.java.net/jmc/pull/366 From hirt at openjdk.java.net Fri Jan 21 15:35:47 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 15:35:47 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 14:25:16 GMT, Johannes Bechberger wrote: > Only run broadcasting related tests when supported. > Tested on Mac M1 with and without VPN. Yup. We can even provide information about the proper command to use on Mac for adding the route. ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From hirt at openjdk.java.net Fri Jan 21 15:40:50 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 15:40:50 GMT Subject: Integrated: 7477: JMC8.2 does not build with eclipse 4.19 (21-03) In-Reply-To: References: Message-ID: On Thu, 20 Jan 2022 22:16:09 GMT, Marcus Hirt wrote: > Something funny is happening with the workflow. Trying in a separate PR to see if it can be reproduced. This pull request has now been integrated. Changeset: c646b146 Author: Marcus Hirt URL: https://git.openjdk.java.net/jmc/commit/c646b1463c5317e279729440bd6b85ff0764a953 Stats: 448 lines in 10 files changed: 0 ins; 448 del; 0 mod 7477: JMC8.2 does not build with eclipse 4.19 (21-03) Reviewed-by: aptmac ------------- PR: https://git.openjdk.java.net/jmc/pull/367 From clanger at openjdk.java.net Fri Jan 21 16:04:16 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Fri, 21 Jan 2022 16:04:16 GMT Subject: RFR: 7540: IItemCollectionJsonSerializerTest.java might fail on Windows due to line endings Message-ID: <4QDJZCaqrjOa0hzKkNkpk25V40v0kap0Y3t5ByPmcoY=.a9c80de6-b329-4928-a7cd-387163576685@github.com> Fix test IItemCollectionJsonSerializerTest.java The line endings should be normalized, to avoid errors on Windows due to incompatible line ending formats. ------------- Commit messages: - JMC-7540 Changes: https://git.openjdk.java.net/jmc/pull/370/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=370&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7540 Stats: 3 lines in 1 file changed: 0 ins; 0 del; 3 mod Patch: https://git.openjdk.java.net/jmc/pull/370.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/370/head:pull/370 PR: https://git.openjdk.java.net/jmc/pull/370 From duke at openjdk.java.net Fri Jan 21 16:42:51 2022 From: duke at openjdk.java.net (Brice Dutheil) Date: Fri, 21 Jan 2022 16:42:51 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v7] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Fri, 21 Jan 2022 14:09:39 GMT, Christoph Langer wrote: >> Could it be a tycho issue, again. Tycho overrides many lifecycle of Maven: >> >> https://github.com/eclipse/tycho/blob/5c83ecd968eae37aa328020d228c8f03b2a3168c/tycho-maven-plugin/src/main/resources/META-INF/plexus/components.xml#L27-L29 >> >> >> >> org.eclipse.tycho:tycho-compiler-plugin:${project.version}:compile >> >> >> >> _By the way tycho 2.6.0 seems to be [around the corner](https://github.com/eclipse/tycho/releases/tag/tycho-2.6.0), I haven't checked the changelog though._ >> >> It can't be `p2-maven-plugin` anyway as it is only used to generate a p2 repository (that is used in the `.target` files), and it is only used in `releng/third-party`. > > I played around with it further. tycho uses JDT under the covers. And it seems to be an issue between Tycho JDT and JDK17. mvn -X shows nice parameters were passed to JDT but I didn't look into it. I will try to see what happens when switching the tycho compiler to javac. Don't know whether that's possible/a good idea... I don't think that's possible, tycho overrides many aspects of maven, typicaly for the compiler the tycho _overlay_ will get depdencies from other tycho plugin, not from maven APIs. ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From clanger at openjdk.java.net Fri Jan 21 16:52:49 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Fri, 21 Jan 2022 16:52:49 GMT Subject: RFR: 7526: JMC not buildable with jdk17 [v7] In-Reply-To: References: <0jZIwZkc6zn5iJyLc3S382gVLEDEjB4JYHABk6sPeik=.61675b51-45d1-404d-a712-dcd76cc632d6@github.com> Message-ID: On Fri, 21 Jan 2022 16:39:33 GMT, Brice Dutheil wrote: >> I played around with it further. tycho uses JDT under the covers. And it seems to be an issue between Tycho JDT and JDK17. mvn -X shows nice parameters were passed to JDT but I didn't look into it. I will try to see what happens when switching the tycho compiler to javac. Don't know whether that's possible/a good idea... > > I don't think that's possible, tycho overrides many aspects of maven, typicaly for the compiler the tycho _overlay_ will get depdencies from other tycho plugin, not from maven APIs. Yup, you're right. I figured that out. I guess we have to live with the workaround. We can try once again with tycho 2.6.0 which should be out really soon. But if that doesn't change a thing we can only open an issue with tycho. ------------- PR: https://git.openjdk.java.net/jmc/pull/363 From duke at openjdk.java.net Fri Jan 21 17:15:22 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 17:15:22 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments [v2] In-Reply-To: References: Message-ID: > Only run broadcasting related tests when supported. > Tested on Mac M1 with and without VPN. Johannes Bechberger has updated the pull request incrementally with two additional commits since the last revision: - Add skip functionality to build.sh script - Introduce -DskipJDPMulticastTests ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/369/files - new: https://git.openjdk.java.net/jmc/pull/369/files/774c2093..a50e543f Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=369&range=01 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=369&range=00-01 Stats: 80 lines in 4 files changed: 41 ins; 16 del; 23 mod Patch: https://git.openjdk.java.net/jmc/pull/369.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/369/head:pull/369 PR: https://git.openjdk.java.net/jmc/pull/369 From duke at openjdk.java.net Fri Jan 21 17:25:18 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 17:25:18 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments [v3] In-Reply-To: References: Message-ID: > Only run broadcasting related tests when supported. > Tested on Mac M1 with and without VPN. Johannes Bechberger has updated the pull request incrementally with one additional commit since the last revision: Formatting ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/369/files - new: https://git.openjdk.java.net/jmc/pull/369/files/a50e543f..f902747c Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=369&range=02 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=369&range=01-02 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.java.net/jmc/pull/369.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/369/head:pull/369 PR: https://git.openjdk.java.net/jmc/pull/369 From duke at openjdk.java.net Fri Jan 21 18:23:47 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Fri, 21 Jan 2022 18:23:47 GMT Subject: Integrated: 7537: Build script assumes that Darwin always targets x86_64 In-Reply-To: <2P2V8rPVYzaQKk43iAkOX4GRdpkHiLMX9RBoS7-_3LY=.e6267ea2-f1bb-44cb-849e-dafe0c345ad7@github.com> References: <2P2V8rPVYzaQKk43iAkOX4GRdpkHiLMX9RBoS7-_3LY=.e6267ea2-f1bb-44cb-849e-dafe0c345ad7@github.com> Message-ID: <3f6G_WCZFccV7m8zZfMWH3GVaPc93pvJL7NuEdnrvrQ=.56691ba5-55b9-40d3-8b45-1cdcdfbee70f@github.com> On Thu, 20 Jan 2022 10:38:35 GMT, Johannes Bechberger wrote: > Tested on Mac M1. This pull request has now been integrated. Changeset: baa6c777 Author: Johannes Bechberger Committer: Patrick Reinhart URL: https://git.openjdk.java.net/jmc/commit/baa6c777e461982b9c8d729fcac799abe2c004b0 Stats: 13 lines in 2 files changed: 7 ins; 0 del; 6 mod 7537: Build script assumes that Darwin always targets x86_64 Reviewed-by: hirt ------------- PR: https://git.openjdk.java.net/jmc/pull/366 From hirt at openjdk.java.net Fri Jan 21 23:36:13 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 23:36:13 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments [v3] In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 17:25:18 GMT, Johannes Bechberger wrote: >> Only run broadcasting related tests when supported. >> Tested on Mac M1 with and without VPN. > > Johannes Bechberger has updated the pull request incrementally with one additional commit since the last revision: > > Formatting Marked as reviewed by hirt (Lead). ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From hirt at openjdk.java.net Fri Jan 21 23:37:15 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 23:37:15 GMT Subject: RFR: 7540: IItemCollectionJsonSerializerTest.java might fail on Windows due to line endings In-Reply-To: <4QDJZCaqrjOa0hzKkNkpk25V40v0kap0Y3t5ByPmcoY=.a9c80de6-b329-4928-a7cd-387163576685@github.com> References: <4QDJZCaqrjOa0hzKkNkpk25V40v0kap0Y3t5ByPmcoY=.a9c80de6-b329-4928-a7cd-387163576685@github.com> Message-ID: On Fri, 21 Jan 2022 15:57:41 GMT, Christoph Langer wrote: > Fix test IItemCollectionJsonSerializerTest.java > > The line endings should be normalized, to avoid errors on Windows due to incompatible line ending formats. Marked as reviewed by hirt (Lead). ------------- PR: https://git.openjdk.java.net/jmc/pull/370 From hirt at openjdk.java.net Fri Jan 21 23:46:37 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Fri, 21 Jan 2022 23:46:37 GMT Subject: RFR: 7541: Switch to using 2021-09 by default Message-ID: This is the platform that Oracle will use when releasing, so might as well make it the default. ------------- Commit messages: - 7541: Switch to using 2021-09 by default Changes: https://git.openjdk.java.net/jmc/pull/371/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=371&range=00 Issue: https://bugs.openjdk.java.net/browse/JMC-7541 Stats: 6 lines in 1 file changed: 3 ins; 3 del; 0 mod Patch: https://git.openjdk.java.net/jmc/pull/371.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/371/head:pull/371 PR: https://git.openjdk.java.net/jmc/pull/371 From duke at openjdk.java.net Sat Jan 22 01:07:52 2022 From: duke at openjdk.java.net (mohno007) Date: Sat, 22 Jan 2022 01:07:52 GMT Subject: RFR: 7420: Update Japanese translation for rules [v2] In-Reply-To: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: > This PR updates/improves Japanese translation of rules and its descriptions. > > ## Update > > * Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. > * Support a new placeholder format introduced in `Rule 2.0`. > * Use Markdown style link. > * Add translations for newly added texts. > * Update texts for translation correctness and understandability. > * Fix some wordings for understandability. Especially usage of Japanese particle. > * Add [Japanese counter word (???)](https://en.wikipedia.org/wiki/Japanese_counter_word) for numeric value. > > You can see decoded version of `messages_ja` using this script: > > > native2ascii -reverse core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties mohno007 has updated the pull request incrementally with one additional commit since the last revision: Update copyright year ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/308/files - new: https://git.openjdk.java.net/jmc/pull/308/files/48d36d49..ac631bd3 Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=308&range=01 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=308&range=00-01 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.java.net/jmc/pull/308.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/308/head:pull/308 PR: https://git.openjdk.java.net/jmc/pull/308 From duke at openjdk.java.net Sat Jan 22 01:16:10 2022 From: duke at openjdk.java.net (mohno007) Date: Sat, 22 Jan 2022 01:16:10 GMT Subject: RFR: 7420: Update Japanese translation for rules [v2] In-Reply-To: References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: <3ifh0-pAlumb7yhlLu69TFfHtugMssKOKaK45-kVYnM=.2dc2c912-5556-4827-971c-3fcd4575db01@github.com> On Sat, 22 Jan 2022 01:07:52 GMT, mohno007 wrote: >> This PR updates/improves Japanese translation of rules and its descriptions. >> >> ## Update >> >> * Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. >> * Support a new placeholder format introduced in `Rule 2.0`. >> * Use Markdown style link. >> * Add translations for newly added texts. >> * Update texts for translation correctness and understandability. >> * Fix some wordings for understandability. Especially usage of Japanese particle. >> * Add [Japanese counter word (???)](https://en.wikipedia.org/wiki/Japanese_counter_word) for numeric value. >> >> You can see decoded version of `messages_ja` using this script: >> >> >> native2ascii -reverse core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties > > mohno007 has updated the pull request incrementally with one additional commit since the last revision: > > Update copyright year As you may know, I can sign the OCA. Thank you to the developers for your patience. Thank you to Dalibor-san and OCA support for resolving the issue. ------------- PR: https://git.openjdk.java.net/jmc/pull/308 From duke at openjdk.java.net Sat Jan 22 01:16:11 2022 From: duke at openjdk.java.net (mohno007) Date: Sat, 22 Jan 2022 01:16:11 GMT Subject: RFR: 7420: Update Japanese translation for rules [v2] In-Reply-To: References: <_3eRPXBrbMr6uVo3lMVwefLwCSLj9Y_hnR21yY0T_vI=.a76a0f72-cb79-4fa9-921b-63d12432b8f4@github.com> Message-ID: On Fri, 21 Jan 2022 12:09:54 GMT, Marcus Hirt wrote: >> mohno007 has updated the pull request incrementally with one additional commit since the last revision: >> >> Update copyright year > > core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties line 2: > >> 1: # >> 2: # Copyright (c) 2018, 2021, Oracle and/or its affiliates. All rights reserved. > > Copyright needs to be updated. I fixed it in ac631bd. ------------- PR: https://git.openjdk.java.net/jmc/pull/308 From duke at openjdk.java.net Sat Jan 22 01:38:50 2022 From: duke at openjdk.java.net (mohno007) Date: Sat, 22 Jan 2022 01:38:50 GMT Subject: RFR: 7421: Update Japanese translation for pages [v2] In-Reply-To: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> References: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> Message-ID: > This PR updates/improves Japanese translation for pages. > > Update texts based on new commits to `messages.properties` made after the last update date of the `messages_ja.properties`. > > You can see decoded version of `messages_ja` using this script: > > > native2ascii -reverse application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties mohno007 has updated the pull request incrementally with three additional commits since the last revision: - Use "???" for "span" - Use "?" instead of "????" - Update copyright year ------------- Changes: - all: https://git.openjdk.java.net/jmc/pull/310/files - new: https://git.openjdk.java.net/jmc/pull/310/files/11b2825f..3fdce404 Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jmc&pr=310&range=01 - incr: https://webrevs.openjdk.java.net/?repo=jmc&pr=310&range=00-01 Stats: 3 lines in 1 file changed: 0 ins; 0 del; 3 mod Patch: https://git.openjdk.java.net/jmc/pull/310.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/310/head:pull/310 PR: https://git.openjdk.java.net/jmc/pull/310 From duke at openjdk.java.net Sat Jan 22 01:41:12 2022 From: duke at openjdk.java.net (mohno007) Date: Sat, 22 Jan 2022 01:41:12 GMT Subject: RFR: 7421: Update Japanese translation for pages [v2] In-Reply-To: References: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> Message-ID: On Fri, 21 Jan 2022 12:10:22 GMT, Marcus Hirt wrote: >> mohno007 has updated the pull request incrementally with three additional commits since the last revision: >> >> - Use "???" for "span" >> - Use "?" instead of "????" >> - Update copyright year > > application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties line 2: > >> 1: # >> 2: # Copyright (c) 2018, 2021, Oracle and/or its affiliates. All rights reserved. > > Should update copyright year. I fixed it in 935be84b. ------------- PR: https://git.openjdk.java.net/jmc/pull/310 From duke at openjdk.java.net Sat Jan 22 01:41:13 2022 From: duke at openjdk.java.net (mohno007) Date: Sat, 22 Jan 2022 01:41:13 GMT Subject: RFR: 7421: Update Japanese translation for pages [v2] In-Reply-To: References: <3BJ0s8EF4PjKGMfzZKjf3LygHTGqkSDJ4J6mzmS_srE=.b49ef1ef-a54b-4ed5-9971-919726bd645a@github.com> Message-ID: On Mon, 15 Nov 2021 22:15:56 GMT, Alex Macdonald wrote: >> mohno007 has updated the pull request incrementally with three additional commits since the last revision: >> >> - Use "???" for "span" >> - Use "?" instead of "????" >> - Update copyright year > > application/l10n/org.openjdk.jmc.flightrecorder.ui.ja/src/main/resources/org/openjdk/jmc/flightrecorder/ui/messages/internal/messages_ja.properties line 514: > >> 512: ThreadsPage_EDIT_LANES=\u30B9\u30EC\u30C3\u30C9\u30FB\u30EC\u30FC\u30F3\u306E\u7DE8\u96C6 >> 513: ThreadsPage_FOLD_CHART_TOOLTIP=\u30C1\u30E3\u30FC\u30C8\u3092\u6298\u308A\u305F\u305F\u3080 >> 514: ThreadsPage_FOLD_TABLE_TOOLTIP=\u30C6\u30FC\u30D6\u30EB\u3092\u6298\u308A\u305F\u305F\u3080 > > Out of curiosity, how come this string uses "????" for table instead of "?" ? Thank you for pointing this out. I overlooked the correspondence between `ThreadsPage_FOLD_TABLE_TOOLTIP` and `ThreadsPage_SHOW_TABLE_TOOLTIP`. I think "?" is appropriate for here. I fixed it in ef89b0dc. ------------- PR: https://git.openjdk.java.net/jmc/pull/310 From clanger at openjdk.java.net Sat Jan 22 06:38:33 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Sat, 22 Jan 2022 06:38:33 GMT Subject: RFR: 7540: IItemCollectionJsonSerializerTest.java might fail on Windows due to line endings [v2] In-Reply-To: <4QDJZCaqrjOa0hzKkNkpk25V40v0kap0Y3t5ByPmcoY=.a9c80de6-b329-4928-a7cd-387163576685@github.com> References: <4QDJZCaqrjOa0hzKkNkpk25V40v0kap0Y3t5ByPmcoY=.a9c80de6-b329-4928-a7cd-387163576685@github.com> Message-ID: > Fix test IItemCollectionJsonSerializerTest.java > > The line endings should be normalized, to avoid errors on Windows due to incompatible line ending formats. Christoph Langer has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains one commit: JMC-7540 Fix test IItemCollectionJsonSerializerTest.java ------------- Changes: https://git.openjdk.java.net/jmc/pull/370/files Webrev: https://webrevs.openjdk.java.net/?repo=jmc&pr=370&range=01 Stats: 3 lines in 1 file changed: 0 ins; 0 del; 3 mod Patch: https://git.openjdk.java.net/jmc/pull/370.diff Fetch: git fetch https://git.openjdk.java.net/jmc pull/370/head:pull/370 PR: https://git.openjdk.java.net/jmc/pull/370 From duke at openjdk.java.net Sat Jan 22 07:43:12 2022 From: duke at openjdk.java.net (Johannes Bechberger) Date: Sat, 22 Jan 2022 07:43:12 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments [v3] In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 17:25:18 GMT, Johannes Bechberger wrote: >> Only run broadcasting related tests when supported. >> Tested on Mac M1 with and without VPN. > > Johannes Bechberger has updated the pull request incrementally with one additional commit since the last revision: > > Formatting My current change still misses the integration in the Windows build script (but this might not be a problem as the VPN stuff primarily seems to affect Mac users) and a short remark in the README. Any thoughts about windows? ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From clanger at openjdk.java.net Sat Jan 22 10:24:11 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Sat, 22 Jan 2022 10:24:11 GMT Subject: RFR: 7541: Switch to using 2021-09 by default In-Reply-To: References: Message-ID: <8cJGFqZ3aXBnsdsNdYDZRA8MPDr_xjygohaXxQGNj2s=.0be2d2db-ea55-4472-9c8d-0e442d79c88d@github.com> On Fri, 21 Jan 2022 23:41:38 GMT, Marcus Hirt wrote: > This is the platform that Oracle will use when releasing, so might as well make it the default. Marked as reviewed by clanger (Author). ------------- PR: https://git.openjdk.java.net/jmc/pull/371 From clanger at openjdk.java.net Sat Jan 22 13:40:15 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Sat, 22 Jan 2022 13:40:15 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments [v3] In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 17:25:18 GMT, Johannes Bechberger wrote: >> Only run broadcasting related tests when supported. >> Tested on Mac M1 with and without VPN. > > Johannes Bechberger has updated the pull request incrementally with one additional commit since the last revision: > > Formatting Looks good, I only have a few minor suggestions. For me it's ok to leave out the windows build script for now. I can add this later on, I want to play with that script anyway, have just built with maven so far. build.sh line 297: > 295: ;; > 296: --skipJDPMulticastTests) > 297: JVM_ARGUMENTS="${JVM_ARGUMENTS} -DskipJDPMulticastTests=true " nit: you could remove the space after -DskipJDPMulticastTests=true core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 55: > 53: private static final String TEST_MULTICAST_ADDRESS_STRING = "224.0.23.177"; > 54: public static final InetAddress TEST_MULTICAST_ADDRESS; > 55: nit: Leave that line. core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 158: > 156: */ > 157: public static boolean areBroadcastingTestsEnabled() { > 158: if (System.getProperty("skipJDPMulticastTests", "false").equals("true")) { you could do: `if (Boolean.getBoolean("skipJDPMulticastTests")) {` here core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 171: > 169: helpMessage += String.format("'sudo ip route add %s dev eth0'", address); > 170: } else { > 171: helpMessage = ""; On windows you can recommend to `route add ... ` in a shell with administrator permissions. I did that and this made the test work. Obviously the user has to look up the gateway. Something like `helpMessage += String.format("'route add %s ' in a shell with administrator permissions", address);` core/tests/org.openjdk.jmc.jdp.test/src/test/java/org/openjdk/jmc/jdp/client/TestToolkit.java line 174: > 172: } > 173: JDPClientTest.LOGGER.log(Level.WARNING, "Broadcasting does not seem to be possible.\n" > 174: + "This is usually related to VPN. There are four possible ways to remedy this:\n" Actually, you enumerate only 3 possibilities, although the last one consists of two distinct options, depending on your build scenario ------------- Changes requested by clanger (Author). PR: https://git.openjdk.java.net/jmc/pull/369 From jpbempel at openjdk.java.net Sat Jan 22 14:13:07 2022 From: jpbempel at openjdk.java.net (Jean-Philippe Bempel) Date: Sat, 22 Jan 2022 14:13:07 GMT Subject: RFR: 7541: Switch to using 2021-09 by default In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 23:41:38 GMT, Marcus Hirt wrote: > This is the platform that Oracle will use when releasing, so might as well make it the default. Marked as reviewed by jpbempel (Committer). ------------- PR: https://git.openjdk.java.net/jmc/pull/371 From clanger at openjdk.java.net Sat Jan 22 14:29:10 2022 From: clanger at openjdk.java.net (Christoph Langer) Date: Sat, 22 Jan 2022 14:29:10 GMT Subject: Integrated: 7540: IItemCollectionJsonSerializerTest.java might fail on Windows due to line endings In-Reply-To: <4QDJZCaqrjOa0hzKkNkpk25V40v0kap0Y3t5ByPmcoY=.a9c80de6-b329-4928-a7cd-387163576685@github.com> References: <4QDJZCaqrjOa0hzKkNkpk25V40v0kap0Y3t5ByPmcoY=.a9c80de6-b329-4928-a7cd-387163576685@github.com> Message-ID: On Fri, 21 Jan 2022 15:57:41 GMT, Christoph Langer wrote: > Fix test IItemCollectionJsonSerializerTest.java > > The line endings should be normalized, to avoid errors on Windows due to incompatible line ending formats. This pull request has now been integrated. Changeset: 3d036435 Author: Christoph Langer Committer: Marcus Hirt URL: https://git.openjdk.java.net/jmc/commit/3d0364353bee86b742a351c5617032b1d1b8aa0c Stats: 3 lines in 1 file changed: 0 ins; 0 del; 3 mod 7540: IItemCollectionJsonSerializerTest.java might fail on Windows due to line endings Reviewed-by: hirt ------------- PR: https://git.openjdk.java.net/jmc/pull/370 From hirt at openjdk.java.net Sat Jan 22 14:31:12 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Sat, 22 Jan 2022 14:31:12 GMT Subject: RFR: 7539: JDP Tests failing in VPN environments In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 15:22:04 GMT, Christoph Langer wrote: >> I think it would be better to have the test provide information about how to properly configure the machine to properly run the tests than to automatically skip the tests. Perhaps we could also add a system property check or something to make it easy to skip the test from the command line, if someone truly can't get it to work. But then it should be a conscious choice, not something happening automatically to avoid having to fix the setup. >> >> Here is for example one possible scenario if we go with automated skipping: >> 1. Images used for our automated testing change their configuration, no longer providing a route for local multicast. >> 2. Tests are automatically skipped. >> 3. JDP changes and breaks. >> 4. We are never the wiser (until some JDP using person complains post release). >> >> We shouldn't automatically skip tests without a very strong reason. It's better to inform the runner of the test how to fix their config. > >> I think it would be better to have the test provide information about how to properly configure the machine to properly run the tests than to automatically skip the tests. Perhaps we could also add a system property check or something to make it easy to skip the test from the command line, if someone truly can't get it to work. But then it should be a conscious choice, not something happening automatically to avoid having to fix the setup. >> >> Here is for example one possible scenario if we go with automated skipping: >> >> 1. Images used for our automated testing change their configuration, no longer providing a route for local multicast. >> 2. Tests are automatically skipped. >> 3. JDP changes and breaks. >> 4. We are never the wiser (until some JDP using person complains post release). >> >> We shouldn't automatically skip tests without a very strong reason. It's better to inform the runner of the test how to fix their config. > > I agree - we should catch the failure and then log something like: > This test failed. Please check if your multicast is working or you are running in a VPN configuration. If this can't be fixed, build with `mvn -DskipJDPMulticastTests=true ...`. > > And then check for this property when deciding whether to run the test. @RealCLanger has provided good insights! Let's act on his feedback before pushing this. ------------- PR: https://git.openjdk.java.net/jmc/pull/369 From hirt at openjdk.java.net Sat Jan 22 14:33:07 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Sat, 22 Jan 2022 14:33:07 GMT Subject: RFR: 7541: Switch to using 2021-09 by default In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 23:41:38 GMT, Marcus Hirt wrote: > This is the platform that Oracle will use when releasing, so might as well make it the default. Need another committer (or a reviewer) to review this. ------------- PR: https://git.openjdk.java.net/jmc/pull/371 From hirt at openjdk.java.net Sat Jan 22 14:35:12 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Sat, 22 Jan 2022 14:35:12 GMT Subject: RFR: 7538: Check in launcher for JVMKeepAlive In-Reply-To: References: Message-ID: On Fri, 21 Jan 2022 11:54:10 GMT, Marcus Hirt wrote: > Helpful for new developers. Good point. Will add some detail to the devguide. ------------- PR: https://git.openjdk.java.net/jmc/pull/368 From hirt at openjdk.java.net Sat Jan 22 14:37:03 2022 From: hirt at openjdk.java.net (Marcus Hirt) Date: Sat, 22 Jan 2022 14:37:03 GMT Subject: RFR: 7449: Add GitHub action to verify copyright year [v3] In-Reply-To: References: Message-ID: <1VqMp-Qm-6ISgdIOjAIb5ZLDxR2DlA-RZnXN1tCvTTc=.4057dc69-c09a-4488-a024-2f5d474a5cc6@github.com> On Sat, 11 Dec 2021 20:20:44 GMT, Alex Ciminian wrote: >> This PR adds a script to check copyright notices on changed files. I've not added a GitHub action yet, I'd like to get some feedback before doing that ?? >> >> The script is written in Kotlin and uses [JGit](https://www.eclipse.org/jgit/) to interface with the git repository. To run, it only needs the kotlin compiler which is [preinstalled on GitHub Actions runners](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md). >> >> It works as follows: >> >> * diff the HEAD commit and the merge base between it and master (i.e. where the feature branch diverged from) >> * for every changed file (except deletions), validate the copyright header >> - if the file is new, it should have Oracle and Datadog copyright starting from the year of the HEAD commit >> - if the file is not new, it should keep the existing copyright holders and update the year range if necessary >> * we compare file contents from objects in the git repo, not the files themselves >> * currently we don't validate we're in the correct directory or the commits >> >> The output looks like this: >> >> >> kotlinc -script scripts/copyrightchecker.main.kts >> Checked out at: 759788185939b16f447e553b3ee64121187ea311 (base: 8b8aa7c299b92b655ba669a92d16f193beb406bc) >> ?? scripts/copyrightchecker.main.kts >> ? Validation succeeded >> >> >> >> kotlinc -script scripts/copyrightchecker.main.kts >> Checked out at: 7ad43eed12c9eb85a96882c9518a9acbe12e74c5 (base: ca204424ce32336f2923aff66f619d571b1fc720) >> ?? .gitignore >> ?? application/org.openjdk.jmc.feature.flightrecorder/feature.xml >> ?? Failed to parse: Copyright (c) 2018, 2021 Oracle and/or its affiliates. All rights reserved. >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/.classpath >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/.gitignore >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/META-INF/MANIFEST.MF >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/build.properties >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/icons/heatmap.png >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/icons/heatmap at 2x.png >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/plugin.properties >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/plugin.xml >> ?? application/org.openjdk.jmc.flightrecorder.heatmap/pom.xml >> Expected: >> >>