Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows] Cannot open browser app #837

Closed
UdoW opened this issue Nov 15, 2017 · 29 comments
Closed

[Windows] Cannot open browser app #837

UdoW opened this issue Nov 15, 2017 · 29 comments
Assignees
Labels
OS/Windows issues related to the Windows OS

Comments

@UdoW
Copy link

UdoW commented Nov 15, 2017

When I start the browser app with http://localhost:3000 I get following error in the browser console:
(the browser window is black and shows my a waiting cursor - rotating points)

Uncaught TypeError: setImmediate is not a function
at triggerMessageQueue (main.js:231)
at StreamMessageReader.callback (main.js:280)
at StreamMessageReader.onData (messageReader.js:211)
at ReadableStream. (messageReader.js:176)
at ReadableStream.EventEmitter.emit (events.js:81)
at ReadableStream.Readable.read (_stream_readable.js:462)
at flow (stream_readable.js:806)
at emitReadable
(_stream_readable.js:498)
at afterTickOne (index.js:23)
at Item.run (browser.js:153)

I get this in Chrome and Firefox.

My versions:
node: 8.9.0
yarn: 1.3.2
npm: 5.5.1

Git commit was: commit 2c8b92f

@kittaakos
Copy link
Contributor

@UdoW, I would say you have a stale process running. You are on Windows, right? Could you please check the open ports and verify my assumption with netstat -o -a? If that is the case, please terminate the stale process, and check the browser again.

Meanwhile, I try to collect the corresponding issues and thread from Gitter.

@kittaakos
Copy link
Contributor

I did not find the Gitter entry. Just this, but that is related to the WDIO.

@UdoW
Copy link
Author

UdoW commented Nov 15, 2017

I do not have any node process running and it still does not work.

@kittaakos
Copy link
Contributor

Thanks for the feedback, I try to reproduce it right now.

Git commit was: commit 2c8b92f

As I see, you are have tried it on the HEAD of the master branch. I get back to you in 5 minutes or so...

@kittaakos
Copy link
Contributor

I can confirm, it works. See attached full console log.

@kittaakos
Copy link
Contributor

kittaakos commented Nov 15, 2017

I have tried it with Chrome, but I'll give it a try with another browser.

@kittaakos
Copy link
Contributor

Meanwhile, you could perhaps attach your full console log to this issue too, so that we can investigate the problem.

@kittaakos
Copy link
Contributor

It works from Edge too.

@UdoW
Copy link
Author

UdoW commented Nov 15, 2017

Ok, I will try it again with a console log.

@hexa00
Copy link

hexa00 commented Nov 16, 2017

One thing to try too is with a browser window in private mode ?

It's possible the workspace restore is having issues. With a private mode tab if the issue is not there it is most likely the restore.

@UdoW
Copy link
Author

UdoW commented Nov 17, 2017

I tried with private mode but still the same error.

@UdoW
Copy link
Author

UdoW commented Nov 17, 2017

I tried again with commit 2ceb174 and logged all output.
yarn_log.txt
browser_yarn_log.txt

And still the same error in the browser log:
Failed to load resource: the server responded with a status of 404 (Not Found)
9main.js:231 Uncaught TypeError: setImmediate is not a function
at triggerMessageQueue (main.js:231)
at StreamMessageReader.callback (main.js:280)
at StreamMessageReader.onData (messageReader.js:211)
at ReadableStream. (messageReader.js:176)
at ReadableStream.EventEmitter.emit (events.js:81)
at ReadableStream.Readable.read (_stream_readable.js:462)
at flow (stream_readable.js:806)
at emitReadable
(_stream_readable.js:498)
at afterTickOne (index.js:23)
at Item.run (browser.js:153)

@hexa00
Copy link

hexa00 commented Nov 17, 2017

I see this:

@theia/example-browser: WARNING in Circular dependency detected:
@theia/example-browser: ..\..\node_modules\readable-stream\lib\_stream_duplex.js -> ..\..\node_modules\readable-stream\lib\_stream_readable.js -> ..\..\node_modules\readable-stream\lib\_stream_duplex.js
@theia/example-browser: WARNING in Circular dependency detected:
@theia/example-browser: ..\..\node_modules\readable-stream\lib\_stream_writable.js -> ..\..\node_modules\readable-stream\lib\_stream_duplex.js -> ..\..\node_modules\readable-stream\lib\_stream_writable.js
@theia/example-browser: WARNING in Circular dependency detected:
@theia/example-browser: ..\..\node_modules\inversify\lib\syntax\binding_on_syntax.js -> ..\..\node_modules\inversify\lib\syntax\binding_when_syntax.js -> ..\..\node_modules\inversify\lib\syntax\binding_on_syntax.js
@theia/example-browser: WARNING in Circular dependency detected:
@theia/example-browser: ..\..\node_modules\inversify\lib\syntax\binding_when_syntax.js -> ..\..\node_modules\inversify\lib\syntax\binding_on_syntax.js -> ..\..\node_modules\inversify\lib\syntax\binding_when_syntax.js
@theia/example-browser: WARNING in Circular dependency detected:
@theia/example-browser: ..\..\node_modules\readable-stream\lib\_stream_readable.js -> ..\..\node_modules\readable-stream\lib\_stream_duplex.js -> ..\..\node_modules\readable-stream\lib\_stream_readable.js
lerna success run Ran npm script 'prepare' in packages:

Is that familiar to anyone ?

@kittaakos
Copy link
Contributor

@hexa00
Copy link

hexa00 commented Nov 17, 2017

OK hard to tell what is going on :(

Actually since this is a 404 @UdoW could you check the Network tab in the inspector and check what resource it's trying to fetch ?

@UdoW
Copy link
Author

UdoW commented Nov 17, 2017

network

@UdoW
Copy link
Author

UdoW commented Nov 17, 2017

This is what I see in the browser:
browser

@hexa00
Copy link

hexa00 commented Nov 17, 2017

:( I don't see the 404 in the network window... is there one ?

@svenefftinge
Copy link
Contributor

@UdoW
Copy link
Author

UdoW commented Nov 20, 2017

Hi Sven, probably this is the bug. I also have a file system here on Windows which ignores the case of fileames.
In the referenced bug report for webpack they mentioned that you should not use "." in the modules list. Does Theia use "." in the modules list?

@svenefftinge
Copy link
Contributor

Do you have a reference? I am not sure what you are referring to.

@UdoW
Copy link
Author

UdoW commented Nov 21, 2017

This is the reference: webpack/webpack#4876

@akosyakov
Copy link
Member

interesting that the difference is not in node_modules, but in the project location, i.e. !D:\Projekte vs !D:\projekte

@akosyakov
Copy link
Member

@UdoW could you do cd with the lower case path before running webpack?

@akosyakov
Copy link
Member

akosyakov commented Nov 21, 2017

this issue seems to be similar: PatrickJS/PatrickJS-starter#926
if the difference would be in js files then it would mean that we use upper-case imports somewhere, otherwise, it does not look like we can do something about it.

@kittaakos kittaakos self-assigned this Nov 21, 2017
@kittaakos
Copy link
Contributor

I give it another try. I hope I can reproduce the defect. That is my plan:

  • I use a fresh clone.
  • I use cmd.exe. (If it does not fail, I'll try it with PS too. It works from GitBash.)
  • I intentionally mess up the case sensitivity in the path.

@kittaakos kittaakos changed the title Cannot open browser app [Windows] Cannot open browser app Nov 27, 2017
@kittaakos kittaakos added the OS/Windows issues related to the Windows OS label Nov 27, 2017
@kittaakos
Copy link
Contributor

Worked fine both from cmd.exe and PS. @UdoW, are you using a mapped network drive? Please do the following: execute the single-line command and share the console output with us again. Instead of piping the output into files, just copy and paste the entire output into a text file and attach it to this issue. Thank you!

mkdir tmp && cd tmp && git clone https://github.com/theia-ide/theia.git && cd theia && node --version && npm --version && yarn --version && python --version && yarn && cd examples/browser && yarn run start

Furthermore, could you please try to use only lower-case characters in your path? It is indeed not a possible fix, I am just still trying to narrow the cause of the issue.

@kittaakos
Copy link
Contributor

@UdoW, are there any updates on this thread?

@kittaakos
Copy link
Contributor

I am closing this. Please reopen, or create a follow up if the problem still present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OS/Windows issues related to the Windows OS
Projects
None yet
Development

No branches or pull requests

5 participants