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
We have an environment where we upgraded from vaping version 1.3.0 (Python 3.6) to vaping version 1.5.3 (Python 3.9.16, RHEL 9). After the upgrade, we see that there is a problem with the plugins that we were using.
We have a total of 3 probe plugins derived from vaping.plugins.TimedProbe all of which output to a common emit plugin derived from vaping.plugins.EmitBase. This combination used to work well in vaping 1.3.0. However in vaping 1.5.3, the output from only one of the probe plugins is being emitted. The output of the other two probe plugins is not emitted even though output is queued as per the log from the framework.
There is no issue with the probe or the emit plugins itself since if there is only one probe plugin specified in the config file, then its output is emitted.
Could you please let us know if there is any known limitation in having multiple probe plugins in vaping 1.5.3 and if they can use a common emit plugin.
Hi @csksudhir, we have made no (intended) changes to limit how emission works, however 1.4.0 switched to asyncio for handling concurrency, maybe that introduced some quirkiness with your setup. I will need to try and reproduce the issue.
We have an environment where we upgraded from vaping version 1.3.0 (Python 3.6) to vaping version 1.5.3 (Python 3.9.16, RHEL 9). After the upgrade, we see that there is a problem with the plugins that we were using.
We have a total of 3 probe plugins derived from vaping.plugins.TimedProbe all of which output to a common emit plugin derived from vaping.plugins.EmitBase. This combination used to work well in vaping 1.3.0. However in vaping 1.5.3, the output from only one of the probe plugins is being emitted. The output of the other two probe plugins is not emitted even though output is queued as per the log from the framework.
There is no issue with the probe or the emit plugins itself since if there is only one probe plugin specified in the config file, then its output is emitted.
Could you please let us know if there is any known limitation in having multiple probe plugins in vaping 1.5.3 and if they can use a common emit plugin.
Here's a sample of the config.yaml:
The text was updated successfully, but these errors were encountered: