Skip to content

Conversation

@karajan1001
Copy link
Contributor

@karajan1001 karajan1001 commented Feb 6, 2023

Because for now pygit2 fetch didn't support file:// format on Windows, we removed this prefix. But didn't add it back after the fetch operation finished, and it makes the following dulwich backend goes wrong.

So here in the PR, we always create a new remote and delete it after the operation to make the remote config unchanged after the operation. Can be removed after #176 solved.

Related to the CI failure in https://github.com/iterative/dvc/actions/runs/4082287489/jobs/7037469526#logs

Because for now `pygit2` fetch didn't support `file://` format on
Windows, we removed this prefix. But didn't add it back after the
fetch operation finished, and it makes the following `dulwich`
backend goes wrong.

So here in the PR, we always create a new remote and delete it
after the operation to make the remote config unchanged after the
operation.
@karajan1001 karajan1001 self-assigned this Feb 6, 2023
@karajan1001 karajan1001 requested a review from pmrowla February 6, 2023 08:33
@karajan1001 karajan1001 added the bug Something isn't working label Feb 6, 2023
@pmrowla
Copy link
Contributor

pmrowla commented Feb 6, 2023

This is probably another indicator that we should really be using git_remote_add_anonymous (since we technically are breaking the config until we actually hit our finally: cleanup block)

@karajan1001 karajan1001 merged commit a2ba900 into treeverse:main Feb 6, 2023
@karajan1001 karajan1001 deleted the solve_remote_url_in_windows branch February 6, 2023 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants