PlebeiusGaragicus
commented
7 months ago Additionally, I am sometimes seeing the following error while running the code:
2024-03-25T06:03:05.274126Z INFO nostr_relay_pool::relay::internal: Connected to wss://relay.mutinywallet.com/
2024-03-25T06:03:05.274591Z INFO nostr_relay_pool::relay::internal: 1 messages queued for wss://relay.mutinywallet.com/ (capacity: 1023)
2024-03-25T06:03:05.662336Z INFO nostr_relay_pool::relay::internal: Connected to wss://relay.damus.io/
2024-03-25T06:03:17.166188Z WARN nostr_relay_pool::relay::internal: Timeout reached for REQ 1b593791b67dcaecebb03cd012f3918d, auto-closing.
Traceback (most recent call last):
File "/Users/satoshi/Downloads/NOSTR/NOS4A2/new_nostr.py", line 30, in <module>
client.zap(ZapEntity.public_key(pk), 20, None)
File "/Users/satoshi/Downloads/NOSTR/NOS4A2/venv/lib/python3.10/site-packages/nostr_sdk/nostr_sdk.py", line 4440, in zap
_rust_call_with_error(_UniffiConverterTypeNostrSdkError,_UniffiLib.uniffi_nostr_sdk_ffi_fn_method_client_zap,self._uniffi_clone_pointer(),
File "/Users/satoshi/Downloads/NOSTR/NOS4A2/venv/lib/python3.10/site-packages/nostr_sdk/nostr_sdk.py", line 363, in _rust_call_with_error
_uniffi_check_call_status(error_ffi_converter, call_status)
File "/Users/satoshi/Downloads/NOSTR/NOS4A2/venv/lib/python3.10/site-packages/nostr_sdk/nostr_sdk.py", line 374, in _uniffi_check_call_status
raise error_ffi_converter.lift(call_status.error_buf)
nostr_sdk.nostr_sdk.NostrSdkError.Generic: zapper: timeout
2024-03-25T06:03:17.364020Z INFO nostr_relay_pool::pool::internal: Relay pool shutdown
2024-03-25T06:03:17.364181Z INFO nostr_relay_pool::relay::internal: Completely disconnected from wss://relay.mutinywallet.com/
2024-03-25T06:03:17.364186Z INFO nostr_relay_pool::relay::internal: Completely disconnected from wss://relay.damus.io/But, this doesn't prevent 10 sat zaps from succeeding, and does not prevent the dev's portion from being paid.
yukibtc
benthecarman
Describe the bug
While using the example python code for zapping and connecting to my mobile Mutiny wallet (auto-pay enabled), zaps are split by client.zap() to pay the devs - this is fine, I'm happy to contribute. Yet, zaps 20 sats or more don't complete, but the dev's portion always finishes. I can see in Mutiny that the split amount is paid to the devs, but the remaining amount hangs unpaid. BUT, when I zap an amount less than 20 sats it goes through with no issues. There is a log output of:
To Reproduce
I used the example code, plugged in my pubkey (with valid LUD16 in my profile) and plugged in my NWC URI from Mutiny.
Expected behavior
I expect the zap to be auto-paid by mutiny (or whichever) without issue. Instead, zaps of a certain amount are split to pay the devs and only those invoices are being paid.
Build environment
Additional context
none