Want to follow up on this issue. We did upgrade to 3.6.0.
After pushing a projection that is emitting to the previously created/emited streams we are still getting faulted state.
Was the issue addressed as you mentioned or we should wait for a new release at some point?
Here are some logs from after the upgrade:
[PID:24579:036 2016.05.12 15:31:56.796 ERROR QueuedHandlerAutoRes] Error while processing message EventStore.Projections.Core.Messages.CoreProjectionManagementMessage+Stop in queued handler ‘Projection Core #7’.
System.Exception: Current state is Faulted. Expected states are: LoadStateRequested, StateLoaded, Subscribed, Running, CompletingPhase, PhaseCompleted
at EventStore.Projections.Core.Services.Processing.CoreProjection.EnsureState (State expectedStates) [0x00000] in :0
at EventStore.Projections.Core.Services.Processing.CoreProjection.Stop () [0x00000] in :0
at EventStore.Projections.Core.Services.Processing.ProjectionCoreService.Handle (EventStore.Projections.Core.Messages.Stop message) [0x00000] in :0
at EventStore.Core.Bus.MessageHandler`1[EventStore.Projections.Core.Messages.CoreProjectionManagementMessage+Stop].TryHandle (EventStore.Core.Messaging.Message message) [0x00000] in :0
at EventStore.Core.Bus.InMemoryBus.Publish (EventStore.Core.Messaging.Message message) [0x00000] in :0
at EventStore.Core.Bus.InMemoryBus.Handle (EventStore.Core.Messaging.Message message) [0x00000] in :0
at EventStore.Core.Bus.QueuedHandlerAutoReset.ReadFromQueue (System.Object o) [0x00000] in :0
[PID:24579:028 2016.05.12 15:31:57.253 ERROR ProjectionManager ] The ‘opportunity_feed’ projection faulted due to ‘Multiple projections emitting to the same stream detected. Stream: ‘$projections-opportunity_feed-order’. Last event projection: ‘8’. Emitting projection: ‘20’’