2020-03-24 02:09:01 +03:00
We were seeing an issue where (it seemed) that every namespace that was visited during a propagate would get a new history node, even when it didn't contain any dependents.
Example:
```unison:hide
a = "a term"
X.foo = "a namespace"
```
```ucm
2024-06-12 01:22:09 +03:00
scratch/main> add
2020-03-24 02:09:01 +03:00
```
Here is an update which should not affect `X` :
```unison:hide
a = "an update"
```
```ucm
2024-06-12 01:22:09 +03:00
scratch/main> update
2020-03-24 02:09:01 +03:00
```
As of the time of this writing, the history for `X` should be a single node, `#4eeuo5bsfr` ;
```ucm
2024-06-12 01:22:09 +03:00
scratch/main> history X
2020-03-24 02:09:01 +03:00
```
however, as of release/M1i, we saw an extraneous node appear. If your `ucm` is fixed, you won't see it below:
```ucm:error
2024-06-12 01:22:09 +03:00
scratch/main> history #7nl6ppokhg
2020-03-24 02:09:01 +03:00
```