Note: To build on Windows, first one must update swift-nio to this revision or later:
apple/swift-nio@8b66b22

@jeffdav Could you enable Windows CI so we can track this properly? See https://github.com/vapor/jwt-kit/blob/main/.github/workflows/test.yml#L35

Sure. But we may have to wait for swift-nio to ship a new minor revision.

Yeah I'm not expecting it to pass but we can at least track the errors across the modules and make sure we don't add regressions in new code. It will be a while until NIO ships a windows compatible version

@0xTim #206
I'm not super familiar with your workflows but it seems straightforward enough. LMK if this isn't what you meant.

BTW when I run swift test with these fixes + the swift-nio fixes everything does pass. I.e. with this locally:

    ],
    dependencies: [
        .package(url: "https://github.com/apple/swift-log.git", from: "1.5.3"),
        .package(url: "https://github.com/apple/swift-nio.git", revision: "8b66b22895115954dca2f1a6c5ab67172b6a6a1c"),
    ],

It looks like swift-nio does releases pretty frequently, so hopefully won't have to wait too long for it!

Codecov Report

Attention: Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.

Project coverage is 54.11%. Comparing base (a44d671) to head (bc3eee0).
Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main     #205      +/-   ##
==========================================
- Coverage   54.18%   54.11%   -0.08%     
==========================================
  Files         103      103              
  Lines        4603     4609       +6     
==========================================
  Hits         2494     2494              
- Misses       2109     2115       +6     

Ah yeah, we're only using NIOConcurrency helpers, not the rest of NIO. Pity we had to pull that in but those fixes should land soon!

SwiftNIO released 2.76.0 with the fixes in it. I believe a rerun of the windows-unit workflow will pass now.