You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A shared service used by several tasks of a process is rejected at compile time in 5.5: deprecate it instead, reject it in 6.0 #382
Since 5.5, TaskLocatorCompilerPass throws an InvalidArgumentException when the container is compiled if a shared service is referenced by several tasks of the same process. This configuration worked without error in 5.4: all these tasks ran with the same instance, initialized with the options of each task in turn. The change is documented in UPGRADE.md and the fix is simple (shared: false), but rejecting a configuration that worked breaks the applications on a minor update: their container no longer compiles.
Fix in 5.6: trigger a deprecation naming the service, the tasks and the process instead of throwing; reject it in 6.0.
Found during the audit after the 5.5 release (audit-v4-post-release.md#219).
Activity
#382 - Deprecate a shared service used by several tasks of a process …
#382 - Deprecation since 5.6, the next release
#382 - Deprecate a shared service used by several tasks of a process …
#382 - Deprecation since 5.6, the next release
Merge pull request #385 from cleverage/382