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
Uncaught Error: ENOENT, no such file or directory 'C:\tmp\atom.apib' #17
Comments
workaround: just create an empty c:\tmp folder |
This should be fixable by doing a check to see if the directory exists, and if not then creating it. Pull requests welcome, otherwise I'll get the fix in when I can. |
I'm seeing this on Mac OSX as well. |
* elarivie/master: Set maxbuffer length to Infinity to avoid stdout maxBuffer exceeded fix danielgtaylor#44 Removed hardcoded path to tmp, now uses os library to get it. Add support for embeded image with data uri Added missing description of response to the template Randomize temp file name to avoid race condition fix danielgtaylor#17 fix danielgtaylor#24 fix danielgtaylor#42
I'm seeing this on Mac OSX too, It seems to work the first time but then it stop working. I had a look and it seems like I would imagine this is a race condition so #55 should probably fix this |
I can confirm this on Mac OSX too. It switches between preview and error every time I change the file and it's really annoying. |
I confirm the same error on Ubuntu 16.04
after adding example-include.md to folder it leads to that which probably it's a Aglio-NodeJS error and has nothing to do with this plugin.
Anyway adding example-include.md to the path folder of building fixed the problem. But this shouldn't probably happen. |
[Enter steps to reproduce below:]
System:
Win 7 pro 64bit
nodejs 0.10.36 x86
npm 2.6.0
Visual Studio 2010 Express
Windows SDK for Windows 7 (7.1)
Visual C++ Redistributable (x86) – 10.0.30139
atom 0.182.0 20.2.2015 18:52:34
Atom Version: 0.182.0
Thrown From: api-blueprint-preview package, v0.3.0
Stack Trace
Uncaught Error: ENOENT, no such file or directory 'C:\tmp\atom.apib'
Commands
Config
Installed Packages
The text was updated successfully, but these errors were encountered: