> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/release-notes/release-notes-10th-of-december-2018.md). # Release Notes - 10th of December 2018 ## Bug * maximum call stack size exceeded * file format limitations list * Einstein Vision: Can't duplicate a box if user is not admin - Access Denied * Toaster not toasting for Error only for Success * Einstein Prediction error: NoMethodError: undefined method \`original\_url' for nil:NilClass ## Features * Image counter on camera page * SharinPix Lightning Component supporting in new Visual Workflow * More specific error messages in Sharinpix Lightning Component * Einstein Vision : Creation of new model upon retrain * Annotation event to track image with/without annotation --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sharinpix.com/release-notes/release-notes-10th-of-december-2018.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.