dependabot[bot] on nuget
Bump Newtonsoft.Json in /src/Ni… (compare)
DamianMac on build-workflow
upload artifacts (compare)
DamianMac on build-workflow
restore. derp (compare)
DamianMac on build-workflow
set dotnet version (compare)
DamianMac on develop
use env vars (compare)
DamianMac on develop
global (compare)
DamianMac on develop
install cake (compare)
DamianMac on develop
yaml formatting (compare)
DamianMac on develop
yummy yaml (compare)
DamianMac on develop
port build infra directly to gi… (compare)
DamianMac on 4.2.0
DamianMac on large-message-redux
DamianMac on develop
Large message redux (#302) * a… (compare)
DamianMac on large-message-redux
added back in azure large messa… package blob store project (compare)
Hey all .. we're getting this message repeatedly in production: "Lock for message c1e4f985949849b6812d55650bdc0def appears to have already expired so we're not dispatching it. Watch out for clock drift between your service bus server and DESKTOP-R6O92KC!"
Obviously we've checked the clocks and there is no drift. We're currently not able to pull any messages off the queue because of this. Anyone else come across this? Cheers.
System.IndexOutOfRangeException: Probable I/O race condition detected while copying memory. The I/O package is not thread safe by default. In multithreaded applications, a stream must be accessed in a thread-safe way, such as a thread-safe wrapper returned by TextReader's or TextWriter's Synchronized methods. This also applies to classes like StreamWriter and StreamReader.
at System.Buffer.InternalBlockCopy(Array src, Int32 srcOffsetBytes, Array dst, Int32 dstOffsetBytes, Int32 byteCount)
at System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.IO.TextWriter.SyncTextWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.Diagnostics.TextWriterTraceListener.WriteLine(String message)
at System.Diagnostics.TraceInternal.WriteLine(String message, String category)
at Nimbus.Configuration.GarbageMan.Add(Object component)
at Nimbus.Infrastructure.NimbusMessagingFactory.CreateTopicSender(String topicPath)
at Nimbus.ConcurrentCollections.ThreadSafeDictionary`2.GetOrAdd(TKey key, Func`2 valueFunc)
at Nimbus.Infrastructure.Events.BusEventSender.<Publish>d__0`1.MoveNext()
Hi everyone! We are using Nimbus API as Windows Services. I am trying to confirm, do the actual Windows Services need any special permissions to run? Can they just run as Local System? Do we need to create a service account that has local Administrator permissions?
Any info most appreciated :)