Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does flushing some times get "out of sync"? #17

Closed
unhammer opened this issue May 3, 2016 · 1 comment
Closed

Does flushing some times get "out of sync"? #17

unhammer opened this issue May 3, 2016 · 1 comment

Comments

@unhammer
Copy link
Member

unhammer commented May 3, 2016

failing sanity-tests run about one hour apart give

exit code 1: .cat-fra: expected 'pour', got 'chaud' (for input: per)
exit code 1: ...................cat-fra: expected 'pour', got 'Éternels' (for input: per)
exit code 1: ............................................................cat-fra: expected 'pour', got '*carcater' (for input: per)
exit code 1:
exit code 1: ........................................................cat-fra: expected 'pour', got 'boulangerie' (for input: per)
exit code 1:
exit code 1: ..........................................cat-fra: expected 'pour', got 'relâcher' (for input: per)
exit code 1: .......................cat-fra: expected 'pour', got '*Cotilló' (for input: per)
exit code 1: ............cat-fra: expected 'pour', got 'rainure' (for input: per)
exit code 1: .................................................cat-fra: expected 'pour', got 'approuvez' (for input: per)

as if the output of sending "per" into apy's cat-fra was from the input of an earlier request.

(That seems quite bad)

@TinoDidriksen
Copy link
Member

It definitely still happens. Currently getting swe-nno: expected 'kva', got 'mitt *sdk-baserte tillegg kan ikkje vert oppgradert' (for input: vad) errors from the hourly selftest.

A solution is to add a nonce to each request sent through the backend pipe. If it doesn't come out with the same nonce, restart that pipe and try again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants