06:52:07 .merge+ 9642 06:52:07 Added 11:52:24 .merge+ 9715 9711 9706 9701 11:52:24 Added 16:09:57 a churn script was posted on reddit, not sure if it's fit for purpose, but noticed it mentions that it deleted p2pstate.bin because there is a "node id" in there that persists between privacynetworks/clearnet , is this still the case? https://github.com/antichainalysis/xmr-churner/issues/1 17:12:46 plowsof: the citation predates tor / i2p integration into monero, I don't think this is relevant for `--tx-proxy` 17:14:09 since we will put out a release soon it would be nice if some node operators could test the current release-v0.18 branch on their nodes 17:41:35 selsta: i have a node, ping me. i run upstream via tor, ok 17:48:39 that was the ping 17:49:51 and thank you tankf33der :) 17:51:52 plowsof: How can I help you with this? What can I do to assist? 17:54:12 this is the branch we can compile https://github.com/monero-project/monero/tree/release-v0.18 17:55:57 ok, and ? 17:58:19 after compiling, simply run your node (monerod) as usual. some easy things to test, does it gain + maintain peers.. can it create / broadcast transactions. are there any errors in the log files.. 18:01:30 ok. next. 18:02:00 ok. next? 18:03:58 when switch to tor ? 18:13:56 shall we take this to our support room? one of our agents can assist with any step by step questions #monero-support 19:20:39 https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/ 19:20:55 Jan 30 v3 uploads wont work anymore 19:21:15 "Starting January 30th, 2025, GitHub Actions customers will no longer be able to use v3 of actions/upload-artifact or actions/download-artifact. Customers should update workflows to begin using v4 of the artifact actions as soon as possible. While v4 of the artifact actions improves upload and download speeds by up to 98% and includes several new 19:21:15 features, there are key differences from previous versions that may require updates to your workflows. Please see the documentation in the project repositories for guidance on how to migrate your workflows." 19:22:40 List of breaking changes https://github.com/actions/upload-artifact?tab=readme-ov-file#breaking-changes 20:46:58 Maybe the warning is just a notice? Looks like the workflow is already on v4 21:24:35 last time I switched from v3 to v4 while testing forgejo actions, it didn't worked, had super weird bug with zero logs, no reported issue. I hope it works nowadays 23:06:47 What is the estimated release date for the new release?