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
{{ message }}
Repository navigation
Commit 13cd2ac
Browse filesBrowse the repository at this point in the historyBrowse files
DPL: record the workflow plugin of each data processor
DataProcessorInfo and DeviceExecution get the plugin which defines the
data processor, as <library>:<plugin>, and the workflow JSON gets a
"plugin" key in the metadata of the data processor. This is what a
driver needs to load the plugins of a workflow itself.
Plugins embedded in the executable, i.e. with an empty library, are not
recorded: their plugin stays empty and the key is not written, so the
dumps of all existing executables are unchanged. Internal data
processors added by DPL have no plugin either. Data processors imported
from an upstream workflow keep the plugin they had there.
Tested by TestDataProcessorInfoPlugin, a round trip of a workflow with
and without plugins, and test_Framework_test_WorkflowPluginsDump, which
dumps the workflow of the two test plugins.
0 commit comments