Slava Egorov

@kdzwinel "Often" does not mean "always". I recommend actually investigating what happens, confirming that it looks like a bug and then filing a bug (with a repro) at V8's bugtracker.

I followed up on dart-lang/sdk#43612 tldr; is that Flutter CLI can be changed to produce necessary dSYMs. No changes in Dart compilation toolchain are required. I have provided the prototype...

@yury-yufimov I am not sure I understand your reasoning about `processAsset` being invoked `O(n^2)` times. It uses `visited` set to avoid revisiting assets, so it should only be invoked once...

PR from @acoutts (https://github.com/grpc/grpc-dart/pull/349) added deserialization of error details for client size, but nobody contributed serialization of error details for server side so far. PRs are welcome.

I don't really have any strong architectural opinion on how to debug. I just sprinkle `print`'s around until I find the problem, but obviously this is not a scalable approach...

@enyo I am saying somebody could modify `grpc` package implementation in the suggested way and expose ability to configure it externally through on `Server` constructor (similar to how server interceptors...

This is an interesting question. Underlying `headers` and `trailers` are nullable because implementation `null`s them out when they are are not longer needed / do not affect subsequent flow of...

We could do that. They are already wrapped in the getters. It would be best if we were to restructure APIs in such a way that error could never occur...

There are no plans to support server reflection at this time. PRs are welcome though

@walsha2 still no plans to support this. main reason is that we don't have engineering resources for ongoing development of this library.