CMake error when doing idf.py set-target esp32 (IDFGH-6384)

I downloaded the  Master IDF from github and installed in Ubuntu.
And then downloaded ESP32 AT project from github.
When I tried to run "idf.py set-target esp32"   ... I get the following error...
Vostro-3581:~/esp/esp-at$ idf.py set-target esp32
Adding "set-target"'s dependency "fullclean" to list of commands with default set of options.
Executing action: fullclean
Build directory '/home/philo/esp/esp-at/build' not found. Nothing to clean.
Executing action: set-target
Set Target to: esp32, new sdkconfig created. Existing sdkconfig renamed to sdkconfig.old.
Running cmake in directory /home/philo/esp/esp-at/build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DIDF_TARGET=esp32 -DCCACHE_ENABLE=0 /home/philo/esp/esp-at"...
CMake Error at CMakeLists.txt:9 (string):
string no output variable specified
CMake Error at CMakeLists.txt:13 (string):
string begin index: 9 is out of range 0 - 0
CMake Error at CMakeLists.txt:14 (string):
string sub-command STRIP requires two arguments.
CMake Error at CMakeLists.txt:15 (string):
string no output variable specified
silence:0 sdkconfig:/home/philo/esp/esp-at/module_config/module__default/sdkconfig.defaults
CMake Error at CMakeLists.txt:53 (include):
include could not find load file:
/home/philo/esp/esp-at/esp-idf/tools/cmake/project.cmake

-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:80 (add_dependencies):
Cannot add target-level dependencies to non-existent target "flash".
The add_dependencies works for top-level logical targets created by the
add_executable, add_library, or add_custom_target commands.  If you want to
add file-level dependencies see the DEPENDS option of the add_custom_target
and add_custom_command commands.
-- Configuring incomplete, errors occurred!
See also "/home/philo/esp/esp-at/build/CMakeFiles/CMakeOutput.log".
cmake failed with exit code 1

Please use build.py in the AT project to compile the firmware, the detailed steps: https://docs.espressif.com/projects/esp-at/en/latest/Compile_and_Develop/How_to_clone_project_and_compile_it.html

Ok, Thanks. But when I run
"./build.py menuconfig"
A new window opens and closes immediately.
https://user-images.githubusercontent.com/41112579/145361632-fa88754f-4b44-4b46-a35d-903a23bd19f2.mp4
IDF. v- 4.3ESP-IDF v4.3.1
Esp-at v -<IP_ADDRESS>

Could you try python build.py menuconfig?

PS C:\Users\aaere\esp\esp-at>  python build.py menuconfig
Traceback (most recent call last):
File "build.py", line 25, in
import xlrd
ModuleNotFoundError: No module named 'xlrd'
PS C:\Users\aaere\esp\esp-at>

python -m pip install pyyaml xlrd
BTW, you can remove esp-idf and  build directory, and it will clone the correct esp-idf.

Yes I got this.
Is this ok?

Installed: python -m pip install pyyaml xlrd
I get this.

Then I run python ./build.py menuconfig
And it fails.. Please help.
PS C:\Users\aaere\esp\esp-at>  python build.py menuconfig
Platform name:

PLATFORM_ESP32
PLATFORM_ESP32C3
choose(range[1,2]):1

Module name:

WROOM-32
WROVER-32
PICO-D4
SOLO-1
MINI-1 (description: ESP32-U4WDH chip inside)
ESP32-D2WD (description: 2MB flash, No OTA)
ESP32_QCLOUD (description: QCLOUD TX:17 RX:16)
choose(range[1,7]):4

Enable silence mode to remove some logs and reduce the firmware size?
0. No

Yes
choose(range[0,1]):0
platform_name=ESP32,module_name=SOLO-1
Please wait for the SDK download to finish...
Cloning into 'esp-idf'...
remote: Enumerating objects: 289933, done.
remote: Total 289933 (delta 0), reused 0 (delta 0), pack-reused 289933
Receiving objects: 100% (289933/289933), 165.13 MiB | 7.59 MiB/s, done.
Resolving deltas: 100% (214286/214286), done.
Updating files: 100% (6722/6722), done.
old commit:37634f09b2e46901c46ec3dff663e7d076c71b69
checkout commit:5595042c16d989c8e44f999eb30ce0e6377fd86e
Please wait for the update to complete, which will take some time
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint:   git config pull.rebase false  # merge (the default strategy)
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Already up to date.
Note: switching to '5595042c16d989c8e44f999eb30ce0e6377fd86e'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 5595042c16 Merge branch 'feature/windows_installer_moved_to_github_backport_4.2' into 'release/v4.2'
Submodule 'components/asio/asio' (https://github.com/espressif/asio.git) registered for path 'components/asio/asio'
Submodule 'components/bootloader/subproject/components/micro-ecc/micro-ecc' (https://github.com/kmackay/micro-ecc.git) registered for path 'components/bootloader/subproject/components/micro-ecc/micro-ecc'
Submodule 'components/bt/controller/lib' (https://github.com/espressif/esp32-bt-lib.git) registered for path 'components/bt/controller/lib'
Submodule 'components/bt/host/nimble/nimble' (https://github.com/espressif/esp-nimble.git) registered for path 'components/bt/host/nimble/nimble'
Submodule 'components/cbor/tinycbor' (https://github.com/intel/tinycbor.git) registered for path 'components/cbor/tinycbor'
Submodule 'components/coap/libcoap' (https://github.com/obgm/libcoap.git) registered for path 'components/coap/libcoap'
Submodule 'components/esp_wifi/lib' (https://github.com/espressif/esp32-wifi-lib.git) registered for path 'components/esp_wifi/lib'
Submodule 'components/esptool_py/esptool' (https://github.com/espressif/esptool.git) registered for path 'components/esptool_py/esptool'
Submodule 'components/expat/expat' (https://github.com/libexpat/libexpat.git) registered for path 'components/expat/expat'
Submodule 'components/json/cJSON' (https://github.com/DaveGamble/cJSON.git) registered for path 'components/json/cJSON'
Submodule 'components/libsodium/libsodium' (https://github.com/jedisct1/libsodium.git) registered for path 'components/libsodium/libsodium'
Submodule 'components/lwip/lwip' (https://github.com/espressif/esp-lwip.git) registered for path 'components/lwip/lwip'
Submodule 'components/mbedtls/mbedtls' (https://github.com/espressif/mbedtls.git) registered for path 'components/mbedtls/mbedtls'
Submodule 'components/mqtt/esp-mqtt' (https://github.com/espressif/esp-mqtt.git) registered for path 'components/mqtt/esp-mqtt'
Submodule 'components/nghttp/nghttp2' (https://github.com/nghttp2/nghttp2.git) registered for path 'components/nghttp/nghttp2'
Submodule 'components/protobuf-c/protobuf-c' (https://github.com/protobuf-c/protobuf-c.git) registered for path 'components/protobuf-c/protobuf-c'
Submodule 'components/spiffs/spiffs' (https://github.com/pellepl/spiffs.git) registered for path 'components/spiffs/spiffs'
Submodule 'components/tinyusb/tinyusb' (https://github.com/espressif/tinyusb.git) registered for path 'components/tinyusb/tinyusb'
Submodule 'components/unity/unity' (https://github.com/ThrowTheSwitch/Unity.git) registered for path 'components/unity/unity'
Submodule 'examples/build_system/cmake/import_lib/main/lib/tinyxml2' (https://github.com/leethomason/tinyxml2.git) registered for path 'examples/build_system/cmake/import_lib/main/lib/tinyxml2'
Submodule 'examples/peripherals/secure_element/atecc608_ecdsa/components/esp-cryptoauthlib' (https://github.com/espressif/esp-cryptoauthlib.git) registered for path 'examples/peripherals/secure_element/atecc608_ecdsa/components/esp-cryptoauthlib'
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/asio/asio'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/bootloader/subproject/components/micro-ecc/micro-ecc'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/bt/controller/lib'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/bt/host/nimble/nimble'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/cbor/tinycbor'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/coap/libcoap'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/esp_wifi/lib'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/esptool_py/esptool'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/expat/expat'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/json/cJSON'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/libsodium/libsodium'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/lwip/lwip'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/mbedtls/mbedtls'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/mqtt/esp-mqtt'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/nghttp/nghttp2'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/protobuf-c/protobuf-c'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/spiffs/spiffs'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/tinyusb/tinyusb'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/unity/unity'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/examples/build_system/cmake/import_lib/main/lib/tinyxml2'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/examples/peripherals/secure_element/atecc608_ecdsa/components/esp-cryptoauthlib'...
Submodule path 'components/asio/asio': checked out '3b66e5b051381fb70de9c2791df70a06181c64e3'
Submodule path 'components/bootloader/subproject/components/micro-ecc/micro-ecc': checked out 'd037ec89546fad14b5c4d5456c2e23a71e554966'
Submodule path 'components/bt/controller/lib': checked out 'cfbb0571fb424ca4a68a0c172cbff1fdc79fd91b'
Submodule path 'components/bt/host/nimble/nimble': checked out '2876071f84596cab0b4e44ca599903099e135e5f'
Submodule path 'components/cbor/tinycbor': checked out 'd2dd95cb8841d88d5a801e3ef9c328fd6200e7bd'
Submodule path 'components/coap/libcoap': checked out '98954eb30a2e728e172a6cd29430ae5bc999b585'
Submodule 'ext/tinydtls' (https://github.com/eclipse/tinydtls.git) registered for path 'components/coap/libcoap/ext/tinydtls'
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/coap/libcoap/ext/tinydtls'...
Submodule path 'components/coap/libcoap/ext/tinydtls': checked out '7f8c86e501e690301630029fa9bae22424adf618'
Submodule path 'components/esp_wifi/lib': checked out 'fbcdc77c26eb0d716927c8bc7d73dbec9a8987c1'
Submodule path 'components/esptool_py/esptool': checked out '4698b396730b23fb4aab023c5fb1744db957fc4c'
Submodule path 'components/expat/expat': checked out 'a28238bdeebc087071777001245df1876a11f5ee'
Submodule path 'components/json/cJSON': checked out 'd348621ca93571343a56862df7de4ff3bc9b5667'
Submodule path 'components/libsodium/libsodium': checked out '4f5e89fa84ce1d178a6765b8b46f2b6f91216677'
Submodule path 'components/lwip/lwip': checked out '2c9c531f0a7e0ee536db9de4f9dc54e453712087'
Submodule path 'components/mbedtls/mbedtls': checked out '6465247f67167518b8813ae2faaf422704e4b1a3'
Submodule path 'components/mqtt/esp-mqtt': checked out '9ea804e0ab5368d5ab53ae2301a5fec9d1f12f1a'
Submodule path 'components/nghttp/nghttp2': checked out '8f7b008b158e12de0e58247afd170f127dbb6456'
Submodule 'third-party/mruby' (https://github.com/mruby/mruby) registered for path 'components/nghttp/nghttp2/third-party/mruby'
Submodule 'third-party/neverbleed' (https://github.com/tatsuhiro-t/neverbleed.git) registered for path 'components/nghttp/nghttp2/third-party/neverbleed'
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/nghttp/nghttp2/third-party/mruby'...
Cloning into 'C:/Users/aaere/esp/esp-at/esp-idf/components/nghttp/nghttp2/third-party/neverbleed'...
Submodule path 'components/nghttp/nghttp2/third-party/mruby': checked out '7c91efc1ffda769a5f1a872c646c82b00698f1b8'
Submodule path 'components/nghttp/nghttp2/third-party/neverbleed': checked out 'b967ca054f48a36f82d8fcdd32e54ec5144f2751'
Submodule path 'components/protobuf-c/protobuf-c': checked out 'dac1a65feac4ad72f612aab99f487056fbcf5c1a'
Submodule path 'components/spiffs/spiffs': checked out 'f5e26c4e933189593a71c6b82cda381a7b21e41c'
Submodule path 'components/tinyusb/tinyusb': checked out '28f89e13473d40637574bcbfe4142633b39899fd'
Submodule path 'components/unity/unity': checked out '7d2bf62b7e6afaf38153041a9d53c21aeeca9a25'
Submodule path 'examples/build_system/cmake/import_lib/main/lib/tinyxml2': checked out '7e8e249990ec491ec15990cf95b6d871a66cf64a'
Submodule path 'examples/peripherals/secure_element/atecc608_ecdsa/components/esp-cryptoauthlib': checked out 'c3d3a69021cfec3236ca2c0b63be4048ec6643a4'
Update completed
WARNING: IDF_PATH environment variable is set to c:\users\aaere\esp\esp-idf but esp-idf\tools\idf.py path indicates IDF directory c:\users\aaere\esp\esp-at\esp-idf. Using the environment variable directory, but results may be unexpected...
Traceback (most recent call last):
File "esp-idf\tools\idf.py", line 794, in
main()
File "esp-idf\tools\idf.py", line 711, in main
cli = init_cli(verbose_output=checks_output)
File "esp-idf\tools\idf.py", line 669, in init_cli
extensions.append((name, import_module(name)))
File "importlib_init_.py", line 127, in import_module
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "c:\users\aaere\esp\esp-idf\tools\idf_py_actions\core_ext.py", line 8, in
from idf_py_actions.constants import GENERATORS, PREVIEW_TARGETS, SUPPORTED_TARGETS
ImportError: cannot import name 'PREVIEW_TARGETS' from 'idf_py_actions.constants' (C:\Users\aaere\esp\esp-at\esp-idf\tools\idf_py_actions\constants.py)
idf.py build ret: 1
idf.py build failed
PS C:\Users\aaere\esp\esp-at>

WARNING: IDF_PATH environment variable is set to c:\users\aaere\esp\esp-idf but esp-idf\tools\idf.py path indicates IDF directory c:\users\aaere\esp\esp-at\esp-idf. Using the environment variable directory, but results may be unexpected...

You can set IDF_PATH to c:\users\aaere\esp\esp-at\esp-idf, and try again

Can you compile hello-world in the esp-idf/example successfully?

ESP-IDF v4.2.2-331-g5595042c16
PS C:\Users\aaere\esp\esp-idf\examples\get-started\hello_world> $IDF_PATH
C:\Users\aaere\esp\esp-idf
PS C:\Users\aaere\esp\esp-idf\examples\get-started\hello_world> idf.py set-target esp32
WARNING: IDF_PATH environment variable is set to c:\users\aaere\esp\esp-at\esp-idf but idf.py path indicates IDF directory c:\users\aaere\esp\esp-idf. Using the environment variable directory, but results may be unexpected...
The following Python requirements are not satisfied:
cryptography>=2.1.4,<35
To install the missing packages, please run "C:\Users\aaere\esp\esp-at\esp-idf\install.bat"
Diagnostic information:
IDF_PYTHON_ENV_PATH: C:\Users\aaere.espressif\python_env\idf4.3_py3.8_env
Python interpreter used: C:\Users\aaere.espressif\python_env\idf4.3_py3.8_env\Scripts\python.exe
ESP-IDF v4.2.2-331-g5595042c16
PS C:\Users\aaere\esp\esp-idf\examples\get-started\hello_world> $IDF_PATH
C:\Users\aaere\esp\esp-idf
PS C:\Users\aaere\esp\esp-idf\examples\get-started\hello_world> ${IDF_PATH} = "C:\Users\aaere\esp\esp_at\esp-idf"
PS C:\Users\aaere\esp\esp-idf\examples\get-started\hello_world> $IDF_PATH
C:\Users\aaere\esp\esp_at\esp-idf
PS C:\Users\aaere\esp\esp-idf\examples\get-started\hello_world> cd ..
PS C:\Users\aaere\esp\esp-idf\examples\get-started> cd ..
PS C:\Users\aaere\esp\esp-idf\examples> cd..
PS C:\Users\aaere\esp\esp-idf> cd ..
PS C:\Users\aaere\esp> cd .\esp-at
PS C:\Users\aaere\esp\esp-at> cd .\esp-idf
PS C:\Users\aaere\esp\esp-at\esp-idf> .\install.bat
Installing ESP-IDF tools
Selected targets are: esp32s2, esp32, esp32s3
Installing tools: xtensa-esp32-elf, xtensa-esp32s2-elf, esp32ulp-elf, esp32s2ulp-elf, cmake, openocd-esp32, ninja, idf-exe, ccache, dfu-util
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Setting up Python environment
ERROR: This script was called from a virtual environment, can not create a virtual environment again
PS C:\Users\aaere\esp\esp-at\esp-idf>

PS C:\Users\aaere\esp\esp-at> $IDF_PATH
C:\Users\aaere\esp\esp-at\esp-idf
PS C:\Users\aaere\esp\esp-at> ${IDF_PATH} = "C:\Users\aaere\esp\esp-at\esp-idf"
PS C:\Users\aaere\esp\esp-at> $IDF_PATH
C:\Users\aaere\esp\esp-at\esp-idf
PS C:\Users\aaere\esp\esp-at> python build.py menuconfig
module_name SOLO-1
platform_name=ESP32,module_name=SOLO-1
WARNING: IDF_PATH environment variable is set to c:\users\aaere\esp\esp-idf but esp-idf\tools\idf.py path indicates IDF directory c:\users\aaere\esp\esp-at\esp-idf. Using the environment variable directory, but results may be unexpected...
Traceback (most recent call last):
File "esp-idf\tools\idf.py", line 794, in
main()
File "esp-idf\tools\idf.py", line 711, in main
cli = init_cli(verbose_output=checks_output)
File "esp-idf\tools\idf.py", line 669, in init_cli
extensions.append((name, import_module(name)))
File "importlib_init_.py", line 127, in import_module
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "c:\users\aaere\esp\esp-idf\tools\idf_py_actions\core_ext.py", line 8, in
from idf_py_actions.constants import GENERATORS, PREVIEW_TARGETS, SUPPORTED_TARGETS
ImportError: cannot import name 'PREVIEW_TARGETS' from 'idf_py_actions.constants' (C:\Users\aaere\esp\esp-at\esp-idf\tools\idf_py_actions\constants.py)
idf.py build ret: 1
idf.py build failed

Can you compile hello-world in the esp-idf/example successfully?

I was working fine  before I changed the path. to ${IDF_PATH} = "C:\Users\aaere\esp\esp-at\esp-idf"
Now I get this....
PS C:\Users\aaere\esp\esp-at\esp-idf\examples\get-started\hello_world> idf.py
WARNING: IDF_PATH environment variable is set to c:\users\aaere\esp\esp-idf but C:\Users\aaere\esp\esp-at\esp-idf\tools\idf.py path indicates IDF directory c:\users\aaere\esp\esp-at\esp-idf. Using the environment variable directory, but results may be unexpected...
Traceback (most recent call last):
File "C:\Users\aaere\esp\esp-at\esp-idf\tools\idf.py", line 794, in
main()
File "C:\Users\aaere\esp\esp-at\esp-idf\tools\idf.py", line 711, in main
cli = init_cli(verbose_output=checks_output)
File "C:\Users\aaere\esp\esp-at\esp-idf\tools\idf.py", line 669, in init_cli
extensions.append((name, import_module(name)))
File "importlib_init_.py", line 127, in import_module
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "c:\users\aaere\esp\esp-idf\tools\idf_py_actions\core_ext.py", line 8, in
from idf_py_actions.constants import GENERATORS, PREVIEW_TARGETS, SUPPORTED_TARGETS
ImportError: cannot import name 'PREVIEW_TARGETS' from 'idf_py_actions.constants' (C:\Users\aaere\esp\esp-at\esp-idf\tools\idf_py_actions\constants.py)
PS C:\Users\aaere\esp\esp-at\esp-idf\examples\get-started\hello_world>

Run ESP-IDF 4.3 CMD, then switch to the root directory of AT
Delete the build directory and sdkconfig file
Execute build.py menuconfig
Enter the esp-idf directory after executing the command
Execute install.bat
Execute export.bat
Return AT root directory and then build.py build

ok i try now.

Run ESP-IDF 4.3 CMD, then switch to the root directory of AT
-Deleted / uninstalled all IDF installation.
-Installed a new ESP-IDF 4.3 to path "C:\Users\aaere\esp"

Then I did
cd %userprofile%\esp
git clone --recursive https://github.com/espressif/esp-at.git
switch to esp-at directory  " cd esp-at"

Delete the build directory and sdkconfig file
since this a fresh installation, no build directory and sdkconfig file

Execute build.py menuconfig

in esp/esp-at folder I run "build.py menuconfig"
a new dialog opens, I configured for esp32, solo-1. and after some time the new dialog closed automatically.

Enter the esp-idf directory after executing the command

entered the esp-idf directory using the command "cd c://users/aaere/esp/esp-at/esp-idf"

Execute install.bat

excuted "install.bat" inside /esp/esp-at/esp-idf folder.
C:\Users\aaere\esp\esp-at\esp-idf>install.bat
Installing ESP-IDF tools
WARNING: File C:\Users\aaere.espressif\idf-env.json was not found.
Creating C:\Users\aaere.espressif\idf-env.json
Selected targets are: esp32, esp32s3, esp32s2
Installing tools: xtensa-esp32-elf, xtensa-esp32s2-elf, esp32ulp-elf, esp32s2ulp-elf, cmake, openocd-esp32, ninja, idf-exe, ccache, dfu-util
Installing<EMAIL_ADDRESS>Downloading xtensa-esp32-elf-gcc8_4_0-esp-2020r3-win64.zip to C:\Users\aaere.espressif\dist\xtensa-esp32-elf-gcc8_4_0-esp-2020r3-win64.zip.tmp
Done
Extracting C:\Users\aaere.espressif\dist\xtensa-esp32-elf-gcc8_4_0-esp-2020r3-win64.zip to C:\Users\aaere.espressif\tools\xtensa-esp32-elf\esp-2020r3-8.4.0
Installing<EMAIL_ADDRESS>Downloading xtensa-esp32s2-elf-gcc8_4_0-esp-2020r3-win64.zip to C:\Users\aaere.espressif\dist\xtensa-esp32s2-elf-gcc8_4_0-esp-2020r3-win64.zip.tmp
Done
Extracting C:\Users\aaere.espressif\dist\xtensa-esp32s2-elf-gcc8_4_0-esp-2020r3-win64.zip to C:\Users\aaere.espressif\tools\xtensa-esp32s2-elf\esp-2020r3-8.4.0
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Installing<EMAIL_ADDRESS>Downloading openocd-esp32-win32-0.10.0-esp32-20210902.zip to C:\Users\aaere.espressif\dist\openocd-esp32-win32-0.10.0-esp32-20210902.zip.tmp
Done
Extracting C:\Users\aaere.espressif\dist\openocd-esp32-win32-0.10.0-esp32-20210902.zip to C:\Users\aaere.espressif\tools\openocd-esp32\v0.10.0-esp32-20210902
Installing<EMAIL_ADDRESS>Downloading ninja-1.10.0-win64.zip to C:\Users\aaere.espressif\dist\ninja-1.10.0-win64.zip.tmp
Done
Extracting C:\Users\aaere.espressif\dist\ninja-1.10.0-win64.zip to C:\Users\aaere.espressif\tools\ninja\1.10.0
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Setting up Python environment
ERROR: This script was called from a virtual environment, can not create a virtual environment again

Execute export.bat
Return AT root directory and then build.py build

PS C:\Users\aaere\esp\esp-at\esp-idf> .\export.bat
Setting IDF_PATH: C:\Users\aaere\esp\esp-at\esp-idf
Adding ESP-IDF tools to PATH...
Not using an unsupported version of tool xtensa-esp32-elf found in PATH: esp-2021r1-8.4.0.
Not using an unsupported version of tool xtensa-esp32s2-elf found in PATH: esp-2021r1-8.4.0.
Not using an unsupported version of tool openocd-esp32 found in PATH: v0.10.0-esp32-20210401.
Not using an unsupported version of tool ninja found in PATH: 1.10.2.
C:\Users\aaere.espressif\tools\xtensa-esp32-elf\esp-2020r3-8.4.0\xtensa-esp32-elf\bin
C:\Users\aaere.espressif\tools\xtensa-esp32s2-elf\esp-2020r3-8.4.0\xtensa-esp32s2-elf\bin
C:\Users\aaere.espressif\tools\openocd-esp32\v0.10.0-esp32-20210902\openocd-esp32\bin
C:\Users\aaere.espressif\tools\ninja\1.10.0
C:\Users\aaere\esp\esp-at\esp-idf\tools
Checking if Python packages are up to date...
The following Python requirements are not satisfied:
cryptography>=2.1.4,<35
To install the missing packages, please run "C:\Users\aaere\esp\esp-at\esp-idf\install.bat"
Diagnostic information:
IDF_PYTHON_ENV_PATH: C:\Users\aaere.espressif\python_env\idf4.3_py3.8_env
Python interpreter used: C:\Users\aaere.espressif\python_env\idf4.3_py3.8_env\Scripts\python.exe
PS C:\Users\aaere\esp\esp-at\esp-idf>

C:\Users\aaere\esp\esp-at\esp-idf>export.bat
Setting IDF_PATH: C:\Users\aaere\esp\esp-at\esp-idf
Adding ESP-IDF tools to PATH...
Not using an unsupported version of tool xtensa-esp32-elf found in PATH: esp-2021r1-8.4.0.
Not using an unsupported version of tool xtensa-esp32s2-elf found in PATH: esp-2021r1-8.4.0.
Not using an unsupported version of tool openocd-esp32 found in PATH: v0.10.0-esp32-20210401.
Not using an unsupported version of tool ninja found in PATH: 1.10.2.
C:\Users\aaere.espressif\tools\xtensa-esp32-elf\esp-2020r3-8.4.0\xtensa-esp32-elf\bin
C:\Users\aaere.espressif\tools\xtensa-esp32s2-elf\esp-2020r3-8.4.0\xtensa-esp32s2-elf\bin
C:\Users\aaere.espressif\tools\openocd-esp32\v0.10.0-esp32-20210902\openocd-esp32\bin
C:\Users\aaere.espressif\tools\ninja\1.10.0
C:\Users\aaere\esp\esp-at\esp-idf\tools
Checking if Python packages are up to date...
The following Python requirements are not satisfied:
cryptography>=2.1.4,<35
To install the missing packages, please run "C:\Users\aaere\esp\esp-at\esp-idf\install.bat"
Diagnostic information:
IDF_PYTHON_ENV_PATH: C:\Users\aaere.espressif\python_env\idf4.3_py3.8_env
Python interpreter used: C:\Users\aaere.espressif\python_env\idf4.3_py3.8_env\Scripts\python.exe
C:\Users\aaere\esp\esp-at\esp-idf>

I have a question ? Do you want to compile ESP32 AT module ? Which version do you want to compile ？

esp-at ver <IP_ADDRESS>
On Thu, Dec 9, 2021 at 5:06 PM Alson-tang @.***> wrote:

I have a question ? Do you want to compile ESP32 AT module ? Which version
do you want to compile ？
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/espressif/esp-idf/issues/8043#issuecomment-989771647,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJZVIAZMWYMO3WF2PECKLITUQCICTANCNFSM5JU4RQOQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Thanks and Best Regards
Reny Vincent
9791008939

I have a question ? Do you want to compile ESP32 AT module ? Which version do you want to compile ？

ESP-AT v<IP_ADDRESS>

ESP32 v<IP_ADDRESS> is built on IDF v4.2 version. So I suggest you run ESP-IDF 4.2 CMD

ok
when I tried the install ESP-IDF release/4.2 cmd, installation fails.
Shall I install IDF version 4.2.2

You can install 4.2 release version

You can install 4.2 release version

Windows installer fails

Could you show me the error picture ?

Steps: what i did...
run "esp-idf-tools-setup-2.3.exe" to install

IDF in path "C:\Users\aaere\esp\esp-idf"
tools in path "C:\Users\aaere.espressif"

An then Installation went fine and I got CMD and Windows Shell for IDF
So opened the CMD prompt and typed this...
C:\Users\aaere\esp\esp-idf>idf.py --version
fatal: bad object HEAD
fatal: 'git status --porcelain=2' failed in submodule third-party/mruby
fatal: 'git status --porcelain=2' failed in submodule components/nghttp/nghttp2
WARNING: Git version unavailable, reading from source
ESP-IDF v4.2.2
C:\Users\aaere\esp\esp-idf>
I was expecting to get 4.2, but i got 4.2.2.

It should be no big problem, you can walk again in the way I gave you

Still Its not working for me...
Let me narrate the steps what I did...

Installed IDF version 4.2
please see the screen shot

cloned the esp-at project version <IP_ADDRESS> using the command...
"C:\Users\aaere\esp>git clone --recursive --branch v<IP_ADDRESS>_esp32 https://github.com/espressif/esp-at.git"
please see the screen shot

I entered to esp/esp-at folder and did "build.py menuconfig"..... So then a new cmd prompt window opens...
please see the screen shot

After entered the following details in new cmd prompt... the dialog clones "esp_idf" into esp/esp_at folder
The details... "ESP32, SOLO1, No Silence"

As I get no warnings or error..... I am going to do build.py menuconfig again in esp/eap_at
and I am expecting the following dialog..

6 But What i get in reality is .... the following video.. please see..
https://user-images.githubusercontent.com/41112579/145526071-fe85f5e5-3110-4a8a-a541-5cda622beb31.mp4

@xcguang @Alson-tang  Any help?

After executing the fourth step, there will be an esp-idf directory in the root directory of AT.
After entering the esp-idf directory, execute install.sh bat and thus execute export.bat
Go back to the AT root directory and continue to execute build.py menuconfig.

C:\Users\aaere\esp\esp-at>cd esp-idf
C:\Users\aaere\esp\esp-at\esp-idf>install.bat
Installing ESP-IDF tools
Installing tools: xtensa-esp32-elf, xtensa-esp32s2-elf, esp32ulp-elf, esp32s2ulp-elf, cmake, openocd-esp32, ninja, idf-exe, ccache, dfu-util
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Installing<EMAIL_ADDRESS>Downloading openocd-esp32-win32-0.10.0-esp32-20200709.zip to C:\Users\aaere.espressif\dist\openocd-esp32-win32-0.10.0-esp32-20200709.zip.tmp
Done
Extracting C:\Users\aaere.espressif\dist\openocd-esp32-win32-0.10.0-esp32-20200709.zip to C:\Users\aaere.espressif\tools\openocd-esp32\v0.10.0-esp32-20200709
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Setting up Python environment
Installing Python packages from C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt
Processing c:\users\aaere\esp\esp-at\esp-idf\tools\kconfig_new\esp-windows-curses
Preparing metadata (setup.py) ... done
Requirement already satisfied: setuptools>=21 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 4)) (51.3.3)
Requirement already satisfied: click>=5.0 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 8)) (8.0.3)
Requirement already satisfied: pyserial>=3.0 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 9)) (3.5)
Requirement already satisfied: future>=0.15.2 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 10)) (0.18.2)
Requirement already satisfied: cryptography>=2.1.4 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 11)) (3.4.8)
Requirement already satisfied: pyparsing<2.4.0,>=2.0.3 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 12)) (2.3.1)
Requirement already satisfied: pyelftools>=0.22 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 13)) (0.27)
Requirement already satisfied: gdbgui==<IP_ADDRESS> in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (<IP_ADDRESS>)
Requirement already satisfied: pygdbmi<=<IP_ADDRESS> in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 18)) (<IP_ADDRESS>)
Requirement already satisfied: python-socketio<5 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 21)) (4.6.1)
Requirement already satisfied: reedsolo<=1.5.4,>=1.5.3 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 24)) (1.5.4)
Requirement already satisfied: bitstring>=3.1.6 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 25)) (3.1.9)
Requirement already satisfied: ecdsa>=0.16.0 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from -r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 26)) (0.17.0)
Requirement already satisfied: Pygments<3.0,>=2.2.0 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (2.10.0)
Requirement already satisfied: Flask<1.0,>=0.12.2 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (0.12.5)
Requirement already satisfied: Flask-Compress<2.0,>=1.4.0 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (1.10.1)
Requirement already satisfied: gevent<2.0,>=1.2.2 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (1.5.0)
Requirement already satisfied: Flask-SocketIO<3.0,>=2.9 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (2.9.6)
Requirement already satisfied: colorama in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from click>=5.0->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 8)) (0.4.4)
Requirement already satisfied: cffi>=1.12 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from cryptography>=2.1.4->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 11)) (1.15.0)
Requirement already satisfied: six>=1.9.0 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from python-socketio<5->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 21)) (1.16.0)
Requirement already satisfied: python-engineio<4,>=3.13.0 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from python-socketio<5->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 21)) (3.14.2)
Requirement already satisfied: windows-curses in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from esp-windows-curses==0.1->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 32)) (2.3.0)
Requirement already satisfied: pycparser in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from cffi>=1.12->cryptography>=2.1.4->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 11)) (2.21)
Requirement already satisfied: Jinja2>=2.4 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from Flask<1.0,>=0.12.2->gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (3.0.3)
Requirement already satisfied: itsdangerous>=0.21 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from Flask<1.0,>=0.12.2->gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (2.0.1)
Requirement already satisfied: Werkzeug<1.0,>=0.7 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from Flask<1.0,>=0.12.2->gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (0.16.1)
Requirement already satisfied: brotli in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from Flask-Compress<2.0,>=1.4.0->gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (1.0.9)
Requirement already satisfied: greenlet>=0.4.14 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from gevent<2.0,>=1.2.2->gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (1.1.2)
Requirement already satisfied: MarkupSafe>=2.0 in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (from Jinja2>=2.4->Flask<1.0,>=0.12.2->gdbgui==<IP_ADDRESS>->-r C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt (line 15)) (2.0.1)
Building wheels for collected packages: esp-windows-curses
Building wheel for esp-windows-curses (setup.py) ... done
Created wheel for esp-windows-curses: filename=esp_windows_curses-0.1-py3-none-any.whl size=1170 sha256=07d0e1ec4cd4e59c2a11bbab95f5bab64805c6f51adba181749ad63fbc485ce4
Stored in directory: c:\users\aaere\appdata\local\pip\cache\wheels\b9\72\6f\ceb22d12afa00053f82745220e8d7dc9caacfbaa6711905483
Successfully built esp-windows-curses
Installing collected packages: esp-windows-curses
Attempting uninstall: esp-windows-curses
Found existing installation: esp-windows-curses 0.1
Uninstalling esp-windows-curses-0.1:
Successfully uninstalled esp-windows-curses-0.1
Successfully installed esp-windows-curses-0.1
All done! You can now run:
export.bat
C:\Users\aaere\esp\esp-at\esp-idf>export.bat
Setting IDF_PATH: C:\Users\aaere\esp\esp-at\esp-idf
Adding ESP-IDF tools to PATH...
Not using an unsupported version of tool openocd-esp32 found in PATH: v0.10.0-esp32-20211111.
C:\Users\aaere.espressif\tools\openocd-esp32\v0.10.0-esp32-20200709\openocd-esp32\bin
C:\Users\aaere\esp\esp-at\esp-idf\tools
Checking if Python packages are up to date...
Python requirements from C:\Users\aaere\esp\esp-at\esp-idf\requirements.txt are satisfied.
Done! You can now compile ESP-IDF projects.
Go to the project directory and run:
idf.py build
C:\Users\aaere\esp\esp-at\esp-idf>
C:\Users\aaere\esp\esp-at\esp-idf>cd ..
C:\Users\aaere\esp\esp-at>build.py menuconfig
C:\Users\aaere\esp\esp-at>build.py menuconfig
C:\Users\aaere\esp\esp-at>
Now I am getting the same result.
Please see the video..
https://user-images.githubusercontent.com/41112579/145586436-29696f8e-52ab-4c68-8d7b-5482f366372c.mp4

In current cmd shell, run python -m pip install pyyaml xlrd and try again please.

C:\Users\aaere\esp\esp-at>python -m pip install pyyaml xlrd
Requirement already satisfied: pyyaml in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (6.0)
Requirement already satisfied: xlrd in c:\users\aaere.espressif\python_env\idf4.2_py3.8_env\lib\site-packages (2.0.1)
C:\Users\aaere\esp\esp-at>build.py menuconfig
And I am getting same result. Please see the video.
https://user-images.githubusercontent.com/41112579/145589484-8f0e5caf-5b42-44e2-abda-132c50b555cd.mp4

python build.py build to check the error log please.

python buil.py build.txt
Build seems success. can you please check sir.?

Now I run
cmd prompt: esp/esp-at/python build.py menuconfig
I get this.
https://user-images.githubusercontent.com/41112579/145594587-ede4f99c-23c0-4a98-b270-997dd33bbb91.mp4

Thanks @Alson-tang @xcguang

Good news

Good to hear it is working, feel free to reopen.

hello guys
I'm using Windows for development
I installed the ESP-IDF Tools and choose release/v4.2(release branch) .
I'm attempting to compile esp-at project for the ESP8266.
Setting PYTHONNOUSERSITE, was not set
Using Python in C:\Users\Hossein\esp.espressif\python_env\idf4.2_py3.8_env\Scripts
Python 3.8.7
Using Git in C:\Users\Hossein\esp.espressif\tools\idf-git\2.30.1\cmd
git version 2.30.1.windows.1
Setting IDF_PATH: C:\Users\Hossein\esp\esp-idf
Adding ESP-IDF tools to PATH...
C:\Users\Hossein\esp.espressif\tools\xtensa-esp32-elf\esp-2020r3-8.4.0\xtensa-esp32-elf\bin
C:\Users\Hossein\esp.espressif\tools\xtensa-esp32s2-elf\esp-2020r3-8.4.0\xtensa-esp32s2-elf\bin
C:\Users\Hossein\esp.espressif\tools\esp32ulp-elf\2.28.51-esp-20191205\esp32ulp-elf-binutils\bin
C:\Users\Hossein\esp.espressif\tools\esp32s2ulp-elf\2.28.51-esp-20191205\esp32s2ulp-elf-binutils\bin
C:\Users\Hossein\esp.espressif\tools\cmake\3.16.4\bin
C:\Users\Hossein\esp.espressif\tools\openocd-esp32\v0.10.0-esp32-20200709\openocd-esp32\bin
C:\Users\Hossein\esp.espressif\tools\ninja\1.10.0
C:\Users\Hossein\esp.espressif\tools\idf-exe\1.0.1
C:\Users\Hossein\esp.espressif\tools\ccache\3.7
C:\Users\Hossein\esp.espressif\tools\dfu-util\0.9\dfu-util-0.9-win64
C:\Users\Hossein\esp\esp-idf\tools
Checking if Python packages are up to date...
Python requirements from C:\Users\Hossein\esp\esp-idf\requirements.txt are satisfied.
Done! You can now compile ESP-IDF projects.
Go to the project directory and run:
idf.py build
C:\Users\Hossein\esp\esp-idf>cd ..
C:\Users\Hossein\esp>cd esp-at
C:\Users\Hossein\esp\esp-at>python build.py menuconfig
module_name ESP8266_1MB
platform_name=ESP8266,module_name=ESP8266_1MB
WARNING: IDF_PATH environment variable is set to c:\users\hossein\esp\esp-idf but esp-idf\tools\idf.py path indicates IDF directory c:\users\hossein\esp\esp-at\esp-idf. Using the environment variable directory, but results may be unexpected...
Checking Python dependencies...
Python requirements from C:\Users\Hossein\esp\esp-idf\requirements.txt are satisfied.
Executing action: menuconfig
Running cmake in directory c:\users\hossein\esp\esp-at\build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DIDF_TARGET=esp8266 -DCCACHE_ENABLE=0 c:\users\hossein\esp\esp-at"...
silence:1 sdkconfig:C:/Users/Hossein/esp/esp-at/module_config/module_esp8266_1mb/sdkconfig_silence.defaults
CMake Warning at esp-idf/tools/cmake/idf.cmake:14 (message):
IDF_PATH environment variable is different from inferred IDF_PATH.
Check if your project's top-level CMakeLists.txt includes the right
CMake files. Environment IDF_PATH will be used for the build.
Call Stack (most recent call first):
esp-idf/tools/cmake/project.cmake:7 (include)
CMakeLists.txt:49 (include)
-- Found Git: C:/Users/Hossein/esp/.espressif/tools/idf-git/2.30.1/cmd/git.exe (found version "2.30.1.windows.1")
CMake Error at C:/Users/Hossein/esp/esp-idf/tools/cmake/targets.cmake:57 (message):
Unable to resolve 'esp8266' for setting toolchain file.
Call Stack (most recent call first):
esp-idf/tools/cmake/project.cmake:245 (__target_set_toolchain)
CMakeLists.txt:51 (project)
-- Configuring incomplete, errors occurred!
cmake failed with exit code 1
idf.py build ret: 2
idf.py build failed
I went this under path , but the install.sh and export.sh files do not run in Windows .
There are no install.bat and export.bat files for esp-idf esp8266 .
C:\Users\Hossein\esp\esp-at>cd esp-idf
C:\Users\Hossein\esp\esp-at\esp-idf>install.bat
'install.bat' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Hossein\esp\esp-at\esp-idf>install.sh
How do you recommend the use of both the ESP32 IDF and ESP8266 IDF since both use the same ENV variable but the associated paths are different?


[BUG] Packets exchanged between client and server shoot up to 3000+ during login/register

Versions

EasyAuth 1.9.3
Fabric API 0.37.1

Describe the bug
When a player joins the server and is in the frozen state where he is asked to login/register, the packets exchanged between the client and the server (tx and xx on left side in F3 debug screen) steadily rise to more than 3000, before the player is disconnected for not entering the password in time (This number may increase if the time limit is increased).
To Reproduce
Steps to reproduce the behavior:

Install EasyAuth on the server.
Start the server.
Join the server, but don't login/register.
Open the debug screen with F3.

Screenshot:
Expected behavior
The packets exchanged should be normal, rather than increasing with time.
Additional context
An increased number of packets being exchanged means that it is impossible to have EasyAuth on the server and implement a reasonable rate-limit from server.properties at the same time.
A higher rate of packet exchange may also require a lot of internet bandwidth, but I cannot confirm whether the packets transferred actually carry enough information to have an impact on network usage.

Thanks for the report!
I'll try to figure it out.
But I'm not sure if I can fix this problem because of the way how packet (movement in particular) cancellation works.

Ok, cool!
I forgot to mention another thing: the increased packets cause you to get kicked form the server in 5-6 seconds if you are in spectator mode, because, apparently, the packet rate limit for spectator mode is 600 or something.

I added new settings in experimental part which limit how often server can send teleportation packet to unauthorized players.
Note that this settings is server-wide so maximum rate would be (1000/teleportationTimeoutInMs) per seconds for all unauthorized players. I don't think it cause any problem until you will have something like few hundreds unauthorized players at the same moment.
Value 0 would effectively disable this settings so players will be teleported after each packet.
By default value is 5, so it will be capped at 200 packets/second.
If you want you can test pre-release version with this settings. You can download it here (click at Artifacts button)

Thanks a lot!


Adafruit_Python_PN532 checksum fail

Hi,
I am running readmifare.py example code from the Adafruit_Python_PN532 library using the PN532 Breakout Board connected to Raspberry Pi 3 via software SPI. When I tap a mifare card against the board the code stops with the following error:
RuntimeError: Response checksum did not match expected value!
Below is a full log from code startup till the run time error:-
sudo python3 readmifare.py
Python Version: 3.5.3
DEBUG:Adafruit_PN532.PN532:Using software SPI
DEBUG:Adafruit_PN532.PN532:Write frame: 0xb'010000ff02fed4022a00'
DEBUG:Adafruit_PN532.PN532:Read frame: 0xb'010000ff06fad50332010607e800'
DEBUG:Adafruit_PN532.PN532:Write frame: 0xb'010000ff02fed4022a00'
DEBUG:Adafruit_PN532.PN532:Read frame: 0xb'010000ff06fad50332010607e800'
Found PN532 with firmware version: 1.6
DEBUG:Adafruit_PN532.PN532:Write frame: 0xb'010000ff05fbd4140114010200'
DEBUG:Adafruit_PN532.PN532:Read frame: 0xb'010000ff02fed5151600'
Waiting for MiFare card..
DEBUG:Adafruit_PN532.PN532:Write frame: 0xb'010000ff04fcd44a0100e100'
DEBUG:Adafruit_PN532.PN532:Read frame: 0xb'010000ff15ebd54b010103442007047368a2c72280067577810280'
Traceback (most recent call last):
File "readmifare.py", line 63, in
uid = pn532.read_passive_target()
File "/usr/local/lib/python3.5/dist-packages/Adafruit_PN532-1.2.1-py3.5.egg/Adafruit_PN532/PN532.py", line 373, in read_passive_target
File "/usr/local/lib/python3.5/dist-packages/Adafruit_PN532-1.2.1-py3.5.egg/Adafruit_PN532/PN532.py", line 327, in call_function
File "/usr/local/lib/python3.5/dist-packages/Adafruit_PN532-1.2.1-py3.5.egg/Adafruit_PN532/PN532.py", line 274, in _read_frame
RuntimeError: Response checksum did not match expected value!
Can anyone tell me what is going wrong. If I bypass the checksum check then the code works fine and I get the card UID
Check frame checksum value matches bytes.
checksum = reduce(self._uint8_add, response[offset+2:offset+2+frame_len+1], 0)
#if checksum != 0:
raise RuntimeError('Response checksum did not match expected value!')
Any help would be greatly appreciated.
-David

could be bad wiring?
also, we've re-written this library to support circuitpython/python, i2c and uart as well! we've redone the GPIO code so this could be fixed there
thanks! https://github.com/adafruit/Adafruit_CircuitPython_PN532


[ZEPPELIN-6099] Fix default ZEPPELIN_ANGULAR_WAR value

What is this PR for?
The misconfigured default ZEPPELIN_ANGULAR_WAR value is causing the failure to load the new UI web application files on development environment.
The new UI web apps are built into ZEPPELIN_HOME/zeppelin-web-angular/dist/zeppelin, but the default value lacks the /zeppelin postfix.
When developers run Zeppelin with ZeppelinServer.main method, it defaults to the incorrect ZEPPELIN_ANGULAR_WAR value, leading to failure to load the web apps.
Note: This issue does not occur when Zeppelin is run using shell scripts in the bin, as they correctly set the ZEPPELIN_ANGULAR_WAR value.
What type of PR is it?
Bug Fix
Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/6099

How should this be tested?

Build Zeppelin
Run Zeppelin using ZeppelinServer.main method and connect to http://localhost:8080

Questions:

Does the license files need to update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Merged to master


Refactor Crdt Initialization

Currently, it is possible to create a Crdt without a parent by accident, e.g.,
const counter = new CCounter()
// Never attaches it to a parent/runtime...
// Messages from remote replicas will throw an error.
counter.add(7) // Throws an error at runtime.

This PR forces all Crdts to have a parent, by adding a CrdtInitToken constructor parameter to the Crdt base class.  That lets us remove the Crdt.init method used previously.
The library used be like this (with parent and name separate instead of in a CrdtInitToken) 6 months ago, but had the downside that any Crdt could make any other Crdt is parent, even if the parent didn't approve (e.g. a PrimitiveCrdt).  To avoid that, we make the rule (documented but not enforceable with types) that new CrdtInitToken(name, parent) can ONLY be called by parent itself, and then parent should immediately construct the child itself.
Methods like CompositeCrdt.addChild, which used to take the child directly, now take a callback (initToken: CrdtInitToken) => Crdt, then call that callback internally.  This lets them fully control the process of adding children, so that they can restrict child types, ban it entirely, only allow it at certain times, etc.  For brevity, we define the type Pre<C> = (initToken: CrdtInitToken) => C.  We also define a function Pre that converts a constructor of type C into a function that inputs the (non-token) constructor arguments and outputs a Pre<C>.  So now, instead of doing
runtime.registerCrdt("name", new CCounter(7));

you do
runtime.registerCrdt("name", Pre(CCounter)(7));

Thanks to Maxime for suggesting this approach a while ago, and to Ria for helpful API discussions.

Resolves https://github.com/composablesys/compoventuals/issues/32

One subtle convention I've been using (possibly a foolish consistency):
In most places where you give a Crdt to its parent (e.g. Runtime.registerCrdt, CompositeCrdt.addChild), you give it as a Pre<Crdt>, and then the parent returns the constructed Crdt.  However, there is a question of what to do when you are giving a child to a parent via a callback that is unrelated to CrdtInitToken.  E.g., in DeletingMutCSet's constructor, you have to supply a valueConstructor, that tells the set how to construct a value Crdt after receiving AddArgs over the network: https://github.com/composablesys/compoventuals/blob/e88d819fda4dc3504b9ec00d7c47b2fb1f569c3f/main/src/types/set/deleting_mut_set.ts#L107-L112
My question is: should a callback like valueConstructor return a Pre<Crdt>, or should it take the CrdtInitToken as its first argument and return the Crdt directly?
The rule I've adopted so far is:

if the parent exposes the created Crdt, then the callback should return a Pre<Crdt>.  E.g. setCallback: https://github.com/composablesys/compoventuals/blob/e88d819fda4dc3504b9ec00d7c47b2fb1f569c3f/main/src/types/list/movable_mut_list_from_set.ts#L62-L70
Here the eventual Crdt constructed from setCallback is exposed as this.set.
otherwise the callback should take the CrdtInitToken as its first argument and return the Crdt directly.  (E.g. DeletingMutCSet's valueConstructor.)

My reasoning is that you may need access to the finished Crdt, in case you want to store it somewhere or add event listeners; but that in general we should prefer Pre<Crdt>s when possible.
However, we could instead:

make all callbacks return the finished Crdt, for consistency
or, make all callbacks return a Pre<Crdt>, and if you want to add event listeners, you can do so in the Pre<Crdt> (which is itself a callback).

Merging for now so I can do other work on top of this, but I am open to suggested changes, which we can do on master later.


KFServing: Move manifests development upstream

Background
Umbrella-Issue: https://github.com/kubeflow/manifests/issues/1740
As part of the work of wg-manifests for 1.3
(https://github.com/kubeflow/manifests/issues/1735), we are moving manifests
development to upstream repos. This gives the application developers full
ownership of their manifests, tracked in a single place.
To give an example from the notebook-controller, the diagram shows the current
situation. Manifests are in two repos, blurring separation of responsibilities
and making things harder for application developers.

Instead, we will copy all manifests from the manifests repo back to each
upstream's repo. From there, they will be imported in the manifests repo. The
following diagram presents the desired state:

Current State
KFServing has manifests:

In the manifests repo, under folder apps/kfserving/upstream.
In upstream repo (https://github.com/kubeflow/kfserving) under folder config.

Desired State
The proposed folder in the upstream repo to receive the manifests is:
config.
The goal is to consolidate all manifests development in the upstream repo.
The manifests repo will include a copy of the manifests under apps/kfserving/upstream.
This copy will be synced periodically.
KFServing in particular already follows a similar pattern in kubeflow/manifests, but keeps the following extra folders:

kfserving-crds and kfserving-install: Are these folders maintained? Should they be transferred here or thrown out?
The installs/generic kustomization. This looks like it should be consolidated with overlays/kubeflow upstream.

What do you think?
Success Criteria
The manifests in apps/kfserving/upstream should be a copy of the upstream manifests
folder. To do that, the application manifests in kubeflow/manifests should be
moved to the upstream application repo.
/assign @yanniszark
cc @kubeflow/wg-serving-leads

/cc @pvaneck

@drewbutlerbb4 @animeshsingh while preparing the KFServing manifests for a PR, I noticed that overlays no longer install CRDs.
In addition, I noticed there are two crd kustomizations:

config/crd
config/default/crd which includes some extra patches and a namespace

It seems they were introduced in this PR: https://github.com/kubeflow/kfserving/pull/1244
Could you help me understand the purpose of this change?

The generated CRD size is too big to store in annotations, so we need to separate it into another kustomization.yaml and run kubectl create for that config.
I think one way to work around this is to manually prune the crd spec with x-kubernetes-preserve-unknown-fields: true . Many Knative CRDs use this on their openAPIV3Schema.

@yuzisun do you know where we should use x-kubernetes-preserve-unknown-fields: true on KFServing?

The generated CRD size is too big to store in annotations, so we need to separate it into another kustomization.yaml and run kubectl create for that config.

@Tomcli I tried to reproduce the issue by applying this file in a minikube cluster:
https://github.com/kubeflow/kfserving/blob/5569670250ed068df904774cdbdd7a2d7ca98a58/install/v0.5.0/kfserving_crds.yaml
I could not reproduce. Should the issue be happening with this file?

oh the KFServing 0.5 release yesterday removed the initContainers spec so it can fit into the annotations now.
@yanniszark so the goal here is to have the same pattern for both kubeflow/manifests and this repo?

oh the KFServing 0.5 release yesterday removed the initContainers spec so it can fit into the annotations now.

Was that a workaround? I think we should continue the discussion in issue https://github.com/kubeflow/kfserving/issues/1296 and update it with this new development.

@yanniszark so the goal here is to have the same pattern for both kubeflow/manifests and this repo?

The goal is to move kfserving manifests development in this repo (the upstream repo). Right now, there are two sources of truth for KFServing (this repo and kubeflow/manifests). We want to only have 1 source of truth (this repo) and kubeflow/manifests should simply copy a subfolder of this repo at a specific commit. You can see a longer explanation in this issue:
https://github.com/kubeflow/manifests/issues/1740
So I'm trying to make a PR to bring the kfserving manifests that are currently at kubeflow/manifests in this repo.
But I'm having some trouble figuring out the newly changed structure.

The kfserving-crds and kfserving-install directories that were in the manifests repo can be removed as those were YAMLs corresponding to an older version of KFServing. In regards to the kubeflow overlay, application.yaml, cluster-role.yaml and statefulset-patch.yaml are likely the only things from manifests repo kfserving/installs/generic directory that should be carried over.
The yaml here will also recreate the kubeflow namespace, so if there is no easy way to omit this, then I'm thinking that the kubeflow overlay will also need a namespace patch to reset the labels on the kubeflow namespace to what they were set to in kubeflow/manifests (i.e. control-plane: kubeflow and istio-injection: enabled). Otherwise applying the overlay will overwrite the initial kubeflow namespace labels.
And, yea. The new CRD structure makes things a bit tricky as I found that just adding ../../default/crd as a base to the kubeflow overlay does not work. If the CRD size is no longer an issue, perhaps going back to the old structure should be fine? It would certainly  simplify things here.
If not, then can just add ../../crd as a base in overlays/kubeflow/kustomize.yaml and copy over the two patches that are applied in ../../default/crd (i.e. inferenceservice_conversion_webhook.yaml and cainjection_conversion_webhook.yaml).

It would certainly simplify things here.

@pvaneck I'm all for simplifying and I believe the old structure was simpler, while the new one has certain peculiarities:

crd kustomization defined in two places, only one of which is valid (the config/default/crd one).
The kustomizations containing the crd resources (config/default/crd) and the installation resources (config/default/crd) can't be combined, as they both contain a namespace.

It also seems that the original reason for moving to this structure is gone:

oh the KFServing 0.5 release yesterday removed the initContainers spec so it can fit into the annotations now.

Given this information, should we revert to the previous configuration or at least fix some of the problems outlined above?
cc @Tomcli @yuzisun @animeshsingh @drewbutlerbb4

We can revert it back to the old ways since we no longer has the blocker issue.

PR for updating the kubeflow overlay to better match what we have in manifests:  #1424.
One concern is the matter of image tags for various images. In the config directory, most kfserving image tags are set to latest, but when the install/kfserving.yaml file is generated, these latest image tags are replaced with the release version (i.e. v0.5.1) through some automated (and also maybe manual) post-processing. So if we copy over the config directory at a specific release/commit, the image tags would probably need to be changed from latest on the manifests side as well.
One alternative is that KFServing generates a kfserving_kubeflow.yaml per release in the install directory (i.e. install/$TAG/kfserving_kubeflow.yaml) and we just keep syncing that. This would be generated using the kubeflow overlay and looks to be something that has already been explored (e.g https://github.com/kubeflow/kfserving/blob/master/install/v0.5.0/kfserving_kubeflow.yaml)

Resolved in https://github.com/kubeflow/kfserving/pull/1424


event request - table 9657 "Custom Report Selection" - GetSendToEmail() - OnBeforeGetSendToEmail()

It is desirable to be able to substitute other email addresses per Customer/Vendor, instead of the Document Layout "Send To Email", particularly when clients are already using e.g. fields on the Card and don't want to have to copy or synchronise those to the Doc Layouts.
So, please add the following event, emission, and Result name to enable it:
procedure GetSendToEmail(Update: Boolean) Result: Text[250]
var
    Contact: Record Contact;
begin
    // +NEW
    OnBeforeGetSendToEmail(Result, IsHandled);

    if IsHandled then
        exit;
    // -NEW

    if "Use Email from Contact" then begin
        Contact.SetFilter("No.", GetSelectedContactsFilter());
        FillSendToEmail(Contact);

        if Update then
            Modify();
    end;

    exit("Send To Email");
end;

[IntegrationEvent(true, false)]
local procedure OnBeforeGetSendToEmail(var Result: Text[250]; var IsHandled: Boolean);

Developers could then e.g. get the Customer from the Source No., and return the email addres through some other means, whether from the Customer Card or elsewhere.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Add https://boardom.io/

https://boardom.io/

Boardom developer here. Thanks for the suggestion.

Cool site, but it doesn't work offline...

@andreasbovens good observation. I've noted that as a requirement, and will open another PR when offline support is up to par with other PWAs.

Thanks, @matthewoates! Any updates from your end?

The site is alive and well, and will be adding offline support in the coming weeks. I'll keep you all updated through this thread.


feat: allow for use of django.contrib.sites domain in password reset e-mail

See #355

Related to #357

Looks like tests are failing after merging. Can you investigate?


[Feature Request] Choose which Directory Cache and Models go to

Is it possible to choose where cached stuff goes to?
My OS Install or C: is becoming full and I ordered a dedicated external HDD for AI stuff.
For example, the models go to my user cached directory, I want everything to go to my separate HDD in a certain folder.

Yes, I'll try to document it in the readme.
Right now there are 3 locations.
Hugging Face cache
Torch Hub cache
data/models/ inside the tts-generation-webui directory
The caches are good because they are shared between installations and even
between different UIs/projects.
For HuggingFace cache, these are the instructions:
The <CACHE_DIR> is usually your user’s home directory. However, it is
customizable with the cache_dir argument on all methods, or by specifying
either HF_HOME or HUGGINGFACE_HUB_CACHE environment variable.
For Torch Hub cache:
The locations are used in the order of

Calling hub.set_dir(<PATH_TO_HUB_DIR>)
$TORCH_HOME/hub, if environment variable TORCH_HOME is set.
$XDG_CACHE_HOME/torch/hub, if environment variable XDG_CACHE_HOME is set.
~/.cache/torch/hub
Later today I can take a look at adding this inside the settings tab and
testing.
On Tue, Jul 11, 2023, 5:21 AM MiYaku Gaming @.***>
wrote:

Is it possible to choose where cached stuff goes to?
My OS Install or C: is becoming full and I ordered a dedicated external
HDD for AI stuff.
For example, the models go to my user cached directory, I want everything
to go to my separate HDD in a certain folder.
—
Reply to this email directly, view it on GitHub
https://github.com/rsxdalv/tts-generation-webui/issues/68, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTRXI5ASQWYVKP6TDGXCSLXPS2CJANCNFSM6AAAAAA2FKGZFM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Good point. The UI approach should make it easier to manage.
Also it's a small risk, though depending on how you update, you can damage
your config. Maybe I'll delay releasing this just a little bit to first
make the config future compatible.
On Tue, Jul 11, 2023, 9:19 PM MiYaku Gaming @.***>
wrote:

Thanks, I would appreciate a user interface version of this, my concern is
future updates will force me to do it over and over again because it will
just overwrite it.
—
Reply to this email directly, view it on GitHub
https://github.com/rsxdalv/tts-generation-webui/issues/68#issuecomment-1631282568,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTRXIZ6Z4RMNNTSEACXEGDXPWKLDANCNFSM6AAAAAA2FKGZFM
.
You are receiving this because you commented.Message ID:
@.***>

Hi there, I'd also like to add to this regarding RVC. Can there be a model dropdown for selecting one in data/models? This is present in audio-webui, but I like this webui a lot more since it has options for tortoise.

Yes, though I've been focusing on tutorials recently, another round of UX
improvements is planned.
On Wed, Jul 12, 2023, 8:01 PM Brian Dashore @.***>
wrote:

Hi there, I'd also like to add to this regarding RVC. Can there be a model
dropdown for selecting one from data/models? This is present in
audio-webui, but I like this webui a lot more since it has options for
tortoise.
—
Reply to this email directly, view it on GitHub
https://github.com/rsxdalv/tts-generation-webui/issues/68#issuecomment-1632895702,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTRXI5NYBD3MJUB2UWS4TDXP3J4XANCNFSM6AAAAAA2FKGZFM
.
You are receiving this because you commented.Message ID:
@.***>

Hi there, I'd also like to add to this regarding RVC. Can there be a model dropdown for selecting one from data/models? This is present in audio-webui, but I like this webui a lot more since it has options for tortoise.

https://github.com/rsxdalv/tts-generation-webui/pull/77

Added in https://github.com/rsxdalv/tts-generation-webui/pull/90

I have tried setting the paths in the Settings tab and applying the changes after a restart, but it never changes anything.
I have my cache and everything in a separate External HDD because I run out of space in my user folder and tried changing the directories to the External HDD.
I still get downloads for my user directory .cache.
How do I do this?

Latest update: https://github.com/rsxdalv/tts-generation-webui/commit/a65307efa55a96c00860a36f4730b2e40bd55775

Closing as completed. Please reopen the issue if the issue persists.


Redux-Saga

Hello, I would like to propose talk about Redux-Saga.
Talk would cover explanations on how Saga and Thunk work and their differences.

Sounds awesome! We will do that in june :1st_place_medal:

sounds good!


disable Fedora 27 per #1204

disable Fedora 27 per #1204

Coverage remained the same at 77.192% when pulling 8f24dc8d54db092ddcc6746c7b1cb26be6797f95 on crd477:pr1204 into e20d5191d9e19076487d69f8ac6cc6d60bd96a69 on cmu-db:master.

@crd477 @pervazea
Does this PR requires review or I can just merge it? Cause I take a look at the code, it seems like you simply comment out Fedora build in Jenkins file.
Thanks!

You can just merge it.


maskrcnn model implementation

hi @wanliuhuo, can you please:
1- complete the changes and upload to this PR?
2- resolve conflicts & rebase with rafiki latest version's master branch?

hi @wanliuhuo, can you please:
1- complete the changes and upload to this PR?
2- resolve conflicts & rebase with rafiki latest version's master branch?

hi @wanliuhuo, can you please:
1- complete the changes and upload to this PR?
2- resolve conflicts & rebase with rafiki latest version's master branch?

Rafiki has changed several versions, there are some new conflict and bugs now, recently, I am working on it to solve these conflict.


changes made

Because

This PR

Issue

Closes #XXXXX
Additional Information

Pull Request Requirements

[ ] I have thoroughly read and understand The Odin Project Contributing Guide
[ ] The title of this PR follows the location of change: brief description of change format, e.g. 01-flex-center: Update self check
[ ] The Because section summarizes the reason for this PR
[ ] The This PR section has a bullet point list describing the changes in this PR
[ ] If this PR addresses an open issue, it is linked in the Issue section
[ ] If applicable, I have ensured that the TOP solution files match the Desired Outcome image

Thanks for taking the time to make this PR, but we don't want to merge solutions into this repo, so I will be closing it.


[sources/parsley] Update parsley source to generate fake GPS messages for testing

Feature Description

Expected implementation date: 2024-11-9
As a: DAQ operator during a test,
I would want to: generate fake GPS CAN messages from the parsley source.
Because: fake GPS CAN messages are needed for testing.

Related Links
 #265
Details
Note that the original fake messages have been removed as they are outdated. In a future feature request new fake messages should be added to the parsley source.
Note that this feature will only work once a small change to the parsley repo has been made to support the new CAN 2.0 format (I will make a PR for this)

Requirements
Specific Requirements

Generated GPS messages MUST comply with CAN Bus 2.0 format.
For longitude/latitude, generated coordinates MUST lie within the general Waterloo region.
The timestamp MUST wrap around once it exceeds the maximum 3 bytes.

Standard Requirements - Do Not Modify Without Approval

All changes made MUST be tested and reviewed by a code reviewer.
The conditions outlined in CONTRIBUTING.MD MUST be respected.
Deep consider of new library dependencies MUST be made before adding them to the project.
Keep the codebase clean, don't push non-code files (e.g. DATA, VirtualEnv, etc.) to the repository.
All new feature changes made SHOULD have associated unit tests (if applicable)
Keep well-documented code, and follow the style guide.

Satisfying the above requirements WILL close this issue.
Stakeholder / Product Owner
Testing / DAQ

@EmpiricalCode I think the fake GPS data is actually going to be used by software dev people to test GPS functionality and NOT for DAQ people, as DAQ doesn't need fake GPS coordinates since it will get them from real parsley, @zangjiucheng can you confirm?

but also yay fake GPS data!! 😎 🎉🎉 🎉 🎉

Yep, you are right :)) This is for software team easier for UI development but don't need to download large dataset. DAQ system they don't need to care with this.

It not a big deal, not mandatory require to change the issue description, but just clarify.

Got it, will leave as "Software Team"


journeycard persistent storage

Add persistent storage to journeycard memory.
When reviewing be sure to expand the renamed file journey_card_manager.go
Also deal with user switching. By throwing out the JourneyCardManagerSingleUser instance on logout and whenever a different uid comes in. The switching layer looks a bit weird, but also seems simpler than merging multi-user checks into the rest of the code. Fundamentally journeycard book-keeping is a single user thing.
I think the same is true for most modules in ChatContext.
cc @mmaxim

These look like flakes. TestTeamMetadataUpdateNotifications passes locally.
    teams_test.go:1960:
        	Error Trace:	teams_test.go:1960
        	Error:      	Received unexpected error:
        	            	hidden team loader error: seed check at generation 2 wasn't found
        	Test:       	TestTeamMetadataUpdateNotifications
    test_logger.go:56: TEST FAILED: TestTeamMetadataUpdateNotifications

+ ./kbfs_test_fuse.test -test.timeout 15m
panic: test timed out after 15m0s


bug(ci): Build issue with pnpm v8 due to incompatible lock file

Problem: The build is breaking because the current pnpm lock file is not supported with pnpm v8.
You may manually pin the pnpm version to v7 temporarily if the build is urgent, but ideally, the existing lock file should be deleted and regenerated.
Discussion, with multiple solutions here: https://github.com/pnpm/pnpm/issues/6307

Hi @santoshyadavdev I just noticed that with #49 you have tried to downgrade the lock file from 5.4 to 5.3 instead, which could be because you may be using pnpm v7.x locally.
On Netlify, the pnpm version being used is v8, as per the public logs, so you need to install v8 locally and upgrade the lock file as a long-term fix and a short-term fix is to pin the pnpm version to v7 in Netlify manually.
I had to do this recently for my own Astro pnpm project, though my issue for the same was with Cloudflare Pages.


pipeline functions use die

This is a stdlib function, and luaposix doesn't require stdlib. Presumably this should be error instead?

agreed


ValueError problem

When I input the folder which is full of binvox format files as input paths,
The when run the code train.py
The system show that:
ValueError: Tried to convert 'reduction_indices' to a tensor and failed. Error: Argument must be a dense tensor: range(0, 1) - got shape [1], but wanted [].
I tried a lot times I have not deal with it

Hi, Qudagang
This is Python3 compatibility issue. I found solution here:
https://github.com/tensorflow/models/issues/3705#issuecomment-375563179
But, a faster way to deal with this problem is to use Python2.


Cellebrite (macos) stale url

The cellebrite inspector image url is stale: https://archive.org/download/cellebrite-inspector-10.3-mac/Cellebrite_Inspector_10.3_Mac.pkg
I haven't been able to find an alternative image

Hi, I will update the code once I discover a working link for Inspector installer… But for now I would recommend either running this on Windows, or modify the Linux part of install.sh, which relies on wine translation layer to run the Windows dll - there is no reason why the same should not run on macOS, with the right commands. I am just hesitant to default to this method for macOS, since there is a native library out there...

@jankais3r Would it be possible to share the PhotoDNAx64.so? From my understanding, that's the only thing needed from Cellebrite Inspector for pyPhotoDNA to work.


Show futbin price on the pack opening page

headline

Currently unable to test, I need to access the game on the console before I get access to the FUT Web App transfer market again, but I didn't buy the game (yet). If someone can provide me with a test account I'm happy to look at this.

+1
There are also a few places that need the futbin price for players to re render. Maybe need to look at some sort of caching.

And it would be nice also on search players results page


Always detecting ReachableViaWiFi 'TRUE' in iOS 11

Method [Reachability reachabilityForLocalWiFi] is returning ReachableViaWiFi all the time, No matter whether wifi is connected or not.
I am facing this issue is only on iOS 11.

@tonymillion  Does this library support iOS 11 ??

@siddharthsuneel not anymore. Take a look: https://developer.apple.com/library/content/samplecode/Reachability/Listings/ReadMe_md.html

I using Xcode test is your situation, but normally open is great

Are you link the cable with device?
If so,  pull off the cable then try again : )


Modify Kong Access log format

Problem statement - We are using Kong and by default, Kong access logs comes in a specified format (defined in ngx_http_log_module module) like :

http {
#main log format
log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log;
}

Now I need to define a custom log format for the access logs. So, I did the following steps:
My Approach -

Define nginx-custom.template file with custom log format.

Add COPY ./data/nginx-custom.template /usr/local/kong/nginx-custom.template line in the docker file (which builds the kong image)

Update docker-entrypoint.sh file with a new argument(--nginx-conf) and value as "/usr/local/kong/nginx-custom.template"  to the kong prepare command.

kong prepare -p "/usr/local/kong" --nginx-conf "/usr/local/kong/nginx-custom.template"

While running Kong container, I get the following error:

Just want to check, what I am missing or doing wrong to fulfil my requirement ?

Hi,
You probably need the following line:
events {}

Before the http { section in your nginx-custom.template file. If that's not enough, please include the (anonymized) file.

Thanks Kikito...😊yes initially I was facing the same issue which u said. But then I was not passing the custom log format name in Kong access log environment in container definition.


Settings: User notes

Description
It would be great if we would be able to "add a user note" to settings UI so they can write down "Why they set it to the value" or something similar.
[cuID:PYPE-1384]

It would be great to have this.
Copy pasting sections of settings from other projects works nicely, but some presets would be really cool.
For example writing down all the Nuke color settings is quite difficult, having Aces and "nuke classic" presets to pick from would make it much easier for new users.

Copy pasting sections of settings from other projects works nicely, but some presets would be really cool.

this is actually a major feature on the backlog, that I can't quite find in the issues here. Will make it with a proposal that we talked about internally before


sco acquistion failure not handled

Sometimes, when a client opens a sco pcm for playback on an AG instance, transport acquisition can fail. This failure is ignored by the sco io thread, so the client becomes blocked writing to a full pipe that the server never reads from. At the very least, the client pcm should be closed when no transport can be acquired (the a2dp code does this).
I can trigger this by first starting an a2dp playback client, then starting a sco playback client to the same device (using bluealsa -p a2dp-source -p hfp-ag). Once this has happened with my device, all future sco attempts fail, even after the a2dp transport has been released. Disconnecting the device then reconnecting restores normal function.

I'm unable to reproduce the acquisition failure today. The connect() call was failing with ECONNABORTED which bluez maps from HCI error 0x16 "Connection terminated by local host", but whatever was causing it has corrected itself now :(
I think the issue is still valid, but just very hard to deliberately trigger.

I think that this issue is real. Sometimes, I've also experienced such behavior.... It was when I was mostly focused on HFP - I've run a lot of "tests". And I remember that from time to time bluealsa server got stuck until BT device reconnection or what worst bluealsa server restart.... I will look at this, but rather in a distant future :|


CAMEL-20095: add langchain4j-embeddings component

Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

@lburgazzoli I opened this one, as there were some commits that I squasjed already https://github.com/zbendhiba/camel/pull/5
Can you check this was your only commit ?

looks like it is


[typescript] Please export the type of a Resolvable

Hello WhiteAutumn, kudos for this great module. Today I found myself having to type an object with a Resolvable field in it. I did
import { Resolvable as ResolvableType } from 'resolvable-promise/dist/types';    // CHEATING!

type MyType = {
      isItdoneAlready: ResolvableType<void>;
};

I am admittedly not a black belt in TypeScript yet, so perhaps there already exists a way to achieve this without cheating?
If so, kindly add it to the documentation. If not, please re-export that type somehow.
Thanks in advance!

perhaps there already exists a way to achieve this without cheating?

No, unfortunately not as it stands. I agree this is cumbersome, but unfortunately it is not as simple as adding the type export. In my effort to make the package compatible with both esm and commonjs this was the compromise I decided to make.
However, that was then! Think I have an idea on how to get the type exported properly and have been thinking of rewriting this package for a while.

Version 3.0.0 has been released @domq
With this version it's possible to use the imported Resolvable as a type on its own!
Here's an example:
import Resolvable from "resolvable-promise";

let resolvable: Resolvable<number>;
resolvable = new Resolvable();

resolvable.then(num => console.log(`${num} + ${num} = ${num + num}`));
resolvable.resolve(10);

10 + 10 = 20

Apologies for not giving any news earlier, I was busy with a variety of Chinese fire drills last week, but I just got around to testing your new release. It works flawlessly! Thank you so much!


add copy-aria

see docs

some aria properties should never be applied together. need to address that (preferably with a validator)
aria attributes should be white-listed into the root element per component configuration

need better definition of which attributes to copy, when to warn / throw etc.
@giladgrush

Currently please copy the following: aria-label, aria-labelledby, aria-describedby. There is no need for any safeguards.

@giladgrush can this be merged into the root function instead of having it in a separate feature?

Yes
On Wed, Aug 23, 2017 at 11:16 AM, Amir Arad<EMAIL_ADDRESS>wrote:

@giladgrush https://github.com/giladgrush can this be merged into the
root function instead of having it in a separate feature?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wix/wix-react-tools/issues/32#issuecomment-324256227,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASSzr1vxChXO3UhGFo6Vnqk2_ac4fSSkks5sa9_agaJpZM4OS4Je
.

--
Gilad Grushka
Product Manager - Core3
40 Namal St. Tel Aviv Israel 63506
http://www.wix.com


Implement new messages structure

Messages should be structured this way:
message_topic: uint8_t describing the message
data_type: uint8_t describing length and type
data_value: variable length and type
That's would mean changing how the protocol works. See #4.

The data_type corresponds to the type and length (uint8, 16, 32, 64, int8, 16, 32, 64, float, double, string)

This has totally been superseded by the use of Nanopb.