eclipse-linuxtools / org.eclipse.linuxtools Goto Github PK

The wiki article at https://wiki.eclipse.org/Linux_Tools_Project/Getting_Involved is outdated after the migration from Eclipse hosted infra to github.
As I'm not part of the project and do not know how you want to proceed, now that you've migrated to github, I think it would be best if someone with the required insight updates the wiki article to describe the new process of sending patches etc. and also update the repository location.

It would be nice to have access to the validator. E.g. to fix things like eclipse-cdt/cdt#181

Also it feels like it should go into core. :)

I'm willing to make a PR, but having some guidelines where to put it and how to best expose it would be nice.

With the latest version of Docker Desktop, at the time of this writing v4.27.2, the docker images cannot be listed (while the containers still can)

Details and exception:

eclipse.buildId=4.30.0.20231201-1200
java.version=21.0.2
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=nl_BE
Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/C:/cegeka/workspaces/jbaas/container-images/ -product org.eclipse.epp.package.jee.product

org.eclipse.core.jobs
Error
Wed Feb 14 13:38:35 CET 2024
An internal error occurred during: "Refreshing Images...".

java.lang.NullPointerException: Cannot invoke "String.startsWith(String)" because "s" is null
at org.eclipse.linuxtools.docker.core.DockerException.calculateMessage(DockerException.java:56)
at org.eclipse.linuxtools.docker.core.DockerException.(DockerException.java:33)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:1136)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:1070)
at org.eclipse.linuxtools.internal.docker.ui.commands.RefreshConnectionHandler$2.run(RefreshConnectionHandler.java:99)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Description

According to the instructions in this page, I tried to configure the development environment on my computer. When setting the target platform, I encountered the problem as shown in the figure.

Source code

latest on branch master cloned from this repo

System info

Linux version 5.15.0-67-generic (buildd@lcy02-amd64-116) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023

Ubuntu 22.0.4 LTS

IDE info

Eclipse IDE for RCP and RAP Developers (includes Incubating components)
Version: 2023-03 (4.27.0)
Build id: 20230309-1520

Java version

openjdk 17.0.6 2023-01-17
OpenJDK Runtime Environment (build 17.0.6+10-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 17.0.6+10-Ubuntu-0ubuntu122.04, mixed mode, sharing)

Could someone do me a favor？ @akurtakov @jjohnstn

eclipse-platform/eclipse.platform.ui#323 removed the deprecated class org.eclipse.jface.databinding.viewers.ViewersObservables <-- link to file before it was deleted so you can read the @deprecated instructions.

xref: eclipse-cdt/cdt#73 which is the same issue for CDT.

If linuxtools fixes this first it will give me some guidance on fixing this. Likewise if CDT fixes it first I hope eclipse-cdt/cdt#73 is useful.

Launching Eclipse IDE for C/C++ Developers on my Gentoo system gives the following dialog:

And this entry in the workspace log file:

!ENTRY org.eclipse.core.jobs 4 2 2022-04-15 13:46:36.328
!MESSAGE An internal error occurred during: "Generating Library Hover help for installed devhelp documentation".
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
        at org.eclipse.linuxtools.internal.cdt.libhover.devhelp.ParseDevHelp$DevHelpParser.parse(ParseDevHelp.java:505)
        at org.eclipse.linuxtools.internal.cdt.libhover.devhelp.ParseDevHelp$DevHelpParser.parse(ParseDevHelp.java:383)
        at org.eclipse.linuxtools.internal.cdt.libhover.devhelp.DevHelpStartup$DevhelpStartupJob.run(DevHelpStartup.java:99)

With some minor debugging to narrowing down the issue points to that it's this XML content that causes the error:

<?xml version="1.0" encoding="UTF-8"?>
<book xmlns="http://www.devhelp.net/book" title="PangoFT2-1.0 Reference Manual" link="index.html" author="Owen Taylor, Behdad Esfahbod" name="PangoFT2" version="2" language="c">
   <chapters>
      <sub name="Classes Hierarchy" link="classes_hierarchy.html" />
      <sub name="Callbacks" link="index.html#callbacks">
         <sub name="SubstituteFunc" link="callback.SubstituteFunc.html" />
      </sub>
      <sub name="Classes" link="index.html#classes">
         <sub name="FontMap" link="class.FontMap.html" />
      </sub>
      <sub name="Functions" link="index.html#functions">
         <sub name="font_get_coverage" link="func.font_get_coverage.html" />
         <sub name="font_get_face" link="func.font_get_face.html" />
         <sub name="font_get_kerning" link="func.font_get_kerning.html" />
         <sub name="get_context" link="func.get_context.html" />
         <sub name="get_unknown_glyph" link="func.get_unknown_glyph.html" />
         <sub name="render" link="func.render.html" />
         <sub name="render_layout" link="func.render_layout.html" />
         <sub name="render_layout_line" link="func.render_layout_line.html" />
         <sub name="render_layout_line_subpixel" link="func.render_layout_line_subpixel.html" />
         <sub name="render_layout_subpixel" link="func.render_layout_subpixel.html" />
         <sub name="render_transformed" link="func.render_transformed.html" />
         <sub name="shutdown_display" link="func.shutdown_display.html" />
      </sub>
   </chapters>
   <functions>
      <keyword type="struct" name="PangoFT2FontMap" link="class.FontMap.html" />
      <keyword type="function" name="pango_ft2_font_map_create_context" link="method.FontMap.create_context.html" since="1.2" deprecated="1.22" />
      <keyword type="function" name="pango_ft2_font_map_set_default_substitute" link="method.FontMap.set_default_substitute.html" since="1.2" deprecated="1.46" />
      <keyword type="function" name="pango_ft2_font_map_set_resolution" link="method.FontMap.set_resolution.html" since="1.2" />
      <keyword type="function" name="pango_ft2_font_map_substitute_changed" link="method.FontMap.substitute_changed.html" since="1.2" deprecated="1.46" />
      <keyword type="function" name="pango_ft2_font_map_new" link="ctor.FontMap.new.html" since="1.2" />
      <keyword type="function" name="pango_ft2_font_map_for_display" link="type_func.FontMap.for_display.html" />
      <keyword type="function" name="pango_ft2_font_get_coverage" link="func.font_get_coverage.html" />
      <keyword type="function" name="pango_ft2_font_get_face" link="func.font_get_face.html" />
      <keyword type="function" name="pango_ft2_font_get_kerning" link="func.font_get_kerning.html" />
      <keyword type="function" name="pango_ft2_get_context" link="func.get_context.html" deprecated="1.22" />
      <keyword type="function" name="pango_ft2_get_unknown_glyph" link="func.get_unknown_glyph.html" />
      <keyword type="function" name="pango_ft2_render" link="func.render.html" />
      <keyword type="function" name="pango_ft2_render_layout" link="func.render_layout.html" />
      <keyword type="function" name="pango_ft2_render_layout_line" link="func.render_layout_line.html" />
      <keyword type="function" name="pango_ft2_render_layout_line_subpixel" link="func.render_layout_line_subpixel.html" since="1.6" />
      <keyword type="function" name="pango_ft2_render_layout_subpixel" link="func.render_layout_subpixel.html" since="1.6" />
      <keyword type="function" name="pango_ft2_render_transformed" link="func.render_transformed.html" since="1.6" />
      <keyword type="function" name="pango_ft2_shutdown_display" link="func.shutdown_display.html" />
   </functions>
</book>

As can be seen, there are no anchors in the links attribute, and thus the linkParts array is only 1 element long.
I don't know the internals of libhover, so I can't say if the correct fix would be to replace ParseDevHelp.java:505 with funcMap.put(linkParts.length > 1 ? linkParts[1] : nameValue, nameValue); or if that would cause other problems.

I have a gmon.out file generated by an assembly project. When I try to open it with gprof, I encounter an issue. When analyzing with gprof itself, the results I see appear correct. However, upon opening with gprof, I've noticed that the call relationships for a few functions are incorrect. Upon reviewing the code,

In gprof, when I inspect the data, observe the following:

When analyzing with the tool, notice the following:

I found that when these functions search for parent-child relationships in the elf file, the size of the parentSymbol they find is 0, and the program promptly returns. In reality, I would like to have the complete call relationships. Could you please advise on how to resolve this situation?

        IAddressFactory addressFactory = program.getAddressFactory();
        IAddress parentAddress = addressFactory.createAddress(Long.toString(from_pc));
		ISymbol parentSymbol = program.getSymbol(parentAddress);

        IAddress childAddress  = addressFactory.createAddress(Long.toString(self_pc));
		ISymbol childSymbol = program.getSymbol(childAddress);
		if (childSymbol == null || parentSymbol == null) {
            return;
        }

@Override
	public ISymbol getSymbol(IAddress addr) {
		ISymbol[] syms = getSymbols();
		int insertion = Arrays.binarySearch(syms, addr);
		if (insertion >= 0) {
			return syms[insertion];
		}
		if (insertion == -1) {
			return null;
		}
		insertion = -insertion - 1;
		ISymbol symbol = syms[insertion - 1];
		if (addr.compareTo(symbol.getAddress().add(symbol.getSize())) < 0) {
			return syms[insertion - 1];
		}
		return null;
	}

With certain images, attempting to do a copy from the file system to the host fails unless "seccomp=undefined" is specified.

Similarly, when trying to run a command such as "meson" it may need to determine what is installed and will fail trying to access /usr/bin. The same "seccomp=undefined" is required.

Add the ability to specify seccomp on a runCommand (already is enabled for launching) and for a CloseableContainer used for copying from container.

Hi,
test case is to run a runtime with all linuxtools bundles with java17. the are equinox resolution errors logged (see below)
this is likely same as https://bugs.eclipse.org/bugs/show_bug.cgi?id=564339

!ENTRY org.eclipse.linuxtools.docker.integration.tests 4 0 2022-08-05 12:45:59.713
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.docker.integration.tests [279]
  Bundle was not resolved because of a uses constraint violation.
  org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.eclipse.linuxtools.docker.integration.tests [osgi.identity; osgi.identity="org.eclipse.linuxtools.docker.integration.tests"; type="osgi.bundle"; version:Version="2.2.0.qualifier"; singleton:="true"] because it is exposed to package 'org.hamcrest' from resources org.hamcrest [osgi.identity; osgi.identity="org.hamcrest"; type="osgi.bundle"; version:Version="2.2.0.v20210711-0821"] and org.hamcrest.core [osgi.identity; osgi.identity="org.hamcrest.core"; type="osgi.bundle"; version:Version="1.3.0.v20180420-1519"] via two dependency chains.

Chain 1:
  org.eclipse.linuxtools.docker.integration.tests [osgi.identity; osgi.identity="org.eclipse.linuxtools.docker.integration.tests"; type="osgi.bundle"; version:Version="2.2.0.qualifier"; singleton:="true"]
    import: (osgi.wiring.package=org.hamcrest)
     |
    export: osgi.wiring.package: org.hamcrest
  org.hamcrest [osgi.identity; osgi.identity="org.hamcrest"; type="osgi.bundle"; version:Version="2.2.0.v20210711-0821"]

Chain 2:
  org.eclipse.linuxtools.docker.integration.tests [osgi.identity; osgi.identity="org.eclipse.linuxtools.docker.integration.tests"; type="osgi.bundle"; version:Version="2.2.0.qualifier"; singleton:="true"]
    require: (osgi.wiring.bundle=org.junit)
     |
    provide: osgi.wiring.bundle: org.junit
  org.hamcrest.core [osgi.identity; osgi.identity="org.hamcrest.core"; type="osgi.bundle"; version:Version="1.3.0.v20180420-1519"]
	at org.eclipse.osgi.container.Module.start(Module.java:463)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1781)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

Changes to gcc 12 gcov are not compatible with the current Linux Tools code coverage gcov profiling support.

Docker Desktop for macOS 4.6.1, on Monterey 12.3 running on M1 Mac.

Docker Tooling in AArch64 version of Eclipse Embedded for C/C++ is unable to connect to Docker Backend (via Unix socket).

Same setup with x86_64 version of Eclipse Embedded for C/C++ (running via Rosetta) is able to connect and execute build in Docker image.

Tested with 2022-03, and 2021-12. Docker Tooling is not working on AArch64 Eclipse.

When trying to launch a shell for a running container by selecting "Execute Shell" option from the container context menu, it is launching a non-interactive shell. The shell doesn't respond any input from the keyboard. It remains a blank shell.

Processor:
Intel Core i7

OS:
macOS Montery 12.6.1 (21G217)

Eclipse:
Version: 2022-09 (4.25.0)
Build id: 20220908-1902

Docker Tooling:
5.8.0.202209062047

Steps to reproduce

1. Run any docker container from Docker Explorer.
2. Right click on the container.
3. Click "Execute Shell".
4. Type any command/text in the opened shell.

Expected behaviour:
The command/text should be typed in the opened shell.

Actual Behaviour:
The shell remains blank. The command doesn't get typed into the shell.

I recently checked out the source code of the Eclipse Linux Tools. The Eclipse Linux Tools do not provide a preconfigured setup like some other Eclipse projects (e.g. JDT). Therefore I used my main Eclipse installation which had Eclipse Linux Tools but not TM4E installed.

When looking at Dockerfile.tmLanguage, the editor is full of errors. It seems that the file is interpreted as Dockerfile, probably due to the changes from #50 .

I suppose the easiest fix is to just rename the grammar file.

There are multiple pullImage methods found in IDockerConnection. One of these throws an org.mandas.docker.client exception called DockerCertificateException and should not have exposed the org.mandas.docker-client. For some reason, even if the other clean pullImage() method is used by a third-party plug-in, Eclipse requires org.mandas.docker-client bundle be specified by the third-party plug-in or it is marked in error saying it references the org.mandas.docker.client.exceptions.DockerCertificateException.

To counter this, create a new public DockerCertificateException class to wrap the org.mandas.docker-client version and create two new methods: pullImageWithHandler() with the same parameters and logic as their old pullImage() methods, but have one of them throw the new DockerCertificateException to keep the interface clean. As such, the other methods should be deprecated.

I have verified this works to solve the problem and a third-party plug-in can call either method without having to require org.mandas.docker-client.

What is the format of a. out file? If there is other data, how can a. out file be generated？

Because in my project, I have another trace that I want to use to parse out a. out file and display the results directly through org. eclipse. linuxtools

I don't know if this is feasible

Looking forward to your answer！

When trying to use the docker compose integration of the Docker Tooling under Windows 10 with installed Docker for Desktop 4+ only a messagebox with the error "The 'docker-compose.exe' command could not be located in 'C:\Program Files\Docker Toolbox'" appears.

The docker-compse.exe is deprecated in newer Docker versions and are integrated in the docker command.
Instead of using docker-compose.exe the command docker compose should be used.

Build Docker Image stopped working, details below.

To reproduce: New workspace -> new general project -> new file -> Dockerfile (attached)

Right click Dockerfile -> Run As -> Docker Image Build

Currently using Docker Desktop 4.22.0

Error log:

eclipse.buildId=4.28.0.20230608-1200
java.version=20.0.1
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=nl_BE
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product

org.eclipse.core.jobs
Error
Thu Aug 10 11:50:18 CEST 2023
An internal error occurred during: "Building Docker Image".

java.lang.NullPointerException: configs value
at java.base/java.util.Objects.requireNonNull(Objects.java:259)
at org.mandas.docker.client.messages.ImmutableRegistryConfigs$Builder.addConfig(ImmutableRegistryConfigs.java:145)
at org.mandas.docker.client.messages.ImmutableRegistryConfigs$Builder.addConfig(ImmutableRegistryConfigs.java:116)
at org.mandas.docker.client.DockerConfigReader.authForAllRegistries(DockerConfigReader.java:140)
at org.mandas.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:107)
at org.mandas.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1413)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.buildImage(DockerConnection.java:1478)
at org.eclipse.linuxtools.internal.docker.ui.jobs.BuildDockerImageJob.run(BuildDockerImageJob.java:163)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Test.zip

I have tried to use the mvn install command to compile the org.eclipse.linuxtools project, but I've encountered various errors. I feel unable to resolve these errors myself. Could you please share how you compile the org.eclipse.linuxtools project? Do you use any other tools?

My Java version is java 21, and my Maven version is Maven 3.9.6.

Looking forward to your reply.thanks

Hello,

We are using this linuxtools project to do code coverage and profiling for embedded system such as arm and riscv, but the toolchain will have a prefix such as riscv64-unknown-elf-gprof/gcov, but the plugin itself seems to bind with a fixed name, is it possible to let user to set it in project properites, which will make embedded development possible to use this great plugin in eclipse cdt.

Like in the embedded cdt plugin https://github.com/eclipse-embed-cdt/eclipse-plugins, it will provide prefix settings

Maybe it will great to set this linux tools prefix in its configuration page, but currently it is not possible.

So to use this profiling and coverage feature in embedded software development, I have to change the gprof and gcov related binaries from its prefixed ones to unprefixed ones like this.

Otherwise the IDE will become not-responding.

Thanks

Oomph recently updated to use a newer bcprov dependency (1.78.1). As a result the org.mandas.docker-client bundle required for the docker tools will no longer start.

org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.docker.core [4158]
  Unresolved requirement: Require-Bundle: org.mandas.docker-client; bundle-version="7.0.7"
    -> Bundle-SymbolicName: org.mandas.docker-client; bundle-version="7.0.7"
       org.mandas.docker-client [4172]
         Unresolved requirement: Import-Package: com.fasterxml.jackson.jakarta.rs.json; version="[2.16.0,3.0.0)"; resolution:="optional"
         Unresolved requirement: Import-Package: com.google.auth.oauth2; resolution:="optional"
         Unresolved requirement: Import-Package: org.jboss.resteasy.client.jaxrs; resolution:="optional"
         Unresolved requirement: Import-Package: org.jboss.resteasy.client.jaxrs.engines; resolution:="optional"
  Bundle was not resolved because of a uses constraint violation.
  org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.mandas.docker-client [osgi.identity; type="osgi.bundle"; version:Version="7.0.7"; osgi.identity="org.mandas.docker-client"] because it is exposed to package 'org.bouncycastle.asn1.pkcs' from resources bcprov [osgi.identity; type="osgi.bundle"; version:Version="1.78.1"; osgi.identity="bcprov"] and org.bouncycastle.bcprov [osgi.identity; type="osgi.bundle"; version:Version="1.72.0.v20221013-1810"; osgi.identity="org.bouncycastle.bcprov"] via two dependency chains.

Chain 1:
  org.mandas.docker-client [osgi.identity; type="osgi.bundle"; version:Version="7.0.7"; osgi.identity="org.mandas.docker-client"]
    import: (&(osgi.wiring.package=org.bouncycastle.asn1.pkcs)(&(version>=1.77.0)(!(version>=2.0.0))))
     |
    export: osgi.wiring.package: org.bouncycastle.asn1.pkcs
  bcprov [osgi.identity; type="osgi.bundle"; version:Version="1.78.1"; osgi.identity="bcprov"]

Chain 2:
  org.mandas.docker-client [osgi.identity; type="osgi.bundle"; version:Version="7.0.7"; osgi.identity="org.mandas.docker-client"]
    import: (&(osgi.wiring.package=org.bouncycastle.openssl)(&(version>=1.77.0)(!(version>=2.0.0))))
     |
    export: osgi.wiring.package=org.bouncycastle.openssl; uses:=org.bouncycastle.asn1.pkcs
  bcpkix [osgi.identity; type="osgi.bundle"; version:Version="1.77.0"; osgi.identity="bcpkix"]
    import: (&(osgi.wiring.package=org.bouncycastle.asn1.pkcs)(version>=1.72.0))
     |
    export: osgi.wiring.package: org.bouncycastle.asn1.pkcs
  org.bouncycastle.bcprov [osgi.identity; type="osgi.bundle"; version:Version="1.72.0.v20221013-1810"; osgi.identity="org.bouncycastle.bcprov"]
	at org.eclipse.osgi.container.Module.start(Module.java:493)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:2073)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:143)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:2064)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:2004)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1967)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1883)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:341)

This is kind of unexpected and should be documented

Reproduce:

• make sure you have no alpine image on your system
• Pull "alpine"

I just need the gprof and gcov modules in the profiling of linuxtools, and want to compile them into installable plug-ins.

I followed the instructions of Creating Source Tarball section from this link , but I ran into some problems.

@akurtakov Could you give me a hand?

% mvn clean compile assembly:single -e
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Tycho Version: 4.0.0-SNAPSHOT (5fb874c2aa16bbdb673d41599dc2b2c651b854ce)
[INFO] Tycho Mode: project
[INFO] Tycho Builder: maven
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Linux Tools GProf Parent [pom]
[INFO] Linux Tools GProf Plug-in [eclipse-plugin]
[INFO] Linux Tools Gprof Documentation Plug-in [eclipse-plugin]
[INFO] Linux Tools GProf Launch Plug-in [eclipse-plugin]
[INFO] Linux Tools GProf Integration Feature [eclipse-feature]
[INFO] Linux Tools GProf Tests Plug-in [eclipse-test-plugin]
[INFO]
[INFO] --------< org.eclipse.linuxtools.gprof:linuxtools-gprof-parent >--------
[INFO] Building Linux Tools GProf Parent 8.11.0-SNAPSHOT [1/6]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ linuxtools-gprof-parent ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.8:prepare-agent (pre-test) @ linuxtools-gprof-parent ---
[INFO] argLine set to -javaagent:/home/user/.m2/repository/org/jacoco/org.jacoco.agent/0.8.8/org.jacoco.agent-0.8.8-runtime.jar=destfile=/home/user/org.eclipse.linuxtools/gprof/../../target/jacoco.exec,append=true,includes=org.eclipse.linuxtools.*
[INFO]
[INFO] --- maven-assembly-plugin:2.2-beta-5:single (default-cli) @ linuxtools-gprof-parent ---
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Linux Tools GProf Parent 8.11.0-SNAPSHOT ........... FAILURE [ 0.141 s]
[INFO] Linux Tools GProf Plug-in 5.1.0-SNAPSHOT ........... SKIPPED
[INFO] Linux Tools Gprof Documentation Plug-in 1.0.0-SNAPSHOT SKIPPED
[INFO] Linux Tools GProf Launch Plug-in 1.2.0-SNAPSHOT .... SKIPPED
[INFO] Linux Tools GProf Integration Feature 8.11.0-SNAPSHOT SKIPPED
[INFO] Linux Tools GProf Tests Plug-in 5.1.0-SNAPSHOT ..... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.782 s
[INFO] Finished at: 2023-04-18T17:27:33+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single (default-cli) on project linuxtools-gprof-parent: Error reading assemblies: No assembly descriptors found. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single (default-cli) on project linuxtools-gprof-parent: Error reading assemblies: No assembly descriptors found.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error reading assemblies: No assembly descriptors found.
at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute (AbstractAssemblyMojo.java:356)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.assembly.io.AssemblyReadException: No assembly descriptors found.
at org.apache.maven.plugin.assembly.io.DefaultAssemblyReader.readAssemblies (DefaultAssemblyReader.java:206)
at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute (AbstractAssemblyMojo.java:352)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

While waiting for the build result of #37, I decided to try the link to the Jenkins job by clicking on "Details" next to the Jenkins line in the browser.
At the time of this report, the link points to https://ci.eclipse.org/linuxtools/job/linuxtools/job/PR-37/display/redirect, but clicking on that link and signing in just gives:

Access Denied
[email protected] is missing the Job/Build permission

I suppose the link should work regardless if you are a committer on the linuxtools project or just a regular contributor. I'm not stating that all contributors should have build permission, but I suppose the link could point to https://ci.eclipse.org/linuxtools/job/linuxtools/job/PR-37/1/ or something similar.
Obviously, I've masked my email to avoid spambots from collecting it ([email protected] is my real address).

Environment

Windows 10
Open JDK 17.0.4
Running from sources: CDT (main) + Linux Tools (master)

Steps to reproduce

• Run container
• Select "Execute Shell"
• Start typing command
  => Exception in the log, typed command is not visible

!ENTRY org.eclipse.linuxtools.docker.core 4 0 2023-05-11 18:16:07.841
!MESSAGE Unable to make field protected volatile java.io.InputStream java.io.FilterInputStream.in accessible: module java.base does not "opens java.io" to unnamed module @4f90225
!STACK 0
java.lang.reflect.InaccessibleObjectException: Unable to make field protected volatile java.io.InputStream java.io.FilterInputStream.in accessible: module java.base does not "opens java.io" to unnamed module @4f90225
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
	at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
	at java.base/java.lang.reflect.Field.setAccessible(Field.java:172)
	at org.eclipse.linuxtools.internal.docker.core.HttpHijackWorkaround.getInternalField(HttpHijackWorkaround.java:161)
	at org.eclipse.linuxtools.internal.docker.core.HttpHijackWorkaround.getOutputStream(HttpHijackWorkaround.java:116)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.openTerminal(DockerConnection.java:2350)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.execShell(DockerConnection.java:2318)
	at org.eclipse.linuxtools.internal.docker.ui.commands.ExecContainerCommandHandler.executeInJob(ExecContainerCommandHandler.java:39)
	at org.eclipse.linuxtools.internal.docker.ui.commands.BaseContainersCommandHandler$1.run(BaseContainersCommandHandler.java:60)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

The maven build for Linuxtools has an exception after success, see full log here

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:12 min
[INFO] Finished at: 2024-02-21T14:53:05-05:00
[INFO] ------------------------------------------------------------------------
Exception in thread "Thread-4" java.lang.NoClassDefFoundError: org/eclipse/jgit/internal/JGitText
	at org.eclipse.jgit.internal.util.ShutdownHook.cleanup(ShutdownHook.java:85)
	at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.ClassNotFoundException: org.eclipse.jgit.internal.JGitText
	... 2 more

@akurtakov I know you are working on this at the moment, but in recent days the Eclipse CDT build breaks:

Error:  Cannot resolve target definition:
Error:    Software being installed: org.eclipse.linuxtools.docker.feature.feature.group 5.12.0.202307201237
Error:    Missing requirement: com.google.guava 32.1.1.jre requires 'java.package; com.google.common.util.concurrent.internal [1.0.0,2.0.0)' but it could not be found
Error:    Cannot satisfy dependency: org.eclipse.linuxtools.docker.core 5.12.0.202307201237 depends on: osgi.bundle; com.google.guava 32.1.1
Error:    Cannot satisfy dependency: org.eclipse.linuxtools.docker.feature.feature.group 5.12.0.202307201237 depends on: org.eclipse.equinox.p2.iu; org.eclipse.linuxtools.docker.core [5.12.0.202307201237,5.12.0.202307201237]

See PRs:

• eclipse-cdt/cdt#470
• eclipse-cdt/cdt#471

If you aren't done yet I will revert to latest release of linuxtools docker for now and rejoin nightly when you want me to test it out again.

There are some new warning in Docker tooling usage of Jersey. Presumably related to #314

Feb. 29, 2024 3:45:25 P.M. org.glassfish.jersey.client.innate.inject.NonInjectionManager <init>
WARNING: Falling back to injection-less client.

This comes from a stack like this:

	at org.glassfish.jersey.client.innate.inject.NonInjectionManager.<init>(NonInjectionManager.java:212)
	at org.glassfish.jersey.client.ClientConfig$State.findInjectionManager(ClientConfig.java:484)
	at org.glassfish.jersey.client.ClientConfig$State.initRuntime(ClientConfig.java:419)
	at org.glassfish.jersey.internal.util.collection.Values$LazyValueImpl.get(Values.java:317)
	at org.glassfish.jersey.client.ClientConfig.getRuntime(ClientConfig.java:834)
	at org.glassfish.jersey.client.ClientRequest.getClientRuntime(ClientRequest.java:181)
	at org.glassfish.jersey.client.JerseyWebTarget.onBuilder(JerseyWebTarget.java:371)
	at org.glassfish.jersey.client.JerseyWebTarget.request(JerseyWebTarget.java:214)
	at org.glassfish.jersey.client.JerseyWebTarget.request(JerseyWebTarget.java:38)
	at org.mandas.docker.client.DefaultDockerClient.info(DefaultDockerClient.java:391)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getInfo(DockerConnection.java:433)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.setClient(DockerConnection.java:303)
	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:272)
	at org.eclipse.linuxtools.internal.docker.core.DefaultTCPConnectionSettingsProvider.getConnectionSettings(DefaultTCPConnectionSettingsProvider.java:32)
	at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.getKnownConnectionSettings(DefaultDockerConnectionSettingsFinder.java:210)
	at org.eclipse.linuxtools.docker.core.DockerConnectionManager.lambda$reloadConnections$0(DockerConnectionManager.java:64)
	at java.base/java.lang.Thread.run(Thread.java:833)

Perhaps related to

Compare the list of Devhelp books read by Libhover versus the Gnome Devhelp tool:

You can see that Libhover misses out a bunch of Devhelp books. You may also have noticed that you see no books at all by default when running inside a flatpak container.

The problem is that you may specify exactly one directory in the Libhover prefs but Devhelp books may be installed in a few different locations.

I would like to enhance Libhover Devhelp to correct find all locations containing Devhelp books, including locations on the sandbox host when running in a sandbox.

Some tools (e.g. Buildah) support Containerfile as an alternative to Dockerfile.

It would be nice if the Eclipse Linux Tools offered syntax highlighting for Containerfile-

Sonoma 14.3, Eclipse 2024-3, Docker for Mac 4.27, on M2 Mini. All software are Aarch64 native.

Docker tooling was working on previous version of Eclipse (2023-9) for this system with previous versions of Sonoma and Docker.

However, after I upgraded macOS, Docker and Eclipse to the latest version (2024-3 for Aarch64), Docker Explorer fails to connect to encounters an error when accessing the Docker socket with the following error:

An internal error occurred during: "Opening connection 'unix:///var/run/docker.sock'[unix:///var/run/docker.sock]...". Cannot invoke "String.startsWith(String)" because "s" is null

/var/run/docker.sock is linked to the macOS user specific socket. I can check docker images via terminal as usual using 'docker images'

Originally posted by @tcwan in #61 (comment)

Edit: Retitled issue, I think it has to do with new version of Sonoma as I tried with a reinstalled Eclipse 2023-9 and it didn't work either.
Edit2: Retitled to indicate issue with Docker 4.27. I found out that the error with docker.sock affects listing of images, whereas containers can be listed despite the error.

Hello, I see gprof also provide call graph features but its call graph is just show in excel like format, which cannot render as a graph which provided by systemtap callgraph plugin as described https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.linuxtools.callgraph.docs%2FLinux_Tools_Project%2FCallgraph%2FUser_Guide%2FGeneral-Usage2.html

Is it possible to use the gprof parsed call graph to draw call graph using this plugin, can somebody give me some hints about how to achieve it.

There is a python script https://github.com/jrfonseca/gprof2dot to draw call graph using gmon.out like this below, I think it might be possible to achieve same effect using existing linux tools's callgraph plugin

Thanks

RedDeer is retiring from Eclipse Simrel and Docker tooling tests are already using Swtbot in tests (https://github.com/eclipse-linuxtools/org.eclipse.linuxtools/tree/master/containers/org.eclipse.linuxtools.docker.ui.tests) thus it make sense to convert the RedDeer ones into Swtbot ones(https://github.com/eclipse-linuxtools/org.eclipse.linuxtools/tree/master/containers/org.eclipse.linuxtools.docker.integration.tests) to have unified testing framework.
The tests in question are:

org.eclipse.linuxtools.docker.integration.tests.connection 9.3 sec 0 0 1 1
org.eclipse.linuxtools.docker.integration.tests.container 2 min 58 sec 0 0 13 13
org.eclipse.linuxtools.docker.integration.tests.image 1 min 41 sec 0 2 7 9
org.eclipse.linuxtools.docker.integration.tests.ui 2 min 43 sec 0 1 12 13

The newer versions of EPP (since 2021-12) now ship with Java 17 included. In the Docker terminal support, reflection is used to access a socket instance and this requires accessing public/non-public fields of the java.base JVM module. To run Docker terminal, --add-opens statements must be added to -vmargs when running Eclipse or else they must be put in the eclipse.ini file for -vmargs

The following statements are needed:

--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.base/sun.nio.ch=ALL-UNNAMED
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens=java.base/sun.security.ssl=ALL-UNNAMED

Failure to do so causes java.lang.reflect.InaccessibleObjectException to occur

Bug 578660 has been created to track this in bugzilla