Liubov Dmitrieva 1bf3ccfd91 cloudsync / infinitepush - add background to the secondary store after both pushbackup / cloud sync ... Summary: If the cloud sync or pushbackup commands start in background themselves, it will trigger a new background command to back up to the secondary afterwards. Note that for cloud sync, for the secondary store we trigger pushbackup command, not cloud sync. If should be fine. We don't backup duplicates as we always check with the server first what is already backup. To call pushback looks simpler as it doesn't involve all the complexity of cloud sync, and basically we just need to backup to the secondary. Reviewed By: markbt Differential Revision: D14578770 fbshipit-source-id: f81a50fd76e64f2d77d8d7004b201fcfe8a090d2		2019-03-22 10:41:13 -07:00
..
__init__.py	commitcloud: deprecate filtration of the push side	2019-03-21 10:27:13 -07:00
baseservice.py	commit cloud code clean up	2019-03-14 10:41:48 -07:00
commitcloudcommands.py	cloudsync / infinitepush - add background to the secondary store after both pushbackup / cloud sync	2019-03-22 10:41:13 -07:00
commitcloudcommon.py	codemod: import from the edenscm package	2019-01-29 17:25:32 -08:00
commitcloudutil.py	codemod: import from the edenscm package	2019-01-29 17:25:32 -08:00
httpsservice.py	commit cloud code clean up	2019-03-14 10:41:48 -07:00
localservice.py	commit cloud code clean up	2019-03-14 10:41:48 -07:00
service.py	codemod: import from the edenscm package	2019-01-29 17:25:32 -08:00
state.py	add logic for safe switching cloud sync between Mercurial and Mononoke and back	2019-03-21 09:02:23 -07:00
workspace.py	codemod: import from the edenscm package	2019-01-29 17:25:32 -08:00