Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Eyal
    @eyalhei
    @rualatngua Wanted to know if there is a similar implementation to pub-sub, and if not, would they accept a PR if add it? or should I write a separate package?
    (also wanted to let know the unit-tests do not pass due to an issue with sinon.spy)
    Daniel Rodríguez Rivero
    @danielo515
    @tegamckinney in my experience on any docker environment the only thing that works is to use the container IP, at least for Seneca mesh
    Mike Lindenau
    @MikeLindenau
    We have been using seneca at our startup for over a year now.. We love it and believe in its potential so much we decided to open up our platform we use internally to release services. If you join the our beta list we will send out invites as soon as we are ready ... join at http://esc.launchrock.com/
    Artak
    @artakvg
    I'd like to see Seneca supporting Zeronode transport, its much more reliable than what Seneca is using and ~ 5x faster
    https://www.npmjs.com/package/zeronode
    Yugo
    @MiYogurt
    why the seneca-mesh example sample code not work.
    image.png
    image.png
    Yugo
    @MiYogurt
    i found a solution senecajs/seneca-mesh#112 should add base.js init a swim network,and ready callback function
    Thank you, though no one.
    Daniel Rodríguez Rivero
    @danielo515
    In general, seneca-mesh is on an unmaintained state
    I am myself making several patches in order to make it scalable
    Daniel Rodríguez Rivero
    @danielo515
    Is anyone facing seneca: transport_client_null errors, and more importand, does anyone know how to fix them ?
    Ohm Trivedi
    @ohmtrivedi
    If I am using Express for my API server, my requests does get forwarded to my microservice listener. But, if I am using Connect & HTTP Server to create my API server, then the same request (http://localhost:12001/api/msOne/fpOS?target=<someIP>) doesn't get forwarded to the microservice listener
    Will the URL be different in case of Connect?
    Khánh Trần
    @rualatngua
    hi @rjrodger, could you check if seneca-meshis supported meta$?
    I also try this fixed but still can not received meta$
    tswaters/seneca-mesh@b9f08fc
    Khánh Trần
    @rualatngua
    @MiYogurt https://github.com/rualatngua/seneca-mesh-kubernetes here is my sample code for seneca-mesh
    we're using seneca-mesh on some production now
    not a busy system but it works
    @rjrodger about meta$ info, I found that in transport-util Wrek.post don't send meta$/custom object
    the meta.test.js is pass but failed for HTTP transport
    I think missing meta$ things like Open Tracing can not work
    seneca-transport-missing-meta.png
    Khánh Trần
    @rualatngua
    Justin
    @fluidnotions
    Is there any transport plugin where you can just supply a list of urls (am using NSD to keep the list current) and then whenever you act the msg just gets sent to the list with a Promise.all if it's an observe$ or a Promise.first if it's consume...I seem to remember seeing something similar in the code at the beginner or the year
    Khánh Trần
    @rualatngua
    @fluidnotions might be seneca-mesh (this plugin go with seneca-balance-client plugin)
    Jet Rico
    @dragonjet
    hi there, i recently submitted an issue on github, and for us his is a critical thing as we are using something in production that broke in a recent publish senecajs/seneca#733
    can someone help us? thanks
    Khánh Trần
    @rualatngua
    @dragonjet here is my quick fix rualatngua/seneca@7576b74
    but I can't create PR because Travis build failed
    :(
    @dragonjet this bug has been fixed 2 days ago
    Martin Mueller
    @matiger
    hey guys, I am having an issue with my microservice. The following error-message is showing up: {"kind":"fatal","level":"fatal","plugin":"seneca","tag":"3.8.0","id":"73pd8bskulzk/1547564510819/1/3.8.0/-","code":"bad_plugin_tag","notice":"seneca: The plugin tag string, if defined, must be alphanumeric (matching /^[a-zA-Z0-9_]+$/), and cannot be longer than 1024 characters. Name was '[name?]', and tag was '2.2.0‘.“. I dont know what „plugin tag string“ it is talking about. I am using seneca@3.7.0 and the seneca-amqp-transport@2.1.0 plugin
    Martin Mueller
    @matiger
    is this the same issue as above?
    Martin Mueller
    @matiger
    Looks like it is because the PLUGIN_TAG for the amp-transport is 2.0.0 and you guys changed it so no .s are allowed anymore.
    2.2.0*
    Martin Mueller
    @matiger
    There might be a fix for that: senecajs/seneca-amqp-transport#130
    shonabell
    @shonabell
    Hi
    can someone guide me? I'm trying to setup like an API gateway. How can I define the routes in the plugin and have the api gateway redirect to the micro services?
    Should the api gateway not use sencia web and just proxy to the micro services?
    neo6053
    @neo6053
    hi, is there any documentation for legacy function such as loghandler?
    Khánh Trần
    @rualatngua
    Should the api gateway not use sencia web and just proxy to the micro services?
    You can use Hapi with a good plugin for seneca.
    I mostly use ExpressJS or Fastify as API gateway, I add a seneca-client to forward requests to downstream services.
    ghter123
    @ghter123
    I am a newbie and I am very upset now. Please pay attention to my Issue post at senecajs/seneca-store-test#47.
    Thank you.
    Tommi Vainikainen
    @tvainika
    What tracing systems have you used with senecajs to have traces for interaction between microservices?
    pusaphil
    @pusaphil
    I am new in NodeJS and i am using seneca version 3.4.3 with seneca-amqp-transport and rabbitMQ as a broker (not sure if terminology is correct).
    I noticed that if you have a seneca listener script (RPC) connect to rabbitMQ, and somehow kill the rabbitMQ, the listener dies as well. My question is how do you track the "dying" part of the listener script? I noticed it emits a 'kill' signal that can be capture via process.on('kill', () => {}), but i want to capture it on the seneca level - something like seneca.on('disconnect', () => {}) kinda thing.
    Mike Lindenau
    @MikeLindenau
    This is super raw but would love any feedback. https://github.com/nscale/usrv
    Julien Perrenoud
    @jfperren

    Hey everyone!

    I am a new Seneca user trying to use Seneca as part of my fairly simple Express/MongoDB setup. More specifically, I am trying to make my models use seneca-entity backed by seneca-mongo-store. This works great, but I cannot find a good way to implement some kind of schema validation.

    In a previous project, I used Mongoose to create schemas which would automatically validate the data upon creation/update. I would like a similar thing here but I could not find good documentation about mongoose/seneca integration online and it feels like Mongoose would be fairly redundant here, or at least a bit clunky to integrate. I feel like there's got to be a better way.

    Am I doing this wrong? How are you guys validating your mongodb data with seneca entities?

    Thank you all in the community for building this project!

    Fran
    @Paker30
    Hi @jfperren I'm not an expert either but at my company we work with Seneca and if you want to add some schema validation, take a look at https://github.com/senecajs/seneca-joi it would give you validation schemas against your pines, you can always check what you send in the pin with the schema