镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

We should run a mini crawl frequently #67

Open

Description

@TimDaub
  • neume-network/data runs a full crawl in roughly 2-3hrs every day
  • But to get e.g. feedback whether some strategies are properly integrated with each other can hence take a very long time. E.g. if we ship a change in strategy X, and downstream strategies break because of it, it may take up to one day for this to surface in a crash of the neume-network/data crawl
  • However, we don't have to crawl the entire chain and all platforms to get the information whether e.g. all strategies are properly integrated with each other. Instead, we could e.g. set up web3subgraph or any other starting strategy to e.g. only return a single id e.g. [{"id":"0x01ab7d30525e4f3010af27a003180463a6c811a6/1","createdAtBlockNumber":"14323199","platform":"sound"} and then do the crawl for just that id. (I've just taken the first value of: https://github.com/raw/neume-network/data/main/results/web3subgraph-extraction)
  • If we found a set of start ids that resulted in all strategies being invoked at least once, we could probably finish an entire mini crawl in a matter of seconds or minutes: and we'd have a fast response/feedback for making coding mistakes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions