dry-orange-3870
07/27/2023, 5:49 PMstderr:
There was 1 error downloading required artifacts:
1. mlprodict 0.9.1883 from <https://files.pythonhosted.org/packages/5b/d2/7f643bb8432e9c7961becb4f44e0e0f8455dffa92344c6e4ca7b4d18d232/mlprodict-0.9.1883.tar.gz>
hint: See above for details.
This works fine for some folks on my team, but is failing for others. I re-ran the command with --keep-sandbox=on_failure
and modified the __run.sh
script with --preserve-pip-download-log
(as mentioned here) and ran the __run.sh
script. But that doesn't output any additional information and I can't find the logs. (The .tmp
folder appears, but disappears as soon as the command exits.) How do I get the full error message?fast-nail-55400
07/27/2023, 6:37 PM--keep-sandboxes=always
so it s guaranteed to not be deleted?fast-nail-55400
07/27/2023, 6:38 PM--keep-sandboxes
and not --keep-sandbox
dry-orange-3870
07/27/2023, 6:51 PM__run.sh
script lives. It's the output logs from running __run.sh
from inside of the sandbox directory that are not available to mefast-nail-55400
07/27/2023, 6:54 PMpip
invocation, maybe add --log <path>
to set a specific file to write to?fast-nail-55400
07/27/2023, 6:54 PMpip --help
)dry-orange-3870
07/27/2023, 7:07 PM__run.sh
isn't calling pip
. It's asking python
to invoke ./pex
fast-nail-55400
07/27/2023, 7:12 PMpex
config options to configure logging. Is PEX_VERBOSE=9
set?fast-nail-55400
07/27/2023, 7:13 PMdry-orange-3870
07/27/2023, 7:20 PM-v 9
to get verbose output. Using -v 9
gave me more lines as output, but changed the behavior in some other way and lead to a different error.
PEX_VERBOSE=9
is goodfast-nail-55400
07/27/2023, 7:29 PM-v 9
and PEX_VERBOSE=9
should technically be the sameenough-analyst-54434
07/27/2023, 7:31 PM-vvvvvvvvv
enough-analyst-54434
07/27/2023, 7:40 PMenough-analyst-54434
07/27/2023, 7:57 PMsetup_requires
mechanism is old, deprecated / removed and buggy. It flat out will not work with Pex. You can fork the repo and add a pyproject.toml
to use setup.py still, but leverage PEP-518 to get those build requirements properly pre-installed. Then send the repo a PR once you have that working through a VCS requirement. Lots to chew on there, and from my phone, but this style of topic should yield slack search hits.dry-orange-3870
07/27/2023, 8:28 PMsetup.py
is unfamiliar territory to me, so it wasn't obvious why building from sources was failing. Thanks for the explanation!dry-orange-3870
07/27/2023, 8:29 PMenough-analyst-54434
07/27/2023, 11:29 PM