Code issue related to import in talend 7.3.1 jobs - talend

Recently we have installed talend 7.3.1 in our virtual machine. There is a git repository which stores all of our jobs. while opening some jobs , I get The import cannot be resolved error in the code tab of the talend job. When I hover over the under lined error message , I get an option to fix the project setup which when selected performs a background operation and the error gets resolved.
There are many jobs with this issue and I am looking for a solution which fixes the issue in all jobs in one shot.

I have force fully re-synchronized poms and applied the change as per the below screen shot and the issue got resolved.

Related

How do I debug a java.lang.illegalStateException that occurs when rebasing a ClearCase view?

Background
I have been trying for the last week to rebase a clearcase view for my project, but every time I try I get a weird null exception depicted in the two windows below:
I do not know why this is occurring and need help determining how to even begin fixing this issue.
So far here is what I have tried:
Restarting the client
Restarting my computer
Refreshing the view and updating.
Updating my eclipse environment.
I have also seen a fix on the IBM website for a similar issue, but my version of Clearteam explorer is well beyond the version it prescribes for a fix:
When you are trying to login with the IBM Rational ClearTeam
Explorer (CTE) version 8.0.1.11 and later with the Eclipse
plugin, you may receive the following error: CRMAP7009: Command
"Login" failed: Error: "java.lang.IllegalStateException: null"
This behavior does not occur with CTE 8.0.1.10 with the Eclipse
plugin or with the standalone CTE 8.0.1.11 client.
It only occurs using the Sun JRE 6, not when using the IBM JRE
6.
My clearteam explorer version is 9.0.2:
Question
What are other possible actions I can take to fix the null pointer issue mentioned above?
OK, you're going to hate this, but the only thing I can do is ask questions and point you to IBM/HCL support.
Is this a web-based view? A snapshot view? A Dynamic view?
Does a new view work?
Are there any errors in the CTE workspace log? (%USERPROFILE%.Rational\CTE8\workspace.log)
Is this the CTE plugin installed into Eclipse? Or the CTE "full" client? And does it matter?
Have you tried this using the command line interface (cleartool/rcleartool as appropriate)
Does running in debug mode tell us anything additional? (See https://www.ibm.com/support/pages/how-enable-trace-ccrc-client-and-server) Note that on windows, CTE/eclipse will spawn a separate console window to print some eclipse diagnostic output that may or may not be important. You'll want to capture that before exiting the session.
If this is a web-based view, has anyone checked the WAN server logs?
CRMAP7009 is a "catch all" message for CTE, but since that is an exception message, it should be expanded upon SOMEWHERE. Half the battle is finding the rest of the message.
In those case, I always try and fall back to command line, using in your case cleartool rebase.
See "Rebase a stream on linux using cleartool" (the same idea applies on Windows), and "How to rebase in ClearCase on latest baselines?".
That way, I can see if the issue is with ClearCase itself or with the Eclipse ClearCase plugin.

Why am I getting an error when loading webviews in VS Code?

I'm using a portable install of VS Code 1.56.1 on Windows 10. Whenever open an extension from the marketplace, I get the following error:
Error loading webview: Error: Could not register service workers: TypeError: Failed to register a ServiceWorker for scope ('vscode-webview://extensioneditor/') with script ('vscode-webview://extensioneditor/service-worker.js?platform=electron&id=extensionEditor&vscode-resource-origin=https%3A%2F%2FextensionEditor.vscode-webview-test.com'): ServiceWorker cannot be started.
Same thing happens for other things using webviews, with a slightly different path (like VS Code release notes). I'm able to install plugins and view the Feature Contributions tab, but I cannot view the Details and Changelog tabs.
Any thoughts on what could be causing this? This is on a managed machine where security settings might be changing. I'm using a portable install because my installed version stopped working out of the blue last week and this was supposed to be the workaround until that was figured out.
I was getting the same error, it looks like an issue introduced on version 1.56.0.
For me the fix was running VS Code without elevated permissions.
I always run as administrator and running without it fixed the issue for me.
I had this problem, in terminal use code . --no-sandbox
Updating python3 to the most recent version may also help.

Error running Specflow tests consecutively

I was wondering if anybody could help with an issue I have come across, I have recently added to my test framework the sharing of a value using feature content
This has been placed in the [BeforeScenario] trigger
FeatureContext.Current.Add("CreatedUser", createdUser);
I then clean this up in the [AfterScenario] with
FeatureContext.Current.Remove("CreatedUser");
Since adding this I am unable to run more then 1 test, if I run the tests individually (1 by 1) then they execute with no issue.
If I select a few tests to run from visual studio, the first one runs with no issue and the next test will always fail with the following error.
Message: System.Collections.Generic.KeyNotFoundException : The given key was not present in the dictionary.
TearDown : System.NullReferenceException : Object reference not set to an instance of an object.
I added the remove line as i thought the feature context was being carried from test to test and causing an issue but with or without the removal i am getting this error.
Any help is appreciated
I eventually managed to fix this issue by removing the Allure NuGet packages.
I had previously installed
Specflow.Allure
Allure.Commons
This package was causing the issue, I am not sure of the reason but after removing this error stopped occurring.

SWbot testcases hanging in jenkins build

Followed the instructions given over here http://wiki.eclipse.org/SWTBot/Automate_test_execution#On_Jenkins and successfully did the integration were the swtbot testcases worked fine but now all of sudden after adding few more swtbot testcases it started hanging and completely stopped working!
Things which I tried till now are,
-> Ran the testcases in Linux local server which passes without any issue but the same in jenkins hangs now.
-> Changing Xvfb process to Xvnc -> Still same issue, build hangs
-> Commented all swtbot testcase and added simple test like creating a project which works fine without any issues.
-> Changed the jenkins server to new slave to make sure if it's DISPLAY issue but again same problem in the new slave.
-> Used NX Client to track the UI flow which happen in jenkins server via sandbox build but fails with widget not found exception.
-> Used upgraded SWTBot plugin but no help
Mailed to swtbot-dev#eclipse.org 4 days back but no reply still! Can someone please help me in this asap? Not sure what else to try with to resolve this problem now.
Thanks.
When you connect via VNC, try checking out if there's not any other modal window hiding behind the Eclipse workbench. We used to have problems especially with the "Usage data" window.
Found the issue finally and fixed the problem!
Our testcases involves checking the shortcut keys which are meant for table operations such as, inserting a new row - insert key, delete a row - delete key and so on..
It seems that when swtbot executes the keystroke as,
bot.shell("").pressShortcut(Keystrokes.DELETE);
it makes the entire eclipse to hang. Am still not sure what is the reason behind it, so replaced DELETE with CTRL + Q key combination in our implementation code and then it started working fine.
Eclipse hangs even when some keystroke is added in the testcase which doesn't do any ui operations. So, did those cleanup and all the testcases are passing now :)
Seems to be a another limitation in swtbot and hope that development team will analyze this further if possible. Already have posted it in eclipse community as well. http://www.eclipse.org/forums/index.php/m/1234514/#msg_1234514
Thanks to Cpt. Senkfuss and Lula for your suggestions!!

Github failed to sync branch

I'm using W7 64 bi , and just got an error from the github client app. It says:
failed to sync branch. you might need to open a shell and debug the state of this repo.
What do I do now ?
I know this will sound crazy, but try restarting your computer.
This happend to me yesterday; I was getting this error, and upon checking: \AppData\Local\GitHub\TheLog.txt
I found messages like:
AppData\Local\GitHub\PortableGit_ca477551eeb4aea0e4ae9fcd3358bd96720bb5c8\bin\sh.exe:
*** Couldn't reserve space for cygwin's heap, Win32 error 0
The problem comes around to GitHub for Windows updating itself (in particular the cygwin-ized PortableGit) in the background while I was using it. Ultimately, some cygwin dlls from the previous PortableGit dlls were still loaded in memory causing errors when trying to execute the new (updated) PortableGit commands.
Restarting cleared out all the previously loaded cygwin dlls.
You might have a more complex problem than my answer can solve, but -- for anyone else who comes across this question -- some basic solutions can be found in this video. In short, status.github.com, git status, and gitstatus are your friends. See what they tell you and then continue your sleuthing with that new information in mind. You can use these tools using Git Shell that comes with the Github Windows client.
I'll note that my own problem stemmed from trying to sync a file that was too large: I only found this by using the Git Shell, which gave me the error when I tried git sync. I'm currently looking for ways to remove the file in question in previous commits so I can sync my repo appropriately. The guide I am currently following can be found here, and if it seems to be taking me in the right direction (it was actually recommended in the Git Shell error message!)
I had this error before, and I fixed it by reinserting the credentials for my github account. Turns out that github logged me out for some reason