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
The workflow run configuration for workflow engine type "Hop remote workflow engine" can reference itself.
Incident Details:
This issue occurred with the following workflow:
Hop server is running on a VM (VirtualBox, Ubuntu 24.04, openjdk version "11.0.23" 2024-04-16), default installation with no modifications.
In the Hop GUI (Windows), the server was added via the Metadata button -> Add Hop Server.
The workflow run configuration "test" was created with "Hop remote workflow engine".
Clicking on the "Start execution button" then click on the play button.
This opens the run configuration for "test". Here it is possible to select again "test" as run configuration.
Clicking OK -> Launch results in the following error, see file: log.log
Resetting to local run configuration and starting the Workflow again -> pop-up indicates that the workflow is already running.
However the stop button is greyed-out.
Later, the stop button becomes visible, but clicking it does not abort the process.
Restarting Hop is required to resume work.
Expected Behavior:
When opening the run options -> edit this metadata
it should not be possible to select "test" run configuration again!
Issue Priority
Priority: 2
Issue Component
Component: Hop Gui, Component: Hop Server, Component: Metadata, Component: Workflows
The text was updated successfully, but these errors were encountered:
Apache Hop version?
2.8.0
Java version?
openjdk version "11.0.23" 2024-04-16 LTS
Operating system
Windows
What happened?
Issue Description:
The workflow run configuration for workflow engine type "Hop remote workflow engine" can reference itself.
Incident Details:
This issue occurred with the following workflow:
Hop server is running on a VM (VirtualBox, Ubuntu 24.04, openjdk version "11.0.23" 2024-04-16), default installation with no modifications.
In the Hop GUI (Windows), the server was added via the Metadata button -> Add Hop Server.
The workflow run configuration "test" was created with "Hop remote workflow engine".
Clicking on the "Start execution button" then click on the play button.
This opens the run configuration for "test". Here it is possible to select again "test" as run configuration.
Clicking OK -> Launch results in the following error, see file: log.log
Resetting to local run configuration and starting the Workflow again -> pop-up indicates that the workflow is already running.
However the stop button is greyed-out.
Later, the stop button becomes visible, but clicking it does not abort the process.
Restarting Hop is required to resume work.
Expected Behavior:
When opening the run options -> edit this metadata
it should not be possible to select "test" run configuration again!
Issue Priority
Priority: 2
Issue Component
Component: Hop Gui, Component: Hop Server, Component: Metadata, Component: Workflows
The text was updated successfully, but these errors were encountered: