Exception handling revamp, parallel multi-host inflation#4398
Merged
Conversation
Pull Request Test Coverage Report for Build 15833375480Details
💛 - Coveralls |
Member
Author
Well, I certainly did not anticipate this! So not only was it not about us using a bad index with an array, it wasn't even about an array at all (insert not-impressed-face meme here)! There is only one Lines 649 to 682 in dd37ee2 I guess we need to switch that cache to a |
1 task
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
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.
Motivations
https://dotnet.microsoft.com/en-us/download/dotnet-framework
Task.Runwas introduced to replace the simplest usages ofTask.Factory.StartNew.https://devblogs.microsoft.com/dotnet/task-run-vs-task-factory-startnew/
resources.storelinks for the DLCs and addedresources.gogstoreandresources.epicstore, but we need some client updates to display them.Index was outside the bounds of the array.errors for a while now, which cannot be reproduced locally. I have audited our code and not found any suspicious usages of array indexes. To figure out what is causing this, we need the bot to log more information from the exception.Problems
Causes
ModUpgrade, which then ran afoul of the upgradability-checking logic from Better version specific relationships at install and upgrade #4023.v1.36.0.25098, but from the GitHub API we get only our tagv1.36.0, and the extra build number piece makes these two in-fact equal versions compare as non-equal.Changes
Task.Factory.StartNeware changed toTask.RunTasks, which means that it will contact GitHub and SpaceDock simultaneously and process each of them independently, which should be overall quicker than doing it sequentially.Kraken.Messageproperty now always holds the user-friendly string that should be displayed to explain the problemKrakenno longer overrideToString, so we can use the standard implementation to print stack traces if neededKraken.MessageforKrakenexceptions rather than custom UI-specific messages, andException.ToString()for non-Krakens. This roughly corresponds to printing simple, user-friendly messages for "expected" exceptions and full stack traces for "unexpected" exceptions, and should allow us to identify the cause of theIndex was outside the bounds of the array.errors.bin/find_unused_resources.shutility is created to identify unused i18n resources