Skip to content

401 "no token provided" from try.playwright.tech on v2.2 (latest PyPI) — selectively fails on some routes #109

@gsingal

Description

@gsingal

v2.2 (currently the latest PyPI release) hits a 401 from the upstream try.playwright.tech endpoint, identical to the closed #53. The owner comment on #53 says "no longer a problem since v3.0rc1, i hope :)", but v3.0rc1 is not published on PyPIpip install fast-flights still resolves to 2.2 (last release 2025-03-08).

Two interesting wrinkles that suggest this isn't a hard global outage:

  1. Selective by route. In one production run (2026-05-21 ~23:06 UTC) two queries fired seconds apart from the same process:
    • `BOS->LAS 2026-05-28 economy 1 adult` → 401
    • `LAS->BOS 2026-05-31 business 1 adult` → success (returned a real fare)
  2. Both calls used the same library version (2.2), same machine, same Python (3.13), so it's not env-level.

Error:
```
AssertionError('401 Result: {"error":"no token provided"}\n')
```

Repro:
```python
from fast_flights import FlightData, Passengers, get_flights
result = get_flights(
flight_data=[FlightData(date="2026-05-28", from_airport="BOS", to_airport="LAS")],
trip="one-way", seat="economy",
passengers=Passengers(adults=1),
)
```

Asks:

  • Could v3.0rc1 (or a v2.3 cherry-pick of the fix) be published to PyPI? Many downstream pipelines pin to PyPI releases and have no path to use the rc1 fix otherwise.
  • Is there a known pattern for which routes the 401 hits — economy vs premium, certain regions, certain date windows? Knowing it would help us gate calls client-side instead of catching exceptions.

For now we've added a kill switch in our daemon to disable the flight adapter when this fires, but obviously we'd rather have working re-shop queries.

Happy to provide more logs / test other date+route combos if it helps.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions