Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First attempt at filing bugs if WDK is out-of-date #850

Merged
merged 1 commit into from
Dec 11, 2024
Merged

Conversation

Alan-Jowett
Copy link
Owner

@Alan-Jowett Alan-Jowett commented Dec 11, 2024

Description

Describe the purpose of and changes within this Pull Request.

Testing

Do any existing tests cover this change? Are new tests needed?

Documentation

Is there any documentation impact for this change?

Installation

Is there any installer impact for this change?

Summary by CodeRabbit

  • New Features
    • Introduced a new automated workflow to check for updates to the Windows Driver Kit (WDK) on a scheduled basis.
    • Workflow includes functionality to create an issue if the WDK version in the repository is outdated compared to the latest available version.

Signed-off-by: Alan Jowett <alanjo@microsoft.com>
Copy link

coderabbitai bot commented Dec 11, 2024

Walkthrough

This pull request introduces a new GitHub Actions workflow file named check_wdk.yml, which automates the process of checking for updates to the Windows Driver Kit (WDK). The workflow is scheduled to run weekly and can also be triggered manually. It includes steps for checking out the repository, retrieving the latest WDK version from NuGet, comparing it with the local version, and filing an issue if there is a version mismatch.

Changes

File Change Summary
.github/workflows/check_wdk.yml Added a new workflow to check for updates to the Windows Driver Kit (WDK) with scheduled runs.

Possibly related PRs

Poem

🐰 In the land of code where rabbits play,
A workflow hops in to check each day.
With WDK updates, it keeps us in line,
Every Sunday midnight, it runs just fine!
So let’s raise our ears and give a cheer,
For smooth updates coming throughout the year! 🎉


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@Alan-Jowett Alan-Jowett merged commit e18fc16 into main Dec 11, 2024
4 of 18 checks passed
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Outside diff range and nitpick comments (3)
.github/workflows/check_wdk.yml (3)

4-4: Fix incorrect workflow description comment

The current comment describes this as a build workflow, but this workflow actually checks for WDK updates.

-# This workflow performs a build of the project and uploads the result as a build artifact.
+# This workflow checks for Windows Driver Kit updates and files issues when updates are needed.

55-61: Enhance issue creation with more details

Consider improving the issue creation with more context and automatic assignment.

             await github.issues.create({
               owner: context.repo.owner,
               repo: context.repo.repo,
               title: 'Update the Windows Driver Kit',
-              body: 'The Windows Driver Kit version in the repository does not match the latest version available on NuGet. Please update the WDK version in the repository to match the latest version available on NuGet.',
+              body: `## WDK Version Update Required
+
+Current version: ${process.env.REPO_WDK_VERSION}
+Latest version: ${process.env.WDK_VERSION}
+
+Please update the WDK version in \`wdk.props\` to match the latest version available on NuGet.
+
+This issue was automatically created by the WDK version check workflow.`,
-              labels: ['wdk-update']
+              labels: ['wdk-update', 'dependencies'],
+              assignees: ['Alan-Jowett']
             });

1-62: Consider adding version compatibility checks

Before creating an issue for a WDK update, it would be valuable to verify that the latest version is actually compatible with your project. Consider:

  1. Maintaining a list of known compatible WDK versions
  2. Adding checks for breaking changes in the WDK release notes
  3. Including compatibility information in the created issues

This would help prevent unnecessary updates to incompatible versions.

Would you like assistance in implementing these compatibility checks?

🧰 Tools
🪛 actionlint (1.7.4)

20-20: property "skip_check" is not defined in object type {}

(expression)


22-22: property "repository" is not defined in object type {}

(expression)


24-24: property "ref" is not defined in object type {}

(expression)


28-28: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)


37-37: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 14bdf0d and eab58b2.

📒 Files selected for processing (1)
  • .github/workflows/check_wdk.yml (1 hunks)
🧰 Additional context used
🪛 actionlint (1.7.4)
.github/workflows/check_wdk.yml

20-20: property "skip_check" is not defined in object type {}

(expression)


22-22: property "repository" is not defined in object type {}

(expression)


24-24: property "ref" is not defined in object type {}

(expression)


28-28: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)


37-37: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)

Comment on lines +28 to +34
run: |
# Get the latest version of the Windows Driver Kit
$packages = nuget list "Microsoft.Windows.WDK.x64"
$packageLine = $package | Where-Object { $_ -match $packageName }
$packageVersion = $packageLine -replace "Microsoft.Windows.WDK.x64", ""
echo "::set-output name=wdk_version::$packageVersion"

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix PowerShell script and update deprecated workflow commands

The script has multiple issues:

  1. The $package variable is undefined but used in line 31
  2. The set-output command is deprecated

Apply these fixes:

     run: |
       # Get the latest version of the Windows Driver Kit
       $packages = nuget list "Microsoft.Windows.WDK.x64"
-      $packageLine = $package | Where-Object { $_ -match $packageName }
+      $packageLine = $packages | Where-Object { $_ -match "Microsoft.Windows.WDK.x64" }
       $packageVersion = $packageLine -replace "Microsoft.Windows.WDK.x64", ""
-      echo "::set-output name=wdk_version::$packageVersion"
+      "wdk_version=$packageVersion" >> $env:GITHUB_OUTPUT
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
run: |
# Get the latest version of the Windows Driver Kit
$packages = nuget list "Microsoft.Windows.WDK.x64"
$packageLine = $package | Where-Object { $_ -match $packageName }
$packageVersion = $packageLine -replace "Microsoft.Windows.WDK.x64", ""
echo "::set-output name=wdk_version::$packageVersion"
run: |
# Get the latest version of the Windows Driver Kit
$packages = nuget list "Microsoft.Windows.WDK.x64"
$packageLine = $packages | Where-Object { $_ -match "Microsoft.Windows.WDK.x64" }
$packageVersion = $packageLine -replace "Microsoft.Windows.WDK.x64", ""
"wdk_version=$packageVersion" >> $env:GITHUB_OUTPUT
🧰 Tools
🪛 actionlint (1.7.4)

28-28: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)

Comment on lines +35 to +40
- name: Check the version of the WDK in the repo
id: check_repo_wdk
run: |
$wdkVersion = (Get-Content -Path .\wdk.props | Select-String -Pattern "<WDKVersion>" | ForEach-Object { $_ -replace "<WDKVersion>", "" -replace "</WDKVersion>", "" }).trim()
echo "::set-output name=repo_wdk_version::$wdkVersion"

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add error handling and update deprecated workflow commands

The script needs error handling and uses deprecated commands.

     run: |
+      if (-not (Test-Path .\wdk.props)) {
+        Write-Error "wdk.props file not found"
+        exit 1
+      }
       $wdkVersion = (Get-Content -Path .\wdk.props | Select-String -Pattern "<WDKVersion>" | ForEach-Object { $_ -replace "<WDKVersion>", "" -replace "</WDKVersion>", "" }).trim()
-      echo "::set-output name=repo_wdk_version::$wdkVersion"
+      "repo_wdk_version=$wdkVersion" >> $env:GITHUB_OUTPUT
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Check the version of the WDK in the repo
id: check_repo_wdk
run: |
$wdkVersion = (Get-Content -Path .\wdk.props | Select-String -Pattern "<WDKVersion>" | ForEach-Object { $_ -replace "<WDKVersion>", "" -replace "</WDKVersion>", "" }).trim()
echo "::set-output name=repo_wdk_version::$wdkVersion"
- name: Check the version of the WDK in the repo
id: check_repo_wdk
run: |
if (-not (Test-Path .\wdk.props)) {
Write-Error "wdk.props file not found"
exit 1
}
$wdkVersion = (Get-Content -Path .\wdk.props | Select-String -Pattern "<WDKVersion>" | ForEach-Object { $_ -replace "<WDKVersion>", "" -replace "</WDKVersion>", "" }).trim()
"repo_wdk_version=$wdkVersion" >> $env:GITHUB_OUTPUT
🧰 Tools
🪛 actionlint (1.7.4)

37-37: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)

Comment on lines +20 to +24
if: steps.skip_check.outputs.should_skip != 'true'
with:
repository: ${{inputs.repository}}
submodules: 'recursive'
ref: ${{inputs.ref}}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix workflow configuration issues

Several critical issues need to be addressed:

  1. The skip_check step is referenced but not defined
  2. The workflow uses undefined inputs (repository and ref)

Either:

  1. Define the inputs in the workflow:
on:
  schedule:
    - cron: '0 0 * * 0'
  workflow_dispatch:
+    inputs:
+      repository:
+        description: 'Repository to check'
+        required: false
+        default: ${{ github.repository }}
+      ref:
+        description: 'Git ref to check'
+        required: false
+        default: ${{ github.ref }}

Or:
2. Remove the unused inputs:

     - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
-      if: steps.skip_check.outputs.should_skip != 'true'
       with:
-        repository: ${{inputs.repository}}
         submodules: 'recursive'
-        ref: ${{inputs.ref}}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
if: steps.skip_check.outputs.should_skip != 'true'
with:
repository: ${{inputs.repository}}
submodules: 'recursive'
ref: ${{inputs.ref}}
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
with:
submodules: 'recursive'
🧰 Tools
🪛 actionlint (1.7.4)

20-20: property "skip_check" is not defined in object type {}

(expression)


22-22: property "repository" is not defined in object type {}

(expression)


24-24: property "ref" is not defined in object type {}

(expression)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant