Conversation
Problem: - CI/CD was failing on Linux when trying to run .NET Framework 4.8 tests - .NET Framework requires Windows environment, not Linux/Mono Solution: - Split tests by platform: - Ubuntu (Linux): Run only .NET 8.0 tests with --framework net8.0 - Windows: Run .NET Framework 4.8 tests with --framework net48 Changes: - Added build-windows job for Windows-specific tests - Updated Linux tests to use --framework net8.0 - Updated job dependencies to include Windows build - Maintained coverage reports on Linux only Benefits: - ✅ All target frameworks tested on appropriate platforms - ✅ No more Mono dependency issues on Linux - ✅ Faster CI pipeline with platform-specific jobs - ✅ Better test isolation and reliability 🎯 CI/CD now supports all target frameworks correctly!
Feature/update actions
Problem: - PowerShell was interpreting '--' as unary operators - Multi-line commands with backslashes were causing syntax errors - Error: 'Missing expression after unary operator --' Solution: - Convert multi-line commands to single-line format - Remove backslashes and combine all parameters on one line - Maintain same functionality with proper PowerShell syntax Changes: - dotnet test commands now use single-line format - All parameters combined on one line for Windows PowerShell compatibility - Preserved all test configuration and logging 🎯 Windows tests should now run without PowerShell syntax errors!
🔧 Fix PowerShell command formatting for Windows tests
Problem: - 'dotnet list package --vulnerable' found multiple solution files - Error: 'Found more than one solution file' - Command failed without specifying which solution to use Solution: - Add MetarDecoder.sln parameter to the command - Explicitly specify the solution file to scan - Ensure consistent behavior across environments Changes: - dotnet list package MetarDecoder.sln --vulnerable --include-prerelease - Targets the main solution file directly - Removes ambiguity in multi-solution scenarios 🎯 Security scan will now run without file conflicts!
🔧 Fix security scan command to specify solution file
Problem: - 'dotnet list package' doesn't accept solution file as direct argument - Error: 'Unrecognized command or argument MetarDecoder.sln' - Command syntax was incorrect for vulnerability scanning Solution: - Remove explicit solution file specification - Let command auto-detect solution in current directory - Use correct syntax for vulnerability checking Changes: - dotnet list package --vulnerable (without solution file) - Command will automatically find and scan MetarDecoder.sln - Simplified and more reliable execution 🎯 Security scan now uses correct .NET CLI syntax!
🔧 Fix security scan command syntax
Owner
Author
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
All Submissions:
New Feature Submissions:
Changes to Core Features: