09:14:24 <liamswenson[m]> I'm trying to use monero-wallet-rpc to handle payments, and it seems to update incomming transactions rather slow. Is there a way to change the interval or make it update early? Otherwise I may just have to query the daemon, I'd rather not add the complexity though.
09:36:07 <rbrunner> Define "slow". I checked, default is every 20 seconds. You can set a new intervall with COMMAND_RPC_AUTO_REFRESH
09:54:06 <rbrunner> Do you already tell it to give back transactions in the pool? If you only query confirmed / mined transactions there is of course quite some delay, you have to wait until the next block.
09:58:58 <liamswenson[m]> <rbrunner> "Define "slow". I checked..." <- sounds about right, and the env var was just what I was looking for thanks!
10:01:29 <rbrunner> Alright :) Not sure what you mean with "env var", in any case it's an RPC call to set it to a new value
10:01:31 <moneromooo> The placebo effect id real :D
10:02:24 <rbrunner> As long as they don't want to manage 100,000,000 subaddresses, everything is alright
10:04:40 <liamswenson[m]> rbrunner: Oh lol, I'm new to RPC sorry. Is there documentation for this? I was using monerodocs but it didnt seem to mention the refresh interval.
10:05:22 <rbrunner> Well, I always directly consult the corresponding C++ header file because that can't possibly be out of date, or incomplete.
10:05:35 <rbrunner> Most calls are pretty clear by just reading the declaration
10:05:37 <moneromooo> Call the auto_refresh RPC, pass enabled as true, period as an integer, number of seconds.
10:06:17 <rbrunner> src/wallet/wallet_rpc_server_commands_defs.h
10:06:39 <rbrunner> moneromooo knows that by heart by now, I guess :)
10:08:06 <moneromooo> No, I just looked into my RPC shell script.
10:08:37 <liamswenson[m]> Thanks for the help guys, appreciate it 
17:08:20 <jtgrassie> rbrunner: "Well, I always directly consult the corresponding C++ header" same, which is why I ended up creating a script to quickly lookup/run, https://github.com/jtgrassie/xmrpc
17:09:34 <rbrunner> Well, that's the next level, obviously :) Nice, never saw that.
17:11:03 <jtgrassie> `xmrpc.sh doc auto_refresh` looks up the request struct
17:12:00 <jtgrassie> I got sick of outdated 3rd party docs and wanted a quick way to get exact params and a quick way to call
17:13:57 <rbrunner> Maybe would get some more visibility and love as part of the Monero ecosystem project?
17:20:05 <jtgrassie> I mean, its just a tool I wrote to aid my owen purposes, but sure, fork it to the ecosystem project if you think others might like
17:20:27 <jtgrassie> *my own
17:21:03 <jtgrassie> it could certainly be improved though!
18:11:04 <scoobybejesus> my hashes match hyc.  gitian-build.py is really noisy now w/ "Copying to container - X" over and over
20:59:53 <hyc> hm, I don't recall seeing a lot of new spam output
20:59:57 <hyc> can you pastebin that too?
23:34:10 <scoobybejesus> The README says the host should be on Ubuntu 18.04.  My 18.04 host hasn't been able to complete a build with dockrun.sh since v0.17.3.2.  uname -a shows I'm on 4.15.0 kernel, which seems old, but the system is otherwise up to date. Though I'd like to do-release-upgrade to 20.04 or even 22.04.  Can I?  ... Anyway, my scroll back was limited to 5k lines, and it was mostly filled with "Copying to container - xMB".  I was 
23:34:10 <scoobybejesus> more interested in trying to get dockrun.sh to work (or figure out why it wouldn't), and builder/var/build.log just stops and I don't see any error at or near the end, and I gave up looking. So I tried plain old gitian-builder.py again with '| tee' to a file to capture it all, and it's not noisy this time. Maybe something related to cache/packages between the last tag and building the release now. But yeah, evidence of 
23:34:10 <scoobybejesus> the spammy misbehavior is gone...