Excavator gets stuck on bedrock blocks

[nothub]

Description

I am experiencing a problem with the excavator. Whenever close to bedrock, the excavator seems to get stuck, switches to a hotbar slot with a placeable solid block in it and stops all visible excavation tasks.

Video

wurst.webm

crash report

[github-actions[bot]]

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

• They are duplicates of other issues
• There is not enough demand
• They are no longer relevant
• There are not enough details

[Alexander01998]

Still relevant.

[github-actions[bot]]

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

• They are duplicates of other issues
• There is not enough demand
• They are no longer relevant
• There are not enough details

[Alexander01998]

Yep, still happens.

[github-actions[bot]]

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

• They are duplicates of other issues
• There is not enough demand
• They are no longer relevant
• There are not enough details

[nothub]

https://drewdevault.com/2021/10/26/stalebot.html

[Alexander01998]

Hey @nothub, thanks for the article!

I agree that stalebot is a flawed system, but IMO it's just a flawed solution to the much more flawed system of GitHub issues.

It would be nice if everyone could just agree that the issue tracker isn't the maintainer's todo-list and that submitting a pull request doesn't entitle them to get their code fixed or even reviewed by the maintainer.

Unfortunately that's not the case. GitHub always makes it look like I have these responsibilities, so most people just assume that I do. And they keep posting issues/PRs and complaining that nothing happens to them.

Then they look at the meaningless number that counts open issues and unreviewed PRs, and they complain that it's "too high", whatever that means.

Despite all of stalebot's flaws, people complain a lot less with stalebot than they do without it. It makes the meaningless numbers go down and makes the not-a-todo-list look a lot cleaner. It's stupid, but unfortunately it works.