Flutter run on Apple Silicon launches Chrome in Rosetta

When launching a debug session with flutter run Chrome is opened in Rosetta/Intel mode.
When launching Chrome from Terminal / Dock it is launched in native Apple Silicon mode.

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.4, on macOS 11.2.3 20D91 darwin-arm, locale de-DE)
    • Flutter version 2.0.4 at /Users/marius/flutter
    • Framework revision b1395592de (3 days ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/marius/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • 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 version 1.10.1

[✓] 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)

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

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 89.0.4389.114

• No issues found!

@albatrosify
can you provide the logs for the scenarios you described

Log for: flutter run --verbose

Output:
[ +109 ms] executing: [/Users/marius/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +62 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +4 ms] b1395592de68cc8ac4522094ae59956dd21a91db
[   +1 ms] executing: [/Users/marius/flutter/] git tag --points-at b1395592de68cc8ac4522094ae59956dd21a91db
[  +28 ms] Exit code 0 from: git tag --points-at b1395592de68cc8ac4522094ae59956dd21a91db
[        ] 2.0.4
[  +58 ms] executing: [/Users/marius/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +27 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/Users/marius/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
[  +72 ms] executing: [/Users/marius/flutter/] git rev-parse --abbrev-ref HEAD
[  +24 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +10 ms] executing: sw_vers -productName
[  +19 ms] Exit code 0 from: sw_vers -productName
[        ] macOS
[        ] executing: sw_vers -productVersion
[  +18 ms] Exit code 0 from: sw_vers -productVersion
[        ] 11.2.3
[        ] executing: sw_vers -buildVersion
[  +19 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 20D91
[  +13 ms] executing: sysctl hw.optional.arm64
[  +10 ms] Exit code 0 from: sysctl hw.optional.arm64
[        ] hw.optional.arm64: 1
[  +60 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.
[   +1 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.
[  +49 ms] executing: /Users/marius/Library/Android/sdk/platform-tools/adb devices -l
[   +8 ms] executing: /usr/bin/xcode-select --print-path
[  +14 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[        ] /Applications/Xcode.app/Contents/Developer
[  +12 ms] executing: sysctl hw.optional.arm64
[  +10 ms] Exit code 0 from: sysctl hw.optional.arm64
[        ] hw.optional.arm64: 1
[        ] executing: /usr/bin/arch -arm64e xcrun xcodebuild -version
[ +184 ms] Exit code 0 from: /usr/bin/arch -arm64e xcrun xcodebuild -version
[   +1 ms] Xcode 12.4
           Build version 12D4e
[   +5 ms] executing: /usr/bin/arch -arm64e xcrun xcdevice list --timeout 2
[   +6 ms] /usr/bin/arch -arm64e xcrun simctl list --json devices
[        ] executing: /usr/bin/arch -arm64e xcrun simctl list --json devices
[  +81 ms] List of devices attached
[  +37 ms] {
             "devices" : {
               "com.apple.CoreSimulator.SimRuntime.tvOS-14-3" : [
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/0C6E2FBD-C725-4620-944A-931769B09BC0\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/0C6E2FBD-C725-4620-944A-931769B09BC0",
                   "udid" : "0C6E2FBD-C725-4620-944A-931769B09BC0",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p",
                   "state" : "Shutdown",
                   "name" : "Apple TV"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/BCE7801F-1524-41DE-8161-574AD21E60E5\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/BCE7801F-1524-41DE-8161-574AD21E60E5",
                   "udid" : "BCE7801F-1524-41DE-8161-574AD21E60E5",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4K",
                   "state" : "Shutdown",
                   "name" : "Apple TV 4K"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/8A3DB34A-B84C-42B6-8234-3010B6B20B5C\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/8A3DB34A-B84C-42B6-8234-3010B6B20B5C",
                   "udid" : "8A3DB34A-B84C-42B6-8234-3010B6B20B5C",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1080p",
                   "state" : "Shutdown",
                   "name" : "Apple TV 4K (at 1080p)"
                 }
               ],
               "com.apple.CoreSimulator.SimRuntime.watchOS-7-2" : [
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/7AA86712-FD30-40B9-96A9-493463963EEA\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/7AA86712-FD30-40B9-96A9-493463963EEA",
                   "udid" : "7AA86712-FD30-40B9-96A9-493463963EEA",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-40mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 5 - 40mm"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/710FE850-4861-4595-BF89-70F6648647B4\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/710FE850-4861-4595-BF89-70F6648647B4",
                   "udid" : "710FE850-4861-4595-BF89-70F6648647B4",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-44mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 5 - 44mm"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/090E0AF3-615C-490F-BB29-D1BEC313A884\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/090E0AF3-615C-490F-BB29-D1BEC313A884",
                   "udid" : "090E0AF3-615C-490F-BB29-D1BEC313A884",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-40mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 6 - 40mm"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/503AC8C3-07DE-423A-A5D4-44989EADD195\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/503AC8C3-07DE-423A-A5D4-44989EADD195",
                   "udid" : "503AC8C3-07DE-423A-A5D4-44989EADD195",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-44mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 6 - 44mm"
                 }
               ],
               "com.apple.CoreSimulator.SimRuntime.iOS-14-4" : [
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/147D698A-E5B0-44B7-8FBB-BE9B2691AAF7\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/147D698A-E5B0-44B7-8FBB-BE9B2691AAF7",
                   "udid" : "147D698A-E5B0-44B7-8FBB-BE9B2691AAF7",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8",
                   "state" : "Shutdown",
                   "name" : "iPhone 8"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/E777903D-C509-410C-A9B8-64F6A58659CC\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/E777903D-C509-410C-A9B8-64F6A58659CC",
                   "udid" : "E777903D-C509-410C-A9B8-64F6A58659CC",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus",
                   "state" : "Shutdown",
                   "name" : "iPhone 8 Plus"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/6D81EE39-8CD1-434A-8C30-4105075A90E2\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/6D81EE39-8CD1-434A-8C30-4105075A90E2",
                   "udid" : "6D81EE39-8CD1-434A-8C30-4105075A90E2",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11",
                   "state" : "Shutdown",
                   "name" : "iPhone 11"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/FBD24DEE-34EE-4BD3-9358-9766A534C52A\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/FBD24DEE-34EE-4BD3-9358-9766A534C52A",
                   "udid" : "FBD24DEE-34EE-4BD3-9358-9766A534C52A",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro",
                   "state" : "Shutdown",
                   "name" : "iPhone 11 Pro"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/64E88187-6214-450D-8840-63AF73635201\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/64E88187-6214-450D-8840-63AF73635201",
                   "udid" : "64E88187-6214-450D-8840-63AF73635201",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro-Max",
                   "state" : "Shutdown",
                   "name" : "iPhone 11 Pro Max"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/F7482B66-943C-49E3-BEA0-E82B0F1186EA\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/F7482B66-943C-49E3-BEA0-E82B0F1186EA",
                   "udid" : "F7482B66-943C-49E3-BEA0-E82B0F1186EA",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE--2nd-generation-",
                   "state" : "Shutdown",
                   "name" : "iPhone SE (2nd generation)"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/79E01437-5A47-482F-B622-0C064CD40817\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/79E01437-5A47-482F-B622-0C064CD40817",
                   "udid" : "79E01437-5A47-482F-B622-0C064CD40817",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-mini",
                   "state" : "Shutdown",
                   "name" : "iPhone 12 mini"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/A4A940A9-5002-4054-892B-DEE624069E8B\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/A4A940A9-5002-4054-892B-DEE624069E8B",
                   "udid" : "A4A940A9-5002-4054-892B-DEE624069E8B",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12",
                   "state" : "Shutdown",
                   "name" : "iPhone 12"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/4AE1ACEE-E072-4C1E-B43B-265E03669209\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/4AE1ACEE-E072-4C1E-B43B-265E03669209",
                   "udid" : "4AE1ACEE-E072-4C1E-B43B-265E03669209",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro",
                   "state" : "Shutdown",
                   "name" : "iPhone 12 Pro"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/A46B4340-B3D6-498E-B83B-04A15E59AEB1\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/A46B4340-B3D6-498E-B83B-04A15E59AEB1",
                   "udid" : "A46B4340-B3D6-498E-B83B-04A15E59AEB1",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro-Max",
                   "state" : "Shutdown",
                   "name" : "iPhone 12 Pro Max"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/7924ABE6-B589-4E62-BE5F-4C0B5A6856E1\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/7924ABE6-B589-4E62-BE5F-4C0B5A6856E1",
                   "udid" : "7924ABE6-B589-4E62-BE5F-4C0B5A6856E1",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-",
                   "state" : "Shutdown",
                   "name" : "iPod touch (7th generation)"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/5ECB12B5-D308-4CB7-BD23-C8064E82578F\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/5ECB12B5-D308-4CB7-BD23-C8064E82578F",
                   "udid" : "5ECB12B5-D308-4CB7-BD23-C8064E82578F",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (9.7-inch)"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/AE9DF36B-A3F8-4EEF-9ED2-A85AD89E9C7A\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/AE9DF36B-A3F8-4EEF-9ED2-A85AD89E9C7A",
                   "udid" : "AE9DF36B-A3F8-4EEF-9ED2-A85AD89E9C7A",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--11-inch---2nd-generation-",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (11-inch) (2nd generation)"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/2518BD4B-37A9-46CA-A588-3CC4B8771243\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/2518BD4B-37A9-46CA-A588-3CC4B8771243",
                   "udid" : "2518BD4B-37A9-46CA-A588-3CC4B8771243",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---4th-generation-",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (12.9-inch) (4th generation)"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/240478DB-773A-4857-B20F-9D98A49C9B21\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/240478DB-773A-4857-B20F-9D98A49C9B21",
                   "udid" : "240478DB-773A-4857-B20F-9D98A49C9B21",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--8th-generation-",
                   "state" : "Shutdown",
                   "name" : "iPad (8th generation)"
                 },
                 {
                   "dataPath" : "\/Users\/marius\/Library\/Developer\/CoreSimulator\/Devices\/2B130E4A-8F42-48E7-97C2-52C9F2D2A134\/data",
                   "logPath" : "\/Users\/marius\/Library\/Logs\/CoreSimulator\/2B130E4A-8F42-48E7-97C2-52C9F2D2A134",
                   "udid" : "2B130E4A-8F42-48E7-97C2-52C9F2D2A134",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air--4th-generation-",
                   "state" : "Shutdown",
                   "name" : "iPad Air (4th generation)"
                 }
               ]
             }
           }
[+2702 ms] [
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,12",
               "identifier" : "2518BD4B-37A9-46CA-A588-3CC4B8771243",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.ipad-pro-12point9-4th-1",
               "modelName" : "iPad Pro (12.9-inch) (4th generation)",
               "name" : "iPad Pro (12.9-inch) (4th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad13,2",
               "identifier" : "2B130E4A-8F42-48E7-97C2-52C9F2D2A134",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.ipad-air4-1",
               "modelName" : "iPad Air (4th generation)",
               "name" : "iPad Air (4th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,9",
               "identifier" : "AE9DF36B-A3F8-4EEF-9ED2-A85AD89E9C7A",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.ipad-pro-11-2nd-1",
               "modelName" : "iPad Pro (11-inch) (2nd generation)",
               "name" : "iPad Pro (11-inch) (2nd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,8",
               "identifier" : "F7482B66-943C-49E3-BEA0-E82B0F1186EA",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-se-1",
               "modelName" : "iPhone SE (2nd generation)",
               "name" : "iPhone SE (2nd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,5",
               "identifier" : "E777903D-C509-410C-A9B8-64F6A58659CC",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-8-plus-2",
               "modelName" : "iPhone 8 Plus",
               "name" : "iPhone 8 Plus"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone13,2",
               "identifier" : "A4A940A9-5002-4054-892B-DEE624069E8B",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-12-1",
               "modelName" : "iPhone 12",
               "name" : "iPhone 12"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,1",
               "identifier" : "6D81EE39-8CD1-434A-8C30-4105075A90E2",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-11-1",
               "modelName" : "iPhone 11",
               "name" : "iPhone 11"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,3",
               "identifier" : "FBD24DEE-34EE-4BD3-9358-9766A534C52A",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-11-pro-1",
               "modelName" : "iPhone 11 Pro",
               "name" : "iPhone 11 Pro"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone13,3",
               "identifier" : "4AE1ACEE-E072-4C1E-B43B-265E03669209",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-12-pro-1",
               "modelName" : "iPhone 12 Pro",
               "name" : "iPhone 12 Pro"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad11,7",
               "identifier" : "240478DB-773A-4857-B20F-9D98A49C9B21",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.ipad-8-wwan-1",
               "modelName" : "iPad (8th generation)",
               "name" : "iPad (8th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.3 (18K559)",
               "available" : true,
               "platform" : "com.apple.platform.appletvsimulator",
               "modelCode" : "AppleTV6,2",
               "identifier" : "8A3DB34A-B84C-42B6-8234-3010B6B20B5C",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.apple-tv-4k",
               "modelName" : "Apple TV 4K (at 1080p)",
               "name" : "Apple TV 4K (at 1080p)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.3 (18K559)",
               "available" : true,
               "platform" : "com.apple.platform.appletvsimulator",
               "modelCode" : "AppleTV6,2",
               "identifier" : "BCE7801F-1524-41DE-8161-574AD21E60E5",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.apple-tv-4k",
               "modelName" : "Apple TV 4K",
               "name" : "Apple TV 4K"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,4",
               "identifier" : "147D698A-E5B0-44B7-8FBB-BE9B2691AAF7",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-8-2",
               "modelName" : "iPhone 8",
               "name" : "iPhone 8"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone13,4",
               "identifier" : "A46B4340-B3D6-498E-B83B-04A15E59AEB1",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-12-pro-max-1",
               "modelName" : "iPhone 12 Pro Max",
               "name" : "iPhone 12 Pro Max"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "7.2 (18S561)",
               "available" : true,
               "platform" : "com.apple.platform.watchsimulator",
               "modelCode" : "Watch6,1",
               "identifier" : "090E0AF3-615C-490F-BB29-D1BEC313A884",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.watch-series6-1",
               "modelName" : "Apple Watch Series 6 - 40mm",
               "name" : "Apple Watch Series 6 - 40mm"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "7.2 (18S561)",
               "available" : true,
               "platform" : "com.apple.platform.watchsimulator",
               "modelCode" : "Watch5,3",
               "identifier" : "7AA86712-FD30-40B9-96A9-493463963EEA",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.watch-series5-1",
               "modelName" : "Apple Watch Series 5 - 40mm",
               "name" : "Apple Watch Series 5 - 40mm"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.3 (18K559)",
               "available" : true,
               "platform" : "com.apple.platform.appletvsimulator",
               "modelCode" : "AppleTV5,3",
               "identifier" : "0C6E2FBD-C725-4620-944A-931769B09BC0",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.apple-tv-4",
               "modelName" : "Apple TV",
               "name" : "Apple TV"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,5",
               "identifier" : "64E88187-6214-450D-8840-63AF73635201",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-11-pro-max-1",
               "modelName" : "iPhone 11 Pro Max",
               "name" : "iPhone 11 Pro Max"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "7.2 (18S561)",
               "available" : true,
               "platform" : "com.apple.platform.watchsimulator",
               "modelCode" : "Watch5,4",
               "identifier" : "710FE850-4861-4595-BF89-70F6648647B4",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.watch-series5-1",
               "modelName" : "Apple Watch Series 5 - 44mm",
               "name" : "Apple Watch Series 5 - 44mm"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad6,4",
               "identifier" : "5ECB12B5-D308-4CB7-BD23-C8064E82578F",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.ipad-pro-9point7-a1674-b9b7ba",
               "modelName" : "iPad Pro (9.7-inch)",
               "name" : "iPad Pro (9.7-inch)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone13,1",
               "identifier" : "79E01437-5A47-482F-B622-0C064CD40817",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.iphone-12-mini-1",
               "modelName" : "iPhone 12 mini",
               "name" : "iPhone 12 mini"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPod9,1",
               "identifier" : "7924ABE6-B589-4E62-BE5F-4C0B5A6856E1",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.ipod-touch-7-2",
               "modelName" : "iPod touch (7th generation)",
               "name" : "iPod touch (7th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "7.2 (18S561)",
               "available" : true,
               "platform" : "com.apple.platform.watchsimulator",
               "modelCode" : "Watch6,2",
               "identifier" : "503AC8C3-07DE-423A-A5D4-44989EADD195",
               "architecture" : "arm64",
               "modelUTI" : "com.apple.watch-series6-1",
               "modelName" : "Apple Watch Series 6 - 44mm",
               "name" : "Apple Watch Series 6 - 44mm"
             }
           ]

           objc[8821]: Class AMSupportURLConnectionDelegate is implemented in both ?? (0x1ef954188) and ?? (0x104a102b8). One of the two will be used. Which one is undefined.
           objc[8821]: Class AMSupportURLSession is implemented in both ?? (0x1ef9541d8) and ?? (0x104a10308). One of the two will be used. Which one is undefined.
[  +34 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.
[   +2 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.
[ +107 ms] Skipping pub get: version match.
[ +140 ms] Generating /Users/marius/Desktop/Projects/crewlog/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[ +221 ms] Launching lib/main.dart on Chrome in debug mode...
[ +146 ms] Updating assets
[  +72 ms] Waiting for connection from debug service on Chrome...
[ +122 ms] <- reset
[   +6 ms] /Users/marius/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev /Users/marius/flutter/bin/cache/artifacts/engine/darwin-x64/frontend_server.dart.snapshot --sdk-root /Users/marius/flutter/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true --output-dill /var/folders/2v/wqk7_j7s275d6nkr32gt94q40000gn/T/flutter_tools.ewWMa9/flutter_tool.Y6cfBF/app.dill --libraries-spec file:///Users/marius/flutter/bin/cache/flutter_web_sdk/libraries.json --packages /Users/marius/Desktop/Projects/crewlog/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-root /var/folders/2v/wqk7_j7s275d6nkr32gt94q40000gn/T/flutter_tools.ewWMa9/flutter_tools.6SfmHE --filesystem-scheme org-dartlang-app --initialize-from-dill build/c7922d95bf4a2462b75c84a97c312edb.cache.dill.track.dill --platform file:///Users/marius/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk.dill --no-sound-null-safety
[  +17 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+8789 ms] Waiting for connection from debug service on Chrome... (completed in 8,9s)
[   +5 ms] Synced 16.1MB.
[   +1 ms] <- accept
[        ] Caching compiled dill
[  +80 ms] Using Google Chrome 89.0.4389.114

[+1843 ms] [CHROME]:
[  +11 ms] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:62112/devtools/browser/3b04f9ba-b94e-4904-9b21-944349a324d4
[ +897 ms] DwdsInjector: Received request for entrypoint at http://localhost:62090/main_module.bootstrap.js
[  +15 ms] MetadataProvider: Loading debug metadata...
[  +27 ms] MetadataProvider: Loaded debug metadata
[  +19 ms] DwdsInjector: Injected debugging metadata for entrypoint at http://localhost:62090/main_module.bootstrap.js
[+1837 ms] DevHandler: Debug service listening on ws://<IP_ADDRESS>:62139/Pw4hT3lIRZc=/ws

[  +22 ms] Debug service listening on ws://<IP_ADDRESS>:62139/Pw4hT3lIRZc=/ws
[        ] Running with unsound null safety
[        ] For more information see https://dart.dev/null-safety/unsound-null-safety
[   +2 ms] 🔥  To hot restart changes while running, press "r" or "R".
[        ] For a more detailed help message, press "h". To quit, press "q".

Hi @albatrosify
Thanks for filing the issue! I can confirm it launches Chrome in intel on stable as well as master
Preview

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.4, on macOS 11.2.3 20D91 darwin-arm, locale
    en-GB)
    • Flutter version 2.0.4 at /Users/nevercode/Code/flutter_stable
    • Framework revision b1395592de (5 days ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/nevercode/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Users/nevercode/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

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

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/nevercode/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/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)

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 11.2.3 20D91 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 89.0.4389.114

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 2.1.0-13.0.pre.498, on macOS 11.2.3 20D91
    darwin-arm, locale en-GB)
    • Flutter version 2.1.0-13.0.pre.498 at /Users/nevercode/Code/flutter_master
    • Framework revision a2f67720ef (18 minutes ago), 2021-04-06 22:55:03 -0700
    • Engine revision 92f4dfb048
    • Dart version 2.13.0 (build 2.13.0-208.0.dev)

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/nevercode/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Users/nevercode/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

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

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/nevercode/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/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)

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 11.2.3 20D91 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 89.0.4389.114

! Doctor found issues in 1 category.

(Sorry for the delay, forgot to connect M1  for testing)

Likely nearly all Google engineers have Macbook M1 computers.  This bug seems like a one liner.  It's now open for nearly 2 weeks.  We can only assume that few people are developing Flutter web apps.  Shame, as it seems like good technology.

If anyone is able to validate https://github.com/flutter/flutter/pull/80758 works as expected on the master channel, that would be awesome!


Still maintained?

I understand angular4 is the new thing and that angular.js is the old thing. But I like the old thing better than the new thing.
So will angular.js be maintained and improved in the future, or am I forced to downgrade to angular4?

AngularJS is still maintained but is considered stable and will not receive substantial feature improvements. More small improvements and bug fixes and helpful tweaks for upgrading to Angular. For new projects you should definitely use Angular.

or am I forced to downgrade to angular4

I understand shifting to Angular might be a bit scary in the start, but eventually I guess you'll start to apreaciate the things that make Angular differ from (and superior to) AngularJS.

@notsonotso Or I am thinking to switch to Vue.js

Hello ma'am,
I'm new to GitHub.
I just joined.
Please tell me how do I learn to code from GitHub?
Thanks
On Mon, 29 May 2017 at 11:42 PM, rognoni<EMAIL_ADDRESS>wrote:

@notsonotso https://github.com/notsonotso Or I am thinking to switch to
Vue.js https://github.com/vuejs/vue
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.js/issues/16019#issuecomment-304709647,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbstvQfwNQF7Lzy0OWLj2HdcpLv-eZdtks5r-wqBgaJpZM4Nohgc
.

In other words, yes AngularJS is still maintained.

@Narretz Just for general knowledge, since when did AngularJS core team stopped delivering new features / core changes? (Like what is the official date)

There is a blog post about the final release and LTS : “Stable AngularJS and Long Term Support” by Pete Bacon Darwin https://link.medium.com/3B8RvxT2MW


make chrome-build failed

I follow all the native build steps, but when I get to the moment to run the "make chrome-build" command I get this error "make: *** No rules for creating the 'chrome-build' target. Stop." . I run this command inside the build folder, following the command order and I understood that it would be in that location.

did you run ../configure first?

yes, I ran the ../config command first and the only error I got was "configure: error: failed to find zlib"

Then you need to make sure that configure runs successfully. The configure script generates the Makefile.
For zlib, consider using brew or apt to install libz on your platform.

If the Makefile script is generated inside the Build folder where the configure command was made, then it was unsuccessful. What could cause the failure and would there be a message indicating?

@WellingtonSI Can you provide more details on the errors you face, including the commands that you ran and their output? Right now it is difficult to understand exactly the problem you are facing.

i have the same issue then i realize that i need install firefox first although i only need chrome.

apt install zlib1g-dev did work for me on Debian.


Adjust default mem fraction to avoid OOM

May you rebase the main branch?

We could test the latest PR E2E test.


[FEATURE] add the blogpost making most of markdown

Is your feature request related to a problem? Please describe.
There is a nice blogpost here:
https://github.com/argilla-io/argilla-workshop
Describe the solution you'd like
N.A.
Describe alternatives you've considered
N.A.
Additional context
N.A.

You can skip the part about DeepSearch

This is to showcase

displacy

table

audio
video
image


MySQL Connection Graphical User Interface design Using JavaFX and Scene builder

…ne builder
Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

`This closes #4384

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Upon running your article through our 3rd party plagiarism checker it seemed to raise a few flags and the % was higher than we typically accept. Please see attached PDF - and revisit the article to ensure we are contributing wholly unique and original content. Be sure to see our resources page to see more info on plagiarism and what is considered as such.
MySQL Connection Graphical User Interface design Using JavaFX and Scene builder #4608 Copyleaks Report.pdf

@Kayere revision done as per the document

@Kayere, could we kindly have another plagiarism check.

Plagiarism check done ✔

Plagiarism check done ✔

@Dawe-7 I have effected the changes

jumping on this one

@JosephAyoma
Please be sure to review any suggestions/changes made by your peer reviewer and/or myself during a final review.


linux argument startup fix

You shouldn't put the the script's arguments in a variable without keeping them as a list because the arguments were merged and then splitted with whitespace. This results in a total mashup of tabs.
See Issue https://github.com/Microsoft/vscode/issues/17852

Hi @mrdrogdrog, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks!

@joaomoreno please cc me for Linux CLI stuff, this re-introduced this issue: https://github.com/Microsoft/vscode/commit/c2935f207378a9106173ebd1fbdf4157ba2cee3e

Fixed looping over the arg array for sudo instead of shifting it https://github.com/Microsoft/vscode/commit/289dbf77e32bd44604d6deeb2bd0bc4cb9300e8c

Ugh! Sorry about that. 🍺

No worries, luckily the issue wasn't closed off so I spotted the regression.


feat: Indent page titles within a Tab Group when group chevron is open

Hi,
I really like the support for Tab Groups, but notices that tabs within a group are not indented when the group chevron is in the open state.

Hey @DanielAsher, I opted for this design to give more space for the tab title. I will try running an experiment with indented tabs to see if it performs better.

Think this design choice is most likely to be useful for readability when people use multiple smaller groups all visible together.
I quite like and the current method with the group colour line down the side, and definitely prefer extra title space, though always happy to have these kind of features available as a toggle.
I think the indenting would only be particularly useful if you could stack within stacks which isn't default group functionality, unless you could detect when there's sort "implied groups" when within one tab you open multiple new tabs, and they append to the end of this temporary group.


Clarify the Display of Large Integers in Arrays

Problem
If query results contain arrays of large integer values, the display of commas to separate 1000s places makes for an ambiguous representation of integer elements in the array. Simple example:
select array [1100,2200] as a;

Produces a result set that looks like this in DBeaver:

Is that the integers "1,100" and "1,200", or the integers "1", "100", "2", and "200"? Not possible to tell without copying and pasting the cell.
Proposed Solution

Use semi-colons between integers: [1,100;2,000]. This is how I would handle ambiguous commas in an English sentence:

My favorite cities are Chicago, IL; San Francisco, CA; and Salt Lake City, UT.

Describe alternatives you've considered
Some countries use periods to separate thousands places, but I feel this would be too confusing with actual floating decimal points. For example [1.101, 1.202]: Are these decimal point values or integers?

I can't reproduce the problem with formatting (in arrays numbers are not formatted with group dividers, at least in PostgreSQL).
What is your database?

ticket closed. there is no update on ticket more than a month

@serge-rider Hi, Sorry I failed to respond. DB is Hadoop 3 and the driver is JDBC Presto 0.192.
Interesting to know that this is not a universal problem with different SQL flavors.

I landed on this page while looking for a solution to the same problem, for anyone in the same situation you can disable grouping or change the locale in Preferences > Editors > Data Editor > Data Formats


Add FormatProvider for FXCop error CA1305. Fix failing tests and a bug

Once I fixed the format provider, the SSH PS tests were failing, which showed a bug. Updated tests with new PS format and fixed the bug.

@WardenGnaw @gregg-miskelly Apparently some test are failing too so I need to fix those also.

@gregg-miskelly @WardenGnaw Can you take another look. This should pass the build now.


Fix issue forms saving too slow after Careplan generation

IMPORTANT: Where possible all PRs must be linked to a Github issue
Cherry Picked updates from release branch PR  (#2699)

Update release version to v1.0.0 (4)
Fix issue forms saving too slow

Fixes https://github.com/onaio/fhir-resources/issues/2531

Engineer Checklist

[x] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[x] I have added any strings visible on UI components to the strings.xml file
[x] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[x] I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
[x] I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

[ ] I have verified Unit tests have been written for any new feature(s) and edge cases
[ ] I have verified any strings visible on UI components are in the strings.xml file
[ ] I have verifed the CHANGELOG.md file has any notable changes to the codebase
[ ] I have verified the solution has been implemented in a configurable and generic way for reuseable components
[ ] I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

The tests are failing because we are ignoring the Task.period filter (which is critical otherwise all Tasks will be marked as ready)

If the implementation here https://github.com/opensrp/fhircore/pull/2705 improves on performance then we can close this PR (code already in main branch) unless we would want to apply the period filter via code (which would require some significant refactor on the affected test classes)

Closing this PR in favor of https://github.com/opensrp/fhircore/pull/2710


Fix bug in jaccard metrics

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

Project coverage is 100.00%. Comparing base (18ce730) to head (323d5eb).
Report is 8 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #295   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           98        98
  Lines         2359      2359
  Branches       214       214
=========================================
  Hits          2359      2359

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


feat: Added Pizza Fact

Description
Added a pizza fact into the repo's fact and trivia markdown file
What type of PR is this? (check all applicable)

[X] ☝ Add a pizza fact or trivia
[ ] 🧑🍳 Add a pizza recipe
[ ] 🗺 Add a regional pizza
[ ] 🍴 Add a traditional food
[ ] 📝 Documentation Update

Related Tickets & Documents
Relates to #36
Added to documentation?

[ ] 📜 README.md
[X] 🙅 no documentation needed

[optional] What GIF best describes this PR or how it makes you feel?

Hey @prw760,
You have a failed check here. You need to address it before we can review your PR.
Thank you! 🙂

Hi, Ayu.   I fixed the problem with the title of the PR, and it appears to have passed the checks now.   Hopefully this is merge ready, finally!  Thanks again.

You did fix the problem, @prw760! Well done! 🎉
But can you please change the issue number?
At the moment, you're referring to the closed PR number. 🙂
Also, you need to put "Relates to" and not "Fixes" in front of the issue number to keep it open as mentioned in the issue.
Thanks!

Hi, again, Ayu.   I fixed the issue number (to #36) and also changed "Fixes" to "Relates to".   Hopefully this works! :)

You are super patient, Ayu! That's an incredible skill. Thanks again for all your help! Every time you have an issue with one of my PRs, I learn more. :)
Sent with Proton Mail secure email.
On Friday, May 17th, 2024 at 2:15 PM, Ayu Adiati @.***> wrote:

Merged #96 into main.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
 You have growth mindset which is very important to have. 🙌🏼


Implement support to variable WEBSERVER_ERROR_LOG inside libmodsecurity

More information about WEBSERVER_ERROR_LOG can be found at ModSecurity reference manual: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual

The variable WEBSERVER_ERROR_LOG is used by OWASP CRS version 3 and version 2, both versions read this variable to identify a possible request violation that was treated internally by Apache. As result of the reading, in case there is a request violation, a warning is generated.
Since it is not feasible to implement it in all platforms that we desire to support, I am removing the support to this variable. If you think otherwise, please re-open this issue for discussion.

I agree the single CRS rule using this is not very useful. But the variable in general seems worthwhile.
Why is not feasible to support it on other platforms?
We have other variables that are empty in certain phases. Why can't it be empty, if the platform does not support it?


Create domain issue

I want to create domain but i face some issue like .. pass second argument .. please help me and tell me that how i pass second argument for create domain.. I am passing second argument like this but i face an error..

Please provide the error message / stack

Please provide the error message / stack
i face this error

It says what the error is: You have to create a CreateRequest-object to provide as second parameter, not an array. If you would use an IDE that's not VisualStudioCode (but e.g. PHPStorm) it would also highlight it as invalid red.
Maybe this is not a good project to learn programming PHP


Implement fseeko and ftello

Summary
And declare chmod/fchmod/utimes
Please ignore the false alarm:
/home/xiaoxiang/nuttx/nuttx/include/stdlib.h:149:10: error: Mixed case identifier found
/home/xiaoxiang/nuttx/nuttx/libs/libc/stdlib/lib_Exit.c:31:5: error: Mixed case identifier found

Impact
Testing

what's the point to have prototypes without implementations?

what's the point to have prototypes without implementations?

Normally, I will try to implement the function if it isn't to hard like: https://github.com/apache/incubator-nuttx/pull/1279
But, it's hard for utimes/chmod/fchmod since VFS layer lack these concept.
On the other hand, the standard c++ library(e.g. libc++) using all most of c standard functions in header files like this:
#include <__config>
#include <stdio.h>

#if !defined(_LIBCPP_HAS_NO_PRAGMA_SYSTEM_HEADER)
#pragma GCC system_header
#endif

_LIBCPP_BEGIN_NAMESPACE_STD

using ::FILE;
using ::fpos_t;
using ::size_t;

using ::fclose;

but don't really use them inside the library.

Please ignore the false alarm:
/home/xiaoxiang/nuttx/nuttx/include/stdlib.h:149:10: error: Mixed case identifier found
/home/xiaoxiang/nuttx/nuttx/libs/libc/stdlib/lib_Exit.c:31:5: error: Mixed case identifier found

@Ouss4 @yamt to speed up the process, I split the PR to the small one, please review again.

Yes, off_t define to int is strange, the better type is long.


PDCL-5957 Fixes issue where error was thrown if sandboxes were returned but without a default.

Description
When a customer has access to at least one sandbox but not sandbox configured as the default for the org, the following error would be thrown: Cannot read property 'name' of undefined. This fixes that issue.

Related Issue
https://jira.corp.adobe.com/browse/PDCL-5957

Motivation and Context

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] All tests pass and I've made any necessary test changes.
[x] I've updated the schema in extension.json or no changes are necessary.

Great job cleaning up the tests too!

I added a couple commits based on @jonsnyder's feedback. Feel free to review. Otherwise I'll merge soonish.


[android] make checked listener in abstract list adapter operate on items instead of views.

Related to #293
So I needed an information for the adapter that the item check state was changed so that the logic of check all box could work. Due to the fact that we can check an item without using the check box but any part of the item (on that branch in check mode) it would be hard to find the checkbox without some .getParent() conga line. I really did not need the exact item because all I needed was the info that any item was passed, so I could have passed a null but that somehow did not seem clean. So I thought why not make the adapter return the item itself rather than a CompundButton with the item as a tag.

I fail to see how this helps you or makes some improvement. If anything I would like to remove OnItemCheckedListener from AbstractListAdapter. Isn't the method  AbstractListAdapter#onItemChecked already protected?

Well I needed to add a method that allows to programmatically check an item (thanks to clicking on item not on checkbox) this happens in FileListAdapter, but I need to be informed in BrowsePeerFragment of that action (for check all button). So using this listener seemed like a good idea, but I decided that it would make more sense if the listener would inform of which item was checked and not which compound button associated with this item was clicked (not really need for me as I need just the fact that there was a change in one of the items and could pass null, but if for some reason someone would want to know which item changed the check state, passing that info inside a compound button is problematic (the button might not even exist))

From a more practical point of view, I'm not too comfortable with this:
- public void onItemChecked(CompoundButton v, boolean checked) {
+public void onItemChecked(T item, boolean checked) {

It's always good to have access to the view that triggers the event. If anything, I think I would've just added the parameter, having just the associated model object to the item clicked here doesn't make too much sense to me, I feel like I'd then have to do acrobatics if I wanted to do any UI code
public void onItemChecked(CompoundButton v, T item, boolean checked) {

this way you avoid doing the .setTag, .getTag acrobatics


Installer job failed for jdk11u-mac-x64

jdk11u-mac-x64-hotspot
jdk11u-mac-x64-openj9
https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-mac-x64-hotspot/579/console
07:35:58  Execution error: null

This error is caused by:
security: SecKeychainUnlock <NULL>: The user name or passphrase you entered is not correct.
Build step 'Execute shell' marked build as failure

Essentially the machine is trying to unlock the keychain and is complaining that the password is incorrect. I've rebooted the machine which fixed the issue (I've had the same issue in the past)
The only thing I can think is that it's because the machine had 2 executors and was trying to codesign 2 binaries at the same time.
Closing for now to see if this fixes things

Problem has re-coccured: https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_mac/4563/console
Copied 3 artifacts from "build-scripts » jobs » jdk » jdk-mac-x64-hotspot" build number 232
[create_installer_mac] $ /bin/sh -xe /var/folders/rt/8_by_h8n5g9d5jhp66cf_7d80000gr/T/jenkins3652285145151103538.sh
+ bash pkgbuild/create-installer-mac.sh
security: SecKeychainUnlock <NULL>: The user name or passphrase you entered is not correct.
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE

Machine: test-macincloud-macos1014-x64-1
@gdams

Looking at it now, the specific machine is test-macincloud-macos1014-x64-1. According to ci.adoptopenjdk.net, it only has one executor, so I would suppose it's a different machine to the one that caused the issue to open initially.
The particular command it's failing on is:
security unlock-keychain -p `cat ~/.password`

However, the correct syntax for unlock-keychain is as follows:  Usage: unlock-keychain [-u] [-p password] [keychain]
When the keychain isn't specified (or passed NULL), it attempts to unlock the system keychain (See : https://developer.apple.com/documentation/security/1400341-seckeychainunlock?preferredLanguage=occ ), which the Jenkins user password is not the correct one.
I was able to do the following as the Jenkins user without error, so I believe the keychain needs to be specified.
security unlock-keychain -p `cat ~/.password` login.keychain-db

This, however, doesn't explain why a restart fixes the issue or why it stops working after awhile.

https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_mac/4628/console
The above PRs seemed to have fixed the keychain issue, so closing the issue.


Support contentRegex for TextMate grammar

Requirements for Adding, Changing, or Removing a Feature

Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must contribute a change that has been endorsed by the maintainer team. See details in the template below.
The pull request must update the test suite to exercise the updated functionality. For guidance, please see https://flight-manual.atom.io/hacking-atom/sections/writing-specs/.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see https://github.com/atom/atom/tree/master/CONTRIBUTING.md#pull-requests.

Issue or RFC Endorsed by Atom's Maintainers

https://github.com/atom/first-mate/pull/109
Description of the Change

NOTE: Requires update on first-mate dependency to make the contentRegex property be picked up in the first place.
Adds support for the contentRegex property existing on TextMate grammars. Treats it as an Oniguruma regex, so that the TextMate grammar is consistent with itself.
Alternate Designs

Could make the contentRegex a regular JS regex, but then it would be the only regex like that for a TextMate grammar.
Possible Drawbacks

Currently it looks at the whole file, which is potentially dangerous for performace. The use case in the linked issue would be fine with 20 lines or less. Declaring how many lines it wants would require more design choices though.
Verification Process

Manually
Release Notes

Add support for contentRegex on TextMate grammars

I added some basic test coverage for the added logic. Waiting on a green build and then I will merge. Thanks for contributing this!

Argh. Got bit by a flaky build failure that I'm actively fighting on another thread. Rebuilding.

Re-triggered the build manually and it passed. Not sure why that is not indicated on the PR.

Thanks again for your contribution!


Fix: Tool descriptions

Resolves: #53
Added the appropriate descriptions for Poet.so and Pika Style.

Perfect


Taptive customer story

Adding content for Taptive's user story

These are all great starts, and I love the stats you chose.
With customer stories, it is less about conveying how one succeeded with Badger and instead an opportunity to get an individual to relate and connect with a point of Badger and the solution it offers from a new perspective.

This thematic template will help guide us through the needed blocks while the perspective and approach for each will be different.

For Taptive, the final result may look like this:

-QUOTE
Taptive was inspired to start using Badger because they were looking for an easy way to issue on-chain rewards to participants who completed their cohorts.
The simplest option available
They found Badger to be the supremely easy option compared to other solutions on the market...

... etc.

Closed in reference to #178


Add result builder to decl blocks

Hi @ahoppen 👋
I have not forgotten you, just had a busy at work and then summer vacation!
And European Championship in football where Denmark did it very good ⚽
But I'll get some time to look at somethings again.
From #291
This PR aims to A MemberDeclBlock should be directly creatable from a MemberDeclListBuilder result builder. This would probably take some hardcoding of MemberDeclBlock in the convenience initializers where the initialization of a MemberDeclBlock with a MemberDeclListBuilder is another convenience added (besides the current ones of: syntax collection through result builder, tokens by string literals and defaulting of tokens)
This will make it possible to make things like
StructDecl("Foo") {
    StructDecl("Bar")
}

I will next week start too look into it again, and catch up.
I will properly ask some questions

Cool. Thanks! And there’s no need to apologize, you are working on this in your free time after all. 😉
Let me know when the code is ready for review or if you have any questions. I just took a look at the code and it still appears to be in an incomplete state to me.

@kimdv What’s the state of this PR? Is it ready for review yet or still work in progress?

@ahoppen I think it is in a state where it is ready for review.
I have rebased with latest master

I just looked through the changes and thought it was a little over-complicated to only generate the ExpressibleAs protocols for types that are children of syntax collections – why not have them for all syntax nodes as they might also come in handy later?

Sure we can generate for them all. Did that initially, but went away because I wouldn't introduce a lot of protocols that wasn't used. Will add them again.

I also thought it was a bit of a shame that ExprBuildable didn’t conform to ExpressibleAsExprBuildable.

My thought was just as we have a ExprBuildable protocol it would be a bit duplicated to have a ExpressibleAsExprBuildable?
But maybe there is some scenarios I haven't thought of.

I couldn’t resist the temptation to play around with your design myself and think it’s easiest to just implement the ExpressibleAs protocols in Buildables.swift.gyb. That way we can also conform protocols like ExprBuildable to their corresponding ExpressibleAs protocols. I pushed my draft idea to ahoppen@d6d4f12. What do you think?

So we should move everything from ExpressibleBuildables.swift.gyb to Buildables.swift.gyb.

Sure we can generate for them all. Did that initially, but went away because I wouldn't introduce a lot of protocols that wasn't used. Will add them again.

My thought process was that we are exposing these protocols publicly and it’s hard to explain why certain syntax kinds have ExpressibleAs protocols and some don’t in case someone wants to use them in their own codebase. Generating all just eliminates that problem.

My thought was just as we have a ExprBuildable protocol it would be a bit duplicated to have a ExpressibleAsExprBuildable?
But maybe there is some scenarios I haven't thought of.

That’s a good point. I hadn’t thought of that. But I think that

if we have an ExressibleAsExprBuildable protocol, ExprBuildable should definitely conform to it (how is ExprBuildable not expressible as ExprBuildable 🤯) or
we should not have the ExpressibleAsExprBuildable protocol at all. In that case, ResultBuilders.swift.gyb would need to check whether element_type has an ExpressibleAs protocol or
typealias ExpressibleAsExprBuildable = ExprBuildable and add a comment that this type alias only exists to simplify code generation.

I don’t have a strong preference for either of these options.

So we should move everything from ExpressibleBuildables.swift.gyb to Buildables.swift.gyb.

Not necessarily. I only did so to conform ExprBuildable to ExpressibleAsExprBuildable (and reuse some of the loops). If we decide that we don’t need ExressibleAsExprBuildable as a protocol, everything can live inside ExpressibleBuildables.swift.gyb again.

@ahoppen I have applied your suggestions 👍

After some thoughts I think it would be strange that ExprBuildable would be the only one with no ExpressibleAs as protocol.

It wouldn’t have been the only one. DeclBuildable also wouldn’t have had an ExpressibleAs protocol 😉 Still I agree it makes sense to add them for consistency.

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 633025d5e21280dcf5af74997c7aa482294d3d13

Build failed
Swift Test OS X Platform
Git Sha - 633025d5e21280dcf5af74997c7aa482294d3d13

Rebased on latest master

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 5c28acc59b13a1710652f67d04ef2d6639638dab

Build failed
Swift Test OS X Platform
Git Sha - 5c28acc59b13a1710652f67d04ef2d6639638dab


Fix gamma (srgb EOTF) for GLTF via Asset3D embedded rgb(a) textures

What
Fix gltf loader assuming that the mesh shader doesn't apply the EOTF, when it fact it does (i.e. it calls linear_from_srgb)
Reference - via raw_mesh which was unaffected:

Before:

After:

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

OETF/EOTFing is hard!


test(extension): minor test code cleanup

Checklist

[ ] JIRA - <link>
[ ] Proper tests implemented
[ ] Screenshots added.

Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met
Screenshots
Attach screenshots here if implementation involves some UI changes

coverage: 52.976%. remained the same
when pulling d00c325f4ee64de8813dbff9c6471e6496f72c14 on test/minor-cleanup
into 7917105f04979c8a479418d36d8add1bbf2d8a65 on main.


FailureCallback is not used when buffer is enabled

A few questions before you begin:
Does this issue relate to a new feature or an existing bug?

[x] Bug
[ ] New Feature

What version of Serilog.Sinks.Elasticsearch is affected?  Please list the related NuGet package.
<PackageReference Include="Serilog.Sinks.Elasticsearch" Version="7.1.0" />
What is the target framework and operating system? See target frameworks & net standard matrix.

[x] netCore 2.0
[ ] netCore 1.0
[ ] 4.7
[ ] 4.6.x
[ ] 4.5.x

Please describe the current behavior?
FailureCallback is not used when buffer is enabled.
Please describe the expected behavior?
FailureCallback is used, no matter if buffer is enabled or not.
If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem

Configure serilog with ES Sink, with a FailureCallback (and usage of callback enabled):

// . . .
.WriteTo.Elasticsearch(
new ElasticsearchSinkOptions(new Uri("<ES server URL>")
    {
        BufferBaseFilename = "<filename>",
        FailureCallback = e => Console.WriteLine(">>> Unable to submit event " + e.RenderMessage()),
        EmitEventFailure = EmitEventFailureHandling.RaiseCallback,
    });

start the application without the ES server being reachable (to provoke errors)
=> no output happens using the FailureCallback
Note: if SelfLog output is enabled, errors appear in SelfLog
Note: if buffer is not enabled, errors are output to FailureCallback
Note: I noticed that FailureCallback is used in ElasticSearchSink.cs, but not in ElasticSearchLogShipper.cs (the error message "Exception while emitting periodic batch from..." is one of the ones we observed in the SelfLog).

Unfortunately the durable part is different from the main logic. Which is annoying and we are looking into options to remove it #254


getMedias not returning owner

Hey, I noticed getMedias isn't returning owner and ownerId, any possible fix for this? Thank you

Hello, thank you.
It has been added @dasENIGMA


Cannot reuse plugin, tasks get reinitialized

Base plugins which have app.use(tasks()) overwrite each other's tasks.
Suppose I am writing two base plugins, each of which export something like the following.
const tasks = require("base-task");
const pluginId = "my-id"; // generated
module.exports = function (app, ..._rest) {
    if (app.isRegistered(pluginId)) {
        return;
    }

    app.use(tasks());
    app.task("foo", function(done) {
        console.log("I am a task");
        done();
    });
}

If the first plugin defines task "foo", and the second "bar", then app will only have task "bar" because the tasks got reinitialized.
I can workaround this by using the following in place of app.use(tasks()).
    if (typeof app.task !== "function") {
        app.use(tasks());
    }

Should base-task use the isRegistered pattern, or is there a use case for reinitialization?

In the latest version of base the .use method can take a name as the first argument. If app is from the new base, then try the following:
app.use('task', tasks());

You can see this done in the tests here


Wireless improvement - add 802.11n channel width (HT) options

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[ x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[ x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
We cannot select on the Wireless options page on the web interface the channel width (HT) - for the wireless cards that allow this. It is quite important from a performance point of view since the drivers are not very optimized on FreeBSD compared to Linux, I use my OPNsense with wireless and works fine.
These are the  channel width I can see (  ,ht/20, ht/40, ht/40):
 ifconfig -v ath0_wlan2 list chan
Channel   1 : 2412      MHz 11b          Channel   9 : 2452      MHz 11g
Channel   1 : 2412      MHz 11g          Channel   9 : 2452      MHz 11g ht/20
Channel   1 : 2412      MHz 11g ht/20    Channel   9 : 2452      MHz 11g ht/40-
Channel   1 : 2412      MHz 11g ht/40+   Channel  10 : 2457      MHz 11b
Channel   2 : 2417      MHz 11b          Channel  10 : 2457      MHz 11g
Channel   2 : 2417      MHz 11g          Channel  10 : 2457      MHz 11g ht/20
Channel   2 : 2417      MHz 11g ht/20    Channel  10 : 2457      MHz 11g ht/40-
Channel   2 : 2417      MHz 11g ht/40+   Channel  11 : 2462      MHz 11b
Channel   3 : 2422      MHz 11b          Channel  11 : 2462      MHz 11g
Channel   3 : 2422      MHz 11g          Channel  11 : 2462      MHz 11g ht/20
Channel   3 : 2422      MHz 11g ht/20    Channel  11 : 2462      MHz 11g ht/40-
Channel   3 : 2422      MHz 11g ht/40+   Channel  36 : 5180      MHz 11a
Channel   4 : 2427      MHz 11b          Channel  36 : 5180      MHz 11a ht/20
Channel   4 : 2427      MHz 11g          Channel  36 : 5180      MHz 11a ht/40+
Channel   4 : 2427      MHz 11g ht/20    Channel  40 : 5200      MHz 11a
Channel   4 : 2427      MHz 11g ht/40+   Channel  40 : 5200      MHz 11a ht/20
Channel   5 : 2432      MHz 11b          Channel  40 : 5200      MHz 11a ht/40-
Channel   5 : 2432      MHz 11g          Channel  44 : 5220      MHz 11a
Channel   5 : 2432      MHz 11g ht/20    Channel  44 : 5220      MHz 11a ht/20
Channel   5 : 2432      MHz 11g ht/40+   Channel  44 : 5220      MHz 11a ht/40+
Channel   5 : 2432      MHz 11g ht/40-   Channel  48 : 5240      MHz 11a
Channel   6 : 2437      MHz 11b          Channel  48 : 5240      MHz 11a ht/20
Channel   6 : 2437      MHz 11g          Channel  48 : 5240      MHz 11a ht/40-
Channel   6 : 2437      MHz 11g ht/20    Channel 149 : 5745      MHz 11a
Channel   6 : 2437      MHz 11g ht/40+   Channel 149 : 5745      MHz 11a ht/20
Channel   6 : 2437      MHz 11g ht/40-   Channel 149 : 5745      MHz 11a ht/40+
Channel   7 : 2442      MHz 11b          Channel 153 : 5765      MHz 11a
Channel   7 : 2442      MHz 11g          Channel 153 : 5765      MHz 11a ht/20
Channel   7 : 2442      MHz 11g ht/20    Channel 153 : 5765      MHz 11a ht/40-
Channel   7 : 2442      MHz 11g ht/40+   Channel 157 : 5785      MHz 11a
Channel   7 : 2442      MHz 11g ht/40-   Channel 157 : 5785      MHz 11a ht/20
Channel   8 : 2447      MHz 11b          Channel 157 : 5785      MHz 11a ht/40+
Channel   8 : 2447      MHz 11g          Channel 161 : 5805      MHz 11a
Channel   8 : 2447      MHz 11g ht/20    Channel 161 : 5805      MHz 11a ht/20
Channel   8 : 2447      MHz 11g ht/40-   Channel 161 : 5805      MHz 11a ht/40-
Channel   9 : 2452      MHz 11b          Channel 165 : 5825*     MHz 11a

they can be setup in the cmd line:
ifconfig ath0_wlan1 channel 36:ht/40
Describe the solution you like
We need some changes in the current wireless page to allow this selection.
Describe alternatives you considered
The current alternative I am using is just configurint this after boot with a bash script.
Additional context
This ticket is related with the wireless fix that allowed 5Ghz channels to be selected:  https://github.com/opnsense/core/pull/6963.
My current wireless card crashes with certain configurations (probably a driver bug on ht/20?) but I am happy to test the improvement fixes if needed.

@adamast0r increasing the heat with 6946f27 without leaving the known territory just yet. Let me know if this works for you still as I don't have an actual card to test against at the moment
BTW, do you know which one is the default? 20, 40+, 40-?
Cheers,
Franco

I can confirm that still works here:

on my WLE200NX, Atheros chipset AR9280 when I don't specify the default in the command line:
ifconfig ath0_wlan1 channel 36:ht;
It seems to be going to 40+.
ath0_wlan1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: WirelessTestl (opt1)
        ether 00:00:00:00:00:00
        inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
        groups: wlan
        ssid WirelessTest channel 36 (5180 MHz 11a ht/40+) bssid 00:00:00:00:00:00
        regdomain FCC country US ecm authmode WPA2/802.11i privacy MIXED
        deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 17 mcastrate 6
        mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 8 shortgi -ldpc
        -uapsd wme burst dtimperiod 1 -dfs
        parent interface: ath0
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11na <hostap>
        status: running
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

Not entirely sure but probably the safest would by default not specify any width in the command line and allow the cards to go to the values they were designed to go? If the interface is selected to somehting else change to the value selected.

I read a little about the channel width and 20 MHZ appears to be the standard size (also for compatibility's sake) and avoids tainting neighbouring channels. So that's ok to use the values as presented (eventually not omitting the channel width in the ifconfig ht command to set it).
Pretty interesting: https://forums.freebsd.org/threads/wifi-operation-in-accespoint-mode-along-with-maximum-transmitter-power-in-the-bridge-with-ethenet-cards.86482/

The channel bandwidth in HT20 mode is 20 MHz, and the channel bandwidth in HT40 mode is 40 MHz. Two neighboring 20 MHz channels are bundled to form a 40 MHz channel. One channel functions as the main channel, and the other as the auxiliary channel. The main channel sends Beacon packets and data packets, and the auxiliary channel sends other packets. When the HT40 mode is used in the 2.4 GHz frequency band, there is only one non-overlapping channel. Therefore, you are not advised to use the HT40 mode in the 2.4 GHz frequency band.
Two neighboring 20 MHz channels are bundled to form a 40 MHz channel. If the center frequency of the main 20 MHz channel is higher than that of the auxiliary channel, 40MHz-plus is displayed; otherwise, 40MHz-minus is displayed. For example, if the center frequency 149 and the center frequency 153 reside on two 20 MHz channels, 149plus indicates that the two 20 MHz channels are bundled to form a 40 MHz channel


Soundcloud Unfollow is incorrectly listing some followers as unfollowers

I just discovered that Soundcloud Unfollow is actually listing some followers as non-followers. I only spotted this by chance and now I don't have a clue as to how many actual followers I have stopped following because of this bug. This is very awkward and your website has no contact details. How many other users have fallen victim to this bug? It should be fixed or shut down. I realise this is a "use at your own risk" scenario but I have spent considerable time cultivating my follower list. This is embarrassing for me as my unfollowing actions will be seen by some as a real insult. These are people I would never want to insult and I have no way of even finding who they are to re-follow or apologise to!
Here are two examples I know of:
my soundcloud username is bonggnostic
Two results that should not have been listed are:
Arkestar
Lambmother
and only god knows how many others

this developer doesn't seem to care

Seems like notifications from my own projects are turned off so I didn't see your issue until yesterday.
First of all - this application is for mainly for my personal use and it runs on my development server. I don't mind if others use it, since it is a public server but I take no responsibility whatsoever for any harm it can cause. As you mentioned, use it at you own risk.
Good news is I think I've found the problem. There was a limit imposed on two of the api calls which restricted  them to 500 users each. I saw that you have like 650 followers so the limit was probably the problem. If you are up to it, try again and let me now if it works.
At the same time I also fixed a couple of thing that annoyed me:

The top header is now smaller so it won't occupy as much screen space (better on mobile units).
Headers with users name are now clickable and they don't overwrite text below.

Hello, is there a place where I can use this app?

No, sorry. This is an archived project since Soundcloud changed its api.

pity... thanks for replying.


MDE: Limited periodic scanning

Currently the docs state that Defender Antivirus is able to do limited-periodic scanning (LPS) when disabled or uninstalled, but states it is not available when in passive mode. I think it should be the other way around, I double checked with a few of my test machines by the following:

Confirm 3rd party AV is installed on machine
Get-MpComputerStatus in elevated PowerShell states AMRunningMode: "SxS Passive Mode"
Defender is able to do LPS in the UI.

Also if you set the "DisableAntiSpyware" to 1 in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender
the enabled LPS option switches back to "Off".

@theonlybrand Please indicate which document you are referring to. Thanks

https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/microsoft-defender-antivirus-compatibility?view=o365-worldwide#how-microsoft-defender-antivirus-affects-defender-for-endpoint-functionality

@theonlybrand Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/10098
Once the author approves, the changes will be live.
Thanks
Sri

@yogkumgit This can be closed.

@msbemba Thank you very much for the contribution and updating the documentation with PR. @theonlybrand Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Avoid string copies in shims

There's a better pattern for moving strings across the FFI instead of copying them.
It doesn't much that we're copying when we don't have to, but when we get the opportunity for breaking changes, we might as well make the code a bit more correct.
Need to wait for a major version bump.
From https://github.com/brson/wasm-opt-rs/issues/95

Yep, and the way to avoid a copy is by passing Pin<&mut CxxString> from Rust to C++, receiving it as std::string&, and calling std::move. let_cxx_string! (which you are already using) produces a local binding of type Pin<&mut CxxString>, so the deref from that to &CxxString in your Rust code is what forces a copy to be done afterward in C++.

Fixed https://github.com/brson/wasm-opt-rs/pull/120


MST-3 slash Issue

MST-3 slash Issue
Auditor: Movebit
Code: MCR Settlement Contract
Severity: Discussion
Status: Pending
Code Location:
protocol-units/settlement/mcr/contracts/src/staking/MovementStaking.sol
Descriptions:
The slash mechanism makes the nodes accountable for their actions and can deter malicious
attack behavior and negligence, ensuring a robust and trustworthy network infrastructure. But
the slash function in the contract can only manipulate data from msg.sender, meaning it
can only be called by the user who is being slashed himself, and all the parameters are
controllable, it's needed to make sure that this is by design.
Suggestion:
It is recommended to ensure that this is as designed.

This is considered an "accepted risk" for this potion of the audit as with any other issues tagged "decentralization."

Also, for clarification, the usage of msg.sender is to identify the domain. Each domain can only slash stake that is staked to them. This is similar to the usage in #452 ; the domain contract is supposed to call the method.


Disable failing JDK 20-ea build for now

See the analysis in #418 for context.
Suggested commit message:
Disable failing JDK 20-ea build for now (#419)

The build fails due to
openjdk/jdk20@2cb64a75578ccc15a1dfc8c2843aa11d05ca8aa7; the upcoming
Error Prone release includes a workaround for this:
google/error-prone@df033f03cb55c3f26221660ac5ea49bbaeeab289.

The enable terminology is used more often I would say, so went with the hyphen option :).


tkn pac resolve doesn't work with git_auth_secret

since it doesn't get replaced it will fail...

as controller creates the secret and replaces in pipelinerin
for cli resolves.. are we thinking do the same? creating secret using cli?

I was thinking, we could just create a fake random secret on cluster and pass the name to the git_auth_secret variable so we could just make it works.
If user really want to setup a secret for private repo, they could pre-setup a secret and use the -p git_auth_secret=secret-name command line.

If we generate a fake secret and pass then may be  end user get confused thinking that by default it creates some secret :thinking:
How about adding git_auth_secret only when user pass it using  -p git_auth_secret=secret-name command line ?

@savitaashture  that sounds a better idea to me!


fix for the textchatservice chat (for krnl users)

i'm sorry if you didnt understand the request name

yes


Anthos icon is missing

Hello @airmisdata
Private Cloud icons design is in progress.
Following cloud providers will be added.

VMware Tanzu
Google Anthos
Redhat Openshift