Closed ian-kinner closed 1 month ago
@jhuckaby I was trying to impress upon my coworkers how awesome of a dev you appear to be before you turned around a feature request in a couple hours and put out a release. Muchos gracias 🙏
My pleasure -- it was an easy fix 😊 -- thank you for reporting it!
Summary
Long job names are cut off and the source of the running event can't be determined when the part that is shown could be one of many with the same first X characters. It says "Chain Reaction (some long job na)" - this could be "some long job name number 1" or "some long job name number 2"
It would be great to have a mouseover show the entire name, or better yet make this a link to the source job.
Steps to reproduce the problem
Have a job with a long name trigger another job. The second job lists the originating job in a fixed width and cuts off long names.
Your Setup
2 servers, thousands of scheduled jobs running a lot
Operating system and version?
Amazon Linux 2 & Ubuntu
Node.js version?
16.20.2
Cronicle software version?
0.9.40
Are you using a multi-server setup, or just a single server? Multi
Are you using the filesystem as back-end storage, or S3/Couchbase? filesystem
Can you reproduce the crash consistently? Yes
Log Excerpts