fix: await in sequence

[DecathectZero]

It's critical that any list of messages coming in are added to the log in the right order.

We have channels/actions that write this incoming data into the database upon adding to the log.
It can potentially run out of order because we run lines 74-78:

core/sync/index.js

Lines 74 to 81 in 0a021be

	return this.options
	.inFilter(...filtered)
	.then(res => {
	return res ? filtered : false
	})
	.catch(e => {
	this.error(e)
	})

the inFilter is actually another promise, and on logux/server, it awaits processor.access:
https://github.com/logux/server/blob/63337798eea393fbeee1c6cb519bce3ae71ef354/server-client/index.js#L214

This means the this.log.add and subsequent processor.process could be out of order.

[ai]

Can you revert this change? It breaks CI since we use another code standard.

[DecathectZero]

yup, noted

[ai]

Good fix. I added Promise.all to make it faster by “parallel” processing, but I agree that it could create more problems.

We need to release it as major release. Do you need to release it quickly (or you found some hacky workaround)?

[DecathectZero]

Good fix. I added Promise.all to make it faster by “parallel” processing, but I agree that it could create more problems.

We need to release it as major release. Do you need to release it quickly (or you found some hacky workaround)?

@ai a quicker release would be preferred, but appreciate whatever works best for you!

[ai]

I will try to do the release on weekend

[ai]

Done. I released Logux Core 0.8 (release name Ա in honor of Armenian alphabet) and major versions of Logux Server and Logux Client.