Logging improvements (Node definition overhaul)

[bilal-fazlani]

The logger currently is a custom implementation and a layer inside MaelstromRuntime. The apis to use logging methods are exposed at top level.

When there is an unhandled error, ZIO's runtime logs it using ZIO's default logger which prints data on STDOUT. This is breaks maelstrom because it uses STDOUT and network IO and can't makes sense of this log.

Also, one thought is - it does not makes sense to have another logging interface for ZIO-Maelstrom when ZIO does provides a native interface.

Somehow, we need to create logger extending ZIO's interface and provide an easy mechanism to replace default logger with Maelstrom logger.

---

Tasks

• implementation
• tests
• documentation
• examples

---

Update: 27 Feb 2024

Using a custom logger as ZIO logger requires overriding bootstrap method in a ZIO app. Overriding was not possible in the older approach there was no parent class to extend from. So this turned out to be a lot bigger change than expected. I had to change the Node definition approach from a simple ZIO effect to an object which extends from a new trait called MaelstromNode. Extending this trait now installs the new ZIOMaelstromLogger. Because logLevel and logFormat were part of settings which was part of layer construction, I also had to break that down make it into an overridable val/def.

[netlify]

✅ Deploy Preview for zio-maelstrom ready!

Name	Link
🔨 Latest commit	40b8f42
🔍 Latest deploy log	https://app.netlify.com/sites/zio-maelstrom/deploys/66813bc0be836c000825b221
😎 Deploy Preview	https://deploy-preview-13--zio-maelstrom.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.