502 on the issues dashboard without search filters

https://gitlab.com/dashboard/issues throw a 502 error. @rspeicher pointed out that this doesn't happen if you filter by ?assignee_id=[user id].

/cc @stanhu @yorickpeterse

https://gitlab.com/dashboard/merge_requests does load for me, although it takes a while.

https://gitlab.com/dashboard/merge_requests times out for me, whereas https://gitlab.com/dashboard/merge_requests?assignee_id=15139 loads in about 2 seconds (still not great).

But that makes me wonder if we're getting all merge requests, and then applying a default filter of the current user's ID, rather than applying the current_user condition immediately to further limit the set.

SQL output from gitlab-profiler: http://profiler.gitlap.com/20170522/92072dc9-7bda-425b-8ca4-11363a01ea10.txt.gz

mentioned in issue #33009 (closed)

So @northrup, @DouweM and myself argued about this for a few minutes.

I think when there's no parameters, we should do the smart thing behind the scenes and add an implicit ?assignee_id=[my user id] parameter. As it is now, if you just go to the URL (i.e., not from the drop-down menu), it loads every merge request you have access to, which is fairly useless in addition to performing terribly.

I think this is a duplicate of https://gitlab.com/gitlab-org/gitlab-ce/issues/25504?

It's also not a regression as I created that in December

removed regression label

moved to gitlab#10045

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue