Bert Frees
Bert Frees
We only need to see in the log file which tables have issues, right? We don't need to see it in the Github interface. (But if there is one log...
OK but for parallelism we don't really need Github do we? (See e.g. https://www.gnu.org/software/parallel/.) (By the way generally I don't like having too much logic in the .github/workflows directory. I'd...
> Well, I would say that whenever we touch C code, we really want to fuzz with all tables Yeah, I was more talking about all the overhead that comes...
Awesome, thanks. Now how do we change this so that it is only triggered in changes to C code?
This PR is in pretty good shape now. But it has 55 commits. Could it be reduced? @sthibaul I don't just want to squash everything into a single commit because...
You mean recreate the .github/workflows/fuzzing.yml file? > the current branch only contains the fuzzing addition Yeah, I know. Not sure what do you mean by that?
Related: https://github.com/liblouis/liblouis/issues/954
https://github.com/liblouis/liblouis/issues/34
I think @dkager also had some problems with numericnocontchars, but I'm not sure what exactly. He's not using it in NL because of "unwanted side-effects". See commit 6379e3b.
Not sure what to do with this. Does this pose a real problem when creating tables?