Skip to content
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

[BUG]There is a delay for extractor tool #450

Closed
mmmbai opened this issue Dec 19, 2023 · 5 comments
Closed

[BUG]There is a delay for extractor tool #450

mmmbai opened this issue Dec 19, 2023 · 5 comments
Labels
question Further information is requested

Comments

@mmmbai
Copy link

mmmbai commented Dec 19, 2023

Release version

5.0.1

Describe the bug

After I create one API in APIM, then I try to use extractor.exe to extract that API. But the tool just ignore that API. there is no error in output but the out folder didn't contains that API. After sometime when I try extract it using same procedure it works fine.
Does anyone know this issue?

Expected behavior

No delay for extractor

Actual behavior

There is delay for extractor

Reproduction Steps

  1. create one API in APIM
  2. try to extract that API immediately
Copy link

  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
Copy link
Contributor

No one ever reported this issue before. Are you running the extractor binary in your own machine or are you using the DevOps pipelines?

@waelkdouh waelkdouh added the question Further information is requested label Dec 19, 2023
@mmmbai
Copy link
Author

mmmbai commented Dec 19, 2023

I am running the extractor binary in from my local machine

@waelkdouh
Copy link
Contributor

Can you try running the extractor using a a DevOps pipeline and tell us if you are facing the same issue?

@mmmbai
Copy link
Author

mmmbai commented Dec 19, 2023

This is something wrong in my side. sorry for that and I will close this issue

@mmmbai mmmbai closed this as completed Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants