I have updated the calabash gem to the latest version(0.20.0) and tried to run the tests on iOS 10 devices. The issue I am facing is that the first test executes as expected but the consecutive tests are failing with the following error message:
Timed out after 60.04 seconds executing
with a timeout of 60
(RunLoop::Shell::TimeoutError)
I get the following warning message on the console, however I am not sure if these are related with the issue.
WARN:
Calabash::Cucumber::Launcher #calabash_no_launch? and support for the NO_LAUNCH
environment variable has been removed from Calabash. This always returns
true. Please remove this method call from your hooks.
WARN: The server version is not compatible with gem version.
Please update your server.
https://github.com/calabash/calabash-ios/wiki/Updating-your-Calabash-iOS-version
gem version: '0.20.0'
min server version: '0.20.0'
server version: '0.19.1'
Could you please share your thoughts on this issue.
Looks like you need to to a 'bundle exec calabash-ios download' again so you can download the latest version of the Calabash server that matches what you have installed which is 0.20.0 and then rebuild your app in Xcode with that framework added. Then use that version for testing. Or, if your build server is doing the work, you just need to update the gem on your build server and rebuild.
Related
I am using the LTS version of NodeJS. The problem started with version node-v16.18.0-x64 and did continue with node-v18.12.0-x64.
What I am doing:
Developing Playwright test. I ran the test and NodeJS was working. After one minute, I rerun the test and NodeJS is no longer recognized in my OS.
The issue appears when I am using Cypress, so I think the issue is not related to the technology that I am using.
I checked the environment variable: It is there.
The workaround I am doing is to uninstall the NodeJS from the control panel and install it again. There is an option to repair the NodeJS installation. But when I try to use it, I receive an error message that the NodeJS is not installed on this OS.
After upgrading to Angular version 11, unit tests now fail on Travis CI. Locally they do succeed (even after clean install with the same node, nvm and npm versions).
The error for all unit tests is the same -
Failed: fn.bind is not a function
TypeError: fn.bind is not a function
at newTrustedFunctionForJIT (node_modules/#angular/compiler/fesm2015/compiler.js:6845:1)
at JitEvaluator.evaluateCode (node_modules/#angular/compiler/fesm2015/compiler.js:6909:1)
at JitEvaluator.evaluateStatements (node_modules/#angular/compiler/fesm2015/compiler.js:6883:1)
Based on the error message, I would assume that the issue might be related to ngcc? Anyone had similar issue?
Today I had the same problem. It involved testing with ChromeHeadless.
I had old version of Chrome Headless 83.0.4103.97 installed in docker image. After updating it to latest version 88.0.4324.96 it started to work.
Additional here is the corresponding angular github issue.
Using Chrome >= 87 should fix the issue.
I decided to upgrade my version of nodejs from 8.11.1 to 10.15.3. I am running on Windows 10 so I downloaded v10.15.3-x64.msi file. I created a brand new Angular application from "ng new" command and I got the "HTTP ERROR 400" page with no error in the console.
I have cleared the cache, reboot the system and nothing helps. When I will go back to node JS version 8.11.1 everything starts to work again. The newest version of nodejs v11.11.0-x86.msi also doesn't work for me.
How this can happen and how can I get any information what is going on?
EDIT: this is not a duplication of any existing topics about upgrading NodeJS, because the new version is seen by the system and all components - see the console result in the screenshot I provided. After upgrading the NodeJs all my solutions based on that technology stoped working showing HTTP Error 400 page. After degrading to v8 everything starts working again.
The problem came back when I had to install newer version of node (12.14.1), so this time it worked. Additionally I deleted folders that prompted from runnig where npm command after deleting an old version.
I'm trying to do IBM Bluemix essential course.
As per the course instructions, I installed Eclipse (I initially got latest Eclipse version Neon instead of Mars but tried both Mars and Neon as of now for installing NodeEclipse .17, 1.0.1 or 1.0.2 or Enide.p2f file using both File import and Eclipse marketplace for installing Enide.p2f Node eclipse plugin in Eclipse).
One of the instruction (after installing IBM Bluemix plugin for eclipse) says, I need to install "Enide.p2f Eclipse NodeJS plugin" https://marketplace.eclipse.org/content/enidep2f-eclipse-nodejs-ide
I tried Eclipse Marketplace to install this. Searched "node eclipse" and selected the top listing entry for "Nodeeclipse 1.0.2 Nodeeclipse Core & Node.js (nodeeclipse-1)" or even "Enide.p2f for Nodeeclipse 1.0.1" version and clicked installed.
A couple of times, if failed during the resolution process to list the plugin components and Eclipse error log showed that the update site / repository server was not available.
Another method was to install the .p2f file directly File > Import > Install > Install from a file and selected the downloaded .p2f file which I got from here: https://raw.github.com/Nodeclipse/eclipse-node-ide/master/ENodeIDE.p2f
or
http://marketplace.eclipse.org/content/enide-eclipse-nodejs-ide/click
Using the import > install via file method, I'm getting "Unhandled event loop exception" error message as per Eclipse Error logs and it didn't install anything.
Using the market place method, I'm getting the following error mesg (per the screen shot):
For Nodeeclipse 1.0.1
https://i.imgsafe.org/1b1bf4f0fb.jpg
https://i.imgsafe.org/1b1be1c00a.jpg
https://i.imgsafe.org/1b1bc75cfc.jpg
For Nodeeclipse 1.0.2.
https://i.imgsafe.org/1afbf9bf56.jpg
https://i.imgsafe.org/1afa90e4f1.jpg
https://i.imgsafe.org/1af372340c.jpg
Error message:
HTTP Server Unknown HTTP Response Code (499):http://nodeeclipse.org/updates/compositeContext.xml
HttpComponents connection error response code 499.
OR
it shows the Enide.p2f .17, 1.0.1 or 1.0.2 (Whichever you select from the list) to install the plugin:
The following solutions are not available: Nodeclipse 1.0.2
(id=markdown.editor.feature.feature.group,
org.nodeclipse.pluginslist.feature.feature.group,
gitaddon.feature.feature.group,
de.bastiankrol.startexplorer.feature.feature.group,
com.eclipsesource.jshint.feature.feature.group,
org.nodeclipse.feature.group,
org.nodeclipse.enide.editors.jade.feature.feature.group,
org.chromium.sdk.feature.group, net.mihai-nita.ansicon.feature.group,
org.chromium.debug.feature.group,
pm.eclipse.editbox.feature.feature.group,
site=http://www.nodeclipse.org/updates/)
With Eclipse Mars, I'm getting the same behavior. More info on this can be found here as well: https://www.ibm.com/developerworks/community/forums/html/topic?id=76a96fa4-1086-41a7-94a6-4326f79dfacb&ps=#repliesPg=0
Did anybody else face this similar issue and what should i do to resolve it.
"https://marketplace.eclipse.org/content/enidep2f-eclipse-nodejs-ide"looks like an update site so I tried the Help->Install New Software... I then entered the address as a new update site but it failed as well...
I'm trying to run the 'hello-foxx' example on my Mac OSX 10.10.5 Yosemite but fail.
ArangoDB is installed and running (from the App store)
Foxx-Manager runs (typing foxx-manager returns the response as described in the manual)
The anrangodb web interface runs (but w/o the 'application' menu
When I execute:foxx-manager install hello-foxx /example
from my home directory I receive the following error:
'Cannot call method 'byExample' of null'
I also tried to run it directly from git:
foxx-manager install https://github.com/arangodb-foxx/demo-hello-foxx.git /example
returns the same error.
tried a local installation and received the same error.
Any ideas?
I can't find the log files. Where should I look?
Many thanks.
The app store version is three versions behind the current release. I recommend installing Arrangodb with Homebrew instead. I did this yesterday and had no problems with Foxx Demo on Yosemite.