Question

我使用Kotlin为Vertx实现了一个grpc API，并启用了FINEST日志级别以进行调试。在我的集成测试中，我正在尝试使用通道将grpc客户端连接到服务器。

客户端代码段：

$( document ).ready(function() {
    //var countimg = $(".main").find('img').length;
    var count2 = $(".main").children('img').length > 20;
    //console.log(countimg);
    //console.log(count2);
    if(count2 === true){
        //var i = 0;

        $.each($('.main img'), function (index, value) {             
            //i++;
            console.log('um inside'+i);
            //if(i > 10){
                $(this).css('display','block');
            //}else{
            //    $(this).css('display','block');
            // }

            return ( index !== "three" );
        });




        $.each($('.main img'), function (index, value) {   
                $(this).css('display','none');
        }
        $(this).parent().append("<a class='show-more'>See More</a>");
        }
});

我在grpc verticle的日志中看到以下内容：

    val clientAsync1 = ctx.async()
            val channel1 = VertxChannelBuilder
                    .forAddress(vertx, "localhost", 10000)
                    .usePlaintext(true)
                    .build()
            val stub1 = ExampleGrpc.newVertxStub(channel1)

            val request = builderUtil.buildRequest()

            stub1.attemptFriendship(request) { stream ->
                    stream.handler { response ->

                    }
            }

有人可以解释[main] 2018-05-24T12:42:27.69+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] Exiting idle mode [grpc-default-executor-0] 2018-05-24T12:42:27.71+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] resolved address: {1}, config={2} [main] 2018-05-24T12:42:27.713+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] {1} created for {2} [main] 2018-05-24T12:42:27.759+09:00 FINE [io.grpc.internal.InternalSubchannel] [{0}] Created {1} for {2} [vert.x-eventloop-thread-0] 2018-05-24T12:42:28.081+09:00 FINE [io.grpc.internal.InternalSubchannel] [{0}] {1} for {2} is ready [vert.x-eventloop-thread-0] 2018-05-24T12:42:35.956+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] Created with target {1} [vert.x-eventloop-thread-0] 2018-05-24T12:42:35.961+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] Exiting idle mode [grpc-default-executor-0] 2018-05-24T12:42:35.962+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] resolved address: {1}, config={2} [grpc-default-executor-0] 2018-05-24T12:42:35.962+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] {1} created for {2} [grpc-default-executor-0] 2018-05-24T12:42:35.963+09:00 FINE [io.grpc.internal.InternalSubchannel] [{0}] Created {1} for {2} [vert.x-eventloop-thread-0] 2018-05-24T12:42:35.974+09:00 FINE [io.grpc.internal.InternalSubchannel] [{0}] {1} for {2} is ready [vert.x-eventloop-thread-0] 2018-05-24T12:42:46.808+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] shutdown() called [vert.x-eventloop-thread-0] 2018-05-24T12:42:46.81+09:00 FINE [io.grpc.internal.ManagedChannelImpl] [{0}] Shutting down的含义吗？请注意，为完成测试而创建了多个通道，响应是流。

Answer 1

{0}格式是MessageFormat格式，java.util.logging是params使用的默认格式化程序。调用log(Level level, String msg, Object[] params)之类的方法时，msg应该与java.util.logging.Logger结合以形成日志字符串。这是有益的，因为如果不打印日志则避免处理。

如java.util.logging.Formatter文档中所示：

通常，格式化程序使用java.text.MessageFormat样式格式来格式化参数，因此例如格式字符串“{0} {1}”会将两个参数格式化为字符串。

您环境中配置的android:layout_centerHorizontal="true"似乎没有这样做。

带Vertx日志的grpc说明需要

1 个答案: