-
Notifications
You must be signed in to change notification settings - Fork 666
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
[BUG] For incorrect name formats return a better error #4174
Comments
I hope you're doing well! I came across this issue and I'm excited about the opportunity to contribute to Hacktoberfest. It looks like a great fit for my skills and interests. I would love to work on this issue and make a meaningful contribution to the project. Could you please assign it to me, or provide guidance on how I can get started? I'm eager to collaborate with the team and ensure the issue is resolved effectively. Thank you for your time, and I'm looking forward to being part of this project! Best regards, |
Looks like a PR has already been created. |
@samhita-alla I'm glad to see the project is so active, and I'll keep an eye out for other opportunities to contribute. If there's anything specific that needs attention or any other way I can help, please feel free to let me know. I'm eager to get involved and contribute to this project. Thanks again, and happy coding! Best regards, |
if this issue is still open i would like to contribute into this please assign this to me. |
Describe the bug
pyflyte run --remote --name 078b0145-016a-44d8-bac0-fffa2e722f9c test2.py wf --n 10
returns
This is hard to understand the problem.
The reason is
flyte/flyteadmin/pkg/manager/impl/validation/execution_validator.go
Line 134 in 81b94a4
returns just the failing field, it should return the expected regex
Expected behavior
invalid name format: 078b0145-016a-44d8-bac0-fffa2e722f9c, does not match regex '^[a-z][a-z\-0-9]*$'
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: