00:18:37 .merge+ 7202 7203 00:18:38 Added 00:37:17 .merges 00:37:17 -xmr-pr- 7193 7196 7197 7202 7203 01:31:28 merges would be nice 04:36:22 all i want for christmas is my merge list merged, my merge list merged, my merge list meeeerged 07:18:18 .merges 07:18:18 -xmr-pr- 7193 7196 7197 7202 7203 08:24:24 hmm. the get_info RPC seems to return an incorrect count of rpc connections 08:24:33 maybe it's not counting the restricted rpc sessions 11:15:20 Hello. I have added the requested documentation to by icecc branch. I hope it meets your standards: https://github.com/monero-project/monero/pull/7160 11:15:24 .merges 11:15:24 -xmr-pr- 7193 7196 7197 7202 7203 13:35:22 It only counts RPC connections for the RPC port you’re hitting. 15:08:22 has monero a fixed max mempool size? 15:09:18 Something like 300 MB by default IIRC. You can alter with an option, see monerod --help. 15:10:05 ok thx, the same size as bitcoin. 15:28:14 Look on the bright side. At least you don't need to rant about signs of life from fireice_uk . 16:01:17 .merges 16:01:17 -xmr-pr- 7193 7196 7197 7202 7203 16:07:15 please also CLI merges 16:27:33 .merge+ 7205 7206 16:27:33 Added 16:33:56 .merges 16:33:56 -xmr-pr- 7193 7196 7197 7202 7203 7205 7206 16:34:03 ^ luigi1111, can you do some CLI merges too? 16:34:18 probably today but not right now 16:53:39 Hi I introduced myself the other day. I'm in the process of setting up my dev env. Question for developers: do you typically interact with test / stagenet or do you stand up your own standalone network env? 16:54:09 I guess it depends on what you do 16:56:49 selsta: I'm trying to familiarize myself with monero at the moment. I've got a development background with OS / networking. 16:59:03 if you work on things with consensus changes you will need your own testnet 16:59:14 else normal testnet / stagenet is probably fine 17:17:36 selsta: ok thanks. I'm having trouble connecting to testnet atm (Is it down?) also having challenges with stagenet.. I guess I'll go with my private testnet for now. 17:30:38 Depends what you want to test. I usually use --testnet --offline --fixed-difficulty 1. 17:31:44 moneromooo: perfect! thanks 17:34:00 Testnet works for me, but maybe the testnet seed nodes are wobbly, as they were occasionally in the past? 17:35:52 rbrunner: I can't connect to monero-testnet.exan.tech 28081 (ref: https://monerodocs.org/infrastructure/networks/ ) 17:36:19 that doc seems way outdated. 17:36:23 just start the daemon with the --testnet flag 17:36:42 you can use the same --data-dir as normal, everything testnet related will go in a testnet subdirectory 17:36:54 same thing for --stagenet 17:37:38 Ah, I thought you were talking about running your own daemon ... 17:39:41 ndorf: nice so it won't clobber mainnet blocks? 17:39:48 definitely not 17:40:22 it will have its own blockchain and log files under that subdirectory 17:42:22 ndorf, rbrunner: thanks looks like I'm up and running! 19:35:44 .merges 19:35:45 -xmr-pr- 7193 7196 7197 7202 7203 7205 7206 19:39:47 7193 needs to be reviewed still, no approvals. 19:42:56 Merged other than 7193 19:43:33 But it's the same as 7192 and that one is merged 19:44:01 Oh, my bad. 19:44:40 Lemme chuck a note on and I'll merge 7193, usually I merge em in pairs to avoid that. 19:52:17 Merged, note added. 19:55:58 Snipa: we have 7207 on top of 7192 which vtnerd reviewed 19:56:38 Is 7207 ready for merge? Not in list. 20:16:50 not yet 20:57:21 kk. 21:07:56 .merge+ 7218 7219 21:07:57 Added 21:20:07 can someone point me to the gitify directions 21:20:09 please 21:23:58 .merge+ 7207 7208 21:23:58 Added 21:25:50 once 7207 has an approval we can tag v0.17.1.8 21:26:47 will that approval be noted here? 21:53:05 Perhaps you'll find this one interesting from the IT point of view. A simple magic. 21:53:07 https://github.com/monero-project/monero/pull/7217 22:59:02 mj-xmr: I have issues with ccache on Mac 22:59:11 execute_process(COMMAND "${CCACHE_FOUND}" "${CMAKE_CXX_COMPILER}" "${TEMP_CPP_FILE}" RESULT_VARIABLE RET) returns 1 22:59:31 but when I manually do `ccache clang test.cpp` it returns 0 23:02:09 where oes stderr go for those execute_process invocations? 23:03:55 I assume ERROR_VARIABLE 23:03:56 I can try that 23:17:43 hyc: Error: ld: library not found for -lc++ 23:17:52 that is the error 23:18:34 it's probably not named libc++ 23:18:56 cmake/FindCcache.cmake:49 is the corresponding file 23:20:56 I wonder if the test would be sufficient with -c and no linking 23:21:31 or if it would just break the same way on a real program target 23:21:45 the test used to work fine, this is new 23:21:53 maybe I updated compiled or cmake 23:21:56 compiler*