Open daipom opened 2 months ago
However, I'm concerned that caller_plugin_id has a race condition, although I don't confirm it. It looks to me that the id can be another plugin-id running concurrently...
As error.backtrace does not have enough information in this context, so current approach seems reasonable. (No need to force 3rdparty plugins to fix it)
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 7 days
Which issue(s) this PR fixes:
What this PR does / why we need it: Add caller plugin-id to warning logs about emitting error events.
It would be helpful if we could know what plugin emitted the error event.
We need to care about the compatibility. This signature change would not break compatibility.
However, I'm concerned that
caller_plugin_id
has a race condition, although I don't confirm it. It looks to me that the id can be another plugin-id running concurrently... It is not the issue with this fix, it is the issue of the existing implementation.Docs Changes: Not needed.
Release Note: Add plugin-id to warning logs about emitting error events.
Example: From #4567.