seantcanavan / anon-eth-net Goto Github PK

when reading the logs for the profiler test we needed to ensure they were flushed from the writer before being able to peek at the log file to pull from it. i lazily put .flush after every individual log output which defeats the purpose of buffering in the first place. we should probably flush inside the method for peeking at logs instead of the LogMessage() function

will be used to run things like go-dos-yourself with

Kinda interested on how you plan to implement the miner? Are you going to have the program download a miner and run it with parameters or...?

think about all the values a new user would have to setup on their first time and see if it's really necessary

need to clean up some zombie code before it gets out of control

no glide and no make... RIP

consider adding an automatic retry if the first time fails. consider also retrying 3-5 times. there's a 30 second built-in timeout in the go code. sometimes one email fails, sometimes both emails fail, sometimes both emails succeed.

one or the other. and fix the printing output too. should be in seconds - not nanoseconds.

do it!

right now local and remote are pulled directly from config.json. they should be pulled in via the asset loader.