You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now Bzl is the application - you can start it from the command line and the console stays locked until Bzl finishes (or gets killed). Please consider mimicking Bazel approach when "bazel" command fires up background process (if it is not yet running) and delegates the work to that process. Then Bzl command would return to console right after the command is sent to the server. For example I visualize client commands such as
I really want to differentiate Bzl service (daemon) and Bzl client (GUI, command line, whatever).
Bzl client should delegate the work to service and return control immediately unless it is intentionally used for some long running operation such as displaying ongoing status, statistics, etc.
Right now Bzl is the application - you can start it from the command line and the console stays locked until Bzl finishes (or gets killed). Please consider mimicking Bazel approach when "bazel" command fires up background process (if it is not yet running) and delegates the work to that process. Then Bzl command would return to console right after the command is sent to the server. For example I visualize client commands such as
The text was updated successfully, but these errors were encountered: