Releases: jhuckaby/Cronicle
Version 0.2.5
Misc changes in this release:
- Added filtering and keyword search to Upcoming Events on Home tab.
- Client-side Socket.IO fixes (better handling for lost connections).
- Fixed percentage display on Job Details page.
- Fixed bug where retry delay controls were clickable even if invisible.
- Removed error when adding servers with bad clocks.
- Added optional
log_expire_days
property which can be outputted into job JSON. - Updated copyright on page footer, added link to Cronicle home.
Version 0.2.4
Minor bug fixes / improvements:
- FontAwesome 4.6.x introduced a new subdirectory in their fonts directory which caused some confusion in the Cronicle installer script. Fixed.
- No longer using the
fs.exists
/fs.existsSync
Node core functions, as they have been deprecated.
Version 0.2.3
Single critical bug fix in this release:
- Fixed bug where file handles to job logs would remain open after delete, causing the disk to eventually run out of space.
Version 0.2.2
This version has a new flat UI design, for a more modern look. Now using Lato from Google Fonts.
Version 0.2.1
Minor release, just a bug fix:
- Fixed bug where "Run Again" button could sometimes freeze up UI if job completed immediately.
Version 0.2.0
This version includes Custom Data Tables and Custom HTML Content on the Job Details page, generated from JSON data emitted by your custom Plugin code.
Version 0.1.9
A few small misc fixes in this release:
- No longer auto-displaying logs over 10 MB on Job Details page, unless user asks for it (threshold is configurable).
- Fixed bug when sending e-mails about jobs which failed to launch (now tracking which events launched per minute tick).
- Unit test now runs on HTTP port 4012, and UDP port 4014, as to not interfere with other servers in a cluster which may be using the default ports (3012 / 3014).
Version 0.1.8
Cronicle will now use streams when managing its log files, as to reduce memory usage. Log files are no longer loaded into memory under any circumstances. However, please note that Node.js uses rather large internal stream buffers, up to 200 MB RAM or so. This is "normal".
Some misc. other bug fixes and tweaks:
- Bug fix: Upcoming event countdown time was based on client's local clock, not server clock.
- Bug fix: Prevent flickering on pagination click on certain pages.
- Text change in dialog: "Waiting for master server..."
- Cosmetic fix for table pagination white-space wrap.
- Cosmetic hack for "day" to "days" in server uptime display.
- New versions of pixl-request, pixl-server-web, and pixl-server-storage.
Version 0.1.7
Minor release, just fixed a race condition dealing with appending to log files.
On some OSes (CentOS 6.x for example), writing to log files with fs.appendFile()
and no callback results in out-of-order lines. Switched to fs.appendFileSync()
.
Version 0.1.6
Changes in this release:
- Fixed memory leaks with Node v0.12 (with new pixl-server 1.0.3)
- Fixed race condition where shell/detached processes may close STDIN before job can be written to it, resulting in an EPIPE error.
- Fixed rare situation in UI Home tab where jobs may be rendered before supporting data is available.
- Fixed issue where state data was getting polluted with user IP address / header data.
- Now including
process.argv
in startup debug message. - Now including
process.memoryUsage()
in GC debug messages. - More misc. memory leaks plugged (using
async.ensureAsync()
instead ofprocess.nextTick()
). - Removed
--color
flag in CLI debug mode by default (can be added by user on CLI)