GraphQL endpoints should be forwardable to proxy nodes #239
Labels
No Label
bug
critical
documentation
duplicate
enhancement
Epic
good first issue
help wanted
Integration tests
invalid
question
v5
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/ipld-eth-server#239
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Right now the GraphQL backend calls directly into the "eth" backend, skipping over the "eth" API abstraction where the forwardOnError and forwardEthCall/forwardStorageAt functionality is enabled.
How is this possible? How are the watchers actually working then? Seems like this an issue with ETH watcher not existing and maybe this feature should just be moved over there? @dboreham
It would mean that the requests are being processed successfully in ipld-eth-server, so no forward-on-error is needed.
In general forward on error is a bit of an antipattern. The ability to forward a particular configured workload is useful, but forwarding when something fails is problematic for a number of reasons, outside of dev testing scenarios.