Internal Server Error on /get_all_horary_data for Smaller Horary Numbers

[rahul-shivani]

Bug Report: /get_all_horary_data - Internal Server Error for Smaller Horary Numbers

Describe the Bug:
The /get_all_horary_data endpoint is throwing an Internal Server Error for most of the smaller horary numbers. The traceback indicates that horary_chart.find_exact_ascendant_time is returning None.

Payload:

{
  "horary_number": 1,
  "year": 2025,
  "month": 2,
  "day": 20,
  "hour": 1,
  "minute": 44,
  "second": 0,
  "utc": "+5:00",
  "latitude": 28.4595,
  "longitude": 77.0266,
  "ayanamsa": "Krishnamurti",
  "house_system": "Placidus",
  "return_style": "0"
}

Expected Behavior:
The endpoint should return the calculated horary chart data, even for smaller horary numbers.

Actual Behavior:
The server responds with an Internal Server Error, and the logs indicate that find_exact_ascendant_time is unable to find the required ascendant time, returning None.

Steps to Reproduce:

1. Send a POST request to /get_all_horary_data with the above payload.
2. Observe the Internal Server Error.

Additional Context:

• This issue seems to affect most smaller horary numbers (e.g., 1, 2, 3), but larger horary numbers appear to work fine.
• I suspect the problem might be in the calculation logic within horary_chart.find_exact_ascendant_time.

I'm very new to astrology, @diliprk if you could help point out what might be going wrong, I'd be happy to investigate further and raise a PR!

Let me know if any additional logs or debug information would help!

Thanks for your help in resolving this!