14 ms·

Gitea is riddled with bugs and the maintainers seem to disagree they exist, which is a shame. We too just switched to bare repos and haven't really missed much

by junon 6y ago

Gitea is riddled with bugs and the maintainers seem to disagree they exist, which is a shame. We too just switched to bare repos and haven't really missed much from the SCM frontends.

codetrotter 6y ago
> and the maintainers seem to disagree they exist, which is a shame Does this extend also to the case of when someone submits a pull request to them, or only for issues that people file? If the former then it is truly problematic. If the latter they may be simply overworked/overburdened by the volume of issues that are being filed, and could need more people submitting pull requests instead of opening issues.
- MrGilbert 6y ago
  > If the latter they may be simply overworked/overburdened by the volume of issues that are being filed, and could need more people submitting pull requests instead of opening issues. Although merging and reviewing a pull request can also be quite time-consuming. If you are already overworked, it might add to the problem. I'm happy that none of my open-source projects went through the roof. I won't be able to manage it alone.
- junon 6y ago
  They aren't saying "we can't fix this right now". They're saying, straight up, "this isn't a problem".
  - freeopinion 6y ago
    Pictures or it didn't happen. One of the maintainers has responded specifically to you here and you have ignored their outreach.
    - oarsinsync 6y ago
      > One of the maintainers has responded specifically to you here and you have ignored their outreach. The maintainer has responded more recently than the GP's last comment. "ignore" feels like a stretch.
    - junon 6y ago
      Lol, "ignored". Why are you so angry? I don't check HN every waking minute of every day. In fact, I have noprocrast enabled, so I can't. Please stop assuming malice in others. You'll be a happier person. I've responded to the dev, FWIW.
Jnr 6y ago
Luckily for me Gitea has been working without any problems for some time now. And I would rather fix those issues than switch to bare repos.
- deleted 6y ago
  [deleted]
kdumont 6y ago
Gitea maintainer here :) Is there an issue/PR you can point me to? I'd be happy to take a look and see if we can get it on the roadmap. We're working on improving testing strategy to reduce new bugs. We don't include front-end in our tests right now, which is imo our biggest issue. Would love some help with the this. We just support so many platforms, databases, and config options it's difficult to catch everything. It's a great project to work on and there is plenty of room for improvement!
- hnjst 6y ago
  Thanks for your work on this nice piece of software! We created our small company last year and it has not only been our VCS (nicely integrated with Drone for CI/CD) but we also based our SSO on it (we had to add a homemade OIDC/OAUTH proxy though). I'll hopefully soon find the time to clean-up the code of said proxy and of the helm chart we wrote in order to propose a contribution to this nice project. I deployed and run Gitlab for a large company and have used it in other contexts in the past. While Gitlab's feature set is obviously much wider, Gitea is a nice trade-off when a lighter footprint is desired. Thanks again!
- junon 6y ago
  Hi. You all but shut down my criticism of the mirroring system and the fact that it fails outright if Gitea dies in the interim - sometimes even due to Gitea deadlocking itself - and insisted this was SQLite's problem and not Gitea's. That's the one example I'm referring to. Since then, we faced a number of UI bugs that we just didn't bother to report since most other attempts at reaching out were rejected as "not our problem".
  - kdumont 6y ago
    We have quite the queue of projects, but we're actually working on the mirroring system and front-end tests. See: - https://github.com/go-gitea/gitea/pull/15268 https://github.com/go-gitea/gitea/pull/15268 - https://github.com/go-gitea/gitea/pull/14726 https://github.com/go-gitea/gitea/pull/14726 - https://github.com/go-gitea/gitea/pull/15315 https://github.com/go-gitea/gitea/pull/15315 - https://github.com/go-gitea/gitea/issues/14639 https://github.com/go-gitea/gitea/issues/14639 We're a volunteer team, so any information you can add to an issue would be greatly appreciated. Even if you're not using Gitea anymore.

by junon 6y ago

Gitea is riddled with bugs and the maintainers seem to disagree they exist, which is a shame. We too just switched to bare repos and haven't really missed much from the SCM frontends.

codetrotter 6y ago

> and the maintainers seem to disagree they exist, which is a shame Does this extend also to the case of when someone submits a pull request to them, or only for issues that people file? If the former then it is truly problematic. If the latter they may be simply overworked/overburdened by the volume of issues that are being filed, and could need more people submitting pull requests instead of opening issues.

MrGilbert 6y ago
> If the latter they may be simply overworked/overburdened by the volume of issues that are being filed, and could need more people submitting pull requests instead of opening issues. Although merging and reviewing a pull request can also be quite time-consuming. If you are already overworked, it might add to the problem. I'm happy that none of my open-source projects went through the roof. I won't be able to manage it alone.
junon 6y ago
They aren't saying "we can't fix this right now". They're saying, straight up, "this isn't a problem".
- freeopinion 6y ago
  Pictures or it didn't happen. One of the maintainers has responded specifically to you here and you have ignored their outreach.
  - oarsinsync 6y ago
    > One of the maintainers has responded specifically to you here and you have ignored their outreach. The maintainer has responded more recently than the GP's last comment. "ignore" feels like a stretch.
  - junon 6y ago
    Lol, "ignored". Why are you so angry? I don't check HN every waking minute of every day. In fact, I have noprocrast enabled, so I can't. Please stop assuming malice in others. You'll be a happier person. I've responded to the dev, FWIW.

Jnr 6y ago

Luckily for me Gitea has been working without any problems for some time now. And I would rather fix those issues than switch to bare repos.

deleted 6y ago
[deleted]

kdumont 6y ago

Gitea maintainer here :) Is there an issue/PR you can point me to? I'd be happy to take a look and see if we can get it on the roadmap. We're working on improving testing strategy to reduce new bugs. We don't include front-end in our tests right now, which is imo our biggest issue. Would love some help with the this. We just support so many platforms, databases, and config options it's difficult to catch everything. It's a great project to work on and there is plenty of room for improvement!

hnjst 6y ago
Thanks for your work on this nice piece of software! We created our small company last year and it has not only been our VCS (nicely integrated with Drone for CI/CD) but we also based our SSO on it (we had to add a homemade OIDC/OAUTH proxy though). I'll hopefully soon find the time to clean-up the code of said proxy and of the helm chart we wrote in order to propose a contribution to this nice project. I deployed and run Gitlab for a large company and have used it in other contexts in the past. While Gitlab's feature set is obviously much wider, Gitea is a nice trade-off when a lighter footprint is desired. Thanks again!
junon 6y ago
Hi. You all but shut down my criticism of the mirroring system and the fact that it fails outright if Gitea dies in the interim - sometimes even due to Gitea deadlocking itself - and insisted this was SQLite's problem and not Gitea's. That's the one example I'm referring to. Since then, we faced a number of UI bugs that we just didn't bother to report since most other attempts at reaching out were rejected as "not our problem".
- kdumont 6y ago
  We have quite the queue of projects, but we're actually working on the mirroring system and front-end tests. See: - https://github.com/go-gitea/gitea/pull/15268 https://github.com/go-gitea/gitea/pull/15268 - https://github.com/go-gitea/gitea/pull/14726 https://github.com/go-gitea/gitea/pull/14726 - https://github.com/go-gitea/gitea/pull/15315 https://github.com/go-gitea/gitea/pull/15315 - https://github.com/go-gitea/gitea/issues/14639 https://github.com/go-gitea/gitea/issues/14639 We're a volunteer team, so any information you can add to an issue would be greatly appreciated. Even if you're not using Gitea anymore.