metadata not properly encoded when sending requestStream with BearerAuthMetadata(jwt) about rsocket-kotlin HOT 3 OPEN

Hey!

Thx for the report, though it's hard to understand what is the issue on current moment.
Can you please add frame logging on client or server side (via rsocket-java/rsocket-kotlin functionality) and post frame logs here (or via link to gist)?
As for rsocket-kotlin (on client side) you will need to add loggerFactory = PrintLogger.withLevel(LoggingLevel.DEBUG) to connector configuration.
f.e. if you are using ktor-client integration:

install(RSocketSupport) {
  connector {
    loggerFactory = PrintLogger.withLevel(LoggingLevel.DEBUG)
  }
}

Also, do you have some custom client / server configuration regarding fragmentation, like maxFragmentSize in rsocket-kotlin?

from rsocket-kotlin.

You are so correct !! I had maxFragmentSize = 1024 set in rsocket-kotlin
If I remove that, that error is gone...

I had copied it right from the //create ktor client example on https://github.com/rsocket/rsocket-kotlin

Is using maxFragmentSize = 1024 an issue?

from rsocket-kotlin.

Good to hear that it solves issue on your side!
Overall using maxFragmentSize should not cause any issues, but overall - stick with defaults unless needed :)
Example in README just shows what is possible to configure, may be we need to cleanup it a bit to make it more robust.

Though, you report confirms that there is a bug somewhere in fragmentation logic inside rsocket-kotlin regarding handling of request stream/channel frames (likely because of additional initialRequest field, that could be handled differently).
I believe rsocket-java implementation is correct, so I think that I will setup some cross-implementation testing in future (at least for fragmentation use case).

from rsocket-kotlin.