-
Notifications
You must be signed in to change notification settings - Fork 26
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
Migrate findAccountsByPublicKey endpoint to QueryAPI #685
Merged
eduohe
merged 3 commits into
master
from
feature/migrate-findAccountsByPublicKey-to-queryapi
Apr 25, 2024
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,11 @@ | ||
const { Pool } = require('pg'); | ||
const Cache = require('node-cache'); | ||
const bunyan = require('bunyan'); | ||
const fetch = require('node-fetch'); | ||
|
||
const { | ||
BRIDGE_TOKEN_FACTORY_ACCOUNT_ID = 'factory.bridge.near', | ||
GRAPHQL_URL = 'https://near-queryapi.api.pagoda.co/v1/graphql', | ||
NEAR_WALLET_ENV, | ||
// INDEXER_DB_CONNECTION, | ||
INDEXER_DB_REPLICAS, | ||
|
@@ -119,15 +121,30 @@ const findAccountActivity = async (ctx) => { | |
const findAccountsByPublicKey = async (ctx) => { | ||
try { | ||
const { publicKey } = ctx.params; | ||
const { rows } = await pool.query(` | ||
SELECT DISTINCT account_id | ||
FROM access_keys | ||
JOIN accounts USING (account_id) | ||
WHERE public_key = $1 | ||
AND accounts.deleted_by_receipt_id IS NULL | ||
AND access_keys.deleted_by_receipt_id IS NULL | ||
`, [publicKey]); | ||
ctx.body = rows.map(({ account_id }) => account_id); | ||
|
||
const response = await fetch(GRAPHQL_URL, { | ||
method: 'POST', | ||
headers: { | ||
'content-type': 'application/json', | ||
'x-hasura-role': 'dataplatform_near' | ||
}, | ||
body: JSON.stringify({ | ||
query: ` | ||
query access_keys_v1_by_public_key { | ||
dataplatform_near_access_keys_v1_access_keys_v1( | ||
where: {public_key: {_eq: \"${publicKey}\"}} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Doesn't look like the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. thanks, removed |
||
) { | ||
account_id | ||
} | ||
} | ||
`, | ||
operationName: 'access_keys_v1_by_public_key' | ||
}), | ||
}); | ||
|
||
const respJson = await response.json(); | ||
const rows = respJson.data.dataplatform_near_access_keys_v1_access_keys_v1; | ||
ctx.body = rows.map(item => item.account_id); | ||
} catch (e) { | ||
if (ctx.log && typeof ctx.log.error === 'function') { | ||
ctx.log.error(e); | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this handle
testnet
queries as well?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah that's a good point, it does not. We may need to parameterise this in ECS, and use ExplorerDB in testnet, QueryAPI doesn't support testnet yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the heads up, I changed to have a fallback for non-mainnet environments or if no results from graphql
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you actually want a fallback for mainnet queries that return no results from graphql? If the DBs are actually going to be unavailable after April 30th then I imagine you'd want to know sooner than later that there's a disparity in what QueryAPI is returning. Also saves you the effort of needing to come back in < 2 weeks to remove the fallback 🙂
Are the testnet indexer DBs also going to be unavailable after April 30th? It's sounding like there will be an indeterminate gap in coverage for testnet. I don't know how severe the real impact of this would be, it's probably safe to assume there isn't a lot of account recovery, staking, etc. coming from testnet environments. It would almost certainly break parity for wallets supporting testnet but it might not be a dealbreaker in the short term.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good questions, yes we want to keep the fallback, April 30th is the desired deadline, but there are other endpoints that needs to be migrated before we turn off the DB instance.
Testnet indexer DBs will stay, there is no deadline or workstream yet to deprecate them.