On 2/28/2022 11:59 AM, Patrick Steinhardt wrote: > On Mon, Feb 28, 2022 at 11:23:38AM -0500, Derrick Stolee wrote: >> On 2/28/2022 10:18 AM, Patrick Steinhardt wrote: >>> I haven't yet found the time to dig deeper into why this is happening. >>> While the repository is publicly accessible at [1], unfortunately the >>> bug seems to be triggered by a commit that's only kept alive by an >>> internal reference. >>> >>> Patrick >>> >>> [1]: https://gitlab.com/gitlab-com/www-gitlab-com.git >> >> Thanks for including this information. Just to be clear: did you >> include patch 4 in your tests, or not? Patch 4 includes a fix >> related to overflow values, so it would be helpful to know if you >> found a _different_ bug or if it is the same one. >> >> Thanks, >> -Stolee > > I initially only applied the first three patches, but after having hit > the fatal error I also applied the rest of this series to have a look at > whether it is indeed fixed already by one of your later patches. The > error remains the same though. Thanks for this extra context. Is this a commit-graph that you wrote with the first three patches and then you get an error when reading it? Do you get the same error when deleting that file and rewriting it with all patches included? Thanks, -Stolee
