text:
Fastlane Unable to repair provisioning profile with API_Keys and prompting for username and password

New Issue Checklist

[ ] 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
Fastlane Unable to repair provisioning profile with API_Keys and prompting for username and password  even though i'm not passing username and password in command
Command executed
fastlane sigh repair --force --api_key_path "AppleConnectAPI/XYZ_InHouse.json" --team_id ******
Complete output when running fastlane, including the stack trace and command used
[✔] 🚀
[06:37:51]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[06:37:53]: To not be asked about this value, you can specify it using 'username'
[06:37:53]: Your Apple ID Username:

 [REPLACE THIS WITH YOUR INFORMATION]

Environment
[06:30:17]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[06:30:19]: Generating fastlane environment output, this might take a few seconds...
✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.5

Ruby
2.6.0

Bundler?
false

Git
git version 2.21.0

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

Host
Mac OS X 10.15.5 (19F101)

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

OpenSSL Version
OpenSSL 1.1.1b  26 Feb 2019

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
11.4

System Locale

Variable
Value

LANG

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.172.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

executable-hooks
1.6.0

bundler-unload
1.0.2

rubygems-bundler
1.4.5

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

terminal-table
1.8.0

multipart-post
2.0.0

word_wrap
1.0.0

artifactory
3.0.15

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

faraday-net_http
1.0.1

ruby2_keywords
0.0.2

faraday
1.3.0

faraday_middleware
1.0.0

gh_inspector
1.1.3

rubyzip
2.3.0

security
0.1.3

uber
0.1.0

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

httpclient
2.8.3

google-api-client
0.38.0

nanaimo
0.3.0

colored2
3.1.2

claide
1.0.3

CFPropertyList
3.0.3

atomos
0.1.3

xcodeproj
1.19.0

unicode-display_width
1.7.0

plist
3.6.0

public_suffix
4.0.6

addressable
2.7.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.4

excon
0.78.1

unf_ext
0.0.7.7

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

fastimage
2.2.1

json
2.2.0

mini_magick
4.11.0

xcpretty-travis-formatter
1.0.1

dotenv
2.7.6

bundler
2.0.1

naturally
2.2.0

simctl
1.6.8

jwt
2.2.2

declarative
0.0.20

mini_mime
1.0.2

multi_json
1.15.0

signet
0.14.0

os
1.1.1

memoist
0.16.2

googleauth
0.14.0

rake
12.3.2

digest-crc
0.6.3

google-cloud-errors
1.0.1

google-cloud-env
1.4.0

google-cloud-core
1.5.0

google-cloud-storage
1.29.2

emoji_regex
3.2.1

aws-eventstream
1.1.0

aws-sigv4
1.2.2

aws-partitions
1.416.0

jmespath
1.4.0

aws-sdk-core
3.111.0

aws-sdk-kms
1.41.0

aws-sdk-s3
1.87.0

forwardable
1.2.0

logger
1.3.0

date
2.0.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

fileutils
1.2.0

mini_portile2
2.4.0

nokogiri
1.10.2

rexml
3.2.0

psych
3.1.0

mutex_m
0.1.0

generated on: 2021-01-22

 [REPLACE THIS WITH YOUR INFORMATION]

There is no official statement from Apple for reparing profiles with App Store Connect API. ( download_all or creating new one would work, but not for 'repairing' profiles.)
Official Doc
https://developer.apple.com/documentation/appstoreconnectapi/profiles?changes=latest_major
Fastlane repair_provisioning_profile! method requires Spaceship.login
https://github.com/fastlane/fastlane/blob/48151291f2c4949c3b1b9919ba2cc81a7cc33293/sigh/lib/sigh/repair.rb#L9

authors: dokimyj nawaahme


text:
gym not respecting export_options when use_legacy_build_api is true

          Original issue by @cbowns - Imported from fastlane/gym#231

I've got a lane for exporting a build for Test Flight upload that goes as follows:
  lane :test_flight do
    match(type: "appstore")

    # use the UDID of the newly created provisioning profile
    ENV["PROFILE_UDID"] = lane_context[SharedValues::SIGH_UDID]

    # build the app.
    gym(
      scheme: "Inspire",
      use_legacy_build_api: true
      )
  end

gym seems like it receives my implicit "appstore" request:
[15:41:37]: -----------------
[15:41:37]: --- Step: gym ---
[15:41:37]: -----------------
[15:41:37]: Using legacy build system - waiting for radar to be fixed: https://openradar.appspot.com/radar?id=4952000420642816
[15:41:37]: xcrun xcodebuild -list -workspace 'Inspire.xcworkspace'

+----------------------+----------------------+
|            Summary for gym 1.6.1            |
+----------------------+----------------------+
| scheme               | Inspire              |
| use_legacy_build_api | true                 |
| export_method        | app-store            |
| sdk                  | iphoneos             |
| workspace            | Inspire.xcworkspace  |
| clean                | true                 |
| output_directory     | ./fastlane/builds    |
| output_name          | Inspire_Utility      |
| destination          | generic/platform=iOS |
| silent               | false                |
| buildlog_path        | ~/Library/Logs/gym   |
+----------------------+----------------------+

(Note: export_method above is app-store, as desired.)
However, when I open the .ipa it produces:
[15:45:55]: Successfully exported and compressed dSYM file
[15:45:55]: Successfully exported and signed the ipa file:
[15:45:55]: /Users/cbowns/Development/crlf/carrot-sense/utility-iOS/fastlane/builds/Inspire_Utility.ipa

# cd ~/Desktop
# cp /Users/cbowns/Development/crlf/carrot-sense/utility-iOS/fastlane/builds/Inspire_Utility.ipa ~/Desktop
# unzip ~/Desktop/Inspire_Utility.ipa

# codesign -d -vv Payload/Inspire.app
Executable=/Users/cbowns/Desktop/Payload/Inspire.app/Inspire
Identifier=com.carrotsense.Inspire.utility
Format=bundle with Mach-O universal (armv7 arm64)
CodeDirectory v=20200 size=18095 flags=0x0(none) hashes=895+5 location=embedded
Signature size=4364
Authority=iPhone Developer: Carrot-Sense Developer (LAG42SBR79)
Authority=Apple Worldwide Developer Relations Certification Authority
Authority=Apple Root CA
Signed Time=Mar 2, 2016, 3:45:43 PM
Info.plist entries=31
TeamIdentifier=L3WD573F5U
Sealed Resources version=2 rules=12 files=58
Internal requirements count=1 size=204

The build is still development-signed: Authority=iPhone Developer: Carrot-Sense Developer (LAG42SBR79)
(For ease of viewing, from ProvisioningQL:

I manually exported another app copy from the archive in Xcode, and Xcode gave me the desired distribution-signed build:
# codesign -d -vv Payload/Inspire.app
Executable=/Users/cbowns/Desktop/Inspire 2016-03-02 15-29-49/Payload/Inspire.app/Inspire
Identifier=com.carrotsense.Inspire.utility
Format=bundle with Mach-O universal (armv7 arm64)
CodeDirectory v=20200 size=18095 flags=0x0(none) hashes=895+5 location=embedded
Signature size=4362
Authority=iPhone Distribution: Carrot Sense, Inc (L3WD573F5U)
Authority=Apple Worldwide Developer Relations Certification Authority
Authority=Apple Root CA
Signed Time=Mar 2, 2016, 3:29:42 PM
Info.plist entries=31
TeamIdentifier=L3WD573F5U
Sealed Resources version=2 rules=12 files=58
Internal requirements count=1 size=200

Screenshot:

The punchline: gym clearly knew I wanted an app-store build, but failed to actually create one. How can I find out why? And how can I get it to actually do an app-store build?

@mpirri I know the repo migration generated a lot of noise. I added more info about our build configs.

To come back to the original issue: You can't provide the export_options when you use the legacy build API, since the legacy build API from Xcode doesn't support it

how does gym export the build when using legacy_build_api?

I'm harping on this issue a bit, because this worked flawlessly in two projects just a few weeks ago, and fell apart sometime recently.

Yes, I still need to use use_legacy_build_api. (Just tried without it in Xcode 7.3.1 and it failed.)
I don't actually know if this is an issue.

Yeah, I think we can close this.

Thanks 👍

source: gharchive/issue

authors: KrauseFx cbowns fastlane-bot-helper

repo: fastlane/fastlane

license: MIT

license_type: permissive

license_source: github-api


text:
Google Api Error: Invalid request - Some of the Android App Bundle uploads are not completed yet.

New Issue Checklist

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

Issue Description
We're using the supply Fastlane action as part of a lane which is executed from our GitHub Actions CI workflow. supply started failing with the error: Google Api Error: Invalid request - Some of the Android App Bundle uploads are not completed yet. just today, seemingly only when release_status is set to completed. I repeatedly tried to re-run the workflow, but had no success. Once release_status was changed to draft, the lane ran successfully. Perhaps this is just a momentary server blip, or a more significant error?
Our Fastfile has otherwise run successfully every week for months with no modification.
Command executed
bundle exec fastlane distribute_play_internal, which executes grade and supply (see Fastfile below).
Complete output when running fastlane, including the stack trace and command used
I've omitted anything sensitive from this output and trimmed out a few repeated Gradle build log lines.

2023-03-10T15:49:37.3044923Z ##[group]Run cd androidApp
2023-03-10T15:49:37.3045334Z cd androidApp
2023-03-10T15:49:37.3045671Z bundle exec fastlane distribute_play_internal
2023-03-10T15:49:37.3099111Z shell: /usr/bin/bash -e {0}
2023-03-10T15:49:37.3099593Z env:
2023-03-10T15:49:37.3123574Z   JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/17.0.6-10/x64
2023-03-10T15:49:37.3124070Z   JAVA_HOME_17_X64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/17.0.6-10/x64
2023-03-10T15:49:37.3124840Z   PATH: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/17.0.6-10/x64/bin:/home/runner/.local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/composer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/snap/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
2023-03-10T15:49:37.3130956Z ##[endgroup]
2023-03-10T15:49:38.9785025Z +-------------------------------------------+---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
2023-03-10T15:49:38.9786991Z |                                                                                Used plugins                                                                                |
2023-03-10T15:49:38.9788489Z +-------------------------------------------+---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
2023-03-10T15:49:38.9838933Z | Plugin                                    | Version | Action                                                                                |
2023-03-10T15:49:38.9840126Z +-------------------------------------------+---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
2023-03-10T15:49:38.9841418Z | fastlane-plugin-firebase_app_distribution | 0.5.0   | firebase_app_distribution_get_udids, firebase_app_distribution, firebase_app_distribution_get_latest_release, firebase_app_distribution_add_testers, firebase_app_distribution_remove_testers                                    |
2023-03-10T15:49:38.9842657Z | fastlane-plugin-sentry                    | 1.15.0  | sentry_upload_sourcemap, sentry_upload_proguard, sentry_finalize_release, sentry_upload_dif, sentry_set_commits, sentry_upload_dsym, sentry_check_cli_installed, sentry_create_deploy, sentry_upload_file, sentry_create_release |
2023-03-10T15:49:38.9844185Z +-------------------------------------------+---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
2023-03-10T15:49:38.9844753Z
2023-03-10T15:49:38.9844934Z [15:49:38]: Sending anonymous analytics information
2023-03-10T15:49:38.9845342Z [15:49:38]: Learn more at https://docs.fastlane.tools/#metrics
2023-03-10T15:49:38.9845737Z [15:49:38]: No personal or sensitive data is sent.
2023-03-10T15:49:38.9846135Z [15:49:38]: You can disable this by adding `opt_out_usage` at the top of your Fastfile
2023-03-10T15:49:38.9857196Z [15:49:38]: ------------------------------
2023-03-10T15:49:38.9935568Z [15:49:38]: --- Step: default_platform ---
2023-03-10T15:49:38.9936033Z [15:49:38]: ------------------------------
2023-03-10T15:49:38.9936564Z [15:49:38]: Driving the lane 'android distribute_play_internal' 🚀
2023-03-10T15:49:38.9937040Z [15:49:38]: -------------------------------------
2023-03-10T15:49:38.9937492Z [15:49:38]: --- Step: clean bundleProdRelease ---
2023-03-10T15:49:38.9937933Z [15:49:38]: -------------------------------------
2023-03-10T15:49:38.9938455Z [15:49:38]: $ /home/runner/work/mobile/mobile/gradlew clean bundleProdRelease -p .
2023-03-10T15:49:45.6980956Z [15:49:45]: ▸ Welcome to Gradle 8.0!
2023-03-10T15:49:45.6981584Z [15:49:45]: ▸ For more details see https://docs.gradle.org/8.0/release-notes.html
2023-03-10T15:49:46.9962443Z [15:49:46]: ▸ Starting a Gradle Daemon (subsequent builds will be faster)
2023-03-10T15:50:07.8971080Z [15:50:07]: ▸ > Task :build-logic:pluginDescriptors
2023-03-10T15:50:07.9959729Z [15:50:07]: ▸ > Task :build-logic:processResources
2023-03-10T15:50:15.8967468Z [15:50:15]: ▸ > Task :build-logic:compileKotlin
2023-03-10T15:50:15.8971907Z [15:50:15]: ▸ > Task :build-logic:compileJava NO-SOURCE
2023-03-10T15:50:15.8972394Z [15:50:15]: ▸ > Task :build-logic:classes
2023-03-10T15:50:15.8972953Z [15:50:15]: ▸ > Task :build-logic:jar
2023-03-10T15:50:15.8973524Z [15:50:15]: ▸ > Task :build-logic:inspectClassesForKotlinIC
2023-03-10T15:50:16.5963489Z [15:50:16]: ▸ > Configure project :shared:api
2023-03-10T15:50:16.5964115Z [15:50:16]: ▸ Please wait while Kotlin/Native compiler 1.8.10 is being installed.
2023-03-10T15:50:17.2963459Z [15:50:17]: ▸ Download https://download.jetbrains.com/kotlin/native/builds/releases/1.8.10/linux-x86_64/kotlin-native-prebuilt-linux-x86_64-1.8.10.tar.gz (180.45 MB)
2023-03-10T15:50:17.2984656Z [15:50:17]: ▸ Download https://download.jetbrains.com/kotlin/native/builds/releases/1.8.10/linux-x86_64/kotlin-native-prebuilt-linux-x86_64-1.8.10.tar.gz finished, took 13 ms
2023-03-10T15:50:17.2985792Z [15:50:17]: ▸ Unpack Kotlin/Native compiler to /home/runner/.konan/kotlin-native-prebuilt-linux-x86_64-1.8.10
2023-03-10T15:50:20.3963179Z [15:50:20]: ▸ Unpack Kotlin/Native compiler to /home/runner/.konan/kotlin-native-prebuilt-linux-x86_64-1.8.10 finished, took 3 s 120 ms
2023-03-10T15:50:27.1061051Z [15:50:27]: ▸ > Task :shared:app:preBuild UP-TO-DATE
2023-03-10T15:50:32.7970392Z [15:50:32]: ▸ > Task :shared:colors:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:32.7971281Z [15:50:32]: ▸ > Task :shared:configuration:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:32.7971999Z [15:50:32]: ▸ > Task :shared:environment:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:32.7972921Z [15:50:32]: ▸ > Task :shared:formatters:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:32.7973910Z [15:50:32]: ▸ > Task :shared:settings:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:32.7974807Z [15:50:32]: ▸ > Task :shared:utils:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:32.7975506Z [15:50:32]: ▸ > Task :shared:api:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:32.7976371Z [15:50:32]: ▸ > Task :shared:api:generateReleaseBuildConfig
2023-03-10T15:50:32.9958519Z [15:50:32]: ▸ > Task :shared:api:parseReleaseLocalResources
2023-03-10T15:50:33.1957498Z [15:50:33]: ▸ > Task :shared:api:generateReleaseRFile
2023-03-10T15:50:33.1958415Z [15:50:33]: ▸ > Task :shared:api:checkApolloVersions
2023-03-10T15:50:37.2957710Z [15:50:37]: ▸ > Task :androidApp:mergeProdReleaseResources
2023-03-10T15:50:37.2959310Z [15:50:37]: ▸ /home/runner/.gradle/caches/transforms-3/daa37936a05fcc21d77d2c55f5e20c64/transformed/material-1.4.0/res/values/values.xml:575:4: Multiple substitutions specified in non-positional format of string resource string/page_accessibility. Did you mean to add the formatted="false" attribute?
2023-03-10T15:50:38.4957067Z [15:50:38]: ▸ > Task :shared:api:generateServiceApolloSources
2023-03-10T15:50:39.8966308Z [15:50:39]: ▸ > Task :checkServiceApolloDuplicates
2023-03-10T15:50:49.7969322Z [15:50:49]: ▸ > Task :shared:baseviewmodel:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:49.8968196Z [15:50:49]: ▸ > Task :shared:featureflags:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:49.8969006Z [15:50:49]: ▸ > Task :shared:localization:compileReleaseAidl NO-SOURCE
2023-03-10T15:50:59.4955030Z [15:50:59]: ▸ > Task :androidApp:packageProdReleaseResources
2023-03-10T15:50:59.8957231Z [15:50:59]: ▸ > Task :androidApp:parseProdReleaseLocalResources
2023-03-10T15:50:59.9955465Z [15:50:59]: ▸ > Task :androidApp:processProdReleaseManifestForPackage
2023-03-10T15:51:02.9956602Z [15:51:02]: ▸ > Task :androidApp:processProdReleaseResources
2023-03-10T15:51:02.9957491Z [15:51:02]: ▸ > Task :androidApp:javaPreCompileProdRelease
2023-03-10T15:51:02.9958134Z [15:51:02]: ▸ > Task :androidApp:processProdReleaseJavaRes NO-SOURCE
2023-03-10T15:51:02.9958801Z [15:51:02]: ▸ > Task :shared:api:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:02.9959433Z [15:51:02]: ▸ > Task :shared:app:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:02.9960074Z [15:51:02]: ▸ > Task :shared:baseviewmodel:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:02.9960722Z [15:51:02]: ▸ > Task :shared:baseviewmodel:bundleLibResRelease
2023-03-10T15:51:02.9961624Z [15:51:02]: ▸ > Task :shared:colors:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:02.9962226Z [15:51:02]: ▸ > Task :shared:colors:bundleLibResRelease
2023-03-10T15:51:02.9962891Z [15:51:02]: ▸ > Task :shared:configuration:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.0961070Z [15:51:03]: ▸ > Task :shared:configuration:bundleLibResRelease
2023-03-10T15:51:03.0962206Z [15:51:03]: ▸ > Task :shared:domainshared:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.0963152Z [15:51:03]: ▸ > Task :shared:environment:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.0964396Z [15:51:03]: ▸ > Task :shared:environment:bundleLibResRelease
2023-03-10T15:51:03.0965029Z [15:51:03]: ▸ > Task :shared:featureflags:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.0965592Z [15:51:03]: ▸ > Task :shared:featureflags:bundleLibResRelease
2023-03-10T15:51:03.0983653Z [15:51:03]: ▸ > Task :shared:featureitemdetail:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.0984748Z [15:51:03]: ▸ > Task :shared:formatters:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.0985576Z [15:51:03]: ▸ > Task :shared:formatters:bundleLibResRelease
2023-03-10T15:51:03.0987302Z [15:51:03]: ▸ > Task :shared:localization:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.0988041Z [15:51:03]: ▸ > Task :shared:localization:bundleLibResRelease
2023-03-10T15:51:03.0988693Z [15:51:03]: ▸ > Task :shared:settings:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.0989403Z [15:51:03]: ▸ > Task :shared:settings:bundleLibResRelease
2023-03-10T15:51:03.1214923Z [15:51:03]: ▸ > Task :shared:utils:processReleaseJavaRes NO-SOURCE
2023-03-10T15:51:03.1215508Z [15:51:03]: ▸ > Task :shared:utils:bundleLibResRelease
2023-03-10T15:51:03.3982830Z [15:51:03]: ▸ > Task :androidApp:collectExternalProdReleaseDependenciesForSentry
2023-03-10T15:51:03.4970362Z [15:51:03]: ▸ > Task :androidApp:mergeProdReleaseShaders
2023-03-10T15:51:03.4971401Z [15:51:03]: ▸ > Task :androidApp:compileProdReleaseShaders NO-SOURCE
2023-03-10T15:51:03.4972525Z [15:51:03]: ▸ > Task :androidApp:generateProdReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.4973357Z [15:51:03]: ▸ > Task :androidApp:generateSentryProguardUuidProdRelease
2023-03-10T15:51:03.4974155Z [15:51:03]: ▸ > Task :shared:api:mergeReleaseShaders
2023-03-10T15:51:03.4974935Z [15:51:03]: ▸ > Task :shared:api:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.4975640Z [15:51:03]: ▸ > Task :shared:api:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.4976306Z [15:51:03]: ▸ > Task :shared:api:packageReleaseAssets
2023-03-10T15:51:03.4976959Z [15:51:03]: ▸ > Task :shared:app:mergeReleaseShaders
2023-03-10T15:51:03.4977636Z [15:51:03]: ▸ > Task :shared:app:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.4978391Z [15:51:03]: ▸ > Task :shared:app:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.4979644Z [15:51:03]: ▸ > Task :shared:app:packageReleaseAssets
2023-03-10T15:51:03.6035110Z [15:51:03]: ▸ > Task :shared:baseviewmodel:mergeReleaseShaders
2023-03-10T15:51:03.6036293Z [15:51:03]: ▸ > Task :shared:baseviewmodel:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.6037156Z [15:51:03]: ▸ > Task :shared:baseviewmodel:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.6037969Z [15:51:03]: ▸ > Task :shared:baseviewmodel:packageReleaseAssets
2023-03-10T15:51:03.6038708Z [15:51:03]: ▸ > Task :shared:colors:mergeReleaseShaders
2023-03-10T15:51:03.6039544Z [15:51:03]: ▸ > Task :shared:colors:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.6040310Z [15:51:03]: ▸ > Task :shared:colors:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.6041005Z [15:51:03]: ▸ > Task :shared:colors:packageReleaseAssets
2023-03-10T15:51:03.6041897Z [15:51:03]: ▸ > Task :shared:configuration:mergeReleaseShaders
2023-03-10T15:51:03.6042611Z [15:51:03]: ▸ > Task :shared:configuration:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.6043359Z [15:51:03]: ▸ > Task :shared:configuration:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.6044145Z [15:51:03]: ▸ > Task :shared:configuration:packageReleaseAssets
2023-03-10T15:51:03.6045450Z [15:51:03]: ▸ > Task :shared:domainshared:mergeReleaseShaders
2023-03-10T15:51:03.6046166Z [15:51:03]: ▸ > Task :shared:domainshared:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.6046893Z [15:51:03]: ▸ > Task :shared:domainshared:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.6970239Z [15:51:03]: ▸ > Task :shared:domainshared:packageReleaseAssets
2023-03-10T15:51:03.6971488Z [15:51:03]: ▸ > Task :shared:environment:mergeReleaseShaders
2023-03-10T15:51:03.6972513Z [15:51:03]: ▸ > Task :shared:environment:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.6973414Z [15:51:03]: ▸ > Task :shared:environment:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.6974440Z [15:51:03]: ▸ > Task :shared:environment:packageReleaseAssets
2023-03-10T15:51:03.6975220Z [15:51:03]: ▸ > Task :shared:featureflags:mergeReleaseShaders
2023-03-10T15:51:03.6976272Z [15:51:03]: ▸ > Task :shared:featureflags:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.6977112Z [15:51:03]: ▸ > Task :shared:featureflags:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.6977877Z [15:51:03]: ▸ > Task :shared:featureflags:packageReleaseAssets
2023-03-10T15:51:03.7981863Z [15:51:03]: ▸ > Task :shared:featureitemdetail:mergeReleaseShaders
2023-03-10T15:51:03.7982883Z [15:51:03]: ▸ > Task :shared:featureitemdetail:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.7983761Z [15:51:03]: ▸ > Task :shared:featureitemdetail:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.7984591Z [15:51:03]: ▸ > Task :shared:featureitemdetail:packageReleaseAssets
2023-03-10T15:51:03.7985354Z [15:51:03]: ▸ > Task :shared:formatters:mergeReleaseShaders
2023-03-10T15:51:03.7986289Z [15:51:03]: ▸ > Task :shared:formatters:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.7987256Z [15:51:03]: ▸ > Task :shared:formatters:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.7987933Z [15:51:03]: ▸ > Task :shared:formatters:packageReleaseAssets
2023-03-10T15:51:03.7988592Z [15:51:03]: ▸ > Task :shared:localization:mergeReleaseShaders
2023-03-10T15:51:03.7989346Z [15:51:03]: ▸ > Task :shared:localization:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.7990155Z [15:51:03]: ▸ > Task :shared:localization:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.7990864Z [15:51:03]: ▸ > Task :shared:localization:packageReleaseAssets
2023-03-10T15:51:03.7991706Z [15:51:03]: ▸ > Task :shared:settings:mergeReleaseShaders
2023-03-10T15:51:03.7992481Z [15:51:03]: ▸ > Task :shared:settings:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.7994324Z [15:51:03]: ▸ > Task :shared:settings:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.8966573Z [15:51:03]: ▸ > Task :shared:settings:packageReleaseAssets
2023-03-10T15:51:03.8967499Z [15:51:03]: ▸ > Task :shared:utils:mergeReleaseShaders
2023-03-10T15:51:03.8968267Z [15:51:03]: ▸ > Task :shared:utils:compileReleaseShaders NO-SOURCE
2023-03-10T15:51:03.8969075Z [15:51:03]: ▸ > Task :shared:utils:generateReleaseAssets UP-TO-DATE
2023-03-10T15:51:03.8969829Z [15:51:03]: ▸ > Task :shared:utils:packageReleaseAssets
2023-03-10T15:51:04.1955891Z [15:51:04]: ▸ > Task :androidApp:mergeProdReleaseAssets
2023-03-10T15:51:04.2975200Z [15:51:04]: ▸ > Task :androidApp:mergeProdReleaseJniLibFolders
2023-03-10T15:51:04.2976159Z [15:51:04]: ▸ > Task :shared:api:mergeReleaseJniLibFolders
2023-03-10T15:51:04.2977227Z [15:51:04]: ▸ > Task :shared:api:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.2978146Z [15:51:04]: ▸ > Task :shared:api:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.2978906Z [15:51:04]: ▸ > Task :shared:app:mergeReleaseJniLibFolders
2023-03-10T15:51:04.2979793Z [15:51:04]: ▸ > Task :shared:app:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.2980500Z [15:51:04]: ▸ > Task :shared:app:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.2981329Z [15:51:04]: ▸ > Task :shared:baseviewmodel:mergeReleaseJniLibFolders
2023-03-10T15:51:04.3968328Z [15:51:04]: ▸ > Task :shared:baseviewmodel:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.3969343Z [15:51:04]: ▸ > Task :shared:baseviewmodel:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.3970141Z [15:51:04]: ▸ > Task :shared:colors:mergeReleaseJniLibFolders
2023-03-10T15:51:04.3970925Z [15:51:04]: ▸ > Task :shared:colors:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.3971747Z [15:51:04]: ▸ > Task :shared:colors:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.3972532Z [15:51:04]: ▸ > Task :shared:configuration:mergeReleaseJniLibFolders
2023-03-10T15:51:04.3973502Z [15:51:04]: ▸ > Task :shared:configuration:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.3974358Z [15:51:04]: ▸ > Task :shared:configuration:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.3975220Z [15:51:04]: ▸ > Task :shared:domainshared:mergeReleaseJniLibFolders
2023-03-10T15:51:04.3976005Z [15:51:04]: ▸ > Task :shared:domainshared:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.3976800Z [15:51:04]: ▸ > Task :shared:domainshared:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.3977503Z [15:51:04]: ▸ > Task :shared:environment:mergeReleaseJniLibFolders
2023-03-10T15:51:04.3978229Z [15:51:04]: ▸ > Task :shared:environment:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.3979337Z [15:51:04]: ▸ > Task :shared:environment:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.4956252Z [15:51:04]: ▸ > Task :shared:featureflags:mergeReleaseJniLibFolders
2023-03-10T15:51:04.4957305Z [15:51:04]: ▸ > Task :shared:featureflags:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.4958415Z [15:51:04]: ▸ > Task :shared:featureflags:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.4959299Z [15:51:04]: ▸ > Task :shared:featureitemdetail:mergeReleaseJniLibFolders
2023-03-10T15:51:04.4960143Z [15:51:04]: ▸ > Task :shared:featureitemdetail:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.4961018Z [15:51:04]: ▸ > Task :shared:featureitemdetail:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.4961753Z [15:51:04]: ▸ > Task :shared:formatters:mergeReleaseJniLibFolders
2023-03-10T15:51:04.4962467Z [15:51:04]: ▸ > Task :shared:formatters:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.4963286Z [15:51:04]: ▸ > Task :shared:formatters:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.4964709Z [15:51:04]: ▸ > Task :shared:localization:mergeReleaseJniLibFolders
2023-03-10T15:51:04.4965465Z [15:51:04]: ▸ > Task :shared:localization:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.4966225Z [15:51:04]: ▸ > Task :shared:localization:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.4966925Z [15:51:04]: ▸ > Task :shared:settings:mergeReleaseJniLibFolders
2023-03-10T15:51:04.4967709Z [15:51:04]: ▸ > Task :shared:settings:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.4969627Z [15:51:04]: ▸ > Task :shared:settings:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.5957760Z [15:51:04]: ▸ > Task :shared:utils:mergeReleaseJniLibFolders
2023-03-10T15:51:04.5958754Z [15:51:04]: ▸ > Task :shared:utils:mergeReleaseNativeLibs NO-SOURCE
2023-03-10T15:51:04.5963727Z [15:51:04]: ▸ > Task :shared:utils:copyReleaseJniLibsProjectOnly
2023-03-10T15:51:04.9954958Z [15:51:04]: ▸ > Task :androidApp:mergeProdReleaseNativeLibs
2023-03-10T15:51:05.3993282Z [15:51:05]: ▸ > Task :androidApp:stripProdReleaseDebugSymbols
2023-03-10T15:51:05.3994378Z [15:51:05]: ▸ Unable to strip the following libraries, packaging them as they are: libsentry-android.so, libsentry.so.
2023-03-10T15:51:05.3995327Z [15:51:05]: ▸ > Task :androidApp:writeProdReleaseAppMetadata
2023-03-10T15:51:05.3996576Z [15:51:05]: ▸ > Task :shared:api:prepareReleaseArtProfile
2023-03-10T15:51:05.3997183Z [15:51:05]: ▸ > Task :shared:app:prepareReleaseArtProfile
2023-03-10T15:51:05.3997724Z [15:51:05]: ▸ > Task :shared:baseviewmodel:prepareReleaseArtProfile
2023-03-10T15:51:05.3998310Z [15:51:05]: ▸ > Task :shared:colors:prepareReleaseArtProfile
2023-03-10T15:51:05.3998836Z [15:51:05]: ▸ > Task :shared:configuration:prepareReleaseArtProfile
2023-03-10T15:51:05.3999391Z [15:51:05]: ▸ > Task :shared:domainshared:prepareReleaseArtProfile
2023-03-10T15:51:05.3999965Z [15:51:05]: ▸ > Task :shared:environment:prepareReleaseArtProfile
2023-03-10T15:51:05.4002120Z [15:51:05]: ▸ > Task :shared:featureflags:prepareReleaseArtProfile
2023-03-10T15:51:05.4006404Z [15:51:05]: ▸ > Task :shared:featureitemdetail:prepareReleaseArtProfile
2023-03-10T15:51:05.4010356Z [15:51:05]: ▸ > Task :shared:formatters:prepareReleaseArtProfile
2023-03-10T15:51:05.4014221Z [15:51:05]: ▸ > Task :shared:localization:prepareReleaseArtProfile
2023-03-10T15:51:05.4962998Z [15:51:05]: ▸ > Task :shared:settings:prepareReleaseArtProfile
2023-03-10T15:51:05.4963901Z [15:51:05]: ▸ > Task :shared:utils:prepareReleaseArtProfile
2023-03-10T15:51:05.9995655Z [15:51:05]: ▸ > Task :androidApp:mergeProdReleaseArtProfile
2023-03-10T15:51:07.0963901Z [15:51:07]: ▸ > Task :androidApp:collectProdReleaseDependencies
2023-03-10T15:51:07.0964825Z [15:51:07]: ▸ > Task :androidApp:configureProdReleaseDependencies
2023-03-10T15:51:07.1955232Z [15:51:07]: ▸ > Task :androidApp:extractProdReleaseNativeSymbolTables
2023-03-10T15:51:07.1961613Z [15:51:07]: ▸ > Task :androidApp:parseProdReleaseIntegrityConfig
2023-03-10T15:51:07.1962734Z [15:51:07]: ▸ > Task :androidApp:validateSigningProdRelease
2023-03-10T15:51:20.5955620Z [15:51:20]: ▸ > Task :shared:api:compileReleaseKotlinAndroid
2023-03-10T15:52:00.0955718Z [15:52:00]: ▸ > Task :shared:api:compileReleaseJavaWithJavac
2023-03-10T15:52:00.3959836Z [15:52:00]: ▸ > Task :shared:api:bundleLibCompileToJarRelease
2023-03-10T15:52:00.4955767Z [15:52:00]: ▸ > Task :shared:api:mergeReleaseGeneratedProguardFiles
2023-03-10T15:52:00.4956455Z [15:52:00]: ▸ > Task :shared:api:exportReleaseConsumerProguardFiles
2023-03-10T15:52:00.6955227Z [15:52:00]: ▸ > Task :shared:api:bundleLibRuntimeToJarRelease
2023-03-10T15:52:02.8955181Z [15:52:02]: ▸ > Task :shared:domainshared:compileReleaseKotlinAndroid
2023-03-10T15:52:03.8956360Z [15:52:03]: ▸ > Task :shared:domainshared:compileReleaseJavaWithJavac
2023-03-10T15:52:03.8957056Z [15:52:03]: ▸ > Task :shared:domainshared:bundleLibCompileToJarRelease
2023-03-10T15:52:04.2968914Z [15:52:04]: ▸ > Task :shared:domainshared:mergeReleaseGeneratedProguardFiles
2023-03-10T15:52:04.2979737Z [15:52:04]: ▸ > Task :shared:domainshared:exportReleaseConsumerProguardFiles
2023-03-10T15:52:04.2980420Z [15:52:04]: ▸ > Task :shared:domainshared:bundleLibRuntimeToJarRelease
2023-03-10T15:52:04.6956372Z [15:52:04]: ▸ > Task :shared:api:bundleLibResRelease
2023-03-10T15:52:04.6957141Z [15:52:04]: ▸ > Task :shared:domainshared:bundleLibResRelease
2023-03-10T15:52:07.2955648Z [15:52:07]: ▸ > Task :shared:featureitemdetail:compileReleaseKotlinAndroid
2023-03-10T15:52:07.3957775Z [15:52:07]: ▸ > Task :shared:featureitemdetail:compileReleaseJavaWithJavac
2023-03-10T15:52:07.3958601Z [15:52:07]: ▸ > Task :shared:featureitemdetail:bundleLibCompileToJarRelease
2023-03-10T15:52:07.3959300Z [15:52:07]: ▸ > Task :shared:featureitemdetail:mergeReleaseGeneratedProguardFiles
2023-03-10T15:52:07.3959979Z [15:52:07]: ▸ > Task :shared:featureitemdetail:exportReleaseConsumerProguardFiles
2023-03-10T15:52:07.4964882Z [15:52:07]: ▸ > Task :shared:featureitemdetail:bundleLibRuntimeToJarRelease
2023-03-10T15:52:07.5955019Z [15:52:07]: ▸ > Task :shared:featureitemdetail:bundleLibResRelease
2023-03-10T15:52:21.6993013Z [15:52:21]: ▸ > Task :shared:app:compileReleaseKotlinAndroid
2023-03-10T15:52:21.6994481Z [15:52:21]: ▸ w: file:///home/runner/work/mobile/mobile/shared/app/src/commonMain/kotlin/com/***/app/viewmodel/itemform/ItemFormSharedViewModel.kt:1373:9 Expected performance impact from inlining is insignificant. Inlining works best for functions with parameters of functional types
2023-03-10T15:52:22.4955707Z [15:52:22]: ▸ > Task :shared:app:compileReleaseJavaWithJavac
2023-03-10T15:52:22.5955178Z [15:52:22]: ▸ > Task :shared:app:mergeReleaseGeneratedProguardFiles
2023-03-10T15:52:22.6972982Z [15:52:22]: ▸ > Task :shared:app:exportReleaseConsumerProguardFiles
2023-03-10T15:52:22.6975482Z [15:52:22]: ▸ > Task :shared:app:bundleLibCompileToJarRelease
2023-03-10T15:52:22.7955209Z [15:52:22]: ▸ > Task :shared:app:bundleLibRuntimeToJarRelease
2023-03-10T15:52:23.3958414Z [15:52:23]: ▸ > Task :shared:app:bundleLibResRelease
2023-03-10T15:52:50.4977459Z [15:52:50]: ▸ > Task :androidApp:compileProdReleaseKotlin
2023-03-10T15:52:55.3955613Z [15:52:55]: ▸ > Task :androidApp:compileProdReleaseJavaWithJavac
2023-03-10T15:52:55.4955201Z [15:52:55]: ▸ > Task :androidApp:mergeProdReleaseGeneratedProguardFiles
2023-03-10T15:52:57.2955551Z [15:52:57]: ▸ > Task :androidApp:transformProdReleaseClassesWithAsm
2023-03-10T15:52:58.2955264Z [15:52:58]: ▸ > Task :androidApp:mergeProdReleaseJavaResource
2023-03-10T15:53:28.2955521Z [15:53:28]: ▸ > Task :androidApp:minifyProdReleaseWithR8
2023-03-10T15:53:37.2955919Z [15:53:37]: ▸ WARNING:Missing classes detected while running R8. Please add the missing classes or apply additional keep rules that are generated in /home/runner/work/mobile/mobile/androidApp/build/outputs/mapping/prodRelease/missing_rules.txt.
2023-03-10T15:53:37.2957555Z [15:53:37]: ▸ WARNING:R8: Missing class jakarta.xml.bind.DatatypeConverter (referenced from: java.lang.String com.github.scribejava.core.base64.JaxbBase64.internalEncode(byte[]))
2023-03-10T15:53:37.3036560Z [15:53:37]: ▸ Missing class java.beans.ConstructorProperties (referenced from: void com.fasterxml.jackson.databind.ext.Java7SupportImpl.())
2023-03-10T15:53:37.3037542Z [15:53:37]: ▸ Missing class java.beans.Transient (referenced from: void com.fasterxml.jackson.databind.ext.Java7SupportImpl.())
2023-03-10T15:53:37.3038548Z [15:53:37]: ▸ Missing class javax.xml.bind.DatatypeConverter (referenced from: java.lang.String com.github.scribejava.core.base64.Jaxb230Base64.internalEncode(byte[]))
2023-03-10T15:57:47.4956315Z [15:57:47]: ▸ > Task :androidApp:l8DexDesugarLibProdRelease
2023-03-10T15:57:49.1958740Z [15:57:49]: ▸ > Task :androidApp:uploadSentryProguardMappingsProdRelease
2023-03-10T15:57:49.1960034Z [15:57:49]: ▸ INFO    2023-03-10 15:57:47.179918444 +00:00 Loaded file referenced by SENTRY_PROPERTIES (/home/runner/work/mobile/mobile/androidApp/sentry.properties)
2023-03-10T15:57:49.1962034Z [15:57:49]: ▸ > compressing mappings
2023-03-10T15:57:49.3972806Z [15:57:49]: ▸ > uploading mappings
2023-03-10T15:57:51.9956512Z [15:57:51]: ▸ > Uploaded a total of 1 new mapping files
2023-03-10T15:57:51.9958065Z [15:57:51]: ▸ Newly uploaded debug symbols:
2023-03-10T15:57:51.9958677Z [15:57:51]: ▸ fd83b92e-72a7-4949-b36e-7a64a0482586
2023-03-10T15:57:52.1955886Z [15:57:52]: ▸ > Task :androidApp:buildProdReleasePreBundle
2023-03-10T15:57:54.2955219Z [15:57:54]: ▸ > Task :androidApp:compileProdReleaseArtProfile
2023-03-10T15:57:55.9956117Z [15:57:55]: ▸ > Task :androidApp:packageProdReleaseBundle
2023-03-10T15:57:58.7972007Z [15:57:58]: ▸ > Task :androidApp:signProdReleaseBundle
2023-03-10T15:57:58.8960962Z [15:57:58]: ▸ > Task :androidApp:produceProdReleaseBundleIdeListingFile
2023-03-10T15:57:58.8962063Z [15:57:58]: ▸ > Task :androidApp:createProdReleaseBundleListingFileRedirect
2023-03-10T15:57:58.8968459Z [15:57:58]: ▸ > Task :androidApp:bundleProdRelease
2023-03-10T15:57:58.8969134Z [15:57:58]: ▸ BUILD SUCCESSFUL in 8m 16s
2023-03-10T15:57:58.8969699Z [15:57:58]: ▸ 345 actionable tasks: 345 executed
2023-03-10T15:57:59.5788643Z [15:57:59]: --------------------
2023-03-10T15:57:59.5789501Z [15:57:59]: --- Step: supply ---
2023-03-10T15:57:59.5790099Z [15:57:59]: --------------------
2023-03-10T15:57:59.5808064Z
2023-03-10T15:57:59.5853575Z +------------------------------------+---------------------------------------------------------------------------------------------------------+
2023-03-10T15:57:59.5854519Z |                                                          Summary for supply 2.212.1                                                          |
2023-03-10T15:57:59.5855407Z +------------------------------------+---------------------------------------------------------------------------------------------------------+
2023-03-10T15:57:59.5856390Z | track                              | internal                                                                                |
2023-03-10T15:57:59.5856977Z | release_status                     | completed                                                                                |
2023-03-10T15:57:59.5858036Z | aab                                | /home/runner/work/mobile/mobile/androidApp/build/outputs/bundle/prodRelease/androidApp-prod-release.aab |
2023-03-10T15:57:59.5859221Z | package_name                       | com.***.android                                                                                |
2023-03-10T15:57:59.5859817Z | json_key                           | ../gc_keys_play.json                                                                                |
2023-03-10T15:57:59.5860408Z | skip_upload_apk                    | false                                                                                |
2023-03-10T15:57:59.5860961Z | skip_upload_aab                    | false                                                                                |
2023-03-10T15:57:59.5861530Z | skip_upload_metadata               | false                                                                                |
2023-03-10T15:57:59.5862106Z | skip_upload_changelogs             | false                                                                                |
2023-03-10T15:57:59.5862789Z | skip_upload_images                 | false                                                                                |
2023-03-10T15:57:59.5863367Z | skip_upload_screenshots            | false                                                                                |
2023-03-10T15:57:59.5864206Z | track_promote_release_status       | completed                                                                                |
2023-03-10T15:57:59.5864776Z | validate_only                      | false                                                                                |
2023-03-10T15:57:59.5865498Z | check_superseded_tracks            | false                                                                                |
2023-03-10T15:57:59.5866063Z | timeout                            | 300                                                                                |
2023-03-10T15:57:59.5866597Z | deactivate_on_promote              | true                                                                                |
2023-03-10T15:57:59.5867289Z | changes_not_sent_for_review        | false                                                                                |
2023-03-10T15:57:59.5868343Z | rescue_changes_not_sent_for_review | true                                                                                |
2023-03-10T15:57:59.5868979Z | ack_bundle_installation_warning    | false                                                                                |
2023-03-10T15:57:59.5869894Z +------------------------------------+---------------------------------------------------------------------------------------------------------+
2023-03-10T15:57:59.5870381Z
2023-03-10T15:58:00.6427100Z [15:58:00]: Preparing aab at path '/home/runner/work/mobile/mobile/androidApp/build/outputs/bundle/prodRelease/androidApp-prod-release.aab' for upload...
2023-03-10T16:07:34.1348755Z [16:07:34]: Updating track 'internal'...
2023-03-10T16:07:34.9845801Z [16:07:34]: Uploading all changes to Google Play...
2023-03-10T16:07:35.7901934Z +-------------------------------------+-------------------------------------------------------------------------------------------------------------+
2023-03-10T16:07:35.7902841Z |                                                                   Lane Context                                                                    |
2023-03-10T16:07:35.7903621Z +-------------------------------------+-------------------------------------------------------------------------------------------------------------+
2023-03-10T16:07:35.7904291Z | DEFAULT_PLATFORM                    | android                                                                                |
2023-03-10T16:07:35.7905158Z | PLATFORM_NAME                       | android                                                                                |
2023-03-10T16:07:35.7905832Z | LANE_NAME                           | android distribute_play_internal                                                                            |
2023-03-10T16:07:35.7906364Z | GRADLE_BUILD_TYPE                   | Release                                                                                |
2023-03-10T16:07:35.7906857Z | GRADLE_ALL_APK_OUTPUT_PATHS         | []                                                                                |
2023-03-10T16:07:35.7907696Z | GRADLE_ALL_AAB_OUTPUT_PATHS         | ["/home/runner/work/mobile/mobile/androidApp/build/outputs/bundle/prodRelease/androidApp-prod-release.aab"] |
2023-03-10T16:07:35.7908347Z | GRADLE_ALL_OUTPUT_JSON_OUTPUT_PATHS | []                                                                                |
2023-03-10T16:07:35.7908965Z | GRADLE_ALL_MAPPING_TXT_OUTPUT_PATHS | ["/home/runner/work/mobile/mobile/androidApp/build/outputs/mapping/prodRelease/mapping.txt"]                |
2023-03-10T16:07:35.7909878Z | GRADLE_AAB_OUTPUT_PATH              | /home/runner/work/mobile/mobile/androidApp/build/outputs/bundle/prodRelease/androidApp-prod-release.aab     |
2023-03-10T16:07:35.7910630Z | GRADLE_MAPPING_TXT_OUTPUT_PATH      | /home/runner/work/mobile/mobile/androidApp/build/outputs/mapping/prodRelease/mapping.txt                    |
2023-03-10T16:07:35.7911688Z +-------------------------------------+-------------------------------------------------------------------------------------------------------------+
2023-03-10T16:07:35.7912685Z [16:07:35]: Google Api Error: Invalid request - Some of the Android App Bundle uploads are not completed yet.
2023-03-10T16:07:35.8010750Z
2023-03-10T16:07:35.8015757Z +------+-------------------------+-------------+
2023-03-10T16:07:35.8016234Z |               fastlane summary               |
2023-03-10T16:07:35.8016633Z +------+-------------------------+-------------+
2023-03-10T16:07:35.8016989Z | Step | Action                  | Time (in s) |
2023-03-10T16:07:35.8018308Z +------+-------------------------+-------------+
2023-03-10T16:07:35.8018643Z | 1    | default_platform        | 0           |
2023-03-10T16:07:35.8018993Z | 2    | clean bundleProdRelease | 500         |
2023-03-10T16:07:35.8036328Z | 💥    | supply                  | 576         |
2023-03-10T16:07:35.8036754Z +------+-------------------------+-------------+
2023-03-10T16:07:35.8036956Z
2023-03-10T16:07:35.8040989Z
2023-03-10T16:07:35.8041524Z [!] Google Api Error: Invalid request - Some of the Android App Bundle uploads are not completed yet.
2023-03-10T16:07:35.8042038Z [16:07:35]: fastlane finished with errors
2023-03-10T16:07:35.8833900Z ##[error]Process completed with exit code 1.

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
13.2.1

Ruby
2.7.3

Bundler?
false

Git
git version 2.37.1 (Apple Git-137.1)

Installation Source
~/.rbenv/versions/2.7.3/bin/fastlane

Host
macOS 13.2.1 (22D68)

Ruby Lib Dir
~/.rbenv/versions/2.7.3/lib

OpenSSL Version
OpenSSL 1.1.1t  7 Feb 2023

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
14.2

Swift Version
5.7.2

System Locale

Variable
Value

LANG
en_GB.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
Irrelevant lanes have been omitted.
`./fastlane/Fastfile`
require 'java-properties'

default_platform(:android)

platform :android do
  desc 'Distribute a new version via Google Play Internal'
  lane :distribute_play_internal do
    gradle(
      task: 'clean bundleProd',
      build_type: 'Release',
      gradle_path: '../gradlew'
    )

    supply(
      track: 'internal',
      release_status: 'completed'
    )
  end
end

`./fastlane/Appfile`
json_key_file("../gc_keys_play.json")
package_name("com.redacted.android")

fastlane gems

Gem
Version
Update-Status

fastlane
2.212.1
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-firebase_app_distribution
0.5.0
✅ Up-To-Date

fastlane-plugin-sentry
1.15.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.4.0

atomos
0.1.3

claide
1.1.0

colored2
3.1.2

nanaimo
0.3.0

rexml
3.2.5

xcodeproj
1.22.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

terminal-table
1.6.0

addressable
2.8.1

multipart-post
2.0.0

word_wrap
1.0.0

optparse
0.1.1

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
2.0.3

commander
4.6.0

unf_ext
0.0.8.2

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

naturally
2.2.1

rubyzip
2.3.2

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.8.1

google-cloud-env
1.6.0

google-cloud-core
1.6.0

google-apis-storage_v1
0.19.0

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.3.0

digest-crc
0.6.4

mini_mime
1.1.2

google-cloud-storage
1.44.0

emoji_regex
3.2.3

uri
0.10.0

CFPropertyList
3.0.6

plist
3.7.0

public_suffix
5.0.1

excon
0.99.0

ruby2_keywords
0.0.5

faraday-retry
1.0.3

faraday-rack
1.0.0

faraday-patron
1.0.0

faraday-net_http_persistent
1.2.0

faraday-net_http
1.0.1

faraday-multipart
1.0.4

faraday-httpclient
1.0.1

faraday-excon
1.1.0

faraday-em_synchrony
1.0.0

faraday-em_http
1.0.0

faraday
1.10.3

json
2.6.3

mini_magick
4.12.0

bundler
2.4.7

simctl
1.6.10

jwt
2.7.0

webrick
1.8.1

httpclient
2.8.3

retriable
3.1.2

trailblazer-option
0.1.2

declarative
0.0.20

uber
0.1.0

representable
3.2.0

google-apis-core
0.11.0

google-apis-playcustomapp_v1
0.13.0

google-apis-androidpublisher_v3
0.34.0

google-cloud-errors
1.3.1

google-apis-iamcredentials_v1
0.17.0

rake
13.0.6

aws-eventstream
1.2.0

aws-sigv4
1.5.2

aws-partitions
1.719.0

jmespath
1.6.2

aws-sdk-core
3.170.0

aws-sdk-kms
1.63.0

aws-sdk-s3
1.119.1

forwardable
1.3.1

logger
1.4.2

cgi
0.1.0

date
3.0.0

timeout
0.1.0

stringio
0.1.0

ipaddr
1.2.2

openssl
2.1.2

zlib
1.1.0

mutex_m
0.1.0

ostruct
0.2.0

strscan
1.0.3

io-console
0.5.6

delegate
0.1.0

fileutils
1.4.1

singleton
0.1.0

open3
0.1.0

nokogiri
1.14.2

racc
1.6.2

yaml
0.1.0

psych
3.1.0

fastlane-plugin-firebase_app_distribution
0.5.0

fastlane-plugin-sentry
1.15.0

generated on: 2023-03-10

Any update with this issue? I have the same problem :)

This issue seems to be happening on new version of fastlane

We hit the same problem almost a month ago (16th February 2023) on fastlane 2.210.1
So if it's a fastlane bug then it was introduced earlier

Someone found a solution?

Same issue on 2.211.0

Can confirm, I have the same issue on version 2.212.1

It seems like a pretty recent issue because I got the same issue minutes ago on version 2.210.1
Even using release_status: 'draft'
And it is coming directly from the Google Play API
https://github.com/fastlane/fastlane/blob/HEAD/supply/lib/supply/client.rb#L184

Same issue with version 2.211.0 using the draft option

I get the same issue and I suspect the Google Play API to be running a bit slow these days when uploading files and thus we hit the timeout set for the supply action (which seems to be 300s by default)

Can confirm that increasing the timeout solved the issue for me! Even with release_status: 'completed'

I get the same issue and I suspect the Google Play API to be running a bit slow these days when uploading files and thus we hit the timeout set for the supply action (which seems to be 300s by default)

Can confirm that increasing the timeout solved the issue for me! Even with release_status: 'completed'

Could you share the timeout that fixed this issue? 👀

I tried 600s, but it actually ran in just 52s

I tried 600s, but it actually ran in just 52s

600s fixed this, but it finished in 29s 🤔

How can I change the timeout?

How can I change the timeout?

You can add a supply(timeout: 1000)

Facing this issue too, does the fix need to be made on the library side and we should wait for a PR ? I'm not sure I understand what needs to be done here !

I think this is a temporary problem on the Google Play API and not in Fastlane

I think this is a temporary problem on the Google Play API and not in Fastlane

I agree with you. For now, it is possible to increase the timeout to work around this issue. For those using the upload_to_play_store action, you can add the timeout parameter following the docs.
...
      upload_to_play_store(
        ...
        timeout: 600,
        ...
      )
...

I think this is a temporary problem on the Google Play API and not in Fastlane

I agree with you. For now, it is possible to increase the timeout to work around this issue. For those using the upload_to_play_store action, you can add the timeout parameter following the docs. On your Fastfile:
...
      upload_to_play_store(
        ...
        timeout: 600,
        ...
      )
...

If anyone is facing this issue, this solution worked for me. I'm using Fastlane 2.210.1.

Hi, im still facing this issue, and increasing timeout seems to not change anything..
Any other solution ?
Also, the "summary for supply" table is not taking count of timeout change does in fact.
maybe the description in the table doesnt care about how it's config, idk..
My lane :
  desc "Submit a new Beta Build to GooglePlayStore Beta"
  lane :beta do
    sh "./../../build.sh cloud android"
    upload_to_play_store(track: 'beta', timeout: 600)
  end

Fastlane v:  2.212.1

Hey, I'm now consistently getting a timeout failure after 10 minutes. You can change the timeout to 100000 seconds if you want. It's either a timeout error or an auth error.
I think Google is maybe hurting with the roll-out of Bard? ;)

@LaurieScheepers same here, yesterday all was good, since few hours can't make any deployments

It's definitely Bard. I bet you 1 trillion dollars the Google outages are going to come to light soon

Well, I tried to take my aab and upload it directly in my track through play console and it's also stuck there.
I can't find any service status about play api's
Well, i will retry later
at least im not the only one facing this issue

We have also increased the timeout to 600 and from today started getting this
Google Api Error: Unauthorized - Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential.

I agree with the above statement. Gosh this is so annoying. I am now on my 10th attempt. :/

16 attempts and two hours later it succeeded

Google Api Error: Invalid request - Some of the Android App Bundle uploads are not completed yet.
5 attempts

My QA app 6 attempts passed
Dev 3 attempts passed

I confirm, by setting these params, the upload goes through successfully:
      skip_upload_metadata: true,
      skip_upload_images: true,
      skip_upload_screenshots: true,

I tried 600s, but it actually ran in just 52s

600s fixed this, but it finished in 29s 🤔

Fixed too, but it finished in 56s

authors: Kazion500 Lakston LaurieScheepers LucasBourgeois MatTerra MateusAndrade alexkeramidas androideveloper bmarkowww bsalesc developerdanx guillaume-tgl hnarimani jasielmacedo mikeblanton moshecohen90 professorkolik rafaelfrancisco-dev sebj sregg v-pavlovskyi


text:
[precheck] migrate to App Store Connect API (except for IAPs)

Motivation and Context
Fixes #17150
Fixes #17158
Description

Replaced most Spaceship::Tunes calls with Spaceship::ConnectAPI calls

Except for IAPs

Added in new optional platform option
Updated tests

seems like this produced another issue #17176

source: gharchive/pull-request

authors: joshdholtz noxo


text:
Installation requires Xcode

Xcode is required to run git clone [git@github.com](mailto:git@github.com):fatipardo/PDBClean-0.0.2.git

We added a note to the installation guide.

authors: fatipardo gdkwxn


text:
remove duplicated translations

maybe checking using elastic search or something

Can you please elaborate the issue a bit more, I might take this! @fawazahmed0

The editions has few duplicates(i.e same translation is stored in multiple editions ).
For example deu-asfbubenheimand is duplicate of deu-frankbubenheima .
If you can give me a list of all dupilcates, that should help.
I will remove the duplicates and keeping only one original copy

Assalamualaikum friends, I hope you are doing well.
My name is Mohammad Shahzad, I am 20 years old.
I have spent the last two years composing the complete translation and interpretation of the Holy Quran in MS Word.
Now I wish to include it in the "API" of Quran.
I want to add it with another script.
I have no knowledge of coding.
But if someone guides me, I can work hard.
Please friends help me in this good work.
JzakAllah

I have a question. Please help me out. I can see all the text is stored in this github repository. There is no external database or external file system where you are putting all "Quran" text. How is this working.
Thanks in advance.

Please guide me. I want to contribute to this project.

I can see all the text is stored in this github repository.

Yes, all the api files are stored in this repo, and these files are served using jsdelivr

authors: Shahzadworld fawazahmed0 jazimabbas njmulsqb

license: Unlicense


text:
Added the deck ad network

I'm not sure whether you intend is to block ads in your network or simply http traffic.
Added the deck ad network:
connect.decknetwork.net

The second commit was not supposed to land here, it needs further testing. For me it happens to block Netflix playback which is pretty interesting at it means this traffic is not encrypted on the one hand and send through one of the listed sites.

Actually I like the Deck for its opinion on privacy. What about putting these mildly "controversial" advertisers in a extra file?
Come to think of it: Maybe even "googleadservices" can go there, because lots of people complain about not being able to click Google ads in Google search results anymore. :)

Thats actually the reason why I asked for the purpose of your list. You write in the readme that you want to convince providers to use https. If this is true, my PR would be wrong.
I guess the best thing would be to provide different lists like for example here: http://www.squidblacklist.org/downloads.html
Basically FritzBox could do that by automatically importing such lists like they do for the content blocker for kids.
Not sure ... what is your opinion?

OK, I like the idea. I split the blacklist into two parts. The naming is somewhat lame, but for a first draft this may suffice.
Oh, and the sentence in REAMDE.md about https is meant rather ironically, because https cannot be blocked by something like a FritzBox. 😁
Actually this project's purpose is to help my visitors and my mobile devices without built-in adblocking capabilities to not be pestered by advertisement as long as they are in my Wifi, and not waste my bandwith.

authors: JamborJan fboes

repo: fboes/fritzbox-blacklist

license: mit

license_source: bigquery


text:
Error when using array of data sources

Hi, when setting the data option as this:
// assemble
gulp.task('assemble', function (done) {
	assemble({
		logErrors: config.dev,
		data: ['package.json', 'src/data/**/*.{json,yml}']
	});
	done();
});

I got following error:
Error (fabricator-assemble): JS-YAML: end of the stream or a document separator is expected at line 1, column 13:
    'use strict';

When using them seperate, I got no issues.

While figuring this one out, I see that when setting the default in assemble to an array, all works. It seems that the following line is messing things up when one is an array and the other a string:
// merge user options with defaults
options = _.merge({}, defaults, userOptions);

I'll see to fix it and do a pull request on the fabricator-assemble repo is this ok?

I actually don't know if it must be solved in fabricator-assemble, as it's actually the lodash merge method that doesn't do what it's supposed to do, no? Any thoughts?

Thanks for tracking this down.
I think you're correct that the _.merge doesn't handled a string vs array.
I made the default option an array, and that seems to work in every case. Check it out. https://github.com/fbrctr/fabricator-assemble/pull/17/files

Hi, I filed that bug in the lodash project and they already fixed it: https://github.com/lodash/lodash/issues/1375
Now just waiting to have it released with a new version on npm.

authors: LukeAskew dietergeerts

repo: fbrctr/fabricator


text:
Cannot install pymrmr

PymRMR version:
Python version: python 3
Operating System: OS X El Capitan "10.11.6"

Description
Describe what you were trying to get done.
Tell us what happened, what went wrong, and what you expected to happen.
What I Did
pip install numpy Cython
pip install pymrmr
Collecting pymrmr
  Using cached pymrmr-0.1.11.tar.gz (69 kB)
Requirement already satisfied: numpy>=1.19.5 in /opt/anaconda3/lib/python3.7/site-packages (from pymrmr) (1.20.1)
Building wheels for collected packages: pymrmr
  Building wheel for pymrmr (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /opt/anaconda3/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/setup.py'"'"'; __file__='"'"'/private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-wheel-frxhfca6
       cwd: /private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/
  Complete output (38 lines):
  /opt/anaconda3/lib/python3.7/site-packages/setuptools/dist.py:723: UserWarning: Module Cython was already imported from /opt/anaconda3/lib/python3.7/site-packages/Cython/__init__.py, but /private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/.eggs/Cython-3.0a6-py3.7.egg is being added to sys.path
    pkg_resources.working_set.add(dist, replace=True)
  running bdist_wheel
  running build
  running build_py
  package init file 'pymrmr/__init__.py' not found (or not a regular file)
  running egg_info
  writing pymrmr.egg-info/PKG-INFO
  writing dependency_links to pymrmr.egg-info/dependency_links.txt
  writing requirements to pymrmr.egg-info/requires.txt
  writing top-level names to pymrmr.egg-info/top_level.txt
  reading manifest file 'pymrmr.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  warning: no previously-included files matching '__pycache__' found under directory '*'
  warning: no previously-included files matching '*.py[co]' found under directory '*'
  warning: no files found matching '*.jpg' under directory 'docs'
  warning: no files found matching '*.png' under directory 'docs'
  warning: no files found matching '*.gif' under directory 'docs'
  writing manifest file 'pymrmr.egg-info/SOURCES.txt'
  creating build
  creating build/lib.macosx-10.9-x86_64-3.7
  creating build/lib.macosx-10.9-x86_64-3.7/pymrmr
  copying pymrmr/crank.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
  copying pymrmr/mrmr.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
  copying pymrmr/nrutil.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
  copying pymrmr/nrutil.h -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
  copying pymrmr/pbetai.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
  copying pymrmr/pymrmr.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
  copying pymrmr/pymrmr.pyx -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
  copying pymrmr/sort2.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
  running build_ext
  skipping 'pymrmr/pymrmr.cpp' Cython extension (up-to-date)
  building 'pymrmr' extension
  creating build/temp.macosx-10.9-x86_64-3.7
  creating build/temp.macosx-10.9-x86_64-3.7/pymrmr
  gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/opt/anaconda3/include -arch x86_64 -I/opt/anaconda3/include -arch x86_64 -I/opt/anaconda3/lib/python3.7/site-packages/numpy/core/include -I/opt/anaconda3/include/python3.7m -c pymrmr/pymrmr.cpp -o build/temp.macosx-10.9-x86_64-3.7/pymrmr/pymrmr.o -fopenmp -Ofast
  clang: error: unsupported option '-fopenmp'
  error: command 'gcc' failed with exit status 1
  ----------------------------------------
  ERROR: Failed building wheel for pymrmr
nning setup.py clean for pymrmr
Failed to build pymrmr
Installing collected packages: pymrmr
    Running setup.py install for pymrmr ... error
    ERROR: Command errored out with exit status 1:
     command: /opt/anaconda3/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/setup.py'"'"'; __file__='"'"'/private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-record-zrfq3baf/install-record.txt --single-version-externally-managed --compile --install-headers /opt/anaconda3/include/python3.7m/pymrmr
         cwd: /private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/
    Complete output (38 lines):
    /opt/anaconda3/lib/python3.7/site-packages/setuptools/dist.py:723: UserWarning: Module Cython was already imported from /opt/anaconda3/lib/python3.7/site-packages/Cython/__init__.py, but /private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/.eggs/Cython-3.0a6-py3.7.egg is being added to sys.path
      pkg_resources.working_set.add(dist, replace=True)
    running install
    running build
    running build_py
    package init file 'pymrmr/__init__.py' not found (or not a regular file)
    running egg_info
    writing pymrmr.egg-info/PKG-INFO
    writing dependency_links to pymrmr.egg-info/dependency_links.txt
    writing requirements to pymrmr.egg-info/requires.txt
    writing top-level names to pymrmr.egg-info/top_level.txt
    reading manifest file 'pymrmr.egg-info/SOURCES.txt'
    reading manifest template 'MANIFEST.in'
    warning: no previously-included files matching '__pycache__' found under directory '*'
    warning: no previously-included files matching '*.py[co]' found under directory '*'
    warning: no files found matching '*.jpg' under directory 'docs'
    warning: no files found matching '*.png' under directory 'docs'
    warning: no files found matching '*.gif' under directory 'docs'
    writing manifest file 'pymrmr.egg-info/SOURCES.txt'
    creating build
    creating build/lib.macosx-10.9-x86_64-3.7
    creating build/lib.macosx-10.9-x86_64-3.7/pymrmr
    copying pymrmr/crank.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
    copying pymrmr/mrmr.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
    copying pymrmr/nrutil.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
    copying pymrmr/nrutil.h -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
    copying pymrmr/pbetai.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
    copying pymrmr/pymrmr.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
    copying pymrmr/pymrmr.pyx -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
    copying pymrmr/sort2.cpp -> build/lib.macosx-10.9-x86_64-3.7/pymrmr
    running build_ext
    skipping 'pymrmr/pymrmr.cpp' Cython extension (up-to-date)
    building 'pymrmr' extension
    creating build/temp.macosx-10.9-x86_64-3.7
    creating build/temp.macosx-10.9-x86_64-3.7/pymrmr
    gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/opt/anaconda3/include -arch x86_64 -I/opt/anaconda3/include -arch x86_64 -I/opt/anaconda3/lib/python3.7/site-packages/numpy/core/include -I/opt/anaconda3/include/python3.7m -c pymrmr/pymrmr.cpp -o build/temp.macosx-10.9-x86_64-3.7/pymrmr/pymrmr.o -fopenmp -Ofast
    clang: error: unsupported option '-fopenmp'
    error: command 'gcc' failed with exit status 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /opt/anaconda3/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/setup.py'"'"'; __file__='"'"'/private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-install-f7qo02kj/pymrmr_32f3a729caae47319ee9a082199328fe/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/var/folders/wf/m4g31w8s68z88597d_64hbw80000gn/T/pip-record-zrfq3baf/install-record.txt --single-version-externally-managed --compile --install-headers /opt/anaconda3/include/python3.7m/pymrmr Check the logs for full command output.
Note: you may need to restart the kernel to use updated packages.

This looks like it might just be a problem with OpenMP -- check out this StackOverflow post.

@MariamSheha Hi, did you have a chance to fix it? I had the same error on my macOS High Sierra.

@MariamSheha , thank you for your reply. I gave up installing this package on my Mac. However,

I successfully installed this package on a Ubuntu 18.04 machine.
On my own Mac, I found this repo working for me. https://github.com/danielhomola/mifs

Hopefully, this helps for you.

authors: JacksonBurns MariamSheha sunformoon

repo: fbrundu/pymrmr


text:
Generic cast range

Along with Elder Staff might create weird behaviors.

Fixed!

Apart from updating after a skill is being used, seems to be just fine. Closing.


text:
Add support for RISE slides in JupyterLab

This PR:

adds support for jupyterlab-rise
clean some commented code
fix setting metadata when modified for JupyterLab 4+

FYI @parmentelat in JupyterLab 4, metadata obtained are a copy of the document metadata. So modifying them required to explicitly call setMetadata with the new value.

Wrong target...

repo: fcollonval/jupytext


text:
Batch actions

Sometimes, you need to reduce several actions at once (to optimize and prevent multiple renders in React for example). It's mostly done by dispatching one action which payload is an array of actions which will be reduced at the same time.
Is there a way to log such use case? Right now, it only logs the batch action itself. I would like to at least log all the batched actions. Even better would be to display where the batch starts and where it ends.
I was thinking about doing it inside the actionTransformer:

log the beginning of the batch
log all batched actions from the payload of the action
return the batch action itself so it is also logged and indicate the end of the batch

But maybe you have a better way to handle it?
Cheers

Have a look a #116

Solved by #116.

Thanks a lot.

authors: pauldijou smashercosmo theaqua

repo: fcomb/redux-logger


text:
Fcrepo 2407 v2

Includes one extra commit over FCREPO-2407, which adds FcrepoResponse.getEtag(), and adds setter methods which take entityTag objects in order to handle the change from strong to weak etags in responses.

@bbpennel I'm going to suggest that you revert the last commit. I am definitely 👎  to requiring JAX-RS in client code. It's fine to use this in test code, but please not the client code.
If you go down that route, it will mean I'll need to write a new fcrepo-client for all of the camel code, and I don't want to do that.

Okay, was keeping it in a separate PR for that reason.  I'll look at #24 some more then.

authors: acoburn bbpennel


text:
Add namespaces to the default CND configuration

Resolves: https://jira.duraspace.org/browse/FCREPO-2258

EBUCore?

ebucore is already in the CND

👍


text:
README: project Hoard doesn't use Tui-rs

See e.g. https://github.com/Shadow53/hoard/blob/main/Cargo.toml
Cheers !

This is not the project that is currently linked on the README page 😄: https://github.com/Hyde46/hoard not https://github.com/Shadow53/hoard.

authors: fdehau ngirard

repo: fdehau/tui-rs


text:
Limited on 480p

It's in title, not the same issue as "higher quality" because is significant lower and not depend of the max flow for unificated files avaible...

I know, Google changed their enpoints and the only source with the remuxed audio/video is 420p, so the yt-dlp command used to extract said data stream in direct mode is currently its maximum quality, sorry. ..
In bridge mode you can make a real-time remux of video and audio giving the maximum quality, be it 1080p, even 2160p, try it. The BIG drawback is that navigation does not work, that is, you cannot move forward or backward freely.
Lately I have been overworked and I don't have much time to dedicate to this project, but when I can I do my tests and I'm sure that I will finally find the key that will make it work... patience

@fe80Grau I confirm I'm not able to have above 480p resolution no matter if  I use direct or bridge mode

Do you work with the last commit/docker image?

Yes, latest docker hub image

Ok, then play a video, go to ytdlp2strm root folder and paste here the last lines generated in ytdlp2strm.log

OK, after looking at the logs in fact 100% of youtube videos was had age restrictions.
After downloading my youtube cookie, and adding it to ytdlp2STRM I van play videos at max resolution
Thanks

authors: fe80Grau maximushugus metasystem


text:
change errors default type to Array instead of object, for consistent…

When the errors is empty it returns an object as response, which is inconsistent, since it always returns an array of objects ( when it has errors )

Consistency with which database? Some key their errors based on the property name.
This will probably also be a breaking change for any client that expects an empty object.
A way to change the default error object in your app would be with the new app error hooks
app.hooks({
  error(hook) {
    const errors = hook.error.errors;

    if(typeof errors.length === 'undefined') {
      hook.error.errors = [];
    }
  }
});

When having multiple errors the response is.
[
  {errors}
]

When having a single error
{error}
when having no errors
{}
Understood that might be breaking changes and your snippet works for me. This can be closed.
Thanks @daffl

Ok thanks. Still appreciate the contribution!

authors: Faianca daffl

repo: feathersjs/feathers-errors


text:
EDITING: (EN) Fix typo in quick-start

Changelog
Fixed the typo in quick-start.md
Checklist

[x] I reviewed CONTRIBUTING guidelines
[x] I did a self-review of the changes
[x] I gave a brief description of the changes
[x] I awaited for CI checks
[x] I specified related materials if needed (discussion/issue/pull-request...)
[x] All requirements for the related issue are resolved if issue exists

@vladthelittleone Заходи еще 🔥

authors: azinit vladthelittleone

repo: feature-sliced/documentation


text:
Being able to view the image

{"chapter_endpoint":"after-transformation-mine-and-her-wild-fantasy-chapter-70-bahasa-indonesia/","chapter_pages":12,"chapter_image":[{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":1},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":2},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":3},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":4},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":5},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":6},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":7},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":8},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":9},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":10},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":11},{"chapter_image_link":"https://i0.wp.com/img.komiku.co.id/norundefined","image_number":12}]}
This is the data received from the chapter request, but how am i actually able to view the image? What is the string concatenation to view the image? Also, is there any way to get the image in English?

Hi, thanks for opening an issue
if you want to see the image just click the chapter_image_link, If you are using chrome browser u can install plugin named JSONView https://chrome.google.com/webstore/detail/jsonview/chklaanhfefbnpoihckbnefhakgolnmc. It will makes the json looks pretty.
Here's the sample image link that supposed to be shown in json https://i0.wp.com/cdn.komiku.co.id/wp-content/uploads/2236269-2.jpg , but the link is undefined because the original website has changed the html. This is the original website where the data coming from https://komiku.id/ch/"after-transformation-mine-and-her-wild-fantasy-chapter-70-bahasa-indonesia/.
For image in English, its impossible to get. because the source just provide image in Indonesia.
I'll fix this issue as fast as possible

@mdevk093 Hi, i've fixed the current issue which the image link in chapter endpoint not shown as expected.

repo: febryardiansyah/manga-api


text:
feat(devimint): start from a previous state (skip setup)

I need a way to verify certain behaviors manually between versions, etc. Similiar to upgrade tests etc.
It occurred to me that it should be possible to just start devimint skipping all the DKGs and other setups, and it should be relatively easy. So I implemeted it.
One blocker that I've hit was inability to tell fedimintd to use certain URL to connect to bitcoind, instead of whatever was added to the config. I made new env variables that can be used to force bitcoind kind&url. The way existing env vars are working is confusing (they are only used as a default for DKG, so I renamed them while at it (with backward-compat.  of course).
Another blocker was that on killing devimint, we send kill -9 right away, which makes bitcoind not get any chance to flush database to disk, and thus lose block history. All other daemons get really upset about it. So I changed it to kill, 3s wait, kill -9 sequence. A bit slower (fedimimtd takes some time to shutdown), but works, and seem better. We can fix & improve with time.
The implementation is a bit meh, but can be improved with time. I would also like to modularize the setup so e.g. test that doesn't need LND, or electrs, etc. does not need to start them, and can configure it via builder.
Testing
Start devimint e.g. like this:
> just devimint-env
...
2024-04-13T04:29:23.013121Z  INFO fm::devimint: Devimint data dir path=/tmp/devimint-3321804-158

Stop it, and then start it again, but skip the setup.
env FM_TEST_DIR=/tmp/devimint-3321804-158 FM_SKIP_SETUP=true RUST_LOG=fm::devimint=debug just devimint-env

It takes it sweet time as LND Gateway blocks on LND starting to return route hints, but works.

Would be great for @maan2003 to ack it at some point.

next week, a bit busy

@maan2003 Thx. I think we can just remove the label to mark the missing approval as taken care of.

repo: fedimint/fedimint


text:
Add coreutils to the flake

Since tmuxinator and other scripts are using sed,
we probably want these reproducibly set in the shell.

Codecov Report

Merging #548 (a50bcf9) into master (3c60fb6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #548   +/-   ##
=======================================
  Coverage   72.66%   72.66%
=======================================
  Files          83       83
  Lines       10999    10999
=======================================
  Hits         7992     7992
  Misses       3007     3007

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

authors: codecov-commenter dpc


text:
🛑 넷스피어 원 is down

In 5062cbd, 넷스피어 원 (https://netsphere.one/api/v1/instance/activity) was down:

HTTP code: 403
Response time: 812 ms

Resolved: 넷스피어 원 is back up in ca2aa4f after 38 minutes.

repo: fediverses-kr/upptime-api


text:
Implement OpenShift/Kubernetes as a backend

With current feature set, you can easily write some python code to validate your standalone containers (which run in dockerd). That's not enough. You usually run your containerized application in production orchestrated environment - Kubernetes or OpenShift. Therefore we should add support for these systems in conu.
The biggest problem with the implementation is the design itself - k8s orchestration doesn't utilize concept of containers nor images.
Detailed plan

Design

As I wrote in the introduction, the design is the most critical part. We, as upstream maintainers, need to approve the proposed design.
The initial design is expected to be simple: conu needs to be able to run a containerized application inside k8s. For that, we need only a few k8s primitives to be implemented:

pod, service, deployment

In case of OpenShift, the app needs to be runnable via oc new-app.
We also require convenient user experience. Ideally users would provide well-known configuration object without the need of learning some complex python API, an example:from conu import Pod
pod_spec = """
    apiVersion: v1
    kind: Pod
    metadata:
      name: my-pod
    spec:
      containers:
      - env:
        - name: SOME_ENV_VAR
          value: "I am a value"
        image: library/fedora:27
        imagePullPolicy: IfNotPresent
        name: my-container
      restartPolicy: Never
"""
pod = Pod(from_spec=pod_spec)
# run the pod now

Implementation

Once the design is approved, you can start working on the implementation.

It is expected to iterate on the design and implementation phases multiple times so we can achieve even the more complex scenarios.
Configuration

Orchestration systems are very complex. When interacting with them, users usually require a flexible workflow which can be customized.
Users should be able to specify: cluster, API token, the way to connect, namespace, user, clean after testing? And even more!

Template support

Once we have the basics, it's time to support templates -- this is the usual way people deploy to k8s/OpenShift.

Parametrizing templates

In order to be flexible and allow parametrizing test cases, we may need to be able to parametrize templates -- users can easily change parts of a template via some well-known templating system (such as jinja).

Finish line

To prove that all the new code works, use it to write at least 2 simple test suites for container images delivered in Fedora and validate they work well in k8s/openshift.

This issue is proposed as a GSoC project as part of Fedora.

Hi,
I'm interested in this idea for GSoC but I want to understand more.
From my understanding, this should implement the k8s interface as a backend so you can plug the configurations for an existing k8s deployment and then run the Pod from the yaml definition.
My question is if we should also write wrappers/utils for different functions/actions you can do on pods(for example)? I'm interested in how much should the abstraction provide?
With the new concepts (pods, deployments ... etc ) you have new actions that you can perform, will the conu project support this actions or just a subset and allow the user to use for example the k8s python client for something else more specific?
Another question is about the yaml definition:
We can integrate jinja easily in the template but do we need to process it more? I would assume is enough to render the template and then pass it to the k8s cluster to create the resource.  Maybe some type checking and linting to see if it's a valid yaml but letting the k8s parser to see if the string is valid.
It looks to the that the design will make/break this type of backend, should the application contain the "final" design or the actual design can be iterated as part of the GSoC program? I'm asking this because coming up with a viable design (even in draft form) might take some time and I don't know if I can get one done in time for the application process.
Thanks in advance! :D

Hi Matei, thanks for your interest!
The overall comment I have for you is that the design should be solved as part of the GSoC project.

My question is if we should also write wrappers/utils for different functions/actions you can do on pods(for > example)?

I would say that yes. The main intent here is to provide this interface to people so they can use it to validate their containerized applications running in kube. I think that implementation for pods will have a smaller prio than implementation for Services and Deployments.

With the new concepts (pods, deployments ... etc ) you have new actions that you can perform, will the
conu project support this actions or just a subset and allow the user to use for example the k8s python
client for something else more specific?

Ideally the implementation would use that API client and it would be fully available to users.

We can integrate jinja easily in the template but do we need to process it more? I would assume is enough
to render the template and then pass it to the k8s cluster to create the resource.

Yup.

Maybe some type checking and linting to see if it's a valid yaml but letting the k8s parser to see if the
string is valid.

If users want to shoot themselves to foot, they are free to do so. Type checking and linting is definitely a nice to have feature.

It looks to the that the design will make/break this type of backend, should the application contain the
"final" design or the actual design can be iterated as part of the GSoC program? I'm asking this because
coming up with a viable design (even in draft form) might take some time and I don't know if I can get one
done in time for the application process.

I completely share your concern. The key here is not to overthink the design and instead start small, iterate and converge to a shared goal -- see last point in the list.

GSoC finished succesfully and the work has been done by @rpitonak

authors: TomasTomecek dhodovsk mateimicu

repo: fedora-modularity/conu


text:
Content behind privacy wall

I tried multiple ways, but didn't manage so far; would this plugin actually be capable to scrape something behind a cookie wall with a button element to accept?
A lot of Dutch websites are using a redirect to a privacy wall. Content is only scrapable after getting a link from the button element. E.g. www.volkskrant.nl, www.trouw.nl and www.vi.nl.

Unfortunately no. There is a chance just changing the user agent will fix your issue, You could look into the plugin ttrss-tumblr-gdpr , you'll have to add the domain's to the supported array: https://github.com/GregThib/ttrss-tumblr-gdpr/blob/master/init.php#L29

authors: dugite-code feedspeed


text:
resolves: 124 support relative filepaths

Closes #124

Relative file paths for cli arguments is now supported.
For the config files, supporting relative paths for an arbitrary field is not trivial as the string might be complex (an option containing a json for example: `"--heat.json.patch='{"op": "replace","path": "/Meshes/heat/Import/filename","value": "$cfgdir/{{parameters.meshes.value}}/case3_p{{parameters.nb_tasks.tasks.value}}.json" }'"
I propose to keep imposing using $PWD in the config. Thoughts? @vincentchabannes @prudhomm
Note that using env vars in config files is already supported. For example, "reframe_base_dir":"$PWD/build/reframe",
Also, I think having relative paths in config files is ambiguous. Is it relative to the file location or to the current directory ?

what does $PWD refer to? I would prefer a better named variable

authors: JavierCladellas prudhomm

repo: feelpp/benchmarking


text:
🛑 Gay Git is down

In cd9472a, Gay Git (https://git.bsd.gay/) was down:

HTTP code: 502
Response time: 1141 ms

Resolved: Gay Git is back up in c9531e0.


text:
Environment variable interpreted as a strong

🐛 Bug Report
I'm using AWS ECS, which gets it's IAM credentials the same way an EC2 instnace would. Setting the FOUNDRY_AWS_CONFIG environment variable to "true" causes it to be read as a string, and it subsequently gets added to the path: The configured awsConfig path /data/Config/true does not exist or is not accessible..  This should not happen, as ECS gets it's IAM credentials the same way that EC2 does.
To Reproduce
Steps to reproduce the behavior:
Set environment variable as "true", get error.
Expected behavior
I expected it to not use any file, or environment variables and use the attached IAM policy instead. I'm not sure if the entrypoint, or later javascript is expected that to be a bool without quotes, but perhaps there should be a check in there to see if the string evaluates to true or false.
Any helpful log output
Please run this command:
docker inspect --format='{{range $k, $v := .Config.Labels}}
    {{- printf "%s = \"%s\"\n" $k $v -}} {{end}}' \
    felddy/foundryvtt:latest

Paste the results here:
Hopefully this is legibly formatted
# ECS Log Output
[info] Application Options:
    {
    "port": 30000,
    "upnp": false,
    "fullscreen": false,
    "hostname": "my.foundryurl.com",
    "localHostname": null,
    "routePrefix": null,
    "sslCert": null,
    "sslKey": null,
    "awsConfig": null,
    "dataPath": "/data",
    "passwordSalt": null,
    "proxySSL": false,
    }
[info] Foundry Virtual Tabletop - Version 9
[info] Loading data from user directory - /data
[error] The configured awsConfig path /data/Config/true does not exist or is not accessible.

Run the container with CONTAINER_VERBOSE set to true,and paste any useful
log output here:

Hmmm.  That does sound broken.   Thanks for the bug report.
It's weird that your application options is logged as: "awsConfig": null, although you can clearly see the error below.
I haven't had a chance to play with the container with ECS, EKS, or Fargate yet so this might take me a bit of time.
I'm just going to paste some context below...  I'm not going to be able to dig into it tonight, but I'll try to take a look tomorrow.
https://github.com/felddy/foundryvtt-docker/blob/d6a9467cb758f08d1712be0bd4f32ed0b514eff0/src/set_options.ts#L41
From: https://github.com/felddy/foundryvtt-docker#optional

Name
Purpose
Default

FOUNDRY_AWS_CONFIG
An absolute or relative path that points to the awsConfig.json or true for AWS environment variable credentials evaluation usage.
null

No worries. I'll play around with a bit, and see if I can't figure it out and get a PR going. Thanks for the reply!

I'm guessing this is a type coercion issue, and I've never done anything in JavaScript but this seems to fix it:
function checkAwsConfig(
  AWS_CONFIG: string | any
) : boolean | string {
  if (!AWS_CONFIG) {
    return AWS_CONFIG;
  } else if (AWS_CONFIG.toLowerCase() === 'true') {
    return true
  } else if (AWS_CONFIG.toLowerCase() === 'false') {
    return false;
  } else {
    return AWS_CONFIG;
  }
}

if (process.env.FOUNDRY_DEMO_CONFIG) {
  parsedDemoConfig = JSON.parse(process.env.FOUNDRY_DEMO_CONFIG);
}

let options: object = {
  awsConfig: checkAwsConfig(process.env.FOUNDRY_AWS_CONFIG) || null,

Guessing you'll want something cleaner in a PR, so I won't open one.

authors: felddy luthes

repo: felddy/foundryvtt-docker


text:
Update sbt-scoverage to 2.0.1

Updates org.scoverage:sbt-scoverage from 2.0.0 to 2.0.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scoverage", artifactId = "sbt-scoverage" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #76.

repo: felipebonezi/play-ground


text:
feat: allow to pass a data & returnValue formatters

@Jivings, I've added this ability with a different approach.
// server.js

const Queue = require('bull')
const QueueMQ = require('bullmq')
const { setQueues, BullMQAdapter, BullAdapter } = require('bull-board')

const someQueue = new Queue()
const someOtherQueue = new Queue()
const queueMQ = new QueueMQ()

const someQueueAdapter = new BullAdapter(someQueue);

someQueueAdapter.setFormatter('data', ({ secret, ...rest }) => ({ ...rest })); // this will apply data formatter
someQueueAdapter.setFormatter('returnValue', ({ token, ...rest }) => ({ ...rest })); // this will apply returnValue formatter

setQueues([
  someQueueAdapter,
  new BullAdapter(someOtherQueue),
  new BullMQAdapter(queueMQ),
]);

closes #204

LGTM :)

authors: Jivings felixmosh

repo: felixmosh/bull-board


text:
perf: reduce peak memory usage and open files when loading bindle

This patch does two things:

Use bindle::client::Client::get_parcel_stream instead of get_parcel.  The
latter loads the whole asset into memory, while the former allows us to stream
into a local file chunk-by-chunk.

Limit parallel I/O in spin_loader::bindle::assets::Copier to avoid
hammering the Bindle server and also avoid running out of file descriptors.

This addresses https://github.com/fermyon/spin/issues/413.
Signed-off-by: Joel Dice joel.dice@gmail.com

This reduces peak memory usage from ~200MB to ~12MB for this test case.

repo: fermyon/spin


text:
How to set user-agent string in generated SDKs

What can be improved
I'm trying to figure out if it's currently possible to set a user-agent string in generated SDKs.
I found this Issue about it: https://github.com/fern-api/fern/issues/2264. Hard to tell from the history on that Issue whether support was added, and if it was I can't find "user-agent" anywhere in the docs.
If this is supported, could somebody advise on how to set it?

@dannysheridan you closed #2264 that this ticket references – any chance you can provide any guidance on this? Thank you! 🙏

Howdy @Arkessler and @mstade! Sending a user-agent string (e.g., User-Agent: ${package}/${version}) is not currently supported.
Today Fern includes the following request headers for the same purpose:
"X-Fern-Language": "${language}",
"X-Fern-SDK-Name": "${package}",
"X-Fern-SDK-Version": "${version}",

A user of Fern has added a UserAgent themselves. If helpful, here's a link the PR: https://github.com/AssemblyAI/assemblyai-java-sdk/pull/105/files

@amckinney do you plan to support this feature? If not, let's close this issue as not planned.

This feature is being rolled out now that its part of Fern's IR (PR). For example, this is available in TypeScript and C#.
Fern SDKs will send the User-Agent header in the <package>/<version> format. If you want to send a custom User-Agent header, you can set an arbitrary HTTP header using the specific language's mechanism.
For example, consider the following Go use case:
header := make(http.Header)
header.Add("User-Agent", "your/custom/user-agent")
client := acmeclient.NewClient(
  option.WithHTTPHeader(header), // These headers are sent on every request.
)

authors: Arkessler amckinney dannysheridan mstade

repo: fern-api/fern


text:
Cannot read property 'wires' of null

I've been able to run webtorrent with node on windows with a lot of success.
Recently I tried it on 2 different ubuntu servers (13.10 and 14.~), but I've been receiving these error messages and I'm not sure why:
/var/pnode/node_modules/webtorrent/node_modules/bittorrent-swarm/lib/peer.js:184
  self.swarm.wires.splice(self.swarm.wires.indexOf(self.wire), 1)
            ^
TypeError: Cannot read property 'wires' of null
    at Peer.destroy (/var/pnode/node_modules/webtorrent/node_modules/bittorrent-swarm/lib/peer.js:184:13)
    at Wire.destroy (/var/pnode/node_modules/webtorrent/node_modules/bittorrent-swarm/lib/peer.js:91:10)
    at Wire.g (events.js:175:14)
    at Wire.EventEmitter.emit (events.js:117:20)
    at finishMaybe (_stream_writable.js:352:12)
    at afterWrite (_stream_writable.js:272:5)
    at _stream_writable.js:259:9
    at process._tickCallback (node.js:415:13)

and
/var/pnode/node_modules/webtorrent/node_modules/bittorrent-swarm/lib/peer.js:184
  self.swarm.wires.splice(self.swarm.wires.indexOf(self.wire), 1)
            ^
TypeError: Cannot read property 'wires' of null
    at Peer.destroy (/var/pnode/node_modules/webtorrent/node_modules/bittorrent-swarm/lib/peer.js:184:13)
    at Timer.ontimeout (/var/pnode/node_modules/webtorrent/node_modules/bittorrent-swarm/lib/peer.js:171:57)

I've also seen a lot more ECONNRESET errors that didn't seem to show up when I was running it on Windows.. any ideas what could be causing this?

Fixed in bittorrent-swarm 5.0.3. webtorrent should inherit the fix if you're running the latest version and you run npm update.

authors: Froren feross

repo: feross/webtorrent


text:
uploadProgress获取上传进度间隔能调吗，间隔时间也太长了

uploadProgress获取上传进度间隔能调吗，间隔时间也太长了

小文件直接跳到100%

repo: fex-team/webuploader


text:
ios 9 支持上传图片么

ios 9 现在支持 不了上传图片，大神求解

求解决办法！！！TK


text:
如何在uploadSuccess后获得图片上传的按钮的dom对象

如何在uploadSuccess后获得图片上传的按钮的dom对象。option pick除外，因为我是用的class不是id。
求解大神！！

改成id
或用queryselector

同问，我也是class，多个按钮

在 uploadSuccess 函数中调用 this. 这这里 this 是 Uploader 对象。
console.log(this);

authors: dsky1990 liyugit lkebin yangedie


text:
[DOC12] Documento de arquitetura

Descrição da mudança

Criação do documento de arquitetura e adição dos diagramas.
Tipo da mudança

[ ] Correção de bug.
[x] Adição de nova fucionalidade.

Issue relacionada

https://github.com/fga-eps-mds/2019.2-Amika-Wiki/issues/45
Informações adicionais

O documento de arquitetura está na pasta docs e as imagens usadas nele na pasta assets/img
Checklist

[x] O pull request possui nome significativo.
[x] O pull request possui descrição significativa.
[x] O pull request possui a marcação correspondente ao tipo da mudança.
[ ] O pull request possui screenshots quando necessário.
[x] O pull request possui labels.

Muito bom galera, parabéns pelo documento!
Segue abaixo alguns pontos para melhorar no documento:

Existe o tópico 1.4 Referências bibliográficas mas ele está vazio.
Dentro das funcionalidades oferecidas pelo pwa estão django e um explicação sobre django, acho que deve ter sido algum erro de formatação.
Colocar um link no tópico do backlog para apontar para o backlog do produto.
Na visão de implementação do angular seria interessante colocar o app.service também.

Alterei algumas coisas em relação a organização do documento e alguns erros que eu encontrei, e também linkei o documento na sidebar.

As alterações foram feitas nos últimos commits.


text:
Integração com o Github Actions e SonarCloud

Integração com o Github Actions e SonarCloud
Issue
https://github.com/fga-eps-mds/2022-1-CAPJu-Doc/issues/43
Descrição
Criação do pipeline de validação de código e integração com o sonarcloud
Tipos de Mudanças

[ ] Bug fix (alteração ininterrupta que corrige um problema)
[x] Nova feature (mudança ininterrupta que adiciona funcionalidade)
[ ] Breaking change (correção ou recurso que faria com que a funcionalidade existente não funcionasse como esperado)
[ ] Documentação (adição ou remoção de algum artefato)

Checklist:

[ ] Meu código segue os padrões de estilo deste projeto.
[ ] Minha alteração requer uma alteração na documentação.
[ ] Atualizei a documentação de acordo.

A falha no passo Sonarcloud do pipeline é prevista, é necessário adicionar o repositório ao sonarcloud depois que o arquivo de configuração estiver na branch devel