finanalyst/collection

Collects content files written in Pod6 (Rakudoc) into (eg) a website

collection's Issues

Is there a binary that can be used directly to generate files?

In "Usage" just a reference to the author tests is made.

can't install Collection

===> Building: Collection:ver<0.15.8>:authzef:finanalyst
[Collection] Released plugin directory exists at ｢/Users/coke/.local/share/Collection｣
[Collection] From https://github.com/finanalyst/collection-plugins
[Collection] 677b2a1..30f02f3 main -> origin/main
[Collection] error: Your local changes to the following files would be overwritten by merge:
[Collection] plugins/html/typegraph_v0_auth_collection/typegraphs/Int.svg
[Collection] Please commit your changes or stash them before you merge.
[Collection] Aborting
===> Building [FAIL]: Collection:ver<0.15.8>:authzef:finanalyst
Aborting due to build failure: Collection:ver<0.15.8>:authzef:finanalyst (use --force-build to override)

Resource usage gets overwhelming during secondary generation

Hello,

this issue arised while I was trying to build the doc website locally. I think it's a technical issue that doesn't really have a place in that repo and not many people would care anyway.

I used to be able to build on my WSL2 Ubuntu instance. For quite a while now, all I got was "Killed" after a long time, and well into the secondary generation. As it turns out, while the memory usage of the tool is pretty high overall (gigabyte magnitude), it really skyrockets during secondary generation, often eating up 20 megabytes per second. Ultimately, it ran out of my 4GB RAM and 1 GB swap and got killed.

I could remedy this by raising the swap file on my rather limited machine to 8 GB, and could witness that the memory usage didn't simply peak at 6GB but the tool would never ever give any of that memory back while it's running, even in the serving phase...

6GB is so much that downright loading all the resources into the memory would still be magnitudes less memory usage and it's very worrying that the tool never gives any memory back. Probably it should stop overconsuming in the build phase already.

I don't know the reason and this is what I'd like to get help with. Is there some resource leak in the tool, memory leak in Rakudo, is the caching more aggressive than it should be, or any permutation of these?