the test test_ray_actor_wrapped_observer in test_ray_executor.py might need some boundary condition to ensure the pipeline has fully executed before checking the length of results. It could explain https://github.com/ssec-jhu/dplutils/actions/runs/7062866758/job/19227624513, which seems to indicate that the pipeline ran through but check might have started before all remote data reolved.
the test
test_ray_actor_wrapped_observerintest_ray_executor.pymight need some boundary condition to ensure the pipeline has fully executed before checking the length of results. It could explain https://github.com/ssec-jhu/dplutils/actions/runs/7062866758/job/19227624513, which seems to indicate that the pipeline ran through but check might have started before all remote data reolved.