To identify the step that is using most of the computation time, I ran cProfile and got the following result: ncalls tottime percall cumtime percall fil
pitest
go-staticcheck
dotnetnuke-9
development-mode
shadow-dom
kairosdb
nrwl-nx
kendo-autocomplete
arcgis
ifc-open-shell
sensitive-data
mcps
terminusdb
vega-lite
google-cloud-firestore
nettcpbinding
ssdt-bi
index-management
sentora
column-major-order
vuejs-transition
lookbehind
designated-initializer
promela
bootstrap-cards
get-eventlog
bsp
sbt-docker-compose
unions
sign-extension