uninitialized constant Gym::CodeSigningMapping

New Issue Checklist

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

Issue Description
When running gym as part of a lane I consistently get an uninitialized constant Gym::CodeSigningMapping error, but havent been able to find any cause.
I have also been having another issue when using fastlane 2.51.0 where gym is not creating an ipa file for my react native (9.42.2) project, but not sure if that related or not!
Complete output when running fastlane, including the stack trace and command used

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

Roberts-MacBook-Pro:papertrailApp robertwalker$ fastlane ios beta
[22:57:20]: -------------------------------------------------
[22:57:20]: --- Step: Verifying required fastlane version ---
[22:57:20]: -------------------------------------------------
[22:57:20]: Your fastlane version 2.53.1 matches the minimum requirement of 2.51.0  ✅
[22:57:20]: ------------------------------
[22:57:20]: --- Step: default_platform ---
[22:57:20]: ------------------------------
[22:57:20]: Driving the lane 'ios beta' 🚀
[22:57:20]: -----------------------
[22:57:20]: --- Step: cocoapods ---
[22:57:20]: -----------------------
[22:57:20]: $ cd './ios' && bundle exec pod install
[22:57:22]: ▸ Analyzing dependencies
[22:57:22]: ▸ Downloading dependencies
[22:57:22]: ▸ Using Crashlytics (3.8.4)
[22:57:22]: ▸ Using Fabric (1.6.11)
[22:57:22]: ▸ Using Intercom (3.2.5)
[22:57:22]: ▸ Generating Pods project
[22:57:22]: ▸ Integrating client project
[22:57:23]: ▸ Sending stats
[22:57:23]: ▸ Pod installation complete! There are 3 dependencies from the Podfile and 3 total pods installed.
[22:57:23]: --------------------
[22:57:23]: --- Step: prompt ---
[22:57:23]: --------------------
[22:57:23]: Changelog:
[22:57:23]: Submit inputs using "END"
END
[22:57:29]: --------------------
[22:57:29]: --- Step: prompt ---
[22:57:29]: --------------------
[22:57:29]: Should the build be distributed to external testers? (y/n)

Please enter "yes" or "no".
[22:57:29]: Should the build be distributed to external testers? (y/n)
n
[22:57:30]: -------------------
[22:57:30]: --- Step: match ---
[22:57:30]: -------------------
[22:57:30]: Successfully loaded '/Users/robertwalker/code/papertrailApp/fastlane/Matchfile' 📄

+----------------+----------------------------------------------+
|          Detected Values from './fastlane/Matchfile'          |
+----------------+----------------------------------------------+
| git_url        |<EMAIL_ADDRESS>|
|                | pp-certs.git                                 |
| shallow_clone  | false                                        |
| platform       | ios                                          |
| app_identifier | com.papertrail.app                           |
| username       |<EMAIL_ADDRESS>                          |
+----------------+----------------------------------------------+

+-----------------------+----------------------------------------------+
|                       Summary for match 2.53.1                       |
+-----------------------+----------------------------------------------+
| type                  | appstore                                     |
| git_url               |<EMAIL_ADDRESS>|
|                       | pp-certs.git                                 |
| shallow_clone         | false                                        |
| platform              | ios                                          |
| app_identifier        | com.papertrail.app                           |
| username              |<EMAIL_ADDRESS>                          |
| git_branch            | master                                       |
| keychain_name         | login.keychain                               |
| readonly              | false                                        |
| team_id               | Z6Y4X6J5N8                                   |
| verbose               | false                                        |
| force                 | false                                        |
| skip_confirmation     | false                                        |
| clone_branch_directly | false                                        |
| force_for_new_devices | false                                        |
| skip_docs             | false                                        |
+-----------------------+----------------------------------------------+

[22:57:30]: Cloning remote git repo...
[22:57:30]: If cloning the repo takes too long, you can use the `clone_branch_directly` option in match.
[22:57:32]: 🔓  Successfully decrypted certificates repo
[22:57:32]: Verifying that the certificate and profile are still valid on the Dev Portal...
[22:57:35]: Installing certificate...

+-------------------+-----------------------------------------------+
|                       Installed Certificate                       |
+-------------------+-----------------------------------------------+
| User ID           | Z6Y4X6J5N8                                    |
| Common Name       | iPhone Distribution: Kit Log Ltd (Z6Y4X6J5N8) |
| Organisation Unit | Z6Y4X6J5N8                                    |
| Organisation      | Kit Log Ltd                                   |
| Country           | US                                            |
| Start Datetime    | May 11 21:21:22 2017 GMT                      |
| End Datetime      | May 11 21:21:22 2018 GMT                      |
+-------------------+-----------------------------------------------+

[22:57:36]: Installing provisioning profile...

+---------------------+------------------------------+------------------------------+
|                          Installed Provisioning Profile                           |
+---------------------+------------------------------+------------------------------+
| Parameter           | Environment Variable         | Value                        |
+---------------------+------------------------------+------------------------------+
| App Identifier      |                              | com.papertrail.app           |
| Type                |                              | appstore                     |
| Platform            |                              | ios                          |
| Profile UUID        | sigh_com.papertrail.app_app  | d49e2942-7d6e-468a-b996-f3c  |
|                     | store                        | 27886bb53                    |
| Profile Name        | sigh_com.papertrail.app_app  | match AppStore               |
|                     | store_profile-name           | com.papertrail.app           |
| Profile Path        | sigh_com.papertrail.app_app  | /Users/robertwalker/Library  |
|                     | store_profile-path           | /MobileDevice/Provisioning   |
|                     |                              | Profiles/d49e2942-7d6e-468a  |
|                     |                              | -b996-f3c27886bb53.mobilepr  |
|                     |                              | ovision                      |
| Development Team ID | sigh_com.papertrail.app_app  | Z6Y4X6J5N8                   |
|                     | store_team-id                |                              |
+---------------------+------------------------------+------------------------------+

[22:57:37]: All required keys, certificates and provisioning profiles are installed 🙌
[22:57:37]: Setting Provisioning Profile type to 'app-store'
[22:57:37]: ------------------------------------
[22:57:37]: --- Step: increment_build_number ---
[22:57:37]: ------------------------------------
Current version of project papertrailApp is:
    135

/Users/robertwalker/code/papertrailApp
[22:57:37]: $ cd /Users/robertwalker/code/papertrailApp/ios && agvtool next-version -all && cd -
[22:57:38]: ▸ Setting version of project papertrailApp to:
[22:57:38]: ▸ 136.
[22:57:38]: ▸ Also setting CFBundleVersion key (assuming it exists)
[22:57:38]: ▸ Updating CFBundleVersion in Info.plist(s)...
[22:57:38]: ▸ Updated CFBundleVersion in "papertrailApp.xcodeproj/../papertrailApp-tvOS/Info.plist" to 136
[22:57:38]: ▸ Updated CFBundleVersion in "papertrailApp.xcodeproj/../papertrailApp-tvOSTests/Info.plist" to 136
[22:57:38]: ▸ Updated CFBundleVersion in "papertrailApp.xcodeproj/../papertrailApp/Info.plist" to 136
[22:57:38]: ▸ Updated CFBundleVersion in "papertrailApp.xcodeproj/../papertrailAppTests/Info.plist" to 136
[22:57:38]: ▸ Updated CFBundleVersion in "papertrailApp.xcodeproj/../papertrailAppUITests/Info.plist" to 136
[22:57:38]: ▸ /Users/robertwalker/code/papertrailApp
[22:57:39]: --------------------------------
[22:57:39]: --- Step: get_version_number ---
[22:57:39]: --------------------------------
[22:57:39]: $ cd /Users/robertwalker/code/papertrailApp/ios && agvtool what-marketing-version -terse
[22:57:40]: ▸ "papertrailApp.xcodeproj/../papertrailApp-tvOS/Info.plist"=2.3.1
[22:57:40]: ▸ "papertrailApp.xcodeproj/../papertrailApp-tvOSTests/Info.plist"=2.3.1
[22:57:40]: ▸ "papertrailApp.xcodeproj/../papertrailApp/Info.plist"=2.3.1
[22:57:40]: ▸ "papertrailApp.xcodeproj/../papertrailAppTests/Info.plist"=2.3.1
[22:57:40]: ▸ "papertrailApp.xcodeproj/../papertrailAppUITests/Info.plist"=2.3.1
[22:57:40]: -----------------
[22:57:40]: --- Step: gym ---
[22:57:40]: -----------------
+------------------------------------+-----------------------------------------+
|                                 Lane Context                                 |
+------------------------------------+-----------------------------------------+
| DEFAULT_PLATFORM                   | ios                                     |
| PLATFORM_NAME                      | ios                                     |
| LANE_NAME                          | ios beta                                |
| SIGH_PROFILE_TYPE                  | app-store                               |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"com.papertrail.app"=>"match AppStore  |
|                                    | com.papertrail.app"}                    |
| BUILD_NUMBER                       | 136                                     |
| VERSION_NUMBER                     | 2.3.1                                   |
+------------------------------------+-----------------------------------------+
[22:57:40]: uninitialized constant Gym::CodeSigningMapping

+------+------------------------------+-------------+
|                 fastlane summary                  |
+------+------------------------------+-------------+
| Step | Action                       | Time (in s) |
+------+------------------------------+-------------+
| 1    | Verifying required fastlane  | 0           |
|      | version                      |             |
| 2    | default_platform             | 0           |
| 3    | cocoapods                    | 2           |
| 4    | prompt                       | 5           |
| 5    | prompt                       | 1           |
| 6    | match                        | 6           |
| 7    | increment_build_number       | 2           |
| 8    | get_version_number           | 1           |
| 💥   | gym                          | 0           |
+------+------------------------------+-------------+

[22:57:40]: fastlane finished with errors

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

Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new
Run `fastlane env` to append the fastlane environment to your issue
/Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/actions/gym.rb:29:in `run': [!] uninitialized constant Gym::CodeSigningMapping (NameError)
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/runner.rb:252:in `block (2 levels) in execute_action'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/runner.rb:230:in `block in execute_action'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/runner.rb:226:in `chdir'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/runner.rb:226:in `execute_action'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/runner.rb:148:in `trigger_action_by_name'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/fast_file.rb:146:in `method_missing'
	from Fastfile:116:in `block (2 levels) in parsing_binding'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/lane_manager.rb:52:in `cruise_lane'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/command_line_handler.rb:30:in `handle'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/commands_generator.rb:104:in `block (2 levels) in run'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in `call'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in `run'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:64:in `run!'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in `run!'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/commands_generator.rb:303:in `run'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/fastlane/lib/fastlane/cli_tools_distributor.rb:66:in `take_off'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/gems/fastlane-2.53.1/bin/fastlane:20:in `<top (required)>'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/bin/fastlane:23:in `load'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/bin/fastlane:23:in `<main>'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval'
	from /Users/robertwalker/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `<main>'

### Environment

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

<details><summary>✅ fastlane environment ✅</summary>

### Stack

| Key                         | Value                                       |
| --------------------------- | ------------------------------------------- |
| OS                          | 10.12.4                                     |
| Ruby                        | 2.3.1                                       |
| Bundler?                    | true                                        |
| Git                         | git version 2.6.2                           |
| Installation Source         | ~/.rvm/gems/ruby-2.3.1/bin/fastlane         |
| Host                        | Mac OS X 10.12.4 (16E195)                   |
| Ruby Lib Dir                | ~/.rvm/rubies/ruby-2.3.1/lib                |
| OpenSSL Version             | OpenSSL 1.0.2h  3 May 2016                  |
| Is contained                | false                                       |
| Is homebrew                 | false                                       |
| Is installed via Fabric.app | false                                       |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/ |
| Xcode Version               | 8.3.3                                       |

### System Locale

| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_GB.UTF-8 | ✅ |
| LC_ALL   |             |   |
| LANGUAGE |             |   |

### fastlane files:

<details><summary>`./fastlane/Fastfile`</summary>

```ruby
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.51.0"

default_platform :ios

platform :ios do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
    cocoapods(
      podfile: './ios'
    )

  end

  desc "Increment the app version patch"
  lane :bumpPatch do
    version_number = increment_version_number(
      xcodeproj: './ios/papertrailApp.xcodeproj',
      bump_type: "patch"
    )

    commit_version_bump(
      xcodeproj: './ios/papertrailApp.xcodeproj',
      message: "build(ios): bump patch to #{version_number}",
      force: true
    )

    push_to_git_remote
  end

  desc "Increment the app version minor"
  lane :bumpMinor do
    version_number = increment_version_number(
      xcodeproj: './ios/papertrailApp.xcodeproj',
      bump_type: "minor"
    )

    commit_version_bump(
      xcodeproj: './ios/papertrailApp.xcodeproj',
      message: "build(ios): bump minor to #{version_number}",
      force: true
    )

    push_to_git_remote
  end

  desc "Increment the app version major"
  lane :bumpMajor do
    ensure_git_branch # defaults to `master` branch

    version_number = increment_version_number(
      xcodeproj: './ios/papertrailApp.xcodeproj',
      bump_type: "major"
    )

    commit_version_bump(
      xcodeproj: './ios/papertrailApp.xcodeproj',
      message: "build(ios): bump major to #{version_number}",
      force: true
    )

    push_to_git_remote
  end

  # desc "Submit a new Beta Build to Apple TestFlight"
  # desc "This will also make sure the profile is up to date"
  # lane :beta do
  #   # match(type: "appstore") # more information: https://codesigning.guide
  #   gym(scheme: "papertrailApp") # Build your app - more options available
  #   pilot
  #
  #   # sh "your_script.sh"
  #   # You can also use other beta testing services here (run `fastlane actions`)
  # end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This action will also do a build version bump and push it to git."
  desc "This will also make sure the profile is up to date"
  desc "This will also send an email to all testers."
  lane :beta do

    changelog = prompt(
      text: "Changelog: ",
      multi_line_end_keyword: "END"
    )

    distribute_external = prompt(
      text: "Should the build be distributed to external testers?",
      boolean: true
    )

    match(type: "appstore")

    # sh %Q{cd ../ && rm -R node_modules && yarn}

    build_number = increment_build_number(
      xcodeproj: './ios/papertrailApp.xcodeproj',
    )

    version_number = get_version_number(
      xcodeproj: './ios/papertrailApp.xcodeproj',
    )

    gym(
      scheme: "papertrailAppRelease",
      workspace: './ios/papertrailApp.xcworkspace'
    )

    pilot(
      changelog: changelog,
      distribute_external: distribute_external
    )

    new_sentry_release(
      build_number: build_number,
      version_number: version_number
    )

    commit_version_bump(
      xcodeproj: './ios/papertrailApp.xcodeproj',
      message: "build(ios): push #{version_number}: #{build_number} to beta",
      force: true
    )

    add_git_tag

    push_to_git_remote

  end

  desc "Deploy a new version to the App Store"
  lane :release do
    # ensure_git_branch # defaults to `master` branch

    update_screenshots = prompt(
      text: "Update screenshots?",
      boolean: true
    )

    match(type: "appstore")

    if update_screenshots
      snapshot

      frameit(
        silver: true
      )
    end

    build_number = increment_build_number(
      xcodeproj: './ios/papertrailApp.xcodeproj',
    )

    version_number = get_version_number(
      xcodeproj: './ios/papertrailApp.xcodeproj',
    )

    gym(
      scheme: "papertrailAppRelease",
      workspace: './ios/papertrailApp.xcworkspace'
    )

    ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t DAV"
    deliver(
      force: true,
      automatic_release: true,
      skip_screenshots: !update_screenshots,
      overwrite_screenshots: update_screenshots,
      app_version: version_number
    )

    commit_version_bump(
      xcodeproj: './ios/papertrailApp.xcodeproj',
      message: "build(ios): push #{version_number}: #{build_number} as release",
      force: true
    )

    add_git_tag

    push_to_git_remote
  end

  # You can define as many lanes as you want

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

    # clean_build_artifacts
    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  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/fastlane#metrics

`./fastlane/Appfile`
app_identifier "com.papertrail.app" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "Z6Y4X6J5N8" # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.53.1
✅ Up-To-Date

gym
2.0.0
✅ Up-To-Date

pilot
2.0.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.2

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.13.6

io-console
0.4.6

CFPropertyList
2.3.5

i18n
0.8.6

minitest
5.10.3

thread_safe
0.3.6

tzinfo
1.2.3

activesupport
4.2.9

public_suffix
2.0.5

addressable
2.5.1

babosa
1.0.2

claide
1.0.2

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
1.3.1

cocoapods-deintegrate
1.0.1

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

netrc
0.7.8

cocoapods-trunk
1.2.0

cocoapods-try
1.1.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.0.1

gh_inspector
1.0.3

molinillo
0.5.7

ruby-macho
1.1.0

nanaimo
0.2.3

xcodeproj
1.5.1

cocoapods
1.3.1

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

declarative
0.0.9

declarative-option
0.1.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

dotenv
2.2.1

excon
0.58.0

multipart-post
2.0.0

faraday
0.13.1

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.12.2

fastimage
2.1.0

jwt
1.5.6

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

memoist
0.16.0

os
0.9.6

signet
0.7.3

googleauth
0.5.3

httpclient
2.8.3

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.1.0

representable
3.0.4

retriable
3.1.1

google-api-client
0.12.0

json
2.1.0

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.3.0

rubyzip
1.2.1

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.8.0

unicode-display_width
1.3.0

terminal-table
1.8.0

tty-screen
0.5.0

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
0.0.4

generated on: 2017-08-21

```

I dont seem to have any issues with the actual code signing itself. I can run fastlane match appstore successfully, and match(type: "appstore") runs fine in the lane. It seems to have issues during the gymphase.

@robwalkerco I suspect the problem here is related to a older, standalone gym (and also pilot) gem you have installed. It is possible you have both gym and pilot in a Gemfile, or maybe you just need to gem uninstall gem and gem uninstall pilot.  Either way, you should not need to have either of these standalone gems installed, as the fastlane gem has included those tools since version 2.0.0.
I hope this is helpful, please let us know if you have further questions!  🚀

Thanks @mpirri. You hit the nail on the head 👏


Option to have OpenAPI generator to generate separate page for each request.

What problem will this feature address?
Right now OpenAPI generates one page with many requests.
Describe the solution you'd like
Would be nice to have it like Mintlify does, where they have each request as separate page
Describe alternatives you've considered
https://demo.mintlify.app/api-reference/endpoint/get
Additional context
No response

I think considering the design of Fumadocs UI is more compact than Mintlify's, honestly it doesn't look good with our design.

I'll add it to the next release, but the default value will still be page.

Released!


[Traefik Plugin Catalog] Plugin Analyzer has detected a problem.

The plugin was not imported into Traefik Plugin Catalog.
Cause:
failed to run the plugin with Yaegi: plugin: failed to decode configuration: 1 error(s) decoding:

* 'TrustIP[0]' expected a map, got 'string'

Traefik Plugin Analyzer will restart when you will close this issue.
If you believe there is a problem with the Analyzer or this issue is the result of a false positive, please fill an issue on piceus repository.

fixed


Location validation

Validate matched stops with a location buffer (100m)
leave out historical stops from JORE data
improve logging

- Validate matched stops with a location comparison. Matches with distance between stops exceeding buffer (100m) are left out.
- Leave out deprecated JORE stops
- Use geojson as source
- improve logging output: stops with conflicting shelter info, stops exceeding the max distance limit


Wrap main around a container and use display: contents;

Check https://stackoverflow.com/questions/32289120/html-css-elements-not-resizing-with-the-web-page

Wrap main around a container and use display: contents;


⚠ Bofrost.at has degraded performance

In 112b9c6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2038 ms

Resolved: Bofrost.at performance has improved in 19b253d.


Recursive Upload of files from directories underneath.

Background : While starting a directory backup to s3, we jump over a directory and only  backup files to s3 within that directory.
Problem: This approach is good initially but not valuable in long run. If we want to backup a directory we need to make sure to back it up completely including the directory underneath.

If anyone willing to pick up this issue, please mention it in comments and also a brief idea about how would you go around doing it ?

I would!
An easy solution would be to refactor the backup method. It has nearly all capabilities. The goal is instead of skipping call itself recursively. Since symlinks could lead to loops I would not follow them by default and add a flag to follow as configuration. Although I am not sure how the sftp lib handles symlinks.
What do you think?

@enc : Let's do this. I think as per the change lets skip the symlinks all together in this change and just do with a recursive solution. We then can create a new PR for just handling the symlinks which will include the flag in configuration settings. Wdyt ?


Crate DAG is not respected when filling in -L flags

Right now when Cargo passes -L flags to the compiler from the output of build scripts, the crate DAG is not preserved. For example, if crate A links against path pathA, crate B links against pathB, and B depends on A. Cargo will compile B like:
rustc b/src/lib.rs -L native=pathA -L native=pathB

Instead it should pass pathB first and in general use a topological ordering to ensure that more relevant paths come first.
This was discovered by Servo where a native library was being picked up from /usr/lib even though it was properly compiled into the build directory. The /usr/lib version wouldn't link while the build directory one was the correct one to use.

Awesome, thanks for jumping on this so quickly!


Fix typo for manageResqueMission method and effected comments.

Fixed a typo where Rescue was misspelled Resque on the manageResqueMission method name in Kerbalism.cs by renaming it to manageRescueMission and also its call.
Changed all other misspelled Resque found.

Thanks! This 'resque' typo is the bane of my existence. I don't seem to be able to unlearn it.


Add Wake 0.19 CI tests

In addition to adding a couple of CI tests to actually attempt compiling and generating RTL for the TestSocketDUT, this makes a few other minor changes for Wake 0.19 compatibility:

https://github.com/sifive/soc-testsocket-sifive/commit/133f26d2507493e51bb4ddd4ed5c21c2619482a3 Bumping api-generator-sifive to pull in all the other Wake 0.19 fixes (these should all still be compatible with Wake 0.17.2)
https://github.com/sifive/soc-testsocket-sifive/commit/5a03f284cbc0b5b233ec90b3e533ad6f71fdea50 Renaming an unused argument
https://github.com/sifive/soc-testsocket-sifive/commit/bc440f740013673cd2dff998b273df1808473836 Removing an old shim from when we were trying to straddle Wake 0.15 and Wake 0.17.

LGTM. I'm unsure why we include so many redundant wit dependencies, though. Particularly, because the ones listed here are too old, and are actually being fulfilled due to api-generator-sifive.

See https://github.com/sifive/block-pio-sifive/pull/70#discussion_r421162562 for an earlier discussion about dependencies.

Also:
(warning) Unused function argument 'module' at <api-languages-sifive/node.wake:47:[24-29]>; consider renaming to _module
63
(warning) Unused local definition of 'genSrcs' at <api-scala-sifive/scala.wake:401:[7-13]>; consider removing or renaming to _genSrcs
64
(warning) Unused local definition of 'statedir' at <api-scala-sifive/scala.wake:440:[7-14]>; consider removing or renaming to _statedir
65
(warning) Unused function argument 'resource' at <environment-example-sifive/environment.wake:100:[35-42]>; consider renaming to _resource
66
(warning) Unused function argument 'tail' at <rocket-chip/build.wake:148:[11-14]>; consider renaming to _tail
67
(warning) Unused top-level definition of 'binary /' at <freedom-metal/build.wake:24:9>; consider removing or renaming to _binary /
68
(warning) Unused top-level definition of 'scalacOpts' at <soc-freedom-sifive/wake/build.wake:1:[5-14]>; consider removing or renaming to _scalacOpts

I don't understand why we keep getting this 'resource' warning from environment-example-sifive. We update environment-blockci-sifive 0.7.0 to point at the version with the fix ...

I don't understand why we keep getting this 'resource' warning from environment-example-sifive. We update environment-blockci-sifive 0.7.0 to point at the version with the fix ...

Apparently I messed up and tagged the wrong commit. Just force re-pushed, which hopefully doesn't screw anything up because all of our dependencies on that repo have been on tag name and not commit hash.

You probably did not intend to remove sifive-blocks!

You probably did not intend to remove sifive-blocks!
EDIT: ok, you did.

Only via the argument that fpga-shells and soc-freedom-sifive expose type definitions from sifive-blocks, which is a bit of a judgment call.


problem in building apollo5.0:Cloning ad-rss-lib from github is to slow

When I build apollo 5.0: ./apollo.sh build, it take a lot of time in this step:
Cloning https://github.com/intel/ad-rss-lib: Receiving objects (1479 / 17648)
maybe 2hours later, Build failed,error is:
 /apollo/modules/planning/tasks/rss/BUILD:5:1: no such package '@ad_rss_lib//': Error cloning repository: Premature EOF caused by Premature EOF caused by Premature EOF and referenced by '//modules/planning/tasks/rss:decider_rss'.
May I clone ad-rss-lib by myself?In which path?
System information

OS Platform and Distribution:Linux Ubuntu 14.04:
Apollo installed from source:
Apollo version 5.0:

@BigBenSure could you answer the System information questions above for better understanding?

My system is Win10, and I build apollo 5.0 in docker Version 18.06.1-ce-win73 (19507), yesterday I try to build it again, maybe 1.5hours later , build succeed. But cloning ad-rss-lib is still slowly(I'm in China). So the problem is solved. If we have a faster way to install ad-rss-lib, it could be better.

See PR,Currentlly apollo team seem did not want to update their docker,So,You can install the lib into docker ,commit the docker,modified WORKSPACE.in file from git to local.

Thank you very much!

@gengqx Hello,
May I ask how to install the rss lib into docker and how to commit the docker? Could you elaborate about the process? I also encounter this problem and puzzled me for a long time.

@gengqx Hello,
May I ask how to install the rss lib into docker and how to commit the docker? Could you elaborate about the process? I also encounter this problem and puzzled me for a long time.
Below is the output when execute bash apollo.sh build:
[INFO] Building with --jobs=12 --ram_utilization_factor 80 for x86_64
INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling --host_jvm_args=-XX:-UseParallelGC
ERROR: (04-27 14:44:26.762) /apollo/modules/planning/tasks/deciders/rss_decider/BUILD:21:1: no such package '@ad_rss_lib//': Error cloning repository: Premature EOF caused by Premature EOF caused by Premature EOF and referenced by '//modules/planning/tasks/deciders/rss_decider:rss_decider_test'.
ERROR: (04-27 14:44:26.814) Analysis of target '//modules/planning/tasks/deciders/rss_decider:rss_decider_test' failed; build aborted.
INFO: (04-27 14:44:26.814) Elapsed time: 636.924s
============================
[ERROR] Build failed!
[INFO] Took 637 seconds
============================

我看你资料在北京,国内网络原因,可以改ad rss lib的源.具体方法是:
在/apollo/WORKSPACE.in里,第47到第53,替换成:
#ad-rss-lib
new_git_repository(
    name = "ad_rss_lib",
    build_file = "third_party/rss_lib.BUILD",
    tag = "v1.1.0",
    remote = "https://gitee.com/audier0879/ad-rss-lib",
)

把remote换成gitee的.欢迎补充.

When I build apollo 5.5.0: bash apollo.sh build --local_resources 2048,1.0,1.0. I encounter this problem and puzzled me for a long time.Could you please teach me where I should put the 'ad-rss-lib' file?
Below is the output when execute bash apollo.sh build --local_resources 2048,1.0,1.0:


Hide debug mode

Currently anyone can enter debug mode from the About screen, which is going to be confusing for most people. Instead we want to hide it so that only people who know to look for it will turn it on:

[ ] Hide existing "Debug Mode: off" button
[ ] Tapping three times on the version on the About screen turns on debug mode
[ ] When debug mode is on, show the button to turn it off. It should read "Turn Off Debug Mode"
[ ] Hide the network tool in Release builds. It doesn't really show any secrets that can't be extracted through decompilation but it does make them easier to find

Adding on to this:

[ ]  Make sure the text in the "Turn off debug mode" button on the about screen is Heading4 in all caps, right now it appears to be in camel case.
[ ] All buttons and the header on the debug screen itself should have text in Heading4 in all caps


[WIP] Feature/admin inst

General first pass done :turtle:
Only overall comment is to add tests throughout that would catch the errors you found earlier (confirming that self.primary_institution always returns an Institution, self._primary_institution returns a Node, self.attributed_institutions returns a SpecialList of Institutions, etc.).


Bugfixing exporter mockserver testcases

This PR fixes the following things:

The current VCSA-Exporter return value inconsistencies in the Connection class.
The current VCSA-Exporter regression bug with adding a metric clear after an exporter request.
Removed unused imports
Fixing the logout handling on the testcases. It was tested with a password before, but we need to test it with the sessionID.
Added a sessionID check on the mock server side. We now get correct results.

Please fix conflict

Fixed the consecutive runs test. On Linux it caused some length issues with the output, because much more information is written into the files than on windows systems.  For example 'process_start_time_seconds 1.61667373865e+09'.
Different lengths caused issues in the testcases.
Also increased the sleep time for the Prometheus to 0.2 seconds. Because 0.1 seconds caused very rare occasions where the connection test might have failed.

The consecutive runs fix caused another issue. Because it utilized the process_response_data method, which utilized a set, we weren't able to check against duplicate data. Therefore I implemented a way to see if a set or list is passed to this method. Now we get the correct testresults.


Stuck in Uploading

I have deployed the bot on heroku ,the bot download the file correctly but after renaming it stuck on trying to upload, and the in status its showing two users but i connect only admin

yeah same with me
It showing 502 bad gateway

use laest version of this repo


Feature: Option to not highlight first item in select-choices by default.

This is my use case for this enhancement. We are using ui-select to filter a list of items such as [Status: In Progress] [Type: Estimate], but we also want to be able to use the $select.search text to search over our list of items. So I don't want the first choice selected by default and hitting enter will close the choices and use the entered text as the search.
I created a pull request that will add this functionality. https://github.com/angular-ui/ui-select/pull/803

:+1:

I've created a plunker that shows a basic use case. http://plnkr.co/XfuJozUv5YfFnYHsVnZA
There aren't very many select options so the best way to see what i'm talking about it to type 'state' and hit enter. This closes the choices and uses 'state' as the search. If you want to select state press down then enter.

I think there is a workaround for this issue, by adding a class to the dropdown item that matched the one bound to the select, and use custom css to highlight based on that class
<ui-select-choices
	repeat="item in $ctrl.items"

</ui-select-choices>


Show error when run "train.py" on RTX-3090

Hi,
I run "train.py" on RTX-3090 (24GB) and show message
"OutOfMemoryError: CUDA out of memory. Tried to allocate 172.00 MiB (GPU 0; 23.70
GiB total capacity; 22.87 GiB already allocated; 120.75 MiB free; 22.89 GiB
reserved in total by PyTorch) If reserved memory is >> allocated memory try
setting max_split_size_mb to avoid fragmentation.  See documentation for Memory
Management and PYTORCH_CUDA_ALLOC_CONF".
How I fix it?

Thank, @awaelchli . I change n_layers=20 and n_embd=2048, it work!!!


fix fastparse failure

by simply not running the tests that are failing
reported upstream at https://github.com/lihaoyi/fastparse/issues/73

test run: https://scala-ci.typesafe.com/job/scala-2.11.x-jdk8-integrate-community-build/124/consoleFull

all good (Shapeless failure is unrelated)


How to use tensorboard with custom datasets

Hi.
I want to create a graph using tensorboard with a custom dataset.
However, the tutorial did not show how to create it.
Can you tell me how to do this?
Thanks.

Add your graph data to tb_dict as output of the algorithm and change it here: https://github.com/microsoft/Semi-supervised-learning/blob/067b0f062333f14bf0ca15beb83d785dab7db74d/semilearn/core/hooks/logging.py#L19

I was able to create it!
Thanks very match.


wsl: Nested virtualization is not supported on this machine. -- Then starts anyway

Windows Version
Microsoft Windows [Version 10.0.22621.1555]
WSL Version
WSL version: <IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Debian GNU/Linux 11
Other Software
virt-manager / KVM
Repro Steps
This following only recently started happening.
Launching WSL from within a Windows 11 virtual machine running inside virt-manager on an Ubuntu 20.04 host results in:
"wsl: Nested virtualization is not supported on this machine."
user@DESKTOP-12345 ~$

WSL appears to boot up and work as expected.
Expected Behavior
No message about nested virtualization not being supported should appear, as was the case previously.
Actual Behavior
wsl: Nested virtualization is not supported on this machine.
Then wsl appears to work but the error leads me to be concerned I am not getting virtualization benefits?
Diagnostic Logs
No response

@thebalaa what CPU are you using? And did you enable nested virtualization in KVM? To check if nested virtualization is available on your system for Intel CPUs type cat /sys/module/kvm_intel/parameters/nested and for AMD CPUs type cat /sys/module/kvm_amd/parameters/nested. If the output is 1 you have nested virtualization.

This is just a warning that your processor does not support the processor feature required for running nested VMs.

@benhillis sorry for not being more clear.
My processor is a Ryzen 5950X which, to the best of my understanding, does support nested virtualization. The motivation for this ticket was that this message appears on a system where it was previously not appearing. The system or VM hadn't even been restarted.


Bulk upload of taxon names doesn't preserve all names in "Verbatim" Author field

Describe the bug
When I upload a bulk TSV of Taxon names with Authors, the verbatim authors are not preserved if author is not in parentheses or if there are multiple authors
To Reproduce
Steps to reproduce the behavior:

When I upload a TSV list of taxon names and associated authors.
Then I go to edit one of the created taxon names.
And those authors are not in parentheses or there are multiple authors not in parentheses.
Nothing is created in the "Authors" "Verbatim" field except for year.

Original TSV:

Resulting name in Verbatim Author section in "Edit Taxon Names" - one author

Resulting name in Verbatim Author section in "Edit Taxon Names" - multiple authors

Expected behavior
Author names should be verbatim parsed from original TSV to that field to save time
Environment (please identify where you experience this bug:

Production
Chrome

This is currently expected behaviour.  When People are creatable and can represent the full name, then verbatim name is not stored.  When parens are required we store verbatim to over-ride people.

I like and don't like this. Is there harm in storing it anyway?

I understand I think. The verbatim_author field overrides calculable values, it's not really what you think of as "value that I started with when I imported", a subtly different concept.  Storing it, when representation is not in doubt, defeats the purpose in many ways.  Taxonomists need to give up the past in some ways ;).

Fair enough. I'm okay with this, now that I know Source and People linkages are connected more.


Very slow responses to rtags commands

I have rtags and vim-rtags installed on my Ubuntu 18.10.
When I issue a rtags mapping in vim, like <leader>rj, called function appears immediately in vim command line like this :call rtags#JumpTo(g:SAME_WINDOW).
I also see the command appearing immediately in rdm logs: rc --absolute-path -f /home/przemek/path/to/file.cpp:375:18
If I issue the same command in terminal instead of vim, I get the answer immidiately.
However in vim I have to wait ages for the result. I'm not even sure if it's always successful, or I need to wait longer.
Funny thing, this issue sometimes appear and after sometime it works normally again. I don't have any heavy cpu load. Can this be a issue in connection to rdm? Maybe some other process is interfering with it?

I have seen this in the past also and wondered if there was possibly a race with obtaining vim channel output.
I think I improved it somewhat in my fork of vim-rtags - but it really should be re-visited.


Exporting cifmw_openshift_login_skip_tls_verify as global

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/lgtm
while it's not using the usual pattern we have with top-level parameters and default, it will work as is.

/approve
/lgtm
better that way :).

tempest issue, unrelated to the change. We need it for the new layout, in order to get an easier way to disable TLS check (until we inject CRC CA in the systems, at least).


Refactor FullyQualifiedAuthority::normalize to always return authority

As requested by @briansmith in https://github.com/runconduit/conduit/issues/415#issuecomment-369026560 and https://github.com/runconduit/conduit/issues/415#issuecomment-369032059, I've refactored FullyQualifiedAuthority::normalize to always return a FullyQualifiedAuthority, along with a boolean value indicating whether or not the Destination service should be used for that authority.
This is in contrast to returning an Option<FullyQualifiedAuthority> where None indicated that the Destination service should not be used, which is what this function did previously.
This is required for further progress on #415.

I'm not sure why this PR's CI build has been in the "Waiting for status to be reported" state for over an hour --- I suspect Travis is misbehaving?

The travis web UI claims that this branch built successfully, so I think GitHub just failed to receive the success notification or something.
I can't merge this branch without a CI success, but maybe @olix0r or someone else with admin access can?

The travis web UI claims that this branch built successfully, so I think GitHub just failed to receive the success notification or something.
I can't merge this branch without a CI success, but maybe @olix0r or someone else with admin access can?

I've had the same issue before:
git commit -s -m "kick CI." --allow-empty && git push
(There are probably typos there, but you get the idea.)

Thanks Brian, hopefully it will behave this time...

I restarted the most recent build of this branch, as the failure was on the web build job. Since there were no web changes, I suspect the failure was spurious.


Non-minified build is minified

Since js-ipfs-api 24.0.1
<EMAIL_ADDRESS>compare with:
<EMAIL_ADDRESS>

Which version of aegir are you on? Should have been fixed in v15.3.0.


Each call to database() on a connection creates its own cache

I was quite surprised to find that I was getting document conflicts with myself.  It turned out that each call to conn.database("x") creates a new cache for objects from that database so you can save an object in one place but you will get a stale object back from another.
My workaround was to monkey-patch the database method so it returns the same database instance on subsequent calls.  Perhaps the core code should do that as well?
However, I noticed that the cache will become problematic in the long term because there's no synchronization nor does the cache expire old entries.  If I were to have multiple processes (say 2 servers or one server and one batch cron job) then I will risk conflicts.
Is the cache basically only suitable for use in single-process deployments?

You would need to write your own cache consistency algorithm for multi-process synchronization.
Would love to see a pull-request for this: cache consistency is hard.

Hmm probably something to think about.
One approach that comes to mind would be to dump all cached objects that are idle for one tick.  This gives a caching benefit when you're getting some stuff and immediately updating it in the same operation but doesn't introduce enough of a cache lifetime that your data will be "too old".
Another approach would be to subscribe to changes to the databases and evict objects that couchdb tells you have changed.  This would potentially add a lot of unnecessary network traffic, though.
Perhaps setting cache:false is the safest approach, I don't think any of the other Couch clients are adding a cache, probably for this very reason.

:+1: ref: #225 #258


Error messages is confusing when accessing a property as function

see http://plnkr.co/edit/60r4KhJQRTMZrXYGohc6?p=preview
When running this, the console shows an error:
TypeError: Cannot read property '0' of null
This happens because $scope.items is an array, but ng-repeat="item in items()". It is hard to find out what ng-repeat causes this and why.
The best error would be "items is not a function in expression 'item in items()'"

Thank you for posting this issue and I am sorry that it is difficult to track down bugs in templates like this. The problem we have right now is that by the time the expression is executed we have lost track of the original ng-repeat expression.
But what we could do, inside ensureSafeFunction is to check whether the obj really is a function or not and then use the fullExpression value, which would be "items()" in this case, to throw a better exception.
@lgalfaso and @IgorMinar - what do you think of that? I don't think it would have a huge impact on performance but it is certainly not going to make it any faster!

Here is an example: http://plnkr.co/edit/p4yOWxj2fm5SDMpCYnGR?p=preview

@petebacondarwin I agree that a nicer message would be helpful, but I am not sure that start adding not security checks to ensureSafe* functions is best.
I think the best would be to add a property debugInfoEnabled to ParseProvider (that is false by default) and when this is true we would wrap ensureSafeFunction to also check that what is provided is really a function

This now throws "v2.items is not a function" which is better, but still not perfect. It's also a duplicate of https://github.com/angular/angular.js/issues/14072 now


[BUG] Client sink closes after adding a keepalive value

The client sink shuts shown after sending the first keepalive ping. Notice the logs where mqtt client connection is closed.
#[ntex::main]
async fn main() -> std::io::Result<()> {
    std::env::set_var("RUST_LOG", "ntex=trace,ntex_mqtt=trace,client=trace");
    env_logger::init();

    // connect to server
    let client = client::MqttConnector::new("<IP_ADDRESS>:1883")
        .client_id("user")
        // [BUG] adding a keep a keep alive timeout causes the client to close
        // after first ping
        .keep_alive(1)
        .connect()
        .await
        .unwrap();

    let sink = client.sink();

    let router = client.resource("response", publish_v5);

    ntex::rt::spawn(router.start_default());

    let expire = RtInstant::from_std(
                        Instant::now() + Duration::from_secs(1000));
    delay_until(expire).await;

    sink.close();
    Ok(())
}

Logs:
2021-01-13T00:54:37Z TRACE ntex_codec::framed] attempting to decode a frame
[2021-01-13T00:54:37Z DEBUG ntex_mqtt::v5::client::connection] start mqtt client keep-alive task 1
[2021-01-13T00:54:38Z TRACE ntex_mqtt::v5::client::connection] send ping
[2021-01-13T00:54:38Z TRACE ntex_mqtt::framed] FLUSH and Stop state
[2021-01-13T00:54:38Z TRACE ntex_codec::framed] flushing framed transport
[2021-01-13T00:54:38Z TRACE ntex_mqtt::framed] ready
[2021-01-13T00:54:38Z TRACE ntex_mqtt::framed] Framed flushed, shutdown
[2021-01-13T00:54:38Z TRACE ntex_codec::framed] framed transport flushed and closed
[2021-01-13T00:54:39Z TRACE ntex_mqtt::v5::client::connection] send ping
**[2021-01-13T00:54:39Z DEBUG ntex_mqtt::v5::client::connection] mqtt client connection is closed, stopping keep-alive task**

this is not a bug. I guess you use default mqtt5 server, but default it uses "DefaultControlService" as a control plain service, and it did not support ping messages, so server closes connection after first pin.
I released 0.4.7 which add ping and disconnect support to mqtt5 default support service.

this is not a bug. I guess you use default mqtt5 server, but default it uses "DefaultControlService" as a control plain service, and it did not support ping messages, so server closes connection after first pin.
I released 0.4.7 which add ping and disconnect support to mqtt5 default support service.

this is not a bug. I guess you use default mqtt5 server, but default it uses "DefaultControlService" as a control plain service, and it did not support ping messages, so server closes connection after first pin.
I released 0.4.7 which add ping and disconnect support to mqtt5 default support service.

this is not a bug. I guess you use default mqtt5 server, but default it uses "DefaultControlService" as a control plain service, and it did not support ping messages, so server closes connection after first pin.
I released 0.4.7 which add ping and disconnect support to mqtt5 default support service.

@fafhrd91 Thank you for promptly looking into that. Actually the bug is in version 0.3.17 (which I was depending on earlier). I updated to 0.4.7 latest version and it is solved now.
It was not because of using the "DefaultControlService", I have my own control service on the server side that responds to clients pings (and works fine with other clients).
Thanks again for looking into it.

@fafhrd91 Thank you for promptly looking into that. Actually the bug is in version 0.3.17 (which I was depending on earlier). I updated to 0.4.7 latest version and it is solved now.
It was not because of using the "DefaultControlService", I have my own control service on the server side that responds to clients pings (and works fine with other clients).
Thanks again for looking into it.


nested object query params

im currently using https://spatie.be/docs/laravel-query-builder , it would be nice if it support something like this http://site.test/admin/users?filter[id]=1&filter[ref]=31"
my workaround:
filter.forEach((filterValue, index) => {
    filterString = filterString + `&filter[${filterValue[0]}]=${filterValue[1]}`
})

this.$inertia.replace(this.route(
    'users.index',
    {
        q: query,
    }
) + filterString)

nevermind, got it route('users.index', {_query: {filter: {id: 'test', haha:'asda', awesome: 'asdad'}}}) haha

I have tried to use the route().current('users.index', {_query: {filter: {id: 'test', haha:'asda', awesome: 'asdad'}}}) and it does not work for me

@DevMakoto you're calling route().current(...), the example in this issue is just route(...).

@bakerkretzmar What I want is to check if it is in said route with those parameters, but it doesn't work

What exact code are you calling, what is the full exact URL of the page at that moment, and what result are you getting/expecting?


ngclient: simplify storing a downloaded file

Fixes #1761
Description of the changes being introduced by the pull request:
Replace the usage of securesystemslib.util.persist_temp_file() with
shutil.copyfileobj() as file system abstraction is not used in the
client.
This way we prevent securesystemslib.exception.StorageError from
leaking through client API calls.
Note: with those changes, we are no longer do fsync.
Signed-off-by: Martin Vrachev<EMAIL_ADDRESS>Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 97.693%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
4088

Relevant Lines:
4169

💛  - Coveralls

@jku I updated pr, so it changes the exceptions docstring inside updater.download_target().
Additionally, I made it dependent on https://github.com/theupdateframework/python-tuf/pull/1787 to make sure we end up with the correct exception docstring for updater.download_target().


Whether we can save OnDateSetListener

Premise: do not keep the application.
In use, A click on the button with out DatePickerDialog, click home, click confirm  doesn't work again
The reason: mCallBack == null
I find the most used DialogFragment lot, found that everyone is all about, I want to know whether we can save Listener , Or not working is the right design.

This behavior is detailed in the FAQ:
https://github.com/wdullaer/MaterialDateTimePicker#why-are-my-callbacks-lost-when-the-device-changes-orientation


Remove deprecated ability to set DynamoDB table name via URL

Follow-up from #357

Should we log a warning if launched with non-empty path?

Probably a good idea. Are you OK for me to merge after that or would you like another review after that? (Roundtrips are expensive)

Oh yeah for sure. LGTM.
On Mon, 27 Mar 2017 at 10:03, Jonathan Lange<EMAIL_ADDRESS>wrote:

Probably a good idea. Are you OK for me to merge after that or would you
like another review after that? (Roundtrips are expensive)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/cortex/pull/370#issuecomment-289381722,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbGhaXRvA7Dx9TcoumPZ5_5YgI0L5Beks5rp21WgaJpZM4MoVPy
.


dropped the php-coveralls requirement; updated the version of codecli…

…mate
(addresses #2 )

this brought in php-coveralls 1.0.0, but I'd like another person for confirm whether this resolves the issue

1 nitpick change, Since they're slow moving on versioning (0.1, 0.2, 0.3.x, etc) lets not use:
"codeclimate/php-test-reporter": "~0", and instead be specific "codeclimate/php-test-reporter": "~0.3", just incase they go ham with updates.

I just noticed that technically this doesn't get us away from the abandoned guzzle/guzzle reference.
local: phergie-irc-bot-react-development $ composer update Loading composer repositories with package information Updating dependencies (including require-dev) Nothing to install or update Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead. Writing lock file Generating autoload files

@svpernova09 ready for review, but i don't think this closes the issue.

We needed these changes but you were right, this doesn't solve the Guzzle version problem. We have to wait for satooshi/php-coveralls to tag a new release. It's fixed in master, but not in a tagged release.


the SL-GCN motion-related data prediction acc very low ?

I download your code and barely not change anything. But the SL-GCN can't recognize the joint-motion and bone-motion very well. below are my result use the train_joint_motion.yaml and train_bone_motion.yaml:

below yaml file I just change the data_path and label_path, and not change other things! If possible, do you know why this result is?
Experiment_name: sign_joint_motion_final_NEU_data

# feeder
feeder: feeders.feeder.Feeder
train_feeder_args:
  data_path: ../../../Datas/TAUSL/AUTSL/skeleton/val_data_joint_motion.npy
  label_path: ../../../Datas/TAUSL/AUTSL/skeleton/val_gt.pkl
  debug: False
  random_choose: True
  random_shift: True
  window_size: 100
  random_mirror: True
  random_mirror_p: 0.5
  normalization: True
  is_vector: True

test_feeder_args:
  data_path: ./data/sign/27_2/train_data_joint_motion.npy
  label_path: ../../../Datas/TAUSL/AUTSL/skeleton/train_label.pkl
  random_mirror: False
  normalization: True
  is_vector: True

# model
model: model.decouple_gcn_attn.Model
model_args:
  num_class: 226
  num_point: 27
  num_person: 1
  graph: graph.sign_27.Graph
  groups: 16
  block_size: 41
  graph_args:
    labeling_mode: 'spatial'

#optim
weight_decay: 0.0001
base_lr: 0.1
step: [150, 200]

# training
device: [0,1]
keep_rate: 0.9
only_train_epoch: 1
batch_size: 64
test_batch_size: 64
num_epoch: 250
nesterov: True
warm_up_epoch: 20

I'm so sorry. After I use your provided traindata in SAMv2 link, the acc of joint_motino and bone_motion could reach to 90+%. I still don't know why, but sorry again to bother you!


Merge accounts with redirect style

Apparently, this approach does not work with loginWithExternalService in redirect style. The reason is that callback function cannot be serialised and then called once users are redirected back to the original application.
As suggested in the documentation, onLogin hook should be used.
(Anyway thanks for this package)

Added support for redirect style https://github.com/lirbank/meteor-accounts-merge/pull/31


Use TreeNodeChoiceField to render category field

Fixes #1887
Using TreeNodeChoiceField to render Category selection nests the subcategories without making any additional queries. This solution is satisfying for now and we can come up with a better-looking solution once we rewrite this view in React.

Pull Request Checklist

[x] Privileged views and APIs are guarded by proper permission checks.
[x] All visible strings are translated with proper context.
[x] All data-formatting is locale-aware (dates, numbers, and so on).
[x] Database queries are optimized and the number of queries is constant.
[x] The changes are tested.
[x] The code is documented (docstrings, project documentation).
[x] Python code quality checks pass: pycodestyle, pydocstyle, pylint.
[x] JavaScript code quality checks pass: eslint.

Do we have any reason for defining Meta: before fields?

@rafalp No idea about that.

@rafalp If you think this is something we should tackle, please open an issue. It's unrelated to this PR.


Store owner packages

Nix/Guix do not allow packages to contain things like:

Private files.
Device nodes.
Setuid binaries.

They do this to enable 'purity' in builds, and may be a worthy goal, but in some situations it can be a pain:

You cannot deploy secrets as packages, they would be public without additional encryption.
Normally in Nixos, I work around this by storing a master key in a root owned folder.
You need a "launcher" script to install setuid links and other OS related files at boot. Nixos does this via it's activation script run by nixos-switch.

It is worth considering if we can relax this restriction for packages submitted by the store owner (root for system owned package). The way it would work is that packages submitted by the store owner, can apply post processing that is run in the context of the store owner.
During post processing, things like device nodes, permission bits etc can be changed to values that are not allowed by the typical build user.

Holding back on this feature until we get a clear idea what is needed for our hermes OS distribution.

There are some security considerations that may be blockers of this feature:

If gc roots installed by other users can keep a privileged package alive, this creates a vulnerability as they can prevent upgrades from removing vulnerable setuid programs.


Add command to view changes since previous release for a package in a monorepo

If the user runs this command from within a monorepo:
yarn create-release-branch log @metamask/controller-utils

then it should show a list of commits that have taken place between HEAD and the given package's previous release (going off of the Git tags). This command should be a proxy over git log, so the user should be able to pass arbitrary arguments to this command they would usually be able to pass to git log.
Similarly, if the user runs
yarn create-release-branch diff @metamask/controller-utils

then it should show a commits with changes that have taken place between HEAD and the given package's previous release (going off of the Git tags). This command should be a proxy over git diff, so the user should be able to pass arbitrary arguments to this command they would usually be able to pass to git log.
(I realize that it may be strange to pass commands to a tool that supposedly creates a release branch, but I'm considering renaming this tool to indicate that it can be used to manage releases and not just create them. That's a different ticket, though.)

Hey team! Please add your planning poker estimate with Zenhub @cryptodev-2s @Gudahtt @MajorLift @mcmire @mikesposito


Stream Support

Close #9

Current version non-streaming requests do not go swich default
Maybe try
type Streamble[T any] interface {
	Stream() <-chan T
}
	v, ok := (response).(Streamble[any])
	if ok {
		if v.Stream() != nil {
			go handle(v.Stream(), httpres.Body)
			return nil
		}
	}
	return decode(response, httpres.Body)

Using a channel instead of a callback will cause the code to block, and if no one receives the channel then the function will block internally.

Handles errors, sometimes returning "Invalid character 'd' looking for the beginning of the value"


ueforth-compatible developer board with audio?

Do you know if there's an ESP32 developer board with audio hardware that will run ueforth?

I've found a couple of them - pretty much every ESP32-S3 board I've found has I2S audio, which reduces this to wiring up DACs/ADCs and amplifiers / microphones. I've got a couple of M5Stack Cardputers and ueforth runs fine on them. I'm closing this.


[WIP] Add API's for additional world management operations

This pull request introduces an API where worlds that exist can be copied and loaded as a new world with a different name.
This pretty much needs an API because of the uuid added for Sponge's worlds. Fixing this would require plugins to copy the world, then load up the NBT and change the name, dimension id and UUID in the file manually, which is prone to breaking and also likely impossible, because plugins shouldn't have access to a way to get the next open dimension ID.
Solves https://github.com/SpongePowered/SpongeAPI/issues/750
Feature list:

[X] Support the ability to copy an existing world and load it as a duplicate with the same name.
[X] Support the ability to get the world directory from the API to allow plugins to store data with the worlds.
[X]  Add ability to delete existing worlds from the disk (after being unloaded first)
[ ] Add the ability to fully rename an existing world, including folder or other stored name.

Todo:

[X] Determine if world copying should only be allowed after unloading a world (It should)

Todo: Determine if world copying should only be allowed after unloading a world

I was doing something like this to account for a bug in Multiverse's clone code (that was before I had a GitHub account, so I just copied and changed it). It's easier to implement if the world does need to be unloaded, as you can simply copy the directory, but it's annoying to users who are in the world.

I found that the copy works even if the world isn't unloaded but I don't
know how safe that is

Do you at least lock saving first?

No. That will definitely be changing, the implementation is in the linked
SpongeCommon PR if you wish to look. That code worked for me, but I didn't
have modification happening during the copy in my testing so I'm pretty
sure that will break.
The only proper way I know to lock saving would be to have the world
unloaded which makes more sense to me anyway.

Will there be a way to clone the world without loading it immediately afterwards? (To have a chance to modify the WorldProperties before the new world is loaded, e.g. making the spawn area not be loaded when the world is.)

Yes the copy will be an optional WorldProperties, the optional World
was before I realized that it could be split.

I have no actual clue, but how fast is the copying of (large) worlds usually? Will this be a problem if done on the server's main thread? If yes, would it make sense to run the file io in a separate thread and let the caller provider some sort of callback, which gets called once the world has been finished copied and loaded?

An asynchronous copy might be a good idea. @SpongePowered/Developers
comments?

Yes I think an asynchronous call would be a good idea. It would return a ListenableFuture.
I think you'd need to be careful in the implementation that you can't attempt to load the world before the thread has finished execution. Possibly introduce a lock to ensure nothing can touch the world while it's copying.

I do like an asynchronous load and copy. I did something like this for a Bukkit minigame plugin. When the world loaded (WorldInitEvent), I would set keepSpawnLoaded to false, use a repeating task to load each chunk, and set keepSpawnLoaded to true. ListenableFuture seems good, though it would be nice to have a way to listen for load progress (e.g. 42%).

Should we allow access to the execution context, or provide some ListenableFutures that already have the execution context defined? I could see one that executes the callback at the next possible synchronous moment using the scheduler if created on the main thread, or an asynchronous context being created if created by an asynchronous task.
It's probably overcomplicating things for people who know what they are doing, but doing magic for beginners.

One problem with asynchronous chunk loading: the ChunkLoadEvent would have to be fired - and probably waited for - on the main thread.

Also, maybe events for world copying, deleting, and renaming ought to be good (so plugins can copy, delete, and rename their data).

Same as API, the code for the import and change of worlds that are cold (haven't been loaded at any point, fresh out of a compressed archive), will be moved into a separate, easier to complete PR.

OMG SOLID GOLD
Thats what this is

Any updates with this?

Will be trying to wrap up by the end of this week. If not done by then I'll
need to push it to someone else as I'll be too busy with school and work
for awhile.

I will be unable to handle proper implementation of this, I should be able to finish API tomorrow.


PrioritizeButton

Complete the story at stories/components/buttons/PrioritizeButton.stories.tsx

Hey @Neuroplastic1 I’m using Zenhub in GitHub, click this link to join my workspace and see other features available in GitHub or download the Zenhub extension and sign up with your GitHub account.
Posted using Zenhub


ng add @clr/angular@next fails with Angular9

Describe the bug
ng add @clr/angular@next

fails on a fresh new Angual9 project
How to reproduce
Steps to reproduce the behavior:

Create a new Angular9 project with ng add my-project
Add clarity 3 next with ng add @clr/angular@next

I get this error
An unhandled exception occurred: Collection "@clr/angular" cannot be resolved.
See "/private/var/folders/xv/8mqxb9qx61bbj7bvxgdv9vmm0000gq/T/ng-II6mmk/angular-errors.log" for further details.

angular-errors.log
Expected behavior
Everything goes well
Versions
App

Angular: 9.0.1
Angular CLI: 9.0.2
Node: 10.13.0
Clarity: 3.0@next0

Device:

Type: MacBook
OS: macOS

This is a known issue due to a publishing error, it will be resolved in the next release. Essentially the schematics weren't published with the package.

Fixed by #4262. Will be fixed in next release.


Add vscode settings + format on commit

What changes did you make?
Added vscode settings for autoformatting code on save. Added pre-commit/husky setup to run prettier formatter on commit. This should be working as a pre-commit action but husky is adding the changes after the commit is pushed. This means a second commit can then be pushed for lint changes.
Why did you make the changes?
To keep code formatting in sync

Nice @annarhughes!
Two things:

Can you add documentation for how this works in the README? No worries about perfect phrasing & formatting, a basic explanation is fine. I'll edit after.
You mentioned this requiring VSCode. Can we document how these settings could be removed for use with other IDEs? VSCode is by far the most popular, but I'd be concerned about excluding Jetbrains which is the second leading IDE.

@kyleecodes I've added notes to the readme now! Ah and it's not that VSCode is required for this to work, it's that we have extra settings/automation for formatting and linting on VSCode. Developers using alternative IDE's should be able to replicate or follow the settings on their IDE


Image: v1.21.0-k3s1 fails when running in a container

Environmental Info:
K3s Version:
k3s version v1.21.0+k3s1 (2705431d)
go version go1.16.2
via k3d v4.4.3
Node(s) CPU architecture, OS, and Version:
OpenSUSE Tumbleweed
Cluster Configuration:
Single-Node cluster using k3d cluster create
Describe the bug:
Containerd fails to create containers
failed to create containerd task: OCI runtime create failed: container_linux.go:380:
          starting container process caused: apply caps: operation not permitted:
          unknown

References

First catched by @ibuildthecloud
Similar issue in kind: https://github.com/kubernetes-sigs/kind/issues/2058

underlying problem fixed in containerd by @AkihiroSuda: https://github.com/containerd/containerd/pull/5017 (released in v1.5.0-beta.2)
fixed in kind by updating the deps: https://github.com/kubernetes-sigs/kind/pull/2084

I guess this would require an update of https://github.com/k3s-io/containerd in the end :thinking:
@AkihiroSuda do you have some more input on this issue maybe?

Assigned to @iwilltry42 for checking if this is resolved in k3s 1.21.1 - if so please close this issue.

@davidnuzik , I just gave it a try on that same test system without any issues :+1:
Thanks for the fix guys!


Change publish to take metadata fields as arguments, docstring change

Changes partially taken from db refactor branch
https://github.com/lbryio/lbry/pull/505/commits/491fba5b36abe394e1437ca7f74ad7481c27fe2a
jsonrpc_publish can now take metadata fields as arguments
Change and make docstring more informative
Move add_fee_to_metadata() function from Publisher class to jsonrpc_publish() so that its consistent with how other metdata fields are handled.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

          1 Message

:book:
See http://keepachangelog.com/en/0.3.0/ for details on good changelog guidelines

  Generated by :no_entry_sign: Danger


error 0x800705b4

It works with User Driven Mode, but with white gloves, the first phase of protection hardware will fail 0x800705b4.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ca5b57d1-61b3-39d4-34ff-d6dcb858c250
Version Independent ID: 42609104-815f-9e7a-39aa-38d92cc910c9
Content: Windows Autopilot for white glove deployment
Content Source: windows/deployment/windows-autopilot/white-glove.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

There could be a lot of things going wrong there. You could be missing patches in your image. It could be the time of your BIOS is set off by 5 minutes. See https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/known-issues for known issues.
If you want to know more about TPM attestation, you may visit https://oofhours.com/2019/07/09/tpm-attestation-what-can-possibly-go-wrong/

Hi all,
I have the same issue as "mMDG0Oowa-3TPkpg7JOmdx4ff4IfPvyCGSAHbnh".
We are using Windows 10 version 1909. When using the white glove approach we are presented with the same error message: 0x800705b4. After a simple restart en retry it simply works. this behavior seems inconsistent, sometimes it just works correctly from the first try. We would be really happy to get this resolved. Is anyone else experiencing this issue at the moment?
Or maybe you've experienced it in the past and you could let us know how this got resolved?
I've been scrolling through the Internet for a while now... :)
Regards,

Devices in some areas may have problems with TPM chips, But it'll be resolved later.

Hi all,
I get this error with a compatible laptop, proper TPM and correct time sync settings.
Solution for me was: the TPM Certification checker sites MUST be reachable from the laptop on the network.
Intel- https://ekop.intel.com/ekcertservice
Qualcomm- https://ekcert.spserv.microsoft.com/EKCertificate/GetEKCertificate/v1
AMD- https://ftpm.amd.com/pki/aia
Infineon- https://pki.infineon.com
Check this.
Zsolt

It seems that the question has been answered by the community,  and thus the issue is being marked as resolved.
Please note that the issues section of the repository is intended for corrections in technical documentation.
Should you need to ask a similar question again, consider asking the question via the Windows 10 Support channel.
Thank you.

I've added a link to the networking requirements section pertinent to white glove and self-deploying mode into the articles for these scenarios. Hopefully this will help.


limitations

I will like to know the limitations of this setup. can it support 0365 like okta, goddady and adfs

SAME!


Right click on desktop to open menu

Discussed in https://github.com/Schneegans/Fly-Pie/discussions/274

Originally posted by abUwUser March 19, 2023
Instead of relying on a key combination or Super + RClick, right clicking the desktop could bring the menu. On pure GNOME, that is, without extensions, the right click menu is with not much of a use, only having options related to display and wallpapaer, so adding Rclick functionality in there would be very appreciated

Flypie is a launcher being used with a mouse.  This is very annoying. I would like to use it with mouse-actions, however how does one start fly-pie from a command-line?

Here's the corresponding documentation: https://github.com/Schneegans/Fly-Pie/blob/main/docs/dbus-interface.md


Add ability to move forward or backward by 1 month instead of 2

If I want to select a range across May and June, it is not possible for me to see both months at the same time which can be tricky for a user.
Airbnb's date range picker is an example of a date range picker that moves 1 month at a time.

v1.3.0
Added new option: moveByOneMonth.
https://jsfiddle.net/6x58y92e/


Propagate static_labels from target collectors config to metrics to enable re-use of query config across fleet of identical but unique server DSN's

This is a usability feature req, more than anything, but enables the use of this at scale across immense fleets without needless duplication of config entries.
In the following scenario, having the ability to propagate a static_label from the target collectors config to the metrics utilized as an inherited label would be amazing. Granted you can't technically label the target, but the metrics should not have to be uniquely configured for each and every unique DSN in a unique metric collector config when they are identical in every way except for label. Adding the ability to specify a static label at the target/collector would enable clean and reproducible filtering of targets in queries and dashboards without having unnecessary duplicative metric collector configs.
In our deployment scenario, we have no static collector hosts, and all scrapers are serverless hosts with dynamic DNS/Host names dynamically registered to Prometheus.
Scenario:

multiple db servers with identical databases, all uniquely identified by by a static cluster identifier
all db servers require the same monitoring queries, only difference between each db server / cluster is the label.

Problem:

Currently you have to create a UNIQUE metric config file for EACH and EVERY individual DSN to get UNIQUE labels on them to enable you to filter in prometheus per UNIQUE ID without breaking queries, dashboards, and alerts every time the scraper cycles.
In our case, each db server has a remote sql_exporter scraper running in an ephemeral docker container with dynamic names and addresses. The addresses are dynamically registered to SRV and picked up by prometheus when the container cycles to ensure monitoring continuity on redeploy updates of the container and container hardware failure / lifecycle.

Result:

1000's of individual config metric templates each only differing with dozens of unique labels identifying the DSN/server/cluster they are associated with.
1000's of metric configurations only different by a cluster_identifier label (this seems needlessly duplicative, and if propagated from target, would enable re-use of metric config's across all servers of similar persuasion

Preferred Result:

1 config per DSN
1 shared config for all DSN's propagating the DSN's unique label / identifier specified in the DSN config
Eliminates needless config duplication, and minimizes chance of accidental config drift when adding, removing, and updating monitoring queries across thousands of sql_exporter containers since all config's are identical save for the DSN
Makes templating of the config generation far less painful and needlessly duplicative
Perhaps this identifier label could be applied to the collector_files/collector_names to minimize duplication?

Current State Example:

unique-server-id.yml

global:
  scrape_timeout: 5m
  # Subtracted from Prometheus' scrape_timeout to give us some headroom and prevent Prometheus from timing out first.
  scrape_timeout_offset: 500ms
  # Minimum interval between collector runs: by default (0s) collectors are executed on every scrape.
  min_interval: 30s
  # Maximum number of open connections to any one target. Metric queries will run concurrently on multiple connections,
  # as will concurrent scrapes.
  max_connections: 3
  # Maximum number of idle connections to any one target. Unless you use very long collection intervals, this should
  # always be the same as max_connections.
  max_idle_connections: 3

# The target to monitor and the collectors to execute on it.
target:
  data_source_name: "postgres://secret_monitoring_user:SuperSecreteMonitoringPasswordHere@unique-server-id.fqdn.tld:5439/unique_identifier?sslmode=require"
  collectors: [unique-server-id]

# Collector files specifies a list of globs. One collector definition is read from each matching file.
collector_files:
  - "unique-server-id.collector.yml"

(Example with only 1 instead of dozens metrics for clarity and brevity. Primary problem lies in requiring a static_label per metric_name, when the static_label is really just a static label for the DSN to enable metric filtering based on that static label)

"unique-server-id.collector.yml"

metrics:
  - metric_name: prefix_something_nothing_age_seconds
    static_labels:
      cluster_identifier: unique-server-id
    type: gauge
    help: "Age in seconds of something from nothing"
    values: [age_seconds]
    query: |
      SELECT datediff(s, timestamp, getdate()) AS age_seconds FROM something.nothing ORDER BY timestamp DESC limit 1;

Why not apply the "static label per DSN" in the Prometheus config? Something like this:
scrape_configs:
  - job_name: 'somedb'
    static_configs:
      - targets: [ 'instance1.cluster13.foo.org:9399', 'instance2.cluster13.foo.org:9399' ]
        labels:
            cluster_identifier: cluster13

This also works with file_sd_config, but you have to place the labels in the targets file, next to the targets themselves (i.e. the part after static_configs above all goes into the targets file).
Or, if you're using some other form of service discovery (e.g. kubernetes_sd_config), you can use metric_relabel_configs to create a cluster_identifier label out of e.g. the instance name. It's all documented here: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config
Or, if you don\t use static-configs

True, dns_sd_config just gets messy with the regex, and we don't necessarily name the scraper running the same as the cluster_identifier as they aren't running on the same hosts.
That is certainly a valid idea, however we also have other labels we want to add that don't belong in the DNS like customer_name, customer_id, etc... so it still gets super messy trying to do it in the prometheus config (also we want this to be dynamic).
Long term we'll have to replace the service discovery with Consul to be able to do this OOB tagging without having to muck with automating hundreds of duplicative file templates that have to be pulled down at container start to bootstrap the config.
I guess, the min-maxer in me just wants to see the labels created once with the DSN instead of dozens of times per file alongside the DSN in the query target config since you can't have more than one server per config anyways.


iOS memory leak on touch input

Godot version
3.5 stable, 3.5.1 RC2
System information
macOS, iOS
Issue description
On iOS, touch input causes memory to leak, even in an empty scene with just a Node2D root (tested on iPhone 6s and 2020 iPhone SE). The leak seems to occur specifically on touch begin (not hold/release), and repeated multitouch tapping will increase the memory use by several MB within a few minutes. This also seems to degrade the FPS more and more as tapping continues.
Seems the leak was introduced back in 3.2.3 (it's not present in 3.2.2) - perhaps by #40723 somehow?
Steps to reproduce
Open a fresh project with an empty test scene, export and run on iOS from Xcode. Repeatedly tap the screen (quite a lot), and Xcode should show the app's memory usage increasing permanently.
Minimal reproduction project
any project should do

CC @godotengine/ios

Related to https://github.com/godotengine/godot/issues/32139.

Tried running Instruments leak tool for the empty scene - I'm tapping throughout this video and we can see memory increase, but no leaks are detected.
(this is Godot 3.5)
https://user-images.githubusercontent.com/33777501/193625959-1994e023-31a1-4d1f-ad13-861307be2c6f.mov

The leak occurs in the gesture recognizer due to an incomplete implementation. Per the docs, part of their requirement is:

Subclasses must set the state property to the appropriate value when they transition between states.

and

Subclasses must also periodically reset the state property

It appears that recognizers need an "end" state in order to purge accumulated touch events.
I experimented by replacing this gesture recognizer with a vanilla UIGestureRecognizer, which doesn't adhere to the above, and it reproduces the memory leak.
Furthermore, I placed a state = UIGestureRecognizerStateEnded at a seemingly logical spot in the current implementation and while it resolved the leak it caused runtime assertions in GodotView. The existing logic in the view requires side effects of this unending gesture recognizer state.
This said: I believe using a gesture for ALL touch input is inappropriate. Sending the raw touch events from the view to Godot suffices and is a simpler implementation. This also removes the need for the special cased delay that exists for the iOS platform.
I have a branches for 3.x and master available for review.


Support GNU environment variable TERM in Windows

Description of the new feature/enhancement

From https://www.gnu.org/software/gettext/manual/html_node/The-TERM-variable.html:

The environment variable TERM contains a identifier for the text window’s capabilities. You can get a detailed list of these capabilities by using the infocmp command, using man 5 terminfo as a reference.

Defining this environment variable on Windows will allow all terminal emulators on Windows to set this based on their capabilities as reported by terminfo. It will need to be established in a way that would allow multiple terminal emulators to set their own value within the variable (similar to how the PATH variable works). By default, conhost will report its terminfo features. When Windows Terminal eventually is shipped by default on Windows, it's terminfo will also be reported by default as well.  Furthermore the command specified by GNU infocmp should be available to all terminals include the default conhost and Windows Terminal to list the terminal capabilities.
The biggest gain from this will be from the use of scripts/utilities/applications that require knowledge of the terminal capabilities that already use this environment variable on other systems (Linux, MacOS, etc.).
Proposed technical implementation details (optional)
We now have a Powershell script that determines the VT support https://github.com/microsoft/terminal/pull/1884. Perhaps it could be adapted to also report the terminfo capabilities set by the TERM env variable in Windows for conhost and Windows Terminal.

Also very related but not quite the same based on what I saw from the discussion: https://github.com/microsoft/terminal/issues/1040.

I'd rather not.
Our goal with conhost has always been "be as close to xterm-256coloras possible". When we started working on WSL 5 years ago, we had basically no VT support. However, by setting the TERM for wsl to xterm (then later to xterm-256color), this made it possible for us to identify the shortcomings of conhost as far as VT support was concerned. Had we defined our own TERM, and populated our own infocmp, then conhost would have just eeked along with whatever support we had given it, and client apps that used tput and the termcap database would have worked alright given what we supported at the time.
That wasn't the goal though - the goal was to make conhost a capable terminal emulator, and that's still our goal. If there are things in xterm-256color that we don't support, or support in a buggy fashion, I'd rather the bugs land here, so we can fix them and maintain parity, rather than codify  what we do and don't support. With how fast we iterate on the Terminal and conhost, it would be disingenuous to codify what level of VT support we have into a infocmp database. We'd almost need one for each and every version of Windows 10 that's included VT support, and then one for each version of the Terminal - it's just not a sustainable feature.
Plus, I'm very reluctant to add TERM based terminal detection to the Terminal. That discussion is already being had in #1040 though, so I won't fork it into this thread as well.
PLUS, there's just no infocmp infrastructure on Windows at all, and there aren't remotely any plans to add it. Nor are there plans to port Windows Terminal to platforms where there is such infra. Sure, the Terminal can be used to connect to ssh sessions, or WSL apps, where there is such support, but again, I'd rather have parity with xterm256-color. I believe WSL still sets TERM to xterm-256color, and I'd imagine that Win32-OpenSSH does as well.

Yes WSL does set it to xterm-256color. I agree we should ensure parity with xterm256-color. I would agree we'd need to do it by Windows release but I'm not so sure we need to do it by Windows Terminal release. We release a new stable every other release and I haven't seen any documentation stating we'd support every release ever produced. We should only support stable for now until we get to a point where Windows Terminal can support doing LTS (and imo we're not quite there yet despite how great Windows Terminal is already.)

This is very similar to the discussion in #8303. The curses project shipped a ms-terminal TERM entry that causes us some trouble. It causes us trouble for the exact reasons Mike mentioned above :smile:

Yes that issue was what inspired me to create this one. I was thinking about how users could manually tell programs what's supported and I didn't see much from the Windows side, just Linux. So maybe I can update it in WSL but then I'd need WSL for remote connections instead simply having a quick powershell ssh profile.

I'm gonna close this one out as a simultaneous /duplicate of #1040 and #8303. Thanks for bringing it up!


希望能增加每日一题的选项,点击直接进入每日一题,应该很简单,每天去爬一下首页获取每日一题题号

🚀 Feature Proposal
A clear and concise description of what the feature is.
Motivation
Please outline the motivation for the proposal.
Contribution
Please describe the solution if you'd like to submit a PR.

🚀 Feature Proposal
Same as Pick One, choose a question of the day with one click
Motivation
Ever since LeetCode-Cn launched the daily questions, every time I search for the daily question on the web and then use the search function in vscode-leetcode to search for the question number, can I add another item to the bottom of the Pick One menu to open the daily questions with one click?
Contribution
I've seen that there are no daily questions on global sites, and this menu item needs to determine the selected site first.

同样的功能虽然algorithm插件已经实现了，但是作为一个非官方插件在使用中还是有许多不方便的，希望官方能实现这个功能！