Improving Engine verbosity for code debugging

[ElisaRojas]

Hi,

After checking the current status of the Engine, I think it would be nice to have a common level of verbosity for all different modules (Shim, Core and Backend). I missed this in our previous version of the Engine, but now that it's getting more complex, it would really help debugging.

What do I mean by common level of verbosity? For example: when a shim or a backend is connected to the core, to show some phrase like "connected to..." and maybe even the ports assigned for that connection (now that we have multiple possibilities, we know the 5555 and 6633, but the rest are random).

Also it would be nice if the output was the same for all backends, for all shims, etc. So that we know what is not working and when (provided those outputs). I missed this a lot in the previous Engine, because every backend and shim showed different messages.

Maybe, for this new Engine, @doriguzzi could show what he's used for verbosity for the Ryu backend and shim, to let other developers know what to do as well. Or we can define some format to do so. In any case, this requires some synchronization and it is not urgent. But I think it would be a good feature to have. What do you think?

Thanks!!

[sergiotamu]

Hello @ElisaRojas,

I think that you can enable the logging option at the beginning of each file just adding to the code:
logger.setLevel(logging.DEBUG)
With this option you can see more details in the console =)

[paaguti]

Right Elisa, I wonder if we cannot take Roberto's implementation as a
reference in many details. Verbosity is one instance I like a lot.
El 29/10/2015 21:03, "Elisa Rojas" [email protected] escribió:

Hi,

After checking the current status of the Engine, I think it would be nice
to have a common level of verbosity for all different modules (Shim, Core
and Backend). I missed this in our previous version of the Engine, but now
that it's getting more complex, it would really help debugging.

What do I mean by common level of verbosity? For example: when a shim or a
backend is connected to the core, to show some phrase like "connected
to..." and maybe even the ports assigned for that connection (now that we
have multiple possibilities, we know the 5555 and 6633, but the rest are
random).

Also it would be nice if the output was the same for all backends, for all
shims, etc. So that we know what is not working and when (provided those
outputs). I missed this a lot in the previous Engine, because every backend
and shim showed different messages.

Maybe, for this new Engine, @doriguzzi https://github.com/doriguzzi
could show what he's used for verbosity for the Ryu backend and shim, to
let other developers know what to do as well. Or we can define some format
to do so. In any case, this requires some synchronization and it is not
urgent. But I think it's a good feature to have.

Thanks!!

—
Reply to this email directly or view it on GitHub
#47.