One hour ago there was a merge into master that fix these errors
gitlab-org/gitlab@990e693
spec/lib/gitlab/audit/target_spec.rb: Rspec/VerifiedDoubles has the wrong namespace - should be RSpec
spec/models/concerns/database_event_tracking_spec.rb: Rspec/LeakyConstantDeclaration has the wrong namespace - should be RSpec
spec/models/concerns/database_event_tracking_spec.rb: Rspec/ExpectGitlabTracking has the wrong namespace - should be RSpecgitlab-org/gitlab@990e693
But it wasn't enough to solve the long time to run :(
I think I have a clue... As community, our runner for this job is a shared runner (green.shared-gitlab-org.runners-manager.gitlab.com) and maybe the server is overloaded for now. I have already run successfully the complete pipeline in the morning from my timezone. I will retry tomorrow morning...
[Lee Tickett, GitLab] I would just callout in the MR why you made that change
Feel free to
Thank you for another contribution +1
Feel free to
@ mention meThank you for another contribution +1
In documentation I see https://about.gitlab.com/handbook/engineering/quality/triage-operations/#reactive-label-command
A new MR note that start with @gitlab-bot label ~"label-name" where label-name matches group::, type:: or is ~"workflow::in dev" or ~"workflow::ready for review"
I want to add backend in this MR to help gitlab-bot to find correct reviewer: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/95175#note_1059848183
Good point @aliokan 🙂 Right now only a subset of labels can be set with the help of gitlab-bot, and as you pointed out frontend and backend are not included 🤔
WDYT about opening an issue to ask to allow them? 🙂
1 reply
Yup 🙂 By opening an issue we could start the discussion 🙂 For example, now that danger reports when the subtype label us missing, should we allow to also set subtype labels?
hi! I am a first time contributor, how can I get started? I would love to contribute code and docs. I am a newbie.
1 reply
Hello friends! This Thursday at 1:30 UTC we are holding a Release Stage office hour call! See you then! https://www.meetup.com/gitlab-virtual-meetups/events/287756492/
[Lee Tickett, GitLab] Hoping to work on gitlab-org/gitlab!88243 during community pair programming around 11am BST. Feel free to join us https://www.twitch.tv/gitlabcommunitycoders and discord https://discord.com/channels/778180511088640070/998578723416711249
Hello everyone! Anyone knows who closes an issue and when can it be done? I have 3 issues that have its linked MRs merged and I don't know if it is me who should close them or if this should be done by the creator (that is not me). Any advice is welcome.
2 replies
Here you are @nick_vh.gitlab_gitlab :
gitlab-org/gitlab#369555
gitlab-org/gitlab#369554
gitlab-org/gitlab#369469
gitlab-org/gitlab#369555
gitlab-org/gitlab#369554
gitlab-org/gitlab#369469
@anshulriyal_gitlab: i Guess you’re talking about the backpack right? 🙂 Christos pointed me to the backpack initiative page where the is a link to the form to request the backpack in case you haven’t been contacted 🙂
This is the page: https://about.gitlab.com/community/contribute/development/backpacking/ 🙂
1 reply
Everytime when I try to run
gdk update... I am getting the following error when db migration is running rails aborted!
ActiveRecord::StatementInvalid: PG::AmbiguousColumn: ERROR: column reference "id" is ambiguous
LINE 1: ...paces ON members.source_id = namespaces.id WHERE ("id" >= 1)...
^
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/connection_proxy.rb:100:in `block in read_using_load_balancer'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/load_balancer.rb:115:in `block in read_write'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/load_balancer.rb:184:in `retry_with_backoff'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/load_balancer.rb:111:in `read_write'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/connection_proxy.rb:99:in `read_using_load_balancer'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/connection_proxy.rb:48:in `select_all'
/home/edith/gitlab-development-kit/gitlab/app/models/concerns/each_batch.rb:62:in `each_batch'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/background_migration/batching_strategies/primary_key_batching_strategy.rb:38:in `next_batch'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:105:in `find_next_batch_range'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:94:in `find_or_create_next_batched_job'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:29:in `run_migration_job'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:140:in `run_migration_while'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:49:in `run_entire_migration'
/home/edith/gitlab-development-kit/gitlab/lib/tasks/gitlab/db.rake:339:in `block (5 levels) in <main>'
/home/edith/gitlab-development-kit/gitlab/lib/tasks/gitlab/db.rake:337:in `block (4 levels) in <main>'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/each_database.rb:17:in `block (2 levels) in each_database_connection'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/each_database.rb:77:in `block in with_shared_connection'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/shared_model.rb:34:in `using_connection'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/each_database.rb:74:in `with_shared_connection'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/each_database.rb:16:in `block in each_database_connection'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/each_database.rb:11:in `each_pair'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/each_database.rb:11:in `each_database_connection'
/home/edith/gitlab-development-kit/gitlab/lib/tasks/gitlab/db.rake:336:in `block (3 levels) in <main>'
/home/edith/gitlab-development-kit/gitlab/lib/tasks/gitlab/db.rake:367:in `block (3 levels) in <main>'
Caused by:
PG::AmbiguousColumn: ERROR: column reference "id" is ambiguous
LINE 1: ...paces ON members.source_id = namespaces.id WHERE ("id" >= 1)...
^
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/connection_proxy.rb:100:in `block in read_using_load_balancer'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/load_balancer.rb:115:in `block in read_write'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/load_balancer.rb:184:in `retry_with_backoff'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/load_balancer.rb:111:in `read_write'
/home/edith/gitlab-development-kit/gitlab/lib/gitlab/database/load_balancing/connection_proxy.rb:99:in `read_using_lo
am I only one getting this error??
After I tried to run
gdk update third time it is resolved... 😅
Yeah, GDK can act a little bit funky sometimes 🙂 I know others that do experience problems somewhat similar to these and after some runs of
gdk update they get i back to work 🙂
Friendly reminder that we are hosting a regular office hour call (without a specific topic) later today https://www.meetup.com/gitlab-virtual-meetups/events/287787579
Why can't I login in into this? The credentials is
root and 12345678, right?
Hi all! To everyone interested, we created an issue to gather ideas/topics for our next pairing session we'll have on Tuesday 🙂 Feel free to take a look and submit any idea 🙂
If there are multiple suggestions, we won't be able to do them all but we'll keep track so that, sooner or later, we can give them a shot 🙂
Here's the issue for Tuesday 6th of September: community-coders/pairing-sessions#7
[Lee Tickett, GitLab] We will be holding our usual weekly community pairing session Tuesday @10.15 UTC
Here's the issue link: community-coders/pairing-sessions#9
Hope to see you there!
Here's the issue link: community-coders/pairing-sessions#9
Hope to see you there!
[Lee Tickett, GitLab] Hi Friends, some of us are seeing an error when updating GDK on Mac. Something along the lines of:
The fix is to run:
Then re-run
ERROR: While executing gem ... (Gem::Exception)
Failed to find gems ["charlock_holmes"] >= 0The fix is to run:
bundle pristine charlock_holmesThen re-run
gdk update
Friends, the Contributor Success team just published an exciting blogpost for pursuing faster time-to-merge for wider community contributions! https://about.gitlab.com/blog/2022/09/13/pursuing-faster-time-to-merge-for-wider-community-contributions/
Hi all! 😄
The issue for next week's pairing session is available for you to suggest topics! 🙂
Here it is: community-coders/pairing-sessions#18
[Lee Tickett, GitLab] We should add a few of our pairing session issues (like creating the bots etc).
Also gitlab-org/quality/triage-ops#1100 as it'd be cool to use the reactive bit of triage-ops for our project right? Especially as we're already using the scheduled policies =D
Also gitlab-org/quality/triage-ops#1100 as it'd be cool to use the reactive bit of triage-ops for our project right? Especially as we're already using the scheduled policies =D
I could definitely use that to add it in our workflow 😄