Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Gutemberg Ribeiro
    @galvesribeiro
    so lets assume the following example:
    in the C# project, you use some attributes at the main(). Those attributes describe the Docker image name, the replicas, etc. The compiler essentially read those metadata, generate the k8s objects from that JSON metadata, and call kubectl -f ...., correct?
    Brendan Burns
    @brendandburns
    yeah, more or less
    Gutemberg Ribeiro
    @galvesribeiro
    oh wait
    Brendan Burns
    @brendandburns
    basically when you run the main()
    it generates a JSON
    Gutemberg Ribeiro
    @galvesribeiro
    humm
    Brendan Burns
    @brendandburns
    then calls the compiler on that JSON
    which generates kubernetes objects
    and then calls kubectl create -f on those objects
    Gutemberg Ribeiro
    @galvesribeiro
    ok
    I wonder how it would work with a debugger
    Brendan Burns
    @brendandburns
    MetaparticleExecutor.cs is the code in question
    Gutemberg Ribeiro
    @galvesribeiro
    like visual studio for example
    Brendan Burns
    @brendandburns
    yeah, it won't really right now
    because it's all async
    but you could imagine using an annotation (or introspection) to detect "debug" and turning up a distributed debugger
    Gutemberg Ribeiro
    @galvesribeiro
    yes
    Brendan Burns
    @brendandburns
    we've done integration with VS Code and containers in Kubernetes for live debugging
    Gutemberg Ribeiro
    @galvesribeiro
    oh! that is cool
    Brendan Burns
    @brendandburns
    though honestly, I've found that live debugging is of limited use in real-world cloud settings
    Gutemberg Ribeiro
    @galvesribeiro
    if it works on VSCode, it should on VS
    well, debug on minikube localy is all the dev wants
    Brendan Burns
    @brendandburns
    yeah, definitely an area where it would be cool to prototype something
    Gutemberg Ribeiro
    @galvesribeiro
    we just need to overrride the ENTRYPOINT to run vsdbg and a cat << /dev/null or something like that
    Brendan Burns
    @brendandburns
    Have you seen:
    Gutemberg Ribeiro
    @galvesribeiro
    yes, I did
    was about to mention that
    I'm still waiting to get invited to that
    Brendan Burns
    @brendandburns
    ah, didn't realize it was private...
    here's the vs code extension
    it can live debug nodejs
    would be relatively easy to adapt to c# I think...
    Gutemberg Ribeiro
    @galvesribeiro
    yeah
    it would
    Brendan Burns
    @brendandburns
    I have devs working on the vs code extension
    (though not in the context of metaparticle)
    Gutemberg Ribeiro
    @galvesribeiro
    ic
    Brendan Burns
    @brendandburns
    it would be interesting to see if there is a good vs-code extension we could add to metaparticle
    haven't thought about it too much.
    got to run, meetings, there are some "help wanted" issues in the metaparticle github
    Gutemberg Ribeiro
    @galvesribeiro
    ok, will have a look
    ttyl
    Brendan Burns
    @brendandburns
    I'll try to file some more to capture what we discussed earlier, would love the help!
    thanks for checking it out!
    Gutemberg Ribeiro
    @galvesribeiro
    :+1:
    Fernando Calheiros
    @xfernando
    hi everyone! just found out this gitter existed! I’m the one who submitted the PR with the initial go implementation :smile: