Fixes #4250 to backport Composer 2.x functionality into 11.x. #4260
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
|
@aweingarten FYI |
mikemadison13
force-pushed
the
4250
branch
3 times, most recently
from
b0a41e4
to
282a5be
Compare
|
@danepowell i may need some help on this one, I tried bumping to composer 2 (orca failed) and upping the travis memory limit from older methods (which also failed). not sure what to do about composer memory errors at this point. |
This was referenced Oct 16, 2020
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.
Motivation
Fixes #4250
What problem does this solve? Why is it important? What's the context? If this fixes an issue, link to it above.
Adds composer 2.x support for BLT 11.x.
Proposed changes
What does this PR change? How does this impact end users? Are manual or automatic updates required?
see #4144