Cannot read property 'forEach' of undefined

[NZT48]

Issue description

The v6 beta.1.23 release introduces several breaking changes, so if you are a node runner make sure to check the necessary instructions:

• OT-Node cleanup (#1746)
• Blazegraph setup instructions (#1747)

Nodes that have not been updated will cause next error message on other nodes:

[2022-02-11 15:39:15] ERROR: Error: TypeError: Cannot read property 'forEach' of undefined, stack: TypeError: Cannot read property 'forEach' of undefined
    at DataService.createAssertion (/root/ot-node/modules/service/data-service.js:123:19)
    at PublishService.handleStore (/root/ot-node/modules/service/publish-service.js:88:57)
    at /root/ot-node/modules/controller/rpc-controller.js:120:85
    at /root/ot-node/external/libp2p-service.js:174:42
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
 Data received: [object Object]
[2022-02-11 15:39:15] USERLVL: Found error will be reported to Telemetry: Libp2pHandleMessageError

Expected behavior

We expect this error message to be gone after all nodes have the version beta 1.23 or higher.

Specifications

• Node version: v6 beta.1.23
• Platform: Ubuntu
• Node wallet: any
• Node libp2p identity: any

Contact details

• Email: /

Error logs

[2022-02-11 15:39:15] ERROR: Error: TypeError: Cannot read property 'forEach' of undefined, stack: TypeError: Cannot read property 'forEach' of undefined
    at DataService.createAssertion (/root/ot-node/modules/service/data-service.js:123:19)
    at PublishService.handleStore (/root/ot-node/modules/service/publish-service.js:88:57)
    at /root/ot-node/modules/controller/rpc-controller.js:120:85
    at /root/ot-node/external/libp2p-service.js:174:42
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
 Data received: [object Object]
[2022-02-11 15:39:15] USERLVL: Found error will be reported to Telemetry: Libp2pHandleMessageError

Disclaimer

Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].

[Valcyclovir]

Some precision :

By @NZT48 : "The 'Cannot read property 'forEach' of undefined' is not related to GraphDB [or Blazegraph], but to changes that we introduced into data layer about how some data is processed before writing and after reading from triple store, so the nodes with versions older then v1.23 will send data in format that is different from nodes with new version and that will cause the error on all nodes with new version until those old nodes switch to new version"

• Until ALL test node runners switch to V1.23 this error might still show up on your logs.
• Blazegraph does NOT affect the outcome of this error
• You can decide to keep using GraphDB, but the team had some issues with GraphDB, so they introduced Blazegraph as an alternative. It is yet to be decided what would be the default triple store (recommended by team). The team wants to see how Blazegraph performs on the network.