Mentionin you error

[jaqra]

After #8201 i check mentionin you group on try.gitea.io. but response 500 status code

When i check same repo on local there is no error, works well 🤔

[guillep2k]

Can you give us the URL? Perhaps an admin can check the logs

[guillep2k]

Here's a link.
https://try.gitea.io/issues?type=mentioned&repo=0&sort=&state=open
I've just registered a new test user (no activity) and the server error shows up immediately.

[guillep2k]

The error is not showing on my dev server, neither with an old user or a new one.

[guillep2k]

@lunny is it possible to get the log from try.gitea.io?

[lunny]

@guillep2k It seems try.gitea.io's log is misconfiguration. I cannot find error stack information.

[jaqra]

i created a user on gitea.com and there is no any error with that

[lunny]

@jaqra gitea.com hasn't been updated to a recent version since there are serval bugs. But I tested it locally and I cannot reproduce this.

[jaqra]

ahh sorryy

[lunny]

@jaqra @guillep2k could you confirm your local instance could reproduce this?

[guillep2k]

@lunny No, I couldn't reproduce it locally. So far the only place the problem showed up is on try.gitea.io.

[jaqra]

@lunny no. with sqlite db

[guillep2k]

In my case I use PostgreSQL

[guillep2k]

@jaqra with the help from @techknowlogick this is an excerpt of the log from the server with the error:

https://gist.github.com/techknowlogick/39b137e092c80c04212ff3c398ed4d86

SELECT count(*) FROM `issue`
INNER JOIN issue_user ON issue.id = issue_user.issue_id and issue_user.is_mentioned = ?
WHERE issue.is_pull=? AND (is_closed = ?) AND (issue_user.uid = ?)

{true, false, false, 4940}

routers/user/home.go:352:Issues() [E] GetUserIssueStats: ambiguous column name: is_closed

It looks like try.gitea.io has some extra columns in the database (in particular issue_user seems to have a is_closed column). It might be a leftover from some old migration.

@lunny is there anything that can be done about it?

[lunny]

OK. The problem is we should use issue.is_closed but not is_closed on models/issue.go:1673.

case FilterModeCreate:
		stats.OpenCount, err = x.Where(cond).And("is_closed = ?", false).
			And("poster_id = ?", opts.UserID).
			Count(new(Issue))
		if err != nil {
			return nil, err
		}
		stats.ClosedCount, err = x.Where(cond).And("is_closed = ?", true).
			And("poster_id = ?", opts.UserID).
			Count(new(Issue))
		if err != nil {
			return nil, err
		}

[guillep2k]

@lunny I've thought the same thing, but I can't explain why the error happens. There should be no two is_closed columns in that query.

It's not bad to patch those queries, though.

[guillep2k]

I'll make a PR for that.

[lunny]

When you have a join, some database ask you indicate which database's columns on the SQL even there is no conflict column names I guess.

[lunny]

And I think add a test for metion mode on func TestGetUserIssueStats(t *testing.T) will be better.

[guillep2k]

@lunny try.gitea.io is still failing. I'd wait until it gets this commit?

[guillep2k]

@lunny try.gitea.io is still failing. I'd wait until it gets this commit?

FIXED!!! 😄