Is there something wrong with my Monero repository on GitHub if the "test-ubunto" runner gives the following error after getting triggered because of a forced update I made today:

rbrunner: github.com/monero-project/monero/ru…s/5602390152?check_suite_focus=true tests run fine here

it's because you force pushed, it couldn't check out the commit

Thanks selsta. So all ok if the tests run on the main repository then? This looks quite fragile if already an update / force push can throw tests off on my own repository ...

Ah, I have a suspicion now. I forced-pushed twice with only 5 minutes in-between because I noticed an error. Maybe that was simply too fast for GitHub runners.

rbrunner: once you force push a new CI job starts to run anyway, so the old one failing is irrelevant

Are there any resources available for the Levin protocol besides LEVIN_PROTOCOL.md?

jeffro256[m]: github.com/sanderfoobar/py-levin

selsta thanks!

.merges

luigi1112 yay! Thanks a bunch!

Does anyone know of anyone creating a Levin Wireshark dissector? I think that could be very useful as an educational tool. I've been reading about the Levin protocol all day, and I was thinking of making one for my own personal use, and maybe it would be helpful for others as well

both users seem to have similar CPUs and issues syncing up but could be coincidence

hmm, AMD FX 8300 is from 2012 that shouldn't be an issue

jeffro256: I don't think anyone has ever gone that far, and it would definitely be a great tool to have! I for one could definitely use it

luigi1112: can you pm me? I can't