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.

Sign up for GitHub

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

Jump to bottom

Error when navigating to an organisations Issue/Pull Request/Milestone page #18229

Closed
eeyrjmr opened this issue Jan 10, 2022 · 3 comments · Fixed by #18314
Closed

Error when navigating to an organisations Issue/Pull Request/Milestone page #18229

eeyrjmr opened this issue Jan 10, 2022 · 3 comments · Fixed by #18314
Labels
issue/regression Indicates a previously functioning feature or behavior that has broken or regressed after a change type/bug
Milestone
1.16.0

Comments

@eeyrjmr
Copy link
Contributor

eeyrjmr commented Jan 10, 2022 •
edited
Loading

Gitea Version

1.16.0+dev-825-gaf9247392

Git Version

2.34

Operating System

Windows

How are you running Gitea?

Console/ service

Database

SQLite

Can you reproduce the bug on the Gitea demo site?

No - only because unable to create organisations

Log Gist

https://gist.github.com/eeyrjmr/da0e4db660632599685d4019953ddb74

Description

When you navigate to an organisations page and try to click on Issue/Pull Request/Milestone page you are presented with a 500 error

This does not happen with 1.15.x

steps to recreate

  1. make an organization (eg test)
  2. navigate to the organization dashboard ( http://localhost:3000/org/test/dashboard)
  3. click on issues ( http://localhost:3000/org/test/issues )

Screenshots

Annotation 2022-01-10 190315
@lunny
Copy link
Member

lunny commented Jan 12, 2022

Could you give some logs? Or you can change run_mode to dev and the error will be displayed in the 500 page.

@eeyrjmr
Copy link
Contributor Author

eeyrjmr commented Jan 12, 2022 •
edited
Loading

here is a log
Steps

  1. fresh "install" of gitea - ie delete all directories
  2. configure gitea
  3. stop gitea
  4. edit app.ini
    RUN_MODE = dev
    log.LEVEL = debug
    log.MODE = file
    log.COLORIZE=false
  5. restart gitea
  6. sign in
  7. create new ORG = test
  8. click on issue ( http://localhost:3000/org/test/issues)
  9. click on pull request ( http://localhost:3000/org/test/pulls)
  10. click on milestones ( http://localhost:3000/org/test/milestones)

The organisation landing page
Annotation 2022-01-12 230110

Fail - while no issues, this occurs if there are issues
Annotation 2022-01-12 230133

Fail - while no PR, this occurs if there are PR
Annotation 2022-01-12 230155

Works
Annotation 2022-01-12 230229

Logfile
gitea.log

@zeripath zeripath added this to the 1.16.0 milestone Jan 15, 2022
@zeripath zeripath added the issue/regression Indicates a previously functioning feature or behavior that has broken or regressed after a change label Jan 15, 2022
@wxiaoguang
Copy link
Contributor

It looks like a regression bug of

zeripath added a commit to zeripath/gitea that referenced this issue Jan 17, 2022
@zeripath
Prevent ambiguous column error in organizations page
84560fd 
Explicitly set the table for the org_id column queries on the organizations pages.

Fix go-gitea#18229

Signed-off-by: Andrew Thornton <art27@cantab.net>
@zeripath zeripath mentioned this issue Jan 17, 2022
Merged
zeripath added a commit that referenced this issue Jan 18, 2022
@zeripath
Prevent ambiguous column error in organizations page (#18314)
a7ee4d5 
Explicitly set the table for the org_id column queries on the organizations pages.

Fix #18229

Signed-off-by: Andrew Thornton <art27@cantab.net>
Chianina pushed a commit to Chianina/gitea that referenced this issue Mar 28, 2022
@zeripath
Prevent ambiguous column error in organizations page (go-gitea#18314)
9453382 
Explicitly set the table for the org_id column queries on the organizations pages.

Fix go-gitea#18229

Signed-off-by: Andrew Thornton <art27@cantab.net>
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/regression Indicates a previously functioning feature or behavior that has broken or regressed after a change type/bug
Projects
None yet
Milestone
1.16.0
Development

Successfully merging a pull request may close this issue.

Prevent ambiguous column error in organizations page zeripath/gitea
5 participants
@lunny @axifive @zeripath @wxiaoguang @eeyrjmr