search

sintaxi / surge

CLI for the surge.sh CDN
https://surge.sh
2.84k stars 136 forks source link

Invalid token error despite using correct token #406

Closed balupton closed 4 years ago

balupton commented 4 years ago

from https://travis-ci.com/github/bevry/get-cli-arg/jobs/327384325

deploying branch of project . to v4.1.0.get-cli-arg.bevry.surge.sh
372
373(node:6396) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
374(Use `node --trace-warnings ...` to show where the warning was created)
375   Invalid token

and https://travis-ci.com/github/bevry/daet/jobs/327317383

deploying branch of project . to v3.1.0.daet.bevry.surge.sh
374
375(node:6457) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
376(Use `node --trace-warnings ...` to show where the warning was created)
377   Invalid token
378

exact same token used successfully on about 40 other deploys today: https://travis-ci.com/github/bevry

balupton commented 4 years ago

This was on my side. Seems the travis CLI could not make up its mind if it was applying the updated env vars to the travis-ci.org site or the travis-ci.com site. I've now made it explicit for every call to the travis ci api - which actually resolves this issue.