Sean Tempesta

I'm confused as to the status of this issue? It seems like it's working for some people? Can someone document how to at least get partial support working? I just...

Reading the blog post, it seems like the react sdk version is wrong? https://blog.expo.io/expo-sdk-v27-0-0-is-now-available-898bf1e5b0e4 ``` In app.json, change sdkVersion to "27.0.0" In package.json, change these dependencies: - react-native to "https://github.com/expo/react-native/archive/sdk-27.0.0.tar.gz"...

Great work @echelon ! Would you mind sharing details about how you trained melgan and got it working with glow-tts? All of my experiments with melgan failed and I'm having...

Hey @sulami: Maybe we should just create a new namespace? That way we don't break existing behavior and we can define new specs/functions to operate in parallel? Also, I'm super...

So, I'm really not familiar enough with Posh's internals to fix this. I thought I saw somewhere that Posh might bring back manual specification of listen patterns? At least then...

Temporary workaround. I found if you explicitly expand isComponent pull patterns the pull analyze picks up the changes. So, in the example above, you'd have to do something like this:...

@eoliphan: It worked for my scenario at that time. No idea if it's working now as I'm no longer using Posh.

Any updates on this? I know you guys are going for the more ambitious "send all relevant datoms to the client", but I'd just be happy with the forwarding the...

Okay, so I don't really understand the Posh codebase, but when I run the test this is the tx-report I'm seeing: ``` (d/transact conn* [{:db/id (tempid) :test/attr "Abcde"}]) => #object[datomic.promise$settable_future$reify__6470...

Looking up the attribute via `d/ident` fixed it. Although there's still a race condition between the thread picking up the change and updating the ratom, so the test fails unless...