Open KnowWhoami opened 2 weeks ago
This is happening because of how the setup_logger
function is unified for all the apps.
Solution: Use different setup_logger
functions for different apps. For v0.1.0 this would be the quickest fix.
This will also be solved once we have our own custom logger.
So should we solve this issue after having our custom logger or fix it now? I think , we should fix it in v0.1.0 itself with the proposed solution otherwise these bugs will be exposed while running our cli-apps. What do you think?
Ack on fixing it now with the quick fix. We need individual setup_logger functions for each apps.
For eg: whenever
directoryd
binary server is started -> 2 other directories named asmaker
,taker
havingdebug.log
file are created along with the expecteddirectory
one which is not a good UX design. This similar behaviour happens if we runmakerd
ortaker
cli app too.Expected Outcome:
Only single directory with the required files must be created whose binary is being used.