< emilengler>
When are the meetings still? 19:00 UTC?
< instagibbs>
1.5 hours from now it seems
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #17678: depends: Support for S390X and POWER targets (master...1912-dependsNewTargets) https://github.com/bitcoin/bitcoin/pull/17678
< gribble>
https://github.com/bitcoin/bitcoin/issues/16702 | p2p: supplying and using asmap to improve IP bucketing in addrman by naumenkogs . Pull Request #16702 . bitcoin/bitcoin . GitHub
< fanquake>
-Wl,-why_live has been getting some use today as well heh
< digi_james>
lol
< wumpus>
heh
< wumpus>
#topic GUI CLI Arg test framework (emilengler)
< emilengler>
Yes so let me first talk about it
< emilengler>
I made a PR a few day ago "Add -guisettings" (Can someone post the id? I'm on my phone). Tests were suggested for it because it adds a cli paramter
< instagibbs>
#17636
< emilengler>
And there are Qt only cli parameters. I was wondering if it would be worth writing a test framework for qt args as well
< wumpus>
why is this a question? isn't testing things always good? what's the small print?
< emilengler>
wumpus: Good question but it would be some effort und probably a bit maintaince as well and I don't know if it is actually worth to make a new framework (or heavily extend the current one) just for one extra parameter
< wumpus>
I guess GUI things are hard to test in general
< sipa>
well what would it be testing?
< wumpus>
like 'does the window start minimized' is not that easy to measure
< sipa>
right
< emilengler>
sipa: It would test if a file is created
< sipa>
that sounds easy
< sipa>
probably doesn't need much of a "framework" at all
< fanquake>
ryanofsky would like to know your thoughts if you are here
< wumpus>
that's just anbother functional test riight
< fanquake>
Given you are doing the settings refactoring
< emilengler>
wumpus: Maybe we could add an extra qt parameter which makes some stdout. This is then getting parsed
< emilengler>
wumpus: IIRC the current functional test framework is bitcoind only
< wumpus>
anyhow, yes, testing GUI arguments would be nice, some are more realitic for automatic testing than others
< emilengler>
Yes, things like -splash are probably impossible to test
< wumpus>
you can run the currrent functional tests w/ bitcoin-qt
< wumpus>
but yes, that one would be bitcoin-qt only
< emilengler>
Ok still thanks for the clarification :). Things I wanted to say are done. Someone wants to say something about it?
< emilengler>
Otherwise this topic would be done
< wumpus>
let's go to warren's topic then
< sipa>
emilengler: i don't know what exactly you're asking
< wumpus>
#topic announcement of the new mailing list host (warren)
< warren>
I must express apologies for the unexpected timing of transition of lists.linuxfoundation.org to a new host. Dealing with this for the past years has been stressful, evaluated alternatives were all found to have drawbacks and communications between parties has been slow. Oddly enough by not changing we ended up with the best outcome. After a brief service disruption due to misconfiguration the lists were back online later that day. End
< warren>
result:
< warren>
- No change to list addresses or archive URL's.
< warren>
- The new host is cooperative, communicative and will properly maintain the mailing list server.
< warren>
- New dev or announce lists can now be requested. For example bitcoin-knots-announce was created. I will put a policy on a webpage somewhere but it will be roughly: "This list server is for only FOSS and strongly preferred to be pertaining to open common infrastructure, specifications or standards. If you want lists for a niche or commercial project you probably should instead use Google Groups or something."
< warren>
I must thank the Linux Foundation for years of politically neutral hosting of dev lists, and now the Oregon State University Open Source Lab (OSUOSL) for continued vendor neutral hosting. The OSUOSL is well known since the early 2000's for infrastructure support for thousands of Open Source projects.
< warren>
fin
< warren>
next
< warren>
unless people have questions, but this isn't really a dev topic so just FYI
< jamesob>
thanks warren!
< sipa>
thanks for the update
< emilengler>
Thanks
< sipa>
and for all the time it took to get there :)
< wumpus>
thanks warren!
< wumpus>
there was some talk of changing the bitcoin-core-dev mailing list to an announcement list
< wumpus>
as, effectively, that's what it is
< sipa>
is anyone on it?
< wumpus>
I have no idea, if not, I can stop doing announcements there
< warren>
I suppose that's a simple change. Also consider if dev would like special interest group dev lists or other announce lists.
< sipa>
i think for non-mailinglist aliases we can use @bitcoincore.org fine
< warren>
wumpus: I can ask for subscriber statistics, in any case it's helpful to keep posting to the same place because the archives are in a well known location that won't change anytime soon
< wumpus>
there was vaguely some interest in it as announcement list, let me see if I can find the bitcoincore.org PR
< sipa>
so, did anyone ever try running test_running with BITCOIND=.../src/qt/bitcoin-qt ?
< sipa>
it's... very hollywood
< jonatack>
For anyone interested in PR #16702, it will the topic of next week's PR Review Club session, Wednesday 11 December at 1800 UTC
< gribble>
https://github.com/bitcoin/bitcoin/issues/16702 | p2p: supplying and using asmap to improve IP bucketing in addrman by naumenkogs . Pull Request #16702 . bitcoin/bitcoin . GitHub
< instagibbs>
sipa, welcome to cyber
< sipa>
only 10 tests fail
< sipa>
i'm surprised it works that well at all
< sipa>
i did have to click a way a few dozen pop-up error messages
< elichai2>
Lol that sounds funny. I'll try that too :)
< bitcoin-git>
[bitcoin] achow101 opened pull request #17681: wallet: Keep inactive seeds after sethdseed and derive keys from them as needed (master...keep-inactive-seeds) https://github.com/bitcoin/bitcoin/pull/17681
< bitcoin-git>
[bitcoin] hebasto closed pull request #17600: qt: Remove connection for unused accepted() signal in ReceiveRequestDialog (master...20191125-unused-connection) https://github.com/bitcoin/bitcoin/pull/17600