[match] Failure During Signing After Compilation, Possibly Signing Failure OS X Sierra

After the fix for OS X Sierra keychains (#6389), we still seem to be having issues during app compilation, it seems at the very end when we begin to codesign with gym.
I believe I've included the implementations for most of our utility methods, but if not, please let me know. I am still doing a workaround by passing in a keychain_name to match, so I'm not sure if that's causing any problems?
Please let me know if I can provide any more details! (This is @kyleturner by the way on behalf of my company :))
New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
Complete output when running fastlane, including the stack trace and command used
Mobile-CI:NeXgen-iOS jenkins$ bundle exec fastlane develop --verbose
DEBUG [2016-10-06 16:32:34.86]: Checking if there are any plugins that should be loaded...
INFO [2016-10-06 16:32:34.87]: -----------------------------
INFO [2016-10-06 16:32:34.87]: --- Step: update_fastlane ---
INFO [2016-10-06 16:32:34.87]: -----------------------------
INFO [2016-10-06 16:32:34.87]: Looking for updates for credentials_manager, fastlane_core, spaceship, cert, deliver, frameit, gym, sigh, match, pem, pilot, produce, scan, screengrab, snapshot, supply, fastlane...
INFO [2016-10-06 16:32:38.69]: Nothing to update ✅
INFO [2016-10-06 16:32:38.69]: ------------------------------
INFO [2016-10-06 16:32:38.69]: --- Step: default_platform ---
INFO [2016-10-06 16:32:38.69]: ------------------------------
INFO [2016-10-06 16:32:38.75]: Driving the lane 'ios develop' 🚀
INFO [2016-10-06 16:32:38.76]: -----------------------------
INFO [2016-10-06 16:32:38.76]: --- Step: unlock_keychain ---
INFO [2016-10-06 16:32:38.76]: -----------------------------
INFO [2016-10-06 16:32:38.87]: -------------------------------
INFO [2016-10-06 16:32:38.87]: --- Step: ensure_git_branch ---
INFO [2016-10-06 16:32:38.87]: -------------------------------
INFO [2016-10-06 16:32:38.88]: Git branch match `develop`, all good! 💪
INFO [2016-10-06 16:32:38.88]: -----------------------------------
INFO [2016-10-06 16:32:38.88]: --- Step: git merge origin/beta ---
INFO [2016-10-06 16:32:38.88]: -----------------------------------
INFO [2016-10-06 16:32:38.88]: $ git merge origin/beta
INFO [2016-10-06 16:32:38.89]: ▸ {:foreground=>"magenta"}mAlready up-to-date.
INFO [2016-10-06 16:32:38.89]: -------------------------------------
INFO [2016-10-06 16:32:38.89]: --- Step: git push origin develop ---
INFO [2016-10-06 16:32:38.89]: -------------------------------------
INFO [2016-10-06 16:32:38.89]: $ git push origin develop
INFO [2016-10-06 16:32:39.83]: ▸ {:foreground=>"magenta"}mEverything up-to-date
INFO [2016-10-06 16:32:39.83]: -----------------------
INFO [2016-10-06 16:32:39.83]: --- Step: cocoapods ---
INFO [2016-10-06 16:32:39.83]: -----------------------
INFO [2016-10-06 16:32:39.83]: $ bundle exec pod install

// Install Cocoapods...

+-----------------------+-------------------------------------------------+
|                         Summary for match 0.8.1                         |
+-----------------------+-------------------------------------------------+
| type                  | development                                     |
| app_identifier        | *                                               |
| keychain_name         | login.keychain-db                               |
| readonly              | true                                            |
| git_url               | git@github.com:XVia/NeXgen-iOS-Certificates.git |
| username              |<EMAIL_ADDRESS>                              |
| git_branch            | master                                          |
| team_id               | CDNDP3ZYKL                                      |
| team_name             | Company, Inc.                                  |
| verbose               | false                                           |
| force                 | false                                           |
| shallow_clone         | false                                           |
| force_for_new_devices | false                                           |
| skip_docs             | false                                           |
+-----------------------+-------------------------------------------------+

INFO [2016-10-06 16:33:12.60]: Cloning remote git repo...
INFO [2016-10-06 16:33:12.60]: $ GIT_TERMINAL_PROMPT=0 git clone 'git@github.com:XVia/NeXgen-iOS-Certificates.git' '/var/folders/bw/86j8p8jd09x7mcvqxwpvq3k8000102/T/d20161006-40927-skloj6'
INFO [2016-10-06 16:33:12.61]: ▸ {:foreground=>"magenta"}mCloning into '/var/folders/bw/86j8p8jd09x7mcvqxwpvq3k8000102/T/d20161006-40927-skloj6'...
INFO [2016-10-06 16:33:13.42]: ▸ {:foreground=>"magenta"}mremote: Counting objects: 291, done.
INFO [2016-10-06 16:33:13.47]: ▸ {:foreground=>"magenta"}mremote: Compressing objects: 100% (16/16), done.
INFO [2016-10-06 16:33:14.25]: ▸ {:foreground=>"magenta"}mremote: Total 291 (delta 0), reused 0 (delta 0), pack-reused 275
INFO [2016-10-06 16:33:14.25]: ▸ {:foreground=>"magenta"}mReceiving objects: 100% (291/291), 626.12 KiB | 610.00 KiB/s, done.
INFO [2016-10-06 16:33:14.25]: ▸ {:foreground=>"magenta"}mResolving deltas: 100% (21/21), done.
INFO [2016-10-06 16:33:14.31]: ▸ {:foreground=>"magenta"}mChecking connectivity... done.
INFO [2016-10-06 16:33:14.34]: 🔓  Decrypted 'P2P8RUSVAA.cer'
INFO [2016-10-06 16:33:14.34]: 🔓  Decrypted '6XA4R26VAB.cer'
INFO [2016-10-06 16:33:14.35]: 🔓  Decrypted 'P2P8RUSVAA.p12'
INFO [2016-10-06 16:33:14.36]: 🔓  Decrypted '6XA4R26VAB.p12'
INFO [2016-10-06 16:33:14.37]: 🔓  Decrypted 'AdHoc_*.mobileprovision'
INFO [2016-10-06 16:33:14.37]: 🔓  Decrypted 'AppStore_com.xvia.AppName.mobileprovision'
INFO [2016-10-06 16:33:14.38]: 🔓  Decrypted 'Development_*.mobileprovision'
INFO [2016-10-06 16:33:14.38]: 🔓  Successfully decrypted certificates repo
INFO [2016-10-06 16:33:14.38]: Installing certificate...
INFO [2016-10-06 16:33:14.38]: $ security list-keychains -d user
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Library/Developer/XcodeServer/Keychains/Portal.keychain"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.40]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.41]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.41]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.41]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.41]: ▸ {:foreground=>"magenta"}m    "/Users/jenkins/Library/Keychains/login.keychain-db"
INFO [2016-10-06 16:33:14.41]: $ security find-certificate -c 'Apple Worldwide Developer Relations Certification Authority' /Library/Developer/XcodeServer/Keychains/Portal.keychain
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}mkeychain: "/Library/Developer/XcodeServer/Keychains/Portal.keychain"
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}mversion: 256
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}mclass: 0x80001000
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}mattributes:
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "alis"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "cenc"<uint32>=0x00000003
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "ctyp"<uint32>=0x00000001
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "hpky"<blob>=0x88271709A9B618608BECEBBAF64759C55254AABC  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\ABC"
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "issu"<blob>=0x3062310B300906035504061302555331133011060355040A130A4150504C4520494E432E31263024060355040B131D4150504C452043455254494649434154494F4E20415554484F52495459311630140603550403130D4150504C4520524F4F54204ABC  "0b1\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\023\012APPLE INC.1&0$\006\003U\004\013\023\035APPLE CERTIFICATION AUTHORITY1\0260\ABC\006\003U\004\003\023\015APPLE ROOT CA"
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "labl"<blob>="Apple Worldwide Developer Relations Certification Authority"
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "skid"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030`\213\354\353\272\366GY\305RT\243\267"
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "snbr"<blob>=0x01DEBCC4396DA010  "\001\336\274\3049m\240\020"
INFO [2016-10-06 16:33:14.44]: ▸ {:foreground=>"magenta"}m    "subj"<blob>=0xABC196310B300906035504061302555331133011060355040A0C0A4170706C6520496E632E312C302A060355040B0C234170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E733144304206035504030C3B4170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E732043657274696669636174696F6E20417574686F72697ABC  "0\201\2261\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\014\012Apple Inc.1,0*\006\003U\004\013\014#Apple Worldwide Developer Relations1D0B\006\003U\004\003\ABC;Apple Worldwide Developer Relations Certification Authority"
DEBUG [2016-10-06 16:41:06.38]: Certificate 'P2P8RUSVAA.cer' is already installed on this machine
INFO [2016-10-06 16:41:06.38]: $ security import /var/folders/bw/86j8p8jd09x7mcvqxwpvq3k8000102/T/d20161006-40927-skloj6/certs/development/P2P8RUSVAA.p12 -k /Users/jenkins/Library/Keychains/login.keychain-db -T /usr/bin/codesign -T /usr/bin/security
security: SecKeychainItemImport: The specified item already exists in the keychain.
INFO [2016-10-06 16:41:06.44]: Installing provisioning profile...
WARN [2016-10-06 16:41:06.95]: Setting environment variable 'sigh_*_development' to '5128c7c0-a594-4132-804a-aa7ac4c695ab'
WARN [2016-10-06 16:41:06.95]: Setting environment variable 'sigh_*_development_team-id' to 'CDNDP3ZYKL'
WARN [2016-10-06 16:41:06.95]: Setting environment variable 'sigh_*_development_profile-name' to 'match Development *'

+---------------------+---------------------------------+--------------------------------------+
|                                Installed Provisioning Profile                                |
+---------------------+---------------------------------+--------------------------------------+
| Parameter           | Environment Variable            | Value                                |
+---------------------+---------------------------------+--------------------------------------+
| App Identifier      |                                 | *                                    |
| Type                |                                 | development                          |
| Profile UUID        | sigh_*_development              | 5128c7c0-a594-4132-804a-aa7ac4c695ab |
| Profile Name        | sigh_*_development_profile-name | match Development *                  |
| Development Team ID | sigh_*_development_team-id      | CDNDP3ZYKL                           |
+---------------------+---------------------------------+--------------------------------------+

INFO [2016-10-06 16:41:06.95]: All required keys, certificates and provisioning profiles are installed 🙌
INFO [2016-10-06 16:41:06.96]: 🔒  Successfully encrypted certificates repo
INFO [2016-10-06 16:41:06.96]: Setting Provisioning Profile type to 'development'
INFO [2016-10-06 16:41:12.11]: -----------------
INFO [2016-10-06 16:41:12.11]: --- Step: gym ---
INFO [2016-10-06 16:41:12.11]: -----------------
INFO [2016-10-06 16:41:12.22]: $ xcodebuild -list -workspace ./XViaMobile.xcworkspace
INFO [2016-10-06 16:41:13.83]: $ xcodebuild clean -showBuildSettings -workspace ./XViaMobile.xcworkspace -scheme AppName-Develop

+----------------------+--------------------------+
|             Summary for gym 1.11.0              |
+----------------------+--------------------------+
| scheme               | AppName-Develop         |
| configuration        | Debug                    |
| export_method        | development              |
| workspace            | ./XViaMobile.xcworkspace |
| destination          | generic/platform=iOS     |
| output_name          | AppName-Develop         |
| clean                | false                    |
| output_directory     | .                        |
| silent               | false                    |
| use_legacy_build_api | false                    |
| buildlog_path        | ~/Library/Logs/gym       |
+----------------------+--------------------------+

Compiling X...

INFO [2016-10-06 16:44:04.05]: {:foreground=>"magenta"}m▸ Touching AppName-Develop.app
INFO [2016-10-06 16:44:08.89]: ▸ {:foreground=>"magenta"}m❌  error: Task failed with exit 1 signal 0 {
INFO [2016-10-06 16:44:09.08]: ▸ {:foreground=>"magenta"}m** ARCHIVE FAILED **
INFO [2016-10-06 16:44:09.08]: ▸ {:foreground=>"magenta"}mThe following build commands failed:
INFO [2016-10-06 16:44:09.08]: ▸ {:foreground=>"magenta"}mCopySwiftLibs /Users/jenkins/Library/Developer/Xcode/DerivedData/XViaMobile-hgehrmmupuvjzhghhemrcxpuicsd/Build/Intermediates/ArchiveIntermediates/AppName-Develop/InstallationBuildProductsLocation/Applications/AppName-Develop.app

Compiling X...

▸ Processing AppName-Develop-Info.plist
▸ Generating 'AppName-Develop.app.dSYM'
▸ Running script 'Copy Pods Resources'
▸ Running script 'Fabric Script'
▸ Touching AppName-Develop.app

❌  error: Task failed with exit 1 signal 0 {

** ARCHIVE FAILED **

The following build commands failed:
CopySwiftLibs /Users/jenkins/Library/Developer/Xcode/DerivedData/XViaMobile-hgehrmmupuvjzhghhemrcxpuicsd/Build/Intermediates/ArchiveIntermediates/AppName-Develop/InstallationBuildProductsLocation/Applications/AppName-Develop.app
(1 failure)
ERROR [2016-10-06 16:44:09.17]: Exit status: 65
INFO [2016-10-06 16:44:09.18]: EXCEPTION===> Error building the application - see the log above
INFO [2016-10-06 16:44:09.18]: -------------------
INFO [2016-10-06 16:44:09.18]: --- Step: slack ---
INFO [2016-10-06 16:44:09.18]: -------------------
INFO [2016-10-06 16:44:09.60]: Successfully sent Slack notification
WARN [2016-10-06 16:44:09.60]: Variable Dump:
INFO [2016-10-06 16:44:09.60]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios develop", :SIGH_PROFILE_TYPE=>"development", :BUILD_NUMBER=>"9471", :VERSION_NUMBER=>"3.9.3"}
ERROR [2016-10-06 16:44:09.60]: Error building the application - see the log above
INFO [2016-10-06 16:44:09.61]: Successfully generated documentation at path '/Users/jenkins/Projects/NeXgen-iOS/fastlane/README.md'

+------+---------------------------------------------------------------+-------------+
|                                  fastlane summary                                  |
+------+---------------------------------------------------------------+-------------+
| Step | Action                                                        | Time (in s) |
+------+---------------------------------------------------------------+-------------+
| 1    | update_fastlane                                               | 3           |
| 2    | default_platform                                              | 0           |
| 3    | unlock_keychain                                               | 0           |
| 4    | ensure_git_branch                                             | 0           |
| 5    | git merge origin/beta                                         | 0           |
| 6    | git push origin develop                                       | 0           |
| 7    | cocoapods                                                     | 32          |
| 8    | git commit -am 'Updating Pods.xcodeproj after running pod ins | 0           |
| 9    | match                                                         | 474         |
| 10   | increment_build_number                                        | 1           |
| 11   | commit_version_bump                                           | 0           |
| 12   | git push origin develop                                       | 2           |
| 13   | get_version_number                                            | 0           |
| 14   | get_build_number                                              | 0           |
| 💥    | gym                                                           | 177         |
| 16   | slack                                                         | 0           |
+------+---------------------------------------------------------------+-------------+

ERROR [2016-10-06 16:44:09.62]: fastlane finished with errors
bundler: failed to load command: fastlane (/Users/jenkins/.rvm/gems/ruby-2.2.4/bin/fastlane)
FastlaneCore::Interface::FastlaneError: [!] Error building the application - see the log above
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/interface.rb:145:in `user_error!'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/gym-1.11.0/lib/gym/error_handler.rb:53:in `handle_build_error'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/gym-1.11.0/lib/gym/runner.rb:101:in `block in build_app'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane_core-0.52.1/lib/fastlane_core/command_executor.rb:88:in `call'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane_core-0.52.1/lib/fastlane_core/command_executor.rb:88:in `execute'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/gym-1.11.0/lib/gym/runner.rb:97:in `build_app'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/gym-1.11.0/lib/gym/runner.rb:12:in `run'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/gym-1.11.0/lib/gym/manager.rb:10:in `work'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/actions/gym.rb:24:in `run'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/runner.rb:202:in `block (2 levels) in execute_action'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/runner.rb:187:in `block in execute_action'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/runner.rb:186:in `chdir'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/runner.rb:186:in `execute_action'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/runner.rb:112:in `trigger_action_by_name'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/fast_file.rb:140:in `method_missing'
  FastUtils:60:in `build_and_deploy_crashlytics'
  Fastfile:76:in `block (2 levels) in parsing_binding'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/lane.rb:33:in `call'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/lane.rb:33:in `call'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/runner.rb:49:in `block in execute'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/runner.rb:45:in `chdir'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/runner.rb:45:in `execute'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/command_line_handler.rb:30:in `handle'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/commands_generator.rb:49:in `block (2 levels) in run'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/commands_generator.rb:244:in `run'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/commands_generator.rb:20:in `start'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/gems/fastlane-1.105.0/bin/fastlane:5:in `<top (required)>'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/bin/fastlane:23:in `load'
  /Users/jenkins/.rvm/gems/ruby-2.2.4/bin/fastlane:23:in `<top (required)>'

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
# Automatically update fastlane if a new version is available
update_fastlane

# fastlane_version "1.37.0"
default_platform :ios

platform :ios do
  before_all do
    ENV["CRASHLYTICS_FRAMEWORK_PATH"] = "Crashlytics.framework"
    ENV["CRASHLYTICS_API_TOKEN"] = "82273c62c87520b6a519f4f18a0386960e7c4196"
    ENV["CRASHLYTICS_BUILD_SECRET"] = "fe335ee450b2551aa10676ad2237a3919a854eee0c68e6025f8ad1c86029e124"
    ENV["SLACK_URL"] = "https://hooks.slack.com/services/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"
    ENV["SNAPSHOT_FORCE_DELETE"] = "true"
    unlock_keychain(path: "login.keychain", password: "Xvia80202")
  end

  desc "Submit a new `develop` Debug IPA to Crashlytics"
  lane :develop do
    ensure_git_branch(branch: 'develop')

    # Merge latest beta into develop and push
    merge_and_push("beta", "develop")

    # Ensure Sandbox file is in sync with Podfile.lock and commit to develop
    cocoapods_and_commit

    update_submodules_and_commit(['NeXgen-Design', 'NeXgen-RulesEngine'])

    # Sync and ensure correct provisioning profiles are used for Gym
    match(type: "development", app_identifier: "*", keychain_name: keychain_name, readonly: true)

    # Push changes to remote and then send archive to Crashlytics
    build_and_deploy_crashlytics(
      "develop",
      "AppName-Develop",
      "Debug",
      "development",
      "develop-ios",
      "https://betas.to/V77xHsqV",
      nil
    )
  end

def keychain_name
  mm=`sw_vers -productVersion | awk -F '.' '{print $2}'`
  if mm.to_i < 12
    "login.keychain"
  else
    "login.keychain-db"
  end
end

def build_and_deploy_crashlytics(lane, scheme, configuration, export_method, crashlytics_group, crashlytics_share_url, provisioning_profile_path)
  # We dont want to issue a push to GitHub for an Enterprise deploy
  if lane != "enterpriserelease"
      increment_version_and_push(true, lane)
  end

  version_verbose, build_number = get_version_information

  gym(
      scheme: scheme,
      configuration: configuration,
      export_method: export_method,
  )
  end

Environment
fastlane version (run fastlane -v): 1.105.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? Yes
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? RVM

Following up, I was able to successfully code sign, archive in Xcode and distribute using Crashlytics local app using the same project and build settings logged in as my default user, not my Jenkins user.

Bumping this conversation, @KrauseFx any more discoveries on the gym/Sierra keychain issues after the one fix you made last week? Seems like there have been a few other related Issues reported (seems like more are starting to adopt Sierra, damn Apple for having to change more security with every major macOS release!).
If there is absolutely anything I can do to provide more details on my specific scenario, please let me know. I am happy to also try anything on a local version of fastlane if you could point me in a general direction.
Thank you!

So everything is working as expected, only when being called from Jenkins it doesn't work? Have you followed the installation section of Jenkins? https://docs.fastlane.tools/best-practices/continuous-integration/#jenkins-integration

Ahh, I will give setup_jenkins a try and keep you posted on my mileage, @KrauseFx - thank you for that suggestion. We were previously doing everything under the same setup and I believe some of the more recent security changes probably make setup_jenkins more of a necessity.
Should hear back from me in 24 hours!

Awesome 👍

Things are starting to look better, @KrauseFx!
Here's the output from setup_jenkins:
[16:51:58]: --- Step: setup_jenkins ---
[16:51:58]: ---------------------------

+-----------------------------+-----------------+
|       Summary for Setup Jenkins Action        |
+-----------------------------+-----------------+
| force                       | false           |
| unlock_keychain             | true            |
| add_keychain_to_search_list | replace         |
| set_default_keychain        | true            |
| set_code_signing_identity   | true            |
| output_directory            | ./output        |
| derived_data_path           | ./derivedData   |
| result_bundle               | true            |
+-----------------------------+-----------------+

[16:51:58]: Set output directory path to: "/Users/jenkins/.jenkins/workspace/iOS_Develop_Tests/output".
[16:51:58]: Set derived data path to: "/Users/jenkins/.jenkins/workspace/iOS_Develop_Tests/derivedData".
[16:51:58]: Set result bundle.

Now compilation is successful! But we get to:
▸ Linking TrackVia-Develop
⚠  ld: directory not found for option '-L/Users/jenkins/.jenkins/workspace/iOS_Develop_Tests/build/Debug-iphoneos'

Not sure if that's concerning?
It appears now I just have an issue accessing the iOS Simulator on the system, per the following logs:
2016-10-10 16:53:11.555 xcodebuild[28536:248839] [MT] iOSSimulator: Could not launch simulator: -10810
xcodebuild: error: Failed to build workspace <WorkspaceName> with scheme <AppName>-Develop.
Reason: The operation couldn’t be completed. (OSStatus error -10810.)

It seems now I just need to assure Jenkins is configured to run as an Agent, not a Daemon, so I can launch GUI applications like the iOS Simulator, and then hopefully just assuring the Jenkins user can access toe simulator?
Let me know if you've seen any errors like the above, otherwise I will keep trucking ahead!
For what it's worth, I intend on writing a blog post about Fastlane, Jenkins, Xcode 8/iOS 10, etc. as I think it would be very beneficial for other iOS developers who are big on CI to follow a guide that isn't 3 years old (most Jenkins walkthroughs). :)
Thanks again, Felix!

How did you install Jenkins? Make sure it's running in the user's context

@KrauseFx Sorry for going dark, I wanted to make sure I had tried everything before I came back up for air and reported back.
TL;DR: Updating Fastlane, Jenkins, macOS X Sierra + Xcode 8 upgrade at the same time caused a lot of problems. I learned a lot about everything that changed in each dependency, and intend on writing a blog post for other iOS developers to follow when looking to use a Jenkins + Fastlane stack for CI.
JENKINS
Felix, your suggestion to dig deeper into the Jenkins install was my main problem. I stumbled across the setup_jenkins action, which was exactly what we needed to configure the environment + Jenkins workspace to play nice with Jenkins running as a LaunchAgent in a user context versus a LaunchDaemon in a headless/detached process. We now run setup_jenkins at the beginning of each job (love that it detects Jenkins user automatically, nice work there) and all is setup correctly for our CI job to execute the various fastlane lanes we've defined.
We generally found this post to be the most helpful, but we intend to write a new blog post specific to the iOS CI stack.
FASTLANE
Using fastlane through RVM and calling bundle exec fastlane X has made integration easier for my entire team, as well simplified our integration with Jenkins.
Update all of your fastlane gems! Unlike other 3rd party dependencies, we always feel safe fetching the latest and greatest fastlane gems.
Update your match command to leverage the new match options. For instance, our development match now looks like:
match(type: "development", app_identifier: "*", readonly: readonly, force_for_new_devices: true, force: true)
OSX SIERRA/Xcode 8
Keychain and security changes causing problems yet again. Also with the Xcode 8 updates, match was not syncing with the existing certs and causing a new cert to be created for each developer versus using the already created cert for the first time running match after a fresh nuke.
To make Xcode happy with the changes we had recently made to coordinate with new fastlane + match, The solution for us was:

Close Xcode
Open Keychain Access > Select your login keychain > Select Certificates in the side menu
Look for any certificates that start with "iPhone Developer", "iPhone Distribution", or have the word "CompanyName" in them
Delete all of these certificates
(Optional) You can also delete any certificates in your keychain that have expired or been revoked.
(Optional) Make sure you don't have any expired/revoked WWDR certificates installed. You can even delete all WWDRs and install a new one fresh to be sure.

All in all, I hope to use all of this knowledge to prepare a more thorough writeup of the end-to-end setup process of provisioning a new machine for iOS continuous integration with all of these tools, mostly so our team has it for reference for future machine provisioning and hopefully help others to setup this very powerful workflow!
Thanks again, @KrauseFx for all your hard work at making such an awesome suite of life improving and smile-generating tools!

Hey @trackvia-ios, thank you so much for publishing this comment, this will be extremely helpful for other users when they search for the same issue. Publishing a blog post sounds like a great idea. I'm sure a ton of people search for setup fastlane on Jenkins and similar. Also, if you feel like our Jenkins guide is lacking some information, we'd love to receive a pull request fixing it 👍
Thanks for all your help  🚀


Return better error info when no servers instances can be found in mu…

This PR changes the error when there are no available servers for worker assignment.
The new message is:
[
  {
    "message": "ServerInstanceMissingError:\nFailed to find enabled fully replicated server for table: <tableName>, partition: <i> in table: <tableName>",
    "errorCode": 715
  }
]

Where <tableName> and <i> are substituted with the specific values

Note that this image is directly showing tableName and i but in real cases these values will be changed
Without this PR, the error show was something like
[
  {
    "message": "SQLParsingError:\nError composing query plan for: <query>;\norg.apache.pinot.query.QueryEnvironment.planQuery(QueryEnvironment.java:182)\norg.apache.pinot.broker.requesthandler.MultiStageBrokerRequestHandler.handleRequest(MultiStageBrokerRequestHandler.java:137)\norg.apache.pinot.broker.requesthandler.BaseBrokerRequestHandler.handleRequest(BaseBrokerRequestHandler.java:263)\norg.apache.pinot.broker.requesthandler.BrokerRequestHandler.handleRequest(BrokerRequestHandler.java:48)\nFailed to find enabled fully replicated server for table: <tableName>, partition: <i> in table: %s\nai.startree.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:802)\norg.apache.pinot.query.routing.WorkerManager.assignWorkersToPartitionedLeafFragment(WorkerManager.java:231)\norg.apache.pinot.query.routing.WorkerManager.assignWorkersToLeafFragment(WorkerManager.java:119)\norg.apache.pinot.query.routing.WorkerManager.assignWorkersToNonRootFragment(WorkerManager.java:85)\n",
    "errorCode": 150
  }
]

In order to correctly react to this error, I've modified the code a bit to throw ProcessingException as soon as we find the issue and just rethrow from the stack. I'm not sure if this is the most correct solution. It seems that ProcessingException is coupled with the wire protocol, so maybe we would prefer to use a protocol generic exception in this case, but I didn't want to create a very large PR.
IMHO the current way to propagate the exceptions relays too much on generic runtime exceptions (like IllegalArgumentException, IllegalStateException or RuntimeException itself), which makes it very difficult to know whether we can send the error message to the user (like in this case) or whether we need to wrap the exception and therefore associate a generic (and possible incorrect, like in this case) error code.
Feel free to suggest other alternatives.
cc: @xiangfu0 @Jackie-Jiang

Codecov Report

Merging #11440 (d34467d) into master (d91e5db) will decrease coverage by 0.13%.
The diff coverage is 25.92%.

@@             Coverage Diff              @@
##             master   #11440      +/-   ##
============================================
- Coverage     62.98%   62.85%   -0.13%
+ Complexity     1107     1105       -2
============================================
  Files          2303     2303
  Lines        124041   124062      +21
  Branches      18895    18896       +1
============================================
- Hits          78133    77985     -148
- Misses        40353    40510     +157
- Partials       5555     5567      +12

Flag
Coverage Δ

integration
<0.01% <0.00%> (ø)

integration1
<0.01% <0.00%> (ø)

integration2
0.00% <0.00%> (ø)

java-11
14.47% <11.11%> (-48.50%)
:arrow_down:

java-17
62.85% <25.92%> (+<0.01%)
:arrow_up:

java-20
14.47% <11.11%> (-48.38%)
:arrow_down:

temurin
62.85% <25.92%> (-0.13%)
:arrow_down:

unittests
62.85% <25.92%> (-0.13%)
:arrow_down:

unittests1
67.31% <20.00%> (-0.21%)
:arrow_down:

unittests2
14.49% <11.11%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

...t/query/planner/physical/PinotDispatchPlanner.java
83.33% <ø> (ø)

.../org/apache/pinot/query/routing/WorkerManager.java
67.53% <0.00%> (-1.29%)
:arrow_down:

.../java/org/apache/pinot/query/QueryEnvironment.java
87.60% <20.00%> (-3.00%)
:arrow_down:

.../apache/pinot/common/exception/QueryException.java
88.11% <33.33%> (-5.43%)
:arrow_down:

...requesthandler/MultiStageBrokerRequestHandler.java
23.30% <42.85%> (-0.73%)
:arrow_down:

... and 26 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@Jackie-Jiang I don't understand how do you propose to make the message more crisp. How do you know, in pinot-MultiStageBrokerRequestHandler (or QueryEnvironment) the actual error reason? The only way I think we have is to parse the message of the exception (looking for something that starts with Failed to find enabled fully replicated server for table:), which seems like a very bad idea. Is there something I'm missing?
Remember that we don't just want to change the error message, we also want to provide a more specific error code. In my example we return 715 instead of the generic 150.
Do you propose to include the exception trace or not?

@Jackie-Jiang I don't understand how do you propose to make the message more crisp. How do you know, in pinot-MultiStageBrokerRequestHandler (or QueryEnvironment) the actual error reason? The only way I think we have is to parse the message of the exception (looking for something that starts with Failed to find enabled fully replicated server for table:), which seems like a very bad idea. Is there something I'm missing?
Remember that we don't just want to change the error message, we also want to provide a more specific error code. In my example we return 715 instead of the generic 150.
Do you propose to include the exception trace or not?

We can include the exception trace because that is very useful debugging info when user run into issues. For this specific error, the most confusing part is the error type because the actual exception has nothing to do with query parsing (the query syntax is completely legit). IMO separating query parsing error and planning error is good enough for now.
Basically I'm okay if it returns something like:
[
  {
    "message": "QueryPlanningError:\nError planning query plan\norg.apache.pinot.broker.requesthandler.MultiStageBrokerRequestHandler.handleRequest(MultiStageBrokerRequestHandler.java:137)\norg.apache.pinot.broker.requesthandler.BaseBrokerRequestHandler.handleRequest(BaseBrokerRequestHandler.java:263)\norg.apache.pinot.broker.requesthandler.BrokerRequestHandler.handleRequest(BrokerRequestHandler.java:48)\nFailed to find enabled fully replicated server for table: <tableName>, partition: <i> in table: %s\nai.startree.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:802)\norg.apache.pinot.query.routing.WorkerManager.assignWorkersToPartitionedLeafFragment(WorkerManager.java:231)\norg.apache.pinot.query.routing.WorkerManager.assignWorkersToLeafFragment(WorkerManager.java:119)\norg.apache.pinot.query.routing.WorkerManager.assignWorkersToNonRootFragment(WorkerManager.java:85)\n",
    "errorCode": 150
  }
]

I've changed the whole code to follow the approach suggested by @Jackie-Jiang. IMHO this is worse, but given that no one else has spoken, I guess it is not an important matter

There is one more issue in MultiStageEngineIntegrationTest.

This is the diff:
diff --git a/pinot-integration-tests/src/test/java/org/apache/pinot/integration/tests/MultiStageEngineIntegrationTest.java b/pinot-integration-tests/src/test/java/org/apache/pinot/integration/tests/MultiStageEngineIntegrationTest.java
index f6a2345a62..4dba3d888f 100644
--- a/pinot-integration-tests/src/test/java/org/apache/pinot/integration/tests/MultiStageEngineIntegrationTest.java
+++ b/pinot-integration-tests/src/test/java/org/apache/pinot/integration/tests/MultiStageEngineIntegrationTest.java
@@ -450,7 +450,8 @@ public class MultiStageEngineIntegrationTest extends BaseClusterIntegrationTestS
     // invalid argument
     sqlQuery = "SELECT toBase64('hello!') FROM mytable";
     response = postQuery(sqlQuery);
-    assertTrue(response.get("exceptions").get(0).get("message").toString().contains("SQLParsingError"));
+    assertTrue(
+        response.get("exceptions").get(0).get("message").toString().contains("value hello! does not match type class"));

     // invalid argument
     sqlQuery = "SELECT fromBase64('hello!') FROM mytable";

I've changed that test to use error codes, which is better (mainly because in case of failure we actually get the actual value)


bot will not join chat

each time i try and run the runbot.bat it gives me the same error every time i have followed the instructions word for word about 3 times now to try and fix the issue even deleting and re installing python an""d git just to be 100% sure they werent the issue yet each time i get this error
""Traceback (most recent call last):
File "run.py", line 162, in main
from musicbot import MusicBot
File "C:\Users\Admin\MusicBot\musicbot_init_.py", line 1, in
from .bot import MusicBot
File "C:\Users\Admin\MusicBot\musicbot\bot.py", line 7, in
import aiohttp
ValueError: source code string cannot contain null bytes""
i know it is not the files either as my friend has the bot and it is running but he gave me his files on a usb and i changed the option.ini file yet the same error and i am unaware of what to do to get this bot working i am currently running windows 10 if that has anything to do with it (as he runs windows 7)

What Python version are you using? MusicBot requires Python 3.5.

that is currently what im running is python 3.5 64 bit

as mentioned i deleted python and git from my computer and redownloaded it twice just to be sure it wasnt a issue with python

(issue is resolved thanks to peach the issue was caused by a issue with pip i beleive deleted that along with python redownloaded it ran the update_deps.bat then ran the runbot.bat and works fine thank you everyone who helped


Team Benefits

Make "Team benefits" section.
Put into landing, because I think we don't need a separate page for team: "Just put into landing"

DOne


MINOR: Update log condition in JassContext.loadServerContext method

@rajinisivaram  currently we are adding SASL_JAAS_CONFIG to KafkaConfig. SASL_JAAS_CONFIG key always will be there in configs. updated the condition to check for value.

@omkreddy Thanks for the PR. Can you add an unit test?

@omkreddy Thanks for the PR. Since it is a trivial change, I will merge to trunk and 1.1, we can add a test later.


jetracer

Hi all,
i build me a jetracer and all notebooks are running, but i have several questions

when i turn on the car, the speedcontroller is bibing all the time
is their a webinterface to drive the car or only with the hardware controller
any assembling or training video available

thx for your help
Alexander

bibing is solved


[feature] Enable Go Builder to create GitHub Release as a prerelease

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently, Go Builder (builder_go_slsa3.yml) doesn't support creating GitHub Release as a prerelease.
When we publish a prerelease, we have to create GitHub Release once and change it as a prerelease.
It's undesirable.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Add an input prerelease to Reusable workflow to support creating GitHub Release as a prerelase.
If this input is true, GitHub Release is created as a prerelease.
This input is false by default, so the default behaviour isn't changed.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I have no idea.
BTW, GoReleaser supports auto.
  # If set to auto, will mark the release as not ready for production
  # in case there is an indicator for this in the tag e.g. v1.0.0-rc1
  # If set to true, will mark the release as not ready for production.
  # Default is false.
  prerelease: auto

This feature is useful. But Go Builder uses softprops/action-gh-release and this action supports only boolean. So it is difficult to support auto.
If we consider supporting auto in future, the type of prerelease should be string rather than boolean to keep the compatibility.
Additional context
Add any other context or screenshots about the feature request here.

Completed in the PR above, thanks!

Reopen to track

[ ] add 1 e2e test
[ ] Update the documentation
[ ] Add a changelog entry

Test successful at https://github.com/slsa-framework/example-package/releases/tag/v34.0.1 !


Banner on Official Website is not changed

Blue banner about Bootstrap 4 on Main Page still pointing to the post with Alpha 2 instead of Alpha 3.

I think this is a duplicate of #20407

Yup! Duplicate.


Apply/Receive PD/PPD Profile Verification  (Part 1)

Description of Task

Revise UX/UI for the 'Apply for PD/PPD' on Student Profile;
Revise UX/UI for the Ministry and Institution view of Student Profile
Allow Ministry to manually change the student's PD/PPD profile status

Context:

Automatic PD/PPD validation with ATBC is not critical for a PT-release. Scale of new PD/PPD applications is small, so can be handled via manual data input into SIMS instead of automatic integration with ATBC.
All related topics are covered in DIFFERENT tickets:
- How SIMS PD/PPD profile status maps into IER / ECE files
- How student can Request a Change on their PD/PPD status
Expiry date and effective dates are NOT applicable in SIMS for MVP release

Acceptance Criteria
Student PD/PPD Profile Application

[ ] Revise the wording on the student's ‘Apply for PD status’ profile button to read: “Apply for PD / PPD Status” Private Zenhub Image
[ ] Revise the wording on the ‘Apply for PD status’ profile modal header to read: “TBD soon” Private Zenhub Image
[ ] Hide the ‘apply now’ button from the modal, so that the modal is for information purposes only (The 'apply now' button and resulting functionality will be re-introduced later when ATBC integration is finalized, but for now, the PD/PPD application process will be conducted entirely outside of SIMS.)_
[ ] Revise the student profile disability status ‘tooltip’ to read: "TBD soon”  (See photo) Private Zenhub Image

Revise PD/PPD Application Wording

[ ] Revise the PD/PPD application question and options (on FT and PT) to read:
"TBD soon"
[ ] Revise the PD/PPD application question banner message (on FT and PT) to read: "TBD soon"

Introduce new PD/PPD Statuses

[ ] Create new PD/PPD Profile ‘status’ options:
Not Requested (this is already the default)
Requested (this will not automatically be assigned, this is manual input by the Ministry as well)
Approved for Permanent Disability
Approved for Persistent or Prolonged Disability
[ ] Allow Ministry staff to view current PD/PPD Profile status within the Ministry view of Student Profile, and to use a dropdown menu to change the status at any time. See photo [Private Zenhub Image]
(https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBNy85QVE9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--e143b222713dc44562a0f1777ff295fdc81e9b1f/image.png)
[ ] Anytime Ministry staff change the PD/PPD status, require a note to be provided. Note gets added to the Notes section of the student account.
[ ] Anytime a Ministry staff change a status to 'Approved for PD' or 'Approved for PPD', log the date that this action was taken within the database as 'Effective Date' (Doesn't need to be reflected in UI for now)
[ ] Display the Student Disability Status on the Student Account Profile, and the Institution view of the Student Profile and the Ministry view of the Student Profile.
[ ] Create a aest role in keycloak for ministry user to update the disability status of a student. And also update the aest keycloak role spreadsheet

Added AC

[ ] Create a aest role in keycloak for ministry user to update the disability status of a student. And also update the aest keycloak role spreadsheet

Removed (Hold off for now) from second AC as per discussion with @HRAGANBC

Note: Ministry role student-update-disability-status added to aest-business-administrators group


How is captioning labeled for Lumina-T2I models?

We use mixture-of-captioner to label images.

We use mixture-of-captioner to label images.

do you use an LLM to caption images?

We use mixture-of-captioner to label images.

do you use an VLM to caption images for natural language prompts for T2I?


Add global so that unbound.conf gets written

to the correct place based on $g setting.

The stuff generated by unbound_statistics() goes into unbound.conf
It had got separated out and was going nowhere. This 2nd commit puts the behavior back the way it was yesterday.
Note: There is a separate issue about unbound_statistics() because the UI has no place to actually select the statistics settings. There is some upgrade code that looks like it was converting statistics settings from the old Unbound package into custom commands in the integrated Unbound. So it looks like the unbound_statistics() function can/should be removed???

Frankly I'd want to statistics checkbox back. The thing is fairly noisy and cannot be controlled in any way now.


Update LICENSE to MIT

@crkos Hey man are you okay with this change? Thanks.

@daniel31x13 Looks good!


add support for coupled-reaction bounds

Closes #20
Completely prospectively (and accordingly to the ConstraintTree practice and FAIR model assembly), I also added the possibility to actually identify and name the couplings.

Codecov Report
Attention: Patch coverage is 85.96491% with 8 lines in your changes missing coverage. Please review.

Project coverage is 96.41%. Comparing base (1e3147b) to head (8841e8e).

Files
Patch %
Lines

src/accessors.jl
0.00%
8 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##            master      #22      +/-   ##
===========================================
- Coverage   100.00%   96.41%   -3.59%
===========================================
  Files            6        6
  Lines          220      279      +59
===========================================
+ Hits           220      269      +49
- Misses           0       10      +10

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


IP-433 Stats Credentials

Update the buildpack so

[x] The generated pgbouncer.ini file includes a stats_users username
[x] the generated users.txt file includes the MD5 hash of the stats user's password
[ ]  an environmental variable is defined so the agent can connect to pgbouncer with the appropriate user and password for the 'pgbouncer' database (similar to the DATABASE_URL_PGBOUNCER variable it currently creates)

New ENV params,

PGBOUNCER_STATS_USER
PGBOUNCER_STATS_PASSWORD

read in jira ...

I will close this PR as well, because we want to keep the changes in the "with_datadog_integration" branch
(https://github.com/deliveroo/heroku-buildpack-pgbouncer/compare/master...deliveroo:with_datadog_integration)


Revert "nodejs-16_x: 16.5.0 -> 16.6.0"

Node.js 16.6.0 fails to build on Darwin
Fixes https://github.com/NixOS/nixpkgs/issues/132533
This reverts commit f5de4158dd462c51741ec48be2e47a3f8015930d.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Thank you for this!
I'm tempted to just merge this, I don't know if you want to get the feedback of more people.

I don't like this as this is a critical security release.

Could we use the older version only on darwin?

https://nodejs.org/en/blog/vulnerability/july-2021-security-releases-2/
Unfortunately it doesn't seem like patches are available and no minor release either

I would be fine with adding that patch.

Result of nixpkgs-review pr 132656 at c73d1006 run on x86_64-linux 1

2 packages skipped due to time constraints:

lumo
nodejs-16_x (nodejs_latest)

1 package built successfully:

nodejs-slim-16_x (nodejs-slim_latest)

1 suggestion:

warning: name-and-version
Did you mean to pass pname instead of name to mkDerivation?
Near pkgs/development/web/nodejs/nodejs.nix:48:5:
   |
48 |     name = "${baseName}-${version}";
   |     ^

Near pkgs/development/web/nodejs/nodejs.nix:46:12:
   |
46 |     inherit version;
   |            ^


Combining Shapes

The original Joy library supports the + operator to join shapes. This gives the ability to easily create shapes like a donut and combine transformed shapes as well.
I'd like to work on this combination to create other compound shapes.

@Sudha247 @nikochiko @AryanGodara Do I have the approval to work on this or should I close the issue?

@nangahamandine this is being worked on in #56
Are you suggesting something different?

Oh I just realized now that the complex shapes method will apply to the combined shapes I was suggesting.
Can I close this then?


API for managing Teams and Users

Tell us about your request
Our organisation (& others I imagine ) would like to keep with the new subscription plans, however managing users for any of the lower tiers is going to be a nightmare if its is add/remove one by one.
Another option might be to enable SAML for the Team plan? Our org does not require any of the features of the Business plan but would be nice to have some way to programmatically add users upto 250 users.
Which service(s) is this request for?
Docker for Desktop
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Managing 250 user licenses is not going to be a pleasant experience and would be nice to have a programatic API to do this. SAML is great but the price for a Business user cannot really be justified.
Are you currently working around the issue?
None available

SAML doesn't provision users, are you thinking more of SCIM for user provisioning

I feel with you, no API, no SAML auth. How docker thinks they can justify forcing people to buy subscription if they do not even provider proper tooling to manage users....

I agree. This capability is sorely needed.

There seems to be public API endpoints for this. I found this by adding myself and removing myself from my org, using + for an additional email, eg<EMAIL_ADDRESS>then running dev tools in chrome.
I'm not sure if this is publicly documented anywhere, so these endpoints could change easily. The only thing I found so far is this: https://docs.docker.com/docker-hub/api/latest/. The naming seems pretty consistent, but since I used my dev tools vs. documentation I wouldn't expect these to last forever.
Here's what I've found:
Add users:
Method: POST
https://hub.docker.com/v2/orgs/{orgName}/groups/{groupName}/members which accepts '{"member": "{email}"}' as the payload.
Get invitees here:
Method: GET
https://hub.docker.com/v2/orgs/{orgName}/invitees/
Resend invite
Method POST
<EMAIL_ADDRESS>Delete invitees:
Method: DELETE
https://hub.docker.com/v2/orgs/{orgName}/invitees/?email={email}
Delete users:
Method: DELETE
Note: Both methods remove a user from an organization
Via group member endpoint
https://hub.docker.com/v2/orgs/{orgName}/groups/{groupName}/members/{dockerUserName}/
Via org member endpoint
https://hub.docker.com/v2/orgs/{orgName}/members/{dockerUserName}/
Example setup:
!#/bin/bash
UNAME=""
UPASS=""
ORG=""
DefaultGroup=""
TOKEN=$(curl -s -H "Content-Type: application/json" -X POST -d '{"username": "'${UNAME}'", "password": "'${UPASS}'"}' https://hub.docker.com/v2/users/login/ | jq -r .token)

json='{"member": "'$userEmail'"}'
curl -X POST -d "$json" -H 'Content-Type: application/json' -H "Authorization: JWT ${TOKEN}" https://hub.docker.com/v2/orgs/$ORG/groups/$DefaultGroup/members/

special thanks: https://gist.github.com/kizbitz/175be06d0fbbb39bc9bfa6c0cb0d4721
Note:
Some of these must of course be url-encoded, so<EMAIL_ADDRESS>wouldn't work, but https://hub.docker.com/v2/orgs/{orgName}/{groupName}/invitees/?email=email%40example.com should

Hello, we are currently in the process of validating this feature and I'm interested in learning more about your use-cases. If you want to drop me a line at<EMAIL_ADDRESS>I'm happy to jump on a call. @joshuafernandes

Hi @nunocoracao,
Our main need is being able to export the full list of members of the organisation to see who has access and regular audit processes. Currently having to email support for this .csv export is not ideal.
Thanks.

Hello @josh-higgs, thanks for your feedback. We are tracking the export users as a separate feature on https://github.com/docker/roadmap/issues/401 if you want to follow progress there.

Is there a status update on development of this feature? I'm being tasked with evaluating a migration to DockerHub for my company, and it's beginning to look like there is no support outside of the (beta?) SCIM feature for SSO, which is only capable of provisioning and deprovisioning, for:

API based management of users - either accessing lists of current users for audit purposes, adding new users, removing existing.
Any management of "Teams" - creating, removing, changing permissions, or modifying membership

With the net result looking like a great deal of manual work is needed to support a business of significant size.

We are looking for APIs to grant/revoke access to users/teams. And I can't put enough emphasis on how much these APIs are very critical for using DockerHub at scale in automated way. As whenever our automation adds a new repo, someone has to manually goto DockerHub web app and grant access to different teams/users.
I see its open for more than a year and considering it's in investigation stage right now, can someone give me best case scenario and most likely scenario timelines for these APIs to be available in Production.

@MercedesSteele (and maybe @nunocoracao) I am in the same situation as @raj-patel1 . We would need for example an API call to set specific permissions ("Read & Write") to a team for a given private repository (that we could create with the current API).
As a reference, ChatGPT suggested the following ;)

Get the team id from the team name

curl -s -H "Authorization: JWT <ACCESS_TOKEN>" https://hub.docker.com/v2/orgs/<DOCKERHUB_ORG>/teams/ | jq -r '.teams[] | select(.name == "<TEAM_NAME>") | .id'

Add write permissions for the team with that id

curl -s -H "Authorization: JWT <ACCESS_TOKEN>" -H "Content-Type: application/json" -X PUT -d '{"name": "<TEAM_NAME>", "permission": "write"}' https://hub.docker.com/v2/repositories/<DOCKERHUB_ORG>/<REPO_NAME>/team/$(echo -n "<TEAM_ID>" | base64)/

The /invitees endpoint doesn't seem to be there? Managing team memberships works, as does removing users from an org, but I still don't see a way to programmatically send an invitation to join an org.

"Add users" seems to be now  the endpoint https://hub.docker.com/v2/invites/bulk with the payload:
{
  "org": "<YOUR_ORG>",
  "team": "",
  "invitees"<EMAIL_ADDRESS>  "dry_run": false,
  "role": "member"
}


[recorder] Support Vitest/Mocha both

Packages impacted by this PR

@azure-tools/test-recorder

Issues associated with this PR
Describe the problem that is addressed by this PR
Migrates the @azure-tools/test-recorder to tshy and ESM to support both vitest and Mocha
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

Closing in favor of https://github.com/Azure/azure-sdk-for-js/pull/28667


Do we have any plans to add members APIs?

I was interested in adding the members to a running cluster using using the library. Do, we have any plans to do so? https://coreos.com/etcd/docs/latest/v2/members_api.html#add-a-member

https://github.com/jplana/python-etcd/pull/219

I am not working on this as I honestly think etcdctl is enough for such actions, but if the current PR gets amended, I'm happy to merge it.

Duplicate of #218


Move to govuk-react org

e.g. for improved CI options

Deploy preview for affectionate-nobel-f3a8ec processing.
Built with commit d9c52c6f9e026545c77fd60a20dd4d94e7c6fe80
https://app.netlify.com/sites/affectionate-nobel-f3a8ec/deploys/5bf6a41e40e2a417e190c701

Codecov Report

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

@@           Coverage Diff           @@
##           master     #479   +/-   ##
=======================================
  Coverage   99.73%   99.73%
=======================================
  Files          80       80
  Lines         381      381
  Branches       15       15
=======================================
  Hits          380      380
  Misses          1        1

Impacted Files
Coverage Δ

components/layout/src/index.js
100% <ø> (ø)
:arrow_up:

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 44c6eac...d9c52c6. Read the comment docs.

Really good idea, nice one!


Create option to switch server

In the admin (and maybe reseller?) level we need to create a option/value to define the used server. Defaults to live (api-01), but we should be able to overwrite this.

Where should we store the value for this option? Shall we use the plugin.conf (which DirectAdmin uses mainly) or create an own .conf file?

I'm not a fan of overwriting files saved in github and not defined in .gitignore (because of the "own work" when pulling updates using git). I'm not sure what we should use for this tho, I think the best option is to use the plugin.conf, yeah..

I am sorry, I lost track with "I'm not a fan of overwriting files saved in github and not defined in .gitignore". What do you mean?

Let's use the plugin.conf

Also see 196f2a0c000420381c5608c67972f7bf21ea33ba

Hmm, yeah, maybe not a "live=yes", but more a "acmeServer=https://acme-v01.api.letsencrypt.org/"? On this way sysadmins should also be able to define other servers (this is only for advanced users, since by default it should be the live one of Lets Encrypt)

Yes, let's define the acmeServer in the plugin.conf and add a feature in the plugin with following options:

Live (sets the server you provided in your comment)
Test (sets the test server)
Custom (sets a server that the admin provides)

Do you agree with this? This way we have an user friendly option but it can also be used for advanced users.

Hmm,  awesome. Let's do that.


os/mac: Remove mention of Mavericks bottles

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

After Issue #985 was merged, bottles for Mavericks are no longer
being built, meaning installations on 10.9 are triggering builds.
This PR updates the FAQ to show that builds will most likely now be
triggered on Mavericks since their bottles are not being generated
and hosted on bintray.

Looks good, just one thought so this doesn't get outdated in future.

Cool, made the change to keep the language more generic.

Perfect, thanks!


Automatically playing music on website

Please don't do this.

Completely unexpected and undesired behavior!
It also makes the website unusable for mobile usage, unless you like the idea of annoying people all around the poor sob scrambling to find out why his phone is blasting out music.

Not sure I understand. Are you on right repository? The app has nothing to do with playing a music..

https://advancedrestclient.com/ is playing music.

To be exact: The following video file which automatically plays when visiting the website mentioned above includes very loud music: https://advancedrestclient.com/images/hero-video.mp4

Hmmm. The video is muted on the website and should not be played. Can you actually hear the music?

Yes, I can confirm the audio playing on both Firefox Mobile on Android 49.0 and Firefox for Windows 48.0.2.
I recommend simply removing the unnecessary audio track from the file itself.

Definitely I'll do this.
Thanks for the issue report.

This is fixed now.
You need to clear cache first.


Check app version before upgrading a Cask

Provide a detailed description of the proposed feature
Basically a lot of apps have an integrated auto-update feature, like Chrome and many more. But when the app is installed from Homebrew, an update may be installed twice, once through the app itself (assuming the auto-update has not been disabled) and another time through brew (assuming it's ran often enough).
Homebrew currently doesn't (seem to?) check the app's version and seems to act based on the last version the app has been installed from brew in.
What I suggest is brew upgrade --cask to check for the current app's version (easily done by using mdls -raw -name kMDItemVersion /Applications/<App>.app) instead of sometimes reinstalling the same version.
What is the motivation for the feature?
Avoiding installing an update that has already been performed, and greatly increase compatibility with such apps featuring auto-update. Some apps also don't really like to be completely uninstalled and reinstalled, and often in that case a complete setup has to be performed again, which can be painful.
Another step on this feature might be to warn and avoid updating apps when auto-update is enabled in them so Homebrew stops managing their versions entirely.
How will the feature be relevant to at least 90% of Homebrew users?
It will let the user decide, avoid going through setup at each update for some, and shorten the brew --upgrade time.
What alternatives to the feature have been considered?
Manually disabling every auto-update feature (if applicable) on all apps installed from Homebrew.

There is an auto_updates stanza (see Cask Cookbook) which can be added to casks to indicate they are handled in-app and should not be upgraded by brew. brew will only upgrade casks without that stanza set, unless you pass --greedy when running brew --upgrade. If you're found any casks you use that autoupdate, but are still being upgraded by brew, please feel free to open PR's adding the auto_updates stanza.


Use Action instead of Action in generic overloads

This allows customisation of bundle-specific properties.

Which issue is the resubmit? It was never linked up.

Haha, oops. I guess I never resubmitted this 😕  I don't think I ended up needing it. Sorry!


adding the greengenes2 naive bayes classifier

Dear , @proteinosome  and @fripp
Would it ber possible to upgrade qiime2 to the latest version (2024.5 as I write) and add greengenes2 (q2-greengenes2 and accompanying classifier database) as an alternative source to classify full length 16S sequences. Greengenes2 relies on full length assemblies and is likely becoming soon a new standard for 16S V1V9 and is being actively developped (https://forum.qiime2.org/t/introducing-greengenes2-2022-10/25291).
Newer versions of the current databases may also be relevant and are linked at https://resources.qiime2.org/
A proper guide on what to change to implement this would already be great value.
Thanks in advance
Stephane

@splaisan I'll look into this in the next few weeks. Unfortunately I can't promise a solid timeline here, but I'll make sure to get to this as soon as I can.

I'm putting this on-hold for now due to the need for further investigation into the sanity of using GG2 database. Please see discussions here: https://github.com/benjjneb/dada2/issues/1680#issuecomment-1724495374

This is now added in a dev branch v0.9 https://github.com/PacificBiosciences/HiFi-16S-workflow/blob/v0.9_dev/CHANGELOG.md
@splaisan the default naive-bayes assignment priority now follows GG2 > GTDB > Silva and single-assignment of any particular databases can also be found in the output folder. Single database assignment using VSEARCH uses GG2 by default, too. If you could test and let me know if there's any issue it'll be great! The nextflow config file has now changed quite a bit so please use the new config file, too. Samples and manifest files format remain unchanged so it should be a straightforward update pipeline --> Replace nextflow.config --> run with the same samples manifest
It's in dev branch because I have not extensively tested it and benchmarked it, but as far as I can tell it runs pretty well and in a few cases  the Naive-Bayes classifier with GG performs really well. I'll close this for now please open new issue if you bump into any.


Implement operator source minting API endpoint

Based on O1's open infrastructure/operations managed services framework for leveraging the collective technical expertise and insights of project communities worldwide, there is an interesting idea surrounding converting automation/Infrastructure-as-code solutions (such as community developed Ansible roles) into NFTs which not only track ownership, contributions to and usage of these solutions but also incentivize development and promote the recognition/awareness of the value they provide.
To contribute towards this idea/effort, it makes sense to experiment with different ways in which these IaC solutions can be tokenized. To start, one thought is to create a collage of the source of these solutions which dynamically updates based on modifications made. The operator service seems like a decent place to initially support this functionality and should expose an endpoint which takes a role url and returns an image representing a collage of its source.

Prior to creating the source code collage, all files need to be converted into a supported image file by PIL. Follow the steps below to handle the conversion:

Install ImageMagick
update ImageMagick policy to allow for read|write of all file types


Remove Ethernet from Windows 10

Per the NetAdapter team at Microsoft, Ethernet is not officially supported in 2.0 for Windows 10.  The APIs required to use it were only in the "preview" version included in WDK 10.0.19041 and those APIs changed in the next release.

Thanks for catching this @grimbeaver!


Roll engine ff1bcdc00941..377dc6400329 (2 commits)

https://github.com/flutter/engine/compare/ff1bcdc00941...377dc6400329
git log ff1bcdc00941188ba27123a4857b443e3c9392bb..377dc6400329fc48cb30b07d0a929d3405f2ee20 --no-merges --oneline
377dc6400 Roll src/third_party/dart 86b5304ccd..8e0a669e74 (6 commits)
7ee3a31c5 Roll src/third_party/dart 907c514c89..86b5304ccd (27 commits)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (jsimmons@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5843460920705024

Commit queue failed; closing this roll.

Commit queue failed; closing this roll.


fix eval when using subset host loading data

b/371572923
Tested on v4-128: https://cloudlogging.app.goo.gl/YqjMDsc27SxXHSLaA

Hi, @aireenmei
Awesome and thank you for the fix!
Do we expect to unblock eval_per_device_batch_size < 1. with this PR?
And do you happen to have some test results?

@ZhiyuLi-goog It should support eval_per_device_batch_size < 1. But let me actually run the tests to make sure. Will get back to you.

@khatwanimohit @ZhiyuLi-goog
I made more chnages. Now it supports eval_per_device_batch_size < 1. Could both of you review again?
Cases tested on v4-128:

M_EXPANSION_FACTOR_REAL_DATA=2, per_device_batch_size=per_eval_device_batch_size=8.0
https://console.cloud.google.com/kubernetes/service/us-central2/v4-128-bodaborg-us-central2-b/default/aireen-20241011-12-10/details?project=cloud-tpu-multipod-dev
per_device_batch_size=eval_per_device_batch_size=0.5 ici_tensor_parallelism=4, expansion_factor=-1: https://console.cloud.google.com/kubernetes/service/us-central2/v4-128-bodaborg-us-central2-b/default/aireen-20241010-18-28/details?project=cloud-tpu-multipod-dev
per_device_batch_size=1.0 eval_per_device_batch_size=0.5, ici_tensor_parallelism=4, expansion_factor=-1: https://console.cloud.google.com/kubernetes/service/us-central2/v4-128-bodaborg-us-central2-b/default/aireen-20241010-19-02/details?project=cloud-tpu-multipod-dev
per_device_batch_size=0.5 eval_per_device_batch_size=1, ici_tensor_parallelism=4, expansion_factor=-1:  https://console.cloud.google.com/kubernetes/service/us-central2/v4-128-bodaborg-us-central2-b/default/aireen-20241010-18-36/details?project=cloud-tpu-multipod-dev

@khatwanimohit @ZhiyuLi-goog I made more chnages. Now it supports eval_per_device_batch_size < 1. Could both of you review again?
Cases tested on v4-128:

M_EXPANSION_FACTOR_REAL_DATA=2, per_device_batch_size=per_eval_device_batch_size=8.0
https://console.cloud.google.com/kubernetes/service/us-central2/v4-128-bodaborg-us-central2-b/default/aireen-20241011-12-10/details?project=cloud-tpu-multipod-dev
per_device_batch_size=eval_per_device_batch_size=0.5 ici_tensor_parallelism=4, expansion_factor=-1: https://console.cloud.google.com/kubernetes/service/us-central2/v4-128-bodaborg-us-central2-b/default/aireen-20241010-18-28/details?project=cloud-tpu-multipod-dev
per_device_batch_size=1.0 eval_per_device_batch_size=0.5, ici_tensor_parallelism=4, expansion_factor=-1: https://console.cloud.google.com/kubernetes/service/us-central2/v4-128-bodaborg-us-central2-b/default/aireen-20241010-19-02/details?project=cloud-tpu-multipod-dev
per_device_batch_size=0.5 eval_per_device_batch_size=1, ici_tensor_parallelism=4, expansion_factor=-1:  https://console.cloud.google.com/kubernetes/service/us-central2/v4-128-bodaborg-us-central2-b/default/aireen-20241010-18-36/details?project=cloud-tpu-multipod-dev

Thank you @aireenmei for those experiments!
Look great to me!

@ZhiyuLi-goog I reliazed _tfds_data_processing_c4_mlperf.py also needs update. Please review my latest push^.


Merge pull request #1 from quantopian/master

nothing

Coverage remained the same at 86.978% when pulling 022d826ec5b02b9055733e40491c05352bca7598 on shaotao527:master into e7ca08038a6c3f83e36e8c2b67d719a58b329de5 on quantopian:master.

As advertised, looks like there's "nothing" in this PR!  Closing, but feel free to add some commits and re-open.


error w/ ember-cli

I've been experiencing this issue on a basic unit test while I'm transition to Ember-CLI
TypeError: Cannot read property 'forEach' of undefined
at Object.forEach (http://localhost:4200/assets/vendor.js:27244:17)
at __exports__.default.Ember.Mixin.create.buildRuleValidator (http://localhost:4200/assets/vendor.js:76983:35)
at __exports__.default.Ember.Mixin.create.buildValidators (http://localhost:4200/assets/vendor.js:76949:18)
at __exports__.default.Ember.Mixin.create.init (http://localhost:4200/assets/vendor.js:76931:14)
at apply (http://localhost:4200/assets/vendor.js:32883:32)
at superWrapper [as init] (http://localhost:4200/assets/vendor.js:32457:15)
at apply (http://localhost:4200/assets/vendor.js:32883:32)
at new Class (http://localhost:4200/assets/vendor.js:47483:9)
at Function.Mixin.create.create (http://localhost:4200/assets/vendor.js:47941:16)
at Ember.Object.extend.buildRecord (http://localhost:4200/assets/vendor.js:75309:27)

This is my bower.json:
{
"name": "jobs-tuftsdaily",
"dependencies": {
"handlebars": "~1.3.0",
"jquery": "^1.11.1",
"ember": "1.8.1",
"ember-data": "1.0.0-beta.12",
"ember-resolver": "~0.1.11",
"loader.js": "ember-cli/loader.js#1.0.1",
"ember-cli-shims": "ember-cli/ember-cli-shims#0.0.3",
"ember-cli-test-loader": "rwjblue/ember-cli-test-loader#0.0.4",
"ember-load-initializers": "ember-cli/ember-load-initializers#0.0.2",
"ember-qunit": "0.1.8",
"ember-qunit-notifications": "0.0.4",
"qunit": "~1.15.0",
"bootstrap": "~3.3.1"
  }
}

This is the failing test:
test('it exists', function() {
  var model = this.subject();
  // var store = this.store();
  ok(!!model);
});

This is typically the result of updating from an older version of ember-cli. Can you try:
rm -rf node_modules && npm cache clear && npm install

Yes, I think that was it as this error has since gone away. Thanks!


Request additional sources

Hi there, would it be possible to add the following sources as repositories to https://github.com/Ultimate-Hosts-Blacklist?
dbl.oisd.nl related issue

https://dbl.oisd.nl (main)
https://dblmobile.oisd.nl (mobile edition)

MoaAB (i.e. Mother of all adblocking)

https://adblock.mahakala.is/ (main)

These lists contain some useful domains to block, but they're bloated with inactive domains, so a CI + PyFunceble sorting and filtering them out will be useful.
Thanks!

We've just dropped mahakala after it being here for a long time because it just has too many false positives. The other team members can have a look inclusion of oisd.nl

Hi @DRSDavidSoft
At first eye sight I don't see any differ from other list.
So where is it you think these list add to existing lists?

@DRSDavidSoft  where is this list coming from? Does it have a repo in GitHub so we can see how well is curated?
Also we'll wait for @funilrys to test it against all the lists present here to check the number of unique domains and we'll go from there.

The MoaAB (adblock.mahakala.is) homepage is actually on the XDA forums here. I don't believe that they use any sort of CVS (let alone git), but aside from the ridiculous amount of false positives, they're kind of a mostly reputable project. (Besides Energized and 1Hosts projects, which are also XDA-oriented projects).
I agree that the number of false positives for MoaAB list is a lot, but I would still appreciate a CI running PyFunceble on it to detect ACTIVE domains, so that I can cross-reference it with the other sources in my list.

@DRSDavidSoft  i was asking about dbl.oisd.nl.
adblock.mahakala.is was removed and ain't no coming back anytime soon.

@dnmTX, oh, I see.
It's worth mentioning that the author has a zero false positive policy and takes this matter very seriously.

This blocklist contains well over 1 million entries, but still you should not have to whitelist things, it's thát good.
It's my goal for this list to be as perfect as possible, so you shouldn't find any :D

What they explaine is that they avoid including any sources that may produce a false positive:

I maintain a separate list (which I call the "skipifcontains"-list. In here I listed domains that should never be blocked. Eg; google.com, facebook.com, amazon.com, microsoft.com, netflix.com, etc)
If a downloaded list contains any one of those listed, then I run the list though a regex loop to only capture the domains that make sense to be blocked, but the rest of the list contents will be skipped.

When I asked him for their sources on Reddit, he linked to only some of them, which is here: https://credits.oisd.nl that's why I'm eager to see what other sources he use.

That's one massive list of credits :scream_cat:  I can almost guarantee you there is no way a list like that can be properly maintained and not contain false positives. Several of my own projects included there but just a quick look through reveals a number of other lists which have been dropped over the years due to not being maintained and containing to many FP's. There's also a lot of duplication due to the projects included there which are already projects made up of unified lists.

@mitchellkrogza This is true, and I agree with you on your points! While that list is extensive (and may contain many redundant entries that serve no purpose to many of the users), it usually contains the bare minimum FPs, and generally doesn't block anything other than what they have advertised to block.
I say this because I maintain a list of whitelist sources (in addition to my list of blacklist sources :3) and whenever I add a new blacklist to my list, I always cross-reference them for any potential FPs, to see if it'll break anything useful in the future. So far, MoaAB seems to contains the most FPs while the oisd list contains the least FPs between any of the aggregated lists that I use.
With that being said, I respect the decision to omit including oisd and/or MoaAB in your repo; it was just a request to see if they'd be accepted here 😄  as I already use the other, more useful lists from your repos.
As for duplicates issues, BTW, I believe it's the user's responsibility to check for and remove any duplicates that might be there, when combining lists from different sources. I know I do, and there are many tools available to do just that for users.

RIGHT ON @mitchellkrogza 🚀

Well, If so a CI + PyFunceble sorting and filtering them out will be useful is the only requirement. It's a good idea I didn't delete it yet from @dead-hosts.
I pinged @mitchellkrogza out there (@dead-hosts ==> dev-center) for the case that he needed help for the setup and configuration of PyFunceble in his very own machine.
In between, we just tested 100000 domains in about 2 hours with my (dev version) changes in the last hours. So let's see what happens with that huge list inside @dead-hosts.
I think everybody will agree, with my decision to close this.
Let me know if some clarification or others are needed.
Cheers,
Nissar


ENT-8224: Added sshd-MaxAuthTries-4 v0.0.1

Superseded by: https://github.com/cfengine/build-index/pull/127


docker network rm docker network ls -q

You cannot do
docker network rm `docker network ls -q`

because docker network rm only takes one argument.
IT would be nice the change this behaviour to be like rm and rmi

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

#17489 implements this

@thanks.


[Feature Request] Linking to Entries

It would be nice to have a way to link any entry (Creature, NPC or Hazard) to a text editor, just as one would link other journals, actors, items, etc. Clicking on the link would open the bestiary tracker directly on the linked entry.
This would be very helpful for cross-referencing between journals and the bestiary tracker.

I just released v1.0.3 that adds this feature 🤖 👌

Button adds the link to your clipboard so you can paste it in the same way you work with sheets.


Is it possible to generate the AUTHORITY of the ContentProvider using App pageName

I want to use the contentProvider in variant package. So the AUTHORITY should be different with each other. Is it possible?
I want something like that:
<provider android:authorities="${applicationId}" />
``
@ContentProvider(
authority = CompulsoryBase.AUTHORITY,
database = CompulsoryBase.class,
baseContentUri = CompulsoryBase.BASE_CONTENT_URI)
@Database(name = CompulsoryBase.NAME, version = CompulsoryBase.VERSION)
public class CompulsoryBase {
public static final String NAME = "CompulsoryLearning";
public static final int VERSION = 1;

public static final String AUTHORITY = ******;//which should be same with packageName, for example: context.getPackageName(), but the annonation value should be constant, what can I do?

public static final String BASE_CONTENT_URI = "content://";

}
``

create a BuildConfigField object that creates the value for you in the BuildConfig class.


kbr-2dzip_f2c150ac

Add content:

[UT3 MAP] KBR-Anubis
[UT3 MAP] KBR-Flarized
[UT3 MAP] KBR-TwinTombs
[UT3 MAP] VKBR-Sandstorm
[UT3 MAP] KBR-IceFields
[UT3 MAP] KBR-2D
[UT3 MAP] KBR-Apophis
[UT3 MAP] KBR-BombingHoops
[UT3 MAP] KBR-Skyline
[UT3 MAP] KBR-Thorns
[UT3 MAP] KBR-RoundAbout

Submission log: https://unrealarchive.org/submit/#f2c150ac

Those maps are going to need a new separate gamemode section in UT3 maps catalogue. Unlike Classic Domination and just Domination in UT3, Kilter's Bombing Run and regular Bombing Run are very different gamemodes with their own map pools. I'm going to quote author of KBR himself:

KilterBR is just what I’m calling my version of Bombing Run for UT3. Unlike the already existing Bombing Run mod, this one is faithful to the 2k4 version. It’s a direct port, only tweaked to work with the new engine. All your favorites are still there, the goals, the ball, and even the ball launcher.

Here's mod's page on ModDB for reference, here's the official KBR website, here's the regular UT3 Bombing Run mod and here's one KBR map on Unreal Archive, that were uploaded earlier, it should be moved to the new section.

Thanks. Captured the gametype: https://unrealarchive.org/gametypes/unreal-tournament-3/K/kilters-bombing-run/index.html
Merging this, and will then update the maps to match.


Mean Episode Reward and Length showing NaN in PPO2 training.

Hello,
First of all I would like to thank you for this is incredibly polished package. Seeing good documentation just makes me feel happy.
While training PPO2 on Pong-ram-v0 (and several other envs) I realized that the episode reward doesn't print correctly to the console.  It is seen as follows:

I tried looking into it but couldn't figure out why just yet. If you give me some pointers I would like to work on fixing it.
I am using python 3.6.5 on an Ubuntu 16.04.

Thank you! This is definitely good enough to get me started.
I will look into it when I have the time, should be within a weeks time.

I managed to get the average reward over multiple environments, however I am having some difficulty getting the episode length.
From what I can tell, there is no easy way of getting the length of every episode?
I worked on taking the difference between "true"s in the masks, however, for that to work I need to know what the maximum episode length (which I assume isn't available?) to handle the overflows which I think is different than n (The number of steps between the last "true" in mask[i] and the first "true" in mask[i+1] is another episode.) My abomination of an implementations currently seems to work if the length of the max_episode is less than 2 * n_steps.
That being said, I am almost sure I am over-complicating things and there is just a nice variable for episode length, somewhere.

Looking at the code again, I found that there was an EpisodeStats class in a2c utils (https://github.com/hill-a/stable-baselines/blob/master/stable_baselines/a2c/utils.py#L428) that apparently can do the job.
It is used in ACER only. @hill-a it seems that this class can be reused, no?
Otherwise, I recommend you taking a look at the new vec env monitor (only in openai baselines for now: https://github.com/openai/baselines/blob/master/baselines/common/vec_env/vec_monitor.py)
@batu looking at your code, using the max episode length won't work as some environments does not have limits.

@batu How are you doing?

I have a semi-working implementation, however, it is definitely not clean enough. When my current work hump passes I will go back to it and when I stop making silly mistakes submit a PR

Hi,
maybe I misunderstand the resolution of this, but for the life of me I still can't get the average episode length for an A2C model. Can someone clarify how I can see eplenmean? Or is it only for PPO2 models?

if you read the first answer, you need to use a Monitor wrapper, this will done automatically if you use the rl zoo.

@hill-a
How is the episode-reward  calculated in tenorsboard?  Is that calculated as same as you tell (you would just need to create a list of the episode rewards, accumulate said rewards, and return average rewards + average episode length)?


NewRelic's deploy notification can only be configured with an API_KEY in plain text

Nowadays, in order to configure a deploy notification to NewRelic, an API_KEY must be stored in plain text in a project's tsuru-bluegreen.ini.
It doesn't seem to be a good practice... What if this could be done with environment variables?
I have a PR for implementing this, if you find it useful.

Link for the Pull Request: https://github.com/emerleite/tsuru-bluegreen/pull/32
☝


Clean and refactor

Codecov Report

Merging #175 into code-refactoring will decrease coverage by 0.45%.
The diff coverage is 99.19%.

@@                 Coverage Diff                 @@
##           code-refactoring    #175      +/-   ##
===================================================
- Coverage             97.56%   97.1%   -0.46%
===================================================
  Files                    58      58
  Lines                  2175    2175
===================================================
- Hits                   2122    2112      -10
- Misses                   53      63      +10

Impacted Files
Coverage Δ

cli-commands/compiler/compiler.js
100% <100%> (ø)
:arrow_up:

cli-commands/compiler/etherlime-resolver/epm.js
100% <100%> (ø)
:arrow_up:

...mands/compiler/etherlime-contract-sources/index.js
100% <100%> (ø)
:arrow_up:

cli-commands/compiler/etherlime-resolver/fs.js
100% <100%> (ø)
:arrow_up:

...i-commands/debugger/etherlime-debug-utils/index.js
100% <100%> (ø)
:arrow_up:

cli-commands/compiler/etherlime-error/index.js
100% <100%> (ø)
:arrow_up:

cli-commands/compiler/etherlime-expect/index.js
100% <100%> (ø)
:arrow_up:

cli-commands/debugger/repl.js
100% <100%> (ø)
:arrow_up:

...mmands/compiler/etherlime-contract-schema/index.js
100% <100%> (ø)
:arrow_up:

cli-commands/compiler/etherlime-resolver/npm.js
100% <100%> (ø)
:arrow_up:

... and 5 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 de340fe...ba40209. Read the comment docs.


Unable to make this work from Mac/Chrome

Finally got to implement this in the live environment. The module connects and gives no errors. When I send a button command nothing happens.
If I add a TCP-UDP connection and connect I can manually send a command like MT00SW0202NT with /r/n but the module doesn't seem to send the commands properly? Any thought? I will try the debug session from my dev machine when I'm next on site.
My thoughts so far is that the variable is getting mashed in the string build? or the send?

Same here on Mac OS. There is also no message in the log (also not in the debug section of the log).

@jrvviz can you look at this?

The current code is creating and destroying the socket for every command . There is a timing and scope hazard here I think as the asynchronous function may not have access to the command variable
Get Outlook for iOShttps://aka.ms/o0ukef

From: Joseph Adams @.>
Sent: Monday, August 1, 2022 10:14:33 PM
To: bitfocus/companion-module-tesmart-hdmimatrix @.>
Cc: James Rankin @.>; Mention @.>
Subject: Re: [bitfocus/companion-module-tesmart-hdmimatrix] Unable to make this work from Mac/Chrome (Issue #4)
@jrvizhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjrviz&data=05|01||2300267d7382475c345b08da7402d6f4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637949852784454287|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=PpGJGJwFhldn4BrVNdnr1wrKqzUbDuryZXj4nTd4Kp8%3D&reserved=0 can you look at this?
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbitfocus%2Fcompanion-module-tesmart-hdmimatrix%2Fissues%2F4%23issuecomment-1201728118&data=05|01||2300267d7382475c345b08da7402d6f4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637949852784454287|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=QHrsS60XIM8r83vDHm9BGGeRP1KgMsm8nStOTKO61Q4%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACWBY4YNA6JTE4VE45JGLPTVXA43TANCNFSM5XGWQW4Q&data=05|01||2300267d7382475c345b08da7402d6f4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637949852784454287|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=FEv4rToLm1JqaLQAaSuBourD24GW4a5r%2FzKo8B4v%2FHE%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

So this should be fixed in #5

There are a number of new config option in this release so if you have this module loaded you should open config, set up your configuration and save.


[Bug]: View echo tags don't work in normal HTML attributs

Tempest Version
1.0-alpha.3
PHP Version
8.3
Operating System
MacOS
Description
<div class="{{ $class ?? '' }}

Steps to Reproduce
/

Wouldn't it be better to just do the following in this case ?

In Vue 3, they deprecated interpolation within attributes, and I believe part of it was to reduce confusion.

That's a good consideration. What you describe is already possible 🤔
It might just be a matter of documenting then that <div class="{{ $class ?? '' }} isn't allowed

Also, it makes more sense if we say that anything between those quotes should be valid PHP.

That's already implelented, both <?=, <?php, {{, and {!!` aren't allowed in expression attributes