Henry
My concrete use-case a role based permission callback system for gorm but it shouldn't depend on the concrete application's types (like qor-example/models).
Since there is no reconnect functionality I applied the patch in [this PR to mailer](https://github.com/qor/mailer/pull/1). It establishes the TCP connection once it sends an email. Maybe I (or someone else)...
I had to copy the templates from `github.com/qor/mailer` into the `app/view` folder of my app because the assetfs or GOPATH renderPath lookup wasn't working correctly.
What makes this even more annoying is that a couple of repisotories were tagged last year with 1.0 but never updated since. If you try to vendor a qor-project today...
Same issue on other repo: https://github.com/qor/transition/issues/7
I think you need to make the _band_ a [hasMany](http://doc.gorm.io/associations.html#has-one) relationship.
I could be wrong but I think this is more of a gorm problem than one with QOR, hence the `sql: ..` error. Either chose a database system that can...
I've done a proof-of-concept of `net/rpc` over websockets in [trakting](https://github.com/cryptix/trakting). It mirrors the database interface to the rpc clients, with some minimal code gen it should be quite pleasant. That...
hmmm... this smells like a corrupted offset log. Do you also get this when you start ssb-server stand-alone?
I just got this during testing the new invites and now get it on each startup of ssb-server ``` [gossip] warning: this can happen if the database closes [Arguments] {:42.9%,...