Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Is it possible to skip or add a nice message to the user when trying to access services like Kitspace?

See original GitHub issue

Using v1.1.5

# Getting part data from KitSpace...
Starting new HTTPS connection (1): dev-partinfo.kitspace.org:443                                                                              
https://dev-partinfo.kitspace.org:443 "POST /graphql HTTP/1.1" 504 192                                                                        
Progress:   0%|                                                                                                      | 0/52 [01:01<?, ?part/s]Traceback (most recent call last):
  File "/usr/local/bin/kicost", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.8/dist-packages/kicost/__main__.py", line 306, in main
    kicost(in_file=args.input, eda_name=args.eda,
  File "/usr/local/lib/python3.8/dist-packages/kicost/kicost.py", line 251, in kicost
    api_partinfo_kitspace.query_part_info(parts, distributor_dict, currency)
  File "/usr/local/lib/python3.8/dist-packages/kicost/distributors/api_partinfo_kitspace.py", line 366, in query_part_info
    get_part_info(queries[slc], query_parts[slc], query_part_stock_code[slc])
  File "/usr/local/lib/python3.8/dist-packages/kicost/distributors/api_partinfo_kitspace.py", line 208, in get_part_info
    results = api_partinfo_kitspace.query(query, distributors)
  File "/usr/local/lib/python3.8/dist-packages/kicost/distributors/api_partinfo_kitspace.py", line 146, in query
    raise Exception('One of the internal Kitspace services may experiencing problems. Contact the Kitspace support.')
Exception: One of the internal Kitspace services may experiencing problems. Contact the Kitspace support.
Progress:   0%|                                                                                                      | 0/52 [01:01<?, ?part/s]

Issue Analytics

State:
Created 3 years ago
Comments:16 (6 by maintainers)

Top GitHub Comments

2reactions

hildogjrcommented, Jun 10, 2020

Yes, we need some code revision for warning and error messages. I did some in past but stil missing a lot.

KiCost emerged a cost tool the --no_price was a feature add after so users that just want the part list of the BOM.

2reactions

mdeweerdcommented, Jun 10, 2020

I always run with --debug 10 to get some hint at which part is failing.

The number of requests to Kitspace is shared amongst the users. Therefor, I also recommend using --no_price while you are cleaning up your BOM and check prices only later when you are confident that you part numbers and variants are correctly set up.