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.

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

Deadlock detection for supply fail-case #20

Open
rtwong opened this issue Nov 24, 2015 · 1 comment
Open

Deadlock detection for supply fail-case #20

rtwong opened this issue Nov 24, 2015 · 1 comment

Comments

@rtwong
Copy link

rtwong commented Nov 24, 2015

If the build order goal has a queued nexus/pylon, and the probe has the action called to go put down this supply structure, but then is killed onroute, the pylon/nexus is removed from the build order goal like desired, however a flag that says whether or not a supplybuilding is building is not properly reset, making it so that the deadlock check returns the incorrect answer.

This bug is most easily noticed when the bot tries to expand for the first time at ~40 supply, if the probe is intercepted no more pylons will be attempted to be built even when supply blocked.

@davechurchill
Copy link
Owner

Thanks, will look into it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants