Skip to content

Conversation

@sarkar-rajarshi
Copy link
Member

No description provided.

- Initialize CommunicationTokenCredential with token and not with CommunicationTokenRefreshOptions
- Convert AccessToken.expires_on to int as compared to datetime
@check-enforcer
Copy link

check-enforcer bot commented Mar 9, 2021

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

Copy link
Member

@juancamilor juancamilor left a comment

Choose a reason for hiding this comment

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

Looks good to me

@sarkar-rajarshi sarkar-rajarshi changed the base branch from master to feature/communication-chat-preview5 March 9, 2021 19:41
@sarkar-rajarshi sarkar-rajarshi changed the title Rsarkar/communication chat preview4 updates Rename user_identifier suffix Mar 9, 2021
@sarkar-rajarshi sarkar-rajarshi merged commit b7dd4b6 into Azure:feature/communication-chat-preview5 Mar 16, 2021
juancamilor pushed a commit that referenced this pull request Mar 19, 2021
* Rename user_identifier suffix (#17178)
* make CommunicationUserIdentifierSerializer private
* CommunicationTokenCredential + AccessToken fix
- Initialize CommunicationTokenCredential with token and not with CommunicationTokenRefreshOptions
- Convert AccessToken.expires_on to int as compared to datetime
* add token_refresher to CommunicationTokenCredential
* update docstring
* Identifier fields renaming _ credential import fixes in sample code
* preview5 models generated
- CommunicationError renamed to ChatError
* rename ChatThread to ChatThreadProperties
* get_chat_thread renamed to get_properties
- Rename method
- Move get_properties from ChatClient to ChatThreadClient
- Change method signature - remove parameter thread_id
- Modify unit and e2e tests - move tests from chat_thread_* to chat_thread_client_*
- Update README.md
* Rename ChatThreadInfo to ChatThreadItem
* Remove add_participant
* Rename repeatability_request_id to idempotency_token
* Change send_message return type from str to SendChatMessageResult
* Changes made due to rename of CommunicationError -> ChatError
- Changes made due to flattening of CreateChatThreadResult and AddChatParticipantsResult
* test recording added
* Address PR comments
* pylint fixes
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.

2 participants