Cannot create demo environment in MacOS

I cloned the git repository, but when I do "vagrant up" I get the errors below:
vagrant up
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 0 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 1 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 2 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 3 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 4 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 5 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 6 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 7 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 8 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 9 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 10 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: wrong element type String at 11 (expected array)
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: ignoring wrong elements is deprecated, remove them explicitly
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:9: warning: this causes ArgumentError in the next release
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'minion1' up with 'virtualbox' provider...
Bringing machine 'minion2' up with 'virtualbox' provider...
==> master: Box 'ubuntu/trusty64' could not be found. Attempting to find and install...
master: Box Provider: virtualbox
master: Box Version: >= 0
The box 'ubuntu/trusty64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
vagrant login. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://atlas.hashicorp.com/ubuntu/trusty64"]
Error:

This issue was happening when using the latest version of vagrant (1.8.7). I removed that version, then installed version 1.8.6 and the salt demo worked just fine then.


[Feature Request] Rule Based request labeling to define multi-tenancy

Is your feature request related to a problem? Please describe
Currently there is no mechanism to label/classify the incoming requests into tenants. There is an RFC open for defining the multi-tenancy in OpenSearch. We should provide a way to translate request's implicit/explicit attributes into tenants. Currently we are working on query sandboxing which can leverage this but this is not limited to this feature only and can be easily leveraged for both the indexing as well as search workloads.
Describe the solution you'd like
Rule Based Labeling
We will enable admin users to define rules to translate requests into output tokens which can be interpreted as tenants for consuming features. These rules can leverage implicit|explicit attributes to define the tenants. The output tokens will be propagated via ThreadContext or can be consumed into the feature directly as return values.
Implicit attributes could be anything like

LoggedIn entity
Indices

Explicit Attributes

custom tags

I am skipping over the authN/authZ part for explicit attributes since that is something which should be handled at the security layer as discussed in the parent RFC
What will a Rule look like ?
{
    "Input": {
        "attr1": ["val1", "val2*"],
        "attr2": ["xyz", "xyz*"]
        .....
    },
    "Output": {
        "field1": "value",
        "field2": "value",
        ....
    }
}

What if multiple rules matches for a request, how to resolve these conflicts ?
Only one Rule should apply for a request. To avoid such conflicts we will ensure that no two rules are overlapping. But doing this will not ensure that the rukes doesn't overlap. We still need to come up with precedence of attributes.
Now the precedence of attributes needs to be tackled for both the supported type of attributes.

Implicit Attributes: For these attributes we can define the precedence based on the request type, if the request is co-ordinator level then give priority to loggedInEntity attribute and if the request is shard level we can give priority to index attribute.
Explicit Attributes: For explicit attributes It will be hard to enforce precedence sicne the we don't know what all attributes could be used as explicit attributes for all the users beforehand. Since this will vary from user to user, It is more suitable for users to define such order. Now we can provide users with two ways of giving this input.

as part of request (QueryParam): something like _search?precedence="attr1>attr2"
define it as part of config to be stored somewhere else

Related component
Other
Describe alternatives you've considered
No response
Additional context
No response

[Triage - attendees 1 2 3 4 5]
@kaushalmahi12 Thanks for creating this issue


Improve dashboard for mobile devices

The error list page was not pretty on mobile. The error detail page was OK. This fixes the error list on mobile and closes #105

Before

After

I ran mix assets.build and somehow the JS file now has 6k new lines.


community[minor]: Add support for Azure Cosmos DB vector store

This PR adds integration of Azure Cosmos DB Vector Store (fixes issue #1449).
I tried to keep it as close as possible to the Python integration: https://github.com/langchain-ai/langchain/blob/master/libs/community/langchain_community/vectorstores/azure_cosmos_db.py
Integration and examples tests were run successfully.
EDIT: Added unit tests and fixed docs in a few places.

This is fantastic! Thank you!


Account for advertised resources in AWS

For non-AWS zones, the only change is that it now uses <resources> syntax rather than flavor.
For AWS zones it will now ask for more memory to compensate for VESPA-16259 and use 2 vCPU as there is no AWS instance type that we support that has 1 vCPU and 4 or 8 GB.

FYI: @jonmv


fix: issue #14 - form

@Oluwasetemi and @Stan015 The code under the 'Validation using Libraries' and 'React Hook Form' sections is too lengthy for each slide. Would it be better to host the code on StackBlitz and include a link in the slides instead?

@victorvictoria-maker yes you can use an iframe to insert a online IDE, page 14 and 15 for a working example of layout of iframe

@Stan015 React 19 new features regarding forms have been added.


Remove redundant Ord (GenTxId blk) constraint from Mempool.Impl

This constraint was most likely introduced in order to add these to a Map,
but if I remember correctly, that's no longer the plan.
By removing this redundant constraint here, it won't pop up in other places,
e.g., RunDemo.

bors r+

bors r+


Add revisionHistoryLimit config option to the default controller enricher.

if we don't specify a limit then folks RS's soon populate with every version ever of a Deployment which can be noisy and painful. Unless users specify something we maybe should pick a sensible default?

Let's make it configurable, and use a default of 2. If set to 0 then no revisionHistoryLimit should be added.

Closing because of @rohanKanojia comment.


Failed to create aliyunecs instance

I tried to create a aliyunecs instance with the aliyunecs driver but without any success.
I set these environment variables first:
export ECS_ACCESS_KEY_ID=xxxx
export ECS_ACCESS_KEY_SECRET=xxxx
export ECS_REGION=cn-beijing
export ECS_SSH_PASSWORD=xxxx
export ECS_INTERNET_MAX_BANDWIDTH=100
export ECS_SECURITY_GROUP=fully-open
export MACHINE_DOCKER_INSTALL_URL=http://acs-public-mirror.oss-cn-hangzhou.aliyuncs.com/docker-engine/internet

The security group, fully-open, is just fully open policy, allow any incoming connections.
And then, I run the following command to create the docker host:
docker-machine create -d aliyunecs --engine-registry-mirror https://xxxx.mirror.aliyuncs.com node-1

However, it stalled at Uploading SSH keypair every time. Here is the output:
Running pre-create checks...
Creating machine...
(node-1) node-1 | Creating key pair for instance ...
(node-1) node-1 | Configuring security groups instance ...
(node-1) node-1 | Creating instance with image ubuntu1404_64_20G_aliaegis_20150325.vhd ...
(node-1) node-1 | Create instance i-25d5tjo9b successfully
(node-1) node-1 | Allocate publice IP address <IP_ADDRESS> for instance i-25d5tjo9b successfully
(node-1) node-1 | Starting instance i-25d5tjo9b ...
(node-1) node-1 | Start instance i-25d5tjo9b successfully
(node-1) node-1 | Waiting SSH service <IP_ADDRESS>:22 is ready to connect ...
(node-1) node-1 | Uploading SSH keypair to <IP_ADDRESS>:22 ...

It just stay there forever, I even waited for several hours with no luck. And there is no error, so I don't know what's going on.
I tried to ssh the instance manually with the password set in the above environment variables, it's fine. So the instance created correctly, ssh connection is ok.
My docker version is 1.12.0:
$ docker version
Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:04:48 2016
 OS/Arch:      darwin/amd64
 Experimental: true

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:04:48 2016
 OS/Arch:      linux/amd64
 Experimental: true

My docker machine version is 0.8.0:
$ docker-machine version
docker-machine version 0.8.0, build b85aac1

I cannot reproduce the problem. Can you try again with debug mode? Then we can have more information for where the problem is.
export DEBUG=true
Thank you

I'm not sure whether it's GFW related problem. I tried to reproduce the problem this morning with export DEBUG=true, I got 2 failed, one partially failed, but with different errors.
Here is the first attempt:
$ docker-machine create -d aliyunecs --engine-registry-mirror https://xxxx.mirror.aliyuncs.com node-1
Running pre-create checks...
Creating machine...
(node-1) node-1 | Creating key pair for instance ...
(node-1) node-1 | Configuring security groups instance ...
(node-1) node-1 | Creating instance with image ubuntu1404_64_20G_aliaegis_20150325.vhd ...
Error creating machine: Error in driver during machine creation: node-1 | Failed to create instance: Aliyun API Error: RequestId:  Status Code: -1 Code: AliyunGoClientFailure Message: Get https://ecs.aliyuncs.com?AccessKeyId=xxx&Action=CreateInstance&ClientToken=elMy_418cuCMsr09FvQY_6fZgwaNpp6o&Format=JSON&ImageId=ubuntu1404_64_20G_aliaegis_20150325.vhd&InstanceName=node-1&InstanceType=ecs.t1.small&InternetChargeType=PayByTraffic&InternetMaxBandwidthOut=100&IoOptimized=none&Password=xxx&RegionId=cn-beijing&SecurityGroupId=sg-25qocfpse&SignatureMethod=HMAC-SHA1&SignatureNonce=8BJvDbrq_qZlc44BXplTueUpd3Xk994T&SignatureVersion=1.0&Timestamp=2016-08-10T01%3A28%3A15Z&Version=2014-05-26&Signature=6DvfsB76ZmH904CM55ti08uo38E%3D: net/http: TLS handshake timeout

I checked on the Aliyun Control Panel, the first attempt failed to create any instance on Aliyun ECS.
Here is a second one:
$ docker-machine create -d aliyunecs --engine-registry-mirror https://xxxx.mirror.aliyuncs.com node-2
Running pre-create checks...
Creating machine...
(node-2) node-2 | Creating key pair for instance ...
(node-2) node-2 | Configuring security groups instance ...
(node-2) node-2 | Creating instance with image ubuntu1404_64_20G_aliaegis_20150325.vhd ...
Error creating machine: Error in driver during machine creation: node-2 | Failed to create instance: Aliyun API Error: RequestId:  Status Code: -1 Code: AliyunGoClientFailure Message: Get https://ecs.aliyuncs.com?AccessKeyId=xxx&Action=CreateInstance&ClientToken=rydzLrhiG07nZ1iaitA11O_rIftB3VIM&Format=JSON&ImageId=ubuntu1404_64_20G_aliaegis_20150325.vhd&InstanceName=node-2&InstanceType=ecs.t1.small&InternetChargeType=PayByTraffic&InternetMaxBandwidthOut=100&IoOptimized=none&Password=xxx&RegionId=cn-beijing&SecurityGroupId=sg-25jybstpe&SignatureMethod=HMAC-SHA1&SignatureNonce=PVw5PIqW9RAl4QD7GWmfXRKS8bBYhRnW&SignatureVersion=1.0&Timestamp=2016-08-10T01%3A29%3A52Z&Version=2014-05-26&Signature=c%2FxO%2Fz0hi8Wqks2DSniABDFizKQ%3D: read tcp <IP_ADDRESS>:49398-><IP_ADDRESS>:443: read: operation timed out

The second attempt actually create a Aliyun ECS instance, but the status is not running.
Here is the third one:
$ docker-machine create -d aliyunecs  node-3
Running pre-create checks...
Creating machine...
(node-3) node-3 | Creating key pair for instance ...
(node-3) node-3 | Configuring security groups instance ...
(node-3) node-3 | Creating instance with image ubuntu1404_64_20G_aliaegis_20150325.vhd ...
(node-3) node-3 | Create instance i-25f8i5y2t successfully
(node-3) node-3 | Allocate publice IP address <IP_ADDRESS> for instance i-25f8i5y2t successfully
(node-3) node-3 | Starting instance i-25f8i5y2t ...
(node-3) node-3 | Start instance i-25f8i5y2t successfully
(node-3) node-3 | Waiting SSH service <IP_ADDRESS>:22 is ready to connect ...
(node-3) node-3 | Uploading SSH keypair to <IP_ADDRESS>:22 ...
(node-3) node-3 | Created instance i-25f8i5y2t successfully with public IP address <IP_ADDRESS> and private IP address <IP_ADDRESS>
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(upstart)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "<IP_ADDRESS>:2376": tls: DialWithDialer timed out
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

The third attempt actually create a working docker host, I can docker-machine ssh node-3, and operate Docker from there.
SSH Key, TLS handshake, tls timed out, these patterns are very similar to the situation the GFW show its existence.
Beside my local network, I also tried to do the same on Digital Ocean droplet, without any luck. Could you give the aliyunecs driver a try from any server outside of the China mainland? Thanks.

@twang2218 我在国内网络环境测试了一下，暂未发现问题。所以判断应该是由于GFW导致的。我找个国外的环境试一下。

@twang2218 你可以尝试使用一下美西Region的机器

@twang2218 由于你在国外，所以你无需指定使用阿里云的mirror和镜像地址。你可以不去指定MACHINE_DOCKER_INSTALL_URL 和 --engine-registry-mirror 参数

我关闭这个issue了。因为多次测试之后，发现如果使用SFO（西海岸）的Digital Ocean服务器，创建北京地区阿里云服务器，成功几率大了很多。那很可能这个问题是伟大的墙所致。
@menglingwei 我创建的的是北京地区的阿里云服务器，那可是必须要配 MACHINE_DOCKER_INSTALL_URL 和 --engine-registry-mirror 的。

Thanks for update.


Gradle changes proposal for installer and AppCDS

Proposal (paths need to be replaced by variables later):
Directories on the brick:

/home/robot/ - location for user JAR wrappers.
/home/robot/java/programs/ - location for user JARs.
/home/robot/java/libraries/ - location for ev3dev-lang-java JARs.
/home/robot/java/modules/ - location for future ev3dev-lang-java JMODs.
/home/robot/java/appcds - location for AppCDS caches

New/changed Gradle tasks:

Integrating installer.sh in Gradle:

java installer - install jri-11-ev3 or openjdk-11-jre-headless
native library installer - install librxtx-java and libopencv2.4-java

Small JARs

ev3dev-lang-java installer - installs maven/another JARs to /home/robot/java/libraries and eventually /home/robot/java/modules
manifest creation for user JARs - the libraries should not be included in the JAR, they should be picking them from the system, i.e. /usr/share/java and /home/robot/java/libraries
user JAR uploader

uploads JARs to /home/robot/java/programs
creates a non-appcds shell script wrapper in /home/robot/

AppCDS support

user JAR uploader+optimizer

deletes appropriate cache files in /home/robot/java/appcds
uploads JARs to /home/robot/java/programs
creates an appcds-aware shell script wrapper in /home/robot/
and then two situations are possible

AppCDS is refreshed on the first startup

the script wrapper will generate the class list and dump the classes

AppCDS is refreshed on upload

a helper script called from Gradle will generate class list from specified sources and then immediately generate the AppCDS cache

JRI class list
ev3dev-lang-java libraries class list
user program class list

We can alternatively integrate it into the IDE plugin, but I think that even command-line users should have a chance to work with this.

Don't worry for the plugin, we have to wait for the initiative of the community. It will take some months.
The folder design is Ok. Maybe we could start without the AppCDS, only the local libraries and later add that support in another iteration. For OpenCV, if you like, try to experiment in your side. For me, it is not working in EV3Dev Stretch. Try in you case to see my point of view to take the control.
For the modules support, I think that in another iteration.
The quick win, is the installation from installer the main libraries included ev3dev-lang-java
This idea is related to this issue:
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/583
We could use your folder structure: /home/robot/java/libraries/ and use it for the execution.
We could have 2 ways to deploy: FatJar or Fast. The fast requires a previous installation of classic libraries.
For AppCDS, we could create a list of classes per jar and later copy to the brick and execute the statement to cache. the .lst should include: jdk, ev3dev-lang-java, etc... we should create a small POC with 2 libraries and check benefits. With this feature with get from the JVM the maximum performance but I am not sure if many people will use. If you use BrickPi3 + RaspberryPi 3 Model B+, the execution is immediate without any optimisation except the initial -Xshare:dump but I didn't enable in template project. (This another issue, I will create tomorrow to get 1 second with no effort)
The fast deployment is interesting, is a quick win for EV3.

Review of current solution:

Integrating installer.sh in Gradle:

java installer - this would call installer.sh java (already done)
native library installer - this would call installer.sh libs (new)

Small JARs

ev3dev-lang-java installer - we can iterate over the externalJars in project.ext and upload them to the library directory on the brick
manifest creation for user JARs - this will not be needed, arguments will be supplied at run time - mainClass property of project.ext
user JAR uploader/wrapper generator - launcher-simple.sh.template can be expanded with variables in project.ext and uploaded to the brick.

Delivered.


How do I use Speaker ID?

In PiperLib.cs I can see "public OptionalLong speakerId;" but I can't find any way to use it for multi-speaker voices.

Oh, sorry, I can't really tell you what exactly this is, it's not clear from original code how this is supposed to work, I added this just for compatibility. I guess the answers are around here
Try to look for answers in the original lib docs or sources
https://github.com/rhasspy/piper


More appealing empty history screen

What

Just this small centered text doesn't look friendly for someone who opened the app for the first time
From the mocks:

I want to work on this but I'm confused about the text that should be displayed in place of the current text.

@bhattabhi013 Don't worry: just put a large icon, a bold title and a subtitle similar to what is displayed in the mock.
Then we may fine-tune.

Can I work on this issue? :)

@bhattabhi013 Have you already started something?

Hi @monsieurtanuki
Yes, I've started working on it and will be submitting PR for the same.

Just a remark: it's very tempting, when on the empty history page, to click on the big central icon to start scanning. But nothing happens.


Enabled disabled translation

I'm happy to do it, just could you tell me how? I'm not very proficient in github.

I added it manually. But I only translated in pl .

Something must have been very confused because I only added the translation of the word Yes. I'm about to see through it.

Ok, corrected.


Revert "bug fixes (#26)"

This reverts commit 3d3c8751e1c93cf1fce0c772afdd5ac18659d28a.
Slow load times - need to F5 to get site to come up.
Possible import vs require issue happening.
Ref: #26

Landing to unblock website not loading.


remove use log of log4j v1

Fixes #12425.
Description
log4j v1 is end of life and full of security issues
indexing-hadoop/pom.xml
extensions-core/hdfs-storage/pom.xml
remove log4j v1 dependences
Fixed the bug to remove log4j v1
Release note
remove log4j v1 dependences

Key changed/added classes in this PR

pom.xml

This PR has:

[x] been self-reviewed.
[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

@FrankChen021 thanks for help for reviewing when you have time.
There is one integration test failed(integration-index-tests-indexer (kafka-index)), which is not related to the modification from the log
ERROR: listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: read unix @->/run/docker.sock: use of closed network connection"
Error:  Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:1000)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:947)
    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:471)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)

@AlbericByte Can you please test a druid build with HDFS storage and see if this patch does not break logging.

@cryptoe  Thanks for your time and suggestion.
I have tested using following command, and it can build successfully
Does it meet your suggestion. if not, could you help provide more detail.
mvn clean install \
     -Pintegration-tests,skip-static-checks,skip-tests \
     -Ddocker.run.skip=true \
     -Ddocker.build.hadoop=true

I think @cryptoe meant to ask if the change is manually verified with HDFS as deep storage.

@abhishekagarwal87 and @cryptoe
Sorry for late, this is my first time to setup druid-hdfs-storage, i have launch a HADOOP docker environment, and test it work as expected, for example: the index log can be write to the HDFS as following:
druid_indexer_logs_type=hdfs
druid_indexer_logs_directory=hdfs://namenode:8020/drui/indexing-logs


Error when using MSSQL

When I use the default sqlite connection the app loads fine but when I change it to us MSSQL connection I get the below Error:
[12:28:05 ERR ] Unhandled exception in circuit 'MHOaaQdplW_43aYvTPib5ud-AZnwHOJp5N1nyR8CyrA'.
System.AggregateException: One or more errors occurred. (Sequence contains no elements.)
---> System.InvalidOperationException: Sequence contains no elements.
at Fluxor.Blazor.Web.StoreInitializer.OnAfterRender(Boolean firstRender) in C:\Data\Mine\Code\Fluxor\Source\Lib\Fluxor.Blazor.Web\StoreInitializer.cs:line 57

@neozhu When you have time, can you take a look at this? I don't have a Microsoft SQL Server database set up at the moment.

@dmarshall4466
please clear local storage in the browser first. F12-> application -> Local Storage

Thanks @neozhu, sorry I thought it was an issue with Fluxor.
Also, I just wanted to say this is a great project which I'm sure will help alot of people, great work :)
One thing that would be helpful would be if you could provide info on how to create a template from your solution, I've managed to do it with template.json but I'm having to rename all of the namespaces each time for Application, Domain, Infrastructure and Blazor.UI.Server + test projects.

@dmarshall4466
I suggest trying the method that worked for me. The reason for the issue you encountered might be due to the fact that different databases generate different JWT Tokens, which are not interchangeable. Therefore, you may need to delete the existing token and log in again.

As for creating a Visual Studio .NET project template, I'm not an expert in that area, so I'm not sure if I can be of much help. However, I recommend looking into the template.json file and renaming the namespaces for the Application, Domain, Infrastructure, and Blazor.UI.Server + test projects. This should help you create a template that suits your needs.

Thanks @neozhu, sorry I thought it was an issue with Fluxor.
Also, I just wanted to say this is a great project which I'm sure will help alot of people, great work :)
One thing that would be helpful would be if you could provide info on how to create a template from your solution, I've managed to do it with template.json but I'm having to rename all of the namespaces each time for Application, Domain, Infrastructure and Blazor.UI.Server + test projects.

We greatly improved being able to use our template. You can find the updated documentation in the README!
See #428


every second: Possible Tor bug, or possible attack if very frequent: Got 1 dropped cell on circ 17 (in state CONFLUX_LINKED None; old state CONFLUX_UNLINKED None)

This messages comes every second in journal.

Oct 21 15:39:40 host vanguards[988]: WARNING[Sat Oct 21 15:39:40 2023]: Possible Tor bug, or possible attack if very frequent: Got 1 dropped cell on circ 17 (in state CONFLUX_LINKED None; old state CONFLUX_UNLINKED None)

Debian 12 bookworm
tor stable Debian package <IP_ADDRESS> from deb.torproject.org.
vanguards package from from packages.debian.org.

This should be fixed in https://gitlab.torproject.org/tpo/core/tor/-/issues/40878. It was backported to 0.4.8; will be in the next 0.4.8 release

This issue is still reproducible with the updated Tor version.
dpkg -l | grep tor

<IP_ADDRESS>-1~d12.bookworm+1

From deb.torproject.org.

Correction: Actually not happening anymore every second.
This was fixed.
Thank you!


Remove Tsagu Language from the GUMBASI Cluster

See user detail: https://github.com/SeedCompany/management/issues/9

Done.


[Go Live][Feb 18]

Docs Build status updates of commit aaa8d44:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/teams-validation-developer-portal.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


adult VNC motor neuron papers

Azevedo et al. (2024)
https://www.nature.com/articles/s41586-024-07600-z
Lesser et al. (2024)
https://www.nature.com/articles/s41586-024-07389-x

Azevedo et al. (2024) is published version of an already-curated preprint
Lesser et al. (2024) is predominantly connectivity analysis (no anatomy to curate)


Incompatible types between citations and classifieds

ERROR:  Citation IntensiveCare has type EnterpriseFunction but its classified BbExecutionOfDiagnosticTherapeuticAndNursingProcedures is in catalogue WhoDhiHealthSystemManagerFeatureCatalogue with type Feature.

The check query seems to be wrong, hito:BbExecutionOfDiagnosticTherapeuticAndNursingProcedures actually is in hito:BbFunctionCatalogue.

ERROR:  Citation InvoicingPatients has type EnterpriseFunction but its classified WhoDhiClientFinancialTransactions is in catalogue WhoDhiClientFeatureCatalogue with type Feature.
InvoicingPatients seems to exist multiple times, split the resource using the spreadsheet for CSV2RDF.

The splitting was already implemented in CSV2RDF and just needed to be called.
However there was a single invalid GNU Health function citation to feature catalogue reference that was removed.
See https://github.com/hitontology/csv2rdf/commit/d6b462f7f62d793716618438cc81331f216656e3 and https://github.com/hitontology/ontology/commit/d487ce0f950327e980360ef50c67cc96b2d0166e.


header and footer functionality of latest release (marp-cli)

It seems that with the newest release of marp-cli, the header and footer functionality contains some incompatibilities. Regular text is shown as expected, but as soon as you use bold text or include images, the respective html code is shown, on both, html and PDF slides.
in markdown:
---
header: "**bold** _test_"
footer: "![image](localimage.png)  footer title"
theme: base
---

on the slide:
bold test
...

 footer line

Thanks !

Maybe it caused by the update of marp-core v0.0.5. (marp-team/marp-core#26)
Header and footer are defined as HTML block in the Marpit framework, so these elements might be sanitized unintentionally.

Ready to use the updated @marp-team/marp-cli v0.0.7, it has included upgrades about the framework (Marpit v0.0.15) and core (marp-core 0.0.6).

:+1:


Make build pipeline parallel

Using the matrix lets the build pipeline in parallel, see my test run: https://github.com/cwansart/microjpa/runs/1995105308
This may speed up the build.

Or for this run: https://github.com/ArneLimburg/microjpa/runs/1995113470
You can see both parallel runs on the left.

Great addition, but would you please then change the name of the step from "Test with OpenWebBeans" to "Test" or something similar?

Also could you please update deploy.yaml accordingly? I guess we would do the sonar publishing in a separate step then.

Good point. I fixed the step name. I also tried to add the profile matrix to the deploy pipeline. I am not 100 % sure if this works. But if the artifacts remain this should work.


Fix required validator and add tests

Coverage increased (+0.0%) to 99.72% when pulling f632c9aa60c3afb73acf9141297c19931a1f83fb on dnephin:fix_validation_bug into d47dfd9b6dbb728f2ccb67c53c01c61b9ae135b3 on striglia:master.

Coverage increased (+0.0%) to 99.72% when pulling f632c9aa60c3afb73acf9141297c19931a1f83fb on dnephin:fix_validation_bug into d47dfd9b6dbb728f2ccb67c53c01c61b9ae135b3 on striglia:master.

Coverage increased (+0.0%) to 99.72% when pulling f632c9aa60c3afb73acf9141297c19931a1f83fb on dnephin:fix_validation_bug into d47dfd9b6dbb728f2ccb67c53c01c61b9ae135b3 on striglia:master.


NPC doesn't avoid danger, keeps teleporting or stops responding.

The output of command /version on my server is: Paper version git-Paper-550 (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 483368e on ver/1.19.4)
The output of command /version citizens on my server is: 2.0.32-SNAPSHOT Build 3188
The output of command /version sentinel on my server is: 2.8.0-SNAPSHOT Build 508
A pastebin.com link to my (full!) Sentinel/config.yml file is: https://pastebin.com/RQM1YkKZ
My NPC stopped avoiding any added entity. It doesn't run away or anything. It only punches if gets too close (sometimes).
If NPC follows player or tries to reach target (by following or by attacking) it teleports or randomly stops moving.
(Link to NPC config: https://pastebin.com/SXbyqU4P)

Please use the #sentinel channel on Discord @ https://discord.gg/Q6pZGSR


Rename level_size to level_width

Closes #258

Codecov Report

Merging #263 (d72edc8) into main (6ad74b3) will not change coverage.
The diff coverage is 100.000%.

@@            Coverage Diff            @@
##              main      #263   +/-   ##
=========================================
  Coverage   96.990%   96.990%
=========================================
  Files           55        55
  Lines         2724      2724
=========================================
  Hits          2642      2642
  Misses          82        82

Impacted Files
Coverage Δ

src/adiar/data.h
100.000% <ø> (ø)

src/adiar/data.cpp
97.740% <100.000%> (ø)

src/adiar/internal/pred.cpp
100.000% <100.000%> (ø)

src/adiar/internal/reduce.h
99.200% <100.000%> (ø)

Continue to review full report at Codecov.

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


[chore] "role-based access control" to the Vale at Red Hat case-sensitive rules

The security term "role-based access control (RBAC) " is often incorrectly capitalized, especially in raw developer docs that Red Hat writers edit and polish.
Add the term in the form bad: good to the .vale/fixtures/RedHat/CaseSensitiveTerms.yml rule.
Update the test fixtures:
.vale/fixtures/RedHat/CaseSensitiveTerms/testinvalid.adoc
.vale/fixtures/RedHat/CaseSensitiveTerms/testvalid.adoc
Use ...
Role Based Access Control | Role-Based Access Control| role based access control : [rR]ole-based access control
PR must be reviewed and all tests must pass before merging.

Please assign this issue to me.


refactor(expr): support variadic function in #[function] macro

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
This PR adds variadic support to #[function] macro.
#[function("array(...) -> list")]
fn array(row: impl Row) -> ListValue {
    ListValue::new(row.iter().map(|d| d.to_owned_datum()).collect())
}

Then we migrate the following functions using the macro:

array
row
concat_ws
format

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[x] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
format() function now support variable inputs.

Others LGTM


General Issue: Move any test data in {admiralonco} to {admiraldata}

Background Information

Prefix: admiralonco_<dataset>.
{admiralonco} contacts: Hinal Patel, @HinalPat, Stefan Bundfuss (@bundfussr)

Definition of Done

ADaM contents of data folder of {admiralonco}, as well as any relevant files in dev folder in copied over to same locations in {admiraldata}.
New datasets catalogued in data.R.

Hi @HinalPat @bundfussr , could you help check which ones should be copied from {admiralonco}? thanks!
There are one dataset admiral_adrs.rda and three programs for generating datasets.
R
└── data.R  #1 dataset
data
└── admiral_adrs.rda
inst
└── templates
    ├── ad_adrs.R         # tempdir()
    ├── ad_adtr.R         # not saved
    └── ad_adtte.R        # tempdir()

keep admiral_adrs.rda, rename to admiralonco_adrs.rda


E3002 Invalid Property Resources/CfnVpcEndPoint/Properties/VpcEndpointType

*cfn-lint version: 0.7.1
Description of issue.
The following fails with invalid property VpcEndpointType, however it creates the resource OK if I comment out the linter:
CfnVpcEndPoint:
Type: AWS::EC2::VPCEndpoint
Condition: IsDevOrProd
Properties:
VpcId: !FindInMap [NetworkMap, !Ref EnvironmentType, "Vpc"]
ServiceName: "com.amazonaws.eu-west-1.cloudformation"
VpcEndpointType: "Interface"
From the docs:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-vpcendpoint.html#cfn-ec2-vpcendpoint-vpcendpointtype

Hey, thanks for reaching out!
There's a discrepancy in the CloudFormation resource specification for the VpcEndpoint for both VpcEndpointType and PrivateDnsEnabled that I'm working with the service team to try to address. You can track this work in #219.
I'm closing this issue as a duplicate.


Minor Typo in Help Dialog

https://github.com/kgretzky/evilginx2/blob/218df95a3f81981ac03c2dc6817b6a76c4ec2e38/core/terminal.go#L489
Before I make the edit, that should be phishlets not phishlet correct?

Yes, it should be phishlets in the command suggestion


Update standard flow library to use beta_dependencies everywhere prior to ci_master

See internal Quip doc "RFC: Beta Dependencies Everywhere".
Critical Changes

The flows dev_org, dev_org_namespaced, qa_org, ci_feature, and install_beta now use beta dependencies by default.
The flows ci_feature_beta_deps and dev_org_beta_deps are now deprecated and should be replaced by their default equivalents above.

Changes
Issues Closed

Instead of using the beta_dependencies flow, I wonder if we should use the dependencies flow with an option override:

@davisagli  I like this idea. Since the options override is so straightforward in project YAML, that makes me think we could go ahead and deprecate the beta_dependencies flow as well.


AZ_BATCH_APP_PACKAGE not invoking

I am trying to invoke one app_package using cmd as below -
string taskCommandLine = string.Format(@"cmd /c %AZ_BATCH_APP_PACKAGE_ffmpeg#4.3%\ffmpeg-4.3-win64-static\bin\ffmpeg.exe -i {0} {1}", inputMediaFile, outputMediaFile);
But getting - "system cannot find the path specified"
I am referring to this doc - https://github.com/Azure-Samples/batch-dotnet-ffmpeg-tutorial
Please help.
Note - I have updated the ffmpeg version from 3.4 to 4.3. thank you.

@shawon017 I suggest you to please open an issue on the mentioned sample repository as this issue is not related to Microsoft documentation.

But can you do some help? Just stuck only that point. APP_PACKAGE is not executing, oother than that everything is working.

@VikasPullagura-MSFT Are you able to help on this issue ?

@shawon017 Apologies in delayed response.
I would recommend to open a support case to get this issue checked.


Fastboot support

Hi,
This is my example to integrate this awesome addon with fastboot, what do you think?

Hey @marucjmar, thanks so much for getting this going! I haven't had  a chance to give it a full review yet, but I did notice that there are some tests broken (here for example). Can you see if you can fix those before we move forward with this PR?

@marucjmar noticed that the tests appear to be broken for everything right now. I'll fix that on master and let you know when to rebase.

ok, #43 was merged to fix the tests on master and update ember versions. Can you rebase on that and force push? Thanks

Ok,
Done

@bgentry you can merge this feature? It's very important, I also think it's worth releasing a release for this fastboot support

I just merged #59 to switch to ember-fetch. Is that actually all that's necessary for Fastboot support?

#59 was included in v0.5.0, I believe.
On Tue, Oct 10, 2017 at 3:56 PM Vinícius Sales<EMAIL_ADDRESS>wrote:

@viniciussbs commented on this pull request.
In addon/utils/fetch-network-interface.js
https://github.com/bgentry/ember-apollo-client/pull/42#discussion_r143874595
:

   method: 'POST',

   body: JSON.stringify({variables, query}),

   ...options,

   headers: {

     Accept: '*/*',

     'Content-Type': 'application/json',

     ...options.headers

   }

 }).then((response) =>{

   resolve(response);

 }).catch((response) =>{

   reject(response);

 })

});
}
+}

@balaf https://github.com/balaf Looks like whatwg-fetch does nothing if
there's a global fetch
https://github.com/github/fetch/blob/master/fetch.js#L4-L6, so
ember-fetch might do the trick if loaded beforehand. It's a matter of
testing the new version of ember-apollo-client now that #59
https://github.com/bgentry/ember-apollo-client/pull/59 is merged.
Who volunteers to write a Fastboot compatible app to fetch data from a public
GraphQL API
https://github.com/APIs-guru/graphql-apis#demonstration-only-apis?
@bgentry https://github.com/bgentry #59
https://github.com/bgentry/ember-apollo-client/pull/59 was released or
it's only on master?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bgentry/ember-apollo-client/pull/42#discussion_r143874595,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG9cVYu-CcprZXfEFENsnPvAFdeCm0zks5sq_YNgaJpZM4PDyBF
.

I'm closing this PR because AFAIK it doesn't add anything that we need after #59. If Fastboot is not working on the latest releases, please open an issue. A fastboot-enabled demo app would also make this a lot easier to verify ( #62 ) or perhaps there are some automated tests that can be added for this functionality?