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
Closing this as we were not able to reproduce the last piece here after all the redeployments. @0x2b3bfa0 feel free to destroy the cluster if it's still running.
Uh oh!
There was an error while loading. Please reload this page.
Description
Apparently, we can't index an empty S3 bucket, and it produces the following exceptions:
FileNotFoundError: Unable to resolve remote path:
when running locally.PermissionError: No AWSAccessKey was presented.
when running from Studio.1Query
Traceback (Local)
Traceback (Studio)
Version Info
Footnotes
This one is especially obscure, and I guess it's the result of attempting anonymous (?) access after the first attempt fails with an exception? ↩
The text was updated successfully, but these errors were encountered: