alamb opened a new issue, #4683:
URL: https://github.com/apache/arrow-rs/issues/4683

   **Describe the bug**
   I was trying to render the docs while working on 
https://github.com/apache/arrow-rs/pull/4682 and I hit an error
   
   ```
   error: unresolved link to `ObjectStore::copy_if_not_exists`
     --> src/aws/copy.rs:20:32
      |
   20 | /// Configure how to provide [`ObjectStore::copy_if_not_exists`] for 
[`AmazonS3`]
      |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no item 
named `ObjectStore` in scope
      |
   note: the lint level is defined here
     --> src/lib.rs:18:9
      |
   18 | #![deny(rustdoc::broken_intra_doc_links, rustdoc::bare_urls, 
rust_2018_idioms)]
      |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   
   error: unresolved link to `AmazonS3`
     --> src/aws/copy.rs:20:72
      |
   20 | /// Configure how to provide [`ObjectStore::copy_if_not_exists`] for 
[`AmazonS3`]
      |                                                                        
^^^^^^^^ no item named `AmazonS3` in scope
      |
      = help: to escape `[` and `]` characters, add '\' before them like `\[` 
or `\]`
   
   error: unresolved link to `ObjectStore::copy_if_not_exists`
     --> src/aws/copy.rs:27:19
      |
   27 |     /// If set, [`ObjectStore::copy_if_not_exists`] will perform a 
normal copy operation
      |                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no item named 
`ObjectStore` in scope
   
   ```
   
   This appears to have been added in 
https://github.com/apache/arrow-rs/pull/4239 but I couldn't find any CI jobs 
that check the object_store docs
   
   
   **To Reproduce**
   ```shell
   cd object_store
   cargo doc --all-features
   ```
   
   **Expected behavior**
   Docs should build cleanly, and that should be verified by CI
   
   **Additional context**
   <!--
   Add any other context about the problem here.
   -->


-- 
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