Asan failure: bins/asan/h2_fakesec_test keepalive_timeout GRPC_POLL_STRATEGY=epollsig

https://grpc-testing.appspot.com/job/gRPC_pull_requests_asan_c/5489/consoleFull
I0626 23:54:16.775702473   15226 ev_epollsig_linux.c:90]     epoll engine will be using signal: 40
D0626 23:54:16.775737072   15226 ev_posix.c:121]             Using polling engine: epollsig
D0626 23:54:16.775822636   15226 dns_resolver.c:316]         Using native dns resolver
I0626 23:54:16.776114339   15226 keepalive_timeout.c:57]     keepalive_timeout/chttp2/fake_secure_fullstack
D0626 23:54:18.311863087   15226 ev_posix.c:121]             Using polling engine: epollsig
D0626 23:54:18.311933609   15226 dns_resolver.c:316]         Using native dns resolver

=================================================================
==15226==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 88 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x5fa911 in resolve_address_impl /var/local/git/grpc/src/core/lib/iomgr/resolve_address_posix.c:192:16
    #3 0xa4908f in dns_start_resolving_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:216:3
    #4 0xa48997 in dns_channel_saw_error_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:129:5
    #5 0x75f432 in grpc_resolver_channel_saw_error_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver.c:81:3
    #6 0x75afcc in on_lb_policy_state_changed_locked /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:271:7
    #7 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #8 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #9 0x62229e in timer_thread /var/local/git/grpc/src/core/lib/iomgr/timer_manager.c:139:7
    #10 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #11 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x608000007ea0 (88 bytes)

Indirect leak of 320 byte(s) in 1 object(s) allocated from:
    #0 0x4c3100 in calloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
    #1 0x77bb16 in zalloc_with_calloc /var/local/git/grpc/src/core/lib/support/alloc.c:42:53
    #2 0x77b567 in gpr_zalloc /var/local/git/grpc/src/core/lib/support/alloc.c:83:7
    #3 0x9ffc19 in grpc_lb_addresses_create /var/local/git/grpc/src/core/ext/filters/client_channel/lb_policy_factory.c:50:26
    #4 0x9ffd00 in grpc_lb_addresses_copy /var/local/git/grpc/src/core/ext/filters/client_channel/lb_policy_factory.c:55:38
    #5 0xa02502 in lb_addresses_copy /var/local/git/grpc/src/core/ext/filters/client_channel/lb_policy_factory.c:143:10
    #6 0x5ce6ad in copy_arg /var/local/git/grpc/src/core/lib/channel/channel_args.c:63:11
    #7 0x5cdc6c in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:122:28
    #8 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #9 0xa497fe in dns_on_resolved_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:178:14
    #10 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #11 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #12 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #13 0x6fb859 in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:93:7
    #14 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #15 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x6120000178c0 (320 bytes)

Indirect leak of 256 byte(s) in 1 object(s) allocated from:
    #0 0x4c3100 in calloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
    #1 0x77bb16 in zalloc_with_calloc /var/local/git/grpc/src/core/lib/support/alloc.c:42:53
    #2 0x77b567 in gpr_zalloc /var/local/git/grpc/src/core/lib/support/alloc.c:83:7
    #3 0xa47e8f in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:259:21
    #4 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #5 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #6 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #7 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #8 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #9 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #10 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #11 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #12 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #13 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #14 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #15 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #16 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #17 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #18 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #19 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #20 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #21 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x611000009000 (256 bytes)

Indirect leak of 248 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x6df8a4 in polling_island_create /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:528:8
    #3 0x6e3829 in add_poll_object /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:1686:18
    #4 0x6dab69 in pollset_set_add_pollset_set /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:1817:3
    #5 0x5f41c2 in grpc_pollset_set_add_pollset_set /var/local/git/grpc/src/core/lib/iomgr/ev_posix.c:260:3
    #6 0xa48179 in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:266:5
    #7 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #8 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #9 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #10 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #11 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #12 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #13 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #14 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #15 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #16 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #17 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #18 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #19 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #20 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #21 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #22 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #23 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #24 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x611000008ec0 (248 bytes)

Indirect leak of 248 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x6df8a4 in polling_island_create /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:528:8
    #3 0x6e3571 in add_poll_object /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:1663:18
    #4 0x6da837 in pollset_add_fd /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:1763:3
    #5 0x5f3edf in grpc_pollset_add_fd /var/local/git/grpc/src/core/lib/iomgr/ev_posix.c:233:3
    #6 0x959cd6 in grpc_tcp_server_start /var/local/git/grpc/src/core/lib/iomgr/tcp_server_posix.c:529:9
    #7 0x7431ad in server_start_listener /var/local/git/grpc/src/core/ext/transport/chttp2/server/chttp2_server.c:165:3
    #8 0x66e9b0 in start_listeners /var/local/git/grpc/src/core/lib/surface/server.c:1060:5
    #9 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #10 0x6fb80e in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:89:9
    #11 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #12 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x61100001db40 (248 bytes)

Indirect leak of 232 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x696d93 in grpc_combiner_create /var/local/git/grpc/src/core/lib/iomgr/combiner.c:130:25
    #3 0x74ad52 in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:669:21
    #4 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #5 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #6 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #7 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #8 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #9 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #10 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #11 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #12 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #13 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #14 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #15 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #16 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #17 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x611000009140 (232 bytes)

Indirect leak of 224 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x5cd830 in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:110:15
    #3 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #4 0xa497fe in dns_on_resolved_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:178:14
    #5 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #6 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #7 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #8 0x6fb859 in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:93:7
    #9 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #10 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x61100001da00 (224 bytes)

Indirect leak of 192 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x5cd830 in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:110:15
    #3 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #4 0x5ce7e9 in grpc_channel_args_copy /var/local/git/grpc/src/core/lib/channel/channel_args.c:129:10
    #5 0xa47fc8 in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:263:21
    #6 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #7 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #8 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #9 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #10 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #11 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #12 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #13 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #14 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #15 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #16 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #17 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #18 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #19 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #20 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #21 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #22 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #23 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x610000007c40 (192 bytes)

Indirect leak of 141 byte(s) in 6 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0x5ce34f in copy_arg /var/local/git/grpc/src/core/lib/channel/channel_args.c:52:13
    #4 0x5cdace in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:116:32
    #5 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #6 0x5ce7e9 in grpc_channel_args_copy /var/local/git/grpc/src/core/lib/channel/channel_args.c:129:10
    #7 0xa47fc8 in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:263:21
    #8 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #9 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #10 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #11 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #12 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #13 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #14 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #15 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #16 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #17 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #18 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #19 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #20 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #21 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #22 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #23 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #24 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #25 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x60200000e3d0 (16 bytes)
0x60300000ded0 (23 bytes)
0x60300000df30 (25 bytes)
0x60300000df60 (28 bytes)
0x60300000df90 (26 bytes)
0x60300000dfc0 (23 bytes)

Indirect leak of 141 byte(s) in 6 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0x5ce34f in copy_arg /var/local/git/grpc/src/core/lib/channel/channel_args.c:52:13
    #4 0x5cdace in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:116:32
    #5 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #6 0xa497fe in dns_on_resolved_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:178:14
    #7 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #8 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #9 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #10 0x6fb859 in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:93:7
    #11 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #12 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60200000de10 (16 bytes)
0x60300000ba10 (23 bytes)
0x60300000ba70 (25 bytes)
0x60300000baa0 (28 bytes)
0x60300000bad0 (26 bytes)
0x60300000bb00 (23 bytes)

Indirect leak of 64 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x5e6d38 in grpc_closure_create /var/local/git/grpc/src/core/lib/iomgr/closure.c:120:25
    #3 0xa49057 in dns_start_resolving_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:218:7
    #4 0xa48997 in dns_channel_saw_error_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:129:5
    #5 0x75f432 in grpc_resolver_channel_saw_error_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver.c:81:3
    #6 0x75afcc in on_lb_policy_state_changed_locked /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:271:7
    #7 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #8 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #9 0x62229e in timer_thread /var/local/git/grpc/src/core/lib/iomgr/timer_manager.c:139:7
    #10 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #11 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60600000b420 (64 bytes)

Indirect leak of 64 byte(s) in 1 object(s) allocated from:
    #0 0x4c32f8 in realloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:71
    #1 0x77b88f in gpr_realloc /var/local/git/grpc/src/core/lib/support/alloc.c:100:7
    #2 0x6e1e5c in polling_island_add_fds_locked /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:425:17
    #3 0x6dfe8c in polling_island_create /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:559:5
    #4 0x6e3571 in add_poll_object /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:1663:18
    #5 0x6da837 in pollset_add_fd /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:1763:3
    #6 0x5f3edf in grpc_pollset_add_fd /var/local/git/grpc/src/core/lib/iomgr/ev_posix.c:233:3
    #7 0x959cd6 in grpc_tcp_server_start /var/local/git/grpc/src/core/lib/iomgr/tcp_server_posix.c:529:9
    #8 0x7431ad in server_start_listener /var/local/git/grpc/src/core/ext/transport/chttp2/server/chttp2_server.c:165:3
    #9 0x66e9b0 in start_listeners /var/local/git/grpc/src/core/lib/surface/server.c:1060:5
    #10 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #11 0x6fb80e in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:89:9
    #12 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #13 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60600000b8a0 (64 bytes)

Indirect leak of 48 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x6da876 in pollset_set_create /var/local/git/grpc/src/core/lib/iomgr/ev_epollsig_linux.c:1772:27
    #3 0x5f3f4e in grpc_pollset_set_create /var/local/git/grpc/src/core/lib/iomgr/ev_posix.c:237:10
    #4 0xa48014 in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:264:27
    #5 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #6 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #7 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #8 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #9 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #10 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #11 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #12 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #13 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #14 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #15 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #16 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #17 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #18 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #19 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #20 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #21 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #22 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x60400000db90 (48 bytes)

Indirect leak of 39 byte(s) in 2 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0x5ce4b4 in copy_arg /var/local/git/grpc/src/core/lib/channel/channel_args.c:55:26
    #4 0x5cdace in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:116:32
    #5 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #6 0xa497fe in dns_on_resolved_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:178:14
    #7 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #8 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #9 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #10 0x6fb859 in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:93:7
    #11 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #12 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60200000ddf0 (16 bytes)
0x60300000ba40 (23 bytes)

Indirect leak of 39 byte(s) in 2 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0x5ce4b4 in copy_arg /var/local/git/grpc/src/core/lib/channel/channel_args.c:55:26
    #4 0x5cdace in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:116:32
    #5 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #6 0x5ce7e9 in grpc_channel_args_copy /var/local/git/grpc/src/core/lib/channel/channel_args.c:129:10
    #7 0xa47fc8 in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:263:21
    #8 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #9 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #10 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #11 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #12 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #13 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #14 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #15 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #16 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #17 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #18 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #19 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #20 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #21 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #22 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #23 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #24 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #25 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x60200000e3b0 (16 bytes)
0x60300000df00 (23 bytes)

Indirect leak of 24 byte(s) in 1 object(s) allocated from:
    #0 0x4c3100 in calloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
    #1 0x77bb16 in zalloc_with_calloc /var/local/git/grpc/src/core/lib/support/alloc.c:42:53
    #2 0x77b567 in gpr_zalloc /var/local/git/grpc/src/core/lib/support/alloc.c:83:7
    #3 0x716274 in grpc_fake_transport_security_credentials_create /var/local/git/grpc/src/core/lib/security/credentials/fake/fake_credentials.c:78:33
    #4 0x4f71a5 in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:111:7
    #5 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #6 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #7 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #8 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #9 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #10 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x60300000e6e0 (24 bytes)

Indirect leak of 24 byte(s) in 1 object(s) allocated from:
    #0 0x4c3100 in calloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
    #1 0x77bb16 in zalloc_with_calloc /var/local/git/grpc/src/core/lib/support/alloc.c:42:53
    #2 0x77b567 in gpr_zalloc /var/local/git/grpc/src/core/lib/support/alloc.c:83:7
    #3 0x9ffb8c in grpc_lb_addresses_create /var/local/git/grpc/src/core/ext/filters/client_channel/lb_policy_factory.c:46:34
    #4 0x9ffd00 in grpc_lb_addresses_copy /var/local/git/grpc/src/core/ext/filters/client_channel/lb_policy_factory.c:55:38
    #5 0xa02502 in lb_addresses_copy /var/local/git/grpc/src/core/ext/filters/client_channel/lb_policy_factory.c:143:10
    #6 0x5ce6ad in copy_arg /var/local/git/grpc/src/core/lib/channel/channel_args.c:63:11
    #7 0x5cdc6c in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:122:28
    #8 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #9 0xa497fe in dns_on_resolved_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:178:14
    #10 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #11 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #12 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #13 0x6fb859 in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:93:7
    #14 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #15 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60300000b9b0 (24 bytes)

Indirect leak of 18 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0x5ce34f in copy_arg /var/local/git/grpc/src/core/lib/channel/channel_args.c:52:13
    #4 0x5cdc6c in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:122:28
    #5 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #6 0xa497fe in dns_on_resolved_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:178:14
    #7 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #8 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #9 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #10 0x6fb859 in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:93:7
    #11 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #12 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60300000b9e0 (18 bytes)

Indirect leak of 16 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0xa47ef3 in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:261:24
    #4 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #5 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #6 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #7 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #8 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #9 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #10 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #11 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #12 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #13 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #14 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #15 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #16 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #17 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #18 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #19 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #20 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #21 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x60200000e430 (16 bytes)

Indirect leak of 16 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x5cd6bd in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:104:28
    #3 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #4 0xa497fe in dns_on_resolved_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:178:14
    #5 0x5e6ec6 in closure_wrapper /var/local/git/grpc/src/core/lib/iomgr/closure.c:115:3
    #6 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #7 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #8 0x6fb859 in closure_exec_thread_func /var/local/git/grpc/src/core/lib/iomgr/executor.c:93:7
    #9 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #10 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60200000de30 (16 bytes)

Indirect leak of 16 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x5cd6bd in grpc_channel_args_copy_and_add_and_remove /var/local/git/grpc/src/core/lib/channel/channel_args.c:104:28
    #3 0x5cd29d in grpc_channel_args_copy_and_add /var/local/git/grpc/src/core/lib/channel/channel_args.c:72:10
    #4 0x5ce7e9 in grpc_channel_args_copy /var/local/git/grpc/src/core/lib/channel/channel_args.c:129:10
    #5 0xa47fc8 in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:263:21
    #6 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #7 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #8 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #9 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #10 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #11 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #12 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #13 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #14 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #15 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #16 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #17 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #18 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #19 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #20 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #21 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #22 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #23 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x60200000e3f0 (16 bytes)

Indirect leak of 16 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0x5fa978 in resolve_address_impl /var/local/git/grpc/src/core/lib/iomgr/resolve_address_posix.c:195:13
    #4 0xa4908f in dns_start_resolving_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:216:3
    #5 0xa48997 in dns_channel_saw_error_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:129:5
    #6 0x75f432 in grpc_resolver_channel_saw_error_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver.c:81:3
    #7 0x75afcc in on_lb_policy_state_changed_locked /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:271:7
    #8 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #9 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #10 0x62229e in timer_thread /var/local/git/grpc/src/core/lib/iomgr/timer_manager.c:139:7
    #11 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #12 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60200000cfb0 (16 bytes)

Indirect leak of 6 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0xa47f43 in dns_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:262:21
    #4 0xa47ad0 in dns_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:288:10
    #5 0xa04f4c in grpc_resolver_factory_create_resolver /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_factory.c:49:10
    #6 0x760392 in grpc_resolver_create /var/local/git/grpc/src/core/ext/filters/client_channel/resolver_registry.c:150:7
    #7 0x74b86c in cc_init_channel_elem /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:712:21
    #8 0x5d3fca in grpc_channel_stack_init /var/local/git/grpc/src/core/lib/channel/channel_stack.c:137:9
    #9 0x5d77f1 in grpc_channel_stack_builder_finish /var/local/git/grpc/src/core/lib/channel/channel_stack_builder.c:270:23
    #10 0x65518b in grpc_channel_create_with_builder /var/local/git/grpc/src/core/lib/surface/channel.c:95:23
    #11 0x6571cf in grpc_channel_create /var/local/git/grpc/src/core/lib/surface/channel.c:194:10
    #12 0x744feb in client_channel_factory_create_channel /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:190:27
    #13 0x744b54 in grpc_secure_channel_create /var/local/git/grpc/src/core/ext/transport/chttp2/client/secure/secure_channel_create.c:228:15
    #14 0x4f74d5 in chttp2_init_client_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:82:7
    #15 0x4f71ba in chttp2_init_client_fake_secure_fullstack /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:112:3
    #16 0x552033 in begin_test /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:60:3
    #17 0x550805 in test_keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:130:7
    #18 0x5503e2 in keepalive_timeout /var/local/git/grpc/test/core/end2end/tests/keepalive_timeout.c:245:3
    #19 0x4f9bea in grpc_end2end_tests /var/local/git/grpc/test/core/end2end/end2end_tests.c:379:7
    #20 0x4f6e43 in main /var/local/git/grpc/test/core/end2end/fixtures/h2_fakesec.c:160:5
    #21 0x7f4c52ff1b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

Objects leaked above:
0x60200000e410 (6 bytes)

Indirect leak of 6 byte(s) in 1 object(s) allocated from:
    #0 0x4c2f78 in __interceptor_malloc /llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:52
    #1 0x77b3b7 in gpr_malloc /var/local/git/grpc/src/core/lib/support/alloc.c:71:7
    #2 0x787098 in gpr_strdup /var/local/git/grpc/src/core/lib/support/string.c:56:17
    #3 0x5fa9c4 in resolve_address_impl /var/local/git/grpc/src/core/lib/iomgr/resolve_address_posix.c:196:21
    #4 0xa4908f in dns_start_resolving_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:216:3
    #5 0xa48997 in dns_channel_saw_error_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver/dns/native/dns_resolver.c:129:5
    #6 0x75f432 in grpc_resolver_channel_saw_error_locked /var/local/git/grpc/src/core/ext/filters/client_channel/resolver.c:81:3
    #7 0x75afcc in on_lb_policy_state_changed_locked /var/local/git/grpc/src/core/ext/filters/client_channel/client_channel.c:271:7
    #8 0x6983ea in grpc_combiner_continue_exec_ctx /var/local/git/grpc/src/core/lib/iomgr/combiner.c:325:5
    #9 0x5f51da in grpc_exec_ctx_flush /var/local/git/grpc/src/core/lib/iomgr/exec_ctx.c:88:17
    #10 0x62229e in timer_thread /var/local/git/grpc/src/core/lib/iomgr/timer_manager.c:139:7
    #11 0x78e8c4 in thread_body /var/local/git/grpc/src/core/lib/support/thd_posix.c:57:3
    #12 0x7f4c538a4063 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x8063)

Objects leaked above:
0x60200000cf90 (6 bytes)

SUMMARY: AddressSanitizer: 2486 byte(s) leaked in 36 allocation(s).

Not seen in >1month.


Mock response to web browser

Hi author, many thanks for providing this amazing tool.
I am testing with selenium webdriver and want to Mock http(s) response to specific requests when submit a form. Is that possible to make Mock Server work as a browser proxy and bypass all irrespective requests to the real destination? In official docs and your previous response to other threads, It only talks about how to do so on a MAC OS. I need to run tests locally on windows laptop and also run it on CI with linux build agents.
Appreciate If you can provide some code examples.

Yes it is absolutely possible to do this.
I would suggest you use desired capabilities in selenium to configure a proxy for the browser, see:

https://sites.google.com/a/chromium.org/chromedriver/capabilities,
https://github.com/mozilla/geckodriver/issues/97 or
https://github.com/SeleniumHQ/selenium/wiki/DesiredCapabilities.

This will ensure all calls from the browser go via the proxy.  The MockServer can then be used to proxy all the calls by using forward actions, see:

http://mock-server.com/mock_server/creating_expectations.html#mock_forward, or
https://github.com/jamesdbloom/mockserver/blob/94e6446c91b83b7d8d7998d14c2ff9c48afc2981/mockserver-client-java/src/test/java/org/mockserver/client/server/MockServerClientIntegrationTest.java#L125

The links above should provide you with the code examples and details you need.  I am going to close this ticket.

@jun1983 I am trying something similar that you mentioned in this issue. Could you please care to share your learning or solution for this problem. Thanks


Where to find unaligned ShapeNetCore shapes?

Hi there, thank you for sharing your code!
Now I'm trying to generate the dataset. However, due to the dependency issue, I'm not able to use your visualizer. So I wrote the visualization code by myself.
However, in visualization, I found some objects look OK, but some objects are too small, or the grasps are always colliding with the objects. The good shapes are from ShapeNetSem and the others are from ShapeNetCore.
I think the problem might be that, in ShapeNetCore, the shapes and centered and normalized. So I'm guessing you were using the unaligned shapes.
Where do you find these unaligned ShapeNetCore shapes? It would be great if you can directly provide your stl files of ShapeNet objects.

Did you close this on purpose?  Unfortunately, we can't share any mesh data. The meshes that were used are from ShapeNetSem, not ShapeNetCore.


Fix whats_new.sh not finding libraries that are directories

I was wondering why whats_left says the entire collections module isn't implemented yet. It's because both libdir and name are bytes, when you format them into a string, you get a invalid path with b'' in it.

Thanks for contributing!

Thanks for contributing!


Make generated *.ld files deterministic

gen_app_partitions.py: make generated/app_smem_*.ld files deterministic
gen_relocate_app.py: make generated/linker_relocate.ld deterministic
Dictionaries are not ordered in Python 3.5 and before, so building twice
in a row could lead to a different sections/partitions order, different
build/zephyr/include/generated/linker_relocate.d, code_relocation.c,
build/zephyr/include/generated/app_smem_*.ld and different binaries.

cc @varun-sha , @AdithyaBaglody (can't be added as reviewers)

'd like the commit bodies to contain some text that reflects the changes in the patches (not just the rationale)

Done. No code change.

Quick question why is sort used instead of an actual ordered dict?  https://docs.python.org/3/library/collections.html#collections.OrderedDict

Thanks @sigvartmh for the attention to detail and post-merge review, really appreciated.

Quick question why is sort used instead of an actual ordered dict?

Good question, both approaches an be used. When there's only one output function sorting is easier so that's what I did here for gen_app_partitions.py. In other cases I've used an OrderedDict.

partsorted = OrderedDict(sorted(partitions.items(), key=lambda x: x[1][SZ], reverse=True))

I tested again and this doesn't work with Python 3.5, investigating why now. You're right I should have either fixed or removed this and explained why it doesn't work.
PS: @ulfalizer is on vacation

partsorted = OrderedDict(sorted(partitions.items(), key=lambda x: x[1][SZ], reverse=True))

This commit is much worse than a no-op: I missed and broke that decreasing size order implemented by @dcpleung in PR #14243. Apologies.
Full explanation, revert and proper determism fix in PR #17132, thanks in advance for reviewing quickly.


The Queue card shows SQS queue twice (one with the queued and one with processed and processing items)

Pulse Version
1.0.0-beta5
Laravel Version
10.34.2
PHP Version
8.2.13
Livewire Version
3.2.6
Database Driver & Version
No response
Description
We are running in an AWS environment and using SQS as queue driver. Currently, we have 1 queue, but Pulse shows it twice. The upper one has the "queued" jobs and the second one has the "processing" and "processed" jobs.

The database (pulse_aggregates) shows that the SQS entries are logged with different names. Some with the driver name and some with the full SQS address:

Steps To Reproduce
Currently, I do not have a second project that uses SQS queue, so I cannot share reproduction steps.

We are aware of this and will get it sorted in the next beta. Thanks for reporting.

This will be fixed in https://github.com/laravel/pulse/pull/187
We can follow that PR.


pitivi: fix build

Motivation for this change
The latest version is not compatible with Python 3.8, let's cherry-pick some patches from master.
Also pre-prepare for incoming release of GStreamer 1.18 and clean it up a bit.
Fixes: #96914
cc @davidak
Did not test it other than by building and starting it.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks for testing it.


Add steps to New-PodeWebRange

Would be great if you can add a -Steps parameter to define an Int between the numbers of the range.
Usecase would be to define RAM in 8GB intervals (8, 16, 24, etc) or CPU cores.

It looks like this should be possible according the Bootstraps docs: https://getbootstrap.com/docs/4.6/components/forms/#range, we just need to set the step attribute on the range input :)


Can't cut, copy and paste folders with spaces

Thanks for the non-java file manager. I'm not a Linux purist and have files and folders with spaces. I can't seem to be able to move them unless I remove the spaces.

I'll check that.

Fixed by Jamie.


Hive Test Failure: ethereum/sync

!!!!!!! This is an automated issue created by the hive test failure !!!!!!!\n\nThe hive test for ethereum/sync failed. Please investigate and fix the issue.\n\nLink to the failed run

Closing (testing)


one of the policy filters failed

Describe the bug
A clear and concise description of what the bug is.
How to Reproduce
Steps to reproduce the behavior:

Open the project, run '...'
Type '...' or do '...'
...

Expected behavior
A clear and concise description of what you think it should happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform:

OS: [e.g. Windows 10 x64]
Version: [e.g. neo3-boa v0.4]
Python version: [e.g. Python 3.8]

(Optional) Additional context
Add any other context about the problem here.
However, if your issue does not fit these aforementioned criteria, or it can be understood in another manner, feel free to open it in a different format.

Closed due to lack of information. Feel free to reopen it, but please don't forget to fill the information we request on our template. Thanks.

oh, sorry, I realised it's not relevant halfway writing it, but possibly hit "save" by accident


feat: add plugin default config

Signed-off-by: Meng JiaFeng<EMAIL_ADDRESS>Pre-Checklist
Note: please complete ALL items in the following checklist.

[x] I have read through the CONTRIBUTING.md documentation.
[x] My code has the necessary comments and documentation (if needed).
[ ] I have added relevant tests

Description

All helm plugins support the default value

Related Issues
#523 #526 #527 #513
New Behavior (screenshots if needed)
Jenkins config Before

After

I have compared the original yaml, the code defaultHelmConfig and the default config table in the doc.

A very helpful documentation improvement for users!👏

@steinliber Please resolve the conflicts. Then we can merge this pr asap.


Misc tweaks on Manage Channels page

can you double check w a lot of teams

mentions do work right?

I double checked on team keybase and scroll is working well. And I put the mention about mentions back, it's just showing up on all teams right now, even on small ones (bug).


Add password_warn_age parameter for login.defs

Simple change to add a new parameter for password_warn_age.  README updated too.  Anything else you'd rather see with it?

@claw-real Thanks a lot for this pr! Looks good to me ...


Preserve nil block arguments

Since 3.1.0 (#583), nil values are automatically stripped from extra block arguments. This is cumbersome when you want to pass nil values in some cases.
This PR aims to fix that while preserving the fix in #583.
I'm not quite sure though whether this fix makes sense, as I do not fully grasp the concept of the attribute parameter which, to my understanding, was the reason to put the compact there in the first place.
Please let me know what you think. Many thanks.

I took care of the merge conflicts, and merged it. Thanks!


i would like to add a theme switcher button like dark and light theme

i am a ssoc participant

which level of issue is this ?

Currently working on this just a little busy due to college

pls assign me this issue

@vaibhavsharma1234 First complete your previous issues.

pls assign me this issue

go ahead

i only have one issue left
i could have done this too

i only have one issue left i could have done this too

Complete that first

Hey @Susmita-Dey  I 've created theme changer but now I'm facing problem  should I remove background image and add gradient colour to it because if we change colour then background image won't change that's why I'm asking pls let me know what should I do ?
Screencast from 09-08-22 07:57:43 PM IST.webm

@vaibhavsharma1234 Do you want to make a theme changes as in the video?
If yes, then it would remove the navbar and the hero section which is a drastic change and also not allowed.


test: add more glitch test cases

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
1137

Relevant Lines:
1137

💛  - Coveralls


Bump NBGV to Fix CodeQL Workflow

Bump nbgv to fix codeql workflow. Update is required due to changes to GitHub Actions set-env deprecation:
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@guyacosta This will get CodeQL working again. Feel free to merge when ready if you approve of the changes.

Will do now
Sent from my T-Mobile 4G LTE Device
Get Outlook for Androidhttps://aka.ms/ghei36

From: Gabe Stocco<EMAIL_ADDRESS>Sent: Wednesday, November 25, 2020 6:33:42 PM
To: microsoft/ApplicationInspector<EMAIL_ADDRESS>Cc: Guy Acosta<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/ApplicationInspector] Bump NBGV to Fix CodeQL Workflow (#315)
@gfs approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FApplicationInspector%2Fpull%2F315%23pullrequestreview-538937624&data=04|01|guacosta%40microsoft.com|304c0f4e240c4892537f08d891ab4f54|72f988bf86f141af91ab2d7cd011db47|1|0|637419512240850952|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=cJicMhfo1Ue3RzjUiF7%2BESrSHXdo1vy6hud2Xn0tYLM%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALLQ4KDMAVV2ZE6YJBDKWTDSRWV7NANCNFSM4UDCEYYA&data=04|01|guacosta%40microsoft.com|304c0f4e240c4892537f08d891ab4f54|72f988bf86f141af91ab2d7cd011db47|1|0|637419512240860946|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=w15%2FJO2NYoPFVsngIQvB3KuZk9aEha8sVLhOexP%2BAwE%3D&reserved=0.


Release version 0.6.0

Sorry, but due to the RustFest workshop, I need to merge this without review/approval. I need the new version right about now :-)

Version has been published.


Support the python debugger

The VS Code plugin should support python debugging.

Some work has been done by @niloc132  and @chipkent with respect to python debugging.  Currently pycharm debugging is supported (https://deephaven.io/core/docs/how-to-guides/debugging/pycharm-debugging/).  VS Code was very close to working, but still needs a little work.

This is my repo that I was using to test the vs code debugger.  Putting it here in case we need it.
https://github.com/chipkent/test-dh-docker-vscode


Storage Blob Service deleteRetentionPolicy should not have restricts when RestorePolicy is disabled

PUT https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/yupstr/providers/Microsoft.Storage/storageAccounts/yups/blobServices/default?api-version=2019-06-01
{
"properties": {
"cors": {
"corsRules": []
},
"deleteRetentionPolicy": {
"enabled": true,
"days":12
},
"RestorePolicy": {
"enabled": true,
"days":7
},
"isVersioningEnabled": true,
"changeFeed":{
"enabled":true
}
}
}

https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/yupstr/providers/Microsoft.Storage/storageAccounts/yups/blobServices/default?api-version=2019-06-01
{
"properties": {
"cors": {
"corsRules": []
},
"deleteRetentionPolicy": {
"enabled": true,
"days":5
},
"RestorePolicy": {
"enabled": false
},
"isVersioningEnabled": true,
"changeFeed":{
"enabled":true
}
}
}

Response:
{
"error": {
"code": "ContainerOperationFailure",
"message": "Blob Delete Retention policy days should be longer than Point In Time Restore policy days.\nRequestId:feb1f7f7-401e-000e-7d8e-a33552000000\nTime:2020-10-16T07:29:21.9434562Z"
}
}

@zfchen95
This looks like a server issue, would you like help to look?

@zfchen95
This looks like a server issue, would you like help to look?

@blueww The service team (Mgmt and data plan) is fixing this problem. They give me an ETA of March.

@blueww The service team (Mgmt and data plan) is fixing this problem. They give me an ETA of March.

@yupwei68
Thanks for the update!
Then let's wait for the fix.

@yupwei68
Thanks for the update!
Then let's wait for the fix.

@yupwei68 has this been fixed?


Optimize StatusCode Line Matching for ASCII

String.matches(String regex) results in a re-compilation of the regex
every single invocation. Instead of using an underlying inefficient
Pattern/Matcher, instead use String.startsWith(String prefix). This
optimization matters for high throughput usecases when an endpoint
goes down and the number of SERVER_ERROR spikes dramatically.

Hey @ingenthr , any chance you could take a look at this and my other pull requests in the near future? Thanks!

Yep, had a look y'day, and planning to do a bit more today.  I'm working at getting them in and another update.

@ingenthr re-bumping


Can't use K8s secret in auth header

Agent Environment
Datadog Helm chart 3.57.3
(
Describe what happened:
Added an Open Metric check for Scalr following these docs:
    openmetrics.yaml: |-
      cluster_check: true
      init_config:
      instances:
        - openmetrics_endpoint: https://<account>.scalr.io:443/api/iacp/v3/metrics
          metrics:
            - .*
          headers:
            Authorization: ENC[k8s_secret@datadog/scalr/token]
            Prefer: profile=preview

I'm including the "Bearer" string as part of the token as per the secrets docs here.
However, the Authorization value is moved to another line and I believe this is stopping it from working as when the token is in plain text and on one line it works
=== openmetrics check ===
Configuration provider: file
Configuration source: file:/etc/datadog-agent/conf.d/openmetrics.yaml
Config for instance ID: openmetrics:86185c9b1a9d5933
empty_default_hostname: true
headers:
  Authorization: |
    Bearer <token>
  Prefer: profile=preview
metrics:
- .*
openmetrics_endpoint: https://<account>.scalr.io:443/api/iacp/v3/metrics
tags:
- cluster_name:minikube
- kube_cluster_name:minikube
~
===

Describe what you expected:
Push Scalr metrics to Datadog
Steps to reproduce the issue:
Deploy the Datadog helm chart with this cluster check
Additional environment details (Operating System, Cloud provider, etc):

HI @frazergibsongohenry,
The reason while the YAML representation use the  | notation is because you token has line breaks in it (see scalars notation from YAML spec).
You can use the setting secret_backend_remove_trailing_line_break: true from datadog.yaml to automatically remove trailing trailing line breaks from all secrets:
## @param secret_backend_remove_trailing_line_break - boolean - optional - default: false
## @env DD_SECRET_BACKEND_REMOVE_TRAILING_LINE_BREAK - boolean - optional - default: false
## Remove trailing line breaks from secrets returned by the secret_backend_command. Some secret management tools automatically
## add a line break when exporting secrets through files.
#
# secret_backend_remove_trailing_line_break: false

I'm closing this issue, but feel free to reopen it if needed.


Tests: adjust the Windows error codes

The Windows error codes are not re-exported, explicitly import the
WinSDK module to gain access to the error codes.  Add Windows specific
checks to ensure that the named forms match the underlying
implementation.

@swift-ci test

Well, I can understand having different families of error codes, but that is the status quo on all the platforms - all the error codes are in a single domain.  Splitting them up based on usage seems interesting but also problematic for things like sockets on unixy platforms.

Note: I'm not saying that Errno definitely wasn't the right choice on Windows -- but I do strongly suspect that is probably the case.
This should not be a thing:
    // TODO(compnerd) map windows error to errno


Cluster templates

rancher/types API PR: https://github.com/rancher/types/pull/799

CRUD ClusterTemplate and ClusterTemplateRevisions
Create Cluster From Template
Changes after design refactored
Integration Tests added
Update Cluster From Template

LGTM


Spring-cloud-starter-alibaba-nacos-config integrates the latest version of client2.0.3

我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。
We recommend using English. If you are non-native English speaker, you can use the translation software.
Which Component
Nacos Discovery
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe alternatives you've considered
The nacos client 2.0.3 version has been released, but the latest client integrated in spring-cloud-starter-alibaba-nacos-config is still 1.4.2. Is there any plan to integrate the latest client into the starter?

refer #2241


Cleanup dead code

Cleanup dead code in D3D12 renderer

Sorry I've made a mistake while rebasing my branches to create this patch.
It does not build anymore because I missed those two lines:
https://github.com/bkaradzic/bgfx/blob/master/src/renderer_d3d12.cpp#L661-L662


log L0 SST ranges when ImportSstService found too many files

Feature Request
Is your feature request related to a problem? Please describe:

to help understand what causes so many files by checking the start/end key
Describe the feature you'd like:

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

/type enhancement

/label affects-6.5


Brash assault seal display issue

See forum: https://community.gamedex.io/t/display-issue-on-brash-assault-desperation-in-calc/420/2
This is related to the redundant logic rewrite I'm proposing. These type of problems would more or less disappear if we didn't have such specific engine logic.

Fixed in the last update (the follow logic one)


List is not being updated when State change

Description
Overview
I'm trying to learn TCA by making a simple app with it. The code for the issue could be found here: https://github.com/hung-m-dao/spendings-app/blob/issue/list-not-updated/Spendings/Transactions.swift
My app consists of a Tab View, with each tab contains a NavigationStackView. The Transactions screen lies within "Accounts" tab, and will be opened if I select a specific account.
Issue
The first time I enters Transactions screen, if I send the loadTransactions action within refreshable or onAppear block, after receiving and updating state.transactions, nothing is being reflected on the UI.

But if I trigger the fetch using Button, the List can update its content accordingly.
If I press back and navigate to Transactions screen again, refreshable or onAppear block can update List content as expected.
Note: I tried to debug, the action refreshable and onAppear went through the reducer, also updated the State, but somehow the List did not pick up that change
Checklist

[ ] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[ ] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
List is updated after State change
Actual behavior
State changes are not being reflected on UI
Reproducing project
https://github.com/hung-m-dao/spendings-app/tree/issue/list-not-updated
The Composable Architecture version information
1.14.0
Destination operating system
iOS 18.1
Xcode version information
Xcode 16.2
Swift Compiler version information
swift-driver version: 1.115.1 Apple Swift version 6.0.3 (swiftlang-<IP_ADDRESS>.10 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0

Turns out the reason behind this is I have some redundant "Focus" field on the Accounts feature, removed them and everything works as expected now


Added non-async functionality

Added non-async, synchronous functionality to transcribing a pre-recorded file.
┆Issue is synchronized with this Asana task by Unito

This functionality was added in a different PR.


How can I get data and detail when I use it as a child component?

I use this lib as a component and import it to a container. It works fine, but how could I get the data and detail objects of this component from its parent container?
I guess I should put something in onPress and use {...this.props} when I refer it in container, but just have no clue how to achieve it.

https://github.com/FaridSafi/react-native-google-places-autocomplete/issues/177#issuecomment-324329315


allow undefined custom encoding

#2  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Update database with localisation table

In the future we want to be able to support multiple languages. While the necessary commands are not part of the Hera 2.0 milestone, adding support for it is much easier now than later.

@Pacmens @kevdelm @MCPGamer one of you please review the changes I made to:

DB model in google drive (Added localisation table)
DB changes made in phpMyAdmin (Added localisation table)

I think for now just having the table without any relations is enough.
Later on when we further refine this feature and implement commands for it we should consider adding a default language and language attribute to a guild, as well as maybe creating separate tables for languages and keys to increase persistency in the database


Partial Date Imputation refactor

Feature Idea
Problem: We need to reduce the cyclometric complexity of derive_date_vars.R and increase readability (#879), whilst also enabling further enhancements and features (as detailed below) to meet all the requests from the external testers.
Allow to impute up to day only and not months (#1020) or up to any highest part of the datetime, e.g. could be everything up to years or only up to seconds (#879)
Agreed Solution:
Firstly, the code needs to be refactored to reduce the cyclometric complexity.
To cover the enhancements, the following new derive_date_vars.R function argument is needed & this needs to be covered in the Date and Time Imputation vignette:

highest_imputation – would be the highest part of the date/time that we want imputation to be applied to – year/month/day/hours/minutes/seconds. Options are “Y”, “M”, “D”, “h”, “m”, or “s”. For DT functions would only be “D”, “M”, or “Y”.

Important notes to consider for this update:

If highest_imputation=“Y” is used for year imputation meaning we are imputing fully missing dates then this can only be used with date_imputation=”first” or “last” (as otherwise what would we set for “mid”?!) and it requires min_dates/max_dates to be used respectively as if "first" we'd set the missing year to min_date and if "last" set to max_date.
We would have to make clear that the users could never pick and choose which sections of the datetime are imputed, e.g. impute months but not days - but this seems an unrealistic need and not something we should need to cater for anyway.
Note this should then allow for cases where only missing hours, only missing minutes, or missing day/month/year but valid time. These examples didn't work for a user previously: 2003-12-15T-:15:18, 2003-12-15T13:-:19, 2020-07--T00:00, so let’s cover them in our unit tests.
We also need to test for the following user feedback: If time_imputation=NULL then you should still get the behaviour that a complete DTC with time gets set as the DTM, and only those with missing time get set as NA. Currently all get set as NA in this case (#879)
Stefan spotted a bug:  impute_dtc(dtc = "2020-02-02", time_imputation = "last", max_dates = list(lubridate::ymd("2020-02-02"))) gives "2020-02-02T00:00:00", but should really be "2020-02-02T23:59:59"
Need to add more documentation to max_dates argument from derive_vars_dtm - as specifying a DT for max_dates does not make sense if you impute time only as it will be ignored (recommend to use DTM instead), but a DT could make sense if date is imputed as well.

Relevant Input
See examples below
Relevant Output
See examples below
Reproducible Example/Pseudo Code
Examples:

Only impute up to DAYS:

  "2019-02-15",
  "2019-02",
  "2019",
  ""

derive_vars_dtm(
  highest_imputation = "D",
  date_imputation = "FIRST",
  time_imputation = "FIRST"
)

Would give imputed DTMs as:
  "2019-02-15T00:00:00",
  "2019-02-01T00:00:00",
  "",
  ""

Only impute up to MONTHS:

  "2019-02-15",
  "2019-02",
  "2019",
  ""

derive_vars_dtm(
  highest_imputation = "M",
  date_imputation = "FIRST",
  time_imputation = "FIRST"
)

Would give imputed DTMs as:
  "2019-02-15T00:00:00",
  "2019-02-01T00:00:00",
  "2019-01-01T00:00:00",
  ""

Impute up to YEARS:

  "2019-02-15",
  "2019-02",
  "2019",
  ""

derive_vars_dtm(
  highest_imputation = "Y",
  date_imputation = "FIRST",
  time_imputation = "FIRST",
  min_dates =  ymd_hms("2018-01-01T00:00:00")
)

Would give imputed DTMs as:
  "2019-02-15T00:00:00",
  "2019-02-01T00:00:00",
  "2019-01-01T00:00:00",
  "2018-01-01T00:00:00"

Only impute up to MINUTES:

  "2019-07-18T15:25",
  "2019-07-18T15",
  "2019-07-18",

derive_vars_dtm(
  highest_imputation = "m",
  date_imputation = "FIRST",
  time_imputation = "FIRST"
)

Would give imputed DTMs as:
  "2019-07-18T15:25:00",
  "2019-07-18T15:00:00",
  ""

Whoever takes this on also makes sense to take https://github.com/pharmaverse/admiral/issues/1001

I am not sure if we can separate the imputation update into two issues. I think if we have two issues, we would need to update many files twice. If we do this issue first, we would need to add the new highest_imputation parameter in all calls of derive_vars_dt(m)() in all functions which use imputation. When we implement the second issue (https://github.com/pharmaverse/admiral/issues/1299) we would remove all the calls.
If we do https://github.com/pharmaverse/admiral/issues/1299 first we would first update all examples and templates without the highest_imputation parameter and then when we implement this issue we would need to update them again for adding the parameter.
Thus I wonder if we should have only one issue.
@rossfarrugia , @thomas-neitmann , @bms63 , what do you think?

@bundfussr i prefer 2 issues but maybe fine to tackle both in one branch by one person as you suggest. having all this in one massive issue i felt would be more difficult for our community to follow.

My opinion is that we need a partial date-time object that we can then layer imputation on top of.  I think that a partial date-time object (including partial date objects and partial time objects) would reduce a lot of the complexity.  With a partial date-time object, "FIRST", "MID", and "LAST" imputation could become very simple, in general with min(), median(), or max()  (and pmin(), pmedian(), and pmax()-- though pmedian() doesn't exist) generics for the object.
The parallel versions could solve some issues that I have seen with imputation like:  "This adverse event occurred after visit 2 and before visit 3", where the date of visit 2 is "2022-07-02", the date of visit 3 is "2022-07-09", so we want to impute the date of the adverse event to be within that range while it's recorded in the SDTM as "2022-07".

@billdenney we're careful with the scope of admiral to cover majority of industry needs for ADaM, but accepting that we'll never cover all. The imputation you mention is such a rare scenario that we would leave that to companies to solve in their own extension package, as it is uncommon and overly complex. If my study clinical scientist were to request this then I would negotiate against, as the analysis impact wouldn't justify the effort.
Therefore we don't plan to go further than allowing the user to supply the missing part directly, e.g. "06-15", or use "FIRST", "MID", or "LAST" options. In this case "MID" doesn't relate to median it just simply picks 15 for missing day and 06-30 for missing month and day.
Look forward to discussing later your ideas on a ISO8601 datetime parsing package.

Seeing this after it was linked from #1315
A lot of these features are already implemented or would be rather simple additions to parttime.
The package has been a bit underloved and could use a bit of polish, but it aims to solve a lot of these exact challenges. It parses iso8601 (largely borrowed from the parsedate package) already has impute_time_max, impute_time_min and impute_time_mid, and @billdenney has proposed a few additional helpers that would solve the date imputation and imputation to a certain field (imputing up until "year", "month", "date", etc). Its goal is to be a partial datetime type that requires minimal gymnastics to handle and propagate datetime missingness.
The imputation is the simplest part of the package so you can pretty reliably use those pieces. It also handles date arithmetic and comparisons for cases that get a bit messy with partial datetimes.


Star renaming, editing, and removal also ringed icons for asteroid belts

i want to add custom star systems but some currently are in the place i want them to be. my idea is a command in game to delete star systems and the planets in them, edit star systems already in the game somehow, and the ability rename stars in the XML file.
i also think ringed icons for asteroid belts would be cool. you choose an asteroid image and it's patterned randomly in a ring relative to it's location in the star system.

Most of this is already either possible or not happening. Most of your editing woes can be solved by editing the XML file itself, the ingame commands were never meant to high precision additions, only for basic stuff or people who want to add one or two planets.

understood. i just have one question. by naming a star system that already exists in game in the XML file even if it's randomly generated will i be able to add planets to them?

You can already add planets manually to any star system, randomly generated or not.

ok! thanks!


wrap irm-iex exprs in pwsh?

See also: https://github.com/axodotdev/oranda/issues/393
We currently emit irm-iex (the windows version of curl-sh) exprs of the form:
irm https://github.com/axodotdev/oranda/releases/download/v0.4.1/oranda-installer.ps1 | iex

This expression only works in powershell, and will fail if pasted into e.g. cmd.exe. Wrapping it in "launch powershell" as follows would make it work more universally, though I don't know if there's Weird Implications:
pwsh -c "irm https://github.com/axodotdev/oranda/releases/download/v0.4.1/oranda-installer.ps1 | iex"

addendum: the expression should be
powershell -c "irm https://github.com/axodotdev/oranda/releases/download/v0.4.1/oranda-installer.ps1 | iex"

(pwsh is the command for "PowerShell Core" aka "PowerShell 6+" which is not installed by default on windows, powershell is the name of "PowerShell" aka "PowerShell 5.1", which is installed by default on windows. Core is essentially an unrelated product in that its implementation and behaviour is arbitrarily divergent, because it was made from the groundup to be run on linux and macos portably. While 5.1 is windows-only and Forever Eternal For Compatibility.)

renewed interest in this solution: a few versions ago we cleaned up error handling and wrapped everything in a try-catch with "exit 1" in the catch block. this works great when you exec the powershell script locally, but the specifics of iem | iex invoking iex in the same way as Get-Content -Raw my-script.ps1 | iex.
Seemingly when invoked in this bytewise way, iex behaves more like source than sh, which hillariously/horribly means the exit 1 exits the user's shell.


1.2.x

Description
Flex Styles for Paragraph component
Overview of Changes
Flex Styles for Paragraph component
Type of Change

[ ] Bug fix

Test Details
Petclinic App
Additional Notes
N/A

You did it @dinakarmeda!
Thank you for signing the Anthem Opensource Software CLA.


Update deps for to get new stats_hero.

The new stats_hero supports sending valid statsd messages in addition
to estatsd.
Updated deps:
envy
2015-03-13 e6ba396 Merge pull request #9 from manderson26/ma/travis
2015-03-13 8431c73 Added travis.yml
2015-03-13 901fefb Merge pull request #8 from joedevivo/master
2015-03-13 881470c Improved envy:get's -specs
ej
2015-03-25 132a9a3 Merge pull request #22 from seth/sf/add-apahce2
2015-03-25 a09b309 Add Apache Licence, Version 2.0
meck
2015-04-08 69664df Use 17.5 since 17.5 is not available on Travis yet
2015-04-08 247ba4b Update build environment to 17.5
2015-04-01 fa3cd97 Merge pull request #139 from gomoripeti/fix-cover-otp-18.0
2015-03-28 e3c9d24 Update meck_cover for OTP 18.0
2015-03-28 79cb5c9 Change macro name for namespaced types
2015-03-30 b7024d3 Merge pull request #138 from gomoripeti/travis-run-tests
2015-03-29 2b5bc62 Run tests in travis
stats_hero
2015-04-24 483b95f Remove unused Port variable
2015-04-23 2295ab6 Merge pull request #11 from chef/ssd/statsd-support
2015-04-23 28c614f Ensure protocol config actually makes it to the workers.
2015-01-12 0789682 Use an accumulator for read_at_least/1
2015-01-12 e210cbc Add read_at_least/1 to capture_udp test scaffold.
2014-12-12 6f70304 Configurably send statsd-compatible messages

cc @chef/lob


DPG, add allowed enum value in Javadoc

As we convert Enum to String in interface, user will need to know known Enum value for these String parameter (required or optional).
Hence Javadoc is the only way to go.

A probably solution, is to modify the "description" when convert Enum to String in parameter map.

something like this in python
https://user-images.githubusercontent.com/70930885/170236357-2b57b5c3-ab76-4b66-9a0c-b06c857bbc0f.png


Documentation, Style and scripting interfaces update

Original report (archived issue) by Nate Koenig (Bitbucket: Nathan Koenig).

Summary
The documentation,  code style, and scripting interfaces in this library needs to be updated. This issue will track progress.
Work to be done
For each class:

Create an example in the examples folder. This example should then be used as a doxygen \snippet in the class's doxygen description.

Check spelling.

Check for code style. Set functions should start with Set. Don't use const with POD types. Etc.

Create a scripting interface. See Angle.i as an example.

Add more tests so that  coverage is as close to 100% as possible.

Target changes to ign-math6. Also, target main with any breaking changes.

Status

[x] Angle. See pull request #325 and pull request #326
[ ] AxisAlignedBox
[ ] Box
[ ] Color
[ ] Cylinder
[ ] DiffDriveOdometry
[ ] Filter
[ ] Frustum
[ ] graph/Edge
[ ] graph/GraphAlgorithms
[ ] graph/Graph
[ ] graph/Vertex
[x] Helpers. See pull request #330.
[ ] Inertial
[ ] Kmeans
[ ] Line2
[ ] Line3
[ ] MassMatrix3
[ ] Material
[ ] MaterialType
[x] Matrix3. See pull request #328
[ ] Matrix4
[ ] MovingWindowFilter
[ ] OrientedBox
[ ] PID
[ ] Plane
[x] Pose3. See pull request #329.
[x] Quaternion. See pull request #327.
[ ] Rand
[ ] RollingMean
[ ] RotationSpline
[ ] SemanticVersion
[ ] SignalStats
[ ] Sphere
[ ] SphericalCoordiantes
[ ] Spline
[ ] Stopwatch
[x] Temperature. See pull request #339.
[ ] Triangle3
[ ] Triangle
[ ] Vector2
[ ] Vector3
[ ] Vector3Stats
[ ] Vector4

we should consider providing conversion functions between our ignition math vector and matrix types and numpy arrays.

#216 - Sets up SWIG to create bindings to python and create python examples and tests for all the classes that already have a SWIG interface (used for ruby)
After the previous is merged, PRs will be adding a swig interface to the remaining classes only for python. (+test)

At the moment, the python interface we are generating is providing the access to the classes methods using the Cpp name convention (e.g. in python you would use Temperature.CelsiusToKelvin(temp) to invoke the method). This could be modified, seemingly with little effort, using the %rename(celsius_to_kelvin) CelsiusToKelvin; SWIG directive in the interface file to get an interface with the PEP8 name convention as used in ROS2.
Would this be a better approach? Or would it be better to leave it matching the Cpp name convention?

At the moment, the python interface we are generating is providing the access to the classes methods using the Cpp name convention (e.g. in python you would use Temperature.CelsiusToKelvin(temp) to invoke the method). This could be modified, seemingly with little effort, using the %rename(celsius_to_kelvin) CelsiusToKelvin; SWIG directive in the interface file to get an interface with the PEP8 name convention as used in ROS2.
Would this be a better approach? Or would it be better to leave it matching the Cpp name convention?

As discussed during the weekly meeting if this isn't much effort we should match ROS2/PEP8 convention.

This issue is mixing a lot of different things. I've broken it into new issues:

Create an example in the examples folder. This example should then be used as a doxygen \snippet in the class's doxygen description.

https://github.com/ignitionrobotics/ign-math/issues/300

Check spelling.

https://github.com/ignitionrobotics/ign-math/issues/303

Check for code style. Set functions should start with Set. Don't use const with POD types. Etc.

https://github.com/ignitionrobotics/ign-math/issues/301

Create a scripting interface. See Angle.i as an example.

https://github.com/ignitionrobotics/ign-math/issues/302

Add more tests so that  coverage is as close to 100% as possible.

Coverage is already 100%


Rewrite configuration init to handle no-dram mode

We also need to set the correct dram size in both dram/no-dram modes, when the manycore hb_mc_config_t struct is initialized. The cuda memory allocator should throw an error if it runs out of space (which it doesn't right now, causing memory locations to get overwritten and tiles to run with wrong symbol values  and spin out of control with invalid EVA accesses)
https://github.com/bespoke-silicon-group/bsg_f1/blob/master/cl_manycore/libraries/bsg_manycore_cuda.cpp#L1295

Related to #333

@bornaehsani I think this is related to our discussion yesterday. Yes?

Very much yes, if we include a parameter dram/no-dram inside ROM, the CUDA API can call hb_mc_disable_dram inside device_init, which means we will not need two versions of each regression tests.

We were discussing this earlier. What was the conclusion?

@bornaehsani @mrutt92 I think this is solved, right?


Njray/sharepoint2

@njray,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/reference-architectures/SharePoint/index.md
:warning:Warning
View
Details

docs/reference-architectures/SharePoint/index.md

Line 328: [Warning] Invalid file link:(~/reference-architectures/SharePoint/CLI).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

index.md for larry/sharepoint containing latest deploy steps

Nanette - appears there a issue from Bennage bot

The latest doc should be in the sharepoint-ra branch
At least, that's the one I made edits on.

Dup of #176


SP5: LayoutEngines.Matched should be public

https://github.com/ScottPlot/ScottPlot/blob/42987b60b6fb90e94d0fb67a60c7dfafc73d8d9a/src/ScottPlot5/ScottPlot5/LayoutEngines/Matched.cs#L6

Hi, I've made changes. Here's my PR
https://github.com/proplunger/ScottPlot/pull/1

Hi @proplunger, thank you so much for this! I'm disappointed it took me so long to merge this in, but I'm happy to do it today. Thanks again!


[sw/device] Consider adding base/math.h

This is a follow of PR [lowrisc/opentitan#5973]. The sw/device codebase has many instances of ad-hoc rounding and alignment operations. This issue is to track the introduction of a math module providing a canonical implementation of such functions.

// Assumes `alignment` is a power of two.
size_t misalignment = num & (alignment - 1);
if (misalignment > 0) {
  num += alignment - misalignment;
}

Is this still relevant?


ARROW-215 Add tox config

Benchmark will fail until we merge this because there is no tox.ini in the previous commit.


jbang: 0.58.0 -> 0.62.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/jbangdev/jbang/releases.
meta.description for jbang is: "Run java as scripts anywhere"
meta.homepage for jbang is: "https://https://www.jbang.dev/"
meta.changelog for jbang is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.62.0 with grep in /nix/store/kqanfi1ibviavda13pn2hjv2bzfbx5d5-jbang-0.62.0

directory tree listing: https://gist.github.com/c94a840fcf90e6fbfca34d6b614c59ee

du listing: https://gist.github.com/d4f315567cf22a9ce6bbbeaa69c9d0df

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
jbang

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kqanfi1ibviavda13pn2hjv2bzfbx5d5-jbang-0.62.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jbang https://github.com/r-ryantm/nixpkgs/archive/00305cca18fbaef088f87362350839929f0e42c5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kqanfi1ibviavda13pn2hjv2bzfbx5d5-jbang-0.62.0
ls -la /nix/store/kqanfi1ibviavda13pn2hjv2bzfbx5d5-jbang-0.62.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jbang

Maintainer pings
cc @moaxcp for testing.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/jbang-in-nixpkgs/11052/2

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/jbang-in-nixpkgs/11052/2


huge amounts of data being written into .local/share/sddm/wayland-session.log after each reload

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit 29cdd7de1f8d99462915540569fbe54f10f609f4 dirty (layers: minor fixes for new animations).
Date: Wed Feb 28 16:59:45 2024
Tag: v0.36.0-4-g29cdd7de

flags: (if any)

System Information:
System name: Linux
Node name: dell-xps
Release: 6.7.6-zen1-1.1-zen
Version: #1 ZEN SMP PREEMPT_DYNAMIC Sat, 24 Feb 2024 04:03:29 +0000

GPU information:
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller])

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

Bug or Regression?
Bug
Description
My home folder was full. After investigating, I had a 37GB file in ~/.local/share/sddm/wayland-session.log. Not sure if this is an issue with sddm or hyprland, but it does appear to increase in size after each hyprctl reload. (tried to run it once to see how much per reload, it was ~10KB, but it is now going up QUICKLY
got from 100MB to 3 GB in a few seconds, I've now deleted it.
How to reproduce
Unsure if hyprctl reload is the culprit, after starting the session it did only appear to go up after each run.
Crash reports, logs, images, videos
After 1 reload (8 -> 28 KiB)
wayland-session.log-1.txt
After 2 reloads (28 -> started going up by itself, idk, 640MB when I stopped it after a couple of seconds)
wayland-session.log-2.txt.gz

what does it write there, tho? Looks like an sddm issue

Yeah sorry, had to restart the session to upload that, as I had already deleted it (for obvious reasons)

Ok it does appear to increase by 20 KB per reload (7.8, 28, 48, 69, 89, ...) and then at some point blow up and start increasing at ~100MB per second

Looking into it, it appears to be because of lxpolkit.
Interestingly, removing the exec line and starting it manually will still cause this issue. Also, the logs still keep growing after I kill the process. Don't really know how polkit stuff works tho
Unrelated, but do you have any idea what might be causing these xkbcomp warnings?
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server

no clue wrt either. Not a hyprland issue tho, it seems