A MP* was mistakenly landed without the last revision that was pushed to it, this might have because of a stale page in the browser or unclear LP slowness. Either way it seems our old tool had checks to prevent this. From IRC:
<nessita> pedronis, I've got that many times. If you approve at an older version, with tarmac there were 2 scenarios: 1- the were new revnos already push, tarmac would bail saying "there are more revnos than those approved"
<nessita> with the new lander, I'm not 100% sure
<sparkiegeek> a quick perusal of the code suggests it will not complain
A MP* was mistakenly landed without the last revision that was pushed to it, this might have because of a stale page in the browser or unclear LP slowness. Either way it seems our old tool had checks to prevent this. From IRC:
<nessita> pedronis, I've got that many times. If you approve at an older version, with tarmac there were 2 scenarios: 1- the were new revnos already push, tarmac would bail saying "there are more revnos than those approved"
<nessita> with the new lander, I'm not 100% sure
<sparkiegeek> a quick perusal of the code suggests it will not complain
* https:/ /code.launchpad .net/~pedronis/ snap-assertions -service/ abstract- database- to-backend/ +merge/ 326011
originally only 138 was landed