wwjCMP

Results 202 comments of wwjCMP

Me too. I hope that under rendering conditions, we can manually expand the context just like under non-rendering conditions.

> @sekrett the following might help shed some light... > > ``` > ls /sys/devices/system/cpu/ > cat /sys/devices/system/cpu/cpu*/topology/thread_siblings > ``` > > For reference, on a 4-core (8 hyperthread) Intel...

``` cpu0 cpu14 cpu2 cpu25 cpu30 cpu36 cpu41 cpu47 cpu52 cpu58 cpu63 cpu69 cpu74 cpu8 cpu85 cpu90 cpufreq kernel_max power cpu1 cpu15 cpu20 cpu26 cpu31 cpu37 cpu42 cpu48 cpu53 cpu59...

``` 00000000,00000000,00000001 00000000,00000000,00000400 00000000,00000000,00000800 00000000,00000000,00001000 00000000,00000000,00002000 00000000,00000000,00004000 00000000,00000000,00008000 00000000,00000000,00010000 00000000,00000000,00020000 00000000,00000000,00040000 00000000,00000000,00080000 00000000,00000000,00000002 00000000,00000000,00100000 00000000,00000000,00200000 00000000,00000000,00400000 00000000,00000000,00800000 00000000,00000000,01000000 00000000,00000000,02000000 00000000,00000000,04000000 00000000,00000000,08000000 00000000,00000000,10000000 00000000,00000000,20000000 00000000,00000000,00000004 00000000,00000000,40000000 00000000,00000000,80000000 00000000,00000001,00000000 00000000,00000002,00000000 00000000,00000004,00000000 00000000,00000008,00000000...

> @wwjCMP if your CPU does not have hyperthreads, then the "thread_siblings" above are supposed to show no siblings, and we should default to one thread per core. If that's...

![Snipaste_2024-04-15_12-24-33](https://github.com/sugarforever/chat-ollama/assets/32979859/69b82fd1-4343-4df8-9ffb-a80da41b0658)

I believe this improvement is valuable.

> Hi, > > 请修改 `CUSTOM_API_KEY_PATTERN = r"^[A-Za-z0-9-_=]+\.[A-Za-z0-9-_=]+\.[A-Za-z0-9-_.+/=]*$"` > > 以适配 JWT 类型的 API_KEY 谢谢你的回答,但还是一样的问题