Resolved Custom IO file not found via CLI #556
+243
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves an issue encountered when executing the model via CLI, where an error was raised due to the absence of the custom_IO.yaml file. In previous versions, the CLI did not explicitly generate a separate configuration for custom I/O. To address this, a script has been added that automatically creates the custom_IO.yaml file based on the specified modeling class.
Additionally, an optional argument --mxint8_kv_cache has been introduced in QEfficient.cloud.export(). This flag enables compression of the Present/Past KV cache to MXINT8 format using the generated CustomIO configuration.