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 }}
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.
Hi Nicholas,
Love the module, have used it quite a few times now.
First time I'm using it against gitlab.com rather than self-hosted instances and now I get below.
Cannot convert value "Х" to type "System.Byte". Error: "Value was either too large or too small | for an unsigned byte."
What's the problem you're trying to solve converting the response to bytes then back to UTF8 that the Invoke-WebRequest can't do already on line L62.
If I read the code correctly you seem to be encoding it on the first initial request but not on subsequent further page requests then just appending to the Results collection on line L72.
Would you be open to a PR to remove that encoding on below line? or have you seen this before?
The text was updated successfully, but these errors were encountered:
ok perhaps false alarm, looking into it further. I've used the powershell container image docker pull mcr.microsoft.com/powershell and it seems to work.
If you've have any ideas do please let me know, would still be good to get your thoughts on the encoding stuff though
Hi Nicholas,
Love the module, have used it quite a few times now.
First time I'm using it against gitlab.com rather than self-hosted instances and now I get below.
Cannot convert value "Х" to type "System.Byte". Error: "Value was either too large or too small | for an unsigned byte."
What's the problem you're trying to solve converting the response to bytes then back to UTF8 that the Invoke-WebRequest can't do already on line L62.
If I read the code correctly you seem to be encoding it on the first initial request but not on subsequent further page requests then just appending to the Results collection on line L72.
Would you be open to a PR to remove that encoding on below line? or have you seen this before?
The text was updated successfully, but these errors were encountered: