-
Notifications
You must be signed in to change notification settings - Fork 51
fix: Fixes in llm after QA #309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| **`modelSource`** - `ResourceSource` that specifies the location of the model binary. For more information, take a look at [loading models](../fundamentals/loading-models.md) section. | ||
|
|
||
| **`tokenizerSource`** - URL to the JSON file which contains the tokenizer. | ||
| **`tokenizerSource`** - `ResourceSource` pointing to the JSON file which contains the tokenizer. | ||
|
|
||
| **`tokenizerConfigSource`** - URL to the JSON file which contains the tokenizer config. | ||
| **`tokenizerConfigSource`** - `ResourceSource` pointing to the JSON file which contains the tokenizer config. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this solves the problem @jakmro mentioned, maybe we should direct here to loading models. In fact we should rename loading models to loading resources, perhaps?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ResourceSourcethat specifies the location of the model binary. For more information, take a look at loading models section.
I direct readers to the details pages here. I think it is enough
| } | ||
|
|
||
| type ResourceSource = string | number; | ||
| type ResourceSource = string | number | object; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this an object btw?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is object when we use require to load the resource. It's like that all over the code, somebody simply forgot to change it here
This PR aims to organize our sidebar in docs by introducing a separation for hooks and TypeScript API. The order of specific subpages will be now configured by editing `sidebars.js`, instead of the default Docusarus way. This PR also changes some styling to make the indentations look prettier. - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Documentation update (improves or adds clarity to existing documentation) - [ ] iOS - [ ] Android <!-- Provide step-by-step instructions on how to test your changes. Include setup details if necessary. --> <!-- Add screenshots here, if applicable --> <!-- Link related issues here using #issue-number --> - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have updated the documentation accordingly - [ ] My changes generate no new warnings <!-- Include any additional information, assumptions, or context that reviewers might need to understand this PR. --> --------- Co-authored-by: Mateusz Kopciński <mateusz.kopcinski@swmansnion.com>
d81f973 to
42b1c96
Compare
Description
Fixes in generate, error handling and docs
Type of change
Tested on
Related issues
#305
Checklist