proto-verse / anomalyjobs

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

JOBS_NUM initialization skips job 2 on initial install #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install Anomaly Jobs
2. Add a new job

What is the expected output? What do you see instead?

The installation creates Job 1.  The first user-created job should be Job
2.  Instead, the first user-created job ends up being Job 3.

Please provide any additional information below.

In the install, the following line is set:
&JOBS_NUM Job Database <JD>=2

In fact, new jobs increment this number for assignment, so it should be
initialized to 1, not 2.

This is easily fixed by using +jobs/compress after installation. But future
patches should be corrected to display properly.

Original issue reported on code.google.com by widdis@gmail.com on 8 Dec 2009 at 1:00

GoogleCodeExporter commented 9 years ago

Original comment by widdis@gmail.com on 10 Dec 2009 at 7:32

GoogleCodeExporter commented 9 years ago

Original comment by widdis@gmail.com on 10 Dec 2009 at 8:25