Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-47395

improve visual cues for cli errors

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 2.8
    • Administration
    • MOODLE_28_STABLE
    • Hide

      read the cli text output in detail every time as a meticulous, often overloaded, moodle systems administrator.

      Show
      read the cli text output in detail every time as a meticulous, often overloaded, moodle systems administrator.
    • Hide

      Test: use cli tools. try to get an error and observe that a biggish unicode 'X' , in red on some systems, appears to indicate to admin that cli has output an error

      example of cli test run using cli_error() call which puts in the visual cue:
      php admin/cli/upgrade.php
      ❌ No upgrade needed for the installed version 2.8dev (Build: 20140918) (2014091800). Thanks for coming anyway!

      Show
      Test: use cli tools. try to get an error and observe that a biggish unicode 'X' , in red on some systems, appears to indicate to admin that cli has output an error example of cli test run using cli_error() call which puts in the visual cue: php admin/cli/upgrade.php ❌ No upgrade needed for the installed version 2.8dev (Build: 20140918) (2014091800). Thanks for coming anyway!

      often cli errors are just text which administrators can easily miss. this aims to put a visual cue into cli_error.

      note: there is no cli api call for cli_ok() or so...

      ps: fwrite(STDERR, "\xF0\x9F\x91\x8E ". $text);

            Unassigned Unassigned
            nebgor Aparup Banerjee
            Damyon Wiese Damyon Wiese
            Sam Hemelryk Sam Hemelryk
            Dan Poltawski Dan Poltawski
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.