Puppet Community

I’d add explicit log message into the method to ensure.. as it’s really strange that there is no reference to this module

or something else is calling it from any other place

there's a systemd timer to import new modules from the forge, but that's not triggering it

opening <https://www.puppetmodule.info/modules/puppetlabs-apache/8.6.0> for the first time will trigger the load_yardoc_from_remote_module method

`Dec 21 09:38:50 voxpupu <http://puppetmodule.info|puppetmodule.info>[1081356]: 2022-12-21 09:38:50 +0100: Downloading remote module tarball for release puppetlabs-apache-8.6.0`

so this is a method for LibraryVersion and that's used in app.rb and in the gem_store. We don't use gem_store directly, but module_store inherits from gem_store. I'm wondering if there's some kind of autowiring/sinatra magic

```      alias yardoc_file_for_remote_gem source_yardoc_file
      alias yardoc_file_for_remote_module source_yardoc_file
      alias yardoc_file_for_disk_on_demand source_yardoc_file
      alias yardoc_file_for_github source_yardoc_file```

I should do a talk about our infra in the future

ah no.. there are “_for_” methods but we’re looking for “_from_” method

`git grep load_yardoc_from_remote_module` doesn't find any references to it, just the definition. Similar to expand_module. that's defined in the same file and only load_yardoc_from_remote_module references it (that's the method that does the actual module download).

I guess it’s easier to raise an exception in the method and see the backtrace :smile:

I think what's happening is <https://github.com/lsegal/yard/blob/main/lib/yard/server/library_version.rb#L49-L66>

and the call is <https://github.com/lsegal/yard/blob/main/lib/yard/server/library_version.rb#L182-L186>

(did I mention I dislike ruby for such practices?)

<https://gist.github.com/bastelfreak/5f207973c6f91685b565a361c404fc23> that's the trace

the rest is left as an excercise to the reader