> For the complete documentation index, see [llms.txt](https://docs.zama.org/concrete-ml/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zama.org/concrete-ml/developers/debug_support_submit_issues.md). # Support and issues Concrete ML is a constant work-in-progress, and thus may contain bugs or suboptimal APIs. Before opening an issue or asking for support, please read this documentation to understand common issues and limitations of Concrete ML. You can also check the [outstanding issues on github](https://github.com/zama-ai/concrete-ml/issues). Furthermore, undefined behavior may occur if the input-set, which is internally used by the compilation core to set bit-widths of some intermediate data, is not sufficiently representative of the future user inputs. With all the inputs in the input-set, it appears that intermediate data can be represented as an n-bit integer. But, for a particular computation, this same intermediate data needs additional bits to be represented. The FHE execution for this computation will result in an incorrect output, as typically occurs in integer overflows in classical programs. If you didn't find an answer, you can ask a question through the [community channels](https://zama.ai/community-channels). ## Submitting an issue When submitting an issue ([here](https://github.com/zama-ai/concrete-ml/issues)), ideally include as much information as possible. In addition to the Python script, the following information is useful: * the reproducibility rate you see on your side * any insight you might have on the bug * any workaround you have been able to find If you would like to contribute to a project and send pull requests, take a look at the [contributor](/concrete-ml/developers/contributing.md) guide. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.zama.org/concrete-ml/developers/debug_support_submit_issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.