[Snyk] Security upgrade python from 3.6 to 3.12.3

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

base/flask/1.1.1/Dockerfile

We recommend upgrading to python:3.12.3, as this image has only 205 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
  829

Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
  829

Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
  829

Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094
  829

Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094
  829

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – 99be4251-4e00-4cf1-a892-f32efea03efb
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/flask/1.1.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.4.1/cli/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//struts2/s2-007/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/solr/7.0.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/nginx/heartbleed/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//httpd/CVE-2021-41773/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/rsync/3.1.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u102/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/metabase/0.46.6/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jetty/9.4.40/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jira/8.1.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/liferay-portal/7.2.0-ga1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/rocketchat/3.12.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5-fpm/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u171/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [16](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/gitea/1.4.0/Dockerfile# L16)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/14/14.0.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/solr/8.2.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/adminer/4.6.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/apisix/1.5/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u4/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u112/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/python/2.7.7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u51/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u24/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u201/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/saltstack/3002/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u6/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u211/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [7](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/zabbix/3.0.3/server/Dockerfile# L7)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/python/python3.5/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/php5.5/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/tikiwiki/21.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/docker/18.03.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/uwsgi/php/2.0.16/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/goahead/5.1.4/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/influxdb/1.6.6/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/confluence/7.13.6/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u22/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/python/python2.7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [8](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/spring/spring-data-commons/2.0.5/Dockerfile# L8)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/kibana/6.5.4/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [11](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/dubbo/2.7.3/Dockerfile# L11)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u75/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u17/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/thinkphp/6.0.12/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/15/15/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/8.1-backdoor/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/10/10.0.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/uwsgi/python/2.0.17/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/9/9.0.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u25/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u32/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [12](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/shiro/1.2.4/Dockerfile# L12)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [11](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/fastjson/1.2.45/Dockerfile# L11)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/imagemagick/7.1.0-49/php/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/flink/1.11.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u80/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u34/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [33](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/mysql/5.5.23/Dockerfile# L33)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/nginx/1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [33](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/mysql/5.6.5/Dockerfile# L33)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/11/11.0.5/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/14/14/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/phpmyadmin/4.8.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/ecshop/4.0.6/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//rsync/common/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u21/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//struts2/s2-012/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u9/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/joomla/4.2.7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u241/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/maven/3.5.2-jdk-8/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/10/10.0.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u33/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/django/2.2.3/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [13](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/spring/spring-webflow/2.4.4/Dockerfile# L13)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/11/11.0.7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [11](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/fastjson/1.2.24/Dockerfile# L11)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.6.12-apache/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//docker/unauthorized-rce/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/electron/windows-builder/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/tomcat/tomcat8.5/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/elfinder/2.1.58/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/nginx/1.4.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [12](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/shiro/1.0.0/Dockerfile# L12)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/webmin/1.850/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/ecshop/2.7.3/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/gitlist/0.6.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/ffmpeg/3.2.4/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/httpd/2.4.43/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/11/11.0.6/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/discuzx/3.4-20170801/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u101/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.6.23-fpm/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/django/4.0.5/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/13/13.0.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/openssl/1.0.1c/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u35/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/django/1.11.4/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//ruby/CVE-2017-17405/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u45/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/struts2/s2-053/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u3/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u74/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/opentsdb/2.4.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/php5.6/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u5/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/solr/8.11.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u60/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u43/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u221/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/thinkphp/5.0.9/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/geoserver/2.22.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/apisix/2.11.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u212/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//openssh/CVE-2018-15473/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/node/9.0.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u72/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u141/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//python/unpickle/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//node/CVE-2017-14849/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u10/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/rails/5.0.7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/yapi/1.10.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/goahead/3.6.4/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/10/10/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u31/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/baselinux/centos-6/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/11/11.0.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u144/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7u67/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//nginx/CVE-2013-4547/php-fpm/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/solr/8.8.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/gitlab/8.13.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/struts2/2.5.12-rest-showcase/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/13/13.0.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/webmin/1.910/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [13](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/spring/spring-rest-data/2.6.6/Dockerfile# L13)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u23/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u72/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [11](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/apereo-cas/4.1.5/Dockerfile# L11)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/6/6u26/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/node/8.5.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/openssl/1.0.1c/with-nginx/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/struts2/2.5.25/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [9](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/xstream/1.4.15/Dockerfile# L9)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/8/8u251/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/activemq/5.13.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/7/7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/ruby/2.4.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/apisix-dashboard/2.9.0/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/oracle-java/jdk/9/9/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/openssl/1.1.1m/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/elasticsearch/1.4.4/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//struts2/s2-013/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/activemq/5.11.1/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/redis/4.0.14/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/rsync/2.6.9/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/phpmyadmin/<IP_ADDRESS>/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//httpd/CVE-2021-40438/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/rails/5.2.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/librsvg/2.50.7/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/struts2/2.3.34-showcase/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [9](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/xstream/1.4.16/Dockerfile# L9)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//phpmailer/CVE-2017-5223/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//php/xdebug-rce/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/discuzx/7.2/Dockerfile# L1)
A user should be specified in the dockerfile, otherwise the image will run as root

WORKDIR Path Not Absolute
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/activemq/5.13.2/Dockerfile# L1)
For clarity and reliability, you should always use absolute paths for your WORKDIR

WORKDIR Path Not Absolute
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/activemq/5.11.1/Dockerfile# L1)
For clarity and reliability, you should always use absolute paths for your WORKDIR

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/xxe/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.3/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/xxe/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/xxe/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.4/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.3/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.3/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [3](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/spring/spring-webflow/2.4.4/Dockerfile# L3)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.3-apache/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.3/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.4.1/apache/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.4/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/git/2.29.1/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/git/2.29.1/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.4.1/apache/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.3/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/git/2.12.2/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.3/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/git/2.29.1/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.4.1/cli/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.3-apache/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/git/2.12.2/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/git/2.12.2/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/couchdb/3.2.1/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/xxe/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.4/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/jumpserver/3.6.4/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined
/Dockerfile: [1](https://github.com/TheRedHatter/vulhub/blob/snyk-fix-e0225b921df31d491eb24ac1d6a144b7//base/php/5.4.1/cli/Dockerfile# L1)
When installing a package, its pin version should be defined

Apt Get Install Pin Version Not Defined

More results are available on AST platform


Import error when Actions, Bonus Actions or Reactions contain a size descriptor (tiny, small, meduim, etc.)

As the title says, the parser appears to get confused when it encounters terms from the list of 5e sizes, i.e., tiny, small, medium, large, huge or gargantuan in other parts of the stat block, typically in Actions, Bonus Actions and Reactions. The result is that the action in question isn't imported properly and the size, type and alignment is overwritten.
E.g., if an action contains the phrase "Large or smaller" to describe acceptable targets for the action, the size becomes "Large", the type becomes "Or" and the alignment becomes "Smaller".
It is relatively simple to work around by replacing any of these terms with some placeholder text and importing it, then manually adding the removed term(s) in the action/bonus action/reaction.
Here's an example from importing the Voiceless Talker from MCDM's Flee, Mortals!
The statblock as copy-pasted into the parser:

Voiceless Talker
Medium Aberration, Typically Lawful Evil
Armor Class 16 (natural armor)
Hit Points 91 (14d8 + 28)
Speed 30 ft., fly 30 ft.
STR DEX CON INT WIS CHA
10 (+0) 16 (+3) 14 (+2) 19 (+4) 15 (+2) 14 (+2)
Saving Throws Con +5, Int +7, Wis +5
Skills Arcana +7, Deception +5, Insight +5, Perception +5,
Persuasion +5, Stealth +6
Damage Resistances bludgeoning
Senses darkvision 120 ft., passive Perception 15
Languages Deep Speech, Undercommon, telepathy 120 ft.
Proficiency Bonus +3
ACTIONS
Multiattack. The voiceless talker manifests a power and makes
one Tentacle or Psionic Pistol attack.
Tentacle. Melee Weapon Attack: +7 to hit, reach 10 ft., one
target. Hit: 15 (2d10 + 4) psychic damage, and if the target is
Large or smaller, they are grappled (escape DC 15).
Psionic Pistol. Ranged Weapon Attack: +7 to hit, range
80/320 ft., one target. Hit: 15 (2d10 + 4) force damage.
*Memory Thief (4th-Order Power). The voiceless talker
psionically plunders the mind of a creature they can see
within 30 feet of them. The target must make a DC 15
Intelligence saving throw. On a failed save, the
target takes 22 (4d10) psychic damage, and
until they finish a long rest or die, their proficiency
bonus is cumulatively lowered by 1 and the voiceless
talker gains a cumulative +2 bonus to damage rolls.
On a successful save, a target takes half as much damage
and doesn’t have their proficiency bonus reduced.
A creature whose proficiency bonus drops to 0 can’t form
new thoughts or speak, and they have disadvantage on ability
checks, attack rolls, and saving throws.
Flay (3/Day; 5th-Order Power). The voiceless talker shoots
forth a 15-foot cone of pure psionic energy. Each creature in
the area must make a DC 15 Intelligence saving throw, taking
28 (8d6) psychic damage on a failed save, or half as much
damage on a successful one.
Guise (3rd-Order Power). The voiceless talker projects a
psionic image over their body, transforming their appearance
for 1 hour into that of a Medium creature they have seen.
When they manifest this power, they can also change the
appearance of any equipment they carry for the duration.
The changes wrought by this power fail to hold up to
physical inspection. A creature can use an action to inspect the
voiceless talker’s appearance and make a DC 15 Intelligence
(Investigation) check, noticing the image is a projection on
a success.
REACTIONS
Brain Drain. When a creature grappled by the voiceless
talker makes a saving throw against one of the voiceless talker’s
powers, the voiceless talker momentarily weakens the creature
and the creature has disadvantage on the saving throw.
CR 7

Results in the following stat block in Foundry:

I don't have much time these days to work on this, but I'm open to pull requests.

Implemented in v1.83.03


Fix: Add tus data to ecc-utils-design-form on upload

Description

Fixes #387
Checklist

[ ] My code follows the contributing guidelines of this project.
[ ] I am aware that all my commits will be squashed into a single commit, using the PR title as the commit message.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code in hard-to-understand areas.
[ ] I have updated the user-facing documentation to describe any new or changed behavior.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have not reduced the existing code coverage.

Comments

Summary by Sourcery
Fix the TUS file upload handling in the ecc-utils-design-form component to return upload data and update form state accordingly. Enhance the management of required fields and document the changes with a new changeset file.
Bug Fixes:

Fix the return value of the handleTusFileUpload function to return upload data instead of void.

Enhancements:

Update the form handling logic to store and alert field changes when TUS upload data is available.
Improve the management of required fields by updating the requiredButEmpty list based on form data presence.

Chores:

Add a changeset file to document the patch changes for the TUS upload data return feature.

hey @anuragxxd, can you please take a look at this


Random StartUp Logos

Show a random logo on startup. Use the submissions from the logo contest.

the official raspiblitz logos can now be found in /logos in this repo


'will-quit' can double trigger all listener in the host application | and why force to use app.quit ?

https://github.com/readium/r2-navigator-js/blob/d20357d964012f585e32f2f378ca3415433c3301/src/electron/main/sessions.ts#L913-L929
I don't think it's a good thing to catch event and to remove the function listener and then call the function linked to this event.
The host application should manage themself his lifecycle. The host should themself call the clearSession api.
I think r2-navigator should not be "clever".
A potential issue is to double trigger all listener in the host application. Instead the 'will-quit' event should be catch in the host app that call clearSession api from r2-navigator.
What do you think ?

I agree.
Related comments: https://github.com/readium/readium-desktop/pull/1041#issuecomment-625167842

Fixed:
https://github.com/readium/r2-navigator-js/blob/9b0c93b46e9c323fb7fc4e4eba6c0035038dbd3f/src/electron/main/sessions.ts#L914-L930

Fixed:
https://github.com/readium/r2-navigator-js/blob/9b0c93b46e9c323fb7fc4e4eba6c0035038dbd3f/src/electron/main/sessions.ts#L914-L930


Create Atom package to install, update and remove tweaks

As stated in the README, this project is no longer maintained and has been retired. Because of this, I am archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


getDeclarationErrorAddendum undefined in production.

Hi,
Thank you for the awesome library! I wouldn't be able to start my project without R3R.
Lately, I update the library and my app stopped working in production. So I took a look and found that getDeclarationErrorAddendum function is undefined. In the React3Renderer.js file, the function is defined when NODE_ENV is NOT production, but the file is in use at line 938.
https://github.com/toxicFork/react-three-renderer/commit/f23fd11d7c9b7c022b94ef64d87a0cce1a6f18f3#diff-3a1f15153809a171b437dd49a6449b6aR938

Ah, the error is not because of the undefined method. There was another error cause the code flow to that position. So I  will look for the error in my code.


[IoT] Adds IoT CLI Extension v0.24.0

Notes for this extension release can be found here:
https://github.com/Azure/azure-iot-cli-extension/releases/v0.24.0

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

IoT

This PR is still in Draft status


"EnhancmenetsAndFixes"

(SelectMethod - DragAndDrop) Exception fixes and Flags added

select method is failing in the pipeline and here's the error, please check.
I notice the you changed some logic; I thought this would the property bug only.

Whats select method added logic is doing
Its checking if we've an Element with the given text below the dropdown element itself or not "for now "
Maybe later we can enhance the logic and make it better but that's whats its actually doing its using Relative locators  to find an Element with the given text below it

@MustafaAgamy
So this error is expected and the logic is discussed with @MohabMohie? ... If you, then you can add the expected error param like this @Test(expectedExceptions = {AssertionError.class}) so it's not failing in the pipeline.

What is the TC being execute In the pipelines?

What is the scenario of the TC being executed In the pipelines?

@MustafaAgamy Check the screenshot I shared in the previous comment..You can also check the pipeline reports.

What is the TC being execute In the pipelines?

Done expected exception added
Should work now


feat: "scan" command or flag

While the underlying tooling for ESP32 and ESP8266 generally works to discover dev board ports, it would be helpful to provide a command or flag to scan from xs-dev and display a nice output.
This could start by shelling to esptool.py and parsing the output. It would be even better to find a way of scanning from NodeJS; perhaps through serialport, node-usb, or something else like the esptool-js utility (https://github.com/espressif/esptool-js).
Once pico support lands in the main branch, this command could expand to look for those boards as well.
A nice to have after scanning would be to save a discovered port to some project configuration file, something like the .env file described in another issue.

As I continue to work with esptool, I realized there might be a path toward auto-detecting the device type from the chip_id logic in that tool. This could simplify the need for the repetitive --device flag when running a project. 🤔
If this works, the default behavior for xs-dev run would be to detect the device type instead of running the platform simulator. That behavior could be replaced by a --sim flag, rather than continuing to consider the mac, win, lin, and wasm targets as "devices".
One potential issue to consider is the ability to detect / select device subsets, i.e. esp32/moddable_two. 🤷

So commands could update to xs-dev run --sim wasm instead of xs-dev run --device wasm. Or default to the OS platform without an argument: xs-dev run --sim. I think xs-dev run should still default to the OS platform simulator if no --device flag is passed.

That sounds pretty reasonable, and nicely doesn't veer far from the behaviors of mcconfig and mcrun.


2D backbone of BEVFusion-base

Hi! Congratulations on your newly submitted results on nuScenes Leaderboard!
As you mentioned in the description that you use a higher input resolution, does that mean the higher input resolution of the images? Like the one you used in ablation study, Table 4c in your paper.
I'm not so familiar with image processing but it seems that the change of input resolution will lead to the change of input channels, hence the structure of camera backbone will be changed. So did you just use a different backbone or alter the original backbone and retrained it? Could you please provide the new backbone you are using so I can better reproduce the new results?
Also, I'm a little bit confused about the sentence, "match the computation cost of concurrent work". Does it mean the updated version is more suitable for parallel computation or more compatible with other researches you're currently occupied with?
Thank you in advance.

Hi @HatakeKiki,
Thanks for your interest. Yes, we used higher input resolution, this is because the original resolution we used (704x256) is much smaller than the widely used one (800x448). As a result, the MACs of our model is in the ~250G range, while almost all other methods have at least ~500G MACs. We scale up the resolution just to match their computation budget. The backbone is not changed, it is still SwinT, the input preprocessing change we mentioned in the description has been released, you can check the commit in late September and git diff will tell you what files we changed.
Best,
Haotian

I notice that the size of the output image after ImageAug3D is still 704256 since the parameter image_size remains unchanged in the new config file. Unlike the previous config that resizes images from 1600900 to 768432 and then crops into 704256, now it resizes images into 880342 and then still crops into 704256. Is this the scale-up process you mentioned?

Our input resolution is now larger than 704x256. The computation is similar to 800x448 models. But your understanding is correct, basically we downsample to a larger size and then crop.

Closed due to inactivity.


ref: general updates to Experiments

Clarifications, corrections, etc.

Begins to address #2292
Reflects iterative/dvc/issues/5664
Misc. copy edits and fixes

Semi-related

https://github.com/iterative/dvc.org/pull/2243#pullrequestreview-603422799 (and others in that ticket)
https://github.com/iterative/dvc.org/pull/2286#discussion_r597957922 and https://github.com/iterative/dvc.org/pull/2286#discussion_r596867654

OK I guess this has grown a lot already + it's already being reviewed...

can it wait until next week?

@dberenbaum if there are contention points then sure we can postpone but otherwise this is meant as maintenance work and I think we should be able to answer any Qs regardless (but the one I had has been solved).
Checking your review now (ty btw) ⌛

@dberenbaum PTAL.
And please lmk if you think I should extract the changes to content/docs/api-reference/make_checkpoint.md to another PR (this one won't close #2292 anyway) and then we can merge everything else first. Keeping it here for now since there are valuable discussions about that ref, above.

p.p.s. actually it seems that the possible disagreements are more in exp remove as well as in --all-commits so I could extract those into another PR if you'd like (and merge make_checkpoint plus the misc. copy edits).

Looks good, @jorgeorpinel! Agree on your ideas for breaking out the PRs:

make_checkpoint.md changes can probably stay here, and more will be addressed in a future PR.
remove and gc could be extracted so that conversation about reachable commits doesn't block the rest of the PR.

Rolled back those files @dberenbaum. Pls approve so we can merge. Thanks!


Jupyter-book build and gh-pages deployment workflow

A documentation builder using jupyter-book is added in docs/ folder
GitHub workflow is added in .github/workflows/

The deployed page will look like this.
https://changgoo.github.io/grid_dendro/intro.html

This looks great! Thank you so much for adding this.


[BUG] -

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This is the second issue that you have opened where it is just filler information and no real information. Is there a real issue that you are trying to address?


Generalize the icon that RMessage presents as a UIView and not an UIImageView

Making the icon RMessage presents a UIView gives us freedom to present a UIButton, a UIImageView, and custom UIViews. This is better than the fixed type UIImageView that is expected to be an icon on the left of the RMessage title and subtitle message. We should also allow the user to dictate whether to present the icon/(custom uiview) to the left, right, top, or bottom of the the actual message.

RMessage 3.0.0 already handles this.


Remove AIR SDK requirement, standalone Flex SDK should be valid

See #1
Beware with external-library-path argument: won't work with directories when using pure Flex SDK

Actually can't remove AIR SDK requirement


Calculation method of UV direction of polygon material

  When I draw a polygon, the texture map direction is sometimes wrong, how can I confirm the UV coordinate direction so that I can calculate the correct material repeat value.
  I drew two polygons with the same parameters, but their texture direction is different:

https://sandcastle.cesium.com/index.html#c=3VVda9swFP0rwk8JpIr1LbtpGYTBBh0rbOxlHsW1tcSbbQVZaZuW/vddx85IO3vkdSMQZOncc6Src+zM1o1Hd4W5Nw5doNrco6Vpim2Fv+znJkmQ7Z+XtvZpURuXBNPzpO5+2b7amwe/dSa/tuVuZWug6fiwqX3hC9PgNM8nT0mNUJ1WJm4HCCXB2wfvtrnJfxOgTc9wX/g12hh3trENMMDM2hSrtW9QWuco2zbeVocqlFnr8qJOvWmSYNaS9zQxeuqk1oVxqcvWuxh97Wb6hW4fD0kQozNCJOVcYxYJRgTVRM+OQbsWxKWgRLWYSCslKHsBedxDaCi4irAQggOYdoDn2d90WchDHCmiJacyFIO6sCWGiWYRD4mQg7qypWFMSCp1dJIwjXSENRBSLhgb0WUa9sZoyOBgw7qEUKw51UxGnIqXwqPSLFKYUi7hNJqIkV5HHM4MF6KoosO9FoLiENjgXpQ8aPcOq7/NDqP2Hwx13fvp3d5OMQIDmh5TgYFckZbxcQjeV+nKfOhXrp0FCr+b9Ccq2sU4CTCe74fNvKu6ubIre7O0pXX4x2bVmxIhZzYm9fER/TJ14NoiremEz0g4fZ7uoW3vnruUDSaM/sMRY5pjKWEgtGJjEWtdqSKlacjFyLVLsHpISZvU05yuwG5MSU5kKNWY1du9cc4gwSNOpwSHGl4BgsjTZEOFNWNMK8nk8HEJh61BAqmMNCdjugpLzgghENRTA0YEphJeLjSC98pIpxnFCnrDCfRmrNMSLgOuhIP4f5evpO6D9Ght9dlOXsVqeo6CWbBo/K40l4f2vCmqjXUebV05gb15U23KNhrz223203icNU1L3kIX8+PSRV7coSK/GPimoqxMmwZWvm/L8lPxaJLgcjEH/B+lpU0hiquPd8aV6a6FrcnlVTeJMV7M4XG40ltb3qbuFfMv

I believe this is because the rotation is defined relative to the normal for polygons with perPositionHeight. You can set the stRotation.property on one to ensure the texture repeat matches, as in this example.

I believe this is because the rotation is defined relative to the normal for polygons with perPositionHeight. You can set the stRotation.property on one to ensure the texture repeat matches, as in this example.

Thank you for your response. How do I know when to rotate, or how can I calculate the normal for polygons with perPositionHeight.

You may not need to use perPositionHeight, unless it is necessary for another reason.
The normal is calculated internally when creating the geometry. It's possible to access, but will require some knowledge of the rendering pipeline.


self signed certificate in certificate chain

I get this error message installing with npm or yarn. Any idea?
This fix doesn't work anymore: https://coderwall.com/p/c2njkg/fix-npm-self_signed_cert_in_chain-or-cert_untrusted-errors
I have node 10.8.0 and yarn 1.9.4

Ok, this makes it work:
npm set strict-ssl false


Open Reader Authentication Failed with InoReader

I am using Vienna with my InoReader account, but the sync stopped working with an authentication failure. I can go to www.inoreader.com and log into my account without issue using my username and password.
I am using Version 3.5.5 :817110fe: (7130) on macOS 10.15.4 (Catalina).

Duplicate of #1252


owon_pct513_thermostat does not work properly in Fahrenheit

Describe the bug
The owon_pct513 thermostat does not work properly in US Units.
This probably ONLY worked in US Units in 2024.3.3. A change was made since then to support Metric.
It looks like the mappings to change the scale and step are not working as expected.
To Reproduce
Configure Home Assistant and thermostat with Metric units. Everything works as expected.
Configure Home Assistant and thermostat with US units. Initial display of thermostat reading is OK.
But can't change the setting because it is trying to scale the value between (approximately) 0 and 1.
Expected behavior
Should be able to set thermostat between 41 and 90 degF.
Additional context
Add any other context about the problem here.
If the bug involves a device, then please include device diagnostics from
Settings / Devices & Services / Tuya Local (your device) / "1 device"
Diagnostics from "Released" owon...yaml file:
tuya_local-a983993ba13b031046de86a827d1517a-Bunk Room-c1f89c7b26cdbdd96016dc6ddb44ceef (2).json
You can see from the diagnostic file the improper min and max values as well as the wrong step.
With my modified owon...yaml file:
owon_pct513_thermostat.yaml.txt
Diagnostics using MY attached owon...yaml file:
tuya_local-a983993ba13b031046de86a827d1517a-Bunk Room-c1f89c7b26cdbdd96016dc6ddb44ceef (3).json
The ramining problem is that the step is still 1/2 degF, in degF units it should be a step of 1 degF.
But the temperature is truncated to nearest 1 degF ... so it still works properly. But the user thinks they can specify 1/2 degF setting.
Please check if there are messages from Tuya Local in the Home
Assistant log (Settings / System / Logs), and include those too.
Logs is as expected considering the incorrect min, max,  and step:
File "/config/custom_components/tuya_local/helpers/device_config.py", line 939, in get_values_to_set
raise ValueError(f"{self.name} ({value}) must be between {mn} and {mx}")
ValueError: temp_f (0.5) must be between 41.0 and 90.0

If applicable, add screenshots to help explain your problem.

I think commit 4e378216c3 should fix this

I tried this file with 2024.6.0
The degF works.
When I change to degC if I change the setpoint on HA, or change the mode, it does not work.
It looks like having a mapping inside a condition that sets step and scale is not working.
See the diagnostic file:
tuya_local-a983993ba13b031046de86a827d1517a-Bunk Room-c1f89c7b26cdbdd96016dc6ddb44ceef (4).json
On an unrelated issue I submitted a request to Tuya development:
Cloud Free Support
If that is something you support and can use your voice ... please pass it on.

Thank you for testing both cases here.

The scale and step needed to be directly in the condition.  owon was the only config with them nested like this, I seem to recall going through the configs some time ago fixing this problem, so probably this one was missed or was introduced later.


Replace sox with in-memory processing

There seem to be several disadvantages to using sox for audio processing:

Requires a lot of I/O via tempfiles
Can create off-by-1 issues (cf. #73 #74)
Poor pitch shifting and time stretching quality
Unwanted warnings (cf. #75)
Clunky in terms of using Scaper as part of a pipeline (cf #3)

The above seems like sufficient motivation to consider a redesign where all audio processing is happening in memory instead of via sox. This would be a major overhaul though, so would require significant cycles.

We should start discussing how to design this a bit. One thought I had was to use the PySox API still as it's nice and modular but replace the operations within it with numpy, soundfile, and pyrubberband functionalities. This could be something we contribute to pysox, even, meaning Scaper wouldn't have to change at all?
Another option is just to write another top-level file (or expand what is already in audio.py) that would do these operations. I like the Sox API though, because the operations are tacked on to a list first and then processed all at once via build. I think staging the operations and then performing them in one swoop is a design decision that works well for Scaper. At least for development, it makes the actual changes to audio happen "all in one spot", which makes it easy to debug PRs like #55.
One other thing that will need to change is the loudness calculation in scaper.audio.r128stats, which requires FFMPEG and a subprocess call. It requires the path to the audio file as input, not a numpy array. That's a bit tricky.

#38 looks relevant.

I just found this project: https://github.com/kkroening/ffmpeg-python/, which could go a long way to making this happen. The processing would still be in tempfiles but there are two advantages:

We get a lot more augmentation capability by using ffmpeg's awesome suite of built-in tools.
We get #38 almost for free with the way that library is written. ffmpeg signal graphs are already a DAG which the library makes much more explicit.

We would have to do some work around that library to expose ffmpeg audio features a bit more easily, though. The library has some level of support for this: https://github.com/kkroening/ffmpeg-python#custom-filters. This would also require specialized installations of ffmpeg to work well, with all the extra bells and whistles (e.g. rubberband).
Finally, offline, we discussed doing most of the stuff in tempfiles but doing the combining and padding of the isolated sound events in memory instead. This would be much faster and would solve issues like #68.
I'll experiment a bit with that library to see how well it works and report back.
One more thing we need to do is isolate all of the tempfile logic in Scaper into one place, rather than having it in several places. This could be done by creating another class (EventAudio?, SingleEvent?) that wraps all of the disk I/O logic we need. Then Scaper could interact with this class instead of interacting with the tempfiles directly. This abstraction should pass all the existing test cases first to be sure it works. Then to implement the above ffmpeg changes (or other proposed changes), we could change the implementation of the class in one spot, rather than having to make changes all over the Scaper codebase.

Cheers @pseeth !
One quick comment - I don't think we should implement anything as a class unless it explicitly requires to hold state. We can probably abstract away I/O logic with simple functional wrappers, right?

I'm thinking what could require state is all of the augmentations required to do on the event. Currently we use the pysox Combiner/Transformer classes to keep track of all this and then feed the tempfile to those classes. I was thinking we would need to wrap those so that the sox operations all happen in one part of the code. I'll have to hack around a bit to see if it's necessary, though.

Sounds like something that could be represented in a simple list, no? Or some simple data structure (e.g. OrderedDict). But yeah I guess it's worth looking into.
Perhaps it would be helpful to first flesh out the full list of audio operations that Scaper currently performs and the order in which they happen, to map everything out explicitly.

Addressed by #116, #117, #118, #130, #128.


Column definition - ability to disable drag and drop for specific columns

My grid has a column that needs to be shown on the far left at all times. It's pinned, but there are other pinned columns as well. I want only this one column to have drag and drop disabled.
Let me know if a PR would be helpful.

set suppressMovable=true on the col def


wx assertions on FreeBSD

Hello world, we observe lots of assertions on startup on FreeBSD. Any hints on the cause and how to fix are welcome :-)

Most likely caused by mixing of wxEXPAND and wxALIGN flags in forms creation. Like: StaticBoxSizer1->Add(btnLoadFile, 1, wxEXPAND | wxALIGN_CENTER_HORIZONTAL | wxALIGN_CENTER_VERTICAL, 5);
The backtrace should contain the stacktrace of which UI elements cause that.
Most of the UI is generated code by wxFormBuilder, maybe it should be enough just to regenerate it with newer version of it.

Most likely caused by mixing of wxEXPAND and wxALIGN flags in forms creation. Like: StaticBoxSizer1->Add(btnLoadFile, 1, wxEXPAND | wxALIGN_CENTER_HORIZONTAL | wxALIGN_CENTER_VERTICAL, 5);
The backtrace should contain the stacktrace of which UI elements cause that.
Most of the UI is generated code by wxFormBuilder, maybe it should be enough just to regenerate it with newer version of it.

Hello @rjonaitis and thank you for feedback and hints! Below is the backtrace. Please let me know if you need additional information. It looks like wx changed api a bit between 2 and 3 and maybe its time to update sources to match 3 :-)
ASSERT INFO:
./src/common/sizer.cpp(1492): assert "!(flags & (wxALIGN_BOTTOM | wxALIGN_CENTRE_VERTICAL)) || !(flags & (wxALIGN_RIGHT | wxALIGN_CENTRE_HORIZONTAL))" failed in DoInsert(): wxEXPAND flag will be overridden by alignment flags

BACKTRACE:
[1] std::__1::char_traits<char>::length(char const*)
[2] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)
[3] std::__1::char_traits<char>::eof()
[4] wxNavigationEnabled<wxTopLevelWindow>::RemoveChild(wxWindowBase*)
[5] std::__1::char_traits<char>::eof()
[6] _ZNSt3__116allocator_traitsINS_9allocatorIdEEE20__construct_backwardIdEENS_9enable_ifIXaaooL_ZNS_17integral_constantIbLb1EE5valueEEntsr15__has_constructIS2_PT_S8_EE5valuesr31is_trivially_move_constructibleIS8_EE5valueEvE4typeERS2_S9_S9_RS9_
[7] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)
[8] void std::__1::allocator_traits<std::__1::allocator<lime::ConnectionHandle> >::__destroy<lime::ConnectionHandle>(std::__1::integral_constant<bool, true>, std::__1::allocator<lime::ConnectionHandle>&, lime::ConnectionHandle*)
[9] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)
[10] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)
[11] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)

Hello @rjonaitis and thank you for feedback and hints! Below is the backtrace. Please let me know if you need additional information. It looks like wx changed api a bit between 2 and 3 and maybe its time to update sources to match 3 :-)
ASSERT INFO:
./src/common/sizer.cpp(1492): assert "!(flags & (wxALIGN_BOTTOM | wxALIGN_CENTRE_VERTICAL)) || !(flags & (wxALIGN_RIGHT | wxALIGN_CENTRE_HORIZONTAL))" failed in DoInsert(): wxEXPAND flag will be overridden by alignment flags

BACKTRACE:
[1] std::__1::char_traits<char>::length(char const*)
[2] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)
[3] std::__1::char_traits<char>::eof()
[4] wxNavigationEnabled<wxTopLevelWindow>::RemoveChild(wxWindowBase*)
[5] std::__1::char_traits<char>::eof()
[6] _ZNSt3__116allocator_traitsINS_9allocatorIdEEE20__construct_backwardIdEENS_9enable_ifIXaaooL_ZNS_17integral_constantIbLb1EE5valueEEntsr15__has_constructIS2_PT_S8_EE5valuesr31is_trivially_move_constructibleIS8_EE5valueEvE4typeERS2_S9_S9_RS9_
[7] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)
[8] void std::__1::allocator_traits<std::__1::allocator<lime::ConnectionHandle> >::__destroy<lime::ConnectionHandle>(std::__1::integral_constant<bool, true>, std::__1::allocator<lime::ConnectionHandle>&, lime::ConnectionHandle*)
[9] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)
[10] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)
[11] void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&)

These asserts are only triggered when program is linked to debug libraries of wxWidgets. Linking to release version of wxWidgets will get rid of them.

Thank you for your time @rjonaitis :-)
Looks like we have debug enabled by default on FreeBSD packages because I am using generic packages :-)
Is this debug switch part of the LimeSuite build?
Why should not we fix the source of the assert anyway instead of just hiding them? :-)

LimeSuite is already choosing to use wxWidgets without debug, but I guess if the system provided libraries do not have that version then it fallbacks to whatever is available (or maybe the wxWidgets libraries were compiled with forced debug enabled). https://github.com/myriadrf/LimeSuite/blob/966b1076b2a03251212f062b5776226ece4bd3e8/src/CMakeLists.txt#L176
Yes, these assertions should be fixed, but it might take a while, because that requires going through basically every single UI element and modifying their flags.

Assertions and compatibility with wxWidgets 3.1.5 has been fixed.

TANK U SIR! =)

I can confirm that assertions are gone in the upstream :-) Time for a new release? :-)

ping @rjonaitis any chance for a new release? last one was almost 2 years ago and there are some important fixes in the upstream :-)

tagged new release

TANK U SIR! =)