Will you one day proofread you system prompts?
It's been YEARS your system prompt are flawed in the first place...
You have the ability to read images, but you cannot generate images. You also cannot transcribe audio files or videos.
You cannot read nor transcribe audio files or videos.
Sorry for the arsh tone but I don't even understand how this could happen when even a 3B model would be able to notice such a redundancy...
When you want to commit changes, you will always use the 'git commit' bash command. It will always\n
be suffixed with a line telling it was generated by Mistral Vibe with the appropriate co-authoring information.
Why the heck is there a new line here...
Great tone here, pleasure reading the comment
Feel free to open a PR, you can bookmark that as an open-source contribution then
I'm again sorry for the tone, but I mean... It's been years! And I'm pretty sure I made a PR long time ago on a Magistral model, but maybe it was in Unsloth repo I don't remember, I give you the benefit of the doubt here...
But it's a system prompt, it's not like... a typo in your readme or whatever...
I'm worried (and I believe that's fairly participating to my violent reaction), that you actually post trained the model with this prompt, wasting a fair amount of GPU compute...
And again, sorry for the spiteful reaction in the first place. And I can finish like this:
I always liked your models and always keep at least one in my library wether it was Mistral-small or Devstral at some point. I also used and absolutely been amazed by your Voxtral model. So I guess this is another factor that made me furious thinking your PT models are good and deserve better care...
So this still isn't fixed ☹️
I changed a bit the Vibe one to remove \n and a typo. Regarding the chat one I also removed the redundancy.
These system prompts are here as an example of usage but are free to update. We didn't train the model on those and it should be perfectly fine that they are changed.
Sad we had to use such a raw, shock-type approach to bring attention, but glad it finally brought a clear answer. I'm reassured and will personally go with it.
Thanks,
Et vive Mistral !
@danielhanchen time to launch the workflow again I guess!
BTW @owao , the most efficient way to get a clear answer and a fix is def not a "shock-type" approach. The more we see "shock-type", the less we will respond. The better approach would have just been to open a PR directly to fix the SP example.
I did almost 6 months ago...
https://huggingface.co/mistralai/Mistral-Small-3.2-24B-Instruct-2506/discussions/22
https://huggingface.co/mistralai/Magistral-Small-2507/discussions/8
https://huggingface.co/mistralai/Magistral-Small-2507/discussions/9
https://huggingface.co/mistralai/Magistral-Small-2507/discussions/7
Oh no wait, this one was even from 8 months ago
https://huggingface.co/mistralai/Mistral-Small-3.1-24B-Instruct-2503/discussions/59