GraphQL endpoints should be forwardable to proxy nodes #239

Open
opened 2023-05-30 14:28:41 +00:00 by i-norden · 2 comments
Member

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.

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.
Owner

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

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
Owner

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.

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.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/ipld-eth-server#239
No description provided.