The second dependency in issue is marked as private #28732
Comments
|
3 projects 2 project depends on 1 projects in the "BLOCK" section of project 1 only project 3 is displayed 1 project (blockchain): 2 project (chat): 3 project (forum): |
|
Dupe of #27722 |
sorry |
lafriks
pushed a commit
that referenced
this issue
Jan 12, 2024
Backport #27736 by @lng2020 Fix #27722 Fix #27357 Fix #25837 Fix #28732 1. Fix the typo `BlockingByDependenciesNotPermitted`, which causes the `not permitted message` not to show. The correct one is `Blocking` or `BlockedBy` 2. Rewrite the perm check. The perm check uses a very tricky way to avoid duplicate checks for a slice of issues, which is confusing. In fact, it's also the reason causing the bug. It uses `lastRepoID` and `lastPerm` to avoid duplicate checks, but forgets to assign the `lastPerm` at the end of the code block. So I rewrote this to avoid this trick.  3. It also reuses the `blocks` slice, which is even more confusing. So I rewrote this too.  Co-authored-by: Nanguan Lin <[email protected]>
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this issue
Jan 23, 2025
Backport go-gitea#27736 by @lng2020 Fix go-gitea#27722 Fix go-gitea#27357 Fix go-gitea#25837 Fix go-gitea#28732 1. Fix the typo `BlockingByDependenciesNotPermitted`, which causes the `not permitted message` not to show. The correct one is `Blocking` or `BlockedBy` 2. Rewrite the perm check. The perm check uses a very tricky way to avoid duplicate checks for a slice of issues, which is confusing. In fact, it's also the reason causing the bug. It uses `lastRepoID` and `lastPerm` to avoid duplicate checks, but forgets to assign the `lastPerm` at the end of the code block. So I rewrote this to avoid this trick.  3. It also reuses the `blocks` slice, which is even more confusing. So I rewrote this too.  Co-authored-by: Nanguan Lin <[email protected]> (cherry picked from commit 571822b)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
In the dependencies block of the issues section, the second dependency displays a lock icon with the caption "You do not have permission to view this dependency" (translated from russian)
This dependency is issue within the same public repository, and i am an administrator and should see ALL issues, even private ones
If you go to this issues directly, it is displayed without any problems
I will provide additional information upon request
Screenshots
Gitea Version
1.22.0+dev-514-gdd5693387 built with GNU Make 4.3, go1.21.4 : bindata
Can you reproduce the bug on the Gitea demo site?
Yes
Operating System
Ubuntu 22
Browser Version
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0
The text was updated successfully, but these errors were encountered: