Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pipe-From-Variable PowerShell Progress Broken in PowerShell 7 #136

Closed
JustinGrote opened this issue Mar 11, 2020 · 3 comments
Closed

Pipe-From-Variable PowerShell Progress Broken in PowerShell 7 #136

JustinGrote opened this issue Mar 11, 2020 · 3 comments
Labels
bug Issues that have been confirmed to be bugs in PrtgAPI and will be fixed in a future version

Comments

@JustinGrote
Copy link

JustinGrote commented Mar 11, 2020

Describe the bug
Clearly and concisely describe what you were trying to do, what happened and what you were expecting to happen

Trying to pipe commands consistently produces Set-ChannelProperty: Don't know how to extract the pipeline input from a 'System.SZArrayEnumerator' enumerator from type ''.

Specifying the items directly usually works fine.

image

Steps to reproduce
Put the relevant code from your application that caused the issue to happen in the code block below

$pingtimechannels | set-channelproperty -LimitsEnabled $true -WarningLimitMessage "Excessive Latency detected for this device. Verify sufficient bandwidth and connectivity to the site." -UpperWarningLimit 300

What is the output of Get-PrtgClient -Diagnostic?

# Output goes here!
PSVersion      : 7.0.0
PSEdition      : Core
OS             : Microsoft Windows 10.0.19041
PrtgAPIVersion : 0.9.11
Culture        : en-US
CLRVersion     : .NETCoreApp,Version=v3.1
PrtgVersion    : 20.1.56.1547
PrtgLanguage   : english.lng

Additional context
Anything else I should know to help solve the issue?
Probably just a type difference or .NET Core 3.1 regression.

@JustinGrote JustinGrote added the alleged-bug Bugs raised by people helpfully using the Bug Report template! label Mar 11, 2020
@lordmilko
Copy link
Owner

Hi @JustinGrote,

I was unable to reproduce this issue; are you able to provide the full code for how you initialized the $pingtimechannels variable?

@lordmilko lordmilko added bug Issues that have been confirmed to be bugs in PrtgAPI and will be fixed in a future version and removed alleged-bug Bugs raised by people helpfully using the Bug Report template! labels Mar 12, 2020
lordmilko added a commit that referenced this issue Mar 12, 2020
…g an Array/SZArrayEnumerator in .NET Core 3.1 (#136)
@lordmilko
Copy link
Owner

Hi @JustinGrote,

I've managed to replicate this and have released a pre-release build of PrtgAPI 0.9.13 that includes a fix for this issue. Can you please follow the manual installation instructions and advise whether this build resolves the issue?

@JustinGrote
Copy link
Author

Worked for me, thanks!

lordmilko added a commit that referenced this issue Mar 21, 2020
…g an Array/SZArrayEnumerator in .NET Core 3.1 (#136)
lordmilko added a commit that referenced this issue Mar 21, 2020
…g an Array/SZArrayEnumerator in .NET Core 3.1 (#136)
@lordmilko lordmilko changed the title PS7: Pipeline Issues Pipe From Variable PowerShell Progress Broken in PowerShell 7 Apr 3, 2020
@lordmilko lordmilko changed the title Pipe From Variable PowerShell Progress Broken in PowerShell 7 Pipe-From-Variable PowerShell Progress Broken in PowerShell 7 Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that have been confirmed to be bugs in PrtgAPI and will be fixed in a future version
Projects
None yet
Development

No branches or pull requests

2 participants