Context size in Lite Web interface does not correspond to one set in launcher and used by backend

[alex-ie]

Describe the Issue

1. I have set 1024 context size in launcher, I see 23744 in Lite web interface with max 8192 in slider. Max Output is 2048 whereas in log I see Generating (xxx / 820 tokens), so actual max size is 820.

2. Changing context size via Lite does not seem to attect actual context used by backend - after increase in Lite I see in log same CtxLimit, after decrease in Lite I don't see any more free memory. What is the point of changing Context Size in Lite? (changing Max Output does change results of backend).
   Could Lite and backend be more 'synchronized' for Context Size?
   TIA

Additional Information:
v1.111.2

P.S.
Do such issues belong more in https://github.com/LostRuins/lite.koboldai.net/issues?

[LostRuins]

It is synchronized at launch. If you refresh the window you should see the slider max context will match what you set in koboldcpp. After that, you can lower it in lite if you want (but not raise it above), this is for cases where you don't want to use the full context.

[alex-ie]

@LostRuins

you can lower it in lite if you want (but not raise it above), this is for cases where you don't want to use the full context.

I could not think of use case myself now, but flexibility is useful. Thanks.

It is synchronized at launch. If you refresh the window you should see the slider max context will match what you set in koboldcpp.

Ctx synchronized only for >=8192, otherwise it sets to 8192 for slider. And Max Output is set to some value I guess based on ctx, not synchronized - why not?

E.g. I set ctx=6144 and MaxSize=4096 in launcher and got 8192 ctx and 1024 MaxOutput in Lite.
And a bit later for same ctx=6144 and MaxSize=4096 in launcher got ctx (Context Size) 131072 (slider max 8192). What was new unexpected.
In log output of backend: Request max_context_length=131072 exceeds allocated context size of 6144, which hints it is indeed possible bug.

I often Ctrl-C koboldcpp and start new one in bash, usually with new Network port, sometimes same. Could the above 'bug' be because new run reads some cached data on disk from previous run? Indeed the run just before 2nd with ctx=6144 was run with ctx=131072.

Now I vaguely recall in recent days several times in a row (I've checked) I saw in log output of backend Request max_context_length=XXXXXX exceeds allocated context size of 131072 - where XXXXXX was a number slightly higher than 131072 and 131072 I carefully set in launcher using slider only (and rechecked on next run to be sure after seeing such unexpected line in log output). Now I guess it was due to Lite incorrectly setting Context Size at launch, so there likely is some bug setting/syncing Context Size even for ctx >8192.

[alex-ie]

@LostRuins I have just realized I am supplying edge cases (not corner ones though - seems as Linus wrote in 7.0 Linux release message one is expected to get them from AI now :) and the question if you have time for them or there is more important work now. Cheers.

[LostRuins]

Don't worry, if its too much the backend will automatically truncate it.