All incoming anchors initialized, but plugin has errors.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Is there a way to deal with custom tools throwing errors when other tools have errors?
I have a tool that does nothing except pass data through, and it is properly configured inside the workflow.
class MyTool(PluginV2):
def __init__(self, provider: AMPProviderV2):
self.name = "My Tool"
self.provider = provider
def on_record_batch(self, batch: pa.Table, anchor: Anchor) -> None:
self.provider.write_to_anchor("Output", batch)
def on_incoming_connection_complete(self, anchor: Anchor) -> None:
pass
def on_complete(self) -> None:
pass
The problem is that is whenever a tool (custom or built-in) is added with an error, all my custom tools will throw an error too.
The custom tool will throw the error "All incoming anchors initialized, but plugin has errors."
This is also annoying because deleting the Filter tool in this example won't remove the custom tool's error until the user interacts with it and causes a reinitialization.
- Labels:
-
Custom Tools
-
Developer
-
SDK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Unfortunately, no - if there's an error upstream, the engine simply doesn't execute the python code. We don't currently have a way of passing that error into python
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
This doesn't occur with just upstream errors. It occurs with downstream errors and even errors that are not connected to the main workflow as in the picture. This also seems to mostly occur for tools with required input anchors.