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

setup-*.bat broken #378

Closed
holgerpieta opened this issue May 23, 2023 · 4 comments
Closed

setup-*.bat broken #378

holgerpieta opened this issue May 23, 2023 · 4 comments
Assignees
Labels
scope/api status/fixed issues that have been fixed and released type/bug broken features
Milestone

Comments

@holgerpieta
Copy link

The setup-*.bat files in api/ just call onnx_env\Scripts\activate.bat in line 2, which will terminate the script after calling the activate script.
Instead they must call the activate script, e.g. like this call onnx_env\Scripts\activate.bat to continue and perform the following commands.

Also the setup guide for Windows is somewhat incomplete, as it does not mention that the setup-*.bat files can be found in api/.

@holgerpieta
Copy link
Author

Uhm, it generally seems like the Windows Python installer is broken and/or incomplete.
The launch.bat is lacking the call to activate.bat , so it doesn't work at all.
After fixing that, it starts and the server is reachable, but when accessing 127.0.0.1:5000 in the browser I just get a 404, so something isn't working, but I don't know what.

@ssube ssube self-assigned this May 27, 2023
@ssube ssube added status/new issues that have not been confirmed yet type/bug broken features labels May 27, 2023
@ssube
Copy link
Owner

ssube commented May 27, 2023

When you say Windows Python installer, which method is that? Using a pre-installed Python on Windows, or the Windows bundle, or something else?

I will fix the calls in the launch scripts, and have some work to do on the docs before the next release (#368, #328), so I will make sure to mention the setup files.

If you are running the API server from a clone of the repo, you may need to build or download the GUI files as well. You can grab a copy from the gh-pages branch: https://github.com/ssube/onnx-web/tree/gh-pages/v0.10.0

The Windows bundle comes with the GUI files, but if you cloned the repo, they will be missing. Download (or build and copy) them into https://github.com/ssube/onnx-web/tree/main/api/gui, and that should work.

@ssube ssube added status/progress issues that are in progress and have a branch scope/api and removed status/new issues that have not been confirmed yet labels May 29, 2023
@ssube ssube modified the milestones: v0.10, v0.11 Dec 3, 2023
@ssube
Copy link
Owner

ssube commented Dec 10, 2023

There were at least two parts to this, and I believe both are now fixed:

I was hoping to add the GUI download to the launch script, but it looks like that might only work reliably within powershell (https://stackoverflow.com/questions/4619088/windows-batch-file-file-download-from-a-url), so that's covered in the setup documentation for now.

@ssube ssube added status/fixed issues that have been fixed and released and removed status/progress issues that are in progress and have a branch labels Dec 10, 2023
@ssube
Copy link
Owner

ssube commented Dec 15, 2023

The launch.bat script now has a check for the web UI files and the launch.ps1 script will check for and download them if they are not found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/api status/fixed issues that have been fixed and released type/bug broken features
Projects
None yet
Development

No branches or pull requests

2 participants