Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix analysis mode of scheduling engine #1586

Merged
merged 1 commit into from
Nov 1, 2024
Merged

Conversation

adrienmaillard
Copy link
Contributor

Description

The issue arose in this case

  • conflictSolverReturn was not initialized
  • the analysis mode was ON
  • the type of the conflict was something else than an association conflict so the variable kept being null

Initializing the conflictSolverReturn variable to its default state (unsatisfied, no activities created) fixes that issue and no other logic is impacted.

Verification

None.

Documentation

None.

Future work

None.

@Mythicaeda
Copy link
Contributor

Would you mind quickly explaining why it was null to begin with, if you recall?

@adrienmaillard
Copy link
Contributor Author

An oversight. Probably from before it had a default state via its default constructor.

@mattdailis mattdailis merged commit 8118519 into develop Nov 1, 2024
14 checks passed
@mattdailis mattdailis deleted the fix-analyze-mode branch November 1, 2024 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix A bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Analyze scheduling fails after removing activity from plan
3 participants