Replies: 6 comments 2 replies
|
Bug is present in 0.1.5-rc3 as well, hit this bug twice already. The only way around it is to be sure to leave some context room for the LLM. Once you hit the bug, stop DSH, increase context window of the LLM by about 10%, then increase it in the settings of DSH as well and finally start DSH again. After that you can trigger a manual compaction, which will successfully finish. Once done, revert the context window setting and restart DSH so you can recover if you hit the bug again. |
|
Thanks for the report. |
|
It's broken in 0.1.7-rc.2 too |
|
Does anyone know if it's broken in 0.2.0 rc1/2? |
|
Explanations here: |
|
To investigate further, please share: your operating system and app platform; a log with tokens and personal information removed. |
Uh oh!
There was an error while loading. Please reload this page.
Auto-compaction not triggering in 0.1.7-rc1
In DeepSeek Harness
0.1.7-rc1, auto-compaction does not appear to trigger when the context window reaches its limit.Configuration:
80,000tokens32,000With these settings, the context continues to grow without triggering automatic compaction.
However, using the latest NPM release,
0.1.5-rc3, with the same configuration, auto-compaction works as expected.Expected behaviour
When the context approaches the configured context window limit, DeepSeek Harness should automatically trigger compaction, as it does in
0.1.5-rc3.Actual behaviour
In
0.1.7-rc1, auto-compaction is not triggered, and the context continues to grow until the context limit is reached.Reproduction
0.1.7-rc1.80kcontext window and32kmax output tokens.80ktokens.0.1.5-rc3using the same configuration. Auto-compaction triggers as expected.All reactions