11:55:19 .merges 11:55:19 -xmr-pr- 9938 9984 9989 9990 9992 9993 9995 10000 10001 10002 10014 10015 12:01:09 .merges 12:01:09 -xmr-pr- 10000 12:02:24 done 22:58:25 @binaryfate would you be able to review this PR to provide fixes for the oss-fuz integration? Plowsof was the first reviewer but two are required 22:58:27 https://github.com/google/oss-fuzz/pull/13691 22:58:52 Asking binaryfate is crazywork :D 22:59:43 I'd leave that invitation more "open" 23:01:03 Anyone is welcome and encouraged to review but the github bot said “The PR must be approved by known contributors before it can be merged. The past contributors are: plowsof, maflcko, inferno-chromium, binaryFate” 23:01:09 That pr is still marked as a draft 23:02:39 i saw that, but does that mean known contributors to oss-fuzz? I think it would imply known contributors, including trusted members upstream 23:05:32 Anyway, comments from me: 1. is the ci supposed to be green? 2. i dont like the merge commit 3. Its marked as draft 23:07:11 [@xmrack:monero.social](https://matrix.to/#/@xmrack:monero.social) 23:07:13 https://github.com/google/oss-fuzz/pull/12936 23:07:15 you can see here that selsta and myself approved plowsof's contribution 23:07:58 (you commented there as well). This just to say that the bot's recommendations arent concrete 23:10:19 I believe CI fails since pr #10004 hasnt been pushed to master 23:11:00 *merged 23:11:38 That might be the same reason it's in draft (waiting for 10004?) 23:12:05 Yea 23:15:28 From that PR it looks like any monero contributor can approve. So I extend the invitation to everyone here :D 23:20:45 Are the adalogics guys going to maintain this long term? I see they were added to the `auto cc` contacts alongside the fluffy, binary, luigi, and mooo. 23:24:08 Their emails would only be temporary so they can thoroughly debug the new harnesses over the next few weeks 23:25:24 I’ll paste my comment advocating for their addition a few MRL meetings ago: 23:25:25 The benefit of adding david from adalogics (temporarily) to the email list of OSS-Fuzz is that his team will be able to more effectively troubleshoot the harnesses as they can potentially hit edge cases and need to be updated. Monero’s OSS-Fuzz integration has been neglected for a while now and having david (the #1 contributor to the OSS-Fuzz project) making sure everything is r 23:25:27 unning smoothly would IMHO be a great asset to the monero community. 23:30:54 tobtoht should the dependencies be cleaned up here (in dockerfile) 23:37:54 xmrack https://github.com/monero-project/monero/pull/9989