Saoud Rizwan
Saoud Rizwan
That's an unrecognized/invalid Unicode character showing up as a replacement character (�). Usually happens with encoding mismatches or when there's an invalid byte sequence in the text. Note to contributors:...
v2.0 brings better deepseek compatibility! Please give it a try and let me know how it goes!
I believe this was caused by a bug with files using "@/" import aliases–I just released v3.1.5 that should fix this, please feel free to re-open if you're still seeing...
Hi @akshaybabloo sorry for this issue getting stale, do you mind creating a feature request on our discussions board so that we can get around to it at some point?...
I hope your experience with v3 is better with the new diff editing.
Closing as duplicate https://github.com/clinebot/cline/issues/340, will need to look into how provide wider compatibility with these APIs.
Should be fixed in v3 now that Cline does targeted diff editing instead of rewriting the entire file's contents. Please let me know how it works for you!
^ Agree related to #962. It's out of the extension's scope to implement an automatic retry mechanism and recommend using a more reliable API.
This issue was fixed in 2.1.5, thank you for reporting!
Hey @edwrdcrpio! I've seen this happen with some other users as well. I think it's because at some point a non-utf8 character was read into context causing the JSON write...