[Player] guard malformed time_to expression parsing#11462
Open
Harmenszoon wants to merge 2 commits into
Open
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
time_to_player expressions before reading the third split segmenttime_to_expressions such asfury.time_to_before reading the third split segmentCause
player_t::create_expression()accepts any expression prefixed withtime_to_, splits it on_, then readsparts[2]. Becauseutil::string_split()skips empty entries, the literaltime_to_produces only{time, to}, so the old code read past the end of the vector.player_t::create_resource_expression()had the same shape for resource expressions. A malformed resource expression likefury.time_to_also split to only{time, to}before the parser readparts[2].Validation
build-fastwith MSVC 14.44 / Ninja throughVsDevCmd.batbuild-baseline/simc.exe profiles/MID1/MID1_Demon_Hunter_Havoc.simc actions=/wait,sec=time_to_ iterations=1 target_error=0 cleanup_threads=1producedInvalid expression 'time_to_': bad allocationbuild-fast/simc.exe profiles/MID1/MID1_Demon_Hunter_Havoc.simc actions=/wait,sec=time_to_ iterations=1 target_error=0 cleanup_threads=1reportsInvalid 'time_to_' expression 'time_to_'.build-baseline/simc.exe profiles/MID1/MID1_Demon_Hunter_Havoc.simc actions=/wait,sec=fury.time_to_ iterations=1 target_error=0 cleanup_threads=1producedInvalid expression 'fury.time_to_': string too longbuild-fast/simc.exe profiles/MID1/MID1_Demon_Hunter_Havoc.simc actions=/wait,sec=fury.time_to_ iterations=1 target_error=0 cleanup_threads=1reportsInvalid resource expression 'fury.time_to_'.build-fast/simc.exe profiles/MID1/MID1_Demon_Hunter_Havoc.simc actions=/wait,sec=time_to_pct_ iterations=1 target_error=0 cleanup_threads=1still reports the existingNo pct value given for 'time_to_pct_' expression.errorbuild-fast/simc.exe profiles/MID1/MID1_Demon_Hunter_Havoc.simc actions+=/wait,sec=fury.time_to_max iterations=1 target_error=0 cleanup_threads=1 output=NULandactions+=/wait,sec=fury.time_to_80 ... output=NULboth exit 0build-fast/simc.exe profiles/CI.simc iterations=10 target_error=0 cleanup_threads=1 output=NULexits 0 with existing baseline warningsRisk
Low. Valid
time_to_die,time_to_pct_*, and<resource>.time_to_*expressions still have at least three split segments and continue through the existing parser paths.