Error: tried to encode an invalid date

[mkitzmann]

Updating quotes for EOD -> MSFT, TSLA, AAPL, A, AA, SUSW to update
/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse-server/lib/ParseServer.js:261
          throw err;
          ^

Error: Tried to encode an invalid date.
    at encode (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/encode.js:85:13)
    at _default (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/encode.js:132:10)
    at SetOp.toJSON (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/ParseOp.js:155:32)
    at AssetPrice._getSaveJSON (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/ParseObject.js:487:61)
    at AssetPrice._getSaveParams (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/ParseObject.js:503:23)
    at task (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/ParseObject.js:3187:35)
    at TaskQueue.enqueue (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/TaskQueue.js:34:7)
    at Object.enqueueTask (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/UniqueInstanceStateController.js:275:22)
    at Object.save (/Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/ParseObject.js:3202:30)
    at /Users/mkitzmann/Developer/GoPlan-app/node_modules/parse/lib/node/ParseObject.js:1816:25
error Command failed with exit code 7.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Process finished with exit code 7

[sadortun]

@mkitzmann

This is most likely fixed by e7de1c4

We could add some checks to ensure that EOD result.timestamp is valid. or set a default value to now

-             assetPrice.recordedAt = dayjs.unix(result.timestamp).toDate();
+             assetPrice.recordedAt = result.timestamp ? dayjs.unix(result.timestamp).toDate() : dayjs().toDate();

[mkitzmann]

@mkitzmann

This is most likely fixed by e7de1c4

We could add some checks to ensure that EOD result.timestamp is valid. or set a default value to now

The check would be good. Setting it to today might not be the right solution. Maybe we should improve the error message first, so we know what value this problem actually occurs on.

[sadortun]

@mkitzmann how often do you have the issue?