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

feat: Refactoring component base #2

Merged
merged 2 commits into from
Sep 4, 2023
Merged

feat: Refactoring component base #2

merged 2 commits into from
Sep 4, 2023

Conversation

cubxxw
Copy link
Member

@cubxxw cubxxw commented Sep 4, 2023

Signed-off-by: Xinwei Xiong(cubxxw-openim) 3293172751nss@gmail.com

Fix: github.com/openimsdk/open-im-server#955

cubxxw added 2 commits August 28, 2023 10:02
Signed-off-by: Xinwei Xiong(cubxxw-openim) <3293172751nss@gmail.com>
Signed-off-by: Xinwei Xiong(cubxxw-openim) <3293172751nss@gmail.com>
@cubxxw cubxxw merged commit 9e6e17a into openim-sigs:main Sep 4, 2023
@cubxxw cubxxw changed the title feat: add test version feat: Refactoring component base Sep 4, 2023
@sweep-ai
Copy link
Contributor

sweep-ai bot commented Sep 10, 2023

GitHub actions yielded the following error.

The command that failed is Run dessant/lock-threads@v4. Here are the relevant lines from the logs:

##[group]Run dessant/lock-threads@v4
with:
github-token: ***
issue-inactive-days: 365
issue-lock-reason: resolved
pr-inactive-days: 365
pr-lock-reason: resolved
log-output: false
##[endgroup]
##[error]Bad credentials

Please note that the GitHub token has been redacted for security purposes.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

7 similar comments
@sweep-ai
Copy link
Contributor

sweep-ai bot commented Sep 10, 2023

GitHub actions yielded the following error.

The command that failed is Run dessant/lock-threads@v4. Here are the relevant lines from the logs:

##[group]Run dessant/lock-threads@v4
with:
github-token: ***
issue-inactive-days: 365
issue-lock-reason: resolved
pr-inactive-days: 365
pr-lock-reason: resolved
log-output: false
##[endgroup]
##[error]Bad credentials

Please note that the GitHub token has been redacted for security purposes.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

@sweep-ai
Copy link
Contributor

sweep-ai bot commented Sep 10, 2023

GitHub actions yielded the following error.

The command that failed is Run dessant/lock-threads@v4. Here are the relevant lines from the logs:

##[group]Run dessant/lock-threads@v4
with:
github-token: ***
issue-inactive-days: 365
issue-lock-reason: resolved
pr-inactive-days: 365
pr-lock-reason: resolved
log-output: false
##[endgroup]
##[error]Bad credentials

Please note that the GitHub token has been redacted for security purposes.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

@sweep-ai
Copy link
Contributor

sweep-ai bot commented Sep 10, 2023

GitHub actions yielded the following error.

The command that failed is Run dessant/lock-threads@v4. Here are the relevant lines from the logs:

##[group]Run dessant/lock-threads@v4
with:
github-token: ***
issue-inactive-days: 365
issue-lock-reason: resolved
pr-inactive-days: 365
pr-lock-reason: resolved
log-output: false
##[endgroup]
##[error]Bad credentials

Please note that the GitHub token has been redacted for security purposes.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

@sweep-ai
Copy link
Contributor

sweep-ai bot commented Sep 10, 2023

GitHub actions yielded the following error.

The command that failed is Run dessant/lock-threads@v4. Here are the relevant lines from the logs:

##[group]Run dessant/lock-threads@v4
with:
github-token: ***
issue-inactive-days: 365
issue-lock-reason: resolved
pr-inactive-days: 365
pr-lock-reason: resolved
log-output: false
##[endgroup]
##[error]Bad credentials

Please note that the GitHub token has been redacted for security purposes.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

@sweep-ai
Copy link
Contributor

sweep-ai bot commented Sep 10, 2023

GitHub actions yielded the following error.

The command that failed is Run dessant/lock-threads@v4. Here are the relevant lines from the logs:

##[group]Run dessant/lock-threads@v4
with:
github-token: ***
issue-inactive-days: 365
issue-lock-reason: resolved
pr-inactive-days: 365
pr-lock-reason: resolved
log-output: false
##[endgroup]
##[error]Bad credentials

Please note that the GitHub token has been redacted for security purposes.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

@sweep-ai
Copy link
Contributor

sweep-ai bot commented Sep 10, 2023

GitHub actions yielded the following error.

The command that failed is Run dessant/lock-threads@v4. Here are the relevant lines from the logs:

##[group]Run dessant/lock-threads@v4
with:
github-token: ***
issue-inactive-days: 365
issue-lock-reason: resolved
pr-inactive-days: 365
pr-lock-reason: resolved
log-output: false
##[endgroup]
##[error]Bad credentials

Please note that the GitHub token has been redacted for security purposes.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

@sweep-ai
Copy link
Contributor

sweep-ai bot commented Sep 10, 2023

GitHub actions yielded the following error.

The command that failed is Run dessant/lock-threads@v4. Here are the relevant lines from the logs:

##[group]Run dessant/lock-threads@v4
with:
github-token: ***
issue-inactive-days: 365
issue-lock-reason: resolved
pr-inactive-days: 365
pr-lock-reason: resolved
log-output: false
##[endgroup]
##[error]Bad credentials

Please note that the GitHub token has been redacted for security purposes.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

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.

[RFC #0006] Introduction of component-base Repository
1 participant