-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hm: remove excess relations #2572
Comments
plugin 0.13This gets more and more problematic and I am loosing a lot of time wrestling with multiple recording issues, some of which cannot really happen anymore with our current version of the recording system. This is now how it is:
|
@lbestock FA needs a fresh look now that we have this error type: It seems to have excess relations, too. |
This looks fine in terms of icons, but I leave it open for @lbestock to look at FA. |
I am very late to this party and only trying to wrap my head around it now. @urapadmin I have noted that you do not allow two relations between the same loci and I have read my Harris and I accept this. Why do some units have an error sign in the menu so that I can toggle the error pane on and off (CC) and other units simply have the error pane visible and I can't turn it off (FA, FI, CA)? Those only have relations removed for other reasons, not cyclic ones, but it still should be possible to toggle the pane off, right? This probably already has a ticket but post-testing there should be a key so the error icons can be easily understood. Now for FA... |
There are two FA excess relations and they are indeed just excess, one totally just made twice, same relationship even. So things look good to me with FA. |
There is a ticket for the error panel issue, I believe, but not for a key (which would indeed be helpful). I think if we create a key ticket this one can be closed? |
I added the key to #2576, so closed this shall be. |
CA-002 is not only sealed by CA-001, it is also "adjacent to" and vice versa. And that's where the system gets confused.
Originally posted by @urapadmin in #2402 (comment)
The text was updated successfully, but these errors were encountered: