search

sparkmicro / Ki-nTree

Fast part creation for KiCad and InvenTree
GNU General Public License v3.0
178 stars 33 forks source link

1.1.0 #221

Closed eeintech closed 5 months ago

eeintech commented 6 months ago
eeintech commented 5 months ago

@T0jan Updating inventree to 0.13.x seems to brake the automated setup but I'm not sure why... given you're more up to date on Inventree than I am, would you know why?

EDIT: Might not actually be due to Inventree version... not sure what's happening it seems like it "randomly" fails

EDIT2: Python 3.11 is consistently failing, not sure if it is a false positive or not yet, will have to check.

T0jan commented 5 months ago

weird one, I have no problems connecting to different InvenTree servers with inventree-0.13.3 and Python3.11. The only instances where I can reproduce the error is by providing a wrong address/credentials or when the server is down.

So I think something goes wrong in the github-job, either while setting up the server or by it then providing an interface, even tho the log looks identical to 3.9 and 3.10 until it fails. Maybe there is a problem with 3.11 and the latest stable InvenTree commit?

T0jan commented 5 months ago

not sure how I made it worse xD

eeintech commented 5 months ago

not sure how I made it worse xD

The test Digi-Key token expired, it happens often. I refreshed it and restarted the CI, let's see

eeintech commented 5 months ago

@T0jan Now both Python 3.9 and 3.10 fail but 3.11 is fine 🤣 It is so confusing...

T0jan commented 5 months ago

rerun of 3.10 worked now and 3.9 again fails due to Digi-Key API, so I call github job problems here.

G-Pereira commented 5 months ago

Is it an issue of having too frequent digikey API requests?

eeintech commented 5 months ago

rerun of 3.10 worked now and 3.9 again fails due to Digi-Key API, so I call github job problems here.

Refreshed token, let's see but I am on your side thinking it is a false positive, maybe something changed on Github's side between different jobs which we are not aware of...

Is it an issue of having too frequent digikey API requests?

Shouldn't be for a normal user