Harden BCU console export and size detection - Fix BCU-console export failures (#879, #880)#897
Open
breshinotestachegira wants to merge 1 commit intoKlocman:masterfrom
Conversation
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.
Summary
This PR hardens two BCU-console related failure paths.
Fixes
es.exeavailability failures more defensively when estimating sizesChanges
FastSizeGeneratorso missing/broken Everything integration degrades gracefullyes.exeand surface a more useful error message on failureWhy
Two open issues report:
hexadecimal value 0x1F, is an invalid characterThis change keeps export working and makes size-detection fallback behavior safer.
Closes #879
Closes #880