You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, like in the example below, it can happen that the use message within onConnected is sent after the live message, although it should be the other way around. It suggests a racing condition not being respected with the useBuffer.
In the following screenshot the request with id 1 is the configuration message (method: 'use'), while the request with id 0 is the live('products'). For no reason, at random, they switch order like this.
The text was updated successfully, but these errors were encountered:
https://github.com/Sandros94/nuxt-surrealdb/blob/57e46f334a0848069b82cd8a00925ba1cbccb8d7/src/runtime/composables/surreal-ws.ts#L59-L80
Currently, like in the example below, it can happen that the
use
message withinonConnected
is sent after thelive
message, although it should be the other way around. It suggests a racing condition not being respected with theuseBuffer
.https://github.com/Sandros94/nuxt-surrealdb/blob/0fb0bf34f703613bb65230e80fc56ffae43d539b/playground/pages/ws-examples.vue#L21-L22
In the following screenshot the request with
id 1
is the configuration message (method: 'use'
), while the request withid 0
is thelive('products')
. For no reason, at random, they switch order like this.The text was updated successfully, but these errors were encountered: