fix: propose consistent usage of debug from tracing

[glihm]

Gm guys,

wondering if this is a typo or an actual fix.

In dojo we're using scarb as a dependency, and when we compile a package of the workspace this error occurs, which prevent us from building a specific package depending on scarb explicitly.

However, when the whole workspace is compiled, it works fine.

Inspecting the scarb code base, everywhere it seems to be tracing::trace, tracing::debug etc... Is this tracing::log::debug forgotten, but not a direct problem as it compiles fine anyway?

Thanks for the feedback!

[maciektr]

Hi!

Yes, this must be a typo! 🙇‍♂️ Thanks for pointing this out! 😍

In dojo we're using scarb as a dependency, and when we compile a package of the workspace this error occurs, which prevent us from building a specific package depending on scarb explicitly.

However, when the whole workspace is compiled, it works fine.

I do not see your error message, but the log module is behind a feature flag in tracing crate, so I suspect it is probably caused by Cargo features resolution. I personally bumped into this as well - apparently, building package alone and as part of workspace may result in usage of different features 🤯. See this issue in Cargo for more context.