Armel Soro 147542db69 Do not necessarily error out if odo dev is stopped via Ctrl+C (#6917) ...

* Add test highlighting the expectations

* Propagate errors and call os.Exit only in 'main' functions

See ExitInMain[1] and ExitInMain_ExitOnce[2] coding convention guidelines.

[1] https://github.com/redhat-developer/odo/wiki/Dev:-Coding-Conventions#exit-in-main
[2] https://github.com/redhat-developer/odo/wiki/Dev:-Coding-Conventions#exit-once

* Handle errors returned by Cleanuper#Cleanup

This makes sure the exit code of the command
is mapped onto any error returned by Cleanup

* Do not return an error when the watch loop in 'odo dev' is interrupted

* Test that the exit code of 'odo dev' matches the error returned by the cleanup logic

2023-06-22 13:14:07 +02:00

..

copy_test.go

Refacto sync pkg (#6163)

2022-09-23 16:30:55 +02:00

copy.go

Do not necessarily error out if odo dev is stopped via Ctrl+C (#6917)

2023-06-22 13:14:07 +02:00

interface.go

Allow to cancel execution of odo dev at any phase (e.g. if build command is taking long) (#6736)

2023-04-20 17:12:28 +00:00

mock.go

Allow to cancel execution of odo dev at any phase (e.g. if build command is taking long) (#6736)

2023-04-20 17:12:28 +00:00

sync_test.go

Allow to cancel execution of odo dev at any phase (e.g. if build command is taking long) (#6736)

2023-04-20 17:12:28 +00:00

sync.go

Check files to sync with gitignore library (#6760)

2023-04-24 16:29:41 +00:00