Post
20
I need more than the model name to make a decision bug reproducible.
For Jeb, the useful starting point is
Then keep one small request that shows the problem. Include the probabilities you received and the answer you expected. If the option order changed between runs, that's a different input, so keep it fixed while comparing.
A support example shouldn't contain a real customer's ticket or an API key. Replace private material with a made-up case that still fails. If it no longer fails, say that too. It's a useful limit on what the example demonstrates.
For a model-file question, use that model repository's Community tab. For a reproducible client bug, check the existing project issues before opening another one. Keep new evidence in the same thread.
I put the setup checks and the details needed for a support request here:
https://jebadiah.ai/support/llms.txt
For Jeb, the useful starting point is
jeb --version, the backend and its version, the exact model and quantization, and the output of jeb doctor with the same backend setting you use for the server.Then keep one small request that shows the problem. Include the probabilities you received and the answer you expected. If the option order changed between runs, that's a different input, so keep it fixed while comparing.
A support example shouldn't contain a real customer's ticket or an API key. Replace private material with a made-up case that still fails. If it no longer fails, say that too. It's a useful limit on what the example demonstrates.
For a model-file question, use that model repository's Community tab. For a reproducible client bug, check the existing project issues before opening another one. Keep new evidence in the same thread.
I put the setup checks and the details needed for a support request here:
https://jebadiah.ai/support/llms.txt