fix: correctly apply auto_unload setting from config
#5953
Merged
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.
Describe Your Changes
Previously, the
autoUnloadflag was not being updated when set via config, causing models to be auto-unloaded regardless of the intended behavior. This patch ensures the setting is respected at runtime.Thanks @louis-menlo for the help!
Important
Fixes issue in
index.tswhereautoUnloadwas not updated from config, ensuring it reflects theauto_unloadsetting at runtime.autoUnloadwas not updated from config inonSettingUpdate()inindex.ts.autoUnloadreflects theauto_unloadsetting at runtime.This description was created by
for 840a3e7. You can customize this summary. It will automatically update as commits are pushed.