Geminiclose
Gemini Password Reset

Please provide your username.

A password reset confirmation email will be sent to your email address.

Username
  • Projects

 
SCHEDULER-1880 - Broken Plan can trigger old debugging assert
Estimated: 2 Hours 0 Minutes   Logged: 1 Hours 0 Minutes   Time Left: 1 Hours 0 Minutes
Print  |  Send  |  Refresh  |  Url
Type: Bug Bug
Priority: High High
Severity: Minor Minor
Status: Closed Closed
Resolution: Complete
Resources: Bob Denny
Reported By: Bob Denny
Component: Dispatch Scheduler Engine
Fixed In Version: 9.0
Versions Affected: 8.3
Start Date: 2/24/2022
Percent Complete:
Created:  2/16/2022 7:38:14 PM
Revised:
 2/24/2022 4:07:15 PM
Closed:  2/24/2022 4:06:58 PM
Resolved:  2/24/2022 4:07:03 PM

See this Comm Center thread by Stephen Avery. This is unreal. He had a Plan that was broken:

2022-02-16 21:20:44.6: **[efficiency entry] Plan NGC 2403-Red 300s (13-18) has no observations! Returning eff=0

With Rising Plan Delay set. that caused the FinalPlist to be off from the nUsablePlans (Engine.cs @ 3163), and this caused an ancient "assert" check to force a run time error. This should instead log an "unusual condition" at brief level so it's always logged. It should "never happen" anyway. he apparently hand constructed or edited the Plan.