The GitHub Actions job "Pull Requests" on pekko.git/materializer-default-attributes has failed. Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run: 80f726829089c7b551272978c13bc875660f2260 / PJ Fanning <[email protected]> feat: support default attributes on materializers Motivation: There is no way to create a materializer that applies a set of default attributes (for example a dispatcher, buffer sizes or a supervision strategy) to every stream it materializes; the attributes have to be put on each stream individually, or changed globally via configuration. Modification: - Add `Materializer(contextProvider, defaultAttributes)` / `Materializer.createMaterializer(contextProvider, defaultAttributes)` for actor-context bound materializers. - Add `Materializer(systemProvider, defaultAttributes)` / `Materializer.createMaterializer(systemProvider, defaultAttributes)` for system level materializers, backed by a new internal `SystemMaterializer.createAdditionalSystemMaterializer(Attributes)`. - Add a new internal `MaterializerGuardian.StartMaterializerWithAttributes` message; the existing `StartMaterializer` case object is unchanged. - The given attributes are combined with the configured materializer settings attributes, so attributes set on a stream still take precedence. - Fix the Scaladoc of the Java `createMaterializer(systemProvider)` and mention the new option in the stream basics docs. Result: Users can create materializers whose default attributes apply to all streams they materialize. All changes are additive, no MiMa excludes. Tests: - Not run locally - left to CI; scalafmt applied, stream-tests/Test/headerCreateAll run for the new spec References: None - new materializer factory overloads Report URL: https://github.com/apache/pekko/actions/runs/39879951070 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
