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

📦
version 1.000172 · 8 versions
, in ubuntu stonking

💖 App::Yath::Command::status 💖

okay so real quick, before we dive in — this page is filed under App::Y...status(3pm), which is the fancy manual-name for App::Yath::Command::status, and it lives in the User Contributed Perl Documentation corner of the 3pm section. That's the whole header, we're done with the boring part, let's go 🫶

🌸 NAME 🌸

App::Yath::Command::status — Status info and process lists for the runner

✨ DESCRIPTION ✨

This command hands you the health details and a full process list for the runner. Like a vibe check but for your test runner, no cap. 💅

🦋 USAGE 🦋

$ yath [YATH OPTIONS] status [COMMAND OPTIONS]

👑 YATH OPTIONS 👑

🛠️ Developer

  • --dev-lib, --dev-lib=lib, -D, -D=lib, -Dlib, --no-dev-lib — Adds paths to @INC before loading ANYTHING. This is the one you reach for when you're developing yath or yath plugins, because it makes sure the yath script finds your local code instead of the installed versions of that same code. You can pass an argument (-Dfoo) to give a custom path, or just rawdog -D with no arg to add 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 defaults to /tmp/yath-persist.json — which limits you to one persistent runner on your system. One. Single. Runner. 😭
  • --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 (iykyk).

🆘 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 in order to bring in command-line options they may provide. This flag disables that. Super useful if you have a naughty plugin that is loading other modules when it should not, and we do not stan that behaviour 🚫
  • --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. (bestie, I'm not gatekeeping, the docs literally say that 💀)

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). Yes, 4%. Basically free. Obsessed.
  • --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.

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 this at a json file or a url holding a hash where the keys are relative test filenames and the values are 'SHORT', 'MEDIUM', or 'LONG' ✨ It overrides the durations listed up in the file headers. If that durations file or url doesn't work? an exception gets thrown, no hesitation, no mercy 💅
  • --durations-threshold ARG, --durations-threshold=ARG, --Dt ARG, --Dt=ARG, --no-durations-threshold — only bother fetching 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. You can say it multiple times 🫶
  • --exclude-list file.txt, --exclude-list http://example.com/exclusions.txt, --no-exclude-list — point at a file or url with a newline separated list of test file names to exclude. Start a line with a # and it gets commented out (for compatibility with Test2::Aggregate list files, cute). Also repeatable as many times as your heart desires ✨
  • --exclude-pattern t/nope.t, --no-exclude-pattern — exclude a pattern, matched using m/$PATTERN/. Repeatable, multiple times, go off 💅
  • --extension ARG, --extension=ARG, --ext ARG, --ext=ARG, --no-extension — tell it which test filename extensions are valid. Default: t and t2 🎀 Repeatable.
  • --maybe-durations file.json, --maybe-durations http://example.com/durations.json, --no-maybe-durations — literally the same vibe as --durations: a json file or url with a hash of relative test filenames as keys and 'SHORT', 'MEDIUM', or 'LONG' as values, overriding the durations in the file headers. And yeah, if the file or url doesn't work, an exception gets thrown 🌈
  • --no-long, --no-no-long — do NOT run tests that have their duration flag set to 'LONG' 🙅‍♀️
  • --only-long, --no-only-long — ONLY run the tests whose duration flag is 'LONG' 👑
  • --rerun, --rerun=path/to/log.jsonl, --rerun=plugin_specific_string, --no-rerun — re-run tests from a previous run, from a log file (or the last log file). Plugins can intercept this, like YathUIDB, which grabs a run UUID and derives 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). Same plugin intercept situation: YathUIDB can grab a run UUID and derive tests to re-run from it 💖
  • --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). Plugins can intercept, e.g. YathUIDB grabbing a run UUID and deriving tests to re-run from that 😭
  • --rerun-missed, --rerun-missed=path/to/log.jsonl, --rerun-missed=plugin_specific_string, --no-rerun-missed — run the missed tests from a previously aborted/stopped run, from a log file (or the last log file). Yep, plugins can intercept — YathUIDB, run UUID, derives tests to re-run, you know the drill 💀
  • --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 🎯 Repeatable, 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 this, such as YathUIDB, grabbing a run UUID and deriving tests to re-run from it 🦋
  • --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 listed ones decline the value; this is just used to set an order of priority 👑 Repeatable, 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 it, like YathUIDB, which will grab a run UUID and derive 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. Repeatable, multiple times 🌸
  • --show-changed-files, --no-show-changed-files — print out a list of changed files, if any get found 👀

🎀 Formatter Options 🎀

  • --formatter ARG, --formatter=ARG, --no-formatter — NO DESCRIPTION - FIX ME 🙈 (I'm not making anything up, bestie, the docs literally say that.)
  • --qvf, --no-qvf — [Q]uiet, but [V]erbose on [F]ailure 💅 Hide all output from tests when they pass, except for saying they passed. But if a test fails? ALL output from the test gets verbosely dumped out. Iconic.
  • --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 commits on the current branch, from most recent, stopping when you hit a commit that's also present in the history of the branch/commit you named as the change base 🔍

🛠️ Help and Debugging 🛠️

  • --dummy, -d, --no-dummy — a dummy run, it does 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, with stdin forwarded to it 🎧
  • --keep-dirs, --keep_dir, -k, --no-keep-dirs — do not delete directories when you're done. Super useful if you want to go inspect the directories used for the 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 you don't give a path, '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 implies -L too. And the .gz prefix gets 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. It'll fall back to the system temp dir if needed 📁
  • --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. It gets overridden by --log-file, if you gave one. 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. These special escape sequences also get replaced: (%!P : project name followed by a ~, if a project is defined, otherwise an 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 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 — normally owner failures get sent as a single batch at the end of testing. Toggle this to send failures as they happen, live, no chill 😤
  • --notify-no-batch-slack, --no-notify-no-batch-slack — same thing but for slack: usually owner failures are one batch at the end of testing. Toggle it and they go out 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 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 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 — this one sets the AUTHOR_TESTING environment to true, so the author-only bits wake up and stretch 🫶
  • --dbi-profiling, --no-dbi-profiling — pulls in Test2::Plugin::DBIProfile to gather up database profiling data, because we love receipts ✨
  • --env-var VAR=VAL, -EVAR=VAL, -E VAR=VAL, --no-env-var — sets environment variables that get set whenever each test runs. Can be specified multiple times, so stack those babies up 💅
  • --event-uuids, --uuids, --no-event-uuids — uses Test2::Plugin::UUID inside tests (default: on) 🌸
  • --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, go off 🎀
  • --input ARG, --input=ARG, --no-input — the input string that gets used as standard input for ALL tests. See also: --input-file 👑
  • --input-file ARG, --input-file=ARG, --no-input-file — uses the file you name as standard input for ALL tests 📄
  • --io-events, --no-io-events — uses Test2::Plugin::IOEvents inside tests so every single print turns into a test2 event (default: off) 🔥
  • --link 'https://travis.work/builds/42', --link 'https://jenkins.work/job/42', --link 'https://buildbot.work/builders/foo/builds/42', --no-link — gives people one or more links they can follow to see more about this run. Can be specified multiple times, share the lore 🔗
  • --load ARG, --load=ARG, --load-module ARG, --load-module=ARG, -m ARG, -m=ARG, --no-load — loads a module in each test (after fork). Heads up bestie, the "import" method is NOT 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), and this time Import is called. Can be specified multiple times. If the same key shows up multiple times, the value lists get appended together 🦋
  • --mem-usage, --no-mem-usage — uses Test2::Plugin::MemUsage inside tests (default: on) 💜
  • --retry ARG, --retry=ARG, -r ARG, -r=ARG, --no-retry — runs any jobs that failed a second time. NOTE: --retry=1 means failing tests will be attempted twice! not me doing the math on that 😭
  • --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 tests that are run. You can hand these over easier 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 — so like, 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. (and yes, that flag is literally written ----no-stream with four dashes, that's not me being chaotic, that's the actual page 💀)

🎀 YathUI Options 🎀

  • --yathui-api-key ARG, --yathui-api-key=ARG, --no-yathui-api-key — your Yath-UI API key. 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 which 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 can't connect to yath-ui it throws an error. Use this to make it fail gracefully instead. You still get a warning, but things keep going 🫶
  • --yathui-long-duration 10, --no-yathui-long-duration — minimum duration length, in seconds, before a test goes from MEDIUM to LONG 📏
  • --yathui-medium-duration 5, --no-yathui-medium-duration — minimum duration length, in 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 your test results belong to 🗂️
  • --yathui-retry, --no-yathui-retry — how many times to try an operation before giving up. Can be specified multiple times 🔁
  • --yathui-upload, --no-yathui-upload — uploads the log to Yath-UI ☁️
  • --yathui-url http://my-yath-ui.com/..., --uri http://my-yath-ui.com/..., --no-yathui-url — Yath-UI url 🌐

💀 NO CATEGORY - FIX ME 💀

  • --check-reload-state, --no-check-reload-state — aborts the run if there are unfixes reload errors, and pops up a confirmation dialogue for unfixed reload warnings 🚨

📚 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 open source excellence ⭐

👑 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/

okay that's literally the whole page bestie, you made it to the end 🎉 this was written up by the Perl documentation crew, perl v5.40.1, dated 2026-05-10, and it's the App::Y...status(3pm) page — now go forth and run your tests, no cap 💖✨

📦 where this page comes from