-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add Windows Support #191
Comments
Hi Team. Please look into adding Windows x64/arm64 Chromium Binary for this reports plugin. As we are starting the process of Windows support. Thanks. |
In the queue... We need to research windows arm. |
@setiah or @peterzhuamazon is it confirmed that we will be supporting windows arm64? if so, windows server never released arm64 version (ref), will this be targeting windows 10/11 arm64? additionally we might be able to run the full chromium in headless mode, but it increases reporting artifact size about 200mb, would it be acceptable or is there a hard limit on artifact size? |
Adding @bbarani in the conversation of this. |
This is relatively new https://www.zdnet.com/article/microsoft-brings-arm-support-to-azure-virtual-machines/ Q4: What CPU architecture do you support in the Windows distribution? |
Hi @anirudha @joshuali925 what is the progress on chromium support on this? cc: @setiah |
researching this further, we will post an update soon on this |
Blocked on windows chromium binary incompatibility with pupeteer. Doing some investigation to see whether newer version of chromium will fix this issue. If so then we may need to create a new windows headless chromium binary CC @rupal-bq @joshuali925 |
Tried building locally on windows but build failed with following error.
Blocked on dashboards support |
Switching to git bash fixed this error |
Was able to download report on windows with dev server download_dashboards_report_windows.mov |
@rupal-bq and I were able to get this to work with a newer version of chromium. CI is also passing on PR. Will connect with @joshuali925 about generating a newer version of headless chromium binary for windows. |
Merged the PR |
@joshuali925 @rupal-bq can one of you folks close this issue? I don't have access.... |
closed by #504 |
Reopen as the code is only in main. Thanks. |
backported |
Not able to build on windows:
Despite the dir is in the |
@peterzhuamazon not able to reproduce, need more information here is a successful build: https://github.com/opensearch-project/dashboards-reports/actions/runs/3292567970/jobs/5428079881 |
closing this as per the comment |
@anirudha Can we please keep this issue open until you hear back from @peterzhuamazon |
Verifying the issue right now will post my findings soon. Thanks. |
I have confirmed that the folder is the correct folder in the correct location, yet it is still not able to build reports dash.
|
Seems like it is caused by this exception in core dashboards: |
could you give steps to reproduce?
|
I am going to close this issue, unless we need to do more work in reporting plugin |
Re-open the issue as we are able to reproduce this specifically on jenkins windows agent. Thanks. |
The issue seems related to dashboards core code returning two different paths literally, but for windows they are the same path:
In Windows |
Add a new issue in core about this. |
I don't believe integration tests are running, and integration tests are very much part of CI. Reopening. Please close when this and any other gaps between Linux/Windows CI/CD are covered. |
Hi, just want to make sure this issue is closed, if all the tasks are completed. Thanks. |
Added integration tests in CI #624. Closing this issue. |
Coming from opensearch-project/opensearch-plugins#95, add Windows support.
The text was updated successfully, but these errors were encountered: