08:20:17 <dEBRUYNE> selsta, binaryFate: Posted the release thread on reddit
08:57:43 <binaryFate> thanks dEBRUYNE
10:22:07 <ErCiccione[m]> dEBRUYNE: Sure i can do it later today
10:55:09 <ErCiccione[m]> Do we have release notes for v0.15.0.5?
10:55:38 <ErCiccione[m]> if not could somebody give me a brief list of the main changes to put in the blog post?
11:28:28 <dEBRUYNE> ErCiccione[m]: I put the release notes selsta gave me in the post on reddit
11:28:34 <dEBRUYNE> <ErCiccione[m]> dEBRUYNE: Sure i can do it later today <= Thanks!
11:35:08 <ErCiccione[m]> Perfect, will copy those
12:08:03 <woodser> 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?
12:09:09 <moneromooo> Nothing interesting in the logs ?
12:11:21 <woodser> 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"
12:11:26 <woodser> are there other logs to check?
12:12:05 <moneromooo> Since it's about the wallet connecting to the daemon, wallet logs and daemon logs.
12:12:11 <moneromooo> It could be either's fault.
12:13:05 <moneromooo> Wallet logs are in build/something/monero-wallet-rpc.log
12:13:14 <moneromooo> Daemon  logs are in ~/.bitmonero/bitmonero.log
12:16:09 <woodser> more of this
12:16:13 <woodser> 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
12:19:05 <woodser> not seeing errors in the daemon log
12:21:32 <woodser> there should be no functional changes in #6332 for the tests; http_client.h just extends an abstract class
12:25:51 <moneromooo> You can bump log level in functional_tests_rpc.py
12:26:24 <woodser> ok I will try that
13:51:39 <woodser> 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
13:52:02 <woodser> I'm building with make debug-test and ctest --output-on-failure
13:54:13 <woodser> nevermind think I found my mistake
13:57:17 <moneromooo> You don't need to rebuild, it's interpreted.
13:57:28 <moneromooo> I run it like this:
13:57:59 <moneromooo> ./tests/functional_tests_rpc.py /usr/bin/python tests/functional_tests build/release/whatever TEST
13:58:10 <moneromooo> And replace TEST with the one that's failing (all also works).
15:03:56 <woodser> 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
16:29:21 <cyyber> Hey, can someone point me to the monero difficulty calculation system based on how fast or slow blocks are mined?
16:29:51 <cyyber> I just wanted to know the maximum increase and minimum decrease possible in monero block difficulty.
16:30:11 <cyyber> *maximum increase & decrease
16:31:07 <moneromooo> next_difficulty_for_next_block (IIRC), src/cryptonote_basic/difficulty.cpp
16:31:57 <cyyber> Thank you very much. You are always a quick replier.
19:40:02 <Snipa> 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. :)