gvfs-helper-client: remove odb check #306
Merged
Conversation
This file contains 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
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
jeffhostetler
approved these changes
Jan 14, 2021
This was referenced Jan 14, 2021
derrickstolee
added a commit
to microsoft/scalar
that referenced
this pull request
Jan 14, 2021
derrickstolee
added a commit
to microsoft/scalar
that referenced
this pull request
Jan 14, 2021
derrickstolee
added a commit
to microsoft/VFSForGit
that referenced
this pull request
Jan 15, 2021
dscho
pushed a commit
that referenced
this pull request
Mar 4, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
dscho
pushed a commit
that referenced
this pull request
Mar 4, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
dscho
pushed a commit
that referenced
this pull request
Mar 4, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
dscho
pushed a commit
that referenced
this pull request
Mar 5, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
dscho
pushed a commit
that referenced
this pull request
Mar 8, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
jeffhostetler
pushed a commit
that referenced
this pull request
Mar 15, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
jeffhostetler
pushed a commit
that referenced
this pull request
Mar 16, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
derrickstolee
added a commit
that referenced
this pull request
May 17, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
derrickstolee
added a commit
that referenced
this pull request
May 17, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
derrickstolee
added a commit
that referenced
this pull request
May 17, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
dscho
pushed a commit
that referenced
this pull request
May 21, 2021
This check verifies that the ODB matches what we supplied, but there are some subtleties around Windows path names that can cause inexact matches to be logically the same. Since this check is really intended only for debugging and development purposes, let's remove it for now as a quick workaround. This was originally part of #304, as I hit it more often in that effort. However, this was hit during the Scalar release process, so I'll need to generate new installers.
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.
This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.
This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.