-
Notifications
You must be signed in to change notification settings - Fork 15
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
Having an issue with searching for Sydney flights (SYD) #24
Comments
Hey @chansters! 👋 I'm here to help you with any bugs, questions, or contributions. I'll do my best to assist you while you wait for a human maintainer. The "No flights found" To resolve this issue, consider the following steps:
These steps should help in addressing the issue you're encountering [1]. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Have you tried the fallback? Here's the docs. |
I'm currently calling your API like this, which I believe is using the fallback method? I've blanked out the dates for privacy reasons as I'm doing this for personal trip planning. The first three routes work just fine but it's failing on the fourth. I've tried just querying using the last route alone (without the first three) and it still fails.
Just read your docs link, I will try the force method: force-fallback – Forces using the fallback. |
Did the |
Thanks for this great work! It's working really well. However, I'm running into an issue when I try to search for Sydney (SYD) flights:
File "/opt/miniconda3/lib/python3.12/site-packages/fast_flights/core.py", line 47, in get_flights_from_filter
return parse_response(res)
^^^^^^^^^^^^^^^^^^^
File "/opt/miniconda3/lib/python3.12/site-packages/fast_flights/core.py", line 151, in parse_response
raise RuntimeError("No flights found:\n{}".format(r.text_markdown))
I'm trying to search for SYD to SFO flights. It works on the Google Flights website but keeps throwing this error. Any ideas?
The text was updated successfully, but these errors were encountered: