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
{{ message }}
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
Similar to #503, except that the reallocated peers is also assigned a whole new slot-id, 1, rather than slot-id 0, which is the correct slot given that there is only one peer allocated to the task.
This causes the windowing/state-management to break, as a task's state becomes split over multiple slots.
The text was updated successfully, but these errors were encountered:
Caused by not doing a de-allocation pass before an allocation pass.
This meant that a slot that should be taken by an allocation was not
available when the allocation occurred before the deallocation.
Caused by not doing a de-allocation pass before an allocation pass.
This meant that a slot that should be taken by an allocation was not
available when the allocation occurred before the deallocation.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Similar to #503, except that the reallocated peers is also assigned a whole new slot-id, 1, rather than slot-id 0, which is the correct slot given that there is only one peer allocated to the task.
This causes the windowing/state-management to break, as a task's state becomes split over multiple slots.
The text was updated successfully, but these errors were encountered: