{"version":"2.1.234","anchor":"a-risky-command-and-frustration-detector-is-present-but-emit","canonical_anchor":"a-risky-command-and-frustration-detector-is-present-but-emit","heading":"A risky-command and frustration detector is present but emits nothing","tier":"soon","area":"Proactivity","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/a-risky-command-and-frustration-detector-is-present-but-emit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### A risky-command and frustration detector is present but emits nothing\n\nA detector shipping patterns for risky commands and user frustration never fires, its handler is empty.\n\n**What**\n\nA subscriber called `issue-flag` ships with patterns for risky commands and for signs of user frustration, but its setup returns an empty handler, so it never fires in this build.\n\n**Details**\n\n- Risky command patterns include `curl`, `ssh`, `kubectl`, `git push` and `nc`.\n- Frustration phrases include `^no[,!]\\s` and `not what I (asked|wanted|meant|said)`.\n- A 1800000 ms (30 minute) cooldown is defined between flags.\n- The code was moved out of the older artifact-arming module.\n\n**Evidence**\n\n`issue-flag`\n\n- Area: Proactivity\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}