This repository was archived by the owner on Dec 5, 2024. It is now read-only.
Attaching to GitUserCache events at a time when they might actually be fired #574
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.
Initial access of
EntryPoint.Envrionment
marks the start of the program and causes the construction of theApplicationManager
.In this bug, during the construction of
ApplicationManager
an access tocacheContainer.GitUserCache
causes construction of aManagedCacheBase<T>
object.This object requires information about the current environment. Which causes a re-entrant call into
EntryPoint.Environment
before the initial call has completed.The bug can be identified by grabbing a stack trace of when
ApplicationManager
is being constructed, and looking for the cycle in the stack trace.