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

After should not fail with "error calling after: no items left" #4894

bep opened this Issue Jul 1, 2018 · 0 comments


None yet
1 participant

bep commented Jul 1, 2018

This now happens in "index out of bound" situation. We worked hard to get index work without errors, this should behave similar. Getting errors are surprising and prevents simple with constructs. I have not checked all of them, but First behaves sensible in this situation.

@bep bep added the Bug label Jul 1, 2018

@bep bep added this to the v0.43 milestone Jul 1, 2018

@bep bep self-assigned this Jul 1, 2018

@bep bep changed the title from After should not fail on "error calling after: no items left" to After should not fail with "error calling after: no items left" Jul 1, 2018

@bep bep closed this in f8212d2 Jul 1, 2018

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