-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
random errors when using gitbook plugin on running "gitbook serve". #1309
Comments
Can you paste me the output of |
And also the output of |
here is the output C:\Projects\myproject_book>gitbook current C:\Projects\myproject_book>node -v |
Run |
Here it is: |
Ok thanks, I'll investigate and fix this. |
I get the same..
|
I have the same problem in Windows7.
I found that when the error message said:
the file |
I have the similar problems in Windows7
The first thing I haved notice is that gitbook create a read only |
I get the same on Windows 7 with GitBook 3.1.1 and Node 6.2.1. |
I ran into the same problem on Windows7 with GitBook 3.1.0 and Node 6.3.0. |
Hi, I have the same error, but in Linux
|
Same:
Everytime a different file. On Windows with 3.2.0. |
The same. |
The same issue on Windows 7. |
The same error on windows 10 when auto restarting server node v4.4.7, gitbook 3.2.0
|
|
I have the same problem with @liutopsec , I used docker to run gitbook serve command. There is no problem with version 2.6.7, and v3.0.x, v3.1.x, v3.2.x has this problem. |
I had same problem with nodejs 0.10.46 on linux. But everything was fine when I switch to windows and build with Nodejs 4.5.0 |
the same problem on windows 7 |
i had same error on windows 7.
|
Same error on Fedora. Seems (for me, at least) that it's caused by disk latency: My working directory is on a network drive, but when I build in |
I think the same @dstelljes, in my case my home is imported from a NFS server and (like you) working in local folder there are no problems. |
I had same error on windows 7.
Is it because of NVM cause? |
Updated. Sorry for this approach seems not working.
My env:
~~I hope this would help you.~~~~ |
Updated. Sorry for this approach seems not working.
|
Hi @hfxu, i tried your solution and saddly didn't work for me. |
After a few days of trying, I finally solved this problem!You only need to reduce the version number and node.js version to solve the problem of failure to start and refresh the interrupt. I did a lot of testing and found that the previous version of 3.0.0 did not have these problems, and node.js was V6. I recommend using: 2.6.7 ~ 2.6.4 You add a line in {
"gitbook" : "2.6.7"
} Node.js: V6
then install:
run:
I tested the version: Recommended:
I am not a javascript expert, I can only use this stupid method to solve the problem, I sincerely hope to help you! |
I get the same error. I have few times(less than 0.1%) works well after run as administrator and |
Scroll up 😉
…On Oct 12, 2017 12:44 AM, "Carson" ***@***.***> wrote:
I get the same error. I have few times(less than 0.1%) works well after
run as administrator and
npm cache clean
I've tried gitbook version 2.6.7. it seems work well and cannot be using
the graceful-fs module.
how to use gitbook 3.x.x for win10. thanks alot
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1309 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEwFd5tCNKuPtZ4GHj6TCZhkubkJsc61ks5srZlDgaJpZM4Ihms8>
.
|
In windows use administrator then run the command, you will resolve the issue. |
In my case installing This error was appearing when using |
Thank you @bluedusk!! Your tip works like a charm. Steps:
by
|
Same error but on MacOS and symbolic links. |
@obogobo thank you.... |
node 8 + , npm 4+ ,gitbook 3.2.3 ,they seems to be lastest,but this problem still appear to my env. |
can you see my problem ?sir |
any update on this, i don't want change the file manually... |
So it's been a while and the bug is still alive. I could see some effort to close this issues within pull requests but sadly without approval. Sincerely, I stopped digging to understand why. I came up with this simple Dockerfile as you might also want to use: FROM node:8.11-alpine
RUN npm install --global gitbook-cli && \
gitbook fetch 3.2.2 && \
gitbook install && \
npm cache clear --force && \
rm -rf /tmp/*
# Fixes https://github.com/GitbookIO/gitbook/issues/1309
RUN sed -i.bak 's/confirm: true/confirm: false/g' \
/root/.gitbook/versions/3.2.2/lib/output/website/copyPluginAssets.js Build the image: $ docker build . -t gitbook Write README.md example: $ echo "# Hello Gitbook" > README.md Build a book: $ docker run -v $(pwd):/gitbook -w /gitbook --rm -it gitbook gitbook build . output |
Seems the code was merged, when a new release will be published? |
The official repository is dead. |
Sure seems that way. The commercial website indicates that they're on Gitbook v2 as of February 2018, which means, despite the semantic versioning of this package, this is all under the Gitbook v1 umbrella. Guess it's time to move on to other tools. Back to LaTeX2html, I guess. ;-P |
Checked out the latest beta version solved this issue for me. Use the below command to list all available versions: Then I installed pre-release 4.0.0-alpha.6 See the GitHub repo for more details: |
I had fixed it by restarting my computer. @everybody |
@15766273878 It can occur randomly any time again. I doubt rebooting is a permanent solution for anything, ever. |
Sadly,I get the same error.
Error: ENOENT: no such file or directory, stat 'F:\cmp2.0\doc\blueking_book\gitbook\gitbook-plugin-toggle-chapters\toggle.css' |
@thiagocaiubi Thanks! I added...
... to my @Simran-B (@sam-falvo ?) Do you know why gitbook decided to deprecate gitbook-cli? |
I am getting this error too. @lzhou1110 I did this and it immediately failed on the next rebuild. EDIT: @thiagocaiubi's solution worked: sed -i.bak 's/confirm: true/confirm: false/g' ~/.gitbook/versions/3.2.3/lib/output/website/copyPluginAssets.js |
My fork |
我已收到您的来信,谢谢。
|
We are running gitbook with some plugins. Plugins are loaded fine but at the end it errors out with different error messages. All of them complains about one or the other plugin file missing. Running gitbook version 2.1.3 on windows 7.
info: 7 plugins are installed
info: loading plugin "prism"... OK
info: loading plugin "edit-link"... OK
info: loading plugin "livereload"... OK
info: loading plugin "search"... OK
info: loading plugin "lunr"... OK
info: loading plugin "fontsettings"... OK
info: loading plugin "theme-default"... OK
info: found 66 pages
info: found 83 asset files
Error: ENOENT: no such file or directory, stat 'C:\Projects\myproject_book\gitbook\gitbook-plugin-fontsettings\buttons.js'
Error: ENOENT: no such file or directory, stat 'C:\Projects\myproject_book\gitbook\gitbook-plugin-lunr\lunr.min.js'
Error: ENOENT: no such file or directory, stat 'C:\Projects\myproject_book\gitbook\gitbook-plugin-livereload\plugin.js'
The text was updated successfully, but these errors were encountered: