Move to chef/fedora-21 Beaker node

I'm currently using a very un-official F21 Vagrant box for my F21 Beaker node. Eventually it'd be much better to move to an official-ish one, like chef/fedora-21. There are complicating factors, like the Chef box not being on Vagrantcloud yet. See details on #10.

This Beaker nodespec config file:
HOSTS:
  fedora-21:
    roles:
      - master
    platform: fedora-21-x86_64
    box: chef/fedora-21
    box_url: http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_fedora-21_chef-provisionerless.box
    hypervisor: vagrant

CONFIG:
  log_level: verbose
  type: foss

Run with bundle exec rake fedora_21 produces this Vagrantfile:
Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.hostname = 'fedora-21'
    v.vm.box = 'chef/fedora-21'
    v.vm.box_url = 'http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_fedora-21_chef-provisionerless.box'
    v.vm.box_check_update = 'true'
    v.vm.network :private_network, ip: "<IP_ADDRESS>", :netmask => "<IP_ADDRESS>", :mac => "0800276DE14F"
    v.vm.provider :virtualbox do |vb|
      vb.customize ['modifyvm', :id, '--memory', '1024']
    end
  end
end

With this output/failure:
[~/puppet-opendaylight]$ bundle exec rake fedora_21                                                                                13:29:34
RS_SET=fedora-21 bundle exec rake beaker
/usr/bin/ruby -I/home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib:/home/daniel/.gem/ruby/gems/rspec-support-3.1.2/lib /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/exe/rspec spec/acceptance --color
/home/daniel/.gem/ruby/gems/beaker-rspec-5.0.0/lib/beaker-rspec/helpers/serverspec.rb:12: warning: already initialized constant Module::VALID_OPTIONS_KEYS
/home/daniel/.gem/ruby/gems/specinfra-2.11.5/lib/specinfra/configuration.rb:4: warning: previous definition of VALID_OPTIONS_KEYS was here
Hypervisor for fedora-21 is vagrant
Beaker::Hypervisor, found some vagrant boxes to create
created Vagrantfile for VagrantHost fedora-21
Bringing machine 'fedora-21' up with 'virtualbox' provider...
==> fedora-21: Importing base box 'chef/fedora-21'...
==> fedora-21: Matching MAC address for NAT networking...
==> fedora-21: Setting the name of the VM: fedora-21yml_fedora-21_1422296997219_30643
==> fedora-21: Fixed port collision for 22 => 2222. Now on port 2201.
==> fedora-21: Clearing any previously set network interfaces...
==> fedora-21: Preparing network interfaces based on configuration...
    fedora-21: Adapter 1: nat
    fedora-21: Adapter 2: hostonly
==> fedora-21: Forwarding ports...
    fedora-21: 22 => 2201 (adapter 1)
==> fedora-21: Running 'pre-boot' VM customizations...
==> fedora-21: Booting VM...
==> fedora-21: Waiting for machine to boot. This may take a few minutes...
    fedora-21: SSH address: <IP_ADDRESS>:2201
    fedora-21: SSH username: vagrant
    fedora-21: SSH auth method: private key
    fedora-21: Warning: Connection timeout. Retrying...
==> fedora-21: Machine booted and ready!
==> fedora-21: Checking for guest additions in VM...
==> fedora-21: Setting hostname...
==> fedora-21: Configuring and enabling network interfaces...
/home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/hypervisor/vagrant.rb:166:in `block (2 levels) in vagrant_cmd': Failed to exec 'vagrant up' (RuntimeError)
	from /usr/share/ruby/open3.rb:217:in `popen_run'
	from /usr/share/ruby/open3.rb:99:in `popen3'
	from /home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/hypervisor/vagrant.rb:161:in `block in vagrant_cmd'
	from /home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/hypervisor/vagrant.rb:159:in `chdir'
	from /home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/hypervisor/vagrant.rb:159:in `vagrant_cmd'
	from /home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/hypervisor/vagrant.rb:121:in `provision'
	from /home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/hypervisor.rb:68:in `create'
	from /home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/network_manager.rb:48:in `block in provision'
	from /home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/network_manager.rb:47:in `each_key'
	from /home/daniel/.gem/ruby/gems/beaker-2.2.0/lib/beaker/network_manager.rb:47:in `provision'
	from /home/daniel/.gem/ruby/gems/beaker-rspec-5.0.0/lib/beaker-rspec/beaker_shim.rb:29:in `provision'
	from /home/daniel/.gem/ruby/gems/beaker-rspec-5.0.0/lib/beaker-rspec/spec_helper.rb:40:in `block in <top (required)>'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core.rb:81:in `configure'
	from /home/daniel/.gem/ruby/gems/beaker-rspec-5.0.0/lib/beaker-rspec/spec_helper.rb:5:in `<top (required)>'
	from /home/daniel/puppet-opendaylight/spec/spec_helper_acceptance.rb:1:in `require'
	from /home/daniel/puppet-opendaylight/spec/spec_helper_acceptance.rb:1:in `<top (required)>'
	from /home/daniel/puppet-opendaylight/spec/acceptance/class_spec.rb:1:in `require'
	from /home/daniel/puppet-opendaylight/spec/acceptance/class_spec.rb:1:in `<top (required)>'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core/configuration.rb:1105:in `load'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core/configuration.rb:1105:in `block in load_spec_files'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core/configuration.rb:1105:in `each'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core/configuration.rb:1105:in `load_spec_files'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:96:in `setup'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:84:in `run'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:69:in `run'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib/rspec/core/runner.rb:37:in `invoke'
	from /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/exe/rspec:4:in `<main>'
/usr/bin/ruby -I/home/daniel/.gem/ruby/gems/rspec-core-3.1.7/lib:/home/daniel/.gem/ruby/gems/rspec-support-3.1.2/lib /home/daniel/.gem/ruby/gems/rspec-core-3.1.7/exe/rspec spec/acceptance --color failed
rake aborted!
Command failed with status (1): [RS_SET=fedora-21 bundle exec rake beaker...]
/home/daniel/puppet-opendaylight/Rakefile:62:in `block in <top (required)>'
Tasks: TOP => fedora_21
(See full trace by running task with --trace)

Copied into a fresh dir and vagrant up'd fails with this:
[~/f21]$ rm -rf Vagrantfile
[~/f21]$ cp ~/puppet-opendaylight/.vagrant/beaker_vagrant_files/fedora-21.yml/Vagrantfile .
[~/f21]$ vagrant destroy -f
==> fedora-21: Forcing shutdown of VM...
==> fedora-21: Destroying VM and associated drives...
[~/f21]$ vagrant up
Bringing machine 'fedora-21' up with 'virtualbox' provider...
==> fedora-21: Importing base box 'chef/fedora-21'...
==> fedora-21: Matching MAC address for NAT networking...
==> fedora-21: Setting the name of the VM: f21_fedora-21_1422297273065_95692
==> fedora-21: Fixed port collision for 22 => 2222. Now on port 2200.
==> fedora-21: Clearing any previously set network interfaces...
==> fedora-21: Preparing network interfaces based on configuration...
    fedora-21: Adapter 1: nat
    fedora-21: Adapter 2: hostonly
==> fedora-21: Forwarding ports...
    fedora-21: 22 => 2200 (adapter 1)
==> fedora-21: Running 'pre-boot' VM customizations...
==> fedora-21: Booting VM...
==> fedora-21: Waiting for machine to boot. This may take a few minutes...
    fedora-21: SSH address: <IP_ADDRESS>:2200
    fedora-21: SSH username: vagrant
    fedora-21: SSH auth method: private key
    fedora-21: Warning: Connection timeout. Retrying...
==> fedora-21: Machine booted and ready!
==> fedora-21: Checking for guest additions in VM...
==> fedora-21: Setting hostname...
==> fedora-21: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device eth1 does not seem to be present, delaying initialization.

Stderr from the command:

Editing the Vagrantfile to remove the network config line fixes things:
[~/f21]$ vim Vagrantfile                                                                                13:35:33
[~/f21]$ cat Vagrantfile                                                                                13:36:43
Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.hostname = 'fedora-21'
    v.vm.box = 'chef/fedora-21'
    v.vm.box_url = 'http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_fedora-21_chef-provisionerless.box'
    v.vm.box_check_update = 'true'
    v.vm.provider :virtualbox do |vb|
      vb.customize ['modifyvm', :id, '--memory', '1024']
    end
  end
end
[~/f21]$ vagrant destroy -f                                                                                13:36:46
==> fedora-21: Forcing shutdown of VM...
==> fedora-21: Destroying VM and associated drives...
[~/f21]$ vagrant up                                                                                13:37:03
Bringing machine 'fedora-21' up with 'virtualbox' provider...
==> fedora-21: Importing base box 'chef/fedora-21'...
==> fedora-21: Matching MAC address for NAT networking...
==> fedora-21: Setting the name of the VM: f21_fedora-21_1422297431722_1818
==> fedora-21: Fixed port collision for 22 => 2222. Now on port 2200.
==> fedora-21: Clearing any previously set network interfaces...
==> fedora-21: Preparing network interfaces based on configuration...
    fedora-21: Adapter 1: nat
==> fedora-21: Forwarding ports...
    fedora-21: 22 => 2200 (adapter 1)
==> fedora-21: Running 'pre-boot' VM customizations...
==> fedora-21: Booting VM...
==> fedora-21: Waiting for machine to boot. This may take a few minutes...
    fedora-21: SSH address: <IP_ADDRESS>:2200
    fedora-21: SSH username: vagrant
    fedora-21: SSH auth method: private key
    fedora-21: Warning: Connection timeout. Retrying...
==> fedora-21: Machine booted and ready!
==> fedora-21: Checking for guest additions in VM...
==> fedora-21: Setting hostname...
==> fedora-21: Mounting shared folders...
    fedora-21: /vagrant => /home/daniel/f21

The F21 Vagrant box (without the network line, to make it work) shows this networking info:
[vagrant@fedora-21 ~]$ ip addr s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:c5:bf:a9 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s3
       valid_lft 85980sec preferred_lft 85980sec
    inet6 fe80::a00:27ff:fec5:bfa9/64 scope link
       valid_lft forever preferred_lft forever

Note that the ether interface is called enp0s3, not eth1, as expected/used by Vagrant:
ARPCHECK=no /sbin/ifup eth1 2> /dev/null

I had a same issue with a CentOS 7 box, updating Vagrant it self fixed the issue for me.

I had a same issue with a CentOS 7 box, updating Vagrant it self fixed the issue for me.

Thanks for the data point!
I upgraded from 1.6.5 to 1.7.2. Unfortunately, I'm seeing the same issue.
[~/f21]$ vagrant up
Bringing machine 'fedora-21' up with 'virtualbox' provider...
==> fedora-21: Importing base box 'chef/fedora-21'...
==> fedora-21: Matching MAC address for NAT networking...
==> fedora-21: Checking if box 'chef/fedora-21' is up to date...
==> fedora-21: Setting the name of the VM: f21_fedora-21_1422986249191_70235
==> fedora-21: Clearing any previously set network interfaces...
==> fedora-21: Preparing network interfaces based on configuration...
    fedora-21: Adapter 1: nat
    fedora-21: Adapter 2: hostonly
==> fedora-21: Forwarding ports...
    fedora-21: 22 => 2222 (adapter 1)
==> fedora-21: Running 'pre-boot' VM customizations...
==> fedora-21: Booting VM...
==> fedora-21: Waiting for machine to boot. This may take a few minutes...
    fedora-21: SSH address: <IP_ADDRESS>:2222
    fedora-21: SSH username: vagrant
    fedora-21: SSH auth method: private key
    fedora-21: Warning: Connection timeout. Retrying...
    fedora-21:
    fedora-21: Vagrant insecure key detected. Vagrant will automatically replace
    fedora-21: this with a newly generated keypair for better security.
    fedora-21:
    fedora-21: Inserting generated public key within guest...
    fedora-21: Removing insecure key from the guest if its present...
    fedora-21: Key inserted! Disconnecting and reconnecting using new SSH key...
==> fedora-21: Machine booted and ready!
==> fedora-21: Checking for guest additions in VM...
==> fedora-21: Setting hostname...
==> fedora-21: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device eth1 does not seem to be present, delaying initialization.

Stderr from the command:

[~/f21]$ vagrant --version
Vagrant 1.7.2
[~/f21]$ cat Vagrantfile                                                                                13:01:12
Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.hostname = 'fedora-21'
    v.vm.box = 'chef/fedora-21'
    v.vm.box_url = 'http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_fedora-21_chef-provisionerless.box'
    v.vm.box_check_update = 'true'
    v.vm.network :private_network, ip: "<IP_ADDRESS>", :netmask => "<IP_ADDRESS>", :mac => "080027FCA124"
    v.vm.provider :virtualbox do |vb|
      vb.customize ['modifyvm', :id, '--memory', '1024']
    end
  end
end

Again, remove the network-related line (created by Beaker) lets the box work:
[~/f21]$ vagrant destroy -f
==> fedora-21: Forcing shutdown of VM...
==> fedora-21: Destroying VM and associated drives...
[~/f21]$ cat Vagrantfile                                                                                13:02:29
Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.hostname = 'fedora-21'
    v.vm.box = 'chef/fedora-21'
    v.vm.box_url = 'http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_fedora-21_chef-provisionerless.box'
    v.vm.box_check_update = 'true'
    v.vm.provider :virtualbox do |vb|
      vb.customize ['modifyvm', :id, '--memory', '1024']
    end
  end
end
[~/f21]$ vagrant up
Bringing machine 'fedora-21' up with 'virtualbox' provider...
==> fedora-21: Importing base box 'chef/fedora-21'...
==> fedora-21: Matching MAC address for NAT networking...
==> fedora-21: Checking if box 'chef/fedora-21' is up to date...
==> fedora-21: Setting the name of the VM: f21_fedora-21_1422986563533_19865
==> fedora-21: Clearing any previously set network interfaces...
==> fedora-21: Preparing network interfaces based on configuration...
    fedora-21: Adapter 1: nat
==> fedora-21: Forwarding ports...
    fedora-21: 22 => 2222 (adapter 1)
==> fedora-21: Running 'pre-boot' VM customizations...
==> fedora-21: Booting VM...
==> fedora-21: Waiting for machine to boot. This may take a few minutes...
    fedora-21: SSH address: <IP_ADDRESS>:2222
    fedora-21: SSH username: vagrant
    fedora-21: SSH auth method: private key
    fedora-21: Warning: Connection timeout. Retrying...
    fedora-21:
    fedora-21: Vagrant insecure key detected. Vagrant will automatically replace
    fedora-21: this with a newly generated keypair for better security.
    fedora-21:
    fedora-21: Inserting generated public key within guest...
    fedora-21: Removing insecure key from the guest if its present...
    fedora-21: Key inserted! Disconnecting and reconnecting using new SSH key...
==> fedora-21: Machine booted and ready!
==> fedora-21: Checking for guest additions in VM...
==> fedora-21: Setting hostname...
==> fedora-21: Mounting shared folders...
    fedora-21: /vagrant => /home/daniel/f21

It looks like I need to figure out why Beaker is adding that network-related line, and potentially prevent it from doing so. Alternatively/additionally, need to check why Vagrant is using eth1 instead of an actual interface.

That's weird because i use beaker as well and worked fine when booting up my CentOS 7 box.. must admit i haven't tried F21.

That's weird because i use beaker as well and worked fine when booting up my CentOS 7 box.. must admit i haven't tried F21.

Yeah, CentOS 7 is working fine (also using Beaker). Also strange, the TFDuesing/Fedora-21 box doesn't show this issue.

Also strange, the TFDuesing/Fedora-21 box doesn't show this issue.

Note that TFDuesing/Fedora-21 isn't totally working, as described on #32.

Going to re-visit this as an attempt at fixing #63.

This is blocked. We can't get feedback about the success/failure of base-box change until #63 is unblocked and the F21 tests work.

I've update all the Vagrant boxes in the last few commits. This is now irrelevant.


Feature/cmp 951/policy selection: Enable the policy selection option to the "/agree" api

Why we create this PR?
Because of data compliance the user needs to be able to "sign" or "agree" the contract and be able to choose which policy he wants to accept.
In case there are more than one policy the application uses to take the first one. However that can cause problems when the Policies contain agreements that can not be fellfield by the user.
What we want to achieve with this PR?
We want to add a "policy selection" feature to the application so that the user can say which policy he wants to choose.
We want to allow the backend to handle more than one policy and more contracts for data soverenighty.
Allow the frontend to handle the new changes without loosing its functionality.
What is new?
Added

Added policyId parameter to "/agree" api.
Added mechanism to get a policy by id from a catalog contract
Added frontend logic to call the "/decline" and "/cancel" backend APIs
Added reload option in case of error
Added/fixed logging of the Digital Twin Registry Contracts and which policy was selected (Data Souverenighty improve)
Added util method to move files from one path to another
Added functionality to treat more than one policy and more than one contract, allowing user to decide
Added safety functionalities to make sure that the contract selected is correct.

Update

[BRAKING CHANGE] Renamed API "sign" to negotiate  "/agree"
Bumped Vite to version >=4.5.2
Updated the frontend to allow the "AutoSigning" of contracts.
Optimized temporary directory logging of the DTR negotiation

Issues Fixed

Fixed issue related to "sleepy" EDCs, allowing the backend to re-request the contract negotiation when the EDC does not respond.

PR Linked to:

Tickets

CMP-951

This is still missing

We should stop pre selecting contracts

Finally Working with Frontend and Backend with the Agree AutoSign


fix(types): fix type regression

Description
Fix regression in types introduced in https://github.com/chimurai/http-proxy-middleware/pull/603

fixes https://github.com/chimurai/http-proxy-middleware/issues/650
fixes https://github.com/chimurai/http-proxy-middleware/issues/692
fixes https://github.com/chimurai/http-proxy-middleware/pull/683

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Coverage remained the same at 98.86% when pulling 42cbc879bf4a01e6f581878579534eb8e843c9b3 on type-regression into aaa15a9874b81bcfdfe98cf222f5324a2e756eb0 on master.


Add location attributes to token object

adds the following location attributes to tokens:

ìndex: raw index in overall query string
line: line of token
col: index within line

additional tests coming

the line and col attributes could be used for more easily formatting in preserve modes, such as that one other PR regarding the placement of line comments that were previously inline - the raw start and end attributes wouldn't encode which line the comment was originally on

I suppose you're referring to this comment-placement issue: #365
Another whitespace-preserving related issue is #329
I think these both might be better solved by bringing back the precedingWhitespace field to tokens. Though, it might also be that storing line numbers is a better approach. However the current implementation won't work for that as we'd need to also store the line number of the token end (so we could compare it with next token start to determine if there are newlines in between).
Perhaps though it would be better to leave this line/column number part completely out for now. As we don't yet know if and how exactly we're going to use it - it's hard to design an API for a future unknown usage. I think it might be better to add this line/col-numbers support together with the feature that actually uses it. It's not really that complex of a functionality to bundle together with another feature, and perhaps we end up not using it at all.


Description of the crash

Description of the crash:
After installing and decompiling the ROMs, this message appears that the file was not found, and the game opens but the screen freezes.
Can you reproduce? If so please list the steps:

[ ] No, I cannot reproduce this crash
[ x] Yes, here are the steps to reproduce the crash:

Screenshots or videos:

Logs:
2 Ship 2 Harkinian.log
System Information:

OS: Windows 11
GFX Backend: DirectX
Game Version: 1.0 and 1.0.1
Rom Version: USA (1.0) and (USA GameCube)

Oops, misclicked!

This might be a result of having special characters in your file path

This might be a result of having special characters in your file path

I renamed the file, but the problem remains the same, I already downloaded the ROM from another different site, but the same error

In your file path is a folder named Fã Games e Ports, this is what I was meaning

@JPFOXPC Did this resolve your issue?

Closing for inactivity and likely caused by an issue with the file path.


Fixes #2160 Custom commands cannot detect installed packages

Fixes #2160 Custom commands cannot detect installed packages
Switches check to treat package specs as requirements rather than names.

👍


[Feature request] command line tool

Thanks for this! I'd love to automate the patching via a script - would it be possible to offer this as a CLI tool as well?

Absolutely. Will make the app have a command line interface with -c

Added in the newest commit!


Roadmap for version 3.0

We are planning to release Create React App version 3.0 soon. This will be a relatively small release but will include a number of necessary breaking changes.
Planned Features

Jest 24: https://github.com/facebook/create-react-app/pull/6278
Hooks ESLint plugin: https://github.com/facebook/create-react-app/pull/5997
TypeScript ESLint plugin https://github.com/facebook/create-react-app/pull/6513
Add browserslist support to @babel/preset-env: #6608
Absolute imports using jsconfig.json/tsconfig.json: https://github.com/facebook/create-react-app/pull/6656

Nice to Have Features

babel-plugin-optimize-react: https://github.com/facebook/create-react-app/pull/6219

Refer to the 3.0 Milestone to see exactly what is included in this release.
☢ How Can I Test This Now? ☢
We're happy you'd like to test the next version of react-scripts! Before getting into the details, we'd like to make you aware of a few things:

Features may be broken or not work as expected
There will be more breaking changes introduced before the final release ⚠
Documentation for new features is still sparse, so look through the pull requests for how they're expected to work

You can install the latest alpha version of react-scripts using one of the following commands:
$ # Create a new application
$ npx create-react-app@next --scripts-version=3.0.0-next.68 app-name
$ # Upgrade an existing application
$ yarn upgrade<EMAIL_ADDRESS>
Upgrading from 2.0 to 3.0

The browserslist config in your package.json is now used to control the output of your JavaScript files. You can use separate configuration for development and production. See https://github.com/facebook/create-react-app/blob/b0cbf2caa18ee8267855b14578ebc3dee826f552/packages/react-scripts/package.json#L83-L94 for a good starting point which gives a good development experience, especially when using language features such as async/await, but still provides high compatibility with many browsers in production

We now have linting support for TypeScript files! If you're using Visual Studio Code, see https://github.com/facebook/create-react-app/blob/master/docusaurus/docs/setting-up-your-editor.md#displaying-lint-output-in-the-editor for tips to get syntax highlighting from the ESLint extension in your .ts and .tsx files

We now support setting basePath in jsconfig.json. To configure basePath to point to the src directory create a jsconfig.json file in your project root:
{
  "compilerOptions": {
    "baseUrl": "src"
  }
}

Known Issues in 3.0 Alphas

File watching issue with Jest 24: #6646
Dynamic imports may not work in some cases: #6673

Please report any bugs you encounter or behavior you believe to be incorrect by creating a new issue. Have fun!

It would be nice if these two css features get included too:

Support scoped CSS in the same file (https://github.com/facebook/create-react-app/issues/5224)
CSS Modules with TypeScript: css-modules-typescript-loader (#5677)

@miraage I do not have any information to share about hot loader support.
@amshtemp Both of those issues are just proposals with no PR so it's very unlikely they will be included.
This is going to be a small release because we need to upgrade Jest due to the security issue with Jest 23. Once this is out we will immediately start work on version 4.0 so it's possible these features could be included then.

@amshtemp, as previously stated on #5677, we aren't planning to add anything like that for now as it's not a good DX. We do want a solution, we just need the right one.

Regrading the Typescript aliases (#6116) could the team give a little bit more details about how you would like this to work? There are still some questions/inconsistencies that I need some clarity on before I can continue working on the aliases part.

With hooks, it seems like class-based components will be used less and less. Should the default App component be function-based?

@cassiozen Yes, we will want to convert the template component to a function for v3. I'll add that to the list.

Excuse, if I am asking a question for which there is an obvious answer.
I am currently testing a web app built on React. I need to release 0.0.1 Beta in March 2019.  For maintainability, I used create-react-app to start my development.
From following this Roadmap and the PR's, version 3.0 will get an upgrade to Jest 24.1.
It also seems that version 3.0 will also use kleur@3 and the latest version of typescript@*.
This will resolve the deprecated package warning for kleur 2.0.2 and the missing peer dependency typescript for for ts-pnp1.0.1.
Is this correct?
Also, what is ETA on version 3.0 release?

love it!

Any thoughts about supporting webpackPrefetch?

Could we please load PostCSS config file from project directory if exists ?

Search available port to start webpack dev server if port is not specified in env

@iansu I saw that #6280 was moved to milestone 3 - does that mean that it will be part of this release?

We've just published the first alpha release of Create React App 3.0! This issue has been updated with instructions on testing the new release. If you encounter any problems please create a new issue instead of commenting here. Thanks!

Any thoughts about supporting webpackPrefetch?

@raRaRa please follow https://github.com/facebook/create-react-app/issues/3319 for updates on this. We're waiting on https://github.com/jantimon/html-webpack-plugin/pull/1014 to support this.

@raix That doesn't necessarily mean it will be included. We're considering it but we're also hoping to get 3.0 final out pretty quickly. Anything that isn't critical to the release and isn't ready will be pushed to a future version. That isn't a breaking change so it can be released at any time.

@iansu I've created a new PR (https://github.com/facebook/create-react-app/pull/6656) for baseUrl support in favor of #6116 so we can hopefully get that in with 3.0

@iansu why 3.0 add ability to configure PostCSS plugins ?

It seems that React @Types are not installed by using --typescript flag.
npx create-react-app@next --scripts-version=3.0.0-next.b0cbf2ca my-app --typescript

It seems that React @types are not installed by using --typescript flag.
npx create-react-app@next --scripts-version=3.0.0-next.b0cbf2ca my-app --typescript

@delasierra please file an issue. Let's keep this issue focused on the roadmap discussions.

Is v3.1.0 also available for testing?

Is v3.1.0 also available for testing?

3.0 is not released yet. We're still in the alpha stage until we feel confident to release an official 3.0. You can watch this post for updates for when we release new alpha versions.

Is v3.1.0 also available for testing?

I also got confused, there are some weird tags for v3.0.0 and v3.1.0 from sep 2018:

https://github.com/facebook/create-react-app/releases/tag/v3.0.0
https://github.com/facebook/create-react-app/releases/tag/v3.1.0

These versions are not published in npm. I guess someone should delete these above. :thinking:

Thanks for pointing that out @stefanmaric. I've cleaned it up.

CRA3 seems (so far) to have support for TypeScript v 3.4.1, for anyone wondering. CRA2 would break on new TS syntax (as const, readonly on array return types, …).

Any approximate timeline for the release of 3.0?

@TomasHubelbauer It's enough to update the indirect dependencies @babel/parser and @babel/plugin-transform-typescript to >= 7.4.0. This allows to use TS 3.4 in CRA 2.1.8.

I noticed a 2-3x slowdown when using TypeScript with Storybook v5. ~9s to ~30s.

updates on when this is going to be released?

I noticed a 2-3x slowdown when using TypeScript with Storybook v5. ~9s to ~30s.

I can confirm this. Compilation time has massively increased.

This transpilation performance is probably due to https://github.com/Microsoft/TypeScript/issues/30663#issuecomment-480437597 - It seems like with typescript@next it's already solved by that comment.

@voliva Even with typescript@next I'm still getting slow storybooks.

We've just published a new alpha release of Create React App 3.0! This issue has been updated with instructions on testing the new release. If you encounter any problems please create a new issue instead of commenting here.
Notable changes since the last alpha

Add support for baseUrl in jsconfig.json (#6656)
Update to core-js 3 (6769)
Upgrade to workbox-webpack-plugin v4 (#6725)
Enable futureEmitAssets setting in webpack config (#6696)
Fix terser causing build to hang on WSL (#6732)
Add PostCSS Normalize (#5810)

Refer to the 3.0 Milestone to see exactly what is included in this release.

@iansu
Not sure where the best place to open an issue is for an alpha build, but I noticed strange behavior after updating to latest alpha trying my test coverage script. Instead of running a coverage report it seems to be entering watch mode.
Here is a reproducible repo.
https://github.com/jkdowdle/creact-react-app-3.0.0-next.68-test-coverage-issue
Or
npx create-react-app@next --scripts-version=3.0.0-next.68 app-name && cd $_ && yarn test --coverage

@jkdowdle Please file this as a new issue so we can track it properly.

I read the “Nice to Have Features” for the 3.0 release, and was wondering whether these PR’s qualify:

Simple electron.js support #5498
Webworker support #3660, please see the updated version #5886

@jlarmstrongiv I don't think either of those features are going to make it into 3.0 but they're not breaking changes so we can include them in a 3.x release.

jsconfig.json is not a good idea. The filename implies that it is somehow a standard JS thing, when it is actually a CRA specific thing. tsconfig.json IS a TypeScript standard thing, since it comes from the sole vendor of the TypeScript language. However, JavaScript is a standard from multiple vendors, and publishing a config file that implies that it is related to that standard will cause confusion when people switch between tools.
I would suggest renaming this file to craconfig.json or something similar, or maybe adding a cra key in package.json for this config.

@devongovett it's a configuration file that is used by TypeScript's JavaScript language service. See http://code.visualstudio.com/docs/languages/jsconfig.
If you still have concerns maybe we could create a separate issue and discuss?

Yeah, Dan already corrected me on Twitter. Even so, I don’t think propagating that config file further outside of VSCode is a good idea for the same reasons.

The file isn't unique to VS Code. Code just happens to have TypeScript baked in 😛. But yeah let's fire up a separate issue to discuss if you prefer!

@devongovett, as @ianschmitz said we're definitely open for discussion in an issue :)
jsconfig.json is quite powerful, and users in IDEs making use of the TypeScript service will benefit from this.
As I understand it, your concern is more that you'd like to see a config file for create-react-app. This is something we've discussed a few times, and we're definitely look at ways to make create-react-app more flexible for different users.

Very excited about CRA 3.0 especially about the eslint-hooks plugin 🎉
Could we also add https://github.com/facebook/create-react-app/pull/6599 to 3.0? It feels like full lerna support is one of the most requested features of the community.

I don't really mind if there is or isn't a CRA specific config, I am mostly concerned with propagating a non-standard config masquerading as a standard one. It will cause confusion for people using other tools that support JavaScript but do not support this config file.

We can specifically mention that in the documentation. But a standard needs to start somewhere, vscode has a huge user base and these users will benefit from a configuration that keeps their IDE and build tool in sync with things like auto completion. Having our own configuration file will not do that.

Again, feel free to open an issue to discuss this further @devongovett.

What are the breaking changes?

Any chance we see https://github.com/facebook/create-react-app/pull/6280 making it in? Suppose its more under the nice to have. But PR seems ready and opens up a bit of possibilities when running multiple CRA apps locally

We just published Create React App 3.0! See the release notes for details about everything that's included and instructions on upgrading your apps.
Big thanks to everyone who contributed to this release and helped test the alphas! 🎉


Feature: Wrap file names in the grid layout

Requirements

File names should wrap up to three lines in the grid view layouts.
Selected items names should wrap as many lines as necessary to show the complete name

We'll need to handle Item Selection when using the new ItemsRepeater

We had to revert this feature because the implementation was causing this issue #10983

Reopening this issue as it's not yet fully resolved.

https://github.com/sbaeumlisberger/VirtualizingWrapPanel/tree/master/src
Do you guys think this might be helpful?

It's for WPF but it would be interesting to see if it could be ported. Fyi @marcelwgn

We could have the textblocks wrap on their own, however I don't think GridView would be able to deal with one textblock being larger than others.

Would this feature of GridView that was mentioned over a decade ago help?  https://supportcenter.devexpress.com/ticket/details/q346476/automatic-width-resizing-of-columns-in-gridcontrol-gridview
It seems there used to be a feature that would allow individual columns to size based on the width of the content of that column.

Would this feature of GridView that was mentioned over a decade ago help?

It would if it were supported in WinUI 3.


driver: update Exoscale info

update Exoscale info
Description

update URL to .com
update data centers locations
use the current logo

Status
ready
Checklist (tick everything that applies)

[ ] Code linting (required, can be done after the PR checks)
[x] Documentation
[ ] Tests
[ ] ICLA (required for bigger changes)

:top:

ta @ste-m

https://github.com/apache/libcloud/pull/1251


feat!: initial OIDC support implementation MONGOSH-1396

@alenakhineika This should be ready now, added the dependency with the changes from https://github.com/mongodb-js/oidc-plugin/pull/5 :+1:


Add liveness checking vars

Do we have a release version for this change? Not 1.2.0?

Rebased to release/1.3.0


freeze with "Paste FX chain to selected tracks"

Step 1 - insert a vst
Step 2 - give a parameter a MIDI link like 14-bit CC 03,35
step 3 - SWS/S&M: Copy FX from selected track
step 4 - select some other tracks
step 5 - SWS/S&M: Paste FX chain to selected tracks
at this point there's a good chance reaper becomes unresponsive.
Was recording video one of the times it happened
https://www.youtube.com/watch?v=y0Fs75J1u5s
Fullsize screenshot is here https://imgur.com/Z0HgTs7
you can see 1 additional plugin was inserted but it's not seen in the track fx chains, the UI is broken and the toolbar button for paste fx is stuck pressed. App is unresponsive.
link to forum post
https://forum.cockos.com/showpost.php?p=1992206&postcount=2443

Observation here:
It only seems to happen if a copied / pasted FX is currently floating.
I.e. when they are in the FX chain or invisible when copy / pasting I don't get a freeze here, can you confirm ?

can confirm. It's interesting that the behavior is different depending on how the fx is displayed.
If the fx is floating then new floating windows will be shown. If just the fx chain is showing, no new windows or fx chains will pop up after paste.
I also just tested and it's not limited to MIDI link, param mod with LFO + fx visible will freeze also.
No freezes without param mod or midi link.

These are exactly my findings.
I've been looking into the code and

If the fx is floating then new floating windows will be shown.
seems to be the culprit.

I've pushed a possible fix which seems to prevent the freeze but with the drawback that above would no longer apply, i.e. when copy / pasting floating FX they'd no longer appear floating but in the FX chain.
Actually I'm wondering if this behaviour could be improved on Reaper's side instead, because I'm not sure if it's strictly speaking 'a bug' on SWS side.
@devs
Opinions ?

I think not floating the fx, or fx-chain is a great solution.

Here's a build with the potential fix for testing if you want:
https://www.dropbox.com/s/helkd5g8tpbpbyz/reaper_sws_extension.zip?dl=1
(no installer, d'nd' into Application Support/REAPER/UserPlugins,overwriting existing one)

excellent, no problems with this version.

Thanks for testing.
The technical issue seems to be (from what I gather) that Reaper doesn't seem to like to get patched with a FX chain chunk that has a floating FX (FLOAT... line) and active MIDI link, param mod (<PROGRAMENV subchunk) which leads to the freeze.
I'll ask Justin if this could maybe be handled on Reaper's side (so we could keep the 'If the fx is floating then new floating windows will be shown.' feature, which I actually find nice.)

Thanks, fixing for REAPER 5.91pre2.

Thanks Justin.
So closing this one.


Add namespace & type to house experimental work

This PR addresses #209.
Hope the warning in the document summary is LOUD AND CLEAR. 📢
If this turns out to be a very bad idea, it can be scratched in any minor release.

I elect SelectAsync from #205 be the first candidate for experimentation.

A screenshot of how the warning appears in an IDE like Visual Studio Code:


dm-serializer-1.2.2 dependency update

@solnic Are there any possibilities of dm-serializer-1.2.2 dependencies be bumped up from json ~> 1.6 and json_pure ~> 1.6 to json ~> 2.0.3 and json_pure ~> 1.8.6 as there are conflicts when used with the latest Ruby environment?
Your assistance or advice would be greatly appreciated.
Many Thanks

I'm not working on datamapper anymore

Thanks for your response


Fixes stylecop warnings on FolderManager.cs

@david-poindexter @mitchelsellers I fixed the stylcop issues on the FolderManager.cs class for fixing the search issues after with a cleaner PR that does not have huge changes.

@bdukes I see multiple of your suggestions with the "commit suggestion" button greyed out, that means you did it?

I haven't committed any of those changes, but maybe @mitchelsellers' commit included some of them.

Ok, so I accepted the other suggestions, we just have to decide on the cast or adding an overload...

I just pushed a change to add overloads (and deprecate the old overloads).

Awesome @bdukes Love it.


[api-docs] Fix links in List_of_Commands.md

A new commit was made into the api-docs repo. This issue was created automatically. Need to review if we made any change to the library for this commit.
https://github.com/discord/discord-api-docs/commit/bbdce35574c1f5e6e98cb78bce9b36d8e2046070

This commit will not effect our lib's code. No changes required.


Create haverford.txt

The Haverford School for Boys

@OctopusProteins Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


autocomplete field present for some reason

Please describe the problem you are having in as much detail as possible:
I just migrated fully to discord-api-types in a package I am working on, and was wondering why RESTPostAPIChatInputApplicationCommandsJSONBody is typed as
export interface RESTPostAPIChatInputApplicationCommandsJSONBody extends RESTPostAPIBaseApplicationCommandsJSONBody {
    type?: ApplicationCommandType.ChatInput;
    /**
     * Whether this application command option should be autocompleted
     */
    autocomplete?: boolean;
    description: string;
}

it has autocomplete property and I am unsure as to why? Especially as when trying to look at the source in this repository it doesn't seem to have this, the above code block is taken from the installed version (running latest as of posting this)
Further details:

Runtime:

Node.js version: 16
deno version: n/a

Priority this issue should have – please be realistic and elaborate if possible:

Since autocomplete is typed as optional it's not a big deal (especially as it's internal code) but would like to get this typed properly asap of course

Looks like you're on an outdated version, this has since been corrected and removed afaik 👀

@vladfrangu that's odd :thinking: will double check this - might be a pnpm linking issue or something

yep my bad was a updating issue! thanks!


Cannot Find Symbol error with 1.0.1

Getting build errors as follows:
Severity	Code	Description	Project	File	Line	Suppression State
Error		....\WearProviderService.java:16: error: cannot find symbol
Severity	Code	Description	Project	File	Line	Suppression State
Error		import com.google.android.gms.wearable.CapabilityClient;
Getting the same error for all com.google.android.gms.wearable imports
Environment Setups
Windows 10
Cordova 8
Android 7
minimum sdk 23
target 26
All android packages for sdk 24 up are installed
Let me know if you have seen this or if you need more information from me. I can't share a ton on the app I am developing. Am under NDA.
error log.txt

Sorry for this question, but for some reason my sdk is not recognizing play services 11.8 update and when including in gradle build I get "could not resolve" errors. Have you seen this before?
I have searched every term and phrase I could think of to no avail.

Are you including the google maven repository?
https://developer.android.com/studio/build/dependencies.html#google-maven

Went head first down the rabbit hole with cleaning up compatibility issues, but I believe I got all the dependencies installed.
For others to reference if they are using Visual Studio, adding the maven url to dependencies worked.
It needs to be added to the android gradle.build file in platforms/android directory of their project folder
Since visual studio 2017 seems to be particular on it's gradle build versions you have to add the actual url and cannot use google() until VS upgrades it's gradle build tool dependency above 3.0.0.
Once this was added it did recognize and download play services 11.8.0
Now, more of a question than an issue, but how does this work with a wear 2 app? From what I understand you cannot add another app on the google play store with the same package name. Does this still depend on the wear app having the same name?

https://developer.android.com/training/wearables/apps/packaging.html
Multi apk releases

You are a wealth of knowledge good sir. A scholar and a gentleman. Thank you for being so helpful with this. Very much appreciated.
I am just getting started on this, so I hope you don't mind if I have further questions upcoming.

Hope all is well, I ran into another snag.
I had everything working, messages coming and going as expected, but had to do a full rebuild an am running into this error:
..\platforms\android\src\net\trentgardner\cordova\androidwear\WearProviderService.java:25: error: cannot find symbol  NodeApi.NodeListener,
Getting this for all NodeApi calls.
Play Services 11.8 installed
Google Support 25.+ installed (Without duplicate)
Gradle V: 3.0.0
MinSdk 25
Target Sdk 26
I'm just gonna include everything. Let me know if I have everything right..
errorlog.txt
buildgradle.txt
buildLog.txt


add test for ldap.go

Coverage decreased (-24.0%) to 26.659% when pulling 6b2bdeee885c9c7cb5bbb86f2ce8010db4b6325a on wemeya:ldap into 84509fbb3ece9d663b243e6e2006e744b60ea4f3 on vmware:configuration.

Coverage increased (+1.2%) to 51.836% when pulling 3be5eefa18346de1d74dccc4728b7d5fca35dd53 on wemeya:ldap into 84509fbb3ece9d663b243e6e2006e744b60ea4f3 on vmware:configuration.


Add pre-commit hooks for the repo

This introduces pre-commit configurations to run golangci before any commits occur.  Goal is to decrease the number of "fixup linter" type commit messages in the repo.
Fixes #83

@bbockelm I didn't see anyone assigned for review on this, but it would be a nice feature to have at this point. I tested and made a small change so that our parameters.yaml doesn't cause pre-commit to fail. I'm going to go ahead and merge, since we aren't enforcing anything yet and running pre-commit is still optional (but recommended). I'll also follow up with a PR that runs pre-commit against the whole repo so that everything gets tidied at least once.


BUG: Not able to run evaluation_db queries - value of Avatar cannot be set to null

Is there an existing issue for this?

[X] I have searched the existing issues

What went down?

Modify the queries wherever "avatar" coloumn is present - change it to a datatype that can have the above default value
Record

[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSOC'24 contributor
[ ] I want to work on this issue

i would love to work on this issue, could you please assign me this issue

Sure @Swapnilden


texinfo: 6.5 -> 6.7; fix cross compiling

Motivation for this change
The current derivation does not correctly cross-build when building in non-interactive mode.
Looking at the derivation, I don't see a reason for this distinction at all, hence this PR removes it.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Is there any way to get move this along? I know it's a bit last minute, but I'd really hate to miss the 20.09 release window with this ...

This broke darwin stdenv and is blocking staging-next (and branch-off thereby) https://nix-cache.s3.amazonaws.com/log/lnkwicmp12bcy9fhdillhkwh2xm9px8b-texinfo-6.7.drv

Proposed revert https://github.com/NixOS/nixpkgs/pull/97218.

Proposed revert #97218.

This PR contains two commits, the cross-compile fixes and the version bump, the later of which seems to introduce this regression.
I think it should be fairly easy to patch this forward, but if you want to revert, would it make sense to just revert the version bump (I'm mostly interested in the cross-compile fixes anyways).
Since I cannot test against Darwin, I'm afraid I cannot offer much active help in form of testing.

A fix is preferred, and otherwise its a revert. I was under the impression it was the interactive change, but did not give it much thought.
I can't test it myself either, like most of us...

Or postpone this whole PR after 20.09?  I can't see why it needs to be in there.  (I can't test Darwin either.)


Add configuration property to override GCS root url for VPC-SC

This is meant to be used to set GCS root URL to https://restricted.googleapis.com/ for VPC-SC
Because GCS does not accept Host: restricted.googleapis.com a HttpRequestInitializer is used to override the Host header on all requests.

Hi Jason,
May you test if this will work in VPCSC environment (possible test described here)

The GCS connector uses com.google.api.services.storage.Storage rather than com.google.cloud.storage.Storage found in the provided example so in this PR I've attempted to replicate StorageOptions.setHost and StorageOptions.setHeaderProvider with HttpRequestInitializer - I will set up a test VPC and post results of the curl test.

I tested with curl and it works - I will create a Java test too to verify Host header is being set correctly.

@jasonmar  re: curl; thats good news.
you can also just enable verbose logging w/ java.util.logging handler as well as within the request initializer.  her'es an example repo ive got w/ some samples

https://github.com/salrashid123/gcpsamples#logging-1

the bit w/ the exponentialbackoff shows how to add in request.setCurlLoggingEnabled just to test

Overriding host header could have unintended consequences and not recommended.
Preferred approach is to properly configure DNS instead for VPC SC access:
https://cloud.google.com/vpc/docs/configure-private-google-access-hybrid#configuring-dns


Write a GO program to find area of a cuboid

Description
Write a GO program to find area of a cuboid
Area of cuboid = 2 × (Length × Width + Length × Height + Width × Height)
Length : 2
Width  : 3
Height : 4

Area : 52

How to contribute

Save the solution in program/find_area_of_a_cuboid.go file
Add find_area_of_a_cuboid.go file in find-area-of-a-cuboid folder

!assign


Delete gallus.txt

The university has ceased operations.

@aaapl Thank you for the update! Pull request merged.


Performance of Barbs unusable with larger data

Describe the bug
The Barb renderer is unusable with larger data. It appears to be performing unnecessary calculations with every update, including scene navigation.
To Reproduce

Load PALM/cbl_KIT_ug00_dx10_masked_M01.000.0119.split.nc from glade
Enable the barb renderer
Try to change the viewpoint. It's impossible to do this interactively.

This one is so bad that I think it deserves a "High."

@stasj we skipped triaging this a couple of days ago. If you've wrapped up TODOs for the release could you please assess whether this is something reasonable to know off for 3.4? It's a pretty significant bug.


ci(workflow): tmp bring back publish job

This pull request introduces a new GitHub Actions workflow for publishing Python packages upon release and includes a minor version pinning adjustment in the pyproject.toml file.
New GitHub Actions workflow for publishing:

.github/workflows/publish.yml: Added a workflow to automate the publishing process on release. This includes steps for setting up Python, installing dependencies, building the package with Poetry, and publishing to PyPI.

Dependency version pinning:

pyproject.toml: Changed the version specification of twine from a range to an exact version ("4.0.2").

:tada: This PR is included in version 1.3.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update sbt to 1.3.5

Updates org.scala-sbt:sbt from 1.3.4 to 1.3.5.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: semver-patch

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #18   +/-   ##
=======================================
  Coverage   33.23%   33.23%
=======================================
  Files          37       37
  Lines        1682     1682
  Branches       53       53
=======================================
  Hits          559      559
  Misses       1123     1123

Continue to review full report at Codecov.

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


Allow redefining member type in extended interface (like "new" keyword in C#)

TypeScript Version:  2.5.2
Code
It would be great if extending Interface would allow to redefine member's types (similar to the "new" modifier in C#)
interface IHasData
{
   data:string|number;
}

interface IHasDataEx extends IHasData
{
   data:string|number|Function;
}

let x:IHasDataEx = {
  data:function(){
     return "Hallo world";
  }
}

Expected behavior:
Successful compilation and ability to do IHasDataEx.data = function(){...}
Actual behavior:
Compilation error:
Interface 'IHasDataEx' incorrectly extends interface 'IHasData'.
  Types of property 'data' are incompatible.
    Type 'Function' is not assignable to type 'string | number'.
      Type 'Function' is not assignable to type 'number'.

Ugly workaround:
interface IHasData
{
   data:string|number;
}

interface _IHasDataEx extends IHasData
{
   data:any;
}

interface IHasDataEx extends _IHasDataEx
{
   data:string|number|Function;
}

let x:IHasDataEx = {
  data:function(){          //OK
     return "Hallo world";
  }
}

x.data = "Hallo world" ;  //OK
x.data = 123;   //OK
x.data = new Promise(...)  //Compilation should fail, because data is not string|number|function

That wouldn't be sound though.
interface IHasData
{
   data:string|number;
}

interface IHasDataEx extends IHasData
{
   data:string|number|Function;
}

function f(x: IHasData) {
    if (typeof x.data !== "string") {
        // This is safe to use as a number, right?
        useAsNumber(x.data);
    }
}
const x: IHasDataEx = { data() {} };
f(x); // IHasDataEx extends IHasData, so safe to call `f` on one, right?

@andy-ms,  Not sure how it helps. Function "f" must accept IHasDataEx, because internally it checks if data is of type Function (or some other type defined in IHasDataEx).

Function "f" must accept IHasDataEx, because internally it checks if data is of type Function (or some other type defined in IHasDataEx).

The problem is not in the function you're defining here to parse the data; the problem is in any other function in the entire codebase that takes IHasData, and will now have unexpected results/consequences once the IHasDataEx interface is introduced.

Perhaps the following alternative might be of use:
   data: string|number;
}

interface IHasData2 {
   data: Function;
}

function f(x: IHasData | IHasData2) {
    if (typeof x.data !== "string") {
        // Error -- x.data might be a Function
        console.log(5 + x.data);
    }
}
const x = { data() {} };
f(x); // IHasDataEx extends IHasData, so safe to call `f` on one, right?

hmm yeah that makes sense

If your subtype can't be used in a location where the supertype is expected, maybe you shouldn't be using extends at all, and use a union instead as in @zspitz's post, which will force you to handle both possible cases.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


🐛 [firebase auth] FirebaseAuthException ([firebase_auth/invalid-credential] Invalid access_token, error code 43)

FirebaseAuthException ([firebase_auth/invalid-credential] Invalid access_token, error code 43)

@harryandroiddev
When you open an issue, please try to use new issue template and fill out requested details so that we'll have enough info to work with.
Just posting the single line error isn't helpful. I'll close it for now as there's not enough details to properly address the issue. You may file new issue using template.


crdclient: support Apply operations

RE: #44165. In general we probably want SSA instead of Patch.

https://github.com/kubernetes-sigs/controller-runtime/issues/1669
oh...

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Archive diff result file repro_diff.out

Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

run tests

Failed jdk20 pipeline but the log gives no clarity as to why :-(

Failed job https://ci.adoptium.net/job/build-scripts-pr-tester/job/build-test/job/jobs/job/jdk20u/job/jdk20u-windows-x64-temurin/12/console
Error message
19:11:32  Creating support/modules_libs/java.security.jgss/sspi_bridge.dll from 1 file(s)
19:11:55  Creating support/modules_libs/java.security.jgss/w2k_lsa_auth.dll from 2 file(s)
19:17:35  Creating support/modules_cmds/java.security.jgss/kinit.exe from 1 file(s)
19:17:35  Creating support/modules_cmds/java.security.jgss/klist.exe from 1 file(s)
19:17:51  Creating support/modules_cmds/java.security.jgss/ktab.exe from 1 file(s)
19:19:53  Cancelling nested steps due to timeout
19:19:53  Sending interrupt signal to process
19:20:13  After 20s process did not stop
[Pipeline] }
[Pipeline] // timeout
[Pipeline] echo
19:20:13  Setting GitHub Checks Status:
[Pipeline] echo
19:20:13  REPO URL: https://github.com/adoptium/ci-jenkins-pipelines.git
[Pipeline] echo
19:20:13  COMMIT SHA: f937f8137e48cfbe91f21fc5ec51a17d6b5ae1c7
[Pipeline] echo
19:20:13  STATE: FAILED
[Pipeline] echo
19:20:13  MESSAGE: Build FAILED
[Pipeline] echo
19:20:13  JOB NAME: jdk20u-windows-x64-temurin

windows build failures. Not related with this PR.


username and client_id is case sensitive？

when use mysql to store acl information, emqx is not case sensitive about client_id and username fileds;

Yes, it is indeed indistinguishable.

thank you for confirming this,there are many strange things happened before,that confused me a lot, is thiere any plan to make it case sensiive?

Sorry @aijingaiyi these fields are case-sensitive, I misunderstood.


August Lock Plug-in Error

Describe Your Problem
Hello, I am trying to an August WiFi lock via Homebridge, and have installed your August Plugin and after trying various Node.js versions (14.18.0 suggested didn't work but the Homebridge Logs stated than I needed 14.20.1 which got me closer. Now I have one remaining Error message:
Relevant log output
[August] Discover Devices: TypeError: Cannot convert undefined or null to object

Config for homebridge-august
{
    "name": "August",
    "credentials": {
        "augustId"<EMAIL_ADDRESS>        "password": "***@*********",
        "validateCode": "******",
        "notice": "Keep your tokens a secret!"
    },
    "platform": "August"
}

Screenshots
No response
Device & Model
August WiFi Lock
Node.js Version
v14.20.1
NPM Version
V6.14.17
Homebridge Version
v1.5.1
Homebridge August Plugin Version
v1.0.5
Homebridge Config UI X Plugin Version
No response
Operating System
macOS Ventura

@evantobin @Geebs11, Can you try the latest beta:

Click here to find out how to install Beta

v1.1.0 has been release which should resolve this.

I’m still having this issue


Vulnerability roundup 92: qt-3.3.8: 1 advisory [5.3]

search, files

[ ] CVE-2020-17507 CVSSv3=5.3 (nixos-20.03, nixos-unstable)

Scanned versions: nixos-20.03: 925ae0dee63; nixos-unstable: c59ea8b8a0e.

See also: #90955


[clapack] Fix linux build

Fix for https://github.com/Microsoft/vcpkg/issues/5368

@kafeg, thanks for contributing to vcpkg!
Here is fail triplet(x64-windows-static) and regression(openblas) with your PR.
Log:
Processing x64-windows-static                   757 vs 767
    blaze                                                        Skip vs Fail
     ceres                                                       Skip vs Pass
     clapack                                                     Skip vs Pass
     dlib                                                        Skip vs Pass
     ensmallen                                                   Skip vs Pass
     g2o                                                         Skip vs Pass
     geogram                                                     Skip vs Pass
     mlpack                                                      Skip vs Pass
     openblas                      **regression**                Fail vs Pass
     openmvg                                                     Skip vs Pass
     sophus                                                      Skip vs Fail
     suitesparse                                                 Skip vs Pass

@seanwarren, could you also update CONTROL revision in https://github.com/Microsoft/vcpkg/blob/master/ports/clapack/CONTROL and
https://github.com/Microsoft/vcpkg/blob/master/ports/openblas/CONTROL?
More information in https://github.com/Microsoft/vcpkg/blob/master/docs/maintainers/control-files.md

@PhoebeHui - this isn't my PR so I don't have write access (I just made a code review suggestion earlier). I think @kafeg will need to update the control file.
Cheers

It is failing due to a post-build validation:
DLLs should not be present in a static build, but the following DLLs were found:

    C:/vsts/_work/1/s/packages/openblas_x64-windows-static/bin/openblas.dll
    C:/vsts/_work/1/s/packages/openblas_x64-windows-static/debug/bin/openblas.dll

There should be no bin\ directory in a static build, but ...\packages\openblas_x64-windows-static\bin is present.
There should be no debug\bin\ directory in a static build, but ...\packages\openblas_x64-windows-static\debug\bin is present.
If the creation of bin\ and/or debug\bin\ cannot be disabled, use this in the portfile to remove them

    if(VCPKG_LIBRARY_LINKAGE STREQUAL static)
        file(REMOVE_RECURSE ${CURRENT_PACKAGES_DIR}/bin ${CURRENT_PACKAGES_DIR}/debug/bin)
    endif()

Found 2 error(s). Please correct the portfile:

Thanks for the contributions, everyone!


Summary class used in grouping specification overrides presentation.summary and provides malformed output

Describe the bug
I am unable to set a summary class using presentation.summary in queries where a different summary class is used to generate a hitlist inside a group() clause. When multiple summary classes are used in this way, the output for fields with highlighting enabled (either through bold: on or dynamic enabled) is also mangled.
To Reproduce
Steps to reproduce the behavior:

Reproduction Code here.
I am running the attached query along with presentation.summary=sample (N.B. the query has a different summary class basic in the group() clause.

Expected behavior
The responses use the basic summary class in the group level hit-list. However, the actual hits (outside the group) also use the basic summary class. I was expecting that the actual response would use the sample summary class.
Environment (please complete the following information):

OS: Linux
Infrastructure: Self-hosted
Versions 22.04
Container based on vespa:8.348.21 with cuda and vespa-onxxruntime packages installed

Vespa version

8.348.21

Updated with end-end reproduction code here: https://github.com/pratheekrebala/vespa-summary-class-repro

I also noticed this weird issue where when I hit the above bug, there's unexpected uni-code separator characters in my response.
Actual Behavior:

Expected Behavior:

Thanks for reporting. I have made a system test reproducing the error, without requiring docker or pyvespa.
It is indeed a bug. Will figure out root cause over after the weekend.

The override of the summary class was fixed in 8.359.13 with #31592.
What seemed like a well defined and easily reproducible bug turned out to be a clever one. It depended on iteration order. So first take at reproducing by extending existing tests failed. Once fixed we found that 1 of your system tests had a workaround for this issue, so it has been present for a very long time.
Expecting fix to available tomorrow, or the day after, if the build pipeline is in a good mood.
I have not yet verified the bolding/highlighting yet. Keeping it open until until then.

It was indeed 2 separate issues. The garbled output, skipped decoding of backend annotations, is fixed in #31630.
Testcase added in https://github.com/vespa-engine/system-test/pull/4076.
Build pipeline is currently not flowing smoothly. Will update once a release is ready.

Fixes has been merged and verified and will be part of 8.360.23 and on


Fix "complex_logic" issue in src/sqlfmt/line.py

Consider simplifying this complex logical expression.
https://codeclimate.com/github/tconbeer/sqlfmt/src/sqlfmt/line.py#issue_61f46a9f597a09000100003d

fixed in #108


Download all the data in the experiment scripts

Merged 128e020 into master, which downloads the (new) census zip file automatically.


(chore): Explicit declaration of source(bucket name) of suggested manifests

Relates to https://github.com/ScoopInstaller/Scoop/issues/5131

[x] I have read the Contributing Guide.

https://github.com/ScoopInstaller/Versions/commit/1f6e09255aa99984bcc67492a5565fc9f194dd4c, https://github.com/ScoopInstaller/Versions/commit/d6a12037002a597016f5fee1ffa8ca216c45fd86, https://github.com/ScoopInstaller/Versions/commit/9b10ddaf15ab65af581f74b003b63558d98121e6, https://github.com/ScoopInstaller/Versions/commit/4ab86c901ca72910332835048d33c9b4f10bfdd1, https://github.com/ScoopInstaller/Versions/commit/8b108ae6502968900d75270dd9e6a0d4c6efd978, https://github.com/ScoopInstaller/Versions/commit/6e26f21c3be6cadc97c93672c655a2befeaa0c5c, https://github.com/ScoopInstaller/Versions/commit/fcb48931c6aac35bf3d7af3de5d56e88c90ad41b, https://github.com/ScoopInstaller/Versions/commit/3a4291c8de1fe1809e9545ea65d93aa9d6daffe8, https://github.com/ScoopInstaller/Versions/commit/4de0a3cbac621ce6efced5214696840d6fe24c3c, https://github.com/ScoopInstaller/Versions/commit/144e00398272bd67f61b36848be32ce0b91c23d6, https://github.com/ScoopInstaller/Versions/commit/0cda6bd0e57085cc0a80a478f2555e2930e9ac3c, https://github.com/ScoopInstaller/Versions/commit/f5eb74be20fa0ccd8734dc51ff55bb1fcf667cff, https://github.com/ScoopInstaller/Versions/commit/f882d7b624211bb2245de64f7167a794ee419ff1, https://github.com/ScoopInstaller/Versions/commit/36c51681da7602b3237e52f961dfe27ada08ee19, https://github.com/ScoopInstaller/Versions/commit/c9ccf8c6965773c483020143ab7fc87464d445ec, https://github.com/ScoopInstaller/Versions/commit/7442f07a579c0e9d486a2a1a6a0446c5449dbe78, https://github.com/ScoopInstaller/Versions/commit/ec96d0f6b15a039ba7a49351e0ad37ee7f78dc00, https://github.com/ScoopInstaller/Versions/commit/ec96d0f6b15a039ba7a49351e0ad37ee7f78dc00, https://github.com/ScoopInstaller/Versions/commit/c5c02bb504809f4e76499c404eee6d1daf95d14f


[WFCORE-1706]: Deploying with force an unmanaged deployment makes it managed

Fixing how the CLI create the replace deployment operation to take unmanaged deployment into account.
Jira: https://issues.jboss.org/browse/WFCORE-1706

@aloubyansky or @jfdenise please approve

The changes look good to merge. Thanks, @ehsavoie
I just checked, unless I missed it somehow, we don't seem to have CLI tests for unmanaged deployments (neither in core nor in full). @jfdenise could you please look into that? Thanks.


Move aya and related crates to a github organization

I think it's time to move aya to an organization. Ideally I'd also move bpf-linker and my WIP rustc fork there to keep everything in one place.
What name should we use? I created github.com/ebpf-rs a while ago, but I'm not so sure about the name anymore. Suggestions welcome!

I started playing a game of word association with Rust,  e(Bee)PF and Aya and have a couple of ideas

ayaka-rs: Ayaka can mean colourful flower... which would attract bees!
aristaeus: A minor Greek god who kept bees
devorah-rs: Hebrew word for bee
thriae or thriai: A bee maiden from Greek mythology
beekeep-rs
lutjanus: Genus of fish. Lutjanus aya, was apparently believed to be a type of Red Snapper. And these fish eat crabs. Poor ferris.

ebpf-rs is nice and functional, but why not just keeping Aya for the org itself?

I suspect because https://github.com/aya is (unfortunately) alreadty taken.
So aya-rs or some other derivative would be needed.

oops, i didn't check, my bad :D

bee-rs? who doesn't like 🍻

I'm leaning towards aya-rs. I don't love it but it's simple and it doesn't introduce new names, which I think may be confusing. Unless anyone hates it I'm going to move things over this weekend.


Custom Template

It is possible to overwrite our default cookie policy law text with a custom template. Just put your favorite html content between the component like in the following example:

<cookie-law position="top">   This website contains cookie.   Read more </cookie-law>
For me this one don't work!!!
I add to axactly the same code and when i change the text it return always "By continuing to browse the site, you're agreeing to our use of cookies.".
How can i resolve ?

@VanDxtr , the live demo project is using the custom template feature and it's working.
Please have a look at the live project available here.
I'm going to close this ticket as I cannot reproduce the bug.
If the problem persists, please reopen this issue and include your package.json file.

Are you serious? it does not even work in the online demo version. in the picture does not seem to me that the text changes with what I put....

@VanDxtr, you're perfectly right, I'm sorry. I'll have a look at this ASAP.
Thanks for the feedback.

so did you fix this bug?

@andreasonny83

no sorry, is not fixed yet.
I reopened the issue. Anyway, pull requests are always more than welcome, considering I don't have enough time to dedicate to this project.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Persist auth on RN

Describe your changes
Add auth persistence on RN.
Issue ticket number and link
issue on mobile :(

Closing as the issue only effects Expo, so we will just eat the dev time loss


add the multilingual ability to the template.

multilingual feature has been implemented using i18n

New branch has been pushed to the repo named "multilingual"


Find Unicode Gurmukhi instead of ASCII in Search query in Lines Model

Currently, is-ascii is being used to detect if the search query is in the GurbaniAkhar format.
However, GurbaniAkhar has letters that are outside the 128char ASCII range. This triggers the search to convert Unicode -> GurbaniAkhar, which messes up the search query (esp in Full Word searches).
Solutions:

Find a library that can check if a character is in a unicode block

Build own solution in gurmukhi-utils to check if string has Unicode Gurmukhi

Try Anµd

Probably have to opt into 2) or write a function that checks if it's in the ANSI range. we need to define this range since it's not a fixed spec at all, and no modules I could find implement it

@Harjot1Singh I remember my exact issue.
I was searching Anµid, but since there is a micro sign (µ), it triggered Unicode->ASCII, which converted it into Anµdi

Another solution is to check if the text is in Gurmukhi Unicode block without implementing into gurmukhi-utils
Python has unicodedata, where one can use a function such as:
def isGurmukhi(sample):
    return unicodedata.name(sample[0]).startswith("GURMUKHI")

Not sure if a similar library is available in JS.

Or check if the hex code point is between 0A00..0A7F

No issue with M or µ
I'm pretty sure this is related to sihari bug
See here:

and

@bhajneet https://github.com/ShabadOS/database/issues/1333#issuecomment-564873169

const isGurumukhi = text => ( text.charCodeAt( 0 ) >= 2560 && text.charCodeAt( 0 ) <= 2687)


Fails on non-application JARs

Possibly I'm doing something wrong. But, consider the case of https://madoka.brage.info/baughn/prometheus-integration-0.2.1.jar
This is a plugin for Minecraft servers, not an application. It could, nevertheless, benefit from a good shaking; a glance at it with jdeps shows that it contains a lot of Jetty components that are never used.
However, no matter what I pass for -k, the Dependencies output shows up empty and the resulting .jar contains no class files.

Sorry for the late response.
I just ran it on the jar you mentioned and it seems to do the job for me.
For instance passing -k net as an argument retains the net.* package and it's dependencies in kotlin.*.

I experienced the same problem running, for example, on guava-28.0-jre.jar (no class files in shrunk
jar despite valid -k switch specified).
As I discovered, that's because the undocumented output format for jdeps' -verbose:class switch has changed since JDK 9 (possibly because of the introduction of JPMS module references).
My fix https://github.com/Deconimus/JarShrink/pull/9 solves this issue.


[GSSoC'24]⚠ [URGENT]⚠ Join Official Cogniguard Discord Channel

Description
Join the Cogniguard project discord channel, where you can connect with mentor and PA and discuss about the projects.
You can join by navigating in #self-roles channel
Just find @Congiguard and click on @ 10
SS

Happy Contribution

⚠[URGENT]⚠ Reminder for GSSoC 24' Contributors Please join our CogniGuard Project #general GSSoC'24 Discord channel:
Here you can discuss your queries and doubts with your mentors.
See #109 issues section.

⚠[URGENT]⚠ Reminder for GSSoC 24' Contributors Please join our CogniGuard Project #general GSSoC'24 Discord channel:
Here you can discuss your queries and doubts with your mentors.
See #109 issues section.

⚠[URGENT]⚠ Reminder for Closing of Contribution period for GSSoC 24'
Finish your work and raise the PRs ASAP to get your points.
Thanks💗 for your valuable Contributions!

GSSoC 24 has been completed Finally'
It was a great experience working with you all
Thanks💗 for your valuable contributions!
PA nomination has been started, Do fill out the forms soon. Share your experiences and let's connect on socials


fix: removes injected config in DcpDefaultServicesExtension

What this PR changes/adds
Removes injected config in DcpDefaultServicesExtension:

edc.iam.sts.publickey.id
edc.iam.sts.privatekey.alias

The read of those config has been switched back when creating the defaultTokenService.
Why it does that
It fixes the case where the SecureTokenService is not default (provided by another extension)
but the above properties are still required
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

We could but it's actually required if you use the embedded sts

yes, exactly, so in the provider method for the embedded STS (createDefaultTokenService) we could check if the values are null and log a warning or throw an exception. the provider method won't get invoked if the embedded STS isn't used

I was thinking more on the autodoc that we would print that's not required, while it is

I was thinking more on the autodoc that we would print that's not required, while it is

yes, but if we make it required, it'll come up as "required" in autodoc, even if it isn't required, so same problem. I guess we could implement a "delegated requirement", which would be the cleanest solution.
for now, I'd keep using the config injection (required=false), and explain in the description that it is indeed required if the default service is used, etc.


Examples link not working in main documentation

It appears the Examples hyperlink to show examples of using AMPL is not functioning. It does not lead to anywhere it appears.

Resolved AMPL/atomsci/ddm/examples/tutorials/README.md in PR https://github.com/ATOMScience-org/AMPL/pull/214.
Thanks.


Device removal has been triggered

I'm using MiniEngine core library to create a DX12 experiment for my master thesis.
In my experiment, I am creating a StructuredBuffer for the dynamic lights in the scene. I want to be able to resize the StructuredBuffer if I add lights (or reduce the StructuredBuffer if I remove lights). In my implementation of the IGameApp class, I override the Update function and in that function the light buffer will be resized if the user presses a key on the keyboard. To resize the buffer, the GpuBuffer::Create method is used on the StructuredBuffer object. The StructuredBuffer object is not destroyed, only the Create method is used to recreate the buffer resource.
The problem is that (seemingly randomly but is more easily reproducible with larger buffers) a device removal is triggered:
D3D12: Removing Device.
D3D12 ERROR: ID3D12Device::RemoveDevice: Device removal has been triggered for the following reason (DXGI_ERROR_DEVICE_HUNG: The Device took an unreasonable amount of time to execute its commands, or the hardware crashed/hung. As a result, the TDR (Timeout Detection and Recovery) mechanism has been triggered. The current Device Context was executing commands when the hang occurred. The application may want to respawn and fallback to less aggressive use of the display hardware). [ EXECUTION ERROR #232: DEVICE_REMOVAL_PROCESS_AT_FAULT]
D3D12: **BREAK** enabled for the previous message, which was: [ ERROR EXECUTION #232: DEVICE_REMOVAL_PROCESS_AT_FAULT ]

The error occurs 100% in the CommandListManager::ExecuteCommandList method when the m_CommandQueue->ExecuteCommandLists gets invoked.
The size of the StructuredBuffer doesn't seem to matter. It happens if I only have 10 lights (1 KB) or 32 lights (3.5 KB) but the more lights, the more likely the timeout will occur. I suspect it's a threading issue as device removal should not occur when uploading only a few KB to a structured buffer.
Any ideas?

I have forwarded your question to James.  He will post a response for you.

Are you waiting for the GPU to be done using the resource before recreating it?  The StructuredBuffer and other GpuResource objects hold a reference counted pointer (ComPtr) to the underlying D3D object.  When Create() is called, the existing pointer is released, and D3D is free to reclaim the memory immediately.  Before destroying or recreating resources, it's a good idea to idle the GPU, which will flush all pending command lists and make sure that the resource's memory will no longer be needed by the GPU.  There is a method you can call to do this:  g_CommandManager.IdleGPU().  There is an example of calling this whenever the native resolution is changed before resizing all of the render targets.  I hope that fixes your problem.  Best of luck!

@stanard Thanks for the tip! I figured it was something like this. I was thinking of double-buffering the StructuredBuffer in my application so that I don't destroy the one being used by the GPU before it is finished with it but I like your solution better.
To fix this, I added g_CommandManager.IdleGPU() call in the GpuBuffer::Create method just before the resource is created on line 40. This fixed the issue with minimal overhead.
Is this the best solution? Or is there a better way? For example, something similar to the double-buffer solution but delay the deletion of the resource until after the GPU frame is complete? Maybe enqueue the resource on a "delete queue" which is processed at the end of the frame? Maybe the delete queue is processed in a separate thread so the main thread does not need to stall while it waits for the GPU to finish with the resource?

Idling the GPU is a non-optimal solution.  You don't want to do it every frame, and if you are creating multiple resources, you wouldn't need to keep idling the GPU.  It's really only in the Destroy() method that you need the idle, as new resources won't have been referenced by the GPU yet.
I think a better solution for you is to use the LinearAllocator class.  If the size of your buffer varies each frame, you can allocate just what you need each time.  You could have a variable number of buffers of different sizes each frame, and the memory gets recycled automatically.  But they are associated with a command context so that they can query whether its fence has transpired and it's safe to reclaim.  (Note that all you need is a GPU virtual pointer to read and write a StructuredBuffer so long as you use root entries to bind it to your shader.)
If you are only changing the size once per frame, a double or triple buffer scheme would possibly be the simplest approach to guarantee safety.


Pairing Ledger device with Daedalus on a windows machine fails

I'm having a very annoying problem when trying to pair a Ledger device with Daedalus on Windows machine and Ledger is not recognized. The screen is still asking user to connect and unlock the wallet. I have to connect and unlock the Ledger device before running Daedalus. This seems like an known issue but nothing is raised here so I decided to create the issue here
https://iohk.zendesk.com/hc/en-us/articles/360038741393

Hello. Yes, this is a known issue and it is currently in our ToDo list to be fixed.
Thank you for your report!

PR created here but some conflicts need resolving

@minh0722 Hello. Could you please advise if issue is still reproducible for you using latest Mainnet release. Thank you in advance!

The issue is now not reproducible in 4.10.0. Thanks for the great work!


Flashy background highlighting.

Patrick doesn't like my color scheme though.

I love it!

How about this?  I think this represents the spirit of Lean very well:

What about a gradient based on the sidebar color (green for theorems, etc)? Or is that too matchy? I guess we have blue links for everything so it could clash.
I'm fine with the current one btw, Patrick and I must have different tastes.

I like the fact that there is highlighting. I'm too much of a barbarian to have an opinion on the details.


Fix dead StackExchange.Redis link

I did not create an issue, since this is a very small (but annoying) issue,

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@TomGroeneboer Thank you for fixing this! Your change will go live within the next 24 hours.


[Feature][Metric]seatunnel spark job metric

seatunnel spark job metric

@yuangjiang Hi, thanks for your patch, please solve the conflicts first.


Yarp drops UDP packets greater then 1472 bytes (windows)

This was a trick issue to solve.
We noticed that on few windows 10 machines of ours, large udp packets (such as images) were dropped by yarp. For example:
yarp read /test
yarp connect /grabber /test udp

was failing without any error message, while the two following examples:
yarp read /test
yarp connect /grabber /test tcp

yarp read /test
yarp connect /icubSim/head/state:o udp

were both working fine.
We also noticed the following facts:

Wireshark was able to see the UDP packets on the receiver side.
Windows 10 was not able to perform large pings, i.e.
ping -l 1473 <IP_ADDRESS>
Interesting, ping packets smaller or equal to 1472 bytes (which is the default fragmentation limit) were handled correctly by the system.

We found was the problem was due to HYPER-V, which was installed on these particular windows machines.
Uninstalling HYPER-V was enough to solve the issue.
Currently it's not clear neither which network parameters are modified by HYPER-V, nor if it is possible to configure the system in a way which allows to use HYPER-V and, at the same time, handle large fragmented packets.

@apaikan @pattacini @drdanz


[Feature]: Add test cases for POST /v1/embeddings

Contact Details(optional)
No response
What feature are you requesting?
_

fixed by #35


15 define and store a generic example with nested structure

@francescalb @jesper-friis @sygout
Adding example generic cuds object with a nested structure. I would love to get your insight into how this could be improved but could be good to have this to aim towards in testing the conversion.

Sorry! I made this ready-for -review by mistake. And I do not see where to revert that :(

@cmclscourtney , With the updated implementation we can now convert between the files you have provided. Please let us know if this is sufficient for your needs.


Dashboard: Waiting for your review block: updates

'Waiting for your review' block which has been updated in #937 needs to be updated in terms of submissions being displayed in this block and the subsequent pre-filtered submission list (accessible via the 'show all' link at bottom of table if more than 5 submissions).
After discussion with OTF, agreed approach for an initial release is that both waiting for your review and the corresponding 'show all' page should show all submissions where I am assigned as reviewer, in any status other than a final determined state, i.e. all states other than accepted, dismissed, concept accepted and invite to proposal (?status=screening&status=more-information-required&status=internal-review&status=ready-for-discussion&status=ready-for-determination&status=advisory-council-review&status=ready-for-preliminary-determination&status=proposal-received&status=ready-for-final-determination&reviewers=9&query=). The waiting for review block on dashboard should show the first 5 in the list as it does now, linking to all submissions prefiltered in the same way.
@frjo we were hoping you could undertake this work.
@todd-dembrey please add any further dev notes needed and then assign to @frjo ?
cc @danblah

Is this what you had in mind https://github.com/OpenTechFund/opentech.fund/pull/1030 ?
I bassed the pr on sprint-3-winter-2019 branch.

@todd-dembrey can you check this pls?

@gibbsmaya this is now on dev.

The dashboard "to review" list is now populated from all statuses in which you can give a review.
If you have more than 5 submissions in this list then the there is a link to the table pre-filtered with the same statuses as the dashboard.

Hi @todd-dembrey
There are a few submissions that are not appearing in this block when I would expect them to. Acting as Lindsay, I should see the  following submissions in my 'waiting for review' block
https://dev-apply.opentech.fund/apply/submissions/21/
https://dev-apply.opentech.fund/apply/submissions/10/
https://dev-apply.opentech.fund/apply/submissions/9/
Please can you take a look?
Thanks,
Maya

Hi Maya, this is now correct on staging.
21 - should not appear - she has submitted a review
9 - correctly appears
10 - Now appears

Thanks @todd-dembrey.
Waiting for your review block now working as expected but there is an issue with the 'all submissions' page that this links too. Again, see Lindsay's dashboard and go through to https://dev-apply.opentech.fund/apply/submissions/all/?reviewers=9screening&status=more-information-required&status=internal-review&status=ready-for-discussion&status=ready-for-determination&status=advisory-council-review&status=ready-for-preliminary-determination&status=invited-for-proposal&status=proposal-received&status=ready-for-final-determination
It may be a typo in the code?

I have fixed this issue, the link is now correct of dev.

Done. Note that the show all page also includes submissions where the review has already been undertaken because we currently don't have a filter to differentiate between 'already reviewed' or 'yet to review'. This is a little confusing, but as things get determined they will disappear from this list. A filter could be added in future to deal with this.

Hi @fourthletter, @danblah, @arduina,
This is now ready for testing. This work is updating the logic of the submissions that appear in the 'Waiting for your review' block on dashboard. @fourthletter probably easiest for you to test this since there were submissions missing from your dashboard.
Please test this against the initial issue description and check this matches. Please also see my comment above (previous comment) about the pre-filtered 'all submissions' page that the user will land on.
Thanks,
Maya

I completed this test and all features are functional and visible. Thanks! 💥

Thanks @fourthletter. Assigning to @todd-dembrey ready for live deployment.


chore: use terraform 1.6 instead of 1.1

Ref. https://github.com/jenkins-infra/helpdesk/issues/3823

No changes. Your infrastructure matches the configuration. (plan)
No WARNING (plan)
WARNING (build output) : Warning: Redundant ignore_changes element can be ignored for now
Terraform 1.6.6 is used thanks to the annotation. Will remove the annotation once pipeline-library's PR will be merged


Rename filePath to filePattern in NumbedShardedFile

R: @reuvenlax @tgroh

LGTM pending green Jenkins

Coverage decreased (-0.006%) to 70.018% when pulling 797f4f8bc3bf69e630753f0219e220a8a9d80e2d on kennknowles:fileGlob into 22ff898a363715a99b19a75de416d62915681a23 on apache:master.


Remove the old implementation of dashboard

What would you like to be added:
Remove the old implementation code of dashboard, clean the code.
Why is this needed:
The old implementation of dashboard will make the contributor confused, the new implementaion is more powerful than the old one, which have clear roadmap, so we prepare to remove the old code before the release the brand new version of karmada dashboard.

/assign

/assign jayesh9747

@jayesh9747

/unassign

@warjiang  can you assign  me this issue?

/assign

/assign @jayesh9747


Change details panel to element inspector

[x] @joeferner
[x] @diegogrz
[x] @mwizeman @sfeng88
[ ] @joeybrk372 @rygim @jharwig @EvanOxfeld

Testing Instructions: Verify that details panel now says element inspector
Points of Regression: Anywhere that would reference the details panel
CHANGELOG
Added:
Changed:
Documentation: Rename details panel to element inspector
Deprecated:
Removed:
Fixed:
Security:

Can you undo all changes to files under docs/extension-points/front-end? Those files are all completely changed in another PR

@jharwig done.

@EvanOxfeld done


400 ms delay from tap to focus on searchbar input on iOS

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X] 3.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Add an ion-searchbar component to a page, when tapping the searchbar observe a noticeable delay until the component has focus. If adding performance.now() in searchbar.js tap and focus events, the delay is measured to about 400 ms between the two.
A similar issue was once reported but closed as performance was "pretty fast": https://github.com/ionic-team/ionic/issues/6028 - 400 ms is indeed not fast and far from the close-to-native experience expected.
Expected behavior:
Instant focus like a normal input field.
Steps to reproduce:
Reproduced with a template as follows:
<ion-header>

  <ion-navbar>
    <ion-title>Searchbar test</ion-title>
  </ion-navbar>

  <ion-toolbar>
    <ion-searchbar [(ngModel)]="searchTerm"
                   [formControl]="searchControl"
                   </ion-searchbar>
  </ion-toolbar>

</ion-header>

Related code:
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (/Users/ug/git/ionic-starter-nabto/node_modules)

    @ionic/cli-plugin-cordova       : 1.6.1
    @ionic/cli-plugin-ionic-angular : 1.4.1
    @ionic/cli-utils                : 1.7.0
    ionic (Ionic CLI)               : 3.7.0

global packages:

    Cordova CLI : 7.0.1

local packages:

    @ionic/app-scripts : 2.1.3
    Cordova Platforms  : ios 4.4.0
    Ionic Framework    : ionic-angular 3.6.0

System:

    Android SDK Tools : 26.0.2
    Node              : v7.9.0
    OS                : macOS Sierra
    Xcode             : Xcode 8.3.3 Build version 8E3004b
    ios-deploy        : 1.9.1
    ios-sim           : 6.0.0
    npm               : 4.2.0

You are on iOS, so are you using WKWebView?

No, just the default platform as per ionic info above.

So try integrating WKWebView:
https://github.com/ionic-team/cordova-plugin-wkwebview-engine

I had a bit of struggle with our own plugin that does not seem to work out of the box with wkwebview, but if reproducing in a simple example with just the searchbar, the delay dropped from 400 ms to less than 40 ms (I verified the 400 ms to still be there with the clean example and no wkwebview). Amazing! Thanks for the suggestion. Should we keep the ticket open as it might be interesting to understand why the regular webview performs as observed?

Glad it helped you. I hope that next major ionic version will ship with wk, I'll ask the devs.
No, ticket should be closed, as the issue was solved.


Remote inspection fixes backported to rhel7-1.7

Signed-off-by: Michal Minar<EMAIL_ADDRESS>

merged


Curators want to rename datasets in a collection without uploading again

See original slack conversation with @pablo-gar.
Currently, if a dataset name (title in Presentation metadata) in A Collection needs to be updated for clarity, the curator must edit the dataset and then upload+replace the original in the collection.
A pending case is Update tabula muris brain datasets to better reflect differences .
Updating a dataset name would currently require writing the change to the database, the dataset, and the CXG.

UX Design
Dropdown Menu
Edit Dialog

Backend Estimate: 1-2 weeks x 1 engineer + 1 reviewer

Create endpoint in the Curation API for patching dataset metadata such as dataset title (i.e. PATCH /curation/v1/collections/<collection_id>/datasets/<dataset_id>, symmetrical to the existing PATCH /curation/v1/collections/<collection_id> for updating collection metadata)
- Must have auth gating this action to owners / super curators
- Must be dataset in an open revision
The endpoint will validate inputs and trigger the existing batch job in dataset_metadata_update.py by calling the existingtrigger_dataset_artifact_update in the business layer. This will kickoff metadata updates to all artifacts, and update dataset status accordingly.
Request schema should be valid uns dict fields available for update via endpoint, mapped to their new desired value (i.e. {"title": "new title"}). Confirm with curators what fields should be included, and confirm whether further updates to the batch job are required to accommodate those.
- "title" must be supported. Others to consider: Citation, default_embedding, batch_condition, adding a new field
- Note: supporting changes to any keys that incur CLI validation will require updating the batch job to run that validation check

Requires (small) tech spec + agreement with produce before merging code