- 18 Feb, 2022 1 commit
-
-
Georges Racinet authored
Not only had I forgotten to list it: it was also complete, as the various settings pages didn't need any fix. --HG-- branch : heptapod-0-28
-
- 15 Feb, 2022 4 commits
-
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
- 14 Feb, 2022 2 commits
-
-
Georges Racinet authored
Introduce API to get Heptapod-specific version information See merge request !329 --HG-- branch : heptapod-stable
-
Elouan Martinet authored
--HG-- branch : heptapod-stable
-
- 12 Feb, 2022 1 commit
-
-
Georges Racinet authored
With the `empty_repository` fixture, the repository is already created. Apparently, Gitaly 14.5 does not return an error (Git repo creation occurs first) but 14.6 will. In any case, we can as well avoid it on the stable branch. --HG-- branch : heptapod-stable
-
- 11 Feb, 2022 7 commits
-
-
Georges Racinet authored
Of course, if VCS type changes, any previous validation of remote endpoint (Git or Mercurial) has to be done again. Was really painful to make work because the previously used CSS selector, although seemingly meant to return only the element from the active pane, was actually returning two of them, and events were attached on the wrong one. Side remark: as soon as the URL field loses focus (meaning the user finished enter a value), the `isProjectImportUrlDirty` becomes true, and stays so even validation result is already known and there are no further changes. Therefore it does not mean "change that has not yet been taken into account" but "changed at least once from initial value". --HG-- branch : heptapod-stable
-
Georges Racinet authored
Part of #621 --HG-- branch : heptapod-stable
-
Georges Racinet authored
This seems to be a worthwile addition, especially because of the critical nature of imports (main use case for this validation service) --HG-- branch : heptapod-stable
-
Georges Racinet authored
We transmit over the VCS Type from JavaScript code, and pass it down to the service, which was already able to validate remote Mercurial servers. Closes #524 --HG-- branch : heptapod-stable
-
Georges Racinet authored
We are piggy-backing on the existing code for Git, although the Mercurial case is simpler: the capabilities request is meant for that, and can be taken whole. At this point, the enforcement for Mercurial is not yet plugged into the UI (or rather, the frontend calls the Git check, which explains the comeback of #524), but it is already active with the API. This can probably still be used in the auto-detection of #406, by using the service twice, for Git and Mercurial. --HG-- branch : heptapod-stable
-
Georges Racinet authored
Related to the comeback of #524. This should not have been removed, at least not in current context: it is not the validation error blocking import, rather the corresponding user feedback. --HG-- branch : heptapod-stable
-
Georges Racinet authored
There are cases when we'll need it without an existing `Project` instance. First use cases in Project creation process. Will also help possible refactoring to move `Project.mercurial?` to the `Repository` model. --HG-- branch : heptapod-stable
-
- 04 Feb, 2022 3 commits
-
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
- 03 Feb, 2022 8 commits
-
-
GitLab Bot authored
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Bot authored
-
GitLab Bot authored
-
GitLab Bot authored
-
GitLab Bot authored
-
GitLab Bot authored
-
GitLab Bot authored
-
- 30 Jan, 2022 2 commits
-
-
Georges Racinet authored
…for the new SSH host keys of upload.heptapod.net --HG-- branch : heptapod-0-28
-
Georges Racinet authored
(we're actually changing server) --HG-- branch : heptapod-stable
-
- 26 Jan, 2022 3 commits
-
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
Problem introduced by d63e143d0e40 because DraftNote doesn't inherit from Note and spotted by the `extended` CI scope on the `heptapod-0-28` branch. Also adding specs for all kind of Notes to regular CI runs, that would have caught it before merge attempt in the release branch. --HG-- branch : heptapod-stable
-
- 25 Jan, 2022 2 commits
-
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
- 24 Jan, 2022 1 commit
-
-
Georges Racinet authored
Makes sense, since we changed it. --HG-- branch : heptapod-stable
-
- 23 Jan, 2022 3 commits
-
-
Georges Racinet authored
--HG-- branch : heptapod-0-28
-
Georges Racinet authored
This is simply replacing by the version in v14.5.3: upstream decided to remove the offending test. Closes #602 --HG-- branch : heptapod-stable
-
Georges Racinet authored
--HG-- branch : heptapod-stable
-
- 22 Jan, 2022 3 commits
-
-
Georges Racinet authored
This simple pattern could be later generalized. Doing it right now for `Note` only because they are the most numerous of the records to migrate. Some figures from my dev workstation: re-migrating HGitaly goes down from 90 to 30s initial migration of hg-git down from 240 to 150s --HG-- branch : heptapod-stable
-
Georges Racinet authored
The `:diff_refs_match_commit` validator cannot work during the migration, because the commit id is now a Mercurial SHA while the repository class is still `HgGitRepository` and the Rugged implementation is typically active. We could have used the `importing?` transient boolean instead of creating a new one. Heres' why we chose not to: - impact could be bigger in these mixins. It is possible that upstram had a good reason not to use it. - `DraftNote#importing?` is always false One could argue that this removes an interesting consistency check but: - there are protections against `commit_id` being `nil` and perhaps something similar with `position`. - we would need to instantiate `HgitalyRepository` specifically to perform it. This can be done in a follow-up if it feels too dangerous, and it would need the same boolean flag. --HG-- branch : heptapod-stable
-
Georges Racinet authored
The Note id is a must-have in the logs. --HG-- branch : heptapod-stable
-