cts | WebGPU Conformance Test Suite

Try encapsulating your query in cts:properties-fragment-query like so:

According to the source, nothing. They both assign to m_timer

To paraphrase the question:

Why, when you create a linked CancellationTokenSource from a CancellationTokenSource with a registered timeout, then set the resultant token source with a timeout of zero, does it not know it should be cancelled?

More paraphrasing:

After all, zero is zero and it should know it's cancelled.

The answer is, because a CancellationTokenSource.CancelAfter tries to register a timer callback, which attempts to set the resolution to zero milliseconds which it cannot possibly honor.

So in turn, you get the minimum resolution any standard timing mechanism can give you without using CPU spins, which is about 5+ milliseconds.

There are likely other solutions to your problem, however, in short you can't rely on a 0 second timeout to give you immediate confirmation via IsCancellationRequested. You will need to rethink your problem.

Use a CancellationTokenSource, in a somewhat simplified example:

I was a bit surprised, but it looks like this is on purpose. When a registration is cancelled, CancellationTokenSource still keeps the instance of CancellationTokenSource+CallbackNode in a free-list to reuse it for the next callback. This is an opiniated optimization, that can backfire in your scenario.

To illustrate this, try running your test twice in a row:

This is actually a common issue not only in MarkLogic but many other DBMS and search engine systems too.

You can locally run a query like this to verify it:

As far as I can see, this is just a wrapper around Threading.Timer with a bunch of extra stuff around it that does not add any actual functionality. Your timer works by calling Task.Delay, but this is just a wrapper around Threading.Timer, so you might as well cut out the middleman.

Most the functionality you expose is already provided by this timer by calling the .Change method. If you want to provide a more intuitive interface I would suggest wrapping this timer, or provide some extension methods, instead.

If you want the behavior that guarantees that the event is not raised concurrently, and that the execution-time is added to the period time, you should wrap the timer and set some due-time and an infinite period. Then at the end of your event handler you would call .Change again to restart the timer.

If you write a simple wrapper around Threading.Timer you will have a much easier time ensuring thread safety, since the Threading.Timer is thread safe.

As it is, I think your class is probably kind of thread safe. But I'm fairly sure it can cause some behavior that is unexpected. For example, calling .Start() multiple times would cause multiple loops to be started. I would have expected such a method to be idempotent.

You've put the ENV statement in the 'build' part of the Dockerfile which means that it doesn't get placed in the final image. Either put it in the 'base' part or the 'final' part.

I'd put it in the 'base' section with the other ENV statements.

You might also want to move the apk add to the base or final sections of the file, if you want the software installed in the final image.

The CoRB tasks use the method method getValueAsBytes() invokes: