Error: "Semver match 3.19.0 to <2.15.1 || >=3.0a1 <3.0.0b9"

[lesiki]

I'm getting [ERROR] Semver match 3.19.0 to <2.15.1 || >=3.0a1 <3.0.0b9 after analysing paths.

The process then seems to freeze - no further logging beyond this. I've tried leaving it for up to 1 hour.

I'm not sure how to interpret this - is there a dependency in my python project with a versioning scheme that confuses the system or doesn't match some requirement? How do I find out which one?

[nate-penner]

I am experiencing a similar problem where it freezes. I do not have the same error message, but on a certain project, it hangs after analyzing the last path, whereas on two other projects it works fine. I am running the casa scan docker container, and it ran with the error: '[ERROR] Computing commit hash: SHA could not be resolved, git returned: b''

However, my other project scans succeed, despite having this same error. The failing project is a react web app.

Edit: In my case, I was running the CASA scan on a VM with only 1 core. When I upped the VM to 4 cores, it completed after a couple minutes. I suspect the skims scan for F085 is computationally intensive. I had found that by either removing two specific files, or removing this scan, it would succeed almost immediately after analyzing the last path (even with only a single core). Hope that helps someone in the future if they read this.