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
If tests are just in running a @runOnServer test, then if the server is restarted at that time (because some test changed), client retries the method, but the test instance does not exist anymore, so errors are thrown in the server side console.
One option would be to find a way to call those methods without them be retried on server restart.
Another is to pass current connection ID when calling the method, so that if the server is retried, an old connection ID will be send as an argument. Server side then checks that the connection ID matches current connection ID before progressing.
The text was updated successfully, but these errors were encountered:
If tests are just in running a
@runOnServer
test, then if the server is restarted at that time (because some test changed), client retries the method, but the test instance does not exist anymore, so errors are thrown in the server side console.One option would be to find a way to call those methods without them be retried on server restart.
Another is to pass current connection ID when calling the method, so that if the server is retried, an old connection ID will be send as an argument. Server side then checks that the connection ID matches current connection ID before progressing.
The text was updated successfully, but these errors were encountered: