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

404 Not found error on blob_excerpt expansion #10851

Closed
2 tasks done
sosak009 opened this issue Mar 27, 2020 · 11 comments · Fixed by #12434
Closed
2 tasks done

404 Not found error on blob_excerpt expansion #10851

sosak009 opened this issue Mar 27, 2020 · 11 comments · Fixed by #12434
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug

Comments

@sosak009
Copy link

sosak009 commented Mar 27, 2020

Description

Hi, gitea returns HTTP/404 not found on a blob_excerpt request while trying to expand the code in pull_request/review conversation (as seen on screenshot). This bug is also reproducable in testing gitea environment.

Request URL example:
Request URL: https://try.gitea.io/testinguserXY/my_bugtest/blob_excerpt/?last_left=0&last_right=0&left=35&right=35&left_hunk_size=6&right_hunk_size=7&path=testfile&style=unified&direction=up&anchor=diff-e05fcb614ab36fdee72ee1f2754ed85e2bd0e8d0K35

Thanks in advance

Screenshots

blob_excerpt
image

@sosak009 sosak009 changed the title 400 Not found error on blob_excerpt expansion 404 Not found error on blob_excerpt expansion Mar 27, 2020
@stale
Copy link

stale bot commented May 30, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label May 30, 2020
@a1012112796
Copy link
Member

Sadly, It still exists :(

image

@stale stale bot removed the issue/stale label May 30, 2020
@stale
Copy link

stale bot commented Jul 29, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Jul 29, 2020
@sosak009
Copy link
Author

sosak009 commented Aug 3, 2020

Issue still present

@stale stale bot removed the issue/stale label Aug 3, 2020
@zeripath
Copy link
Contributor

zeripath commented Aug 3, 2020

I just tried the provided url: https://try.gitea.io/testinguserXY/my_bugtest/pulls/3 and couldn't reproduce.

@zeripath
Copy link
Contributor

zeripath commented Aug 3, 2020

@sosak009 what version of Gitea is this present in?

@sosak009
Copy link
Author

sosak009 commented Aug 3, 2020

@sosak009 what version of Gitea is this present in?

I just reproduced it on the try.gitea.io ...

Request URL: https://try.gitea.io/testinguserXY/my_bugtest/blob_excerpt/?last_left=0&last_right=0&left=35&right=35&left_hunk_size=6&right_hunk_size=7&path=testfile&style=unified&direction=up&anchor=diff-e05fcb614ab36fdee72ee1f2754ed85e2bd0e8d0K35
Request Method: GET
Status Code: 404 

@lunny
Copy link
Member

lunny commented Aug 4, 2020

@sosak009 Cannot reproduce it on macOS & firefox

@zeripath
Copy link
Contributor

zeripath commented Aug 4, 2020

@zeripath zeripath added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Aug 4, 2020
@zeripath
Copy link
Contributor

zeripath commented Aug 4, 2020

Now the question is what should that arrow do? Should it just redirect to the files page? Should it even exist?


I suspect the answer is it shouldn't exist.

@lunny
Copy link
Member

lunny commented Aug 5, 2020

Just remove that up arrow.

zeripath added a commit to zeripath/gitea that referenced this issue Aug 5, 2020
Prior to this PR it was possible that an expansion arrow could be displayed
on comment diffs displayed on the comments pages of pulls

These arrows would not successfully work because they were not attached to
a commit id - nor can they necessarily be.

This PR prevents these from being shown.

Fix go-gitea#10851

Signed-off-by: Andrew Thornton <[email protected]>
lunny pushed a commit that referenced this issue Aug 8, 2020
* Do not show arrows on comment diffs on pull comment pages

Prior to this PR it was possible that an expansion arrow could be displayed
on comment diffs displayed on the comments pages of pulls

These arrows would not successfully work because they were not attached to
a commit id - nor can they necessarily be.

This PR prevents these from being shown.

Fix #10851

Signed-off-by: Andrew Thornton <[email protected]>

* as per @silverwind

Signed-off-by: Andrew Thornton <[email protected]>

* one more indentation fix

Signed-off-by: Andrew Thornton <[email protected]>

* one more indentation fix

Signed-off-by: Andrew Thornton <[email protected]>
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants