bundler: failed to load command: pod

New Issue Checklist

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

Issue Description
When running fastlane I found that in my local environment it keeps breaking at cocoapods step
My workaround is the following to get the app to build, however I don't get this problem on my other machine.
I tried reinstalling fastlane / gems and nothing seems to be working except the following. I'm wondering if this has something to do with fastlane being recently updated recently.
use_bundle_exec: false,

Thank you...
Complete output when running fastlane, including the stack trace and command used
$ fastlane beta_build_without_upload
[07:47:00]: fastlane detected a Gemfile in the current directory
[07:47:00]: however it seems like you don't use `bundle exec`
[07:47:00]: to launch fastlane faster, please use
[07:47:00]:
[07:47:00]: $ bundle exec fastlane beta_build_without_upload
[07:47:00]:
[07:47:00]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[07:47:12]: ------------------------------
[07:47:12]: --- Step: default_platform ---
[07:47:12]: ------------------------------
[07:47:12]: Driving the lane 'ios beta_build_without_upload' 🚀
[07:47:12]: -----------------------
[07:47:12]: --- Step: cocoapods ---
[07:47:12]: -----------------------
[07:47:12]: $ cd '.' && bundle exec pod install --verbose
[07:47:14]: ▸ bundler: failed to load command: pod (/Users/USER/.fastlane/bin/bundle/bin/pod)
[07:47:14]: ▸ Bundler::GemNotFound: Could not find CFPropertyList-3.0.0 in any of the sources
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:87:in `block in materialize'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `map!'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `materialize'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:176:in `specs'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:235:in `specs_for'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:224:in `requested_specs'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:118:in `block in definition_method'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:19:in `setup'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler.rb:100:in `setup'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/setup.rb:20:in `<top (required)>'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[07:47:14]: Exit status of command 'cd '.' && bundle exec pod install --verbose' was 1 instead of 0.
bundler: failed to load command: pod (/Users/USER/.fastlane/bin/bundle/bin/pod)
Bundler::GemNotFound: Could not find CFPropertyList-3.0.0 in any of the sources
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:87:in `block in materialize'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `map!'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `materialize'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:176:in `specs'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:235:in `specs_for'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:224:in `requested_specs'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:118:in `block in definition_method'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:19:in `setup'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler.rb:100:in `setup'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/setup.rb:20:in `<top (required)>'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'

[07:47:14]: $ cd '.' && bundle exec pod install --verbose --repo-update
[07:47:14]: ▸ bundler: failed to load command: pod (/Users/USER/.fastlane/bin/bundle/bin/pod)
[07:47:14]: ▸ Bundler::GemNotFound: Could not find CFPropertyList-3.0.0 in any of the sources
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:87:in `block in materialize'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `map!'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `materialize'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:176:in `specs'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:235:in `specs_for'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:224:in `requested_specs'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:118:in `block in definition_method'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:19:in `setup'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler.rb:100:in `setup'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/setup.rb:20:in `<top (required)>'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[07:47:14]: ▸ /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[07:47:14]: Exit status of command 'cd '.' && bundle exec pod install --verbose --repo-update' was 1 instead of 0.
bundler: failed to load command: pod (/Users/USER/.fastlane/bin/bundle/bin/pod)
Bundler::GemNotFound: Could not find CFPropertyList-3.0.0 in any of the sources
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:87:in `block in materialize'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `map!'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `materialize'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:176:in `specs'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:235:in `specs_for'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:224:in `requested_specs'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:118:in `block in definition_method'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:19:in `setup'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler.rb:100:in `setup'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/setup.rb:20:in `<top (required)>'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'

+------------------+-------------------------------+
|                   Lane Context                   |
+------------------+-------------------------------+
| DEFAULT_PLATFORM | ios                           |
| PLATFORM_NAME    | ios                           |
| LANE_NAME        | ios beta_build_without_upload |
+------------------+-------------------------------+
[07:47:14]: bundler: failed to load command: pod (/Users/USER/.fastlane/bin/bundle/bin/pod)
Bundler::GemNotFound: Could not find CFPropertyList-3.0.0 in any of the sources
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:87:in `block in materialize'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `map!'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `materialize'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:176:in `specs'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:235:in `specs_for'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:224:in `requested_specs'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:118:in `block in definition_method'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:19:in `setup'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler.rb:100:in `setup'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/setup.rb:20:in `<top (required)>'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'

+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | default_platform | 0           |
| 💥   | cocoapods        | 2           |
+------+------------------+-------------+

[07:47:15]: fastlane finished with errors

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

/Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in `shell_error!': [!] bundler: failed to load command: pod (/Users/USER/.fastlane/bin/bundle/bin/pod) (FastlaneCore::Interface::FastlaneShellError)
Bundler::GemNotFound: Could not find CFPropertyList-3.0.0 in any of the sources
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:87:in `block in materialize'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `map!'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/spec_set.rb:80:in `materialize'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:176:in `specs'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:235:in `specs_for'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/definition.rb:224:in `requested_specs'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:118:in `block in definition_method'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:19:in `setup'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler.rb:100:in `setup'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/bundler-1.14.6/lib/bundler/setup.rb:20:in `<top (required)>'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /Users/USER/.fastlane/bin/bundle/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'

	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/actions/cocoapods.rb:45:in `call_error_callback'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/actions/cocoapods.rb:31:in `block (2 levels) in run'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/helper/sh_helper.rb:78:in `call'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/helper/sh_helper.rb:78:in `sh_control_output'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/helper/sh_helper.rb:12:in `sh'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/actions/cocoapods.rb:30:in `block in run'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/helper/sh_helper.rb:78:in `call'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/helper/sh_helper.rb:78:in `sh_control_output'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/helper/sh_helper.rb:12:in `sh'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/actions/cocoapods.rb:27:in `run'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:232:in `block in execute_action'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:227:in `chdir'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/fast_file.rb:154:in `method_missing'
	from Fastfile:166:in `block (2 levels) in parsing_binding'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:281:in `call'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:281:in `execute_flow_block'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:46:in `block in execute'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/lane_manager.rb:56:in `cruise_lane'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/commands_generator.rb:333:in `run'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/fastlane/lib/fastlane/cli_tools_distributor.rb:108:in `take_off'
	from /Users/USER/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.112.0/bin/fastlane:23:in `<top (required)>'
	from /Users/USER/.fastlane/bin/bundle/bin/fastlane:22:in `load'
	from /Users/USER/.fastlane/bin/bundle/bin/fastlane:22:in `<main>'

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.2

Ruby
2.2.4

Bundler?
false

Git
git version 2.17.2 (Apple Git-113)

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

Host
Mac OS X 10.14.2 (18C54)

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

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

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

Xcode Version
10.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

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

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

# git url of match
@match_git_url = ENV["MATCH_GIT_URL"]

# Configuration to build an app
# minimum requirment to pack an app
Configuration = Struct.new(
  :provisioningProfile, # file name of the provisioning profile
  :buildConfiguration, # configuration name in xcode project
  :appIdentifier, # the app id for this configuration
  :exportMethod, # export methods, such as "ad-doc" or "appstore"
  :productName, # product name of config
  :scheme, # scheme to build ipa
  :matchType) # type to use match, type is adhoc, appstore and so on.

# @alpha = Configuration.new(
#   "match AdHoc io.hello.MyApp-dev",
#   "Debug",
#   "io.hello.MyApp-dev",
#   "ad-hoc",
#   "Your App Alpha",
#   "MyApp-Dev",
#   "adhoc")

# Adhoc is for thirdparty - crashlytics
@beta = Configuration.new(
  "match AdHoc io.domain.myApp",
  "AdHoc",
  "io.domain.myApp",
  "ad-hoc",
  "MyApp Beta",
  "MyApp-Dev",
  "adhoc")

@release = Configuration.new(
  "match AppStore io.domain.myApp",
  "App Store",
  "io.domain.myApp",
  "app-store",
  "MyApp",
  "MyApp-AppStore",
  "appstore")

module ProjectSetting
  Target = "MyApp"
  ProjectName = "MyApp.xcodeproj"
  WorkspaceName = "MyApp.xcworkspace"
  SDK = "iphoneos"
end

def match_config(config)
  match(git_url: @match_git_url,
        type: config.matchType,
        app_identifier: config.appIdentifier)
end

def package(config)
  # increase build number everytime when packaging a new build
  increment_build_number

  # stamp a bage on beta/alpha apps
  # stampBadge(config)

  # build_ios_app(
  #   clean: true,
  #   export_method: "development",
  #   scheme: "Development",
  #   workspace: "MyApp.xcworkspace"
  # )

  build_app(
    workspace: ProjectSetting::WorkspaceName,
    scheme: config.scheme,
    clean: true,
    output_directory: @output_directory,
    output_name: "#{config.productName}.ipa",
    configuration: config.buildConfiguration,
    silent: true,
    export_method: config.exportMethod,
    export_options: {
      signingStyle: "automatic", # or manual
      compileBitcode: false,
      uploadBitcode: false,
      provisioningProfiles: {
        config.appIdentifier => config.provisioningProfile
      }
    },
    sdk: ProjectSetting::SDK
  )
end

def notify_deliver_to_testflight
  slack_message("✈ Successfully Deliver to TestFlight! (ﾉ>ω<)ﾉ ✈", true)
end

def notify_build_complete
  slack_message("Build: COMPLETE.", true)
end

def notify_error(exception)
  slack_message("🖕 Something Wrong (ﾒ ﾟ皿ﾟ)ﾒ 🖕\n#{exception}", false)
  puts exception.message
  throw exception # throw error to cause lane to fail
end

def notify_deliver_to_appstore
  slack_message("🙆♂ Successfully Deliver to App Store! (๑´ㅂ`๑) 🙆♂", true)
end

def slack_message(message, success)
  slack(
    message: message,
    channel: "#devops",  # Optional, by default will post to the default channel configured for the POST URL.
    success: success,        # Optional, defaults to true.
    payload: {  # Optional, lets you specify any number of your own Slack attachments.
      "Build Date" => Time.new.to_s,
      "Built by" => @build_by || "Anonymous",
    },
    default_payloads: [:git_branch, :git_author]
  )
end

##############

default_platform(:ios)

platform :ios do

  before_all do |lane|

    # Ensure that git branch is clean
    # ensure_git_status_clean
    cocoapods(
      # use_bundle_exec: false,
      # clean: true,
      verbose: true,
      podfile: "./Podfile",
      try_repo_update_on_error: true
    )
  end

  # PRIVATE LANES

  # Beta TestFlight Lane
  lane :beta_testflight do
    begin
      match_config(@release)
      package(@release)
      # upload_to_testflight
      upload_to_testflight(
        beta_app_description: "Beta App",
        skip_waiting_for_build_processing: true
      )
      notify_deliver_to_testflight

    rescue => exception
        notify_error(exception)
    end

  end

  # Beta TestFlight Lane
  lane :beta_build_without_upload do
    begin

      match_config(@release)
      package(@release)
      notify_build_complete

    rescue => exception
        notify_error(exception)
    end
  end

  desc "Submit app to App Store."
  lane :build_and_upload_to_appstore do
    begin
      match_config(@release)
      package(@release)
      notify_build_complete
      deliver(
        force: true,
        skip_binary_upload: false,
      )
      notify_deliver_to_appstore
    rescue => e
      notify_error(e)
    end
  end

  desc "[Screenshots]"
  lane :capture_and_frame do
    snapshot
    frameit
  end

  desc "[Deliver Screenshots only]"
  lane :deliver_screenshots_and_metadata_only do
    deliver(
      submit_for_review: false,
      automatic_release: false,
      skip_binary_upload: true
    )
  end

  # A helper lane for refreshing provisioning profiles.
  desc "[REFRESH DEVICES]"
  lane :refresh_profiles do
    match(
      force_for_new_devices: true
    )
  end

  # Add device
  desc "[ADD DEVICE] Add a device using uuid"
  lane :add_device do
      device_name = prompt(text: "Enter the device name: ")
      device_udid = prompt(text: "Enter the device UDID: ")
      device_hash = {}
      device_hash[device_name] = device_udid
      register_devices(
        devices: device_hash
      )
    refresh_profiles
  end

  # Unit Test
  desc "[TEST] Runs all tests"
  lane :unittest do
    scan
  end

  after_all do |lane|
    # This block is called, only if the executed lane was successful
  end
  error do |lane, exception|
    # Error block
  end

end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier("io.domain.myApp") # The bundle identifier of your app
<EMAIL_ADDRESS># Your Apple email address

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

fastlane gems

Gem
Version
Update-Status

fastlane
2.112.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
2.3.5

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.7.0

rouge
2.0.7

xcpretty
0.3.0

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

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.5

tty-cursor
0.6.0

tty-spinner
0.9.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.6

excon
0.55.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.1.3

json
1.8.1

mini_magick
4.5.1

multi_json
1.12.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

naturally
2.2.0

simctl
1.6.5

uber
0.0.15

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

jwt
1.5.6

signet
0.11.0

memoist
0.16.0

os
0.9.6

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-env
1.0.5

google-cloud-core
1.2.7

digest-crc
0.4.1

google-cloud-storage
1.15.0

emoji_regex
0.1.1

libxml-ruby
3.0.0

psych
2.0.8

generated on: 2018-12-23

@fastlane-bot this is not a code signing issue..

[07:47:14]: ▸ bundler: failed to load command: pod (/Users/USER/.fastlane/bin/bundle/bin/pod) [07:47:14]: ▸ Bundler::GemNotFound: Could not find CFPropertyList-3.0.0 in any of the sources

This is the actual problem - somehow CFPropertyList-3.0.0 is not installed on your local machine. Can you check your project's 'Gemfile.lock which version is installed?


project directory keeps disappearing

I have a project on one computer that keeps losing a directory. In the project definition projects.cson file it looks like this:
[
  …
  {
    title: "Foo"
    paths: [
      "A:\\example\\foo"
      "A:\\example\\bar"
      "C:\\Users\\jdoe\\foo\\bar"
    ]
  }
  …
]

Every few times I use this (on Windows 10), I'll switch back to this "Foo" project and suddenly "C:\\Users\\jdoe\\foo\\bar" will be gone.
So I used to use https://atom.io/packages/project-plus and never had this problem. I only switched to project-manager because I thought project-plus was being discontinued.
I'm using project-manager 3.3.5.

There, it just did it again. I've done nothing but use Atom normally, and now a section of my projects.cson file as reverted to this:
[
  …
  {
    title: "Foo"
    paths: [
      "A:\\example\\foo"
      "A:\\example\\bar"
    ]
  }
  …
]

What is happening? Why do my edits keep disappearing from projects.cson? Is there a different "master file" I should be editing instead of projects.cson?

The only thing I can think of is that it for some reason is removed form the tree-view, because when that happens it will automatically be removed from the projects settings to keep it synced when you add/remove folders. So could there be anything else removing it because it's on another drive?

It's on the main C: drive, and should be available whenever I log in, as it's in my user directory.
But as I'm sure you are aware Atom + Project Manager has become really unstable recently when switching projects; sometimes it hangs, sometimes it switches but nothing appears, sometimes it switches fine, etc. This started happening around the time they introduced all these new dockable/hideable whatevers on the sides. I believe there are bugs registered for this both for Project Manager and Project Plus. So who knows what Atom is doing with the tree view, because it doesn't seem to work half the time when switching projects, anyway.


Failed DynamoDB update when committer is unexpected

I've set up a simple project to try out LambCI, essentially a barebones copy of mhart/test-ci-project.
The first build triggered successfully and I could view the logs in CloudWatch, albeit it was a failed build (expected) due to not finding the package.json as the project only had a README.md at the time. You can see the output of that here.
I then copied some of mhart/test-ci-project to add a simple NodeJS test, committed and pushed. I was presented with this stacktrace in CloudWatch:
2016-07-10T16:12:16.221Z	9a1541fb-46b8-11e6-bf88-f9860b5e257a	InvalidSetType: Sets can contain string, number, or binary values
 at Set.util.inherit.detectType (/var/runtime/node_modules/aws-sdk/lib/dynamodb/set.js:30:24)
 at Set.util.inherit.initialize (/var/runtime/node_modules/aws-sdk/lib/dynamodb/set.js:14:10)
 at new Set (/var/runtime/node_modules/aws-sdk/lib/dynamodb/set.js:8:10)
 at DocumentClient.AWS.DynamoDB.DocumentClient.AWS.util.inherit.createSet (/var/runtime/node_modules/aws-sdk/lib/dynamodb/document_client.js:451:12)
 at /var/task/db/index.js:107:60
 at Response.<anonymous> (/var/task/db/index.js:65:5)
 at Request.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/request.js:355:18)
 at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
 at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:77:10) at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:615:14)

This points to line 107 in db/injex.js.
So I think what's happened is this:
My local git config user.email property was set to a corporate email address and not one that is linked to my Github account (obviously my fault). My commit history shows that.
Updating the user.email property locally and committing again fixed the issue.
To reproduce this:

Set up project and integrate with LambCI
Ensure builds are being triggered in response to commits
Update your git config user.email property to an email not linked to your Github account: git config user.email "$UNRECOGNISED_AUTHOR"
git commit --allow-empty -m 'Trigger another LambCI build' && git push

I've uploaded a new zip to Lambda with a log line added to db/index.js before client.put:
log.info(build.committers)
log.info(Array.from(build.committers))

This outputs:
2016-07-10T17:33:11.816Z	5ca39eee-46c4-11e6-a459-41d3b5762327	Set { undefined }
2016-07-10T17:33:11.817Z	5ca39eee-46c4-11e6-a459-41d3b5762327	[ undefined ]

this happens in the case where the committer's email is not linked to the user's Github account.

Great tracking down – yeah, I should make sure to get rid of any undefined elements, hadn't really considered that.
Thanks for reporting!

This is fixed in v0.9.2 – thanks again for reporting it!


JBPM-5260 Filtering process/task tables in Process & Task Dashboard i…

…s broken
Added interval interpretation used in dataSetGroups  for dashboard drilldown functionality. @mswiderski, @cristianonicolai    can you take a look? Thanks!

really nice @nmirasch, +1


On update/creation of access, the browser offers to save the credentials

This is quite disturbing, and could be considered as a safety issue.

I think there's a HTML attribute to add that hints the browser not to save the password. Can't find it on MDN right now, though. I also seem to recall that the browser tries to save the password if the password field is within a form; putting the password field outside the form would be a workaround, but meh. Thanks for opening an issue.

removing id="login" of the input does the trick


AJ-528: More consistent error handling, reserve sys_*, test improvements

The big changes in this PR center around error handling.  I endeavored to ensure that all exceptions should now result in a standard error response that looks like:
{
	"timestamp": "2022-08-24T15:13:56.207+00:00",
	"status": <http status error code>,
	"error": "<code description (Bad Request e.g.)>",
	"message": "<exception message>",
	"path": "<url /264dc567-d962-46a1-988a-a698d2cdff19/records/v0.21/samples/entity_3 e.g.>"
}

I didn't specifically pinpoint the location of this behavior in the spring code, but it seems like ResponseStatusException when thrown seem to work fully out of the box--they yield the expected message and MockMvc handles them the same as the full blown app server.  this seems to corroborate what I was seeing.
For the reference related exceptions in RecordDao where we trap and inspect Postgres level SQL inspections, it initially didn't feel right to use a ResponseStatusException so I kept the existing custom exceptions and annotated them @ResponseStatus then in order to get those annotated exceptions to work properly I needed to add server.error.include-message=always to application.properties and I needed to introduce a new test suite that uses the full web stack in order to verify behavior.  I'm not sure if all of those changes were actually worth it.  It might be better to just let RecordDao throw ResponseStatusExceptions since the dao is already coupled to spring web via the annotation so I'm not sure what I've done is an improvement, but I got curious to see if I could make it work.  Another alternative that would de-couple the dao code from web classes entirely is to go back to the way things were before this PR and have the dao throw checked exceptions and for the calling code to try catch around those calls--this leads to more indentation and uglier controller code.  It seems unlikely that we'd have a use case for using RecordDao apart from the web service so the coupling in exchange for cleaner controller code seems like a good tradeoff to me.
Finally, there's a change here to prohibit using the prefix "sys_" when naming attributes and some changes to parse json in tests and assert against those parsed values rather that just use string matching.

Just realized I need to make these error responses consistent with the swagger.  Doing that now!

Just realized I need to make these error responses consistent with the swagger. Doing that now!

This is done; though admittedly I am not a swagger pro.


feat(react-query): add usePrefetchQuery, usePrefetchInfiniteQuery

close #1250
PR Checklist

[x] I did below actions if need

I read the Contributing Guide
I added documents and tests.

Codecov Report
Attention: Patch coverage is 0% with 10 lines in your changes missing coverage. Please review.

Project coverage is 69.51%. Comparing base (779121f) to head (2f3e640).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1252      +/-   ##
==========================================
- Coverage   70.57%   69.51%   -1.06%
==========================================
  Files          70       74       +4
  Lines         656      666      +10
  Branches      132      134       +2
==========================================
  Hits          463      463
- Misses        171      179       +8
- Partials       22       24       +2

Components
Coverage Δ

@suspensive/utils
47.16% <ø> (ø)

@suspensive/react
100.00% <ø> (ø)

@suspensive/react-dom
100.00% <ø> (ø)

@suspensive/react-native
100.00% <ø> (ø)

@suspensive/react-query
72.09% <ø> (ø)

@suspensive/react-query-4
0.00% <0.00%> (ø)

@suspensive/react-query-5
0.00% <0.00%> (ø)

@suspensive/react-query-next-experimental
∅ <ø> (∅)

@suspensive/react-query-next-experimental-4
6.15% <ø> (ø)

@suspensive/jotai
0.00% <ø> (ø)

@suspensive/cache
98.01% <ø> (ø)

@suspensive/react-image
80.39% <ø> (ø)

Docs after this pr being merged


In the graph, duplicating with Ctrl+D doesn't show the new node until you move another node around

I unfortunately can't easily test this as Ctrl + D does not work for me


Refinements to drop down boxes in UI

[ ] Can type in field to refine options, not just select with arrows for drop down lists

This is now #281


fix type of keywords entry in frontmatter (in /docker-store/, /toolbox/, and /kitematic/ dirs)

Describe the proposed changes
in /docker-store/, /kitematic/ and /toolbox/ :
change keywords's type from array to string.
Project version
current stable
Related issue
contributes to #435
Signed-off-by: Gaetan de Villele<EMAIL_ADDRESS>

Deploy preview processing.
Built with commit e92f48234bcf636252c8d951ff9689dc25241cf3
https://app.netlify.com/sites/docker-docs/deploys/582290c8d6865d57c77e3d7b

Thanks, @gdevillele :)


Any plans to bring this to 1.19.2 and beyond?

Just curious as I did entertain the idea of porting myself, but I don’t know if you have such plans already.
@raltsmc

Also, you will likely have to use Terrablender for the biomes.

Hey @raltsmc I am wondering the same thing but with a different twist.  If you are not interested in this mod anymore, I would like to publish it to CurseForge and Modrinth and maintain it myself.  Please let me know if you disapprove of this; otherwise if I don't hear from you for a while, I will pick some new name like Desolation Renewed or something and forge ahead.
If at any point in the future you would like to resume maintenance of the mod, just let me know that too.  I think Desolation was and still is a fairly unique biome mod which brings some fun new mechanics to the game, so I don't really care who maintains it; I just want to keep it available for folks like myself to play.

Hey @gniftygnome, sorry for the delayed reply - you have my blessing. I've been on and off wanting to pick up development again but as of now I don't see myself being interested in working on the mod in the foreseeable future. I'm happy to see the mod brought to newer versions, and it looks like you've done a great job of porting it so I thank you for that. Let me know once you've published it and I'll update the mod pages with links to your continuation.

I don't monetize my mods (it's disallowed by my employment contract) so if you would prefer to give me upload permissions to Curseforge and Modrinth, I can upload to the existing projects instead.

Sounds good.

I was considering 1.19.2 for my own attempt as well, but I had issues with my workspace acting off. Do you think you could help with creating a build for that version? @raltsmc

There are some quality issues that are harder to solve in 1.19.4, which is why I did not make a build for it.  Personally if I were you I'd just wait until I was making a 1.20 modpack.  1.20.1 has pretty broad community uptake at this point.

I've been out of the modding scene since I last worked on this mod so unfortunately I wouldn't be of much help with a 1.19.2 build. @Sunconure11


Missing plan_feature_id column in plan_subscription_usages table

Could you please add missing column plan_feature_id to plan_subscription_usages table?
Because right now relation usage of the PlanFeature model is working incorrectly.
$usage = $feature->usage;

 SQLSTATE[42S22]: Column not found: 1054 Unknown column 'plan_subscription_usages.plan_feature_id' in 'where clause' (SQL: select * from `plan_subscription_usages` where `plan_subscription_usages`.`plan_feature_id` = 3798 and `plan_subscription_usages`.`plan_feature_id` is not null)

Hi @czechbox could you please assist to this issue?


StyleSheet injection order

I have an issue related to the style sheet injection order. Say I create a React component library that exports a Button:
// MyLib/index.js
export const Button =
  injectSheet({ root: { color: 'blue' } })
    (({children, classes, className}) =>
      <button className={classnames(classes.root, className)}>{children}</button>)

Now I want to use this Button in my App:
// MyApp/menu.js
import { Button }  from 'mylib';

export const Menu = injectSheet({ button: { color: 'red' } })
  (({classes}) => <Button className={classes.button}>Click Me</Button>

In this scenario, I'd expect the button element in Menu to be red and this is how I understand this part of the documentation: https://github.com/cssinjs/react-jss/#injection-order

Style tags are injected in the exact same order as the injectSheet() invocation. Source order specificity is higher the lower style tag is in the tree, therefore you should call injectSheet of components you want to override first.

In practice this is what I see, so it works fine, except when I am developping both MyLib and MyApp at the same time so linking MyLib in MyApp: yarn link mylib. In that case, I have noticed some order issue. The button element has 2 classes that look like this:

Button-root-1-1-1 -> this is coming from the first injectSheet in MyLib
Menu-button-0-1-2 -> from the second injectSheet in Menu
In this scenario, the Button-root-1-1-1 class wins and the button is blue and not red..

I've noticed that the moduleId number differs between the two. Could it be the issue? I tried using a JssProvider with classNameGenerator prop in MyApp as explained here https://github.com/cssinjs/react-jss/#multi-tree-setup which seems to keep the moduleId to 0 but still I see the same css conflict.
Any idea on how to solve this?
Thanks

if module id differs, you included multiple versions of JSS in your bundle, try to fix that and use one version.

Thanks @kof for your prompt response. When doing a yarn link you do not expect this happening right?

Can't tell, not using yarn, but you can check what version ends up in the bundle in the various ways.


Why does PolynomialDecaySchedule default to power=1.0?

Question
This is not a bug report but a hparam choice question for PolynomialDecaySchedule.
We are adding a polynomial decay scheduler in transformers (https://github.com/huggingface/transformers/pull/6361) and I was told to match the defaults to PolynomialDecaySchedule.
Could you please explain why the default power is 1.0 and not another value that actually activates the polynomial decay?
Surely one can override it, but your recommendation is not to override it as it can be seen here:
https://github.com/pytorch/fairseq/blob/master/examples/mbart/README.md#finetune-on-en-ro
--power is left to the default value of 1.0.
Thank you for your time.

This is based on the original BERT code, which implemented a linear decay via a polynomial schedule with power=1.0: https://github.com/google-research/bert/blob/f39e881b169b9d53bea03d2d341b31707a6c052b/optimization.py#L37

Thank you very much for your response and the link, @myleott!


Removing Items Added Via Search n' Pick Option Bug

@cabarius :
Describe the bug
See following screenshot:

To Reproduce
Steps to reproduce the behavior:

Click 'Remove Item' for any inventory item under Search n' Pick
Error depicted in screenshot above produced.

Save File
File over 25MB : https://ufile.io/2gf6aa4d
Settings
Settings.zip
Version Info:

ToyBox Version: [e.g. 1.4.16]
WotR Version [1.3.3e]

Just wanted to say I'm getting this bug too.

Same here, tried it on a completely new game and it looks like save game size or game progression aren't the issue.

Is this still an issue?

Sadly my PC's mobo died and it's going to be a few weeks before I can test this again. @Xyrmes @Dhraiden if you guys could try it that'd be awesome.
Cheers!


Use absolute imports for ART

Because you get an import error when this is used as a dependency to another package.

can we please merge this


Workspace updates

@ddunbar this contains misc changes to Workspace, I can split these into multiple PRs if this becomes difficult to review

Sending back with some comments... I don't think we should take all of this in the current form. Let's break up the pieces and discuss individually.


FancyZones resets to Priority Grid layout if remote desktop sessions is disconnected and connected back

Microsoft PowerToys version
Release v0.60.1
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Each time I disconnect and reconnect to a Windows remote desktop session the zone layout defaults back to Priority Grid template from any other zone layout had set to before disconnecting.
I'm not even logging out just disconnecting the session. Everything upon reconnecting session remains open as is. This is basically equivalent to locking screen and unlocking screen.
I have tried without any success

disconnecting and connecting immediately back in
Running as admin or user mode
Selecting remember positions
both custom or ready templates
PowerToysReport_2022-07-23-20-56-15.zip
tested with multiple machines (windows 10 and Server 2022)

Is there no way to permanently set as default another layout for many monitors?
Works for the first two monitors in v 0.45.0 but the 3rd monitor resets to Priority Grid there as well
✔ Expected Behavior
Layout once selected should be remembered if momentarily i disconnect from Windows remote desktop session (RDP)

❌ Actual Behavior
Defaults back to

Other Software
Windows 10 v 21H2 Build 19044.1826
or
Server 2022  v 21H2 Build 20348.859

I am having the same exact issue. After connecting to a remote laptop with fancy zones already set via RDP, the layout is switched to Priority Grid.
If it makes any difference I also have fancy zones enabled on the local pc.
Power Toys v0.66.0

/dup https://github.com/microsoft/PowerToys/issues/9040


Support binding models to different credentials

Long story short, this allows you to do something like:
bounduser = LdapUser.bind_as(alias='somerandomid', username='foouser', password='foopassword')
with bounduser.objects.get(username='foouser') as u:
    u.something = 'something'
    u.save()

while keeping the 'global' LDAP credentials anonymous. We're going to use this to perform LDAP changes using the password user provided for authentication.

@rbarrois What do you generally think about this idea? I'd also need it and would now update the PR, add tests, and so on, but only if you will accept this feature once it is complete ☺.

I think this is quite interesting; but we'll have to think thoroughly at all the ways credentials can be passed; for instance, when a user logs in with a kerberos ticket, we must provide entrypoints for the site developer to provide that (proxied) ticket to the library.

I think this is quite interesting; but we'll have to think thoroughly
at all the ways credentials can be passed; for instance, when a user
logs in with a kerberos ticket, we must provide entrypoints for the
site developer to provide that (proxied) ticket to the library.

I think that's out of scope here, because ldapdb doesn't work with Kerberos anyway (hardcoded simple_bind).
How about first getting this in for simple credentials, and open a new issue for full Kerberos support?


feat: added package-folders option to changesets cli

#250  👈
develop

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

Join @bob-obringer and the rest of your teammates on  Graphite


Beginning of audio egress is sped up

When I create an audio egress, the first few seconds of the recording are sped up - is there anything I can do to prevent this?

Can you share the Egress request that you've made? also moving this to the right project


Fix zip file bug

Fix #10 - looks like there was an issue in how the zip URL was constructed.
Also made some small changes to the logging output.

Actually it looks like Kleros is still failing for some reason.


Inception output size

Hi! I'm confused as to the fusion layer. I thought Inception Resnet v2 was supposed to have 1000 classes, so  the output is supposed to be of the shape (1000, ), not 1001. Can you explain this?

The original implementation of Inception ResNet v2 uses an output shape of 1001. Probably to include a "background/unknown" class. In order to use the pretrained version of Inception you must stick to those 1001 outputs or replace the final layer (and train it).


[Announcement] This repo will be archived November 2023

TLDR; With the growing dev container spec, our core dev container work has moved to the dev containers org on GitHub. Thus, we will archive this vscode-dev-containers repo in November 2023.

👋 Hi dev container community!
Opening the dev container specification has been an incredible journey over the past year. We've implemented key changes to how and where we host and accept contributions to dev container resources, which we described in an earlier announcement issue: https://github.com/microsoft/vscode-dev-containers/issues/1589.
Archiving this repo
We want to ensure everyone gets the latest resources (dev container images, Features, and Templates), which are all hosted in the dev containers org on GitHub, or through our community index. The spec has reached a point where we will no longer use or reference this vscode-dev-containers repo.
To avoid confusion and an additional maintenance burden, we will archive this repository in November 2023.
What does archiving mean to me?
If you've already been using the latest dev container resources in the dev containers org on GitHub, this change should have no impact on you!
If you're still using any of the resources in this repo, please migrate to using resources in the dev containers org instead by November 2023. If you'd like to contribute a definition from this repo that isn't yet in our index, please feel free to publish one and contribute it to our index. We will not be deleting this repo though, so you can still review it if necessary after November.
Closing - thank you!
Your involvement, feedback, contributions to, and use of dev containers has been instrumental in us opening up the dev container spec - THANK YOU for everything! We can't wait to see how our community continues to grow and collaborate!
If you're looking to get started with dev containers or filing an issue / feature request, here are some places to get started:

Dev Container images managed by the Dev Container spec maintainers: https://github.com/devcontainers/images
Dev Container Features managed by the Dev Container spec maintainers: https://github.com/devcontainers/features
Dev Container Templates managed by the Dev Container spec maintainers: https://github.com/devcontainers/templates
For new Definitions/Templates, see https://github.com/devcontainers/template-starter to get started and add your Template to the community index
For new Dev Container Features, see https://github.com/devcontainers/feature-template to get started and add your Feature to the community index

Hi @papakpmartin, thanks for reaching out. The repos above are accurate and will provide the latest resources provided by the spec maintainers and community.
Certain templates in this repo, like the Azure Functions ones, haven't been migrated elsewhere. You're welcome to explore and try using such templates, but please note that they aren't being maintained so you'll want to make sure they have the right versions of images, other packages, etc that you need.
For any templates that aren't yet migrated elsewhere, we certainly welcome the community to contribute their own to our index too!

Nov 29, 2023 archive update
Thank you to everyone again for the continued interest in, adoption of, and contributions to dev containers. Dev containers and their open spec are able to succeed because of our incredible community!
As mentioned in the issue above, we're so excited to continue growing dev containers with you all. Please continue to use the dev container GitHub org and containers.dev as the new homes for everything dev containers.
We'll be archiving this vscode-dev-containers repo this week.
We can't wait to continue collaborating with you all in the new repos and GitHub org - THANK YOU again!


[Node.JS]Securing Node.JS web apps with JSON Web Tokens(JWTs) - A comprehensive guide

Topic Suggestion
Proposal Submission
Proposed title of article

Securing Node.JS web apps with JSON Web Tokens(JWTs) - A comprehensive guide

Proposed article introduction

Security is a very important driving factor to be considered when creating any form of software for use, this also includes websites and applications. One way or the other, a website or web app always has some sensitive data to hold as entrusted by its users. At the most minimal level, websites are required to store user login information I.e username or email and password which serve as credentials to verify registered or recognized users.
At the same time, there are always people who would want to gain unauthorized access to these data and it lies in the hands of the owner or creator of an application to ensure that the best measures possible are implemented to secure their users' information.
There are so many popular ways by which hackers gain unauthorized access to networks, databases, people's credentials, and many more entities on the internet. Almost all of these methods or attacks have countermeasures, and it is very important to be aware of the threats posed by these attacks and how to prevent falling victim to the attacks. A few examples of these attacks are SQL injection, Cross-Site Scripting(XSS), Cross-Site Request Forgery(CSRF), etc. A reasonable amount of the attacks have a goal which is: the attacker impersonating the original user to carry out actions on behalf of the user on the web application. It is therefore the responsibility of every developer to gain some knowledge of the most popular attacks and ways to defend their websites, applications, and users against them.
In this article, you'll learn how to JSON Web Tokens to authenticate and authorize users of your application, eliminating XSS and CSRF attacks as well as possible.

Key takeaways

At the end of this article, the reader must have learned:
The importance of web security and different forms of web attacks
What JWTs are and what they do
The pros and cons of JWTs
How to create a CRUD app with user authentication in Node.JS
How to store JSON Web Tokens securely

Article quality

This article is unique in the sense that it gives its reader a basic idea of why security is very important in web development today, how important it is to ensure that users won't regret entrusting an application with their information and card details, and many more expo on why it is such a necessity to take the security of web apps seriously. It also adds the bonus of teaching the reader a simple, secure, and optimized method to store JWTs on the client side.

References
jwt.io/introduction
https://fusionauth.io/learn/expert-advice/tokens/pros-and-cons-of-jwts/
https://jcbaey.com/authentication-in-spa-reactjs-and-vuejs-the-right-way/?utm_source=medium&utm_campaign=spa-authentication

Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Unfortunately, we are not accepting more Node.js articles. We have plenty of them at the moment. Feel free to suggest another topic. Thanks


After adding file or folder exceptions the integration no longer identifies any errors

I am running HA Core 2023.2.1, VENV on Python 3.10.  Integration has been running well for quite some time, thank you!  However, I have some KeyMaster yaml and services that I would like to exclude.  I tried “Configuring” the integration again with the file/folder exceptions but after saving, Watchman no longer identifies known errors that were previously listed and not part of the exception list.  This occurs even after restarting and reloading the integration.
note: I have not removed and attempted to reinstall the integration.

This is a duplicate of issue #78

Apologies, for some reason the issue never posted on my phone but apparently it did!  Closing this as it is a duplicate.


missing smplx_vertex_lmkid.npy

Hi, thank you for releasing the code. I tried the demo code but got this error.
FileNotFoundError: [Errno 2] No such file or directory: './data/smpl_related/smpl_data/smplx_vertex_lmkid.npy'
Could you please share this file?
Thanks!

+1

Let me check this. Here is a link to this file on onedrive: https://1drv.ms/u/s!AtYZWFVkmRdwnEGztvH42Pmd4dYK?e=Ql1hsq
I'll check what is wrong with the data downloading instructions and update it as soon as possible. Thanks for pointing out!

thank you. i will try it.
---Original---
From: "Zechuan @.>
Date: Wed, Mar 6, 2024 19:04 PM
To: @.>;
Cc: "Guangtao Lyu ( 吕光涛<EMAIL_ADDRESS>Subject: Re: [River-Zhang/SIFU] missing smplx_vertex_lmkid.npy (Issue #4)
Let me check this. Here is a link to this file on onedrive: https://1drv.ms/u/s!AtYZWFVkmRdwnEGztvH42Pmd4dYK?e=Ql1hsq
I'll check what is wrong with the data downloading instructions and update it as soon as possible. Thanks for pointing out!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

missing  MANO_SMPLX_vertex_ids.pkl

https://huggingface.co/lilpotat/pytorch3d/tree/main/smpl_data
this link has many related files?

The website is not accessible. Could you please share the source file with me instead?

https://huggingface.co/lilpotat/pytorch3d/tree/main/smpl_data this link has many related files?

The website is not accessible. Could you please share the source file with me instead?

This website is accessible but you may need a VPN or tizi to open it.


Apply to relevel to SANDBOX or INCUBATION

The CNCF Sandbox and Incubation application forms are live GitHub Webform.
Sandbox is here: https://github.com/cncf/sandbox/issues/new?assignees=&labels=New&projects=&template=application.yml&title=[Sandbox]+<Project+Name>?assignees=&labels=New&projects=&template=application.yml&title=[Sandbox]+<Project+Name>
Incubation is here: (TBD)
We should familiarize ourselves with it and begin preparing & collecting data to fil in each field.
SANDBOX
CNCF TOC provided guidance as to how they will review Sandbox applications.
See it here: https://github.com/cncf/sandbox#how-applications-are-reviewed
The current CNCF Sandbox Application GitHub Project Board is here: https://github.com/orgs/cncf/projects/14
As of today, there are 54 projects in the queue. I have started doing some analysis on them.
11 projects are currently in HOLD status
These projects have been given explicit feedback by TOC as to why they have not been APPROVED

5 have been postponed and asked to reapply in 6 ~ 12 months
5 have been DECLINED and REJECTED
1 has been advised to MERGE with a CNCF project and become a sub-project of the parent
The above 11 project experienced an average waiting time of 4 months from making the application to getting an Decision

25 new Projects (separate to the ones on HOLD) have passed through the entire process in 2023 / 2024

18 have been voted on an APPROVED
6 have been DECLINED and/or REJECTED

Maintainers decided that we will apply into the SANDBOX level.

We received advise from Chris A (CNCF) that we are permitted to re-apply as Incubation level.
We are now considering this option.

Maintainers are still to decide, moving target date to end of this week

Decision to apply for SANDBOX was made on 27 May 2024.
 SANDBOX Application was submitted by @edrob999  on 13 June 2024.

CNCF Tracking Issue is here:  https://github.com/cncf/sandbox/issues/104

Great job everyone !


The Avatar of Death monster has incorrect CR and XP

Originally in GitLab by @captain-yoshi
The Monster Avatar of Death has incorrect CR (should be an En or EM dash —) and have 0 XP per DMG pg. 164.
Is this monster really in the SRD? It is not in the SRD (Basic Rules) of DnD Beyond (It comes with the DMG). And I cannot see this monster in any website that talks about DnD5e SRD.

I think the DMG made a mistake making the Avatar of Death's CR as a dash. The point is the Avatar of Death is worth 0 XP. The SRD, the Monster Manual (p.9) and even the DMG itself (p.275) all state that a CR 0 creature is worth 0 or 10 XP. So maybe we need two different CR 0 entries?
CR 0 (0 XP) (a new entry, used for the Avatar of Death, and maybe others)
CR 0 (10 XP) (a relabel of the existing entry)

So maybe we need two different CR 0 entries?

Alternatively, allow for overriding the XP value of a creature such that it is not necessarily derived from its CR. It could work identically to how Hit Point maximum of a character is derived (if null) but can be overridden.

Now that NPC CR is a nullable field, this creature should probably have a CR of null.