-
Notifications
You must be signed in to change notification settings - Fork 22
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
error invoking store/list through access-api (proxying to upload-api) #359
Comments
It would be a little helpful if upload-api stack traces used source maps. (update: not fully because this stack trace is from access-api not upload-api🤦 , though in other debugging I get upload-api error stacks so it would still be useful) |
I added a unit test for the ucanto proxy that attempts a reduced test case for what I think is happening when the OP error happens, specifically:
Unfortunately I can't reproduce this error. Going to sleep on it I'm wondering if there's any chance that this line converting the lambda event body from base64 could be a culprit? https://github.com/web3-storage/w3infra/blob/main/upload-api/functions/ucan-invocation-router.js#L90 |
thinking it's more likely that somewhere in access-api is calling |
The |
Motivation: * attempt to fix according to this theory #359 (comment)
Motivation: * I invoked upload-api and [got an error response](storacha/w3up#359 (comment)). The error response had a stack trace, but the stack trace doesn't seem to be source-maps-aware in either our sentry logigng nor the stack trace included in the http response * attempt to configure the stack in a way that we get source-map-aware stack traces * in sentry - most important * in the stack traces included in the http response - nice to have Rationale * in [these sst docs for source maps](https://docs.sst.dev/advanced/source-maps), it says we might need this `bundle.sourcemap === true`
That resolved the issue when invoking |
Motivation: * attempt to fix according to this theory #359 (comment)
Motivation:
When trying to invoke access-api staging with a
can: "store/list"
invocation, I see this error from the upstream upload-apiThe text was updated successfully, but these errors were encountered: