che-server resolves the unexisting repo with a default devfile
Describe the bug
Create a new workspace from the unexisting repo and a new workspace will be created without any errors.
Che version
7.71@latest
Steps to reproduce
- Try to create a new workspace from the unexisting repo
<che-server>#https://github.com/eclipse-che/che-dashboard888888888
- A new workspace will be opened without any errors.
Expected behavior
- Try to create a new workspace from the unexisting repo
<che-server>#https://github.com/eclipse-che/che-dashboard888888888
- An error message should be appaired during creation.
Runtime
minikube
Screenshots
Installation method
chectl/latest
Environment
macOS
Eclipse Che Logs
No response
Additional context
No response
This is a tricky one, as the same logic covers a) repositories that actually do not exist, and b) repositories that do exist but are inaccessible by the server.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
/remove-lifecycle stale