Molecule can not run Gathering Facts when using podman

Issue Type

Bug report

Molecule and Ansible details
ansible --version && molecule --version
ansible 2.9.5
  config file = None
  configured module search path = ['/home/florian/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible
  executable location = /home/florian/venv/molecule/bin/ansible
  python version = 3.7.6 (default, Jan 30 2020, 09:44:41) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]

molecule 3.0.3.dev9+g7fd93e8d
   ansible==2.9.5 python==3.7

Molecule installation method (one of):

source

Ansible installation method (one of):

pip

Detail any linters or test runners used:
Desired Behavior
I created a new role using molecule init role --driver-name podman test-role.
Running molecule check runs the molecule checks - without failing when using podman:
podman --version
podman version 1.8.0

Actual Behaviour
When attempting to run molecule check it breaks during the Gathering Facts stage:
--> Test matrix

└── default
    ├── dependency
    ├── cleanup
    ├── destroy
    ├── create
    ├── prepare
    ├── converge
    ├── check
    ├── cleanup
    └── destroy

--> Scenario: 'default'
--> Action: 'dependency'
Skipping, missing the requirements file.
--> Scenario: 'default'
--> Action: 'cleanup'
Skipping, cleanup playbook not configured.
--> Scenario: 'default'
--> Action: 'destroy'
--> Sanity checks: 'podman'
DEBUG: ANSIBLE ENVIRONMENT
---
ANSIBLE_CONFIG: /home/florian/.cache/molecule/test-role/default/ansible.cfg
ANSIBLE_FILTER_PLUGINS: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/filter:/home/florian/.cache/molecule/test-role/default/plugins/filter:/home/florian/code/test-role/plugins/filter:/home/florian/.ansible/plugins/filter:/usr/share/ansible/plugins/filter
ANSIBLE_LIBRARY: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules:/home/florian/.cache/molecule/test-role/default/library:/home/florian/code/test-role/library:/home/florian/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
ANSIBLE_ROLES_PATH: /home/florian/.cache/molecule/test-role/default/roles:/home/florian/code:/home/florian/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles

DEBUG: MOLECULE ENVIRONMENT
---
MOLECULE_DEBUG: 'True'
MOLECULE_DEPENDENCY_NAME: galaxy
MOLECULE_DRIVER_NAME: podman
MOLECULE_ENV_FILE: /home/florian/code/test-role/.env.yml
MOLECULE_EPHEMERAL_DIRECTORY: /home/florian/.cache/molecule/test-role/default
MOLECULE_FILE: /home/florian/.cache/molecule/test-role/default/molecule.yml
MOLECULE_INSTANCE_CONFIG: /home/florian/.cache/molecule/test-role/default/instance_config.yml
MOLECULE_INVENTORY_FILE: /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml
MOLECULE_PROJECT_DIRECTORY: /home/florian/code/test-role
MOLECULE_PROVISIONER_NAME: ansible
MOLECULE_SCENARIO_DIRECTORY: /home/florian/code/test-role/molecule/default
MOLECULE_SCENARIO_NAME: default
MOLECULE_STATE_FILE: /home/florian/.cache/molecule/test-role/default/state.yml
MOLECULE_VERIFIER_NAME: ansible
MOLECULE_VERIFIER_TEST_DIRECTORY: /home/florian/code/test-role/molecule/default/molecule

DEBUG: SHELL REPLAY
ANSIBLE_CONFIG=/home/florian/.cache/molecule/test-role/default/ansible.cfg ANSIBLE_FILTER_PLUGINS=/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/filter:/home/florian/.cache/molecule/test-role/default/plugins/filter:/home/florian/code/test-role/plugins/filter:/home/florian/.ansible/plugins/filter:/usr/share/ansible/plugins/filter ANSIBLE_LIBRARY=/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules:/home/florian/.cache/molecule/test-role/default/library:/home/florian/code/test-role/library:/home/florian/.ansible/plugins/modules:/usr/share/ansible/plugins/modules ANSIBLE_ROLES_PATH=/home/florian/.cache/molecule/test-role/default/roles:/home/florian/code:/home/florian/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles MOLECULE_DEBUG=True MOLECULE_DEPENDENCY_NAME=galaxy MOLECULE_DRIVER_NAME=podman MOLECULE_ENV_FILE=/home/florian/code/test-role/.env.yml MOLECULE_EPHEMERAL_DIRECTORY=/home/florian/.cache/molecule/test-role/default MOLECULE_FILE=/home/florian/.cache/molecule/test-role/default/molecule.yml MOLECULE_INSTANCE_CONFIG=/home/florian/.cache/molecule/test-role/default/instance_config.yml MOLECULE_INVENTORY_FILE=/home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml MOLECULE_PROJECT_DIRECTORY=/home/florian/code/test-role MOLECULE_PROVISIONER_NAME=ansible MOLECULE_SCENARIO_DIRECTORY=/home/florian/code/test-role/molecule/default MOLECULE_SCENARIO_NAME=default MOLECULE_STATE_FILE=/home/florian/.cache/molecule/test-role/default/state.yml MOLECULE_VERIFIER_NAME=ansible MOLECULE_VERIFIER_TEST_DIRECTORY=/home/florian/code/test-role/molecule/default/molecule

DEBUG: COMMAND
/home/florian/venv/molecule/bin/ansible-playbook --skip-tags=molecule-notest,notest --diff --inventory=/home/florian/.cache/molecule/test-role/default/inventory /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/destroy.yml -vvv

    ansible-playbook 2.9.5
      config file = /home/florian/.cache/molecule/test-role/default/ansible.cfg
      configured module search path = ['/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules', '/home/florian/.cache/molecule/test-role/default/library', '/home/florian/code/test-role/library', '/home/florian/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
      ansible python module location = /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible
      executable location = /home/florian/venv/molecule/bin/ansible-playbook
      python version = 3.7.6 (default, Jan 30 2020, 09:44:41) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]
    Using /home/florian/.cache/molecule/test-role/default/ansible.cfg as config file
    host_list declined parsing /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml as it did not pass its verify_file() method
    script declined parsing /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml as it did not pass its verify_file() method
    Parsed /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml inventory source with yaml plugin

    PLAYBOOK: destroy.yml **********************************************************
    1 plays in /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/destroy.yml

    PLAY [Destroy] *****************************************************************
    META: ran handlers

    TASK [Destroy molecule instance(s)] ********************************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/destroy.yml:8
    <<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: florian
    <<IP_ADDRESS>> EXEC /bin/sh -c 'echo ~florian && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572 `" && echo ansible-tmp-1582623730.4329584-169574783148572="` echo /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572 `" ) && sleep 0'
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/commands/command.py
    <<IP_ADDRESS>> PUT /home/florian/.ansible/tmp/ansible-local-84632p65v1w8/tmp_z8q24m4 TO /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572/AnsiballZ_command.py
    <<IP_ADDRESS>> PUT /home/florian/.ansible/tmp/ansible-local-84632p65v1w8/tmpbgtycxr3 TO /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572/async_wrapper.py
    <<IP_ADDRESS>> EXEC /bin/sh -c 'chmod u+x /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572/ /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572/AnsiballZ_command.py /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572/async_wrapper.py && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c 'ANSIBLE_ASYNC_DIR='"'"'~/.ansible_async'"'"' /home/florian/venv/molecule/bin/python3 /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572/async_wrapper.py<PHONE_NUMBER>78 7200 /home/florian/.ansible/tmp/ansible-tmp-1582623730.4329584-169574783148572/AnsiballZ_command.py _ && sleep 0'
    changed: [localhost] => (item=None) => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": true
    }
    changed: [localhost] => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": true
    }

    TASK [Wait for instance(s) deletion to complete] *******************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/destroy.yml:15
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/utilities/logic/async_status.py
    Pipelining is enabled.
    <<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: florian
    <<IP_ADDRESS>> EXEC /bin/sh -c '/home/florian/venv/molecule/bin/python3 && sleep 0'
    FAILED - RETRYING: Wait for instance(s) deletion to complete (300 retries left).Result was: {
        "attempts": 1,
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false,
        "retries": 301
    }
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/utilities/logic/async_status.py
    Pipelining is enabled.
    <<IP_ADDRESS>> EXEC /bin/sh -c '/home/florian/venv/molecule/bin/python3 && sleep 0'
    FAILED - RETRYING: Wait for instance(s) deletion to complete (299 retries left).Result was: {
        "attempts": 2,
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false,
        "retries": 301
    }
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/utilities/logic/async_status.py
    Pipelining is enabled.
    <<IP_ADDRESS>> EXEC /bin/sh -c '/home/florian/venv/molecule/bin/python3 && sleep 0'
    changed: [localhost] => (item=None) => {
        "attempts": 3,
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": true
    }
    changed: [localhost] => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": true
    }
    META: ran handlers
    META: ran handlers

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

--> Scenario: 'default'
--> Action: 'create'
DEBUG: ANSIBLE ENVIRONMENT
---
ANSIBLE_CONFIG: /home/florian/.cache/molecule/test-role/default/ansible.cfg
ANSIBLE_FILTER_PLUGINS: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/filter:/home/florian/.cache/molecule/test-role/default/plugins/filter:/home/florian/code/test-role/plugins/filter:/home/florian/.ansible/plugins/filter:/usr/share/ansible/plugins/filter
ANSIBLE_LIBRARY: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules:/home/florian/.cache/molecule/test-role/default/library:/home/florian/code/test-role/library:/home/florian/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
ANSIBLE_ROLES_PATH: /home/florian/.cache/molecule/test-role/default/roles:/home/florian/code:/home/florian/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles

DEBUG: MOLECULE ENVIRONMENT
---
MOLECULE_DEBUG: 'True'
MOLECULE_DEPENDENCY_NAME: galaxy
MOLECULE_DRIVER_NAME: podman
MOLECULE_ENV_FILE: /home/florian/code/test-role/.env.yml
MOLECULE_EPHEMERAL_DIRECTORY: /home/florian/.cache/molecule/test-role/default
MOLECULE_FILE: /home/florian/.cache/molecule/test-role/default/molecule.yml
MOLECULE_INSTANCE_CONFIG: /home/florian/.cache/molecule/test-role/default/instance_config.yml
MOLECULE_INVENTORY_FILE: /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml
MOLECULE_PROJECT_DIRECTORY: /home/florian/code/test-role
MOLECULE_PROVISIONER_NAME: ansible
MOLECULE_SCENARIO_DIRECTORY: /home/florian/code/test-role/molecule/default
MOLECULE_SCENARIO_NAME: default
MOLECULE_STATE_FILE: /home/florian/.cache/molecule/test-role/default/state.yml
MOLECULE_VERIFIER_NAME: ansible
MOLECULE_VERIFIER_TEST_DIRECTORY: /home/florian/code/test-role/molecule/default/molecule

DEBUG: SHELL REPLAY
ANSIBLE_CONFIG=/home/florian/.cache/molecule/test-role/default/ansible.cfg ANSIBLE_FILTER_PLUGINS=/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/filter:/home/florian/.cache/molecule/test-role/default/plugins/filter:/home/florian/code/test-role/plugins/filter:/home/florian/.ansible/plugins/filter:/usr/share/ansible/plugins/filter ANSIBLE_LIBRARY=/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules:/home/florian/.cache/molecule/test-role/default/library:/home/florian/code/test-role/library:/home/florian/.ansible/plugins/modules:/usr/share/ansible/plugins/modules ANSIBLE_ROLES_PATH=/home/florian/.cache/molecule/test-role/default/roles:/home/florian/code:/home/florian/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles MOLECULE_DEBUG=True MOLECULE_DEPENDENCY_NAME=galaxy MOLECULE_DRIVER_NAME=podman MOLECULE_ENV_FILE=/home/florian/code/test-role/.env.yml MOLECULE_EPHEMERAL_DIRECTORY=/home/florian/.cache/molecule/test-role/default MOLECULE_FILE=/home/florian/.cache/molecule/test-role/default/molecule.yml MOLECULE_INSTANCE_CONFIG=/home/florian/.cache/molecule/test-role/default/instance_config.yml MOLECULE_INVENTORY_FILE=/home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml MOLECULE_PROJECT_DIRECTORY=/home/florian/code/test-role MOLECULE_PROVISIONER_NAME=ansible MOLECULE_SCENARIO_DIRECTORY=/home/florian/code/test-role/molecule/default MOLECULE_SCENARIO_NAME=default MOLECULE_STATE_FILE=/home/florian/.cache/molecule/test-role/default/state.yml MOLECULE_VERIFIER_NAME=ansible MOLECULE_VERIFIER_TEST_DIRECTORY=/home/florian/code/test-role/molecule/default/molecule

DEBUG: COMMAND
/home/florian/venv/molecule/bin/ansible-playbook --skip-tags=molecule-notest,notest --diff --inventory=/home/florian/.cache/molecule/test-role/default/inventory /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml -vvv

    ansible-playbook 2.9.5
      config file = /home/florian/.cache/molecule/test-role/default/ansible.cfg
      configured module search path = ['/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules', '/home/florian/.cache/molecule/test-role/default/library', '/home/florian/code/test-role/library', '/home/florian/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
      ansible python module location = /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible
      executable location = /home/florian/venv/molecule/bin/ansible-playbook
      python version = 3.7.6 (default, Jan 30 2020, 09:44:41) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]
    Using /home/florian/.cache/molecule/test-role/default/ansible.cfg as config file
    host_list declined parsing /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml as it did not pass its verify_file() method
    script declined parsing /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml as it did not pass its verify_file() method
    Parsed /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml inventory source with yaml plugin

    PLAYBOOK: create.yml ***********************************************************
    1 plays in /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml

    PLAY [Create] ******************************************************************
    META: ran handlers

    TASK [Log into a container registry] *******************************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml:9
    skipping: [localhost] => (item=None)  => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false
    }

    TASK [Check presence of custom Dockerfiles] ************************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml:23
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/files/stat.py
    Pipelining is enabled.
    <<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: florian
    <<IP_ADDRESS>> EXEC /bin/sh -c '/home/florian/venv/molecule/bin/python3 && sleep 0'
    ok: [localhost] => (item=None) => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false
    }
    ok: [localhost] => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false
    }

    TASK [Create Dockerfiles from image names] *************************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml:29
    skipping: [localhost] => (item=None)  => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false
    }

    TASK [Discover local Podman images] ********************************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml:47
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/cloud/podman/podman_image_info.py
    Pipelining is enabled.
    <<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: florian
    <<IP_ADDRESS>> EXEC /bin/sh -c '/home/florian/venv/molecule/bin/python3 && sleep 0'
    ok: [localhost] => (item=None) => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false
    }
    ok: [localhost] => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false
    }

    TASK [Build an Ansible compatible image] ***************************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml:55
    skipping: [localhost] => (item={'changed': False, 'skipped': True, 'skip_reason': 'Conditional result was False', 'item': {'image': 'docker.io/pycontribs/centos:7', 'name': 'instance', 'pre_build_image': True}, 'ansible_loop_var': 'item', 'i': 0, 'ansible_index_var': 'i'})  => {
        "ansible_loop_var": "item",
        "changed": false,
        "item": {
            "ansible_index_var": "i",
            "ansible_loop_var": "item",
            "changed": false,
            "i": 0,
            "item": {
                "image": "docker.io/pycontribs/centos:7",
                "name": "instance",
                "pre_build_image": true
            },
            "skip_reason": "Conditional result was False",
            "skipped": true
        },
        "skip_reason": "Conditional result was False"
    }

    TASK [Determine the CMD directives] ********************************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml:72
    ok: [localhost] => (item=None) => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false
    }
    ok: [localhost] => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": false
    }

    TASK [Create molecule instance(s)] *********************************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml:81
    <<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: florian
    <<IP_ADDRESS>> EXEC /bin/sh -c 'echo ~florian && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366 `" && echo ansible-tmp-1582623744.7301147-258857586846366="` echo /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366 `" ) && sleep 0'
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/commands/command.py
    <<IP_ADDRESS>> PUT /home/florian/.ansible/tmp/ansible-local-8586zy_49vdh/tmpee5uxpma TO /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366/AnsiballZ_command.py
    <<IP_ADDRESS>> PUT /home/florian/.ansible/tmp/ansible-local-8586zy_49vdh/tmp86fqnp_n TO /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366/async_wrapper.py
    <<IP_ADDRESS>> EXEC /bin/sh -c 'chmod u+x /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366/ /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366/AnsiballZ_command.py /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366/async_wrapper.py && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c 'ANSIBLE_ASYNC_DIR='"'"'~/.ansible_async'"'"' /home/florian/venv/molecule/bin/python3 /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366/async_wrapper.py<PHONE_NUMBER>83 7200 /home/florian/.ansible/tmp/ansible-tmp-1582623744.7301147-258857586846366/AnsiballZ_command.py _ && sleep 0'
    changed: [localhost] => (item=None) => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": true
    }
    changed: [localhost] => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": true
    }

    TASK [Wait for instance(s) creation to complete] *******************************
    task path: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/playbooks/podman/create.yml:109
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/utilities/logic/async_status.py
    Pipelining is enabled.
    <<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: florian
    <<IP_ADDRESS>> EXEC /bin/sh -c '/home/florian/venv/molecule/bin/python3 && sleep 0'
    changed: [localhost] => (item=None) => {
        "attempts": 1,
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": true
    }
    changed: [localhost] => {
        "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
        "changed": true
    }
    META: ran handlers
    META: ran handlers

    PLAY RECAP *********************************************************************
    localhost                  : ok=5    changed=2    unreachable=0    failed=0    skipped=3    rescued=0    ignored=0

--> Scenario: 'default'
--> Action: 'prepare'
Skipping, prepare playbook not configured.
--> Scenario: 'default'
--> Action: 'converge'
DEBUG: ANSIBLE ENVIRONMENT
---
ANSIBLE_CONFIG: /home/florian/.cache/molecule/test-role/default/ansible.cfg
ANSIBLE_FILTER_PLUGINS: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/filter:/home/florian/.cache/molecule/test-role/default/plugins/filter:/home/florian/code/test-role/plugins/filter:/home/florian/.ansible/plugins/filter:/usr/share/ansible/plugins/filter
ANSIBLE_LIBRARY: /home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules:/home/florian/.cache/molecule/test-role/default/library:/home/florian/code/test-role/library:/home/florian/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
ANSIBLE_ROLES_PATH: /home/florian/.cache/molecule/test-role/default/roles:/home/florian/code:/home/florian/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles

DEBUG: MOLECULE ENVIRONMENT
---
MOLECULE_DEBUG: 'True'
MOLECULE_DEPENDENCY_NAME: galaxy
MOLECULE_DRIVER_NAME: podman
MOLECULE_ENV_FILE: /home/florian/code/test-role/.env.yml
MOLECULE_EPHEMERAL_DIRECTORY: /home/florian/.cache/molecule/test-role/default
MOLECULE_FILE: /home/florian/.cache/molecule/test-role/default/molecule.yml
MOLECULE_INSTANCE_CONFIG: /home/florian/.cache/molecule/test-role/default/instance_config.yml
MOLECULE_INVENTORY_FILE: /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml
MOLECULE_PROJECT_DIRECTORY: /home/florian/code/test-role
MOLECULE_PROVISIONER_NAME: ansible
MOLECULE_SCENARIO_DIRECTORY: /home/florian/code/test-role/molecule/default
MOLECULE_SCENARIO_NAME: default
MOLECULE_STATE_FILE: /home/florian/.cache/molecule/test-role/default/state.yml
MOLECULE_VERIFIER_NAME: ansible
MOLECULE_VERIFIER_TEST_DIRECTORY: /home/florian/code/test-role/molecule/default/molecule

DEBUG: SHELL REPLAY
ANSIBLE_CONFIG=/home/florian/.cache/molecule/test-role/default/ansible.cfg ANSIBLE_FILTER_PLUGINS=/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/filter:/home/florian/.cache/molecule/test-role/default/plugins/filter:/home/florian/code/test-role/plugins/filter:/home/florian/.ansible/plugins/filter:/usr/share/ansible/plugins/filter ANSIBLE_LIBRARY=/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules:/home/florian/.cache/molecule/test-role/default/library:/home/florian/code/test-role/library:/home/florian/.ansible/plugins/modules:/usr/share/ansible/plugins/modules ANSIBLE_ROLES_PATH=/home/florian/.cache/molecule/test-role/default/roles:/home/florian/code:/home/florian/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles MOLECULE_DEBUG=True MOLECULE_DEPENDENCY_NAME=galaxy MOLECULE_DRIVER_NAME=podman MOLECULE_ENV_FILE=/home/florian/code/test-role/.env.yml MOLECULE_EPHEMERAL_DIRECTORY=/home/florian/.cache/molecule/test-role/default MOLECULE_FILE=/home/florian/.cache/molecule/test-role/default/molecule.yml MOLECULE_INSTANCE_CONFIG=/home/florian/.cache/molecule/test-role/default/instance_config.yml MOLECULE_INVENTORY_FILE=/home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml MOLECULE_PROJECT_DIRECTORY=/home/florian/code/test-role MOLECULE_PROVISIONER_NAME=ansible MOLECULE_SCENARIO_DIRECTORY=/home/florian/code/test-role/molecule/default MOLECULE_SCENARIO_NAME=default MOLECULE_STATE_FILE=/home/florian/.cache/molecule/test-role/default/state.yml MOLECULE_VERIFIER_NAME=ansible MOLECULE_VERIFIER_TEST_DIRECTORY=/home/florian/code/test-role/molecule/default/molecule

DEBUG: COMMAND
/home/florian/venv/molecule/bin/ansible-playbook --skip-tags=molecule-notest,notest --diff --inventory=/home/florian/.cache/molecule/test-role/default/inventory /home/florian/code/test-role/molecule/default/converge.yml -vvv

    ansible-playbook 2.9.5
      config file = /home/florian/.cache/molecule/test-role/default/ansible.cfg
      configured module search path = ['/home/florian/venv/molecule/lib64/python3.7/site-packages/molecule/provisioner/ansible/plugins/modules', '/home/florian/.cache/molecule/test-role/default/library', '/home/florian/code/test-role/library', '/home/florian/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
      ansible python module location = /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible
      executable location = /home/florian/venv/molecule/bin/ansible-playbook
      python version = 3.7.6 (default, Jan 30 2020, 09:44:41) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]
    Using /home/florian/.cache/molecule/test-role/default/ansible.cfg as config file
    host_list declined parsing /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml as it did not pass its verify_file() method
    script declined parsing /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml as it did not pass its verify_file() method
    Parsed /home/florian/.cache/molecule/test-role/default/inventory/ansible_inventory.yml inventory source with yaml plugin

    PLAYBOOK: converge.yml *********************************************************
    1 plays in /home/florian/code/test-role/molecule/default/converge.yml

    PLAY [Converge] ****************************************************************

    TASK [Gathering Facts] *********************************************************
    task path: /home/florian/code/test-role/molecule/default/converge.yml:2
    <instance> Attempting python interpreter discovery
    <instance> RUN [b'podman', b'mount', b'instance']
    Failed to mount container instance: b'Error: cannot mount using driver overlay in rootless mode'
    <instance> RUN [b'podman', b'exec', b'instance', b'/bin/sh', b'-c', b"echo PLATFORM; uname; echo FOUND; command -v '/usr/bin/python'; command -v 'python3.7'; command -v 'python3.6'; command -v 'python3.5'; command -v 'python2.7'; command -v 'python2.6'; command -v '/usr/libexec/platform-python'; command -v '/usr/bin/python3'; command -v 'python'; echo ENDFOUND && sleep 0"]
    <instance> RUN [b'podman', b'exec', b'instance', b'/bin/sh', b'-c', b'/usr/bin/python && sleep 0']
[WARNING]: Unhandled error in Python interpreter discovery for host instance:
Expecting value: line 1 column 1 (char 0)
    Using module file /home/florian/venv/molecule/lib64/python3.7/site-packages/ansible/modules/system/setup.py
    Pipelining is enabled.
    <instance> RUN [b'podman', b'exec', b'instance', b'/bin/sh', b'-c', b'/usr/bin/python && sleep 0']
fatal: [instance]: FAILED! => {
    "ansible_facts": {},
    "changed": false,
    "failed_modules": {
        "setup": {
            "ansible_facts": {
                "discovered_interpreter_python": "/usr/bin/python"
            },
            "failed": true,
            "module_stderr": "",
            "module_stdout": "",
            "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
            "rc": 0,
            "warnings": [
                "Platform linux on host instance is using the discovered Python interpreter at /usr/bin/python, but future installation of another Python interpreter could change this. See https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html for more information."
            ]
        }
    },
    "msg": "The following modules failed to execute: setup\n"
}

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

ERROR:

Not reproducible for me with Ansible 2.10 and Podman 2.1.1
Seems like problem was in a specific molecule version.

Lets set few things right, please:

do not close bugs confirmed by multiple people for which we even had to implement workarounds like https://github.com/ansible-community/molecule/pull/2897
do no report bugs here about RPM packaging, we only support latest wheels or both driver and molecule itself, nothing else.
it there is a version of podman or specific configuration setup that is not supported, this driver must fail sanity_check() method, which is currently empty.

@sshnaidm Feel free to remove yourself from the ticket if you do not want to look into it (or if you do not have time). Being a community supported project, there are no obligations.
I can confirm that gathering facts is broken with 2.1.1(fedora-32) but seems to be working with 2.0.5(centos-8-stream) --- same molecule* versions.

Hi all,
I can confirm that this is happening with podman 2.1.1 and gather_facts enabled. Do we already know why? And is the podman team informed about this? Can I debug here something?
Thanks (also for this cool project),
David

@davidvoit it's not reproducible.
What is your OS version, ansible version, podman info --debug, and exact playbook you run?

Package from fedora 33 (podman-2.1.1-12.fc33.x86_64)
[david@quantilion hello-molecule]$ molecule converge
--> Test matrix
└── default
├── dependency
├── create
├── prepare
└── converge
--> Scenario: 'default'
--> Action: 'dependency'
Skipping, missing the requirements file.
Skipping, missing the requirements file.
--> Scenario: 'default'
--> Action: 'create'
Skipping, create action has no playbook.
--> Scenario: 'default'
--> Action: 'prepare'
Skipping, prepare playbook not configured.
--> Scenario: 'default'
--> Action: 'converge'
--> Sanity checks: 'podman'
PLAY [Converge] ****************************************************************

TASK [Gathering Facts] *********************************************************

fatal: [instance]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in "/tmp", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p "echo ~/.ansible/tmp"&& mkdir "echo ~/.ansible/tmp/ansible-tmp-1605724779.1760023-1114208-36261109272282" && echo ansible-tmp-1605724779.1760023-1114208-36261109272282="echo ~/.ansible/tmp/ansible-tmp-1605724779.1760023-1114208-36261109272282" ), exited with result 125", "unreachable": true}
PLAY RECAP *********************************************************************
instance                   : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0

ERROR:
gather_facts disabled in converge
[david@quantilion hello-molecule]$ molecule converge
--> Test matrix
└── default
├── dependency
├── create
├── prepare
└── converge
--> Scenario: 'default'
--> Action: 'dependency'
Skipping, missing the requirements file.
Skipping, missing the requirements file.
--> Scenario: 'default'
--> Action: 'create'
Skipping, instances already created.
--> Scenario: 'default'
--> Action: 'prepare'
Skipping, prepare playbook not configured.
--> Scenario: 'default'
--> Action: 'converge'
--> Sanity checks: 'podman'
PLAY [Converge] ****************************************************************

TASK [Include hello-molecule] **************************************************

TASK [hello-molecule : Molecule Hello World!] **********************************
ok: [instance] => {
    "msg": "Hello, World!"
}

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

I will upload the code (just generated with molecule on same system) to a repo

https://github.com/davidvoit/molecule_podman_gatherfacts

host:
arch: amd64
buildahVersion: 1.16.1
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.0.21-3.fc33.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.0.21, commit: 0f53fb68333bdead5fe4dc5175703e22cf9882ab'
cpus: 4
distribution:
distribution: fedora
version: "33"
eventLogger: journald
hostname: quantilion
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 2000544
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 2000544
size: 65536
kernel: 5.8.18-300.fc33.x86_64
linkmode: dynamic
memFree:<PHONE_NUMBER>
memTotal:<PHONE_NUMBER>
ociRuntime:
name: crun
package: crun-0.15.1-1.fc33.x86_64
path: /usr/bin/crun
version: |-
crun version 0.15.1
commit: eb0145e5ad4d8207e84a327248af76663d4e50dd
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
os: linux
remoteSocket:
path: /run/user/1000/podman/podman.sock
rootless: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.1.4-4.dev.giteecccdb.fc33.x86_64
version: |-
slirp4netns version 1.1.4+dev
commit: eecccdb96f587b11d7764556ffacfeaffe4b6e11
libslirp: 4.3.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.0
swapFree:<PHONE_NUMBER>
swapTotal:<PHONE_NUMBER>
uptime: 204h 56m 36.99s (Approximately 8.50 days)
registries:
search:

registry.fedoraproject.org
registry.access.redhat.com
registry.centos.org
docker.io
store:
configFile: /home/david/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.mount_program:
Executable: /usr/bin/fuse-overlayfs
Package: fuse-overlayfs-1.2.0-1.fc33.x86_64
Version: |-
fusermount3 version: 3.9.3
fuse-overlayfs: version 1.1.0
FUSE library version 3.9.3
using FUSE kernel interface version 7.31
graphRoot: /home/david/.local/share/containers/storage
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
imageStore:
number: 85
runRoot: /run/user/1000
volumePath: /home/david/.local/share/containers/storage/volumes
version:
APIVersion: 2.0.0
Built:<PHONE_NUMBER>
BuiltTime: Wed Oct  7 18:21:20 2020
GitCommit: ""
GoVersion: go1.15.2
OsArch: linux/amd64
Version: 2.1.1

@davidvoit tried it on fresh fefora 33 with your role and still not reproducible:
$ ansible-playbook --version
ansible-playbook 2.10.3
  config file = None
  configured module search path = ['/home/fedora/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/fedora/.local/lib/python3.9/site-packages/ansible
  executable location = /home/fedora/.local/bin/ansible-playbook

$ molecule --version
molecule 3.1.5
    ansible:2.10.3 python:3.9
    delegated:3.1.5 from molecule
    podman:0.3.0 from molecule_podman

$ podman version
Version:      2.1.1
API Version:  2.0.0
Go Version:   go1.15.2
Built:        Wed Oct  7 16:21:20 2020
OS/Arch:      linux/amd64

$ git clone https://github.com/davidvoit/molecule_podman_gatherfacts.git hello-molecule
$ cd hello-molecule/
$ molecule converge
--> Test matrix

└── default
    ├── dependency
    ├── create
    ├── prepare
    └── converge

--> Scenario: 'default'
--> Action: 'dependency'
Skipping, missing the requirements file.
Skipping, missing the requirements file.
--> Scenario: 'default'
--> Action: 'create'
--> Sanity checks: 'podman'

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

    TASK [Log into a container registry] *******************************************
    skipping: [localhost] => (item=None)

    TASK [Check presence of custom Dockerfiles] ************************************
    ok: [localhost] => (item=None)
    ok: [localhost]

    TASK [Create Dockerfiles from image names] *************************************
    skipping: [localhost] => (item=None)

    TASK [Discover local Podman images] ********************************************
    ok: [localhost] => (item=None)
    ok: [localhost]

    TASK [Build an Ansible compatible image] ***************************************
    skipping: [localhost] => (item={'changed': False, 'skipped': True, 'skip_reason': 'Conditional result was False', 'item': {'image': 'docker.io/pycontribs/centos:8', 'name': 'instance', 'pre_build_image': True}, 'ansible_loop_var': 'item', 'i': 0, 'ansible_index_var': 'i'})

    TASK [Determine the CMD directives] ********************************************
    ok: [localhost] => (item=None)
    ok: [localhost]

    TASK [Create molecule instance(s)] *********************************************
    changed: [localhost] => (item=None)
    changed: [localhost]

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

    PLAY RECAP *********************************************************************
    localhost                  : ok=5    changed=2    unreachable=0    failed=0    skipped=3    rescued=0    ignored=0

--> Scenario: 'default'
--> Action: 'prepare'
Skipping, prepare playbook not configured.
--> Scenario: 'default'
--> Action: 'converge'

    PLAY [Converge] ****************************************************************

    TASK [Gathering Facts] *********************************************************
[WARNING]: Unhandled error in Python interpreter discovery for host instance:
Expecting value: line 1 column 1 (char 0)
[WARNING]: Platform linux on host instance is using the discovered Python
interpreter at /usr/bin/python3.6, but future installation of another Python
interpreter could change the meaning of that path. See https://docs.ansible.com
/ansible/2.10/reference_appendices/interpreter_discovery.html for more
information.
    ok: [instance]

    TASK [Include hello-molecule] **************************************************

    TASK [hello-molecule : Molecule Hello World!] **********************************
    ok: [instance] => {
        "msg": "Hello, World!"
    }

    PLAY RECAP *********************************************************************
    instance                   : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

$ podman ps -a
CONTAINER ID  IMAGE                          COMMAND               CREATED        STATUS            PORTS   NAMES
015a80b3cc31  docker.io/pycontribs/centos:8  bash -c while tru...  6 minutes ago  Up 6 minutes ago          instance

@davidvoit when it fails, please run podman ps -a to see if you have container instance running.

@davidvoit
You can run it with more verbosity so we can see what is the failure:
ANSIBLE_VERBOSITY=5 molecule --debug converge

I think I found the error.
If a $HOME/.cache/molecule/NAME exists but no container exists, than molecule-podman expects that the container is existing, and a new converge call fails:
(venv-molecule) [david@quantilion hello-molecule]$ podman ps -a
CONTAINER ID  IMAGE   COMMAND  CREATED  STATUS  PORTS   NAMES
TASK [Gathering Facts] *********************************************************************************************************************************************************
task path: /home/david/Programmieren/ansible/hello-molecule/molecule/default/converge.yml:2
 RUN [b'podman', b'mount', b'instance']
STDOUT b''
STDERR b'Error: cannot run command "podman mount" in rootless mode, must execute podman unshare first\n'
RC CODE 125
Failed to mount container instance: b'Error: cannot run command "podman mount" in rootless mode, must execute podman unshare first'
 RUN [b'podman', b'exec', b'instance', b'/bin/sh', b'-c', b'echo ~ && sleep 0']
STDOUT b''
STDERR b'Error: no container with name or ID instance found: no such container\n'
RC CODE 125
STDOUT b'Error: no container with name or ID instance found: no such container\n' STDERR b'Error: no container with name or ID instance found: no such container\n'
 RUN [b'podman', b'exec', b'instance', b'/bin/sh', b'-c', b'echo "pwd" && sleep 0']
STDOUT b''
STDERR b'Error: no container with name or ID instance found: no such container\n'
RC CODE 125
STDOUT b'Error: no container with name or ID instance found: no such container\n' STDERR b'Error: no container with name or ID instance found: no such container\n'
 RUN [b'podman', b'exec', b'instance', b'/bin/sh', b'-c', b'( umask 77 && mkdir -p "echo ~/.ansible/tmp"&& mkdir "echo  ~/.ansible/tmp/ansible-tmp-1605971153.022807-29673-163034645906772" && echo ansible-tmp-1605971153.022807-29673-163034645906772="echo  ~/.ansible/tmp/ansible-tmp-1605971153.022807-29673-163034645906772" ) && sleep 0']
STDOUT b''
STDERR b'Error: no container with name or ID instance found: no such container\n'
RC CODE 125
STDOUT b'Error: no container with name or ID instance found: no such container\n' STDERR b'Error: no container with name or ID instance found: no such container\n'
fatal: [instance]: UNREACHABLE! => {
"changed": false,
"msg": "Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing
the remote tmp path in ansible.cfg to a path rooted in "/tmp", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p "echo ~/.ansible/tmp"&&
mkdir "echo ~/.ansible/tmp/ansible-tmp-1605971153.022807-29673-163034645906772" && echo ansible-tmp-1605971153.022807-29673-163034645906772="echo  ~/.ansible/tmp/ansible-tmp-1605971153.022807-29673-163034645906772" ), exited with result 125, stderr output: Error: no container with name or ID instance found: no such
container\n",
"unreachable": true
}
If I now remove the cache entry.
rm -rf /home/david/.cache/molecule/hello-molecule/
and rerun molecule converge
PLAY [Converge] ****************************************************************************************************************************************************************
TASK [Gathering Facts] *********************************************************************************************************************************************************
ok: [instance]
TASK [Include hello-molecule] **************************************************************************************************************************************************
TASK [hello-molecule : Molecule Hello World!] **********************************************************************************************************************************
ok: [instance] => {
"msg": "Hello, World!"
}
PLAY RECAP *********************************************************************************************************************************************************************
instance                   : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
It now works

@davidvoit thanks, now it's clear the bug is in molecule, not in podman or driver. @ssbarnea take a look and please fix it in molecule code. And close this issue finally, stop reopening it.

This is still popping up with
Fedora Silverblue 33/podman 3.0.1/molecule 3.3.0/molecule-podman 0.3.0
Also on
Ubuntu 20.04 with the same software versions.
Error message when running setup module:
  fatal: [chrony_docker]: FAILED! =>
    msg: |-
      Failed to copy file from /home/runner/.ansible/tmp/ansible-local-4617jdw2zyk6/tmpyz1zoubf to /tmp/runner/ansible/ansible-tmp-1618497822.3653443-4621-34508958919121/AnsiballZ_setup.py in container chrony_docker
      b'Error: "/tmp/runner/ansible/ansible-tmp-1618497822.3653443-4621-34508958919121/AnsiballZ_setup.py" could not be found on container chrony_docker: No such file or directory\n'

Hi,
I am moving from Travis CI to GitHub actions and I have the same problem, see:

https://github.com/fauust/ansible-role-mariadb/runs/2669297163?check_suite_focus=true#step:5:98 (runner ubuntu-latest);
https://github.com/fauust/ansible-role-mariadb/runs/2669344054?check_suite_focus=true#step:5:90 (runner ubuntu-18.04).

I am not able to reproduce this locally with:
.venv ❯ molecule --version
molecule 3.3.2 using python 3.9
    ansible:2.10.10
    delegated:3.3.2 from molecule
    podman:0.3.0 from molecule_podman

Tested on:

Debian Bullseye (podman version 3.0.1)
Debian Buster (podman version 3.0.0)

I finally found out that I have another problem with github action CI and podman, the container is just not running :)
You can verify this with (in GH action context):
podman run --systemd=always -it fauust/docker-systemd:debian-10
podman ps

Using sudo resolves the problem but I am not able to run molecule test with rootless: false...

I finally found out that I have another problem with github action CI and podman, the container is just not running :)
You can verify this with (in GH action context):
podman run --systemd=always -it fauust/docker-systemd:debian-10
podman ps

Using sudo resolves the problem but I am not able to run molecule test with rootless: false...

I'd remove this option at all not to confuse people. If need to run root container - you have to run molecule as root.

PLEASE if someone finds this issue via Google:
IF YOU HAVE ERROR WITH "Gathering Facts" WHEN USING PODMAN WITH MOLECULE - IT MEANS YOU DO NOT HAVE CONTAINER RUNNING.
There is no any issue with podman and molecule that prevents facts gathering, this issues is misleading and must be closed.

@sshnaidm That is a huge problem, we cannot ask users to run molecule as root at all. There is a big difference between being able to sudo and running as root. We should find a workaround, maybe detecting that particular case and throwing an error?
Now I am busy fixing the molecule-docker drivers which started to fall apart but once I am done I think we need to address this famous ticket. That is by far the most "popular" issue with podman driver and while it involves some user-errors it does underlines some real issues on the user experience part.
Funny bit is that I tried to run the command above to start the container interactively and I ended up having to raise another bug at https://github.com/containers/podman/issues/10469 -- still it did start the container without requiring any sudo.
I am wondering if adding an extra step to create.yml that checks that the started container is still running would be enough to address most false-positive reports. At least we will know that create failed if the container is not running at the end.

I am wondering if adding an extra step to create.yml that checks that the started container is still running would be enough to address most false-positive reports. At least we will know that create failed if the container is not running at the end.

Agree with that, above all because one expect that the container is up and running because of:
TASK [Wait for instance(s) creation to complete] *******************************

FYI, I don't want to pollute this issue with a different problem so I opened a discussion here https://github.com/ansible-community/molecule/discussions/3155. The molecule-podman driver does not seem to work with systemd containers on GitHub action ubuntu-latest runner. It works perfectly well on a fresh Ubuntu 20.04 VM (with the same podman version that GH ubuntu-latest runner use).

This bug is happening when ansible pipelining is enabled as this is not supported for podman. In fact ansible reports pipelining as enabled but fails to gather facts after.
As this option is a very common one, I am not surprised so many people encountered it, including myself. Also it can be activated from a plethora or places, so we need to find a way to detect it and to fail create.yml if detected, sparing user precious debugging hours.

Apparently the root cause is https://github.com/containers/ansible-podman-collections/blob/ba763e2988c4d3f94940695a5699f26fb94ed31f/plugins/connection/podman.py#L82 -- this should be set to False until it really supports pipelining.


Update glossary: Add self-test

Resolves #3000
#glossary_selftest

#rat_tan_hotline

Internal Tracking ID: EXPOSUREAPP-13526

I suggest also to link "self-test" in #glossary_rapid_antigen_test to the new #glossary_selftest.

I suggest also to link "self-test" in #glossary_rapid_antigen_test to the new #glossary_selftest.

Thanks for the suggestion. A link from #glossary_rapid_antigen_test to #glossary_selftest has been added in https://github.com/corona-warn-app/cwa-website/pull/3001/commits/81561b08e4f3947d5bdc221a641b6f88af785531.


[Artificial Intelligence] Building a Neural Network from scratch with Julia

Building a Neural Network from scratch with Julia
Introduction
At some basic level, Neural networks can be seen as a system which tries to take inspiration from how biological neurons share information with each other in an attempt to discover patterns within some supplied data.
This article intends to build a vanilla neural network with no AI bundle except for rather execute these numerical ideas with Julia.
Key takeaways

Initialization of parameters
Propagation Algorithms (Foward and Backward)
Optimization
Training the network

Article quality
The goal is to implement a neural network model from scratch to solve a binary classification problem rather than using
ML packages as covered in other online blogs.
References
N/A
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentations.
We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic, it has to serve value to the larger developer community at large.
An option and a great way to write this as an in-depth article and make it more add value to the greater developer community at large would be to walk the reader through the USE of methods and functions by building a unique, different, useful project.

We would love to learn your thought process behind the solution you arrived at using these concepts and topics.

That way a developer could see them in action.
As mentioned above - we believe this topic is widely covered on other blog sites.
The best way for students to build a great portfolio is by building what does not exist and what can provide the most value.


feat(pallet-ranked-collective): added types

This PR added associated types(AddOrigin & RemoveOrigin) to Config. It allows you to decouple types and areas of responsibility, since at the moment the same types are responsible for adding and promoting(removing and demoting). This will improve the flexibility of the pallet configuration.
/// The origin required to add a member.
type AddOrigin: EnsureOrigin<Self::RuntimeOrigin, Success = ()>;

/// The origin required to remove a member. The success value indicates the
/// maximum rank *from which* the removal may be.
type RemoveOrigin: EnsureOrigin<Self::RuntimeOrigin, Success = Rank>;

To achieve the backward compatibility, the users of the pallet can use the old type via the new morph:
type AddOrigin = MapSuccess<Self::PromoteOrigin, ReplaceWithDefaultFor<()>>;
type RemoveOrigin = Self::DemoteOrigin;

Polkadot companion: https://github.com/paritytech/polkadot/pull/7500

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3186587

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3186588

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3188061

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3415826

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate-macos
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3415827


Multiple tasks

How to send multiple tasks on same request?
No example has been able to demonstrate. I need to send thousands of tasks in a single request.
Currently the task is slow in synchronous mode.

Currently we do not support bulk task enqueueing. For feature requests to the underlying service, we recommend you file an issue in their public issue tracker. You can find that  https://issuetracker.google.com/issues/new?component=608118&template=0. Using multithreading could improve performance, but at this time we do not have the capability to provide an example.


NPM upgrade

Fixes #69.

npm audit

                       === npm audit security report ===

found 0 vulnerabilities
 in 14912 scanned packages


[Question] Event list not showing on initialization if current date have events.

how to show events list too if current date have events on calendar start.?
if click on current date after select another date it shows.

Hi can you add some basic code of what you are currently doing? Thanks.

i am just using sample code..
in sample code there is events for 6th of month.. if you change current date to 6 then restart app you won't see a list of events below in sample..
if you select other day and then select again it will show list.

just call  notifydatasetchanged() after adding event to list and adapter initialization.


Drop code is more powerful

Your bot is super cool, and the best of its kind.
One more feature will make it even better, i.e. let the admin start a card drop by a code.
The code setting allows dropping the code outside Discord, e.g. on YouTube/Twitch chat.
Sth. like this:
/drop-card - start a card dropping event (admin only)

Set a drop code with a time limit or maximum claims

/claim-card [drop code]

Successful` only if the code is active

Thanks for your good work.

Hey @kongkong445 glad to know this bos is useful for someone else!
Your idea looks very interesting for the concept of this bot, it is likely that I will try to make it like that:
The admin can generate code(/generate-drop-code [date/time limit] [claims limit] [cardname]) that allows users to get the opportunity of getting a random card or some specific by using claim-card [drop code].
Think parameters of generate-drop-code can be:

no options - generates code only for 1 user and gives opportunity to get 1 random card
date/time limit - parameters can be: Date format (like dd.mm.yyyy.hh.mm) or remaining Time format (like hh:mm:ss)
claims limit - count of possible uses of this code.

Im currently working on admin system of this bot, but I can't say when this update will be released for sure.
Hope it will be done soon.
Thanks for your comment and great idea ♥

I was away for a long time, for which I apologize, I saw the wishes for the bot and added new functionality for this. I will update the readme soon for a detailed description of the new features.


Ignore views that don't belong to the adapter

Thanks for publishing this, it's really helpful!
I'm not sure if it's my particular setup or not, but I'm encountering a crash when I try to use the library. I've narrowed it down to the fact that my RecyclerView often has child views that no longer belong to the adapter. I show/hide a progress bar view so I think it has something to do with that.
The crash occurs whenever the library gets a reference to a child of the RecyclerView, tries to find the adapter position of it, and then then asks the adapter for the item. My fix is to check for RecyclerView.NO_POSITION before using the value.

Thanks, I think this will fix some a lot of the IndexOutOfBounds issues people have been seeing.

Thanks!!

I'll do a release as soon as the other PR gets merged.


⚠ Samsung has degraded performance

In c42b1e2, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1906 ms

Resolved: Samsung performance has improved in 38e9c52.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/source-wg-leads lberk
/assign knative-sandbox/source-wg-leads lberk
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/eventing a574b7b...90932eb:
  > 90932eb upgrade to latest dependencies (# 5556)
bumping knative.dev/pkg dd0db4b...30f9568:
  > 30f9568 Update actions (# 2177)
  > 51cfaab Added inverse functions for the ptr package (# 2172)
  > cf1994e Update community files (# 2171)
  > 4cdacd0 add concurrency for each controller (# 2160)
  > e117baa Replace reference to obsolete xip.io service (# 2169)
  > a1bc850 Print proper warning logs from API warnings (# 2168)
  > a421cf1 upgrade to latest dependencies (# 2167)
  > 6b252df Update community files (# 2165)

/lgtm
/approve


Added boilerplate template for license & contributors

 Issue by andybs
Thursday Feb 04, 2016 at 18:03 GMT
Originally opened as https://github.ibm.com/ibmswift/Phoenix/pull/94

andybs included the following code: https://github.ibm.com/ibmswift/Phoenix/pull/94/commits

duplicate of #92

Did we add a CONTRIBUTING file? I think @triceam was going to give this to us.

not yet but #93 captures this


[Icons] Compute viewBox with iconset data (+tests)

There were a bug for icons with no individual "height" attribute.
Now it fallbacks on IconSet metada.
And i started a test class for Iconify

Thanks Simon.


Fix Kernel#initialize_copy to frozen object

I have no objection to this change, but since initialize_copy is a private method in CRuby, we should not test like a.initialize_copy(a). Probably we should call initialize_copy indirectly via clone or dup.

The comment above does not mean we need to ensure test suits to be executable by CRuby. But we may support public/private visibility in mruby in the future. So I think it's better to avoid direct invoking of methods marked as private in CRuby.

I agree with your comment. And I withdraw this PR because Kernel#initialize_copy doesn't change anything so this PR itself doesn't make much sense.
Thank you.


Scope of auto provisioning

Doc states: "Security Center collects data from your Azure virtual machines (VMs), virtual machine scale sets, IaaS containers, and non-Azure (including on-premises) computers"
Doc also states: "When automatic provisioning is on, Security Center deploys the Log Analytics agent on all supported Azure VMs and any new ones that are created."
Does that mean that automatic provisioning does NOT work for VM scale sets, IaaS containers, and non-Azure computers? The doc should make clear which compute resources are covered by automatic provisioning and which are not.

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

ID: 8267e218-3748-2820-3eee-80479705eec2
Version Independent ID: 8c6d5fce-6383-a0f8-7df3-f5e0a77bbad6
Content: Data Collection in Azure Security Center
Content Source: articles/security-center/security-center-enable-data-collection.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@jtuliani Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

It's actually pretty straightforward: Security Center does collect info from all of the resource types listed in the first sentence you quoted ("Security Center collects data from your Azure virtual machines (VMs), virtual machine scale sets, IaaS containers, and non-Azure (including on-premises) computers").
But auto-provisioning only works for Azure machines. So "When automatic provisioning is on, Security Center deploys the Log Analytics agent on all supported Azure VMs and any new ones that are created.". Meaning:

Azure virtual machines (VMs) & IaaS containers can be auto-provisioned
Virtual machine scale sets and non-Azure (including on-prem) machines require manual provisioning

Thanks for your feedback!
#please-close

Thanks for clarifying.
I would argue the doc says nothing about whether the auto-provisioning applies to VMSS, either way. The doc should be explicit that it does not apply. As written the doc requires (by your own argument) to make the inference/assumption that VMSS is not supported, simply because they're not mentioned.
What is the downside in the doc being explicit on this matter, in much the same way as your comment above?


Refund test

Codecov Report

Merging #330 (e90ca54) into main (a8d7f39) will decrease coverage by 0.5%.
The diff coverage is 0.7%.

@@           Coverage Diff           @@
##            main    #330     +/-   ##
=======================================
- Coverage   15.1%   14.7%   -0.5%
=======================================
  Files         27      27
  Lines       6628    6858    +230
=======================================
+ Hits        1004    1007      +3
- Misses      5624    5851    +227

Impacted Files
Coverage Δ

src/farcasterd/runtime.rs
0.0% <0.0%> (ø)

src/swapd/runtime.rs
0.0% <0.0%> (ø)

src/walletd/runtime.rs
0.0% <0.0%> (ø)

src/rpc/request.rs
15.9% <66.7%> (+0.1%)
:arrow_up:

src/cli/command.rs
32.7% <0.0%> (-0.9%)
:arrow_down:

src/cli/opts.rs
52.6% <0.0%> (-0.1%)
:arrow_down:

src/lib.rs
13.1% <0.0%> (-<0.1%)
:arrow_down:

Continue to review full report at Codecov.

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

tACK @ [b06fe2d](https://github.com/farcaster-project/farcaster-node/pull/330/commits/b06fe2d9a9fe8f4786b288e23f773038e966b97a)


Remove snapshot dependency

Pull Request Test Coverage Report for Build 18

2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.636%

Totals

Change from base Build 16:
0.0%

Covered Lines:
39

Relevant Lines:
44

💛  - Coveralls


Nsetm 2196 update output

Codecov Report

Merging #41 (6a2c1fa) into NSETM-2196-multiple-probability-maps (4ffd4bb) will decrease coverage by 0.05%.
The diff coverage is 96.29%.

@@                           Coverage Diff                            @@
##           NSETM-2196-multiple-probability-maps      #41      +/-   ##
========================================================================
- Coverage                                 97.79%   97.74%   -0.05%
========================================================================
  Files                                        22       22
  Lines                                      1360     1377      +17
========================================================================
+ Hits                                       1330     1346      +16
- Misses                                       30       31       +1

Flag
Coverage Δ

pytest
97.74% <96.29%> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

...ities/densities/mtype_densities_from_map/create.py
98.00% <96.29%> (-2.00%)
:arrow_down:

Output a json file with the mapping of mtype and etypes to the filename:
ex:
{
"$mtype": {
"$etype0": "data/ccfv2/test_regions_me-types/BP|bAC_densities.nrrd",
"$etype1": "data/ccfv2/test_regions_me-types/BP|bIR_densities.nrrd",
},
[...]
}

Nice! output looks like it makes sense.

@mgeplf, the usage of this output legend is to get the M and E type of a given file.
Can we reverse the dictionary?
Something like:
{
  "filename_0": ["Mtype_0", "EType_0"],
  "filename_1": ["Mtype_1", "EType_1"],
  ...
}

We could, but it's also to transform it with:
b = {f: (m, e) for m, mv in a.items() for e, f in mv.items()}
where a is the dictionary.


Packaging test

@surajpaib why'd poetry.lock change?

@ibro45 @kbressem So the concept of poetry.lock is to maintain consistent versioning across different users. If there is a poetry.lock file in the package then doing poetry install/make install will install exact versions from poetry.lock.
Adding a new dependency updates the poetry.lock as a result. I think its good practice to keep updating this file as we make changes to deps to make sure we always have the same versions


Cosmos Spark: active cached CosmosClients prevent clean Spark driver shut down

Description
Any active CosmosClient instance will prevent java apps to cleanly shut down because the Cosmos Client keeps netty-io threads which are not daemon threads around. This also prevents the Spark driver from clearly shutting down when submitting Spark jobs via jar/main instead of using notebooks. The Spark CosmosClientCache should release client instances on the driver when the SparkContext gets closed.
All SDK Contribution checklist:

[X] The pull request does not introduce [breaking changes]
[] CHANGELOG is updated for new features, bug fixes or other significant changes.
[X] I have read the contribution guidelines.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

/azp run java - cosmos - spark

/azp run java - cosmos - spark

/azp run java - cosmos - spark

/azp run java - cosmos - spark

/azp run java - cosmos - spark

/azp run java - cosmos - spark


Added AbstractCommand.getExecutionException to solve #998

Rebased #1003 against master

NetflixOSS » Hystrix » Hystrix-pull-requests #274 SUCCESS
This pull request looks good


[android] Implement distinct signal for card overflow

Probably, could be done with ordinary exception and proper exception display.

Just an exception


[BUG] onSubmitFail not called anymore on submitHandler promise rejection in v7.2.1

Hi,
Are you submitting a bug report or a feature request?
bug report
What is the current behavior?
after moving from v7.2.0 to v7.2.1 the registered onSubmitFail handler is not called anymore if submitHandler rejects the promise.
What is the expected behavior?
onSubmitFail should be called if an an async submitHandler rejects the promise.
What's your environment?
Chrome

https://github.com/erikras/redux-form/blob/master/src/handleSubmit.js#L79

@AlimovSV Yeah, that's the spot in the code that introduced this new behaviour.
In the latest change on the file, as you pointed out, error has been newly added to the boolean expression as a prerequisite for onSubmitFail being called (https://github.com/erikras/redux-form/commit/1a0660c3477024c094f1906ddab0984a386a45f0#diff-28d8f38ee02f29d2bc406450f6c0d870).
The problem is that the error in our forms do not extend SubmissionError but are of a different type so redux form as of 7.2.3 doesn't count them as error anymore :(
The docs clearly state:

onSubmitFail
A callback function that will be called when a submission fails for whatever reason. It will be called with the following parameters:
https://redux-form.com/7.2.3/docs/api/reduxform.md/#-code-onsubmitfail-function-code-optional-

So I suggest reverting the line change that was introduced in v7.2.3 (i.e. if (error && onSubmitFail) back to if (onSubmitFail)).
Regards

@erikras would you be fine with a patch that changes this behaviour back to allowing any error to be thrown in order to trigger submitFailed (as it was in pre v7.2.1)? Otherwise, this would be quite a breaking change and I don't see much of a benefit of this restriction either.

Yes, I agree this change (from https://github.com/erikras/redux-form/pull/3723) should be reverted. It doesn't seem to have been a good PR for more than one reason. Also see https://github.com/erikras/redux-form/issues/3821

@felixhayashi perhaps the test suite could be improved to cover your situation, as I agree this is a breaking change in the expected behavior around onSubmitFail

Published fix in v7.3.0.


Uncaught SyntaxError: Unexpected end of JSON input

[Enter steps to reproduce:]

...
...

Atom: 1.16.0 x64
Electron: 1.3.13
OS: Mac OS X 10.12.4
Thrown From: linter-julia package 0.7.2
Stack Trace
Uncaught SyntaxError: Unexpected end of JSON input
At file:///Applications/Atom.app/Contents/Resources/app.asar/static/index.html:1

SyntaxError: Unexpected end of JSON input
    at Object.parse (native)
    at /packages/linter-julia/lib/linter-julia.coffee:93:26)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:493:12)

Commands
     -0:26.1.0 julia-client:run-and-move (input.hidden-input)
     -0:20.7.0 editor:newline (input.hidden-input)
  3x -0:16.1.0 core:backspace (input.hidden-input)
     -0:14.2.0 julia-client:run-and-move (input.hidden-input)
     -0:12.1.0 inline:clear-current (input.hidden-input)
     -0:12.1.0 editor:consolidate-selections (input.hidden-input)
     -0:12.1.0 core:cancel (input.hidden-input)
     -0:10.9.0 inline:clear-current (input.hidden-input)
     -0:10.9.0 editor:consolidate-selections (input.hidden-input)
     -0:10.9.0 core:cancel (input.hidden-input)
     -0:10.2.0 inline:clear-current (input.hidden-input)
     -0:10.2.0 editor:consolidate-selections (input.hidden-input)
  2x -0:10.2.0 core:cancel (input.hidden-input)
  2x -0:05.7.0 core:move-right (input.hidden-input)
  2x -0:05.1.0 core:backspace (input.hidden-input)
     -0:03.6.0 autocomplete-plus:cancel (input.hidden-input)

Non-Core Packages
atom-dark-fusion-syntax 2.2.0
autocomplete-python 1.8.63
busy-signal 1.4.1
git-plus 7.8.0
Hydrogen 1.12.1
ink 0.6.5
intentions 1.1.2
julia-client 0.5.12
language-julia 0.11.0
latex-completions 0.3.2
linter 2.1.4
linter-flake8 2.2.1
linter-julia 0.7.2
linter-ui-default 1.2.4
nucleus-dark-ui 0.12.1
python-debugger 0.2.0
python-indent 1.0.2
python-tools 0.6.9
tool-bar 1.1.0
uber-juno 0.1.1

See #38. Have you installed Lint.jl?
julia> Pkg.add("Lint")

Yes, but occasionally I get that error message.

+1
Same issue here, occurs at random times. Lint.jl is installed and I've run Pkg.checkout("Lint") and using Lint at least once.

I recommend testing the master versions. It's totally rewritten and only the testing is pending to release it.

maybe this has something to do with this: https://github.com/gdkrmr/flycheck-julia/issues/1

How can we install the master version?

Pkg.checkout("Lint") will install the latest master

I assumed that the reference was to the master version of the atom linter-julia package, rather than to Lint.jl. Am I wrong?

Sorry for the late answer I have been travelling. @dpsanders is correct I meant linter-julia master version. Installing it should be as easy as copy-pasting the link to the github repo to the Atom install package search window.

Just updated my Atom package version and will let you know if the error persists. As an FYI to anyone else who updates, be aware that the latest Git version of linter-julia does not correctly inherit the Julia executable path from Juno. You need to set it manually in the options.

Tried to use linter-julia in Atom on MacOS. Initially, got the errors similarly as in #43 and #38. Followed previous discussions: uninstalled "linter-ui-default" and installed the latest master "Lint.jl" but still get the below errors:
[Linter-Julia] Server returned non-JSON response:
/Users/yifei-macpro/.atom/packages/linter-julia/lib/index.js:107
[Linter] Error running Julia Error: Error parsing server response. See console for more info
at Socket. (/Users/yifei-macpro/.atom/packages/linter-julia/lib/index.js:96:20)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:493:12)
[Linter] Error running Julia Error: Request timed out linter-registry.js [sm]:137
at /Users/yifei-macpro/.atom/packages/linter-julia/lib/index.js:80:18

I am the author of flycheck-julia which is implements Lint.jl for Emacs. After I start the server, the first couple of queries give the (probably) same error. When looking at the actual String I get back from the server, it is sometimes empty "" or contains just "[{" or an incomplete json object.

This is annoying. Updated to Julia 0.6, still have this problem on Ubuntu 16.04. Any suggestion what to try fixing it?

for emacs' flycheck-julia the problem appears the first ~20 seconds after starting the server, this is probably due to compilation, then everything works just fine. I observe the same behavior for atom so I think that this is Lint.jl issue but I do not think that it is critical.

I finally fixed the problem for flycheck-julia, the trick was to wait until the connection gets closed by the server.

Any fix for this?

It looks like since the last comment here this package has been entirely re-written in JavaScript, and I'll be pushing out a release shortly with several fixes. If you are on a version newer than v0.7.3 and still seeing this let us know!


Add config option to use current_line_blame_formatter for uncommited changes

Is your feature request related to a problem? Please describe.
Currently there isn't a way to specify the formatting of an uncommited line.  The code checks for a hardcoded string here.
Describe the solution you'd like
It would be great to have the ability to specify the format of an uncommited line. Something like below,
Ideal result:
You, 1 hour ago • Uncommited changes

Potential config option:
  current_line_blame_formatter = '      <author>, <author_time> • <summary>',
  current_line_blame_formatter_opts = {
    include_uncommited_line = true
  },

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
VSCode with the gitlens extension is a great place to reference this functionality.

I think this is a duplicate of #476 .

You, 1 hour ago • Uncommited changes

Note this isn't possible since it is impossible to know when the changes were introduced. I.e. <author_time> is unknown.

@lewis6991 I think how VSCode works is that it looks at the last time the buffer was edited.  It then uses that time for all uncommitted code.   To be fair this doesn't add that much value, mostly just a UX thing where the blame looks consistent across all lines.


Add model attribute to experimental design loop

Description of changes: Add model property to experimental design loop
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #112 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #112      +/-   ##
===========================================
+ Coverage    83.44%   83.45%   +<.01%
===========================================
  Files           83       83
  Lines         2042     2043       +1
  Branches       186      186
===========================================
+ Hits          1704     1705       +1
  Misses         297      297
  Partials        41       41

Impacted Files
Coverage Δ

...tal_design/model_based/experimental_design_loop.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


direct link churning

Nebula prefers direct links to hosts, however, in situations with asymetric routing or links with high packet loss as described in https://github.com/slackhq/nebula/issues/893 the direct link will churn forever leading to decreased throughput or even no connectivity at all.
This PR attemtps to throttle direct link churning and successfully mitigates situations with asymetric routing or links with high packet loss in conjuction with a few other settings.
In a 3-node set up (client-1, client-2, relay/lighthouse) where client-1 has either a full ip-block to client-2 or an 80% loss with iptables -A INPUT -s {client-2-pub-ip} -m statistic --mode random --probability 0.8 -j DROP
Setting the following values will lead to very quick switch to relays; with a retry of the direct link in 60s
handshakes:
  churn_limiting: true
  churn_num_failures: 1
  churn_period: 60s
timers:
  connection_alive_interval: 1
  pending_deletion_interval: 1

Any new developments on this？ Right now it conflicts with main

Any new developments on this？ Right now it conflicts with main

I have moved on to a different (private) fork with additional features. It doesn't seem like this will get merged; haven't received any feedback. If you want to use this fork, i'm happy to clean up the conflicts, just let me know.

Hi Dan, thanks for the filed issue and this PR. This isn't a scenario we've run into yet, and you seem to be the first user to report it. While I'm sure it's a legitimate scenario, we haven't had enough experience or time to think through the causes or what an ideal solution looks like. Specifically we are a bit gun shy to add additional state that looks similar to how ConnectionManager behaves to detect and stop churn.
Seeing as you've moved on to your own fork, we're going to close this for the time being.
@ExplodingDragon If you're experiencing issues, please file a new issue describing what you're seeing.


Add Splink Blog to the docs

Type of PR

[ ] BUG
[ ] FEAT
[ ] MAINT
[X] DOC

Is your Pull Request linked to an existing Issue or Pull Request?

Closed #1215
Give a brief description for the solution you have provided

Add blog to the documentation site. Primary usage will be to highlight latest features to users, but may end up being more general in future.
PR Checklist

[ ] Added documentation for changes
[ ] Added feature to example notebooks at tutorial in splink_demos (if appropriate)
[ ] Added tests (if appropriate)
[ ] Made changes based off the latest version of Splink
[ ] Run the linter

This looks great! Really like the style and think it will be a great addition.
As far as content goes, I'm not sure how far back you had in mind for this, but one thing I thought might be nice to include is the regex match/null functionality - it's quite a cool feature that can otherwise quite easily slip by unnoticed, as it is just a couple of extra function params, and this feels like a useful place to highlight

Great idea! I have made a note to add this

@ADBond I have added the EM caveat as well as the regex stuff and a few other small tweaks. Would you mind having a quick check over?
On the clerical labelling stuff - I am slightly torn. I think we should have some documentation, as you have rightly pointed out. However, I would like to get this published relatively soon as I think it will be valuable for people, and the docs will take time to write up/get reviewed properly. I'm also running out of steam on the docs front and think I need to go off and do some actual coding for a bit over the next week or so. Is it possibly worth leaving the labelling tool for the next blog when we have properly documented it? I know we probably want to get feedback on it sooner rather than later though...
@RobinL would also be keen to hear any thoughts you have on this?

@ADBond I have added the EM caveat as well as the regex stuff and a few other small tweaks. Would you mind having a quick check over?
On the clerical labelling stuff - I am slightly torn. I think we should have some documentation, as you have rightly pointed out. However, I would like to get this published relatively soon as I think it will be valuable for people, and the docs will take time to write up/get reviewed properly. I'm also running out of steam on the docs front and think I need to go off and do some actual coding for a bit over the next week or so. Is it possibly worth leaving the labelling tool for the next blog when we have properly documented it? I know we probably want to get feedback on it sooner rather than later though...
@RobinL would also be keen to hear any thoughts you have on this?

Yeah I'd probably err on the side of getting this out rather than delaying it until we write more docs, especially since there's the example that people can take a look at without actually writing any code.  It's not ideal, but if people really want to use this immediately, they can always ask a question on the discussion forum

@ADBond I have added the EM caveat as well as the regex stuff and a few other small tweaks. Would you mind having a quick check over?
On the clerical labelling stuff - I am slightly torn. I think we should have some documentation, as you have rightly pointed out. However, I would like to get this published relatively soon as I think it will be valuable for people, and the docs will take time to write up/get reviewed properly. I'm also running out of steam on the docs front and think I need to go off and do some actual coding for a bit over the next week or so. Is it possibly worth leaving the labelling tool for the next blog when we have properly documented it? I know we probably want to get feedback on it sooner rather than later though...
@RobinL would also be keen to hear any thoughts you have on this?

Yeah I'd probably err on the side of getting this out rather than delaying it until we write more docs, especially since there's the example that people can take a look at without actually writing any code. It's not ideal, but if people really want to use this immediately, they can always ask a question on the discussion forum

Ok, thanks both. I will edit to make it more obvious what state of WIP this is in. @RobinL are you happy for me to include a link to the gist you posted on the docs issue?

Yeah, totally fine to link to the gist.  Not sure, but might also be worth linking to the pr since it contains quite a lot of information about the background to the tool

Great, thanks both! I will make a minor wording edit then we are good to go.


groups selecction feature in Stops Reports

Is your feature request related to a problem? Please describe.
In the legacy version of the traccar, the "stops"  report included a valuable selection feature  "groups"  that allowed users to categorize and analyze stop data based on predefined groups. This feature was highly beneficial in identifying unusual behaviors and determining if units were staying overnight in unexpected locations.
Describe the solution you'd like
I would like to request the reintroduction of the "groups" in the "STOPS" report of the modern version. The inclusion of this feature is crucial for gaining insights into the behavior of units and identifying anomalies in their stops. This addition would greatly enhance the usability of the stops report and provide users with a powerful tool for analyzing and understanding their data.

I would love that, it's a needed feature


Project Vargant and Vagrant-AWS plugin are dead

Hi,
in my opinion the project vagrant-aws plugin is dead. Currently there are 233 issues and 25 open pull requests.
Is there someone who feels responsible for the code?

Well Vagrant isn't dead by any stretch... but yes, this project looks like it's sunsetting :(
It does still work, just! If you have an existing project, upgrade to all the latest tooling (vagrant + plugins, chef, parallels) and apply the fixes detailed in this issue thread...
https://github.com/mitchellh/vagrant-aws/issues/365
But certainly not recommended for any new projects.
It is a shame because the AWS built-in solution, OpsWorks, works out ~$15p/month for a single instance. When a micro-instance capable of running a dozen low traffic websites can cost as little as $6-7 p/month - the OpsWorks management cost kills the economics. This plugin fitted very neatly for those simple, ultra low cost use cases.

+1
I moved to use terraform.

@planesweep I believe you just nominated yourself


Bump project with workDir does not work as expected

I created a sample repo (https://github.com/florimm/SemanticRelease) that have two projects (in different folders) and Im trying to update version only for one project but when I run Versionize it updates both (I think it should only one) even if I send parameter for workingDir or even if I run from the subfolder of the project.
Am I doing something wrong ?

I just ran into this problem.
I expected that setting "--workingDir" would limit Versionize to only bump projects in that directory.
This is inconsistent behavior compared to other cli tools.

Fixed by #90


Add Banners to News Listing Page

The news listing page currently does not have any banners set to it. I believe that it would good to designate some banners specifically for it (news-themed).
I've come up with some examples:
Current

1

2

3

4

5

6

7

New banners not necessary, current banners are fine for the news page. Closing issue.


pr3: more file reorg, completed drafts of first tranche of topics under methodology

Docs Build status updates of commit 9c45e94:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

globalization/internationalization/contextual-metadata.md
:white_check_mark:Succeeded

globalization/internationalization/externalization.md
:white_check_mark:Succeeded

globalization/internationalization/externalize-resources.md
:white_check_mark:Succeeded
View

globalization/internationalization/isolate-localizable-resources.md
:white_check_mark:Succeeded

globalization/internationalization/non-localizable-text.md
:white_check_mark:Succeeded

globalization/internationalization/string-repurposing.md
:white_check_mark:Succeeded

globalization/methodology/continuous-localization.md
:white_check_mark:Succeeded
View

globalization/methodology/exit-criteria.md
:white_check_mark:Succeeded
View

globalization/methodology/index.md
:white_check_mark:Succeeded
View

globalization/methodology/international-design.md
:white_check_mark:Succeeded
View

globalization/methodology/rapid-development.md
:white_check_mark:Succeeded
View

globalization/methodology/roles-and-responsibilities.md
:white_check_mark:Succeeded
View

globalization/reference/glossary.md
:white_check_mark:Succeeded
View

globalization/reference/index.md
:white_check_mark:Succeeded
View

globalization/toc.yml
:white_check_mark:Succeeded
View

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

#sign-off

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Correctnessscore
Scorecard
Processed

globalization/internationalization/externalize-resources.md
91
75
100
link
:white_check_mark:

globalization/methodology/continuous-localization.md
92
70
100
link
:white_check_mark:

globalization/methodology/exit-criteria.md
96
76
100
link
:white_check_mark:

globalization/methodology/index.md
97
89
100
link
:white_check_mark:

globalization/methodology/international-design.md
97
90
90
link
:white_check_mark:

globalization/methodology/rapid-development.md
85
59
76
link
:white_check_mark:

globalization/methodology/roles-and-responsibilities.md
100
100
100
link
:white_check_mark:

globalization/reference/glossary.md
95
92
92
link
:white_check_mark:

globalization/reference/index.md
100
100
100
link
:white_check_mark:

globalization/toc.yml
97
87
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Correctnessscore
Scorecard
Processed

globalization/internationalization/externalize-resources.md
86
60
88
link
:white_check_mark:

globalization/methodology/continuous-localization.md
92
70
100
link
:white_check_mark:

globalization/methodology/exit-criteria.md
98
89
100
link
:white_check_mark:

globalization/methodology/index.md
97
89
100
link
:white_check_mark:

globalization/methodology/international-design.md
93
67
67
link
:white_check_mark:

globalization/methodology/rapid-development.md
85
59
76
link
:white_check_mark:

globalization/methodology/roles-and-responsibilities.md
95
81
81
link
:white_check_mark:

globalization/reference/glossary.md
95
88
88
link
:white_check_mark:

globalization/reference/index.md
100
100
100
link
:white_check_mark:

globalization/toc.yml
97
87
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit 9539aff:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

globalization/internationalization/contextual-metadata.md
:white_check_mark:Succeeded

globalization/internationalization/externalization.md
:white_check_mark:Succeeded

globalization/internationalization/externalize-resources.md
:white_check_mark:Succeeded
View

globalization/internationalization/isolate-localizable-resources.md
:white_check_mark:Succeeded

globalization/internationalization/non-localizable-text.md
:white_check_mark:Succeeded

globalization/internationalization/replaceable-text.md
:white_check_mark:Succeeded

globalization/internationalization/string-repurposing.md
:white_check_mark:Succeeded

globalization/methodology/continuous-localization.md
:white_check_mark:Succeeded
View

globalization/methodology/exit-criteria.md
:white_check_mark:Succeeded
View

globalization/methodology/index.md
:white_check_mark:Succeeded
View

globalization/methodology/international-design.md
:white_check_mark:Succeeded
View

globalization/methodology/rapid-development.md
:white_check_mark:Succeeded
View

globalization/methodology/roles-and-responsibilities.md
:white_check_mark:Succeeded
View

globalization/reference/glossary.md
:white_check_mark:Succeeded
View

globalization/reference/index.md
:white_check_mark:Succeeded
View

globalization/toc.yml
:white_check_mark:Succeeded
View

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


[mungegithub] Deployment of cherrypick from the Makefile does not work.

When we try something along the lines of:
REPO=docker.io/eparis APP=cherrypick KUBECONFIG=/path/to/kubeconfig make deploy
The image name is not updated when creating cherrypick/local.deployment.yaml.
This may be because mungegithub/cherrypick/deployment.yaml points to docker.io/eparis/cherrypick:2016-03-14-7fb1dae, instead of a gcr.io image.

Fixed in https://github.com/kubernetes/contrib/pull/1436


sudo: fix cross compilation for aarch64

See https://github.com/NixOS/nixpkgs/issues/354544

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I'd rather use the commit upstream is using to fix this than revert a commit from history (#354576).


feat(ontology): display description for default and existing props (DSP-1154)

resolves DSP-1154

The description from the default properties will be displayed as tooltipp:

@mdelez could you check the english sentences? Thanks

I suggest for "Text":
"Short text such as" instead of "Small text like"
A question concerning Date/Time: The inclusion of the new GUI element which allows for a proper display of dates with lower precision than one day - is this another PR?

I suggest for "Text":
"Short text such as" instead of "Small text like"

I will update as suggested.

A question concerning Date/Time: The inclusion of the new GUI element which allows for a proper display of dates with lower precision than one day - is this another PR?

The new gui element for dates should already be implemented. So yes, how should the description look like?

We need a kind of dd/mm/yyyy BCE/CE icon and for the short description I suggest "dd/mm/yyyy format; for historical dates"