sec_parser doesnt work for other Major Tickers

[nnilayy]

Hey, I planned on starting the work on sec-ai and for doing so I wanted to see how data flow will be from parser to llm, Assuming that the parsers output will be used for llm. So whilst doing so, i was testing the parser for different tickers, but i got a few errors. As laid out in Github example, The AAPL Ticker works, but for other tickers like AMZN, AMD, MSFT the parser does not work, all of which were random examples i used. For AMZN and AMD tickers, I got a list index out of range error and for MSFT, the html was parsed but there was not output.

I wanted to make sure that tickers were not the issue, so i checked with random invalid tickers and the code did raise the error for being an invalid tickers.

Wanted to know, if this is a known error and was gonna be worked on in the future or its an unusual output/bug.

[Elijas]

Hey, I planned on starting the work on sec-ai and for doing so I wanted to see how data flow will be from parser to llm, Assuming that the parsers output will be used for llm. So whilst doing so, i was testing the parser for different tickers, but i got a few errors. As laid out in Github example, The AAPL Ticker works, but for other tickers like AMZN, AMD, MSFT the parser does not work, all of which were random examples i used. For AMZN and AMD tickers, I got a list index out of range error and for MSFT, the html was parsed but there was not output.

I wanted to make sure that tickers were not the issue, so i checked with random invalid tickers and the code did raise the error for being an invalid tickers.

Wanted to know, if this is a known error and was gonna be worked on in the future or its an unusual output/bug.

Hey, thanks for the report! The system is currently undergoing a big refactor, and we have a limited selection currently in our end-to-end tests, We will definitely support these tickers and even consider adding then to our automated CI/CD tests so that any kinds of regressive bugs are caught early and prevented.

Expect a fix over the next few days! Thank you for your patience

[Elijas]

Thank you for bringing this to our attention, nnilayy!

Upon further investigation, I've concluded that the issue you encountered is related to documentation and performance rather than being a bug.

1. Updated Readme Example Code (✅ Fixed)

The example code in the Readme and User Guide was initially tailored for the "Apple" ticker. This meant that when you tried to run the example with other company tickers, you received an "index out of range" error. To address this, we've revised the Readme to include a more general example that should be compatible with any ticker symbol.

2. Improved Computational Efficiency (✅ Fixed)

In the case of Microsoft's ticker (MSFT), there was actually an inefficient loop in the code. This has been identified and rectified using our newly added Performance Profiler.

These changes should improve your experience with sec-parser. If you encounter any further issues, please don't hesitate to let us know.

Best regards,
Elijas