aklivity / zilla-examples Goto Github PK

http.filesystem % curl --cacert test-ca.crt https://localhost:9090/index.html
curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

+ ZILLA_CHART=oci://ghcr.io/aklivity/charts/zilla
+ helm install zilla-amqp-reflect oci://ghcr.io/aklivity/charts/zilla --namespace zilla-amqp-reflect --create-namespace --wait --values values.yaml --set-file 'zilla\.yaml=zilla.yaml' --set-file 'secrets.tls.data.localhost\.p12=tls/localhost.p12'

Error: INSTALLATION FAILED: timed out waiting for the condition

$ docker build -t zilla-examples/sse-server:latest .
$ docker stack deploy -c stack.yml example --resolve-image never
$ export JWT_TOKEN=$(jwt encode \
    --alg "RS256" \
    --kid "example" \
    --iss "https://auth.example.com" \
    --aud "https://api.example.com" \
    --sub "example" \
    --exp 30s \
    --no-iat \
    --payload "scope=proxy:stream" \
    --secret @private.pem)

# in shell 1:
$ curl -v --cacert test-ca.crt "https://localhost:9090/events?access_token=${JWT_TOKEN}"
# in shell 2:
$ echo '{ "data": "Hello, world '`date`'" }' | nc -c localhost 7001
# in shell 1 observe:
* Connection #0 to host localhost left intact # curl exits

# in shell 1:
$ curl -v --cacert test-ca.crt "https://localhost:9090/events?access_token=${JWT_TOKEN}"
# in shell 2:
$ echo '{ "data": "Hello, world '`date`'" }' | nc -c localhost 7001
# in shell 1 observe:
* Connection #0 to host localhost left intact # curl exits

# in shell 1:
$ curl -v --cacert test-ca.crt "https://localhost:9090/events?access_token=${JWT_TOKEN}"
# wait for the rest of the 20s...
event:challenge
data:{"method":"POST","headers":{"content-type":"application/x-challenge-response"}}

# things are starting to work OK from this point on until the token expires...
# in shell 2:
$ echo '{ "data": "Hello, world '`date`'" }' | nc -c localhost 7001
# in shell 1 observe:
data:Hello, world Wed Jan 25 10:39:42 CET 2023
# in shell 2:
$ echo '{ "data": "Hello, world '`date`'" }' | nc -c localhost 7001
# in shell 1 observe:
data:Hello, world Wed Jan 25 10:39:42 CET 2023

# wait for the rest of the 10s for the token to expire
* Connection #0 to host localhost left intact # curl exits

FROM  maven:3.9.0-eclipse-temurin-17-alpine

RUN apk upgrade --no-cache && \
    apk add --no-cache libgcc libstdc++ ncurses-libs && \
    apk add --no-cache libgcc nodejs git

RUN wget -q -O /etc/apk/keys/sgerrand.rsa.pub https://alpine-pkgs.sgerrand.com/sgerrand.rsa.pub && \
    wget https://github.com/sgerrand/alpine-pkg-glibc/releases/download/2.35-r0/glibc-2.35-r0.apk

RUN apk add --force-overwrite glibc-2.35-r0.apk

WORKDIR /usr/app

RUN git clone https://github.com/akrambek/grpc-echo.git
RUN cd grpc-echo && mvn install

ENTRYPOINT ["java", "-jar", "grpc-echo/target/echo-develop-SNAPSHOT.jar"]

#10 33.54 [INFO] Compiling 1 proto file(s) to /usr/app/grpc-echo/target/generated-sources/protobuf/java
#10 33.66 [ERROR] PROTOC FAILED: qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
#10 33.66
#10 33.66 [ERROR] /usr/app/grpc-echo/src/main/resources/proto/echo.proto [0:0]: qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
`maven:3.9.0-eclipse-temurin-17-alpine

./setup.sh 
+ helm install zilla-grpc-kafka-proxy-kafka chart --namespace zilla-grpc-kafka-proxy --create-namespace --wait --timeout 2m
Error: INSTALLATION FAILED: timed out waiting for the condition

kcat -b localhost:9092 -L
%3|1698090965.456|FAIL|rdkafka#producer-1| [thrd:localhost:9092/bootstrap]: localhost:9092/bootstrap: Connect to ipv6#[::1]:9092 failed: Connection refused (after 1ms in state CONNECT)
%3|1698090966.459|FAIL|rdkafka#producer-1| [thrd:localhost:9092/bootstrap]: localhost:9092/bootstrap: Connect to ipv6#[::1]:9092 failed: Connection refused (after 0ms in state CONNECT, 1 identical error(s) suppressed)
%3|1698090967.464|FAIL|rdkafka#producer-1| [thrd:localhost:9092/bootstrap]: localhost:9092/bootstrap: Connect to ipv4#127.0.0.1:9092 failed: Connection refused (after 0ms in state CONNECT)
%3|1698090968.464|FAIL|rdkafka#producer-1| [thrd:localhost:9092/bootstrap]: localhost:9092/bootstrap: Connect to ipv6#[::1]:9092 failed: Connection refused (after 0ms in state CONNECT)
%3|1698090969.468|FAIL|rdkafka#producer-1| [thrd:localhost:9092/bootstrap]: localhost:9092/bootstrap: Connect to ipv4#127.0.0.1:9092 failed: Connection refused (after 0ms in state CONNECT)
% ERROR: Failed to acquire metadata: Local: Broker transport failure (Are the brokers reachable? Also try increasing the metadata timeout with -m <timeout>?)

echo 'message: "test"' | protoc --encode=example.FanoutMessage proto/fanout.proto > binary.data

kcat -P -b localhost:9092 -t messages -k -e ./binary.data                      

 grpcurl -insecure -proto proto/fanout.proto -d '' localhost:9090 example.FanoutService.FanoutServerStreamproto/fanout.proto -d '' localhost:9090 example.FanoutService.FanoutServerStream
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x28 pc=0x104f5d4e8]

goroutine 1 [running]:
github.com/jhump/protoreflect/desc/protoparse.parseToProtoRecursive({0x1053f2c80, 0x1400000f308}, {0x1400005d920, 0x1b}, 0x140001e7608?, 0x104ef4bf4?, 0x0?)
        github.com/jhump/[email protected]/desc/protoparse/parser.go:389 +0x148
github.com/jhump/protoreflect/desc/protoparse.parseToProtoRecursive.func1(0x140002eb380, 0x140000bfa90, 0x140000bf860, {0x1053f2c80, 0x1400000f308}, 0x1053a6560?, 0x140000b3f01?)
        github.com/jhump/[email protected]/desc/protoparse/parser.go:401 +0x164
github.com/jhump/protoreflect/desc/protoparse.parseToProtoRecursive({0x1053f2c80, 0x1400000f308}, {0x16b77f749, 0x12}, 0x140002e9480?, 0x0?, 0x140001e77b8?)
        github.com/jhump/[email protected]/desc/protoparse/parser.go:402 +0x1d8
github.com/jhump/protoreflect/desc/protoparse.parseToProtosRecursive({0x1053f2c80, 0x1400000f308}, {0x14000288da0, 0x1, 0x0?}, 0x0?, 0x0?)
        github.com/jhump/[email protected]/desc/protoparse/parser.go:365 +0x80
github.com/jhump/protoreflect/desc/protoparse.Parser.ParseFiles({{0x0, 0x0, 0x0}, 0x1, 0x0, 0x0, 0x0, 0x1, 0x0, 0x0, ...}, ...)
        github.com/jhump/[email protected]/desc/protoparse/parser.go:153 +0x210
github.com/fullstorydev/grpcurl.DescriptorSourceFromProtoFiles({0x0, 0x0, 0x0}, {0x14000288da0?, 0x140001e7b18?, 0x10468f018?})
        github.com/fullstorydev/grpcurl/desc_source.go:71 +0xbc
main.main()
        github.com/fullstorydev/grpcurl/cmd/grpcurl/grpcurl.go:501 +0xca8
adanelz@Andrews-MBP-2 grpc.kafka.fanout % 

 http.echo.jwt % jwt encode \
    --alg "RS256" \
    --kid "example" \
    --iss "https://auth.example.com" \
    --aud "https://api.example.com" \
    --exp 1968862747 \
    --no-iat \
    --secret @private.pem
thread 'main' panicked at 'Invalid JSON provided!', src/translators/encode.rs:122:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

2023-10-26 12:58:17 internal/process/esm_loader.js:74
2023-10-26 12:58:17     internalBinding('errors').triggerUncaughtException(
2023-10-26 12:58:17                               ^
2023-10-26 12:58:17 
2023-10-26 12:58:17 TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
2023-10-26 12:58:17     at Object.openSync (fs.js:454:10)
2023-10-26 12:58:17     at Object.readFileSync (fs.js:364:35)
2023-10-26 12:58:17     at SSEServer.createServer (file:///usr/app/node_modules/sse-server/index.js:36:15)
2023-10-26 12:58:17     at file:///usr/app/node_modules/sse-server/bin/cli.js:32:28
2023-10-26 12:58:17     at ModuleJob.run (internal/modules/esm/module_job.js:145:37)
2023-10-26 12:58:17     at async Loader.import (internal/modules/esm/loader.js:182:24)
2023-10-26 12:58:17     at async Object.loadESM (internal/process/esm_loader.js:68:5) {
2023-10-26 12:58:17   code: 'ERR_INVALID_ARG_TYPE'
2023-10-26 12:58:17 }

$ docker stack deploy -c stack.yml example --resolve-image never
$ nghttp -ansy https://localhost:9090/demo.html # run this multiple times

***** Statistics *****

Request timing:
  responseEnd: the  time  when  last  byte of  response  was  received
               relative to connectEnd
 requestStart: the time  just before  first byte  of request  was sent
               relative  to connectEnd.   If  '*' is  shown, this  was
               pushed by server.
      process: responseEnd - requestStart
         code: HTTP status code
         size: number  of  bytes  received as  response  body  without
               inflation.
          URI: request URI

see http://www.w3.org/TR/resource-timing/#processing-model

sorted by 'complete'

id  responseEnd requestStart  process code size request path
 13    +46.71ms        +32us  46.68ms  200  320 /demo.html
  2    +47.66ms *   +38.54ms   9.12ms  200   89 /style.css

Some requests were not processed. total=2, processed=1
***** Statistics *****

Request timing:
  responseEnd: the  time  when  last  byte of  response  was  received
               relative to connectEnd
 requestStart: the time  just before  first byte  of request  was sent
               relative  to connectEnd.   If  '*' is  shown, this  was
               pushed by server.
      process: responseEnd - requestStart
         code: HTTP status code
         size: number  of  bytes  received as  response  body  without
               inflation.
          URI: request URI

see http://www.w3.org/TR/resource-timing/#processing-model

sorted by 'complete'

id  responseEnd requestStart  process code size request path
 13    +14.99ms        +29us  14.96ms  200  320 /demo.html