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

Closing Eclipse should not block on Bazel commands #156

Closed

plaird opened this issue Aug 25, 2020 · 0 comments · Fixed by #172

Assignees

Labels

bug

Contributor

plaird commented Aug 25, 2020

Repro:

import a moderately sized bazel workspace into BEF
kick off a command on the command line that will take a while (e.g. bazel clean && bazel test //...)
try and close Eclipse+BEF, it will hang waiting to run some Bazel commands (which are blocked by the long running command)

Ideally we wouldn't block when closing. Either don't execute any bazel commands (best) or at least timeout and close after 15 seconds or so.

plaird added the bug label

plaird mentioned this issue

implement early exit from getClasspath for fast IDE close and other use cases #172

Merged

plaird closed this as completed in #172

plaird self-assigned this

plaird mentioned this issue

Closing the IDE after a command line 'bazel clean --expunge' throws many errors #113

Closed

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