Ansible playbook failed

Trying to run the Ansible playbook: ansible-playbook -i "hosts" enable-ius.yml I get the error: Failure downloading https://centos7.iuscommunity.org/ius-release.rpm, 'NoneType' object has no attribute 'read'
Running with -vvvv
TASK [install IUS release package] *********************************************
task path: /home/vagrant/ansible-playbook-aegir-centos/enable-ius.yml:24
<haproxy.dev> ESTABLISH SSH CONNECTION FOR USER: None
<haproxy.dev> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/vagrant/.ansible/cp/ansible-ssh-%h-%p-%r haproxy.dev '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1478002414.39-180297584212514 `" && echo ansible-tmp-1478002414.39-180297584212514="` echo $HOME/.ansible/tmp/ansible-tmp-1478002414.39-180297584212514 `" ) && sleep 0'"'"''
<haproxy.dev> PUT /tmp/tmpcDwJ_w TO /home/vagrant/.ansible/tmp/ansible-tmp-1478002414.39-180297584212514/yum
<haproxy.dev> SSH: EXEC sftp -b - -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/vagrant/.ansible/cp/ansible-ssh-%h-%p-%r '[haproxy.dev]'
<haproxy.dev> ESTABLISH SSH CONNECTION FOR USER: None
<haproxy.dev> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/vagrant/.ansible/cp/ansible-ssh-%h-%p-%r haproxy.dev '/bin/sh -c '"'"'chmod u+x /home/vagrant/.ansible/tmp/ansible-tmp-1478002414.39-180297584212514/ /home/vagrant/.ansible/tmp/ansible-tmp-1478002414.39-180297584212514/yum && sleep 0'"'"''
<haproxy.dev> ESTABLISH SSH CONNECTION FOR USER: None
<haproxy.dev> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/vagrant/.ansible/cp/ansible-ssh-%h-%p-%r -tt haproxy.dev '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-qhedrztmtfnuecabiruxawxazzdnjrzl; LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python /home/vagrant/.ansible/tmp/ansible-tmp-1478002414.39-180297584212514/yum; rm -rf "/home/vagrant/.ansible/tmp/ansible-tmp-1478002414.39-180297584212514/" > /dev/null 2>&1'"'"'"'"'"'"'"'"' && sleep 0'"'"''
fatal: [haproxy.dev]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"conf_file": null, "disable_gpg_check": false, "disablerepo": null, "enablerepo": null, "exclude": null, "install_repoquery": true, "list": null, "name": ["https://centos7.iuscommunity.org/ius-release.rpm"], "state": "present", "update_cache": false, "validate_certs": true}, "module_name": "yum"}, "msg": "Failure downloading https://centos7.iuscommunity.org/ius-release.rpm, 'NoneType' object has no attribute 'read'"}

Something else I notice and maybe help; When you run a task to install the epel repo using the state: latest it fails instead when you run as state: present
This one will fail:
- name: Install epel repo
  yum:
    name: https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    state: latest

But this one will work:
- name: Install epel repo
  yum:
    name: https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    state: present

Unfortunately doing the same on for the IUS repo it always fails:
- name: Install IUS repo
  yum:
    name: https://centos7.iuscommunity.org/ius-release.rpm
    state: present

Hey @tovletoglou,
Thanks for taking the time to submit this issue.  Personally, I do not have much experience with Ansible.  Looking at the error message, it would seem that the server in question can not access the IUS release URL.  Can you confirm the following from the server in question:
$ curl -I https://centos7.iuscommunity.org/ius-release.rpm
HTTP/1.1 301 Moved Permanently
Date: Tue, 01 Nov 2016 13:57:09 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips
Location: https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-14.ius.centos7.noarch.rpm
Content-Type: text/html; charset=iso-8859-1

$ curl -I https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-14.ius.centos7.noarch.rpm
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 01 Nov 2016 14:41:27 GMT
Content-Type: application/x-redhat-package-manager
Content-Length: 8264
Last-Modified: Tue, 01 Nov 2016 04:16:36 GMT
Connection: keep-alive
ETag: "58181724-2048"
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
Accept-Ranges: bytes

If you are able to access these URLs, you might want to try using the full URL, 'https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-14.ius.centos7.noarch.rpm'.  The way that EPEL and IUS handles the latest release URLs are different.  IUS uses a 301 redirect while EPEL returns a 200.  I am not sure if that will make a difference, but it might be worth a try.
Also, what version of Ansible are you using?

Hi @b-harper thanks for the quick reply.
I'm running ansible <IP_ADDRESS>
Both commands return the exact same output with yours.
But trying the Ansible role:
- name: Install IUS
  yum:
    name: https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-14.ius.centos7.noarch.rpm
    state: present

Returns the error:
TASK [ansible-role-git : Install ius] ******************************************
task path: /home/vagrant/ansible-playbook-aegir-centos/roles/ansible-role-git/tasks/git-install-from-repository.yml:8
<haproxy.dev> ESTABLISH SSH CONNECTION FOR USER: None
<haproxy.dev> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/vagrant/.ansible/cp/ansible-ssh-%h-%p-%r haproxy.dev '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1478020201.94-274781954102298 `" && echo ansible-tmp-1478020201.94-274781954102298="` echo $HOME/.ansible/tmp/ansible-tmp-1478020201.94-274781954102298 `" ) && sleep 0'"'"''
<haproxy.dev> PUT /tmp/tmpU5OTlk TO /home/vagrant/.ansible/tmp/ansible-tmp-1478020201.94-274781954102298/yum
<haproxy.dev> SSH: EXEC sftp -b - -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/vagrant/.ansible/cp/ansible-ssh-%h-%p-%r '[haproxy.dev]'
<haproxy.dev> ESTABLISH SSH CONNECTION FOR USER: None
<haproxy.dev> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/vagrant/.ansible/cp/ansible-ssh-%h-%p-%r haproxy.dev '/bin/sh -c '"'"'chmod u+x /home/vagrant/.ansible/tmp/ansible-tmp-1478020201.94-274781954102298/ /home/vagrant/.ansible/tmp/ansible-tmp-1478020201.94-274781954102298/yum && sleep 0'"'"''
<haproxy.dev> ESTABLISH SSH CONNECTION FOR USER: None
<haproxy.dev> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/vagrant/.ansible/cp/ansible-ssh-%h-%p-%r -tt haproxy.dev '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-ggucypfbxrfsxjrpulnqcprkzrtnsgvj; LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python /home/vagrant/.ansible/tmp/ansible-tmp-1478020201.94-274781954102298/yum; rm -rf "/home/vagrant/.ansible/tmp/ansible-tmp-1478020201.94-274781954102298/" > /dev/null 2>&1'"'"'"'"'"'"'"'"' && sleep 0'"'"''
fatal: [haproxy.dev]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"conf_file": null, "disable_gpg_check": false, "disablerepo": null, "enablerepo": null, "exclude": null, "install_repoquery": true, "list": null, "name": ["https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-14.ius.centos7.noarch.rpm"], "state": "present", "update_cache": false, "validate_certs": true}, "module_name": "yum"}, "msg": "Failure downloading https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-14.ius.centos7.noarch.rpm, 'NoneType' object has no attribute 'read'"}

Probably something is going wrong with Ansible and the 301 redirect.

Now I'm trying the Ansible task yum_repository https://docs.ansible.com/ansible/yum_repository_module.html that seems more appropriate to setup a repository.
Here is an example role to install IUS using yum_repository on Centos 7.
- name: Add IUS repository to /etc/yum.repos.d/
  yum_repository:
    name: ius
    file: ius
    description: IUS Community Packages for Enterprise Linux 7 - $basearch
    mirrorlist: https://mirrors.iuscommunity.org/mirrorlist?repo=ius-centos7&arch=$basearch&protocol=http
    gpgkey: http://dl.iuscommunity.org/pub/ius/IUS-COMMUNITY-GPG-KEY
    enabled: yes
    gpgcheck: yes

In your last example, the url https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-14.ius.centos7.noarch.rpm is not a 301 redirect, that is the exact path to the rpm.  It appears that while yum supports installing from a url, the ansible yum module does not.  The final part of your error message, 'NoneType' object has no attribute 'read', usually indicates that something unexpected happened in the Python code.
The yum_repository module seems useful, but we would still prefer an approach that gets our official ius-release rpm installed on the system, so I'm not sure what the best solution would be for this example playbook.  Perhaps a two step download and install?  That would require the ansible yum module to support installing a local rpm file (I'm not sure if it does or not).

@scottsb,
As someone that contributed this Ansible example, do you have any idea whats happening or changes that might need to be made?

tovletoglou:  I've got a slightly modified version of the enable-ius.yml file linked below.  Can you try running this and letting us know what you get for the output?
https://gist.github.com/chrishultin/d986c13772da1f5d7f6d2d6152b45c8c

It will drive me crazy... Running the following task from a Vagrant, Centos 7.2, Ansible <IP_ADDRESS>
# Must be state: present due to deficiency in ansible. See:
# https://github.com/ansible/ansible-modules-core/issues/948
- name: install IUS release package
  yum:
    name: "https://{{ ius_distribution_abbrev }}{{ ansible_distribution_major_version }}.iuscommunity.org/ius-release.rpm"
    state: present
  when: ansible_os_family == 'RedHat'
  register: install_via_url
  ignore_errors: yes

to a DigitalOcean, Centos 7.2 VM everything goes ok!
to a Vagrant, Centos 7.2 VM reports:
fatal: [vagrant.dev]: FAILED! => {"changed": false, "failed": true, "msg": "Failure downloading https://centos7.iuscommunity.org/ius-release.rpm, 'NoneType' object has no attribute 'read'"}

Running the @chrishultin's playbook failed on VMs that can install from URL. But this is not a real issue.
  fatal: [digitalocean.vm]: FAILED! => {
  "failed": true,
  "msg": "The conditional check 'install_via_url.failed' failed. The error was: error while evaluating conditional (install_via_url.failed): 'dict object' has no attribute 'failed'

  The error appears to have been in '/home/vagrant/ansible-playbook-aegir-centos/ius.yml': line 32, column 7, but may
  be elsewhere in the file depending on the exact syntax problem.

  The offending line appears to be:

      - name: download IUS release package
      ^ here"
  }

@carlwgeorge I don't know how https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-14.ius.centos7.noarch.rpm works to setup a repo, but it will make something different from creating (on a Centos system) these files?
/etc/yum.repos.d/ius.repo
/etc/yum.repos.d/ius-archive.repo
/etc/yum.repos.d/ius-dev.repo
/etc/yum.repos.d/ius-testing.repo

So I got asking around to some folks that know and use Ansible.  This pull request got created for better error reporting.  Someone else mentioned the difference between 'state=present' and 'state=latest', but it seems you have tried both without any luck.  A third person voiced frustration about the overall state of the yum module.
In regards to using the ius-release RPM, it is not so much about initially creating the repositories, but having a smooth transition if they need to get updated.  Generally we recommend using the ius-release RPM, but there are some cases where it does not make sense, like if you run your own private mirror.  If end up not using the ius-release RPM, I would recommend watching our announce repository as that is where we would announce any changes.

@tovletoglou, were you able to make any progress?
That pull request got merged, but it is not clear when it will make it into a proper release.

We decide to drop the yum installation and keep the yum_repository task for the moment. The only problem is that we miss the official changes on the ius-release rpm.

@tovletoglou,
Thanks for the update.  We try to change the ius-release RPM as little as possible.  That being said, I would recommend watching the announce repository and/or the ius-release repositories.


Add before you begin checkbox for marketplace

update marketplace region list for ray
update before you begin checkbox for marketplace.

/gcbrun

/gcbrun

/gcbrun

/gcbrun


resource-group-authoring-templates.md

Modified the JSON snippet to an array input, per the documentation guidelines further down.

@ljtill : Thanks for your contribution! The author, @tfitzmac, has been notified to review your proposed change.

@ljtill - thanks for fixing this issue!
#sign-off


More options

Such as
selector for grid/list item,
grid padding,
progress bar while loading packages,
image picker infinite loading,
dim,
grid/list hiding scrollbar...

Some of these things (selector, padding, etc) will be configurable via styleables at some point (#39). The others are better left to the user to implement themselves. We're going to keep the library simple with an eye towards extensibility, rather than try to predict all the possible use cases and UIs people could want.

@hzsweers how to configure Dim via BottomSheet layout?

Is it possible, through the library, to dim the whole screen and not just content view?


Unnecessary &mut in Query.iter

Right now, the signature of Query.iter is
pub fn iter(&mut self) -> QueryBorrowChecked<'_, Q>
However, changing it to
pub fn iter(&self) -> QueryBorrowChecked<'_, Q>
still compiles (a lot of warnings suggesting to drop the "mut" in systems appear, though).
This would be good for ergonomics, as instead of declaring queries as mutable in systems we wouldn't have to.
The following example:
fn greet_people(
    time: Res<Time>, mut timer: ResMut<GreetTimer>, mut query: Query<(&Person, &Name)>) {
    for (_person, name) in &mut query.iter() {
            println!("hello {}!", name.0);
        }
}

would then be:
fn greet_people(
    time: Res<Time>, mut timer: ResMut<GreetTimer>, query: Query<(&Person, &Name)>) {
   for (_person, name) in &mut query.iter() {
            println!("hello {}!", name.0);
        }
}

You still need to &mut query.iter() as QueryBorrowChecked.iter() does take it mutably.
I have the change in a local branch, if my proposal makes sense, I can fix the warnings and open PR and update the docs.

I agree that we could get away with this today and it would still be safe because we do run-time borrow checking. I ultimately want to remove the run-time checks completely as an optimization, which will require us to rely on lifetimes / mutable borrows. So while its safe now, it would be a breaking to remove runtime checks.
Instead, I think we can start moving the api in the direction it will take with compile-time borrow checking, which should make the api a bit more usable. Specifically, now the Bevy 0.2 has "read only" query traits, we can make "read only queries" immutable borrows (query.iter()) and write queries mutable borrows (query.iter_mut())

That makes sense to me :slightly_smiling_face:


Exit early when logging info is not set

Description

Previously the code "accepts" config with missing logging info, but then fail on the first call of any log method
Exit early when logging info is not set
It changes app init

Type of change

[ ] Refactor
[x] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Unit tests and integration tests should pass

Makes sense.
/lgtm

/approve

/hold

logging config should not be required, we should default to INFO level logging if the config file doesn't specify a level.

/unhold

/lgtm

/lgtm


Change bifi to pancake

tested, seems to update the TVL locally.

Merging the change manually, as I need to rewrite the commit history first.

Merging the change manually, as I need to rewrite the commit history first.


Create model domain polygons from cross-section extents

We need to create polygons for the extent of each HEC-RAS model processed by ras2fim. These polygons will eventually have two functions (not within the scope of this task). We will use them to determine when a feature_id has reached its horizontal flood boundary and as a reference layer for FIM users.
It would probably be best to include this in src/create_shapes_from_hecras.py using the df_xs geodataframe  (created on line 703) to get the first and last vertices from each cross-section. Each HEC-RAS model should have just one polygon with the appropriate metadata attached.

Here's a screenshot of the REM. The domain polygon should be similar to the extent of the REM in this section: connecting the ends of the cross-sections.

Yes, this is great!


feat(proto-cli): added custom type fetching

Also added custom type object when "custom_type" decorator is found

CI broken, omw to fix it, don't merge

bors merge

Configuration problem: bors.toml: not found

no luck…
I don't know how to merge and it seems I don't have on this repo
@Ben-Rey please see if you can merge


ValueError while using --optimize_on_cpu

Traceback (most recent call last): | 1/87970 [00:00<8:35:35, 2.84it/s]
File "./run_squad.py", line 990, in
main()
File "./run_squad.py", line 922, in main
is_nan = set_optimizer_params_grad(param_optimizer, model.named_parameters(), test_nan=True)
File "./run_squad.py", line 691, in set_optimizer_params_grad
if test_nan and torch.isnan(param_model.grad).sum() > 0:
File "/people/sanjay/anaconda2/envs/bert_pytorch/lib/python3.5/site-packages/torch/functional.py", line 289, in isnan
raise ValueError("The argument is not a tensor", str(tensor))
ValueError: ('The argument is not a tensor', 'None')

Command:
CUDA_VISIBLE_DEVICES=0 python ./run_squad.py
--vocab_file bert_large/uncased_L-24_H-1024_A-16/vocab.txt
--bert_config_file bert_large/uncased_L-24_H-1024_A-16/bert_config.json
--init_checkpoint bert_large/uncased_L-24_H-1024_A-16/pytorch_model.bin
--do_lower_case
--do_train
--do_predict
--train_file squad_dir/train-v1.1.json
--predict_file squad_dir/dev-v1.1.json
--learning_rate 3e-5
--num_train_epochs 2
--max_seq_length 384
--doc_stride 128
--output_dir outputs
--train_batch_size 4
--gradient_accumulation_steps 2
--optimize_on_cpu
Error while using --optimize_on_cpu only.
Works fine without the argument.
GPU: Nvidia GTX 1080Ti Single GPU.
PS: I can only fit in train_batch_size 4 on the memory of a single GPU.

Thanks! I pushed a fix for that, you can try it again. You should be able to increase a bit the batch size.
By the way, the real batch size that is used on your the gpu is train_batch_size / gradient_accumulation_steps so 2 in your case. I think you should be able to go to 3 with --optimize_on_cpu
The recommended batch_size for BERT large on SQuaD is 24 so you could try the following possibility to get to this batch_size:

keeping the same 'real batch size' that you currently have but just a bigger batch_size --train_batch_size 24 --gradient_accumulation_steps 12
trying a 'real batch size' of 3 with optimization on cpu --train_batch_size 24 --gradient_accumulation_steps 8 --optimize_on_cpu
switching to fp16 (implies optimization on cpu): --train_batch_size 24 --gradient_accumulation_steps 6 or 4 --fp16

If your GPU support fp16, the last solution should be the fastest otherwise, the second should be the fastest. The first solution should work out-of-the box and give better results (EM, F1) but you won't have any speed-up.

Should be fixed now. Don't hesitate to re-open an issue if needed. Thanks for the feedback!

Yes it works now!
With

--train_batch_size 24 --gradient_accumulation_steps 8 --optimize_on_cpu

I get {"exact_match": 83.78429517502366, "f1": 90.75733469379139} which is pretty close.
Thanks for this amazing work!


run test

hello,maxbren! I hava download your code and want to tun it on my local pc. You say that change the single agent as false. But,I can not fint it.  Could you telll me?

I find the single agent.  But, when I run it, it occurs

do you know this?

single_agent is in constants.json in the constants directory (or constants-grid.json if running random or grid search). As for the error that might mean your traci installation is messed up. Have you gotten traci to work on your own outside of this repo?

But, my traci and sumo is run well ! It can run normally!

Hello, Maxbren! I am sure my sumo setting is right!
I have test it on my local pc by win and linux.
My sumo version is 1.6.0 and which version do you update?
In my pycharm, it shows the envrioment.py reset can not connect?
Do you can run normally?

Hello, Maxbren! I am sure my sumo setting is right! I have test it on my local pc by win and linux. My sumo version is 1.6.0 and which version do you update? In my pycharm, it shows the envrioment.py reset can not connect? Do you can run normally?

Hello, did you run the model? Could you tell me to get the outputs from the trained model?


Compatibility with SED-ML level 1 version 2

= Description =

Make the package compatible with all level 1 version 2 features.

= Context =

SED-ML is the chosen language for encoding work flows in !BioPreDyn; the latest version of the language is L1V2.

= Success criteria =

L1V2 files can be read and executed with the prototype.

= Expected issues =

Some features are used by the language but no library currently supports them.
Some features are supported by libraries in a language different from C++ or Python.

Imported from trac issue 22.  Created by bmoreau on 2014-02-20T16:50:48, last modified: 2015-01-19T11:49:27


tree used in the guide isn't available on osx, some linux distros

Not sure how big of a deal this is, but was just thinking about it and wanted to get others' thoughts.
The cargo guide, in the creating a new project section, shows:
$ cd hello_world
$ tree .
.
├── Cargo.toml
└── src
    └── main.rs

1 directory, 2 files

OSX doesn't come with tree -- a quick brew install tree and I was good to go, though.
On my cursory research, it looks like ubuntu comes with tree, but some others might have to apt-get it?
Windows users have tree, since it was originally a DOS command (TIL!), but most examples show just tree, not tree . -- is that equivalent? (Sorry, don't have a quickly accessible windows machine to check with).
Should we link to instructions for installing tree? Is there a different command that would be more cross-platform and achieve approximately the same results? Or should we assume that readers of the cargo guide will figure it out?

Ah I'd be fine just switching to something like find . or some equivalent, no need to go to great lengths to explain I think

Just FYI, tree . is equivalent to tree on Windows.

Echoing my suggestion in #5382, perhaps use exa 😉.


Move Nimble out of Nim compiler wrapper

Description of changes
Nimble doesn't need to be bundled with the Nim compiler and shouldn't be tied to a specific Nim compiler.
Package the alternate package tool atlas.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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

[ ] Fits CONTRIBUTING.md.

Please rename commits to comply with CONTRIBUTING.md.

Please rename commits to comply with CONTRIBUTING.md.

Please be more specific so I don't have to fix the messages twice.

https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions

Hi, this broke master and causes eval errors on ofborg: https://gist.github.com/GrahamcOfBorg/7a33204709bf948180670867a9e22e02. I will push a new PR to fix it.


New Log files does not pick when frontail running

Hi Mthenw,
Thank you for giving this tool. This has helped my developers to view logs.
But I needed one more help in knowing how to enable new log files in same folder to be picked. I am running below command. Every day new logs will be added to the logs folder.
Now I have to kill fontail and start every day.
frontail --disable-usage-stats -t dark -d /usr/local/lib/node_modules/@liquidapps/dsp/logs/*

Hey, could you provide more details? Which version do you use? Which OS?

Sorry for the late response.
frontail --version
4.9.1
I am running on Ubuntu-18

Interested in this as well so that it will always tail the most recent file with a given pattern without needing a restart.
OSX Host.

Is this feature available or needs to be worked?


DateTimeRange in Postgres not supported

Affected module
Ingestion Framework
Describe the bug
DateTimeRange type of Postgres is not ingested but fails instead with:
Object of type 'DateTimeRange' is not JSON serializable
Error fetching sample data: 'DataType' object has no attribute 'dialect_impl'

To Reproduce
create a table with a column of type DateTimeRange and try to run the Postgres profiler on it
Expected behavior
it should work/profile
Version:

OpenMetadata version: 1.0.1
OpenMetadata Ingestion package version: <IP_ADDRESS>

Additional context
Add any other context about the problem here.

fixed in https://github.com/open-metadata/OpenMetadata/pull/12583


GlideModuleUnsafeOkHttp

I have implemented UsageExampleGlideModuleUnsafeOkHttp.java as per the given example. Still not able to load Unsafe SSL URL Image.

me too


Support for multiple drop-shadows per layer.

This adds support for multiple drop shadows per layer.
Generator JSON introduces a new property dropShadowMult which has an array of multiple drop shadows. However, it is not consistent with the use of dropShadowMult and dropShadow so I transform them all to a list in svgOMG.

Also noticed that this commit includes .DS_Store files. You will want to update your .gitignore to ignore them and git rm the ones included in this commit.

The last two patches are preparation. I will turn over the other filter effects as I edit them similarly to drop shadow.

Looks good to me! Feel free to merge when ready.

Oh wait. Do you want to drop a .DS_Store into the .gitignore to avoid you accidentally adding them again.

Oh too late :D

Heh, I wonder why we didn't create the project with this options already.


onListMarketBook is not a function

Hey!
I try to get listMarketBook but instead an error occurs:
BetFair/node_modules/betfair/lib/betfair_invocation.js:196
        emulator.onListMarketBook(self.response.result);
                 ^

TypeError: emulator.onListMarketBook is not a function

Could you fix that?

You could add module.exports = require('./lib/emulator'); to the index.js file and the issue will be solved.


container has runAsNonRoot and image will run as root

I am trying to install solr as per below link.
https://apache.github.io/solr-operator/docs/local_tutorial.html
Zookeeper operator is installed successfully. But getting error in Solr operator installation.

The official solr image should not be running as root, at least not on later releases. Can you include the exact helm command/yaml files you are using to install?

I m not changing anything in the yaml file
https://nightlies.apache.org/solr/release/operator/crds/v0.5.0/all-with-dependencies.yaml
helm install solr-operator apache-solr/solr-operator --version 0.5.0

I m not changing anything in the yaml file
https://nightlies.apache.org/solr/release/operator/crds/v0.5.0/all-with-dependencies.yaml
helm install solr-operator apache-solr/solr-operator --version 0.5.0

Can you post the error that you get and where it comes from? Can't do much without more information.

Below is the output of kubectl describe

Name:         solr-operator-b5548847b-f7x7w
Namespace:    default
Priority:     0
Node:         pbg-vubs92/<IP_ADDRESS>
Start Time:   Tue, 18 Jan 2022 14:40:16 +0000
Labels:       control-plane=solr-operator
istio.io/rev=default
pod-template-hash=b5548847b
security.istio.io/tlsMode=istio
service.istio.io/canonical-name=solr-operator
service.istio.io/canonical-revision=latest
Annotations:  kubectl.kubernetes.io/default-container: solr-operator
kubectl.kubernetes.io/default-logs-container: solr-operator
prometheus.io/path: /stats/prometheus
prometheus.io/port: 15020
prometheus.io/scrape: true
sidecar.istio.io/status:
{"initContainers":["dns-probe","istio-init"],"containers":["istio-proxy"],"volumes":["cilium-unix-sock-dir","istio-envoy","istio-data","is...
Status:       Pending
IP:           <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/solr-operator-b5548847b
Init Containers:
dns-probe:
Container ID:
Image:         busybox:1.31.1
Image ID:
Port:
Host Port:
Command:
sh
-c
max=120; i=0; until nslookup kube-dns.kube-system.svc.cluster.local; do i=$((i + 1)); if [ $i -eq $max ]; then echo timed-out; exit 1; else sleep 1; fi done
State:          Waiting
Reason:       CreateContainerConfigError
Ready:          False
Restart Count:  0
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ds8dx (ro)
istio-init:
Container ID:
Image:         quay.io/cilium/istio_proxy:1.10.4
Image ID:
Port:
Host Port:
Args:
istio-iptables
-p
15001
-z
15006
-u
1337
-m
TPROXY
-i
*
-x

  -b
  *
  -d
  15090,15021,15020
State:          Waiting
  Reason:       PodInitializing
Ready:          False
Restart Count:  0
Limits:
  cpu:     2
  memory:  1Gi
Requests:
  cpu:        100m
  memory:     128Mi
Environment:  <none>
Mounts:
  /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ds8dx (ro)

Containers:
solr-operator:
Container ID:
Image:         apache/solr-operator:v0.5.0
Image ID:
Port:          8080/TCP
Host Port:     0/TCP
Args:
-zk-operator=true
--tls-skip-verify-server=true
--tls-watch-cert=true
--health-probe-bind-address=:8081
--metrics-bind-address=:8080
--leader-elect=true
State:          Waiting
Reason:       PodInitializing
Ready:          False
Restart Count:  0
Liveness:       http-get http://:15020/app-health/solr-operator/livez delay=15s timeout=1s period=20s #success=1 #failure=3
Readiness:      http-get http://:15020/app-health/solr-operator/readyz delay=5s timeout=1s period=10s #success=1 #failure=3
Environment:
POD_NAMESPACE:  default (v1:metadata.namespace)
POD_NAME:       solr-operator-b5548847b-f7x7w (v1:metadata.name)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ds8dx (ro)
istio-proxy:
Container ID:
Image:         quay.io/cilium/istio_proxy:1.10.4
Image ID:
Port:          15090/TCP
Host Port:     0/TCP
Args:
proxy
sidecar
--domain
$(POD_NAMESPACE).svc.cluster.local
--serviceCluster
solr-operator.default
--proxyLogLevel=warning
--proxyComponentLogLevel=misc:error
--log_output_level=default:info
--concurrency
2
State:          Waiting
Reason:       PodInitializing
Ready:          False
Restart Count:  0
Limits:
cpu:     2
memory:  1Gi
Requests:
cpu:      100m
memory:   128Mi
Readiness:  http-get http://:15021/healthz/ready delay=1s timeout=3s period=2s #success=1 #failure=30
Environment:
JWT_POLICY:                    third-party-jwt
PILOT_CERT_PROVIDER:           istiod
CA_ADDR:                       istiod.istio-system.svc:15012
POD_NAME:                      solr-operator-b5548847b-f7x7w (v1:metadata.name)
POD_NAMESPACE:                 default (v1:metadata.namespace)
INSTANCE_IP:                    (v1:status.podIP)
SERVICE_ACCOUNT:                (v1:spec.serviceAccountName)
HOST_IP:                        (v1:status.hostIP)
CANONICAL_SERVICE:              (v1:metadata.labels['service.istio.io/canonical-name'])
CANONICAL_REVISION:             (v1:metadata.labels['service.istio.io/canonical-revision'])
PROXY_CONFIG:                  {"interceptionMode":"TPROXY"}
  ISTIO_META_POD_PORTS:          [
                                     {"name":"metrics","containerPort":8080,"protocol":"TCP"}
                                 ]
  ISTIO_META_APP_CONTAINERS:     solr-operator
  ISTIO_META_CLUSTER_ID:         Kubernetes
  ISTIO_META_INTERCEPTION_MODE:  TPROXY
  ISTIO_METAJSON_ANNOTATIONS:    {"prometheus.io/scrape":"true"}

  ISTIO_META_WORKLOAD_NAME:      solr-operator
  ISTIO_META_OWNER:              kubernetes://apis/apps/v1/namespaces/default/deployments/solr-operator
  ISTIO_META_MESH_ID:            cluster.local
  TRUST_DOMAIN:                  cluster.local
  ISTIO_PROMETHEUS_ANNOTATIONS:  {"scrape":"true","path":"","port":""}
  ISTIO_KUBE_APP_PROBERS:        {"/app-health/solr-operator/livez":{"httpGet":{"path":"/healthz","port":8081,"scheme":"HTTP"},"timeoutSeconds":1},"/app-health/solr-operator/readyz":{"httpGet":{"path":"/readyz","port":8081,"scheme":"HTTP"},"timeoutSeconds":1}}
Mounts:
  /etc/istio/pod from istio-podinfo (rw)
  /etc/istio/proxy from istio-envoy (rw)
  /var/lib/istio/data from istio-data (rw)
  /var/run/cilium from cilium-unix-sock-dir (rw)
  /var/run/secrets/istio from istiod-ca-cert (rw)
  /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ds8dx (ro)
  /var/run/secrets/tokens from istio-token (rw)

Conditions:
Type              Status
Initialized       False
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
cilium-unix-sock-dir:
Type:          HostPath (bare host directory volume)
Path:          /var/run/cilium
HostPathType:
istio-envoy:
Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:     Memory
SizeLimit:
istio-data:
Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
istio-podinfo:
Type:  DownwardAPI (a volume populated by information about the pod)
Items:
metadata.labels -> labels
metadata.annotations -> annotations
limits.cpu -> cpu-limit
requests.cpu -> cpu-request
istio-token:
Type:                    Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds:  43200
istiod-ca-cert:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      istio-ca-root-cert
Optional:  false
kube-api-access-ds8dx:
Type:                    Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds:  3607
ConfigMapName:           kube-root-ca.crt
ConfigMapOptional:
DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type     Reason            Age                 From               Message

Warning  FailedScheduling  6m36s               default-scheduler  0/1 nodes are available: 1 node(s) were unschedulable.
Warning  FailedScheduling  2m (x3 over 5m30s)  default-scheduler  0/1 nodes are available: 1 node(s) were unschedulable.
Normal   Scheduled         45s                 default-scheduler  Successfully assigned default/solr-operator-b5548847b-f7x7w to pbg-vubs92
Normal   Pulled            11s (x5 over 44s)   kubelet            Container image "busybox:1.31.1" already present on machine
Warning  Failed            11s (x5 over 44s)   kubelet            Error: container has runAsNonRoot and image will run as root (pod: "solr-operator-b5548847b-f7x7w_default(c8c06a03-ead6-4248-a6e2-23ad3550193d)", container: dns-probe)

Ahh so it's the sidecar container that cannot be run as non-root. We need to specify that only the Solr Operator container in the pod must be run as non-root.


Helical FBP does not work properly

The helical FBP reconstruction does not work properly and we are currently working on fixing this.

Helical FBP works now, but needs speed improvement.


Move cluster-capabilities-table to a headless bundle

Move cluster-capabilities-table to a headless bundle and include it as a page instead of reading the file
This prevents the table to automatically be included on pages of other bundles.
By including the page instead of reading the file also the shortcodes in the table are expanded correctly.
This fixes broken links in the table.
Fixes https://github.com/rancher/docs/issues/2577

@bashofmann I accidentally merged this too soon. After merging these changes I don't see the tables. Were you able to see the tables if you build the docs locally with `./scripts/dev'?

@catherineluse There seems to be a difference between doing a fresh build and what the watch process is doing when you change something. It was definitely showing up while I was working on it, but when doing a fresh built it's not working. I'm very sorry for that :(
I also figured out the reason, you can only use .Site.GetPage on a complete page bundle and include the index.md and not on a single file, at least on a fresh build.
I opened https://github.com/rancher/docs/pull/2592 which fixes this for me.

Thank you @bashofmann looks good now.


narsil: 1.3.0-234-g228c4f0cb -> 1.3.0-353-g7a242f456

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for narsil is: Unofficial rewrite of Sil, a roguelike influenced by Angband
meta.homepage for narsil is: https://github.com/NickMcConnell/NarSil/
meta.changelog for narsil is: https://github.com/NickMcConnell/NarSil/releases/tag/1.3.0-353-g7a242f456
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.0-353-g7a242f456 in filename of file in /nix/store/7qyl7spzwi7zxmqsfi010x40c7wkj5hv-narsil-1.3.0-353-g7a242f456

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

narsil

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7qyl7spzwi7zxmqsfi010x40c7wkj5hv-narsil-1.3.0-353-g7a242f456 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A narsil https://github.com/r-ryantm/nixpkgs/archive/20ec8cb38e646bdeda688eb69e2b3bf78126d5fe.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/20ec8cb38e646bdeda688eb69e2b3bf78126d5fe#narsil

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7qyl7spzwi7zxmqsfi010x40c7wkj5hv-narsil-1.3.0-353-g7a242f456
ls -la /nix/store/7qyl7spzwi7zxmqsfi010x40c7wkj5hv-narsil-1.3.0-353-g7a242f456/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

narsil

Maintainer pings
cc @nanotwerp @x123 for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

While the build completes, the game seems to panic on the use of a forge, which appears to be an upstream bug. I've reported it to upstream here: https://github.com/NickMcConnell/NarSil/issues/728

Closing this in favor of https://github.com/NixOS/nixpkgs/pull/350228 which should fix both the update-script to use the correct branch and put narsil on the latest main branch version.


[Feature]: load agentscope studio model from python

AgentScope is an open-source project. To involve a broader community, we recommend asking your questions in English.
Is your feature request related to a problem? Please describe.
agentscope studio is awesome, if it could be load from python, it will be great.
Describe the solution you'd like
load agentscope studio html from python
Describe alternatives you've considered
or transfer python codes to agentscope html

Thanks for your attention.
I want to confirm if the "agentscope studio html" refers to the config exported from workstation(the dragging-and-dropping interface)?

Thanks for your attention.
I want to confirm if the "agentscope studio html" refers to the config exported from workstation(the dragging-and-dropping interface)?

yes, i hope i can load python code in the inrerface

Thank you for your suggestions.
However, extracting a workflow from Python code is essentially equivalent to building a compiler system, which is challenging for our limited developement team.
For now, we are planning to support save and load workflow in our workstation for continuous development, hoping these features could help.

Thanks for your attention again.
If you have any other questions, please feel free to create a new issue, closing this for now.


chore: removed wrong comment and updated according to python samples

b/155662652

Thanks @stephaniewang526 @chingor13


proposal: tape-join gate

I'd like to add a gate for joining tapes to the standard library. It's a fairly common operation, easily available in the other languages.
Here's an example that does what is says on the tin:
=join |=  {a/tape b/(list tape)}
^-  tape
?~  b  ~
%+  weld  i.b
?~  t.b  ~
(weld a $(b t.b))

(join " - " ~["foo" "bar" "baz"]) produces "foo - bar - baz".
Is it worth using a wet gate here? It seems like joining a collection-of-collections is generically useful.
=join |*  {a/(list) b/(list (list))}
=.  a  `_?>(?=(^ b) i.b)`a
|-  ^+  a
?~  b  ~
%+  weld  i.b
?~  t.b  ~
(weld a $(b t.b))

(Callers then have to supply the cast: (join " - " (limo ~["foo" "bar" "baz"])))

This is good (though maybe just for tapes, not sure about the generic), but...
What would be even more cool is a ++by-style two letter door for tapes.  The string handling code is really old and ad hoc...  a much more complex proposal, I understand!
Sent from my iPhone

On Sep 30, 2016, at 1:49 PM, Joe Bryan<EMAIL_ADDRESS>wrote:
I'd like to add a gate for joining tapes to the standard library. It's a fairly common operation, easily available in the other languages.
Here's an example that does what is says on the tin:
=join |=  {a/tape b/(list tape)}
^-  tape
?~  b  ~
%+  weld  i.b
?~  t.b  ~
(weld a $(b t.b))
(join " - " ~["foo" "bar" "baz"]) produces "foo - bar - baz".
Is it worth using a wet gate here? It seems like joining a collection-of-collections is generically useful.
=join |*  {a/(list) b/(list (list))}
=.  a  _?>(?=(^ b) i.b)a
|-  ^+  a
?~  b  ~
%+  weld  i.b
?~  t.b  ~
(weld a $(b t.b))
(Callers then have to supply the cast: (join " - " (limo ~["foo" "bar" "baz"])))
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't know of many generic, tape-specific gates -- are you suggesting that new ones should be added? Any recommendations for how ++join would work in such a door?
Also, would this be separate from the oft-proposed list engined (++of)? I started working on that for my own amusement, just folding Section 2bB into a door.

Closing this one as it doesn't seem to have gone anywhere.

I've written several versions of this in several places, will probably just PR a generic stdlib implementation at some point. The issue certainly doesn't need to be open (we'd drown in issues for stdlib proposals ...)


Can only connect when port appended to host

Issue: When running the localtunnel-server, the client can only connect when the port is appended to the host URL.

Here are the results: (Note: Replaced IP and domain info for privacy.)
$ lt --host http://domain.com --port 3040
tunnel server offline: connect ECONNREFUSED <IP_ADDRESS>:80, retry 1s
tunnel server offline: connect ECONNREFUSED <IP_ADDRESS>:80, retry 1s
tunnel server offline: connect ECONNREFUSED <IP_ADDRESS>:80, retry 1s
... repeats

$ lt --host http://domain.com:3040
Complains not enough params: Usage: lt --port [num]

The only working solution is this:
$ lt --host http://domain.com:3040 --port 3040
your url is: http://xratdozebf.domain.com:3040

OS:
$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.10.1
BuildVersion:	14B25
Node (io.js) version:
$ node -v
v2.0.1

Doh! I completely misunderstood what the --port parameter was for. The parameter is for pointing it to your local server instance NOT the remote port where the localtunnel server lives.


Fix coverage report

make coverage was failing after the change to make JS metatype a
module. First, test-javascript now may depend on modules, so check
should depend on them. Second, duktape is now compiled from the module
directory, so fix the removal from the coverage results to include them
specifically.
Signed-off-by: Caio Marcelo de Oliveira Filho<EMAIL_ADDRESS>

@ricardotk @dorileo

:+1:

Applied in 90af0e9438e681383318bb77821e001d3c74cedb.


RD2: Handle Cancel and Save buttons on save/error

Display an error when the user is missing field permissions and disable the [Save] button.
Disable [Cancel] and [Save] buttons when the record is being saved.

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

Tracking W-7865067

@rjanjanam , the PR has merge conflicts. I am going to resolve it now, but once it is resolved in a new commit, the code needs to be checked out and the dev_org flow re-run on the same NPSP org.
CC @rponti-sforg , @ravensisco

@rjanjanam , the merge conflict has been resolved. Can you please re-deploy code onto the existing NPSP scratch org? Thanks.


Adding colleges belonging to Colorado Community College System board

All colleges on this list use an email system provided by the Colorado Community College System board. All student emails from the colleges below use the cccs.edu domain (https://cccs.edu/ )
Added additional/remaining Colorado State/Community colleges that belong to the Colorado Community College System board
(Seen here for list: https://www.cccs.edu/college/ )
In the initial commit to cccs.edu, looks like Arapahoe Community College was already added. It's the same case with the other colleges. That all of the colleges use the same domain for their email system.
Colorado Northwestern Community College:
https://www.cncc.edu/degrees/craig/cybersecurity
Community College of Aurora:
https://www.ccaurora.edu/programs-classes/departments/cis/cyber-security
Community College of Denver:
https://www.ccd.edu/program/cybersecurity-center
Front Range Community College:
https://www.frontrange.edu/programs-and-courses/a-z-program-list/computer-networking-virtualization-cybersecurity
Lamar Community College:
http://catalog.lamarcc.edu/preview_program.php?catoid=4&poid=195&returnto=117
Morgan Community College:
https://erpdnssb.cccs.edu/PRODMCC/bwckschd.p_disp_detail_sched?term_in=202330&crn_in=31184
Northeastern Junior College:
https://erpdnssb.cccs.edu/PRODNJC/bwckschd.p_disp_detail_sched?term_in=202330&crn_in=30182
Otero College:
https://www.ed2go.com/otero/online-courses/introduction-cybersecurity/
Pikes Peak State College:
https://www.pikespeak.edu/programs/cybersecurity/cybersecurity-program-options.php
Pueblo Community College:
https://pueblocc.edu/Programs/CSE
Red Rocks Community College:
https://www.rrcc.edu/cyber/program-info
Trinidad State College:
https://trinidadstate.edu/cis/index.html

@ZorudaRinku First stage of verification passed, official domain is cccs.edu as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@ZorudaRinku I am sorry, the domain cccs.edu is removed from our trusted domains list because the school allows to register an email address there even if you are not a student of the school. If you are the student of this school, please apply with official document (OFFICIAL DOCUMENT tab at https://www.jetbrains.com/shop/eform/students).


Alternate Flash Policy Port  - needs documenting

Lots of searching through docs and web to find how to configure this with not much success, so here is one solution.
Needed to change the flash policy port from the default 10843 (issues with ISP opening ports).  I found  information on how to run on another port for the server but still kept getting SecurityError on the client.
In this example the node server is running with SSL and is only used for socket.io communication (not feeding up any HTML).  The flash policy port has been reconfigured to also listen on port 3300
SERVER
var fs = require('fs');

var options = {
  key: fs.readFileSync('/etc/ssl/ebscerts/wildcard.my_example.com.no_pass.key'),
  cert: fs.readFileSync('/etc/ssl/ebscerts/wildcard.my_example.com.crt'),
  ca: fs.readFileSync('/etc/ssl/ebscerts/bundle.crt')
};

var app = require('https').createServer(options, handler)
  , io = require('socket.io').listen(app);

app.listen(3300);

//for testing
function handler (req, res) {
      res.writeHead(200);
    res.end("welcome to ebidnsave\n");
}

//production settings
io.enable('browser client minification');  // send minified client
io.enable('browser client etag');          // apply etag caching logic based on version number
io.enable('browser client gzip');          // gzip the file
io.set('log level', 1);                              // reduce logging
//io.set('match origin protocol', 'true');
io.set('flash policy port', 3300);       //override policy port
io.set('transports', [                     // enable all transports (optional if you want flashsocket)
    'websocket'
  , 'flashsocket'
  , 'htmlfile'
  , 'xhr-polling'
  , 'jsonp-polling'
]);

Finally realized the client also has to be overridden.  This can be done by passing the 'flash policy port' on the io.connect call.
CLIENT
   //socketAddr is server uri  ex. https://ww2.my_example.com:3300
   var socket = io.connect(socketAddr,{'flash policy port':3300});
   socket.on('connect', function () { .....

The above works with IE9 (seems to work with IE8 with a quick test).  BUT there is still a delay in setting up the socket which I think is due to flashsocket trying port 843 first.
Socket.io.client documentation lists some of the options that can be configured but does not mention 'flash policy port'.
In digging through the file I found on line 1512 of 0.9.10 this list of options that  if passed are merged in and override defaults. Not recommending others be changed.

 function Socket (options) {
    this.options = {
        port: 80
      , secure: false
      , document: 'document' in global ? document : false
      , resource: 'socket.io'
      , transports: io.transports
      , 'connect timeout': 10000
      , 'try multiple transports': true
      , 'reconnect': true
      , 'reconnection delay': 500
      , 'reconnection limit': Infinity
      , 'reopen delay': 3000
      , 'max reconnection attempts': 10
      , 'sync disconnect on unload': false
      , 'auto connect': true
      , 'flash policy port': 10843
      , 'manualFlush': false
    };

    io.util.merge(this.options, options);

It would be nice if this could be added to both socket.io and socket.io.client documentation.  Hopes this helps...

Hi, I followed the steps you suggest but the browser warns me of the following:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://teachlr.dev:3006/socket.io/1/?t=1422538971224. This can be fixed by moving the resource to the same domain or enabling CORS.

May you help me?
I used 3006 port


SQLMIonline_kekiran.md

Changes already approved for SQL DB offline migration and updating the same for others as well.

@kekiran007 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add NFNets to keras.applications

Transferring from https://github.com/tensorflow/tensorflow/issues/47233 as requested
System information

TensorFlow version (you are using): 2.4.1
Are you willing to contribute it (Yes/No): Yes, as much as possible but probably need help.

Describe the feature and the current behavior/state.
DeepMind recently introduced their new "Normalizer-Free" NFNets, matching the test accuracy of EfficientNet-B7 on ImageNet while being up to 8.7x faster to train, and their largest models attain a new state-of-the-art top-1 accuracy of 86.5%. It seems fitting that these would be available in keras since they surpass EfficientNets which are already available.
Will this change the current api? How?
This would introduce new APIs i.e., tensorflow.keras.applications.NFNetF0 through to tensorflow.keras.applications.NFNetF6.
Who will benefit with this feature?
Anyone doing image classification, including transfer learning and fine tuning; a large portion of the machine learning community!
Any Other info.
DeepMind's implementation
Other reference implementations (some incomplete):

https://github.com/ypeleg/nfnets-keras
https://github.com/rwightman/pytorch-image-models/blob/master/timm/models/nfnet.py
https://github.com/vballoli/nfnets-pytorch

Any ETAs here?

Hi there,
Yes, we'd welcome such a contribution. However, we have no availability to work on it, so you'd have to open a PR yourself (we will review the PR and guide you). Do you have an ImageNet checkpoint available for the model?

Got it, i'll see if i can make a PR on this. i have some components built in the past but just need to clean it up a bit

@fchollet would you mind tagging Contributions welcome label on this?

@ypeleg any scope to contribute here?

Hello, Thank you for reporting an issue.
We're currently in the process of migrating the new Keras 3 code base from keras-team/keras-core to keras-team/keras.
Consequently, This issue may not be relevant to the Keras 3 code base . After the migration is successfully completed, feel free to reopen this Issue at keras-team/keras if you believe it remains relevant to the Keras 3 code base. If instead this Issue is a bug or security issue in legacy tf.keras, you can instead report a new issue at keras-team/tf-keras, which hosts the TensorFlow-only, legacy version of Keras.
To know more about Keras 3, please read https://keras.io/keras_core/announcement/


Pip install failing on Ubuntu 12.04, Python 3.4.3

This is the first time I have attempted to utilize this library, so hopefully I am missing something easy.
I installed the dependencies:
apt-get install libxml2-dev libxmlsec1-dev
A pip install xmlsec==0.3.3 generates the following error:
[...]
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DXMLSEC_NO_GOST=1 -D__XMLSEC_FUNCTION__=__FUNCTION__ -DXMLSEC_OPENSSL_098=1 -DXMLSEC_CRYPTO_OPENSSL=1 -DXMLSEC_NO_XKMS=1 -DXMLSEC_CRYPTO=\\openssl\\ -DXMLSEC_NO_SIZE_T= -DXMLSEC_NO_CRYPTO_DYNAMIC_LOADING=1 -Isrc -I/home/daaray/.virtualenvs/market_builder/build/xmlsec/lxml-3.5.0b1-py3.4-linux-x86_64.egg/lxml/includes -I/home/daaray/.virtualenvs/market_builder/build/xmlsec/lxml-3.5.0b1-py3.4-linux-x86_64.egg/lxml -I/usr/include/xmlsec1 -I/usr/include/libxml2 -I/usr/include/python3.4m -I/home/daaray/.virtualenvs/market_builder/include/python3.4m -c src/xmlsec/constants.c -o build/temp.linux-x86_64-3.4/src/xmlsec/constants.o -DXMLSEC_CRYPTO_OPENSSL=1

src/xmlsec/constants.c: In function ‘PyInit_constants’:

src/xmlsec/constants.c:2419:61: error: ‘xmlSecTransformEcdsaSha1Id’ undeclared (first use in this function)

src/xmlsec/constants.c:2419:61: note: each undeclared identifier is reported only once for each function it appears in

src/xmlsec/constants.c:2431:61: error: ‘xmlSecTransformEcdsaSha224Id’ undeclared (first use in this function)

src/xmlsec/constants.c:2443:61: error: ‘xmlSecTransformEcdsaSha256Id’ undeclared (first use in this function)

src/xmlsec/constants.c:2455:61: error: ‘xmlSecTransformEcdsaSha384Id’ undeclared (first use in this function)

src/xmlsec/constants.c:2467:61: error: ‘xmlSecTransformEcdsaSha512Id’ undeclared (first use in this function)

error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

Please advise.

Try installing the latest version of cython first.
pip install "cython==0.23.3"

This seems to be a recent problem from the recent release. It's not supposed to need an install of cython (it should install it using install requires).

Nope. That didn't fix it for me.
Hmm..
For now, ping your version to 0.3.2
pip install "xmlsec==0.3.2"

What version of gcc are you using? I can reproduce the failure with 4.8.2 but it installs successfully with 5.2.0.

4.6.3; I will update. Thanks for the quick responses.

Any ideas @bgaifullin / @changjej  ? I'd like to keep gcc 4.x compatibiltiy.
@daaray For the record, v0.3.2 installs fine on gcc 4.x and has the same features as v0.3.3. The release was intended to support the newest version of cython in combination with gcc 5.x.

Apparently I'm crazy -- make that 0.3.1. 0.3.2 doesn't exist.

Ah, ok...I will go that route 1st; installing v0.3.1. Thanks again.

Reporting back...with gcc v4.6.3 a pip install xmlsec==0.3.1 resulted in the following for me:
src/xmlsec/enc.c: In function '__pyx_import_star_set':

src/xmlsec/enc.c:3384:37: error: lvalue required as left operand of assignment

error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

Try uninstalling cython (hopefully you're in a virtualenv). Sorry this has been so hard to install. Will be working on it.

hrm, a pip freeze inside the virtualenv does not list Cython at all.

This is broken for me too in a deployment script. Trying to come up with a resolution.

I'm currently running it now with a force install of cython as:
pip install "cython<0.23"

This seems to work for me. @daaray ?

Yes, xmlsec v0.3.1 installed successfully with Cython<0.23 in play using gcc 4.6.3. Thanks!

I am running gcc version 4.4.7 and can not install it even with:
pip install "cython<0.23"
pip install "xmlsec==0.3.1"

Fresh Ubuntu 14.04 with dependences resolved:
Python 2.7.6
gcc (Ubuntu 4.8.4-2ubuntu1~14.04)
pip 7.1.2
setuptools 18.7.1
libxmlsec1 1.2.18
libxml2 2.9.1
libxslt 1.1.28

I was not able to install xmlsec.
pip install "cython<0.23"
Successfully built cython
Installing collected packages: cython
Successfully installed cython-0.22.1

Following error when installing xmlsec==0.3.1:
Building lxml version 3.5.0.
    Building without Cython.
    Using build configuration of libxslt 1.1.28
    Compile failed: command 'x86_64-linux-gnu-gcc' failed with exit status 4
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/tmp/pip-build-yWkLxX/xmlsec/setup.py", line 121, in <module>
        make_extension('xmlsec.template'),
      File "/usr/lib/python2.7/distutils/core.py", line 111, in setup
        _setup_distribution = dist = klass(attrs)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__
        self.fetch_build_eggs(attrs['setup_requires'])
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 313, in fetch_build_eggs
        replace_conflicting=True,
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 846, in resolve
        dist = best[req.key] = env.best_match(req, ws, installer)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1091, in best_match
        return self.obtain(req, installer)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1103, in obtain
        return installer(requirement)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 380, in fetch_build_egg
        return cmd.easy_install(req)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 639, in easy_install
        return self.install_item(spec, dist.location, tmpdir, deps)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 669, in install_item
        dists = self.install_eggs(spec, download, tmpdir)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 853, in install_eggs
        return self.build_and_install(setup_script, setup_base)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1081, in build_and_install
        self.run_setup(setup_script, setup_base, args)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1069, in run_setup
        raise DistutilsError("Setup script exited with %s" % (v.args[0],))
    distutils.errors.DistutilsError: Setup script exited with error: command 'x86_64-linux-gnu-gcc' failed with exit status 4

Similar with xmlsec==0.3.3
    Complete output from command python setup.py egg_info:
    x86_64-linux-gnu-gcc: internal compiler error: Killed (program cc1)
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
    Building lxml version 3.5.0.
    Building without Cython.
    Using build configuration of libxslt 1.1.28
    Compile failed: command 'x86_64-linux-gnu-gcc' failed with exit status 4
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/tmp/pip-build-PVFjyb/xmlsec/setup.py", line 121, in <module>
        make_extension('xmlsec.template'),
      File "/usr/lib/python2.7/distutils/core.py", line 111, in setup
        _setup_distribution = dist = klass(attrs)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__
        self.fetch_build_eggs(attrs['setup_requires'])
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 313, in fetch_build_eggs
        replace_conflicting=True,
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 846, in resolve
        dist = best[req.key] = env.best_match(req, ws, installer)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1091, in best_match
        return self.obtain(req, installer)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1103, in obtain
        return installer(requirement)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 380, in fetch_build_egg
        return cmd.easy_install(req)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 639, in easy_install
        return self.install_item(spec, dist.location, tmpdir, deps)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 669, in install_item
        dists = self.install_eggs(spec, download, tmpdir)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 853, in install_eggs
        return self.build_and_install(setup_script, setup_base)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1081, in build_and_install
        self.run_setup(setup_script, setup_base, args)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1069, in run_setup
        raise DistutilsError("Setup script exited with %s" % (v.args[0],))
    distutils.errors.DistutilsError: Setup script exited with error: command 'x86_64-linux-gnu-gcc' failed with exit status 4

Now with pip install "cython==0.23.3"
  Found existing installation: Cython 0.22.1
    Uninstalling Cython-0.22.1:
      Successfully uninstalled Cython-0.22.1
Successfully installed cython-0.23.3

pip install "xmlsec==0.3.1"
Collecting xmlsec==0.3.1
  Using cached xmlsec-0.3.1.tar.gz
    Complete output from command python setup.py egg_info:
    x86_64-linux-gnu-gcc: internal compiler error: Killed (program cc1)
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
    Building lxml version 3.5.0.
    Building without Cython.
    Using build configuration of libxslt 1.1.28
    Compile failed: command 'x86_64-linux-gnu-gcc' failed with exit status 4
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/tmp/pip-build-nozTIu/xmlsec/setup.py", line 121, in <module>
        make_extension('xmlsec.template'),
      File "/usr/lib/python2.7/distutils/core.py", line 111, in setup
        _setup_distribution = dist = klass(attrs)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__
        self.fetch_build_eggs(attrs['setup_requires'])
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 313, in fetch_build_eggs
        replace_conflicting=True,
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 846, in resolve
        dist = best[req.key] = env.best_match(req, ws, installer)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1091, in best_match
        return self.obtain(req, installer)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1103, in obtain
        return installer(requirement)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 380, in fetch_build_egg
        return cmd.easy_install(req)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 639, in easy_install
        return self.install_item(spec, dist.location, tmpdir, deps)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 669, in install_item
        dists = self.install_eggs(spec, download, tmpdir)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 853, in install_eggs
        return self.build_and_install(setup_script, setup_base)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1081, in build_and_install
        self.run_setup(setup_script, setup_base, args)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1069, in run_setup
        raise DistutilsError("Setup script exited with %s" % (v.args[0],))
    distutils.errors.DistutilsError: Setup script exited with error: command 'x86_64-linux-gnu-gcc' failed with exit status 4

Same with "xmlsec==0.3.3"
  Downloading xmlsec-0.3.3.tar.gz
    Complete output from command python setup.py egg_info:
    x86_64-linux-gnu-gcc: internal compiler error: Killed (program cc1)
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
    Building lxml version 3.5.0.
    Building without Cython.
    Using build configuration of libxslt 1.1.28
    Compile failed: command 'x86_64-linux-gnu-gcc' failed with exit status 4
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/tmp/pip-build-WF5EyP/xmlsec/setup.py", line 121, in <module>
        make_extension('xmlsec.template'),
      File "/usr/lib/python2.7/distutils/core.py", line 111, in setup
        _setup_distribution = dist = klass(attrs)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__
        self.fetch_build_eggs(attrs['setup_requires'])
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 313, in fetch_build_eggs
        replace_conflicting=True,
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 846, in resolve
        dist = best[req.key] = env.best_match(req, ws, installer)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1091, in best_match
        return self.obtain(req, installer)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1103, in obtain
        return installer(requirement)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/dist.py", line 380, in fetch_build_egg
        return cmd.easy_install(req)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 639, in easy_install
        return self.install_item(spec, dist.location, tmpdir, deps)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 669, in install_item
        dists = self.install_eggs(spec, download, tmpdir)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 853, in install_eggs
        return self.build_and_install(setup_script, setup_base)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1081, in build_and_install
        self.run_setup(setup_script, setup_base, args)
      File "/home/vagrant/Envs/myproject/local/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 1069, in run_setup
        raise DistutilsError("Setup script exited with %s" % (v.args[0],))
    distutils.errors.DistutilsError: Setup script exited with error: command 'x86_64-linux-gnu-gcc' failed with exit status 4

In this case, Its seems that the problem is related to lxml 3.5.0:
/tmp/easy_install-Ew8_x0/lxml-3.5.0/temp/xmlXPathInitI_sX_B.c:2:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
 main (int argc, char **argv) {

I am also unable to install with this line in the requirements.txt file
git+git://github.com/mehcode/python-xmlsec.git

connection keeps timing out, may be some access rights issue?

Could everyone here try installing again
pip install xmlsec==0.5.0

@mehcode
My system Ubuntu 14.04.3.   python2.7
I tried xmlsec-0.5.0 and Cython-0.23 . Installation worked but I have a segmentation fault when using
xmlsec
Same happens with xmlsec-0.5.0 and Cython-0.23.4
(I trying it in python3-saml with the setup.py edited to point those versions. and got the error when executing the python setup.py test  command.
testValidateSign (tests.src.OneLogin.saml2_tests.utils_test.OneLogin_Saml2_Utils_Test) ...  segment fault.

@pitbulk, thank you for report. I will check this.

Appreciate, let me know if I can help

@bgaifullin , any progress with that issue?

@pitbulk Ive reproduced issue, but I do not found root cause yet.

When I run xmlsec tests with same data - no fault.
When run onelogin tests - fault. :(

I discovered that maybe is related with lxml and the cython version.
I installed
pip install lxml==3.5.0b1
pip install Cython==0.23

and I was able to install xmlsec==0.3.0 and python3-saml  and test no failing.

@pitbulk, Could you check that #20 works for you, please.

@bgaifullin bad news
I created a new virtualenv, cloned python3-saml, edited the setup.py

so now I point your master branch
Searching for xmlsec>=0.3.1
Reading https://github.com/bgaifullin/python-xmlsec/tarball/master

xmlsec 0.5.0, Cython 0.23.4, lxml-3.5.0 are used.
Installation worked
Installed /home/pitbulk/proyectos/toolkits/python3-saml/venv/lib/python2.7/site-packages/lxml-3.5.0-py2.7-linux-x86_64.egg
Finished processing dependencies for python3-saml==1.0.0

but segmentation fault happens on
testValidateSign (tests.src.OneLogin.saml2_tests.utils_test.OneLogin_Saml2_Utils_Test)

segfault at libxmlsec1.so.1.2.20[7f9e82021000+65000]

@pitbulk thank you. I will continue investigation.

@pitbulk You are using xmlsec from pip, the xmlsec from https://github.com/bgaifullin/python-xmlsec has version 0.3.3
root@node-1:~/python3-saml# pip3 show xmlsec
Name: xmlsec
Version: 0.3.3
Location: /usr/local/lib/python3.4/dist-packages/xmlsec-0.3.3-py3.4-linux-x86_64.egg
Requires: lxml
Please try to use the following command to install custom version of xmlsec
/bin/pip install git+http://github.com/bgaifullin/python-xmlsec

@pitbulk I found the reason. As soon as CI has been completed I will merge the fix.

@mehcode Please upload new build to pypi.

I tested, the change solved the issue ;)


Add new preview version 2022-09-30-preview based on 2021-12-01-preview

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
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.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[ ] 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 the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] 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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

/azp run

This pr is to create a new 2022-09-30-preview version based on 2021-12-01-preview. There are no actual update on current apis for MySQL. And we add private link as new apis. The private link features have been approved in previous pr: https://github.com/Azure/azure-rest-api-specs/pull/21957/checks?check_run_id=11093067073.
The linter errors are in previous version and to fix them might be a breaking change for service so we prefer not to touch the current api.

Team , I see that in your previous checkin , you have changed the formatting of the folders : https://github.com/Azure/azure-rest-api-specs/pull/22988
This was not reviewed by any ARM reviewer.
Can you please explain the rationale for this change ? We recommend releasing the api versions with all features together .. not the problem is that when you release this PRs 2022-09-30-preview version SDK it will not have any of the apis from the 2021-12-01-preview. Customers will have trouble managing these separate versions of the SDK in their environments.

Team , I see that in your previous checkin , you have changed the formatting of the folders : #22988
This was not reviewed by any ARM reviewer.
Can you please explain the rationale for this change ? We recommend releasing the api versions with all features together .. not the problem is that when you release this PRs 2022-09-30-preview version SDK it will not have any of the apis from the 2021-12-01-preview. Customers will have trouble managing these separate versions of the SDK in their environments.

Hi @raosuhas , thanks a lot for your review. I understand that when we release a new version, all APIs should be included. We are not to just release private link or any other features alone. In our case, some APIs will not be updated frequently while others may be updated like monthly. So we group swagger into different feature groups and we can upgrade the subservice separately. In this pull request, we do not add a new tag to include private link and we will not release any SDK package with in this pull request. After all features for 2022-009-30-preview are ready, we will raise a new tag to include all APIs either of 2022-09-30-preview or 2021-12-01-preview.

Team , I see that in your previous checkin , you have changed the formatting of the folders : #22988
This was not reviewed by any ARM reviewer.
Can you please explain the rationale for this change ? We recommend releasing the api versions with all features together .. not the problem is that when you release this PRs 2022-09-30-preview version SDK it will not have any of the apis from the 2021-12-01-preview. Customers will have trouble managing these separate versions of the SDK in their environments.

Hi @raosuhas , thanks a lot for your review. I understand that when we release a new version, all APIs should be included. We are not to just release private link or any other features alone. In our case, some APIs will not be updated frequently while others may be updated like monthly. So we group swagger into different feature groups and we can upgrade the subservice separately. In this pull request, we do not add a new tag to include private link and we will not release any SDK package with in this pull request. After all features for 2022-009-30-preview are ready, we will raise a new tag to include all APIs either of 2022-09-30-preview or 2021-12-01-preview.

I see , that makes sense , unfortunately this has triggered a large number of breaking changes errors in the pipleline : https://github.com/Azure/azure-rest-api-specs/pull/23067/checks?check_run_id=12120553598 I am not sure how we deal with this since according to you this should not be a breaking change at all . I will discuss with my colleagues and get back in a bit on this one

Hi @raosuhas, The breaking change is kind of false alarm, you can ignore it. I have approved it
Privatelink in version 2018-06-01 which is for single server implementation which is deprecated.
current private link swagger is first time support for flexibleserver.
Also single server and flexibleserver is 2 different SDK package.

/azp run

approved linter diff as it is green in Linter (staging) and linter error for privatelink is false alarm according to Jianye


Support for installing Drivers

Description of the new feature/enhancement
Appart from apps, Microsoft should also let us install drivers like Nvidia/AMD/Intel display drivers and graphics drivers.
Proposed technical implementation details (optional)
In future I wish all drivers like wifi or touchpad to be available in winget or store and Microsoft promote vendors to use this version of the drivers.

How the drivers installers are different from the other installers?

You might need to manually update drivers or maybe when on a brand-new machine in which you do require manually updating of the drivers such as NVIDIA drivers, you could do so. It should include both beta releases and the latest stable releases for each device.  When the update mechanism is in place, it should  allow an option for beta with use of a --pre flag or similar but that is a separate feature request.

We have features to support .zip and .exe (non-installer) files. If the drivers are in an installable exe, MSI, or MSIX they are supported. Are there other formats we need to consider?

https://github.com/microsoft/winget-cli/issues/140 is support for .zip files.

You also need to add NSIS and 7z formats or CAB files format, lots of drivers come in the later format.


Update nb selected row whene rows(selector).remove()

Hello,
When I use table.rows('.myClass').remove(), the number of select row is not updated.
I must be used :
table.rows('.myClass').deselect().remove().draw();
Can you help me please ?

Yes - very happy to help. Can you post your question in the DataTables forums as indicated in the "New issue" template text. Thanks.


build: Add ens domain to provider info

Relates to #3231
How this PR relates to it
ENS Resolution when adding a provider
How to test it

Open the Safe
Connect a wallet that has a registered ENS domain
Observe ensDomain in redux providers

Screenshots

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.008%) to 32.412%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/logic/wallets/getWeb3.ts
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
3113

Relevant Lines:
8554

💛  - Coveralls

The logic is solid but this still needs the deployment of the Core SDK ENS resolution to build successfully.

I tried by connecting a user with MM that has a ENS name "francotest.eth" but I don't see the name. I'm trying this on Rinkeby
I tried in this PR use the ENS name in the address book to create an entry and the name still works.
ENS name: "francotest.eth"
Address: 0x61a0c717d18232711bC788F19C9Cd56a43cc8872
Rinkeby only

I tried by connecting a user with MM that has a ENS name "francotest.eth" but I don't see the name.

The domain has to be set as the "Primary ENS Name" in the ENS App otherwise it won't be registered with the Resolver Contract

Oh, didn't know about the primary ENS name.
I registered it and now it works


import control segfaults on darwin-arm64

installed via conda, with all the latest numpy, etc, explicitly darwin-arm64 versions.  Also happens on 3.10.8
$ python
Python 3.11.0 | packaged by conda-forge | (main, Jan 14 2023, 12:26:40) [Clang 14.0.6 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import control
[1]    3606 segmentation fault  python

Version is control            conda-forge/noarch::control-0.9.3.post2-pyhd8ed1ab_0
Also happens with 0.9.3.post2 from pip

Can you try import slycot and see if that is the source of the problem?
Also: what version of MacOS are you using?

Possibly another case of https://github.com/python-control/Slycot/issues/186.
Do we have reports of functioning Mac on Arm installs? @murrayrm, @sawyerbfuller you have Macs right?

This is on Ventura 13.1, 16 inch M1 Pro machine
import slycot does indeed also segfault; if this is covered under Slycot#186, feel free to close this issue

Please feel free to report details in https://github.com/python-control/Slycot/issues/186. Particularly if you can post core-dumps, debugger backtraces and results for a self-compiled Slycot instead of the conda-forge package.


docs: Update webhook URL marco to introduce the event filtering system.

This plumbs all_event_types defined on the view function with the
webhook_view to the documentation along with a brief instruction
on how to use the system.

#18392
GIFs or screenshots:
Github

Travis

One thing that I want to note with the PR is that some of the marcos are just duplicate with different different indentation, and some of them don't match each other (like webhook-url-with-bot-email-indented.md and webhook-url-with-bot-email.md). I think this is a consequence of letting people manually copying changes for both files. I checked the documentation and see that there is a indent function that we might probably use.


Add libmad

http://www.underbit.com/products/mad/

@madebr,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@madebr, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

Thanks for the PR!


Update bind-get.md

Fixes #14150

:smile: it was cut-'n-paste directly from my comment. :smile:

ooooops ... look at the diff. My suggestion was a cut-'n-paste directly from the GH comment :point_up:. Your cut from the comment edit (looks like that's what happened) grabbed the escapes.

Arg, Do you miind fixing it?

Sure thing.


Unset values default to null

Describe the feature
When defining a Pinia ORM model in TypeScript, optional fields must be typed as field: type | null because the save method of Pinia ORM repos converts unset values (null, undefined) to null.
However, the usual TypeScript way is declaring an optional field as field?: type, which treats an unset value as undefined. Furthermore, TypeScript's optional chaining (a?.b?.c) and utility types (Required<T>, Partial<T>, etc.) also revolve around the undefined value.
My proposition is to replace the usage of null for unset values with undefined. This seems fairly easy and is rather a matter of acceptance by/relevance to the project.
Additional information

[X] Would you be willing to help implement this feature?

Final checks

[X] Check existing discussions and issues.

Probably something to investigate: attributes default to null, but it seems that relations default to undefined 🤔

I think you are right. But changing this, is something for v2 i think. Because it's a huge breaking change.
But i could already implement this behaviour with a feature flag.

The optional chaining works with undefined and null
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining

If the object accessed or function called using this operator is undefined or null, the expression short circuits and evaluates to undefined instead of throwing an error.


Keywords and other 'reserved' words (incl. other JS keywords) should be disallowed as identifiers

19/06 - New approach

I have renamed jsKeywords to reservedWords, and removed any that are already Elan keywords
I have removed any Elan keywords (e.g. curryKeyword) that we are not using already, and put them in reservedWords also.

TODO - compile rules
I thought there was a compile rule that disallowed the use of an Elan keyword as an identifier - but I just tried it out and that doesn't seem to be the case!  Even if this does work, I think it should be disallowed, as most languages have such a rule. So I  suggest we have two rules giving rise to separate messages e.g.
'print' is a keyword, and may not be used as an identifier
'curry' is a reserved word, and may not be used as an identifier
update
The enforcement of no keywords as identifier appears to be somewhat intermittent - we have both observed this, but no error is being thrown.

Working but in the course of testing found #566 (which has I think been around for a while)