"Problems during content assist" with studio 8.0.1

[selimseddiki]

Hi,

We have recently installed Talend v8.0.1 on a Windows 10 Pro machine.

When I try to add a repository context group and use it in a tjava doing context. and CTR-SPACE, I have the following message :

The 'org.talend.designer.core.tos.variables' proposal from the '

org.talend.designer.core

' plug-in did not complete normally.

Thank you in advance

[Anonymous]

This could be due to a number of things. The most obvious (without looking at the installation) is that you have not installed Talend as close to the root of the drive as possible. Unfortunately Windows 10 has a maximum path length of 260 chars (see this: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry). Now the Talend installation paths can exceed this if the base folder is not as close to the root of the drive as possible.

That is just one option, but does (understandably) catch a lot of people out. If you think this could be the cause, simply move the base folder to somewhere else. If you do not think this is the cause, I would raise a Support call.

[selimseddiki]

Hi Rhall,

It does not seem to be the cause since Talend v8 install directory is in the root of C:/

Thank you !

Best regards, Sélim

[selimseddiki]

Are there other potential causes of the issue ?

[Anonymous]

I think it is best you raise this with Support.

[Anonymous]

Hello,

What's JDK version are you using?

We've seen this in the past already on some JRE.

Change to another JVM then it was fine (JDK). Not sure if it's the case here of course !

If not, we need to analyze the logs if possible.

Best regards

Sabrina

[selimseddiki]

Hi Sabrina, we are using the JDK jdk-11.0.17. Please find the logs below.

[Anonymous]

Hello,

The studio log is located in <Talend Studio installation path>/workspace/.metadata/.log

Could you please raise a support case on talend support portal so that we could give you a remote assistance to deliver a patch to you if needed?

Best regards

Sabrina

[selimseddiki · Accepted solution]

installing the latest patch (R202212) has resolved the issue.

Many thanks!