Deliver fails promoting app to review, possible missing field

New Issue Checklist

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

Issue Description

We have a lane that takes care of uploading metadata/screenshots/build and promoting directly to review. Although all fields are correct, the lane fails with this issue:
The provided entity is missing a required attribute - You must provide a value for the attribute 'usesNonExemptEncryption' with this request

This is the redacted lane declaration:
deliver(
    platform: "ios",
    app_identifier: bundleId,
    languages: ["it"],
    team_id: teamId,
    team_name: teamName,
    app_version: version,
    run_precheck_before_submit: false,
    force: true,
    ipa: "builds/#{bundleId}/#{xcodeTarget}-app-store.ipa",
    skip_metadata: true,
    skip_screenshots: true,
    metadata_path: "metadata/#{bundleId}",
    screenshots_path: "screenshots/#{bundleId}",
    submission_information: {
      add_id_info_uses_idfa: false,
      export_compliance_uses_encryption: true,
      export_compliance_is_exempt: true
    },
    submit_for_review: true,
    automatic_release: true,
  )

I have tried the following things:

Splitting the different uploads (screens, metadata, etc) but the same error persists
Removing and rebuilding the release, no luck
Setting all values explicitly for the submission info, no luck

I have close to no knowledge of ruby, but looking at this file it seems to me that the field usesNonExemptEncryption is never mapped to the payload, therefore missing from the actual request.
Could anyone confirm?
Command executed

bundle exec fastlane store_distribution_lane

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

 [15:16:37]: ---------------------------------------------
[15:16:37]: --- Step: Switch to _distribute_lane lane ---
[15:16:37]: ---------------------------------------------
[15:16:37]: Cruising over to lane '_distribute_lane' 🚖
[15:16:37]: ----------------------------------------------------------
[15:16:37]: --- Step: Switch to _obtain_app_store_connect_key lane ---
[15:16:37]: ----------------------------------------------------------
[15:16:37]: Cruising over to lane '_obtain_app_store_connect_key' 🚖
[15:16:38]: Login Status Code: 200
[15:16:38]: Downloading 1c4a079a-d160-4877-860e-a982ed3361b7 to ./connect-api-key-file-APP_NAME.p8
[15:16:38]: URL: https://api.client-manager.loopalty.ch/static/1c4a079a-d160-4877-860e-a982ed3361b7
[15:16:38]: Finished downloading 1c4a079a-d160-4877-860e-a982ed3361b7 to ./connect-api-key-file-APP_NAME.p8
[15:16:38]: ---------------------------------------
[15:16:38]: --- Step: app_store_connect_api_key ---
[15:16:38]: ---------------------------------------
[15:16:38]: Cruising back to lane '_distribute_lane' 🚘
[15:16:38]: Downloading previous metadata...might take a white
[15:16:38]: -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[15:16:38]: --- Step: bundle exec fastlane deliver download_metadata -m metadata/BUNDLE_ID -u 'USERNAME' -a 'BUNDLE_ID' --api_key_path 'fastlane/IDENTIFIER.json' --languages 'it' ---
[15:16:38]: -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[15:16:38]: $ bundle exec fastlane deliver download_metadata -m metadata/BUNDLE_ID -u 'USERNAME' -a 'BUNDLE_ID' --api_key_path 'fastlane/IDENTIFIER.json' --languages 'it'
[15:16:41]: ▸ [15:16:41]: Creating authorization token for App Store Connect API
[15:16:42]: ▸ +--------------------------------------+-------------------------------+
[15:16:42]: ▸ |                       deliver 2.205.2 Summary                        |
[15:16:42]: ▸ +--------------------------------------+-------------------------------+
[15:16:42]: ▸ | metadata_path                        | metadata/BUNDLE_ID |
[15:16:42]: ▸ | username                             | USERNAME         |
[15:16:42]: ▸ | app_identifier                       | BUNDLE_ID          |
[15:16:42]: ▸ | api_key_path                         | fastlane/IDENTIFIER.json        |
[15:16:42]: ▸ | languages                            | ["it"]                        |
[15:16:42]: ▸ | screenshots_path                     | ./fastlane/screenshots        |
[15:16:42]: ▸ | platform                             | ios                           |
[15:16:42]: ▸ | edit_live                            | false                         |
[15:16:42]: ▸ | use_live_version                     | false                         |
[15:16:42]: ▸ | skip_binary_upload                   | false                         |
[15:16:42]: ▸ | skip_screenshots                     | false                         |
[15:16:42]: ▸ | skip_metadata                        | false                         |
[15:16:42]: ▸ | skip_app_version_update              | false                         |
[15:16:42]: ▸ | force                                | false                         |
[15:16:42]: ▸ | overwrite_screenshots                | false                         |
[15:16:42]: ▸ | sync_screenshots                     | false                         |
[15:16:42]: ▸ | submit_for_review                    | false                         |
[15:16:42]: ▸ | reject_if_possible                   | false                         |
[15:16:42]: ▸ | phased_release                       | false                         |
[15:16:42]: ▸ | reset_ratings                        | false                         |
[15:16:42]: ▸ | run_precheck_before_submit           | true                          |
[15:16:42]: ▸ | precheck_default_rule_level          | warn                          |
[15:16:42]: ▸ | ignore_language_directory_validation | false                         |
[15:16:42]: ▸ | precheck_include_in_app_purchases    | true                          |
[15:16:42]: ▸ +--------------------------------------+-------------------------------+
[15:16:46]: ▸ [15:16:46]: Writing to 'metadata/BUNDLE_ID/it/name.txt'
[15:16:46]: ▸ [15:16:46]: Writing to 'metadata/BUNDLE_ID/it/subtitle.txt'
[15:16:46]: ▸ [15:16:46]: Writing to 'metadata/BUNDLE_ID/it/privacy_url.txt'
[15:16:46]: ▸ [15:16:46]: Writing to 'metadata/BUNDLE_ID/it/apple_tv_privacy_policy.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/it/description.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/it/keywords.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/it/release_notes.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/it/support_url.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/it/marketing_url.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/it/promotional_text.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/primary_category.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/secondary_category.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/primary_first_sub_category.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/primary_second_sub_category.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/secondary_first_sub_category.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/secondary_second_sub_category.txt'
[15:16:48]: ▸ [15:16:48]: Writing to 'metadata/BUNDLE_ID/copyright.txt'
[15:16:49]: ▸ [15:16:49]: Writing to 'metadata/BUNDLE_ID/review_information/first_name.txt'
[15:16:49]: ▸ [15:16:49]: Writing to 'metadata/BUNDLE_ID/review_information/last_name.txt'
[15:16:49]: ▸ [15:16:49]: Writing to 'metadata/BUNDLE_ID/review_information/phone_number.txt'
[15:16:49]: ▸ [15:16:49]: Writing to 'metadata/BUNDLE_ID/review_information/email_address.txt'
[15:16:49]: ▸ [15:16:49]: Writing to 'metadata/BUNDLE_ID/review_information/demo_user.txt'
[15:16:49]: ▸ [15:16:49]: Writing to 'metadata/BUNDLE_ID/review_information/demo_password.txt'
[15:16:49]: ▸ [15:16:49]: Writing to 'metadata/BUNDLE_ID/review_information/notes.txt'
[15:16:49]: --------------------------------
[15:16:49]: --- Step: rm ./IDENTIFIER.json ---
[15:16:49]: --------------------------------
[15:16:49]: $ rm ./IDENTIFIER.json
[15:16:49]: ---------------------
[15:16:49]: --- Step: deliver ---
[15:16:49]: ---------------------
[15:16:49]: Creating authorization token for App Store Connect API
+----------------------------------------------------------+----------------------------------------------------+
|                                            deliver 2.205.2 Summary                                            |
+----------------------------------------------------------+----------------------------------------------------+
| platform                                                 | ios                                                |
| app_identifier                                           | BUNDLE_ID                               |
| languages                                                | ["it"]                                             |
| team_id                                                  | TEAM_ID                                         |
| team_name                                                | COMPANY                                      |
| app_version                                              | 1.7                                                |
| run_precheck_before_submit                               | false                                              |
| force                                                    | true                                               |
| ipa                                                      | builds/BUNDLE_ID/IDENTIFIER-app-store.ipa |
| skip_metadata                                            | true                                               |
| skip_screenshots                                         | true                                               |
| metadata_path                                            | metadata/BUNDLE_ID                      |
| screenshots_path                                         | screenshots/BUNDLE_ID                   |
| submission_information.add_id_info_uses_idfa             | false                                              |
| submission_information.export_compliance_uses_encryption | true                                               |
| submission_information.export_compliance_is_exempt       | true                                               |
| submit_for_review                                        | true                                               |
| automatic_release                                        | true                                               |
| api_key                                                  | ********                                           |
| edit_live                                                | false                                              |
| use_live_version                                         | false                                              |
| skip_binary_upload                                       | false                                              |
| skip_app_version_update                                  | false                                              |
| overwrite_screenshots                                    | false                                              |
| sync_screenshots                                         | false                                              |
| reject_if_possible                                       | false                                              |
| phased_release                                           | false                                              |
| reset_ratings                                            | false                                              |
| precheck_default_rule_level                              | warn                                               |
| ignore_language_directory_validation                     | false                                              |
| precheck_include_in_app_purchases                        | true                                               |
+----------------------------------------------------------+----------------------------------------------------+
[15:16:50]: Making sure the latest version on App Store Connect matches '1.7'...
[15:16:51]: '1.7' is the latest version on App Store Connect
[15:16:51]: Uploading binary to App Store Connect
[15:16:52]: Going to upload updated app to App Store Connect
[15:16:52]: This might take a few minutes. Please don't interrupt the script.
[15:21:26]: iTunes Transporter successfully finished its job
[15:21:26]: ------------------------------------------------------------------------------------------------------------------
[15:21:26]: --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
[15:21:26]: ------------------------------------------------------------------------------------------------------------------
[15:21:26]: Finished the upload to App Store Connect
[15:21:27]: Selecting the latest build...
[15:21:27]: Waiting for processing on... app_id:<PHONE_NUMBER>, app_version: 1.7, build_version: 75, platform: IOS
[15:21:29]: Read more information on why this build isn't showing up yet - https://github.com/fastlane/fastlane/issues/14997
[15:21:29]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[15:21:45]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[15:22:03]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[15:22:20]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[15:22:36]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[15:22:53]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[15:23:11]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[15:23:31]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:23:50]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:24:07]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:24:24]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:24:42]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:24:59]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:25:16]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:25:33]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:25:50]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:26:07]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:26:25]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:26:43]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:26:59]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:27:16]: Waiting for App Store Connect to finish processing the new build (1.7 - 75) for IOS
[15:27:33]: Successfully finished processing the build 1.7 - 75 for IOS
[15:27:33]: Selecting build 1.7 (75)...
[15:27:36]: Successfully selected build
[15:27:38]: Successfully updated IDFA declarations on App Store Connect
+--------------------+--------------------------------------------------------------------------------------------------------------+
|                                                           Lane Context                                                            |
+--------------------+--------------------------------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM   | ios                                                                                |
| PLATFORM_NAME      |                                                                                |
| LANE_NAME          | store_distribution_lane                                                                                |
| BUILD_NUMBER       | 75                                                                                |
| VERSION_NUMBER     | 1.7                                                                                |
| IPA_OUTPUT_PATH    | REPO_PATH/builds/BUNDLE_ID/IDENTIFIER-app-store.ipa          |
| XCODEBUILD_ARCHIVE | /Users/Lucas/Library/Developer/Xcode/Archives/2022-05-02/IDENTIFIER-app-store 2022-05-02 15.09.36.xcarchive    |
| DSYM_OUTPUT_PATH   | REPO_PATH/builds/BUNDLE_ID/IDENTIFIER-app-store.app.dSYM.zip |
+--------------------+--------------------------------------------------------------------------------------------------------------+
[15:27:42]: appStoreVersions with id 'APP_STORE_ID' is not in valid state. - This resource cannot be reviewed, please check associated errors to see why.
The provided entity is missing a required attribute - You must provide a value for the attribute 'usesNonExemptEncryption' with this request
+------+---------------------------------------------------------------+-------------+
|                                  fastlane summary                                  |
+------+---------------------------------------------------------------+-------------+
| Step | Action                                                        | Time (in s) |
+------+---------------------------------------------------------------+-------------+
| 1    | default_platform                                              | 0           |
| 2    | Switch to _build_for_appstore_lane lane                       | 0           |
| 3    | increment_build_number                                        | 2           |
| 4    | increment_version_number                                      | 2           |
| 5    | gym                                                           | 434         |
| 6    | Switch to _distribute_lane lane                               | 0           |
| 7    | Switch to _obtain_app_store_connect_key lane                  | 0           |
| 8    | app_store_connect_api_key                                     | 0           |
| 9    | bundle exec fastlane deliver download_metadata -m metadata/ch | 11          |
| 10   | rm ./IDENTIFIER.json                                            | 0           |
| 💥   | deliver                                                       | 652         |
+------+---------------------------------------------------------------+-------------+
[15:27:42]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
bundler: failed to load command: fastlane (/usr/local/bin/fastlane)
Spaceship::UnexpectedResponse: [!] appStoreVersions with id 'APP_STORE_ID' is not in valid state. - This resource cannot be reviewed, please check associated errors to see why.
The provided entity is missing a required attribute - You must provide a value for the attribute 'usesNonExemptEncryption' with this request
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/spaceship/lib/spaceship/connect_api/api_client.rb:204:in handle_response'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/spaceship/lib/spaceship/connect_api/api_client.rb:124:in post'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:1209:in post_review_submission_item'   /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in post_review_submission_item'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/spaceship/lib/spaceship/connect_api/models/review_submission.rb:69:in add_app_store_version_to_review_items'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/deliver/lib/deliver/submit_for_review.rb:49:in create_review_submission'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/deliver/lib/deliver/submit_for_review.rb:26:in submit!'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/deliver/lib/deliver/runner.rb:223:in submit_for_review'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/deliver/lib/deliver/runner.rb:65:in run'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/actions/upload_to_app_store.rb:22:in run'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:255:in block in execute_action'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:229:in chdir'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:229:in execute_action'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/fast_file.rb:159:in method_missing'   Fastfile:396:in block in parsing_binding'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/lane.rb:33:in call'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:204:in try_switch_to_lane'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:146:in trigger_action_by_name'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/fast_file.rb:159:in method_missing'
Fastfile:221:in block (2 levels) in parsing_binding'   Fastfile:215:in each'
Fastfile:215:in block in parsing_binding'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/lane.rb:33:in call'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:49:in block in execute'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:45:in chdir'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/runner.rb:45:in execute'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/commands_generator.rb:110:in block (2 levels) in run'
/Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'   /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run'
/Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in run!'
/Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/commands_generator.rb:354:in run'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/commands_generator.rb:43:in start'   /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/bin/fastlane:23:in <top (required)>'   /usr/local/bin/fastlane:23:in load'
/usr/local/bin/fastlane:23:in `<top (required)>'

Environment

 swift-driver version: 1.45.2 🚫 fastlane environment 🚫
Stack

Key
Value

OS
12.3.1

Ruby
2.6.8

Bundler?
true

Git
git version 2.32.0 (Apple Git-132)

Installation Source
/usr/local/bin/fastlane

Host
macOS 12.3.1 (21E258)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
13.3

Swift Version
5.6

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
`./Fastfile`
NOT NEEDED

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.205.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

bundler
1.17.2

etc
1.0.1

forwardable
1.2.0

rake
13.0.6

rexml
3.2.5

CFPropertyList
3.0.5

public_suffix
4.0.7

addressable
2.8.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.581.0

aws-sigv4
1.5.0

jmespath
1.6.1

aws-sdk-core
3.130.2

aws-sdk-kms
1.56.0

aws-sdk-s3
1.113.2

babosa
1.0.4

claide
1.1.0

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.4

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.3

excon
0.92.3

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.0.0

faraday-multipart
1.0.3

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.0

http-cookie
1.0.4

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

jwt
2.3.0

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.16.1

googleauth
1.1.3

httpclient
2.8.3

mini_mime
1.1.2

trailblazer-option
0.1.2

uber
0.1.0

representable
3.1.1

retriable
3.1.2

webrick
1.7.0

google-apis-core
0.4.2

google-apis-androidpublisher_v3
0.19.0

google-apis-playcustomapp_v1
0.7.0

google-apis-iamcredentials_v1
0.10.0

google-apis-storage_v1
0.13.0

google-cloud-env
1.6.0

google-cloud-errors
1.2.0

google-cloud-core
1.6.0

google-cloud-storage
1.36.2

json
2.6.1

mini_magick
4.11.0

naturally
2.2.1

optparse
0.1.1

plist
3.6.0

rubyzip
2.3.2

security
0.1.3

simctl
1.6.8

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.21.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2022-05-02

@joshdholtz I am taking the liberty to ping you as you requested in https://github.com/fastlane/fastlane/pull/16646
It looks like the change never got applied to the release version, I think these two are related
Let me know if I can provide any additional info/fix

I faced similar kind of issue last time, I am still searching for some proper solution


Ingest rate

What does this pull request do? Explain your changes. (required)
Ingest-rate: add 'sourceBytes', 'transcodedBytes', 'ingestRate' and 'outgoingRate' fields to the stream object. Scrape sourceBytes and transcodedBytes from broadcaster's /status endpoint, calculate ingest rate from that and save to the stream object.

Specific updates (required)

-

How did you test each of these updates (required)

Does this pull request close any open issues?
Fixes #239
Screenshots (optional):

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.

How often is ingest rate updated? Same for source bytes, transcoded bytes and outgoing rate? Also can you please describe what formulas you used for ingest rate and outgoing rate? I will want to include info about that in the documentation. Good work getting this done fast, @darkdarkdragon.

@wohlner

Everything updated each 2 seconds
ingest rate = (source bytes now - source bytes at previous update) / (time passed since previous scrape (should be 2 sec))
outgoing rate is same but for transcoded bytes

one more question @darkdarkdragon, in the screenshot above transcoded bytes is orders of magnitude smaller than the source bytes. Let me make sure I understand why. Source bytes is 1080p only and transcoded bytes is all the smaller transcoded renditions only, correct?

@wohlner that's because for the test I'm using OBS and streams just some rendered clock like this:

OBS produces output stream of 2.5M/s, as requested, but then transcoded it produces much less bitrate.

If I'm enabling actual video in OBS - output bitrate jumps:


Fixed numBadBoneIndices calculation in validateSkinning.

There is tiny linting issue

Fixed, let's hope it checks out now!


v2.0.0

Fixes #38
Fixes #46
2.0.0

Breaking Change: console.error instead of console.log to output error messages #55.
Added: Default value for options <files...> #46.
Added: Exclude binary files #45.
Added: Beautiful console report #53.
Added: Support for .gitignore when [<files>...] are not provided #56.
Added: Test cases for CLI #55.
Fixed: Stripping of BOMs #50.
Fixed: path import in README #48.
Upgraded dependencies.

@gucong3000 published! Thanks for all your hard work! 🎊 🏮 🎆 ㊗


knife will not communicate with chef using an internal ca signed cert

Description
knife ssl check will not communicate with chef, using an internal ca signed cert
I have tried both putting the internal ca signed cert in /var/opt/opscode/nginx/ca
I have tried the setup suggested in https://docs.chef.io/server_security.html setting the two attributes to my cert and key location in /etc/opscode/chef-server.rb
nginx['ssl_certificate_key']
nginx['ssl_certificate']
The fqdn matches the server and hostname -f.
I have done knife ssl fetch
I have manually copied in the full ca bundle to the trusted certs location
positioned as:

I have appended my intermediate, and root ca to the cacert.pem used by chefdk at:
/opt/chefdk/embedded/ssl/certs/cacert.pem
My ca_bundle is already a part of the OS trusted ca certs
I have tried adding ssl_ca_path and ssl_ca_file to my knife.rb pointing to my internal ca bundle.
I can run openssl verify with the chefdk cert, and it verifies my cert perfectly.
openssl s_client -showcerts -connect :443 verifies correctly
ChefDK Version
[root@lpawschef00 ca]# chef --version
Chef Development Kit Version: 2.0.28
chef-client version: 13.2.20
delivery version: master (17c1b0fed9be4c70f69091a6d21a4cbf0df60a23)
berks version: 6.2.0
kitchen version: 1.16.0
inspec version: 1.31.1
Platform Version
[root@lpawschef00 ca]# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
Replication Case
Create a root CA
Sign an intermediate CA with your root CA
Create and sign a certificate using your intermediate CA
Copy intermediate CA cert and key to /var/opt/opscode/nginx/ca
Stacktrace
Debug steps
knife-debug.zip
Strace file
knife-strace-sanitized.out.zip
NOTE: CHEFDK BUGS ONLY
This issue tracker is for the code contained within this repo -- chefdk.

Server issues
Chef-client issues
Cookbook Issues (see the https://github.com/chef-cookbooks repos or search Supermarket or GitHub/Google)

Try setting export SSL_CERT_FILE=/path/to/whatever.pem to point at your internal CA bundle?

Yea, I did that as well. It was part of what I tried when I appended it to the chefdk cacert. I'll attach that debug output as well. It still fails verification of the cert, but technically does allow knife to talk to chef. It's weird because it throws the same "unable to get local issuer certificate" on the trusted cert.
knife-export-debug.zip

@rfelsburg  did you ever figure this out?

Knife is actually part of the Chef project so you'll want to file this bug against the Chef repo so we can track it there. https://github.com/chef/chef.


Add support new P3 64x32 #issue119

Please add this code to the library, for support new P3 64x32, #issue119

Fixed in latest master - see comments in issue tracker


Release/0.0.2

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9feac59). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   20.61%
=========================================
  Files             ?        1
  Lines             ?      131
  Branches          ?        0
=========================================
  Hits              ?       27
  Misses            ?      104
  Partials          ?        0

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 9feac59...952a6f2. Read the comment docs.


About comparison fairness and dataset splitting

Dear Authors,
Thank you for your invaluable contributions to this repository. I am currently exploring the field of time series imputation and have encountered some aspects regarding the evaluation protocols that I believe could benefit from further discussion.

Dataset Splitting: The choice to split the dataset chronologically is well-suited for time series forecasting to prevent data leakage. However, for imputation tasks where the goal is to address the missingness in available data, such splitting may not be necessary. Given that the primary concern in imputation is dealing with inherently missing data, a non-chronological split might be more appropriate as it reflects real-world scenarios where all available data is subject to imputation, instead of the recent ones.
Evaluation Comparisons: The evaluation process raises somewhat questions about fairness and consistency across different methods. We compare for instance the Transformer and mean imputer. While the Transformer model is assessed using test data, the approach for evaluating a mean imputer remains unclear. Should the mean imputer also have access to the test data since the non-missing data in the test data should also be available in model serving? There are two options:

training the mean imputer on the train-eval set is unfair since the non-missing data in the test set should be available for the mean imputer too, which does not cause leakage and has been exploited by nn models.
training the mean imputer exclusively on the test set does not leverage the potentially informative train-eval sets, which seems equally unfair.

In view of these points, I suggest the following:

For generalized imputation methods like those in HyperImpute, should we maintain merely the unavailability of missing values in the test set while considering the rest of the data  as usable (including the non-missing values in the test data, the train and eval data)?
Could we use a non-chronological train-val-test split, given that in practical applications, the emphasis is on imputing the entire dataset rather than the recent months? More importantly, in the case of missing value imputation, the non-missing data is often unavailable (kindly see the protocol of HyperImpute for reference)

I look forward to your insights and any suggestions you might have on aligning the evaluation framework with real-world imputation tasks.
Best regards,
Hao

Hi @HowardZJU, thanks for raising the discussion here.

Splitting datasets chronologically will be necessary for all time-series modeling tasks if you want to use the model for future data. Splitting is not only a way to avoid data leakage but also to prevent overfitting (the two may stand for the same thing in some cases). In the time-series imputation field, there are two scenarios, i.e. in-sample and out-of-sample. For the in-sample case, as you've said, there is no necessity to split data chronologically. But for out-of-sample, it is vital because we need to ensure the generalization ability of the trained models. Obviously, we take the latter one in our experiments, not only because imputation generalization is important to deep learning algorithms, but also because out-of-sample imputation is commonly used in real-world applications;
In our current implementations of PyPOTS naive imputation methods, e.g. the mean imputer, they don't have the training stage. Hence, if you'd like to make them calculate empirical values on both the training set and the test set, you can merge the sets together to feed into the imputers;

You ask good questions and provide helpful insights here. We appreciate that. If you also work with POTS (partially-observed time series) data, we sincerely invite you to join our community and build PyPOTS better together ;-)


how to get the plots in html reporter

hello：
the fastp is great software for QC ,but how we can get the plots in html，because plots not saved independently，can you updated the feature to save the plots independently for each html reporter，thankyou.

hi @liwg123
fastp html report using plotly.js for curve rendering, u can when hovering on the curve, a button will be show for save image as png


Remove version: Daum.PotPlayer version 220106

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://t1.daumcdn.net/potplayer/PotPlayer/Version/220106/PotPlayerSetup64.exe
Status Code: 200
(Automated message - build 871)


Sublime dev

Resurecting: https://github.com/NixOS/nixpkgs/pull/26718

Right, sorry, fixed in 8e18b7c409600faf9b60685944a00fb1bb4f1c3f


chore: release 1.2 rc1 helm file updates

Description
What this PR does / why we need it:
release 1.2 rc1 helm file updates
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

@susanshi @binbin-li are we sure we want this PR to merge for RC? Our main quickstart points to these files. Do we want users using a non stable version?

For the actual 1.2 release, we need to update the helmfile in the dev branch.


build: linux/ppc64 builder doesn't start on boot

Back. It was running in a screen session in our KVM slice and somebody rebooted the host.

It's dead again.
bradfitz@laptop ~$ ssh<EMAIL_ADDRESS>ssh: connect to host <IP_ADDRESS> port 22: Network is unreachable
bradfitz@laptop ~$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
92 bytes from 140-211-168-57-openstack.osuosl.org (<IP_ADDRESS>): Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  20 5400 92c5   0 0000  36  01 7790 <IP_ADDRESS>  <IP_ADDRESS>


Fix HTTP OPTIONS request auth handling

Fixes #5588
This PR sets the AUTHORIZATION_CHECKED flag to true for all HTTP OPTIONS requests. This is handled in a new servlet filter (Druid has no explicit OPTIONS method handlers on its endpoints).
It seems that CORS pre-flight OPTIONS requests do not generally contain credentials headers:

https://stackoverflow.com/questions/15734031/why-does-the-preflight-options-request-of-an-authenticated-cors-request-work-in
https://fetch.spec.whatwg.org/#cors-preflight-request
https://bugzilla.mozilla.org/show_bug.cgi?id=778548

So a disableHttpOptionsAuthentication config is added to disable authentication checks on OPTIONS requests (authentication is required by default) to support CORS use cases.

I merged https://github.com/druid-io/druid/pull/5615 too early, so reopening in this PR.
This addresses the comments left on the last PR.

@jon-wei are you planning to do the backport?


Remove Node.prototype.setUserData and supporting UserDataHandler

This has not been supported in browsers for a very long time. This change removes the functionality.
See https://developer.mozilla.org/en-US/docs/Web/API/Node/setUserData

Created internal issue http://b/137762920

Importing for review and testing

Thanks


raidboss/oopsy: add EX5

Closes #5208 (because it incorporates most of it)
Co-Authored-By: ksh<EMAIL_ADDRESS>Co-Authored-By: valarnin<EMAIL_ADDRESS>

I took #5208 and @valarnin's work from discord and combined it and a few other things here.  Thank you!

I'm gonna go ahead and merge this, but feel free to leave comments if you think there's something that could be better here.  Just trying to get something in.


Add a 'serde-derive' feature

These changes add a way to have #[derive(serde::Serialize)] and #[derive(serde::Deserialize)] added to types from prost-types.
They may or may not be useful depending on the user needs, and they add a dependency, so they are gated behind a serde-derive feature.
This MR will conflict with #414 , but if you agree to merge both of them I can fix the conflicts if you want

Hi @daladim, thanks for the PR.  I agree with the motivation for this change, but unfortunately this implementation will not be able to land.  The files you have modified are auto-generated (see bootstrap.rs).  I would like to have a prost-build option that would result in the correct serde derive annotations being added to generated code.  Critical to this is that the serde format be compatible with the protobuf json serialization rules.  See #75 for the tracking issue.


community: Relax constraints on Cassandra VectorStore constructors

If Session and/or keyspace are not provided, they are resolved from cassio's context. So they are not required.

@hemidactylus

LGTM, nice work @cbornet !


Robot name

Edits based on Dan and Paul’s comments.

@athiercelin @djkotowski Really like rework. I feel this is a great refactor. There are just a couple changes I'd like you to make before closing out this exercise.


Allow Applicants to save application as a draft

Fixes #309
Added Save Draft button on all fund pages.

When the applicant clicks on the Save Draft button, submission is considered as a draft.
Following things are taken into consideration while building this feature.

The applicant can see and edit draft submission made in the dashboard.

The applicant can edit and submit a submission that becomes in_discussion aka INITIAL_STATUS

Staff cannot see draft submission made by the applicant also can't see in the submission list.

@frjo Not sure if I understood it correctly

When I as an admin/staff try to save a draft application I can not see or view it. I can edit it do. This needs a fix I believe.

Do we want the draft submissions submitted by Admin/Staff to appear in Submissions table? Currently, we do not show Admin submissions in their dashboard like Applicant under "Your active submissions". The submissions table in /apply/submissions/ exclude draft submissions. I think we should only display finally submitted applications there. For staff, if required we can add Your active submissions in their dashboard to allow them to edit their submission.

@vaibhavmule Instead of showing the following message after successful draft submission, we should ask them to complete the application later after log-in.

Thank you for your submission to the Acme Corporation.

So, in the case of draft submissions, we can show a message like

Your application is saved as a draft. Please note that it is not submitted for review. You can complete your application by following the log-in details emailed to you.

OTF can change it later based on requirements.
This template will need updates.


B #3080: Packet provision of CentOS 7 on c2.medium fails

I guess this applies to one-5.8 as well?


Cannot open menu via shortcut when activity bar is hidden

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.64.2
OS Version: 10.0.19044

Steps to Reproduce:

Set the following "window.menuBarVisibility": "compact"
Toggle the activity bar so that it is hidden (Ctrl+Shift+P then type "View: Toggle Activity BarVisibility")
Hit Alt+f

Expected behavior: file menu shows
Actual behavior: nothing happens
Same goes for any of the other menus that one would normally expect to access by using the Alt+Letter shortcut.

technically a dupe of a closed won't fix issue, but I may have a simpler idea for handling this than I previously thought. old issue #85124


[Q] Is development dead on this?  Can't find it in the RHEL8 EPEL repo

We heavily depend on python-carbon as the go-between between our monitoring system, CheckMk, and Grafana.  CheckMk writes to whisper files via carbon-cache and Grafana reads from the whisper files.
We're replacing our RHEL7 server and I cannot find the python-carbon package in the RHEL8 or 9 EPEL repos.

Hi @armada-lmt
We have never been involved in packaging Graphite, distro maintainers did that. I see python-carbon  in Fedora but not in EPEL8/9 - https://src.fedoraproject.org/rpms/python-carbon


Element components imported as node components

Hello,
I have a model containing element components (named selections).
When I import the rst file, result.geometry._elem_comps / result.geometry.element_components is empty and I find the components in result.geometry._node_comps / result.geometry.node_components.
Could you please have a look at it?
Thank you!
Francesco

Thanks for pointing this out.  The result reader was misinterpreting all the components as node components.  I've fixed this in https://github.com/akaszynski/pyansys/pull/249 and the changes are live on pypi with pyansys==0.41.6.

That was super fast. Thank you for the update!


Many randomized environments in parallel

I would like to use some form of domain randomization with brax environments. Ideally, I would like re-sample the parameters of the envs in every iteration / after every step. So far I only managed to sample random parameters and replace the default parameters in the environment XML. However, loading the 'system' from XML takes very long and makes this approach very inefficient.
Is there a clean and efficient way to change relevant physics parameters (e.g. body mass, size, friction coef, etc.) without the significant overhead of reconstructing the 'system' from scratch?

Hi @jonasrothfuss
Yes there is a way to sample multiple systems, but we have not polished/released such a thing in v2. Tracing over the System is a high-level intent of the new design of brax. One way to get your project off the ground is to create a vectorized System like so:
def _write_sys(sys, attr, val):
  """"Replaces attributes in sys with val."""
  if not attr:
    return sys
  if len(attr) == 2 and attr[0] == 'geoms':
    geoms = copy.deepcopy(sys.geoms)
    if not hasattr(val, '__iter__'):
      for i, g in enumerate(geoms):
        if not hasattr(g, attr[1]):
          continue
        geoms[i] = g.replace(**{attr[1]: val})
    else:
      sizes = [g.transform.pos.shape[0] for g in geoms]
      g_idx = 0
      for i, g in enumerate(geoms):
        if not hasattr(g, attr[1]):
          continue
        size = sizes[i]
        geoms[i] = g.replace(**{attr[1]: val[g_idx:g_idx + size].T})
        g_idx += size
    return sys.replace(geoms=geoms)
  if len(attr) == 1:
    return sys.replace(**{attr[0]: val})
  return sys.replace(**{attr[0]:
                        _write_sys(getattr(sys, attr[0]), attr[1:], val)})

def set_sys(sys, params: Dict[str, jp.ndarray]):
  """Sets params in the System."""
  for k in params.keys():
    sys = _write_sys(sys, k.split('.'), params[k])
  return sys

def randomize(sys, rng):
  return set_sys(sys, {'link.inertia.mass': sys.link.inertia.mass + jax.random.uniform(rng, shape=(sys.num_links(),))})

rng = jax.random.PRNGKey(0)
rng, *key = jax.random.split(rng, batch_size + 1)
key = jp.reshape(jp.stack(key), (batch_size, 2))
sys_v = jax.vmap(functools.partial(randomize, sys=sys))(key)

I have not fully tested the code, but the intent and rough idea should there. [1] Create a batch of rng keys, [2] randomize the system over the batch of rng keys, [3] use the vectorized system sys_v to do stuff
We're planning to get a wrapper that does this for you at some point, but still TBD

Thanks a lot! The code snippet helped me a lot in getting vectorized random systems to work!
While the masses, friction and elasticity and be easily changed with the set_sys method, it seems that changing the length of links causes problems and changes the system dynamics in unintended ways. I think this is because the transforms (rotation matrices?) depend on the length of the links and get calculated when leading the system XML. Are you aware of any clean workaround to change both the length + transform of a link correctly within the system object without reloading the XML?

Hi @jonasrothfuss , sure here's a code snippet for capsules which I've been using:
def set_sys_capsules(sys, lengths, radii):
  """Sets the system with new capsule lengths/radii."""
  sys2 = set_sys(sys, {'geoms.length': lengths})
  sys2 = set_sys(sys2, {'geoms.radius': radii})

  # we assume inertia.transform.pos is (0,0,0), as is often the case for
  # capsules

  # get the new joint transform
  cur_len = sys.geoms[1].length[:, None]
  joint_dir = jax.vmap(math.normalize)(sys.link.joint.pos)[0]
  joint_dist = sys.link.joint.pos - 0.5 * cur_len * joint_dir
  joint_transform = 0.5 * lengths[:, None] * joint_dir + joint_dist
  sys2 = set_sys(sys2, {'link.joint.pos': joint_transform})

  # get the new link transform
  parent_idx = jp.array([sys.link_parents])
  sys2 = set_sys(
      sys2,
      {
          'link.transform.pos': -(
              sys2.link.joint.pos
              + joint_dist
              + 0.5 * lengths[parent_idx].T * joint_dir
          )
      },
  )
  return sys2

@jax.jit
def randomize_sys_capsules(
    rng: jp.ndarray,
    sys: base.System,
    min_length: float = 0.0,
    max_length: float = 0.0,
    min_radius: float = 0.0,
    max_radius: float = 0.0,
):
  """Randomizes joint offsets, assume capsule geoms appear in geoms[1]."""
  rng, key1, key2 = jax.random.split(rng, 3)
  length_u = jax.random.uniform(
      key1, shape=(sys.num_links(),), minval=min_length, maxval=max_length
  )
  radius_u = jax.random.uniform(
      key2, shape=(sys.num_links(),), minval=min_radius, maxval=max_radius
  )
  length = length_u + sys.geoms[1].length  # pytype: disable=attribute-error
  radius = radius_u + sys.geoms[1].radius  # pytype: disable=attribute-error
  return set_sys_capsules(sys, length, radius)

Does anyone have any ideas on how to effectively implement domain randomization in the new v2 environment?

Hi @jc-bao , you can check out the test here for an example of domain randomization in v2:
https://github.com/google/brax/blob/main/brax/training/agents/ppo/train_test.py#L100-L132
Notice that rand_fn randomizes the System, and the ppo.train routine takes advantage of this function to wrap the environment:
https://github.com/google/brax/blob/main/brax/envs/wrappers/training.py#L53


Trying to fix #2248. ADDITIVE is working like intended, but I dont know how to fix MULTIPLY yet :)

nice one man!


feat: fix & upgrade

:tada: This PR is included in version 1.4.0 :tada:
The release is available on:

GitHub release
v1.4.0

Your semantic-release bot :package::rocket:


Add a migration helper for reducing HistoryDepth config value in staking pallet

PR https://github.com/paritytech/substrate/pull/12230 introduced HistoryDepth as a config value in staking pallet which bounds several storage item in the pallet. In order to lower this value for a runtime once it has been already set, we need to handle migration of the storage items affected.
Following storage items are affected by History Depth
ErasStakers, ErasStakersClipped, ErasValidatorPrefs, ErasValidatorReward, ErasRewardPoints, ErasTotalStake, ErasStartSessionIndex, StakingLedger.claimed_rewards
We should add a  generic migration function fn migrate_history_depth(from: u32, to: u32) -> Weight and put it in staking::migrations  that can be used by a future migrations to reduce the HistoryDepth gracefully.
We should also look into reducing the current HistoryDepth = 84 on Polkadot and Kusama once we have this.
cc: @kianenigma

@kianenigma  Not sure if its a nonsense idea. But I am thinking wouldn't it be great if there is a hook in the pallets like fn on_config_change(key, old_val, new_val) whenever runtime is upgraded with a new configuration value. And in this hook, we should be able to take care of very hidden/opaque migrations that are needed on config change, such as reducing HistoryDepth.
I am assuming we will have lots of cases like this elsewhere in pallets since these config values are used to bound storage items and I think its easy for a developer to not go through docs and believe a config change would be safe.

I like the idea overall, but the reason that we have so far tried to not automate things too much about this has been that doing such things in a blockchain is really hard. For example, if we write this script, perhaps in a blockchain it takes a lot of weight to do this whole migration.
Our simplistic strategy so far has been to "let the developer deal with it", not because we couldn't do it for them, but mainly because they can probably do it better.
I think was a reasonable approach in substrate in the early adoption days. I am happy to explore more automated features like this.

in pallet-bags-list we have an example of this:
https://github.com/paritytech/substrate/blob/dc22e48e1da70b84fb7b8a1ffc2076cf1b6e1d99/frame/bags-list/src/list/mod.rs#L143


Handle nonexistent login and get correct avatar

Details
Does a few things:

Makes sure app doesn't crash when login doesn't exist (for tooltips)
Makes sure we show display name in avatar tooltip if login doesn't exist
Fixes a few other crashes when logins don't exist in personalDetailsList

Fixed Issues
$ Related to https://github.com/Expensify/App/issues/20069
Tests
The following should be tested in Web-E main & in this Web-E PR: https://github.com/Expensify/Web-Expensify/pull/37753

Make sure avatars all still are working well - normal avatar & tooltip when hovering over avatar - check in at least these places

LHN
Report actions
Report Header
Report members / participants page
Profile page (New & old)

Make sure reactions work will & right-clicking them does show who the reacting user is

[ ] Verify that no errors appear in the JS console

Offline tests
None needed here
QA Steps
Same as above

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Same as above, but we can skip this since this is super quick PR
not sure that I agree with the no QA here.

@luacmartins good call, i updated to make sure we do test in staging too 👍

I'll jump in and review to help get this one out the door; but if someone approves before me don't wait for my review.

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Web-E main
https://github.com/Expensify/App/assets/9680864/60c2ff7d-4000-44f7-9204-403b0136b4e1
Web-E associated PR:
https://github.com/Expensify/App/assets/9680864/aeed2103-985e-4e69-90d1-bf75fed406c5

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Great catch @situchan!

oof!!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/youssef-lr in version: 1.3.29-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 1.3.29-11 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


How to show prompt when leaving component

How can I show a confirm popup to app users when they are moving away from component. I want to show a message something like "Unsaved changes. Do you want to leave?" and based on user action, I want to control navigation.
I tried onExit() function inside component but returning false here does not prevent navigation.
I am looking for something like react-router: setRouteLeaveHook.

Hey, So you can do this with Alerts
This is an example of my Router line
<Scene key="personal"  component={Personal} title="Personal Information" onExit={()=> Actions.refs.personal.onBack()} />
And then inside the personal component define the method onBack()
(Or whatever you put after the personal.yourmethodname)
onBack(){
console.warn("triggered back")
// {I18n.t('Account_Name')}
if(this.state.verified == false){
Alert.alert(
'Verification Recommended',
'You will not receive daily rewards without a verified number',
[
{ text: 'Verify', onPress: () => Actions.personal() },
{text: 'Ask me later', onPress: () => console.log('Ask me later pressed')},
],
{ cancelable: false },
);
}
}
Then do the actual routing based off the selected alert message :)
Note: Only tested on IOS
Hope this helps


go API: Add support for more than one block device

Changes DiskImage to an array called DiskImages with keys Path and
SizeMB. Also changes the JSON key from "disk" to "disk_images".
DiskSize is removed as size is set per disk image.
This allows multiple block devices to be mounted via the API and fixes #137

@rn thanks for the review. I've updated to make it more consistent with current linuxkit.

Minor comment but LGTM


Fix moving position indicator out of bounds in FileAccessMemory

Position indicator was incremented by p_length in get_buffer() and store_buffer() even if it meant exceeding buffer length.

Thanks!

Cherry-picked for 4.0.3.

Cherry-picked for 3.5.3.


Going to Storage tab in host details page causes Error page

Rancher Version: v1.2.0-pre3
Steps to Reproduce:

Go to Host details page
Click on Storage tab

Results: Error e.forEach is not a function

Expected: No error

Same on 1.1.4 stable (just upgraded from 1.1.3 stable)

Rancher	v1.1.4
Cattle	v<IP_ADDRESS>
User Interface	v1.1.14
Rancher Compose	v0.8.6
I got same error just now

Version - 1.2.0-pre4-rc2
Not able to duplicate

Got the same error with
Rancher 1.1.4
EFS Convoy

Seeing this as well.
Rancher	v1.1.4
User Interface	 v1.1.14
OS: CoreOS 1122.2.0
Docker: 1.10.3

Application Error TypeError: e.forEach is not a function
    at Array.addObjects (.../assets/vendor-ebfa7dda04b9f2b654291bf27e70bf22.js:14:20536)
...

same error

Useful
Info

Versions
Rancher v1.1.4 Cattle: v<IP_ADDRESS> UI: v1.1.14

Access
Disabled

Orchestration
Cattle

Route
host.containers

Facing same issue with following:

@harshal-shah Yes, it is fixed in v1.2.0-pre4-rc2+ and will be available in the next release.


Regenerate UCUM and FHIRPath lexers/parsers with latest antlr4

And update to 4.9.3.
At first I tried to not add the copyright back in as we are neither the authors
of the grammar nor the generated java classes, but that failed our checkstyle
rule and so now I've added those back in.
I also removed the generated tokens and interp files as those are not
needed at runtime (source:
https://stackoverflow.com/questions/59734259/antlr-generated-files).
Commands for regenerating:
antlr4 -no-listener -package com.ibm.fhir.model.ucum fhir-model/UCUM.g4
&& sed -i.bak $'s/\t/    /g' fhir-model/UCUM*.java && mv
fhir-model/UCUM*.java fhir-model/src/main/java/com/ibm/fhir/model/ucum/

antlr4 -visitor -no-listener -package com.ibm.fhir.path fhir-path/FHIRPath.g4 &&
sed -i.bak $'s/\t/    /g' fhir-path/FHIRPath*.java && mv
fhir-path/FHIRPath*.java fhir-path/src/main/java/com/ibm/fhir/path/

Signed-off-by: Lee Surprenant<EMAIL_ADDRESS>

And update to 4.9.3.
At first I tried to not add the copyright back in as we are neither the authors of the grammar nor the generated java classes, but that failed our checkstyle rule and so now I've added those back in.
I also removed the generated tokens and interp files as those are not needed at runtime (source: https://stackoverflow.com/questions/59734259/antlr-generated-files).
Commands for regenerating:
antlr4 -no-listener -package com.ibm.fhir.model.ucum fhir-model/UCUM.g4
&& sed -i.bak $'s/\t/    /g' fhir-model/UCUM*.java && mv
fhir-model/UCUM*.java fhir-model/src/main/java/com/ibm/fhir/model/ucum/

antlr4 -visitor -no-listener -package com.ibm.fhir.path fhir-path/FHIRPath.g4 &&
sed -i.bak $'s/\t/    /g' fhir-path/FHIRPath*.java && mv
fhir-path/FHIRPath*.java fhir-path/src/main/java/com/ibm/fhir/path/

Signed-off-by: Lee Surprenant<EMAIL_ADDRESS>
https://github.com/IBM/FHIR/wiki/ANTLR-Usage <-- Lee created this.


bugfix: remove config check and fix memory leak in traffic-tag

Ⅰ. Describe what this PR did
修复 traffic-tag 内存泄露和空配置时不阻塞配置下发
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhaonan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

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

Project coverage is 43.49%. Comparing base (ef31e09) to head (8237889).
Report is 169 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1435      +/-   ##
==========================================
+ Coverage   35.91%   43.49%   +7.57%
==========================================
  Files          69       76       +7
  Lines       11576    12320     +744
==========================================
+ Hits         4157     5358    +1201
+ Misses       7104     6626     -478
- Partials      315      336      +21

see 69 files with indirect coverage changes


Delete entrypoint.sh

Thank you for contributing! Please confirm this pull request meets the following requirements:

[x ] I followed the contributing guidelines: https://github.com/github/explore/blob/master/x I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee). Mike

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[ ] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

you must check data entry with starting and then restart your program for this might help us both


Automatic bracing cannot be used with vertical bars in physics extension

Issue Summary
The auto-bracing command \qty does not work with vertical bars (though \vqty works)
Admittedly \qty|a+b| is a somewhat odd thing to try to use and might be sufficiently rare that it doesn't warrant fixing in MathJax, but it does catch me off guard every now and then and does deviate from the reference implementation of physics.
The documentation for the LaTeX physics package can be found on CTAN
Note that the physics package needs to be loaded. I couldn't find a demo page that has this loaded by default, unfortunately.
Steps to Reproduce:
This does not render
$$
\qty|a+b|
$$

This renders fine
$$
\vqty{a+b}
$$

Technical details:

MathJax Version: 3.2.2
Client OS: Windows
Browser: Electron Application (Chromium)

Thanks for the report.  I am able to reproduce the issue and will check it out.
Just FYI, you can use \require{physics} to load the physics package if it isn't loaded by default.

OK, it turns out that the code that looks for nested delimiters is causing this problem, and is treating the close | like a nested open |.  There is an easy fix, and I will make a PR for it.  If you need a patch in the meantime, let me know I can give you a configuration that fixes it.

Thank you so much for looking into this! I've resorted to using \vqty for now, but super happy to see that I won't have to in the future! No need for an interim patch, I am perfectly content to wait for the next release!


FEAT: add HSM groups in CFS configuration and BOS sessiontemplates in SAT file as tags to CFS configurations

One of Manta's goals is to make CFS configurations as first citizens, for this we need to make user we can identify each CFS configuration for each HSM group/tenant.
CFS configurations don't contain HSM information, this makes difficult to find out which CFS configuration belongs to which tenant. Currently, CSCS is embedding the HSM name into the CFS configuration name, this is far from optimal.
This issue proposes to add HSM groups as tags to the CFS configurations.

CFS configurations don't have a tags, this means this development will need to be done outside CSM.
We won't do this for now


Fix error on array_reverse of null array

This can occur if a directory is filtered out. In my case, all folders were filtered out, resulting in this issue

I don't understand the problem this solves and don't get any errors by filtering out all folders. Can you please provide a detailed set of instructions to follow from a clean installation so I can reproduce this?


all dead mobs turn sideways, even if the sprite shouldn't

Description

this needs to be a datafield so that it can be enabled/disabled when needed

This still needs fixing as alive mobs are still rotated and moving around.

Also separately is that someone needs to audit all mobs for dead / crit states.

Might even be easier to just remove RotationVisuals from non-humanoid mobs unless the buckling rotation is that desired.


build!: bump sdk to 3.0.0-dev.73

BREAKING CHANGE: Consume SDK interface changes by adding Start func

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?) not impact
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?) not impact

Testing Instructions

Run unit test
New Dependency Instructions (If applicable)

Codecov Report

Merging #320 (33edf6f) into main (b3088f7) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #320      +/-   ##
==========================================
- Coverage   33.42%   33.38%   -0.04%
==========================================
  Files          18       18
  Lines        1798     1800       +2
==========================================
  Hits          601      601
- Misses       1131     1133       +2
  Partials       66       66

Impacted Files
Coverage Δ

internal/driver/driver.go
14.09% <0.00%> (-0.08%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


⚠ Turnos 24x7 has degraded performance

In 5d546ff, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 805 ms

Resolved: Turnos 24x7 performance has improved in cc04b63.


Improve_egi_check_in_api_v2_instructions

Summary

Add instructions on how VO Managers can request REST API credentials

@vardizzo-lab can you please review this change?


Add wrapper to new client SDK method to produce GraphQL input from Rosetta txns

The new method is what #8282 will create. Need to make that available in the distributed SDK.

Closing because https://github.com/MinaProtocol/mina/pull/8390 is merged


Update page ping functionality to make it possible to separately set ping resolution and timeout interval

Suggested by @UriGrod
In the current implementation, a page ping fires every X seconds. A user is considered active if there's been activity in the last ping period, in which case a ping fires. If not, no ping fires.
A byproduct of this approach is that it results in problems for users who want to to use a very high ping resolution (i.e. distinguish users who are active on the site for 53 seconds vs 58 seconds for example). By setting ping periods to be very short, it forces the user to be active over that very short period in order for the ping to fire. This means that it may report a user as inactive, when in fact, the user is still reading content, but hasn't e.g. moved a mouse or performed another activity to trigger the ping. As a result, we recommend that users keep ping periods relatively long (e.g. 10 seconds plus).
An alternative approach is to set two periods:

A ping period, that determines the resolution of the measure
A timeout period, which determines how long a period of inactivity needs to occur before a ping fails to fire

This is the approach taken by Riveted. See here for more details.

+1 for this. We are looking at moving to snowplow from our homegrown tracking that uses riveted for tracking active engaged time. Is there any way to incorporate riveted-based timing using snowplow?

Hey @ryanrozich - it should be straightforward to use Riveted with Snowplow. You would just model the data portion of the Riveted callback as a JSON Schema, add it to Iglu Central and fire a Snowplow self-describing event in the Riveted event handler.


The particles generated by spell circles cannot be seen through colored or tinted glass

I have also included a picture of my video settings and the log file if that helps
latest.log

Are you using Optifine, Sodium, or any other mods that mess with graphics like that?

Im only using the mods that hexcasting requires
also im using the curseforge launcher if that helps
heres a picture of the mods folder:

after a bit of searching it turns out this is actually a relatively new minecraft feature and to see the particles through colored glass you need to enable "fabulous" graphics


task-timer/task-timer sample seems broken with beta6

task-timer/task-timer sample seems broken with beta6
openjdk version "1.8.0_162"
ubuntu16.04
ballerina-0.970.0-beta6-SNAPSHOT

command
./ballerina run /home/shavantha/products/ballerina/ballerina-examples/examples/task-timer/task-timer.bal
output
error: ./task-timer.bal:23:5: undefined function 'sleepCurrentWorker'
compilation contains errors

I updated the examples before testing
From https://github.com/ballerina-platform/ballerina-examples
bcbfbd6..7d1c14d  master     -> origin/master

[new branch]      release-0.970.0-beta5 -> origin/release-0.970.0-beta5
[new branch]      release-0.970.0-beta6 -> origin/release-0.970.0-beta6
[new tag]         v0.970.0-beta5 -> v0.970.0-beta5
[new tag]         v0.970.0-beta6 -> v0.970.0-beta6
Updating bcbfbd6..7d1c14d


Incorrect year in binary names

Platform:
Mac
Architecture:
X64
Please describe the issue that you are having with our binaries and if possible how to recreate it.
The releases for AdoptOpenJDK 11 are named incorrectly on github: the 2019-12-31 build is mis-tagged as jdk11u-2020-12-31-15-31. There are a few others mislabelled as 2020 too. This plays havoc with automation scripts that grab the latest release.

@johnoliver spotted this yesterday afternoon too. Thanks for raising the issue

@sxa555 I think this is different, this issue is the Nov 31st year rollover issue we had, we should just delete https://github.com/AdoptOpenJDK/openjdk11-binaries/releases/tag/jdk11u-2020-12-31-15-31

+1 from me to removal


[Webpack 5] Module Federation - Shared exposed modules from host to remote do not work

Bug report

What is the current behavior?
application-a exposes SharedFromA to application-b  and imports AppAgendaChild from application-b
application-b exposes AppAgendaChild to application-a but it imports {SharedFromA} from 'application_a/SharedFromA';
If the current behavior is a bug, please provide the steps to reproduce.

clone repo https://github.com/mihaisavezi/federated-libraries-get-started/tree/issue/use-case-host-remote
run yarn dev to start the applications
Uncomment  import {SharedFromA} from 'application_a/SharedFromA'; in application-b/src/app.jsx
notice the error

VM284 remoteEntry.js:2 Uncaught (in promise) TypeError: r is not a function
while loading "./SharedFromA" from webpack/container/reference/application_a
    at s (VM284 remoteEntry.js:2)
    at p (VM284 remoteEntry.js:2)
    at s (VM284 remoteEntry.js:2)
    at VM284 remoteEntry.js:2
    at s (VM284 remoteEntry.js:2)
    at VM284 remoteEntry.js:2
    at Array.forEach (<anonymous>)
    at Object.i.f.remotes (VM284 remoteEntry.js:2)
    at VM284 remoteEntry.js:2
    at Array.reduce (<anonymous>)

What is the expected behavior?

application-a can load module exposed by application-b that itself loads something exposed from application-a

Other relevant information:
webpack version:  5.0.0-beta.24
Node.js version: 10.15.3
Operating System: MacOS Mojave 10.14.6
Additional tools:

https://github.com/mihaisavezi/federated-libraries-get-started/blob/05a1d1ed0e75a626afef432ae18f8190fa2d8a8a/packages/application-a/public/index.html#L6
This should be <script src="http://localhost:3001/remoteEntry.js"></script>


Where is the code for generating error maps?

Dear authors,
Thanks for your impressive work!
I am trying to reproduce the error maps you showed in Figure 6, but I cannot find the code for it. Could you share it? Thanks!

Hi,
I will add the code to generate the error map this week :)
Thanks
Yiming

Hi,
Please check my latest commit for saving the error maps. You need to set error_map=False (https://github.com/neu-vi/PlanarRecon/blob/main/tools/eval3d_geo_ins.py#L67) if you want to save the error maps.
Best

Dear authors,
Thanks for your impressive work!
I am trying to reproduce the error maps you showed in Figure 6, but I cannot find the code for it. Could you share it? Thanks!

Do you have the ScanNet dataset? Can you share it? Thank you very much.


Added CSV processor

This adds a reusable CSV file processor that can handle:

row validation
file format validation
checksums based on arbitrary columns
two-stage commit
undo of committed data
asynchronous file processing using celery

Current use cases are for Staff Graded Points, Gradebook import/export, and Program Enrollment import/export.

@davestgermain This is great functionality.   Can you put this in a new repo?  This is not necessarily a feature that all Django apps will need.  Let me know if you want me to create the new repo for you.

@nasthagiri I wasn't sure if it needed a new repo. I can do that (though I wish it didn't require an IT ticket every time). For simplicity, would this be a cookiecutter django app repo, even though it isn't a django app?

Moved to davestgermain/super-csv


Support for laravel 5.5

Added possibility to change resource path in configuration

Hi, thanks for PR, but I will not merge it. If you would like to use your own view, you can do it by publishing package views and updating them - it is built in Laravel functionality: Overriding Package Views


Crash from Inventory NPE with SpongeVanilla 1.17.1

I am currently running
Sponge: 1.17.1-9.0.0-SNAPSHOT
SpongeVanilla: 1.17.1-9.0.0-RC929
JVM: 16.0.1/64-bit (Private Build)
OS: Linux/5.4.0-66-generic (amd64)

Plugins/Mods:
CubeEngine - LibCube v2.0.0-SNAPSHOT
CubeEngine - Zoned v1.1.0-SNAPSHOT
CubeEngine - ItemDuct v1.2.0-SNAPSHOT
CubeEngine - Roles v1.1.0-SNAPSHOT
CubeEngine - Chat v1.0.1-SNAPSHOT
CubeEngine - Portals v1.1.0-SNAPSHOT
CubeEngine - Locker v1.1.0-SNAPSHOT
CubeEngine - tablist v1.0.0-SNAPSHOT
CubeEngine - Squelch v1.0.0-SNAPSHOT
CubeEngine - VanillaPlus v1.1.0-SNAPSHOT
CubeEngine - Teleport v1.1.0-SNAPSHOT
CubeEngine - Writer v1.0.0-SNAPSHOT
CubeEngine - KickBan v1.1.0-SNAPSHOT
CubeEngine - Protector v1.2.0-SNAPSHOT
CubeEngine - Spawn v1.1.0-SNAPSHOT
CubeEngine - Terra v1.2.0-SNAPSHOT
CubeEngine - Travel v1.1.0-SNAPSHOT
CubeEngine - Multiverse v1.1.0-SNAPSHOT
CubeEngine - Spawner v1.0.1-SNAPSHOT
CubeEngine - Powertools v1.1.0-SNAPSHOT
CubeEngine - Elevator v1.1.0-SNAPSHOT
CubeEngine - Mechanism v1.0.0-SNAPSHOT
CubeEngine - Kits v1.1.0-SNAPSHOT

Issue Description
The server crashed after a player logged in. They were online earlier with no problems.
[Server thread/FATAL]: Error executing task on Server java.lang.NullPointerException: Cannot invoke "net.minecraft.world.entity.player.Player.getInventory()" because "player" is null

Here's the log file that captures the above, and then the phase tracker convulsing in all it's glory:
latest.log

java.lang.NullPointerException: Cannot invoke "net.minecraft.world.entity.player.Player.getInventory()" because "player" is null
	at org.spongepowered.common.event.tracking.context.transaction.inventory.PlayerInventoryTransaction.<init>(PlayerInventoryTransaction.java:49) ~[PlayerInventoryTransaction.class:1.17.1-9.0.0-RC929]
	at org.spongepowered.common.event.tracking.context.transaction.TransactionSink.logPlayerInventoryChange(TransactionSink.java:322) ~[TransactionSink.class:1.17.1-9.0.0-RC929]
	at org.spongepowered.common.event.tracking.phase.packet.PacketContext.close(PacketContext.java:133) ~[PacketContext.class:1.17.1-9.0.0-RC929]

PacketContext.packetPlayer is missing.

Fixed by https://github.com/SpongePowered/Sponge/commit/5d0c1eeb169af323c55c3b88f924b58f13d899fe
Merged into api-9


call isPlaying function properly

setCurrentFrame was not working if the video was not playing, because the control.isPlaying() function was not called properly, as if it was a property instead of a function.
easy fix!

the current package version (npm) is not the current in github as well.

I pushed a current version to npm. Thanks for the hint


Stereo Image pointcloud Possibility?

Hi just curious if was possible for NVIDIA_ISAAC-ROS to use a point cloud generated from stereo cameras and what would be  their equivalent params lidar_width, lidar_height, and lidar_vertical_fov_rad would be set for a stereo camera pointcloud.

This is not currently supported. We support rotating LiDAR pointclouds and depth images.
Can you project your pointcloud into a depth image and then feed it in to nvblox?


emitDecoratorMetadata does not preserve array types on fields

TypeScript Version:  2.1.1 / nightly (2.2.0-dev.201xxxxx)
All Typescript Versions
Code
class Post {
     tags: string[];
}

Expected behavior:
There should be metadata added to indicate the type of array.
class Post {
   constructor() {}
}
__decorate([
    __metadata('design:type', [String])
], Post.prototype, "tags", void 0);

Actual behavior:
class Post {
   constructor() {}
}
__decorate([
    __metadata('design:type', Array)
], Post.prototype, "tags", void 0);

If you look at how rest parameters are handled, there is precedent for preserving array type:
Given:
class Post {
     tags: string[];
     constructor(...tags:string[]) {}
}

The output is:
class Post {
   constructor() {}
}
__decorate([
    __metadata('design:type', Array)
], Post.prototype, "tags", void 0);
Post = __decorate([
    __metadata('design:paramtypes', [String])
], Post);

@rbuckton It looks like you have done a great deal of the work on the file (src/compiler/transformers/ts.ts).  Do you know if PRs would be accepted for this change, or if this change is even acceptable?

So after thinking about this for a bit, I realized that the param types is actually reducing string[] to String to handle the variadic arguments.  Would it be possible to treat the array as a generic class? Array<string>, and perhaps store all generic types in the metadata?

Closing as a duplicate of #3015.


Refactor RowMutationInformation to use string type

This PR closes #31335 via refactoring BigQueryIO's assignment of the _CHANGE_SEQUENCE_NUMBER pseudo column from a long to fixed hex string.
All BigQuery related tests for ./gradlew :sdks:java:io:google-cloud-platform:postCommit and ./gradlew :sdks:java:io:google-cloud-platform:build passed on my local machine.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Can we add or update existing tests in StorageApiSinkRowUpdateIT? That class contains integration tests for RowMutationInformation. Would be good to have some real end-to-end tests to check this new behavior

@ahmedabu98 that test already covers the refactor behavior. For example, there's a call to RowMutationInformation.of using a long value. This is forwarded to the RowMutationInformation.of that takes the string parameter set using Long.toHexString. Adding additional tests using the string parameter directly would just test implementation details.

@damondouglas Sorry I mean the new behavior of having multiple sections in the CSN (e.g. a\b\c\d). I don't think that's covered in our integration tests.

R: @ahmedabu98

@damondouglas Sorry I mean the new behavior of having multiple sections in the CSN (e.g. a\b\c\d). I don't think that's covered in our integration tests.

@ahmedabu98 I added the test cases but to keep things simple used AAA/<n> where n was the original long.

Thank you, @ahmedabu98 . I will merge after checks pass.

Thank you, @ahmedabu98 . I will merge after checks pass.

FYI failing checks have nothing to do with code in the PR. Ran additional internal tests (see internal chat) and passed.


fix(@angular/cli) escape paths using double quotes

Closes #21027

@elvisbegovic, confirms that this fix addresses the problem.


Add examples for random and manual partitioning

Towards addressing #323 and #302. @Shopify/kafka

just nits, no major objections

A more useful example might be writing your own partitioner, but I guess there's real live code (the existing implementations) for that

It's only a one line change, but it doesn't necessarily make natural sense that this is part of the Config, instead of part of the ProducerMessage struct or SendMessage call

¯_(ツ)_/¯

one typo, then :shipit:


Dom tree improvement

@sushant94 this is the PR for #46 , how do you find it ?

Sorry, took me a while to get to this. Reviewing this now.

I guess its fine to merge

pls @shakram02  rebase.
pls @P4N74 review
pls @sushant94 wakeup

I'm a bit busy those days, so it might take some time

@radare Doing another review. I don't remember what has changed, need to look back at the feedback I gave @shakram02.

Pingy-pongy-pong.

@sushant94 what with this one?


Changed the value structure to include vectors.

Closes #138

[:)] pvget PANDA1:PVI
...
    structure pvi # Same as before
...
    structure value
        structure bits
            string d PANDA1:BITS:PVI
        structure[] calc
            (none)
            structure
                string d PANDA1:CALC1:PVI
            structure
                string d PANDA1:CALC2:PVI
        structure[] clock
            (none)
            structure
                string d PANDA1:CLOCK1:PVI
            structure
                string d PANDA1:CLOCK2:PVI
...

Please can we have a 0.11 release when this is in?