Files property comments-count gets autoincremented even after deleting the file or the user.

[SergioBertolinSG]

Steps to reproduce:

    Given user "user0" exists
    And As an "user0"
    And User "user0" uploads file "data/textfile.txt" to "/myFileToComment.txt"
    And user "user0" comments with content "My first comment" on file "/myFileToComment.txt"
    And user "user0" should have the following comments on file "/myFileToComment.txt"
            | user0 | My first comment |
    When as "user0" gets properties of folder "/myFileToComment.txt" with
          | {http://owncloud.org/ns}comments-href |
          | {http://owncloud.org/ns}comments-count |
          | {http://owncloud.org/ns}comments-unread |
    Then the single response should contain a property "{http://owncloud.org/ns}comments-count" with value "1"

Expected behaviour:

That property should have the number of comments.

Actual behaviour

That property gets incremented and never decremented. Removing the user doesn't make the number be reduced.

Server configuration

Operating system:
Ubuntu 16.04

Web server:
Apache

Database:
MySQL

PHP version:
7.0

ownCloud version: (see ownCloud admin page)
Current master
{"installed":"true","maintenance":"false","needsDbUpgrade":"false","version":"10.0.0.3","versionstring":"10.0.0 alpha","edition":"Community","productname":"ownCloud"}

Updated from an older ownCloud or fresh install:
Fresh

The content of config/config.php:

Are you using external storage, if yes which one: local/smb/sftp/...
No

Are you using encryption:
No

Logs

Client configuration

guzzle client.

[ownclouders]

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

[ownclouders]

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

[paurakhsharma]

PR #31592 verifies this issue doesn't exist anymore so closing the issue

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.