Feature request
I searched for 2010 KV8 over a 7 month period with 1 hr time steps. It crashed, likely because of too many ephemeris points, but the error message in the GUI is not informative:
Application Output:
2026-06-01 15:34:34,404 [WARNING] root: Note: The image and photometry service may take a while.
This terminal widget will not refresh in real-time until each full step completes.
Please be patient after initiating a run.
2026-06-01 15:37:05,310 [INFO] root: Running Ephemeris service.
2026-06-01 15:37:05,315 [INFO] ephemeris_client: Querying horizons for target: 2010 KV8
2026-06-01 15:37:22,417 [INFO] horizons_interface: Query for range 2025-01-01 15:34:34.000 to 2025-07-31 15:34:34.000 successful for target 2010 KV8. Time taken: 17.08 seconds.
2026-06-01 15:37:55,299 [INFO] stdout: ----------------------------------------
2026-06-01 15:37:55,304 [INFO] stdout: The image search is now initiated.
2026-06-01 15:37:55,306 [INFO] stdout: ----------------------------------------
2026-06-01 15:37:55,309 [INFO] odc: Using point-based image search method
2026-06-01 15:37:55,313 [INFO] stdout: Begin the image search based on ephemeris data.
2026-06-01 15:45:38,389 [INFO] image_service: Job phase is ERROR
2026-06-01 15:45:38,479 [ERROR] image_service: Error executing query: Query Error: StackOverflowError:null
2026-06-01 15:45:38,482 [WARNING] image_service: No results found
2026-06-01 15:45:38,493 [INFO] stdout: ----------------------------------------
2026-06-01 15:45:38,496 [INFO] stdout: The image search has been completed.
2026-06-01 15:45:38,499 [INFO] stdout: The process took 7.72 minutes.
2026-06-01 15:45:38,501 [INFO] stdout: ----------------------------------------
Can a better error message be provided in this case? Or at least some guidance to the user on what to do next?
Before submitting
Please check the following:
Feature request
I searched for 2010 KV8 over a 7 month period with 1 hr time steps. It crashed, likely because of too many ephemeris points, but the error message in the GUI is not informative:
Can a better error message be provided in this case? Or at least some guidance to the user on what to do next?
Before submitting
Please check the following: