Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 20 2022 07:54

    DamianMac on develop

    fix missing comma (compare)

  • Dec 20 2022 07:49

    DamianMac on develop

    Update redis client (#306) * r… (compare)

  • Dec 20 2022 07:49
    DamianMac closed #306
  • Dec 20 2022 07:49
    DamianMac opened #306
  • Dec 20 2022 07:48

    DamianMac on update-redis-client

    user myget instead (compare)

  • Dec 20 2022 06:37

    DamianMac on update-redis-client

    nuget tweaks (compare)

  • Dec 20 2022 06:25

    DamianMac on update-redis-client

    big update, skip integration te… (compare)

  • Dec 20 2022 05:27

    DamianMac on update-redis-client

    deprecated cakes (compare)

  • Dec 20 2022 05:23

    DamianMac on update-redis-client

    derping on dotnet versions (compare)

  • Dec 20 2022 05:20

    DamianMac on update-redis-client

    net 6 upgrade (compare)

  • Dec 20 2022 05:15

    DamianMac on update-redis-client

    rev redis binaries build this branch (compare)

  • Sep 26 2022 05:41

    DamianMac on develop

    github secrets (compare)

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

    DamianMac on develop

    Release Dotnet 5 / core branch … (compare)

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

    DamianMac on build-workflow

    added in newget task (compare)

  • Sep 25 2022 01:54

    DamianMac on build-workflow

    go back to full integration tes… (compare)

  • Sep 25 2022 01:51

    DamianMac on build-workflow

    specify trx files (compare)

  • Sep 25 2022 01:40

    DamianMac on build-workflow

    typo in unit test path (compare)

Luke Schafer
@lukeschafer
If we decide to go to rabbit + nimbus, it would depend on the V3 timelines (prod quality release etc) because our times are tight. What we can't afford is issues like that one recently raised by @drewfreyling and amos
IF that's the path we decide on, we're happy (and probably need to) contribute, but like I said, we are about to embark upon the investigation
so like, don't do anything for our sake :) but if you are about to do it anyway, keep us up to date here
Damian Maclennan
@DamianMac
So you're moving off your tightly coupled SOAP mess ?
Luke Schafer
@lukeschafer
have been doing that for yonks
but it's a slow process, and we've had.... issues.... with service bus so we're not keen to do a full migration yet
Drew Freyling
@drewfreyling
i'm curious as to the prod quality of the builds 2.0.0.98 - 2.0.0.232?
they were never released to nuget
plus with #249 now on top of the v2 branch (which includes everything from 98-232)
Luke Schafer
@lukeschafer
I was wondering if perhaps appveyor or something might be better than the private TC server
at the moment that probably wouldn't work due to how the solution/packages are set up (could be wrong), but if it was made to work, people could easily fork nimbus and point at their appveyor nuget to more easily control what version they are using
Damian Maclennan
@DamianMac
Going to have a look at it with @uglybugger later, not sure if appveyor will like the integration and stress tests we have
happy if somebody wants to try to get it to work though
TheeJamesLee
@TheeJamesLee
Hi all, I pulled down v3 from the MyGet source for a new project and think there might be a bug with the windows service bus transport. Not sure if you guys wanted an issue logged on the current repo or not so thought I'd mention it here. Created a handler for a competing consumer event that recieved the message fine - however on an exception during message handling it looks like the transport is trying to create a queue with the same name as the topic (which it won't allow on ASB) so fails to put the message back for any form of retry / dead lettering, etc
Damian Maclennan
@DamianMac
Hey @TheeJamesLee can you please open up a GitHub issue and we can take a look
TheeJamesLee
@TheeJamesLee
Thanks @DamianMac , just opened the issue.
Mustafa Arif
@ma499
I have had a working Appveyor.yml in my fork for yonks. However, I had to disable the stress tests as @DamianMac suspected. I still think it's of use for community contributions and just have the stress tests run separately in TC. Happy to contribute .
Drew Freyling
@drewfreyling

@DamianMac @uglybugger any word on my questions about the unreleased versions of v2 that are in the v2maint branch?

plus with #249 now on top of the v2 branch (which includes everything from 98-232)

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!