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

[third-party] `node-inspector` debug console has a bug. #8469

Closed
codeHatcher opened this Issue Mar 8, 2017 · 8 comments

Comments

Projects
None yet
4 participants
@codeHatcher

codeHatcher commented Mar 8, 2017

Similar to #7991 and #7977

When I run with meteor debug and then go to http://localhost:8080/?port=5959 upon opening the page I first see the following error in the console

Network.loadResourceForFrontend failed. Error: ENOENT: no such file or directory, open '/Users/avi/Code/transfs/.meteor/local/build/programs/server/profile.js.map

when I try and type a variable in the console, I do not get any response (see gif)

b3ebf061e4f3623a926c3a644e0cc30e

Chrome: 56.0.2924.87 (64-bit)
OSX: 10.11.6 (15G1217)
Meteor: 1.4.2.7 and 1.4.2 and 1.4.2.3

@brucejo75

This comment has been minimized.

Contributor

brucejo75 commented Mar 8, 2017

This is a dup of #7991. This is not a meteor bug, you can work around by patching node-inspector bug. All described in #7991.

@codeHatcher

This comment has been minimized.

codeHatcher commented Mar 8, 2017

@brucejo75 @abernix If this is not a bug then can we update the meteor debug part of the Meteor documentation to include those instructions for the patch? I have a few minutes of free time where I can update the Meteor documentation if someone will accept the PR

@codeHatcher

This comment has been minimized.

codeHatcher commented Mar 8, 2017

This is the list of things I have tried so the next poor soul that comes across this doesn't have to read all the existing issues

@abernix abernix changed the title from [1.4.2 and 1.4.2.7] with `meteor debug`, node-inspector debug console is unusable to [third-party] `node-inspector` debug console has a bug. Mar 9, 2017

@abernix

This comment has been minimized.

Member

abernix commented Mar 9, 2017

This is absolutely a bug with node-inspector and as @brucejo75 said, a duplicate of #7991 which explains the problem fairly clearly. The same happens in node-inspector outside Meteor and will (eventually?) be fixed if/when node-inspector lands node-inspector/node-inspector#955 and is reported in node-inspector/node-inspector#903.

There are easy work-arounds in the other issue which will fix all versions of Meteor you currently have installed for all projects on that computer (just not new versions of Meteor until you run it again).

I realize it's been frustrating to solve for you, but considering the relatively low impact actually feel this is a really reasonable I'm not currently willing to fork node-inspector for the very few users this has affected. Please rally behind the node-inspector issue/PR (linked above) and we'll happily bump to a stable release when it's fixed. You can also consider using Safari (which still supports .keyIdentifier) if you absolutely need this console functionality right now.

I've temporarily updated the docs (with meteor/docs@bf0b340) to help mitigate future confusion.

This can remain open for 60 days as a reminder to check and possibly remove the docs disclaimer/update node-inspector.

@codeHatcher

This comment has been minimized.

codeHatcher commented Mar 10, 2017

I appreciate you updating the docs, thank you! I posted on the node-inspector issues as well hoping that they create a fix. It looks like it's sitting in a PR whose build failed because of a timeout (possibly not a build issue)

@abernix abernix added this to the Release 1.4.4 milestone Apr 10, 2017

@abernix abernix modified the milestones: Release 1.5, Release 1.4.4 Apr 19, 2017

@abernix abernix closed this in e82ad97 Apr 25, 2017

abernix added a commit that referenced this issue Apr 25, 2017

abernix added a commit that referenced this issue Apr 25, 2017

@abernix

This comment has been minimized.

Member

abernix commented May 3, 2017

This should be fixed in Meteor 1.4.4.2!

@abernix abernix modified the milestones: Release 1.4.4.2, Release 1.5 May 3, 2017

@codeHatcher

This comment has been minimized.

codeHatcher commented May 5, 2017

@abernix YAY

@aramk

This comment has been minimized.

Contributor

aramk commented May 14, 2017

I'm still seeing this when using node-inspector@1.1.1 on Node 4.5.0 and Meteor 1.4.4.2 :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment