cerc-io/stack-orchestrator
16
1
Fork 1
Code Issues 87 Pull Requests 14 Actions Packages Projects Releases 434 Wiki Activity

WIP: update uniswap stack with ipld-eth-server #465

Closed
zramsay wants to merge 2 commits from update-uniswap into main
pull from: update-uniswap
merge into: cerc-io:main
Conversation 0 Commits 2 Files Changed 6 +16 -8
zramsay commented 2023-07-27 01:14:29 +00:00
Member
Copy Link

currently fails like so:

# laconic-so --stack uniswap-v3 deploy up
[+] Running 11/11
 ✔ Network laconic-30b284773ec895b5a4601fcc6bd17780_default                          Cre...                                                            0.1s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uniswap-watcher-db-1           Healthy                                                          53.0s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-ipld-eth-db-1                  Healthy                                                          31.3s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-erc20-watcher-server-1         Healthy                                                          53.0s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uni-watcher-job-runner-1       Healthy                                                          41.7s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-migrations-1                   Started                                                          31.6s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-ipld-eth-server-1              Healthy                                                          52.1s 
 ✘ Container laconic-30b284773ec895b5a4601fcc6bd17780-uni-watcher-server-1           Error                                                           353.8s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uni-info-watcher-job-runner-1  Created                                                           0.0s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uni-info-watcher-server-1      Created                                                           0.0s 
 ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uniswap-v3-info-1              Created                                                           0.0s

looking at: # docker logs laconic-30b284773ec895b5a4601fcc6bd17780-uni-watcher-job-runner-1 there's the clue:

2023-07-27T00:35:58.433Z vulcanize:job-runner Starting job runner...
2023-07-27T00:35:58.436Z vulcanize:metrics Metrics exposed at http://0.0.0.0:9000/metrics
2023-07-27T00:36:18.403Z vulcanize:job-queue Processing queue block-processing job 99ee9830-2c15-11ee-9af8-0bb6564ab21d...
2023-07-27T00:36:18.404Z vulcanize:common size:common#fetchBlocksAtHeight-prefetch-_blockAndEventsMap-size: 0
2023-07-27T00:36:18.446Z vulcanize:common common#cache-miss-12369621
time:eth-client#getBlocks-{"blockNumber":12369621}: 87.234ms
time:eth-client#getBlocks-{"blockNumber":12369628}: 70.899ms
time:eth-client#getBlocks-{"blockNumber":12369629}: 80.177ms
time:eth-client#getBlocks-{"blockNumber":12369622}: 97.556ms
time:eth-client#getBlocks-{"blockNumber":12369630}: 84.205ms
time:eth-client#getBlocks-{"blockNumber":12369627}: 95.676ms
time:eth-client#getBlocks-{"blockNumber":12369625}: 99.747ms
time:eth-client#getBlocks-{"blockNumber":12369623}: 107.078ms
time:eth-client#getBlocks-{"blockNumber":12369624}: 106.508ms
time:eth-client#getBlocks-{"blockNumber":12369626}: 103.295ms
time:common#fetchBatchBlocks-getBlocks: 168.341ms
2023-07-27T00:36:18.615Z vulcanize:common No blocks fetched for block number 12369621, retrying after 2000 ms delay.

I think the Optional step in the README is required with the correct heights. There also may be better ways to do this with the latest development of SO.

currently fails like so: ``` # laconic-so --stack uniswap-v3 deploy up [+] Running 11/11 ✔ Network laconic-30b284773ec895b5a4601fcc6bd17780_default Cre... 0.1s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uniswap-watcher-db-1 Healthy 53.0s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-ipld-eth-db-1 Healthy 31.3s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-erc20-watcher-server-1 Healthy 53.0s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uni-watcher-job-runner-1 Healthy 41.7s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-migrations-1 Started 31.6s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-ipld-eth-server-1 Healthy 52.1s ✘ Container laconic-30b284773ec895b5a4601fcc6bd17780-uni-watcher-server-1 Error 353.8s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uni-info-watcher-job-runner-1 Created 0.0s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uni-info-watcher-server-1 Created 0.0s ✔ Container laconic-30b284773ec895b5a4601fcc6bd17780-uniswap-v3-info-1 Created 0.0s ``` looking at: `# docker logs laconic-30b284773ec895b5a4601fcc6bd17780-uni-watcher-job-runner-1` there's the clue: ``` 2023-07-27T00:35:58.433Z vulcanize:job-runner Starting job runner... 2023-07-27T00:35:58.436Z vulcanize:metrics Metrics exposed at http://0.0.0.0:9000/metrics 2023-07-27T00:36:18.403Z vulcanize:job-queue Processing queue block-processing job 99ee9830-2c15-11ee-9af8-0bb6564ab21d... 2023-07-27T00:36:18.404Z vulcanize:common size:common#fetchBlocksAtHeight-prefetch-_blockAndEventsMap-size: 0 2023-07-27T00:36:18.446Z vulcanize:common common#cache-miss-12369621 time:eth-client#getBlocks-{"blockNumber":12369621}: 87.234ms time:eth-client#getBlocks-{"blockNumber":12369628}: 70.899ms time:eth-client#getBlocks-{"blockNumber":12369629}: 80.177ms time:eth-client#getBlocks-{"blockNumber":12369622}: 97.556ms time:eth-client#getBlocks-{"blockNumber":12369630}: 84.205ms time:eth-client#getBlocks-{"blockNumber":12369627}: 95.676ms time:eth-client#getBlocks-{"blockNumber":12369625}: 99.747ms time:eth-client#getBlocks-{"blockNumber":12369623}: 107.078ms time:eth-client#getBlocks-{"blockNumber":12369624}: 106.508ms time:eth-client#getBlocks-{"blockNumber":12369626}: 103.295ms time:common#fetchBatchBlocks-getBlocks: 168.341ms 2023-07-27T00:36:18.615Z vulcanize:common No blocks fetched for block number 12369621, retrying after 2000 ms delay. ``` I think the `Optional` step in the README is required with the correct heights. There also may be better ways to do this with the latest development of SO.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
feature

   
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
in progress

   
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
in progress
invalid
question
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 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/stack-orchestrator#465
No description provided.
Delete Branch "update-uniswap"

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?