500 error, Unable to view organisation Dashboard when using MSSQL. #1107

New Issue

GiteaMirror · 2025-11-02T03:48:56-06:00

GiteaMirror commented

2025-11-02 03:48:56 -06:00

Originally created by @sgtwilko on GitHub (Sep 29, 2017).

Gitea version (or commit ref): 1.2.0+rc1-6-g002fa73 built with: bindata, sqlite
Git version: 2.14.1.windows.1
Operating system: Windows Server 2008R2
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant (I did try but couldn't replicate because try.gitea.io probably isn't using MSSQL for the database)
Log gist:

[...routers/user/home.go:137 Dashboard()] [E] env.MirrorRepos: MirrorRepoIDs: mssql: Column "repository.updated_unix" is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the GROUP BY clause.

Description

When changing to view an organisation dashboard you receive a 500 error.

Screenshots

Originally created by @sgtwilko on GitHub (Sep 29, 2017). - Gitea version (or commit ref): `1.2.0+rc1-6-g002fa73 built with: bindata, sqlite` - Git version: `2.14.1.windows.1` - Operating system: `Windows Server 2008R2` - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [x] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant (I did try but couldn't replicate because try.gitea.io probably isn't using MSSQL for the database) - Log gist: `[...routers/user/home.go:137 Dashboard()] [E] env.MirrorRepos: MirrorRepoIDs: mssql: Column "repository.updated_unix" is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the GROUP BY clause.` ## Description When changing to view an organisation dashboard you receive a 500 error. ## Screenshots ![image](https://user-images.githubusercontent.com/658876/31009798-917833c0-a500-11e7-8fec-6b2b47aa6d05.png)

GiteaMirror added the issue/duplicate label 2025-11-02 03:48:56 -06:00

GiteaMirror closed this issue

2025-11-02 03:48:56 -06:00

GiteaMirror commented

2025-11-02 03:48:57 -06:00

@ethantkoenig commented on GitHub (Sep 30, 2017):

I believe this has already been fixed: https://github.com/go-gitea/gitea/pull/2504

@ethantkoenig commented on GitHub (Sep 30, 2017): I believe this has already been fixed: https://github.com/go-gitea/gitea/pull/2504

GiteaMirror commented

2025-11-02 03:48:57 -06:00

@sgtwilko commented on GitHub (Oct 5, 2017):

Sorry for reporting a duplicate, I did search the issues before posting, but not the pull requests.

I've just upgraded to 1.2.0+rc3-4-g5b36379 which still has this issue, any idea if this fix make it into the final 1.2.0?

@sgtwilko commented on GitHub (Oct 5, 2017): Sorry for reporting a duplicate, I did search the issues before posting, but not the pull requests. I've just upgraded to 1.2.0+rc3-4-g5b36379 which still has this issue, any idea if this fix make it into the final 1.2.0?

GiteaMirror commented

2025-11-02 03:48:57 -06:00

@lafriks commented on GitHub (Oct 5, 2017):

@sgtwilko yes this fix will be backported to 1.2 branch

@lafriks commented on GitHub (Oct 5, 2017): @sgtwilko yes this fix will be backported to 1.2 branch

GiteaMirror commented

2025-11-02 03:48:57 -06:00

@lafriks commented on GitHub (Oct 5, 2017):

Backport submitted as PR #2662

@lafriks commented on GitHub (Oct 5, 2017): Backport submitted as PR #2662

GiteaMirror commented

2025-11-02 03:48:58 -06:00