6 Replies
That's a bit light on the details
Run mix credo --strict last_files_chaged.exs
Checking 29 source files ...
this command is taking approximately 30 min
I don't know how I can give more information that might help. I don't know if it's something in my code or if it's expected behavior.
is it that slow locally as well? the screenshot looks like github actions
yes slow locally too
credo has a
--debug flag, that gives a you a report and shows which rules/files took the longest, maybe that can give you a hintThanks to the --debug flag, I was able to identify the root cause of the issue — it was related to a very large file in my project, which was making tools like mix credo appear slow or unresponsive.
Just to clarify:
The issue was not caused by the Ash Framework itself. Ash continues to work perfectly and wasn't responsible for the slowdown. The performance issue was due to the size and structure of a specific file in my codebase, which impacted static analysis tools.