Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 23 2017 14:09

    jeremydmiller on dotnet

    Bumping to 0.2.13 (compare)

  • May 23 2017 14:07

    jeremydmiller on dotnet

    Add global.json file, bump stor… (compare)

  • May 23 2017 14:07
    jeremydmiller closed #12
  • Apr 27 2017 20:40
    joemcbride synchronize #12
  • Apr 27 2017 20:03
    joemcbride edited #12
  • Apr 27 2017 20:02
    joemcbride opened #12
  • Feb 03 2017 17:14

    CoreyKaylor on dotnet

    Added license (compare)

  • Nov 23 2016 14:01

    jeremydmiller on dotnet

    trying to harden the Queue disp… (compare)

  • Nov 08 2016 14:02

    jeremydmiller on dotnet

    tweaks to the logging, added In… (compare)

  • Sep 23 2016 16:34

    CoreyKaylor on dotnet

    Bumping version and LightningDB… (compare)

  • Sep 22 2016 23:06

    CoreyKaylor on dotnet

    Timeout slow clients (compare)

  • Sep 22 2016 22:01

    CoreyKaylor on dotnet

    Fixes for sending retries, adde… Hardening the sending error pol… (compare)

  • Sep 02 2016 18:54

    CoreyKaylor on dotnet

    Bumping version on lmdb storage (compare)

  • Sep 02 2016 18:48

    CoreyKaylor on dotnet

    Updated lmdb lib for bug fixes (compare)

  • Aug 29 2016 20:34

    CoreyKaylor on dotnet

    Updated LightningDB, fixed test… (compare)

  • Aug 20 2016 15:36

    CoreyKaylor on dotnet

    Bumping version (compare)

  • Aug 20 2016 15:31

    CoreyKaylor on dotnet

    Fixed incorrect logic on length… (compare)

  • Aug 20 2016 00:03

    CoreyKaylor on dotnet

    Bumping version (compare)

  • Aug 20 2016 00:02

    CoreyKaylor on dotnet

    More polish and some end-to-end… (compare)

  • Aug 15 2016 23:39

    CoreyKaylor on dotnet

    Added GetMessage for diagnostic… Bumping version (compare)

Corey Kaylor
@CoreyKaylor
That’s where fubu came in. Along with error policies on message retries, etc.
Jeff Doolittle
@jeffdoolittle
yeah, I am looking forward to seeing what jeremy has in mind for this in 2017
I'm guessing that's what this is a placeholder for: https://github.com/JasperFx/jasper
Corey Kaylor
@CoreyKaylor
it is, it’s always been a moving target though as to what would make it in
the bus portion is the only sure thing to my knowledge
Brad Barnich
@BradBarnich
Hi, is there a license for LQ?
Corey Kaylor
@CoreyKaylor
Should be MIT, but realize now that you’ve asked that it’s not included in the repo.
Corey Kaylor
@CoreyKaylor
@BradBarnich I’ve added the license to the repository now.
Weston
@ronnyek
is lmdbmessage store not part of the nuget package?
also is there a snippet somewhere of like simplest example
I'm trying to convert test code over (which understandably is built for reuse and to be a bit abstract on purpose)
Weston
@ronnyek
ahh another package required for the lmdb store
Weston
@ronnyek
I am seeing this
Exception thrown: 'System.NullReferenceException' in LightningQueues.Storage.LMDB.dll
Exception thrown: 'System.NullReferenceException' in System.Private.CoreLib.dll
but its not actually breaking... is there any easy way to get more information about why publishing causes breakage?
Weston
@ronnyek
So I would like to use lightning queues as a sort of persistent job queue... I effectively send, to localhsot with appropriate port, then when I lose connectivity, I'm disposing the receiver, and then when connection comes back, I re-instantiate the receiver
is that the right way to handle things?
Jeremy D. Miller
@jeremydmiller
Sounds reasonable to me
Weston
@ronnyek
I noticed when I am calling send, and there is no receiver, its throwing extended network exception or something
it does seem to resume sending once my receiver re-attaches
Jeremy D. Miller
@jeremydmiller
C
orrect
Weston
@ronnyek
I guess my question there is, is the throwing of the exception normal, and if I am always intending to deal with this locally (even in process) do I have to go out via tcp?
Jeremy D. Miller
@jeremydmiller
So that’s all that LQ can do today. I did basically rewrite LQ directly into Jasper, and there we’re planning on also supporting HTTP for sending/receiving messages
Weston
@ronnyek
seems like it can use a lot of ports quickly
if you are rapidly pushing messages through it