Closed iranzo closed 5 years ago
I wonder if this bug is caused by the fact that you have so many modules talking to the same git repo. Under the covers peru is going to make them share a single cached repo, and it's possible that that leads to some of the caching machinery getting confused. Do you know what steps you might've taken to hit the bug? Maybe something like "the upstream repo forcefully rebases and then I peru sync
again" or something like that? So far with a simple sync I haven't been able to repro your problem.
All that said, you might be interested in the Rules section of the readme, for reducing the amount of duplication you have to write in your peru.yaml file. What you're doing here probably isn't an issue in most cases because of how caching works, but you might notice some less common cases (e.g. peru sync --no-cache
) where things substantially slow down, because most of your modules end up waiting on the same cache lock and so running only one-at-a-time.
Hi, thing is that that peru.yaml works fine sometimes and sometimes fail, and theoretically the upstream repo doesn't force rebases, so that's why I tried to either set or unset the peru cache dir and even clean it up to start clean again.
I've replaced the repos to rules:
imports:
# The dircolors file just goes at the root of our project.
elegant: themes/elegant/
plugins: plugins/
git module elegant:
url: https://github.com/Pelican-Elegant/elegant.git
rev: next
git module plugins:
url: https://github.com/getpelican/pelican-plugins.git
rule sitemap:
pick: sitemap
rule yuicompressor:
pick: yuicompressor
rule better_figures_and_images:
pick: better_figures_and_images
rule better_codeblock_line_numbering:
pick: better_codeblock_line_numbering
rule extract_toc:
pick: extract_toc
rule tipue_search:
pick: tipue_search
rule liquid_tags:
pick: liquid_tags
rule neighbors:
pick: neighbors
rule render_math:
pick: render_math
rule related_posts:
pick: related_posts
rule share_post:
pick: share_post
rule series:
pick: series
rule assets:
pick: assets
rule post_stats:
pick: post_stats
And cleaned the cache dir, and even tried with --no-cache
Is there any way I can try to get more debug information to help diagnosing this?
Thanks! Pablo
Tried -v and got this:
Traceback (most recent call last):
File "/home/iranzo/.bin/peru", line 11, in
Git clone of the repo works fine: git clone git@github.com:getpelican/pelican-plugins.git
Is maybe that submodule is listed even if not initialized and not available?
git submodule init git submodule update
does work (but that pelican-fontawesome) is not there either (but no error, etc)
Seems to have worked, I removed a trailing ".peru" subdir in current folder from previous attemps and now it syncs properly even on the PERU_CACHE_DIR, closing the issue.
Thanks a lot! Pablo
Interesting. I still suspect there's a bug here, so if you ever manage to run into this again (or if you still have a .peru
dir sitting around somewhere that you could tar up and send to me), let me know.
Sometimes and not in all computers I get a traceback like this:
With a peru.yaml like this:
Something wrong on my side? as the same peru.yaml works fine on other computers from time to time.
only variable set is the PERU_CACHE_DIR="~/.cache/peru", but either set or unset, I do get the same error.
Regards, Pablo