order of function call corrected. On similar lines of rasa-sdk

[gajendrarao1979]

Proposed changes:

• ...

Status (please check what you already did):

• added some tests for the functionality
• updated the documentation
• [*] updated the changelog (please check changelog for instructions)
• [*] reformat files using black (please check Readme for instructions)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[vcidst]

Hi @gajendrarao1979, thank you for the pull request! Can you please describe the changes you've made and why are they required?

[gajendrarao1979]

@vcidst
Currently in rasa main.py the configure_logging_and_warnings function which configures the logging from the config file is called at line 103 and after that configure_colored_logging is called at line 116.

The configure_colored_logging function leverages coloredlogs module which discards and reinitializes logging.StreamHandler. Essentially this overwrites any changes coming from logging.yml (if someone is using StreamHandler).

In my PR I have updated the order of the function call to ensure that logging.yml changes are not overwritten. This is already correct in rasa-sdk code.

I hope this provides the explanation.

[gajendrarao1979]

@vcidst Any updates on this?

[pdelagrave]

Necessary change for using on a production system where observability matters. Hoping to see this PR merged soon!

[vcidst]

Hey @gajendrarao1979, we won't be able to merge these PRs as this repository isn't under active maintenance anymore. Please see this page for our product releases and maintenance policy

[arththebird]

Hey @gajendrarao1979, we won't be able to merge these PRs as this repository isn't under active maintenance anymore. Please see this page for our product releases and maintenance policy

Hi @vcidst, could you please clarify why this PR won't be merged? I've read the maintenance policy page you referenced and I can't see any mention of Rasa Open Source being deprecated. Is there an announcement from Rasa anywhere that the open source version is no longer maintained?

Thanks!

[gajendrarao1979]

Hey @gajendrarao1979, we won't be able to merge these PRs as this repository isn't under active maintenance anymore. Please see this page for our product releases and maintenance policy

Hi @vcidst, could you please clarify why this PR won't be merged? I've read the maintenance policy page you referenced and I can't see any mention of Rasa Open Source being deprecated. Is there an announcement from Rasa anywhere that the open source version is no longer maintained?

Thanks!

@vcidst can you please comment on this? If RASA Opensource is no longer maintained then we need to find alternate solution.

[gajendrarao1979]

@arththebird , @pdelagrave One workaround which we did to circumvent this issues is re-initialized logging in custom-channel code which gets executed after rasa initialization (not ideal but works until the fix in the library is available.)