[I] Init-time fatal errors are not surfaced to the websocket [texera]

["aglinxinyuan (via GitHub)" <gi...@apache.org>]

aglinxinyuan opened a new issue, #5782:
URL: https://github.com/apache/texera/issues/5782

   ### Problem
   
   When workflow execution **initialization** fails, the error is recorded into the execution metadata store but is **never delivered to connected frontend clients** — the user sees no error in the UI even though the execution failed to start.
   
   ### Root cause
   
   `WorkflowService.initExecutionService` wraps execution construction + start in a `try`/`catch`. The catch arm only calls `errorHandler(e)`, which records a `WorkflowFatalError` into the execution metadata store. It does **not** push anything to `errorSubject`, the workflow-level websocket channel that `connect()` subscribers listen on.
   
   For failures during `new WorkflowExecutionService(...)` — i.e. *before* `executionService.onNext(execution)` publishes the execution — no subscriber is ever attached to that execution's metadata store, so the recorded error stays invisible to the UI (it is only logged server-side).
   
   ```
   init fails -> errorHandler records fatal error in metadata store
              -> (no push to errorSubject)
              -> frontend connect() subscriber receives nothing   [X]
   ```
   
   ### Expected
   
   Init-time fatal errors should reach the frontend the same way other errors do:
   
   ```
   init fails -> errorHandler records fatal error
              -> errorSubject.onNext(WorkflowErrorEvent(fatalErrors))
              -> frontend receives WorkflowErrorEvent             [OK]
   ```
   
   Discovered while splitting #5700 (loop operators); the fix is independent of that feature.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Init-time fatal errors are not surfaced to the websocket [texera]

["aglinxinyuan (via GitHub)" <gi...@apache.org>]

aglinxinyuan closed issue #5782: Init-time fatal errors are not surfaced to the websocket
URL: https://github.com/apache/texera/issues/5782


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Init-time fatal errors are not surfaced to the websocket [texera]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on issue #5782:
URL: https://github.com/apache/texera/issues/5782#issuecomment-4746873608

   <!-- texera:template-compliance -->
   👋 Thanks for opening this issue, @aglinxinyuan!
   
   It looks like the issue description doesn't quite follow our template yet:
   
   - The **What happened?** section is missing; please keep the template's headings.
   - The **How to reproduce?** section is missing; please keep the template's headings.
   - The **Version/Branch** section is missing; please keep the template's headings.
   
   Filling out the template helps reviewers understand and triage your contribution faster. Please edit the description to complete it. This message will disappear automatically once the template is followed.
   
   You can find the template prompts by editing the description, or see [CONTRIBUTING.md](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) for the full contribution flow.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org