Tim Caswell
Tim Caswell
Thanks for finding this bug and sorry for the frustration. I'll try to reproduce it. Between 1.2.x and 2.x there were over 1000 new lines of code in the refactor...
Since your client is connecting, I assume that `ws://127.0.0.1:4288` was a typo and you meant `ws://127.0.0.1:4822`?
Wait, did you say it hangs on both `lit add` and `lit publish`? If so then the upstream isn't the culprit since add is local-only.
Ahh, now I remember. If you have an active upstream, lit add will first check for remote updates. This is a safety measure to prevent version conflicts (same version, different...
@necrophcodr I still can't reproduce it. I wonder if it's something in your local db that's triggering the bug. As a test, can you change the path to your db...
Did you make any progress on this. I'm still at a loss as how to reproduce the issue.
It appears your netbook is running Linux. Is there something different from your working desktop? OS, arch, firewall, network device?
@urzds thanks for fixing the wiki, I missed that one when the behavior changed early on. @squeek502 thanks for helping out. I'm on vacation for the next while building a...
You can't run any scripts as part of publish or install, but there is some logic to use pre-built binaries. It's documented at https://github.com/luvit/lit/wiki/Publishing-Compiled-Code I hope this works for your...
Yes, this would be a neat feature, but the official luvi doesn't even distribute the header files required for this in the distribution. I do publish a full source tarball...