This project uses GitHub Issues to track bugs and feature requests. Before filing a new issue, please search the existing issues to avoid duplicates. If you find a related issue, add a 👍 reaction or a comment with additional context instead of opening a new one.
When the existing issues do not cover your problem, open a new issue and choose the type that best matches your request:
- Bug report — include the kompli version, the Linux distribution and version, the procedure or benchmark involved, the exact command you ran, the relevant portion of the logs, and the expected versus actual behavior. A minimal reproduction (for example, the JSON/MOF payload or Lua snippet) makes triage much faster.
- Feature request — describe the use case, the benchmark or control it relates to, and why the existing functionality is insufficient.
- Question / usage help — for "how do I…" questions, start a thread in
GitHub Discussions when it is
enabled; otherwise open an issue with the
questionlabel.
To help others find answers, please keep one topic per issue and use a clear, specific title.
Do not report security vulnerabilities through public GitHub issues, discussions, or pull requests. Follow the coordinated disclosure process described in SECURITY.md instead.
If you would like to fix a bug or implement a feature yourself, see CONTRIBUTING.md for development, testing, and pull-request guidelines.
Kompli is maintained by Microsoft. Issues and pull requests are reviewed on a best-effort basis and the maintainers aim to respond to new, well-formed issues within a few business days. There is no guaranteed service-level agreement for this open-source project, and response times may vary around holidays and release cycles.
Support for kompli is limited to the resources listed above. For questions about the kompli project that are not suited to a public issue, you may contact the team at kompli@microsoft.com.