💬 instagibbs commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626448996)
seems ever so slightly more direct, even though this seems correct as is
```Suggestion
if (&other == this) return *this;
```
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626448996)
seems ever so slightly more direct, even though this seems correct as is
```Suggestion
if (&other == this) return *this;
```
💬 theuni commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#issuecomment-2148290427)
> `if (this == &other) return *this;`
Huh, that worked. But this (the one I tried) doesn't
```c++
if (*this == other) return *this;
```
(https://github.com/bitcoin/bitcoin/pull/30161#issuecomment-2148290427)
> `if (this == &other) return *this;`
Huh, that worked. But this (the one I tried) doesn't
```c++
if (*this == other) return *this;
```
💬 theuni commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#issuecomment-2148299043)
Oh, duh, that's a totally different comparison. Ofc that didn't do what I wanted :)
(https://github.com/bitcoin/bitcoin/pull/30161#issuecomment-2148299043)
Oh, duh, that's a totally different comparison. Ofc that didn't do what I wanted :)
💬 maflcko commented on pull request "test: Set mocktime in p2p_disconnect_ban.py to avoid intermittent test failure":
(https://github.com/bitcoin/bitcoin/pull/30174#discussion_r1626530422)
Yeah, I think it shouldn't matter here. An alternative would be to increase the magic number `120` sufficiently (maybe by a factor of 10 or so).
(https://github.com/bitcoin/bitcoin/pull/30174#discussion_r1626530422)
Yeah, I think it shouldn't matter here. An alternative would be to increase the magic number `120` sufficiently (maybe by a factor of 10 or so).
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626544077)
Indeed!
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626544077)
Indeed!
💬 willcl-ark commented on pull request "ci: add markdown link check job":
(https://github.com/bitcoin/bitcoin/pull/30034#issuecomment-2148338315)
I think an upstream PR may be the best approach here, So I opened https://github.com/becheran/mlc/pull/89
(https://github.com/bitcoin/bitcoin/pull/30034#issuecomment-2148338315)
I think an upstream PR may be the best approach here, So I opened https://github.com/becheran/mlc/pull/89
💬 maflcko commented on pull request "ci: add markdown link check job":
(https://github.com/bitcoin/bitcoin/pull/30034#issuecomment-2148351046)
Not sure if globbing is the right fix. Conceptually, no folder or file should be scanned that is not tracked in git.
Though, I wonder if there is an easy way to ask git to print all files/folders that are "dirty", ignoring the gitignore. An alternative may be to teach mlc to read understand the gitignore files. However, that will also be incomplete, because devs may add random other folders themselves.
So for now the only solution would be to call `mlc` in a loop over `git ls-files -- '*.m
...
(https://github.com/bitcoin/bitcoin/pull/30034#issuecomment-2148351046)
Not sure if globbing is the right fix. Conceptually, no folder or file should be scanned that is not tracked in git.
Though, I wonder if there is an easy way to ask git to print all files/folders that are "dirty", ignoring the gitignore. An alternative may be to teach mlc to read understand the gitignore files. However, that will also be incomplete, because devs may add random other folders themselves.
So for now the only solution would be to call `mlc` in a loop over `git ls-files -- '*.m
...
💬 maflcko commented on pull request "test: Set mocktime in p2p_disconnect_ban.py to avoid intermittent test failure":
(https://github.com/bitcoin/bitcoin/pull/30174#issuecomment-2148366625)
> nit: If another push happens, these look like typos:
Thanks, fixed.
> Did you run into this specific failure scenario, or simply being proactive?
It happened once with valgrind, which sometimes takes some time to load. You can test with:
```diff
diff --git a/test/functional/p2p_disconnect_ban.py b/test/functional/p2p_disconnect_ban.py
index 72a42a658e..aa4ae7ea27 100755
--- a/test/functional/p2p_disconnect_ban.py
+++ b/test/functional/p2p_disconnect_ban.py
@@ -103,6 +103,7 @@
...
(https://github.com/bitcoin/bitcoin/pull/30174#issuecomment-2148366625)
> nit: If another push happens, these look like typos:
Thanks, fixed.
> Did you run into this specific failure scenario, or simply being proactive?
It happened once with valgrind, which sometimes takes some time to load. You can test with:
```diff
diff --git a/test/functional/p2p_disconnect_ban.py b/test/functional/p2p_disconnect_ban.py
index 72a42a658e..aa4ae7ea27 100755
--- a/test/functional/p2p_disconnect_ban.py
+++ b/test/functional/p2p_disconnect_ban.py
@@ -103,6 +103,7 @@
...
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626579091)
Done.
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626579091)
Done.
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626579194)
Done.
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626579194)
Done.
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626579310)
Done.
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626579310)
Done.
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626580105)
I didn't take this suggestion. The current should be invoking `compare_fn` whenever an element is destructed or destructively overwritten; that's not necessarily number `idx` though.
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626580105)
I didn't take this suggestion. The current should be invoking `compare_fn` whenever an element is destructed or destructively overwritten; that's not necessarily number `idx` though.
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626580268)
Done.
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626580268)
Done.
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626580385)
Done.
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626580385)
Done.
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626581320)
Added an `Assume` to reflect this.
(https://github.com/bitcoin/bitcoin/pull/30161#discussion_r1626581320)
Added an `Assume` to reflect this.
✅ laanwj closed a pull request: "depends: Remove Qt build-time dependencies"
(https://github.com/bitcoin/bitcoin/pull/29923)
(https://github.com/bitcoin/bitcoin/pull/29923)
💬 achow101 commented on pull request "wallet: Ensure best block matches wallet scan state":
(https://github.com/bitcoin/bitcoin/pull/30221#issuecomment-2148413538)
> You might not want to write to the wallet database each time a block is connected if the block doesn't contain any relevant transactions
I think you would since not writing it would result in possibly rescanning that block at the next loading which takes a little bit of time, regardless of whether any relevant transactions are in the block.
> especially during reindexing.
Perhaps an easy solution to this is to just write the best block every 1000 blocks (or some other interval) when w
...
(https://github.com/bitcoin/bitcoin/pull/30221#issuecomment-2148413538)
> You might not want to write to the wallet database each time a block is connected if the block doesn't contain any relevant transactions
I think you would since not writing it would result in possibly rescanning that block at the next loading which takes a little bit of time, regardless of whether any relevant transactions are in the block.
> especially during reindexing.
Perhaps an easy solution to this is to just write the best block every 1000 blocks (or some other interval) when w
...
💬 sipa commented on pull request "util: add VecDeque":
(https://github.com/bitcoin/bitcoin/pull/30161#issuecomment-2148476988)
Added a few missing `compare_fn` calls, and also added branches to the fuzz test to exercise `pop_front()` and `pop_back()`, which were apparently missing.
(https://github.com/bitcoin/bitcoin/pull/30161#issuecomment-2148476988)
Added a few missing `compare_fn` calls, and also added branches to the fuzz test to exercise `pop_front()` and `pop_back()`, which were apparently missing.
💬 willcl-ark commented on pull request "ci: add markdown link check job":
(https://github.com/bitcoin/bitcoin/pull/30034#issuecomment-2148477466)
> Not sure if globbing is the right fix. Conceptually, no folder or file should be scanned that is not tracked in git.
>
> Though, I wonder if there is an easy way to ask git to print all files/folders that are "dirty", ignoring the gitignore. An alternative may be to teach mlc to read understand the gitignore files. However, that will also be incomplete, because devs may add random other folders themselves.
>
> So for now the only solution would be to call `mlc` in a loop over `git ls-fil
...
(https://github.com/bitcoin/bitcoin/pull/30034#issuecomment-2148477466)
> Not sure if globbing is the right fix. Conceptually, no folder or file should be scanned that is not tracked in git.
>
> Though, I wonder if there is an easy way to ask git to print all files/folders that are "dirty", ignoring the gitignore. An alternative may be to teach mlc to read understand the gitignore files. However, that will also be incomplete, because devs may add random other folders themselves.
>
> So for now the only solution would be to call `mlc` in a loop over `git ls-fil
...
💬 achow101 commented on pull request "chainparams: Add achow101 DNS seeder":
(https://github.com/bitcoin/bitcoin/pull/30007#issuecomment-2148506279)
Anything left to do here?
***
> Are you sure you want to put this on a common domain with other things?
I don't think this will be an issue.
(https://github.com/bitcoin/bitcoin/pull/30007#issuecomment-2148506279)
Anything left to do here?
***
> Are you sure you want to put this on a common domain with other things?
I don't think this will be an issue.