[Bug]: Failed sending heartbeat, got: undefined

ChristophWurst commented 1 year ago

⚠️ This issue respects the following points: ⚠️

[X] This is a bug, not a question or a configuration/webserver/proxy issue.
[X] This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
[X] Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
[X] I agree to follow Nextcloud's Code of Conduct.

Bug description

I saw this in my browser console. I don't know if/how it's a bug but it smells like one.

PUT https://localhost/ocs/v2.php/apps/user_status/api/v1/heartbeat?format=json returns 204.

Steps to reproduce

Open a Nextcloud page
Wait and watch the browser console

Expected behavior

No status heartbeat failure

Installation method

None

Nextcloud Server version

master

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

[ ] Default user-backend (database)
[ ] LDAP/ Active Directory
[ ] SSO - SAML
[ ] Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

Failed sending heartbeat, got: undefined UserStatus.vue:210
Failed sending heartbeat, got: undefined UserStatus.vue:210
Failed sending heartbeat, got: undefined UserStatus.vue:210

Additional info

No response

szaimen commented 1 year ago

cc @Antreesy @nickvergessen

Antreesy commented 1 year ago

Can't reproduce it ATM. Have you set some statuses in advance? Point to the code: https://github.com/nextcloud/server/blob/b8c3f6bd2d91a1056931a5098d024dd2772d70e2/apps/user_status/src/UserStatus.vue#L201-L212

Documentation is empty about it, but maybe I'm looking in wrong place: https://docs.nextcloud.com/server/latest/developer_manual/client_apis/OCS/ocs-status-api.html?highlight=user_status

ChristophWurst commented 1 year ago

I don't use statuses on my dev env.

ChristophWurst commented 1 year ago

I noticed that there is a GET https://localhost/ocs/v2.php/apps/user_status/api/v1/statuses/_admin with a response status 500 when I open the status modal. My user's UID is admin, not _admin. This might be related.

Antreesy commented 1 year ago

I noticed that there is a GET https://localhost/ocs/v2.php/apps/user_status/api/v1/statuses/_admin with a response status 500 when I open the status modal.

Underscore is added to fetch the backup status: https://docs.nextcloud.com/server/latest/developer_manual/client_apis/OCS/ocs-status-api.html?highlight=user_status#fetch-a-user-s-backup-status . On my local, it's 404:

 "ocs": {  "meta": {
            "status": "failure",
            "statuscode": 404,
            "message": "No status for the requested userId"
        },  "data": [],
}

ChristophWurst commented 9 months ago

This still happens for, now on production.

wargreen commented 7 months ago

Same here, but line 161. NC 28.0.2

nextcloud / server