Projects plugin cache not being updated

[alexvoss]

Context

Using the projects plugin in Insiders, I am having the problem that it seems the cache is never updated.

Bug description

Changes to the mkdocs.yml files in project do not get picked up. I am changing the color scheme as an example, see below. It seems the config.pickle file in .cache is not getting updated when a mkdocs.yml file in a project is changed.

Related links

• Reporting a bug
• https://squidfunk.github.io/mkdocs-material/plugins/projects/#caching

Reproduction

9.4.8+insiders.4.43.0-projects-plugin-cache.zip

Steps to reproduce

1. rm -rf .cache
2. mkdocs serve
3. Open subproject in a browser and observe that the project has an indigo palette
4. In another window, edit the project's mkdocs.yml to set the palette to red
5. Make a change to the docs/index.md to see that the browser updates
6. You will see that while the change from (5) shows, the palette is still indigo
7. Restart mkdocs serve
8. Observe that the color scheme still has not changed.
9. Stop mkdocs serve
10. rm -rf .cache
11. Start mkdocs serve
12. Observe that the color scheme has changed now.

Btw. I selected a browser below without thinking and it seems this selection cannot be reset?

Browser

Other

Before submitting

• I have read and followed the bug reporting guidelines.
• I have attached links to the documentation, and possibly related issues and discussions.
• I assure that I have removed all customizations before submitting this bug report.
• I have attached a .zip file with a minimal reproduction.

[squidfunk]

Thanks for reporting! Could you maybe check if data is updated when you disable the cache:

plugins:
  - projects:
      cache: false

[alexvoss]

Will do. As soon as I managed to produce a new zip file - because the info plugin did not include the projects directory?

[alexvoss]

Ok, here is the new .zip file.
9.4.8+insiders.4.43.0-projects-plugin-cache.zip

[alexvoss]

Ok, with cache: false a cache is still being created, which might be something to change. Also, the palette does not update. In contrast to the version with no setting for cache, it does change on a restart of mkdocs serve. I think this is how I have been rolling with the examples, have cache turned off and restart whenever I made a chance to a mkdocs.ymlfile.

I did try to debug this but the only thing I could find out is that line 108 in plugin.py might need to be and not self.is_root: instead of or not self.is_root:?

Changing this alone did not fix it, though.

[squidfunk]

The cache must be created - we need a way to store intermediate results. This is the same for all plugins. What we could do in theory (but I haven't done it, because nobody complained) is to create a temporary directory and use that for intermediate storage, but the plugins definitely need intermediate storage. Thus, cache disables cache usage, not the cache itself.

I'll investigate as soon as possible.

[squidfunk]

Fixed in f0b2a6e. My testing shows that the editing experience is much smoother now. In fact, we forgot to update the cache that must be used in nested projects when detecting a change and reloading the configuration. That's now sorted.

By the way, I'm very sorry this took so long, but you know: #6307 kind of eats up all my time right now 😅

[squidfunk]

Released as part of 9.4.10+insiders-4.43.1.

[squidfunk]

@alexvoss does this work better for you now?

[alexvoss]

Did a quick test by modifying the mkdocs.yml files in one of our examples and it did get picked up. Thanks for fixing this. I will try and do some more work with the projects plugin in the coming days and will report any remaining issues I find but this fix and the other one that helped with newly created projects or those that do not use Material fix the two issues I had some across - IIRC.

[squidfunk]

That's great to hear! I'm really looking forward making the editing experience as smooth as possible.