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
The title says it all.
The problem can be easily reproduced in the rather sloppy code below.
I think the problem is simple, as I also wrote in pull request #17 .
I believe updating of the last_generation deserves the same handling as the report_generation(new_generation);
Which would coincidentally stop last_generation from being overwritten by empty new_generation, which should only
be empty when user_request_stop is set.
The title says it all.
The problem can be easily reproduced in the rather sloppy code below.
I think the problem is simple, as I also wrote in pull request #17 .
I believe updating of the last_generation deserves the same handling as the report_generation(new_generation);
Which would coincidentally stop last_generation from being overwritten by empty new_generation, which should only
be empty when user_request_stop is set.
The text was updated successfully, but these errors were encountered: