You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PowerShellForGitHub: Update Check Fails with an Invalid XML Response #249
VERBOSE: [0.14.0] Executing: Get-GitHubUser -Current:$true -Verbose:$true
VERBOSE: [PowerShellForGitHub] update check failed for today (invalid XML response). Assuming up-to-date.
VERBOSE: Getting current authenticated user
VERBOSE: Accessing [Get] https://api.github.com/user [Timeout = 0)]
VERBOSE: GET https://api.github.com/user with 0-byte payload
VERBOSE: received 1223-byte response of content type application/json; charset=utf-8
VERBOSE: [0.14.0] Executing: Set-TelemetryEvent -EventName "Get-GitHubUser"
VERBOSE: Sending telemetry event data to https://dc.services.visualstudio.com/v2/track [Timeout = 0)]
VERBOSE: POST https://dc.services.visualstudio.com/v2/track with -1-byte payload
VERBOSE: received 49-byte response of content type application/json; charset=utf-8
Requested Assignment
I'm just reporting this problem, but don't want to fix it.
Operating System
OsName : Microsoft Windows 10 Pro
OsOperatingSystemSKU : 48
OsArchitecture : 64-bit
WindowsVersion : 1903
WindowsBuildLabEx : 18362.1.amd64fre.19h1_release.190318-1202
OsLanguage : en-GB
OsMuiLanguages : {en-GB, en-US}
changed the title [-]PowerShellForGitHub: Update Check Fails with an Invalid XML Resposne[/-][+]PowerShellForGitHub: Update Check Fails with an Invalid XML Response[/+]on Jun 28, 2020
Activity
[-]PowerShellForGitHub: Update Check Fails with an Invalid XML Resposne[/-][+]PowerShellForGitHub: Update Check Fails with an Invalid XML Response[/+]HowardWolosky commentedon Jun 28, 2020
Thanks for the report. This is a regression introduced by #242 unfortunately when I was reducing the lines in the module that exceeded 100 chars.
Specifically:
PowerShellForGitHub/UpdateCheck.ps1
Line 86 in 17f6122
(note the
=Messageinstead of the-Message)Invoke-UpdateCheck fixes
Invoke-UpdateCheck fixes (#252)