Closed garycjohnson closed 3 years ago
@garycjohnson Issue should be resolved now. This particular issue was caused by amazon locking my personal AWS account last night for a few hours. The current setup uses S3 to store the prebuilt binaries, some newer tooling has come out that would allow us to publish them to github via releases which would be a lot better - currently I'm footing the bill for all of the bandwidth off my personal account which is not great.
Going to move this discussion to https://github.com/contra/node-gdal-next/issues/41
Also FWIW the fallback if the prebuilds don't exist is to build from source - this should still work fine, it just takes a while.
Thanks for the prompt resolution for this. Much appreciated.
Somewhere between 2330 and 0330 UTC the pre-built binaries have disappeared. This is now causing our Bitbucket Pipelines to fail as the pipeline doesn't have the resources necessary to do a fallback build. Is this a permanent change to remove the pre-built binaries?
When testing
https://gdal-next-binary.s3.amazonaws.com/gdal/v2.0.0/node-v72-linux-x64.tar.gz
I am getting the error: