Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 26 05:41

    DamianMac on develop

    github secrets (compare)

  • Sep 25 22:45
    DamianMac closed #283
  • Sep 25 22:45

    DamianMac on develop

    Release Dotnet 5 / core branch … (compare)

  • Sep 25 22:45
    DamianMac closed #305
  • Sep 25 22:43
    DamianMac opened #305
  • Sep 25 08:44

    DamianMac on build-workflow

    added in newget task (compare)

  • Sep 25 01:54

    DamianMac on build-workflow

    go back to full integration tes… (compare)

  • Sep 25 01:51

    DamianMac on build-workflow

    specify trx files (compare)

  • Sep 25 01:40

    DamianMac on build-workflow

    typo in unit test path (compare)

  • Sep 25 01:35

    DamianMac on build-workflow

    bump test result publish version (compare)

  • Sep 25 01:31

    DamianMac on build-workflow

    test loggers (compare)

  • Sep 25 00:09

    DamianMac on nuget

    (compare)

  • Sep 25 00:09

    DamianMac on build-workflow

    Bump Newtonsoft.Json in /src/Ni… (compare)

  • Sep 25 00:09
    DamianMac closed #303
  • Sep 25 00:09
    DamianMac edited #303
  • Sep 25 00:09

    DamianMac on nuget

    (compare)

  • Sep 25 00:08

    DamianMac on build-workflow

    Bump Azure.Storage.Blobs in /sr… (compare)

  • Sep 25 00:08
    DamianMac closed #304
  • Sep 25 00:08
    DamianMac edited #304
  • Sep 24 23:45

    DamianMac on build-workflow

    update artifct upload (compare)

Drew Freyling
@drewfreyling
@DamianMac @uglybugger any word on ^^
ybesson
@ybesson
Hi, anybody experienced some timeout issues (RPUSH and other commands) with Redis Transport (on Nimbus V3) with Azure Redis?
Mustafa Arif
@ma499
I've just noticed that Nimbus 3.0 now Receives rather than Peeks messages from Windows Service Bus - meaning that it is now using the 'at most once' message delivery guarantee rather than 'at least once'. Is this really desirable? For us the ability to rely on the message bus guarantees is crucial to the decision to use one in the first place.
We use appveyor on our fork (of 2.x). We just accept that it doesn't run the integration and stress tests.
Drew Freyling
@drewfreyling
I've opened up NimbusAPI/Nimbus#253 as I wasn't getting a response here
Mustafa Arif
@ma499
If anyone wants to orchestrate sagas across nimbus, we've released the state machine we're using to do that: https://github.com/Aqovia/Aqovia.SagaMachine
Drew Freyling
@drewfreyling
@uglybugger @DamianMac any reason this one is being ignored - especially given that v3 hasn't been realised as final yet? NimbusAPI/Nimbus#253
Granville Schmidt
@gramidt
Hey everyone! Just found out about NimbusAPI a couple days ago on a flight back home. Looking forward to digging in and and contributing.
Mustafa Arif
@ma499
There are quite a few pull requests left hanging. in some cases for over a year. Any chance @uglybugger, @DamianMac that you could start declining (with reasons) the ones that you don't want to accept at all, or feedback on where you want changes?
Granville Schmidt
@gramidt
Looking forward to checking out your state machine @ma499!
Richard Dalziel
@RDalziel
Anyone else get issues with registering types with a failed Microsoft.ServiceBus (Or dependency) load?
Richard Dalziel
@RDalziel
Sorted - was just faulty app config assembly bindings!
Drew Freyling
@drewfreyling
@DamianMac why did u close #253 it hasn't been addressed yet or even commented on by the team?
I feel like the lack of communication of v2 and the missing bug fixes to be quite poor - especially when v3 isn't available yet
Damian Maclennan
@DamianMac
Sorry @drewfreyling I was trying to do a cleanup. We decided last night to just do a v2 fork and set up a separate build. Running the v2 and v3 builds on the one config was just too painful
Drew Freyling
@drewfreyling
ok sounds good - do you guys need a hand with that?
we manually built a copy of 2.0.0.98 with the #249 fix and are using that across alot of microservices
so a v2 build with #249 in it would be less painful until v3 is finalised
(on myget or nuget)
markduk
@markduk
Hey everyone, we're making use of Nimbus v3 and need to use the large message feature but it seems to be removed in v3, the packages are there but BlobStorageBuilder is gone. Are large messages done another way now? Many thanks
markduk
@markduk
@uglybugger @DamianMac , hi guys. Is there a way to access CorrelationId's and MessageId's within a handler? I want to include them in my logs. Thanks
Justin Patterson
@StandBackBurrito
Any word on when v3 might be released? we are looking into Nimbus but hoping to get a timeline
Justin Patterson
@StandBackBurrito
@uglybugger I noticed a peek lock spike branch in the repo has anybody tried it out
I would really like to use that, gonna give it a try
Mustafa Arif
@ma499
@uglybugger, @StandBackBurrito what's the status of the PeekLock branch? I can make some time to help complete it.
@KodrAus did you make any progress with a port to CoreCLR?
Granville Schmidt
@gramidt
I'm also interested in the status of both the PeekLock branch and the port to CoreCLR.
Ashley Mannix
@KodrAus
@ma499 Howdy! Sorry I didn't really make progress while CoreCLR was churning. I made the mistake of trying to do the whole thing Sans-Windows. I don't think I'm going to have time to come back and pick that up anytime soon :(
Drew Freyling
@drewfreyling
anbody had any issues with .net 4.61+ and multiple dns claims on nimbus 2 or 3?
looks like only 3.1.3 of windowsazure.servicebus fixes it
which nimbus 2 and nimbus.transports.windowsservicebus do not allow!
Chui Tey
@teyc
@drewfreyling where did you find the latest v2 builds? nuget is still at 2015
Drew Freyling
@drewfreyling
@teyc NimbusAPI/Nimbus#253
Apparently there isn't any build infrastructure setup for v2 while v3 is being built
I've offfered help in this area but haven't heard anything back from @DamianMac
Chui Tey
@teyc
dang.
Drew Freyling
@drewfreyling
there are some nasty bugs after 2.0.0.98 which would be nice to have an official build for
NimbusAPI/Nimbus#249 is one of them
Chui Tey
@teyc
Is that in the Nimbus_V2 repo ?
Drew Freyling
@drewfreyling
so we just need to get some builds happening on that "fork"
Chui Tey
@teyc
Good stuff, I might get an appveyor account and do some unofficial builds.
Mustafa Arif
@ma499
I've got builds running on our own fork. I could use the config to set something up for v2 - although our own fork is also public, with the nuget artefacts in bintray.
Mustafa Arif
@ma499
Okay, @teyc , unofficial V2 builds from our fork are now available (follow link in Readme): https://github.com/Aqovia/Nimbus
Hadi Eskandari
@HEskandari
Hello, any news on v3 release? Would be great if you confirm if #267 has been fixed in v3 or not?
Jonathan Yee
@jonyeezs

Question: When an exception is thrown, nimbus will retry the event. This is a nice feature to have. But there are occasions where we don't want to retry and put it on the deadletter queue immediately for manual intervention.

How can i bypass the retry mechanism and straight to the dead letter queue?

Luke Schafer
@lukeschafer
@jonyeezs I can't remember specifically (been a long time since I used Nimbus), but if nothing else you can add an error interceptor and manually bump up the delivery attempts. That said, I swear there's a better way
Jonathan Yee
@jonyeezs
@lukeschafer that's what i've gone for. wish i could just do bus.DeadLetterIt(message)
Shingi Mutandwa
@shingi
Just started upgrading an existing v2 solution to v3 using Windows Service Bus. Having issues with registrations and I have been looking for more samples to see if configuration has changed. Nimbus.Configuration.PoorMansIocContainer.DependencyResolutionException : No registration for type Nimbus.Transports.WindowsServiceBus.Filtering.ISqlFilterExpressionGenerator