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
Fastly CLI version 0.36.0 (dd0b7d9)
Built with go version go1.16.6 linux/amd64
What happened
I ran fastly compute publish and expected the project to be published to the Fastly Service but instead came across this error:
fastly compute publish --service-id 79cgjkVGQd9Db0tdbBjGbP
✓ Initializing...
✓ Verifying package manifest...
✓ Verifying local javascript toolchain...
✓ Building package using javascript toolchain...
✓ Creating package archive...
SUCCESS: Built javascript package js (pkg/js.tar.gz)
✓ Initializing...
✗ Uploading package...
ERROR: the Fastly API returned 503 Service Unavailable: .
occasionally the error would be different and say something about a broken pipe (I can't replicate that error anymore though and didn't save the full error message)
Update: just in case it is useful to know, here are the sizes of the files being published:
ls -la bin pkg
bin:
.rw-r--r-- 82M jake.champion 2 Aug 15:08 index.js
.rw-r--r-- 342M jake.champion 2 Aug 15:08 main.wasm
pkg:
.rw-r--r-- 71M jake.champion 2 Aug 15:08 js.tar.gz
The text was updated successfully, but these errors were encountered:
JakeChampion
changed the title
JSC@E publish error "ERROR: the Fastly API returned 503 Service Unavailable: ."
JS C@E publish error "ERROR: the Fastly API returned 503 Service Unavailable: ."
Aug 2, 2021
Hi @JakeChampion there does appear to be some size restrictions in place. These restrictions aren't currently documented and there is ongoing discussion regarding this particular issue. We'll update this ticket once we have some more feedback.
Version
What happened
I ran
fastly compute publish
and expected the project to be published to the Fastly Service but instead came across this error:occasionally the error would be different and say something about a broken pipe (I can't replicate that error anymore though and didn't save the full error message)
Update: just in case it is useful to know, here are the sizes of the files being published:
The text was updated successfully, but these errors were encountered: