unable to publish/add to local lit instance

[necrophcodr]

It appears that as of 1.3.0 (the version I am currently using) it is not possible to use a local upstream as such:
upstream: ws://127.0.0.1:4822

When running lit serve in one terminal, and lit {publish|add} [app].lua ot simply hangs.
The output from the client is:

lit version: 1.3.0
luvi version: v3.1.0
command: {publish|add} [app].lua
load config: /home/USER/.litconfig
Enter PEM pass phrase:
checking for updates: USER/[app]
connecting ws://127.0.0.1:4822

Output from the lit serve command is:

lit version: 1.3.0
luvi version: v3.1.0
command: serve
load config: /home/USER/.litconfig
client connected: 127.0.0.1:[localport]
client command: 127.0.0.1:[localport] - match
connecting ws://127.0.0.1:4822
client connected: 127.0.0.1:[localport2]
client command: 127.0.0.1:[localport2] - match

Nothing happens after this. No data being sent or received, no commits happening to /home/USER/.litdb.git/.

edited

.litconfig:

checked: 143114903
privateKey: /home/USER/.ssh/id_rsa
upstream: ws://127.0.0.1:4822
database: /home/USER/.litdb.git
username: USER
email: same as github
name: USER
defaultUpstream: wss://lit.luvit.io/

[creationix]

Can you try updating to lit 2.0.2? I think the auto-updater is broken in 1.3.0 and it won't see the 2.x series. Perhaps I can publish 1.3.1 with fixed auto-update.

[creationix]

To update manually, just do lit make lit://luvit/lit and move the resulting lit file on top of your old one.

[necrophcodr]

A 1.3.1 would be a good idea, considering it might be broken. I'll update manually, but your solution should probably be considered, if manually updating is considered a workaround rather than a solution.

[necrophcodr]

it appears that the latest version 2.0.2 suffers the same issue on my end.

[creationix]

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 and I was afraid there might be some regressions.

[necrophcodr]

no problem. if you need any additional information, i'll be more than happy to post it.

[creationix]

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?

[creationix]

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.

[necrophcodr]

lit add calls upstream too, from what i can tell. it attempts to connect to ws://127.0.0.1:4822 anyway.

and yes, you are correct, i meant to write 4822, as can be seen in the edited .litconfig i added.

[necrophcodr]

in other words, the output from publish and add is completely identical on my end.

[creationix]

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 content).

This helps. Publish internally does an add first, so the issue must be in add and in this sync check.

[creationix]

@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 in your .litconfig to a new path (append -temp or something)?

[necrophcodr]

I previously tried removing the entire directory completely and running the commands again, with the same result. May have been with 1.3.0, so I'll give it a shot with 2.0.2.

[necrophcodr]

It appears to be an issue even after removing the .litdb.git directory entirely, sync'ing the disks, and then running the commands again.

[creationix]

Did you make any progress on this. I'm still at a loss as how to reproduce the issue.

[necrophcodr]

Unfortunately I have not made any progress. It appears to be related to the specific setup I have on my netbook, considering my desktop works fine with it (lit 2.0.3).

I'll be looking into this a bit more over the coming days, today included, given that I have the spare time.

[creationix]

It appears your netbook is running Linux. Is there something different from your working desktop? OS, arch, firewall, network device?