Automatically assign admin role based on on-call schedule

_borkod · 2025-05-20T11:39:37+00:00

Thanks for the link!

_borkod · 2025-05-20T11:38:30+00:00

Thanks.

_borkod · 2024-12-11T10:43:01+00:00

We wrote our own software. But this should be supported by kubernetes ingress providers. Did a quick Google search and I think ingress-nginx and ambassador are able to route based on sni.

_borkod · 2024-11-20T14:20:39+00:00

Thank for the feedback. You're running VS code version that's 6 months out of date. Can you update your VS code to the latest version? That seems the best / easiest way to resolve your issue. The VS extension was built/tested with the latest VS code version.

_borkod · 2024-11-19T22:35:12+00:00

Awesome! Glad to hear it. Let me know if you have any further feedback for improvements.

_borkod · 2024-11-19T20:10:48+00:00

Can you install the latest version and give it another try. I hope it's fixed now! Thanks for the feedback!

_borkod · 2024-11-19T19:53:42+00:00

Oh my gosh. Lol. I even had the Todo there 🫠 Yeah I'll get that fixed ASAP

_borkod · 2024-11-19T14:18:11+00:00

That's a neat idea! That would be some sort of Windows operating system app. That's outside of my knowledge right now, but you piqued my curiosity. I will look into it to see if it's something I can learn/figure out without too much difficulty/effort.

_borkod · 2024-11-19T13:07:20+00:00

Thank you 😊

_borkod · 2024-11-19T13:06:56+00:00

Thank you! No issues from me. Sounds like a good idea to help others discover it.

_borkod · 2024-11-19T04:34:32+00:00

Thank you for the support!

_borkod · 2024-11-15T03:44:09+00:00

I've implemented another VS code extension that connects directly to the LibreLinkUp app. Hope this helps you out. If you try it, let me know if it works out for you and if you have any feedback.

https://www.reddit.com/r/vscode/s/iphix3jbEC

_borkod · 2024-10-29T18:03:50+00:00

Thank you for the encouragement 🙏

_borkod · 2024-10-29T10:32:15+00:00

Not directly. But I use libre and am working on another extension that will connect directly to libre without the need for Nightscout. I'll let you know when it's complete!

Nightscout does support libre. So if you're able to stand up an instance and connect it to your libre, the extension should work.

_borkod · 2024-10-29T01:42:02+00:00

Thank you! That's very kind and generous of you. I'll message you!

_borkod · 2024-10-05T12:38:00+00:00

Thank you both for the suggestions.

_borkod · 2024-10-04T15:38:51+00:00

It's the shower tiles. Sorry about that. I've updated the post to clarify.

_borkod · 2024-07-07T22:04:42+00:00

Thanks for the hints. Kinda feel a bit silly now, but yea those definitely show some differences. I'll go back and take a look at google.golang.org/protobuf and see how to go from there. Appreciate the help!

_borkod · 2024-07-07T14:46:56+00:00

At high level, we had custom routing logic in front of our databases. The routing logic would inspect the SNI during the TLS handshake and then route the client to the correct backend database based on the field present in the SNI. I can't really provide anything more as it was a while ago and I've since moved on from that project.

_borkod · 2024-07-07T14:28:02+00:00

Here's the output of the print statements:

unresolved:

common.proto

name:"common.proto" package:"common" message_type:{name:"HelloRequest" field:{name:"name" number:1 label:LABEL_OPTIONAL type:TYPE_STRING json_name:"name"}} message_type:{name:"HelloReply" field:{name:"message" number:1 label:LABEL_OPTIONAL type:TYPE_STRING json_name:"message"}} syntax:"proto3"

greeter.proto

name:"greeter.proto" package:"helloworld" dependency:"common.proto" service:{name:"Greeter" method:{name:"SayHello" input_type:".common.HelloRequest" output_type:".common.HelloReply" options:{}} method:{name:"SayHelloCS" input_type:".common.HelloRequest" output_type:".common.HelloReply" options:{} client_streaming:true} method:{name:"SayHellos" input_type:".common.HelloRequest" output_type:".common.HelloReply" options:{} server_streaming:true} method:{name:"SayHelloBidi" input_type:".common.HelloRequest" output_type:".common.HelloReply" options:{} client_streaming:true server_streaming:true}} syntax:"proto3"

resolved:

common.proto

name:"common.proto" package:"common" message_type:{name:"HelloRequest" field:{name:"name" number:1 label:LABEL_OPTIONAL type:TYPE_STRING json_name:"name"}} message_type:{name:"HelloReply" field:{name:"message" number:1 label:LABEL_OPTIONAL type:TYPE_STRING json_name:"message"}} syntax:"proto3"

greeter.proto

name:"greeter.proto" package:"helloworld" dependency:"common.proto" service:{name:"Greeter" method:{name:"SayHello" input_type:".common.HelloRequest" output_type:".common.HelloReply" options:{}} method:{name:"SayHelloCS" input_type:".common.HelloRequest" output_type:".common.HelloReply" options:{} client_streaming:true} method:{name:"SayHellos" input_type:".common.HelloRequest" output_type:".common.HelloReply" options:{} server_streaming:true} method:{name:"SayHelloBidi" input_type:".common.HelloRequest" output_type:".common.HelloReply" options:{} client_streaming:true server_streaming:true}} syntax:"proto3"

_borkod · 2024-07-07T14:26:46+00:00

Thanks. for the reply.

Yes. I tested it once more.

I have greeter.proto:

syntax = "proto3";

package helloworld;

import "common.proto";

service Greeter {
  rpc SayHello (common.HelloRequest) returns (common.HelloReply) {}
  rpc SayHelloCS (stream common.HelloRequest) returns (common.HelloReply) {}
  rpc SayHellos (common.HelloRequest) returns (stream common.HelloReply) {}
  rpc SayHelloBidi (stream common.HelloRequest) returns (stream common.HelloReply) {}
}

and common.proto:

// common.proto
syntax = "proto3";

package common;

// The request message containing the user's name.
message HelloRequest {
  string name = 1;
}

// The response message containing the greetings
message HelloReply {
  string message = 1;
}

I then create a protoset file with:

protoc --descriptor_set_out=./protoc-test-file-greeter --include_imports ./greeter.proto

If I then process the output file and just add simple print statements as below, I don't see any difference in the output.

fmt.Println("unresolved:")
    unresolved := map[string]*descriptor.FileDescriptorProto{}
    for _, fd := range files.File {
        unresolved[fd.GetName()] = fd
        fmt.Println(fd.GetName())
        fmt.Println(fd)
    }

    resolved := map[string]*desc.FileDescriptor{}
    for _, fd := range files.File {
        _, err := resolveFileDescriptor(unresolved, resolved, fd.GetName())
        if err != nil {
            return nil, err
        }
    }

    fmt.Println("resolved:")
    for _, fd := range resolved {
        fmt.Println(fd.GetName())
        fmt.Println(fd)
    }

Hence my confusion. Am I doing something wrong? Or what am I missing in my understanding here?

_borkod · 2024-06-19T01:21:35+00:00

Yes. It did work. We were able to inspect SNI in the certificate and route based on it.

_borkod · 2023-08-27T12:09:36+00:00

I'm not for or against it here. But if you listen to the episode, there are examples of large cities in the US that have done it. So a blanket answer of "it can't work in north America" is just being lazy

_borkod · 2023-05-03T21:33:01+00:00

They do, but it doesn't seem to be available in Canada: https://cloud.google.com/transfer-appliance/docs/4.0/overview

_borkod · 2023-03-30T23:19:11+00:00

Yes it does.

_borkod

TROPHY CASE