Hey all, here's a set of potentially downstream breaking changes: https://github.com/apache/openwhisk/pull/4736: Note how I changed "| string" to "| lower" in the ansible scripts. Pureconfig seems to be more picky when it comes to Boolean values and only allows "true" and "false" there. Python usually produces "True" and "False", which caused things to break. https://github.com/apache/openwhisk/pull/4749: This updates the akka-management parts of the system which potentially has an impact on setups that use Kubernetes or Mesos API to build the controller cluster.
Am Do., 21. Nov. 2019 um 15:10 Uhr schrieb Carlos Santana < [email protected]>: > Woot +1 > > - Carlos Santana > @csantanapr > > > On Nov 21, 2019, at 5:58 AM, David P Grove <[email protected]> wrote: > > > > > > > > > > "Markus Thömmes" <[email protected]> wrote on 11/21/2019 > 02:03:30 > > AM: > >>> > >>> One thing to be careful of is that many downstream repos (runtime, > >>> providers) depend on the test suite from the core repo. We had a > > couple > >>> rounds of breakage in the last few months where a test suite change got > > a > >>> clean core travis run, but still broke all the downstream repos leading > > to > >>> some hasty fixing and/or reverting. > >>> > >> > >> I hear you! Is there a good way to verify stuff works across all > >> repositories or will I have to manually go through all of them and check > > if > >> my changes have any impact? > >> > >> > > > > Not going to be perfect, but I think all of the breakages we had would > have > > been caught by building even one downstream repo against the modified > core > > since the test suite is used more or less the same way in all the runtime > > repos. > > > > --dave >
