Build fails on Linux

Steps to Reproduce

Create a new project from the command-line.
Run command flutter run
Exception: Build process failed

Expected results:
Expected flutter to run the Linux version.
Actual results:
Error: unused parameter in my_application.cc

Logs

flutter run -v:
[ +125 ms] executing: uname -m
[  +67 ms] Exit code 0 from: uname -m
[        ] x86_64
[  +10 ms] executing: [/home/mhmd/flutter/] git -c log.showSignature=false log
-n 1 --pretty=format:%H
[  +17 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
--pretty=format:%H
[        ] ffccd96b62ee8cec7740dab303538c5fc26ac543
[   +1 ms] executing: [/home/mhmd/flutter/] git tag --points-at
ffccd96b62ee8cec7740dab303538c5fc26ac543
[  +28 ms] Exit code 0 from: git tag --points-at
ffccd96b62ee8cec7740dab303538c5fc26ac543
[        ] 3.3.0
[ +114 ms] executing: [/home/mhmd/flutter/] git rev-parse --abbrev-ref
--symbolic @{upstream}
[  +12 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{upstream}
[        ] origin/stable
[        ] executing: [/home/mhmd/flutter/] git ls-remote --get-url origin
[   +8 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +65 ms] executing: [/home/mhmd/flutter/] git rev-parse --abbrev-ref HEAD
[   +9 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[ +108 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[  +90 ms] executing: /home/mhmd/Android/Sdk/platform-tools/adb devices -l
[  +86 ms] List of devices attached
[  +11 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[   +3 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[ +132 ms] Skipping pub get: version match.
[ +282 ms] Generating
/home/mhmd/Projects/fluttest/android/app/src/main/java/io/flutter/plugins/Genera
tedPluginRegistrant.java
[ +164 ms] Initializing file store
[  +14 ms] Skipping target: gen_localizations
[  +10 ms] gen_dart_plugin_registrant: Starting due to
{InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/home/mhmd/Projects/fluttest/.dart_tool/package_config_subset}
[  +35 ms] gen_dart_plugin_registrant: Complete
[   +1 ms] Skipping target: _composite
[   +3 ms] complete
[   +8 ms] Launching lib/main.dart on Linux in debug mode...
[   +6 ms] /home/mhmd/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/mhmd/flutter/bin/cache/dart-sdk/bin/snapshots/frontend_server.dart.snapsho
t --sdk-root
/home/mhmd/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/
--incremental --target=flutter --debugger-module-names
--experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true --output-dill
/tmp/flutter_tools.UWGRCB/flutter_tool.RKONPJ/app.dill --packages
/home/mhmd/Projects/fluttest/.dart_tool/package_config.json
-Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts
--track-widget-creation --filesystem-scheme org-dartlang-root
--initialize-from-dill
build/c075001b96339384a97db4862b8ab8db.cache.dill.track.dill --verbosity=error
--enable-experiment=alternative-invalidation-strategy
[  +37 ms] Building Linux application...
[  +28 ms] <- compile package:fluttest/main.dart
[   +3 ms] executing: [build/linux/x64/debug/] cmake -G Ninja
-DCMAKE_BUILD_TYPE=Debug -DFLUTTER_TARGET_PLATFORM=linux-x64
/home/mhmd/Projects/fluttest/linux
[ +106 ms] -- Configuring done
[  +14 ms] -- Generating done
[  +21 ms] -- Build files have been written to:
/home/mhmd/Projects/fluttest/build/linux/x64/debug
[   +8 ms] executing: ninja -C build/linux/x64/debug install
[  +17 ms] ninja: Entering directory `build/linux/x64/debug'
[+6807 ms] [1/6] Generating
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/libflutter_linux_gtk.so,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_basic_mess
age_channel.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_binary_cod
ec.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_binary_mes
senger.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_dart_proje
ct.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_engine.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_json_messa
ge_codec.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_json_metho
d_codec.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_message_co
dec.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_method_cal
l.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_method_cha
nnel.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_method_cod
ec.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_method_res
ponse.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_plugin_reg
istrar.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_plugin_reg
istry.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_standard_m
essage_codec.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_standard_m
ethod_codec.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_string_cod
ec.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_value.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/fl_view.h,
/home/mhmd/Projects/fluttest/linux/flutter/ephemeral/flutter_linux/flutter_linux
.h, _phony_
[  +33 ms] [ +147 ms] executing: uname -m
[        ] [ +100 ms] Exit code 0 from: uname -m
[        ] [        ] x86_64
[        ] [  +17 ms] executing: [/home/mhmd/flutter/] git -c
log.showSignature=false log -n 1 --pretty=format:%H
[   +7 ms] [  +13 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
--pretty=format:%H
[        ] [        ] ffccd96b62ee8cec7740dab303538c5fc26ac543
[        ] [   +1 ms] executing: [/home/mhmd/flutter/] git tag --points-at
ffccd96b62ee8cec7740dab303538c5fc26ac543
[  +12 ms] [  +40 ms] Exit code 0 from: git tag --points-at
ffccd96b62ee8cec7740dab303538c5fc26ac543
[        ] [        ] 3.3.0
[        ] [ +226 ms] executing: [/home/mhmd/flutter/] git rev-parse
--abbrev-ref HEAD
[        ] [  +15 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] [        ] stable
[        ] [ +111 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is
not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required,
skipping update.
[        ] [   +7 ms] Artifact Instance of 'WindowsEngineArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not
required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not
required, skipping update.
[        ] [ +208 ms] executing: [/home/mhmd/flutter/] git rev-parse
--abbrev-ref --symbolic @{upstream}
[        ] [  +10 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic
@{upstream}
[        ] [        ] origin/stable
[        ] [        ] executing: [/home/mhmd/flutter/] git ls-remote --get-url
origin
[        ] [  +14 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] [        ] https://github.com/flutter/flutter.git
[        ] [   +2 ms] Artifact Instance of 'MaterialFonts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'GradleWrapper' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is
not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'FlutterSdk' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'WindowsEngineArtifacts' is not
required, skipping update.
[   +3 ms] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not
required, skipping update.
[        ] [   +2 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[   +1 ms] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[  +13 ms] [        ] Artifact Instance of 'FontSubsetArtifacts' is not
required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'PubDependencies' is not required,
skipping update.
[   +3 ms] [ +120 ms] Initializing file store
[        ] [  +18 ms] Done initializing file store
[   +1 ms] [ +156 ms] Skipping target: gen_localizations
[        ] [  +82 ms] Skipping target: gen_dart_plugin_registrant
[        ] [+1674 ms] Skipping target: unpack_linux
[   +2 ms] [+1260 ms] Skipping target: kernel_snapshot
[        ] [ +809 ms] Skipping target: debug_bundle_linux-x64_assets
[        ] [   +2 ms] Persisting file store
[        ] [  +23 ms] Done persisting file store
[        ] [  +10 ms] build succeeded.
[   +6 ms] [  +18 ms] "flutter assemble" took 4,460ms.
[        ] [ +264 ms] ensureAnalyticsSent: 255ms
[        ] [   +1 ms] Running shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [   +1 ms] exiting with code 0
[+2005 ms] [2/6] Building CXX object
CMakeFiles/fluttest.dir/flutter/generated_plugin_registrant.cc.o
[   +2 ms] FAILED:
CMakeFiles/fluttest.dir/flutter/generated_plugin_registrant.cc.o
[  +20 ms] /bin/clang++ -DAPPLICATION_ID=\"com.example.fluttest\"
-I/home/mhmd/Projects/fluttest/linux/flutter/ephemeral -isystem
/usr/include/gtk-3.0 -isystem /usr/include/pango-1.0 -isystem
/usr/include/glib-2.0 -isystem /usr/lib64/glib-2.0/include -isystem
/usr/include/sysprof-4 -isystem /usr/include/harfbuzz -isystem
/usr/include/freetype2 -isystem /usr/include/libpng16 -isystem
/usr/include/libmount -isystem /usr/include/blkid -isystem /usr/include/fribidi
-isystem /usr/include/libxml2 -isystem /usr/include/cairo -isystem
/usr/include/pixman-1 -isystem /usr/include/gdk-pixbuf-2.0 -isystem
/usr/include/gio-unix-2.0 -isystem /usr/include/cloudproviders -isystem
/usr/include/atk-1.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem
/usr/include/dbus-1.0 -isystem /usr/lib64/dbus-1.0/include -isystem
/usr/include/at-spi-2.0 -Wall -Wextra -std=c++20 -g -Wall -Werror -pthread -MD
-MT CMakeFiles/fluttest.dir/flutter/generated_plugin_registrant.cc.o -MF
CMakeFiles/fluttest.dir/flutter/generated_plugin_registrant.cc.o.d -o
CMakeFiles/fluttest.dir/flutter/generated_plugin_registrant.cc.o -c
/home/mhmd/Projects/fluttest/linux/flutter/generated_plugin_registrant.cc
[  +13 ms]
/home/mhmd/Projects/fluttest/linux/flutter/generated_plugin_registrant.cc:10:44:
error: unused parameter 'registry' [-Werror,-Wunused-parameter]
[  +17 ms] void fl_register_plugins(FlPluginRegistry* registry) {
[        ]                                            ^
[        ] 1 error generated.
[  +26 ms] [3/6] Building CXX object CMakeFiles/fluttest.dir/main.cc.o
[ +337 ms] [4/6] Building CXX object CMakeFiles/fluttest.dir/my_application.cc.o
[        ] FAILED: CMakeFiles/fluttest.dir/my_application.cc.o
[   +5 ms] /bin/clang++ -DAPPLICATION_ID=\"com.example.fluttest\"
-I/home/mhmd/Projects/fluttest/linux/flutter/ephemeral -isystem
/usr/include/gtk-3.0 -isystem /usr/include/pango-1.0 -isystem
/usr/include/glib-2.0 -isystem /usr/lib64/glib-2.0/include -isystem
/usr/include/sysprof-4 -isystem /usr/include/harfbuzz -isystem
/usr/include/freetype2 -isystem /usr/include/libpng16 -isystem
/usr/include/libmount -isystem /usr/include/blkid -isystem /usr/include/fribidi
-isystem /usr/include/libxml2 -isystem /usr/include/cairo -isystem
/usr/include/pixman-1 -isystem /usr/include/gdk-pixbuf-2.0 -isystem
/usr/include/gio-unix-2.0 -isystem /usr/include/cloudproviders -isystem
/usr/include/atk-1.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem
/usr/include/dbus-1.0 -isystem /usr/lib64/dbus-1.0/include -isystem
/usr/include/at-spi-2.0 -Wall -Wextra -std=c++20 -g -Wall -Werror -pthread -MD
-MT CMakeFiles/fluttest.dir/my_application.cc.o -MF
CMakeFiles/fluttest.dir/my_application.cc.o.d -o
CMakeFiles/fluttest.dir/my_application.cc.o -c
/home/mhmd/Projects/fluttest/linux/my_application.cc
[   +4 ms] /home/mhmd/Projects/fluttest/linux/my_application.cc:97:48: error:
unused parameter 'self' [-Werror,-Wunused-parameter]
[   +1 ms] static void my_application_init(MyApplication* self) {}
[        ]                                                ^
[        ] 1 error generated.
[        ] ninja: build stopped: subcommand failed.
[  +31 ms] Building Linux application... (completed in 9.6s)
[+11384 ms] Exception: Build process failed
[  +10 ms] "flutter run" took 21,943ms.
[  +12 ms]
           #0      throwToolExit
(package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand
           (package:flutter_tools/src/commands/run.dart:713:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure>
           (package:flutter_tools/src/runner/flutter_command.dart:1209:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand
(package:args/command_runner.dart:209:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure>
           (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand
           (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure>
           (package:flutter_tools/runner.dart:62:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:91:3)
           <asynchronous suspension>

[ +255 ms] ensureAnalyticsSent: 251ms
[   +2 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 1

flutter analyzer:
Analyzing fluttest...
No issues found! (ran in 19.4s)

I don't use Android Studio.
[✓] Flutter (Channel stable, 3.3.0, on Fedora Linux 36 (Workstation Edition)
    5.19.4-200.fc36.x86_64, locale en_US.UTF-8)
    • Flutter version 3.3.0 on channel stable at /home/mhmd/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ffccd96b62 (3 days ago), 2022-08-29 17:28:57 -0700
    • Engine revision 5e9e0e0aa8
    • Dart version 2.18.0
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version
    32.1.0-rc1)
    • Android SDK at /home/mhmd/Android/Sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • ANDROID_SDK_ROOT = /home/mhmd/Android/Sdk
    • Java binary at: /bin/java
    • Java version OpenJDK Runtime Environment (Red_Hat-<IP_ADDRESS>.8-1.fc36)
      (build 17.0.4+8)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at
    google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Linux toolchain - develop for Linux desktop
    • clang version 14.0.5 (Fedora 14.0.5-1.fc36)
    • cmake version 3.22.2
    • ninja version 1.10.2
    • pkg-config version 1.8.0

[!] Android Studio (not installed)
    • Android Studio not found; download from
      https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup
      for detailed instructions).

[✓] Connected device (1 available)
    • Linux (desktop) • linux • linux-x64 • Fedora Linux 36 (Workstation
      Edition) 5.19.4-200.fc36.x86_64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

Hello @muhammadz0. I am able to successfully run the default counter application. Can you provide any more details steps for reproduction of this issue?
Flutter Doctor
flutter doctor -v (Stable)
[✓] Flutter (Channel stable, 3.3.0, on Ubuntu 22.04.1 LTS 5.15.0-46-generic, locale en_US.UTF-8)
    • Flutter version 3.3.0 on channel stable at /home/nabeel/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ffccd96b62 (3 days ago), 2022-08-29 17:28:57 -0700
    • Engine revision 5e9e0e0aa8
    • Dart version 2.18.0
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /home/nabeel/Android/Sdk
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = /home/nabeel/Library/Android/sdk/
    • Java binary at: /home/nabeel/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/brave-browser

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 14.0.0-1ubuntu1
    • cmake version 3.22.1
    • ninja version 1.10.1
    • pkg-config version 0.29.2

[✓] Android Studio (version 2021.2)
    • Android Studio at /home/nabeel/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.70.2)
    • VS Code at /usr/share/code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.1 LTS 5.15.0-46-generic
    • Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

flutter doctor -v (Master)
[✓] Flutter (Channel master, 3.4.0-19.0.pre.39, on Ubuntu 22.04.1 LTS 5.15.0-46-generic, locale en_US.UTF-8)
    • Flutter version 3.4.0-19.0.pre.39 on channel master at /home/nabeel/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision a632ab71db (55 minutes ago), 2022-09-02 06:43:06 -0400
    • Engine revision 5bf3bf0433
    • Dart version 2.19.0 (build 2.19.0-154.0.dev)
    • DevTools version 2.16.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /home/nabeel/Android/Sdk
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = /home/nabeel/Library/Android/sdk/
    • Java binary at: /home/nabeel/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/brave-browser

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 14.0.0-1ubuntu1
    • cmake version 3.22.1
    • ninja version 1.10.1
    • pkg-config version 0.29.2

[✓] Android Studio (version 2021.2)
    • Android Studio at /home/nabeel/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.70.2)
    • VS Code at /usr/share/code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.1 LTS 5.15.0-46-generic
    • Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Should I switch channel to master?

Uh I just did flutter create
Did flutter run again and it worked!

If you are able to reproduce this issue, please do share a sample here so that we can verify and investigate it.

Sorry, I'm not able to reproduce it. However, these "warnings as errors" are pretty common when using GLib or GTK stuff, so I don't use -Werror flag when compiling such things.

Can you provide the following information related to your application that's crashing:

Have you added any custom code in my_application.cc? If so, can you post the contents of the file?
Was the project generated with a previous version of Flutter? Like 3.0 or 2.10? If so, does generating an application with that version, then building it with 3.3 reproduce this issue?

Have you added any custom code in my_application.cc? If so, can you post the contents of the file?
Nope

Was the project generated with a previous version of Flutter? Like 3.0 or 2.10? If so, does generating an application with that version, then building it with 3.3 reproduce this issue?
I did check updates before that IIRC, so I don't think so

Okay thank you for the information. I cannot reproduce this but there may be some other insights the team may give here. Labelling for the same reason. Thank you.

`
[  +56 ms] Connected devices:
[  +33 ms] Linux (desktop) • linux  • linux-x64      • Manjaro Linux 6.6.19-1-MANJARO
[        ] Chrome (web)    • chrome • web-javascript • Google Chrome 123.0.6312.86
[        ] [1]: Linux (linux)
[        ] [2]: Chrome (chrome)
[        ] Please choose one (or "q" to quit)
[        ] :
[+11185 ms] 1
[   +8 ms] Skipping pub get: version match.
[  +27 ms] Found plugin fl_downloader at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/fl_downloader-1.2.0/
[   +5 ms] Found plugin flutter_inappwebview at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/flutter_inappwebview-5.8.0/
[  +11 ms] Found plugin permission_handler at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler-10.4.5/
[   +1 ms] Found plugin permission_handler_android at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_android-10.3.6/
[   +1 ms] Found plugin permission_handler_apple at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_apple-9.1.4/
[   +2 ms] Found plugin permission_handler_windows at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_windows-0.1.3/
[   +9 ms] Found plugin url_launcher at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher-6.2.5/
[   +1 ms] Found plugin url_launcher_android at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_android-6.3.0/
[   +1 ms] Found plugin url_launcher_ios at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_ios-6.2.5/
[   +1 ms] Found plugin url_launcher_linux at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_linux-3.1.1/
[   +1 ms] Found plugin url_launcher_macos at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_macos-3.1.0/
[   +3 ms] Found plugin url_launcher_web at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_web-2.3.0/
[   +1 ms] Found plugin url_launcher_windows at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_windows-3.1.1/
[  +51 ms] Found plugin fl_downloader at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/fl_downloader-1.2.0/
[   +1 ms] Found plugin flutter_inappwebview at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/flutter_inappwebview-5.8.0/
[   +7 ms] Found plugin permission_handler at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler-10.4.5/
[   +1 ms] Found plugin permission_handler_android at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_android-10.3.6/
[   +1 ms] Found plugin permission_handler_apple at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_apple-9.1.4/
[   +1 ms] Found plugin permission_handler_windows at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_windows-0.1.3/
[   +5 ms] Found plugin url_launcher at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher-6.2.5/
[   +1 ms] Found plugin url_launcher_android at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_android-6.3.0/
[        ] Found plugin url_launcher_ios at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_ios-6.2.5/
[        ] Found plugin url_launcher_linux at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_linux-3.1.1/
[        ] Found plugin url_launcher_macos at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_macos-3.1.0/
[   +1 ms] Found plugin url_launcher_web at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_web-2.3.0/
[   +1 ms] Found plugin url_launcher_windows at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_windows-3.1.1/
[  +25 ms] Found plugin fl_downloader at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/fl_downloader-1.2.0/
[        ] Found plugin flutter_inappwebview at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/flutter_inappwebview-5.8.0/
[   +6 ms] Found plugin permission_handler at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler-10.4.5/
[   +1 ms] Found plugin permission_handler_android at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_android-10.3.6/
[        ] Found plugin permission_handler_apple at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_apple-9.1.4/
[   +1 ms] Found plugin permission_handler_windows at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_windows-0.1.3/
[   +4 ms] Found plugin url_launcher at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher-6.2.5/
[        ] Found plugin url_launcher_android at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_android-6.3.0/
[        ] Found plugin url_launcher_ios at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_ios-6.2.5/
[        ] Found plugin url_launcher_linux at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_linux-3.1.1/
[        ] Found plugin url_launcher_macos at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_macos-3.1.0/
[   +1 ms] Found plugin url_launcher_web at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_web-2.3.0/
[        ] Found plugin url_launcher_windows at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_windows-3.1.1/
[  +54 ms] Generating /home/susu/source/flutter/web2app/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +82 ms] No packages with native assets. Skipping native assets compilation.
[   +1 ms] Initializing file store
[   +5 ms] Skipping target: gen_localizations
[   +2 ms] gen_dart_plugin_registrant: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/home/susu/source/flutter/web2app/.dart_tool/package_config_subset,/home/susu/source/flutter/web2app/.dart_tool/flutter_build/dart_plugin_registrant.dart}
[  +23 ms] Found plugin fl_downloader at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/fl_downloader-1.2.0/
[   +1 ms] Found plugin flutter_inappwebview at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/flutter_inappwebview-5.8.0/
[   +7 ms] Found plugin permission_handler at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler-10.4.5/
[        ] Found plugin permission_handler_android at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_android-10.3.6/
[        ] Found plugin permission_handler_apple at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_apple-9.1.4/
[   +1 ms] Found plugin permission_handler_windows at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/permission_handler_windows-0.1.3/
[   +5 ms] Found plugin url_launcher at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher-6.2.5/
[   +1 ms] Found plugin url_launcher_android at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_android-6.3.0/
[        ] Found plugin url_launcher_ios at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_ios-6.2.5/
[        ] Found plugin url_launcher_linux at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_linux-3.1.1/
[        ] Found plugin url_launcher_macos at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_macos-3.1.0/
[   +1 ms] Found plugin url_launcher_web at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_web-2.3.0/
[   +1 ms] Found plugin url_launcher_windows at /home/susu/.pub-cache/hosted/mirrors.tuna.tsinghua.edu.cn%47dart-pub%47/url_launcher_windows-3.1.1/
[  +12 ms] gen_dart_plugin_registrant: Complete
[        ] Skipping target: _composite
[   +1 ms] complete
[   +3 ms] Launching lib/main.dart on Linux in debug mode...
[   +2 ms] /home/susu/Tools/FlutterSdk/bin/cache/dart-sdk/bin/dartaotruntime --disable-dart-dev
/home/susu/Tools/FlutterSdk/bin/cache/dart-sdk/bin/snapshots/frontend_server_aot.dart.snapshot --sdk-root
/home/susu/Tools/FlutterSdk/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --incremental --target=flutter --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true
-DFLUTTER_WEB_CANVASKIT_URL=https://www.gstatic.com/flutter-canvaskit/e76c956498841e1ab458577d3892003e553e4f3c/ --output-dill /tmp/flutter_tools.JCUWFU/flutter_tool.SDZBWP/app.dill
--packages /home/susu/source/flutter/web2app/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-scheme
org-dartlang-root --initialize-from-dill build/129fe64d39a60f20f40290b7a749e2dc.cache.dill.track.dill --source
file:///home/susu/source/flutter/web2app/.dart_tool/flutter_build/dart_plugin_registrant.dart --source package:flutter/src/dart_plugin_registrant.dart
-Dflutter.dart_plugin_registrant=file:///home/susu/source/flutter/web2app/.dart_tool/flutter_build/dart_plugin_registrant.dart --verbosity=error
--enable-experiment=alternative-invalidation-strategy
[  +13 ms] Building Linux application...
[   +6 ms] <- compile package:web2app/main.dart
[   +2 ms] executing: [build/linux/x64/debug/] cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DFLUTTER_TARGET_PLATFORM=linux-x64 /home/susu/source/flutter/web2app/linux
[  +31 ms] -- Configuring done (0.0s)
[        ] CMake Error in CMakeLists.txt:
[        ]   Imported target "PkgConfig::GTK" includes non-existent path
[        ]     "/usr/include/sysprof-4"
[        ]   in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:
[        ]   * The path was deleted, renamed, or moved to another location.
[        ]   * An install or uninstall procedure did not complete successfully.
[        ]   * The installation package was faulty and references files it does not
[        ]   provide.
[   +2 ms] CMake Error in flutter/ephemeral/.plugin_symlinks/url_launcher_linux/linux/CMakeLists.txt:
[        ]   Imported target "PkgConfig::GTK" includes non-existent path
[        ]     "/usr/include/sysprof-4"
[        ]   in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:
[        ]   * The path was deleted, renamed, or moved to another location.
[        ]   * An install or uninstall procedure did not complete successfully.
[        ]   * The installation package was faulty and references files it does not
[        ]   provide.
[   +2 ms] -- Generating done (0.0s)
[  +10 ms] CMake Generate step failed.  Build files cannot be regenerated correctly.
[   +9 ms] Building Linux application... (completed in 60ms)
[+5013 ms] Error: Unable to generate build files
[        ] "flutter run" took 16,882ms.
[   +7 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:815:9)

#2      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:1389:27)

#3      AppContext.run. (package:flutter_tools/src/base/context.dart:153:19)

#4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)

#5      FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:355:9)

#6      AppContext.run. (package:flutter_tools/src/base/context.dart:153:19)

#7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)

#8      run.. (package:flutter_tools/runner.dart:119:9)

#9      AppContext.run. (package:flutter_tools/src/base/context.dart:153:19)

#10     main (package:flutter_tools/executable.dart:90:3)

[  +65 ms] ensureAnalyticsSent: 64ms
[        ] Running 1 shutdown hook
[   +5 ms] Shutdown hooks complete
[  +71 ms] exiting with code 1
`


Get rid of "return home" button when in VR.

When using Caffeine in VR mode with a headset, there's no way to press the "return home" button, so it should be hidden. You can return home by pressing Wiimote button B instead.

Fixed in 416fb6f.


"Challanges"

That's a very minor issue, but also wanted to know you if you can show us how many coins do we currently have on the donation machine.
My English is shit, sorry about that.
EDIT: In case you don't see it, it's supposed to be "Challenges"

You can already see how many coins you currently have in the donation machine. It's the last row in the "Basic" column in Stats,  called "Coins donated".
Thanks for the typo report.

That's really weird. I thought I CTRL+F'd The word coin and it gave me no results...
Anyways, I see it now. Thanks.


clicking links ( elements) with href omitted or with an empty href incorrectly generates External UrlRequest's

Empty links, i.e. a elements without a href attribute or with href "" will cause External UrlRequests to be generated, and if handled as suggested in the Elm guide will cause page reloads.
This can be handled in update if you know about it, but is non-standard behavior that I think would surprise most people. it is also behavior that a lot of code depends on, among them  elm-bulma, and it miight therefore not be immediately apparent what the cause is.
As far as I can understand, the standard behavior is:

When href is omitted it should not be considered a hyperlink (source)
When href is an empty string, it should be considered a reference to the beginning of the document (source)

My suggestion is to simply not emit a UrlRequest if href is omitted, and to emit an Internal UrlRequest if it is an empty string.
Here's a minimal, complete and verifiable example:
module Main exposing (main)

import Browser
import Browser.Navigation
import Html exposing (..)
import Url

type alias Model =
    ()

type Msg
    = UrlRequested Browser.UrlRequest
    | UrlChanged Url.Url

init () _ _ =
    ( (), Cmd.none )

update msg model =
    case msg of
        UrlRequested (Browser.Internal _) ->
            ( model, Cmd.none )

        UrlRequested (Browser.External url) ->
            ( model, Browser.Navigation.load url )

        UrlChanged _ ->
            ( model, Cmd.none )

view model =
    { title = ""
    , body = [ a [] [ text "click to reload" ] ]
    }

main =
    Browser.application
        { init = init
        , view = view
        , update = update
        , subscriptions = \_ -> Sub.none
        , onUrlRequest = UrlRequested
        , onUrlChange = UrlChanged
        }

My solution/workaround is to add a branch in update to do nothing on External "". For others coming across this looking for an easy fix, here's the fixed update function:
update msg model =
    case msg of
        UrlRequested (Browser.Internal _) ->
            ( model, Cmd.none )

        UrlRequested (Browser.External "") ->
            ( model, Cmd.none )

        UrlRequested (Browser.External url) ->
            ( model, Browser.Navigation.load url )

        UrlChanged _ ->
            ( model, Cmd.none )

I just ran in to this too. A possible fix, provided you aren't relying on fragment identifiers in the same context, is to add a href "#" attribute to the tag. This will trigger a URL that will be correctly recognized as internal.

In the mean-time, a docs update would be highly appreciated.


Adds support for special ansible_python_interpreter values, ansible_python_interpreter discovery, and fixes tests

Fixes #597 , fixes #680 , fixes #673
adds support for Jinja templating in ansible_python_interpreter, adds support for ansible_python_interpreter discovery, and fixes up some test issues I ran into in order to get this PR passing (tests hadn't passed on a PR since last year).
Additionally I had to update the Mac VM to 10.14; MS said they'll stop supporting 10.13 soon: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops#use-a-microsoft-hosted-agent and also updated away from ubuntu 16.04:
https://dev.azure.com/dw-mitogen/Mitogen/_build/results?buildId=793&view=logs&j=364fd14b-95c5-5834-280a-1629ce194374&t=2241d271-1077-5b70-19c7-218604a5902c
E: Failed to fetch https://packages.microsoft.com/ubuntu/16.04/prod/dists/xenial/main/binary-amd64/Packages.bz2  Hash Sum mismatch
E: Some index files failed to download. They have been ignored, or old ones used instead.
Status: Downloaded newer image for mitogen/debian-test:latest

sometimes this happened... 🤦♂
I ported over the tests found here: https://github.com/ansible/ansible/pull/50163/files#diff-2efff5ba3589af60c1010f00a234ef57R1 from ansible where interpreter discovery was first added, and added them to the CI to verify interpreter discovery works.
Also, I leveraged the existing discover_interpreter function from Ansible, which means that interpreter discovery won't work in Ansible < 2.8.0 but it already doesn't work in those Ansible versions so I didn't think this was an issue.
Finally, I disabled a bunch of tests that worked locally but wouldn't pass on CI. I made new github issues out of the fails and labeled them with ci.

If I'm going about this the wrong way please let me know; I ran into an issue where this was broken:
ansible_python_interpreter: source /opt/rh/rh-python36/enable && python
and noticed the created ssh command looked a bit off so thought that'd be a good place for the fix.

I'm gonna run more tests on my end and then add a test for the new functionality + docs.
This so far has passed this command:
- name: pull down docker binaries
  get_url:
    url: https://download.docker.com/linux/static/stable/x86_64/docker-{{ docker_version }}.tgz
    dest: /usr/local/share
    mode: 0644
  vars:
    ansible_python_interpreter: source /opt/rh/rh-python36/enable && python

Fails on a more complex command:
{"changed": false, "msg": "EOF on stream; last 100 lines received:\nroot@IP's password: \nbash: {%: command not found", "unreachable": true}

- name: download helm and tiller
  get_url:
    url: "https://get.helm.sh/helm-v2.14.1-linux-amd64.tar.gz"
    dest: "/usr/local/src/helm-v2.14.1-linux-amd64.tar.gz"
  vars:
    ansible_python_interpreter: >
      {% if ansible_facts['distribution'] == "CentOS" and ansible_facts['distribution_major_version'] == "6" %}
        source /opt/rh/rh-python36/enable && python
      {% else %}
        python
      {% endif %}

I'll try and fix that up as well

PR ready! Passed all automation on my side, and passes dw.mitogen here. Travis says it's over its data quota which is why it's failing. I'll add some documentation now

@dw this PR is ready for review now 😄

Traceback (most recent call last):
  File "/home/vsts/work/1/s/tests/testlib.py", line 520, in tearDownClass
    cls.dockerized_ssh.check_processes()
  File "/home/vsts/work/1/s/tests/testlib.py", line 469, in check_processes
    counts
AssertionError: Docker container 'mitogen-test-9f743adbdb483a88' contained extra running processes after test completed: {'sshd': 1, 'doas <defunct>': 1, 'ps': 1}

I'll rerun tests; commit adding a few sentences to a readme file is unrelated to ^^^

I haven't used azure devops before, not sure how to kick off a rebuild. There's no rebuild button that I can see from https://dev.azure.com/dw-mitogen/Mitogen/_build/results?buildId=696&view=ms.vss-test-web.build-test-results-tab

(Epdb) found_interpreters
['/usr/bin/python', '/opt/rh/python27/root/usr/bin/python2.7', '/usr/bin/python2.6', '/usr/bin/python3', '/opt/rh/python27/root/usr/bin/python']

able to detect interpreters now! My test cases taken mostly from https://github.com/ansible/ansible/pull/50163/files#diff-2efff5ba3589af60c1010f00a234ef57 still don't fully pass yet though

that's great that you're supporting the ansible 2.8 discovery options for python.  That was my major issue since you can't run against RHEL 8 without setting an explicit interpreter path for the host.

Running make complex-args-test from https://github.com/s1113950/mitogen-test almost passes OSX, fails here:
TASK [complex_args : assert] ****************************************************************************************************************************************************************
task path: /Users/robertso/mitogen-test/roles/complex_args/tasks/main.yml:156
fatal: [localhost]: FAILED! => {
    "assertion": "discovered_interpreter_bogus | default('nope') == 'nope'",
    "changed": false,
    "evaluated_to": false,
    "msg": "Assertion failed"
}
META: facts cleared

localhost                  : ok=18   changed=1    unreachable=0    failed=0    skipped=5    rescued=0    ignored=0```
all test cases from running `make complex-args-test` on OSX pass now, still have to validate RHEL fully

I'll try and add the ansible test cases to mitogen as well when I'm all done 👍

TASK [complex_args : get the interpreter being used on the target to execute modules] *******************************************************************************
task path: /Users/robertso/mitogen-test/roles/complex_args/tasks/main.yml:76
ok: [sm-160-52] => {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python"}, "changed": false, "running_python_interpreter": "/opt/rh/python27/root/usr
/bin/python"}

TASK [complex_args : assert] ****************************************************************************************************************************************
task path: /Users/robertso/mitogen-test/roles/complex_args/tasks/main.yml:87
fatal: [sm-160-52]: FAILED! => {
    "assertion": "echoout.running_python_interpreter == auto_out.ansible_facts.discovered_interpreter_python",
    "changed": false,
    "evaluated_to": false,
    "msg": "Assertion failed"
}

RHEL still has some issues 😞

Centos7 passes!

Rewrote test cases I've been using from https://github.com/s1113950/mitogen-test to spin up a container on the fly to make testing different OSs easier, and the following image values pass in a fresh container after running make complex-args-test USE_DOCKER=true CONTAINER_IMAGE=$image:
centos:6
centos:7
centos:8
ubuntu:14.04
ubuntu:16.04
ubuntu:18.04
ubuntu:19.10
ubuntu:20.04

as well as running locally on a mac outside a container.
The detected interpreter for centos8 is {"ansible_facts": {"discovered_interpreter_python": "/usr/libexec/platform-python"} as well.
Some tests are still failing though; working on that still.

nice, lots of tests passing now :)

I checked out master and ran the same issue_152__virtualenv_python_fails.yml test on my Mac and it failed as well. I'm not sure what's up @dw , should I get all tests passing or ignore the dw.mitogen test fails?

Something is also up with tests, I added my commit https://github.com/dw/mitogen/pull/658/commits/5fbcb9e28c9c20acad3e2f52e19c8a0d6c5c2447 which reverts back to a previously passing state and a test is now failing O_o hit rebuild and a docker test container is still complaining of excess processes

I'm gonna try and get the failing tests to pass on this branch regardless

I believe the issue with failing tests could be linked to several other issues filed about Mitogen breaking on Ansible 2.9+.
The requirements.txt file for testing installs the latest version of Ansible to test with, which isn't working for me (even on master).
Ansible 2.8.3 (https://github.com/ansible/ansible/tree/v2.8.3) would be the latest version that tests used in the last PR I found that had all tests passing: https://github.com/dw/mitogen/pull/612 (this PR went in Aug 9th, 2019).
I'll see what's changed since then and try and get tests passing with Ansible 2.8.3 for now.

Looks like the ansible version isn't the issue. Mac is doing a weird symlink thing which is affecting what the sys.executable value outputs as, regardless of ansible version, so I'm pegging now to ansible 2.9.4 again

ANSIBLE_STRATEGY=mitogen_linear ./run_ansible_playbook.py integration/action/make_tmp_path.yml -l target -vvv -k -K

this works locally for me running on Mac 10.14.4 with the same mitogen + ansible versions 🤔 not sure why there's an issue on azure...

dw.mitogen now passes all tests except for Mac

I'm not sure what to do about some of the tests 🤔 I change unrelated things and some other test fails that was previously passing. I'll keep trying to get them passing but I might disable some of them for now

Similar tests fail on master as did before I started fixing them up here: https://github.com/dw/mitogen/pull/693
I'm going to disable the failing ones and make tickets to fix them up later

🤦♂ 🤦♂ the latest errors after updating to 18.04 are because of https://github.community/t5/GitHub-Actions/apt-get-update-failing-with-quot-Conflicting-distribution-quot/td-p/47157 which literally just happened. Attempting a rerun because that might fix it

result of mitogen_shutdown_all test when ran locally on a Mac:
TASK [mitogen_shutdown_all ] ******************************************************************************************************************************************
changed: [target]

TASK [shell _raw_params=true] *****************************************************************************************************************************************
changed: [target] => (item=1)
changed: [target] => (item=2)
changed: [target] => (item=3)

TASK [mitogen_action_script script=self._connection._connect()
result['dump'] = self._connection.get_binding().get_service_context().call_service(
  service_name='ansible_mitogen.services.ContextService',
  method_name='dump'
)
] ***
ok: [target]

TASK [assert that=out.dump|length == (play_hosts|length) * 4] *********************************************************************************************************
ok: [target] => {
  changed: False
  msg: All assertions passed
}

TASK [mitogen_action_script script=self._connection._connect()
result['dump'] = self._connection.get_binding().get_service_context().call_service(
  service_name='ansible_mitogen.services.ContextService',
  method_name='dump'
)
] ***
ok: [target]

TASK [assert that=out.dump|length == play_hosts|length] ***************************************************************************************************************
ok: [target] => {
  changed: False
  msg: All assertions passed
}

PLAY RECAP ************************************************************************************************************************************************************
target                     : ok=6    changed=2    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

but it's also failing CI 😞 tested via ANSIBLE_STRATEGY=mitogen_linear ./run_ansible_playbook.py integration/context_service/disconnect_cleanup.yml -l target -k -K

It was a bit of a hack to get it all working but tests finally pass now! 😅
They don't pass on master (https://github.com/dw/mitogen/pull/693) so verifying if the test fails were due to my PR was done by running tests locally, and then if they passed locally but kept failing on CI I commented them out for now (see PR description).
Sorry it's taken so long to finish 😞 the PR ended up being bigger than originally intended.
@bradh352 @ssbarnea  can you please run this patch against your playbooks and see if it works for you? 😄

There were some bugs discovered in testing this patch on other github issues:

The _connect_docker connection type needs to be able to discover the interpreter inside the container, rather than on the host. Ansible's interpreter discovery works by running on inventory_hostname, which in my test case is still localhost when I'm targeting a specific container via delegate_to, which means that my host (Mac) is detected as /usr/bin/python but RHEL8 for example needs to be /usr/libexec/platform-python
There's an infinite recursive loop I initially patched but it won't work for all scenarios so that needs to be fixed: interpreter_discovery calls low_level_execute_command which then (in Mitogen's case) calls spec.python_path() which then would retrigger discovery, when then calls back to interpreter_discovery, etc. I fixed this by assuming that /usr/bin/python could be used during the 2nd callback (hence not retriggering discovery and then correctly setting the desired python eventually), but this breaks on systems that don't have /usr/bin/python like RHEL8

The bugs from https://github.com/dw/mitogen/issues/673#issuecomment-594731973 are fixed now, but there's an issue with meta: reset_connection. discover_interpreter wants an Action object but Strategy's _execute_meta doesn't have an Action obj... 🤦♂

Waiting for some folks who've reported bugs related to interpreter discovery to try the updated patch, and if it works for them will merge

You'd recommend testing the install via something like:
pip3 remove mitogen
pip3 install git+https://github.com/s1113950/mitogen@complexAnsiblePythonInterpreterArg

Right?
About to test...

I think that'll work? Make sure that strategy_plugins is set too maybe. I've done both though and it seems to work either way (I do the python setup.py install local approach when running tests locally and the strategy_plugins thing when testing job runs)

Thanks for the review @cognifloyd ! Suggestion applied :)

@bradh352 thinking about it more now I'd say set the strategy_plugins to the patch path just to be sure. Did it work for you?

I can't get it to work ... not sure what I may be doing wrong...  I'm using a minimal CentOS 8.1 installation.  The only python on the system is in /usr/libexec/platform-python.
in ansible.cfg i have:
strategy_plugins = /usr/share/ansible_plugins/strategy_plugins:/usr/local/lib/python3.6/site-packages/ansible_mitogen/plugins/strategy:/usr/local/lib/python3.7/site-packages/ansible_mitogen/plugins/strategy:/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/ansible_mitogen/plugins/strategy
strategy = mitogen_linear
interpreter_python = auto

So first I try the normal mitogen which fails as expected:
$ ansible all -u root -k -i <IP_ADDRESS>, -m setup
SSH password:
BECOME password[defaults to SSH password]:
Vault password:
<IP_ADDRESS> | UNREACHABLE! => {
    "changed": false,
    "msg": "EOF on stream; last 100 lines<EMAIL_ADDRESS>password: \nbash: /usr/bin/python: No such file or directory",
    "unreachable": true
}

So I remove that mitogen:
sudo pip3 uninstall mitogen

Verify it fails since there is no latent mitogen:
$ ansible all -u root -k -i <IP_ADDRESS>, -m setup
SSH password:
BECOME password[defaults to SSH password]:
Vault password:
ERROR! Invalid play strategy specified: mitogen_linear

Then install the mitogen from this PR:
sudo pip3 install git+https://github.com/s1113950/mitogen@complexAnsiblePythonInterpreterArg

And try again and it still fails:
$ ansible all -u root -k -i <IP_ADDRESS>, -m setup
SSH password:
BECOME password[defaults to SSH password]:
Vault password:
[WARNING]: Unhandled error in Python interpreter discovery for host <IP_ADDRESS>: EOF on stream; last 100 lines received<EMAIL_ADDRESS>password:  bash: python:
command not found

<IP_ADDRESS> | UNREACHABLE! => {
    "changed": false,
    "msg": "EOF on stream; last 100 lines<EMAIL_ADDRESS>password: \nbash: /usr/bin/python: No such file or directory",
    "unreachable": true
}

What's even more odd if I install python3 in the CentOS8.1 vm, it finds /usr/libexec/platform-python and uses it:
ansible all -u root -k -i <IP_ADDRESS>, -m setup | grep python
SSH password:
BECOME password[defaults to SSH password]:
Vault password:
            "_": "/usr/libexec/platform-python"
        "ansible_python": {
            "executable": "/usr/libexec/platform-python",
            "type": "cpython",
        "ansible_python_version": "3.6.8",
        "ansible_selinux_python_present": true,
        "discovered_interpreter_python": "/usr/libexec/platform-python",

The only command I ran in the VM for it to work vs not work was yum install python3.

Hmmm ok, I think I know how to repro. In https://github.com/s1113950/mitogen-test I install python on my test containers but don't do it for rhel:8 (Ubuntu 20 container doesn't have python for some reason for example). I'll also not do that on centos:8 and hopefully should get your error as well! Thanks so much for debugging. I'll try to have a patch for this by EOD or EOD tomorrow.
My theory is there's an issue with the way I tell mitogen to detect python if there's no python_path. Right now I default it to auto but I might be doing that too late in the pipeline.

shoot I can't repro on my end @bradh352 :( I edited https://github.com/s1113950/mitogen-test to not install python into it and then ran my tests, and it correctly detected /usr/libexec/platform-python for me the first time.
I ran the tests via:
make complex-args-test CONTAINER_IMAGE=centos:8.1.1911 ANSIBLE_SSH_PASS='localSSHPasswordHere' USE_DOCKER=true
As part of the run in each test container I do a call to setup: in the beginning as well. There might be some differences between the default centos:8.1.1911 image and what's on your VM though, as it's clear yours failed.
Ok new plan: can you run your failed setup call again, but with -vvvv and dump the output here? It should dump something related to trying to do interpreter discovery in the logs. Specifically, I'm after the traceback here from Ansible:
display.warning(msg=u'Unhandled error in Python interpreter discovery for host {0}: {1}'.format(host, to_text(ex)))
display.debug(msg=u'Interpreter discovery traceback:\n{0}'.format(to_text(format_exc())), host=host)

Entire output here with -vvvv
ansible.txt

I see it adding /usr/libexec/platform-python to the search:
[task 51049] 20:18:25.148381 D ansible_mitogen.mixins: _low_level_execute_command("echo PLATFORM; uname; echo FOUND; command -v '/usr/bin/python'; command -v 'python3.7'; command -v 'python3.6'; command -v 'python3.5'; command -v 'python2.7'; command -v 'python2.6'; command -v '/usr/libexec/platform-python'; command -v '/usr/bin/python3'; command -v 'python'; echo ENDFOUND", in_data=<class 'NoneType'>, exe=None, dir=None)

Which appears to succeed I think.
Then It tries to run /usr/libexec/platform-python without the leading /:
[mux  51048] 20:18:29.641987 D mitogen.parent: command line for Connection(None): ssh -o "LogLevel ERROR" -l root -p 22 -o "Compression yes" -o "ServerAliveInterval 30" -o "ServerAliveCountMax 10" -o "StrictHostKeyChecking no" -o "UserKnownHostsFile /dev/null" -o "GlobalKnownHostsFile /dev/null" -C -o ControlMaster=auto -o ControlPersist=60s <IP_ADDRESS> usr/libexec/platform-python -c "'import codecs,os,sys;_=codecs.decode;exec(_(_(\"eNqFkcFPgzAUxs/jr+DWNmtYmRqVpIlmB+PBmBAjB11MgeKq0DYFxuZf7xsYB/Pgqe+X971+X96LacJNHVhlJSaeo92IVOEDFMZ9YhJ5M6jz1i4xoyFj5MgxHZODbjhwVppa4ngMbgzJGDoAMKz3YF+KBlwrn3Mf5cJ1SiNf6Lxvyp3M2kakpezbi7Z2i1Tphd03G6MR5JydyOa8H9xKVyujX6KzdW8r9VY5YHQb3z0ztObTsUEDWOJpg05xjnClGvMudZRuTFvLm+EJbMg+xC4wRaEyGVRGy8aJIDNVdBGy8yuCiAcOnVONxCFFD/dPj4yxV40gWWZyOADxVvwNH06QGys1LB65FJHASZHj8JItrwlFX8rCT4XlR11CUZeiw1UK+2Ow6uth0yfq7j/135ThNOXvDZfkG4zwusI=\".encode(),\"base64\"),\"zip\"))'"
[mux  51048] 20:18:30.193632 D mitogen.parent: ssh.<IP_ADDRESS>: (unrecognized): bash: usr/libexec/platform-python: No such file or directory

Not sure why the leading / is being killed though.

I forgot to include the beginning slash 🤦♂ my bad

Ok please try again @bradh352

Ok please try again @bradh352

works!

Nice!!!

Now the other test failed D: these tests are too flaky...

travis is under maintenance now. Once it's back up, if tests are solid I'll wait a day or two for more people to try the patch, but I really want to get it in soon so I can start getting ansible 2.9 support working (this PR also fixes tests which is why it should come in first)

Hello,
I currently have this same issue using your latest commit.  I'm using Ansible 2.9.6
Here's a line of the -vvvv showing it's still trying to use /usr/bin/python
[mux  19549] 09:18:12.658834 D mitogen: <Side of ssh.<IP_ADDRESS> fd 85>: empty read, disconnecting
[mux  19549] 09:18:12.659361 D mitogen.parent: failing connection ssh.<IP_ADDRESS> due to EofError("EOF on stream; last 100 lines<EMAIL_ADDRESS>password: \nbash: /usr/bin/python: No such file or directory",)

Here's my ansible.cfg (as you can see I also tried setting to auto with the same results)
[defaults]
# Set reasonable default command line flags
vault_password_file = vault-sops-client.py
inventory = amp_database_using_serial.yaml
host_key_checking = False
ansible_python_interpreter = /usr/bin/python3
#ansible_python_interpreter = auto

# Use the YAML callback plugin.
stdout_callback = yaml

# Use the stdout_callback when running ad-hoc commands.
bin_ansible_callbacks = True

Here's my pertinent environment variables
export ANSIBLE_INVENTORY_PLUGINS=/home/chase/dev/axon/ansible-playbooks/inventory_plugins

export ANSIBLE_STRATEGY=mitogen_linear
export ANSIBLE_STRATEGY_PLUGINS=/home/chase/.cache/pypoetry/virtualenvs/amp-ansible-lib-aZl7EoP--py3.6/src/mitogen/ansible_mitogen/plugins/strategy

export ANSIBLE_HOST_KEY_CHECKING=False

On the target machine (the machine I'm running Ansible against), there is only a /usr/bin/python3 directory, NOT /usr/bin/python.  Hence the error.  Please let me know if you need any additional information as I love Mitogen and really want to use it in my current setup.  Thanks!

Can you try with Ansible 2.8.8? Ansible 2.9.6 support isn't fully available yet (some playbooks work and some don't); it might still be broken but it would be good to rule that out first

Are we still not compatible with Ansible >=2.9?

@s1113950 - 2.8.8 has always worked wonderfully.  That's what I've been using before posting this.  I didn't realize this wasn't fully supported in 2.9.6.  What's the best way to keep my finger on the pulse of what's supported when regarding 2.9.6?

@cbrum11 it should be supported in 2.9.6, just wanted to check if there's a case where it doesn't because I originally added the feature using 2.8.8. However, I recently updated the tests to test 2.9.6 as well though and they passed interpreter discovery 🤔
Does interpreter discovery work without mitogen for you on Ansible 2.9.6? Mitogen calls Ansible's discover_interpreter to determine which interpreter to use, and the "possible_pythons" list that Mitogen uses (chicken-and-egg situation where Mitogen needs a python in order to run anything) matches the INTERPRETER_PYTHON_FALLBACK of Ansible, but there's definitely a bug somewhere, as you've shown in your comment.
If interpreter discovery works for you without Mitogen, I'll need your host and target OS in order to better debug your issue :)
As of right now, afaik everything should be supported in Ansible 2.9.6 as of #705 except for collections. There's a big discussion on collections (and Mitogen backwards compat/new releases) here: #715 .

Thanks for the super speedy response.  I believe interpreter discovery does work on 2.9.6 without mitogen, but I'll give it a specific test to make 100% sure this week.

I have just stumbled into this problem.  The server is an ubuntu-netinst VM without anything on it.  It has only /usr/bin/python3, which ansible -m setup ... also confirms.
Adding the mitogen in the strategy results in ansible -m ping ... to complain about server unreachable.
This is the simplest case I can present.
mitogen is the one from pip3 install: mitogen-0.2.9
Is may not be relevant unless this MR is already published there.

This PR will be in the next release; 0.2.9 doesn't have it. You can pip install from master of this repo to get the fix for now :) a new release(s) is planned for after Ansible 2.10 comes out

This PR will be in the next release; 0.2.9 doesn't have it. You can pip install from master of this repo to get the fix for now :) a new release(s) is planned for after Ansible 2.10 comes out

Hi, what would the command to install from master be in this case? I am, unfortunately, still not too familiar with pip.
Thank you!

@fourstepper pip install git+ssh://git@github.com/dw/mitogen.git@a18be5afefd1c8b7a860a994773737f788405a93 will give you the latest commit :)

@fourstepper pip install git+ssh://git@github.com/dw/mitogen.git@a18be5afefd1c8b7a860a994773737f788405a93 will give you the latest commit :)

For strategy_plugins in ansible.cfg where should I point to the installed verion? Thank you for replying and your hard work

@fourstepper pip install git+ssh://git@github.com/dw/mitogen.git@a18be5afefd1c8b7a860a994773737f788405a93 will give you the latest commit :)

For strategy_plugins in ansible.cfg where should I point to the installed verion? Thank you for replying and your hard work

Ok it should be /usr/local/lib/python3.6/site-packages/ansible_mitogen/plugins/strategy for me

I am a little late to the party, but was the issue resolved in regards to the unhandled python interpreter warning message?  I am running ansible 2.8.12 via mitogen and receiving that warning:
[WARNING]: Unhandled error in Python interpreter discovery for host <removed>: unexpected output from Python interpreter discovery
Wondering what configuration updates need to be done on my end if any.  Thanks in advance for any help.
cc @tom10271 @s1113950

I am a little late to the party, but was the issue resolved in regards to the unhandled python interpreter warning message?  I am running ansible 2.8.12 via mitogen and receiving that warning:
[WARNING]: Unhandled error in Python interpreter discovery for host <removed>: unexpected output from Python interpreter discovery
Wondering what configuration updates need to be done on my end if any.  Thanks in advance for any help.
cc @tom10271 @s1113950

@lancefriday945 either of these tags should have the fix in them:
https://github.com/dw/mitogen/releases/tag/v0.2.10-rc.0
https://github.com/dw/mitogen/releases/tag/v0.3.0-rc.0

@lancefriday945 either of these tags should have the fix in them:
https://github.com/dw/mitogen/releases/tag/v0.2.10-rc.0
https://github.com/dw/mitogen/releases/tag/v0.3.0-rc.0

@lancefriday945 either of these tags should have the fix in them:
https://github.com/dw/mitogen/releases/tag/v0.2.10-rc.0
https://github.com/dw/mitogen/releases/tag/v0.3.0-rc.0

I got that cleaned up. Were you working on a fix for the unreachable issue?
UNREACHABLE! => {"changed": false, "msg": "Connection timed out.", "unreachable": true}
I am still experiencing that issue.  Do I need to put my config somewhere else for ssh retry logic?  Right now I have this set in my ansible.cfg file:
[ssh_connection] retries = 5
I also have group_vars folders for our different environments.

@lancefriday945 either of these tags should have the fix in them:
https://github.com/dw/mitogen/releases/tag/v0.2.10-rc.0
https://github.com/dw/mitogen/releases/tag/v0.3.0-rc.0

I got that cleaned up. Were you working on a fix for the unreachable issue?
UNREACHABLE! => {"changed": false, "msg": "Connection timed out.", "unreachable": true}
I am still experiencing that issue.  Do I need to put my config somewhere else for ssh retry logic?  Right now I have this set in my ansible.cfg file:
[ssh_connection] retries = 5
I also have group_vars folders for our different environments.

@lancefriday945 I'm not sure about the connection issue, I don't think it relates specifically to the python interpreter patch. Mitogen should use the same logic that Ansible does for setting ssh_connection retries

@lancefriday945 I'm not sure about the connection issue, I don't think it relates specifically to the python interpreter patch. Mitogen should use the same logic that Ansible does for setting ssh_connection retries


Is arm64 support a possibility?

Hey
Firstly, this project looks really cool!
Like many though my "home server" consists entirely of a raspberry pi. Unfortunately there is no arm64 container available yet.
Thanks :)

@3rikk Thank you for taking some time to submit this improvement opportunity. I have enabled ARM support and is now available on main branch. However, I don't have any ARM system to test the image on.
Can you please test it using mandarons/yadd:main tag on your ARM system? Please let me know if you find any issues. Else, I will include it in upcoming 1.1.0 release.

Thanks a lot :)
Unfortunately, the container gives out the following error at launch:
(node:8) UnhandledPromiseRejectionWarning: SequelizeConnectionError: SQLITE_CANTOPEN: unable to open database file at Database.<anonymous> (/app/node_modules/sequelize/lib/dialects/sqlite/connection-manager.js:70:34)

(Use `node --trace-warnings ...` to show where the warning was created)

(node:8) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

(node:8) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The webpage does load however you can't create any new services (the button doesn't do anything), probably due to the database being inaccessible
The folder ~/yadd/node-modules/ also doesn't exist, while ~/yadd/config/ does.
The command I use for installation was:
docker container run --name yadd -p 3334:3334 -v ${PWD}/config/:/app/config/ mandarons/yadd:main
Other than that I didn't configure anything.
Is it a configuration mistake that I made? I apologise if that's the case

@3rikk: Yeah, looks like db.sqlite creation is having some problem. Can you try the following:

In a new directory (e.g. yadd), create config folder.
Then run the command: docker container run --name yadd -p 3334:3334 -v ${PWD}/config/:/app/config/ mandarons/yadd:main

@mandarons hey there :)
Sorry for the late response. I tweaked your solution a bit and it worked!
Making both the directories config and node-modules prior to running the container seems to make it all work.
I've tested the rest of the app a bit now too and everything seems to function properly.

This feature will be released in 1.1.0.


Wednesday 28-06-2023 roll call

Roll Call!
Leave a comment with these two things:

A summary of your study using only emojis
Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

Good Morning

Good morning

hi

Good morning 🙋♀

good morning

👋🏼

buenos dias

present

Good morning

good morning

morning

Hi

Good morning

Good morning!

Present


No shorcut

Hi guys, thank you for this tool, i love it
As i've mentionned it in the tittle there's no shorcut and clicking on make-shorcut.bat doesn't work neither.

Are you on windows? (That only works on windows, not linux/mac)
Do you maybe have an unusual Desktop folder? That saves the shortcut to %userprofile%\Desktop\StableSwarmUI.url, so if you eg have OneDrive replacing your desktop that might cause it to go missing (in which case you may have to copy the shortcut from that directory to the hacked one)

Hi, sorry for the delay, yes, I'm on window 11, and I've installed swarmUi on my second hard drive. There's no shortcut in desktop folder, one drive or any other.

You've checked specifically the path %userprofile%\Desktop? (You can copypaste that exactly into file explorer's address bar and hit enter)
for the record you can always create one manually by right clicking on the launch-windows.bat file and clicking "Create Shortcut" in the file menu


bugs with play bar and sound bar

When listening to songs, the progress bar is compromised, just as the sound bar. You can see that on my printscreen

You have moved from fluent theme aren't you

Send a screenshot of your xpui file ill tell you what to do

@davimaiaa

Yes! I moved from Fluent! As you asked, here's the xpui file screenshot! Btw thanks for the help

@nimsandu

I completely reinstalled spicetify and now it's working! tks for the great theme bro

@davimaiaa All right enjoy calm design
If you having any confusions don't hesitate to open another issue


Fix this.node on reloadableprototype.

Fix this.data on reloadableprototype.
Fixes #55

Coverage increased (+0.04%) to 79.838% when pulling 4010737e19789f783fb02a8d9eb19858d76533e5 on jansav:reloadable-fix into 0ec64587fd985d6fd156a5582f8f9823613657bf on Houston-Inc:v2.0.3.

Coverage increased (+0.04%) to 79.839% when pulling 11f4d0f543565073b0e09903f43574b055c855fa on jansav:reloadable-fix into 0ec64587fd985d6fd156a5582f8f9823613657bf on Houston-Inc:v2.0.3.

Coverage increased (+0.04%) to 79.839% when pulling 11f4d0f543565073b0e09903f43574b055c855fa on jansav:reloadable-fix into 0ec64587fd985d6fd156a5582f8f9823613657bf on Houston-Inc:v2.0.3.

Coverage increased (+0.04%) to 79.839% when pulling 11f4d0f543565073b0e09903f43574b055c855fa on jansav:reloadable-fix into 0ec64587fd985d6fd156a5582f8f9823613657bf on Houston-Inc:v2.0.3.


Always pulling images even when they're locally available

I've noticed that the TestContainers code is always attempting to pull images, even when they are locally available. This obviously makes builds slower, and can cause problems when working without internet access.
The problem seems to be in RemoteDockerImage.resolve(), though I've not worked out any more than that yet.

In particular, it seems to be around this code:
            List<Image> updatedImages = listImagesCmd.exec();
            updatedImages.stream()
                .map(Image::getRepoTags)
                .filter(Objects::nonNull)
                .flatMap(Stream::of)
                .map(DockerImageName::new)
                .collect(Collectors.toCollection(() -> AVAILABLE_IMAGE_NAME_CACHE));

The updatedImages collection does contain the image that I'm working with, but after this the AVAILABLE_IMAGE_NAME_CACHE doesn't get updated to have anything.
However, when AVAILABLE_IMAGE_NAME_CACHE is added to lower down then that does persist and does work correctly, so it seems to literally be the above code not updating the collection correctly.

Quite strange. Can you confirm the image you're trying to pull? Might also be worth providing your docker version and OS.
With my local testing I can see that the AVAILABLE_IMAGE_NAME_CACHE gets correctly populated for me when I try with a simple postgres image.

For ref here's my setup:
andy@andy-pc:~$ docker -v
Docker version 18.09.6, build 481bc77

andy@andy-pc:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 19.04
Release:	19.04
Codename:	disco

I can get exact versions later, but:

macOS - latest
Docker for Desktop - latest for macOS
Java - OpenJDK 13
Containers: postgres:11.5-alpine, selenium, vncrecorder and sazzer/fakeauth:latest

My app is also written in Kotlin and builds with Maven, but I don't see that being relevant.
Cheers

More version info:
-> % docker version
Client: Docker Engine - Community
 Version:           19.03.2
 API version:       1.40
 Go version:        go1.12.8
 Git commit:        6a30dfc
 Built:             Thu Aug 29 05:26:49 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.8
  Git commit:       6a30dfc
  Built:            Thu Aug 29 05:32:21 2019
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

-> % mvn -v
executing mvnw instead of mvn
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T19:41:47+01:00)
Maven home: /Users/coxg/.m2/wrapper/dists/apache-maven-3.6.0-bin/2dakv70gp803gtm5ve1ufmvttn/apache-maven-3.6.0
Java version: 13, vendor: Oracle Corporation, runtime<EMAIL_ADDRESS>Default locale: en_GB, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac"

Are you able to run this with TRACE logging enabled?
I think you can do this by building and running your tests with a logback.xml file similar to the following in your resources folder:
<configuration>

    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
        <!-- encoders are assigned the type
             ch.qos.logback.classic.encoder.PatternLayoutEncoder by default -->
        <encoder>
            <pattern>%d{HH:mm:ss.SSS} %-5level %logger - %msg%n</pattern>
        </encoder>
    </appender>

    <root level="INFO">
        <appender-ref ref="STDOUT"/>
    </root>

    <logger name="org.testcontainers" level="TRACE"/>

    <logger name="com.github.dockerjava" level="TRACE"/>
    <logger name="org.zeroturnaround.exec" level="TRACE"/>
    <logger name="org.testcontainers.shaded" level="TRACE"/>

</configuration>

I don't quite know what I've done, but it's no longer doing it...
I'd been trying to get a local build of TestContainers that I could depend on - and not worked out how to get my Maven build to depend on a Gradle project :\ - but I've got zero changes outstanding and now it's not trying to pull images every time.
I'll keep an eye on it to see if it happens again, but for now it seems to have resolved itself somehow.

No worries - possibly something environmental in your docker setup? If it crops up again then message back 👍

#1345 might have an effect on this, or at least give options should you find a way to reproduce again.
I'll close this ticket for now, but of course if you do find this happening consistently again please feel free to reopen.
BTW, thanks @AndyMacDroo for your input here 🙇


actions/jekyll-build-pages is too simple to satisfy Gemfile dependencies

The current CI build
https://github.com/UW-Madison-DSI/ospo.wisc.edu-uw-jekyll-theme/blob/d306594937dd2637b8ede4127519b41734725f17/.github/workflows/jekyll-gh-pages.yml#L29-L30
has the warning:

The github-pages gem can't satisfy your Gemfile's dependencies. If you want to use a different Jekyll version or need additional dependencies, consider building Jekyll site with GitHub Actions: https://jekyllrb.com/docs/continuous-integration/github-actions/

From looking at https://github.com/actions/jekyll-build-pages/blob/2b9a1ccfebe79720f5512bbfcb5358d27c5426bf/action.yml it looks like https://github.com/actions/jekyll-build-pages is too simple and setting up Ruby similar to how IRIS-HEP does in https://github.com/iris-hep/iris-hep.github.io/blob/293b76a79e76c1d84d3d448ba2476d3fd0c99767/.github/workflows/deploy.yml will be required.

These PRs are all great, but I wanted to note that they should make their way back upstream to
https://github.com/UW-Madison-DSI/uw-jekyll-theme

@cranmer Sounds good, though can you comment on what the plan is for the UW (https://github.com/UW-Madison-DSI/uw-jekyll-theme) vs. the OSPO (https://github.com/UW-Madison-DSI/ospo.wisc.edu-uw-jekyll-theme) themes? I'm not fully clear on why the OSPO theme is a fork given that it seems to have deviated significantly. Was the OSPO theme supposed to be a specific implementation of the UW theme? Or is there a plan to reunify them in the future?

Yes, the original plan was that the ospo site would be a fork of the generic uw-jekyll-theme. I was hoping all the core uw-jekyll-theme changes would have already been made, but in reality many of the changes to the theme have been done in the ospo site. Once we clean it up, I'd like to advertise the uw-jekyll-theme for people at UW more generally. I also would like my cranmer-lab site to be based on that uw-jekyll-theme as well (but that also has an inverted time ordering).

Thanks. This all helps put things in a more clear perspective.
I think that creating a cookiecutter (or maybe there is a Ruby equivalent — a question for Henry probably) makes more sense for achieving what the design goal seems to be here, as otherwise all the projects are tied to each other forever (unless you email GitHub support for each individual repo and ask them to sever the "fork" tie between things). This isn't necessarily "bad", but once projects start to deviate then it can start to become a bit strange to have large deviations in the commit history from the parent project and the fork if there isn't any plan for reunification in the future.
Though all of this is discussion for the future too. :)

Yeah, I agree, but it seems to be the pattern used in the original al-folio project
https://github.com/alshedivat/al-folio
It is a bit of a mess for distributing new features from al-folio as well.
Kyle
From: Matthew Feickert @.>
Date: Monday, August 5, 2024 at 4:31 PM
To: UW-Madison-DSI/ospo.wisc.edu-uw-jekyll-theme @.>
Cc: Kyle Stuart Cranmer @.>, Mention @.>
Subject: Re: [UW-Madison-DSI/ospo.wisc.edu-uw-jekyll-theme] actions/jekyll-build-pages is too simple to satisfy Gemfile dependencies (Issue #11)
Thanks. This all helps put things in a more clear perspective.
I think that creating a cookiecutter (or maybe there is a Ruby equivalent — a question for Henry probably) makes more sense for achieving what the design goal seems to be here, as otherwise all the projects are tied to each other forever (unless you email GitHub support for each individual repo and ask them to sever the "fork" tie between things). This isn't necessarily "bad", but once projects start to deviate then it can start to become a bit strange to have large deviations in the commit history from the parent project and the fork if there isn't any plan for reunification in the future.
Though all of this is discussion for the future too. :)
—
Reply to this email directly, view it on GitHubhttps://github.com/UW-Madison-DSI/ospo.wisc.edu-uw-jekyll-theme/issues/11#issuecomment-2269953934, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABCATCU4RHNWPMJ4KTDIG5TZP7VLBAVCNFSM6AAAAABMAOKZUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZHE2TGOJTGQ.
You are receiving this because you were mentioned.Message ID: @.***>


Anchor private feeds

The following are used in paid Spotify subscriptions. I’m not that good with regex, so am lazily leaving it for you, @daveajones (or someone else) to do a PR.
https://anchor.fm/s/%/podcast/auth/%
https://anchor.fm/s/%/podcast/private?token=%

I’ll get these included and tweaked.


[InProgress]C_API & DataLayer

p

It has some accuracy drop while changing double to float.
Maybe it is better for our c_api support both for float_32 and float_64.

@guolinke , it should be , considering most of functional language mixing 32 and 64 type.

I see you're making great progress on the API, thanks!
Looking at the various CreateDataset[...] functions you expose, I have a suggestion. Since you usually have to process any data you from an external process anyway (binning, etc.), it might be worth exposing two versions of LGBM_CreateDatasetFromMat to avoid unnecessary conversion on the external process' end. One LGBM_CreateDataFromRowMajorMat for languages that use row-major order arrays, and a second LGBM_CreateDataFromColMajorMat for languages that use column-major order arrays. Especially with large databases and (somewhat) limited memory, it could be advantageous to not having to transpose the database array on the external process' end before calling LightGBM.

@Allardvm , It is a good suggestion. I think we can add an parameter like "is_row_major" the avoid expose two functions.

That sounds great.

@guolinke , template will make it easy

@chivee I think we cannot use template for expose c_api. C don't have template...

Ops， i forget that
获取 Outlook for Android
On Wed, Nov 2, 2016 at 9:19 PM +0800, "Guolin Ke"<EMAIL_ADDRESS>wrote:
@chivee I think we cannot use template for expose c_api. C don't have template...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@chivee I have finished the interface for dataset part. you can review or refine it now

@guolinke , it's almost ready to merge to master?

refer to #45  #19 #11

@chivee I will merge it after all tests are passed


monitor: remove comma from monitor description

Describe your PR, what does it fix/add?
This PR fixes issue #2457, it sanitize the monitor description, removing all comma from the description, to allow for monitor specific rules to apply.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
I did some code refactor, replacing all m->output->description by m->getOutputDescription(). It should not change anything.
I check the code with my monitor (it have the coma issue) and it works fine.
Is it ready for merging, or does it need work?
It should be ready to merge

Indeed storing it as a class member is more elegant. I just push a revision with it


Grafana or similar mapping for node voltage data etc

As per email, it would be great to be able to see more detail of the node voltages etc by way of more detailed graphs. Thanks!

I've now implemented a new device metrics graph. More info in this comment: https://github.com/liamcottle/meshtastic-map/issues/46#issuecomment-2323656687


fix: Initial merge, created new action

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Stats element does not work in iOS

After touching the "Stats" element from the post's drop-down menu, the menu collapses and no stats appear.

Addressed in v1.15.1


conn(dm): add timeout for Conn

Signed-off-by: lance6716<EMAIL_ADDRESS>
What problem does this PR solve?

Issue Number: close #3733
What is changed and how it works?
Conn will block until either a connection is returned or ctx is canceled

we manually add a timeout
Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
 `None`.

/cc @buchuitoudegou

/merge

/run-dm-integration-test
/run-verify

/run-dm-integration-test

/run-dm-integration-test

/merge

/run-verify

Codecov Report

Merging #6055 (a552697) into master (5c5c5a5) will increase coverage by 0.0603%.
The diff coverage is 59.4339%.

Flag
Coverage Δ

cdc
63.1469% <58.3333%> (+0.0014%)
:arrow_up:

dm
51.9787% <100.0000%> (+0.0585%)
:arrow_up:

engine
62.7248% <58.2278%> (+0.2447%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6055        +/-   ##
================================================
+ Coverage   57.7148%   57.7751%   +0.0602%
================================================
  Files           699        699
  Lines         82743      82738         -5
================================================
+ Hits          47755      47802        +47
+ Misses        30637      30593        -44
+ Partials       4351       4343         -8


[TACHYON-1302] Add replay cache for handling retried RPCs

https://tachyon.atlassian.net/browse/TACHYON-1302
This is part one for TACHYON-1302. Part two will be applying the cache in all RPCs.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6800/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6801/
Test PASSed.

@aaudiber thank you for the PR ... overall it looks good, but I left some minor comments

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6813/
Test PASSed.

@yupeng9 @jsimsa PTAL, this is blocking us from stopping the build from failing 50% of the time.

LGTM

LGTM

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6819/
Test FAILed.

Jenkins, why do you fail to fetch :(
Jenkins, test this please.

Jenkins, test this please.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6823/
Test FAILed.

Jenkins, test this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6825/
Test PASSed.


ng generate @angular/material:material-nav not working

Versions
Angular CLI: 6.0.3
Node: 10.1.0
OS: darwin x64
Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.6.3
@angular-devkit/core         0.6.3
@angular-devkit/schematics   0.6.3
@schematics/angular          0.6.3
@schematics/update           0.6.3
rxjs                         6.1.0
typescript                   2.7.2

Repro steps

ng new my-new-app --routing
ng add @angular/material
npm install
ng generate @angular/material:material-nav --name=home
ng serve

Observed behavior
Fails to compile with the following error:
ERROR in src/app/home/home.component.ts(13,3): error TS2322: Type ‘Observable’ is not assignable to type ‘Observable’. Type ‘boolean’ is not assignable to type ‘BreakpointState’.
The code causing the error is the generated code from step 4 above (home.component.ts)
sHandset$: Observable<BreakpointState> = this.breakpointObserver.observe(Breakpoints.Handset)
.pipe(
map(result => result.matches)
);

Desired behavior
ng serve should compile and run the generated application locally without the observed error.
Mention any other details that might be useful (optional)
OS Mac OSX High Sierra

This is an issue in Angular Material, not in Angular CLI. And it was fixed in https://github.com/angular/material2/pull/11448

Change
isHandset$: Observable =
in
isHandset$: Observable =

Sorry, change
isHandset$: Observable =
in
isHandset$: Observable =

Sorry Change BreakpointState in boolean

Change :
isHandset$: Observable = this.breakpointObserver
.observe(Breakpoints.Handset)
.pipe(map(result => result.matches));

Change:
isHandset$: Observable<BreakpointState> = this.breakpointObserver
.observe(Breakpoints.Handset)
.pipe(map(result => result.matches));
in
isHandset$: Observable<boolean> = this.breakpointObserver
.observe(Breakpoints.Handset)
.pipe(map(result => result.matches));

Closing this issue as I have a manual workaround based on angular/material2#11448


Can you provide the paper titled "Information-Theoretic Testing and Debugging of Fairness Defects in Deep Neural Networks"

Thank you for the coding. Where can I get the access to the full paper to have a better understanding of your novel idea?

The link to the paper is added.


Update CONTRIBUTORS.md

Thanks for joining Pull Request Club!

Thank you @kyzn! I got this message I can't confirm the PR on GitHub. If you think this is an error, please contact us. when trying to mark the task as Done. Can you help please? Thanks!

Hi @emen , apologies for the issue. I went ahead and marked the PR as done on your behalf. Thanks again for joining the Pull Request Club!

Thank you @kyzn!


eliminate predicate which is pushed to storage engine

Currently, although we push down predicates to StorageEngine, but we do it in OlapScanner again. This is a waste for query which will read too many rows from Engine.
we should reduce this eval operation, which need us to eliminate the predicates which can be done in Storage Engine.
It is difficult that we has normalize user predicates, and there is no relation between user predicates and Storage filter.

Are we not doing this because we don’t trust the filtering of the storage engine?


How to check file types and reject when added

RT.

This is an awful solution - not a solution really. more of a workaround.. and a bad user experience ..
The user select a file they thing is ok(because we dont limit the input) and then we cancel their selected ..
cant be the best solution you can come up with.
@AidasK

It's not a workaround, it's how it was created at that time

Please ignore my comment i just went over the code and saw you have an option to add "accept" through attributes object - which is what i was looking for.


Add banner to the readme.md

@Femme-js I want to work on this. Can you please assign this to me??

@Femme-js  can you please describe specifically what should be include in banner??

@Femme-js  can you please describe specifically what should be include in banner??


feat: the prayer times screen

resolves #84

:tada: This PR is included in version 1.4.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Feature request: i18n support

Hi, is there any plan to add i18n support in the project?

Hi, thanks for the suggestion. At the moment, I don't have plans to add i18n suppor, I encourage contributors to try implementing it as needed.


TypeObjectRegistry refactor [21134]

Description
This PR only regenerate the IDL files.
Related implementation PR:

eprosima/fast-dds#4874

Contributor Checklist

[x] Commit messages follow the project guidelines.
N/A Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
N/A Changes are API compatible.
N/A Applicable backports have been included in the description.

Reviewer Checklist

[ ] The PR has a milestone assigned.
[ ] The title and description correctly express the PR's purpose.
[ ] Check contributor checklist is correct.
[ ] Check CI results: changes do not issue any warning.
[ ] Check CI results: failing tests are unrelated with the changes.

[Manual CI] passed ✅


Window size for paging does not match returned results for the discovery endpoint.

Describe the bug
When you go to the Endpoint /server/api/discover/search/objects?size=1000 and you pass the size Parameter with a value bigger than 100 (like above), the embedded searchResult JSON-Object returns only 100 objects even if there are more Elements found. The page JSON-Object will show that the size is 1000 and the paging is taking this into account but the "objects"-Array inside the searchResult will only return the first 100 objects found for the specified page.
To Reproduce
Steps to reproduce the behavior:

In the HAL-Browser, go to the Endpoint /server/api/discover/search/objects
Pass the size parameter at the End of the URL with a value bigger than 100
Look at the page Object inside the searchResult Object and if the totalElements exceeds the 100, the objects array will still max 100 elements even if the size defined for the page is bigger.

Expected behavior
The paging should match the returned results. Means, when the size parameter is bigger than 100 and the returned result is only 100 then the size parameter should fallback to 100 or the returned results should match the size parameter. Otherwise it would result in skipping elements for every page if the window size for the specified page does not match the results.

DLCorp would like to claim this issue. It is closely related to issues #8576 and #8577. It would be a great addition to our yet-to-be-review PR #8840.
Our estimated time for this is about 6 hours of contribution.

Sure, @buithaihai ! Please feel free to add to the existing PR or open a new one (your choice).  Thanks!

@tdonohue Would you mind taking a look at this pull request: #8840? It has been dormant for too long.


Simplify blocking Delay.

Quick summary of discussions in #177 and in today's REWG meeting:

We need a hardawre-agnostic, efficient way of representing time durations for use in the e-h traits, but that's probably far away.
The current DelayMs/DelayUs traits are not the answer, they require duplicating impls for each unit and each integer size.
There's issues where HALs don't implement all DelayMs/DelayUs combinations, causing some drivers to not work with them.
However, "blocking delay" is an incredibly important and widely used trait, releasing 1.0 without it is not an option.

The compromise found to unblock 1.0 while mitigating the issues is:

remove DelayMs
change DelayUs to use u32 instead of generic width integers.

Why:

Fixes the pain of HALs not implementing all combinations.
For the most common use cases (blinks, waiting for chips to initialize...) microsecond precision is enough.
u32 allows for a max delay of ~1.2h. Such blocking delays should be extremely rare, as the core can do absolutely nothing else during it (unless it uses interrupts, but then you're probably already doing interrupt-based timers).
The runtime cost of forcing using 32bit is negligible, most HALs are already doing 32bit math on the duration to convert it to clock ticks.

The name Delay is reserved for the future trait that will use the new shiny Duration representation, hence DelayUs is kept even though there's only one trait.
When the final Delay trait is released, we may (or may not if we still think it's handy) deprecate DelayUs.

r? @eldruin
(rust-highfive has picked a reviewer for you, use r? to override)

goddamnit I didn't see #312 :rofl:


Where to ask questions?

Hey, thanks for setting this up, looks nice. So where is a good place to ask questions? Do I just open an issue here? Should we have multiple repositories beside "awesome-iontraps"?

test

That's a good question. I think this repo should provide useful links in the readme and for general questions we can use the discussions.

Or if you just want to say hi, feel free to join us on https://iontraps.slack.com with the following link:
https://join.slack.com/t/iontraps/shared_invite/zt-wivcgsty-BOXHuirgnMFtmvmAFQQpQw


Rename wagtail.wagtailsearch to wagtail.search

Part of #3918
This PR renames wagtail.wagtailsearch to wagtail.search.

Merged in #4069