Skip to content

Latest commit

 

History

History
34 lines (25 loc) · 1.41 KB

SUPPORT.md

File metadata and controls

34 lines (25 loc) · 1.41 KB

Support

Thanks for using Simantic. Here is the fastest way to get an answer.

Documentation first

  • Docs — simantic.dev/docs
  • Python SDK — the pippy README covers install, authentication, engines, and the pytest plugin.
  • Is it configured? — simantic status prints what resolved on your machine (binary, account, engine). Include its output when you ask for help.

Asking a question

  • A bug, or something that looks wrong — open an issue on the repository it affects. Include the version, your OS, and the smallest firmware or script that reproduces it.
  • A feature request — open an issue describing what you are trying to do, not only the API you have in mind. Knowing the goal often changes the answer.
  • An unsupported MCU or peripheral — open an issue naming the part. This is useful to us even when we cannot get to it soon; it is how we prioritise.
  • Anything account, billing, or access related — email [email protected]. Do not put account details in a public issue.

Security

Do not use issues for security reports. Follow the security policy instead.

Response times

We are a small team and read everything, but we are not staffing a 24/7 support rotation. Public issues are usually the fastest route, because other people can help and the answer stays searchable.