I've been noticing the the Pants Daemon (`pantsd`)...
# general
s
I've been noticing the the Pants Daemon (
pantsd
) starts up anew for every invocation of pants. I tried downgrading to older versions of pants, but still see the same behavior. I don't have any options set which would modify pantsd.
1
Options:
Copy code
➜  pants help-all global |  jq '{PANTS_PANTSD: .env_var_to_help_info.PANTS_PANTSD, PANTS_CONCURRENT: .env_var_to_help_info.PANTS_CONCURRENT}'      
{
  "PANTS_PANTSD": {
    "choices": null,
    "comma_separated_choices": null,
    "comma_separated_display_args": "--[no-]pantsd",
    "config_key": "pantsd",
    "default": true,
    "deprecated_message": null,
    "deprecation_active": false,
    "display_args": [
      "--[no-]pantsd"
    ],
    "env_var": "PANTS_PANTSD",
    "fromfile": false,
    "help": "Enables use of the Pants daemon (pantsd). pantsd can significantly improve runtime performance by lowering per-run startup cost, and by memoizing filesystem operations and rule execution.",
    "removal_hint": null,
    "removal_version": null,
    "scoped_cmd_line_args": [
      "--pantsd",
      "--no-pantsd"
    ],
    "target_field_name": null,
    "typ": "bool",
    "unscoped_cmd_line_args": [
      "--pantsd",
      "--no-pantsd"
    ],
    "value_history": {
      "ranked_values": [
        {
          "details": null,
          "rank": "NONE",
          "value": null
        },
        {
          "details": null,
          "rank": "HARDCODED",
          "value": true
        }
      ]
    }
  },
  "PANTS_CONCURRENT": {
    "choices": null,
    "comma_separated_choices": null,
    "comma_separated_display_args": "--[no-]concurrent",
    "config_key": "concurrent",
    "default": false,
    "deprecated_message": null,
    "deprecation_active": false,
    "display_args": [
      "--[no-]concurrent"
    ],
    "env_var": "PANTS_CONCURRENT",
    "fromfile": false,
    "help": "Enable concurrent runs of Pants. With this enabled, Pants will start up all concurrent invocations (e.g. in other terminals) without pantsd. As a result, enabling this option will increase the per-run startup cost, but will not block subsequent invocations.",
    "removal_hint": null,
    "removal_version": null,
    "scoped_cmd_line_args": [
      "--concurrent",
      "--no-concurrent"
    ],
    "target_field_name": null,
    "typ": "bool",
    "unscoped_cmd_line_args": [
      "--concurrent",
      "--no-concurrent"
    ],
    "value_history": {
      "ranked_values": [
        {
          "details": null,
          "rank": "NONE",
          "value": null
        },
        {
          "details": null,
          "rank": "HARDCODED",
          "value": false
        }
      ]
    }
  }
}
Ummm.... I can no longer reproduce 😵‍💫 up until I sent that message, I could reproduce consistently (watching the pantsd process die as soon as the pants invocation completed). Seems to have magically resolved....
w
Sometimes when that happens, wipe the .pants.d I dont see it often, I have seen it happen before though
👍 1