<o​frnxmr:xmr.mx> jeffro256 . 1 more, can you open 9845 against release? (w/ jbermans suggestion) :) thanks

things are being added because 9844 is not in yet?

at some point things have to stop being added

<o​frnxmr:xmr.mx> no

<o​frnxmr:xmr.mx> zerobin.net/?9de1e9da3d0d15b1#hhDgD…fgAIG9lgtq12D+q1OgwCZ0eWSY6xp7agL8= vtnerd

<o​frnxmr:xmr.mx> died on me again. Wont respond to rpc calls like sync info, but would respond to set_log

<v​tnerd:monero.social> The release branch dying/hanging issue again?

<v​tnerd:monero.social> Last time it locked up the whole os though?

<o​frnxmr:xmr.mx> this is master, but yeah. Doesnr seem identical. Looks like its not completely dead. I tried to shut it down (the nkde) and it responded to shutdown request after 10+mins (but didnt finisj shutting down)

<o​frnxmr:xmr.mx> The first time, it didnt lockup the whole os, but i wasnt able to kill the process

<o​frnxmr:xmr.mx> matrix.monero.social/_matrix/media/…oad/xmr.mx/NdickpMxpUGPloKLzVVqvnGT

<o​frnxmr:xmr.mx> i'm not able to -9 it again

<o​frnxmr:xmr.mx> I tried to kill it 5-10 more times and it worked

<o​frnxmr:xmr.mx> Started up and now its syncing again

after 18.4, probably a good idea to get master out the door, perhaps without the HFs

Hi, my monero stucking here: Found preferred rct inputs for rct tx: 49 (4.500000000000) , what causes this?

Its self hosted wallet-rpc, daemon-rpc. its connected locally. binding 127.0.0.1 between them. node seems full synced

With google search i just found this: "caused by the dns problem" , if dns problem why my node full synced? or how can be sure or debug it

NakedKing: #monero-support is the correct channel

thanks, what about #monero-community-dev?

<t​zadiko:matrix.org> simplewallet.cpp has a line of code `if (info.has_payment_id || !payment_id_uri.empty())`. I'm curious why these two can contradict. In other words, is there a case where has_payment_id is false and payment_id_uri is not empty?