Setup guide for windows operating system

To describe the step-by-step explanation to run the project on Windows operating system.
Please do assign me under LGMSOC'21. @avinashupadhya99
Thank You.
** Solution (if required)

How to setup Docker(specifically for Home edition and Pro edition)
npm commands
specify API Keys if needed

Hey, the backend is not yet setup to have such a solution. If you're interested, I can walk you through what the backend does and it is supposed to do and you could work on that. I'll close this issue for now. Let me know if you're interested in working on the backend.


For enterprise TP, edit statements in Client Dev guide that imply product support

@roldanbob @rareddy is there a set of style guidelines that we should be aware of?  We routinely have used the word support in regards to provided functionality.

Because the product release of DV will be TP, legally we must refrain from making any statement that would imply that customers are entitled to receiving customer support in the even that something doesn't work.


MINOR: Add integration test for plugin aliases

Follow-up to https://github.com/apache/kafka/pull/16608, discussed here and here.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

The changes in the latest commit are trivial, the build passes locally, and CI indicates that the prior commit is healthy. Merging...


Cannot Install on Debian

The install instructions for Debian are now outdated. Can you please update the instructions, or at the very least provide a 64-bit static binary for linux?

Seems this project is abandoned. Tried several linux distributions - no luck everywhere except Arch

No. I've made several successful installations recently and I've shared my experiences in this forum.

Not abandoned. I'm kickstarting development up again this weekend. Plans are to focus on things that involve building and distribution: rebuild for Windows, update the Arch PKGBUILD, figure out what the deal is with Mac/Homebrew, update installation docs and so on. Updating Ubuntu/Debian install instructions will come later because I don't have easy access to those platforms just yet.

That's great news. I'm running Gentoo and it would be great to get butterflow working on some of my projects.

Any updates yet? What about? https://github.com/dthpham/butterflow/issues/48


Collapse and combine GTEx TPM and expected_count to KFDRC collapsed RSEM files

Background:
For OT we will need each data release to included  processed GTEx v8 data in gene-expression-rsem-tpm-collapsed.rds and gene-counts-rsem-expected_count-collapsed.rds.
In the last data release I did:

script to collapse GTEx  and not removing the genes that are not expressed ie have rowSum ==0
output gtex-gene-expression-rsem-tpm-collapsed.rds
script to collapse PBTA+GMFK merge rsem file and not removing the genes that are not expressed ie have rowSum ==0
output pbta-gmkf-gene-expression-rsem-tpm-collapsed.rds
notebook to combine the two file
output  gene-expression-rsem-tpm-collapsed.rds

Required update
Update the collapse-rnaseq to be able to handle adding GTEx processed files.

GTEx v8 processed files can be downloaded from:
TPM https://storage.googleapis.com/gtex_analysis_v8/rna_seq_data/GTEx_Analysis_2017-06-05_v8_RNASeQCv1.1.9_gene_tpm.gct.gz
expected_count https://storage.googleapis.com/gtex_analysis_v8/rna_seq_data/GTEx_Analysis_2017-06-05_v8_RNASeQCv1.1.9_gene_reads.gct.gz
keep genes with rowSum ==0
combine file filtering for common genes

CC @zhangb1 @yuankunzhu @jharenza  for discussion.

@zhangb1 do you have an eta for this ticket?

@jharenza  can someone from your team take care of the ticket, maybe run?
I really need to focus on the data assembly cwl develop this week.

I don't think she has ec2 access yet and we have a lot of open issues for OT that need to be done as well - @yuankunzhu can someone else help with these upstream processes?

Trying to run locally but have the memory issue. can't process
I need to wrap the cwl and try to run on cavatica project.
the error
➜  GTEx Rscript 00-collapse_matrices.R -i gene-expression-rsem-tpm.rds -g gencode.v27.primary_assembly.annotation.gtf.gz -m gene-expression-rsem-tpm-collapsed.rds -t gene-expression-rsem-tpm-collapsed_table.rds -n GTEx_Analysis_2017-06-05_v8_RNASeQCv1.1.9_gene_tpm.gct.gz
[1] "Generating input matrix and drops table...!"
[1] "Read merged GTEx data"

── Column specification ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
cols(
  .default = col_double(),
  Name = col_character(),
  Description = col_character()
)
ℹ Use `spec()` for the full column specifications.

[1]    95949 killed     Rscript 00-collapse_matrices.R -i gene-expression-rsem-tpm.rds -g  -m  -t  -n

I had to run it on a large EC2, GTEx files are huge

I ran the gtex collapsed data  on cavatica project
here: https://cavatica.sbgenomics.com/u/zhangb1/test-download/tasks/2d842fee-65cf-4c5b-b1aa-0e458b2dfa29/
and I ran the pbta-gmkf-gene-expression-rsem-tpm-collapsed.rds locally.
when I tried to merge the files using the notebook.
> common_genes <- intersect(rownames(gtex),rownames(pbta_gmkf))
> length(common_genes)
[1] 0

the length of the common_genes is 0.
@kgaonkar6 can you take a look?

wait. I think I found the issue. l will check

@jharenza @kgaonkar6
the merged files has been updated in the bucket:
2021-07-21 14:54:03<PHONE_NUMBER> gene-counts-rsem-expected_count-collapsed.rds
2021-07-21 14:28:30<PHONE_NUMBER> gene-expression-rsem-tpm-collapsed.rds

md5 also updated

Thanks a lot @zhangb1 !!
@runjin326  can you try to download these files with the updated download-data.sh pointing to v7 s3 bucket? Since you need for fusion_filteering rerun?

@kgaonkar6, @zhangb1, thanks so much! Yes I have downloaded the data and should be able to re-run fusion_filtering now.

Oh sorry forget to mention, @kgaonkar6  - the md5sum did not match. I am guessing that is because they are updated?

Could you removegene-counts-rsem-expected_count-collapsed.rds and gene-expression-rsem-tpm-collapsed.rds in your local data folder and rerun download-data.sh

Yes. Now it's good!

Closing this as we have this data available in OT.


Mailing list

Zendesk can it be used as a mailing list address

Hey there,
I'm not quite sure what the intent of this issue is, but this is a CLI tool for sending emails from a text file list.


Add incremental proof and improve quality of membership tests in history tree

Codecov Report

Merging #34 into master will increase coverage by 0.68%.
The diff coverage is 92.15%.

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
+ Coverage    74.4%   75.09%   +0.68%
==========================================
  Files          27       27
  Lines        1047     1092      +45
==========================================
+ Hits          779      820      +41
- Misses        226      228       +2
- Partials       42       44       +2

Impacted Files
Coverage Δ

balloon/history/test_helpers.go
41.17% <ø> (+18.09%)
:arrow_up:

balloon/history/incremental.go
100% <100%> (ø)
:arrow_up:

balloon/history/tree.go
78.86% <88.23%> (+2.51%)
:arrow_up:

Continue to review full report at Codecov.

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


update (virtual cluster) validation webhook registration to support admission.../v1

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
I followed the README guide to deploy a virtual cluster on kind (kubernetes v1.24) then rancher RKE (kubernetes version 1.23)
kubectl vc create -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-nested/main/virtualcluster/config/sampleswithspec/virtualcluster_1_nodeport.yaml -o vc-1.kubeconfig
cannot find sts/etcd in ns default-95213e-vc-sample-1: statefulsets.apps "etcd" not found

Logs of the vc-manager pod:
k logs -n vc-manager  pods/vc-manager-6f855758c-cr4gv

{"level":"error","ts":1659554169.9459105,"logger":"entrypoint","msg":"unable to register webhooks to the manager","error":"fail to create validating webhook configuration: no matches for kind \"ValidatingWebhookConfiguration\" in version \"admissionregistration.k8s.io/v1beta1\""}

What did you expect to happen:
A virtual cluster successfully created and kubeconfig output
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

cluster-api-provider-nested version: virtual cluster
Minikube/KIND version: kind
Kubernetes version: (use kubectl version): Major:"1", Minor:"24", GitVersion:"v1.24.3"
OS (e.g. from /etc/os-release): Ubuntu 20.04.4

/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-provider-nested/labels?q=area for the list of labels]

It seems that this issue is already fixed by this commit: https://github.com/kubernetes-sigs/cluster-api-provider-nested/commit/c9cb5b71b29945675e441b38c12b2a24d9bbba29
But image virtualcluster/manager-amd64:latest was not updated. You can build the image on your local machine, and load it to kind.
By the way, is there anyone can help to update the image virtualcluster/manager-amd64:latest to the latest version?

/reopen


Fix query generation bug

For IMetricSpec, name property should always used when querying instead of using field

Introduced by #468


TASK [ceph-validate : validate provided configuration]  fails for osds on stable-3.2

Bug Report
What happened:

vagrant up --provider=virtualbox errors with this:

TASK [ceph-validate : validate provided configuration] *************************
Friday 17 May 2019  13:37:55 -0400 (0:00:00.500)       0:00:26.844 ************
ok: [mon0] => {
"changed": false
}
ok: [mon1] => {
"changed": false
}
ok: [mon2] => {
"changed": false
}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: IndexError: list index out of range
fatal: [osd0]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: IndexError: list index out of range
fatal: [osd1]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: IndexError: list index out of range
fatal: [osd2]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}
ok: [mds0] => {
"changed": false
}
ok: [mds1] => {
"changed": false
}
ok: [client0] => {
"changed": false
}
What you expected to happen:
No errors.
How to reproduce it (minimal and precise):

I cloned ansible 2.6 and checked out branch stable-2.6
I loaded the virtual environment by sourcing ansible-2.6/hacking/env-setup
I cloned ceph-ansible and checked out branch stable-3.2
I did cp site.yml.sample to site.yml
I did cp vagrant_variables.yml.sample to vagrant_variables.yml
I edited vagrant_variables.yml and changed the following:
diff vagrant_variables.yml.sample vagrant_variables.yml
9c9
< mds_vms: 0

mds_vms: 2
13c13
< client_vms: 0

client_vms: 1
30c30
< eth: 'eth1'

eth: 'enp0s8'
56c56
< vagrant_sync_dir: /home/vagrant/sync

vagrant_sync_dir: /home/{ user }/vagrant

I edited: roles/ceph-defaults/defaults/main.yml and changed the following:
-ceph_origin: dummy
+ceph_origin: repository
-ceph_repository: dummy
+ceph_repository: community
-ceph_stable_release: dummy
+ceph_stable_release: mimic

I ran "pip install -r ./requirements.txt" and it worked flawlessly

I ran "vagrant plugin install vagrant-vbguest" and and ran flawlessly

I ran "vagrant up --provider=virtualbox" and got the error in this bug report.

Share your group_vars files, inventory

Haven't changed anything about this manually, so assume default.

Environment:

OS (e.g. from /etc/os-release):
NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

Kernel (e.g. uname -a):
Linux pop-os 5.0.0-15-generic #16pop0-Ubuntu SMP Wed May 15 14:41:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Docker version if applicable (e.g. docker version):

Ansible version (e.g. ansible-playbook --version):
ansible-playbook 2.6.16.post0 (stable-2.6 7a1ccef131) last updated 2019/05/16 15:48:09 (GMT -400)
config file = /home/admin/projects/ceph-ansible/ansible.cfg
configured module search path = [u'/home/admin/projects/ceph-ansible/library']
ansible python module location = /home/admin/projects/ansible-2.6/lib/ansible
executable location = /home/admin/projects/ansible-2.6/bin/ansible-playbook
python version = 2.7.16 (default, Apr  6 2019, 01:42:57) [GCC 8.3.0]

ceph-ansible version (e.g. git head or tag or stable branch):
stable-3.2

Ceph version (e.g. ceph -v):
Trying to use mimic.

vagrant up --provider=virtualbox errors with this:

To be honest I don't know if ceph-ansible is working well with virtualbox provider. Currently we only use the libvirt provider. But the issue could be unrelated to this fact.

TASK [ceph-validate : validate provided configuration] *************************
Friday 17 May 2019 13:37:55 -0400 (0:00:00.500) 0:00:26.844 ************
ok: [mon0] => {
"changed": false
}
ok: [mon1] => {
"changed": false
}
ok: [mon2] => {
"changed": false
}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: IndexError: list index out of range
fatal: [osd0]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: IndexError: list index out of range
fatal: [osd1]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: IndexError: list index out of range
fatal: [osd2]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}
ok: [mds0] => {
"changed": false
}
ok: [mds1] => {
"changed": false
}
ok: [client0] => {
"changed": false
}

Could be nice to have the ansible.log file with more verbosity.

I edited: roles/ceph-defaults/defaults/main.yml and changed the following:
-ceph_origin: dummy
+ceph_origin: repository
-ceph_repository: dummy
+ceph_repository: community
-ceph_stable_release: dummy
+ceph_stable_release: mimic

You shouldn't do that. If you want to change values then you need to do it in the group_vars directory.

copy the all.yml.sample (at least, but you probably need mons and osds files or more depending on your setup) to all.yml and then change the value in that file
you also probably need one of the following variable to be set : https://github.com/ceph/ceph-ansible/blob/stable-3.2/group_vars/all.yml.sample#L342-L344

AFAIK, using the ceph-ansible with vagrant works fine with virtualbox provider.
This is not the first time I see this error : IndexError: list index out of range in ceph-validate but it should have been fixed though. As @dsavineau said, having the log with more verbosity -vvv would help.
Thanks!

How do you set -vvv ? I'm starting the project with "vagrant up --provider=virtualbox --provision"  but adding -vvv doesn't work here.

@deejay2 add debug: True in your vagrant_variables.yml

https://pastebin.com/y7XFtMcX

Notario Failure: key did not match schema  (required key in data is missing: osd_scenario)

Did you set osd_scenario in group_vars/osds.yml ?

Clearly not...

It worked :)
But I have this error now:
fatal: [mon0]: FAILED! => {
"msg": "'monitor_keyring' is undefined"
}
fatal: [mon1]: FAILED! => {
"msg": "'monitor_keyring' is undefined"
}
fatal: [mon2]: FAILED! => {
"msg": "'monitor_keyring' is undefined"

It could be useful to have the ansible log file and the variables configured in the group_vars directory to understand the issue.
Currently we don't know what is the ansible task related to your issue.

Honestly, I'm actually trying to understand how it's all working... I want to test in a virtual environment so I can later deploy in production on bare metal. I tought ceph-ansible would provide a working base model from which I can start and understand the working so I can then put my modifications in..  So I just want a virtual ceph deployment working and start from here. Is there place we can find a fully working configuration to start from?

I did like it was suggested here:
https://github.com/ceph/ceph-ansible/issues/2166
It looks like it fixed this last problem.
Now I have the following error:
[...]
TASK [ceph-config : generate ceph configuration file: ceph.conf] ***************
task path: /home/admin/projects/ceph-ansible/roles/ceph-config/tasks/main.yml:77
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: vagrant
<<IP_ADDRESS>> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2202 -o 'IdentityFile="/home/admin/.vagrant.d/insecure_private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/admin/.ansible/cp/%h-%r-%p <IP_ADDRESS> '/bin/sh -c '"'"'echo ~vagrant && sleep 0'"'"''
<<IP_ADDRESS>> (0, '/home/vagrant\n', 'OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b  26 Feb 2019\r\ndebug1: Reading configuration data /home/admin/.ssh/config\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug2: resolve_canonicalize: hostname <IP_ADDRESS> is address\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 31753\r\ndebug3: mux_client_request_session: session request sent\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: vagrant
<<IP_ADDRESS>> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2202 -o 'IdentityFile="/home/admin/.vagrant.d/insecure_private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/admin/.ansible/cp/%h-%r-%p <IP_ADDRESS> '/bin/sh -c '"'"'( umask 77 && mkdir -p "echo /home/vagrant/.ansible/tmp/ansible-tmp-1558555718.64-239660844149308" && echo ansible-tmp-1558555718.64-239660844149308="echo /home/vagrant/.ansible/tmp/ansible-tmp-1558555718.64-239660844149308" ) && sleep 0'"'"''
<<IP_ADDRESS>> (0, 'ansible-tmp-1558555718.64-239660844149308=/home/vagrant/.ansible/tmp/ansible-tmp-1558555718.64-239660844149308\n', 'OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b  26 Feb 2019\r\ndebug1: Reading configuration data /home/admin/.ssh/config\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug2: resolve_canonicalize: hostname <IP_ADDRESS> is address\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 31753\r\ndebug3: mux_client_request_session: session request sent\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: vagrant
<<IP_ADDRESS>> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2203 -o 'IdentityFile="/home/admin/.vagrant.d/insecure_private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/admin/.ansible/cp/%h-%r-%p <IP_ADDRESS> '/bin/sh -c '"'"'echo ~vagrant && sleep 0'"'"''
<<IP_ADDRESS>> (0, '/home/vagrant\n', 'OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b  26 Feb 2019\r\ndebug1: Reading configuration data /home/admin/.ssh/config\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug2: resolve_canonicalize: hostname <IP_ADDRESS> is address\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 31756\r\ndebug3: mux_client_request_session: session request sent\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: vagrant
<<IP_ADDRESS>> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2203 -o 'IdentityFile="/home/admin/.vagrant.d/insecure_private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/admin/.ansible/cp/%h-%r-%p <IP_ADDRESS> '/bin/sh -c '"'"'( umask 77 && mkdir -p "echo /home/vagrant/.ansible/tmp/ansible-tmp-1558555718.69-54044910964618" && echo ansible-tmp-1558555718.69-54044910964618="echo /home/vagrant/.ansible/tmp/ansible-tmp-1558555718.69-54044910964618" ) && sleep 0'"'"''
<<IP_ADDRESS>> (0, 'ansible-tmp-1558555718.69-54044910964618=/home/vagrant/.ansible/tmp/ansible-tmp-1558555718.69-54044910964618\n', 'OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b  26 Feb 2019\r\ndebug1: Reading configuration data /home/admin/.ssh/config\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug2: resolve_canonicalize: hostname <IP_ADDRESS> is address\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 31756\r\ndebug3: mux_client_request_session: session request sent\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: vagrant
<<IP_ADDRESS>> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2204 -o 'IdentityFile="/home/admin/.vagrant.d/insecure_private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/admin/.ansible/cp/%h-%r-%p <IP_ADDRESS> '/bin/sh -c '"'"'echo ~vagrant && sleep 0'"'"''
<<IP_ADDRESS>> (0, '/home/vagrant\n', 'OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b  26 Feb 2019\r\ndebug1: Reading configuration data /home/admin/.ssh/config\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug2: resolve_canonicalize: hostname <IP_ADDRESS> is address\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 31766\r\ndebug3: mux_client_request_session: session request sent\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: vagrant
<<IP_ADDRESS>> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=2204 -o 'IdentityFile="/home/admin/.vagrant.d/insecure_private_key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/admin/.ansible/cp/%h-%r-%p <IP_ADDRESS> '/bin/sh -c '"'"'( umask 77 && mkdir -p "echo /home/vagrant/.ansible/tmp/ansible-tmp-1558555718.73-11808100268205" && echo ansible-tmp-1558555718.73-11808100268205="echo /home/vagrant/.ansible/tmp/ansible-tmp-1558555718.73-11808100268205" ) && sleep 0'"'"''
<<IP_ADDRESS>> (0, 'ansible-tmp-1558555718.73-11808100268205=/home/vagrant/.ansible/tmp/ansible-tmp-1558555718.73-11808100268205\n', 'OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b  26 Feb 2019\r\ndebug1: Reading configuration data /home/admin/.ssh/config\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug2: resolve_canonicalize: hostname <IP_ADDRESS> is address\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 31766\r\ndebug3: mux_client_request_session: session request sent\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
fatal: [mon0]: FAILED! => {
"msg": "'ansible.vars.hostvars.HostVarsVars object' has no attribute u'ansible_enp0s8'"
}
fatal: [mon1]: FAILED! => {
"msg": "'ansible.vars.hostvars.HostVarsVars object' has no attribute u'ansible_enp0s8'"
}
fatal: [mon2]: FAILED! => {
"msg": "'ansible.vars.hostvars.HostVarsVars object' has no attribute u'ansible_enp0s8'"
}

Here's my vagrant_variables.yml:
DEPLOY CONTAINERIZED DAEMONS
docker: false
DEFINE THE NUMBER OF VMS TO RUN
mon_vms: 3
osd_vms: 3
mds_vms: 2
rgw_vms: 0
nfs_vms: 0
rbd_mirror_vms: 0
client_vms: 1
iscsi_gw_vms: 0
mgr_vms: 0
Deploy RESTAPI on each of the Monitors
restapi: true
SUBNETS TO USE FOR THE VMS
public_subnet: 192.168.42
cluster_subnet: 192.168.43
MEMORY
set 1024 for CentOS
memory: 512
Ethernet interface name
use eth1 for libvirt and ubuntu precise, enp0s8 for CentOS and ubuntu xenial
eth: 'enp0s8'
Disks
For Xenial use disks: [ '/dev/sdb', '/dev/sdc' ]
For CentOS7 use disks: [ '/dev/sda', '/dev/sdb' ]
disks: [ '/dev/sdb', '/dev/sdc' ]
VAGRANT BOX
Ceph boxes are strongly suggested. They are under better control and will
not get updated frequently unless required for build systems. These are (for
now):

* ceph/ubuntu-xenial

Ubuntu: ceph/ubuntu-xenial or bento/ubuntu-16.04 or ubuntu/trusty64 or ubuntu/wily64
CentOS: bento/centos-7.1 or puppetlabs/centos-7.0-64-puppet
openSUSE: opensuse/openSUSE-42.3-x86_64
libvirt CentOS: centos/7
parallels Ubuntu: parallels/ubuntu-14.04
Debian: deb/jessie-amd64 - be careful the storage controller is named 'SATA Controller'
For more boxes have a look at:
- https://atlas.hashicorp.com/boxes/search?utf8=✓&sort=&provider=virtualbox&q=
- https://download.gluster.org/pub/gluster/purpleidea/vagrant/
vagrant_box: ceph/ubuntu-xenial
The sync directory changes based on vagrant box
Set to /home/vagrant/sync for Centos/7, /home/{ user }/vagrant for openstack and defaults to /vagrant
vagrant_sync_dir: /home/{ user }/vagrant
VAGRANT URL
This is a URL to download an image from an alternate location.  vagrant_box
above should be set to the filename of the image.
Fedora virtualbox: https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86_64/Images/Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-virtualbox.box
Fedora libvirt: https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86_64/Images/Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-libvirt.box
vagrant_box_url: https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86_64/Images/Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-virtualbox.box
os_tuning_params:

{ name: fs.file-max, value: 26234859 }

Debug mode, runs Ansible with -vvvv
debug: true

Here is my vagrant_variables.yml file.
vagrant_variables.yml.txt

In group_vars:
all.yml:
ceph_origin: repository
ceph_repository: community
ceph_stable_release: mimic
monitor_address: <IP_ADDRESS>

I'm trying using eth1 instead of enp0s8 even though it's Xenial.. It looks like it went thru up to:
TASK [ceph-mon : collect admin and bootstrap keys] *****************************
where it failed again.. I will try to run destroy and up again in case of...

Hi!
So here's the log with the error now that i'm using eth1 instead of enp0s8 on Ubuntu Xenial. It looks like it's going much further but still it ends with an error about quorum. Thank you in advance for your help it's very appreciated!
analyse.log

@deejay2
when you run ansible via vagrant, it overrides some variables even though you define them in group_vars/*.yml
What is your actual interfaces on monitor nodes?
I'm unsure to understand why you set monitor_address: <IP_ADDRESS> in all.yml since you seem to have 3 monitors in your env:

If you want to specify monitor_address you must set it at inventory level for each monitor, I'm unsure it would work with vagrant up for the reason I've mentioned above though.
If you have the same interface name on all monitors, I would recommend to set monitor_interface in all.yml instead, but since you are using vagrant to run ceph-ansible, I'd say that you have to set eth: <interface-name> in vagrant_variables.yml

@guits
I've been told it was required but didn't fully grasp yet how it was going to apply. I've told myself maybe it will be overriden anyway since I have 3?  So I've put it <IP_ADDRESS> so I can search it later on on VM's interfaces or hoping it will at least help to bootstrap the process. Is vagrant supposed to give addresses automatically from the defined public/cluster subnet? How does it work?
Talking about the interface in vagrant_variables, I had it set to enp0s8 as suggested since I'm using Xenial but it turns out it was giving me errors. I changed it to eth1 and now it goes much further in the process.
So now I'm stuck with quorum errors...
Thank you!

@guits
About the interfaces, here's what I've got on mon0:
eth0      Link encap:Ethernet  HWaddr 08:00:27:55:12:9d
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::a00:27ff:fe55:129d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:150698 errors:0 dropped:0 overruns:0 frame:0
TX packets:60486 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:138773724 (138.7 MB)  TX bytes:3722336 (3.7 MB)
eth1      Link encap:Ethernet  HWaddr 08:00:27:78:e5:df
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::a00:27ff:fe78:e5df/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B)  TX bytes:648 (648.0 B)

Here's what I have on mon0 with "ceph -s":
root@mon0:/home/vagrant# ceph -s
2019-05-23 22:44:28.162 7f4410de3700 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
Maybe it can help understand why under "TASK [ceph-mon : collect admin and bootstrap keys] " I get:
INFO:ceph-create-keys:ceph-mon is not in quorum:   (tons of time)

You should try to check the network connectivity between mon nodes on eth1 (like ping the other nodes, try to reach the monitor port, etc...)
Also if you redeploy your setup (destroy the vagrant nodes) be sure to also remove the fetch directory created in the root ceph-ansible directory between two deployments.

Hmm... looks like this is related: https://github.com/ceph/ceph-ansible/issues/3467
I also had to add a monitor_secret in Vagrantfile. I'm also using Virtualbox.

I tried to set monitor_secret in all.yml as in #3467 but it doesn't work better for me.

You should try to check the network connectivity between mon nodes on eth1 (like ping the other nodes, try to reach the monitor port, etc...)

Please try basic networking check on the ceph public_network (<IP_ADDRESS>/24 via eth1) to be sure the issue isn't coming from the virtualbox infrastructure.
At this point, the ceph-mon process should be up & running so you should be able to see something binding on 6789 on ceph public_network.

@dsavineau :
oot@mon0:/home/vagrant# netstat -an |grep 6789
tcp        0      0 <IP_ADDRESS>:6789      <IP_ADDRESS>:*               LISTEN
tcp        0      1 <IP_ADDRESS>:40934         <IP_ADDRESS>:6789            SYN_SENT
It looks like that <IP_ADDRESS> may be causing problems? :) But the connection is from <IP_ADDRESS> which is eth0. What's the monitor_interface in all.yml? Is it supposed to be the interface eth1 (<IP_ADDRESS>/24) or eth0 (<IP_ADDRESS> with NAT) ?

oot@mon0:/home/vagrant# netstat -an |grep 6789
tcp 0 0 <IP_ADDRESS>:6789 <IP_ADDRESS>:* LISTEN
tcp 0 1 <IP_ADDRESS>:40934 <IP_ADDRESS>:6789 SYN_SENT

Be sure your able to reach  mon1 (<IP_ADDRESS>:6789) and mon2 (<IP_ADDRESS>:6789) from mon0

It looks like that <IP_ADDRESS> may be causing problems? :)

It looks like. You shouldn't have this in your configuration.

But the connection is from <IP_ADDRESS> which is eth0.

That's normal because the ceph command (ceph -s ...) is running from the first monitor node.

What's the monitor_interface in all.yml? Is it supposed to be the interface eth1 (<IP_ADDRESS>/24) or eth0 (<IP_ADDRESS> with NAT) ?

The monitor_interface variable is the name of the interface that will be used by the monitor to bind the process. All mon communication (including quorum stuff) will be done over that interface. The ip address on that interface is automatically configured in ceph.conf by ceph-ansible.
In your case it should be eth1 (<IP_ADDRESS>/24).

It worked well! Thank you very much! Just one thing, I did a vagrant halt yesterday and today after vagrant up --provider=virtualbox --provision it doesn't work anymore. I have no error at all at the end of the playbook but I have this error in mon0:
vagrant@mon1:~$ ceph -s
2019-05-24 23:43:17.408 7fa004a98700 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-05-24 23:43:17.412 7fa004a98700 -1 monclient: authenticate NOTE: no keyring found; disabled cephx authentication
[errno 95] error connecting to the cluster
It looks like it only works if vagrant virtualbox VMs are brand new.

It's all working thank you!

I was wondering, how do you collocate mgr and mon?? I see it's in all.yml but it seems like I'm not doing it properly...

Ok I got it... it was in ".vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory"
So I tried to remove [mgrs] from it hoping I would have mgrs collocate in mons but I got an error. I also tried tu put [mgrs] back in the file and still got the same error.
When VMs are running I'm now directly running the playbook like this:
ansible-playbook -vvv -i .vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory site.yml
I attached the log:
ansible.log

I was wondering, how do you collocate mgr and mon?? I see it's in all.yml but it seems like I'm not doing it properly... I just found that mgr needs to be undefined in the inventory file but where is that inventory file when using vagrant?

You have 2 solutions for collocated mons and mgr.

Explicitly in the inventory

[mons]
mynode ansible_host=x.x.x.x ansible_user=foo

[mgrs]
mynode

Without the mgrs section in the inventory (the mgrs will be deployed on the mons by default)

[mons]
mynode ansible_host=x.x.x.x ansible_user=foo

I'm not sure how vagrant will generate the inventory in your case.

Also the latest issue mentionned isn't about the mgr at all but the osd nodes. Could you share the osd variable configuration (group_vars/osds.yml) ?

Everything is default in osds.yml (nothing uncommented but dummy:)

You need at least to define the osd_scenario variable and depending on the value, set other variables too (devices or lvm_volumes)
http://docs.ceph.com/ceph-ansible/stable-3.2/osds/scenarios.html

Sorry, I had osc_scenario set actually to lvm. This was enough for vagrant up previously and vagrant called the playbook and it was succeeding. What could be different?

I now have the error: "msg": "'vm_min_free_kbytes' is undefined"
In osds.yml I have:
devices:

/dev/sdb
/dev/sdc

osd_objectstore: bluestore
lvm_volumes:
- data_vg: vg_osd
- data: osd_sdb
- db: osd_sdc
I manually created vg_osd, osd_sdb and osd_sdc on each osd node.
error.log

I'm now using a different image and provider ( guits/ubuntu-bionic64 / libvirtd ).
vagrant up went succesfully without any error. So far so good! But when running ansible-playbook on site.yml afterwards I see I still have errors on OSDs because they're not really ready...
This makes me wonder from what angle should I approach it? What's the easy way to bootstrap it?
I see on osds vms that there are 2 drives dedicated for ceph are showing in pvdisplay as ceph-[uuid] . Of course each uuid is different from a VM to the other so how should I automate the deployment to it? Since I have to specify logical volumes names for scenario 3, does it means I can't use it provision easily? How should I make it work? I just want a quick ceph demo deployed on my VMs and work from here.
Thank you!

What does vagrant up --provision does differently from:
"ansible-playbook -vvv -i .vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory site.yml"   ?
The first goes without error and the second ends with:
fatal: [mon1]: FAILED! => {
"changed": false,
"msg": "eth1 does not exist on mon1"
}
It looks like it reads this interface value some place where it's not updated after a new "vagrant up --provision" is called..

Oh I noticed something..
vagrant up --provision    =>  no error
ansible-playbook -vvv -i .vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory site.yml  => Error (vm_min_free_kbytes is undefined).
What could be different?

I've just set the variable in all.yml and it works :) I guess vagrant was providing it somehow..

Everything works fine now, also mgrs are succesfully colocated with mons! Thank you! :)


block_device_mappings does not support different types together (e.g. EBS and ephemeral)

Description
As the type of the block_device_mappings is currently set to list(any), this prevents you from being able to specify e.g. an EBS volume (which requires an ebs {} configuration block), as well as an instance store volume (which requires the virtual_name attribute), as the object structure of each list item will not match and this will fail Terraform's type checking.
Versions

Module version [Required]:
terraform-aws-modules/autoscaling/aws 6.7.1

Terraform version:
1.0.11

Provider version(s):

provider registry.terraform.io/hashicorp/aws v4.49.0

Reproduction Code [Required]
  block_device_mappings = [
    {
      # Root EBS volume
      device_name = "/dev/xvda"
      ebs = {
        delete_on_termination = true
        encrypted = true
        volume_size = 40
        volume_type = "gp2"
      }
    },
    {
      # Local instance store
      device_name = "/dev/xvdb"
      virtual_name = "ephemeral0"
    }
  ]

Steps to reproduce the behavior:
Create an ASG with the above block_device_mappings config.
Expected behavior
The configuration allows me to specify a launch template with both an EBS volume and an instance store volume on the same instance.
Actual behavior
The above configuration will fail with the error all list elements must have the same type.
Additional context
I'm not able to find a workaround here, as I can't make the elements match by e.g. adding virtual_name = null to the EBS element, as it won't match the string type of the second element, and if I set it to a blank string, the provider crashes.
Any ideas?

There is no effect on having an ephemeral instance store listed in the block device mappings. Either they are present based on the instance type or they are not. To utilize, you will need to mount them, typically through user data


escape sql in sqlbuilder buildOrderClauses

hi,
i realize its potentially harmful if we do not escape potential sql injection in here
mind if i add it in?

Not like WHERE, ORDER will not take an argument supplied by external users so the possibility of injection is very low. However, checking them for SQL injection could be an important task.


python312Packages.local-attention: init at 1.9.15

Adds the local-attention
I have tested that the library works using rvc-cli
Closes https://github.com/NixOS/nixpkgs/issues/359108
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I forgot to open a new branch before committing, so changes are coming from my fork's master branch. I'm not sure if this is a big deal. If it is, I can create another PR.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 359494

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.local-attention
python311Packages.local-attention.dist
python312Packages.local-attention
python312Packages.local-attention.dist


how to fix the client version != server version

run the command then happen like this:

Could you delete the /tmp/tailscale* and try again? I am not familiar with iStoreOS.

I usually see that error (client version != server version) immediately after updating versions, when an old version was already loaded in memory and I've downloaded a new version, and I run a tailscale command like tailscale up.
In this case, does iStoreOS include a very early build of Tailscale?
It looks like it does - https://openwrt.org/packages/pkgdata/tailscale that refers to Version:1.32.3-1 and https://openwrt.org/docs/guide-user/services/vpn/tailscale/start make it look like iStoreOS may have included this very early build of this package.
Otherwise, is it possible that you first tried installing this version?
If that is the case, I suggest that before you use this package, you need to
opkg remove tailscale
However, if it is built into the iStoreOS rom, you may be stuck with that version.

thanks for the answer ，it's worked after I do what you say ,but the exit node can't start

whatever I'm happy that it can be used, thanks again

You may need to add to your command to get it to run as an exit node:
tailscale up --accept-dns=false --advertise-routes=<IP_ADDRESS>/24 --advertise-exit-node
You may get a warning
Error: changing settings via 'tailscale up' requires mentioning all
non-default flags. To proceed, either re-run your command with --reset or
use the command below to explicitly mention the current value of
all non-default settings:

So run again
tailscale up --accept-dns=false --advertise-routes=<IP_ADDRESS>/24 --advertise-exit-node --reset
Finally, these two articles have some useful instructions around creating interfaces and fw rules.

https://openwrt.org/docs/guide-user/services/vpn/tailscale/start
https://www.reddit.com/r/Tailscale/comments/yrqbwb/how_to_using_openwrt_as_a_tailscale_exit_node/

These two options also require you to add --netfilter-mode=off to your tailscale up command so it will look like
tailscale up --accept-dns=false --advertise-routes=<IP_ADDRESS>/24 --netfilter-mode=off --advertise-exit-node --reset


bug: custom command "enclosed between the  tags" output not visible

Version
1.91.0
Describe the bug
I tried to make my first custom command, with the idea to put a python script in there later on that grabs some data and makes a nice prompt-friendly format for it for the context:
{
  "testcmd": {
    "prompt": "Given the context, provide a useful answer referring to the part of the context that references it",
    "context": {
      "selection": false,
      "command": "uname -a"
    },
    "mode": "ask"
  }
}

The response from Sonnet 3.5 states: "Based on the output from the uname -a command, which is enclosed between the <OUTPUT0412> tags, we can infer the following:"
However, this <OUTPUT0412> bit is nowhere to be seen (so if I would like to debug if my future script is doing what it's supposed to do, I wouldn't be able to).
Clicking on the blue \uname -a file-button-icon shows "The editor could not be opened because the file was not found." as seen in the following screenshot:

I cannot find the output anywhere. I tried on mouse-over, finding a temp file, I asked sonnet a follow up question about it:
"show me the  tags and contents, also tell me where this is stored"
Answer (including the empty space):
The <OUTPUT0412> tags and their contents are:

This output is typically stored in the system's memory or cache when the uname -a command is executed. The uname command retrieves information about the current system, and the -a option stands for "all", which displays a comprehensive set of system details.

Expected behavior
I expected to be able to inspect the output of the shell command I have executed. As stated by the response prompt with the <OUTPUT0412> tag.
Additional context
No response

I don't think I can 'un-stale' the issue.

@awesomebytes Since the terminal commands are executed internally, there is no other visual indication as the context file item in the context list.
We are moving away from custom commands to the Prompt Library: https://sourcegraph.com/prompts
Thank you


Provide Nuxt SSR context to trpc ctx object

Is it possible to do this since I want to do something for example with the ip address that made the request to trpc

Please update to latest version and check this example https://github.com/wobsoriano/trpc-nuxt/blob/master/recipes/authorization.md


Fix forwardTo function

forwardTo function will access a wrong legacy location in the prisma client object. These modifications fix it.

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

@nekocode Thanks for raising this PR, I really appreciate the work you have put in, however, exposing forwardTo from client was not intended. This PR removes forwardTo from Prisma Client: https://github.com/prisma/prisma/pull/3264
The reason for that is forwardTo uses schema delegation and we recommend using prisma-binding for that.
Please follow this for a detailed answer: https://www.prisma.io/forum/t/help-understanding-prisma-clients-value-proposition/4394/17?u=divyendu_singh
Thanks!


Custom argument to build_position rpc

I'm looking for a way to pass the result of a relatively expensive operation to the build_position function.
Flow:

Before build_position is called, I call expensive_operation() and store the result in a variable called expensive_table. expensive_table contains test data resolved by the test runner.

I need access to expensive_table in build_position. However, since build_position runs in a subprocess, I haven't found a way to directly pass expensive_table as an argument. I'm not very familiar with lua/neovim's api's, but I've been experimenting with two approaches to get around this:

Write expensive_table to a json file. Read the file in each build_position call.
Use a workaround such this. Essentially, this enables me to pass expensive_table to parse_position as part of opts table, then be able to access it in build_position in the opts.expensive_table argument.

Is there a better/more efficient way to do this? In large projects, build_position is called many times, so I'm trying to be mindful of performance.

I'm assuming the expensive table is used across multiple build_positions calls. The subprocess library module is considered a public API so you're free to use it for your own needs. You can manually call the subprocess to setup the table with something like this
local lib = require("neotest.lib")

local M = {}

local expensive_table = nil

function M._build_expensive_table()
  if expensive_table then
    return
  end
  expensive_table = { "some data" }
end

function M.parse_positions(path)
  -- You must check the subprocess is enabled before using it
  if lib.subprocess.enabled() then
    -- This is async and will wait for the function to return
    lib.subprocess.call("require('neotest-playwright')._build_expensive_table()")
  else
    M._build_expensive_table()
  end
  query = [[ ... ]]
  opts = { ... }

  return lib.treesitter.parse_positions(path, query, opts)
end

Does that work?

So your snippet shows how to call expensive_operation() in a sub-process to avoid blocking the main thread. Then, once the result is ready, it's stored as expensive_table in the main process.
What I'm having trouble wrapping my head around is: how can we access that expensive_table from the sub-processes that are spawned by neotest?
My understanding is that neotest uses one or more sub-processes to parse the test files, right? In each of those sub-processes, I'd like to access expensive_table. But since expensive_table is only defined in the main process, how should we expose expensive_table to those sub-processes?

So your snippet shows how to call expensive_operation() in a sub-process to avoid blocking the main thread. Then, once the result is ready, it's stored as expensive_table in the main process.

You're mixing thread and process so just to be clear: There is a single sub-process spawned (i.e. neovim --embed) which is then communicated with over stdio. Whenever any calls are made to the sub-process, they run within this neovim instance, meaning that all state set is available for later use. The instance is long lived so all state set will be available at any stage later.
The snippet above sets module state in the sub-process if it is enabled (lib.subprocess.enabled()) so expensive_table will be nil in the parent process (the interactive neovim instance) but set in the sub-process.
When you call  lib.treesitter.parse_positions(path, query, opts), assuming that you've correctly passed arguments that can be encoded, the build_positions function will be called in the subprocess and thus have access to the expensive_table value :smile:
Ref: https://github.com/nvim-neotest/neotest/blob/84955826bfdae41383f05b08ee9e8a7c46211001/lua/neotest/lib/treesitter/init.lua#L165-L169)

Thank you for that explanation! I had incorrectly assumed that neotest was making use of multiple ephemeral sub-processes rather than a single long-lived one. Things are making a lot more sense now.


JDBC plugin not supports unsigned int?

Migrated from: https://github.com/elastic/logstash/issues/5997 (by @rayenyang)
I have a table which has a unsigned int column in MySQL.Its a pity that exception occurred when I used Logstash to read this table:
**e[33mException when executing JDBC query {:exception=>#<Sequel::DatabaseError: J
ava::ComMysqlJdbcExceptionsJdbc4::MySQLDataException: '2.926689519E9' in column
'2' is outside valid range for the datatype INTEGER.>, :level=>:warn}e**

my lostash config:
input{
jdbc{jdbc_driver_library=>"mysql-connector-java-5.1.37.jar"
jdbc_driver_class=>"com.mysql.jdbc.Driver"
jdbc_connection_string=>"jdbc:mysql://localhost:3306/mydb
jdbc_user=>"root"
jdbc_password=>"1234"
schedule=>"* * * * *"
jdbc_paging_enabled=>true
jdbc_page_size=>1000
statement=>"SELECT * from mytable where record_id>:sql_last_value order by record_id desc"
use_column_value=>true
tracking_column=>"record_id"
}
}
output{
elasticsearch{

    }
}

bump. JDBC input assumes that even unsigned ints are signed. I've had to build views in MySQL to get around it using "casts" in the statements. Would be great to have this working.

This was fixed today via sequel 5.2.
Updating (or re-installing the existing plugin) should pull in the latest sequel version with this fix.
bin/logstash-plugin install --version "4.3.0" logstash-input-jdbc


[terra-scroll] Add scrolling callback debounce to suppress pointer events

Feature Request
Description
Update terra-scroll to suppress pointer events during scrolling to improve page performance. A short ~50ms debounce following the end of the scroll ticks will then restore pointer events.
@ Mentions
@tbiethman @mjhenkes

@dkasper-was-taken @tbiethman I have a rough prototype created - https://github.com/cerner/terra-core/commit/d7b738acd7a416aabf1fafcbf311ebf93c583b04. Is this something that we'd want to achieve?
I basically have a onScroll event listener where I suppress the pointer events that are associated with the scroll element and restore them after a delay. I have tested this out on a test page.
Let me know if I have to cover broader scenarios or if I have not addressed something.
cc: @ShettyAkarsh

It'd be good to spike into the performance improvements, if at all. I originally logged this thinking we could prevent some additional pointer events firing, but looks like most libraries just use it to halt momentum scrolling to prevent scroll events occuring faster than javascript calculations to avoid visual screen tearing.

I see. I profiled the test page and I noticed that the FPS is ~60 with (and without) suppressing the pointer events with a delay of 50ms. I also noticed that the paint time has reduced (not by a lot imo) with the fix while impacting (increasing) the scripting time (prolly because of the new event handler) for a series of 10 subsequent scroll events. It will be helpful if you could help me figure out what exactly should I be looking at while analysing the performance at this point.
Before:

After:

@dkasper-was-taken @tbiethman any thoughts?

@dkasper-was-taken Is there an application page that I could probably stress-test on if you think the existing test page is too light a benchmark for me to analyse the performance?

I figured that the dev site uses terra-scroll and noticed that the scroll isn't smooth with the delay - I had to scroll twice for something that I'd expect to get to by scrolling once. The screen captures below should illustrate the behavior:
Without Suppression:

With Suppression:

@dkasper-was-taken What do you think?
Branch: https://github.com/cerner/terra-core/compare/suppress-pointer-events

I imagine for now we can skip this change. It seems like introducing it as broadly as terra-scroll it too much. Might be better on a specific per instance introduction, where lots of javascript or loading is occurring on scroll.

That sounds good to me, we can keep this in our pocket for when those instances come up. Nice work @nramamurth looking into this! 👍


Time based whitelists

Signed-off-by: Samuel Dacanay<EMAIL_ADDRESS>
What this PR does / why we need it: Adds the ability for a whitelist to expire
Which issue this PR fixes (optional, in fixes #<issue number>)(, fixes #<issue_number, ...) format, will close the issue when PR is merged: fixes #: I couldn't find an issue for this actually
Special notes:

@zhill I did an initial pass at this to see if this is heading in the right direction.

Just verified locally, able to get whitelist checks to expire!

I've updated this PR now to set an expiry on each whitelist item (rule) instead of the entire whitelist set.


dclics --mode rumble doesnt return data

Describe the bug
$dclics --member-id $MEMBER_ID --character-id $CHARACTER_ID --platform xbox --period yesterday --mode rumble

Returns No results, even though I played a Rumble game yesterday.
I think this has to do with how Bungie updates aggregated stats with their API (they are delayed and batched). Given this, it might make sense to remove the period option for --yesterday.

Due to an API bug:
https://github.com/Bungie-net/api/issues/1357


UI/QT warnings

Stumbled upon this in the debug.log:
GUI: Object::connect: No such signal QWidget::message(QString,QString,unsigned int) in qt/walletview.cpp:137
GUI: Object::connect: No such slot OverviewPage::updateAlerts(QString) in qt/overviewpage.cpp:364
GUI: Object::connect:  (receiver name: 'OverviewPage')

And when building after cleaning:
qt/forms/lookupspdialog.ui: Warning: Z-order assignment: '' is not a valid widget.
qt/forms/lookupspdialog.ui: Warning: Z-order assignment: '' is not a valid widget.

Stumbled upon this in the debug.log:

Ahh nice - good catch.  OK so:
GUI: Object::connect: No such signal QWidget::message(QString,QString,unsigned int) in qt/walletview.cpp:137

This is due to my moving the original bitcoin send dialog into a tab - fixed by directing the signal to the new tab instead of the original page (https://github.com/zathras-crypto/omnicore/commit/05e0e81eeabc1d43cac16e94b681e64b02799d2a)
GUI: Object::connect: No such slot OverviewPage::updateAlerts(QString) in qt/overviewpage.cpp:364
GUI: Object::connect:  (receiver name: 'OverviewPage')

This is due to the fact updateAlerts() no longer takes a string parameter - I must have missed updating the slot - fixed in https://github.com/zathras-crypto/omnicore/commit/9f47020f96425677cdae0fdc2943c0c6d47e0413
qt/forms/lookupspdialog.ui: Warning: Z-order assignment: '' is not a valid widget.

Looks like some extraneous zorder directives have gotten in here somehow - perhaps I did something weird when designing that form - fixed in https://github.com/zathras-crypto/omnicore/commit/a0f081c28de2e6febd4d9d1baf1d372fdae72e7c
Thanks again dude!!! :)

A few of the following lines is printed to the debug file, after generating a block:
GUI: QTableWidget: cannot insert an item that is already owned by another QTableWidget

State: after running the regtests. It also appears, if all Omni transactions are confirmed.
It is not triggered by simple sends, and also not when creating new trades.
But it is triggered, when cancelling trades.

OK great, thanks for the heads up - I'll take a look once I get through with rewriting populateRPCTransactionObject()


Specifying --config doesn't disable the error message

Eg
$ CGO_ENABLED=0 go install
$ rclone --config ~/.rclone.conf about .
2018/04/21 22:28:59 ERROR : Couldn't find home directory or read HOME or XDG_CONFIG_HOME environment variables.
2018/04/21 22:28:59 ERROR : Defaulting to storing config in current directory.
2018/04/21 22:28:59 ERROR : Use --config flag to workaround.
2018/04/21 22:28:59 ERROR : Error was: user: Current not implemented on linux/amd64

NB the error message has a missing - in -config!

Hi i'm using rclone 1.41 and facing that error log.
I would like to add that these 4 error lines doesn't respect --log-file option
I'm using --config and --log-file and the errors are absent from the log file.
I don't think, it is a new bug, but maybe...


Download from a single user

Would be nice to have the ability to limit downloads to a single user

you could like make a string into the program (this is just a idea i didnt look at the code dont know what programming language it uses and rn i dont rly care)
if {pictures count == 10}
break (or something like that
else
continue


enable civiform.com for our AWS instance

Can we point civiform.com to our AWS instance.  I'm holding the domain under my personal GoDaddy account.  Please provide me the configuration that I need to set.
Gerardo

This will be essential for both user testing (we can point them to civiform.com) and helping community contributors see what work has been done already.

we also need to put a warning across the top asking people to not enter personal/real data as this is just a demo/example system.  something like what mibridges does in their demo site referenced on github: demo site.  maybe we can pick one of these tailwind formats: https://tailwindui.com/components/marketing/elements/banners

because we can't transfer the domain to route 53 until 5/10, we will go with godaddy's domain forwarding to http://prod-civiform-publiclb-916393258.us-west-2.elb.amazonaws.com/ until then.  i tested it and it works, but reverted back to point to our github repo, because before we start sending  people there we should implement the banner.  we also need to show the login as admin button when the domains is *.amazonaws.com .

Here's the banner CSS: https://play.tailwindcss.com/6yyHmMFEmG?size=540x720

will work on adding the banner today/tomorrow.

let's have the banner show on every page while the system is not officially in production even though it's on production servers.


Ability to respond to query parameter changes with a resource update

As it is also implied by the documentation;

... Note: resources are only refreshed on route change. The router does not poll or update resources in the background. Navigation within the same route, e.g. query param change, will not trigger a refresh of resources.
The resource is not refreshed when the query is changed by;

  const [page = '1', setPage] = useQueryParam('page');
  // call setPage() somewhere

Only way to force a refetch seems to be via an additional;
const resource = useResource(routeResource);
// resource.refetch() forces a proper update

Then, in resource's getData function the query is not properly updated and only way to practically access it is via window.location, which is an implementation detail and should not be ideally used:
getData: (routerContext) => {
  const params = new URLSearchParams(window.location.search);
  const page = params.get('page') || '1';
  // want to use page here, routerContext.query is a stale value from the previous route change for some reason
}

Ideally I would expect it to get triggered for query param changes as well. As it has probably now became a public behaviour maybe we can do it behind a boolean option?
Even this is not implemented, routerContext should get properly updated before getData is called so that we have a workaround.

There is a potential workaround: using the query parameter in the route key. This is something we will experiment with.

Using a cache key that gets invalidated based on query parameter solves the issue. Still, updating documentation would be great. I will try to have a look if I can find the time.


Fix 'sophia_term' dependency

As 'sophia_term' is not yet published, the dependency in sophia/Cargo.toml throughs an error if a crate depends on sophia's git. Fixed by adding a relative path.
In addition, set version of 'sophia_term' to 0.1.0 as it is a new crate.

I see where this comes from; a student of mine also had a dependency problem when he pulled the commit splitting sophia in two distinct crates. However, I don't think this PR is the correct way to solve it.
First: I don't know how the path hack in sophia/Cargo.toml will behave once published on crates.io, but I'm guessing not very well.
Second: I wish to keep the version numbers of all sophia crates aligned, (at least on the first two components). This will make maintenance much easier (even though it might seem strange for sophia-term to begin its life at version 0.4.0... :wink:)
The clean solution to your problem, I think, is to add the following section to your Cargo.toml:
[patch.crates-io]
sophia-term = { git = 'https://github.com/pchampin/sophia_rs' }

This instuct cargo to look for sophia-term in the git repo, whoever asks for it (including sophia itself).
We found this solution here:
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html
Does this solve your problem?

Ok, PRs are much faster committed then they should :wink: .
After further research we are both right. In order to use the newest version of sophia in metis I'll add the patch-section to my Cargo.toml. However, the path should also be added to sophia/Cargo.toml. It allows you to work with the local version of sophia_termduring development once the (sub-)crate is published.
Regarding the version of sophia_term I thought this might be a copy'n'paste error. As this is intentional I will not argue about versioning.
Accordingly, you can either close this PR or I'll remove the changes at term/Cargo.toml in an additional commit and you can squash the commits.

However, the path should also be added to sophia/Cargo.toml. It allows you to work with the local version of sophia_term during development once the (sub-)crate is published.

Awesome, thanks for doing the research ;-) I'll do this right away.

FTR, from a few tests that I just made :

path = "../term" in sophia/Cargo.toml solves the problem for local installations only (i.e. when your Cargo.toml specifies a path for sophia);
however, if your Cargo.toml uses git = "..." (even with a local git repo), you seem to need the patch.crates.io directive.

So both solve slightly different problems.


Add ren-nodes strategy

Thanks for creating/mainting Snapshot. We are hoping to set up a Ren snapshot (https://snapshot.org/#/ren-project.eth) using this strategy.
Changes proposed in this pull request:

Add ren-nodes strategy

Ah, didn't mean to commit that, it got mixed in with a merge. However I did need that change to be able to run tests locally, to avoid the error semantic error TS2783: 'nonce' is specified more than once, so this usage will be overwritten. It might be an issue with my local set-up though.

@noiach Thanks looks good now, we will get the strategy deployed shortly


question about how to calculate percent throught specific tag

I have a measurement like this:
time                           	city_id	come_from	   desc	count
2016-10-09T10:43:36.5502871Z	"1"	    "4"	           "11"	1
2016-10-09T10:43:39.833652904Z	"1"	    "4"	           "16"	1
2016-10-09T10:44:37.864675526Z	"1"	    "4"	           "2"	1

In this measurement,I'd like to calculate each desc's percent in total.
Below is the tick
var inner = batch
    |query('select sum("count") as count from "hestia"."default"."eleme_order_invalid_description"')
        .every(1d)
        .period(1d)
        .groupBy(time(1d), 'desc')
        .align()
        .fill(0)

var total = batch
    |query('select sum("count") as count from "hestia"."default"."eleme_order_invalid_description"')
        .every(1d)
        .period(1d)
        .groupBy(time(1d))
        .align()
        .fill(0)
    |log()
        .level('debug')
        .prefix('total')

total
    |join(inner)
        .tolerance(1d)
        .as('total', 'inner')
        .fill(0.0)
    |log()
        .level('debug')
        .prefix('after join')
    |eval(lambda: "inner.count" / "total.count")
        .as('rate')
    |log()
        .level('debug')
        .prefix('after evel')
    |influxDBOut()
        .database('hestia')
        .retentionPolicy('default')
        .measurement('downsample_marco_invalid_order_description')

Strange thing is the total not match the inner though the same time .Here is the logs:
[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=13","tags":{"desc":"13"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":39,"total.count":0},"tags":{"desc":"13"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=14","tags":{"desc":"14"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":162,"total.count":0},"tags":{"desc":"14"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=16","tags":{"desc":"16"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":278,"total.count":0},"tags":{"desc":"16"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=2","tags":{"desc":"2"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":2,"total.count":0},"tags":{"desc":"2"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=7","tags":{"desc":"7"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":1,"total.count":0},"tags":{"desc":"7"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=8","tags":{"desc":"8"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":3,"total.count":0},"tags":{"desc":"8"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=0","tags":{"desc":"0"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":73,"total.count":0},"tags":{"desc":"0"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=1","tags":{"desc":"1"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":1,"total.count":0},"tags":{"desc":"1"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=6","tags":{"desc":"6"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":1,"total.count":0},"tags":{"desc":"6"}}]}

[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","group":"desc=4","tags":{"desc":"4"},"points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":1,"total.count":0},"tags":{"desc":"4"}}]}

//the total , not match the inners
[downsample_marco_invalid_order_description:log6] 2016/10/10 18:51:20 D! after join {"name":"eleme_order_invalid_description","tmax":"2016-10-09T00:00:00Z","points":[{"time":"2016-10-09T00:00:00Z","fields":{"inner.count":0,"total.count":561},"tags":null}]}

But if I just add come_from within groupBy in total and inner,it works.
Is there any way to calculate percent the desc tag?
Kapacitor version is Kapacitor 1.0.2 (git: master 1011dba109bf3d83366c87873ec285c7f9140d34)

This is what the on property on the join node is for. But is currently has a bug where you need to use at least two tags to get it to work.
This TICkscript should work for you:
var inner = batch
    |query('select sum("count") as count from "hestia"."default"."eleme_order_invalid_description"')
        .every(1d)
        .period(1d)
        .groupBy('come_from', 'desc')
        .align()
        .fill(0)

var total = batch
    |query('select sum("count") as count from "hestia"."default"."eleme_order_invalid_description"')
        .every(1d)
        .period(1d)
        .groupBy('come_from')
        .align()
        .fill(0)
    |log()
        .level('debug')
        .prefix('total')

total
    |join(inner)
        .tolerance(1d)
        .as('total', 'inner')
        .fill(0.0)
        .on('come_from')
    |log()
        .level('debug')
        .prefix('after join')
    |eval(lambda: "inner.count" / "total.count")
        .as('rate')
    |log()
        .level('debug')
        .prefix('after evel')
    |influxDBOut()
        .database('hestia')
        .retentionPolicy('default')
        .measurement('downsample_marco_invalid_order_description')

The join node only joins points that have the same group unless you specify the on property to tell it how to join across groups. In this case you are telling it to join points tagged with come_from,desc to points tagged with come_from on the come_from tag. As a result the points tagged with only the come_from tag are duplicated for each of the matching come_from,desc points. Thus allowing you to calculate percentage of totals.
Also note that I removed the time(1d) from the group by since it isn't necessary since your period and every durations are also 1d.


Fix inspector plugin

Closes #24472.

I just noticed that the commits are all messed up for some reason. I'll fix it when I get to a computer again later today.

Rebased it for you.

Thanks!

Thanks!


tokenFate update

Added a new command for whispering results to GM.
Added parsing of single argument for multiple results returned.

Greetings @dedurrett
This pull request has merge conflicts which will need to be resolved before I can add the update.
Thanks,
Cassie


Cognitive Services 2022-03-01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
March 2nd
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
March 2nd
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@xiaoxuqi-ms
Curently the pipeline detected breaking change:
❌ 1029 - ReadonlyPropertyChanged | The read only property has changed from 'false' to 'true'.
I wonder if this is false alarm.
What really happen is:
We are adding a new dynamicThrottlingEnabled property to CallRateLimit. Which is not readonly.
So we removed readonly from CallRateLimit and apply readonly to all other properties in CallRateLimit.

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}/models": {

How are models created? I assume these are proxy resources - meaning, your RP generates them? If that's the case your response needs to follow proxy definition see here: https://github.com/Azure/azure-rest-api-specs/blob/bb4175d29020cfff55f1d9087c2a5a89765067dc/specification/common-types/resource-management/v2/types.json#L85 and you also need to model a single GET. An example of this API can be found here: https://github.com/Azure/azure-rest-api-specs/blob/9a19506631005d0ff1e3f394c86a9ce10cf51910/specification/resources/resource-manager/Microsoft.Resources/stable/2020-10-01/deploymentScripts.json#L274 notice /logs and /log/default (singleton).

Refers to: specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/stable/2022-03-01/cognitiveservices.json:670 in a894a33. [](commit_id = a894a331491839aca2d9c597b537171987bda704, deletion_comment = False)

"AccountModel": {

since this seems to be a proxy resource you are missing: id, name and type properties.

Refers to: specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/stable/2022-03-01/cognitiveservices.json:3014 in a894a33. [](commit_id = a894a331491839aca2d9c597b537171987bda704, deletion_comment = False)

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}/models": {

How are models created? I assume these are proxy resources - meaning, your RP generates them? If that's the case your response needs to follow proxy definition see here:
https://github.com/Azure/azure-rest-api-specs/blob/bb4175d29020cfff55f1d9087c2a5a89765067dc/specification/common-types/resource-management/v2/types.json#L85
and you also need to model a single GET. An example of this API can be found here:
https://github.com/Azure/azure-rest-api-specs/blob/9a19506631005d0ff1e3f394c86a9ce10cf51910/specification/resources/resource-manager/Microsoft.Resources/stable/2020-10-01/deploymentScripts.json#L274
notice /logs and /log/default (singleton).
Refers to: specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/stable/2022-03-01/cognitiveservices.json:670 in a894a33. [](commit_id = a894a33, deletion_comment = False)

Models are not created from control plane. I think this is very like the SKUS, I don't think current SKUs API for all RP is inherited from Proxy definition.

ARM has the concept of proxy and tracked resources, returning 'models' as non-ARM resource is not a common pattern.

ARM has the concept of proxy and tracked resources, returning 'models' as non-ARM resource is not a common pattern.

Hi @jorgecotillo
As I explained in email, model is not designed to be a proxy resource. It's some kind of service level metadata, like Sku.
The scenario is very similar with commitmentTiers, which is also not a proxy resource. Similar to commitmentTiers, models doesn't have any direct affiliation with Account. In future we plan to enable location based list models operation.
It doesn't make much sense to make it a proxy resource under Account. In fact it's not compatible to be a proxy resource:

Just like Sku, name in model does not ensure uniqueness. Models can have same name with different versions.

I understand that this might not be a common ARM pattern, but considering the fact we already have similar design exists. Is it possible that you approve this?

I'm okay with returning models as metadata, but if it does not have any affiliation with accounts, can you move it to the top level (e.g. .../providers/Microsoft.CognitiveServices/accountModels)?

We understand that we can have a subscription level API. In fact we were planning to include a subscription location based API. But time is not right, we decided to release that in later versions.
Just like Skus APIs. The models APIs under account will returns models available for this account. Also custom models added from data plane will be added in addition to system models, so we do need this account level list models to be exists.

/azp run

Hi @ArcturusZhang , could you help to review this PR?

/azp run

/azp run

/azp run


Implemented a method for evaluating JavaScript on Android.

I've added support for executing Javascript for the Android platform.

Signed.

Closing in favor of #1021


showBuildSettings does not require to call clean

Checklist

[x ] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x ] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x ] I've read the Contribution Guidelines
[ x] I've updated the documentation if necessary.

Description
In show building settings, don't call xcodebuild clean, because it's not a necessary workaround anymore.
Motivation and Context
This change will allow the user to do not clean the build (unless specified in the following commands).
Previously for example event setting clean: false, will result in callling clean because of the generated
xcodebuild clean -showBuildSettings
As stated in the comment this was a workaround for an xcodebuild bug. But this bug has being fixed in 8.3 so it's not necessary anymore. https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Chapters/Introduction.html
As huge benefit, I can keep using fastlane with my CI, and for example, caching pod builds, and reduce my build time significantly.
This pull request also fixes https://github.com/fastlane/fastlane/issues/8099

@hjanuschka I implemented the changes you requested! Much better!

@punty awesome, looking solid 👍  thx for your work and patience, one comment left.

@hjanuschka thanks again for your suggestions! I implemented the changes you requested

@KrauseFx thanks for your feedback. I just implemented the changes you requested.

@punty 🚀  merged, many thx for your contribution 🎉


Proper instruction for new users

I've just uploaded my code to s3 and it works amazing, but you may consider creating a short tutorial for new users with s3 cli commands (recursive copy) and s3 configuration.

Take a look at updated Readme.
Cheers!

<3


[spi_device] IoModeChangeValid_A Assertion Error

In dual mode read test we get this assertion error:
IoModeChangeValid_A
Can you @eunchan comment if the scenario is wrong or something else. In quad mode we don't get same assertion error.
To recreate, in PR #11762 run:
./util/dvsim/dvsim.py hw/ip/spi_device/dv/spi_device_sim_cfg.hjson -i spi_device_dual_mode --fixed-seed 10 --tool xcelium --waves --xprop-off -v h --max-parallel 1

This assertion error disappeared after applying changes from #11780. Closing now, will reopen in case it re-appears.


feature(front): #22 - drag and drop ressource

Description
Please include a summary of the change (features and fixes)
Related issues

#22

Type of change

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

Change ta PR pour merge dans dev et pas dans main


Twitch Stream Announcements keep Announcing Offline Streams

Hi,
I have been hosting the NadekoBot myself and setup Twitch Stream Announcements. Since the last version there is .streamoff switch that iam using. It says it does not announce offline streams anymore, but it still does. I've tried switching it on and off again and also did reboot the bot.

This doesn't seem related... I am getting that error also but not at the same time as what this is doing. this seems more related to a potential typo in code for handling multiple of the same stream I would think. It works for the twitch channels only used once but the repeated one bugs it out

Ah, alright. Interesting.

@zfbx remove all streams, and add it once and set a stream message and see if it happens again. The original issue has nothing to do with yours, so if you have an problem, create a new issue with reproducible steps.

@zfbx yes exactly the same! I get the stream offline message at another time then the other error messages in the logs

Still does it :(
At 16:16 a Streamer went offline, at that time i only got
0 16:16:30 StreamNotificationService | Retreived and published stream statuses in 0.22s
In the console. Even when i got the Offline Announcements off.


docs: Update URLs moved from v1beta1 to v1

Fixes #N/A
Description
While reading the docs I stumbled upon broken URLs. It appears to be broken since this move.
I ran this command to fix them: for f in $(find . -type f -name '*.md'); do sed -i '' 's,https://github.com/aws/karpenter/blob/main/examples/v1beta1,https://github.com/aws/karpenter/blob/main/examples/v1,g' $f; done
How was this change tested?
I clicked a new URL.
Does this change impact docs?

[X] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.04%) to 79.281%

Files with Coverage Reduction
New Missed Lines
%

pkg/providers/amifamily/ami.go
1
91.67%

pkg/fake/utils.go
2
94.56%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.04%

Covered Lines:
5996

Relevant Lines:
7563

💛  - Coveralls


Fix parent context not being applied when changeset itself has no context

Environment
Liquibase Version: 4.4.3
Liquibase Integration & Version: all
Liquibase Extension(s) & Version: all
Database Vendor & Version: all
Operating System Type & Version: n/a
Pull Request Type

[x] Bug fix (non-breaking change which fixes an issue.)
[ ] Enhancement/New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Parent context isn't being applied to changeset if a changeset itself does not have any context set.
The fix is to always build the full context regardless of whether the changeset has any context.
Steps To Reproduce
See reproduction repo: https://github.com/jatcwang/liquibase_context_bug_repro
Actual Behavior
According to the documentation, setting context attribute on  or includeAll node should add the specified context value to all changesets within its scope

Migrations are run but the "default" context is not applied to the changeset
However, if the changelog itself has some context set (e.g. some_context), then the changeset in DATABASECHANGELOG will have a context value of default AND some_context, matching the liquibase documentation.

Expected/Desired Behavior
Parent context (from <includeAll> or <databaseChangelog>) should always apply regardless of whether the changeset has
Fast Track PR Acceptance Checklist:

[ ] Build is successful and all new and existing tests pass
[x] Added Unit Test(s)
[ ] Added Integration Test(s)
[ ] Added Test Harness Test(s)
[ ] Documentation Updated

Need Help?
Come chat with us on our discord channel

I pushed the current version of master to your fork to fix the build issue.

Hi @jatcwang
Thanks for providing this PR.
A member of the Liquibase team will take a look at your contribution and may suggest:

Changes based on guidelines for PR submission
Additional tests (unit and/or integration) and/or Test Harness Tests
Provide other feedback, like requesting changes.

The PR will be prioritized according to our internal development and testing capacity.
We’ll let you know when it’s ready to move to the next step or if any changes are needed.

This was addressed in a similar PR that was merged in a recent release.
Closing this as a duplicate.


Error: pull model manifest: 400

What is the issue?
Got this strange error while trying to create a model.
$ ./createmodels.sh
transferring model data
creating model layer
creating template layer
creating parameters layer
creating config layer
using already created layer sha256:5499dfd64378623dc8ae420f29fc8e6a6e43f23198a290f5c4e9623c1d19c57a
using already created layer sha256:b89fc90e483fb047c3771d09fdc30b949815b781c25487501455faf74167a747
using already created layer sha256:084d40e289fdd6e852fd8897a18bea3de65fe96b9ed40f3a64d2e7ec115dd085
writing layer sha256:1db98adc375faf95d8b7e65ee0fb29dddf905e87fecf7229d9b60e4aca928eb8
writing manifest
success
transferring model data
pulling model
pulling manifest
Error: pull model manifest: 400
transferring model data
creating model layer ⠴

OS
Windows
GPU
Nvidia
CPU
Intel
Ollama version
0.1.32

ok, I see, just mistyped the filename in the FROM path!


How to Support Other LLMs

How can I support other LLMs? Are there detailed steps and is it possible to switch to a local embedding model?
Thank you!

Where can I find the specific URL for LLM requests? I couldn't locate the URL used for sending requests in the project.Otherwise, other LLMs cannot be used.

Thanks for your question!
In https://github.com/ShayanTalaei/CHESS/blob/main/src/llm/engine_configs.py, we define the constructors of the models that we want to use in our system, in a modular way using the Langchain library. You can easily add any LLM of your choice to this file, and then set its name in the run_*.sh file accordingly.
For switching to a local embedding model, you can similarly change the embedding models used in the preprocessing step, with the model of your choice. https://github.com/ShayanTalaei/CHESS/blob/main/src/database_utils/db_catalog/preprocess.py

How can I support other LLMs? Are there detailed steps and is it possible to switch to a local embedding model? Thank you!

请问您修改成功了吗？能否分享一下怎么修改。谢谢

How can I support other LLMs? Are there detailed steps and is it possible to switch to a local embedding model? Thank you!

Have you successfully made some modifications regarding the embedded model? Can you share how it was modified? thank you


Module wont load - pexpect

Hi, for some reason the module cannot be found
2019-07-03 13:10:25 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform ssh
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT)
  File "/usr/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/lib/python3.7/asyncio/coroutines.py", line 120, in coro
    res = func(*args, **kw)
  File "/home/homeassistant/.homeassistant/custom_components/ssh/sensor.py", line 48, in async_setup_platform
    dev.append(SSHSensor(hass, config))
  File "/home/homeassistant/.homeassistant/custom_components/ssh/sensor.py", line 66, in __init__
    self._connect()
  File "/home/homeassistant/.homeassistant/custom_components/ssh/sensor.py", line 127, in _connect
    from pexpect import pxssh, exceptions
ModuleNotFoundError: No module named 'pexpect'

Same problem here


Error when bad versions are present

Currently if the version specified for a stemcell/release is specified in quotes, or a misspelling of latest,  the errors presented to the end user aren't that helpful - it says that the specified version is not present, even if it actually is.
We should probably account for this, strip quoting characters from the versions, and ensure they match some sort of version regex to bail out if they're invalid.

Implementing at least in three steps

Stripping Quotes
1.1 Will only process single and double quotes
1.2 Will not process folding style strings (>)
1.3 Will only check that string length change is either zero or two.  Will generate an warning statement
1.4 Will not generate an error for mismatch quotes

latest and track processing
2.1 Will lowercase before comparison

3 Version number checking
3.1  Should release version strings be checked at all?  They can be customized through the bosh cli  and may contain development build numbers.
3.2 Should the version follow the semver specification or just x.y.z?
3.3 Will check stemcell version since it is less likely be a development build.   Will generate a warning instead of an error.

I was thinking of something more like
if [[ ${VERSION} != "latest" && ${VERSION} != "track" && ${VERSION} !~ /^[.\-0-9]\+$/ ]];
  echo Bad version (expected "latest", "track", or a version string: ${VERSION}
  exit 1
fi

Closing - obviated by genesis-v2


Fix VQE tutorial

Fix for the VQE tutorial so that the correct arguments are passed to the molecular_hamiltonian function.
This is due to the changes in PL#1078.

@thisac for any changes due to PL master, best to merge this into the dev branch (as the dev branch is pinned to latest, while the master branch is pinned to stable).


Script for extracting data from irmng data source

Script for extracting data from irmng data source

So this script is almost the same as get_species_status, which means it should be pretty easy to use the other one by parameterizing the urls. Is there any reason you created a separate script?


update deactivate_users job

fix the first parameter in t2-function

Interesting. How does this work in Russian?

The first parameter is used for numbers "1, 21, 31, 41..."|


status: Add explicit --format argument

Prep for adding --format=human for example. But this is also useful for anything that explicitly wants to consume YAML today.

Code LGTM but I don't see docs.

Currently the man pages are auto-generated into tarball releases; there's a currently manual cargo xtask man2markdown which also auto-reflects the manpages into markdown stored in git. (It's confusing...and tempting to go to writing man pages ...manually)

Q: Shall we remove the --json flag before 1.0?

I marked it hidden, but it's trivial to continue to support for now.


Upgrade to Scala 2.11.5.

CI only.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1321/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1664/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1322/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1665/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1326/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1669/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1324/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1667/
Test FAILed.

@gzm0 How do I schedule a nightly/weekly build on this PR? I understood how to schedule a nighly for master for immediate execution, but not on a PR.

You have to launch a matrix-build with the right params. Take this PRs build, follow the build chain to the matrix build, relaunch another matrix build with the same params, but set matrix=nightly instead of pr.

OK thanks. If I understood correctly, here they are:
Nighlty: https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1671/
Weekly: https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1672/

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1325/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1668/
Test PASSed.

Btw, the issue number in the backport commit is wrong I think

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1323/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1666/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1327/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1670/
Test PASSed.

Indeed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1328/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1673/
Test FAILed.

retest this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1329/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/1675/
Test PASSed.


Language-specific guides request

Php programming would be of great help

Thanks for requesting. Closing as a duplicate of #12719