• anarcat's avatar
    don't allow d() to run before drush is fully initialized · 9391a997
    anarcat authored
    we add safety check so that we don't get caught running d() before
    drush is fully initialized. otherwise, the proper services hooks may
    not be properly declared and found by drush, so the object cache
    ($instances) would be initialised with incomplete data.
    
    it is possible that more initialisation we need happens after
    DRUSH_BOOTSTRAP_NONE, but this is already better than nothing.
    
    it took me and ergonlogic three freaking full days of headbanging on
    keyboards to figure that stuff out.
    9391a997
Name
Last commit
Last update
Provision Loading commit data...
Symfony/Component/ClassLoader Loading commit data...
db Loading commit data...
debian Loading commit data...
dns Loading commit data...
example Loading commit data...
http Loading commit data...
platform Loading commit data...
provision-tests Loading commit data...
.gitignore Loading commit data...
HACKING_2x.mdwn Loading commit data...
LICENSE.txt Loading commit data...
README.txt Loading commit data...
aegir-dev.make Loading commit data...
aegir-release.make Loading commit data...
aegir.make Loading commit data...
example.drushrc.php Loading commit data...
example.sudoers Loading commit data...
install.hostmaster.inc Loading commit data...
migrate.hostmaster.inc Loading commit data...
parse.backend.inc Loading commit data...
provision.api.php Loading commit data...
provision.context.inc Loading commit data...
provision.drush.inc Loading commit data...
provision.file.inc Loading commit data...
provision.inc Loading commit data...
provision.info Loading commit data...
provision.service.inc Loading commit data...
release.sh Loading commit data...
uninstall.hostmaster.inc Loading commit data...
upgrade.sh.txt Loading commit data...