J Burnett

Could it be for the purpose of allowing others in the future? Or does the spec set it in stone forever?

I had the same problem today. `(node:1772341) UnhandledPromiseRejectionWarning: StatusCodeError: 401 - undefined at new StatusCodeError (/home/jb/src/github.com/pouriaa/bitbucket-to-github/node_modules/request-promise-core/lib/errors.js:32:15) at Request.plumbing.callback (/home/jb/src/github.com/pouriaa/bitbucket-to-github/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/home/jb/src/github.com/pouriaa/bitbucket-to-github/node_modules/request-promise-core/lib/plumbing.js:46:31) at Request.self.callback (/home/jb/src/github.com/pouriaa/bitbucket-to-github/node_modules/request/request.js:185:22) at Request.emit (events.js:198:13)...

We're experiencing w/Intel CPUs like @wickedw. May be helpful to correct the title. Is there an env var for disabling build servers? Would be helpful for cross compile.

These 4 sectors are still stuck in FinalizeSector, even after our 1.10.0 to 1.10.1 upgrade. Any ideas on how to nudge these forward? We only have 6 days left to...

To clarify, these sectors are inactive and do not WdPoSt due to (local?) FinalizeSector state. The last entry of sector status log is Proving, so there's some mismatch.