### SUMMARY
**sqlite transport**
This transport now batches and bulk inserts objects when writing resulting in huge performance improvements (100x).
**base object serializer**
Batching in the sqlite transport necessitated some refactoring here in order to safely call end_write when not using operations.send/receive. This has been resolved by turning traverse_base into a wrapper for _traverse_base which can take care of calling begin/end_write and resetting the writer at the top level. This is not breaking since the top level methods to call have not changed names and the original method has just been prepended with a _
Additionally, missing referenced child objects in the read transport used to raise a SpeckleException. However, using the gql client to call objects.get() will return an object with missing references by design thus throwing an error in serialization. This has been resolved by instead raising a SpeckleWarning when child objects can't be found and just returning the reference + id. ((this method of interacting with objects is discouraged so it is not surprising to me that this bug was lurking for so long - but an oopsie nonetheless!))
**ci / dev**
Updates for the ci config and the dev container to work with the recent changes in server.
NOTE: dev container seems to be pulling an older version of server -- not resolved yet
---
* quick and hacky sqlite batching
* feat(transports): batching sqlite inserts
* chore: upgrade gql3
also removed py-spy as it's not used and i was getting install errors :/
* ci: bump node version
* ci: formatting
* update CI versions
* update to new circleci redis baseimage
* update test fixture auth to non deprecated token based method
* add start and finish write method calls to base object serialize
* chore: dev container update
* fix(serialization): move end and begin write
* style: formatting
* fix(serializer): warn but don't throw if ref not found
this is _not_ an issue with the transports, but an issue with using the
graphql api to fetch objects. since you are only receiving one obj and none of
the children, the transport has no way to find them and should simply
return the reference as is. idk why anyone would really use `object.get`
so tbh i'm not surprised no one has found this bug yet lol
* fix(client): don't parse obj create response
* fix(serializer): wrap `traverse_base`
moving `begin` and `end_write` to the seriazlier due to the new
sqlite transport with batched writes necessitates a wrapper around
`traverse_base` so end/begin write can be called once at the top level.
just adding begin/end write to the original traversal method would make
tons of calls to `end_write` since the traversal is recursive
Co-authored-by: izzy lyseggen <izzy.lyseggen@gmail.com>
* feat(models): a quickie lil update
- adds fave and comment count
(mutations to come)
- adds source app to commit within stream query
* feat(client): add favorite mutation
* feat(models): `ActivityCollection` and `Activity`
* feat(client): stream activity method
* test(client): test for stream activity
* refactor(client): use datetime args for activity
* docs(client): clean up stream activity docstring
* feat/test(client): user activity
so i'm a bit of a dumbo here.
i didn't realise that doing `.update()` on attr would update the parent
attr as well and extend to all objects every ahhhhhh
you have to do `self.thing = self.thing + blah blah` to just update
the instance attr. the more ya know!
#roastme @cristi8
Implement automatic type register mechanism that stores all speckle Base model subclasses in a type
register for deserialization reuse in transports. This enables the Base to be useful as a base kit
object.
fix#50
It was possible to override the builint types with a duplicate speckle_type, either via a duplicate
class name of an explicit speckle_type definition. It is now checked before registering the new type
in the subclass registry, and a meaningful error is thrown.
Gergő Jedlicska