Hi, there seems to be a problem with the latest 2 versions of ArLocal (v1.1.63 and v1.

moving the discussion here (from <a class="issue-link js-issue-link" data-error-text="

Hey, I've found the root cause (testing on latest ArLocal version - <code class="notra

Write-interactions silently fail using Warp Contracts about arlocal HOT 3 CLOSED

erhant commented on June 11, 2024 1

Write-interactions silently fail using Warp Contracts

from arlocal.

Comments (3)

erhant commented on June 11, 2024 1

moving the discussion here (from warp-contracts/warp#494 (comment))

during this change v1.1.62...v1.1.63 the removal of || undefined causes null values to stay null instead of undefined, which the server probably does not handle.

from arlocal.

ppedziwiatr commented on June 11, 2024

Hey, I've found the root cause (testing on latest ArLocal version - 1.1.64)

The issue - latest versions of the ArLocal do not behave properly if null is passed as max in the block filter.
I.e. this filter works:

block: { min: 0, max: 100 }

This filter does NOT work:

block: { min: 0, max: null }

This works:

Query:

query {
  transactions(
    ids: ["thLz97087UrlLfXJ0RphXZ7g_mK569ro63ulCxxRtdY"],
    block: { min: 0, max: 100 }
  ) {
    pageInfo {
      hasNextPage
    }
    edges {
      node {
        id
        bundledIn {
          id
        }
        tags {
          name
          value
        }
      }
    }
  }
}

This does NOT work:

Query:

query {
  transactions(
    ids: ["thLz97087UrlLfXJ0RphXZ7g_mK569ro63ulCxxRtdY"],
    block: { min: 0, max: null }
  ) {
    pageInfo {
      hasNextPage
    }
    edges {
      node {
        id
        bundledIn {
          id
        }
        tags {
          name
          value
        }
      }
    }
  }
}

This apparently has changed in the latest ArLocal versions AND is inconsistent with how the arweave.net/graphql works: