Xtreme-Firmware compatability?

Current FAP not compatible with latest Xtreme firmware version and crashes when selecting any option in meny,
Unable to self compile for Xtreme-Firmware
Using fbt fap_esp32_gravity
$ ./fbt fap_esp32_gravity
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_attacks.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_attacks_mana.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_console_output.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_help.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_help_info.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_main.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_packets.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_packets_deauth.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_packets_fuzz.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_purge.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_settings.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_targets.c
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_text_input.c
        CC      applications_user/esp32_gravity/storage.c
        CC      applications_user/esp32_gravity/sync.c
applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c: In function 'uart_terminal_scene_settings_mac_changed_callback':
applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c:47:62: error: unused parameter 'context' [-Werror=unused-parameter]
   47 | void uart_terminal_scene_settings_mac_changed_callback(void *context) {
      |                                                        ~~~~~~^~~~~~~
applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c: In function 'uart_terminal_scene_settings_mac_on_exit':
applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c:82:53: error: unused parameter 'context' [-Werror=unused-parameter]
   82 | void uart_terminal_scene_settings_mac_on_exit(void* context) {
      |                                               ~~~~~~^~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_settings_mac.o] Error 1
applications_user/esp32_gravity/storage.c: In function 'load_settings':
applications_user/esp32_gravity/storage.c:155:14: error: variable 'bytesRead' set but not used [-Werror=unused-but-set-variable]
  155 |     uint16_t bytesRead;
      |              ^~~~~~~~~
applications_user/esp32_gravity/storage.c:152:38: error: unused parameter 'app' [-Werror=unused-parameter]
  152 | bool load_settings(UART_TerminalApp *app) {
      |                    ~~~~~~~~~~~~~~~~~~^~~
applications_user/esp32_gravity/storage.c: In function 'save_data':
applications_user/esp32_gravity/storage.c:173:34: error: unused parameter 'app' [-Werror=unused-parameter]
  173 | bool save_data(UART_TerminalApp *app) {
      |                ~~~~~~~~~~~~~~~~~~^~~
applications_user/esp32_gravity/storage.c: In function 'load_data':
applications_user/esp32_gravity/storage.c:200:14: error: variable 'bytesRead' set but not used [-Werror=unused-but-set-variable]
  200 |     uint16_t bytesRead;
      |              ^~~~~~~~~
applications_user/esp32_gravity/storage.c:197:34: error: unused parameter 'app' [-Werror=unused-parameter]
  197 | bool load_data(UART_TerminalApp *app) {
      |                ~~~~~~~~~~~~~~~~~~^~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/storage.o] Error 1

********** FBT ERRORS **********
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_settings_mac.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/storage.o: Error 1

Using fbt launch_app APPSRC=esp32_gravity
$ ./fbt launch_app APPSRC=esp32_gravity
        CC      applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c
        CC      applications_user/esp32_gravity/storage.c
        CC      applications_user/esp32_gravity/uart_terminal_app.c
        CC      applications_user/esp32_gravity/uart_terminal_uart.c
        ICONS   build/f7-firmware-C/.extapps/esp32_gravity/uart_terminal_icons.c
        CC      applications_user/esp32_gravity/uart_validators.c
applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c: In function 'uart_terminal_scene_settings_mac_changed_callback':
applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c:47:62: error: unused parameter 'context' [-Werror=unused-parameter]
   47 | void uart_terminal_scene_settings_mac_changed_callback(void *context) {
      |                                                        ~~~~~~^~~~~~~
applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c: In function 'uart_terminal_scene_settings_mac_on_exit':
applications_user/esp32_gravity/scenes/uart_terminal_scene_settings_mac.c:82:53: error: unused parameter 'context' [-Werror=unused-parameter]
   82 | void uart_terminal_scene_settings_mac_on_exit(void* context) {
      |                                               ~~~~~~^~~~~~~
cc1: all warnings being treated as errors
applications_user/esp32_gravity/storage.c: In function 'load_settings':
applications_user/esp32_gravity/storage.c:155:14: error: variable 'bytesRead' set but not used [-Werror=unused-but-set-variable]
  155 |     uint16_t bytesRead;
      |              ^~~~~~~~~
applications_user/esp32_gravity/storage.c:152:38: error: unused parameter 'app' [-Werror=unused-parameter]
  152 | bool load_settings(UART_TerminalApp *app) {
      |                    ~~~~~~~~~~~~~~~~~~^~~
applications_user/esp32_gravity/storage.c: In function 'save_data':
applications_user/esp32_gravity/storage.c:173:34: error: unused parameter 'app' [-Werror=unused-parameter]
  173 | bool save_data(UART_TerminalApp *app) {
      |                ~~~~~~~~~~~~~~~~~~^~~
applications_user/esp32_gravity/storage.c: In function 'load_data':
applications_user/esp32_gravity/storage.c:200:14: error: variable 'bytesRead' set but not used [-Werror=unused-but-set-variable]
  200 |     uint16_t bytesRead;
      |              ^~~~~~~~~
applications_user/esp32_gravity/storage.c:197:34: error: unused parameter 'app' [-Werror=unused-parameter]
  197 | bool load_data(UART_TerminalApp *app) {
      |                ~~~~~~~~~~~~~~~~~~^~~
cc1: all warnings being treated as errors
        APIPREP build/f7-firmware-C/sdk_origin.i
        APIPP   build/f7-firmware-C/sdk_origin.i
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_settings_mac.o] Error 1
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/storage.o] Error 1

fbt: warning: The 'launch_app' target is deprecated. Use 'launch' instead.
<lambda>, line 90, in file "/mnt/c/Users/thier/GoogleDrive/_dev/flipperzero/Xtreme-Firmware/site_scons/extapps.scons"

********** FBT ERRORS **********
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_settings_mac.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/storage.o: Error 1'

So while comping doesnt work I still managed to get to fap working. Eventhough the firmware incompatability message is still there it seems to work.
Issue was that the ESP32 kept rebooting and the Flipper did not take that well.
Adding a capacitor on the 5v and gnd pins helps keeping the ESP32 powered.

Ps. Would still like to compile it for Xtreme though

Sorry for not  replying more quickly, I've had a lot going and haven't had a chance to open VSCode for a few weeks.
I'm glad you were able to get it working, what sort of ESP32 chip/board are you using? I've only ever powered mine from 3v3 and don't think I've encountered any issues as a result.
Thanks for including the compiler output, that's very useful - and very surprising. I've never seen a compiler treat an unused variable as an error before, sorry for pushing non-compilable code :(
The repo is in a worse state than it should be at the moment because I found a significant bug after merging v1.0.0 into the head and killed the release. As a result of that the code you were compiling was v1.0.0, while the latest functional release was the prior release, v0.6.0.
That said, head should be in a pretty good state now if you want to try compiling again.
What build tools are you using? While writing this comment I went back through the compiler output above to make sure I hadn't missed anything, and your compiler is throwing up some utterly unfair errors, considering a variable to be unused even when it's a function argument. That's not cool at all. For the time being I've put in some really ugly code that should handle those cases without giving you an error, but ideally your compiler would treat those cases like every other compiler does :/
Because my compiler wasn't generating a warning for most of the errors you're seeing I'm flying blind with these changes to a fairly large extent - That means I can't promise what I've just done will work, but if it doesn't you should be able to see the type of changes I made to make your warnings go away in recent commits. You're welcome to do a similar thing for any further things your compiler complains about and submit a pull request to merge your changes into the repo.
Alternatively - and this will probably save you a lot of pain compiling other applications as well - you could create a small Linux VM or container to use as your build environment. Hopefully that will resolve the unusual configuration of your compiler and you'll encounter dramatically fewer errors trying to compile things in the future.
Lastly, you mentioned a "firmware incompatibility message" - I've compiled this once and run the same FAP on RogueMaster, stock and eXtreme. This isn't a firmware problem but (am I right in assuming the message includes the text "API mismatch"?) a version mismatch, where the FZ API version you're running is different from the FZ API version the FAP was compiled with.
All firmware bundles use the same APIs, all FAPs should run on all firmware distributions that use the same API version, the solution to this issue is to either install a firmware containing the API version a FAP was built with, or compile the FAP yourself using the API version you're running. I try to update my build tools regularly, so precompiled FAPs should run with whatever was newest at the time the FAP was released. The API mismatch error provides you with API versions; that lets you know whether your firmware is older or newer than what the FAP was built with. I think the best solution is: If your firmware is older than the FAP target firmware then upgrade your firmware, if the FAP was compiled against older firmware than you're running then compile the app yourself.
TL;DR:

Cloning the repository and compiling will hopefully work for you now.

There are a huge number of UI and settings changes in the most up-to-date code and there's a lot of testing still to be done. There may be some pernicious issues not yet found in the bleeding-edge code.
If it's flaky, the latest release is v0.6.0 and it should be fairly robust.

If it doesn't compile for you (and I'd suggest this even if it does) it's probably a good idea to create a Linux container or VM as your build environment, because the compiler you're using is a nasty little bugger.
Gravity works fine with eXtreme, it sounds like we've simply been on incompatible versions of the underlying FZ API. Use the version info in the error message to determine whether it'll be better for you to upgrade your firmware or compile apps yourself.

Let me know how you go, please!
Chris BC

Oops, unintentionally closed this - reopened now, I'm keen to hear whether your issues are resolved, and what OS & platform you're using to build given how little tolerance it has

Thanks for your reply, Ive read the non tldr and will let you know what a recompile does with HEAD.

Howdy, I'm getting similar build errors trying to compile against both Stock and Xtreme with API 49.1. I'm running Debian Bullseye through WSL2.
Against Xtreme through VSCode on Windows
 *  Executing task: ./fbt COMPACT=1 DEBUG=0 build APPSRC=applications_user/Flipper-Gravity

fbt: warning: Failed parsing manifest '/home/vixin/Flipper-Xtreme/applications/external/mifare_nested/application.fam' : Invalid appid '.mifare_nested'. Must match regex 're.compile('^[a-z0-9_]+$')'
LoadAppManifest, line 132, in file "/home/vixin/Flipper-Xtreme/scripts/fbt_tools/fbt_apps.py"
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help_info.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_main.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_deauth.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_fuzz.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_purge.c
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_attacks.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_attacks_mana.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:5:1: error: unknown type name 'TickType_t'
    5 | TickType_t launchTime;
      | ^~~~~~~~~~
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c: In function 'uart_terminal_console_output_handle_rx_data_cb':
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:34:5: error: unknown type name 'TickType_t'
   34 |     TickType_t delay = pdMS_TO_TICKS(10000);
      |     ^~~~~~~~~~
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:34:24: error: implicit declaration of function 'pdMS_TO_TICKS' [-Werror=implicit-function-declaration]
   34 |     TickType_t delay = pdMS_TO_TICKS(10000);
      |                        ^~~~~~~~~~~~~
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:35:9: error: implicit declaration of function 'xTaskGetTickCount' [-Werror=implicit-function-declaration]
   35 |     if (xTaskGetTickCount() - launchTime >= delay) {
      |         ^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_console_output.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help_info.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help_info.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_help_info.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_help.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_main.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_main.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_main.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_deauth.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_deauth.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets_deauth.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_fuzz.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_fuzz.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_purge.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_purge.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets_fuzz.o] Error 1
scons: *** [build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_purge.o] Error 1

********** FBT ERRORS **********
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_attacks.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_attacks_mana.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_console_output.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_help_info.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_help.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_main.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets_deauth.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets_fuzz.o: Error 1
build/f7-firmware-C/.extapps/esp32_gravity/scenes/uart_terminal_scene_purge.o: Error 1

Against Stock directly in Debian on Windows Terminal
$ ./fbt build APPSRC=esp32_gravity
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help_info.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_main.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_deauth.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_fuzz.c
        CC      applications_user/Flipper-Gravity/scenes/uart_terminal_scene_purge.c
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_attacks.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:5:1: error: unknown type name 'TickType_t'
    5 | TickType_t launchTime;
      | ^~~~~~~~~~
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c: In function 'uart_terminal_console_output_handle_rx_data_cb':
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:34:5: error: unknown type name 'TickType_t'
   34 |     TickType_t delay = pdMS_TO_TICKS(10000);
      |     ^~~~~~~~~~
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:34:24: error: implicit declaration of function 'pdMS_TO_TICKS' [-Werror=implicit-function-declaration]
   34 |     TickType_t delay = pdMS_TO_TICKS(10000);
      |                        ^~~~~~~~~~~~~
applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:35:9: error: implicit declaration of function 'xTaskGetTickCount' [-Werror=implicit-function-declaration]
   35 |     if (xTaskGetTickCount() - launchTime >= delay) {
      |         ^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_console_output.o] Error 1
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_attacks_mana.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_help.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_main.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_main.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_main.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help_info.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help_info.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_help_info.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_deauth.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_deauth.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets_deauth.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_fuzz.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_fuzz.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets_fuzz.o] Error 1
In file included from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_purge.c:1:
applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from applications_user/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from applications_user/Flipper-Gravity/scenes/uart_terminal_scene_purge.c:1:
applications_user/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_purge.o] Error 1

********** FBT ERRORS **********
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_attacks.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_console_output.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_attacks_mana.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_help.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_main.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_help_info.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets_deauth.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_packets_fuzz.o: Error 1
build/f7-firmware-D/.extapps/esp32_gravity/scenes/uart_terminal_scene_purge.o: Error 1

Using ufbt in the app directory through Terminal
$ ufbt build APPSRC=esp32_gravity
scons: Entering directory `/home/vixin/.ufbt/current/scripts/ufbt'
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_help_info.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_main.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_deauth.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_packets_fuzz.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_purge.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_settings.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_settings_mac.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_targets.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/scenes/uart_terminal_scene_text_input.c
        ICONS   /home/vixin/.ufbt/build/esp32_gravity/uart_terminal_icons.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/storage.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/sync.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/uart_terminal_app.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/uart_terminal_uart.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/uart_validators.c
        CC      /home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/uart_text_input.c
        CC      /home/vixin/.ufbt/build/esp32_gravity/uart_terminal_icons.c
/home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/storage.c: In function 'writeDataToFile':
/home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/storage.c:219:40: error: unused parameter 'app' [-Werror=unused-parameter]
  219 | bool writeDataToFile(UART_TerminalApp* app, File* file) {
      |                      ~~~~~~~~~~~~~~~~~~^~~
/home/vixin/Flipper-Xtreme/applications_user/Flipper-Gravity/storage.c:219:51: error: unused parameter 'file' [-Werror=unused-parameter]
  219 | bool writeDataToFile(UART_TerminalApp* app, File* file) {
      |                                             ~~~~~~^~~~
cc1: all warnings being treated as errors
scons: *** [/home/vixin/.ufbt/build/esp32_gravity/storage.o] Error 1

I'm going to try and build it in a Debian VM on my homelab instead and see if that fares any better.

Error there as well:
$ ufbt
22:56:05.849 [I] Deploying SDK for f7
22:56:05.850 [I] Fetching version info for UpdateChannel.RELEASE from https://update.flipperzero.one/firmware/directory.json
22:56:06.367 [I] Using version: 0.95.0
22:56:06.368 [I] uFBT SDK dir: /home/princessvixin/.ufbt/current
22:56:09.672 [I] Deploying SDK
22:56:10.324 [I] SDK deployed.
Checking for tar..yes
Checking if downloaded toolchain tgz exists..no
Checking curl..yes
Downloading toolchain:
######################################################################################################################################### 100.0%done
Removing old toolchain..done
Unpacking toolchain to '/home/princessvixin/.ufbt/toolchain':
################################################## 100.0%
done
Cleaning up..done
scons: Entering directory `/home/princessvixin/.ufbt/current/scripts/ufbt'
        CC      /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene.c
        CC      /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c
        CC      /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c
        CC      /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c
        CC      /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_help.c
In file included from /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:1:
/home/princessvixin/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c:1:
/home/princessvixin/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from /home/princessvixin/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:1:
/home/princessvixin/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from /home/princessvixin/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_attacks_mana.c:1:
/home/princessvixin/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c:1:
/home/princessvixin/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from /home/princessvixin/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_attacks.c:1:
/home/princessvixin/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_help.c:1:
/home/princessvixin/Flipper-Gravity/scenes/../uart_terminal_app_i.h:114:6: error: redundant redeclaration of 'syncProcessResponse' [-Werror=redundant-decls]
  114 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
In file included from /home/princessvixin/Flipper-Gravity/scenes/../uart_terminal_app_i.h:15,
                 from /home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_help.c:1:
/home/princessvixin/Flipper-Gravity/scenes/../sync.h:11:6: note: previous declaration of 'syncProcessResponse' was here
   11 | bool syncProcessResponse(UART_TerminalApp *app);
      |      ^~~~~~~~~~~~~~~~~~~
/home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:5:1: error: unknown type name 'TickType_t'
    5 | TickType_t launchTime;
      | ^~~~~~~~~~
/home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c: In function 'uart_terminal_console_output_handle_rx_data_cb':
/home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:34:5: error: unknown type name 'TickType_t'
   34 |     TickType_t delay = pdMS_TO_TICKS(10000);
      |     ^~~~~~~~~~
/home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:34:24: error: implicit declaration of function 'pdMS_TO_TICKS' -Werror=implicit-function-declaration]
   34 |     TickType_t delay = pdMS_TO_TICKS(10000);
      |                        ^~~~~~~~~~~~~
/home/princessvixin/Flipper-Gravity/scenes/uart_terminal_scene_console_output.c:35:9: error: implicit declaration of function 'xTaskGetTickCoun' [-Werror=implicit-function-declaration]
   35 |     if (xTaskGetTickCount() - launchTime >= delay) {
      |         ^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scons: *** [/home/princessvixin/.ufbt/build/esp32_gravity/scenes/uart_terminal_scene_console_output.o] Error 1
cc1: all warnings being treated as errors
cc1: all warnings being treated as errors
scons: *** [/home/princessvixin/.ufbt/build/esp32_gravity/scenes/uart_terminal_scene_help.o] Error 1
scons: *** [/home/princessvixin/.ufbt/build/esp32_gravity/scenes/uart_terminal_scene_attacks.o] Error 1
cc1: all warnings being treated as errors
scons: *** [/home/princessvixin/.ufbt/build/esp32_gravity/scenes/uart_terminal_scene_attacks_mana.o] Error 1


TreeView drag&drop reordering inside a TreeView[Item] using ItemsSource crashes

Describe the bug
When using the TreeView with an ItemsSource and Binding the TreeViewItems' ItemsSource, reordering the items inside one node by drag and drop will crash.
Reordering with ALT+SHIFT+[UP/DOWN] is works fine.
Drag and Drop into any position in any other Node works fine (when enabled, is disabled in reproduction code (given below) for simplicity).
Steps to reproduce the bug
Steps to reproduce the behavior:

Clone and Build the NodesVsItems branch from https://github.com/Shad0wlife/TreeViewCrashSampleApp
The TreeViews in this App have explicitly disabled dragging Items into other parents but enabled reordering, to make handling easier. This would happen as well, if dragging were enabled, but it's (subjectively) harder to drop the item to reorder.
The Application opens on a TreeView that is set up to only directly use the TreeViewNodes and their Children. Here, you can drag and drop reorder items. Bug here: It is possible to "reorder" an Item outside its parent. Collapsing and re-expanding said parent will move it into the correct spot inside again. (Probably caused because of the ListView reorder code that is used that I read about somewhere in the code)
You can switch to the mode using TreeView.ItemsSource and TreeViewItem.ItemsSource by clicking the Button "Switch to Content Mode"
Here, when you reorder by Drag&Drop, if the Item is dropped anywhere else than its original spot, the programm will crash.

Expected behavior
In Content Mode, when reordering by drag and drop inside the same node, the moved item gets moved inside the corresponding ItemsSource and the Program does not crash.
In node mode, I would suggest snapping the target node back into its parent if it gets moved outside the parent's "scope" without actually changing the target's parent. This is just an observation and not the main point of the bug report though.
Screenshots
The node mode reordering issue with moving a node out of its parent visually but not technically visualized:

Version Info

NuGet package version:
Microsoft.UI.Xaml 2.4.0-prerelease.200422001
Microsoft.UI.Xaml 2.4.3
Microsoft.UI.Xaml 2.5.0-prerelease.200812001

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

November 2019 Update (18363)
Yes

May 2019 Update (18362)

October 2018 Update (17763)
Yes

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Mobile

Xbox

Surface Hub

IoT

Additional context
This comment in the TreeViewItem's code suggestes that if Drag&Drop into new parents does not happen, the backing ListView's reorder code will run. My guess is that since then, the change only happens in the ListViews items and is not synced into the TreeViewItem's ItemsSource, maybe the mismatch happening there is part of the problem. Maybe the TreeView needs its own reorder code to be able to reflect the changes made into the ItemsSources.

Updated version info after checking on new package and Windows versions. Crash still happens.


Ron Darby Profile

Hi @RonDarby
Thanks for your submission. It looks like you missed Step Three  of loading your Profile in to the kernel so your profile is not yet loading.
Add this quick and I'll get your merge accepted

lol, ya, I only did one of the step 3's, skimmed over to step 4

No worries :)
Thanks for the update to the ReadMe.
Dont forget to tweet, come say hi and grab a sticker


Update diagnostics: take 2, updated custom handler

An alternative to #447.
This addresses both issues I listed in #447, but requires me to maintain more code.

Will go with #447.


Changes to upgrade kubeone to 1.4.0

What this PR does / why we need it:

upgrade kubeone to 1.4.0
install lazygit, zsh, oh-my-zsh, powerlevel10k for oh-my-zsh
fix fzf auto completion
remove minio kubectl plugin

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/assign @toschneck

two smaller things I would think we should change

/assign @dharapvj

two smaller things I would think we should change
I could only find minio plugin issue as open.. I reverted that change to remove minio krew plugin and pushed new version to quay.io. Please recheck the PR

/assign @toschneck

/approve

/lgtm

/retest

/lgtm


tools: add numasched: trace task switch between NUMA

Tasks frequently switch between NUMA, often resulting in poor performance.
since commit 121f73df1cb8("Add builtin 'numaid'") bpftrace support 'numaid' builtin. As described in the commit notes that introduced 'numaid', programs running on the same NUMA will have better performance (usually at the memory level). If processes are migrating between different CPUs and these CPUs belong to different NUMAs, this tool provides an effective means of tracing to optimize the program or configuration.
For example:
NUMA info:
  $ numactl --hardware
  available: 4 nodes (0-3)
  node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
  node 0 size: 97373 MB
  node 0 free: 1756 MB
  node 1 cpus: 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
  node 1 size: 98192 MB
  node 1 free: 1269 MB
  node 2 cpus: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
  node 2 size: 98192 MB
  node 2 free: 4811 MB
  node 3 cpus: 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95
  node 3 size: 98135 MB
  node 3 free: 1617 MB
  node distances:
  node   0   1   2   3
    0:  10  12  20  22
    1:  12  10  22  24
    2:  20  22  10  12
    3:  22  24  12  10

Running 'yes' task:
  $ taskset -c 1 yes >/dev/null                   # running on NUMA0

Then, taskset 'yes' to other NUMA:
  $ taskset -p 0x1000000 $(pidof yes)             # NUMA0 -> NUMA1
  $ taskset -p 0x1000000000000 $(pidof yes)       # NUMA1 -> NUMA2
  $ taskset -p 0x1000000000000000000 $(pidof yes) # NUMA2 -> NUMA3

numasched.bt shows:
  $ sudo ./numasched.bt
  Attaching 3 probes...
  Tracing task numa switch.
  TIME     PID      SRC_NID     DST_NID  COMM
  16:30:43 915504   0        -> 1        yes
  16:30:44 915504   1        -> 2        yes
  16:30:46 915504   2        -> 3        yes

There's the same question that @brendangregg raised earlier - should new tools go to bpftrace rather than bcc/libbpf?
This one may be an exception, though, since bcc doesn't seem to have the numa builtin and can't provide this detailed information (the exact numa numbers between which the migration happens).

I tried using bcc to tracgk the migration between NUMA, but found it more difficult.

I tried using bcc to track the migration between NUMA, but found it more difficult.

what makes it more difficult?

There's the same question that @brendangregg raised earlier - should new tools go to bpftrace rather than bcc/libbpf?

I think it's ok to add some tools here to provide real world examples. We do however have to be careful that the tool is correct and doens't cause to much maintenance

This one may be an exception, though, since bcc doesn't seem to have the numa builtin and can't provide this detailed information (the exact numa numbers between which the migration happens).

isn't it just a single helper call to get the info?

I just wrote a bcc version numasched in https://github.com/iovisor/bcc/pull/4396, It has to be said that bpftrace looks more concise.

Rebase to master.

Hi @Rtoax , the consensus is we want to keep community contributed tools in a new repo. Please subscribe to https://github.com/iovisor/bpftrace/issues/2829 if you want to be notified when it's created

Repo has been created: https://github.com/bpftrace/user-tools
Please send PRs!


Allow additional options for request-promise.

What is the usecase of this?
Tbh I think we should make the whole data fetching pluggable which would allow you to pass in your own options and even chose whether you're going to use request-promise, node-fetch or something else.

As you can see bellow by link the request has set of options.
https://github.com/request/request#requestoptions-callback
And as example I have tried to decode gzip'ed traffic by const requestOptions = { gzip: true };

But may be the best way to pass initial graphQL schema options like object
graphQLSchema({   pathToSwaggerSchema,   proxyUrl,   customHeaders,   requestOptions, })

@0xR that would be quit painful to write converters from swagger to all possible http libs options

For me this pull request sounds quite useful. I miss possibilities to set stuff like in https://github.com/swagger-api/swagger-js. At the moment we use this in our hand crafted GraphQL API´s to make calls in the resolvers. A lot of stuff has to be reconfigured. It would be fantastic to have those possibilites with swagger-to-graphql. I think a fetch like interface is very popular to most developers.

We don't have to support all http libs. We can provide a URL, headers and a
request body and users can patch this in their own library however they
want. We can still default on request-promise but allow any override, like
node-fetch, as well.
Op vr 15 jun. 2018 15:28 schreef Roman Krivtsov<EMAIL_ADDRESS>
@0xR https://github.com/0xR that would be quit painful to write
converters from swagger to all possible http libs options
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yarax/swagger-to-graphql/pull/79#issuecomment-397605470,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGH2MDe6YAvmwwmt99yeTwDQW75hac93ks5t86iAgaJpZM4UiRPK
.

@0xR please provide a example, that would be helpful

Something like this:
  const myFetcher = (url, fetchOptions) => {
    fetch(url, { ...fetchOptions, otherOption: 'new value' });
  }
  app.use('/graphql', graphqlHTTP(() => {
    return {
      schema,
      graphiql: true,
      fetch: myFetcher
    };
  }));

True, also it makes possible to use unit tests with DI for us. But in most cases users just need to pass additional headers and writing the request function would be overkill for them. so probably it would make sense to have transformed function for those arguments and the request function to pass through, and all of them are optional

I'm sure we can think of something userfriendly. If we have the callback we can implement any userfriendlyness by just providing our own callbacks.
If only I had time to implement all this...

But in any case user will have to map path, query string, headers and body manually to its own HTTP function. So it's still fine for people who really want a deep customization and we can do it, but if you want to add just an editional header and don't care about HTTP implementation, then probably transform function like
({path, headers, qs, body}) => {path, headers, qs, body}

would be more useful. So we give give both possibilities

+1 on this (and BTW: thanks for the great library).
I want to be able to modify the request options at the time the request-promise object is created.  I was thinking a callback function would be ideal: it would get passed the 'req' object before it is used to create the request-promise.
Something like this (adapted from index.js):
// ADDITIONAL ARGUMENT 'reqFunc'
const resolver = (endpoint: Endpoint, proxyUrl: ?(Function | string), customHeaders = {}, reqFunc = null) =>
  async (_, args: GraphQLParameters, opts: SwaggerToGraphQLOptions) => {
    const proxy = !proxyUrl ? opts.GQLProxyBaseUrl : (typeof proxyUrl === 'function' ? proxyUrl(opts) : proxyUrl);
    const req = endpoint.request(args, proxy);
    if (opts.headers) {
      const { host, ...otherHeaders } = opts.headers;
      req.headers = Object.assign(customHeaders, req.headers, otherHeaders);
    }
    // UPDATED LINE HERE
    const res = await rp(reqFunc == null ? req : reqFunc(req));
    return JSON.parse(res);
  };

My intention is to be able to have an opportunity to modify the 'req' object before it is actually used to create the request-promise.

I agree with @ateamlunchbox having a callback to give access view and modify the full request object before sending is a way better way to go.
As an example, a project I'm working on needs to sign the service calls before sending them incorporating the full path + query parameters and a hashed version of the body which currently there is no way to do, in addition I also have to implement the gzip: true flag for the request.
Simply allowing for additional parameters to be added to the request creation as @Andrey-Kovinjonok has done doesn't cover enough use cases.

Tanks for a great library.     Is that possible ?


Angular 4 Universal project - problem with "Unexpected token import"

Hi, I use your library, but it's impossible to build a project with this library for Angular 4 Universal server. It's look like a problem with you library export files - you can find more details about this problem hire:
https://github.com/angular/angular-cli/issues/7200
especially in Toxicable commented on Sep 12.
What I finnally see is:
> ts-node src/server.ts

/home/xxxx/Projects/private/angular4-cli-seed/node_modules/localize-router/src/localize-router.config.js:1
(function (exports, require, module, __filename, __dirname) { import { Inject, OpaqueToken } from '@angular/core';
                                                              ^^^^^^

SyntaxError: Unexpected token import
    at createScript (vm.js:74:10)
    at Object.runInThisContext (vm.js:116:10)
    at Module._compile (module.js:588:28)
    at Module._extensions..js (module.js:635:10)
    at Object.require.extensions.(anonymous function) [as .js] (/home/xxxx/Projects/private/angular4-cli-seed/node_modules/ts-node/src/index.ts:384:14)
    at Module.load (module.js:545:32)
    at tryModuleLoad (module.js:508:12)
    at Function.Module._load (module.js:500:3)
    at Module.require (module.js:568:17)
    at require (internal/module.js:11:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `ts-node src/server.ts`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

--- EDIT
Temporary I use this solution: https://stackoverflow.com/questions/46873887/unexpected-token-import-when-use-localize-router-in-angular-4-universal-app?noredirect=1

Thanks for bringing this up. I will look into it

Can this problem be solved using webpack-node-externals module?
I'm running an Angular 4 Universal project with it with no problems.
On Oct 24, 2017 8:59 PM, "Miroslav Jonaš"<EMAIL_ADDRESS>wrote:

Thanks for bringing this up. I will look into it
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Greentube/localize-router/issues/82#issuecomment-339030520,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH7MPktv1j32yKrp5qnounzMCBgqlotyks5svgJWgaJpZM4QCBeZ
.

@umeshkumawat I think that Babel or recompile are only solutions for this issue.


Arhaan Memon - Personal Issue for 3.1 and 3.4 lesson

Assignment
Points
Grade
Evidence

Baseline Grade
55%

Max Grade
90%

Pull Request (Integration)
1

Relevancy Checklist (Peer)
2

Lesson Style (Period)
1

Homework, Popcorn Hacks
1 x 5

Individual Contribution
1

Personal Notebooks / Blogs
1

Total
11

Skill
Points
Grade
Evidence

Work Habits (Analytics)
1

Team Planning (Issue)
1

Presentation Memories
1

Grading and Feedback
1

Beyond Perfunctory
1

Had an organization table that was very easy to read through and look through
Created a profile project that includes topics from all throughout the sprint
Learned from homework, and I think this is well shown!
Understanding difference between booleans, conditionals and nested conditionals.
Enjoyed 3.2 lesson :)

Created a large final project with the cumulation of all the projects (It was a uno game, where he implemented if else, variables, and more).
He also talked about what he needed to improve on, and where he believes he could get better.
Discussed team teaching collaboration skills.

Has a table that is easy to use and find whatever you need.
Created a final project that showcases all the concepts he learned like strings, conditionals, etc.
Nice overall summary showing how he understands the core concepts of the lessons and can understand the key and the less important concepts.
Learned a lot about conditions like If/Else statements.
Nice website!

Hi Arhaan,
I liked that you had a clear and concise table with summaries and links to each lesson. It was also cool that you created an uno game that includes all the different units and it really showed that you learned a lot from the lessons. I like how you discussed that the team teach helped build your collaboration skills,

Had a very complex uno game! Had an in-depth summary of learning. It might be nice to split this up into chunks so that when you look back at it it is easier to understand what you learned. I like how you felt that the team teach helped you improve your collaboration skills and your javascript skills.

Hi Arhaan, I like your final project of the uno game. I also like your overall summary that included things you could improve on.

Created a table with the links and summary already shown a little description. Made a uno game using if/else statements. Has an overall summary of everything he's learned and needs improving on, improved on if/else statements. good explanation and a great uno game

He had a big table that had links to lessons and summaries. Below each link, he had small summaries of each of the lessons. I really liked how everything was formatted neatly.  He also had an overall summary that  included things he needs to improve on as well as things he learned. He talked about how his collaborating skills increased, which is great.

I like the summary that you added at the very end summarizing everything you learned and what you need to improve on. You also had a great uno game, implementing if/else statements.

You had a great uno game, and I liked how you have small summaries of each lessons. Your formatting was great. Good job Arhaan!

I liked your uno game and your implementation of the topics your learned into it

I liked your uno game and also your summaries were very great.


Remove the hero module

Out of all of the modules to me stands out the hero module as being too specific. I feel it shouldn't be in this project.

maybe we could move this to the examples/hero/ directory. I think it's a reasonable module, I just suspect that it's not something people are actually using in their own code. Probably shouldn't be a built-in module.

Yes. Move to examples. Good idea.


del host initiator

This PR add new feature for host-initiators (storage), the ability to delete an existing host-initiator.

Links

https://github.com/ManageIQ/manageiq-ui-classic/pull/8249
https://github.com/ManageIQ/manageiq-providers-autosde/pull/147
https://github.com/ManageIQ/manageiq-api/pull/1157

update:
merged sporadic test failure
Hope that will get this green

Backported to najdorf in commit 453a4b3f605f804fb87bf1a5cdf19aea307a1fc2.
commit 453a4b3f605f804fb87bf1a5cdf19aea307a1fc2
Author: Adam Grare<EMAIL_ADDRESS>Date:   Wed May 4 09:18:11 2022 -0400

    Merge pull request #21845 from Autosde/delete_host

    del host initiator

    (cherry picked from commit 3eb4856d12cb0d6deb12093fd7a649fd68201067)


Change of name

Hola hombres!
I really like the name bombillo! But what I think is a little redundant is the "el". When I talk about "el bombillo" I usually just omit the "el" so I can articulate the name faster. Additionally I noticed that all the big brands don't use articles for their products and even "the facebook" is just "facebook" nowadays.
So, I would like to change the name to "bombillo".
What do you think?

:+1:

Wow you're quick!
I liked the name as a circle beneath the bulb better..

I think the "El" is fun when you talk about the project, but for end users it might be easier to just call it "Bombillo". :+1:


Thanks for this package

This is not an issue, just thanks for creating this package.
Incorporated and testing using prange and all works as intended.
Massively useful.

Thanks! I'm glad this is useful for someone :).


Source compilation by gitea, web side CSS style is invalid

Gitea version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
Windows source compilation gitea, web side CSS style failure, how should I solve?
...
Screenshots

Please give more details.

Please give more details.

As shown, the page works fine, but there is no style effect

How did you compile gitea?

How did you compile gitea?

I downloaded the source code from the master branch and ran "go build" from the console, then ran "./gitea web".

go build by itself will definitely not be enough. :sweat_smile:
Please follow the steps in the documentation regarding building from source. :slightly_smiling_face:

这是一个编译方法不对的问题，TAGS="bindata" make build，这是正确的方法

这是一个编译方法不对的问题，TAGS="bindata" make build，这是正确的方法

Thanks,you are right.I follow the steps in the documentation to reconfigure the environment,and run TAGS="bindata sqlite sqlite_unlock_notify" make build,It turns out to be right.


Splitters

Many screens will benefit from splitters. We should try and find a solution that we can easily use in many different screens

With the new KendoUI architecture, the overhead of using a few selected "widgets" should be minimal

fixed this as part of https://github.com/monterey-framework/monterey/issues/218


Improve ColumnTemporalContinuousSection

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ff82ea2) 100.00% compared to head (f65dd63) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #208   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           69        69
  Lines         1670      1679    +9
  Branches       175       176    +1
=========================================
+ Hits          1670      1679    +9

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Support for ingestion time partition table on BigQuery as incremental materialization

resolves https://github.com/dbt-labs/dbt-bigquery/issues/75
-->
Description
Support for ingestion time partition table on BigQuery as incremental materialization
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt-bigquery next" section.

@Kayrnt you're very close here. correct me if I'm wrong, but my understanding is that you'd like to:

for a given relation (table/view), give me the column type for each column.

The way to do this is with column_type column of the table returned by the get_catalog() (bigquery__get_catalog()) macro.
Not only do I totally understand the approach you're taken, but I've also made the same mistake a few times. Your call statement('get_columns_with_types_in_query'.... construction was sound, and it will return an empty table with column names.
The problem is with load_result which takes the json returned by the call statement and converts it into an Agate table. When Agate is given data to turn into an Agate table, there's a specific way it guesses the type of each columnn provided by looking at the values in each column. Because there are no example values for each column, Agate defaults to assuming they are Number type. If you're interested, you can read more on Agate Data Types,  Agate's type inference, and how dbt-core modifies the Agate's type inference and even adds a new type in agate_helper.py.
However, you are correct that directly querying BQ via an API will return the column types, however, AFAICT, there's nothing in dbt-core or dbt-biqquery that uses the metadata in every query response and passes the needed types to Agate before loading. Perhaps it could be though starting with BigQueryConnectionManager.get_table_from_response(). Agree or disagree: @VersusFacit @McKnight-42 @jtcohen6?

Finally got a chance to look in slightly more detail. Very cool work!
I wonder if, rather than futzing with the addition of fields() to all AdapterResponse objects, what we really want is a BigQuery-specific implementation of get_columns_in_query. This would be comparable to the default implementation, but using a similar underlying approach to get_columns_in_relation (i.e. leveraging the Python client).
Something like:
{% macro bigquery__get_columns_in_query(select_sql) %}
  {% set sql %}
    select * from (
      {{ select_sql }}
    ) as __dbt_sbq
    where false
    limit 0
  {% endset %}
  {{ return(adapter.get_columns_in_select_sql(sql)) }}
{% endmacro %}

Leveraging a new adapter method like:
    @available.parse(lambda *a, **k: False)
    def get_columns_in_select_sql(self, select_sql: str) -> List[BigQueryColumn]:
        try:
            conn = self.connections.get_thread_connection()
            client = conn.handle
            query_job, iterator = self.connections.raw_execute(select_sql)
            query_table = client.get_table(query_job.destination)
            return self._get_dbt_columns_from_bq_table(query_table)

        except (ValueError, google.cloud.exceptions.NotFound) as e:
            logger.debug("get_columns_in_query error: {}".format(e))
            return []

Following the integration test example, that returns for me:
  {%- set columns = get_columns_in_query(sql) -%}
  {%- do log(columns, info = true) -%}

[<BigQueryColumn id (INT64, NULLABLE)>, <BigQueryColumn field1 (STRING, NULLABLE)>, <BigQueryColumn field2 (STRING, NULLABLE)>]

Thanks a lot for the feedback & the details @jtcohen6, I'll try that!
Putting it in the AdapterResponse felt like it was a good way to provide the information for other usages but since it brings serialization issues you're probably right about isolating that usage.

@Kayrnt fantastic work on this! looks like we've developed a conflict in some files if you can update to get tests rerunning that would be fantastic. if you can't please let me know.

Hello @McKnight-42, thank you for having a look. I can't commit on a timeline till the very end of May as explained in my latest Slack message:
https://getdbt.slack.com/archives/C030A0UF5LM/p1651225949330499?thread_ts=1648824631.462679&cid=C030A0UF5LM
Feel free to take over if you want 👍
I would love to see the features shipped in the next release!

@Kayrnt alright I will look into clearing up the conflicts and see where we can get it as time allows. feel free to hop back onto when you can and stay involved!!!!

I can comment and review a bit but next days will be busy on my end so expect some delay. Good luck on conflicts, it's a good opportunity to deeply review the code 😉

Hello, how is it going on your end? I'm still traveling till the end of May but I'm looking forward to making progress on that PR to discuss #167 :+1:

Hey @Kayrnt! J'espère que tu profites bien des vacances. Sorry for the lack of response on our end these past few weeks.
As part of our work for v1.2, we're planning to meaningfully refactor the incremental materialization, starting with incremental strategies (https://github.com/dbt-labs/dbt-core/issues/5245). The code here has gotten a bit out of hand, and it's become quite tricky for us to maintain, especially as we onboard new folks to help out.
We also rolled out a new more intuitive testing framework in v1.1, which uses more standard pytest builtins. We're converting all our old integration tests to use the new framework. In any place where we're adding new functionality, and extending old-school test cases to test it, we're taking it as an opportunity to first convert those tests.
The capabilities added here and in #167 are ones I'd very much like to support, ideally in dbt-bigquery==1.2.0. I'm immensely grateful for all your work in these issues and PRs, all the way to working reference implementations! After discussing with the Core engineering team, we think the right move is to "freeze" new additions to the incremental materializations, in dbt-core and in our adapter plugins, while we pursue that refactor. After the code is cleaner and the interfaces are clearer, I have a lot of appetite to help get this functionality merged in. That may look like helping you rebase these changes, if you have the availability/stamina next month. If you don't (which is 100% reasonable), one of us can adapt these PRs, and take them over the finish line.

Hello @jtcohen6, tout se passe bien de mon côté mis à part pour tous les coups de soleil que j'ai reçu !
Ok no wonder, you're busy I had a quick look at your core roadmap and there is definitely a lot of work to ship everything!
Thank you for all the details you're sharing with the community!
I'll have a proper read once I get back as I'm curious about some plans but it's another topic.
Anyway I understand there is a lot of refactoring to be done to be able to move forward confidently and scale your team.
Hopefully it's also an opportunity for the dbt labs team to write down a more comprehensive documentation for contributors to understand the high level structure, the development environment and CI process if you find time to. It is already nice but I think I could have avoided you some questions and save a lot of time with some more details.
I'll likely be able to support the PRs over the next months (hopefully it won't be as much work as the original implementation).
In the meantime, I might use my fork in my organization as we're maintaining 2 systems because of those missing features. It might be an opportunity to find out some flaws till it's available to all users.
I'm following #dbt-core-development on Slack, let me know if there is another more appropriate channel to keep up with the changes. Let me know if I can help a bit (or provide feedback if you need some).

I've rebased the change to work with the python.
The code should be properly tested and tests appears to pass.
I'll have few tests locally to confirm it works as intended but you can rereview the code.

What's the status on your end @jtcohen6 @McKnight-42? It would be sad to miss the 1.3 release 😉
@dataders I think you'll have to dismiss your review because it looks like I can't (and I think I made the change since then, but feel free to review 🙌 ). Thanks!

@github-christophe-oudar shined a light on this one while testing locally as part of review looking good, hoping to get it merged soon!

It looks like the stars are about to align then! ⭐ ⭐ ⭐
After that I'll rebase https://github.com/dbt-labs/dbt-bigquery/pull/167
Let's be ambitious and try to merge both in September 🙌

👋
Any chance we merge over the next weeks?
It will become a blocker on my end, so I'm wondering if I need to fork for my organisation.
Thanks 🙇

@cla-bot check


[Peer] addInstanceToPool() failes when a datetime field is part of the primary key

When using setXxxs() with PropelCollection and on an object with a datetime field as part of the primary key it throws an exception:
Catchable Fatal Error: Object of class DateTime could not be converted to string in ....

DateTime does not implement toString so perhaps setting the format to "c" or "U" could solve the problem ?

btw, the problem only occurs when the propel.defaultXXFormat properties are not set.

So, it may be better to set this property by default, instead of patching the code.

that would be an easier fix yes


Java: fix parse_jvm_version vm_name regex pattern

better regex:
e.g. this regex was failed to match the functions' own java -version output example
on my PC it's Java HotSpot(TM) 64-Bit Server VM... so I added support
replaced TODO with an informative comment
tests, including the documented java -version example from parse_jvm_version()

one question I have is why do we need the regex? why can't we just lines[2].startswith() or even if 'HotSpot' in lines[2]?

better regex:
e.g. this regex was failed to match the functions' own java -version output example

You can add the example as a testcase as well :)

@Jongy

You can add the example as a testcase as well :)

tests, including the documented java -version example from parse_jvm_version()

Good @roi-granulate I missed it. Thanks


Help using cpp vit example for inference on images with trained .npz model

First of all thank you very much for all the hard work on making this project available. I have been trying to use the CPP example of the VIT transformer to load a trained model (npz file format). But like the TensorRT (Python) version I haven't been able to find any information on how to load a trained model.
Also I have been trying to expand the CPP example of the VIT transformer code to inference on images, without any success (especially on retrieving the inference results). By any chance is there anyone working on expanding the cpp example of the VIT transformer to do inference on images?
Any help is welcome~ Thanks in advance!

You can found how to load model in ViTPlugin.cpp. We don't load the real model in cpp example because we don't have real input in cpp example.
We don't have work to run cpp end to end example.

Thank you very much for the quick reply. Then by any chance could u also tell me how to parse the Output Tensor. So that I can receive the classification result from the cpp output tensor?

You can get, print or store the output tensor of vit_example.cc directly

Close this bug because it is inactivated. Feel free to re-open this issue if you still have any problem.


TestBinder does not support PollableMessageSource

public interface PollingSink {
	String INPUT = "input";

	@Input(PollingSink.INPUT)
	PollableMessageSource input();
}

java.lang.ClassCastException: org.springframework.cloud.stream.test.binder.TestSupportBinder cannot be cast to org.springframework.cloud.stream.binder.PollableConsumerBinder
at org.springframework.cloud.stream.binding.BindingService.doBindPollableConsumer(BindingService.java:173)
at org.springframework.cloud.stream.binding.BindingService.bindConsumer(BindingService.java:113)
at org.springframework.cloud.stream.binding.BindableProxyFactory.createAndBindInputs(BindableProxyFactory.java:234)

@dturanski I have exactly the same issue. I have introduced a pollable message source and I ended up with the same error as you. It is blocking for me as it influences as it makes all my tests fail.

At the moment we are not planning to add this feature to this test binder.
We actually have a new test binder which does support pollable message source and you can see the example here. Also if you want o use it in your project here are the important maven bits you will need

@olegz Is it already released? Is it referenced somewhere in the documentation? Because for the moment in the documentation only this artifact is referenced
 testImplementation("org.springframework.cloud:spring-cloud-stream-test-support")
and by default this artifact instantiate a test binder which is not compatible with pollableMessageSource

Yes it is. It's been out since 2.0, we just didn't publicize/blog about it.
Also, to use it and not deal with conflicts, remove spring-cloud-stream-test-support from your dependencies

@olegz Just for my understanding which isn't it the public solution if it supports more use case?

Not sure I understand the question, but it is intended for public consumption and we will fully document it. It just didn't happen yet

We actually have a new test binder which does support pollable message source and you can see the example here. Also if you want o use it in your project here are the important maven bits you will need

Example mentioned above (SampleStreamApp) is not working for me. It writes
Polled payload: polled data
Handling payload: Hello

But i believe should be
Polled payload: Hello
Handling payload: Hello

??

@olegz and @VictorKrapivin  Do you have an example of project, not inside the spring sources, which shows how to instantiate this test binder? I am struggling with the Maven/Gradle dependencies that I should use and the configuration to set up to instantiate that test binder!

@ghilainm I'm not sure this will be helpful, but here is https://gist.github.com/VictorKrapivin/83c7e41efedce14db98c28bfb37622c8 my pom.xml
Java code is the same as https://github.com/spring-cloud/spring-cloud-stream/blob/master/spring-cloud-stream/src/test/java/org/springframework/cloud/stream/binder/test/SampleStreamApp.java

+1 for requesting some documentation about this new test binder, especially with something like gradle.

I've changed this issue to 'document`, so we'll do before the release. Meanwhile, here is what you need to defined as your dependency to include it into your project
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-stream</artifactId>
    <version>${project.version}</version>
    <type>test-jar</type>
    <scope>test</scope>
    <classifier>test-binder</classifier>
</dependency>
. . .
<plugins>
    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-jar-plugin</artifactId>
        <version>3.0.2</version>
        <executions>
	    <execution>
		<configuration>
		    <includes>
			 <include>**/integration/*</include>
		    </includes>
		    <classifier>test-binder</classifier>
		</configuration>
                <goals>
                    <goal>test-jar</goal>
                </goals>
            </execution>
        </executions>
    </plugin>
</plugins>

You can retrofit the above to Gradle i guess

We actually have a new test binder which does support pollable message source and you can see the example here. Also if you want o use it in your project here are the important maven bits you will need

Example mentioned above (SampleStreamApp) is not working for me. It writes
Polled payload: polled data
Handling payload: Hello

But i believe should be
Polled payload: Hello
Handling payload: Hello

??

@olegz I'm able to get the binder working now too.  I didn't notice the comments within the TestChannelBinder class.
But I'm also having the same issue that @VictorKrapivin is running into -- whatever data I'm consuming with the PollableMessageSource always returns the string polled data.  Can you point me to a test using the new test-binder where this isn't the case?


add nonce for replay protection

Signed-off-by: Gregory Hill<EMAIL_ADDRESS>
Always incrementing nonce per account
Move referee from Option.sol to Obligation.sol

Discussed with @alexeiZamyatin offline, we most likely don't need the nonce if we manage a blocklist of previously submitted transaction IDs. In this case we would still require that the writer has a 'fresh' address or we could alter our relay to check the Bitcoin block timestamp.

Closing in favor of #30


Composer package

Will you make this a composer package in packagist?

Sorry, seen it already is. Maybe nice to include a small composer require part in the readme so people can see it.

Yes, it is also a packager on packagist.org - https://packagist.org/packages/bueltge/must-use-loader
Maybe you send also a request for the hint inside the readme?

What do you @DannyvanHolten think, is this enough to find a little bid help?

Yeah :) Very good. Thanx :)

Now, the new release is public, also on packagist.
Thanks for your help and hints.


Expire Never shows up in Grocy as Expiring Today

I created this product while in the store, with the never expire option selected. When it shows up in grocy it expires today. The product looks correct with -1 in the product details.

Oh no! This was a bug in earlier versions of the app. Do you have the
most recent version? Did this happen when you used the purchase screen?
On Tue, Jul 28, 2020 at 4:28 PM kses<EMAIL_ADDRESS>wrote:

I created this product while in the store, with the never expire option
selected. When it shows up in grocy it expires today. The product looks
correct with -1 in the product details.
https://user-images.githubusercontent.com/17168512/88711648-c7385700-d118-11ea-846d-7388d28209b4.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PantryParty/pantry_party/issues/97, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABQ6MRY7FRLWNC4Y5E2ZR3R54YHPANCNFSM4PK4RMRQ
.

It should be the latest. I can not find anywhere to check, but it auto updates (iOS).
Purchase view and creating new product. No issues with existing products.


copy-dbacredential: add support for cryptographic providers

Type of Change

[ ] Bug fix (non-breaking change, fixes # )
[x] New feature (non-breaking change, adds functionality, fixes #7896 )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[x] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Unit test is included
[ ] Documentation
[ ] Build system

Purpose

Enable the copy of credentials that use a crypto provider as requested in #7896
Approach

Minor change to check if a crypto provider was used in the source credential and then apply that to the destination/copied credential. If the destination instance does not have the crypto provider than a warning is returned.
Commands to test

See the tests for details. There is a conditional based on whether the test environment has the crypto providers configured at the instance level. It seems safer to assume that the crypto providers are installed separately from the pester test.

Looks good, thank you


Include x-common as submodule

Including this to be able to test if any canonical-data used is up to date with what's in x-common.

By adding this we now have two copies of x-common in the trackler gem. I'd appreciate it if we could find another way.

Hmm... Maybe I can take it out of the repo and clone within Travis. I'll take a look when I get home.

Changes in https://github.com/exercism/xperl6/pull/131, sorry about that 😓

:heart: thanks so much!


Need a license file in the repo

Hi JB. I am just planning to play with these. But it would help if there is a license file in the repo. I am sorry if I missed something.

Hi @anandk266,
I can add a license file, but please note that most of the code here rather old. It may be better to look at my jsfiddle dashboard which has more up to date examples.

https://jsfiddle.net/user/dashboard/

Sorry, make that, https://jsfiddle.net/user/peppertech/fiddles/

Thanks JB. I work for Oracle too :-) I will checkout your fiddles. I just
wanted to know what I can and cannot do with the code in OracleJet-Samples.
Anand
On Fri, Nov 24, 2017 at 10:53 AM, John Brock<EMAIL_ADDRESS>wrote:

Sorry, make that, https://jsfiddle.net/user/peppertech/fiddles/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/peppertech/OracleJET-Samples/issues/1#issuecomment-346745442,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJfy27V4NZlBwOv1t2OZu8kj6HruuZnpks5s5lLDgaJpZM4QpWMJ
.

I'm out for the Thanksgiving holiday break, but when I get back I will make
everything MIT. Do anything you like with the code. Just be aware of it's
age.
On Fri, Nov 24, 2017, 3:50 AM anandk266<EMAIL_ADDRESS>wrote:

Thanks JB. I work for Oracle too :-) I will checkout your fiddles. I just
wanted to know what I can and cannot do with the code in OracleJet-Samples.
Anand
On Fri, Nov 24, 2017 at 10:53 AM, John Brock<EMAIL_ADDRESS>wrote:

Sorry, make that, https://jsfiddle.net/user/peppertech/fiddles/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/peppertech/OracleJET-Samples/issues/1#issuecomment-346745442
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AJfy27V4NZlBwOv1t2OZu8kj6HruuZnpks5s5lLDgaJpZM4QpWMJ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/peppertech/OracleJET-Samples/issues/1#issuecomment-346811722,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMdQlKCMyIW83mJS-6l-LbXuCItEJe6ks5s5q2ZgaJpZM4QpWMJ
.

Thanks JB.
Anand
On Fri, Nov 24, 2017 at 9:12 PM, John Brock<EMAIL_ADDRESS>wrote:

I'm out for the Thanksgiving holiday break, but when I get back I will make
everything MIT. Do anything you like with the code. Just be aware of it's
age.
On Fri, Nov 24, 2017, 3:50 AM anandk266<EMAIL_ADDRESS>wrote:

Thanks JB. I work for Oracle too :-) I will checkout your fiddles. I just
wanted to know what I can and cannot do with the code in
OracleJet-Samples.
Anand
On Fri, Nov 24, 2017 at 10:53 AM, John Brock<EMAIL_ADDRESS>wrote:

Sorry, make that, https://jsfiddle.net/user/peppertech/fiddles/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/peppertech/OracleJET-Samples/issues/1#
issuecomment-346745442
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/
AJfy27V4NZlBwOv1t2OZu8kj6HruuZnpks5s5lLDgaJpZM4QpWMJ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/peppertech/OracleJET-Samples/issues/1#issuecomment-
346811722>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABMdQlKCMyIW83mJS-6l-
LbXuCItEJe6ks5s5q2ZgaJpZM4QpWMJ>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/peppertech/OracleJET-Samples/issues/1#issuecomment-346855208,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJfy2yYjG5bnSe30TloZ8GdrqTWcP1_Kks5s5uPVgaJpZM4QpWMJ
.

files added.  If a project is using Bower, it's out of date and should not be used as an example.  Fair warning.


otLinkOutOfBandTransmitRequest() and otPlatRadioTransmit()

According to #2488, otLinkOutOfBandTransmitRequest() is designed to be in conjunction with other mac operation which includes normal transmission. However, otPlatRadioTransmit() is designed to accept buffer provided by otPlatRadioGetTransmitBuffer() only(see https://github.com/openthread/openthread/blob/master/include/openthread/platform/radio.h#L422), which returns a single static buffer on most example platforms. If  otLinkOutOfBandTransmitRequest() respect the definition of otPlatRadioTransmit() and get the buffer from otPlatRadioGetTransmitBuffer(), it could destroy data of normal transmission, and If otLinkOutOfBandTransmitRequest() ignores the design and constructs its own buffer, it may not be properly processed(at least on platform posix and nrf82540).
Shall we adjust the design of otPlatRadioTransmit() or shall we forbid initiating requests to send normal Thread frame and out of bound frame simultaneously?

Hi Yakun.  It is expected that a module which calls otLinkOutOfBandTransmitRequest would have also called otPlatRadioGetTransmitBuffer to acquire a valid buffer.  Therefore systems that expect to call otLinkOutOfBandTransmitRequest, must implement otPlatRadioGetTransmitBuffer, such that it can provide multiple buffers.  Since the call to otLinkOutOfBandTransmitRequest and the implementation of otPlatRadioGetTransmitBuffer are both implemented by the 3rd party, this should not pose a problem.  Finally, we use this feature internally at Nest.


Columns generated with []string should have their columns pluralized.

When I created a new model, command below, everything was correct, except for the struct tags for the two columns I created. They were singularized, author and topic, but everything else, including the migration is pluralized.
$ buffalo g resource tool name url description:nulls.Text authors:[]string topics:[]string

create_table("tools", func(t) {
	t.Column("id", "uuid", {"primary": true})
	t.Column("name", "string", {})
	t.Column("url", "string", {})
	t.Column("description", "text", {"null": true})
	t.Column("authors", "varchar[]", {})
	t.Column("topics", "varchar[]", {})
})

type Tool struct {
        ...
	Authors     slices.String `json:"author" db:"author"`
	Topics      slices.String `json:"topic" db:"topic"`
}

I can't reproduce with the latest development version, it seems to be fixed:
type Tool struct {
	ID          uuid.UUID     `json:"id" db:"id"`
	CreatedAt   time.Time     `json:"created_at" db:"created_at"`
	UpdatedAt   time.Time     `json:"updated_at" db:"updated_at"`
	Name        string        `json:"name" db:"name"`
	URL         string        `json:"url" db:"url"`
	Description nulls.String  `json:"description" db:"description"`
	Authors     slices.String `json:"authors" db:"authors"`
	Topics      slices.String `json:"topics" db:"topics"`
}


test

Link to feature: https://stoplightio.productboard.com/feature-board/planning/features/8416803