Problem/Motivation
In #3357941: Write helpful message to FailureMarker if script execution time was exceeded during stage life cycle the FailureMarker was going to be used if there were time outs must of which would not leave your code in an indeterminate state which is the purpose the FailureMarker file.
We document in the class doc but we should probably document that elsewhere.
If the PACKAGE_MANAGER_FAILURE.yml exists 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.
Proposed resolution
Lets document this in several places
- package_manager.api.php
- In https://www.drupal.org/docs/8/update/automatic-updates
- Project Browser docs?
Issue fork automatic_updates-3360548
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:
Comments
Comment #2
tedbowComment #3
kunal.sachdev commentedComment #5
kunal.sachdev commentedComment #6
omkar.podey commentedComment #7
omkar.podey commented3 nits and still need to address the remaining 2 points in proposed resolution.
Comment #8
kunal.sachdev commentedCreated follow ups for 2. and 3. point of proposed resolution:
#3361244: Document PACKAGE_MANAGER_FAILURE.yml in https://www.drupal.org/docs/8/update/automatic-updates,
#3361246: Document what the existence of the PACKAGE_MANAGER_FAILURE.yml means
Comment #9
kunal.sachdev commentedComment #10
wim leers99% ready!
Comment #11
kunal.sachdev commentedComment #12
wim leersLGTM!
Comment #15
phenaproxima