Beta Testing Features

gokermu · 2 September 2021 14:46

This looks great @SpeckleTeam. One thing:

Did you mean “Stream Home”?

dimitrie · 2 September 2021 14:48

Totally. Good spot! I’ll do a crazy thing right now, and commit straight to master a fix.

gokermu · 2 September 2021 14:49

. Great
(Have to make 20 characters)

JdB · 3 September 2021 07:49

Good stuff! As usual

Some quick thoughts from my side.

Great improvement!
Maybe move the invite button to the left side menu (see A in screenshot 1) because it’s not really part of the stream but a more high level action?
When the left side menu is collapsed, you see a few dots on the top left (see B in screenshot 1), maybe place the Speckle icon there?
Typo on the globals page (see screenshot 2, sorry I just love windows Snip & Sketch )
I noticed some inconsistency when the left side menu is open or closed. When you go to the Feed or Streams page it looks the same (screenshot 3), which is good. However, when you open a stream it looks different (screenshot 4). Might be better to use the same icon (so ≡ instead of <)?
On a stream page with the left side menu out, you quite quickly reach the character limit of stream names (see again screenshot 4). This is not the case when the left side menu is collapsed (screenshot 5).
When on the Feed or Streams page and the left side menu is closed, this guy pop ups on the top right to create a new stream:
. It’s not really needed, in my opinion.
Did I already mentioned I really like the changes?

Screenshot 1

Screenshot 2

Screenshot 3

Screenshot 4

Screenshot 5

dimitrie · 3 September 2021 08:22

Thanks @JdB, they’re all valid points. Problem “B” from screenshot 1 I can’t reproduce unfortunately, could you tell me browser/os/resolution combo? It’s where the Speckle logo is

The rest I can massage into place. The with a + inside should actually appear only on mobile, but i seem to have fumbled some breakpoints.

Happy you like the changes! They’ll allow us for future expansion (more sidebar items for new features such as projects/organisations, lots of room for a table view under the viewer now, etc). I won’t raise an issue with them, as I’m a bit lazy to copy paste these in one. We’ll refer to this thread

JdB · 3 September 2021 10:00

Problem “B” appears to be a browser issue. I used Firefox on Windows with 1920x1080. I tried a bunch of lower resolutions as well (all the way down to 800x600) but it remained the same in Firefox. In Chrome and Edge I do see the logo as it should.

Sounds good. Also nice indeed to have room for future features!

dimitrie · 4 September 2021 17:32

I fixed it - FF didn’t like svgs as background images, as vuetify’s default v-img component works. I’ve fixed most of the things you’ve pointed out

The changes should be on their way to latest.speckle.dev as I type right now.

JdB · 6 September 2021 07:29

Thank you! It looks good and works like a charm

teocomi · 8 September 2021 17:03

Hello @Insiders !

We have just released v2.1.30-beta of the Connectors.
This release contains some major changes in the serialization and deserialization logic giving us some impressive speed improvements :

serialization 2-10x
deserialization 3-10x
server upload 4x

All of this thanks to @cristi 's magic!

Please update all connectors and help us test them!

You can report any issues you find down below.

https://media.giphy.com/media/26vUzl3ufQxx9dims/giphy.gif

JdB · 9 September 2021 08:02

I’ve updated to the beta connectors and now I get an error in Revit when receiving a stream made in GH. It contains 4 Speckle walls. @teocomi: I made you owner of the stream (GH > Revit walls test).

The error in Revit:

One or more errors occurred.
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.ConvertJsonElement(JsonElement doc)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.ConvertJsonElement(JsonElement doc)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.ConvertJsonElement(JsonElement doc)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.ConvertJsonElement(JsonElement doc)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.ConvertJsonElement(JsonElement doc)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.DeserializeTransportObject(String objectJson)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.Deserialize(String rootObjectJson)
   at Speckle.Core.Api.Operations.<Receive>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Speckle.ConnectorRevit.UI.ConnectorBindingsRevit.<ReceiveStream>d__5.MoveNext() in C:\Users\circleci\project\ConnectorRevit\ConnectorRevit\UI\ConnectorBindingsRevit.Receive.cs:line 62
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Speckle.DesktopUI.Streams.StreamsRepository.<ConvertAndReceive>d__3.MoveNext() in C:\Users\circleci\project\DesktopUI\DesktopUI\Streams\StreamsRepository.cs:line 46

AlanRynne · 9 September 2021 08:04

Thanks @JdB, I was actually just reporting this on our private Discord.

Seems like our new and improved deserialiser is angry about something… We’ll post here when we’ve found a solution (and likely, deploy a new beta version)

If you need to “Roll back” to the latest sable version, just deactivate the option for beta releases. Then uninstall the beta ones and you should be able to install the stable ones instead.

AlanRynne · 9 September 2021 09:57

Hello again @Testers!!

We just released version 2.2.0-beta that fixes the issue reported by @JdB. This was preventing any newly sent object from being received.

Enjoy the performance improvements!

JdB · 10 September 2021 14:31

When receiving the stream in different Revit I get an error. Hopefully the information below helps and let me know if I can check anything else.

Manager: v2.1.3
Connectors for Rhino and Revit: 2.2.0-BETA

I created the following public stream in Rhino 7, which contains a Speckle floor: Speckle

When receiving the stream in Revit 2019, I get this error:

Array cannot be null.
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.GetClosures(String rootObjectJson)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.Deserialize(String rootObjectJson)
   at Speckle.Core.Api.Operations.<Receive>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Speckle.ConnectorRevit.UI.ConnectorBindingsRevit.<ReceiveStream>d__5.MoveNext() in C:\Users\circleci\project\ConnectorRevit\ConnectorRevit\UI\ConnectorBindingsRevit.Receive.cs:line 62
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Speckle.DesktopUI.Streams.StreamsRepository.<ConvertAndReceive>d__3.MoveNext() in C:\Users\circleci\project\DesktopUI\DesktopUI\Streams\StreamsRepository.cs:line 46

When receiving in Revit 2020, this is the error:

The type initializer for 'System.MemoryExtensions' threw an exception.
   at System.Text.Json.JsonDocument.Parse(ReadOnlyMemory`1 json, JsonDocumentOptions options)
   at System.Text.Json.JsonDocument.Parse(String json, JsonDocumentOptions options)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.DeserializeTransportObject(String objectJson)
   at Speckle.Core.Serialisation.BaseObjectDeserializerV2.Deserialize(String rootObjectJson)
   at Speckle.Core.Api.Operations.<Receive>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Speckle.ConnectorRevit.UI.ConnectorBindingsRevit.<ReceiveStream>d__5.MoveNext() in C:\Users\circleci\project\ConnectorRevit\ConnectorRevit\UI\ConnectorBindingsRevit.Receive.cs:line 62
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Speckle.DesktopUI.Streams.StreamsRepository.<ConvertAndReceive>d__3.MoveNext() in C:\Users\circleci\project\DesktopUI\DesktopUI\Streams\StreamsRepository.cs:line 46

When receiving the stream in Revit 2021, Revit crashes:

JdB · 10 September 2021 14:42

Sorry for the spam, but I think it would be good to also share this one. The online viewer doesn’t show the model in Firefox on my end. It still works perfectly fine in chrome and edge.

teocomi · 10 September 2021 18:15

Hey @JdB I can replicate your bug (but only in 2019), we are looking into it!
Ping @dimitrie re viewer.

Thanks a bunch as always!!!

bcall · 10 September 2021 22:52

I would like to become a tester, please!

teocomi · 14 September 2021 20:05

@JdB it turns out an addin shipped with Revit was conflicting with one of our dependencies, could you please try with 2.2.1-beta when you get a chance?

@bcall invited!

Mayur_Mistry · 15 September 2021 11:33

I am interested to be a tester. Loving the product and the community is awesome

dimitrie · 15 September 2021 11:39

Cool, check your inbox for an invite to latest.speckle.dev currently we’ve just pushed out a release, so there’s not much difference between the bleeding edge and the stable https://speckle.xyz, but as we go ahead things will diverge.

JdB · 16 September 2021 07:29

For Revit 2020 and 2021 the new beta works like a charm (for 1 floor from Rhino to Revit)!

Revit 2019 gives an error. I have polluted that version of Revit with to much addins, which might cause the error . Would you like me to run some script to get a proper overview of all addins and dependencies?

Screenshot of my Revit 2019 top bar (showing a bunch of the addins):

The error in Revit 2019:

Could not load file or assembly 'System.Text.Json, Version=5.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. Invalid pointer (Exception from HRESULT: 0x80004003 (E_POINTER))
   at Speckle.Core.Api.Operations.<Receive>d__3.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
   at Speckle.Core.Api.Operations.Receive(String objectId, CancellationToken cancellationToken, ITransport remoteTransport, ITransport localTransport, Action`1 onProgressAction, Action`2 onErrorAction, Action`1 onTotalChildrenCountKnown, Boolean disposeTransports, SerializerVersion serializerVersion)
   at Speckle.ConnectorRevit.UI.ConnectorBindingsRevit.<ReceiveStream>d__5.MoveNext() in C:\Users\circleci\project\ConnectorRevit\ConnectorRevit\UI\ConnectorBindingsRevit.Receive.cs:line 62
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Speckle.DesktopUI.Streams.StreamsRepository.<ConvertAndReceive>d__3.MoveNext() in C:\Users\circleci\project\DesktopUI\DesktopUI\Streams\StreamsRepository.cs:line 46