< MarcoFalke>
mryandao: Missing white space between "in" and "BTC", no?
< * MarcoFalke>
zzz
< mryandao>
MarcoFalke: ok added the space :/
< jonasschnelli>
roasbeef: that is what I'm doing.. but it still complains after 1.3GB that the map is full
< bitcoin-git>
[bitcoin] laanwj closed pull request #13113: tests: Make it clear that MAX_INV_SZ is not covered by functional tests (master...add-note-about-MAX_INV_SZ) https://github.com/bitcoin/bitcoin/pull/13113
< wumpus>
jonasschnelli: I found it strange too, but it's what e.g. monero is doing
< wumpus>
jonasschnelli: I think they double the map size every time that is needed
< jonasschnelli>
wumpus: okay... funny... also, I can't find any hint in the documentation... it looks like it should be possible to initialize a 4GB map size and fill it up.
< jonasschnelli>
wumpus: do you know how monero deals with the 4GB 32bit limitation?
< wumpus>
jonasschnelli: probably better to take it #monero-dev, but IIRC monero doesn't run on 32-bit
< jonasschnelli>
thanks
< fanquake>
wumpus #13119 & #13109 probably ready to go in
< mryandao>
promag: just to be sure what i'm looking at here -- is it just the "descendent" in the release-notes that needs fixing?
< promag>
mryandao: right
< bitcoin-git>
[bitcoin] mryandao opened pull request #13124: [doc] nit: descendent should be spelled descendant even in the release-notes (master...fix-getrawmempool-fee-representation) https://github.com/bitcoin/bitcoin/pull/13124
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13125: scheduler: Add Clang thread safety annotations for variables guarded by m_cs_callbacks_pending (master...m_cs_callbacks_pending) https://github.com/bitcoin/bitcoin/pull/13125
< fanquake>
#13124 can go in now too, and that'll be the end of "descendent".
< gribble>
https://github.com/bitcoin/bitcoin/issues/13124 | [doc] nit: descendent should be spelled descendant even in the release-notes by mryandao · Pull Request #13124 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13126: util: Add Clang thread safety annotations for variables guarded by cs_args (master...guarded-by-cs_args) https://github.com/bitcoin/bitcoin/pull/13126
< wumpus>
lol couldn't that be done in one PR
< fanquake>
wumpus unfortunately I forgot to search after looking at the last one..
< bitcoin-git>
bitcoin/master 9b78ef3 mryandao: nit: descendent should be spelled descendant even in the release-notes
< bitcoin-git>
bitcoin/master 19fadd9 Wladimir J. van der Laan: Merge #13124: [doc] nit: descendent should be spelled descendant even in the release-notes...
< bitcoin-git>
[bitcoin] laanwj closed pull request #13124: [doc] nit: descendent should be spelled descendant even in the release-notes (master...fix-getrawmempool-fee-representation) https://github.com/bitcoin/bitcoin/pull/13124
< fanquake>
The GH UI lags a fair way behind a merge being announced here by the git bot
< wumpus>
yes, I've also noticed, can be quite long before the UI notices
< wumpus>
all the requests on their server must be like stampeding unicorns
< fanquake>
hehe
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13127: wallet: Add Clang thread safety annotations for variables guarded by cs_db (master...guarded-by-cs_db) https://github.com/bitcoin/bitcoin/pull/13127
< wumpus>
we should probably poke practicalswift to group these things, not create a zillion PRs in a day
< promag>
afaiu he is splitting?
< fanquake>
wumpus I thought there was already one large PR that grouped all these together, and they were now being split up.
< fanquake>
Although I agree, a couple PRs a day is probably enough.
< wumpus>
ok...
< promag>
imo he should go easy
< promag>
wait for a merge and submit a new one
< promag>
otherwise it's overwhelming
< wumpus>
right, it feels a bit like a swarm attack on reviewers
< wumpus>
and I know he doesn't mean it that way...
< promag>
honestly atm I try to avoid those PR
< wumpus>
we should review BlueMatt's PRs more
< promag>
you mean #12979?
< gribble>
https://github.com/bitcoin/bitcoin/issues/12979 | Split validationinterface into paralell validation/mempool interfaces by TheBlueMatt · Pull Request #12979 · bitcoin/bitcoin · GitHub
< provoostenator>
"Makefile:5697: recipe for target 'libbitcoin_server_a-init.o' failed" on Ubuntu 16.04 on VM with 2 GB RAM, 30% of which used up by some other process.
< provoostenator>
Killing said process makes the problem go away. But it seems we're quite close to the limit of the minimum recommended system RAM (2 GB) for that file.
< provoostenator>
(the other process being sipa's DNS seeder FYI :-)
< wumpus>
which compiler/version?
< wumpus>
FWIW in the issue about compiler memory usage (#6658) there are some cflags that can be used to tone down memory usage for at least gcc..