Přemek Vysoký
Přemek Vysoký
Thanks for logging the issue. We do not log fail for regular patch application failures. I think these this is an actual unexpected exception when trying to fix the file....
I have a fix in a branch for this
Partially done, one error will be handled in #5767
@dkurepa please put the issue on the board too
@dotnet/dotnet-cli fyi there's 2 conflicts here
This one appeared again: https://dataexplorer.azure.com/dashboards/83ee5d57-8e86-454e-b0ee-69568a6c10e7?p-_startTime=2025-08-05T15-24-00Z&p-_endTime=2025-08-06T15-24-00Z&p-_operationId=v-96fd1f6429c6786376f9cccf7ec9d2f7#8a5bc9bb-f9b8-4876-bbfa-94046fdf0174 > The given key 'NuGet.Frameworks' was not present in the dictionary.
@ViktorHofer would some colouring make it even more readable on what is behind?
We have agreed that we want the page to show the list of repos based on the source manifest in the selected branch, not based on existing subscriptions but based...
We have looked at the requirements here and decided to do the following: ### Design We will show 3 badges: - Last applied build, Builds behind, Active PR (if exists)...
This is the codeflow diagram with the commits in question highlighted: