The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_legacy_present should respond with legacy_appeals_present Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_associated_request_issues should respond with the associated request issues Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_same_multiple_decision_issues_per_request_issue should respond with the same multiple decision issues per request issue Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_number_of_paginated_issues should only show number of request issues listed in the paginates_per value on first page Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_remaining_issues should only show remaining request issues on next page Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_page_1_when_page_0 should show page 1 when attempting to get page 0 Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_default_to_page_1 should default to page 1 Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_first_page_if_page_negatvie should show the first page if page is negative Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_last_page_if_page_larger_than_total should show last page if page larger than total Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_correct_total_number_of_pages_and_max_request_issues_per_page_on_per_change should show correct total number of pages and max request issues per page on per change Skipped: Flakey test