-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
ERROR #134
Comments
@MarianoAntezana @yashar1908 @virattt Hi Mariano, thanks for flagging this—sorry to hear it’s not working despite your API keys being set! I dug into the output you shared, and it looks like the tool’s hitting an error in parse_hedge_fund_response() (likely from issue #141), defaulting to "HOLD" with 0 quantity and confidence. Since Poetry’s installed and keys are in place, the issue might be an invalid API response or a network glitch—tricky to pin down with the current setup. I tested Yashar’s fix with various cases (bad JSON, None, empty strings), and it’s solid—no bugs there. It catches errors and returns None, which triggers the "HOLD" fallback in the portfolio logic. The problem seems to be upstream—maybe the API’s sending junk—or we need better debugging. Current print() logs aren’t cutting it for tracking this down. I’d like to contribute a tweak to help: switching to logging with file output, adding a response validity check, and passing error context to the portfolio output. Here’s my proposal: logger = logging.getLogger(name) def parse_hedge_fund_response(response):
def update_portfolio(data):
Logs go to portfolio_debug.log—Mariano, check that file after running to see the error. |
Seems that the code is not working, I have put everysingle API key for not having errors, but its not working. Also im sure i Have installed poetry well, but is there any way to debug it?
thank you!
The text was updated successfully, but these errors were encountered: