stirling support for boringcrypto as used by the 'boringcrypto' version of Golang

It would be great if stirling were able to decode TLS flows from the 'boringcrypto' versions of Golang.
Stirling would need to be modified to have uprobes for this version of Golang: https://go.googlesource.com/go/+/dev.boringcrypto
This version of Golang is used in order to have FIPS compliant Go programs.  We at VMware use it extensively.
Alternatives:
Don't use the boringcrypto version of Golang.  This is not an option in cases where one wants to claim FIPS compliance for their Go program.

@kay-ge while working on #692, I realized that our existing Go TLS tracing already covers Go applications using boringcrypto (as long as DWARF debug information is available).
Can you confirm if your boringcrypto applications had missing traffic or was it because our documentation only states Go TLS and OpenSSL support?
I was able to update Pixie's go tls tracing tests to use binaries opted into GOEXPERIMENT=boringcrypto and the tests pass (commit). This is because the functions we hook into (crypto/tls.(*Conn) Write and Read) are triggered for both the standard crypto and boringcrypto case. I'm going to add a boringcrypto acceptance test to the Pixie repo so we are regularly exercising this.

Test output
# Verify that boringcrypto is active

ddelnano@vigenere:~/code/pixie (main) $ bazel build //src/stirling/testing/demo_apps/go_grpc_tls_pl/server:golang_1_19_grpc_tls_server_binary
ddelnano@vigenere:~/code/pixie (main) $ bazel build //src/stirling/testing/demo_apps/go_grpc_tls_pl/server:golang_1_20_grpc_tls_server_binary

ddelnano@vigenere:~/code/pixie (main) $ ~/go/bin/goversion -crypto bazel-bin/src/stirling/testing/demo_apps/go_grpc_tls_pl/server/golang_1_19_grpc_tls_server_binary
bazel-bin/src/stirling/testing/demo_apps/go_grpc_tls_pl/server/golang_1_19_grpc_tls_server_binary go1.19.9 X:boringcrypto (boring crypto)

ddelnano@vigenere:~/code/pixie (main) $ ~/go/bin/goversion -crypto bazel-bin/src/stirling/testing/demo_apps/go_grpc_tls_pl/server/golang_1_20_grpc_tls_server_binary
bazel-bin/src/stirling/testing/demo_apps/go_grpc_tls_pl/server/golang_1_20_grpc_tls_server_binary go1.20.4 X:boringcrypto,nocoverageredesign (boring crypto)

# Verify that the testing is working
ddelnano@vigenere:~/code/pixie (main) $ ./scripts/sudo_bazel_run.sh src/stirling/source_connectors/socket_tracer:go_tls_trace_bpf_test
INFO: Invocation ID: 6d5c214e-68fc-4ff2-bdb2-cee3030a7c35
INFO: Streaming build results to: https://bb.corp.pixielabs.ai/invocation/6d5c214e-68fc-4ff2-bdb2-cee3030a7c35
INFO: Build option --run_under has changed, discarding analysis cache.
INFO: Analyzed target //src/stirling/source_connectors/socket_tracer:go_tls_trace_bpf_test (365 packages loaded, 68206 targets configured).
INFO: Found 1 target...
Target //src/stirling/source_connectors/socket_tracer:go_tls_trace_bpf_test up-to-date:
  bazel-bin/src/stirling/source_connectors/socket_tracer/go_tls_trace_bpf_test
INFO: Elapsed time: 11.184s, Critical Path: 3.90s
INFO: 232 processes: 219 remote cache hit, 3 internal, 10 linux-sandbox.
INFO: Running command line: external/bazel_tools/tools/test/test-setup.sh /bin/bash -c '"$@"' /bin/bash sudo src/stirling/source_connectors/socket_tracer/go_tls_trace_bpf_test
INFO: Streaming build results to: https://bb.corp.pixielabs.ai/invocation/6d5c214e-68fc-4ff2-bdb2-cee3030a7c35
INFO: Build completed successfully, 232 total actions
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //src/stirling/source_connectors/socket_tracer:go_tls_trace_bpf_test
-----------------------------------------------------------------------------
I20230606 21:36:17.353314 3753491 env.cc:47] Started: src/stirling/source_connectors/socket_tracer/go_tls_trace_bpf_test
[==========] Running 8 tests from 4 test suites.
[----------] Global test environment set-up.
[----------] 2 tests from GoTLSTraceTest/0, where TypeParam = px::stirling::Go1_17TLSClientServerContainers
[ RUN      ] GoTLSTraceTest/0.BasicHTTP
I20230606 21:36:17.477846 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_17_https_server
I20230606 21:36:17.579900 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_17_https_client
I20230606 21:36:17.579963 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --name=https_server_1300236325333127 localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_17_https_server
I20230606 21:36:17.833567 3753491 container_runner.cc:144] Container https_server_1300236325333127 status: running
I20230606 21:36:17.866173 3753491 container_runner.cc:175] Container https_server_1300236325333127 process PID: 3753670
I20230606 21:36:17.866202 3753491 container_runner.cc:177] Container https_server_1300236325333127 waiting for log message: Starting HTTPS service
I20230606 21:36:17.898833 3753491 container_runner.cc:189] Container https_server_1300236325333127 status: running
I20230606 21:36:17.898867 3753491 container_runner.cc:225] Container https_server_1300236325333127 is ready.
I20230606 21:36:17.899278 3753491 linux_headers.cc:211] Found Linux kernel version using .note section.
I20230606 21:36:17.899297 3753491 source_connector.cc:35] Initializing source connector: socket_trace_connector
I20230606 21:36:17.899320 3753491 linux_headers.cc:94] Obtained Linux version string from `uname`: 5.19.0-1022-gcp
I20230606 21:36:17.899329 3753491 linux_headers.cc:642] Detected kernel release (uname -r): 5.19.0-1022-gcp
I20230606 21:36:17.899365 3753491 bcc_wrapper.cc:121] Using linux headers found at /lib/modules/5.19.0-1022-gcp/build for BCC runtime.
I20230606 21:36:17.899418 3753491 bcc_wrapper.cc:170] Initializing BPF program ...
I20230606 21:36:26.323107 3753491 scoped_timer.h:48] Timer(init_bpf_program) : 8.42 s
I20230606 21:36:27.136358 3753491 socket_trace_connector.cc:427] Number of kprobes deployed = 40
I20230606 21:36:27.136401 3753491 socket_trace_connector.cc:428] Probes successfully deployed.
I20230606 21:36:27.136457 3753491 socket_trace_connector.cc:362] Initializing perf buffers with ncpus=96 and scaling_factor=0.0865385
I20230606 21:36:27.136494 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kData buffers across all cpus: 268038720
I20230606 21:36:27.136504 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kControl buffers across all cpus: 13353216
I20230606 21:36:27.241335 3753491 socket_trace_connector.cc:432] Number of perf buffers opened = 8
I20230606 21:36:27.654106 3753722 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:36:28.308135 3753722 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:36:28.933756 3753722 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:36:29.316942 3753722 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:36:29.712752 3753722 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:36:30.110132 3753722 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:36:30.493902 3753722 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:36:36.479471 3753722 uprobe_manager.cc:908] Number of uprobes deployed = 10283
I20230606 21:36:36.543285 3753762 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:36:36.580655 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --network=container:https_server_1300236325333127 --name=https_client_1300255326022761 localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_17_https_client --http2=false --iters=2 --sub_iters=5
I20230606 21:36:36.814766 3753491 container_runner.cc:144] Container https_client_1300255326022761 status: running
I20230606 21:36:36.849220 3753491 container_runner.cc:175] Container https_client_1300255326022761 process PID: 3753827
I20230606 21:36:36.849249 3753491 container_runner.cc:177] Container https_client_1300255326022761 waiting for log message: {"status":"ok"}
I20230606 21:36:36.882223 3753491 container_runner.cc:189] Container https_client_1300255326022761 status: running
I20230606 21:36:36.882259 3753491 container_runner.cc:225] Container https_client_1300255326022761 is ready.
I20230606 21:36:38.097079 3753821 uprobe_manager.cc:908] Number of uprobes deployed = 37
I20230606 21:36:38.367131 3753884 uprobe_manager.cc:908] Number of uprobes deployed = 59
I20230606 21:36:43.551957 3753959 uprobe_manager.cc:908] Number of uprobes deployed = 18
I20230606 21:36:55.013135 3753491 container_runner.cc:53] podman rm -f https_client_1300255326022761 &>/dev/null
I20230606 21:36:55.045686 3753491 container_runner.cc:53] podman rm -f https_server_1300236325333127 &>/dev/null
[       OK ] GoTLSTraceTest/0.BasicHTTP (39063 ms)
[ RUN      ] GoTLSTraceTest/0.BasicHTTP2
I20230606 21:36:56.512127 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_17_https_server
I20230606 21:36:56.609123 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_17_https_client
I20230606 21:36:56.609201 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --name=https_server_1300275354575322 localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_17_https_server
I20230606 21:36:56.855082 3753491 container_runner.cc:144] Container https_server_1300275354575322 status: running
I20230606 21:36:56.886946 3753491 container_runner.cc:175] Container https_server_1300275354575322 process PID: 3754584
I20230606 21:36:56.886977 3753491 container_runner.cc:177] Container https_server_1300275354575322 waiting for log message: Starting HTTPS service
I20230606 21:36:56.918601 3753491 container_runner.cc:189] Container https_server_1300275354575322 status: running
I20230606 21:36:56.918632 3753491 container_runner.cc:225] Container https_server_1300275354575322 is ready.
I20230606 21:36:56.918870 3753491 source_connector.cc:35] Initializing source connector: socket_trace_connector
I20230606 21:36:56.918912 3753491 linux_headers.cc:94] Obtained Linux version string from `uname`: 5.19.0-1022-gcp
I20230606 21:36:56.918921 3753491 linux_headers.cc:642] Detected kernel release (uname -r): 5.19.0-1022-gcp
I20230606 21:36:56.918948 3753491 bcc_wrapper.cc:121] Using linux headers found at /lib/modules/5.19.0-1022-gcp/build for BCC runtime.
I20230606 21:36:56.919004 3753491 bcc_wrapper.cc:170] Initializing BPF program ...
I20230606 21:37:05.421617 3753491 scoped_timer.h:48] Timer(init_bpf_program) : 8.50 s
I20230606 21:37:06.229264 3753491 socket_trace_connector.cc:427] Number of kprobes deployed = 40
I20230606 21:37:06.229305 3753491 socket_trace_connector.cc:428] Probes successfully deployed.
I20230606 21:37:06.229362 3753491 socket_trace_connector.cc:362] Initializing perf buffers with ncpus=96 and scaling_factor=0.0865385
I20230606 21:37:06.229398 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kData buffers across all cpus: 268038720
I20230606 21:37:06.229406 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kControl buffers across all cpus: 13353216
I20230606 21:37:06.331228 3753491 socket_trace_connector.cc:432] Number of perf buffers opened = 8
I20230606 21:37:06.893393 3754788 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:07.358516 3754788 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:07.693328 3754788 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:08.121908 3754788 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:08.491451 3754788 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:08.888175 3754788 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:09.498785 3754788 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:15.461755 3754788 uprobe_manager.cc:908] Number of uprobes deployed = 10535
I20230606 21:37:15.526285 3754804 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:37:15.563195 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --network=container:https_server_1300275354575322 --name=https_client_1300294308565042 localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_17_https_client --http2=true --iters=2 --sub_iters=5
I20230606 21:37:15.720250 3753491 container_runner.cc:144] Container https_client_1300294308565042 status: running
I20230606 21:37:15.753818 3753491 container_runner.cc:175] Container https_client_1300294308565042 process PID: 3754861
I20230606 21:37:15.753849 3753491 container_runner.cc:177] Container https_client_1300294308565042 waiting for log message: {"status":"ok"}
I20230606 21:37:15.787252 3753491 container_runner.cc:189] Container https_client_1300294308565042 status: running
I20230606 21:37:15.787283 3753491 container_runner.cc:225] Container https_client_1300294308565042 is ready.
I20230606 21:37:17.074206 3754864 uprobe_manager.cc:908] Number of uprobes deployed = 37
I20230606 21:37:17.330798 3754926 uprobe_manager.cc:908] Number of uprobes deployed = 41
I20230606 21:37:17.615985 3754930 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:37:34.425158 3753491 container_runner.cc:53] podman rm -f https_client_1300294308565042 &>/dev/null
I20230606 21:37:34.457953 3753491 container_runner.cc:53] podman rm -f https_server_1300275354575322 &>/dev/null
[       OK ] GoTLSTraceTest/0.BasicHTTP2 (39468 ms)
[----------] 2 tests from GoTLSTraceTest/0 (78531 ms total)

[----------] 2 tests from GoTLSTraceTest/1, where TypeParam = px::stirling::Go1_18TLSClientServerContainers
[ RUN      ] GoTLSTraceTest/1.BasicHTTP
I20230606 21:37:35.982336 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_18_https_server
I20230606 21:37:36.081152 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_18_https_client
I20230606 21:37:36.081214 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --name=https_server_1300314826587724 localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_18_https_server
I20230606 21:37:36.307430 3753491 container_runner.cc:144] Container https_server_1300314826587724 status: running
I20230606 21:37:36.339200 3753491 container_runner.cc:175] Container https_server_1300314826587724 process PID: 3755337
I20230606 21:37:36.339228 3753491 container_runner.cc:177] Container https_server_1300314826587724 waiting for log message: Starting HTTPS service
I20230606 21:37:36.369964 3753491 container_runner.cc:189] Container https_server_1300314826587724 status: running
I20230606 21:37:36.369990 3753491 container_runner.cc:225] Container https_server_1300314826587724 is ready.
I20230606 21:37:36.370245 3753491 source_connector.cc:35] Initializing source connector: socket_trace_connector
I20230606 21:37:36.370290 3753491 linux_headers.cc:94] Obtained Linux version string from `uname`: 5.19.0-1022-gcp
I20230606 21:37:36.370299 3753491 linux_headers.cc:642] Detected kernel release (uname -r): 5.19.0-1022-gcp
I20230606 21:37:36.370324 3753491 bcc_wrapper.cc:121] Using linux headers found at /lib/modules/5.19.0-1022-gcp/build for BCC runtime.
I20230606 21:37:36.370373 3753491 bcc_wrapper.cc:170] Initializing BPF program ...
I20230606 21:37:44.779799 3753491 scoped_timer.h:48] Timer(init_bpf_program) : 8.41 s
I20230606 21:37:45.587615 3753491 socket_trace_connector.cc:427] Number of kprobes deployed = 40
I20230606 21:37:45.587656 3753491 socket_trace_connector.cc:428] Probes successfully deployed.
I20230606 21:37:45.587711 3753491 socket_trace_connector.cc:362] Initializing perf buffers with ncpus=96 and scaling_factor=0.0865385
I20230606 21:37:45.587749 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kData buffers across all cpus: 268038720
I20230606 21:37:45.587757 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kControl buffers across all cpus: 13353216
I20230606 21:37:45.688004 3753491 socket_trace_connector.cc:432] Number of perf buffers opened = 8
I20230606 21:37:46.144762 3755386 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:46.672156 3755386 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:47.098901 3755386 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:47.371347 3755386 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:47.732771 3755386 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:48.059239 3755386 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:48.672499 3755386 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:37:54.677088 3755386 uprobe_manager.cc:908] Number of uprobes deployed = 10742
I20230606 21:37:54.742759 3755398 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:37:54.778105 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --network=container:https_server_1300314826587724 --name=https_client_1300333523475675 localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_18_https_client --http2=false --iters=2 --sub_iters=5
I20230606 21:37:54.970698 3753491 container_runner.cc:144] Container https_client_1300333523475675 status: running
I20230606 21:37:55.003922 3753491 container_runner.cc:175] Container https_client_1300333523475675 process PID: 3755445
I20230606 21:37:55.003962 3753491 container_runner.cc:177] Container https_client_1300333523475675 waiting for log message: {"status":"ok"}
I20230606 21:37:55.037881 3753491 container_runner.cc:189] Container https_client_1300333523475675 status: running
I20230606 21:37:55.037921 3753491 container_runner.cc:225] Container https_client_1300333523475675 is ready.
W20230606 21:37:56.301640 3755462 uprobe_manager.cc:760] Cannot analyze binary /proc/3755446/root/usr/bin/dash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3755446/root/usr/bin/dash
I20230606 21:37:56.301682 3755462 uprobe_manager.cc:908] Number of uprobes deployed = 64
I20230606 21:37:57.803908 3755523 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:38:02.934703 3755694 uprobe_manager.cc:908] Number of uprobes deployed = 18
I20230606 21:38:13.373070 3753491 container_runner.cc:53] podman rm -f https_client_1300333523475675 &>/dev/null
I20230606 21:38:13.404954 3753491 container_runner.cc:53] podman rm -f https_server_1300314826587724 &>/dev/null
[       OK ] GoTLSTraceTest/1.BasicHTTP (38447 ms)
[ RUN      ] GoTLSTraceTest/1.BasicHTTP2
I20230606 21:38:14.423771 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_18_https_server
I20230606 21:38:14.519914 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_18_https_client
I20230606 21:38:14.519966 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --name=https_server_1300353265340468 localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_18_https_server
I20230606 21:38:14.740466 3753491 container_runner.cc:144] Container https_server_1300353265340468 status: running
I20230606 21:38:14.772504 3753491 container_runner.cc:175] Container https_server_1300353265340468 process PID: 3756360
I20230606 21:38:14.772527 3753491 container_runner.cc:177] Container https_server_1300353265340468 waiting for log message: Starting HTTPS service
I20230606 21:38:14.802927 3753491 container_runner.cc:189] Container https_server_1300353265340468 status: running
I20230606 21:38:14.802945 3753491 container_runner.cc:225] Container https_server_1300353265340468 is ready.
I20230606 21:38:14.803196 3753491 source_connector.cc:35] Initializing source connector: socket_trace_connector
I20230606 21:38:14.803244 3753491 linux_headers.cc:94] Obtained Linux version string from `uname`: 5.19.0-1022-gcp
I20230606 21:38:14.803253 3753491 linux_headers.cc:642] Detected kernel release (uname -r): 5.19.0-1022-gcp
I20230606 21:38:14.803279 3753491 bcc_wrapper.cc:121] Using linux headers found at /lib/modules/5.19.0-1022-gcp/build for BCC runtime.
I20230606 21:38:14.803329 3753491 bcc_wrapper.cc:170] Initializing BPF program ...
I20230606 21:38:23.275279 3753491 scoped_timer.h:48] Timer(init_bpf_program) : 8.47 s
I20230606 21:38:24.087327 3753491 socket_trace_connector.cc:427] Number of kprobes deployed = 40
I20230606 21:38:24.087368 3753491 socket_trace_connector.cc:428] Probes successfully deployed.
I20230606 21:38:24.087424 3753491 socket_trace_connector.cc:362] Initializing perf buffers with ncpus=96 and scaling_factor=0.0865385
I20230606 21:38:24.087460 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kData buffers across all cpus: 268038720
I20230606 21:38:24.087469 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kControl buffers across all cpus: 13353216
I20230606 21:38:24.189576 3753491 socket_trace_connector.cc:432] Number of perf buffers opened = 8
I20230606 21:38:24.435456 3756587 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:38:25.073774 3756587 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:38:25.551555 3756587 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:38:25.941008 3756587 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:38:26.375900 3756587 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:38:26.770718 3756587 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:38:27.219740 3756587 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:38:33.561997 3756587 uprobe_manager.cc:908] Number of uprobes deployed = 10958
I20230606 21:38:33.628572 3756600 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:38:33.663100 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --network=container:https_server_1300353265340468 --name=https_client_1300372408469798 localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_18_https_client --http2=true --iters=2 --sub_iters=5
I20230606 21:38:33.856223 3753491 container_runner.cc:144] Container https_client_1300372408469798 status: running
I20230606 21:38:33.888442 3753491 container_runner.cc:175] Container https_client_1300372408469798 process PID: 3756649
I20230606 21:38:33.888470 3753491 container_runner.cc:177] Container https_client_1300372408469798 waiting for log message: {"status":"ok"}
I20230606 21:38:33.920763 3753491 container_runner.cc:189] Container https_client_1300372408469798 status: running
I20230606 21:38:33.920789 3753491 container_runner.cc:225] Container https_client_1300372408469798 is ready.
W20230606 21:38:35.195266 3756665 uprobe_manager.cc:760] Cannot analyze binary /proc/3756647/root/usr/bin/dash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3756647/root/usr/bin/dash
W20230606 21:38:35.195317 3756665 uprobe_manager.cc:760] Cannot analyze binary /proc/3756648/root/usr/bin/podman for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3756648/root/usr/bin/podman
I20230606 21:38:35.426390 3756665 uprobe_manager.cc:908] Number of uprobes deployed = 96
I20230606 21:38:37.849357 3756732 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:38:52.301106 3753491 container_runner.cc:53] podman rm -f https_client_1300372408469798 &>/dev/null
I20230606 21:38:52.333333 3753491 container_runner.cc:53] podman rm -f https_server_1300353265340468 &>/dev/null
[       OK ] GoTLSTraceTest/1.BasicHTTP2 (39306 ms)
[----------] 2 tests from GoTLSTraceTest/1 (77753 ms total)

[----------] 2 tests from GoTLSTraceTest/2, where TypeParam = px::stirling::Go1_19TLSClientServerContainers
[ RUN      ] GoTLSTraceTest/2.BasicHTTP
I20230606 21:38:53.742610 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_19_https_server
I20230606 21:38:53.860426 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_19_https_client
I20230606 21:38:53.860493 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --name=https_server_1300392605866847 localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_19_https_server
I20230606 21:38:54.112104 3753491 container_runner.cc:144] Container https_server_1300392605866847 status: running
I20230606 21:38:54.143815 3753491 container_runner.cc:175] Container https_server_1300392605866847 process PID: 3757135
I20230606 21:38:54.143842 3753491 container_runner.cc:177] Container https_server_1300392605866847 waiting for log message: Starting HTTPS service
I20230606 21:38:54.174379 3753491 container_runner.cc:189] Container https_server_1300392605866847 status: running
I20230606 21:38:54.174396 3753491 container_runner.cc:225] Container https_server_1300392605866847 is ready.
I20230606 21:38:54.174649 3753491 source_connector.cc:35] Initializing source connector: socket_trace_connector
I20230606 21:38:54.174698 3753491 linux_headers.cc:94] Obtained Linux version string from `uname`: 5.19.0-1022-gcp
I20230606 21:38:54.174707 3753491 linux_headers.cc:642] Detected kernel release (uname -r): 5.19.0-1022-gcp
I20230606 21:38:54.174733 3753491 bcc_wrapper.cc:121] Using linux headers found at /lib/modules/5.19.0-1022-gcp/build for BCC runtime.
I20230606 21:38:54.174782 3753491 bcc_wrapper.cc:170] Initializing BPF program ...
I20230606 21:39:02.647487 3753491 scoped_timer.h:48] Timer(init_bpf_program) : 8.47 s
I20230606 21:39:03.459894 3753491 socket_trace_connector.cc:427] Number of kprobes deployed = 40
I20230606 21:39:03.459937 3753491 socket_trace_connector.cc:428] Probes successfully deployed.
I20230606 21:39:03.459993 3753491 socket_trace_connector.cc:362] Initializing perf buffers with ncpus=96 and scaling_factor=0.0865385
I20230606 21:39:03.460036 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kData buffers across all cpus: 268038720
I20230606 21:39:03.460047 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kControl buffers across all cpus: 13353216
I20230606 21:39:03.562886 3753491 socket_trace_connector.cc:432] Number of perf buffers opened = 8
I20230606 21:39:03.827862 3757186 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:39:04.302207 3757186 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:39:04.689600 3757186 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:39:05.074455 3757186 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:39:05.456552 3757186 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:39:05.915161 3757186 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:39:06.506151 3757186 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
W20230606 21:39:11.220996 3757186 uprobe_manager.cc:760] Cannot analyze binary /proc/3757182/root/usr/bin/sleep for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3757182/root/usr/bin/sleep
I20230606 21:39:12.720753 3757186 uprobe_manager.cc:908] Number of uprobes deployed = 11174
I20230606 21:39:12.789543 3757316 uprobe_manager.cc:908] Number of uprobes deployed = 18
I20230606 21:39:12.822078 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --network=container:https_server_1300392605866847 --name=https_client_1300411567444612 localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_19_https_client --http2=false --iters=2 --sub_iters=5
I20230606 21:39:13.015336 3753491 container_runner.cc:144] Container https_client_1300411567444612 status: running
I20230606 21:39:13.047950 3753491 container_runner.cc:175] Container https_client_1300411567444612 process PID: 3757368
I20230606 21:39:13.047983 3753491 container_runner.cc:177] Container https_client_1300411567444612 waiting for log message: {"status":"ok"}
I20230606 21:39:13.079881 3753491 container_runner.cc:189] Container https_client_1300411567444612 status: running
I20230606 21:39:13.079913 3753491 container_runner.cc:225] Container https_client_1300411567444612 is ready.
W20230606 21:39:14.333946 3757385 uprobe_manager.cc:760] Cannot analyze binary /proc/3757366/root/usr/bin/dash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3757366/root/usr/bin/dash
W20230606 21:39:14.333994 3757385 uprobe_manager.cc:760] Cannot analyze binary /proc/3757367/root/usr/bin/podman for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3757367/root/usr/bin/podman
I20230606 21:39:14.565354 3757385 uprobe_manager.cc:908] Number of uprobes deployed = 96
I20230606 21:39:15.922740 3757450 uprobe_manager.cc:908] Number of uprobes deployed = 18
W20230606 21:39:17.236884 3758643 uprobe_manager.cc:760] Cannot analyze binary /proc/3758554/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758554/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:39:17.236941 3758643 uprobe_manager.cc:760] Cannot analyze binary /proc/3758555/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758555/root/usr/bin/bash
W20230606 21:39:17.238430 3758643 uprobe_manager.cc:760] Cannot analyze binary /proc/3758579/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758579/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:39:17.239379 3758643 uprobe_manager.cc:760] Cannot analyze binary /proc/3758584/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758584/root/usr/bin/bash
I20230606 21:39:17.307154 3758643 uprobe_manager.cc:908] Number of uprobes deployed = 108
W20230606 21:39:17.465656 3758706 uprobe_manager.cc:760] Cannot analyze binary /proc/3758663/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758663/root/usr/bin/bash
W20230606 21:39:17.465718 3758706 uprobe_manager.cc:760] Cannot analyze binary /proc/3758667/root/usr/bin/sleep for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758667/root/usr/bin/sleep
W20230606 21:39:17.465739 3758706 uprobe_manager.cc:760] Cannot analyze binary /proc/3758668/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758668/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:39:17.465756 3758706 uprobe_manager.cc:760] Cannot analyze binary /proc/3758669/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758669/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:39:17.465775 3758706 uprobe_manager.cc:760] Cannot analyze binary /proc/3758670/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758670/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:39:17.465792 3758706 uprobe_manager.cc:760] Cannot analyze binary /proc/3758671/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758671/root/usr/bin/bash
W20230606 21:39:17.465808 3758706 uprobe_manager.cc:760] Cannot analyze binary /proc/3758672/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758672/root/usr/bin/bash
I20230606 21:39:17.465826 3758706 uprobe_manager.cc:908] Number of uprobes deployed = 108
I20230606 21:39:17.600340 3758777 uprobe_manager.cc:908] Number of uprobes deployed = 63
W20230606 21:39:17.890043 3758869 uprobe_manager.cc:760] Cannot analyze binary /proc/3758839/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758839/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:39:17.890985 3758869 uprobe_manager.cc:760] Cannot analyze binary /proc/3758843/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758843/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:39:17.891009 3758869 uprobe_manager.cc:760] Cannot analyze binary /proc/3758844/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758844/root/usr/bin/bash
I20230606 21:39:17.891027 3758869 uprobe_manager.cc:908] Number of uprobes deployed = 99
W20230606 21:39:18.003372 3758939 uprobe_manager.cc:760] Cannot analyze binary /proc/3758916/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758916/root/usr/bin/bash
W20230606 21:39:18.017271 3758939 uprobe_manager.cc:760] Cannot analyze binary /proc/3758929/root/usr/bin/sleep for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758929/root/usr/bin/sleep
I20230606 21:39:18.042614 3758939 uprobe_manager.cc:908] Number of uprobes deployed = 135
I20230606 21:39:18.155433 3758961 uprobe_manager.cc:908] Number of uprobes deployed = 45
W20230606 21:39:18.452198 3759000 uprobe_manager.cc:760] Cannot analyze binary /proc/3758989/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/udf/registry_test for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758989/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/udf/registry_test
W20230606 21:39:18.452253 3759000 uprobe_manager.cc:760] Cannot analyze binary /proc/3758990/root/usr/bin/python3.10 for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3758990/root/usr/bin/python3.10
I20230606 21:39:18.452275 3759000 uprobe_manager.cc:908] Number of uprobes deployed = 90
W20230606 21:39:18.743194 3759006 uprobe_manager.cc:760] Cannot analyze binary /proc/3759004/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/udf/registry_test for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3759004/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/udf/registry_test
W20230606 21:39:18.743256 3759006 uprobe_manager.cc:760] Cannot analyze binary /proc/3759005/root/usr/bin/python3.10 for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3759005/root/usr/bin/python3.10
I20230606 21:39:18.743271 3759006 uprobe_manager.cc:908] Number of uprobes deployed = 36
I20230606 21:39:19.188568 3759019 uprobe_manager.cc:908] Number of uprobes deployed = 27
I20230606 21:39:19.367743 3759023 uprobe_manager.cc:908] Number of uprobes deployed = 27
I20230606 21:39:20.391285 3759041 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:39:20.694757 3759042 uprobe_manager.cc:908] Number of uprobes deployed = 72
I20230606 21:39:20.860173 3759055 uprobe_manager.cc:908] Number of uprobes deployed = 54
I20230606 21:39:21.086771 3759060 uprobe_manager.cc:908] Number of uprobes deployed = 54
I20230606 21:39:21.584852 3759071 uprobe_manager.cc:908] Number of uprobes deployed = 54
I20230606 21:39:22.663909 3759085 uprobe_manager.cc:908] Number of uprobes deployed = 54
I20230606 21:39:22.806337 3759090 uprobe_manager.cc:908] Number of uprobes deployed = 27
I20230606 21:39:22.989348 3759095 uprobe_manager.cc:908] Number of uprobes deployed = 27
I20230606 21:39:24.359383 3759128 go_syms.cc:66] Falling back to the runtime.buildVersion symbol for go version detection
W20230606 21:39:24.418660 3759128 uprobe_manager.cc:813] Failed to attach HTTP2 Uprobes to /proc/3759100/root/usr/bin/podman: Internal : Unable to find offset for binary /proc/3759100/root/usr/bin/podman symbol github.com/containers/podman/vendor/google.golang.org/grpc/internal/transport.(*http2Client).operateHeaders address 0
I20230606 21:39:24.572408 3759128 uprobe_manager.cc:908] Number of uprobes deployed = 90
I20230606 21:39:54.677610 3753491 container_runner.cc:53] podman rm -f https_client_1300411567444612 &>/dev/null
I20230606 21:39:54.776916 3753491 container_runner.cc:53] podman rm -f https_server_1300392605866847 &>/dev/null
[       OK ] GoTLSTraceTest/2.BasicHTTP (64692 ms)
[ RUN      ] GoTLSTraceTest/2.BasicHTTP2
I20230606 21:39:58.507894 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_19_https_server
I20230606 21:39:58.662302 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_19_https_client
I20230606 21:39:58.662384 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --name=https_server_1300457407755886 localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_19_https_server
I20230606 21:39:58.974414 3753491 container_runner.cc:144] Container https_server_1300457407755886 status: running
I20230606 21:39:59.012107 3753491 container_runner.cc:175] Container https_server_1300457407755886 process PID: 3770606
I20230606 21:39:59.012161 3753491 container_runner.cc:177] Container https_server_1300457407755886 waiting for log message: Starting HTTPS service
I20230606 21:39:59.059190 3753491 container_runner.cc:189] Container https_server_1300457407755886 status: running
I20230606 21:39:59.059244 3753491 container_runner.cc:225] Container https_server_1300457407755886 is ready.
I20230606 21:39:59.059557 3753491 source_connector.cc:35] Initializing source connector: socket_trace_connector
I20230606 21:39:59.059628 3753491 linux_headers.cc:94] Obtained Linux version string from `uname`: 5.19.0-1022-gcp
I20230606 21:39:59.059643 3753491 linux_headers.cc:642] Detected kernel release (uname -r): 5.19.0-1022-gcp
I20230606 21:39:59.059687 3753491 bcc_wrapper.cc:121] Using linux headers found at /lib/modules/5.19.0-1022-gcp/build for BCC runtime.
I20230606 21:39:59.059756 3753491 bcc_wrapper.cc:170] Initializing BPF program ...
I20230606 21:40:09.347512 3753491 scoped_timer.h:48] Timer(init_bpf_program) : 10.29 s
I20230606 21:40:10.167308 3753491 socket_trace_connector.cc:427] Number of kprobes deployed = 40
I20230606 21:40:10.167349 3753491 socket_trace_connector.cc:428] Probes successfully deployed.
I20230606 21:40:10.167404 3753491 socket_trace_connector.cc:362] Initializing perf buffers with ncpus=96 and scaling_factor=0.0865385
I20230606 21:40:10.167441 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kData buffers across all cpus: 268038720
I20230606 21:40:10.167452 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kControl buffers across all cpus: 13353216
I20230606 21:40:10.272289 3753491 socket_trace_connector.cc:432] Number of perf buffers opened = 8
I20230606 21:40:10.742357 3774748 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:11.255637 3774748 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:11.648445 3774748 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:12.014964 3774748 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:12.364245 3774748 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:12.700414 3774748 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:13.330469 3774748 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
W20230606 21:40:17.898676 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773208/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773208/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:40:17.898737 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773214/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773214/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:40:17.898757 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773215/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773215/root/usr/bin/bash
W20230606 21:40:17.898777 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773227/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/planner/compiler/ast_visitor_test for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773227/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/planner/compiler/ast_visitor_test
W20230606 21:40:17.898794 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773228/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773228/root/usr/bin/bash
W20230606 21:40:17.898813 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773235/root/usr/bin/sleep for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773235/root/usr/bin/sleep
W20230606 21:40:17.898830 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773684/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773684/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:40:17.898847 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773685/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773685/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:40:17.898865 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773686/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773686/root/usr/bin/bash
W20230606 21:40:17.898882 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773696/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/planner/compiler/compiler_test for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773696/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/planner/compiler/compiler_test
W20230606 21:40:17.898900 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773697/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773697/root/usr/bin/bash
W20230606 21:40:17.898916 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773701/root/usr/bin/sleep for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773701/root/usr/bin/sleep
W20230606 21:40:17.898932 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773702/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773702/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:40:17.898948 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773703/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773703/root/home/james/.cache/bazel/_bazel_james/install/edecd2b1233e0abfae42ec33ee10b762/linux-sandbox
W20230606 21:40:17.898967 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773704/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773704/root/usr/bin/bash
W20230606 21:40:17.898985 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773714/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/carnot_test for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773714/root/home/james/.cache/bazel/_bazel_james/378b5f37a0ee36a56febb1595fb99436/execroot/px/bazel-out/k8-fastbuild/bin/src/carnot/carnot_test
W20230606 21:40:17.899003 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773715/root/usr/bin/bash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773715/root/usr/bin/bash
W20230606 21:40:17.899019 3774748 uprobe_manager.cc:760] Cannot analyze binary /proc/3773719/root/usr/bin/sleep for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3773719/root/usr/bin/sleep
I20230606 21:40:19.448841 3774748 uprobe_manager.cc:908] Number of uprobes deployed = 11390
I20230606 21:40:19.517427 3774902 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:40:19.550380 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --network=container:https_server_1300457407755886 --name=https_client_1300478295745860 localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_19_https_client --http2=true --iters=2 --sub_iters=5
I20230606 21:40:19.781998 3753491 container_runner.cc:144] Container https_client_1300478295745860 status: running
I20230606 21:40:19.817109 3753491 container_runner.cc:175] Container https_client_1300478295745860 process PID: 3774969
I20230606 21:40:19.817147 3753491 container_runner.cc:177] Container https_client_1300478295745860 waiting for log message: {"status":"ok"}
I20230606 21:40:19.850095 3753491 container_runner.cc:189] Container https_client_1300478295745860 status: running
I20230606 21:40:19.850122 3753491 container_runner.cc:225] Container https_client_1300478295745860 is ready.
W20230606 21:40:21.098584 3774966 uprobe_manager.cc:760] Cannot analyze binary /proc/3774946/root/usr/bin/dash for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3774946/root/usr/bin/dash
W20230606 21:40:21.098644 3774966 uprobe_manager.cc:760] Cannot analyze binary /proc/3774947/root/usr/bin/podman for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3774947/root/usr/bin/podman
I20230606 21:40:21.098663 3774966 uprobe_manager.cc:908] Number of uprobes deployed = 55
I20230606 21:40:21.426651 3775028 uprobe_manager.cc:908] Number of uprobes deployed = 59
I20230606 21:40:28.139052 3775175 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:40:31.051141 3775204 go_syms.cc:66] Falling back to the runtime.buildVersion symbol for go version detection
W20230606 21:40:31.107789 3775204 uprobe_manager.cc:813] Failed to attach HTTP2 Uprobes to /proc/3775187/root/usr/bin/podman: Internal : Unable to find offset for binary /proc/3775187/root/usr/bin/podman symbol github.com/containers/podman/vendor/google.golang.org/grpc/internal/transport.(*http2Client).operateHeaders address 0
I20230606 21:40:31.123049 3775204 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:40:39.597115 3753491 container_runner.cc:53] podman rm -f https_client_1300478295745860 &>/dev/null
I20230606 21:40:39.629444 3753491 container_runner.cc:53] podman rm -f https_server_1300457407755886 &>/dev/null
[       OK ] GoTLSTraceTest/2.BasicHTTP2 (42686 ms)
[----------] 2 tests from GoTLSTraceTest/2 (107379 ms total)

[----------] 2 tests from GoTLSTraceTest/3, where TypeParam = px::stirling::Go1_20TLSClientServerContainers
[ RUN      ] GoTLSTraceTest/3.BasicHTTP
I20230606 21:40:41.119590 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_20_https_server
I20230606 21:40:41.228438 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_20_https_client
I20230606 21:40:41.228510 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --name=https_server_1300499973883862 localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_20_https_server
I20230606 21:40:41.439800 3753491 container_runner.cc:144] Container https_server_1300499973883862 status: running
I20230606 21:40:41.471391 3753491 container_runner.cc:175] Container https_server_1300499973883862 process PID: 3775529
I20230606 21:40:41.471422 3753491 container_runner.cc:177] Container https_server_1300499973883862 waiting for log message: Starting HTTPS service
I20230606 21:40:41.501849 3753491 container_runner.cc:189] Container https_server_1300499973883862 status: running
I20230606 21:40:41.501868 3753491 container_runner.cc:225] Container https_server_1300499973883862 is ready.
I20230606 21:40:41.502111 3753491 source_connector.cc:35] Initializing source connector: socket_trace_connector
I20230606 21:40:41.502161 3753491 linux_headers.cc:94] Obtained Linux version string from `uname`: 5.19.0-1022-gcp
I20230606 21:40:41.502168 3753491 linux_headers.cc:642] Detected kernel release (uname -r): 5.19.0-1022-gcp
I20230606 21:40:41.502194 3753491 bcc_wrapper.cc:121] Using linux headers found at /lib/modules/5.19.0-1022-gcp/build for BCC runtime.
I20230606 21:40:41.502241 3753491 bcc_wrapper.cc:170] Initializing BPF program ...
I20230606 21:40:50.012264 3753491 scoped_timer.h:48] Timer(init_bpf_program) : 8.51 s
I20230606 21:40:50.821755 3753491 socket_trace_connector.cc:427] Number of kprobes deployed = 40
I20230606 21:40:50.821812 3753491 socket_trace_connector.cc:428] Probes successfully deployed.
I20230606 21:40:50.821867 3753491 socket_trace_connector.cc:362] Initializing perf buffers with ncpus=96 and scaling_factor=0.0865385
I20230606 21:40:50.821903 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kData buffers across all cpus: 268038720
I20230606 21:40:50.821913 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kControl buffers across all cpus: 13353216
I20230606 21:40:50.924621 3753491 socket_trace_connector.cc:432] Number of perf buffers opened = 8
I20230606 21:40:51.243664 3775577 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:51.885387 3775577 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:52.246434 3775577 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:52.649816 3775577 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:53.041460 3775577 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:53.432793 3775577 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:40:53.862509 3775577 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
W20230606 21:40:58.547820 3775577 uprobe_manager.cc:760] Cannot analyze binary /proc/3775575/root/usr/bin/sleep for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3775575/root/usr/bin/sleep
I20230606 21:41:00.044050 3775577 uprobe_manager.cc:908] Number of uprobes deployed = 10814
I20230606 21:41:00.110008 3775677 uprobe_manager.cc:908] Number of uprobes deployed = 18
I20230606 21:41:00.145191 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --network=container:https_server_1300499973883862 --name=https_client_1300518890559556 localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_20_https_client --http2=false --iters=2 --sub_iters=5
I20230606 21:41:00.301157 3753491 container_runner.cc:144] Container https_client_1300518890559556 status: running
I20230606 21:41:00.334977 3753491 container_runner.cc:175] Container https_client_1300518890559556 process PID: 3775733
I20230606 21:41:00.335003 3753491 container_runner.cc:177] Container https_client_1300518890559556 waiting for log message: {"status":"ok"}
I20230606 21:41:00.366328 3753491 container_runner.cc:189] Container https_client_1300518890559556 status: running
I20230606 21:41:00.366358 3753491 container_runner.cc:225] Container https_client_1300518890559556 is ready.
I20230606 21:41:01.652113 3775743 uprobe_manager.cc:908] Number of uprobes deployed = 37
I20230606 21:41:01.939931 3775795 uprobe_manager.cc:908] Number of uprobes deployed = 59
I20230606 21:41:04.967063 3775855 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:41:08.314496 3775961 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:41:08.798010 3775986 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:41:10.414721 3776034 uprobe_manager.cc:908] Number of uprobes deployed = 45
I20230606 21:41:19.061192 3753491 container_runner.cc:53] podman rm -f https_client_1300518890559556 &>/dev/null
I20230606 21:41:19.093426 3753491 container_runner.cc:53] podman rm -f https_server_1300499973883862 &>/dev/null
[       OK ] GoTLSTraceTest/3.BasicHTTP (39945 ms)
[ RUN      ] GoTLSTraceTest/3.BasicHTTP2
I20230606 21:41:21.061506 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_20_https_server
I20230606 21:41:21.169705 3753491 container_runner.cc:36] Loaded image: localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_20_https_client
I20230606 21:41:21.169773 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --name=https_server_1300539915147734 localhost/bazel/src/stirling/testing/demo_apps/go_https/server:golang_1_20_https_server
I20230606 21:41:21.388166 3753491 container_runner.cc:144] Container https_server_1300539915147734 status: running
I20230606 21:41:21.419574 3753491 container_runner.cc:175] Container https_server_1300539915147734 process PID: 3776393
I20230606 21:41:21.419595 3753491 container_runner.cc:177] Container https_server_1300539915147734 waiting for log message: Starting HTTPS service
I20230606 21:41:21.450573 3753491 container_runner.cc:189] Container https_server_1300539915147734 status: running
I20230606 21:41:21.450593 3753491 container_runner.cc:225] Container https_server_1300539915147734 is ready.
I20230606 21:41:21.450845 3753491 source_connector.cc:35] Initializing source connector: socket_trace_connector
I20230606 21:41:21.450882 3753491 linux_headers.cc:94] Obtained Linux version string from `uname`: 5.19.0-1022-gcp
I20230606 21:41:21.450891 3753491 linux_headers.cc:642] Detected kernel release (uname -r): 5.19.0-1022-gcp
I20230606 21:41:21.450914 3753491 bcc_wrapper.cc:121] Using linux headers found at /lib/modules/5.19.0-1022-gcp/build for BCC runtime.
I20230606 21:41:21.450964 3753491 bcc_wrapper.cc:170] Initializing BPF program ...
I20230606 21:41:30.011158 3753491 scoped_timer.h:48] Timer(init_bpf_program) : 8.56 s
I20230606 21:41:30.823117 3753491 socket_trace_connector.cc:427] Number of kprobes deployed = 40
I20230606 21:41:30.823158 3753491 socket_trace_connector.cc:428] Probes successfully deployed.
I20230606 21:41:30.823212 3753491 socket_trace_connector.cc:362] Initializing perf buffers with ncpus=96 and scaling_factor=0.0865385
I20230606 21:41:30.823247 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kData buffers across all cpus: 268038720
I20230606 21:41:30.823256 3753491 socket_trace_connector.cc:351] Total perf buffer usage for kControl buffers across all cpus: 13353216
I20230606 21:41:30.925472 3753491 socket_trace_connector.cc:432] Number of perf buffers opened = 8
I20230606 21:41:31.350883 3776447 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:41:31.946213 3776447 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:41:32.327951 3776447 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:41:32.693809 3776447 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:41:33.075191 3776447 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:41:33.431862 3776447 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
I20230606 21:41:34.063288 3776447 uprobe_symaddrs.cc:849] Getting symbol offsets for version: major=16 minor=17 patch=1
W20230606 21:41:38.499164 3776447 uprobe_manager.cc:760] Cannot analyze binary /proc/3776445/root/usr/bin/sleep for uprobe deployment. If file is under /var/lib, container may have terminated. Message = Can't find or process ELF file /proc/3776445/root/usr/bin/sleep
I20230606 21:41:39.981185 3776447 uprobe_manager.cc:908] Number of uprobes deployed = 10967
I20230606 21:41:40.047283 3776461 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:41:40.082437 3753491 container_runner.cc:114] podman run --timeout=3600 --rm -q --pid=host --network=container:https_server_1300539915147734 --name=https_client_1300558827805296 localhost/bazel/src/stirling/testing/demo_apps/go_https/client:golang_1_20_https_client --http2=true --iters=2 --sub_iters=5
I20230606 21:41:40.274593 3753491 container_runner.cc:144] Container https_client_1300558827805296 status: running
I20230606 21:41:40.307360 3753491 container_runner.cc:175] Container https_client_1300558827805296 process PID: 3776511
I20230606 21:41:40.307387 3753491 container_runner.cc:177] Container https_client_1300558827805296 waiting for log message: {"status":"ok"}
I20230606 21:41:40.339344 3753491 container_runner.cc:189] Container https_client_1300558827805296 status: running
I20230606 21:41:40.339375 3753491 container_runner.cc:225] Container https_client_1300558827805296 is ready.
I20230606 21:41:41.617419 3776528 uprobe_manager.cc:908] Number of uprobes deployed = 55
I20230606 21:41:41.839206 3776574 uprobe_manager.cc:908] Number of uprobes deployed = 32
I20230606 21:41:48.457949 3776617 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:41:50.386976 3776654 uprobe_manager.cc:908] Number of uprobes deployed = 9
I20230606 21:41:58.745162 3753491 container_runner.cc:53] podman rm -f https_client_1300558827805296 &>/dev/null
I20230606 21:41:58.777207 3753491 container_runner.cc:53] podman rm -f https_server_1300539915147734 &>/dev/null
[       OK ] GoTLSTraceTest/3.BasicHTTP2 (39229 ms)
[----------] 2 tests from GoTLSTraceTest/3 (79174 ms total)

[----------] Global test environment tear-down
[==========] 8 tests from 4 test suites ran. (342838 ms total)
[  PASSED  ] 8 tests.
I20230606 21:42:00.192272 3753491 env.cc:51] Shutting down


[PRM-1154] - Changed page structure for index page

Looks like we are not writing test cases for these layouts, is it worth adding.

I feel that it wouldn't add any value and that we don't really test the layout


chore: add volunteer aksh-kr

Thanks @aksh-kr for volunteering with AskDevs. Added some comments on your change.

Thanks @aksh-kr. Welcome!

Thank you @codewithvoid!


[Bug]: Job Details -> Showing Proxy Group (x) instead of Proxy Group Name

Version of the software
0.1.21
Operating system
Microsoft Windows NT 6.2.9200.0 | Server 2012 DC
Browser
Chrome 91 / Opera 77.0.4054.203
What happened?
When viewing a job's details it no longer displays the proxy groups name, now it just displays the index number.
Relevant LoliCode if needed
No response

I don't think it ever displayed the group name 🤔 but ye sure I can make it so that it shows the name

My apologies I guess I wasnt paying attention before the update


Add "Report an Issue" link

Adds link for opening an issue.  I'd like it to open a specific issue template, but it doesn't work.  Opened a discussion here: https://github.com/quarto-dev/quarto-cli/discussions/7203

Waiting for this bugfix: https://github.com/quarto-dev/quarto-cli/issues/7206

It looks like that issue has not yet been addressed.

Going to go ahead and merge this.  It'll at least link to an empty issue for now and will be fixed when we render it after 1.4 is out


LINT ERROR IN EDIT PRODUCTS BLADE

Bug Report

Issue Description
I am getting a linting error. I need the correct expression. Please see the screenshot attached.

Bagisto Version

[ ] master branch
[ ] 1.3.3
[ * ] 1.3.2
[ ] 1.3.1
[ ] 1.3.0

Steps To Reproduce
Go to packages/Webkul/Velocity/src/Resources/views/admin/content/content-type/edit-product.blade.php
Actual Result
There is a linting error.
Expected Result
Linting Error should be removed.

Hi @soodankush
Thanks for reporting we will fix it

Please can you fix it as soon as possible?

Hi @soodankush
We will fix it as soon as possible. and will reflect in the next release.

Hi @soodankush
Now, this issue is fixed. Please verify from your end.
If still, you are getting the same issue. Then please let me know.

Hi @Sanjaybhattwebkul ,
Thank you. The issue has been fixed.


There is no support for turborepo deployment

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d123vt5pu3noof
AWS Region
us-east-1
Amplify Hosting feature
Monorepo
Describe the bug
I need to deploy 2 apps inside my root folder which uses turbo.json the deployment works fine on Vercel but not on Amplify
Expected behavior
I root folder has apps folder inside it has 2 nextjs apps out of which one of them is root app and other nextjs app needs to run on root/app
Reproduction steps
My root app looks like this in package.json
{
  "name": "root-app",
  "version": "0.0.0",
  "private": true,
  "workspaces": [
    "apps/*",
    "packages/*"
  ],
  "scripts": {
    "build": "turbo run build",
    "dev": "turbo run dev --parallel",
    "lint": "turbo run lint",
    "format": "prettier --write \"**/*.{ts,tsx,md}\"",
    "prepare": "husky install"
  },
  "devDependencies": {
    "husky": "^8.0.3",
    "prettier": "^2.8.2",
    "pretty-quick": "^3.1.3",
    "turbo": "^1.8.1"
  },
  "engines": {
    "npm": ">=7.0.0",
    "node": ">=14.0.0"
  },
  "dependencies": {
    "react-hotjar": "^5.5.0"
  }
}

Build Settings
version: 1
applications:
  - appRoot: apps/beem-web-main
    commands:
      preBuild:
        - yarn install
      build:
        - yarn build
      postBuild:
        - next-sitemap
    artifacts:
      baseDirectory: .next
      files:
        - '**/*'
      discard-paths: no
  - appRoot: apps/beem-web-app
    commands:
      preBuild:
        - yarn run start
      build:
        - yarn run build
    artifacts:
      baseDirectory: .next
      files:
        - '**/*'
      discard-paths: no

Log output

2023-05-21T22:38:54.215Z [INFO]: # Cloning repository: git@github.com:linefinancial/root-app.git
2023-05-21T22:38:56.127Z [INFO]:
2023-05-21T22:38:56.129Z [INFO]: Cloning into 'root-app'...
2023-05-21T22:38:56.130Z [INFO]: # Switching to commit: 8b2d38da2a14f9644a7a7353eaa8f9afdcd4d213
2023-05-21T22:38:56.148Z [INFO]: Note: switching to '8b2d38da2a14f9644a7a7353eaa8f9afdcd4d213'.
                                 You are in 'detached HEAD' state. You can look around, make experimental
                                 changes and commit them, and you can discard any commits you make in this
                                 state without impacting any branches by switching back to a branch.
                                 If you want to create a new branch to retain commits you create, you may
                                 do so (now or later) by using -c with the switch command. Example:
                                 git switch -c <new-branch-name>
                                 Or undo this operation with:
                                 git switch -
                                 Turn off this advice by setting config variable advice.detachedHead to false
                                 HEAD is now at 8b2d38d rm -rf nvmrc
2023-05-21T22:38:56.186Z [INFO]: Successfully cleaned up Git credentials
2023-05-21T22:38:56.186Z [INFO]: # Checking for Git submodules at: /codebuild/output/src216366039/src/root-app/.gitmodules
2023-05-21T22:38:56.191Z [ERROR]: !!! CustomerError: Missing frontend definition in buildspec
2023-05-21T22:38:56.192Z [INFO]: # Starting environment caching...
2023-05-21T22:38:56.678Z [INFO]: # Environment caching completed
Terminating logging...

Additional information
No info

This time my build went fine but opening the URL : its showing 404
https://main.d3o0ed97yo5r4n.amplifyapp.com/
version: 1
applications:
  - appRoot: apps/beem-web-app
    commands:
      - command: yarn run build
    frontend:
      phases:
        preBuild:
          commands:
            - yarn install
        build:
          commands:
            - yarn run build
        postBuild:
          commands:
            - npx turbo run lint
      artifacts:
        baseDirectory: .next
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*
  - appRoot: apps/beem-web-main
    commands:
      - command: yarn run build
    frontend:
      phases:
        preBuild:
          commands:
            - yarn run install
        build:
          commands:
            - yarn run build
        postBuild:
          commands:
            - npx turbo run lint
      artifacts:
        baseDirectory: .next
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*

@vashisth00 You would need to specify the AMPLIFY_MONOREPO_APP_ROOT environment variable for your app that indicates which app you want Amplify to build and host
You can learn more here: https://docs.aws.amazon.com/amplify/latest/userguide/monorepo-configuration.html
Thanks

Closing this issue as it appears you have properly configured your build settings as well as the AMPLIFY_MONOREPO_APP_ROOT variable and your site is deployed.


Fixed few typos

Here's another PR with a couple of typos fixed. As you can see there was a typo in fileReferenceIndentifiers, in class ParsedProjectInfo. Maybe we should do some check on that since I'm not sure if that property is used somewhere outside Flutter?
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

LGTM after the two comments are resolved.

All done!


[GSSOC23]Adding onboarding for new users

Is your feature request related to a problem? Please describe.
The app doesn't have a proper onboarding set up. If done, it would make the users get familiar with the application fairly easily and would make them understand how to use the application properly.
Describe the solution you'd like
I'd design and implement the intro screens along with proper onboarding, so that when the app would be installed and opened for the first time, the users would be greeted by an automated experience which would acquaint users with app's features and how to use it.
Sample intro and onboarding screens for the purpose of understanding and clarity

i can contribute  to this project, as i was recently working on UI/ UX fronted design using Flutter, Assign me this issue so i can contribute under the label of GSSOC

I want to contribute under the label Of GSSOC

Hey, please assign me this issue

Go Ahead @jaivsh

Hi @avinashkranjan
I've completed the PR work and have created a pull request regarding the same. Can you please check the work?
Thanking you in anticipation!


Support RTL languages in admin interface

Is your proposal related to a problem?
Wagtail supports internationalization, But wagtail admin interface doesn't support right to left (RTL) layout for languages written from right to left. There are some important languages (Persian, Arabic, Hebrew, ...) that are written from right to left.
Describe the solution you'd like
I want wagtail admin templates to provide an RTL layout (for example the sidebar should be on the right of the page) when the language is right to left.

Hi @HsnVahedi - thanks for the report. There's an existing open issue for this here: #1240


Use test.yml for the badge as we have no CI workflow

All looking green with this PR!
...multiple shades of it, or is it just me that the "test" and "license scan" badges have a different shade of green?


Improve reading configs from env

Add support of https://pypi.org/project/python-dotenv/ and also add development and test sample .env

Hello Friends
i worked on this little issue
i can send the changes if you want

Sure, why not?

Closed by #60


With a standard dbContext (Scoped), my context is being shared across requests.

Steps to reproduce
Add a scoped lifetime datacontext
In my controller it is injected in this way

  private ApplicationDbContext _context;
        private UserManager<ApplicationUser> _userManager;
        public PatchSetsController(ApplicationDbContext context, UserManager<ApplicationUser> mgr)
        {
            _context = context;
            _userManager = mgr;
        }

In a dotnetcore 1.0, EF7 application, add dbcontext in Startup.cs like so:
  services.AddEntityFramework().AddDbContext<ApplicationDbContext>(options =>
                options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")));

(or, explicitly set to scoped lifetime)
Create a synchronous endpoint that executes a longer (~1s) query, and returns the result.
My controller has a method to run a long-running query and respond with the results as JSON. This calls .ToList() at the end of a LINQ query.
Specifically, my actual query is this:
List<PatchSet> patches  = _context.PatchSets.Include(c => c.Baseline).Include(c => c.Patches).ThenInclude(p => p.Patch).Where(c => c.Baseline.Id == currentPatchSet.Baseline.Id && c.Status == PatchSetStatus.Released).ToList();

Call this method, twice (via AJAX/xhr), with different parameters from the same page at nearly the same time.
Client logs show these requests occur within 1ms of eachother. Debugging shows that the operations occur concurrently.
The issue
The context appears to be shared between requests and causes some internal implementation errors (NPE, index out of range, etc) because both queries are running simultaneously.
If I use a mutex and lock around the query statement, the issue disappears entirely. The concurrent requests should be separate datacontexts, no?
  lock (locker)
            {
      patches  = _context.PatchSets.Include(c => c.Baseline).Include(c => c.Patches).ThenInclude(p => p.Patch).Where(c => c.Baseline.Id == currentPatchSet.Baseline.Id && c.Status == PatchSetStatus.Released).ToList();

            }

The above code throws no exceptions at any time.
Further technical details
EF Core version: 1.0.0
Operating system:  Windows 10
Visual Studio version: VS 2015
Other details about my project setup:

The errors I am getting are a Null Pointer Error, and an Index Out of Range error, these appear randomly but fairly consistently.
Using a lock statement prevents these 100% of the time.  These requests are on separate threads and separate XHR requests

This appears to be fixed in 1.0.1, so this issue may be moot. I will report after further testing

This looks like https://github.com/aspnet/EntityFramework/issues/5456 which was fixed in 1.0.1


Support HTTP requests that are sent in arbitrary number of chunks

The current implementation of the SocketServer only supports HTTP requests that are sent in 1 or 2 chunks, with the additional requirement of the "Content-Length" header being fully contained in the first chunk for POST and PUT requests. HTTP requests however can be sent in an arbitrary number of chunks and a server must only process the request, after all headers and the full body was received.
On a fast localhost connection an additional problem occurs:
The current implementation checks if the body was contained in the first chunk, if not, it just calls read() on the socket. But in many cases, the body data is not available on the socket yet, which will result in a socket read error 35 (EAGAIN) and the body data is silently dropped.
I issues a pull request that should fix the above issues. There are still some memory leaks when handling massive amounts of requests, those should be addressed separately.

I just updated the pull request and resolved merge conflicts.


Difference between chgcar.density and cubegen.density

Hey there, I am currently wondering why the cubegen density function calls numint.eval_rho and the chgcar is directly computing the einsum via lib.einsum
What is the benefit of calling eval_rho?
Thanks in advance for any explanation.

eval_rho is a little faster than naive einsum. And numint.eval_rho2 would be faster.

ah so nothing more than speed.
Wouldn't it be better to call eval_rho in chgcar.density as well?


New version(?): DuckStudio.ChineseGit.Csharp version 2.9.1

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

This pull request should require manual review:

https://github.com/microsoft/winget-pkgs/pull/164102#issuecomment-2248189203

/azp run

/azp run

/azp run


Disconnect because of UNKNOWN EXCEPTION /ERROR

I'm trying to connect with the Server from Android 14, but the client is not connecting and showing this Disconnect because of UNKNOWN EXCEPTION /ERROR in the Notification.

it`s my log file :
log_mvc_20221122094642.txt


examples from purescript-agronaut should be migrated here

The example from purescript-agronaut should be migrated to this repo (or purescript-agronaut-codecs?).
This will help future users when they are trying to figure out how to use argonaut.  Don't want users to have to go looking in a deprecated library for examples.

:+1:

I'm updating the argonaut-codecs documentation, which includes updating examples, so I'm going to close this issue. That example is better suited for the -codecs repository and will be included there.


Add more description in README

Add more descriptions about the project
Add information about how to learn GitHub
Add more information about how to use this project.

Hey @Amit-TheOne 👋🏻
I want to work on this issue. Please assign it to me

Hey @pixan198
Assigning it to you.
What do you think will be the ETA?

Hey @Amit-TheOne
I can update in few mins


[release-1.13] Test with go 1.18

Please provide a description of this PR:
Test with Go 1.18

@ericvn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test lint

release-notes_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test lint

release-notes_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test release-notes

integ-security_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test lint

release-notes_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test release-notes

integ-security_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Same test, file_mounted_certs: TestClientToServiceTls, failed in too integ-security_istio runs.

/test integ-security

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test lint

release-notes_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test release-notes

integ-security_istio_release-1.13
b3acebbab7cbfdb2c19c9f8c1f1558869c5b1711
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

A simple update to Go 1.18 causes one test failure. Closing this PR for now. We can resurrect if it's decided to move to 1.18 to tests fixes.


Extract multiaddr_to_peer_info.ts in common package

This is a bug report/feature or change request/support request
Problem
multiaddr_to_peer_info.ts is duplicated in the codebase as it is used by the two peer discovery protocols.
Proposed Solutions

Define a package that implements this feature
Use it to remove dupe code
Add some tests

Do teh same for random_subset.ts


Campgrounds and potential new POI color

Campgrounds have a long tradition of being prominently displayed on American road maps, so they are very appropriate for this project. I think the icon to use is fairly obviously some sort of tent. I personally quite like the NPS icon:

Campgrounds (OMT class=campsite + subclass=camp_site) appear in the tiles beginning at z14, so that puts a practical limit on how early we can render them, despite American road maps sometimes displaying camping POIs even at state-wide scales.
What I'm most interested to discuss is what color to make the icon. The contributing guidelines have long left a spot open for an "outdoors" POI color, presumably a shade of green. This category could be appropriate for campsites, as well as other POIs like sports fields, picnic sites, and maybe even natural features like peaks (though that might be worth a separate discussion). If we go with green, care will be needed to choose a shade that contrasts appropriately with the park background fill many campgrounds will be on top of. Relatedly, would it be acceptable for the POI label text to be a similar shade of green as the park labels, or do they need to contrast? We'll also want to consider accessibility for color-blind users (see #1038), whether that means choosing a shade that transforms to a sufficiently different color under color-blindness or implementing some kind of color switcher.
Alternatively, campsites could plausibly be grouped with hotels in consumer-orange, or as attraction-brown.
Distinguishing campgrounds from individual campsites could be a candidate for a treatment similar to how we distinguish bus stops vs. stations: by inscribing the campground in a circle. But this is getting ahead of things, since tourism=camp_pitch is not present in the OMT tiles as far as I can tell.

I like the idea of distinguishing camp_pitch via lack of circle.


GH-38857: [Python] Add append mode for pyarrow.OsFile

Rationale for this change
Seems reasonable. :)
What changes are included in this PR?
Exposes the C++ append parameter from FileOutputStream  to PyArrow's OSFile.
Are these changes tested?
Yes.
Are there any user-facing changes?
Can add a or ab to mode parameter in pyarrow.OsFile

Closes: #38857

Ah, how embarrassing. Issue created and and title updated as requested!

Thanks for the review @AlenkaF.
In adding the doc example and looking at test_native_file_modes, I see that NativeFile.mode plays only with 'is_readable' and 'is_writable'.
Should I go about adding a is_appendable to facilitate returning a 'ab'?

Ah, thank you for looking into it.
I am not sure how to handle 'ab' mode in connection to the NativeFile class. I do not see an issue if OSFile subclass handles extra append mode and NativeFile does not. @jorisvandenbossche what do you think?

Should I go about adding a is_appendable to facilitate returning an 'ab'?

You could add a private _is_appending attribute that would default to False.

Failure seems unrelated.

I have rerun it just in case.
LGTM otherwise, thank you!

I also think is unrelated. I've opened https://github.com/apache/arrow/issues/39003 to track it.

Thanks! 👋


Slides are offset when transition to full screen and back

View a slide in normal window.  Then restore. Slide is shifted.

Good catch ... I know about this issue but decided to leave it for a later fix. Even if it happens while I'm presenting I'll simply hit refresh and will solve the problem. The fix that I can do will probably cost more in filesize and performance.

Your call. F5 works for me.


Feature Request: Add inlineChat API to @vscode/dts for Prototyping

Feature Request: Add inlineChat API to @vscode/dts for Prototyping
Currently, the inlineChat feature is available in the workbench, and it's a highly useful tool for enhancing interactive user experiences. However, there is currently no available API in @vscode/dts for developers to prototype with this functionality.
Request
We would like to request the inclusion of the inlineChat API in the vscode.proposed.d.ts file. This would allow developers to prototype and experiment with inlineChat functionality using npx @vscode/dts main. Ideally, the type definitions would be included in something like vscode.proposed.inlineChat.d.ts.
Rationale
By providing early access to the inlineChat API for prototyping, the VS Code extension developer community could:

Prototype with cutting-edge features in real-time.
Provide valuable feedback on the API before its official release.
Develop innovative extensions that leverage in-editor interactivity.

Thanks for considering this request, and we look forward to the opportunity to experiment with this exciting feature!
### Tasks

A very rough proposal exists, but it is buried here: https://github.com/microsoft/vscode/blob/06fc5cd29f1fc6074f8cb033a6578741d2c398f1/src/vscode-dts/vscode.proposed.chatParticipantPrivate.d.ts#L32-L39
You also need to add (and ignore warnings) to package.json#chatParticipants the following
// .. participant stuff
"locations": [
	"editor"
],

Feature Request: Add inlineChat API to @vscode/dts for Prototyping
功能请求：将 inlineChat API 添加到 @vscode/dts 以进行原型设计
Currently, the inlineChat feature is available in the workbench, and it's a highly useful tool for enhancing interactive user experiences. However, there is currently no available API in @vscode/dts for developers to prototype with this functionality.目前，Workbench 中提供了 inlineChat 功能，它是增强交互式用户体验的非常有用的工具。但是，@vscode/dts 中目前没有可用的 API 供开发人员使用此功能进行原型设计。
Request 请求
We would like to request the inclusion of the inlineChat API in the vscode.proposed.d.ts file. This would allow developers to prototype and experiment with inlineChat functionality using npx @vscode/dts main. Ideally, the type definitions would be included in something like vscode.proposed.inlineChat.d.ts.我们想请求在 vscode.proposed.d.ts 文件中包含 inlineChat API。这将允许开发人员使用 npx @vscode/dts main 对 inlineChat 功能进行原型设计和试验。理想情况下，类型定义将包含在类似 vscode.proposed.inlineChat.d.ts .
Rationale 理由
By providing early access to the inlineChat API for prototyping, the VS Code extension developer community could:通过提供对 inlineChat API 的早期访问以进行原型设计，VS Code 扩展开发人员社区可以：

Prototype with cutting-edge features in real-time.实时使用尖端功能进行原型设计。
Provide valuable feedback on the API before its official release.在 API 正式发布之前提供有关 API 的宝贵反馈。
Develop innovative extensions that leverage in-editor interactivity.开发利用编辑器内交互性的创新扩展。

Thanks for considering this request, and we look forward to the opportunity to experiment with this exciting feature!感谢您考虑此请求，我们期待着有机会尝试这一令人兴奋的功能！
Tasks 任务
Beta 试用版
Give feedback 提供反馈
No tasks being tracked yet.
尚未跟踪任何任务。

[ ]
Options
    * Convert to issue
    * Toggle completion
    * Rename
    * Remove

how to use inline-chat in my vscode-ext?

Can I call the inline-chat api directly from a custom vscode ext? @jrieken

@qiyx2019
Can I call the inline-chat api directly from a custom vscode ext? @jrieken

As i see it, it shouldn't be much different that calling QuickPick or InputBox. Its implementation should be straightforward

I don't know what I should do. It seems that this api is not exposed in the official version. Can you show a demo? Thank you

I don't know what I should do. It seems that this api is not exposed in the official version. Can you show a demo? Thank you @32teeth

I think @jrieken illustrated some usage
But you're right. Maybe a more solid demo or usage example
Seems it's currently exclusive to @github copilot extension
You could theoretically download the VSIX file, change the extension to .zip and do some reverse engineering

/duplicate of https://github.com/microsoft/vscode/issues/228177


Need higher resolution GIF for Codepen

Refers a change done via https://github.com/freeCodeCamp/freeCodeCamp/pull/13895
We need a higher resolution GIF for this http://i.imgur.com/oLYs8EA.gif
It has to be hosted on imgur as the original, and should have the same steps as done in the original.
We would then need a pull request replacing the image.

I won't be taking this since this is a 'first timers only' issue 😃
Whoever is willing to take this issue can use Recordit to record the gif. The resolution of the generated gif is pretty good and the app is simple to use.
Cheers!

Can I give it a shot?
I'm actually a 2nd timer, but pretty much still a newbie.

As the original low ref .gif owner I can add that it was recorded on:

MacBook pro with NVIDIA GeForce GT 650M
QuickTime as the screen recorder
Processed with imgur built in .gif maker

I strongly suspect that the last one is what caused the end result to be that low quality.

Also @raisedadead forgive me for the late reply on the original thread: busy busy days :)

@Marmiz Sure, thing. Thanks a lot for all the contributions you do.
@dakshshah96 thanks a lot for sharing the resource.
@fortMaximus sure thing if you are interested, you can record and share the link here in this thread for a review. Then once confirmed that the res is good enough, please make a pull request.

Hi I never contributed to an open source project before. I was wondering if I could work on that

Hi everyone, i have done a video. It is here http://recordit.co/bLSBCcJl7z by using recordit as told by@dakshshah96 ,i am a first-timer so can anybody tell me what to do next.

@usunil0
Click the button

Generate the GIF and upload it to imgur.
Then share the link here

@raisedadead In what file do we place the link to the new gif before submitting the pull request!?

@raisedadead Created a branch called gif, and added a file called NEWGIF.md to the branch. Submitted the pull request with a link to the image.
http://imgur.com/vidgif?url=http%3A%2F%2Frecordit.co%2FYK0paRsf6W

@pporche87 thanks but, your link doesn't fulfil the requirement. I have updated the opening post of the issue for clarification.
@fortMaximus @usunil0 and @pporche87 @lkeude96  if anyone of you can submit an pull request after following the GIF in the opening post, it would be awesome.
P.S: The recordit video doesn't get converted to GIF on my side, so you may have to use an alternative.

@raisedadead Thanks for the clarity. I'm on it.

@raisedadead is this one good?

@fortMaximus yes this is perfect, please make a pull request.

@fortMaximus and everyone else, we have a PR open for this issue. We thank everyone for their interest in fixing this issue.
Please do not be disheartened. We request you to look through any of the open issues that are tagged "help wanted".
Reach out to us in the chat rooms for any assistance, we would be happy to help.

@raisedadead Thanks for the support.