2022-11-26 23:57:50 +00:00
|
|
|
// Copyright 2021 The Jujutsu Authors
|
2021-10-13 19:53:35 +00:00
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
//
|
|
|
|
// https://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
2023-02-17 22:34:41 +00:00
|
|
|
use jujutsu_lib::backend::{Conflict, ConflictTerm, FileId, TreeValue};
|
2021-10-29 03:55:36 +00:00
|
|
|
use jujutsu_lib::conflicts::{materialize_conflict, parse_conflict, update_conflict_from_content};
|
2023-02-14 21:51:55 +00:00
|
|
|
use jujutsu_lib::repo::Repo;
|
2021-10-13 19:53:35 +00:00
|
|
|
use jujutsu_lib::repo_path::RepoPath;
|
2022-07-10 18:01:48 +00:00
|
|
|
use jujutsu_lib::store::Store;
|
2022-11-08 12:35:16 +00:00
|
|
|
use testutils::TestRepo;
|
2021-10-13 19:53:35 +00:00
|
|
|
|
2023-02-17 22:34:41 +00:00
|
|
|
fn file_conflict_term(file_id: &FileId) -> ConflictTerm {
|
|
|
|
ConflictTerm {
|
2023-02-17 17:34:33 +00:00
|
|
|
value: TreeValue::File {
|
|
|
|
id: file_id.clone(),
|
|
|
|
executable: false,
|
|
|
|
},
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-10-13 19:53:35 +00:00
|
|
|
#[test]
|
|
|
|
fn test_materialize_conflict_basic() {
|
2022-05-21 18:20:51 +00:00
|
|
|
let test_repo = TestRepo::init(false);
|
2022-02-05 23:34:27 +00:00
|
|
|
let store = test_repo.repo.store();
|
2021-10-13 19:53:35 +00:00
|
|
|
|
|
|
|
let path = RepoPath::from_internal_string("file");
|
|
|
|
let base_id = testutils::write_file(
|
2021-11-21 07:46:54 +00:00
|
|
|
store,
|
2021-10-13 19:53:35 +00:00
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2
|
|
|
|
line 3
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
);
|
|
|
|
let left_id = testutils::write_file(
|
2021-11-21 07:46:54 +00:00
|
|
|
store,
|
2021-10-13 19:53:35 +00:00
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2
|
2022-07-10 17:36:45 +00:00
|
|
|
left 3.1
|
|
|
|
left 3.2
|
|
|
|
left 3.3
|
2021-10-13 19:53:35 +00:00
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
);
|
|
|
|
let right_id = testutils::write_file(
|
2021-11-21 07:46:54 +00:00
|
|
|
store,
|
2021-10-13 19:53:35 +00:00
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2
|
2022-07-10 17:36:45 +00:00
|
|
|
right 3.1
|
2021-10-13 19:53:35 +00:00
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
);
|
|
|
|
|
conflicts: preserve order of adds in materialized conflict
We write conflict to the working copy by materializing them as
conflict markers in a file. When the file has been modified (or just
the mtime has changed), we parse the markers to reconstruct the
conflict. For example, let's say we see this conflict marker:
```
<<<<<<<
+++++++
b
%%%%%%%
-a
+c
>>>>>>>
```
Then we will create a hunk with ["a"] as removed and ["b", "c"] as
added.
Now, since commit b84be06c0822, when we materialize conflicts, we
minimize the diff part of the marker (the `%%%%%%%` part). The problem
is that that minimization may result in a different order of the
positive conflict terms. That's particularly bad because we do the
minimization per hunk, so we can end up reconstructing an input that
never existed.
This commit fixes the bug by only considering the next add and the one
after that, and emitting either only the first with `%%%%%%%`, or both
of them, with the first one in `++++++++` and the second one in
`%%%%%%%`.
Note that the recent fix to add context to modify/delete conflicts
means that when we parse modified such conflicts, we'll always
consider them resolved, since the expected adds/removes we pass will
not match what's actually in the file. That doesn't seem so bad, and
it's not obvious what the fix should be, so I'll leave that for later.
2023-02-18 06:29:30 +00:00
|
|
|
// The left side should come first. The diff should be use the smaller (right)
|
|
|
|
// side, and the left side should be a snapshot.
|
2022-07-10 17:36:45 +00:00
|
|
|
let mut conflict = Conflict {
|
2023-02-17 22:34:41 +00:00
|
|
|
removes: vec![file_conflict_term(&base_id)],
|
|
|
|
adds: vec![file_conflict_term(&left_id), file_conflict_term(&right_id)],
|
2021-10-13 19:53:35 +00:00
|
|
|
};
|
2022-07-10 18:01:48 +00:00
|
|
|
insta::assert_snapshot!(
|
|
|
|
&materialize_conflict_string(store, &path, &conflict),
|
|
|
|
@r###"
|
|
|
|
line 1
|
|
|
|
line 2
|
|
|
|
<<<<<<<
|
2022-07-10 17:36:45 +00:00
|
|
|
+++++++
|
|
|
|
left 3.1
|
|
|
|
left 3.2
|
|
|
|
left 3.3
|
conflicts: preserve order of adds in materialized conflict
We write conflict to the working copy by materializing them as
conflict markers in a file. When the file has been modified (or just
the mtime has changed), we parse the markers to reconstruct the
conflict. For example, let's say we see this conflict marker:
```
<<<<<<<
+++++++
b
%%%%%%%
-a
+c
>>>>>>>
```
Then we will create a hunk with ["a"] as removed and ["b", "c"] as
added.
Now, since commit b84be06c0822, when we materialize conflicts, we
minimize the diff part of the marker (the `%%%%%%%` part). The problem
is that that minimization may result in a different order of the
positive conflict terms. That's particularly bad because we do the
minimization per hunk, so we can end up reconstructing an input that
never existed.
This commit fixes the bug by only considering the next add and the one
after that, and emitting either only the first with `%%%%%%%`, or both
of them, with the first one in `++++++++` and the second one in
`%%%%%%%`.
Note that the recent fix to add context to modify/delete conflicts
means that when we parse modified such conflicts, we'll always
consider them resolved, since the expected adds/removes we pass will
not match what's actually in the file. That doesn't seem so bad, and
it's not obvious what the fix should be, so I'll leave that for later.
2023-02-18 06:29:30 +00:00
|
|
|
%%%%%%%
|
|
|
|
-line 3
|
|
|
|
+right 3.1
|
2022-07-10 17:36:45 +00:00
|
|
|
>>>>>>>
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
"###
|
|
|
|
);
|
conflicts: preserve order of adds in materialized conflict
We write conflict to the working copy by materializing them as
conflict markers in a file. When the file has been modified (or just
the mtime has changed), we parse the markers to reconstruct the
conflict. For example, let's say we see this conflict marker:
```
<<<<<<<
+++++++
b
%%%%%%%
-a
+c
>>>>>>>
```
Then we will create a hunk with ["a"] as removed and ["b", "c"] as
added.
Now, since commit b84be06c0822, when we materialize conflicts, we
minimize the diff part of the marker (the `%%%%%%%` part). The problem
is that that minimization may result in a different order of the
positive conflict terms. That's particularly bad because we do the
minimization per hunk, so we can end up reconstructing an input that
never existed.
This commit fixes the bug by only considering the next add and the one
after that, and emitting either only the first with `%%%%%%%`, or both
of them, with the first one in `++++++++` and the second one in
`%%%%%%%`.
Note that the recent fix to add context to modify/delete conflicts
means that when we parse modified such conflicts, we'll always
consider them resolved, since the expected adds/removes we pass will
not match what's actually in the file. That doesn't seem so bad, and
it's not obvious what the fix should be, so I'll leave that for later.
2023-02-18 06:29:30 +00:00
|
|
|
// Swap the positive terms in the conflict. The diff should still use the right
|
|
|
|
// side, but now the right side should come first.
|
2022-07-10 17:36:45 +00:00
|
|
|
conflict.adds.reverse();
|
|
|
|
insta::assert_snapshot!(
|
|
|
|
&materialize_conflict_string(store, &path, &conflict),
|
|
|
|
@r###"
|
|
|
|
line 1
|
|
|
|
line 2
|
|
|
|
<<<<<<<
|
2022-09-20 03:31:20 +00:00
|
|
|
%%%%%%%
|
2022-07-10 17:36:45 +00:00
|
|
|
-line 3
|
|
|
|
+right 3.1
|
2022-07-10 18:01:48 +00:00
|
|
|
+++++++
|
2022-07-10 17:36:45 +00:00
|
|
|
left 3.1
|
|
|
|
left 3.2
|
|
|
|
left 3.3
|
2022-07-10 18:01:48 +00:00
|
|
|
>>>>>>>
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
"###
|
2021-10-13 19:53:35 +00:00
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2023-02-24 04:04:26 +00:00
|
|
|
#[test]
|
|
|
|
fn test_materialize_conflict_multi_rebase_conflicts() {
|
|
|
|
let test_repo = TestRepo::init(false);
|
|
|
|
let store = test_repo.repo.store();
|
|
|
|
|
|
|
|
// Create changes (a, b, c) on top of the base, and linearize them.
|
|
|
|
let path = RepoPath::from_internal_string("file");
|
|
|
|
let base_id = testutils::write_file(
|
|
|
|
store,
|
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2 base
|
|
|
|
line 3
|
|
|
|
",
|
|
|
|
);
|
|
|
|
let a_id = testutils::write_file(
|
|
|
|
store,
|
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2 a.1
|
|
|
|
line 2 a.2
|
|
|
|
line 2 a.3
|
|
|
|
line 3
|
|
|
|
",
|
|
|
|
);
|
|
|
|
let b_id = testutils::write_file(
|
|
|
|
store,
|
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2 b.1
|
|
|
|
line 2 b.2
|
|
|
|
line 3
|
|
|
|
",
|
|
|
|
);
|
|
|
|
let c_id = testutils::write_file(
|
|
|
|
store,
|
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2 c.1
|
|
|
|
line 3
|
|
|
|
",
|
|
|
|
);
|
|
|
|
|
|
|
|
// The order of (a, b, c) should be preserved. For all cases, the "a" side
|
|
|
|
// should be a snapshot.
|
|
|
|
let conflict = Conflict {
|
|
|
|
removes: vec![file_conflict_term(&base_id), file_conflict_term(&base_id)],
|
|
|
|
adds: vec![
|
|
|
|
file_conflict_term(&a_id),
|
|
|
|
file_conflict_term(&b_id),
|
|
|
|
file_conflict_term(&c_id),
|
|
|
|
],
|
|
|
|
};
|
|
|
|
insta::assert_snapshot!(
|
|
|
|
&materialize_conflict_string(store, &path, &conflict),
|
|
|
|
@r###"
|
|
|
|
line 1
|
|
|
|
<<<<<<<
|
|
|
|
+++++++
|
|
|
|
line 2 a.1
|
|
|
|
line 2 a.2
|
|
|
|
line 2 a.3
|
|
|
|
%%%%%%%
|
|
|
|
-line 2 base
|
|
|
|
+line 2 b.1
|
|
|
|
+line 2 b.2
|
|
|
|
%%%%%%%
|
|
|
|
-line 2 base
|
|
|
|
+line 2 c.1
|
|
|
|
>>>>>>>
|
|
|
|
line 3
|
|
|
|
"###
|
|
|
|
);
|
|
|
|
let conflict = Conflict {
|
|
|
|
removes: vec![file_conflict_term(&base_id), file_conflict_term(&base_id)],
|
|
|
|
adds: vec![
|
|
|
|
file_conflict_term(&c_id),
|
|
|
|
file_conflict_term(&b_id),
|
|
|
|
file_conflict_term(&a_id),
|
|
|
|
],
|
|
|
|
};
|
|
|
|
insta::assert_snapshot!(
|
|
|
|
&materialize_conflict_string(store, &path, &conflict),
|
|
|
|
@r###"
|
|
|
|
line 1
|
|
|
|
<<<<<<<
|
|
|
|
%%%%%%%
|
|
|
|
-line 2 base
|
|
|
|
+line 2 c.1
|
|
|
|
%%%%%%%
|
|
|
|
-line 2 base
|
|
|
|
+line 2 b.1
|
|
|
|
+line 2 b.2
|
|
|
|
+++++++
|
|
|
|
line 2 a.1
|
|
|
|
line 2 a.2
|
|
|
|
line 2 a.3
|
|
|
|
>>>>>>>
|
|
|
|
line 3
|
|
|
|
"###
|
|
|
|
);
|
|
|
|
let conflict = Conflict {
|
|
|
|
removes: vec![file_conflict_term(&base_id), file_conflict_term(&base_id)],
|
|
|
|
adds: vec![
|
|
|
|
file_conflict_term(&c_id),
|
|
|
|
file_conflict_term(&a_id),
|
|
|
|
file_conflict_term(&b_id),
|
|
|
|
],
|
|
|
|
};
|
|
|
|
insta::assert_snapshot!(
|
|
|
|
&materialize_conflict_string(store, &path, &conflict),
|
|
|
|
@r###"
|
|
|
|
line 1
|
|
|
|
<<<<<<<
|
|
|
|
%%%%%%%
|
|
|
|
-line 2 base
|
|
|
|
+line 2 c.1
|
|
|
|
+++++++
|
|
|
|
line 2 a.1
|
|
|
|
line 2 a.2
|
|
|
|
line 2 a.3
|
|
|
|
%%%%%%%
|
|
|
|
-line 2 base
|
|
|
|
+line 2 b.1
|
|
|
|
+line 2 b.2
|
|
|
|
>>>>>>>
|
|
|
|
line 3
|
|
|
|
"###
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2023-02-18 06:02:43 +00:00
|
|
|
#[test]
|
|
|
|
fn test_materialize_parse_roundtrip() {
|
|
|
|
let test_repo = TestRepo::init(false);
|
|
|
|
let store = test_repo.repo.store();
|
|
|
|
|
|
|
|
let path = RepoPath::from_internal_string("file");
|
|
|
|
let base_id = testutils::write_file(
|
|
|
|
store,
|
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2
|
|
|
|
line 3
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
);
|
|
|
|
let left_id = testutils::write_file(
|
|
|
|
store,
|
|
|
|
&path,
|
|
|
|
"line 1 left
|
|
|
|
line 2 left
|
|
|
|
line 3
|
|
|
|
line 4
|
|
|
|
line 5 left
|
|
|
|
",
|
|
|
|
);
|
|
|
|
let right_id = testutils::write_file(
|
|
|
|
store,
|
|
|
|
&path,
|
|
|
|
"line 1 right
|
|
|
|
line 2
|
|
|
|
line 3
|
|
|
|
line 4 right
|
|
|
|
line 5 right
|
|
|
|
",
|
|
|
|
);
|
|
|
|
|
|
|
|
let conflict = Conflict {
|
|
|
|
removes: vec![file_conflict_term(&base_id)],
|
|
|
|
adds: vec![file_conflict_term(&left_id), file_conflict_term(&right_id)],
|
|
|
|
};
|
|
|
|
let mut result: Vec<u8> = vec![];
|
|
|
|
materialize_conflict(store, &path, &conflict, &mut result).unwrap();
|
|
|
|
insta::assert_snapshot!(
|
|
|
|
String::from_utf8(result.clone()).unwrap(),
|
|
|
|
@r###"
|
|
|
|
<<<<<<<
|
conflicts: preserve order of adds in materialized conflict
We write conflict to the working copy by materializing them as
conflict markers in a file. When the file has been modified (or just
the mtime has changed), we parse the markers to reconstruct the
conflict. For example, let's say we see this conflict marker:
```
<<<<<<<
+++++++
b
%%%%%%%
-a
+c
>>>>>>>
```
Then we will create a hunk with ["a"] as removed and ["b", "c"] as
added.
Now, since commit b84be06c0822, when we materialize conflicts, we
minimize the diff part of the marker (the `%%%%%%%` part). The problem
is that that minimization may result in a different order of the
positive conflict terms. That's particularly bad because we do the
minimization per hunk, so we can end up reconstructing an input that
never existed.
This commit fixes the bug by only considering the next add and the one
after that, and emitting either only the first with `%%%%%%%`, or both
of them, with the first one in `++++++++` and the second one in
`%%%%%%%`.
Note that the recent fix to add context to modify/delete conflicts
means that when we parse modified such conflicts, we'll always
consider them resolved, since the expected adds/removes we pass will
not match what's actually in the file. That doesn't seem so bad, and
it's not obvious what the fix should be, so I'll leave that for later.
2023-02-18 06:29:30 +00:00
|
|
|
+++++++
|
|
|
|
line 1 left
|
|
|
|
line 2 left
|
2023-02-18 06:02:43 +00:00
|
|
|
%%%%%%%
|
|
|
|
-line 1
|
|
|
|
+line 1 right
|
|
|
|
line 2
|
|
|
|
>>>>>>>
|
|
|
|
line 3
|
|
|
|
<<<<<<<
|
|
|
|
%%%%%%%
|
|
|
|
line 4
|
|
|
|
-line 5
|
|
|
|
+line 5 left
|
|
|
|
+++++++
|
|
|
|
line 4 right
|
|
|
|
line 5 right
|
|
|
|
>>>>>>>
|
|
|
|
"###
|
|
|
|
);
|
|
|
|
|
conflicts: preserve order of adds in materialized conflict
We write conflict to the working copy by materializing them as
conflict markers in a file. When the file has been modified (or just
the mtime has changed), we parse the markers to reconstruct the
conflict. For example, let's say we see this conflict marker:
```
<<<<<<<
+++++++
b
%%%%%%%
-a
+c
>>>>>>>
```
Then we will create a hunk with ["a"] as removed and ["b", "c"] as
added.
Now, since commit b84be06c0822, when we materialize conflicts, we
minimize the diff part of the marker (the `%%%%%%%` part). The problem
is that that minimization may result in a different order of the
positive conflict terms. That's particularly bad because we do the
minimization per hunk, so we can end up reconstructing an input that
never existed.
This commit fixes the bug by only considering the next add and the one
after that, and emitting either only the first with `%%%%%%%`, or both
of them, with the first one in `++++++++` and the second one in
`%%%%%%%`.
Note that the recent fix to add context to modify/delete conflicts
means that when we parse modified such conflicts, we'll always
consider them resolved, since the expected adds/removes we pass will
not match what's actually in the file. That doesn't seem so bad, and
it's not obvious what the fix should be, so I'll leave that for later.
2023-02-18 06:29:30 +00:00
|
|
|
// The first add should always be from the left side
|
2023-02-18 06:02:43 +00:00
|
|
|
insta::assert_debug_snapshot!(
|
|
|
|
parse_conflict(&result, conflict.removes.len(), conflict.adds.len()),
|
|
|
|
@r###"
|
|
|
|
Some(
|
|
|
|
[
|
|
|
|
Conflict {
|
|
|
|
removes: [
|
|
|
|
"line 1\nline 2\n",
|
|
|
|
],
|
|
|
|
adds: [
|
|
|
|
"line 1 left\nline 2 left\n",
|
conflicts: preserve order of adds in materialized conflict
We write conflict to the working copy by materializing them as
conflict markers in a file. When the file has been modified (or just
the mtime has changed), we parse the markers to reconstruct the
conflict. For example, let's say we see this conflict marker:
```
<<<<<<<
+++++++
b
%%%%%%%
-a
+c
>>>>>>>
```
Then we will create a hunk with ["a"] as removed and ["b", "c"] as
added.
Now, since commit b84be06c0822, when we materialize conflicts, we
minimize the diff part of the marker (the `%%%%%%%` part). The problem
is that that minimization may result in a different order of the
positive conflict terms. That's particularly bad because we do the
minimization per hunk, so we can end up reconstructing an input that
never existed.
This commit fixes the bug by only considering the next add and the one
after that, and emitting either only the first with `%%%%%%%`, or both
of them, with the first one in `++++++++` and the second one in
`%%%%%%%`.
Note that the recent fix to add context to modify/delete conflicts
means that when we parse modified such conflicts, we'll always
consider them resolved, since the expected adds/removes we pass will
not match what's actually in the file. That doesn't seem so bad, and
it's not obvious what the fix should be, so I'll leave that for later.
2023-02-18 06:29:30 +00:00
|
|
|
"line 1 right\nline 2\n",
|
2023-02-18 06:02:43 +00:00
|
|
|
],
|
|
|
|
},
|
|
|
|
Resolved(
|
|
|
|
"line 3\n",
|
|
|
|
),
|
|
|
|
Conflict {
|
|
|
|
removes: [
|
|
|
|
"line 4\nline 5\n",
|
|
|
|
],
|
|
|
|
adds: [
|
|
|
|
"line 4\nline 5 left\n",
|
|
|
|
"line 4 right\nline 5 right\n",
|
|
|
|
],
|
|
|
|
},
|
|
|
|
],
|
|
|
|
)
|
|
|
|
"###);
|
|
|
|
}
|
|
|
|
|
2021-10-13 19:53:35 +00:00
|
|
|
#[test]
|
|
|
|
fn test_materialize_conflict_modify_delete() {
|
2022-05-21 18:20:51 +00:00
|
|
|
let test_repo = TestRepo::init(false);
|
2022-02-05 23:34:27 +00:00
|
|
|
let store = test_repo.repo.store();
|
2021-10-13 19:53:35 +00:00
|
|
|
|
|
|
|
let path = RepoPath::from_internal_string("file");
|
|
|
|
let base_id = testutils::write_file(
|
2021-11-21 07:46:54 +00:00
|
|
|
store,
|
2021-10-13 19:53:35 +00:00
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2
|
|
|
|
line 3
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
);
|
2023-02-17 17:54:26 +00:00
|
|
|
let modified_id = testutils::write_file(
|
2021-11-21 07:46:54 +00:00
|
|
|
store,
|
2021-10-13 19:53:35 +00:00
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2
|
2023-02-17 17:54:26 +00:00
|
|
|
modified
|
2021-10-13 19:53:35 +00:00
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
);
|
2023-02-17 17:54:26 +00:00
|
|
|
let deleted_id = testutils::write_file(
|
2021-11-21 07:46:54 +00:00
|
|
|
store,
|
2021-10-13 19:53:35 +00:00
|
|
|
&path,
|
|
|
|
"line 1
|
|
|
|
line 2
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
);
|
|
|
|
|
2023-02-17 17:54:26 +00:00
|
|
|
// left modifies a line, right deletes the same line.
|
2021-10-13 19:53:35 +00:00
|
|
|
let conflict = Conflict {
|
2023-02-17 22:34:41 +00:00
|
|
|
removes: vec![file_conflict_term(&base_id)],
|
2023-02-17 17:54:26 +00:00
|
|
|
adds: vec![
|
2023-02-17 22:34:41 +00:00
|
|
|
file_conflict_term(&modified_id),
|
|
|
|
file_conflict_term(&deleted_id),
|
2023-02-17 17:54:26 +00:00
|
|
|
],
|
2021-10-13 19:53:35 +00:00
|
|
|
};
|
2022-07-10 18:01:48 +00:00
|
|
|
insta::assert_snapshot!(&materialize_conflict_string(store, &path, &conflict), @r###"
|
|
|
|
line 1
|
|
|
|
line 2
|
|
|
|
<<<<<<<
|
|
|
|
+++++++
|
2023-02-17 17:54:26 +00:00
|
|
|
modified
|
conflicts: preserve order of adds in materialized conflict
We write conflict to the working copy by materializing them as
conflict markers in a file. When the file has been modified (or just
the mtime has changed), we parse the markers to reconstruct the
conflict. For example, let's say we see this conflict marker:
```
<<<<<<<
+++++++
b
%%%%%%%
-a
+c
>>>>>>>
```
Then we will create a hunk with ["a"] as removed and ["b", "c"] as
added.
Now, since commit b84be06c0822, when we materialize conflicts, we
minimize the diff part of the marker (the `%%%%%%%` part). The problem
is that that minimization may result in a different order of the
positive conflict terms. That's particularly bad because we do the
minimization per hunk, so we can end up reconstructing an input that
never existed.
This commit fixes the bug by only considering the next add and the one
after that, and emitting either only the first with `%%%%%%%`, or both
of them, with the first one in `++++++++` and the second one in
`%%%%%%%`.
Note that the recent fix to add context to modify/delete conflicts
means that when we parse modified such conflicts, we'll always
consider them resolved, since the expected adds/removes we pass will
not match what's actually in the file. That doesn't seem so bad, and
it's not obvious what the fix should be, so I'll leave that for later.
2023-02-18 06:29:30 +00:00
|
|
|
%%%%%%%
|
|
|
|
-line 3
|
2022-07-10 18:01:48 +00:00
|
|
|
>>>>>>>
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
"###
|
2021-10-13 19:53:35 +00:00
|
|
|
);
|
|
|
|
|
2023-02-17 17:54:26 +00:00
|
|
|
// right modifies a line, left deletes the same line.
|
2021-10-13 19:53:35 +00:00
|
|
|
let conflict = Conflict {
|
2023-02-17 22:34:41 +00:00
|
|
|
removes: vec![file_conflict_term(&base_id)],
|
2023-02-17 17:54:26 +00:00
|
|
|
adds: vec![
|
2023-02-17 22:34:41 +00:00
|
|
|
file_conflict_term(&deleted_id),
|
|
|
|
file_conflict_term(&modified_id),
|
2023-02-17 17:54:26 +00:00
|
|
|
],
|
2021-10-13 19:53:35 +00:00
|
|
|
};
|
2023-02-17 17:54:26 +00:00
|
|
|
insta::assert_snapshot!(&materialize_conflict_string(store, &path, &conflict), @r###"
|
2022-07-10 18:01:48 +00:00
|
|
|
line 1
|
|
|
|
line 2
|
|
|
|
<<<<<<<
|
2022-09-20 03:31:20 +00:00
|
|
|
%%%%%%%
|
2022-07-10 18:01:48 +00:00
|
|
|
-line 3
|
|
|
|
+++++++
|
2023-02-17 17:54:26 +00:00
|
|
|
modified
|
2022-07-10 18:01:48 +00:00
|
|
|
>>>>>>>
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
"###
|
2021-10-13 19:53:35 +00:00
|
|
|
);
|
2023-02-17 17:51:14 +00:00
|
|
|
|
|
|
|
// modify/delete conflict at the file level
|
|
|
|
let conflict = Conflict {
|
2023-02-17 22:34:41 +00:00
|
|
|
removes: vec![file_conflict_term(&base_id)],
|
|
|
|
adds: vec![file_conflict_term(&modified_id)],
|
2023-02-17 17:51:14 +00:00
|
|
|
};
|
|
|
|
insta::assert_snapshot!(&materialize_conflict_string(store, &path, &conflict), @r###"
|
|
|
|
<<<<<<<
|
|
|
|
%%%%%%%
|
2023-02-17 18:05:47 +00:00
|
|
|
line 1
|
|
|
|
line 2
|
2023-02-17 17:51:14 +00:00
|
|
|
-line 3
|
|
|
|
+modified
|
2023-02-17 18:05:47 +00:00
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
+++++++
|
2023-02-17 17:51:14 +00:00
|
|
|
>>>>>>>
|
|
|
|
"###
|
|
|
|
);
|
2021-10-13 19:53:35 +00:00
|
|
|
}
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_parse_conflict_resolved() {
|
|
|
|
assert_eq!(
|
|
|
|
parse_conflict(
|
|
|
|
b"line 1
|
|
|
|
line 2
|
|
|
|
line 3
|
|
|
|
line 4
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
1,
|
|
|
|
2
|
|
|
|
),
|
|
|
|
None
|
|
|
|
)
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_parse_conflict_simple() {
|
2023-02-18 23:01:25 +00:00
|
|
|
insta::assert_debug_snapshot!(
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
parse_conflict(
|
|
|
|
b"line 1
|
|
|
|
<<<<<<<
|
2022-09-20 03:31:20 +00:00
|
|
|
%%%%%%%
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
line 2
|
|
|
|
-line 3
|
|
|
|
+left
|
|
|
|
line 4
|
|
|
|
+++++++
|
|
|
|
right
|
|
|
|
>>>>>>>
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
1,
|
|
|
|
2
|
|
|
|
),
|
2023-02-18 23:01:25 +00:00
|
|
|
@r###"
|
|
|
|
Some(
|
|
|
|
[
|
|
|
|
Resolved(
|
|
|
|
"line 1\n",
|
|
|
|
),
|
|
|
|
Conflict {
|
|
|
|
removes: [
|
|
|
|
"line 2\nline 3\nline 4\n",
|
|
|
|
],
|
|
|
|
adds: [
|
|
|
|
"line 2\nleft\nline 4\n",
|
|
|
|
"right\n",
|
|
|
|
],
|
|
|
|
},
|
|
|
|
Resolved(
|
|
|
|
"line 5\n",
|
|
|
|
),
|
|
|
|
],
|
|
|
|
)
|
|
|
|
"###
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
)
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_parse_conflict_multi_way() {
|
2023-02-18 23:01:25 +00:00
|
|
|
insta::assert_debug_snapshot!(
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
parse_conflict(
|
|
|
|
b"line 1
|
|
|
|
<<<<<<<
|
2022-09-20 03:31:20 +00:00
|
|
|
%%%%%%%
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
line 2
|
|
|
|
-line 3
|
|
|
|
+left
|
|
|
|
line 4
|
|
|
|
+++++++
|
|
|
|
right
|
2022-09-20 03:31:20 +00:00
|
|
|
%%%%%%%
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
line 2
|
|
|
|
+forward
|
|
|
|
line 3
|
|
|
|
line 4
|
|
|
|
>>>>>>>
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
2,
|
|
|
|
3
|
|
|
|
),
|
2023-02-18 23:01:25 +00:00
|
|
|
@r###"
|
|
|
|
Some(
|
|
|
|
[
|
|
|
|
Resolved(
|
|
|
|
"line 1\n",
|
|
|
|
),
|
|
|
|
Conflict {
|
|
|
|
removes: [
|
|
|
|
"line 2\nline 3\nline 4\n",
|
|
|
|
"line 2\nline 3\nline 4\n",
|
|
|
|
],
|
|
|
|
adds: [
|
|
|
|
"line 2\nleft\nline 4\n",
|
|
|
|
"right\n",
|
|
|
|
"line 2\nforward\nline 3\nline 4\n",
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
],
|
2023-02-18 23:01:25 +00:00
|
|
|
},
|
|
|
|
Resolved(
|
|
|
|
"line 5\n",
|
|
|
|
),
|
|
|
|
],
|
|
|
|
)
|
|
|
|
"###
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
)
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_parse_conflict_different_wrong_arity() {
|
|
|
|
assert_eq!(
|
|
|
|
parse_conflict(
|
|
|
|
b"line 1
|
|
|
|
<<<<<<<
|
2022-09-20 03:31:20 +00:00
|
|
|
%%%%%%%
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
line 2
|
|
|
|
-line 3
|
|
|
|
+left
|
|
|
|
line 4
|
|
|
|
+++++++
|
|
|
|
right
|
|
|
|
>>>>>>>
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
2,
|
|
|
|
3
|
|
|
|
),
|
|
|
|
None
|
|
|
|
)
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_parse_conflict_malformed_marker() {
|
2022-09-20 03:31:20 +00:00
|
|
|
// The conflict marker is missing `%%%%%%%`
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
assert_eq!(
|
|
|
|
parse_conflict(
|
|
|
|
b"line 1
|
|
|
|
<<<<<<<
|
|
|
|
line 2
|
|
|
|
-line 3
|
|
|
|
+left
|
|
|
|
line 4
|
|
|
|
+++++++
|
|
|
|
right
|
|
|
|
>>>>>>>
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
1,
|
|
|
|
2
|
|
|
|
),
|
|
|
|
None
|
|
|
|
)
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_parse_conflict_malformed_diff() {
|
|
|
|
// The diff part is invalid (missing space before "line 4")
|
|
|
|
assert_eq!(
|
|
|
|
parse_conflict(
|
|
|
|
b"line 1
|
|
|
|
<<<<<<<
|
2022-09-20 03:31:20 +00:00
|
|
|
%%%%%%%
|
conflicts: add a function for parsing a materialized conflict
I initially made the working copy materialize conflicts in its
`check_out()` method. Then I changed it later (exactly a year ago, on
Halloween of 2020, actually) so that the working copy expected
conflicts to already have been materalized, which happens in
`MutableRepo::check_out`().
I think my reasoning then was that the file system cannot represent a
conflict. While it's true that the file system itself doesn't have
information to know whether a file represents a conflict, we can
record that ourselves. We already record whether a file is executable
or not and then preserve that if we're on a file system that isn't
able to record it. It's not that different to do the same for
conflicts if we're on a file system that doesn't understand conflicts
(i.e. all file systems).
The plan is to have the working copy remember whether a file
represents a conflict. When we check if it has changed, we parse the
file, including conflict markers, and recreate the conflict from
it. We should be able to do that losslessly (and we should adjust
formats to make it possible if we find cases where it's not).
Having the working copy preserve conflict states has several
advantages:
* Because conflicts are not materialized in the working copy, you can
rebase the conflicted commit and the working copy without causing
more conflicts (that's currently a UX bug I run into every now and
then).
* If you don't change anything in the working copy, it will be
unchanged compared to its parent, which means we'll automatically
abandon it if you update away from it.
* The user can choose to resolve only some of the conflicts in a file
and squash those in, and it'll work they way you'd hope.
* It should make it easier to implement support for external merge
tools (#18) without having them treat the working copy differently.
This patch prepares for that work by adding support for parsing
materialized conflicts.
2021-10-31 18:57:12 +00:00
|
|
|
line 2
|
|
|
|
-line 3
|
|
|
|
+left
|
|
|
|
line 4
|
|
|
|
+++++++
|
|
|
|
right
|
|
|
|
>>>>>>>
|
|
|
|
line 5
|
|
|
|
",
|
|
|
|
1,
|
|
|
|
2
|
|
|
|
),
|
|
|
|
None
|
|
|
|
)
|
|
|
|
}
|
2021-10-29 03:55:36 +00:00
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_update_conflict_from_content() {
|
2022-05-21 18:20:51 +00:00
|
|
|
let test_repo = TestRepo::init(false);
|
2022-02-05 23:34:27 +00:00
|
|
|
let store = test_repo.repo.store();
|
2021-10-29 03:55:36 +00:00
|
|
|
|
|
|
|
let path = RepoPath::from_internal_string("dir/file");
|
2021-11-21 07:46:54 +00:00
|
|
|
let base_file_id = testutils::write_file(store, &path, "line 1\nline 2\nline 3\n");
|
|
|
|
let left_file_id = testutils::write_file(store, &path, "left 1\nline 2\nleft 3\n");
|
|
|
|
let right_file_id = testutils::write_file(store, &path, "right 1\nline 2\nright 3\n");
|
2021-10-29 03:55:36 +00:00
|
|
|
let conflict = Conflict {
|
2023-02-17 22:34:41 +00:00
|
|
|
removes: vec![file_conflict_term(&base_file_id)],
|
2021-10-29 03:55:36 +00:00
|
|
|
adds: vec![
|
2023-02-17 22:34:41 +00:00
|
|
|
file_conflict_term(&left_file_id),
|
|
|
|
file_conflict_term(&right_file_id),
|
2021-10-29 03:55:36 +00:00
|
|
|
],
|
|
|
|
};
|
2022-03-31 16:21:50 +00:00
|
|
|
let conflict_id = store.write_conflict(&path, &conflict).unwrap();
|
2021-10-29 03:55:36 +00:00
|
|
|
|
|
|
|
// If the content is unchanged compared to the materialized value, we get the
|
|
|
|
// old conflict id back.
|
|
|
|
let mut materialized = vec![];
|
2021-11-21 07:46:54 +00:00
|
|
|
materialize_conflict(store, &path, &conflict, &mut materialized).unwrap();
|
|
|
|
let result = update_conflict_from_content(store, &path, &conflict_id, &materialized).unwrap();
|
2021-10-29 03:55:36 +00:00
|
|
|
assert_eq!(result, Some(conflict_id.clone()));
|
|
|
|
|
|
|
|
// If the conflict is resolved, we None back to indicate that.
|
|
|
|
let result = update_conflict_from_content(
|
2021-11-21 07:46:54 +00:00
|
|
|
store,
|
2021-10-29 03:55:36 +00:00
|
|
|
&path,
|
|
|
|
&conflict_id,
|
|
|
|
b"resolved 1\nline 2\nresolved 3\n",
|
|
|
|
)
|
|
|
|
.unwrap();
|
|
|
|
assert_eq!(result, None);
|
|
|
|
|
|
|
|
// If the conflict is partially resolved, we get a new conflict back.
|
2022-09-20 03:31:20 +00:00
|
|
|
let result = update_conflict_from_content(
|
|
|
|
store,
|
|
|
|
&path,
|
|
|
|
&conflict_id,
|
|
|
|
b"resolved 1\nline 2\n<<<<<<<\n%%%%%%%\n-line 3\n+left 3\n+++++++\nright 3\n>>>>>>>\n",
|
|
|
|
)
|
|
|
|
.unwrap();
|
2021-10-29 03:55:36 +00:00
|
|
|
assert_ne!(result, None);
|
|
|
|
assert_ne!(result, Some(conflict_id));
|
2022-03-31 16:21:50 +00:00
|
|
|
let new_conflict = store.read_conflict(&path, &result.unwrap()).unwrap();
|
2021-10-29 03:55:36 +00:00
|
|
|
// Calculate expected new FileIds
|
2021-11-21 07:46:54 +00:00
|
|
|
let new_base_file_id = testutils::write_file(store, &path, "resolved 1\nline 2\nline 3\n");
|
|
|
|
let new_left_file_id = testutils::write_file(store, &path, "resolved 1\nline 2\nleft 3\n");
|
|
|
|
let new_right_file_id = testutils::write_file(store, &path, "resolved 1\nline 2\nright 3\n");
|
2021-10-29 03:55:36 +00:00
|
|
|
assert_eq!(
|
|
|
|
new_conflict,
|
|
|
|
Conflict {
|
2023-02-17 22:34:41 +00:00
|
|
|
removes: vec![file_conflict_term(&new_base_file_id)],
|
2021-10-29 03:55:36 +00:00
|
|
|
adds: vec![
|
2023-02-17 22:34:41 +00:00
|
|
|
file_conflict_term(&new_left_file_id),
|
|
|
|
file_conflict_term(&new_right_file_id)
|
2021-10-29 03:55:36 +00:00
|
|
|
]
|
|
|
|
}
|
|
|
|
)
|
|
|
|
}
|
2022-07-10 18:01:48 +00:00
|
|
|
|
|
|
|
fn materialize_conflict_string(store: &Store, path: &RepoPath, conflict: &Conflict) -> String {
|
|
|
|
let mut result: Vec<u8> = vec![];
|
|
|
|
materialize_conflict(store, path, conflict, &mut result).unwrap();
|
|
|
|
String::from_utf8(result).unwrap()
|
|
|
|
}
|