Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions crates/bevy_ecs/src/schedule/schedule.rs
Original file line number Diff line number Diff line change
Expand Up @@ -415,6 +415,11 @@ impl Schedule {
this
}

/// Returns whether this schedule has been changed since the last time it was built.
pub fn is_changed(&self) -> bool {
self.graph.changed
}

/// Returns the [`InternedScheduleLabel`] for this `Schedule`,
/// corresponding to the [`ScheduleLabel`] this schedule was created with.
pub fn label(&self) -> InternedScheduleLabel {
Expand Down
91 changes: 81 additions & 10 deletions crates/bevy_remote/src/builtin_methods.rs
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ use crate::{
json_schema::{export_type, JsonSchemaBevyType},
open_rpc::OpenRpcDocument,
},
BrpError, BrpResult,
BrpError, BrpResult, PreviousScheduleBuildMetadata,
};

#[cfg(all(feature = "http", not(target_family = "wasm")))]
Expand Down Expand Up @@ -1613,7 +1613,7 @@ pub fn schedule_graph(In(params): In<Option<Value>>, world: &mut World) -> BrpRe

let schedules = world.resource::<Schedules>();

let Some((label, schedule)) = schedules
let Some((_, mut schedule)) = schedules
.iter()
.find(|(label, _schedule)| format!("{:?}", label) == schedule_label)
else {
Expand All @@ -1622,10 +1622,33 @@ pub fn schedule_graph(In(params): In<Option<Value>>, world: &mut World) -> BrpRe
schedule_label
)));
};
// Get the interned label.
let label = schedule.label();

if schedule.is_changed() {
match world.schedule_scope(label, |world, schedule| schedule.initialize(world)) {
Ok(build_metadata) => {
assert!(build_metadata.is_some());
}
Err(err) => {
return Err(BrpError::internal(format!(
"Failed to initialize schedule with label={label:?}: {err}"
)))
}
}
// Note: we don't need to insert into the `PreviousScheduleBuildMetadata`, since the
// metadata caching observer already does that for us.

schedule = world.resource::<Schedules>().get(label).unwrap();
}

let metadata = world
.get_resource::<PreviousScheduleBuildMetadata>()
.and_then(|res| res.0.get(&label));

// TODO: We should consider saving all the `ScheduleBuilt` events when BRP is enabled, and
// looking it up here (or even building the schedule here to get the metadata to fill it in).
let schedule_data = match ScheduleData::from_schedule(schedule, world.components(), None) {
let schedule_data = match ScheduleData::from_schedule(schedule, world.components(), metadata) {
Ok(schedule_data) => schedule_data,
Err(err) => {
return Err(BrpError::internal(format!(
Expand Down Expand Up @@ -1883,7 +1906,10 @@ mod tests {
}

use super::*;
use crate::schemas::json_schema::{ComponentMetadata, RelationshipKind, StorageKind};
use crate::{
cache_schedule_build_metadata,
schemas::json_schema::{ComponentMetadata, RelationshipKind, StorageKind},
};
use bevy_ecs::{
component::Component,
event::Event,
Expand Down Expand Up @@ -2141,7 +2167,7 @@ mod tests {
}

#[test]
fn test_schedule_graph() {
fn schedule_graph_for_uninitialized_schedule() {
#[derive(Resource)]
struct Resource1;

Expand All @@ -2168,10 +2194,13 @@ mod tests {
schedule.add_systems(f4.in_set(S2).after(S1));

let mut world = World::default();

let _ = schedule.initialize(&mut world);
world.add_schedule(schedule);

// Normally, this is done by the `RemotePlugin`, but we don't actually want to start a
// server here, so just manually init these.
world.init_resource::<PreviousScheduleBuildMetadata>();
world.add_observer(cache_schedule_build_metadata);

let params = serde_json::to_value(&BrpScheduleGraphParams {
schedule_label: "MySchedule".to_string(),
})
Expand All @@ -2183,18 +2212,60 @@ mod tests {
// - 5 systems (f1, f2, f3, f4, apply_deferred)
// - 6 system sets (F1, F2, F3, F4, S1, S2)
// - 6 hierarchy edges: F1 -> f1, F2 -> f2, F3 -> f3, F4 -> f4, S1 -> f3, S2 -> f4
// - 2 dependency edges: f1 -> f2, S1 -> f4
// - 4 dependency edges: f1 -> f2, S1 -> f4, f1 -> apply_deferred, apply_deferred -> f2

let res = schedule_graph(In(Some(params)), &mut world);
let res2 = res.expect("expect to work");
let res3 = serde_json::from_value::<BrpScheduleGraphResponse>(res2).unwrap();

assert_eq!(res3.schedule_data.systems.len(), 5,);
assert_eq!(res3.schedule_data.systems.len(), 5);
assert_eq!(res3.schedule_data.system_sets.len(), 6);
assert_eq!(res3.schedule_data.hierarchy.len(), 6);
assert_eq!(res3.schedule_data.dependency.len(), 2);
assert_eq!(res3.schedule_data.dependency.len(), 4);
// Components are only currently recorded for conflicts - this may change in the future.
assert_eq!(res3.schedule_data.components.len(), 0);
assert_eq!(res3.schedule_data.conflicts.len(), 0);
}

#[test]
fn schedule_graph_for_initialized_schedule() {
#[derive(Resource)]
struct Resource1;

fn f1(mut commands: Commands) {
commands.insert_resource(Resource1);
}
fn f2(_r: Res<Resource1>) {}

#[derive(ScheduleLabel, Hash, Clone, PartialEq, Eq, Debug)]
struct MySchedule;

let mut schedule = Schedule::new(MySchedule);

schedule.add_systems((f1, f2).chain());

let mut world = World::default();
world.add_schedule(schedule);

// Normally, this is done by the `RemotePlugin`, but we don't actually want to start a
// server here, so just manually init these.
world.init_resource::<PreviousScheduleBuildMetadata>();
world.add_observer(cache_schedule_build_metadata);

// Initialize the schedule early. Now `schedule_graph` should still report the metadata.
world
.schedule_scope(MySchedule, |world, schedule| schedule.initialize(world))
.unwrap();

let params = serde_json::to_value(&BrpScheduleGraphParams {
schedule_label: "MySchedule".to_string(),
})
.unwrap();

let response = schedule_graph(In(Some(params)), &mut world).unwrap();
let response = serde_json::from_value::<BrpScheduleGraphResponse>(response).unwrap();

// We expect 3 edges thanks to the cached metadata: f1 -> f2, f1 -> apply_deferred -> f2
assert_eq!(response.schedule_data.dependency.len(), 3);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would heavily prefer we asserted that these systems are the systems we expect. I recently ran into a test suite that only used the counts like this in an ecosystem crate and it was more confusing to fix than it needed to be, since the test didn't include which items it expected to exist other than the count.

As an example (anything similar would be fine if you prefer .find or something):

Suggested change
assert_eq!(response.schedule_data.dependency.len(), 3);
assert!(response.schedule_data.systems[0].name.ends_with("f1"));
assert!(response.schedule_data.systems[1]
.name
.ends_with("apply_deferred"));
assert!(response.schedule_data.systems[2].name.ends_with("f2"));
assert_eq!(response.schedule_data.dependency.len(), 3);

}
}
33 changes: 32 additions & 1 deletion crates/bevy_remote/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -539,8 +539,12 @@ use bevy_app::{prelude::*, MainScheduleOrder};
use bevy_derive::{Deref, DerefMut};
use bevy_ecs::{
entity::Entity,
observer::On,
resource::Resource,
schedule::{IntoScheduleConfigs, ScheduleLabel, SystemSet},
schedule::{
InternedScheduleLabel, IntoScheduleConfigs, ScheduleBuildMetadata, ScheduleBuilt,
ScheduleLabel, SystemSet,
},
system::{Commands, In, IntoSystem, ResMut, System, SystemId},
world::World,
};
Expand Down Expand Up @@ -812,6 +816,14 @@ impl Plugin for RemotePlugin {
);
}

if remote_methods
.0
.contains_key(builtin_methods::BRP_SCHEDULE_GRAPH)
{
app.init_resource::<PreviousScheduleBuildMetadata>()
.add_observer(cache_schedule_build_metadata);
}

app.init_schedule(RemoteLast)
.world_mut()
.resource_mut::<MainScheduleOrder>()
Expand Down Expand Up @@ -1450,6 +1462,25 @@ fn remove_closed_watching_requests(mut requests: ResMut<RemoteWatchingRequests>)
}
}

/// Resource tracking the last [`ScheduleBuildMetadata`] of each schedule as it is built.
///
/// This allows the `schedule.graph` endpoint to return better results for schedules.
#[derive(Resource, Default)]
struct PreviousScheduleBuildMetadata(HashMap<InternedScheduleLabel, ScheduleBuildMetadata>);

fn cache_schedule_build_metadata(
event: On<ScheduleBuilt>,
mut metadata: ResMut<PreviousScheduleBuildMetadata>,
) {
let new_metadata = ScheduleBuildMetadata {
// We intentionally don't bother cloning the warnings, since they aren't used by the
// `ScheduleData`.
warnings: vec![],
edges_added_by_build_passes: event.build_metadata.edges_added_by_build_passes.clone(),
};
metadata.0.insert(event.label, new_metadata);
}

#[cfg(test)]
mod tests {
use crate::BrpRequest;
Expand Down