job run doesn't exist for long running jobs

[wdbaruni]

When submitting a service or daemon job, the expectation is for the job progress to exist as soon as the job is scheduled or maybe just when accepted. Whatever behaviour we had with v1.4.0

The case today is that job progress doesn't exist and waits for the jobs to be completed, which will never happen unless the user stops the job.

How to reproduce

1. Create a file named service_job.yaml with the following content:

name: Long-Running Service Job
type: service
namespace: default
count: 3
tasks:
  - name: main
    engine:
      type: docker
      params:
        Image: ubuntu:latest
        Entrypoint:
          - /bin/bash
        Parameters:
          - -c
          - while true; do (date && echo "Service job running" && sleep 5); done

2. Submit the service job using the YAML file:

→ bacalhau-1.5.0 job run service_job.yaml

Job successfully submitted. Job ID: j-c2123969-2e93-4773-acfd-d4ee6a4d105e
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):

 TIME                 EXEC. ID    TOPIC         EVENT
 Sep 17 13:07:25.172  e-05f1d99f  Execution     Running
 Sep 17 13:07:25.172              State Update  Running
 Sep 17 13:07:25.222  e-f6af9dd0  Execution     Running
 Sep 17 13:07:25.222  e-dd7941f8  Execution     Running

[udsamani]

@wdbaruni Do you have any default timeout in mind ?

[wdbaruni]

I remember we had something before with v1.4.0. If not lets say 5 minutes?