Skip to content
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

Important bug in superclasses #2228

Open
davidzbiral opened this issue May 29, 2024 · 2 comments
Open

Important bug in superclasses #2228

davidzbiral opened this issue May 29, 2024 · 2 comments
Assignees
Labels

Comments

@davidzbiral
Copy link
Collaborator

davidzbiral commented May 29, 2024

Important bug found in superclasses, I never encountered it before. Remains even after page reload.
I am editing these two entities: 1, 2, which have SYN relation between them. But for some reason their superclasses seem to be edited by the app, or displayed badly, in such a way that some or all appear twice based on having added them in the other one (the synonym) - as if the app was taking them from the synonym and thus duplicating them. So far, I think, we requested no symmetrization of the SCL of synonyms, only warning that SCL of synonyms is inconsistent. So I do not know what to think about this behaviour, and whether the data structure is not in danger.

Interestingly, over these incorrect duplicates, mouseover shows nothing, while for one set which correctly belongs there, the mouseover works just as always.

obrazek

@adammertel
Copy link
Contributor

Seems that identical relations are returned in this case. Just to make sure - when one of them is removed, are the duplicate removed as well? If yes, there should be no danger and the fix should be quite simple.

@adammertel adammertel assigned jancimertel and unassigned adammertel May 29, 2024
@davidzbiral
Copy link
Collaborator Author

davidzbiral commented May 30, 2024

@adammertel This morning it was fine, i.e. only 2 SCL were under both particeps and member, and I also tried removing and re-adding under one SCL under one of them, and no misbehaviour was observed under either particeps and member (synonyms). Can it thus be that it was a bug in some slow or misguided communication between app and server?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants