17:03:29
boog900:monero.social:
meeting here in 1 hour
17:03:48
syntheticbird:monero.social:
ok
17:59:46
boog900:monero.social:
!meeting
17:59:48
moo:monero.social:
Starting meeting: https://github.com/monero-project/meta/issues/1309
17:59:50
boog900:monero.social:
1) greetings
18:00:19
syntheticbird:monero.social:
Goodbye
18:00:25
syntheticbird:monero.social:
Good morning
18:01:28
hinto:monero.social:
hello
18:01:38
boog900:monero.social:
2) updates
18:02:37
boog900:monero.social:
Me: I spent some time investigating an issue with wallet sync, turns out axum drops connections after responding if you don't read the whole request.
18:03:27
boog900:monero.social:
Wallet syncing is otherwise going good, ran into another issue today that looks to be on the cli side but it seems to be rare.
18:04:54
syntheticbird:monero.social:
if it doesn't read the whole request? You mean client reading response, or server reading request
18:05:37
boog900:monero.social:
server handling request. If we don't decode the JSON for example, axum will respond but after responding will drop the connection.
18:05:59
hinto:monero.social:
me: started attempting Guix and StageX on more complicated repos including `Cuprate/cuprate` and stopped at dep compile issues, moved onto working on ZMQ related code for PoWER
18:07:01
syntheticbird:monero.social:
Why would we not decode the JSON
18:07:24
syntheticbird:monero.social:
what's a situation where we wouldn't process the request and still respond somehow
18:07:26
boog900:monero.social:
becuase on one request we didn't need it.
18:08:40
boog900:monero.social:
the request was the txpool hashes "bin" request, so we didn't need any of the pay for RPC data which is the only data in the request so I just didn't read it.
18:09:30
boog900:monero.social:
which then meant we would respond to the txpool hashes bin request fine but then disconnect after, which was hard to debug as to me all requests were fine.
18:09:45
boog900:monero.social:
3) Project: What is next for Cuprate?
18:13:11
hinto:monero.social:
RPC payments may stay with us forever, it's unused and clutters code yet it's too harmless to get consensus/review to remove
18:14:08
hinto:monero.social:
1 thing to add onto the bucket list of the fabled monerod RPC/P2P rewrite
18:14:16
syntheticbird:monero.social:
wait until 50%+ of nodes are cuprate, you'll see how quick the consensus on removing it will be
18:14:29
boog900:monero.social:
Cuprate doesn't support it
18:14:36
syntheticbird:monero.social:
i know and it's good
18:14:40
boog900:monero.social:
it just has the fields in its types
18:14:44
syntheticbird:monero.social:
but it could be removed from the specs altogether
18:22:37
boog900:monero.social:
Anything else anyone wants to discuss today?
18:24:12
boog900:monero.social:
We can end here, thanks everyone!
18:24:14
syntheticbird:monero.social:
I just bought a chessboard
18:24:39
boog900:monero.social:
!meeting
18:24:45
moo:monero.social:
- Logs: https://github.com/monero-project/meta/issues/1309#issuecomment-3661848868
18:24:46
moo:monero.social:
- Next meeting: https://github.com/monero-project/meta/issues/1312
18:39:23
ohchase:envs.net:
https://www.reddit.com/r/rust/comments/1pnz1iz/comment/nubzhpc/ not sure if you're aware but just checked and see there is bincode reference in cuprate, please be aware there is concerns around them deleting git history
18:43:41
boog900:monero.social:
Hmm, we don't use it directly but its pulled in through heed. We might be able to remove some feature flags to get rid of it
18:45:55
ohchase:envs.net:
I don't see any objective or proven intent of malice but I know supply chain attacks are rampant, so figured yall would be the ones to know and might be worth investigating
18:49:54
boog900:monero.social:
arti also pulls it in
18:50:18
boog900:monero.social:
yeah it should be ok, with the .lock it wont update by itself
18:50:44
ohchase:envs.net:
there seems to be some drama around the whole situation so might just be nerdle fighting