Query<EntityMut> system param unexpectedly conflicts with some Res<T> one

[djeedai]

Bevy version

0.14.2

What you did

pub fn component_animator_system(
    time: Res<Time>,
    events: ResMut<Events<TweenCompleted>>,
    mut q_anim: Query<EntityMut, With<Animator>>,
) {

What went wrong

The component query conflicts with the resources:

bevy_ecs-0.14.2/src/system/system_param.rs:302:5:
error[B0001]: Query<bevy_ecs::world::entity_ref::EntityMut, bevy_ecs::query::filter::With<bevy_tweening::Animator>> in system bevy_tweening::plugin::component_animator_system accesses component(s) bevy_ecs::event::Events<bevy_tweening::tweenable::TweenCompleted>, bevy_time::time::Time in a way that conflicts with a previous system parameter. Consider using `Without<T>` to create disjoint Queries or merging conflicting Queries into a `ParamSet`. See: https://bevyengine.org/learn/errors/#b0001

Asked on #ecs-dev, this looks like an error, as component queries shouldn't conflict with resources.

[djeedai]

Commenting out the ResMut<Events<T>> doesn't change anything. So this is not due to the mutability access of the resource.

[BorisBoutillier]

Minimalist full example reproducing the issue:

use bevy::prelude::*;

fn main() {
    App::new().add_systems(Update, test_system).run();
}

pub fn test_system(time: Res<Time>, mut query: Query<EntityMut>) {}

[alice-i-cecile]

Can you check on main? I remember merging a related fix.

[BorisBoutillier]

I have checked on main my minimal example and it no more report any conflicts.
I'll try to find out the associated PR that fixes this for reference.

[djeedai]

Sorry my bad I didn't think about checking main. 😬

[BorisBoutillier]

This is the same issue as #13139 and this is effectively fixed with the associated PR #14561