import { DFUSE_API_KEY, runMain, DFUSE_API_NETWORK, prettifyJson } from "../../config"
import { createDfuseClient, Stream, DfuseClient, GraphqlStreamMessage } from "@dfuse/client"
import { writeFileSync, readFileSync, existsSync } from "fs"
import * as path from "path"

/**
 * In this example, we will showcase how to implement bulletproof
 * data integrity while using the dfuse GraphQL Stream by ensuring
 * you never miss a single beat.
 *
 * This pattern can be used when you want to process messages only
 * once, while still ensuring you correctly receive all the blocks,
 * transactions and actions you want to process.
 *
 * We go through an example of how to easily mark the stream progress
 * and how the marker is then used when the socket reconnects to
 * restart the stream at the exact location you need.
 *
 * In the example we will implement an action persistence storer,
 * having our code restart at the exact correct place a commit had
 * occurred.
 */
const LAST_CURSOR_FILENAME = "last_cursor.txt"

async function main(): Promise<void> {
  const client = createDfuseClient({
    apiKey: DFUSE_API_KEY,
    network: DFUSE_API_NETWORK,
    graphqlStreamClientOptions: {
      socketOptions: {
        reconnectDelayInMs: 250,
      },
    },
  })

  const engine = new Engine(client)
  await engine.run()

  client.release()
}

type Message<T> = {
  searchTransactionsForward: {
    undo: boolean
    cursor: string
    block: {
      id: string
      num: number
    }
    trace?: {
      matchingActions: {
        json: T
      }[]
    }
  }
}

type KarmaTransfer = {
  from: string
  to: string
  quantity: string
  memo: string
}

class Engine {
  private client: DfuseClient
  private stream?: Stream

  private pendingActions: KarmaTransfer[] = []
  private committedActions: KarmaTransfer[] = []

  constructor(client: DfuseClient) {
    this.client = client
  }

  public async run(): Promise<void> {
    console.log("Engine starting")

    /**
     * At the engine start, we load back our latest persisted cursor,
     * if it exists. This way, we either start fresh because it's the
     * very first time to script is run.
     *
     * Or, already ran but was stopped or crashed while streaming
     * data. In this case, our persistence storage (a simple file
     * in this demo), will contains our last persisted stored cursor.
     */
    let lastPersistedCursor = ""
    const lastCursorPath = path.resolve(__dirname, LAST_CURSOR_FILENAME)
    if (existsSync(lastCursorPath)) {
      lastPersistedCursor = readFileSync(lastCursorPath).toString()
      console.log("Read last persisted cursor, start back at cursor " + lastPersistedCursor)
    }

    /**
     * Two things to note in the operation GraphQL document.
     *
     * First thing, we use a `$cursor` variable to pass the cursor. This is critical
     * for proper functionning of the auto restart feature. On initial start of the
     * stream, the `$cursor` variable is used straight from the `variables` options
     * of the `graphql` method (which is either empty or the last persisted cursor).
     * However, upon a stream re-connection, the `variables.cursor` is automatically
     * updated with the latest marked cursor when provided enabling the stream to
     * automatically restart at the exact location it stops, i.e. the `cursor`.
     *
     * Second thing, we use the `liveMarkerInterval` which with give us a notification each
     * 10 blocks. This is useful to update the cursor when your query is low traffic.
     * Otherwise, you could restart thousands of blocks behing tip of chain. See
     * `onProgress` for further details about cursor saving on this notification.
     *
     * **Note** The `cursor` value when defined (i.e. not the empty string) always takes
     * precedence over `lowBlockNum`/`highBlockNum` boundaries. For example, a query
     * `cursor: "", lowBlockNum: 10, highBlockNum: 20` will start from `lowBlockNum`
     * then stream up, while `cursor: <cursor>, lowBlockNum: 10, highBlockNum: 20`
     * will start at `<cursor>` location, maybe transaction #3 within block #15 and
     * then reach top boundary and stop there.
     */
    const operation = `
      subscription ($cursor: String!) {
        searchTransactionsForward(query: "receiver:therealkarma action:transfer", cursor: $cursor, liveMarkerInterval: 10) {
          undo cursor
          block { id num }
          trace { matchingActions { json } }
        }
      }
    `

    this.stream = await this.client.graphql(
      operation,
      (message: GraphqlStreamMessage) => {
        if (message.type === "data") {
          this.onResult(message.data as Message<KarmaTransfer>)
        }

        if (message.type === "error") {
          this.onError(message.errors, message.terminal)
        }

        if (message.type === "complete") {
          this.onComplete()
        }
      },
      {
        variables: {
          /**
           * The `cursor` variable is used on initial start of the stream. Afterwards, if the
           * stream is marked (via `marker.mark(...)` like in the demo), the marked `cursor` will
           * be used upon a reconnection. This means `lastPersistedCursor` is only really used
           * once and overriden later on by the library. Other variables, if any, are left intact
           * and only the cursor is updated to reflect the current marker state.
           */
          cursor: lastPersistedCursor,
        },
      }
    )

    this.stream.onPostRestart = () => {
      console.log()
      console.log(
        "<============= Stream has reconnected to the socket correctly (at latest `mark()`) =============>"
      )
      console.log()

      /**
       * When the stream reconnects, we must flush all of the current pending transactions
       * as the stream restarts at our last marked block, inclusively.
       *
       * Since we mark after commit, anything currently in pending was not committed.
       * As such, let's flush all pending actions. The dfuse GraphQL Stream API will stream
       * them back anyway due to `cursor`.
       */
      console.log("Flushing pending action(s) due to refresh")
      this.pendingActions = []
    }

    console.log("Stream connected, ready to receive messages")

    // This join the stream, resolving only when the stream completes, which is never in our example
    // so we wait forever at that point.
    await this.stream.join()
  }

  private onProgress = (blockId: string, blockNum: number, cursor: string): void => {
    console.log(`Live marker received @ ${printBlock(blockId, blockNum)}`)

    // We commit also on progress. The reasoning is that we have now move 10 blocks
    // forward through the chain, and we received a corresponding cursor. In the
    // commit phase, we will mark the stream with `stream.mark({ cursor })` which
    // we ensure that on reconnection, the cursor will start back right at the
    // correct progress cursor, this is cost effective and improves slightly the
    // reconnection performance as we start closer to the tip of the chain.
    this.commit(cursor)
  }

  private onResult = (message: Message<KarmaTransfer>): void => {
    const data = message.searchTransactionsForward
    const { id: blockId, num: blockNum } = data.block

    // A message without the trace object being set means we deal with a live marker progress message
    if (!data.trace) {
      this.onProgress(blockId, blockNum, data.cursor)
      return
    }

    data.trace.matchingActions.forEach((action) => {
      const { from, to, quantity } = action.json

      console.log(
        `Pending transfer [${from} -> ${to} ${quantity}] @ ${printBlock(blockId, blockNum)}`
      )
      this.pendingActions.push(action.json)
    })

    console.log("Comitting changes after transaction")
    this.commit(data.cursor)
  }

  private onError = (errors: Error[], terminal: boolean): void => {
    console.log("Received an 'error' message", prettifyJson(errors))

    if (terminal) {
      console.log(
        "Received a terminal 'error' message, the stream will automatically reconnects in 250ms"
      )
    }
  }

  private onComplete = (): void => {
    console.log("Received a 'complete' message, no more results for this stream")
  }

  private commit(cursor: string): void {
    if (this.pendingActions.length > 0) {
      console.log(`Committing all actions up to cursor ${cursor}`)

      // Here, in your production code, action would be saved in a database, as well as error handling
      this.pendingActions.forEach((action) => this.committedActions.push(action))
      this.pendingActions = []
    }

    /**
     * This is one of the most important calls of the example. By marking the stream
     * at the right block, upon restarting, the stream will automatically start back
     * at this block ensuring you never miss a single action.
     */
    this.ensureStream().mark({ cursor })

    /**
     * In a real-word production code, you need to also persist the cursor into
     * a persistent storage. This is important so when the actual process ends
     * or crash, upon restart, you simply load your latest saved `cursor` and
     * starts back from that point.
     *
     * In this demo, we simply save it to a file on the file system. This could be
     * easily replaced with a database save, cloud upload, local storage in the
     * browser on anything that is persistent across restarts of the script.
     */
    writeFileSync(path.resolve(__dirname, LAST_CURSOR_FILENAME), cursor)
  }

  private ensureStream(): Stream {
    if (this.stream) {
      return this.stream
    }

    throw new Error("Stream should be set at this runtime execution point")
  }
}

function printBlock(blockId: string, blockNum: number): string {
  return `${blockId.slice(0, 8)}...${blockId.slice(-8)} (${blockNum})`
}

runMain(main)