On my Windows machine, I have Aptana Studio 3 installed. I have a new installation of Firefox 37.0.2 installed along with the add-ons Aptana Debugger 1.7.2 and Firebug 1.8.3.
From Aptana, I choose to debug an HTML page. Firefox opens with a URL like http://www.aptana.com/?debugger=true&port=63923 and shows the Aptana.com home page. After about 30 seconds I get an error in Aptana:
Socket connection error. Please try shutting down and restarting your web browser, and then run 'debug' again.
Accept timed out
Restarting the browser does no good.
Looking at the output of the Aptana debugger add-on in Firefox, I see this:
Logger initialized (Tue Apr 21 2015 10:56:45 GMT-0400 (Eastern Standard Time))
Platform: Firefox v37.0.2 (WINNT)
Debugger: v1.7.2
And I see this error:
[Tue Apr 21 2015 10:56:45 GMT-0400 (Eastern Standard Time)] TypeError: AptanaDebugger.initDebugger is not a function at chrome://aptanadebugger/content/aptanaLaunch.js:120
I am very suspicious of the protocol "chrome" being used with Firefox. I cannot determine where that protocol is coming from though. I have tried this with Firefox being and not being my default browser. Anyone know the fix?
Got it at last! The problem is in Firefox/Firebug/AptanaDebugger compatibilities. With some of debugging of these Firefox extensions I've got the information. Strange enough that I couldn't find it with the help of aptanadebugger.err log. So, at first, AptanaDebugger 1.7.2 which comes even with the latest for now 3.6.1 version of Aptana Studio from Appcelerator requires Firefox version 32 or below (as in 33 and higher support for JavaScript Debugger Service was removed, but AptanaDebugger still reies on JDS). And then comes Firebug/AptanaDebugger compatibility. In short, you have to install Firefox version 18 and Firebug 1.9.2 seems OK. Maybe, if any problems with 1.9.2 will go, 1.8.4 version of Firebug must be OK with certainty. Then I switched off Firefox automatic updates through about:config in URL/search string, and set up app.update.auto and app.update.enabled to false, and modified app.update.url to do no update accidentaly through Help-About dialog again )
Related
2022-03-08 11:21:22 WARN Selenium [DEPRECATION] [:driver_path] Selenium::WebDriver::Chrome#driver_path= is deprecated. Use Selenium::WebDriver::Chrome::Service#driver_path= instead.
An error occurred while loading spec_helper.
Failure/Error: browser = Capybara.current_session.driver.browser
Selenium::WebDriver::Error::SessionNotCreatedError:
session not created: This version of ChromeDriver only supports Chrome version 99
Current browser version is 98.0.4758.102 with binary path /usr/bin/google-chrome
The error message explains exactly what your issue is - You're using chromedriver v99.x with Chrome v98.x -- that won't work. Rather than trying to manually manage the version of chromedriver being used, just use the webdrivers gem to automatically manage it for you.
I'm getting the following error message when I try different operations such as installing an application to a Firefox OS simulator:
Operation timed out: installing and running app
I've tried versions 1.3, 1.4, 2.0 of the simulator - all have the same error.
The application does get deployed to the simulator and runs. However, console.log() output does not get displayed in the WebIDE Console.
For the location of the error message, see the screenshot below
My Firefox Version is - 42.0a1 (2015-07-16)
This is running on Ubuntu 14.04 x64.
When I click on the Troubleshooting link, I can't find any tips for troubleshooting a simulator.
Any ideas?
The steps I followed were:
Open WebIDE. Terminal output:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Start Firefox OS 2.0 simulator, simulator displays. Terminal output:
console.log: Connection status changed: connecting
console.log: Connection status changed: connected
Project >> Open Packaged App, and select my application. No Terminal output.
Project >> Install and Run. Application displays on simulator. Terminal output:
console.log: Installing app from /home/snowch/tmp/Scratch/myapp/hw_chs
console.log: Starting bulk upload
console.log: File size: 14253
console.log: Bulk upload done
After about 10 seconds the error message is shown as per the screenshot.
Update
The jconsole error messages:
Simulating large screen devices (Operation timed out: installing and running app)
Simulating small screen devices, after clicking on the spanner (Operation timed out: opening toolbox)
It looks like you've run into several bugs with older simulator versions.
For the issue with app install when the screen is set to Via Vixen, I filed bug 1186929. For myself, it only reproduced on 2.0, but please comment in that bug if you have more specifics.
For the "opening toolbox" issue, I believe that is a compatibility problem that needs to be resolved with older simulators, which is bug 1161131.
I tried asking several times in the comments above if you ever actually see the toolbox appear, or if you just get error messages. It would still help to know the answer here.
As a workaround, you should be able to use Simulator 2.2 or later to avoid these issues until they are resolved.
On Linux, the RSelenium/Selenium seems to be behaving erratically. I start the server manually and it seems to start up fine. Sometimes I am able to connect to it from my R session and other times I get an error. I cannot yet pinpoint the cause: the same script seems to work sometimes and not other times. Any ideas?
Here is the output from starting the server:
12:41:25.811 INFO - Launching a standalone server
12:41:26.102 INFO - Java: Sun Microsystems Inc. 11.0-b16
12:41:26.102 INFO - OS: Linux 2.6.32-431.17.1.el6.x86_64 amd64
12:41:26.157 INFO - v2.44.0, with Core v2.44.0. Built from revision 76d78cf
12:41:26.492 INFO - Default driver org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: registration capabilities Capabilities [{platform=WINDOWS, ensureCleanSession=true, browserName=internet explorer, version=}] does not match with current platform: LINUX
12:41:26.589 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub
12:41:26.589 INFO - Version Jetty/5.1.x
12:41:26.590 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
12:41:26.590 INFO - Started HttpContext[/selenium-server,/selenium-server]
12:41:26.590 INFO - Started HttpContext[/,/]
12:41:36.597 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler#2993a66f
12:41:36.598 INFO - Started HttpContext[/wd,/wd]
12:41:36.601 INFO - Started SocketListener on 0.0.0.0:4444
12:41:36.601 INFO - Started org.openqa.jetty.jetty.Server#6f507fb2
The error I receive in my R session:
Couldnt connect to host on http://localhost:4444/wd/hub.
Please ensure a Selenium server is running.Error in queryRD(paste0(serverURL, "/session"), "POST", qdata = toJSON(serverOpts))
Other times, running the exact same script everything proceeds successfully. It could be a difference of what computer node actually executes the script but I cannot tell what the problem is when it will not connect.
library(RCurl)
library(RJSONIO)
library(XML)
# running selenium
system("java -jar selenium-server-standalone-2.44.0.jar")
I faced same issue and try to run above code. Finally know that there only support 1.7 but not 1.8 as time being. You might try to download jre7 and jdk7.
I faced the same error in Mac, but I noticed that due to security settings the system does not let me to run the file with that piece of code. I downloaded the selenium standalone file and using control key I single-clicked the file and then from the menu I chose the open. Then the problem get solved.
I have an application that runs fine on my Win 8.1 development machine but when I go to install it on my Win 7 64 bit test box I run into a TypeInitializationException with Caliburn.Micro.Platform. What could be causing this? the error log that leads me to believe it is Caliburn.Micro is below.
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7601 Service Pack 1</Build>
<Product>(0x30): Windows 7 Professional</Product>
<Edition>Professional</Edition>
<BuildString>7601.18409.amd64fre.win7sp1_gdr.140303-2144</BuildString>
<Revision>1130</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
<ParentProcessInformation>
<ParentProcessId>2356</ParentProcessId>
<ParentProcessPath>C:\Windows\explorer.exe</ParentProcessPath>
<ParentProcessCmdLine>C:\Windows\Explorer.EXE</ParentProcessCmdLine>
</ParentProcessInformation>
<ProblemSignatures>
<EventType>CLR20r3</EventType>
<Parameter0>MyApp.exe</Parameter0>
<Parameter1>0.6.25.0</Parameter1>
<Parameter2>546dfbc7</Parameter2>
<Parameter3>Caliburn.Micro.Platform</Parameter3>
<Parameter4>2.0.1.0</Parameter4>
<Parameter5>53f41236</Parameter5>
<Parameter6>92</Parameter6>
<Parameter7>0</Parameter7>
<Parameter8>System.TypeInitialization</Parameter8>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>6.1.7601.2.1.0.256.48</Parameter1>
<Parameter2>1033</Parameter2>
<Parameter22>2b5c</Parameter22>
<Parameter23>2b5cea20275728230acc663702d2e8da</Parameter23>
<Parameter24>5bd8</Parameter24>
<Parameter25>5bd8dc1fa50918888316b6b5f643c5e9</Parameter25>
</DynamicSignatures>
<SystemInformation>
<MID>BA765621-6E94-49A3-BF5C-4CA9CB339779</MID>
<SystemManufacturer>Microsoft Corporation</SystemManufacturer>
<SystemProductName>Virtual Machine</SystemProductName>
<BIOSVersion>090006</BIOSVersion>
</SystemInformation>
</WERReportMetadata>
And you are building against .NET 4.5, and you have the assemblies all correctly referenced. The one that tends to pop out is the Interactivity assembly, it gets buried hard to detected. Since it is a .NET usually version changes between Windows version. Can only suggest it is missing or a version number needed mismatch. Make sure the one from the lib folder in your packages from nuget is present on the install of your WIN7 box. If that is how you got the CM framework. otherwise pull the latest github release
UPDATED: Took everyone's advice and decided plone.app.registry and 4.1.1 were not the issue, question is, what is? Where can I find the error logs in binary installer?
symptom: can't add content types (under Add New... folders, pages, news items, etc. -- hangs on save, more specifically my portal_factory is unable to validate and move the content to ZODB).
had same issue using both unified (4.1) and binary (4.1) installers
environment: mac book 10.6 Snow Leopard 32-bit
When I run buildout I see no errors:
2012-05-08 18:13:34 INFO ZServer HTTP server started at Tue May 8 18:13:34 2012
Hostname: 0.0.0.0
Port: 8080
2012-05-08 18:14:01 WARNING ZODB.FileStorage Ignoring index for /Applications/Plone/zinstance/var/filestorage/Data.fs
2012-05-08 18:14:27 INFO Zope Ready to handle requests
When I create a new site in Plone, Terminal says: http://pastie.org/3882025
Line 23: 2012-05-08 18:16:01 INFO GenericSetup.plone.app.registry Cannot find registry
That's not an error - that's what happens whenever you start up an instance with a new Data.fs file. If there's no Data.fs.index, or the .index file is inconsistent with the Data.fs, the existing one is ignored and the index is rebuilt. It means absolutely nothing on a new install.
There must be more information than this in the log.
Fixed this issue by following this post here: http://plone.293351.n2.nabble.com/Add-new-Plone-site-creates-site-with-JS-problems-4-1-4-tt7547774.html#a7555663
Basically, had to go to javascript registry, save, empty cache, restart browser, testing in Chrome only.