Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

[cpplint] reported by reviewdog 🐶 Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2] Raw Output: src/filter/filmgrain/filmgrain.c:32: Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2]

[cpplint] reported by reviewdog 🐶 Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2] Raw Output: src/filter/filmgrain/filmgrain.c:228: Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2]

[cpplint] reported by reviewdog 🐶 Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2] Raw Output: src/filter/filmgrain/filmgrain.c:241: Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2]

[cpplint] reported by reviewdog 🐶 Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2] Raw Output: src/filter/filmgrain/filmgrain.c:243: Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2]

[cpplint] reported by reviewdog 🐶 Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2] Raw Output: src/filter/filmgrain/filmgrain.c:245: Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2]

[cpplint] reported by reviewdog 🐶 Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2] Raw Output: src/filter/gateweave/gateweave.c:38: Consider using rand_r(...) instead of rand(...) for improved thread safety. [runtime/threadsafe_fn] [2]