facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-06 23:07:18 +03:00
Code Issues Projects Releases Wiki Activity
a8f232e0ab
sapling/eden/scm/tests/test-commitcloud-sync-omission.t

852 lines
26 KiB
Perl
Raw Normal View History

mark all tests requiring Python 2 Summary: This diff marks **ALL** mercurial tests requiring Python 2 feature. After you fixes some tests, simply remove the `py2` feature requirement and that tests will be continuously run after your diff is landed. To bypass this feature requirement, run the tests command with `HGTEST_FORCE_PY2=1`. For example: ``` HGTEST_FORCE_PY2=1 buck test //eden/scm/tests:hg_run_tests ``` or ``` HGTEST_FORCE_PY2=1 python run-tests.py ``` ---- Basically this diff are created with the following commands: ``` $ sed -i 's/import feature\(.*\)$/import feature\1\n\nfeature.require(["py2"])/' test-*-t.py $ sed -i '1s/^/#require py2\n/' test-*.t $ ls | grep -P "^test.*(?<\!-t)\.py$" > list && vim -p $(cat list) # manually adding feature requires for these Python tests. ``` (Note: this ignores all push blocking failures!) ignore-conflict-markers Reviewed By: singhsrb Differential Revision: D19655148 fbshipit-source-id: 985e3ccb4010cc559049f1d89f8909bc2d9b5e20
2020-01-31 05:40:49 +03:00
#require py2
tests: enable chg for 572 tests Summary: Add `#chg-compatible` to 572 tests that seem to pass with chg enabled. This should make them run faster. Reviewed By: xavierd Differential Revision: D18870507 fbshipit-source-id: fe895e733efffc9286cd3d17c7a156c803124395
2019-12-10 02:24:31 +03:00
#chg-compatible
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
#require jq
tests: update tests-[a-h]*.t to use new tinit features Reviewed By: quark-zju Differential Revision: D19457677 fbshipit-source-id: 9f121837dfc6bf98ff4525c6535496b292409844
2020-01-20 13:42:49 +03:00
$ configure dummyssh evolution
tests: use disable treemanifest in place of setconfig Summary: Use `disable treemanifest` in place of `setconfig extensions.treemanifest=!` Reviewed By: quark-zju Differential Revision: D19457678 fbshipit-source-id: 47c8b3c4f4ed5cfc97275ca67afab4a86ffe7f0d
2020-01-20 13:42:49 +03:00
$ disable treemanifest
tests: update tests-[a-h]*.t to use new tinit features Reviewed By: quark-zju Differential Revision: D19457677 fbshipit-source-id: 9f121837dfc6bf98ff4525c6535496b292409844
2020-01-20 13:42:49 +03:00
$ enable amend commitcloud infinitepush rebase remotenames share smartlog
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
tests: update tests-[a-h]*.t to use new tinit features Reviewed By: quark-zju Differential Revision: D19457677 fbshipit-source-id: 9f121837dfc6bf98ff4525c6535496b292409844
2020-01-20 13:42:49 +03:00
$ setconfig infinitepush.branchpattern="re:scratch/.*"
$ setconfig infinitepushbackup.enablestatus=true
$ setconfig commitcloud.hostname=testhost commitcloud.max_sync_age=14
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
treemanifest: set reponame and cachepath by default Summary: We want to migrate the tests to run using treemanifest. As part of that, we need remotefilelog reponame and cachepath to always be set. So let's set that for all tests now. Differential Revision: D15030250 fbshipit-source-id: 4147997ceebb1294deb322bdbef77b6caab18c44
2019-05-10 19:56:31 +03:00
$ setconfig remotefilelog.reponame=server
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ hg init server
$ cd server
$ cat >> .hg/hgrc << EOF
> [infinitepush]
> server = yes
> indextype = disk
> storetype = disk
> reponame = testrepo
> EOF
$ touch base
$ hg commit -Aqm base
$ hg phase -p .
$ cd ..
Make shared part of config
$ cat >> shared.rc << EOF
> [commitcloud]
> servicetype = local
> servicelocation = $TESTTMP
> user_token_path = $TESTTMP
> auth_help = visit https://localhost/oauth to generate a registration token
> education_page = https://someurl.com/wiki/CommitCloud
> owner_team = The Test Team @ FB
> EOF
Utility script to dump commit cloud metadata
$ cat > dumpcommitcloudmetadata.py <<EOF
> import json
> ccmd = json.load(open("$TESTTMP/commitcloudservicedb"))
> print("version: %s" % ccmd["version"])
> print("bookmarks:")
> for bookmark, node in sorted(ccmd["bookmarks"].items()):
> print(" %s => %s" % (bookmark, node))
> print("heads:")
> for head in (ccmd["heads"]):
> print(" %s" % head)
> EOF
Utility function to run HG with a fake date
$ hgfakedate() {
> fakedate="$1"
> shift
> hg --config extensions.fakedate="$TESTDIR/fakedate.py" --config fakedate.date="$fakedate" "$@"
> }
Make a clone of the server
$ hg clone ssh://user@dummy/server client1 -q
$ cd client1
$ cat ../shared.rc >> .hg/hgrc
$ hg cloud auth -t xxxxxx
setting authentication token
authentication successful
Connect the first client
$ hg cloud join
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: this repository is now connected to the 'user/test/default' workspace for the 'server' repo
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
Make some stacks with various dates. We will use Feb 1990 for these tests.
- Old stack
$ hg up -q 0
$ touch oldstack-feb1
$ hg commit -Aqm oldstack-feb1 --config devel.default-date="1990-02-01T00:00Z"
$ hg book -i oldbook
$ touch oldstack-feb4
$ hg commit -Aqm oldstack-feb4 --config devel.default-date="1990-02-04T12:00Z"
- Middle stack
$ hg up -q 0
$ touch midstack-feb7
$ hg commit -Aqm midstack-feb7 --config devel.default-date="1990-02-07T00:00Z"
$ hg book -i midbook
$ touch midstack-feb9
$ hg commit -Aqm midstack-feb9 --config devel.default-date="1990-02-09T12:00Z"
- New stack
$ hg up -q 0
$ touch newstack-feb13
$ hg commit -Aqm newstack-feb13 --config devel.default-date="1990-02-13T00:00Z"
$ hg book -i newbook
$ touch newstack-feb15
$ hg commit -Aqm newstack-feb15 --config devel.default-date="1990-02-15T12:00Z"
Write node metadata out to disk (this is loaded by the commit cloud local service
implementation)
$ hg log -r "all()" -Tjson >> $TESTTMP/nodedata
Sync these to commit cloud - they all get pushed even though they are old
$ hgfakedate 1990-02-28T00:00Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
backing up stack rooted at 1f9ebd6d1390
remote: pushing 2 commits:
remote: 1f9ebd6d1390 oldstack-feb1
remote: d16408588b2d oldstack-feb4
backing up stack rooted at 1c1b7955142c
remote: pushing 2 commits:
remote: 1c1b7955142c midstack-feb7
remote: d133b886da68 midstack-feb9
backing up stack rooted at 56a352317b67
remote: pushing 2 commits:
remote: 56a352317b67 newstack-feb13
remote: 7f958333fe84 newstack-feb15
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
@ 6: 7f958333fe84 draft 'newstack-feb15'
|
o 5: 56a352317b67 draft 'newstack-feb13' newbook
|
| o 4: d133b886da68 draft 'midstack-feb9'
| |
| o 3: 1c1b7955142c draft 'midstack-feb7' midbook
|/
| o 2: d16408588b2d draft 'oldstack-feb4'
| |
| o 1: 1f9ebd6d1390 draft 'oldstack-feb1' oldbook
|/
o 0: df4f53cec30a public 'base'
$ python $TESTTMP/dumpcommitcloudmetadata.py
version: 2
bookmarks:
midbook => 1c1b7955142cd8a3beec705c9cca9d775ecb0fa8
newbook => 56a352317b67ae3d5abd5f6c71ec0df3aa98fe97
oldbook => 1f9ebd6d1390ebc603e401171eda0c444a0f8754
heads:
d16408588b2d047410f99c45e425bf97923e28f2
d133b886da6874fe25998d26ae1b2b8528b07c59
7f958333fe845fe5cbc60d9d96e3d68a262d684c
Create a new client that isn't connected yet
$ cd ..
$ hg clone ssh://user@dummy/server client2 -q
$ cat shared.rc >> client2/.hg/hgrc
Connect to commit cloud
$ cd client2
$ hgfakedate 1990-02-20T16:00Z cloud join
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: this repository is now connected to the 'user/test/default' workspace for the 'server' repo
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
omitting heads that are older than 14 days:
d16408588b2d from Sun Feb 04 12:00:00 1990 +0000
pulling d133b886da68
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 2 changes to 2 files
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
pulling 7f958333fe84
pulling from ssh://user@dummy/server
searching for changes
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
adding changesets
adding manifests
adding file changes
changegroup: do not show "(+/- ? heads)" Summary: In an upcoming change we'll replace `cl.heads()` with `repo.heads()`. In changegroup code path the repo can be in an inconsistent state (ex. a bookmark refers to an unknown commit) which breaks `repo.heads()`. Since the whole purpose of the heads calculation is just to show `(+/- ? heads)`, which does not affect any real features, let's just remove it. Reviewed By: markbt Differential Revision: D18366735 fbshipit-source-id: 893be2cec0c32b64a80b3ef4ca65b69f8ed76b27
2019-11-07 21:50:10 +03:00
added 2 changesets with 2 changes to 2 files
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
1f9ebd6d1390ebc603e401171eda0c444a0f8754 not found, omitting oldbook bookmark
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
o 4: 7f958333fe84 draft 'newstack-feb15'
|
o 3: 56a352317b67 draft 'newstack-feb13' newbook
|
| o 2: d133b886da68 draft 'midstack-feb9'
| |
| o 1: 1c1b7955142c draft 'midstack-feb7' midbook
|/
@ 0: df4f53cec30a public 'base'
Create a new commit
$ hg up 0
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ touch client2-file1
$ hg commit -Aqm client2-feb28 --config devel.default-date="1990-02-28T01:00Z"
$ (cat $TESTTMP/nodedata ; hg log -r . -Tjson) | jq -s add > $TESTTMP/nodedata.new
$ mv $TESTTMP/nodedata.new $TESTTMP/nodedata
$ hgfakedate 1990-02-28T01:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
backing up stack rooted at ff52de2f760c
remote: pushing 1 commit:
remote: ff52de2f760c client2-feb28
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
Sync these commits to the first client - it has everything
$ cd ../client1
$ hgfakedate 1990-02-28T01:02Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
pulling ff52de2f760c
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
changegroup: do not show "(+/- ? heads)" Summary: In an upcoming change we'll replace `cl.heads()` with `repo.heads()`. In changegroup code path the repo can be in an inconsistent state (ex. a bookmark refers to an unknown commit) which breaks `repo.heads()`. Since the whole purpose of the heads calculation is just to show `(+/- ? heads)`, which does not affect any real features, let's just remove it. Reviewed By: markbt Differential Revision: D18366735 fbshipit-source-id: 893be2cec0c32b64a80b3ef4ca65b69f8ed76b27
2019-11-07 21:50:10 +03:00
added 1 changesets with 1 changes to 1 files
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
o 7: ff52de2f760c draft 'client2-feb28'
|
| @ 6: 7f958333fe84 draft 'newstack-feb15'
| |
| o 5: 56a352317b67 draft 'newstack-feb13' newbook
|/
| o 4: d133b886da68 draft 'midstack-feb9'
| |
| o 3: 1c1b7955142c draft 'midstack-feb7' midbook
|/
| o 2: d16408588b2d draft 'oldstack-feb4'
| |
| o 1: 1f9ebd6d1390 draft 'oldstack-feb1' oldbook
|/
o 0: df4f53cec30a public 'base'
Second client can still sync
$ cd ../client2
$ hgfakedate 1990-02-28T01:22Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
@ 5: ff52de2f760c draft 'client2-feb28'
|
| o 4: 7f958333fe84 draft 'newstack-feb15'
| |
| o 3: 56a352317b67 draft 'newstack-feb13' newbook
|/
| o 2: d133b886da68 draft 'midstack-feb9'
| |
| o 1: 1c1b7955142c draft 'midstack-feb7' midbook
|/
o 0: df4f53cec30a public 'base'
$ python $TESTTMP/dumpcommitcloudmetadata.py
commitcloud: don't bump version when there are omissions Summary: Stop comparing the local heads and bookmarks with the full cloud heads and bookmarks when some heads or bookmarks have been omitted. Since they're omitted, they won't be there. Reviewed By: liubov-dmitrieva Differential Revision: D13214275 fbshipit-source-id: 35a897f053f58d0793d384ff60b8202e80aec0c7
2018-11-27 18:18:29 +03:00
version: 3
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
bookmarks:
midbook => 1c1b7955142cd8a3beec705c9cca9d775ecb0fa8
newbook => 56a352317b67ae3d5abd5f6c71ec0df3aa98fe97
oldbook => 1f9ebd6d1390ebc603e401171eda0c444a0f8754
heads:
d16408588b2d047410f99c45e425bf97923e28f2
d133b886da6874fe25998d26ae1b2b8528b07c59
7f958333fe845fe5cbc60d9d96e3d68a262d684c
ff52de2f760c67fa6f89273ca7f770396a3c81c4
Add a new commit to a stack on the first client
$ cd ../client1
$ touch newstack-feb28
$ hg commit -Aqm newstack-feb28 --config devel.default-date="1990-02-28T02:00Z"
$ (cat $TESTTMP/nodedata ; hg log -r . -Tjson) | jq -s add > $TESTTMP/nodedata.new
$ mv $TESTTMP/nodedata.new $TESTTMP/nodedata
$ hgfakedate 1990-02-28T02:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
backing up stack rooted at 56a352317b67
remote: pushing 3 commits:
remote: 56a352317b67 newstack-feb13
remote: 7f958333fe84 newstack-feb15
remote: 46f8775ee5d4 newstack-feb28
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ python $TESTTMP/dumpcommitcloudmetadata.py
commitcloud: don't bump version when there are omissions Summary: Stop comparing the local heads and bookmarks with the full cloud heads and bookmarks when some heads or bookmarks have been omitted. Since they're omitted, they won't be there. Reviewed By: liubov-dmitrieva Differential Revision: D13214275 fbshipit-source-id: 35a897f053f58d0793d384ff60b8202e80aec0c7
2018-11-27 18:18:29 +03:00
version: 4
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
bookmarks:
midbook => 1c1b7955142cd8a3beec705c9cca9d775ecb0fa8
newbook => 56a352317b67ae3d5abd5f6c71ec0df3aa98fe97
oldbook => 1f9ebd6d1390ebc603e401171eda0c444a0f8754
heads:
d16408588b2d047410f99c45e425bf97923e28f2
d133b886da6874fe25998d26ae1b2b8528b07c59
ff52de2f760c67fa6f89273ca7f770396a3c81c4
46f8775ee5d479eed945b5186929bd046f116176
Second client syncs that in, but still leaves the old commits missing
$ cd ../client2
$ hgfakedate 1990-02-28T02:02Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
omitting heads that are older than 14 days:
d16408588b2d from Sun Feb 04 12:00:00 1990 +0000
pulling 46f8775ee5d4
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 3 files
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
o 6: 46f8775ee5d4 draft 'newstack-feb28'
|
| @ 5: ff52de2f760c draft 'client2-feb28'
| |
o | 4: 7f958333fe84 draft 'newstack-feb15'
| |
o | 3: 56a352317b67 draft 'newstack-feb13' newbook
|/
| o 2: d133b886da68 draft 'midstack-feb9'
| |
| o 1: 1c1b7955142c draft 'midstack-feb7' midbook
|/
o 0: df4f53cec30a public 'base'
$ python $TESTTMP/dumpcommitcloudmetadata.py
commitcloud: don't bump version when there are omissions Summary: Stop comparing the local heads and bookmarks with the full cloud heads and bookmarks when some heads or bookmarks have been omitted. Since they're omitted, they won't be there. Reviewed By: liubov-dmitrieva Differential Revision: D13214275 fbshipit-source-id: 35a897f053f58d0793d384ff60b8202e80aec0c7
2018-11-27 18:18:29 +03:00
version: 4
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
bookmarks:
midbook => 1c1b7955142cd8a3beec705c9cca9d775ecb0fa8
newbook => 56a352317b67ae3d5abd5f6c71ec0df3aa98fe97
oldbook => 1f9ebd6d1390ebc603e401171eda0c444a0f8754
heads:
d16408588b2d047410f99c45e425bf97923e28f2
d133b886da6874fe25998d26ae1b2b8528b07c59
ff52de2f760c67fa6f89273ca7f770396a3c81c4
46f8775ee5d479eed945b5186929bd046f116176
commitcloud: exclude omitted heads from infinitepush backup state Summary: Commit cloud maintains the infinitepush backup state to match what it has synced to commit cloud. It should only include locally backed-up heads. When syncing with the server and omitting some heads, don't include the omitted ones. Reviewed By: liubov-dmitrieva Differential Revision: D13719477 fbshipit-source-id: 817c1a73a34af6b5550f6254e2b08d01283760a5
2019-01-18 03:05:45 +03:00
Commit cloud keeps infinitepush backup state up-to-date. Ensure it hasn't included the omitted head.
infinitepush backup: separate depends on the remote infinitepush path Summary: We are going to support 2 different backends of Commit Cloud: Mercurial and Mononoke. Each of them should maintain local backup state separately. Output of some tests have been slightly changes, this is because a separate backup state, the same error appears earlier when we are trying the backup stacks. The idea is to have separate backup states for different remote paths, but there will be only one cloud sync state for the current source of truth. We could include there the remote path and then validate that cloud sync state is correct if the remote path has been changed. However, for backup states it is much easier to have them separately (and we will backup in 2 places) Reviewed By: markbt Differential Revision: D14138496 fbshipit-source-id: 0a7a763a395be5456cbd724bff7ebc069f03fb0e
2019-02-21 02:20:11 +03:00
$ grep -r d16408588b2d047410f99c45e425bf97923e28f2 .hg/infinitepushbackups
commitcloud: exclude omitted heads from infinitepush backup state Summary: Commit cloud maintains the infinitepush backup state to match what it has synced to commit cloud. It should only include locally backed-up heads. When syncing with the server and omitting some heads, don't include the omitted ones. Reviewed By: liubov-dmitrieva Differential Revision: D13719477 fbshipit-source-id: 817c1a73a34af6b5550f6254e2b08d01283760a5
2019-01-18 03:05:45 +03:00
[1]
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
First client add a new commit to the old stack
$ cd ../client1
$ hg up 2
2 files updated, 0 files merged, 3 files removed, 0 files unresolved
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ touch oldstack-mar4
$ hg commit -Aqm oldstack-mar4 --config devel.default-date="1990-03-04T03:00Z"
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ (cat $TESTTMP/nodedata ; hg log -r . -Tjson) | jq -s add > $TESTTMP/nodedata.new
$ mv $TESTTMP/nodedata.new $TESTTMP/nodedata
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-04T03:02Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
backing up stack rooted at 1f9ebd6d1390
remote: pushing 3 commits:
remote: 1f9ebd6d1390 oldstack-feb1
remote: d16408588b2d oldstack-feb4
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
remote: 2b8dce7bd745 oldstack-mar4
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ python $TESTTMP/dumpcommitcloudmetadata.py
commitcloud: don't bump version when there are omissions Summary: Stop comparing the local heads and bookmarks with the full cloud heads and bookmarks when some heads or bookmarks have been omitted. Since they're omitted, they won't be there. Reviewed By: liubov-dmitrieva Differential Revision: D13214275 fbshipit-source-id: 35a897f053f58d0793d384ff60b8202e80aec0c7
2018-11-27 18:18:29 +03:00
version: 5
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
bookmarks:
midbook => 1c1b7955142cd8a3beec705c9cca9d775ecb0fa8
newbook => 56a352317b67ae3d5abd5f6c71ec0df3aa98fe97
oldbook => 1f9ebd6d1390ebc603e401171eda0c444a0f8754
heads:
d133b886da6874fe25998d26ae1b2b8528b07c59
ff52de2f760c67fa6f89273ca7f770396a3c81c4
46f8775ee5d479eed945b5186929bd046f116176
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
2b8dce7bd745e54f2cea9d8c630d97264537cbad
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
Second client syncs the old stack in, and now has the bookmark
$ cd ../client2
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-04T03:03Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
pulling 2b8dce7bd745
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
changegroup: do not show "(+/- ? heads)" Summary: In an upcoming change we'll replace `cl.heads()` with `repo.heads()`. In changegroup code path the repo can be in an inconsistent state (ex. a bookmark refers to an unknown commit) which breaks `repo.heads()`. Since the whole purpose of the heads calculation is just to show `(+/- ? heads)`, which does not affect any real features, let's just remove it. Reviewed By: markbt Differential Revision: D18366735 fbshipit-source-id: 893be2cec0c32b64a80b3ef4ca65b69f8ed76b27
2019-11-07 21:50:10 +03:00
added 3 changesets with 3 changes to 3 files
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
o 9: 2b8dce7bd745 draft 'oldstack-mar4'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
o 8: d16408588b2d draft 'oldstack-feb4'
|
o 7: 1f9ebd6d1390 draft 'oldstack-feb1' oldbook
|
| o 6: 46f8775ee5d4 draft 'newstack-feb28'
| |
+---@ 5: ff52de2f760c draft 'client2-feb28'
| |
| o 4: 7f958333fe84 draft 'newstack-feb15'
| |
| o 3: 56a352317b67 draft 'newstack-feb13' newbook
|/
| o 2: d133b886da68 draft 'midstack-feb9'
| |
| o 1: 1c1b7955142c draft 'midstack-feb7' midbook
|/
o 0: df4f53cec30a public 'base'
$ python $TESTTMP/dumpcommitcloudmetadata.py
commitcloud: don't bump version when there are omissions Summary: Stop comparing the local heads and bookmarks with the full cloud heads and bookmarks when some heads or bookmarks have been omitted. Since they're omitted, they won't be there. Reviewed By: liubov-dmitrieva Differential Revision: D13214275 fbshipit-source-id: 35a897f053f58d0793d384ff60b8202e80aec0c7
2018-11-27 18:18:29 +03:00
version: 5
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
bookmarks:
midbook => 1c1b7955142cd8a3beec705c9cca9d775ecb0fa8
newbook => 56a352317b67ae3d5abd5f6c71ec0df3aa98fe97
oldbook => 1f9ebd6d1390ebc603e401171eda0c444a0f8754
heads:
d133b886da6874fe25998d26ae1b2b8528b07c59
ff52de2f760c67fa6f89273ca7f770396a3c81c4
46f8775ee5d479eed945b5186929bd046f116176
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
2b8dce7bd745e54f2cea9d8c630d97264537cbad
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
Create a new client that isn't connected yet
$ cd ..
$ hg clone ssh://user@dummy/server client3 -q
$ cat shared.rc >> client3/.hg/hgrc
Connect to commit cloud
$ cd client3
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-05T12:00Z cloud join
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: this repository is now connected to the 'user/test/default' workspace for the 'server' repo
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
omitting heads that are older than 14 days:
d133b886da68 from Fri Feb 09 12:00:00 1990 +0000
pulling ff52de2f760c 46f8775ee5d4
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
adding changesets
adding manifests
adding file changes
changegroup: do not show "(+/- ? heads)" Summary: In an upcoming change we'll replace `cl.heads()` with `repo.heads()`. In changegroup code path the repo can be in an inconsistent state (ex. a bookmark refers to an unknown commit) which breaks `repo.heads()`. Since the whole purpose of the heads calculation is just to show `(+/- ? heads)`, which does not affect any real features, let's just remove it. Reviewed By: markbt Differential Revision: D18366735 fbshipit-source-id: 893be2cec0c32b64a80b3ef4ca65b69f8ed76b27
2019-11-07 21:50:10 +03:00
added 3 changesets with 3 changes to 3 files
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
pulling 2b8dce7bd745
pulling from ssh://user@dummy/server
searching for changes
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
adding changesets
adding manifests
adding file changes
changegroup: do not show "(+/- ? heads)" Summary: In an upcoming change we'll replace `cl.heads()` with `repo.heads()`. In changegroup code path the repo can be in an inconsistent state (ex. a bookmark refers to an unknown commit) which breaks `repo.heads()`. Since the whole purpose of the heads calculation is just to show `(+/- ? heads)`, which does not affect any real features, let's just remove it. Reviewed By: markbt Differential Revision: D18366735 fbshipit-source-id: 893be2cec0c32b64a80b3ef4ca65b69f8ed76b27
2019-11-07 21:50:10 +03:00
added 3 changesets with 3 changes to 3 files
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
1c1b7955142cd8a3beec705c9cca9d775ecb0fa8 not found, omitting midbook bookmark
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-05T12:00Z smartlog -T '{rev}: {node|short} {desc} {bookmarks}' --config infinitepushbackup.autobackup=true
o 7: 2b8dce7bd745 oldstack-mar4
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
commitcloud: print message in hg sl --all when commits are omitted Summary: When we have omitted syncing commits from the cloud workspace, give the user advice on what to do to fetch them if they run `hg sl --all`. Reviewed By: markbt Differential Revision: D13085505 fbshipit-source-id: 624ce6cbf4cb2194ab5ffbc09c1ac3e073932249
2018-11-21 16:59:36 +03:00
o 6: d16408588b2d oldstack-feb4
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
o 5: 1f9ebd6d1390 oldstack-feb1 oldbook
commitcloud: print message in hg sl --all when commits are omitted Summary: When we have omitted syncing commits from the cloud workspace, give the user advice on what to do to fetch them if they run `hg sl --all`. Reviewed By: markbt Differential Revision: D13085505 fbshipit-source-id: 624ce6cbf4cb2194ab5ffbc09c1ac3e073932249
2018-11-21 16:59:36 +03:00
|
| o 4: 46f8775ee5d4 newstack-feb28
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
| |
commitcloud: print message in hg sl --all when commits are omitted Summary: When we have omitted syncing commits from the cloud workspace, give the user advice on what to do to fetch them if they run `hg sl --all`. Reviewed By: markbt Differential Revision: D13085505 fbshipit-source-id: 624ce6cbf4cb2194ab5ffbc09c1ac3e073932249
2018-11-21 16:59:36 +03:00
| o 3: 7f958333fe84 newstack-feb15
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
| |
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
| o 2: 56a352317b67 newstack-feb13 newbook
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|/
commitcloud: print message in hg sl --all when commits are omitted Summary: When we have omitted syncing commits from the cloud workspace, give the user advice on what to do to fetch them if they run `hg sl --all`. Reviewed By: markbt Differential Revision: D13085505 fbshipit-source-id: 624ce6cbf4cb2194ab5ffbc09c1ac3e073932249
2018-11-21 16:59:36 +03:00
| o 1: ff52de2f760c client2-feb28
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|/
commitcloud: print message in hg sl --all when commits are omitted Summary: When we have omitted syncing commits from the cloud workspace, give the user advice on what to do to fetch them if they run `hg sl --all`. Reviewed By: markbt Differential Revision: D13085505 fbshipit-source-id: 624ce6cbf4cb2194ab5ffbc09c1ac3e073932249
2018-11-21 16:59:36 +03:00
@ 0: df4f53cec30a base
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
commitcloud: print message in hg sl --all when commits are omitted Summary: When we have omitted syncing commits from the cloud workspace, give the user advice on what to do to fetch them if they run `hg sl --all`. Reviewed By: markbt Differential Revision: D13085505 fbshipit-source-id: 624ce6cbf4cb2194ab5ffbc09c1ac3e073932249
2018-11-21 16:59:36 +03:00
hint[commitcloud-old-commits]: some older commits or bookmarks have not been synced to this repo
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
(run 'hg cloud sl' to see all of the commits in your workspace)
(run 'hg pull -r HASH' to fetch commits by hash)
(run 'hg cloud sync --full' to fetch everything - this may be slow)
commitcloud: print message in hg sl --all when commits are omitted Summary: When we have omitted syncing commits from the cloud workspace, give the user advice on what to do to fetch them if they run `hg sl --all`. Reviewed By: markbt Differential Revision: D13085505 fbshipit-source-id: 624ce6cbf4cb2194ab5ffbc09c1ac3e073932249
2018-11-21 16:59:36 +03:00
hint[hint-ack]: use 'hg hint --ack commitcloud-old-commits' to silence these hints
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
Move one of these bookmarks in the first client.
$ cd ../client1
$ hg book -f -r 4 oldbook
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-05T12:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
Do a sync in the new client - the bookmark is left where it was
$ cd ../client3
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-05T12:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
omitting heads that are older than 14 days:
d133b886da68 from Fri Feb 09 12:00:00 1990 +0000
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
d133b886da6874fe25998d26ae1b2b8528b07c59 not found, omitting oldbook bookmark
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
o 7: 2b8dce7bd745 draft 'oldstack-mar4'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
o 6: d16408588b2d draft 'oldstack-feb4'
|
commitcloud: remove omitted bookmarks that are available locally Summary: When syncing, if a locally-available bookmark is synced to a new commit that has been omitted, remove the local bookmark to ensure that the next cloud sync doesn't move the bookmark back to where it used to be. Reviewed By: mitrandir77 Differential Revision: D15414172 fbshipit-source-id: 71aaa2d89f734e4c575c24da2c0ef6b59ca4deaa
2019-05-22 00:29:10 +03:00
o 5: 1f9ebd6d1390 draft 'oldstack-feb1'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
| o 4: 46f8775ee5d4 draft 'newstack-feb28'
| |
| o 3: 7f958333fe84 draft 'newstack-feb15'
| |
| o 2: 56a352317b67 draft 'newstack-feb13' newbook
|/
| o 1: ff52de2f760c draft 'client2-feb28'
|/
@ 0: df4f53cec30a public 'base'
Move the bookmark locally - this still gets synced ok.
$ hg book -f -r 3 oldbook
$ tglogp
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
o 7: 2b8dce7bd745 draft 'oldstack-mar4'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
o 6: d16408588b2d draft 'oldstack-feb4'
|
o 5: 1f9ebd6d1390 draft 'oldstack-feb1'
|
| o 4: 46f8775ee5d4 draft 'newstack-feb28'
| |
| o 3: 7f958333fe84 draft 'newstack-feb15' oldbook
| |
| o 2: 56a352317b67 draft 'newstack-feb13' newbook
|/
| o 1: ff52de2f760c draft 'client2-feb28'
|/
@ 0: df4f53cec30a public 'base'
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-05T12:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ cd ../client1
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-05T12:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
@ 9: 2b8dce7bd745 draft 'oldstack-mar4'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
| o 8: 46f8775ee5d4 draft 'newstack-feb28'
| |
| | o 7: ff52de2f760c draft 'client2-feb28'
| | |
| o | 6: 7f958333fe84 draft 'newstack-feb15' oldbook
| | |
| o | 5: 56a352317b67 draft 'newstack-feb13' newbook
| |/
| | o 4: d133b886da68 draft 'midstack-feb9'
| | |
| | o 3: 1c1b7955142c draft 'midstack-feb7' midbook
| |/
o | 2: d16408588b2d draft 'oldstack-feb4'
| |
o | 1: 1f9ebd6d1390 draft 'oldstack-feb1'
|/
o 0: df4f53cec30a public 'base'
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
A full sync pulls the old commits in
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ cd ../client3
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ hgfakedate 1990-03-05T12:01Z cloud sync --full
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
pulling d133b886da68
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
changegroup: do not show "(+/- ? heads)" Summary: In an upcoming change we'll replace `cl.heads()` with `repo.heads()`. In changegroup code path the repo can be in an inconsistent state (ex. a bookmark refers to an unknown commit) which breaks `repo.heads()`. Since the whole purpose of the heads calculation is just to show `(+/- ? heads)`, which does not affect any real features, let's just remove it. Reviewed By: markbt Differential Revision: D18366735 fbshipit-source-id: 893be2cec0c32b64a80b3ef4ca65b69f8ed76b27
2019-11-07 21:50:10 +03:00
added 2 changesets with 2 changes to 2 files
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
$ tglogp
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
o 9: d133b886da68 draft 'midstack-feb9'
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
o 8: 1c1b7955142c draft 'midstack-feb7' midbook
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
|
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
| o 7: 2b8dce7bd745 draft 'oldstack-mar4'
| |
| o 6: d16408588b2d draft 'oldstack-feb4'
| |
| o 5: 1f9ebd6d1390 draft 'oldstack-feb1'
|/
commitcloud: omit older commits when pulling during sync Summary: Add a new config option: `commitcloud.max_sync_age`. When set, commit cloud will not pull in any commits that are older than this when it is joining or syncing. The commits are still nominally in the cloud workspace, we just save join or sync time by not including the commits. Reviewed By: liubov-dmitrieva Differential Revision: D13062470 fbshipit-source-id: 17a4bdb4095766a83a4bf6d4151ae86b39edf59c
2018-11-15 20:48:14 +03:00
| o 4: 46f8775ee5d4 draft 'newstack-feb28'
| |
| o 3: 7f958333fe84 draft 'newstack-feb15' oldbook
| |
| o 2: 56a352317b67 draft 'newstack-feb13' newbook
|/
| o 1: ff52de2f760c draft 'client2-feb28'
|/
@ 0: df4f53cec30a public 'base'
commitcloud: fix omission logic if a bookmark was removed Reviewed By: markbt Differential Revision: D13196329 fbshipit-source-id: 78fd305dc9520f735383cd6e86bf020cb891c02e
2018-11-27 15:18:51 +03:00
Create a new client that isn't connected yet
$ cd ..
$ hg clone ssh://user@dummy/server client4 -q
$ cat shared.rc >> client4/.hg/hgrc
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
A part sync omitting everything
commitcloud: fix omission logic if a bookmark was removed Reviewed By: markbt Differential Revision: D13196329 fbshipit-source-id: 78fd305dc9520f735383cd6e86bf020cb891c02e
2018-11-27 15:18:51 +03:00
$ cd ./client4
$ hgfakedate 1990-04-01T12:01Z cloud join
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: this repository is now connected to the 'user/test/default' workspace for the 'server' repo
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
omitting heads that are older than 14 days:
d133b886da68 from Fri Feb 09 12:00:00 1990 +0000
ff52de2f760c from Wed Feb 28 01:00:00 1990 +0000
46f8775ee5d4 from Wed Feb 28 02:00:00 1990 +0000
2b8dce7bd745 from Sun Mar 04 03:00:00 1990 +0000
commitcloud: fix omission logic if a bookmark was removed Reviewed By: markbt Differential Revision: D13196329 fbshipit-source-id: 78fd305dc9520f735383cd6e86bf020cb891c02e
2018-11-27 15:18:51 +03:00
* not found, omitting * bookmark (glob)
* not found, omitting * bookmark (glob)
* not found, omitting * bookmark (glob)
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: fix omission logic if a bookmark was removed Reviewed By: markbt Differential Revision: D13196329 fbshipit-source-id: 78fd305dc9520f735383cd6e86bf020cb891c02e
2018-11-27 15:18:51 +03:00
$ tglogp
@ 0: df4f53cec30a public 'base'
Remove some of the bookmarks
$ cd ../client1
$ hg book --delete newbook
$ hg book --delete oldbook
$ hg cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: fix omission logic if a bookmark was removed Reviewed By: markbt Differential Revision: D13196329 fbshipit-source-id: 78fd305dc9520f735383cd6e86bf020cb891c02e
2018-11-27 15:18:51 +03:00
Check that it doesn't break cloud sync
$ cd ../client4
$ hgfakedate 1990-04-01T12:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
omitting heads that are older than 14 days:
d133b886da68 from Fri Feb 09 12:00:00 1990 +0000
ff52de2f760c from Wed Feb 28 01:00:00 1990 +0000
46f8775ee5d4 from Wed Feb 28 02:00:00 1990 +0000
2b8dce7bd745 from Sun Mar 04 03:00:00 1990 +0000
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: fix omission logic if a bookmark was removed Reviewed By: markbt Differential Revision: D13196329 fbshipit-source-id: 78fd305dc9520f735383cd6e86bf020cb891c02e
2018-11-27 15:18:51 +03:00
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
Pull in some of the commits by setting max age manually
$ hgfakedate 1990-04-01T12:01Z cloud sync --config commitcloud.max_sync_age=30
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
omitting heads that are older than 30 days:
d133b886da68 from Fri Feb 09 12:00:00 1990 +0000
ff52de2f760c from Wed Feb 28 01:00:00 1990 +0000
46f8775ee5d4 from Wed Feb 28 02:00:00 1990 +0000
pulling 2b8dce7bd745
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
added 3 changesets with 3 changes to 3 files
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ tglogp
o 3: 2b8dce7bd745 draft 'oldstack-mar4'
|
o 2: d16408588b2d draft 'oldstack-feb4'
|
o 1: 1f9ebd6d1390 draft 'oldstack-feb1'
|
@ 0: df4f53cec30a public 'base'
Create a bookmark with the same name as an omitted bookmark
$ hg book -r tip midbook
$ hgfakedate 1990-04-01T12:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: pull heads in small groups Summary: When pulling heads from commit cloud during sync, pull them in small groups of heads from around the same time, to prevent overloading the server when pulling a large number of heads. Reviewed By: mitrandir77 Differential Revision: D15317184 fbshipit-source-id: 5e69eb970b18292a4f5d643b25fac80c90c5d537
2019-05-20 16:11:59 +03:00
omitting heads that are older than 14 days:
d133b886da68 from Fri Feb 09 12:00:00 1990 +0000
ff52de2f760c from Wed Feb 28 01:00:00 1990 +0000
46f8775ee5d4 from Wed Feb 28 02:00:00 1990 +0000
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
Sync these changes to client3 - the deleted bookmarks are removed and the
other bookmark is treated like a move.
$ cd ../client3
$ hgfakedate 1990-04-01T12:01Z cloud sync
commitcloud: use component for status and exceptions Summary: Set the `component` to `"commitcloud"` for commit cloud statuses and messages, rather than using custom highlight functions. Reviewed By: quark-zju Differential Revision: D15201944 fbshipit-source-id: 7635942a5ca029209711a2b89c32cc5fd677d22f
2019-05-09 16:50:03 +03:00
commitcloud: synchronizing 'server' with 'user/test/default'
commitcloud: commits synchronized
commitcloud: trigger a backup to a secondary storage after cloud sync in the background Summary: We can't run in parallel at the moment as the log file and the lock file are shared. Every path maintains independent backup state (the previous diff). The secondary backup state doesn't affect smartlog (only the main one) The issue with this approach is that we maintain backup lock a bit longer. Unfortunately, the progress in smartlog doesn't show anything about the second backup. I added 'finished', it makes it easier to compare in the logs. Reviewed By: markbt Differential Revision: D14149399 fbshipit-source-id: f90e8aac6cb8dee53d5c7468bd6adba067e13362
2019-02-21 02:20:11 +03:00
finished in * (glob)
commitcloud: pull in changes if maxage changes or full is specified Summary: If full is specified, or the maxage config option changes from one sync to another, we need to actually pull in the new commits. Since the version number won't necessarily have changed, we need to request a full copy of the cloud workspace to work from. Reviewed By: liubov-dmitrieva Differential Revision: D13214274 fbshipit-source-id: b21594c04c05f065caf9f9dc494e6274debbde5c
2018-11-27 18:18:29 +03:00
$ tglogp
o 9: d133b886da68 draft 'midstack-feb9'
|
o 8: 1c1b7955142c draft 'midstack-feb7'
|
| o 7: 2b8dce7bd745 draft 'oldstack-mar4' midbook
| |
| o 6: d16408588b2d draft 'oldstack-feb4'
| |
| o 5: 1f9ebd6d1390 draft 'oldstack-feb1'
|/
| o 4: 46f8775ee5d4 draft 'newstack-feb28'
| |
| o 3: 7f958333fe84 draft 'newstack-feb15'
| |
| o 2: 56a352317b67 draft 'newstack-feb13'
|/
| o 1: ff52de2f760c draft 'client2-feb28'
|/
@ 0: df4f53cec30a public 'base'
commitcloud: accept cloud bookmarks for hidden commits Summary: When receiving cloud bookmarks, if they point to a hidden/obsolete commit, don't omit them. The bookmark will make the commit visible again. Reviewed By: quark-zju Differential Revision: D14183009 fbshipit-source-id: ddcb8cce6aaa1eefae93490f76c3dffeaffda21c
2019-02-25 13:31:10 +03:00
In client1 (which hasn't synced yet), make the midbook commit obsolete.
$ cd ../client1
$ hg up -q 2b8dce7bd745
$ hg amend -m "oldstack-mar4 amended"
Attempt to sync. The midbook bookmark should make it visible again.
$ hg cloud sync -q
$ tglog
@ 10: 2ace67ee4791 'oldstack-mar4 amended'
|
| x 9: 2b8dce7bd745 'oldstack-mar4' midbook
|/
| o 8: 46f8775ee5d4 'newstack-feb28'
| |
| | o 7: ff52de2f760c 'client2-feb28'
| | |
| o | 6: 7f958333fe84 'newstack-feb15'
| | |
| o | 5: 56a352317b67 'newstack-feb13'
| |/
| | o 4: d133b886da68 'midstack-feb9'
| | |
| | o 3: 1c1b7955142c 'midstack-feb7'
| |/
o | 2: d16408588b2d 'oldstack-feb4'
| |
o | 1: 1f9ebd6d1390 'oldstack-feb1'
|/
o 0: df4f53cec30a 'base'
commitcloud: add test demonstrating bad behaviour for moved omitted bookmarks Summary: Add a test that shows moving a synced bookmark onto a commit which will be omitted elsewhere causes the bookmark to be moved back. Reviewed By: mitrandir77 Differential Revision: D15414173 fbshipit-source-id: 92dc42d1c5560fa2f5bc618d5335e21ac14d9e7d
2019-05-22 00:29:10 +03:00
Sync in client2. It should match.
$ cd ../client2
$ hg cloud sync -q
$ tglog
o 10: 2ace67ee4791 'oldstack-mar4 amended'
|
| x 9: 2b8dce7bd745 'oldstack-mar4' midbook
|/
o 8: d16408588b2d 'oldstack-feb4'
|
o 7: 1f9ebd6d1390 'oldstack-feb1'
|
| o 6: 46f8775ee5d4 'newstack-feb28'
| |
+---@ 5: ff52de2f760c 'client2-feb28'
| |
| o 4: 7f958333fe84 'newstack-feb15'
| |
| o 3: 56a352317b67 'newstack-feb13'
|/
| o 2: d133b886da68 'midstack-feb9'
| |
| o 1: 1c1b7955142c 'midstack-feb7'
|/
o 0: df4f53cec30a 'base'
Hide some uninteresting commits and sync everywhere
$ hg hide -r 1:: -r 3:: -r 5::
hiding commit 1c1b7955142c "midstack-feb7"
hiding commit d133b886da68 "midstack-feb9"
hiding commit 56a352317b67 "newstack-feb13"
hiding commit 7f958333fe84 "newstack-feb15"
hiding commit ff52de2f760c "client2-feb28"
hiding commit 46f8775ee5d4 "newstack-feb28"
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
working directory now at df4f53cec30a
6 changesets hidden
$ hg cloud sync -q
$ cd ../client1
$ hg cloud sync -q
Make a new public commit
$ cd ../server
$ echo public1 > public1
$ hg commit -Aqm public1
$ hg phase -p .
Pull this into client1
$ cd ../client1
$ hg pull
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
changegroup: do not show "(+/- ? heads)" Summary: In an upcoming change we'll replace `cl.heads()` with `repo.heads()`. In changegroup code path the repo can be in an inconsistent state (ex. a bookmark refers to an unknown commit) which breaks `repo.heads()`. Since the whole purpose of the heads calculation is just to show `(+/- ? heads)`, which does not affect any real features, let's just remove it. Reviewed By: markbt Differential Revision: D18366735 fbshipit-source-id: 893be2cec0c32b64a80b3ef4ca65b69f8ed76b27
2019-11-07 21:50:10 +03:00
added 1 changesets with 1 changes to 1 files
commitcloud: add test demonstrating bad behaviour for moved omitted bookmarks Summary: Add a test that shows moving a synced bookmark onto a commit which will be omitted elsewhere causes the bookmark to be moved back. Reviewed By: mitrandir77 Differential Revision: D15414173 fbshipit-source-id: 92dc42d1c5560fa2f5bc618d5335e21ac14d9e7d
2019-05-22 00:29:10 +03:00
Move midbook to the public commit.
$ hg book -fr 11 midbook
$ hg cloud sync -q
Sync in client 2. It doesn't have the new destination of midbook, so should omit it.
$ cd ../client2
$ hg cloud sync -q
f770b7f72fa59cf01503318ed2b26904cb255d03 not found, omitting midbook bookmark
$ tglogp
o 10: 2ace67ee4791 draft 'oldstack-mar4 amended'
|
commitcloud: remove omitted bookmarks that are available locally Summary: When syncing, if a locally-available bookmark is synced to a new commit that has been omitted, remove the local bookmark to ensure that the next cloud sync doesn't move the bookmark back to where it used to be. Reviewed By: mitrandir77 Differential Revision: D15414172 fbshipit-source-id: 71aaa2d89f734e4c575c24da2c0ef6b59ca4deaa
2019-05-22 00:29:10 +03:00
| x 9: 2b8dce7bd745 draft 'oldstack-mar4'
commitcloud: add test demonstrating bad behaviour for moved omitted bookmarks Summary: Add a test that shows moving a synced bookmark onto a commit which will be omitted elsewhere causes the bookmark to be moved back. Reviewed By: mitrandir77 Differential Revision: D15414173 fbshipit-source-id: 92dc42d1c5560fa2f5bc618d5335e21ac14d9e7d
2019-05-22 00:29:10 +03:00
|/
o 8: d16408588b2d draft 'oldstack-feb4'
|
o 7: 1f9ebd6d1390 draft 'oldstack-feb1'
|
@ 0: df4f53cec30a public 'base'
$ cd ../client1
$ hg cloud sync -q
$ tglogp
commitcloud: remove omitted bookmarks that are available locally Summary: When syncing, if a locally-available bookmark is synced to a new commit that has been omitted, remove the local bookmark to ensure that the next cloud sync doesn't move the bookmark back to where it used to be. Reviewed By: mitrandir77 Differential Revision: D15414172 fbshipit-source-id: 71aaa2d89f734e4c575c24da2c0ef6b59ca4deaa
2019-05-22 00:29:10 +03:00
o 11: f770b7f72fa5 public 'public1' midbook
commitcloud: add test demonstrating bad behaviour for moved omitted bookmarks Summary: Add a test that shows moving a synced bookmark onto a commit which will be omitted elsewhere causes the bookmark to be moved back. Reviewed By: mitrandir77 Differential Revision: D15414173 fbshipit-source-id: 92dc42d1c5560fa2f5bc618d5335e21ac14d9e7d
2019-05-22 00:29:10 +03:00
|
| @ 10: 2ace67ee4791 draft 'oldstack-mar4 amended'
| |
commitcloud: remove omitted bookmarks that are available locally Summary: When syncing, if a locally-available bookmark is synced to a new commit that has been omitted, remove the local bookmark to ensure that the next cloud sync doesn't move the bookmark back to where it used to be. Reviewed By: mitrandir77 Differential Revision: D15414172 fbshipit-source-id: 71aaa2d89f734e4c575c24da2c0ef6b59ca4deaa
2019-05-22 00:29:10 +03:00
| | x 9: 2b8dce7bd745 draft 'oldstack-mar4'
commitcloud: add test demonstrating bad behaviour for moved omitted bookmarks Summary: Add a test that shows moving a synced bookmark onto a commit which will be omitted elsewhere causes the bookmark to be moved back. Reviewed By: mitrandir77 Differential Revision: D15414173 fbshipit-source-id: 92dc42d1c5560fa2f5bc618d5335e21ac14d9e7d
2019-05-22 00:29:10 +03:00
| |/
| o 2: d16408588b2d draft 'oldstack-feb4'
| |
| o 1: 1f9ebd6d1390 draft 'oldstack-feb1'
|/
o 0: df4f53cec30a public 'base'
commitcloud: add a test case demonstrating failure to cloud sync Summary: Add a test case that shows that cloud sync fails when an omitted head has been removed from the cloud workspace. Reviewed By: mitrandir77 Differential Revision: D15535779 fbshipit-source-id: 5d91c4e05715b7c2a7424debb66f0ba864a98850
2019-05-29 17:22:11 +03:00
Sync in client 4. Some of the omitted heads in this client have been removed
from the cloud workspace, but the sync should still work.
$ cd ../client4
$ hg cloud sync
commitcloud: synchronizing 'server' with 'user/test/default'
pulling 2ace67ee4791
pulling from ssh://user@dummy/server
searching for changes
adding changesets
adding manifests
adding file changes
changegroup: do not show "(+/- ? heads)" Summary: In an upcoming change we'll replace `cl.heads()` with `repo.heads()`. In changegroup code path the repo can be in an inconsistent state (ex. a bookmark refers to an unknown commit) which breaks `repo.heads()`. Since the whole purpose of the heads calculation is just to show `(+/- ? heads)`, which does not affect any real features, let's just remove it. Reviewed By: markbt Differential Revision: D18366735 fbshipit-source-id: 893be2cec0c32b64a80b3ef4ca65b69f8ed76b27
2019-11-07 21:50:10 +03:00
added 1 changesets with 0 changes to 3 files
commitcloud: add a test case demonstrating failure to cloud sync Summary: Add a test case that shows that cloud sync fails when an omitted head has been removed from the cloud workspace. Reviewed By: mitrandir77 Differential Revision: D15535779 fbshipit-source-id: 5d91c4e05715b7c2a7424debb66f0ba864a98850
2019-05-29 17:22:11 +03:00
f770b7f72fa59cf01503318ed2b26904cb255d03 not found, omitting midbook bookmark
commitcloud: use lastsyncstate omittedheads for lastsyncstate head omissions Summary: When computing which of the lastsyncstate heads should be available in the repo, use the omittedheads from the lastsyncstate, not the new omitted heads. Reviewed By: mitrandir77 Differential Revision: D15535780 fbshipit-source-id: 215f037215b20d1188999abfa42e7a45391b7723
2019-05-29 17:22:11 +03:00
obsoleted 1 changesets
commitcloud: commits synchronized
finished in 0.00 sec
Reference in New Issue Copy Permalink