search

Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
https://azure.github.io/apiops
MIT License
321 stars 188 forks source link

Error on Extractor #487

Closed Arslan007 closed 8 months ago

Arslan007 commented 8 months ago

Release version

5.1.1

Question Details

Getting this error on Extractor Stage for 5.1.1

VERBOSE: Requested HTTP/1.1 GET with 0-byte payload VERBOSE: Received HTTP/1.1 response of content type text/html of unknown size Invoke-WebRequest: /home/vsts/work/_temp/5c8b5d2e-8578-4aac-b426-dfa870b89d28.ps1:22 Line 22 Invoke-WebRequest -Uri "$uri" -OutFile "$destinationFilePath" ~~~~~~~~~~~~~

[debug]Exit code 1 received from tool '/usr/bin/pwsh'

[debug]STDIO streams have closed for tool '/usr/bin/pwsh'

[debug]task result: Failed

[error]PowerShell exited with code '1'.

[debug]Processed: ##vso[task.issue type=error;]PowerShell exited with code '1'.

[debug]Processed: ##vso[task.complete result=Failed;]PowerShell exited with code '1'.

[debug]task result: Failed

[error]PowerShell wrote one or more lines to the standard error stream.

[debug]Processed: ##vso[task.issue type=error;]PowerShell wrote one or more lines to the standard error stream.

[debug]Processed: ##vso[task.complete result=Failed;]PowerShell wrote one or more lines to the standard error stream.

[error]Invoke-WebRequest: /home/vsts/work/_temp/5c8b5d2e-8578-4aac-b426-dfa870b89d28.ps1:22

[debug]Processed: ##vso[task.issue type=error;]Invoke-WebRequest: /home/vsts/work/_temp/5c8b5d2e-8578-4aac-b426-dfa870b89d28.ps1:22

[error]Line |

22 Invoke-WebRequest -Uri "$uri" -OutFile "$destinationFilePath" ~~~~~~~~~~~~~

[debug]Processed: ##vso[task.issue type=error;]Line |

22 Invoke-WebRequest -Uri "$uri" -OutFile "$destinationFilePath" ~~~~~~~~~~~~~

Finishing: Fetch extractor

Expected behavior

Should work

Actual behavior

Throwing error on Extractor Stage

Reproduction Steps

Run with 5.1.1

github-actions[bot] commented 8 months ago 
  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.