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

Duplicated/empty row on My Repositories on Organization dashboard #695

Closed
2 tasks done
jomp16 opened this issue Jan 18, 2017 · 13 comments
Closed
2 tasks done

Duplicated/empty row on My Repositories on Organization dashboard #695

jomp16 opened this issue Jan 18, 2017 · 13 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@jomp16
Copy link
Contributor

jomp16 commented Jan 18, 2017

  • Gitea version (or commit ref): 1.0.0+133-gd2bb8ef5
  • Git version: 2.11.0
  • Operating system: Arch Linux
  • Database (use [x]):
    • MySQL
  • Can you reproduce the bug at https://try.gitea.io:
    • No (not sure tho).

Description

I created a new organization and changed the owner of repository to that organization. That worked perfectly.

But I found something strange on Organization dashboard:

The empty row on "my repositories" just links to the Organization url.

Excepted result is:

(I removed the empty rows with Chrome inspector).

I don't know if the way I did to change ownership from me to a organization is wrong, or this is a Gitea bug.

@tboerger
Copy link
Member

Duplicate of #56, please try to reproduce a big first on try.gitea.io which is always running latest master.

@tboerger tboerger added the issue/duplicate The issue has already been reported. label Jan 18, 2017
@jomp16
Copy link
Contributor Author

jomp16 commented Jan 18, 2017

I guess I didn't ask for theme support? Maybe you linked the wrong issue number?

And I also guess try.gitea.io isn't always updated, because version: 1.0.0+116-g69b86378.

But yeah, I don't see it on try.gitea.io. Update it to latest master and I can check it again.

I'll build with commit 69b8637 (to match try.gitea.io) and check if issue is on my side or some recent commit broke it.

--

Not a bug on my side, I build with version: 1.0.0+116-g69b86378 and it correctly show all the six repositories, without any empty <li> tag.

Did you misunderstand my issue?

--

I guess I need to find the faulty commit...

@jomp16
Copy link
Contributor Author

jomp16 commented Jan 19, 2017

I found the faulty commit: 302fa42.

Tested the commit before that (which is 88f45ce) and it didn't give out empty <li> tags.

I'm not sure why this commit gives an empty <li> tags, because it never touched the template file.

Maybe this line? 302fa42#diff-97681c8a2932ea3c23325d3518374d98R608

I'll revert this commit and see the results

--

Yep, reverting that commit renders the "My repositories" correctly without any extra empty <li> , but I really not sure the why.

--

@tboerger can you reopen this?

@tboerger
Copy link
Member

#564 is the correct issue and the referenced pull request should have fixed that.

@tboerger
Copy link
Member

And try.gitea.io is always the latest version... It shows 1.0.0 + 116 commits.

If your issue still isn't resolved please explain more details.

@jomp16
Copy link
Contributor Author

jomp16 commented Jan 19, 2017 via email

@lunny
Copy link
Member

lunny commented Jan 19, 2017

try.gitea.io seems not the latest version. It's 1.0.0+116-g69b86378, but it should 1.0.0+134-g3c4d5e1e.

@bkcsoft
Copy link
Member

bkcsoft commented Jan 20, 2017

^ I've noticed that try. isn't always updated as well, though I assumed it was drone being slow on the builds...

@lunny
Copy link
Member

lunny commented Jan 20, 2017

@tboerger

@jomp16
Copy link
Contributor Author

jomp16 commented Jan 25, 2017

And since try.gitea.io is updated (1.0.0+149-g8bc43195). I can reproduce this bug on it.

http://i.imgur.com/XHg2PyK.png

@tboerger now reopen this. You can reproduce this bug by switching to Organization on Dashboard. Like I said.

All teh info is on comments above.

@Bwko
Copy link
Member

Bwko commented Jan 25, 2017

Possible duplicate of #746?

@jomp16
Copy link
Contributor Author

jomp16 commented Jan 25, 2017

Possible, but I reported first, and nobody believed me :)

Anyways, if it's a known issue now. Good :)

@Bwko
Copy link
Member

Bwko commented Jan 25, 2017

@jomp16 I agree #746 is a duplicate of this issue 😉
Could you test if #749 solves your issue?

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

5 participants