Initial PowerShelll kernel prototype#9
Conversation
|
Ok I believe I've addressed all feedback from the original PR and cleaned up some copy-paste relics. |
| # Generated by: tyleonha | ||
| # | ||
| # Generated on: 1/23/2020 | ||
| # |
There was a problem hiding this comment.
Replace this comment section with the following?
//
// Copyright (c) Microsoft. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
//
There was a problem hiding this comment.
The copyright and license we're using elsewhere is:
// Copyright (c) .NET Foundation and contributors. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
There was a problem hiding this comment.
updated 👍 Not sure what you want the AuthorName and CompanyName to be in the psd1 so I left it at Microsoft for now. Let me know if you prefer something else.
There was a problem hiding this comment.
Should probably be .NET Foundation instead of Microsoft
|
Not really sure what to do about the CI failure:
|
|
@TylerLeonhardt For the |
...oft.DotNet.Interactive.PowerShell.Tests/Microsoft.DotNet.Interactive.PowerShell.Tests.csproj
Show resolved
Hide resolved
Microsoft.DotNet.Interactive.PowerShell/Microsoft.DotNet.Interactive.PowerShell.csproj
Show resolved
Hide resolved
ac96a71 to
3c05dbc
Compare
Microsoft.DotNet.Interactive.PowerShell/Commands/TracePipelineObjectCommand.cs
Outdated
Show resolved
Hide resolved
a1c0b3e to
fdf28a3
Compare
|
Can someone help me understand the CI failure? |
|
@brettfo Does this build failure ring any bells? |
colombod
left a comment
There was a problem hiding this comment.
I am concerned with the lack of tests.
|
@jonsequitur The build failure is due to dotnet/symstore#81. I've sent email internally to figure out what the workaround is and how to apply it here. I'll reply once I have something actionable. |
TylerLeonhardt
left a comment
There was a problem hiding this comment.
I've added powershell to a few tests and added a test to test all the different streams and their order.
Any other tests you'd like?
8c13d8d to
2a08ea9
Compare
| e => e.Should().BeOfType<CommandHandled>()); | ||
| } | ||
|
|
||
| [Fact(Timeout = 45000)] |
There was a problem hiding this comment.
You don't need to add the timeouts.
There was a problem hiding this comment.
All the other tests in this file have timeouts for similar tests. Should remove those as well?
There was a problem hiding this comment.
If you want to, feel free. If not, we'll do it. These were an artifact of an investigation into timeout and memory issues that were plaguing us but have been resolved.
There was a problem hiding this comment.
I removed them just from my added tests.
|
@TylerLeonhardt Can you try merging/cherry-picking/manually-applying the head commit in the |
|
@brettfo doesn't look like that did the trick :( |
|
I just added a commit that manually strips the offending files from the symbols packages. Build worked locally, now we'll see what happens in the PR. |
|
The recent MSBuild hackery gets us past the symbol uploading and the Linux leg now passes. I'll pass this back to @TylerLeonhardt now to look into the test failure(s) in Windows and add any extra features/tests you may want. |
248f653 to
1cb3994
Compare
|
🎉🎉🎉🎉 |
|
@TylerLeonhardt The full-signed build with the PowerShell kernel failed due to signing issues (link here). Do you know who owns the publishing of the I tried using the My guess is that this package (and it's Unix and Windows sub-packages) will have to be re-published with consistent signing/keys. |
|
@adityapatwardhan @TravisEz13 @SteveL-MSFT can one of you guys offer some advice here? I'm not familiar with this package. |
|
@brettfo The Windows and non-Windows packages are separate packages from separate sources and policy says we should sign them with different Authenticode signatures. What kind of signing are we talking about here? Authenticode or strong name? |
|
After speaking with some people, I found a way to exclude just that one file from the signing checks due to the different signatures. See PR #110. |

Original PR: dotnet/try#751 (all feedback addressed)
This handles the 3 basic messages:
This change also includes tests 🙂
Example PowerShell notebook that came from this very change.
cc @SteveL-MSFT @daxian-dbw