VFS for Git background server access and credential expiration

VFS for Git acquires user credentials from git credentials helper, when it first clones and stores them. What happens when those credentials expire? (https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops shows PATs default expiration time as 90d)

When the mount process tries to communicate with the server, will get a 401 and will try to invoke git credential fill, it might, or might not work, depending on configured credentials helper. It will work, when credential helper is able to renew credentials without any user interaction, that's the best case. It might also work, if some UI popup shows up and asks the user to fill in their credentials, but could be very confusing to the user. In case if configured git credential helper relies on getting input from terminal, this will not work and whatever operation VFS for Git was trying to perform, will just fail.

Are there any plans to support such scenarios, by perhaps showing some UI message to the user, that VFS for Git mount has failed and is terminating and the user should run gvfs mount again to be able to use it?

Start by tracing the mount process when server communication returns 401 and how it invokes git credential fill. Review the documented credential-helper behaviors, including terminal input and UI renewal, then define the user-visible handling for an expired credential, such as reporting that the mount terminated and gvfs mount must be run again.