Submit an iOS app for review with deliver fails with: There is another reviewSubmissions with id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx still in progress.

New Issue Checklist

[ ] Updated fastlane to the latest version

I'm still on 2.210.1

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

Issue Description
I had an existing iOS version pending developer release (15.9.1), but we discovered a bug, so I cancelled 15.9.1 and then submitted iOS version 15.9.2 for review with deliver. deliver failed with:
ERROR [2023-08-24 16:01:26.85]: Resource state invalid - There is another reviewSubmissions with id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx still in progress.

I tried running the same submission again, but I got a different error:
ERROR [2023-08-24 16:11:18.18]: appStoreVersions with id 'yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy' is not in valid state. - This resource cannot be reviewed, please check associated errors to see why.
The request cannot be fulfilled because of the state of another resource. - Version is not ready to be submitted yet, please try again later.

My app has an iOS app and a tvOS app in the store. We also have a macOS App in a 1.0 Prepare for Submission state.
I was able to submit successfully through the App Store Connect Web UI, though App Store Connect was showing me a lot of server error pages while I used the UI, so maybe this was some kind of App Store Connect bug?
Command executed
bundle exec fastlane --verbose SUBMIT_TESTFLIGHT_BUILD_FOR_REVIEW \
  build_number:"$app_build_number" \
  app_version:"$app_version" \
  skip_metadata:"$skip_metadata" \
  skip_screenshots:"$skip_screenshots" \
  overwrite_screenshots:"$overwrite_screenshots" \
  submit_for_review:"$submit_for_review"

This is the lane that has my deliver call. app_store_api_key is a function that pulls my app store API key out of the CI environment.
lane :SUBMIT_TESTFLIGHT_BUILD_FOR_REVIEW do |options|
  api_key = app_store_api_key
  deliver(
    api_key: api_key,
    skip_binary_upload: true,
    app_version: options[:app_version],
    build_number: options[:build_number],
    skip_metadata: options[:skip_metadata],
    skip_screenshots: options[:skip_screenshots],
    overwrite_screenshots: options[:overwrite_screenshots],
    submit_for_review: options[:submit_for_review],
    phased_release: true,
    precheck_include_in_app_purchases: false
  )
end

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

first attempt

+------------------------+----------------------+
| Detected Values from './fastlane/Deliverfile' |
+------------------------+----------------------+
!!!!! REDACTED !!!!!!
| automatic_release      | false                |
| phased_release         | true                 |
| force                  | true                 |
| submission_information |                      |
+------------------------+----------------------+
INFO [2023-08-24 15:57:27.74]: Creating authorization token for App Store Connect API
+--------------------------------------------------------------------+--------------------------+
|                                    deliver 2.210.1 Summary                                    |
+--------------------------------------------------------------------+--------------------------+
| api_key                                                            | ********                 |
| skip_binary_upload                                                 | true                     |
| app_version                                                        | 15.9.2                   |
| build_number                                                       | 1592                     |
| skip_metadata                                                      | false                    |
| skip_screenshots                                                   | true                     |
| overwrite_screenshots                                              | false                    |
| submit_for_review                                                  | true                     |
| phased_release                                                     | true                     |
| precheck_include_in_app_purchases                                  | false                    |
| screenshots_path                                                   | ./fastlane/screenshots   |
| metadata_path                                                      | ./fastlane/metadata      |
!!!!! REDACTED !!!!!!
| platform                                                           | ios                      |
| edit_live                                                          | false                    |
| use_live_version                                                   | false                    |
| skip_app_version_update                                            | false                    |
| force                                                              | true                     |
| sync_screenshots                                                   | false                    |
| verify_only                                                        | false                    |
| reject_if_possible                                                 | false                    |
| automatic_release                                                  | false                    |
| reset_ratings                                                      | false                    |
| submission_information.add_id_info_limits_tracking                 | true                     |
| submission_information.add_id_info_tracks_action                   | true                     |
| submission_information.add_id_info_tracks_install                  | false                    |
| submission_information.add_id_info_serves_ads                      | true                     |
| submission_information.add_id_info_uses_idfa                       | true                     |
| submission_information.content_rights_contains_third_party_content | true                     |
| submission_information.content_rights_has_rights                   | true                     |
!!!!! REDACTED !!!!!!
| run_precheck_before_submit                                         | true                     |
| precheck_default_rule_level                                        | warn                     |
| ignore_language_directory_validation                               | false                    |
+--------------------------------------------------------------------+--------------------------+
INFO [2023-08-24 15:57:42.24]: Making sure the latest version on App Store Connect matches '15.9.2'...
INFO [2023-08-24 15:57:45.60]: Successfully set the version to '15.9.2'
INFO [2023-08-24 15:57:45.61]: Loading './fastlane/metadata/cs/description.txt'...
!!!!! REDACTED !!!!!
INFO [2023-08-24 15:57:45.82]: Loading './fastlane/metadata/review_information/notes.txt'...
WARN [2023-08-24 15:57:54.05]: Will begin uploading metadata for '15.9.2' on App Store Connect
INFO [2023-08-24 15:57:54.05]: Uploading metadata to App Store Connect for version
INFO [2023-08-24 15:57:57.48]: Uploading metadata to App Store Connect for localized version 'cs'
!!!!! REDACTED !!!!!
INFO [2023-08-24 15:58:10.92]: Uploading metadata to App Store Connect for localized info 'ja'
Timeout received! Retrying after 3 seconds (remaining: 5)...
INFO [2023-08-24 15:58:10.96]: Uploading metadata to App Store Connect for localized info 'ko'
INFO [2023-08-24 15:58:11.23]: Uploading metadata to App Store Connect for localized info 'id'
INFO [2023-08-24 15:58:11.26]: Uploading metadata to App Store Connect for localized info 'zh-Hant'
INFO [2023-08-24 15:58:11.38]: Uploading metadata to App Store Connect for localized info 'vi'
ERROR [2023-08-24 15:58:12.83]: Category 'MZGenre.Photography' from iTunesConnect has been deprecated. Please replace with 'PHOTO_AND_VIDEO'
ERROR [2023-08-24 15:58:12.83]: Category 'MZGenre.SocialNetworking' from iTunesConnect has been deprecated. Please replace with 'SOCIAL_NETWORKING'
ERROR [2023-08-24 15:58:12.83]: You can find more info at https://docs.fastlane.tools/actions/deliver/#reference
INFO [2023-08-24 15:58:14.47]: Uploading app review information to App Store Connect
INFO [2023-08-24 15:58:15.22]: Running precheck before submitting to review, if you'd like to disable this check you can set run_precheck_before_submit to false
INFO [2023-08-24 15:58:15.22]: Making sure we pass precheck   ♀    before we submit
+--------------------------+--------------------------+
|            Summary for precheck 2.210.1             |
+--------------------------+--------------------------+
| default_rule_level       | warn                     |
| include_in_app_purchases | false                    |
!!!!! REDACTED !!!!!
| platform                 | ios                      |
| use_live                 | false                    |
+--------------------------+--------------------------+
INFO [2023-08-24 15:58:15.23]: Creating authorization token for App Store Connect API
INFO [2023-08-24 15:58:15.23]: Checking app for precheck rule violations
INFO [2023-08-24 15:58:55.91]: ✅  Passed: No negative  sentiment
INFO [2023-08-24 15:58:55.92]: ✅  Passed: No placeholder text
!!!!! REDACTED !!!!!
WARN [2023-08-24 15:58:55.94]:     Failed: No mentioning  competitors-> mentioning other platforms, like Android or Blackberry
INFO [2023-08-24 15:58:55.95]: ✅  Passed: No future functionality promises
INFO [2023-08-24 15:58:55.96]: ✅  Passed: No words indicating test content
INFO [2023-08-24 15:58:56.22]: ✅  Passed: No curse words
INFO [2023-08-24 15:58:56.22]: ✅  Passed: No words indicating your IAP is free
DEBUG [2023-08-24 15:58:56.22]: custom_text excluded because no data was passed to it e.g.: custom_text(data: )
DEBUG [2023-08-24 15:58:56.23]:     CopyrightDateRule didn't find words "2023"
WARN [2023-08-24 15:58:56.23]:     Failed: Incorrect, or missing copyright date-> using a copyright date that is any different from this current year, or missing a date
WARN [2023-08-24 15:59:20.59]:     Failed: No broken urls-> unreachable URLs in app metadata
+--------------------------------+-------------------------+
|                    Potential problems                    |
+--------------------------------+-------------------------+
| Field                          | Failure reason          |
+--------------------------------+-------------------------+
|  tv privacy policy: (da)      | found: google           |
|  tv privacy policy: (zh-Hans) | found: google           |
|  tv privacy policy: (el)      | found: google           |
|  tv privacy policy: (ms)      | found: google           |
|  tv privacy policy: (ja)      | found: google           |
|  tv privacy policy: (pt-BR)   | found: google           |
|  tv privacy policy: (es-MX)   | found: google           |
|  tv privacy policy: (ko)      | found: google           |
|  tv privacy policy: (vi)      | found: google           |
|  tv privacy policy: (tr)      | found: google           |
|  tv privacy policy: (es-ES)   | found: google           |
|  tv privacy policy: (fr-FR)   | found: google           |
|  tv privacy policy: (it)      | found: google           |
|  tv privacy policy: (no)      | found: google           |
|  tv privacy policy: (zh-Hant) | found: google           |
|  tv privacy policy: (sv)      | found: google           |
|  tv privacy policy: (nl-NL)   | found: google           |
|  tv privacy policy: (th)      | found: google           |
|  tv privacy policy: (pt-PT)   | found: google           |
|  tv privacy policy: (id)      | found: google           |
|  tv privacy policy: (de-DE)   | found: google           |
|  tv privacy policy: (ru)      | found: google           |
|  tv privacy policy: (fi)      | found: google           |
| copyright                      | missing: 2023           |
!!!!! REDACTED !!!!!
+--------------------------------+-------------------------+
WARN [2023-08-24 15:59:20.60]: precheck   ♀     found one or more potential metadata problems, but this won't prevent fastlane from completing
INFO [2023-08-24 15:59:22.20]: Selecting existing build-number: 1592
INFO [2023-08-24 15:59:23.63]: Selecting build 15.9.2 (1592)...
INFO [2023-08-24 15:59:31.03]: Successfully selected build
DEBUG [2023-08-24 15:59:31.45]: Updating app store version for IDFA status of 'true'
DEBUG [2023-08-24 15:59:31.71]: Updated app store version for IDFA status of 'true'
DEBUG [2023-08-24 15:59:31.71]: Updating IDFA declaration
DEBUG [2023-08-24 15:59:32.23]: Updated IDFA declaration
INFO [2023-08-24 15:59:32.23]: Successfully updated IDFA declarations on App Store Connect
DEBUG [2023-08-24 15:59:32.23]: Updating contents rights declaration on App Store Connect
INFO [2023-08-24 15:59:35.39]: Successfully updated contents rights declaration on App Store Connect
Timeout received! Retrying after 3 seconds (remaining: 5)...
Timeout received! Retrying after 3 seconds (remaining: 4)...
WARN [2023-08-24 16:01:26.85]: Lane Context:
INFO [2023-08-24 16:01:26.85]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios SUBMIT_TESTFLIGHT_BUILD_FOR_REVIEW", :MY_METADATA=>[]}
ERROR [2023-08-24 16:01:26.85]: Resource state invalid - There is another reviewSubmissions with id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx still in progress.

second attempt

+------------------------+----------------------+
!!!!! REDACTED !!!!!!
| automatic_release      | false                |
| phased_release         | true                 |
| force                  | true                 |
| submission_information |                      |
+------------------------+----------------------+
INFO [2023-08-24 16:09:03.98]: Creating authorization token for App Store Connect API
+--------------------------------------------------------------------+--------------------------+
|                                    deliver 2.210.1 Summary                                    |
+--------------------------------------------------------------------+--------------------------+
| api_key                                                            | ********                 |
| skip_binary_upload                                                 | true                     |
| app_version                                                        | 15.9.2                   |
| build_number                                                       | 1592                     |
| skip_metadata                                                      | false                    |
| skip_screenshots                                                   | true                     |
| overwrite_screenshots                                              | false                    |
| submit_for_review                                                  | true                     |
| phased_release                                                     | true                     |
| precheck_include_in_app_purchases                                  | false                    |
| screenshots_path                                                   | ./fastlane/screenshots   |
| metadata_path                                                      | ./fastlane/metadata      |
!!!!! REDACTED !!!!!!
| platform                                                           | ios                      |
| edit_live                                                          | false                    |
| use_live_version                                                   | false                    |
| skip_app_version_update                                            | false                    |
| force                                                              | true                     |
| sync_screenshots                                                   | false                    |
| verify_only                                                        | false                    |
| reject_if_possible                                                 | false                    |
| automatic_release                                                  | false                    |
| reset_ratings                                                      | false                    |
| submission_information.add_id_info_limits_tracking                 | true                     |
| submission_information.add_id_info_tracks_action                   | true                     |
| submission_information.add_id_info_tracks_install                  | false                    |
| submission_information.add_id_info_serves_ads                      | true                     |
| submission_information.add_id_info_uses_idfa                       | true                     |
| submission_information.content_rights_contains_third_party_content | true                     |
| submission_information.content_rights_has_rights                   | true                     |
!!!!! REDACTED !!!!!!
| run_precheck_before_submit                                         | true                     |
| precheck_default_rule_level                                        | warn                     |
| ignore_language_directory_validation                               | false                    |
+--------------------------------------------------------------------+--------------------------+
INFO [2023-08-24 16:09:13.47]: Making sure the latest version on App Store Connect matches '15.9.2'...
INFO [2023-08-24 16:09:13.84]: '15.9.2' is the latest version on App Store Connect
INFO [2023-08-24 16:09:13.85]: Loading './fastlane/metadata/cs/description.txt'...
!!!!! REDACTED !!!!!!
INFO [2023-08-24 16:09:14.04]: Loading './fastlane/metadata/review_information/notes.txt'...
WARN [2023-08-24 16:09:18.71]: Will begin uploading metadata for '15.9.2' on App Store Connect
INFO [2023-08-24 16:09:18.71]: Uploading metadata to App Store Connect for version
INFO [2023-08-24 16:09:22.18]: Uploading metadata to App Store Connect for localized version 'cs'
!!!!! REDACTED !!!!!!
INFO [2023-08-24 16:09:26.26]: Uploading metadata to App Store Connect for localized info 'pt-PT'
ERROR [2023-08-24 16:09:27.48]: Category 'MZGenre.Photography' from iTunesConnect has been deprecated. Please replace with 'PHOTO_AND_VIDEO'
ERROR [2023-08-24 16:09:27.48]: Category 'MZGenre.SocialNetworking' from iTunesConnect has been deprecated. Please replace with 'SOCIAL_NETWORKING'
ERROR [2023-08-24 16:09:27.48]: You can find more info at https://docs.fastlane.tools/actions/deliver/#reference
INFO [2023-08-24 16:09:29.12]: Uploading app review information to App Store Connect
INFO [2023-08-24 16:09:31.07]: Running precheck before submitting to review, if you'd like to disable this check you can set run_precheck_before_submit to false
INFO [2023-08-24 16:09:31.07]: Making sure we pass precheck   ♀    before we submit
+--------------------------+--------------------------+
|            Summary for precheck 2.210.1             |
+--------------------------+--------------------------+
| default_rule_level       | warn                     |
| include_in_app_purchases | false                    |
!!!!! REDACTED !!!!!!
| platform                 | ios                      |
| use_live                 | false                    |
+--------------------------+--------------------------+
INFO [2023-08-24 16:09:31.08]: Creating authorization token for App Store Connect API
INFO [2023-08-24 16:09:31.08]: Checking app for precheck rule violations
INFO [2023-08-24 16:09:59.03]: ✅  Passed: No negative  sentiment
INFO [2023-08-24 16:09:59.04]: ✅  Passed: No placeholder text
!!!!! REDACTED !!!!!!
WARN [2023-08-24 16:09:59.06]:     Failed: No mentioning  competitors-> mentioning other platforms, like Android or Blackberry
INFO [2023-08-24 16:09:59.07]: ✅  Passed: No future functionality promises
INFO [2023-08-24 16:09:59.08]: ✅  Passed: No words indicating test content
INFO [2023-08-24 16:09:59.34]: ✅  Passed: No curse words
INFO [2023-08-24 16:09:59.34]: ✅  Passed: No words indicating your IAP is free
DEBUG [2023-08-24 16:09:59.34]: custom_text excluded because no data was passed to it e.g.: custom_text(data: )
DEBUG [2023-08-24 16:09:59.34]:     CopyrightDateRule didn't find words "2023"
WARN [2023-08-24 16:09:59.34]:     Failed: Incorrect, or missing copyright date-> using a copyright date that is any different from this current year, or missing a date
INFO [2023-08-24 16:10:26.25]: ✅  Passed: No broken urls
+--------------------------------+----------------+
|               Potential problems                |
+--------------------------------+----------------+
| Field                          | Failure reason |
+--------------------------------+----------------+
|  tv privacy policy: (da)      | found: google  |
|  tv privacy policy: (zh-Hans) | found: google  |
|  tv privacy policy: (el)      | found: google  |
|  tv privacy policy: (ms)      | found: google  |
|  tv privacy policy: (ja)      | found: google  |
|  tv privacy policy: (pt-BR)   | found: google  |
|  tv privacy policy: (es-MX)   | found: google  |
|  tv privacy policy: (ko)      | found: google  |
|  tv privacy policy: (vi)      | found: google  |
|  tv privacy policy: (tr)      | found: google  |
|  tv privacy policy: (es-ES)   | found: google  |
|  tv privacy policy: (fr-FR)   | found: google  |
|  tv privacy policy: (it)      | found: google  |
|  tv privacy policy: (no)      | found: google  |
|  tv privacy policy: (zh-Hant) | found: google  |
|  tv privacy policy: (sv)      | found: google  |
|  tv privacy policy: (nl-NL)   | found: google  |
|  tv privacy policy: (th)      | found: google  |
|  tv privacy policy: (pt-PT)   | found: google  |
|  tv privacy policy: (id)      | found: google  |
|  tv privacy policy: (de-DE)   | found: google  |
|  tv privacy policy: (ru)      | found: google  |
|  tv privacy policy: (fi)      | found: google  |
| copyright                      | missing: 2023  |
+--------------------------------+----------------+
WARN [2023-08-24 16:10:26.26]: precheck   ♀     found one or more potential metadata problems, but this won't prevent fastlane from completing
INFO [2023-08-24 16:10:27.05]: Selecting existing build-number: 1592
INFO [2023-08-24 16:10:28.25]: Selecting build 15.9.2 (1592)...
INFO [2023-08-24 16:10:30.43]: Successfully selected build
DEBUG [2023-08-24 16:10:30.71]: Updating app store version for IDFA status of 'true'
DEBUG [2023-08-24 16:10:31.96]: Updated app store version for IDFA status of 'true'
DEBUG [2023-08-24 16:10:31.96]: Updating IDFA declaration
DEBUG [2023-08-24 16:10:32.50]: Updated IDFA declaration
INFO [2023-08-24 16:10:32.50]: Successfully updated IDFA declarations on App Store Connect
DEBUG [2023-08-24 16:10:32.50]: Updating contents rights declaration on App Store Connect
INFO [2023-08-24 16:10:42.69]: Successfully updated contents rights declaration on App Store Connect
WARN [2023-08-24 16:11:18.18]: Lane Context:
INFO [2023-08-24 16:11:18.18]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios SUBMIT_TESTFLIGHT_BUILD_FOR_REVIEW", :MY_METADATA=>[]}
ERROR [2023-08-24 16:11:18.18]: appStoreVersions with id 'yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy' is not in valid state. - This resource cannot be reviewed, please check associated errors to see why.
The request cannot be fulfilled because of the state of another resource. - Version is not ready to be submitted yet, please try again later.

Environment
Fastfile
I can't include my whole Fastfile, but I included the associated lane where I call deliver above

fastlane gems

Gem
Version
Update-Status

fastlane
2.210.1
💥 Check failed

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-firebase_app_distribution
0.3.7
💥 Check failed

Loaded gems

Gem
Version

error_highlight
0.3.0

did_you_mean
1.6.1

bundler
2.3.9

pathname
0.2.0

rake
13.0.6

rexml
3.2.5

CFPropertyList
3.0.5

concurrent-ruby
1.1.10

i18n
1.12.0

minitest
5.16.3

tzinfo
2.0.5

zeitwerk
2.6.1

activesupport
6.1.7

public_suffix
4.0.7

addressable
2.8.1

httpclient
2.8.3

json
2.6.2

algoliasearch
1.27.5

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.644.0

aws-sigv4
1.5.2

jmespath
1.6.1

aws-sdk-core
3.159.0

aws-sdk-kms
1.58.0

aws-sdk-s3
1.114.0

babosa
1.0.4

claide
1.1.0

fuzzy_match
2.0.4

nap
1.1.0

netrc
0.11.0

ffi
1.15.5

ethon
0.15.0

typhoeus
1.4.0

cocoapods-core
1.11.3

cocoapods-deintegrate
1.0.5

cocoapods-downloader
1.6.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.1

cocoapods-trunk
1.6.0

cocoapods-try
1.2.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.3.1

gh_inspector
1.1.3

molinillo
0.8.0

ruby-macho
2.5.1

nanaimo
0.3.0

xcodeproj
1.22.0

cocoapods
1.11.3

colored
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.8.1

emoji_regex
3.2.3

excon
0.93.0

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.4

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.2

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

jwt
2.5.0

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.2.0

mini_mime
1.1.2

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

webrick
1.7.0

google-apis-core
0.9.0

google-apis-androidpublisher_v3
0.29.0

google-apis-playcustomapp_v1
0.11.0

google-apis-iamcredentials_v1
0.15.0

google-apis-storage_v1
0.19.0

google-cloud-env
1.6.0

google-cloud-errors
1.3.0

google-cloud-core
1.6.0

google-cloud-storage
1.43.0

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

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

fastlane-plugin-firebase_app_distribution
0.3.7

xcode-install
2.8.1

I just submitted an app successfully with deliver using the same Fastfile and fastlane command above, so I think this was an App Store Connect issue, and not a fastlane issue.

I wonder if they are A/B testing something or slowly rolling it out, because we just saw the same issue, and the web UI had a slightly different flow for pressing the submit button now.

This happened to me again, and I re-ran deliver 5 minutes later and it succeeded. 🤷♂

Happens to me today, repetitively on one of our apps (the other one succeeds).

Yep. We have 3 apps, 2 of which fail in this way every single time, one of which seems to work. So far I haven't figured out what the difference is.

I had one app work today and the other did not. A pattern I've noticed is when there is a newer version that's been uploaded, but is not the one we are submitting. For example, I'm submitting 2.0.0, but we also have a build uploaded under 2.1.0. Does that match what others are seeing?

For example, I'm submitting 2.0.0, but we also have a build uploaded under 2.1.0. Does that match what others are seeing?

I haven't noticed this state yet, but I'll look for it the next time I get this error. I got this error on my most recent release, but a retry fixed it.


[HOLD for payment 2023-06-29] [$250] [Accessible Pressables] Migrate ReportPreview to use accessible pressables

Migrate ReportPreview to use new pressables
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01789015714d12d8b4
Upwork Job ID:<PHONE_NUMBER>414673920
Last Price Increase: 2023-06-12

Just confirming, are we trying to achieve the below changes ?

Sorry @jeet-dhandha, we've already hired someone for this and all other [Accessible Pressable] issues. Also:

You shouldn't post proposals on issues without the Help Wanted label
For issues that do have the Help Wanted label, we have a proposal template, and are encouraged to ignore any proposals that do not follow the template.

Hi! As an expert contributor from Software Mansion I'd like to get this issue, can you assign me to this one?

PR was deployed to staging two hours ago. Are we waiting the standard regression period on these?

Are we waiting the standard regression period on these?

yep

For this payout, everyone is eligible for $250. @parasharrajat Upwork job is here, do you mind applying? Or alternatively, will you submit this payment via NewDot? Everyone else will be handled via invoice.

@JmillsExpensify minor clarification ... since this is a new feature related to a project and not a bug, the $250 review bounty for this issue should not be included in the SWM invoice. They should only be invoicing hourly for time spent on projects.

@JmillsExpensify @parasharrajat what are the next steps here?

Made a weekly

Approved $250 for Rajat based on https://github.com/Expensify/App/issues/20603#issuecomment-1621695465

All set here then?

All set! Thanks


LateInitializationError: Field 'textureId' has not been initialized

Hi, i'm your big fan.
When i added this plugin in to my project. Some log was happened.
Please help to fix this

Looks like the project is abandoned...

Hi @ntvkhoasgt, sorry for the late reply, I have been busy lately,
The reason I haven't use you approach from the beginning is because initialize textureId with 0 name may raise conflict with any other renderer that also use 0 name.
But according to this, 0 is not a name corresponds to a texture, initialize with 0 name should be non issue, so your approach is good.
I have merge your pull request, many thanks for your help.
I'm closing the issue, feel free to reach out if you have any concern.


Update gulpfile.js

comment added in this file.

reviewed and approved these changes.

this has been reviewed and approved.


doesn't work with Adobe Audition

extension works fine with photoshop but not with audition

are you able to open the extension panel in audition

are you able to open the extension panel in audition

Nope

Same issue here, works fine with all the apps I have installed (Photoshop, After Effects, Premiere Pro) except for Audition

create a ticket on discord

can you try if this version works from github actions https://github.com/teeteeteeteetee/adobe-discord-rpc/suites/18408716090/artifacts/1066722204

it fixed adobe audition problem but i have new problem now. i can't change any config options and save configuration

fixed in latest https://github.com/teeteeteeteetee/adobe-discord-rpc/releases/tag/v0.0.2


Updates spo roledefinition list, Closes #4075

This PR updates the spo roledefinition list command. Which makes the function setFriendlyPermissions global.
Closes #4075

Thank you @nicodecleyre
We'll review it ASAP!

@nicodecleyre this is an amazing change.
what do you say we wait with this PR for
#4063
#4070
#4065
to do all in one go?

@nicodecleyre this is an amazing change. what do you say we wait with this PR for #4063 #4070 #4065 to do all in one go?

it's the same for me! Whatever is the best approach 😄 !

it's the same for me! Whatever is the best approach 😄 !

Lets see how fast we will be able to merge the other PRs. If in the coming days then lets wait with this a bit and include more refactoring to it not to create a new PR in just a couple of days with the same change 👍

@nicodecleyre the mentioned PRs got merged. I think we could align this change to also refactor it in the updated commands 👍
Thanks for your awesome work. You rock 🤩

@nicodecleyre the mentioned PRs got merged. I think we could align this change to also refactor it in the updated commands 👍 Thanks for your awesome work. You rock 🤩

Hi Adam, thank you for your amazing work! :smiling_face_with_three_hearts:
I'v updated the mentioned commands to use the setFriendlyPermissions function. And also the command spo file get command
Cheers!

Thanks @nicodecleyre for the quick response. I will try to review it ASAP 👍

Could you resolve the merge conflicts in the mean time @nicodecleyre?

Could you resolve the merge conflicts in the mean time @nicodecleyre?

Thx Milan! Should be good now!

@nicodecleyre IMO this one is ready to be merged 🚀
currently, we have a bit of a 'code freeze' and we don't merge anything just before the v6 release so I will merge it after v6 is published so it will make it for the v6.1 👍

@nicodecleyre IMO this one is ready to be merged 🚀
currently, we have a bit of a 'code freeze' and we don't merge anything just before the v6 release so I will merge it after v6 is published so it will make it for the v6.1 👍

Perfect! Thank you @Adam-it !

merged manually


LRem bug fix: "bucket count" error thrown when size == count

Updated test case
Reference to https://github.com/xujiajun/nutsdb/issues/81#issuecomment-747916516

Thank you for your PR. I have Fixed it (https://github.com/xujiajun/nutsdb/pull/92) Mention from this link: #66 . So I close this PR.


Adds tests for apps.get_model

In issues #99 and #138, we had some problems when getting tenant column, when getting class with apps.get_model
Problem fixed wirh previous developments. I added a test to test the case

there's a skipped test in the check details. As discussed offline, we'll create another issue for it. It's unrelated to this pr

Two questions:

The migration reverse_func() is uncovered by tests. While that seems potentially harmless, is it typical for the other test migrations? Or do we cover them by tests in some way?
You're adding the test after the fix. Have you verified that the test fails prior to applying the fix? (Just want to be sure it's an effective test.)

Removed reverse_func,
Yes always verifying. When I'm working tests always fails, at the end I succeed to make them pass


Unable to kill long running query OR close app

I am connected to Redshift (from Windows) and I have query that is taking forever. I changed my mind and hit the "Cancel" button but the query never stops. So I tried to close the app but it will give me the error "Editor can''t be closed while SQL query is being executed". The only way to stop is by killing the process in task manager. This is not neat.

Redshift driver doesn't support query cancellation.
I'll add ability to close SQL editor with hanging query.
As a workaround you can use "Emergency Exit" (menu File) - it will close DBeaver immediately.

Hi,
but the "emergency exit" workaround is only available in the standalone version (or i am simply unable to find it in eclipse). It would be nice to have this in eclipse as well.

Hallo, which is the state of this? Is there any workaround to terminate a Redshift query? Thanks!


Consider AVIF image format for future inclusion in the engine

https://jakearchibald.com/2020/avif-has-landed/
AVIF is a new image format derived from the keyframes of AV1 video. It's a royalty-free format, and it's already supported in Chrome 85 on desktop. Android support will be added soon, Firefox is working on an implementation

See also https://netflixtechblog.com/avif-for-next-generation-image-coding-b1d75675fe4
TBH AVIF looks extraordinary, even compared to webP.

As I understand it, the AVIF format would automatically work if the browser supports it? Would be great to use this. Also as it has a lossless compression, I'm wondering If it's possible to use with the LUT problem in #774

It seems AVIF supports HDR but I suspect this might be 10-12bit precision vs full floats .. would that be enough?

Any update on that topic? Or what about webp? Draco is working so well for meshes but regarding textures, if Im not mistaken, Playcanvas is only using JPG and PNG

You can also use Basis compressed textures
On Fri, 22 Sep 2023 at 08:26, NicolasVZ777 @.***> wrote:

Any update on that topic? Or what about webp? Draco is working so well for
meshes but regarding textures, if Im not mistaken, Playcanvas is only using
JPG and PNG
—
Reply to this email directly, view it on GitHub
https://github.com/playcanvas/engine/issues/2418#issuecomment-1730935201,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADJFLCXH7CSNRX3EI3VF7DX3U4SDANCNFSM4RBQFWIQ
.
You are receiving this because you commented.Message ID:
@.***>

webp format inside glb should be supported I believe using EXT_texture_webp extension, I tested this a while back. See https://github.com/playcanvas/engine/pull/5360
You can also load webp as an assert.
But using it as a source in the Editor is not supported yet.

AVIF now support: https://blog.playcanvas.com/avif-webp-land-in-editor/


Update instructions for setup to use new InstantiateFromURL, etc

First decide on #600

#612 does some of this.

The new instructions look good. They install InstantiateFromURL in getting_started, and then we tell them their first notebook might take a while to run.


training code

Dear Annbless
Thanks for your great work for video stabilization! The result is amazing!
Could you  release the training code for this project?
Thank you for an early answer!

I had the same problem, please did you find it now？


An Error about the description in the related works

Dear authors,
Good evening!
I recently noticed your research paper "SpeechGPT: Empowering Large Language Models with Intrinsic Cross-Modal Conversational Abilities" published on Arxiv.
However, there is an error in the description of our recent work X-LLM: Bootstrapping Advanced Large Language Models by Treating Multi-Modalities as Foreign Languages
Our design is not a cascade architecture that separates ASR and large language models and then connects them. Instead, we use a pre-trained acoustic encoder based on CIF (Continuous Integration and Fire Mechanism) to connect with LLM through the S2L interface. As far as I know, our work is the first to use a representation-based end-to-end modeling approach for LLM-based speech recognition.
I hope you can make a correction to this issue as soon as possible to avoid any misunderstandings by the public about our work.
Thanks!
Minglun.

@MingLunHan
Fantastic work from both of you!
On another note, do you have an estimated timeline for when the code of X-LLM will be available to the public?

@tensorboy
Hello！
We are currently busy with our doctor thesis defense and graduation-related matters. The code of X-LLM will be released as soon as possible within 1-2 weeks.
Thanks for your attention！

Sorry for that. We have already corrected the mistake and uploaded the latest version of the paper to arXiv.

@0nutation Thank you very much!


DPIA Screening for GitHub

User Need
Mandatory requirement for all tooling to have a DPIA Screening. GitHub doesn't have one.
Functional Requirements:

Complete DPIA Screening

Acceptance Criteria:

Screening submitted

Notes:

OneTrust Reference 9270


Making  fix for 2016.5.1

The classifier.yaml contains an array. So if it's an array set nc_settings to the first element. Mirroring changes made in this similar commit
https://github.com/puppetlabs/pltraining-rbac/commit/3ad787e3077fe7b14b2e8362a889bbbb74b8263d

@WhatsARanjit ^^ Can we cut a new release for this and updated the forge?


Some naphthalene SMARTS lead to a central bond with single bond order

Configuration:

RDKit Version: 2020.03.1
Operating system: Linux
Python version (if relevant): 3.6.2
Are you using conda? No
If you are not using conda: how did you install the RDKit? Schrodinger build.

Description:
When parsing a SMARTS for naphthalene, I'm surprised that one of the bonds is a single bond according to GetBondType():
In [71]: mol = Chem.MolFromSmarts('c1cccc(c12)cccc2')

In [72]: [b.GetBondType() for b in mol.GetBonds()]
Out[72]:
[rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.SINGLE,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC]

But note that the query still works, because the bond in question still matches single or aromatic:
In [73]: [b.DescribeQuery() for b in mol.GetBonds()]
Out[73]:
['SingleOrAromaticBond 1 = val\n',
 'SingleOrAromaticBond 1 = val\n',
 'SingleOrAromaticBond 1 = val\n',
 'SingleOrAromaticBond 1 = val\n',
 'BondOr\n  BondOrder 1 = val\n  BondOrder 12 = val\n',
 'SingleOrAromaticBond 1 = val\n',
 'SingleOrAromaticBond 1 = val\n',
 'SingleOrAromaticBond 1 = val\n',
 'SingleOrAromaticBond 1 = val\n',
 'SingleOrAromaticBond 1 = val\n',
 'SingleOrAromaticBond 1 = val\n']

It is curious that for this one bond, instead of using the SingleOrAromaticBond check, we use BondOrder 1 OR BondOrder 12 (where 12 means aromatic, so it works anyway).
With a different SMARTS representation without branching, the issue does not occur:
In [75]: [b.GetBondType() for b in Chem.MolFromSmarts('c1cccc2c1cccc2').GetBonds()]
Out[75]:
[rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC,
 rdkit.Chem.rdchem.BondType.AROMATIC]

This is not the worst thing in the world since, like I said, the query still works, but we had a program that was inspecting the bond orders from a SMARTS and this was confusing (we are only using simple bonds, nothing fancy like "single or double" or "double and not ring" or anything like that).

Hi Ivan,
There is a single bond in naphthalene- it’s the fusion bond. The 10 atom
envelope ring Is aromatic but the two 6 atom rings aren’t.
I don’t have a pen and paper to hand to check, but I don’t think your
second SMARTS is correct for naphthalene. I would write it (I think, I
haven’t checked) as c12ccccc2cccc1.
Dave
On Thu, 4 Jun 2020 at 20:06, Ivan Tubert-Brohman<EMAIL_ADDRESS>wrote:

Configuration:

RDKit Version: 2020.03.1
Operating system: Linux
Python version (if relevant): 3.6.2
Are you using conda? No
If you are not using conda: how did you install the RDKit?
Schrodinger build.

Description:
When parsing a SMARTS for naphthalene, I'm surprised that one of the bonds
is a single bond according to GetBondType():
In [71]: mol = Chem.MolFromSmarts('c1cccc(c12)cccc2')
In [72]: [b.GetBondType() for b in mol.GetBonds()]
Out[72]:
[rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.SINGLE,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC]
But note that the query still works, because the bond in question still
matches single or aromatic:
In [73]: [b.DescribeQuery() for b in mol.GetBonds()]
Out[73]:
['SingleOrAromaticBond 1 = val\n',
'SingleOrAromaticBond 1 = val\n',
'SingleOrAromaticBond 1 = val\n',
'SingleOrAromaticBond 1 = val\n',
'BondOr\n  BondOrder 1 = val\n  BondOrder 12 = val\n',
'SingleOrAromaticBond 1 = val\n',
'SingleOrAromaticBond 1 = val\n',
'SingleOrAromaticBond 1 = val\n',
'SingleOrAromaticBond 1 = val\n',
'SingleOrAromaticBond 1 = val\n',
'SingleOrAromaticBond 1 = val\n']
It is curious that for this one bond, instead of using the
SingleOrAromaticBond check, we use BondOrder 1 OR BondOrder 12 (where 12
means aromatic, so it works anyway).
With a different SMARTS representation without branching, the issue does
not occur:
In [75]: [b.GetBondType() for b in Chem.MolFromSmarts('c1cccc2c1cccc2').GetBonds()]
Out[75]:
[rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC,
rdkit.Chem.rdchem.BondType.AROMATIC]
This is not the worst thing in the world since, like I said, the query
still works, but we had a program that was inspecting the bond orders from
a SMARTS and this was confusing (we are only using simple bonds, nothing
fancy like "single or double" or "double and not ring" or anything like
that).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rdkit/rdkit/issues/3209, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGF2FSES3NBBOOI24BDSALRU7WBZANCNFSM4NS43CCA
.

--
David Cosgrove
Freelance computational chemistry and chemoinformatics developer
http://cozchemix.co.uk

The bond orders in molecules constructed from SMARTS are not always set to what you expect (I hesitate to use the word "correctly" since there's not really any such thing for these query molecules). It's kind of a "best guess" approach that we do in the hopes that you will be able to generate a SMILES for a molecule generated from SMARTS and get something sensible.
In this particular case that algorithm isn't doing the right thing.
Interestingly, if you use the SMARTS c1ccc2ccccc2c1 for napthalene everything works fine.
Marking this as a bug since we should be handling this case better.


Put directories at top of file listing when sorting by name

Issue Report Checklist

[☑] Searched the issues page for similar reports
[[☑] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[☑] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[☑] Could not reproduce inside jupyter qtconsole (if console-related)
[☑] Tried basic troubleshooting (if a bug/error)

[☑] Restarted Spyder
[☑] Reset preferences with spyder --reset
[☑] Reinstalled the latest version of Anaconda
[☑] Tried the other applicable steps from the Troubleshooting Guide

[☑] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
When sorting by name, directories are all mixed in with everything by name, which is different from the way most OS's do it, which is to have all the directories at the top (sorted by name) and then all files (also sorted by name). It may be best if this were some kind of setting you could change, since some people may also want it the way it is, but it would be nice if the directory-first setting were available somehow.
The way things are now is also kind of an eye strain because .py files, .pyc files, and folders are all small black icons which are difficult to differentiate from one another at a glance, although you do have the little ">" there to expand folders.
What steps reproduce the problem?

Open the "Files" pane
Sort by name
Folders are mixed in with files

What is the expected output? What do you see instead?

If sorted by name alphabetically, directories are first and then files.
If sorted reverse-alphabetically, you have files first and then directories.
Currently, the sorting behavior is correct for everything else - size, type, date modified. Only sorting by name differs from the usual.

 You have a valid point here.
Unfortunately, we are swamped at the moment, so we won't be able to address it in several months, perhaps a year. So, if you would like to see this fixed in the short term, we'd really appreciate your help with it. Otherwise, you'll have to wait for us.

I'm sure this is a one line fix - where is the relevant sorting routine
stored?
On Wed, May 5, 2021, 4:42 PM Carlos Cordoba @.***>
wrote:

Hey @battaglia01 https://github.com/battaglia01, thanks for reporting.
You have a valid point here.
Unfortunately, we are swamped at the moment, so we won't be able to
address it in several months, perhaps a year. So, if you would like to see
this fixed in the short term, we'd really appreciate your help with it.
Otherwise, you'll have to wait for us.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/15512#issuecomment-832993313,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHZFMQP2EYPUGXRUGVD7FLTMGUTNANCNFSM44D5HX2Q
.

Er, this is not at all easy to do, and is a much deeper problem with Qt's QFileSystemModel that many have talked about. See also:
https://forum.qt.io/topic/113138/sorting-folders-first-qfilesystemmodel-with-directory-filter
https://stackoverflow.com/questions/10789284/qfilesystemmodel-sorting-dirsfirst
https://stackoverflow.com/questions/20006775/how-to-sort-folders-above-files-with-qsortfilterproxymodel
Maybe if someone wants to do this, they can start there, but sheesh.


ajax capture stop working since 1.7.0

so, from what I test, version 1.6.5 and 1.6.8 are working fine with ajax but it stops working since 1.7.0.
I'm using jquery and it's pretty simple.
$.getJSON(url).done(function (resp) { })

my bad...
try 1.7.2

@recca0120 yep, it works now with 1.7.2. thanks!


RT-476: Feature/scd listing

Codecov Report

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

@@            Coverage Diff             @@
##             develop     #223   +/-   ##
==========================================
  Coverage           ?   97.12%
==========================================
  Files              ?       73
  Lines              ?     4492
  Branches           ?        0
==========================================
  Hits               ?     4363
  Misses             ?      129
  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 6ebad5d...c54e450. Read the comment docs.


Oauth Login

Using Flask Oauthlib

Twitter
GitHub
Google

@levlaz I would like to implement this feature. Is this issue taken ?

@acemaster It is not, please feel free to work on it! This is something that should go into the auth module. :)

@levlaz Cool :+1: I will post regarding the progress I am making

Thank you very much!

@levlaz I had a few doubts

For which all services do you want login, like Google, Facebook, Github etc.
Once logged in with oauth the user has to added in the db right. Should I use the existing model or create a new one?

Currently I am using keys from a test application I created on Google and Github.


Catch is not compatible with new showrss

When you put a new generated url from new.showrss Catch says that is not a valid URL.
For example:
http://showrss.info/user/40937.rss?magnets=true&namespaces=true&name=null&quality=sd&re=yes

Works for me, please make sure you're running the latest version.
I'm assuming that URL is fake because it gets a 404, but it is accepted by Catch.

Sorry, I'm afraid I'm stuck in older version 1.6 (old Mac supporting only 10.7.5) . Sorry for wasting you time.

Yeah, support for "new showrss" was added way after we dropped 10.7, sorry :(


Modify API clients to pass cache_discovery and cache parameters to BaseRepositoryClient from global_configs

Currently BaseRepositoryClient accepts the cache_discovery parameter, but it's defaulted to False with no way for a user of Forseti to change it.
We'd like to set it to True so that we don't have to make an HTTP request for discovery every time a new API client is created.
The new cache parameter is provided so that callers can provide their own cache implementation for use by googleapiclient. This is needed because googleapiclient relies by default on a cache provided by the (deprecated) oauth2client lib! We want to do API discovery caching without adding a dependency on a deprecated lib.
Thanks for opening a Pull Request!
Here's a handy checklist to ensure your PR goes smoothly.

[x] I signed Google's Contributor License Agreement
[x] My code conforms to Google's python style.
[x] My PR at a minimum doesn't decrease unit-test coverage (if applicable).
[x] My PR has been functionally tested.
[x] All of the tests pass.
[ ] I have submitted a corresponding PR for documentation in the forsetisecurity.org-dev branch and included this on this PR (if applicable).
[ ] My documentation has been functionally tested and used (if applicable).
[ ] I have submitted a corresponding PR in the Forseti Terraform module (if applicable).

These guidelines and more can be found in our contributing guidelines.

How will the config variables be set, will there be an additional change on the Terraform module?

Our code creates a BatchFirewallEnforcer and passes in the cache settings in the global_configs there. We don't use Terraform.

Please fix lint:

Fixed the lint errors... Sorry. When I run pylint on this it returns tons of existing issues. Do you know an easy way to filter it to changed code?


Fix version tag linting

the no-version-tag rule will not lint the zeebe:versionTag attribute anymore, the scenario of binding by version tag with Camunda <8.6 is covered by the no-binding-type rule; as a result there will only be one lint error instead of two for what's essentially the same problem

the new version-tag rule will lint version tags and report and report an error if they're empty

Related to https://github.com/camunda/camunda-modeler/issues/4519
Required by https://github.com/camunda/linting/pull/117

@philippfromme anything learning you can share with the team regarding design of "validation", based off this PR? Likely relevant for the future.

Released as v2.26.0.


repair Bootstrap popover

Latest Bootstrap throws an error if popover title is null. Replaced with an empty string.

🎁

🎁


change in names for parties - main name is from table column short_na…

change in names for parties - main name is from table column short_na…me, longer name  from column name

Fixed with PRs #143 and #144


[Fremennik Medium Diary] Add Between a Rock to general requirements list

The Fremennik Medium Diary requires the player to wear a gold helmet that is obtained during the Between a Rock quest. This is listed in the "Mine Gold" task, but not the overall requirements.

#1194 has fixed this issue, merged today.


add phpstan timeout option

adds an option to configure the phpstan timeout, see https://github.com/TomasVotruba/phpstan-bodyscan/issues/28
I'm having issues building this locally though... I'm getting the following errors on full-tool-build.sh:
`[ERROR] Could not process "/var/www/html/vendor/symfony/console/Command/LockableTrait.php" file, due to:
"System error: "Scope not available on "PhpParser\Node\Stmt\Expression" node, but is required by a
refactorWithScope() method of "Rector\DowngradePhp80\Rector\Expression\DowngradeMatchToSwitchRector" rule. Fix
scope refresh on changed nodes first"
Run Rector with "--debug" option and post the report here: https://github.com/rectorphp/rector/issues/new". On line: 25
[ERROR] Could not process "/var/www/html/vendor/symfony/service-contracts/ServiceSubscriberTrait.php" file, due to:
"System error: "Scope not available on "PhpParser\Node\Stmt\Expression" node, but is required by a
refactorWithScope() method of "Rector\DowngradePhp80\Rector\Expression\DowngradeMatchToSwitchRector" rule. Fix
scope refresh on changed nodes first"
Run Rector with "--debug" option and post the report here: https://github.com/rectorphp/rector/issues/new". On line: 25
[ERROR] Could not process "/var/www/html/vendor/symfony/service-contracts/ServiceLocatorTrait.php" file, due to:
"System error: "Scope not available on "PhpParser\Node\Expr\Array_" node, but is required by a
refactorWithScope() method of "Rector\DowngradePhp81\Rector\Array_\DowngradeArraySpreadStringKeyRector" rule.
Fix scope refresh on changed nodes first"
Run Rector with "--debug" option and post the report here: https://github.com/rectorphp/rector/issues/new". On line: 25
[ERROR] Could not process "vendor/symfony/console/Tester/ApplicationTester.php" file, due to:
"Analyze error: "Class PHPStanBodyscan202407\Symfony\Component\Console\Tester\ApplicationTester was not found
while trying to analyse it - discovering symbols is probably not configured properly.". Include your files in
"$rectorConfig->autoloadPaths([...]);" or "$rectorConfig->bootstrapFiles([...]);" in "rector.php" config.
See https://github.com/rectorphp/rector#configuration".
[ERROR] Could not process "vendor/symfony/console/Tester/CommandTester.php" file, due to:
"Analyze error: "Class PHPStanBodyscan202407\Symfony\Component\Console\Tester\CommandTester was not found while
trying to analyse it - discovering symbols is probably not configured properly.". Include your files in
"$rectorConfig->autoloadPaths([...]);" or "$rectorConfig->bootstrapFiles([...]);" in "rector.php" config.
See https://github.com/rectorphp/rector#configuration".`
On executing the binary the following error occurs:
PHP Fatal error:  Uncaught Error: Class "PHPStanBodyscan202407\Illuminate\Container\Container" not found in /var/www/html/src/DependencyInjection/ContainerFactory.php:17
Any idea?

not sure how this works, do I need to do something to trigger the ci again?

@npo-mmenke Its Github's default once you contribute a new repository first time. Not very helpful though https://github.com/orgs/community/discussions/14334
I have to basically confirm everytime you push a commit. Once we merge something, you'll be verified as "known user" and CI will run automatically :)

anything else you need from me here?

Looks good, thanks 👍


Fix the paths to transformer.cjs documented in the README

I could not get the documented CJS-oriented configuration changes to work without prefixing the svelte-jester/dist/transformer.cjs path with ./node_modules. If this is an invalid suggestion, let me know and I can remove that part of the change (or feel free to reject the pull request altogether).
The other part of this change is a small indentation adjustment under the Installation --> TypeScript --> ESM version heading that causes the rendering of the README on the NPM registry to be buggy:

You are correct, thanks for trying it out


Silently failing login when no network connection

Cannot handle network exceptions on signin, just like https://github.com/firebase/FirebaseUI-Android/issues/164
Step 2: Describe your environment

Android device: Emulator
Android OS version: 10
Google Play Services version: _____
Firebase/Play Services SDK version: _____
FirebaseUI version: 6.2.0, 6.2.1

Step 3: Describe the problem:
When the user tries to login without an internet connection, firebaseUI fails silently and there's no feedback to the user, nor a return to onActivityResult like other errors in the signin process, where based on an error code we could give the proper feedback to the user
The app actually doesn't crash, which might be different from #164 . The error is just in logcat but there's no way to return control to the main app where we could handle the error by (e.g.) showing a message to the user
Steps to reproduce:

Disable network connection
Try to login using email-link (that's what I use and I can't test with email/password but it might have the same problem)

Observed Results:

Logcat shows

E/AuthUI: A sign-in error occurred.
    com.google.firebase.FirebaseNetworkException: A network error (such as timeout, interrupted connection or unreachable host) has occurred.
        at com.google.firebase.auth.api.internal.zzeh.zza(com.google.firebase:firebase-auth@@19.3.1:15)
        at com.google.firebase.auth.api.internal.zzfo.zza(com.google.firebase:firebase-auth@@19.3.1:21)
        at com.google.firebase.auth.api.internal.zzfe.zza(com.google.firebase:firebase-auth@@19.3.1:33)
        at com.google.firebase.auth.api.internal.zzfg.zza(com.google.firebase:firebase-auth@@19.3.1:74)
        at com.google.firebase.auth.api.internal.zzen.zza(com.google.firebase:firebase-auth@@19.3.1:18)
        at com.google.android.gms.internal.firebase_auth.zza.onTransact(com.google.firebase:firebase-auth@@19.3.1:13)
        at android.os.Binder.execTransactInternal(Binder.java:1021)
        at android.os.Binder.execTransact(Binder.java:994)

Expected Results:

An error message
or
FirebaseUI to return to the calling activity with a proper error code in onActivityResult()

@theHilikus thanks for reporting this.  We should have standard error handling behavior for network errors but looks like we might have missed a spot.

This issue is fixed and released in version 6.3.0.


Statically import core.stdc.stdlib in the test runner

Silence deprecations warnings that were triggered by the change of behaviour in imports.
Current output:
d_do_test.d(287): Deprecation: module core.stdc.stdlib is not accessible here, perhaps add 'static import core.stdc.stdlib;'
d_do_test.d(289): Deprecation: module core.stdc.stdlib is not accessible here, perhaps add 'static import core.stdc.stdlib;'
d_do_test.d(287): Deprecation: package core.stdc is not accessible here
d_do_test.d(287): Deprecation: module core.stdc.stdlib is not accessible here, perhaps add 'static import core.stdc.stdlib;'
d_do_test.d(289): Deprecation: package core.stdc is not accessible here
d_do_test.d(289): Deprecation: module core.stdc.stdlib is not accessible here, perhaps add 'static import core.stdc.stdlib;'

Auto-merge toggled on


Feature Suggestions

Adding greyscale inverse can be useful for roughness <-> smoothness maps
A color picker for creating a solid color channel.
A label to hint the internal shader's channel representation. Or better, creating some preset with corresponding labels for that.

Thanks for the suggestion ! I also plan to turn this into a package for easier integration with latest versions (2019 and above)


Consider Unix programming

@danghai What do you mean with unix programming ?

I mean using python to handle some issue relates to path, IO file, thread, process, Operating system, network, ...


Discuss how to deal with table items that start with a space

I think the table eats up those extra spaces, but we may need them. I'm not sure it's as simple as putting quotes around table items - could someone need a value that includes surrounding quotes?

Taken over by #214


Change permissions probably doesn't work for PotentialUsers

Just when inspecting the code - I don't see a code path for changing the permissions of Potentialusers.
Now, we might decide that it isn't possible to change the permissions of potential users (I don't have a complaint with that) - but in that case I imagine we need some UI stuff preventing it too.

This is in the context of release user participant right?
Seems to be there and it is working as expected if we allow to edit the potential-user.
https://github.com/umccr/elsa-data/blob/c0e88a1a358570e16230191b8bc85e8a0134e013/application/backend/src/business/services/release-participation-service.ts#L237C4-L237C4

I think I was looking at the "non release" user API i.e. change user permissions. And I guess that is fine because we never want to grant permissions to PotentialUsers - until they become an actual user.
Thanks for checking.


Improvement on lineage with airflow dags

Is your feature request related to a problem? Please describe.
Usually, airflow DAGs can have several tasks, where each task originates a table in your datalake. For example, a task named (A) reads data from Kafka source and saves it in the raw layer as a bronze table. Task (B) reads the bronze table, performs data transformations and returns the silver table. Finally, task C reads the silver data, performs some aggregations and returns a gold.
In short, allow in the edge pipeline editor make reference to a DAG task.
Describe the solution you'd like
Allow in the edge pipeline editor make reference to a DAG task.

Yeah, I would like that too.
Our tasks (usually stored procedures) work with a decent number of tables. No division into tasks... so our pipeline's lineages mostly looks like this :/

In my opinion, if the tables, when they reach a certain number, were hidden, breaking up according to the schemes, it would be great.


when the full codel will be released?

Thank you for the great Job.
when the full code will be released?

Thanks for your patience! The full code is released.


Benchmark AndroidX bespoke collections vs JS built-in collections

I suspect we're wasting a lot of cycles on these collections which help the JVM and native, but which hurt JS due to Long boxing and being user code vs intrinsics. Benchmark them on QuickJS and Node, and if the built-in ones are better let's send a PR to AndroidX to make the custom impls non-JS only.
In the JS I see scatter map and set, int int map and set, and int object map. Let's check 'em all.

Benchmarked and started a whole bunch of PRs to upstream repos.


FireTV playback sensor

Your Device
FireTV (3rd gen)
App Name
Kodi for the media session
Kodi for audio session
audio.txt
media_session.txt

Duplicate issues #81


Fix for RuntimeError on second local pipeline run on py3.7

On my mac on py3.7 I get RuntimeError('context has already been set')
when multiprocessing.set_start_method('fork') is run during the the second
pipeline run (the first is fine).
Debugging middleware caught exception in streamed response at a point where response headers were already sent.
Traceback (most recent call last):
  File ".venv/lib/python3.7/site-packages/werkzeug/wsgi.py", line 507, in __next__
    return self._next()
  File ".venv/lib/python3.7/site-packages/werkzeug/wrappers/base_response.py", line 45, in _iter_encoded
    for item in iterable:
  File "packages/data-integration/data_integration/ui/run_page.py", line 108, in process_events
    for event in execution.run_pipeline(pipeline, nodes, with_upstreams):
  File "packages/data-integration/data_integration/execution.py", line 45, in run_pipeline
    multiprocessing.set_start_method('fork')
  File "/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/context.py", line 242, in set_start_method
    raise RuntimeError('context has already been set')

The fix is to only set the start methog if this is not set to that value.

will do


Fix aws s3 startup check preventing keydb from starting

During startup, when db-s3-object is set, keydb can't start and gets into error
"could not access s3 bucket"

Thanks for the catch, didn't realize execlp needed to have a nullptr passed as the last argument.


fix: save checked full color picker between renders

Description
Save switch value for full color picker when switching between primary and background colors
PR fixes following issue(s)
Fixes #26960
Media
https://github.com/appsmithorg/appsmith/assets/11555074/53ef8c11-beae-4ade-b441-80ac39b82a8a
Type of change

Bug fix (non-breaking change which fixes an issue)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[ ] JUnit
[ ] Jest
[x] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/build-deploy-preview env=release

/ok-to-test

/ok-to-test


phpfpm: allow configuring PHP package per-pool

all props to @4levels
Motivation for this change
This allows choosing the PHP version for a PHPFPM pool so that you can run multiple versions per system.
I took the work done by @4levels (see the discussion) and combined it into this PR.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Hi @wmertens,
Thanks for this!
I never created a PR for this as this is imo a backward incompatible change. Can you work your magic and add a compatibility update so that this won't break existing configurations when people don't need to specify a custom phpPackage?
Thanks!

Actually, I think it's backwards compatible. The only that changes is the intermediate representation of the php config, and that's only used in the file itself. The PHP package defaults to the phpfpm-configured package, so that should be ok too…

anyway it seems I broke eval ;) fixing

Hi @wmertens,
Are you sure? I was forced to adjust my phpFpm configurations due to the new nested config attribute. I failed to use the passed set as the config if no config attribute if no config attribute exists, hope this still makes sense :wink: pm me if it doesn't

Hmm indeed it might be not compatible. I'll need to do some tests.

Ok I finally realized what's wrong with this: the poolConfigs attribute is used directly in places, and it's a literal string.o
To fix it, I'll combine it in a separate attribute, so it can stay a string.

Hi @wmertens,
That's exactly what I was trying to explain before, glad you figured it out ;-)
I was kind of hoping the poolConfig could be a string or an attribute set to keep bc compatibility, and would be converted to an attribute set ONLY if it was passed as string (instead of the expected set).
Thanks again for looking into this!
Erik aka 4levels

I now realize that there is no /nixos/tests for phpfpm. I'll see about adding one.

Oh yeah that issue is still there… second try.
@GrahamcOfBorg build nixosTests.nextcloud

Success on aarch64-linux (full log)
Attempted: nixosTests.nextcloud
Partial log (click to expand)
nextcloud: exit status 0
test script finished in 192.87s
cleaning up
killing client (pid 631)
killing nextcloud (pid 644)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/z0gzsisgd983qm4z6s58wgfypi5n8jdp-vm-test-run-nextcloud-basic
/nix/store/51myk7pgmvwdkga4dbbls3gq2rnyj09d-vm-test-run-nextcloud-with-mysql-and-memcached
/nix/store/jn3rjgrz1l2a4q7vvwkzdf6b5bkqd4gi-vm-test-run-nextcloud-with-postgresql-and-redis

Success on x86_64-linux (full log)
Attempted: nixosTests.nextcloud
Partial log (click to expand)
nextcloud: exit status 0
test script finished in 47.46s
cleaning up
killing client (pid 597)
killing nextcloud (pid 609)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/bhpqbb31w84z7f95c84y0wp6mwfwmxkw-vm-test-run-nextcloud-basic
/nix/store/5b6g38wlb72v3vf6xs53c06aib4khr5j-vm-test-run-nextcloud-with-mysql-and-memcached
/nix/store/sg53sjrbl53sk1ldsggyp0n0j8vk4hi3-vm-test-run-nextcloud-with-postgresql-and-redis


Slow UI

Hi,
Could we get some performance work on the UI, we have about 300 services coming from consul, and when I open the UI, it takes a long time to load and its just really slow when i click around.
Kristian

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.
I have to close this one because of its lack of activity :disappointed:
Feel free to re-open it or join our Slack workspace for more community #support.


chore(deps): update terraform terraform-ibm-modules/base-ocp-vpc/ibm to v3.15.0

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/base-ocp-vpc/ibm (source)
module
minor
3.14.4 -> 3.15.0

Release Notes

terraform-ibm-modules/terraform-ibm-base-ocp-vpc (terraform-ibm-modules/base-ocp-vpc/ibm)
v3.15.0
Compare Source
Features

Added support to attach additional security groups to the worker pools, VPE and load balancers.

See Advanced Security Group Options for details. An example of usage is provided at Attaching custom security groups example

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.0.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Multiple bidders with the same adapter

Is it possible to have multiple bidders with the same ad-network adapter?
Description of the problem:
We'd like to implement two separate sellers for our inventory, but both of them are technically using the same system for serving ads and therefore both of them should use the same adapter. How is it possible to distinguish them and have them both compete in the same time?
Correct me if I'm wrong, but to my understanding setting a bidder name also sets the adapter to be used.
Thanks a lot.

You should just call the same bidder twice with the specific settings
{
    bidder: "mybidder",
    params: {
        placement: 1111111
},
{
    bidder: "mybidder",
    params: {
        placement: 22222
}

Thank you for your reply! However with this approach it will not be possible to distinguish the bidders in DFP reports. Is there a way to send another key value or something to mark the bidder's name in DFP along with it?

@gavoc you could alias the second bidder - see http://prebid.org/dev-docs/publisher-api-reference.html#module_pbjs.aliasBidder
You may need to add additional key values for the new bidder name depending on your DFP setup (max 20 chars)
pbjs.aliasBidder('mybidder', 'myotherbidder');

{
    bidder: "mybidder",
    params: {
        placement: 1111111
    }
},
{
    bidder: "myotherbidder",
    params: {
        placement: 22222
    }
}

hb_bidder_myotherbid

Awesome! I didn't notice aliases before. This solves everything.
@aneuway2 thank you very much for your time!
(closing the thread since it had been solved)


update readme

Added explanation on how to provide options to the tasks.
I mistakenly tried to run: task: 'default --verbose' or tasks: ['default --verbose'] which did not work. Options need to be provided as separate elements in the tasks array.

It's not tasks: 'string' but task: ''string, or tasks: ['string', 'string']`

Yea, my earlier commit message had a typo, sorry about that. I updated it. task: 'default --verbose' and tasks: ['default --verbose']  do not work and cause grunt to not be able to find the task. The current readme doesn't explain this.
task: 'default --verbose' results in error. You understandable cant do anything about that case.
tasks: ['default --verbose'] also results in an error (at least on windows).
However tasks: ['default', '--verbose'] does work (and was not immediately apparent since --verbose isn't exactly a task.)


Coordinate Pretested Integration Plugin (PIP) features with git-phlow

How can we coordinate features done in git-phlow or/and PIP is only done once? And that they are coordinated to work in the same way?
Do we have an overview on differences?
Should we consider using git-phlow agent underneath PIP?

As far as I understand this is the highlander from the discussion on slack. This tool or package should be the standard for how pretested integration works and is implemented across the board.
We need a longer discussion about this and what our vision is


Update ValidatesRequests

Allow to only pass the rules to the validation method.
$this-validate([
    'body' => 'required'
]);

Without passing the $request every time.

Then just do $request->validate([ .. ]);

@brunogaspar it could be too!

Thanks @socieboy  but 5.3 is not supported anymore, also it's not right to use the request component in the validation component like this.


SSH Environment does not match app environment

When an app runs it has it's HOME set to /home/vcap/app and all of the files in /home/vcap/app/.profile.d are sourced in order to set up the expected environment.
When a user SSH's to the same app container, the HOME is set to /home/vcap and none of the .profile.d files are sourced.
This means that tenants are unable to load installed libraries, run management commands, or really do anything with the app in the container unless they fix this first. Tenants can be instructed to run export HOME=/home/vcap/app; for f in ~/.profile.d/*; do source $f; done when they first connect, but I do not feel this should be necessary.

There is some context as to why this is the case here: http://cf-dev.70369.x6.nabble.com/cf-dev-In-Diego-maybe-DEA-also-why-is-HOME-home-vcap-app-and-not-home-vcap-td4802.html

tl;dr; the launcher is responsible for setting the home env variable and sourcing in files in .profiles.d. we thought about using the launcher to start the ssh process. the tricky part is ensuring that the .profiles.d files are idempotent and won't be destructive to execute multiple times. since we cannot guarantee that, we held back on making this change. we are open for suggestions though

For reference, the HOME var is set using the diego SSH daemon by copying it from the existing environment the daemon is running in.
Are you aware of any buildpacks where the .profiles.d files are not idempotent, or is this a theoretical concern?

Update: I had a cursory glance over all the core buildpacks and couldn't find any that had non-idempotent .profile.d's, most of them don't use it at all. I presume the concern is that they might be supplied by tenants?

that's correct, it is just a theoretical concern since there's no way to enforce that restriction on custom buildpacks.

@jvshahid Would an alternative solution be to simply document that .profile.d scripts must be idempotent? This assumes that no known existing buildpacks exhibit that behaviour.

Thanks for asking about this, @Jonty. That solution sounds like a behavioral restriction for buildpacks that would be most appropriate for @sclevine, the PM of the  Buildpacks, to address. It would likely also be appropriate to apply the same restriction to the optional app-provided .profile file that will be sourced after any .profile.d files, as that too may set up environment important to the deployed CF application process. Given the general guideline that CF attempts to be compatible with Heroku buildpacks, that may not be a reasonable restriction to enforce given the currently documented contract for .profile.d and .profile scripts.
In the meantime, this environmental discrepancy is noted in the CF documentation at http://docs.cloudfoundry.org/devguide/deploy-apps/ssh-apps.html#ssh-env, along with manual steps to take to set up the environment to match that of the app processes. Also, although it does depend on current implementation details of how applications are run in containers, if you are certain for a particular app that it is safe to run the buildpack and app profile scripts repeatedly, you can run cf ssh APP_NAME -t -c '/tmp/lifecycle/launcher app bash ""' to start an interactive session with the same starting environment as the app processes.
More broadly, it sounds like we would want the capability to run one or more commands with the environment variables captured from an earlier stage of setup. We could use that capability to run the app start command and the SSH server simultaneously with the environment set up by the profile scripts. I have some initial ideas about how we might be able to achieve that through a receipt file inside the container filesystem. I'll discuss the feasibility of that approach with the Diego team and with the Greenhouse team, as it would be important for the same invocation flow to work on Windows cells as well as on Linux cells.
Thanks,
Eric

Thanks @ematpl, please do keep this issue updated with any progress.
I noticed the docs you linked to were slightly incorrect and would lead to partial environment setup for some buildpacks, I've filed a PR to fix them: https://github.com/cloudfoundry/docs-dev-guide/pull/152

you can now get the app environment by running /tmp/lifecycle/shell from within your app ssh session


Add config entry for AirVisual

Breaking change

The config schema for AirVisual has changed; users who configure AirVisual via configuration.yaml will need to update. Additionally, in order to protect the AirVisual cloud API, scan_interval is no longer configurable for this integration.
Proposed change

This PR adds a config entry for AirVisual. It does not include config options; that will come in a future PR.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[x] New feature (which adds functionality to an existing integration)
[x] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
airvisual:
  api_key: !secret airvisual_api_key

Additional information

This PR fixes or closes issue: N/A
This PR is related to issue: N/A
Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/12166

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist
[x] The code has been formatted using Black (black --fast homeassistant tests)
[x] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

[ ] No score or internal
[ ] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

@Kane610 Anything else you want to see here?

Thanks, @MartinHjelmare. I’m out of the country for a week; I’ll take care of these notes when I return.


Autosuggest of 'this' not working on anonymous function

I've included the extra promise/async syntax to reproduce the exact scenario I have. Probably doesn't work in simpler scenarios.
class foo {

   constructor(private bar){}

    async test() {
        return await new Promise(async (resolve, reject) => {
           var a = (await bar.someAsyncMethod()).someResult;
        });
    }
}

Autosuggest does not suggest that bar use this.bar... it just says cannot find name 'bar'

@mjbvz probably worth showing you this one too

Thanks. Opened https://github.com/Microsoft/TypeScript/issues/23580 to track this upstream


Fixed some minor typos

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:

Diff has 236 changes from multiple authors? :thinking:
It looks like this was caused by branching off of dev, but setting target branch to master.


MAC vendor string for known devices.

Description: Add the MAC vendor string to known device entry to easier identify devices found through device trackers.
This pullrequest adds a feature to device trackers. It will try to find the vendor string for a MAC address in a local IEEE OUI database (using the netaddr python library).
This will make it easier to identify found devices in the known_devices.yaml file as you can now distinguish between for example a Raspberry Pi, server, Apple phone, Android phone, etc.
An example of how the output now looks:
b827eb000000:
  hide_if_away: false
  mac: B8:27:EB:00:00:00
  name: b827eb000000
  picture:
  track: true
  vendor: Raspberry Pi Foundation

This pull request includes some changes related to isort and a fix for a bug that seems to present on the dev branch as well https://travis-ci.org/home-assistant/home-assistant/jobs/176031122
I am pitching this PR as an feature proposal. If needed I can pull the isort related changes out into a separate branch. The isort related changes basically make sure the standards set for this project (by: https://github.com/home-assistant/home-assistant/pull/1330 and Pylint) are available for other tools like IDE's or texteditors.
Checklist:
If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

@aequitas can you please rebase this and fix the merge conflicts to get it in a mergeable shape?

Question: As an extra bonus, would it be possible to automatically set the icon/picture for the discovered device (if none manually set by the user) based on the vendor? E.g. "mdi:cellphone-android" for Android devices, "mdi:cellphone-iphone" for IPhone, "mdi:raspberrypi" etc. (not sure if related to https://github.com/home-assistant/home-assistant/pull/3974)

@molobrakos that could be a nice addition. We would need to create a lookup list for that I think.
For some devices it might work. But for example for Apple you don't know if it would be a phone or a laptop. Or for LG if it is a phone or TV. Maybe manufacturers uses a different OUI for each device type? But that is something that has to be investigated.

@SEJeff rebased, waiting for the tests to pass.

@molobrakos maybe you could open an issue for that RFE and reference this PR? That would be a neat enhancement, but we wouldn't want to go too crazy.

This should not have been merged before our pending release in a couple of
hours!
I'm also not convinced that adding a dependency for helping people identify
their device is worth it. I rather link them to a page in the docs.
On Sat, Nov 19, 2016, 07:53 Jeff Schroeder<EMAIL_ADDRESS>wrote:

Merged #4401 https://github.com/home-assistant/home-assistant/pull/4401.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/4401#event-865371826,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYJ2l26wlt2LcmjHdqUvB9CwfDGIGqSks5q_xuFgaJpZM4KyhQP
.

I have for now removed the commit from dev and would like to re-open discussion.

@balloob should I open a new PR in that case or is there a way to reopen this one?
What would a page in the docs look like? In my opinion having the device names in the known_devices.yaml is best for user experience. As you can quickly identify entries without having to go back and forth between the the file and a tool so search mac vendors.
Instead of having netaddr as dependency we might consider including the OUI file into HA itself (like netaddr does https://github.com/drkjam/netaddr/tree/rel-0.7.x/netaddr/eui), as it is the only part of netaddr that is being used in this case, it can be found here: http://standards-oui.ieee.org/oui.txt
Whats your thoughts?

That file is 3.4MB. That's just too much to include for such a relative minor enhancement. What about we use something like this ? https://macvendors.com/api

Sorry didn't consider that. The API looks like a good solution, they seem to offer it for free. Would be easy enough to refactor to this. If you think the feature is worth including this way I will spend some more time on it.

Yes, using the API is 👍


[QUESTION] Making rocket land in specific area of space station?

So I built a rocket bay on my space station and it's where I'd like my rocket to land, but I can't figure out how to force it to land on the specific coordinates of the space station. I've tried messing around with the ID chip while on the station as well as tried to set it up with a station docking port(It says on the wiki you're supposed to keep the chip when adding a module to a space station? Mine gets eaten every time, though I've been good about keeping extras)
I just want my rocket to land in the room I made for it, and not on top of my Astral Sorcery celestial gateway room every time, how can I get it to land where I want it to?
Heck if there's some unknown wiki link I don't know about, tell me that too, but I checked the space station page, the space station assembler page, the id chips page and a few others, following what I read but still getting stuck.

Re: chip eating. That's intentional as it was causing duplication bugs the other way and it makes more logical sense for it to eat the chip. Copy chips in the satellite builder.
Re: docking. Use the landing pad (looks like an all-border concrete block) and explicitly select it in the station ID chip.

How do I select it with the ID chip? Do I just right click? Because I swear I tried to right click it with no result.

Should be I think shift-rightclick to open the UI.

I tried a shift + right click at the landing pad and tried to save as a new one while on the station, it didn't save the coordinates at all, it just did nothing.

But yeah, I've tried shift + right clicking and clicking add new, works fine on the overworld but on my space station it does nothing at all, clicking the other options also doesn't get rid of a "last" coordinate either if one is there, but it doesn't matter if the last coords are there or not, it won't add the new coords regardless of how many times I shift+right click the launch pad and click "add new"

You should be able to specifically select a placed pad block on the station.

https://imgur.com/a/UtDWUcX
I've tried the single launch pad tile as well as a 3x3 launch pad(I've a 3x3 rocket), no option to select the launch pad on the station shows up.
I know enigmatica 2 expert is still on build 250, not sure if this is a build 250 bug that was fixed in a later build, or if I'm just so dense I can't figure it out.

Once again, I am dumb, I got the launch pad mixed with the docking pad, my bad.
I wholeheartedly apologize for wasting your time.