OCaml good first issues

AI Summary: This issue proposes a performance optimization by detecting and replacing sequential calls to related Stan math functions with their combined, more efficient counterparts. The goal is to eliminate redundant computations when functions like `qr_Q` and `qr_R` are called consecutively, by instead using the single `qr` function. A warning mechanism is also suggested for models that continue to use the older, separate function calls.

AI Summary: The issue proposes to refine exception handling for `Miou_unix.connect`. The current documentation states it only raises `Invalid_argument _`, but the reporter suspects other exceptions might be thrown, necessitating a more precise catch mechanism.

AI Summary: This issue requests the ability to configure the InfluxDB port, as it is currently hardcoded. This would involve making the port a configurable parameter rather than a fixed value within the application.

AI Summary: This issue proposes adding support for using hostnames instead of only IP addresses when configuring InfluxDB connections. This would improve flexibility and usability by allowing users to leverage DNS for managing their InfluxDB instances.

AI Summary: This issue proposes the deletion of an unreferenced and outdated scratch module `src/test.ml`. The module is not used, its name is misleading, and it unnecessarily contributes to the build process. The fix involves removing the file and updating the build configuration.

AI Summary: The README file for the project is currently a minimal stub and lacks essential information for new users and contributors. This issue proposes expanding the README to include a project description, a quickstart guide for building and testing, details on the development workflow and test locations, and potentially a CONTRIBUTING.md file.

AI Summary: This issue identifies approximately 500 instances of bare `with _ ->` exception handlers in the codebase, which can hide critical errors and make debugging difficult. The proposed solution involves an incremental approach: disallowing new bare handlers, routing 'best effort' exceptions through logging, and gradually refactoring existing offenders, particularly in frequently modified files.

AI Summary: The repository has lost its automated testing CI on GitHub after a recent commit removed the test workflow. This means that build and test regressions can go unnoticed on the master branch. The issue proposes restoring a test workflow, potentially a simplified version of the previous one, to act as a fast gate for changes, while also suggesting updates to deprecated GitHub Actions versions in the existing documentation workflow.

AI Summary: Users are reporting that formatting dune files on save, typically handled by editor extensions, is failing when Dune's build is running in watch mode. This is suspected to be a regression introduced around Dune version 3.21, likely due to conflicts with build locks.

AI Summary: The `sem.malloc.fail` option in memory leak analysis is causing a reduction in precision, particularly when `free` is called on pointers that might be NULL. This is because `free(NULL)` is a no-op and should not affect leak detection, but it appears to be causing discrepancies in the analysis results. This issue impacts a significant number of tasks within the sv-benchmarks suite.

AI Summary: This issue reports that enabling `sem.malloc.fail` in a benchmarking environment causes unexpected behavior in tasks that utilize `alloca`. The problem arises because `alloca` is documented to never return NULL, implying a potential conflict with the simulated malloc failure.

AI Summary: This issue is a discussion about the ideal error handling strategy for the 'wyzer' programming language. The author suggests deviating from Rust's approach to create a unique system that aligns with wyzer's core ideologies, aiming for a more enjoyable developer experience. It's labeled as an enhancement and a good first issue.