Overriding default value makes alias go away

Bug
When overriding a default of in a child model, the alias defined in the parent is lost for the child.
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
pydantic version: 1.6.1
            pydantic compiled: True
                 install path: /Users/powerjo/dev/juice/juiceutils/.venv/lib/python3.8/site-packages/pydantic
               python version: 3.8.2 (default, Apr 14 2020, 11:26:53)  [Clang 10.0.1 (clang-1<IP_ADDRESS>)]
                     platform: macOS-10.14.6-x86_64-i386-64bit
     optional deps. installed: ['email-validator']

Example:
from pydantic import BaseModel, Field

class Parent(BaseModel):
    a: int = Field('1', alias='version_a')

class Child(Parent):
    a = 2

def test_override_default():
    parent = Parent()
    child = Child()
    assert parent.dict(by_alias=True).get('version_a') == parent.a
    assert child.dict(by_alias=True).get('version_a') == child.a

Result:
def test_override_default():
        p = Parent()
        c = Child()
        assert p.dict(by_alias=True).get('version_a') == p.a
>       assert c.dict(by_alias=True).get('version_a') == c.a
E       assert None == 2

test_ov.py:16: AssertionError

Maybe related:

https://github.com/samuelcolvin/pydantic/issues/757
https://github.com/samuelcolvin/pydantic/issues/782

I think this is the expected behaviour, I can't see any other approach that would overall be less confusing.


sampler is not in the sampler registry issue

fatal: not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Traceback (most recent call last):
  File "tools/train.py", line 200, in <module>
    main()
  File "tools/train.py", line 188, in main
    train_detector(
  File "/home/data1/my/Project/nucleiDetCls/ACFormer/ssod/apis/train.py", line 70, in train_detector
    data_loaders = [
  File "/home/data1/my/Project/nucleiDetCls/ACFormer/ssod/apis/train.py", line 71, in <listcomp>
    build_dataloader(
  File "/home/data1/my/Project/nucleiDetCls/ACFormer/ssod/datasets/builder.py", line 68, in build_dataloader
    build_sampler(sampler_cfg, default_args=default_sampler_cfg)
  File "/home/data1/my/Project/nucleiDetCls/ACFormer/ssod/datasets/builder.py", line 40, in build_sampler
    return build_from_cfg(cfg, SAMPLERS, default_args)
  File "/home/my/.conda/envs/ACFormer/lib/python3.8/site-packages/mmcv/utils/registry.py", line 61, in build_from_cfg
    raise KeyError(
KeyError: 'sampler is not in the sampler registry'

I'm not very familiar with the mechanics of mmdetection, can you help me with this?

I also have this problem, have you solved it？

Please try using distributed training script bash tools/dist_train.sh {config_file} 1 instead of using python train.py


How to handle timeout exception in guzzle ?

Hello,
Is there any official exception for handling timeout in guzzle ?
Is there any way to get tcp socket error from guzzle object ? or does curl support such a thing at all ?
I have a couple of issues with exception handling listed below:

I need a way to handle timeout exception. i know there is a ConnectException for that, but this is not really precise and requires a lot efforts to handle it. if you believe i can implement a separate Exception for timeout please help me implement that.

Second issue  is that since $e->getCode() return 0 in ConnectException and can't be used for troubleshooting and reporting. what i need is tcp socket error like
110 = Connection timed out
111 = Connection refused

"guzzlehttp/guzzle": "~6.0"
"php 7.2"
sorry for asking many questions here.

try {
  // Code
} catch(GuzzleHttp\Exception\GuzzleException $e) {
  // Handle excpetion
}

Hi, and how to handle Async Request timeout ?

try {
  // Code
} catch(GuzzleHttp\Exception\GuzzleException $e) {
  // Handle excpetion
}

That was not working for me, I just did like following code:
try{
    $this->request = $this->client->request('POST', $this->params);
    $this->response = $this->request->getBody()->getContents();
} catch (RequestException $e){
    Log::alert('Request Exception: '.$e ,[$this->params]);
}

Hope this help some body.

try {
  // Code
} catch(GuzzleHttp\Exception\GuzzleException $e) {
  // Handle excpetion
}

that was worked for me.

In PHP7, I had to use:
try {
  // Code
} catch(\GuzzleHttp\Exception\GuzzleException $e) {
  // Handle excpetion
}

In PHP7, I had to use:
try {
  // Code
} catch(\GuzzleHttp\Exception\GuzzleException $e) {
  // Handle excpetion
}

this worked for me too.

i guess the topic starter point is he wants to discriminate timeout from another errors, and same goes for me. Is there any reliable way to do that?

i guess the topic starter point is what he wants to discriminate timeout from another errors, and same goes for me. Is there any reliable way to do that?

For a timeout exception you can capture the ConnectException and inspect the exception object like this:
$exception->handlerContext->errno <-- should be 28 for cURL error 28 (timeout)


make this Happy Client Works section as  automatic  slide

Improve this section by implementing the feature of automatic sliding.
Feel Free to take this issue !!

@Vikash-8090-Yadav I would like to work on this.

@Vikash-8090-Yadav I have implemented the autoplay on slider, please have a look:
Current speed: 5s
https://user-images.githubusercontent.com/85064763/228038964-aa5369e9-9242-4435-8cae-b5c4c29c79c7.mp4

Changed speed to  4 .

And then Raise pr


[CI] Self-upgrade merging self-upgrade-master into master

Manual run of self-upgrade logic

/kind cleanup

/cherrypick release-1.16

/kind bug


AMBARI-22847. Let HBase use ZK principal name set by users when enabling Kerberos (until now it's been hardcoded to 'zookeeper')

See description in #202

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3803/
Test PASSed.


New filmstrip

⚠ PR is WIP ⚠
Thank you @cal2195 for the ffmpeg extraction code to get the images arranged horizontally and resized properly with hstack 👍
I'd love to add black bars between the screens, I suppose 3px would be the best size, do you have any preferences?
I'll try to code it up but might turn to you for help again:
https://video.stackexchange.com/questions/18419/add-black-or-other-color-padding-when-doing-vstack-or-hstack
Cheers!

Thank you for noticing the ; - I typed out the changes you've made (to show me what to do) on your copy of the branch into my branch to get a better sense of what was happening - but should have been more careful 😅 - noticed it didn't work after the commit and fixed it 👍

I think it would make the math easier with fewer bugs in the app if we extracted all images onto a standard black background with consistent size regardless of the source video aspect ratio.
I would opt for a 16:9 (~1.777) standard across all screenshots regardless of the underlying resolution. We would then only need to store a single number across the whole .vha file rather than individual widths for each video!
This would require a bit of tricky ffmpeg scripting, but seems like it's doable. We'll start with a black base background. For example, a user selects a height of 100px for all screenshots. We compute the desired output to be 100 * 1.777 = 178 and add 1px for a minimum border on each side (180px total). When extracting screenshots we'll match the height to 100px and keep the video's aspect ratio to output the video to the center of a 180px region (cropping anything that is over 178px wide).
The height (100px) and width (180px) are saved in the .vha file and every thumbnail and filmstrip preview simply uses those dimensions for computing which of the many screen-captures to show.

The upshot of this approach is that within the app we can simply show the relevant region of the horizontal strip (which will have the black bars around each image within the jpg).

I got a script to work, but it works by manually adding vertical stripes (no fun) ... would prefer to do it another way: pasting into the center a (possibly cropped) video screenshot, and attaching the output as a horizontal stack. But for now:
-ss<PHONE_NUMBER>636364 -i 'E:\Movies\someMovie.mp4' \
-ss 1622.7272727272727 -i 'E:\Movies\someMovie.mp4' \
-ss 2434.090909090909 -i 'E:\Movies\someMovie.mp4' \
-ss 3245.4545454545455 -i 'E:\Movies\someMovie.mp4' \
-frames 1 -filter_complex \
"[0:v]scale=300:-2[0]; \
color=black:5x162[0c]; \
[1:v]scale=300:-2[1]; \
color=black:5x162[1c]; \
[2:v]scale=300:-2[2]; \
color=black:5x162[2c]; \
[3:v]scale=300:-2[3]; \
[0][0c][1][1c][2][2c][3]hstack=inputs=7" \
'C:\temp\output.jpg'

There's a very similar question with a great answer on StackOverflow:
https://superuser.com/questions/547296/resizing-videos-with-ffmpeg-avconv-to-fit-into-static-sized-player

Branch now works as desired 🎉
I'll now remove previous mentions and needless computations of screenshot widths 👍
Currently there may be rounding errors (1px per scroll) when extracting screenshots not at 300px. Will fix.

Once this PR lands, this issue will be ready to work on: https://github.com/whyboris/Video-Hub-App/issues/39

⚠ Minor bug -- current branch doesn't work if the .vha file name has any spaces in it 😅
Will fix 👌

Branch now works as desired 🎉
I'll now remove previous mentions and needless computations of screenshot widths 👍
Currently there may be rounding errors (1px per scroll) when extracting screenshots not at 300px. Will fix.

This is happening for me even at 300px! 😕

Excellent! Thank you for the approval -- I'll merge this in now and get started on bug-fixing / improvement PR.
🎉


Text repeating on letter remove on LG Q6 with LG Keyboard

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
Just create a normal text field and try to write something with keyboard other than google keyboard. On google keyboard it works fine

Expected results:
I didn't wanted text to get repeat on text remove
Actual results:
I see repeated text on text remove

Logs

[ +158 ms] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +73 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[   +1 ms] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git tag --points-at 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[  +33 ms] Exit code 0 from: git tag --points-at 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[        ] 2.0.3
[  +83 ms] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +9 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git ls-remote --get-url origin
[  +11 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +106 ms] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[  +10 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[ +125 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +164 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb devices -l
[  +82 ms] List of devices attached
           LGM70035d57187         device usb:3-4 product:mh_global_com model:LG_M700 device:mh transport_id:2
[  +11 ms] /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 shell getprop
[ +214 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[  +17 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.
[ +172 ms] Skipping pub get: version match.
[ +242 ms] Generating /home/faiyyaz/AndroidStudioProjects/textfield_bug/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[ +103 ms] ro.hardware = mh
[        ] ro.build.characteristics = default
[  +72 ms] Initializing file store
[  +27 ms] Skipping target: gen_localizations
[  +12 ms] complete
[   +9 ms] Launching lib/main.dart on LG M700 in debug mode...
[  +16 ms] /home/faiyyaz/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/faiyyaz/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root
/home/faiyyaz/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --incremental --target=flutter --debugger-module-names --experimental-emit-debug-metadata
--output-dill /tmp/flutter_tools.EYBIYQ/flutter_tool.KMKCLA/app.dill --packages /home/faiyyaz/AndroidStudioProjects/textfield_bug/.dart_tool/package_config.json -Ddart.vm.profile=false
-Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-scheme org-dartlang-root --initialize-from-dill build/cache.dill.track.dill
[  +31 ms] executing: /home/faiyyaz/Android/Sdk/build-tools/30.0.3/aapt dump xmltree /home/faiyyaz/AndroidStudioProjects/textfield_bug/build/app/outputs/flutter-apk/app.apk
AndroidManifest.xml
[  +12 ms] Exit code 0 from: /home/faiyyaz/Android/Sdk/build-tools/30.0.3/aapt dump xmltree /home/faiyyaz/AndroidStudioProjects/textfield_bug/build/app/outputs/flutter-apk/app.apk
AndroidManifest.xml
[   +1 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)0x1e
               A: android:compileSdkVersionCodename(0x01010573)="11" (Raw: "11")
               A: package="com.dexter.textfield_bug" (Raw: "com.dexter.textfield_bug")
               A: platformBuildVersionCode=(type 0x10)0x1e
               A: platformBuildVersionName=(type 0x10)0xb
               E: uses-sdk (line=7)
                 A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
                 A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1e
               E: uses-permission (line=14)
                 A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
               E: application (line=16)
                 A: android:label(0x01010001)="textfield_bug" (Raw: "textfield_bug")
                 A: android:icon(0x01010002)=@0x7f080000
                 A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
                 A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
                 E: activity (line=21)
                   A: android:theme(0x01010000)=@0x7f0a0000
                   A: android:name(0x01010003)="com.dexter.textfield_bug.MainActivity" (Raw: "com.dexter.textfield_bug.MainActivity")
                   A: android:launchMode(0x0101001d)=(type 0x10)0x1
                   A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
                   A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
                   A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
                   E: meta-data (line=35)
                     A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
                     A: android:resource(0x01010025)=@0x7f0a0001
                   E: meta-data (line=45)
                     A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw: "io.flutter.embedding.android.SplashScreenDrawable")
                     A: android:resource(0x01010025)=@0x7f040000
                   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.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
                 E: meta-data (line=59)
                   A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
                   A: android:value(0x01010024)=(type 0x10)0x2
[  +24 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 shell -x logcat -v time -t 1
[  +33 ms] <- compile package:textfield_bug/main.dart
[ +212 ms] --------- beginning of main
                    03-30 12:27:09.656 D/sensors_hal_Util(  641): waitForResponse: timeout=0
[  +47 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb version
[  +13 ms] Android Debug Bridge version 1.0.41
           Version 31.0.1-7187441
           Installed as /home/faiyyaz/Android/Sdk/platform-tools/adb
[   +6 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb start-server
[  +13 ms] Building APK
[  +42 ms] Running Gradle task 'assembleDebug'...
[   +7 ms] Using gradle from /home/faiyyaz/AndroidStudioProjects/textfield_bug/android/gradlew.
[  +11 ms] /home/faiyyaz/AndroidStudioProjects/textfield_bug/android/gradlew mode: 33277 rwxrwxr-x.
[  +13 ms] executing: [/home/faiyyaz/AndroidStudioProjects/textfield_bug/android/] /home/faiyyaz/AndroidStudioProjects/textfield_bug/android/gradlew -Pverbose=true
-Ptarget-platform=android-arm -Ptarget=/home/faiyyaz/AndroidStudioProjects/textfield_bug/lib/main.dart -Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root assembleDebug
[+1557 ms] Welcome to Gradle 6.7!
[        ] Here are the highlights of this release:
[  +32 ms]  - File system watching is ready for production use
[  +10 ms]  - Declare the version of Java your build requires
[        ]  - Java 15 support
[        ] For more details see https://docs.gradle.org/6.7/release-notes.html
[+6429 ms] > Task :app:compileFlutterBuildDebug
[        ] [ +187 ms] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [  +77 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [        ] 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[        ] [   +1 ms] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git tag --points-at 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[        ] [  +27 ms] Exit code 0 from: git tag --points-at 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[        ] [        ] 2.0.3
[        ] [  +83 ms] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[        ] [  +14 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] [        ] origin/stable
[   +1 ms] [        ] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git ls-remote --get-url origin
[        ] [  +16 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] [        ] https://github.com/flutter/flutter.git
[   +6 ms] [ +129 ms] executing: [/home/faiyyaz/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[   +7 ms] [  +15 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] [        ] stable
[   +1 ms] [ +109 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +7 ms] [        ] 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.
[        ] [ +114 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] 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.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'PubDependencies' is not required, skipping update.
[ +150 ms] [ +257 ms] Initializing file store
[ +100 ms] [  +54 ms] Skipping target: gen_localizations
[        ] [  +23 ms] kernel_snapshot: Starting due to {}
[        ] [  +34 ms] /home/faiyyaz/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/faiyyaz/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root
/home/faiyyaz/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --target=flutter --no-print-incremental-dependencies -Ddart.vm.profile=false
-Ddart.vm.product=false --enable-asserts --track-widget-creation --no-link-platform --packages /home/faiyyaz/AndroidStudioProjects/textfield_bug/.dart_tool/package_config.json
--output-dill /home/faiyyaz/AndroidStudioProjects/textfield_bug/.dart_tool/flutter_build/002748c60d234324e05a0d1c56384c6b/app.dill --depfile
/home/faiyyaz/AndroidStudioProjects/textfield_bug/.dart_tool/flutter_build/002748c60d234324e05a0d1c56384c6b/kernel_snapshot.d package:textfield_bug/main.dart
[+22698 ms] [+22683 ms] kernel_snapshot: Complete
[ +899 ms] [ +906 ms] debug_android_application: Starting due to {}
[ +699 ms] [ +653 ms] debug_android_application: Complete
[ +900 ms] [ +970 ms] Persisting file store
[ +100 ms] [  +16 ms] Done persisting file store
[        ] [   +8 ms] build succeeded.
[        ] [  +23 ms] "flutter assemble" took 25,799ms.
[        ] [   +7 ms] ensureAnalyticsSent: 0ms
[        ] [   +2 ms] Running shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [        ] exiting with code 0
[ +397 ms] > Task :app:packLibsflutterBuildDebug
[        ] > Task :app:preBuild UP-TO-DATE
[        ] > Task :app:preDebugBuild UP-TO-DATE
[        ] > Task :app:compileDebugAidl NO-SOURCE
[        ] > Task :app:compileDebugRenderscript NO-SOURCE
[  +97 ms] > Task :app:generateDebugBuildConfig
[ +301 ms] > Task :app:checkDebugAarMetadata
[        ] > Task :app:cleanMergeDebugAssets
[        ] > Task :app:mergeDebugShaders
[        ] > Task :app:compileDebugShaders NO-SOURCE
[   +1 ms] > Task :app:generateDebugAssets UP-TO-DATE
[  +95 ms] > Task :app:mergeDebugAssets
[ +299 ms] > Task :app:copyFlutterAssetsDebug
[        ] > Task :app:generateDebugResValues
[        ] > Task :app:generateDebugResources
[+1299 ms] > Task :app:createDebugCompatibleScreenManifests
[        ] > Task :app:extractDeepLinksDebug
[  +99 ms] > Task :app:mergeDebugResources
[ +200 ms] > Task :app:processDebugMainManifest
[  +99 ms] > Task :app:processDebugManifest
[        ] > Task :app:processDebugManifestForPackage
[ +699 ms] > Task :app:processDebugResources
[+2899 ms] > Task :app:compileDebugKotlin
[   +1 ms] > Task :app:mergeDebugNativeDebugMetadata NO-SOURCE
[        ] > Task :app:javaPreCompileDebug
[ +598 ms] > Task :app:compileDebugJavaWithJavac
[  +14 ms] > Task :app:compileDebugSources
[        ] > Task :app:processDebugJavaRes NO-SOURCE
[ +588 ms] > Task :app:checkDebugDuplicateClasses
[ +196 ms] > Task :app:dexBuilderDebug
[  +99 ms] > Task :app:mergeDebugJniLibFolders
[ +100 ms] > Task :app:desugarDebugFileDependencies
[ +200 ms] > Task :app:compressDebugAssets
[  +99 ms] > Task :app:validateSigningDebug
[ +199 ms] > Task :app:mergeDebugJavaResource
[+1409 ms] > Task :app:mergeExtDexDebug
[+1790 ms] > Task :app:mergeDebugNativeLibs
[        ] > Task :app:mergeDexDebug
[ +599 ms] > Task :app:stripDebugDebugSymbols
[        ] Unable to strip the following libraries, packaging them as they are: libflutter.so.
[+4398 ms] > Task :app:packageDebug
[+1400 ms] > Task :app:assembleDebug
[ +100 ms] Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
[        ] Use '--warning-mode all' to show the individual deprecation warnings.
[        ] See https://docs.gradle.org/6.7/userguide/command_line_interface.html#sec:command_line_warnings
[        ] BUILD SUCCESSFUL in 51s
[        ] 32 actionable tasks: 32 executed
[ +899 ms] Running Gradle task 'assembleDebug'... (completed in 52.8s)
[ +565 ms] calculateSha: LocalDirectory: '/home/faiyyaz/AndroidStudioProjects/textfield_bug/build/app/outputs/flutter-apk'/app.apk
[  +44 ms] calculateSha: reading file took 42us
[+1173 ms] calculateSha: computing sha took 1172us
[   +8 ms] ✓ Built build/app/outputs/flutter-apk/app-debug.apk.
[   +8 ms] executing: /home/faiyyaz/Android/Sdk/build-tools/30.0.3/aapt dump xmltree /home/faiyyaz/AndroidStudioProjects/textfield_bug/build/app/outputs/flutter-apk/app.apk
AndroidManifest.xml
[  +61 ms] Exit code 0 from: /home/faiyyaz/Android/Sdk/build-tools/30.0.3/aapt dump xmltree /home/faiyyaz/AndroidStudioProjects/textfield_bug/build/app/outputs/flutter-apk/app.apk
AndroidManifest.xml
[   +1 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)0x1e
               A: android:compileSdkVersionCodename(0x01010573)="11" (Raw: "11")
               A: package="com.dexter.textfield_bug" (Raw: "com.dexter.textfield_bug")
               A: platformBuildVersionCode=(type 0x10)0x1e
               A: platformBuildVersionName=(type 0x10)0xb
               E: uses-sdk (line=7)
                 A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
                 A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1e
               E: uses-permission (line=14)
                 A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
               E: application (line=16)
                 A: android:label(0x01010001)="textfield_bug" (Raw: "textfield_bug")
                 A: android:icon(0x01010002)=@0x7f080000
                 A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
                 A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
                 E: activity (line=21)
                   A: android:theme(0x01010000)=@0x7f0a0000
                   A: android:name(0x01010003)="com.dexter.textfield_bug.MainActivity" (Raw: "com.dexter.textfield_bug.MainActivity")
                   A: android:launchMode(0x0101001d)=(type 0x10)0x1
                   A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
                   A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
                   A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
                   E: meta-data (line=35)
                     A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
                     A: android:resource(0x01010025)=@0x7f0a0001
                   E: meta-data (line=45)
                     A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw: "io.flutter.embedding.android.SplashScreenDrawable")
                     A: android:resource(0x01010025)=@0x7f040000
                   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.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
                 E: meta-data (line=59)
                   A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
                   A: android:value(0x01010024)=(type 0x10)0x2
[   +3 ms] Stopping app 'app.apk' on LG M700.
[   +1 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 shell am force-stop com.dexter.textfield_bug
[ +177 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 shell pm list packages com.dexter.textfield_bug
[+1477 ms] Installing APK.
[   +5 ms] Installing build/app/outputs/flutter-apk/app.apk...
[   +1 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 install -t -r /home/faiyyaz/AndroidStudioProjects/textfield_bug/build/app/outputs/flutter-apk/app.apk
[+7930 ms] Performing Streamed Install
                    Success
[        ] Installing build/app/outputs/flutter-apk/app.apk... (completed in 7.9s)
[   +2 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 shell echo -n 95b814ae9fb3dada4eef5ff542a4a72af904627f >
/data/local/tmp/sky.com.dexter.textfield_bug.sha1
[ +107 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 shell -x logcat -v time -t 1
[ +151 ms] --------- beginning of main
                    03-30 12:28:18.390 I/Finsky  (13800): [1096] qre.run(16): Wrote row to frosting DB: 8383
[  +19 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 shell am start -a android.intent.action.RUN -f 0x20000000 --ez enable-background-compilation true
--ez enable-dart-profiling true --ez enable-checked-mode true --ez verify-entry-points true com.dexter.textfield_bug/com.dexter.textfield_bug.MainActivity
[ +225 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.dexter.textfield_bug/.MainActivity (has extras) }
[        ] Waiting for observatory port to be available...
[+1962 ms] Observatory URL on device: http://<IP_ADDRESS>:53892/jRLsIF3R25Q=/
[   +1 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 forward tcp:0 tcp:53892
[  +14 ms] 44875
[        ] Forwarded host port 44875 to device port 53892 for Observatory
[  +10 ms] Caching compiled dill
[ +333 ms] Connecting to service protocol: http://<IP_ADDRESS>:44875/jRLsIF3R25Q=/
[ +907 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at http://<IP_ADDRESS>:44875/jRLsIF3R25Q=/.
[ +360 ms] DDS is listening at http://<IP_ADDRESS>:43953/KiY0Ca6ZzcY=/.
[ +150 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:44875/jRLsIF3R25Q=/
[ +853 ms] DevFS: Creating new filesystem on the device (null)
[ +103 ms] DevFS: Created new filesystem on the device (file:///data/user/0/com.dexter.textfield_bug/code_cache/textfield_bugALFSMQ/textfield_bug/)
[  +18 ms] Updating assets
[ +150 ms] Syncing files to device LG M700...
[   +3 ms] <- reset
[        ] Compiling dart to kernel with 0 updated files
[   +3 ms] <- recompile package:textfield_bug/main.dart 9be88a68-78e1-4376-a367-ef5cf7c581c8
[        ] <- 9be88a68-78e1-4376-a367-ef5cf7c581c8
[ +282 ms] Updating files.
[        ] DevFS: Sync finished
[   +5 ms] Syncing files to device LG M700... (completed in 292ms)
[   +2 ms] Synced 0.0MB.
[   +3 ms] <- accept
[  +21 ms] Connected to _flutterView/0xa5a6c010.
[   +4 ms] Flutter run key commands.
[   +7 ms] r Hot reload. 🔥🔥🔥
[   +3 ms] R Hot restart.
[   +1 ms] h Repeat this help message.
[   +1 ms] d Detach (terminate "flutter run" but leave application running).
[        ] c Clear the screen
[        ] q Quit (terminate the application on the device).
[        ] An Observatory debugger and profiler on LG M700 is available at: http://<IP_ADDRESS>:43953/KiY0Ca6ZzcY=/
[   +1 ms]
           Flutter DevTools, a Flutter debugger and profiler, on LG M700 is available at: http://<IP_ADDRESS>:9101?uri=http%3A%2F%2F<IP_ADDRESS>%3A43953%2FKiY0Ca6ZzcY%3D%2F
[        ] Running with unsound null safety
[        ] For more information see https://dart.dev/null-safety/unsound-null-safety
[+2034 ms] I/ViewRootImpl(19719): ViewRoot's Touch Event : ACTION_DOWN
[ +176 ms] I/ViewRootImpl(19719): ViewRoot's Touch Event : ACTION_UP
[+10810 ms] I/zygote  (19719): Do partial code cache collection, code=31KB, data=30KB
[   +1 ms] I/zygote  (19719): After code cache collection, code=31KB, data=30KB
[        ] I/zygote  (19719): Increasing code cache capacity to 128KB
[+8370 ms] I/zygote  (19719): Do partial code cache collection, code=61KB, data=55KB
[   +2 ms] I/zygote  (19719): After code cache collection, code=61KB, data=55KB
[   +1 ms] I/zygote  (19719): Increasing code cache capacity to 256KB
[+9580 ms] I/ViewRootImpl(19719): ViewRoot's KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=6242541, downTime=6242541,
deviceId=-1, source=0x101 } to DecorView@b21479c[MainActivity]
[  +82 ms] I/ViewRootImpl(19719): ViewRoot's KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=6242625, downTime=6242541,
deviceId=-1, source=0x101 } to DecorView@b21479c[MainActivity]
[  +59 ms] I/zygote  (19719): Do full code cache collection, code=125KB, data=96KB
[   +4 ms] I/zygote  (19719): After code cache collection, code=120KB, data=81KB
[ +297 ms] I/ViewRootImpl(19719): ViewRoot's KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=6242989, downTime=6242989,
deviceId=-1, source=0x101 } to DecorView@b21479c[MainActivity]
[   +4 ms] I/AudioManagerEx(19719): AudioManagerEx created
[  +60 ms] I/ViewRootImpl(19719): ViewRoot's KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=6243056, downTime=6242989,
deviceId=-1, source=0x101 } to DecorView@b21479c[MainActivity]
[ +471 ms] W/InputMethodManager(19719): APP_CALLED_RESTART_INPUT_API  failed. Window focus may have already been lost. win=null view=io.flutter.embedding.android.FlutterView{24e4d7a
VFE...... .F....I. 0,0-1080,2004},focus=true,windowFocus=false,window=android.view.ViewRootImpl$WEx@d4e592b,temporaryDetach=false
[   +2 ms] W/InputMethodManager(19719): force mHasBeenInactive = true
[  +34 ms] E/libEGL  (19719): call to OpenGL ES API with no current context (logged once per thread)
[+77128 ms] Service protocol connection closed.
[        ] Lost connection to device.
[   +3 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 forward --list
[  +11 ms] Exit code 0 from: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 forward --list
[        ] LGM70035d57187 tcp:44875 tcp:53892
[   +3 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 forward --remove tcp:44875
[  +20 ms] DevFS: Deleting filesystem on the device (file:///data/user/0/com.dexter.textfield_bug/code_cache/textfield_bugALFSMQ/textfield_bug/)
[ +256 ms] Ignored error while cleaning up DevFS: TimeoutException after 0:00:00.250000: Future not completed
[   +5 ms] executing: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 forward --list
[  +16 ms] Exit code 0 from: /home/faiyyaz/Android/Sdk/platform-tools/adb -s LGM70035d57187 forward --list
[   +3 ms] "flutter run" took 1,81,144ms.
[ +171 ms] ensureAnalyticsSent: 161ms
[   +3 ms] Running shutdown hooks
[        ] Shutdown hook priority 4
[   +7 ms] Shutdown hooks complete
[        ] exiting with code 0

Analyzing textfield_bug...
No issues found! (ran in 29.3s)

[✓] Flutter (Channel stable, 2.0.3, on Linux, locale en_IN)
    • Flutter version 2.0.3 at /home/faiyyaz/snap/flutter/common/flutter
    • Framework revision 4d7946a68d (11 days ago), 2021-03-18 17:24:33 -0700
    • Engine revision 3459eb2436
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /home/faiyyaz/Android/Sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /usr/bin/java
    • Java version Java(TM) SE Runtime Environment (build 1.8.0_261-b12)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

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

[✓] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at /home/faiyyaz/Personal/idea-IC-203.7717.56
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] Connected device (2 available)
    • LG M700 (mobile) • LGM70035d57187 • android-arm    • Android 8.1.0 (API 27)
    • Chrome (web)     • chrome         • web-javascript • Google Chrome 89.0.4389.90

! Doctor found issues in 1 category.

Attaching bug video and zip file for main.dart file
https://user-images.githubusercontent.com/69201999/112947512-846dc980-9154-11eb-8984-a4a6e422c209.mp4
main.dart.zip

I cannot reproduce this on Xiaomi device. Since I don't have the mentioned device, this needs further investigation.

code sample
import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({this.title});

  final String? title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title!),
      ),
      body: Center(
        child: TextField(),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.3, on macOS 11.2.3 20D91 darwin-x64, locale en-AO)
    • Flutter version 2.0.3 at /Users/pedromassango/Code/flutter_stable
    • Framework revision 4d7946a68d (11 days ago), 2021-03-18 17:24:33 -0700
    • Engine revision 3459eb2436
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/pedromassango/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 54.0.3
    • Dart plugin version 203.7759

[✓] VS Code (version 1.54.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (3 available)
    • iPhone 12 Pro Max (mobile) • AE2F4F51-880E-44FB-BB29-171B766D9B54 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-4 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • macOS 11.2.3 20D91 darwin-x64
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 89.0.4389.90

! Doctor found issues in 1 category.

CC @justinmc

@justinmc Yes this works fine on master channel. Can i have some estimated timeline when this will be merged to the stable branch?

I'll close this since it's fixed on master.
Maybe a month until it ends up on stable?  You can look at the releases here to get some idea: https://flutter.dev/docs/development/tools/sdk/releases


fix: handle "Invalid config property" log for "ai config get ..." cmd

I noticed that when a user attempts to set an invalid property in the config, they receive an error response from the cli, however, when the user tries to config get non-existed property - there is silence, so I thought we could be consistent here

This is great, thanks @georgesstein!


Add manual steps

This proposal outlines the addition of a manual step type.
RFC written as requested in concourse/concourse#3265.

Good to see this RFC. I also received a number of user asks for manual steps, because many users have Jenkins experience, and Jenkins has such functionality. I may consider to help implement this feature if I get some bandwidth.

Wonders if this is progressing further? 🙇 🤔

Re. @vito :

Just to be upfront, and I believe I'm preaching to the choir here based on some of your review comments, I think Concourse's strength is in being a continuous thing-doer, and we should avoid turning it into a general GUI driver for executing workloads interactively. It's more designed around "give me a declarative config which describes your total workflow and I'll connect the dots" - while making a conscious effort to not have Concourse be a mission-critical part of the workflow.

100%.

That being said, I think it would be more Concoursey to have an external record of who approved what and when, from the standpoint that Concourse should never be the source of truth - it's the dot connector, not the dot. I understand that this approach is painful and awkward to implement in practice right now, but I would like to unpack the specifics there just to make sure we're at our wit's end and we really just need to add a manual step after all.
I think the downside of this approach is it requires you to have some sort of external mechanism for approval, but there's at least some evidence that that is a common case, and this might be one of those things where Concourse forces you to "do the right thing" - which may feel heavy on day 1, but may pay off on day 1000 when you really need to figure out who OK'd the build on August 24, 2017 and you've since migrated your pipelines to a different Concourse instance altogether.
There are a few other benefits to it - externalizing the approval also lets "who can approve" be configured elsewhere, rather than requiring RBAC in Concourse. It also lets whoever's doing the approval stay in an appropriate context - such as replying to an e-mail or a Slack thread - rather than diving into a Concourse pipeline and clicking a button, which may feel awkward for folks who's only role in a pipeline is to approve things. I'm just theorycrafting here, though.
I would imagine viewing a build that's waiting for approval and then having to go over to Slack would be annoying. Maybe that could be addressed by still allowing approval through the Concourse UI, but then recording that action through some other event so that it can still be logged in the external service.

Permit me to tell a short story: once upon a time, I was a contractor, and I was doing some work for a bank. The bank had software that kept track of approvals from management for workflow like deploying to production. It was off-the-shelf from some BigEnterpriseSoftwareVendorCo and I honestly can't remember the name of it, but I do remember that everyone hated that software. That software was both bureaucratically impossible to make changes to (as it was an integral part of the bank's compliance workflow), technically impossible to make changes to (old, no open documentation, no documented API, etc.), and scapegoated the frustrations of people who work in big bank environments (needing a zillion approvals to do simple tasks). I'm sure, as any other piece of corporate IT, that software represented its own operational complexity - web servers, a load balancer, a database, monitoring, SSO login, etc.
For the sake of argument, let's say that a Concourse user who wishes to configure a pipeline wants such an external approval system, Foo to control manual approvals for resuming a pipeline. Well, that's easily modeled in Concourse today, with two resource types: a FooRequestApproval resource, which with put/out creates a request for approval in the external approval system, and a resource type FooRequireApproval, which uses the check, get/in mechanisms to poll the external system for approvals and only provide a new Concourse resource version when the necessary approval has been issued.
As an added bonus, this system does even more than what you suggested - as a dedicated system, it can provide its own rules engine, its own notifications, its own audit trail, etc. It will necessarily be much more powerful than anything Concourse could provide.
So my question is this: do you know of any systems like this that could be pointed to for people who need to implement this pattern? Something that's relatively easy for small teams to set up and maintain for the "simple" use-case (i.e. reviewing automatically generated output), but powerful enough for big enterprise teams as their needs grow and compliance becomes a genuine business concern? Even if it doesn't have Concourse resources yet (hopefully it wouldn't be too difficult to create a third-party resource, as long as the API is well-documented)? Maybe available as a SaaS so that we don't have to run the infrastructure ourselves?

So, I guess what I'm asking is this: do you value having a history of who approved what and when, and does your workflow currently involve a service that could be used for such a thing? Following that, would that workflow feel natural or more like a constant burden?

We don't even keep a durable build history. We set up our Concourse instance such that, if our Concourse instance blew up, we run a script and it sets everything back up for us, soup to nuts - deploying Concourse on Kubernetes, creating teams, setting up auth, setting up credential managers (including populating the credential managers with secrets), running a bootstrap pipeline that sets up all of the other pipelines in the system. Nobody really cares about build history because all of our pipelines are set up with idempotent-only operations in mind following a GitOps model - if something is screwed up, just re-run, and it either fixes the issue or reproduces it for you in a fresh build log. So we run PostgreSQL in a Kubernetes pod on commodity nodes, with no backups. We take the risk of being down for a few hours to give everything time to run, but that's fine with us for now.... actually, it's been fine for us for two years and counting. #yolo
We couldn't care less of keeping track of approvals and the idea of having to set up an entirely separate system to keep durable track of approvals sounds like an anti-pattern to me, considering the rest of how our infrastructure is set up.
Regarding auditing approvals, I recall touching upon the potential for Concourse to add better support for audit sinks, at least here: https://github.com/concourse/rfcs/pull/41#discussion_r357562300 but I'm sure the question has come up elsewhere. If Concourse had better support for external audit sinks in general (also sending more information than what's available in current audit logs) then such support would probably naturally support the kind of auditing needs that you foresee needing in a manual approval.

Thanks again! And sorry for the wall of text. sweat_smile

I seem to have repaid you in kind :sweat_smile: Thanks for taking the time to review the RFC!

@vito the point about the value of an external state store for approvals made me think about another point -
Why does Concourse have a Postgres database to begin with? To keep track of pipeline configurations, build coordination, and build logs, more or less?
Allow me to draw a hypothetical:

All of Concourse's pipelines, team configurations, etc. are all defined in some configuration file. Concourse starts, pointing to this configuration file, and from it assembles all of the pipelines, teams, etc. Changes can be made by changing the configuration file and sending SIGHUP. For highly available setups, the file can instead be put in an object bucket somewhere.
Build coordination is stored in etcd / Raft-protocol distributed consensus
Instead of storing build logs in a Postgres database, instead allow pipelines to declare a "build log sink" which sends the build logs somewhere. This allows the user to choose to send the logs anywhere from a Postgres database (what's currently done), to an object store (after the build is completed, it's basically just an object), to an Elasticsearch cluster (better for indexing and searching logs), to /dev/null (user doesn't care about log persistence).

If you think this has merit, I can write it up in a separate RFC... this one isn't the place to debate it. The point I wish to raise with this hypothetical is, as long as Concourse maintains state internally at all, whether the scope of that state should be expanded to support a given feature (say, manual steps) becomes debatable, as it essentially represents an attempt to get a "bang for the buck" simple implementation, in the way that storing build logs in Postgres is "good enough" for most use-cases. If a design goal of Concourse is to reduce the amount of state which Concourse itself is responsible for, then perhaps we should have more interesting RFCs on the reduction in the scope of state - like build log sinks.

@ari-becker PostgreSQL is a bit of a compromise for making Concourse easy to use out-of-the-box. There's all sorts of cool tech we could utilize but I don't want to scare folks away who just want an open-source CI solution that's easy to deploy and use for side projects. Some folks even complain about the Postgres dependency, since Jenkins doesn't need such a thing. 😆
To me the most risky state we store in Postgres is pinned / disabled versions and paused jobs, but I don't know where else we could really put that information. 🤷 They're what I'd classify as "emergent state" in that pipeline operators sometimes need to be able to quickly pull the trigger on them, but it would be a lot closer to our ideals if we had some way to tie them to a source of truth.
I'd be very interested in hashing out an RFC about your first point. I think it would eliminate a lot of the need for a public HTTP API, since a lot of the demand seems to be centered around configuring Concourse. The more we can make Concourse self-configuring, the closer we can get to pipelines (or more generally, build plans) as the only API to worry about. I talked about that in https://github.com/concourse/concourse/issues/3208 which I see you were also active in.
Re: build log sinks, it's probably worth checking out @aoldershaw's RFC: https://github.com/concourse/rfcs/pull/53 - and associated PR: https://github.com/concourse/concourse/pull/5651

@ari-becker PostgreSQL is a bit of a compromise for making Concourse easy to use out-of-the-box. There's all sorts of cool tech we could utilize but I don't want to scare folks away who just want an open-source CI solution that's easy to deploy and use for side projects. Some folks even complain about the Postgres dependency, since Jenkins doesn't need such a thing. laughing

For what it's worth, running a static binary by itself is strictly less complex than running a static binary and a database. I'm not saying that Jenkins is better, it's much worse, but I would think that finding a way to run Concourse without the database would only make it easier to use out-of-the-box.

To me the most risky state we store in Postgres is pinned / disabled versions and paused jobs, but I don't know where else we could really put that information. shrug They're what I'd classify as "emergent state" in that pipeline operators sometimes need to be able to quickly pull the trigger on them, but it would be a lot closer to our ideals if we had some way to tie them to a source of truth.

I would look to Kubernetes and kubectl for inspiration here. It's a really bad anti-pattern for client code to be able to touch the database directly, and I don't think anybody would suggest that users should write SQL directly to pause/unpause pipelines or enable/disable/pin versions. But what Kubernetes did with manifests is to essentially expose most of the relevant bits of the etcd database to the user directly (working through the API server mostly as a secure proxy), therefore making it more explicit to the user what was happening, and therefore making it clear that the "quick-trigger-pull" way of doing things was not the only way of doing them.
What I'm trying to refer to by that is, let's say that I want to scale a Kubernetes deployment. On the one hand, I can execute kubectl scale deployment/example --replicas=5. This is the "quick-trigger-pull" way of scaling a deployment, and it's similar to quickly executing fly pause-pipeline etc. However, that's not the only way to scale a Kubernetes deployment. I can also edit the manifest itself:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: example
spec:
  replicas: 5
  # most fields omitted

and indeed, the only thing that actually happens when I call kubectl scale deployment/example --replicas=5 is an editing of the underlying manifest.
I point this out because, if pipeline manifests looked something like the following:
paused: false
resources:
- name: example
  versions:
    pinned: { hash: foo }
    disabled:
    - hash: bar
jobs:
- name: baz
  paused: true

then I think that you'd find that the problem more-or-less solves itself in the same way as Kubernetes manifests.

I'd be very interested in hashing out an RFC about your first point. I think it would eliminate a lot of the need for a public HTTP API, since a lot of the demand seems to be centered around configuring Concourse. The more we can make Concourse self-configuring, the closer we can get to pipelines (or more generally, build plans) as the only API to worry about. I talked about that in concourse/concourse#3208 which I see you were also active in.

Cool, I'll start writing something up... might take me some time though.

Re: build log sinks, it's probably worth checking out @aoldershaw's RFC: #53 - and associated PR: concourse/concourse#5651

I went ahead and added some comments on the RFC :)

I'd be very interested in hashing out an RFC about your first point. I think it would eliminate a lot of the need for a public HTTP API, since a lot of the demand seems to be centered around configuring Concourse. The more we can make Concourse self-configuring, the closer we can get to pipelines (or more generally, build plans) as the only API to worry about. I talked about that in concourse/concourse#3208 which I see you were also active in.

For the sake of bookkeeping on this post (as I've reached out to you separately and I know you already know about it), the RFC is up here: https://github.com/concourse/rfcs/pull/59

I'm cleaning up my old open PRs. This hasn't gone anywhere, so I'll close it.
I would be happy to re-open if someone thinks I should.


SWC-6644

In the user react-select component, make the following changes:

Do not pop up the options when the textbox is selected (openMenuOnClick={false})
Instead of the default placeholder text ("Select..."), always set the placeholder text to something meaningful based on the TYPE_FILTER.
Only run the useSearchUserGroupHeaders if user input has been defined.

Before:
https://github.com/Sage-Bionetworks/synapse-web-monorepo/assets/1864447/29de2b40-0107-462c-a8a4-34a8ac06923f
After:
https://github.com/Sage-Bionetworks/synapse-web-monorepo/assets/1864447/39807097-1a4c-459a-aeab-0cad7da34924


Subharmonic oscillation on +12V power supply

PCB rev. A's LM5141 +12V power supply shows subharmonic oscillation with ~13.5V in, ~12-12.2V out, ~2.5A out to blower (TKFAN BA7050H12B).  Waveforms @ https://docs.google.com/document/d/1YLGYWPdSB4p-uytQrrjSSuHdnbYHyTh2L5PIqJrbATQ/edit#heading=h.xnnb3lnoe97w
Doesn't cause any major downstream issues except couple hundred mV of ripple on +12V rail.
@inceptionev did some testing earlier with an eval. board (not sure whether it was LM5141 or bq24773) and saw no issues; would be useful to compare test conditions.
Will try programming higher VLink voltage to decrease duty cycle and see if that helps (even though it shouldn't be quite reaching the min. 100 ns off-time as-is).

Control signals on LM5141 that could be observed for clues/could be picking up noise:
[ ] Dither (pin 5), try tying to VDDA (pin 2) to disable
[ ] Over-current restart timer (pin 24), try tying to VDD to disable
[ ] Fbk (pin 19), with its gnd connection near the path of the return currents on gnd plane? cap coupling from nearby large sw node?  Could try adding a parallel cap from R212/R213/R214 to C140's AGND, 33 pF at most for ~500 kHz LPF, shouldn't affect loop much but may help filter any spikes from switching transitions.
[ ] Comp (pin 20), with a potentially-large-loop-area return trace for AGND / pickup from nearby input current loop?
[ ] Soft start (pin 22), same?
[ ] Current sense (pins 17, 18), with its long multi-layer run, breaking up gnd? (can't measure directly)
[ ] Timing resistor (pin 4), although trace isn't very long and has fairly direct connection to AGND pin? (least likely)

With 15.1V VLink and both DITH and RES disabled, can see both the occasional large subharmonic oscillations, but also frequent small ones as well (of roughly 5% pp):

For comparison, the bq24773 (VLink) converter's duty cycle is far more stable cycle-to-cycle, with variations appearing mostly random and being under 1%:

Control loop calculations (based on LM5141 datasheet p.31-33, don't entirely trust because of Rcs not being separated from inductor's DCR in modulator gain, and because it doesn't match TI's calculator spreadsheet) with populated compensation component values show stability ok, >50° phase margin with crossover in the 10 kHz ballpark, >20 dB gain margin.

TI's LM5141 calculations spreadsheet shows plenty of stability as well with 1.6A out:

Tried simulating with TI's PSPICE model and testbench schematic (with values changed to match our circuit), to examine the effects of different compensation values on load step response, but even steady-state in simulation (with 1.6A resistive load) shows massive subharmonic instability once startup ends and the peak-current-setpoint drops:

This obviously doesn't happen in real life, so

In summary, haven't learned anything new, except:
Control loop stability (at least calculated) is great and not a problem
Don't trust the TI simulation model of the LM5141
Don't trust the LM5141 datasheet's control loop calculations either

Replacing fan with 0.75A (9W) dummy load doesn't help: has a different pattern of subharmonic oscillation, plus measurable duty cycle changes:

Bootstrap cap (C146) voltage doesn't seem to be a problem, high side of it stays ~5V over the switch node:

Slope compensation seems fine, based on TI's LM5141 calculator spreadsheet: slope compensation's slope is > 1/2 of the falling slope, so shouldn't be a risk of subharmonic oscillation based on >50% duty cycle alone (noise getting into control may be another issue): with slope comp > falling slope it's actually looking more like a voltage-mode converter than anything else.

Simulation more accurate than previously believed (matches measurements with dummy load): shows the converter passing through DCM during startup, and getting stuck in every-other-cycle DCM instead of transitioning to CCM.  This is due to un-analyzed separate subharmonic stability criteria in DCM.

Adjusting compensation value or increasing inductor value doesn't help, but swapping R203 and R204 to disable diode emulation mode (and instead force CCM with negative-current valleys @ light load) solves the problem both in simulation and on the bench.    Adjusting the loop compensation to more reasonable values, either (6.49K + 2.7nF) || 1nF, or (22.6K + 3.3nF) || 1nF, doesn't change this.  However, neither simulation nor bench measurements show any problematic interactions with the blower's 7-8 kHz current draw, such as large duty cycle swings that approach the off-time limits (95.6% @ 440 kHz).


[Bug] Error opening fixed-layout publications

Describe the bug
When opening fixed-layouts such as Comic Books the reader does not display the epub. Just a blank screen.
Happens with all fixed-layout titles we've tested.
🔎 EPUBSpreadView.swift:152: Evaluate script: spread.load([{"link":{"href":"OEBPS/cover.xhtml","properties":{"encrypted":{"algorithm":"http://www.w3.org/2001/04/xmlenc#aes256-cbc","compression":"deflate","originalLength":494,"scheme":"http://readium.org/2014/01/lcp"},"id":"cover"},"templated":false,"type":"application/xhtml+xml"},"page":"left","url":"http://localhost:63381/F6BD61BE-7DF1-4B49-A41A-56CE0645265E/OEBPS/cover.xhtml"}]);

❌ undefined:1:	JavaScript: ReferenceError: Can't find variable: readium

How to reproduce?

Download fixed-layout lcp epub
Open the publication

Xcode version
15.4 (15F31d)
Readium version
3.0.0-alpha.1
OS version
17.5.1
Testing device
iPhone 14 Pro
Environment
No response
Additional context
No response

Could you try again from develop and confirm that it fixes the problem for you? Thanks!

Hello, now we are using Xcode 16.1 and have just  updated to 3.0.0-alpha.3.
But we keep facing the same problem with fixed layouts. Except this time it's only this line:
❌ undefined:1:	JavaScript: ReferenceError: Can't find variable: readium
Our fixed layouts are .epub files with lcp drm protection.
Thanks!


k8s: add statefulset probe

to enable use:
k8s:
  probes:
  - statefulset

to create resource use:
kubectl create -f tests/k8s/statefulset.yaml

@lebauce / @safchain - please review/merge

@hunchback Don't worry, we do receive notifications from Github :-)

@hunchback Please rebase


Documented the Tree column behaviour of min_width in conjunction with expand

Might close pull request #30399 and issue #30233
The differences between the current behaviour and that in pull request #30399 only really seem to come into play when the tree has been resized to be small enough that the min-sizes cause a horizontal scrollbar to appear, versus getting sized down to almost nothing (if ratios are in use and min_size is low).

Thanks!

Cherry-picked for 3.1.2.


Compatibility with IE

Problem Description
The lib doesn't seem to support IE (10 or 11). I couldn't find any information about compatibility in the README.
Code Snippet(s) or Codepen (http://codepen.io/tannerlinsley/pen/QpeZBa?editors=0010)
Steps to Reproduce

Take the link of the Codepen demo
Open it in IE 10 or IE 11

System Information

Browser & Browser Version: IE 10 and IE 11
Node Version:
OS Version: Windows 10 pro
NPM Version:
Yarn Version:

Looks like some polyfills are missing for IE11. Now it fails with: "Object doesn't support property or method 'find'".

Really need help here.. Did this used to work with ie11?

@kolbeypruitt: According to #105, it used to work. @tannerlinsley said in #171 that he doesn't guarantee support for ie, but he seems concerned with the compatibility issue (#240). If it's only a matter of a few polyfills, I think it wouldn't take too much time to fix it, but would be useful to several people.

I am currently using the Table for a project with IE10 and IE11 support. To make the table work you have to provide a polyfill e.g. -> https://babeljs.io/docs/usage/polyfill/. There is also an issue with flexbox see #304 so you have to add the following to your CSS:
.ReactTable {
  display: block;
}

And an issue related to the loading overlay as already referenced by @alexandrebensimon  #240. The loading overlay persists on IE10 so you can't hover or click on the table rows. I resolved this issue by manipulating the z-index by adding following:
.ReactTable .-loading {
  z-index: -1;
}
.ReactTable .-loading.-active {
  z-index: 2;
}

This is exactly what I needed. Thanks so much! (:

Yes! Thank you @Ixl123. I think you should propose a PR with this.

I will accept a PR with these changes. Open it up when you want! :)

Thank you Ixl123, resolved the issue for us.


Refactor server run

Simplify etcd Server Run() so it returns the client info instead of taking in a run func.
Replace the runFunc with inline code.
Create clients and shared informer factories higher in the stack so they can be shared by multiple controllers.
Plumb the context's Done channel to as many places as possible.

Just pushed a new commit that further refactors by creating clients and shared informers higher so they can be shared by multiple controllers. There's probably still some more cleanup that could be done, but this seems like a good start. I'm also plumbing through context's Done channel to more places.


HGNetv2 latency

Hi guys, it is a wonderful work.
Regarding the latency, I have two confusions:

When paired with HGNetv2-L and HGNetv2-X, the RT-DETRs achieve 114 and 74 FPS, respectively. However, the latency of RT-DETR with HGNetv2-L is 9.25 ms in your paper, which is about 108 FPS. Such a gap is unusual, as both of you claim to be on the same GPU device with TensorRT. Could you please explain it?

Model
Input shape
Dataset
APval
AP50val
Params(M)
FLOPs(G)
T4 TensorRT FP16(FPS)

RT-DETR-HGNetv2-L
640
COCO
53.0
71.6
32
110
114

--
--
--
--
--
--
--
--

RT-DETR-HGNetv2-X
640
COCO
54.8
73.1
67
234
74

In your ablation study, the latency drops from 9.25ms to 8.02ms after removing the decoder projection layers. As we know, the decoder projection layers in RT-DETR are a layer of Conv1x1 with BN. It is abnormal to save such costs after removing them. Could you please check this again?

Thank you for your valuable questions!

Since it’s not the same machine, variables like CPU and hard drive performance can't be controlled, so I cannot reproduce the exact FPS from the original paper 100%. In fact, when testing across 8 independent T4 machines (both platform and local), a 0.5ms difference is quite normal, and this doesn't affect the relative speed between models. Please also refer to the papers of YOLOv10 and LW-DETR to check the differences in RT-DETR speed compared to the original paper.

Please check this link. Removing the projection layer does not just save the time for Conv1x1; it also reduces many repeated memory accesses and processing operations.

We removed not only the input_proj layer but also the value_proj and output_proj layers. This further reduces the computational complexity and memory access operations.


[FLINK-9043][CLI]Automatically search for the last successful checkpoint when recover the job from externalized checkpoint

What is the purpose of the change
This PR base on 5982.
Automatically search for the last successful checkpoint from the given checkpoint pointer, this would be more friendly when user try to recover job from the externalized checkpoint.
Brief change log

Automatically search for the last successful checkpoint when recover the job from externalized checkpoint

Verifying this change
This change extended the AbstractFileCheckpointStorageTestBase#testPointerPathResolution().
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
I will add the doc, once the reviews is almost complete.

Sorry, but can we take back a step and first agree on what we actually want the behavior to be before jumping into an implementation?

@sihuazhou Has this feature been completed or tested？We met with the same problem.


Added fst

What problem does this PR solve?
Phase 1 of https://github.com/infiniflow/infinity/issues/359
What is changed and how it works?
Code changes

[x] Has Code change
[ ] Has CI related scripts change

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (knn performance test)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Note for reviewer

@mergify queue


won't build on OS X

I suspect you folks already know this. But PDFIUM no longer builds on OS X.
It appears that branch chromium/2387 from April 21, 2015 is the last version that builds on OS X.(saw the branch versions on the google source site and tested until I found a working branch)
I'm passing this along, in case you didn't already know the specific branch that last worked on OS X.

hey @bobweston, funny meeting you here.
I'm working on updating my homebrew formula so that you can build pdfium locally.

Hi @knowtheory,
That's appreciated. We worked around it by using the last working release. :)

Just to let you know, we've also just put up a new pdfium debian package, check the PDFshaver readme for the url :)

Just a note updating Ted's link to the PDFshaver readme.
The link to the PDFshaver readme is here, in the event others want to follow along at home. :)
https://github.com/documentcloud/pdfshaver/

Oops, sorry i mistyped that before, just updated the link.

In case anyone finds this, PDFium from the main repo (pdfium.googlesource.com/pdfium/) should build correctly on OSX (and is a lot more up to date then this repo)

Thanks @dj2!  I asked the Github folk if we could take over this group and help keep things up to date (since there wasn't any public activity) and they informed me that there was still activity and they couldn't hand it over as a consequence.
Thank you for letting us know that things will build fine on OSX again.
I have a homebrew recipe and a .deb generator that i maintain as well, and regretfully i've let lag due to time constraints.  I'll try and get those back up to head too.

Your best bet is to follow the main repo at pdfium.googlesource.com. There is a reviews[1] and a bugs[2] mailing list.  I'd also ping'd Github and tried to get access to PDFium with no luck.
[1] https://groups.google.com/forum/#!forum/pdfium-reviews
[2] https://groups.google.com/forum/#!forum/pdfium-bugs

Oh, and feel free to file any bugs at https://bugs.chromium.org/p/pdfium/issues/list which is the list we work from.

Are you able to build and create library on OS X?

@bafnaparag have you tried using the official repo? This repo is very out of date and doesn't seem to be updated. Please try pdfium.googlesource.com and if that doesn't work please file bugs at https://bugs.chromium.org/p/pdfium/issues/list so we can take a look.


fix: no longer generate .nuxt/tailwind.config.cjs

The file is no longer needed for editor support, because as of tailwindcss 3.3.0 and<EMAIL_ADDRESS>ESM and TS config files are supported out of the box.
I also updated the editor support section in the docs to the simplified setup instructions.

Also, would you be able to see why the test is failing? I see that it may have something to do with test/fixture/basic/override-tailwind.config.js (overriding content through a function is allowed as the module uses defu, but keep in mind that functions do not get serialized into the files)


Feat: view times in user timezone

As users and system users may be located in various time zones, it is essential to implement a feature that allows users to set their preferred time zone.  and show times for each user in his time-zone.
This customization will enhance the overall user experience and ensure accurate time-related information across the system.

The current system use UTC as default time zone.
we should create setting variable for each user and then show times in that time zone if has been set.
and keep the database time set to UTC.
see mshannaq://extendytest/date_utc_user.md for the idea.


[iPhone] Possible to get app in incorrect orientation

Open VIR mode in landscape
Navigate back
App is in incorrect orientation (landscape)

Basically like #621.
Tested on device.

cool, this is a break from previous behaviour (back should show only in vertical), can we get some tests on this pleassseee.

Confirmed!


chore: fix ci.

Fix some commands to adapt to the latest version of ledger-app-builder.

Codecov Report
Base: 77.72% // Head: 77.72% // No change to project coverage :thumbsup:

Coverage data is based on head (b9bb203) compared to base (15067bb).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #48   +/-   ##
========================================
  Coverage    77.72%   77.72%
========================================
  Files           12       12
  Lines         2352     2352
========================================
  Hits          1828     1828
  Misses         524      524

Flag
Coverage Δ

unittests
77.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

ledger-app-builder released a new version last week, so it looks like these modifications are no longer needed, I think we can close this PR.

It works fine now.


Background deadtime

Fix deadtime correction for the background if the background is created from a poly fit
Refactor EventList classes
add a np.around before type-casting the counts as np.int64, to avoid that for example 0.9999999999999999999999999 -> 0

I think the build is failing due to an unrelated issue. I will merge to fix this bug


the number layerIDs 0 and LayerDescriptor 4 are mismatch

sealer pull registry.cn-hangzhou.aliyuncs.com/xxxx/openjdk:11-jre-slim-buster
Error: the number layerIDs 0 and LayerDescriptor 4 are mismatch
Usage:
sealer pull [flags]
Examples:
sealer pull registry.cn-qingdao.aliyuncs.com/sealer-io/kubernetes:v1.19.8

sealer only supports pull sealer image and supports pushing sealer images to the docker repository.

thx


Replace login_or_token arg with auth arg

Please read the CLA carefully before submitting your contribution to Mercari.
Under any circumstances, by submitting your contribution, you are deemed to accept and agree to be bound by the terms and conditions of the CLA.
https://www.mercari.com/cla/
WHY
Starting pygithub 1.59.0, login_or_token was deprecated and replaced by a single auth arg.
The following message is shown when we run mkdocs build.
INFO     -  DeprecationWarning: Argument login_or_token is deprecated, please use auth=github.Auth.Token(...) instead
              File "/Users/USERNAME/.local/share/virtualenvs/VENVDIR/lib/python3.8/site-packages/mkdocs_git_snippet/plugin.py", line 23, in
            _git_snippet
                g = Github(os.getenv("GITHUB_TOKEN"))
              File "/Users/USERNAME/.local/share/virtualenvs/VENVDIR/lib/python3.8/site-packages/github/MainClass.py", line 145, in __init__
                warnings.warn(

WHAT

Replaced login_or_token arg with auth arg.
Updated requirements.txt to use pygithub>=1.59.0 as auth arg is not available with older versions.

Could you release the next version so I can use it in my docs?

@ysk24ok The changes look good to me. Since I no longer maintain the repository, I have added you as a admin.
Could you check with the JP MLP team, merge and then release.


[svgl] Multi-path svg not displaying correctly in search

Extension
https://www.raycast.com/1weiho/svgl
Raycast Version
1.75.2
macOS Version
14.3
Description
The RelaGit logo does not display both its elements inside of raycast. The icon displays correctly on the site.

The icon shown in svgl.app vs. raycast
Steps To Reproduce

Open the "Search SVG Logos" command
Search for RelaGit
Observe the incorrect display.

Current Behaviour
The image does not display both parts.

Expected Behaviour
The image displays as on the site.

Possibly related:
The instatus, linux, bitcoin, eth, dogecoin, xrp, bnb, alogrand, firebase, angular, next.js, vk, and dev student club icons do not appear to render at all.

Thanks for reporting this issue.
This issue was discovered when I first developed it.
I tried not to use the svgl API, directly downloading these svgs and creating a brand new Raycast Extension project, reading my local svg files through basic file path methods.
However, it still cannot be displayed normally.
I'm not sure if this is related to the issue of rendering svg images in Raycast.
I'll try to troubleshoot the issue again.


Permission force rejected before choose 'Allow' or 'Reject'

I'm getting mad with this bug. Before I choose the 'Allow' button, the permission's dialog is not shown. Please fix this

Is this still happening?
What platform are you in?
There's too few details to work on


consume Creds from file

we dont need to pass the creds around. we can just use it from the file shipped over,

[test]


New doc on context pooling

Fixes #501, Fixes #1181
Internal review URL

@daniel-white @ROMYIM @Menighin please review

I think the consensus we reached in the team is that we backtick a type once when we introduce it, but remove backticks later to make the text flow better. For DbContext specifically, we generally prefer to talk about "context" - I've submitted suggestions to do so.
Apart from that it all looks good to me.

The MS style guide is very clear on this. The first use should use <xref:type> and subsequent should all be code fenced. That's how all of docs.ms.com is.
Note this PR adds   "xref_query_tags": [ to .openpublishing.publish.config.json to make that possible.

@Rick-Anderson The problem is that the rendering is so ugly... We really don't want our docs to be unreadable in this way. Can you point to the data that shows always fencing creates more readable docs? Or some other data-based reason that the docs are this way?

I think I may have misunderstood. Changing DbContext to context is fine,  as context is not a type. Rarely can you substitute a type for a general term.

The problem is that the rendering is so ugly...

If you're talking about types, my guess is the consensus is fencing makes the doc look better. Perhaps  you're eyes need to get used to it. It's also a consistency issue with docs.ms.com.  I think most writers would say it looks better with types fenced and makes the docs more readable.
On problem with replacing DbContext with context is that context is now localized, and in some languages that can be problematic.

Can you point to the data that shows always fencing creates more readable docs? Or some other data-based reason that the docs are this way?

I'll bring it up with the folks who author the style guide. They usually have sound reasons for each rule AFAIK.

I do agree we should be consistent with general MS docs standard, the thing is that this is the way our docs are currently written pretty much across the board. As an example, see DbSet in the docs on entity types. We could obviously change everything (again) if needed, but for now it is what it is (and I think we like it).
Re localization for context, unfortunately I think that's a pretty universal problem. For example, we fence the AddDbContextPool method, but then talk about pooling (the concept) in English - the two may end up completely disconnected after localization, etc.

"context" may be clearer, and translate better if you say: "database context", and on first use, (similar to acronyms), say "database context (dbContext)". Then it is clear that you are introducing specific terminology.


HP left on enemy in PvP

Would appreciate the ability to see a number left on hp rather than % remaining. Could pull the hp level from highscores and just multiply it.

Duplicate of #1788


ButterKnife with PagerAdapter not working

I have the following code in my Activity:
public class DataListActivity extends SherlockFragmentActivity
{
  @Override
  protected void onCreate(Bundle savedInstanceState)
  {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_datalist);
    dataSwipeAdapter = new DataSwipeAdapter(values);
    ViewPager myPager = (ViewPager) findViewById(R.id.viewpager);
    myPager.setAdapter(dataSwipeAdapter);
    myPager.setCurrentItem(0);
  }
}

Inside the Adapter, I have this code:
public class DataSwipeAdapter extends PagerAdapter
{
   @Nullable @BindView(R.id.checkBoxData)
   CheckBox dataCheckbox;
   ...
}

In the instantiateItem method, I use this code:
@Override
public Object instantiateItem(View collection, int position)
{
  LayoutInflater inflater = (LayoutInflater) collection.getContext()
    .getSystemService(Context.LAYOUT_INFLATER_SERVICE);
  int resId = 0;
  switch (position)
  {
    case 0:
      resId = R.layout.dataList;
      break;
    case 1:
      resId = R.layout.mainList;
      break;
  }
  final View view = inflater.inflate(resId, null);
  try
  {
    if (position == 0)
    {
      ButterKnife.bind(this,view);

      if(dataCheckbox==null)
      {
         //it is somehow null
      }
   ...
  return view;
}

The null check always says that my CheckBox is null.
What am I doing wrong?

It's impossible to know without more information? Have you configured your build correctly? Is the view binder being generated? Can you reproduce it in a small, standalone sample?


Add support for construction strategy

In NewInstance strategy will be required some strategy for construction of objects. It may have own annotation for customization. Also the construction strategy should support already prepared annotation @Contructor.

Resolved.