The GitHub Actions job "Lint PR" on texera.git/hackathon/workflow-hub has failed. Run started by GitHub user EmilySun621 (triggered by EmilySun621).
Head commit for run: 979618e321d3a406bb913bb823ae6b448bd5884f / Emily Sun <[email protected]> fix(hub): fork builds a real DAG from seed entries, not a blank workflow The previous fix used createWorkflow with empty content, so forking a seed entry produced a workflow with the right name but zero operators — the "Executions doesn't exist" 403 the user saw was just the workspace trying to load nonexistent executions for an empty workflow. Now seed entries carry a sampleOperators field listing REAL Texera operator types from the running backend's metadata (verified against the 163 operators the deployed build exposes). When the user forks: 1. Wait for OperatorMetadataService to publish the schema list. 2. For each known sampleOperators type, build a proper OperatorPredicate via WorkflowUtilService.getNewOperatorPredicate (which fills in ports, default properties, and the correct operatorVersion). 3. Connect consecutive operators by their first output→input ports. 4. Lay them out in a horizontal chain (200px apart). 5. POST to /workflow/create with the populated WorkflowContent and navigate to the new wid. Any sampleOperators not present in the running build land in a single comment box at the top of the canvas so the user can see what was intended. For real (published) hub entries with a workflowId, the path is still WorkflowPersistService.duplicateWorkflow — unchanged. Report URL: https://github.com/apache/texera/actions/runs/25970608275 With regards, GitHub Actions via GitBox
