Failed to build iOS app with error: Target debug_unpack_ios failed: Exception: Binary does not contain

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Create a new Flutter project with flutter create my_app
Add DJI mobile SDK to pubspec.yaml dji: ^1.0.10
Open the project in Xcode by running open ios/Runner.xcworkspace
Change the architecture to arm64
Select a valid development team, bundle identifier, and provisioning profile for the app
Connect a real iOS device and run the app with flutter run

Expected results
The app builds and runs on the device without errors.
Actual results
The app fails to build with the following error:
Failed to build iOS app
Could not build the precompiled application for the device.
Error (Xcode): Target debug_unpack_ios failed: Exception: Binary /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/Debug-iphoneos/Flutter.framework/Flutter does not contain . Running lipo -info:

Error launching application on Stoyan’s iPhone.

The app is working, when I run it through the simulator.
Code sample
N/A
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
log.txt
Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.7.11, on macOS 13.0 22A380 darwin-arm64 (Rosetta), locale bg-BG)
    • Flutter version 3.7.11 on channel stable at /Users/bg2/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f72efea43c (8 days ago), 2023-04-11 11:57:21 -0700
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/bg2/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.12.0

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

[✓] Android Studio (version 2022.2)
    • 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 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (4 available)
    • Stoyan’s iPhone (mobile) • 00008101-0012503C1445001E            • ios            • iOS 16.5 20F5039e
    • iPhone 14 Pro (mobile)   • 90C34729-016F-4273-AEA9-6ADBF445855E • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)          • macos                                • darwin-arm64   • macOS 13.0 22A380 darwin-arm64 (Rosetta)
    • Chrome (web)             • chrome                               • web-javascript • Google Chrome 112.0.5615.121

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

• No issues found!

Thanks for the report @SSIvanov19
You are running on physical device and selecting arm64 as arch, but in the logs, EXCLUDED_ARCHS is showing as arm64 itself and hence the error you are getting.
You've excluded arm64, but that's the physical phone architecture. I suggest you completely remove all EXCLUDED_ARCHS from that file, and let Flutter manage the allowed architectures for you based on what plugins you're using and what simulator types are available.
I'll go ahead and close as the error you are reporting is expected based on my explanation above.

Thank you for your response!
After changing the required settings, the project is building fine. But I have a new error, when running the app on my iPhone. When I try to run it, it says "Unable to Verify App", "An internet connection is required to verify trust of developer "Apple Development:  ()". This app will not be available until verified." I am connected to internet and I have trusted my certificated in Settings -> General -> VPN & Device Management -> Developer App. But when I try to click on Verify Apps, it does nothing. Here are the last logs for flutter run -v:
[   +6 ms] Installing and launching...
[        ] Debugging is enabled, connecting to observatory
[   +5 ms] executing: script -t 0 /dev/null /Users/bg2/Development/flutter/bin/cache/artifacts/ios-deploy/ios-deploy --id 00008101-0012503C1445001E --bundle build/ios/iphoneos/Runner.app --app_deltas build/ios/app-delta --debug --no-wifi --args --enable-dart-profiling
--enable-checked-mode --verify-entry-points
[  +42 ms] [....] Waiting for iOS device to be connected
[ +154 ms] [....] Using 00008101-0012503C1445001E (D54pAP, iPhone 12 Pro Max, iphoneos, arm64e, 16.5, 20F5039e) a.k.a. 'Stoyan’s iPhone'.
[        ] ------ Install phase ------
[        ] [  0%] Found 00008101-0012503C1445001E (D54pAP, iPhone 12 Pro Max, iphoneos, arm64e, 16.5, 20F5039e) a.k.a. 'Stoyan’s iPhone' connected through USB, beginning install
[ +262 ms] [  5%] TransferringPackage
[        ] [  5%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/META-INF/ to device
[        ] [  5%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/META-INF/com.apple.ZipMetadata.plist to device
[        ] [  5%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/ to device
[        ] [  6%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/ to device
[        ] [  6%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/ to device
[        ] [  6%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/_CodeSignature/ to device
[        ] [  6%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/_CodeSignature/CodeResources to device
[   +1 ms] [  7%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/_CodeSignature/CodeResources to device
[        ] [  7%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Info.plist to device
[        ] [  7%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Runner to device
[   +5 ms] [  8%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Runner to device
[        ] [  8%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/com.apple.deltainstallcommands.com.example.droneapp to device
[        ] [  8%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/ to device
[        ] [  8%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIWidget.framework/ to device
[        ] [  9%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIWidget.framework/ to device
[        ] [  9%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIWidget.framework/_CodeSignature/ to device
[        ] [  9%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIWidget.framework/_CodeSignature/CodeResources to device
[        ] [ 10%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIWidget.framework/_CodeSignature/CodeResources to device
[        ] [ 10%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIWidget.framework/DJIWidget to device
[  +72 ms] [ 10%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIWidget.framework/Info.plist to device
[        ] [ 11%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIWidget.framework/Info.plist to device
[        ] [ 11%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxMobileEvents.framework/ to device
[        ] [ 11%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxMobileEvents.framework/_CodeSignature/ to device
[        ] [ 12%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxMobileEvents.framework/_CodeSignature/ to device
[        ] [ 12%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxMobileEvents.framework/_CodeSignature/CodeResources to device
[        ] [ 12%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxMobileEvents.framework/MapboxMobileEvents to device
[  +53 ms] [ 12%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxMobileEvents.framework/Info.plist to device
[        ] [ 13%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxMobileEvents.framework/Info.plist to device
[        ] [ 13%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxAnnotationExtension.framework/ to device
[        ] [ 13%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxAnnotationExtension.framework/_CodeSignature/ to device
[        ] [ 14%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxAnnotationExtension.framework/_CodeSignature/ to device
[        ] [ 14%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxAnnotationExtension.framework/_CodeSignature/CodeResources to device
[        ] [ 14%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxAnnotationExtension.framework/MapboxAnnotationExtension to device
[  +15 ms] [ 14%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxAnnotationExtension.framework/Info.plist to device
[        ] [ 15%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/MapboxAnnotationExtension.framework/Info.plist to device
[        ] [ 15%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIUXSDK.framework/ to device
[        ] [ 15%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIUXSDK.framework/_CodeSignature/ to device
[        ] [ 16%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIUXSDK.framework/_CodeSignature/ to device
[        ] [ 16%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIUXSDK.framework/_CodeSignature/CodeResources to device
[        ] [ 16%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIUXSDK.framework/DJIUXSDK to device
[ +148 ms] [ 17%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIUXSDK.framework/DJIUXSDK to device
[ +194 ms] [ 18%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJIUXSDK.framework/DJIUXSDK to device
[        ] [ 18%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/FFmpeg.framework/ to device
[        ] [ 18%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/FFmpeg.framework/_CodeSignature/ to device
[        ] [ 19%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/FFmpeg.framework/_CodeSignature/ to device
[        ] [ 19%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/FFmpeg.framework/_CodeSignature/CodeResources to device
[        ] [ 19%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/FFmpeg.framework/FFmpeg to device
[ +172 ms] [ 20%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/FFmpeg.framework/FFmpeg to device
[ +231 ms] [ 21%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/FFmpeg.framework/FFmpeg to device
[  +23 ms] [ 21%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/ to device
[        ] [ 21%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/_CodeSignature/ to device
[        ] [ 22%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/_CodeSignature/ to device
[        ] [ 22%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/_CodeSignature/CodeResources to device
[        ] [ 22%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +102 ms] [ 23%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +253 ms] [ 24%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +143 ms] [ 25%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +175 ms] [ 26%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +314 ms] [ 27%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +119 ms] [ 28%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +140 ms] [ 29%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +128 ms] [ 30%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +134 ms] [ 31%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +155 ms] [ 32%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +115 ms] [ 33%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[ +124 ms] [ 34%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/Mapbox.framework/Mapbox to device
[   +2 ms] [ 34%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/dji.framework/ to device
[        ] [ 34%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/dji.framework/_CodeSignature/ to device
[        ] [ 35%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/dji.framework/_CodeSignature/ to device
[        ] [ 35%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/dji.framework/_CodeSignature/CodeResources to device
[        ] [ 35%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/dji.framework/dji to device
[  +17 ms] [ 36%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/dji.framework/dji to device
[        ] [ 36%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/dji.framework/Info.plist to device
[        ] [ 36%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/mapbox_gl.framework/ to device
[        ] [ 36%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/mapbox_gl.framework/_CodeSignature/ to device
[        ] [ 37%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/mapbox_gl.framework/_CodeSignature/ to device
[        ] [ 37%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/mapbox_gl.framework/_CodeSignature/CodeResources to device
[        ] [ 37%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/mapbox_gl.framework/mapbox_gl to device
[  +54 ms] [ 38%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/mapbox_gl.framework/mapbox_gl to device
[        ] [ 38%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/mapbox_gl.framework/Info.plist to device
[        ] [ 38%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/geolocator_apple.framework/ to device
[        ] [ 39%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/geolocator_apple.framework/ to device
[        ] [ 39%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/geolocator_apple.framework/_CodeSignature/ to device
[        ] [ 39%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/geolocator_apple.framework/_CodeSignature/CodeResources to device
[        ] [ 39%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/geolocator_apple.framework/geolocator_apple to device
[   +3 ms] [ 40%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/geolocator_apple.framework/geolocator_apple to device
[        ] [ 40%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/geolocator_apple.framework/Info.plist to device
[        ] [ 40%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/ to device
[        ] [ 41%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/ to device
[        ] [ 41%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/_CodeSignature/ to device
[        ] [ 41%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/_CodeSignature/CodeResources to device
[   +2 ms] [ 41%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[  +40 ms] [ 42%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[ +191 ms] [ 43%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[ +229 ms] [ 44%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[ +244 ms] [ 45%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[ +245 ms] [ 46%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[ +252 ms] [ 47%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[ +227 ms] [ 48%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[ +165 ms] [ 49%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/Frameworks/DJISDK.framework/DJISDK to device
[   +3 ms] [ 49%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/Payload/Runner.app/PkgInfo to device
[        ] [ 49%] Copying /Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/app-delta/Runner.app.Ps0zbT/Runner.app_sparse.ipa/ManifestCache.plist to device
[+1015 ms] [ 52%] CreatingStagingDirectory
[        ] [ 57%] ExtractingPackage
[        ] [ 60%] InspectingPackage
[ +109 ms] [ 65%] PreflightingApplication
[        ] [ 67%] PatchingApplication
[+2284 ms] [ 70%] VerifyingApplication
[+2601 ms] [ 75%] CreatingContainer
[  +28 ms] [ 80%] InstallingApplication
[  +17 ms] [ 85%] PostflightingApplication
[  +16 ms] [ 90%] SandboxingApplication
[  +35 ms] [ 95%] GeneratingApplicationMap
[+1058 ms] [100%] InstallComplete
[ +586 ms] [100%] Installed package build/ios/iphoneos/Runner.app
[  +69 ms] ------ Debug phase ------
[        ] Starting debug of 00008101-0012503C1445001E (D54pAP, iPhone 12 Pro Max, iphoneos, arm64e, 16.5, 20F5039e) a.k.a. 'Stoyan’s iPhone' connected through USB...
[ +524 ms] [  0%] Looking up developer disk image
[  +19 ms] [ 95%] Developer disk image mounted successfully
[  +48 ms] Symbol Path: /Users/bg2/Library/Developer/Xcode/iOS DeviceSupport/16.5 (20F5039e) arm64e/Symbols
[ +431 ms] [100%] Connecting to remote debug server
[        ] -------------------------
[ +300 ms] (lldb) command source -s 0 '/tmp/72C6B1D8-8C18-4DC7-BE7A-9302BCDF24ED/fruitstrap-lldb-prep-cmds-00008101_0012503C1445001E'
[        ] Executing commands in '/tmp/72C6B1D8-8C18-4DC7-BE7A-9302BCDF24ED/fruitstrap-lldb-prep-cmds-00008101_0012503C1445001E'.
[        ] (lldb)     platform select remote-'ios' --sysroot '/Users/bg2/Library/Developer/Xcode/iOS DeviceSupport/16.5 (20F5039e) arm64e/Symbols'
[        ]   Platform: remote-ios
[        ]  Connected: no
[        ]    Sysroot: /Users/bg2/Library/Developer/Xcode/iOS DeviceSupport/16.5 (20F5039e) arm64e/Symbols
[        ]   SDK Path: "/Users/bg2/Library/Developer/Xcode/iOS DeviceSupport/16.5 (20F5039e) arm64e/Symbols"
[        ] (lldb)     target create "/Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/iphoneos/Runner.app"
[+6408 ms] Current executable set to '/Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/iphoneos/Runner.app' (arm64).
[   +3 ms] (lldb)     script fruitstrap_device_app="/private/var/containers/Bundle/Application/C89A21F8-71C3-4B54-916D-F049E8A863E5/Runner.app"
[        ] (lldb)     script fruitstrap_connect_url="connect://<IP_ADDRESS>:53670"
[        ] (lldb)     script fruitstrap_output_path=""
[        ] (lldb)     script fruitstrap_error_path=""
[        ] (lldb)     target modules search-paths add /usr "/Users/bg2/Library/Developer/Xcode/iOS DeviceSupport/16.5 (20F5039e) arm64e/Symbols/usr" /System "/Users/bg2/Library/Developer/Xcode/iOS DeviceSupport/16.5 (20F5039e) arm64e/Symbols/System"
"/private/var/containers/Bundle/Application/C89A21F8-71C3-4B54-916D-F049E8A863E5" "/Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/iphoneos" "/var/containers/Bundle/Application/C89A21F8-71C3-4B54-916D-F049E8A863E5"
"/Users/bg2/Documents/cup-2022-yottabyte/droneapp/build/ios/iphoneos" /Developer "/Users/bg2/Library/Developer/Xcode/iOS DeviceSupport/16.5 (20F5039e) arm64e/Symbols/Developer"
[  +24 ms] (lldb)     command script import "/tmp/72C6B1D8-8C18-4DC7-BE7A-9302BCDF24ED/fruitstrap_00008101_0012503C1445001E.py"
[   +3 ms] (lldb)     command script add -f fruitstrap_00008101_0012503C1445001E.connect_command connect
[        ] (lldb)     command script add -s asynchronous -f fruitstrap_00008101_0012503C1445001E.run_command run
[        ] (lldb)     command script add -s asynchronous -f fruitstrap_00008101_0012503C1445001E.autoexit_command autoexit
[        ] (lldb)     command script add -s asynchronous -f fruitstrap_00008101_0012503C1445001E.safequit_command safequit
[        ] (lldb)     connect
[  +23 ms] (lldb)     run
[  +85 ms] error: The operation couldn’t be completed. Unable to launch com.example.droneapp because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user.
[   +1 ms] Could not run build/ios/iphoneos/Runner.app on 00008101-0012503C1445001E.
[   +5 ms] Try launching Xcode and selecting "Product > Run" to fix the problem:
[        ]   open ios/Runner.xcworkspace
[   +2 ms] Installing and launching... (completed in 20,7s)
[        ] Error launching application on Stoyan’s iPhone.
[  +10 ms] "flutter run" took 112 663ms.
[  +13 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:722:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1257:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand (package:args/command_runner.dart:209:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:283:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:91:3)
           <asynchronous suspension>

Please file a new issue for it so that it can tracked better.


Test failed. Error: Dialog Error: Protocol error.

I don't know why it happens.

This issue has no reproducible steps. Please re-open this issue if it still occurs.


upload polygon data for DRSRS

Here is a description

Eric just determined how to upload the data. The coordinate system was causing problems. He just figured it out as of this morning. Now he's looking for a larger data set to work with.

Should have the code ready for review tomorrow March 27.

Mocked up coordinates are working fine. What's left is to modify the getEvents to allow for additional parameters.


Fix wrong version help string in pyflyte register

TL;DR
The click.option("-v", "--version", ..) currently has the help string from @click.option("--service-account", ...).
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

@fg91  can you dco sign off?

@pingsutw could you please merge?

Merged, thank you


fix-extraEnv-default-value

Summary
I messed up the default value for extraEnv in #316. This fixes the jobserver.extraEnv to be an array, which is what the template is expecting
Without this change, if trying to use jobserver's extraEnvs, you get this error:
cannot overwrite table with non table for mattermost-enterprise-edition.global.features.jobserver.extraEnv

Hello @ruckc,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

the tests need to be retried

@spirosoik / @pfltdv / @stylianosrigas - can you review?

@pfltdv did you give a try to test locally?

@pfltdv did you give a try to test locally?

@spirosoik Yes tested with and without jobserver extra vars. Had no issue at both executions.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

@ruckc any reason this wasn't merged / updated anymore? Just saw that i've just create a PR for the same issue.

@jonathanwiemers - no real reason, other than the 3 week lag on feedback.  My need for this was removed as we moved away from mattermost due to the integration and license headaches.

/update-branch


InvalidArgumentError Incompatible shapes when multi_gpu_model used on LSTM model in TF 2.0

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.0.0-dev20190228
Python version: 3.7
CUDA/cuDNN version: 10/7.4
GPU model and memory:  Tesla M60 on AWS g3.8xlarge

Describe the current behavior
multi_gpu_model fails to parallelize LSTM model. Things I've tried without success:

setting  cpu_relocation=True parameter
disabling eager mode

Describe the expected behavior
the code below should run instead of giving an error.
Code to reproduce the issue
import tensorflow as tf
from tensorflow.keras.datasets import imdb
from tensorflow.keras.preprocessing.sequence import pad_sequences
from tensorflow.keras.models import Sequential
from tensorflow.keras.layers import Dense, LSTM, Embedding
from tensorflow.keras.utils import multi_gpu_model

vocab_size= 20000
maxlen=80

(X_train, y_train), (X_test, y_test) = \
    imdb.load_data(num_words=vocab_size)

X_train_pad = pad_sequences(X_train, maxlen=maxlen)
X_test_pad = pad_sequences(X_test, maxlen=maxlen)

with tf.device('/cpu:0'):
    model = Sequential([
        Embedding(vocab_size, 100, input_length=maxlen),
        LSTM(64, dropout=0.2, recurrent_dropout=0.2),
        Dense(1, activation='sigmoid')
    ])

model = multi_gpu_model(model, 2)

model.compile(loss='binary_crossentropy',
              optimizer='rmsprop',
              metrics=['accuracy'])

model.fit(X_train_pad, y_train,
          batch_size=2048,
          epochs=2,
          shuffle=True)

Other info / logs
W0301 07:00:25.055628<PHONE_NUMBER>90560 tf_logging.py:161] <tensorflow.python.keras.layers.recurrent.UnifiedLSTM object at 0x7f45f84f5470>: Note that this layer is not optimized for performance. Please use tf.keras.layers.CuDNNLSTM for better performance on GPU.

Epoch 1/2

---------------------------------------------------------------------------
InvalidArgumentError                      Traceback (most recent call last)
<ipython-input-6-827e285c76cb> in <module>
     33           batch_size=2048,
     34           epochs=2,
---> 35           shuffle=True)

~/miniconda3/envs/tf2/lib/python3.7/site-packages/tensorflow/python/keras/engine/training.py in fit(self, x, y, batch_size, epochs, verbose, callbacks, validation_split, validation_data, shuffle, class_weight, sample_weight, initial_epoch, steps_per_epoch, validation_steps, validation_freq, max_queue_size, workers, use_multiprocessing, **kwargs)
    871           validation_steps=validation_steps,
    872           validation_freq=validation_freq,
--> 873           steps_name='steps_per_epoch')
    874
    875   def evaluate(self,

~/miniconda3/envs/tf2/lib/python3.7/site-packages/tensorflow/python/keras/engine/training_arrays.py in model_iteration(model, inputs, targets, sample_weights, batch_size, epochs, verbose, callbacks, val_inputs, val_targets, val_sample_weights, shuffle, initial_epoch, steps_per_epoch, validation_steps, validation_freq, mode, validation_in_fit, prepared_feed_values_from_dataset, steps_name, **kwargs)
    349
    350         # Get outputs.
--> 351         batch_outs = f(ins_batch)
    352         if not isinstance(batch_outs, list):
    353           batch_outs = [batch_outs]

~/miniconda3/envs/tf2/lib/python3.7/site-packages/tensorflow/python/keras/backend.py in __call__(self, inputs)
   3215         value = math_ops.cast(value, tensor.dtype)
   3216       converted_inputs.append(value)
-> 3217     outputs = self._graph_fn(*converted_inputs)
   3218     return nest.pack_sequence_as(self._outputs_structure,
   3219                                  [x.numpy() for x in outputs])

~/miniconda3/envs/tf2/lib/python3.7/site-packages/tensorflow/python/eager/function.py in __call__(self, *args, **kwargs)
    523       raise TypeError("Keyword arguments {} unknown. Expected {}.".format(
    524           list(kwargs.keys()), list(self._arg_keywords)))
--> 525     return self._call_flat(args)
    526
    527   def _filtered_call(self, args, kwargs):

~/miniconda3/envs/tf2/lib/python3.7/site-packages/tensorflow/python/eager/function.py in _call_flat(self, args)
    592     # Only need to override the gradient in graph mode and when we have outputs.
    593     if context.executing_eagerly() or not self.outputs:
--> 594       outputs = self._inference_function.call(ctx, args)
    595     else:
    596       self._register_gradient()

~/miniconda3/envs/tf2/lib/python3.7/site-packages/tensorflow/python/eager/function.py in call(self, ctx, args)
    380             attrs=("executor_type", executor_type,
    381                    "config_proto", config),
--> 382             ctx=ctx)
    383       # Replace empty list with None
    384       outputs = outputs or None

~/miniconda3/envs/tf2/lib/python3.7/site-packages/tensorflow/python/eager/execute.py in quick_execute(op_name, num_outputs, inputs, attrs, ctx, name)
     64     else:
     65       message = e.message
---> 66     six.raise_from(core._status_to_exception(e.code, message), None)
     67   except TypeError as e:
     68     if any(ops._is_keras_symbolic_tensor(x) for x in inputs):

~/miniconda3/envs/tf2/lib/python3.7/site-packages/six.py in raise_from(value, from_value)

InvalidArgumentError: Incompatible shapes: [1024,64] vs. [2048,64]
	 [[{{node sequential_5_1/unified_lstm_5/while/body/_1008/mul_6}}]]
	 [[training_3/RMSprop/gradients/loss_5/dense_5_loss/binary_crossentropy/Mean_grad/Prod/_842]] [Op:__inference_keras_scratch_graph_32546]

Thanks for reporting the issue and sorry for the late reply. Let me take some time to troubleshoot the issue.

Thanks @qlzh727, let me know if I can help you with anything.

Is multi_gpu_model not recommended any longer with TF 2.0 ?

In 2.0  we will recommend user to use distribution strategy. Having said that, I don't see the multi_gpu_model gets deprecated, @fchollet, should we actually deprecate multi_gpu_model in v2 since istribution strategy is the new recommended way for model sharding?

Update on this bug:
replacing LSTM(64, dropout=0.2, recurrent_dropout=0.2) with LSTM(64, dropout=0.2) in the model definition runs fine, albeit the warnings:
W0321 18:52:50.309778<PHONE_NUMBER>77184 tf_logging.py:161] <tensorflow.python.keras.layers.recurrent.UnifiedLSTM object at 0x7fb7748c2748>: Note that this layer is not optimized for performance. Please use tf.keras.layers.CuDNNLSTM for better performance on GPU.
W0321 18:52:50.793717<PHONE_NUMBER>77184 deprecation.py:506] From /home/ubuntu/miniconda3/envs/myenv/lib/python3.7/site-packages/tensorflow/python/keras/backend.py:4081: calling dropout (from tensorflow.python.ops.nn_ops) with keep_prob is deprecated and will be removed in a future version.
Instructions for updating:
Please use `rate` instead of `keep_prob`. Rate should be set to `rate = 1 - keep_prob`.

I suspect the problem is somewhere in the new bundled LSTM layer that automatically chooses where to allocate the weights and whether to use CuDNN or not. In fact CuDNN layers need to be on the GPU and do not support recurrent_dropout.
Also, notice that when the LSTM layer is defined without the recurrent dropout, it's allocated on the GPU regardless of the context setter. This seems similar to #26244

Interesting, thanks for sharing the finding, which will narrow down the cause of the issue.
Regarding to the device context, it has been recently updated with https://github.com/tensorflow/tensorflow/commit/584ad2f575ffc644accb8f0d8c4e1038edd42412. You can try updating your installed TF with nightly-2.0-preview and it should fixed issue.

Looks like nightly builds are not available for mac py3.7? I get:
$ pip install tf-nightly-2.0-preview
Collecting tf-nightly-2.0-preview
  Could not find a version that satisfies the requirement tf-nightly-2.0-preview (from versions: )
No matching distribution found for tf-nightly-2.0-preview

I'll try on linux

Still getting this error in 2.1.0. Am I doing something wrong? I also get the No matching distribution error trying to install the nightly build on Ubuntu ....

Switching to MirroredStrategy seemed to fix it. Although I still can't install the nightly build ....

@ghego,
It is recommended to use Distribution Strategy over multi_gpu_model. Even the documentation of multi_gpu_model is not available in the Tensorflow Site.
Please refer the documentation for Distributed Training using Keras and Distributed Training Using Tensorflow for more information
Thanks!

Yes, this issue is 3 years old. I'm aware that Distribution Strategy is the way to go. I'll close it.


Hide #inspect and #to_s in docs.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

Every Object has these methods, so don't explicitly show them in docs.

Is it possible to use query filters to hide methods with those names at build time?

@EricFromCanada, it's probably possible to hide these in a similar way as in https://github.com/Homebrew/brew/pull/16831, but I'd rather get that merged first to avoid conflicts.

@reitermarkus Just adding this to .yardopts will do the trick: --query 'object.name != :inspect && object.name != :to_s'


Interview Request

This might be the oddest issue I've ever raised, and I can anticipate that the answer would normally be "No", but still, I'd like to try at least, so that when the time comes, at least I can tell people that "I had tried my best". So before asking for it directly and getting a “No” as the answer, let me start with something else, to pave my way to my questions.
I live in Canada, Toronto. One year, I was on my way to see the autumn maple leaves and was a bit lost, so I drove around the vast mostly-empty area until I was able to see a small shop, and I went in to ask for directions. I said “I’m a bit lost”, and before I was able to explain anything else, the shop owner asked me if I was there to see the “Bethune House”. Not knowing anything about this Bethune House, and having great difficulties to communicate with the heavily accented shop owner, I basically came out of the shop “empty handed”.
It was not until two or three years later when I heard that phrase “Bethune House” again, but this time it was from a Chinese person and I suddenly realized what it was, and I regret to have missed it ever since then, even until today. Yes, if you know what Bethune House is, it IS the Bethune Memorial House National Historic Site in Gravenhurst, Ontario, in memory and commemorates the life and achievements of Dr. Norman Bethune.
It’s in such a rural and remote area, which took me more than two and half hours to drive to get there, one won’t expect too much tourism traffic normally. Yet, Chinese from all over the world visit it, to pay their respects to Dr. Norman Bethune (and I will too sometime in future). So from that small shop owner’s perspective, any Chinese that shows up in that rural and remote area, is there to visit the Bethune House, which I’d say that he’s 99.9999% correct.
What such story has anything to do with this github repo? Well, let me reveal it in the end, but first let me explain why I need to ask my questions -- two folds:

Being a computer programmer, who is obsessed with version controlling everything, I had been looking for a plain text music notation for decades. I had almost settled with the ABC notation when I happened to stumble upon jianpu-ly, which I hadn’t imagined that such a thing would exist before. So now I am very curious why such a wonderful program ever exists. So I started to look up who Mr. Silas S. Brown is, but
Unlike youngsters nowadays who post everything about their lives on facebook, people in the computer world tend to leave as minimum digital footprint as possible. I’m like that and I found so is Mr. Silas S. Brown. Thus I want to interview him to satisfy my curiosity, to know more about him.

As put in his personal bio, Mr. Silas S. Brown is a partially-sighted computer scientist at Cambridge University in the UK, who come from West Dorset on the South-West peninsula of England. There isn’t much more personal information revealed in the English version of his self introduction, yet interestingly, he reveals himself much more in his Chinese version of self-introduction, from which we know that he involves with 剑桥大学中国文化促进协会 & 剑桥大学华乐团, and he self teach himself Chinese, which is amazing giving Chinese is the most difficult language to learn in the world.
I thought him to be an old professor but it turns out that he might be rather young, as he seems to be still attending Cambridge University in 1996 when he wrote Clara Empricost, but such a guess might be wrong.
So, now, finally, here are my interview questions (please don’t decline):

Please identify if there is anything wrong with the above guess work.
You seem to have learned Chinese by self teaching, with the help of gradint, a program for self-study of foreign languages, that you co-authorized, is that so?
How long did it take you to learn Chinese, and since what age did you start?
Why are you interested in learning Chinese, and are there many Chinese friends around you?
The jianpu-ly seems to be instigated by your 五线谱和盲文音乐软件, but still,
why jianpu? Why not the staff, or ABC notation or anything?
What are the challenges when you’re doing the jianpu-ly programming? It must be hard for any partially-sighted person.
Your eyes’ situation seems to have gone worse, and you’re now legally blind. Is it so or the situation hasn’t developed much.
May I know if you are born with the eye problem please? It must be very hard for anyone, let alone going to the universities, and being a professor.

I have many more questions but so far for now, as I’m afraid that they’ll be declined. For reasons behind all above, including my above story, I just think the world deserves to know better about the inventor and author of the jianpu-ly program, especially when jianpu is invented by a French / Genevan Jean-Jacques Rousseau, and it is only common/popular in East Asia, including Myanmar(Burma), Japan, Mainland China including Taiwan, and not a single person from those area cares enough to write such a helpful program.

Hi, you're right my home page needs more work.  I have a full site index but it's 166 pages so far & harder to navigate, so I guessed the home page had better have just a few basic links (like the most important software I've done), and link to the full index at the bottom.  The Chinese version of my homepage has a slightly different set of links: it prioritizes things that I've translated into Chinese and/or done in connection with Chinese.  Both the English and the Chinese versions of the homepage are basically slightly different subsets of the full site index (which I've also done in Chinese: I haven't yet managed to translate all the pages it links to, but at least the titles are there).
You might be interested in 梦姐's interview of me.  My condition is from birth, but it was misdiagnosed until 1993 when I was 15 years old.  (My eyes are OK but the brain is not talking with them correctly.  So basically a kind of brain damage.)
A lot changed in 1993.  We finally knew what was wrong with me and what to do about it.  I was given access to specialist magnification equipment and other help, trained to use a cane for navigation (finally I could confidently walk down a street without having to follow a wall), didn't have to see psychotherapists any more, and moved to more appropriate schooling.  My family bought a PC and a friend got us a C++ compiler (I joined ACCU the following year) and I started working on a music program.  (I had programmed school computers before, but this was going up a level.)
Then from 1995 to 1997 I did the final two years of my schooling at a specialist school for the blind in Worcester and that's where I did the automatic composition experiment.  (I recently talked about this at an English section of the Oxford China forum, here is the video; I'm hoping they will release a version with the Q&A included because the audience had some good questions.)
Then in 1997 I started my undergraduate degree at Cambridge, where I started to meet East Asian international students for the first time.
At that time, I had to use computers in Cambridge that were still running Windows 3 and Netscape 2, which tended to crash or mess things up whenever I tried to change the size and colours (as I needed to do for my condition).  So I wrote my Web Access Gateway to fix that.  Then I discovered that the East Asian students were unable to read emails from their parents because the university was refusing to install East Asian fonts (they said they didn't want to risk installing anything not required by a course), and I thought "I can fix this: I've got an access gateway" and added a feature to show hanzi etc as pictures, which made me hugely popular with the Chinese and Japanese students (although the Koreans were not interested; maybe they all had their own computers).  Eventually, an actual Chinese Studies lecturer started using it, and then I knew what I had to do: help her write a letter to the computing service explaining that East Asian fonts and input methods are indeed required by a course, so please install them properly.  They did, my server traffic fell to zero and I became a nobody again (but I'd done the right thing).
(I'm hoping that jianpu-ly will follow the same pattern.  Once the core Lilypond developers realize jianpu is important, and integrate it properly into Lilypond itself, we won't need my add-on script anymore, at least not for new scores that don't already use it.  It's a transitory fix.)
One of my Chinese classmates wanted to start a Chinese club and we started one.  I'd been involved in the computer society etc so I knew a bit about how to do student clubs, so I helped.  Their first website ran on my server along with the Access Gateway.  (Now it's all done on WeChat and I'm not sure how it works anymore, but I still say hi to them when I can.)  And later I encouraged some Chinese students to start a 华乐团 and I play flute with them sometimes.
I'm not a professor (perhaps I got too involved in helping Chinese people instead) but not to worry.
I met my wife when I was translating a talk from English into Chinese for a local group.  I asked if she'd like to take over translating, which unnerved her a bit but I showed her how I was using Wenlin to help, which she found interesting and we started to keep in touch.  When we eventually married, we had terrible trouble getting her a UK visa but got there in the end.  The first version of jianpu-ly was originally written to print a hymnal for her father, as he wanted to sing in a group in Hong Kong that was using 5-line music he couldn't read.  (Unfortunately I made quite a few copying mistakes, but his friend gave my version to their leadership and they thought it was a good idea and published their own official corrected version.  They didn't use jianpu-ly to do it though; I'm not sure what they used.)  I was hoping jianpu-ly would also be useful for our local Chinese orchestra, but they haven't used it much, just occasionally for a yangqin part or something if their Xunscore printouts are particularly difficult to read (but sometimes they just write things by hand).  Perhaps they'll use it more in the future.
There are still quite a number of Chinese people in Cambridge and in the UK and many of them still treat me as a friend (well occasionally they throw virtual knives at me but mostly we're good), which is nice.

Ah, it's so refreshing and dearing to read what you write, and the linked contents too.

I have a full site index but it's 166 pages so far & harder to navigate

Haha, I digged some of my "findings" from there, and apparently I'm missing quite a lot, :)
梦姐's interview really touches me, and I'd like to quote a few paragraphs,

In November 2021 a Master’s student who uses the Internet name “Dream” wanted to interview me to encourage disabled friends back home not to give up. . . the resulting video was viewed by hundreds of thousands of people
Title: story of a visually-impaired person who finished Cambridge’s Computer Science degree
. . .
Dream: After chatting with Silas it’s hard to express my feelings, seems to be tough and pure, he was visually impaired from birth and bullied, misdiagnosed, sent to a special school and tried to take his life but still chose to do good and help others as far as he could, I hope his life runs well

this part really touches me, and then I read this:

He hasn’t seen trees, sunlight, rain or snow and hasn’t even seen the face of a Chinese person. In the Western environment he probably heard many smears against China, but he can still choose to go and help those international students he’s never seen with his eyes, noble soul.

This comment is not just a hollow compliment. Take a look at this

I was invited to apply for a new lectureship at Manchester that specifically wanted what I’d worked on—but by this time I’d become involved in helping Cambridge’s local Chinese immigrants so much that I was worried what would happen to them if I left Cambridge for Manchester. 我在剑桥一两学院的研究员候选名单但进不去了，然后被邀请申请曼城的讲师任务，那时曼城特别对我的研究感兴趣。不过，那时候我也已经开始帮助剑桥的华人，我恐怕我离开剑桥去曼城也许使那些华人更困境，所以我留下了。

Indeed, noble soul!!
And lastly,

I'm hoping that jianpu-ly will follow the same pattern. Once the core Lilypond developers realize jianpu is important, and integrate it properly into Lilypond itself, we won't need my add-on script anymore . . .

No! Being a computer programmer, who is obsessed with version controlling everything, I firmly believe that jianpu-ly has it is place as a plain text music notation tool, and I'll be continue using and advocating it.
Thanks for all your answers,
Cheers & Best Regards,


Updates

:tada: This PR is included in version @giscus/react-v1.1.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @giscus/svelte-v1.1.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @giscus/vue-v1.1.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support selecting a specific Xcode project for xcodebuild through the SPI manifest

As reported by @groue in #1890 (thank you!), packages with multiple project files in the package root will not build as xcodebuild does not know which project file to use.
Passing the --project flag to xcodebuild fixes this. We should allow an Xcode project to be specified in the SPI manifest, just like we do for projects where we can not automatically detect the scheme.
For example, for GRDB:
env DEVELOPER_DIR="/Applications/Xcode-13.4.1.app" xcrun xcodebuild -IDEClonedSourcePackagesDirPathOverride="$PWD/.dependencies" -derivedDataPath "$PWD/.derivedData" build -project "GRDB.xcodeproj" -scheme "GRDBiOS" -destination "generic/platform=ios"

It would seem logical for this to be defined at the same level we currently define the scheme configuration inside the manifest, but that may change as we come to implement it.

Could you instead (or by default?) run xcodebuild for every project that you find (by filtering the directory contents with the xcodeproj extension)?

The problem with that is aggregating build success. We could require them all to succeed. However, say one is a sample project, we wouldn't want to mark the build as incompatible if that fails (easy to imagine as it's probably not part of CI).

You could still have a manifest flag for ultimate control. I was just thinking that the default of running all Xcode projects might reduce the number of interventions required.
I guess it's a relatively rare occurrence in the first place, however, so perhaps requiring intervention is not a problem.


Turn off smart builds

While the manifest generated ties together a release of automate, it is
still confusing to have components at different versions for chef
server. Also, automate depends on openresty from chef server, which
doesn't get changed often thus never picks up changes upstream.

A full build takes 13 minutes: https://buildkite.com/chef/chef-chef-server-master-habitat-build/builds/32#49c9309d-4aa6-4fbc-ae88-5cdbc26dd8a4
Seems worth it for the predictability of having everything build.


Release google-cloud-java v0.69.0

This pull request was generated using releasetool.
11-01-2018 10:50 PDT
Bigtable

Bigtable: Add integration test to test nonexistent row handling (#3870)

BigQuery

BigQuery: Add support for retreiving labels (#3879)
Fixes BigQuery getTableId with empty projectId (https://github.com/googleapis/google-cloud-java/pull/3808). (#3873)

Datastore

Added project ID in validation failure #3292 (#3875)

Spanner

Fix: writeAtLeastOnce should use a ReadWriteSession (#3882)

Video Intelligence

Regenerate video-intelligence client (#3865

Dependencies

Added explicit dependencies for surefile-junit4 in order to fix testing in offline mode.  (#3820)
Cleanup: Stop bundling test-jars (#3874)

Internal / Testing Changes

Fix search folder for BQDT synth output (#3878)
Bump next snapshot (#3862)

Release is at https://github.com/googleapis/google-cloud-java/releases/tag/v0.69.0


Send flush message to JS when position is ahead

In certain circumstances, a JS client can get channel positions that are
ahead of the message bus. When this happens, the client will not recieve
any more messages until the page is refreshed. This patch fixes that by:

(middleware) delivering a message on the __flush channel when the
condition is detected
(client) resetting all subscriptions to -1 when the __flush message
is recieved

Note: The 'ahead' condition happens when the Redis DB is flushed.
Although this is not a common operation, flush-resiliency is a desirable
property of many applications using Redis; this change improves the
flush resiliency of MessageBus from "new messages will be lost for an
indeterminate period of time" to "all old messages are lost, plus those
that happen until the client next polls".

Test failure looks spurious.

I do want to fix this for 2.0 but I would like a simpler solution if possible.

I really want something here but it feels a bit too complicated.
perhaps if we ever try to subscribe ahead message bus returns the "last id" in status, then client corrects it and if debugging is enabled reports something. Then we don't need a _flush channel and can simply use status


Lazy computation of array shape for statistical tests

Updates the computation of the number of data points in statistical tests to be lazy, allowing them to handle nan dimensional inputs

[x] Closes #9546
[x] Tests added / passed: 3728 passed, 230 skipped, 8 xfailed, 40 xpassed, 1 warning
[x] Passes pre-commit run --all-files

Can one of the admins verify this patch?
Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.

ok to test


ACLs / Company Accounts

Is it possible to define sub-accounts in one installation which can only view the tracking data, but for example not edit devices? Or define other limited access rights?
If not, is this planed?

Yes, it is possible. You can share device between user account. Some user accounts can be marked as readonly which would not allow them to edit anything except their own user settings.

@tananaev, where is that opiton to mark user accounts as readonly. From admin login I tried to edit user account but could not find any checkbox related to "Readonly". Below is screenshot.

Well, you have to install the latest version of Traccar first.

@tananaev do we have anywhere Changelog maintained for each version, so that it will be easy for us to see the list of features added or removed from the version.

Yes we do:
https://www.traccar.org/blog/category/releases/

@tananaev Thanks.


make a new curve editor node

learn what works from after effects first, see how it could be integrated


fix(paperless-ngx): Allow redis username to be overridden

As described in https://github.com/gabe565/charts/issues/551, under certain circumstances the redis connection seems to not work with the current chart due to an empty username in the redis connection string.
This PR would allow users to override the redis username (in my case, supplying default works), with an empty string remaining the default value.

@gabe565 could you please merge this as the Redis connection does not work for me unless the username is set to default


Implement config CAN message handling

Everything inside storage can be configured - think over the API inside data for that...

also check RXB0CON.RXFUL inside CAN message handler to be 1. And set it to 0 once done processing the message. In processing, read data from RXBnDm - just data, we should probably know the data length and we do not care about canID since we know what we receive only


Support fallback app types

Makes sense to me. its basically the way overriding values is handled in cocoa as well.


Misplaced error with document.createElement

/* @flow */
var sheet = document.createElement('style');
sheet.type = 'text/css';

[chris ~/Coding/flow-test]$ flow --version
Flow, a static type checker for JavaScript, version 0.13.1
[chris ~/Coding/flow-test]$ flow

/Users/chris/Coding/flow-test/a.js:2:13,43: call of method createElement
Function cannot be called on
/private/var/folders/4m/px1762nd6y515zdshl6_pz600000gn/T/flow/flowlib_133d8699/lib/dom.js:230:5,17: Document

Found 1 error

I assume it's erroring because document.createElement is annotated to return an HTMLElement, but HTMLElement doesn't have a type property. The issue is that the error message is on the wrong line and its message is incorrect.
Commenting out the third line (sheet.type = 'text/css';) or adding if (!(sheet instanceof HTMLStyleElement)) throw new Error("wrong"); between lines 2 and 3 causes the error to go away as expected.

I think your issue may be resolved as of 4 days ago, in f0745e1ca185985163d75b8b53c20d8232887cb5.
I tested against the latest commit on master and I don't get any errors.

That looks like it fixes the specific problem of the definitions not including a specialization for document.createElement('style'), but this issue was made more about the error message being nonsense and not pointing to the right thing. I'm okay with working around things that aren't listed yet in the definitions. It's the error messages that lead me down the wrong way that bug me. Here's another example of this issue:
/* @flow */
var script = document.createElement('script');
script.typo = 'text/css';

Oh, yeah. That error message is atrocious! Gonna leave this one open and I'll tag it because this is a good example of bad error message.

Just hit this and wasted an hour of my life. Crazytown!

 Can you share an example?

Exactly as above:

vs

webview.setAttribute('src', 'https://facebook.com'); works fine of course :)

It's not that it's not valid (perhaps depending on your point of view about Web Components), just that the error made me scratch my head for a very long time. The .src was a lot further down the file.

@jamesgpearce Gotcha. In this case, src isn't technically a property, so using setAttribute is the correct code. Regardless, the error message is a nightmare.
FWIW, until we fix the issue here, you can get a better error message out of Flow by adding an annotation: const webview: HTMLElement = document.createElement('webview').

@jamesgpearce Hey James. It's been a while since you surfaced this issue. We recently improved error messages around function overloads which resolves the original issue here, but we don't support document.registerElement or Web components in general yet, so calls to document.createElement with an unknown element type will still return just a normal HTMLElement. Standard instanceof refinement should still work in this case, but if it is still an issue for you, would you please open a new issue for Web component support? Thanks!


Handle block with intervals

Do you want to request a feature or report a bug?
feature
What is the current behavior?
Block handlers run on each block
What is the expected behavior?
Since block handlers have a big impact on indexing time, would be great to have an out-of-the-box handler to define an arbitrary block interval. E.g: for 10 blocks
blockHandlers
   - handler: handleBlockWithInterval
     interval: 10

#959

Duplicate of https://github.com/graphprotocol/graph-node/issues/959 - Please add a thumbs up to that issue and/or add a comment there if you want to voice your support or contribute some nuance/feedback for that feature request!


Convert choice adventure script from ash to ts

Still needs some validation & testing done but it feels weird that the choice adventure script is written in ash, not ts.
The main idea of this PR however is so that future changes can be written without pulling hair out because of the difference in language styles. Also possibly using other typescript modules.

PR has been tested and works fine

Thanks!


Is there a way to deploy the pages with Site Designs?

Is there a way to deploy pages with site design?
No where it was mentioned the limitations of site designs as not possible to deploy pages, not possible to deploy look up columns, not possible to add web parts to the pages etc.
Is there any documentation available for the limitations of the site design?

[X] Question

This is not currently supported, so you'd need to do this with extension hosted in Azure and then using remote provisioning techniques, like PnP provisioning engine.


I can't get the right value

I've wrote a code to get the NP's current value to put it in a TextView when a button is pressed. But, instead of getting the "x" value, I get "x+1". For example, when I select on NP 1, I get 2 on the TextView. Here is the code:
var v1 = np_1.value
btn_add.setOncClickListener{
    textview.text = "$v1"
}

Have you tried installing the sample App?


[Eligibility Questionnaire][Accessibility] Consider how to best label the age input

The age input uses conversational style. Consider whether it should have a screen reader only label of "age", or if we should use "years old" as the label.
I tried to do some preliminary research on accessible labels for conversational style inputs but didn't find anything definitive.

[ ] Add a hidden age label for the screenreader

send PR to @elenm

Actually, given that we're going to replace this question entirely in #526, I don't think we need this issue.


allow a configurable minimum liquidity for the order to be started

alternately just check that it's non-zero

i think this is probably not necessary with #5 fixed, since you can configure individual tokens only


feature/implement API call for pie chart

Description
This implements a preliminary API call for data to the pie chart of "origin of energy"

@cla-bot check


Add more ideas from previous CWs

CW Collaborative and hack ideas

[x] CW22 Hack day ideas
[x] CW22 Collaborative ideas
[x] CW21 Hack day ideas
[x] CW21 Collaborative ideas
[x] CW20 Hack day ideas
[x] CW20 Collaborative day ideas
[x] CW19 Hack day ideas
[x] CW19 Collaborative day ideas
[x] CW18 Hack ideas
[x] CW18 Collaborative ideas

In some cases a (*) is used to indicate that a title was not provided so one was created.
CW22 Hack ideas

[x] Developing scenarios to help nurture Inclusive Research Leaders
[x] Code Review Cupid
[x] RESPIRATOR (Research Software Performance Indicators Really Acknowledging The Objective Reality)
[x] Carpentries-style Lesson on R’s Bug Tracking Process
[x] iFortran Linter
[x] CFF in the wild - analysing software citation metadata file usage

CW22 Collaborative ideas

[x] Easy Open Source Bio-Graphs
[x] Interdisciplinary Glossary of Glossaries
[x] Squashing conceptual bugs when computational bugs have been exterminated
[x] Interdisciplinary Researchers ‘R’ Us
[x] Weather Log
[x] Key Performance Indicators for Research Software Engineering Output
[x] Path to Open Platforms - new chapter for the Turing Way
[x] The Code Review Cupid - a matchmaking service for connecting coders
[x] Hi-Brid!
[x] Choose your own research-software adventure

CW21 hack day ideas

[x] HowDescribedIs
[x] Escape room: Translating between RSEs and Arts & Humanities Researchers
[x] Tools to recognise underlying software infrastructure visible and funded
[x] Credit All
[x] Running a dugnad in a research group
[x] Exploratory analysis of past Collaborative Ideas
[x] Hello world (of CI/CD)
[x] Coding Confessions
[x] Using Raspberry Pis to deliver Carpentries training in remote locations
[x] Enabling analysis of research software: Creating an enhanced research software corpus

CW21 collaborative ideas

[x] Macavity
[x] DEPTH: Developer error/problem treasure hunt!
[x] User centred design principles for research apps / citizen science
[x] Koko
[x] Software citation videos (to understand why and how to make your software citable)
[x] Improving data visualization literacy
[x] End of Life Plans for Software
[x] Leo
[x] How to encourage and ensure software maintenance gets sufficiently funded
[x] Bursting the Bubble: Teaching PIs the value of good code
[x] Open Source Covid Analysis of References (OSCAR)

CW20 Hack ideas

[x] How Wrong Is The Research Code Base?
[x] How do we facilitate effective collaboration in a virtual event (*)
[x] Let’s make some better manuscript templates for the Journal of Open Research Software
[x] Ticket to Data Wall Garden
[x] Equitable Collaboration guide for distributed/online teams and communities in The Turing
[x] Storyboarding Sustainability

CW20 collaborative ideas

[x] Adding Behaviour Driven Development to Exploratory Research Notebooks
[x] Conferencing 3.0: ensuring equality for in-person and online participants
[x]  Online Community Cookie Cutter c3
[x] Does grade inflation exist?
[x] Dealing with Legacy Code
[x] Message in e-Bottle: work more effectively with ephemeral teams across timezones
[x] RSE2_D2
[x] State of the Art
[x] Storyboarding Sustainability
[x] The Turing Way

CW19 Collaborative (and hack?) ideas

[x] A "Cite this" button for GitHub   Hackday Pitch   Stephan Druskat
[x] Terminal History Sharing  Hackday Pitch   Jason Gates
[x] Automating Screenshots for Documentation  Hackday Pitch   Colin Sauze
[x] GitHub annotator/failure map      Hackday Pitch   Ilektra Christidi
[x] Software reporting guidelines     Hackday Pitch   Alexander Konovalov
[x] Creating a Lessons Roadmap and Proficiency Framework for Software and Data Training       Hackday Pitch   Neil Chue Hong
[x] Slack overflow: getting permanent docs from instant messaging     Hackday Pitch   ben krikler
[x] R2D?.. (Ready to Deposit?)        Hackday Pitch   Patrick McCann
[x] Improving The Turing Way  Hackday Pitch   Kirstie Whitaker
[x] Netflix of libraries      Hackday Pitch   ben Krikler
[x] Code-literate peer-review for everyone    Hackday Pitch   Alessandro Felder
[x] Maintainable Tutorials Made Quickly       Hackday Pitch   Adam Jackson
[x] Is your online training material accessible?      Hackday Pitch   David Perez-Suarez
[x] Checklists for open reproducible research Hackday Pitch   Anna Krystalli
[x] Hover Eels        Hackday Pitch   Niall Beard
[x] Col-Laboratory    Hackday Pitch   Niall Beard
[x] DUQI (Documentation Utility & Quality Interrogator)       Hackday Pitch   Rebecca J Arnold
[x] CarpenTREE
[x] Reproducibility and Collaboration Challenges in interactive / exploratory research (*)
[x] RSE Careers (*)
[x] Infrastructure to support following up after a workshop/training session (*)
[x] Best Practice Checklist (*)
[x] Identify new roles within Academia (*)
[x] The Research Data Sandbox
[x] What is my contribution? (*)
[x] DUQI (Document Utility and Quality Interrogator) - proposal
[x] How to map out software and data skills lessons like Duolingo - proposal
[x] How do you motivate researchers to adopt better software practices?
[x] Interoperability & Continuous Integration
[x] Libflix (*)
[x] The Doctor button

The above has not been properly designated - some are hack ideas while others are collaborative ideas.
CW18 Hack-ideas:

[x] Aligning the Citation File Format and CodeMeta
[x] Automated Network Map construction
[x] Carpentries platform to support translations
[x] Choose-a-Visualisation
[x] Code is Science Manifesto
[x] Geospatial metadata sharing
[x] Keeping up with the Joneses: Providing evidence for software and data citations in published papers
[x] Productivity Approximator

CW18 collaborative ideas

[x] Guidelines for research library users and providers
[x] ASAP - Automated Software-Assisted Provisioning
[x] SCAT (STEM Career Advising Tool)
[x] Sustainability Deniers
[x] Teaching programming to researchers across all research domains
[x] Keeping up with the Joneses: Providing evidence for software and data citations in published papers
[x]  Code review across projects for software sustainability
[x] AutoSoftCat
[x] Crediting Super Awesome Documentation to get Research Software Certification
[x] Translating between programming languages (*)
[x] How to manage expectations while juggling different projects with overlapping deadlines and competing resources?
[x] Downloading and filtering datasets (*)
[x] Streamlining JupyterLab as a teaching tool

I think all the ones that I found have been added.


Update access-tiers-overview.md

Imp note

@normesta
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@normesta - Should we close this PR?
Thanks, PR review team

I think so.
#please-close


Refactor build script

Ok, admittedly this is a beastly build script, but it's working pretty well now. I'm sure you can see why people choose Webpack/React et al to normalize some of the work, although it has its own set of complications. :smile:
Here's some of the changes:

Use regular budo API instead of cli() and simplify npm run scripts
Don't pass { live: true } instead we will just manually set it all up to our needs
Use the dir flag to serve up the release directory
Use browserify (the main reason budo would be useful) so we can take advantage of things like require('url') in the public/js/main.js
Use the same build script for the "production" release (clean, copy files, generate templates, browserify + uglify)
Only watch a subset of files in our input/output directories for performance
Use fs-extra instead of shell calls and make sure things happen properly in sync

Using the nunjucks API instead of shell commands might improve the rendering time, though I've never used nunjucks before. Maybe check out nunjucksify for reference there.

wow, fancy me impressed. didn't expect you to rewrite my whole hacked-together build system! you fixed the JS bundle not reloading, consolidated the dev/prod pipeline, and even added minification - not to mention rewriting everything to work, and quite reliably in my initial tests right now! 🎉
and the Live Reloading speeds didn't degrade at all. I'm a happy camper ⛺!  really do owe you owe - thank you so much.


Docker: Don't installl Cypress

Noticed this in the Docker Hub build log:
https://cloud.docker.com/u/shieldsio/repository/registry-1.docker.io/shieldsio/shields/builds/de14f15e-0f10-4842-9ad2-42b8558bc2ff
Ref #3558

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 678d451ba9e87780c41208b05843c9ef30c67ef1

^^ I got Heroku re-authenticated using a service account, so it no longer shows my name in all these messages.


table prefix duplication

When generating migrations from existing database with table prefix example: **prefix_**tablename - it stores the schema along with the table prefixes. Afterwords when you run php artisan migrate - it uses the prefix from configuration and adds additional prefixes example: **prefix_**prefix_tablename
I have a workaround with renaming the migrations and removing the prefixes from the table names so when I run the migrate command it adds the prefix configured in database config file.
You should consider eliminating the prefix based on the one configured in database config file and generating migration without prefixes if set

I remember this being added. There might be a bug with it... Will check it out

#22 appears to be an attempt to fix it. I believe it still has a few problems. Please check it out and let me know :) Thanks

This seems to be a duplicate of #22, closing this one as duplicate


Handle libvirt_domain_interface_meta with SR-IOV interfaces

This pull request changes the way that we report the libvirt_domain_interface_meta metric so that it is only present if the SourceBridge or VirtualInterface are present. In systems which use SR-IOV, there is no concept of a bridge or virtual interface, as the interface is completely passed through to the hypervisor.
This resolves a problem where the exporter would fail on a domain which has an SR-IOV enabled interface with with the following error:
An error has occurred while serving metrics:

collected metric "libvirt_domain_interface_meta" { label:<name:"domain" value:"host" > label:<name:"source_bridge" value:"" > label:<name:"target_device" value:"" > label:<name:"virtual_interface" value:"" > gauge:<value:1 > } was collected before with the same name and label values

Thanks, @bswinnerton !


Remove final restriction from Doctrine\ORM\Query to allow mocking

The Doctrine\ORM\Query class is marked as final but does not have a full interface, so mocking it is basically next to impossible.
I propose dropping the final restriction, leaving it commented as it was done in the EntityManager. Documentation could also recommend not to extend it.

There's no need to extend the Query object. The semantics are absolutely terrifying and specific to the ORM: just don't do it.

@Ocramius I'm not extending, I'm trying to mock it.

@guiwoda a query object is code, and cannot really be mocked. It's like mocking eval(): doesn't really work.
Keep Query and QueryBuilder as part of your private API only. Also, there's no way to really unit test it: needs integration tests, as asserting on a DQL string or structure is not sufficient to assert its correctness.

@Ocramius Query is final, but there is no interface that covers it. Other parts of Doctrine (right now Paginator is the one that bugs me) depend on a final, non-mockable class.
How do you propose I test a code that instantiates a Paginator without the ability to mock a Query?

How do you propose I test a code that instantiates a Paginator without the ability to mock a Query?

Code that instantiates a paginator is statically coupled to both the paginator (which doesn't have an interface, besides being an Iterator) and the query/query builder: it's in fact query logic that is not mockable. Consumers of the paginator should expect a Countable or an Iterator or IteratorAggregate instead.

@Ocramius the code instantiates the Paginator but passes through a Query from parameters. That's why I would have mocked the Query and let the Paginator be built with it.
This is Laravel Doctrine bridge code. You can check the linked PR if you want to.


Magpie causes server to crash on startup (linux)

crash log
Hi again!
If I had a nickel for every time Magpie worked on my client but crashed the server on startup, I'd have two nickels, which isn't a lot, but it's weird that it happened twice. This time it's a little bit different, though. I was running the server on Windows with clients on Windows (same configuration as when Magpie previously crashed the server). I moved everything over for the server to run on Linux instead, but for some reason once it got there, Magpie causes the server to crash on startup. My client (on Linux) still works perfectly fine though, just like before.
I'm assuming that whatever the cause is, it happened because I'm on Linux now, but unfortunately I can't not be on Linux because of other, irrelevant reasons :(

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file password: changeme In the installer menu, select "gcc."

I want to make it clear that I really, really appreciate your super quick response to my issue. But please understand that I can't just blindly download a file and run it. What is this and what does it do?

Hey! So I actually Googled the error and it turns out it's because I installed the "headless" version of the JRE instead of the full JDK. There were things in the JDK that Magpie needs to run, I guess.
Thank you for all your hard work! Farewell for now, I hope we never have to meet again HAHAHA (unless you release a new fantastic mod like Magpie :))

Download https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file password: changeme In the installer menu, select "gcc."

I want to make it clear that I really, really appreciate your super quick response to my issue. But please understand that I can't just blindly download a file and run it. What is this and what does it do?

Hi, I am glad that you found the solution to the problem.
I was just wondering, who sent you this link? Was it from my account? Because I can't find this comment anymore.

Hey! No, it was from an account named "bkballoon." After they sent the link, I did download the link (in a VM) but I never opened the zip file and I forgot about it so it's long gone now.
I looked at their profile soon after they sent the link, and it looked like a regular, real GitHub account. I just searched it now and it has seemingly vanished. My theory is that their account got hacked and was used to spread malware? And then the account was terminated by the hacker after they were done or the original user to try to stop the hacker. It's a shame they lost their account.
They responded SUPER quickly, too, so it was very suspicious all around.

I apologize for the bad quality photo, I should have taken a screenshot, but here is the exact message and user. If you Google this username, you can clearly see that it once existed, but every link leads to the GitHub 404 page.


Could not find current folder in /var/lib/ceph/osd/ceph-1

Bug Report
What happened:
I could not find the current folder in ceph directory
What you expected to happen:
I wish to find it and try to test the stability of ceph
How to reproduce it (minimal and precise):

I use rados put one file and I can get the file. But I could not find the "current" folder.
I don't know if it's the version difference or I install ceph failed
Share your group_vars files, inventory and full ceph-ansibe log
This is the content in all.yml in group_vars folder
ceph_origin: repository
ceph_repository: community
ceph_stable_release: luminous
ceph_mirror: http://mirrors.aliyun.com/ceph
ceph_stable_key: http://mirrors.aliyun.com/ceph/keys/release.asc
ceph_stable_repo: "{{ ceph_mirror }}/rpm-{{ ceph_stable_release }}"
public_network: "<IP_ADDRESS>/24"
cluster_network: "<IP_ADDRESS>/24"
monitor_interface: eth0
devices:
  - '/dev/vdb'
osd_scenario: collocated
cephfs: cephfs
cephfs_data: cephfs_data
cephfs_metadata: cephfs_metadata

cephfs_pools:
  - { name: "{{ cephfs_data }}", pgs: "{{ osd_pool_default_pg_num }}", size: "{{ osd_pool_default_size }}" }
  - { name: "{{ cephfs_metadata }}", pgs: "{{ osd_pool_default_pg_num }}", size: "{{ osd_pool_default_size }}" }

And this is the hosts information
[mons]
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
[mgrs]
<IP_ADDRESS>
[mdss]
<IP_ADDRESS>
[osds]
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

I am sorry that I couldn't find full deploy log.
And this is the content in /etc/ceph/ceph.conf
# Please do not change this file directly since it is managed by Ansible and will be overwritten

[global]
fsid = a2f28533-7713-4d59-a18f-05b4855e4675

mon initial members = host1,host2,host3
osd pool default crush rule = -1

mon host = <IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>

public network = <IP_ADDRESS>/24
cluster network = <IP_ADDRESS>/24

[osd]
osd memory target =<PHONE_NUMBER>

Environment:

OS (e.g. from /etc/os-release):
CentOS Linux release 7.6.1810 (Core)
Kernel (e.g. uname -a):
Linux hosts 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Docker version if applicable (e.g. docker version):
Ansible version (e.g. ansible-playbook --version):
ansible-playbook 2.7.4
ceph-ansible version (e.g. git head or tag or stable branch):
stable-3.2
Ceph version (e.g. ceph -v):
ceph version 12.2.13 (584a20eb0237c657dc0567da126be145106aa47e) luminous (stable)

Share your group_vars files, inventory and full ceph-ansibe log

Please share the required information

I update the information and I wonder how could i find the path that I store files. @dsavineau
Most articles says that the file is in /var/lib/ceph/osd/ceph-X/current, but I couldn't find this folder.
Thank you.

Most articles says that the file is in /var/lib/ceph/osd/ceph-X/current, but I couldn't find this folder.

If you put a file in a pool via the rados command then you won't see the file on disk in /var/lib/ceph/osd/ceph-X/
Looking at your configuration, you should have a cluster with 3 OSDs (0, 1, 2). The /var/lib/ceph/osd/ceph-{0,1,2} directories (0 could be on .101, 1 on .102, and 2 on .103, it's totally random) only contain the bluestore metadata.
The data are stored on a raw devices so you can't see the files (ie: there's no filesystem on the data device)
Your /dev/vdb device should have 2 partitions

/dev/vdb1 which is the bluestore metadata partition (the one mounted in /var/lib/ceph/osd/ceph-{0,1,2})
/dev/vdb2 which is the bluestore data partition (you should be able to see the symlink to this partition in /var/lib/ceph/osd/ceph-{0,1,2}/block)


Use new package structure

This commit will modify the python script that allows us to quickly generate packages for ayon-backend ingestion, either by copying them to the rez repo (not advised) or installing them via the ayon-frontend by uploading the resulting zips of the script.
Changelog Description
This is a PR that will allow us to then test the functionality of this ayon-backend PR: https://github.com/ynput/ayon-backend/pull/29
Instead of creating a folder structure at this step, we delegate it to the rezbuild.py on the ayon-backend which expects the package.py and the usual folder structure  of the addon source code (https://github.com/ynput/ayon-addon-template), thus this step is greatly simplified where we only copy the contents of the addon, add a package.py and zip them up.

4113ff7bf0 Add rez packages generation for server_addons Allow to generate rez compatible packages for the server_addons, will create a package.py which then is also included in the .zip.

0744c27c91 package.py Ensure we require the correct ayon_server version For more info on rez package requests syntax check: https://rez.readthedocs.io/en/latest/basic_concepts.html#package-requests-concept

Testing notes:

Clone this branch
Run python server_addon/create_ayon_addons.py -r
Confirm zip archives have been generated in ayon-core/server_addon/packages ending in -rez.zip and should have the package.py at the root of the zip alongside the manifest.json.
If you are running the backend with the rez implementation: Install the addon, enable it and make sure it is able to initialize.

Modified the code. Now it always create new structure, and removed manifest.json. Also fixed issue in applications addon caused by new structure.


The composer.json files are hardcoding grpc version in them.

We should generate these from a template and build.yaml instead.


Security headers recommended by Mozilla Observatory

Issue #, if available:
Description of changes:
I suggest adding the following headers to make the headers set more robust:

frame-ancestors (to CSP)
referrer-policy

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

It's worth noting that CloudFront Functions are not invoked if the HTTP code is an error (> 400). Thus using CloudFront Functions can introduce a wrong sense of security as they are not returned for error pages. Any XSS vulnerabilities on the error page can then be exploited due to the missing headers. See https://github.com/aws-samples/amazon-cloudfront-functions/issues/8.


Lint rules

Description
Thanks for such a great friend. We are together for many years, and we have developed some habits how we live together, and what we can expect from each other.
Those habits sometimes lead to a bad situation when a friend lets a friend down 😢
Steps to reproduce

how it started

{
  "*.js": "this works",
  "*.scss": "this works",
}

how it ended

{
  "*.{js,jsx,ts,tsx}": "this works",
  // let's be consistent in the pattern!
  "*.{scss}": "this dont",
}

The issue is not bound to the lint-staged and more about implementation detail of minimatch, but we spend ~month trying to understand why our styles are not linted on commit.
We have 6 lint-staged rules, 5 never worked.
Proposed solution
Report a wrong match in the configuration.

🤔 I understand your frustration but I’m not sure how to solve this. Is here a way to tell that a glob is invalid from minimatch perspective? Feel free to propose a solution!

Look like I found something "acceptable" for me:

https://github.com/micromatch/micromatch#options has strictBrackets option, which gives the first level of confidence
{scss} can be verified via

if(pattern.includes('{')) {
  if(braces(pattern, {expand: true}.length===1) {
    throw new Error(pattern + "should be writen as "+pattern.replace(/[\{\}]/g,''))
  }

For what it's worth, I asked about this earler here: https://github.com/micromatch/braces/issues/32

I think we’re fine with a breaking change but I don’t see it as such since it’s leading to a working configuration. Maybe instead of throwing we could print a warning? In this case it’s not a breaking change. But as I said I’m fine with a breaking one too if it leads to better DX.

@iiroj - thanks for validating my concern. I'll prepare nessesary changes during weekends.

I opened this PR to try fixing this issue by detecting and removing these unnecessary/incorrect braces, and also warning the user:
https://github.com/okonet/lint-staged/pull/992


Update Set-Mailbox.md

Branding updates

Docs Build status updates of commit 7418a76:
:clock10: Full build: the average full build time is 12 min(s) 7 sec(s), this is based on the last 631 build(s) for this repository.

Docs Build status updates of commit 7418a76:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/mailboxes/Set-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit ed1acb8:
:clock10: Full build: the average full build time is 12 min(s) 5 sec(s), this is based on the last 650 build(s) for this repository.

Docs Build status updates of commit ed1acb8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/mailboxes/Set-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


🐛 [cloud_firestore] CollectionReferenceWeb uses implements instead of extends, makes CollectionReferencePlatform fragile

Bug report
Describe the bug
QueryPlatform.verifyExtends does not call PlatformInterface.verifyToken if the instance being verified is an instance of CollectionReferencePlatform. Instead it could call either QueryPlatform.verifyExtends or CollectionReferencePlatform.verifyExtends depending on the type of the instance.
As a result, CollectionReferenceWeb is able to implement CollectionReferencePlatform without extending it.
Steps to reproduce
Steps to reproduce the behavior:

Add a new method to CollectionReferencePlatform and release as a "minor" update.
Compile error in CollectionReferenceWeb: method is not implemented.

Expected behavior
When _JsonQuery calls QueryPlatform.verifyExtends on a CollectionReferencePlatform instance, the implementation of QueryPlatform.verifyExtends should call PlatformInterface.verifyToken even if _delegate is a CollectionReferencePlatform.

/cc @Salakar


Mac CI Block:try change filehash to recache macOS tools

Summary
Rebuild cache
Impact
Testing

I manually delete the cache:

Let's see what's happen in the new ci.

I manually delete the cache:
@xiaoxiang781216 in the latest ci sim/posix_test, Makefile has some execution errors on Mac platform. i fix in https://github.com/apache/nuttx-apps/pull/2051
let's also track this

Don't need.


Warning message when using custom loss function

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): YES
OS Platform and Distribution: UBUNTU 18.04
TensorFlow installed from: CONDA
TensorFlow version: 2.4.1
Python version: 3.8
CUDA/cuDNN version: 11.2
GPU model and memory: 4 x TITAN Xp 12GB

Greetings from Italy!
I coded a simple autoencoder (I used one of the stock example script you can find on TF) just to see if I was able to implement a custom loss function. This is the code (jupyter notebook file):
https://github.com/notprime/autoencoder/blob/main/autoencoder.ipynb
Basically, that function in [3] is something I didn't code, and its vectorialization is pretty hard. Therefore, when I get the hidden output tensor, I convert it into a numpy array, compute the matrix I need, convert it back into a TF tensor, and I compute the custom loss function.
When I train the model, I get the following error:
WARNING:tensorflow:AutoGraph could not transform <function compute_loss at 0x7f0e688fbe50> and will run it as-is.
Please report this to the TensorFlow team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output.
Cause: module 'gast' has no attribute 'Index'

Is this something I should worry about?
Moreover, how does TF handle the automatic-differentiation of this compute_loss function (which calls in every for loop the other ** function**? This is something I'd really like to better understand.
If you also have some advices on how optimize the code let me know, this is really my first time using TF. Maybe I can convert those function into TF function using the methods tf.autograph or tf.autograph.to_graph?
Thanks in advance!

@notprime  Could you please confirm what version of gast are you using? Please try with gast 0.3.3 for TF version 2.4. Thanks!


chore(deps) dependencies update by dependabot

Pull Request Test Coverage Report for Build 289946728

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 81.667%

Totals

Change from base Build 276554024:
0.0%

Covered Lines:
153

Relevant Lines:
177

💛  - Coveralls