var polylines = commitObject
.Flatten()
.Where(b => b is Polyline)
.Cast<Polyline>();
automationContext.AttachResultToObjects(
level: Speckle.Automate.Sdk.Schema.ObjectResultLevel.Info,
category: "Alignments",
objectIds: polylines.Select(x => x.id),
message: "Processed curves");
The automation is working and seems to be finding the objects ( Viewer - Chris’ Second Project - Speckle), but they aren’t being highlighting or isolating in the viewer when I click the dropdown.
…now that I’ve thought about this for more than 2 seconds, I think it’s because the polylines are actually the visualisation of a nurbs curve, and are being filtered out of the viewer? But still, not the expected outcome
Update, I refactored the above to point at the Curves that actually appear in the viewer, and the selection still doesn’t do anything, so I’ll wait for guidance on that.
As an aside, in my digging I also found the docs for Traversing Structured Data | Speckle Docs, which might need a refactor or some extension methods to cope with the new use case of Automate functions (currently it all seems to assume a converter).
Holler coming from the depths of DUI3 (spoiler alert): when bringing in automate results in the connectors, to highlight the “offending” culprits we’ll need their applicationIds as well. Sorry to use the public forum for internal feature request tracking
Neither are surfacing in the UI - from the decompiled code it looks like the CreateNewVersionInProject function is never registering to the automation context that a version has been created?
@jonathon and co, any thoughts on this? I could just be configuring my C# incorrectly but it’d be good to be able to confirm. My expectation based on the docs is creating a commit + context view should make them show up in the UI.
I’ve just pushed a fix for the double status report issue @sanchez, @chris.welch.
Its a forward only fix, so existing double reports wont go away, but on new version push to models, we reset the statuses and once automations completed, you should only see correct result status.
Could you confirm, that its fixed on your models too?
Thanks
Hi Gergő, it’s working properly on both on old and new models for me. It looks like some of the front end is still not responding to the job succeeding however:
Front end bug: the first time I created a new automation in a while, “that’s it, you’ve loaded everything!” popped up before any function in the library had loaded. I couldn’t reproduce this a second time shortly after - it just showed a loading screen and then all the functions as you’d expect.
we sort of know, that there are a few of these subscription related issues in the current setup.
This one we’re probably only going to fix in the automate 1.0 release, since we’re changing most of the underlying api with that effort.
