Commit 1661b80
authored
Handled additional Range constructor in toSigners side condition. (#944)
This PR replaces the `allKeys` condition in the requires clause of
`toSigners` with another function, `allRangeWrappedKeys`, that works in
exactly the same way except is unwraps an additional Range constructor
from the provided `ListItem`. This `Range` is generated from `fromKey`,
and the existing `allKeys` implementation was not sufficient to handle
it, as it was expecting just a List.
The issue came up when investigating the failure of the proof for
test_process_initialize_multisig2. I attach a file that contains a part
of the stuck configuration, where I isolated a term that shows the
issue. The relevant term is `SignersError(...)`. With this change, the
proof was able to pass.
[signers-error.txt](https://github.com/user-attachments/files/25424362/signers-error.txt)
Note: I chose to use a new function rather than extend the functionality
of `allKeys` beyond its (apparent) intend to handle Lists, but I believe
that the issue could be solved with just another rule in `allKeys`, if
that is what you prefer.1 parent 133e94d commit 1661b80
1 file changed
Lines changed: 7 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
130 | 130 | | |
131 | 131 | | |
132 | 132 | | |
133 | | - | |
| 133 | + | |
134 | 134 | | |
135 | 135 | | |
136 | 136 | | |
| |||
155 | 155 | | |
156 | 156 | | |
157 | 157 | | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
158 | 164 | | |
159 | 165 | | |
160 | 166 | | |
| |||
0 commit comments