I noticed an issue when using the Grasshopper Synchronous Receiver component. This was quickly discussed with @jonathon and @Nikos in a call last week.
If I set the output mode to “Do Not Convert”, close my definition and re-open it, I get an error saying:
Missing object chunk in archive. An object could not be found in the document,it will be missing once the file is loaded.
When I close the message, my definition opens but the Synchronous Receiver is missing.
See below:
I think the issue might happen in other cases as well, as we seem to have missing receivers after uploading definitions to ShapeDiver, albeit a bit randomly. I will dig further, but the case I am reporting above happens consistently for me.
In case the error is not reproducible, I could find a way to share the data I am importing, or even create a temporary token.
Thanks in advance for any insight about this issue!
Hey @Mathieu_Huard, @Nikos managed to reproduce and we’ll try to have a look. In case you’re on a roll and you get there before us, you know where the source is (this is my way of saying pre-holiday stuff is busy/clogged and we might get to it in early jan…)
Thanks for the heads-up @dimitrie! As much as I’d love to issue a PR, I’m afraid we are on the same boat here . There is no big rush, happy to revisit this after the holiday period.
Happy belated new year!
We are eager to move forward with finalizing a demo that receives data from Speckle streams into ShapeDiver. @Nikos did you have a chance to look into the issue described above?
The good news is that, in the latest plugin version, I can confirm that the previously reported issue is fixed! As a side note, it does also work on ShapeDiver now, which we are very happy about!
However, I found a related issue with the “Stream Get with Token” component. I am not sure if you prefer to handle it here or if I should open a separate topic (if so, let me know and I will copy my report there).
Somehow, when sending incorrect or fake inputs to “Stream Get with Token” after having previously loaded a stream, it seems the previous stream is cached and again returned by the component. See the clip below:
This can lead to confusing situations in the context of ShapeDiver, as well as security risks. Unless I am missing something, I don’t think this is what users would expect from the component either.
@Nikos and @Mathieu_Huard are there any progress on this issue? We’re eager to start setting up ShapeDiver apps that get the latest model data from Speckle.
(this is my way of saying pre-holiday stuff is busy/clogged and we might get to it in early jan…)
. There is no big rush, happy to revisit this after the holiday period.
