Search Issue Tracker
Fixed
Fixed in 2021.3.36f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b4
Votes
3
Found in
2021.3.21f1
2022.2.11f1
2023.1.0b8
2023.2.0a6
Issue ID
UUM-31240
Regression
No
"vector<bool> too long" error is thrown when using UnityYAMLMerge
Steps to reproduce:
1. Open user attached “Repro_I_Received” folder
2. Run the Repro.bat file
Expected result: Runs the Repro.bat file without any errors
Actual result: “vector <bool> too long” error is thrown
Reproducible with: 2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Could not test with: 2020.3.46f1 (“Invalid rule format at line 38” error is thrown)
Reproduced on: Windows 11 (Intel)
Not reproduced on: macOS Monterey 12.2 (Intel) (can’t run .bat file)
Note: Replace the UnityYAMLMerge file in the “Repro_I_Received” folder from each reproducible with Editor version by going to /Data/Tools
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
shifatkhan
Sep 25, 2023 16:22
Reproduced Error with 2020.3.36f1 and Fork.
Scenario: I have Branch A and Branch B, where B is was created from A. Both branches changed the same file. B is trying to merge A into itself.
One work-around I found is to create a new Branch from A. Then cherrypick each commit from B. The conflict when the conflict arise, the UnityYAMLMerge seemed to have no problem fixing it.
The issue with this workaround is that it can take a long time if you have many commits.