Develop spm 2024 #2350

JoeMatt · 2024-10-11T05:50:08Z

What does this PR do

A lot

Where should the reviewer start

How should this be manually tested

Any background context you want to provide

What are the relevant tickets

Screenshots (important for UI changes)

Questions

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

… develop

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

codiumai-pr-agent-pro · 2024-10-21T02:25:29Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a submodule: The submodule 'Cores/melonDS/melonds-libretro' did not contain the commit '597067cde77ae5a0a214e57e4997da0e271220ce'. This resulted in a fatal error during the git fetch operation, causing the process to exit with code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1278: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1279: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1280: From https://github.com/Provenance-Emu/mGBA-Core 1281: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1282: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1283: From https://github.com/Provenance-Emu/melonDS 1284: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1285: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1286: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1287: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1288: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-21T02:26:49Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-XL Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to a problem with fetching a specific commit in a submodule: The submodule 'Cores/melonDS/melonds-libretro' did not contain the commit '597067cde77ae5a0a214e57e4997da0e271220ce'. This caused a fatal error during the git fetch operation, resulting in an exit code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1280: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1281: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1282: From https://github.com/Provenance-Emu/mGBA-Core 1283: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1284: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1285: From https://github.com/Provenance-Emu/melonDS 1286: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1287: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1288: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1289: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1290: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-21T02:26:52Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-Lite Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to a problem with fetching a specific commit in a submodule: The submodule path `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. This resulted in a fatal error during the git fetch operation, causing the process to exit with code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1283: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1284: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1285: From https://github.com/Provenance-Emu/mGBA-Core 1286: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1287: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1288: From https://github.com/Provenance-Emu/melonDS 1289: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1290: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1291: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1292: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1293: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-21T02:27:26Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (ProvenanceTV-Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to a problem with fetching a specific commit in a submodule: The submodule `Cores/melonDS/melonds-libretro` attempted to fetch a commit with the hash `597067cde77ae5a0a214e57e4997da0e271220ce`. The remote repository did not recognize this commit hash, resulting in a "not our ref" error. Consequently, the git process failed with exit code 128 because it could not fetch the specified commit.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1297: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1298: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1299: From https://github.com/Provenance-Emu/mGBA-Core 1300: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1301: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1302: From https://github.com/Provenance-Emu/melonDS 1303: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1304: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1305: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1306: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1307: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

… local files to import correctly

Cloud and Local Files importing

codiumai-pr-agent-pro · 2024-10-21T15:09:31Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-Lite Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to a problem with fetching a specific commit in a submodule: The submodule `Cores/melonDS/melonds-libretro` attempted to fetch a commit with the hash `597067cde77ae5a0a214e57e4997da0e271220ce`. The remote repository did not recognize this commit, resulting in a "not our ref" error. This caused the git process to fail with exit code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1282: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1283: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1284: From https://github.com/Provenance-Emu/mGBA-Core 1285: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1286: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1287: From https://github.com/Provenance-Emu/melonDS 1288: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1289: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1290: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1291: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1292: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-21T15:09:50Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-Release)

Failed stage: Checkout code [❌]

Relevant error logs:

1:  ##[group]Operating System
2:  macOS
...

1273:  Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6'
1274:  Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a'
1275:  From https://github.com/Provenance-Emu/mGBA-Core
1276:  * branch            2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD
1277:  Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01'
1278:  From https://github.com/Provenance-Emu/melonDS
1279:  * branch            08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD
1280:  Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc'
1281:  ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce
1282:  ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed.
1283:  ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-21T15:10:17Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-UnderDevelopment)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a submodule: The submodule `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. This resulted in a fatal error during the git fetch operation, causing the process to exit with code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1286: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1287: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1288: From https://github.com/Provenance-Emu/mGBA-Core 1289: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1290: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1291: From https://github.com/Provenance-Emu/melonDS 1292: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1293: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1294: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1295: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1296: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-21T15:10:21Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (ProvenanceTV-Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a git submodule: The submodule `Cores/melonDS/melonds-libretro` attempted to fetch commit `597067cde77ae5a0a214e57e4997da0e271220ce`. The remote repository did not recognize this commit, resulting in a "not our ref" error. This caused the git process to fail with exit code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1277: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1278: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1279: From https://github.com/Provenance-Emu/mGBA-Core 1280: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1281: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1282: From https://github.com/Provenance-Emu/melonDS 1283: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1284: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1285: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1286: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1287: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-21T15:10:21Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-XL Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed because of an issue with a Git submodule: The submodule `Cores/melonDS/melonds-libretro` attempted to fetch a specific commit `597067cde77ae5a0a214e57e4997da0e271220ce`. The commit was not found in the remote repository, resulting in a fatal error. This caused the Git process to exit with code 128, leading to the failure of the action.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1291: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1292: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1293: From https://github.com/Provenance-Emu/mGBA-Core 1294: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1295: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1296: From https://github.com/Provenance-Emu/melonDS 1297: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1298: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1299: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1300: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1301: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

codiumai-pr-agent-pro · 2024-10-23T13:25:48Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-XL Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a submodule: The submodule path `Cores/melonDS/melonds-libretro` attempted to fetch a commit with the hash `597067cde77ae5a0a214e57e4997da0e271220ce`. The remote repository did not recognize this commit hash, resulting in a "not our ref" error. Consequently, the direct fetching of the specified commit failed, causing the git process to exit with code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1282: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1283: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1284: From https://github.com/Provenance-Emu/mGBA-Core 1285: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1286: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1287: From https://github.com/Provenance-Emu/melonDS 1288: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1289: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1290: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1291: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1292: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-23T13:26:24Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (ProvenanceTV-Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a git submodule: The submodule path `Cores/melonDS/melonds-libretro` attempted to fetch a commit with the hash `597067cde77ae5a0a214e57e4997da0e271220ce`. The remote repository did not recognize this commit hash, resulting in a "not our ref" error. Consequently, the git command failed with exit code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1323: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1324: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1325: From https://github.com/Provenance-Emu/mGBA-Core 1326: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1327: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1328: From https://github.com/Provenance-Emu/melonDS 1329: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1330: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1331: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1332: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1333: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-23T13:26:26Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to a problem with fetching a specific commit in a git submodule: The submodule `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. This caused a fatal error during the git fetch operation, leading to the failure of the process with exit code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1287: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1288: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1289: From https://github.com/Provenance-Emu/mGBA-Core 1290: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1291: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1292: From https://github.com/Provenance-Emu/melonDS 1293: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1294: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1295: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1296: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1297: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-23T13:26:48Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-UnderDevelopment)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a submodule: The submodule `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. This caused a fatal error during the git fetch operation, resulting in an exit code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1276: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1277: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1278: From https://github.com/Provenance-Emu/mGBA-Core 1279: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1280: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1281: From https://github.com/Provenance-Emu/melonDS 1282: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1283: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1284: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1285: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1286: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-23T13:26:57Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-Lite Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a submodule: The submodule `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. A remote error occurred indicating that the commit is not available in the repository. The git command failed with exit code 128 due to this missing commit.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1319: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1320: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1321: From https://github.com/Provenance-Emu/mGBA-Core 1322: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1323: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1324: From https://github.com/Provenance-Emu/melonDS 1325: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1326: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1327: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1328: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1329: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

codiumai-pr-agent-pro · 2024-10-23T19:07:18Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (ProvenanceTV-Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to a problem with fetching a specific commit in a submodule: The submodule `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. This resulted in a fatal error during the submodule update process, causing the Git command to exit with code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1283: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1284: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1285: From https://github.com/Provenance-Emu/mGBA-Core 1286: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1287: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1288: From https://github.com/Provenance-Emu/melonDS 1289: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1290: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1291: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1292: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1293: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-23T19:07:21Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-Lite Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a submodule: The submodule `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. A fatal error occurred because the system attempted to fetch a commit that does not exist in the specified submodule. This resulted in the git process failing with exit code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1286: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1287: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1288: From https://github.com/Provenance-Emu/mGBA-Core 1289: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1290: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1291: From https://github.com/Provenance-Emu/melonDS 1292: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1293: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1294: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1295: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1296: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-23T19:07:27Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-XL Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a git submodule: The submodule `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. The error `fatal: remote error: upload-pack: not our ref` indicates that the commit is not available in the remote repository. This caused the git process to fail with exit code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1280: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1281: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1282: From https://github.com/Provenance-Emu/mGBA-Core 1283: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1284: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1285: From https://github.com/Provenance-Emu/melonDS 1286: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1287: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1288: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1289: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1290: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-23T19:07:29Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-Release)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with a Git submodule: The submodule `Cores/melonDS/melonds-libretro` attempted to fetch a commit with the hash `597067cde77ae5a0a214e57e4997da0e271220ce`. The commit was not found in the remote repository, resulting in a fatal error. This caused the Git process to exit with code 128, leading to the failure of the action.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1313: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1314: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1315: From https://github.com/Provenance-Emu/mGBA-Core 1316: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1317: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1318: From https://github.com/Provenance-Emu/melonDS 1319: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1320: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1321: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1322: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1323: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

codiumai-pr-agent-pro · 2024-10-23T19:07:37Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Build and upload Provenance (Provenance-UnderDevelopment)
Failed stage: Checkout code [❌]
Failure summary: The action failed due to an issue with fetching a specific commit in a submodule: The submodule `Cores/melonDS/melonds-libretro` did not contain the commit `597067cde77ae5a0a214e57e4997da0e271220ce`. This resulted in a fatal error during the git operation, causing the process to exit with code 128.
Relevant error logs: 1: ##[group]Operating System 2: macOS ... 1318: Submodule path 'Cores/fuse/fuse-libretro': checked out '3f9344ddf88dfd251d95cffdea615692479e8cc6' 1319: Submodule path 'Cores/hatari/hatari': checked out '018d0fe66afc881caf5a65588d09de40897da73a' 1320: From https://github.com/Provenance-Emu/mGBA-Core 1321: * branch 2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01 -> FETCH_HEAD 1322: Submodule path 'Cores/mGBA/Sources/libmGBA': checked out '2abe0f4993b65030e33e0a3b5b6ca1c1e9247f01' 1323: From https://github.com/Provenance-Emu/melonDS 1324: * branch 08e6d39a2e822ed2a70204459f6a5ce5a35b89cc -> FETCH_HEAD 1325: Submodule path 'Cores/melonDS/melonDS': checked out '08e6d39a2e822ed2a70204459f6a5ce5a35b89cc' 1326: ##[error]fatal: remote error: upload-pack: not our ref 597067cde77ae5a0a214e57e4997da0e271220ce 1327: ##[error]fatal: Fetched in submodule path 'Cores/melonDS/melonds-libretro', but it did not contain 597067cde77ae5a0a214e57e4997da0e271220ce. Direct fetching of that commit failed. 1328: ##[error]The process '/opt/homebrew/bin/git' failed with exit code 128

✨ CI feedback usage guide:

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

Failed stage
Failed test name
Failure summary
Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

SeiRyu and others added 30 commits May 10, 2024 02:21

emuthree: submodule

34c04cc

emuthree use Provenance branch

f21e306

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

emuThree add to build add debug config

1659945

Fix renamed launchscreen.storyboard path

1f151c6

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

emuThree fix some warnings, min ios version

c6e3df8

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

AppStore remove 3ds, fix other refs

a263638

Compile: Fix PS2 Paths / Fix PSP to compile on AppleTV

ad80a7d

Cores: Autosign -> Manual

bbdf46c

Build: reorder

e5243c0

AppIcons: build

9879acb

Update project version XCode 15.3, codesign

923e168

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

gitignore add psp build products

cb0c76d

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

PVSupport swift oehashing replace objc

1ac5509

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

metalviewcontroller error fix and log

44df748

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

homeview.swift fix possible crash on game delete

08a733d

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

pvsettings fix type-o

757f2fd

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

PVsystem minor change for easier debug

b3a3e0e

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

PVemulatorConfiguration gpt better code for error

b8e1dc2

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

appstore scheme fix logging flag xcode bug

9369aa8

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

package.resolved zstd and rxswift bump

597ae48

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

AppDelegate minor shortcut code cleanup

a4c7317

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

mednafen psx new options placeholder

da9d865

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

PVLib project codeisng and entitlements fixes

f2c15b0

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

PVRetro vulkan framework, codesign

f9b9de8

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

MoltenVK xcframeowrk dynamic and static

dad5270

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

Stella fix color format

0f9ad03

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

MoltenVK path fixes for XCframework

1354eb7

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

Merge branch 'pullrequests/rf2222222/rf2222222-emuthreeRebirth2' into…

2716ecd

… develop

Swift refactor snapshot

1ddb793

Signed-off-by: Joseph Mattello <mail@joemattiello.com>

Swift PM builds and loads

798d1a9

proskd and others added 3 commits October 21, 2024 10:52

Fixes code signing setups for Lite targets

ba7d479

Correct? access to secure url resources - these changes allow cloud /…

6f0b1e3

… local files to import correctly

Merge pull request #2356 from proskd/cloud-local-files-import

00e751b

Cloud and Local Files importing

JoeMatt added 6 commits October 23, 2024 01:07

swiftui menues, new icons, themes changes

f8f6d9d

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

SwiftUI choose artworks works

a3f84e7

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

hide share menu from swiftui

be952b0

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

Possible gl to metal fixes

5cefd70

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

Hide iCloud sync option for now, broken

0782bd5

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

Swift UI game rename menu item

dac6f38

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

JoeMatt added 2 commits October 23, 2024 12:36

Themes: no color defaults look OK

c993f50

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

Speed up caches, speeds up systems list UI

936f21f

Signed-off-by: Joseph Mattiello <git@joemattiello.com>

Develop spm 2024 #2350

Are you sure you want to change the base?

Develop spm 2024 #2350

Conversation

JoeMatt commented Oct 11, 2024

What does this PR do

Where should the reviewer start

How should this be manually tested

Any background context you want to provide

What are the relevant tickets

Screenshots (important for UI changes)

Questions

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 21, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 23, 2024

CI Failure Feedback 🧐

Configuration options