Agree with Fabien. This is how we identified issues with the previous hardfork activation, but it was never landed on master.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 29 2019
Why does setting greatwallactivationtime uncover this config issue? Seems like there's another underlying problem. I noticed the Core PR didn't give much info about its discovery either. Is this a spurious/flaky failure or is it triggered by some specific action?
Regarding the warning: https://github.com/bitcoin/bitcoin/issues/10030 Looks like Core didn't care about the issue much either.
Will green once release notes are in a reviewable state.
Still unable to recv it on SKS or MIT keyservers.
Some items in the summary need to be called out in release notes.
Not only the new features, but also the behavior changes. The behavior changes are actually more important, IMO, as some people have complex configurations that could mysteriously break.
I see the last commit in that PR has release notes: https://github.com/bitcoin/bitcoin/pull/11862/commits/c25321ff96737bdba80d626d2425ef02c7a4c181 Since you're breaking these changes up, do you think updating the release notes to match the current state makes sense, or are you going to just tack c25321ff onto the end once you're done?
Jan 28 2019
Please rebase and then bug me if I don't get to reviewing this again in the next few days.
We talked more offline and it's clear that using this keyserver by default doesn't not work well on all configurations. It just happens to work well on my machines.
Tried recv-keys on this fingerprint and I get nothing. Please double check that it's available on a few keyservers.
I support this, but I'll wait for @deadalnix to sign off
I'm against this because the default configuration for Ubuntu tends to pick a server like pgp.mit.edu which has very poor uptime. You are free to use whatever keyserver you see fit, but it makes sense to pick one that works at least 99% of the time.
Jan 27 2019
Yes, 0.19.0 will probably come after this release since the hardfork upgrade code cutoff is after when 0.18.8 would release.
Jan 26 2019
Jan 25 2019
Jan 24 2019
Fixed note regarding bitcoin-qt fix
Rebase + fixed comment
Fix version comment
nvm I see this diff actually has a dependency on D2336
Looks like same build failure as before. Not sure why this change would re-introduce it though.
I checked again and I see the radio button on master.