UnitOfWork.FindGroup() and EntityTuple not respecting aggregates in a join

Hi

I have a join

        var query = new Query(typeof(EntityOne));
        query.Join = Join.Inner<EntityOne, EntityTwo>("Id", "Id");
        query.AggregateName = filter.Aggregate;

Both EntityOne and EntityTwo have their own properties that should be eager loaded through the aggregate.

If I do:

        var res = new EntityTuple<EntityOne, EntityTwo>();
        UnitOfWork.FindGroup(query, res);
       //items in res don't have eager loaded properties

Neither of them has the properties specified in the aggregate eager loaded. I can see the SQL being issued actually sends a SQL query including the aggregates relevant for EntityOne, but doesn't hydrate entity properties (and the generated SQL completely omitted aggregates for EntityTwo).

On the contrary, if I don't use the tuple and just load each of the entities collection separately, they get eager loaded correctly. Like this:

       var plRsult = UnitOfWork.Find<EntityOne>(query);
       var tRsult = UnitOfWork.Find<EntityTwo>(query);
       //items in both collections have eager loaded properties

In this case 1st query gets EntityOnes with its aggregates, and 2nd query gets EntityTwo with its aggregates (and in both cases off the initial join).

That's a bug, isn't it?

Yes this sounds incorrect, the eager load should be applied in this situation. I have set up an equivalent scenario here with the code above and the eager loading is working correctly for me - are you able to send through a small repro project (ConsoleApplication or UnitTest) which I can use to reproduce this behavior and I can have a look into this for you. Also which version of LightSpeed are you using? Are you able to retry this with a current nightly build if you are not using this already?

Thanks!
Jeremy