Jan Mrázek
Jan Mrázek
A step-by-step guide with all the input data so the issue can be reproduced. To be honest, I don't even fully understand where the issue is. You showed a screenshot...
No further information was provided, closing. Feel free to reopen if you supply enough information to reproduce and trace the issue.
I am sorry, the steps for reproductions are incomplete - there are no files to run the commands on. There won't be any action taken until they are completed.
As there is no reproducer, closing.
No need to feel guilty about being pedantic. The board should be placed precisely, this is a bug in KiKit and I will look into it.
At the moment, this is the recommended way of using KiKit: https://github.com/yaqwsx/KiKit/discussions/701#discussioncomment-9801784 Until the new IPC API matures enough and we migrate KiKit to it, there is no other (easy)...
Please, attach the output when running with `--debug 'trace: true'`.
The KiCAD API is highly unstable until late in the development cycle. Trying to keep up with it is a waste of effort. We usually begin the adaptation of the...
You shared your frustration. You haven't, however, provided any steps for reproduction; hence, there is not much we can do. Currently, we have no similar reports, so having steps to...
We fetch a list of LCSC codes available on JLCPCB via their API. This happens every time. Then, we use the heavy rate-limited API of LCSC to fetch attributes of...