Skip to content

Commit ffb0d70

Browse files
author
joeyaiello
committed
add June community call
1 parent b151b4a commit ffb0d70

File tree

2 files changed

+197
-1
lines changed

2 files changed

+197
-1
lines changed
Lines changed: 195 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,195 @@
1+
Joey Aiello 9:31 AM:
2+
Hey everyone!
3+
Joey Aiello 9:31 AM:
4+
Just getting set up, give us a second
5+
Sullivan, Trevor 9:31 AM:
6+
Hello
7+
Joey Aiello 9:32 AM:
8+
Hello!
9+
Sullivan, Trevor 9:32 AM:
10+
Yes
11+
Glenn Sarti 9:32 AM:
12+
yup
13+
Darwin Sanoy 9:32 AM:
14+
yes
15+
Iain Brighton 9:32 AM:
16+
Yep!
17+
Keith Hill 9:32 AM:
18+
yes
19+
Constantin Hager 9:32 AM:
20+
jes
21+
Thomas Rayner 9:32 AM:
22+
affirmative
23+
Constantin Hager 9:32 AM:
24+
yes
25+
Monty Evans 9:32 AM:
26+
yep
27+
Hector, Michael 9:32 AM:
28+
(y)
29+
Eugene Bekker 9:37 AM:
30+
Does the Job run with the environment captured of the launching environment?
31+
Keith Hill 9:40 AM:
32+
Crytographically strong randomness one might say. :-)
33+
Steve Lee (POWERSHELL) 9:41 AM:
34+
lol
35+
Glenn Sarti 9:41 AM:
36+
+1 UTF8NOBOM
37+
Thomas Rayner 9:42 AM:
38+
That's awesome
39+
Keith Hill 9:44 AM:
40+
+1 for uniform experience cross-plat.
41+
Darwin Sanoy 9:44 AM:
42+
This just effects PowerShell Core?
43+
Keith Hill 9:45 AM:
44+
Unicode in-mem and UTF8 on file just makes sense.
45+
Sullivan, Trevor 9:45 AM:
46+
Oh, so *that's* why VSCode kept saying that my module manifests were binaries. Interesting.
47+
Keith Hill 9:45 AM:
48+
Yup
49+
Jonathan Medd 9:45 AM:
50+
Yay for fixing that problem with New-ModuleManifest and git. I wondered why that happened :-)
51+
Keith Hill 9:45 AM:
52+
Which BTW is why Plaster generates a module manifest as UTF8NoBOM.
53+
Nicholas M. Getchell 9:45 AM:
54+
Thanks Keith!
55+
Keith Hill 9:47 AM:
56+
Hate to admit this but I didn't even know powershell.exe took positional params. I always specify -Command or -File
57+
Sullivan, Trevor 9:47 AM:
58+
I always specify parameter names for the powershell binary, too.
59+
Eugene Bekker 9:48 AM:
60+
Is it time to consider a distinct name for the PS Core binary vs Windows PS?
61+
Eugene Bekker 9:48 AM:
62+
For example, leave WInPS as powershell.exe and something else, like ps1.exe or posh.exe
63+
Sullivan, Trevor 9:48 AM:
64+
PowerShell Desktop Edition vs. PowerShell Core Edition @Eugene
65+
Eugene Bekker 9:48 AM:
66+
for PS6+
67+
Glenn Sarti 9:49 AM:
68+
I assume it'll throw an appropriate error (file not found) to the console if you do pass in a command instead of a file... Nothing too obtuse
69+
Keith Hill 9:49 AM:
70+
RE & operator - so the job is a traditional out-of-proc job instead on an in-process (separate runspace) job?
71+
Eugene Bekker 9:50 AM:
72+
Thanks @Trevor
73+
Eugene Bekker 9:50 AM:
74+
Two different names means we can have both live side-by-side on Windows with no conflicts or ambiguity
75+
Sullivan, Trevor 9:51 AM:
76+
There are bigger fish to fry than changing the PowerShell binary name. Just leave it for now.
77+
Keith Hill 9:51 AM:
78+
You could do that with a version parameter, no?
79+
Eugene Bekker 9:51 AM:
80+
If PS6 is changing the CLI params (which is great!), but it will mean invoking PS.exe will require some magic by the caller
81+
Eugene Bekker 9:52 AM:
82+
Also, maybe with PS Core have the ability to specify which "Engine Version" is loaded, much like dotnet CLI allows multiple SDKs living side by side
83+
Keith Hill 9:52 AM:
84+
Heh maybe powershell needs a version manager. :-) psvm select 6.1
85+
Eugene Bekker 9:52 AM:
86+
:-)
87+
Sullivan, Trevor 9:52 AM:
88+
+1 Keith
89+
Glenn Sarti 9:52 AM:
90+
Thanks. Sometimes PS errors can be a bit verbose but that looks good.
91+
Bergmeister, Christoph (Reigate) 9:53 AM:
92+
+1 Keith because this would be great for testing
93+
Sullivan, Trevor 9:54 AM:
94+
Are these discussions / feedback being discussed openly, or just internally to Microsoft? If you could point us to public discussions on pros/cons of issues like PS version manager and the binary renaming issue, that would be useful.
95+
Andrew Bradley 9:54 AM:
96+
Will there be a simple, recommended way to invoke PSCore cross-platform? E.g. if a build script in an open-source project must have predictable UTF8 output on Linux and Windows
97+
Thomas Rayner 9:54 AM:
98+
(N) changing the name of the binary name
99+
(Y) adding a minver/maxver/requirever param or launching
100+
Thomas Rayner 9:55 AM:
101+
imo
102+
Eugene Bekker 9:55 AM:
103+
But Desktop and Core are different enough that when I simply say "powershell.exe" I would like to have some predictability
104+
Keith Hill 9:55 AM:
105+
Speaking of breaking changes, I'd like to add the Unicode esc seq PR to the agenda (towards the end) if possible since it is a low risk breaking change. Would be nice to get into 6.0.
106+
Eugene Bekker 9:55 AM:
107+
Especially if you're changing the CLI params
108+
Sullivan, Trevor 9:56 AM:
109+
A *huge* issue to me is the lack of semantic versioning for dependencies in PowerShell module manifests. I'd love to see this breaking change in PS v6.0.
110+
Eugene Bekker 9:56 AM:
111+
I agree -- it's not a "burning" issue
112+
Sullivan, Trevor 9:57 AM:
113+
I hear you @Eugene. Nice to have, but pretty low in priority list.
114+
Thomas Rayner 9:59 AM:
115+
Gotta run to another meeting. Thanks for the call and info!
116+
Joey Aiello 9:59 AM:
117+
See ya! Thanks for joining!
118+
Iain Brighton 10:01 AM:
119+
Gotta shoot - thanks!
120+
Sullivan, Trevor 10:04 AM:
121+
I had reported an issue with AssemblyLoadContext a couple calls ago ... does this fix that issue? I was getting a silent failure when loading a .NET Core assembly using the default load context.
122+
Sullivan, Trevor 10:05 AM:
123+
I haven't tried on .NET Standard 2.0. Maybe I should give that a shot.
124+
Sullivan, Trevor 10:06 AM:
125+
Wow, really? That is awesome. Single assembly for PS 3.0 Desktop *and* Core 6.0?
126+
Eugene Bekker 10:06 AM:
127+
Awesome! +1 PSStd
128+
David Jones 10:09 AM:
129+
why not use install-package ?
130+
Sullivan, Trevor 10:09 AM:
131+
Any news to share about including PowerShell Remoting "out of box" with the PowerShell Core install package?
132+
Keith Hill 10:13 AM:
133+
Here the two Unicode esc forms as implemented: fixed width "`u00A9Acme Inc" (ala C# and Bash) and variable width "`u{1f44d}" (ala JavaScript) that also supports Unicode surrogate pairs (emoji).
134+
Sullivan, Trevor 10:14 AM:
135+
I already have an "Emojis" PowerShell module. :)
136+
Sullivan, Trevor 10:14 AM:
137+
It's on the PowerShell Gallery.
138+
Keith Hill 10:16 AM:
139+
BTW big +1 to whoever fixed the PSReadline bug that was causing garbage characters to be displayed in the prompt on Linux.
140+
Bergmeister, Christoph (Reigate) 10:16 AM:
141+
I find it great that you want to make PowerShell rather quality rather than date driven but can we have an update for each Beta version how many more Beta versions are roughly expected until RTM?
142+
Jonathan Medd 10:16 AM:
143+
Can you join it now? I thought it was only recorded with the MS Azure guys?
144+
Sullivan, Trevor 10:16 AM:
145+
+1 Keith to PSReadline fix. Does that fix the issue with VSCode Integrated Terminal?
146+
Sullivan, Trevor 10:17 AM:
147+
I used to get all sorts of weird characters printed in the Integrated Terminal, and it was rather unpredictable / hard to reproduce.
148+
Keith Hill 10:18 AM:
149+
THere is a caveat to that fix. The last line which PSReadline modifies (changes color to indicate error) must not contain any vt term esc seqs.
150+
Nicholas M. Getchell 10:18 AM:
151+
I saw that as well Trevor. I couldn't tell if it was PSReadline, vscode-powershell ext, integrated terminal, or my prompt. It was so random.
152+
Sullivan, Trevor 10:18 AM:
153+
+1 for quality-driven release. Thanks for your efforts in this area. :)
154+
Sullivan, Trevor 10:19 AM:
155+
@Nicholas yeah, I'm not sure where the source of the issue was. Figured Keith would know.
156+
Bergmeister, Christoph (Reigate) 10:19 AM:
157+
Thanks for the info. :-)
158+
Sullivan, Trevor 10:19 AM:
159+
I'm using VSCode on Mac.
160+
Sullivan, Trevor 10:20 AM:
161+
It might have been PSReadLine related.
162+
Eugene Bekker 10:20 AM:
163+
The link hasn't been posted yet
164+
Eugene Bekker 10:20 AM:
165+
According to Roney's twitter
166+
Sullivan, Trevor 10:20 AM:
167+
Have a great day folks, cheers!
168+
Bergmeister, Christoph (Reigate) 10:21 AM:
169+
I found some minor remoting bugs for older pre-release version of PowerShell and OpenSSH. They are not blocking for me but are you still interest in getting to know about them?
170+
Keith Hill 10:21 AM:
171+
@trevor - https://github.com/lzybkr/PSReadLine/issues/470
172+
Keith Hill 10:21 AM:
173+
Chrome is slow!!
174+
Glenn Sarti 10:22 AM:
175+
Thanks all!
176+
Darwin Sanoy 10:22 AM:
177+
Memory hog cause it follows UAC process level best practice - like IE ;)
178+
Keith Hill 10:22 AM:
179+
Thanks!
180+
Darwin Sanoy 10:22 AM:
181+
THanks!
182+
Eugene Bekker 10:22 AM:
183+
Thanks!
184+
Kenny, Richard 10:22 AM:
185+
Thanks
186+
Hector, Michael 10:23 AM:
187+
TY
188+
Jonathan Medd 10:23 AM:
189+
Thanks
190+
Bergmeister, Christoph (Reigate) 10:23 AM:
191+
Thanks
192+
Wiedmeyer, Martin - NTT 10:23 AM:
193+
demke
194+
Joey Aiello 10:24 AM:
195+
bitte

CommunityCall/README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,5 @@ Use [this ICS file](RecurringCommunityCall.ics) (right-click `Raw` and select `S
99
* [Jan 26, 2017](./20170126_ChatTranscript.txt) ([YouTube recording (partial)](https://www.youtube.com/watch?v=j7g5UbVFYqQ))
1010
* Mar 16, 2017 ([YouTube recording](https://www.youtube.com/watch?v=tkBiVxd7l2I))
1111
* Apr 20, 2017 ([YouTube recording](https://www.youtube.com/watch?v=7NFct1AxFOU))
12-
* [May 18, 2017](./20170518_ChatTranscript.txt) ([YouTube recording](https://www.youtube.com/watch?v=f8WXuFrVSKM)
12+
* [May 18, 2017](./20170518_ChatTranscript.txt) ([YouTube recording](https://www.youtube.com/watch?v=f8WXuFrVSKM))
13+
* [June 15, 2017](./20170615_ChatTranscript.txt) ([YouTube recording](https://www.youtube.com/watch?v=Iu_Q_3cUxTQ))

0 commit comments

Comments
 (0)