disable ethers logging

[scott-silver]

Our scenario output is dominated by duplicate definition - //...

We can turn that off using ethers.utils.Logger.setLogLevel.

Not sure if we'd be losing other useful information, but it makes things a lot more readable:

Before:

After:

source: ethers-io/ethers.js#379 (comment)

[kevincheng96]

🙌 Would love for these pesky logs to go away. Though I'm not sure if it will be masking any other warnings that we might care about. Let's see what Jared and Geoff think.

[jflatow]

Yeah these logs are super annoying, but seems like we might want some logging at some point?

[scott-silver]

@jflatow yeah, we probably do want these logs some of the time. but i've been using this patch locally the last few days and it's been really helpful to actually be able to read the scenario logs

maybe we could optionally disable it?

[jflatow]

@jflatow yeah, we probably do want these logs some of the time. but i've been using this patch locally the last few days and it's been really helpful to actually be able to read the scenario logs

maybe we could optionally disable it?

Yeah what about adding an env var to disable like hre.ethers.utils.Logger.setLogLevel(hre.ethers.utils.Logger.levels[env.HRE_LOG_LEVEL || 'OFF'])

[scott-silver]

@jflatow I updated this to be a flag on the scenario task. So now you can run:

yarn scenario --quiet

if you want to reduce the output.