Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent check-ins by user andybradford
|
2024-12-01
| ||
| 05:23 | This should just be for propagating tags, not single. ... (check-in: c34cf835 user: andybradford tags: show-branch-change) | |
| 01:44 | Check the tagxref table for changes to branch name before commit and if there exists a change that wasn't made by the current user then prompt. ... (check-in: 0aabb6bc user: andybradford tags: show-branch-change) | |
|
2024-11-30
| ||
| 17:37 | When --no-prompt is being used and there is a branch name change during commit skip the prompt and the condition because it's not a fatal condition. ... (check-in: c552f440 user: andybradford tags: show-branch-change) | |
|
2024-11-29
| ||
| 16:23 | When --force is specified do not treat a branch name change that arrives during autosync as fatal. ... (check-in: 82fee40e user: andybradford tags: show-branch-change) | |
|
2024-11-27
| ||
| 20:29 | I think this conveys the message with slightly more clarity. ... (check-in: 4e7e1647 user: andybradford tags: show-branch-change) | |
| 19:28 | If the branch name changes during a commit, prompt user to confirm continue (behaves similar to other pre-commit checks). Inspired by forum post d5a1b209186552dd. ... (check-in: a70f279a user: andybradford tags: show-branch-change) | |
|
2024-11-26
| ||
| 19:49 | Minor update to conform to style, no change in function. ... (check-in: 8e06863e user: andybradford tags: show-branch-change) | |
| 19:24 | Only emit the change in branch if there is no VERSION argument to minimize additional output. ... (check-in: 2ef47b81 user: andybradford tags: show-branch-change) | |
|
2024-11-24
| ||
| 03:38 | Improve situational awareness with "fossil update" by including a message in the changes: information if the name of the branch changes. See forum discussion 7f5ae505e4144a0c for details. ... (check-in: bb9150c4 user: andybradford tags: show-branch-change) | |
|
2024-11-23
| ||
| 17:22 | Bug fix for allowing SSH command to be overridden once for sync operations. ... (check-in: 4c6e394d user: andybradford tags: trunk) | |
| 17:19 | Prepare for merge into trunk. ... (Closed-Leaf check-in: c88ed3e1 user: andybradford tags: ssh-command-once) | |
| 01:11 | This fixes the logic error introduced in [f019cb5fc3f]. ... (check-in: 25857ebb user: andybradford tags: ssh-command-once) | |
| 01:08 | This commit had more than I had intended. ... (check-in: 91adccdb user: andybradford tags: ssh-command-once) | |
| 01:07 | Fix logic error from previous commit. ... (check-in: 3ada7a67 user: andybradford tags: ssh-command-once) | |
|
2024-11-22
| ||
| 15:11 | When using --once with --ssh-command, prefer the command-line argument over the stored option. Addresses forum post 90c1f5fef258c704. ... (check-in: f019cb5f user: andybradford tags: ssh-command-once) | |
|
2024-09-11
| ||
| 13:30 | Update tests to account for new settings introduced with [1a0b304307] and [cadfcba32c]. ... (check-in: 6ead7d99 user: andybradford tags: trunk) | |
|
2024-04-27
| ||
| 00:52 | With the changes introduced in [213ca339c2951ad1] it is now possible to restrict the timeline to a single branch also with "fossil timeline". ... (check-in: abb54cb0 user: andybradford tags: trunk) | |
|
2024-04-25
| ||
| 13:36 | Fix minor typo in test introduced by previous commit. ... (check-in: f0c4705d user: andybradford tags: trunk) | |
| 13:34 | Use join instead to avoid prepending garbage at the beginning of the string. ... (check-in: 4d556700 user: andybradford tags: trunk) | |
|
2024-03-23
| ||
| 05:54 | Updates from trunk for sync changes et al. ... (Leaf check-in: 2304041e user: andybradford tags: clone-resume) | |
|
2024-02-09
| ||
| 13:51 | Sync up with trunk for latest improvements. ... (check-in: 12390507 user: andybradford tags: clone-resume) | |
|
2024-02-08
| ||
| 15:10 | Update help for "fossil ui" to more closely match the behavior in the code. ... (check-in: b2b373ff user: andybradford tags: trunk) | |
|
2024-02-07
| ||
| 14:25 | Pull in the remaining bits from trunk for integration testing. ... (check-in: d27cb05f user: andybradford tags: clone-resume) | |
|
2024-02-06
| ||
| 14:19 | Bring in fixes for SSH from trunk. ... (check-in: c55d1b7b user: andybradford tags: clone-resume) | |
| 03:22 | Don't use the ssh file descriptor as an indicator that we should be using SSH transport. Arguably we could also just reset sshIn to 0, but I think this is better. ... (Closed-Leaf check-in: bcf6abe5 user: andybradford tags: ssh-path-prefix) | |
|
2024-02-03
| ||
| 16:55 | Update with all changes from trunk. ... (check-in: c454059a user: andybradford tags: clone-resume) | |
|
2023-12-17
| ||
| 05:49 | When resuming a clone, delete the previous setup user so it can be reset. This also handles the case where a new --admin-user is passed in. ... (check-in: b86d4da5 user: andybradford tags: clone-resume) | |
|
2023-12-08
| ||
| 15:30 | Limit the scope to the error condition to clone operations only for now. ... (check-in: 29e9e84a user: andybradford tags: clone-resume) | |
| 14:33 | Only output clone retry warning if there is another round to go. ... (check-in: bdd22578 user: andybradford tags: clone-resume) | |
| 14:20 | The rebuilt string is only regenerated if the manifest changes, so use the mtime of when the rebuild is done instead. ... (check-in: a92fddc0 user: andybradford tags: clone-resume) | |
| 13:52 | If the clone is interrupted by the user this should constitute an error condition. ... (check-in: 2c8ad9a4 user: andybradford tags: clone-resume) | |
|
2023-12-05
| ||
| 14:12 | Clean up signal includes. ... (check-in: e6da7f08 user: andybradford tags: clone-resume) | |
|
2023-12-02
| ||
| 18:30 | Use a new pragma requested only in the first clone cycle to track the rebuilt time on the remote server to be able to error out if the rids are rebuilt before resuming a clone. This is currently just a fossilized string but it could instead be a hash of the components to make it more like a "code". Requesting the pragma only at the beginning does not account for the possibility that a rebuild will happen after the clone begins. I find that scenario highly unlikely, but grant that it might be possible. If the remote server does not yet support the pragma the client falls back to using the remote server-code. ... (check-in: 7f116a43 user: andybradford tags: clone-resume) | |
|
2023-12-01
| ||
| 22:37 | Typo corrections in comments only. No change in functionality. ... (check-in: a8b6fdc8 user: andybradford tags: trunk) | |
| 21:22 | Just write the value the first time it is seen since there is no need to have the value during the sync (yet). ... (check-in: 15b166df user: andybradford tags: clone-resume) | |
| 21:14 | Prevent resuming a clone from a different server by preserving the remote server-code and comparing on resume. This is a crude heuristic to determine whether or not it is likely that the remote server still has the same rids. A better heuristic may be to probe the server for known rids that have been received (e.g. each clone seqno that is sent by the server could be recorded and then probed with a pragma request by the client later on). ... (check-in: aa54ea41 user: andybradford tags: clone-resume) | |
| 20:31 | Prevent the resuming of a clone that does not have the product code. ... (check-in: 63af8da3 user: andybradford tags: clone-resume) | |
| 20:17 | Minor style change. ... (check-in: d8207954 user: andybradford tags: clone-resume) | |
| 20:12 | Skip all finalizing until the clone is complete. ... (check-in: 9fa25cd7 user: andybradford tags: clone-resume) | |
| 17:55 | Try to handle some error conditions better. First, if the clone's first sync didn't bring down any artifacts there isn't likely any point in continuing. Second, if on resuming a clone no artifacts were received, abort. Third, check if the project-code has changed earlier (this might be detected even earlier when the client receives the "push" card). ... (check-in: 17f3408f user: andybradford tags: clone-resume) | |
| 04:12 | Minor correction in comment. No change in functionality. ... (check-in: 4fdc41bd user: andybradford tags: clone-resume) | |
| 03:58 | Shorten warning message to fit in a terminal without wrapping. ... (check-in: 5bb6d261 user: andybradford tags: clone-resume) | |
| 03:53 | Verify that the project-code on resume hasn't changed per discussion in forum post d1a2ed56271602fa and rollback changes if they are different. ... (check-in: ee5b9420 user: andybradford tags: clone-resume) | |
|
2023-11-30
| ||
| 06:26 | Defer rebuilding the database until the clone is complete. This prevents a lot of unnecessary rebuilding while there aren't enough artifacts to make it worth it. ... (check-in: 333a89bf user: andybradford tags: clone-resume) | |
| 04:01 | Catch SIGINT during sync so that when pressing ctrl-c during a clone of a large repository it doesn't dispose of all the progress that was made during, thus enabling resume from an user interrupt. When the handler returns, the last sync will complete and then exit the loop. ... (check-in: ad2e1485 user: andybradford tags: clone-resume) | |
|
2023-11-29
| ||
| 04:32 | Merge in latest from trunk. ... (check-in: 5d12d426 user: andybradford tags: clone-resume) | |
|
2023-11-27
| ||
| 06:19 | Take advantage of the fact that the seqno is recorded and automatically resume up to three times if failure is encountered. ... (check-in: bc0a4c60 user: andybradford tags: clone-resume) | |
| 06:14 | Check for valid value from return of function. ... (check-in: 2f0aac8c user: andybradford tags: clone-resume) | |
|
2023-11-25
| ||
| 15:56 | Remove description of unsupported option that was removed with [298ccff06c487d035a7] from "fossil all rebuild" command. No change in functionality. ... (check-in: 33fa9155 user: andybradford tags: trunk) | |
|
2023-11-24
| ||
| 23:51 | Do away with the --resume flag as it is mostly redundant and can be assumed by the presence of the recorded clone_seqno. Suggested by Warren Young in forum post 4bcbb41aab2538d4. ... (check-in: b0a60d8f user: andybradford tags: clone-resume) | |