Closed ProExpertProg closed 1 year ago
I think this was fixed in 546d85f89734e404dc19298292fe2c144b68b926, I'm not sure whether this is part of the current PyPI release. Is OPENAI_API_KEY
defined?
@emeryberger Maybe we should issue a new release?
Yeah, if I run env:
$ env
SHELL=/bin/bash
NVM_INC=/home/luka/.nvm/versions/node/v16.13.2/include/node
WSL2_GUI_APPS_ENABLED=1
WSL_DISTRO_NAME=Ubuntu-20.04
OPENAI_API_KEY=sk-...
I am able to reproduce this downloading cwhy
from PyPI and manually lowering the timeout to force a timeout error.
I am assuming it hangs for a bit (30 seconds) before failing from the httpx.ReadTimeout
? I have also increased the timeout in 22ce96191b405b4e2467e47f8a7d0f0aaa22fed7. We maybe should make it a CLI option. Could you by any chance try with the current main
instead of the PyPI version and see if this still happens?
[~] git clone https://github.com/plasma-umass/cwhy.git
[cwhy] pip install .
Yeah, with a simple message, it does not fail, it's the longer error message that likely takes longer to process and timeout. I'll try with the longer timeout
Just made the timeout a CLI option in 89fca5c48ea884b4612841b558c0a5d4477c621d and improved the error message in case of timeout in c3a27b6c08a30d7fec310f1d9e28d5f5920ac069.
Thanks for the quick turnaround!
(and for what it's worth, it correctly hypothesized that there is an issue with the standard library installation - I was using something from std::ranges
that hasn't been implemented in the compiler version I'm using. I am quite impressed!)
Thanks - that's great to hear!
Getting this sequence of errors when running
cwhy
, and I was curious if you've experienced that: