Contrib.social

Document what the existence of the PACKAGE_MANAGER_FAILURE.yml means

Open on Drupal.org →
Created on 18 May 2023, about 1 year ago
Updated 4 June 2023, about 1 year ago

Problem/Motivation

Package Manager places a file PACKAGE_MANAGER_FAILURE.yml in the active directory while staged code is copied back into it, and then removed after the copying is finished. If this file exists that means the site is in an indeterminate state and probably the only thing you can do is restore your code from a backup. We intentionally made this a file instead of using Drupal state service because depending which files did not get copied over you site might not even load. In this case the docs should let the user know that they should check for this existence of this file.

Steps to reproduce

Proposed resolution

Document it.

Remaining tasks

  • ✅ File an issue about this project
  • ☐ Manual Testing
  • ☐ Code Review
  • ☐ Accessibility Review
  • ☐ Automated tests needed/written?
📌 Task
Status

Postponed: needs info

Version

1.0

Component

Documentation

Created by

🇮🇳India kunal.sachdev

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @kunal.sachdev
  • Comment about 1 year ago →
    🇮🇳India kunal.sachdev
  • Status changed to Postponed: needs info about 1 year ago
  • Comment about 1 year ago →
    🇺🇸United States chrisfromredfin Portland, Maine

    Wondering WHY we should tell the user about this, or moreso, under what circumstances? Yes, it can be pretty broken but could also be fine and you just have to delete the file. However, considering our target audience, I'm wondering what the right UI is for this, or if this belongs in Project Browser at all, or is better-served in Package Manager (Package Manager provides that "indeterminate state" error message).

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024