Closed Bug 1427356 Opened 8 years ago Closed 8 years ago

Fix unhandled promise rejections in azure-blob-storage

Categories

(Taskcluster :: Services, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

Details

(node:4693) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 8): Error: Refreshed SAS, but got a Shared-Access-Signature that expires less than options.minSASAuthExpiry from now, signature expiry: 2017-12-29T13:01:12Z (node:4693) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
This seems to pass with node 6 but fail with 8: Data Container - Tests for authentication with SAS from auth.taskcluster.net Constants file does not exist, setting constants to {} ✓ should create an instance of data container (105ms) ✓ should create an instance of data container with read-only access and try to create a blob (65ms) ✓ should create a data block blob (63ms) 1) should call for every operation, expiry < now => refreshed SAS Azure Blob Storage - Data Container Version Support ✓ should create a dataBlockBlob in a container with version 1 of schema (100ms) ✓ should create a dataBlockBlob in a data container with version 2 of json schema (136ms) ✓ should load a dataBlockBlob with v1 from a data container with v2 (213ms) ✓ should create an append data blob with version 1 of schema, update the content with v2 (235ms) 35 passing (36s) 1 failing 1) Data Container - Tests for authentication with SAS from auth.taskcluster.net should call for every operation, expiry < now => refreshed SAS: Expected no error., assumed `false` to equal (===) true
Assignee: nobody → dustin
https://github.com/taskcluster/fast-azure-storage/pull/27 ..but that just leaves the tests failing. I suspect these tests never worked, and we just didn't know it.
https://github.com/taskcluster/azure-blob-storage/pull/3 I don't think this is enough, but it should be a start. I suspect most of the bugs here are in fast-azure-storage.
I think this is all fixed now, between the two PRs
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: Platform Libraries → Services
You need to log in before you can comment on or make changes to this bug.