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

Nested recursion breaking max nested level for parent comment calculation #16523

Conversation

nickvergessen
Copy link
Member

The bug had no effect so far because the comments app does not allow replying.
However the integration tests I'm writing for nextcloud/spreed#2000 failed with the following error, when replying to a message which was already a reply:

Error: Maximum function nesting level of '256' reached, aborting! at …/server/lib/private/Comments/Manager.php#243

@nickvergessen
Copy link
Member Author

/backport to stable16

Copy link
Member

@rullzer rullzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure

Copy link
Member

@blizzz blizzz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The else is unnecessary. Why would this prevent an infinite loop however?

@blizzz blizzz merged commit babe133 into master Jul 24, 2019
@delete-merged-branch delete-merged-branch bot deleted the bugfix/noid/nested-recursion-breaking-max-nested-level-for-parent-comment branch July 24, 2019 09:50
@backportbot-nextcloud
Copy link

backport to stable16 in #16524

@danxuliu
Copy link
Member

The else is unnecessary. Why would this prevent an infinite loop however?

Not the else, but the change from $comment->getId() to $comment->getParentId() (first commit).

@blizzz
Copy link
Member

blizzz commented Jul 24, 2019

The else is unnecessary. Why would this prevent an infinite loop however?

Not the else, but the change from $comment->getId() to $comment->getParentId() (first commit).

Gosh, and i doublechecked that :-/ more ☕ needed. makes sense anyway :)

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

Successfully merging this pull request may close these issues.

4 participants