You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A ticket of the same name (#148) is closed, but I'd like to gingerly and respectfully suggest that this problem should be addressed. Perhaps the author of #148 was suggesting that this issue belongs in a non-terminus issue queue (i.e. it's an issue at the API level)? I would like to suggest that terminus should at the very least 1) indicate to the user whether the deploy succeeded or failed and 2) suppress repeating php errors.
I'm attempting to further automate our Drupal update scripts and conditions like this one are difficult to handle.
I completely sympathize with the annoyance of failing API requests dumping context-less stack-traces. My initial assumption here is that the deploy workflow is polling for status and for some reason it is erroring out in the API. We should be trapping those API errors and returning something human-readable and debuggable.
A ticket of the same name (#148) is closed, but I'd like to gingerly and respectfully suggest that this problem should be addressed. Perhaps the author of #148 was suggesting that this issue belongs in a non-terminus issue queue (i.e. it's an issue at the API level)? I would like to suggest that terminus should at the very least 1) indicate to the user whether the deploy succeeded or failed and 2) suppress repeating php errors.
I'm attempting to further automate our Drupal update scripts and conditions like this one are difficult to handle.
The text was updated successfully, but these errors were encountered: