Handle Li.Fi final quote *failures*

[gomesalexandre]

Overview

This Li.Fi is to explicitly handle Li.Fi failures. Notice the emphasis on failures here, as opposed to "happy response, but final quote doesn't contain the previous quote from rate time".

We already handle the former following Li.Fi final quote work, Li.Fi final quote fix for bridges and Li.Fi final quote fix for unstable routes.

We should use the exact same logic as the latter in case Li.Fi fails on us at final quote time, which is v. possible if it's feeling cheeky at this particular moment (Li.Fi has its mood swings and may just fail because "why not, that's why") or if you as a user got limited between rate and quote.

References and additional details

Refer to Li.Fi final quote fix for unstable routes - exact same logic, except we want to catch HTTP failures instead of checking for !routes.length

Acceptance Criteria

• Li.Fi axios failures are captured and the same logic as fix: li.fi unstable quotes use original rate #8350 is used to handle these

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

[gomesalexandre]

Deterministically reproducible by:

• Ensuring you're not rate-limited already (fresh vpn server)
• Getting a rate
• Blocking request domain before getting quote
• Notice bork ensue

See Jam: https://jam.dev/c/f11bcd66-84db-4cae-a227-4a5debe8c782