Overflow error on lq listing

[TG-Brad]

Error:

Uncaught Error: overflow [ See: https://links.ethers.org/v5-errors-NUMERIC_FAULT-overflow ] (fault="overflow", operation="toNumber", value="9007200921603363", code=NUMERIC_FAULT, version=bignumber/5.7.0)
    at Logger.makeError (index.ts:269:1)
    at Logger.throwError (index.ts:281:1)
    at throwFault (bignumber.ts:356:1)
    at BigNumber.toNumber (bignumber.ts:186:1)
    at useLiquidityUnlockTime (hooks.ts:164:1)
    at FullPositionCard (index.tsx:130:1)
    at renderWithHooks (react-dom.development.js:14985:1)
    at updateFunctionComponent (react-dom.development.js:17356:1)
    at beginWork (react-dom.development.js:19063:1)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945:1)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:1)
    at invokeGuardedCallback (react-dom.development.js:4056:1)
    at beginWork$1 (react-dom.development.js:23964:1)
    at performUnitOfWork (react-dom.development.js:22776:1)
    at workLoopSync (react-dom.development.js:22707:1)
    at renderRootSync (react-dom.development.js:22670:1)
    at performSyncWorkOnRoot (react-dom.development.js:22293:1)
    at react-dom.development.js:11327:1
    at unstable_runWithPriority (scheduler.development.js:646:1)
    at runWithPriority$1 (react-dom.development.js:11276:1)
    at flushSyncCallbackQueueImpl (react-dom.development.js:11322:1)
    at flushSyncCallbackQueue (react-dom.development.js:11309:1)
    at batchedUpdates$1 (react-dom.development.js:22387:1)
    at Object.notify (Subscription.js:19:1)
    at Subscription.notifyNestedSubs (Subscription.js:90:1)
    at Subscription.handleChangeWrapper (Subscription.js:95:1)
    at dispatch (redux.js:222:1)
    at index.js:260:1
    at serializableStateInvariantMiddleware.ts:190:1
    at immutableStateInvariantMiddleware.ts:262:1
    at updater.tsx:174:1

[BytePhoenixCoding]

Think that's to do with BigNumbers, had a similar thing before. Does my head in lol

[TG-Brad]

Think I had it too high by 1 number potentially, though when going Lock Forever and setting it to the highest int - 1 so it doesn't overflow apparently has it so high it's an invalid date. That works though, I'll just make invalid dates say forever because they're locked forever anyway. 😂