Ronnie Dutta

I think that is beyond the scope of this bugfix I'm afraid. It's been a couple of weeks since I looked at the code, but I think rose prune only...

@cutlerrickel What do you mean? This is a bug report.

Interesting. I am using Vuetify 3.7.4. But I have not had this problem before with older versions of Vue devtools

I tried upgrading to the latest version of Vue but still encountered the problem

I've tested on 8.3.x and master, and in the networks panel of devtools I see all the prerequisites listed in every update, even if only one of them changed

https://github.com/cylc/cylc-flow/blob/c029d6be35c8f6f4961e6d16150dcd267d1e1aec/cylc/flow/data_store_mgr.py#L1781-L1789 A `PbTaskProxy` was not found in the store despite the task ID being added to `self.all_task_pool` https://github.com/cylc/cylc-flow/blob/c029d6be35c8f6f4961e6d16150dcd267d1e1aec/cylc/flow/data_store_mgr.py#L2651-L2662 Do we have a copy of this workflow?

I had a quick go at reproducing using a copy of the workflow in sim mode; no luck. > A `PbTaskProxy` was not found in the store despite the task...

From #6739 > Another possibility could be to plug in the existing `next()`/`previous()` functionality which can currently only be used in the `initial cycle point` setting. E.g. > ```cylc >...

MacOS failures caused by different functional tests being introduced into the chunk due to the added functional test. Addressed by https://github.com/wxtim/cylc/pull/63

> MacOS failures caused by different functional tests being introduced into the chunk due to the added functional test. Addressed by [wxtim#63](https://github.com/wxtim/cylc/pull/63) Still awaiting