[MGNLSCH-35] Contexts available to commands executed by CommandJob don't have access to the repository Created: 11/Jan/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Scheduler
Component/s: None
Affects Version/s: 1.5.4
Fix Version/s: 1.5.x

Type: Bug Priority: Critical
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLSCH-34 Two different contexts available to c... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When a command is executed via the scheduler, i.e by info.magnolia.module.scheduler.CommandJob, its context (passed to execute() or as MgnlContext.getInstance() don't have their repositoryStrategy set, resulting in an ugly NullPointerException.

At the very least, this should not throw an NPE, but a more explicit exception. But I don't see there's a reason for this ? We can't have a user-specific context, but then why not pass the system context, rather than let developers believe they can use the given context, when really they can't ?
(alternatively, if we had a "sudo" type of API, we could go as far as letting the scheduled job use the context of a specific configured user)



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 10:45:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.