DavidKorczynski

> Other UIs are available to get flame graphs cf https://www.markhansen.co.nz/profiler-uis/ FYI a few months ago we used Prodfiler to debug some of the Envoy fuzzers (check page 10 in...

I think it would be really nice to get this added and add the flame graphs to Fuzz Introspector

I think the easiest from Fuzz Introspector's perspective would be to accept the `.svg` file and perhaps a textual representation of what the flamegraph represents, rather than having Fuzz Introspector...

Looks like python can't find docker? The code is fully integrated as a regular project so you shuludn't expect anything unusual in the oss-fuzz infra.

Awesome! Let me know how you'd prefer to place this. It would work well from my perspective (i.e. for further development) to simply place it somewhere in the Docker images...

fyi a project is already running with the first version of pysecsan: https://github.com/google/oss-fuzz/blob/d76fb7d57925e4a8bed86c7176354a71de3c1831/projects/pyxdg/fuzz_menu.py#L20-L21 It just uses the packaged version https://pypi.org/project/pysecsan

is this ready for merge?

@michaelni could you assist reviewing?

The following config file gives me an infinite recursion: ``` @INCLUDE * ``` The problem is the line https://github.com/fluent/fluent-bit/blob/93ece8d7d415c8cb50b7b757ec4b956edcdefd68/src/config_format/flb_cf_fluentbit.c#L514 Will end up triggering https://github.com/fluent/fluent-bit/blob/93ece8d7d415c8cb50b7b757ec4b956edcdefd68/src/config_format/flb_cf_fluentbit.c#L177 Which calls `read_config` again, which then...

@nokute78 thanks, note you're using a different config than the one I post (I *only* have `INCLUDE *` in the config, nothing else) which I assume would break the infinite...