You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Can mutagen session reconnect itself if master host moves between networks. For example, during the day, my notebook moves between wired connection at work, wireless connection at work, vpn connection remotely.
I tried to not terminate session each time, as I did before (because terminating session tends to create artificial conflicts every time files change), but just wait for it to reconnect, but I get this:
Is there a way to not terminate session and reconnect while moving between networks, so that artificial conflicts are not created like in issue #180 ? Also, from time to time some sessions hang and cannot terminate at all like in issue #174 so there is actually no way to reconnect after network change without a reboot
The text was updated successfully, but these errors were encountered:
Mutagen will reconnect automatically if disconnected. That error message indicates that the connection was terminated abruptly, but Mutagen will continue trying to reconnect at 5 second intervals. If you want to force reconnection faster, you can use mutagen sync resume <session> or mutagen sync resume --all.
Hi! Can mutagen session reconnect itself if master host moves between networks. For example, during the day, my notebook moves between wired connection at work, wireless connection at work, vpn connection remotely.
I tried to not terminate session each time, as I did before (because terminating session tends to create artificial conflicts every time files change), but just wait for it to reconnect, but I get this:
Is there a way to not terminate session and reconnect while moving between networks, so that artificial conflicts are not created like in issue #180 ? Also, from time to time some sessions hang and cannot terminate at all like in issue #174 so there is actually no way to reconnect after network change without a reboot
The text was updated successfully, but these errors were encountered: