Integration tests are failing in master

[trivikr]

Describe the bug
Integration tests are failing in master

git log

$ git log | head
commit cd4813013063fc015678bfb1e71d7c1bbc26e2ab
Author: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Date:   Wed Jun 10 18:05:44 2020 +0000

    chore(deps-dev): bump prettier from 2.0.4 to 2.0.5 (#1200)

commit a021d43d14949dcf58307192303e544d634c49b7
Author: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
Date:   Wed Jun 10 11:01:45 2020 -0700

Output

$ yarn test:integration-legacy
yarn run v1.22.4
$ cucumber-js --fail-fast
........................................................................................................................................................................................................F----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Failures:

1) Scenario: Creating a table # features/dynamodb/tables.feature:6
   ✔ Before # features/dynamodb/step_definitions/dynamodb.js:65
   ✔ Before # features/extra/hooks.js:22
   ✖ When I create a table # features/dynamodb/step_definitions/dynamodb.js:102
       SerializationException: Start of structure or map found where not expected
           at deserializeAws_json1_0CreateTableCommandError (/local/home/trivikr/workspace/test/aws-sdk-js-v3/clients/client-dynamodb/dist/cjs/protocols/Aws_json1_0.js:620:41)
           at processTicksAndRejections (internal/process/task_queues.js:97:5)
   - Then the table should eventually exist # features/dynamodb/step_definitions/dynamodb.js:165

153 scenarios (1 failed, 109 skipped, 43 passed)
534 steps (1 failed, 421 skipped, 112 passed)
0m05.737s
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

SDK version number
N/A

Is the issue in the browser/Node.js?
N/A

Details of the browser/Node.js version
N/A

To Reproduce (observed behavior)
Run integration tests on master
yarn test:integration-legacy

Expected behavior
Integration tests should pass

[trivikr]

The integration tests started failing after updating to smithy 1.0

Before smithy 1.0

$ git log | head
commit 7dbb571861656c541f29d9d9c42feb85b34428eb
Author: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
Date:   Fri Jun 5 14:42:45 2020 -0700

    chore: rename maxRetries to maxAttempts (#1244)

commit abfb40ff1cdc74df32d3ffb5c561480282954239
Author: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
Date:   Fri Jun 5 14:21:04 2020 -0700

$ yarn build:all
...

$ AWS_PROFILE=team yarn test:integration-legacy                             
yarn run v1.22.4
$ cucumber-js --fail-fast
.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

153 scenarios (153 passed)
534 steps (534 passed)
0m56.651s
Done in 59.83s.

After smithy 1.0

$ git log | head
commit e19fc4feea5268442370af97e266c982beef4210
Author: kstich <kevin@kstich.com>
Date:   Fri Jun 5 12:39:15 2020 -0700

    chore: codegen for Smithy 1.0 updates

commit c65f7303592f646e14258f3d4f6c73c5fbe547f3
Author: stickevi <stickevi@amazon.com>
Date:   Wed May 20 09:20:18 2020 -0700

$ yarn build:all
...

$ AWS_PROFILE=team yarn test:integration-legacy                            
yarn run v1.22.4
$ cucumber-js --fail-fast
........................................................................................................................................................................................................F----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Failures:

1) Scenario: Creating a table # features/dynamodb/tables.feature:6
   ✔ Before # features/dynamodb/step_definitions/dynamodb.js:65
   ✔ Before # features/extra/hooks.js:22
   ✖ When I create a table # features/dynamodb/step_definitions/dynamodb.js:102
       SerializationException: Start of structure or map found where not expected
           at deserializeAws_json1_0CreateTableCommandError (/local/home/trivikr/workspace/test/aws-sdk-js-v3/clients/client-dynamodb/dist/cjs/protocols/Aws_json1_0.js:620:41)
           at processTicksAndRejections (internal/process/task_queues.js:97:5)
   - Then the table should eventually exist # features/dynamodb/step_definitions/dynamodb.js:165

153 scenarios (1 failed, 109 skipped, 43 passed)
534 steps (1 failed, 421 skipped, 112 passed)
0m05.522s
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[trivikr]

Error is thrown in createTable command:

aws-sdk-js-v3/features/dynamodb/step_definitions/dynamodb.js

Lines 80 to 86 in cd48130

	world.service.createTable(params, function (err, data) {
	if (err) {
	callback(err);
	return;
	}
	waitForTableExists(world, callback);
	});

params

{
  TableName: 'aws-sdk-js-integration-1591820356630',
  AttributeDefinitions: [ { AttributeName: 'id', AttributeType: 'S' } ],
  KeySchema: [ { AttributeName: 'id', KeyType: 'HASH' } ],
  BillingMode: 'PAY_PER_REQUEST'
}

error

SerializationException: Start of structure or map found where not expected
    at deserializeAws_json1_0CreateTableCommandError (/local/home/trivikr/workspace/aws-sdk-js-v3/clients/client-dynamodb/dist/cjs/protocols/Aws_json1_0.js:620:41)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  __type: 'com.amazon.coral.service#SerializationException',
  '$fault': 'client',
  '$metadata': {
    httpStatusCode: 400,
    httpHeaders: {
      server: 'Server',
      date: 'Wed, 10 Jun 2020 20:17:32 GMT',
      'content-type': 'application/x-amz-json-1.0',
      'content-length': '123',
      connection: 'keep-alive',
      'x-amzn-requestid': 'SFSUJUT5LT7ECO2BI1630SCEG3VV4KQNSO5AEMVJF66Q9ASUAAJG',
      'x-amz-crc32': '1115736629'
    },
    requestId: 'SFSUJUT5LT7ECO2BI1630SCEG3VV4KQNSO5AEMVJF66Q9ASUAAJG',
    attempts: 1,
    totalRetryDelay: 0
  }
}

[trivikr]

The issue is with table creation and not integration test setup.
Verified by writing following code in root:

test.js

const { DynamoDB } = require("./clients/client-dynamodb");

(async () => {
  const region = "us-west-2";
  const client = new DynamoDB({ region });

  const response = await client.createTable({
    TableName: "aws-sdk-js-integration-1591820356630",
    AttributeDefinitions: [{ AttributeName: "id", AttributeType: "S" }],
    KeySchema: [{ AttributeName: "id", KeyType: "HASH" }],
    BillingMode: "PAY_PER_REQUEST"
  });
  console.log(response);
})();

Output

$ pwd
/home/trivikr/workspace/aws-sdk-js-v3

$ node test.js 
(node:20436) UnhandledPromiseRejectionWarning: SerializationException: Start of structure or map found where not expected
    at deserializeAws_json1_0CreateTableCommandError (/local/home/trivikr/workspace/aws-sdk-js-v3/clients/client-dynamodb/dist/cjs/protocols/Aws_json1_0.js:620:41)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:20436) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
(node:20436) [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.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.