Default Scope with Paranoia Column Not Applied in Rails 7.2 has_many relations

Hi,
Thanks for maintaining this gem.
I'm encountering an issue after upgrading my app from Rails 7.1 to Rails 7.2. Here's what I'm seeing:
Previously in Rails 7.1:
Parking.first.to_sql
# => "SELECT * FROM parkings WHERE parkings.deleted IS NULL"

Parking.first.spots.to_sql
# => "SELECT spots.*  FROM spots WHERE spots.parking_id = 1"

It seems that when fetching rows from a has_many or has_one association, the default_scope with the paranoia_column is no longer being applied. This change is causing issues in our application.
Is there a way to restore the previous behavior?
Thanks in advance!

@navidemad I can't seem to reproduce this issue. Can you share some of the table structure and the acts_as_paranoid calls?

Hi @mvz
The gem seems to be working fine with a default project as I removed all the unnecessary gems to find out which one was faulty, apparently it comes from the gem "arel_extensions".
I make a reproducible ruby bundle inline script for you:
Create a file called bug.rb with the following content and run it as ruby bug.rb
# frozen_string_literal: true

require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  git_source(:github) { |repo| "https://github.com/#{repo}.git" }

  gem "pg", "1.5.7"

  # It is working with this version
  # gem "activerecord", "<IP_ADDRESS>", require: false
  # It is not working with this version
  gem "activerecord", "7.2.0", require: false
  gem "acts_as_paranoid", "0.10.2", require: false
  gem "arel_extensions", "2.1.11", require: false
end

require "active_record"
require "arel_extensions"

ActiveRecord::Schema.verbose = false
ActiveRecord::Base.logger = nil
ActiveRecord::Base.then do |base|
  base.establish_connection(adapter: "postgresql", host: "localhost", database: "postgres")
  begin
    base.connection.create_database("acts_as_paranoid_bug_report")
  rescue ActiveRecord::DatabaseAlreadyExists
    base.connection.drop_database("acts_as_paranoid_bug_report")
    base.connection.create_database("acts_as_paranoid_bug_report")
  end
  base.establish_connection(adapter: "postgresql", host: "localhost", database: "acts_as_paranoid_bug_report")
end

ActiveRecord::Schema.define do
  create_table :parkings, force: true do |t|
    t.string :name, limit: 255, null: false
    t.datetime :created_at, precision: nil
    t.datetime :updated_at, precision: nil
    t.datetime :deleted_at, precision: nil
  end
  add_index :parkings, :deleted_at

  create_table :spots, force: true do |t|
    t.integer :parking_id, null: false
    t.string :number, limit: 255, null: false
    t.datetime :created_at, precision: nil
    t.datetime :updated_at, precision: nil
    t.datetime :deleted_at, precision: nil
  end
  add_index :spots, :parking_id
  add_index :spots, :deleted_at
end

ActiveRecord::Base.logger = Logger.new($stdout)

require "acts_as_paranoid"
require "minitest/autorun"

class ApplicationRecord < ActiveRecord::Base
  self.abstract_class = true
end

class Parking < ApplicationRecord
  acts_as_paranoid
  has_many :spots, dependent: :destroy
end

class Spot < ApplicationRecord
  acts_as_paranoid
  belongs_to :parking
end

class BugTest < Minitest::Test
  def setup
    parking = Parking.create!(name: "Foo")
    parking.spots.create!(number: "42")
  end

  def test_output_has_many_relation
    puts ("#" * 100) + Parking.last.spots.to_sql
    assert Parking.last.spots.to_sql.include?("\"spots\".\"deleted_at\" IS NULL")
  end
end

I have commented on this issue on our repo, but I think @mvz you should be looking at it as well, since the issue is Relation + the variable that causes the breaking is Rails 7.2 and not arel_extensions, as I explained here https://github.com/Faveod/arel-extensions/issues/114#issuecomment-2296773755.
I'm getting myself more familiar with acts_as_paranoid, but I don't think I will be able to catch it as fast as you guys.

Thanks for the info @navidemad and @stackmystack, I'll take a look as well to see if I can figure out what's going wrong here.

With some bisecting from rails v<IP_ADDRESS> to v7.2.0, i used the following script:
Apparently it starts to fail from this commit:
c313d9161360f4539afeb36cc8353ad29ba6bef3 is the first bad commit
commit c313d9161360f4539afeb36cc8353ad29ba6bef3
Author: Rafael Mendonça França<EMAIL_ADDRESS>Date:   Tue Nov 28 16:59:45 2023 +0000

    Remove deprecated support to pass `rewhere` to `ActiveRecord::Relation#merge`

 activerecord/CHANGELOG.md                          |   4 +
 activerecord/lib/active_record/relation/merger.rb  |  10 +--
 .../lib/active_record/relation/spawn_methods.rb    |  20 +----
 .../lib/active_record/relation/where_clause.rb     |  20 +----
 activerecord/test/cases/relation/merging_test.rb   | 100 ---------------------
 guides/source/7_2_release_notes.md                 |   2 +
 6 files changed, 14 insertions(+), 142 deletions(-)
 ` ` `

```ruby
# frozen_string_literal: true

# Usage: ruby <absolute_path/bug.rb> --bisect

require "bundler/inline"
require "open3"

RAILS_REPO_PATH = "/tmp/rails"

# Function to checkout a specific commit in the Rails repository
def checkout_rails_commit(commit)
  system("git clone https://github.com/rails/rails.git #{RAILS_REPO_PATH}") unless Dir.exist?(RAILS_REPO_PATH)
  Dir.chdir(RAILS_REPO_PATH) do
    system("git fetch --all")
    system("git checkout #{commit}")
  end
end

# Function to get the current commit hash and message
def current_commit_info
  Dir.chdir(RAILS_REPO_PATH) do
    commit_hash = `git rev-parse HEAD`.strip
    commit_message = `git log -1 --pretty=%B`.strip
    return commit_hash, commit_message
  end
end

# Function to run the test
def run_test
  Bundler.with_unbundled_env do
    output, _status = Open3.capture2("ruby #{__FILE__} --no-bisect")
    if output.include?("Failure")
      return false
    else
      return true
    end
  end
end

# Function to run git bisect
def bisect
  Dir.chdir(RAILS_REPO_PATH) do
    # Start the bisect process
    system("git bisect start")
    system("git bisect good v<IP_ADDRESS>")
    system("git bisect bad v7.2.0")

    # Run the test on each commit during bisect
    system("git bisect run ruby #{__FILE__}")

    # Finish the bisect process and get the result
    system("git bisect reset")
  end
end

# If we are running the bisect process
if ARGV.include?("--bisect")
  bisect
  exit
end

# Main script logic, executed during each bisect step
checkout_rails_commit("HEAD") # Check out the current HEAD or relevant commit

commit_hash, commit_message = current_commit_info
puts "Testing commit #{commit_hash}: #{commit_message}"

gemfile(true) do
  source "https://rubygems.org"

  git_source(:github) { |repo| "https://github.com/#{repo}.git" }

  gem "pg", "1.5.7"

  # Point to the current commit of ActiveRecord from the local Rails repo
  gem "activerecord", path: RAILS_REPO_PATH, require: false
  gem "acts_as_paranoid", "0.10.2", require: false
  gem "arel_extensions", "2.1.11", require: false
end

require "active_record"
require "arel_extensions"

ActiveRecord::Base.logger = nil
ActiveRecord::Schema.verbose = false
ActiveRecord::Base.then do |base|
  base.establish_connection(adapter: "postgresql", host: "localhost", database: "postgres")
  begin
    base.connection.create_database("acts_as_paranoid_bug_report")
  rescue ActiveRecord::DatabaseAlreadyExists
    base.connection.drop_database("acts_as_paranoid_bug_report")
    base.connection.create_database("acts_as_paranoid_bug_report")
  end
  base.establish_connection(adapter: "postgresql", host: "localhost", database: "acts_as_paranoid_bug_report")
end

ActiveRecord::Schema.define do
  create_table :parkings, force: true do |t|
    t.string :name, limit: 255, null: false
    t.datetime :created_at, precision: nil
    t.datetime :updated_at, precision: nil
    t.datetime :deleted_at, precision: nil
  end
  add_index :parkings, :deleted_at

  create_table :spots, force: true do |t|
    t.integer :parking_id, null: false
    t.string :number, limit: 255, null: false
    t.datetime :created_at, precision: nil
    t.datetime :updated_at, precision: nil
    t.datetime :deleted_at, precision: nil
  end
  add_index :spots, :parking_id
  add_index :spots, :deleted_at
end

require "acts_as_paranoid"
require "minitest/autorun"

class ApplicationRecord < ActiveRecord::Base
  self.abstract_class = true
end

class Parking < ApplicationRecord
  acts_as_paranoid
  has_many :spots, dependent: :destroy
end

class Spot < ApplicationRecord
  acts_as_paranoid
  belongs_to :parking
end

class BugTest < Minitest::Test
  def setup
    parking = Parking.create!(name: "Foo")
    parking.spots.create!(number: "42")
  end

  def test_output_has_many_relation
    assert Parking.last.spots.to_sql.include?("\"spots\".\"deleted_at\" IS NULL")
  end
end

# Execute the test and exit with appropriate status during bisect
exit(run_test ? 0 : 1) if ARGV.include?("--no-bisect")

I've done a git bisect on the Rails repository and it tells me this starts breaking at https://github.com/rails/rails/commit/c313d9161360f4539afeb36cc8353ad29ba6bef3. I don't know yet how that change breaks things.

For reference, here is the version of bug.rb that I used for bisecting:
# frozen_string_literal: true

require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  gem "sqlite3", "~> 1.7.3"

  gem "activerecord", require: false, path: "./activerecord"
  gem "activesupport", require: false, path: "./activesupport"
  gem "activemodel", require: false, path: "./activemodel"

  gem "acts_as_paranoid", "0.10.2", require: false
  gem "arel_extensions", "2.1.11", require: false
end

require "active_record"
require "arel_extensions"

ActiveRecord::Schema.verbose = false
ActiveRecord::Base.logger = nil
ActiveRecord::Base.then do |base|
  base.establish_connection(adapter: "sqlite3", database: ":memory:")
end

ActiveRecord::Schema.define do
  create_table :parkings, force: true do |t|
    t.string :name, limit: 255, null: false
    t.datetime :created_at, precision: nil
    t.datetime :updated_at, precision: nil
    t.datetime :deleted_at, precision: nil
  end
  add_index :parkings, :deleted_at

  create_table :spots, force: true do |t|
    t.integer :parking_id, null: false
    t.string :number, limit: 255, null: false
    t.datetime :created_at, precision: nil
    t.datetime :updated_at, precision: nil
    t.datetime :deleted_at, precision: nil
  end
  add_index :spots, :parking_id
  add_index :spots, :deleted_at
end

ActiveRecord::Base.logger = Logger.new($stdout)

require "acts_as_paranoid"
require "minitest/autorun"

class ApplicationRecord < ActiveRecord::Base
  self.abstract_class = true
end

class Parking < ApplicationRecord
  acts_as_paranoid
  has_many :spots, dependent: :destroy
end

class Spot < ApplicationRecord
  acts_as_paranoid
  belongs_to :parking
end

class BugTest < Minitest::Test
  def setup
    parking = Parking.create!(name: "Foo")
    parking.spots.create!(number: "42")
  end

  def test_output_has_many_relation
    puts ("#" * 100) + Parking.last.spots.to_sql
    p Parking.last.spots.where_values_hash
    assert Parking.last.spots.to_sql.include?("\"spots\".\"deleted_at\" IS NULL")
  end
end

Do'h, @navidemad you already did that bisect. Sorry I missed that ...

I can confirm that reverting that commit on top of the v7.2.0 tag in the Rails repository fixes this bug.

This part looks strange to me: https://github.com/rails/rails/commit/c313d9161360f4539afeb36cc8353ad29ba6bef3#diff-2a3cf8f0755b5c5706f693ab23d6953cfec15f5eda8a3f348edede22ccfabf04
The default is nil, but the change changes the implementation to the version for when the value is not nil.
The only way that can work is if predicates_unreferenced_by(other) and except_predicates(other.extract_attributes) do the same thing. My guess is that they do, but arel_extensions somehow makes them do different things.

I foucsed on the new except_predicats method, and it contains a call attrs.include? attr. With arel_extensions that call returns true, without it it returns false. It boils down to the following two objects being considered equal when arel_extensions is present:
#<struct Arel::Attributes::Attribute
relation=#<Arel::Table:0x00007fbf1eafef30 @name="spots", @klass=Spot(id: integer, parking_id: integer, number: string, created_at: datetime, updated_at: datetime, deleted_at: datetime), @type_caster=#<ActiveRecord::TypeCaster::Map:0x00007fbf1ec20990 @klass=Spot(id: integer, parking_id: integer, number: string, created_at: datetime, updated_at: datetime, deleted_at: datetime)>, @table_alias=nil>,
name="deleted_at">
#<struct Arel::Attributes::Attribute
relation=#<Arel::Table:0x00007fbf1eafef30 @name="spots", @klass=Spot(id: integer, parking_id: integer, number: string, created_at: datetime, updated_at: datetime, deleted_at: datetime), @type_caster=#<ActiveRecord::TypeCaster::Map:0x00007fbf1ec20990 @klass=Spot(id: integer, parking_id: integer, number: string, created_at: datetime, updated_at: datetime, deleted_at: datetime)>, @table_alias=nil>,
name="parking_id">

Clearly, these two objects differ by their name property. It looks like arel_extensions overrides the equality operator: https://github.com/Faveod/arel-extensions/blob/master/lib/arel_extensions/attributes.rb#L21.
@stackmystack can you take a look at this and tell me what you think?

On it.

@navidemad could you please try this on your main project?
  gem 'arel_extensions', git: 'https://github.com/stackmystack/arel-extensions', branch: 'rails-7.2-attributes'

The issue of Attribute equality is indeed from arel-extensions as you noted @mvz.
I'm having a discussion with other maintainers of arel-extensions to make a better decision than the one I did in the suggested branch.

Equality will be deprecated and removed.

Thanks @stackmystack. Regarding deprecations: I looked at your branch and the deprecation message there, and I hope you can tie the deprecation to an arel_extensions release instead of a Rails release.

Thanks @stackmystack. Regarding deprecations: I looked at your branch and the deprecation message there, and I hope you can tie the deprecation to an arel_extensions release instead of a Rails release.

We don't have scheduled releases like rails, so we can't promise a depreciation at a specific point in time, or a version number. But maybe you mean conditioning the warning emission on a arel_exteisions version and not that of rails?

But maybe the warning message should be clearer and make sure users understand it's a message from arel_extensions.

Yes, that seems important since users could upgrade to a new arel_extensions version that drops those methods while staying on the same Rails version.

I'm going to close this issue because there's nothing to do on the part of acts_as_paranoid.


fix: Fixed ImproperConfig import error

Fixes ImportError raised on use of the CLI inside semantic_release/pypi.py.
Fixes, Resolves, and Closes Issue #376
fixes#376
Issue Raised By: Ron Nathaniel
PR Submitted By: Ron Nathaniel

Thanks 👍


[error-issue] Add class for finding git blame info for each line of a stacktrace

Part of https://github.com/ampproject/amphtml/issues/27675
Easiest to follow commit-by-commit rather than file-by-file
Top-down view:
PASS  test/utils.test.ts
  parsePrNumber
    ✓ parses the PR number from a commit message (3ms)
    ✓ returns 0 when the commit message contains no PR number
  parseSource
    ✓ parses the components of a standardized source URL:line string (1ms)
    non-standardized sources
      ✓ returns null for "https://cdn.ampproject.org/rtv/2004030010070/v0.js:1337"
      ✓ returns null for "unexpected-token-js:1" (1ms)
      ✓ returns null for "https://raw.githubusercontent.com/ampproject/amphtml/undefined"
  parseStacktrace
    ✓ parses frames from a stacktrace string (1ms)

 PASS  test/rate_limited_graphql.test.ts
  RateLimitedGraphQL
    ✓ returns the query result (17ms)
    ✓ queues multiple queries and executes after delay (4ms)

 PASS  test/blame_finder.test.ts
  BlameFinder
    blameForFile
      ✓ issues a GraphQL query for the file the the specified ref (18ms)
      ✓ caches blame queries for rtv-path pairs (17ms)
      ✓ queries `master` if the ref is invalid (13ms)
      ✓ returns blame ranges (7ms)
    blameForLine
      ✓ finds the relevant blame range (6ms)
      ✓ makes only one request per file (6ms)
      ✓ throws an error if no range contains the desired line (6ms)
    blameForStacktrace
      ✓ fetches blame info for lines in the stacktrace (4ms)

--------------------------|---------|----------|---------|---------|-------------------
File                      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------------------|---------|----------|---------|---------|-------------------
All files                 |     100 |      100 |     100 |     100 |
 src                      |     100 |      100 |     100 |     100 |
  blame_finder.ts         |     100 |      100 |     100 |     100 |
  rate_limited_graphql.ts |     100 |      100 |     100 |     100 |
  utils.ts                |     100 |      100 |     100 |     100 |
 test/fixtures            |     100 |      100 |     100 |     100 |
  index.ts                |     100 |      100 |     100 |     100 |
--------------------------|---------|----------|---------|---------|-------------------
Test Suites: 3 passed, 3 total
Tests:       17 passed, 17 total
Snapshots:   0 total
Time:        4.015s

You know how I feel about using real data with real usernames for tests :( I thought we decided to scrub test data?

We discussed it and did some of it, but over the past few months in PR discussions with @danielrozenberg we haven't stuck with it. I can maybe see reasoning for doing so with non-public information, but these tests are meant to reflect real world data, and it's all public information within the repository. Manually scrubbing fixtures just doesn't seem to add any benefit, and takes up a significant amount up time

You know how I feel about using real data with real usernames for tests :( I thought we decided to scrub test data?

We discussed it and did some of it, but over the past few months in PR discussions with @danielrozenberg we haven't stuck with it. I can maybe see reasoning for doing so with non-public information, but these tests are meant to reflect real world data, and it's all public information within the repository. Manually scrubbing fixtures just doesn't seem to add any benefit, and takes up a significant amount up time

To add to this last point, it doesn't only add a significant amount of one-time work, it also makes it more difficult to keep these tests fixtures up-to-date because you either have to re-scrub them, or you have to merge the changes. By using the data coming back from the GitHub API as-is we make it easier to override these files whenever we need to update the fixtures

Ok, I can understand keeping it because it is public information.
The point I made last time, which I'll make again here, is that "significant amount of work" is not a good enough reason to skip scrubbing private data.

The point I made last time, which I'll make again here, is that "significant amount of work" is not a good enough reason to skip scrubbing private data.

Noted :+1: Did you have any other concerns that I haven't addressed here yet?

Noted 👍 Did you have any other concerns that I haven't addressed here yet?

All addressed 👍 thanks @rcebulko.

Bumping this for approval if all looks good :upside_down_face:


Update release-1.4.14

This ports late changes to release-1.4.13 into release-1.4.14.

bors merge


Added move types

Added feature:
Three movement mode of panorama

touch
motion
all (touch and motion)

Example "MonoImage" changed for demonstrate new feature.

@Allui hey,
Regarding the issue: https://github.com/ejeinc/MetalScope/issues/28#issuecomment-332152687
do you have a solution for iOS11? I saw your comment but it doesn't hlep.
Thanks,
Eliza

Hi @Allui,
Thanks for your PR!
I will check back later this week, but before that I will be saved if you reflect the updates I pushed to the master branch 🙏


MP4

https://github.com/user-attachments/assets/ca1f8579-20d7-46c9-b1de-573796b94ed5

https://github.com/user-attachments/assets/211ee32b-61e8-46a5-bf9e-fdb5dc069b24


pfp: expose computation method

recently we gained a way to compute the PFP directly, considering all pods (standard behavior up until now) or only pods with exclusive resources allocated to them.
Expose the computation method as NRT attribute, to enable the consumers to know explicitely how the PFP was computed and react accordingly.

/lgtm
/approve
I'm not an expert on that area, but look like a trivial change armed with an e2e test + all test are passing so LGTM.

/cc


autocompletion + difference from c pkg

Hey friend! Would you like a second maintainer to ensure no loneliness here? Big fan of this nifty utility :)
Have you tested the autocompletion feature? It doesn't seem to work for me... Also, this is the python client; are there any differences or any potential dis/advantages of building the c pkg?

[x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Yes, the more the merrier!
I packaged the python implementation because a) it looks well maintained, b) python is easy to package for conda-forge, and c) that is what Arch Linux packages. The closest thing to an "official" command line client is the npm version according to https://github.com/tldr-pages/tldr/wiki/tldr-pages-clients but it didn't seem so much better as to justify the more difficult exercise of packaging npm packages for conda-forge.
The documentation instructions for enabling autocomplete but I haven't looked into it: https://github.com/tldr-pages/tldr-python-client#autocomplete

I see. Agree with the ease and perhaps maintenance of python as opposed to c, etc.
I will submit an issue to get me added here


Shutdown command and more

A command to shutdown the app after finishing to use.

Since this app is now designed to work 24/7, this command is not necessary anymore. I'll close this issue.


Plex unable to get posters/show description

Describe the bug
clean install on 18.04 using the script; also installed Sonarr, Transmission, Couchpotato; everything works except Plex cannot seem to find any metadata, posters are black, no show description, actor etc.
It appears the Plex container can't access the Internet. (using default 'host' networking).
I have a FreeNas Server running Plex as a plugin on same LAN and that is working fine, so can't be network or firewall.
I've also tried running in 'bridge' mode, but same issue.
Sonarr is running in the same docker and is working fine, getting artwork etc.
Anyone else seen this, could it be a host config issue? I'm at a loss how to fix this and this stops me from migrating from FreeNAS.
Thanks for any pointers.
Environment

Ansible-NAS revision (f96bf92):
Ansible version:
ansible 2.5.1
config file = /home/dongennl/ansible-nas/ansible.cfg
configured module search path = [u'/home/dongennl/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.15+ (default, Oct  7 2019, 17:39:04) [GCC 7.4.0]
Ansible-NAS operating system:
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"
Are you running the playbook from a remote box or the Ansible-NAS box itself?  local
media is on ZFS but that seems to work fine.

Expected behavior
Plex should be able to find metadata and show posters/descriptions.
Actual behavior
Black posters and 'get metadata' seems to time out; nothing in container log.
Steps to reproduce
Add some shows from disk and force metadata refresh

Interesting one, and not something that's caused by Ansible-NAS - we simply spin up the linuxserver/plex image. What version of that are you using, and what version of Plex itself?
Other things you could try (again, not related to Ansible-NAS):

I'm assuming from your issue that you're only trying to retrieve movie metadata - does it work for music?
What metadata source are you using?
Are your files named correctly for Plex to be able to search for the right thing?

I can only suggest you jump on the Plex forums and try some of the suggestions on there, you are most certainly not the first person to have this issue .eg - https://forums.plex.tv/t/unraid-linuxserver-plex-cover-art-not-downloading/440246/10

Hi, you are right, not due to the script; I managed to log into the running Plex container and verify that it could reach the outside world.
Turns out the posters/descriptions work ok for Films, just not TV shows. Read elsewhere that theTVDatabase are having API changes/troubles, so that is probably causing it.
Sorry!

Great, glad you got it sorted :+1:


fix: cannot set salts for credential creation (suggestion)

This is my suggestion on how to solve #221 .
I know this is a breaking change, but I don't think we need the additional interface for IssueCredentialArgs. I think it just adds confusion with the additional mapping of properties. Same for the other operations such as create identifier, rotate etc.

It's good if the API can accept exn messages directly, without property mapping.
The API probably becomes harder to use with the compact one letter property names. Need to make sure all required properties are declared and have some reasonable documentation.

I just listened in on the dev call and wanted to provide some comments.
It seems like this change sparked some discussion on which direction to take regarding the API. I am voting for going towards a signify API that as closely as possible resembles the API of KERIA. The additional property mapping just is just another layer of indirection that in itself requires documentation. Some benefits of the approach:

Documentation of the signify-ts API can be derived or implied from KERIA API documentation.
Typescript types for request and response object shapes can probably be completely generated by openapi tooling (once Openapi specs for keria is complete).
Less issues of the type #221 (there has previously been more issues like this)

Also, for this particular API of issuing credential, a user of this library could add their own functions for ACDC creation according to which ever schema they want to use, like this.
function createQviCredentialData(args: QviCredentialData): CredentialData {
    return {
        ri: args.registryId,
        i: args.issuerPrefix,
        s: "EBf...",
        a: { LEI: args.LEI, i: args.recipientPrefix }
    }
}

const data = createQviCredentialData({ registryId, issuerPrefix: "abc", recipientPrefix: "def", LEI: "123" })
await credentials().issue("issuer", data)

As @psteniusubi mentioned as well, the fact that the API can accept the same shape of objects that is passed in exchange messages is a huge plus in my opinion, as can be seen in this change: https://github.com/WebOfTrust/signify-ts/pull/222/commits/7022f95e7056862e1ec5a66d85938732656f70a1#diff-6d0716ef2bd3e3e9494efe4b175ef940675ac2c0615c4d98172c7c5f69671c9aR906.
If we decide to go for this approach, we should probably plan to change the rest of the API to do follow the same strategy and then strictly adhere to it going forward.
I do see the argument against it as well though, using more descriptive property names is helpful, but the benefits mentioned are just much greater in my opinion.

@lenkan - I agree with the suggestion to move forward with compact labels.
The Keri spec already has definitions for message types and labels. (I could not immediately find all message types, for example "iss" and "vcp" are missing.)
As you suggest it is relatively easy to build a higher lever abstraction on top of the lower level Signify API. One could even implement a backwards compatibility layer.
There is at least one catch. Because Keri sets strict rules on ordering of the fields, the Signify API should still internally re-build all messages. I don't think the API can internally use the spread ... operator. For messages that originate from the API client ordering is not known, or there could exist unknown fields.
Should this design change apply to signifypy as well?


sparsetools.cxx call_thunk can segfault due to out of bounds if strlen(spec) < MAX_ARGS during cleanup

At: https://github.com/scipy/scipy/blob/master/scipy/sparse/sparsetools/sparsetools.cxx#L420
It shouldn't be accessing spec[j] unchecked. Probably the loop should be modified to iterate through spec like in the other loops in that function.

We found this potential segfault using AddressSanitizer.

Thanks, pretty obvious bug.

Do you need a patch for this?  I hit this recently (also detected w/ ASAN) and would like to see it fixed upstream.  I've tried a similar approach to LazyKoala with success.

@dakoner that would be very helpful, thanks


Ctrl+tab+arrow keys not working

Since VSCode update version 1.44 a few days ago, the shortcut to switch between open editor tabs (ctrl+tab) won't work with the up/down arrows.
So, keystroke ctrl+tab, then release 'tab' while holding down the ctrl key drops down the open editors list, but you can't navigate  up or down the list with up/down arrows. This behaviour stopped working as of the March 2020 version 1.44 update.

/duplicate #94775


Add support for systems rolling multiple dice or dice types

Currently, this only supports a single die, a d20 for example. It would be great if we could configure this to work for multiple dice.
Example, is Savage Worlds, can use d4,d6,d8,d10, and d12. Along with rolling that, the user also rolls a d6 as a player character, known as a wild card (also special NPC's). Such as, if their skill is a d8, they would roll a d8, plus their wildcard d6, and take the best of the two.
So I think ideally, it would just look at whatever dice are rolled, and use the minimum and maximum as a baseline for a crit fail or success. In savage worlds, there's no critical successes per se, but if you roll a max number on a dice it explodes and can roll another dice. likewise, a critical failure is when both of your dice roll a 1, not just one of them.
Any chance we could try and get support like this (I know it all wouldn't be immediate) would bre pretty awesome. This could work with other systems as well. such as 2d6/3d6 systems, 2d10, or whatever.

This will imply almost a full rewrite of the module for the current implementation. And as of now, we have no plans to continue developing features. Sorry.


Remove sample prefix from file names

Sample-specific files are in sample-specific subdirectories (in branch use-umi-tools-deplex-84, #84). Remove sample-prefix from file names. Requires update to code, docs, workflow images (in docs-80 branch) and regression test samples (provide HOW-TO for how to restructure current regression test samples directory)

See branch remove-sample-prefix-114. This includes changes merged in from branch config-86 (see #86).

Done, will create pull request in new year.

Merged via pull request #125.


test/drbgtest.c: call OPENSSL_thread_stop() explicitly

The manual says this in its notes:
... and therefore applications using static linking should also call
OPENSSL_thread_stop() on each thread. ...

Fixes #8171

I did not check whether/why the leak does not occur on linux or whether/why it is not detected by mdebug. Do you think we should?

This is answered by the fuller context of the man page that @levitte referenced:
Resources local to a thread are deallocated automatically when the thread exits
(e.g. in a pthreads environment, when pthread_exit() is called). On Windows
platforms this is done in response to a DLL_THREAD_DETACH message being sent to
the libcrypto32.dll entry point. Some windows functions may cause threads to exit
without sending this message (for example ExitProcess()). If the application
uses such functions, then the application must free up OpenSSL resources
directly via a call to OPENSSL_thread_stop() on each thread. Similarly this
message will also not be sent if OpenSSL is linked statically, and therefore
applications using static linking should also call OPENSSL_thread_stop() on each
thread. Additionally if OpenSSL is loaded dynamically via LoadLibrary() and the
threads are not destroyed until after FreeLibrary() is called then each thread
should call OPENSSL_thread_stop() prior to the FreeLibrary() call.

This is answered by the fuller context of the man page that @levitte referenced

If I understand it correctly, calling OPENSSL_thread_stop() manually is not necessary when pthreads are used, but it does no harm to call this cleanup function twice. So it is just a matter of taste whether one adds it only to the Windows thread function or to both thread functions for the sake of symmetry, correct?

Yes, I don't see it being a problem if it gets called twice.

Merged.
master:
03cdfe1efaf2a3b5192b8cb3ef331939af7bfeb8 test/drbgtest.c: call OPENSSL_thread_stop() explicitly
1.1.1:
eaacc2475044b624a7b3b1ecd9ebe5953a6ff45d test/drbgtest.c: call OPENSSL_thread_stop() explicitly


UI review for 2.0 launch

(Please don't close this issue before 2.0 launch. Sub-tasks can be marked as completed. Grouped by section)
SELECTION UI - 1ST TIME USE

[ ] Release notes popup: remove for first time users (they should be focusing on starting quickly - tracking latest changes is not interesting to them)
[ ] Implement the large tooltip pointing to Learn as designed here: https://www.figma.com/file/ttKKFbqVWEPg3BNseXmSsb/Towards-2.0?node-id=2287%3A10135&t=BojHnYKqKJsI8PSo-1

SELECTION UI - RECURRING USER

[ ] Header: Have the main search there as designed. We can mimic the same exact logic than the Ctrl+p search
[ ] Header: remove the action from the monokle icon.
[ ] Recent projects: When that area its empty (1st time use or I deleted all projects): show a simple text that says: "Click on New project on the left menu to create a project" (adding the plus icon next to new project label)
[ ] All projects: When that area its empty  (1st time use or I deleted all projects): show a simple text that says: "Click on New project on the left menu to create a project" (adding the plus icon next to new project label)
[ ] Settings: all content below the tabs is contained on a grey box. Delete that box or have the color transparent or the same color as the background.
[ ] Settings > Plugins manager: let's have the install action aligned left and within a grey box (as it is now, but aligned left). The templates can appear below, out of the box, as said above.
[ ] Its great that we have the left menu column fixed and the middle column scrolling itself (settings, learning...). But can we have that scroll to the right of the whole page? maybe having the central column and the right empty one being just one element?
[ ] Three dots menu on the top right: add a bit more padding overall (circa 10px) to the whole dropdown. Now text goes very to the right border of the dropdown element.
[ ] "connect to cluster" label on the left menu. are we ok with that label? shouldn't it be "quick cluster preview" or "cluster preview"? more on cluster section below.

CLUSTER DASHBOARD

[ ] When connecting to a cluster the header with my current project stays there, but cluster connection is independent (since it has its own left menu also). The header  should not show the three lines and the name of the project, but a Back to projects button, as in design: https://www.figma.com/file/YrcAzt79dPB2keqt2QDft7/Cluster-management?node-id=706%3A5593&t=c57A5cwmYo25iqEL-1
[ ] Related to previous one, when I exit cluster mode, the editor UI header stays in top of the selection UI, see illustration below. Fix. User should be in either editor UI or selection UI. It's even possible to change projects and you still see the cluster left menu - you get in a loop you can't scape from.

[ ] Error count badges in resource groups list on the left. Now they are in a circle. Let's have them into an adaptative rectangle (16px height, adaptpative width) with sufficient radius (8px), so the tag nicely adapts to whichever long number.
[ ] Same with error badges on the main area, in resources list.
[ ] Status module: it appears weirdly floating within its space with different margins than the rest of the modules. See illustration. Fix to appear as the others, same height as the one on the right, etc

EDITOR UI
Validation tab (left pane)

[ ] blue header: to the text "Visualize & fix errors according to your validation setup." lets add (in the same line): "Set up your validation policy, activate/deactivate rules, etc in the settings section from the left menu." being "settings" word a link to the settings, corresponding tab.
[ ] Errors list: errors appear collapsed. Guess we want it like that for performance?
[ ] When no error is selected the editor appears empty. Let's have the same UI that in the View GIT operations tab (see image below) with the text "Select an error in the left to view it in the code, fix it, get fixing tips and more."

[ ] Errors list: do we want tooltips for items in the left or the error? validation source, severity, line of code... I would have them.
[ ] Errors list: lets have the error badge with same looks as in the resources pane (not totally round ones)
[ ] Code: we are briefly highlighting the line of code containing the error. Looks great but since its on the bottom of the code view (last visible loc) it kind of gets unnoticed a bit. Can we have the line of code in the center of the view instead or the bottom? or simulate that somehow?

[ ]  Accordion is hiding when you select Files

[ ] Three dots still talk about "what's new in 1.13"
[ ] Learn button is not available in the files view


Adjust to new DirectoryProvider structure

Backs off Directory that is provided, allows a hardcoded root to get back to where it was
Allows us to unpin our dependency on dodal (through it, ophyd-async)

Noting that this will need to be moved: https://github.com/DiamondLightSource/blueapi/issues/353

IMPORTANT: Must also now unpin dependency on dodal

As it is this is fine, all the code seems to be replaced in DiamondLightSource/dodal#445. Except there are tests in this PR that have no correspondent in dodal. Could you make a PR on dodal that moves the appropriate tests over?

I've been working on it today: the FakeDetector structure wasn't correct for how a StandardDetector actually uses a DirectoryProvider


Performance issue with predictBest()

recognizer.predictBest(cvFace, unknownThreshold);
takes between 75-110ms on a 1280x720 frame resized to 500. Is this normal?

I installed openblas and rebuilt dlib. Predition times are down to about 40-70ms but I still think its slower than it should be. Its running on a Linux server 6-core AMD CPU with 16GB Ram.

40-70ms seems to be very decent performance on the CPU, if you ask me

I have 2461.929 ms :) it's a problem for me...


decoration::blur::enabled = 1 Makes Max FPS Half of Monitor Refresh Rate

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit b240704bee1d04eacc27654ea875cf6f15033c7c dirty (renderer: allow rendering multiple fullscreen windows in third fs pass).
Date: Tue Jan 9 14:42:07 2024
Tag: v0.34.0-37-gb240704b

Bug or Regression?
Bug
Description
Upon setting decoration::blur::enabled 1, my FPS immediately goes from the maximum (refresh rate of the monitor) to exactly half of that. In my case it went from 144 to 72.
I highly doubt that this is just a "blue is intensive, of course FPS is lower" type of scenario. If that were the case, it would not make sense for the FPS to be exactly half of the max refresh rate, or for it to  be so stable around that point.
 Enabling that option just makes my FPS non-existent, so I have not checked with it on
How to reproduce
Start glxgears. toggle decoration::blur::enabled 1, and wait for FPS to stabilize. Toggle it back to 0, wait for the FPS to stabilize. On my system, the end FPS with blur was exactly half of the refresh rate.
Crash reports, logs, images, videos

In the beginning, blur was enabled, FPS = 72. When it was disabled, FPS rose to the refresh rate. Later, I enabled it again, FPS halved.

If that were the case, it would not make sense for the FPS to be exactly half of the max refresh rate, or for it to be so stable around that point.

kinda would. Why don't you post hyprctl systeminfo as requested?

"hyprctl systeminfo" is simply not working for me, unfortunately, prints the "usage: hyprctl" info.
I would like to understand why it makes sense for blur to halve the FPS to exactly half of the refresh rate. From my perspective, if it was a bit more than half, or a bit less, I would agree. But for it to be exactly half, like, 72.00, and hold that framerate for a minute straight with barely any deviations, seems like it would be far too unlikely a coincidence.

partial upgrades moment?

I would like to understand why it makes sense for blur to halve the FPS to exactly half of the refresh rate. From my perspective, if it was a bit more than half, or a bit less, I would agree. But for it to be exactly half, like, 72.00, and hold that framerate for a minute straight with barely any deviations, seems like it would be far too unlikely a coincidence.

well learn about how graphics stacks in vsync applications work, especially wayland. That should help understand why this happens.

Yeah, I think you might be right.

Did you manage to solve this problem? I have the same situation and I saw that the problem is due to the fact that the hyprland session is running on the iGPU. Yes, as I have two iGPU graphics cards from Intel and nvidia GPU on my laptop. I was not able to solve this problem and make hyprland run on nvidia. The nvidia-smi command shows that Hyprland is using 1mib. The only solution I found was to increase the frequency of the integrated graphics card from 300-350 by default to 900. This could be a solution, but it always makes me use the fans, which is annoying.


Python Console Fuzzy Search

Version and Platform (required):

Binary Ninja Version: 4.2.5756
OS:
OS Version:
CPU Architecture:

Bug Description:
The new fuzzy search makes tab completion inconvenient compared with the previous behavior. We should probably disable ui.scripting.fuzzySearch by default, or fix the tab completion handling to match that of other familiar editors.

Also tab-completing current_function. shows all the dunder methods in the suggestions. All members tarting with _ should only be shown when completing an _


no support in new SDK?

I know that not all documentation is up to date with the new Azure.Storage.Blob package. That's ok, but I can't seem to find anything related to SAS in the new SDK. Are we supposed to use the older Microsoft.Azure.Storage.Blob SDK? Did I miss something? Or will support for SAS be added later?

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

ID: 4ba8dd43-ef02-5c5c-382d-f8d653721280
Version Independent ID: 4127d388-f82a-b182-c912-879cf854c37a
Content: Create a service SAS for a container or blob with .NET - Azure Storage
Content Source: articles/storage/blobs/storage-blob-service-sas-create-dotnet.md
Service: storage
Sub-service: blobs
GitHub Login: @tamram
Microsoft Alias: tamram

@LanderVe - Thanks for your feedback! Take a look at the example for creating a user delegation SAS. It shows how to use the new library to create a SAS.
For a service SAS, you can use a similar approach, but you'll want to use the other overload for BlobSasBuilder.ToSasQueryParameters, the one that takes a shared key credential.
Let us know if you have any problems. Meanwhile, we'll work on getting a similar example into the service SAS docs.

#please-close

Much appreciated, thanks a lot!

@tamram Thanks for the response. :+1:


What you did with ELK stack

Hi, what you did with elk stack? did you doing real time detection? Thanls!

Hi,
Yes exactly. I got the logs through a docker and implemented the detector in real time.

Hi i'm doing my last project on college to detect intrusion on network
I already did the project and try to implement with dataset  ciccseids2018.
I got high accuracy on dataset, but high false alarm on real time data. I
use TCP Dump to capture into the pcap file and use CICflowmeter to extract
into cicflowmeter format.
I use this
https://github.com/iPAS/TCPDUMP_and_CICFlowMeter
Can you help me with your approach? Thanks
On Tue, Aug 13, 2024, 22:59 Hady Hammad @.***> wrote:

Hi,
Yes exactly. I got the logs through a docker and implemented the detector
in real time.
—
Reply to this email directly, view it on GitHub
https://github.com/HadyKh/Feature-Selection-in-DDoS-attacks/issues/1#issuecomment-2286599717,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATWXCYI4PKIQZH66RG2EGV3ZRIUOPAVCNFSM6AAAAABLR4AOJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBWGU4TSNZRG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Are you sure that your model is not overfitting the training data?
Also how many features used to train the model?


Feature: Allow Elements in list Constructor of Message Being str

I was trying to compose a Message (in nonebot.adapters.onebot.v11) object, but encountered some problems.
At first, I tried the following code:
Message('Example message')

It returned a Message object, with text "Example message," just as expected.
Later on, I decided to have the bot at me in the IM software, so I updated the code to be:
Message(['Example message', MessageSegment.at(42)])

Let us pretend that my id is 42 in the IM software. Surprisingly, the code failed on linting, as there is only list[TMS] constructor for Message.
The problem is actually easily solvable by simply making 'Example message' into MessageSegment.text('Example message'), or to be more clear, like:
Message([MessageSegment.text('Example message'), MessageSegment.at(42)])

However, I am not satisfied by the solution, as Message(MessageSegment.text('Example message')) and Message('Example message') are equal to each other, but Message(['Example message', MessageSegment.at(42)]) cannot even pass the linter.
Moreover, if I just turn a blind eye to the linter and run the code anyway, Message(['Example message', MessageSegment.at(42)]) and Message([MessageSegment.text('Example message'), MessageSegment.at(42)]) are equal to each other as well!
Please let me know if there is a unseen problem preventing me from construct Message with ['Example message', MessageSegment.at(42)], otherwise I recognize this as a typing mistake. It would be good and unarguably increase the quality of my life to make it pass the linter.

Hi, the problem I want to point out here is that
Although the code can be run, this is a non-recommended way. The code may be more confusing to developer. Some reasons:
First, Message("some text here") is not equal to Message(MessageSegment.text("some text here")).
Passing a raw string to Message class will make the adapter to construct the text into a list of MessageSegments. Here's an example for onebot v11:
Message("[cq:at,qq=123123]") == Message([MessageSegment.at(123123)])

As you can see, raw string input will be convert to structured segments. So, passing a string to Message class is calling parsing action.
Back to your code, Message(["some text here", MessageSegment.at(123123)]) is also not equal to Message([MessageSegment.text("some text here"), MessageSegment.at(123123)]), because of the action of parser constructing.
But why type hint does not allow this behavior? As the code you provided, passing a string in list is confusing! The actual behavior is not consistent with what you think. So, we limited the Message class type hints to ensure that user will not writing such confusing code.
Finally, some recommended way:

Write every segment type. This will prevent unexpected behavior.MessageSegment.text("some text here") + MessageSegment.at(123123)

Construct separately.Message("some text here") + MessageSegment.at(123123)

In onebot adapter only, for security reason, string will not cause construct if used in binary operator."some text here" + MessageSegment.at(123123)


Uncaught SyntaxError: Identifier 'module' has already been declared.

Uncaught SyntaxError: Identifier 'module' has already been declared.
Trying to use goog.require(...) or anything similar results in a compiler error stating: Failed to compile. 'goog' is not defined. This is probably a side effect of the first error.
There seems to be a module variable in the google closure library that does not play well with another module variable already existing in the react app.

Can you post a minimal reproduction/example? The full stacktrace from your first error would be helpful as well.


Calling internal commands

It would be cool if you could execute a command using the -c option just like in bash.
node main.js -c "my-command"
It could also be cool if you could require the node file and run commands manually. This way we can share the CLI code.

Why would you want to fix the CLI code. Is it related to USSD codes in any way? (Just dial 46 on your mobile phone if you can an EE mobile and you'll be able to examine the output of the USSD code).

Not sure what you're talkig about there. I'm saying that i have a command:
vorpal.command('my-command').action(/*...*/)

and I'd like to be able to run that command from a bash script.

That's pretty basic.

@ccorcos, you can use vorpal.parse(process.argv) to run the commands given as arguments. Doing that only when -c is given as a parameter should be quite easy thing to add to your own app. Adding it to Vorpal by default would require an unnecessary major version bump as someone might already be using it for their own app (and therefore being a breaking change).

awesome. .parse should do it though! thanks
On Mon, Feb 29, 2016 at 2:29 PM, Ristomatti Airo<EMAIL_ADDRESS>wrote:

@ccorcos https://github.com/ccorcos, you can use
vorpal.parse(process.argv) to run the commands given as arguments. Doing
that only when -c is given as a parameter should be quite easy thing to
add to your own app. Adding it to Vorpal by default would require an
unnecessary major version bump as someone might already be using it for
their own app (and therefore being a breaking change).
—
Reply to this email directly or view it on GitHub
https://github.com/dthree/vorpal/issues/121#issuecomment-190428978.

Are people still talking about parsing? So last year.

@ristomatti nailed it. Closing this issue.
@ccorcos if you have any question on Vorpal, feel free to ask in Stack Overflow! I'm very fast to respond, among others, and it helps build the general knowledge base.

No. You do not ever close this issue because you haven't fixed the underlying problem as you know dthree.

Of course, if you edit the compiler you can force the compiler to run from bash but to force a compiler to run is completely wrong and will cause a huge number of problems for you down the line.

@GranularDetective your comments are not sequitur to the discussion. It honestly sounds like you're trolling, which will get you blocked.

You don't understand what I'm telling you or more likely you are pretending not to understand.


CPDNPQ-867 Iterate the "Where do you work" page

Context
Ticket: https://dfedigital.atlassian.net/browse/CPDNPQ-867

@javier-npq
On the 'check answers and confirm page' the answer given needs to be updating to 'Yes' or 'No' Currently 'Yes' is showing as 'England' and 'No' is empty.

@javier-npq
When a user selects 'No' and completes the registration. Then views their submitted registration it is showing 'Do you work in England?' and 'Yes':

@javier-npq this is all looking good now, thank you


Migrate from NYC to C8 for internal Serenity/JS test automation

NYC doesn't support ECMAScript modules, while C8 does.
Scope:

[x] Replace NYC with C8 for code coverage recording
[x] Replace NYC merge script with an C8 equivalent
[x] Replace HTML report aggregation step with a C8 equivalent
[x] Avoid recording coverage reports in Windows, LTS-1 and LTS+1 jobs since they don't use it anyway

Done in #1682


fix: Automation Script Modification

What type of PR is this?
/kind bug

What does this PR do?

Automation Script Modification
Which issue(s) does this PR fix?

Fixes #210
Special notes for your reviewer:

Does this PR introduce a user-facing change?

@hanweisen @duanmeng @wuyingjun-lucky

@hanweisen @duanmeng @wuyingjun-lucky

@lvtaococo Why at me?

@duanmeng Sorry, I thought you were my colleague. Your real name is the same as my colleague's.

@duanmeng Sorry, I thought you were my colleague. Your real name is the same as my colleague's.

Small world hahaha

/approve
/lgtm


[Windows] DebugAdapter bin folder not found on path

DebugAdapter bin folder not found on path C:/..../.vscode/extensions/ms-vscode.csharp-0.3.7/coreclr-debug/debugAdapters/OpenDebugAD7.exe.
Dotnet-Cli info:
OS: Windows 10
dotnet-cli:
Version: 1.0.0-beta-001598
Commit Sha: 7582649f88
This is on a brand new install of VSCode.  Works in linux.
error: The supplied user buffer is not valid for the requested operation
dotnet exited with error code 1
Error while installing .NET Core Debugger.

Have you opened a csharp file after installing the C# extension? The acquisition of the debugger bits for the specific platform you are on will not be triggered until a C# file is opened.

Nevermind, I see that the the acquisition is triggered and failing. Is there an install.log file in C:/..../.vscode/extensions/ms-vscode.csharp-0.3.7/coreclr-debug?

There is.  I appear to not have access to this file?

That is strange. Are you an administrator on the box?

I am opening notepad++ as administrator, and attempting to open the file.
Getting the following:

I'm not sure why you're seeing this. Here's what I would try:

Close all VS Code instances.
Delete the debugAdapters directory inside C:/..../.vscode/extensions/ms-vscode.csharp-0.3.7/coreclr-debug.
Completely uninstall your current dotnet cli from Control Panel -> Programs -> Programs and Features.
Reinstall the dotnet cli from here: https://dotnetcli.blob.core.windows.net/dotnet/beta/Installers/<IP_ADDRESS>661/dotnet-win-x<IP_ADDRESS>.001661.exe (this version supports portable pdb's on windows).
Open VS Code and open a C# file, triggering the acquisition of the debugger again.

that link just keeps asking if I want to download the C# extensions.  Even after downloading + restarting.

what is "that link"?

@zach-folwick Do you have any more information on this?

This problem has be solved?
I come with the same one.But I think that focus on the version of .NET Core?
https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger.md

@zach-folwick you can try open [.vscode\extensions\ms-vscode.csharp-0.3.7] by VSC, then publish.

Downloading and configuring the .NET Core Debugger...
log  : Restoring packages for C:\Users\Zushun.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.json...
info : Committing restore...
log  : Lock file has not changed. Skipping lock file write. Path: C:\Users\Zushun.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.lock.json
log  : C:\Users\Zushun.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.json
log  : Restore completed in 2072ms.
NuGet Config files used:
C:\Users\Zushun.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\NuGet.config
Feeds used:
https://www.myget.org/F/dotnet-core/api/v3/index.json
https://api.nuget.org/v3/index.json
https://www.myget.org/F/coreclr-debug/api/v3/index.json
Publishing dummy for DNXCore,Version=v5.0
Project dummy (DNXCore,Version=v5.0) was previously compiled. Skipping compilation.
Publishing dummy 1.0.0 ...
Publishing Microsoft.CSharp 4.0.1-rc3-23829 ...
Publishing Microsoft.DotNet.CoreHost 0.0.1-beta-00001 ...
Publishing Microsoft.NETCore.Platforms 1.0.1-rc3-23829 ...
Publishing Microsoft.NETCore.Runtime 1.0.2-rc3-23829 ...
Publishing Microsoft.NETCore.Runtime.CoreCLR 1.0.2-rc3-23829 ...
Publishing Microsoft.NETCore.Runtime.Native 1.0.2-rc3-23829 ...
Publishing Microsoft.NETCore.Targets 1.0.1-rc3-23829 ...
Publishing Microsoft.NETCore.Targets.DNXCore 5.0.0-rc3-23829 ...
Publishing Microsoft.NETCore.Windows.ApiSets 1.0.1-rc3-23829 ...
Publishing Microsoft.VisualStudio.clrdbg 14.0.25109-preview-2865786 ...
Publishing Microsoft.VisualStudio.clrdbg.MIEngine 14.0.30309-preview-2 ...
Publishing Microsoft.VisualStudio.Debugger.Interop.Portable 1.0.1 ...
Publishing Microsoft.VisualStudio.OpenDebugAD7 1.0.20308-preview-1 ...
Publishing Microsoft.Win32.Primitives 4.0.1-rc3-23829 ...
Publishing NETStandard.Library 1.0.0-rc3-23829 ...
Publishing NETStandard.Platform 1.0.0-rc3-23829 ...
Publishing Newtonsoft.Json 7.0.1 ...
Publishing System.AppContext 4.1.0-rc3-23829 ...
Publishing System.Collections 4.0.11-rc3-23829 ...
Publishing System.Collections.Concurrent 4.0.12-rc3-23829 ...
Publishing System.Collections.Immutable 1.2.0-rc3-23829 ...
Publishing System.Collections.NonGeneric 4.0.1-rc3-23829 ...
Publishing System.Collections.Specialized 4.0.1-rc3-23829 ...
Publishing System.ComponentModel 4.0.1-rc3-23829 ...
Publishing System.ComponentModel.Annotations 4.1.0-rc3-23829 ...
Publishing System.ComponentModel.EventBasedAsync 4.0.11-rc3-23829 ...
Publishing System.Console 4.0.0-rc3-23829 ...
Publishing System.Diagnostics.Contracts 4.0.1-rc3-23829 ...
Publishing System.Diagnostics.Debug 4.0.11-rc3-23829 ...
Publishing System.Diagnostics.Process 4.1.0-rc3-23829 ...
Publishing System.Diagnostics.StackTrace 4.0.1-rc3-23829 ...
Publishing System.Diagnostics.Tools 4.0.1-rc3-23829 ...
Publishing System.Diagnostics.Tracing 4.1.0-rc3-23829 ...
Publishing System.Dynamic.Runtime 4.0.11-rc3-23829 ...
Publishing System.Globalization 4.0.11-rc3-23829 ...
Publishing System.Globalization.Calendars 4.0.1-rc3-23829 ...
Publishing System.Globalization.Extensions 4.0.1-rc3-23829 ...
Publishing System.IO 4.1.0-rc3-23829 ...
Publishing System.IO.FileSystem 4.0.1-rc3-23829 ...
Publishing System.IO.FileSystem.Primitives 4.0.1-rc3-23829 ...
Publishing System.Linq 4.1.0-rc3-23829 ...
Publishing System.Linq.Expressions 4.0.11-rc3-23829 ...
Publishing System.Net.Http 4.0.1-rc3-23829 ...
Publishing System.Net.Primitives 4.0.11-rc3-23829 ...
Publishing System.Net.Sockets 4.1.0-rc3-23829 ...
Publishing System.ObjectModel 4.0.11-rc3-23829 ...
Publishing System.Reflection 4.1.0-rc3-23829 ...
Publishing System.Reflection.Emit 4.0.1-rc3-23829 ...
Publishing System.Reflection.Emit.ILGeneration 4.0.1-rc3-23829 ...
Publishing System.Reflection.Extensions 4.0.1-rc3-23829 ...
Publishing System.Reflection.Primitives 4.0.1-rc3-23829 ...
Publishing System.Reflection.TypeExtensions 4.1.0-rc3-23829 ...
Publishing System.Resources.ResourceManager 4.0.1-rc3-23829 ...
Publishing System.Runtime 4.1.0-rc3-23829 ...
Publishing System.Runtime.Extensions 4.1.0-rc3-23829 ...
Publishing System.Runtime.Handles 4.0.1-rc3-23829 ...
Publishing System.Runtime.InteropServices 4.1.0-rc3-23829 ...
Publishing System.Runtime.InteropServices.PInvoke 4.0.0-rc3-23829 ...
Publishing System.Runtime.InteropServices.RuntimeInformation 4.0.0-rc3-23829 ...
Publishing System.Runtime.Numerics 4.0.1-rc3-23829 ...
Publishing System.Runtime.Serialization.Primitives 4.1.0-rc3-23829 ...
Publishing System.Security.Cryptography.Algorithms 4.0.0-rc3-23829 ...
Publishing System.Security.Cryptography.Primitives 4.0.0-rc3-23829 ...
Publishing System.Text.Encoding 4.0.11-rc3-23829 ...
Publishing System.Text.Encoding.Extensions 4.0.11-rc3-23829 ...
Publishing System.Text.RegularExpressions 4.0.12-rc3-23829 ...
Publishing System.Threading 4.0.11-rc3-23829 ...
Publishing System.Threading.Tasks 4.0.11-rc3-23829 ...
Publishing System.Threading.Tasks.Dataflow 4.6.0-rc3-23829 ...
Publishing System.Threading.Tasks.Extensions 4.0.0-rc3-23829 ...
Publishing System.Threading.Tasks.Parallel 4.0.1-rc3-23829 ...
Publishing System.Threading.Thread 4.0.0-rc3-23829 ...
Publishing System.Threading.Timer 4.0.1-rc3-23829 ...
Publishing System.Xml.ReaderWriter 4.0.11-rc3-23829 ...
Publishing System.Xml.XDocument 4.0.11-rc3-23829 ...
Publishing System.Xml.XmlDocument 4.0.1-rc3-23829 ...
Publishing System.Xml.XmlSerializer 4.0.11-rc3-23829 ...
Published to C:\Users\Zushun.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\debugAdapters
Published 1/1 projects successfully
Error while installing .NET Core Debugger.

My environment:

dotnet --version
1.0.0-beta-002202
code --version
0.10.11

There have been breaking changes in very recent builds of the .NET CLI that cause problems for the 0.37 version of the extension. If you don't care what version of the .NET CLI you use, I would recommend using the instructions on http://dotnet.github.io/getting-started/. If you need to be on newer bits, you can try building the package from the 'dev' branch of this repo.

The latest version of the extension available here should work with the latest builds of the .NET CLI.

@DustinCampbell  The latest version works perfectly on my machine. Cool~ thanks.

Excellent! That's great to hear.


TTS Demos are failing

Describe the bug
I am trying to run TTS pipelines and looks like some of the popular ones are not running.
I wonder if you have any idea of why this is happening.

Reproduction
https://huggingface.co/facebook/tts_transformer-en-ljspeech?text=Hello%2C+this+is+a+test+run
Logs
{"error":"unknown error","warnings":["There was an inference error: layer_norm(): argument 'input' (position 1) must be Tensor, not tuple"]}

System Info
https://huggingface.co/facebook/tts_transformer-en-ljspeech?text=Hello%2C+this+is+a+test+run

cc @cndn @lpw0

Just wanted to follow up on this. thanks! @osanseviero


inconsistent api endpoints in v1.21

Looking at the new remote api endpoints for POST /volumes and POST /networks/create, which both create a new volume or a network, and then looking at the older endpoints like POST /images/create, I get the impression that the POST /volumes endpoint should be renamed to POST /volumes/create.
WDYT?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Hum, yeah there is a little bit of inconsistency it seems. From a pure REST point of view, POST /volumes to create a volume is quite good.

Yes, it should be even POST /images :)

@runcom and POST /containers. But the question(s) then is/are the other actions inspect, stop, … and if docker needs to be implemented in a pure REST way.
Anyway, having consistency — using /…/create or not for all creation operation — would be good :wink:

I would also prefer a more RESTful way, but I wouldn't like to start a discussion about the degree of RESTfulness of the Docker api ;-)
So like @vdemeester said, I'd also prefer consistency over RESTfulness. I actually started to create a PR and can add it here asap.

P.S.: discussing about a more RESTful design of the whole api could be an independent issue.
In this case, I only wanted to help making the upcoming 1.9 Docker release to be consistent with the other endpoints people are already used to.

PR #17136 renames the POST /volumes endpoint. I've run the tests locally, but two failed. I guess that both failing tests only fail on my local setup and not due to the changes in the PR:
FAIL: docker_api_containers_test.go:789: DockerSuite.TestContainerApiCreateWithCpuSharesCpuset

docker_api_containers_test.go:799:
    c.Assert(status, check.Equals, http.StatusCreated)
... obtained int = 500
... expected int = 201

FAIL: docker_api_inspect_unix_test.go:14: DockerSuite.TestInspectApiCpusetInConfigPre120

docker_api_inspect_unix_test.go:19:
    dockerCmd(c, "run", "--name", name, "--cpuset", "0-1", "busybox", "true")
/go/src/github.com/docker/docker/pkg/integration/dockerCmd_utils.go:35:
    c.Assert(err, check.IsNil, check.Commentf("%q failed with errors: %s, %v", strings.Join(args, " "), out, err))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc209d27420)} ("exit status 1")
... "run --name cpusetinconfig-pre120 --cpuset 0-1 busybox true" failed with errors: Warning: '--cpuset' is deprecated, it will be replaced by '--cpuset-cpus' soon. See usage.
Error response from daemon: Requested CPUs are not available - requested 0-1, available: 0.
, exit status 1


XD-2972 Add workaround for Eclipse 1.8 compiler issue

Jira: https://jira.spring.io/browse/XD-2972

LGTM Merged


Add support for service proxies

In the 3.x boilerplate we use arcgisUtils.createMap's layerMixins option to replace layer urls for premium and subscriber content with proxied urls if users choose to enable that option. We need to support this in the 4.x boilerplate. In 4.x there isn't an option to mixin the layers so we'll need to add logic to the app to handle this.

@kellyhutchins I don't think the appProxies property is on the PortalItem in 4x either. At least it's not documented.
I can probably mix them into the WebMap/WebScene items if the appProxies were available on the application item.

@driskull  I spoke to Dasa and it isn't there so we'll just need to get the proxies (if specified) the same way we do in the 3.x boilerplate and then do the layer mixin ourselves.
If you are working on the boilerplate and have time it would be great to add this. If not I can do it.

@kellyhutchins I don't think appProxies is on the item though. How would we get it?

It should be on the application item is it not? If not let me know and I'll setup a test and talk to Dasa.

I don't see it.

Ok I'll look into it and see what I can find out.

@kellyhutchins can you implement this here: https://github.com/Esri/application-boilerplate-js/blob/4masterts/src/boilerplate/Boilerplate.ts#L284 ?
I think we should be able to look at the appProxies and then modify any of the layer URLs that are contained in the webmap/webscene items. In theory. right?

@driskull  sure I'll take a look


Bug: You have to remove (or rename) that container to be able to reuse that name.

Describe the bug
When we use testcontainer in our build pipeline we get the following error:

Conflict ("Conflict. The container name "/testcontainers-ryuk-d5f13be0-c6ab-43c0-83ad-071f3604cb77" is already in use by container "0f610da3c88a6f4ff0d46c71b55219b08db90dd699aa75a990f041e0bccf83b6". You have to remove (or rename) that container to be able to reuse that name.")

To Reproduce
I am not sure what exactly is the cause for that problem, locally everything runs just fine.
Runtime environment
testcontainers 4.5.0
pytest  6.2.5

a workaround for this would be to disable ryuk with TESTCONTAINERS_RYUK_DISABLED, but this is not a known issue, so perhaps if there is anything else different about your build environment that you can share to help debug this, that would be helpful. for example, if tests are running in parallel there

Thanks for the quick reply @alexanderankin!
I already tried to set TESTCONTAINERS_RYUK_DISABLED but without any effect, I will check again, maybe I was just too tired and overlooked something.
regarding our environment: the build pipeline runs on azure dev ops with an on premise agent. I believe also with rootless docker. I saw this is also a known problem so I will confirm if this is the case. Apart from that I think there is nothing unusual.

I am not certain what was the root cause for the error to appear in the first place. If I run a docker ps -a I get nothing.
However, since the pipeline is configured in yaml, and yaml treats some strings as bool, I end up with the environment variable being TESTCONTAINERS_RYUK_DISABLED=True instead of "true". That is why I can't the the workaround to work.
Maybe it would be good to have some normalisation here like .lower()

Okay, it took use quite some time to get to the bottom of this, because debugging things that only happen in build pipelines is a nightmare.
but it appears to be a DinD issue #517
This is the first time we looked into the whole setup inside the pipeline so deeply, so now we are wondering why it ever worked with previous versions of testcontainers (and more specifically what the workaround was).
In essence „our“ code runs in a container that gets starters from the pipeline agent, and that gets assigned its own docker network. When we then start a testcontainer it gets connected to the default bridge network, and the two can’t talk to each other.

yeah so the workaround for dind is basically this code idea here - https://github.com/testcontainers/testcontainers-python/issues/475#issuecomment-2040182302 - we commented it out here - https://github.com/testcontainers/testcontainers-python/pull/388/files#r1366799006 - and this is what folks are seeing with DinD setup.
I am thinking of just undoing it, I don't have the time to really figure out how to resolve or how to even test tc.host to ensure the/a potential fix works for both. youll note that the workaround mirrors the PR that changes it.

What took us much longer to figure out was the fact that the two containers are on different networks. And that also seems to influence the port. So if dind and they are on the same network that the internal port, but otherwise the published port.
So the workaround in the old code is not complete for our case, but we could fix it by always using the puplished port, because local would not be dind.


Hurricane/Weather Events Plugin

It would be cool to have: a job that checks for hurricane advisories; a command to output status of a hurricane or the Atlantic in general; etc.
API: https://www.weather.gov/documentation/services-web-api#/default/get_alerts_active

Could also make this a job so that it alerts when something severe is coming

Could also make this a job so that it alerts when something severe is coming

That’s a splendid idea. Hurricane season is upon us

About to work on this with Cleverwolf soon


Docs: remove all non technical documentation

What happend to the Recipes section? Especially Async tasks was my No.1 rescue page, I often consulted 🙂. Thanks in advance!
(or am I just missing it on the current page)

I migrated the recipes to their own repository just now so they are available again. I'll submit a PR to this repo soon with a link to those recipes.
Mind you, there are still broken links in there and the examples need highlighting (or, preferrably, a REPL). But it's a start :)
https://grossbart.github.io/fp-ts-recipes/

@grossbart would you consider also adding the rambda table?
https://github.com/gcanti/fp-ts/blob/1.x/docs/recipes/ramda.md

@newswim that was for<EMAIL_ADDRESS>for<EMAIL_ADDRESS>there's fp-ts-ramda


Create 3.9.yaml for RandyRants.com's SharpKeys

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

Microsoft Reviewers: Open in CodeFlow

FYI: ran through all four check list items successfully.


release: 4.0.0

Checklist

[x] Assign to next release manager
[x] Close previous release milestone
[x] Create next release milestone
[x] Associate issue with next release milestone

Any progress? There were some problems with the previous release. I want to experience 3.12.1

@pavlelee Very close! You'll see some remaining TODOs from this PR. We need to create issues and add those to this milestone. Follow that for progress updates!

I just realized I will be out of town Dec 2-3 so @code-asher maybe you can handle the release? If not, we can push to Monday, Dec. 6

No problem.

@jsjoeio I am aware, that release 4.0.0 is a major work-over. But it has been postponed many times now.
Keep up the great work and stay focused.

Full of expectation

But it has been postponed many times now.
Keep up the great work and stay focused.

I was out last week to take some vacation with family (we just had a baby), one of our team members has decided to take December off for person reasons and then another team member was pulled into product, hence the postponing.
We're doing the best we can with the bandwidth we have so thank you for understanding!

Keep up the great work and stay focused.

We only have a couple things left to finish so hoping we can get it out this week! 🤞 Thanks for the patience!

An early Christmas present for us 👍. Thanks for the hard work 👏

@jsjoeio  Congratulations for the new baby !
Hope everything going well ~~


tabs 的v-model 设置无效

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome98.0.4758.82
Reproduction Link: https://www.baidu.com/

What is expected?
v-model的值能够正确聚焦

@followyourhreat tabs的v-model需要绑定属性名 https://codesandbox.io/s/happy-visvesvaraya-hy5m57?file=/src/App.vue


chore: Renamed EmbeddingFunctions.py  to follow snakecase convention

Description
Changed models/ EmbeddingFunctions.py to embedding_functions.py
Fixes #659
Type of change
Please delete options that are not relevant.

[x] Refactor (does not change functionality, e.g. code style improvements, linting)

How Has This Been Tested?
Ran poetry run pytest
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

Currently getting this when running poetry run pytest

hey, this error looks something specific to your machine. Tests working fine for me.
Can you please search more about this error on Google/Stack overflow keying in your machine details as well?
I think this should solve the problem.

hey, this error looks something specific to your machine. Tests working fine for me. Can you please search more about this error on Google/Stack overflow keying in your machine details as well? I think this should solve the problem.

I think the issue is I'm running on a Windows machine, and the code is adding a / as a prefix to the path, which produces an invalid Windows path /C:/Users/Osama/AppData/Local/Temp/tmpxt5jtbt_
Do the tests have to work properly on my local machine for the PR to be accepted? Since you mentioned they work fine on yours?

Hey @OsamaNabih , yes will prefer that all the tests should pass before merging.

I switched to a WSL2 Ubuntu 22 and everything is working properly now, all tests are passing

Let me you know if anything else is required
Thank you


Delete rows with matching unique key

Description & motivation
This introduces "merge" behaviour for insert by period to match the standard incremental materialisation. This allows insert by period to be used with models where rows change over time.
I simply copied the code from the standard incremental materialisation here: https://github.com/dbt-labs/dbt-core/blob/8442fb66a591c4f5353f8baaaaf62f846c5f5171/core/dbt/include/global_project/macros/materializations/models/incremental/merge.sql#L50.
Checklist

[x] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[ ] Postgres
[x] Redshift
[ ] Snowflake

[x] I followed guidelines to ensure that my changes will work on "non-core" adapters by:

[ ] dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
[ ] using the limit_zero() macro in place of the literal string: limit 0
[ ] using dbt_utils.type_* macros instead of explicit datatypes (e.g. dbt_utils.type_timestamp() instead of TIMESTAMP

[x] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[x] I have added an entry to CHANGELOG.md

@matthewrj Fancy! Thanks for opening this. It'd be nice to have this process support deletes 👍
Two conflicting thoughts here:

I'd love to see some tests around this to ensure that it behaves correctly. I think this would be a series of seeds with different stages of progress, but I don't know how to cause it to re-run without multiple invocations of the automated tests, which feels a bit fragile...
We're still thinking about the future of this macro (see #410), so I don't want to ask you to do a bunch of work that might go unmerged for a while.

For now, please don't be offended if this sits on ice for a bit - we're about to dive into the future of dbt-utils with a vengeance, so I expect there to be some progress in the next month or two.


What is happening to all these releases!

What is happening to all these releases!

What do you mean?

Test release.........3.XX while we are in 2.XX.
What does test release mean?
Release Note??

There's an issue with the NuGet release version numbering of SqlKata.Execution;
3.2.3 | 1,155 | 19 days ago
2.3.7 | 484 | 8 days ago

It jumps from 2.3.7 to 3.2.3, and depends on SqlKata 3.2.3, which does not exist in NuGet.

Execution required 3.2.3

And latest package is 2.3.7

Yes the version 3.2.3 was released by mistake while we are testing the CI/CD pipeline, and I've requested to unlist it from NuGet.
However it can still be installed if referenced directly, I strongly recommend to ignore the version and not use it in your projects.


Plugin/Preset files are not allowed to export objects, only functions

On running ./node_modules/.bin/babel ./src -d ./lib, I get an error telling my that 'Plugin/Preset files are not allowed to export objects, only functions'.
I am fairly certain that this issue is due to Flow, as when I remove flow from my presets, the error disappears (or rather it is replaced by a different error about flow-syntax which is now not being dealt with).

My babel.config.js:
module.exports = function(api) {

  // Cache the returned value forever and don't call this function again.
  api.cache(true);

  const presets = [
    "@babel/preset-env",
    "flow",
    "mobx",
    "airbnb",
  ];

  return {
    presets,
  };
}

My console error:
><EMAIL_ADDRESS>build /Users/jamesmulholland/proj/composable-mobx
> babel ./src -d ./lib

Error: Plugin/Preset files are not allowed to export objects, only functions. In /Users/jamesmulholland/proj/composable-mobx/node_modules/babel-preset-flow/lib/index.js
    at createDescriptor (/Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/config-descriptors.js:178:11)
    at items.map (/Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/config-descriptors.js:109:50)
    at Array.map (<anonymous>)
    at createDescriptors (/Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/config-descriptors.js:109:29)
    at createPresetDescriptors (/Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/config-descriptors.js:101:10)
    at presets (/Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/config-descriptors.js:47:19)
    at mergeChainOpts (/Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/config-chain.js:315:26)
    at /Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/config-chain.js:278:7
    at buildRootChain (/Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/config-chain.js:89:20)
    at loadPrivatePartialConfig (/Users/jamesmulholland/proj/composable-mobx/node_modules/@babel/core/lib/config/partial.js:85:55)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `babel ./src -d ./lib`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.

My package.json:
{
  "name": "composable-mobx",
  "version": "0.0.1",
  "description": "A package to make dealing with MobX easier",
  "main": "build/index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build": "./node_modules/.bin/babel ./src -d ./lib",
    "flow": "flow"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/Evermind-Digital/composable-mobx.git"
  },
  "keywords": [
    "mobx"
  ],
  "author": "James Mulholland",
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/Evermind-Digital/composable-mobx/issues"
  },
  "homepage": "https://github.com/Evermind-Digital/composable-mobx#readme",
  "dependencies": {
    "axios": "^0.18.0",
    "camelcase-keys": "^5.0.0",
    "flow-typed": "^2.5.1",
    "lodash": "^4.17.11",
    "mobx": "^5.5.1",
    "mobx-react": "^5.3.3",
    "snakecase-keys": "^1.2.0"
  },
  "devDependencies": {
    "@babel/cli": "^7.1.2",
    "@babel/core": "^7.1.2",
    "@babel/polyfill": "^7.0.0",
    "@babel/preset-env": "^7.1.0",
    "@babel/preset-react": "^7.0.0",
    "babel-preset-airbnb": "^3.0.1",
    "babel-preset-flow": "^6.23.0",
    "babel-preset-mobx": "^2.0.0",
    "flow-bin": "^0.83.0"
  }
}

I didn't really manage to resolve this issue, but I found a workaround by just reverting to the last commit before this and then re-doing my steps.

I am fairly certain that this issue is due to Flow, as when I remove
flow from my presets, the error disappears (or rather it is replaced
by a different error about flow-syntax which is now not being dealt
with).

I’m not sure that this is a sound assessment. If you’re not dealing with
Flow syntax, then you’ll have an error at parse time. The “plugin/preset
files are not allowed to export objects, only functions” error is raised
after parse time. So removing Flow simply masks the actual error by
raising another error earlier in the process.
The source of the error message is also in the Babel repository,
not the Flow repository.

This is an issue with the package mentioned in the doc not working with Babel's presets. I had the same issue and just managed to solve by installing the @babel/preset-flow and then listing @babel/preset-flow rather than flow in the presets config.
The page in the doc is a bit misleading and also got me as it says to list "flow" as the preset arg; Also followed the same directions at first 😅
(referencing: https://flow.org/en/docs/tools/babel/)

@rob2d suggestion solved it for me. But here only an additional info.
I'd installed 'babel-preset-flow' before, which throws error.
But  after replacing it with @babel/preset-flow in package.json and in babel.config.js it works  like a charm.
Thanks @rob2d

The problem is probably using a babel 6 plugin with babel 7; I've hit it by ending up with a mixed set of babel 7 and 6 packages due to dependencies.  Making sure you're consistently using one or the other should help.

@mulholio This is an issue with the package mentioned in the doc not working with Babel's presets. I had the same issue and just managed to solve by installing the @babel/preset-flow and then listing @babel/preset-flow rather than flow in the presets config.
The doc is a bit misleading and also got me as it says to list "flow" as the preset arg; Also followed the same directions at first 😅
(referencing: https://flow.org/en/docs/tools/babel/)
[Edit: attempted to fix this with a PR but hadn't signed the CLA/had an awareness about that -- so can't merge that quite yet. But let me know if it doesn't fix things!]

I really don't understand how these two packages differ. But anyways your solution worked like charm. Thanks a lot 👌


Bump moment.js version to 2.21.0

This is a fix for : https://github.com/ansman/validate.js/issues/262

Coverage remained the same at 100.0% when pulling e49fd6c2fbe93068db638b09e2aeb9c3fb0f097b on danielwpz:master into cccc345aa70cda2a59bccdbc240ffd52b7528bda on ansman:master.


Enhancement: Upload to Rackspace Cloud Files

I see that there is an option to upload to AWS. Is it also possible to upload to rackspace cloud files?

No, only support for AWS has been included.


[bazel] Should ensure we share version info among separate workspaces / CMake projects

We should do this either via symlinks or shared tooling, or simple linting.
This should do things like ensure we are:

Fetching the same version of Drake (currently v1.10.0)
Fetching the same version of common supported tooling

Alternatively, we may want to reconsider the multi-Bazel-workspace approach we're using here.

Alternatively, we may want to reconsider the multi-Bazel-workspace approach we're using here.

It does feel like we're fighting bazel by having so many WORKSPACEs. What if we combined drake_ros_core, drake_ros_tf2, and drake_ros_viz into a single package drake_ros? That removes some of the duplication.
Having them in separate packages as they are now allows someone to depend on drake_ros_core without getting the extra dependencies of drake_ros_tf2 or drake_ros_viz, but those extra dependencies are pretty small: tf2_ros, visualization_msgs. It might be worth removing that ability to make maintenance of this repo easier.

Yeah, I'd be fine if Bazel's consumption is monorepo-esque, as Bazel itself has great mechanisms for granularity.
My only concern is how that might affect ergonomics of colcon/ament workflows.
Is it possible for us to have nested stack (in ye olde ROS 1 parlance) for CMake, and then merged for Bazel?
Example:
drake_ros_core/
├──WORKSPACE
└──CMakeLists.txt
drake_ros_tf2/
├──WORKSPACE
└──CMakeLists.txt
drake_ros_viz/
├──WORKSPACE
└──CMakeLists.txt

to
drake_ros/
├──WORKSPACE
├──drake_ros_core/
│  └──CMakeLists.txt
├──drake_ros_tf2/
│  └──CMakeLists.txt
└──drake_ros_viz/
   └──CMakeLists.txt

My only concern is how that might affect ergonomics of colcon/ament workflows.
Is it possible for us to have nested stack (in ye olde ROS 1 parlance) for CMake, and then merged for Bazel?

It would be possible; though, in this case I think combining them might improve the ergonomics. It would make the CMake required to depend on them a bit shorter.
# ---- Before ----
find_package(drake_ros_core REQUIRED)
find_package(drake_ros_tf2 REQUIRED)
find_package(drake_ros_viz REQUIRED)

# Depending on one library
target_link_libraries(mylib PUBLIC drake_ros_core::drake_ros_core)
# Depending on all libraries
target_link_libraries(mylib PUBLIC drake_ros_core::drake_ros_core drake_ros_tf2::drake_ros_tf2 drake_ros_viz::drake_ros_viz)

# ---- After---
find_package(drake_ros REQUIRED)

#...

# Depending on one library
target_link_libraries(mylib PUBLIC drake_ros::core)
# Depending on all libraries
target_link_libraries(mylib PUBLIC drake_ros::core drake_ros::viz drake_ros::tf2)
# Now could have a shortcut to depend on all libraries?
target_link_libraries(mylib PUBLIC drake_ros::drake_ros)

Having separate packages also allows users to install only the dependencies they need, but In this case the difference between drake_ros_core and drake_ros_viz is pretty small. I made an Ubuntu 22.04 container with just the dependencies for drake_ros_core excluding Drake. Then I checked how much more disk space was needed for the dependencies of drake_ros_viz and drake_ros_tf2. It's only 13 MB. I also checked how much Drake's dependencies are, and found that to be 1527 MB more. Since we're already depending on Drake I don't think it's worth trying to give users the opportunity to save another 13 MB.
drake_ros_tf2 and drake_ros_viz extra deps
The following NEW packages will be installed:
  libconsole-bridge-dev libconsole-bridge1.0 ros-humble-class-loader ros-humble-composition-interfaces ros-humble-console-bridge-vendor ros-humble-message-filters ros-humble-rclcpp-action
  ros-humble-rclcpp-components ros-humble-sensor-msgs ros-humble-tf2 ros-humble-tf2-msgs ros-humble-tf2-py ros-humble-tf2-ros ros-humble-tf2-ros-py ros-humble-visualization-msgs
0 upgraded, 15 newly installed, 0 to remove and 0 not upgraded.
Need to get 1408 kB of archives.
After this operation, 12.7 MB of additional disk space will be used.

Need to get 309 MB of archives.
After this operation, 1527 MB of additional disk space will be used.

How about
bazel_ros2_rules/ ...
drake_model_interop/...
drake_ros/
├──BUILD.bazel
├──CMakeLists.txt
├──package.xml
├──WORKSPACE
├──core/
├──tf2/
└──viz/
drake_ros_examples/
├──BUILD.bazel
├──CMakeLists.txt
├──package.xml
└──WORKSPACE
ros2_example_bazel_installed/...

Sweet, that all sounds like a great and convincing analysis to me!

Resolved by #201, thanks!


Replace the use of the ANDROID_SDK_ROOT env variable with ANDROID_HOME

Replace the use of the ANDROID_SDK_ROOT env variable with ANDROID_HOME as the former is deprecated.
See https://developer.android.com/tools/variables#android_home for more details.
Fixes https://github.com/godotengine/godot/issues/80910

Thanks!


Implement 'containsSame' on 'OptionalAssert'

There are times when it is necessary to assert that an Optional not only contains an equal instance but a specific one, i.e. the same which is given to the assertion. (E.g. when working with classes which do not properly implement equals or the implemented equals is - for some reason or another - not sufficient in a given situation.)
These assertions should then fail:
	assertThat(Optional.of(new String("something"))).containsSame(new String("something"));
	assertThat(Optional.of(new Integer(10))).containsSame(new Integer(10));

This pull request implements containsSame which tests for reference equality.

@nicolaiparlog your code is far behind the latest commit on java-8 branch, your code can't be directly merged/rebased since OptionalShouldContain has changed.
Please rebase your on top of the latest java-8 commit.
OptionalShouldContain message has been changed to:
"%nExpecting:%n  <%s>%nto contain:%n  <%s>%nbut did not.", actual, expected

which is fine, no need to update it, just take care of containsSame, speaking of it I suggest to change your message to:
"%nExpecting:%n  <%s>%nand:%n  <%s>%nto contain the same value %s (i.e. compared with ==) but did not.";

Something we might do is that if actual and expected option description are equals, then differentiate them using object hascode, this si already done in ShouldBeEqual and it gives something like:
// both actual and expected toString are identical : Person[name=Jake]
// we differentiate them with hash code (in hexa)
Expecting:
 <"Person[name=Jake] (Person@76724357)">
to be equal to:
 <"Person[name=Jake] (Person@47a34181)">
but was not."

Oh ... please add a test in OptionalShouldContain_create_Test for containsSame message ;-)

See #431 for a continuation of this discussion.


installation failure: unknown switches

Expected behavior and actual behavior
I installed middleman using gem install middleman, and I can see the gem listed in my local gem list as follows:
middleman (4.3.5) middleman-cli (4.3.5) middleman-core(4.3.5)
but when I enter middleman -v I get
Unknown switches "-v"
If I enter middleman --version I get
Unknown switches "--version" Did you mean? "--verbose"
Steps to reproduce the problem (from a clean middleman installation)
I installed rbenv and then ruby 2.6.3 (set to global default)
then I ran gem install ruby-dev
and then gem install middleman
then i entered middleman -v to check that the installation was successful but I got back
unknown switches "--version"
Additional information
which middleman returns home/.rbenv/shims/middleman
which ruby returns home/.rbenv/shims/ruby
I'm running ruby version 2.6.3 by default on Ubuntu 18.04

Ruby version: 2.6.3 (whith rbenv)
Middleman version: 4.3.5
OS version: Not OS but Ubuntu 18.04

The command is middleman version, no hyphens.

Thanks so much! Glad there was no real error!


perf: update civil servant profile and exists by identity

performance improvement for profile screen
updating civil servant profile
replacing 'get identity' with 'exists by identity'

No longer needed. Replaced by successive PRs.


Previews get cropped

I haven’t used ComfyUI in a while, but since I’ve updated Bleh (and ComfyUI), I’m getting square previews filled up with black to compensate the aspect ratio mismatch with what would have been a normal (Blegh-less) preview:

In this example, I’m keen on seeing if there are any tiny people moving at the bottom of the image, but it gets cropped. A few months ago, I used to get uncropped previews without black padding; the node would be super tall as a result, but that was okay. Is there anything in the settings I can add/change to recover this behaviour? Here are the contents of my blehconfig.yaml:
betterTaesdPreviews:
    enabled: true
    max_size: 768
    max_batch: 2
    max_batch_cols: 2
    throttle_secs: 1
    maxed_batch_step_mode: true
    skip_upscale_layers: -2

thanks for the report! i must have messed something up, it's not an issue with your settings: no cropping is ever intended. i won't have a chance to work on it today but hopefully tomorrow.
if you need a quick fix and you only care about the preview function you could try reverting to https://github.com/blepping/ComfyUI-bleh/commit/810cfd13f044420283603e0de9d074a8c36cd5b7 temporarily (the commit just before the one that most likely broke it).

Amazing, thank you so much! Yes of course, no rush at all 🤗

@UnaiM i just pushed a change that should fix this. was a dumb issue where i had width/height swapped, however it only triggered when using batches and non-square aspect ratios together.
please update to the latest version and give it another try.

Works beautifuly, thanks a bunch again! 🎉

no problem, thanks for the report and sorry about the inconvenience!


History graph plotting incorrect element

Following on from issues #135 I've updated to 0.75.1 and things have improved but it's still not right.
Ahead of the fix for 135 I had a real mess of graphs not working, now it seems more limited. I have the following in one of my views:
      - type: history-graph
        title: Temperature
        entities:
          - entity: sensor.aeotec_zw100_multisensor_6_temperature
            name: 'Temperature'
      - type: history-graph
        title: Humidity
        entities:
          - entity: sensor.aeotec_zw100_multisensor_6_relative_humidity
            name: 'Humidity'

When it's rendered by lovelace I end up with two graphs, both of which are showing humidity, not one for humidity and one for temperature.

Testing with 0.76.2 and the graphs are now working correctly.