devblog | adesso Developer Blog | Blog library

The root cause of the stuck issue is that the pipeline microsoft-hosted agent for public and private projects in the new organization has been restricted in the latest update.

For more detailed info, you could refer to these two docs: Private Project Pipelines, Public Project Pipelines.

In Release 183, the reasons for adding restrictions are as follows:

Over the past few months, the situation has gotten substantially worse, with a high percentage of new public projects in Azure DevOps being used for crypto mining and other activities we classify as abusive. In addition to taking an increasing amount of energy from the team, this puts our hosted agent pools under stress and degrades the experience of all our users – both open-source and paid.

Private Project:

You could send email to azpipelines-freetier@microsoft.com in order to get your free tier.

• Your name
• Name of the Azure DevOps organization

Public Project:

You could send email to azpipelines-ossgrant@microsoft.com in order to get your free tier.

• Your name
• Azure DevOps organization for which you are requesting the free grant
• Links to the repositories that you plan to build
• Brief description of your project

Windows Hello may meet your requirement. It works with the Azure Active Directory account or Microsoft Account connected in Windows settings, and it replaces passwords with strong 2FA by verifying your biometric. Besides, in Windows Hello architecture you no longer need to host your Ory Kratos OAuth2 server.

I found the solution:

I had to change the sdk in the csproj file from Microsoft.NET.Sdk.Worker to Microsoft.NET.Sdk.Web.

(Basically the project is a .NET 5 SDK-style Windows Service / BackgroundWorker with an Asp.Net Core API included.)

It seems this was not an issue with earlier versions before 8.*

To recap:

A DLL's DLLMain/DLLProc is called whenever a process is "attached/detached" and a thread is "attached/detached"

• DllMain entry point
• Dynamic-Link Library Entry-Point Function

There is also a blog post by Raymond Chen that discusses thread deadlocks in DLLMain.

Because DLLMain is called when the the DLL is unloaded and also when a thread exits I cannot do a thread WaitFor in the DLL Unloading code (OnWebModuleDestroy) as that will obviously cause a deadlock as the one will be waiting for the other.

After R.Hoek's comment I started looking to see if Apache calls some sort of cleanup procedure before it actually unloads the module DLL and came upon its apr_pool_cleanup and the companion apr_pool_cleanup_register procedure which registers a hook into the the cleanup. Fortunately this has already been handled inside the Web.ApacheApp unit and its TApacheApplication class that has an OnTerminate "event" which is called by the apr_pool_cleanup.

Assigning cleanup code to the OnTerminate "event" allows you to properly get rid of your threads without fear of deadlocks in DLLMain:

It somewhat depends on what you want the export to look like. However, the below example is a starting point:

Does the fact that I omitted await and did not declare SaveImage as async make it actually [synchronous]?

No. async void methods are dangerous for several reasons. They're asynchronous, but there's no way for your code to detect when the asynchronous operation completes. Also, since there's no way for your code to detect errors from the asynchronous operation, any exceptions are raised directly on the current context, which usually results in an application shutdown. This behavior seems very odd an undesirable, until you realize that async void methods were specifically designed to be used as event handlers, and should be avoided in other scenarios.

What I would expect to happen is that the loop would instantly complete because even though WritePngAsync takes a long time SaveImage is not awaited and would return instantly.

Yes, the loop completes quickly, and all of the PNG.WriteAsync operations may be incomplete when the loop completes.

I think this is causing issues with the file contents being overwritten when called like this

That sounds reasonable. Your code cannot know when the WritePngAsync methods are complete.

Currently in VS Code, it supports single condition filtering, but it does not support ">2006 AND <2014".

So I have submitted this problem and you could follow it: Can the "data viewer" in VS Code filter data with multiple conditions?

TLDR:

Remove this from appsettings.json:

Hey I recently did a video on implementing webhooks with Xero, let me know if this gets you unstuck. I found that trying to pass itrBodyParser on the route the way you have wasn't working for me so I switched it with an app.use statement on my specific webhooks endpoint. If you prefer a written guide over video, here's the blog post