Skip to content

Releases: Poikilos/outputinspector

Double-click the path even if hidden behind an ellipsis!

14 Mar 01:32
Compare
Choose a tag to compare

Example of feature above:

Minetest Lua tracebacks

Output Inspector un-mangles paths with an ellipsis!

2020-03-13 03:15:17: ERROR[Main]: ServerError: AsyncErr: environment_Step: Runtime error from mod 'unified_foods' in callback environment_Step(): ...../gameshunger.lua:342: attempt to compare number with nil
2020-03-13 03:15:17: ERROR[Main]:       ...../games/ENLIVEN/mods/coderfood/unified_foods/hunger.lua:342: in function <...../games/ENLIVEN/mods/coderfood/unif

*.../dir becomes ../dir, resulting in a path such as:
../games/ENLIVEN/mods/coderfood/unified_foods/hunger.lua (this will
work if you run outputinspector from the same directory as the program
you ran. If the path exists in . then the path will also be
transformed correctly to something like
games/ENLIVEN/mods/coderfood/unified_foods/hunger.lua.

If you installed the binary version of 1.1.0, 1.2.0, or 1.3.0, you may have to upgrade to get new features starting at one of those releases. Due to changes to Qt Creator, it changed the build location so I may have uploaded old versions.

Changelog

Added

  • a description (PARSE_DESCRIPTION) in the syntax def
  • unmangledPath (remove ellipsis!) resolves #5
  • Show a warning regarding deprecated settings (show what value was used).

Changed

  • Document the new settings file path correctly (in documents and
    message(s) shown at run-time).
  • Rename variable from kate to editor as of
    d19bd00
  • Copy the old kate variable to the new editor variable.
  • Rename config object to settings.
  • Clarify names of transient variables.
  • Improve formatting in readme.md.
  • Place the configuration into a separate class (See settings.h and
    settings.cpp).
  • Move globals into classes.
  • Rename variables.
  • Move jshint parsing to a unified parsing def.
  • Change settings path from /etc/outputinspector.conf to
    $HOME/.local/share/outputinspector/settings.txt
  • Reduce double-click warnings (such as for missing file) to one line.
  • Prepend "[outputinspector]" to output such as warnings.

Removed

  • Delete previously-commented code in DoubleClicked event.

Accept standard input such as via the pipe character!

13 Mar 07:56
Compare
Choose a tag to compare

This version also improves the linux install script so that you can use it without being root. The install script is not necessary if you use the web install instructions in the Web Install section of readme.md

Added

  • Accept standard input such as by piping from another program!
  • Run the script as a user not named "root" to install to use the
    prefix ~/.local (if the PREFIX environment variable is not
    specified)

Changed

  • If any standard input is waiting, change dialog behavior. Instead of
    showing dialog boxes that interrupt init (in the case of a missing
    input file), show lines in the window.
  • Move old known issues from readme.md to the issue tracker.
    • The "allow param for directory" issue is now a part of issue #5
    • Any not added to the issue tracker were already resolved.

Add support for Minetest Lua Warnings.

13 Mar 01:36
Compare
Choose a tag to compare

This version supports warnings such as:

2020-03-12 15:58:20: WARNING[Server]: Undeclared global variable "default_model_def" accessed at ...n/../games/ENLIVEN/mods/codercore/tsm_pyramids/mummy.lua:63
2020-03-12 15:58:20: WARNING[Server]: Assignment to undeclared global "visual" inside a function at ...n/../games/ENLIVEN/mods/codercore/tsm_pyramids/mummy.lua:63.
2020-03-12 15:58:20: WARNING[Server]: Assignment to undeclared global "prop" inside a function at ...n/../games/ENLIVEN/mods/codercore/tsm_pyramids/mummy.lua:70.

Minetest examples:

./minetest >& err.txt
# running without a param looks for err.txt
outputinspector &

# example 2:
outputinspector ~/.minetest/debug.txt &

You can also use it with grep!

# example 3:
# ogrep "setting" -r ~/minetest/games/Bucket_Game/mods
  • See new non-root install instructions in the "Release Web Install" section in readme.md.

Known Issues

  • The above syntax would only work in cases where the paths are not truncated. See issue #5: "Automatically fix paths that contain elipses".

Added

  • Handle Minetest Lua Warnings.
  • Add Qt-style doxygen strings for constants pointing to parsing markers
    and their values.

You can process many more log types now!

12 Mar 23:56
Compare
Choose a tag to compare

Changes since last release:

[git] - 2020-03-12

Added

  • Handle Minetest Lua tracebacks (such as from debug.txt or stderr)
    (requires fix below)

Fixed

  • Handle PARSE_MARKER_FILE value not at the start of a line.

[git] - 2020-03-11

Added

  • Allow simpler syntax while avoiding false positives by only allowing
    the param opener when it is followed by a digit.
    • Detect grep output syntax.
    • Detect nose test output syntax without hard-coded split(":").

[git] - 2019-12-27

Changed

  • Fix pycodestyle support.
  • Improve changelog formatting and grammar.

[git] - 2019-01-11

Changed

  • Make parsing modes into modular, expandable datasets.
  • Use clang-format for coding style.

[git] - 2018-01-11

Added

  • Support nosetests output.

[git] - 2018-08-15

Changed

  • Warn if input file is missing or has only blank lines.
  • Allow a param to specify output (continue to use err.txt as default).

First GitHub Release!

10 Nov 21:48
Compare
Choose a tag to compare

This release has 2 main advantages over the previous release (on sourceforge):

  • processes jshint output (may work with other node.js code quality tools) -- still also works with mcs-style errors, warnings, and TODOs though
  • install script uses /usr/local/bin which is proper for client-side non-os software on GNU/Linux systems

It also has the following 2 necessary changes in order for it to work on modern operating system configurations, that were made along the way this year when the project was revived:

  • Uses Qt5
  • Uses kate if found in different locations than expected (now is detected with command -v during install)

See README.md at (https://github.com/expertmm/outputinspector) for details on what the output of your compiler or code quality tool must be in order for outputinspector to work.

Changes since sourceforge version

(see README.md for more details):

  • (2017-11-09) mechanism to detect and show fatal errors (with an explanation that your tool recorded them before outputinspector started, to avoid any confusion)
  • (2017-11-09) drastically improved install script (detects and warns if can't manipulate existing install in any way, and installs to /usr/local/bin instead of /usr/bin)
  • (2017-03-25) migrated from qt4 to qt5
  • (2017-03-25) moved from sourceforge to GitHub

Downloads below

  • the file named outputinspector is a binary for linux. It was compiled using:
    • Qt Creator on Antergos, qmake version (according to qmake --version) : "QMake version 3.1 Using Qt version 5.9.2"
    • gcc (output from gcc --version): 7.2.0
    • Kernel (output from uname -a): 4.13.11-1-ARCH #1 SMP PREEMPT Thu Nov 2 10:25:56 CET 2017 x86_64 GNU/Linux