Besancon query: output text issues
- Dominant language
- Python
- Stars
- 791
- Forks
- 451
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 4
Description
(First time commenter so I apologise if the format of this isn't quite right).
I've been using astroquery.besancon for a while now as part of my research, and I'm having some slight issues with the output. If relevant, I'm working in Jupyter Notebook.
When a query successfully runs, for example this incredibly simple query here:

You get output text in the form of: "Awaiting Besancon file...
Waiting 30.0s for model to finish (elapsed wait time 0.0s, total wait time 0.5)"
Which then leads on to give you the url of your model when it is complete.
No issues there.
However, when running the model is unsuccessful (for reasons both known and unknown), I've found that the output simply gives:
"Awaiting Besancon file..."
and nothing extra.
Sometimes, I've found and corrected an issue with my code, as it has been due to the format of my inputs being incorrect. However, I'm currently stuck because a code I ran successfully a few days ago (multiple times, to retrieve about ~30 simulations) now only gives me the "awaiting" message and nothing more. I did not modify the original code between runs.
So, my question boils down to: what _exactly_ does an output of only "Awaiting Besancon file..." mean? Is it purely because there is an error in the code somewhere and the model cannot successfully run? Or is there more to it than that? Additionally, is it currently possible to display a more comprehensive output (debugging? error message?) text, that possibly highlights what issue the query is running into that causes it to not work?
Thank you for your time, I hope this post has made sense. If more examples of the code I'm using is needed, please let me know.
Contributor guide
Research direction
Start at the astroquery.besancon query entry point and reproduce both successful and failing requests, including the Jupyter Notebook context. Trace how the wait and error responses are handled; done should mean a useful failure reason is shown instead of only "Awaiting Besancon file...". No file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100