selsta, binaryFate: Posted the release thread on reddit

thanks dEBRUYNE

dEBRUYNE: Sure i can do it later today

Do we have release notes for v0.15.0.5?

if not could somebody give me a brief list of the main changes to put in the blog post?

ErCiccione[m]: I put the release notes selsta gave me in the post on reddit

<ErCiccione[m]> dEBRUYNE: Sure i can do it later today <= Thanks!

Perfect, will copy those

with the changes in #6332, requests to the daemon in the python tests are failing with "error: no connection to daemon". the monerod executable does run and my client tests pass against it. perhaps, though, the python tests are not connecting to the monerod executable. any idea what I need to do?

Nothing interesting in the logs ?

all I see in the terminal from the tests are failures that the requests to the daemon are returning a response with an error field, "no connection to daemon"

are there other logs to check?

Since it's about the wallet connecting to the daemon, wallet logs and daemon logs.

It could be either's fault.

Wallet logs are in build/something/monero-wallet-rpc.log

Daemon logs are in ~/.bitmonero/bitmonero.log

more of this

src/wallet/wallet2.cpp:13538 !r. THROW EXCEPTION: tools::error::no_connection_to_daemon2020-03-19 01:16:13.462 [RPC0] WARNING net.http src/wallet/wallet_errors.h:896 //src/wallet/wallet2.cpp:13538:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = get_transaction_pool_hashes.bin

not seeing errors in the daemon log

there should be no functional changes in #6332 for the tests; http_client.h just extends an abstract class

You can bump log level in functional_tests_rpc.py

ok I will try that

weird that I am not seeing any change in the logs after adjusting the log levels in functional_tests_rpc.py, even after re-building

I'm building with make debug-test and ctest --output-on-failure

nevermind think I found my mistake

You don't need to rebuild, it's interpreted.

I run it like this:

./tests/functional_tests_rpc.py /usr/bin/python tests/functional_tests build/release/whatever TEST

And replace TEST with the one that's failing (all also works).

only monero-wallet-rpc.log has errors and the only errors that seem relevant are "no connection to daemon" and 5 instances of "invalid password" in wallet2. otherwise not much is revealed at log level 3

Hey, can someone point me to the monero difficulty calculation system based on how fast or slow blocks are mined?

I just wanted to know the maximum increase and minimum decrease possible in monero block difficulty.

*maximum increase & decrease

next_difficulty_for_next_block (IIRC), src/cryptonote_basic/difficulty.cpp

Thank you very much. You are always a quick replier.

I'll be making an updated run through MR's this weekend, sorry guys, it's been a crazy week here. We're 100% dependant on shipping, and trying to make sure the family's taken care of has been a bit rough. :)