Follow up of moving functions out of hlt1_tracking
Follow up of !1443 (merged).
When calling the deprecated functions an exception is thrown. The reason for throwing exceptions over removing the functions is to be able to give users an error message with instructions what to do.
Merge request reports
Activity
added RTA label
- Resolved by Sebastien Ponce
Deprecated normally means the function is still there and can be used but is discouraged pending removal. In this case the functions have moved and users need to adjust immediately. So I'm not sure I see the benefit of this approach compared to removing the code and updating the documentation to reflect what users should be doing. If we stick to this approach could you in parallel open an issue so we remember to eventually remove this code for good?
Also, although I didn't comment on the original MR, in general I would prefer it if we could avoid these kinds of configuration reorganisations over the next months, so we can focus on changing those things which absolutely do have to change to enable datataking and commissioning.
- Resolved by Sebastien Ponce
Also, although I didn't comment on the original MR, in general I would prefer it if we could avoid these kinds of configuration reorganisations over the next months, so we can focus on changing those things which absolutely do have to change to enable datataking and commissioning.
I think the changes in this merge request remove potential confusion, also during the commissioning, in our codebase, especially because it has happened that people were confused by what these functions do. That being said, I don't mind if people decide that merge requests are not necessary and are closed as they don't bring substantial benefit.
mentioned in issue #421 (closed)
mentioned in issue #426 (closed)
mentioned in issue #432 (closed)
- Resolved by Sebastien Ponce
Is this ready to be tested ?
assigned to @fsouzade
added ci-test-triggered label
- [2022-06-08 16:48] Validation started with lhcb-master-mr#4678
mentioned in commit b8b4144d
mentioned in issue #444 (closed)
mentioned in issue #404 (closed)