@bot preview-e.cash

rebase

In D16138#365514, @Fabien wrote:

You had the same test plan in D16131, how come it didn't work ? Did you run your test plan ?

make sure chronik/ files are in place before calling ./build-wasm

rebase

ecash-lib-integration tests also depend on ecashaddrjs

It is passing locally but so were the previous diffs

something going on with the rebasing here

lint

ecashaddrjs needs to be built first

rebase to include updates from depends on

update other apps that do not have CI deployments but do have CI tests

rebase to include js-mocha-integration-tests template update

rebase

remove cashtab copypasta, do not label stage 1 if there are no other stages

update CI for local deps

need to update CI for tests

put Cargo.toml in place

improve comment order

remove checksum

re-add legacy Dockerfile for now

For the sake of avoiding breaking production, I would suggest you don't remove the cashtab/Dockerfile yet. This is the right move but it buys you time to update the CI to the new one and make sure everything is working before you actually remove the file, so you always have a backup.

In D16123#365192, @emack wrote:

We already have an implementation of this in the Alias codebase, what additional benefit do you get from using this library to achieve this?

improve logic by using padstart

In D16122#365091, @emack wrote:

Much better. Although I noticed it is scrolling even when there isn't content down below, however that's in prod too so not specific to this diff but nontheless I think previously we tried to stop that?

It is a bit complicated to setup these txs. Not too big of a deal since will be handled by devs and not users.

use const for repeated elapsed timers, correct double 0 string issue

wait for expected ws msgs before testing them

In D16088#364978, @teamcity wrote:

Build Bitcoin ABC Diffs / Diff Testing (chronik-client-integration-tests) failed.

Failed tests logs:

====== History endpoints and websocket for LOKAD ID: Websocket and endpoints correctly recognize txs with a lokadId in an input scriptSig and the same lokadId in OP_RETURN (non-EMPP).History endpoints and websocket for LOKAD ID Websocket and endpoints correctly recognize txs with a lokadId in an input scriptSig and the same lokadId in OP_RETURN (non-EMPP) ======
AssertionError: expected [] to deeply equal [ { type: 'Tx', …(2) } ]
    at /work/modules/chronik-client/test/integration/lokad_id.ts:254:47
    at Generator.next (<anonymous>)
    at fulfilled (test/integration/lokad_id.ts:31:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

      + expected - actual

      -[]
      +[
      +  {
      +    "msgType": "TX_ADDED_TO_MEMPOOL"
      +    "txid": "1ef4bebdb5a1298877aed9b7f741e3e0903820514316a35f3e7c05957308471a"
      +    "type": "Tx"
      +  }
      +]
====== History endpoints and websocket for LOKAD ID: Websocket and endpoints correctly recognize a tx with a new lokadId in a spend input and a new lokad id in EMPP OP_RETURN.History endpoints and websocket for LOKAD ID Websocket and endpoints correctly recognize a tx with a new lokadId in a spend input and a new lokad id in EMPP OP_RETURN ======
AssertionError: expected [ { type: 'Tx', …(2) }, …(1) ] to deeply equal [ { type: 'Tx', …(2) } ]
    at /work/modules/chronik-client/test/integration/lokad_id.ts:307:47
    at Generator.next (<anonymous>)
    at fulfilled (test/integration/lokad_id.ts:31:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

      + expected - actual

       [
         {
           "msgType": "TX_ADDED_TO_MEMPOOL"
      -    "txid": "1ef4bebdb5a1298877aed9b7f741e3e0903820514316a35f3e7c05957308471a"
      -    "type": "Tx"
      -  }
      -  {
      -    "msgType": "TX_ADDED_TO_MEMPOOL"
           "txid": "a989e07ae47f3925e911942e6dfbb0a5217fbd6617975b5c7a03a235c0c8a554"
           "type": "Tx"
         }
       ]
====== History endpoints and websocket for LOKAD ID: After these txs are mined, chronik-client returns this info appropriately.History endpoints and websocket for LOKAD ID After these txs are mined, chronik-client returns this info appropriately ======
AssertionError: expected [ { type: 'Tx', …(2) }, …(1) ] to deeply equal [ { type: 'Tx', …(2) } ]
    at /work/modules/chronik-client/test/integration/lokad_id.ts:372:59
    at Generator.next (<anonymous>)
    at fulfilled (test/integration/lokad_id.ts:31:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

      + expected - actual

           "msgType": "TX_CONFIRMED"
           "txid": "1ef4bebdb5a1298877aed9b7f741e3e0903820514316a35f3e7c05957308471a"
           "type": "Tx"
         }
      -  {
      -    "msgType": "TX_CONFIRMED"
      -    "txid": "a989e07ae47f3925e911942e6dfbb0a5217fbd6617975b5c7a03a235c0c8a554"
      -    "type": "Tx"
      -  }
       ]

Each failure log is accessible here:
History endpoints and websocket for LOKAD ID: Websocket and endpoints correctly recognize txs with a lokadId in an input scriptSig and the same lokadId in OP_RETURN (non-EMPP).History endpoints and websocket for LOKAD ID Websocket and endpoints correctly recognize txs with a lokadId in an input scriptSig and the same lokadId in OP_RETURN (non-EMPP)
History endpoints and websocket for LOKAD ID: Websocket and endpoints correctly recognize a tx with a new lokadId in a spend input and a new lokad id in EMPP OP_RETURN.History endpoints and websocket for LOKAD ID Websocket and endpoints correctly recognize a tx with a new lokadId in a spend input and a new lokad id in EMPP OP_RETURN
History endpoints and websocket for LOKAD ID: After these txs are mined, chronik-client returns this info appropriately.History endpoints and websocket for LOKAD ID After these txs are mined, chronik-client returns this info appropriately