iliakan / iliakan/node-dev

Error: ENOENT, No such file or directory './4913'

Open
#3 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
38
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Issue on Ubuntu 11.04 Natty Narwhal, Node.JS version v.0.4.7, using npm and nvm for package and version management respectively.

Ran the script below with 'node-dev testing.js':

var http = require('http');

http.createServer(function(req, res) {
res.write('testing this now...');
res.end();
}).listen(6404);

It served the request fine. Upon changing the file, however, I got this error:

fs.js:400
return binding.stat(path);
^
Error: ENOENT, No such file or directory './4913'
at Object.statSync (fs.js:400:18)
at Inotify.callback [as 1](/home/frank/.nvm/v0.4.7/lib/node_modules/dev/manager.js:229:13)

Let me know if you need more information

Thanks!
Frank

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report with node-dev testing.js and the http server shown in the issue, then inspect the file-watching path at /home/frank/.nvm/v0.4.7/lib/node_modules/dev/manager.js:229 and the fs.statSync failure. Done means changing testing.js no longer produces the ENOENT error and node-dev continues handling the file change.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.