Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MessagingSession reconnects with refreshed endpoint and credentials if needed #2180

Merged
merged 11 commits into from
Apr 26, 2022

Conversation

dpwspoon
Copy link
Contributor

@dpwspoon dpwspoon commented Apr 22, 2022

MessagingSession reconnects with refreshed endpoint and credentials if needed

Issue #:

Description of changes:

MessagingSession reconnects with refreshed endpoint and credentials if needed

Testing:

Tested on 2.x line with chime demo and this is cherry pick of that but will try testing using https://github.com/aws/amazon-chime-sdk-js/blob/main/demos/browser/app/messagingSession/messagingSession.ts

Can these tested using a demo application? Please provide reproducible step-by-step instructions.

Start the messaging demo. Force the network to shutdown and then reopen. Should reconnect.

Checklist:

  1. Have you successfully run npm run build:release locally?
    yes

  2. Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
    ~ sort of. I made a parameter optional

  3. Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
    No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dpwspoon dpwspoon requested a review from a team as a code owner April 22, 2022 00:00
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated
Comment on lines 8 to 19
## [3.1.1] - 2022-04-07

### Added

### Removed

### Changed

### Fixed

- MessagingSession reconnects with refreshed endpoint and credentials if needed

Copy link
Contributor

@xuesichao xuesichao Apr 22, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We haven't released 3.1.0 version. I think you should add your CHANGELOG under 3.1.0 section.
And remove 3.1.1 section.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dpwspoon Hi, when do we schedule this release? if it's before the release of 3.1.0. Maybe we should update the version to 3.0.1, if it's a patch version.

Sorry I didn't catch this in the previous comment.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ltrung @devalevenkatesh how do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, this chanelog can be under 3.1.0 we will later fix the changelog once the patch is released. I think I had checked the same with Trung. After release we will need to add 3.0.1 as a patch with this change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changelog update is a bit of improvement we have to make once we go through this hotfix release once and fix any hiccups if seen. But yes, we would like to add as part of the PR after we release this time.

CHANGELOG.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@dpwspoon dpwspoon merged commit e47bbbd into main Apr 26, 2022
@dpwspoon dpwspoon deleted the feature/msg-sess-reconnect-main branch April 26, 2022 00:08
devalevenkatesh added a commit that referenced this pull request Apr 27, 2022
devalevenkatesh added a commit that referenced this pull request Apr 27, 2022
* Revert "Version bump for [email protected] (#2186)"

This reverts commit 1f987a9.

* Revert "MessagingSession reconnects with refreshed endpoint and credentials if needed (#2180)"

This reverts commit e47bbbd.

* Remove demo/browser messaging client sdk dependency
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants