graphprotocol / graphprotocol/indexer
Discrepancy in UX of setting `indexer-agent` geocoordinates when multimode is `false` vs `true`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
Indexer is reporting discrepancy in UX of setting indexer-agent geocoordinates when multimode is false vs true.
and I found a cool workaround for an issue on my side:
multimode=false agent didn't require a comma between the geo coordinate numbers and it was building the array by itself
multimode=true agent requires you to build the array yourself, ie: [69.69, 69.69]
the workaround - a nice little bash magic:
grep -q 'INDEXER_AGENT_MULTINETWORK_MODE=true' .env && awk '/geoCoordinates: \[\$\{GEO_COORDINATES:-[0-9.]* [0-9.]*\}\]/ {gsub(/([0-9.]+) ([0-9.]+)/, "\\1, \\2")} 1' indexer-agent-configs/mainnet.yaml > tmp.yaml && mv tmp.yaml indexer-agent-configs/mainnet.yaml
-Payne
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with indexer-agent-configs/mainnet.yaml and compare the geoCoordinates input expected when INDEXER_AGENT_MULTINETWORK_MODE is true versus false. Reproduce the discrepancy using the two coordinate formats described in the issue; done means both modes provide consistent coordinate input behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100