[BUG] Hyperf\Coroutine\Exception\ChannelClosedException" not found

Execute the command and paste the result below.
Warning: Class "Hyperf\Coroutine\Exception\ChannelClosedException" not found in /home/asdf/DEV/swoole/hyperf-skeleton/vendor/hyperf/utils/src/Exception/ChannelClosedException.php on line 14
swoole bin/hyperf.php start
Warning: Class "Hyperf\Coroutine\Exception\ChannelClosedException" not found in /home/asdf/DEV/swoole/hyperf-skeleton/vendor/hyperf/utils/src/Exception/ChannelClosedException.php on line 14

Fatal error: Uncaught Error: Class "Hyperf\Coroutine\Exception\ChannelClosedException" not found in /home/asdf/DEV/swoole/hyperf-skeleton/vendor/hyperf/utils/src/Exception/ChannelClosedException.php:20
Stack trace:
#0 /home/asdf/DEV/swoole/hyperf-skeleton/vendor/composer/ClassLoader.php(571): include()
#1 /home/asdf/DEV/swoole/hyperf-skeleton/vendor/composer/ClassLoader.php(428): Composer\Autoload\includeFile('/home/asdf/DEV/...')
#2 [internal function]: Composer\Autoload\ClassLoader->loadClass('Hyperf\\Utils\\Ex...')
#3 /home/asdf/DEV/swoole/hyperf-skeleton/vendor/hyperf/utils/src/Functions.php(541): class_exists('Hyperf\\Utils\\Ex...')
#4 /home/asdf/DEV/swoole/hyperf-skeleton/vendor/composer/autoload_real.php(55): require('/home/asdf/DEV/...')
#5 /home/asdf/DEV/swoole/hyperf-skeleton/vendor/composer/autoload_real.php(38): composerRequire9f630ee78015a795c6afb270c0c614e2('bbeb7603826cb92...', '/home/asdf/DEV/...')
#6 /home/asdf/DEV/swoole/hyperf-skeleton/vendor/autoload.php(12): ComposerAutoloaderInit9f630ee78015a795c6afb270c0c614e2::getLoader()
#7 /home/asdf/DEV/swoole/hyperf-skeleton/bin/hyperf.php(20): require('/home/asdf/DEV/...')
#8 {main}
  thrown in /home/asdf/DEV/swoole/hyperf-skeleton/vendor/hyperf/utils/src/Exception/ChannelClosedException.php on line 20

按照官网教程安装 使用swool-cli 5.0

参考这个 issue 中的解决办法：https://github.com/hyperf/hyperf/issues/5677#issuecomment-1524500969


ci: Ensure docker-compose build works.

Currently, we don't check that the Dockerfiles are valid, or build in CI. We'd like to do this, so that you can't merge code that breaks docker.

#12 [control 7/8] RUN go build -v ./cmd/control
#12 0.461 internal/assets/assets.go:8:12: pattern satellite-amd64-linux: no matching files found
failed to solve: process "/bin/sh -c go build -v ./cmd/control" did not complete successfully: exit code: 1
#12 ERROR: process "/bin/sh -c go build -v ./cmd/control" did not complete successfully: exit code: 1
------
 > [control 7/8] RUN go build -v ./cmd/control:
0.461 internal/assets/assets.go:8:12: pattern satellite-amd64-linux: no matching files found
------
Error: Process completed with exit code 17.

This found the error we ran into yesterday lol

Closes #90


Still can't select the embedding model by docker

          Still can't select the embedding model by docker

version 1.3.2
Originally posted by @edisonzf2020 in https://github.com/ItzCrazyKns/Perplexica/issues/63#issuecomment-2094833397

Be sure to clear your DevTools > Application > Local Storage -- Right-click and delete all of them. Then hard refresh.
Mac: cmd + shft + R
Windows: ctrl + shft + R

Hi, the version 1.3.3 will fix your issue. If you face the error again feel free to re-open this issue.

Hi, on my linux with v1.8.1, everything is fine except Embedding Model which is still blocked on 'invalid provider', how can i do to overcome the problem please

Be sure to clear your DevTools > Application > Local Storage -- Right-click and delete all of them. Then hard refresh.
Mac: cmd + shft + R Windows: ctrl + shft + R
^^

Thanks ! so much


No 'params' in state.router

It is my understanding that these properties should be present in state.router. However, the only property that's there is location.
This is what my <Route /> looks like:
<Route path='/whatevs/:param' component={WhatevsView} />

And my view:
const mapStateToProps = function (state) {
  return {
    router: state.router
  }
}

// ...

console.log(this.props.router) // Object {location: Object}

I'm not sure if it's an issue with the starter kit, an issue with react-router, or I'm simply doing something wrong. Any help would be greatly appreciated.

So react-router-redux only stores the location object (refer to the last bullet point in these release notes: https://github.com/rackt/react-router-redux/blob/master/CHANGELOG.md#202). I'm sure there's a good reason for this, but I'm just not aware of it.
That aside, if you need to access the params from @connect, mapStateToProps receives a second argument ownProps, which are the props passed to the component. In this case, since this component lives at a route you have full access to ownProps.params.<whatever>. Hope that helps.

Thanks for the help, @davezuko, and for, y'know, making my life infinitely easier to begin with. This does solve my problem.

:tada:


For now, I need to generate sbom of python or go project with this sbom-tool, how should I do?

I have made node related project successfully, as the dependent packages all have package.json, but it seems that it does not auto detection when it is python related project.

I have found the way this sbom-tool supporting other programing languages, they are in the VERBOSE log. Please feel free to put them on obvious position, like README.md. Thanks


fix(graphql-auth-transformer): fix key condition expression

Description of changes

fix key condition expression in auth transformer

Issue #, if available

Fixes: https://github.com/aws-amplify/amplify-cli/issues/9222

Description of how you validated changes

manually following reproduction steps with mock
manually executing tests with the ticket schema and appsync
yarn test passes
added unit tests

Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I see this PR was already approved. Is there an ETA when the fix will be merged/released? Thanks


1st Deployment fine - ongoing deployments fail - No such file or directory - /usr/bin/env git fetch origin

I am able to deploy the first time as expected. When I attempt to redeploy I get the following errors.
The second time I get this error.
Error "Errno::ENOENT: No such file or directory - /usr/bin/env git fetch origin"
Testing Connection from local to bitbucket
bigre@DESKTOP-30G9FPT MINGW64 /d/WinNMP/WWW/DM-M2/tools/cap (master)
$ ssh -T<EMAIL_ADDRESS>logged in as bigredkacy

You can use git or hg to connect to Bitbucket. Shell access is disabled

Testing on the SSH Server to Bitbucket
`www-dev@917436-staging:03:10 PM:/var/www/dev$ ssh -T<EMAIL_ADDRESS>logged in as bigredkacy
You can use git or hg to connect to Bitbucket. Shell access is disabled
Here is the output of the deploy
`
bigre@DESKTOP-30G9FPT MINGW64 /d/WinNMP/WWW/DM-M2/tools/cap (master)
$ bundle exec cap dev deploy
00:00 deploy:pending:log
      01 git fetch origin
#<Thread:0x00000000066c0768@C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/runners/parallel.rb:10 run> terminated with exception (report_on_exception is true):
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/runners/parallel.rb:15:in `rescue in block (2 levels) in execute': Exception while executing as<EMAIL_ADDRESS>No such file or directory - /usr/bin/env git fetch origin (SSHKit::Runner::ExecuteError)
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/runners/parallel.rb:11:in `block (2 levels) in execute'
C:/Ruby26-x64/lib/ruby/2.6.0/open3.rb:213:in `spawn': No such file or directory - /usr/bin/env git fetch origin (Errno::ENOENT)
        from C:/Ruby26-x64/lib/ruby/2.6.0/open3.rb:213:in `popen_run'
        from C:/Ruby26-x64/lib/ruby/2.6.0/open3.rb:101:in `popen3'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/local.rb:44:in `execute_command'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/abstract.rb:148:in `block in create_command_and_execute'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/abstract.rb:148:in `tap'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/abstract.rb:148:in `create_command_and_execute'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/abstract.rb:80:in `execute'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-magento2-0.9.4/lib/capistrano/tasks/pending.rake:48:in `block (6 levels) in <top (required)>'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/abstract.rb:31:in `instance_exec'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/abstract.rb:31:in `run'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/dsl.rb:76:in `run_locally'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-magento2-0.9.4/lib/capistrano/tasks/pending.rake:47:in `block (5 levels) in <top (required)>'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-magento2-0.9.4/lib/capistrano/magento2/pending.rb:18:in `ensure_revision'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-magento2-0.9.4/lib/capistrano/tasks/pending.rake:45:in `block (4 levels) in <top (required)>'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/abstract.rb:31:in `instance_exec'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/abstract.rb:31:in `run'
        from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/runners/parallel.rb:12:in `block (2 levels) in execute'
(Backtrace restricted to imported tasks)
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as<EMAIL_ADDRESS>No such file or directory - /usr/bin/env git fetch origin

Caused by:
Errno::ENOENT: No such file or directory - /usr/bin/env git fetch origin

Tasks: TOP => deploy:check => deploy:pending:warn => deploy:pending:log
(See full trace by running task with --trace)
The deploy has failed with an error: Exception while executing as<EMAIL_ADDRESS>No such file or directory - /usr/bin/env git fetch origin

** DEPLOY FAILED
** Refer to log/capistrano.log for details. Here are the last 20 lines:

 DEBUG [80b4b91b] Command: [ -f /var/www/delmar-m2/current/REVISION ]

 DEBUG [80b4b91b] Finished in 1.621 seconds with exit status 0 (successful).

  INFO [f4352135] Running /usr/bin/env git fetch origin as bigre@localhost

 DEBUG [f4352135] Command: /usr/bin/env git fetch origin

  INFO ---------------------------------------------------------------------------

  INFO START 2020-10-01 13:03:42 -0700 cap dev deploy

  INFO ---------------------------------------------------------------------------

 DEBUG [0cb253fa] Running [ -f /var/www/delmar-m2/current/REVISION ] as<EMAIL_ADDRESS>
 DEBUG [0cb253fa] Command: [ -f /var/www/delmar-m2/current/REVISION ]

 DEBUG [0cb253fa] Finished in 1.512 seconds with exit status 0 (successful).

  INFO [2572cef3] Running /usr/bin/env git fetch origin as bigre@localhost

 DEBUG [2572cef3] Command: /usr/bin/env git fetch origin

  INFO ---------------------------------------------------------------------------

  INFO START 2020-10-01 13:04:24 -0700 cap dev deploy

  INFO ---------------------------------------------------------------------------

 DEBUG [b4ef174c] Running [ -f /var/www/delmar-m2/current/REVISION ] as<EMAIL_ADDRESS>
 DEBUG [b4ef174c] Command: [ -f /var/www/delmar-m2/current/REVISION ]

 DEBUG [b4ef174c] Finished in 1.675 seconds with exit status 0 (successful).

  INFO [3d7e6cc4] Running /usr/bin/env git fetch origin as bigre@localhost

 DEBUG [3d7e6cc4] Command: /usr/bin/env git fetch origin

What directory is not found?
Here is the directory of the Remote

SSH the command where it fails in the application/repo/ direction and returns ok

Hi @bigredkacy. I'm not sure what is going on but I see in the back trace that SSHKit local is being used. That seems very out of place. It looks like you intend to deploy to a remote host. Any idea why local is coming into play with your setup? Perhaps you have a capistrano plugin that is changing the standard behavior?
from C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/sshkit-1.21.0/lib/sshkit/backends/local.rb:44:in `execute_command'

If Capistrano tries to run /usr/bin/env git fetch origin locally, no surprise that will fail. You want to run that command on the remote host, not locally. /usr/bin/env probably doesn't even exist on a Windows PC (it looks like you are running Windows), hence the "No such file or directory" error.
I am not sure if you missed it in our GitHub issue template, but it is super helpful if you provide the cap <stage> doctor output. Capistrano is a general purpose tool and its behavior is completely different based on settings and plugins, so knowing those things makes it easier to troubleshoot.

Thank you for the quick reply and also for the doctor command. I am including that and my deploy.rb and dev.rb if that may help. No where is "local" referenced.
Here is the output. Please note it ends before it is finished @ the variable command, so I added --trace
bigre@DESKTOP-30G9FPT MINGW64 /x/var/www/Delmar/tools/cap (master)
$ cap dev doctor --trace
** Invoke dev (first_time)
** Execute dev
** Invoke load:defaults (first_time)
** Execute load:defaults
** Invoke doctor (first_time)
** Invoke doctor:environment (first_time)
** Execute doctor:environment
** Invoke doctor:gems (first_time)
** Execute doctor:gems
** Invoke doctor:variables (first_time)
** Execute doctor:variables
cap aborted!
NameError: uninitialized constant Capistrano::CLI
Did you mean?  CGI
config/deploy/dev.rb:3:in `block in <top (required)>'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/configuration/variables.rb:54:in `peek'
C:/Ruby26-x64/lib/ruby/2.6.0/delegate.rb:83:in `method_missing'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/doctor/variables_doctor.rb:57:in `block in inspect_all_values'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/doctor/variables_doctor.rb:53:in `each'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/doctor/variables_doctor.rb:53:in `each_with_object'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/doctor/variables_doctor.rb:53:in `inspect_all_values'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/doctor/variables_doctor.rb:28:in `call'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/tasks/doctor.rake:17:in `block (2 levels) in <top (required)>'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `block in execute'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `each'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `execute'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/airbrussh-1.4.0/lib/airbrussh/rake/context.rb:61:in `execute'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
C:/Ruby26-x64/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:243:in `block in invoke_prerequisites'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:241:in `each'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:241:in `invoke_prerequisites'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:218:in `block in invoke_with_call_chain'
C:/Ruby26-x64/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:188:in `invoke'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:160:in `invoke_task'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block (2 levels) in top_level'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `each'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block in top_level'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:125:in `run_with_threads'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:110:in `top_level'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:83:in `block in run'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:186:in `standard_exception_handling'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:80:in `run'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/lib/capistrano/application.rb:14:in `run'
C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/capistrano-3.14.1/bin/cap:3:in `<top (required)>'
C:/Ruby26-x64/bin/cap:23:in `load'
C:/Ruby26-x64/bin/cap:23:in `<main>'
Tasks: TOP => doctor => doctor:variables

Environment
    Ruby     ruby 2.6.4p104 (2019-08-28 revision 67798) [x64-mingw32]
    Rubygems 3.0.3
    Bundler  N/A
    Command  C:/Ruby26-x64/bin/cap dev doctor

Gems
    capistrano          3.14.1
    airbrussh           1.4.0
    rake                13.0.1
    sshkit              1.21.0
    net-ssh             6.1.0
    capistrano-magento2 0.9.4

Variables

dev.rb
# Target server connection info
server '<IP_ADDRESS>', user: 'www-dev', roles: %w{app web}
set(:user) { Capistrano::CLI.ui.ask "Username=> " }
set :deploy_to, '/var/www/delmar-m2'
set :branch, ENV['BRANCH'] || "master"
set :tmp_dir, '/home/www-dev/tmp2'

deploy.rb
# config valid for current version and patch releases of Capistrano
lock "~> 3.14.1"

set :application, "DMF-M2"
set :repo_url, 'git@bitbucket.org:bigredkacy/delmar.git'
set :user, "www-dev"

Capfile
# Load DSL and set up stages
require 'capistrano/setup'

# Load Magento deployment tasks
require 'capistrano/magento2/deploy'
require 'capistrano/magento2/pending'

# Load Git plugin
require "capistrano/scm/git"
install_plugin Capistrano::SCM::Git

# Load custom tasks from `lib/capistrano/tasks` if you have any defined
Dir.glob('lib/capistrano/tasks/*.rake').each { |r| import r }

OK it looks like this is a problem with the capistrano-magento2 gem. I took a look at its source code and as you can see it is trying to run the git command locally:
https://github.com/davidalger/capistrano-magento2/blob/3d32c7d654bd9221f67e20c27fc4e62503bdd73d/lib/capistrano/tasks/pending.rake#L47-L49
I suggest that you open an issue in the capistrano-magento2 repo. Hope that helps!
I'll close this issue since it is a third-party bug.


Evaluate performance of object detection pipeline

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
Evaluate performance of perception pipeline.
Purpose
Evaluate performance of perception pipeline to confirm if current perception has enough capability for BGus
Possible approaches
Find available open datasets for evaluation and do benchmark testing.
Possible datasets:

Waymo dataset https://github.com/waymo-research/waymo-open-dataset
KITTI dataset http://www.cvlibs.net/datasets/kitti/

Definition of done

[ ] plan data conversion for open datasets to feed into Autoware perception pipeline
[ ] Develop benchmark tools to test perception pipeline
[ ] Run tests on datasets and make results available in public. (e.g. in documentation)

In the Autoware.Auto, we have 2D and 3D detection benchmark tools for the KITTI dataset. We can test our 2D/3D detections by integrating these tools into Autoware.Universe.
In addition, I think, we need to evaluate the entire perception stack of Autoware.Universe from sensor output(Point Cloud/Camera Frame) to object tracking output, because all perception modules work together. Such as; deterministic and deep learning-based 3D bounding boxes are based merged or tracking results are merged with detected objects. For object tracking, the KITTI dataset has only 2D bounding box-based evaluation. For this reason, we are planning to implement Waymo dataset for 3D detection & tracking evaluation.

I shared high-level architecture for the planned perception benchmark pipeline. If you have any comments feel free to share them with us.

Limitations when benchmarking with the Waymo dataset:

We don't have PCD/Vector Map information from the Waymo dataset. The current perception pipeline can run with/or without PCD Map.
In our codebase, a cylindrical prism is used when assigning shapes to pedestrians, we need 3D bounding boxes for pedestrians when evaluating with the Waymo dataset.

Current situation:

I created a ROS interface that contains data conversion functionalities for the Waymo dataset.
I fed the data from the Waymo dataset to the lidar-only Autoware.Universe pipeline.

@kaancolak I'm wondering if using Waymo Open Dataset Toolkit for evaluation is a good idea. I understand that the best solution would be to make it possible to use the same metric calculation software for Waymo, Kitti ( + other open datasets), as well as with synthetic data generated in the simulators. In this case, as Autoware is based on ROS2, it would be perfect to have metric calculation based on ROS topics directly, optionally on rosbags (like we develop in this issue) What is your opinion ? I'm not really familiar with Waymo Open Dataset toolkit, so I might misunderstand something.

Thanks a lot for the explanation. Pipeline that you created is perfect for comparing Autoware results with others, as well as it will be very easy to just connect metric calculation node that is created in the task I mentioned directly to the same topics that you connect the "data converter" converting to the Waymo format. Look perfect to me and once we have proper metrics we will connect it with your code.

@WJaworskiRobotec Instead of working on the different benchmarking pipelines, I think we can extend the metric calculation node. It's a more generic evaluator that contains the entire stack(evaluator, planning, control, detection, etc.) that makes sense. I would like to implement the perception(2D/3D perception) part on your metric calculation nodes, base algorithm will be very similar to this tool but must be in the same code format as your nodes.

@kaancolak Sounds great. @djargot is currently working on the last node that we wanted to create as an example and it is related to perception (segmentation algorithm evaluation). Once it's done we will assign you as a reviewer, and you can continue with adding your nodes for 2D/3D Object Detection.

This PR waiting for review.

@kaancolak can you update the current status of this issue?

I have made some updates on the code base. Currently, it's waiting for review.

@kaancolak If you have any evaluation results, please


Can't open WSL2 distro - "The specified file is encrypted and the user does not have the ability to decrypt it"

Environment
Windows build number: 10.0.19041.0
Your Distribution version: Ubuntu 20.04
Whether the issue is on WSL 2 and/or WSL 1: WSL 2

Some other possibly relevant information:

I have Docker Desktop installed, and it's set to use the WSL 2 backend. I don't use it though, I couldn't get it to talk to my WSL2 systems properly so I'm running docker inside the guest OS instead.
my user account is not an administrator, though I have an administrator account on this computer. This is a security precaution.

Steps to reproduce
I'm not sure the exact steps to reproduce this. Now that I'm having the issue, all I need to do is (now for either of my two WSL2 distributions, but previously only one) try to open a WSL command line.
Things that might or might not be relevant:

This happened to one of my systems a few weeks ago, and I couldn't fix it so I gave up and installed another WSL distro. This is the second time it's happened.
Maybe it started when my computer ran out of battery and did not cleanly shut down?
For my first distro on which this occurred, maybe it started when I ran sudo ifconfig eth0 down in the guest OS? I was trying to debug this issue https://github.com/microsoft/WSL/issues/4246 which eventually one of the workarounds in that issue helped me with in the second WSL installation.

I've also tried downgrading to WSL 1 but I get the same error.
Expected behavior
I get access to my WSL VM
Actual behavior
PS C:\Users\Jakob> wsl
The specified file is encrypted and the user does not have the ability to decrypt it.

Here's the strace wsl output: https://gist.github.com/jakob223/a6f95c14cef7895af07b9d71b026ada6
And the detailed logs: detailed_logs.zip

Do you have any third-party security or antivirus software installed?
It appears that something is blocking access to C:\Windows\System32\lxss\LxssManagerProxyStub.dll link
onecore\vm\wsl\lxss\lxcmdlineshared\hcs.cpp(252)\lxssmanager.dll!00007FFD94D64A51: (caller: 00007FFD94D64783)
Exception(4) tid(187c) 80071772 The specified file is encrypted and the user does not have the ability to decrypt it.
    Msg:[(null)]

Yep, I'm running Sophos Endpoint Agent (or my employer is, anyway). Does that seem like a plausible culprit?
It doesn't list any events that look like blocking access to that DLL, but maybe it's not important enough to make the event list.

It's a possible culprit yes, but other causes should not be ruled out.

This was happening to me too - not sure if this will help you @jakob223, but I worked around the issue by finding the distro's Appx package under c:\Program Files\WindowsApps\
$ gci 'C:\Program Files\WindowsApps\' -Filter '*Canonical*'

    Directory: C:\Program Files\WindowsApps

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----l        25/07/2020     18:38                CanonicalGroupLimited.Ubuntu20.04onWindows_2004.2020.424.0_x64__79rhkp1fndgsc

Then copying everything in there into a separate directory on the root of your drive.
If you copy them using Windows Explorer, you'll probably get an error saying something like 'your organization doesn't allow copying this file here' for the AppxMetadata & Assets directories - I fixed this by creating directories with the same names inside the new directory at the root of my drive, and then copying the child files of AppxMetadata & Assets inside them both. It might prompt you saying that encryption isn't supported in the new directory, just click OK.
I think this is where the distro will run from, so make sure you don't delete it afterwards.

I had this issue and my fix was similar to @abagonhishead . I had to give myself permissions to the Program Files\WindowsApps folder and COPY (cutting did not work) to a folder in the root directory. After that I ran Kali.exe as administrator from the newly copied location.


fix: only add emoji once

Emoji is added during Agent.say() so no need to add it in methods that use .say().


Questions: How do you bring in third-party winmds?

Questions
The documentation states:

In this project you would also need to reference the C#/WinRT NuGet package and the project-specific .winmd files you want to project, whether through a NuGet package, project reference or direct reference

But doesn't explain what a "direct reference" is.
Q: What is a "direct reference"?
Q: How do I reference my external winmd?
I tried, to no avail:

adding a reference in my .csproj to a winmd via a None build action (e.g. <None Include="../my.winmd">)
dropping the winmd directly into the project directory hierarchy for automatic inclusion
manually specifying the file via CsWinRTInputs

Entering gibberish into CsWinRTInputs also yields no error, which is very confusing. And none of the logging facilities work either, so I must have missed something.)
Repro cases

Repro for no log output, not clear how to reference winmd: CsWinrtBringInWinmd.zip

Repro for bad CsWinRTInputs not generating errors: CsWinrtBadInputsRepro.zip

Additional information
.net5.0 project
Visual Studio 2019 16.8.5
Windows 10 19042
CsWinRT 1.1.2

Hi Rafael, I noticed in your first repro you have <OutputType>Exe</OutputType>, but to build a projection you need to use a class library project. There is a walkthrough here that demonstrates how to build a projection with a C# library project.
You should be able to reference the a winmd using the <None Include=.. or by browsing for the winmd file in the Reference Manager here.

CsWinRTIncludes is the property to use for specifying which namespaces to project and is required in your project file. The default is to not project any namespaces as documented here. You shouldn't need CsWinRTInputs.
@Scottj1s, is there anything you can add on CsWinRTInupts not generating errors?

@angelazhangmsft I think I misunderstood the project completely. I was focused strictly on replicating what .NET yanked out of the runtime and overlooked the auto-magic that occurred. Sounds like I need to do some of the legwork of building the projection myself and then consume that in a subsequent step. I'll try this now.
There's definitely room here for some improvements around error checking and documentation!


RelmApp API for using MessageBroker with the top-level Component

Hey! So as we discussed in Matrix room, I'm trying to add builder pattern to RelmApp to allow message broker to be attached to the top-level component.
I guess there's no much point to use proper builder pattern with RelmAppBuilder here versus adding modifier methods to RelmApp because it behaves like a builder itself: simply stores data until consumed when run. Ideally, I hoped it would allow it to use it like this:
RelmApp::new<Model>(app_id)
    .with_args(&some_args)
    .with_broker(&some_broker)
    .as_async(true)
    .run()

But there are a few issues here.
First, to store those optional fields RelmApp would need to be generic over component but also over args type, which for sync component only could look like this:
pub struct RelmApp<'broker, 'args, C: Component, S: AsRef<str>> {
    app: gtk::Application,
    broker: Option<&'broker MessageBroker<C>>,
    args: Option<&'args [S]>,
}

And when with_broker and with_args aren't used (and I assume this is most of the time), Rust would require to specify those generic types explicitly, which doesn't make much sense when those aren't used.
Second, it seems to be quite hard and probably unreasonable to make it properly generic over both sync and async components, and it looks easier to stick to separate run<C: Component>() and run_async<C: AsyncComponent>() methods. MessageBroker is implemented for sync only, but I assume it should be easy to add it to async too. It looks like MessageBroker doesn't use anything besides Input type from the Component it is generalized over, so maybe it can rather be generalized over message type? And then if the same message broker struct could be reused for async, then I guess RelmApp could be generic over message type and store the broker.
But overall, I'm really not sure how to proceed. Just adding run_with_broker and run_with_args_and_broker methods doesn't seem like such a bad idea anymore, but only until message broker is implemented for async.
What are your thoughts?

I'll have a closer look at this tomorrow. Maybe using dyn or even converting it to &str directly would at least help with getting rid of generics for the args and the additional lifetime.

Yes, storing args as Vec<String> and changing MessageBroker's generic to message type itself actually made it quite doable. Message type is always derived automatically from component type, so all of the following works as expected:
RelmApp::new(app_id).with_args(&some_args).with_broker(&some_broker).run::<SomeComponent>();

RelmApp::new(app_id).run::<SomeComponent>();

RelmApp::new(app_id).run_async::<SomeAsyncComponent>()

I made a draft PR, but haven't properly tested it yet.


Can't turn off pull_image

Hi,
When I create a container I unchecked "Always pull image before creating" But in the labels I have :
System  io.rancher.container.pull_image always
And my container not start because my image does not exist to docker hub.

I encountered the same problem.
The label is set to "always" even if the checkbox is unchecked which implies that rancher tries to find the image at a remote location and of course does not find it. The result is that container does not start with error ~ "Image cannot be found".

But I managed to find a workaround. You just need to :

uncheck the checkbox as you already do
manually add  the label io.rancher.container.pull_image (in advanced options) with value "never"

Value is then left as it is and image is locally retrieved

Reproduced with v0.56.0-rc1.

Version - master ui 1/22
Verified fixed

Issue still persist in the new version.
Image [index.docker.io/local/grr-lzd] failed to pull: repository docker.io/local/grr-lzd not found:
Have unchecked the box and also set label  io.rancher.container.pull_image: never
It just keeps trying to pull and download image everytime.
Is there something else I need to do to turn off the pull_image?


Feedback for Deploy WebTools

The part of the article "Supporting groups that should (not) have MailLink" is confusing. In order to have access to Mail Link should the registry entries be removed or should they stay in registry. Please make a clear formulation e.g.:
If access needed, please delete following entries....
If  no access needed, please remove following entries....

Document Details
⚠ Do not edit this section. It is required for docs.superOffice.com ➟ Docs Team processing.

Content Source: deploy_maillink_webextensions_on_citrix

Can you please look at this @pavlas77 ?


update README.md

delete_tkey => CRITICAL_delete_tkey
added explanation about manual sync mode.
change initialize() func
guide for using tkey ios sdk in multidevice environment

closing PR


installing angular-redux/store on angular 8.0.0 causes warning on missing peer dependencies<EMAIL_ADDRESS>

This is a...

[ ] feature request
[X] bug report
[ ] usage question

What toolchain are you using for transpilation/bundling?

[X] @angular/cli
[ ] Custom @ngTools/webpack
[ ] Raw ngc
[ ] SystemJS
[ ] Rollup
[ ] Other

Environment
NodeJS Version: v10.15.3
Typescript Version<EMAIL_ADDRESS>Angular Version: 8.0.0
@angular-redux/store version<EMAIL_ADDRESS>@angular/cli version: (if applicable<EMAIL_ADDRESS>OS: Windows 10 Version 1803 (OS Build 17134.765)
Link to repo showing the issus
(optional, but helps a lot)
Expected Behaviour:
npm installs @angular-redux/store on<EMAIL_ADDRESS>without warning
Actual Behaviour:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
Stack Trace/Error Message:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
Additional Notes:
(optional)

same with me, but everything seems to work fine !!

same to me too


Fix bare mode resolvers for Prefix and NamingConvention transforms

Hello @ardatan , been a while; so to remind you that you cannot get rid of me, here I am with fresh PR 🙂
Description
This PR fixes the following issues with bare mode transforms.
Prefix

The built-in resolver was always applying the prefix to the resolved typeName. Sometimes the typeName might be an extension over a resolver of another field that already went through transformation; hence the prefix might be applied multiple times. This fix ensures the prefix is not applied more than once.

Naming convention

Bug in the built-in defaultResolverComposer causing the return value of an entire original result in place of a single array item
Added processing of composite fields when enum config is available so that their types get the resolver composer attached
Prevent mapping of arguments for fields where arguments are not affected by the given config

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have followed the
CONTRIBUTING doc and the
style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] New and existing unit tests and linter rules pass locally with my changes

I missed your PRs already <3 Do you think we can have tests to prevent future regressions?


Update ansi-html to v0.0.8

Resolves #492.

Please accept this pull request. My npm audit report looks very bad because of the ansi-html vulnerability.

@Z-Zhao Unfortunately this project seems to have remained dormant as the Ember community has shifted their focus to building out Embroider as the eventual replacement for Broccoli.
For now I would recommend specifying the updated version as an override in your package.json. Assuming you're using NPM, this would be:
"overrides": {
  "ansi-html": "^0.0.8"
}

(If you're using Yarn, use "resolutions" instead of "overrides".)


docker-compose: fix image names

Symptoms:
$ sudo docker-compose up
Error: image library/cilium not found
ERROR: Error: image library/cilium not found

The images are located on
https://hub.docker.com/r/cilium/cilium/

Thanks for the fix :-)


Add debug function

Issue

Add Debug function on the app (relates to the issue #80 )

Overview (Required)

Debug menu from any screen
Add Clear cache function

Links

Please welcome a debug menu debot. Debot is a library to add a debug menu on any screens. Please refer to the document for more information.
If you are using an emulator, just press command + M. If you are running your dev app on a real device, shake it. The debug menu dialog will show up as seen in the image below.
Added Clear cache function for the custom debug function

Screenshot

Before
After

Technical change

Added injection to MainApplication to use repository
Implemented deleteAll method for SessionsRepository class

shake it

Does this library support any other way to show debug menu?
Like debug menu button on InformationFragment.

If you are using an emulator, just press command + M. We can add the button on the InformationFragment page by calling  debot.showDebugMenu(this);

looks like test is failing, I will take a look

debot.showDebugMenu(this);

Cool 🆒
Now I don't have concrete idea to show debug menu, this shake option seems good.

Ok, let me add the explanation about the debug menu on the info page. BTW I only have 14% of my battery now and forgot my adapter in my office, I will work on tomorrow.

Got it! Thanks!

Ok, let me add the explanation about the debug menu on the info page.

It's also okay to add this on another PR 😉

Great PR!
I want to add debug function to develop notification easily.
Currently, I uncomment this line to develop notification, it's too annoying :(
https://github.com/DroidKaigi/conference-app-2017/blob/master/app/src/main/java/io/github/droidkaigi/confsched2017/util/AlarmUtil.java#L22-L23

It's also okay to add this on another PR 😉

Yes, I would like to create another PR for this.

:pray:

:clap: Thanks for contribution! LGTM :100:


Upmerge v1.3.x branch to master

Upmerge the v1.3.x branch to master

No significant performance differences

No significant performance differences

@murgatroid99 Can you take a look at this Node failure on Mac? https://grpc-testing.appspot.com/job/gRPC_pull_requests_macos/5497/testReport/junit/(root)/node_macos_opt_native/tools_run_tests_helper_scripts_run_node_sh/

No significant performance differences

I fixed the node error - something slipped thru when resolving the upmerge conflict.
Mac failure is #11116
Windows failure are #9542, #11188, #11216


Add missing type for useTheme, and Example

This PR complements commit c427aed and fixes #2

Add missing type for useTheme
Add example for how to use this hook

const UseThemeExample = () => {
  const theme = useTheme();
  return <ActivityIndicator size="small" color={theme.colors?.blue100} />;
};

Organize Example layout

@Temzasse pls feel to merge it whenever if you agree with the change. Thanks!

Closing this PR for now. Will re-open a new one once #8 is merged


Change http- options to rpc- ones

Hi, I've got an error with Ubuntu 14.04 and Consul v0.7.4:
~# consul reload -http-addr=localhost:8500
flag provided but not defined: -http-addr
Usage: consul reload

  Causes the agent to reload configurations. This can be used instead
  of sending the SIGHUP signal to the agent.

Options:

  -rpc-addr=<IP_ADDRESS>:8400 RPC address of the Consul agent.

So the pull makes reload_command option adjustable.

This version of puppet-consul targets 0.7 and up, please instead simply adjust the command to match the new required argument (-rpc-addr)

solarkennedy, thanks for the fast answer! I've edited options with sth like s/http/rpc/g and removed firstly created option.

Yeah, with the latest edits it works well on my boxes:
Info: Class[Consul::Run_service]: Scheduling refresh of Service[consul]
Notice: /Stage[main]/Consul::Run_service/Service[consul]: Triggered 'refresh' from 1 events
Notice: Applied catalog in 51.98 seconds

Some tests are broken cause http-port is 8500 but rpc-port is 8400.
I've adjusted ports in tests.

Yay! Tests are green again. Kennedy, I've done please review.

Updated to Consul v0.8.3 and the problem has gone. Could you just update default Consul version to 0.8.3 from 0.7.4 in the consul::params from the module > 3.0.0?

Well... that is because consul 0.8 removed rpc-add entirely!
https://www.consul.io/docs/upgrade-specific.html#consul-0-8-0
I'm not ready to make such a breaking change on 0.8 yet.

 I guess we should remove the rpc-addr options entirely!!


First Meet-Up

Definitely!  Once you start seeing familiar faces it becomes much easier to start new discussions.


Make sure to add version numbers for autora-core in child packages

Make sure these are version numbers like "autora-core=^3.1.0" (not sure about the syntax here), rather than pinning specific version numbers. Otherwise we'll have a terrible time handling updates.


spi_nor: remove unneeded enter_dpd() at end of spi_nor_configure()

This block of code was in the original commit that added CONFIG_SPI_NOR_IDLE_IN_DPD but later modifications added acquire_device() and release_device() calls
earlier in spi_nor_configure() and the release_device() function will have already done the enter_dpd().

Hi, I ran across this just this morning and was about to open a PR with the same change, but then I found this PR. Guess my first contribution to zephyr will have to be something else :sweat_smile:
I have a board here with nothing on it but an nrf52840 and a flash chip (macronix MX25R8035F) where I am testing/measuring the current consumption with a high accuracy power supply and ampere meter. With the firmware just sleeping and all peripherals powered off I get a current draw of ~3 uA at 3V which aligns with the expected value of 2,35 uA from the nrf52840 product specification. This is with CONFIG_SPI_NOR_IDLE_IN_DPD=n  and manually suspending the flash and the spi bus (pm_device_action_run(device, PM_DEVICE_ACTION_SUSPEND)).
I noticed that with CONFIG_SPI_NOR_IDLE_IN_DPD=y the current draw is around 10 uA, so the flash apparently is not in deep power-down. I was able to trace this down the root cause: enter_dpd is called twice, once by the last release_device from spi_nor_configure and a second time from the code that this PR removes. Sending the SPI_NOR_CMD_DPD twice causes the flash to exit deep power-down. Funny enough, sending the command 3 times will let the flash go into deep-power down again. Sending an even number of SPI_NOR_CMD_DPD let's the device be in stand-by mode, odd number of SPI_NOR_CMD_DPD puts it in deep power-down :smile:
Just wanted to share this to illustrate the impact. For us in our project we will have to either cherry pick this commit or go for CONFIG_SPI_NOR_IDLE_IN_DPD=n  and manual suspend/resume until this patch makes its way from upstream to nrf sdk.

Hi, I ran across this just this morning and was about to open a PR with the same change, but then I found this PR. Guess my first contribution to zephyr will have to be something else 😅
I have a board here with nothing on it but an nrf52840 and a flash chip (macronix MX25R8035F) where I am testing/measuring the current consumption with a high accuracy power supply and ampere meter. With the firmware just sleeping and all peripherals powered off I get a current draw of ~3 uA at 3V which aligns with the expected value of 2,35 uA from the nrf52840 product specification. This is with CONFIG_SPI_NOR_IDLE_IN_DPD=n and manually suspending the flash and the spi bus (pm_device_action_run(device, PM_DEVICE_ACTION_SUSPEND)).
I noticed that with CONFIG_SPI_NOR_IDLE_IN_DPD=y the current draw is around 10 uA, so the flash apparently is not in deep power-down. I was able to trace this down the root cause: enter_dpd is called twice, once by the last release_device from spi_nor_configure and a second time from the code that this PR removes. Sending the SPI_NOR_CMD_DPD twice causes the flash to exit deep power-down. Funny enough, sending the command 3 times will let the flash go into deep-power down again. Sending an even number of SPI_NOR_CMD_DPD let's the device be in stand-by mode, odd number of SPI_NOR_CMD_DPD puts it in deep power-down 😄
Just wanted to share this to illustrate the impact. For us in our project we will have to either cherry pick this commit or go for CONFIG_SPI_NOR_IDLE_IN_DPD=n and manual suspend/resume until this patch makes its way from upstream to nrf sdk.

The info here, IMHO, should be registered as an issue as it may be something that others stumble upon. The PR here should be referencing that issue. I think this is important to note such issue and the fact that it has been solved, for others.

The info here, IMHO, should be registered as an issue as it may be something that others stumble upon.

Sorry for the delay, created an issue: https://github.com/zephyrproject-rtos/zephyr/issues/70146 and referenced this PR.

Also, you may be interested in this other PR https://github.com/zephyrproject-rtos/zephyr/pull/69588.

Thanks for pointing me there! We don't user the nvs in the use case that I'm currently working on, but good to know :)


Screen Reader Support For Blind Spymaster

I was just testing the app with a screen reader on my phone (iPhone) and I noticed that there is no information whether a word is blue, red, bystander or assassin when going through the words. So, a blind player cannot play as the spymaster. Any chance you can add this feature? I'm not sure if you can simply add alt-text to the words that hte screen reader picks up while it is not visible in the UI to distract sighted players.

@ninjabunny
Was this issue solved? I just checked the app and you still can't tell with the screen reader whether a word is red, blue, bystander, or assassin.

Hey, sorry for taking so long. My life was pretty hectic for the last year. now covid allowed me more time to fix this issue. I just forgot to push it. please test it out now and see if it reads for you. i forgot how to use mac screen reader on the site.

Hi,
No worries, hope you are doing well during these chaotic times. Unfortunately, it still doesn't seem to work. Both in the Spymaster view and also in the normal view when you click the links to reveal the colors, nothing besides the word is read. Tried with both NVDA and Narrator on Windows. Maybe you should look into ARIA labels? These are visually invisible but the screen reader reads the values. You'll just need to enable them and disable them depending on the state of the word.
Thanks for doing this, I have a blind board gamers group which might be interested in playing Codenames as we are all stuck at home right now :)


Exception thrown when a DraggableScrollableSheet is taken out of the tree before animateTo finishes

Steps to Reproduce

Execute flutter run on the code sample
Tap the button to trigger the DraggableScrollableSheet (the one that says trigger).
Just after you press the previous button, and before the animation finishes, tap the hide button.

Expected results:
This should just take the DraggableScrollableSheet out of the tree without errors.
Actual results:
This produced the error below.

Code sample

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  bool showDraggable = false;
  bool scrollTrigger = false;

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
          body: SafeArea(
        child: Stack(
          children: [
            if (showDraggable)
              DraggableWidget(
                scrollTrigger: scrollTrigger,
              ),
            Positioned(
              left: 0,
              top: 0,
              child: ElevatedButton(
                onPressed: () {
                  setState(() {
                    showDraggable = !showDraggable;
                  });
                },
                child: showDraggable ? const Text('hide') : const Text('show'),
              ),
            ),
            Positioned(
              right: 0,
              top: 0,
              child: ElevatedButton(
                onPressed: () {
                  setState(() {
                    scrollTrigger = !scrollTrigger;
                  });
                },
                child: const Text('trigger'),
              ),
            ),
          ],
        ),
      )),
    );
  }
}

class DraggableWidget extends StatefulWidget {
  final bool scrollTrigger;

  const DraggableWidget({required this.scrollTrigger, Key? key})
      : super(key: key);

  @override
  State<DraggableWidget> createState() => _DraggableWidgetState();
}

class _DraggableWidgetState extends State<DraggableWidget> {
  late DraggableScrollableController controller;
  double scrollSize = 0.3;

  @override
  void initState() {
    super.initState();
    controller = DraggableScrollableController();
    controller.addListener(updateSize);
  }

  void updateSize() {
    scrollSize = controller.size;
  }

  @override
  void dispose() {
    controller.removeListener(updateSize);
    controller.dispose();
    super.dispose();
  }

  @override
  void didUpdateWidget(DraggableWidget oldWidget) {
    super.didUpdateWidget(oldWidget);

    WidgetsBinding.instance.addPostFrameCallback((timestamp) {
      if (0.5 > controller.size) {
        controller.animateTo(0.8,
            duration: const Duration(milliseconds: 500), curve: Curves.ease);
      } else {
        controller.animateTo(0.3,
            duration: const Duration(milliseconds: 500), curve: Curves.ease);
      }
    });
  }

  @override
  Widget build(BuildContext context) {
    return DraggableScrollableSheet(
      minChildSize: 0.3,
      maxChildSize: 0.8,
      initialChildSize: scrollSize,
      controller: controller,
      builder: ((context, scrollController) {
        return SingleChildScrollView(
          controller: scrollController,
          child: Container(
            height: 100,
            color: Colors.red,
          ),
        );
      }),
    );
  }
}

Logs

                     ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
                     The following assertion was thrown while finalizing the widget tree:
                     ScrollableState#641cc(tickers: tracking 1 ticker, position:
                     _DraggableScrollableSheetScrollPosition#576a8(offset: 0.0, range: -1.0..1.0, viewport: 471.3,
                     ScrollableState, ClampingScrollPhysics -> RangeMaintainingScrollPhysics, null,
                     ScrollDirection.idle), effective physics: ClampingScrollPhysics -> RangeMaintainingScrollPhysics)
                     was disposed with an active Ticker.
                     ScrollableState created a Ticker via its TickerProviderStateMixin, but at the time dispose() was
                     called on the mixin, that Ticker was still active. All Tickers must be disposed before calling
                     super.dispose().
                     Tickers used by AnimationControllers should be disposed by calling dispose() on the
                     AnimationController itself. Otherwise, the ticker will leak.
                     The offending ticker was:
                       _WidgetTicker(created by ScrollableState#641cc)
                       The stack trace when the _WidgetTicker was actually created was:
                       #0      new Ticker.<anonymous closure> (package:flutter/src/scheduler/ticker.dart:67:40)
                       #1      new Ticker (package:flutter/src/scheduler/ticker.dart:69:6)
                       #2      new _WidgetTicker (package:flutter/src/widgets/ticker_provider.dart:385:81)
                       #3      TickerProviderStateMixin.createTicker
                       (package:flutter/src/widgets/ticker_provider.dart:295:34)
                       #4      new AnimationController.unbounded
                       (package:flutter/src/animation/animation_controller.dart:279:21)
                       #5      DraggableScrollableController.animateTo
                       (package:flutter/src/widgets/draggable_scrollable_sheet.dart:107:73)
                       #6      _DraggableWidgetState.didUpdateWidget.<anonymous closure> (package:issue/main.dart:98:20)
                       #7      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1146:15)
                       #8      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1091:9)
                       #9      SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:997:5)
                       #13     _invoke (dart:ui/hooks.dart:151:10)
                       #14     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:308:5)
                       #15     _drawFrame (dart:ui/hooks.dart:115:31)
                       (elided 3 frames from dart:async)

                     When the exception was thrown, this was the stack:
                     #0      TickerProviderStateMixin.dispose.<anonymous closure> (package:flutter/src/widgets/ticker_provider.dart:342:13)
                     #1      TickerProviderStateMixin.dispose (package:flutter/src/widgets/ticker_provider.dart:360:6)
                     #2      RestorationMixin.dispose (package:flutter/src/widgets/restoration.dart:983:11)
                     #3      ScrollableState.dispose (package:flutter/src/widgets/scrollable.dart:516:11)
                     #4      StatefulElement.unmount (package:flutter/src/widgets/framework.dart:5032:11)
                     #5      _InactiveElements._unmount (package:flutter/src/widgets/framework.dart:1914:13)
                     #6      _InactiveElements._unmount.<anonymous closure> (package:flutter/src/widgets/framework.dart:1912:7)
                     #7      ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:4859:14)
                     #8      _InactiveElements._unmount (package:flutter/src/widgets/framework.dart:1910:13)
                     #9      _InactiveElements._unmount.<anonymous closure> (package:flutter/src/widgets/framework.dart:1912:7)
                     #10     SingleChildRenderObjectElement.visitChildren (package:flutter/src/widgets/framework.dart:6202:14)
                     #11     _InactiveElements._unmount (package:flutter/src/widgets/framework.dart:1910:13)
                     #12     _InactiveElements._unmount.<anonymous closure> (package:flutter/src/widgets/framework.dart:1912:7)
                     #13     SingleChildRenderObjectElement.visitChildren (package:flutter/src/widgets/framework.dart:6202:14)
                     #14     _InactiveElements._unmount (package:flutter/src/widgets/framework.dart:1910:13)
                     #15     _InactiveElements._unmount.<anonymous closure> (package:flutter/src/widgets/framework.dart:1912:7)
                     #16     _LayoutBuilderElement.visitChildren (package:flutter/src/widgets/layout_builder.dart:68:14)
                     #17     _InactiveElements._unmount (package:flutter/src/widgets/framework.dart:1910:13)
                     #18     _InactiveElements._unmount.<anonymous closure> (package:flutter/src/widgets/framework.dart:1912:7)
                     #19     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:4859:14)
                     #20     _InactiveElements._unmount (package:flutter/src/widgets/framework.dart:1910:13)
                     #21     _InactiveElements._unmount.<anonymous closure> (package:flutter/src/widgets/framework.dart:1912:7)
                     #22     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:4859:14)
                     #23     _InactiveElements._unmount (package:flutter/src/widgets/framework.dart:1910:13)
                     #24     ListIterable.forEach (dart:_internal/iterable.dart:39:13)
                     #25     _InactiveElements._unmountAll (package:flutter/src/widgets/framework.dart:1923:25)
                     #26     BuildOwner.lockState (package:flutter/src/widgets/framework.dart:2516:15)
                     #27     BuildOwner.finalizeTree (package:flutter/src/widgets/framework.dart:2932:7)
                     #28     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:893:19)
                     #29     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:370:5)
                     #30     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1146:15)
                     #31     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1083:9)
                     #32     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:997:5)
                     #36     _invoke (dart:ui/hooks.dart:151:10)
                     #37     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:308:5)
                     #38     _drawFrame (dart:ui/hooks.dart:115:31)
                     (elided 3 frames from dart:async)
                     ════════════════════════════════════════════════════════════════════════════════════════════════════
[   +2 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[  +15 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[  +15 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[  +15 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +8 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +8 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +8 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +8 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +6 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +9 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[  +13 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[  +45 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[  +45 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[  +44 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[        ]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +1 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +3 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.
[   +8 ms]
           Another exception was thrown: ScrollController not attached to any scroll views.

Analyzing issue...
No issues found! (ran in 1.4s)

[✓] Flutter (Channel stable, 3.0.5, on Ubuntu 22.04.1 LTS 5.15.0-46-generic, locale en_US.UTF-8)
    • Flutter version 3.0.5 at /home/guido/snap/flutter/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f1875d570e (7 weeks ago), 2022-07-13 11:24:16 -0700
    • Engine revision e85ea0e79c
    • Dart version 2.17.6
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /home/guido/Android/Sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /snap/android-studio/123/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
    • cmake version 3.10.2
    • ninja version 1.8.2
    • pkg-config version 0.29.1

[✓] Android Studio (version 2021.2)
    • Android Studio at /snap/android-studio/123/android-studio
    • Flutter plugin version 69.0.2
    • Dart plugin version 212.5744
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code
    • VS Code at /snap/code/current
    • Flutter extension version 3.46.0

[✓] Connected device (3 available)
    • motorola edge 20 pro (mobile) • ZY22DZ85NZ • android-arm64  • Android 12 (API 31)
    • Linux (desktop)               • linux      • linux-x64      • Ubuntu 22.04.1 LTS 5.15.0-46-generic
    • Chrome (web)                  • chrome     • web-javascript • Google Chrome 104.0.5112.101

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hi @danagbemava-nc. Thank you very much ! Yes, it seems to be fixed in the latest version. I tried both with my example and the app i'm working on and neither show the error

Thanks for confirming this.
Closing as fixed.


Encountered two children with the same key

The key for event generated with the logic key={'${event.start}${event.title}'}. I have a case where there can be multiple events with exactly same details. This results in a react warning.
Maybe index be added to the combination to prevent this from happening?

Hi, thanks for the interest. Yes it should be fixed. Can you send a PR for this? Maybe index is enough, but adding keyExtractor is ideal.
https://reactnative.dev/docs/flatlist#keyextractor

As I've published v2.0.0-rc and implemented this topic, I'll close this issue. If you have bugs on it, feel free to report it!
https://github.com/acro5piano/react-native-big-calendar/releases/tag/v2.0.0-rc
Summary: I've added ${event.end} too. It's rare that the collision happens.


Invalid az cli commands for migrating classic storage account

The az cli commands for migrating a classic storage account do not work.
azure storage account prepare-migration <storage-account>
azure storage account abort-migration <storage-account>
azure storage account commit-migration <storage-account>

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

ID: 1bb435b1-f9b4-ba08-0a44-146d5db505ad
Version Independent ID: b44176d7-8770-3727-2b28-cc31497536d6
Content: Migrate a classic storage account - Azure Storage
Content Source: articles/storage/common/storage-account-migrate-classic.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@rguptar
Thanks for your feedback! We will investigate and update as appropriate.

@rguptar
I'm going to assign this to the document author so they can take a look at it accordingly.
@tamram
Can you please check and add your comments on this doc update request as applicable.

@rguptar - We've updated the article to include PowerShell samples.
Per our internal communication, you should be able to use the CLI commands shown in this article for VMs, if you install the original version of Azure CLI:
https://learn.microsoft.com/azure/virtual-machines/migration-classic-resource-manager-cli#step-2-set-your-subscription-and-register-the-provider

#please-close

We are still blocked. @tamram please reopen.

Hi, blocked here as well.
The Classic Storage Account Migration commands don't work properly.
This is an enterprise case.


Opal API Tests

Tests written to test the Opal API endpoints, checking that data can be sent and read successfully.
Closes https://github.com/ImperialCollegeLondon/gridlington-datahub/issues/68

Currently have this in draft as the test_get_opal_api function isn't working. I get the following error when converting the GET request JSON into a Dataframe and comparing it to the global Opal variable:
ValueError: Can only compare identically-labeled (both index and columns) DataFrame
objects

Both Dataframe objects look identical in terms of index and columns. The only difference I can spot is a difference in how the Time column values have been formatted. @AdrianDAlessandro Could you have a look and see if you can figure out the issue?

Have a look at this, from Solidity: https://github.com/ImperialCollegeLondon/Solidity-GUI/blob/af4e254820ab49072d1f1ab351cca959144d77ed/tests/conftest.py#L29


Define es_version property and reuse it in both project and buildscript

Closes #213

@vvanholl PTAL
I would love to have this merged before I push final PR for ES 7.3.0 upgrade (https://github.com/vvanholl/elasticsearch-prometheus-exporter/issues/202).

@vvanholl any news?

@vvanholl Please take a look. Merging this will unblock pushing in PRs for plugin upgrades stacked in the queue.


Question - Avoid multi-reporter-config.json and runner-result creation

Hi, Is there a way to avoid the multi-reporter-config.json file creation and also the runner-result folder creation, I don't want that since I am only interested on the console output.

@tnicola could you please, give any comment on that please?

@tnicola We're also trying to implement your functionality, but we're struggling with getting our reports configured. We don't want the included reports, we want to use mochaawesomereporter and to disable the excess file being produced.
If you're done updating this repository, can you please telll us, so we can move on?


Use FlutterProject to locate files

A bit of cleanup of flutter_tools' handling of project directories and manifests.

@szakarias Could you take a look. Especially the latest commit?


Text editor adds spaces in front of quotes in html files

VSCode Version:  1.49
OS Version:  windows 8.1

Steps to Reproduce:

create html using emmet
create css
use beautify to format
save
close vscode
reopen vscode
make edits in both html and css
reformat
save (starts adding spaces before quotes in multiple locations, most noticeably in id/class specifications)

Does this issue occur when all extensions are disabled?: Yes/No - - yes

Can you add a sample code that shows that? Do you have format on save enabled?
Do you have an other formatter installed as well? I checked that beautify does not add spaced before =

Sorry, I do not have the VS Code editor installed any longer, and did not
take screenshots;  the automated spaces were added before the quotes ( " ),
and not the equal sign.
The HTML files that I was editing had to be opened in the brackets editor
in order to remove the spaces permanently; otherwise, they returned
whenever I saved changes.
Beautify was the only formatter that I had intentionally installed for that
purpose.
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Fri, Sep 25, 2020 at 4:40 PM Martin Aeschlimann<EMAIL_ADDRESS>wrote:

Can you add a sample code that shows that? Do you have format on save
enabled?
Do you have an other formatter installed as well? I checked that beautify
does not add spaced before =
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/107441#issuecomment-699144360,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJACTZPIDW7RCBOZAYWSZEDSHT52TANCNFSM4RZQ3FYQ
.

Ah, then it's an issue with the Beautify extension. Please file the issue there.

Thanks Martin; issue was forwarded to the beautify team.
-Kevin Tousey
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Thu, Oct 1, 2020 at 2:07 PM Martin Aeschlimann<EMAIL_ADDRESS>wrote:

Ah, then it's an issue with the Beautify extension. Please file the issue
there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/107441#issuecomment-702307128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJACTZK6EQIOTCOEBR2X7EDSITAPLANCNFSM4RZQ3FYQ
.


version not found<EMAIL_ADDRESS>

i have a issue following the instructions on the getting started page.
version not found<EMAIL_ADDRESS>i tried to search for the issue, but i have not see any post on this
bmatusiak:~/workspace $ git clone https://github.com/twbs/bootstrap.git
Cloning into 'bootstrap'...
remote: Counting objects: 93466, done.
remote: Compressing objects: 100% (64/64), done.
remote: Total 93466 (delta 28), reused 0 (delta 0), pack-reused 93402
Receiving objects: 100% (93466/93466), 91.62 MiB | 19.86 MiB/s, done.
Resolving deltas: 100% (60181/60181), done.
Checking connectivity... done.
bmatusiak:~/workspace $ npm install -g grunt-cli
/home/ubuntu/.nvm/versions/node/v4.4.0/bin/grunt -> /home/ubuntu/.nvm/versions/node/v4.4.0/lib/node_modules/grunt-cli/bin/grunt
<EMAIL_ADDRESS>/home/ubuntu/.nvm/versions/node/v4.4.0/lib/node_modules/grunt-cli
├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>bmatusiak:~/workspace $ cd bootstrap/
bmatusiak:~/workspace/bootstrap (master) $ npm install
npm WARN deprecated<EMAIL_ADDRESS>Grunt needs your help! See https://github.com/gruntjs/grunt/issues/1403.
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.

><EMAIL_ADDRESS>install /home/ubuntu/workspace/bootstrap/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs
> node install.js

PhantomJS not found on PATH
Downloading https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-1.9.8-linux-x86_64.tar.bz2
Saving to /tmp/phantomjs/phantomjs-1.9.8-linux-x86_64.tar.bz2
Receiving...
| [================------------------------] 40% 0.0s/
Received 12854K total.
Extracting tar contents (via spawned process)
Removing /home/ubuntu/workspace/bootstrap/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom
Copying extracted folder /tmp/phantomjs/phantomjs-1.9.8-linux-x86_64.tar.bz2-extract-1458748219665/phantomjs-1.9.8-linux-x86_64 -> /home/ubuntu/workspace/bootstrap/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom
Writing location.js file
Done. Phantomjs binary available at /home/ubuntu/workspace/bootstrap/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom/bin/phantomjs
npm ERR! Linux 4.2.0-c9
npm ERR! argv "/home/ubuntu/.nvm/versions/node/v4.4.0/bin/node" "/home/ubuntu/.nvm/versions/node/v4.4.0/bin/npm" "install"
npm ERR! node v4.4.0
npm ERR! npm  v2.14.20

npm ERR! version not found<EMAIL_ADDRESS>npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/workspace/bootstrap/npm-debug.log
bmatusiak:~/workspace/bootstrap (master) $

https://github.com/twbs/bootstrap/issues/19595

Caused by https://github.com/uber/npm-shrinkwrap/issues/103
Nothing wrong with your setup. I've spent some time troubleshooting, installing and reinstalling node and npm and finally figured out which package is responsible. I guess this will resolve itself in a short while (hopefully)! I assume this breaks lots of builds all over the world.

It's because of this<EMAIL_ADDRESS>

ok so this worked for me...
before npm install
do npm install https://github.com/uber/npm-shrinkwrap.git
and should temp fix this issue

Fixing #18559 will sidestep this clusterfsck.

Fixed by #19604 & #19605.


Also add engine-node version into repo

...  so that Admin/Controller can use it to not install incompatible versions

@Apollon77
Is this issue still relevant in an way?
If still needed:
Should this info be added by user or retrived from some source i.e. from io-package.json?
Should the info incorporated into source dist-sources-*.json or added by converter creating the downloaded files?

Repodata already contains 'common.node'. This data is merged from package.json during repo build:
https://github.com/ioBroker/ioBroker.repobuilder/blob/d77433836ace11ef9fbfabbb9ddf0e1215623ef5/lib/github.js#L43
So I close her. Please open a ne issue if something is still open.


The disaster endDate isn't checking for absurd values

Will accept 9999

I can verify that the website does not accept 9999 nor 09/21/2999 as an end date when a volunteer clicks the volunteer button.
Close bug?

@asherw That was also fixed at CodeMash. I fell behind closing issues :(


Add cosine distance to core.chpl

GO ahead and put it right here: https://github.com/buddha314/numsuch/blob/mad/src/core.chpl#L65 in the MAD branch
Additionally, we should try to mirror the Scipy Version's interface if we can, will let people get into the code quicker.

And one more thing, the original code did cosine SIMILARITY, we should have both.  Similarity is |vw|/|v||w| and DISTANCE is 1-|vw|/|v||w|

Bonus, threw in Cosine Similarity on top of Ben's work!


It causing vertical scroll issue in list when building with XCode 16

In Xcode 15, it’s working fine. However, when I run the app from Xcode 16, the list with swipe action items gives me a hard time scrolling vertically. I checked this behavior in Xcode 15, and it’s working, but in Xcode 16, it’s causing problems.

Seeing the same issue. I can't scroll within a scroll view if I am touching a SwipeView. If the whole screen is covered in SwipeViews it therefor makes the scroll view un-scrollable

sorry, nevermind, I used ' .swipeMinimumDistance(30)' and this problem was resolved


Homebrew recipe

Hey Jeff - what do you think about providing localtunnel as a Homebrew formula, instead of (or in addition to) installing with pip? I'm a Rubyist who loves localtunnel, and it would be great to be able to install it without having to install Python-specific stuff that I wouldn't otherwise need.
Thanks for your good work.

That Python version has reached EOL. There is a minimal Go version in master incubating. If there is demand, I'll produce binary releases that work on OS X and Linux.

also ngrok is available through homebrew.

ngrok is now closed source. :(


chore: add generateBuilders

This PR adds the option generateBuilders to jsonschema2pojo since those make the usage of the generated models much more fun. Additionally, a link in the documentation is fixed.

For consistency I would suggest adding builders to these classes as well: https://github.com/MobilityData/gbfs-json-schema/tree/master/models/java/gbfs-java-model/src/main/java/org/mobilitydata/gbfs/v2_3/gbfs (same with v2_2)

I agree, thats why I added generateBuilders three times in pom.yml.

I agree, hence I already added generateBuilders three times in pom.yml.

The classes I pointed to are not generated, so you need to add them manually. The generated sources are not checked in to the repo.

I agree, hence I already added generateBuilders three times in pom.yml.

The classes I pointed to are not generated, so you need to add them manually. The generated sources are not checked in to the repo.

Ah, thanks for the clarification. I will do that.

I'm closing this PR. I was confused with exactly these not generated classes without a builder, the other ones already provide builders.


Consider exporting toQuery?

I want to change a class based on media queries, and while it is possible to do it like:
const className = matchMedia("(min-width: 768px)") ? 'desktop' : 'mobile';

I'll rather use your already awesome work and do it like
import {toQuery} from 'react-responsive';
const className = matchMedia(toQuery({minWidth: 768})) ? 'desktop' : 'mobile';

just to keep stuff consistent.
btw, thank you for this awesome package.

You can try importing react-responsive/src/toQuery directly, otherwise we could export it. Would be a great starter PR if you'd like to submit it.

@soska Did that work? Going to close this since it should work fine.


Update Example in Introduction

Update the example so it works/compiles
The main function could be cleaned up a bit, the error handling I wrote is a bit hard to read

Thanks! 💕


Sunsetting project and archiving the repo in 2020

Hi @all-contributors and everyone else,
I'm creating this issue because I plan to sunset the React Notification project and to archive the repo. I'm sunsetting the project for two reasons: one is practical and the other is personal.
The practical reason is because the Material UI project provides the same component, with support for React 16.9. The Material UI implementation also:

Has official support for new versions, fixing issues, etc.
Uses the true Material design spec for snackbars
Provides better support for customization
Ships with support for accessibility

The personal reason is because I have less time to support the project and because I don't use React as much as in 2015-2017 (when this project was under active development). This is evident in how long it has taken for me to work in support for React 16.9. @TheRusskiy started the React 16.9 implementation in #155 and I continued that work with a rewrite in #158, but as I worked on this, I wanted to take a step back. I asked if it was worth the time and effort of myself and other contributors to maintain this project.
Here's the current plan. In Jan 2020, I will:

Close any open issues on this project
Close any open pull requests
Archive the Github repo

I will keep the version 6.8.5 published on npm for legacy use. It's a stable release, but if new bugs are discovered, I can't promise a fix.
Thanks everyone for a great 4 years and ~8 months on this project.  It was rewarding to create this project and to see it used by so many people. I released v1 on Mar 21, 2015 and the project is now 37 versions later at v6.8.5 and 31 contributors. The package has been downloaded from npm over 1,013,000 times! Special thanks to all of the contributors. You're the nice people who make open source awesome.
Best,
pburtchaell (Patrick)

cc @all-contributors


DockerExternalVolumeSuite: add daemon to test

Part of #23998. Adds a daemon to this test, so that the
volume that's created is added to this test daemon's vol store
instead of the main test daemons.
This doesn't solve the issue, as there isn't currently a way to remove a nil volume,
but does make sure no other tests are affected by it, increasing the integration
cli tests runtime by ~12 minutes.
Signed-off-by: Christopher Jones<EMAIL_ADDRESS>

ping @cpuguy83 @vdemeester wdyt?

SGTM 👼

LGTM

LGTM 🐮


Integration Tests for full service

Done....ish.  Although this is technically dependent on Tika Translate, all the pieces which surround Tika and network calls are tested with stubs, so all of the logic is indeed Unit Tested and Integration Tested.


Bolt client lifetime

The docs show GraphClientFactory being used to create instances of GraphClient. Is there an equivalent pattern for BoltGraphClient? It looks like BoltGraphClient might have to be a singleton to avoid multiple calls to BoltGraphClient.ConnectAsync().

Hey Matt,
Yes, both the GraphClient and BoltGraphClient should be singletons, and no - there is no factory equivalent for the BoltGraphClient. Is this something you need?
I've always used the DI to work with singletons...

I'm working on a codebase that uses IGraphClientFactory to get hold of IGraphClient and hoped I wouldn't have to make code changes switching to the bolt client. Seems I'm going to have to inject IGraphClient directly into the repository classes, and remove the factory. Thanks for clarifying.


Trade offers are not always canceled

Hi guys!
For some reason, it is not always possible to reject a trade offer using the cancelOffer (or declineOffer) method
Here is my code:
function cancelTrade(offerid) {
	offers.cancelOffer({
		tradeOfferId: offerid
	}, function(err, log) {
	if (err) {
		logger.error('Couldn't cancel the trade #' + offerid);
		logger.debug(err);
		return;
	}
		logger.debug(log);
		logger.trace('Trade offer #' + offerid + ' was canceled successfully! v2');
	});

	offers.declineOffer({
		tradeOfferId: offerid
	}, function (error, result) {
	if (error) {
		logger.error('Couldn't cancel the trade #' + offerid + ' v1');
		logger.debug(err);
		return;
	}
		logger.trace('Trade offer #' + offerid + ' was canceled successfully! v1');
	});
}

What could be the problem?
I use steam-tradeoffers v 3.2.1

Have a same issue

Have a same issue


Documentation for ELK and Coherence

TBD:

create tags for latest code with Coherence changes.
update tag name in _data/var.yml

Hello @edburns  the pr is ready for review, but a prerequisite https://github.com/wls-eng/arm-oraclelinux-wls/issues/197, you can finish that with 4 clicks and 1 input.

Have tested the changes via galiacheng/wls-repos/2020-12-02-01-Q4.


CocoaPods gives an error of no compatible version

Could solve it by uncommenting platform :ios, '9.0' in podfile
This plugin was always working fantastic. But from today on, the autocomplete did not show any places (like my internet connection was disabled). I then upgraded to 2.0.0 and get the following error from CocoaPods:
CocoaPods' output:
↳
Preparing
Analyzing dependencies

Inspecting targets to integrate
  Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

Finding Podfile changes
  M Flutter
  - cloud_firestore
  - firebase_auth
  - firebase_core
  - firebase_database
  - firebase_messaging
  - firebase_storage
  - flutter_facebook_login
  - flutter_native_image
  - fluttertoast
  - geocoder
  - google_places_picker
  - image_cropper
  - image_downloader
  - image_picker
  - keyboard_visibility
  - location
  - path_provider
  - permission_handler
  - shared_preferences
  - sqflite
  - url_launcher
  - vibrate

Fetching external sources
-> Fetching podspec for `Flutter` from `.symlinks/flutter/ios`
-> Fetching podspec for `cloud_firestore` from `.symlinks/plugins/cloud_firestore/ios`
-> Fetching podspec for `firebase_auth` from `.symlinks/plugins/firebase_auth/ios`
-> Fetching podspec for `firebase_core` from `.symlinks/plugins/firebase_core/ios`
-> Fetching podspec for `firebase_database` from `.symlinks/plugins/firebase_database/ios`
-> Fetching podspec for `firebase_messaging` from `.symlinks/plugins/firebase_messaging/ios`
-> Fetching podspec for `firebase_storage` from `.symlinks/plugins/firebase_storage/ios`
-> Fetching podspec for `flutter_facebook_login` from `.symlinks/plugins/flutter_facebook_login/ios`
-> Fetching podspec for `flutter_native_image` from `.symlinks/plugins/flutter_native_image/ios`
-> Fetching podspec for `fluttertoast` from `.symlinks/plugins/fluttertoast/ios`
-> Fetching podspec for `geocoder` from `.symlinks/plugins/geocoder/ios`
-> Fetching podspec for `google_places_picker` from `.symlinks/plugins/google_places_picker/ios`
-> Fetching podspec for `image_cropper` from `.symlinks/plugins/image_cropper/ios`
-> Fetching podspec for `image_downloader` from `.symlinks/plugins/image_downloader/ios`
-> Fetching podspec for `image_picker` from `.symlinks/plugins/image_picker/ios`
-> Fetching podspec for `keyboard_visibility` from `.symlinks/plugins/keyboard_visibility/ios`
-> Fetching podspec for `location` from `.symlinks/plugins/location/ios`
-> Fetching podspec for `path_provider` from `.symlinks/plugins/path_provider/ios`
-> Fetching podspec for `permission_handler` from `.symlinks/plugins/permission_handler/ios`
-> Fetching podspec for `shared_preferences` from `.symlinks/plugins/shared_preferences/ios`
-> Fetching podspec for `sqflite` from `.symlinks/plugins/sqflite/ios`
-> Fetching podspec for `url_launcher` from `.symlinks/plugins/url_launcher/ios`
-> Fetching podspec for `vibrate` from `.symlinks/plugins/vibrate/ios`

Resolving dependencies of `Podfile`
[!] CocoaPods could not find compatible versions for pod "google_places_picker":
  In snapshot (Podfile.lock):
    google_places_picker (from `.symlinks/plugins/google_places_picker/ios`)

  In Podfile:
    google_places_picker (from `.symlinks/plugins/google_places_picker/ios`)

It seems like you've changed the constraints of dependency `google_places_picker` inside your development pod `google_places_picker`.
You should run `pod update google_places_picker` to apply changes you've made.

/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:328:in `raise_error_unless_state'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:310:in `block in unwind_for_conflict'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:308:in `tap'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:308:in `unwind_for_conflict'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:257:in `process_topmost_state'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:182:in `resolve'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolver.rb:43:in `resolve'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/resolver.rb:123:in `resolve'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/analyzer.rb:781:in `block in resolve_dependencies'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/user_interface.rb:64:in `section'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/analyzer.rb:779:in `resolve_dependencies'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/analyzer.rb:88:in `analyze'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:243:in `analyze'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:154:in `block in resolve_dependencies'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/user_interface.rb:64:in `section'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:153:in `resolve_dependencies'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:116:in `install!'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/command/install.rb:41:in `run'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/lib/cocoapods/command.rb:52:in `run'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/gems/cocoapods-1.5.3/bin/pod:55:in `<top (required)>'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/bin/pod:22:in `load'
/usr/local/Cellar/cocoapods/1.5.3_1/libexec/bin/pod:22:in `<main>'

Error output from CocoaPods:
↳
[!] Automatically assigning platform `ios` with version `8.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

Finished with error: Error running pod install

You need to set the platform version to at least 9.0 in your Profile, due to an increase in the minimum requirements of the Google Places SDK.


Upgrade to Unicode 15.0.0, prepare for v1.3.0 release

Fixes https://github.com/artichoke/focaccia/issues/163.

repo labeler dry run:
🏃 Running GitHub Labeler
[dryrun] ✅ Skipping update for 'A-build' label. Same color and description
[dryrun] ✅ Skipping update for 'A-build-target' label. Same color and description
[dryrun] ✅ Skipping update for 'A-casecmp' label. Same color and description
[dryrun] ✅ Skipping update for 'A-crate-features' label. Same color and description
[dryrun] ✅ Skipping update for 'A-deps' label. Same color and description
[dryrun] ✅ Skipping update for 'A-folding' label. Same color and description
[dryrun] ✅ Skipping update for 'A-packaging' label. Same color and description
[dryrun] ✅ Skipping update for 'A-performance' label. Same color and description
[dryrun] ✅ Skipping update for 'A-project' label. Same color and description
[dryrun] ✅ Skipping update for 'A-release' label. Same color and description
[dryrun] ✅ Skipping update for 'A-security' label. Same color and description
[dryrun] 🎨 Creating 'A-unicode' label with color 'f7e101' and desc 'Area: Unicode tables and version bumps.'
[dryrun] ✅ Skipping update for 'C-bug' label. Same color and description
[dryrun] ✅ Skipping update for 'C-docs' label. Same color and description
[dryrun] ✅ Skipping update for 'C-enhancement' label. Same color and description
[dryrun] ✅ Skipping update for 'C-quality' label. Same color and description
[dryrun] ✅ Skipping update for 'C-question' label. Same color and description
[dryrun] ✅ Skipping update for 'E-easy' label. Same color and description
[dryrun] ✅ Skipping update for 'E-medium' label. Same color and description
[dryrun] ✅ Skipping update for 'E-hard' label. Same color and description
[dryrun] ✅ Skipping update for 'E-help-wanted' label. Same color and description
[dryrun] ✅ Skipping update for 'E-needs-test' label. Same color and description
[dryrun] ✅ Skipping update for 'F-ASCII' label. Same color and description
[dryrun] ✅ Skipping update for 'F-full' label. Same color and description
[dryrun] ✅ Skipping update for 'F-Lithuanian' label. Same color and description
[dryrun] ✅ Skipping update for 'F-simple' label. Same color and description
[dryrun] ✅ Skipping update for 'F-Turkic' label. Same color and description
[dryrun] ✅ Skipping update for 'O-linux' label. Same color and description
[dryrun] ✅ Skipping update for 'O-macOS' label. Same color and description
[dryrun] ✅ Skipping update for 'O-wasm-emscripten' label. Same color and description
[dryrun] ✅ Skipping update for 'O-wasm-unknown' label. Same color and description
[dryrun] ✅ Skipping update for 'O-windows' label. Same color and description
[dryrun] ✅ Skipping update for 'S-archive' label. Same color and description
[dryrun] ✅ Skipping update for 'S-blocked' label. Same color and description
[dryrun] ✅ Skipping update for 'S-do-not-merge' label. Same color and description
[dryrun] ✅ Skipping update for 'S-duplicate' label. Same color and description
[dryrun] ✅ Skipping update for 'S-invalid' label. Same color and description
[dryrun] ✅ Skipping update for 'S-postponed' label. Same color and description
[dryrun] ✅ Skipping update for 'S-speculative' label. Same color and description
[dryrun] ✅ Skipping update for 'S-stale' label. Same color and description
[dryrun] ✅ Skipping update for 'S-wip' label. Same color and description
[dryrun] ✅ Skipping update for 'S-wontfix' label. Same color and description