Skip to content
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

chore: change max length secondary branch #268

Merged
merged 4 commits into from
Feb 27, 2024
Merged

Conversation

@ThibaultFy ThibaultFy marked this pull request as ready for review October 20, 2023 09:17
@ThibaultFy ThibaultFy requested review from HamdyD, jmorel and a team as code owners October 20, 2023 09:17
@ThibaultFy ThibaultFy force-pushed the feat/merge-predict-test branch 2 times, most recently from 7c92b06 to 191f7b2 Compare October 26, 2023 07:30
ThibaultFy and others added 4 commits February 26, 2024 15:44
@ThibaultFy ThibaultFy force-pushed the feat/merge-predict-test branch from 191f7b2 to ccb5566 Compare February 26, 2024 14:44
@guilhem-barthes
Copy link
Contributor

Can this unlock showing graphs for bigger workflows ?

@ThibaultFy
Copy link
Member Author

Can this unlock showing graphs for bigger workflows ?

Mmmmh that's an interesting question. Does the current limit is set in number of task or with an other metric ?
If this is in number of tasks, the number of round of a common workflow will increase but only due to the fact that a round will have less tasks than before.

@ThibaultFy ThibaultFy merged commit 59c97d9 into main Feb 27, 2024
3 checks passed
@ThibaultFy ThibaultFy deleted the feat/merge-predict-test branch February 27, 2024 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants