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 RSpec@ mention meIn 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"
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? π
@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/ π
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
gdk update third time it is resolved... π
gdk update they get i back to work π
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
ERROR: While executing gem ... (Gem::Exception)
Failed to find gems ["charlock_holmes"] >= 0bundle pristine charlock_holmesgdk update
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