security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.There are no local code signing identities found.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
we are trying to setup CI/CD on circle ci and facing this issue currently
[05:51:49]: 🔓  Successfully decrypted certificates repo
[05:51:49]: Installing certificate...
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
[05:51:49]: There are no local code signing identities found.
You can run `security find-identity -v -p codesigning fastlane_tmp_keychain` to get this output.
This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774.
(Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)
[05:51:50]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
[05:51:50]: security: SecItemCopyMatching: The specified item could not be found in the keychain.
[05:51:50]: Setting key partition list... (this can take a minute if there are a lot of keys installed)

Complete output when running fastlane, including the stack trace and command used

fastlane logs
#!/bin/bash --login -o pipefail
bundle exec fastlane ios beta --env staging
^D^D[⠋] 🚀 [⠙] 🚀 [⠹] 🚀 [⠸] 🚀 [⠼] 🚀 [⠴] 🚀 [⠦] 🚀 [✔] 🚀
[05:51:45]: Sending anonymous analytics information
[05:51:45]: Learn more at https://docs.fastlane.tools/#metrics
[05:51:45]: No personal or sensitive data is sent.
[05:51:45]: You can disable this by adding `opt_out_usage` at the top of your Fastfile
[05:51:45]: ----------------------------------------
[05:51:45]: --- Step: Verifying fastlane version ---
[05:51:45]: ----------------------------------------
[05:51:45]: Your fastlane version 2.117.1 matches the minimum requirement of 2.61.0  ✅
[05:51:45]: ------------------------------
[05:51:45]: --- Step: default_platform ---
[05:51:45]: ------------------------------
[05:51:45]: Loading from './fastlane/.env.staging'
[05:51:45]: Driving the lane 'ios beta' 🚀
[05:51:45]: -----------------------------
[05:51:45]: --- Step: setup_circle_ci ---
[05:51:45]: -----------------------------
[05:51:45]: Creating temporary keychain: "fastlane_tmp_keychain".
[05:51:45]: Enabling match readonly mode.
[05:51:45]: -------------------
[05:51:45]: --- Step: match ---
[05:51:45]: -------------------
[05:51:45]: Successfully loaded '/Users/distiller/project-react-native/ios/fastlane/Matchfile' 📄
+---------+---------------------------------------------------+
|         Detected Values from './fastlane/Matchfile'         |
+---------+---------------------------------------------------+
| git_url | https://github.com/project/Project_certificates |
| type    | development                                       |
+---------+---------------------------------------------------+
+-----------------------+---------------------------------------------------+
|                         Summary for match 2.117.1                         |
+-----------------------+---------------------------------------------------+
| type                  | appstore                                          |
| git_url               | git@github.com:company/Project_certificates.git |
| readonly              | true                                              |
| app_identifier        | ["com.project.project"]                         |
| username              |<EMAIL_ADDRESS>                          |
| team_id               | HL7CH76RCR                                        |
| storage_mode          | git                                               |
| git_branch            | master                                            |
| shallow_clone         | false                                             |
| clone_branch_directly | false                                             |
| keychain_name         | fastlane_tmp_keychain                             |
| force                 | false                                             |
| force_for_new_devices | false                                             |
| skip_confirmation     | false                                             |
| skip_docs             | false                                             |
| platform              | ios                                               |
| verbose               | false                                             |
+-----------------------+---------------------------------------------------+
[05:51:45]: Cloning remote git repo...
[05:51:45]: If cloning the repo takes too long, you can use the `clone_branch_directly` option in match.
[05:51:49]: 🔓  Successfully decrypted certificates repo
[05:51:49]: Installing certificate...
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
[05:51:49]: There are no local code signing identities found.
You can run `security find-identity -v -p codesigning fastlane_tmp_keychain` to get this output.
This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774.
(Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)
[05:51:50]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
[05:51:50]: security: SecItemCopyMatching: The specified item could not be found in the keychain.
[05:51:50]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
+-------------------+----------------------------------------------------+
|                         Installed Certificate                          |
+-------------------+----------------------------------------------------+
| User ID           | .......                                         |
| Common Name       | iPhone Distribution: project Limited (HL7CH84QMQ) |
| Organisation Unit | .......                                         |
| Organisation      | Domain Limited                                   |
| Country           | US                                                 |
| Start Datetime    | 2019-03-10 11:47:14 UTC                            |
| End Datetime      | 2020-03-09 11:47:14 UTC                            |
+-------------------+----------------------------------------------------+
[05:51:50]: Installing provisioning profile...
+---------------------+--------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
|                                                                              Installed Provisioning Profile                                                                               |
+---------------------+--------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
| Parameter           | Environment Variable                             | Value                                                                                |
+---------------------+--------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
| App Identifier      |                                                  | com.domain.domain                                                                                |
| Type                |                                                  | appstore                                                                                |
| Platform            |                                                  | ios                                                                                |
| Profile UUID        | sigh_com.domain.domain_appstore              | 5b3fba8d-5e2f-40c2-a5db-bec1cd887e3a                                                                             |
| Profile Name        | sigh_com.domain.domain_appstore_profile-name | match AppStore com.domain.domain                                                                             |
| Profile Path        | sigh_com.domain.domain_appstore_profile-path | /Users/distiller/Library/MobileDevice/Provisioning Profiles/5b3fba8d-5e2f-40c2-a5db-bec1cd887e3a.mobileprovision |
| Development Team ID | sigh_com.domain.domain_appstore_team-id      | HL7CH84QMQ                                                                                |
+---------------------+--------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
[05:51:50]: All required keys, certificates and provisioning profiles are installed 🙌
[05:51:50]: Setting Provisioning Profile type to 'app-store'
[05:51:50]: -----------------
[05:51:50]: --- Step: gym ---
[05:51:50]: -----------------
[05:51:50]: $ xcodebuild -showBuildSettings -workspace ./projectreactnative.xcworkspace -scheme projectreactnative
[05:51:53]: Detected provisioning profile mapping: {:"com.domain.domain"=>"match AppStore com.domian.domain", :"com.domain.projectprod"=>"match AppStore com.domain.projectprod"}
+---------------------------------------------------------------+--------------------------------------------------------------+
|                                                   Summary for gym 2.117.1                                                    |
+---------------------------------------------------------------+--------------------------------------------------------------+
| scheme                                                        | projectreactnative                                          |
| xcargs                                                        | -UseNewBuildSystem=NO                                        |
| clean                                                         | true                                                         |
| export_method                                                 | app-store                                                    |
| export_options.provisioningProfiles.com.project.project     | match AppStore com.project.project                         |
| export_options.provisioningProfiles.com.project.projectprod | match AppStore com.project.projectprod                     |
| workspace                                                     | ./projectreactnative.xcworkspace                            |
| destination                                                   | generic/platform=iOS                                         |
| output_name                                                   | projectreactnative                                          |
| build_path                                                    | /Users/distiller/Library/Developer/Xcode/Archives/2019-03-10 |
| output_directory                                              | output/gym                                                   |
| silent                                                        | false                                                        |
| skip_package_ipa                                              | false                                                        |
| result_bundle                                                 | false                                                        |
| buildlog_path                                                 | output/buildlogs/gym                                         |
| skip_profile_detection                                        | false                                                        |
| xcode_path                                                    | /Applications/Xcode-10.1.app                                 |
+---------------------------------------------------------------+--------------------------------------------------------------+
[05:51:53]: $ set -o pipefail && xcodebuild -workspace ./projectreactnative.xcworkspace -scheme projectreactnative -destination 'generic/platform=iOS' -archivePath /Users/distiller/Library/Developer/Xcode/Archives/2019-03-10/projectreactnative\ 2019-03-10\ 05.51.53.xcarchive -UseNewBuildSystem=NO clean archive | tee /Users/distiller/project-react-native/ios/output/buildlogs/gym/projectreactnative-projectreactnative.log | xcpretty
[05:51:55]: ▸ Cleaning React/yoga [Debug]
......................................
The following build commands failed:
Check dependencies
(1 failure)
[05:56:01]: Exit status: 65
[05:56:01]:
[05:56:01]: Maybe the error shown is caused by using the wrong version of Xcode
[05:56:01]: Found multiple versions of Xcode in '/Applications/'
[05:56:01]: Make sure you selected the right version for your project
[05:56:01]: This build process was executed using '/Applications/Xcode-10.1.app'
[05:56:01]: If you want to update your Xcode path, either
[05:56:01]:
[05:56:01]: - Specify the Xcode version in your Fastfile
[05:56:01]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[05:56:01]:
[05:56:01]: - Specify an absolute path to your Xcode installation in your Fastfile
[05:56:01]: ▸ xcode_select "/Applications/Xcode8.app"
[05:56:01]:
[05:56:01]: - Manually update the path using
[05:56:01]: ▸ sudo xcode-select -s /Applications/Xcode.app
[05:56:01]:
+---------------+------------------------------+
|              Build environment               |
+---------------+------------------------------+
| xcode_path    | /Applications/Xcode-10.1.app |
| gym_version   | 2.117.1                      |
| export_method | app-store                    |
| sdk           | iPhoneOS12.1.sdk             |
+---------------+------------------------------+
[05:56:01]: ▸ === BUILD TARGET projectreactnative OF PROJECT projectreactnative WITH CONFIGURATION Release ===
[05:56:01]: ▸ Check dependencies
[05:56:01]: ▸ Code Signing Error: No profile for team 'HL7CH84QMQ' matching 'match Development com.project.project' found:  Xcode couldn't find any provisioning profiles matching 'HL7CH84QMQ/match Development com.project.project'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the General tab of the target editor.
[05:56:01]: ▸ Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.1'
[05:56:01]:
[05:56:01]: ⬆  Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
[05:56:01]: 📋  For the complete and more detailed error log, check the full log at:
[05:56:01]: 📋  /Users/distiller/project-react-native/ios/output/buildlogs/gym/projectreactnative-projectreactnative.log
[05:56:01]:
[05:56:01]: Looks like fastlane ran into a build/archive error with your project
[05:56:01]: It's hard to tell what's causing the error, so we wrote some guides on how
[05:56:01]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[05:56:01]: Before submitting an issue on GitHub, please follow the guide above and make
[05:56:01]: sure your project is set up correctly.
[05:56:01]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
[05:56:01]: the full commands printed out in yellow in the above log.
[05:56:01]: Make sure to inspect the output above, as usually you'll find more error information there
[05:56:01]:
+------------------------------------+-------------------------------------------------------------------+
|                                              Lane Context                                              |
+------------------------------------+-------------------------------------------------------------------+
| DEFAULT_PLATFORM                   | ios                                                               |
| ENVIRONMENT                        | staging                                                           |
| PLATFORM_NAME                      | ios                                                               |
| LANE_NAME                          | ios beta                                                          |
| ORIGINAL_DEFAULT_KEYCHAIN          | "/Users/distiller/Library/Keychains/login.keychain-db"            |
| SIGH_PROFILE_TYPE                  | app-store                                                         |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"com.project.project"=>"match AppStore com.project.project"} |
+------------------------------------+-------------------------------------------------------------------+
[05:56:01]: Error building the application - see the log above
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | default_platform           | 0           |
| 3    | setup_circle_ci            | 0           |
| 4    | match                      | 4           |
| 💥   | gym                        | 251         |
+------+----------------------------+-------------+
[05:56:01]: fastlane finished with errors
[!] Error building the application - see the log above
Exited with code 1

.circleci/config.yml
version: 2
jobs:
  node:
    working_directory: ~/project-react-native
    docker:
      - image: circleci/node:8
    steps:
      - checkout

      - restore_cache:
          key: yarn-v1-{{ checksum "yarn.lock" }}-{{ arch }}

      - restore_cache:
          key: node-v1-{{ checksum "package.json" }}-{{ arch }}

      - run: yarn install

      - save_cache:
          key: yarn-v1-{{ checksum "yarn.lock" }}-{{ arch }}
          paths:
            - ~/.cache/yarn

      - save_cache:
          key: node-v1-{{ checksum "package.json" }}-{{ arch }}
          paths:
            - node_modules

      - persist_to_workspace:
          root: ~/project-react-native
          paths:
            - node_modules

  # android:
    # working_directory: ~/demo-react-native/android
    # docker:
      # - image: circleci/android:api-27-node8-alpha
    # steps:
      # - checkout:
          # path: ~/demo-react-native

      # - attach_workspace:
          # at: ~/demo-react-native

      # - restore_cache:
          # key: bundle-v1-{{ checksum "Gemfile.lock" }}-{{ arch }}

      # - run: bundle install

      # - save_cache:
          # key: bundle-v1-{{ checksum "Gemfile.lock" }}-{{ arch }}
          # paths:
            # - vendor/bundle

      # - run:
          # name: fastlane tests
          # command: |
            # mkdir -p test-results/fastlane
            # bundle exec fastlane test
            # mv fastlane/report.xml test-results/fastlane
      # - store_test_results:
          # path: test-results

      # - store_artifacts:
          # path: test-results

  ios:
    macos:
      xcode: 10.1.0
    working_directory: ~/project-react-native

    environment:
      FASTLANE_PASSWORD: <password>
      DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS: "-t DAV"
      MATCH_PASSWORD: <password>
      FL_OUTPUT_DIR: output

    # use a --login shell so our "set Ruby version" command gets picked up for later steps
    shell: /bin/bash --login -o pipefail

    steps:
      - checkout

      - run:
          name: set Ruby version
          command:  echo "ruby-2.4" > ~/.ruby-version

      - restore_cache:
          key: yarn-v1-{{ checksum "yarn.lock" }}-{{ arch }}

      - restore_cache:
          key: node-v1-{{ checksum "package.json" }}-{{ arch }}

      # not using a workspace here as Node and Yarn versions
      # differ between our macOS executor image and the Docker containers above
      - run: yarn install

      - save_cache:
          key: yarn-v1-{{ checksum "yarn.lock" }}-{{ arch }}
          paths:
            - ~/.cache/yarn

      - save_cache:
          key: node-v1-{{ checksum "package.json" }}-{{ arch }}
          paths:
            - node_modules

      - restore_cache:
          key: bundle-v1-{{ checksum "ios/Gemfile.lock" }}-{{ arch }}

      - run:
          command: bundle install
          working_directory: ios

      - save_cache:
          key: bundle-v1-{{ checksum "ios/Gemfile.lock" }}-{{ arch }}
          paths:
            - vendor/bundle

      - run
          command: bundle exec fastlane env
          working_directory: ios
      - run:
          command: bundle exec fastlane ios beta --env staging
          working_directory: ios

      - store_artifacts:
          path: output/Game.ipa

workflows:
  version: 2
  node-android-ios:
    jobs:
      - node
      # - android:
          # requires:
            # - node
          # filters:
            # branches:
              # only: master
      - ios:
          requires:
            - node
          filters:
            branches:
              only: ci-ios

Environment

🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.13.6

Ruby
2.4.5

Bundler?
true

Git
git version 2.19.1

Installation Source
~/.gem/ruby/2.4.5/bin/fastlane

Host
Mac OS X 10.13.6 (17G3025)

Ruby Lib Dir
~/.rubies/ruby-2.4.5/lib

OpenSSL Version
OpenSSL 1.0.2p  14 Aug 2018

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode-10.1.app/Contents/Developer/

Xcode Version
10.1

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://docs.fastlane.tools/actions/
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.61.0"

default_platform :ios

platform :ios do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
    # cocoapods
    # carthage
    # setup_circle_ci
  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    setup_circle_ci
    match(
      readonly: is_ci,
      type: "appstore",
      git_url: "git@github.com:project/project_certificates.git"
    ) # more information: https://codesigning.guide
    gym(scheme: "projectreactnative", xcargs: "-UseNewBuildSystem=NO", clean: true) # Build your app - more options available
    pilot(skip_waiting_for_build_processing: true)
    slack(
      message: "Dev App successfully released!",
      slack_url: "..."
    )

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

  desc "Deploy a new version to the App Store"
  lane :release do
    # match(type: "appstore")
    # snapshot
    match(
      type: "appstore",
      git_url: "git@github.com:project/project_certificates.git"
    )
    gym(scheme: "projectreactnativeprod") # Build your app - more options available
    deliver(
      force: true,
    )
    slack(
      message: "Production App successfully released!",
      slack_url: "..."
    )

    # frameit
  end

  desc "Register new device"
  lane :register_new_device do  |options|
      device_name = prompt(text: "Enter the device name: ")
      device_udid = prompt(text: "Enter the device UDID: ")
      device_hash = {}
      device_hash[device_name] = device_udid
      register_devices(
                       devices: device_hash
                       )
  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used. No personal data is recorded.
# Learn more at https://github.com/fastlane/fastlane#metrics

`./fastlane/Appfile`
app_identifier "com.project.project" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "..." # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

for_lane :release do
  app_identifier 'com.project.projectprod'
end

fastlane gems

Gem
Version
Update-Status

fastlane
2.117.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

bundler
1.17.1

io-console
0.4.6

CFPropertyList
3.0.0

public_suffix
2.0.5

addressable
2.6.0

atomos
0.1.3

babosa
1.0.2

claide
1.0.2

colored
1.2

colored2
3.1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.10

declarative-option
0.1.0

digest-crc
0.4.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

dotenv
2.7.1

emoji_regex
1.0.1

excon
0.62.0

multipart-post
2.0.0

faraday
0.15.4

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.13.1

fastimage
2.1.5

gh_inspector
1.1.3

jwt
2.1.0

memoist
0.16.0

multi_json
1.13.1

os
1.0.0

signet
0.11.0

googleauth
0.6.7

httpclient
2.8.3

mime-types-data
3.2018.0812

mime-types
3.2.2

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.23.9

google-cloud-env
1.0.5

google-cloud-core
1.3.0

google-cloud-storage
1.16.0

json
2.2.0

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.5.0

rubyzip
1.2.2

security
0.1.3

naturally
2.2.0

simctl
1.6.5

slack-notifier
2.3.2

terminal-notifier
1.8.0

unicode-display_width
1.5.0

terminal-table
1.8.0

tty-screen
0.6.5

tty-cursor
0.6.1

tty-spinner
0.9.0

word_wrap
1.0.0

nanaimo
0.2.6

xcodeproj
1.8.1

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.0

generated on: 2019-03-10

we are facing the same issue on bitrise

👋 @fadyZohdy
According to the logs it looks like there's an issue with the expired WWDR Certificate:

There are no local code signing identities found.
...
Check in Keychain Access for an expired WWDR certificate

I'd suggest to follow the solution described on stackoverflow threads (links from the logs):

https://stackoverflow.com/q/35390072/774
https://stackoverflow.com/a/35409835/774

Please let us know if that helped 🙏

Also experiencing this in CircleCI, please advise if anyone finds the solution when running on a fresh image install. 😢

Also sometimes experience the same issue on Bitrise - restarting the build helps.

@fadyZohdy The log excerpt you posted is the expected successful output when running match for the first time on a new machine. It's a little confusing but if you run it with the --verbose flag it will make more sense. For example, SecKeychainSearchCopyNext: The specified item could not be found in the keychain. just means you don't have the item yet.
The actual error you're experiencing is much lower, after gym:

[05:56:01]: ▸ Code Signing Error: No profile for team 'HL7CH84QMQ' matching 'match Development com.project.project' found:  Xcode couldn't find any provisioning profiles matching 'HL7CH84QMQ/match Development com.project.project'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the General tab of the target editor.

In your case it looks like you are trying to sign a release build with a development cert.
You might need to select the correct certificate (the distribution cert) in Xcode.
If you don't want to mess with the Xcode project for some reason (for example, if you are using Xcode's automatic provisioning for development builds), you can force a specific release configuration (e.g. iPhone Distribution) and/or provisioning profile at build time after match runs.
For example, one of my lanes looks like this:
  lane :deploy_app_store_connect do
    disable_automatic_code_signing(code_sign_identity: 'iPhone Distribution')
    sync_code_signing
    update_project_provisioning(profile: ENV['sigh_com.companyname.appname_appstore_profile-path'])
    build_app
    upload_to_testflight(changelog: 'Here is the latest test build.',
       distribute_external: true,
       groups: 'QA Testers')
  end

You can get the correct value for ENV['sigh_com.companyname.appname_appstore_profile-path'] from your match logs:
+---------------------+--------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
| Parameter           | Environment Variable                             | Value                                                                                |
+---------------------+--------------------------------------------------+------------------------------------------------------------------------------------------------------------------+
| App Identifier      |                                                  | com.domain.domain                                                                                |
| Type                |                                                  | appstore                                                                                |
| Platform            |                                                  | ios                                                                                |
| Profile UUID        | sigh_com.domain.domain_appstore              | 5b3fba8d-5e2f-40c2-a5db-bec1cd887e3a                                                                             |
| Profile Name        | sigh_com.domain.domain_appstore_profile-name | match AppStore com.domain.domain                                                                             |
| Profile Path        | sigh_com.domain.domain_appstore_profile-path | /Users/distiller/Library/MobileDevice/Provisioning Profiles/5b3fba8d-5e2f-40c2-a5db-bec1cd887e3a.mobileprovision |
| Development Team ID | sigh_com.domain.domain_appstore_team-id      | HL7CH84QMQ                                                                                |
+---------------------+--------------------------------------------------+------------------------------------------------------------------------------------------------------------------+


Where does omero metadata go?

The omero metadata has been labeled "transitional" in the current spec draft, see https://ngff.openmicroscopy.org/latest/#omero-md.
This means the intention is to remove it in the future, once the actual storage destination for such metadata in OME-NGFF has been figured out (see https://ngff.openmicroscopy.org/latest/#document-conventions). I have no idea what the timeline is for this, it doesn't appear imminent. But we should keep an eye on it and ensure the info we need will be available in the new metadata when it comes up (I strongly suspect this is after v0.5)
Also, we are starting to add some custom metadata, e.g. wavelength_id for channel selection, see https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/211
We can use this as a conversation topic with the OME-NGFF folks, but I don't think it makes sense to contribute changes to the transitional "omero" spec. Let's just make sure we bring up these additions when the new metadata destination is figured out

I think our main approach here should be adding experimental key-value pairs in .zattrs to figure out what metadata we want to store in OME-Zarr. Once we have those figured out better, we can contribute it back to the spec.
Some ideas:

a history attribute that gets an ordered list of what has been applied to an OME-Zarr file with what versions/parameters
Additional entries as discussed here: https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/212

Turns out, things move much slower in the spec than I thought in 2022 ;)
Let's open a new issue if there's actually a need to move omero metadata somewhere else


Update subscriptions.md - updated IACM to say 120 Executions per Year

updated IACM to say 120 Executions per Year
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

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

Issue(s)

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

[ ] Tested Locally
[ ] Optional Screenshot.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65fb75fd49536948cb04999c--harness-developer.netlify.app


Zone templates with ALIAS records don't work

PDA version
0.4.1
Python version
3.9
Steps to Reproduce
I have a zone template with an ALIAS record type. Any time I try to use the template for creating a new zone the new zone gets created but only with an SOA record. All other records in the templates are missing.
If I remove the ALIAS record from the zone template, and create a new zone using the revised template, all the records from the template are created as expected.
It would be nice to allow ALIAS records as we typically want to ALIAS the root/apex domain to www.domain.com
Expected Behavior
A new zone should get created with ALIAS records
Observed Behavior
A new zone gets created with ONLY SOA records. All other record types from the zone template are missing.

It also appears this happens if you create an empty record.  So for example, if I create a record like this:

I get these are not valid records however the idea with a template is to have these pre-created so all we have to do is plug in an IP  address and we're done.

Here's a screenshot of the ALIAS record:

www.domain.com is hot hosted on my server so I can see where that would be a problem, that being said I tried using something like www.mydomain.com which is hosted with me and that also fails in the same way.

I think I see the issue. ALIAS records work if you enter the data as www.domain.com. (note the dot at the end). A missing dot results in it working as described above. Adding the dot at the end and it works. Is this intentional (that a dot is required)?


Iterables/Dictionaries

In an example config file below
# config.yml
Github:
  Domain: github.com
  Gateways:
    Public:
      Path: /api/v1.0.0
      Services:
        Document:
          Path: document
          Endpoints:
            List: { Method: "GET", Path: "list/{root}" }
        Objectives:
          Path: tasks
          Endpoints:
            Create: { Method: "POST", Path: "task" }
        Tags:
          Path: tags
          Endpoints:
            Creation: { Method: "POST", Path: "" }
            Assign: { Method: "POST", Path: "assign" }
Gitlab:
  Domain: gitlab.com

Github.Gateways, Github.Gateways.Public.Services and Github.Gateways.Public.Services.Tags.Endpoints are all not literally but semantically lists. There could be contexts that iterating over items of those lists (whose types are hypothetically []Gateway, []Service, []Endpoint)  inevitable; eg. a generic function that takes a list of Endpoints and registers into router.
Considerations:

List items in YAML files are not required to share same schema.
Field names are not available to iterating over, since they only exist before compilation.

Commit 3e83735cf9d5a9ea26eb3e2be97276c47a133b2e solves the issue by generating named types for those "dict" type structs and implementing .Range() map[string]itemType method on them.
Range method gets generated for types only its all fields in same type.
Rest of the considerations are not currently in roadmap.


AsyncFtpClient - The operation has timed out

FTP Server OS: Windows
FTP Server Type:  IIS
Client Computer OS: Windows
FluentFTP Version: 50.0.1
Framework: .NET 7
I'm connecting to the AsyncFtpClient but i'm getting "the operation has timed out" on every call i do:
DirectoryExists, DeleteDirectory, CreateDirectory, UploadStream, UploadFile

I have tried with both my own cancellationToken and without it. Im still getting the same error "the operation has timed out". It doesn't let me do anything??
Note - I can connect to the FTP successfully but can't do anything after that. I also tried using the FtpClient, but getting the same issue there.

Unless you post a verbose log of the sequence of events, I am afraid there is not much one could do for you here. I just used an ASYNC client on V50.0.1 with .NET 6 a few moments ago, it worked.
And I am not sure that this is really what you mean to say: "I'm connecting to the AsyncFtpClient".
Put yourself in my shoes: I must deduce from your prose, that the AutoConnect must have worked, for example, but more than that I know nothing, not the FEAT reply of the server (or must I google that for IIS or test it quickly myself).
My crystal ball is at the cleaners right now, so even that doesn't help.
Post a log, OK?

Hi!
I managed to get a log from an UploadStream call:
UploadStream("8721056381685/8721056381685.xml", NoCheck, False)
OpenWrite("8721056381685/8721056381685.xml", Binary, −1, False)
Command:  TYPE I
Status:   Waiting for response to: TYPE I
Response: 200 TYPE is now 8-bit binary [24ms]
OpenDataStreamAsync("STOR<PHONE_NUMBER>685/8721056381685.xml", 0)
OpenPassiveDataStreamAsync(PASV, "STOR<PHONE_NUMBER>685/8721056381685.xml", 0)
Command:  PASV
Status:   Waiting for response to: PASV
Response: 227 Entering Passive Mode (178,237,44,159,131,201) [24ms]
Status:   Connecting to IP #1= ***:33737
Command:  STOR<PHONE_NUMBER>685/8721056381685.xml
Status:   Waiting for response to: STOR<PHONE_NUMBER>685/8721056381685.xml
Response: 150 Accepted data connection [25ms]
Warning:  SSL Buffering disabled because of .NET 5.0 and later
Status:   FTPS authentication successful, lib = .NET SslStream, cipher suite = Tls12 (Aes256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, DiffieHellman, 0) [57ms]
Status:   Uploaded 3566 bytes
Status:   Disposing(async) FtpSocketStream(data connection of AsyncFtpClient)
Status:   Waiting for response to: STOR<PHONE_NUMBER>685/8721056381685.xml
Status:   Error encountered uploading file

And here is a log from DeleteDirectory:
DeleteDirectory("8721056381685")
GetListing("/8721056381685", Auto)
Command:  TYPE I
Status:   Waiting for response to: TYPE I
Response: 200 TYPE is now 8-bit binary [27ms]
OpenDataStreamAsync("MLSD /8721056381685", 0)
OpenPassiveDataStreamAsync(PASV, "MLSD /8721056381685", 0)
Command:  PASV
Status:   Waiting for response to: PASV
Response: 227 Entering Passive Mode (178,237,44,159,118,178) [24ms]
Status:   Connecting to IP #1= ***:30386
Command:  MLSD /8721056381685
Status:   Waiting for response to: MLSD /8721056381685
Response: 150 Accepted data connection [24ms]
Warning:  SSL Buffering disabled because of .NET 5.0 and later
Status:   FTPS authentication successful, lib = .NET SslStream, cipher suite = Tls12 (Aes256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, DiffieHellman, 0) [61ms]
+---------------------------------------+
Status:   Disposing(async) FtpSocketStream(data connection of AsyncFtpClient)
CloseDataStream()
Status:   Waiting for response to: MLSD /8721056381685

I need to see a download attempt, can you?

Thanks for that last log, it looks very bad now.
In your original post:

Note - it works perfectly fine with the sync FtpClient, but i need the AsyncFtpClient to send in my cancellationToken.

Then you edited:

Note - I can connect to the FTP successfully but can't do anything after that. I also tried using the FtpClient, but getting the same issue there.

I suppose that SYNC and ASYNC have the same problem, right???
I will write more in the next post...

Correct, it worked in the beginning for me when i started using SYNC. Then i changed the code ASYNC and i started to get the operation timeout problem. Then i changed back to SYNC to test that again - but then i got the same operation timeout problem again. That was why i edited my first comment.

It seems that the PASV command gives an IP and PORT to connect to, which succeeds. Then the SSL negotiation, which means some data going back and forth on that connection, succeeds. And then, it seems, the connection drops. Even the control connection becomes dead.

I agree, feels strange. No corporate, just me at home. Running an Azure SQL database created in Docker Desktop in my local environment.

MLSD - no data received
RETR - no data received
STOR - able to write 3566 bytes to the network, it probably gets stored in a buffer somewhere but does not reach the server.
Aahh! AZURE. In Docker. That's a big gotcha. I have some suggestions.

You would need first to verify functionality using a manual FTP client of your choosing, such as WinSCP or FileZilla accessing that server - the AZURE SQL database running in the docker container. Did I get that right?
See if that works, first.

I mean, I am not an AZURE knowleagable person - so tell me: Exactly where are you running the client code? And exactly where is the server located?

I put a lot of Azure labels on this, even if they are not necessarily on target. Helps others find Azure related stuff.

I'm using the app 'Commander One' to access to the FTP manually, it's exactly like FileZilla. I'm able to access it if that is what you meant?
I have a Blazor WASM app, with both client and server project. Server is located in a Docker Container with the image:
"mcr.microsoft.com/azure-sql-edge"

Commander One running on the same physical machine as Balzor WASM app? Docker Container also on that physical machine?

Well it's all localhost/development environment so everything is from my computer, correct!
I can manually download/upload files to the FTP using Commander One program, but i can't do it using FluentFTP in my c# code

I tried restarting my docker container - didn't help

With this kind of configuration, if this is all on your machine, I would

Install Wireshark and take a trace of the download attempt. I would study that trace and probably know more after that.
Perhaps use FluentFTP.GnuTLS instead of the standard .NET SslStream, it produces more log information, but not as good as using wireshark.
I would try to see the server logs, very much a hassle if it inside the container.

but i can't do it using FluentFTP in my c# code

Trouble is, that code is also running (as opposed to FileZilla etc.) in a sort of different environment (Blazor? Yuck...) so the comparison is not totally exact.

Try an excerpt of your ftp code in a c# console app, first, maybe

Is there any chance, even if only once for testing, to try without encryption? Allow this in the server? Let's see if there is a difference.

it worked in the beginning for me when i started using SYNC. Then i changed the code to ASYNC and i started to get the operation timeout problem. Then i changed back to SYNC to test that again - but then i got the same operation timeout problem again

I have debugging experience and this is also something you need to worry about: Until you can get it to work again like in the beginning with SYNC, something is still very fishy

Hi again. I created a new Console app with simple code to just delete an existing folder:

Listen: This kind of problem (with Azure, Docker and other "strange" environments) has plagued us for a long time already. If there is any kind of things I can modify in FluentFTP, not in the Nuget but in special GitHub branches/repos to help diagnose, I am available. I really wonder what makes the connection simply stop , especially as the Ssl Handshake needs at least certain number of transactions on the data connection to succeed.

Try unencrypted, if you can. SslStream is slightly finnicky concerning the connection
Try FluentFTP.GnuTLS instead of SslStream, it is much more robust.
Send me a Wireshark, it is my swiss knife
In the end, you might not succeed - many others have tried.

Especially two Wireshark traces: 1. The console App which works 2. The fail in the Blazor App
And then to compare those two.... :-)

@FanDjango so this issue was closed because no further info was provided? (i can't see a linked PR to this issue)

Yes.


[SUPPORT] hoodie.combine.before.insert silently broken for bulk_insert if meta fields disabled (causes duplicates)

Describe the problem you faced
hoodie.combine.before.insert works with bulk_insert if the meta fields are enabled but silently does not work and causes duplicates if disabled (ie. "hoodie.populate.meta.fields": "false").
To Reproduce
I provided a trivial reproduction below (hoodie.populate.meta.fields seems like only option that matters on whether bug happens):
# Generate dummy data
from pyspark.sql import Row

input_data = [
    Row(
        id=4,
        value="foo",
        ts=0,
    ),
    Row(
        id=4,
        value="bar",
        ts=1,
    ),
]
df = spark.createDataFrame(input_data)

# Example Hudi configs
hudi_options = {
    "hoodie.table.name": "fake_name",
    "hoodie.datasource.write.table.name": "fake_name",
    "hoodie.datasource.write.table.type": "COPY_ON_WRITE",
    "hoodie.datasource.write.hive_style_partitioning": "true",
    "hoodie.metadata.enable": "false",
    "hoodie.bootstrap.index.enable": "false",
    "hoodie.datasource.write.partitionpath.field": "",
    "hoodie.datasource.write.recordkey.field": "id",
    "hoodie.datasource.write.precombine.field": "ts",
    # Testing out bulk insert
    "hoodie.combine.before.insert": "true",
    "hoodie.datasource.write.operation": "bulk_insert",
}

PATH = "hdfs:///example_github
df.write.format("hudi").options(**hudi_options).mode("overwrite").save(PATH)

# Should be 1 but prints 2
print(spark.read.format("hudi").load(PATH).count())
# Both rows exist
print(spark.read.format("hudi").load(PATH).collect())

Expected behavior
The following is surprising:

bulk_insert deduplicates properly if hoodie.populate.meta.fields is enabled
bulk_insert does not deduplicate if hoodie.populate.meta.fields is disabled
insert deduplicates properly regardless of hoodie.populate.meta.fields

I think the user expectation is that bulk_insert has consistent/documented behavior regardless of hoodie.populate.meta.fields. Ideally we would like hoodie.combine.before.insert to work.
Environment Description
This runs on https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-6101-release.html

Hudi version : 0.12.2

Spark version : 3.3.1

Hive version : 3.1.3

Hadoop version : 3.3.3

Storage (HDFS/S3/GCS..) : HDFS/S3 both seem affected

Running on Docker? (yes/no) : Yes

Additional context
We would love to update to a new version of Hudi but there are serious blocking bugs with key generators that are still open:

https://github.com/apache/hudi/issues/10508 ("The ComplexKeyGenerator does not produce the same result for 0.14.1 than previous versions.")
https://github.com/apache/hudi/issues/8372 (CustomKeyGenerator does not work with delete partitions operation)

Is there a way to workaround this on our current version of Hudi?

@mzheng-plaid This issue still exists in 0.14.1. I confirmed that this issue is only there for bulk_insert and hoodie.populate.meta.fields as false. (as mentioned by @mzheng-plaid )
Created a jira ticket for tracking too - https://issues.apache.org/jira/browse/HUDI-7717

@mzheng-plaid @ad1happy2go The issue could be closed.
Fixed in master branch: 7fc5adad7aa9787e961c36536a08622f62fabe49

Thanks a lot @geserdugarov


Document how Mixpanel treats App Extensions

I'm currently in the process of moving from Flurry to Mixpanel for the purpose of tracking events in my iOS Keyboard App Extension. While it seems the regular library can be used in both targets, I'm curious as to what limitations there are in the App Extension target, best practices on using Mixpanel in one (because there is no App Delegate), and how events from the extension are treated in the Dashboard compared to those from a regular app. I have not found much, if any, information on how Mixpanel treats App Extensions on your developer site, help site, or this GitHub repo.

@alekplay Regarding the Dashboard treatment, they'll be treated identically to the app's. If you need to keep track of the source of the event, you may want to attach the bundle identifier onto the event's parameters to tell which extension reported what.
Also, as I'm sure you're aware, keyboard extensions are treated differently from other extensions due to the sensitivity of user input. Your keyboard extension will have to declare that it wants open access which the user would have to grant before you'd be able to do any sort of networking (similar to user's enabling location services except the users have to specifically go to it in Settings I believe).  App Store Review will also likely be interested to know why you need Open Access & what data is being transmitted to who for what purpose.

thanks @abotkin-cpi !

Thanks @abotkin-cpi, @zihejia.
I've noticed that the Automatic Events (such as App Session) are not being tracked in my Keyboard Extension. [Mixpanel sharedInstanceWithToken:...] is being called when the extension is launched, and manual events are tracked fine. Is this intended behavior? How can I track such events in the Extension?
Furthermore, I also noticed that the events are not attached to the same user I identified previously in the main app. In fact, they've got a completely different Distinct ID. Is this also intended? How can I ensure the Distinct ID set while in the app is also being used in the extension?

@alekplay Can't speak to the Automatic Events as I haven't looked into them.
On the distinct ID, if you're relying on the default distinct ID (which should be IDFV unless you've set the distinct ID yourself via identify: OR you included AdSupport.framework and got the IDFA instead), what is the bundle ID set for your keyboard extension & how does it relate to your main app?  The IDFV as specified in documentation will only be the same if you follow the app extension bundle ID standards where your main app's bundle ID prefixed your app extension's bundle ID (ex. main app is "com.yourcompany.yourapp" & extension is "com.yourcompany.yourapp.keyboardextension").
If you're calling identify: yourself with some value though, you'll need to ensure that value you pass in the main app is saved somewhere that the extension can retrieve it (shared keychain, shared app group container, shared user defaults, etc.) and then when your extension comes up, you'll want to call identify: with that value from within the app extension process.  For keyboard extensions, I think again this is another case where you need the Open Access granted by the user in the Settings app as I vaguely remember the keyboard extension can't access these shared data spaces without it (since they could be used as a way for the developer to pipe out user input).
Disclaimer: Just a third-party who uses Mixpanel

@abotkin-cpi Thank you for your answer!
As for the distinct ID, I do set that myself. I assumed the Distinct ID used by mixpanel was shared between all the targets, but if that's not the case then I can go ahead and manually duplicate that in both my app and extension. I will give that a try at once and update you if it did not work.
As for the automatic events, @zihejia I would love some more information on these.

After a little searching, it seems the reason the session event ($ae_session) is not being tracked in my keyboard extension is that Mixpanel triggers it after the appWillResignActive notification is posted. This does not happen in app extensions.
https://github.com/mixpanel/mixpanel-iphone/blob/2a4da3ac0783dc476a5b15cdd44d4c30ffe34f40/Mixpanel/AutomaticEvents.m#L88
The team may want to look into ways of triggering this in a different manner such that app-extension sessions are also logged. In the meantime, I will go ahead and create a separate Extension Session event and trigger that in my keyboard extension (alternatively just triggering the $ae_session event itself). I'm open for suggestions if anyone knows of a better way to do it.

I'm currently in the process of moving from Flurry to Mixpanel for the purpose of tracking events in my iOS Keyboard App Extension. While it seems the regular library can be used in both targets, I'm curious as to what limitations there are in the App Extension target, best practices on using Mixpanel in one (because there is no App Delegate), and how events from the extension are treated in the Dashboard compared to those from a regular app. I have not found much, if any, information on how Mixpanel treats App Extensions on your developer site, help site, or this GitHub repo.

Yes I have some


commend line Vs. API

I write python code to segment given words, main code is :
model=io.read_any_model(model.bin')
with open(test.txt,'r') as OutputFile:
                for line in InputFile:
                        words=line.strip().split()
                        morphemes=[(w," ".join(model.viterbi_segment(w)[0])) for w in words]

only few words segmented, but i used the same model on commend line to segment the same text, and most of the words are segmented,
$morfessor-segment -l model.bin test.txt
So any idea what is wrong in my python code? thank you!!!

The most logical thing would be if you are using the wrong encoding. Did you make sure that the InputFile is opened with the right encoding flag? Morfessor uses internally always unicode strings (unicode in python2, str in python3)

Thank you!!! It helps...


Cant run local engine with error:  /../flutter/flutter/packages/flutter/lib/src/rendering/layer.dart:2308:38: Error: 'PhysicalShapeEngineLayer' isn't a type.

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
I have followed the guides here:
Engine dev environment
Compiling the engine
Debug The build
I am on arm64 Mac.
After fetching the repos

Q1: Could u please explain why after fetching all the repos the flutter Engine (src/flutter) is on specific commit? (I would anticipate it following the master)
Q2: how the src repo related to  src/flutter? If I jump to to different branches in the src/flutter should I also do something in the src repo OR gclient sync would be enough? should the  gclient sync run from src repo or it doesn't matter.
I have did:
./flutter/tools/gn --ios --simulator-cpu=arm64 --unoptimized
ninja -C out/ios_debug_unopt_arm64 && ninja -C out/host_debug_unopt
My flutter version:
Flutter 3.10.6 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f468f3366c (9 days ago) • 2023-07-12 15:19:05 -0700
Engine • revision cdbeda788a
Tools • Dart 3.0.6 • DevTools 2.23.1

As far as I understand this is the flutter framework, whenever I build and use the engine I still use that precompiled framework
Q3: please correct me if I am wrong about the above.
Q4: The framework might not work with every engine so flutter/bin/internal/engine.version that hash should be used to checkout on the engine OR how do I make sure which flutter framework support which engine?
I have the following use case:
Q5: If I want to develop a plugin BUT during the development I would like to test in on the stable and master channels.
What the proper process you would recommend? check out the stable or the master in the framework get the engine version (via engine.version)and check that out and build? (I am still not sure what role plays the src repo, buildroot)
My issue is more about general knowledge, I will make the engine work but I would like to understand the underhood  so I could create a proper process in my company.
Thanks a lot for your help.
Expected results
The app runs and compile with local engine
Actual results
error: ../../../../flutter/flutter/packages/flutter/lib/src/rendering/layer.dart:2308:38: Error: 'PhysicalShapeEngineLayer' isn't a type.
        oldLayer: _engineLayer as ui.PhysicalShapeEngineLayer?,
                                     ^^^^^^^^^^^^^^^^^^^^^^^^
../../../../flutter/flutter/packages/flutter/lib/src/rendering/layer.dart:2302:29: Error: The method 'pushPhysicalShape' isn't defined for the class 'SceneBuilder'.
 - 'SceneBuilder' is from 'dart:ui'.
Try correcting the name to the name of an existing method, or defining a method named 'pushPhysicalShape'.
      engineLayer = builder.pushPhysicalShape(
                            ^^^^^^^^^^^^^^^^^
../../../../flutter/flutter/packages/flutter/lib/src/semantics/binding.dart:23:9: Error: The setter 'onSemanticsAction' isn't defined for the class 'PlatformDispatcher'.
 - 'PlatformDispatcher' is from 'dart:ui'.
Try correcting the name to the name of an existing setter, or defining a setter or field named 'onSemanticsAction'.
      ..onSemanticsAction = _handleSemanticsAction
        ^^^^^^^^^^^^^^^^^
../../../../flutter/flutter/packages/flutter/lib/src/semantics/semantics.dart:673:60: Error: Member not found: 'doNotUseWillBeDeletedWithoutWarningValuesAsList'.
      for (final SemanticsAction action in SemanticsAction.doNotUseWillBeDeletedWithoutWarningValuesAsList)
                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
../../../../flutter/flutter/packages/flutter/lib/src/semantics/semantics.dart:685:54: Error: Member not found: 'doNotUseWillBeDeletedWithoutWarningValuesAsList'.
      for (final SemanticsFlag flag in SemanticsFlag.doNotUseWillBeDeletedWithoutWarningValuesAsList)
                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
../../../../flutter/flutter/packages/flutter/lib/src/semantics/semantics.dart:2761:46: Error: Member not found: 'doNotUseWillBeDeletedWithoutWarningValuesAsList'.
    final List<String> flags = SemanticsFlag.doNotUseWillBeDeletedWithoutWarningValuesAsList.where((SemanticsFlag flag) => hasFlag(flag)).map((SemanticsFlag flag) => flag.toString().substring('SemanticsFlag.'.length)).toList();
                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
../../../../flutter/flutter/packages/flutter/lib/src/widgets/text_selection.dart:3262:13: Error: The type 'AppLifecycleState' is not exhaustively matched by the switch cases since it doesn't match 'AppLifecycleState.hidden'.
 - 'AppLifecycleState' is from 'dart:ui'.
Try adding a default case or cases that match 'AppLifecycleState.hidden'.
    switch (state) {
            ^
../../../../flutter/flutter/packages/flutter/lib/src/scheduler/binding.dart:389:13: Error: The type 'AppLifecycleState' is not exhaustively matched by the switch cases since it doesn't match 'AppLifecycleState.hidden'.
 - 'AppLifecycleState' is from 'dart:ui'.
Try adding a default case or cases that match 'AppLifecycleState.hidden'.
    switch (state) {
            ^
Target debug_unpack_ios failed: Exception: No iOS frameworks found in /Users/michael.rozenblat/Desktop/flutter/engine/src/out/ios_debug_unopt_arm64/Flutter.xcframework
Target kernel_snapshot failed: Exception
Failed to package /Users/michael.rozenblat/Desktop/flutter_pendo/sample_apps/my_app/my_app.

Code sample
there is no actual code sample
flutter create my_app
and
flutter run --local-engine=$HOME/Desktop/flutter/engine/src/out/ios_debug_unopt_arm64
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
flutter doctor -v
[✓] Flutter (Channel stable, 3.10.6, on macOS 13.4.1 22F82 darwin-arm64, locale en-IL)
    • Flutter version 3.10.6 on channel stable at /Users/michael.rozenblat/Desktop/flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (9 days ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/michael.rozenblat/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • 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-14.3.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.12.1

[✓] 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.80.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • iPhone 14 Pro (mobile) • 178D5317-EE26-465D-811E-7ED06BC11E2B • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.4.1 22F82 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 115.0.5790.102

[✓] Network resources
    • All expected network resources are available.

Hi @mraleph,
Maybe if you have a few spare minutes you could answer some of the question I had in the ticket. I can make the engine work but I would like to understand the underhood of the build process. I think my questions don't require really digging in to the issue
Thanks a lot

ok switching channel to master seems like run with local engine. (kinda anticipated). So probably the issue was caused by mismatching of flutter framework with the engine

So although it runs from command line it crashes if I get run via Xcode

so checking out  the 3.10.6 stable and building the engine withe from engine.version  checkout seems to work.
I guess there is some issue on the master

Hi @MikePendo
The goal of this Github repo is to improve flutter reporting bugs or feature requests.  Please see flutter's community for resources and ask questions above.
I'm not sure what is your current engine revision in the local engine repo (src/flutter). But taking a look at the error from the stack trace, it might be caused by it is missing https://github.com/flutter/engine/pull/42418. I see its commit is only available on some master versions, see https://github.com/flutter/engine/commit/81839ac81a644b58c598cbf3560eb9e76aafceeb. So I would suggest you fetch the latest engine version and retry. And when you check the engine build, please remember you set --local-engine-src-path param in the run command.

@huycozy
Thanks, what do u mean some master versions? isn't it a single master.
in general the best approach to fetching the master would be:
To checkout master  channel and then use engine.version to check out the engine and build?
in that case what the src buildroot responsible for? (I mean do we need to update it to something specific).

what do u mean some master versions? isn't it a single master.

You can click to "more" button to see all available versions contain that commit.

in that case what the src buildroot responsible for?

It's build environment for the Flutter engine (as described in the repository's README file)
Could you confirm the issue has been solved on the latest master engine version? Please make sure you pull the latest changes from upstream:
git pull upstream main in src/flutter to update the Flutter Engine repo.


Integration test failures in Git smoke tests

Some of the latest builds failed with a integration test failure in Git smoke test. An example is here: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=230425&view=logs&j=9833cdaa-2e92-5f8d-56a8-239fd18fd628&t=edbe7b40-a28f-5623-0f73-30c2af7b2039
  git smoke test
2023-09-04 16:35:16.607 Code - Insiders Helper (Renderer)[8675:57014] CoreText note: Client requested name ".NewYork-Regular", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].
    ✔ reflects working tree changes (4749ms)
    ✔ opens diff editor (568ms)
    ✔ stages correctly (151ms)
    1) stages, commits changes and verifies outgoing change
Switched to branch 'test'
Switched to branch 'main'
    ✔ rename/delete conflict (6115ms)
  33 passing (1m)
  1 failing
  1) git smoke test
       stages, commits changes and verifies outgoing change:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/runner/work/1/s/extensions/git/out/test/smoke.test.js)
      at listOnTimeout (node:internal/timers:569:17)
      at processTimers (node:internal/timers:512:7)

Related to https://github.com/microsoft/vscode/pull/192161/files.

Still getting this https://dev.azure.com/monacotools/Monaco/_build/results?buildId=275726&view=logs&j=0304f796-6596-5b42-8573-3d5da85bc4a5&t=3408b3dd-e53f-56a6-90e3-02cabcda26b7

Closing as I have done quite some work in recent months to improve the reliability of the git integration tests.


Update golden file tests to use static versions

What this PR does / why we need it:
When bumping release versions we don't want to have to update tests.
By making this change we ensure the values would have matched the
build versions, but we no longer require the tests to be updated
when we modify that value.
Which issue(s) this PR fixes
Fixes #745
Special notes for your reviewer:
You could test this by:

run the tests (confirm they pass)
modify the buildinfo.Version value manually
rerun tests (confirm they still pass)

Also, fyi, lots of these changes are due to gofmt -s simplifying some of the syntax.
Release note:
N/A

Codecov Report

Merging #751 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #751   +/-   ##
=======================================
  Coverage   42.59%   42.59%
=======================================
  Files          70       70
  Lines        4029     4029
=======================================
  Hits         1716     1716
  Misses       2208     2208
  Partials      105      105

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6d02613...e4d6073. Read the comment docs.


Set playing to true doesnt play the video on iOS

Hi,
Im using the latest version of your player which is great!
I have an issue with my videos on iOS...
Its just doesnt play although its set to mute (only in safari)
android works just fine
<ReactPlayer
            ref={videoRef => (this._videoPlayer = videoRef)}
            url={this.urlsArray}
            style={style}
            playing={this.shouldPlayVideo()}
            config={config}
            muted={true}
            volume={0}
            loop={loop}
            width="100%"
            height="100%"
          />

This is how I use it... this.shouldPlayVideo returns true or false.
Im trying to play a video from a file....
Thanks for your help!

Solved, if someone else encounters this issue the missing part was to add playsinline={true} to the component props


Include throwable in FailedWorkRecycler log statement

:pencil: Description
Minor enhancement for easier troubleshoot of failures - passing the throwable as the last parameter into slf4j logger allows the stack trace and root cause exception to show up in the logs.
Was tested by running locally and verifying the log entries contain more information than just the exception message
:link: Related Issues

Extensions should have the ability to log the entire Error/Stacktrace if desired. I'd say it is undesirable to do so by default


Hey hey! Latest version of the Nova Wallet (8.7.2) currently supports adding custom networks. Please, let us know if it solves your issue.

          Hey hey! Latest version of the Nova Wallet (8.7.2) currently supports adding custom networks. Please, let us know if it solves your issue.

Originally posted by @ERussel in https://github.com/novasamatech/nova-wallet-ios/issues/853#issuecomment-2416362812

Hello @alialobidm  A support ticket has been opened for you. Kindly Talk to Support on the Live support page so that your issue can be looked into. CLICK HERE


Trying to speed up type handling

This PR should speed up type handling immensely. The list of first oder types is now a map of a list instead of a list. The issue is that we have a lot of "types" (remember, a "type" is a unique combination of a scope and a name), we potentially have many scopes and a simple "myType" can exist as multiple Type nodes before the type resolver harmonises this. In order to at least have unique types per scope, we iterate existing types and return one that matches the name/scope combination. This was previously done over the complete list and is now only restricted to those types whos name matches in the first place.
This is more a workaround than a complete solution to the problem of types but should at least be significantly faster now.
As a benchmark I parsed http://github.com/openstack/glance. This speeds up the parsing from 73s to 42s.


create pseudo-probability from ensemble of different classifiers and hyperparameters

we now have code for easily setting up classification pipelines. We should do this for several classifiers, and several hyperparameters for each, to one or more ensembles of results. The result of each could e considered a vote and tallied up for each profile. This could be normalised by the number of results so that the tallies add up to one in a probability like fashion. So for example if 4 classifier vote T4 sippican and 6 classifiers vote T7 sippican, we can say 0.4 prob of T4 and 0.6 prob of T7.

This has now been demonstrated in notebooks and implementedin the experiment framework.


Add function to get mime type from file name

This function is needed to supply information for the http protocol.

Your suggestion looks valid and safe. I will add it to the baseapp in the coming days.

This pull request has been addressed through pull request #46. The code will ship with January update.


test : Adds RedisTest.testRedisAddItemSetsExpires

Adds test for ensuring addItem adheres to TTL as expected. Test is a variation of the CommonAdapterTest.testHasItemReturnsFalseOnExpiredItem.

Closed for #2; Test code moved to CommonAdapterTest.


Snackbars are not going away (sometimes?)

Describe the bug
This has now happened twice -- a Snackbar (in Code) is staying around indefinitely.
How to reproduce
not sure -- got as a "Could not find" message -- needs further testing.
Example code
No response
Relevant output
No response
Platform
macOS

might be good to add a failsafe click to dismiss feature -- would be nice in any case.  perhaps was already there at some point?


Reverse time axis

Small bug I found.
Any stencil of the form lhs = rhs * time overwrite the time axis as forward even with time_axis=Backward.
The bug hapens line 94 of operator  at   clusters = rewrite(clusters, mode=dse)

Please enclose a minimal failing executable example

example :
b = TimeData(name='b', shape=(11, 11), time_order=1,
                 time_dim=6, save=False)
eqn = Eq(b.backward, time * b - 1.)

Operator(eqn, dle=None, dse='advanced', time_axis=Backward)()

produces:
#define _POSIX_C_SOURCE 200809L
#include "stdlib.h"
#include "math.h"
#include "sys/time.h"

struct profiler
{
  double loop_t_0;
} ;

int Kernel(float *restrict b_vec, const int t_size, const int x_size, const int y_size, const int time_size, struct profiler *timings)
{
  float (*restrict b)[x_size][y_size] __attribute__((aligned(64))) = (float (*)[x_size][y_size]) b_vec;
  struct timeval start_loop_t_0, end_loop_t_0;
  gettimeofday(&start_loop_t_0, NULL);
  for (int time = 1; time < time_size; time += 1)
  {
    int t0 = (time) % 2;
    int t1 = (time - 1) % 2;
    for (int x = 0; x < x_size; x += 1)
    {
      for (int y = 0; y < y_size; y += 1)
      {
        b[t1][x][y] = time*b[t0][x][y] - 1.0F;
      }
    }
  }
  gettimeofday(&end_loop_t_0, NULL);
  timings->loop_t_0 += (double)(end_loop_t_0.tv_sec-start_loop_t_0.tv_sec)+(double)(end_loop_t_0.tv_usec-start_loop_t_0.tv_usec)/1000000;
  return 0;
}

The time loop is in the wrong order AND with wrong bounds. This is only the case with dse enabled, no problem with dse=None

wdym by wrong order? you mean it's Forward rather than Backward? I'll check tmr


Drag and drop

Hi @jemise111 ,
It would be possible to implement an example that allows drag and drop, if it is enabled.

Hey @Angelk90, drag and drop is a separate feature set that is a really out of the scope of this component. I would recommend using one of the OS drag and drop flatlist libraries and in the renderItem use a <SwipeRow /> from this library. You'll lose a little of the built in 'SwipeListView' functionality but it should get you a good chunk of the way there. Hope that helps!

I wonder if it's possible to combine it with this library https://github.com/computerjazz/react-native-draggable-flatlist


Bug(hub-nodejs/examples): Chron feed example script result in HubError: NotFound if one the fids is not resolved

What is the bug?
Chron feed example script index.ts result in HubError: NotFound if one of the fids is not resolved to a fname.
I found that some fids are not resolved to a fname (e.g. fid: 12993) and it result in a broken script even if the other fids can be resolved.
How can it be reproduced?
You can reproduce the bug by running theindex.ts script located in hub-nodejs/examples/chron-feed/index.ts, with the following FIDS array as a parameter.
const FIDS = [2, 3, 12993];
It will result with the following error:
Fetching fnames failed
HubError: NotFound:
    at fromServiceError (file:///Users/yanismeziane/Desktop/hub-monorepo/packages/hub-nodejs/examples/chron-feed/node_modules/@farcaster/hub-nodejs/dist/index.mjs:6480:10)

The result expected should be to return the messages feed, with only the non resolved fnames as undefined.
Potential solution
Here is the actual code:
  // 1. Create a mapping of fids to fnames, which we'll need later to display messages
  const fidToFname = new Map<number, string>();

  const fnameResultPromises = FIDS.map((fid) => client.getUserData({ fid, userDataType: UserDataType.FNAME }));
  const fnameResults = Result.combine(await Promise.all(fnameResultPromises));

  if (fnameResults.isErr()) {
    console.error('Fetching fnames failed');
    console.error(fnameResults.error);
    return;
  }

The workaround I found is the following one:
  // 1. Create a mapping of fids to fnames, which we'll need later to display messages
  const fidToFname = new Map<number, string>();

  const fnameResultPromises = FIDS.map((fid) => client.getUserData({ fid, userDataType: UserDataType.FNAME }));
  const fnameResultPromisesSettled = await Promise.allSettled(fnameResultPromises);
  const successfulResults = fnameResultPromisesSettled
    .filter((result) => result.status === 'fulfilled')
    .map((result) => (result as PromiseFulfilledResult<Result<any, any>>).value)
    .filter((result) => result.isOk());
  const fnameResults = Result.combine(successfulResults);

  if (fnameResults.isErr()) {
    console.error('Fetching fnames failed');
    console.error(fnameResults.error);
    return;
  }

I'm open to do a PR if you think that this is a good solution and if the bug need to be resolved.

@Meyanis95 thanks for the report.
I'm open to a PR, I think the right fix is to attempt to fetch the fnames and if one of the promises returns an error, replace it with a string like fid:xyz which can be used instead of the fname.


feat(tenants): initial tenants module

Initial version of the tenants module. This is not fully finished yet and ready for prime time, but it contains most of the things needed for multi-tenancy. It doesn't introduce any breaking changes (those were addressed in the PRs this PR depends on).
Dependant on:

#920
#921
#922

Until the modularization is fully here the API for registering module is not really nice, but I see that as a separate task that we can address after multi-tenancy has been merged. This is how you use it:
import { DependencyManager, Agent } from '@aries-framework/core'
import { TenantsApi, TenantsModule } from '@aries-framework/module-tenants'
import { agentDependencies } from '@aries-framework/node'

// create dependency manager and register module
const dependencyManager = new DependencyManager()
dependencyManager.registerModules(TenantsModule)

// create agent, and resolve tenants api
const agent = new Agent({ /* config */, agentDependencies , dependencyManager)
const tenantsApi = agent.dependencyManager.resolve(TenantsApi)

const tenantRecord = await tenantsApi.createTenant({
  config: {
   label: 'Tenant 1',
  },
})

const tenantAgent = await tenantsApi.getTenantAgent({
  tenantId: tenantRecord.id,
})

// Create oob invitation in scope of tenant
const outOfBandRecord = await tenantAgent.oob.createInvitation()

I would like to already merge so we can keep PRs reasonable (this is already getting quite large).
Basically the only thing that's left to do is correctly managing the tenant lifecycle and managing tenant sessions (see https://hackmd.io/vGLVlxLvQR6jsEEjzNcL8g?view#Tenant-Lifecycle). Currently, wallets are being opened when needed and will not be closed afterwards. That means over time the number of open wallets keeps increasing. Correctly opening wallets and avoiding race conditions if two sessions would like to open the same wallet is handled (using async-mutex library). This does need some improvements in not waiting indefinitely.
Concrete what's still todo:

Agent lifecycle. Currently you call getTenantAgent with no proper way to dispose of the agent (session count won't be reduced)
Check we're not using context after a process is complete (e.g. by setting an event listener). This should always start a new session instead of using the session from the upper scope

I'm quite happy with how it turned out and how multi-tenancy is an optional addon without having the code in the core package.

Codecov Report

Merging #932 (a1613b1) into 0.3.0-pre (96c5ef8) will increase coverage by 0.21%.
The diff coverage is 95.95%.

@@              Coverage Diff              @@
##           0.3.0-pre     #932      +/-   ##
=============================================
+ Coverage      86.70%   86.91%   +0.21%
=============================================
  Files            518      531      +13
  Lines          12603    12854     +251
  Branches        2137     2181      +44
=============================================
+ Hits           10927    11172     +245
- Misses          1581     1587       +6
  Partials          95       95

Impacted Files
Coverage Δ

packages/core/src/agent/Events.ts
100.00% <ø> (ø)

packages/core/src/agent/context/AgentContext.ts
83.33% <0.00%> (-16.67%)
:arrow_down:

...ges/core/src/agent/models/InboundMessageContext.ts
77.77% <0.00%> (-22.23%)
:arrow_down:

.../core/src/modules/connections/ConnectionsModule.ts
67.24% <ø> (ø)

packages/core/src/wallet/IndyWallet.ts
63.28% <20.00%> (-0.87%)
:arrow_down:

...le-tenants/src/context/TenantSessionCoordinator.ts
97.22% <97.22%> (ø)

packages/core/src/agent/Agent.ts
97.56% <100.00%> (+0.01%)
:arrow_up:

packages/core/src/agent/AgentConfig.ts
95.00% <100.00%> (+4.83%)
:arrow_up:

packages/core/src/agent/BaseAgent.ts
95.29% <100.00%> (+2.03%)
:arrow_up:

packages/core/src/agent/EventEmitter.ts
100.00% <100.00%> (ø)

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 96c5ef8...a1613b1. Read the comment docs.

Additionally, maybe it's nice to add methods for creating and getting multiple tenants. E.g. createTenants([{...}, {...}, {...}, {...}]). Maybe that is too difficult regarding sessions management tho. Idk, just a thought.

We could. Do you think it will be an often used use case to create a lot of tenants at the same time? I'd like to keep the API minimal, so if you have a good use case for it, I'd be happy to add it.

So I can't think of a good use case for creating multiple tenants atm, but I can imagine wanting to execute some kind of action in batch for multiple tenants at the same time (e.g. creating a connection invite). In this case a getTenants method could be useful.

So I can't think of a good use case for creating multiple tenants atm, but I can imagine wanting to execute some kind of action in batch for multiple tenants at the same time (e.g. creating a connection invite). In this case a getTenants method could be useful.

Ok, I've made some changes to these method in a next PR. Let me look at it in that branch and see If I can come up with nice API

Merging as only failing test is the one from #923


Update MF2 definition to 2024-01-24 version

Lexer ✅
AST/Parser ✅
Builder ❌

@VladislavsPerkanuks can you please provide diff screenshot? So it is clear what changes are required.

@janishorsts Once again diff is in issue


⚠ Bofrost.at has degraded performance

In 730eb0d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1846 ms

Resolved: Bofrost.at performance has improved in 17a21d4.


signature for registry files

Problem
In registry, files are served with only checksum. I'm worrying about "supply chain attack" when developers are using 3rd party mirror of registry. Since registry can define custom dl link for replacing the origin aws s3.
this should not be confused with #4768.
This issues is talking about how to ensure the 3rd party mirror are serving the crates unmodified from the origin ones. #4768 is talking about how to ensure the registry are serving the crates from the original authors.
Proposed Solution
I propose to add an optional gpg signature as long as the checksum which is signed by the registry authority (in current situation, it's crates.io). Just like apt and other os package mange system does, it has a signing keyring signs the packages.
To maintain the backwards compatibility, the gpg signature should be optional but enforce for crates.io.
This is a valid record for now:
{"name":"NAME","vers":"VERSION","deps":[],"cksum":"CHECKSUM","features":{},"yanked":false}

The new record look like this:
{"name":"NAME","vers":"VERSION","deps":[],"cksum":"CHECKSUM","sig":"SIGNATURE","features":{},"yanked":false}

Notes
No response

Having a third party mirror of the registry serve malicious crates is already somewhat mitigated by the fact that the crate checksums end up in the lockfile. This means that if the lockfile contains the checksum for the clean version trying to use the malicious registry will result in an error, thus preventing the attack. If the lockfile contains the checksum for the malicious version trying to use the official (or a non-malicious) registry will cause a build issue, thus giving away the fact that the malicious registry is malicious.

Here's a previous RFC which proposed something quite similar: https://github.com/rust-lang/rfcs/pull/2474
It was closed with a disposition to postpone, but there's plenty of prior discussion there.
See also: https://github.com/rust-lang/crates.io/issues/75


Show startup errors, don't leave user hanging

29 Apr 16:42:33 - Error creating pidfile /tmp/sc_client-main-tunnel-pool.pid: resource temporarily unavailable
if a resource can't be obtained show user and declare tunnel a failure.

  ...bin/sc -u -k  -v --no-remove-colliding-tunnels -N -i main-tunnel-p    ool --se-port 0 --pidfile 0.pid
...bin/sc -u  -k-v --no-remove-colliding-tunnels -N -i main-tunnel-p    ool --se-port 0 --pidfile 0.pid

example failing config  above ^.  The reuse of0.pid will cause the 2nd tunnel fail to open.  Should check periodically if the tunnel failed or wait for the logfile to close then report the error and/or last 10-20 log lines.


Errors during "Generate animation frames"

Everything worked fine till i got to the Generate animation frames part.
It stopped on the fetching variations at this loop:
for _ in range(tot_variations):
Fetching variations
1
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
[<ipython-input-12-ccdc85f3c37d>](https://localhost:8080/#) in <module>
    153         tot_variations -= curr_variation_count  # only generate variations we still need
    154         for _ in range(tot_variations):
--> 155             img = get_variations_w_init(prompt, init_image, start_schedule=(1-image_consistency))[0]
    156             save_frame(
    157                 img,

3 frames
[/usr/local/lib/python3.8/dist-packages/torch/autograd/grad_mode.py](https://localhost:8080/#) in decorate_context(*args, **kwargs)
     25         def decorate_context(*args, **kwargs):
     26             with self.clone():
---> 27                 return func(*args, **kwargs)
     28         return cast(F, decorate_context)
     29

TypeError: __call__() missing 1 required positional argument: 'image'

i'm wondering if maybe this was a bug due to a change in huggingface or something like that? I swear I was able to reproduce this not that long ago, but now I can't. Can you double check if this is still an issue for you?

I got a very similar issue today.  I was able to reproduce it after reloading the notebook and rerunning everything.
Fetching variations
1
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
[<ipython-input-20-6970025e684d>](https://localhost:8080/#) in <module>
    153         tot_variations -= curr_variation_count  # only generate variations we still need
    154         for _ in range(tot_variations):
--> 155             img = get_variations_w_init(prompt, init_image, start_schedule=(1-image_consistency))[0]
    156             save_frame(
    157                 img,

3 frames
[/usr/local/lib/python3.8/dist-packages/torch/autograd/grad_mode.py](https://localhost:8080/#) in decorate_context(*args, **kwargs)
     25         def decorate_context(*args, **kwargs):
     26             with self.clone():
---> 27                 return func(*args, **kwargs)
     28         return cast(F, decorate_context)
     29

TypeError: __call__() got an unexpected keyword argument 'init_image'

I got a very similar issue today. I was able to reproduce it after reloading the notebook and rerunning everything.
Fetching variations
1
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
[<ipython-input-20-6970025e684d>](https://localhost:8080/#) in <module>
    153         tot_variations -= curr_variation_count  # only generate variations we still need
    154         for _ in range(tot_variations):
--> 155             img = get_variations_w_init(prompt, init_image, start_schedule=(1-image_consistency))[0]
    156             save_frame(
    157                 img,

3 frames
[/usr/local/lib/python3.8/dist-packages/torch/autograd/grad_mode.py](https://localhost:8080/#) in decorate_context(*args, **kwargs)
     25         def decorate_context(*args, **kwargs):
     26             with self.clone():
---> 27                 return func(*args, **kwargs)
     28         return cast(F, decorate_context)
     29

TypeError: __call__() got an unexpected keyword argument 'init_image'

Hey Andrew,  I'm having this issue as well.  Were you able to find a solution?

Unfortunately not. I've been able to generate videos in the past so I'm not sure what the cause is. Please let me know if you come up with anything.

Same with me.  I had no issues 2 days ago,  then yesterday that issue popped up.  Hopefully it just kind of fixes itself. lol

@mjea1980 ,
I tried the solution proposed in https://github.com/dmarx/video-killed-the-radio-star/pull/96 but wasn't able to get it to work.  Might be worth a shot.

@H2whoaMusic @SchmitzAndrew I tried to put together a video this morning,  and still no dice.  Its generates such cool images,  I wish it would just finish off the final step!! haha.  Hopefully one day soon it starts working again :)
@dmarx any idea what the problem could be ?  Looks like its been a known issue for a couple months now..

@mjea1980 I know, I'm in the same boat. I've generated some truly fantastic images. @dmarx was kind enough to guide me on how to modify the storyboard to make really bespoke sequences, and I'm dying to get it pulled together!

I'm getting the same issue and was able to create a video about a month ago! not sure what changed here

Same issue here! That...was not a good timing to buy Colab pro

Same issue here! That...was not a good timing to buy Colab pro

Lol, same. But I have faith that a solution will be found. It's way out of my very limited coding experience, but it's such an impressive project that I don't doubt that it will get resolved.

thanks for your patience folks and sorry for the delay, issue should be fixed now. Will close this after I've got confirmation from one of y'all that it's working for you as well.
@ianhirsch @DerisoryPull @H2whoaMusic @mjea1980 @SchmitzAndrew @VicRejkia

You’re the man! I’ll give it a go this afternoon and report back 🫡
On Wed, Mar 22, 2023 at 3:46 PM David Marx @.***> wrote:

thanks for your patience folks and sorry for the delay, issue should be
fixed now. Will close this after I've got confirmation from one of y'all
that it's working for you as well.
@ianhirsch https://github.com/ianhirsch @DerisoryPull
https://github.com/DerisoryPull @H2whoaMusic
https://github.com/H2whoaMusic @mjea1980 https://github.com/mjea1980
@SchmitzAndrew https://github.com/SchmitzAndrew @VicRejkia
https://github.com/VicRejkia
—
Reply to this email directly, view it on GitHub
https://github.com/dmarx/video-killed-the-radio-star/issues/94#issuecomment-1480160226,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJPPL2CDZK5U3A4FFYAR54DW5NJJ5ANCNFSM6AAAAAASYVXGUQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Lol My Colab pro expired a couple hours ago

So far, so good. Created a new project and taken it right through to generating animation images. Currently running and appears to be working. Actively generating images, which it was not doing before. Will confirm once completed, but looks good. Thank you!

I am now compiling my video! Was able to generate the animation frames successfully. Huge thanks to you, @dmarx


Exclude /proc and /sys

This fixes the following error while trying to install system/cos from a
container from scratch:
 DEBUG (docker.go:#66:github.com/mudler/luet/pkg/installer/client.(*DockerClient).DownloadArtifact) Cache file /var/cache/luet/packages/cos-system-0.5.7+2.package.tar.zst
 DEBUG (docker.go:#81:github.com/mudler/luet/pkg/installer/client.(*DockerClient).DownloadArtifact) Cache hit for artifact cos-system-0.5.7+2.package.tar.zst
 Failed installing package cos Error met while unpacking rootfs: lchown /sys: read-only file system
The command '/usr/bin/luet install -y -d system/cos' returned a non-zero code: 1

Signed-off-by: Ettore Di Giacinto<EMAIL_ADDRESS>

Superseded by #384


Use decimal.js or dinero.js to deal with money

Use decimal.js or dinero.js to deal with money
When computing money amounts, JS is not very precise, and can lead to unwanted UI renders:

duplicate of #1541


Issue with positions

Hi,
I'm trying include wizViewMessenger in my App: i0s, Android.
I'm having some issues with the position of  the view, depending on the platform.
My options are: 	var options = {
src: "http://www.movie.com.uy/mobile",
top: 75,
left: 0,
height: 512,
scalesPageToFit: false,
bounces: false
};
On iPhone all ok, in iPad the viewport is located on top=0, on some Android, the view apperar like a small square (ignoring height an width).
Do you have any consideration about this issue? Could you help me?
I'm using phonegap build.
Thanks in advance and thanks for the plugin.

Hello,
We could not reproduce your issue with these specific options. We used Cordova 3.6.3 and tried on portrait/landscape orientation.
Could you provide more information? Or best, could you provide a small project reproducing this issue?

Thanks. I'm going to make an example and I send it.

Hey there,
got the same ... my workaround is to add a topmargin to the source-html, wich has the same height like the top option. It seems, the view is right positioned, but the src is always on top 0. oO I am testing on iOS 8.1

@Ready2X Thanks for reporting it. Do you have a source code sample to reproduce this issue? It would be nice to fix it since several users seem to be running into this bug.


Clearer Vectorized Indexing example

[x] Passes isort . && black . && mypy . && flake8
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst

I found the existing example not that clear as to why it was selecting [[1,1],[5,5]], I think this is more obvious (open to disagreement of course!)
Before
In [37]: da = xr.DataArray(
   ....:     np.arange(12).reshape((3, 4)),
   ....:     dims=["x", "y"],
   ....:     coords={"x": [0, 1, 2], "y": ["a", "b", "c", "d"]},
   ....: )
   ....:

In [38]: da
Out[38]:
<xarray.DataArray (x: 3, y: 4)>
array([[ 0,  1,  2,  3],
       [ 4,  5,  6,  7],
       [ 8,  9, 10, 11]])
Coordinates:
  * x        (x) int64 0 1 2
  * y        (y) <U1 'a' 'b' 'c' 'd'

In [39]: da[[0, 1], [1, 1]]
Out[39]:
<xarray.DataArray (x: 2, y: 2)>
array([[1, 1],
       [5, 5]])
Coordinates:
  * x        (x) int64 0 1
  * y        (y) <U1 'b' 'b'

After:

In [4]:     da[[1, 2, 2], [0, 3]]
Out[4]:
<xarray.DataArray (x: 3, y: 2)>
array([[ 4,  7],
       [ 8, 11],
       [ 8, 11]])
Coordinates:
  * x        (x) int64 1 2 2
  * y        (y) <U1 'a' 'd'`

Yes, please.
Minor: also I'd personally find even more intuitive the selection da[[0, 2, 2], [1, 3]] that still shows you can repeat indexes, but somewhat looks more like a downsampling. Your call.

Thanks @max-sixty

& @alexamici for suggestions!


Updating licenses

/cc @Eilon

:shipit:

@pranavkm Good to merge?

:shipit: from me.

:shipit:


x2cpg: rename node creation fns

The idea is to have two consistent ways of generating nodes:

The AstNodeBuilder trait which provides fns with signatures similar to: aTypeOfNode(PROP1, PROP2, PROP3)
The NodeBuilders object which provides fns with signatures similar to: newATypeOfNode(PROP1, PROP2, PROP3, LINE, COLUMN)

I'm not sure of the best way to do this, but adding some way of enforcing this or documentation stating that this is the intent would be useful for keeping this consistent as more nodes are added.

@johannescoetzee I've added a comment

Left me wondering: should we next aim to have only newATypeOfNode(PROP1, PROP2, PROP3, LINE, COLUMN) kind of methods?

Moving everything into the AstNodeBuilder trait would also be cleaner in this case.

@xavierpinho Why? In the case of the trait, all the frontends use a consistent invocation and one doesn't need to set the line/column

Left me wondering: should we next aim to have only newATypeOfNode(PROP1, PROP2, PROP3, LINE, COLUMN) kind of methods?

Moving everything into the AstNodeBuilder trait would also be cleaner in this case.

true, nice idea!

Why? In the case of the trait, all the frontends use a consistent invocation and one doesn't need to set the line/column

They could perhaps have line and column as an optional parameter with None default. That way we can keep the existing behaviour unchanged, while also not having to worry about 2 different signature patterns (except perhaps for nodes which can't actually have a line and column set)

After having tried a few different options locally, I think it's best to keep this PR as is, remove as much of the individual NodeBuilders as possible, and only then look for further refactoring possibilities