Run Extractor with config - Error

[abymsft]

Release version

v5.1.4

Describe the bug

The extractor runs fine when I use "Extract All APIs" option.

But, I intend to extract one API using "configuration.extractor.yaml".

The config file is in place

The release version changes are in place

Expected behavior

The extractor should extract the desired API

Actual behavior

Actions Error

Raw Error Logs
2024-04-07T20:15:30.5928771Z �[31;1m�[0m�[36;1m�[36;1m�[0m�[36;1m�[0m�[36;1m | �[31;1m ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~�[0m 2024-04-07T20:15:30.5929918Z �[31;1m�[0m�[36;1m�[36;1m�[0m�[36;1m�[0m�[36;1m�[31;1m�[31;1m�[36;1m | �[31;1m �[0m 2024-04-07T20:15:30.5970640Z �[31;1m�[0m�[36;1m�[36;1m�[0m�[36;1m�[0m�[36;1m�[31;1m�[31;1m�[36;1m�[31;1m�[36;1m | �[31;1m{"locale":"en","featureFlags":["code_vulnerability_scanning","copilot_conversational_ux_history_refs","copilot_smell_icebreaker_ux","copilot_implicit_context","failbot_handle_non_errors","geojson_azure_maps","image_metric_tracking","marketing_forms_api_integration_contact_request","marketing_pages_search_explore_provider","turbo_experiment_risky","sample_network_conn_type","no_character_key_shortcuts_in_inputs","react_start_transition_for_navigations","custom_inp","remove_child_patch"]} Page not found · GitHub · GitHub Skip to content {"props":{}} Toggle navigation Sign in Product Actions Automate any workflow Packages Host and manage packages Security Find and fix vulnerabilities Codespaces Instant dev environments Copilot Write better code with AI Code review Manage code changes Issues Plan and track work Discussions Collaborate outside of code Explore All features Documentation GitHub Skills Blog Solutions For Enterprise Teams Startups Education By Solution CI/CD & Automation DevOps DevSecOps Resources Learning Pathways White papers, Ebooks, Webinars Customer Stories Partners Open Source GitHub Sponsors Fund open source developers The ReadME Project GitHub community articles Repositories Topics Trending Collections Pricing "> Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation. Cancel Create saved search Sign in Sign in to GitHub --> Username or email address Password Forgot password? or sign in with a passkey Sign up 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 }} --> Find code, projects, and people on GitHub: Search Contact Support — GitHub Status — @githubstatus Subscribe to our developer newsletter Get tips, technical guides, and best practices. Twice a month. Right in your inbox. Subscribe Product Features Enterprise Copilot Security Pricing Team Resources Roadmap Compare GitHub Platform Developer API Partners Electron GitHub Desktop Support Docs Community Forum Professional Services Premium Support Skills Status Contact GitHub Company About Customer stories Blog The ReadME Project Careers Press Inclusion Social Impact Shop GitHub on X GitHub on Facebook GitHub on LinkedIn GitHub on YouTube GitHub on Twitch GitHub on TikTok GitHub’s organization on GitHub © 2024 GitHub, Inc. Terms Privacy (Updated 08/2022) Sitemap What is Git? Manage cookies Do not share my personal information You can’t perform that action at this time.�[0m 2024-04-07T20:15:30.7150950Z ##[error]Process completed with exit code 1. 2024-04-07T20:15:30.7257465Z Post job cleanup.

Reproduction Steps

• Here is the public project - Link to actions https://github.com/abymsft/apiops/actions
• Run the "Extractor" with configuration.extractor.yaml
• Link to repo: https://github.com/abymsft/apiops

[github-actions]

  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.

[waelkdouh]

This seems to be an issue with your environment. Also the logs you posted are not related to apiops.

[abymsft]

Something seems to be the problem with the exe being used to invoke the request. I reused the code from "without config file section" and it worked fine 🤔
I can't dive into this right now. Have a customer demo tomorrow :P
Sharing the "run with config section" from runextractor.yaml below.

run: |
Set-StrictMode -Version Latest
$ErrorActionPreference = "Stop"
$VerbosePreference = "Continue"
$InformationPreference = "Continue"
Write-Information "Downloading extractor..."
$extractorFileName = "extractor.linux-x64"
$extractorFinalFileName = "extractor"
if ("${{ runner.os }}" -like "win") {
$extractorFileName = "extractor.win-x64.exe"
$extractorFinalFileName = "extractor.exe"
}
elseif ("${{ runner.os }}" -like "mac" -and "${{ runner.arch }}" -like "arm") {
$extractorFileName = "extractor.osx-arm64"
}
elseif ("${{ runner.os }}" -like "mac" -and "${{ runner.arch }}" -like "x86_64") {
$extractorFileName = "extractor.osx-x64"
}
$uri = "https://github.com/Azure/apiops/releases/download/${{ env.apiops_release_version }}/$extractorFileName"
$destinationFilePath = Join-Path "${{ runner.temp }}" $extractorFinalFileName

Here's the result - PR created with the desired artifacts in place.

[DibyaRanjan1]

This seems to be an issue with your environment. Also the logs you posted are not related to apiops.

I am facing the same issue recently.

[waelkdouh]

@abymsft did your issue ever get resolved?