[BUG] Some testing issues

[paulgoleary]

Found some potential issues testing with production data around sendCertificate. Capturing here to follow up.

• Large numbers in bridge table - likely others - choke meddler
  • e.g. 1.5e+19 These numbers appear to be valid.
  • Haven't found a good remediation. The sqlite type is DECIMAL(78, 0) but the type returned from the internal query is string. Then big.Int.SetString fails because it doesn't support exponent in the string.
• Logical inconsistency: shouldSendCertificate checks that there are no pending certs. But then GetLastSentCertificate filters and only selects pending certs.
  • The net result is that sendCertificate only sends one cert and then doesn't send again
  • My fix (workaround?) is to remove the PENDING predicate from GetLastSentCertificate
• Got code generating test certs from production data. Not sure if they are 'valid' because - for instance - don't seem to see any claims yet.
  • Q: are we indexing old claim format? If not, might want to for testing purposes.

[vcastellm]

Large numbers in bridge table - likely others - choke meddler

• e.g. 1.5e+19 These numbers appear to be valid.
• Haven't found a good remediation. The sqlite type is DECIMAL(78, 0) but the type returned from the internal query is string. Then big.Int.SetString fails because it doesn't support exponent in the string.

See this comment https://github.com/0xPolygon/cdk/pull/22/files#r1816496554 I think that's should be the way to go

[goran-ethernal]

@paulgoleary First two points are solved, and are merged to the develop branch on cdk repo.