Copilot

Results 4682 issues of Copilot

- [x] Identify CI test failures - [x] Investigate failed debian-11 integration tests - [x] Determine that debian-11 is not configured in kitchen.dokken.yml - [x] Verify this is a pre-existing...

Release: Patch

- [x] Extract config_file method from action_class to enable external access - [x] Add test case for config_file accessibility - [x] Extract config_file implementation to helpers.rb (per review feedback) -...

The npm source installation tests were defined but not being executed in the CI pipeline, and the underlying npm_from_source recipe had a critical bug that prevented npm from being installed...

Unpinned dependencies in requirements.txt caused production docker builds to fail unpredictably when upstream packages released breaking changes. Dependencies were scattered across setup.py, requirements.txt, requirements_dev.txt, environment.yml, and environment_dev.yml with no clear...

This PR refactors the RZInput system to eliminate the cumbersome singleton-based virtual interface pattern and replaces it with a clean static function design similar to RZFileSystem. This change significantly simplifies...

Architecture

This PR adds comprehensive unit test coverage for all Razix Engine APIs, addressing the need for systematic testing of engine modules using the Google Test framework. ## Overview The Razix...

After #1178 fixed SYSCALL 5 in CLI mode, program output gets mixed with simulator messages ("Starting execution", "Loaded file", etc.), making it hard to distinguish actual program output. Adds quiet...

After simulation completes (status shows 'STOPPED' or 'HALTED'), clicking "Clear Code" did not reset the simulator status back to 'READY'. ### Changes - Added `worker.reset()` call in the `clearCode` function...

Adds UI tests for the Swing frontend to verify basic functionality: window rendering, menu presence, file parsing, and simulator execution. ### Changes - **Dependencies**: Added `org.assertj:assertj-swing:3.17.1` to build.gradle.kts - **CI**:...

The `htmlDocs` and `allDocs` tasks use `GradleBuild` type which spawns nested Gradle processes that don't participate in the parent build's parallel execution. This prevents documentation tasks from running in parallel...