When I want to install IBM WDT V8.5 via MarketPlace, I get this error:
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Failed to transfer artifact canonical: osgi.bundle,com.ibm.websphere.v85.core,1.0.200.v20170613_0418.
Connection to http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/oxygen_comp/repository/plugins/com.ibm.websphere.v85.core_1.0.200.v20170613_0418.jar failed on Read timed out.
.
.
.
Retry attempt 15 started
Read timed out
Unable to read repository at http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/oxygen_comp/repository/plugins/com.ibm.websphere.v85.core_1.0.200.v20170613_0418.jar.
Read timed out
The download of the file always freezes after about 2.9 MB. The same problem occurs when trying to download the file in a browser. The resource is however downloadable via secured https.
I tried Oxygen and Oxygen1 versions of Eclipse.
How to fix it? Or at least, is there any workaround?
The jar file that you mentioned is not available any longer. It has been replaced by:
http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/oxygen_comp/repository/plugins/com.ibm.websphere.v85.core_1.0.200.v20171214_0201.jar
I was able to successfully install WDT via Eclipse marketplace using Oxygen.
Related
I tried to run expo start or yarn start and the console threw an error. On wsl1 it is working fine, it shows the QR code. However, I have to switch to wsl2 to set up mysql for my local server and now expo is not starting.
Also sometimes the QR code shows up but when I try to open the app in my device, the same error shows up.
Developer tools running on http://localhost:19002
Could not get status from Metro bundler. connect ECONNREFUSED 127.0.0.1:19001
Connecting to Metro bundler failed.
Error: Connecting to Metro bundler failed.
at _waitForRunningAsync (/home/kevsmercs/.nvm/versions/node/v12.13.0/lib/node_modules/expo-cli/node_modules/xdl/src/start/startLegacyReactNativeServerAsync.ts:344:11)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
I think the problem here is expo itself. I tried to I check the developer tools url, the site cant be reached. I also tried to check my account using expo login and this error shows up
Fetching the user profile failed
connect ECONNREFUSED 127.0.0.1:8888
connect ECONNREFUSED 127.0.0.1:8888
Error: connect ECONNREFUSED 127.0.0.1:8888
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1128:14)
jest-haste-map: Watchman crawl failed. Retrying once with node crawler. Usually this happens when watchman isn't running. Create an empty .watchmanconfig file in your project's root folder or initialize a git or hg repository in your project. Error: Watchman error: query failed: synchronization failed: Connection timed out. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.html.
I tried multiple fixes but no luck.
1. set `REACT_NATIVE_PACKAGER_HOSTNAME` to my ip using `export`
2. delete `.expo` from root of project and run `expo start -c`
3. turn off windows defender and firewall
4. update `expo-cli` to latest (4.4.1)
5. restart laptop
Maybe this GitHub issue describes your problem and the workaround?
This can usually happen when publishing without ever having run expo start, also it's a good idea to run rm -rf .expo to clear your local state
it's listed in our common development errors
Your latest edit shows this error message and suggested fix: Usually this happens when watchman isn't running. Create an empty .watchmanconfig file in your project's root folder or initialize a git or hg repository in your project. Did you try that?
I have a CKAN 2.8 installed on an Ubuntu 16.04 server and I have successfully configured filestore, datastore and datapusher. Whenever I try to upload a to datastore, I get the message "Error: Process completed but unable to post to result_url" and the status says pending. I have set SSL_VERIFY to FALSE in datapusher_settings.py but the error kept coming. Anyone who can help with this?
Thanks.
To get the JDBC Hook working, I first add in the jaydebeapi package in the PYPI packages page in Composer.
However, that alone does not allow a JDBC connection to work:
1) How do I specify the .jar driver path for the JDBC driver I have?
I was thinking it would be something like "/home/airflow/gcs/drivers/xxx.jar" (assuming I've created a drivers folder in the gcs directory)... but I haven't been able to verify or find documentation on this.
2)How do I install/point toward the Java JRE? On Ubuntu I run this command to install JRE: sudo apt-get install default-jre libc6-i386. Is a JRE or ability to install a JRE available in Cloud Composer? This is the current error message I get in the Adhoc window with the JDBC connection: [Errno 2] No such file or directory: '/usr/lib/jvm'
If either of the above options are not currently available, are there any workarounds to get a JDBC connection working with Composer?
There are known issues with JDBC issues in Airflow 1.9 (https://github.com/apache/incubator-airflow/pull/3257); hopefully, we should be able to backport these fixes in Composer by GA!
I'm trying to use an older version of Firefox on AWS (running selenium, 55 isn't compatible) but I haven't had any luck. When I try to download the compressed older files, I get
(firefox:6186): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally without any error message
Any ways to fix this/alternate ways to download?
I faced same issue with firefox when I was running selenium project with it. I did the following things that helped me. First uninstall the firefox by using command,
sudo apt-get remove --purge firefox
Some of the old files could also be there, you need to remove them manually.
Then you can install the previous version from the link provided below which shows list of all previous versions of the firefox, version 54, works fine for selenium.
https://support.mozilla.org/en-US/kb/install-older-version-of-firefox
When you install it, Mozilla build for Firefox would be opened as a browser and you can perform selenium tests there.
Hope this helps!
When you attempt to apply any hot fixes via the ColdFusion 10 Administrator you continuously get:
Error occurred while installing the update:
Failed Signature verification
You may have even validated the files and manually and placed them in the hf-updates directory at which point the CF10 admin page still shows the "Install" option, but again you receive the same error.
This error means you've forgotten to apply the ColdFusion 10 Mandatory Update which updates the certificate used to validate install packages.
From Adobe's website:
All ColdFusion updates are now signed with the new code signing
certificate because of a code signing certificate revocation. This
mandatory Update ensures that your current installation of ColdFusion
10 is updated with the new code signing certificate. This update is
also required for proper functioning of the auto update functionality
in ColdFusion 10. Adobe strongly recommends that you apply this
update.
Once the update has been installed (you can find the JAR install instructions here) the service will be restarted and you will be able to apply subsequent updates via the ColdFusion administrator.
Edit:
Run the command prompt as Administrator:
Navigate to your jar file, and run the following command to run jar file:
D:\>java -jar cf10_mdt_updt.jar
#UncleSol,
I also encountered the issue after having installed the mandatory update (cf10_mdt_updt.jar). After successfully applying the mandatory update, CF wanted to apply update 12 as the first update, which is where I encountered this issue, so I downloaded and manually installed Update 11 from this page:
https://helpx.adobe.com/coldfusion/kb/coldfusion-10-updates.html (installed in exactly the same manner as NotJustClarkKent's instructions)
After manually installing update 11, I was able to use the CF Updater to install the rest of my updates.
Hope that helps.