Age Manning

Hey, thanks for this! These are great suggestions. I think the best benefit and easiest to implement here would be to do 2 and 3. 3. Should be as simple...

I like the coloured logging to file. I think that makes it nicer and easier to read. Except for those red thingy's in there, but I assume thats some vscode...

@ThreeHrSleep - Looks like there's still some todo's in here. I've gone through and fixed most of the stuff @macladson has flagged, there is a lot of comments still in...

I had a quick skim over the SEE logging and it looks like its implemented. I'll try running some versions like pawan and see if I notice anything and will...

Just want to point out, As we currently have gossipsub integrated into Lighthouse (i.e its currently not strictly a dependency), we are showing tracing logs to std out for gossipsub....

Yeah, lets merge that before this. I've been running this PR and finding quite a few issues. For example: ``` Feb 05 13:45:59.120 DEBUG Requesting batch epoch=339076 batch=Start Slot: 10850432,...

@ThreeHrSleep - There are many such cases of broken logs from what I can see. I've only run this for < 10 seconds. The way I'm testing is by following...

This looks like a duplicate of #461. #461 seems to handle some other cases like partial sync

I think we are going to need some logs to diagnose this. The described behaviour is similar to a node that loses an internet connection. Debug logs can be found...

I have been through these logs. The logs show "Socket Updated" (you can grep through the logs for this). This log indicates that discovery is changing contactable IP/PORT based on...