Problem with ? in responses from some models

[NorbertKlockiewicz]

Sometimes, some models, especially qwen3 returns mysterious "?" character. It looks like the character is intended to be an emote. Investigate the issue to find out from where the problem originates and fix it.

[DarkSorrow]

Hello,

Im experiencing this as well and on the last version im using (0.4.6) each time that a qwen 3 model end up with a �. the model stop giving answers to my subsequent calls (on android only). I'm using the module version with only the generate function.

The problem seems to be that some emote (and maybe other characters) are given on multiple token and just assembling them in the response (now token callback) fails. I tried some other libraries and they also have problems with the emotes when i receive the token as a string and i put them together manually
However when i get the full response at then end the emotes are present. But with this library even in the full response from the generate function the emote doesn't appear. This is just a guess but maybe the token should be assemble from the raw bytes? Im not very familiar with that part yet as the other library i used does it internally but the conversion to string might create some character loss because its not encoded properly?

[pweglik]

This is merged now and will be released in 0.5.0! We're discussing possibility of releasing it as a quick path to 0.4.x as well, but it is a bit problematic

[DarkSorrow]

Better focus on the 0.5.0 if its going to make you lose a bit of time to port to 4.x
I think the problem with android can be a bit annoying but since it's only with some models that heavily does emoji it's not really a big deal and it can wait a little bit. Most functionalities to build around the LLM is working so i personally don't think you should spend extra work on current version if it's going to delay new one :o

[msluszniak]

Consider adding this one to a milestone v0.5.0

[pweglik]

With release of v0.5.0 I'm closing it :D If problem reoccurs, feel free to open another issue @DarkSorrow