text:
faker-cli should be a separate gem

Checklist

[x] Invite @akabiru  to be collaborator of this repository
[x] Move original fakerbot repository to organization
[ ] Publish faker-cli as a separate gem
[ ] Grant admin access to @stympy, @akabiru, @vbrazo on Rubygems.org

@akabiru thanks 👍

Cheers Vitor, I have some time. I'll amend amend the namespaces shortly. 👍 🙂

I'm not able to push the gem to Rubygems.org. We'll need your help on that @akabiru
(base) VOLIVEIRA-MBP:faker-cli voliveira$ gem push faker-cli-0.4.5.gem
Pushing gem to https://rubygems.org...
You do not have permission to push to this gem. Ask an owner to add you with: gem owner faker-cli --add vbrazo@email.com
(base) VOLIVEIRA-MBP:faker-cli voliveira$ gem owner faker-cli --add vbrazo@email.com
Adding vbrazo@email.com: You do not have permission to manage this gem.

Hey Vitor,
Sure thing.
Will try and address this as soon as possible.
I’m afk but should have access in the next 24hrs.
Best,
On Sun, 7 Jul 2019 at 9:08 pm, Vitor Oliveira notifications@github.com
wrote:

I'm not able to push the gem to Rubygems.org. We'll need your help on that
@akabiru https://github.com/akabiru
(base) VOLIVEIRA-MBP:faker-cli voliveira$ gem push faker-cli-0.4.5.gem
Pushing gem to https://rubygems.org...
You do not have permission to push to this gem. Ask an owner to add you with: gem owner faker-cli --add vbrazo@email.com
(base) VOLIVEIRA-MBP:faker-cli voliveira$ gem owner faker-cli --add vbrazo@email.com
Adding vbrazo@email.com: You do not have permission to manage this gem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/faker-ruby/faker-cli/issues/26?email_source=notifications&email_token=AED6ORZ32MH4SRGNLV5HFWLP6IWJFA5CNFSM4H6TR2U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZLQKRA#issuecomment-509019460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AED6ORZE2A4JRUTTFJAI3TLP6IWJFANCNFSM4H6TR2UQ
.

--
Austin Kabiru
Software Engineer / +254.714.665.734
Twitter: @akabiru_  GitHub: @akabiru

@vbrazo Looks like somebody alrealy owns faker-cli on ruby gems https://rubygems.org/gems/faker-cli
⋊> ~/p/a/faker-cli on master ◦ gem owner faker-cli                                  21:15:05
Owners for gem: faker-cli
- ich@dwgadf.de

Seems like we have to go with another name.
Some options off the top of my head:
1.) faker-cli-ruby - not as nice
2.) faker-bot - namespace Faker::Bot instead of Faker::CLI
3.)fakerbot (original name, I own this one)

@stympy which one would you prefer: fakerbot or faker-bot?

Let's do faker-bot.

@stympy @akabiru I've just granted access for your users on Rubygems.org. Now you can release new faker-bot versions.

authors: akabiru vbrazo

repo: faker-ruby/faker-cli


text:
fix(falco-exporter): fix FalcoExporterAbsent rule

What type of PR is this?
/kind bug
/kind cleanup
/kind chart-release
Any specific area of the project related to this PR?
/area falco-exporter-chart
What this PR does / why we need it:
Fixes this error:
The  "prometheusrules" is invalid: : 49:11: group "falco-exporter", rule 1, "FalcoExporterAbsent": could not parse expression: 1:31: parse error: unexpected character inside braces: ')'

Which issue(s) this PR fixes:
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

Signed-off-by: Lucas Bickel lucas.bickel@adfinis.com

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hairmare
To complete the pull request process, please assign issif after the PR has been reviewed.
You can assign the PR to them by writing /assign @issif in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hairmare, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 3aa63dd2e0286d7f82e47164cc46eb6296bdcd87

source: gharchive/pull-request

authors: hairmare poiana

repo: falcosecurity/charts

license_type: permissive

license_source: github-api


text:
fix(userspace/libsinsp): make sinsp struct size independent from compilation flags

What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
What this PR does / why we need it:
The libsinsp class struct size is currently dependent on some compilation flags masked under #ifdef definitions. This is troublesome for whoever imports the libs headers, as they may see a different struct size compared to the libsinsp object files, which inherently can lead to out-of-memory access and segfaults.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
fix(userspace/libsinsp): make sinsp struct size independent from compilation flags

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: b7c0d12886c1a84c875da53b08fe07a89485aa78

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.12.0
While small, this is very valuable for libs consumers since sinsp class size is now written in stone.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

/hold

LGTM label has been added.  Git tree hash: 7613b38fbd509acb77f6fef663f2d0a1c29b4d50

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/unhold

authors: Andreagit97 FedeDP jasondellaluce poiana

repo: falcosecurity/libs


text:
chore(driver): allow kmod and bpf drivers different components

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area build
/area driver-kmod
/area driver-bpf
Does this PR require a change in the driver versions?
What this PR does / why we need it:
This PR has a main scope: allow to install kmod and bpf under different components.
Also, now the ebpf probe gets built under CMAKE_CURRENT_BINARY_DIR instead of CMAKE_CURRENT_SOURCE_DIR, in a similar way to kmod.
Moreover, to properly build the bpf probe, all the driver/*.h header files are copied under CMAKE_CURRENT_BINARY_DIR for bpf and get eventually installed when issuing make install.
It has the main advantage that in the future we might want to split up falco-kmod and falco-bpf packages, BUT still retain the possibility to build the bpf probe under /usr/src/driverversion/bpf/ folder.
An example of the aforementioned issue is the current behavior if we configure libs using:
-DENABLE_DKMS=Off -DBUILD_DRIVER=Off -DBUILD_BPF=On ..

and then make install it. Under /usr/src/$version/ we will just have a bpf folder, and if we move under it, we cannot build the bpf probe because its sources include headers from the parent (that was not installed).
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.15.0

Driverkit / build-drivers (linux-4.x) (pull_request) Failing after 33s

Need to fix bpf build under driverkit :/

Driverkit 0.17.0 was released, and driverkit related tests now pass fine.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @jasondellaluce

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [FedeDP,jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: FedeDP poiana


text:
fix(driver/modern_bpf): address task_struct has no embedded thread_info

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area driver-modern-bpf
Does this PR require a change in the driver versions?
No
What this PR does / why we need it:
This PR fixes the cases in which the struct task_struct doesn't contain the field thread_info returning always false. If task_struct has no embedded thread_info, we cannot deduce anything. We just return false.
NOTE: this means that emulated 32bit syscalls will be parsed as 64bits syscalls.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Refs https://github.com/falcosecurity/libs/pull/1794

LGTM label has been added.  Git tree hash: 0d17496a78b041179ac7da972a84f50361ee9f6b

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97,FedeDP,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: Andreagit97 FedeDP poiana


text:
🛑 Archive is down

In c93f4ea, Archive (https://archive.stsci.edu) was down:

HTTP code: 400
Response time: 441 ms

Resolved: Archive is back up in ee95be0 after 8 minutes.

source: gharchive/issue

repo: falkben/mast-status

license: MIT


text:
🛑 Portal is down

In 71990cc, Portal (https://mast.stsci.edu/portal/Mashup/Clients/Mast/Portal.html) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal is back up in 04bec2b after 7 minutes.


text:
Hotfix/verify

重复校验

校验

repo: fantasticit/think


text:
up --init: Initialize containers at startup

In order to support initializating containers easily, we add an up --init command, which can invoke one or more cage run tasks to create database, apply migrations, etc. In order to make this reliable, we have a little magic:

We query the Docker daemon at runtime to get a list of exported ports for a container and its IP address.
We "port scan" the container to repeatedly until all the ports open up.

We also use this new Docker support to enhance cage status a bit.

I'm going to go ahead and merge this now so that I can work on another bug that will share the same test script. But please feel free to review it anyway!

@emk my one concern is that if you have a service with restart: always, running these scripts via docker run is going to leave containers continually running/restarting.

@dkastner Honestly, I really feel like cage containers shouldn't be declaring restart: "always" everywhere. If something falls over in development mode, then we shouldn't just keep endlessly restarting it. Instead, we should perhaps consider having some kind of cage watch mode that notifies the user of things like this.
And we could always have a plugin which strips restart: completely in development or test mode, or one which adds it in for release mode.

authors: dkastner emk

repo: faradayio/cage

license_source: bigquery


text:
When I run the timer, an unknown number appears and then disappears.

I set it up so that a 5 second timer starts when the button is clicked.
In version 1.2.1, when I click the button, an unknown number, 93, appears and then disappears.
In the 0.6.0 version, that number does not appear.
I didn't put anything in there except the duration property.
return SlideCountdown(duration: Duration(milliseconds: 5000));

[0.6.0]
https://github.com/farhanfadila1717/slide_countdown/assets/106897491/784531dd-3495-4947-ac2b-9bd88db9184d
[1.2.1 - bug]
https://github.com/farhanfadila1717/slide_countdown/assets/106897491/7d194638-adbb-476e-8362-495e3731b84d

@farhanfadila1717
Using version 1.2.2 fixed the unknown numbers, thank you.
But when the first number is sliding, the animation is not playing.
For example, if I set a timer for 5 seconds,
I get 5 -- no animation --> 4 -> 3 -> 2 -> 1

@synstin checkout the lastest version, i have refacor the RawDigitItem widget.

@farhanfadila1717
Thank you so much. But, This has been fixed, but a new error occurs.
flutter: 'package:flutter/src/animation/animation_controller.dart': Failed assertion: line 527 pos 7: '_ticker != null': AnimationController.animateTo() called after AnimationController.dispose()
AnimationController methods should not be used after calling dispose.
flutter:
#0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:51:61)
#1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:40:5)
#2      AnimationController.animateTo (package:flutter/src/animation/animation_controller.dart:527:7)
#3      _RawDigitItemState.playHalfControllerOne (package:slide_countdown/src/widgets/raw_digit_item.dart:134:26)

And slideAnimationDuration option and the curve option are gone.
Is it not possible to customize slideAnimationDuration and curve now?
The sliding speed is too slow.
I'm really sorry for the continued demand.

@synstin whoop it's seems i forgot check the widget still mounted or disposing. i've tried to fix this, checkout the latest version.
thanks for using and reporting issue in my OS, i really appreciate it 🍻

@synstin yes it's true, i decided to remove slide Countdown duration and curve.

Hi @synstin  sorry for late reply, now you can custom slide animation duration. Please check out slide_countdown 2.0.1-dev+1

@farhanfadila1717 Thank you, but is it possible to change the animation curves? I was able to in the previous version.

@farhanfadila1717
Setting slideAnimationDuration has no effect.

@synstin I have fixed it and published it in the latest dev version. checkout https://pub.dev/packages/slide_countdown/versions/2.0.1-dev+2


text:
Adding important guideline documents

Hi,
May I contribute some interesting documentation for this project, like setup documentation, code of conduct, code contribution and Bug reports guidelines.

Thanks for your offer. I think the current README.md is fine for now as it's just me developing this project and I don't get a lot of frequently asked questions.

authors: farmerbb santoshhiremani

repo: farmerbb/Notepad


text:
Not compatible with netstandard2.0 (.NETStandard,Version=v2.0).

Not compatible with netstandard2.0 (.NETStandard,Version=v2.0).

I added support for netstandart
you can use https://www.nuget.org/packages/HDWallet.Tron/0.5.0

Thank you~  And by the way, I think it's a very useful suggestion: this project should consider fully supporting xamarin (. Netstandard). Mobile wallet app is very popular

What is missing from full support?

The target version is not required to be the highest

Many projects are incompatible，please target version is  .net standard 2.0

Can't you target 2.1 instead of 2.0

authors: farukterzioglu liuzhenLz

repo: farukterzioglu/HDWallet


text:
fast-curd全局配置切换多语言时 部分字段没有翻译成目标语言

感谢您支持fast-crud，请按如下规范提交issue
如果有条件，请尽量在github上提交

一、问题描述
fast-curd全局配置切换多语言时 部分字段没有翻译成目标语言
复现步骤
[示例地址](http://fast-crud.docmirror.cn/antdv/#/crud/component/text) 打开示例页面 左上角选择切换语言为英语
代码截图

报错截图

效果截图

二、当前使用的库版本
1. fast-crud版本：
    "@fast-crud/fast-crud": "^1.3.0",     "@fast-crud/fast-extends": "^1.3.0",     "@fast-crud/ui-antdv": "^1.3.0",
2. 使用的ui库以及版本
中括号中输入x即选中，或者删除其他，仅保留你正使用的ui库

[x] Antdv (版本？)
[ ] ElementPlus（版本？）
[ ] NaiveUI（版本？）

3. 使用的admin框架
请您填写您当前使用的admin框架是哪一套

[x] fs-admin-antdv
[ ] fs-admin-element
[ ] fs-admin-naive
[ ] fs-in-vben
[ ] vben-admin
[ ] cool-admin
[ ] 其他：请注明

1.4.0 已修复

authors: greper zhaohejing

repo: fast-crud/fast-crud


text:
Some additional LU algos

A few more LU algorithms

Awesome :)

repo: fastats/learning


text:
IP local address show by default?

There is probably some reason why others also dont show it by default
but I feel like its one of the major info you want
but at least in neofetch all I have to do is uncomment one line info "Local IP" local_ip
while it seems more hands on with fastfetch
seems like I would have to redo the defaul json to just have it there, not sure

It's explictly forbidden by the project author @LinusDierheimer. See https://github.com/fastfetch-cli/fastfetch/pull/92#discussion_r730408469

seems like I would have to redo the defaul json to just have it there, not sure

What do you mean redo? You can either generate the default json file with fastfetch --migrate-config and add localip into it, or copy / download the presets/all.json and disable things you don't need.

It's explictly forbidden by the project author @LinusDierheimer. See https://github.com/fastfetch-cli/fastfetch/pull/92#discussion_r730408469

I think i mixed up public and local IP there. @CarterLi Do as you think.

Awesome, thanks!
I use fastfetch when posting submissions on /r/homeserver about power consumption, like this one and I love that it works it works in windows and linux the same.

Which fastfetch version were you using? (Default string) printed in Host module was unexpected. Really strange...

When I use it from SSH it shows public ip instead of local ip.
And sorry to say this but showing local ip and locale by default does not look a sane default.

Right I was one of those person, it's local ip sorry.

authors: CarterLi DoTheEvo LinusDierheimer realroot2185

repo: fastfetch-cli/fastfetch


text:
Posting release notes returns 400

This seems like it's related to this issue
Here is what I'm getting from the logs
/home/travis/.rvm/gems/ruby-2.4.1/gems/faraday-1.0.1/lib/faraday/response/raise_error.rb:16:in `on_complete': [!] the server responded with status 400 (Faraday::BadRequestError)
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/faraday-1.0.1/lib/faraday/response.rb:12:in `block in call'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/faraday-1.0.1/lib/faraday/response.rb:65:in `on_complete'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/faraday-1.0.1/lib/faraday/response.rb:11:in `call'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/faraday_middleware-1.0.0/lib/faraday_middleware/response_middleware.rb:36:in `call'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/faraday-1.0.1/lib/faraday/rack_builder.rb:153:in `build_response'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/faraday-1.0.1/lib/faraday/connection.rb:492:in `run_request'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/faraday-1.0.1/lib/faraday/connection.rb:279:in `post'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-plugin-firebase_app_distribution-0.2.3/lib/fastlane/plugin/firebase_app_distribution/client/firebase_app_distribution_api_client.rb:69:in `post_notes'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-plugin-firebase_app_distribution-0.2.3/lib/fastlane/plugin/firebase_app_distribution/actions/firebase_app_distribution_action.rb:37:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	from Fastfile:146:in `block (2 levels) in parsing_binding'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
	from /home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.162.0/bin/fastlane:23:in `<top (required)>'
	from /home/travis/.rvm/gems/ruby-2.4.1/bin/fastlane:23:in `load'
	from /home/travis/.rvm/gems/ruby-2.4.1/bin/fastlane:23:in `<main>'
	from /home/travis/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `eval'
	from /home/travis/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `<main>'

Here are the versions
Fastlane: 2.162.0
+---------------------------------------------+---------+---------------------------------+
|                                      Used plugins                                       |
+---------------------------------------------+---------+---------------------------------+
| Plugin                                      | Version | Action                          |
+---------------------------------------------+---------+---------------------------------+

| fastlane-plugin-commit_android_version_bump | 0.2.0   | commit_android_version_bump     |
| fastlane-plugin-android_versioning          | 0.5.3   | get_version_code                |
|                                             |         | increment_version_name          |
|                                             |         | get_value_from_build            |
|                                             |         | set_value_in_build              |
|                                             |         | get_version_name                |
|                                             |         | increment_version_code          |
| fastlane-plugin-firebase_app_distribution   | 0.2.3   | firebase_app_distribution_login |
|                                             |         | firebase_app_distribution       |
+---------------------------------------------+---------+---------------------------------+

Here is how I'm calling the firebase_app_distribution from the Fastfile
    firebase_app_distribution(
      app: "my_app_id...",
      groups: "group1,group2",
      release_notes_file: "fastlane/changelog.txt"
    )

And I was able to get it to build by calling the firebase_app_distribution and setting the release_notes to an empty string like this
    firebase_app_distribution(
      app: "my_app_id...",
      groups: "group1,group2",
      release_notes: ""
    )

@Furman950 how long are the release notes in fastlane/changelog.txt? I think this may be related to artyomdevyatov's comment in issue #159. We have a 16384 character limit on release notes.
We'll look into adding a better error messaging.

@tagboola Yeah your right, my change log has more that the character limit... Thanks!

Hey @Furman950 with v0.2.4 we now show a less generic error message when release notes are too long 🙂

license: mit


text:
[XWATCH~VIDEOs-NOW]™ Ari kytsya Leaked Video Viral On Twitter Official Leaks (√20kNOW)

[XWATCH~VIDEOs-NOW]™ Ari kytsya Leaked Video Viral On Twitter Official Leaks (√20kNOW)
20 𝗌𝖾𝖼𝗈𝗇𝖽 𝖺𝗀𝗈 - 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝗏𝗂𝖽𝖾𝗈 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝗋𝖺𝗅 𝗍𝗁𝖾 𝗂𝗇𝗍𝖾𝗋𝗇𝖾𝗍 𝖻𝗒 𝗌𝗍𝗈𝗋𝗆 𝖺𝗇𝖽 𝖺𝗆𝖺𝗓𝖾𝖽 𝗏𝗂𝖾𝗐𝖾𝗋𝗌 𝗈𝗇 𝗏𝖺𝗋𝗂𝗈𝗎𝗌 𝗌𝗈𝖼𝗂𝖺𝗅 𝗆𝖾𝖽𝗂𝖺 𝗉𝗅𝖺𝗍𝖿𝗈𝗋𝗆𝗌. 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺.𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺.𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺.

𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024.𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024. 𝖳𝗁𝖾 𝗋𝖾𝖼𝗎𝗋𝗋𝖾𝗇𝗍 𝗍𝗁𝖾𝗆𝖾 𝗈𝖿 𝖫𝖾𝖺𝚔𝖾𝖽 𝗍𝖺𝗉𝖾𝗌 𝖺𝗇𝖽 𝗍𝗁𝖾 𝗌𝗎𝖻𝗌𝖾𝗊𝗎𝖾𝗇𝗍 𝖿𝖺𝗅𝗅𝗈𝗎𝗍 𝗌𝖾𝗋𝗏𝖾𝗌 𝖺𝗌 𝖺 𝗋𝖾𝗆𝗂𝗇𝖽𝖾𝗋 𝗈𝖿 𝗍𝗁𝖾 𝖿𝗋𝖺𝗀𝗂𝗅𝗂𝗍𝗒 𝗈𝖿 𝗋𝖾𝗉𝗎𝗍𝖺𝗍𝗂𝗈𝗇 𝗂𝗇 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖾𝗋𝖺. 𝖠𝗌 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾𝗌 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝗉𝗋𝗂𝗏𝖺𝗍𝖾 𝖺𝗇𝖽 𝗉𝗎𝖻𝗅𝗂𝖼 𝗅𝗂𝖿𝖾 𝖼𝗈𝗇𝗍𝗂𝗇𝗎𝖾 𝗍𝗈 𝖻𝗅𝗎𝗋, 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗂𝖾𝗌 𝗅𝗂𝗄𝖾 𝖯𝗋𝗂𝗌𝗈𝗇 𝖮𝖿𝖿𝗂𝖼𝖾𝗋𝖿𝗂𝗇𝖽 𝗍𝗁𝖾𝗆𝗌𝖾𝗅𝗏𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝗆𝖾𝗋𝖼𝗒 𝗈𝖿 𝗂𝗇𝗍𝖾𝗋𝗇𝖾𝗍 𝖼𝗁𝖺𝗍𝗍𝖾𝗋, 𝗐𝗁𝖾𝗋𝖾 𝖺 𝗋𝗎𝗆𝗈𝗋 𝖼𝖺𝗇 𝗂𝗀𝗇𝗂𝗍𝖾 𝖺 𝖿𝗂𝗋𝖾𝗌𝗍𝗈𝗋𝗆 𝗈𝖿 𝗌𝗉𝖾𝖼𝗎𝗅𝖺𝗍𝗂𝗈𝗇 𝖺𝗇𝖽 𝗃𝗎𝖽𝗀𝗆𝖾𝗇𝗍.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

Thank You

ndw
✅🟢 HD VIDEO PLAY NOW ▶
✅🟢 PLAY NOW ONLINE

✅🟢 HD HOT ONLINE

✅🟢 PLAY NOW ONLINE

✅🟢 HD VIDEO PLAY NOW ▶

✅🟢 PLAY NOW LIVE ▶

[ PLY ]
✅🟢 HD VIDEO PLAY NOW ▶
✅🟢 PLAY NOW ONLINE

✅🟢 HD HOT ONLINE

✅🟢 PLAY NOW ONLINE

✅🟢 HD VIDEO PLAY NOW ▶

✅🟢 PLAY NOW LIVE ▶

vcd

repo: fastlane/fastlane


text:
Scan hangs when getting build settings

New Issue Checklist

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

Issue Description
Scan hangs when getting the build settings:
xcrun xcodebuild -showBuildSettings -workspace './App.xcworkspace' -scheme 'AppTests'

A couple things to note:

I thought that it was related to https://github.com/fastlane/fastlane/issues/1844 since it was the last command showing up in the logs, but after looking at the stacktrace when I force quite fastlane, it seems that it's actually hanging on showBuildSettings.
I can reproduce the freeze by running the -showBuildSettings command manually, though it only happens one time out of five, something like that.
It happens consistently when running in a CI environment (circleci 7.3)
It started happening after I removed all files in the App target from the AppTests target. Instead, I now have @testable import App everywhere. This change required to modify my Podfile to have different pods for the AppTests target (see below)
DerivedData is relative to my project directory.

Complete output when running fastlane, including the stack trace and command used
Please note that I modified fastlane_core's sources to show the build settings command, which is why it shows up in the logs. If I hadn't, only the -list command would appear.
ldiqual@ldiqual-mbp ~/S/App-ios-test1> bundle exec fastlane test --verbose
/Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/user_interaction.rb:334: warning: constant ::TimeoutError is deprecated
INFO [2016-04-04 15:18:48.74]: ---------------------------
INFO [2016-04-04 15:18:48.74]: --- Step: opt_out_usage ---
INFO [2016-04-04 15:18:48.74]: ---------------------------
INFO [2016-04-04 15:18:48.74]: Disabled upload of used actions
INFO [2016-04-04 15:18:48.74]: -------------------------------------------------
INFO [2016-04-04 15:18:48.74]: --- Step: Verifying required fastlane version ---
INFO [2016-04-04 15:18:48.74]: -------------------------------------------------
INFO [2016-04-04 15:18:48.74]: fastlane version valid
INFO [2016-04-04 15:18:48.74]: ------------------------------
INFO [2016-04-04 15:18:48.74]: --- Step: default_platform ---
INFO [2016-04-04 15:18:48.74]: ------------------------------
INFO [2016-04-04 15:18:48.91]: Driving the lane 'ios test' 🚀
INFO [2016-04-04 15:18:48.91]: ------------------
INFO [2016-04-04 15:18:48.91]: --- Step: scan ---
INFO [2016-04-04 15:18:48.91]: ------------------
WARN [2016-04-04 15:18:48.93]: xcrun xcodebuild -list -workspace './App.xcworkspace'
2016-04-04 15:18:50.261 xcodebuild[94625:3349109] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/SparkInspectorXcodePlugin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-04 15:18:50.265 xcodebuild[94625:3349109] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FixCode.xcplugin' not present in DVTPlugInCompatibilityUUIDs
INFO [2016-04-04 15:18:51.94]: $ xcrun xcodebuild -showBuildSettings -workspace './App.xcworkspace' -scheme 'AppTests'
2016-04-04 15:18:52.174 xcodebuild[94629:3349189] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/SparkInspectorXcodePlugin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-04 15:18:52.176 xcodebuild[94629:3349189] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FixCode.xcplugin' not present in DVTPlugInCompatibilityUUIDs
^C/Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.1/lib/fastlane_core/helper.rb:51:in ``': Interrupt
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.1/lib/fastlane_core/helper.rb:51:in `backticks'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.1/lib/fastlane_core/project.rb:203:in `build_settings'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.1/lib/fastlane_core/project.rb:168:in `mac?'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.1/lib/fastlane_core/project.rb:180:in `ios?'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/scan-0.5.2/lib/scan/detect_values.rb:23:in `set_additional_default_values'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/scan-0.5.2/lib/scan.rb:27:in `config='
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/scan-0.5.2/lib/scan/manager.rb:4:in `work'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/actions/scan.rb:10:in `run'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/runner.rb:143:in `block (2 levels) in execute_action'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/runner.rb:129:in `block in execute_action'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/runner.rb:128:in `chdir'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/runner.rb:128:in `execute_action'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/fast_file.rb:149:in `method_missing'
    from Fastfile:16:in `block (2 levels) in parsing_binding'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/lane.rb:36:in `call'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/runner.rb:52:in `block in execute'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/runner.rb:46:in `chdir'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/runner.rb:46:in `execute'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/lib/fastlane/command_line_handler.rb:30:in `handle'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/bin/fastlane:38:in `block (2 levels) in run'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.1/lib/fastlane_core/ui/fastlane_runner.rb:23:in `run!'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/bin/fastlane:156:in `run'
    from /Users/ldiqual/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane-1.70.0/bin/fastlane:162:in `<top (required)>'
    from /Users/ldiqual/.rbenv/versions/2.3.0/bin/fastlane:23:in `load'
    from /Users/ldiqual/.rbenv/versions/2.3.0/bin/fastlane:23:in `<main>'

ldiqual@ldiqual-mbp ~/S/App-ios-test1> xcrun xcodebuild -showBuildSettings -workspace './App.xcworkspace' -scheme 'AppTests'
2016-04-04 15:31:51.235 xcodebuild[94673:3360581] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/SparkInspectorXcodePlugin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-04 15:31:51.238 xcodebuild[94673:3360581] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FixCode.xcplugin' not present in DVTPlugInCompatibilityUUIDs
Build settings for action build and target AppTests:

Note that the command above doesn't exit (1 time out of 5), I have to force kill it.
Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
opt_out_usage
fastlane_version "1.49.0"
default_platform :ios

platform :ios do
  desc "Runs all the tests"
  lane :test do
    scan(scheme: "AppTests")
  end
end

Podfile:
source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '9.0'
use_frameworks!
inhibit_all_warnings!

abstract_target 'Common' do

    target 'App'

    target 'AppTests' do
        pod 'SomePod'
    end

    pod 'SomeOtherPod'
end

Environment
fastlane 1.70.0
Bundler + rbenv
ruby 2.3.0
xcode 7.3
cocoapods 1.0.0.beta.6

Looks like carthage had the same issue and added a timeout: https://github.com/Carthage/Carthage/pull/1120. And also on xctool: https://github.com/facebook/xctool/issues/295

Hi @ldiqual Hope you are doing well! Can you let me know if this is a duplicate of #3886? Thanks!

I solved this by having fewer targets in the scheme, I'm not sure if this applies to you. Oddly enough I was only experiencing this inside a VM, there is definitely something sketchy but after some investigation I blame xcodebuild

@TKBurner Thanks for getting back to me. I'm not too sure why you're thinking those issues could be related, I don't see any mention of -showBuildSettings hanging.
@stepanhruda Turns out that I worked around the issue by using scan on the main scheme instead of the test scheme. To be more specific, I had two schemes: App and AppTests, and was running scan ... -scheme AppTests, which was hanging during the -showBuildSettings step. Using scan ... - scheme App fixed the issue. As a result, I deleted the AppTests scheme to avoid future confusion.
I'll close the issue since I won't be able to reproduce it anyway, but @TKBurner I believe fastlane should have a timeout+retry on the showBuildSettings step, as implemented by other tools (see links above).
Thanks and have a great day!

@ldiqual Thanks for following up. I'm going to mark this as a feature request so we can triage your idea:
I believe fastlane should have a timeout+retry on the showBuildSettings step, as implemented by other tools (see links above).'
Really glad to have you using Fastlane :+1:

We sorted this by moving the test schema up in the list of Manage Schemes. We had some schemes with spaces in - not sure if that could be part of the problem? We moved it above them and it started working.
Similar environment, CI (Jenkins) with rbenv.
Although - might have just been coincidental...

@bencollier Thanks for documenting your fix!

I'm having the same problem with a similar environment, my CI is TeamCity and I don't use rbenv (only Bundler). +1000 for timeout+retry
Also the logs should print the command that is being run, instead of the previous one.

Should this issue be closed since it is now a feature request?

@fcy Thanks for following up. We'll review this as a team and reply to it as a feature request. Hope that you have a wonderful week!

Forgot to mention that none of the fixes worked for me. It happens constantly I the only that works for me is re-run the CI build.

@fcy Thanks for following up 👍 We'll follow up here with relevant updates.

One more thing for when you guys discuss it. If adding the auto-retry if not a good idea for you, at least add the timeout to make it fail fast so CI builds don't hang for 10 minutes or more before getting killed.

@fcy Thanks for following up! Good point 👍

We hit this again in a different project, again running on Jenkins. Trying all these things fixed it;

Unticking show on all of the schemes that aren't actively used (for example, all the pods)
Unticking Shared on all the shared schemes
Reticking Shared on all the shared schemes
Changing some of the Scheme settings (like the targets that should be built)

It seems that sometimes the project / scheme files just needs something to change to fix this, these steps above seem to somehow kick it into action.

Hi @bencollier Thanks for following up. Can you let me know if it works consistently if you only have one target per scheme? Thanks!

Thanks for sharing @bencollier. FWIW I tried and none of that solved it for me.

Finally! PR #4492 fixes the problem once and for all. I hope it gets merged.

Thanks @fcy! I'm going to bump that pull request internally so we can hopefully merge soon 👍

Any news or plans to create a new PR?

Any updates on this? I am also seeing this happen once we upgraded to Xcode 7.3.1

Our CI environment suffers from the same, since I upgraded it to Xcode 7.3.1
To be more exact, something strange is happening:
We are using rvm with ruby 2.2.3. It seems that everything is fine with fastlane version 1.81.0, but this problem occurs with fastlane version 1.98.0
I also thougth that maybe rvm/rbenv is causing this somehow, since @ldiqual said, that they are using rbenv.

FWIW we don't use rvm/rbenv, we use the system Ruby. And we keep OS X up to date.

To be more specific we get stuck on this:
xcodebuild -list -workspace ....

@ilsinszkibal Was it just the last message in your log or you performed some debugging? I found out that the real command in my case was xcrun xcodebuild -showBuildSettings ... despite that last message was xcodebuild -list -workspace .... (lack of logging).

Oh, I see :)
It was just the last message on the console log

Hi @ilsinszkibal and @dragvs can you share your full input and output? I want to take a look into this. Hope you have a great day! 👍

Thanks a lot, it is on my list to collect everything to be able to reproduce this!

Sorry for the late response. I've tried out a number of things. Currently I realised, that this script will also get stuck without using fastlane. I am currently checking out if this only occures for all of our iOS projects -even the smaller ones- or if this has to do something with the project settings/size.
#!/bin/bash

set -ex

for i in `seq 1 10`;
do
	currentDate=`date`
	echo "Try:$i Date:$currentDate"
	xcodebuild -showBuildSettings -workspace ...xcworkspace -scheme ...iOSTests
done

Update: we've managed to figure out what is causing the problem for us:
In our project the shared unit test scheme was set to Analyze Test and Build(Edit Scheme, on the Build section). Once we removed Analyze and Build the problem went away.
The way we figured this out, in case any poor soul needs to solve this:

Modified the script above to run 30 times. Started running on the local project.
Figured out that the problem occurred for our test scheme and not our main scheme.
Confirmed that a new unit test target and scheme was fine.
Started to delete everything and reset all settings on the test scheme and target in question and checked if the problem is still there.

@ilsinszkibal thanks for sharing your workaround, unfortunately it does not work with my projects :'(

Xcode 8 beta 4 still has the same problem #5163
PR #5188 seems to fix the issue

@hotbott We'll work with you on those issues. Thanks!

Closed? Has it been fixed (I mean a fix merged and released)?

@fcy What version of Xcode are you still experiencing this in? Thanks!

@TKBurner 7.3.1, I have been using #5188 to solve the problem but simce it isn't merged I asked to see if there were an official merged fix already.

FWIW I am still experiencing this issue with XCode 8 Beta 5. It seems to me that fastlane does sometimes retry once, but that retry may also hang so I have to retry manually.

@TKBurner I can see this issue on several App and Library projects. That leads to a hanging build server.
PR #5188 solves the issue. What's the reason not to accept it?
I don't want to remove fastlane from our projects, but that workaround is currently under discussion in my team.

Hi @hotbott Are you using Xcode 7 or 8? We are working on merging our PRs, so you'll see this in master soon.
Thanks!

I'm having the same issue (using Xcode 7), this is getting pretty frustrating.

@revile Have you checked out the PR to see if it clears things up for you? Thanks!

@TKBurner We're using Xcode 7.3.1 but Xcode 8 beta still has the same problem.
Thanks

@TKBurner The PR will definitely help. Like others I can reproduce the issue manually in the command line by running the command in question, roughly 20% of the time this will hang in Terminal. Retrying will fix it.

@revile Thanks! Are you able to run it locally. We are working to merge our PRs but as you can see there are about 30 right now so it'll be faster for you to use that version until we are able to merge.
Thanks!

Hi all, we've shipped a workaround (#5626) and timeout/retry solution (#5188) as part of fastlane_core 0.51.0 🚀
Thanks very much for your help! Please let us know how it looks 👍

To test the latest release, please run [sudo] gem update fastlane_core or if you have a Gemfile, bundle update

Thanks for merging! It works :)

Hi all, gym 1.9.0 💪 and scan 0.12.0 🔍 have been released to pick up these fastlane_core improvements.
To get updated and try them out, please run [sudo] gem update gym scan :rocket:

I'm going to close this for now, but please feel free to continue the conversation and we can reopen as needed! 👍

authors: TKBurner arkku arunks bencollier dragvs fcy hotbott ilsinszkibal ldiqual mfurtak revile stepanhruda


text:
Pilot: Need to specify -itc_provider error when supplying team name

New Issue Checklist

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

Issue Description
Pilot is asking for itc_provider when trying to upload an app. We use Deliver and Pilot on a few of our apps on the same account but for some reason this one specific app refuses to submit and the iTMSTransporter issue bubbles up despite us providing team name. Originally the issue was popping up in Bitrise CI for us but I tried exporting the IPA myself and using Pilot via the command line with no success. Not sure where I'm going wrong here. As far as I can see providing itc_provider isn't necessary because I provide team name and looking at the logs it seems to identify the team correctly from this but fail on upload. Please let me know if there are any further details I can provide that would be of use.
Complete output when running fastlane, including the stack trace and command used
Matthews-MBP:Local iOS matthewcheetham$ pilot upload --team_name "American Red Cross" --ipa /Users/matthewcheetham/Desktop/First\ Aid\ 2.0\ 2016-10-13\ 09-27-41/First\ Aid\ 2.0.ipa --verbose
WARN [2016-10-13 09:34:01.30]: To not be asked about this value, you can specify it using 'username'
Your Apple ID Username: email@domain.com
INFO [2016-10-13 09:34:05.09]: Login to iTunes Connect (email@domain.com)
Looking for iTunes Connect Team with name American Red Cross
Looking for iTunes Connect Team with ID 351910
INFO [2016-10-13 09:34:11.65]: Login successful
DEBUG [2016-10-13 09:34:11.68]: App identifier (com.americanredcross.firstaid)
INFO [2016-10-13 09:34:14.42]: Ready to upload new build to TestFlight (App: 529160691)...
INFO [2016-10-13 09:34:15.00]: Wrote XML data to '/tmp/529160691.itmsp'
INFO [2016-10-13 09:34:15.27]: Going to upload updated app to iTunes Connect
INFO [2016-10-13 09:34:15.27]: This might take a few minutes. Please don't interrupt the script.
DEBUG [2016-10-13 09:34:15.33]: /Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/java/bin/java -Djava.ext.dirs=/Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/java/lib/ext -XX:NewSize=2m -Xms32m -Xmx1024m -Xms1024m -Djava.awt.headless=true -Dsun.net.http.retryPost=false -classpath /Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/lib/itmstransporter-launcher.jar com.apple.transporter.Application -m upload -u email@domain.com -p YourPassword -f /tmp/529160691.itmsp -t Signiant -k 100000 2>&1
DEBUG [2016-10-13 09:34:18.66]: [Transporter]: INFO: Transporter is skipping bundle update check: Already checked recently.
DEBUG [2016-10-13 09:34:18.82]: [Transporter]: INFO: Logging configured successfully.
DEBUG [2016-10-13 09:34:18.82]: [Transporter]: DEBUG: Attempting refresh of configuration data from https://contentdelivery.itunes.apple.com/transporter/Defaults.properties
DEBUG [2016-10-13 09:34:18.98]: [Transporter]: DEBUG: Configuration refresh successful.
DEBUG [2016-10-13 09:34:18.98]: [Transporter]: DEBUG: Saving configuration to local path: /Users/matthewcheetham/.itmstransporter/Defaults.properties
DEBUG [2016-10-13 09:34:18.98]: [Transporter]: INFO: iTMSTransporter : iTunes Store Transporter [1.9.0]
DEBUG [2016-10-13 09:34:18.98]: [Transporter]: INFO: OS identifier: Mac OS X 10.12 (x86_64); jvm=24.80-b07; jre=1.7.0-internal-root_2015_05_12_09_52-b00
DEBUG [2016-10-13 09:34:18.98]: [Transporter]: INFO: Memory: [JVM] 853M free, 982M total, 982M max [System] (Physical) 85M free, 16384M total (Swap) 928M free, 5120M total
DEBUG [2016-10-13 09:34:18.99]: [Transporter]: INFO: Upload mode selected.
DEBUG [2016-10-13 09:34:19.00]: [Transporter]: INFO: Examining the package at: /tmp/529160691.itmsp
DEBUG [2016-10-13 09:34:19.00]: [Transporter]: INFO: Ensuring that package has well formed metadata file...
DEBUG [2016-10-13 09:34:19.00]: [Transporter]: DEBUG: Getting case-sensitive metadata xml filename...
DEBUG [2016-10-13 09:34:19.00]: [Transporter]: INFO: Gathering the list of valid files from the package ...
DEBUG [2016-10-13 09:34:19.00]: [Transporter]: DEBUG:   3cdb0f86e0f0b7161689273ee0fc18b0.ipa will be verified by Apple's web service to determine if it is a valid file.
DEBUG [2016-10-13 09:34:19.00]: [Transporter]: DEBUG:   metadata.xml will be verified by Apple's web service to determine if it is a valid file.
DEBUG [2016-10-13 09:34:19.00]: [Transporter]: INFO: Finished gathering the list of valid files from the package.
DEBUG [2016-10-13 09:34:19.00]: [Transporter]: DEBUG:   Case-sensitive metadata filename is: metadata.xml
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: INFO: Performing authentication of package 529160691.itmsp ...
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X: Memory: [JVM] 843M free, 982M total, 982M max [System] (Physical) 75M free, 16384M total (Swap) 927M free, 5120M total
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X: Memory: [JVM] 843M free, 982M total, 982M max [System] (Physical) 75M free, 16384M total (Swap) 927M free, 5120M total
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X: Using operation named: authenticateForSession
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X: Apple's web service operation input parameters:
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X:   parameter Application = iTMSTransporter
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X:   parameter BaseVersion = 1.9.0
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X:   parameter OSIdentifier = Mac OS X 10.12 (x86_64); jvm=24.80-b07; jre=1.7.0-internal-root_2015_05_12_09_52-b00
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X:   parameter Password = **hidden value**
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X:   parameter TransporterArguments = -m upload -u email@domain.com -p **hidden value** -f /tmp/529160691.itmsp -t Signiant -k 100000
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X:   parameter Username = email@domain.com
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X:   parameter Version = 1.9.0
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: DBG-X:   parameter iTMSTransporterMode = upload
DEBUG [2016-10-13 09:34:19.05]: [Transporter]: INFO: id = 20161013093419-767
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X: Apple's web service operation return value:
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter SessionId = CIqnDBIQltnHo5wDTD6iKTRHTpXPKg==
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter SharedSecret = 42e2797e-4391-4e3b-b903-337ccdfac204
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X: Deflated 452 bytes to 392
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X: Using operation named: validateMetadata
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X: Apple's web service operation input parameters:
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter Application = iTMSTransporter
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter BaseVersion = 1.9.0
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter Files = [3cdb0f86e0f0b7161689273ee0fc18b0.ipa, metadata.xml]
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter Metadata = <?xml version="1.0" encoding="UTF-8"?>
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter MetadataChecksum = 7ed8d16438a4dd34bfe3c974c307159e
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter MetadataCompressed = (suppressed)
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter OSIdentifier = Mac OS X 10.12 (x86_64); jvm=24.80-b07; jre=1.7.0-internal-root_2015_05_12_09_52-b00
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter PackageName = 529160691.itmsp
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter PackageSize = 100302566
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter Throttle = 100000
DEBUG [2016-10-13 09:34:19.62]: [Transporter]: DBG-X:   parameter TransporterArguments = -m upload -u email@domain.com -p **hidden value** -f /tmp/529160691.itmsp -t Signiant -k 100000
DEBUG [2016-10-13 09:34:19.63]: [Transporter]: DBG-X:   parameter Username = email@domain.com
DEBUG [2016-10-13 09:34:19.63]: [Transporter]: DBG-X:   parameter Version = 1.9.0
DEBUG [2016-10-13 09:34:19.63]: [Transporter]: DBG-X:   parameter iTMSTransporterMode = upload
DEBUG [2016-10-13 09:34:19.63]: [Transporter]: INFO: id = 20161013093419-647
DEBUG [2016-10-13 09:34:33.99]: [Transporter]: DBG-X: Apple's web service operation return value:
DEBUG [2016-10-13 09:34:34.00]: [Transporter]: DBG-X:   parameter ErrorMessage = Your Apple ID account is attached to other iTunes providers. You will need to specify which provider you intend to submit content to by using the -itc_provider command. Please contact us if you have questions or need help. (1627)
DEBUG [2016-10-13 09:34:34.00]: [Transporter]: DBG-X:   parameter Errors = [Your Apple ID account is attached to other iTunes providers. You will need to specify which provider you intend to submit content to by using the -itc_provider command. Please contact us if you have questions or need help. (1627)]
DEBUG [2016-10-13 09:34:34.00]: [Transporter]: DBG-X:   parameter ErrorCode = 1627
DEBUG [2016-10-13 09:34:34.00]: [Transporter]: DBG-X:   parameter Success = false
ERROR [2016-10-13 09:34:34.00]: [Transporter Error Output]: Your Apple ID account is attached to other iTunes providers. You will need to specify which provider you intend to submit content to by using the -itc_provider command. Please contact us if you have questions or need help. (1627)
DEBUG [2016-10-13 09:34:34.00]: [Transporter]: DBG-X: The error code is: 1627
ERROR [2016-10-13 09:34:34.11]: Transporter transfer failed.
WARN [2016-10-13 09:34:34.11]:
ERROR [2016-10-13 09:34:34.11]: Your Apple ID account is attached to other iTunes providers. You will need to specify which provider you intend to submit content to by using the -itc_provider command. Please contact us if you have questions or need help. (1627)
ERROR [2016-10-13 09:34:34.18]: Your Apple ID account is attached to other iTunes providers. You will need to specify which provider you intend to submit content to by using the -itc_provider command. Please contact us if you have questions or need help. (1627)
Return status of iTunes Transporter was 1: Your Apple ID account is attached to other iTunes providers. You will need to specify which provider you intend to submit content to by using the -itc_provider command. Please contact us if you have questions or need help. (1627)
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
/Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/interface.rb:145:in `user_error!': [!] Error uploading ipa file, for more information see above (FastlaneCore::Interface::FastlaneError)
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/lib/pilot/build_manager.rb:22:in `upload'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/lib/pilot/commands_generator.rb:59:in `block (2 levels) in run'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/lib/pilot/commands_generator.rb:135:in `run'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/lib/pilot/commands_generator.rb:15:in `start'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/bin/pilot:6:in `<top (required)>'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/bin/pilot:23:in `load'
    from /Users/matthewcheetham/.rbenv/versions/2.3.0/bin/pilot:23:in `<main>'
Matthews-MBP:Local iOS matthewcheetham$

Configuration Files
N/A
Environment
fastlane 1.105.2
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
No
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
Yes. rbenv on this machine on 2.3.0

@MattCheetham Have you tried providing that parameter? It seems like this is the most viable workaround. We provide sane defaults but sometimes you need to manually set things. Thanks!

Is there any way for fastlane to detect this value automatically? Sorry, I don't have an account handy that requires this parameter

@TKBurner Providing that parameter and removing the --team_id one spits out the error
Multiple iTunes Connect teams found, please enter the number of the team you want to use:  Note: to automatically choose the team, provide either the iTunes Connect Team ID, or the Team Name in your fastlane/Appfile:
Proivding both --team_id and --itc_provider also still errors
ERROR [2016-10-18 08:27:09.65]: [Transporter Error Output]: Unable to find an iTunes Connect user for username email@domain.com and provider 351910. This username may not be enabled for iTunes Connect. Contact your team admin for assistance. (1296) DEBUG [2016-10-18 08:27:09.65]: [Transporter]: DBG-X: The error code is: 1296 ERROR [2016-10-18 08:27:09.75]: Transporter transfer failed. WARN [2016-10-18 08:27:09.75]:  ERROR [2016-10-18 08:27:09.75]: Unable to find an iTunes Connect user for username email@domain.com and provider 351910. This username may not be enabled for iTunes Connect. Contact your team admin for assistance. (1296) ERROR [2016-10-18 08:27:09.81]: Unable to find an iTunes Connect user for username email@domain.com and provider 351910. This username may not be enabled for iTunes Connect. Contact your team admin for assistance. (1296) Return status of iTunes Transporter was 1: Unable to find an iTunes Connect user for username email@domain.com and provider 351910. This username may not be enabled for iTunes Connect. Contact your team admin for assistance. (1296) The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure. /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/interface.rb:145:in user_error!': [!] Error uploading ipa file, for more information see above (FastlaneCore::Interface::FastlaneError)
from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/ui.rb:14:in method_missing' 	from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/lib/pilot/build_manager.rb:22:in upload'
from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/lib/pilot/commands_generator.rb:59:in block (2 levels) in run' 	from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:178:in call'
from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:153:in run' 	from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in run_active_command'
from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/fastlane_runner.rb:36:in run!' 	from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in run!'
from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/lib/pilot/commands_generator.rb:135:in run' 	from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/lib/pilot/commands_generator.rb:15:in start'
from /Users/matthewcheetham/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/pilot-1.10.1/bin/pilot:6:in <top (required)>' 	from /Users/matthewcheetham/.rbenv/versions/2.3.0/bin/pilot:23:in load'
from /Users/matthewcheetham/.rbenv/versions/2.3.0/bin/pilot:23:in <main>' Matthews-MBP:Local iOS matthewcheetham$
@KrauseFx Sorry I don't have any idea how you can go about this automatically. It seems even providing the right info doesn't work although I'm still not sure why.

@MattCheetham Does this account have an admin role on iTC?

@TKBurner We have the "App Manager" role on that account

@MattCheetham Can you try with an account with admin privileges and let me know if that clears things up for you? Because of certain API permissions beyond our control you might need to be in this role. Thanks!

@TKBurner Hmm I'll give it a try. Curious as to why that would affect one specific app on the account where all the other submit fine with the same account permission setup.
It's a client's account so will need to get them to bump us to admin and then I'll get back to you.

@MattCheetham Interesting. That shouldn't be the case, but maybe something is weird here. Let me know what happens with the change. Thanks!

@TKBurner Okay so I didn't get around to elevating access on that account but the issue has popped up again on a new app that we've just set up under another account (That is also a linked account like the original issue). I've verified that I can upload fine through Xcode and we are an Admin on this account.
So we're actually building this new one through Bitrise and submitting using the deliver step. I'm at a bit of a loss of how to fix this as the error just says to provide --itc_provider to iTMSTransporter which I obviously can't do.

Okay so the command that Bitrise runs is deliver --username username@domain.com --app 1180912547 --team_name '3 SIDED CUBE DESIGN LTD' --ipa '/Users/matthewcheetham/Downloads/Ready for Business.ipa' --skip_screenshots --skip_metadata --force which fails
I ran it locally and also get the failure.
However adding the --itc_provider key does fix the issue and the upload succeeds. So it does look like it's something to do with the --team_name or --team_id identifying correctly. Unfortunately, I have no way to pass --itc_provider in Bitrise but I'll link them to this issue as they have been following too and maybe it is something that they can provide functionality for.
The command that succeeds is deliver --username username@domain.com --app 1180912547 --team_name '3 SIDED CUBE DESIGN LTD' --ipa '/Users/matthewcheetham/Downloads/Ready for Business.ipa' --skip_screenshots --skip_metadata --force --itc_provider "3SIDEDCUBEDESIGNLTD"

Have the same issue with such code:
    pilot(
      ipa: ipa,
      skip_waiting_for_build_processing: true,
      team_id: itc_team_id,
      username: apple_username,
    )

for some teams (not all).
Adding itc_provider: itc_provider helped.
itc_provider i've take from (second column)
/Applications/Xcode-8.2.1.app/Contents/Applications/Application\ Loader.app/Contents/itms/bin/iTMSTransporter -m provider -u 'USER' -p "PASSWORD" -account_type itunes_connect -v off

itc_provider is sometimes (not always) the same team_id from Developer Portal.
Hope it helps.

authors: KrauseFx MattCheetham TKBurner yakimant


text:
Hidden error while failing to decode provisioning profile

New Issue Checklist

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

Issue Description
I probably have broken my keychain setup because some tests are failing by default when running the standard rspec.
In particular I found out that security cms -D -i  ./match/spec/fixtures/test.mobileprovision fails:
security: cert import failed: The specified keychain could not be found.
security: problem decoding

This fails the following code:
      def parse(path)
        require 'plist'

        plist = Plist.parse_xml(`security cms -D -i "#{path}" 2> /dev/null`) # /dev/null: https://github.com/fastlane/fastlane/issues/6387
        if (plist || []).count > 5
          plist
        else
          UI.error!("Error parsing provisioning profile at path '#{path}'")
          nil
        end

And the error message is maybe not 100% accurate / complete.
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

N/A
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
N/A

Test issue has been resolved now 👍

It has been reported that setting the login keychain to be the default should allow the command to be run:
security cms -D -i /Users/lyndsey.ferguson/Desktop/embedded.mobileprovision
Thanks @lyndsey-ferguson !!

authors: KrauseFx lacostej taquitos


text:
Initializing with declared lazy var causes error

New Issue Checklist

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

Issue Description
07:40:43 .../workspace/.../CollectionViewController.swift:143:235:
    extra argument 'timestamp' in call
07:40:43 ...forStruct: MyStruct(startDate: startDate.addingTimeInterval(-4 * 30 * 24 * 3600),
    endDate: endDate.addingTimeInterval(4 * 30 * 24 * 3600), timestamp: nil))

The same scheme with the same target can be compiled in Xcode directly without any error.
Example
I've build a little example showing how MyStruct in the log above is implemented. In Xcode there is no upcoming error with the code we're using.
struct MyStruct {
    var startDate, endDate: Date
    lazy var timestamp = Date()
}

let anInstance = MyStruct(startDate: Date(), endDate: Date(), timestamp: Date())

Xcode suggests us to use the initializer with all three parameters.

But fastlane asks us for let anFastlaneInstance = MyStruct(startDate: Date(), endDate: Date()) but Xcode is throwing an error then, that timestamp is Missing.
Workaround
We've worked around this error/issue by changing the impekentation of our struct to something like this.
struct MyStruct {
    var startDate, endDate: Date
    var timestamp: Date

    init(startDate: Date, endDate: Date, timestamp: Date = Date()) {
        self.startDate = startDate
        self.endDate = endDate
        self.timestamp = timestamp
    }
}

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.2.4

Bundler?
false

Git
git version 2.10.1 (Apple Git-78)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

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

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.13.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

i18n
0.7.0

json
1.8.1

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.4.3

activesupport
4.2.7.1

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.11.0

unf_ext
0.0.7.2

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
0.11.0.1

generated on: 2017-02-02

Added current environment

fastlane is just running xcodebuild under the hood. Have you tried taking the command line argument that is being sent to xcodebuild and calling it directly from the Terminal?

@lyndsey-ferguson yes we tried this, it is working by command-line, too.

Can you include the output from fastlane?

@lyndsey-ferguson I'm sorry but the snippet above is all i can publish from our log. Hoped it's enough to reproduce the error anywhere :(

Unfortunately, it is not enough as it just points out the error. If I were to investigate it, I would look at the output from fastlane to learn:

which action is being run, gym, xcodebuild
what are the environment variables
what is the exact xcodebuild command that is being executed from fastlane.
what other errors or warnings are being emitted --> that would provide some clues

Maybe the above is enough for you to figure it out without providing more info here. Like clues or things to think about.

I've installed xcode and fastlane fresh and clean again and it works now with my demo project, containing the code snippet above.

@DBocksteger awesome!! glad it works now, i am going to close the issue then, feel free to reopen or file a new issue whenever needed.

authors: DBocksteger hjanuschka lyndsey-ferguson


text:
[notarize] Add parameter to select if compressed package should be removed

Checklist

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

Motivation and Context
Was not able to distribute my zipped up app after notarization, as notarize removes the zip file it generates, which is being notarized as well.
Description
The problem is that notarize creates a zip file that is sent to the notarization service. The zip file is then also notarized.
{
  "logFormatVersion": 1,
  "jobId": "48e1bb69-e2aa-47ec-8c82-adc340aaa88a",
  "status": "Accepted",
  "statusSummary": "Ready for distribution",
  "statusCode": 0,
  "archiveFilename": "AppName.app.zip",
  "uploadDate": "2020-04-30T18:23:09Z",
  "sha256": "1d88ea6a1af6ad82fa7c23b49e81da4cfaaace1637a2df26819f9b91158b6d68",

Then, notarize removes the zip file. If a new zip file is then created to distribute the app, it fails notarization (at least on macOS 10.15.4)
This PR provides a new configuration parameter that can be used to prevent the zip file from being removed. This notarized zip file can then be used for distribution.
I tried setting the flag to true and to false, and it behaves as expected.
Also, I set the default to "true" so notarize will continue to work the same way unless the parameter is set to false.
Regarding documentation, I documented the parameter in the code by adding it to the available options. Not sure what other documentation might be required for this small change.
Testing Steps

Set the parameter remove_compressed_package to false
Run notarize
Verify that the generated zip file is not removed.

@googlebot I signed it!


text:
Update excon dependency

See https://github.com/fastlane/fastlane/issues/6367 for details.
Thanks for contributing to fastlane! Before you submit your pull request, please make sure to check the following boxes:

[ ] Run rspec for all tools you modified
[ ] Run rubocop -a to ensure the code style is valid
[ ] We currently don't accept new actions, please publish a plugin instead, more information in Plugins.md

Before submitting a pull request, we appreciate if you create an issue first to discuss the change :+1:

CI passed, but test failed locally:
===================
| Testing Summary |
===================

Finished in 60.194 seconds
3165 examples, 1 failure(s)

================================================
| 2 repo(s) with test failures: gym, spaceship |
================================================

1) Gym Gym::PackageCommandGeneratorLegacy supports passing a path to a provisioning profile
Failure/Error: expect(FastlaneCore::ProvisioningProfile).to receive(:install).with("./spec/fixtures/dummy.mobileprovision")
(<FastlaneCore::ProvisioningProfile (class)>).install("./spec/fixtures/dummy.mobileprovision")
    expected: 1 time with arguments: ("./spec/fixtures/dummy.mobileprovision")
    received: 0 times# gym/spec/package_command_generator_legacy_spec.rb:60:in `block (3 levels) in <top (required)>'

Failed examples:
gym/spec/package_command_generator_legacy_spec.rb:58 # Gym Gym::PackageCommandGeneratorLegacy supports passing a path to a provisioning profile

================
| Exceptions 💣 |
================

gym: Command failed with status (1): [bundle exec rspec --format documentation -...]
spaceship: Command failed with status (7): [bundle exec rspec --format documentation -...]
rake aborted!
All tests did not complete successfully. Search for '[[FAILURE]]' in the build logs.
/Users/lijie/source/fastlane/fastlane/rakelib/test_all.rake:170:in `block in <top (required)>'
/Users/lijie/.rvm/gems/ruby-2.3.1/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
/Users/lijie/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval'
/Users/lijie/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => test_all
(See full trace by running task with --trace)

I can't solve it, it happened in official master branch code on my machine.

This shouldn't be related to your change, thanks for running the tests though 👍

Thanks for the PR 👍

authors: KrauseFx cpunion


text:
Add the option to export simulator device logs

Checklist

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

Description
This adds support for the snapshot action to output simulator device logs.
Motivation
Sometimes it is helpful if there are problems with the screenshots to debug what went wrong in the application. Copying the system logs for the simulated device will provide the logging that the application outputs and can help narrow down such problems.
Testing

I created a unit test
I created a Fastfile in the example folder with a lane :snappy and ran it locally. The screenshots and the log files were created.

This is not yet ready

@hjanuschka can you take a look, and if all is good, merge this change?

@hjanuschka comments addressed. Ready to go! 🚀

many thx for this PR!

I would suggest xcrun simctl spawn booted log collect. The output will be written to $(xcrun simctl getenv booted SIMULATOR_SHARED_RESOURCES_DIR)/system_logs.logarchive
As more and more things move to os_log the old text log file may become less useful. Some debugging information is already stored in an in-memory ring buffer.

@russbishop that sounds awesome, i am ready to go for it.
just to make sure i got it:

launch snapshot, doe tests on simulator
collect screenshots
run xcrun simctl spawn booted log collect
get log folder via xcrun simctl getenv booted SIMULATOR_SHARED_RESOURCES_DIR
copy over path/system_logs.logarchive

does this include the "normal" NSLog, or do we need to fetch the system.log too to get them?
would love to hear back on this.

@russbishop  carried on in https://github.com/fastlane/fastlane/pull/8033 maybe you can have a look at the code.

@hjanuschka Yes, that's correct. The new system captures Syslog, Apple System Logger, and the new os_log messages all in one place. I would expect everything to switch to the new logging system over time.
I updated the env var; I should have spelled the word "directory" out fully.

authors: hjanuschka lyndsey-ferguson russbishop


text:
wokers复制过去搭建的

页面提示Authorization header is missing
是我哪里理解错误了么

这个部署之后，你请求的时候还是需要头里带 key 的
Ben @.***>于2024年4月25日 周四09:59写道：

页面提示Authorization header is missing
是我哪里理解错误了么
—
Reply to this email directly, view it on GitHub
https://github.com/fatwang2/search2ai/issues/18, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A77NZSUOL2MLUOD4WUCWWH3Y7BPQFAVCNFSM6AAAAABGX6YZ3CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3DENBYGUYDANI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

纯小白，请求头带key是什么意思，worker里复制粘贴后的代码，有一个地方需要改么？能截图或者示意说明一下

不改也行，直接用也可以
whutxd @.***>于2024年7月25日 周四下午6:09写道：

纯小白，请求头带key是什么意思，worker里复制粘贴后的代码，有一个地方需要改么？能截图或者示意说明一下
—
Reply to this email directly, view it on GitHub
https://github.com/fatwang2/search2ai/issues/18#issuecomment-2249965648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2QBNFPD7QAPEAJ7PVZCQ3ZODFENAVCNFSM6AAAAABGX6YZ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZHE3DKNRUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


text:
New gencode schema index page with categorisation

Example - https://noursaidi.github.io/udmi/gencode/docs/
This change intends to make the schema browser easier to use now that there are a lot more defined schemas.
Changes:

Schema is now automatically generated for any page which is a "root" schema (not referenced by another schema file) or deliberately excluded (event.json). This prevents pages being created for state_pointset etc.
Use MD file rather than HTML file
Use categorisation. If a schema is given a category in etc/schema_categories.txt then it'll be placed unread that category , otherwise it's lodged into the Other category
Add description of schema to the page

Don't specifically care if it's gencode_schemas or gencode_rockets :-) --
just as long as it's prefaced with gencode_ then all good. The other
refactor is fine too... not particular about it as long as there's some
kind of structure/hierarchy in place.
On Wed, Aug 31, 2022 at 12:15 PM Noureddine @.***>
wrote:

@.**** commented on this pull request.
In bin/list_root_schemas
https://github.com/faucetsdn/udmi/pull/436#discussion_r959940628:

@@ -0,0 +1,92 @@
+#!/usr/bin/env python3

Could add it into a script called gencode_doc_utils along with other
gendoc related scripts to reduce the number of those? I don't think
gencode_schemas is a good name for this particular script.
Incidentally .. I was planning to split the HTML documentation generation
out of gendocs and calling that gencode_schemas because gencode_docs
itself is getting messy to work with
—
Reply to this email directly, view it on GitHub
https://github.com/faucetsdn/udmi/pull/436#discussion_r959940628, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIEPD7BBANAIRMFBRA3H43V36VNFANCNFSM6AAAAAAQBMAIUA
.
You are receiving this because your review was requested.Message ID:
@.***>

@grafnu file renamed and documentation updated, PTAL

authors: grafnu noursaidi

repo: faucetsdn/udmi


text:
EventEmitter doesn't remove listeners

Not sure why this is. The test in getters and setters should watch i2c and should initialize and watch i2c both have been made to pass by using toBeGreaterThan rather than toBe.
I have also posted the question to StackOverflow, but so far no luck in fixing it. http://stackoverflow.com/posts/32455306/revisions

Not sure what was going on here, unfortunately I never resolved it, but I removed the eventEmitter and now watch and removeWatch works.

repo: favor/it


text:
Figure out if sunlight scattered of Jupiter onto Io matters

How would we model this in Starry, second light source in addition to the Sun? Is it time variable?

From this paper:

During the photometry of mutual events, one must take
care with the possibility of a parasitic flux, as pointed out
by Emel’yanov (2017) and Arlot et al. (2017). The origin
of this flux is likely to be the background (mostly Jupiter’s
scattered light) or the CCD detector. In our case, we attenuate this parasitic flux with the Methane filter and a rigorous
calibration process. Tests showed that the parasitic flux in
our images is one order of magnitude below the noise of our
observations.

Not sure about IRTF observations of Io in sunlight.

repo: fbartolic/volcano


text:
Bayesian optimization of weight initialization

I think with my current dataset models can converge to a lot of silly solutions so I was thinking one way of finding deeper minima could be train a bunch of models in parallel and iteratively adjust the random weight initialization by Bayesian optimization as a function of validation loss, and restart training. Has anyone attempted something like this before with Keras and perhaps could share an example? Is it worthwhile?

@fchollet mentions in #896 that he's done this hyperparameter optimization in Keras using hyperopt http://hyperopt.github.io/hyperopt/ and there's some example code posted here https://github.com/fchollet/keras/issues/1591#issuecomment-177062588 while others have suggested doing this with https://github.com/HIPS/Spearmint including this issue #2266
I don't know how common it is to optimize the weight initialization scheme vs other hyperparameters, if you check the example code above you can see @jacobzweig is sticking with (what is now the default) "glorot_uniform" init.

Nice! Thanks for the links, @kylemcdonald.
Actually, after thinking about it I figure training over several epochs is a much simpler way of optimizing the initial weights and that it probably wouldn't be worth the effort to do any more since in high-dimensional spaces getting stuck in local minima is improbable. http://www.kdnuggets.com/2015/11/theoretical-deep-learning.html
For other hyperparameters it seems very promising though. Again, thanks for the help!

This package is also a good point to start: Hyperopt + Keras = hyperas.

@tboquet thanks! :smile:

authors: carlthome kylemcdonald tboquet

repo: fchollet/keras


text:
Comment mistake in merge function

It's not a big problem, but some might have problems whether the 'join' merge mode is available or not.
https://github.com/fchollet/keras/blob/master/keras/engine/topology.py#L1403
In line 1403,
If I'm right, you should remove 'join' since it's no longer supported.

I removed it.

authors: fchollet hongkunyoo


text:
Switch tasks to pytest

@fchollet , @phreeza please take a look.  While github diff looks terrible, I didn't do much, just few renames and fixes. Here I just want to throw few ideas in to avoid spending time in the future.
Small cleanup of test_tasks:

switch to pytest
fix random seed to be independent on the order of imports
readable test names
remove unnecessary prints

Experimental:

switch some tests to use list of layers in constructor. I was always wandering why torch do not do that - just pass a list of layers into Sequential. I was pleasantly surprised to find this in Keras.

switch some tests to use list of layers in constructor.

Could you clarify what you mean?
I think these are reasonable changes. Regarding prints, we should keep prints that make the test logs easier to read, specifically prints such as "now testing this and that...".
Also: any assert should have a readable failure message associated to it. If a test fails because some value was too high or something, we want to know what the value was (and what it was being compared to).

@fchollet, this is exactly what you get with pytest - I renamed functions to be the same as prints so you get the same as you had. Also pytest will generate you a nice assert message if it fails

Ok, sounds good.

authors: fchollet olegsinyavskiy


text:
Fix ValueError(ndim of gamma and beta) of batch normalization when using Theano

I am using the latest version of theano and keras, and ValueError same as #3667 occurs when using batch normalization. The error is caused by theano's batch normalization methods, which require the exactly same ndim as input. So, in all cases gamma and beta must be reshaped when using theano.

This sounds like more of a Theano bug, and it was definitely not the case in earlier versions of Theano. Shouldn't Theano be able to automatically do the broadcast?

@fchollet In earlier versions, batch norm implementation of Theano is called instead of that of cuDNN. See theano_backend.py#419. theano.sandbox.cuda.dnn.dnn_batch_normalization_test is in the latest version, and the error occurs in that method. While dnn_batch_normalization_test strictly checks the dimensionality of parameters, T.nnet.bn.batch_normalization doesn't. (ps. I think T.nnet.bn.batch_normalization is more buggy because it doesn't check parameters and users mistake.)
The purpose of if statement in normalization.py#143 is to automatically broadcast the last depth dimension. However, we cannot be sure the last dimension is always depth in Theano. So, it's not a common case in Theano compared to Tensorflow (See tensorflow's batch norm). In my opinion, it's more general to always broadcast all dimensions before batch normalization.

I wanted to +1 this. It fixes Issue #3667 for me.

LGTM

authors: alexmarkley fchollet woozzu


text:
jwt ssl warning

Fire a warning if the request is insecure rather than refusing to send the cookie.
Allow override a single cookie property

Please have a look https://github.com/feathersjs/feathers-authentication/compare/master...aboutlo:ls-JWT-ssl-warning?diff=unified&expand=1&name=ls-JWT-ssl-warning#diff-1fdf421c05c1140f6d71444ea2b27638L60
In my opinion app.get('auth') is always undefined at this stage.

@aboutlo this is awesome! Nice work! I think we do need app.get('auth') from what I explained above. I probably need to add a test for that. If you can add that back in this is good to go! 🍻

Thank you @ekryski for the kind words. I added back app.get('auth'). Tests are still green :)

Oh sorry, this was totally good to go to. I'll merge it in, it'll make it into the next release.

Yup :shipit:

cool

Released v0.7.9 with this fix in! 🍻 @aboutlo!

authors: aboutlo daffl ekryski

repo: feathersjs/feathers-authentication


text:
Attempt to get token right away.

This makes it so that we don’t have to wait for an async response in order to start making authenticated requests.

@ekryski Any idea how to setup the token on socket.io?  This isn't doing the trick for some reason.

👍  :shipit: no need to worry about tests right now. I'll have to fix/re-write a bunch

authors: ekryski marshallswain


text:
URIs may have empty paths

I stand corrected.

Just curious, where did this cause an problem?

One of the Nodes returned something like https://example.com in a place where the spec says it has to be a valid URI.

authors: jernst steve-bate

repo: fediverse-devnet/feditest


text:
how to get user rating and comments from itc?

@fedoco I had saw the itc-reporter,it is very useful,but I also need to get users rating and comments in itunes connect,how can I solve it ? Can you help me?

Ratings are not available via official API - you would need to scrape them. https://github.com/grych/AppStoreReviews is an example of how to do that.

@fedoco It is too older,so it did not work now.Were there other ways to slove my issue?

I'm sorry, I cannot help you here. My script has nothing to do with user ratings. Why don't you ask the author of the script I mentioned instead?

authors: diaojunxian fedoco

repo: fedoco/itc-reporter


text:
Make method coders be able to show breadcrumbs dynamically

We need in multiple places to show the breadcrumb of a method (package>class), such as the expanded methods or the preview of the implementation of a view.
This:
(GtMethodCoder forMethod: Object>>#printOn:)
	coderLook: GtSourceCoderHeaderLook + GtMethodCoderCategoryLook;
	asElement

does not work because we cannot install the look in multiple elements.
Instead we need to be able to pass a block.

This can be rewritten as
(GtMethodCoder forMethod: Object>>#printOn:)
	coderLook: [ GtSourceCoderHeaderLook + GtMethodCoderCategoryLook ];
	asElement

We should added it to the expanded method (expander add-on)

We would need it here:

authors: girba syrel

repo: feenkcom/gtoolkit


text:
[Debugger]: Created Method after DNU should have better default protocol

When a method is created in the debugger after a DNU, the default protocol is the infrequently-used "reflective operations". I guess the most common default would be accessing, unless we have some more sophisticated algorithm. First reported on Discord.

The real bug is that the debugger shows the wrong classification for that stack frame. The method is actually compiled into as yet unclassified. If you then change the method in the debugger, though, it will get reclassified as reflective operations which was the original category of the DNU.

Let’s call it two bugs lol

authors: refactoringdr seandenigris


text:
Inspecting an AST node with a breakpoint freezes the image

Same as https://github.com/feenkcom/gtoolkit/issues/3994

authors: chisandrei girba


text:
Correct systemd network setup

In testing the OS on an older machine I've found that the simple network solution is too simple. As we're targeting learners and hobbyists ultimately, we can replace the single file with two: one for the first Ethernet card found, and one for the first Wifi card found.

We can also simplify the entire situation further: according to https://wiki.archlinux.org/title/Systemd-networkd the match section accepts types as an alternative to assuming names. This also gives us the option to remove net.ifnames from the kernel command line and put it in the bootloader entry instead.

repo: feli-flitzberg/FerretOS


text:
Well... No Geometry?

I am finding some libraries about computational geometry, especially Bezier-curve related.
Including these algorithms will be helpful.

Feel free to send pull-requests, I'll be happy to review and merge them


text:
[Feature Request] Option to only show installed games during search

I have found that it can be difficult to find some games to play because it mixes games that are uninstalled in the list so this should help. Personally I think only installed games should be in the search by default because you are not installing games constantly but not sure.
For example, typing Dark Souls gives me an uninstalled and unplayable game

I mean its kind of the point of this to find everything there is, so I would not want to filter out not installed games completely. I'm thinking I could add an option to reorder game results such that it pushes one or more (max number set by the user) installed games in front of the first not installed game. This would always give you a playable game as the first result if available, but still keep highly matching uninstalled games easily accessible.

Yeah anything that helps see installed games first is appreciated.

For the time being I added a new option to sort by installation status before the name if scores are equal in version 1.2.

authors: darklinkpower felixkmh

repo: felixkmh/QuickSearch-for-Playnite


text:
High Severity Vulnerabilty

Installing this package via npm resulted in a high severity vulnerability. Result of npm audit are as follows:
                       === npm audit security report ===

                                 Manual Review
             Some vulnerabilities require your attention to resolve

          Visit https://go.npm.me/audit-guide for additional guidance

  High            Arbitrary File Write

  Package         decompress

  Patched in      No patch available

  Dependency of   download

  Path            download > decompress

  More info       https://npmjs.com/advisories/1217

My bad. The report was not for this package.

repo: felixrieseberg/electron-windows-store


text:
Add a replacement shared_task decorator.

Celery provides the shared_task decorator so that programmers can create application-agnostic (i.e. reusable) tasks.  It seems like django-celery-transactions should patch this decorator in addition to celery.task, so I am providing a trivial patch to make it so.

Thanks @zbmott! I'll make sure to test it and release it within 24h

authors: fellowshipofone zbmott


text:
i18n to pt-BR

PR Checklist
Please check if your PR fulfills the following requirements:

[X] The commit message follows our guidelines.
[X] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build related changes
[ ] Documentation content changes
[X] Other, Please describe: i18n to `pt-BR`

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[X] No

Other information

Codecov Report

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

@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   80.44%   80.44%
=======================================
  Files           8        8
  Lines         680      680
=======================================
  Hits          547      547
  Misses        133      133

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0348a2f...ae2b8d4. Read the comment docs.

authors: codecov-io robsonoduarte

repo: fengyuanchen/pickerjs


text:
test: unit tests for the 'load' Function

Summary

unit tests for the load function within the Image package. The main goal is to ensure the function behaves as expected when provided with different types of ImageSource inputs.
Checks

Please check the following:

[x] I have written documents and tests, if needed.

How about removing test folder
I think simply making load.ts be close with load.test.ts is easy to maintain our library.

How about removing __test__ folder I think simply making load.ts be close with load.test.ts is easy to maintain our library.

@manudeli cool. i got this #34

If spec of load, I think load.spec.ts is better naming

How about this

If spec of load, I think load.spec.ts is better naming

How about this

I've given it some thought, and I agree with you. @manudeli
Since the test cases are focused on the behavior of specific functionalities (e.g., "should load defaultSrc when webpSrc is not provided"), spec seems more appropriate. I'll make the changes. Thanks for the review. 768118c

test(image): add load test case
How about this Pull Request title
This title will be commit message when merging this Pull Request. I want to care simple, easy to read, monorepo's scope

repo: fepack/image


text:
🛑 Support is down

In 911fb60, Support (https://support.jegtheme.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Support is back up in a3addcc after 19 minutes.

repo: ferdysopian/jegmontol