Add runtime support for AdaptiveMiddleware

I have a new C# AdaptiveMiddleware class I've created that lets you run composer defined dialog(s) as middleware before the bot runs. This should be super useful as you can do things in middleware that would be difficult (or impossible) to do with the bot.  I've checked in the code for this class as part of an AdaptiveMiddlewareSample bot in a branch called stevenic/adaptive-middleware.  I'd like to explore what it would take to either integrate this functionality directly into composers runtime or at least find a better place to hos my sample as it requires an ejected runtime.
I'll reply with a separate comment that points out the runtime changes I had to make but let me go through the sample first. The sample is a simple echo bot that adds two different flavors of middleware; A TermsOfUseMiddleware dialog that prevents a user from talking to the bot until they've accepted its terms of use. And a DebugMiddleware dialog that lets a user ask to see the bots user state or conversation state at anytime during a conversation.
TermsOfUseMiddleware
Adaptive middleware fires OnBeforeTurn, OnAfterTurn, OnSendActivities, OnUpdateActivity, and OnDeleteActivity custom events that your dialog can catch to either; perform some processing on the incoming/outgoing activities, modify the bots memory, or interrupt the bots normal execution. The events are passed into your bots dialog when its started so to handle them you need to just implement a super simple dispatcher:

The TermsOfUseMiddleware dialog uses the OnBeforeTurn event to force the user to confirm that they accept the bots TOU. If the user says yes the text of the current activity will be restored to the original utterance and the bots execution will be allowed to continue, otherwise they will told they can't talk to the bot and the execution will be interrupted.  Once they accept the terms user.acceptedTOU will be set to true and this middleware will essentially become a no-op.

Here's a sample run:

DebugMiddleware
Adaptive middleware supports a second flavor of middleware which is all intent based.  The DebugMiddleware dialog shows how you can create a piece of middleware which looks for the user to trigger a special intent, like asking to see the current user state:

This middleware is configured to run before the TermsOfUseMiddleware so it also shows how a piece of middleware can interrupt other middleware without effecting the execution of the either the bot or other middleware. Here's a sample run:

The bots Middleware DIalogs are current configured as part of its settings file:

I then had to eject the runtime and add a the AdaptiveMiddleware class to the runtimes core library. Next I added support for the new setting.  I then add a new ConfigureAdaptiveMiddleware() method to startup.cs for both the azurewebapp & azurefunctions projects. And finally I modified GetBotAdapter() for both projects to call my new method at the end of the middleware chain.
That's it... Relatively minor changes to the runtime and while we would need to do that same thing in JS it's all pretty straight forward.
We'd also need to write an article documenting everything and add a new template type to composers samples plugin.


Fix ubuntu-desktop/xrdp when xrdp-debian.yml runs more than once

Currently there's a bug that if xrdp-debian.yml runs a second time on a Ubuntu host, you can no longer RDP to the host (connection error returned from xrdp).

Deferring for now.


Ship Ruby 3.1 precompiled native support

This is a placeholder to ship a new version of Nokogiri with Ruby 3.1 precompiled native support.
Please note that Nokogiri supports Ruby 3.1, but until a precompiled native gem is shipped, you will have to use the ruby vanilla platform gem which will compile from source during installation. Modern bundler will do this for you automatically.
This work is currently waiting for a version of rake-compiler-dock with Ruby 3.1 build capabilities. The maintainers of that project are aware, and there is no need to bother them. Feel free to subscribe to this issue and I'll keep it updated.
See #2408 for status.

Not urgent at all, obviously, since it's Christmas :)
Just wanted to note that I ran into this when trying to upgrade a project to Ruby 3.1 and running bundle install:
nokogiri-1.12.5-x86_64-darwin requires ruby version < 3.1.dev, >= 2.5, which is incompatible with the current version, ruby 3.1.0p0

% ruby -v
ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [x86_64-darwin21]

The platforms in my Gemfile.lock include Ruby, so I'm not sure why Bundler isn't falling back to it automatically like (based on the description of this issue?) it should:
PLATFORMS
  ruby
  x86_64-darwin-18
  x86_64-darwin-19
  x86_64-darwin-20
  x86_64-linux

The following is my Gemfile and Gemfile.lock:

Gemfile
source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }

ruby '>= 2.7'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '~> 6.1.4'

# Use postgresql as the database for Active Record
gem 'pg', '~> 1.2'

# Use Puma as the app server
gem 'puma', '~> 5.5'

# Transpile app-like JavaScript. Read more: https://github.com/rails/webpacker
gem 'webpacker', '~> 5.4.0'

# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
gem 'turbolinks', '~> 5'

# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.11'

# Use devise for Users and authentication.
gem 'devise', '~> 4.8'

# Use kaminari for pagination.
gem 'kaminari', '~> 1.2'

# Reduces boot times through caching; required in config/boot.rb
gem 'bootsnap', '>= 1.1.0', require: false

# Use Pundit for access control.
gem 'pundit', '~> 2.1'

# Postgres Search
gem 'pg_search', '~> 2.3'

# Image transformation
gem 'image_processing', '~> 1.12'

# Validations for ActiveStorage.
gem 'active_storage_validations', '~> 0.9.6'

# Generate URL slugs for models, e.g. '/users/spiderman'.
gem 'friendly_id', '~> 5.4.2'

# Use SPARQL for querying Wikidata in imports.
gem 'sparql', '~> 3.1.8', require: false

# Use Addressable for use with the Wikidata API.
gem 'addressable', '~> 2.8.0', require: false

# Use the AWS SDK S3 gem for DigitalOcean Spaces - which are S3-compatible.
gem 'aws-sdk-s3', '~> 1.66', require: false

# A CLI progress bar for use with the import rake tasks.
gem 'ruby-progressbar', '~> 1.11', require: false

# Use Sentry for error tracking in production.
gem 'sentry-ruby', '~> 4.8.1'
gem 'sentry-rails', '~> 4.8.1'

# Sorbet runtime typechecker and Sorbet Rails.
gem 'sorbet-runtime', '~> 0.5'
gem "sorbet-rails", '~> 0.7'

# GraphQL API https://github.com/rmosolgo/graphql-ruby
gem 'graphql', '~> 1.13.2'

# Doorkeeper for OAuth API tokens
gem "doorkeeper", "5.5.0.rc2"

# Rack::Cors for handling CORS in API requests.
gem "rack-cors", "~> 1.1"

# Render SVGs inline using Webpacker.
gem 'inline_svg', '~> 1.7'

# Honeypot for spambots that doesn't require the user to actually do any
# captcha and doesn't use google stuff.
gem 'invisible_captcha', '~> 2.0.0'

# For parallel execution of long-running tasks.
gem 'parallel', '~> 1.21', require: false

# For tracking changes to records.
gem 'paper_trail', '~> 12.1'

group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]

  # Pry for debugging.
  gem 'pry', '~> 0.14'
  gem 'pry-rails', '~> 0.3'

  # Rubocop for linting
  gem 'rubocop', '~> 1.24', require: false

  # rubocop extensions
  gem 'rubocop-performance', '~> 1.12', require: false
  gem 'rubocop-rspec', '~> 2.6', require: false
  gem 'rubocop-rails', '~> 2.12', require: false

  # Database cleaner for cleaning the database after tests/before seeding.
  gem 'database_cleaner', '~> 2.0'

  # Rspec-rails for testing.
  gem 'rspec-rails', '~> 5.0'

  # Factory Bot for creating factories.
  gem 'factory_bot_rails', '~> 6.2'

  # Code coverage
  gem 'simplecov', '~> 0.21', require: false

  # Shoulda-matchers for writing better tests on models.
  gem 'shoulda-matchers', '5.1.0'

  # For generating fake seeding data.
  gem 'faker', '~> 2.19'

  # For better display of rspec test suite progress
  gem 'fuubar', '~> 2.5.1'

  # Pundit matchers for simplifying policy testing.
  gem 'pundit-matchers', '~> 1.7.0'

  # Sorbet typechecker
  gem 'sorbet', '~> 0.5'
end

group :development do
  # Access an interactive console on exception pages or by calling 'console' anywhere in the code.
  gem 'web-console', '~> 4.2.0'
  gem 'listen', '~> 3.7'
  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
  gem 'spring', '~> 2.1'
  gem 'spring-watcher-listen', '~> 2.0.0'
  # Better error pages.
  gem 'better_errors', '~> 2.9'
  # For more useful BetterError error pages.
  gem 'binding_of_caller', '~> 1.0'
  # Open screenshots when they're taken with capybara.
  gem 'launchy', '~> 2.5'
  # Improve the formatting of GraphQL requests in the logs.
  # https://github.com/jetruby/graphql-rails_logger
  gem 'graphql-rails_logger', '~> 1.2.3'
  # Enable dotenv for local environment variables.
  gem 'dotenv-rails', '~> 2.7'
  # Tapioca for generating Sorbet RBI files.
  # Use a fork to fix this issue: https://github.com/Shopify/tapioca/issues/208
  gem 'tapioca', '~> 0.6.0'
end

group :test do
  # Adds support for Capybara system testing and selenium driver
  gem 'capybara', '~> 3.36'
  gem 'selenium-webdriver', '~> 4.1'
  # Easy installation and use of WebDriver clients for various browsers.
  gem 'webdrivers', '~> 5.0'
end

# # Windows does not include zoneinfo files, so bundle the tzinfo-data gem
# gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]

Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    actioncable (<IP_ADDRESS>)
      actionpack (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      nio4r (~> 2.0)
      websocket-driver (>= 0.6.1)
    actionmailbox (<IP_ADDRESS>)
      actionpack (= <IP_ADDRESS>)
      activejob (= <IP_ADDRESS>)
      activerecord (= <IP_ADDRESS>)
      activestorage (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      mail (>= 2.7.1)
    actionmailer (<IP_ADDRESS>)
      actionpack (= <IP_ADDRESS>)
      actionview (= <IP_ADDRESS>)
      activejob (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      mail (~> 2.5, >= 2.5.4)
      rails-dom-testing (~> 2.0)
    actionpack (<IP_ADDRESS>)
      actionview (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      rack (~> 2.0, >= 2.0.9)
      rack-test (>= 0.6.3)
      rails-dom-testing (~> 2.0)
      rails-html-sanitizer (~> 1.0, >= 1.2.0)
    actiontext (<IP_ADDRESS>)
      actionpack (= <IP_ADDRESS>)
      activerecord (= <IP_ADDRESS>)
      activestorage (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      nokogiri (>= 1.8.5)
    actionview (<IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      builder (~> 3.1)
      erubi (~> 1.4)
      rails-dom-testing (~> 2.0)
      rails-html-sanitizer (~> 1.1, >= 1.2.0)
    active_storage_validations (0.9.6)
      activejob (>= 5.2.0)
      activemodel (>= 5.2.0)
      activestorage (>= 5.2.0)
      activesupport (>= 5.2.0)
    activejob (<IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      globalid (>= 0.3.6)
    activemodel (<IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
    activerecord (<IP_ADDRESS>)
      activemodel (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
    activestorage (<IP_ADDRESS>)
      actionpack (= <IP_ADDRESS>)
      activejob (= <IP_ADDRESS>)
      activerecord (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      marcel (~> 1.0.0)
      mini_mime (>= 1.1.0)
    activesupport (<IP_ADDRESS>)
      concurrent-ruby (~> 1.0, >= 1.0.2)
      i18n (>= 1.6, < 2)
      minitest (>= 5.1)
      tzinfo (~> 2.0)
      zeitwerk (~> 2.3)
    addressable (2.8.0)
      public_suffix (>= 2.0.2, < 5.0)
    amazing_print (1.4.0)
    ast (2.4.2)
    aws-eventstream (1.2.0)
    aws-partitions (1.390.0)
    aws-sdk-core (3.109.2)
      aws-eventstream (~> 1, >= 1.0.2)
      aws-partitions (~> 1, >= 1.239.0)
      aws-sigv4 (~> 1.1)
      jmespath (~> 1.0)
    aws-sdk-kms (1.39.0)
      aws-sdk-core (~> 3, >= 3.109.0)
      aws-sigv4 (~> 1.1)
    aws-sdk-s3 (1.83.2)
      aws-sdk-core (~> 3, >= 3.109.0)
      aws-sdk-kms (~> 1)
      aws-sigv4 (~> 1.1)
    aws-sigv4 (1.4.0)
      aws-eventstream (~> 1, >= 1.0.2)
    bcrypt (3.1.16)
    better_errors (2.9.1)
      coderay (>= 1.0.0)
      erubi (>= 1.0.0)
      rack (>= 0.9.0)
    bindex (0.8.1)
    binding_of_caller (1.0.0)
      debug_inspector (>= 0.0.1)
    bootsnap (1.9.3)
      msgpack (~> 1.0)
    builder (3.2.4)
    byebug (11.1.3)
    capybara (3.36.0)
      addressable
      matrix
      mini_mime (>= 0.1.3)
      nokogiri (~> 1.8)
      rack (>= 1.6.0)
      rack-test (>= 0.6.3)
      regexp_parser (>= 1.5, < 3.0)
      xpath (~> 3.2)
    childprocess (4.1.0)
    coderay (1.1.3)
    commander (4.6.0)
      highline (~> 2.0.0)
    concurrent-ruby (1.1.9)
    connection_pool (2.2.5)
    crass (1.0.6)
    database_cleaner (2.0.1)
      database_cleaner-active_record (~> 2.0.0)
    database_cleaner-active_record (2.0.1)
      activerecord (>= 5.a)
      database_cleaner-core (~> 2.0.0)
    database_cleaner-core (2.0.1)
    debug_inspector (1.1.0)
    devise (4.8.1)
      bcrypt (~> 3.0)
      orm_adapter (~> 0.1)
      railties (>= 4.1.0)
      responders
      warden (~> 1.2.3)
    diff-lcs (1.5.0)
    docile (1.4.0)
    doorkeeper (5.5.0.rc2)
      railties (>= 5)
    dotenv (2.7.6)
    dotenv-rails (2.7.6)
      dotenv (= 2.7.6)
      railties (>= 3.2)
    ebnf (2.2.1)
      amazing_print (~> 1.2)
      htmlentities (~> 4.3)
      rdf (~> 3.1)
      scanf (~> 1.0)
      sxp (~> 1.1)
      unicode-types (~> 1.6)
    erubi (1.10.0)
    factory_bot (6.2.0)
      activesupport (>= 5.0.0)
    factory_bot_rails (6.2.0)
      factory_bot (~> 6.2.0)
      railties (>= 5.0.0)
    faker (2.19.0)
      i18n (>= 1.6, < 2)
    faraday (1.8.0)
      faraday-em_http (~> 1.0)
      faraday-em_synchrony (~> 1.0)
      faraday-excon (~> 1.1)
      faraday-httpclient (~> 1.0.1)
      faraday-net_http (~> 1.0)
      faraday-net_http_persistent (~> 1.1)
      faraday-patron (~> 1.0)
      faraday-rack (~> 1.0)
      multipart-post (>= 1.2, < 3)
      ruby2_keywords (>= 0.0.4)
    faraday-em_http (1.0.0)
    faraday-em_synchrony (1.0.0)
    faraday-excon (1.1.0)
    faraday-httpclient (1.0.1)
    faraday-net_http (1.0.1)
    faraday-net_http_persistent (1.2.0)
    faraday-patron (1.0.0)
    faraday-rack (1.0.0)
    ffi (1.15.4)
    friendly_id (5.4.2)
      activerecord (>= 4.0.0)
    fuubar (2.5.1)
      rspec-core (~> 3.0)
      ruby-progressbar (~> 1.4)
    globalid (1.0.0)
      activesupport (>= 5.0)
    graphql (1.13.2)
    graphql-rails_logger (1.2.3)
      actionpack (> 5.0)
      activesupport (> 5.0)
      railties (> 5.0)
      rouge (~> 3.0)
    hamster (3.0.0)
      concurrent-ruby (~> 1.0)
    highline (2.0.3)
    htmlentities (4.3.4)
    i18n (1.8.11)
      concurrent-ruby (~> 1.0)
    image_processing (1.12.1)
      mini_magick (>= 4.9.5, < 5)
      ruby-vips (>= 2.0.17, < 3)
    inline_svg (1.7.2)
      activesupport (>= 3.0)
      nokogiri (>= 1.6)
    invisible_captcha (2.0.0)
      rails (>= 5.0)
    jbuilder (2.11.5)
      actionview (>= 5.0.0)
      activesupport (>= 5.0.0)
    jmespath (1.4.0)
    kaminari (1.2.1)
      activesupport (>= 4.1.0)
      kaminari-actionview (= 1.2.1)
      kaminari-activerecord (= 1.2.1)
      kaminari-core (= 1.2.1)
    kaminari-actionview (1.2.1)
      actionview
      kaminari-core (= 1.2.1)
    kaminari-activerecord (1.2.1)
      activerecord
      kaminari-core (= 1.2.1)
    kaminari-core (1.2.1)
    launchy (2.5.0)
      addressable (~> 2.7)
    link_header (0.0.8)
    listen (3.7.0)
      rb-fsevent (~> 0.10, >= 0.10.3)
      rb-inotify (~> 0.9, >= 0.9.10)
    logger (1.5.0)
    loofah (2.13.0)
      crass (~> 1.0.2)
      nokogiri (>= 1.5.9)
    mail (2.7.1)
      mini_mime (>= 0.1.1)
    marcel (1.0.2)
    matrix (0.4.2)
    method_source (1.0.0)
    mini_magick (4.11.0)
    mini_mime (1.1.2)
    mini_portile2 (2.6.1)
    minitest (5.15.0)
    msgpack (1.4.2)
    multipart-post (2.1.1)
    net-http-persistent (4.0.1)
      connection_pool (~> 2.2)
    nio4r (2.5.8)
    nokogiri (1.12.5)
      mini_portile2 (~> 2.6.1)
      racc (~> 1.4)
    nokogiri (1.12.5-x86_64-darwin)
      racc (~> 1.4)
    nokogiri (1.12.5-x86_64-linux)
      racc (~> 1.4)
    orm_adapter (0.5.0)
    paper_trail (12.1.0)
      activerecord (>= 5.2)
      request_store (~> 1.1)
    parallel (1.21.0)
    parlour (6.0.1)
      commander (~> 4.5)
      parser
      rainbow (~> 3.0)
      sorbet-runtime (>= 0.5)
    parser (<IP_ADDRESS>)
      ast (~> 2.4.1)
    pg (1.2.3)
    pg_search (2.3.5)
      activerecord (>= 5.2)
      activesupport (>= 5.2)
    polyfill (1.9.0)
    pry (0.14.1)
      coderay (~> 1.1)
      method_source (~> 1.0)
    pry-rails (0.3.9)
      pry (>= 0.10.4)
    public_suffix (4.0.6)
    puma (5.5.2)
      nio4r (~> 2.0)
    pundit (2.1.1)
      activesupport (>= 3.0.0)
    pundit-matchers (1.7.0)
      rspec-rails (>= 3.0.0)
    racc (1.6.0)
    rack (2.2.3)
    rack-cors (1.1.1)
      rack (>= 2.0.0)
    rack-proxy (0.7.0)
      rack
    rack-test (1.1.0)
      rack (>= 1.0, < 3)
    rails (<IP_ADDRESS>)
      actioncable (= <IP_ADDRESS>)
      actionmailbox (= <IP_ADDRESS>)
      actionmailer (= <IP_ADDRESS>)
      actionpack (= <IP_ADDRESS>)
      actiontext (= <IP_ADDRESS>)
      actionview (= <IP_ADDRESS>)
      activejob (= <IP_ADDRESS>)
      activemodel (= <IP_ADDRESS>)
      activerecord (= <IP_ADDRESS>)
      activestorage (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      bundler (>= 1.15.0)
      railties (= <IP_ADDRESS>)
      sprockets-rails (>= 2.0.0)
    rails-dom-testing (2.0.3)
      activesupport (>= 4.2.0)
      nokogiri (>= 1.6)
    rails-html-sanitizer (1.4.2)
      loofah (~> 2.3)
    railties (<IP_ADDRESS>)
      actionpack (= <IP_ADDRESS>)
      activesupport (= <IP_ADDRESS>)
      method_source
      rake (>= 0.13)
      thor (~> 1.0)
    rainbow (3.0.0)
    rake (13.0.6)
    rb-fsevent (0.11.0)
    rb-inotify (0.10.1)
      ffi (~> 1.0)
    rbi (0.0.9)
      ast
      parser
      sorbet-runtime (>= 0.5.9204)
      unparser
    rdf (3.1.15)
      hamster (~> 3.0)
      link_header (~> 0.0, >= 0.0.8)
    rdf-aggregate-repo (3.1.0)
      rdf (~> 3.1)
    rdf-xsd (3.1.1)
      rdf (~> 3.1)
      rexml (~> 3.2)
    regexp_parser (2.2.0)
    request_store (1.5.0)
      rack (>= 1.4)
    responders (3.0.1)
      actionpack (>= 5.0)
      railties (>= 5.0)
    rexml (3.2.5)
    rouge (3.27.0)
    rspec-core (3.10.1)
      rspec-support (~> 3.10.0)
    rspec-expectations (3.10.1)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.10.0)
    rspec-mocks (3.10.2)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.10.0)
    rspec-rails (5.0.2)
      actionpack (>= 5.2)
      activesupport (>= 5.2)
      railties (>= 5.2)
      rspec-core (~> 3.10)
      rspec-expectations (~> 3.10)
      rspec-mocks (~> 3.10)
      rspec-support (~> 3.10)
    rspec-support (3.10.3)
    rubocop (1.24.0)
      parallel (~> 1.10)
      parser (>= <IP_ADDRESS>)
      rainbow (>= 2.2.2, < 4.0)
      regexp_parser (>= 1.8, < 3.0)
      rexml
      rubocop-ast (>= 1.15.0, < 2.0)
      ruby-progressbar (~> 1.7)
      unicode-display_width (>= 1.4.0, < 3.0)
    rubocop-ast (1.15.0)
      parser (>= <IP_ADDRESS>)
    rubocop-performance (1.12.0)
      rubocop (>= 1.7.0, < 2.0)
      rubocop-ast (>= 0.4.0)
    rubocop-rails (2.12.4)
      activesupport (>= 4.2.0)
      rack (>= 1.1)
      rubocop (>= 1.7.0, < 2.0)
    rubocop-rspec (2.6.0)
      rubocop (~> 1.19)
    ruby-progressbar (1.11.0)
    ruby-vips (2.1.4)
      ffi (~> 1.12)
    ruby2_keywords (0.0.5)
    rubyzip (2.3.2)
    safe_type (1.1.1)
    scanf (1.0.0)
    selenium-webdriver (4.1.0)
      childprocess (>= 0.5, < 5.0)
      rexml (~> 3.2, >= 3.2.5)
      rubyzip (>= 1.2.2)
    semantic_range (3.0.0)
    sentry-rails (4.8.1)
      railties (>= 5.0)
      sentry-ruby-core (~> 4.8.1)
    sentry-ruby (4.8.1)
      concurrent-ruby (~> 1.0, >= 1.0.2)
      faraday (>= 1.0)
      sentry-ruby-core (= 4.8.1)
    sentry-ruby-core (4.8.1)
      concurrent-ruby
      faraday
    shoulda-matchers (5.1.0)
      activesupport (>= 5.2.0)
    simplecov (0.21.2)
      docile (~> 1.1)
      simplecov-html (~> 0.11)
      simplecov_json_formatter (~> 0.1)
    simplecov-html (0.12.3)
    simplecov_json_formatter (0.1.3)
    sorbet (0.5.9464)
      sorbet-static (= 0.5.9464)
    sorbet-coerce (0.5.0)
      polyfill (~> 1.8)
      safe_type (~> 1.1, >= 1.1.1)
      sorbet-runtime (>= 0.4.4704)
    sorbet-rails (0.7.27)
      method_source (>= 0.9.2)
      parlour (>= 4.0.1)
      parser (>= 2.7)
      sorbet-coerce (>= 0.2.6)
      sorbet-runtime (>= 0.5)
    sorbet-runtime (0.5.9464)
    sorbet-static (0.5.9464-universal-darwin-14)
    sorbet-static (0.5.9464-universal-darwin-15)
    sorbet-static (0.5.9464-universal-darwin-16)
    sorbet-static (0.5.9464-universal-darwin-17)
    sorbet-static (0.5.9464-universal-darwin-18)
    sorbet-static (0.5.9464-universal-darwin-19)
    sorbet-static (0.5.9464-universal-darwin-20)
    sorbet-static (0.5.9464-universal-darwin-21)
    sorbet-static (0.5.9464-x86_64-linux)
    sparql (3.1.8)
      builder (~> 3.2)
      ebnf (~> 2.1)
      logger (~> 1.4)
      rdf (~> 3.1, >= 3.1.14)
      rdf-aggregate-repo (~> 3.1)
      rdf-xsd (~> 3.1)
      sparql-client (~> 3.1, >= 3.1.2)
      sxp (~> 1.1)
    sparql-client (3.1.2)
      net-http-persistent (~> 4.0, >= 4.0.1)
      rdf (~> 3.1)
    spoom (1.1.7)
      sorbet (>= 0.5.9204)
      sorbet-runtime (>= 0.5.9204)
      thor (>= 0.19.2)
    spring (2.1.1)
    spring-watcher-listen (2.0.1)
      listen (>= 2.7, < 4.0)
      spring (>= 1.2, < 3.0)
    sprockets (4.0.2)
      concurrent-ruby (~> 1.0)
      rack (> 1, < 3)
    sprockets-rails (3.4.2)
      actionpack (>= 5.2)
      activesupport (>= 5.2)
      sprockets (>= 3.0.0)
    sxp (1.1.0)
      rdf (~> 3.1)
    tapioca (0.6.0)
      bundler (>= 1.17.3)
      pry (>= 0.12.2)
      rbi (~> 0.0.0, >= 0.0.9)
      sorbet-runtime (>= 0.5.9204)
      sorbet-static (>= 0.5.9204)
      spoom (~> 1.1.0, >= 1.1.4)
      thor (>= 0.19.2)
      yard-sorbet
    thor (1.1.0)
    turbolinks (5.2.1)
      turbolinks-source (~> 5.2)
    turbolinks-source (5.2.0)
    tzinfo (2.0.4)
      concurrent-ruby (~> 1.0)
    unicode-display_width (2.1.0)
    unicode-types (1.7.0)
    unparser (0.6.2)
      diff-lcs (~> 1.3)
      parser (>= 3.0.0)
    warden (1.2.9)
      rack (>= 2.0.9)
    web-console (4.2.0)
      actionview (>= 6.0.0)
      activemodel (>= 6.0.0)
      bindex (>= 0.4.0)
      railties (>= 6.0.0)
    webdrivers (5.0.0)
      nokogiri (~> 1.6)
      rubyzip (>= 1.3.0)
      selenium-webdriver (~> 4.0)
    webpacker (5.4.3)
      activesupport (>= 5.2)
      rack-proxy (>= 0.6.1)
      railties (>= 5.2)
      semantic_range (>= 2.3.0)
    webrick (1.7.0)
    websocket-driver (0.7.5)
      websocket-extensions (>= 0.1.0)
    websocket-extensions (0.1.5)
    xpath (3.2.0)
      nokogiri (~> 1.8)
    yard (0.9.27)
      webrick (~> 1.7.0)
    yard-sorbet (0.6.1)
      sorbet-runtime (>= 0.5)
      yard (>= 0.9)
    zeitwerk (2.5.1)

PLATFORMS
  ruby
  x86_64-darwin-18
  x86_64-darwin-19
  x86_64-darwin-20
  x86_64-linux

DEPENDENCIES
  active_storage_validations (~> 0.9.6)
  addressable (~> 2.8.0)
  aws-sdk-s3 (~> 1.66)
  better_errors (~> 2.9)
  binding_of_caller (~> 1.0)
  bootsnap (>= 1.1.0)
  byebug
  capybara (~> 3.36)
  database_cleaner (~> 2.0)
  devise (~> 4.8)
  doorkeeper (= 5.5.0.rc2)
  dotenv-rails (~> 2.7)
  factory_bot_rails (~> 6.2)
  faker (~> 2.19)
  friendly_id (~> 5.4.2)
  fuubar (~> 2.5.1)
  graphql (~> 1.13.2)
  graphql-rails_logger (~> 1.2.3)
  image_processing (~> 1.12)
  inline_svg (~> 1.7)
  invisible_captcha (~> 2.0.0)
  jbuilder (~> 2.11)
  kaminari (~> 1.2)
  launchy (~> 2.5)
  listen (~> 3.7)
  paper_trail (~> 12.1)
  parallel (~> 1.21)
  pg (~> 1.2)
  pg_search (~> 2.3)
  pry (~> 0.14)
  pry-rails (~> 0.3)
  puma (~> 5.5)
  pundit (~> 2.1)
  pundit-matchers (~> 1.7.0)
  rack-cors (~> 1.1)
  rails (~> 6.1.4)
  rspec-rails (~> 5.0)
  rubocop (~> 1.24)
  rubocop-performance (~> 1.12)
  rubocop-rails (~> 2.12)
  rubocop-rspec (~> 2.6)
  ruby-progressbar (~> 1.11)
  selenium-webdriver (~> 4.1)
  sentry-rails (~> 4.8.1)
  sentry-ruby (~> 4.8.1)
  shoulda-matchers (= 5.1.0)
  simplecov (~> 0.21)
  sorbet (~> 0.5)
  sorbet-rails (~> 0.7)
  sorbet-runtime (~> 0.5)
  sparql (~> 3.1.8)
  spring (~> 2.1)
  spring-watcher-listen (~> 2.0.0)
  tapioca (~> 0.6.0)
  turbolinks (~> 5)
  web-console (~> 4.2.0)
  webdrivers (~> 5.0)
  webpacker (~> 5.4.0)

RUBY VERSION
   ruby 2.7.2p137

BUNDLED WITH
   2.3.3

Anyway, Merry Christmas and again - not urgent at all, just reporting it in case anyone else runs into it or these details help :)

Not urgent at all, obviously, since it's Christmas :)
Just wanted to note that I ran into this when trying to upgrade a project to Ruby 3.1 and running bundle install:
nokogiri-1.12.5-x86_64-darwin requires ruby version < 3.1.dev, >= 2.5, which is incompatible with the current version, ruby 3.1.0p0

% ruby -v
ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [x86_64-darwin21]

The platforms in my Gemfile.lock include Ruby, so I'm not sure why Bundler isn't falling back to it automatically like (based on the description of this issue?) it should:
PLATFORMS
  ruby
  x86_64-darwin-18
  x86_64-darwin-19
  x86_64-darwin-20
  x86_64-linux

The following is my Gemfile and Gemfile.lock:
Gemfile
Gemfile.lock
Anyway, Merry Christmas and again - not urgent at all, just reporting it in case anyone else runs into it or these details help :)
EDIT: I removed these lines from my Gemfile.lock and it seems to be installing fine now:
    nokogiri (1.12.5-x86_64-darwin)
      racc (~> 1.4)
    nokogiri (1.12.5-x86_64-linux)
      racc (~> 1.4)

@connorshea
1- Delete your Gemfile.lock
2 - run bundle install

We got a similar report on slack, bundler should be handling this fine, but this is tricky stuff and I believe we might not be there yet :( On an initial look, this would seem similar to https://github.com/rubygems/rubygems/issues/4455.
Does bundle update nokogiri work?

To clarify, Bundler should handle this just fine if there's no Gemfile.lock. This problem is specific to having a lockfile generated with a previous Ruby, and thus including platform specific variants of nokogiri not compatible with the running Ruby. That's why @connorshea's smart trick works.

So, I tried to reproduce now and things seem to just work for me, but I tested this under arm64-darwin21, which is not locked at all, so I guess that's why.
@simi reported that somehow ruby version constraints were by passed for him and 1.12.5-x86_64-linux got installed under ruby 3.1. I guess that's what's causing the problem for him, but I still have no idea how 1.12.5-x86_64-linux would get installed under Ruby 3.1 in the first place.

@deivid-rodriguez My project is open source, so you can try reproducing it yourself:

Clone https://github.com/connorshea/vglist
Use 2.7.x (or 3.0.x I think?) on the main branch and bundle install
Then switch to Ruby 3.1.0 by either using rbenv local 3.1.0 or switching to the test-branch-for-bundler-issue branch which has a .ruby-version file.

I'm on an M1 Mac, if that matters at all.

Yup,, I managed to reproduce easily with your initial Gemfile, but creating a lockfile from scratch with ruby 3.0 and then bundle it with ruby 3.1. I'm working on a fix now.

This is trickier than it seemed to me in the first place :(
When using gem information from the lockfile, it is initially forbidden to fetch the "real underlying specification" for each gem and we're only allowed to use names, versions, and dependency information recorded in the lockfile. The problem is, required_ruby_version metadata is not recorded in the lockfile, so we can't check it before resolving in order to figure out whether we need to discard some data in the lockfile due to not satisfying the running ruby version.
To fix the issue I can think of two approaches:

Start recording required_ruby_version metadata in the lockfile. This is what I suggested at rubygems/rubygems#4455 and it seems doable, but requires special backwards compatibility work.
Materialize locked specs before resolving, so that we can check required_ruby_version information. This also sounds doable, but I tried it at https://github.com/rubygems/rubygems/pull/5070 and I couldn't get it to fully work.

I'll try hard to figure out some solution.

Thank you for all your great work as always, Deivid 🙇♂

Oddly, I ran into this issue with only ruby in the PLATFORMS section. When I deleted the Gemfile.lock and ran bundle it updated PLATFORMS to be just x86_64-linux.

Yes, I think that is expected. Even if your lockfile is locked to RUBY, bundler will still try to also resolve for your specific platform, and will run into the same issue.

In my experience, the only reliable way to avoid the aforementioned problems is to use bundle config set force_ruby_platform true.

I had a similar experience as @mockdeep. I deleted my Gemfile.lock, ran bundle, and it completed successfully on an Macbook Air M1. My Gemfile.lock diff afterwards was:
 PLATFORMS
-  ruby
+  arm64-darwin-21

Has someone tried bundle update nokogiri? I just tried it myself and it worked fine, since it completely avoids the lockfile for nokogiri.

On an intel mac, with several rails applications, deleting the Gemfile.lock (or bypassing with bundle update nokogiri) didn't work for me. Following @skaes' advice, however, has produced clean builds with no lockfile diff.

Really? What error did you get? That's completely unexpected and sounds like a similar issue to the one reported by @simi in Slack. If you were able to reproduce that and report an issue to https://github.com/rubygems/rubygems, that'd be great.

@deivid-rodriguez the error I was getting from running bundle install against an existing Gemfile was:
nokogiri-1.12.5-x86_64-darwin requires ruby version >= 2.5, < 3.1.dev, which is incompatible with the current version, ruby 3.1.0p0

Which is oddly very close to but not exactly what @connorshea reported above (the version bounds are reversed—they had < 3.1.dev, >= 2.5).
My Gemfile's platforms were simply:
PLATFORMS
  ruby

This is exactly my problem, I'll try to dig deeper soon to provide reproducing script.

I'm able to repro with a Gemfile that simply contains:
source "https://rubygems.org"
gem "nokogiri"

Here's a transcript of working with it:
14:56:41 ~/work/etc/bundletest/ % ls
Gemfile
14:56:50 ~/work/etc/bundletest/ % cat Gemfile
source "https://rubygems.org"
gem "nokogiri"
14:56:59 ~/work/etc/bundletest/ % ruby -v
ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [x86_64-darwin20]
14:57:03 ~/work/etc/bundletest/ % gem -v
3.3.3
14:57:13 ~/work/etc/bundletest/ % bundle config
Settings are listed in order of priority. The top value will be used.
14:57:21 ~/work/etc/bundletest/ % bundle
Fetching gem metadata from https://rubygems.org/.......
Resolving dependencies...
nokogiri-1.12.5-x86_64-darwin requires ruby version >= 2.5, < 3.1.dev, which is incompatible with the current version, ruby 3.1.0p0
14:57:28 ~/work/etc/bundletest/ % bundle config set force_ruby_platform true
14:57:33 ~/work/etc/bundletest/ % bundle
Fetching gem metadata from https://rubygems.org/.......
Resolving dependencies...
Using bundler 2.3.3
Using racc 1.6.0
Using mini_portile2 2.6.1
Using nokogiri 1.12.5
Bundle complete! 1 Gemfile dependency, 4 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
14:57:40 ~/work/etc/bundletest/ % cat Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    mini_portile2 (2.6.1)
    nokogiri (1.12.5)
      mini_portile2 (~> 2.6.1)
      racc (~> 1.4)
    racc (1.6.0)

PLATFORMS
  ruby

DEPENDENCIES
  nokogiri

BUNDLED WITH
   2.3.3
15:00:15 ~/work/etc/bundletest/ % bundle config set force_ruby_platform false
You are replacing the current global value of force_ruby_platform, which is currently "true"
15:00:26 ~/work/etc/bundletest/ % bundle
Using bundler 2.3.3
Using mini_portile2 2.6.1
Using racc 1.6.0
Using nokogiri 1.12.5 (x86_64-darwin)
Bundle complete! 1 Gemfile dependency, 4 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.

One thing that jumps out at me is, after I set force_ruby_platform to false, the install succeeds again but as Using nokogiri 1.12.5 **(x86_64-darwin)**
@deivid-rodriguez apologies, I'm not sure exactly how to frame this for a rubygems issue. What other info could I provide?

So @simi's issue was that somehow nokogiri-1.12.5-x86_64-x86_64-linux got installed in his system on Ruby 3.1, which is completely unexpected since it's not supported there. Somehow required_ruby_version constraints were bypassed but we don't know how yet. I think your issue is the same, but on MacOS. If you manually uninstall nokogiri-1.12.5-x86_64-darwin through gem uninstall nokogiri, it should work again.
The problem, and what we need to be able to reproduce reliably, is how this is happening in the first place.
...
Actually, while I was writing this I think I realized what the problem might be. Let me do some testing and I'll get back to you.

No, not really, I'm unable to reproduce this :(

Yep you're right, after doing gem uninstall nokogiri (and "yes"ing everything), it behaves great.

@deivid-rodriguez I think I've got something. My initial bundle install with Ruby 3.1.0 was on a project that used a private gem repository (Artifactory) instead of rubygems. Redoing the basic Gemfile above allows the platform-specific version to be installed:
16:06:56 ~/work/etc/bundletest/ % gem list | grep nokogiri
16:07:00 ~/work/etc/bundletest/ % ruby -v
ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [x86_64-darwin20]
16:07:04 ~/work/etc/bundletest/ % gem -v
3.3.3
16:07:07 ~/work/etc/bundletest/ % bundler -v
Bundler version 2.3.3
16:07:12 ~/work/etc/bundletest/ % l
total 16
-rw-r--r--  1 bencullen-kerney  11 Dec 29 14:37 .ruby-version
-rw-r--r--  1 bencullen-kerney  84 Dec 29 16:06 Gemfile
16:07:18 ~/work/etc/bundletest/ % cat Gemfile
source "https://stitchfix01.jfrog.io/stitchfix01/api/gems/eng-gems/"
gem "nokogiri"
16:07:23 ~/work/etc/bundletest/ % bundle
Fetching gem metadata from https://XXXXXXX/........
Resolving dependencies...
Using bundler 2.3.3
Using racc 1.6.0
Fetching nokogiri 1.12.5 (x86_64-darwin)
Installing nokogiri 1.12.5 (x86_64-darwin)
Bundle complete! 1 Gemfile dependency, 3 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
16:07:45 ~/work/etc/bundletest/ % gem list | grep nokogiri
nokogiri (1.12.5 x86_64-darwin)
16:07:58 ~/work/etc/bundletest/ % cat Gemfile.lock
GEM
  remote: https://XXXXXXX/
  specs:
    nokogiri (1.12.5-x86_64-darwin)
      racc (~> 1.4)
    racc (1.6.0)

PLATFORMS
  x86_64-darwin-20

DEPENDENCIES
  nokogiri

BUNDLED WITH
   2.3.3

Unfortunately I'm not very familiar with how the repository is configured, but happy to dig in where I can.

Also apologies for continuing this thread—this is clearly not a nokogiri-specific bug. I'm honestly not sure it's a rubygems bug, or if the private repository is misconfigured somehow.

My problem was with Geminabox private repo, but I have seen it using rubygem.org as well.

@simi did you gem uninstall nokogiri between the two? It seems that, once the platform-specific version is allowed through, it will reproduce for Gemfiles with the rubygems source.

Yeah, maybe this should be moved to our repository. I think the culprit is here:
https://github.com/rubygems/rubygems/blob/62d14e47f58d8cc3c32f0e69a082c7d9a16a001e/bundler/lib/bundler/lazy_specification.rb#L92-L96
The actual filtering of required_ruby_version is only done for EndpointSpecifications, which represent the data given by the Compact Index API. Older APIs provide RemoteSpecification objects, which did not include required_ruby_version information. And custom gem servers like Geminabox only support older APIs as far as I know.

Has someone tried bundle update nokogiri?

I tried that and it didn't fix the issue. I needed to regenerate Gemfile.lock.

Hi, although this conversation is valuable, I'd prefer if it didn't happen here and instead happened on a bundler issue. @deivid-rodriguez can you recommend somewhere this can continue?
Please don't run bundle config set force_ruby_platform true to work around problems. Instead uninstall all nokogiri versions from your system and re-bundle.

See #2408 for status on shipping 3.1 support in native precompiled gem releases.

@flavorjones Yes, I'm so sorry for hijacking this thread with a bundler issue. I created a fresh ticket in our repository: https://github.com/rubygems/rubygems/issues/5251. Let's post any comments about that issue there.

I hope this isn't adding noise. On MBP M1. No Gemfile.lock file has yet been created. New Rail 7 app
➜ gem install nokogiri
Building native extensions. This could take a while...
Successfully installed nokogiri-1.12.5
1 gem installed

app_name on  main [?] via 💎 ruby-3.1.0 took 42s
➜ bundle update
Fetching gem metadata from https://rubygems.org/...........
Resolving dependencies...
nokogiri-1.12.5-arm64-darwin requires ruby version >= 2.5, < 3.1.dev, which is incompatible with the current version, ruby 3.1.0p0

Tried
➜ bundle update nokogiri
This Bundle hasn't been installed yet. Run `bundle install` to update and install the bundled gems.

Thanks everyone for working on this

@MtnBiker please uninstall all versions of nokogiri and try again.

@flavorjones and others. Thank you. I sorted it out. I think the problem was that Rails 7.0.0 wasn't compatible with Ruby 3.1.0. So went with another version of Ruby. Ran into another problem with pg. Lots of activity on Rails, but in response tot the 3.1.0 problem: "This is already fixed on main - #43951.
It was expected for rails 7.0.1 to be released before ruby 3.1.0. See https://bugs.ruby-lang.org/issues/14394#note-36."  But  current release still at 7.0.0. And mentions of Ruby 3.2 in Issues

Oh that nokogiri issue is about ruby 3.1, from a year ago, not ruby 3.2. Still, it explains how nokogiri is "supposed" to work, and combined with the 1.14.0.rc1 release notes --  I think it is exactly what is going on now with ruby 3.2, it explains everything else I've been seeing.
Everywhere else, bundler figures out not to use the pre-compiled nokogiri, which is why I haven't had any problems with it in those other environments -- and noticed nokogiri taking longer to install, compiling from source!
But on CircleCI, nope.


[CI] Fix wrong docker release tags in adapters

Current Behavior
Due to being incorrectly sorted, the git ls-remote --tags command returned the release tags in unwanted order, which resulted in the automation script tagging the adapters' image with the wrong version.
Desired Behavior
Sort the versions in an unambiguous way and get the latest version for tagging.
Implementation
The changes from this PR have to be propagated accross all adapters.
Steps to propagate

Go to the adapter repository
Navigate to .github/workflows/multi-platform.yml
Within the yaml file, navigate to the job called docker-build
Within that job, navigate to the 'Identify Release Values' step
In the run field of the job, change the tag variables by replicating the changes of the above linked PR.

(See the exact lines to change in the Istio adapter as an example here)
To be done for all the adapters:

[ ] meshery-istio
[ ] meshery-linkerd
[ ] meshery-consul
[ ] meshery-kuma
[ ] meshery-osm
[ ] meshery-traefik-mesh
[ ] meshery-nginx-sm
[ ] meshery-cilium

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Can I work on this ?

@gr455 can you please assign this task to me

Can you please assign me the task

Can I work on this issue?

@gr455 already raised

Folks, one of the most important goals of good first issues is to familiarize people with the code and get their first contribution in to build a momentum. Please do only a few of these and move on to more difficult issues.
Also please mention below the issue what part of the issue you will be working on before actually starting to work on it to avoid duplications.

Cool I'll pick up meshery-linkerd as I already have it locally.

Hi @gr455, I am new here. Is this issue still available? I saw the issue description but still asking to double-check. Thanks,

@SD-13 As a matter of fact, yes! There is one more adapter remaining, can you help with that one? (meshery-nsm)

@gr455 yes, I will be more than happy to do that. Thanks,

@gr455 hey can i try to fix the last one please?

Hello can i be assigned to this issue?


privateConversationData fields getting overwritten/replaced when conversation is started with 2 concurrent messages

System Information (Required)

SDK Language: NodeJS 7.10
SDK Version: Bot Builder 3.7
Development Environment: Bot running locally but accessed by Webchat (through DirectLineJS) over internet through ngrok

Issue Description
Writing data into privateConversationData not getting saved and accessible to next message dialogs.
Steps to Reproduce

Send 2 messages (concurrently) from webchat using directLineJS APIs.
In respective dialogs of these messages set a field into session.privateConversationData.
Try to access the these fields in subsequent message dialogs.
Only one field set by one of the first 2 messages are seen in session.privateConversationData.

Expected Behavior
All fields set into session.privateConversationData by all messages should be accessible to subsequent message dialogs.
Actual Results
Scenario:
My webchat code sends 2 messages to Bot (using directLine.postActivity) to start the conversation: 1) A Greeting message which invokes greetings:/ dialog and sets GREET:true field in session.privateConversationData. 2) A SetRegion message which invokes setRegion:/ dialogue and sets REGION:UK field in session.privateConversationData and responds with a HeroCard message.
User clicks on one of the buttons of HeroCard to send a message to Bot. takeAction:/ dialog gets invoked.
In this dialog if I try to access session.privateConversationData, I could see only one field, either GREET:true or REGION:UK, but not both.
My guess is that because 2 messages are send concurrently to initiate the conversation, the bot connector is replacing/overwriting the session created by one message with that of another message.

Hey @bhushanvadgave, could be the same issue (https://github.com/Microsoft/BotBuilder/issues/2103) we had a couple of months back?
We implemented queuing and it works fine.

@michaelvol I tried with BotBuilder 3.7 and 3.8 versions. Still facing this issue.

As @Stevenic mentioned in #2103

This is just a general issue with bots, they're not great at handling back-to-back messages from a user. You could potentially serialize the messages to the bot but you'd need to do all of that work. We don't have any built in logic to serialize them at this point.

The recommendation we currently make is that you send a typing indicator using session.sendTyping() before performing any long running operations. That will minimize the chance of a user sending you multiple messages.


Skill and statistic purchasing advanced integrations

Integrate the direction, cost, purchase, and tier options into the actual purchase process of statistics and skills.

Partially resolved by commit 9e6a93ea46de2104f1eead59b715fa07af8b5343.  direction is still left to be included.

Inclusion of direction resolved by commit 8e6d51140038d05fc284833ffa91df43c8804982.


trying again to update jmavlib

sigh... how did the BOM com back ?  I have one more idea....

Hey, what's missing here?

One of the files I changed has a Unicode byte order mark at the top of the file (0xFF FE) and apparently your build system can't handle that kind of byte order mark.  But when I remove this in a branch and try and do a pull request "git" decides NOT to remove the byte order mark in the master branch.  So I believe this will require someone manually merging the bits and removing the byte order mark before committing to the master branch.   See https://en.wikipedia.org/wiki/Byte_order_mark.


Ability to have a profile that can open multiple tabs

Right now I use cmder and I have a keyboard shortcut that can launch multiple tabs, like, one will start and run the local proxy, the other one for development and one for database
I couldnt do that in current Windows Terminal, it would be nice to have that setup.

@amarth1982 I will have a look on this and try to find a way to implement this functionality ;)
I will keep you up to date

Something like #756?

Yes but not exactly same, if its done at default profile level, I would be able to launch multiple tabs when I launch terminal, instead if I can create a profile that would launch multiple tabs, then I could associate keyboard shortcut to it or still use it as default profile, and also it would not annoy me if I just need one tab for a simple task, I don't have to close others

I think we'll tackle them in the same way, so I'll close this as a duplicate. In general, if we think about a profile as a type of configured launchable, we'll need to introduce a new top-level concept (arrangement?) that can be key-bound. It's really similar to opening one tab with multiple panes, each of which is running a different profile. That would also be one of these "arangement"s.


Intel Edison recommended in docs, but device is discontinued! (Last buy September 16, 2017)

It appears that the documentation and software(?) will need revision - and a new hardware home
https://communities.intel.com/docs/DOC-112093
Intel will support last time orders of Intel Edison products through September 16, 2017 and will fulfill those orders through December 16, 2017.

Intel® Edison Discontinuation Notice: Version 1
Created by MTaylor on Jul 5, 2017 3:46 PM. Last modified by MTaylor on Jul 5, 2017 3:46 PM.
Intel is discontinuing Intel® Edison compute modules and developer kits. To help customers manage through the Intel Edison discontinuance, Intel will support last time orders of Intel Edison products through September 16, 2017 and will fulfill those orders through December 16, 2017. The current level of community forum-based support for Intel Edison will continue to be available through September 15, 2017. There are no further software releases planned for the Intel Edison platform. After September 15, 2017, Intel will archive its online resources and maintain availability to the Intel Edison community until June 15, 2020. Files licensed under open source licenses will continue to be generally available in binary and source code on GitHub.

There is predicted to be plenty of stock through the end of the year, so Edison is continuing to be the recommended setup for now and will be supported by the community into the future.
There's ongoing work to adapt the Explorer Board to other devices (still TBD for final decision, but PiZeroW and CHIP are contenders) and find the next recommended hardware solution, which will then be added to the docs once it's decided and available.
Whichever solution, it will be Linux based so software won't need revision, just new setup instructions.

Excellent.
My $0.0001 worth... Chip would get my vote for not relying on flaky SD
cards for the holding the OS. I know there will be many other aspects to
consider though!
On 2017-07-24 4:57 p.m., Dana Lewis wrote:

There is predicted to be plenty of stock through the end of the year,
so Edison is continuing to be the recommended setup for now and will
be supported by the community into the future.
There's ongoing work to adapt the Explorer Board to other devices
(still TBD for final decision, but PiZeroW and CHIP are contenders)
and find the next recommended hardware solution, which will then be
added to the docs once it's decided and available.
Whichever solution, it will be Linux based so software won't need
revision, just new setup instructions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openaps/docs/issues/976#issuecomment-317552453,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGfsiQFwpQ_pgshb_nOyBT0bDqwnKB-Nks5sRQU4gaJpZM4Ohuia.


EventReader::iter() is confusing as it moves the cursor of events read

What problem does this solve or what need does it fill?
I would like to propose to consideration the following thing: usually, in Rust there is a function iter() that allows to iterate containers multiple times without consuming elements of the container. And the fact that EventReader has a function named iter() that consumes events is making me a bit confused. I'm totally agreed, that the consuming of the events is necessary while iterating them, but I have a case in which it doesn't seem to work:

First of all I iterate dog's entities for ticking their timers (every dog has it's own timer). And in the inner cycle I iterate events, so I need to save them into the Vec in the beginning of the system.
What solution would you like?
Either you could rename iter() to something like iter_once (or anything else you'll prefer) to make it more noticeable that the event is consumed in this system, or you can create another iterator that won't consume the events
What alternative(s) have you considered?
A workaround here is to create a Vec (for instance) to save events, but this Vec could theoretically allocate excess memory for events that are copied and have big size. I know, that practically it's almost impossible, but still...
Additional context
I'm new in Rust and therefore I can be wrong, so if it's a peace of garbage, never mind :)

Yeah, this is a bit confusing: it advances the iterator specific to this system param's view of events.
This is both not quite "drain" or "consume" like behavior, but also surprising for those who want to reuse the iterator in the same system.
In your particular case, you could add two EventReader system parameters to your same system, each of which will have their own tracker. Just a workaround, but hopefully helpful.

Thank's a lot! I'll try it out :)


[FEATURE] : Add the icon for experimental

Describe the solution you'd like
Add the icon for experimental equipment

Task :

[ ] Add the experimental icon
[ ] Place SVG in ts file


Installation failed

Hi,
I didn't find how to reopen a closed ticket, the solution provided doesn't change anything.
https://github.com/treeDiM/StackBuilder/issues/125
I'm fully available and can even provide access remotly for testing (teamviewer for example).
Again fresh install of windows, machine totaly dedicated to this.
Thanks yannick
Hi,
following the instructions on a fresh win2012R2 virtual machine fully updated.
.Net framework 4.7.2
IIS 8.59.600.16384
Web Deploy 3.6
The package CMD returns following message:
_Windows PowerShell
Copyright (C) 2014 Microsoft Corporation. Tous droits r‚serv‚s.
PS C:\Users\administrateur.BDMB> cd C:_install\treeDiM.StackBuilder.Installer_toBeExtracted
PS C:_install\treeDiM.StackBuilder.Installer_toBeExtracted> .\treeDiM.StackBuilder.WCFAppServ.deploy.cmd /Y
SetParameters from:
"C:_install\treeDiM.StackBuilder.Installer_toBeExtracted\treeDiM.StackBuilder.WCFAppServ.SetParameters.xml"
You can change IIS Application Name, Physical path, connectionString
or other deploy parameters in the above file.
Start executing msdeploy.exe
"C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -source:package='C:_install\treeDiM.StackBuilder.Installer
toBeExtracted\treeDiM.StackBuilder.WCFAppServ.zip' -dest:auto,includeAcls="False" -verb:sync -disableLink:AppPoolExtens
ion -disableLink:ContentExtension -disableLink:CertificateExtension -setParamFile:"C:_install\treeDiM.StackBuilder.Inst
aller_toBeExtracted\treeDiM.StackBuilder.WCFAppServ.SetParameters.xml"
InfoÂ : Ajout de sitemanifest (sitemanifest).
InfoÂ : CrÃ©ation de lâ€™application (StackBuilderWCFAppServ)
InfoÂ : Ajout du chemin dâ€™accÃ¨s virtuel (StackBuilderWCFAppServ)
Code d'erreurÂ : ERROR_SITE_DOES_NOT_EXIST
Informations supplÃ©mentairesÂ : Le site 'StackBuilderWCFAppServ' n'existe pas. Pour en savoir plusÂ : http://go.micros
oft.com/fwlink/?LinkId=221672#ERROR_SITE_DOES_NOT_EXIST.
Nombre d'erreursÂ : 1.
PS C:_install\treeDiM.StackBuilder.Installer_toBeExtracted>
I tried iisreset, reboot several times, admin powershell console....
Is there a manual way to install the APP ?
Regards, Yannick

I'm still in the same place.

Holidays ?
I would like to provide the service to my users... anyone can help there ?

Was ASP.NET component installed on the machine?
I will make a video of the installation...

Many Thanks @fgasnier71 for the video.
But yes, I've the ASP.NET installed.

I've created manually a site called "StackBuilderWCFAppServ". Creating the directory
Do the normal installation.
It's running.
=]
Next step? Crate a Wep page to use the service.

Thanks @fgasnier71 !!

So, finally the site needed to be created manually?
Le mer. 22 août 2018 à 15:12, norman masià<EMAIL_ADDRESS>a
écrit :

I've created manually a site called "StackBuilderWCFAppServ".
Creating the directory
Do the normal installation.
It's running.
=]
Next step? Crate a Wep page to use the service.

Thanks @fgasnier71 https://github.com/fgasnier71 !!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/treeDiM/StackBuilder/issues/126#issuecomment-415026688,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcSZ-GPGKbDL1EoCREjvQyucbfbWyg1ks5uTVjAgaJpZM4Vn-fr
.

Hi manually it did work.
I was trying to go to next step, but website totally changed !! I cant find the example anymore.
Donwloading the last version doesn't requiere a server anymore ?!
I'm lost !

If you want to install the web service you still need a server.
See issue #125

I mean this page totally changed :
http://www.treedim.com/stackbuilder/fr/telechargement

There is only info for the client, that is totaly operationnal standalone pointing on your online azure server

Is the internal server setup still supported, what is the "plus" to do so ?

http://plmpack.com/stackbuilder/ClickOnce/treeDiM.StackBuilder.Desktop.application

This simple link does everything


First pass at OAK termset similarity implementation

FYI the api call function I put in semsim.py is like six different kinds of broken


WSL 2 shows a KMODE_EXCEPTION_NOT_HANDLED BSOD upon installing a distro.

Windows Build Number
Microsoft Windows [Version 10.0.22000.194]
WSL Version

[x] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Enable Windows Subsystem for Linux feature.
Change to WSL 2 with wsl --set-default-version 2.
Install 'Ubuntu' from Microsoft Store.
Launch the Ubuntu application.
Expected Behavior
Ubuntu installs itself and shows first time setup.
Actual Behavior
The window shows 'Installing, this may take a few minutes`. Then, after 2-3 seconds the whole system hangs and then a BSOD pops up with error KMODE_EXCEPTION_NOT_HANDLED. The file that it shows is dxgmms2.sys.
Diagnostic Logs
No response

I'm having the exact same issue after installed Windows 11. I've tried to find for some solution, but I didn't have any success.. Idk, but seems like it's some kind of incompatibility between the Windows 11 kernel and the graphic drivers currently available - in my case, AMD. Guess we'll have to wait for updates..

Hi guys, did you had a chance to solve issue?

Nope, still using Windows 10 with WSL2 as I thought that my processor/motherboard is old enough for everything to break on Windows 11. However, using Windows 11 on a 9 year old unsupported laptop is flawless and even WSL2 works fine. Maybe it's about the difference between Intel and AMD processors.


Add Fitbit provider to readme

The provider itself is of high quality, but the current FitbitUser implementation is very limited and does not return all of the user information in the toArray method. I have opened an issue about this.


Need static Framework

Hi, can you generate a static library, because dynamic libraries cannot be placed in the SDK，thank you

@Miko-J
hi Miko!
Can you tell me why I need a static framework?
Thanks 👍

Hi, I need static library too, because I want to combine Naver SDK to my SDK, so the users of my SDK only need to deal with one framework. Thank you very much!!!


Custom Appender in Javascript Code

Custom Appender in Javascript Format
| Type                     |  Version |
| -------------- ---- | -------- |
| Question              | 6.1.2      |
Description
We have multiple examples of multiple custom appenders in TS, can we have a simple Custom Appender in Javascript. A sample example would help to use the logger in JS.
Please let me know, if there is a sample example of this.

Finally we are able to write one. Thanks.


[ubuntu-base] [ubuntu-22.04] ssh keys don't work in ubuntu-base image

I am creating a simple devcontainer based on the base images stored here.
I have tried two images:

mcr.microsoft.com/vscode/devcontainers/base:ubuntu-22.04
mcr.microsoft.com/vscode/devcontainers/base:bullseye

Using the bullseye image, ssh keys are passed from the host automatically.
In the ubuntu-22.04 image, they are not?
I have checked the ubuntu-20.04 image and they work fine also. Seems to be isolated to the 22.04 image?

Hi 👋
Thanks for reporting the issue. Looks like it's similar to problem mentioned in https://github.com/devcontainers/images/issues/650#issuecomment-1692898082
@alexander-smolyakov Can you help investigate this issue? Thank you!

I just hit this same issue.  It's very strange since I can see my keys show up in the vs-code terminal when i run ssh-add -l  however when I try to do ssh -T<EMAIL_ADDRESS>or any other git operations I get a permission denied (public key) error

Same with debian:bookworm. ssh-add -l correctly returns the identity but authenticating with git or ssh fails with an error message somewhere in the log: get_agent_identities: ssh_fetch_identitylist: communication with agent failed
It seems to be some kind of incompatibility with different OpenSSH versions, see also https://github.com/microsoft/vscode-remote-release/issues/7525

Thanks @Roemer for pointing it out. Closing as this looks like an upstream issue!
Might be worth looking at https://github.com/microsoft/vscode-remote-release/issues/7525#issuecomment-1354742843 and upgrading OpenSSH for Windows.


Replace casts of &T to &mut T with UnsafeCell

Specifically we cast *const T to *const UnsafeCell<T> then use the UnsafeCell::raw_get method.

Casts of &T to &mut T are UB. Caught by this lint.

Changes to the SPI implementation validated on hardware


[release]: Data Prepper 2.2.0

Did you read the on-boarding document
Yes
What is the name of your component?
Data Prepper 2.2.0
What is the link to your GitHub repo?
https://github.com/opensearch-project/data-prepper
Targeted release date
04/20/2023
Where should we publish this component?
Publishing to Docker Hub, ECS, opensearch.org artifacts, Maven Central.
The current Jenkins job publishes these.
What type of artifact(s) will be generated for this component?
Docker image
tar.gz artifacts
Maven artifacts
Have you completed the required reviews including security reviews, UX reviews?
Not at this time, though we are in the process and will release only after completion.
Have you on-boarded automated security scanning for the GitHub repo associated with this component?
Yes.
Additional context
Data Prepper builds artifacts using GitHub Actions. This will publish to staging repositories. Our team is responsible for this portion. We will need the opensearch-build team to run the Jenkins job which promotes these to production.
A Data Prepper maintainer will supply the DATA_PREPPER_BUILD_NUMBER parameter.
Parameters:
VERSION: 2.2.0
RELEASE_MAJOR_TAG: true
RELEASE_LATEST_TAG: true
DATA_PREPPER_BUILD_NUMBER - To be supplied later.

VERSION: 2.2.0
RELEASE_MAJOR_TAG: true
RELEASE_LATEST_TAG: true
DATA_PREPPER_BUILD_NUMBER - 51

https://build.ci.opensearch.org/job/release-data-prepper-all-artifacts/
Data Prepper 2.2.0 is released https://aws.oss.sonatype.org/content/repositories/releases/org/opensearch/dataprepper/data-prepper-api/2.2.0/


Can this be used in xamarin?

Can this be used in xamarin?
I want to develop v2ray for Android and IOS

The sdk nuget package:

Based on .NET Standard 1.5, Xamarin.iOS 10.0 or Xamarin.Android 7.0 is required.
For more information, check here.

But this tool project has only been tested under Windows.

The sdk nuget package:

Based on .NET Standard 1.5, Xamarin.iOS 10.0 or Xamarin.Android 7.0 is required.
For more information, check here.

But this tool project has only been tested under Windows.

The sdk nuget package:

Based on .NET Standard 1.5, Xamarin.iOS 10.0 or Xamarin.Android 7.0 is required.
For more information, check here.

But this tool project has only been tested under Windows.

If we can support. Net standard 2.0 and develop custom VPN protocol in IOS and Android, it will be a great project,.

The sdk nuget package:

Based on .NET Standard 1.5, Xamarin.iOS 10.0 or Xamarin.Android 7.0 is required.
For more information, check here.

But this tool project has only been tested under Windows.

If we can support. Net standard 2.0 and develop custom VPN protocol in IOS and Android, it will be a great project,.

There may be a misunderstanding here, let me clarify:
This project is V2Ray Grpc API client implemention, an SDK to interact with a running V2Ray server, NOT the dotnet implemention of V2Ray Core.
If you are looking for a VMESS protocol client implement, this project does not meet your requirements.

There may be a misunderstanding here, let me clarify:
This project is V2Ray Grpc API client implemention, an SDK to interact with a running V2Ray server, NOT the dotnet implemention of V2Ray Core.
If you are looking for a VMESS protocol client implement, this project does not meet your requirements.


Feature: Allow routing demonstration

I'm not sure if it's technically possible, but it would be neat if it webpackbin allowed routing demonstrations. I'm thinking mainly react-router. I don't know what this would take technically, though.

Yeah, this is possible I believe, just have to expose a fake addressbar for the iframe and back/forward buttons. Have to research a bit


Switch go-kit/kit/log to go-kit/log in HTTP SD

When #8927 merged I didn't have the new HTTP SD in my branch so that file slipped by the change.

Thanks!


Styling Image - React Native

Hello everyone, I had a screen using an Image tag to display a background image. With default react native styling it works, but when I tried to convert to a styled component, if returned an error.
The js:
import React, { Component } from 'react';
import { Image } from 'react-native';
import styled from 'styled-components/native';

const bgImage = styled.Image`
  flex: 1;
  width: undefined;
  height: undefined;
  background-color: transparent;
  display: flex;
  align-items: center;
  justify-content: center;
`;

export default class LoginScreen extends Component {
  render() {
    return (
      <bgImage source={require('../images/login_bg.jpg')}>

      </bgImage>
    );
  }
}

The error in the simulator:
Expected a component class, got [object Object].

I have other components using TextInput ou TouchableHighlight, and the styling is working perfectly.

Your components have to begin with an upper case letter. This way React knows that you want to render a component and not a normal element.

Jesus... Thanks a lot @k15a, that is embarassing.
Here is the working class, because some of the styling was also unsupported:
import React, { Component } from 'react';
import { Image, Text } from 'react-native';
import styled from 'styled-components/native';
export default class LoginScreen extends Component {
render() {
return (
<BgImage source={require('../images/login_bg.jpg')}>
Test

);
}
}
const BgImage = styled.Image  background-color: transparent;   display: flex;   align-items: center;   justify-content: center;;

Yes this is not supported:
width: undefined;
height: undefined;

FYI you can use code fences to hightlight code in GitHub issues:
```js
// code
```


[Bug]fix radarr flowchart guide for 4k

Which Guide
Please add which Guide you found a Bug/Error with.
radarr cfs
Describe the Error in the Guide
A clear and concise description of what the bug is.
flow chart gudie for remux + web points to 1080p and 2160p without considering if they want 4k
redo flowchart and guide for remux + web to have a branch of 4k/1080p so the proper quality profile can be more easily referenced

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
That flowchart guide is slightly off since it points the web remux to both 1080 and 4k but ignored the 4k of not question
Additional context
Add any other context about the problem here.

One of the first flowcharts concepts had that option
What resulted in some weird loops in the charts or even adding HDR formats to 1080p or it got as huge and complicated as the tracker chat
And when you need to scroll from left to right from top to bottom and back, it's getting more complicated then needed
And I would need to add another full described quality profile.
Now we can say he you want 1080p and 2160p remuxes, just follow and add both to 1 qualify profile

I think the first question should be 4k or not and then go from there?  Have we explored that as a tree?

Yes and then I get 2x the question if you want remuxes or encodes
One for the 1080p and one for the 2160p
And the same counts for the audio formats


Set up a first benchmark

AIUI a good first candidate for benchmarking might be the tx-parser: https://github.com/mozilla/mentat/blob/rust/tx-parser/tests/parser.rs.
There's built in support for benchmark tests: https://doc.rust-lang.org/book/benchmark-tests.html, so let's try to use them if possible.

After adding a benchmark test for tx-parser, it can be run with cargo bench --package mentat_tx_parser

@ncalexan wanted to get some feedback on the approach here before opening a PR.

Any opinion on whether to incorporate these in the code or an external folder?  Here's some code that does benchmarks in-file and here's some that does benchmarks in a separate file.  I'm leaning towards the latter myself so that we could see all benchmarks in one place, but I'm not sure if there's a criteria you've been using for when a test should be inline vs external that might be relevant here.
Any opinion on what to actually benchmark? Both examples above use the same code which I sniped / modified from some of the tests in tx-parser/src/lib.rs and are basically running Tx::parse through a situation with a small and large sample of edn.

@ncalexan wanted to get some feedback on the approach here before opening a PR.
Any opinion on whether to incorporate these in the code or an external folder? Here's some code that does benchmarks in-file and here's some that does benchmarks in a separate file. I'm leaning towards the latter myself so that we could see all benchmarks in one place, but I'm not sure if there's a criteria you've been using for when a test should be inline vs external that might be relevant here.

Slight preference for external folder (benches?), like we have tests (for some things).

Any opinion on what to actually benchmark? Both examples above use the same code which I sniped / modified from some of the tests in tx-parser/src/lib.rs and are basically running Tx::parse through a situation with a small and large sample of edn.

This useful, for sure.  I've been thinking of the combinatorial product of:

{N assertion,N retraction} for N=1,2,3,4,5,10,50,500,5000
:db/cardinality :db.cardinality/{one,many}
{:db/unique :db.unique/identity} where it makes sense

Into an empty store, and into a store with N=1,10,100,1000,10000,...1e6 existing datoms/transactions.

Slight preference for external folder (benches?), like we have tests (for some things).

Sounds good to me, I'll proceed with that branch.


Execution failed for task ':app:mergeLibDexDebug'.

Bug report

Summary

Execution failed for task ':app:mergeLibDexDebug'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.

Failed to transform classes.jar (project :react-native-maps) to match attributes {artifactType=android-dex, com.android.build.api.attributes.BuildTypeAttr=debug, com.android.build.api.attributes.VariantAttr=debug, dexing-enable-desugaring=true, dexing-incremental-transform=false, dexing-is-debuggable=true, dexing-min-sdk=29, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.

Execution failed for DexingNoClasspathTransform:

Environment info

react-native info output:
info Fetching system and libraries information...
System:
    OS: macOS 11.2.3
    CPU: (4) x64 Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz
    Memory: 101.10 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.10.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.5.3 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 29, 30
      Build Tools: 28.0.3, 29.0.2
      System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>42882
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_282 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.4 => 0.63.4
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

"react-native-maps": "0.27.1"
"react-native-geolocation-service": "^5.2.0"
"react-native-maps-directions": "^1.8.0"

"@react-native-firebase/app": "^11.5.0"
"@react-native-firebase/messaging": "^11.5.0"

Steps to reproduce

Setup react-native-maps, react-native-geolocation-service and react-native-maps-directions. Working properly after that Installed firebase for Push Notification.
@react-native-firebase/messaging setup from given steps

Describe what you expected to happen:

The project must run on Android. In iOS, the project is running without any conflicts.
Describe what you actually happens:

Getting
Execution failed for task ':app:mergeLibDexDebug'.
In Android
Reproducible sample code

Closing for now. If you believe that this is still relevant, please feel free to open a new issue.


Disable main window

How would I disable interactions on the main game window while a dialog is open? I can't seem to find a way to do it with Godot.

The best solution is to create a control node that occupies the entire screen, setting its mouse filter flag to stop. Then, make this node visible whenever you want the user to not interact with the UI, and hide it again to give control back to the user. I found this trick here

That would work, however I am looking for something like the Windows Notepad Save File as dialogue where it completely blocks access to the main window until the save dialog is finished.

Not sure if that is possible, sorry

I looked into other solutions and Godot 4's new Window class with the Exclusive and Popup flags set actually works exactly how I would want it.
Is there any possibility to include some if not all of the new Window class flags into this project for Godot 4?
I can manage all this from my own game of course but would be nice if it was built in.

My current solution is to simply open a new Window 1x1px in size at position x: -1, y: -1 making it invisible and disabling all rendering related things associated to it. Its not a perfect solution since it doesn't force the dialogs to the top when you click the main window but hopefully I can find a solution to that soon, might be some way to associate the dialogs to the new window.

The only thing I can think of is to detect the user focusing on your program's main window to call the show method again. The library I use for this plugin doesn't have the option to make the windows it creates to be always on top, unfortunately.

Here is how you may achieve that:
var window: Window = get_viewport()
window.connect("focus_entered", show)

Tried it and it doesn't really work as intended, it just ends up creating an infinite loop of reopening the dialog if you close it.
I did however find something else, create a sub-window with the properties "transient, exclusive and popup_window" set it never forces the Godot window above any other application except for tabbing into it, including the dialogs. Effectively this completely disables any input into the main game window as long as the popup is open.
One caveat though is that the option embed_subwindows must be disabled on the parent window for the OS controls (only tested on Window btw) to be disabled on the window, otherwise it simply disables any standard Godot inputs. Not sure if there would be a better solution with a different plugin perhaps, this seems to be about as much as I can do with the current setup.

From what I saw in the Popup class, they disable some of the window properties so I imagine you would be able to do so with any property.
Also I think in this case the embedded subwindows option on the parent is more negative than positive since it completely disables OS controls, including dragging the window around, resizing, and using the OS buttons. Leaving it true (default) only prevents normal Godot inputs.
I do think that there may be a bit too many inconsistencies with implementing such a thing though, say someone did change embedded subwindows to false then this addons functionality would change along with it and there is also a potential performance draw from just inheriting from Window in the first place.

Yeah, that's why I think documenting this workaround is the best option. Just inform people about this solution and let them judge if it fits their use case.


Feature Request: Does this support OTP field?

Feature Requested
Thank you for developing this excellent workflow, I'd like to ask that the OTP field is supported now or is there a plan to follow up with support?
Relevant Screenshot
No response
Checklist

[X] The feature would be useful to more users than just me.

There is currently no OTP support. You mean with pass-otp I assume?
Since I am neither using the feature myself, and since it's an extension for pass (meaning far fewer people will use it), I am afraid I don't have any plans to add support for that in the foreseeable future.


chore(types): Added types for plugin options and removed ts-ignore

What does it do?
Added plugin options type so that we do not need to use @ts-ignore
I also tried fixing some eslint errors, but I am still getting some and it seems like eslint cannot infer the type correctly, maybe a new version is needed @boazpoolman
Why is it needed?
We should avoid using @ts-ignore when it is possible

I think the problem here is eslint, if you hover over the values in your editor you will see that the types are not any as eslint says. So I think at least the @typescript-eslint/parser needs to be updated, but that also means all the eslint plugins should probably be updated too. The eslint dependencies is not defined in this project, so I am not quite sure how to update all of them.

I see. The issues are rather eslint instead of hard Typescript errors.
But then still; this is not an issue in the head monorepo branch. Meaning that something in this PR is causing these linting warning to occur.

Yes, you're right, the errors only occur when the declare module part in the strapi.ts file is there.

I suspect it has something to do with the location of the /types/generated files.
Those are generated and read by @strapi/strapi to strictly type it's return types.
For example the response of strapi.entityService is modified like that.
Those files are just magically picked up by @strapi/strapi as it expects it to be in the /types/generated location.
Maby if we move the declare module @strapi/strapi we also need to move that types folder to reflect that change?
That's the only thing I can think of.

I don't think strapi expects the typing files to be anywhere, I think it is entirely up to what we set in the typeroots or include  in the tsconfig file.
The way that we override Schema in this PR seems to be correct since typescript does pick up the correct types, however it is only eslint that fails to get the types right. I did find some issues on some eslint repos about similar issues, so it might not be possible to fix right now.
I tried to install newer versions of the typescript eslint parser and the plugins, but it did not make any difference.

I think we may just have to resort to using @ts-ignore and as boolean. It's not ideal, but extending the @strapi/strapi types like this just gives to much issues. Let's hope the PluginOptions will just be properly typed by strapi one day.

Yeah, you are probably right and we don't know how long it takes for a fix to be release for eslint.
However Imo I think it would be better to use @ts-expect-error instead of @ts-ignore so that when the types work one day, we can easily remove all the @ts-expect-errors :)

Fine by me!

Just took another jab at making this work but was unable to.
I'll close this PR in favor of #91


Pornhub playlist download

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.01.16
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.01.16
[debug] Python version 2.7.15rc1 (CPython) - Linux-4.4.0-19041-Microsoft-x86_64-with-Ubuntu-18.04-bionic
[debug] exe versions: none
[debug] Proxy map: {}

Description

A couple of days ago, youtube-dl stopped downloading playlists from pornhub.
I see the download in the log, but everything freezes on one line Downloading m3u8 information and "dies".

Most likely network issues on your side.

Most likely network issues on your side.


material-ui-next.com does not load under Firefox, but material-ui.com does

Under  FF 60.0.2  (MacOS), with all extensions disabled, material-ui-next.com loads incompletely and the main (hamburger) menu does not function:

In the console, the error is:
Loading failed for the <script> with source “https://material-ui-next.com/_next/bff046c5-ac42-48c3-bfca-ab3449dac015/page/index.js”.
material-ui-next.com:38
Loading failed for the <script> with source “https://material-ui-next.com/_next/bff046c5-ac42-48c3-bfca-ab3449dac015/page/_error.js”.
material-ui-next.com:38
Loading failed for the <script> with source “https://material-ui-next.com/_next/bff046c5-ac42-48c3-bfca-ab3449dac015/main.js”.

material-ui.com, thankfully, works just fine.

[x] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
I go to material-ui-next.com and can use it.
Current Behavior
The hamburger menu is broken under FF 60.0.2 MacOS (no extensions enabled)
Steps to Reproduce (for bugs)

Navigate to material-ui-next.com
Attempt to use hamburger menu

Context

I was trying to use the site.

Your Environment

MacOS X FF 60.0.2 no extensions

@liz-mars material-ui-next.com is legacy, use material-ui.com.


cdk deployments on aws get stuck

Over a sample of a dozen automated deployments on aws, 30% of them get stuck at a stage like the following:
http://paste.ubuntu.com/p/KSJ8yh3gPh/
The minimal repro case is as follows:
wget https://api.jujucharms.com/charmstore/v5/canonical-kubernetes/archive/bundle.yaml
sed -ri 's/series: bionic/series: xenial/g' bundle.yaml
sed -ri 's/num_units: ./num_units: 1/g' bundle.yaml
juju add-model cdk
juju deploy ./bundle.yaml
juju deploy cs:~containers/aws-integrator
juju add-relation 'aws-integrator:aws' 'kubernetes-master:aws'
juju add-relation 'aws-integrator:aws' 'kubernetes-worker:aws'
juju trust aws-integrator

As a workaround, the errors get resolved by just rebooting the units.
results-2018-12-09-18-46-44.tar.gz

This is the same issue as https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/702, which was fixed by https://github.com/juju-solutions/layer-etcd/pull/145, which was released to the stable charm channel on Dec 7.
@iatrou once you start using the latest stable etcd charm (rev 332+), you should no longer see this issue. Please let us know if you do.


Update app-custom-theme.md

Updating syntax in doc for clean up of Theme object
Signed-off-by: Damola Obaleke<EMAIL_ADDRESS>Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Thanks for taking the time to correct this, much appreciated!

No prob!


[SPARK-16367][PYSPARK] Support for deploying Anaconda and Virtualenv environments in Spark Executors

What changes were proposed in this pull request?
Support automatic deployment of Anaconda or virtualenv environment on executor, and add wheel and wheelhouse support to PySpark, based on SPARK-13587 (see #13599).
Full description in SPARK-16367
The developer write its Python code and it describes the dependencies of this script (numpy, pandas, requests,...) inside a requirements.txt file. When the job will be deployed on the executor (and when the driver will be deployed in cluster mode), the same environment will be automatically setup using pip (or conda).
 Could be a wheel as well, eventhough distributing a source package for the job is safer.
I have described a bit more this approach here
In bonus, this PR adds support for "wheelhouse" deployment, where all dependencies are packaged into a single archive, so that no network connection is needed when Spark executors deploy the environment
How was this patch tested?
Manually tested on Ubuntu, Spark Standalone. Seems to work on YARN cluster as well.

Can one of the admins verify this patch?

@Stibbons, sorry for late review. Let's work together on this PR in the next few days if it is OK for you.

Yes, I'll be glad  ! It is not fully ready yet, I still need to figure out how the script is launched in each situation

ping @Stibbons  Any updates ?

Yes I am back from vacation! Can work on it now :)

Opened #14567 with Pep8, import reorganisations and editconfig.

Rebased, without import reorg and editorconfig files. Still not fully validated.

@Stibbons Do you have time to continue this work ?

Actually I was waiting for #14567 to be reviewed and merged :(
I might have some questions on how Spark deploys Python script on YARN or Mesos if you know how it works

I can help if you have any question regarding spark on yarn.  For mesos, since not so many people use it, we may put it another ticket.

We are implementing Mesos here (may take a while). While not so many people use it, on the paper it looks great ;)
Please mail me at gaetan[a t]xeberon.net if is easier for you (it is for me), this patch does not do the job completely for the moment :(

@Stibbons  After second review your PR, I have one concern that may be support wheelhouse and virtualenv in one PR is too big to review, it might be better to do it in 2 PRs. I will try to get some feedback on #13599 first, but will continue look at this PR.

It makes sense. If you manage to get this merged I can rebase with only my diff.
Too bad we cannot stack pull requests on github :(

This new version is meant to be rebased after #13599 is merged.
Here is my current state:

only Standalone and YARN supported. Mesos not supported
only tested with virtualenv/pip. Conda not tested
wheelhouse deployment works (ie, all dependencies can be packaged into a single zip file and automatically and quickly installed on workers).
for example, deploying a package with numpy + pandas + scitkit-learn is fast once the installation has been done at least once on all workers, and if the wheelhouse provides all wheel on for all version, pip will install everything without internet connection and very fast)

I'd like to have the same ability to specify the entry point in Python that we can do in Java/Scala with the --class argument of spark-submit.

Status for test 'standalone install, 'client' deployment":

virtualenv create and pip install Pypi repository: ok (1 min 30 exec)
wheelhouse (Pypi repositoy): ko, because 'cffi' refuses the built wheel. Not related to this patch, but require more effort on documentation.

Test deploys a job that depends from many popular Pypi packages, among them Pandas, Theano, Scikit-learn,...):
alabaster==0.7.9
arrow==0.8.0
astroid==1.4.8
attrs==16.1.0
autopep8==1.2.4
Babel==2.3.4
backports.functools-lru-cache==1.2.1
BeautifulSoup==3.2.1
bolt-python==0.7.1
boto==2.42.0
cffi==1.7.0
click==6.6
configparser==3.5.0
cryptography==1.5
cycler==0.10.0
dask==0.11.0
decorator==4.0.10
docutils==0.12
enum34==1.1.6
findspark==1.1.0
first==2.0.1
flake8==3.0.4
funcsigs==1.0.2
futures==3.0.5
hypothesis==3.4.2
idna==2.1
imagesize==0.7.1
ipaddress==1.0.16
isort==4.2.5
Jinja2==2.8
jira==1.0.3
kerberos-sspi===0.1-intel
lazy-object-proxy==1.2.2
linecache2==1.0.0
MarkupSafe==0.23
matplotlib==1.5.2
mccabe==0.5.2
mock==2.0.0
mpmath==0.19
ndg-httpsclient==0.4.2
networkx==1.11
nltk==3.2.1
nose==1.3.7
numpy==1.11.1
oauthlib==1.1.2
panda==0.3.1
pandas==0.18.1
pathlib==1.0.1
pbr==1.10.0
pep8==1.7.0
Pillow==3.3.1
pip-tools==1.7.0
py==1.4.31
pyasn1==0.1.9
pyasn1-modules==0.0.8
PyBrain==0.3
pycodestyle==2.0.0
pycparser==2.14
pycrypto==2.6.1
pyflakes==1.2.3
PyGithub==1.26.0
Pygments==2.1.3
pylint==1.6.4
pyOpenSSL==16.1.0
pyparsing==2.1.8
pytest==3.0.1
python-dateutil==2.5.3
python-ntlm==1.1.0
pytz==2016.6.1
PyYAML==3.12
-e git+ssh://gsemet@android.intel.com:29418/a/qsi/spark@1af5c148f8f2d55f6f26a067a822f722528e13b9#egg=qsi_jobs
requests==2.11.1
requests-aws4auth==0.9
requests-kerberos===0.6.1-intel
requests-oauthlib==0.6.2
requests-toolbelt==0.7.0
scikit-image==0.12.3
scikit-learn==0.17.1
scipy==0.18.0
service-identity==16.0.0
singledispatch==<IP_ADDRESS>
six==1.10.0
sklearn-pandas==1.1.0
snowballstemmer==1.2.1
spark-testing-base==0.0.7.post2
Sphinx==1.4.6
suds==0.4
sympy==1.0
Theano==0.8.2
thunder-python==1.4.2
tifffile==0.9.2
tlslite==0.4.9
toolz==0.8.0
traceback2==1.4.0
Unidecode==0.4.19
unittest2==1.1.0
urllib3==1.16
wrapt==1.10.8
-e git+ssh://internal.server.com/a/project/name@7f4a7623aa219743e9b96b228b4cd86fe9bc5595#egg=projectname
yapf==0.11.1

Execution of this installation takes 1 min on each executor, thanks to pip and wheels being downloaded from our internal pypi.python.org mirror:
16/08/30 17:07:47 DEBUG PythonWorkerFactory: Running command: virtualenv_app-20160830170740-0000_0/bin/pip install -r requirements.txt --index-url https://internal.pypmirror/artifactory/api/pypi/pypi-prod/simple --trusted-host internal.pypmirror qsi-jobs-0.0.1.dev15.tar.gz
16/08/30 17:08:58 DEBUG PythonWorkerFactory: Starting daemon with pythonExec: virtualenv_app-20160830170740-0000_0/bin/python

Hello. Can someone help to review this PR? I find the current way Spark handle Python programs really problematic, with this proposal (based on top of #13599), jobs deployment becomes so much easier.

I have written a blog post about this pull request to explain what we can do with it: http://www.great-a-blog.co/wheel-deployment-for-pyspark/

Rebased.

I was going through the old PySpark JIRAs and there is one about an unexpected pandas failure, which could be semi-related (e.g. good virtual env support with a reasonable requirements file could help avoid that) - but I still don't see the reviewer interest required to take this PR forward (I'm really sorry).

cc @holdenk Any thought about this PR?

So I think we need some support for virtualenv/anaconda but this feels a little overly complicated as the first step (and mostly untested) -- maybe starting with a simple supporting running from a specific virtualenv/conda env that is already set up?
What are your thoughts @gatorsmile / @davies ? If there is a consesus with the other people working on Python I'm happy to do some more reviews :)

Here's my approach #13599 for virtualenv and conda support, welcome any comments and reviews
https://docs.google.com/document/d/1EGNEf4vFmpGXSd2DPOLu_HL23Xhw9aWKeUrzzxsEbQs/edit?usp=sharing

cc @ueshin

ping @ueshin Should we continue this PR?

gentle ping @ueshin

Can one of the admins verify this patch?

Is this still being looked into? Or possibly has wheel support been added in another PR?

This doesn't seem active so closing the PR for now.


UPDATE: few additions to README

@madhu-sagar Thank you for your contribution! Team will review the changes and will update you soon.

Architecture Considerations is a new section added.
Helpful tools links are introduced. All the other texts are replaced with the same text with links.
LGTM for merge @sunnypuri


E- mail Issue

**Reopened
Apologies for leaving this on the github, not sure how else to contact you.
My account username: JCDenton, I used a throw-away email address and am unable to actually verify the withdrawl of BTC i am trying to make, will you assist me here?
The registered email begins with t971005
thank you team monyx
action: Confirm Withdrawl

Alternatively change the email to<EMAIL_ADDRESS>thank you

@t971005 changed!


Should we allow setting color for different streams separately?

Is there a case where people want to enable color for stderr but disable it for stdout?
If yes, how would the command line options UX be for a cli to allow the end users to configure this?

The cases I can think of

Piping both, one will go to less, needing to be forced, and the other will go to a file and wanting it to remain disabled
The application's ux is different enough for stdout/stderr that the application wants to (ab)use concolor for controlling its UX

If people can think of more, we can add it to the list.

For me, the cases don't seem compelling enough to deal with the complexity.
Instead, I've been wondering if CLICOLOR_FORCE /  --color=always should still cause the terminal's capabilities to be queried (truecolor, 256color, 16color) or if they should force a specific version of the modes.

How do I move this issue to anstyle?

Without an end-user with a use case for it, I personally wouldn't bother.


Flutter 2.10.2 renamed pie_chart_outlined to pie_chart_outline

Flutter 2.10.2 renamed pie_chart_outlined to pie_chart_outline and so the build fails if I use the dynamic_widget as a dependency on my projects

Flutter 2.10.2 renamed pie_chart_outlined to pie_chart_outline and so the build fails if I use the dynamic_widget as a dependency on my projects

You have to change the name of the icon in the icons_helper.dart file while waiting for the fix

Please fix this

This pull request  #89 from @zhangruiyu  fixes this

@dengyin2000 please checkout this

@dengyin2000 please checkout this

merged by other pr

Sorry, I still get this error with dynamic_widget 4.0.4 and flutter 2.10.4. How I can fix that?


Move ssl_verify to the action variables

Need to create an action variable for ssl_verify instead of a custom resource variable.

Done.

Property aapSSL can be set at the action or as a property.


Default values for parameters

How can I get params with default values within the interactor. For example
class PayParkingTransaction
  include Interactor
  delegate parking_transaction, to: :context

  def call
    puts parking_transaction
  end
end

t = 'test'
PayParkingTransaction.call(parking_transaction: t)

This will output test
t = nil
PayParkingTransaction.call(parking_transaction: t)

This will output nil but I would like to have is a default in this case that when t is nil, it will take a default value. Ofcourse I can set it manually in the interactor but I don't want to do that for all interactors I have. Is there any other better way to achieve this?

If it were me, I'd use a before block in my interactor:
before do
  context.parking_transaction ||= my_default_value
end

If the logic is similar across multiple interactors, you could pull that logic out into a concern that's included in those interactors:
class MyInteractor
  include Interactor
  include TransactionDefaults

  def call
    # …
  end
end

module TransactionDefaults
  extend ActiveSupport::Concern

  included do
    before do
      context.parking_transaction = my_default_value
    end
  end
end

The other thing to do would be to apply your defaults before you pass them into the interactor.
Unfortunately, Interactor just cannot know your intentions. Passing nil into an interactor's context is a perfectly legitimate use case so we don't do any clever protection against that sort of thing.
I hope that helps!

@laserlemon Thanks a lot. Didn't realize that before block was available here. This seems like a perfect solution.


Resolve issues with Merkle Commitments

There is (I believe) an outstanding issue related to the implementation of vector commitments using Merkle proofs.   The problem is that the index is not encoded into the proof.  Specifically, see this comment in BlobMerklization:
// Verify an opening using the Merkle Proof
predicate Verify(c: Commitment, o: Opening, i: nat, m: Message) {
     var last := |o.0|;
     var hashes := o.1;
     // FIXME: this is actually broken because it only verifies that m is
     // contained within the original data, but does not verify the index
     // position.
     hashes[last] == Hasher(m) && Merkle.Verify(o,HashJoin) == c
}

In particular, we can see that the variable i is never used.  I don't quite know how to resolve this though.  Some points:

(Path) There is a relationship between i and the path through tree.
(Length) If the vector length is known (e.g. its fixed at 1024 elements as for KZG) then i can be checked against the path concretely.

One obvious solution is that the last element of the proof is a hash of m and i.  Or, even, that all leaves are hashed with their index.
Q) What do real-world implementations do?

In some sense this could be an interesting "bug" in the implementation.    That is, can we prove there is a problem here?


Devtools/Labs fixes

[ ] Button to output diagnostics (see dx debug stats)
[ ] Reactivity spaces panel startup time
[ ] Reactivity in identity panel devices
[ ] iframe-proxy-runtime.ts close causes runaway error

[ ] Epoch creation in labs.dev.dxos.org test plugin causes negative precentage in devtools

=====

[ ] Add devtools link in test plugin in labs.dev.dxos.org
[ ] Round data progress percentage
[ ] "Restart" button that kills the SharedWorker and reloads the current page
[ ] Navigation from space pipeline table to feed does not work
[ ] Tree view in the storage tab is not foldable
[ ] Indicate which tab is hosting the webrtc connection

https://github.com/dxos/dxos/issues/4701


Dudas[QUESTION]:

Consent

[X] I have searched the existing issues and verified that there is no open issue for the same subject.
[X] I understand that the YTMDesktop Elgato Plugin has NO affiliation with Google, YouTube or the YTMDesktop application.

Question
Soy nuevo usando esta app pero la quiero controlar con mi stream deck pero no consigo hacerlo con el pluggin de streamdeck

I guess this is a /duplicate of #55
Please see my answer there.


How to start and stop Ollama in the process?

What is the issue?
As the title described.
OS
No response
GPU
No response
CPU
No response
Ollama version
No response

As the bare minimum, identify your operating system.

sudo systemctl start ollama
sudo systemctl stop ollama


Gulp

We still have to fix three files mentioned in the gulp task.

See also #1976.

One remark. Rest is ok.

You can merge it if you don't want to fix the three files at the moment.


[COMPILE]Request for Compatibility with Older MSVC Versions

I'm encountering compatibility issues with the current verison of the library on MSVC2017.It seems that the library iwas compiled with the latest MSVC version,making it incompatible with older versions like MSVC 2017,In order to use the library with MSVC2017,could you please provide a version compiled with an older MSVC toolset,such as 2017?This would greatly facilitate compatibility for users like myself who are constrained to older toolsets.Thank you for considering this request

@BreadAndSalt Thanks for the feedback. According to https://learn.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017?view=msvc-170, we will start to use MSVC 2017 to generate Windows libraries for future releases. This should make our library compatible with MSVC 2017 and later versions.
If you are currently in need of a MSVC 2017 version of RDK v0.9, please let us know, we will provide it to you.

@pzhu-flexiv  Thanks for the support! Yes , I am currently in need of a MSVC 2017 version of RDK v0.9, would you please get one for me.
Much appreciate!


Max size of head/tail

I noticed the implementation only increments head/tail atomic size_t variables.
If head/tail reaches the max value of size_t and overflows, does the implementation still perform as expected?

yes, as the two's complement numbers add/subtract correctly across unsigned overflow.