René Vlugt

I just noticed @ BlackReloaded has sort of forked/borrowed some code from @benpye's project specifically for WSL2 (using socat): https://github.com/BlackReloaded/wsl2-ssh-pageant. That setup works for me. Just note that the docs...

> > > > I just noticed @ BlackReloaded has sort of forked/borrowed some code from @benpye's project specifically for WSL2 (using socat): https://github.com/BlackReloaded/wsl2-ssh-pageant. That setup works for me. Just...

I've been having this issues for ages myself, I've updated serveral versions but to no avail. Think I'll follow @GregorGlinka's advice and look into Telegraf.js

Having the same issue as Dennis using a local file: ```ts const fetchMetadata = async () => { await fetch('https://fr2.ah.fm/stats?sid=1&json=1') .then(data => data.json()) .then(async obj => { if (obj.songtitle &&...

I think I've found a workaround just now: If I call both `updateMetadataForTrack` and `updateNowPlayingMetadata`, my artwork will actually stay: ```tsx TrackPlayer.updateMetadataForTrack(currentTrack, { title: obj.songtitle, artwork: require('./assets/afterhours-fm.jpg'), }); TrackPlayer.updateNowPlayingMetadata({ title:...

This has just been fixed 3 weeks ago with the new release of react-native-webview v13.6.2. I'm runnin gon Expo 48 and React Native 71 (without Hermes) that comes with v11.26.0...

I've created an elaborate ticket over [here](https://github.com/prisma/prisma-engines/issues/3826) based on the comments from @Jolg42 which I think specifies everything that needs to be done. Would be great if somebody can pick...

@tomhoule You mention a on [#3826](https://github.com/prisma/prisma-engines/issues/3826) the discussion will have to take place here and we need to reach a conclusion first. What is currently unclear? If `@default(cuid())` should start...

Well fixed length would already be a bit of an issue. Digging through some tickets, Prisma 1 originally used varchar(25). As it turns out, the original rust implemenation could already...

One worker and only one time? Probably just an accidental error during login, probably fixes itself on the retry.