selsta opened pull request #11298: wallet2: handle non-curve tx public keys in reserve proofs [release-v0...

> monero-project/monero #11298

j-berman opened pull request #11306: cryptonote_basic: parse_and_validate_tx param to check max size [v0.18...

> monero-project/monero #11306

j-berman opened pull request #11305: p2p: don't reset timeout timer for handshakes [v0.18]

> monero-project/monero #11305

j-berman opened pull request #11304: tx_pool: do expensive verify after potential no-drop offenses [v0.18]

> monero-project/monero #11304

j-berman opened pull request #11303: blockchain: limit offsets cache size [v0.18]

> monero-project/monero #11303

j-berman opened pull request #11302: cryptonote_basic: serialization checks [v0.18]

> monero-project/monero #11302

j-berman opened pull request #11301: cryptonote_core: rm unnecessary db reads before block relay [v0.18]

> monero-project/monero #11301

j-berman opened pull request #11300: blockchain: if block is known invalid, fail block verification [v0.18]

> monero-project/monero #11300

j-berman opened pull request #11299: p2p: update peer's height on new block & widen window for relay [v0.18...

> monero-project/monero #11299

jpk68 opened pull request #11307: blockchain_db: remove redundant comments

> monero-project/monero #11307

Ap4sh opened pull request #11308: net: accept SOCKS5 domain reply addresses

> monero-project/monero #11308

PyXMR2025 opened pull request #11309: rpc: support http login with auth config

> monero-project/monero #11309

<pyxmr2025:mozilla.org> Constructor to be added later in http_auth.h; ignore CI build errors.

<ofrnxmr> @pyxmr2025:mozilla.org please dont spam commits to your pr branch

<ofrnxmr> Finish your work before pushing

<pyxmr2025:mozilla.org> My bad. Sorry

<ofrnxmr> It runs a new ci job every time you push. Also, once finished, squash into a single commit

<ofrnxmr> Donr use "git push" as a save button

<pyxmr2025:mozilla.org> Won’t do that anymore. 😅

<thomasbuilds:matrix.org> @ofrnxmr: Are those ci jobs free $ to run btw? They should be but since there are so many idk

<ofrnxmr:xmr.mx> depends on the project

<ofrnxmr:xmr.mx> on github, "yes" but nothing is free, and spamming potentially hours of ci runs can get you banned

<ofrnxmr:xmr.mx> luckily the builds all failed, so the ci only ran for a couple seconds or minutes, instead of the full hour+ test suite on every commit

<ofrnxmr:xmr.mx> also runs twice. once on your own repo, and again on monero-project. so if your tests arent even passing, its best to just push to your own repo (if you arent running the tests locally)

<thomasbuilds:matrix.org> It didn't run twice before

<ofrnxmr:xmr.mx> abusing something that is provided for free, is a fast path to being charged for it

<ofrnxmr:xmr.mx> @thomasbuilds:matrix.org: "always" had

<ofrnxmr:xmr.mx> has*

<ofrnxmr:xmr.mx> your personal repo runs the ci as well

<thomasbuilds:matrix.org> Really u sure, few months ago my monero fork didn't run ci

<thomasbuilds:matrix.org> ?

<ofrnxmr:xmr.mx> im 100% sure

<ofrnxmr:xmr.mx> github.com/monero-project/monero/actions

<ofrnxmr:xmr.mx> whoops

<ofrnxmr:xmr.mx> github.com/jpk68/monero/actions

<ofrnxmr:xmr.mx> github.com/thomasbuilds/monero/actions

<thomasbuilds:matrix.org> Yep u see?

<ofrnxmr:xmr.mx> see what

<thomasbuilds:matrix.org> My first workflow run on my fork was 21 august

<thomasbuilds:matrix.org> I had commits before that

<ofrnxmr:xmr.mx> github.com/jpk68/monero/actions?page=18

<ofrnxmr:xmr.mx> github.com/selsta/monero/actions?page=51

<ofrnxmr:xmr.mx> not sure why yours wasnt running, but theyve been running automatically for as long as im aware

<thomasbuilds:matrix.org> I guarantee I didn't delete my fork because of that PR db_lmdb: fix uninit read in...

<ofrnxmr:xmr.mx> im not saying you did. maybe you had some different settings or smthn, or a stale master branch

<thomasbuilds:matrix.org> Weird yeah

<thomasbuilds:matrix.org> surely jpk68 used pushed commits in his fork before Jul 24

<thomasbuilds:matrix.org> Mr Claude:

<thomasbuilds:matrix.org> > The reason is that GitHub disables inherited workflows on forks by default. Workflows in forked repositories are turned off until you go to the Actions tab and click "I understand my workflows, go ahead and enable them." The banner reads: because the repository contained workflow files when it was forked, they've been disabl [... too long, see mrelay.p2pool.observer/e/8Ync9qkLWXlyY05r ]

<thomasbuilds:matrix.org> I don't recall having done any of that

<thomasbuilds:matrix.org> just 1 day it started running ci on my fork

<thomasbuilds:matrix.org> maybe I had lol

<thomasbuilds:matrix.org> drahtbot for monero? github.com/maflcko/DrahtBot

<thomasbuilds:matrix.org> I guess it hasn't been implemented because monero is less crowded than bitcoin, but what you think?

<ofrnxmr:xmr.mx> i liked that thing

<thomasbuilds:matrix.org> yeah lol me too

<jpk68:matrix.org> Am I being investigated? > <@ofrnxmr:xmr.mx> github.com/jpk68/monero/actions?page=18

<ofrnxmr:xmr.mx> hm?

<jpk68:matrix.org> Bad joke, nevermind

<ofrnxmr:xmr.mx> Ah i see. No sense of humor

<ofrnxmr:xmr.mx> (me)

<jpk68:matrix.org> github.com/monero-project/monero/bl…lockchain_db/blockchain_db.cpp#L459

<jpk68:matrix.org> ^ Same for stagenet, I assume?

.merges

10361 10886 10887 10964 11024 11237 11238 11239 11245 11246 11248 11250 11251 11255 11257 11258 11287

jpk68 opened pull request #11310: db_lmdb: avoid uninitialized read

> monero-project/monero #11310

Hello, question is it possible to coordinate a transaction with 2 utxo's from 2 users in xmr?

I am looking for a way to fund a multisig wallet by 2 parties, in a way either both fund the wallet or none.

Ap4sh opened pull request #11311: common: exit child when execve fails

> monero-project/monero #11311