Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect supplier #205

Closed
Con30 opened this issue Jan 30, 2024 · 3 comments · Fixed by #208
Closed

Incorrect supplier #205

Con30 opened this issue Jan 30, 2024 · 3 comments · Fixed by #208
Labels
bug Something isn't working

Comments

@Con30
Copy link

Con30 commented Jan 30, 2024

Digi-Key parts are failing to be created. The following message is seen when trying to create a new part:

[MAIN]  Creating supplier part←[0m 
[TREE]  Creating new supplier "DIGI" 
Exception in thread Thread-149 (create_part): 
Traceback (most recent call last):

The Supplier Name is unchanged from what is being received from the Digi-Key API and is "Digi-Key" not "DIGI". Additionally, when the Supplier Name is manually changed to something else the same message is seen saying it is trying tp create the supplier "DIGI". Clearing the cache and reinstalling kintree does not appear to resolve the issue.

Are there any other places it could be pulling this from?

Note: This doesn't occur when using Mouser as the part supplier/API.

@T0jan
Copy link
Collaborator

T0jan commented Jan 31, 2024

Does this happens for specific parts or for all of them? Do you already have a supplier Digi-Key in your inventree database?

@Con30
Copy link
Author

Con30 commented Jan 31, 2024

This appears to be for all parts. Yes, the supplier Digi-Key already exists in the database.

I'm wondering if it is searching the companies table and finding the Manufacturer DIGI and trying to use it as it is close to Digi-Key.

@eeintech eeintech added the bug Something isn't working label Feb 3, 2024
@eeintech
Copy link
Contributor

eeintech commented Feb 3, 2024

Yup I was able to reproduce with a "DIGI" manufacturer, good catch and sorry for the issue, fixing it now...

eeintech added a commit that referenced this issue Feb 3, 2024
@eeintech eeintech mentioned this issue Feb 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants