Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.

You forgot to mention that when building, half of the users will inevitably encounter an error:
[INFO]:    Detected highest available build tools version to be 31.0.0-rc4
[DEBUG]:   -> running gradlew assembleDebug
[DEBUG]:        > Task :javaPreCompileDebug FAILED
[DEBUG]:
[DEBUG]:        FAILURE: Build failed with an exception.
[DEBUG]:
[DEBUG]:        * What went wrong:
[DEBUG]:        Execution failed for task ':javaPreCompileDebug'.
[DEBUG]:        > Could not resolve all files for configuration ':debugCompileClasspath'.
[DEBUG]:           > Could not find com.google.firebase:firebase-bom:27.0.1.
[DEBUG]:             Required by:
[DEBUG]:                 project :
[DEBUG]:           > Could not find com.google.firebase:firebase-messaging:.
[DEBUG]:             Required by:
[DEBUG]:                 project :
[DEBUG]:           > Could not find com.google.firebase:firebase-analytics:.
[DEBUG]:             Required by:
[DEBUG]:                 project :
[DEBUG]:
[DEBUG]:        * Try:
[DEBUG]:        Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[DEBUG]:
[DEBUG]:        * Get more help at https://help.gradle.org
[DEBUG]:
[DEBUG]:        Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
[DEBUG]:        Use '--warning-mode all' to show the individual deprecation warnings.
[DEBUG]:        See https://docs.gradle.org/6.4.1/userguide/command_line_interface.html#sec:command_line_warnings
[DEBUG]:
[DEBUG]:        BUILD FAILED in 3s
[DEBUG]:        3 actionable tasks: 1 executed, 2 up-to-date

Python-for-Android seems incompatible with Gradle 7. Could you try downgrading by setting
distributionUrl=https\://services.gradle.org/distributions/gradle-6.4.1-all.zip

in
pythonforandroid/bootstraps/common/build/gradle/wrapper/gradle-wrapper.properties

@Fox520 This is the default and has not been changed by me.

@Fox520 Full stacktrace:
[INFO]:    Detected highest available build tools version to be 31.0.0-rc4
[DEBUG]:   -> running gradlew assembleDebug
[DEBUG]:        Starting a Gradle Daemon (subsequent builds will be faster)
[DEBUG]:        > Task :javaPreCompileDebug FAILED
[DEBUG]:
[DEBUG]:        FAILURE: Build failed with an exception.
[DEBUG]:
[DEBUG]:        * What went wrong:
[DEBUG]:        Execution failed for task ':javaPreCompileDebug'.
[DEBUG]:        > Could not resolve all files for configuration ':debugCompileClasspath'.
[DEBUG]:           > Could not resolve com.google.firebase:firebase-bom:28.0.1.
[DEBUG]:             Required by:
[DEBUG]:                 project :
[DEBUG]:              > Could not resolve com.google.firebase:firebase-bom:28.0.1.
[DEBUG]:                 > Could not get resource 'https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-bom/28.0.1/firebase-bom-28.0.1.pom'.
[DEBUG]:                    > Could not GET 'https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-bom/28.0.1/firebase-bom-28.0.1.pom'.
[DEBUG]:                       > dl.google.com: nodename nor servname provided, or not known
[DEBUG]:              > Could not resolve com.google.firebase:firebase-bom:28.0.1.
[DEBUG]:                 > Could not get resource 'https://jcenter.bintray.com/com/google/firebase/firebase-bom/28.0.1/firebase-bom-28.0.1.pom'.
[DEBUG]:                    > Could not GET 'https://jcenter.bintray.com/com/google/firebase/firebase-bom/28.0.1/firebase-bom-28.0.1.pom'.
[DEBUG]:                       > jcenter.bintray.com: nodename nor servname provided, or not known
[DEBUG]:           > Could not find com.google.firebase:firebase-messaging:.
[DEBUG]:             Required by:
[DEBUG]:                 project :
[DEBUG]:           > Could not find com.google.firebase:firebase-analytics:.
[DEBUG]:             Required by:
[DEBUG]:                 project :
[DEBUG]:
[DEBUG]:        * Try:
[DEBUG]:        Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[DEBUG]:
[DEBUG]:        * Get more help at https://help.gradle.org
[DEBUG]:
[DEBUG]:        Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
[DEBUG]:        Use '--warning-mode all' to show the individual deprecation warnings.
[DEBUG]:        See https://docs.gradle.org/6.4.1/userguide/command_line_interface.html#sec:command_line_warnings
[DEBUG]:
[DEBUG]:        BUILD FAILED in 2m 18s
[DEBUG]:        3 actionable tasks: 3 executed

Exception in thread background thread for pid 10519:
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 926, in _bootstrap_inner
    self.run()
  File<EMAIL_ADDRESS>line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.7/site-packages/sh.py", line 1633, in wrap
    fn(*rgs, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/sh.py", line 2557, in background_thread
    handle_exit_code(exit_code)
  File "/usr/local/lib/python3.7/site-packages/sh.py", line 2261, in fn
    return self.command.handle_command_exit_code(exit_code)
  File "/usr/local/lib/python3.7/site-packages/sh.py", line 861, in handle_command_exit_code
    raise exc
sh.ErrorReturnCode_1:

  RAN: /Users/macbookair/Projects/My-Project/pushyy-main/.buildozer/android/platform/build-armeabi-v7a/dists/youtube__armeabi-v7a/gradlew assembleDebug

  STDOUT:
Starting a Gradle Daemon (subsequent builds will be faster)
> Task :javaPreCompileDebug FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':javaPreCompileDebug'.
> Could not resolve all files for configuration ':debugCompileClasspath'.
   > Could not resolve com.google.firebase:firebase-bom:28.0.1.
     Required by:
         project :
      > Could not resolve com.google.firebase:firebase-bom:28.0.1.
         > Could not get resource 'https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-bom/28.0.1/firebase-bom-28.0.1.pom'.
            > Could not GET 'https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-bom/28.0.1/firebase-bom-28.0.1.pom'.
               > dl.google.com: nodename nor servname provided, or not known
      > Could not resolve com.google.firebase:firebase-bom:28.0.1.
         > Could not get resource 'https://jcenter.bintray.com/com/google/firebase/firebase-bom/28.0.1/firebase-bom-28.0.1.pom'.
            > Could not GET 'https://jcenter.bintray.com/com/google/firebase/firebase-bom/28.0.1/firebase-bom-28.0.1.pom'.
               > jcenter.bintray.com: nodename nor servname provided, or not known
   > Could not find com.google.firebase:firebase-messaging:.
     Required by:
         project :
   > Could not find com.google.firebase:firebase-analytics:.
     Required by:
         project :

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.4.1/userguide/command_line_interface.html#sec:command_line_warnings

hi i am having the same problem waiting for the solutions

I'm checking it out though I can't provide an ETA

@HeaTTheatR I can't seem to replicate the issue on a fresh install of Ubuntu 18.04
Can you try enabling androidx by adding android.enable_androidx = True in the buildozer.spec

This is an easy task , i managed to build my project kivy with firebase by just using buildozer android clean and setting it the spec using below
[app]
(str) Title of your application
title = My Application
(str) Package name
package.name = myapp
(str) Package domain (needed for android/ios packaging)
package.domain = org.test
(str) Source code where the main.py live
source.dir = .
(list) Source files to include (let empty to include all the files)
source.include_exts = py,png,jpg,kv,atlas
(list) List of inclusions using pattern matching
#source.include_patterns = assets/,images/.png
(list) Source files to exclude (let empty to not exclude anything)
#source.exclude_exts = spec
(list) List of directory to exclude (let empty to not exclude anything)
#source.exclude_dirs = tests, bin, venv
(list) List of exclusions using pattern matching
Do not prefix with './'
#source.exclude_patterns = license,images//.jpg
(str) Application versioning (method 1)
version = 0.1
(str) Application versioning (method 2)
version.regex = version = '"['"]
version.filename = %(source.dir)s/main.py
(list) Application requirements
comma separated e.g. requirements = sqlite3,kivy
requirements = python3==3.8.13,hostpython3==3.8.13,kivy,pillow
(str) Custom source folders for requirements
Sets custom source for any requirements with recipes
requirements.source.kivy = ../../kivy
(str) Presplash of the application
#presplash.filename = %(source.dir)s/data/presplash.png
(str) Icon of the application
#icon.filename = %(source.dir)s/data/icon.png
(str) Supported orientation (one of landscape, sensorLandscape, portrait or all)
orientation = portrait
(list) List of service to declare
#services = NAME:ENTRYPOINT_TO_PY,NAME2:ENTRYPOINT2_TO_PY

OSX Specific

author = © Copyright Info
change the major version of python used by the app
osx.python_version = 3
Kivy version to use
osx.kivy_version = 1.9.1

Android specific

(bool) Indicate if the application should be fullscreen or not
fullscreen = 0
(string) Presplash background color (for android toolchain)
Supported formats are: #RRGGBB #AARRGGBB or one of the following names:
red, blue, green, black, white, gray, cyan, magenta, yellow, lightgray,
darkgray, grey, lightgrey, darkgrey, aqua, fuchsia, lime, maroon, navy,
olive, purple, silver, teal.
#android.presplash_color = #FFFFFF
(string) Presplash animation using Lottie format.
see https://lottiefiles.com/ for examples and https://airbnb.design/lottie/
for general documentation.
Lottie files can be created using various tools, like Adobe After Effect or Synfig.
#android.presplash_lottie = "path/to/lottie/file.json"
(str) Adaptive icon of the application (used if Android API level is 26+ at runtime)
#icon.adaptive_foreground.filename = %(source.dir)s/data/icon_fg.png
#icon.adaptive_background.filename = %(source.dir)s/data/icon_bg.png
(list) Permissions
#android.permissions = INTERNET
(list) features (adds uses-feature -tags to manifest)
#android.features = android.hardware.usb.host
(int) Target Android API, should be as high as possible.
android.api = 32
(int) Minimum API your APK / AAB will support.
android.minapi = 23
(int) Android SDK version to use
android.sdk = 32
(str) Android NDK version to use
#android.ndk = 19b
(int) Android NDK API to use. This is the minimum API your app will support, it should usually match android.minapi.
#android.ndk_api = 21
(bool) Use --private data storage (True) or --dir public storage (False)
#android.private_storage = True
(str) Android NDK directory (if empty, it will be automatically downloaded.)
#android.ndk_path =
(str) Android SDK directory (if empty, it will be automatically downloaded.)
#android.sdk_path =
(str) ANT directory (if empty, it will be automatically downloaded.)
#android.ant_path =
(bool) If True, then skip trying to update the Android sdk
This can be useful to avoid excess Internet downloads or save time
when an update is due and you just want to test/build your package
android.skip_update = False
(bool) If True, then automatically accept SDK license
agreements. This is intended for automation only. If set to False,
the default, you will be shown the license when first running
buildozer.
android.accept_sdk_license = False
(str) Android entry point, default is ok for Kivy-based app
#android.entrypoint = org.kivy.android.PythonActivity
(str) Full name including package path of the Java class that implements Android Activity
use that parameter together with android.entrypoint to set custom Java class instead of PythonActivity
#android.activity_class_name = org.kivy.android.PythonActivity
(str) Extra xml to write directly inside the  element of AndroidManifest.xml
use that parameter to provide a filename from where to load your custom XML code
#android.extra_manifest_xml = ./src/android/extra_manifest.xml
(str) Extra xml to write directly inside the  tag of AndroidManifest.xml
use that parameter to provide a filename from where to load your custom XML arguments:
#android.extra_manifest_application_arguments = ./src/android/extra_manifest_application_arguments.xml
(str) Full name including package path of the Java class that implements Python Service
use that parameter to set custom Java class instead of PythonService
#android.service_class_name = org.kivy.android.PythonService
(str) Android app theme, default is ok for Kivy-based app
android.apptheme = "@android:style/Theme.NoTitleBar"
(list) Pattern to whitelist for the whole project
#android.whitelist =
(str) Path to a custom whitelist file
#android.whitelist_src =
(str) Path to a custom blacklist file
#android.blacklist_src =
(list) List of Java .jar files to add to the libs so that pyjnius can access
their classes. Don't add jars that you do not need, since extra jars can slow
down the build process. Allows wildcards matching, for example:
OUYA-ODK/libs/*.jar
#android.add_jars = foo.jar,bar.jar,path/to/more/*.jar
(list) List of Java files to add to the android project (can be java or a
directory containing the files)
#android.add_src =
(list) Android AAR archives to add
#android.add_aars =
(list) Put these files or directories in the apk assets directory.
Either form may be used, and assets need not be in 'source.include_exts'.
1) android.add_assets = source_asset_relative_path
2) android.add_assets = source_asset_path:destination_asset_relative_path
#android.add_assets =
(list) Gradle dependencies to add
android.gradle_dependencies = com.google.android.gms:play-services-base:18.0.1, com.google.firebase:firebase-bom:29.3.1, com.google.firebase:firebase-analytics:20.1.2
(bool) Enable AndroidX support. Enable when 'android.gradle_dependencies'
contains an 'androidx' package, or any package from Kotlin source.
android.enable_androidx requires android.api >= 28
android.enable_androidx = True
(list) add java compile options
this can for example be necessary when importing certain java libraries using the 'android.gradle_dependencies' option
see https://developer.android.com/studio/write/java8-support for further information
android.add_compile_options = "sourceCompatibility = 1.8", "targetCompatibility = 1.8"
(list) Gradle repositories to add {can be necessary for some android.gradle_dependencies}
please enclose in double quotes
e.g. android.gradle_repositories = "maven { url 'https://kotlin.bintray.com/ktor' }"
#android.add_gradle_repositories =
(list) packaging options to add
see https://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.PackagingOptions.html
can be necessary to solve conflicts in gradle_dependencies
please enclose in double quotes
e.g. android.add_packaging_options = "exclude 'META-INF/common.kotlin_module'", "exclude 'META-INF/*.kotlin_module'"
#android.add_packaging_options =
(list) Java classes to add as activities to the manifest.
#android.add_activities = com.example.ExampleActivity
(str) OUYA Console category. Should be one of GAME or APP
If you leave this blank, OUYA support will not be enabled
#android.ouya.category = GAME
(str) Filename of OUYA Console icon. It must be a 732x412 png image.
#android.ouya.icon.filename = %(source.dir)s/data/ouya_icon.png
(str) XML file to include as an intent filters in  tag
#android.manifest.intent_filters =
(str) launchMode to set for the main activity
#android.manifest.launch_mode = standard
(list) Android additional libraries to copy into libs/armeabi
#android.add_libs_armeabi = libs/android/.so
#android.add_libs_armeabi_v7a = libs/android-v7/.so
#android.add_libs_arm64_v8a = libs/android-v8/.so
#android.add_libs_x86 = libs/android-x86/.so
#android.add_libs_mips = libs/android-mips/*.so
(bool) Indicate whether the screen should stay on
Don't forget to add the WAKE_LOCK permission if you set this to True
#android.wakelock = False
(list) Android application meta-data to set (key=value format)
#android.meta_data =
(list) Android library project to add (will be added in the
project.properties automatically.)
#android.library_references =
(list) Android shared libraries which will be added to AndroidManifest.xml using  tag
#android.uses_library =
(str) Android logcat filters to use
#android.logcat_filters = *:S python:D
(bool) Android logcat only display log for activity's pid
#android.logcat_pid_only = False
(str) Android additional adb arguments
#android.adb_args = -H host.docker.internal
(bool) Copy library instead of making a libpymodules.so
#android.copy_libs = 1
(list) The Android archs to build for, choices: armeabi-v7a, arm64-v8a, x86, x86_64
In past, was android.arch as we weren't supporting builds for multiple archs at the same time.
android.archs = arm64-v8a
(int) overrides automatic versionCode computation (used in build.gradle)
this is not the same as app version and should only be edited if you know what you're doing
android.numeric_version = 1
(bool) enables Android auto backup feature (Android API >=23)
android.allow_backup = True
(str) XML file for custom backup rules (see official auto backup documentation)
android.backup_rules =
(str) If you need to insert variables into your AndroidManifest.xml file,
you can do so with the manifestPlaceholders property.
This property takes a map of key-value pairs. (via a string)
Usage example : android.manifest_placeholders = [myCustomUrl:"org.kivy.customurl"]
android.manifest_placeholders = [:]
(bool) disables the compilation of py to pyc/pyo files when packaging
android.no-compile-pyo = True
(str) The format used to package the app for release mode (aab or apk).
android.release_artifact = aab

Python for android (p4a) specific

(str) python-for-android URL to use for checkout
#p4a.url =
(str) python-for-android fork to use in case if p4a.url is not specified, defaults to upstream (kivy)
#p4a.fork = kivy
(str) python-for-android branch to use, defaults to master
#p4a.branch = master
(str) python-for-android specific commit to use, defaults to HEAD, must be within p4a.branch
#p4a.commit = HEAD
(str) python-for-android git clone directory (if empty, it will be automatically cloned from github)
#p4a.source_dir =
(str) The directory in which python-for-android should look for your own build recipes (if any)
#p4a.local_recipes =
(str) Filename to the hook for p4a
#p4a.hook =
(str) Bootstrap to use for android builds
p4a.bootstrap = sdl2
(int) port number to specify an explicit --port= p4a argument (eg for bootstrap flask)
#p4a.port =
Control passing the --use-setup-py vs --ignore-setup-py to p4a
"in the future" --use-setup-py is going to be the default behaviour in p4a, right now it is not
Setting this to false will pass --ignore-setup-py, true will pass --use-setup-py
NOTE: this is general setuptools integration, having pyproject.toml is enough, no need to generate
setup.py if you're using Poetry, but you need to add "toml" to source.include_exts.
#p4a.setup_py = false
(str) extra command line arguments to pass when invoking pythonforandroid.toolchain
#p4a.extra_args =

iOS specific

(str) Path to a custom kivy-ios folder
#ios.kivy_ios_dir = ../kivy-ios
Alternately, specify the URL and branch of a git checkout:
ios.kivy_ios_url = https://github.com/kivy/kivy-ios
ios.kivy_ios_branch = master
Another platform dependency: ios-deploy
Uncomment to use a custom checkout
#ios.ios_deploy_dir = ../ios_deploy
Or specify URL and branch
ios.ios_deploy_url = https://github.com/phonegap/ios-deploy
ios.ios_deploy_branch = 1.10.0
(bool) Whether or not to sign the code
ios.codesign.allowed = false
(str) Name of the certificate to use for signing the debug version
Get a list of available identities: buildozer ios list_identities
#ios.codesign.debug = "iPhone Developer:   ()"
(str) The development team to use for signing the debug version
#ios.codesign.development_team.debug =
(str) Name of the certificate to use for signing the release version
#ios.codesign.release = %(ios.codesign.debug)s
(str) The development team to use for signing the release version
#ios.codesign.development_team.release =
(str) URL pointing to .ipa file to be installed
This option should be defined along with display_image_url and full_size_image_url options.
#ios.manifest.app_url =
(str) URL pointing to an icon (57x57px) to be displayed during download
This option should be defined along with app_url and full_size_image_url options.
#ios.manifest.display_image_url =
(str) URL pointing to a large icon (512x512px) to be used by iTunes
This option should be defined along with app_url and display_image_url options.
#ios.manifest.full_size_image_url =
[buildozer]
(int) Log level (0 = error only, 1 = info, 2 = debug (with command output))
log_level = 2
(int) Display warning if buildozer is run as root (0 = False, 1 = True)
warn_on_root = 1
(str) Path to build artifact storage, absolute or relative to spec file
build_dir = ./.buildozer
(str) Path to build output (i.e. .apk, .aab, .ipa) storage
bin_dir = ./bin
-----------------------------------------------------------------------------
List as sections

You can define all the "list" as [section:key].
Each line will be considered as a option to the list.
Let's take [app] / source.exclude_patterns.
Instead of doing:

#[app]
#source.exclude_patterns = license,data/audio/.wav,data/images/original/

This can be translated into:

#[app:source.exclude_patterns]
#license
#data/audio/.wav
#data/images/original/

-----------------------------------------------------------------------------
Profiles

You can extend section / key with a profile
For example, you want to deploy a demo version of your application without
HD content. You could first change the title to add "(demo)" in the name
and extend the excluded directories to remove the HD content.

#[app@demo]
#title = My Application (demo)

#[app:source.exclude_patterns@demo]
#images/hd/*

Then, invoke the command line with the "demo" profile:

#buildozer --profile demo android debug
you should use the latest API version , and minimum api to 23 ,     then enabling android.enable_androidx thanks

any updates ? please tell if my solution works for you :) thanks

please add me on the kivymd builder project so i can help to figure out other challenges you had experience

I also was able to fix this error partially with the steps from here.


Public-access/self-registration for Metabase

Or possibly look into other options? Otherwise been very impressed w/ Metabase

This is enabled via google sign in. There is still pending verification to allow for more than 100 user sign up but for that I would need help from Jamie to put verification code in a file in specific location on server for dewi.org.

After setting to in production, verification is not required. we have already seen few users logging in with google sign in. so we can consider this implementation successful and complete.

Woohoo, nicely done!

Having issues logging in via Google, any tips?


fixed url_launcher link in url_launcher_web README

Description
fixed url_launcher link in url_launcher_web README. It was being sent to 404 not found
Related Issues
Fixes https://github.com/flutter/flutter/issues/57819
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@googlebot I signed it!

@googlebot I signed it!

@googlebot I signed it!

@googlebot I signed it!

@googlebot I fixed it.


Fix build files by updating Grale version

Also updated .gitignore.

@shawnbuso Review, please?

LGTM


Breaking changes with django-filter 0.15

This is a heads up to notify you about breaking changes with django-filter's develop branch.
See https://github.com/carltongibson/django-filter/pull/459#issuecomment-242292309.

Thx. I guess who needs this feature to be updated will send a patch.

django-filter 0.15 is now released, projects that use drf-gis and django-filter 0.15 are broken.

#117 was merged


Feature: handle mempool paused

marking as draft request because would like to squash all my adapter changes into single commit and rebase other changes


improvement combination.py using memoization

#357 I try to improve combination.py
(Put an X inside the [ ] to denote check mark [X].)

[ ] If creating a new file :

[ ] added links to it in the README files ?
[ ] included tests with it ?
[ ] added description (overview of algorithm, time and space compleixty, and possible edge case) in docstrings ?

[X] if done some changes :

[X] wrote short description in the PR explaining what the changes do ?
[X] Fixes #[issue number] if related to any issue

[ ] other

I forgot check parameter
combination_memo(50, 10) <- before
combination_memo(50, 10) <- after

Pull Request Test Coverage Report for Build 640

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 70.951%

Totals

Change from base Build 638:
0.1%

Covered Lines:
3632

Relevant Lines:
5119

💛  - Coveralls

you can use factorial and combination function.
https://github.com/huseyindalbudak/mathpy/blob/master/combination.py
the code is so faster for combination(50, 10) than keon algorithms


How can I disable the updater

It was mentioned that the updater can be disabled by the user. Unfortunately he forgot to say how this is done. So, tell me, please.

Open Task Scheduler, locate entry called ViGEmBusUpdater and disabled that.


Tests not passing since last commit

06caaaac409b5d9e0ce5caad753f8b1f0f7db722

modified the package for custom needs.
Readme, tests have to be updated

It is not the tests. Failed conditions are being returned as true.


RFC: Built-in support for HTTP mocking

There's often a need to mock network calls when writing unit tests. While one can use jest.mock to implement the http API of your choice - or use modules like jest-fetch-mock that only works for fetch - this is often technical debt the moment you swap out your HTTP abstraction. If one migrates to request or axios, they often have to also switch out their mock implementation. This pain is potentially even worse if moving from e.g. traditional xhr requests to fetch, or vice versa. Or even starting to use GraphQL instead of the more traditional REST based approaches.
One could set up a mock server with some canned responses (e.g. create-test-server is nice), but that is often slower than you want it to be, especially for unit tests which needs to run against a clean instance every single test.
A third alternative, and what I want to see in Jest, is to mock out the http layer of the runtime. nock is a module which does this for node (so works fine also for JSDom based tests), but I find its API clunky to use and work with. Other alternatives are sinon or faux-jax.
If we could provide a simpler and/or more intuitive API out of the box with Jest, I think that might solve a lot of common issues where people today find solutions to plug into Jest.
I don't have any particular API suggestions here, but I think something akin to jest.useFakeTimers() (say jest.useFakeNetwork()) with related APIs such as jest.fakeGet('url', {headers}, body) might be a good start. Looking at existing solutions for inspirations sounds like a great way forward! Having something for GraphQL out of the box would be awesome as well.
One source of inspiration beyond sinon and faux-jax could be ava-nock. Especially the NOCK_MODE feature sounds like an awesome watch plugin for jest.

Done! 10 days isn't too bad :D

I'm interested in this. Right now I'm facing an issue where I want to assert that an HTTP request was made with a certain shape (host, path, search, body, etc), without caring about the response or even the return value from the containing function/method.
Do you think that use calls fall under this RFC?

Yes, I'd say so 🙂 The functions would be jest spies essentially, so you would be able to do toHaveBeenCalledWith() and other goodies.

@palmerj3 IIRC you said you had something at Spotify along these lines, any news on that?

@SimenB yeah we have this (something similar) at Spotify and our intention is to open source it this quarter. Happy to hop on video chat sometime and show you how it works.

@palmerj3 awesome! Let's talk about it in Stockholm later this month :)

@palmerj3 @SimenB was there any follow-up to this?

Yeah, @palmerj3 showed it to me, and it looked pretty good! 🙂 I don't know how the effort to open source it is going, though.

+1 Love to see what you're working on @SimenB

any news on this?

Not exactly what this issue is about but we did release this https://github.com/spotify/polly-jest-presets

Doesn't https://github.com/ScaleLeap/jest-polly/ provide this?


Fix warnings

I encountered some warnings in this gem while reviewing orgsync/stoplight#78. This pull request fixes those warnings. I chose the path of least resistance for most of these fixes. Since I don't know this library, there may be better ways to fix them.
Ultimately I think the only commit I really care about is 5647d23f5f03f953d789f1be66d0de61ab09caa5. I think it's causing my JRuby build to fail.

Hi @tfausak! Thank you for the contribution. I took a look at the crash in JRuby and can confirm the crash and the fix. In addition, shadowing the config variable is undesirable and might lead to weird bugs later.
Regarding the use of uninitialized instance variables, this seems to be a fairly standard pattern in Ruby. Have you seen anything in particular which is broken by this syntax? In the meantime, I'm merging this pull request with the caveat of removing 022c3e1 (uninitialized instance variables) and e7aec19 (enable warnings by default). Enabling all warnings turns on a fair amount of chatter from dependencies.
Merged manually in a041d1f.

Using uninitialized instance variables is common in Ruby. I think that is unfortunate, however I don't think it breaks anything. My main motivation for initializing instance variables in this gem was to avoid spurious warning when running the tests in Stoplight. The "chatter" you see when enabling warnings is the same chatter that I see in my gem — and I'm trying to reduce it.

Using uninitialized instance variables is common in Ruby. I think that is unfortunate, however I don't think it breaks anything.

Ah, thank you for the confirmation.

My main motivation for initializing instance variables in this gem was to avoid spurious warning when running the tests in Stoplight. The "chatter" you see when enabling warnings is the same chatter that I see in my gem — and I'm trying to reduce it.

Gotcha. I understand not wanting it in your output and share the sentiment. From the bugsnag gem side, enabling warnings picks up a few things in webmock and httpclient which are not ideal but did not seem harmful. I split the dependency warnings into a separate issue to address later (#257). Thank you for following up.

Thanks!


refactor(transformer): use Option::get_or_insert_with

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

#6299  👈
#6297
#6296
#6295
#6294
#6293
#6290
#6289
#6288
#6287
#6286
main

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

Join @overlookmotel and the rest of your teammates on  Graphite


Dictionary inside list serialization error

I have following code structure:

And when serializing it this error occurs: System.ArgumentNullException: 'Value cannot be null. Parameter name: key'
Stack:
  at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)    at ExtendedXmlSerializer.ExtensionModel.Xml.XmlWriter.CreatePrefix(String identifier)    at ExtendedXmlSerializer.ExtensionModel.Xml.XmlWriter.Get(TypeParts parameter)    at ExtendedXmlSerializer.ExtensionModel.Xml.XmlWriter.GetType(TypeInfo parameter)    at ExtendedXmlSerializer.ExtensionModel.Xml.XmlWriter.Get(MemberInfo parameter)    at ExtendedXmlSerializer.ExtensionModel.Xml.OptimizedNamespaceXmlWriter.Get(MemberInfo parameter)    at ExtendedXmlSerializer.ContentModel.Format.FormattedContent`1.Get(IFormatWriter writer, T instance)    at ExtendedXmlSerializer.ContentModel.Format.ContextualWriter`1.Write(IFormatWriter writer, T instance)    at ExtendedXmlSerializer.ContentModel.DecoratedWriter`1.Write(IFormatWriter writer, T instance)    at ExtendedXmlSerializer.ContentModel.Serializer`1.Write(IFormatWriter writer, T instance)    at ExtendedXmlSerializer.ContentModel.Properties.Property`1.Write(IFormatWriter writer, T instance)    at ExtendedXmlSerializer.ContentModel.Collections.ArrayIdentity.Write(IFormatWriter writer, Array instance)    at ExtendedXmlSerializer.ContentModel.GenericWriterAdapter`1.Write(IFormatWriter writer, Object instance)    at ExtendedXmlSerializer.ContentModel.Content.Enclosure`1.Write(IFormatWriter writer, T instance)    at ExtendedXmlSerializer.ContentModel.SerializerAdapter`1.Write(IFormatWriter writer, T instance)    at ExtendedXmlSerializer.ExtensionModel.RootInstanceExtension.Serializer.Write(IFormatWriter writer, Object instance)    at ExtendedXmlSerializer.ExtensionModel.Xml.Write.Execute(Writing parameter)    at ExtendedXmlSerializer.ExtensionModel.Xml.Serializer.Serialize(XmlWriter writer, Object instance)    at ExtendedXmlSerializer.ExtensionModel.Xml.ExtendedXmlSerializer.Serialize(XmlWriter writer, Object instance)    at ExtendedXmlSerializer.ExtensionModel.Xml.InstanceFormatter.Get(Object parameter)    at ExtendedXmlSerializer.ExtensionMethodsForSerialization.Serialize(IExtendedXmlSerializer this, XmlWriterSettings settings, Object instance)
If this object is serialized by itself (and not inside the list) everything works fine.

Thanks for reporting this, @maxkoshevoi.  Unfortunately I was not able to reproduce this by eyeballing your schema.  I may have overlooked something though.  Here is the passing test in our suite:
https://github.com/ExtendedXmlSerializer/home/blob/147e8a80acc67b0fd50ce383c3ab5d850402abe0/test/ExtendedXmlSerializer.Tests.ReportedIssues/Issue423Tests.cs
Could I bother you to get a minimal repro with code you are using that generates this error?  It could be party due to how you are configuring the container as well.

FWIW I did have an inaccuracy, in that I was not using multiple dictionaries within each instance.  I have addressed this and updated the test here:
https://github.com/ExtendedXmlSerializer/home/blob/744f3e628116cfad4460401fb41710b0d6c2b72e/test/ExtendedXmlSerializer.Tests.ReportedIssues/Issue423Tests.cs
It still passes, and I am actually entirely surprised that it does. 😅

Thanks for quick response! Here is console app that reproduces the issue: https://github.com/maxkoshevoi/ExtendedXmlSerializer-423

OK great, thank you for that.  Looks like the issue is with EnableImplicitTypingFromNamespace.  If I remove that it appears to work OK.  I will dig around and see if this can be patched up.

Ah, to be more specific it has to do with combining several extensions.  I am able to reproduce this with the following configuration:
var serializer = new ConfigurationContainer().UseOptimizedNamespaces().EnableImplicitTyping(typeof(NewOptionSetFieldInfo)).Create();

Yeah, I have EnableImplicitTypingFromNamespace cause as you can see I have several models that extend each other (more than in the provided sample) and I need to serialize and deserialize list of all of them. And UseOptimizedNamespaces is kink of a best practice, right?

Yes you are correct.  There shouldn't be a problem with combining these extensions and this all should work.
Looking into it further, it's a very specific set of conditions:

UseOptimizedNamespaces
EnableImplicitTyping*
Use of read-only list/dictionary property.
Root instance of T[].

I have been able to reproduce it with this as a minimum:
[Fact]
public void VerifyReported()
{
	var subject = new Subject();
	var element = new[] { subject };

	var serializer = new ConfigurationContainer().UseOptimizedNamespaces()
	                                             .EnableImplicitTyping(typeof(Subject))
	                                             .Create();
	serializer.Serialize(element);

}

sealed class Subject
{
	public List<string> Values { get; } = new List<string>();
}

Note that if I do the following it works:
var element = new[] { subject }.ToList();

I would be interested in seeing that unblocks you for the time-being as I track this down.

I used array instead of list, case List serializes with capacity info. So there is excess data in serialized XML and I think users can break serialization by changing it (or by not changing it and adding elements to the list).
This issue is not super urgent, it can wait a couple of days. I will revert to using list if there wouldn't be a fix by then.
Thank you for such quick troubleshooting and workaround!

Yep, I hear you on the Capacity.  You can configure to ignore it but it's a bit of a hassle.
FWIW I found another workaround for you that allows you to use Array.  You have to add it as an implicit type.  You can do the following:
var serializer = new ConfigurationContainer().UseOptimizedNamespaces()
											 .EnableImplicitTyping(new AllTypesInSameNamespace<NewOptionSetFieldInfo>().Append(typeof(Array)))
											 .Create();

That seems to work, but would be interested in knowing on your side if there are any further issues you find with it.

Looks solid. I think I'll use that one for the meanwhile.
Thank you, I'll reach out if there will be any issues.

Cool!  Yeah, this looks like a tricky one so it might be a bit before I get a fix in.  I should be able to dedicate some time tomorrow and will update here with any news. 👍

Alright, good news @maxkoshevoi I managed to figure out a fix:
https://github.com/ExtendedXmlSerializer/home/pull/424#issuecomment-672267042
That's the good news.  The bad news is that the fix is in the core XmlWriter component which is used by everything.  All our tests pass but even at 1200+ passing tests, it makes me nervous to publish and possibly break someone else out there.  Oh well, such is the life of software development/deployment. 😁
Anyways, let me know if that build treats you better.  I release every Tuesday, but since this one might be impacting I will let it sit until next Tuesday and see if I can think of a better solution.  Please feel free to use the preview build until then (and let me know of any further issues you encounter).

This has been deployed to NuGet:
https://www.nuget.org/packages/ExtendedXmlSerializer/
Please do let me know of any problems you find and I will investigate.  Thank you for improving the quality of ExtendedXmlSerializer!  Closing this issue for now.


Fix JS to replace liveblog plugin

Coverage remained the same at 95.96% when pulling 67536d5ca575954ed90b72f473ff57df866d57cf on feature/liveblog_fixes into 51c99f6f79d0e6f80d9e2a49b264fdf9d03b4bcd on develop.

Current coverage is 92.41% (diff: 100%)

Merging #329 into develop will not change coverage

@@            develop       #329   diff @@
==========================================
  Files            25         25
  Lines          1411       1411
  Methods           0          0
  Messages          0          0
  Branches        176        176
==========================================
  Hits           1304       1304
  Misses           57         57
  Partials         50         50

Powered by Codecov. Last update 51c99f6...67536d5


[core] Add support of partial update with aggregate function

Purpose

Linked issue: close #2242
Linked issue: close #2248

Tests

API and Format

Documentation

This PR also add support of the first_value aggregation function. And will update the  related doc in a following PR. Please take a look  again. @JingsongLi

Thanks @Aitozi , I will take a review next week.

Can you keep this PR simple? Just support agg for partial-update.
Multiplex things here make me confused.

I've reset the commit to only keep the commits of https://github.com/apache/incubator-paimon/issues/2242

please keep first_value

got it. first_value pr will be submitted seperately

I took a quick look at it, I think the logic is correct now.
But I still have some concerns about the codes abstraction, now everything is rely on Agg function. What I see both partial-update and agg become more complicated.

now everything is rely on Agg function

Thanks for your comments, I think the previous behavior of the partial-update  have two behavior:

in sequence group.  it means a lastValue agg
not in sequence group. it means a last_not_null agg

So a unified solution with fieldAggregators looks more consolidated.
But, it will brings some more function call than before, do you care about this ?

I think we can have some concept first:

User only need to use both sequenceGroup and agg.
Sequence field should not have agg func.
In updateWithSequenceGroup:

if (previousSeq == null || currentSeq >= previousSeq) {
     row.setField(i, aggregator == null ? field : aggregator.agg(getField(i), field));
} else if (aggregator != null) {
     row.setField(i, aggregator.agg(field, getField(i)));
}

Something like this.
4. For retractWithSequenceGroup, maybe we should do something similiar.


Mainnet start compile error.

just run mainnet start

Suibase does not require compilation of suibase-daemon anymore (this is new from a commit done today).
Do "~/suibase/update" to try the latest.
(Note: I could not reproduce this probem)


Fixed grammar and clarified explanations

The article contained 11 useful and simple commands, not 11. Added new header for administrative commands.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


scrollableTarget naming problem

props should be lower case
scrollabletarget
React does not recognize the `scrollableTarget` prop on a DOM element. If you intentionally want it to appear in the DOM as a

custom attribute, spell it as lowercase `scrollabletarget` instead. If you accidentally passed it from a parent component, remove it

from the DOM element.

It works fine for me. Check this example Example.
Please provide your code, which is causing this issue.

it got fixed thank you,
the problem was typescript
i used wrong interface
you can close it now


Custom-jhlite should depends on jhlite version that has been used to generate it

See https://github.com/jhipster/jhipster-lite/pull/8760#issuecomment-1913704631

jhlite version in src/main/resources/generator/dependencies/pom.xml is now computed from project version
in ci tests, the jhlite jars of the current branch are installed in local maven repository
jar repackaged by spring-boot-plugin now has its own exec classifier, in order to have both jar: the one for running jhlite, and the one custom-jhlite depends on, as recommended by Spring in situation where module is both runnable and a dependency for other module

Thanks for your great work @murdos !
I think we should wait before merging this. I need to analyze further, because I don't want to break:

the upload to maven central
the upload of the jar with release drafter

As I can see, there is a change related to jar.original and -exec.jar
Currently:
-rw-rw-r--  1 pgrimaud pgrimaud  52M févr.  6 17:38 jhlite-1.3.1-SNAPSHOT.jar
-rw-rw-r--  1 pgrimaud pgrimaud 6,7M févr.  6 17:38 jhlite-1.3.1-SNAPSHOT.jar.original
-rw-rw-r--  1 pgrimaud pgrimaud 4,1M févr.  6 17:38 jhlite-1.3.1-SNAPSHOT-javadoc.jar
-rw-rw-r--  1 pgrimaud pgrimaud 1,8M févr.  6 17:38 jhlite-1.3.1-SNAPSHOT-sources.jar
-rw-rw-r--  1 pgrimaud pgrimaud 780K févr.  6 17:38 jhlite-1.3.1-SNAPSHOT-tests.jar

With your change:
-rw-rw-r--  1 pgrimaud pgrimaud  52M févr.  6 17:41 jhlite-1.3.1-SNAPSHOT-exec.jar
-rw-rw-r--  1 pgrimaud pgrimaud 6,7M févr.  6 17:40 jhlite-1.3.1-SNAPSHOT.jar
-rw-rw-r--  1 pgrimaud pgrimaud 4,1M févr.  6 17:41 jhlite-1.3.1-SNAPSHOT-javadoc.jar
-rw-rw-r--  1 pgrimaud pgrimaud 1,8M févr.  6 17:41 jhlite-1.3.1-SNAPSHOT-sources.jar
-rw-rw-r--  1 pgrimaud pgrimaud 779K févr.  6 17:41 jhlite-1.3.1-SNAPSHOT-tests.jar

As I can see, there is a change related to jar.original and -exec.jar

Indeed. Let me summarize:
Before this PR
Artifacts were different between release artifacts and snapshot ones:
Release artifacts

jhlite-1.3.1.jar <-- small jar (circa 7Mb) without dependencies, the one uploaded to maven central and use as a dependency by custom-jhlite

Snapshost artifacts

jhlite-1.3.1-SNAPSHOT.jar <-- repackaged jar (circa 52Mb) that can only by started with jar -jar but can't be used as a dependency by custom-jhlite
jhlite-1.3.1-SNAPSHOT.jar.original <-- small jar that was backup-ed by spring-boot-plugin

As you can see this is a bit confusing since artifacts have different function depending on the release status.
With this PR
In case like this one where the maven module represents an application that can be run AND a dependency, Spring recommends to use a custom classifier:

jhlite-<VERSION>.jar <-- small jar that can be used as dependency
jhlite-<VERSION>-exec.jar <-- repackaged jar with dependency that will be used to launch application

where VERSION is either a snapshot or a release version.
And I made changes to start.sh script and Dockerfile to use the jhlite-<VERSION>-exec.jar for starting application.

Oh ok, understood
Last thing to change is here: https://github.com/jhipster/jhipster-lite/blob/main/.github/workflows/release.yml#L35
To do:

remove the small jar
rename the exec jar to normal name without exec
so this one will be uploaded

Last thing to change is here: https://github.com/jhipster/jhipster-lite/blob/main/.github/workflows/release.yml#L35

Good catch, I totally forgot this part!
Should be fixed now :)

Thanks a lot @murdos !

@pascalgrimaud Bounty claimed: https://opencollective.com/generator-jhipster/expenses/199152

@murdos : approved


template elements have an empty innerHTML

it looks like template elements have an innerHTML of an empty string

template.content.toString() also gives an empty string, but `template.toString() shows the content just fine

replaceChildren looks like the issue, but a quick glance of the source code reveals no obvious mistakes

my temporary fix was to rewrite the getter on template elements
get innerHTML() {
  const {unescape} = require('html-escaper');
  return unescape(this.childNodes.join(''));
  //return this.content.toString();
}```

you set template.innerHTML and you use the template.content, which is what has been tested.
what doesn't work, exactly?

I figured it was too simple to require a reduced test case, but here you go
const { parseHTML } = require("linkedom");
const test = parseHTML("<template>
foo

bar
</template>");
const template = test.document.querySelector("template");
console.log(template.content.toString()); // empty string
console.log(template.innerHTML); // empty string

I figured it was too simple to require a reduced test case, but here you go

it's never the case, as there might be some obvious thing you are doing it wrong, but it takes nothing for me to reproduce the issue you are having so, thanks for the example, I'll have a look, although I'm after much bigger refactoring so this might help me covering such refactoring.

this is a very ambitious project you're taking on

btw, I can confirm the bug and it will be solved with the next release/minor update

@MathGeniusJodie please give latest a try and let me know if you find other issues, thanks 👋

I've got a pretty big ssr project I'm working on, I'll find bugs fast


Wrong highlighting in

It seems to me that in some cases, the language of a script tag is incorrectly assumed to be javascript although the type attribute explicitly defines it as something else.
The case at hand is:
``` html
<!DOCTYPE html>
<html>
<body>
<script type="text/x-handlebars">
  <!-- Handlebars body highlighted as javascript -->
</script>
</body>
</html>
```

The html output generated from the script tag above has class="javascript" which results in incorrect highlighting (handlebars template highlighted as javascript code).
I think the type attribute should be taken into consideration and the body of the script tag highlighted as such.

Maybe we should use auto highlighting for <script> tag content.

If that means that the body of the


How do we publicly show our model in the library?

We created a model - Aurora, which is a fine-tuned Mixtral-8X7B model with bilingual (chinese and english) dialog. But we can't search for it in the library.

I got same issue, not sure how to add library into library list.
For personal uploaded library, the full name of the model is "/<model_name>"

This search box is buggy, please don't use it!


[Test-operator] Fix detection of failures

With the introduction of the the tobiko workflows there might be more than one pod spawned by the test-operator to execute tobiko tests. This patch makes sure that we detect failures of all pods. Previously, the role was always checking status of only one pod.
As a pull request owner and reviewers, I checked that:

[ ] Appropriate testing is done and actually running
[ ] Appropriate documentation exists and/or is up-to-date:

[ ] README in the role
[ ] Content of the docs/source is reflecting the changes

Testing here -> https://github.com/openstack-k8s-operators/test-operator/pull/58

/retest


Notifications override each other

You can currently display one notification at a time due to new notifications overriding previous notifications

Fixed #5


chore(main): release faro-shop 0.29.0

:robot: I have created a release beep boop
0.29.0 (2024-07-19)
Features

Bump app to 0.34.0 (#593) (4c50b2a)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

faro-shop-0.29.0
:sunflower:


Protocol error: Connection closed. Most likely the page has been closed.

🐛 Bug Report
when page crashed, cause teardown failed. like this:
yarn run v1.22.4
$ jest
  console.error node_modules/jest-jasmine2/build/jasmine/Env.js:248
    Unhandled error

  console.error node_modules/jest-jasmine2/build/jasmine/Env.js:249
    Error: Page crashed!
        at Page._onTargetCrashed (/mnt/d/Project/jest-page-closed/node_modules/puppeteer/lib/Page.js:213:24)
        at CDPSession.<anonymous> (/mnt/d/Project/jest-page-closed/node_modules/puppeteer/lib/Page.js:122:56)
        at CDPSession.emit (events.js:311:20)
        at CDPSession._onMessage (/mnt/d/Project/jest-page-closed/node_modules/puppeteer/lib/Connection.js:200:12)
        at Connection._onMessage (/mnt/d/Project/jest-page-closed/node_modules/puppeteer/lib/Connection.js:112:17)
        at WebSocket.<anonymous> (/mnt/d/Project/jest-page-closed/node_modules/puppeteer/lib/WebSocketTransport.js:44:24)
        at WebSocket.onMessage (/mnt/d/Project/jest-page-closed/node_modules/ws/lib/event-target.js:120:16)
        at WebSocket.emit (events.js:311:20)
        at Receiver.receiverOnMessage (/mnt/d/Project/jest-page-closed/node_modules/ws/lib/websocket.js:789:20)
        at Receiver.emit (events.js:311:20)

 FAIL  ./demo.spec.ts
  ● Test suite failed to run

    Protocol error: Connection closed. Most likely the page has been closed.

      at assert (node_modules/puppeteer/lib/helper.js:283:11)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        32.445s
Ran all test suites.
Jest did not exit one second after the test run has completed.

This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

To Reproduce

In WSL page.goto seems always crashed. When I run the reproduce repo in git-bash, it is Ok.

Clone repo below.
Install dependencies.
In WSL run yarn test.
Expected behavior
expect throw a Page Crashed error, not teardown  throw Protocol error: Connection closed.
I think that should check whether page is closed and browser is conected, before close page and disconnect browser,
Link to repl or repo (highly encouraged)
https://github.com/yidafu/jest-page-crashed-reproduce-repo
Run npx envinfo --system --binaries --npmPackages expect-puppeteer,jest-dev-server,jest-environment-puppeteer,jest-puppeteer,spawnd --markdown --clipboard
Paste the results here:
## System:
 - OS: Linux 4.4 Ubuntu 18.04.4 LTS (Bionic Beaver)
 - CPU: (4) x64 Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
 - Memory: 6.17 GB / 15.87 GB
 - Container: Yes
 - Shell: 4.4.20 - /bin/bash
## Binaries:
 - Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
 - Yarn: 1.22.4 - ~/.nvm/versions/node/v12.16.1/bin/yarn
 - npm: 6.14.3 - ~/.nvm/versions/node/v12.16.1/bin/npm
## npmPackages:
 - expect-puppeteer: ^4.4.0 => 4.4.0
 - jest-puppeteer: ^4.4.0 => 4.4.0

similar issue:  https://github.com/smooth-code/jest-puppeteer/issues/292

any update on this?

@bogdancss if you want to create a PR that would be very helpful 😁👍

I also have this issue. Any updates?

I close it, let's open a new issue if you experience this problem.


Not Working In Mobile UC Web Browser

Hey,
Material Design Lits is not properly rendering on Mobile Uc Browser.
The Header is not rendering in my site.
Floating is not working.
Can u please help me out this.
Thanks.

What is the "Mobile UC Browser"?
Our official browser support does not cover this browser it seems. So any issues in it would be on developers to work on fixing in their own projects.

Ok..
I mean the "UC Browser" for mobile is not rendering the css properly.
u can download the "UC Browser" here http://www.ucweb.com/ucbrowser/download/ .
Thanks.

That isn't a currently supported browser. I'm not finding any information on the engine it uses to help pin-point things. Looking around though, it appears they tend to use a proxy as well to compress things which can cause issues as well.
Closing out since this is on developers to deal with in their own applications.

Yes i have faced same issue. UC browser does not support materializecss. UC browser are mostly used in India and china, but we website have to develop websites which should run almost all the browsers.

My website also breaks when i open it on UC Browsers. What should i do now ?


action: run releases partially with GH actions

What
Use GitHub actions to release this project.
Why
Jenkins will be decommissioned in the near future, hence there is a need to implement the release outside of Jenkins. BuildKite is the one in charge of running releases. Hence, this proposal will use BK and hide the implementations by facilitating the release process through GH actions.
### Issues
Requires https://github.com/elastic/apm-pipeline-library/pull/2033

@LikeTheSalad and @elastic/observablt-ci , what are your thoughts? This PR will need further changes in terms of passing parameters to the BK GH action, but I'd like to gather your feedback, 🙏

Looks good to me! I like the idea of having the release.sh script in this repo since it could make things smoother when it comes to update the overall CD process


Hi, could you please confirm if this problem still exists with the latest versions on stable or master?

          Hi, could you please confirm if this problem still exists with the latest versions on stable or master?

Thanks a lot
Originally posted by @escamoteur in https://github.com/flutter/flutter/issues/29366#issuecomment-534593243

@misbahazmi, do not file issues with comments from old issues.
Closing from here as there's nothing to do in this issue.

What's the sense in this? Am 28. Okt. 2024, 13:17 +0000 schrieb Mohammad Misbah @.>:
…
Hi, could you please confirm if this problem still exists with the latest versions on stable or master? Thanks a lot Originally posted by @escamoteur in #29366 (comment) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

Please refer this:  https://github.com/flutter/flutter/issues/29366


Chikita Isaac

Please help us by filling out the text below. All answers are optional
New Meetup
Where
The location you are running things in
What
A short description of the event.

[x] Learners Group
[x] Meetup with talks
[x] Conference/Camp

Links: add links, e.g. a meetup page, here
When
Insert time and date here.

[ ] I'd like the event to be on the public calendar
[x] It's a repeating event, I would like to have access to the calender to do things on my own

Support

[x] I need coaching or help to get started faster
[x] I would like to be introduced to fellow meetup organizers in my area
[x] I need help promoting

You can promote your event by advertising it on Twitter, Reddit and other channels. We understand that the breadth of this may be overwhelming for organizers and would offer to advertise the event for you. If you already have an active Twitter account and/or regularly announce your meetup through other channels you might not need this option.

[x] I need additional help promoting my event

CoC
The Rust project uses a Code of Conduct and we generally recommend you to as well. We also give advice on motivations and which one could be fitting for your project.

[x] We use a Code of Conduct
[x] We need a recommendation for one

Contact details

[x] I filled out the form at https://docs.google.com/forms/d/e/1FAIpQLSf52YXGhqBaHtCXtVna4iHYMK7IQaTqUW6V-ztsZC8C2TBInQ/viewform and would like you to contact me with news.

Hey!
Unfortunately we currently don't have much capacity within the community team, and this form wasn't used in a long while.
Is there something specific you like our help with?


Add local address autodetection on swarm init

- What I did
Added local address auto detection during swarm init when --advertise-addr is a non local address.
It is the same best-effort auto detection logic which is being used when advertise address is not specified.
- How to verify it
Form a cluster on AWS with
swarm init --advertise-addr <this VM public IP> and
swarm join ... --advertise-addr <this VM public IP>
Create a service over an encrypted overlay network and make sure tasks can talk to other nodes' tasks. Run a container on the attachable network and make sure it can access the service.
Fixes #27647
- A picture of a cute animal (not mandatory but encouraged)

Nice! Thanks for working on this.

ping @aboch @mrjana @mavenugo

@aaronlehmann Changed to only set the local address. Tested it on aws. PTAL when you get a chance.

LGTM

LGTM
@aboch is it possible to write a integration-test for this ?

@mavenugo It is a bit tricky, because in order to test this scenario I need traffic to flow via two docker hosts (whatever their abstraction is in integ framework) with 1 to 1 NAT between their internal address and external address. So that I can create a 2 tasks service or attach two containers so that the ipsec tunnels are programmed, then finally run traffic among containers.
I would prefer this functionality to go in in time for 1.13 and investigate later if/how a meaningful test for this can be done.

@aboch okay. Is it possible to add a test without checking for the actual data-path ? I mean, we could do docker swarm init --advertise-addr={ext-ip} and it must succeed without the need for --listen-addr purely from an UX standpoint at the minimum ?
(I dont think there is any API / UX to check for the chosen --listen-addr :( )...

@mavenugo Oh, I see, just to test the swarm init go through. That should be possible. Let me take a look.

@mavenugo Added the test. Verified it does not pass on master. Thanks.

When I run the integ test locally it works, it is able to detect a system address.
But it fails on jenkins:
19:21:32 FAIL: docker_cli_swarm_test.go:89: DockerSwarmSuite.TestSwarmInitExtAdvAddress
19:21:32
19:21:32 [d1e047f1f3cf9] waiting for daemon to start
19:21:32 [d1e047f1f3cf9] daemon started
19:21:32 docker_cli_swarm_test.go:93:
19:21:32     c.Assert(err, checker.IsNil, check.Commentf("out: %v", out))
19:21:32 ... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc420569e00), Stderr:[]uint8(nil)} ("exit status 1")
19:21:32 ... out: Error response from daemon: must specify a listening address because the address to advertise is not recognized as a system address, and a system's IP address to use could not be uniquely identified

It looks like a leaked interface from a previous test is causing this (thanks @tonistiigi for leading me to the logs):
time="2016-11-10T19:19:16.821920630Z" level=debug msg="form data: {\"AdvertiseAddr\":\"<IP_ADDRESS>\",\"AutoLockManagers\":false,\"ForceNewCluster\":false,\"ListenAddr\":\"<IP_ADDRESS>:2377\",\"Spec\":{\"CAConfig\":{},\"Dispatcher\":{},\"EncryptionConfig\":{\"AutoLockManagers\":false},\"Orchestration\":{},\"Raft\":{\"ElectionTick\":0,\"HeartbeatTick\":0},\"TaskDefaults\":{}}}"
time="2016-11-10T19:19:16.822767149Z" level=warning msg="Could not find a local address: could not choose an IP address to advertise since this system has multiple addresses on different interfaces (<IP_ADDRESS> on eth0 and <IP_ADDRESS> on br-8798ff8194c8)"
time="2016-11-10T19:19:16.822787214Z" level=error msg="Error initializing swarm: must specify a listening address because the address to advertise is not recognized as a system address, and a system's IP address to use could not be uniquely identified"
time="2016-11-10T19:19:16.822798134Z" level=error msg="Handler for POST /v1.25/swarm/init returned error: must specify a listening address because the address to advertise is not recognized as a system address, and a system's IP address to use could not be uniquely identified"

Given the test is not really adding much, I am suggesting to remove it for now.
I will add it later once I find the test which is not removing the bridge interface.

@aboch yes. agreed. pls do so.


SSL is broken after upgrade to 1.5.1

After upgrading deis from 1.4.1 to 1.5.1, which introduced application-level certificates (http://docs.deis.io/en/latest/using_deis/app-ssl/), my previous wildcard certificates (http://docs.deis.io/en/latest/managing_deis/ssl-endpoints/#router-ssl) no longer work. Deployed application work via http, but trying to access them via https always give 404. According to deis-router logs, it tries to route all https requests, whatever subdomain they are for, to deis-controller (in my case <IP_ADDRESS>:8000), like:
Apr 13 18:15:13 staging-coreos-2 sh[5425]: [INFO] - [13/Apr/2015:18:15:13 +0000] - <IP_ADDRESS> - - - 301 - "HEAD / HTTP/1.1" - 183 - "-" - "curl/7.41.0" - "staging.example.com" - <IP_ADDRESS>:49159 - staging.example.com - 0.000 - 0.000
Apr 13 18:15:23 staging-coreos-2 sh[5425]: [INFO] - [13/Apr/2015:18:15:23 +0000] - <IP_ADDRESS> - - - 404 - "HEAD / HTTP/1.1" - 214 - "-" - "curl/7.41.0" - "~^deis\x5C.(?<domain>.+)$" - <IP_ADDRESS>:8000 - staging.example.com - 0.003 - 0.003

First request is http, seconds is https. Obviously staging.example.com doesn't match ^deis wildcard, but this upstream is chosen, probably because it is first in nginx.conf.

Looks like the problem is https://github.com/deis/deis/blob/master/router/image/templates/nginx.conf#L161-L163
Does it mean that I no longer can use wildcard certificate for custom domains?

What do you guys think about following solutions for custom domains:

If sslKey is set and there's no custom certificate for the domain, enable platform certificate.
If custom certificate contains asterisk, remove it and match against domain, so not only exact matches would work, but wildcards as well.

This is related to #3441 Application SSL does not support SAN certificates
I suggest you just create a custom router for now.
Just replace these lines: router/image/templates/nginx.conf#L158-L169 with  include deis.conf; and you should be good to go. That's what I did.

@Blystad Thank you, plan in #3441 sounds great to me.

@bacongobbler This definitely sounds like a regression. If users use a router-level wildcard certificate, that should apply to all domains as it did before. We'll need to address this and consider #3441 as a potential solution.

This definitely sounds like a regression. If users use a router-level wildcard certificate, that should apply to all domains as it did before.

That should be unchanged, but if it isn't then yes it's a regression. I specifically called that out in the docs, so if it isn't working then it's definitely a regression

Note
deis certs is only useful for custom domains. Default application domains are SSL-enabled already and can be accessed simply by using https, e.g. https://foo.deisapp.com (provided that you have installed your wildcard certificate on the routers or on the load balancer).

That should be unchanged, but if it isn't then yes it's a regression. I specifically called that out in the docs, too

Look at the code @Blystad called out:

Just replace these lines: router/image/templates/nginx.conf#L158-L169 with include deis.conf; and you should be good to go. That's what I did.

Not including deis.conf at all for app domains seems like the culprit.

@ineu @Blystad Would you mind testing out the proposed solution in #3519? You can upgrade your routers by:
$ deisctl config set router image=deisci/router:jenkins-test-ec2-580
$ deisctl restart router@*

@carmstrong Works for me, thank you.


Add opentracing context propagator

https://github.com/uber/cadence-java-client/pull/478

Since opentracing is now part of opentelemetry, it would be great if you could check that the new context propagator will work with opentelemetry as well.

This can be closed. It's addressed in https://github.com/temporalio/sdk-java/pull/418


use scenarios for punctuators

currently, a switch statement is used for punctuators. while this works, it's still better to use scenarios to show scenarist at play :)

done in #3


Protocol versioning

What is the goal of this PR?
We use a new protocol API to perform a "connection open". This API does server-side protocol version compatibility checks, and replaces our previous need to get all databases to check that the connection is available.
This API is called transparently during the construction of both the Core and Cluster clients.
What are the changes implemented in this PR?

Refactor Stubs to call connectionOpen in their constructors
Throw a useful message if the server returns an unimplemented error

@alexjpwalker  maybe you can do a post-review, I will merge it for now to proceed with release


Replace GameObject.SendMessage("Method") with event delegates

Pull request for issue https://github.com/Microsoft/HoloToolkit-Unity/issues/224
Many experienced Unity developers would probably tell you not use GameObject.SendMessage("String"); because it's slow (under the hood it uses reflection), hard to debug, and it lacks direct symbol references in the editor which makes it prone to spelling errors because it's a string and not a symbol. This can also make it difficult to find everywhere the method referenced can be called and could potentially increase the amount of spaghetti code.  It may be worth while to see this updated to utilize a delegate/Event call instead.
TL;DR
This will make the code easier to follow in the editor, easier to debug, and will increase performance.
Some arguments for using a delegate vs SendMessage:

SendMessage and delegates are used for similar purposes, but they work entirely differently. Delegates/Events behave exactly like they do in any other .Net program. SendMessage() is called much like Unity calls other messages like Update(). Unity reflects over all the code on the game object to see if it can invoke any messages.
As far as performance. Delegates are several times faster than SendMessage. In the order of performance:

(Least) Direct Method Call ==> Delegate/Event ==> Update() ==> SendMessage (Most Expensive)

As far as usage, SendMessage is like a very broad direct method call. The general paradigm is that one script specifically wants to send a message to a specific object. We're just not sure how many times is can respond or if it can respond at all. We know the intended receiver, we just don't know if it can receive the message.
With events, I usually follow the idea that the event owner doesn't know who or how many objects might respond. We are simply telling the world that something happened without too much knowledge of who will use this information.

Changes to the following classes:
GestureManager.cs

[x] Change System.Actions to delegate events to fix delegate subtraction issues in GestureManipulator.cs
[x] Add OnSelect(GameObject) event
[x] Add explicit private modifiers to Unity Methods

GestureManipulator.cs

[x] Remove redundant using HoloToolkit.Unity reference
[x] Ensure we're checking GesureManager instance is null
[x] Add explicit private modifiers to Unity Methods

GazeManager.cs

[x] Remote unused using reference
[x] Add delegate events for OnGazeEnter
[x] Add delegate events for OnGazeExit
[x] Ensure StabilizationPlaneModifier instance is null

TapToPlace.cs

[x] Update to work with new design pattern

GestureResponder.cs

[x] Update to work with new design pattern

SelectedObjectMessageSender.cs

[x] Remove File

SelectedObjectMessageReciever.cs

[x] Rename file to ChangeColorOnFocus
[x] Update to work with new design pattern

FocusedObjectMessageSender.cs

[x] Remove File

FocusedObjectMessageReciever.cs

[x] Rename file
[x] Update to work with new design pattern

OnSelectEvent.cs

[x] Remove File (replaced by Intractable.cs)

OnGazeEnterEvent.cs

[x] Remove File (replaced by Intractable.cs)

OnGazeLeaveEvent.cs

[x] Remove File (replaced by Intractable.cs)

Intractable.cs

[x] Add file Intractable.cs

KeywordManager.cs

[x] Update to work with new design pattern

ScaleObjectMessageReciever.cs

[x] Update to work with new design pattern
[x] Renamed to ScaleFocusedObject.cs

SphereKeywords.cs

[x] Update to work with new design pattern

Updates to the following scenes:
SelectedObjectKeywords.unity
FocustedObjectKeywords.unity
GazeEvents.unity
Updates to the following Prefabs:
SelectedObjectKeywordManager.prefab
FocusedObjectKeywordManager.prefab

Hi @HodgsonSDAS, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Kind of a huge change @HodgsonSDAS - can we break this up by feature area and make sure all the test scenes pass tests of functionality on both sides of the change?

@jwittner Of course! I fully expected this.  But I wasn't sure exactly which features we wanted to break this up into.  Any suggestions?
I also fully expect a through review period.

Thanks @riverar for your feedback!

I'd really prefer if we layered support for these events on top of the existing SendMessage functionality. This change as it stands pretty much breaks all my apps and would introduce a large swath of required changes if I wanted to update to the latest HTK post it's inclusion.

I'd really prefer if we layered support for these events on top of the existing SendMessage functionality. This change as it stands pretty much breaks all my apps and would introduce a large swath of required changes if I wanted to update to the latest HTK post it's inclusion.

I understand, and I've addressed these concerns in the comments of issue https://github.com/Microsoft/HoloToolkit-Unity/issues/224

If you guys want to keep SendMessage and sunset it, we'll need a clear deprecation plan and mark the methods as such. I prefer we gut it now and inconvenience the small user base. There are only 77 apps in the Store to date, most of which aren't real apps.

In fact, if we can remove SendMessage from the Test scenes and only keep it around just for people we are still using it, I think this might be the easiest way to ensure we don't step on toes, while keeping the examples and test scenes clean.

This is a comical case of Bikeshedding.
There are some real issues that need to be dealt with, and here we are doing peephole optimization.

@riverar  @HodgsonSDAS  The issue with simply gutting SendMessage is that there's no tool time way to tell that something has changed. Objects will simply stop getting their message method called and functionality will stop working, but there will be no warning or any indication of why this has happened. I feel we must go through a deprecation phase.
There may be only 77 apps on the store, but we have no way to measure the number of apps currently in development that may be leveraging the HTK right? I have zero apps on the marketplace, but at least four in development that leverage the HTK and this functionality.

@jwittner I agree we need a depreciation path. I've already addressed this issue in the GestureManager by adding:
        private void OnSelect()
         {
             ThrowDeprecatedWarning();
         }

         private void OnGazeLeave()
         {
             ThrowDeprecatedWarning();
         }

         private void OnGazeEnter()
         {
             ThrowDeprecatedWarning();
         }

         private void ThrowDeprecatedWarning()
         {
             // For more information see: TODO:Link to HoloToolkit Documentation.
             Debug.LogWarning("Using SendMessage is not recommended in the HoloToolkit and has been replaced by delegate events. See Documentation");
         }

@HodgsonSDAS Cool! A little confused on those changes - it looks like the functionality would still be broken. To deprecate we should print the warning, but still issue the messages, i.e. call SendMessage.

@jwittner agreed, and it indeed does, in fact, call SendMessage.

@darax Another good link

Emblematic example of these bad choices is the communication system built around SendMessage and BroadcastMessage. If you use them, you should just stop already!
In fact SendMessage and BroadcastMessage are so wrong mostly because they heavily rely on reflection to find the functions to call. This of course has a given impact on performance, but performance is not the issue here, the issue is instead related to the quality of the resulting code.
What can be so bad about it? First (and foremost) the use of  a string to recognize a function is way worse than using a string to recognize an Event. Just think about it: what happens if someone in the team decides to refactor the code where the calling function is defined and decides to rename the function or delete it?
I tell you what happens: the compiler will not warn the poor programmer of the mistake is doing and even worse, the code will just run as nothing happened. When the error will be found, it could be already too late.
Even worse is the fact that the calling function can be declared as private since the system uses reflection. You know what I usually do when I find a private function that is not used inside the declaring class? I just delete it, because the code is telling me: this function cannot be used outside this class and I am not using it, so why keep useless code?

Can we just cut SendMessage out already? There's not enough usage out there to care about back compat. I'm surprised to still see active discussion on what is clearly inferior.

Moved to https://github.com/Microsoft/HoloToolkit-Unity/pull/244


[BEAM-1343] Fix HDFSFileSource’s split size estimate

This is a port of this fix:
https://github.com/GoogleCloudPlatform/DataflowJavaSDK/pull/534
HDFSFileSource incorrectly calculates estimated byte size. The source can represent either a top level source or a split from splitIntoBundles. However, getEstimatedSizeBytes always calculates the size of the entire top level source.
This PR detects if the source represents a split and returns its length.

R: @jkff

LGTM

(Sorry, I should have seen this and reviewed it -- I reviewed the DataflowJavaSDK version.)
Thanks @igorbernstein2 for porting it forward. I really appreciate it.
Merging now.


[Bug] Point Blank more not accounted for

Doesn't seem to work for neither the keystone nor the gem. Using Barrage, Slower Proj, Pierce, Faster Attacks, Physical Projectile Attack Damage & Point Blank in a link & have Enemy is at Close Range  checked in configuration.

Physical Projectile Attack Damage more modifier isn't accounted for either it seems.

Duplicates #73
It's not a bug as such, but a lack of support for that keystone.


[Web] Copying Image to Clipboard working on MacOS and Linux but Black screen on Windows

Hi,
I figured out how to get Images to copy successfully to the Clipboard from Flutter Web using some starting code I found in the rich_clipboard package (this package does not support images and the code below doesn't use that package). It turns out for some reason though the code below works in MacOS and Linux but in Windows Chrome / Edge / Opera it comes out as a black screen for some reason.
Have you any insight why there is a difference between the client platforms and is it a Flutter framework bug?
*The pngBytes appears to be the same on all platforms so it appears to be on the transform / write where things are going wrong.

Flutter Doctor
[√] Flutter (Channel stable, 3.0.1, on Microsoft Windows [Version 10.0.22598.1], locale en-IE)
• Flutter version 3.0.1 at c:\code\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision fb57da5f94 (3 weeks ago), 2022-05-19 15:50:29 -0700
• Engine revision caaafc5604
• Dart version 2.17.1
• DevTools version 2.12.2
[X] Android toolchain - develop for Android devices
X Unable to locate Android SDK.
Install Android Studio from: https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK components.
(or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
If the Android SDK has been installed to a custom location, please use
flutter config --android-sdk to update to that location.
[√] Chrome - develop for the web
• CHROME_EXECUTABLE = c:\code\rocketx\chromecorsarm.bat
[X] Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
[!] 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/windows#android-setup for detailed instructions).
[√] VS Code (version 1.68.0)
• VS Code at C:\Users\Rober\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.42.0
[√] Connected device (3 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22598.1]
• Chrome (web)      • chrome  • web-javascript • Google Chrome 102.0.5005.63
• Edge (web)        • edge    • web-javascript • Microsoft Edge 102.0.1245.33
[√] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 3 categories.

Sample code
import 'dart:html';
import 'package:js/js.dart';
import 'package:js/js_util.dart';
import 'package:flutter/material.dart';
import 'package:qr_flutter/qr_flutter.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(home: const MyHomePage());
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  var image;

  void _createandcopyQRCode() async {
    final image = await QrPainter(
      data: "https://www.slashdot.org",
      version: QrVersions.auto,
      errorCorrectionLevel: QrErrorCorrectLevel.H,
    ).toImageData(400);

    var pngBytes = image!.buffer.asUint8List();

    final clipboard = window.navigator.clipboard as _Clipboard?;
    if (clipboard == null) {
      return;
    }

//DOES not work on Firefox due to limitations in Clipboard API

    final dataMap = <dynamic, dynamic>{
      'image/png': Blob([pngBytes], 'image/png')
    };

    var out = jsify(dataMap);
    final item = _ClipboardItem(out);
    await clipboard.write([item]);

    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text('You have copied the QR Code this many times:'),
            Text('$_counter', style: Theme.of(context).textTheme.headline4),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _createandcopyQRCode,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

@JS('ClipboardItem')
@staticInterop
class _ClipboardItem {
  external _ClipboardItem(dynamic args);
}

@JS('Clipboard')
@staticInterop
class _Clipboard {}

extension _ClipboardImpl on _Clipboard {
  @JS('write')
  external dynamic _write(List<_ClipboardItem> items);
  Future<void> write(List<_ClipboardItem> items) => promiseToFuture(_write(items));
}

Hi @zambetpentru
It looks like you are approaching Copying Image to Clipboard functionality using 3rd party plugins rather than to Flutter itself.  For example, js dependency issue should be opened in the dedicated dart-lang/sdk repository and the same to qr_flutter.
FYI: There is in-progressing issue #32045 related to this issue (official supporting image for clipboard in Flutter).
So, if you still want to handle the issue by yourself approach, please provide a completed and minimal reproducible code sample that represents the problem (without 3rd party plugins). Otherwise, I will close this issue as a duplicate of #32045.
Thanks!

Hi @huycozy, okay cheers let me come back to you with an example without the external packages.

Hi @huycozy, I couldn't easily extract the js package pieces as it depends on internal dart packages so I took your advice and have raised it in the dart-lang/sdk repo here: https://github.com/dart-lang/sdk/issues/49299


add blosc to run dependencies

not sure bumping build number is the right thing to do, since the functionality using blosc is not in there...

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


[BUGFIX] fix final linear layer

So I did a big woops and, since the final linear layer when weight tying was turned off didn't inherit from torch.nn.module, its parameters weren't even getting registered :facepalm:
This should fix that.

LGTM, what problems did not registering the parameters cause?

didn't actually see any problems caused by it but it meant we failed some unit tests lol - better safe than sorry I guess


Problem in point cloud positioning with the Introduction to ICP

Hi,
I am following the introduction to ICP tutorial. After running pmicp with the default config file (found in examples/icp_tutorial/icp_tutorial_cfg.yaml), I noticed (in Paraview) that my reference point cloud (cloud_0.vtk) is not on the same coordinates as the reference point cloud generated by the algorithm (vissteps-reference). Attached a screenshot of the problem.
Can you please help me understand the problem?

Great question. Quick answer, it's normal.
The output given by the vtk inspector (visstep) is an internal view of what's going on inside the iterative process. We translate both point clouds to have the origin of the reference point cloud to its center of masse. We do that because we solve the rotation error around the origin and some point clouds (terrestrial survey, for example) use global coordinates with the origin being excessively far away. We do the transformation inverse before outputting the final transformation.
In your case, this means that cloud*.vtk are coherent together and visstep*.vtk are in a different frame but coherent together.

I get it. Thank you for your help.


Feature Request: Reset Button + Handposes

Hi there. Thanks a lot for this great extension! Two things that would come in really handy ^^

Reset Button: ok I see restore last scene is like the reset to the original, if no other scene is loaded :)

Hands are not easy to configure with this model (at least not for beginners). It would really help and safe some time, to have hand gestures like "fist" "stretched out hands" some of the most common hand signs be "loadable" and be able to adjust from there.

Thanks again, maybe sometime it can be implemented :)
Greets

Hello, I think "restore last scene", restores the previous editing scene, avoiding accidentally closing the webpage and causing data loss.
I also consider collecting hand gestures from users, but you know it is just the web page not any server work in the background.


Reinstate -std=gnu99 flag

In 913e2f3b9a618d169eb56f645b2b2aa03fd9765a -std=gnu99 was removed from the Makefiles. Please put it back. This code is not compatible with the default gnu89 mode of older compilers:
error: ‘for’ loop initial declaration used outside C99 mode

The AC_PROG_CC_C99 macro in configure.ac is supposed to do that automatically. The documentation states:

— Macro: AC_PROG_CC_C99
If the C compiler is not in C99 mode by default, try to add an option to output variable CC to make it so. This macro tries various options that select C99 on some system or another. It considers the compiler to be in C99 mode if it handles _Bool, flexible arrays, inline, long long int, mixed code and declarations, named initialization of structs, restrict, varargs macros, variable declarations in for loops and variable length arrays.

Can you provide more details about the compiler and autoconf version?


Support production deployment of Lyra

Description
#266 removes the legacy build steps for minifying CSS and JS. These processes should be added back in to the build, preferably integrated with the webpack build & webpack dev server, in such a way that webpack -p produces a production build.
Tasks

[ ] Research whether Webpack can be configured to use .min.js extensions on --production-mode build, to allow files to live side-by-side
[ ] Research how to integrate sass build into webpack (possibly w/ HMR integration)
[ ] Coordinate with @arvind and @deathbearbrown to identify how a "production" build can be integrated into a gh-pages branch deployment

Available thanks to #363 (and subsequent bug fixes). Thanks @kadamwhite!


chore: check format with actions

The prettifier bot can't handle 2.0. @sw-yx Do you feel strongly about the PR comments the bot used to make?

no, i don't.

would you like me to uninstall Prettifier bot?

Yep. Doesn't add anything other than a comment as far as I can tell and blocks #208.


Anolis supported multiple references linked by a single id

Prior to the move to Bikeshed, WHATWG cross-references were managed in a separate repo, which allowed a single reference ID to point to multiple actual references.
For example, here's the reference entry for the ID "HTTP":
https://github.com/whatwg/xref/blob/c275b8f3c9d1ae654b42c3db5ad2c723e77c8e8e/references.json#L339-L369
There are other examples in the same file.
It doesn't appear that SpecRef supports this concept, and the ID "HTTP11" there is an alias to just RFC 7230:
https://github.com/tobie/specref/blob/a6e795ff6de993110ffb4f34227f64ac62c488a9/refs/biblio.json#L1512-L1514

I think it's fine to wontfix this. We can convert those cases to multiple independent references instead. (That's what we've done in Fetch.)

That works for me. ^_^


docs: ✏ add code of conduct

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support providing your own webdriver instance, parallell instances break

It's unclear today how the bootstrap method sets up webdrivers, it would be good to be able to provide your own webdriver instance in many cases (newer drivers, custom drivers, parallelll tests).
We have the following setup:

We have some tests
We run nunit 3 because it supports parallell execution
We use browserstack so all our tests are running towards clean instances

We have a base fixture like this:
    [TestFixture("Edge", "12.0", "Windows", "10", "TestData.json")]
    [TestFixture("IE", "11.0", "Windows", "8.1", "TestData.json")]
    [TestFixture("Chrome", "47.0", "Windows", "8.1", "TestData.json")]
    [TestFixture("Firefox", "43.0", "Windows", "8.1", "TestData.json")]
    [Parallelizable(ParallelScope.Fixtures)]
    public class BaseTestFixture : FluentTest
    {
        public string Browser { get; set; }
        public string BrowserVersion { get; set; }
        public string Os { get; set; }
        public string OsVersion { get; set; }
        public string TestDataPath { get; set; }

        public Dictionary<string, object> Capabilities { get; set; }

        public BaseTestFixture(string browser, string browserVersion, string os, string osVersion, string testDataPath)
        {
            Browser = browser;
            BrowserVersion = browserVersion;
            Os = os;
            OsVersion = osVersion;
            TestDataPath =<EMAIL_ADDRESS>testDataPath);
        }

        [SetUp]
        public void Init()
        {
            ReadTestData();
            Capabilities = GetCapabilitites();

            SeleniumWebDriver.Bootstrap(
                BrowserStack.Uri,
                Capabilities);
            LogCapabilities();

            // Setup settings
            FluentSettings.Current.ExpectIsAssert = true;

            // Navigate to root page to initialize the provider
            I.Open(new Uri(string.Format(TestHelper.BaseUrl, TestData.customer.domain.Value)));

            // Show session state
            LogCookies();
        }

...

I expected each test having it's own driver using this, but it doesn't seem like it since fluentautomaiton is using the TinyIoCContainer.
Would it be possible to have some initialization like this and for fluentautomation to not use any static state sharing between instances?
SeleniumWebDriver.Bootstrap(new MyDriver(Capabilities));

Researching a bit further I checked the bootstrap code and there you seems to be generating new driver instances per browser name (depending on which of the bootstap overloads you use).
It would be good to be able to specify your own identifier to support parallell runs. For example: myContextBasedOnParallellRun could be created from a combination of browser, versions, and os to enable parallell remote runs using nunit.
myContextBasedOnParallellRun = "FF-43-WIN-8"; // build this from the nunit attributes or some other parallell metadata instead of just browser name
container.Register<IWebDriver>((c, f) => new EnhancedRemoteWebDriver(BrowserStack.Uri, desiredCapabilities, defaultCommandTimeout), myContextBasedOnParallellRun);


Fix -Wmissing-template-arg-list-after-template-kw issued by Clang 19

This warning is treated as error by default:
https://releases.llvm.org/19.1.0/tools/clang/docs/DiagnosticsReference.html#wmissing-template-arg-list-after-template-kw
So build breaks for all library consumers even when -Werror, -Wall, etc. are not used.
STR:
$ CXX=clang++-19 CC=clang-19 cmake -B build -DATOMIC_QUEUE_BUILD_TESTS=yes &> /dev/null
$ cmake --build build
[  0%] Built target atomic_queue
[ 50%] Building CXX object src/CMakeFiles/atomic_queue_tests.dir/tests.cc.o
In file included from /tmp/atomic_queue/src/tests.cc:8:
/tmp/atomic_queue/include/atomic_queue/atomic_queue.h:407:31: error: a template argument list is expected after a name prefixed by the template keyword [-Wmissing-template-arg-list-after-template-kw]
  407 |         return Base::template do_pop_any(states_[index], elements_[index]);
      |                               ^
/tmp/atomic_queue/include/atomic_queue/atomic_queue.h:413:24: error: a template argument list is expected after a name prefixed by the template keyword [-Wmissing-template-arg-list-after-template-kw]
  413 |         Base::template do_push_any(std::forward<U>(element), states_[index], elements_[index]);
      |                        ^
/tmp/atomic_queue/include/atomic_queue/atomic_queue.h:538:31: error: a template argument list is expected after a name prefixed by the template keyword [-Wmissing-template-arg-list-after-template-kw]
  538 |         return Base::template do_pop_any(states_[index], elements_[index]);
      |                               ^
/tmp/atomic_queue/include/atomic_queue/atomic_queue.h:544:24: error: a template argument list is expected after a name prefixed by the template keyword [-Wmissing-template-arg-list-after-template-kw]
  544 |         Base::template do_push_any(std::forward<U>(element), states_[index], elements_[index]);
      |                        ^
4 errors generated.

Thank you for your contribution.
For some reason, this piece of code came to my mind yesterday, out of the blue, and a question arose why template was there.


test: clean up the test build script

Signed-off-by: Paul Osborne<EMAIL_ADDRESS>

r? @kamalmarhubi

@homu r+

:pushpin: Commit b8f0535 has been approved by kamalmarhubi

:zap: Test exempted - status


Installing docker 1.5 via curl on Debian Jessie (RC1 or RC2) results in docker daemon not starting after reboot

When I install Docker v1.5 via the curl method "curl -sSL https://get.docker.com/ | sh" as advised at "https://docs.docker.com/installation/debian/#debian-wheezystable-7x-64-bit" for Debian Jessie (RC1 or RC2) rather than for Debian Wheezy, the docker daemon does not automatically start on reboot.
Please fix.
Thanks,
Ken Wolcott
<EMAIL_ADDRESS>

You need to systemctl enable docker, for it to automatically start on boot
On Mon, Apr 6, 2015 at 5:36 PM, Kenneth A. Wolcott<EMAIL_ADDRESS>
wrote:

When I install Docker v1.5 via the curl method "curl -sSL
https://get.docker.com/ | sh" as advised at "
https://docs.docker.com/installation/debian/#debian-wheezystable-7x-64-bit"
for Debian Jessie (RC1 or RC2) rather than for Debian Wheezy, the docker
daemon does not automatically start on reboot.
Please fix.
Thanks,
Ken Wolcott
<EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/12114.

Thank you for the tip but shouldn't that step be performed by the installation of Docker?

ping @moxiegirl we may want to add this to the docs, but users of systemd are mostly used to this, but regardless. You must systemctl enable docker to tell systemd you allow it to automatically be started on reboot

@kwolcott-vendini no it should not, this is a decision the user must make. It's not fair for us to automatically do it, if the user does not want that to happen

I see.  I would think that if someone wanted to install docker that they would want the daemon to be auto-started.  I reluctantly accept this conclusion.

Please do add this to the docs.  So, the docker daemon is automatically started for Ubuntu, but not for Debian.  Seems inconsistent.

@kwolcott-vendini You might want to jump on #12088 which is related to this.  IOW, we do intend to discuss it.