Cannot apply available updates with Terminus

[chrisgross]

When I try to deploy upstream updates with Terminus, I get the message [info] No updates to list., even though my dashboard says that updates are available. This never used to happen but has been occurring more and more recently.

[TeslaDethray]

@chrisgross A fix for this was added in #1233 and a release was cut yesterday. Please give it another try and write back if it's still giving you grief.

[chrisgross]

Still having this issue as of today.

[TeslaDethray]

@chrisgross I'm sorry that's still troubling you. I'll give this issue another look today.

[chrisgross]

I am still having this problem. Both on the old version of terminus and the 1.0.0-beta.2. I see upstream updates on the dashboard but terminus is not seeing them, even though I pushed the latest commit two hours hours ago.

[TeslaDethray]

I'm sorry you've waited so long for this, @chrisgross. It is now on our scheduled work for this sprint (lasting until 1/20).

[TeslaDethray]

Could I ask you to run the command with a -vvv and share that for debug so that I can see what your Terminus install is sending and receiving? This'll go a long way to helping me figure out what's gone awry for you. @chrisgross You will want to be sure to expunge identifying information like your site's UUID and your session token from your output before posting it .

[chrisgross]

The sanitized output is below. This is hard to troubleshoot on my end, because I have multiple sites, and it works fine for some and not others, and also it doesn't happen every time. So I couldn't get you a standard example, which is that I push a single commit and some sites don't see it.

So, in this situation I only noticed something odd in the debug after I had unsuccessfully tried to get four commits to be ignored by terminus, because it kept correctly seeing each of the first three on all of my sites.

Finally, I got this output, which shows only one commit is available, when there should be four. At first I thought maybe it only shows one at a time intentionally, perhaps the oldest or newest, but now I know that all four should be in the list because one of my other sites actually lists all four when I run the terminus command below. The debug output from the other site looks exactly the same, only there are four commits available instead of one.

So the fact that there is one instead of four is analogous to there being zero when there should be one.

~/Downloads/terminus/bin $ ./terminus upstream:updates:list xxxxxxxx -vvv                                                                             master
 [debug] #### REQUEST ####
Headers: {"User-Agent":"Terminus\/1.0.0-beta.2 (php_version=5.5.38&script=bin\/terminus)","Content-type":"application\/json","Authorization":"Bearer xxxxxxx"}
URI: https://terminus.pantheon.io:443/api/site-names/xxxxxxx
Method: GET
Body:
 [debug] #### RESPONSE ####
Headers: {headers}
Data: {data}
Status Code: 200
 [debug] #### REQUEST ####
Headers: {"User-Agent":"Terminus\/1.0.0-beta.2 (php_version=5.5.38&script=bin\/terminus)","Content-type":"application\/json","Authorization":"Bearer xxxxxxx"}
URI: https://terminus.pantheon.io:443/api/sites/xxxxxxx?site_state=true
Method: GET
Body:
 [debug] #### RESPONSE ####
Headers: {headers}
Data: {data}
Status Code: 200
 [debug] #### REQUEST ####
Headers: {"User-Agent":"Terminus\/1.0.0-beta.2 (php_version=5.5.38&script=bin\/terminus)","Content-type":"application\/json","Authorization":"Bearer xxxxxxx"}
URI: https://terminus.pantheon.io:443/api/sites/xxxxxxx/environments
Method: GET
Body:
 [debug] #### RESPONSE ####
Headers: {headers}
Data: {data}
Status Code: 200
 [debug] #### REQUEST ####
Headers: {"User-Agent":"Terminus\/1.0.0-beta.2 (php_version=5.5.38&script=bin\/terminus)","Content-type":"application\/json","Authorization":"Bearer xxxxxxx"}
URI: https://terminus.pantheon.io:443/api/sites/xxxxxxx/code-upstream-updates?base_branch=master
Method: GET
Body:
 [debug] #### RESPONSE ####
Headers: {headers}
Data: {data}
Status Code: 200
 ------------------------------------------ --------------------- ------------------------------- -------------
  Commit ID                                  Timestamp             Message                         Author
 ------------------------------------------ --------------------- ------------------------------- -------------
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx   2017-01-12T22:10:05   testing terminus deploy delay   Chris Gross

 ------------------------------------------ --------------------- ------------------------------- -------------

[chrisgross]

Do you have any updates about this? This problem has effectively crippled my ability to deploy sites other than manually doing it through the dashboard. This is highly critical.