bug: Arch Detector Causing Special Characters in GPU Name in `settings.json` about jan

[louis-jan]

Root cause:
The extension detects only GPU models that start with 30 or 40. Which is incorrect, should cover other cases (E.g. Axx)

[cbai970]

im subbing to this, when you get a solution, Ill retest on that same platform.

[cbai970]

Im happy to help move this forward but I dont know the full .js tree and how it gets created to the point where we hit this bug. Ive been been reading through as much Tensorflow and Tensorflow-LLM documentation as I can but not entirely sure.

If i could have someone tell me how we end up getting to "index.js" in the spawning of the tree, Ill do my best to post what I find (if it helps) , I am under the assumption that this function ends up calling a "compile from source against Arch(itecture)" thread, but maybe Im wrong.

give me a little friends, and Ill give you a lot :) p.s. I am a former defect research engineer...

[louis-jan]

Is a possible fix coming from cortex-cpp? cc @imtuyethan @Van-QA

[cbai970]

Root cause: The extension detects only GPU models that start with 30 or 40. Which is incorrect, should cover other cases (E.g. Axx)

I would go with CUDA compute levels, unless there are additional architectural reasons not to, but I could not find any.

I was actually trying to figure out how to code myself, but (again) im not a programmer kind of afraid of breaking stuff, Also... this is all gets autogenerated when Jan first executes (and regens when you reset, because i definitely tested that) so Im not sure what root this all comes out from.