-
Notifications
You must be signed in to change notification settings - Fork 115
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
"'Closewrite' not defined" Error when using Franklin.serve() #1034
Comments
It's something screwy with the HTTP package (it could be better handled at the LiveServer level which I also maintain, but for this I need to understand the issue at HTTP level and that code base is too obscure for me) More importantly though: usually these errors show up but don't harm the actual functioning of |
The error does affect the output. When I open localhost:8000 with the browser I get nothing (opening the browser also seems to be what triggers the error). It doesn't seem to actually crash the server, though; I have to use Ctrl-C to terminate it. I'm going to nose around and see if I can find a workaround. |
Well, I'm not sure why, but everything is working now. One of these mysteries of computing. Perhaps a bad sprite had infested my computer last time. I'll let you know if the problem reappears. |
So FYI I'm aware of this kind of problem popping up when eg:
This will typically show errors probably because the socket was dropped and then reopened (or something magical of the sort) Same kind of stuff can happen when using several browsers and using different tabs and, again, refreshing stuff around the time a server is restarted. If you happen to recreate the problem and got to it via another route, let me know, it's always useful! |
I am using Franklin with Julia 1.9.2 on Debian. When I follow the instructions on the main Franklin site, the site files are generated, but when I open a browser on localhost:8000, nothing shows, and I get the following error:
(The error repeats multiple times, but it's always the same.) I've used Franklin before and never seen this error before. I'm not sure if it's a Franklin error or something screwy with the HTTP package.
Any help would be appreciated. Thanks.
The text was updated successfully, but these errors were encountered: