inspect-process
inspect-process copied to clipboard
jaridmargolin
data:,
If I run this I get a Chrome window with the url data:,
and nothing much else ...
What command exactly?
On Wed, Feb 15, 2017, 17:43 weepy [email protected] wrote:
If I run this I get a Chrome window with the url data:,
and nothing much else ...
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jaridmargolin/inspect-process/issues/36, or mute the thread https://github.com/notifications/unsubscribe-auth/AAmyx-PeNUzbVSMioIyTaHHi6jl56AOeks5rcx06gaJpZM4MB36W .
I'm getting the same results as the OP. I even tried previous versions of inspect-process and it still breaks with the same results. A Chrome window opens with the url data:,
Chrome: 57.0.2987.37 beta (64-bit) node: v7.5.0
May be an issue with node v7.5.0. Looking into it now. Thank you for reporting.
@pho3nixf1re / @weepy - could you run with logging turned on and paste the output (inspect --log-level=silly?
╭─mturney@mturney-laptop ~/Workspace/waybetter/wb-admin ‹ruby-2.3.3› ‹7.5.0› ‹master*›
╰─➤ inspect --log-level=silly node_modules/ava/profile.js app/components/Header/index.test.js 1 ↵
sill devtools: create
sill process: listening
sill devtools: open
sill devtools: resize
verb debugger: Debugger listening on port 9229.
Warning: This is an experimental feature and could change at any time.
To start debugging, open the following URL in Chrome:
chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/f0675153-87ee-49ec-8674-938ffe7bf288
verb WebDriverError: unknown error: cannot get automation extension
from unknown error: page could not be found: chrome-extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html
(Session info: chrome=57.0.2987.54)
(Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cfd9),platform=Mac OS X 10.12.3 x86_64)
It seems putting the URL manually in Chrome works fine. It's just the auto open that breaks. Could be an extension issue?
we may be hitting an issue with chromedriver version incompatibilities with chrome version. Could you uninstall and then reinstall inspect-process?
I am seeing this error referenced in selenium issues as well: https://github.com/SeleniumHQ/selenium/issues/3508
Ok... so the common thread here is that you are both utilizing beta chrome builds. I am currently running with no issues:
Chrome: Version 56.0.2924.87 (64-bit)
Node: v7.5.0
It is possible the chrome beta is incompatible with the current released version of chromedriver. Uncertain how much I will be able to control here :/
At the very least there should be clear messaging if we suspect there may be a compatibility issue. I'll spend some time thinking about possible solutions.
I could try forcing to use a specific chrome version? There is some relevant code over at selenium-assistant:
detecting executable: https://github.com/GoogleChrome/selenium-assistant/blob/master/src/local-browsers/chrome.js#L116 downloading executable: https://github.com/GoogleChrome/selenium-assistant/blob/master/src/download-manager.js#L137
I most likely would not want to be doing any of this without user approval. Just jotting down notes :)
Not sure I like that. But clear documentation on the limitation would be nice. There are many reasons why you might want to be using the beta or canary versions of chrome in development. There just needs to be a clear error message that the launch failed and to verify your version of chrome.
works on non-beta chrome FYI
On Thu, Feb 16, 2017 at 4:30 PM Matthew Turney [email protected] wrote:
Not sure I like that. But clear documentation on the limitation would be nice. There are many reasons why you might want to be using the beta or canary versions of chrome in development. There just needs to be a clear error message that the launch failed and to verify your version of chrome.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jaridmargolin/inspect-process/issues/36#issuecomment-280381903, or mute the thread https://github.com/notifications/unsubscribe-auth/AAADNCRU8qG62cS60ywMoLC728QfCNRfks5rdHmQgaJpZM4MB36W .
@pho3nixf1re - I would only be forcing chrome usage for the inspect window. It would not effect other development.
Additionally... this functionality could be put behind a flag, or could display a prompt asking for permission. Especially if you have multiple versions of chrome installed on your machine.
The largest issue I am seeing, is there is no way to determine when these mismatch versions of chrome/chromedriver occur. At best, a service could be created than continually tests the latest version of chromedriver, again the latest releases of chrome (either on a cron or on some webhook if exposed by chrome). That is just a large undertaking for this project to take on.
@gauntface - I wanted to tag you incase you had any input. I know we briefly discussed this before, but a library/service to help in managing browser/driver installations would be incredibly useful across an array of projects.
@jaridmargolin I forgot that this is just for the inspector. I'm on board with that idea, especially a selection option for multiple Chrome versions. I think it's important not to let the supported Chrome version lag behind too much. Otherwise this is a good solution. 👍
Personally, I would add flags to select stable, beta and unstable if that is an option. Forces a developer decision and also allows testing in different versions if a bug is hit.
Agree that a service like that would be immensely helpful. It could be done with travis-ci and a cron job to run the tests every day to check for updates and issues.
@gauntface do you think the devs on angular/protractor would be interested in contributing/working on a solution for testing driver compatibility? Might align well with https://github.com/angular/webdriver-manager ?
I'd raise an issue on that project. It seems well aligned for what you are looking for.
Any development on this issue? Will I need to manually install an older version of Chrome? Is there an easy way to tell inspect-process which Chrome executable to use?
I'm currently using Chrome 62.0.3202.94.
