Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

?. operator fails on Linux 7.0.3 but works on Windows 7.0.3

See original GitHub issue

With 7.0.3 the ?. operator works on Windows but not Linux.

Steps to reproduce

$test = @{ field = 'value' }
${test}?.field

Expected behavior

value

Actual behavior

ParserError: You must provide a value expression following the '?' operator.

Environment data

Name                           Value
----                           -----
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Linux 4.4.0-18362-Microsoft #836-Microsoft Mon May 05 16:04:00 PST 2020
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Issue Analytics

State:
Created 3 years ago
Comments:5

Top GitHub Comments

2reactions

rkeithhillcommented, Aug 27, 2020

You need to enable this experimental feature in 7.0.3:

Enable-ExperimentalFeature PSNullConditionalOperators

1reaction

MaximoTrinidadcommented, Aug 27, 2020

Just an FYI

This experimental feature seems already included in 7.1.0-Preview.6.

😃

Top Results From Across the Web

7.0.3 on linux woes -- or is it just me? - KiCad.info Forums

I moved the file I was editing in 7.0.3 on linux (that crashed when I went to update pcb) to a win system...

vSphere 7.0 Update 3 Known Issues - Workarounds & Fix ...

This issue is resolved in ESXi 7.0 Update 3c. Enabling vSphere HA might fail or never complete on hosts that were upgraded to...

Troubleshoot app launch failures

Learn about common reasons for app launch failures and possible solutions.

VMware ESXi 7.0 Update 3l Release Notes

This problem can occur when vCenter manages multiple clusters, and the vCenter VM runs on one of the clusters. If you shut down...

6-68796-05 Rev. B StorNext 7.0.3 Release Notes

Fixed Issues and Enhancements Addressed in StorNext 7.0.3. 5. Supported StorNext Upgrade Paths ... Metadata restore failed but the problem went unnoticed.