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

ApiLogicServer 4.1.0 error on windows 10 #32

Closed
sylvoslee opened this issue Jan 18, 2022 · 5 comments
Closed

ApiLogicServer 4.1.0 error on windows 10 #32

sylvoslee opened this issue Jan 18, 2022 · 5 comments

Comments

@sylvoslee
Copy link

When i run ApiLogicServer 4.10 on windows 10,get the follow error.


  File "c:\users\miniconda3\envs\debug\lib\site-packages\api_logic_server_cli\cli.py", line 1244, in run_api
    create_utils.run_command(f'python {run_file}', msg="Run created ApiLogicServer project", new_line=True)
  File "c:\users\miniconda3\envs\debug\lib\site-packages\api_logic_server_cli\create_from_model\api_logic_server_utils.py", line 77, in run_command
    result_b = subprocess.check_output(cmd, shell=True, env=use_env)  # , stderr=subprocess.STDOUT)  loses all logging
  File "c:\users\miniconda3\envs\debug\lib\subprocess.py", line 415, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "c:\users\miniconda3\envs\debug\lib\subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'python E:\project\ApiLogicProject/api_logic_server_run.py localhost 5656' returned non-zero exit status 1.
@thomaxxl
Copy link
Collaborator

What is the output when you execute

python .\api_logic_server_run.py

in E:\project\ApiLogicProject ?
(note: you have to run this in a virtualenv with the appropriate modules installed)

@valhuber
Copy link
Owner

valhuber commented Jan 18, 2022 via email

@valhuber
Copy link
Owner

I can recreate this bug.  Sorry.  Investigating now

@valhuber
Copy link
Owner

valhuber commented Jan 18, 2022

This is a bug (sorry) in some advance work.  We have determined the problem, and are evaluating the most optimal fix.  Definitely today: 4.01.01

@valhuber
Copy link
Owner

Fixed in 4.01.01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants