01:30:38 selsta: How do you suggest I implement a sort of status label in the GUI for the I2P router's up/down status? 01:31:11 It seems the best way is to make a C++ function invokable from Qt that uses QTcpSocket to ping the SAM bridge 01:31:32 I'm not completely sure though, and it might be a pain if we don't use Qt networking stuff already 03:51:34 This is what it looks like right now 03:51:38 https://mrelay.p2pool.observer/m/matrix.org/BIHwiStUlwuCjEcFmjnmnMNT.png (clipboard.png) 09:19:33 yes, we don't use Qt networking so I'd prefer not adding that dependencies 09:19:40 the epee http client might work? 09:20:15 Also I'm not really sure how the integration looks like, what exactly happens once you select I2P? 13:42:52 Hi. Does anyone know how to resolve an error when attempting to Solo Mine on the Linux GUI? 13:47:28 The log seems to indicate it cannot “find” the daemon despite running a fully synced local node. I have screenshots and the full log in case it helps shed some light. 14:02:55 sure, send screenshots 14:29:56 https://mrelay.p2pool.observer/m/zano.org/bNcEBUCXNTiJCEjoHtrdWrEc.png (Local Node Daemon.png) 14:30:10 https://mrelay.p2pool.observer/m/zano.org/oJucKHvlraieOnhskqCWFytY.png (Mining Error.png) 14:30:21 https://mrelay.p2pool.observer/m/zano.org/iDhyYVNdhtHlCOxejBUvpyEG.png (GUI Log.png) 14:55:19 .merge+ 4623 14:55:19 Added 17:20:13 selsta: It just restarts the daemon with the SAM flag 17:23:53 fwiw, i think the sam flag should probable go into the gui config file 17:27:01 Maybe, but also, it only works in its current state with a local full node 17:27:14 SAM is integrated only into the daemon (not wallet2, etc.) 17:28:28 yes, but other flags are in gui config 17:28:54 like pruneBlockchain=true 17:29:17 Makes sense, I didn't know that :) 17:29:44 blockchainDataDir etc 17:29:57 selsta: SAM uses raw TCP instead of HTTP. Would Boost work better for that then? 17:30:00 yeah, i only learned about it when looking into it for another user 17:30:30 FWIW the header I'm using currently is 17:34:02 ok, but if it restarts the daemon with sam flag i don't know if it makes sense to add sam logic into the GUI, the daemon should say if it works, no need to manually do raw TCP 17:34:19 No, it's for giving up/down status of the I2P router 17:34:38 i know but why is that info not given by daemon 17:35:55 How would it be given from the daemon and displayed in a text label (see above screenshot)? My understanding is that would require a new RPC endpoint or something 17:36:53 The current commit I have for it on my fork works functionally perfectly fine (using Qt sockets) 17:43:15 I feel like there is a layer mismatch here. The daemon is the one communicating with SAM, so it's the daemon that should say if it can access to router or not. Adding custom TCP code to the GUI is not the right solution, especially since other projects would have to copy this. 17:43:29 And this isn't taking into account that I'm currently working on Qt6 upgrade where we would slim down unused packages. 17:44:36 For context, this is the code in question 17:44:36 https://codeberg.org/jpk68/monero-gui/pulls/5/files#diff-6f375bc7f27fdf27a15f90b345abbf30f8757cd0 17:44:49 It does not communicate over SAM, it literally just sees whether the socket is open 17:46:23 If you're just using the daemon by itself, you can already see through the error messages if the SAM bridge is not open. However, the daemon logs are somewhat opaque in the GUI (by design) and it would be nice to have a friendly, graphical way to see router status. As is mentioned in the CCS :) 17:47:23 but isn't that also misleading? it just checks a port, it does not even tell if it is a SAM router running? 17:48:08 adding a huge Qt depedency (network) for a port check seems like a waste 17:48:23 I would prefer if the daemon itself would give a status message to the gui somehow, I can't tell you the best design for it yet 17:48:30 dependency 17:53:44 It checks the address + port combo provided by the user. I agree with you in that we shouldn't add more dependencies > but isn't that also misleading? it just checks a port, it does not even tell if it is a SAM router running? 17:54:04 Since we already use Boost.Asio that might be a bit better (?) 17:57:27 we don't use any boost code in monero-gui currently but it's a dependency from monero itself 17:57:33 also not ideal hmm 17:59:25 I would prefer not to use the POSIX API, lol 18:16:13 Looks like the epee thing worked 19:43:23 .merge+ 4625 19:43:23 Added 20:59:22 .merges 20:59:22 4623 4625 21:05:28 done 22:16:27 .merge+ 4626 22:16:27 Added 22:31:49 luigi1111: please also merge ^ and tag v0.18.5.1 gui 22:33:35 🚀 22:53:14 .merges 22:53:14 4626