Skip to content
This repository was archived by the owner on Apr 27, 2026. It is now read-only.

[feature/dotnet8] update arcade sdk#2697

Merged
brettfo merged 1 commit into
dotnet:feature/dotnet8from
brettfo:update-arcade
Feb 8, 2023
Merged

[feature/dotnet8] update arcade sdk#2697
brettfo merged 1 commit into
dotnet:feature/dotnet8from
brettfo:update-arcade

Conversation

@brettfo

@brettfo brettfo commented Feb 7, 2023

Copy link
Copy Markdown
Member

No description provided.

@brettfo
brettfo merged commit dc89102 into dotnet:feature/dotnet8 Feb 8, 2023
@brettfo
brettfo deleted the update-arcade branch February 8, 2023 00:10
colombod added a commit that referenced this pull request Nov 22, 2023
* update dependencies from arcade

* update to dotnet 8

* skip csharpproject kernel tests due to different binlog format

* skip docker build step

* set tool feed to experimental

* update arcade sdk (#2697)

* upgrade projects to <TargetFramework>net8.0</TargetFramework>

* fix api contract

* try multi taget

* Update arcade

* remove multi targets

* Fix new warnings reported from .NET8 SDK.

* new projcts

* [feature/dotnet8] Fix race in KernelScheduler (#3222)

* Use KernelCommandResult.Events in place of Kernel.Events.

* Fix race.

* Enable more complete logging for commands and events in tests.

* Add a test.

* [feature/dotnet8] Fix bug related to resetting of KernelScheduler._currentlyRunningTopLevelOperation (#3237)

Cherry-picked from #3235.

`_currentlyRunningTopLevelOperation` was not being reset in the case where a top-level operation would schedule child operations. In this case, `_currentlyRunningOperation` was correctly being reset when each child operation was completed. However, when the parent operation was completed, we would fail to reset `_currentlyRunningTopLevelOperation` since we were comparing `_currentlyRunningTopLevelOperation` with the value of `_currentlyRunningOperation` (and `_currentlyRunningOperation` would have a value null at this point because it was reset to null when the child operation was completed above).

The above bug was breaking parenting (and command token assignment) for subsequent commands. Subsequent commands were being incorrectly parented to the stale value reflected in `_currentlyRunningTopLevelOperation`. And this in turn was leading to hangs.

This was an unfortunate regression triggered by the changes in #3222 that fixed a race condition. The regression happened because were missing tests that exercised the above scenario. I have included some tests for this as part of the current commit.

Also add a skipped test for related issue #3236.

* update_sdk (#3320)

* fix

* Suppress new warning reported from .NET8 SDK.

* these files are no longer needed

* address comment

* revert change

---------

Co-authored-by: Brett V. Forsgren <brettfo@microsoft.com>
Co-authored-by: Shyam Namboodiripad <gnamboo@microsoft.com>
Co-authored-by: Shyam N <shyamnamboodiripad@users.noreply.github.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant