You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every time opsdroid responds in a thread for the slack connector, the log is throwing an error in the following form:
ERROR Payload: {...} is not implemented. Event wont be parsed
This is not really an error, but just a misplaced log message that should be a debug message.
The create_event method from the slack connector is returning an empty event. The event_handler checks that the event is not empty and throws the error, which should not be. If the event returns empty (which is valid) the event handler should not parse the event.
Since it's labeled as an error, every time there is a response in a thread from opsdroid, the ERROR is logged, which creates a lot of false entries in a production log.
Steps to Reproduce
Create a skill where opsdroid replies inside a thread
Expected Functionality
The error log should not appear as it's not really an error
Experienced Functionality
The logger is longing an ERROR message which is not really an error
Versions
0.26:
The text was updated successfully, but these errors were encountered:
chillipeper
changed the title
Opsdroid is logging
Opsdroid is logging an error which is not really an error
May 5, 2022
chillipeper
changed the title
Opsdroid is logging an error which is not really an error
Slack Connector is logging an error which is not really an error
May 5, 2022
Description
Every time opsdroid responds in a thread for the slack connector, the log is throwing an error in the following form:
This is not really an error, but just a misplaced log message that should be a debug message.
The create_event method from the slack connector is returning an empty event. The event_handler checks that the event is not empty and throws the error, which should not be. If the event returns empty (which is valid) the event handler should not parse the event.
Since it's labeled as an error, every time there is a response in a thread from opsdroid, the ERROR is logged, which creates a lot of false entries in a production log.
Steps to Reproduce
Create a skill where opsdroid replies inside a thread
Expected Functionality
The error log should not appear as it's not really an error
Experienced Functionality
The logger is longing an ERROR message which is not really an error
Versions
The text was updated successfully, but these errors were encountered: