Conversation
Member
|
The question is whether anyone will notice there was a failure, as the workflow will still show as successful? |
Contributor
Author
|
You are right. We could add another job to check for timeouts and then mark this job as failed or create an issue out of the failed translation. We can also just leave it as it and see how often it will bother us, maybe that´s the best solution for now. What do you think? |
Member
|
Yes, let's leave this open and see if we can live without it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@DavidMStraub maybe we also add this. If a timeout happens, the rest will still be translated and we can manually trigger the missing ones...