Problem/Motivation

Webform 6.1.4 was released 12 Jan 2023 by: jrockowitz
https://www.drupal.org/project/webform/releases/6.1.4


Webform 6.2.0-beta5 was released on: 12 Jan 2023 by: jrockowitz
https://www.drupal.org/project/webform/releases/6.2.0-beta5
Works with Drupal: ^9.4 || ^10
Thank you, Jacob

Proposed resolution

  • Change drupal/webform to ~6.1.0 in the composer.json on the 9.0.x branch
  • Remove the committed patch for #3283614: Support PHP 8.1 on Varbase 9.0.x branch with the latest stable Webform version ( not to use a beta testing version on production sites )
  • Change drupal/webform to ~6.2.0 in the composer.json on the 10.0.x branch
  • Test Webform 6.2.0-beta5 with Varbase 10.0.x branch only

Remaining tasks

  • ✅ File an issue about this project
  • ✅ Addition/Change/Update/Fix to this project
  • ✅ Testing to ensure no regression
  • ➖ Automated unit/functional testing coverage
  • ➖ Developer Documentation support on feature change/addition
  • ➖ User Guide Documentation support on feature change/addition
  • ➖ Accessibility and Readability
  • ✅ Code review from 1 Varbase core team member
  • ✅ Full testing and approval
  • ✅ Credit contributors
  • ✅ Review with the product owner
  • ✅ Update Release Notes and Update Helper on new feature change/addition
  • ✅ Release varbase-9.0.11, varbase_core-9.0.43, varbase_core-9.0.44

Varbase update type

  • ✅ No Update
  • ➖ Optional Update
  • ➖ Forced Update
  • ➖ Forced Update if Unchanged

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • Issue #3333038: Updated Webform from 6.1.3 to 6.1.4 ( ~6.1.0 ) and removed committed patches

Comments

Rajab Natshah created an issue. See original summary.

rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Assigned: rajab natshah » mohammed j. razem
Issue summary: View changes
Status: Active » Needs review
Issue tags: +varbase-9.0.11, +varbase_core-9.0.43
rajab natshah’s picture

Assigned: mohammed j. razem » Unassigned
rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Issue summary: View changes
Status: Needs review » Fixed

✅ Released varbase_core-9.0.43

rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Related issues: +#3283614: Support PHP 8.1
rajab natshah’s picture

Title: Update Webform from 6.1.3 to 6.1.4 ( ~6.0 ) and keep needed patches » Update Webform from 6.1.3 to 6.1.4 ( ~6.1.0 ) and remove committed patches
Issue summary: View changes
Issue tags: +varbase_core-9.0.44
rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Assigned: Unassigned » mohammed j. razem
Issue summary: View changes
Status: Fixed » Needs review

✅ Released varbase_core-9.0.44
Removed the patch.
Faced issue with composer not getting latest commit changes on packages from https://packages.drupal.org/8


https://twitter.com/drupal_infra/status/1613594516958904320

http://Git.drupalcode.org is experiencing 'Geo' replication lag, which is resulting in composer and CI failures for Merge Requests, delayed d.o issue updates, etc. We are working to find a resolution, and have filed an upstream issue with
@gitlab
: https://gitlab.com/gitlab-org/gitlab/-/issues/387980

Geo verification not keeping up
For the last few weeks, repositories and wikis verifications on our geo secondary for git.drupalcode.org have been gradually falling behind.

I think this may have started with the 15.5 to 15.6.1 upgrade. Since the falling behind was very gradual, and it was over the holidays, I was monitoring but did not take any measures to correct it.
Around this upgrade, we stabilized our upgrade process, stopping sidekiq processes early before the upgrade, so long-running jobs can complete in time. We also aligned our upgrade process with the current instructions https://docs.gitlab.com/ee/administration/geo/replication/upgrading_the_...
After upgrading to 15.7.2, what we are currently running, verifications have fallen further behind, losing maybe a percent a day.
/admin/geo/sites reports all instances are healthy.
The primary site's verifications have been 99.9% or higher.
sudo gitlab-rake gitlab:geo:check reports everything is good on both primary and secondary sites.
On the secondary geo site:
In the tuning settings, we doubled the verification concurrency limit 3 times, currently to 800
We added a second Sidekiq process, both having 20 threads. We have not seen any Sidekiq backlog.
It does not appear resource constrained, CPU usage is 10% or less, load average 2-3, ~50% free memory.
We have 86,500 repositories.
I've reviewed https://docs.gitlab.com/ee/administration/geo/replication/troubleshootin... and haven't spotted anything helpful for our situation.
None of these measures seem to have had much of an effect on the secondary's verification queue, it is still gradually falling further behind.

I'd like recommendations for finding potential underlying issues, and ways to get verification caught up.

rajab natshah’s picture

Assigned: mohammed j. razem » Unassigned
rajab natshah’s picture

Status: Needs review » Fixed
rajab natshah’s picture

Issue summary: View changes

✅ Released varbase-9.0.11

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.