-
Notifications
You must be signed in to change notification settings - Fork 614
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
[Docs] Docstring for map_task
's min_success_ratio
#4623
Comments
Thank you for opening your first issue here! 🛠 |
🤖 Hello @artgillespie! I'm Dosu, a friendly bot here to help you while we wait for a real human maintainer. I'm here to assist with bugs, answer questions, and guide you through contributing. Remember, no question is too small or too big for me! Let's work together on this. Thank you for your feedback on the Based on the context provided, the In the Flyte codebase, the In contrast, in the test case named "OneSubNodeFailed", there is no You can find these test cases in the flytepropeller/pkg/controller/nodes/array/handler_test.go file. Based on this, a more accurate docstring for the :param min_success_ratio: This determines the minimum ratio of successful sub-tasks required for the overall task to be considered successful. If the success ratio of the sub-tasks falls below this value, the task will be terminated and marked as unsuccessful. I hope this clarifies the purpose and usage of the SourcesThis response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
Is this something I can work on? |
@0xSolanaceae sure! let us know soon if you have questions. Thanks! |
Description
See Slack thread for more context.
I found the docstring
to be somewhat unclear. Specifically,
map_task
will map across all inputs as long asmin_success_ratio
is satisfied and only terminate early when the number of failed tasks exceeds1.0 - min_success_ratio
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: