-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The UD does not have a length limitation for auto-generated names #22758
The UD does not have a length limitation for auto-generated names #22758
Comments
@olexii4: hello, Therefore, reopening the issue for further investigation. |
@dmytro-ndp It is not about length limitation for auto-generated names. We have a different problem now: che-server generates an invalid devfile in the case with an unexisting repo. We should create a new issue for che-server and close this one. |
@olexii4 : thanks for the answer. |
@olexii4 : The error has been reproduced on Dev Spaces 3.12.0 deployed to the DevSandbox Stage with an existing repository having a 70-character-long name: https://github.com/dmytro-ndp/70_symbols_long_repo_name_kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Note: click on "Continue with default devfile" button at the error page is leading to the same error page. |
@dmytro-ndp I investigated the problem. It happened because of the changes in We can test these changes with a custom repository instead of Steps to reproduce:
|
Describe the bug
It is impossible to create a new workspace from a git repository URL when the repository doesn't have a Devfile and its path includes more than 63 characters.
Che version
7.79@latest
Steps to reproduce
https://github.com/olexii4/che-editor-theiahkhjkhkjhkjhjhghjhgfghfhgfhgjfghfghjfghjfhgfghfghjfhgfghfhgjfhgjfhg
.Expected behavior
It should create a new workspace with a name shorter than 63 characters.
Runtime
OpenShift
Screenshots
Installation method
chectl/latest, chectl/next
Environment
macOS
Eclipse Che Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: