Noise plugin hangs while trying to receive the most recent message
See original GitHub issuerecvmsg with no id works as it should, but using the most recent received message id it behaves the same way, as if I didn’t enter an id at all. I am able to retrieve older messages, and the output lists the correct number of messages, I am just incapable of reading the most recent one. I have some commands I’ve been running with outputs, if this helps.
user@user-ThinkPad-T420:~/lightning$ l3-cli sendmsg 03c1002e4832efc5528907ac08d4b628c454dfe4507192fbcf219aa5ef979872e2 "test 1"
{
"route": [
{
"id": "03645cd14343cb9a325d1244c396bfb023b6ba49ec23e16bf2e8beb41dfd445273",
"channel": "378x1x1",
"direction": 0,
"msatoshi": 11,
"amount_msat": "11msat",
"delay": 15,
"style": "tlv"
},
{
"id": "03c1002e4832efc5528907ac08d4b628c454dfe4507192fbcf219aa5ef979872e2",
"channel": "378x2x1",
"direction": 0,
"msatoshi": 10,
"amount_msat": "10msat",
"delay": 9,
"style": "tlv"
}
],
"payment_hash": "b0b158521ee9ed956e5707c2708e39c8a02f8281fdc6888b636581b0f0d854b3",
"attempt": 1
}
user@user-ThinkPad-T420:~/lightning$ l1-cli recvmsg 0
^C
user@user-ThinkPad-T420:~/lightning$ l3-cli sendmsg 03c1002e4832efc5528907ac08d4b628c454dfe4507192fbcf219aa5ef979872e2 "test 2"
{
"route": [
{
"id": "03645cd14343cb9a325d1244c396bfb023b6ba49ec23e16bf2e8beb41dfd445273",
"channel": "378x1x1",
"direction": 0,
"msatoshi": 11,
"amount_msat": "11msat",
"delay": 15,
"style": "tlv"
},
{
"id": "03c1002e4832efc5528907ac08d4b628c454dfe4507192fbcf219aa5ef979872e2",
"channel": "378x2x1",
"direction": 0,
"msatoshi": 10,
"amount_msat": "10msat",
"delay": 9,
"style": "tlv"
}
],
"payment_hash": "4876098fa27d5d82b9cd706631e357884f066438ba1921fc6d43bb8b4205d9bd",
"attempt": 1
}
user@user-ThinkPad-T420:~/lightning$ l1-cli recvmsg 0
{
"id": 0,
"sender": "02cfd15aa88deb05a7e9395a41922b995051d6384e831bf422da684286fda8a7ca",
"body": "test 1",
"signature": "207ca8e5e6e4290e04d030f5c66197d88fafbe0ccaa59165f78c4c37083c3920ff093d9a0322412ddf1320226d490f9fac28e44fcda4da58b83d1f5fecefa50efc",
"payment": null,
"verified": true,
"total_messages": 2
}
user@user-ThinkPad-T420:~/lightning$ l1-cli recvmsg 1
{
"id": 2,
"sender": "02cfd15aa88deb05a7e9395a41922b995051d6384e831bf422da684286fda8a7ca",
"body": "test 3",
"signature": "1fa0a83f55285efb5b812592a7c783ab10bef0bdbed60e82d8b02d3020da925d196f357bbf2ccb09e8e617b95915ed49c13c0944a706dcf9d5c9dcd8555f84e5ed",
"payment": null,
"verified": true,
"total_messages": 3
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
A plugin crashed Gig Performer - how to find out which one
Click on the File menu, then click on Open Recent and choose your gig file. If Gig Performer still crashes, repeat the steps...
Read more >Plugins crashing Pro Tools - Avid Pro Audio Community
So your first step in troubleshooting is to move plugins to unused plugins folder and see if PT works as it should. Then...
Read more >Logic Pro X 'hanging' on startup 'scanning audio units ...
I just created a 'Disabled' folder in Library/Audio/Plugins and moved everything to there from the Components folder. Added them back a few at...
Read more >Media Composer quits at Initializing plugin: AMPIPluginDSM.avx
Media Composer crashing on Initializing plugins AMPIPluginDSM. ... of the Plug-Ins folder to a separate folder (preferably a new folder on the desktop)....
Read more >Problems with VST / AU Plugins in FL Studio and Solutions ...
Solution: Make sure the plugin is activated and the latest version installed. AG Works Chorus CH-2. Problem: No sound and the audio monitor...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
When one finds a bug, its generally good to have a testcase that shows the issue for the following reasons:
So its not always a hard requirement, but good practice 😃