Tim Möhlmann c0e45b63d8

fix: reset the call timestamp after a bulk trigger (#6080) ...

* reproduce #5808

Add an integration test that imports and gets N amount of human users.
- With N set to 1-10 the operation seems to succeed always
- With N set to 100 the operation seems to fail between 1 and 7 times.

* fix merge issue

* fix: reset the call timestamp after a bulk trigger

With the use of `AS OF SYSTEM TIME` in queries,
there was a change for the query package not
finding the latest projection verson after
a bulk trigger.
If events where processed in the bulk trigger,
the resulting row timestamp would be after the call
start timestamp.
This sometimes resulted in consistency issues when
Set and Get API methods are called in short succession.
For example a Import and Get user could sometimes result in a Not Found
error.

Although the issue was reported for the Management API user import,
it is likely this bug contributed to the flaky integration and e2e tests.

Fixes #5808

* trigger bulk action in GetSession

* don't use the new context in handler schedule

* disable reproduction test

---------

Co-authored-by: Livio Spring <livio.a@gmail.com>

2023-07-07 08:15:05 +00:00

..

duration_test.go

perf: query data AS OF SYSTEM TIME (#5231)

2023-02-27 22:36:43 +01:00

duration.go

fix: reset the call timestamp after a bulk trigger (#6080)

2023-07-07 08:15:05 +00:00