Trivikram Kamat

Verified that LifeCycleConfiguration is added in Bucket in both cases: * When payload is `` * When payload is `` Code changed in https://github.com/aws/aws-sdk-js-v3/blob/da2c0852df6bc64cbd397489f2a8d1aea5d88c6f/clients/client-s3/protocols/Aws_restXml.ts#L10193 The body tag console.log at https://github.com/aws/aws-sdk-js-v3/blob/da2c0852df6bc64cbd397489f2a8d1aea5d88c6f/clients/client-s3/protocols/Aws_restXml.ts#L3439...

Verified that v2 sends `LifeCycleConfiguration` by console.log `req.httpRequest.body` in `populateBody` https://github.com/aws/aws-sdk-js/blob/17245a8c612ddd3cfe01b0c45e70cfbb557b62d1/lib/protocol/rest_xml.js#L26 Code ```js const AWS = require("aws-sdk"); (async () => { const region = "us-west-2"; const client = new AWS.S3({...

The fix is to be added in XmlShapeSerVisitor https://github.com/aws/aws-sdk-js-v3/blob/da2c0852df6bc64cbd397489f2a8d1aea5d88c6f/codegen/smithy-aws-typescript-codegen/src/main/java/software/amazon/smithy/aws/typescript/codegen/XmlShapeSerVisitor.java#L195-L196

The bug exists in serializing structure where codegen tries to read XmlName trait https://github.com/aws/aws-sdk-js-v3/blob/da2c0852df6bc64cbd397489f2a8d1aea5d88c6f/codegen/smithy-aws-typescript-codegen/src/main/java/software/amazon/smithy/aws/typescript/codegen/XmlShapeSerVisitor.java#L190-L193 Confirmed that the xmlName trait is present on LifecycleConfiguration https://github.com/aws/aws-sdk-js-v3/blob/4f9f4a79b019c1c35530e05c4138fde88a6fb547/codegen/sdk-codegen/aws-models/s3.2006-03-01.json#L9558-L9566 Smithy documentation on xmlName trait https://awslabs.github.io/smithy/1.0/spec/core/xml-traits.html#xmlname-trait

The S3 Transfer Manager in AWS SDK for Java v1 supports pause/resume. The application has to explicitly call pause though. Blog post: https://aws.amazon.com/blogs/developer/pausing-and-resuming-transfers-using-transfer-manager/

A reproducible example was provided in https://github.com/nodejs/node/issues/45168#issuecomment-1294277796

I'm receiving the same error. Failed GitHub Action for reference: https://github.com/trivikr/test-postinstall-node-version-check/actions/runs/727995782 Error: ```console Error: Error: Input required and not supplied: token at Object.getInput (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/node_modules/@actions/core/lib/core.js:94:1) at main (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/action/index.ts:17:14) at Object.48 (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/action/index.ts:74:1)...

> Unfortunately I don't have a choice in leaning away from Lerna. > Agree, I'm moving away from lerna. unlerna for me! @jmitchell38488 @iamrommel What are the lerna alternatives that...

> What's not working for you? The lerna 3.x is working fine for me right now. I'm preemptively exploring moving away from lerna for my monorepo setup for concerns largely...

Update: [yarn 3](https://dev.to/arcanis/yarn-3-0-performances-esbuild-better-patches-e07) was released today.