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
Progress/status is written for each request, in a static location.
Actual behavior
Progress/status appears to shift over by 3 or 4 columns after each request, leading to "drift" to the right.
This, coupled with #1625, causes significant usability issues for scripts that are doing repeated web requests, e.g. to process paginated API responses.
Impact would be lessened if there was a way to disable progress from Invoke-WebRequest but AFAIK that is not possible.
Steps to reproduce
On OSX
1..20 |%{ $null = Invoke-WebRequest 'https://www.google.com'; Start-Sleep -Milliseconds 250 }Expected behavior
Progress/status is written for each request, in a static location.
Actual behavior
Progress/status appears to shift over by 3 or 4 columns after each request, leading to "drift" to the right.
This, coupled with #1625, causes significant usability issues for scripts that are doing repeated web requests, e.g. to process paginated API responses.
Impact would be lessened if there was a way to disable progress from
Invoke-WebRequestbut AFAIK that is not possible.Screencap below:
Environment data