Support #11152
services.scheduler.errorOnFailureToPut should default to true
Description
The lariat-online code broke when it switched over to art v1_17_03 , and I found that to fix it I needed to add the "errorOnFailureToPut" variable to services.scheduler. To see exactly what I did, if you check out lariat-online you can do the following:
git diff 656c7033f2adf26efafdfc482e77aa396b400050 6f158e82bd64962beb725fa69a7265d82a96f4b7 -- daq/lariat-artdaq/tools/fcl/Aggregator1_for_Lariat_1x1x2.fcl
although really, the relevant info here is that I changed
services: { scheduler: { fileMode: NOMERGE } . . .
to
services: { scheduler: { fileMode: NOMERGE errorOnFailureToPut: true } . . .
I realize that this was added as a way to address Issue 7852 ; however, it seems to me that while it's reasonable to allow users whose code doesn't conform to the new requirements to be able to turn off the requirement by setting "errorOnFailureToPut: false", users whose code already conforms to the requirements shouldn't see their code break because of this parameter. Would it be possible to have this variable default to true, without it needing to be set explicitly?
History
#1 Updated by Kyle Knoepfel about 5 years ago
- Status changed from New to Feedback
The services.scheduler.errorOnFailureToPut
flag is set to true
by default for any art
job that uses the standard artapp
executable. I wonder if you're running into the same problem that Eric Flumerfelt ran into a couple weeks ago--see issue #10972-5. Please let us know if your situation is different than the one described there.
#2 Updated by John Freeman about 5 years ago
#3 Updated by Kyle Knoepfel about 5 years ago
- Tracker changed from Feature to Support
- Status changed from Feedback to Closed
- % Done changed from 0 to 100
- SSI Package art added
- SSI Package deleted (
)
Thanks, John. Closed it is.