1.1.0

[eeintech]

• prevent crashes caused by leading spaces and parts without parameters #219
• Fixes KeyError 'parameters' when updating a component in/to inventree #217
• Should fix Coverage is not following new releases #202
• Update flet package to latest version Upgrade flet version to latest #224
• Incorporated Search UI enhancments #223 here directly as new flet version broke it
• Update README and add note in the docs about InvenTree server field assumes https unless http specified #225

[eeintech]

@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]

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]

not sure how I made it worse xD

[eeintech]

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]

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

[T0jan]

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]

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

[eeintech]

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