Cross compiling SampleApp error

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

Hi AVS Team,
An error occurred while compiling sdk via setup.sh. Please help me solve this problem. Thank you. The log is as follows,
jerome@Jerome:~/work$ ./setup.sh config.json -a androidConfig.txt
= ANDROID_HOME:         /home/jerome/Android
= ANDROID_NDK:          /home/jerome/Android/ndk/ndk-bundle/android-ndk-r16
= CMAKE_TOOLCHAIN_FILE: /home/jerome/Android/ndk/ndk-bundle/android-ndk-r16/build/cmake/android.toolchain.cmake
= CXX:                  /home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/bin/arm-linux-androideabi-clang++
= READELF:              /home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/bin/arm-linux-androideabi-readelf
= STRIP:                /home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/bin/arm-linux-androideabi-strip
= SYSROOT:              /home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/sysroot
= TOOLCHAIN:            /home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22
= TOOLCHAIN_HOST:       arm-linux-androideabi
= INSTALL_PATH:         /home/jerome/work/debug/android-22/armeabi-v7a/install
= DEVICE_INSTALL_PATH:  /data/alexa
################################################################################
################################################################################
AVS Device SDK Android Script - Terms and Agreements
The AVS Device SDK is dependent on several third-party libraries, environments,
and/or other software packages that are installed using this script from
third-party sources ("External Dependencies"). These are terms and conditions
associated with the External Dependencies
(available at https://github.com/alexa/avs-device-sdk/wiki/Dependencies) that
you need to agree to abide by if you choose to install the External Dependencies.
If you do not agree with every term and condition associated with the External
Dependencies, enter "QUIT" in the command line when prompted by the installer.
Else enter "AGREE".
################################################################################
################################################################################
-- The CXX compiler identification is Clang 5.0.300080
-- Check for working CXX compiler: /home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/bin/arm-linux-androideabi-clang++
-- Check for working CXX compiler: /home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/bin/arm-linux-androideabi-clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Creating the build directory for the AlexaClientSDK with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/CMakeLists.txt:3 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/googlemock/CMakeLists.txt:40 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/googletest/CMakeLists.txt:47 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ACL with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ADSL with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the AFML with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the DeviceSettings with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the BluetoothImplementations with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the EqualizerImplementations with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the CertifiedSender with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ContextManager with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the CapabilitiesDelegate with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the PlaylistParser with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the CapabilityAgents with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the AIP with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Alerts with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the AudioPlayer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Bluetooth with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the DoNotDisturbCA with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Equalizer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ExternalMediaPlayer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the InteractionModel with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the MRM with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the Notifications with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the SpeakerManager with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the SpeechSynthesizer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Integration with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Please fill /home/jerome/work/build/Integration/AlexaClientSDKConfig.json before you execute integration tests.
Skipping build of NetworkIntegrationTests.cpp.
Creating the build directory for the ApplicationUtilities with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the DefaultClient with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the AndroidUtilities with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the AndroidSLESMediaPlayer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ESP with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the RegistrationManager with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Authorization with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the CBLAuthDelegate with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the SampleApp with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Storage with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
Creating the build directory for the SQLiteStorage with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Bluetooth implementation not supported
WARNING: Unknown android device installation path. To run unit tests, you'll need to upload the tests to the device.
Including FFmpeg libraries
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
FATALDoxygen is required to generate documentation.
-- Configuring done
-- Generating done
-- Build files have been written to: /home/jerome/work/build
[ 32%] Built target AVSCommon
[ 32%] Built target SQLiteStorage
[ 32%] Linking CXX shared library libACL.so
[ 34%] Built target ADSL
[ 39%] Built target ACL
[ 41%] Built target AFML
[ 41%] Built target RegistrationManager
[ 44%] Built target EqualizerImplementations
[ 44%] Built target ContextManager
[ 44%] Linking CXX shared library libCapabilitiesDelegate.so
[ 46%] Built target PlaylistParser
[ 48%] Built target CapabilitiesDelegate
[ 48%] Built target SpeechEncoder
[ 51%] Built target AudioResources
[ 51%] Built target AudioPlayer
[ 53%] Built target Bluetooth
[ 55%] Built target Equalizer
[ 58%] Built target ExternalMediaPlayer
Scanning dependencies of target Notifications
[ 58%] Built target InteractionModel
[ 60%] Built target PlaybackController
[ 60%] Built target SpeakerManager
[ 62%] Building CXX object CapabilityAgents/Notifications/src/CMakeFiles/Notifications.dir/NotificationIndicator.cpp.o
[ 65%] Built target SpeechSynthesizer
[ 67%] Linking CXX shared library libAVSSystem.so
[ 69%] Built target AVSSystem
[ 69%] Building CXX object CapabilityAgents/Notifications/src/CMakeFiles/Notifications.dir/NotificationRenderer.cpp.o
[ 69%] Building CXX object CapabilityAgents/Notifications/src/CMakeFiles/Notifications.dir/NotificationsCapabilityAgent.cpp.o
[ 72%] Built target TemplateRuntime
[ 74%] Built target AndroidUtilities
[ 74%] Linking CXX shared library libCBLAuthDelegate.so
[ 74%] Built target CBLAuthDelegate
Scanning dependencies of target CertifiedSender
[ 74%] Building CXX object CertifiedSender/src/CMakeFiles/CertifiedSender.dir/CertifiedSender.cpp.o
[ 74%] Building CXX object CapabilityAgents/Notifications/src/CMakeFiles/Notifications.dir/SQLiteNotificationsStorage.cpp.o
[ 74%] Linking CXX shared library libNotifications.so
[ 74%] Building CXX object CertifiedSender/src/CMakeFiles/CertifiedSender.dir/SQLiteMessageStorage.cpp.o
[ 74%] Built target Notifications
Scanning dependencies of target AIP
[ 74%] Building CXX object CapabilityAgents/AIP/src/CMakeFiles/AIP.dir/AudioInputProcessor.cpp.o
[ 76%] Linking CXX shared library libCertifiedSender.so
[ 76%] Built target CertifiedSender
[ 81%] Built target AndroidSLESMediaPlayer
[ 83%] Building CXX object CapabilityAgents/AIP/src/CMakeFiles/AIP.dir/ESPData.cpp.o
Scanning dependencies of target DeviceSettings
[ 83%] Building CXX object Settings/src/CMakeFiles/DeviceSettings.dir/Storage/SQLiteDeviceSettingStorage.cpp.o
[ 83%] Linking CXX shared library libDeviceSettings.so
[ 83%] Built target DeviceSettings
Scanning dependencies of target Alerts
[ 83%] Linking CXX shared library libAIP.so
[ 83%] Built target AIP
Scanning dependencies of target DoNotDisturbCA
[ 83%] Building CXX object CapabilityAgents/Alerts/src/CMakeFiles/Alerts.dir/Renderer/Renderer.cpp.o
[ 83%] Building CXX object CapabilityAgents/DoNotDisturb/src/CMakeFiles/DoNotDisturbCA.dir/DNDMessageRequest.cpp.o
[ 83%] Building CXX object CapabilityAgents/DoNotDisturb/src/CMakeFiles/DoNotDisturbCA.dir/DNDSettingProtocol.cpp.o
[ 86%] Building CXX object CapabilityAgents/Alerts/src/CMakeFiles/Alerts.dir/Storage/SQLiteAlertStorage.cpp.o
[ 86%] Building CXX object CapabilityAgents/DoNotDisturb/src/CMakeFiles/DoNotDisturbCA.dir/DoNotDisturbCapabilityAgent.cpp.o
[ 86%] Building CXX object CapabilityAgents/Alerts/src/CMakeFiles/Alerts.dir/Alarm.cpp.o
[ 86%] Building CXX object CapabilityAgents/Alerts/src/CMakeFiles/Alerts.dir/Alert.cpp.o
[ 88%] Linking CXX shared library libDoNotDisturbCA.so
[ 88%] Built target DoNotDisturbCA
Scanning dependencies of target Settings
[ 88%] Building CXX object CapabilityAgents/Alerts/src/CMakeFiles/Alerts.dir/AlertsCapabilityAgent.cpp.o
[ 90%] Building CXX object CapabilityAgents/Settings/src/CMakeFiles/Settings.dir/Settings.cpp.o
[ 90%] Building CXX object CapabilityAgents/Settings/src/CMakeFiles/Settings.dir/SettingsUpdatedEventSender.cpp.o
[ 90%] Building CXX object CapabilityAgents/Alerts/src/CMakeFiles/Alerts.dir/AlertScheduler.cpp.o
[ 90%] Building CXX object CapabilityAgents/Settings/src/CMakeFiles/Settings.dir/SQLiteSettingStorage.cpp.o
[ 90%] Linking CXX shared library libSettings.so
[ 90%] Built target Settings
[ 93%] Building CXX object CapabilityAgents/Alerts/src/CMakeFiles/Alerts.dir/Reminder.cpp.o
[ 93%] Building CXX object CapabilityAgents/Alerts/src/CMakeFiles/Alerts.dir/Timer.cpp.o
Scanning dependencies of target ESP
[ 93%] Linking CXX shared library libAlerts.so
[ 93%] Building CXX object ESP/src/CMakeFiles/ESP.dir/DummyESPDataProvider.cpp.o
[ 93%] Built target Alerts
Scanning dependencies of target DefaultClient
[ 93%] Linking CXX shared library libESP.so
[ 93%] Built target ESP
[ 93%] Building CXX object ApplicationUtilities/DefaultClient/src/CMakeFiles/DefaultClient.dir/DefaultClient.cpp.o
[ 95%] Building CXX object ApplicationUtilities/DefaultClient/src/CMakeFiles/DefaultClient.dir/EqualizerRuntimeSetup.cpp.o
[ 95%] Linking CXX shared library libDefaultClient.so
[ 95%] Built target DefaultClient
Scanning dependencies of target SampleApp
[ 95%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/ConnectionObserver.cpp.o
[ 95%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/ConsolePrinter.cpp.o
[ 95%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/ConsoleReader.cpp.o
[ 97%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/GuiRenderer.cpp.o
[ 97%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/InteractionManager.cpp.o
[ 97%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/KeywordObserver.cpp.o
[ 97%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/UIManager.cpp.o
[ 97%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/UserInputManager.cpp.o
[100%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/SampleApplication.cpp.o
[100%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/SampleEqualizerModeController.cpp.o
[100%] Building CXX object SampleApp/src/CMakeFiles/SampleApp.dir/main.cpp.o
[100%] Linking CXX executable SampleApp
/home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lrt
/home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lpthread
/home/jerome/Android/ndk/toolchains/android-ndk-r16/toolchain-armeabi-v7a/android-22/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lasound
clang50++: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [SampleApp/src/SampleApp] Error 1
make[2]: *** [SampleApp/src/CMakeFiles/SampleApp.dir/all] Error 2
make[1]: *** [SampleApp/src/CMakeFiles/SampleApp.dir/rule] Error 2
What is the expected behavior?

What behavior are you observing?

Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:

What version of the AVS Device SDK are you using?
  <1.12.0>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[x] Other - tell us more:

Tell us about your OS (Type & version):

[x] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @ANDROIDTODO thanks for bringing this to our attention. From the linker error you posted it looks like lpthread and lasound might not be installed. Could you run the following commands to install them explicitly:
sudo apt-get install libpthread-stubs0-dev
sudo apt-get install libasound2
Let us know if this fixed the linking issue.

Hi @ANDROIDTODO,
The android build should not be trying to link against any of the libraries listed above. It could be that CMAKE_SYSTEM_NAME is not being set correctly. Can you  remove this target_link_libraries statement from here and try again?
Note that we only support Android 23 and above.
Thanks

I am closing this issue due to inactivity. Please feel free to re-open it if it has been closed in error.


📖 Fix links recently broken

Summary
This PR fixes some links between documents that were broken by recent re-orgs.
Preview at https://mikespreitzer.github.io/kcp-edge-mc/doc-fixlinx-628a/readme/
Related issue(s)
Fixes #

/cc @KPRoche
/cc @francostellari
/cc @ezrasilvera
/cc @clubanderson

/lgtm
/approve


Feature: ability to change defaults

I would like to have "backend" and "frontend" set for all widgets. Would be nice to set it up once for as default for all.
Currently I think it is only possible to change each widget/instance separately.

Hi @spinus.
Sorry for the long wait and the lack of response during the holiday period. :/
I have been working on that in the past weeks.
It should be here in the next version.
Would you be interested in testing some sort of prerelease to give me some feedback?
I still need to work on the documentation and testing but next version should add:
Default config
stqdm.set_default_config(frontend=True) # but it should work with any stqdm or tqdm kwargs

Config scopes
with stqdm.scope(bar_format="{bar}{desc}":
   # my code using stqdm

Moreover, I am looking for feedback on the way it works:

does it feel good?
does autocompletion / typing works?
would it be better to use a config dict instead of **kwargs?

I would appreciate your help if you would like to.


Mobile Responsive Reset password Page

https://college-reboot.vercel.app/reset

@dineshigdd  would you like to work on this issue?

yes...sure I think I forgot to test it for mobiles

made a new PR

Would like to work on it

Shall I work on this issue? @Ayushpanditmoto

Add left right margin

Make sure you work on beta branch

I am Closing this issue as this issue is fixed


Why is _____ happening?

What's the problem you are having while you are using C-REAL?
i dont know what the token is
Have you checked the errors in the console?
Yes or no yes

have you watch the video tutorial?


user-guide: add more links to the .dvcignore guide from other docs. Subtask one completed

Subtask :

Definitely in the description of https://dvc.org/doc/command-reference/add, and maybe add an > example (not sure) which could be copied from these.

of issue #1033 completed.

Please link this PR to the issue it addresses. See https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue

Or if this only addresses a specific checkbox (subtask) and doesn't close the entire issue still link to the issue without a special word and copy-paste the checkbox  text that is being addressed into a quote in this PR's description. Thanks

Fixes #1033 .

The word fixes is a special word that should only be used if the PR intends to close that issue. Is that the intention here? Or is it just to address one particular subtask? Sorry for the back and forth here but this is important GH collaboration logistics.

Added example script also to support my statement.

OK I see the statement and the example are just appended at the end of the document. Please understand the structure of the doc: the explanation should probably go in the Description section, and the example should be a new section i.e. have it's own H2 header. They don't have to be next to each other.
Thanks

Hi. I still see the description claims this PR totally fixes the underlying issue but it's only for a subtask so again, please don't use that special word that causes the issue to be closed if this gets merged:

The 2nd checkbox here is still not addressed: https://github.com/iterative/dvc.org/pull/1346#issuecomment-633282712

*I meant from Github

@jorgeorpinel  I have addressed https://github.com/iterative/dvc.org/pull/1346#issuecomment-633282712 in a possible way.
Also

To avoid tracking a file or directory, just add the corresponding patterns in a .dvcignore file.

what if this is modified to

To avoid tracking a file or directory, just add the corresponding patterns in a .dvcignore file and that won't get tracked by dvc add.

Thanks @sarthakforwet ! This is done.


Fix eeglab.py, an error for read annotations in RawEEGLab

In io.eeglab.RawEEGLab, read annotations should also pass argument uint16_codec.
Reference issue
This problem has been reported in the group, click link for details:
https://mne.discourse.group/t/bug-report-an-error-in-io-eeglab-and-solution-to-it/7173
What does this implement/fix?
Merely by passing the correct codec argument to function call.
Additional information
No

@frostime can you merge the upstream main branch here so the CI can be green and we could merge?
thanks a lot for taking the time @frostime

@frostime can you merge the upstream main branch here so the CI can be green and we could merge?
thanks a lot for taking the time @frostime

Hello, I'm a bit confused cause I've sync to the main branch before launching this pr,  what do you mean by saying "merge the upstream main branch here"?

Oh no, I add new commits to re launch the ci, but it seems that there still some error.

Mr. @agramfort , if this pr bother you too much, I think you can merely close this pr, and make changes at your branch.
The only changes in this pr is merely add uint16_codec parameter to read_annotations

@frostime can you update doc/changes/latest.inc using :newcontrib: and add a URL to doc/changes/names.inc? Or alternatively let us know what name/URL you prefer to use to get credit for your change and we can push a quick commit to do it then merge, thanks!

@frostime can you update doc/changes/latest.inc using :newcontrib: and add a URL to doc/changes/names.inc? Or alternatively let us know what name/URL you prefer to use to get credit for your change and we can push a quick commit to do it then merge, thanks!

Hello, sorry that I'm not familiar with the mne dev pipeline and don't know what is :newcontrib:.
It would be nice of you if you could help me to fill the required information, shown as follow:

My names: Yiping Zuo
My url: https://github.com/frostime

Appreciate your dedication, thanks! 👍

sorry @larsoner I enabled auto-merge without requesting changelog entry. @frostime I'll do the changelog in another PR.


Saving firing remove event before update event

What happened
Saving fires a remove event before subsequent save fires an update event
What I expected to happen
Saving fires only an update event
Steps to reproduce

run theme watch -n .tk_update
make changes to a theme file and save
output reads [development] Received Remove event on <your-file>.liquid
save again
output reads [development] Received Update event on <your-file>.liquid

My Environment
OS (including version): OSX Sierra
Themekit version:  0.7.5
Ignore Files(if any):

package.json
yarn.lock
README.md

Relates to #168 and #188

What editor are you using?

I'm using vim

I've confirmed that the bug I've reported doesn't happen when running in Atom or text edit (that's all I have to test on)

I can confirm the same problem on my end, also using vim. It doesn't happen on Sublime Text.

What is your vim version? I am wondering if a new update to Vim causes it to swap files slower.

I'm using nvim. Problem seems to be related to the saving strategy.
Using :set backupcopy=yes seems to fix the problem on all files except *.scss files.

Yes, vim has this problem because of the way it uses swap files. In the past I tweaked the debouncing of events to make sure that the remove event doesn't happen.

@wiznia @colindresj Please upgrade to v0.8.0 and try to reproduce this. I am running vim 8.1 and not having these issues, with or without backupcopy. If you are still having issues, it may be a plugin so please start vim without any config using vim --clean <filename> and see if the problem still persists. Thank you!

I am closing this because I believe this has been fixed in the newest version with updates to the file watcher. Please re-open if this is not the case.


feat(typography): Improve typography demo

Separate typography section into several sections for better demo code readability. Close #291
Fix incorrect sizing of dc-h3. Close #289

@gabrielhl Looks good. But can you open another issue for the "separate typography" changes and add the issue number to your initial comment?

@gregdeane Like this?

@gabrielhl yep. thx!

👍


Feature: Input Details component

Summary
Code changes to display the content from DApp outputs (Notices/Reports/Vouchers) that we are calling InputDetails.
Other changes:

Added Vitest and @testing-library to the UI package
Made all the requested changes from Prettier + Eslint to have a clean slate (that is way 43 changes)
Added story + test cases for the UI components, including the InputDetails.
Add a GitHub action to run lint and formatting checks including the initial couple of tests added.

@tuler,
I wondering if we could merge that PR. When I added the GitHub Action, I went through the rabbit hole of fixing all the prettier + Eslint requests to have a clean slate, but currently, that means 43 files were changed. 🫠


Issue with JSON Object and arrays

Dear Indri Muska,
I was trying with your API example as given below....
$scope.remoteConfig = {
url: "http://services.groupkt.com/country/search",
transformResponse: function (data) {
console.log(typeof data);
// var str = data;
// var json = JSON.stringify(eval("{"+"tags:" + str + "}"));
// var myJsonString = JSON.stringify(yourArray);
// var catcher = JSON.stringify(data);
// var catcher = JSON.stringify({data});
var catcher = {
'tags': JSON.parse(data)
};
console.log(typeof catcher);
var countries = angular.fromJson(data).RestResponse.result;
return countries.map(function (country) {
return {
name: country.name,
code: country.alpha2_code
};
});
}
};
However, I could not maniputate the array with catcher, which is a JSON object converted from an JSON array.
Is it necessary that we need to convert the JSON array to JSON Object?
The code pasted above is giving me errors...
Thanks.
Regards,
Vivek Elayidom

Hi @mdrift-central,
I don't understand why you're saying that is necessary to convert the JSON array to a JSON object, which object/array are you talking about? I can't see any error with the code you posted.
However, if you want to manipulate the result array data with any of your functions (catcher) you simply have to parse the data parsed from a JSON string:
transformResponse: function (string) {
  // parse JSON string -- similar to JSON.parse
  var myData = angular.fromJson(data);
  // manipulate your data
  var result = myData.RestResponse.result;
  var countries = result.map(function (country) {
    return { name: country.name, code: country.alpha2_code };
  });
  // apply other functions
  // ...
  // return countries array
  return countries;
}

Thanks Indri Muska,
Your suggestion helped me a lot... Thanks and keep up the good work...
So far, I found your library the best for tagging..
All the very best.
Regards,
Vivek

Also, how do I call multiple RemoteConfig functions? Any suggestions?

Glad to see you've solved your issue. :smile:
With "multiple RemoteConfig functions", do you mean a kind of dynamic transformation callback for your ajax responses? If so, remember that the remoteConfig property is the same object passed to the native Angular $http service (docs here), so you can use any valid options the service have.


Very laggy AllProjectAssetsReferencesWindow

I ran the analysis and I got 874 unused assets:

I have a quite powerful CPU but it can't handle this list of fields :)
I'm getting like 1 FPS or less with this window
Profiler shows strange things. I don't use FMOD but it's here o_O.

In other frames, spikes go from UIElements, etc

That happens due to the nature of Unity Editor GUI when it comes to rendering such large lists.
Some folks use something like loop/wrap/dynamic lists for such tasks but I think that is too much for such a plugin.
So I have added pagination in this commit 47ae2ec6dd7a4c5698b59c0ed3fd0c95e1c33232
It will allow you to render 50 items at a moment (the number is customizable)


rxjs EISDIR: illegal operation on a directory, read

⚠ IMPORTANT ⚠ Please do not ignore this template. If you do, your issue will be closed immediately.

[X] Read the docs.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] This is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Describe the bug
rxjs EISDIR: illegal operation on a directory, read
A clear and concise description of what the bug is.
importing rxjs and use it cause EISDIR: illegal operation on a directory, read

Reproduction

yarn add rxjs tslib vite
create index.html

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Document</title>
</head>
<body>
  <script type="module" src="./index.ts"></script>
</body>
</html>

create index.ts

import { of } from 'rxjs'

of([ 'Hello' ])
  .subscribe(data => console.log(data))

Please provide a link to a repo that can reproduce the problem you ran into.
Please see Steps above.
A reproduction is required unless you are absolutely sure that the the problem is obvious and the information you provided is enough for us to understand what the problem is. If a report has only vague description (e.g. just a generic error message) and has no reproduction, it will receive "need reproduction" label. If no reproduction is provided after 3 days, it will be auto-closed.
System Info

vite version: 2.0.5
Operating System: MacOS
Node version: 14
Package manager (npm/yarn/pnpm) and version: yarn 1.22.4

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.
io

I have another issue with Rx via esm

<EMAIL_ADDRESS>(HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE)

I got the same bug, really annoying

@matias-capeletto @antfu @yyx990803
If this bug is real / havn't checked, this issue may be bumped up in prio to p3-downstream-blocker, p4-important or even p5-urgent

I can't reproduce this issue.

@aelbore could you create a minimal reproduction in github with the latest Vite version so it is easier for others to look at this?

@patak-js upgrading to latest version of vite fixed the issue we can close this one, many thanks

@aelbore the error is still there with vite-2.1.5, why close it?
https://user-images.githubusercontent.com/1595209/110825418-0e88e780-82a5-11eb-9b0d-cd1ddfff258d.png

@transtone It's obviously a different error than the original post. Please open a new issue with proper reproduction.

I have another issue with Rx via esm

<EMAIL_ADDRESS>(HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE)

@sodatea thx.
use import { of } from 'rxjs/internal/observable/of' can avoid this.

设置 "@": path.resolve(__dirname, "src") 会出现此问题

是有文件不存在，导致出现此问题，我的是这样解决的


Typo "|delta_store_hobt_id|bigint|"→"|delta_store_hobt_id|big…

…int|"
https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-column-store-row-groups-transact-sql?view=sql-server-ver15

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks @hyoshioka0128.

Looks good; thanks @hyoshioka0128.


Update go-redis to v7.2.0

Please update go-redis to v7.2.0.
With v6.15.6 I see following errors when trying to read from a Redis stream:
{"@timestamp":"2020-05-20T18:24:36+01:00","@service":"benthos","level":"INFO","component":"benthos.input","message":"Receiving messages from Redis streams: [tst_messages]"}
{"@timestamp":"2020-05-20T18:24:36+01:00","@service":"benthos","level":"ERROR","component":"benthos.input","message":"Error from redis: redis: can't parse array reply: \"$15\""}
{"@timestamp":"2020-05-20T18:24:36+01:00","@service":"benthos","level":"INFO","component":"benthos.input","message":"Receiving messages from Redis streams: [tst_messages]"}
{"@timestamp":"2020-05-20T18:24:36+01:00","@service":"benthos","level":"ERROR","component":"benthos.input","message":"Error from redis: redis: can't parse array reply: \"$15\""}

Updating go-redis to v.7.2.0 fixes my use case.

Looks good, thanks @citrin! I'll put a release out this weekend.


refactor: Deprecate static template configurations and fix the issue that meta descriptions were shortened

1. Why is this change necessary?
Currently one can enter 255 characters of meta description in the administration, but only 150 are shown in the storefront. Furthermore there exist some static config variables, only used by the theme, which could not be changed.
2. What does this change do, exactly?
Deprecate the static config variables, remove their remaining occurrences and set the truncation length of the meta description to 255 as indicated in the administration.
3. Describe each step to reproduce the issue or behaviour.
Create a meta description longer than 150 characters.
4. Please link to the relevant issues (if any).
-
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-22056
Please use this issue to track the state of your pull request.


include stac_version to default search attributes: #253

Related Issue(s): #253
Description:
Adds stac_version to default attributes advertised o /search results. Extra fields properties.proj:epsg and properties.odc:product are a "good to have" but they require tests modified to accommodate them.
PR Checklist:

[ ] Code is formatted and linted (run pre-commit run --all-files)
[ ] Tests pass (run make test)
[ ] Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
[ ] Changes are added to the CHANGELOG.

@jaysnm   LGTM, can you add a changelog entry?

I'll add this changelog entry in a followup PR


Remove The Horizontal Scroll Bar

Purpose

The purpose of this PR is to fix #330
Goals

Removing the Horizontal Scroll Bar in Home Page.
Approach

I removed the unwanted classes in index.html file.
Screenshots

Preview Link
https://yoshitha-sack.github.io/sack-site/
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[ ] I have read and understood the development best practices guidelines
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Related PRs

Test environment

Learning

Good job! @Yoshitha-SACK
Could you please update the issue number? It should be 328. Also, add the previous pull request number (the one you accidentally closed) to the Related PRs section.

Ok

@Piumal1999 Now is it ok


Feature request: Force a Correction step if Module-Level Inputs Involve Step Changes

Is your feature request related to a problem? Please describe.
If a module-level output used as input in other module (such blade-pitch angle or generator torque passed from ServoDyn to ElastoDyn) involves a step change, the extrapolation of inputs to ElastoDyn results in inaccuracies that require a correction step to resolve (requiring the user to set NumCrctn > 0).
Describe the solution you'd like
It would be great if the OpenFAST solver was "smart" enough to identify that a step change of input has occurred and force a local correction step rather than requiring that a correction step be added in each time step of the simulation as set by the user.  The hard part will be defining a general threshold that indicates whether an input step change has occurred.  Given that most module-level inputs are either motions or loads, I imagine that this threshold could be derived from a characteristic length in the wind turbine (such as the tower height or blade length in ElastoDyn) and characteristic mass (such as UJacSclFact).  It would be great if this could be addressed in the ongoing implementation of tight coupling.
Additional context
An example of the issue is demonstrated in the following OpenFAST discussion: https://github.com/OpenFAST/openfast/discussions/2266.

I assume we probably want to do this in v 5.0.0


Onboarding women to web3 by Superwomen DAO!

Hello team, Aditi Chopra here! First things first congratulate y'all on putting together the event, choosing a kickass location, and setting up a seamless event submission process! :)
Title
Onboarding women to web3 by Superwomen DAO!
Recommended Labels
45 mins panel, women in web3, beginner, intermediate
Description
Proposal for a women-only panel discussion (45 mins) about how more and more women can be brought into web3 across domains (art to tech to marketing) and how those who building in it can be empowered.
I first organized a web3 women-only meetup out of frustration of having only a few countable women at all web3 events, whether it be hackathons, meetups, or education sessions. The belief of Superwomen DAO is that now that we have a new tech revolution at our doorstep, let's make sure as an ecosystem to have the starting line same for all genders. With this panel, I'd like to bring forth women experts to the world, share personal stories of starting, challenges faced over the journey, what's helped, and the way to identify and prepare themselves for the opportunities in the space. There's so much that needs to be discussed here!!
About me
Currently, I am building Superwomen DAO which has crossed 1000 members across channels, leading Community and Co. - my consulting firm (33 startups in clientele), and working on a weekend project to create a playbook for marketing and community in web3.
Superomen DAO is on twitter @ https://twitter.com/superwomendao.
I'm reachable on Twitter @ https://twitter.com/aditichoprax
and other links can be found on my Linktree.

Hello, @aditichoprax  Congratulations on getting shortlisted for a talk at Web3Conf India. Please share your email so that we can take it further.

Beautiful! Thank you team ☺
My email is<EMAIL_ADDRESS>

Hey guys!
Prabhjote here from CryptoNova by Jajabor Brand Consultancy (JBC). I used to be the crypto editor with Business Insider, up until 3 months ago. One of the primary reasons I switched over to brand consulting is because there wasn't enough representation and with CryptoNova we want to bring more women into the web3 fold -- it's actually one of my OKRs for the year.
It would be really awesome to be a part of this panel. Do let me know how I can contribute. :)
My DMs are open on Twitter https://twitter.com/pabsgill
Or you can reach out to me at<EMAIL_ADDRESS>


CI for Node

Run npm test failed.. with Error: Process completed with exit code 1

Merged and deleted branch.


Verify SDL3 namespacing

Should be easy enough, but will take a nonzero amount of time so here's a ticket!

Question... should the API be SDL_GPU*? instead of mix-casing an acronym?

I like GPU over Gpu but I recall there being a reason we did it like this... @thatcosmonaut do you remember anything here? It's pretty easy to change this so I could go either way.

Actually I remember now: Ryan's API chose Gpu so we just went with his style - @icculus, any opinion on this?

Fine with me either way.

So here's where I ruin everyone's day by like 10%, I'm sorry in advance.
I personally like "Gpu" better because I think "SDL_GPUWhatever" looks bad, but I also chose this before we went wild renaming all the SDL3 APIs to be consistent.
Since we renamed everything else, none of these should be "SDL_GpuSetWidget" anymore; it would be more like "SDL_SetGpuWidget" now... SDL_+verb+noun. It's going to be a simple search/replace or perl script, but it's a little more of a pain in the butt than just changing the capitalization.
Imho, I still think the camel casing looks better in the newer form, but there are lots of things in SDL that don't do this (SDL_LoadWAV, SDL_HasNEON, SDL_GetJoystickGUID, etc), so we should probably go with "GPU" here, too.
@slouken, agree?

I don't feel strongly about GPU vs Gpu. I suggest that the first part of the renaming, to change to verb+noun be done, and people look and see how they like it, and whether we search and replace Gpu with GPU.
FYI, build-scripts/rename_symbols.py is a handy tool if you want to automate some of this, and includes a --substring command line option.

Also, having GPU in the name isn't necessarily a requirement, e.g. SDL_DestroyTexture(). If it refers unambiguously to something in the new API, it can stand alone. The final API should be reviewed for sanity and consistency though.

Okay, let's do the nasty part first then, and we'll revisit afterwards.
(There is a risk of people getting confused, though, when they wonder why they can't use SDL_CreateTexture with the GPU API, so as things get renamed, use your best judgment and we'll make a pass over it at that point.)

Given how much overlap there is with SDL_render terminology, it's probably less confusing to just put the GPU qualifier on everything - if it has GPU in it you'll know for sure that it's part of the GPU API.

Given how much overlap there is with SDL_render terminology, it's probably less confusing to just put the GPU qualifier on everything - if it has GPU in it you'll know for sure that it's part of the GPU API.

Sounds good.

it's probably less confusing to just put the GPU qualifier on everything - if it has GPU in it you'll know for sure that it's part of the GPU API.

Agreed.

We've effectively hit Beta minus this task and a few minor bugfixy things, so I'll push the weekly update today and then on Monday I'll run the C++ comment script at https://github.com/libsdl-org/SDL/commit/6501e90018ab1d58047e5b4382c6bc6d04051191 as well as a custom script for both SDL and other repos to automatically rename all functions to the new scheme, and that should take care of everything!

FYI, I'm in the process of removing the status code from the SDL API, switching a ton of functions from int to SDL_bool return values. I think you're already here, but the rest of SDL is being updated to match.

I changed SDL API functions to return SDL_bool instead of int, so they should be consistent with the GPU API. Go ahead and make sure you're not using the old approach when you're doing the naming revamp?

Confirmed that we use void, SDL_bool, or a Gpu pointer for return types, so we should be all set there!

Confirmed that we use void, SDL_bool, or a Gpu pointer for return types, so we should be all set there!

Great!

Resolved in gpu_next, which will be pushed to gpu in just a moment...


Not compatible with vscode 1.64.2

The earliest version that I've tested this with is 1.70.0. I'll try to find some time to actually test the extension with earlier version; as long as API is available - and API used is really limited - should be up.

Unfortunately, I am unable to perform tests as of now. You can always edit the VSIX (It's a ZIP file) to test it yourself.


KYLIN-4173 cube list search can not work

Can one of the admins verify this patch?

Codecov Report

Merging #846 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #846      +/-   ##
===========================================
- Coverage     25.71%   25.7%   -0.02%
+ Complexity     6125    6124       -1
===========================================
  Files          1400    1400
  Lines         83729   83729
  Branches      11740   11740
===========================================
- Hits          21531   21520      -11
- Misses        60126   60139      +13
+ Partials       2072    2070       -2

Impacted Files
Coverage Δ
Complexity Δ

...g/apache/kylin/rest/controller/CubeController.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ream/core/storage/columnar/ColumnarStoreCache.java
51.16% <0%> (-3.49%)
8% <0%> (ø)

.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java
63.84% <0%> (-2.31%)
0% <0%> (ø)

...eam/core/storage/columnar/DataSegmentFragment.java
57.37% <0%> (-1.64%)
17% <0%> (-1%)

...rg/apache/kylin/cube/inmemcubing/MemDiskStore.java
69.6% <0%> (-1.52%)
7% <0%> (ø)

...a/org/apache/kylin/dict/Number2BytesConverter.java
81.74% <0%> (-0.8%)
17% <0%> (-1%)

...org/apache/kylin/rest/util/QueryRequestLimits.java
40.47% <0%> (+4.76%)
6% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5867d6b...9dc5d74. Read the comment docs.


 If you're on ubuntu, sys/prctl.h is in libc6-dev. In general, shellphish-afl has all the same requirements as building AFL itself.

I have upgraded libc6-dev, it still didn't work.
make[1]: Entering directory `/tmp/pip-DpW3c7-build/bin/afl-multi-cgc/fakeforksrv'
cc -O3 -march=core2 -m32 -std=gnu99 -g -g3 -ggdb -gdwarf-4 -Wall -Wextra    fakeforksrv.c   -o fakeforksrv
cc -O3 -march=core2 -m32 -std=gnu99 -g -g3 -ggdb -gdwarf-4 -Wall -Wextra    run_via_fakeforksrv.c   -o run_via_fakeforksrv
run_via_fakeforksrv.c:3:23: fatal error: sys/prctl.h: No such file or directory
#include <sys/prctl.h>
^
fakeforksrv.c:2:23: fatal error: sys/prctl.h: No such file or directory
#include <sys/prctl.h>
^
compilation terminated.
compilation terminated.
make[1]: *** [fakeforksrv] Error 1


Switcher_only modules are only omitted from the list if something is typed into search

Describe the bug
Switcher-only modules defined by config (file in ~/.config/walker/_config.yaml, running walker -c ~/.config/walker/_config.yaml
builtins:
    applications:
        switcher_only: true

only get hidden after the user types a key.
Aditionally, I can't seem to disable any modules through the config, i.e.:
disabled:
    - runner
    - emojis
    - dmenu
    - windows
    - ssh
    - websearch
    - finder
    - hyprland
    - applications
    - clipboard

Still shows all modules.
Version
0.7.3 (latest)
Minimal Config
See above.
To Reproduce
Run walker -c ~/.config/walker/_config.yaml as described above. Applications still show up in the default screen. Only after typing a character does the set of applications get hidden as expected.
Disabled modules should not show up in the search window.
Expected behavior
switcher_only config option to work as expected.
Desktop
Fedora Linux 40
DE: Hyprland

Modules not being disabled has already been fixed in git.
Right now "show_initials" means = show applications = doesnt matter if switcher only or not.
That behaviour is subject to change... not sure yet.


Enhancement request and general queries in the GNSS subsystem

@bjarki-trackunit @fabiobaltieri

Why are we not parsing time and navigational data in gnss_nmea0183_parse_gga?
Is it necessary to enable both GGA and RMC messages on our gnss device?
Why data is published only when both GGA and RMC messages are received?

Because we get it in RMC, no need to get it from both :)
Yes, although there is overlap, we need speed, bearing and date from RMC, and we need HDOP and number of satellites from GGA
Since we need data from both RMC and GGA to fulfill the struct gnss_data, we need to parse both before we publish. We also need to ensure the RMC and GGA are related to the same GNSS fix

@fabiobaltieri Hey, I figured it out! both RMC and GGA contain the same UTC timestamp, so we can use it to ensure they are related to the same fix rather than a timeout :) GSV contains its own index to tie it together (message number and total number of messages)
I will update the NMEA0183 match handlers to use the fix instead of a timeout :)

@fabiobaltieri Hey, I figured it out! both RMC and GGA contain the same UTC timestamp, so we can use it to ensure they are related to the same fix rather than a timeout :) GSV contains its own index to tie it together (message number and total number of messages)

Neat!


BBox rotation is blocked near 90°

Describe the bug
If i try to rotate bounding box at 90° the box is stuck.
To Reproduce
See the dif below
#https://gifyu.com/image/SSNB3
Expected behavior
The bbox should rotate over 360°
Environment (please complete the following information):

OS: Windows 10 home
Label Studio Version   Docker label studio latest

EDIT:
i've also tried with other version using docker:

1.1.0: not present
1.2.0: not present
1.3.0: present

Thank you for your report.  We do have a few problems related to the region rotation now. But most of them, including this bug, might be fixed in this pull request https://github.com/heartexlabs/label-studio/pull/1849
So you could try a version from its branch. But anyway, I hope we will merge it soon.


[Release-1.26] - Failed bootstrapping of node leads to certificate mismatches

Backport fix for Failed bootstrapping of node leads to certificate mismatches

#8893

Unable to replicate the issue, tried with the 1.26.10+k3s2 version on different OS (Ubuntu, RHEL) with various setups (HA, split roles, etc). Closing it for now and will keep an eye out if this issue resurfaces and will check as part of patch validation for any regression.
Validated the dynamic listener version bump in go.mod for RC v1.26.11-rc1+k3s1, which is tagged using commit d00ad9db
https://github.com/k3s-io/k3s/blob/d00ad9db6aeed9496d1781809d53eaf4499ed1b5/go.mod#L128
From release v1.26.10+k3s2 (commit cb5cb55):
https://github.com/k3s-io/k3s/blob/cb5cb5557f34e240e38c68a8c4ca2506c68b1d86/go.mod#L127


abseil_cpp: 0.4.0-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository abseil_cpp to 0.4.0-1:

upstream repository: https://github.com/Eurecat/abseil-cpp.git
release repository: https://github.com/Eurecat/abseil_cpp-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.8.0
previous version for package: 0.2.3-0

abseil_cpp
* updated to version 2019-05-28
* ensure that -fPIC is set
* fixes
* Contributors: Alexander Rössler, Davide Faconti

hi. Any reason not to merge this?

hi. Any reason not to merge this?

We have an ongoing issue with the buildfarm: https://discourse.ros.org/t/security-issue-on-ros-build-farm/9342/7 .  Until that is resolved, we aren't merging new/updated package PRs into rosdistro.

It appears that this release broke ros_type_introspection's build.
http://build.ros.org/view/Kbin_uX32/job/Kbin_uX32__ros_type_introspection__ubuntu_xenial_i386__binary/2/


Add possibility to filter by discounts, on sale and new products

Questions
Answers

Description?
Adds a new feature that allows filtering for new products, discounted products or products with "On sale" flag.

Type?
new feature

BC breaks?
no

Deprecations?
no

Fixed ticket?

How to test?
Try this new filter, try to upgrade the module.

Description

Adds a new feature that adds possibility to filter by some new product special things.

You can filter out products that are new.
You can filter out products that are discounted.
You can filter out products that have "On sale" label on them.

I named a group of these new features "Highlights".

Screenshot

This change is

@MatShir what do you mean? it is about showing products with different state, on discount, on sale, new products - how would you like to split this?

Hello @Hlavtox :-)
As @MatShir said, it would be nice to have two separate parts for the two "types" of labels so it's not too confusing. By that, I mean that Discounted & On sale products should not be in the same section as New products, because they don't share common properties.
I liked your proposition with the use of "highlights" but in an ecommerce context, it doesn't work. We need to use words users are familiar with.
There's a second point: how can we translate it? It works fine in English, but for languages like French, you'd need to split it into two words and it would take too much space.
So, considering this, here's what we propose:
Instead of the Highlights category, two categories: Deals and Selection.
The Deals section is dedicated to Discounted and On sale products.
And, as a personal suggestion: Ultimately, "Flash sales" could be added to this category as well.
The Selection section contains a selection of specific products. In this case, the New products category.
Again, suggestion: categories such as season-themed or holiday-themed product collections could be added to this category. (e.g.: "Christmas collection", "Summer collection", etc.)
So it would look like this:

Deals:

Discounted
On Sale

Selection:

New products

What do you think? 🏎

@MatShir @kpodemski It's ready for review.

I went for facet name "Selections" and putting three values there. After Slack discussion, it doesn't make sense to have a separate category with one filter.
This filter is now enabled on new module install. For existing users, it's not.
When installing this module, I moved the stock, price and selections filter to the top. As they are the most important.
The filters work like this, if enabled - ((On sale OR Discounted) AND New product)

How it looks

Looks good to me !

Hi @florine2623, it works only on clean installs when there never was faceted search. For existing installs, there will be no change.

well done 👏🏻 thanks @Hlavtox

Hi @florine2623, it works only on clean installs when there never was faceted search. For existing installs, there will be no change.

Even after a module upgrade ? what needs to be done for this part to be on top ? @Hlavtox


RZBaseSwipeInteractionController short circuits interactive transitions [#46]

Fixes an issue where RZBaseSwipeInteractionController was canceled as soon as the gesture started tracking
Cleanup RZCirclePushAnimationController after the animation is completed. Fixes an issue where the modal Present animation would end up in a stuck state after canceling a transition.

@bskinner This looks good to me. We just need to update the pod spec to 1.2.1 and then merge.


Duplicated line in Token list

Bug Description
https://tokens.coingecko.com/all.json
There are duplicates lines in this list.
Steps to Reproduce
Here is the duplicated line info.
{"chainId":1,"address":"0xed0d5747a9ab03a75fbfec3228cd55848245b75d","name":"e Money","symbol":"NGM","decimals":6,"logoURI":"https://assets.coingecko.com/coins/images/13722/thumb/nx5m_kZJt3oz9UM0XhE-IEeJ8TGjX1831iNfLVWeMvHuYoyDGwN0vh9Wj8u5hCxe1u5Kw56zT5kqX_ia5u1hsMElA-ioKCvK2jUK4EdJMDUx4J1GOnjqIu30iXHrLfmdzqO2SyucZZZnutFVLIAkxWMcTbIo1GDPZ3dZSj2onSeEOnIY4GJKR9B6ByR1XUZrJxtpY9QjwoWLfPC.jpg?1611182880"}
Expected Behavior
It should be unique token list.

"name": "ZEDXION Token",
"website": "https://zedxion.io",
"description": "ZEDXION is a stablecoin issued by Paxos in partnership with Etherum.",
"explorer": "https://etherscan.io/token/0xfbc4f3f645c4003a2e4f4e9b51077d2daa9a9341,
"type": "TRC20",
"symbol": "ZEDXION",
"decimals": 18,
"status": "active",
"id": "0xfbc4f3f645c4003a2e4f4e9b51077d2daa9a9341"
}

This is an issue with the list, not the spec


Replace the structure generator java module

Ideally I would like the command placement to be handled in the python script, rather than relying on external tools.
See if there's a way to get python to talk to minecrafts chat box.

I've managed to find a library that works with minecraft.
PyDirectInput.
I'll need to update some code/docs.

Replace Autotyper with a PyDirectInput Variant
Remove the Java Module code
Remove the Jar and Bat files from the structure generator code
Update docs - remove JDK9 requirement
Update requirements.txt, remove py4j, replace it with PyDirectInput and PyperClip

Replaced Autotyper with a PyDirectInput Variant
Removed the Java Module code
Removed the Jar and Bat files from the structure generator code
Updated docs - removed JDK9 requirement
Updated requirements.txt, removed py4j, replaced it with PyDirectInput and PyperClip


__host_peek is byte swapped on Chihiro

It's 4 byte aligned only as well, meaning TYPE_SHORT & TYPE_BYTE don't function as expected, I imagine poke is the same way.
Because of above, netdimm_peekpoke's dump function returns bad results.

If its broken on Chihiro it is likely broken on Triforce as well. I think Naomi might be the only one that supports 8 and 16 bit accesses. FWIW Naomi has byte alignment for 4 and 2 byte reads as well, but it does support 1 byte access.


Fix Timezone to UTC in Datapipes and Cosine Zenith

Modulus Pull Request
Description
This PR fixes timezones in the ERA5 datapipes and in the related cosine zenith utilities. There was a discrepancy because of this that caused a +3600 to appear to be correct, but was likely an artifact due to improperly set time zones.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[ ] An issue is linked to this pull request.

/blossom-ci

/blossom-ci

This looks good, I'm approving the fix as well.

/blossom-ci

/blossom-ci

/blossom-ci


FlatShading=false is not working as expected

The shading of the ExtrudeBufferGeometry looks always like setting flatShading to true.
Expected: The flatShading depends on the material setting. Default is "flatShading: false" and the geometry looks smooth.
We can solve this by adding one line after line 49 in /src/aframe-rounded-box-component.ts (update from Latest commit [78e78b1] on Nov 23, 2022):
line 49:           Geometry.center()
line 50:           Geometry = THREE.BufferGeometryUtils.toCreasedNormals(Geometry);

Result is on the right (left is with material="flatShading: true")

AFrame-Version: 1.4.1

But THREE.BufferGeometryUtils.toCreasedNormals(Geometry);  functionality isn't available in ThreeJS r126,
(Aframe 1.5.0 is locked off at r126)
Am I missing something?

I didn't checked the past versions, but I know we added it since March 2023. Currently aframe 1.5.0 master uses Three 0.158 (or greater) and there it exist like here https://threejs.org/docs/#examples/en/utils/BufferGeometryUtils.toCreasedNormals described.
The second parameter seems to be optional (checking the funtction definition) with a default of PI/3 which is 60 degrees in gradians.

The module needs to be especially imported. I'm restricted on my project in that I need to use vanilla Aframe 1.5.0 with no extra threeJS modules.
Looks like I need another solution.


How to set badge self-increasing on iOS?

How to set badge self-increasing when receive a notification? Thank you!

@YingshanDeng the plugin doesn't handle increasing the badge number automatically it will only set the badge to the value you specify in the APNS payload.
https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/PayloadKeyReference.html


[Request] Agents in Inventory Changer

I would love to see agents in the inventory changer

you can add them by adding #Type_CustomPlayer next to the other ones and adding the weapon id for the playerskins

#2951


feat(MWPW-142267): Merch What's Included and Merch Mnemonic List (TwP)

Introduces Merch What's Included and Merch Mnemonic List web components for TwP What's included screen.
Resolves: MWPW-142267
Test link: https://mwpw-142267--milo--adobecom.hlx.page/drafts/axel/block-samples/twp/illustrator#twpmodal
Migrated from https://git.corp.adobe.com/wcms/tacocat.js/pull/572

How it works in Milo
In merch-twp block
Given a merch-twp block, a third separator --- is expected and then below a link to the what's included screen modal content.

In merch-card block
A link with name "merch-whats-included" is expected (link text is authorable)

This PR also introduces 2 new web components, which are:
merch-whats-included

Contains link of whats-included modal content (works as an inline fragment) and lets the author configure number of rows in mobile to display before "+ See more".
merch-mnemonic-list

Contains content of what's included screen.
Assumptions
What's included is an experience only applicable to a CC All Apps merch card.
Supports unlimited number of columns
Supports configurable number of rows before displaying "+ See more" in mobile.
Preview URLs:

Before: https://main--milo--adobecom.hlx.page/drafts/axel/block-samples/twp/illustrator#twpmodal
After: https://mwpw-142267--milo--adobecom.hlx.page/drafts/axel/block-samples/twp/illustrator#twpmodal

URL for testing:

https://mwpw-142267--mas--adobecom.hlx.page/

Overal I like your approach with [slot="merch-whats-included"]

There are some visual issues on mobile.

expecting a fragment with a specific name feels a bit limiting to me. Couldn't we use a #merch-whats-included  hash or something similar?
How to we close and go back to TWP without closing the modal?

Please find my answers below.

Fixed.
2: Using a hash will make Milo treat the content as Modal which complicates things and would require a "hacky" approach to not update the URL and capture the click event of such modal. Using query parameters also doesn't work with fragments since those are stripped by milo. In my example it is not specifically tied to that name, it could be a different name as long as the name contains 'merch-whats-included'. Another thing to keep in mind is that the end user will not see this file name at all (unless inspecting the code). Please suggest.

By capturing the close modal event and toggling if the fragment content visibility. I have started a thread in #milo-dev

@Axelcureno to make the PSI check green you can just provide a fake link, with your branch, you can check the example green pr here:
https://github.com/adobecom/mas/pull/19

URL for testing:

https://mwpw-142267--mas--adobecom.hlx.page/

Introduces Merch What's Included and Merch Mnemonic List web components for TwP What's included screen. Resolves: MWPW-142267 Test link: https://mwpw-142267--milo--adobecom.hlx.page/drafts/axel/block-samples/twp/illustrator#twpmodal Migrated from https://git.corp.adobe.com/wcms/tacocat.js/pull/572
How it works in Milo In merch-twp block Given a merch-twp block, a third separator --- is expected and then below a link to the what's included screen modal content.
In merch-card block A link with name "merch-whats-included" is expected (link text is authorable)
This PR also introduces 2 new web components, which are:
merch-whats-included  Contains link of whats-included modal content (works as an inline fragment) and lets the author configure number of rows in mobile to display before "+ See more".
merch-mnemonic-list
Contains content of what's included screen.
Assumptions What's included is an experience only applicable to a CC All Apps merch card. Supports unlimited number of columns Supports configurable number of rows before displaying "+ See more" in mobile.
Preview URLs:

Before: https://main--milo--adobecom.hlx.page/drafts/axel/block-samples/twp/illustrator#twpmodal
After: https://mwpw-142267--milo--adobecom.hlx.page/drafts/axel/block-samples/twp/illustrator#twpmodal

URL for testing:

https://mwpw-142267--mas--adobecom.hlx.page/?martech=off


Automatic virtual groups for package.js based on apps, templates, runs

Automatic virtual groups for package.js based on apps, templates, runs
This is not required for the demo.

It might be right time to address this issue.

I think that this issue was a conceptual grandparent for https://github.com/Starcounter/RebelsLounge/issues/14 and can be closed now. @tomalec do you agree?

Yep, that is probably a grandparent :)
However I think, this issue adds a fair point, that we may consider adding all elements given by an app, into a group, if  we do not want to do so, we can close this issue.

Closing, because it is related to the old layout editor which was phased out.


storageV2 blob containers dont open on Azure Storage Explorer tool (web consoleworks fine)

Storage Explorer Version: 1.14.2
Build Number: 20200715.2
Platform/OS: Windows 10
Architecture: ia32
Regression From:  NA

Bug Description
Unable to retrieve child resources.
Details:
["FetchError:request to https://ae041030fspstg.blob.core.windows.net/?include=metadata&comp=list failed, reason: read ECONNRESET"]

Steps to Reproduce

Add an Azure account.
click on storage account(storageV2)
expand blob container.
Note: storage account of type BlobStorage opens fine.

Expected Experience
full access to files in storage
Actual Experience
unable to load file list.
Additional Context

@pardhivchunduri are you consistently seeing this error? Does it happen when trying to load blobs in other storage accounts?

Yes @MRayermannMSFT , the issue applies to all Storage accounts with "Account Kind" = "StorageV2" || "Storage", irrespective of which subscription they belong to. the only ones opening are "Account Kind" = "BlobStorage". and just to be clear all these open perfectly on the Azure web console.

@pardhivchunduri are your storage accounts behind a virtual private network or maybe a storage firewall that would prevent them from being accessed from your machine?

I have raised the issue to my admin department, they are investigating the issue. once i have something, i will update or close this ticket. Thanks.

@pardhivchunduri we're going to go ahead and close this. If you ever have an update, please open a new issue and include a link back to this one. Thanks!


Bedhead Upcycle Project

Started modifications to pre-loved bedhead obtained when neighbour moved out.

Review switch input / WS2812B level shifting output circuit. Need to create a BOM for parts picking and selection.

Mounted switch socket IO connections and routed wires along rear of LED extrusion. LED extrusion cut to length and test fitted into slot routed in the headboard.

08-02-23
Need to trim back extrusion and fit switch plates.
Think about wiring and power options?

03-09-2023

Attach bedhead to bed base.
Solder driver circuit onto ESPMAX board
Swap Fusco D1 MIni to ESPMAX baord
Power on to test functionality.

TODO
Add switch interface components
Add I2C connection for Humidity / Temperature sensor (BME280)
Design / construct enclosure for ESPMAX and / or mains power supply.
Maybe add fuse to positive power lead.


[Hacktoberfest] Memoization of properties!

Bug or feature request?
Enhancement
Description:
For Hacktoberfest, I would love help adding a memoization decorator to certain computed get properties in StateNode, such as:

.definition
.config
.on
.after
.tree
.delays
.resolvedStateValue
.initialStateValue
.initialState
etc.

For some properties, caching is already done in an ad-hoc way (e.g., with __cache and idMap) but there's definitely better ways to do this.
(Feature) Potential implementation:
Take a look at something like typescript-memoize to guide you.

Is anyone working on this? I'd like to pick it up if it's available :)

@tarsir It's yours if you want it! Would love the help.

Is this issue already done @davidkpiano ?
In case it's not done, I'd like to take it.

@ivanportillo It's not done yet, feel free to take it!


does the pykaldi support python(2.7.15)?

conda install -c pykaldi pykaldi-cpu
it gives prompt。
The following packages will be DOWNGRADED:
libedit                           3.1.20170329-h6b74fdf_2 --> 3.1-heed3624_0
mkl_fft                             1.0.10-py27ha843d7b_0 --> 1.0.1-py27h3010b51_0
mkl_random                           1.0.2-py27hd81dba3_0 --> 1.0.1-py27h629b387_0
ncurses                                    6.1-he6710b0_1 --> 6.0-h9df7e31_2
python                                  2.7.15-h9bab390_6 --> 2.7.14-h89e7a4a_22
qt                                       5.9.7-h5867ecd_1 --> 5.9.6-h52aff34_0
readline                                   7.0-h7b6447c_5 --> 7.0-ha6073c6_4
sqlite                                  3.26.0-h7b6447c_0 --> 3.23.1-he433501_0

It does. I am not sure why conda is trying to downgrade the packages. Try installing it in a fresh environment and see if that changs anything.

installing in a fresh environment of python(2.7.15) is ok. the environment is installed by kaldio of other version ant it gives the  prompt.


If the address is added as default and while the customer updates that particular address it removes the default address.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
master
Issue Description
If the address is added as default and while the customer updates that particular address it removes the default address.
Preconditions

Customer must be logged in.
Customer should have at least one added address and set it as default.

Steps to reproduce

Go to 'Shop' and login as User
Edit the default address and save it inside the Accounts/Addresses
See the error

Expected Result
It should be saved as the default address until the user does not set another address as default or deletes that address.
Actual Result
After updating the address it was removed as the default address.  Here
Screenshots
No response
Additional context
No response

@Amitk-webkul Please assign this issue to me, i am working on it

@JunaidJaved248, I have assigned the issue to you please proceed.


Run Digest Access Authentication test on HHVM

Travis CI seems to be using an old version of HHVM (3.6.6). Last environment update was 2015-04-09.
https://docs.travis-ci.com/user/build-environment-updates/2015-04-09/
https://docs.travis-ci.com/user/build-environment-updates/
Need at least HHVM 3.12.X scheduled "January 29th 2016 (cut on January 18 2016)" for this pull request to succeed.
https://github.com/facebook/hhvm/wiki/Release Schedule


Support enumerating the known event types

It looks like go-github has an internal list of all the GitHub event types .  I'd like to be able to iterate over the list in my own code where I route events based on event type.  I'm thinking of exposing the following methods:
// WebhookTypes returns a list of all the known GitHub event type strings supported by go-github.
func WebhookTypes() []string {
  // ...
}

// EventForType returns an empty struct matching the specified GitHub event type.
func EventForType(messageType string) any {

}

The second method would extract a lot of Event.ParsePayload https://github.com/google/go-github/blob/master/github/event.go#L30, so it wouldn't be much additional code.

I have no problem with that as long as you can refactor to reuse existing code as much as possible.
I say this because any time a new PR comes in to support a new webhook event type, it is a bit of a pain to make sure you tweak all the various places that need tweaking, and it would be nice to not add more pain to this process.


add facts from database

[missing validation]: validate predicate arity for loading facts from a Data Source. The following validation needs to be implemented:

an exception must be thrown if the artity of a predicate whose facts are added from a data source does not match the arity of facts in the corresponding data source.

implemented


Getting started needed for Jetson Nano eMMC

Getting started points to: https://docs.balena.io/jetson-nano-emmc/nodejs/getting-started/#adding-your-first-device

Looks like an issue has been already opened for this DT, closing


Add a "reset" method

It would be nice if I could call some kind of "reset" or "clear" in the middle of my test, that will cleanup any expectations or stubs I set on the mock object previously.

Maybe I'm missing the point, but why not just create a new mock object?

If I already gave the mock as a dependency to an object in the setUp for instance.
I agree it's not very common, but we had a use case for it.
On Tue, Jan 27, 2015 at 7:26 PM, Erik Doernenburg
<EMAIL_ADDRESS>wrote:

Maybe I'm missing the point, but why not just create a new mock object?
Reply to this email directly or view it on GitHub:
https://github.com/erikdoe/ocmock/issues/176#issuecomment-71688980

Would love to see this implemented. Even better, it'd be nice if a second call to stub overwrote the first. This is useful for setting defaults in a test setUp block and then overriding in the specific tests as needed.

Please see the discussion on #103 for more detail on why overwriting stubs isn't something we're likely to see soon.
Regarding the scenario you describe, having a setup method that creates some default stubs which are overwritten by tests, I'd say that on the one hand my goal for OCMock is to create a general tool that allows different approaches, and not "opinionated software" (http://stackoverflow.com/questions/802050/what-is-opinionated-software). On the other hand, though, the pattern of creating default stubs and then overwriting them doesn't sound like a particularly good idea to me.
Personally, and that is based on more than 10 years of experience with test-driven development and mock objects, I've moved away more and more from using setup methods at all. Saving a couple of lines in each test might look attractive at first but in the end it does create coupling between the individual tests, making the suite more brittle. In the example with the default stubs, imagine what happens when you change a default stub; you have to go through all tests to assess the impact. Also imagine someone works in another part of the system and breaks a seemingly unrelated unit test that uses this pattern; what's the cognitive overhead to understand a unit test if you have to understand that interplay between setup and individual tests. I'm clearly a DAMP not DRY guy (http://stackoverflow.com/questions/6453235/what-does-damp-not-dry-mean-when-talking-about-unit-tests).

Thanks for the detailed response! I agree that it does create coupling between the tests. On the other hand, there are instances where I am testing a number of slightly different configurations. If we decide to change a method, or the manner in which an object is initialized, not having a setup method requires a change in every test. Perhaps this is preferable to the coupling between, but I've never seen any real issues with using a setup method.
I think the idea of later stubs overriding earlier stubs is very intuitive, especially since other popular mocking frameworks (e.g. RSpec) do support this behavior.
Theoretically, if someone were to create a PR with this functionality, would it have a chance of being accepted?

A common approach to avoid duplication when setting up instances with slightly different configurations is to implement the Builder pattern. I've written about an Objective-C approach here: http://erik.doernenburg.com/2011/11/builder-pattern-in-objective-c/
Regarding the question about the hypothetical PR, I still stand by what I wrote in issue #103: "That said, with the benefit of hindsight, having later stubs overwriting earlier ones does seem preferable. However, making this change now would be very disruptive, it would break lots of tests that people have written. For that reason I am shying away from switching the behaviour now."


⚠ Bofrost.at has degraded performance

In 4a5d3a3, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2389 ms

Resolved: Bofrost.at performance has improved in 881c04e after 13 minutes.


feat(avm): e2e radix

Please read contributing guidelines and remove this line.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6882  👈
#6880
#6877
#6848
#6806 : 1 other dependent PR (#6819 )
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Maddiaa0 and the rest of your teammates on  Graphite

this was to debug a radix fix, which was a calldata copy inconsistency


Summarize changes in each release

Hey folks! Our team has been tracking down a breaking issue in N1 today and it turns out it's caused by the 3.3.0 release of node-spellchecker (mysteriously, it just causes the app to fall into a hard loop at launch. We haven't determined why yet.). Looking over the recent commits, it's really not clear what has changed or why—would be really great if we could start putting release notes on new versions to make triaging things easier. We'll be locking N1 to a specific release rather than ^3.2.1 to avoid these problems in the future, but it'd be great to keep up with changes.

How do people usually tracking the changes? Is adding a CHANGELOG.md enough?

We have a tool that the Atom team uses to roll up all Pull Request information relevant for each release. Perhaps the Electron team should start using it as well? I'll bring it up in the next team meeting.


[FALSE-POSITIVE]

Domains or links
Please list any domains and links listed here which you believe are a false positive.
https://bp-home-idd-ui-nwo.qa.dlgdigitalapi.com/online/qpm/login
https://bp-home-qa-ui-nwo.qa.dlgdigitalapi.com/online/qpm/login
https://bp-home-ua-ui-rbso.qa.dlgdigitalapi.com/online/qpm/login
Basically the whole qa.dlgdigitalapi.com domain.
More Information
Incorrectly marked as Phishing on Phishtank or OpenPhish?
Have you requested removal from other sources?
Google Security Console
Additional context
Add any other context about the problem here.
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR on the whitelist.me file

https://github.com/mitchellkrogza/Phishing.Database/blob/master/whitelist.me/whitelist.me
Please include the same above information to help speed up the whitelisting process.

Should have said. This whole domain is supposed to have access restricted by IP. This occurred because someone put a /0 rule in a global security group


xsbt-web-plugin 1.0.0 is incompatible with scalatra-sbt 0.3.5

We should fix that in the next release. If no one fix this issue, I'll send a pull request later.
https://github.com/earldouglas/xsbt-web-plugin
Caused by: java.lang.ClassNotFoundException: com.earldouglas.xsbtwebplugin.PluginKeys$
	at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at org.scalatra.sbt.ScalatraPlugin$.<init>(ScalatraPlugin.scala:15)
	at org.scalatra.sbt.ScalatraPlugin$.<clinit>(ScalatraPlugin.scala)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:340)

Using webappDest during dist:stage to stage the standalone distribution also includes WEB-INF/lib. This leads to problems, since the libraries are then contained twice in the distribution (in ./webapp/WEB-INF/lib and ./lib directory). This requires a better solution.

I think excluding the WEB-INF/lib and WEB-INF/classes when building a distribution is a simple but effective solution. See: https://github.com/dozed/scalatra-sbt/commit/6845051835a49e9d2ecc7c951770ca288041be44

@dozed Thank you for your attention to this matter. It would be nice upgrading scalatra-sbt to use web plugin 1.0 when Scalatra 2.4.0 release (the date of release is not decided yet).

@seratch It needs some testing, but I think it is stable. If you need help let me know.

Fixed 0.4.0 will be out soon (I'll do the release).


WIFI-1934-LED-Turnoff

This Patch will add support to turnoff LEDs of the AP through cloud
command
Signed-off-by: Nagendrababu<EMAIL_ADDRESS>

No mechanism to go back to pre-existing configuration.
I believe you will take care of this in the LED "system state" signalling story.

sure, I'll add that mechanism as well in my https://telecominfraproject.atlassian.net/browse/WIFI-1932 user story


SQL Server parser incorrectly reports "Table or subquery not found" with STRING_AGG and WITHIN GROUP

Description
Hello DBeaver team,
I've encountered an issue with the SQL Server parser in DBeaver. It incorrectly reports a "Table or subquery not found" error when using STRING_AGG with a WITHIN GROUP clause, despite the query being valid and executable in SQL Server.
When using STRING_ADD without WITHIN GROUP:

When using STRING_ADD with WITHIN GROUP (This reports an error and will cause auto-completion to be disabled):

DBeaver Version
Community Edition <IP_ADDRESS>409221725
Operating System
Fedora Linux 40
Database and driver

Database: Microsoft SQL Server 2022
Driver: Microsoft JDBC Driver for SQL Server (mssql-jdbc-12.8.0.jre11.jar)

Steps to reproduce

Create test tables and data:

CREATE TABLE Customers (
  customer_id INT PRIMARY KEY IDENTITY(1,1),
  name VARCHAR(255),
  address VARCHAR(255)
);

CREATE TABLE Orders (
  order_id INT PRIMARY KEY IDENTITY(1,1),
  order_date DATE,
  total DECIMAL(10, 2),
  customer_id INT,
  order_description VARCHAR(500),
  FOREIGN KEY (customer_id) REFERENCES Customers(customer_id)
);

-- Insertar clientes
INSERT INTO Customers (name, address)
VALUES
  ('John Doe', '123 Main St'),
  ('Jane Smith', '456 Elm St');

-- Insertar pedidos
INSERT INTO Orders (order_date, total, customer_id, order_description)
VALUES
  ('2022-01-01', 100.00, 1, 'Pedido de prueba'),
  ('2022-01-15', 200.00, 1, 'Compra de electrónicos'),
  ('2022-02-01', 50.00, 1, 'Compra de accesorios'),
  ('2022-03-01', 300.00, 2, 'Compra de ropa'),
  ('2022-04-01', 250.00, 2, 'Compra de muebles'),
  ('2022-05-01', 150.00, 2, 'Compra de juguetes');

Run the following query, which works correctly and doesn't trigger any parser errors:

SELECT
	c.customer_id,
	c.name,
	STRING_AGG(
    	        CONCAT(o.order_description, o.total, FORMAT(o.order_date, 'ddMMyyyy')),
		'/'
        ) AS order_details
FROM
	master.dbo.Customers c
LEFT JOIN
        master.dbo.Orders o
ON
	o.customer_id = c.customer_id
GROUP BY
	c.customer_id, c.name;

Modify the query by adding WITHIN GROUP (ORDER BY o.order_date DESC) and run it (the query executes correctly but the parser reports an error in the code).

SELECT
	c.customer_id,
	c.name,
	STRING_AGG(
    	        CONCAT(o.order_description, o.total, FORMAT(o.order_date, 'ddMMyyyy')),
		'/'
        ) WITHIN GROUP (ORDER BY o.order_date DESC) AS order_details
FROM
	master.dbo.Customers c
LEFT JOIN
        master.dbo.Orders o
ON
	o.customer_id = c.customer_id
GROUP BY
	c.customer_id, c.name;

Additional context
Dbeaver installed via flatpak

Thank you for your report.


Fix find usage in some resolves.

We currently are using fp.find in a few resolves where we are not expecting to deal with the maybe type.
Switch those resolve to use Array.prototype.find instead.

Codecov Report

Merging #13 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage   94.97%   94.97%   +<.01%
==========================================
  Files         291      291
  Lines        3860     3861       +1
  Branches      462      462
==========================================
+ Hits         3666     3667       +1
  Misses        173      173
  Partials       21       21

Impacted Files
Coverage Δ

source/iml/lnet/lnet-dispatch-source.js
100% <100%> (ø)
:arrow_up:

source/iml/server/server-detail-resolves.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 83f1cd0...7a78afb. Read the comment docs.


Error: SocketException: OS Error: Connection refused, errno = 111

when i am trying to post anything on meilisearch it is showing me the error:
Error: SocketException: OS Error: Connection refused, errno = 111, address = <IP_ADDRESS>, port = 41200
this is my code in flutter:
http.post(                 Uri.parse('https://<IP_ADDRESS>:7700/indexes'),                 body: json.encode({'uid': 'questions', 'primaryKey': 'id'}),               );

Hello @madhavanswami!
It looks like your MeiliSearch is not accessible from your flutter code. Can you try this curl command in your terminal (not from your flutter code)?
curl -X GET http://localhost:7700/health

If changing from https to http doesn't work are you using the Andriod emulator? If yes try http://<IP_ADDRESS> instead of http://<IP_ADDRESS>. More info on this here.

If changing from https to http doesn't work are you using the Andriod emulator? If yes try http://<IP_ADDRESS> instead of http://<IP_ADDRESS>. More info on this here.

tried both http as well as https but does not work. I've deployed meilisearch on aws and then am using it from a physical device. I also tried the official meilisearch package for flutter but then also facing the same issue. Please help me

So your MeiliSearch you are testing against is running on AWS? If yes, you need to send the request to that address instead of to local host.

So your MeiliSearch you are testing against is running on AWS? If yes, you need to send the request to that address instead of to local host.

yes i am doing that only but the same error comes

Do you have a firewall blocking on the AWS end?

Do you have a firewall blocking on the AWS end?

no

I don't get it, is your MeiliSearch in your local machine?
If you get the error with the curl it means this is not a MeiliSearch error, but a connexion error -> you don't use the right address to reach the MeiliSearch server

I suspect @curquiza is correct and the issue is in the address, but one more thing to check is if you gave the app permissions to access the internet in the manifest file? <uses-permission android:name="android.permission.INTERNET" />

I don't get it, is your MeiliSearch in your local machine?
If you get the error with the curl it means this is not a MeiliSearch error, but a connexion error -> you don't use the right address to reach the MeiliSearch server

Meilisearch is deployed on aws. The curl gives 200 ok.  I am using the adress of aws

I suspect @curquiza is correct and the issue is in the address, but one more thing to check is if you gave the app permissions to access the internet in the manifest file. <uses-permission android:name="android.permission.INTERNET" />

Yes I've done that

Do you have a master key set in MeiliSearch? It looks like you aren't passing one in your request so maybe that is the issue?

Do you have a master key set in MeiliSearch? It looks like you aren't passing one in your request so maybe that is the issue?

Yes i am passing the master key. I've figured out that the problem i am facing is due to aws and not because of meilisearch.
Ive tried to make calls with postman and

connect ECONNREFUSED <IP_ADDRESS>:443

this error it shows me eventhough passing the right master key.