Invalidate cached WebAssembly binaries about web-llm

[CharlieFRuan]

Thanks for the suggestion! We are thinking about adding versioning to the binary name, say Llama-v0.2.21, then when updating it we update it to Llama-v0.2.22 so the outdated one in user's cache will not be used and be removed.

[CharlieFRuan]

I don't think the recent changes require redownloading. Besides, if we were to redownload a model, only the model library (tens of MB) is needed, not the weights.

[CharlieFRuan]

@UXDart This shouldn't be related to the model library versioning issue described by the OP. Seems to be more related to #322 and #313. Will look into this issue today; meanwhile clearing the cache might alleviate the issue as a temporary workaround.

[CharlieFRuan]

Update: we now support wasm versioning such that whenever a new version of wasm is required, we will download the new wasm (since the URL is different). The idea is that each web-llm npm version binds to a wasm version. See the PR below for more:

• #355

[UXDart]

but what recently changed that a re download was needed of the model? we can't make each user download 10+GB too many times... thanks

[UXDart]

it's been already a few times that even on the chat demo, I need to clear the cache to be able to to make it work. it just happens in the last release of the npm web llm, I updated from .20 to .23 and get this error, I can't find the reason, when calling reload mistral model get ExitStatus {name: 'ExitStatus', message: 'Program terminated with exit(1)', status: 1} when it is on 40-60%. if I clear the cache it works but then it can't load from cache again. if I go back to .20 it works ok. what it could be? thanks - using chrome on mac

[kudaibergenu]

it's been already a few times that even on the chat demo, I need to clear the cache to be able to to make it work. it just happens in the last release of the npm web llm, I updated from .20 to .23 and get this error, I can't find the reason, when calling reload mistral model get ExitStatus {name: 'ExitStatus', message: 'Program terminated with exit(1)', status: 1} when it is on 40-60%. if I clear the cache it works but then it can't load from cache again. if I go back to .20 it works ok. what it could be? thanks - using chrome on mac

Same happens to me for every model on chrome extension. Do not know how to fix it. I am also using chrome on mac

[CharlieFRuan]

@UXDart @kudaibergenu Just updated the npm to 0.2.24: #323

This should fix it. Let us know if issues persist. Thank you!