v.1.6.10 - Rollup Conductor tweaks #554
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
jamessimone
commented
Jan 12, 2024
jamessimone
commented
- Fixes RollupAsyncProcessor is creating a second queueable job per apex invocation #551 by tweaking logic and docs for how batch/queueable apex is used to start up the async portion of Apex Rollup
… used to start up the async portion of Apex Rollup
Bumps [@salesforce/sfdx-scanner](https://github.com/forcedotcom/sfdx-scanner) from 3.19.0 to 3.20.0. - [Release notes](https://github.com/forcedotcom/sfdx-scanner/releases) - [Commits](forcedotcom/sfdx-scanner@v3.19.0...v3.20.0) --- updated-dependencies: - dependency-name: "@salesforce/sfdx-scanner" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…r starting up Apex Rollup, as that particular batch class is NOT stateful and changes made to it in start() are not persisted in finish() - to get around this, when apex rollup is started up async but the only processors included are themselves full recalc operations, the start() method now conditionally checks to see if it needs to do a one-time match on Organization, which allows the full recalc processors to be properly invoked within the execute() method (instead of skipping straight from start() to finish() due to all of the full recalc processors being winnowed out)
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #554 +/- ##
==========================================
+ Coverage 96.53% 96.60% +0.07%
==========================================
Files 32 32
Lines 6720 6725 +5
Branches 61 61
==========================================
+ Hits 6487 6497 +10
+ Misses 228 223 -5
Partials 5 5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.