.merge+ 7202 7203

Added

.merges

merges would be nice

all i want for christmas is my merge list merged, my merge list merged, my merge list meeeerged

.merges

hmm. the get_info RPC seems to return an incorrect count of rpc connections

maybe it's not counting the restricted rpc sessions

Hello. I have added the requested documentation to by icecc branch. I hope it meets your standards: monero-project/monero #7160

.merges

<hyc "hmm. the get_info RPC seems to r"> It only counts RPC connections for the RPC port you’re hitting.

has monero a fixed max mempool size?

Something like 300 MB by default IIRC. You can alter with an option, see monerod --help.

ok thx, the same size as bitcoin.

Look on the bright side. At least you don't need to rant about signs of life from fireice_uk .

.merges

please also CLI merges

.merge+ 7205 7206

Added

.merges

^ luigi1111, can you do some CLI merges too?

probably today but not right now

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?

I guess it depends on what you do

selsta: I'm trying to familiarize myself with monero at the moment. I've got a development background with OS / networking.

if you work on things with consensus changes you will need your own testnet

else normal testnet / stagenet is probably fine

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.

Depends what you want to test. I usually use --testnet --offline --fixed-difficulty 1.

moneromooo: perfect! thanks

Testnet works for me, but maybe the testnet seed nodes are wobbly, as they were occasionally in the past?

rbrunner: I can't connect to monero-testnet.exan.tech 28081 (ref: monerodocs.org/infrastructure/networks )

that doc seems way outdated.

just start the daemon with the --testnet flag

you can use the same --data-dir as normal, everything testnet related will go in a testnet subdirectory

same thing for --stagenet

Ah, I thought you were talking about running your own daemon ...

ndorf: nice so it won't clobber mainnet blocks?

definitely not

it will have its own blockchain and log files under that subdirectory

ndorf, rbrunner: thanks looks like I'm up and running!

.merges

7193 needs to be reviewed still, no approvals.

Merged other than 7193

But it's the same as 7192 and that one is merged

Oh, my bad.

Lemme chuck a note on and I'll merge 7193, usually I merge em in pairs to avoid that.

Merged, note added.

Snipa: we have 7207 on top of 7192 which vtnerd reviewed

Is 7207 ready for merge? Not in list.

not yet

kk.

.merge+ 7218 7219

Added

can someone point me to the gitify directions

please

.merge+ 7207 7208

Added

once 7207 has an approval we can tag v0.17.1.8

will that approval be noted here?

Perhaps you'll find this one interesting from the IT point of view. A simple magic.

mj-xmr: I have issues with ccache on Mac

execute_process(COMMAND "${CCACHE_FOUND}" "${CMAKE_CXX_COMPILER}" "${TEMP_CPP_FILE}" RESULT_VARIABLE RET) returns 1

but when I manually do `ccache clang test.cpp` it returns 0

where oes stderr go for those execute_process invocations?

I assume ERROR_VARIABLE

I can try that

hyc: Error: ld: library not found for -lc++

that is the error

it's probably not named libc++

cmake/FindCcache.cmake:49 is the corresponding file

I wonder if the test would be sufficient with -c and no linking

or if it would just break the same way on a real program target

the test used to work fine, this is new

maybe I updated compiled or cmake

compiler*