Restarting application makes it look like it failure

[kadel]

/kind bug
/priority medium

How did you run odo exactly?

▶ odo init --name test --devfile nodejs --starter nodejs-starter
  __
 /  \__     Initializing a new component
 \__/  \
 /  \__/    odo version: v3.5.0
 \__/

 ✓  Downloading devfile "nodejs" [2s]
 ✓  Downloading starter project "nodejs-starter" [570ms]

Your new component 'test' is ready in the current directory.
To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
Changes will be directly reflected on the cluster.

▶ odo dev
  __
 /  \__     Developing using the "test" Devfile
 \__/  \    Namespace: tkral-dev
 /  \__/    odo version: v3.5.0
 \__/

↪ Deploying to the cluster in developer mode
 •  Waiting for Kubernetes resources  ...
 ✓  Pod is Running
 ✓  Syncing files into the container [2s]
 ✓  Building your application in container on cluster (command: install) [6s]
 •  Executing the application (command: run)  ...
 -  Forwarding from 127.0.0.1:40002 -> 3000

 -  Forwarding from 127.0.0.1:40003 -> 5858


↪ Dev mode
 Status:
 Watching for changes in the current directory /Users/tkral/Code/odo-examples/tmp

 Keyboard Commands:
[Ctrl+c] - Exit and delete resources from the cluster
     [p] - Manually apply local changes to the application on the cluster

make changes to server.js

Pushing files...


File /Users/tkral/Code/odo-examples/tmp/server.js changed
 •  Waiting for Kubernetes resources  ...
 ✓  Syncing files into the container [1s]
 ✓  Building your application in container on cluster (command: install) [2s]
 ✗  Finished executing the application (command: run) [1m]
 •  Executing the application (command: run)  ...

↪ Dev mode
 Status:
 Watching for changes in the current directory /Users/tkral/Code/odo-examples/tmp

 Keyboard Commands:
[Ctrl+c] - Exit and delete resources from the cluster
     [p] - Manually apply local changes to the application on the cluster

line
✗ Finished executing the application (command: run) [1m]
makes it look like something failed

Expected behavior

When it is expected that the run process should end the status message should have the green tick mark

[rm3l]

Grooming (2023-01-23)

• Distinguish between a "normal" stop of the application (when we are intentionally restarting it, e.g., due to a change in local files) and an "abnormal" stop (remote command exited, container restarted due to changes in the cluster, ...)
• Idea to have 3 states in the Spinner (started, finished with error, finished without error)

[github-actions]

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

[rm3l]

/remove-lifecycle stale
/lifecycle active

Under consideration for the upcoming sprints.