Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JS C@E publish error "ERROR: the Fastly API returned 503 Service Unavailable: ." #362

Closed
JakeChampion opened this issue Aug 2, 2021 · 4 comments · Fixed by #380
Closed
Labels
bug Something isn't working

Comments

@JakeChampion
Copy link
Collaborator

JakeChampion commented Aug 2, 2021

Version

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
@JakeChampion JakeChampion added the bug Something isn't working label Aug 2, 2021
@JakeChampion 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
@Integralist
Copy link
Collaborator

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.

@JakeChampion
Copy link
Collaborator Author

I found the limits on this page -- https://docs.fastly.com/products/compute-at-edge-billing-and-resource-limits#resource-limits

The limit is 50mb for uploading a package

@Integralist
Copy link
Collaborator

Thanks @JakeChampion just working on a PR now to add error checking for the package size limit.

@Integralist
Copy link
Collaborator

@JakeChampion see linked PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants