With the introduction of the new Bucket#makePublic and Bucket#makePrivate system tests we've run into issues regarding rate limits (surprise surprise!). One issue that is unrelated to rate limits but is actually a legitimate issue we should address can be found at this build.
1) storage acls buckets should make a bucket public:
Uncaught Error: The metadata for bucket "gcloud-test-bucket-temp-a8cd5d60-d1be-11e4-a62a-dd6b7e745b01" was edited during the operation. Please try again.
at handleResp (/home/travis/build/GoogleCloudPlatform/gcloud-node/lib/common/util.js:9:4462)
at Request._callback (/home/travis/build/GoogleCloudPlatform/gcloud-node/lib/common/util.js:9:14414)
at Request.self.callback (/home/travis/build/GoogleCloudPlatform/gcloud-node/node_modules/request/request.js:344:22)
at Request.emit (events.js:110:17)
at Request.<anonymous> (/home/travis/build/GoogleCloudPlatform/gcloud-node/node_modules/request/request.js:1239:14)
at Request.emit (events.js:129:20)
at IncomingMessage.<anonymous> (/home/travis/build/GoogleCloudPlatform/gcloud-node/node_modules/request/request.js:1187:12)
at IncomingMessage.emit (events.js:129:20)
at _stream_readable.js:908:16
at process._tickCallback (node.js:355:11)
Because we are doing a number of operations in parallel when making the bucket public or private, we're running into the issue above where the metadata is edited at the same time as some actions are being taken place, a race condition we didn't anticipate. I believe simply doing the operations in series should eliminate this issue.
With the introduction of the new Bucket#makePublic and Bucket#makePrivate system tests we've run into issues regarding rate limits (surprise surprise!). One issue that is unrelated to rate limits but is actually a legitimate issue we should address can be found at this build.
Because we are doing a number of operations in parallel when making the bucket public or private, we're running into the issue above where the metadata is edited at the same time as some actions are being taken place, a race condition we didn't anticipate. I believe simply doing the operations in series should eliminate this issue.