Hide new sandbox logs

[austinabell]

@ChaoticTempest I know you had this on your radar, just opening an issue to track.

logs to hide by default:

16 yU2WXsRE33GP67Z1Xxrj2JQtC1PVnwseotLoxDhyMnw Processed in progress for 1ms   Chunks:(✔))
15 xEMRPzeXaYd3EukmjWqUpoP15sGd2D4UoxsCZqddjoD Processed in progress for 145ms   Chunks:(✔))
14 NaJrcgeQShGNSa8yXdNcicPcLbodxppuTtzBNMWSk6v Processed in progress for 2ms   Chunks:(✔))
13 363LbGfK2j6N5h3ZwnV479seJfqcFFR8E8jNNnEgTqq9 Processed in progress for 2ms   Chunks:(✔))
12 Cc3TiXwXxEn9X5R6968yjmC8UedycWuhqimh5gDTaUkc Processed in progress for 1ms   Chunks:(✔))
11 9CotxEkFwm9iWy5jGrv1oPBnj6h1oPErPWJXoi3ZjRtu Processed in progress for 3ms   Chunks:(✔))
10 7JjRmL2BCVao8JLyLoREw1EyNqsyguBuQXv9mLidUzm6 Processed in progress for 4ms   Chunks:(✔))
9 tDqAjRKkunbP2WSMPD2x7GvVNSENsPgofTxn4PBhXTh Processed in progress for 1ms   Chunks:(✔))
8 5gPkVKXrHkZgvrUJgw6r31hJqayzC5Z71BDDYTPq7XsF Processed in progress for 2ms   Chunks:(✔))
7 CK2zL3cdn39zZdi8AhVVGwVKbXxyfpotsQ2JHtFAc6XY Processed in progress for 1ms   Chunks:(✔))
6 5iE7xopvoiKKEmCdx3MmLEG2VwmdwhF2eG63k8YybVjR Processed in progress for 2ms   Chunks:(✔))
5 4auXnPNA8ZMhuke92Re2xoZajmf37g4XdtaCkmmpEAMR Processed in progress for 2ms   Chunks:(✔))
4 FZQMwvSHPY2t2Aq4Zbs4ScXbQjakNp3DAsxbZEVA4Mej Processed in progress for 3ms   Chunks:(✔))
3 EL1VMtZ53BjkD1HdZuhdDFDAepq1oQxbiRNwY1XGy7JT Processed in progress for 11ms   Chunks:(✔))
2 Bi4otFrVyF3fTjcJuBSkU9pTDCTA41mDk1VkG8H8aTq3 Processed in progress for 4ms   Chunks:(✔))
1 8NrNh3bFKGgozJ4N97zrT8rSH2mRR8YfVLVo1S1Qwt6m Processed in progress for 1ms   Chunks:(X))

[ChaoticTempest]

these are quite annoying. Trying to fix it this sprint as well, so hopefully it's not such an eyesore afterwards

[joshuajbouw]

Usually you see these if there is a subscriber to the logs. In particular, the tracing-subscriber, which I would argue, should not be included in the dev dependencies. The choice for logs should be down to the user of the library, even in dev env.

Thanks for posting this, as I was too about to write an issue for this.

[ChaoticTempest]

fix by #213