depwl9992 / anomalyjobs

Automatically exported from code.google.com/p/anomalyjobs
0 stars 0 forks source link

New Job indicator broken on Penn for never-read jobs #130

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Have someone create a new job with +request, etc.
2. &JOBSN me=1
3. +jobs/new

What is the expected output?
New job included in the list, with * indicator

What do you see instead?
New job is not included, has no * indicator in the full job list

Please use labels and text to provide additional information.
The bug is in %va/FIL_NEW1: 
  gt(dec(get(%0/NUM_COMMENT)),last(grab(get(%0/LIST_READERS),%#|*),|))

The last() returns null if the enactor has never read the job (or executed 
+jobs/update, or a variety of other means of resetting the indicator).  On 
PennMUSH, null is not treated as zero (unless configured to do so with 
@config/set null_eq_zero=Yes) and gt() returns #-1 ARGUMENTS MUST BE NUMBERS.

Original issue reported on code.google.com by widdis@gmail.com on 1 Nov 2010 at 11:17

GoogleCodeExporter commented 9 years ago
Fixed in r364.

Original comment by widdis@gmail.com on 4 Nov 2010 at 8:21