These are chat archives for coala/coala-bears
confidenceparameter affects the results/reports? I couldn’t find in documentation.
confidenceis just a number between 0 and 100 describing the likelihood of this result being a real issue. What do you mean by how it affects the results?
pip show coalais raising an exception because of your name :smile:
pip show coala is raising an exception because of your name :smile:
Then you should use
@Makman2 Implementation difficulties aside, why do you think it doesn’t make sense, and doesn’t align with coala’s concepts? I’m not pushing for a new radical feature here. Just trying to understand why things are the way they are. It’ll help me set things up.
What bear gets priority working on a file when multiple bears want to work on it?
Is there a concept of priority now? The bears could run in any order, considering the dependencies.
And what if you run two bears, and both emit patches, and you don't accept the first one, what happens with the second patch? Because it builds on the first
I don’t see a problem. Why wouldn’t it work the same way as now as if
--jobsis set to 1?
I have a small bunch of bears which perform simple analysis. I have a large set of files waiting for analysis. Instead of splitting these simple tasks into multiple bears to achieve concurrency (with the associated problem of patch conflicts), I was just wondering why not assign each file’s processing to a process in a pool, wherein the bears will be run sequentially on the file. There wouldn’t be any patch conflict this way. Usually, the set of bears is limited, but the number of source files is more.
clang ast being shared by multiple bears
I know this can’t happen with the process pool.
Then you should use pip3 :wink:
Same issue with pip3 as well. This is trivial, but does it work for you, @Makman2?