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

Debug orphan connections ( actual data ) [Timebox] #3910

Closed
daneryl opened this issue Sep 8, 2021 · 2 comments
Closed

Debug orphan connections ( actual data ) [Timebox] #3910

daneryl opened this issue Sep 8, 2021 · 2 comments

Comments

@daneryl
Copy link
Collaborator

daneryl commented Sep 8, 2021

2021-09-08T16:10:50.821Z [localhost] There's a connection to entity: XXXXXXXX on hub: XXXXXXXXXXXXX, but no entity data.

@mfacar thinks the amount of errors we have its not caused by the fix that will be developed on #3905 , try other routes to find why this happened.

  • check when the flood of errors started
  • check which instances/tenants are affected.
  • use the time found when this happened to try to find something in activity logs and migrations.
@konzz konzz changed the title Debug orphan connections ( actual data ) Debug orphan connections ( actual data ) [Timebox] Sep 21, 2021
@daneryl
Copy link
Collaborator Author

daneryl commented Oct 18, 2021

we think this is now caused by a total different problem, the error is being reported because the user requesting for connections do not have permissions to see the connected entity, this needs to be confirmed.

@RafaPolit
Copy link
Member

I can confirm that the flood of errors is due to "expected" missing entities: with the introduction of permissions, and, particularly 3bd8b5d in order to fix aggregations of relationships tree view.

The relationships array may include links to entities that have not been published. A non-logged user that tries to access an entity that is related to a non-published entity will have that entityData missing, but not because the entity doesn't exist, but because you don't have permissions to access that entity's data.

Already submitted a PR with a fix, and created #3988 to decide where and how to re-think that error reporting.

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

Successfully merging a pull request may close this issue.

3 participants