fastlane deliver: Potential server error received: 'Unexpected Error'

New Issue Checklist

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

Issue Description
I'm seeing a strange server error whenever I try to push screenshots up to itc.  I've got a whole bunch of screens taken, as near as I can tell my directory structure looks correct, but things bomb out once we get to the uploading step.
Command executed
fastlane deliver --verbose
Complete output when running fastlane, including the stack trace and command used
➜  XXXXXXX git:(ios13) ✗ fastlane deliver --verbose                                                                                [7:08:52 PM]
[✔] 🚀
[19:08:54]: fastlane detected a Gemfile in the current directory
[19:08:54]: However, it seems like you didn't use `bundle exec`
[19:08:54]: To launch fastlane faster, please use
[19:08:54]:
[19:08:54]: $ bundle exec fastlane deliver --verbose
[19:08:54]:
[19:08:54]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
Successfully loaded Appfile at path '/Users/XXXXXXX/Documents/XXXXXXX/fastlane/Appfile'
- app_identifier: 'XXXXXXX'
- apple_id: 'XXXXXXX'
- itc_team_id: 'XXXXXXX'
- team_id: 'XXXXXXX'
-------
INFO [2020-06-16 19:08:56.67]: Successfully loaded '/Users/XXXXXXX/Documents/XXXXXXX/fastlane/Deliverfile' 📄

+-----------------------------------+-----------+
| Detected Values from './fastlane/Deliverfile' |
+-----------------------------------+-----------+
| force                             | true      |
| overwrite_screenshots             | true      |
| skip_binary_upload                | true      |
| skip_metadata                     | true      |
| skip_screenshots                  | false     |
| precheck_include_in_app_purchases | false     |
| run_precheck_before_submit        | false     |
+-----------------------------------+-----------+

INFO [2020-06-16 19:08:56.68]: Login to App Store Connect (XXXXXXX)
Reading keychain entry, because either user or password were empty
Loading session from '/Users/XXXXXXX/.fastlane/spaceship/XXXXXXX/cookie'
Looking for App Store Connect Team with ID XXXXXXX
INFO [2020-06-16 19:08:58.13]: Login successful

+--------------------------------------+-----------------------------+
|                      deliver 2.149.1 Summary                       |
+--------------------------------------+-----------------------------+
| screenshots_path                     | ./fastlane/screenshots      |
| metadata_path                        | ./fastlane/metadata         |
| username                             | XXXXXXX           |
| app_identifier                       | XXXXXXX |
| platform                             | ios                         |
| edit_live                            | false                       |
| use_live_version                     | false                       |
| skip_binary_upload                   | true                        |
| skip_screenshots                     | false                       |
| skip_metadata                        | true                        |
| skip_app_version_update              | false                       |
| force                                | true                        |
| overwrite_screenshots                | true                        |
| submit_for_review                    | false                       |
| reject_if_possible                   | false                       |
| automatic_release                    | false                       |
| phased_release                       | false                       |
| reset_ratings                        | false                       |
| team_id                              | XXXXXXX                      |
| dev_portal_team_id                   | XXXXXXX                  |
| run_precheck_before_submit           | false                       |
| precheck_default_rule_level          | warn                        |
| individual_metadata_items            | []                          |
| ignore_language_directory_validation | false                       |
| precheck_include_in_app_purchases    | false                       |
+--------------------------------------+-----------------------------+

INFO [2020-06-16 19:09:02.14]: Starting with the upload of screenshots...
INFO [2020-06-16 19:09:02.14]: Removing all previously uploaded screenshots...
[⠴] Activating languages de-DE, en-US, es-ES, fr-FR, it, ja, ko, zh-Hans, zh-Hant... Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
[⠦] Activating languages de-DE, en-US, es-ES, fr-FR, it, ja, ko, zh-Hans, zh-Hant... Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 1)...
[⠇] Activating languages de-DE, en-US, es-ES, fr-FR, it, ja, ko, zh-Hans, zh-Hant...
Looking for related GitHub issues on fastlane/fastlane...
Search query: The request could not be completed because:
	Unexpected Error

URL: https://api.github.com/search/issues?q=The%20request%20could%20not%20be%20completed%20because%3A%0A%09Unexpected%20Error+repo:fastlane/fastlane
[⠙] Activating languages de-DE, en-US, es-ES, fr-FR, it, ja, ko, zh-Hans, zh-Hant... ➡  [upload_to_app_store] #<ArgumentError: different prefix: "/" and "fastlane">
    https://github.com/fastlane/fastlane/issues/16317 [closed] 4 💬
    2 weeks ago

➡  Fastlane trying to access my photos?!
    https://github.com/fastlane/fastlane/issues/15768 [closed] 6 💬
    05 Apr 2020

➡  Fastlane Upload : Unexpected Error
    https://github.com/fastlane/fastlane/issues/14214 [closed] 12 💬
    01 Aug 2019

and 19 more at: https://github.com/fastlane/fastlane/search?q=The%20request%20could%20not%20be%20completed%20because%3A%0A%09Unexpected%20Error&type=Issues&utf8=✓

🔗  You can ⌘ + double-click on links to open them directly in your browser.
Traceback (most recent call last):
	21: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `<main>'
	20: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `eval'
	19: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/fastlane:23:in `<main>'
	18: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/fastlane:23:in `load'
	17: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/bin/fastlane:23:in `<top (required)>'
	16: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in `take_off'
	15: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:17:in `start'
	14: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:183:in `run'
	13: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	12: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	11: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	10: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	 9: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	 8: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:80:in `block (2 levels) in run'
	 7: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:38:in `run'
	 6: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:121:in `upload_metadata'
	 5: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/upload_screenshots.rb:43:in `upload'
	 4: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/app_version.rb:412:in `save!'
	 3: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:463:in `update_app_version!'
	 2: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:1553:in `with_tunes_retry'
	 1: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:470:in `block in update_app_version!'
/Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:228:in `handle_itc_response': Unexpected Error (Spaceship::Tunes::PotentialServerError)
	21: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `<main>'
	20: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `eval'
	19: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/fastlane:23:in `<main>'
	18: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/bin/fastlane:23:in `load'
	17: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/bin/fastlane:23:in `<top (required)>'
	16: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in `take_off'
	15: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:17:in `start'
	14: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:183:in `run'
	13: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	12: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	11: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	10: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	 9: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	 8: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:80:in `block (2 levels) in run'
	 7: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:38:in `run'
	 6: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:121:in `upload_metadata'
	 5: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/deliver/lib/deliver/upload_screenshots.rb:43:in `upload'
	 4: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/app_version.rb:412:in `save!'
	 3: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:463:in `update_app_version!'
	 2: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:1553:in `with_tunes_retry'
	 1: from /Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:470:in `block in update_app_version!'
/Users/XXXXXXX/.rvm/gems/ruby-2.6.5/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:228:in `handle_itc_response': [!] The request could not be completed because: (Spaceship::Tunes::PotentialServerError)
	Unexpected Error
Time: 0h:00m:32s

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.5

Ruby
2.6.5

Bundler?
false

Git
git version 2.24.3 (Apple Git-128)

Installation Source
~/.rvm/gems/ruby-2.6.5/bin/fastlane

Host
Mac OS X 10.15.5 (19F101)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.6.5/lib

OpenSSL Version
OpenSSL 1.1.1d  10 Sep 2019

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
11.5

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do

  desc "lol screenshots"
  lane :screens do
    capture_ios_screenshots(
      dark_mode: true,
      clear_previous_screenshots: true,
    )

    capture_ios_screenshots(
      dark_mode: false
    )

  end

  desc "Push a new beta build to TestFlight"
  lane :beta do
    enable_automatic_code_signing
    get_certificates

    build_app(scheme: "xxxx",
      export_xcargs: "-allowProvisioningUpdates",
      export_options: {
        method: "app-store",
        provisioningProfiles: {
        }
      }
    )
    # build_app
    upload_to_testflight(changelog: "changelog")
  end
end

`./fastlane/Appfile`
app_identifier("com.xxxxx.xxxxx") # The bundle identifier of your app
apple_id("xxxxx") # Your Apple email address

itc_team_id("xxxxx") # App Store Connect Team ID
team_id("xxxxx") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.149.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

executable-hooks
1.6.0

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday
0.17.3

faraday_middleware
0.13.1

fastimage
2.1.7

gh_inspector
1.1.3

multi_xml
0.6.0

rubyzip
1.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

bundler
2.1.0

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

httpclient
2.8.3

google-api-client
0.38.0

emoji_regex
1.0.1

jmespath
1.4.0

aws-eventstream
1.0.3

aws-sigv4
1.1.1

aws-sdk-core
3.92.0

aws-sdk-kms
1.30.0

aws-sdk-s3
1.61.1

nanaimo
0.2.6

colored2
3.1.2

claide
1.0.3

CFPropertyList
3.0.2

atomos
0.1.3

xcodeproj
1.15.0

unicode-display_width
1.7.0

tty-screen
0.7.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.3

excon
0.73.0

json
2.3.0

mini_magick
4.10.1

naturally
2.2.0

simctl
1.6.8

multi_json
1.14.1

signet
0.13.2

os
1.0.1

memoist
0.16.2

googleauth
0.11.0

digest-crc
0.5.1

google-cloud-errors
1.0.0

google-cloud-env
1.3.1

google-cloud-core
1.5.0

google-cloud-storage
1.25.1

aws-partitions
1.289.0

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

zlib
1.0.0

mini_portile2
2.4.0

nokogiri
1.10.4

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

webrick
1.4.2

generated on: 2020-06-16

I'm seeing this too

There was a big new appstoreconnect update today - I can't tell if that's relevant, but it definitely falls under suspicious.

I am also seeing this. I noticed App Store Connect seems to have refreshed it's look. I was wondering if there were any back end changes. My app just now started showing the "Limit Ad Tracking settings in iOS" checkbox when selecting uses IDFA. Have a handful of apps and most of them uploaded successfully, but 2 are seeing this failure on the delivery step.

I'm also experiencing this

+1

+1

+1

+1
Must have something to do with the AppStoreConnect refresh. It's funny because my immediate reaction upon seeing the new interface was, 'Okay but will this break fastlane???'

+1

+1

Had to use altool to deliver our IPA file
https://help.apple.com/app-store-connect/#/devb1c185036

+1

+1

+1

Yeap happens after the new Appstore Connect updates
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 1)...

+1

+1, probably API changes in Appstore Connect. Our upload to appstore step in CI is currently broken due to this.

+1

+1, we're also facing the same error.

+1

+1

+1

+1

+1
[11:45:55]: Starting with the upload of screenshots...
[11:45:55]: Removing all previously uploaded screenshots...
[11:45:56]: Activating languages de-DE, en-AU, en-CA, en-GB, en-US, es-ES, es-MX, fr-CA, fr-FR, ja, sv, it, ko, nl-NL, pt-BR, pt-PT, ru, tr, zh-Hans, zh-Hant...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 1)...

+1

+1
In produce and deliver.

Uploading binaries seem to work well.
For current workaround, we can skip to upload metadata and screenshots.
However, there is no efficient way to skip upload assets...
upload_to_app_store(
  skip_metadata: true,
  skip_screenshots: true,
  metadata_path: nil
)

For me, @giginet's upload_to_app_store snippet above still resulted in an Unexpected Error. However, using upload_to_testflight worked for uploading the binary.

👋 Hey! There was an update to App Store Connect yesterday and looks like it requires some changes on your side. I will be looking into this right away this morning and get a fix out as soon as I can 💪

Best josh in this world

+1

Please don't comment +1, peeps. That's why the 👍 emoji exists for.

Hello everyone. Has anyone managed to solve this problem?

@alekzernov I'm working on a fix now. Please see https://github.com/fastlane/fastlane/issues/16621#issuecomment-645301517 😊

waiting fix )))

I take screenshots and do not upload via fastlane
power: true
skip_metadata: true
skip_screenshots: true

Today we have hotfix release & our release pipeline is broken 😱😤
Now Skipping metadata & screenshots...trying again 🤞🏻

@crazymanish I'm working as hard as I can on a fix now to adapt to new API endpoints that are available.

👋  I'm making progress on things here. I have almost all of the API endpoints figured out and will soon be integrating them into tools like deliver
I would appreciate if there were no more "+1" comments or anything that doesn't provide value into helping me solve this issue 😇
I would like it easy for new people coming to this issue to find the actual status of things.
Original comment from me about what's happening - https://github.com/fastlane/fastlane/issues/16621#issuecomment-645301517
I will add more comments and a link to a PR when I have progress I can share 💪

I try to upload my app with deliver and this configuration:
skip_metadata: true
skip_screenshots: true
This not work for me so I use the upload_to_testflight lane:
upload_to_testflight(
ipa: './fastlane/${app.name}.ipa',
skip_submission: true,
skip_waiting_for_build_processing: true
)
Hope this help someone

Update 1
I've successfully completed the following with new API endpoints:

List App Store versions
List App Store version localizations
Create new App Store version localization
Delete App Store version localization
List screenshots by display type
Upload new screenshots
Delete screenshots

Thing I (might) need to do still

Create new App Store version
List previews (videos)
Upload previews
Delete previews)

Now that I've gotten most of the new API endpoints and models implemented, I will be starting to rip out all usage of Spaceship::Tunes from deliver in favor of my new Spaceship::ConnectAPI::Tunes module.
I will probably discover some new endpoints that I need to implement but this is light at the end of the tunnel.
I will create a PR once I have a working deliver with screenshots, previews, and metadata.
⚠  This PR will be available for you all to test but I won't guarantee there won't be some issues right away 😉 I will still need to write a bunch of tests for all the changes.

Update 2
🥳 I got screenshots uploading through deliver with the new App Store Connect API endpoints
Next steps

Check (and fix) creating new version of app
Check (and fix) metadata
Check (and fix) app previews/videos

I will get a PR pushed once I can verify that creating new app version and uploading meta data either still works or works again 💪

Yikes, fastlane just accidentally submitted a build from April 2019 for review. Luckily that version had a bug in it that was caught by Apple Review so it didn't go out to users.

[10:59:29]: Successfully exported and compressed dSYM file
[10:59:29]: Successfully exported and signed the ipa file:
[10:59:29]: /Users/********.ipa
[10:59:31]: ---------------------------------
[10:59:31]: --- Step: upload_to_app_store ---
[10:59:31]: ---------------------------------
[10:59:33]: Login to App Store Connect (*******)
Available session is not valid any more. Continuing with normal login.
[10:59:36]: Login successful
[...]
[10:59:37]: Making sure the latest version on App Store Connect matches '3.0.1592314125' from the ipa file...
[10:59:40]: Successfully set the version to '3.0.1592314125'
[11:00:25]: Successfully uploaded set of metadata to App Store Connect
[11:00:27]: Starting with the upload of screenshots...
[11:00:27]: Successfully uploaded screenshots to App Store Connect
[11:00:27]: Uploading binary to App Store Connect
[11:00:34]: Going to upload updated app to App Store Connect
[11:00:34]: This might take a few minutes. Please don't interrupt the script.
[11:06:19]: iTunes Transporter successfully finished its job
[11:06:19]: --------------------------------------------------------------------
[11:06:19]: Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online.
[11:06:19]: --------------------------------------------------------------------
[11:06:19]: Finished the upload to App Store Connect
[...]
[11:06:31]: Selecting the latest build...
[11:06:33]: Selecting build 3.0.1592314125<PHONE_NUMBER>0017)...
[11:06:36]: Successfully selected build
[11:06:36]: Submitting the app for review...
[...]
[11:06:46]: Successfully submitted the app for review!

Notice [11:06:33]: Selecting build 3.0.1592314125<PHONE_NUMBER>0017)... - I'm guessing it's because<PHONE_NUMBER>0017 is first in list at App Store Connect -> Activity -> iOS Builds.

@Mike278 Thanks for the report! I will also look into this too while I'm in deliver 👍

Update 3
There is A LOT of metadata. Hoping to have PR up in an hour-ish.

Heads up
At Tellus, all our iOS releases are manual, and iTunes Connect would remember this setting from the last app version. Unfortunately, that wasn't the case now with this iTunes Connect revamp! The option went back to the Automatically release this version default 👎 luckily, I caught this in time.

Check your apps, make sure you update this setting correctly.

@rogerluan Thanks for the info! I just wrote the new code to handle this about 30 minutes ago in deliver so we should be good once fastlane is fixed 😊

Update 4
My PR is "ready" 😛 - https://github.com/fastlane/fastlane/pull/16626
Things working

App screenshots
App metadata

Version metadata
Localized version metadata
Review detail
Review attachment
Version phased release
Reset rating request

Things not working yet

App preview
App metadata

App rating
Trade representative information

Submitting correct version

Any field testing would be appreciated 🙏

Update Gemfile to below 👇
Run bundle install, bundle update, or bundle update fastlane

gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-update-deliver-for-app-store-connect-api"

Please leave any comment about this PR in the PR 😊

Hey Guys, I am using azure devops and the AppStorePromote step uses fastlane. Does anyone know how to specify how to exclude the meta data in the yaml?
I am trying to implement the above:
upload_to_app_store(
skip_metadata: true,
skip_screenshots: true,
metadata_path: nil
)
with this step:
- task: AppStorePromote@1
inputs:
serviceEndpoint: 'Apple'
appIdentifier: 'com.xxx'
shouldAutoRelease: true
thanks!

@danimal521 Heyyy 👋 Can you move that to a new issue? 😊 Its related but kind of its own thing since its about azure devops.

can we expect another release right after the PR got merged?

@csv8674xn For sure! I will pump out a release as soon as I click the merge button.
I have quite a bit more new feature/fixes work yet and then updating all of the tests 😀 I will try to get it all done tonight 🤞

Hey @joshdholtz, looking forward to the new release 😄 I just wanted to say thanks for your hard work and your real time updates today! Thanks for saving our asses man!

Update 5
There were some issues reported in the PR and I'm working on taking care of them! I will probably not end up getting everything finished today 😔 I've worked about 15 hours on this and my brain is starting to get a bit loopy 🙃
I'll be waking up early tomorrow to continue where I leave off tonight. I'm feeling pretty confident that I should be able to release a new version tomorrow (with some follow up versions with any other issues that pop up).
Thank you to all of you for the patience! I really appreciate it 😊 ❤

@joshdholtz , Thanks your hard work, Man, You're my hero.

Update 6
We made lots of progress on the PR! Only a few things left I think 😊
Also..
ERROR ITMS-90382: "Upload limit reached. The upload limit for your application has been reached. Please wait 1 day and try again."

I hit my binary upload limit and need to wait 24 hours 🤷♂

Thanks for working on this Josh!  I have 100 apps to update in a few days and this stopped everything cold.  Anxiously waiting!

Question
👋 Hey, fam! I have never used app previews for any of my apps so I just noticed that deliver does not actually support uploading app previews 😔
Would this be a feature you would like me to add in a follow up PR?
👍 reaction for "yes"
👀 reaction for "I'd use if I needed it"
👎 reaction for "seems like overkill"

Update 7
Giving you all another update before go to bed 😊
Made pretty good progress today. Spent most of the morning and afternoon working with issues of users testing out the PR. This evening was finishing up missing meta data information. Lost quite a bit of time to IDFA and app category endpoints.
Below is a checklist I've made on the PR 👇 Tomorrow is going to be testing screenshots on things that aren't iOS and wrangling the broken tests 😇

If anybody else could test out that PR tomorrow that would be great!
Thanks again for all the help and being patient ❤

Can I just say your dedication and commitment to getting this fixed so fast in a highly pressured week before WWDC is just incredible. Thank you.

Hey @joshdholtz, we've successfully submitted an app using this branch 🎉  Thanks for the hard work!
Here's the deliver summary for the reference:
+--------------------------------------+--------------------------------------+
|                           deliver 2.149.1 Summary                           |
+--------------------------------------+--------------------------------------+
| force                                | true                                 |
| team_id                              | *********                            |
| team_name                            | *********                            |
| itc_provider                         | *********                            |
| username                             | *********                            |
| app_identifier                       | *********                            |
| skip_screenshots                     | false                                |
| skip_metadata                        | false                                |
| submit_for_review                    | true                                 |
| automatic_release                    | true                                 |
| price_tier                           | 0                                    |
| app_icon                             | app-store-icon.png                   |
| copyright                            | *********                            |
| primary_category                     | Business                             |
| description.en-US                    | *********                            |
| keywords.en-US                       | *********                            |
| release_notes.en-US                  | *********                            |
| privacy_url.en-US                    | *********                            |
| marketing_url.en-US                  | *********                            |
| support_url.en-US                    | *********                            |
| submission_information.add_id_info_  | false                                |
| uses_idfa                            |                                      |
| submission_information.add_id_info_  | false                                |
| serves_ads                           |                                      |
| submission_information.add_id_info_  | false                                |
| tracks_action                        |                                      |
| submission_information.add_id_info_  | false                                |
| tracks_install                       |                                      |
| submission_information.content_righ  | true                                 |
| ts_has_rights                        |                                      |
| submission_information.content_righ  | true                                 |
| ts_contains_third_party_content      |                                      |
| submission_information.export_compl  | ios                                  |
| iance_platform                       |                                      |
| submission_information.export_compl  | false                                |
| iance_compliance_required            |                                      |
| submission_information.export_compl  | false                                |
| iance_encryption_updated             |                                      |
| submission_information.export_compl  | true                                 |
| iance_uses_encryption                |                                      |
| submission_information.export_compl  | true                                 |
| iance_is_exempt                      |                                      |
| submission_information.export_compl  | false                                |
| iance_contains_third_party_cryptogr  |                                      |
| aphy                                 |                                      |
| submission_information.export_compl  | false                                |
| iance_contains_proprietary_cryptogr  |                                      |
| aphy                                 |                                      |
| submission_information.export_compl  | false                                |
| iance_available_on_french_store      |                                      |
| app_review_information.first_name    | *********                            |
| app_review_information.last_name     | *********                            |
| app_review_information.phone_number  | *********                            |
| app_review_information.email_addres  | *********                            |
| s                                    |                                      |
| app_review_information.demo_user     | *********                            |
| app_review_information.demo_passwor  | *********                            |
| d                                    |                                      |
| overwrite_screenshots                | true                                 |
| run_precheck_before_submit           | false                                |
| app_rating_config_path               | ./fastlane/ratings.json              |
| ipa                                  | *********                            |
| screenshots_path                     | ./fastlane/screenshots               |
| metadata_path                        | ./fastlane/metadata                  |
| app_version                          | *********                            |
| platform                             | ios                                  |
| edit_live                            | false                                |
| use_live_version                     | false                                |
| skip_binary_upload                   | false                                |
| skip_app_version_update              | false                                |
| reject_if_possible                   | false                                |
| phased_release                       | false                                |
| reset_ratings                        | false                                |
| precheck_default_rule_level          | warn                                 |
| individual_metadata_items            | []                                   |
| ignore_language_directory_validatio  | false                                |
| n                                    |                                      |
| precheck_include_in_app_purchases    | true                                 |
+--------------------------------------+--------------------------------------+

@mjovkovic Submit for review is fixed now! I had one line commented out during my testing 😇 Thanks for testing!

@joshdholtz, your branch works for me too - great job!
Where can I drop some $ for a coffee or an ale, sir?

@Aw79 Glad it works! And I appreciate the offer but you don't need to do that 😊

@joshdholtz Too bad it's not real dub-dub next week so I could "hi-5" you

@mjovkovic Submit for review is fixed now! I had one line commented out during my testing 😇 Thanks for testing!

Just to confirm that submit for review works now! Thank you!

@Aw79 Maybe we can high five next year!
@mjovkovic Glad that worked! Can’t believe I left that commented out line in there 😝

@joshdholtz just tried your branch and it worked well, apart from the fact that it removed the Primary Category from the general app information (which was Travel).

@arne-dott Ah, my apologies! The new API changed the category keys so I had to map them the old ones to the new ones but might have missed travel 😩 What value were you using? Was it just “Travel”?

@arne-dott Ah, my apologies! The new API changed the category keys so I had to map them the old ones to the new ones but might have missed travel 😩

No worries! I'm glad it actually almost worked perfectly 😄

What value were you using? Was it just “Travel”?

Just checked, we are using MZGenre.Travel. Not sure if this is what we should be using, but this used to work.

Update 8
Good ! We have decided that we are going to release PR #16626 as a release candidate build here soon™.
Making of candidate 2.150.0.rc1
We are going to forgo writing new tests for deliver in PR #16626  I want to get this build out as soon as I can and there are a lot of tests that need to be written. We will then release a new version as 2.150.0.rc1.
Plan after 2.150.rc1

Create new temporary issue template specifically for reporting issues on deliver and release candidate
Monitor issues closely for any with deliver or spaceship
Make fixes quickly and release new release candidates as fix is merged in
Open new PR for updating deliver tests

Any thoughts, questions, or concerns are appreciated! 😊

@joshdholtz How long before there's a public release? I have a handful of white labeled apps waiting in queue. Also not entirely sure how to update the gemfile to point to your specific branch on github?

@tmaly1980 Great question!  Will probably be tomorrow last morning / early afternoon Chicago time 🤞

OK I've updated my Gemfile to use:
gem 'fastlane', '2.149.1', git: 'https://github.com/fastlane/fastlane.git', branch: 'joshdholtz-update-deliver-for-app-store-connect-api'
However, now I'm getting this error:
The request cannot be fulfilled because of the state of another resource. - Attribute 'whatsNew' cannot be edited at this time
I'm setting deliver's release_notes. Am I doing something wrong, is this needing to be fixed, or is it an issue with apple's servers?

@tmaly1980 I’ve been hearing some issues with people not being able to even edit whatsNew on the dashboard so I’m not sure if that is the case or not. Are you able to edit the “what’s new” section for your app on the website?

@joshdholtz I got the "Attribute 'whatsNew' cannot be edited at this time" for an app that hadn't been publicly released yet, so I deleted the release notes from the fastlane meta and had no issues proceeding. @tmaly1980 Does that bear resemblance to your situation?

Not worked for me =(
+--------------------------------------+------------------------------------------------------------+
|                                      deliver 2.149.1 Summary                                      |
+--------------------------------------+------------------------------------------------------------+
| submit_for_review                    | false                                                      |
| force                                | true                                                       |
| ipa                                  | xxxxx                                                      |
| app_identifier                       | xxxxx                                                      |
| screenshots_path                     | ./fastlane/screenshots                                     |
| metadata_path                        | ./fastlane/metadata                                        |
| app_version                          | xxx                                                        |
| username                             | xxxxxxxxxxxxxxxxxx                                         |
| platform                             | ios                                                        |
| edit_live                            | false                                                      |
| use_live_version                     | false                                                      |
| skip_binary_upload                   | false                                                      |
| skip_screenshots                     | true                                                       |
| skip_metadata                        | false                                                      |
| skip_app_version_update              | false                                                      |
| overwrite_screenshots                | false                                                      |
| reject_if_possible                   | false                                                      |
| automatic_release                    | false                                                      |
| phased_release                       | false                                                      |
| reset_ratings                        | false                                                      |
| team_id                              | xxxxxxxxx                                                  |
| dev_portal_team_id                   | xxxxxxxxxx                                                 |
| run_precheck_before_submit           | true                                                       |
| precheck_default_rule_level          | warn                                                       |
| individual_metadata_items            | ["[]"]                                                     |
| ignore_language_directory_validation | false                                                      |
| precheck_include_in_app_purchases    | true                                                       |
+--------------------------------------+------------------------------------------------------------+
Traceback (most recent call last):
19: from /usr/local/bin/fastlane:23:in <main>' 	18: from /usr/local/bin/fastlane:23:in load'
17: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/bin/fastlane:23:in <top (required)>' 	16: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in take_off'
15: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:17:in start' 	14: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:183:in run'
13: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	12: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
11: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	10: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
9: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	 8: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/commands_generator.rb:80:in block (2 levels) in run'
7: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:37:in run' 	 6: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/deliver/lib/deliver/runner.rb:92:in verify_version'
5: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/application.rb:250:in ensure_version!' 	 4: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/app_version.rb:412:in save!'
3: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:463:in update_app_version!' 	 2: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:1553:in with_tunes_retry'
1: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:470:in block in update_app_version!' /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.149.1/spaceship/lib/spaceship/tunes/tunes_client.rb:228:in handle_itc_response': [!] The request could not be completed because: (Spaceship::Tunes::PotentialServerError)

@romandutov Hey! Your stacktrace shows an error from the latest release of fastlane (which is known to be broken). If you switch to the branch of the PR that fixes this issue you would probably be okay 🙂 I will be releasing a new release candidate version tomorrow that will fix things for a lot of users 💪

Hi @joshdholtz , thanks a lot for you work, it is very helpful. I have just used version from your branch, and I have one error, which was not before
[03:04:19]: Making sure the latest version on App Store Connect matches '1.6.3'...
+---------------------------------------+--------------------------------------------------------+
|                                          Lane Context                                          |
+---------------------------------------+--------------------------------------------------------+
| DEFAULT_PLATFORM                      | ios                                                    |
| PLATFORM_NAME                         | ios                                                    |
| LANE_NAME                             | ios precheck_itunes_connect                            |
| ORIGINAL_DEFAULT_KEYCHAIN             | ""|
| GET_IPA_INFO_PLIST_VALUE_CUSTOM_VALUE | 1.6.3                                                  |
+---------------------------------------+--------------------------------------------------------+
[03:04:20]: The provided entity includes a relationship with an invalid value - You cannot create a new version of the App in the current state. The provided entity includes an attribute with a value that has already been used - The version number has been previously used.

@starostin Do you already have a version of your app that is live with version 1.6.3?

Before I had this

@starostin Is 1.6.3 already for sale/download on the App Store? 🤔 If so, you need to increment the build number in Xcode before using deliver. It looks like its trying to edit metadata on a version that is already for sale which is not allowed.

@joshdholtz This app in app store connect, but it is rejected by app review. And before using your branch I was able to send builds with the same build number to testflight

@starostin Ahhhh! I will have a new commit that should fix things for you in like 5 minutes 😊

@tmaly1980 Pushed a new commit that should fix whatsNew from getting sent up for first versions
@starostin Pushed new commit that finds "editable" versions with the rejected state.
If you could let me know if/when things work for you that would be 🔥

@joshdholtz, sorry for the delay. I still have the same error ((

@starostin Not a problem! I went on a 🍩 run 😇
Would be able to...

Send me your entire console output?
Run bundle exec fastlane run spaceship_logs print_contents:true and uploaded the output to me? It will output the contents from our Spaceship/API logs so you can see what the last requests/responses were like. It can sometimes help with seeing more of the error response 🙂

You can email me the files at<EMAIL_ADDRESS>if you don't want to upload them here 🙃

And also interesting thing, that one app which has status in app store connect "Developer rejected" is processing fine, but second which has status "Metadata rejected" has this error. Ok, I will do that

@starostin OHHHHHH... that metadata rejected must be a status enum that I don't have 😱 The enums are listed anywhere at the moment so been trying to discover them all. Having those spaceship logs should be a huge help 😊

The log for the first api call is huge, and I cant send you the whole response, but I found on it the mention of metadata
"versionString"=>"1.6.3", "appStoreState"=>"METADATA_REJECTED",

@starostin That is perfect!  You can find just the file location with bundle exec fastlane run spaceship_logs

@joshdholtz Oooops, seems I did not update fastlane before running command, I will give one more try. Sorry for that. Also I am running everything from CI, so that is why it takes some time

@starostin Ha, not a problem! 😊 I have plenty of other things I'm still working on 🤷♂

@joshdholtz It works 🥳🥳🥳 Thanks a lot !!!

Everything is working except that it is not updating the age ratings.

@tymcdowell Fixed that about 16 minutes ago 😇 https://github.com/fastlane/fastlane/pull/16626/commits/3a46a0031ca6866854f32d9ee7e3bbab5ffbdcbf

Update 9
👋 We are SOOOOOO close! Everything is feeling pretty good on the PR. I'm going to go for a health walk to clear mind and see if anything else pops in to my head that I missed.
The release candidate should be out in a few hours 🚀 I'll update more info here later on how to use.
Thanks, all! ❤

Update 10
👋 Hey, fam! I merged in #16626, created the 2.150.0.rc1 release, and pushed the gem out to Ruby gems.
You can install it by 👇
gem "fastlane", ">= 2.150.0.rc1"

I will be working on cleaning feature up, adding tests, and responding/fixing any issues that come in. I'm hoping to get an official 2.150.0 release out end of next week 🤞
🙏 Please make new issues for anything that you see in 2.150.0.rc1. It is easier to have conversations and work through issues that way 😊
⚠ I will most likely be locking this issue tomorrow sometime to prevent any other issues from getting added into this one 😊
❓ Please feel free to create new issues and mention me if you if have any questions or concerns. You can also tweet/DM me at @joshdholtz for any questions.
Thanks again for all the help in testing this out!
New issue template for release candidate
Use this for creating new any issues with the release candidate 👇

PR/branch for 2.150.0 release candidate
I will be adding a few more features, code cleanup, and tests into this branch before it gets officially released 👇
https://github.com/fastlane/fastlane/pull/16640
Issue for release candidate
I created a pinned issue explaining how to use the release candidate 👇
https://github.com/fastlane/fastlane/issues/16639

RC worked for me, thank you so much! <3

@TheWirv Ahhh, I think App Store Connect doesn’t reuse the setting from previous builds anymore? Something changed about this but I’m not sure how I feel about defaulting it to false 🧐 I don’t want to get users in trouble be defaulting something like that.
Thoughts?

@joshdholtz Yeah no, that's difficult. I don't know, if I'd be comfortable to default it to false, either. On the other hand, I think that people who do use it/need it, already might have set it to true, so there might be no harm done there. Also, this is still marked as an RC, so you could default it to false and test it out as part of the RC phase, no?
Regarding the reuse of previous build: I don't know about that because yesterday was the first time I ever heard about usesIdfa. I never had to set it before.

@joshdholtz - I just got the following error:
[14:34:34]: The request cannot be fulfilled because of the state of another resource. - Submit for review errors found.
The provided entity is missing a required relationship - You must provide a value for the relationship 'primaryCategory' with this request

@joshdholtz
Hello there
This problem is often found during uploading screenshots
[!] The request could not be completed because:
Server error got 504
Don't know how to fix it?

@joshdholtz - I just got the following error:
[14:34:34]: The request cannot be fulfilled because of the state of another resource. - Submit for review errors found.
The provided entity is missing a required relationship - You must provide a value for the relationship 'primaryCategory' with this request

@natedenh You can just add a primary_category.txt file to your metadata directory and fill it with whatever category represents your app best. Check the docs for reference.

@joshdholtz - Thanks.  I found that and I am adding it now. I only told you because I never got this before.

@joshdholtz Sweet! Everything works for me now!

Thanks a lot @joshdholtz , a real MVP 🚀

I have same issue - “ The provided entity is missing a required attribute - You must provide a value for the attribute 'honorsLimitedAdTracking' with this request”

@joshdholtz  I am still getting same issue after uplift of fatlane version to 2.150.0.rc1?

works for me! v 2.150.0.rc1

When will this fix be available, our CI builds rely on Fastlane deliver for meta content uploads.

I appreciate your work. Thank a lot @joshdholtz

same here, still getting the error

Still getting the problem, here's a snippet from my bitrise log.
fastlane 2.133.0
#######################################################################
fastlane 2.149.1 is available.
You should use the latest version.
Please update using bundle update fastlane.
#######################################################################
2.150.0.rc1

[deliver][produce][spaceship] Update to use new App Store Connect API endpoints (#16626) via @joshdholtz

Instructions on testing the release candidate
Bundler
Update your Gemfile to include the following:
gem "fastlane", ">= 2.150.rc1"

At the bottom of the log file the error is displayed, included below:

`Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...`

Still getting the problem, here's a snippet from my bitrise log.
2.150.0.rc1
- [deliver][produce][spaceship] Update to use new App Store Connect API endpoints (#16626) via @joshdholtz
## Instructions on testing the release candidate
### Bundler
Update your `Gemfile` to include the following:
```rb
gem "fastlane", ">= 2.150.rc1"

At the bottom of the log file the error is displayed, included below:
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...

Still getting the problem, here's a snippet from my bitrise log.
�[32m2.150.0.rc1�[0m
- [deliver][produce][spaceship] Update to use new App Store Connect API endpoints (#16626) via @joshdholtz
## Instructions on testing the release candidate
### Bundler
Update your `Gemfile` to include the following:
```rb
gem "fastlane", ">= 2.150.rc1"

At the bottom of the log file the error is displayed, included below:
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 2)...

I think your Fastlane is not really updated. Just try to verify your Fastlane version again

.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
fastlane 2.150.0.rc1

Still getting the problem. too..

Update 11
👋 Happy WWDC week, everyone! I will be going ham on fixing issues from the release candidate so that we can get an official version of this build out as soon as possible. My goal is by end of the week but it really depends on when everything is super stable.
I've read through all the comments and updated my checklist on #16640 with issues to your comments if you want to follow there! I hope I got them all but its hard to sift through them all (see below 👇)

I'm going to lock this issue (for now)
I don't lock issues very often at all but it is very difficult to multiple conversations about your specific issues in this thread 🙃. Some of the issues require a conversation about configurations or environment information and that is just too much to handle for this thread. I would like for issue to be filed individually following the issue template so that I can debug easier without needing to ask all the questions I need every time 😊
For the issues mentioned above in comments: I will mention you in a PR that is specific to your issue when I have it fixed. We can have more of a conversation there if we need.
See PR for 2.150.0 for code updates 👉  https://github.com/fastlane/fastlane/pull/16640
Create new Release Candidate issue if you have issues 👉 https://github.com/fastlane/fastlane/issues/new?template=A_RELEASE_CANDIDATE_ISSUE.md
Sorry about locking the issue! ❤ I don't want to limit conversation of the community but I'd like to get this fix out at as soon as possible for everyone. The easiest way to do that is to have new issues for the release candidate submitted as new issues.

Update 12
🚀  Released 2.150.0.rc2 with a bunch of fixes 👉 https://github.com/fastlane/fastlane/releases/tag/2.150.0.rc2
Hoping to make this release official in a few days 🤞


Create a way to setup allowed origin for a Worker

Two possible examples of allowed origin:
1. Secure Channel. Worker may only accept messages that got into its node through Secure Channel, optionally worker may as well have requirements on WHO is on the other end of that Secure Channel. Also I can imagine use case where worker accepts messages from any Secure Channel, but after the first message is received, all the other messages should be from the same secure channel. Examples of that is Tcp Inlet, we may receive only messages from Secure Channel, sometimes we know other participant EntityId beforehand, sometimes we may accept any participant, but since one Outlet always has exactly one connection to the target Server, we want to be sure that nobody other than initial client could send messages to that Outlet after connection is created.
2. Local message. Worker may only want to accept messages that were created inside its node, or only messages sent from specific address. Example of that is VaultSync. New Context with new Address is created for every new request, then request is sent to the Vault Worker, and we only want to accept responses from Vault Worker. Even though local addresses are mostly random, we should consider safety concerns, like remote node sending us vault responses through TCP, and trying to guess the address.
Current implementation only partially satisfies our needs.
The other problem is that receiving Worker may not know what Secure Channel is (like Tcp Outlet) and routing itself knows nothing about Secure Channels. Therefore, I think, these origin rules should be setup at the place of Worker creation/start, this is the place we have access to Secure Channels, routing, business logic and receiving worker.

The other example for 2. is Secure Channel. Each Secure Channel have 2 addresses, first is for encryption and sending to the remote end of the channel, second if for decryption. Encryption address wants to accept messages that were created on the same node only


All points belong to the same primitive

Hi,
I just followed ur work and trained the network. Unfortunately, when I check the validation and the test dataset, all points belong to the same primitive.
Can you provide some well-trained parameters?
Thank you so much!

Hi,
I just followed ur work and trained the network. Unfortunately, when I check the validation and the test dataset, all points belong to the same primitive.
Can you provide some well-trained parameters?
Thank you so much!

Hello, I encountered such an error when training the model. Could you give me some advice on how to solve it?
File "/home/shiying/.conda/envs/spfn/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1717, in init
self._traceback = tf_stack.extract_stack()
InvalidArgumentError (see above for traceback): No OpKernel was registered to support Op 'FarthestPointSample' with these attrs.  Registered devices: [CPU], Registered kernels:
device='GPU'
     [[Node: SPFN/est_net/layer1/FarthestPointSample = FarthestPointSample[npoint=512](SPFN/est_net/Slice)]]

@Stone-sy I don't think the issue you mentioned is the same as mine.
FYI, you can search your issue in PointNet/PointNet++ codebase on github


[screengrab] Re-add locale and images to screenshots output path

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

The output of the screenshots taken with screengrab were not including the locale any more, which broke several features. For example, I got my outputs for all languages to fastlane/metadata/android/phoneScreenshots. This also broke any links within the screenshots.html file.
Description

This PR is doing the move step of the screenshots per language instead of only once at the end. For me this PR fixes https://github.com/fastlane/fastlane/issues/15690 and https://github.com/fastlane/fastlane/issues/14584.

Waiting for a review before I fix the tests as I'm not sure if the approach I've taken is accepted. It was the quickest fix I could come up with, feel free to refactor to a proper fix. If it's fine, I could also update the tests to pass. Need your feedback on this.

Any idea why this broke, although it worked before (I assume)?

@janpio I'm not sure, I have to guess, the relevant code was last touched 4 years ago so:

Either it never actually worked in the first place (I personally just starting using screengrab for the first time, so I can't tell)
adb or Androids behavior has changed at some point within the last 4 years and before, the en-US/images subpath was automatically generated when taking screenshots by Android / adb but now, it's no longer added

@googlebot I consent.


Easy documentation lookup on google

From #2980.

np.histog + Select histogram2d + AltGr
--> Launch "Chrome/Default Browser" + Google.com + search: python "import numpy" histogram2d ("import package_name") + function/attribut

The initial idea was to trigger the search from the completion tooltip with a specific shortcut. I think it's better to do it from the Help widget once the doc is displayed for the function. Using a google search is usually because the inline documentation is not enough, and the functionality would be more discoverable if it can be triggered by a pushbutton or a menu entry rather than by a shortcut alone.

docrepr is going (eventually :-) to autolink to docs.python.org for objects that belong to the standard library.
I agree with @Nodd that this doesn't belong to the the completion widget but to the Help plugin.
Besides, someone will have to implement this one because it's an important issue for us to have :-)


docker events return null when I use authorization plugin

Docker Version:
Client:
Version:      1.10.0-dev
API version:  1.23
Go version:   go1.5.3
Git commit:   7faff24-unsupported
Built:        Thu Jan 21 06:06:47 2016
OS/Arch:      linux/amd64
Server:
Version:      1.10.0-dev
API version:  1.23
Go version:   go1.5.3
Git commit:   7faff24-unsupported
Built:        Thu Jan 21 06:06:47 2016
OS/Arch:      linux/amd64
Docker Info:
Containers: 15
Running: 0
Paused: 0
Stopped: 15
Images: 5
Server Version: 1.10.0-dev
Storage Driver: devicemapper
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: null host overlay bridge
Authorization: leeProcess
Kernel Version: 4.1.8-200.fc22.x86_64
Operating System: Fedora 22 (Twenty Two)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 11.46 GiB
Cluster store: etcd://<IP_ADDRESS>:4001/docker-cluster1
Cluster advertise: <IP_ADDRESS>:2375
step:
1.docker daemon -s devicemapper  --authorization-plugin=leeProcess
2.docker events
3.at the same time,I command "docker start {CID}"
I don't get any message from events terminal
If I run other docker command ,I get the result that i expected

Hi @leejansq  Could you confirm if just docker start   not have event ?

@HackToday  All command not only docker start

@leejansq what is your plugin doing? is it preventing containers to start? authz plugins shouldn't interfere with docker events at all - given you aren't preventing containers from starting

@runcom  the problem is ，If I use the authz plugin,I don't get any events via docker events api

ping @runcom have you been able to reproduce this?

I've published a possible fix, you can use the authorization plugin with example policy to validate.

@liron-l so this is an issue with the plugin, not docker?

@thaJeztah, no. Unfortunately the issue is with the authorization system (specifically when calling the /events endpoint).

@liron-l alright, thanks, I'll add a "bug" label; are you able to look into this?

@thaJeztah already submitted a fix in #20002, waiting for code-review.


Add to support convert inline code block from Markdown to HTML

Add a feature to support to convert inline code block from Markdown to HTML tag

This issue is solved. Issue closed 5a735a585c0e48ff1f0425cc9a9c026de9ce5441


fix: bump version of Ubuntu in Dockerfile

Description
Seems like dependencies have bumped that can no longer be found in Ubuntu 20.04 (Focal). This PR bumps Ubuntu to 22.04 which resolves this.
Note: this does not resolve the ARM issue which will have to be explored next.
Related Items
Further discussion can be found in #775

[x] I agree to contribute to the project under Apache 2 License.
[x] To the best of my knowledge, the proposed patch is not based on code under GPL or other license that is incompatible with FlexMeasures

Thanks for this!
Interesting that tests are not running ("Expected — Waiting for status to be reported"). Any idea why that is?
To test this PR, we'd need to build the Docker image, and then run the toy tutorial inside it (the tutorial also has steps for exactly that).
Let me know if you're able to do that, otherwise I can look into it next week.

Okay, need to look at that some other day. More important is to test the new image.

I ran into a few issues the other day with auth. I'll start running the tutorial to go through the errors.

Just a note: we made an issue (#795) for testing that a Docker image can be built inside of Github Actions.
#776 should be merged today and would have caught your issue with 3.8 (probably also without upgrading the Ubuntu LTS version)

Ok, so should we close this then and I can change my focus to ARM devices?

Bumping the Ubuntu version might still be useful, so I want to keep this PR open.
#776 hopefully lets you work further.
Feel free to talk about the ARM approach in your other issue.


fix no defaultValue in ts parser

rt;
check module before install it;

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 5 committers have signed the CLA.:white_check_mark: LeoYuan:white_check_mark: liujuping:white_check_mark: mark-ck:white_check_mark: Clarence-pan:x: JackLianYou have signed the CLA already but the status is still pending? Let us recheck it.

build-plugin-lowcode 组件依赖没有升级到此版本


Remove superfluous Router in <EntitySecurityInsightsContent>

This PR removes a superfluous <Router> in the EntitySecurityInsightsContent component from the security insights plugin. The router in question seems to be configured to work with<EMAIL_ADDRESS>but not more recent versions. Since it doesn't add anything in this context, I have removed it.
This fixes #989. The incorrectly configured router component would simply not render anything on recent versions of react-router.
I have left the router component around since it's still being exported with deprecations referencing old versions of the plugin. This is so that I don't cause a breaking change.
Note that I have somewhat been able to test this locally but I don't have currently access to a setup with working GitHub authentication. I would recommended some testing before getting this merged.
:heavy_check_mark: Checklist

[ ] Added tests for new functionality and regression tests for bug fixes
[x] Added changeset (run yarn changeset in the root)
[ ] Screenshots of before and after attached (for UI changes)
[ ] Added or updated documentation (if applicable)

Hi,
Any update on this when it can be merged?
Thanks

Ping @kissmikijr
We are kind of struck.
Can you please have a look to this Pull Request

Hey, not sure don't have an ETA on this one as you stated in the description it involves a bigger time commitment from us  as you were not able to test this change.

Hi @kissmikijr. I am from the same team as @grvpandey11 and I was wondering if it would speed up the process for your team if we test the proposed fix on our end by manually installing the plugin codebase from this branch. I can then report back if this fix solves the issue or not. Please let me know if this would be appropriate.

@steff-petro Yes, I'd really appreciate it and would help a lot!

@kissmikijr Great! I will try the solution as soon as I have time and I will report back the results in this pr.

@kissmikijr I have now tried the proposed solution. On our end this solution seems to fix the issue that we originally had. I have tried it on a couple of entities and it all works as expected on our end.

@kissmikijr Ping. Now that we have tested it, any chance you could provide us with a timeline on when this can be merged. Additionally, if there is any other way I can help to speed it up please let me know.

Hey, can you please rebase this branch ?

@kissmikijr done


idk why when i compile the source code it just stops at here

idk why when i compile the source code it just stops at here
C:\Users\samma\Downloads\FNF-PsychEngine-0.5.2h\FNF-PsychEngine-0.5.2h>lime test windows
source/Alphabet.hx:200: characters 20-28 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/editors/ChartingState.hx:143: characters 13-21 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/Main.hx:78: characters 61-65 : Float should be Int
source/Main.hx:78: characters 61-65 : ... For optional function argument 'updateFramerate'
source/Main.hx:78: characters 61-65 : ... For function argument 'child'
source/PlayState.hx:84: characters 40-48 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PlayState.hx:122: characters 20-28 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PlayState.hx:200: characters 17-25 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/FreeplayState.hx:242: characters 28-36 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PauseSubState.hx:27: characters 17-25 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PlayState.hx:84: characters 68-76 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/FunkinLua.hx:1370: characters 18-26 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/FunkinLua.hx:1404: characters 18-26 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PauseSubState.hx:64: characters 20-28 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/FreeplayState.hx:339: characters 19-27 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/FreeplayState.hx:341: characters 19-27 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PlayState.hx:498: characters 22-30 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PlayState.hx:1787: characters 17-25 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PlayState.hx:1789: characters 17-25 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/PlayState.hx:1792: characters 27-35 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/editors/ChartingState.hx:1275: characters 16-24 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/editors/EditorPlayState.hx:39: characters 13-21 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/editors/EditorPlayState.hx:109: characters 17-25 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/editors/EditorPlayState.hx:111: characters 17-25 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
source/TitleState.hx:653: characters 15-23 : Warning : flixel.system.FlxSound was moved to flixel.sound.FlxSound
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

Psych 0.5.2h is not supported anymore

in the newer version i get this
source/PlayState.hx:1621: characters 13-23 : Type not found : MP4Handler
source/FunkinLua.hx:2221: lines 2221-2224 : flixel.sound.FlxSound should be flixel.system.FlxSound
source/FunkinLua.hx:2221: lines 2221-2224 : ... For function argument 'value'
source/PauseSubState.hx:73: characters 23-33 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PauseSubState.hx:73: characters 23-33 : ... For function argument 'Object'
source/FreeplayState.hx:344: characters 25-31 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/FreeplayState.hx:344: characters 25-31 : ... For function argument 'Object'
source/PlayState.hx:583: characters 25-35 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:583: characters 25-35 : ... For function argument 'Object'
source/PlayState.hx:2434: characters 23-29 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:2434: characters 23-29 : ... For function argument 'Object'
source/PlayState.hx:2435: characters 23-83 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:2435: characters 23-83 : ... For function argument 'Object'
source/PlayState.hx:1827: characters 25-37 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:1827: characters 25-37 : ... For function argument 'Object'
source/PlayState.hx:1874: characters 25-34 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:1874: characters 25-34 : ... For function argument 'Object'
source/PlayState.hx:1945: characters 25-36 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:1945: characters 25-36 : ... For function argument 'Object'
source/flixel/system/FlxSound.hx:716: characters 17-30 : Warning : flixel.system.FlxSoundGroup was moved to flixel.sound.FlxSoundGroup
source/flixel/system/FlxSound.hx:722: characters 21-25 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/flixel/system/FlxSound.hx:722: characters 21-25 : ... For function argument 'sound'
source/flixel/system/FlxSound.hx:725: characters 15-19 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/flixel/system/FlxSound.hx:725: characters 15-19 : ... For function argument 'sound'
source/editors/ChartingState.hx:1359: characters 24-30 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/editors/ChartingState.hx:1359: characters 24-30 : ... For function argument 'Object'
source/editors/ChartingState.hx:2193: characters 4-42 : flixel.sound.FlxSound should be flixel.system.FlxSound
C:/haxelib/flixel/5,3,1/flixel/ui/FlxButton.hx:259: characters 55-64 : flixel.animation.FlxAnimationController has no field numFrames
source/TitleState.hx:723: characters 7-58 : flixel.sound.FlxSound should be flixel.system.FlxSound
source/TitleState.hx:725: characters 7-58 : flixel.sound.FlxSound should be flixel.system.FlxSound
source/TitleState.hx:729: characters 7-55 : flixel.sound.FlxSound should be flixel.system.FlxSound

Psych 0.5.2h is not supported anymore

in the newer version i get this
source/PlayState.hx:1621: characters 13-23 : Type not found : MP4Handler
source/FunkinLua.hx:2221: lines 2221-2224 : flixel.sound.FlxSound should be flixel.system.FlxSound
source/FunkinLua.hx:2221: lines 2221-2224 : ... For function argument 'value'
source/PauseSubState.hx:73: characters 23-33 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PauseSubState.hx:73: characters 23-33 : ... For function argument 'Object'
source/FreeplayState.hx:344: characters 25-31 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/FreeplayState.hx:344: characters 25-31 : ... For function argument 'Object'
source/PlayState.hx:583: characters 25-35 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:583: characters 25-35 : ... For function argument 'Object'
source/PlayState.hx:2434: characters 23-29 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:2434: characters 23-29 : ... For function argument 'Object'
source/PlayState.hx:2435: characters 23-83 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:2435: characters 23-83 : ... For function argument 'Object'
source/PlayState.hx:1827: characters 25-37 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:1827: characters 25-37 : ... For function argument 'Object'
source/PlayState.hx:1874: characters 25-34 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:1874: characters 25-34 : ... For function argument 'Object'
source/PlayState.hx:1945: characters 25-36 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/PlayState.hx:1945: characters 25-36 : ... For function argument 'Object'
source/flixel/system/FlxSound.hx:716: characters 17-30 : Warning : flixel.system.FlxSoundGroup was moved to flixel.sound.FlxSoundGroup
source/flixel/system/FlxSound.hx:722: characters 21-25 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/flixel/system/FlxSound.hx:722: characters 21-25 : ... For function argument 'sound'
source/flixel/system/FlxSound.hx:725: characters 15-19 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/flixel/system/FlxSound.hx:725: characters 15-19 : ... For function argument 'sound'
source/editors/ChartingState.hx:1359: characters 24-30 : flixel.system.FlxSound should be flixel.sound.FlxSound
source/editors/ChartingState.hx:1359: characters 24-30 : ... For function argument 'Object'
source/editors/ChartingState.hx:2193: characters 4-42 : flixel.sound.FlxSound should be flixel.system.FlxSound
C:/haxelib/flixel/5,3,1/flixel/ui/FlxButton.hx:259: characters 55-64 : flixel.animation.FlxAnimationController has no field numFrames
source/TitleState.hx:723: characters 7-58 : flixel.sound.FlxSound should be flixel.system.FlxSound
source/TitleState.hx:725: characters 7-58 : flixel.sound.FlxSound should be flixel.system.FlxSound
source/TitleState.hx:729: characters 7-55 : flixel.sound.FlxSound should be flixel.system.FlxSound


phpcs warnings should not be reported as errors

phpcs warnings count as errors, exit with code 1 and break ci builds.
this could be avoided by changing the errorsXPath setting of phpcs.
change phpqa/src/CodeAnalysisTasks.php : 26 from "'errorsXPath' => '//checkstyle/file/error'" to "'errorsXPath' => '//checkstyle/file/error[@severity="error"]'".

You are right, phpqa does not distinguish between errors and warnings.
I think that Jenkins does it too so I have never thought about it.
Would it be okay for you to set "ignore warnings" in .phpqa.yml?

an "ignore warnings" setting in .phpqa.yml would be absolutely fine for me


Fix health check 'command'

#222
The current version of marathon-python (0.9.2) generates COMMAND type protocol healthchecks command property as a string, but current version of marathon expects an object with the 'value' property:
Current:
{
  "protocol": "COMMAND",
  "command":  "curl -f -X GET http://$HOST:$PORT0/health"
}

Expected:
{
  "protocol": "COMMAND",
  "command": { "value": "curl -f -X GET http://$HOST:$PORT0/health" }
}

I can see that all the messages in the package are handled by the logger defined in the marathon/__init__.py, so instead of using the warnings package to issue a DeprecationWarning I would rather user marathon.log.warn() to be in accordance with the rest of the package.
I don't wanna do  a import  marathon because I'd be importing many things I don't need into app.py, but yet it's consistent to make all places that uses the log imports it from the same place.
So my solution was:
Remove import logging and log = logging.getLogger(__name__) from marathon/__init__.py and replace by a call to a function in marathon/util.py called get_log to retrieve the log, so it can be sued anywhere with importing unnecessary thins from marathon/__init__.py.

Just one job failed with a connection error when installing a python dependency.
Can someone run the tests again?
ProtocolError: ("Connection broken: error(104, 'Connection reset by peer')", error(104, 'Connection reset by peer'))
The command "pip install tox" failed and exited with 2 during .


Swift 3

it'd be cool to have a swift 3 version, if you have any interest to create a branch i would like to help with that.

@nschucky @andreacremaschi PR created: https://github.com/andreacremaschi/GEOSwift/pull/27

@vfn do you plan to release a new version soon? Right now I would have to reference master directly to get Swift 3 support.

@falkobuttler please reference tag https://github.com/andreacremaschi/GEOSwift/tree/0.5 on your Podfile. I haven't been able to publish it yet due to issues when pushing it to Cocoapods trunk. I should be releasing it in the next couple of weeks

@nschucky @falkobuttler @andreacremaschi Swift 3 support is now officially available on v0.5.1. Tag https://github.com/andreacremaschi/GEOSwift/tree/0.5.1.
Cocoapods v1.1.1 fixed the issues I was having when publishing the podspec file.


Sync executable with formal spec - NEWEPOCH STS

The exec. spec effectively does
floor (activeSlotCoeeff pp * (floor ((d pp) * SlotsPerEpoch))) - 1

instead of the formal spec's
floor (activeSlotCoeeff pp * ((d pp) * SlotsPerEpoch)))

the exec spec considers the two cases
e_l + 1 /= 1
e_l + 1 == 1

and the formal spec uses two different cases althogether
e  = e_l + 1
e_l /= e + 1

the sd and pd' definitions in the formal spec are hard to recognise in the exec spec

I see if eL' + 1 /= e'     then pure src     else do in the exec spec

I agree that aggregate+ should be translated more clearly, maybe using Relation could be of help here?

I see if eL' + 1 /= e' then pure src else do in the exec spec

thanks, fixed that in the above (but the mismatch remains)


luci-ssl-nginx: fix dependencies

Remove libustream-openssl because Nginx doesn't depend on it.

But other https related packages may depend on that, so adding that small wrapper can still be useful, I think. Otherwise some other packages may try to pull in libustream-mbedtls (which is the default)
cc @Ansuel

@hnyman @dengqf6 it looks like libustream is needed only by uhttpd so think we can drop that dependency

Looking at the source code, also (luci-app-)ddns and (luci-app-)dnscrypt may need at least some libustream version, so it is not quite that clearcut. But as nginx is non-standard, I guess that the users using that will then survive by installing the needed libustream versions manually.
However, as openssl-utils are still installed for key generation, then the large openssl library gets installed in any case and the few additional kilobytes from libustream-openssl wrapper package have no significance.
So, I am still a bit hesitant although you are right, as nginx does not directly depend on libustream-openssl.


Need to fix console errors

Description

fix following console errors

fix opening file upload twice (locally in dev mode)

Verified on staging successfully. No errors in console if to work with settings; attachment functionality.


cannot load such file -- protoc-gen-openapiv2/options/annotations_pb

hi, i try to follow the example but getting this error. could someone help me?
Ruby version:
ruby 2.6.9p207 (2021-11-24 revision 67954) [arm64-darwin21]
Gemfile:
source "https://rubygems.pkg.github.com/flipt-io" do
  gem "flipt-grpc", "1.4.0"
end

gem 'grpc', '1.53.0'

Gemfile.lock:
GEM
  remote: https://rubygems.pkg.github.com/flipt-io/
  specs:
    flipt-grpc (1.4.0)
      grpc (~> 1.0)
    google-protobuf (3.22.2-arm64-darwin)
    googleapis-common-protos-types (1.5.0)
      google-protobuf (~> 3.14)
    grpc (1.53.0)
      google-protobuf (~> 3.21)
      googleapis-common-protos-types (~> 1.0)

PLATFORMS
  ruby

DEPENDENCIES
  flipt-grpc (= 1.4.0)!
  grpc (= 1.53.0)

BUNDLED WITH
   1.17.2

Full error message:
bundler: failed to load command: flipt.rb (flipt.rb)
LoadError: cannot load such file -- protoc-gen-openapiv2/options/annotations_pb
  /Users/dzakaammar/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/flipt-grpc-1.4.0/lib/flipt_pb.rb:8:in `require'
  /Users/dzakaammar/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/flipt-grpc-1.4.0/lib/flipt_pb.rb:8:in `<top (required)>'
  /Users/dzakaammar/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/flipt-grpc-1.4.0/lib/flipt_services_pb.rb:5:in `require'
  /Users/dzakaammar/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/flipt-grpc-1.4.0/lib/flipt_services_pb.rb:5:in `<top (required)>'
  flipt.rb:4:in `require'
  flipt.rb:4:in `<top (required)>'

Hi @dzakaammar 👋 Thanks for bringing this to our attention.
I believe we're running into a similar issue to what is described here: https://github.com/grpc-ecosystem/grpc-gateway/issues/3155
I think some unwanted openapi annotations slipped through the net into our Ruby gem.
Just need to figure out specifically what and where we can move this out into configuration.

I've got a couple PRs up I believe fix the problem.
I ran the example project with this PR and it worked as expected.

Hi @dzakaammar could you try again with gem version v1.4.1 for me?

thank you @GeorgeMac for your help. it's working fine now.

Thanks again for reporting it @dzakaammar 🙌


Emojis in paths are not recognized

I have a file in a path like the following:
/Users/yair/Workspace/firebase-microservices/functions/src/microservice/retailer/⚡onRetailerDB/index.ts
Actual Behavior
It replaces the ⚡ in the path with %E2%9A%A1%EF%B8%8F.
Expected Behavior
To read the path with emojis correctly .
Steps to Reproduce the Problem Or Description
Place a fragment in a folder which has an emoji in his name.
Specifications

GraphQL for VSCode Extension Version: GraphQL Insiders v0.3.5
VSCode Version: 1.62.3
OS Name: Darwin x64
OS Version: 21.1.0
graphql config filename and format example:

module.exports = {
	schema: "https://...",
	documents: "functions/**/*.{graphql,js,ts,jsx,tsx}",
	extensions: {
		endpoints: {
			default: {
				url: "https://...",
				headers: {
					"secret": "...."
				},
			}
		}
	}
};

Logs Of TS Server || GraphQL Language Service

@yairopro we swapped out for a better cross-platform path resolution approach that shouldn't result in these encoding errors, does this issue still exist?


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ccr3dal8e7/clone/recipe/meta.yaml:25: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_ccr3dal8e7/clone/recipe/meta.yaml:25: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ccr3dal8e7/clone/recipe/meta.yaml:36: missing_pip_check: For pypi packages, pip check should be present in the test commands
Errors were found


doc(examples): add string and number condition examples

Description

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

#223  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Mallika05 and the rest of your teammates on  Graphite


Infura configuration for prysm-no-geth

I wonder how to configure an infura endpoint when launching prysm with no geth configuration. Does prysm point by default to https://goerli.prylabs.net?
Should you add http-web3provider in beacon-no-geth.yaml?

Thanks for your inquery!
Prysm's default setting for http-web3provider points to https://goerli.prylabs.net.
Using infura is as simple as using the same flag here and replacing the endpoint with your infura url.

Yes thanks for the confirmation. Maybe that could help for the README to be more explicit on how to use the no geth configuration. For mainnet will Prysm also use a default web3provider?

https://github.com/stefa2k/prysm-docker-compose#i-want-to-use-a-specific-ethereum-1-node


Add support for extended information tags in playlist file

Hi,
Would it be possible for you to insert a dictionary table into the code for '#EXTINF:-1,' as well?  And then the user can edit the table with the matching tvg-id tags. This would allow the script to output a working epg format for iptv simple client. For example the working epg output would need to look as follows:
#EXTINF:-1 tvg-id="I16485.labs.zap2it.com", 01 ESPNews
#EXTINF:-1 tvg-id="I10179.labs.zap2it.com", 02 ESPN
(Where as the table allows for me to insert my tvg-id tags right before the comma of #EXTINF:-1,)
Thanks in advance if possible!

I second this!

Hi @MB004 @dbowles1975, thanks for your input.
Forgive my ignorance, but can you provide more information on what you'd like to see happening here?  The way I'm reading your question is that you would like a JSON-like dictionary of tvg-id tags, to be inserted at the correct index into the m3u8.
For example, the dictionary would look like this (using your example):
tvgDictionary = {
'01': 'I16485.labs.zap2it.com',
'02': 'I10179.labs.zap2it.com',
...
}

and at the time of playlist creation, the tvg-id tags are inserted by index (channel number).
for channel in sorted(channelDictionary, key=lambda channel: int(channel)):
    m3u8 += ('#EXTINF:-1, ' + 'tvg-id="' + tvgDictionary[channel] + '", ' +
            channel + ' ' + channelDictionary[channel] +
            '\n' + 'http://' + server +
            '.smoothstreams.tv:9100/viewstvn/ch' + channel +
            'q1.stream/playlist.m3u8?wmsAuthSign=' + authSign + '\n')

resulting in a playlist looking like this:
#EXTM3U
#EXTINF:-1, tvg-id="I16485.labs.zap2it.com", 01 ESPNews
http://dna.smoothstreams.tv:9100/viewstvn/ch01q1.stream/playlist.m3u8?wmsAuthSign=abcd1234efgh5678ijkl90==
#EXTINF:-1, tvg-id="I10179.labs.zap2it.com", 02 ESPN
http://dna.smoothstreams.tv:9100/viewstvn/ch02q1.stream/playlist.m3u8?wmsAuthSign=abcd1234efgh5678ijkl90==

Is that what you're looking for?  If not, please clarify.  Thanks again for taking the time to submit a request like this.  Cheers!

Hey stvhwrd,
Thanks for the reply and for all your work!
That was exactly what I was looking for. This format allows iptv simple client to correctly associate the playlist to  a xmltv file for epg data. For example, I added your new code addition to the generator, filled in all of the linking tags to my xmltv file and get this desired output in kodi :
https://gyazo.com/bb88074bfc17de42237d49b39c2fa069
The only caveat seems to be if a channel is turned on in the channeldictionary, it must also be turned on in the tvgdictionary or the generator will fail. This is no problem though. If for example I do not have epg data for channel 118 (Sky Sports F1 UK) and end up with this output:
#EXTINF:-1, tvg-id="insert tag here", 118 Sky Sports F1 UK
The channel will still play correctly (without any epg info of course)
Thanks!

Please forgive my ignorance as I am not a Python person but I have tried to make the changes myself and I cannot get the script to run (runs fine without any changes). I am sure I'm overlooking something simple. Could anyone offer some assistance? Thanks.

Hi @dbowles1975, sorry for the delay in response, I overlooked your message.  I'll be working on this again later this week and weekend.   In the meantime, perhaps @MB004 could share his working script with you?  Thanks for your engagement in this project.  Stay tuned for updates this week.  Cheers 🍻

Hey, sorry about that also lost track of this topic. I've attached my working script. I updated a few of the channels (ie, 76-83 now seem to be dedicated HD versions of previous channels and 108-111 I think are always the BT channels).
So now paste any relevant epg tags into the corresponding channel number of the tvgDictionary. Put it right between the two quotation marks like so:
'01': 'I16485.labs.zap2it.com',
If` you don't have a tag for a certain channel just leave it as is.  If you want to turn off any channels that SS doesn't use, make sure you turn it off in both the channel and tvg dictionaries or the script will fail.
Don't forget to edit in your login info and server choice, I almost forgot to remove mine =)
sstv-playlist epg tags.zip

I've decided to close this issue.  There are a couple of notable forks of this project (stankness on BitBucket, and bradmurray on GitHub that provide the enhancements called for by this issue.  Rather than mirroring the changes in those forks, I'd like to keep this project as a simple script base that people can build cool stuff off of (with those forks being great examples of that).
Thanks @MB004 and @dbowles1975 for your input, hope you guys are cool with this decision.


shape_coloring.rb - I believe there is a very, very small(ish) bug, not sure if worthy to fix it, but at the least it should be reported

Hey there Andy,
I just tested shape_coloring.rb.
It works and is quite neat. glimmer-dsl-libui is like going the way for kids-drawing sketches! :D
Would be fun if the whole glimmer-suite becomes like a kids-platform (aka to use it to create stuff, even without being
a programmer), but I digress.
The basic functionality of shape_coloring.rb works fine, but I noticed one small problem with the ... bezier ellipsoid
thingy. The shape on the bottom right.
I believe it is best to show an image here, I will link in from imgur (not sure whether you can embed directly in github
issue requests but I hope this link in is no big bother, on my linux machine I can mouse middle-click and it opens
in a new tab):
https://i.imgur.com/ReXOxwa.png
I am not sure if you can instantly spot the problem, so let me also describe it.
On that image you can see that I have selected the most bototm right shape. It's a bit like a half-circle thingy, not
sure how it is called ... other than a half-circle. :P (But it reminds me a bit of these bezier curves too, my memory
is probably contaminated with GIMP tutorials from years ago...)
The curved area is correctly selected via red. But the upper area is not selected red at all, so I assume the code
currently does not include these parts. But I think the code works fine in general, because the full circle, when I
click on it, correctly has ALL of its border red, thus indicating the selection. The other objects all work fine, so
only that half-circle thingy for some reason does not correctly highlight everything; the full circle does, though,
which is peculiar.
Not sure if it is worth to report this tiny bug but either way I think reporting is bettter at the least just so that you
know. And perhaps you get a weekend with beer to fix things in the future! \o/
PS: One reason I mentioned kids is not solely due to glimmer, but I remember _why used to have his comics
kind of relate to a younger audience too, and before he quit, things such as the original shoes KIND of tap
into that. And the turtle drawing program if you know that, e. g. where kids can tell the turtle to move, or rather
to input commands that is then drawn into bars and circles and stuff. So that's why it reminded me ... glimmer
reminds me a bit of the original shoes in some ways. I wonder if _why ever contacted you. I know baweaver
did, the original badger. :P

Oh yes, I forgot, just for quick copy/paste, or if anyone else wants to test, here is the code as-is, I got it from the official webpage for glimmer libui:
require 'glimmer-dsl-libui'

class ShapeColoring
  include Glimmer::LibUI::Application

  COLOR_SELECTION = Glimmer::LibUI.interpret_color(:red)

  before_body {
    @shapes = []
  }

  body {
    window('Shape Coloring', 200, 200) {
      margined false

      grid {
        label("Click a shape to select and\nchange color via color button") {
          left 0
          top 0
          hexpand true
          halign :center
          vexpand false
        }

        color_button { |cb|
          left 0
          top 1
          hexpand true
          vexpand false

          on_changed do
            @selected_shape&.fill = cb.color
          end
        }

        area {
          left 0
          top 2
          hexpand true
          vexpand true

          rectangle(0, 0, 600, 400) { # background shape
            fill :white
          }

          @shapes << colorable(:rectangle, 20, 20, 40, 20) {
            fill :lime
          }

          @shapes << colorable(:square, 80, 20, 20) {
            fill :blue
          }

          @shapes << colorable(:circle, 75, 70, 20) {
            fill :green
          }

          @shapes << colorable(:arc, 120, 70, 40, 0, 145) {
            fill :orange
          }

          @shapes << colorable(:polygon, 120, 10, 120, 50, 150, 10, 150, 50) {
            fill :cyan
          }

          @shapes << colorable(:polybezier, 20, 40,
                     30, 100, 50, 80, 80, 110,
                     40, 120, 20, 120, 30, 91) {
            fill :pink
          }
        }
      }
    }
  }

  def colorable(shape_symbol, *args, &content)
    send(shape_symbol, *args) do |shape|
      on_mouse_up do |area_mouse_event|
        old_stroke = Glimmer::LibUI.interpret_color(shape.stroke).slice(:r, :g, :b)
        @shapes.each {|sh| sh.stroke = nil}
        @selected_shape = nil
        unless old_stroke == COLOR_SELECTION
          shape.stroke = COLOR_SELECTION.merge(thickness: 2)
          @selected_shape = shape
        end
      end

      content.call(shape)
    end
  end
end

ShapeColoring.launch

Hi @rubyFeedback,
Thank you for your feedback.
The good news is what you ask for in the case of "Glimmer for Kids" and turtle graphics already exists in the DCR Programming Language (written using Glimmer DSL for SWT), which is short for Draw Color Repeat.

I'd be happy to port it into Glimmer DSL for LibUI.
The shape you mentioned is in fact an arc, which is a part of a circle, so you were almost right about calling it half circle, though the arc angle is less than half of a circle (145 degrees only, not 180 degress as required by half circles).
SWT supports drawing an arc with a stroked border around its inner area. C libui does not currently support that, which is why when you stroke it, you do not see a red border on the inside of the arc.
You are welcome to open this as an issue in C libui.


create_predictor or forward？ Difference & applicable scenarios？

In MoiraiForecast, you have implemented both create_predictor and forward.  What is the difference between these two methods, and if there are differences, what scenarios should they be used in respectively?
At the same time, in the directory src/uni2ts/model/moirai, there is a file named module.py. Additionally, there are three files named pretrain, finetune, and forecast, each defining a different class such as MoiraiPretrain. If one wishes to use a pre-trained model to obtain the model's output, what differences would there be in calling these three? It seems that the inputs in their forward methods are also different?

forward implements the standard pytorch forward function for forecasting.
create_predictor returns a gluonts Predictor object, which applies will apply various data transformations given a dataset, and return an iterator of predictions.
MoiraiPretrain is used specifically for the pre-training phase. The transformations applied are different, and will not return a nicely formatted prediction.

Thank you for your reply. I can guess and understand their general functions from their names. I would like to confirm that, apart from the differences in various transformations of the dataset, they should be consistent in the computational process.


[ClickHouseResultSet.java] Require null check.

Line 222:
@Override
public BigDecimal getBigDecimal(int index) throws SQLException {
  Object data = getObject(index);
  return new BigDecimal(data.toString());  // data may be null
 }

Line 238:
@Override
 public byte[] getBytes(int index) throws SQLException {
  String data = (String) getObject(index);
  return data.getBytes(cfg.charset());  // data may be null
}

Good catch! @gmxyb
Would you like to send a PR to fix it? Just follow below steps:

fork repo (I believe you have done it)
git clone [your repo url]
git remote add upstream https://github.com/housepower/ClickHouse-Native-JDBC.git
git fetch upstream
git branch --set-upstream-to=upstream/master master
Checkout branch from latest master branch git checkout -b gh-251
Then modify the code, don't forget add unit test to verify your code.
If all things looks great, commit you code with meaningful comment.
Then push the branch to your repo
Go to Github page, then you will see a tips for send a Pull Request, just follow it!

You can find more details at Contributing Guide

partial fixed by #256