Fix #3813 move auctionEnd events so it always executes when auction completes #3841
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.
Type of change
Description of change
Fixes #3813.
This change was made primarily to ensure that the auctionEnd event will always trigger even if the publisher didn't include a
bidsBackHandler
when making thepbjs.requestBids()
call (as found while looking into the above issue).This change also ensures other actions taken after the auction finishes are always executed (such as calling timed out bidders, firing userSyncs, and changing the auctionStatus).