I still feel the allowable growth is excessively large monero-project/research-lab #70#issuecomment-785193630 <---- Take a look at bitinfocharts.com/comparison/transactions-ltc-xmr.html#log

Monero exceeded the current rate in July / September 2016 and again in February - May 2019 Litecoin went over 80x in 2017 when Bitcoin seized up

Over 80x in one year.

Set this too low and it will trigger the issue 70. All it would take for example is a successful 51% attack on BCH for example

Take a look at the volatility in BCH hashrate bitinfocharts.com/comparison/hashrate-bch.html#log

The reason for the 2x growth in the long term median is the Monero network needs to be able to respond over a 4 month to a year period to actual and possible, even likely, fluctuation in transaction demand.

I also should be able to comment and provide a response.

I wonder if we could try turning off the contributors only tag again

there's not an option for automatic recurring payments in the wallet, is there? was considering working on that

I commented on pull 7819

luigi1111w: worth a try IMO

selsta: while merging, 7780 is fine, just choked on a connection problem.

DangrOnTheRangr -> Whilst the exact mechanics would need some testing - that would be very exciting to see (the option for automatic recurring payments)

"monero-project/monero #7797", mj-xmr, was it the first time you saw compiler wrapper written in form of shell script ? they're used everywhere and work, this pr is an ugly try to workaround bad wrapper instead of fixing it

Change your tone please, as a starter.

"CCache expects an executable file." there is `chmod 755 bin/*` which adds `+x`, so those files are executable

I meant a binary.

How did you debug that try_compile ? Can you paste exact error you saw there ?

<wfaressuissia[m]> ""CCache expects an executable..." <- Just double checked. These scripts are already executable.

wfaressuissia[m]: I will check after work.

Debug of try_compile is a real pane since there is no cmake flag to show stdout/stderr of build process, which would simplify it significantly. But there would be quite vocal error related to syscall which can be easily reproducud in isolated way. And the fix is small too.

Does decoy selection bug affect whole transactions that spent within 30 minutes?

I spent xmr within 30 minutes right after recieving from exchange.

I read <1% of transactions affected, this mean there's a probability of mine not affected?

rebsdar3[m], better for #monero, but yeah, you should be fine. you'd have to try real hard to spend in the same block its ok to spend

Thank you 💯

<wfaressuissia[m]> "Debug of try_compile is a real..." <- Basically that's why I asked the author for help.

"I will check after work." waiting for this, it's try to debug how you debugged that problem, lol

FWIW, seeing there's an issue with scripts not being liked reminds me that in some cases, scripts are forbidden as binaries due to security reasons, the details of which I forget. Might be related.

Though I think I remember using a one off script as compiler for ccache so I could see the command line the compiler ended with, so that did work. It was linux though.

moneromoooo: I know the solution, just trying to reconstruct debugging actions that lead to the pr

<wfaressuissia[m]> "moneromoooo: I know the solution..." <- I don't play games here. Too old.

Just show the solution and I can close that PR.

Your double check would be useful

<wfaressuissia[m]> "Your double check would be..." <- I sometimes have hard time to get your real intentions. At the same time I'm happy that you improve my PR one way or another.

In meantime I recalled how I got this error message.

I called ccache's link to the compiler and then the file to be compiled. You can achieve this with prepending the PATH with the ccache's directory (that /usr/lib/ccache or sth)

Or course the FreeBSD's version.

ccache then wrote, that it expected a binary, not a text file.

And "The compiler" was the script in question.

"... ccache then wrote, that it expected a binary" exact error msg is needed

I don't remember and I couldn't even find it in the source code.

Why do you need the exact msg?

to avoid any ambiguity since interpretation is biased a bit

In the end you'll have your double-check once you see that the CMake script detects a working ccache.

At least the CMake script is so rough, that if there's any mistake, it aborts.

wait, did you add ccache detection initially only due to freebsd failure ?

Yep.

Precisely the check if it works was done only for FreeBSD.

then whole journey is a about complex workaround instead of proper fix

Be my guest.

FWIW I'd been using ccache with monero for years before all that. It worked just fine.

once there is small isolated reproducible test the fix is obvious for anyone, even 0 knowledge students

moneromoooo: It has never worked on Github before.

presumably you have to set cmake to use it

"travis-ci.org/github/monero-project/monero/jobs/675745041#L1575" this is it

"monero-project/monero #6452#issuecomment-614670232" from here

"ccache: error: execv of /home/travis/build/monero-project/monero/contrib/depends/x86_64-unknown-freebsd/native/bin/clang-8 " how would you reproduce it in isolated way ?

"... failed: Exec format error"