Produce fails to create a new app id

New Issue Checklist

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

Issue Description
produce fails to create a new app id.
Complete output when running fastlane, including the stack trace and command used
(Dropbox/otherscripts) % produce create --app_identifier com.lyft.ios.enterprise.debug.siri.ui -u<EMAIL_ADDRESS>--team_id seckret --app_name "the name" --skip_itc true --skip_devcenter false

+----------------+---------------------------------------+
|               Summary for produce 1.2.0                |
+----------------+---------------------------------------+
| app_identifier | com.lyft.ios.enterprise.debug.siri.ui |
| username       |<EMAIL_ADDRESS>                      |
| team_id        | seckret                            |
| app_name       | Development Siri UI                   |
| skip_itc       | true                                  |
| skip_devcenter | false                                 |
| sku            |<PHONE_NUMBER>                            |
| language       | English                               |
+----------------+---------------------------------------+

[13:41:43]: Creating new app 'the name' on the Apple Dev Center

Looking for related GitHub issues on fastlane/fastlane...

➡  crash on ad_hoc provisioning profile delete
   https://github.com/fastlane/fastlane/issues/3427 [closed] 1 💬
   08 Mar 2016

➡  crash on ad_hoc provisioning profile delete!
   https://github.com/fastlane/fastlane/issues/3485 [closed] 0 💬
   08 Mar 2016

/Users/ksmiley/.rubies/ruby-2.3.1/lib/ruby/2.3.0/json/common.rb:156:in `parse': [!] 784: unexpected token at 'Bad Request' (Faraday::ParsingError)
        from /Users/ksmiley/.rubies/ruby-2.3.1/lib/ruby/2.3.0/json/common.rb:156:in `parse'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in `block in <class:ParseJson>'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `parse'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in `process_response'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in `block in call'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday-0.9.2/lib/faraday/response.rb:57:in `on_complete'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in `call'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in `build_response'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in `run_request'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in `post'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/spaceship-0.31.2/lib/spaceship/client.rb:411:in `block in send_request'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/spaceship-0.31.2/lib/spaceship/client.rb:328:in `with_retry'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/spaceship-0.31.2/lib/spaceship/client.rb:410:in `send_request'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/spaceship-0.31.2/lib/spaceship/client.rb:385:in `request'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/spaceship-0.31.2/lib/spaceship/portal/portal_client.rb:177:in `create_app!'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/spaceship-0.31.2/lib/spaceship/portal/app.rb:97:in `create!'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/produce-1.2.0/lib/produce/developer_center.rb:22:in `create_new_app'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/produce-1.2.0/lib/produce/developer_center.rb:8:in `run'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/produce-1.2.0/lib/produce/manager.rb:7:in `start_producing'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/produce-1.2.0/lib/produce/commands_generator.rb:37:in `block (2 levels) in run'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/fastlane_core-0.50.2/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/produce-1.2.0/lib/produce/commands_generator.rb:127:in `run'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/produce-1.2.0/lib/produce/commands_generator.rb:11:in `start'
        from /Users/ksmiley/.gem/ruby/2.3.1/gems/produce-1.2.0/bin/produce:6:in `<top (required)>'
        from /Users/ksmiley/.gem/ruby/2.3.1/bin/produce:23:in `load'
        from /Users/ksmiley/.gem/ruby/2.3.1/bin/produce:23:in `<main>'

Environment
% produce -v
produce 1.2.0

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)? No/chruby

This is quite a few steps before the code signing step @fastlane-bot :P

+1
Same problem here

+1

Thanks for the report everyone, I can reproduce and work on a fix right now

Pull request is ready, we'll push a new release in a few minutes https://github.com/fastlane/fastlane/pull/5803 🚀

You're awesome.
--
Keith Smiley

On Aug 18, 2016, at 17:17, Felix Krause<EMAIL_ADDRESS>wrote:
Pull request is ready, we'll push a new release in a few minutes #5803 🚀
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The new release is live, please update using [sudo] gem update spaceship or if you're using bundler, use bundle update 🚀
Please let us know if that solves the problem for you 👍

😢 I updated to the latest spaceship and I am still getting the same error.

@sungolo can you share the complete output and stack trace?

`
+----------------+------------------------------+
|           Summary for produce 1.2.0           |
+----------------+------------------------------+
| username       | xxxxxxxxxx                   |
| app_identifier | com.olo.testoloautomation    |
| app_name       | TestOloAutomation - Ordering |
| app_version    | 1.0                          |
| sku            | testoloautomation            |
| language       | English                      |
| skip_itc       | false                        |
| skip_devcenter | false                        |
| team_id        | xxxxxxxxxx                   |
| team_name      | xxxxxxxxxx                   |
+----------------+------------------------------+
[21:44:31]: Creating new app 'TestOloAutomation  Ordering' on the Apple Dev Center
[21:44:31]: Variable Dump:
[21:44:31]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios start", :CERT_FILE_PATH=>"xxxxxxxxxx", :CERT_CERTIFICATE_ID=>"xxxxxxxxxx"}
[21:44:31]: 757: unexpected token at 'Bad Request'
+------+-------------------------------+-------------+
|                  fastlane summary                  |
+------+-------------------------------+-------------+
| Step | Action                        | Time (in s) |
+------+-------------------------------+-------------+
| 1    | default_platform              | 0           |
| 2    | Switch to ios createcert lane | 0           |
| 3    | cert                          | 4           |
| 4    | Switch to ios createapp lane  | 0           |
| 5    | produce                       | 2           |
+------+-------------------------------+-------------+
[21:44:31]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
➡  Bad Request - portal_client.rb - associate_groups_with_app
https://github.com/fastlane/fastlane/issues/2049 [open] 0 💬
07 Mar 2016
➡  Produce not creating new applications anymore
https://github.com/fastlane/fastlane/issues/5799 [open] 5 💬
an hour ago
➡  757: unexpected token at 'HTTP 400 Bad Request'
https://github.com/fastlane/fastlane/issues/2947 [closed] 4 💬
08 Mar 2016
and 18 more at: https://github.com/fastlane/fastlane/search?q=757: unexpected token at 'Bad Request'&type=Issues&utf8=✓
/Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in parse': [!] 757: unexpected token at 'Bad Request' (Faraday::ParsingError) 	from /Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in parse'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in block in <class:ParseJson>' 	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in call'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in parse' 	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in process_response'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in block in call' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/response.rb:57:in on_complete'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in call' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in build_response'
from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in run_request' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in post'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:411:in block in send_request' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:328:in with_retry'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:410:in send_request' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:385:in request'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/portal/portal_client.rb:175:in create_app!' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/portal/app.rb:97:in create!'
from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/developer_center.rb:22:in create_new_app' 	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/developer_center.rb:8:in run'
from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/manager.rb:7:in start_producing' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:19:in block in run'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:17:in chdir' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:17:in run'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:190:in block (2 levels) in execute_action' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/actions/actions_helper.rb:35:in execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:175:in block in execute_action' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in chdir'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in execute_action' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:100:in trigger_action_by_name'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/fast_file.rb:140:in method_missing' 	from ../fastlane/Fastfile:48:in block (2 levels) in parsing_binding'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in call' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in call'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:153:in try_switch_to_lane' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:108:in trigger_action_by_name'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/fast_file.rb:140:in method_missing' 	from ../fastlane/Fastfile:34:in block (2 levels) in parsing_binding'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in call' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in call'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:49:in block in execute' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in chdir'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in execute' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/lane_manager.rb:46:in cruise_lane'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/command_line_handler.rb:30:in handle' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:49:in block (2 levels) in run'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:178:in call' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:178:in call'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:153:in run' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in run_active_command'
from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.50.2/lib/fastlane_core/ui/fastlane_runner.rb:36:in run!' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in run!'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:246:in run' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:20:in start'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/cli_tools_distributor.rb:58:in take_off' 	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/bin/fastlane:5:in <top (required)>'
from /usr/local/bin/fastlane:23:in load' 	from /usr/local/bin/fastlane:23:in '`

Same here....
[19:38:23]: ---------------------
[19:38:23]: --- Step: produce ---
[19:38:23]: ---------------------

+----------------+-------------------+
|     Summary for produce 1.2.0      |
+----------------+-------------------+
| app_name       | farah.lucas.kodeo |
| language       | English           |
| app_version    | 1.0               |
| sku            | 123abc            |
| username       |<EMAIL_ADDRESS>|
| app_identifier | farah.lucas.Kodeo |
| skip_itc       | false             |
| skip_devcenter | false             |
| team_id        | NN3TD9EB8G        |
+----------------+-------------------+

[19:38:26]: Creating new app 'farahlucaskodeo' on the Apple Dev Center
[19:38:26]: Variable Dump:
[19:38:26]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios provision"}
[19:38:26]: 757: unexpected token at 'Bad Request'

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | cocoapods                           | 3           |
| 4    | produce                             | 3           |
+------+-------------------------------------+-------------+

[19:38:26]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...

➡  Bad Request - portal_client.rb - associate_groups_with_app
   https://github.com/fastlane/fastlane/issues/2049 [open] 0 💬
   07 Mar 2016

➡  Produce not creating new applications anymore
   https://github.com/fastlane/fastlane/issues/5799 [open] 5 💬
   2 hours ago

➡  757: unexpected token at 'HTTP 400 Bad Request'
   https://github.com/fastlane/fastlane/issues/2947 [closed] 4 💬
   08 Mar 2016

and 19 more at: https://github.com/fastlane/fastlane/search?q=757:%20unexpected%20token%20at%20'Bad%20Request'&type=Issues&utf8=✓
/Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/json-1.8.3/lib/json/common.rb:155:in `parse': [!] 757: unexpected token at 'Bad Request' (Faraday::ParsingError)
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/json-1.8.3/lib/json/common.rb:155:in `parse'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in `block in <class:ParseJson>'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `call'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `parse'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in `process_response'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in `block in call'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday-0.9.2/lib/faraday/response.rb:57:in `on_complete'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in `call'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in `build_response'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in `run_request'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in `post'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:411:in `block in send_request'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:328:in `with_retry'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:410:in `send_request'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:385:in `request'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/spaceship-0.31.3/lib/spaceship/portal/portal_client.rb:175:in `create_app!'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/spaceship-0.31.3/lib/spaceship/portal/app.rb:97:in `create!'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/produce-1.2.0/lib/produce/developer_center.rb:22:in `create_new_app'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/produce-1.2.0/lib/produce/developer_center.rb:8:in `run'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/produce-1.2.0/lib/produce/manager.rb:7:in `start_producing'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:19:in `block in run'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:17:in `chdir'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:17:in `run'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:190:in `block (2 levels) in execute_action'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:175:in `block in execute_action'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in `chdir'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in `execute_action'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:100:in `trigger_action_by_name'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/fast_file.rb:140:in `method_missing'
	from Fastfile:30:in `block (2 levels) in parsing_binding'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:49:in `block in execute'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in `execute'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/command_line_handler.rb:30:in `handle'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:49:in `block (2 levels) in run'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane_core-0.50.2/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:246:in `run'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:20:in `start'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/bin/fastlane:5:in `<top (required)>'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/bin/fastlane:23:in `load'
	from /Users/lucasfarah/.rbenv/versions/2.2.5/bin/fastlane:23:in `<main>'

the also.....
+---------------+--------------------------------------------------+
|                      Summary for cert 1.4.1                      |
+---------------+--------------------------------------------------+
| development   | false                                            |
| force         | false                                            |
| keychain_path | /Users/shenyuan/Library/Keychains/login.keychain |
+---------------+--------------------------------------------------+
[15:27:03]: To not be asked about this value, you can specify it using 'username'
Your Apple ID Username: xxxxx
[15:27:14]: Starting login with user 'xxxxx'
[15:27:23]: Successfully logged in
[15:27:26]: Couldn't find an existing certificate... creating a new one
Looking for related GitHub issues on fastlane/fastlane...
➡  Bad Request - portal_client.rb - associate_groups_with_app
https://github.com/fastlane/fastlane/issues/2049 [open] 0 💬
07 Mar 2016
➡  Produce not creating new applications anymore
https://github.com/fastlane/fastlane/issues/5799 [open] 6 💬
3 hours ago
➡  757: unexpected token at 'HTTP 400 Bad Request'
https://github.com/fastlane/fastlane/issues/2947 [closed] 4 💬
08 Mar 2016
and 19 more at: https://github.com/fastlane/fastlane/search?q=757: unexpected token at 'Bad Request'&type=Issues&utf8=✓
/Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in parse': [!] 757: unexpected token at 'Bad Request' (Faraday::ParsingError) 	from /Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in parse'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in block in <class:ParseJson>' 	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in call'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in parse' 	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in process_response'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in block in call' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/response.rb:57:in on_complete'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in call' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in build_response'
from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in run_request' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in post'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:411:in block in send_request' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:328:in with_retry'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:410:in send_request' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:385:in request'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/portal/portal_client.rb:282:in create_certificate!' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/portal/certificate.rb:298:in create!'
from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/lib/cert/runner.rb:137:in create_certificate' 	from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/lib/cert/runner.rb:37:in run'
from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/lib/cert/runner.rb:6:in launch' 	from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/bin/cert:33:in block (2 levels) in run'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in call' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in call'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in run' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in run_active_command'
from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.50.0/lib/fastlane_core/ui/fastlane_runner.rb:36:in run!' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in run!'
from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/bin/cert:49:in run' 	from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/bin/cert:55:in <top (required)>'
from /usr/local/bin/cert:22:in load' 	from /usr/local/bin/cert:22:in '

@KrauseFx   i update spaceship like this:
ShenYuandeMacBook-Pro:zhMe_fastlane shenyuan$ sudo gem update spaceship
Password:
Updating installed gems
Nothing to update
ShenYuandeMacBook-Pro:zhMe_fastlane shenyuan$
then  i try again  it's the same problem.
why???

[16:09:40]: -------------------------------------------------
[16:09:40]: --- Step: Verifying required fastlane version ---
[16:09:40]: -------------------------------------------------
[16:09:40]: fastlane version valid
[16:09:40]: ------------------------------
[16:09:40]: --- Step: default_platform ---
[16:09:40]: ------------------------------
[16:09:40]: Driving the lane 'ios create' 🚀
[16:09:40]: --------------------------------------------------------------------------------------------------------------------------------
[16:09:40]: --- Step: rm -f 'xxxx'; ---
[16:09:40]: --------------------------------------------------------------------------------------------------------------------------------
[16:09:40]: $ rm -f 'xxxx';
[16:09:40]: /xxxxx
[16:09:40]: ---------------------
[16:09:40]: --- Step: produce ---
[16:09:40]: ---------------------

+----------------+-----------------------+
|       Summary for produce 1.2.0        |
+----------------+-----------------------+
| username       | xxxx      |
| app_identifier | xxxxx |
| app_name       | xxxxxx                 |
| language       | Russian               |
| app_version    | 1.0                   |
| sku            | xxxxx |
| team_name      | xxxxxx          |
| skip_itc       | false                 |
| skip_devcenter | false                 |
| team_id        | xxxxxxx            |
+----------------+-----------------------+

[16:09:47]: Creating new app 'RU471' on the Apple Dev Center
[16:09:48]: Variable Dump:
[16:09:48]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios create"}
[16:09:48]: 757: unexpected token at 'Bad Request'

+------+---------------------------------------------------------------+-------------+
|                                  fastlane summary                                  |
+------+---------------------------------------------------------------+-------------+
| Step | Action                                                        | Time (in s) |
+------+---------------------------------------------------------------+-------------+
| 1    | Verifying required fastlane version                           | 0           |
| 2    | default_platform                                              | 0           |
| 3    | rm -f 'xxxxxxx | 0           |
| 4    | produce                                                       | 8           |
+------+---------------------------------------------------------------+-------------+

[16:09:49]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...

➡  Bad Request - portal_client.rb - associate_groups_with_app
   https://github.com/fastlane/fastlane/issues/2049 [open] 0 💬
   07 Mar 2016

➡  Produce not creating new applications anymore
   https://github.com/fastlane/fastlane/issues/5799 [open] 6 💬
   8 hours ago

➡  757: unexpected token at 'HTTP 400 Bad Request'
   https://github.com/fastlane/fastlane/issues/2947 [closed] 4 💬
   08 Mar 2016

and 19 more at: https://github.com/fastlane/fastlane/search?q=757:%20unexpected%20token%20at%20'Bad%20Request'&type=Issues&utf8=✓
/Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in `parse': [!] 757: unexpected token at 'Bad Request' (Faraday::ParsingError)
	from /Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in `parse'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in `block in <class:ParseJson>'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `parse'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in `process_response'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in `block in call'
	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/response.rb:57:in `on_complete'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in `build_response'
	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in `run_request'
	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in `post'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:411:in `block in send_request'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:328:in `with_retry'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:410:in `send_request'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:385:in `request'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/portal/portal_client.rb:175:in `create_app!'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/portal/app.rb:97:in `create!'
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/developer_center.rb:22:in `create_new_app'
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/developer_center.rb:8:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/manager.rb:7:in `start_producing'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:19:in `block in run'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:17:in `chdir'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/actions/produce.rb:17:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:190:in `block (2 levels) in execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:175:in `block in execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in `chdir'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in `execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:100:in `trigger_action_by_name'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/fast_file.rb:140:in `method_missing'
	from Fastfile:180:in `block (2 levels) in parsing_binding'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:49:in `block in execute'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in `chdir'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in `execute'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/command_line_handler.rb:30:in `handle'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:49:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.50.2/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:246:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:20:in `start'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.101.0/bin/fastlane:5:in `<top (required)>'
	from /usr/local/bin/fastlane:23:in `load'
	from /usr/local/bin/fastlane:23:in `<main>'

error, please help.

@GandjaFuzz gem update spaceship

It looks like this is still failing for some people using spaceship 0.31.3. We're looking into another fix and will update this thread when we know more!
If anyone is able to narrow down the cases (account type, number of teams, creating the app in iTC vs Dev portal,e tc) that produce errors (since 0.13.3 fixed a problem for a number of people) that would really help us get this fixed quickly! 👍

sh-3.2# gem update spaceship
Updating installed gems
Nothing to update

it is not update

also happening with cert
cert -u<EMAIL_ADDRESS>[10:54:50]: Successfully logged in
[10:54:51]: Couldn't find an existing certificate... creating a new one
Looking for related GitHub issues on fastlane/fastlane...
➡  Bad Request - portal_client.rb - associate_groups_with_app
https://github.com/fastlane/fastlane/issues/2049 [open] 0 💬
07 Mar 2016
➡  Produce not creating new applications anymore
https://github.com/fastlane/fastlane/issues/5799 [open] 6 💬
11 hours ago
➡  757: unexpected token at 'HTTP 400 Bad Request'
https://github.com/fastlane/fastlane/issues/2947 [closed] 4 💬
08 Mar 2016
and 19 more at: https://github.com/fastlane/fastlane/search?q=757: unexpected token at 'Bad Request'&type=Issues&utf8=✓
/Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in parse': [!] 757: unexpected token at 'Bad Request' (Faraday::ParsingError) 	from /Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in parse'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in block in <class:ParseJson>' 	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in call'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in parse' 	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in process_response'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in block in call' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/response.rb:57:in on_complete'
from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in call' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in build_response'
from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in run_request' 	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in post'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:411:in block in send_request' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:328:in with_retry'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:410:in send_request' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/client.rb:385:in request'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/portal/portal_client.rb:282:in create_certificate!' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.31.3/lib/spaceship/portal/certificate.rb:298:in create!'
from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/lib/cert/runner.rb:137:in create_certificate' 	from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/lib/cert/runner.rb:37:in run'
from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/lib/cert/runner.rb:6:in launch' 	from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/bin/cert:33:in block (2 levels) in run'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in call' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in call'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in run' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in run_active_command'
from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.50.0/lib/fastlane_core/ui/fastlane_runner.rb:36:in run!' 	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in run!'
from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/bin/cert:49:in run' 	from /Library/Ruby/Gems/2.0.0/gems/cert-1.4.1/bin/cert:55:in <top (required)>'
from /usr/local/bin/cert:22:in load' 	from /usr/local/bin/cert:22:in '

We have merged a fix for this and it will be available shortly in the next version of spaceship.

spaceship 0.31.4 has been released. Please run gem update spaceship and confirm the fix for us! 👍

If you're using bundler, use bundle update 🚀
Please let us know if that solves the problem for you 👍

Everything works now! :tada::tada::tada::balloon:
Thanks guys!

Same thing is happening with PEM.  Can you release a fix for that too please?

I'm seeing the same issue with PEM too.
(/Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/bin/fastlane)
Faraday::ParsingError: [!] 776: unexpected token at 'Bad Request'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/json-1.8.3/lib/json/common.rb:155:in `parse'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/json-1.8.3/lib/json/common.rb:155:in `parse'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in `block in <class:ParseJson>'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `parse'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in `process_response'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in `block in call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday-0.9.2/lib/faraday/response.rb:57:in `on_complete'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in `call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in `build_response'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in `run_request'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in `post'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/spaceship-0.31.6/lib/spaceship/client.rb:411:in `block in send_request'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/spaceship-0.31.6/lib/spaceship/client.rb:328:in `with_retry'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/spaceship-0.31.6/lib/spaceship/client.rb:410:in `send_request'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/spaceship-0.31.6/lib/spaceship/client.rb:385:in `request'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/spaceship-0.31.6/lib/spaceship/portal/portal_client.rb:287:in `create_certificate!'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/spaceship-0.31.6/lib/spaceship/portal/certificate.rb:298:in `create!'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/pem-1.3.2/lib/pem/manager.rb:47:in `create_certificate'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/pem-1.3.2/lib/pem/manager.rb:30:in `start'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/actions/pem.rb:19:in `run'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:190:in `block (2 levels) in execute_action'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:175:in `block in execute_action'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in `chdir'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in `execute_action'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:100:in `trigger_action_by_name'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/fast_file.rb:140:in `method_missing'
  Fastfile:62:in `block (2 levels) in parsing_binding'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:153:in `try_switch_to_lane'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:108:in `trigger_action_by_name'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/fast_file.rb:140:in `method_missing'
  Fastfile:32:in `block (2 levels) in parsing_binding'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:49:in `block in execute'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in `chdir'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in `execute'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/command_line_handler.rb:30:in `handle'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:49:in `block (2 levels) in run'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane_core-0.50.2/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:246:in `run'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:20:in `start'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/gems/fastlane-1.101.0/bin/fastlane:5:in `<top (required)>'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/bin/fastlane:23:in `load'
  /Users/travis/build/flipdish/ios/vendor/bundle/ruby/2.2.0/bin/fastlane:23:in `<top (required)>'

@CareerFairPlus We are working on a release for pem stay tuned!

+1

We're hitting this with sigh as well;
+-------------------------------------+----------------------+
|                   Summary for sigh 1.9.0                   |
+-------------------------------------+----------------------+
| username                            | xxxxxxx |
| app_identifier                      | com.xxxxxx.xxx |
| adhoc                               | false                |
| skip_install                        | false                |
| development                         | false                |
| force                               | false                |
| team_id                             | XXXXXXX           |
| ignore_profiles_with_different_name | false                |
| cert_id                             | XXXXXXX           |
| skip_fetch_profiles                 | false                |
| skip_certificate_verification       | false                |
+-------------------------------------+----------------------+

[15:51:46]: Starting login with user 'xxxxxxxx'
[15:51:49]: Successfully logged in
[15:51:49]: Fetching profiles...
[15:51:50]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[15:51:54]: Creating new provisioning profile for 'com.XXXXX' with name 'com.XXXXXXXX AppStore'
rm: Snapfile: No such file or directory
[15:51:57]: Variable Dump:
[15:51:57]: {:DEFAULT_PLATFORM=>:iOS, :PLATFORM_NAME=>:iOS, :LANE_NAME=>"iOS prep", :PRODUCE_APPLE_ID=>"XXXXXX", :CERT_FILE_PATH=>"/Users/...XXXX.cer", :CERT_CERTIFICATE_ID=>"XXXXX"}
[15:51:57]: 776: unexpected token at 'Bad Request'

@bencollier you didn't share your full stack trace. Can you check if you have the latest version of spaceship installed? Update using [sudo] gem update spaceship or bundle update if you're using bundler.

Yup updated spaceship beforehand which fixed the produce error :)
Sorry for forgetting the stack trace:
/Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/2.2.0/json/common.rb:155:in `parse': [!] 776: unexpected token at 'Bad Request' (Faraday::ParsingError)
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/2.2.0/json/common.rb:155:in `parse'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in `block in <class:ParseJson>'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `call'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `parse'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in `process_response'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in `block in call'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday-0.9.2/lib/faraday/response.rb:57:in `on_complete'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in `call'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in `build_response'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in `run_request'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in `post'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/spaceship-0.31.10/lib/spaceship/client.rb:413:in `block in send_request'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/spaceship-0.31.10/lib/spaceship/client.rb:330:in `with_retry'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/spaceship-0.31.10/lib/spaceship/client.rb:412:in `send_request'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/spaceship-0.31.10/lib/spaceship/client.rb:387:in `request'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/spaceship-0.31.10/lib/spaceship/portal/portal_client.rb:370:in `create_provisioning_profile!'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/spaceship-0.31.10/lib/spaceship/portal/provisioning_profile.rb:230:in `block in create!'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/spaceship-0.31.10/lib/spaceship/client.rb:330:in `with_retry'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/spaceship-0.31.10/lib/spaceship/portal/provisioning_profile.rb:229:in `create!'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/sigh-1.9.0/lib/sigh/runner.rb:113:in `create_profile!'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/sigh-1.9.0/lib/sigh/runner.rb:39:in `run'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/sigh-1.9.0/lib/sigh/manager.rb:7:in `start'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/actions/sigh.rb:20:in `run'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:190:in `block (2 levels) in execute_action'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:175:in `block in execute_action'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in `chdir'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:174:in `execute_action'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:100:in `trigger_action_by_name'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/fast_file.rb:140:in `method_missing'
	from ../../../fastlane/Fastfile:116:in `block (2 levels) in parsing_binding'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane.rb:33:in `call'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:49:in `block in execute'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/runner.rb:45:in `execute'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/command_line_handler.rb:30:in `handle'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:49:in `block (2 levels) in run'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane_core-0.50.3/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:246:in `run'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/commands_generator.rb:20:in `start'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
	from /Users/ocasta/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/fastlane-1.101.0/bin/fastlane:5:in `<top (required)>'
	from /Users/ocasta/.rbenv/versions/2.2.3/bin/fastlane:23:in `load'
	from /Users/ocasta/.rbenv/versions/2.2.3/bin/fastlane:23:in `<main>'

@bencollier Thanks for letting us know. Can you let me know if you are still seeing this? We are just now pushing out the last of the updates related to this issue. Thanks!


Highlighted student

Click on a student and edit the student. You will see that the selected student changed

:C

Emm, I think that is an intended feature, to always show the newly added/edited entry

Emm, I think that is an intended feature, to always show the newly added/edited entry

Hmm I don't think it is the intended feature, selected student is not the newly edited entry but the one before the previously selected student

Minor issue of

@yiwen101
After clicking on the third student (left panel) and using the command: "edit 3 -subject biology"
After successfully editing the student, the selected student is (the show student panel is correct - showing the edited student), but the selected student on the left panel jumps to the index before it as shown below:
Before editing student at index 3:

After editing student at index 3:

Third student shown with edited field but left panel shows selected student to be student at index 2.
Can choose to close this issue if not important/ not fixing.

Emm, I do not know how to fix.
Looks like a GUI issue.
Probably close for now?


ability to render last element in 1 render

I'm not quite sure what you mean by this. Do you mean force-rendering all items on the first render?

Closing for inactivity. Feel free to reopen.


Allow configuring custom proxy routes

Allows configuring custom routes in the ocis proxy. This enables development of custom ocis extensions

As discussed with @kobergj there needs to be an addon to the proxy service readme describing the behaviour of the capability and that it is only configurable via yaml.

Will add docu in separate PR :+1:


Updated README to further explain skip-if-no-diff

Current dependencies on/for this PR:

main

PR #360   👈

This comment was auto-generated by Graphite.


Onboard to 1.1 Release manifest in opensearch-build.

To include CCR inside of the full 1.1 bundle, it will need to be onboarded on to the build system here.
Requirements:

[ ] #147
Add necessary build.sh script if there is custom build logic for CCR.
Update the manifest.yml for the 1.1 release inside of opensearch-build repository.

Closing this as 1.1 changes are pushed.


Setup auto-updates

Is your feature request related to a problem? Please describe.
Currently application auto-updates is not working with the new Advanced Installer GitHub releases integration.
We can not release the application publicly without it.
Describe the solution you'd like
Figure out how the new github releases integration works and update the installer and CI process to support it.
Describe alternatives you've considered
NA
Additional context
Add any other context or screenshots about the feature request here.

The documentation is super vague. I have ran a few tests but been unable to get it working.
I posted the question in the advanced installer forums and I'm awaiting an answer from support.


Replacing more than 999+ occurences does not work?

VSCode Version: Code 1.16.0 (787b31c0474e6165390b5a5989c9619e3e16f953, 2017-09-06T16:54:47.289Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

elm-format
aba
0.1.0

vscode-eslint
dba
1.2.11

python
don
0.7.0

terminal
for
0.0.10

elm
sbr
0.15.0

Steps to Reproduce:
1.Having file like this
13
00:03:39,761 --> 00:03:42,179
You don't think he'll ask us how they died?
14
00:03:44,433 --> 00:03:46,225
Get back on your horse.
15
00:03:50,939 --> 00:03:53,441
Whatever did it to them
could do it to us.
16
00:03:53,567 --> 00:03:55,151
They even killed the children.
17
00:03:56,111 --> 00:03:58,112
It's a good thing we're not children.

CTRL+H with regex
^[\d:,> -]*$
Got
1of 999+
4.Replace all with nothing
5.Does not work

Reproduces without extensions: Yes/No

Releated to #32522

Duplicate of #32522 i.e. 54ca5101065a7cdb73049755e0393e7b2b31477f also fixes this.


Security 1.3: Major Database Updates

Create new table: Team
• team_ID (INT) – PK, NN
• name - NN
Location
• Add team_ID attribute as INT with default NULL
• Add foreign key: “fk_Location_Team” referencing Team from team_ID to team_ID
Sample
• Add team_ID attribute as INT with default NULL
• Add foreign key: “fk_Sample_Team” referencing Team from team_ID to team_ID
Assay
• Add team_ID attribute as INT with default NULL
• Add foreign key: “fk_Assay_Team” referencing Team from team_ID to team_ID
Plate
• Add team_ID attribute as INT with default NULL
• Add foreign key: “fk_Plate_Team” referencing Team from team_ID to team_ID
Create new table: TeamAffiliatedWithUser
• user_ID – PK, NN
• team_ID – PK, NN
• Add foreign key: “fk_TeamAffiliatedWithUser_Team” referencing Team from team_ID to team_ID
• Add foreign key: “fk_TeamAffiliatedWithUser_User” referencing Users from user_ID to ID
Users
• activated (TINYINT(1)) – NN, default 0
• Delete attribute “role”
Create new table: C_Security_Points
• ID (INT)– PK, NN
• name (VARCHAR(200)) – NN
• populate with security points as in Table 1
Create new table: C_User_Roles
• ID (INT) – PK, NN
• name (VARCHAR(45)) – NN
• populate with user role names as in Table 2
Create new table: UserRoleDefinitions
• security_point_ID – PK, NN
• user_role_ID – PK, NN
• Add foreign key: “fk_UserRoleDefinitions_C_Security_Points” referencing C_Security_Points from security_point_ID to ID
• Add foreign key: “fk_UserRoleDefinitions_C_User_Roles” referencing C_User_Roles from user_role_ID to ID
• populate with user role definitions as in Table 2
Create new table: UserSecurity
• user_ID – PK, NN
• security_point_ID – PK, NN
• Add foreign key: “fk_UserSecPoints_Users” referencing Users from user_ID to ID
• Add foreign key: “fk_UserSecPoints_C_Security_Points” referencing C_Security_Points from security_point_ID to ID
Create new table: C_Species
• ID (INT) – PK, NN
• name (VARCHAR(45)) – NN
Sample
• Change species attribute (VARCHAR) to “species_deprecated”
• Add species attribute as INT
• Add foreign key: “fk_Sample_C_Species” referencing C_Species from species to ID

All changes made.


Color Output in the CLI

The output can be hard to read at times. Especially now, with analyze-directory, it can be a lot to scroll through. Coloring the output might make this easier.

Maybe we could use TTK as a reference for this, they output with colors

No longer high priority


Graphics Tutorials

Although these have proved quite successful used in an ad hoc way with both adults and children as young as 10, there is much work needed to bring them up to a fully presentable form.
All the lessons need their own web page documentation.
The whole organisational structure of the lessons needs to be looked at.
But their are many smaller improvements that can be made. I can flesh out this issue further if needed.

yes do :)


connection problem

impossible to execute the connector:
ogame = OGame('Uriel', USER, PASW)
always the same error -> BAD CREDENTIALS

J'assume que tu parle français ?
Si c'est le cas, gâte toi :P
Otherwise, are you sure the USER and PASW values are set properly ?
let say you print(USER, PASW) can you see the right values.
Also, the default domain is en.ogame.gameforge.com, so if you're playing on fr.ogame.gameforge.com, you have to do:
ogame = OGame('Uriel', USER, PASW, domain='fr.ogame.gameforge.com')

perfect it's working the problem was with the domain. Thanks for all


[WIP] fix compilation on AIX

Fixes several issues in conjunction with #2671

TARGET autodetection always returning POWER5
Architecture detection failure setting the CROSS build flag
utest getting built as an empty shell without actual tests
lapack-test failures in COMPLEX with gfortran 7.3
compilation broken for POWER7 and earlier
m4 aborts with the AIX m4
inadequate compiler options for xlc/xlf

About c0afc11 (Fix POWERPC builds on AIX (gcc/gfortran 7)):

I see MYOS and MYTARGET instead of OS and TARGET
Also, on AIX, we use the OpenSource GNU version of m4, not the AIX version. And, for the OpenSource GNU version (v1.4.18), the option -B does exist but is not documented (they say: " warning: `m4 -B' may be removed in a future release "). So, it should be better to use some variable which could be defined out of the Makefile.L3 file.

I guess I could ask the m4 if it is GNU or AIX (probably not safe to assume everybody uses the GNU one). I have a few more compatibility fixes for assembly files that I need to append here, but I am still far from getting OpenBLAS to build with the AIX as and xlc (register naming, unimplemented constraints,...)


webapp:az webapp list-runtimes - Results in error. Ubuntu

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp list-runtimes
Errors:
'bool' object has no attribute 'provider'
Traceback (most recent call last):
python3/dist-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 608, in execute
    raise ex
cli/core/commands/__init__.py, ln 666, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 659, in _run_job
    six.reraise(*sys.exc_info())
...
cli/command_modules/appservice/custom.py, ln 704, in list_runtimes
    return [s['displayName'] for s in runtime_helper.stacks]
cli/command_modules/appservice/custom.py, ln 2159, in stacks
    self._load_stacks()
cli/command_modules/appservice/custom.py, ln 2180, in _load_stacks
    raw_stacks = self._client.provider.get_available_stacks(os_type_selected=os_type, raw=True)
AttributeError: 'bool' object has no attribute 'provider'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp list-runtimes

Expected Behavior
Environment Summary
Linux-5.8.0-53-generic-x86_64-with-glibc2.29
Python 3.8.5
Shell: bash

azure-cli 2.0.81

Extensions:
azure-devops 0.17.0

Additional Context

route to service team

@calvinsID - Since you already make some work around it in the recent past, I am assigning it to you. Please take a look in to this.

hey @SiebeDev it seems like an old version of CLI - can you please try using a newer version?

@SiebeDev can you try with newer version of CLI- 2.23.0 and confirm back.

Hi, yes my bad indeed. I used the ubuntu native version.
apt install  instead of following the instructions on the docs website.


Add valid_output_type() to validate the filename given via '-o'

fixes allinurl/goaccess#901

Minor fix was force pushed.  PR is stable now.

sigh - I need to make a minor fix, '-o' != '-f'

Minor fix has been force pushed.  PR is ready to merge.

Merged. This is great! Thank you!


Checks are attached to the first suite not necessarily the correct suite

Relevant discussion: Specify check suite when creating a checkrun


Advantage of pipeline over cloud function

Thank you for this great example!
I was wondering what the advantages are of triggering a Kubeflow pipeline over calling Vertex AI endpoints from the cloud function directly? Or is the latter not possible?

@doender
Vertex AI pipeline can be triggered in any ways, and you can benefit many things by triggering it in Cloud Function. For example:

Cloud Function can be triggered from events from GCP's other services.
When it is set to be triggered by GCS bucket, whenever there are changes in a bucket, you can decide to trigger the pipeline by putting some conditional logics in the Cloud Function.
When it is set to be triggered by Cloud Scheduler, you can periodically check if the performance of the currently deployed model degraded, and you can trigger the pipeline based on the threshold you set
....


warning: directory not found for option '-F/Users/user/development/bleApp/ios/../node_modules/react-native-ble-plx/ios/BleClientManager/Carthage/Build/iOS.' when running in Xcode.

I've managed to get further with getting this library to work with iOS, however this one mystifies me. I have followed all the steps necessary (except 11) for getting this to work in iOS. However, I'm getting this error when I run this in Xcode. The directory and files do exist, they've been made, but I don't understand what's going on here. Has anyone got any advice? Thank you in advance!
(NOTE: No, my username on my computer is not 'user!')

Do you have carthage installed?
If not, do this in terminal (you need homebrew to download carthage)
brew install carthage
create cart file with terminal in your repository where your .xcodeproj file is
touch Cartfile
open the file with a Texteditor and add the line
GitHub "Polidea/react-native-ble-plx"
save and then run
carthage update
Thats where I get my error
https://github.com/Polidea/react-native-ble-plx/issues/149
I hope you will succeed

UPDATE: I have got it working! Though I will admit, the fault is my own. Also, the clue is in the title of this issue.
That's right, this was caused by a spelling mistake.
Altogether now...

This issue is now closed. I'm off on a humiliation conga.

What spelling mistake? Can  you please clarify?


I am happy

I am happy
Originally posted by @MTTVI in https://github.com/MTTVI/github-slideshow/pull/3/threads/MDIzOlB1bGxSZXF1ZXN0UmV2aWV3VGhyZWFkNDA5MjI4NjAw/resolve

done


The training speed with InfiniBand

I updated our device from ethernet to InfiniBand, and expected there would be a huge boost in training speed. Unfortunately, it did not happen.
Have you tested your training with InfiniBand? How the training speed is?
Are there any extra steps for using InfiniBand? In my case, I just test the connection speed with "ping", and used it the same way as using ethernet.

Haven't tried this before. Maybe you can create a discussion to discuss this


Updated cs (Czech) translation

Commit made via Stringlate

Please add the translated Strings to the strings.xml


Bump addons and inbound versions

Bump addons and inbound versions

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9707609402

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9707609402
Status: success


Removed Names from LoadBalancers, and TargetGroups

Stack name is now captured in tags.
Issue #, if available:
Ingress's would fail to build if stack name was longer than 32 characters.
Description of changes:
This change lets Cloudformation auto name these resources.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1


LPCXpresso55S69_ns target : build failed

There are some compilation problems when trying to compile Zephyr samples with the target "lpcxpresso55s69_ns".
To Reproduce
west build -p auto -b lpcxpresso55s69_ns samples/hello_world
Issues
It seems that there are 3 problems :
One in lpcxpresso55s69_ns_defconfig file : CONFIG_ARM is not user configurable
and two in nxp_lpc55s6x_ns.dtsi file : It's missing i2c.h as included file and we have to replace kinetis-gpio by lpc-gpio otherwise the declaration of kinetis-port is missing.
Environment :

OS: Ubuntu
Toolchain : Zephyr SDK
Zephyr version : 2.2.99

Fixed by #24368


xxHash: add pkg-config file fix, clean up a bit

Description of changes
Add a patch to fix the pkg-config file generated by the new cmake-based build. Fixes tdesktop and friends. No nixpkgs-review because this is a lot, but tdesktop builds fine.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Ping @RasmusRendal @vcunat

A very large rebuild :-(  but yes, it looks like a regression since nixpkgs master.

This was merged, but github didn't properly register.

Indeed.

Commit 20972d657edef0ca was merged but this PR shows commit dc8c268.  I'm not sure how this happened.

Probably because of your Committed-by


Spelling mistake

A VARY BASIC Go Based Licensing System...
-> "A VERY BASIC..." (unless VARY has some hidden meaning I am unaware of)

my bad, spelling is an issue for me... I hate to admit

No problem, I'm dyslexic too... :)


Bump version to 1.1-1 and fix automatic update PRs

As per conda-forge/r-skynet-feedstock#5

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin please rerender


Cleanup tslint/vscode warnings, require more recent vscode

target es6
Require at least 2 years old version of vscode for runInTerminal support
fix line number (broke due to independent PRs?)
vscode deprecations and warnings in launch.json
address tslint complaints

I have tried to address your comments, let me know if anything is still off.

Thanks @hoehrmann !

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


Add gitg 3.20.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

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

Microsoft Reviewers: Open in CodeFlow

cc @ryfu-msft: looks like it's bugged?


hongbo/test new features2

test new features
tweak

Pull Request Test Coverage Report for Build 3016
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.008%) to 83.717%

Files with Coverage Reduction
New Missed Lines
%

array/array.mbt
1
83.33%

Totals

Change from base Build 3013:
0.008%

Covered Lines:
3887

Relevant Lines:
4643

💛  - Coveralls


Cannot resolve 'react-addons-test-utils' in '...\enzyme\build'

Similar to  #891
ERROR in ./node_modules/enzyme/build/react-compat.js
Module not found: Error: Can't resolve 'react-addons-test-utils'

full error (click to expand)
ERROR in ./node_modules/enzyme/build/react-compat.js
Module not found: Error: Can't resolve 'react/addons' in 'D:\Projects\pvc\node_modules\enzyme\build'
@ ./node_modules/enzyme/build/react-compat.js 40:14-37 41:44-67
@ ./node_modules/enzyme/build/ReactWrapper.js
@ ./node_modules/enzyme/build/index.js
@ ./test/unit/tests/client/components/App.test.js
@ ./test/unit/tests/client/components/index.js
@ ./test/unit/tests/client/index.js
@ ./test/unit/tests/index.js
@ ./test/unit/entry.js
ERROR in ./node_modules/enzyme/build/react-compat.js
Module not found: Error: Can't resolve 'react-addons-test-utils' in 'D:\Projects\pvc\node_modules\enzyme\build'
@ ./node_modules/enzyme/build/react-compat.js 137:18-52
@ ./node_modules/enzyme/build/ReactWrapper.js
@ ./node_modules/enzyme/build/index.js
@ ./test/unit/tests/client/components/App.test.js
@ ./test/unit/tests/client/components/index.js
@ ./test/unit/tests/client/index.js
@ ./test/unit/tests/index.js
@ ./test/unit/entry.js
ERROR in ./node_modules/enzyme/build/react-compat.js
Module not found: Error: Can't resolve 'react/lib/ReactContext' in 'D:\Projects\pvc\node_modules\enzyme\build'
@ ./node_modules/enzyme/build/react-compat.js 42:21-54
@ ./node_modules/enzyme/build/ReactWrapper.js
@ ./node_modules/enzyme/build/index.js
@ ./test/unit/tests/client/components/App.test.js
@ ./test/unit/tests/client/components/index.js
@ ./test/unit/tests/client/index.js
@ ./test/unit/tests/index.js
@ ./test/unit/entry.js
ERROR in ./node_modules/enzyme/build/react-compat.js
Module not found: Error: Can't resolve 'react/lib/ExecutionEnvironment' in 'D:\Projects\pvc\node_modules\enzyme\build'
@ ./node_modules/enzyme/build/react-compat.js 72:2-43
@ ./node_modules/enzyme/build/ReactWrapper.js
@ ./node_modules/enzyme/build/index.js
@ ./test/unit/tests/client/components/App.test.js
@ ./test/unit/tests/client/components/index.js
@ ./test/unit/tests/client/index.js
@ ./test/unit/tests/index.js
@ ./test/unit/entry.js
webpack: Failed to compile.

package.json
"enzyme": "^2.9.1",
"react": "^15.6.1",
"react-dom": "^15.6.1",
"react-test-renderer": "^15.6.1"

I don't think this is relevant any more now that we're on v3.


Sphinx docs

Still need to setup a sphinx project in the doc directory.
Need to setup auto source file parsing and intersphinx at least.
A lot of stuff that has gone in lately already needs to be documented, for example the Django-like models and auth system, or how to create a management command, this all needs documentation.

this is done and merged into master


[DEV] Enhance OOB Record Output for Improved Clarity

The following image shows a sample output of new OOB printing function.

Now added traceback info.

Looks good to me!


Update dnsmasq.nix

Description of changes

Things done
modified dnsmasq's systemd preStart script so it executes the correct binary. Without this, dnsmasq will not start

Built on platform(s)

[x ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Fix.

Please restart from master branch.


Setup Preview Environment

This should be helpful for PRs and allowing contributions

And slowdown all the flood for changes directly ending up in the main branch


Feature Request: Hover to reveal highlighting

https://ptb.discord.com/channels/915186263609454632/1107502968179273778/1143315033871372389

Added in v0.6.7.


Can't use out option for adding multiple new download

Hi, I notice that the download links text box seems doesn't support the out option. Although I could set it in the Options page, the trouble is, when I add multiple links, all the task will be named the same!
I think that supporting the out option in the link box would be a useful feature.

Why don't you use the 'dir' option? The 'out' option is used to specify the full path and file name.

Yeah, that's exactly what I want to do. I need to rename the file for each link differently.
Here is my situation:
I got some videos to download and they had links like http://domain.com/xxx/videoname/1080.mp4. It's painful to rename them one by one after download, so I wrote a script to extract the file names from URL and generate the out options.
But I found out AriaNg doesn't support the out option and I have to back to Aria2 WebUI to add tasks.


fix htmlparser

need to set eol=lf in .gitattributes for testing compare html content from file.

close in flavor of https://github.com/nim-lang/fusion/pull/101


Code review request

Purpose of code changes on this branch:
Add a terminal mode interface for database editing using the urwid toolkit.

When reviewing my code changes, please focus on:
Usage of urwid widgets, proper subclassing, and signal usage. Particularly, is
it necessary to unregister signals when an object is no longer needed (goes out
of scope)?

After the review, I'll merge this branch into:
/trunk

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 8 Nov 2012 at 4:51

I'm willling...

Hello... thanks for being willing. But this request seems to be an artifact of the transfer of code from Google code hosting to github.  The code is already in there, but some aspects of urwid I had to guess at, and IIRC, this review was for the urwid author to take a look at it.


Performance test OPA, authorization

Overview
We did a great set of V1 and a few V2.0 benchmark tests. A single V2.1 benchmark was added to help debug terrible projects performance and was very helpful. Let's update all of the benchmarks to be for 2.1 since we've tested 1.0 and 2.0 in production at this point.
Done Criteria

[ ] Update all of the above benchmarks to run against 2.1 and add benchmarks for any other performance case we are concerned about (large number of teams, policies, etc) so we can feel confident what the limitations of AuthZ are when debugging customer issues and making recommendations.
[ ] Have a plan for how we can track the benchmark performance over time and correlate that to changes in Automate

Sprint planning notes:

edge cases to test

300 projects at least
lots of projects / subjects / policies
number of roles vs. action lists
introspection-related calls

ideas

testing on a system that matches our recommended requirements for automate
how do we track the benchmark performance over time and relate it to changes?

Responding to "how do we track the benchmark performance over time and relate it to changes?"
The most promising tool looks like benchplot:
https://godoc.org/github.com/aclements/go-misc/benchplot
"Command benchplot plots the results of benchmarks over time."
That's an enticing headline... but no examples or docs at all--just source code to figure out what to do with it.
As a backup, this one does plots of benchmark output also, so could be used in a more manual fashion:
https://github.com/cep21/benchdraw
"A CLI to turn Go's benchmark output into pictures"

Looks like applications-service is using benchstat to compare performance on master vs. an incoming pull request. It's not automated as part of the CI yet though

found a few more better documented benchmark charting options:

go-chart
plot (with some example plots)

created this issue for tracking OPA performance


Failed to execute question for question 89dbd7a9-b6e6-4de7-83d9-b05e9c8c5764

Hi, it's failed to execute question
The sql is timeout, but feedback type is unset. @Mini256
Question title
Who contributes both in TiDB and Kubernetes Repos?
Error message
Query execution timeout.
Generated SQL
SELECT DISTINCT
  `ge`.`actor_login` AS `user_login`
FROM
  `github_events` AS `ge`
WHERE
  `ge`.`repo_name` IN ('pingcap/tidb', 'kubernetes/kubernetes')
GROUP BY
  `ge`.`actor_login`
HAVING
  COUNT(*) = 2
LIMIT
  200

Chart info
{
  "chartName": "PersonalCard",
  "title": "Contributors in TiDB and Kubernetes Repos",
  "user_login": "user_login"
}

gharchive_dev> select * from explorer_question_feedbacks where question_id = UUID_TO_BIN('89dbd7a9-b6e6-4de7-83d9-b05e9c8c5764')\G
***************************[ 1. row ]***************************
id               | 420055
user_id          | 0
question_id      | 0x89dbd7a9b6e64de783d9b05e9c8c5764
satisfied        | 0
feedback_type    | error-query-timeout
feedback_content | {"timeout":30000,"querySQL":"SELECT DISTINCT `ge`.`actor_login` AS `user_login` FROM `github_events` AS `ge` WHERE `ge`.`repo_name` IN ('pingcap/tidb', 'kubernetes/kubernetes') GROUP BY `ge`.`actor_login` HAVING COUNT(*) = 2 LIMIT 200"}
created_at       | 2023-01-31 08:36:33
1 row in set
Time: 0.236s


data_center supplied to Client not used in all API calls

Several API calls do not use API_REGION_FORMAT setting, even when cronofy client is configured with data_center= 'de'  option. Several methods in client.py use settings.API_BASE_URL directly instead.
Workaround: Change API_BASE_URL setting in settings.py. This works, if the default data center need not be used at all.

This is fixed in 1.1.7


Update create-new-saas-offer.md

corrected billing models to reflect metered billing and per user options and clarified agency fee and saas promo.

@BrianLevenson : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@jborsecnik : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@BrianLevenson - can you resubmit these changes / commits to the private repo? these are too large for the public repo (and you should be working in the private repo for all your doc writing and editing.) thanks.

Some relevant info:

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you review staging and fix all validation issues, you can tag an author for review or add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see How to get to the private repo. You can also take a look at the GitHub account setup page for additional details on making sure you're set up.

re-opening after email discussion. will move these commits to the private repo, and tag you when it's ready. if it passes acrolinx and validation, and looks good on staging, we can sign of. thanks.


Error handling with effect

Which @ngneat/effects-* package(s) are the source of the bug?
effects-ng
Is this a regression?
No
Description
If an effect returns an unhandled exception, it can not be started again. For me its seems like a bug, or some kind of missing documentation to handle errors.
It's possible to use catchError, but there should be a more generic way to solve that problem?
From my submitted sample:

Please provide a link to a minimal reproduction of the bug
https://codesandbox.io/s/elfeffectserrorhandling-oo7qvf?file=/src/app/app.component.ts
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
No response
Anything else?
No response
Do you want to create a pull request?
Yes

Use tapResult. See readme.

I updated the sample, and it doesn't work like described in the readme
Can you please adapt my minimal sandbox example to show a working error handling? Maybe then I can create a PR with documentation on this topic for other people.

It should be in the inner observable:
  sampleEffect = this.createEffectFn(($: Observable<number>) =>
    $.pipe(
      switchMap(() => {
        return from(fetch('https://not-exists')).pipe(
          tapResult(
            (x) => console.log("Further processing of:", x),
            (error) => console.error(error)
          )
        )
      }),
    )
  );


setHorizontalSpacing not honored when setBodyBoxWidth also used

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?

Report a bug

What is the current behavior?

setHorizontalSpacing is not respected if setBodyBoxWidth is also used. It's only the latter that gets performed, whichever order they're called in  (I'm using the default left-to-right orientation).

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

Just take any of the basic box examples bundled with the code release and ensure the following call for getNodeSettings:
.getNodeSettings()
          .setSizingMode('size')
          .setBodyBoxWidth(250)
          .setHorizontalSpacing(200)
          .back()

What is the expected behavior?

That both the box width and horizontal spacing between nodes adopt the above values.

What is the motivation / use case for changing the behavior?

The default box width is too small for my purpose, so I need to make the boxes wider. This results in the boxes starting to encroach on each other.

Please tell us about your environment:

Version: 1.1.2
Browser: all
Language: Javascript

OK, so I can work around this by using setNodeDepthMultiplier, but surely using setHorizontalSpacing should be the correct way to go about this.