Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Introduce GraphQLTokenFeeFetcher (no traffic) #736

Merged
merged 11 commits into from
Jun 17, 2024

Conversation

xrsv
Copy link
Contributor

@xrsv xrsv commented Jun 13, 2024

Introducing a GraphQLTokenFeeFetcher (implementation + tests only for now, no live traffic)
This fetcher will use GraphQL endpoint to fetch token fee data, and will fallback to OnChain fetching if something goes wrong or to fetch any remaining tokens that couldn't be fetched from graphQL.

Did setup env variables UNI_GRAPHQL_ENDPOINT / UNI_GRAPHQL_HEADER_ORIGIN for GraphQL in routing-api

A separate PR will follow for shadow traffic,

Testing

  • added unit/integration tests
  • ran e2e tests with 100% GraphQL traffic

@xrsv xrsv requested review from a team, jsy1218 and mikeki June 13, 2024 16:20
Copy link
Contributor

@mikeki mikeki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's looking good overall, some minor comments :)

@jsy1218
Copy link
Member

jsy1218 commented Jun 13, 2024

Pasting my comments from old PR. I think we want to shadow sample GQL traffic first, with FOT fee comparison. We aren't in rush to switch 10% (or whatever) traffic to GQL

@xrsv
Copy link
Contributor Author

xrsv commented Jun 13, 2024

Pasting my comments from old PR. I think we want to shadow sample GQL traffic first, with FOT fee comparison. We aren't in rush to switch 10% (or whatever) traffic to GQL

makes sense - I'll remove the traffic switch part from this PR and will add that logic to a different PR

@xrsv xrsv changed the title feat: Introduce GraphQLTokenFeeFetcher at 10% traffic feat: Introduce GraphQLTokenFeeFetcher (no traffic) Jun 13, 2024
@graphite-app graphite-app bot requested review from a team, uni-guillaume, mikeki and cgkol and removed request for a team and uni-guillaume June 13, 2024 19:48
Copy link

graphite-app bot commented Jun 13, 2024

Graphite Automations

"Request reviewers once CI passes on routing-api repo" took an action on this PR • (06/13/24)

5 reviewers were added and 1 assignee was added to this PR based on 's automation.

Copy link
Contributor

@mikeki mikeki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM

@jsy1218 jsy1218 merged commit 4bbc535 into main Jun 17, 2024
5 checks passed
@jsy1218 jsy1218 deleted the xrsv/introduce-graphql-token-fee-fetcher-10-percent branch June 17, 2024 16:32
Copy link
Member

jsy1218 commented Jun 17, 2024

Merge activity

xrsv added a commit that referenced this pull request Jun 17, 2024
xrsv added a commit that referenced this pull request Jun 17, 2024
Revert "feat: Introduce `GraphQLTokenFeeFetcher` (no traffic) (#736)"

This reverts commit 4bbc535.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants