-
Notifications
You must be signed in to change notification settings - Fork 1
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
Stopped working after migrating Octopus Deploy to Linux #6
Comments
After reading this I ran |
Hey Andrew - I'm happy to hear that anyone is even using this utility! I hope it is helping you; having access to the internal data was incredibly helpful for me when I was working with Octopus Deploy. I haven't touched that code in a LONG time. That setting change you made was for how many parallel tasks would run to download the data. The parallelism is implemented with a 3rd party component; it's hard to believe that that could be causing the problem but it could be. If necessary, that code could be converted to use ForEach-Object -Parallel, as long as running in PS 7+ is OK for you. Another possibility: that code is running in it's own runspace so maybe there's some auth setting in the main script process that is now getting lost when running the parallel jobs... if you can pass that setting (google that error) to the sub jobs that could fix it, too. Or just live with it being slower. Hope all this helps! And, again, I'm just excited anyone used that at all! |
@DTW-DanWard Thank you for your work, Dan, I have been using this and praising you silently for many years, this is the first time I'm having an issue. It's nothing short of a miracle that Octopus did not break the API in that many years, and it just keeps working. The stack overflow link I pasted above leads me to believe that it could be the http client fault. |
oduexport gives:
The text was updated successfully, but these errors were encountered: