Mark Duckworth

@manoslive, can you tell us when this error started occurring for you?

Thanks for the update. I communicated this to the backend team. @manoslive, if you can provide a project ID, that will help them diagnose. You may want to [create a...

@PL47productions, thanks for letting us know that this is also impacting you. I updated the internal conversation with this information. As @iAMkVIN-S mentioned, using `preferRest` may provide a workaround. You...

@sbhvt, Sorry to hear this change has caused performance degradation for you. preferRest was introduced to reduce function cold start times associated with loading and initializing the grpc stack. There's...

@JamieCurnow, Thanks for bringing this to our attention. I reproduced the behavior and I agree that it is confusing and the throwing behavior of `FieldValue.delete()` on a nested property adds...

I just reviewed `set(..., {merge: true})` and I can see that the message sent to the backend is slightly different than when using `update(...)`. The set+merge call is requesting that...

Cleanup. Working on another branch now.

This sounds like a usage question that might be specific to Svelte or Docker, I'm not seeing anything that indicates an issue with the Firestore SDK yet. Perhaps you will...

@jramosss, I attempted a reproduction with this code (guessed on the value of `number` and return type of `parseRecipientAsNumber`), but I was not able to reproduce with nodejs-firestore v7.1.0. The...

I'm still not able to reproduce this. The following code works fine. ``` import {initializeApp} from 'firebase-admin/app'; import {Filter, getFirestore, FieldValue} from 'firebase-admin/firestore'; async function main() { initializeApp() const fs...