gardar
gardar
I don't believe there is an official file extension, but from what I've seen .j2 .jinja and .jinja2 are widely accepted I'm mostly working with jinja in ansible and then...
@jakecoble did you ever manage to trace the source of this issue? I'm facing a similar issue myself. I've got a fresh install of aconfmgr but a not-so-fresh install of...
Sure thing, here's the full output with `-x`: https://gist.github.com/gardar/892d26ec4de0f7bace104deadff031d8
> Thanks. Unfortunately I can't tell what is failing from the log. > > Could you please try this patch (without `-x`), and post the output: https://github.com/CyberShadow/aconfmgr/compare/debug-find Here's the output...
I'm pretty certain GNU find can handle it just fine... I tried the find command and it ran successfully (printed `0` ) I tried adding all mounts except `/` to...
After tracing down a lot of directories to add to `IgnorePath` I figured out what the issue is! grep is eating all my ram and getting oom killed. I watched...
63M - 892248 lines
Strange! Could there be something else at play? If this was an issue with grep I would suspect others would be affected by this issue too. Here's the oom dmesg...
Yep, eats the memory too. I tried it on two other machines I have that are similarily set up, and both of them seem to be unaffected by this issue.
Found the culpit I think. Tried using ripgrep instead of grep but it failed with the following error: `/dev/fd/63:214314: found invalid UTF-8 in pattern at byte offset 22: O/usr/lib/aspell-0.60/\xEDslenska.alias (disable...