destroy fails if create was not invoked first

Action: Invoke "molecule destroy" for the first time
Expected behavior: "molecule destroy" finds no EC2 instance to destroy, and returns success
Observed behavor: "molecule destroy" fails in ec2_instance.py, in get_default_subnet, with a "TypeError: 'NoneType' object is not subscriptable" error
NOTE: If "molecule create" is called first, followed by "molecule destroy", "molecule destroy" functions as expected. This problem also prevents "molecule check" from working properly.
Example output:
$ python -m venv .venv

$ source .venv/bin/activate

(.venv) $ python -VV
Python 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0]

(.venv) $ python -m site
sys.path = [
    '/home/myuser/projects/ansible/ansible-role-molecule_ec2_template',
    '/usr/lib/python310.zip',
    '/usr/lib/python3.10',
    '/usr/lib/python3.10/lib-dynload',
    '/home/myuser/projects/ansible/ansible-role-molecule_ec2_template/.venv/lib/python3.10/site-packages',
]
USER_BASE: '/home/myuser/.local' (exists)
USER_SITE: '/home/myuser/.local/lib/python3.10/site-packages' (exists)
ENABLE_USER_SITE: False

(.venv) $ python -m pip install --upgrade pip setuptools wheel
Requirement already satisfied: pip in ./.venv/lib/python3.10/site-packages (22.0.2)
Collecting pip
  Using cached pip-23.1.2-py3-none-any.whl (2.1 MB)
Requirement already satisfied: setuptools in ./.venv/lib/python3.10/site-packages (59.6.0)
Collecting setuptools
  Using cached setuptools-67.7.2-py3-none-any.whl (1.1 MB)
Collecting wheel
  Using cached wheel-0.40.0-py3-none-any.whl (64 kB)
Installing collected packages: wheel, setuptools, pip
  Attempting uninstall: setuptools
    Found existing installation: setuptools 59.6.0
    Uninstalling setuptools-59.6.0:
      Successfully uninstalled setuptools-59.6.0
  Attempting uninstall: pip
    Found existing installation: pip 22.0.2
    Uninstalling pip-22.0.2:
      Successfully uninstalled pip-22.0.2
Successfully installed pip-23.1.2 setuptools-67.7.2 wheel-0.40.0

(.venv) $ python -m pip install -r requirements.txt
Collecting ansible==7.5.0 (from -r requirements.txt (line 1))
  Using cached ansible-7.5.0-py3-none-any.whl (43.6 MB)
Collecting ansible-compat==3.0.2 (from -r requirements.txt (line 2))
  Using cached ansible_compat-3.0.2-py3-none-any.whl (19 kB)
Collecting ansible-core==2.14.5 (from -r requirements.txt (line 3))
  Using cached ansible_core-2.14.5-py3-none-any.whl (2.2 MB)
Collecting ansible-lint==6.15.0 (from -r requirements.txt (line 4))
  Using cached ansible_lint-6.15.0-py3-none-any.whl (289 kB)
Collecting arrow==1.2.3 (from -r requirements.txt (line 5))
  Using cached arrow-1.2.3-py3-none-any.whl (66 kB)
Collecting attrs==23.1.0 (from -r requirements.txt (line 6))
  Using cached attrs-23.1.0-py3-none-any.whl (61 kB)
Collecting awscli==1.27.127 (from -r requirements.txt (line 7))
  Using cached awscli-1.27.127-py3-none-any.whl (4.1 MB)
Collecting binaryornot==0.4.4 (from -r requirements.txt (line 8))
  Using cached binaryornot-0.4.4-py2.py3-none-any.whl (9.0 kB)
Collecting black==23.3.0 (from -r requirements.txt (line 9))
  Using cached black-23.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.7 MB)
Collecting boto==2.49.0 (from -r requirements.txt (line 10))
  Using cached boto-2.49.0-py2.py3-none-any.whl (1.4 MB)
Collecting boto3==1.26.127 (from -r requirements.txt (line 11))
  Using cached boto3-1.26.127-py3-none-any.whl (135 kB)
Collecting botocore==1.29.127 (from -r requirements.txt (line 12))
  Using cached botocore-1.29.127-py3-none-any.whl (10.7 MB)
Collecting bracex==2.3.post1 (from -r requirements.txt (line 13))
  Using cached bracex-2.3.post1-py3-none-any.whl (12 kB)
Collecting certifi==2022.12.7 (from -r requirements.txt (line 14))
  Using cached certifi-2022.12.7-py3-none-any.whl (155 kB)
Collecting cffi==1.15.1 (from -r requirements.txt (line 15))
  Using cached cffi-1.15.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (441 kB)
Collecting chardet==5.1.0 (from -r requirements.txt (line 16))
  Using cached chardet-5.1.0-py3-none-any.whl (199 kB)
Collecting charset-normalizer==3.1.0 (from -r requirements.txt (line 17))
  Using cached charset_normalizer-3.1.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (199 kB)
Collecting click==8.1.3 (from -r requirements.txt (line 18))
  Using cached click-8.1.3-py3-none-any.whl (96 kB)
Collecting click-help-colors==0.9.1 (from -r requirements.txt (line 19))
  Using cached click_help_colors-0.9.1-py3-none-any.whl (5.5 kB)
Collecting colorama==0.4.4 (from -r requirements.txt (line 20))
  Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)
Collecting cookiecutter==2.1.1 (from -r requirements.txt (line 21))
  Using cached cookiecutter-2.1.1-py2.py3-none-any.whl (36 kB)
Collecting cryptography==40.0.2 (from -r requirements.txt (line 22))
  Using cached cryptography-40.0.2-cp36-abi3-manylinux_2_28_x86_64.whl (3.7 MB)
Collecting docutils==0.16 (from -r requirements.txt (line 23))
  Using cached docutils-0.16-py2.py3-none-any.whl (548 kB)
Collecting enrich==1.2.7 (from -r requirements.txt (line 24))
  Using cached enrich-1.2.7-py3-none-any.whl (8.7 kB)
Collecting filelock==3.12.0 (from -r requirements.txt (line 25))
  Using cached filelock-3.12.0-py3-none-any.whl (10 kB)
Collecting flake8==6.0.0 (from -r requirements.txt (line 26))
  Using cached flake8-6.0.0-py2.py3-none-any.whl (57 kB)
Collecting hvac==1.1.0 (from -r requirements.txt (line 27))
  Using cached hvac-1.1.0-py3-none-any.whl (144 kB)
Collecting idna==3.4 (from -r requirements.txt (line 28))
  Using cached idna-3.4-py3-none-any.whl (61 kB)
Collecting Jinja2==3.1.2 (from -r requirements.txt (line 29))
  Using cached Jinja2-3.1.2-py3-none-any.whl (133 kB)
Collecting jinja2-time==0.2.0 (from -r requirements.txt (line 30))
  Using cached jinja2_time-0.2.0-py2.py3-none-any.whl (6.4 kB)
Collecting jmespath==1.0.1 (from -r requirements.txt (line 31))
  Using cached jmespath-1.0.1-py3-none-any.whl (20 kB)
Collecting jsonschema==4.17.3 (from -r requirements.txt (line 32))
  Using cached jsonschema-4.17.3-py3-none-any.whl (90 kB)
Collecting markdown-it-py==2.2.0 (from -r requirements.txt (line 33))
  Using cached markdown_it_py-2.2.0-py3-none-any.whl (84 kB)
Collecting MarkupSafe==2.1.2 (from -r requirements.txt (line 34))
  Using cached MarkupSafe-2.1.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (25 kB)
Collecting mccabe==0.7.0 (from -r requirements.txt (line 35))
  Using cached mccabe-0.7.0-py2.py3-none-any.whl (7.3 kB)
Collecting mdurl==0.1.2 (from -r requirements.txt (line 36))
  Using cached mdurl-0.1.2-py3-none-any.whl (10.0 kB)
Collecting molecule==5.0.1 (from -r requirements.txt (line 37))
  Using cached molecule-5.0.1-py3-none-any.whl (239 kB)
Collecting molecule-plugins==23.4.1 (from -r requirements.txt (line 38))
  Using cached molecule_plugins-23.4.1-py3-none-any.whl (67 kB)
Collecting mypy-extensions==1.0.0 (from -r requirements.txt (line 39))
  Using cached mypy_extensions-1.0.0-py3-none-any.whl (4.7 kB)
Collecting packaging==23.1 (from -r requirements.txt (line 40))
  Using cached packaging-23.1-py3-none-any.whl (48 kB)
Collecting pathspec==0.11.1 (from -r requirements.txt (line 41))
  Using cached pathspec-0.11.1-py3-none-any.whl (29 kB)
Collecting platformdirs==3.5.0 (from -r requirements.txt (line 42))
  Using cached platformdirs-3.5.0-py3-none-any.whl (15 kB)
Collecting pluggy==1.0.0 (from -r requirements.txt (line 43))
  Using cached pluggy-1.0.0-py2.py3-none-any.whl (13 kB)
Collecting pyasn1==0.5.0 (from -r requirements.txt (line 44))
  Using cached pyasn1-0.5.0-py2.py3-none-any.whl (83 kB)
Collecting pycodestyle==2.10.0 (from -r requirements.txt (line 45))
  Using cached pycodestyle-2.10.0-py2.py3-none-any.whl (41 kB)
Collecting pycparser==2.21 (from -r requirements.txt (line 46))
  Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting pyflakes==3.0.1 (from -r requirements.txt (line 47))
  Using cached pyflakes-3.0.1-py2.py3-none-any.whl (62 kB)
Collecting Pygments==2.15.1 (from -r requirements.txt (line 48))
  Using cached Pygments-2.15.1-py3-none-any.whl (1.1 MB)
Collecting pyhcl==0.4.4 (from -r requirements.txt (line 49))
  Using cached pyhcl-0.4.4-py3-none-any.whl
Collecting pyrsistent==0.19.3 (from -r requirements.txt (line 50))
  Using cached pyrsistent-0.19.3-py3-none-any.whl (57 kB)
Collecting python-dateutil==2.8.2 (from -r requirements.txt (line 51))
  Using cached python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
Collecting python-slugify==8.0.1 (from -r requirements.txt (line 52))
  Using cached python_slugify-8.0.1-py2.py3-none-any.whl (9.7 kB)
Collecting PyYAML==5.4.1 (from -r requirements.txt (line 53))
  Using cached PyYAML-5.4.1-cp310-cp310-linux_x86_64.whl
Collecting requests==2.30.0 (from -r requirements.txt (line 54))
  Using cached requests-2.30.0-py3-none-any.whl (62 kB)
Collecting resolvelib==0.8.1 (from -r requirements.txt (line 55))
  Using cached resolvelib-0.8.1-py2.py3-none-any.whl (16 kB)
Collecting rich==13.3.5 (from -r requirements.txt (line 56))
  Using cached rich-13.3.5-py3-none-any.whl (238 kB)
Collecting rsa==4.7.2 (from -r requirements.txt (line 57))
  Using cached rsa-4.7.2-py3-none-any.whl (34 kB)
Collecting ruamel.yaml==0.17.22 (from -r requirements.txt (line 58))
  Using cached ruamel.yaml-0.17.22-py3-none-any.whl (107 kB)
Collecting ruamel.yaml.clib==0.2.7 (from -r requirements.txt (line 59))
  Using cached ruamel.yaml.clib-0.2.7-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl (485 kB)
Collecting s3transfer==0.6.1 (from -r requirements.txt (line 60))
  Using cached s3transfer-0.6.1-py3-none-any.whl (79 kB)
Collecting six==1.16.0 (from -r requirements.txt (line 61))
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting subprocess-tee==0.4.1 (from -r requirements.txt (line 62))
  Using cached subprocess_tee-0.4.1-py3-none-any.whl (5.1 kB)
Collecting text-unidecode==1.3 (from -r requirements.txt (line 63))
  Using cached text_unidecode-1.3-py2.py3-none-any.whl (78 kB)
Collecting tomli==2.0.1 (from -r requirements.txt (line 64))
  Using cached tomli-2.0.1-py3-none-any.whl (12 kB)
Collecting urllib3==1.26.15 (from -r requirements.txt (line 65))
  Using cached urllib3-1.26.15-py2.py3-none-any.whl (140 kB)
Collecting wcmatch==8.4.1 (from -r requirements.txt (line 66))
  Using cached wcmatch-8.4.1-py3-none-any.whl (39 kB)
Collecting yamllint==1.31.0 (from -r requirements.txt (line 67))
  Using cached yamllint-1.31.0-py3-none-any.whl (64 kB)
Installing collected packages: text-unidecode, resolvelib, pyhcl, boto, urllib3, tomli, subprocess-tee, six, ruamel.yaml.clib, PyYAML, python-slugify, pyrsistent, Pygments, pyflakes, pycparser, pycodestyle, pyasn1, pluggy, platformdirs, pathspec, packaging, mypy-extensions, mdurl, mccabe, MarkupSafe, jmespath, idna, filelock, docutils, colorama, click, charset-normalizer, chardet, certifi, bracex, attrs, yamllint, wcmatch, ruamel.yaml, rsa, requests, python-dateutil, markdown-it-py, jsonschema, Jinja2, flake8, click-help-colors, cffi, black, binaryornot, rich, hvac, cryptography, botocore, arrow, s3transfer, jinja2-time, enrich, ansible-core, cookiecutter, boto3, awscli, ansible-lint, ansible-compat, ansible, molecule, molecule-plugins
Successfully installed Jinja2-3.1.2 MarkupSafe-2.1.2 PyYAML-5.4.1 Pygments-2.15.1 ansible-7.5.0 ansible-compat-3.0.2 ansible-core-2.14.5 ansible-lint-6.15.0 arrow-1.2.3 attrs-23.1.0 awscli-1.27.127 binaryornot-0.4.4 black-23.3.0 boto-2.49.0 boto3-1.26.127 botocore-1.29.127 bracex-2.3.post1 certifi-2022.12.7 cffi-1.15.1 chardet-5.1.0 charset-normalizer-3.1.0 click-8.1.3 click-help-colors-0.9.1 colorama-0.4.4 cookiecutter-2.1.1 cryptography-40.0.2 docutils-0.16 enrich-1.2.7 filelock-3.12.0 flake8-6.0.0 hvac-1.1.0 idna-3.4 jinja2-time-0.2.0 jmespath-1.0.1 jsonschema-4.17.3 markdown-it-py-2.2.0 mccabe-0.7.0 mdurl-0.1.2 molecule-5.0.1 molecule-plugins-23.4.1 mypy-extensions-1.0.0 packaging-23.1 pathspec-0.11.1 platformdirs-3.5.0 pluggy-1.0.0 pyasn1-0.5.0 pycodestyle-2.10.0 pycparser-2.21 pyflakes-3.0.1 pyhcl-0.4.4 pyrsistent-0.19.3 python-dateutil-2.8.2 python-slugify-8.0.1 requests-2.30.0 resolvelib-0.8.1 rich-13.3.5 rsa-4.7.2 ruamel.yaml-0.17.22 ruamel.yaml.clib-0.2.7 s3transfer-0.6.1 six-1.16.0 subprocess-tee-0.4.1 text-unidecode-1.3 tomli-2.0.1 urllib3-1.26.15 wcmatch-8.4.1 yamllint-1.31.0

(.venv) $ python -m pip freeze
ansible==7.5.0
ansible-compat==3.0.2
ansible-core==2.14.5
ansible-lint==6.15.0
arrow==1.2.3
attrs==23.1.0
awscli==1.27.127
binaryornot==0.4.4
black==23.3.0
boto==2.49.0
boto3==1.26.127
botocore==1.29.127
bracex==2.3.post1
certifi==2022.12.7
cffi==1.15.1
chardet==5.1.0
charset-normalizer==3.1.0
click==8.1.3
click-help-colors==0.9.1
colorama==0.4.4
cookiecutter==2.1.1
cryptography==40.0.2
docutils==0.16
enrich==1.2.7
filelock==3.12.0
flake8==6.0.0
hvac==1.1.0
idna==3.4
Jinja2==3.1.2
jinja2-time==0.2.0
jmespath==1.0.1
jsonschema==4.17.3
markdown-it-py==2.2.0
MarkupSafe==2.1.2
mccabe==0.7.0
mdurl==0.1.2
molecule==5.0.1
molecule-plugins==23.4.1
mypy-extensions==1.0.0
packaging==23.1
pathspec==0.11.1
platformdirs==3.5.0
pluggy==1.0.0
pyasn1==0.5.0
pycodestyle==2.10.0
pycparser==2.21
pyflakes==3.0.1
Pygments==2.15.1
pyhcl==0.4.4
pyrsistent==0.19.3
python-dateutil==2.8.2
python-slugify==8.0.1
PyYAML==5.4.1
requests==2.30.0
resolvelib==0.8.1
rich==13.3.5
rsa==4.7.2
ruamel.yaml==0.17.22
ruamel.yaml.clib==0.2.7
s3transfer==0.6.1
six==1.16.0
subprocess-tee==0.4.1
text-unidecode==1.3
tomli==2.0.1
urllib3==1.26.15
wcmatch==8.4.1
yamllint==1.31.0

(.venv) $ env | sort
AWS_PROFILE=mycorp-didev
AWS_REGION=us-west-2
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1002/bus
EC2_REGION=us-west-2
HOME=/home/myuser
LANG=en_US.UTF-8
LC_TERMINAL=iTerm2
LC_TERMINAL_VERSION=3.4.19
LESSCLOSE=/usr/bin/lesspipe %s %s
LESSOPEN=| /usr/bin/lesspipe %s
LOGNAME=myuser
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
MOTD_SHOWN=pam
OLDPWD=/home/myuser/projects/ansible
PATH=/home/myuser/projects/ansible/ansible-role-molecule_ec2_template/.venv/bin:/home/myuser/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
PS1=(.venv) ${debian_chroot:+($debian_chroot)}\u@\h:\w\$
PWD=/home/myuser/projects/ansible/ansible-role-molecule_ec2_template
SHELL=/bin/bash
SHLVL=0
SSH_CLIENT=<IP_ADDRESS> 56119 22
SSH_CONNECTION=<IP_ADDRESS> 56119 <IP_ADDRESS> 22
SSH_TTY=/dev/pts/0
TERM=ansi
USER=myuser
_=/usr/bin/env
VAULT_ADDR=https://vault.mycorp.com:8200
VAULT_TLS_SERVER_NAME=vault.mycorp.com
VIRTUAL_ENV=/home/myuser/projects/ansible/ansible-role-molecule_ec2_template/.venv
VIRTUAL_ENV_PROMPT=(.venv)
XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop
XDG_RUNTIME_DIR=/run/user/1002
XDG_SESSION_CLASS=user
XDG_SESSION_ID=515
XDG_SESSION_TYPE=tty

(.venv) $ cat molecule/default/molecule.yml
---
dependency:
  name: galaxy
driver:
  name: ec2
platforms:
   - name: ubuntu-22.04
     image: ami-04861a2e4ef4abd6b  # Ubuntu 22.04 LTS
     instance_type: t2.micro
     vpc_subnet_id: subnet-01eb1db29e0209d48
     assign_public_ip: false
     ansible_user: ubuntu
provisioner:
  name: ansible
verifier:
  name: ansible

(.venv) $ molecule destroy
INFO     Found config file /home/myuser/projects/ansible/ansible-role-molecule_ec2_template/.config/molecule/config.yml
WARNING  The scenario config file ('/home/myuser/projects/ansible/ansible-role-molecule_ec2_template/molecule/default/molecule.yml') has been modified since the scenario was created. If recent changes are important, reset the scenario with 'molecule destroy' to clean up created items or 'molecule reset' to clear current configuration.
WARNING  Driver ec2 does not provide a schema.
INFO     default scenario test matrix: dependency, cleanup, destroy
INFO     Performing prerun with role_name_check=0...
INFO     Set ANSIBLE_LIBRARY=/home/myuser/.cache/ansible-compat/30597c/modules:/home/myuser/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
INFO     Set ANSIBLE_COLLECTIONS_PATH=/home/myuser/.cache/ansible-compat/30597c/collections:/home/myuser/.ansible/collections:/usr/share/ansible/collections
INFO     Set ANSIBLE_ROLES_PATH=/home/myuser/.cache/ansible-compat/30597c/roles:/home/myuser/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles
INFO     Using /home/myuser/.cache/ansible-compat/30597c/roles/mycorp.molecule_ec2 symlink to current repository in order to enable Ansible to find the role using its expected full name.
INFO     Running default > dependency
WARNING  Skipping, missing the requirements file.
WARNING  Skipping, missing the requirements file.
INFO     Running default > cleanup
WARNING  Skipping, cleanup playbook not configured.
INFO     Running default > destroy

PLAY [Destroy] *****************************************************************

TASK [Validate platform configurations] ****************************************
[WARNING]: Unable to find '/home/myuser/.cache/molecule/ansible-role-
molecule_ec2_template/default/run-config.yml' in expected paths (use -vvvvv to
see paths)
ok: [localhost] => (item=ubuntu-22.04)

TASK [Look up subnets to determine VPCs (if needed)] ***************************
[WARNING]: Unable to find '/home/myuser/.cache/molecule/ansible-role-
molecule_ec2_template/default/run-config.yml' in expected paths (use -vvvvv to
see paths)
[DEPRECATION WARNING]: Support for the 'EC2_REGION', 'EC2_ACCESS_KEY',
'EC2_SECRET_KEY', 'EC2_SECURITY_TOKEN', 'EC2_URL', and 'S3_URL' environment
variables has been deprecated.  These variables are currently used for all AWS
services which can cause confusion.  We recomend using the relevant module
parameters or alternatively the 'AWS_REGION', 'AWS_ACCESS_KEY_ID',
'AWS_SECRET_ACCESS_KEY', 'AWS_SESSION_TOKEN', and 'AWS_URL' environment
variables can be used instead. This feature will be removed from amazon.aws in
a release after 2024-12-01. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
ok: [localhost] => (item=ubuntu-22.04)

TASK [Validate discovered information] *****************************************
[WARNING]: Unable to find '/home/myuser/.cache/molecule/ansible-role-
molecule_ec2_template/default/run-config.yml' in expected paths (use -vvvvv to
see paths)
ok: [localhost] => (item=ubuntu-22.04)

TASK [Destroy ephemeral EC2 instances] *****************************************
[WARNING]: Unable to find '/home/myuser/.cache/molecule/ansible-role-
molecule_ec2_template/default/run-config.yml' in expected paths (use -vvvvv to
see paths)
[WARNING]: Unable to find '/home/myuser/.cache/molecule/ansible-role-
molecule_ec2_template/default/instance_config.yml' in expected paths (use
-vvvvv to see paths)
changed: [localhost] => (item=ubuntu-22.04)

TASK [Wait for instance destruction to complete] *******************************
[WARNING]: Unable to find '/home/myuser/.cache/molecule/ansible-role-
molecule_ec2_template/default/run-config.yml' in expected paths (use -vvvvv to
see paths)
failed: [localhost] (item=ubuntu-22.04) => {"ansible_index_var": "index", "ansible_job_id": "j368239605520.381935", "ansible_loop_var": "item", "attempts": 2, "changed": false, "cmd": "/home/myuser/.ansible/tmp/ansible-tmp-1683388151.8528783-381915-266859886423936/AnsiballZ_ec2_instance.py", "data": "", "finished": 1, "index": 0, "item": {"ansible_job_id": "j368239605520.381935", "ansible_loop_var": "item", "changed": true, "failed": 0, "finished": 0, "item": {"ansible_user": "ubuntu", "assign_public_ip": false, "aws_profile": "mycorp-didev", "image": "ami-04861a2e4ef4abd6b", "instance_type": "t2.micro", "key_inject_method": "cloud-init", "key_name": "molecule-cvgsj", "name": "ubuntu-22.04", "region": "us-west-2", "security_group_name": "molecule-ipbvs", "security_groups": [], "vpc_id": "", "vpc_subnet_id": "subnet-01eb1db29e0209d48"}, "results_file": "/home/myuser/.ansible_async/j368239605520.381935", "started": 1}, "msg": "Traceback (most recent call last):\n  File \"/tmp/ansible_ansible.legacy.async_wrapper_payload_c4bwbmz4/ansible_ansible.legacy.async_wrapper_payload.zip/ansible/modules/async_wrapper.py\", line 180, in _run_module\n  File \"/tmp/ansible_ansible.legacy.async_wrapper_payload_c4bwbmz4/ansible_ansible.legacy.async_wrapper_payload.zip/ansible/modules/async_wrapper.py\", line 98, in _filter_non_json_lines\nValueError: No start of json char found\n", "results_file": "/home/myuser/.ansible_async/j368239605520.381935", "started": 1, "stderr": "Traceback (most recent call last):\n  File \"/home/myuser/.ansible/tmp/ansible-tmp-1683388151.8528783-381915-266859886423936/AnsiballZ_ec2_instance.py\", line 107, in <module>\n    _ansiballz_main()\n  File \"/home/myuser/.ansible/tmp/ansible-tmp-1683388151.8528783-381915-266859886423936/AnsiballZ_ec2_instance.py\", line 99, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/home/myuser/.ansible/tmp/ansible-tmp-1683388151.8528783-381915-266859886423936/AnsiballZ_ec2_instance.py\", line 47, in invoke_module\n    runpy.run_module(mod_name='ansible_collections.amazon.aws.plugins.modules.ec2_instance', init_globals=dict(_module_fqn='ansible_collections.amazon.aws.plugins.modules.ec2_instance', _modlib_path=modlib_path),\n  File \"/usr/lib/python3.10/runpy.py\", line 224, in run_module\n    return _run_module_code(code, init_globals, run_name, mod_spec)\n  File \"/usr/lib/python3.10/runpy.py\", line 96, in _run_module_code\n    _run_code(code, mod_globals, init_globals,\n  File \"/usr/lib/python3.10/runpy.py\", line 86, in _run_code\n    exec(code, run_globals)\n  File \"/tmp/ansible_ec2_instance_payload_ga1x__vo/ansible_ec2_instance_payload.zip/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py\", line 2167, in <module>\n  File \"/tmp/ansible_ec2_instance_payload_ga1x__vo/ansible_ec2_instance_payload.zip/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py\", line 2141, in main\n  File \"/tmp/ansible_ec2_instance_payload_ga1x__vo/ansible_ec2_instance_payload.zip/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py\", line 2018, in build_filters\n  File \"/tmp/ansible_ec2_instance_payload_ga1x__vo/ansible_ec2_instance_payload.zip/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py\", line 1566, in get_default_subnet\nTypeError: 'NoneType' object is not subscriptable\n", "stderr_lines": ["Traceback (most recent call last):", "  File \"/home/myuser/.ansible/tmp/ansible-tmp-1683388151.8528783-381915-266859886423936/AnsiballZ_ec2_instance.py\", line 107, in <module>", "    _ansiballz_main()", "  File \"/home/myuser/.ansible/tmp/ansible-tmp-1683388151.8528783-381915-266859886423936/AnsiballZ_ec2_instance.py\", line 99, in _ansiballz_main", "    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)", "  File \"/home/myuser/.ansible/tmp/ansible-tmp-1683388151.8528783-381915-266859886423936/AnsiballZ_ec2_instance.py\", line 47, in invoke_module", "    runpy.run_module(mod_name='ansible_collections.amazon.aws.plugins.modules.ec2_instance', init_globals=dict(_module_fqn='ansible_collections.amazon.aws.plugins.modules.ec2_instance', _modlib_path=modlib_path),", "  File \"/usr/lib/python3.10/runpy.py\", line 224, in run_module", "    return _run_module_code(code, init_globals, run_name, mod_spec)", "  File \"/usr/lib/python3.10/runpy.py\", line 96, in _run_module_code", "    _run_code(code, mod_globals, init_globals,", "  File \"/usr/lib/python3.10/runpy.py\", line 86, in _run_code", "    exec(code, run_globals)", "  File \"/tmp/ansible_ec2_instance_payload_ga1x__vo/ansible_ec2_instance_payload.zip/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py\", line 2167, in <module>", "  File \"/tmp/ansible_ec2_instance_payload_ga1x__vo/ansible_ec2_instance_payload.zip/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py\", line 2141, in main", "  File \"/tmp/ansible_ec2_instance_payload_ga1x__vo/ansible_ec2_instance_payload.zip/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py\", line 2018, in build_filters", "  File \"/tmp/ansible_ec2_instance_payload_ga1x__vo/ansible_ec2_instance_payload.zip/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py\", line 1566, in get_default_subnet", "TypeError: 'NoneType' object is not subscriptable"], "stdout": "", "stdout_lines": []}
FAILED - RETRYING: [localhost]: Wait for instance destruction to complete (300 retries left).

PLAY RECAP *********************************************************************
localhost                  : ok=4    changed=1    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

WARNING  Retrying execution failure 2 of: ansible-playbook --inventory /home/myuser/.cache/molecule/ansible-role-molecule_ec2_template/default/inventory --skip-tags molecule-notest,notest /home/myuser/projects/ansible/ansible-role-molecule_ec2_template/molecule/default/destroy.yml
CRITICAL Ansible return code was 2, command was: ['ansible-playbook', '--inventory', '/home/myuser/.cache/molecule/ansible-role-molecule_ec2_template/default/inventory', '--skip-tags', 'molecule-notest,notest', '/home/myuser/projects/ansible/ansible-role-molecule_ec2_template/molecule/default/destroy.yml']

(.venv) $ molecule create
INFO     Found config file /home/myuser/projects/ansible/ansible-role-molecule_ec2_template/.config/molecule/config.yml
WARNING  The scenario config file ('/home/myuser/projects/ansible/ansible-role-molecule_ec2_template/molecule/default/molecule.yml') has been modified since the scenario was created. If recent changes are important, reset the scenario with 'molecule destroy' to clean up created items or 'molecule reset' to clear current configuration.
WARNING  Driver ec2 does not provide a schema.
INFO     default scenario test matrix: dependency, create, prepare
INFO     Performing prerun with role_name_check=0...
INFO     Set ANSIBLE_LIBRARY=/home/myuser/.cache/ansible-compat/30597c/modules:/home/myuser/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
INFO     Set ANSIBLE_COLLECTIONS_PATH=/home/myuser/.cache/ansible-compat/30597c/collections:/home/myuser/.ansible/collections:/usr/share/ansible/collections
INFO     Set ANSIBLE_ROLES_PATH=/home/myuser/.cache/ansible-compat/30597c/roles:/home/myuser/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles
INFO     Using /home/myuser/.cache/ansible-compat/30597c/roles/mycorp.molecule_ec2 symlink to current repository in order to enable Ansible to find the role using its expected full name.
INFO     Running default > dependency
WARNING  Skipping, missing the requirements file.
WARNING  Skipping, missing the requirements file.
INFO     Running default > create

PLAY [Create] ******************************************************************

TASK [Validate platform configurations] ****************************************
[WARNING]: Unable to find '/home/myuser/.cache/molecule/ansible-role-
molecule_ec2_template/default/run-config.yml' in expected paths (use -vvvvv to
see paths)
ok: [localhost] => (item=ubuntu-22.04)

TASK [Write run config to file] ************************************************
[WARNING]: Unable to find '/home/myuser/.cache/molecule/ansible-role-
molecule_ec2_template/default/run-config.yml' in expected paths (use -vvvvv to
see paths)
changed: [localhost]

TASK [Generate local key pairs] ************************************************
changed: [localhost] => (item=ubuntu-22.04)

TASK [Look up EC2 AMI(s) by owner and name (if image not set)] *****************
skipping: [localhost] => (item=ubuntu-22.04)
skipping: [localhost]

TASK [Look up subnets to determine VPCs (if needed)] ***************************
[DEPRECATION WARNING]: Support for the 'EC2_REGION', 'EC2_ACCESS_KEY',
'EC2_SECRET_KEY', 'EC2_SECURITY_TOKEN', 'EC2_URL', and 'S3_URL' environment
variables has been deprecated.  These variables are currently used for all AWS
services which can cause confusion.  We recomend using the relevant module
parameters or alternatively the 'AWS_REGION', 'AWS_ACCESS_KEY_ID',
'AWS_SECRET_ACCESS_KEY', 'AWS_SESSION_TOKEN', and 'AWS_URL' environment
variables can be used instead. This feature will be removed from amazon.aws in
a release after 2024-12-01. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
ok: [localhost] => (item=ubuntu-22.04)

TASK [Validate discovered information] *****************************************
ok: [localhost] => (item=ubuntu-22.04)

TASK [Create ephemeral EC2 keys (if needed)] ***********************************
skipping: [localhost] => (item=ubuntu-22.04)
skipping: [localhost]

TASK [Create ephemeral security groups (if needed)] ****************************
changed: [localhost] => (item=ubuntu-22.04)

TASK [Create ephemeral EC2 instance(s)] ****************************************
changed: [localhost] => (item=ubuntu-22.04)

TASK [Wait for instance creation to complete] **********************************
FAILED - RETRYING: [localhost]: Wait for instance creation to complete (300 retries left).
FAILED - RETRYING: [localhost]: Wait for instance creation to complete (299 retries left).
FAILED - RETRYING: [localhost]: Wait for instance creation to complete (298 retries left).
FAILED - RETRYING: [localhost]: Wait for instance creation to complete (297 retries left).
FAILED - RETRYING: [localhost]: Wait for instance creation to complete (296 retries left).
FAILED - RETRYING: [localhost]: Wait for instance creation to complete (295 retries left).
FAILED - RETRYING: [localhost]: Wait for instance creation to complete (294 retries left).
changed: [localhost] => (item=ubuntu-22.04)

TASK [Collect instance configs] ************************************************
ok: [localhost] => (item=ubuntu-22.04)

TASK [Write Molecule instance configs] *****************************************
changed: [localhost]

TASK [Start SSH pollers] *******************************************************
changed: [localhost] => (item=ubuntu-22.04)

TASK [Wait for SSH] ************************************************************
[WARNING]: The 'finished' test expects an async task, but a non-async task was
tested
ok: [localhost] => (item=ubuntu-22.04)

TASK [Wait for boot process to finish] *****************************************
Pausing for 120 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
ok: [localhost]

PLAY RECAP *********************************************************************
localhost                  : ok=13   changed=7    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0

INFO     Running default > prepare

PLAY [Prepare] *****************************************************************

TASK [Make sure python3 is installed] ******************************************
ok: [ubuntu-22.04]

PLAY RECAP *********************************************************************
ubuntu-22.04               : ok=1    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

(.venv) $ molecule destroy
INFO     Found config file /home/myuser/projects/ansible/ansible-role-molecule_ec2_template/.config/molecule/config.yml
WARNING  The scenario config file ('/home/myuser/projects/ansible/ansible-role-molecule_ec2_template/molecule/default/molecule.yml') has been modified since the scenario was created. If recent changes are important, reset the scenario with 'molecule destroy' to clean up created items or 'molecule reset' to clear current configuration.
WARNING  Driver ec2 does not provide a schema.
INFO     default scenario test matrix: dependency, cleanup, destroy
INFO     Performing prerun with role_name_check=0...
INFO     Set ANSIBLE_LIBRARY=/home/myuser/.cache/ansible-compat/30597c/modules:/home/myuser/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
INFO     Set ANSIBLE_COLLECTIONS_PATH=/home/myuser/.cache/ansible-compat/30597c/collections:/home/myuser/.ansible/collections:/usr/share/ansible/collections
INFO     Set ANSIBLE_ROLES_PATH=/home/myuser/.cache/ansible-compat/30597c/roles:/home/myuser/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles
INFO     Using /home/myuser/.cache/ansible-compat/30597c/roles/mycorp.molecule_ec2 symlink to current repository in order to enable Ansible to find the role using its expected full name.
INFO     Running default > dependency
WARNING  Skipping, missing the requirements file.
WARNING  Skipping, missing the requirements file.
INFO     Running default > cleanup
WARNING  Skipping, cleanup playbook not configured.
INFO     Running default > destroy

PLAY [Destroy] *****************************************************************

TASK [Validate platform configurations] ****************************************
ok: [localhost] => (item=ubuntu-22.04)

TASK [Look up subnets to determine VPCs (if needed)] ***************************
[DEPRECATION WARNING]: Support for the 'EC2_REGION', 'EC2_ACCESS_KEY',
'EC2_SECRET_KEY', 'EC2_SECURITY_TOKEN', 'EC2_URL', and 'S3_URL' environment
variables has been deprecated.  These variables are currently used for all AWS
services which can cause confusion.  We recomend using the relevant module
parameters or alternatively the 'AWS_REGION', 'AWS_ACCESS_KEY_ID',
'AWS_SECRET_ACCESS_KEY', 'AWS_SESSION_TOKEN', and 'AWS_URL' environment
variables can be used instead. This feature will be removed from amazon.aws in
a release after 2024-12-01. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
ok: [localhost] => (item=ubuntu-22.04)

TASK [Validate discovered information] *****************************************
ok: [localhost] => (item=ubuntu-22.04)

TASK [Destroy ephemeral EC2 instances] *****************************************
changed: [localhost] => (item=ubuntu-22.04)

TASK [Wait for instance destruction to complete] *******************************
FAILED - RETRYING: [localhost]: Wait for instance destruction to complete (300 retries left).
FAILED - RETRYING: [localhost]: Wait for instance destruction to complete (299 retries left).
FAILED - RETRYING: [localhost]: Wait for instance destruction to complete (298 retries left).
FAILED - RETRYING: [localhost]: Wait for instance destruction to complete (297 retries left).
FAILED - RETRYING: [localhost]: Wait for instance destruction to complete (296 retries left).
FAILED - RETRYING: [localhost]: Wait for instance destruction to complete (295 retries left).
FAILED - RETRYING: [localhost]: Wait for instance destruction to complete (294 retries left).
changed: [localhost] => (item=ubuntu-22.04)

TASK [Write Molecule instance configs] *****************************************
changed: [localhost]

TASK [Destroy ephemeral security groups (if needed)] ***************************
changed: [localhost] => (item=ubuntu-22.04)

TASK [Destroy ephemeral keys (if needed)] **************************************
skipping: [localhost] => (item=ubuntu-22.04)
skipping: [localhost]

PLAY RECAP *********************************************************************
localhost                  : ok=7    changed=4    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0

INFO     Pruning extra files from scenario ephemeral directory

Seems to duplicate https://github.com/ansible-community/molecule-plugins/issues/46


[Question] About the last several questions of FAQ section

Hi there,
I am translating the pact documents to Chinese version with @wldandan. But in the FAQ section, about the last several questions from here, I can not find the source text either in gitbook branch or master branch of this repo. The repo only contains those questions before this question I mentioned. Could you help find out where are the sources of the docs.pact.io site ? Thanks.

Is the latest content of https://docs.pact.io/ synced using the test branch?

@mefellows you're across the gitbook stuff aren't you?

@tongzh yes, I believe it does use the test branch.

Yep, it sure is. we're probably about due to change that, we'll let you know if we do though :)

Thanks @mefellows , to keep the consistency with docs.pact.io, we're using the test branch for translating.


Image rendering on smaller viewports causes overflow issues.

Rendering messages with

Attachment images
Emotes
A name with a Bot/Server badge

all cause overflow issues on mobile devices when rendering with lists such as React Virtuoso, which causes blank spaces and jumping.
I'm sure its the images causing this, because when tested with channels that only have text content and no image attachments, it renders fine on mobile.
Video of issue:
https://github.com/widgetbot-io/message-renderer/assets/94828874/a6bffae4-96fb-45aa-836f-20f5a0e25147

Hello, I'm author of https://github.com/inokawa/virtua .
It has better jump suppression logic than react-virtuoso for iOS browsers and for resizes outside of viewport.
Check it out if you interested in it.


Remove FileManager

I've much improved the handling of Blob data: it's now possible to pass an arbitrary number of Blobs embedded in your output schema, and these will be converted to JSON data with href and media_type with the actual data retrieved from a URL under /blob/. I've never used FileManager in anger, and it requires a bunch of slightly unsatisfying special-case code. I propose to remove FileManager and replace it with the Blob API.
Similarly, Blob replaces BlobOutput and I propose to make this change. I think we are still early enough in development that it's better to just make a breaking change than to keep old code and phase it out gradually.

The change to Blob is in #83.


Problem - download images from docker.bintray.io

Hi i have problem to download images.
Yesterday (13.06.2017) it works. I am trying to use https://github.com/JFrogDev/artifactory-docker-examples/blob/master/docker-compose/artifactory-pro.yml
docker.bintray.io/postgres:9.5.2
docker.bintray.io/jfrog/artifactory-pro:5.3.2
docker.bintray.io/jfrog/nginx-artifactory-pro:5.3.2

Hi @JarRoDk ,
I just checked a pull on a public network and it works
16:25 $ docker pull docker.bintray.io/jfrog/artifactory-pro:5.3.2
5.3.2: Pulling from jfrog/artifactory-pro
43c265008fae: Already exists
af36d2c7a148: Already exists
143e9d501644: Already exists
bfc4cdbc8d81: Already exists
38c6fc3e9968: Already exists
0bfa8d5153bb: Already exists
05bc8d0fffca: Already exists
f1266a2a7ecb: Already exists
55154431b279: Downloading [====================================>              ] 64.21 MB/87.41 MB
7e68651520ff: Download complete
37ce5c92c25a: Download complete
3a8dcf30dc42: Downloading [============================================>      ] 74.71 MB/83.14 MB
1ee56eb783e6: Downloading [==========================>                        ] 46.68 MB/87.37 MB
ae9d0331e30f: Waiting

I assume something changed in your network settings.
Eldad

Ok, thx to confirm.

Hello,
I have the same problem actually with the OSS version :
https://github.com/JFrogDev/artifactory-docker-examples/blob/master/docker-compose/artifactory-oss-postgresql.yml
artifactory git:(master) ✗ docker-compose up
Pulling artifactory (docker.bintray.io/jfrog/artifactory-oss:5.4.2)...
5.4.2: Pulling from jfrog/artifactory-oss
43c265008fae: Already exists
af36d2c7a148: Already exists
143e9d501644: Already exists
c933b00c3409: Already exists
b2df646b60f9: Already exists
ceeb7ccd5b89: Already exists
05bc8d0fffca: Waiting

I copy the content of the artifactory-oss-postgresql.yml to a docker-compose.yml file (this is why I can use docker-compose up without -f option)
any Idea ?

@paulcayon - I tested it now, and the pull is ok now. You might have experienced temporary network hangs.
Can you test again and confirm it's working?


Search results for LORA not working right.

I'm trying to find specific LORA from civitai but i can't find it no matter what term i search, "kula" just gives me whatever results i had searched before, seems like searching specific words or phrases are just broken in general since i tried searching some other characters and it didn't work, the lora in question https://civitai.com/models/465144?modelVersionId=517620
i was able to find it by typing "kul" but still this is an issue so i am bringing it to your attention regardless since it's happening with lot of search terms that should work, If there was some way to search via model Hash this wouldn't be an issue even with this bug.

same

try beta site for the V2 version artbot.site/


Fix Dark Color Scheme

Type of Change

[x] UI/UX improvement

Description

Most likely some of the Changes to the Theme were broken during some of the last commits, so here's my two cents on how to fix it (without actually taking the time and checking what settings were used before)

Before
After

I feel like tha background could be a bit darker than this.

I feel like tha background could be a bit darker than this.

It's actually the same as it is in the current stable release

Yeah ik I meant that, maybe not as dark as current main branch but a bit darker

Let's leave the final design to our best maintainer :D

Oh this broke again.

@Marterich for color reference you can look youtube dark mode.

DNS Button color also broke

It is the "Comboboxforegroundcolor" is used in many places, which is ducked up

It is the "Comboboxforegroundcolor" is used in many places, which is ducked up

Rly? Haven't seen it anywhere else while taking a quick peek

i think we need to document what goes where for future ease.


Handling scale incorrectly

When the object is scaled with [x, y, z], we don't have a good way to propagate the scale to children links if they are not perfectly aligned (or at least orthogonally aligned) with the base link.

fixed by #166


Crash Report

Mod Version:
DynamicSurroundings-1.12.2-<IP_ADDRESS>BETA.jar
Forge Version:
1.12.2 - <IP_ADDRESS>68
Link to crash log (if applicable):
crash-2018-12-01_12.10.31-client.txt
Description:
World loads up fine but when i started to move and open up new chunks game crashed to desktop

@PG85 When does the biome information get loaded on the client?  With v3.5 I have a world load event handler at the lowest priority that will initialize my biome registry.  My goal is to avoid lag doing this reset during world load rather than when the player is wandering around.

Pushed v<IP_ADDRESS> to CurseForge with a fix.


Clarification on Deliver lane- Pricing and availability updates - App store connect

Hi Team,
While going through documents we understand that the metadata for availability section of IOS can be provided with the country code.
However wanted to know if there is any way or parameter which we can use to update the availability/visiblity to be only within the business organization or school and not public ?

Facing same issue here. Help is appreciated.

I have the exact same problem. Have tried a variety of things. Me too facing the similar issues.

Hi Team,
Apologies,This is not an issue.
We would need clarity on the possibility of making changes to the
availablity flag.
Thanks
Kamal
On Wed, 15 Jun, 2022, 3:33 pm fastlane bot, @.***>
wrote:

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the
issue to include the output of fastlane env 👍
—
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/issues/20382#issuecomment-1156266594,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APNVKEY4ZKKHU7QRHREOX23VPGS6VANCNFSM5Y2WJZOA
.
You are receiving this because you authored the thread.Message ID:
@.***>


plugin in preview mode

Hello,
I have an issue with the plugin in preview mode (in reading/editing it's ok).
For my supercharged links I have in preview mode the content after link but not the links style.
In the settings, the four options are ok.
Someone has an idea for the root cause?
thanks
preview;

source  mode:

test with different theme same result, test without plugin (only style setting and supercharged) same result

all links are corrupted...it's not dur to the plugin sorry


Allow lib user to construct they own java client

Upstream PR: https://github.com/zio/zio-kafka/pull/410/files


fixing peacekraber in sp ( again )

the previous pr ( #382 ) didn't work for everyone. this time it should.
https://canary.discord.com/channels/920776187884732556/987319483846778890/987459128878313513

yeah because you need to precache it.

Anything blocking this from being merged?

@catornot update your branch

oh no I merged co-op

huh should have fixed idk

you need to merge main into sp-fix2

😅

damn this is a lot of commit history for a single line change

And I cannot even test it atm cause I cannot launch SP without Invalid Name error xD

damn this is a lot of commit history for a single line change

And I cannot even test it atm cause I cannot launch SP without Invalid Name error xD

allow insecure auth in customservers autoexec.cfg

@GeckoEidechse did you manage to test yet?

It's supposed to be precached in co-op
sh_coop_custom_precache.gnut

sure, but that's not fixing the peacekraber in SP, that's fixing it in coop. The peacekraber remains in a broken state in normal SP

Btw from my own testing just now, just running sh_northstar_custom_precache on CLIENT || SERVER works just fine with no noticeable side effects in normal SP (triple threat works, as does the peacekraber)
If there are errors from running it with coop, then maybe remove the precaching on coop?

making sh_northstar_custom_precache  CLIENT || SERVER wasn't working for some people, weird stuff ¯\_(ツ)_/¯


Improve error messaging for "bolt script run" on Powershell

Describe the Bug
When the PowerShell ExecutionPolicy is set to Restricted or AllSigned, Bolt won’t be able to execute an unsigned powershell script via bolt script run.
Expected Behavior
A clear generic error returned to the user or an error that explains the restricted execution policy that is preventing Bolt from running.
Steps to Reproduce
Steps to reproduce the behavior:

Create a Windows target with the PowerShell Execution Policy set to Restricted or AllSigned
Execute a powershell script on target

Environment

Version 3.0.0
Platform Windows

Additional Context
Example output:
Started on winrm://wsus.dreamworx.nl...
--
Failed on winrm://wsus.dreamworx.nl:
The command failed with exit code 1
STDERR:
$invokeArgs = @{
: System.Management.Automation.ParameterBindingValidationException: Cannot validate argument on parameter 'ScriptBlock'. The argument is null. Provide a valid value for the argument, and then try running the command again. ---> System.Management.Automation.ValidationMetadataException: The argument is null. Provide a valid value for the argument, and then try running the command again.
at System.Management.Automation.ValidateNotNullAttribute.Validate(Object arguments, EngineIntrinsics engineIntrinsics)
at System.Management.Automation.ParameterBinderBase.BindParameter(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, ParameterBindingFlags flags)
--- End of inner exception stack trace ---
at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
+ CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException
Failed on 1 target: winrm://wsus.dreamworx.nl
Ran on 1 target in 2.09 sec

Reported by : @kreeuwijk

Note that Bolt ships it's PowerShell module signed, so this problem occurs on the target not the host running Bolt.
We can improve the error message by either checking for execution policy first before executing the script and returning a custom message, or by executing the script in a try/catch block and relying on the error message to be coherent.


Alot of cities cannot be found via setup search

Thus leaving you with a blank weather forecast. This include capitals like Copenhagen, Berlin etc.
I have been scouring the code for the url insertion to use hardcoded forecast.io/darksky url/coordinates, but I am strugling to find where you do this.

Hi, had this problem myself a couple of days ago. It's due to the fact that cities outside of the US (afaik) don't feature the visibility attribute. So when it gets the forecast for a city outside of the US, there's no visiblity attribute in the JSON response and the visibility attribute becomes "null". This causes the request to fail and keeps the app from showing the weather data.
I made a quick fix by adding a line that checks if it's "null" and than replaces it with an "unknown" String.
String visibilityInfo = response.getCurrently().getVisibility() != null response.getCurrently().getVisibility().intValue() + distanceUnit: "unknown";
Add this to the getCurrentWeather method in the ForecastIOService class and change:
 .visibilityInfo(response.getCurrently().getVisibility().intValue() + distanceUnit)
to:
.visibilityInfo(visibilityInfo)
in the WeatherBuilder in the return statement of that method.
Ideally all attributes should be checked for "null".
Hope this fixes your problem.

Fixed it indeed! Thanks!
I have hidden those weather UI elements on my build (small tablet) so didnt even think to check the JSON response if those attributes were the incorrect ones..

Sorry, I may be a noob on this - but where should I make this change?
As OP writes, I am trying to choose Copenhagen, but with no luck.


Loss of control over AI driver if another player gets into the commander seat

Enable AI driver while in the gunner seat of a vehicle.
If a player gets in to the commander seat, the existing AI driver created by the gunner stops functioning.
The other issue is that players are able to get into the driver seat even if there is an AI driver already occupying it.

I believe this has always been the case, has it not?

Yes. It has been a bane of missions where AI driver is enabled.

I believe the commander switch may be possible, not sure about blocking the seat

recent changes in this command may yield some success: https://community.bistudio.com/wiki/turretOwner


feat(echo): metrics

Details

EchoDataMonitor class integration with LevelDBStorageAdapter and EchoNetworkAdapter for storage and replication metrics capture.
EchoDataMonitor manages a set of remote and local metrics.
EchoDataMonitor exports stats through EchoHost.echo-stats diagnostics channel.
New stats are displayed in StatsPanel.
SlidingWindowSummary util class for computing sliding window statistics.
If @trace.resource() annotated object implements TimeAware interface its tick method is going to be invoked by trace processor every 1s.
CircularBuffer returns evicted element on push.

Indexing should be covered in a separate PR.
Sentry metrics.

Network metrics are sometimes split into replication and collection-sync because collection-sync payloads grow with the number of spaces while replication messages should stay the same.
-rate should be interpreted as "when there was activity in the app here's how many operations were performed". Related counters help us understand how often the app is not doing this type of operation, eg.:

dxos.echo.storage.load{status=busy} / dxos.echo.storage.load is equal to 0.05. Out of all recorded app running time 5% of seconds had some storage reads.
p90(dxos.echo.storage.load-rate) is equal to 1000. During these seconds in 90% of cases load rate has not exceeded 1000 operations per second.

Distributions:

dxos.echo.storage.(load|store)-rate
dxos.echo.network.(receive|send)-rate
dxos.echo.storage.bytes-(loaded|stored)
dxos.echo.(replication|collection-sync).bytes-(sent|received) split by message type.
dxos.echo.(replication|collection-sync).send-duration split by message type.

Counters:

dxos.echo.storage.(load|store) split by status: 'busy' | 'idle'.
dxos.echo.network.(send|receive) split by status: 'busy' | 'idle'.
dxos.echo.(replication|collection-sync).send-status split by success: boolean.

Local metrics.

Extended information can be retrieved from EchoDataMonitor using dxos.tracing, for example time series or split of last sent messages by peer id.
const monitor = dxos.tracing.findResourcesByClassName('EchoDataMonitor')[0].instance.deref()

For comparison indexed-db supports around 3000 reads per second according to some benchmarks


Add docs powered by gatsby

Adapted from Gatsby's own docs. I hope they won't mind :-" I tried making it look different enough. But kept the typography so still looks quite similar.

Live here: https://qubitproducts.github.io/tiny-atom/.
Just need to work on the content now.


Form Components

I hope you don't mind me using your issue list as a placeholder for the things I'd like to see! Regarding forms there needs to be:

Textfield
Textarea
Checkbox/toggle
Select & multiselect
Date and Time
Disabled/readonly states

Is this on your hitlist? Would be good to see a roadmap on the wiki too. I'll be free in the new year to spend some time on this I think and having a list of priorities might be handy.

Hey @JedWatson, first off, this framework is looking awesome! Really looking forward to watching it continue to develop.
I was playing around with the demo on my phone, and noticed on the form page when tabbing or tapping between inputs there's a pretty gnarly jump where the cursor as well as the view is out of sync with the element you're trying to type in. Have you noticed that/do you any idea why that is happening?

@zkilgore Thanks!
Re: the keyboard jankiness, we've been working on that one.
It's related to the default "scroll on focus" and "keyboard shrinks view" behaviour(s) in iOS. Cordova has a patchy history with this (used to be a core feature, then a plugin which was abandoned, now there are two popular plugins that do slightly different things)
Will update as soon as we've got it solved. Also planning to put together a knowledgeable of how to set up your cordova project (e.g. recommended plugins and settings, etc.)

@JedWatson That's what I was thinking it was. Well, something like that at least!
I am currently writing a form heavy piece of an app now, so if you guys have any specific leads that you just don't have the bandwidth to work on, I'd be more than happy to help out and help squash this.

These components/issues have been added/resolved either in Touchstone itself or by other React components


WIP : Module local lcos

Add local_lcos module, and move some dependencies to make it independent:

move static_reinit, reinitializable and first_argument into the functional module
remove some unused headers
deprecate receive buffer

What's the rationale of deprecating receive_buffer?

What's the rationale of deprecating receive_buffer?

That's on me. It's used in exactly one example, and nowhere in the main codebase. Is it useful to keep around? I'm easy to convince to keep it; I just don't want to keep it around for the sake of keeping it around.

What's the rationale of deprecating receive_buffer?

That's on me. It's used in exactly one example, and nowhere in the main codebase. Is it useful to keep around? I'm easy to convince to keep it; I just don't want to keep it around for the sake of keeping it around.

We could make it part of the example. That would keep it around, but remove the need for us to document or maintain it...

What's the rationale of deprecating receive_buffer?

That's on me. It's used in exactly one example, and nowhere in the main codebase. Is it useful to keep around? I'm easy to convince to keep it; I just don't want to keep it around for the sake of keeping it around.

We could make it part of the example. That would keep it around, but remove the need for us to document or maintain it...

Fair enough! That sounds like a good compromise.

What's the rationale of deprecating receive_buffer?

That's on me. It's used in exactly one example, and nowhere in the main codebase. Is it useful to keep around? I'm easy to convince to keep it; I just don't want to keep it around for the sake of keeping it around.

We could make it part of the example. That would keep it around, but remove the need for us to document or maintain it...

Fair enough! That sounds like a good compromise.

It's actually used in channel.hpp so we'll keep it around sorry ^^

To remove the circular dependency between the local_lcos and the execution module, we need to split local_lcos into "synchronization lcos" the others (the ones which returns futures).
@hkaiser would you have a good name for those ?

would you have a good name for those ?

@aurianer how about sync or synchronization for the low-lever stuff and local_lcos for the ones that depend on hpx::future

There is still some dependencies to some main headers but they will move in the execution module or in the threading module :)

Just a couple of things from me as well, but looks good otherwise!

Ok all should be fine now :)

I've just pushed a commit to turn on compatibility headers in the local_lcos module that was causing the APEX build to fail. Merging now.

@aurianer, @msimberg Thanks everybody for this! Very nice!


Dragen somatic with germline pipeline v4.0.3

Description
Dragen somatic with germline pipeline v4.0.3
Dragen team have no plan to add germline vcf to list of somatic outputs, so we run both tools in parallel instead.
This means future umccrise workflows will only need to run umccrise, not the germline pipeline as well. This should hopefully also speed up analysis by a few hours.
Upstream PRs

[x] https://github.com/umccr/cwl-ica/pull/138
[x] https://github.com/umccr/cwl-ica/pull/139
[x] https://github.com/umccr/cwl-ica/pull/141

Resolved

[x] Sporadic task failures on ICAv1 for dragen v4 containers

https://github.com/umccr-illumina/stratus/issues/183

[x] Job failing to collect tool outputs

https://github.com/umccr-illumina/cwl-iap/issues/214

Completed runs

wfr.2ab19906840343c2b5cd281b6edd08ef

This one is also good to go now


flutter update-packages stuck

$ flutter update-packages
Running "flutter pub get" in automated_tests...                     4.7s
Running "flutter pub get" in complex_layout...                      6.5s
Running "flutter pub get" in macrobenchmarks...
Git error. Command: `git clone --mirror https://github.com/flutter/gallery.git C:\src\flutter\.pub-cache\git\cache\gallery-e81411447eb674bf0aa7b6d3b66e18a667cfbf46`
stdout:
stderr: Cloning into bare repository 'C:\src\flutter\.pub-cache\git\cache\gallery-e81411447eb674bf0aa7b6d3b66e18a667cfbf46'...
fatal: early EOF
fatal: the remote end hung up unexpectedly
fatal: index-pack failed
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
exit code: 128
pub get failed (server unavailable) -- attempting retry 1 in 1 second...
Running "flutter pub get" in macrobenchmarks...                 (This is taking an unexpectedly long time.)       \

C:\Users\liwei>flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, 1.22.0-12.2.pre, on Microsoft Windows [Version 10.0.19041.508], locale zh-CN)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Chrome - develop for the web
[√] Android Studio (version 3.5)
[√] VS Code (version 1.49.2)
[√] Connected device (3 available)

• No issues found!

used Flutter社区主镜像
export PUB_HOSTED_URL=https://pub.flutter-io.cn
export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn

@liwei511
Looking at the error log you sent:
fatal: early EOF
fatal: the remote end hung up unexpectedly
fatal: index-pack failed
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
exit code: 128
pub get failed (server unavailable) -- attempting retry 1 in 1 second...

This looks more like a network connection issue rather than Flutter. Please try on another network and see if it works.
Closing this, as it doesn't seem to be an issue with Flutter. If you disagree, write in comments and I'll reopen.
Also check this link if you in China.


Enabling Backend Connection via API Key

Allow Backend Connection also via API Key next to the current Basic Auth (User name + password).
See: https://github.com/International-Data-Spaces-Association/DataspaceConnector/issues/364

Authentication data is added to  backend Connections (Generic Endpoints) via Data Sources:
PUT /api/endpoints/{id}/datasource/{dataSourceId}
The Swagger documentation of POST /api/datasources is
{
  "authentication": {
    "key": "string",
    "value": "string"
  },
  "type": "Database"
}

I am not sure how to set API Key for this endpoint and did not find any other documentation on this topic by now.

API key authentication can currently only be set directly on the artifact.
DataSource needs to be extended so that the user can save the API key authentication directly with the Backend Connection (Generic Endpoint) just like BasicAuth.

Current solution:
Basic auth: set key=user, value=password for data source
API-Key: only set value=api key
Implemented in e58f1db


Some user scripts affect component behavior

Bug, feature request, or proposal:
Some user scripts affect component behavior.such as <input>
Usually when I browse other sites have not been affected.
What is the expected behavior?
<input> should be the same as usual

What is the current behavior?
No longer have animation effects(:focus..),and color.just as native, except for placeholder

What are the steps to reproduce?
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
"@angular/core": "^4.4.1",
"@angular/material": "^2.0.0-beta.8",
"typescript": "^2.4.2",
ver. 63.0.3218.0 Chrome canary
Chrome.extensions -> Tampermonkey
Tampermonkey.userScript -> Anti-Adblock Killer | Reekv10.0
Is there anything else we should know?
When I found the problem, I just closed the plugin.
But there may be other people encounter such a situation, so I just feedback the problem

I would call this an issue with whatever scripts/extensions being used.


Added --stdout flag to output single file transforms to stdout

To use this tool in combination with others, I found it useful to have a option which allows to pipe the output of  a single file transform to stdout instead a file.
Changes:

Added output variable, which can be either file or stdout
Added log() and logError() functions so that no debugging messages are written to stdout if output is set to stdout

Example Usage:
doctoc README.md --stdout

Sorry for not responding sooner, I actually like this.
How about we just redirect all log messages to stderr which is the better way anyways IMO?
So all we'd have to do is change all console.log to console.error.

Sure, you could do that. I seperated the log funtions into stdout  and stderr because then you can handle the output independently, e.g. redirect regular log messages to /dev/null and just get errors on the console (on UNIX of course).

Yeah, either way works for me.
Could you please squash these commits into one and rebase on master? Currently there are merge conflicts.

Replaced by #48


Update E2E kube version

What type of PR is this?
/kind failing-test

What this PR does / why we need it:
Kubespray adjusted minimum version support (https://github.com/kubernetes-sigs/kubespray/pull/10420)
Which issue(s) this PR fixes:

Fixes #954
Special notes for your reviewer:

/lgtm

/lgtm


Deploy ENS to the blockchain container

It should be pretty easy to deploy ENS suite to Ganache which would enable testing and development with ENS names. Only question is how the domain names would be managed in some form of UI.
https://docs.ens.domains/deploying-ens-on-a-private-chain

We don’t need to manage them in UI imho, we just need to do this through cli


Update for compatability with the dart dev compiler

Problem
I'm using this package in a project that we're keeping compatible with the ddc. The == implementation caused a compilation error.
Solution
Update the type signature to prevent the following error:
error: Invalid override. The type of 'Diff.==' ('(Diff) → bool') isn't a subtype of 'Object.==' ('(dynamic) → bool'). (strong_mode_invalid_method_override at [diff_match_patch] lib/src/diff/diff.dart:75)

+1

@localvoid are there any other repo maintainers we should tag to review this?

@localvoid circling back to this.  Is there anything we can do to help get this merged / released?

@localvoid I checked the google's official implementation. They are having the same issue.

@localvoid is the source code in the google repo the one used for the pub package, or is it this one?

@localvoid We would have to go through a few internal hoops to transfer this package to our org - would you be open to giving a Workiva member maintainer permissions on this project where it currently is?

@aaronlademann-wf this one is published at the diff_match_patch pub package.
@clairesarsam-wf sure. I'll transfer ownership over this repo and pub package, just need a github account to transfer this repo and email to transfer diff_match_patch pub package.

I upgraded this code to Dart 2.0, available at https://github.com/jheyne/diff-match-patch. Hopefully, my changes (or similar) will find it's way to this repository and pub.

@jheyne I've stopped using Dart, so it is better if someone who is actively working with Dart will take ownership over this repo/pub package. If you want to maintain it, I'll transfer it to you. I just need an email address to transfer pub package.

Sure, Boris -- thanks for your work on this.
<EMAIL_ADDRESS>Jim
On Sun, Oct 7, 2018 at 10:30 PM Boris Kaul<EMAIL_ADDRESS>wrote:

@jheyne https://github.com/jheyne I've stopped using Dart, so it is
better if someone who is actively working with Dart will take ownership
over this repo/pub package. If you want to maintain it, I'll transfer it to
you. I just need an email address to transfer pub package.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/localvoid/diff-match-patch/pull/2#issuecomment-427725187,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhaHB8KwR6o3XGF2wGinp2SpjMqh_Fbks5uiuMGgaJpZM4Vy8rz
.


handleLogoutRequest and config file

Hello to everybody,
I've got a small issue I haven't been able to resolve during the last two weeks, so I'm coming here for some help.
I have a phpCAS client app. When someone logs out of the CAS server, the server sends (apparently) a logout notification to my app.
But when I logout of the server and I refresh my client app I'm still connected. Looking at the log file, no request was intercepted.
To handle the logout I just added the phpCAS:: handleLogoutRequest(); line before the phpCAS::forceAuthentication(); one. Is there something I should add also to the config.php file to handle the logout request ?
Thanking you in advance for your help.

Please check #195 and test one of our examples https://github.com/apereo/phpCAS/blob/master/docs/examples/example_logout.php

And also #212

Typically the connection from the CAS server to the phpCAS service is not working:  (flow of the logout signal is from client -> CAS server -> phpCAS service)

You need working HTTPS
You need a Certificate trusted by the CAS server
Your need working network connection/routing/dns between the systems (loadbalancers or network topology may get in the way)

Thank you for your quick answer.
I doubt it is a HTTPS or certificate issue : the app has worked up to now (before I implemented the central logout feature). Besides when I look at the log files, no error message. Just a :
CD4E .=> CAS_Client::handleLogoutRequests(true, array ()) [CAS.php:1298]
CD4E .|    Not a logout request [Client.php:1744]
CD4E .<= ''
Which seems strange because the guy who are managing the CAS server assured me that a logout request was send to my application.
Here's the code for the index.php :
`<?php
/**
* Example for proxied service with session support
*
* PHP Version 5
*
* @file     example_service.php
* @category Authentication
* @package  PhpCAS
* @author   Joachim Fritschi<EMAIL_ADDRESS>* @author   Adam Franco<EMAIL_ADDRESS>* @license  http://www.apache.org/licenses/LICENSE-2.0  Apache License 2.0
* @link     https://wiki.jasig.org/display/CASC/phpCAS
*/
  require_once 'config.php';
  require_once $phpcas_path . '/CAS.php';
  phpCAS::client(CAS_VERSION_3_0, $cas_host, $cas_port, $cas_context);
  phpCAS::setCasServerCACert($cas_server_ca_cert_path);
  phpCAS::handleLogoutRequests();
  phpCAS::forceAuthentication();

  if (isset($_REQUEST['logout'])) {
  	phpCAS::logout();
  }
  include 'webapp.php';

?>`

There is a big difference from a HTTPS certificate working in your browser (with populated trusted certificate authorities) and the certificate being accepted as "trusted" by the java library on the CAS server itself. It's not uncommon for a trust store file of a java installation to be empty....
Ask your CAS admin to check if he sees a connection denied or similar entry in the CAS server logs. Without specific ssl debugging enabled any un-trusted certificate shows up as a connection error.
I have also seen many cases were CAS servers were behind load balancers and could not initiate any outgoing TCP connections or routing/DNS was not working fully. Ask your CAS admin to use any commandline web clients to connect your application (wget, curl...)
You can also use wireshark or any network monitoring to check if any connection is established on your end.  If the SSL handshake fails it will not even register in your webserver or phpCAS logs but it would be visible in the network data.

Thank you very much.
I'll see with the admin then.

So, I contacted the adminstrator of the CAS server, and the only thing he told me was that he's seeing a logout request sent by the CAS sever (image in attachment). And he asked me to see if I received that request on my server.
Not really knowing what I was doing, I did a tcpdump listening to port 443 and I see indeed the logging in to my app, and also a request with a F flag when I logout of the CAS server.
Don't know if it is of any help, neither what I'm really supposed to do now...

Have you checked the debug log of phpCAS?  I typically just "tail -f" the debug log and than issue a logout... You can then follow the trace what phpCAS is doing with any incoming request.
If you cannot see anything in the logs the issue is outside of phpCAS....
I can only recommend that you start debugging issues like this with our simple examples to avoid to much complexity. If the session handling is not done by phpCAS itself a logout will only work if configure a custom callback handler to do whatever magic is needed in your application phpCAS::setSingleSignoutCallback()

Issue has been resolved. Here's what I did :
Using SSLLabs I've tested the SSL certificate. The result was an "Incomplete Certificate". Apparently browser can overcome this issue, but it wasn't the case of the CAS server (or Curl, or Python).
I had to complete the apache ssl.conf file with the SSLCertificateChainFile option.
That being done, I could send a secure POST request with curl and python. But the logout function still wasn't working.
The phpCAS logout file showed that now the logout request was received but the server sending it was different than the one responsible for the login, so I had to add it in the phpCAS::handleLogoutRequest options.
And now, finally, it all works.
Thank you very much for all your help jfritschi (and indeed, as you stated at the beginning, it was a SSL issue) !

Glad you figured it out!


Generate training data from Freebase index

We need to retrieve training examples from Freebase index.
The training examples can be used in machine learning applications.
Depending on the target property, the retrieval queries will change to reflect how data is represented in Freebase RDF triples.

@lintool Is this still relevant?

Closing, Freebase code removed in #329 - no longer relevant


Support filtering in backtrace command

Closes #137

c9d9f58910d0f6eb2f641996730bbe12a99e57a9 fixed the index issue.
Also support to filter by method name.
Do you have any problem about that?

of course I don't have a problem about that 😅
I think it should be helpful too 👍


Handle NetBSD in generic code switches

Enhance the NetBSD support in generic code using the linux struct,
and where applicable use the netbsd struct.

@plusun I think that this is the penultimate change for now. Verifying whether it still works is welcome!
It works for me locally.

@krytarowski I've checked it and it works! Sorry for the late reply!

@plusun thank you!


[FOLLOWUP] Use the PHP 7.2 language level for Rector

Followup to #771

coverage: 38.583%. remained the same
when pulling f539e54b2e61bef0fb18e93148b3cf784b73e86f on followup/rector-php-version
into 3eb42ce6d809c884e08aeeb1a34ca605f9c0becc on main.


page-set: make generic

This is an alternative approach to making trie algorithms generic over where pages are stored in-memory. There are two key benefits:

This doesn't require any user to import pages into a BTreeMap, rather enabling them to store pages in a way which is natural to their I/O, caching, and so on.
Leads to cleaner code

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#33  👈
#32
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rphmeier and the rest of your teammates on  Graphite

Merge activity

Mar 28, 1:43 PM EDT: @rphmeier started a stack merge that includes this pull request via Graphite.


[cinder-csi-plugin] Enable only required services

What this PR does / why we need it:
This PR enables only nova, neutron, glance , cinder for the cinder csi e2e job.
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/test openstack-cloud-csi-cinder-e2e-test


requests doen't work with IPv6 addresses that contains the '%' sign

Some IPv6 addresses contains the '%' sign ( link-local addresses : ex. fe80::21b:63ff:feab:e6a6%eth0 or [fe80::21b:63ff:feab:e6a6%eth0] )
When using this addresses the requests library raises the fallowing exception: "requests.exceptions.InvalidURL: Invalid percent-escape sequence: 'et'"
(raised by the function unquote_unreserved() from the utils.py).
If I put as first line in this function the "return uri" line (in other words if I pass over this function), everything works ok.

comment: In some environments IPv6 Link Local addressing is VERY useful. If you would fix it, that would be helpful.

@steve100 can you test if the rfc3986 library handles this appropriately?

what do I have to load to test the rfc3986 library?

I am also stuck on this issue. I can also pitch in if needed.

if someone tells me how to test with this library:
I can.  rfc3986
On Fri, Mar 11, 2016 at 1:42 AM, littypreeth<EMAIL_ADDRESS>wrote:

I am also stuck on this issue. I can also pitch in if needed.
—
Reply to this email directly or view it on GitHub
https://github.com/kennethreitz/requests/issues/1985#issuecomment-195219184
.

I had forgotten that there's already an open issue for this feature within rfc3986: https://github.com/sigmavirus24/rfc3986/issues/2 so there's no need to test it.

Thanks.
I know the issues that surround using the IPv6 Link Local Address..
Here it is   SO tempting to use the link local address help get a device or
vm configured with better addresses and other configuration information.
Steve
On Fri, Mar 11, 2016 at 2:32 PM, Ian Cordasco<EMAIL_ADDRESS>wrote:

I had forgotten that there's already an open issue for this feature within
rfc3986: sigmavirus24/rfc3986#2
https://github.com/sigmavirus24/rfc3986/issues/2 so there's no need to
test it.
—
Reply to this email directly or view it on GitHub
https://github.com/kennethreitz/requests/issues/1985#issuecomment-195512868
.

Old thread, but I'm running into this LL IPv6 % handling issue and wondering if was ever resolved?  people are (successfully) using curl instead of requests and it breaks my heart.  I'm using python 2.7.11 and requests 2.9.1

No. It's not resolved yet.
On 17-Aug-2016 9:47 pm, "briggr1"<EMAIL_ADDRESS>wrote:

Old thread, but I'm running into this LL IPv6 % handling issue and
wondering if was ever resolved? people are (successfully) using curl
instead of requests and it breaks my heart. I'm using python 2.7.11 and
requests 2.9.1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kennethreitz/requests/issues/1985#issuecomment-240464306,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ9F5Qht1dy6A2VFw1UN_htNSCgf_dnOks5qgzQFgaJpZM4BuSvZ
.

updated to python 2.7.12, and requests 2.11.0 - no dice.

So I'm going to start working on adding this support to rfc3986. In reading the specification, there's this:

In a URI, a literal IPv6 address is always embedded between "[" and
"]".  This document specifies how a <zone_id> can be appended to the
address.  According to URI syntax [RFC3986], "%" is always treated as
an escape character in a URI, so, according to the established URI
syntax [RFC3986] any occurrences of literal "%" symbols in a URI MUST
be percent-encoded and represented in the form "%25".  Thus, the
scoped address fe80::a%en1 would appear in a URI as
http://[fe80::a%25en1].

So the right thing to do is encode the % sign it seems.
@Lukasa should we reopen this to track the work that we need to do in urllib3?

In the first instance let's just open a relevant issue on urllib3.

Hi @Lukasa
Wondering if you could post the related issue number for this on urllib3 so I could track it?  I tried looking for it, but didn't see it (I did see something about proxy handling...).  Thanks in advance
Also, for others that might be wondering - there is a workaround: if your system only has 1 interface with IPv6 addressing, then you do not need to supply the %, and things work just fine.  Unfortunately, all of my testing involves many networks with different vlans and I need IPv6 support on them all.

@briggr1 I don't believe any tracking issue for this was actually opened on urllib3. I'd need @sigmavirus24 to outline exactly what work he believes is needed though: in my initial testing urllib3 seems to be handling this appropriately.

So with shazow/urllib3#1012 if your URL is RFC-6874 compliant, then I believe everything should "just work".


Fixed height scaling

I made this change because I was faced with the problem of scaling the image in height. My change concerns the _ItemsBox class, if you change the value of size_hint: None, None to size_hint_x: None, then the problem is solved.
For the test, the code from the documentation was used
https://user-images.githubusercontent.com/40869738/113522206-4be04c80-95a7-11eb-8165-fbb2918932bc.mp4

@Neizvestnyj
Thanks for the PR.
Please make more detailed commits: why did you make this change, what fixes this change, in which class.

@Neizvestnyj
Thanks for the PR.
Please make more detailed commits: why did you make this change, what fixes this change, in which class.

done

@Neizvestnyj
Reading your commit, I don't understand at all why you changed something. The commit should be succinct and understandable. Scaling what? The height of what exactly? After a month, someone will read the commit history ... What can be understood from the Fixed height scaling commit?..

@Neizvestnyj
Reading your commit, I don't understand at all why you changed something. The commit should be succinct and understandable. Scaling what? The height of what exactly? After a month, someone will read the commit history ... What can be understood from the Fixed height scaling commit?..

So I think it's clearer, there is still a limit on the number of characters

@Neizvestnyj There is no limit on the number of characters for a commit.

@Neizvestnyj There is no limit on the number of characters for a commit.

Like 50 characters limit

@Neizvestnyj It does not matter. Only quality matters.

Then tell me, is it better?  Or what else to change?

@Neizvestnyj For example - https://github.com/kivymd/KivyMD/commit/907a90abc46edd7a9315d4c955532b30699e29d7 - clear and simple commit

@HeaTTheatR It should be clearer now

@Neizvestnyj
I mean the text of the commit, not the text of the PR:

@HeaTTheatR Yes, I understand, just as you can see, I changed the name several times, and creating a new pool request every time is stupid.  Is it a normal title now?

@Neizvestnyj
Changed the value of the size_hint parameter in the _ItemsBox rule to properly scale elements of the MDSwiper class when the root application window is resized.


"UTXO" and not "Utxo" should be in UTXO details

"UTXO" and not "Utxo" should be in UTXO details
Open UTXO Screen
Check one of the UTXO's details
It is written "Utxo" details
and "Utxo" history
should be "UTXO"

checked


Implement experiment lock files

In order to allow to run more experiments of the same model safely in parallel, we need to implement lockfiles. These files would have all the necessary fields in order for check_params to work and block running more experiments with the same parameters concurrently. One consideration to keep in mind, the start of the jobs in the array should be somewhat randomized at the beginning as there is potential for collision, however I have yet to found a simple argument for this in the SLURM docummention.

The lockfiles can either be deleted on failure or kept. Both cases are easily supported in evaluation, which throws out samples without scores. The choice is probably method dependent as some of them are more deterministic than others.


Update Telegram.php

Support for unicode characters in commands. (try number three, edit file in github editors)

What a...


SvelteKit reloads pages and clears form data on mobile

Describe the bug
I have an issue on mobile (iOS/iPhone). I'm developing a form that has text inputs. If I enter some data and swipe to a different app for a short while, when I swipe back to the SvelteKit app, it refreshes the page and clears all the form inputs.  Just tested and this even happens if I simply add an input the index.svelte of the skeleton app after a fresh SvelteKit install.
This does not seem to happen with Svelte apps. Only SvelteKit apps.
Mobile ONLY! Desktop apps are fine
Reproduction
Install the skeleton SvelteKit app.
Add an input to the index.svelte page.
Run the app
Enter some data in the form input
Switch to another app
Wait 5+ seconds
Switch back to the SvelteKit app
Watch the form data clear...
Logs
No response
System Info
System:
    OS: macOS 12.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 48.90 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.5.0 - /usr/local/bin/node
    npm: 8.5.1 - /usr/local/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 98.0.4758.109
    Firefox: 97.0.1
    Safari: 15.2
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.30
    @sveltejs/kit: next => 1.0.0-next.292
    svelte: ^3.44.0 => 3.46.4

Severity
blocking all usage of SvelteKit
Additional Information
No response

Is this in dev mode, or a production version of the app?

Dev mode.

I created a simple kit app with a <input> tag.
And I access the app over ngrok, but I couldn't reproduce it.
So could you please share us specific reproduce step?

{name}
<input bind:value={name}>

Hello {name}!

https://user-images.githubusercontent.com/19153718/156915522-71180b6c-0c80-4500-9180-2cb750f521e3.mov

Please read the instructions for the bug template. I will close this issue shortly if code is not provided shortly

A link to a repository, or a fork of https://node.new/sveltekit, that reproduces the issue. Explaining how to reproduce is generally not enough. It pushes the burden of creating a reproduction project onto a small set of volunteer maintainers and isn't scalable. If no reproduction is provided, the issue will be closed.

Dev server started on mac.
`SvelteKit v1.0.0-next.294
local:   http://localhost:3000
network: http://<IP_ADDRESS>:3000`
Code in the index.svelte from the skeleton installation with a form and input element added.
`Welcome to SvelteKit
Visit kit.svelte.dev to read the documentation

`
Accessed the app by the public IP address provided by the --host option.
	"scripts": { 		"dev": "svelte-kit dev --host",
Link to screen recording showing the issue on my iPhone.
https://youtu.be/0lulzwWF8_U

This issue seems to be related to Vite as I can also reproduce it from the vanilla Vite template https://vite.new/vanilla-ts


Atualize o conteúdo/patrocinadores/começar-com-patrocinadores do github/sobre-gi...

…thub-sponsors.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Eu quero ganhar


fix(@angular/cli): directly remove ansi color codes when no color support

Third party libraries can attempt to write color codes to the output even though the CLI has already determined that color should not be used.  The previously implemented color removal code is no longer functional since the update of ansi-colors to 4.1.0.  While this appears to be a defect in the aforementioned package, the new CLI removal method not only bypasses the defect but also unneeded execution logic that the CLI does not need in this case.
Fixes: #17053

Also merged to patch branch (9.0.x).


Fix the behavior of auto-loading credentials chain on S3

Problem Statement
Currently, Lance does not support a "default chain of credentials lookups", which makes the experience on AWS bad.
AWS rust sdk has the desired functionalty
https://docs.rs/aws-config/latest/aws_config/default_provider/credentials/struct.DefaultCredentialsChain.html
Not sure how to integrate into object_store rust crate yet.

There was a thread in Arrow-rs (i forgot where) that talks about how pulling in the AWS SDK makes the crate really big / complicated. I don't remember whether it was on github or discord. But it's something to watch out for.

quick note: object_store only recently exposed the configurbility of credentials field https://github.com/apache/arrow-rs/pull/4235
Going to need to upgrade arrow-rs for this one


Presence Notifications Improvements

There are some issues with the current presence notifications, namely:

[ ] Notifications currently show for users already in the session before we join. Ideally they should not.
[ ] A notification shows that represents the current user. Ideally it should not.

WIP here https://github.com/vizhub-core/vzcode/pull/247
Related thread in ShareDB: https://github.com/share/sharedb/issues/632

Closed in https://github.com/vizhub-core/vzcode/pull/247


johndanz/ch15039/canceled-orders-do-not-automatically-disappear

https://app.clubhouse.io/augur/story/15039/canceled-orders-do-not-automatically-disappear-from-open-orders-list
All the event logs are messed up, this is a high priority.
fixed log handler, at some point things where changed to emit an array of log objects, instead of each log object individually. This is causing the check, which assumes log is an object, to fail and not send the log to the log listeners, there by messing up all of our updating and causing canceled orders to stick around on the page until a refresh.

Coverage decreased (-0.03%) to 66.592% when pulling 627084e64fc2ce39f3057d26ee51659d5da6ea8b on johndanz/ch15039/canceled-orders-do-not-automatically-disappear into 86a043962257e0a32e61daa56d9ccbdb6f8e94a1 on master.


DBZ-121 take2

The approach I ended up settling on is outlined in (1) here: https://github.com/debezium/debezium/pull/193 .
This approach is built on top of @rhauch 's approach that he began here: https://github.com/debezium/debezium/pull/129
Again, my main changes were to try to eliminate the need for the TopicMappingProvider abstraction. Now, each table shares the same instance of the TopicMapper, rather than instantiating a new one. This required changing the TopicMapper.addNonRowFieldsToKey() method, since this can be called at any time and different tables will have different values to add and they all share the same TopicMapper instance now. Instead, the functionality is now provided by the TopicMapper.getNonRowFieldsToAddToKey() method.

Overall, I like where you're going, and it is simpler than either of my original approaches. One thing that we might consider is having a initialize(Configuration) method on the provider so that the implementation could take custom configuration properties.

@rhauch , not sure if you get notifications when I push more commits here, but I've resolved some of the issues you commented on. Curious what you think whenever you get a chance.

Thanks @dasl- for your continued work and patiences on this topic. My one remaining question is whether we should use a single TopicMapper, or whether we can change the design slightly to support multiple chained TopicMapper instances. This might be possible if each mapper were to return null if they don't apply, and then an ChainingTopicMapper is responsible for iterating through the list of instances and stopping as soon one successfully calls the method. The chaining is straightforward, but getting it to work when we're calling this in multiple places seems harder.
To be honest, I realized the benefit of having multiple when looking at the design for the Single Message Transforms. It sure would be easier to set up regexes for a few distinct mappers, rather than come up with a single likely-to-be more complex regex that handles all of my tables.
The only reason I ask about this is in case the current configuration pattern doesn't allow multiple mappers; then we'd be stuck and would have to configure multiple ones a completely different way. I'd rather get the configuration right now.
WDYT?

Abandoning this PR in favor of a new approach. See: https://github.com/debezium/debezium/pull/211

Abandoning this PR in favor of a new approach. See: #211


return secrets back to original structure

This returns the secrets back to the original config structure however omits secrets from the configmap.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@11319f1). Learn more about missing BASE report.

Additional details and impacted files
@@          Coverage Diff           @@
##             main     #84   +/-   ##
======================================
  Coverage        ?   9.77%
======================================
  Files           ?      22
  Lines           ?     696
  Branches        ?       0
======================================
  Hits            ?      68
  Misses          ?     622
  Partials        ?       6

Flag
Coverage Δ

unittests
9.77% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Closes #369 : Fix input validation in search by barcode

Description
Enclosed the entire layout in a ScrollView so that it can be scrolled and the button is easily accessible and input validation is possible.
Related issues and discussion
Fixes #369
Screen-shots, if any

Checklist
Make sure you've done all the following (You can delete the checklist before submitting)

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.
[x] Code is well documented
[x] Include unit tests for new functionality
[x] All user-visible strings are made translatable
[x] Code passes Travis builds in your branch
[x] If you have multiple commits please combine them into one commit by squashing them.
[x] Read and understood the contribution guidelines .

Hey @huzaifaiftikhar,
Your changes look good to me!


Typo in the README

In the 2AT2 description, there is "2AT2 stands for AAssembler for Assembly Team 2".

"IAT2" is still mentioned in the README.

fixed in https://github.com/algosup/2023-2024-project-3-virtual-processor-team-2/commit/ecdc488f5891c4747e09c2803bd3e0134c830297


RNG-181: LXM family to support SplittableUniformRandomProvider

Create generic RandomStreams class that can stream objects created with a seed and splittable source of randomness. The seed uses the stream position mixed with random bits to ensure it is unique within the stream (up to a size limit of 2^60). Use this feature to support splits in the LXM family.
Add isSplittable method to RandomSource to use to identify supported interfaces.
Use of the splittable interface by other modules requires an exception in RevAPI for exposing an external class in the API. This is similar to exposure of UniformRandomProvider and is allowed. The change is non-breaking for binary and source compatibility (see revapi java.class.externalClassExposedInAPI).

Codecov Report

Merging #117 (0021eb9) into master (0238d2d) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             master     #117    +/-   ##
==========================================
  Coverage     99.73%   99.73%
- Complexity     1378     1420    +42
==========================================
  Files           150      151     +1
  Lines          5558     5724   +166
  Branches        531      552    +21
==========================================
+ Hits           5543     5709   +166
  Misses           11       11
  Partials          4        4

Impacted Files
Coverage Δ

...java/org/apache/commons/rng/core/BaseProvider.java
100.00% <ø> (ø)

...g/apache/commons/rng/core/source32/LXMSupport.java
100.00% <ø> (ø)

...g/apache/commons/rng/core/source64/LXMSupport.java
100.00% <ø> (ø)

...rg/apache/commons/rng/core/source32/L32X64Mix.java
100.00% <100.00%> (ø)

...apache/commons/rng/core/source64/L128X1024Mix.java
100.00% <100.00%> (ø)

.../apache/commons/rng/core/source64/L128X128Mix.java
100.00% <100.00%> (ø)

.../apache/commons/rng/core/source64/L128X256Mix.java
100.00% <100.00%> (ø)

.../apache/commons/rng/core/source64/L64X1024Mix.java
100.00% <100.00%> (ø)

...g/apache/commons/rng/core/source64/L64X128Mix.java
100.00% <100.00%> (ø)

...che/commons/rng/core/source64/L64X128StarStar.java
100.00% <100.00%> (ø)

... and 3 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Adds documentation for getting all secrets in dotenv format

This was added in 2ca2be6 but missing from the README. This PR just ensures the docs are in sync.

Thanks @nkhoshini!

@nkhoshini I merged #167 because it mostly incorporated your changes. There were a couple other bits in your PR that I used after I fixed merge conflicts introduced by #167. I'm closing this PR but you'll still get credit in the release notes :). Thanks again for the PR!


Add sis_id columns to course and course_section tables (#42)

This PR adds a migration and modifies course_inventory/inventory.py in order to add and populate sis_id columns in the course and course_section tables of the database. In addition, I modified an existing UDW query to use the params parameter of pd.read_sql, hopefully resolving a SQL injection warning raised by Codacy. Also, I modified the existing process_sis_id mapping function so it could be used to also drop non-integer SIS ID values for sections. This PR aims to resolve issue #42.
Resolves #42.

I'm going to merge this now to not hold up anything else, but I'm going to wait before we roll this out while we're still working with IQ on understanding the new data from other recent PRs. Thanks for the reviews!


Document steps you can take to monitor CD deployment

It's quite a black box experience otherwise! And devs shouldn't need to dig around for
these links / pipeline information.

Agreed it should all be handled for you and that sitting and monitoring a release isn't ideal. It's a shame we don't have something like the GOV.UK PaaS UI, which shows you how the release is proceeding and where it fails.
It's quite unnerving to not see any change to the Release page (smart-answers build took about 5 minutes before the release tag was registered). And if it were to stall halfway through because of a Smokey error, we have no real visibility of that - I guess I'd just have to do some digging if I notice after 15 minutes or so that the release hasn't gone beyond Integration.
In that case it's useful to be able to point to the various bits of the pipeline to help guide the developer to where it went wrong. That slideshow looks very useful, but I do think that info should live in the dev docs, where it can be reviewed and kept up to date, and have its various subsections linked to.
Could I have a go at writing up that slideshow as a 'how to' doc?

I'd like to hold off on that for now. The "Learning GOV.UK" decks should be replayed at roughly the same frequency as we review the dev docs, so I regard them as some form of documentation. It would be a shame to repeat the information if we don't have to. After I present it, I'll populate the speaker notes to actually explain what's going on with links and stuff. Can we try linking to that (next week) as a lower effort/maintenance first pass?

Superseded by #2649.