amoeba commented on PR #3695:
URL: https://github.com/apache/arrow-adbc/pull/3695#issuecomment-3513235042

   Testing here on CI. I based this PR branch on a commit before the fix so 
this should fail on CI with this error,
   
   ```
   error[E0432]: unresolved import `windows_sys`
       --> driver_manager\src\lib.rs:1755:9
        |
   1755 |     use windows_sys as windows;
        |         ^^^^^^^^^^^^^^^^^^^^^^ no external crate `windows_sys`
   
   error[E0433]: failed to resolve: use of unresolved module or unlinked crate 
`windows_registry`
      --> driver_manager\src\lib.rs:554:17
       |
   554 |                 windows_registry::CURRENT_USER,
       |                 ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked 
crate `windows_registry`
       |
       = help: if you wanted to use a crate named `windows_registry`, use 
`cargo add windows_registry` to add it to your `Cargo.toml`
   
   error[E0433]: failed to resolve: use of unresolved module or unlinked crate 
`windows_registry`
      --> driver_manager\src\lib.rs:573:17
       |
   573 |                 windows_registry::LOCAL_MACHINE,
       |                 ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked 
crate `windows_registry`
       |
       = help: if you wanted to use a crate named `windows_registry`, use 
`cargo add windows_registry` to add it to your `Cargo.toml`
   
   error[E0433]: failed to resolve: use of unresolved module or unlinked crate 
`windows_registry`
      --> driver_manager\src\lib.rs:677:12
       |
   677 |     root: &windows_registry::Key,
       |            ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate 
`windows_registry`
       |
       = help: if you wanted to use a crate named `windows_registry`, use 
`cargo add windows_registry` to add it to your `Cargo.toml`
   ```
   
   After I confirm that, I'll rebase and see if CI passes.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to