00:41:54 .merges 00:41:54 Merge queue empty 00:45:38 hmm I remember adding things to it but I can’t find it in the logs... 00:49:09 .merge+ 6947 6956 6977 6989 7003 00:49:09 Added 00:49:34 vtnerd: please rebase 7009 (not urgent) 01:49:08 luigi1111w: sorry, there is a typo here: https://github.com/monero-project/monero/releases/tag/v0.17.1.6 01:49:15 replace with the following sentence 01:49:38 if you’re using the --rpc-restricted-bind-port option along with --rpc-bind-ip currently you will need to add the new --rpc-restricted-bind-ip arg or else the daemon will bind restricted RPC only to localhost. 01:52:33 Sorry 😢 01:52:39 Got the syntax mixed up 01:52:47 np 03:10:43 TheCharlatan: https://github.com/monero-project/monero/pull/7103 03:15:20 -xmr-pr- selsta opened pull request #7104: workflows: shorten name 03:15:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7104 03:15:20 -xmr-pr- selsta opened pull request #7103: workflows: add depends workflow, upload binaries 03:15:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7103 03:51:13 Please what causes The I2P OUT connections all disconnected in a matter of minutes? 03:53:53 i am using i2p java(not zero) 03:54:59 do you have --anonymous-inbound? 03:55:35 It is possible that we have too aggressive timeouts for I2P, Tor seems to work a bit better 04:00:03 yes i have. but no INC , I think it's because NAT? 04:41:40 [P2P2] ERROR net contrib/epee/include/net/abstract_tcp_server2.inl:1576 [sock 173] Failed to start connection, connections_count = 795 04:42:01 is this likely due to some file limit or something variable in the system? 04:45:20 -xmr-pr- selsta opened pull request #7105: travis: remove from repo 04:45:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7105 08:23:59 Latest version without blocklist +2 issue is still to me 08:40:45 cvg8 check your log and see if it's blocking any nodes. It might take a while until it blocks all malicious nodes one by one. 08:50:26 ok 51.79.58.90 , 51.68.209.38 it's gone takes a few minutes 08:51:49 yes, they're both in the block list 08:52:01 I would still keep using https://gui.xmr.pm/files/block.txt 08:52:21 ok ,thanks 08:52:22 They are known malicious nodes, better to block them right away 09:06:26 sech1, what can do a bad node? 09:07:38 a lot of things, from spying on transactions to disrupting the network 09:07:58 https://www.reddit.com/r/Monero/comments/k9d0hu/a_brief_breakdown_of_moneros_ongoing_network/ 09:10:41 ragn4: it can NOT put your funds at risk (but might stop you from spending them), it can not reveal the destination address, or the amount. 09:10:41 then those nodes are from the nsa? 09:12:05 or just the bytecoin devs jaja 12:29:36 can anyone point me at a simple monero task I can do to get started? 12:30:21 a beginner friendly bug 12:30:55 or feature enhancement. I know c++, java, js well 12:31:16 https://github.com/monero-project/monero/issues/7012 maybe 12:35:24 moneromooo: thank you. I will explore it. btw could I get paid by doing something like that? 12:35:52 Unlikely. 12:36:26 For some larger body of work though, there's a CCS (ccs.getmonero.org) which can provide funding, 12:38:56 :( 12:41:55 I doubt I have that much time. I just wanted to pitch in when I had some time. 13:56:12 The CLI can transact with the +2 blockheight problem. Feather wallet can also do it. But the GUI wallet cannot. I thought that was an oversight that was going to be fixed in *.1.6 but apparently not? Is there a reason to keep the GUI this way? 14:29:51 "Is there a reason to keep the GUI this way?" -> is the daemon issue, should be fixed on the monerod side 14:30:45 Lyza: I submitted a patch, it did not make it in 14:34:37 xiphon I mean I don't disagree that it should be fixed in the daemon as well but what's the reasoning for the CLI and GUI to behave differently here? I don't get it. 14:35:03 tobtoht_ do you have a link? 14:36:37 Lyza: https://github.com/monero-project/monero/pull/7066 14:38:24 thanks 14:39:20 Ig I sort of get it but consistent behavior between official wallets does still seem desirable *shrug* 14:39:52 both CLI and GUI use the same libwallet codebase 14:40:07 CLI uses wallet2 directly 14:40:52 so? the other is just a wrapper around wallet2 14:41:07 the issue is inside the wrapper 14:41:26 ugh. then the wrapper is not just a wrapper any more, and that was a mistake. 14:42:39 all of this should start over and both CLI and GUI should just be frontends to wallet-rpc 14:43:35 having diverging code in the official source tree like this is ... sloppy 14:44:32 hyc: would be feasible once wallet-rpc opens its interface _before_ it starts the wallet refresh 14:47:46 now you have to wait an indefinite amount of time before you can any information from the wallet 14:50:47 sounds like that should be fixable 14:54:35 .merge+ 7106 7107 14:54:36 Added 14:59:32 .merge+ 7009 14:59:32 Added 15:27:39 Prove that you really have the most critical thinking community. Come to https://t.me/get_monero and let's discuss things like adults. 15:54:15 2020-12-10 15:53:19.937 [RPC0] ERROR net.http contrib/epee/include/net/http_protocol_handler.inl:318 [IP:port INC] simple_http_connection_handler::handle_char_out: Error state!!! 15:54:45 im seriously thinking of just grepping my logs for ERROR, then extracting the IP and then blocking via firewall 15:55:35 i think IP is always bracketed like [IP:port IN/OUT] right? should make for easy cut parsing 15:56:20 Yes. 16:00:20 -xmr-pr- moneromooo-monero opened pull request #7109: protocol: fix switchting to adding blocks if noone's adding the next … 16:00:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7109 16:00:21 -xmr-pr- moneromooo-monero opened pull request #7108: protocol: fix switchting to adding blocks if noone's adding the next … 16:00:21 -xmr-pr- > https://github.com/monero-project/monero/pull/7108 16:18:25 huh. this error state shows up when i legitimately try to connect to a remote node from the GUI 16:19:38 aaand now the gui won't close :( 16:21:53 it should close if you wait long enough, it tries to exit cleanly, else just force quit it 16:25:01 [RPC1] ERROR net.http contrib/epee/include/net/http_protocol_handler.inl:387 [IP:PORT INC] simple_http_connection_handler::handle_invoke_query_line(): Failed to match first line: 16:25:12 yeah, so thats from a legitimate attempt from my GUI to access the node 16:25:37 ah well, there goes that idea 16:51:39 gingeropolous: https://github.com/monero-project/monero/pull/7081 might be interesting for you 17:00:20 -xmr-pr- moneromooo-monero opened pull request #7110: protocol: drop origin IP if a block fails to verify in sync mode 17:00:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7110 17:15:20 -xmr-pr- moneromooo-monero opened pull request #7112: rpc: report target height as 0 when synced 17:15:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7112 17:15:21 -xmr-pr- moneromooo-monero opened pull request #7111: protocol: drop origin IP if a block fails to verify in sync mode 17:15:21 -xmr-pr- > https://github.com/monero-project/monero/pull/7111 17:28:26 ? 17:40:17 fluffypony: do you know about https://github.com/monero-project/monero/issues/7077 for sure ? 17:43:57 yes it's the root 17:44:24 https://dnssec-analyzer.verisignlabs.com/checkpoints.moneropulse.net 17:44:34 you can see the query order there 17:45:03 ty 18:00:20 -xmr-pr- moneromooo-monero opened pull request #7113: simplewallet: don't complain about connecting to the daemon when offli... 18:00:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7113 18:30:20 -xmr-pr- moneromooo-monero opened pull request #7114: protocol: fix asking for pruned blocks for v10 18:30:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7114 19:15:20 -xmr-pr- moneromooo-monero opened pull request #7115: cmake: fix "release" version string on tagged releases 19:15:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7115 20:15:20 -xmr-pr- moneromooo-monero opened pull request #7118: protocol: add a sanity check to the number of block hashes sent 20:15:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7118 20:15:21 -xmr-pr- moneromooo-monero opened pull request #7117: protocol: add a sanity check to the number of block hashes sent 20:15:21 -xmr-pr- > https://github.com/monero-project/monero/pull/7117 20:20:06 .merge+ 7116 7115 7102 7106 7107 7108 7109 7110 7111 7104 7104 7100 7101 7117 7118 20:20:15 that’s a lot of PRs... 20:20:38 7106 7108 7110 would benefit from a second look 20:35:02 .merge+ 7105 7103 20:35:02 Added 21:00:20 -xmr-pr- moneromooo-monero opened pull request #7119: protocol: add calls to reserve where appropriate 21:00:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7119 21:41:49 luigi1111w: please merge 7108 7109 early so that we can avoid merge conflict 21:50:06 done 21:50:44 thx 21:51:03 moneromooo: please rebase 7110 7111 22:00:16 done 22:22:02 .merges 22:22:02 -xmr-pr- 6947 6956 6977 6989 7003 7009 7100 7101 7102 7103 7104 7105 7106 7107 7110 7111 7115 7116 7117 7118 22:24:44 .merge- 6989 22:24:44 Removed 22:37:15 So — the +2 height issue is completely disabling all BTCPayServer Monero users ATM, it appears 22:37:53 Anyone running that is getting fed the false block-height and unable to sync because of it. 22:37:53 Is there any other fix except the ban-list? Apparently they use a custom Docker Monero image that doesn’t allow easily adding in the ban-list. 22:38:17 I’ve had two separate merchants reach out to me on Twitter about this, as we were hoping v0.17.1.6 would resolve this in some way. 22:38:22 hmm, both CLI and RPC should not have issues 22:38:35 but I don’t know what BTCPayServer does exactly 22:38:41 Yeah me either TBH 22:38:55 It must use the same wrapper as the GUI if it’s still having the issue on v0.17.1.6 23:00:20 -xmr-pr- moneromooo-monero opened pull request #7120: protocol: fix asking for pruned blocks for v10 23:00:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7120 23:14:14 .merge+ 7114 7120 7121 7122 23:14:15 Added 23:15:20 -xmr-pr- moneromooo-monero opened pull request #7122: protocol: one more sanity check on usable data from a peer 23:15:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7122 23:15:21 -xmr-pr- moneromooo-monero opened pull request #7121: protocol: one more sanity check on usable data from a peer 23:15:21 -xmr-pr- > https://github.com/monero-project/monero/pull/7121 23:31:03 .merges 23:31:03 -xmr-pr- 6947 6956 6977 7003 7009 7100 7101 7102 7103 7104 7105 7106 7107 7110 7111 7114 7115 7116 7117 7118 7120 7121 7122 23:31:41 luigi1111w: not sure how available you are, but it would be great if you could merge these and tag v0.17.1.7 23:31:59 if you have less time I can write you the release-v0.17 PRs list specifically