"File synchronization failed" error while updating

[krishjan05]

When I am trying to updating a file on a live container, Visual studio code gives "File synchronization failed" error in the terminal. If I stop and run it again the changes are reflected correctly.

Visual Studio Code details:
Version: 1.43.2 (system setup)
Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50
Date: 2020-03-24T07:38:38.248Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4d7cb58c-7130-0a00-3d8b-2c3e35ef42ec
• Version Independent ID: be23b961-c5ba-d257-da0c-860377d5ce9b
• Content: Create a Kubernetes dev space: Visual Studio Code & .NET Core - Azure Dev Spaces
• Content Source: articles/dev-spaces/get-started-netcore.md
• Service: azure-dev-spaces
• GitHub Login: @zr-msft
• Microsoft Alias: zarhoads

[PramodValavala-MSFT]

@krishjan05 Is there a specific doc that you are referring to there? If so, could you please share the same?

[krishjan05]

I am following the steps in https://docs.microsoft.com/en-us/azure/dev-spaces/get-started-netcore

[PramodValavala-MSFT]

@krishjan05 Thanks for the question! We will review and get back to you!

[daniv-msft]

Thank you for reporting this issue. I couldn't reproduce this issue locally, and thus would need a bit more information to investigate.

Could you please attach to this issue the latest logs (azds-cli-*.txt and azds-sdk-*.txt) you can find in the Dev Spaces logs folder?

• For Windows: %TEMP%/Azure Dev Spaces
• For OSX/Linux: $TMPDIR/Azure Dev Spaces

[krishjan05]

Azure_Dev_Spaces_CLI_20200325074522.log
Azure_Dev_Spaces_CLI_20200325074522_000_AzdsCLI.log

These are the 2 log file which I could find at the location specified.
Let me know if you need any more information.

[daniv-msft]

Thanks for your reply. It looks like the Azure logging is disabled on your machine, as you should have found there azds-cli-*.txt and azds-sdk-*.txt files.

Could you please:

• Open the file %UserProfile%\.azure\config
• Add this new configuration in the file:

[logging]
enable_log_file = yes

• Restart VS Code and reproduce the bug.
• Retrieve Azure Dev Spaces logs as mentioned above.

[krishjan05]

I enabled logging and tried the steps again. Following are the generated log files.

azds-cli-2020-03-28-12-26-37-172280.txt
azds-sdk-2020-03-28-12-26-38-172280.txt

[daniv-msft]

Thank you for your reply and providing these logs!
I had a look at them and the issue seems to be related to one of our components called DevHostAgent, that is used to synchronize files while you're debugging. A problem with this component would explain the issue you encounter.

Could you please retrieve the DevHostAgent logs, so that I can investigate further?

• Open the Kubernetes Dashboard for your cluster.
• Filter the resources by the namespace in which you deployed your code (for example, if your dev space is called "dev/krishna", the namespace to look for is "krishna").
• In this namespace, look for the webfrontend pod corresponding to the code you deployed.
• Click the "Exec" button to exec into this pod, and run the command "ps aux". You should see the azds-agent running:
  
• Run the command "cat ../tmp/devhostagent.log" so that we can get the DevHostAgent logs.
• Could you please provide me these logs?

Also, in order for me to understand better the context in which this happens:

• Does it reproduce consistently, or is it a transient issue?
• Did it work in the past? Is this a recent regression or was it always the case?
• Did you do any kubeconfig operations (switching from one cluster/namespace to another) when testing this? We recently had issues related to switching clusters/namespaces while keeping VS Code opened, and this could be related.

Thanks!

[daniv-msft]

@krishjan05 Another similar issue was opened recently, and has likely the same root cause: Azure/dev-spaces#306

After investigating, it seems to me that the root of the issue is related to using a .NET Core 3.1 project. I couldn't reproduce the issue with a .NET Core 2.2 project.
Could you please confirm that your project runs on .NET Core 3.1 as well?

[SamaraSoucy-MSFT]

Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.