nextcloud / nextcloud/integration_gitlab
404 error in logs if user have no access to project
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 49
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce
- Install plugin
- Open nextcloud talk and send link to issue to user, user dos not have access to this project in Gitlab
- See nextcloud log for errors
Expected behaviour
Not supose to be errors in log
Actual behaviour
Error in logs:
{"reqId":"2HPePL6Rp0QUrITRvgoH","level":2,"time":"2025-03-19T12:50:34+00:00","remoteAddr":"193.194.100.4","user":"gitlab_oidc-3","app":"integration_gitlab","method":"GET","url":"/ocs/v2.php/references/resolve?reference=%0Ahttps%3A%2F%2Fgitlab.uco.co.il%2Ffixdigital%2Flms.fixdigital.co.il%2F-%2Fissues%2F2203%0A","message":"GitLab API error : Client error: GET https://gitlab.uco.co.il/api/v4/projects/fixdigital%2Flms.fixdigital.co.il` resulted in a 404 Not Found response:\n{"message":"404 Project Not Found"}\n","userAgent":"Mozilla/5.0 (Windows) Nextcloud-Talk v1.1.5","version":"31.0.1.2","data":{"app":"integration_gitlab"},"id":"67dabe541aac0"}`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the /ocs/v2.php/references/resolve request shown in the log and the GitLab project lookup for users without project access. Reproduce the shared issue link in Nextcloud Talk, then verify that an inaccessible or missing project no longer produces an error-level log entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100