Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    FoxMaSk
    @foxmask
    I agree
    Antonio Di Mariano
    @antoniodimariano
    in the end, nothing is simple in a microservices architecture so
    ...
    for exampe, anyone know how I can disable the debug message in nameko
    I am using the logging module
    but I have the console full of msgs like
    2017-12-19 15:35:46,472 nameko.containers DEBUG    signalling result for <WorkerContext [proxy.register_action] at 0x105ce79b0>
    tore down worker <WorkerContext [proxy.register_action] at 0x105ce79b0> in 0.000s
    FoxMaSk
    @foxmask
    i tested wamp.ws earlier ; I think I could find my marks but it's not trivial ; need time to test
    Antonio Di Mariano
    @antoniodimariano
    what’s about?
    in order to dinamically assign a proxy?
    FoxMaSk
    @foxmask
    or event_handler
    Matt Yule-Bennett
    @mattbennett
    @antoniodimariano, add a logging configuration to your config.yaml and set the level of the root logger there. example: http://nameko.readthedocs.io/en/stable/cli.html?highlight=logging#running-a-service
    Antonio Di Mariano
    @antoniodimariano
    thanks a lot.
    Matt Yule-Bennett
    @mattbennett
    @foxmask there is a recent thread on the mailing list exactly about dynamic RPC proxies: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/nameko-dev/XE-uarCEV00
    FoxMaSk
    @foxmask
    @mattbennett thanks a lot
    FoxMaSk
    @foxmask
    @mattbennett any other example about dynamic event_handler ? I would like to be able to use the decorator ; but with a new of a service I don't know yet. like in the example of dynamic RPC proxies
    FoxMaSk
    @foxmask
    i'm asking myself what's the concept of containers ... that's a service with specific config ? and about ServiceRunner ? what's the goal of runner.add_runner() ?
    runner.add_service() i meant
    Matt Yule-Bennett
    @mattbennett
    @foxmask no such example dynamic event handlers i'm afraid. wouldn't be too difficult to implement yourself though, if you study the existing event hander
    @foxmask re containers, yes -- the container is the thing that runs a singular service. it manages the extensions (entrypoints, dependency providers) declared by the service and creates workers when an entrypoint fires. the runner is just a convenience wrapper around one or more containers.
    FoxMaSk
    @foxmask
    the runner bootstraps services that are not necessary linked with each other ?
    Matt Yule-Bennett
    @mattbennett
    not sure what you mean by bootstrapping. it will just run any services that you ask it to, each in their own containers
    when you do nameko run <module> on the command line, nameko will discover any service classes defined in <module> and start them all under one runner
    FoxMaSk
    @foxmask
    ok
    Antonio Di Mariano
    @antoniodimariano
    Hi guys,
    I was wondering where I can find a nice guide to logging
    I dunno, I think I’ve not understood the logging system
    but still I have a weird logging
    Antonio Di Mariano
    @antoniodimariano
    for example, at start time, I’d like to print something like “service listening on "
    and show the ip address and the port as well.
    FoxMaSk
    @foxmask
    Hi
    I try to use the factory pattern to be able to make dynamics calls of services, but I'm facing an issue with a dispatching method https://gist.github.com/foxmask/9fa8cf16392e5fa66804ee0380894bef how could I fix that ?
    Matt Yule-Bennett
    @mattbennett
    @foxmask i commented on your gist
    FoxMaSk
    @foxmask
    @mattbennett thanks a lot ! I'll try it soon
    yumxiao
    @yumxiao
    hi all, how to monitor namkeo service?
    Matt Yule-Bennett
    @mattbennett
    @yumxiao check out https://github.com/Overseas-Student-Living/nameko-tracer for capturing entrypoint traces, and https://github.com/mattbennett/nameko-sentry for sending worker tracebacks to sentry
    Dani Guardiola
    @DaniGuardiola
    Hi there
    Trying to user worker_factory but I don't know how to pass arguments to the service class constructor
    Is there any clean way of doing this?
    Dani Guardiola
    @DaniGuardiola
    Trying to use*
    Matt Yule-Bennett
    @mattbennett
    @DaniGuardiola Nameko service classes should not have custom constructors. They are stateless and not instantiated like normal objects in the OOP sense. All state should live in dependencies. The worker_factory is for providing alternative dependencies when creating a service worker.
    You might want to post a question on https://discourse.nameko.io to get more information.
    李满满
    @forcemain
    hi
    Matt Yule-Bennett
    @mattbennett
    :wave:
    Davis Kirkendall
    @daviskirk
    Is there a roadmap for when 3.0 is coming out? There are a lot of nice changes to the rpc implementations that we really like (nice work on that by the way)
    Matt Yule-Bennett
    @mattbennett
    @daviskirk no definite timeline, but should be soon. It's been out in prerelease for long enough for us to feel confident. @iky just has a couple more tweaks to the config changes that he wants to make
    in the mean time you can install the prerelease now with pip install --pre nameko. more prerelease users are always appreciated
    Gustavo Gawryszewski
    @gawry
    How would you compare nameko with Celery and Dramatiq?
    Matt Yule-Bennett
    @mattbennett
    @gawry if you ask this question over on the forum (https://discourse.nameko.io) i'll be able to give a more in-depth answer. the gist is that celery and dramatiq are for outsourcing jobs to workers, whereas nameko is a framework specifically designed for creating microservices