theflagbug
Joined 13 years ago
Joined 13 years ago
Just a few days ago the service connection to Azure suddenly stopped working with "401 CouldNotFetchAccessTokenForAzureStatusCode" which appeared when deploying to Azure AppService. We had to recreate the service connection to get it working again.
Recently we also wanted to move our Android builds to Azure DevOps but in the end the documentation was so confusing that we just used Bitrise instead.
Sadly this goes for a lot of Azure services and all the enterprise-buzzword laden documentation doesn't make that easier
Also, the Azure Portal is ridiculously bad and slow.
Interesting, I had the exact opposite experience, since the Java->C# mappings often reduce much of the boilerplate code that you have to write if you were using Java (e.g C# events, properties, etc..)
I also never came across any bugs in the mappings, but I can't say for sure that there aren't any.
Xamarin Forms may be useful for internal super-CRUD LOB apps that really are just a collection of input fields, but as soon as you do anything customer facing, you should be using the standard native UI approach.
Also +1 for ReactiveUI, it completely changed the way I build apps for the better.
Source: I'm the developer of said versions :)
> I tried the small dictionary john.dict that comes with John-the-Ripper, and it didn't find anything. But of course, I don't need a real dictionary. The password is probably also in the clear in the memory dump. I could just use the file super.txt as my dictionary! I tried this, but it was taking a long time, with 150k unique lines of text. It'd take many hours to complete. To speed things up, I filtered the list for just lower-case words
1.) In the StartSenders method, you're violating the Rx grammar by calling channel.OnNext concurrently. Wrap it on a lock statement.
2) In StartReceiver you're missing out messages the way you handle the channel. Replace the loop with a call to channel.Subscribe