Pub / Sub Publisher: Async publish breaks around 1000 messages

Am unsure if this is a bug (can't find documentation explaining this behavior).
I can send up to 999 pubsub messages and wait for results before continuing, but if I try to send 1000, none of them complete. However, if I run in debug mode, they will complete (because I have a breakpoint in the code allowing more execution time).
It exhibits this failure both in the main thread, or calling Publisher.publish from a thread.

OS type and version
MacOS High Sierra

Python version and virtual environment information python --version
Python 3.6.3

google-cloud-python version pip show google-cloud, pip show google-<service> or pip freeze

google-api-core==0.1.2
google-auth==1.2.1
google-cloud-core==0.28.0
google-cloud-pubsub==0.29.2
google-gax==0.15.16
googleapis-common-protos==1.5.3
grpc-google-iam-v1==0.11.4

Stacktrace if available

None, hanging, no exception.

Steps to reproduce

Publish 1000 messages storing their futures. None of the futures will complete.

Code example
Goal here is to send specified number of messages per second and sleep.

    def publish_function(self):
        # save all futures so we can wait for them to complete
        # Callbacks receive the future as their only argument, as defined in
        # the Future interface.
        def callback(future):
            message_id = future.result()
            self.logger.debug(f"Sent message: {message_id}")

        # The callback is added once you get the future. If you add a callback
        # and the future is already done, it will simply be executed immediately.
        future = self.publisher.publish(self.topic_path, data=self.message)
        print(future)
        future.add_done_callback(callback)
        self.results.append(future)

    def publish(self, total_messages, messages_per_second):
        i = 0
        sleep_time = 1
        if messages_per_second < 1:
            sleep_time = float(sleep_time) / float(messages_per_second)
        logger.debug(f"Sleep time is: {sleep_time}")
        while i < total_messages and not self.exit:
            start = time.time()
            # number of times to send per second
            # if less than one, then the sleep timer handles the wait. We just send one message here
            for j in range(int(math.ceil(messages_per_second))):
                self.publish_function()
                i += 1
                self.next_id()
                # exit inner loop if we hit the total to send
                if i >= total_messages or self.exit:
                    self.stop()
                    break

            # apply result to all futures in self.results. This blocks until the future it's called on completes
            # list forces the map to execute since map returns an iterable

            list(map(futures.Future.result, self.results)) <<<<<<<<<<<--------- ***HANGS HERE***

            end = time.time()
            logger.info(
                f"Took {end - start} to send {messages_per_second} messages in thread {current_thread().getName()}")
            logger.debug(f"If greater than 0 seconds, sleeping for {sleep_time - (end - start)}")
            if sleep_time - (end - start) > 0:
                time.sleep(sleep_time - (end - start))

@anorth2 I'm fairly certain it's a bug. I ran into it yesterday when reproducing a subscriber issue that required a large backlog of published messages. I got as high as 1375 messages through before failure, but not consistently.
Thanks for filing.

@dhermes   Also wanted to ask, are there expected side effects from calling publisher.publish from a thread?
if I use the following code list(set(map(Future.result, running_futures)))
where running_futures is a list of threads each executing publisher.publish,  I get an error from the publisher where   len(message_ids) != len(futures)

@anorth2 To provide a quick answer: I don't know. Since I've started the "hardening" process on the highly concurrent Pub / Sub implementation (i.e. 0.28.x and beyond) I have only worked on the subscriber. But I hope to know more later this week.

I have a reproducible sample that I am debugging here: https://github.com/dhermes/google-cloud-pubsub-performance/tree/master/publish-many

danny, any idea when this will land on pypi?
On Tue, Dec 19, 2017 at 11:16 AM Danny Hermes<EMAIL_ADDRESS>wrote:

Closed #4575
https://github.com/GoogleCloudPlatform/google-cloud-python/issues/4575
via #4616
https://github.com/GoogleCloudPlatform/google-cloud-python/pull/4616.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-python/issues/4575#event-1394461506,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARrMFtjBvZ102E6vwNDirh-BPEOwnjG_ks5tB-FUgaJpZM4Q_cqb
.

--
Kir Titievsky | Product Manager | Google Cloud Pub/Sub
https://cloud.google.com/pubsub/overview

Soon: see #4619

@kir-titievsky TADA :tada: https://pypi.org/project/google-cloud-pubsub/0.30.0/

This is still not working for me, but with a new error:

import time
from google.cloud import pubsub_v1

publisher = pubsub_v1.PublisherClient(batch_settings)
topic_path = publisher.topic_path('XXXX', 'XXX')

for n in range(1000):
    data = u'Message number {}'.format(n)
    def dt(n, t):
        def g(message_id):
            print "%g\t%g\t%g"%(n, time.clock() - t , t)
        return g

    data = data.encode('utf-8')
    publisher.publish(topic_path, data=data).add_done_callback(dt(n, time.clock()))

pip show google-cloud-pubsub
Name: google-cloud-pubsub
Version: 0.30.0
Summary: Python Client for Google Cloud Pub/Sub
Home-page: https://github.com/GoogleCloudPlatform/google-cloud-python
Author: Google Cloud Platform
Author-email<EMAIL_ADDRESS>License: Apache 2.0
Location: /Users/kir/cloud/env/lib/python2.7/site-packages
Requires: psutil, google-auth, google-api-core, grpc-google-iam-v1

Errors (many of these:)

ERROR:root:AuthMetadataPluginCallback "" raised exception!
Traceback (most recent call last):
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/grpc/_plugin_wrapping.py", line 74, in __call__
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/google/auth/transport/grpc.py", line 77, in __call__
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/google/auth/transport/grpc.py", line 65, in _get_authorization_headers
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/google/auth/credentials.py", line 121, in before_request
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/google/oauth2/credentials.py", line 117, in refresh
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/google/oauth2/_client.py", line 191, in refresh_grant
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/google/oauth2/_client.py", line 105, in _token_endpoint_request
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/google/auth/transport/requests.py", line 122, in __call__
  File "/Users/kir/cloud/env/lib/python2.7/site-packages/six.py", line 737, in raise_from
TransportError: HTTPSConnectionPool(host='accounts.google.com', port=443): Max retries exceeded with url: /o/oauth2/token (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 8] nodename nor servname provided, or not known',))

Discussed with @kir-titievsky on Hangouts. Seems to be an intermittent HTTP issue (the error indicates that https://accounts.google.com was unreachable).


contact us page

Creating the contact us page

Hey ,can I work on this issue?

Yes sure, let me assign you

Can you assign this to me?


where's the inference code? or anything else?

Is this some sort of a scam, on kaggle it's listed as number #1  for FER, for multiple datasets, yet from the interest in this GitHub repository it seems useless, & even though the research paper says the source code will be available here, ,there's nothing at all

Hi, we have just uploaded the training notebook. It is recommended to train on your database before evaluating the model for optimal performance.


Android dependency 'androidx.versionedparcelable:versionedparcelable' has different version for the compile (1.0.0-rc01) and runtime (1.0.0) classpath

After upgrading to latest flutter stable release I can't build or run my app. It keeps failing
Steps to Reproduce

Upgrade to latest stable flutter release v1.12.13+hotfix.5
Run flutter run

Target Platform: Linux
Target OS version/browser:
Devices: Both physical and emulator
Logs

flutter_04.log
[  +48 ms] executing: [/home/munene/flutter/] git -c log.showSignature=false log
-n 1 --pretty=format:%H
[  +68 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
--pretty=format:%H
[   +1 ms] 27321ebbad34b0a3fafe99fac037102196d655ff
[        ] executing: [/home/munene/flutter/] git describe --match v*.*.*
--first-parent --long --tags
[  +19 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long
--tags
[   +1 ms] v1.12.13+hotfix.5-0-g27321ebba
[  +14 ms] executing: [/home/munene/flutter/] git rev-parse --abbrev-ref
--symbolic @{u}
[  +19 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/home/munene/flutter/] git ls-remote --get-url origin
[  +18 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +106 ms] executing: [/home/munene/flutter/] git rev-parse --abbrev-ref HEAD
[  +25 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[ +204 ms] executing: /home/munene/Android/Sdk/platform-tools/adb devices -l
[  +17 ms] Exit code 0 from: /home/munene/Android/Sdk/platform-tools/adb devices
-l
[   +1 ms] List of devices attached
           RZ8MA26ZH2E            device usb:1-1.1 product:a50dd model:SM_A505F
           device:a50 transport_id:2
[  +39 ms] /home/munene/Android/Sdk/platform-tools/adb -s RZ8MA26ZH2E shell
getprop
[ +156 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required,
skipping update.
[   +6 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[   +1 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[ +126 ms] Found plugin esys_flutter_share at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/esys_flutter_share-1.0.2
/
[  +78 ms] Found plugin image_picker at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/image_picker-0.6.2+1/
[  +31 ms] Found plugin path_provider at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-1.5.1/
[  +32 ms] Found plugin sqflite at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/sqflite-1.1.6+5/
[  +19 ms] Found plugin url_launcher at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.1/
[   +2 ms] Found plugin url_launcher_macos at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1
/
[   +4 ms] Found plugin url_launcher_web at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.0+1
/
[ +171 ms] Found plugin esys_flutter_share at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/esys_flutter_share-1.0.2
/
[  +21 ms] Found plugin image_picker at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/image_picker-0.6.2+1/
[  +18 ms] Found plugin path_provider at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-1.5.1/
[  +31 ms] Found plugin sqflite at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/sqflite-1.1.6+5/
[   +8 ms] Found plugin url_launcher at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.1/
[   +1 ms] Found plugin url_launcher_macos at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1
/
[   +2 ms] Found plugin url_launcher_web at
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.0+1
/
[ +548 ms] Generating
/home/munene/Projects/Flutter/echo/android/app/src/main/java/io/flutter/plugins/
GeneratedPluginRegistrant.java
[ +111 ms] ro.hardware = exynos9610
[        ] ro.build.characteristics = phone
[ +758 ms] Launching lib/main.dart on SM A505F in debug mode...
[  +37 ms] executing: /home/munene/Android/Sdk/build-tools/29.0.2/aapt dump
xmltree /home/munene/Projects/Flutter/echo/build/app/outputs/apk/app.apk
AndroidManifest.xml
[ +265 ms] Exit code 0 from: /home/munene/Android/Sdk/build-tools/29.0.2/aapt
dump xmltree /home/munene/Projects/Flutter/echo/build/app/outputs/apk/app.apk
AndroidManifest.xml
[   +2 ms] N: android=http://schemas.android.com/apk/res/android
             E: manifest (line=2)
               A: android:versionCode(0x0101021b)=(type 0x10)0x1
               A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
               A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1c
               A: android:compileSdkVersionCodename(0x01010573)="9" (Raw: "9")
               A: package="com.mindle.echo" (Raw: "com.mindle.echo")
               A: platformBuildVersionCode=(type 0x10)0x1
               A: platformBuildVersionName="1.0.0" (Raw: "1.0.0")
               E: uses-sdk (line=7)
                 A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
                 A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1c
               E: uses-permission (line=14)
                 A: android:name(0x01010003)="android.permission.INTERNET" (Raw:
                 "android.permission.INTERNET")
               E: uses-permission (line=22)
                 A:
                 android:name(0x01010003)="android.permission.WRITE_EXTERNAL_STO
                 RAGE" (Raw: "android.permission.WRITE_EXTERNAL_STORAGE")
               E: uses-permission (line=23)
                 A:
                 android:name(0x01010003)="android.permission.READ_EXTERNAL_STOR
                 AGE" (Raw: "android.permission.READ_EXTERNAL_STORAGE")
               E: application (line=25)
                 A: android:label(0x01010001)="echo" (Raw: "echo")
                 A: android:icon(0x01010002)=@0x7f080000
                 A: android:name(0x01010003)="io.flutter.app.FlutterApplication"
                 (Raw: "io.flutter.app.FlutterApplication")
                 A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
                 A:
                 android:appComponentFactory(0x0101057a)="androidx.core.app.Core
                 ComponentFactory" (Raw:
                 "androidx.core.app.CoreComponentFactory")
                 E: activity (line=31)
                   A: android:theme(0x01010000)=@0x7f0a0000
                   A: android:name(0x01010003)="com.mindle.echo.MainActivity"
                   (Raw: "com.mindle.echo.MainActivity")
                   A: android:launchMode(0x0101001d)=(type 0x10)0x1
                   A: android:configChanges(0x0101001f)=(type 0x11)0x400037b4
                   A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
                   A: android:hardwareAccelerated(0x010102d3)=(type
                   0x12)0xffffffff
                   E: meta-data (line=45)
                     A:
                     android:name(0x01010003)="io.flutter.app.android.SplashScre
                     enUntilFirstFrame" (Raw:
                     "io.flutter.app.android.SplashScreenUntilFirstFrame")
                     A: android:value(0x01010024)=(type 0x12)0xffffffff
                   E: intent-filter (line=49)
                     E: action (line=50)
                       A: android:name(0x01010003)="android.intent.action.MAIN"
                       (Raw: "android.intent.action.MAIN")
                     E: category (line=52)
                       A:
                       android:name(0x01010003)="android.intent.category.LAUNCHE
                       R" (Raw: "android.intent.category.LAUNCHER")
                 E: provider (line=56)
                   A:
                   android:name(0x01010003)="de.esys.esysfluttershare.EsysFlutte
                   rShareFileProvider" (Raw:
                   "de.esys.esysfluttershare.EsysFlutterShareFileProvider")
                   A: android:exported(0x01010010)=(type 0x12)0x0
                   A:
                   android:authorities(0x01010018)="com.mindle.echo.fileprovider
                   .github.com/orgs/esysberlin/esys-flutter-share" (Raw:
                   "com.mindle.echo.fileprovider.github.com/orgs/esysberlin/esys
                   -flutter-share")
                   A: android:grantUriPermissions(0x0101001b)=(type
                   0x12)0xffffffff
                   E: meta-data (line=61)
                     A:
                     android:name(0x01010003)="android.support.FILE_PROVIDER_PAT
                     HS" (Raw: "android.support.FILE_PROVIDER_PATHS")
                     A: android:resource(0x01010025)=@0x7f0c0000
                 E: activity (line=66)
                   A: android:theme(0x01010000)=@0x01030007
                   A:
                   android:name(0x01010003)="io.flutter.plugins.urllauncher.WebV
                   iewActivity" (Raw:
                   "io.flutter.plugins.urllauncher.WebViewActivity")
                   A: android:exported(0x01010010)=(type 0x12)0x0
                 E: provider (line=71)
                   A:
                   android:name(0x01010003)="io.flutter.plugins.imagepicker.Imag
                   ePickerFileProvider" (Raw:
                   "io.flutter.plugins.imagepicker.ImagePickerFileProvider")
                   A: android:exported(0x01010010)=(type 0x12)0x0
                   A:
                   android:authorities(0x01010018)="com.mindle.echo.flutter.imag
                   e_provider" (Raw: "com.mindle.echo.flutter.image_provider")
                   A: android:grantUriPermissions(0x0101001b)=(type
                   0x12)0xffffffff
                   E: meta-data (line=76)
                     A:
                     android:name(0x01010003)="android.support.FILE_PROVIDER_PAT
                     HS" (Raw: "android.support.FILE_PROVIDER_PATHS")
                     A: android:resource(0x01010025)=@0x7f0c0001
[  +24 ms] executing: /home/munene/Android/Sdk/platform-tools/adb -s RZ8MA26ZH2E
shell -x logcat -v time -s flutter
[  +13 ms] executing: /home/munene/Android/Sdk/platform-tools/adb version
[  +73 ms] Android Debug Bridge version 1.0.41
           Version 29.0.5-5949299
           Installed as /home/munene/Android/Sdk/platform-tools/adb
[   +3 ms] executing: /home/munene/Android/Sdk/platform-tools/adb start-server
[  +24 ms] Building APK
[  +30 ms] Running Gradle task 'assembleDebug'...
[   +2 ms] gradle.properties already sets `android.enableR8`
[  +37 ms] Using gradle from /home/munene/Projects/Flutter/echo/android/gradlew.
[  +21 ms] executing: /home/munene/android-studio/jre/bin/java -version
[ +102 ms] Exit code 0 from: /home/munene/android-studio/jre/bin/java -version
[        ] openjdk version "1.8.0_202-release"
           OpenJDK Runtime Environment (build
           1.8.0_202-release-1483-b49-5587405)
           OpenJDK 64-Bit Server VM (build 25.202-b49-5587405, mixed mode)
[   +6 ms] executing: [/home/munene/Projects/Flutter/echo/android/]
/home/munene/Projects/Flutter/echo/android/gradlew -Pverbose=true
-Ptarget=/home/munene/Projects/Flutter/echo/lib/main.dart
-Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root
-Ptarget-platform=android-arm64 assembleDebug
[+6569 ms] > Configure project :app
[        ] WARNING: The option setting 'android.enableR8=true' is experimental
and unsupported.
[        ] The current default is 'false'
[        ] Consider disabling R8 by removing 'android.enableR8=true' from your
gradle.properties before publishing your app.
[ +267 ms] > Configure project :esys_flutter_share
[        ] WARNING: The option setting 'android.enableR8=true' is experimental
and unsupported.
[        ] The current default is 'false'
[   +5 ms] Consider disabling R8 by removing 'android.enableR8=true' from your
gradle.properties before publishing your app.
[ +590 ms] > Configure project :image_picker
[   +1 ms] WARNING: The option setting 'android.enableR8=true' is experimental
and unsupported.
[        ] The current default is 'false'
[        ] Consider disabling R8 by removing 'android.enableR8=true' from your
gradle.properties before publishing your app.
[        ] > Configure project :path_provider
[        ] WARNING: The option setting 'android.enableR8=true' is experimental
and unsupported.
[        ] The current default is 'false'
[        ] Consider disabling R8 by removing 'android.enableR8=true' from your
gradle.properties before publishing your app.
[ +595 ms] > Configure project :sqflite
[        ] WARNING: The option setting 'android.enableR8=true' is experimental
and unsupported.
[        ] The current default is 'false'
[        ] Consider disabling R8 by removing 'android.enableR8=true' from your
gradle.properties before publishing your app.
[ +398 ms] > Configure project :url_launcher
[        ] WARNING: The option setting 'android.enableR8=true' is experimental
and unsupported.
[        ] The current default is 'false'
[   +3 ms] Consider disabling R8 by removing 'android.enableR8=true' from your
gradle.properties before publishing your app.
[  +95 ms] > Configure project :url_launcher_web
[        ] WARNING: The option setting 'android.enableR8=true' is experimental
and unsupported.
[        ] The current default is 'false'
[        ] Consider disabling R8 by removing 'android.enableR8=true' from your
gradle.properties before publishing your app.
[+2301 ms] > Transform lifecycle-viewmodel.aar
(androidx.lifecycle:lifecycle-viewmodel:2.0.0-rc01) with JetifyTransform
[        ] > Transform lifecycle-viewmodel.aar
(androidx.lifecycle:lifecycle-viewmodel:2.0.0-rc01) with ExtractAarTransform
[        ] > Transform lifecycle-viewmodel.aar
(androidx.lifecycle:lifecycle-viewmodel:2.0.0-rc01) with AarTransform
[        ] > Transform print.aar (androidx.print:print:1.0.0-rc01) with
JetifyTransform
[        ] > Transform print.aar (androidx.print:print:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform print.aar (androidx.print:print:1.0.0-rc01) with
AarTransform
[  +96 ms] > Transform localbroadcastmanager.aar
(androidx.localbroadcastmanager:localbroadcastmanager:1.0.0-rc01) with
JetifyTransform
[   +2 ms] > Transform localbroadcastmanager.aar
(androidx.localbroadcastmanager:localbroadcastmanager:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform localbroadcastmanager.aar
(androidx.localbroadcastmanager:localbroadcastmanager:1.0.0-rc01) with
AarTransform
[        ] > Transform documentfile.aar
(androidx.documentfile:documentfile:1.0.0-rc01) with JetifyTransform
[   +1 ms] > Transform documentfile.aar
(androidx.documentfile:documentfile:1.0.0-rc01) with ExtractAarTransform
[        ] > Transform documentfile.aar
(androidx.documentfile:documentfile:1.0.0-rc01) with AarTransform
[        ] > Transform cursoradapter.aar
(androidx.cursoradapter:cursoradapter:1.0.0-rc01) with JetifyTransform
[        ] > Transform cursoradapter.aar
(androidx.cursoradapter:cursoradapter:1.0.0-rc01) with ExtractAarTransform
[        ] > Transform cursoradapter.aar
(androidx.cursoradapter:cursoradapter:1.0.0-rc01) with AarTransform
[   +2 ms] > Transform annotation.jar
(androidx.annotation:annotation:1.0.0-rc01) with JetifyTransform
[   +7 ms] > Transform annotation.jar
(androidx.annotation:annotation:1.0.0-rc01) with IdentityTransform
[        ] > Transform collection.jar
(androidx.collection:collection:1.0.0-rc01) with JetifyTransform
[   +1 ms] > Transform collection.jar
(androidx.collection:collection:1.0.0-rc01) with IdentityTransform
[  +79 ms] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0-rc01) with
JetifyTransform
[   +4 ms] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform interpolator.aar
(androidx.interpolator:interpolator:1.0.0-rc01) with JetifyTransform
[        ] > Transform interpolator.aar
(androidx.interpolator:interpolator:1.0.0-rc01) with ExtractAarTransform
[        ] > Transform interpolator.aar
(androidx.interpolator:interpolator:1.0.0-rc01) with AarTransform
[        ] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0-rc01) with AarTransform
[        ] > Transform core-common.jar
(androidx.arch.core:core-common:2.0.0-rc01) with JetifyTransform
[        ] > Transform core-common.jar
(androidx.arch.core:core-common:2.0.0-rc01) with IdentityTransform
[  +92 ms] > Transform core-runtime.aar
(androidx.arch.core:core-runtime:2.0.0-rc01) with JetifyTransform
[        ] > Transform core-runtime.aar
(androidx.arch.core:core-runtime:2.0.0-rc01) with ExtractAarTransform
[        ] > Transform core-runtime.aar
(androidx.arch.core:core-runtime:2.0.0-rc01) with AarTransform
[        ] > Transform lifecycle-common.jar
(androidx.lifecycle:lifecycle-common:2.0.0-rc01) with JetifyTransform
[        ] > Transform lifecycle-common.jar
(androidx.lifecycle:lifecycle-common:2.0.0-rc01) with IdentityTransform
[        ] > Transform lifecycle-livedata-core.aar
(androidx.lifecycle:lifecycle-livedata-core:2.0.0-rc01) with JetifyTransform
[        ] > Transform lifecycle-livedata-core.aar
(androidx.lifecycle:lifecycle-livedata-core:2.0.0-rc01) with ExtractAarTransform
[        ] > Transform lifecycle-livedata-core.aar
(androidx.lifecycle:lifecycle-livedata-core:2.0.0-rc01) with AarTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0-rc01) with JetifyTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0-rc01) with ExtractAarTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0-rc01) with AarTransform
[        ] > Transform asynclayoutinflater.aar
(androidx.asynclayoutinflater:asynclayoutinflater:1.0.0-rc01) with
JetifyTransform
[        ] > Transform asynclayoutinflater.aar
(androidx.asynclayoutinflater:asynclayoutinflater:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform asynclayoutinflater.aar
(androidx.asynclayoutinflater:asynclayoutinflater:1.0.0-rc01) with AarTransform
[  +95 ms] > Transform swiperefreshlayout.aar
(androidx.swiperefreshlayout:swiperefreshlayout:1.0.0-rc01) with JetifyTransform
[        ] > Transform swiperefreshlayout.aar
(androidx.swiperefreshlayout:swiperefreshlayout:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform swiperefreshlayout.aar
(androidx.swiperefreshlayout:swiperefreshlayout:1.0.0-rc01) with AarTransform
[        ] > Transform core.aar (androidx.core:core:1.0.0-rc01) with
JetifyTransform
[        ] > Transform core.aar (androidx.core:core:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform core.aar (androidx.core:core:1.0.0-rc01) with
AarTransform
[  +97 ms] > Transform customview.aar
(androidx.customview:customview:1.0.0-rc01) with JetifyTransform
[        ] > Transform customview.aar
(androidx.customview:customview:1.0.0-rc01) with ExtractAarTransform
[        ] > Transform customview.aar
(androidx.customview:customview:1.0.0-rc01) with AarTransform
[        ] > Transform slidingpanelayout.aar
(androidx.slidingpanelayout:slidingpanelayout:1.0.0-rc01) with JetifyTransform
[        ] > Transform slidingpanelayout.aar
(androidx.slidingpanelayout:slidingpanelayout:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform slidingpanelayout.aar
(androidx.slidingpanelayout:slidingpanelayout:1.0.0-rc01) with AarTransform
[        ] > Transform drawerlayout.aar
(androidx.drawerlayout:drawerlayout:1.0.0-rc01) with JetifyTransform
[        ] > Transform drawerlayout.aar
(androidx.drawerlayout:drawerlayout:1.0.0-rc01) with ExtractAarTransform
[        ] > Transform drawerlayout.aar
(androidx.drawerlayout:drawerlayout:1.0.0-rc01) with AarTransform
[  +98 ms] > Transform coordinatorlayout.aar
(androidx.coordinatorlayout:coordinatorlayout:1.0.0-rc01) with JetifyTransform
[        ] > Transform coordinatorlayout.aar
(androidx.coordinatorlayout:coordinatorlayout:1.0.0-rc01) with
ExtractAarTransform
[   +1 ms] > Transform viewpager.aar (androidx.viewpager:viewpager:1.0.0-rc01)
with JetifyTransform
[        ] > Transform coordinatorlayout.aar
(androidx.coordinatorlayout:coordinatorlayout:1.0.0-rc01) with AarTransform
[        ] > Transform viewpager.aar (androidx.viewpager:viewpager:1.0.0-rc01)
with ExtractAarTransform
[        ] > Transform viewpager.aar (androidx.viewpager:viewpager:1.0.0-rc01)
with AarTransform
[        ] > Transform loader.aar (androidx.loader:loader:1.0.0-rc01) with
JetifyTransform
[        ] > Transform loader.aar (androidx.loader:loader:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform loader.aar (androidx.loader:loader:1.0.0-rc01) with
AarTransform
[  +93 ms] > Transform legacy-support-core-utils.aar
(androidx.legacy:legacy-support-core-utils:1.0.0-rc01) with JetifyTransform
[        ] > Transform legacy-support-core-utils.aar
(androidx.legacy:legacy-support-core-utils:1.0.0-rc01) with ExtractAarTransform
[        ] > Transform legacy-support-core-utils.aar
(androidx.legacy:legacy-support-core-utils:1.0.0-rc01) with AarTransform
[        ] > Transform legacy-support-core-ui.aar
(androidx.legacy:legacy-support-core-ui:1.0.0-rc01) with JetifyTransform
[        ] > Transform legacy-support-core-ui.aar
(androidx.legacy:legacy-support-core-ui:1.0.0-rc01) with ExtractAarTransform
[        ] > Transform legacy-support-core-ui.aar
(androidx.legacy:legacy-support-core-ui:1.0.0-rc01) with AarTransform
[        ] > Transform fragment.aar (androidx.fragment:fragment:1.0.0-rc01) with
JetifyTransform
[        ] > Transform fragment.aar (androidx.fragment:fragment:1.0.0-rc01) with
ExtractAarTransform
[        ] > Transform fragment.aar (androidx.fragment:fragment:1.0.0-rc01) with
AarTransform
[  +95 ms] > Transform lifecycle-common-java8.jar
(androidx.lifecycle:lifecycle-common-java8:2.0.0-rc01) with JetifyTransform
[        ] > Transform lifecycle-common-java8.jar
(androidx.lifecycle:lifecycle-common-java8:2.0.0-rc01) with IdentityTransform
[  +99 ms] > Transform x86_64_debug.jar
(io.flutter:x86_64_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695) with
JetifyTransform
[   +1 ms] > Transform x86_64_debug.jar
(io.flutter:x86_64_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695) with
IdentityTransform
[        ] > Transform x86_debug.jar
(io.flutter:x86_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695) with
JetifyTransform
[        ] > Transform x86_debug.jar
(io.flutter:x86_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695) with
IdentityTransform
[  +96 ms] > Transform arm64_v8a_debug.jar
(io.flutter:arm64_v8a_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695) with
JetifyTransform
[        ] > Transform arm64_v8a_debug.jar
(io.flutter:arm64_v8a_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b695) with
IdentityTransform
[        ] > Transform lifecycle-viewmodel.aar
(androidx.lifecycle:lifecycle-viewmodel:2.0.0-rc01) with AarTransform
[        ] > Transform print.aar (androidx.print:print:1.0.0-rc01) with
AarTransform
[        ] > Transform localbroadcastmanager.aar
(androidx.localbroadcastmanager:localbroadcastmanager:1.0.0-rc01) with
AarTransform
[        ] > Transform documentfile.aar
(androidx.documentfile:documentfile:1.0.0-rc01) with AarTransform
[        ] > Transform cursoradapter.aar
(androidx.cursoradapter:cursoradapter:1.0.0-rc01) with AarTransform
[        ] > Transform interpolator.aar
(androidx.interpolator:interpolator:1.0.0-rc01) with AarTransform
[        ] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0-rc01) with AarTransform
[        ] > Transform core-runtime.aar
(androidx.arch.core:core-runtime:2.0.0-rc01) with AarTransform
[        ] > Transform lifecycle-livedata-core.aar
(androidx.lifecycle:lifecycle-livedata-core:2.0.0-rc01) with AarTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0-rc01) with AarTransform
[        ] > Transform core.aar (androidx.core:core:1.0.0-rc01) with
AarTransform
[        ] > Transform asynclayoutinflater.aar
(androidx.asynclayoutinflater:asynclayoutinflater:1.0.0-rc01) with AarTransform
[        ] > Transform swiperefreshlayout.aar
(androidx.swiperefreshlayout:swiperefreshlayout:1.0.0-rc01) with AarTransform
[        ] > Transform customview.aar
(androidx.customview:customview:1.0.0-rc01) with AarTransform
[        ] > Transform slidingpanelayout.aar
(androidx.slidingpanelayout:slidingpanelayout:1.0.0-rc01) with AarTransform
[        ] > Transform drawerlayout.aar
(androidx.drawerlayout:drawerlayout:1.0.0-rc01) with AarTransform
[        ] > Transform coordinatorlayout.aar
(androidx.coordinatorlayout:coordinatorlayout:1.0.0-rc01) with AarTransform
[        ] > Transform viewpager.aar (androidx.viewpager:viewpager:1.0.0-rc01)
with AarTransform
[        ] > Transform loader.aar (androidx.loader:loader:1.0.0-rc01) with
AarTransform
[        ] > Transform legacy-support-core-utils.aar
(androidx.legacy:legacy-support-core-utils:1.0.0-rc01) with AarTransform
[        ] > Transform legacy-support-core-ui.aar
(androidx.legacy:legacy-support-core-ui:1.0.0-rc01) with AarTransform
[        ] > Transform fragment.aar (androidx.fragment:fragment:1.0.0-rc01) with
AarTransform
[  +90 ms] > Transform flutter_embedding_debug.jar
(io.flutter:flutter_embedding_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b6
95) with JetifyTransform
[  +99 ms] > Task :app:compileFlutterBuildDebug UP-TO-DATE
[        ] > Transform flutter_embedding_debug.jar
(io.flutter:flutter_embedding_debug:1.0.0-2994f7e1e682039464cb25e31a78b86a3c59b6
95) with IdentityTransform
[        ] > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[        ] > Transform lifecycle-viewmodel.aar
(androidx.lifecycle:lifecycle-viewmodel:2.0.0-rc01) with AarTransform
[        ] > Transform core-runtime.aar
(androidx.arch.core:core-runtime:2.0.0-rc01) with AarTransform
[        ] > Transform print.aar (androidx.print:print:1.0.0-rc01) with
AarTransform
[        ] > Transform localbroadcastmanager.aar
(androidx.localbroadcastmanager:localbroadcastmanager:1.0.0-rc01) with
AarTransform
[        ] > Transform documentfile.aar
(androidx.documentfile:documentfile:1.0.0-rc01) with AarTransform
[        ] > Transform cursoradapter.aar
(androidx.cursoradapter:cursoradapter:1.0.0-rc01) with AarTransform
[        ] > Transform interpolator.aar
(androidx.interpolator:interpolator:1.0.0-rc01) with AarTransform
[        ] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0) with JetifyTransform
[        ] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0) with
ExtractAarTransform
[        ] > Transform lifecycle-livedata-core.aar
(androidx.lifecycle:lifecycle-livedata-core:2.0.0-rc01) with AarTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0) with JetifyTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0) with ExtractAarTransform
[        ] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0) with AarTransform
[        ] > Transform core.aar (androidx.core:core:1.0.2) with JetifyTransform
[        ] > Transform core.aar (androidx.core:core:1.0.2) with
ExtractAarTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0) with AarTransform
[   +4 ms] > Transform asynclayoutinflater.aar
(androidx.asynclayoutinflater:asynclayoutinflater:1.0.0-rc01) with AarTransform
[        ] > Transform swiperefreshlayout.aar
(androidx.swiperefreshlayout:swiperefreshlayout:1.0.0-rc01) with AarTransform
[        ] > Transform customview.aar
(androidx.customview:customview:1.0.0-rc01) with AarTransform
[        ] > Transform slidingpanelayout.aar
(androidx.slidingpanelayout:slidingpanelayout:1.0.0-rc01) with AarTransform
[        ] > Transform drawerlayout.aar
(androidx.drawerlayout:drawerlayout:1.0.0-rc01) with AarTransform
[        ] > Transform coordinatorlayout.aar
(androidx.coordinatorlayout:coordinatorlayout:1.0.0-rc01) with AarTransform
[        ] > Transform core.aar (androidx.core:core:1.0.2) with AarTransform
[        ] > Transform viewpager.aar (androidx.viewpager:viewpager:1.0.0-rc01)
with AarTransform
[        ] > Transform media.aar (androidx.media:media:1.0.0-beta01) with
JetifyTransform
[        ] > Transform media.aar (androidx.media:media:1.0.0-beta01) with
ExtractAarTransform
[        ] > Transform media.aar (androidx.media:media:1.0.0-beta01) with
AarTransform
[        ] > Transform loader.aar (androidx.loader:loader:1.0.0-rc01) with
AarTransform
[        ] > Transform legacy-support-core-utils.aar
(androidx.legacy:legacy-support-core-utils:1.0.0-rc01) with AarTransform
[        ] > Transform legacy-support-core-ui.aar
(androidx.legacy:legacy-support-core-ui:1.0.0-rc01) with AarTransform
[        ] > Transform fragment.aar (androidx.fragment:fragment:1.0.0-rc01) with
AarTransform
[        ] > Transform legacy-support-v4.aar
(androidx.legacy:legacy-support-v4:1.0.0-beta01) with JetifyTransform
[        ] > Transform legacy-support-v4.aar
(androidx.legacy:legacy-support-v4:1.0.0-beta01) with ExtractAarTransform
[        ] > Transform legacy-support-v4.aar
(androidx.legacy:legacy-support-v4:1.0.0-beta01) with AarTransform
[        ] > Transform lifecycle-viewmodel.aar
(androidx.lifecycle:lifecycle-viewmodel:2.0.0-rc01) with AarTransform
[        ] > Transform core-runtime.aar
(androidx.arch.core:core-runtime:2.0.0-rc01) with AarTransform
[        ] > Transform print.aar (androidx.print:print:1.0.0-rc01) with
AarTransform
[        ] > Transform localbroadcastmanager.aar
(androidx.localbroadcastmanager:localbroadcastmanager:1.0.0-rc01) with
AarTransform
[        ] > Transform documentfile.aar
(androidx.documentfile:documentfile:1.0.0-rc01) with AarTransform
[        ] > Transform cursoradapter.aar
(androidx.cursoradapter:cursoradapter:1.0.0-rc01) with AarTransform
[        ] > Transform interpolator.aar
(androidx.interpolator:interpolator:1.0.0-rc01) with AarTransform
[        ] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0) with AarTransform
[        ] > Transform lifecycle-livedata-core.aar
(androidx.lifecycle:lifecycle-livedata-core:2.0.0-rc01) with AarTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0) with AarTransform
[        ] > Transform core.aar (androidx.core:core:1.0.2) with AarTransform
[        ] > Transform asynclayoutinflater.aar
(androidx.asynclayoutinflater:asynclayoutinflater:1.0.0-rc01) with AarTransform
[        ] > Transform swiperefreshlayout.aar
(androidx.swiperefreshlayout:swiperefreshlayout:1.0.0-rc01) with AarTransform
[        ] > Transform customview.aar
(androidx.customview:customview:1.0.0-rc01) with AarTransform
[        ] > Transform slidingpanelayout.aar
(androidx.slidingpanelayout:slidingpanelayout:1.0.0-rc01) with AarTransform
[        ] > Transform drawerlayout.aar
(androidx.drawerlayout:drawerlayout:1.0.0-rc01) with AarTransform
[        ] > Transform coordinatorlayout.aar
(androidx.coordinatorlayout:coordinatorlayout:1.0.0-rc01) with AarTransform
[        ] > Transform viewpager.aar (androidx.viewpager:viewpager:1.0.0-rc01)
with AarTransform
[        ] > Transform media.aar (androidx.media:media:1.0.0-beta01) with
AarTransform
[        ] > Transform loader.aar (androidx.loader:loader:1.0.0-rc01) with
AarTransform
[  +82 ms] > Transform legacy-support-core-utils.aar
(androidx.legacy:legacy-support-core-utils:1.0.0-rc01) with AarTransform
[   +2 ms] > Transform fragment.aar (androidx.fragment:fragment:1.0.0-rc01) with
AarTransform
[        ] > Transform legacy-support-core-ui.aar
(androidx.legacy:legacy-support-core-ui:1.0.0-rc01) with AarTransform
[        ] > Transform legacy-support-v4.aar
(androidx.legacy:legacy-support-v4:1.0.0-beta01) with AarTransform
[        ] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0-rc01) with AarTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0-rc01) with AarTransform
[        ] > Transform core.aar (androidx.core:core:1.0.0-rc01) with
AarTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0-rc01) with AarTransform
[   +1 ms] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0-rc01) with AarTransform
[        ] > Transform core.aar (androidx.core:core:1.0.0-rc01) with
AarTransform
[        ] > Transform annotation.jar (androidx.annotation:annotation:1.1.0)
with JetifyTransform
[        ] > Transform core-common.jar (androidx.arch.core:core-common:2.0.0)
with JetifyTransform
[        ] > Transform annotation.jar (androidx.annotation:annotation:1.1.0)
with IdentityTransform
[        ] > Transform core-common.jar (androidx.arch.core:core-common:2.0.0)
with IdentityTransform
[        ] > Transform collection.jar (androidx.collection:collection:1.0.0)
with JetifyTransform
[   +3 ms] > Transform versionedparcelable.aar
(androidx.versionedparcelable:versionedparcelable:1.0.0) with AarTransform
[   +1 ms] > Transform collection.jar (androidx.collection:collection:1.0.0)
with IdentityTransform
[        ] > Transform lifecycle-runtime.aar
(androidx.lifecycle:lifecycle-runtime:2.0.0) with AarTransform
[   +1 ms] > Transform core.aar (androidx.core:core:1.0.2) with AarTransform
[        ] > Transform media.aar (androidx.media:media:1.0.0-beta01) with
AarTransform
[        ] > Transform legacy-support-v4.aar
(androidx.legacy:legacy-support-v4:1.0.0-beta01) with AarTransform
[        ] > Transform lifecycle-common.jar
(androidx.lifecycle:lifecycle-common:2.0.0) with JetifyTransform
[        ] > Task :app:preBuild UP-TO-DATE
[        ] > Transform lifecycle-common.jar
(androidx.lifecycle:lifecycle-common:2.0.0) with IdentityTransform
[        ] > Task :app:checkDebugClasspath UP-TO-DATE
[        ] > Task :esys_flutter_share:preBuild UP-TO-DATE
[        ] > Task :esys_flutter_share:preDebugBuild UP-TO-DATE
[        ] > Task :esys_flutter_share:checkDebugManifest UP-TO-DATE
[        ] > Task :esys_flutter_share:processDebugManifest UP-TO-DATE
[   +2 ms] > Task :image_picker:preBuild UP-TO-DATE
[        ] > Task :image_picker:preDebugBuild UP-TO-DATE
[        ] > Task :image_picker:checkDebugManifest UP-TO-DATE
[   +1 ms] > Task :image_picker:processDebugManifest UP-TO-DATE
[        ] > Task :path_provider:preBuild UP-TO-DATE
[        ] > Task :path_provider:preDebugBuild UP-TO-DATE
[        ] > Task :path_provider:checkDebugManifest UP-TO-DATE
[        ] > Task :path_provider:processDebugManifest UP-TO-DATE
[        ] > Task :sqflite:preBuild UP-TO-DATE
[        ] > Task :sqflite:preDebugBuild UP-TO-DATE
[        ] > Task :sqflite:checkDebugManifest UP-TO-DATE
[        ] > Task :sqflite:processDebugManifest UP-TO-DATE
[        ] > Task :url_launcher:preBuild UP-TO-DATE
[        ] > Task :url_launcher:preDebugBuild UP-TO-DATE
[        ] > Task :url_launcher:checkDebugManifest UP-TO-DATE
[        ] > Task :url_launcher:processDebugManifest UP-TO-DATE
[        ] > Task :url_launcher_web:preBuild UP-TO-DATE
[        ] > Task :url_launcher_web:preDebugBuild UP-TO-DATE
[        ] > Task :url_launcher_web:checkDebugManifest UP-TO-DATE
[        ] > Task :url_launcher_web:processDebugManifest UP-TO-DATE
[        ] > Task :app:preDebugBuild FAILED
[  +68 ms] FAILURE: Build failed with an exception.
[   +2 ms] * What went wrong:
[        ] Execution failed for task ':app:preDebugBuild'.
[        ] > Android dependency
'androidx.versionedparcelable:versionedparcelable' has different version for the
compile (1.0.0-rc01) and runtime (1.0.0) classpath. You should manually set the
same version via DependencyResolution
[        ] * 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
[        ] BUILD FAILED in 12s
[        ] 16 actionable tasks: 1 executed, 15 up-to-date
[ +378 ms] Running Gradle task 'assembleDebug'... (completed in 12.8s)
[   +3 ms] The built failed likely due to AndroidX incompatibilities in a
plugin. The tool
           is about to try using Jetfier to solve the incompatibility.
[   +7 ms] Building plugin esys_flutter_share...
[   +5 ms] Running Gradle task 'assembleAarRelease'...
[        ] gradle.properties already sets `android.enableR8`
[   +1 ms] Using gradle from
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/esys_flutter_share-1.0.2
/android/gradlew.
[        ] executing:
[/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/esys_flutter_share-1.0.
2/android/]
/home/munene/flutter/.pub-cache/hosted/pub.dartlang.org/esys_flutter_share-1.0.2
/android/gradlew
-I=/home/munene/flutter/packages/flutter_tools/gradle/aar_init_script.gradle
-Pflutter-root=/home/munene/flutter
-Poutput-dir=/home/munene/Projects/Flutter/echo/build/app -Pis-plugin=true
-Ptarget-platform=android-arm,android-arm64,android-x64 assembleAarRelease
[  +21 ms] Running Gradle task 'assembleAarRelease'... (completed in 0.0s)
[   +5 ms] "flutter run" took 15,758ms.

Sending crash report to Google.
Crash report sent (report ID: 799e368d46467d52)
Oops; flutter has exited unexpectedly.

Crash report written to /home/munene/Projects/Flutter/echo/flutter_04.log;
please let us know at https://github.com/flutter/flutter/issues.

Analyzing echo...

   info • Unused import: 'package:moor_flutter/moor_flutter.dart' •
          lib/pages/edit_journal.dart:10:8 • unused_import
   info • The declaration '_capturePng' isn't referenced •
          lib/pages/journal.dart:61:21 • unused_element
   info • The value of the field '_messages' isn't used •
          lib/pages/journals.dart:43:16 • unused_field
   info • The value of the field '_reflections' isn't used •
          lib/pages/notes.dart:14:8 • unused_field
   info • The value of the field '_color' isn't used • lib/pages/notes.dart:17:9
          • unused_field
   info • The declaration '_capturePng' isn't referenced •
          lib/pages/rich.dart:57:21 • unused_element
   info • Don't import implementation files from another package •
          lib/pages/rich_edit.dart:6:8 • implementation_imports

7 issues found. (ran in 55.6s)

[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Linux, locale en_US.UTF-8)
    • Flutter version 1.12.13+hotfix.5 at /home/munene/flutter
    • Framework revision 27321ebbad (34 hours ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/munene/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /home/munene/Android/Sdk
    • Java binary at: /home/munene/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Android Studio (version 3.5)
    • Android Studio at /home/munene/android-studio
    • Flutter plugin version 40.2.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)

[✓] IntelliJ IDEA Ultimate Edition (version 2019.2)
    • IntelliJ at /home/munene/IntelliJ
    • Flutter plugin version 39.0.5
    • Dart plugin version 192.6262.58

[✓] VS Code (version 1.40.2)
    • VS Code at /usr/share/code
    • Flutter extension version 3.7.1

[✓] Connected device (1 available)
    • SM A505F • RZ8MA26ZH2E • android-arm64 • Android 9 (API 28)

• No issues found!

 The built failed likely due to AndroidX incompatibilities in a plugin.
it might depend from this 3rd party plugin esys_flutter_share;
since you just upgraded try running
flutter clean
flutter pub cache repair
if the issue persists you may want to consider opening an issue on the dedicate github
or try without said plugin.
Let me know if the issue persists.
Thank you

This is what worked for me https://github.com/flutter/flutter/issues/27254#issuecomment-458689343

Hi @newtonmunene99
given your last message I feel safe to close this issue,
if you disagree please write in the comments
and I will reopen it.
Thank you


WIP: fix: band grid settings

What has changed and why
Summarize files edited as part of this MR along with a brief description of what was changed/why.

Added variables to the system for standard grid gaps, per breakpoint
Added an align-self variable hook to pfe-card to allow the card to fill or not-fill it's container
Added a max-height: fit-content to pfe-cta to prevent it from getting too fat (tall) in a grid layout.

Testing instructions
Be sure to include detailed instructions on how your update can be tested by another developer.

Open the demo page in various browsers to ensure the layout variables are being honored.

Browser requirements
Your component should work in all of the following environments:

[ ] Latest 2 versions of Edge
[ ] Internet Explorer 11 (should be useable, not pixel perfect)
[ ] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[ ] Firefox 60.7.2 (or latest version for Red Hat Enterprise Linux distribution)
[ ] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[ ] Latest 2 versions of Safari
[ ] Galaxy S9 Firefox
[ ] iPhone X Safari
[ ] iPad Pro Safari
[ ] Pixel 3 Chrome

Ready-for-merge Checklist

[ ] Expected files: all files in this pull request are related to one feature request or issue (no stragglers)?
[ ] Did browser testing pass?
[ ] Did you update or add any necessary documentation (README.md, WHY.md, etc.)?
[ ] Was this feature demo'd and the design review approved?
[ ] Did you update the CHANGELOG.md file with a summary of this update?

Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!
TODO

Would you be up for fixing https://github.com/patternfly/patternfly-elements/issues/619 in this branch?

@starryeyez024 Can you add some tests to support the new attribute?

@starryeyez024 Can this be updated to sync with the latest or do we want to close this for now?

@starryeyez024 Can this be updated to sync with the latest or do we want to close this for now?

I attempted to resolve merge conflicts on this one and it is very challenging and quite out of date.  I suspect a lot of this has been addressed so I'll close it for now.  If you want to go through the update process, feel free to re-open!


refactor: try to use select in async stream function

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Close #4947
However, seems not easy to add a tokio::select in futures-async-stream.
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

There are some other potential solutions:

Manually use if to try_recv from the channel.
Manually implement the #[try_stream] just like https://crates.io/crates/futures-async-stream. (Just like RemoteInput, LocalInput, needs investigation).

cc @BugenZhao


🔧 BalanceInput height

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[] Closes #6871
[ ] Requires deployment <snek/rubick/worker>

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed UI

Copilot Summary

🤖 Generated by Copilot at bb0ef29
Improved the UI of the balance input component by adding a custom CSS class. This affects the file components/shared/BalanceInput.vue.

🤖 Generated by Copilot at bb0ef29

To make the balance input look nice
We added a custom CSS class
It's called .h-full
And it makes the element tall
So it fills the parent's height with sass

forms affected:


Feature to opt-in/opt-out log collection

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[x] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[x] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@visingl , can you go through the first comment of this PR and check on proper items? I assume this service isn't GAed, right? Is public repo master branch used in rpaas production or it uses private repo RpSaasMaster branch spec?

@visingl , can you go through the first comment of this PR and check on proper items? I assume this service isn't GAed, right? Is public repo master branch used in rpaas production or it uses private repo RpSaasMaster branch spec?

@ArcturusZhang @msyyc , can you check if there's any potential breaking change for GO/Python SDKs?

For python, the breaking change is ok.

/azp run

The brekaing changes are accumulated from previous PRs.

Breaking change policy is out of scope because this service is not GAed.

/azp run


Add telemetry support for H8 3D

I am so used to the great Telemetry support in the other Silverware versions that its a shame the unique H8 3D doesn't have it. Maybe one day all the silverware versions could even share a single codebase with different build targets to accommodate the different supported boards. Thanks for making crappy plastic toys to insane precise micro racers

The single codebase could be nice, but I like make sure the quad flies with the posted code, as this is intended for uses without programming experience. Sometimes little things can break hardware support, especially as the hardware is sometimes different between quads in various ways.
I would probably do things differently now but when I started this I didn't know how it's going to work out.
Anyway, I added telemetry now, I didn't think anyone uses h8 3ds because it was never really popular.

Great to hear! Sadly I lost my H83D due to missing telemetry ;) and running the lipo flat but as soon as a new one arrives I will test the changes.


Guest Access to AWS Fleet Manager (Remote Desktop only)

User Story
I have a query involving granting temporary PPUD access to a guest user (MoJ partner). We need to allow them to have access to AWS Fleet Manager but only the RDP component. We need to disable terminal session access. Further RDP access will then be controlled via domain security groups. Terminal session access via ssm-user is a backdoor that we'd like to close off, but this can only be done in AWS. Can a profile be created to provide this level of access? Are the permissions that granular?
The profile should only be allowed access to the Development environment. I know this is easily done. It should also only have read only permissions to allow other aspects of AWS.
Value / Purpose
The guest user is performing some development work for the MoJ and needs access to the code base, which we are going to provide on a custom built EC2 instance. We need to lock down access to only this EC2 instance and only via remote desktop.
Useful Contacts
Nick Buckingham
Additional Information
I've reviewed the guide on user access but don't see a particular profile that meets our requirements, meaning a custom one may be required. Is this possible?
https://user-guide.modernisation-platform.service.justice.gov.uk/user-guide/creating-environments.html#access
Proposal / Unknowns
No response
Definition of Done
Guest user has remote desktop access to a single EC2 instance. Read only permissions on AWS and terminal session access via fleet manager is disabled for the user.

Step 3 on page 953 might do what we need to lock down session manager access to a single EC2 instance.
https://docs.aws.amazon.com/pdfs/systems-manager/latest/userguide/systems-manager-ug.pdf

can we add to an existing role or does it need to be a brand new role. Edd to discuss with Nick. To be done by a new member of the team, supported by Edd

I'm easy, whatever works. As long as they can only access a single EC2 instance via fleet manager then we're good. This will be in January now.

lets create new role with access to fleet manager only

Role and policy created. Informed @SimonPPledger of it, and tested it. @sukeshreddyg has done all this work, and it works great! All we need when the time arises is the name of the third party (so we can created them collab access)
Apart from that, ticket complete, waiting Simons sign off.

Great news, so the role/policy only grant access to fleet manager and the terminal session option is disabled?

Role created for collaborators.


Split mutations into separate files

The desired project structure is to have each mutation in a separate file. Some modules that need refactoring include:

account
giftcard
invoice
menu
meta
payment
shipping
shop
warehouse

Review the test modules as well - each mutation should have tests in a separate file as well.

Great work @IKarbowiak 👍 🎉


Upgrade to Alpine 3.6

Mainly because it has Ruby 2.4:
https://alpinelinux.org/posts/Alpine-3.6.0-released.html

Agent done in: #2630
Server done in: #2456


fix: add new example to use existing kms

Description
Adds new example to create keyring within existing KMS.
Types of changes in this PR
Changes that affect the core Terraform module or submodules

[ ] Bug fix
[ ] New feature
[ ] Dependency update

Changes that don't affect the core Terraform module or submodules

[x] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other

Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.

[x] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
If a release is required, replace this text with information that users need to know about the release. Write the release notes to help users understand the changes, and include information about how to update from the previous version.
Your notes help the merger write the commit message for the PR that is published in the release notes for the module.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

/run pipeline

/run pipeline

A few points:

It would be better to keep any one of the examples, not both. As they both are very similar.
But if you decide to keep both of them, then I'd recommend you make a change in the "default" example, to consume https://github.com/terraform-ibm-modules/terraform-ibm-key-protect module to create the Key protect instance. Right now, it creates on its own using Terraform.
Also, please add a new test for the example as well. Maybe in the other_test.go. To make that test work you need to spin up a permanent Key Protect instance. You can do that here https://github.ibm.com/GoldenEye/ge-dev-account-management/blob/master/main.tf

A few points:
1. It would be better to keep any one of the examples, not both. As they both are very similar.

2. But if you decide to keep both of them, then I'd recommend you make a change in the "default" example, to consume https://github.com/terraform-ibm-modules/terraform-ibm-key-protect module to create the Key protect instance. Right now, it creates on its own using Terraform.

3. Also, please add a new test for the example as well. Maybe in the `other_test.go`. To make that test work you need to spin up a permanent Key Protect instance. You can do that here https://github.ibm.com/GoldenEye/ge-dev-account-management/blob/master/main.tf

@rajatagarwal-ibm

Going forward, this repo will be used as KMS i.e. for KP and HPCS. So in one of the discussion...the idea of adding a new example came out hence the example was added. So we'll keep both the examples.
As this example was added to make this repo ready for HPCS, so lets merge this PR. Request to change example 1 - will address as a separate issue - #5153 . I can pick this up after HPCS activities.
I do not think if we really need a test for this...as it is just creating keyring which anyways is getting tested in default example.

Let me know your thoughts. Thanks

Alright if you want to address some of the points in the separate PR. I will approve this one.
Also, in case this module supports HPCS then perhaps we need to rename this module from Key Protect to Key Management.
I think in that case we can add a test pointing to the existing HPCS instance. That will give coverage to both KP and HPCS KMS services.

yes, KP -> KMS change is the next that is coming for this module. Addressing that via #5141.


foundation.css file throw an 404 error on childthemes

Hello everyone,
I get an 404 error for http://localhost/X/wp-content/themes/my-child-theme-name/assets/stylesheets/foundation.css?ver=2.3.0 file.
I didn't get an 404 error when I change get_stylesheet_directory_uri() to get_template_directory_uri()
I'm talking about : https://github.com/olefredrik/FoundationPress/blob/v2.5.0/library/enqueue-scripts.php#L16
Is there any special reason to use get_stylesheet_directory_uri() instead of get_template_directory_uri()?

How can this bug be reproduced?

Create a child theme and set to default theme from WP admin panel.
Visit your homepage and check your browser network console log.

What did you expect to happen?
I must get 200, not 400.

Thanks. Fixed https://github.com/olefredrik/FoundationPress/pull/759

This gives me an error when using a child theme with FoundationPress, see the get_stylesheet_directory_uri documentation.

Use get_template_directory_uri() to avoid being overridden by a child theme

so get_stylesheet_directory_uri was the right way for child themes :)


fix(TileGroup): Wrap RadioTiles inside TileGroup

This adds a wrapper div element around the RadioTiles inside the TileGroup component so that a flex layout can be applied to the tiles to make them render horizontally.
Already merged into latest master. See https://github.com/carbon-design-system/carbon/pull/3947

@asudoh I'm hoping we can get this TileGroup fix into v6, where we really need it right now.  Can you take a look?


Macos anka build farm doc 1727

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-684

Preview environment: https://ci.pr.harness.io/pr-684

Preview environment: https://ci.pr.harness.io/pr-684

Finalizing this doc in a new PR: https://github.com/harness/developer-hub/pull/732


[release-2.9] Update to Go v1.22

ref: https://issues.redhat.com/browse/ACM-14251

This won't be necessary since we're not upgrading the go.mod for 2.9 yet (just the builder image).


Linear Model Deviation-base Outlier Detection isn't setting 'random_state'

I'm calling LMDD(contamination=outliers_fraction,random_state=42) and from .get_params(deep=True) I got:
{'contamination': 0.37894127856522997, 'dis_measure': 'aad', 'n_iter': 50, 'random_state': None}

thanks for the great work.

Thanks for your query.
That is because the variable name, in the implementation, is self.random_state_ with an underscore at the end.
I can change it right now, yet I do not know if this would make it incompatible with Scikit learn, as in this similar query.
Escalated to @yzhao062.
Regards,
Yahya.

sorry I was caught by developing new things at the moment. Let me see if this can be fixed in a few minutes now :) thanks both for the thought!


#554: Only show teams from the current season and division in new date

Resolves #554

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
7774

Relevant Lines:
7933

💛  - Coveralls


Remove support for Python 2.x

Required for https://github.com/UAVCAN/pyuavcan/issues/37

Done in uavcan-v1.0. The rewrite requires Python 3.7 or newer.


Develop

Version 1.3 merge
This should be full merge not squash and merge.

If tests pass this can be merged.


Type Annotations in ansible-core

Proposal: Type Annotations in Ansible Core
Author: Matt Davis - @nitzmahone
Date: 2021-11-17

Status: New
Proposal type: core design
Targeted release: 2.13
Associated PR: https://github.com/ansible/ansible/pull/76332
Estimated time to implement: TBD

Motivation
Since the ansible-core controller fully dropped support for older versions of Python in 2.12, new Python language features like inline type annotations have become available to us. Before we open the floodgates to type annotations being splattered across the core codebase, it's necessary to define some policy around how type annotations will be used, and especially how they will be validated.
Problems
What problems exist that this proposal will solve?

Ensure reasonable consistency in application of type annotations in core codebase
Ensure that type annotations are being validated by sanity tests
Balance the usefulness of type annotations (call-site validation, self-documentation, IDE completion) with ease of development and maintenance

Solution proposal
General guidelines

At minimum, any net-new public Python API added to ansible-core from 2.13 on should have type annotations.
Type annotations should be added to existing public API surfaces only after consensus has been reached on the value of doing so, and if the resultant type annotations are not overly complex. Adding pedantically-correct type annotations to existing APIs that were not designed for it can result in unmaintainable or unreadable code. A careful balance between maintainability and correctness needs to be struck for annotations of pre-existing APIs.
Each release of ansible-core will specify a major.minor release of mypy to validate its annotations. Other validators were considered (pytype, pyright, pyre), but mypy currently strikes the best balance of stability, performance, and ease-of-use in our testing.
Type validation ignore entries should be per-Python version (TBD whether annotations are validated for multiple Python versions- the current sample PR tests all supported controlller/target Python versions)
For validation, require pinned type stubs for defined/documented public ansible-core deps (eg, Jinja2, pyyaml, requests, packaging, toml). Use a template mechanism to manage updates to pinned versions across major releases of core (the sample PR implements this).

Style

Imports: import typing as t where possible for brevity (balance typing import boilerplate with terse annotations)
Function/method annotations take priority. Call-site/var type annotations can be added where most calls are to well-annotated code and the annotations provide significant benefit without impeding readability/maintainability.

Controller code

Use PEP484/PEP526 language-integrated inline type annotations, since the controller is always Python3.8+
The PEP563 deferred annotations future should be imported to improve runtime performance. Consider adding this to the required boilerplate for controller code.

Non-controller code (module API, modules, module_utils, collection loader)

Use inline PEP484 type comments on new module APIs.
Avoid use of stub files unless type annotations become extremely unwieldy; we should be worried more about moving docs out of target-side code before worrying about the additional code bloat from type annotations.

ansible-test code
The ansible-test codebase is already heavily type-annotated, and the annotation sample PR above includes validation.
Dependencies

A type annotation validator (eg, mypy as in the sample sanity test PR above)

Testing
Type annotations should always be validated when present; sanity testing is a necessary pre-requisite to applying new type annotations.
Documentation
When these policies are finalized, they should be documented in the ansible-core development guidelines.
Non-Goals
Collections support
Bounding the problem-space properly for the ansible-core codebase will be difficult enough, and may take several releases to get the proper tooling and procedures in place. Supporting collections with the initial tooling adds a significant amount of complexity we're not currently staffed to deal with (multiple Ansible versions, broader Python/validator version scopes, multiple profiles).
Type-annotating the entire ansible-core codebase
Our initial approach should be to tread lightly and discover problems by applying type annotations to new public APIs and high-value areas, not to blanket apply type annotations to the entire codebase. Massive unsolicited type annotation PRs should not be accepted.
Runtime type checks
Runtime type-checking in Python is in relative infancy; our initial application should be focused on validation at development-time, not strict runtime enforcement.
Docstring integration
Language-standard type annotations, while a form of documentation, were generally designed to be used inline for consumption by type checkers and IDE completion. Defining an overall policy for docstrings is orthogonal, since the stated goals cannot be met with legacy type annotations in docstrings.

+1 from me

+1

+1

+1

+1

Closing since this was implemented by https://github.com/ansible/proposals/issues/202 (and related followups)


cc-wrapper: pass always -B and -L together to avoid mixing parts of libc

Motivation for this change
Before this change cc-wrapper was mixing crt1.o and libc.so.6
from different libc during bootstrap:
expand-response-params>   -B/...-bootstrap-tools/lib
expand-response-params>   -B/...-glibc-2.35/lib/
...
expand-response-params>   -L/...-glibc-2.35/lib
expand-response-params>   -L/...-bootstrap-tools/lib

Normally it's not a problem as crt1.o did not change for
quite a few releases. But glibc-2.35 dropped __libc_csu_fini symbol:
expand-response-params> ld: ...-bootstrap-tools/lib/crt1.o: in function `_start':
expand-response-params> ...glibc-2.27/csu/../sysdeps/x86_64/start.S:101: undefined reference to `__libc_csu_fini'
expand-response-params> ld: /build/glibc-2.27/csu/../sysdeps/x86_64/start.S:102: undefined reference to `__libc_csu_init'
expand-response-params> collect2: error: ld returned 1 exit status

The change always passes -B/-L together to have a higher chance
to override both parts of libc. It allows bootstrapping toolchain
on glibc-2.35.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Was too impatient. After a few packages it still fails. I probably need to find the opposite place where only -L is injected. Will debug a bit more.

Added -L in a second missing place. And now -rpath for both libcs is being injected and breaking bianries.

This version should be better now. Ready for review.

@trofi @lovesegfault  If you have the cycles to spare, I would *really deeply appreciate instead making the bootstrap tools not throw everything together, in combined bin / inc / lib dirs. If we organized it like a little mini Nix store, with a separate dirs per each item, we would flat out avoid sketchy ordering problems altogether, and it would better line up with the other bootstrapping we do.
This would also pave the way for both of

https://github.com/NixOS/nixpkgs/pull/31414
https://github.com/NixOS/nixpkgs/pull/132343
More generally making the native bootstrapping follow the cross patterns and be more "automatic"

especially the former, which failed precisely because of these sorts of issues!
I have been meaning to do this for years, but never found the time. It would be a game changer to see this first step done!

@trofi @lovesegfault If you have the cycles to spare, I would really, deeply appreciate instead making the bootstrap tools not throw everything together, in combined bin / inc / lib dirs. If we organized it like a little mini Nix store, with a separate dirs per each item, we would flat out avoid sketchy ordering problems altogether, and it would better line up with the other bootstrapping we do.
This would also pave the way for both of
* [Stdenv setup: Process dependencies before dependents #31414](https://github.com/NixOS/nixpkgs/pull/31414)

* [WIP: GCC with separated runtime libraries #132343](https://github.com/NixOS/nixpkgs/pull/132343)

* More generally making the native bootstrapping follow the cross patterns and be more "automatic"

especially the former, which failed precisely because of these sorts of issues!
I have been meaning to do this for years, but never found the time. It would be a game changer to see this first step done!

I agree it would help. I'd like to look at it longer term as well. I have a few questions:

Is this change blocking the other efforts or or has a potential of causing subtle problems? I'd like to get it merged :)
Is bootstrap from FHS system somewhat supported by nixpkgs? I think we would need to deal with the -B/-L ordering for that case as well.

Bootstrap from native FHS is at most barely supported and a separate bootstrap. I wouldn't worry about it.
Could we just cut down the comment to say something like "warning, changing the order could break certain bootstraps until libraries are better separated to more does"? I don't want to falsely imply this is a better order when I think the rearranging is just a stop-gap fix and the order ought not to matter.

Shrunk the comment, explicitly mentioned that ordering is a workaround.

Thanks, and sorry to be a nit-pick!


Add AI-assisted development tools and update project structure

Add .ai folder with development tools:

Codex for learnings and errors
Session management tools
Blueprints for technical setups
Rules for AI behavior
Snippets for code generation

Add new Python files:

benchmark.py
eval.py
utils.py

Add tokenizer.model file
Update dependencies in poetry.lock and pyproject.toml
Add pytest configuration and test files
Update project documentation in README.md

This commit introduces a comprehensive set of AI-assisted development tools
and updates the project structure to improve code quality and consistency.

Thanks for submitting a PR! A few notes:

the at folder has a lot of boilerplate not really specific to this repo (frontend, shadcn, etc). I am generally fine including this kind of directory in to aid AI tooling but i want to make sure its both very specific to this repo and there is ample documentation showing how to use it with cursor or continue.dev, etc. We really want to make sure this is a minimalist repo and project and only the very essential tools and docs are added

On a clean clone of your branch there are failing tests. Please make sure the tests are passing from a clean state before you submit, We also want to make sure each of the tests has a clear goal (i.e, functionality its exercising, assumptions its validating, etc) vs just general coverage. Tests are valuable but they are also additional code that needs to be maintained and updated, so we want to make sure each line of code we add pulls its weight.

I like the idea of including the eval and benchmark files but i want to make sure they are immediately useful if we merge them to main. Please run the benchmark and include the output of the results to verify that its working properly and as expected. Please also include at least one working eval with the corresponding test data (preferably in jsonl included in the repo or with clear download instructions) with the output of the eval to ensure its working as expected. For extra credit, a nice addition would be to compare the new eval against a reference llama impl (hf or meta) to make sure the new eval is measuring results as expected.

I highly encourage the use of AI tools and copy / paste from different relevant other projects but there did seem to be a few bits that were direct AI output. No problems there, but do make sure that you review all that AI code and make sure its relevant to the code and projects.


Getting Bad Gateway on a fresh setup. When using dot in my service name.

I was trying to set up a couple of instances with Kamal and was constantly getting Bad Gateway on all of them. I tried redeploying and spun up fresh ones as well.
With health checks passing, the setup and deploy commands were successful.
I did some digging:

both containers are up
docker inspect looked fine(to me).
I even SSH'd into the app and traefik containers on the instance to make sure they could communicate with each other.
when I tried curl from the traefik container, it worked without any issues.

Traefik logs:
2024-02-07T17:09:17.248587866Z time="2024-02-07T17:09:17Z" level=debug msg="'502 Bad Gateway' caused by: dial tcp <IP_ADDRESS>:0: connect: connection refused"
2024-02-07T17:12:43.194810142Z time="2024-02-07T17:12:43Z" level=debug msg="'502 Bad Gateway' caused by: dial tcp <IP_ADDRESS>:0: connect: connection refused"

~Solution
I used a dot in the service name, like app7.1, which seemed harmless at first glance.
To fix it, I simply removed the dot from the service name, making it app71, and everything started working smoothly.
Just to be clear it's config/deploy.yml:
# Name of your application. Used to uniquely configure containers.
service: app71

My theory is that, although I'm not an expert in Docker routing and Traefik, the issue might be related to how the config files are named after the service name and Traefik/Docker labels. It seems like they could be causing some unintended issues.
Can someone confirm/deny it? If this is the case we can add it to documentation.

Hi @tahirwaseer ,
You're correct in that a dot in the service name would cause an issue.
In the documentation under configuration search "Using container labels" and you'll see:
Traefik rules are in the “service-role-destination” format. The default role will be web if no rule is specified. If the destination is not specified, it is not included. To give an example, the above rule would become “traefik.http.routers.hey-web-staging.rule” if it was for the “staging” destination.
This sort of eludes to the reason why you get the error. The orchestration happening with Kamal, docker and Traefik breaks if you use a dot. Traefik leans heavily on dot notation for labels and passing in configuration.
Hope this helps gain a bit of context.

Looks like it should be either handled by Kamal or explicitly forbidden.

@tahirwaseer Opened a PR to fail early if the service name contains dots in #692.


Promoting certain items

Hello! I'm not a user yet.
MeiliSearch looks promising!
Is it possible to move some item from somewhere on the result list to the top?
#priority

I think you can use custom ranking rules, and add a priority field to your documents that you'd use to sort.

Thank you.
https://docs.meilisearch.com/learn/core_concepts/relevancy.html#adding-your-rules


How to disConnect the device immediately, after OTA complete。

Hi guys:
After OTA complete, How to disconnect the device immediately,  When I call - (void)cancelPeripheralConnection:(CBPeripheral *)peripheral;, But is don't work,  I can call - (void)scanForPeripheralsWithServices:(nullable NSArray<CBUUID *> *)serviceUUIDs options:(nullable NSDictionary<NSString *, id> *)options; to scan the device, It  work.
Is there some to method call in iOSDFULibrary. Any suggestions ?
Thank you!

After the DFU is complete, the device will disconnect automatically on it's own.
You may connect using the original CBPeripheral object, had it not changed the MAC address.

Thank you , I will try it.


Normalize timeout exception

When the Socket adapter meet timeout problems, it raises an AdapterException\TimeoutException exception.
Let's do the same for the cURL client too.

@mlocati can you provide a unit test to cover this new use case? Thanks,

@mlocati can you provide a unit test to cover this new use case? Thanks,

Sure: https://github.com/zendframework/zend-http/pull/99/commits/69ca294117e882e3fe223500768da8e9aed0e143

@mlocati can you send the PR against develop branch? Thanks!

@mlocati can you send the PR against develop branch? Thanks!

Done.

@mlocati thanks for your contribution!


[incubator/vault]: allow adding service type as nodeport with predefi…

…ned nodeport value
Signed-off-by: Mukesh Sharma<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md

/assign @mattfarina

@sssd-dev Thanks for the pull request. Can you please rebase from master and increment the chart version in the Chart.yaml file.

@mattfarina I have rebased as per Master and also added the variable in Readme

@sssd-dev Can you please sign the commits. Please see the checks tab on the pull request for details on how to do this.


Periodically eats up memory until killed because of OOM

Here is screenshot of grafana metrics

This is caused by #1 not being implemented yet.


WorkItem Links does not show up on when direct detail link is hit

Steps to reproduce

Go to http://demo.almighty.io/work-item-list/detail/346
No links are shown
Select another WorkItem from the List
Use back button to go back to the first WorkItem
64 links are shown (64 links are actually correct number according to DB)

Demo: https://youtu.be/sjAUbtMVrUM

@sanbornsen can you please take a look at this.

Can't reproduce.

I think this issue is not there anymore. Got resolved with last set of update for linking.

@aslakknutsen can you verify and close the issue?

Closing as the issue has been fixed.


onChange does not work....

OnChage() function does not recognize external variables...
i can't save contents

@kk2415 you can try this react-summernote-lite


Add label background image asynchronously

Fixes https://github.com/CesiumGS/cesium/issues/10342
Here's a local sandcastle that easily shows the issue.
This arose during https://github.com/CesiumGS/cesium/pull/10275. I've confirmed that this fixes the above issue while still maintaining the 3d tileset inspector  label behavior that was restored as part of that pull request.
I also removed _whitePixelIndex as it was assigned but never read anywhere as far as I could tell.
However, I'm having trouble understanding why this fix works. The canvas canvas passed to the addImage function does not require loading and therefore does not require awaiting a promise in order to add it to the texture atlas.
@lilleyse Would you be able to give this a look?

It seems like canvas drawing operations have a synchronous API but are actually queued up and drawn when the browser hits an animation refresh. I assume by wrapping it in a promise the promise gets resolved after that refresh.
I would've expected gl.texImage2D to wait until the canvas is ready. So I'm not really sure what's going on either without diving deeper into this.

Thanks @lilleyse. I'm not sure what may be happening with gl.texImage2D, but that at least explains what's happening with the update flow here. Added a comment to explain.


Fix naive NewUintXXX implementation.

Current implementation has a big problem :clown_face:
// NewBigInt generates a random `BigInt` in range 0 <= `CEIL`.
export function NewBigInt(rng: PRNG, CEIL: bigint): bigint {
	const base = CEIL / 2n;
	const offset = (BigInt(Math.floor(100 * rng.uFloat32())) * base) / 100n; // <-- Not good.
	const add = (v1: bigint, v2: bigint): bigint => {
		return v1 + v2;
	};
	const sub = (v1: bigint, v2: bigint): bigint => {
		return v1 - v2;
	};
	const op = rng.uFloat32() < 0.5 ? add : sub;
	return op(base, offset);
}

This results in a lot of repeated values and false negatives in some tests. Even better if we can find a battletested library which we could utilise for stuff like this.

Could we short-term just use our newRandomUint8Array and truncate the last byte, if CEIL is not a power of 256?

Besides that I'm also not too happy with the prng lib that we use. Martin Helmut's number-generator has only 9 ⭐ It still looks like a solid project though.


Unify collection indexing: int or long?

If we want to support very big collections (i.e. Vector or List could reasonably support > 2 billion elements), we should change all index related operations to longs instead of ints, e.g.:

get(int index)
int length()
update(int index, T element)
insert(int index, T element)
removeAt(int index)
indexOf(T element, int from)
…

If we're not planning on doing that, than we should unify all index related types to integers instead:

grouped(long size)
drop(long n) & dropRight(long n)
take(long n) & takeRight(long n)
splitAt(long n)
slice(long beginIndex, long endIndex) & sliding(long size, long step)
…

I don't see the advantage of keeping both versions.

@danieldietrich, @ruslansennov, @eduardmanas, @zsolt-donca, opinions?

also see #1024

Thanks, we should finish the task and apply it to the whole codebase consistently, as currently the long indices just cast to ints (lose-lose situation).

ps. I can't even create a 1 billion element Vector on my laptop, we should only support it, if we can test it also :/

Yes, you are aright. The trigger was the java.util.stream.Stream. It has long indices, e.g. #skip(long).
However, it is only of interest when processing long-running Streams of data I think. When in doubt, we should do it like Scala's Stream and use int, see #drop(Int).
Let's use int, if you are ok with that solution.


400TH!!!!! WOOOOOOOOOOO

PLEASE READ THE FOLLOWING

Make sure you installed the latest version of HaC Mini
Follow all the troubleshooting steps
Check the open issues and make sure it is not already reported
Delete this section from your report and continue

Describe the bug
A clear and concise description of what the bug is.
Expected behavior
A clear and concise description of what you expected to happen.
Configuration

HaC Mini version [e.g: 2.0]:
OSX version [e.g: 10.14.6]:
NUC model [e.g: NUC8i7HNK]:
Boot SSD model and protocol [e.g: Samsung EVO 860 1TB, SATA]:
Second SSD model and protocol (if installed) [e.g: HP EX920 1TB, NVMe]:
First DIMM model [e.g: Patriot DDR4-2666 16GB]:
Second DIMM model (if installed):
Display port(s) used [e.g: USB-C, mini DP]:
Display resolution(s) [e.g: 4K, 5K]:
Any TB3 devices:
Any USB devices:
Any Wi-Fi/Bluetooth devices [e.g:DW1820A, BCM94360CS2, Intel 8265]:

Modifications
List any mods to config.plist, any additional kexts, anything installed to /Library/Extensions and /System/Library/Extensions, any additional patches, etc. Please attach your config.plist if you made any modifications.


Screenshot after each step

Config: Java+TestNG+Maven
Is it possible to make a screenshot after execution of each step(method with annotation @Step)?
Thanks in advance for your reply!

Could be easily done with aspectj:
@Aspect
public class ScreenshotsAspect {
<EMAIL_ADDRESS>* your.package..*.*(..))")
	public void takeScreenshotAfterStep(final JoinPoint joinPoint) {
		attachScreenshot("After " + joinPoint.getSignature().getName() + " screenshot");
	}
}

@sskorol I've used this solution:
http://stackoverflow.com/questions/26030426/how-can-i-invoke-my-methods-before-and-after-mtd-annotated-by-step/26052783#26052783
Could you, please, tell me which solution is better?

@yarafed just ask yourself if it's reasonable to call attachment method in each step explicitly?.. or would it be better to call it implicitly via aspect?

@sskorol I am sorry, I didn't specify that I mean to use LifecycleListener. I totally agree with you that it will be not reasonable to call explicitly attachment method in each step, that's why I am trying to find a better solution.


"ructures" node type looks like a bug

The nodetypes.json file has a member named "ructures". I can't see how this snuck in by looking at the Ruby code but surely this is a bug.

There are some others like this, including "de", "ecutor", and "grefExprState". These all seem to be being pulled out of comment lines.

FWIW, this is still a thing in the 2.0.0 release.