You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👎 Sweep Needs Improvement
I created this PR to fix the failing GitHub Actions.## Description
This PR addresses the issue of the failing GitHub Action dessant/lock-threads@v4 due to bad credentials. The issue was identified in the workflow file where the action is used. The action was not being provided with the necessary GitHub token to perform its tasks.
Summary of Changes
Modified the .github/workflows/main.yml file to provide the GITHUB_TOKEN to the dessant/lock-threads@v4 action.
If the GITHUB_TOKEN was already being provided, ensured that it was being correctly referenced as secrets.GITHUB_TOKEN and not as a string literal.
If the issue persists after these changes, instructions have been provided to add a personal access token (PAT) to the repository's secrets and use this token instead of the GITHUB_TOKEN.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You have signed the CLA already but the status is still pending? Let us recheck it.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You have signed the CLA already but the status is still pending? Let us recheck it.
I'm currently fixing this PR to address the following:
[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:
The command:
Run release-drafter/release-drafter@v5
yielded the following error:
##[error]Invalid config file
##[warning]openimsdk/community: Invalid config file
{
name: 'event',
id: '7403459501',
stack: 'Error: Configuration file .github/release-drafter.yml is not found. The configuration file must reside in your default branch.\n' +
' at getConfig (/home/runner/work/_actions/release-drafter/release-drafter/v5/dist/index.js:142745:13)\n' +
' at async /home/runner/work/_actions/release-drafter/release-drafter/v5/dist/index.js:142240:22\n' +
' at async Promise.all (index 0)',
type: 'Error'
}
##[error]Invalid config file
Here are the logs:
"pull_request_target.opened" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
"pull_request_target.reopened" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
"pull_request_target.synchronize" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
"pull_request_target.edited" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
##[warning]openimsdk/community: Invalid config file
{
name: 'event',
id: '7403459501',
stack: 'Error: Configuration file .github/release-drafter.yml is not found. The configuration file must reside in your default branch.\n' +
' at getConfig (/home/runner/work/_actions/release-drafter/release-drafter/v5/dist/index.js:142745:13)\n' +
' at async drafter (/home/runner/work/_actions/release-drafter/release-drafter/v5/dist/index.js:142339:20)\n' +
' at async Promise.all (index 1)',
type: 'Error'
}
I'm currently fixing this PR to address the following:
[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:
The command:
Run contributor-assistant/github-action@v2.3.1
yielded the following error:
##[error]graphql call to get the committers details failed: HttpError: Bad credentials
Here are the logs:
CLA Assistant GitHub Action bot has started the process
I'm currently fixing this PR to address the following:
[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:
The command:
Run github/codeql-action/analyze@v2
yielded the following error:
##[error]Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.15.4/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14567 /home/runner/work/_temp/codeql_databases/go". Exit code was 32 and last log line was: CodeQL detected code written in , but not any written in Go. Review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build . See the logs for more details.
Here are the logs:
[command]/opt/hostedtoolcache/CodeQL/2.15.4/x64/codeql/codeql version --format=json
{
"productName" : "CodeQL",
"vendor" : "GitHub",
"version" : "2.15.4",
"sha" : "6994dfd6d94ee3d205768fbe15e18312bf22b388",
"branches" : [
"codeql-cli-2.15.4"
],
"copyright" : "Copyright (C) 2019-2023 GitHub, Inc.",
"unpackedLocation" : "/opt/hostedtoolcache/CodeQL/2.15.4/x64/codeql",
"configFileLocation" : "/home/runner/.config/codeql/config",
"configFileFound" : false,
"features" : {
"analysisSummaryV2Option" : true,
"featuresInVersionResult" : true,
"indirectTracingSupportsStaticBinaries" : false,
"supportsPython312" : true,
"mrvaPackCreate" : true,
"threatModelOption" : true
}
}
##[group]Finalizing go
[command]/opt/hostedtoolcache/CodeQL/2.15.4/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14567 /home/runner/work/_temp/codeql_databases/go
CodeQL detected code written in , but not any written in Go. Review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build .
I'm currently fixing this PR to address the following:
[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:
The command:
Run sudo chmod +x ./scripts/build_all_service.sh
yielded the following error:
##[error]Process completed with exit code 1.
##[group]Run sudo chmod +x ./scripts/stop_all.sh
�[36;1msudo chmod +x ./scripts/stop_all.sh�[0m
�[36;1msudo ./scripts/stop_all.sh�[0m
�[36;1msudo cat logs/openIM.log 2>/dev/null�[0m
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
##[endgroup]
chmod: cannot access './scripts/stop_all.sh': No such file or directory
##[error]Process completed with exit code 1.
Here are the logs:
chmod: cannot access './scripts/build_all_service.sh': No such file or directory
I'm currently fixing this PR to address the following:
[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:
The command:
Run sudo make tidy
yielded the following error:
##[error]Process completed with exit code 2.
Here are the logs:
Tidying up the project...
tidying_command_here
make: tidying_command_here: No such file or directory
make: *** [Makefile:43: tidy] Error 127
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
size/MDenotes a PR that changes 30-99 lines, ignoring generated files.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Feedback (click)
I created this PR to fix the failing GitHub Actions.## Description
This PR addresses the issue of the failing GitHub Action
dessant/lock-threads@v4due to bad credentials. The issue was identified in the workflow file where the action is used. The action was not being provided with the necessary GitHub token to perform its tasks.Summary of Changes
.github/workflows/main.ymlfile to provide theGITHUB_TOKENto thedessant/lock-threads@v4action.GITHUB_TOKENwas already being provided, ensured that it was being correctly referenced assecrets.GITHUB_TOKENand not as a string literal.GITHUB_TOKEN.Please review the changes and provide feedback.