App::Y...::stop(3pm)

📦
version 1.000172 · 8 versions
, in ubuntu stonking

💖 App::Y...::stop(3pm) 💖

User Contributed Perl Documentation · App::Y...::stop(3pm) · yes bestie, that's the manual name, she's a little mysterious but she's valid 💅

🦋 NAME 🦋

App::Yath::Command::stop — Stop the persistent test runner 🛑

💅 DESCRIPTION 💅

okay so, real talk? This command will stop a persistent instance, and output any log contents. That's it. That's the whole job. She stops the thing, she shows you the logs, she leaves. main character energy, no notes ✨

🌸 USAGE 🌸

$ yath [YATH OPTIONS] stop [COMMAND OPTIONS]

✨ YATH OPTIONS ✨

the global vibes. these apply to yath itself, not just to stop.

🌈 Developer

  • --dev-lib, --dev-lib=lib, -D, -D=lib, -Dlib, --no-dev-lib — adds paths to @INC before loading ANYTHING. This is what you reach for if you're developing yath or yath plugins, so the yath script finds your local code instead of the installed versions of that exact same code. You can hand it an argument (-Dfoo) for a custom path, or just do -D with no arg and it adds lib, blib/lib and blib/arch. Can be specified multiple times 🔁

🌸 Environment

  • --persist-dir ARG, --persist-dir=ARG, --no-persist-dir — where to find persistence files 📁
  • --persist-file ARG, --persist-file=ARG, --pfile ARG, --pfile=ARG, --no-persist-file — where to find the persistence file. The default is /{system-tempdir}/project-yath-persist.json. If no project is specified then it will fall back to the current directory. And if the current directory is not writable it will default to /tmp/yath-persist.json, which limits you to one persistent runner on your system 🫠
  • --project ARG, --project=ARG, --project-name ARG, --project-name=ARG, --no-project — this lets you provide a label for your current project/codebase. Best used in a .yath.rc file. This is necessary for a persistent runner 🏷️

🔍 Finder Options

  • --finder MyFinder, --finder +Test2::Harness::Finder::MyFinder, --no-finder — specify what Finder subclass to use when searching for files / processing the file list. Use the + prefix to specify a fully qualified namespace, otherwise the Test2::Harness::Finder::XXX namespace is assumed 🕵️

🆘 Help and Debugging

  • --show-opts, --no-show-opts — exit after showing what yath thinks your options mean 👀
  • --version, -V, --no-version — exit after showing a helpful usage message 📜

🧚 Plugins

  • --no-scan-plugins, --no-no-scan-plugins — normally yath scans for and loads all App::Yath::Plugin::* modules so it can bring in whatever command-line options they provide. This flag disables that. Super useful if you have a naughty plugin that is loading other modules when it should not 🙈
  • --plugins PLUGIN, --plugins +App::Yath::Plugin::PLUGIN, --plugins PLUGIN=arg1,arg2,..., --plugin PLUGIN, --plugin +App::Yath::Plugin::PLUGIN, --plugin PLUGIN=arg1,arg2,..., -pPLUGIN, --no-plugins — load a yath plugin 🧩 Can be specified multiple times.

🚀 COMMAND OPTIONS 🚀

🎀 Cover Options

  • --cover-aggregator ByTest, --cover-aggregator ByRun, --cover-aggregator +Custom::Aggregator, --cover-agg ByTest, --cover-agg ByRun, --cover-agg +Custom::Aggregator, --no-cover-aggregator — choose a custom aggregator subclass 🧮
  • --cover-class ARG, --cover-class=ARG, --no-cover-class — choose a Test2::Plugin::Cover subclass 🎨
  • --cover-dirs ARG, --cover-dirs=ARG, --cover-dir ARG, --cover-dir=ARG, --no-cover-dirs — NO DESCRIPTION - FIX ME 😭 (that's literally what the docs say, I'm not gonna invent a meaning for you). Can be specified multiple times.
  • --cover-exclude-private, --no-cover-exclude-private, --cover-files, --no-cover-files — use Test2::Plugin::Cover to collect coverage data for what files are touched by what tests. Unlike Devel::Cover this has very little performance impact (About 4% difference) ⚡
  • --cover-from path/to/log.jsonl, --cover-from http://example.com/coverage, --cover-from path/to/coverage.jsonl, --no-cover-from — this can be a test log, a coverage dump (old style json or new jsonl format), or a url to any of the previous. Tests will not be run if the file/url is invalid 🚫
  • --cover-from-type json, --cover-from-type jsonl, --cover-from-type log, --no-cover-from-type — file type for coverage source. Usually it can be detected, but when it cannot be you should specify. "json" is old style single-blob coverage data, "jsonl" is the new by-test style, "log" is a logfile from a previous run 🔎
  • --cover-manager My::Coverage::Manager, --no-cover-manager — coverage 'from' manager to use when coverage data does not provide one 🧑💼
  • --cover-maybe-from path/to/log.jsonl, --cover-maybe-from http://example.com/coverage, --cover-maybe-from path/to/coverage.jsonl, --no-cover-maybe-from — this can be a test log, a coverage dump (old style json or new jsonl format), or a url to any of the previous. Tests will coninue if even if the coverage file/url is invalid 🫶
  • --cover-maybe-from-type json, --cover-maybe-from-type jsonl, --cover-maybe-from-type log, --no-cover-maybe-from-type — same as from_type but for maybe_from. Defaults to from_type if that is specified, otherwise auto-detect 🔁
  • --cover-metrics, --no-cover-metrics, --cover-types ARG, --cover-types=ARG, --cover-type ARG, --cover-type=ARG, --no-cover-types — NO DESCRIPTION - FIX ME 😭 again, that's the literal doc, I'm being honest with you. Can be specified multiple times.
  • --cover-write, --cover-write=coverage.jsonl, --cover-write=coverage.json, --no-cover-write — create a json or jsonl file of all coverage data seen during the run (This implies --cover-files) 📝

💖 Display Options

  • --color, --no-color — turn color on, default is true if STDOUT is a TTY 🌈
  • --hide-runner-output, --no-hide-runner-output — hide output from the runner, showing only test output. (See Also truncate_runner_output) 🤫
  • --no-final-table, --no-no-final-table — when printing final results, don't use table-style display 🙅
  • --no-wrap, --no-no-wrap — do not do fancy text-wrapping, let the terminal handle it 🌀
  • --progress, --no-progress — toggle progress indicators. On by default if STDOUT is a TTY. You can use --no-progress to disable the 'events seen' counter and buffered event pre-display ⏳
  • --quiet, -q, --no-quiet — be very quiet 🤐 Can be specified multiple times.
  • --renderers +My::Renderer, --renderers Renderer=arg1,arg2,..., --renderer +My::Renderer, --renderer Renderer=arg1,arg2,..., --no-renderers — specify renderers, (Default: Formatter=Test2). Use + to give a fully qualified module name. Without +, Test2::Harness::Renderer:: will be prepended to your argument. Can be specified multiple times. If the same key is listed multiple times the value lists will be appended together 🧵
  • --show-times, -T, --no-show-times — show the timing data for each job ⏱️
  • --term-width 80, --term-width 200, --term-size 80, --term-size 200, --no-term-width — alternative to setting $TABLE_TERM_SIZE. Setting this will override the terminal width detection to the number of characters specified 📏
  • --truncate-runner-output, --no-truncate-runner-output — only show runner output that was generated after the current command. This is only useful with a persistent runner ✂️
  • --verbose, -v, --no-verbose — be more verbose 🗣️ Can be specified multiple times.

🔍 Finder Options

  • --changed path/to/file, --no-changed — specify one or more files as having been changed 📂 Can be specified multiple times.
  • --changed-only, --no-changed-only — only search for tests for changed files (Requires a coverage data source, also requires a list of changes either from the --changed option, or a plugin that implements changed_files() or changed_diff()) 🎯
  • --changes-diff path/to/diff.diff, --no-changes-diff — path to a diff file that should be used to find changed files for use with --changed-only. This must be in the same format as git diff -W --minimal -U1000000 🧾
  • --changes-exclude-file path/to/file, --no-changes-exclude-file — specify one or more files to ignore when looking at changes 🚮 Can be specified multiple times.
  • --changes-exclude-loads, --no-changes-exclude-loads — exclude coverage tests which only load changed files, but never call code from them. (default: off) 📦
  • --changes-exclude-nonsub, --no-changes-exclude-nonsub — exclude changes outside of subroutines (perl files only) (default: off) 📛
  • --changes-exclude-opens, --no-changes-exclude-opens — exclude coverage tests which only open() changed files, but never call code from them. (default: off) 🪟
  • --changes-exclude-pattern '(apple|pear|orange)', --no-changes-exclude-pattern — ignore files matching this pattern when looking for changes. Your pattern will be inserted unmodified into a $file =~ m/$pattern/ check 🍎 Can be specified multiple times.
  • --changes-filter-file path/to/file, --no-changes-filter-file — specify one or more files to check for changes. Changes to other files will be ignored 🔬 Can be specified multiple times.
  • --changes-filter-pattern '(apple|pear|orange)', --no-changes-filter-pattern — specify a pattern for change checking. When only running tests for changed files this will limit which files are checked for changes. Only files that match this pattern will be checked. Your pattern will be inserted unmodified into a $file =~ m/$pattern/ check 🍐 Can be specified multiple times.
  • --changes-include-whitespace, --no-changes-include-whitespace — include changed lines that are whitespace only (default: off) 🌬️
  • --changes-plugin Git, --changes-plugin +App::Yath::Plugin::Git, --no-changes-plugin — what plugin should be used to detect changed files 🧙
  • --default-at-search ARG, --default-at-search=ARG, --no-default-at-search — specify the default file/dir search when 'AUTHOR_TESTING' is set. Defaults to ./xt. The default AT search is only used if no files were specified at the command line 🔎 Can be specified multiple times.
  • --default-search ARG, --default-search=ARG, --no-default-search — specify the default file/dir search. defaults to ./t, ./t2, and test.pl. The default search is only used if no files were specified at the command line 🔍 Can be specified multiple times.
  • --durations file.json, --durations http://example.com/durations.json, --no-durations — Point at a json file or a url that's got a hash where the keys are relative test filenames and the values are 'SHORT', 'MEDIUM', or 'LONG'. This overrides the durations that are listed in the file headers. Heads up though: if the durations file or url doesn't work, an exception gets thrown. No silent fails, bestie. 💀
  • --durations-threshold ARG, --durations-threshold=ARG, --Dt ARG, --Dt=ARG, --no-durations-threshold — Only go fetch the duration data if you're running at least this many tests. Default is (-j value + 1). ✨
  • --exclude-file t/nope.t, --no-exclude-file — Exclude a file from testing. 🚫
    • Can be specified multiple times
  • --exclude-list file.txt, --exclude-list http://example.com/exclusions.txt, --no-exclude-list — Point at a file or url which has a new-line-separated list of test file names to leave out of testing. If a line starts with a # it gets commented out (that's for compatibility with Test2::Aggregate list files, iykyk). 💅
    • Can be specified multiple times
  • --exclude-pattern t/nope.t, --no-exclude-pattern — Exclude a pattern from testing — it gets matched using m/$PATTERN/. 🎀
    • Can be specified multiple times
  • --extension ARG, --extension=ARG, --ext ARG, --ext=ARG, --no-extension — Tell it which test filename extensions are valid. Default: t and t2. 🌸
    • Can be specified multiple times
  • --maybe-durations file.json, --maybe-durations http://example.com/durations.json, --no-maybe-durations — Point at a json file or url with a hash of relative test filenames as keys and 'SHORT', 'MEDIUM', or 'LONG' as values. This overrides the durations listed in the file headers. And same as above: an exception will be thrown if the durations file or url does not work. 🦋
  • --no-long, --no-no-long — Do not run tests that have their duration flag set to 'LONG'. periodt.
  • --only-long, --no-only-long — Only run tests that have their duration flag set to 'LONG'. 👑
  • --rerun, --rerun=path/to/log.jsonl, --rerun=plugin_specific_string, --no-rerun — Re-run tests from a previous run, pulled from a log file (or the last log file). Plugins can intercept this — like YathUIDB, which will grab a run UUID and derive the tests to re-run from that. 🔥
  • --rerun-all, --rerun-all=path/to/log.jsonl, --rerun-all=plugin_specific_string, --no-rerun-all — Re-run all the tests from a previous run, from a log file (or the last log file). Plugins can intercept this too, such as YathUIDB, which grabs a run UUID and derives the tests to re-run from that. ✨
  • --rerun-failed, --rerun-failed=path/to/log.jsonl, --rerun-failed=plugin_specific_string, --no-rerun-failed — Re-run the failed tests from a previous run, from a log file (or the last log file). Again, plugins like YathUIDB can intercept this — they'll grab a run UUID and derive the tests to re-run from it. 😭
  • --rerun-missed, --rerun-missed=path/to/log.jsonl, --rerun-missed=plugin_specific_string, --no-rerun-missed — Run the tests that got missed from a previously aborted/stopped run, from a log file (or the last log file). Plugins can intercept — like YathUIDB, which grabs a run UUID and derives the tests to re-run from that. 🙈
  • --rerun-modes failed,missed,..., --rerun-modes all, --rerun-modes failed, --rerun-modes missed, --rerun-modes passed, --rerun-modes retried, --rerun-mode failed,missed,..., --rerun-mode all, --rerun-mode failed, --rerun-mode missed, --rerun-mode passed, --rerun-mode retried, --no-rerun-modes — Pick which test categories to run. 🎯
    • Can be specified multiple times
  • --rerun-passed, --rerun-passed=path/to/log.jsonl, --rerun-passed=plugin_specific_string, --no-rerun-passed — Re-run the passed tests from a previous run, from a log file (or the last log file). Plugins can intercept, such as YathUIDB, which grabs a run UUID and derives the tests to re-run from that. 💖
  • --rerun-plugin Foo, --rerun-plugin +App::Yath::Plugin::Foo, --no-rerun-plugin — Which plugin(s) should be used for rerun. It'll fall back to other plugins if the ones you listed decline the value — this is just used to set an order of priority. 🌈
    • Can be specified multiple times
  • --rerun-retried, --rerun-retried=path/to/log.jsonl, --rerun-retried=plugin_specific_string, --no-rerun-retried — Re-run the retried tests from a previous run, from a log file (or the last log file). Plugins can intercept this — like YathUIDB, grabbing a run UUID and deriving the tests to re-run from that. 🫶
  • --search ARG, --search=ARG, --no-search — A list of tests and test directories to use instead of the default search paths. Usually you can just list these as plain command line arguments without the --search prefix. 🔍
    • Can be specified multiple times
  • --show-changed-files, --no-show-changed-files — Print a list of the changed files, if any are found. 📝

🎀 Formatter Options 🎀

  • --formatter ARG, --formatter=ARG, --no-formatter — NO DESCRIPTION - FIX ME 😭 (yes really, that's literally what it says, not me being lazy)
  • --qvf, --no-qvf — [Q]uiet, but [V]erbose on [F]ailure. Hide all output from tests when they pass — except to say they passed. But if a test fails, then ALL the output from that test gets verbosely output. best of both worlds fr fr. 💅
  • --show-job-end, --no-show-job-end — Show output when a job ends. (Default: on)
  • --show-job-info, --no-show-job-info — Show the job configuration when a job starts. (Default: off, unless -vv)
  • --show-job-launch, --no-show-job-launch — Show output for the start of a job. (Default: off unless -v)
  • --show-run-info, --no-show-run-info — Show the run configuration when a run starts. (Default: off, unless -vv)

🌸 Git Options 🌸

  • --git-change-base master, --git-change-base HEAD^, --git-change-base df22abe4, --no-git-change-base — Find the files changed by all the commits in the current branch from most recent, stopping when a commit is found that's also present in the history of the branch/commit you specified as the change base. 🧚

👑 Help and Debugging 👑

  • --dummy, -d, --no-dummy — Dummy run — do not actually execute anything. 💀
    • Can also be set with the following environment variables: T2_HARNESS_DUMMY
  • --help, -h, --no-help — exit after showing help information.
  • --interactive, -i, --no-interactive — Use interactive mode, 1 test at a time, stdin forwarded to it. 🎮
  • --keep-dirs, --keep_dir, -k, --no-keep-dirs — Do not delete directories when done. Super useful if you wanna go inspect the directories used for various commands. 🔍
  • --procname-prefix ARG, --procname-prefix=ARG, --no-procname-prefix — Add a prefix to all proc names (as seen by ps). 🏷️
  • --summary, --summary=/path/to/summary.json, --no-summary — Write out a summary json file. If no path is provided then 'summary.json' gets used. The .json extension is added automatically if you omit it. 📄

💜 Logging Options 💜

  • --bzip2, --bz2, --bzip2_log, -B, --no-bzip2 — Use bzip2 compression when writing the log. This option implies -L. The .bz2 prefix is added to the log file name for you. 🗜️
  • --gzip, --gz, --gzip_log, -G, --no-gzip — Use gzip compression when writing the log. This option implies -L. The .gz prefix is added to the log file name for you. 🗜️
  • --log, -L, --no-log — Turn on logging. 📝
  • --log-dir ARG, --log-dir=ARG, --no-log-dir — Specify a log directory. Will fall back to the system temp dir.
  • --log-file ARG, --log-file=ARG, -F ARG, -F=ARG, --no-log-file — Specify the name of the log file. This option implies -L. 📁
  • --log-file-format ARG, --log-file-format=ARG, --lff ARG, --lff=ARG, --no-log-file-format — Specify the format for the automatically-generated log files. Overridden by --log-file, if given. This option implies -L. Default: $YATH_LOG_FILE_FORMAT, if that's set, or else "%!P%Y-%m-%d~%H:%M:%S~%!U~%!p.jsonl". This is a string where percent-escape sequences get replaced as per POSIX::strftime. There are also these special escape sequences that get replaced:
    • (%!P : Project name followed by a ~, if a project is defined, otherwise empty string)
    • (%!U : the unique test run ID)
    • (%!p : the process ID)
    • (%!S : the number of seconds since local midnight UTC)
    • Can also be set with the following environment variables: YATH_LOG_FILE_FORMAT, TEST2_HARNESS_LOG_FORMAT

🦋 Notification Options 🦋

  • --notify-email foo@example.com, --no-notify-email — Email the test results to the specified email address(es). 📧
    • Can be specified multiple times
  • --notify-email-fail foo@example.com, --no-notify-email-fail — Email the failing results to the specified email address(es). 😭
    • Can be specified multiple times
  • --notify-email-from foo@example.com, --no-notify-email-from — If any email gets sent, this is who it'll be from. ✉️
  • --notify-email-owner, --no-notify-email-owner — Email the owner of the broken test files upon failure. Add `# HARNESS-META-OWNER foo@example.com` to the top of a test file to give it an owner. 👤
  • --notify-no-batch-email, --no-notify-no-batch-email — Usually owner failures are sent as a single batch at the end of testing. Toggle this to send the failures as they happen. ⚡
  • --notify-no-batch-slack, --no-notify-no-batch-slack — Usually owner failures are sent as a single batch at the end of testing. Toggle this to send the failures as they happen. ⚡
  • --notify-slack '#foo', --notify-slack '@bar', --no-notify-slack — Send results to a slack channel and/or user. 💬
    • Can be specified multiple times
  • --notify-slack-fail '#foo', --notify-slack-fail '@bar', --no-notify-slack-fail — Send the failing results to a slack channel and/or user. 💬
    • Can be specified multiple times
  • --notify-slack-owner, --no-notify-slack-owner — Send slack notifications to the slack channels/users listed in the test meta-data when tests fail. 📢
  • --notify-slack-url https://hooks.slack.com/..., --no-notify-slack-url — Specify an API endpoint for slack webhook integrations. 🔗
  • --notify-text ARG, --notify-text=ARG, --message ARG, --message=ARG, --msg ARG, --msg=ARG, --no-notify-text — Add a custom text snippet to your email/slack notifications. ✍️
  • --notify-text-module ARG, --notify-text-module=ARG, --message_module ARG, --message_module=ARG, --no-notify-text-module — Use the specified module to generate messages for emails and/or slack. 🧩

⭐ Run Options ⭐

  • --author-testing, -A, --no-author-testing — flips the AUTHOR_TESTING environment variable to true. bestie your author tests are getting RUN. 💅
  • --dbi-profiling, --no-dbi-profiling — pulls in Test2::Plugin::DBIProfile to gather database profiling data. we're profiling the db, no cap 📊
  • --env-var VAR=VAL, -EVAR=VAL, -E VAR=VAL, --no-env-var — sets environment variables that get set when each test runs.

Can be specified multiple times ✨

  • --event-uuids, --uuids, --no-event-uuids — uses Test2::Plugin::UUID inside tests (default: on). literally every event gets its own little serial number 🎀
  • --fields name:details, --fields JSON_STRING, -f name:details, -f JSON_STRING, --no-fields — adds custom data to the harness run.

Can be specified multiple times 💖

  • --input ARG, --input=ARG, --no-input — an input string used as standard input for ALL the tests. see also: --input-file 👀
  • --input-file ARG, --input-file=ARG, --no-input-file — uses the file you name as standard input to ALL the tests 📄
  • --io-events, --no-io-events — uses Test2::Plugin::IOEvents inside tests so that every print becomes a test2 event (default: off). turning prints into events is lowkey iconic 🦋
  • --link 'https://travis.work/builds/42', --link 'https://jenkins.work/job/42', --link 'https://buildbot.work/builders/foo/builds/42', --no-link — give one or more links that people can follow to see more about this run.

Can be specified multiple times 🌈

  • --load ARG, --load=ARG, --load-module ARG, --load-module=ARG, -m ARG, -m=ARG, --no-load — loads a module in each test (after fork). the import method does not get called.

Can be specified multiple times 🧚

  • --load-import Module, --load-import Module=import_arg1,arg2,..., --loadim Module, --loadim Module=import_arg1,arg2,..., -M Module, -M Module=import_arg1,arg2,..., --no-load-import — loads a module in each test (after fork). here, import is called.

Can be specified multiple times. If the same key is listed multiple times the value lists will be appended together. 💜

  • --mem-usage, --no-mem-usage — uses Test2::Plugin::MemUsage inside tests (default: on). watching the memory go brrr 🍓
  • --retry ARG, --retry=ARG, -r ARG, -r=ARG, --no-retry — reruns any jobs that failed, a second time. NOTE: --retry=1 means failing tests will be attempted twice! not me double-checking the math on that one 😭
  • --retry-isolated, --retry-iso, --no-retry-isolated — if true, then any job retries get done in isolation (as though -j1 was set).
  • --run-id, --id, --no-run-id — sets a specific run-id. (Default: a UUID)
  • --test-args ARG, --test-args=ARG, --no-test-args — arguments to pass in as @ARGV for all the tests that run. these are easier to provide using the :: argument separator.

Can be specified multiple times ⭐

  • --stream, --no-stream — uses the stream formatter (default is on) 🌊
  • --tap, --TAP, ----no-stream, --no-tap — the TAP format is lossy and clunky. Test2::Harness normally uses a newer streaming format to receive test results. there are old/legacy tests where this causes problems, and in that case setting --TAP or --no-stream can help. 🫶

🌸 YathUI Options 🌸

  • --yathui-api-key ARG, --yathui-api-key=ARG, --no-yathui-api-key — yath-ui API key. this is not necessary if your yath-ui instance is set to single-user 🔑
  • --yathui-coverage, --no-yathui-coverage — polls coverage data from yath-ui to figure out what tests should be run for the files that changed.
  • --yathui-durations, --no-yathui-durations — polls duration data from yath-ui to help order tests efficiently ⏱️
  • --yathui-grace, --no-yathui-grace — normally, if yath cannot connect to yath-ui it throws an error. use this to make it fail gracefully. you get a warning, but things keep going. we love a soft landing 💖
  • --yathui-long-duration 10, --no-yathui-long-duration — minimum duration length (seconds) before a test goes from MEDIUM to LONG.
  • --yathui-medium-duration 5, --no-yathui-medium-duration — minimum duration length (seconds) before a test goes from SHORT to MEDIUM.
  • --yathui-mode summary, --yathui-mode qvf, --yathui-mode qvfd, --yathui-mode complete, --no-yathui-mode — sets the upload mode (default 'qvfd') 🎀
  • --yathui-project ARG, --yathui-project=ARG, --no-yathui-project — the yath-ui project for your test results.
  • --yathui-retry, --no-yathui-retry — how many times to try an operation before giving up.

Can be specified multiple times 🔁

💀 NO CATEGORY - FIX ME 💀

  • --check-reload-state, --no-check-reload-state — aborts the run if there are unfixed reload errors, and shows a confirmation dialogue for unfixed reload warnings. (yes bestie the section heading really does say fix me, we're all just living like this 🙈)

📚 SOURCE 📚

the source code repository for Test2-Harness can be found at http://github.com/Test-More/Test2-Harness/. go star it, it's giving main character energy 👑

🫶 MAINTAINERS 🫶

Chad Granum <exodist@cpan.org>

✨ AUTHORS ✨

Chad Granum <exodist@cpan.org>

Copyright 2026 Chad Granum <exodist7@gmail.com>.

this program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

See http://dev.perl.org/licenses/

and that's a wrap on this gorgeous little manpage, fr fr 💅 this was perl v5.40.1, dated 2026-05-10 — stan the version, stan the date, and go run your tests bestie 🌸💖✨
📦 where this page comes from