Just three days after this post and the bug has shown again. But the improved debug logging helped and so it looks like it is identified and fixed now.
nostr:nevent1qqsxwtzpls95pahjyhwq99sn79ccxncj7uzk27m3429je3v6n53q6qgpr3mhxue69uhkummnw3ezuumhd9ehxtt9de5kwmtp9e3kstczyzdxdgwhu0dj2tng673ux4usy24ms9gfrrargf6d4sn2cqqqyp5d5qcyqqqqqqgu542sp
Ich bin sehr gespannt ob das wirklich stimmt und der Bug (ein deadlock) jetzt wirklich Geschichte ist.
nostr:nevent1qqsdle4yd0lk4aj6vpz5qguenl25xn8d6r6jrl4zhcnhwpp6ckpecsgprdmhxue69uhkummnw3ezuumhd9ehxtt9de5kwmtp9e3ksq3qnfn2r4lrmvjju6xh50p40ypz4wup2zgclg6zwndvy6kqqqpqdrdqxpqqqqqqzvrfv9n
Please Login to reply.
No replies yet.