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.

Sign up for GitHub

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

Jump to bottom

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

Closed
bep opened this issue Jul 1, 2018 · 1 comment
Closed

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

bep opened this issue Jul 1, 2018 · 1 comment
Assignees
@bep
Labels
Bug Outdated
Milestone
v0.43

Comments

@bep
Copy link
Member

bep commented Jul 1, 2018 •
edited

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 After should not fail on "error calling after: no items left" After should not fail with "error calling after: no items left" Jul 1, 2018
@bep bep closed this as completed in f8212d2 Jul 1, 2018
@dependencies dependencies bot mentioned this issue Jul 9, 2018
Closed
@github-actions
Copy link

github-actions bot commented Mar 2, 2022

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bep bep

Labels
Bug Outdated
Projects
None yet
Milestone
v0.43
Development

No branches or pull requests
1 participant
@bep