Problem/Motivation

The ddev rebuild command deletes everything which is not really needed and can create a weird situation where things aren't loaded as expected, e.g. the transaction isolation level is not properly set to 'READ COMMITTED' and this results in a warning.

Steps to reproduce

Install Drupal CMS via DDEV, run ddev rebuild and confirm there is a warning about the transaction isolation level on the status report.

Proposed resolution

Update the rebuild command to be less aggressive.

CommentFileSizeAuthor
#22 Screenshot 2025-01-08 at 16.12.19.png107.31 KBdunx

Issue fork drupal_cms-3497775

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

pameeela created an issue. See original summary.

pameeela credited dunx.

pameeela’s picture

pameeela commented
pameeela’s picture

pameeela commented

Hmm. DDEV docs say this should be done by default: https://ddev.readthedocs.io/en/stable/users/usage/cms-settings/#database...

pameeela’s picture

pameeela commented

I think this must be new-ish because I don't remember seeing it before, and it's not included in #3492115: Audit warning messages shown in the status report after installation. Perplexing.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented

That is weird. I think probably we should run this past @rfay.

pameeela’s picture

pameeela commented

Yeah, chatting in Slack. Seems to be something funny about ddev rebuild, it goes away if I run ddev restart.

So that deletes all of the docroot, which means the settings.ddev.php is gone until you do a ddev restart after laying down the code again

pameeela’s picture

pameeela commented
Status: Active » Postponed (maintainer needs more info)

@dunx not sure if you're following this issue but wondering how you installed? If you were using the zip file, you shouldn't see this warning.

pameeela’s picture

pameeela commented

I'm also seeing the warning on a new install from the repo using ddev start.

pameeela’s picture

pameeela commented
Title: Set transaction isolation level to 'READ COMMITTED' in DDEV config » Update ddev rebuild command to be less aggressive
Issue summary: View changes

phenaproxima opened merge request !394

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented
Assigned: Unassigned » pameeela
Status: Postponed (maintainer needs more info) » Needs review

phenaproxima credited rfay.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented
Title: Update ddev rebuild command to be less aggressive » Make the `ddev rebuild` command less aggressive

Crediting @rfay for some input in Slack.

pameeela’s picture

pameeela commented
Status: Needs review » Reviewed & tested by the community

Confirmed this works as expected.

  • phenaproxima committed e5186cb0 on 1.x 
    Issue #3497775 by phenaproxima, pameeela, dunx, rfay: Make the `ddev...
phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented
Assigned: pameeela » Unassigned
Status: Reviewed & tested by the community » Fixed

Merged into 1.x and cherry-picked to 1.0.x. Thanks!

  • phenaproxima committed 46a93e86 on 1.0.x 
    Issue #3497775 by phenaproxima, pameeela, dunx, rfay: Make the `ddev...
dunx’s picture

dunx commented

I was using the zip file @pameeela - basically following everything under the "Try it locally" heading of https://new.drupal.org/drupal-cms/release-candidate

I'll re-test all of these Status Report Warning issues today using the latest 1.x. I'll have a play around with ddev rebuild and ddev restart and report back.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented

ddev rebuild is not part of the zip file and never will be. It’s only for internal development. So no need to pay any further attention to this. :)

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented
Component: General » Infrastructure
dunx’s picture

dunx commented
StatusFileSize
new Screenshot 2025-01-08 at 16.12.19.png107.31 KB

I performed a latest install from git:

git clone https://git.drupalcode.org/project/drupal_cms.git
cd drupal_cms
ddev config --project-type=drupal11 --docroot=web --php-version=8.3
ddev start
ddev composer install 
ddev launch

Now admittedly, it did take a few attempts to get what I wanted, but the final build was preceded by a:
ddev stop --omit-snapshot --remove-data
which I think should have resulted in a clean install.

On completing the installation and visiting the Status Report page, I still see the "Transaction isolation level" warning.
Status report

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

You do have to do a `ddev restart` one time. After doing that and moving on with the `ddev rebuild` command I expect you won't see the warning. The command to set up the database happens on start (post start) with a Drupal project.

dunx’s picture

dunx commented

I can confirm that if you perform a ddev restart on your container then this status warning goes away.

I came to this issue because I was seeing the warning after running the launch-drupal-cms.sh script that "we" had provided for people to "Try it out locally" at https://new.drupal.org/drupal-cms/release-candidate.

I'm not sure how we'll be asking people to install Drupal CMS 1.0, but if we can add a ddev restart to any script provided that would be good. Does anybody know here whether the same script-based launcher will be used or something else, so I can raise this as a separate issue for that script?

Status: Fixed » Closed (fixed)

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