search

fiatjaf / noscl

Command line client for Nostr.
Other
269 stars 53 forks source link

noscl publish hangs after publishing on master #51

Open 1ma opened 1 year ago

1ma commented 1 year ago

Commit 3334f27a953c04657fc5b7a303757910928b5b25 introduced some change that makes the command hang after successfully publishing a note. I can see these notes on https://nostr.guru and other clients, but noscl doesn't finish execution. The previous commits up to the latest tagged release (0.6.0) seem to work fine.

I'm on Ubuntu 22.04 and installed noscl with go install github.com/fiatjaf/noscl@3334f27a953c04657fc5b7a303757910928b5b25 using Go 1.20.2, if that helps.

Sample output of the hanged command after a few minutes:

$ noscl publish 3334
Sent event b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 to 'wss://nostr.bitcoiner.social'.
Sent event b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 to 'wss://nos.lol'.
Sent event b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 to 'wss://relay.orangepill.dev'.
Sent event b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 to 'wss://nostr-pub.wellorder.net'.
Sent event b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 to 'wss://relay.damus.io'.
Sent event b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 to 'wss://relay.snort.social'.
Sent event b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 to 'wss://relay.nostr.band'.
Sent event b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 to 'wss://nostr.mom'.
Seen b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 on 'wss://nostr.bitcoiner.social'.
Seen b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 on 'wss://nostr.mom'.
Seen b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 on 'wss://relay.damus.io'.
Seen b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 on 'wss://nos.lol'.
Seen b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 on 'wss://relay.nostr.band'.
Seen b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 on 'wss://nostr-pub.wellorder.net'.
Seen b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 on 'wss://relay.snort.social'.
Seen b3e986b76eab79c35bf3836c1a3d1d824e4bb5903e4cb08570dcea1ca0b8d704 on 'wss://relay.orangepill.dev'.

<> 2023/03/19 12:03:03 read error:  websocket: close 1006 (abnormal closure): unexpected EOF
<> 2023/03/19 12:03:43 read error:  websocket: close 1006 (abnormal closure): unexpected EOF
bndw commented 1 year ago

I've experienced this as well, but have not looked into what's causing it.

fiatjaf commented 1 year ago

This will probably be fixed once we replace go-nostr.