GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||
GeezerVison is showing github.com — Revert refactoring changes that broke remoting to Windows PowerShell 5.1 by SteveL-MSFT · Pull Request #5321 · PowerShell/PowerShell Conversation
Member
Call backs depend on private members to have the same name across versions of PowerShell. Specifically fixes prompts and clear. Paul Higinbotham (@PaulHigin) are there other callbacks I need to fix? I noticed that ctrl+c doesn't work from PSCore6 to Windows PowerShell 5.1. Fix #4615
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions…ws PowerShell 5.1
Steve Lee (SteveL-MSFT)
requested review from
Bruce Payette (BrucePay),
Dongbo Wang (daxian-dbw) and
Jason Shirk (lzybkr)
as code owners
Jason Shirk (lzybkr)
approved these changes
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sigh - it's silly that the protocol requires the names of the private fields. I suppose it's just an expedient implementation detail - just use reflection, but it's so brittle.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Member
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Paul Higinbotham (PaulHigin)
suggested changes
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the warning messages should say "it will break remoting compatibility with Windows PowerShell".
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is incomplete. To fully fix this incompatibility we need to revert field names for all encoded class/structs. Here is the supported list:
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I reused an existing comment. I can update all occurrences of that comment to be more specific. Thanks for the pointer to the list of types, I'll fix those as well.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Steve Lee (SteveL-MSFT)
requested review from
Dan Travison (dantraMSFT) and
Mike Richmond (mirichmo)
as code owners
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Steve Lee (SteveL-MSFT)
force-pushed
the
remoting-callback
branch
from
930e4ab to
0c14e56
Compare
Member
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
|
|
Travis Plunk (@TravisEz13) can you merge? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…5.1 (PowerShell#5321) - Revert refactoring changes so that it doesn't break remoting to Windows PowerShell 5.1 - Fix the rest of the supported types for remoting - Put remoting sensitive private members in a descriptive region
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Remoting host callbacks incompatible between PowerShell 5.1 and 6.0
There was an error while loading. Please reload this page.