Closed alexcg1 closed 3 years ago
Describe Problem
Running python app.py index -n 100 should index 100 documents. It doesn't. Instead it indexes whatever the num_docs variable is in app.py
python app.py index -n 100
num_docs
app.py
I even ran:
python app.py index -n foo
To confirm it's -n isn't connected to anything. No errors thrown, just indexes as normal
-n
Why happening?
I'm guessing app.py isn't specifying the -n flag to do anything. It should (I guess) be tied to num_docs?
Environment
jina 0.3.6 jina-proto 0.0.45 jina-vcs-tag [33m(unset)[0m libzmq 4.3.2 pyzmq 1.19.0 protobuf 3.12.2 proto-backend cpp grpcio 1.30.0 ruamel.yaml 0.16.10 python 3.8.3 platform Linux platform-release 5.6.16-1-MANJARO platform-version #1 SMP PREEMPT Wed Jun 3 14:26:28 UTC 2020 architecture x86_64 processor jina-resources /home/alexcg/.local/share/virtualenvs/test_my_first-1HJJ4O2U/lib/python3.8/site-packages/jina/resources JINA_ARRAY_QUANT [33m(unset)[0m JINA_CONTRIB_MODULE [33m(unset)[0m JINA_CONTRIB_MODULE_IS_LOADING[33m(unset)[0m JINA_CONTROL_PORT [33m(unset)[0m JINA_DEFAULT_HOST [33m(unset)[0m JINA_EXECUTOR_WORKDIR [33m(unset)[0m JINA_FULL_CLI [33m(unset)[0m JINA_IPC_SOCK_TMP [33m(unset)[0m JINA_LOG_FILE [33m(unset)[0m JINA_LOG_LONG [33m(unset)[0m JINA_LOG_NO_COLOR [33m(unset)[0m JINA_LOG_PROFILING [33m(unset)[0m JINA_LOG_SSE [33m(unset)[0m JINA_LOG_VERBOSITY [33m(unset)[0m JINA_POD_NAME [33m(unset)[0m JINA_PROFILING [33m(unset)[0m JINA_SOCKET_HWM [33m(unset)[0m JINA_STACK_CONFIG [33m(unset)[0m JINA_TEST_CONTAINER [33m(unset)[0m JINA_TEST_GPU [33m(unset)[0m JINA_TEST_PRETRAINED [33m(unset)[0m JINA_VCS_VERSION [33m(unset)[0m JINA_VERSION [33m(unset)[0m JINA_WARN_UNNAMED [33m(unset)[0m JINA_BINARY_DELIMITER [33m(unset)[0m JINA_DISABLE_UVLOOP [33m(unset)[0m
This seems to only work on examples that use click library. Cookiecutter'ed code doesn't use it
click
Describe Problem
Running
python app.py index -n 100
should index 100 documents. It doesn't. Instead it indexes whatever thenum_docs
variable is inapp.py
I even ran:
To confirm it's
-n
isn't connected to anything. No errors thrown, just indexes as normalWhy happening?
I'm guessing
app.py
isn't specifying the-n
flag to do anything. It should (I guess) be tied tonum_docs
?Environment
jina 0.3.6 jina-proto 0.0.45 jina-vcs-tag [33m(unset)[0m libzmq 4.3.2 pyzmq 1.19.0 protobuf 3.12.2 proto-backend cpp grpcio 1.30.0 ruamel.yaml 0.16.10 python 3.8.3 platform Linux platform-release 5.6.16-1-MANJARO platform-version #1 SMP PREEMPT Wed Jun 3 14:26:28 UTC 2020 architecture x86_64 processor
jina-resources /home/alexcg/.local/share/virtualenvs/test_my_first-1HJJ4O2U/lib/python3.8/site-packages/jina/resources JINA_ARRAY_QUANT [33m(unset)[0m JINA_CONTRIB_MODULE [33m(unset)[0m JINA_CONTRIB_MODULE_IS_LOADING[33m(unset)[0m JINA_CONTROL_PORT [33m(unset)[0m JINA_DEFAULT_HOST [33m(unset)[0m JINA_EXECUTOR_WORKDIR [33m(unset)[0m JINA_FULL_CLI [33m(unset)[0m JINA_IPC_SOCK_TMP [33m(unset)[0m JINA_LOG_FILE [33m(unset)[0m JINA_LOG_LONG [33m(unset)[0m JINA_LOG_NO_COLOR [33m(unset)[0m JINA_LOG_PROFILING [33m(unset)[0m JINA_LOG_SSE [33m(unset)[0m JINA_LOG_VERBOSITY [33m(unset)[0m JINA_POD_NAME [33m(unset)[0m JINA_PROFILING [33m(unset)[0m JINA_SOCKET_HWM [33m(unset)[0m JINA_STACK_CONFIG [33m(unset)[0m JINA_TEST_CONTAINER [33m(unset)[0m JINA_TEST_GPU [33m(unset)[0m JINA_TEST_PRETRAINED [33m(unset)[0m JINA_VCS_VERSION [33m(unset)[0m JINA_VERSION [33m(unset)[0m JINA_WARN_UNNAMED [33m(unset)[0m JINA_BINARY_DELIMITER [33m(unset)[0m JINA_DISABLE_UVLOOP [33m(unset)[0m