Problem/Motivation

Tugboat fails building a fresh instance in #2634854: Add dropdowns to horizontal toolbar menu (as with 'admin toolbar' in contrib).

  • 2634854-add-admin-toolbar changes, plain diff MR !2126 mergeable
    Check out this branch

    Add test / retest

    View live preview (failed) via Tugboat View log Rebuild

    • From the log link:

      Problem 1
    - Root composer.json requires drupal/core 9.4.x, it is satisfiable by drupal/core[9.4.x-dev] from composer repo (https://repo.packagist.org) but drupal/core[dev-main] from path repo (core) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 2
    - Root composer.json requires drupal/core-project-message 9.4.x, it is satisfiable by drupal/core-project-message[9.4.x-dev] from composer repo (https://repo.packagist.org) but drupal/core-project-message[dev-main] from path repo (composer/Plugin/ProjectMessage) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 3
    - Root composer.json requires drupal/core-vendor-hardening 9.4.x, it is satisfiable by drupal/core-vendor-hardening[9.4.x-dev] from composer repo (https://repo.packagist.org) but drupal/core-vendor-hardening[dev-main] from path repo (composer/Plugin/VendorHardening) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

    Also the https://www.tugboat.qa/drupal-welcome link results in a 404 Not Found.

    Steps to reproduce

    Proposed resolution

    Remaining tasks

    User interface changes

    API changes

    Data model changes

    Comments

    ressa created an issue. See original summary.

    ressa’s picture

    ressa
    he/him
    commented
    Issue summary: View changes
    ressa’s picture

    ressa
    he/him
    commented
    Issue summary: View changes
    ressa’s picture

    ressa
    he/him
    commented
    Priority: Normal » Major
    q0rban’s picture

    q0rban commented

    I've taken a look at this, and cannot figure out why Composer is failing. Composer is working fine on the Base Preview. I'll need some help from a composer guru to figure this out. Happy to screen share with someone to work through this!

    q0rban’s picture

    q0rban commented
    Status: Active » Needs review

    I believe this is fixed now. To verify, you can close an open merge request and re-open it. That will trigger the creation of a new preview on Tugboat with the new config.

    Greg Anderson helped me with the solution, so please attribute him on this issue.

    Changeset here: https://github.com/TugboatQA/drupalorg/compare/9d574a...236175d

    ressa’s picture

    ressa
    he/him
    commented
    Status: Needs review » Reviewed & tested by the community

    Thanks @q0rban and @greg.1.anderson, Tugboat now works perfectly.

    Maybe @drumm can take care of credits?

    PS. The "via Tugboat" link https://www.tugboat.qa/drupal-welcome is still a 404.

    q0rban’s picture

    q0rban commented

    PS. The "via Tugboat" link https://www.tugboat.qa/drupal-welcome is still a 404.

    Oh goodness, that's embarrassing. Thank you for letting me know!

    ressa’s picture

    ressa
    he/him
    commented

    No problem, and thanks for providing Tugboat to the Drupal community!

    q0rban’s picture

    q0rban commented
    Assigned: Unassigned » q0rban
    Status: Reviewed & tested by the community » Fixed
    ressa’s picture

    ressa
    he/him
    commented

    I set the issue to "Reviewed & tested by the community" deliberately, since it then might get handled later on by admins for credits, whereas a "Fixed" Status will automatically transfer to "Closed" after 2 weeks, I believe.

    q0rban’s picture

    q0rban commented
    Status: Fixed » Reviewed & tested by the community

    Good call, thanks Ressa.

    drumm credited greg.1.anderson.

    drumm’s picture

    drumm
    he/him
    Location NY, US
    commented

    Thanks!

    ressa’s picture

    ressa
    he/him
    commented
    Status: Reviewed & tested by the community » Fixed

    Thanks @drumm!

    Status: Fixed » Closed (fixed)

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