How to move a desktop application child window

I am working with a Windows desktop application. I have child windows for my main window and these child windows sometimes goes out of the screen (monitor). So, how can I display/move these child windows in the screen ?  If possible in JAVA.
I can move the main window to the top left corner of screen, using below code:
Point WndPos = MyDriver.manage().window().getPosition();
WndPos.move(0, 0);
MyDriver.manage().window().setPosition(WndPos);
but, how can I do the same for its child windows ?
I am able to get the child windows of main window using List xpath = MyMainWnd.findElementsByXPath("/");
so, xpath.get(i) is a child window of MyMainWnd that goes out of laptop screen.
String rect =xpath.get(i).getAttribute("BoundingRectangle");
and this rect is showing: Left:-240 Top:0 Width:1048 Height:884
so, how can I show/display/move this child window in my screen

Use alt + space and then send m and then using the arrow key move the window

I tried this but, it did not work:
Actions builder = new Actions(MyDriver);				builder.keyDown(Keys.ALT).keyDown(Keys.SPACE).sendKeys("m").keyUp(Keys.ALT).keyUp(Keys.SPACE);
builder.perform();
builder.sendKeys(Keys.chord(Keys.ARROW_DOWN));
builder.perform();
builder.sendKeys(Keys.chord(Keys.ARROW_DOWN));
builder.perform();


Xcode 7.3: Include of non-modular header inside framework module 'WatsonDeveloperCloud.os_types'

I am having problems to build the framework itself using Xcode 7.3 and the latest code base in the master branch. The carthage command seems to finish successfully and I have the .framework files in my Carthage/Build/iOS folder.

Is anyone else getting this same error?
Thanks in advance.

Thanks for letting us know about this, @luish.
I'm downloading Xcode 7.3 so we can take a look and fix this as soon as possible. Unfortunately, it looks like Apple's servers are being hammered right now, so it might take a little while...

Ok, @glennrfisher, please let me know if you were able to reproduce this issue.
I just found this thread on stackoverflow and it might really be something related to Xcode 7.3.

Apparently I could managed to make it build successfully adding the file config_types.h.in that comes in the libogg-1.3.2 (tar.gz link). To be honest I don't really know if this is a solution. Please take a look at my commit https://github.com/luish/ios-sdk/commit/e94c65a56a3b832a373036d2fe3c23fc6196fd36 and hopefully it might have some light to solve this issue. If it works for you I would be glad to create a pull request with the supposed fix. :-)

Unfortunately, it's going to take some time for us to track down the root cause of this problem and fix it in a way that we're comfortable with. (This StackOverflow question and Github issue also seem to be promising leads.)
Our current plan is to move quickly to get our repository building with Xcode 7.3. Unfortunately, the quickest approach will be to remove the ogg and opus libraries. That will allow us to take the time to investigate the problem in more detail and make the right, lasting changes.
In the mean-time, while we're working to add support for Xcode 7.3, you can still use Xcode 7.2 to build the framework and write programs that use it. Here are instructions for installing Xcode 7.2 side-by-side with Xcode 7.3 and using it:

Download Xcode 7.2
Open the Xcode 7.2 disk image and drag Xcode to your Applications folder.
When prompted that An item named "Xcode" already exists in this location be sure to select Keep Both. This will copy Xcode 7.2 to your Applications directory under the name Xcode copy.
Open your Applications directory and rename Xcode copy to Xcode 7.2.
Open Xcode 7.2. In the preferences panel for Locations set the Command Line Tools to Xcode 7.2 (7C68).

Now Carthage is configured to use Xcode 7.2 at the command-line. And you can continue developing with the Watson Developer Cloud iOS SDK using Xcode 7.2.

I hope that this issue is resolved!

Just want to give everyone an update on our progress so far:

The include of non-modular header error is caused by our use of the Ogg/Opus libraries.
To fix the error, we are removing the Ogg/Opus libraries until we can learn how to properly import and use them with the changes made to Xcode 7.3.
Since the Text to Speech implementation uses Opus-encoded audio, we have switched to using WAV.
However, the WAV header is corrupt, so we wrote a function to manually repair the header.
Most Text to Speech tests now pass, with the exception of the SSML test.

What remains is to investigate why the SSML test fails with WAV. A hexdump of the returned audio seems to suggest that it is OPUS-encoded instead of WAV-encoded. This may be a bug with our request or a bug with the service. Once we have solved this bug, we can re-run the tests and merge the fix to master.

Thanks for the update Glenn!

Thank you for your information!

This was fixed with PR #220.
However, to use the Watson Developer Cloud iOS SDK with Xcode 7.3, you will need to use Carthage to rebuild all dependencies (including pre-built binaries). To do so, navigate to your project directory and run the following command:
carthage update --platform iOS --no-use-binaries

If you have any further issues with Xcode 7.3, Swift 2.2, or anything else, please don't hesitate to post here or open a new issue. We want to make sure that all of you are good-to-go!

Many thanks for the update, @glennrfisher! :+1:


Godot 4.3 Can't Resume from Background on Android

Tested versions

4.3.stable

System information
Android 9 - Godot v4.3.stable - Compatibility
Issue description
Export the Platformer 2d sample project to Android. Open the exported game then bring it to background but can't resume the game when click to the game icon again
Steps to reproduce

Export the Platformer 2d sample project to Android
Install the exported game on Android phone
Click the game icon to open
Bring the game to background
Click the game icon again to back to the game
Notice that the game's not resume and the flash screen is shown
Logcat prints error:  Fatal signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x8a048a40 in tid 23512 (le.platformer2d), pid 23512 (le.platformer2d)...

Minimal reproduction project (MRP)
The Platformer 2d sample project

It happen on Godot 4.2.2.stable and 4.3-dev too. Any workaround at the moment?

Seems to be working fine on these specs
Godot v4.4.dev3 - Android - Single-window, 1 monitor - OpenGL ES 3 (Compatibility) - Mali-G52 -  (8 threads)
https://github.com/user-attachments/assets/6d4833e5-434f-44e7-bbb6-c9d7facecd38

It's working fine for me too on my Android 11 (motorola), Android 13 (Xiaomi) and Android 14 (Xiaomi).
@toannth Are you exporting a release or debug ?

Debug export on Xiaomi Redmi Android 9

I tried with debug too, but cannot reproduce this issue.

Debug export on Xiaomi Redmi Android 9

I cannot reproduce this issue even in debug export.
It looks like your OS is force closing it. We will have to wait until a contributor can reproduce this issue.

By any chance do you have application/config/quit_on_go_back set to true in your General>Application>Config(advanced settings need to be on)?

Debug export on Xiaomi Redmi Android 9

I cannot reproduce this issue even in debug export. It looks like your OS is force closing it. We will have to wait until a contributor can reproduce this issue.

Logcat prints error: Fatal signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x8a048a40 in tid 23512 (le.platformer2d), pid 23512 (le.platformer2d)...


MusicBrainz integration

It would be cool if lyrics could be associated with a MusicBrainz recording ID.
This would be especially useful for music  libraries managed with MusicBrainz Picard or beets.

Second this but due to a different reason. It's common for artists to change their artist name, and sometimes even change the name of the song. It's not ideal to adapt to these changes by making new lyrics with new names. So instead, maybe store extra information regarding artist and song aliases when propagating the database? Or just like the original issue said, associate with one recording ID then do all sorts of things with it when needed.

I was thinking of writing a plugin for Picard that fetches lyrics from LRCLIB, having this would be really useful (assuming the plugin API exposes the recording ID, which I'm 99% sure it does)

@Z-A-Y-D Haven't tried it but you can check out Picard Sozler

@Z-A-Y-D Haven't tried it but you can check out Picard Sozler

This looks like what I was trying to do, didn't see it in Picard's plugin repos. I'll check it out once I'm at the computer with all my music stored on it.

@Z-A-Y-D Haven't tried it but you can check out Picard Sozler

Tried it out a bit, at least currently it isn't of much use to me as it doesn't embed the tags in a way ncmpcpp likes and doesn't download a separate lrc file, so I can't use it with mpv. Probably could be fixed for my own use by changing some paths around in the code.


Error when migrating for MiniTest to RSpec

What Ruby, Rails and RSpec versions are you using?
Ruby version: 2.6.5p114
Rails version: <IP_ADDRESS>
RSpec version: 3.9.0

Observed behavior
I'm trying to migrate my rails application to RSpec. But I'm getting the error uninitialized constant ActiveRecord::Relation when running the specs. It says it's on line 10 of application.rb which is Bundler.require(:default, Rails.env) if defined?(Bundler)
Can you provide an example app?
error message
An error occurred while loading rails_helper.
Failure/Error: require File.expand_path('../config/environment', __dir__)

NameError:
  uninitialized constant ActiveRecord::Base
# ./config/application.rb:12:in `<top (required)>'
# ./config/environment.rb:4:in `require'
# ./config/environment.rb:4:in `<top (required)>'
# ./spec/rails_helper.rb:11:in `require'
# ./spec/rails_helper.rb:11:in `<top (required)>'
# ------------------
# --- Caused by: ---
# NameError:
#   uninitialized constant ActiveRecord::Base
#   ./config/application.rb:12:in `<top (required)>'

Spec
require 'rails_helper'

RSpec.describe Api::V1::CertificateRequestsController, type: :controller do
  describe '#create_v1_4' do
    it 'worked' do
        expect(true).to eq(true)
    end
  end
end

spec_helper.rb
# frozen_string_literal: true

RSpec.configure do |config|
  config.expect_with :rspec do |expectations|
    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
  end

  # rspec-mocks config goes here. You can use an alternate test double
  # library (such as bogus or mocha) by changing the `mock_with` option here.
  config.mock_with :rspec do |mocks|
    # Prevents you from mocking or stubbing a method that does not exist on
    # a real object. This is generally recommended, and will default to
    # `true` in RSpec 4.
    mocks.verify_partial_doubles = true
  end

  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
  # have no way to turn it off -- the option exists only for backwards
  # compatibility in RSpec 3). It causes shared context metadata to be
  # inherited by the metadata hash of host groups and examples, rather than
  # triggering implicit auto-inclusion in groups with matching metadata.
  config.shared_context_metadata_behavior = :apply_to_host_groups
end

rails_helper.rb
# frozen_string_literal: true

# This file is copied to spec/ when you run 'rails generate rspec:install'
puts "Your env: #{ENV.fetch('RAILS_ENV', 'test')}"

require 'spec_helper'
require 'database_cleaner'
require 'pry'

ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../config/environment', __dir__)
# binding.pry

# Prevent database truncation if the environment is production
if Rails.env.production?
  abort('The Rails environment is running in production mode!')
end
require 'rspec/rails'
# include Warden::Test::Helpers
# Warden.test_mode!
# Add additional requires below this line. Rails is not loaded until this point!

# Requires supporting ruby files with custom matchers and macros, etc, in
# spec/support/ and its subdirectories.
Dir[Rails.root.join('spec', 'support', '**', '*.rb')].each { |f| require f }

# Checks for pending migrations and applies them before tests are run.
# If you are not using ActiveRecord, you can remove these lines.
begin
  ActiveRecord::Migration.maintain_test_schema!
rescue ActiveRecord::PendingMigrationError => e
  puts e.to_s.strip
  exit 1
end
RSpec.configure do |config|
  # If you're not using ActiveRecord, or you'd prefer not to run each of your
  # examples within a transaction, remove the following line or assign false
  # instead of true.
  config.use_transactional_fixtures = true

  # RSpec Rails can automatically mix in different behaviours to your tests
  # based on their file location, for example enabling you to call `get` and
  # `post` in specs under `spec/controllers`.
  config.infer_spec_type_from_file_location!

  # Filter lines from Rails gems in backtraces.
  config.filter_rails_from_backtrace!
  # arbitrary gems may also be filtered via:
  # config.filter_gems_from_backtrace("gem name")

  config.before(:suite) do
    DatabaseCleaner.strategy = :transaction
    DatabaseCleaner.clean_with(:truncation)
  end

  config.around(:each) do |example|
    DatabaseCleaner.cleaning do
      example.run
    end
  end
end

test.rb
AwesomeApp::Application.configure do
  MIGRATING_FROM_LEGACY = false
  # Settings specified here will take precedence over those in config/environment.rb

  # The test environment is used exclusively to run your application's
  # test suite.  You never need to work with it otherwise.  Remember that
  # your test database is "scratch space" for the test suite and is wiped
  # and recreated between test runs.  Don't rely on the data there!
  config.cache_classes = true

  # Log error messages when you accidentally call methods on nil.
  config.whiny_nils = true

  # Show full error reports and disable caching
  config.consider_all_requests_local       = true
  config.action_controller.perform_caching = false

  # Raise exceptions instead of rendering exception templates
  config.action_dispatch.show_exceptions = false

  # Disable request forgery protection in test environment
  config.action_controller.allow_forgery_protection    = false

  # Tell Action Mailer not to deliver emails to the real world.
  # The :test delivery method accumulates sent emails in the
  # ActionMailer::Base.deliveries array.
  config.action_mailer.delivery_method = :test
  config.action_mailer.perform_deliveries = true
  config.action_mailer.default_url_options = {host: 'localhost:3000'}

  config.after_initialize do
    Rails.application.routes.default_url_options = {host: 'localhost:3000'}
  end

  config.force_ssl = false

  # Use SQL instead of Active Record's schema dumper when creating the test database.
  # This is necessary if your schema can't be completely dumped by the schema dumper,
  # like if you have constraints or database-specific column types
  # config.active_record.schema_format = :sql

  # Sort the order test cases are executed.
  config.active_support.test_order = :sorted

  # Print deprecation notices to the stderr
  config.active_support.deprecation = :stderr

  ActiveMerchant::Billing::Base.mode = :test

  config.eager_load=false

  config.serve_static_assets = true
  config.static_cache_control = "public, max-age=3600"

  #config.log_level = Logger::INFO

  GATEWAY_TEST_CODE=1.0
  # END ActiveMerchant configuration
end

#require "#{Rails.root}/lib/firewatir_url.rb"

application.rb
# frozen_string_literal: true

require File.expand_path('boot', __dir__)
require 'oauth/rack/oauth_filter'
require 'rack/ssl-enforcer'
require 'rails/all'
require './lib/middleware/catch_json_parse_errors'

Bundler.setup
# If you have a Gemfile, require the gems listed there, including any gems
# you've limited to :test, :development, or :production.
Bundler.require(*Rails.groups)

CLIENT_OPTIONS = ['aswesome.com', 'aswementer'].freeze
DEPLOYMENT_CLIENT = CLIENT_OPTIONS[0]

Struct.new('Expiring', :before, :after, :cert)
Struct.new('Notification', :before, :after, :domain, :expire, :reminder_type, :scanned_certificate_id)
Struct.new('Reminding', :year, :cert)

module AwesomeApp
  class Application < Rails::Application
    # set environment variables
    config.before_configuration do
      env_file = File.join(Rails.root, 'config', 'local_env.yml')
      YAML.safe_load(File.open(env_file)).each do |key, value|
        ENV[key.to_s] = value
      end
    end

    # Settings in config/environments/* take precedence over those specified here.
    # Application configuration should go into files in config/initializers
    # -- all .rb files in that directory are automatically loaded.

    # Custom directories with classes and modules you want to be autoloadable.
    config.autoload_paths += %W[#{config.root}/lib]

    Bundler.require(*Rails.groups)
    # Config::Integration::Rails::Railtie.preload

    # Add additional load paths for your own custom dirs
    %w[observers mailers middleware serializers].each do |dir|
      config.autoload_paths << "#{config.root}/app/#{dir}"
    end

    # Only load the plugins named here, in the order given (default is alphabetical).
    # :all can be used as a placeholder for all plugins not explicitly named.
    # config.plugins = [ :exception_notification, :ssl_requirement, :all ]

    # Activate observers that should always be running.
    # config.active_record.observers = :cacher, :garbage_collector, :forum_observer

    # Set Time.zone default to the specified zone and make Active Record auto-convert to this zone.
    # Run "rake -D time" for a list of tasks for finding time zone names. Default is UTC.
    config.time_zone = 'Central Time (US & Canada)'

    # The default locale is :en and all translations from config/locales/*.rb,yml are auto loaded.
    # config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s]
    # config.i18n.default_locale = :de

    # Configure the default encoding used in templates for Ruby 1.9.
    config.encoding = 'utf-8'

    # Configure sensitive parameters which will be filtered from the log file.
    config.filter_parameters += %i[password password_confirmation]
    # config.action_mailer.default_url_options = { :host => Settings.actionmailer_host }

    # machinist generator
    # config.generators do |g|
    #   g.fixture_replacement :machinist
    # end

    # Rails Api
    config.api_only = false

    # turn off strong parameters
    config.action_controller.permit_all_parameters = true

    config.generators do |g|
      g.test_framework :minitest, spec: true, fixture: false
      g.jbuilder false
    end

    # config.middleware.use OAuth::Rack::OAuthFilter
    config.middleware.insert_before ActionDispatch::ParamsParser, 'CatchJsonParseErrors'

    # Delayed Job
    config.active_job.queue_adapter = :delayed_job

    config.middleware.insert_before 0, Rack::Cors do
      allow do
        origins '*'
        resource '/certificate/*',
                 headers: :any,
                 methods: %i[get post delete put options head],
                 max_age: 0
      end
    end

    # Enable the asset pipeline
    config.assets.enabled = true

    config.sass.preferred_syntax = :sass
    config.sass.line_comments = false
    config.sass.cache = false
    config.action_mailer.default_url_options = { host: 'secure.awesome.com', protocol: 'https' }
    if DEPLOYMENT_CLIENT =~ /certassure/i && Rails.root.to_s =~ /Development/
      paths['config/database'] = 'config/client/certassure/database.yml'
    end
  end
end

require "#{Rails.root}/lib/base.rb"
require "#{Rails.root}/lib/asset_tag_helper.rb"
require "#{Rails.root}/lib/array.rb"
require "#{Rails.root}/lib/range.rb"
require "#{Rails.root}/lib/in_words.rb"
require "#{Rails.root}/lib/kernel.rb"
require "#{Rails.root}/lib/money.rb"
# require "#{Rails.root}/lib/subdomain-fu.rb"
require "#{Rails.root}/lib/domain_constraint.rb"
require "#{Rails.root}/lib/preferences.rb"
require "#{Rails.root}/lib/active_record.rb"
require "#{Rails.root}/lib/active_record_base.rb"
require "#{Rails.root}/lib/hash.rb"
require 'will_paginate'

# try to figure this out for heroku and rails 3
# class Fixnum; include InWords; end
# class Bignum; include InWords; end
DB_STRING_MAX_LENGTH = 255
DB_TEXT_MAX_LENGTH = 40_000
HTML_TEXT_FIELD_SIZE = 20
AMOUNT_FIELD_SIZE = 10
ADDRESS_FIELD_SIZE = 30
SERVER_SIDE_CART = false
# SQL_LIKE = Rails.configuration.database_configuration[Rails.env]['adapter'].
#   downcase=='postgresql' ? 'ilike' : 'like'
db_env = Rails.configuration.database_configuration[Rails.env]
db_adapter = db_env['adapter'].downcase if db_env.present?
SQL_LIKE = db_adapter == 'postgresql' ? 'ilike' : 'like'

# uncomment to track down bugs on heroku production
# ApplicationRecord.logger.level = 0 # at any time
ActiveMerchant::Billing::CreditCard.require_verification_value = false
PublicSuffix::List.default =
  PublicSuffix::List.parse(File.read(PublicSuffix::List::DEFAULT_LIST_PATH), private_domains: false)

Gemfile
# frozen_string_literal: true

source 'http://rubygems.org'

gem 'activemerchant'
gem 'acts_as_publishable'
gem 'authlogic'
gem 'awesome_print'
gem 'aws-sdk', '~> 2.0'
gem 'bootsnap', require: false
gem 'declarative_authorization', git: 'https://github.com/xymist/declarative_authorization.git', branch: 'allow_rails_5'
gem 'dynamic_form'
gem 'easy_roles'
gem 'haml', '>= 3.1.alpha.50'
gem 'json' # , '~> 1.8.6'
gem 'money', '2.1.0'
gem 'mysql2'
gem 'paperclip', '~> 5.3.0'
gem 'protected_attributes'
gem 'pry-rails'
gem 'rabl', '0.14.1'
gem 'rack-ssl-enforcer'
gem 'rails', '~> <IP_ADDRESS>'
gem 'rb-inotify', require: false
gem 'responders', '~> 2.0'
gem 'savon', '~> 2.0'
gem 'sprockets'
gem 'squeel'
gem 'will_paginate'
gem 'workflow', '~> 1.2'
gem 'xml-simple'
gem 'yui-compressor'
gem 'zip-zip'
# Commented out while converting to pipeline
# gem 'jammit'
gem 'config'
gem 'oauth-plugin', '>= 0.4.0.pre1'
gem 'openssl-extensions', require: 'openssl-extensions/all'
gem 'radix62'
gem 'simpleidn'
gem 'uuidtools'
gem 'whenever', require: false
# gem "therubyracer", '~> 0.12.3', platform: :ruby
gem 'actionpack-action_caching', '~> 1.1', '>= 1.1.1'
gem 'airbrake', '~> 9.5' # https://airbrake.io/docs/ruby/upgrading-your-notifier/
gem 'api-pagination'
gem 'attr_encrypted', '>= 3.0.3'
gem 'bootstrap'
gem 'cancan'
gem 'coffee-rails'
gem 'compass-rails'
gem 'daemons'
gem 'dalli'
gem 'dalli-elasticache'
gem 'delayed-web'
gem 'delayed_job_active_record'
gem 'delayed_job_groups_plugin'
gem 'jbuilder'
gem 'jquery-rails'
gem 'jquery-ui-rails'
gem 'json-schema'
gem 'jsonapi-serializers'
gem 'libv8'
gem 'mini_racer', platforms: :ruby
gem 'nokogiri', '>= 1.10.4'
gem 'popper_js', '~> 1.11.1'
gem 'public_suffix', '>= 4.0.0'
gem 'rack-cors', '>= 0.4.1', require: 'rack/cors'
gem 'rails-api'
gem 'rails-observers'
gem 'request_exception_handler'
gem 'rubyzip', '>= 1.3.0'
gem 'rvm-capistrano'
gem 'sass-rails'
gem 'sdoc', group: :doc
gem 'select2-rails'
gem 'stripe'
gem 'turbolinks'
gem 'unscoped_associations'
# gem 'wkhtmltopdf-binary' see config/initializers/wicked_pdf.rb for installation instructions
gem 'duo_web', '~> 1.0'
gem 'u2f'
gem 'wicked_pdf'
# gem 'simple_captcha2', require: 'simple_captcha'
gem 'acts_as_tree'
gem 'font-awesome-rails'
gem 'recaptcha', require: 'recaptcha/rails'
gem 'where-or'
gem 'whois', '~> 4.0'
gem 'whois-parser'
# gem "skylight"
gem 'authy'
gem 'mailboxer'
gem 'memoist'
# gem 'countries'
gem 'bootstrap-datepicker-rails'
gem 'timezone', '~> 1.0'
# required by sws-a1
gem 'activerecord-import'
gem 'date'
gem 'etc'
gem 'fileutils', '~> 1.1.0'
gem 'forwardable'
gem 'scout_apm'
gem 'stringio'
gem 'strscan'
gem 'zlib'

group :development do
  gem 'annotate'
  gem 'better_errors'
  gem 'binding_of_caller'
  gem 'bullet'
  gem 'dotenv-rails'
  gem 'letter_opener_web', '~> 1.0'
  gem 'memory_profiler'
  gem 'meta_request'
  gem 'spring'
  gem 'spring-commands-testunit'
  gem 'web-console', '~> 2.0'

  # Linting
  gem 'rubocop', require: false
  gem 'rubocop-performance'
  gem 'rubocop-rails'
  gem 'solargraph', require: false
end

group :development, :test do
  gem 'builder'
  gem 'byebug'
  gem 'factory_bot_rails'
  gem 'pry-byebug'
  gem 'pry-remote'
  gem 'ruby-odbc'
  gem 'ruby_parser'
  gem 'rspec-rails'
end

group :test do
  gem 'database_cleaner'
  gem 'faker'
  gem 'mocha'
  gem 'simplecov', require: false
  gem 'vcr'
  gem 'webmock'
end

gem 'foreman'
gem 'httparty'
gem 'swagger-blocks'
gem 'swagger-docs'
gem 'uglifier', '4.1.8'

gem 'rswag-ui'

gem 'bcrypt_pbkdf', '~> 1'
gem 'ed25519', '~> 1.2'

environment.rb
# frozen_string_literal: true

# Load the rails application
require File.expand_path('application', __dir__)

# Initialize the rails application
SslCom::Application.initialize!

# for IDN (unicode names)
Encoding.default_external = Encoding::UTF_8
Encoding.default_internal = Encoding::UTF_8

ApplicationRecord.include_root_in_json = true

boot.rb
ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../../Gemfile', __FILE__)
require 'bundler/setup' # Set up gems listed in the Gemfile.
require 'bootsnap/setup'

It's strange that it reports ./spec/rails_helper.rb:5:in require', but there's no require` on line 5 there. Can you please confirm this is correct?

:wave: There is something strange going on with your load ordering (Its highly unlikely this is an rspec-rails issue), from your stacktrace:
NameError:
  uninitialized constant ActiveRecord::Relation
# ./config/application.rb:10:in `<top (required)>'
# ./config/environment.rb:2:in `require'
# ./config/environment.rb:2:in `<top (required)>'
# ./spec/rails_helper.rb:5:in `require'
# ./spec/rails_helper.rb:5:in `<top (required)>'
# ./spec/swagger_helper.rb:2:in `require'
# ./spec/swagger_helper.rb:2:in `<top (required)>'
# ./spec/requests/teams_spec.rb:1:in `require'
# ./spec/requests/teams_spec.rb:1:in `<top (required)>'
# ------------------
# --- Caused by: ---
# NameError:
#   uninitialized constant ActiveRecord::Relation
#   ./config/application.rb:10:in `<top (required)>'

Can you confirm that whats in swagger_helper? And that your rails_helper is exactly as pasted above? As the line numbers don't match up.
You might also want to make sure that spring / bootsnap has been stopped / restarted after installing rspec.

@JonRowe @pirj  I've updated the error and files above. Those were from a different branch where I tried to implement RSpec. Sorry for the confusion.

I might be mistaken, but this might be the culprit:
# config/application.rb
require 'rails/all'
Bundler.setup
Bundler.require(*Rails.groups)

Rails 4.2's default template suggests:
require 'rails/all'
Bundler.require(*Rails.groups)

Can you please try it this way (without Bundler.setup)?

@pirj That didn't help

Whats the contents of config/environment.rb and config/boot.rb?
I'm closing this for now because its not an rspec-rails issue, but an issue with your configuration. I'm happy to keep helping here but bare in mind its the holidays so there may be delays in replies.

@JonRowe I've added those files above.

Can you try to narrow it down to a specific group by changing:
- Bundler.require(*Rails.groups)
+ Rails.groups.each do |group|
+   puts group
+   Bundler.require(group)
+ end

@pirj The only group that gets printed is default.

@antarr can you run rspec with --backtrace to see if there is some missing entries?
What likely happening is something isn't requiring active_record but needs it. Need to find what it is so you can require it.
Does this app start up in dev?

@JonRowe
This is the error log when trying to start in development

=> Booting WEBrick
=> Rails <IP_ADDRESS> application starting in development on https://<IP_ADDRESS>:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
/vagrant/config/initializers/bypass_ssl_verification_for_open_uri.rb:2: warning: already initialized constant OpenSSL::SSL::VERIFY_PEER
/var/lib/gems/2.6.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/http/mime_type.rb:163: warning: already initialized constant Mime::PDF
/var/lib/gems/2.6.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/http/mime_type.rb:163: warning: previous definition of PDF was here
DEPRECATION WARNING: Core extensions are deprecated and will be removed in Squeel 2.0. (called from /vagrant/config/initializers/squeel.rb:11:in `block in <main>')
Exiting
Traceback (most recent call last):
bin/rails: Bootsnap::LoadPathCache::FallbackScan
        106: from bin/rails:39:in `<main>'
        105: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `require'
        104: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:240:in `load_dependency'
        103: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `block in require'
        102: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
        101: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require_with_bootsnap_lfi'
        100: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
         99: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `block in require_with_bootsnap_lfi'
         98: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require'
         97: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands.rb:17:in `<main>'
         96: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
         95: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/commands_tasks.rb:75:in `server'
         94: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/commands_tasks.rb:75:in `tap'
         93: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/commands_tasks.rb:80:in `block in server'
         92: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/server.rb:78:in `start'
         91: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/server.rb:139:in `log_to_stdout'
         90: from /var/lib/gems/2.6.0/gems/rack-1.6.11/lib/rack/server.rb:337:in `wrapped_app'
         89: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/server.rb:61:in `app'
         88: from /var/lib/gems/2.6.0/gems/rack-1.6.11/lib/rack/server.rb:209:in `app'
         87: from /var/lib/gems/2.6.0/gems/rack-1.6.11/lib/rack/server.rb:300:in `build_app_and_options_from_config'
         86: from /var/lib/gems/2.6.0/gems/rack-1.6.11/lib/rack/builder.rb:40:in `parse_file'
         85: from /var/lib/gems/2.6.0/gems/rack-1.6.11/lib/rack/builder.rb:49:in `new_from_string'
         84: from /var/lib/gems/2.6.0/gems/rack-1.6.11/lib/rack/builder.rb:49:in `eval'
         83: from /vagrant/config.ru:in `<main>'
         82: from /vagrant/config.ru:in `new'
         81: from /var/lib/gems/2.6.0/gems/rack-1.6.11/lib/rack/builder.rb:55:in `initialize'
         80: from /var/lib/gems/2.6.0/gems/rack-1.6.11/lib/rack/builder.rb:55:in `instance_eval'
         79: from /vagrant/config.ru:3:in `block in <main>'
         78: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `require'
         77: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:240:in `load_dependency'
         76: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `block in require'
         75: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
         74: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require_with_bootsnap_lfi'
         73: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
         72: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `block in require_with_bootsnap_lfi'
         71: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require'
         70: from /vagrant/config/environment.rb:7:in `<main>'
         69: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/railtie.rb:194:in `method_missing'
         68: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/railtie.rb:194:in `public_send'
         67: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/application.rb:352:in `initialize!'
         66: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:54:in `run_initializers'
         65: from /usr/lib/ruby/2.6.0/tsort.rb:205:in `tsort_each'
         64: from /usr/lib/ruby/2.6.0/tsort.rb:226:in `tsort_each'
         63: from /usr/lib/ruby/2.6.0/tsort.rb:347:in `each_strongly_connected_component'
         62: from /usr/lib/ruby/2.6.0/tsort.rb:347:in `call'
         61: from /usr/lib/ruby/2.6.0/tsort.rb:347:in `each'
         60: from /usr/lib/ruby/2.6.0/tsort.rb:349:in `block in each_strongly_connected_component'
         59: from /usr/lib/ruby/2.6.0/tsort.rb:431:in `each_strongly_connected_component_from'
         58: from /usr/lib/ruby/2.6.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
         57: from /usr/lib/ruby/2.6.0/tsort.rb:228:in `block in tsort_each'
         56: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:55:in `block in run_initializers'
         55: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:30:in `run'
         54: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:30:in `instance_exec'
         53: from /var/lib/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/application/finisher.rb:50:in `block in <module:Finisher>'
         52: from /var/lib/gems/2.6.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/reloader.rb:55:in `prepare!'
         51: from /var/lib/gems/2.6.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/reloader.rb:83:in `prepare!'
         50: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:81:in `run_callbacks'
         49: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:778:in `_run_prepare_callbacks'
         48: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
         47: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:504:in `call'
         46: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:504:in `each'
         45: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:504:in `block in call'
         44: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:192:in `block in simple'
         43: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:446:in `block in make_lambda'
         42: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:446:in `instance_exec'
         41: from /vagrant/config/environments/development.rb:37:in `block (2 levels) in <main>'
         40: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:184:in `const_missing'
         39: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:59:in `load_missing_constant'
         38: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:16:in `allow_bootsnap_retry'
         37: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:60:in `block in load_missing_constant'
         36: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:494:in `load_missing_constant'
         35: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:47:in `require_or_load'
         34: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:16:in `allow_bootsnap_retry'
         33: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:48:in `block in require_or_load'
         32: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:354:in `require_or_load'
         31: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:456:in `load_file'
         30: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:647:in `new_constants_in'
         29: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:457:in `block in load_file'
         28: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:54:in `load'
         27: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:54:in `load'
         26: from /vagrant/app/models/billing_profile.rb:1:in `<main>'
         25: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:184:in `const_missing'
         24: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:59:in `load_missing_constant'
         23: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:16:in `allow_bootsnap_retry'
         22: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:60:in `block in load_missing_constant'
         21: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:494:in `load_missing_constant'
         20: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:47:in `require_or_load'
         19: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:16:in `allow_bootsnap_retry'
         18: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:48:in `block in require_or_load'
         17: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:354:in `require_or_load'
         16: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:456:in `load_file'
         15: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:647:in `new_constants_in'
         14: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:457:in `block in load_file'
         13: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:54:in `load'
         12: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:54:in `load'
         11: from /vagrant/app/models/application_record.rb:14:in `<main>'
         10: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `require'
          9: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:238:in `load_dependency'
          8: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:647:in `new_constants_in'
          7: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:238:in `block in load_dependency'
          6: from /var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:274:in `block in require'
          5: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:26:in `require'
          4: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:40:in `rescue in require'
          3: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require_with_bootsnap_lfi'
          2: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/loaded_features_index.rb:89:in `register'
          1: from /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `block in require_with_bootsnap_lfi'
/var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require': cannot load such file -- acts_as_publishable/lib/acts_as_publishable (LoadError)

After changing ApplicationRecord to ActiveRecord::Base in lib\ files I get this error when running rspec with --backtrace
Your env: test
/var/lib/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/object/duplicable.rb:111: warning: BigDecimal.new is deprecated; use BigDecimal() method instead.
Loading group: default

An error occurred while loading rails_helper.
Failure/Error: require File.expand_path('../config/environment', __dir__)

NameError:
  uninitialized constant ActiveRecord::Base
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:79:in `block in load_missing_constant'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:8:in `without_bootsnap_cache'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:79:in `rescue in load_missing_constant'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:58:in `load_missing_constant'
# /var/lib/gems/2.6.0/gems/acts_as_publishable-0.2/lib/acts_as_publishable.rb:3:in `<main>'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `block in require_with_bootsnap_lfi'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require_with_bootsnap_lfi'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
# /var/lib/gems/2.6.0/gems/bundler-1.17.3/lib/bundler.rb:114:in `require'
# ./config/application.rb:16:in `block in <top (required)>'
# ./config/application.rb:13:in `each'
# ./config/application.rb:13:in `<top (required)>'
# ./config/environment.rb:4:in `require'
# ./config/environment.rb:4:in `<top (required)>'
# ./spec/rails_helper.rb:14:in `require'
# ./spec/rails_helper.rb:14:in `<top (required)>'
# ------------------
# --- Caused by: ---
# NameError:
#   uninitialized constant ActiveRecord::Base
#   /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:60:in `block in load_missing_constant'
No examples found.
No examples found.

Finished in 0.00005 seconds (files took 1.28 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

Finished in 0.00005 seconds (files took 1.28 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

The problem seems to be with ActsAsPublishable. If I remove it from ApplicationRecord.rb I can start the server in development. But I still can't run the specs.
bundle exec rspec --backtrace /spec
An error occurred while loading rails_helper.
Failure/Error: require File.expand_path('../config/environment', __dir__)

NameError:
  uninitialized constant ActiveRecord::Base
# /var/lib/gems/2.6.0/gems/acts_as_publishable-0.2/lib/acts_as_publishable.rb:3:in `<top (required)>'
# /var/lib/gems/2.6.0/gems/bundler-1.17.3/lib/bundler.rb:114:in `require'
# ./config/application.rb:16:in `block in <top (required)>'
# ./config/application.rb:13:in `each'
# ./config/application.rb:13:in `<top (required)>'
# ./config/environment.rb:4:in `require'
# ./config/environment.rb:4:in `<top (required)>'
# ./spec/rails_helper.rb:14:in `require'
# ./spec/rails_helper.rb:14:in `<top (required)>'
No examples found.
No examples found.

Finished in 0.00004 seconds (files took 1.66 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

Finished in 0.00004 seconds (files took 1.66 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

app/models/application_record.rb
# frozen_string_literal: true

require 'acts_as_billable/lib/active_merchant_default_gateway'
require 'acts_as_billable/lib/acts_as_sellable'
require 'acts_as_billable/lib/acts_as_seller'
require 'acts_as_billable/lib/acts_as_billable'

require 'acts_as_money/aggregations'
require 'acts_as_money/acts_as_money'

require 'acts_as_notable/lib/notable_methods'
require 'acts_as_notable/lib/note_methods'

# require 'acts_as_publishable/lib/acts_as_publishable'

class ApplicationRecord < ActiveRecord::Base
  include Swagger::Blocks
  include CollectiveIdea::Acts::Billable
  include CollectiveIdea::Acts::Sellable
  include CollectiveIdea::Acts::Money
  # include Acts::As::Publishable

  self.abstract_class = true
  self.include_root_in_json = true
end

It seems that the problem goes beyond RSpec.
I can suggest to require activerecord from app/models/application_record.rb and get rid of bootsnap to pinpoint the issue.

@pirj That didn't change anything at all

It seems that acts_as_publishable is quite old and might not be compatible with your version of Rails. Its gemspec for that version has no dependency on rails and still references ActiveRecord::Base, what is most probably the reason for failures.
If you can dump it, or bump its version (there's a branch that is compatible with Rails 3, but not Rails 4), that might help, but there's no guarantee the rest will work.
Otherwise, I'm afraid if the application fails to boot up, we can't provide much help here.

Try adding require: false to the options for your gem listing for acts_as_publishable, then requiring it immediately after your bundler setup...

@JonRowe That seems to help. I had to do it for a few gems. So now I'm getting an error when trying to load authlogic.
error
Failure/Error: require File.expand_path('../config/environment', dir)
NoMethodError:
  undefined method `gem_version' for ActiveRecord:Module
# /var/lib/gems/2.6.0/gems/authlogic-4.4.3/lib/authlogic/acts_as_authentic/queries/find_with_case.rb:12:in `<class:FindWithCase>'
# /var/lib/gems/2.6.0/gems/authlogic-4.4.3/lib/authlogic/acts_as_authentic/queries/find_with_case.rb:8:in `<module:Queries>'
# /var/lib/gems/2.6.0/gems/authlogic-4.4.3/lib/authlogic/acts_as_authentic/queries/find_with_case.rb:5:in `<module:ActsAsAuthentic>'
# /var/lib/gems/2.6.0/gems/authlogic-4.4.3/lib/authlogic/acts_as_authentic/queries/find_with_case.rb:4:in `<module:Authlogic>'
# /var/lib/gems/2.6.0/gems/authlogic-4.4.3/lib/authlogic/acts_as_authentic/queries/find_with_case.rb:3:in `<main>'

application.rb
Rails.groups.each do |group|
  puts "Loading group: #{group}"
  Bundler.require(group)
end

require 'acts_as_publishable'
require 'authlogic'
# require 'authlogic/version'
require 'squeel'
require 'unscoped_associations'
require 'acts_as_tree'
require 'where-or'
require 'delayed_job_active_record'
require 'delayed_job_groups_plugin'

tried adding this to application.rb
# GEMS::VESION.gem_version = '5.2'
module ActiveRecord
  module Module
    def gem_version
      '5.2'
    end
  end
end

I also tried requiring rubygems in the application.rb

I also get the error below when trying to require declarative_authorization
error
NameError:
  uninitialized constant ActiveRecord::Relation
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:79:in `block in load_missing_constant'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:8:in `without_bootsnap_cache'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:79:in `rescue in load_missing_constant'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:58:in `load_missing_constant'
# /home/vagrant/.bundle/ruby/2.6.0/declarative_authorization-3cd79342d073/lib/declarative_authorization/obligation_scope.rb:45:in `<module:Authorization>'
# /home/vagrant/.bundle/ruby/2.6.0/declarative_authorization-3cd79342d073/lib/declarative_authorization/obligation_scope.rb:1:in `<main>'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `block in require_with_bootsnap_lfi'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require_with_bootsnap_lfi'
# /var/lib/gems/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
# /home/vagrant/.bundle/ruby/2.6.0/declarative_authorization-3cd79342d073/lib/declarative_authorization/in_model.rb:3:in `<main>'

I added this code before . It doesn't error but doesn't help either
ActiveSupport.on_load(:active_record) do
  # preload common constants to work around https://github.com/rails/rails/issues/26273
  # ActiveRecord::StatementCache
  # ActiveRecord::Associations::JoinDependency::JoinBase
  # ActiveRecord::ConnectionAdapters::TransactionManager
  ActiveRecord::Base
  ActiveRecord::Relation
end

What is dependent on polyamorous? Can you please share your Gemfile.lock as well?
 Have you tried to apply the trick with require: false squeel and declarative_authorization in Gemfile?

I've applied it to all these gems
require 'acts_as_publishable'
require 'authlogic'
require 'polyamorous'
require 'squeel'
require 'unscoped_associations'
require 'acts_as_tree'
require 'where-or'
require 'delayed_job_active_record'
require 'delayed_job_groups_plugin'

Please add it to declarative_authorization as well.


Add github-app-user-auth

I've created an associated GitHub app on my account, this can probably only be managed by me: https://github.com/settings/apps/hub-jupytearth-org-github-integ

Awesome, thanks so much @consideRatio! Does this close #96, or do you want to do a bit more testing first?

Thanks for the encouragement @fperez!
I figure it doesn't yet close #96, I need to deploy changes so that the user pod's start with a certain environment variable and a /etc/gitconfig file mounted. I'll also want to test it as well after having done that.
I'm iterating with Yuvi about smaller details in https://github.com/yuvipanda/github-app-user-auth/issues. It is really fun to work on something when there are active participants across the entire chain, from developers to end users!
I'll ping you in #96 when I've verified it to function!


add if-is statement

var a = [23, 43]
var b = $a as Any
if($b is Array<String>) {
  $b[0]
}

close in commit edfe73d279fb4289b500d4d33f28635e23b68d9e


Hwameictl snapshot

What this PR does / why we need it:
add ctl vs lvs vac
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?
NONE

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (1f638d5) 27.74% compared to head (d7f1bed) 28.74%.
Report is 16 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1331      +/-   ##
==========================================
+ Coverage   27.74%   28.74%   +1.00%
==========================================
  Files          34       34
  Lines        3767     3079     -688
==========================================
- Hits         1045      885     -160
+ Misses       2605     2077     -528
  Partials      117      117

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Refactor common code in gh-dxp

📝 Description

Add terminal-helper commands to utils
Added file manipulation function to utils
Added os.Chdir to the executor, so that it can be mocked
Made MockExecutor a struct in its own package (testutils). This ensures that we don't need to copy-paste the same MockExecutor to every package. Could use build tags to ensure this does not get built with the regular code, but that breaks VsCode.
Added specific tests for the utils code. More testing is still needed, though.
Refactor initiated to support future changes to PR-create/update (where we need the files.go functionality)

🔗 Issue ID(s): TDX-625
📋 Checklist

✅ Lint checks passed on local machine.
✅ Unit tests passed on local machine.
✅ This PR adds news tests.

LGTM. I agree that we should ideally add more utils tests, but this PR is large enough as-is imo

Yep. I actually started out by adding some more tests, but that then led to a bunch of refactoring, so I stopped. 🤣


observed loss of tracked, unstaged work after interrupting hung process

Description
lint-staged may lose tracked, unstaged work when interrupting tasks that appear to have hung and backup stash does not appear in git stash list.

Steps to reproduce
At commit time we observed lint-staged appearing to hang and spam the console. After about 2 minutes, the user interrupted the process.

working tree with multiple files with staged changes and multiple files with unstaged tracked changes
git commit
send keyboard interrupt during lint-staged run

After interrupting, unstaged tracked changes were all missing.
Backup stash was not present in git stash list.
We would expect that, in the worst case, an interrupted run would still leave us the backup stash to restore our changes from.
Fortunately, the user was able to recover much of their work that was still open in their editor.
We are hoping that this is kind of a "lightning strike" and we just got unlucky. But wanted to raise this here to hopefully understand how we could have gotten into that state, how to avoid it, and ultimately help make lint-staged even more robust.
lint-staged config:
module.exports = {
  '**/a-prettier-linted-directory/**/*.{js,jsx,ts,tsx}': [
    'prettier --write --single-quote'
  ],
  '*.{js,jsx,ts,tsx}': files => {
    const filesToLint = files.filter(customFilteringFunction).join(' ');

    return [
      `eslint --max-warnings=0 --fix ${filesToLint}`,
      `git add ${filesToLint}`
    ];
  }
};

Debug Logs
We were not able to capture debug logs but provided below is the console dump from the session where we observed this behavior.

expand to view
❯ git commit
husky > pre-commit (node v12.14.1)
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Preparing...
  ✔ Running tasks...
  ⠼ Applying modifications...
  ✔ Preparing...
  ✔ Running tasks...
  ✖ Applying modifications...
    → Unstaged changes could not be restored due to a merge conflict!
  ✖ Reverting to original state...
    → remove the file manually to continue.
  ✔ Cleaning up...

  ✖ lint-staged failed due to a git error.
  Any lost modifications can be restored from a git stash:

    > git stash list
    stash@{0}: On master: automatic lint-staged backup
    > git stash pop stash@{0}

Unstaged changes could not be restored due to a merge conflict!
fatal: Unable to create '/Users/username/path/to/repo/.git/index.lock': File exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.

Environment

OS: mac os version 10.15.2 (19C57)
Node.js: node v12.14.1
lint-staged: v10.0.7
git: v2.23.0

Please let me know if I can provide any more context!

Hmm, according to the log, since the revert step failed the cleanup job should probably be skipped as well. That multiple preparing doesn’t look normal either.
I can check if there’s some error being missed, but without debug logs I can’t promise anything.
Was the open editor running some git integration that might have caused this (locking the repo so lint-staged’s git commands fail)?
You might be able to restore the dropped backup stash using gitk: https://stackoverflow.com/questions/89332/how-to-recover-a-dropped-stash-in-git#91795

Thanks for pointing me to the gitk/git fsck` resource, glad to have that in my back pocket!
We haven't seen anything like this reoccur since I opened the issue, and still aren't able to reproduce. Seems like we just got unlucky.

:tada: This issue has been resolved in version 10.0.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

I added a failsafe so that whenever the restore task fails, the stash cleanup is skipped. In<EMAIL_ADDRESS>the behavioural change is that in this case the stash should be preserved instead of dropped.


Support for Checkbox, Radio, Toggle, Spinner

Hi, thanks for the PR.
I actually merged another implementation of Checkbox and Switch in there earlier. It would be great if you could rework those components which are still missing onto the current feature/mixins branch. Otherwise I will most probably do this myself at some point :)
Fair warning, most of the repository changed in that branch. Some Information about that can be found in #28.


Fix #296 Added LightSwitch

Fix #296
Showcase is still to do.. I'll take care of that after this has been reviewed

I also just fixed some oddities with our themeswitcher and deleted a bunch of old JS methods for theme switching in core.js that weren't even being used!

I also just fixed some oddities with our themeswitcher and deleted a bunch of old JS methods for theme switching in core.js that weren't even being used!

I am thinking one more good change might be a disabled flag on the component and two new widget methods for enable and disable. This way people can control it if they need to.

I added an automatic attribute instead and some API functions to control the switch. Disabling does not make sense to me as it's only executed on page load. If you don't want it to run you can now use automatic="false" or rendered="false".

I am thinking one more good change might be a disabled flag on the component and two new widget methods for enable and disable. This way people can control it if they need to.

I added an automatic attribute instead and some API functions to control the switch. Disabling does not make sense to me as it's only executed on page load. If you don't want it to run you can now use automatic="false" or rendered="false".


lodash update require (security)

npm audit raise an issue about latest version of package.
lodash should be updated.
Can you please provide a MR with the update?
Low           │ Prototype Pollution  Package       │ lodash                      Patched in    │ >=4.17.19                                                     Dependency of │ swagger-spec-express         Path          │ swagger-spec-express > lodash   More info     │ https://npmjs.com/advisories/1523

Any update for this point?


volume allocation issue

by default, there will be concurrently 7 writable volumes allocated.
but the issue is that I have 10 volume nodes, there are 2 writable volumes allocated on one node although some other nodes have no writable volume.
that means it doesn't guarantee that one node serves only one volume when there are enough nodes, so I fear that even 7 writable volumes are allocated on one node in some extreme case in despite of other free nodes.

see https://github.com/chrislusf/seaweedfs/wiki/Master-Server-API#pre-allocate-volumes


Heroku CLI with Heroku Enterprise?

At work, we navigate to our Heroku apps hosted on Heroku Enterprise by first going through Okta. Is there any support for this through the CLI? I can't seem to authenticate with my Heroku Enterprise email address.

@gjtorikian could you please try logging in with heroku login --sso?

Yup, that did it! Thank you!


the dimension of inference result was 3

I ran your sample code(ResNet50MaskRCNN.ipynb)
I didn't fix any code
I thought it worked fine
but the result didn't have mask information.

What is the result then?

How to get mask information @KARAMKIM88 @hgaiser ?
I'm also getting only 3 items in result i.e bounding_box,score and labels.
How to fix this ?

I didnt find the solution
So i used pytorch and detectron
Sorry
2020년 3월 3일 (화) 오후 8:07, Ujjawal Kumar Singh<EMAIL_ADDRESS>작성:

How to get mask information @KARAMKIM88 https://github.com/KARAMKIM88
@hgaiser https://github.com/hgaiser ?
I'm also getting only 3 items in result i.e bounding_box,score and labels.
How to fix this ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fizyr/keras-maskrcnn/issues/96?email_source=notifications&email_token=AB7JHVJZBCPPZI3UXBPT46LRFTQHLA5CNFSM4J7WKEJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENTCJMI#issuecomment-593896625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7JHVLWHBJHQVQAHONNBYLRFTQHLANCNFSM4J7WKEJA
.

Okay Thanks.
On Tue 3 Mar, 2020, 17:07 KARAMKIM88<EMAIL_ADDRESS>wrote:

I didnt find the solution
So i used pytorch and detectron
Sorry
2020년 3월 3일 (화) 오후 8:07, Ujjawal Kumar Singh<EMAIL_ADDRESS>작성:

How to get mask information @KARAMKIM88 https://github.com/KARAMKIM88
@hgaiser https://github.com/hgaiser ?
I'm also getting only 3 items in result i.e bounding_box,score and
labels.
How to fix this ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/fizyr/keras-maskrcnn/issues/96?email_source=notifications&email_token=AB7JHVJZBCPPZI3UXBPT46LRFTQHLA5CNFSM4J7WKEJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENTCJMI#issuecomment-593896625
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AB7JHVLWHBJHQVQAHONNBYLRFTQHLANCNFSM4J7WKEJA
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fizyr/keras-maskrcnn/issues/96?email_source=notifications&email_token=AH2BJCFKMKFTF2VD2BYRSOLRFTTXLA5CNFSM4J7WKEJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENTE6HI#issuecomment-593907485,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH2BJCFNY7D6XBA7ZSYYSBLRFTTXLANCNFSM4J7WKEJA
.


feat(rich-list-core): merge dfi utxo & dfi token rich list

What this PR does / why we need it:
Merge calculation for the rich list of DFI utxo and DFI token together. This will make the rich list is more friendly to users, since DFI utxo and DFI token refer to essentially the same asset.
Which issue(s) does this PR fixes?:

Closes #1260
Additional comments?:

@cwkang1998 need help to resolve conf


Bloodhound

As we discussed @papandreou, I need the first commit to land in trackingdog, to be able to reuse the AssetGraph instance.
The bloodhound method itself is not quite there yet - formatting is changed and there's probably a bunch of other polishing necessary.

Coverage decreased (-1.0%) to 78.788% when pulling 90c6339c3a41f6a4291a0c787f87eb9556f60fb5 on gustavnikolaj:feature/bloodhound into 1b4cd4e3a3e39280b6e84562a83a9da0d16c2e14 on papandreou:master.

Hmm, I should probably have brought this up before, but how about turning trackingDog into a class that owns the AssetGraph instance and can be reused by calling a track method multiple times?

We can of course find a way to include the bloodhound name :)

We can make it into a class :-) I actually considered that when I started out, but wanted to keep the change set as small as possible.
Only the first commit is supposed to be landed in trackingdog - I should have explained that. The second commit is to show how I'd use it to implement the bloodhound function and the third is an example of how it would be used.
I weren't sure if you wanted to expand trackingdog itself, and I'd be okay with just having the additional layer in a tool in my end. :)
I think the most important bit right now is getting the assetgraph-reuse in, one way or the other, as that allows us to start experimenting with different approaches.

Making it a class would also be sufficient to support tracking an entire stack trace without wasting a lont of time, which would be a great feature. I think we should do that.

Would be really great to have the stack trace tracking ability in the cli as well. Maybe the trackingdog binary could just display a notice and wait for a stack trace on stdin if no source location is given at the command line?

Closing, replaced by PR referenced above.


Add a setting to deploy downstream/upstream embedded bits

Currently EIB deploys metallb and e-c-o from upstream charts (suse-edge/charts) if the container image is being built by the user but if using the downstream EIB image, metallb and e-c-o (something else?) are deployed using downstream charts (IBS).
This is ok but if someone wants to run a test with downstream bits based on a PR here or while the changes haven't been backported, it is currently not possible.

We'll keep it on the backlog, but realistically this is such a niche use case that I don't see when we'd actually address this.

To elaborate this a little bit. I think maybe just an env var that can be overwritten at execution time will be nice, so something like:
podman run -it ... -e METALLB_CHART="my-fork-metallb" -e METALLB_CHART_REPO="oci://myregistry.example.com/foobar" -e ...


Since "...we concluded that it is better to hold off with major changes this time...", maybe we can use this release to put the focus on any optimisations and changes that would help our worldwide community to reduce their carbon (CO2) footprint:

Using less memory, means less VirtualMachines are needed.
Using less CPU cycles, means less power and cooling are needed.
Smaller binaries use less disk space, which means fewer storage is needed.

A so called "Go Green" release.
These changes are likely part of an ongoing effort to improve Go one version to the next.
The proposal for 1.15 is to prioritise some of these issues over others, and to highlight the improvements made in this area. Maybe put some nice marketing around it, to increase the awareness of Go in the wider development community.

This proposal has no concrete actionable suggestions. We work every release to make Go use less memory, less CPU, and less disk space. In some releases other concerns like functionality or correctness are judged more important than those. But for the most part Go does get more efficient with each release.
The most actionable suggestion would be to "put some nice marketing" around performance improvements as good for the environment. That's not the kind of gimmick we typically do.
It is not even clear to me that using less memory, less CPU, and less disk space necessarily translates into less environmental impact. Perhaps if those go down people just write programs that hold more data, do more computation, and have more code in the binary. Certainly that's the trend over time. It's probably more effective to make sure that the CPU etc that you do pay for is carbon-neutral. If you are interested in that topic, see https://cloud.google.com/sustainability for what Google does, both for itself and Google Cloud usage.
I'm going to close this issue as not actionable, but thanks for raising it. I agree that it's important to consider what role we can play, and it's nice to think that our never-ending efficiency work serves a purpose of making computing greener. Here's hoping (and remembering that carbon-neutral energy is also important).


 If it is too much to review, I will split it into multiple smaller ones, just let me know:)
Additions:

FriendsEval class:

performs a simple Network Analysis on evaluations involving one user
shows the top 10 most involved with logins and gives user the option to see the full list

Animation class:

moved full animation logic into the Animation class
start an animation by instantiating an object with your desired loading message: loading_animation = Animation("<your message>")
stop the animation by calling stop_animation() on your Animation object

Utils class: make_request_with_backoff():

created the make_request_with_backoff() function to adress the "429: Too Many Requests" response that the 42 API returns often
you can call it exactly like request.get(), the key difference is that on status code 429, it will backoff and retry
max_retries is set to 5 by default, I have found it to be enough but you can add it to your method call if you want to change it

Update: Merge conflicts with main are fixed, tested functionality & reformatted after fixes

921fc29

a35729e


Crash with the Fletching Table, because of Apotheosis.

On the last version, when we open the fletching table, the client suddendly crashes.
Here is the changelog : https://mclogs.minestrator.com/5aBqRcz

Also can confirm, newest version 4.7.1 causes the below crash on client-side every time anyone attempts to use a fletching table.
Error: java.lang.BootstrapMethodError: java.lang.IllegalAccessError: tried to access method net.minecraft.block.CraftingTableBlock.func_220270_a(Lnet/minecraft/world/World;Lnet/minecraft/util/math/BlockPos;ILnet/minecraft/entity/player/PlayerInventory;Lnet/minecraft/entity/player/PlayerEntity;)Lnet/minecraft/inventory/container/Container; from class shadows.apotheosis.village.fletching.ApothFletchingBlock
Reverting to the previous 4.6.1 version -- where this still functions until a fix is found.


Support a 'safe' mode where Kudu doesn't write to d:\home

Today, when d:\home is full, you can't even use Kudu to investigate, as it itself writes there, for things like log files. It fails with:
[IOException: There is not enough space on the disk.
]
   System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +11185413
   System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) +1305
   System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) +65
   System.IO.Abstractions.FileWrapper.Open(String path, FileMode mode, FileAccess access, FileShare share) +36
   Kudu.Core.Tracing.LogFileHelper.WriteLine(String value, IDictionary`2 attributes, Int32 depth, Boolean end) +901
   Kudu.Core.Tracing.TextTracer.Trace(String message, IDictionary`2 attributes) +22
   Kudu.Core.Tracing.CascadeTracer.Trace(String message, IDictionary`2 attributes) +36
   Kudu.Services.Web.Tracing.TraceModule.TraceStartup(HttpContext httpContext) +383
   Kudu.Services.Web.Tracing.TraceModule.OnBeginRequest(Object sender, EventArgs e) +494
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +136
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +69

I wonder whether with careful coding, we could make Kudu work in this scenario, by simply not having it write to the xdrive at all. E.g. in this case, it’s failing to write the Kudu trace file, which is totally non-essential.
We could have some kind of optional SCM_SAFE_MODE=1 appsetting that would disable any such logic. In theory, to run Kudu console, we shouldn't need to be writing anything under d:\home afaik.

Try set appSettings SCM_TRACE_LEVEL=0.  This should disable all traces.  BTW, we mentioned Verbose but not OFF level.

Yes, that seems to work!
In addition, I found that even without the flag, you only hit the error on the first request, and after refresh Kudu runs fine.
Good enough for me!


Unreliable merge commit check in examples

https://github.com/danger/danger/blob/626c450619d19377424feb1071b22fda8a8a8141/lib/danger/danger_core/plugins/dangerfile_git_plugin.rb#L25
Checking for merge commits this way causes a false positive on regular commits with message beginning with Merge branch 'master' and false negative on merge commits with commit subject altered so it wouldn't match the regex.
Consider using something like c.parents.count > 1 instead

Sure thing, open to it

I just opened https://github.com/danger/danger/pull/1400


Simplified Bytes (internal)

This PR decouples Bytes from everything except std.
This ports @jhorstmann's PR in arrow-rs. Although not as relevant here since we use Vec anyways, it enable us to potentially move Bytes to its own crate.
I am not fan of using Arc instead of Box - the struct itself does not need an Arc, will try to address this in a future PR.
Relevant thread in rust-users: https://users.rust-lang.org/t/implementing-a-potentially-foreign-allocated-potentially-mutable-memory-region/77388

@jhorstmann I had to require Send + Sync to the owner, or Bytes would not be Send + Sync. unsafe impl Send for Bytes in arrow-rs may be unsound.

So we remove 1 layer of indirection to the data? And only decide at Drop what to do with the Vec we created? That saves a lot of branches!

So we remove 1 layer of indirection to the data? And only decide at Drop what to do with the Vec we created? That saves a lot of branches!

I believe so - although it is unclear whether the compiler was not optimizing it already.

P.S. which Arc are you referring to?

The one at Foreign(Arc<dyn RefUnwindSafe + Send + Sync>) - this arc is only here due to some constraint in the FFI that imo can go away.

I believe so - although it is unclear whether the compiler was not optimizing it already

I don't think it can. It could be either branch, so it has to check. I think.

The one at Foreign(Arc<dyn RefUnwindSafe + Send + Sync>) - this arc is only here due to some constraint in the FFI that imo can go away.

Right, and if we remove it, the clone call goes over FFI go that smart atomic pointer?

Right, and if we remove it, the clone call goes over FFI go that smart atomic pointer?

We do not know about smart pointers in FFI - in this case the idea is that we can Arc the struct containing the ref counter of the FFI struct (i.e. instead of Arc<Arc<, we use Box<Arc<, just like we did for Array.


Open5GS with eUPF as UPF

Components and subsystems
open5gs
Proposed functionality
Hey - we are using your Helm charts for deploying open5gs for 5G-SA networks. We've recently realized that the UPF component within open5gs limits the maximum available UP throughput. There are more powerful UPF components such as eUPF that can be used as a drop-in-replacement together with the rest of open5gs. Are there any plans to add support for eUPF in your charts so that can be used together with open5gs and/or free5gc?
External dependencies
No response

Hi @andrepuschmann
Thanks for the suggestion. We haven't thought about it yet, but seeing that it could be interesting to have new UPF components as Helm Chart, we'll talk internally and see how it fits into our roadmap. I will keep you informed.
At the same time, if you have already made progress in this field, feel free to make a PR and we will review it.
BR,
Álvaro


Uses u32 for answers, today's answer required u64.

I wasted a lot of time because of this :(

It's documented in the readme and should error in non-release mode, but maybe we should just use u64 everywhere.

I would accept a PR that changes this to u64 by default.


Support sound device

What this PR does / why we need it:
Support sound device support.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #4137
Special notes for your reviewer:
Plz do not review until I finish the UT.
Release note:

"NONE"

I made some minor comments here and there. The direction here needs some discussion.
For our video devices, we made the decision to simply introduce a boolean to autoattach a default graphics device or not. I believe this was done to support VNC. I'm curious if it would make sense for us to simply add a default for sound as well and attach by default.
If we end up taking the direction of this pr, it handles the case where we emulate a sound device, but I want to make sure we have a plan for audio device host passthrough as well that naturally works with the api exposed by this PR.
Looking at the libvirt documentation, apparently it's possible to map each sound device to a host audio device backend [1]. I'm not completely certain I understand this mapping, but this could be something we need to support in the future.
@vladikr, I know you're working on general host device passthrough into the VMI pod. How would you envision these audio devices working?
My thought is maybe something like this, where we define the audio device in your soon to be merged hostDevices list, then map it to the soundDevice as a backend audio device?
spec: domain: devices: hostDevices: - deviceName: some-host-audio/whatever name: audio-device soundDevices: - model: some-model - hostDevice: audio-device

https://libvirt.org/formatdomain.html#sound-devices

@davidvossel Thx for your review.  I also agree to simply add a default device for sound, since we don't want to config too many complex devices. The current implementation is because of the flexible use case. I think we need others' comments.
And the sound device doesn't map to a host device. Hmmm, I think nobody wants to listen to music with a compute node~ It is the spice which transfers data to the client (like remote viewer).

And the sound device doesn't map to a host device. Hmmm, I think nobody wants to listen to music with a compute node~ It is the spice which transfers data to the client (like remote viewer).

from https://libvirt.org/formatdomain.html#audio-devices
"A virtual audio device corresponds to a host audio backend that is mapped to the guest sound device"
I don't quite follow what the use case is here. Do you have an understanding of what a host audio device being mapped to a guest sound device would be used for?

I'm also not quite sure what do we want to achieve with the addition of a sound device. So far we didn't add a sound device since we stopped supporting graphical remote access to the guests with Spice.
I think if someone would want to pass a host sound device, it would require a device plugin and #3937 would provide it.

I'm also not quite sure what do we want to achieve with the addition of a sound device. So far we didn't add a sound device since we stopped supporting graphical remote access to the guests with Spice.
I think if someone would want to pass a host sound device, it would require a device plugin and #3937 would provide it.

@vladikr Thx for your reply. And I'd like to know why kubevirt stopped supporting graphical remote access to the guests with Spice? Because of my company's cloud-desktop scenario based on spice, I also want to contribute the spice feature.  Is there any record of it?  Thx again.
Also, can we support sound device like:
<devices>
<sound model='ich6'>
<codec type='micro'/>
</sound>
</devices>
Any example?
Thx again.

And the sound device doesn't map to a host device. Hmmm, I think nobody wants to listen to music with a compute node~ It is the spice which transfers data to the client (like remote viewer).

from https://libvirt.org/formatdomain.html#audio-devices
"A virtual audio device corresponds to a host audio backend that is mapped to the guest sound device"
I don't quite follow what the use case is here. Do you have an understanding of what a host audio device being mapped to a guest sound device would be used for?

I'm not sure, in my scenario, it is configured as:
<devices>
<sound model='ich6'>
<codec type='micro'/>
</sound>
</devices>
Seems it doesn't map to a real host device, also no pci device to passthrough.

And I'd like to know why kubevirt stopped supporting graphical remote access to the guests with Spice? Because of my company's cloud-desktop scenario based on spice, I also want to contribute the spice feature. Is there any record of it?

I don't think we'd necessarily block someone from attempting to add spice support, but it's not something on our road map or something we're interested in supporting given how complex it will be to implement
Our stance has been that we provide vnc/console support, and if someone needs something more advanced then it should involve connecting to the guest directly (like rdp). Because of the way KubeVirt ties VMIs into the Pod network, libvirt and qemu do not have direct network access. This means things like vnc and console connections have to be proxied out of the pod via a unix socket to another environment that has network access, then proxied from there to the client generally over a websocket. Spice involves multiple connections and this proxy technique isn't as feasible.
Are you still interested in this sound device even without spice support?

And I'd like to know why kubevirt stopped supporting graphical remote access to the guests with Spice? Because of my company's cloud-desktop scenario based on spice, I also want to contribute the spice feature. Is there any record of it?

I don't think we'd necessarily block someone from attempting to add spice support, but it's not something on our road map or something we're interested in supporting given how complex it will be to implement
Our stance has been that we provide vnc/console support, and if someone needs something more advanced then it should involve connecting to the guest directly (like rdp). Because of the way KubeVirt ties VMIs into the Pod network, libvirt and qemu do not have direct network access. This means things like vnc and console connections have to be proxied out of the pod via a unix socket to another environment that has network access, then proxied from there to the client generally over a websocket. Spice involves multiple connections and this proxy technique isn't as feasible.
Are you still interested in this sound device even without spice support?

Fine! It makes sense. And let me improve my patch later. Thx again~

@wangzh21 could you explain how to set yaml file after apply your patch? any doc can refer to?


Fix ORT whisper example

Type of Change
bug fix
API changed or not: no
Description
Fix ORT whisper example
How has this PR been tested?
extension test
Dependency Change?
no

https://inteltf-jenk.sh.intel.com/job/nlp_toolkit_optimize_validation_localtest/3517/

https://inteltf-jenk.sh.intel.com/job/nlp_toolkit_optimize_validation_localtest/3518/


test(e2e): Enable priv init container for OpenShift

Signed-off-by: Kalya Subramanian<EMAIL_ADDRESS>
Description:
Partially fixes #3097

Affected area:

Functional Area

New Functionality
[ ]

Documentation
[ ]

Install
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Ingress
[ ]

Egress
[ ]

Networking
[ ]

Observability
[ ]

SMI Policy
[ ]

Sidecar Injection
[ ]

Security
[ ]

Upgrade
[ ]

Tests
[X]

CI System
[ ]

Demo
[ ]

Performance
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?
No

Is this a breaking change?
No

Codecov Report

Merging #3480 (32df6ce) into main (d858adb) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3480      +/-   ##
==========================================
+ Coverage   65.87%   65.90%   +0.02%
==========================================
  Files         169      169
  Lines        7886     7886
==========================================
+ Hits         5195     5197       +2
+ Misses       2660     2658       -2
  Partials       31       31

Flag
Coverage Δ

unittests
65.90% <ø> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/kubernetes/announcement_handlers.go
77.14% <0.00%> (+5.71%)
:arrow_up:

Continue to review full report at Codecov.

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


HHH-12787 - SessionJdbcBatchTest hangs with DB2

https://hibernate.atlassian.net/browse/HHH-12787

Basically, this is what we need to do to intercept JDBC operations:

If SQL statement logging is what we need, then SQLStatementInterceptor is the way to go since it does not require JDBC mocking or stubbing
If we need JDBC mocking or stubbing, then PreparedStatementSpyConnectionProvider is unavoidable. But then, we need the test will @RequiresDialectFeature(DialectChecks.SupportsJdbcDriverProxying.class) so we can skip such tests for those JDBC Drivers that cannot be proxied.

@vladmihalcea looks good to me. Thanks for taking the time to convert all the tests that could be converted.
We will need this in 5.3 too.


Dynamically set placeholder prop to SearchBar according to query

What this PR does / why we need it?
Showing total counts of projects / documents can increase UX
Any background context you want to provide?
I tried to add new DOM for showing total counts of search results,
but after having discussion on Discord channel, I decided to put the information on placeholder.
What are the relevant tickets?
Fixes #34
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Stop compiled js/css from being committed during development

When I run npm run dev while developing it changes these files. Since those files are compiled during deployment I thought it would be a good idea to stop changes from happening in these directories.

I was wrong. Turns out it doesn't. Deploy script:
cd /home/forge/symposiumapp.com
git pull origin master
composer install --no-interaction --prefer-dist --optimize-autoloader
echo "" | sudo -S service php7.1-fpm reload

if [ -f artisan ]
then
    php artisan migrate --force
fi

I'd love to add it eventually so we could actually be building the prod assets, but I'm a bit wary of doing an npm run prod and taking the site down for how long that takes on every deploy. Maybe it's worth moving the site over to Envoyer so we can get a full Capistrano-style deploy? hmmm

@greydnls i changed my mind. it's like this on develop now. :) thanks!


Adding support for terraform_version_map

what & why

Adding the ability to pass a terraform_version_map that will dictate which patch version of Terraform to use for each minor version

/test all

/rebuild-readme

/test all

/test all

/test bats readme


A - Elliptic Arc Render Issue

Elliptic Arc does not render.
Gist for the example
Kivg :

SvgPathEditor :

Hi @VICTORVICKIE, thanks for pointing it out. Honestly, arcs are kinda pain to work with but, fortunately, there are workarounds. I've added some useful links in the Readme that one can use to modify a few svg files in order to work with this library.
Kindly read here: https://github.com/shashi278/svg-anim-kivy#useful-links and let me know if that's useful.


Multi-Language Scripting API

I know this engine is set to support C# scripting soon, but I have an idea that could potentially enable the engine to support a multitude of programming languages while only maintaining one. You may have heard of a programming language called "Haxe". Well, not many seem to know that it's compiler has an interesting feature that allows it to trans-pile to multiple different languages, including C#, C++, lua, java, etc! It might not be perfect, but Haxe, including it's compiler, is open-source... It's just an idea to consider!
If you wish to read up on the language and it's compiler, they have a manual:
https://haxe.org/manual/compiler-usage.html
Thanks for your time,
erherhh4herh.

I haven't heard of it actually. At first glance, the fact that it's open source and that it can generate source code for a multitude of languages are two big pluses. If Haxe hides the trans-pilation complexity well enough (e.g. it trully comes down to those compiler arguments) then I can't think of anything negative.
Of course, I'm just thinking out loud here, I will have a look at it during the weekend to get a more in-depth understanding. I'll leave this issue open as a reminder that scripting has to be taken care of at some point and/or further discussion etc.
Thanks for your time as well erherhh4herh :-)

is C# scripting still continuing?

Yes. Although I'll probably switch to .Net Core instead of moving forward with Mono.


Liquibase doesn't validate bad formatted SQL changesets

Environment
Formatted SQL changelogs
Liquibase Version:
Any
Liquibase Integration & Version:
CLI
Database Vendor & Version:
Any supported database
Operating System Type & Version:
Win, Linux
Description
When running the validate or status or update commands, Liquibase should go over the changesets in the target changelog (Formatted SQL, XML, JSON and YAML) and check for any Liquibase related syntax errors.
However, it appears that the case is inconsistent for Formatted SQL changelogs.
If the structure of a Formatted changeset is incorrect or have bad syntax, Liquibase will just skip that changeset.
Steps To Reproduce

Run the below changesets.  Notice that the first changeset starts with a single “-“ instead of double “--“.  Also notice that the second changeset is missing a unique ID (only has an author "SteveZ").

--liquibase formatted sql
-changeset SteveZ:45555-createtablecontacts labels:onlytest
CREATE TABLE contacts (
id int GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
firstname VARCHAR(255),
lastname VARCHAR(255)
);
--rollback drop table contacts;

--changeset SteveZ
CREATE TABLE actor (
id int GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
firstname VARCHAR(255),
lastname VARCHAR(255)
);
--rollback drop table actor;

Actual Behavior
After running the update command the changesets will be skipped.
Expected/Desired Behavior
Liquibase should throw an error indicating the there is something wrong with the changesets.
Additional Context

I also reproduced this issue using a formatted SQL changelog; in my case, I tried both with a duplicated changeset and by changing SQL in deployed changesets. As you found, @szandany, this feature does not work as expected.
Thanks for writing this up!


Override plugin if available in eslint config

Fixes - https://github.com/babel/babel/issues/10675

Thank you for the PR. Now that @babel/eslint-parser has been released, we are making this repository read-only. If this is a change you would still like to advocate for, please reopen this in the babel/babel monorepo.


MAINT: remove time print lbfgsb fixes #8417

Removes print statement for elapsed time in LBFGSB, fixes #8417

I checked this manually, the timing part isn't printed out with the rest of the info, and the minimization still works.


Shouldn't it be the opposite?

like
this.result.configFilename = isESMModule ? "eslint.config.js" : "eslint.config.mjs";
should instead be
this.result.configFilename = isESMModule ? "eslint.config.mjs" : "eslint.config.js";
No ?

it's working as expected - the generated config is always esm, and it has be .mjs in type: "commonjs".
Have you encountered any problems? Please provide as much detail as possible.


disconnectedBuffer Queue dos'not release command

i can't foud the io.lettuce.core.cluster.ClusterNodeEndpoint.disconnectedBuffer
where release the command recources, it caused my program oom,becourse the  disconnectedBuffer hold too many objects
references.

disconnectedBuffer gets GC'd once the connection is closed and there are no more references to the actual cluster connection.
If that doesn't work for some reason, please provide a minimal example that is able to demonstrate the issue.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Alert containers do not resize when text runs over multiple lines, icon also shrinks

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have read the contributing guidelines

Describe the issue
As seen in the below image, the alert container does not resize with multi-line text. Also the icon that is shown shrinks in size to become almost invisible.

Reduced test cases
No response
What operating system(s) are you seeing the problem on?
Windows, macOS, Android, iOS, Linux
What browser(s) are you seeing the problem on?
Chrome, Safari, Firefox, Microsoft Edge, Opera
What is the issue regarding ?
@trimble-oss/modus-web-components
What version of npm package are you using ?
No response
Priority
Low
What product/project are you using Modus Components for ?
Predesign, AddLocation, Spaces
What is your team/division name ?
Habitat/SketchUp
Are you willing to contribute ?
Yes
Are you using Modus Web Components in production ?
no

Plan:

Grows in height to fit content
Up to UX to make sure text length is reasonable
Icon should not shrink
Maintain padding around text as text wraps


Multiple node elments can't be created Exception

Description
var html = "

FOO

BAR

";
var htmlNode = HtmlNode.CreateNode(html);

Throws exception: Multiple node elments can't be created.
Exception
Exception message: Multiple node elments can't be created.
Stack trace:
System.Exception : Multiple node elments can't be created.
   at HtmlAgilityPack.HtmlNode.CreateNode(String html)

Fiddle or Project
https://dotnetfiddle.net/jfdjpB
Further technical details

HAP version: 1.11.24
NET version netcore 3.1

Worked fine in HAP 1.8.14

Hello @moikot ,
Sorry for the waiting time.
Unfortunately, this issue happen cause we fixed the P tag.

HTML does not allow a paragraph to contain a table.

Ref: https://stackoverflow.com/a/28042932/5619143
This is still possible to go back to the old behavior by disabling the new P behavior HtmlDocument.DisableBehaviorTagP = false;
HtmlDocument.DisableBehaviorTagP = false;
var html = "

FOO

BAR

";
var htmlNode = HtmlNode.CreateNode(html);

Let me know if that solves your issue.
Best Regards,
Jon

Hello @JonathanMagnan ,
Thank you for the clarification. As soon as it's not allowed by HTML and there is a workaround, I'm good.


refactor: Implement typed SelectionInfo object

I took a look at what was done with the SelectionRelations and thought about how best to introduce a typed object, that works for both relations and complex objects.

@TriPSs , So I updated this original draft based on the discussions that have taken place previously.
Key notes:

Fixed bugs in graph and added support for queries with Fragments and Union types
Removed secondary parse with graphql-parse-resolve-info package, ResolveInfo is now parsed within the nestjs-query
Remove type contraint on BaseServiceResolver to fix TS2322 issue
Cast assembler.convertQuery result as unknown to mask typeconversion mismatch

Initially looking through the changes (on mobile) it's not really how I had it in mind though.
Will update the looking ahead of total count tonight so you can see how I though on tackling it OK?
We can than discuss from there

Not sure why this PR is now closed but with #151 merged you should have all the info needed, all the info of that decorator is still marked as internal with the warning that it can change so we can still bring changes to that if we want.


Fixes behavior in Ember 3.1 (#2)

Little fix from @luketheobscure's original PR.
https://github.com/aupac/ember-aupac-typeahead/pull/66

@pjcarly The Travis CI build failed. Can you look into fixing?

There you go. Fails weren't related to code, It was a headless chrome issue.

<EMAIL_ADDRESS>


Update Schematics for Angular 11.2 Tailwind CSS Support

Angular 11.2 adds Tailwind CSS support.
~Test @apply in a library bundled with ng-packagr~ no support for @apply in a library

[x] Update setup

Steps to add Tailwind CSS to Angular 11.2
Update Angular CLI npm i -g @angular/cli@next as its not published as latest yet
npm install -D tailwindcss

# init tailwind.config.js
npx tailwindcss init

Add to styles.css
@tailwind base;
@tailwind components;
@tailwind utilities;

Or add to styles.scss
@import "tailwindcss/base";
@import "tailwindcss/components";
@import "tailwindcss/utilities";

Add build script to enable purge during prod build and also with cross-env
"scripts: {
  "build:prod": "NODE_ENV=production ng build --prod"
}

Updating from before Angular 11.2

Update angular.json by replacing ngx-build-plus with @angular-devkit/build-angular and remove "extraWebpackConfig": "webpack.config.js",.
Delete the file webpack.config.js
Remove devDependencies autoprefixer, ngx-build-plus, postcss, postcss-import, postcss-loader, postcss-scss

@garygrossgarten do you like to test it out?
npm i -g @angular/cli@next

ng new test

cd test

ng add ngx-tailwind@dev


Feat/5.5.0/Connector-apis

This PR contains connector service related changes

[x] Create connector
[x] Delete connector
[x] Reset password
[x] Apis docs

Build finished.