Show descriptive error when Fanout is not enabled
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Start at the handoff_fanout and createFanoutHandoff entry points, then compare their handling with the Go SDK reference implementation in PR 275. Handle the platform's Unsupported status and verify that calls on services without Fanout or WebSockets produce the descriptive support message instead of a generic error.
Written by the indexing model from the issue text.
Description
Summary
When handoff_fanout / createFanoutHandoff is called on a service that does not have Fanout enabled, the platform now returns a specific status code indicating the feature is not available. The SDK should catch this and surface a clear, actionable error message to the developer rather than a generic/opaque failure.
Expected behavior
When a developer calls the fanout handoff on a service without Fanout enabled, they should receive an error with a message like:
"Fanout or WebSockets are not enabled on this service; please contact support for help"
Current behavior
The SDK returns a generic error (or empty error) with no indication of what went wrong or how to fix it.
Reference implementations
Go SDK: https://github.com/fastly/compute-sdk-go/pull/275
Checks for the Unsupported status from the redirect_to_grip_proxy / redirect_to_websocket_proxy hostcalls and return a specific error variant with the descriptive message.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fastly/compute-sdk-python
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fastly/compute-sdk-python#98 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
fastly/compute-sdk-python#74 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
fastly/compute-sdk-python#61 ·
-
fastly/compute-sdk-python#60 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
fastly/compute-sdk-python#59 ·
All issues in fastly/compute-sdk-python
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·