When the ray cluster runs for a long time or execute many tasks, log files can be large, such as monitor.err, full of could not find ip for client xxxx. I find parameters logging_level, logging_format and log_to_driver in ray.init(). Is there a way to restrict the size of log files by default, like using logging.handlers.RotatingFileHandler and set maxBytes?

![image](https://user

Is your feature request related to a problem? Please describe.
Currently, I have to search code sample on HTTP servlet when I am writing a new rule from scratch in Semgrep editor.

Describe the solution you'd like
Add a generic HTTP servlet code to the existing sample java code. This will be useful for writing a rule that involves the request and response.

I'm sorry if I missed this functionality, but CLI version hasn't it for sure (I saw the related code only in generate_code_examples.py). I guess it will be very useful to eliminate copy-paste phase, especially for large models.

Of course, piping is a solution, but not for development in Jupyter Notebook, for example.

We noticed that we have some common patterns for common conflicts/duplicate resolution in our monorepo across different binaries.
Like

  deploy_jar_rules=jar_rules(rules=[
    Duplicate('^BUILD', Duplicate.SKIP),
    Duplicate('^META-INF/ASL2.0', Duplicate.SKIP),
    Duplicate('^META-INF/INDEX.LIST', Duplicate.SKIP),
    Duplicate('^META-INF/io.netty.versions.properties', Duplicate.SKIP