quarchpy 2.1.24.dev3__py2.py3-none-any.whl → 2.1.24.dev5__py2.py3-none-any.whl

quarchpy/connection_specific/QPS/win-amd64/launchQPSJ21.bat

@@ -1,4 +0,0 @@
-cd..
-cd..
-cd..
-py run.py qps

quarchpy/connection_specific/jdk-j21-jres/JDK 21 JREs Notes.txt

@@ -1,93 +0,0 @@
-*** JDK 21 JREs ***
-
-J21 JREs 21.0.1_12 as of the 17th of October 2023 release.
-
-J8 used to consist of a JDK and a JRE. Later versions of Java have dropped the JRE as it is now part of the JDK.
-The problem is that if we are to ship a JRE it can be a bit bloated at ~365MB.
-
-This article describes stripping jmods and src.zip from the jdk when shipping a JRE:
-
-https://dzone.com/articles/no-more-jre-packaging-no-big-deal-1
-
-I copied Java-21 jdk from /usr/lib/jvm/ into quarch/software/j21 and deleted /jmods and src.zip and then pointed to this Java and ran QPS, and worked fine.
-Size reduction: 365MB --> 223MB.
-
-The problem is, this is a bit of the seat of the pants hacking. A much better and proper way is to use jlink as described in this article:
-
-https://adoptium.net/en-GB/blog/2021/10/jlink-to-produce-own-runtime/
-
-Copied J21 jdk to temp folder /jres and ran:
-
-./amazon-corretto-21.0.0.35.1-linux-x64/bin/jlink --add-modules ALL-MODULE-PATH --output jdk-21-jre --strip-debug --no-man-pages --no-header-files --compress=zip-6
-
-which outputs "lin-amd64-jdk-21-jre" and of size 102MB, which is 365-102=263MB smaller or 28% the size.
-
-Again, pointing QPS to this JRE works fine.
-
-He then goes on to strip out extra modules such as jpackage, jshell that are not needed for running QPS.
-Note that incubator.foreign is no longer present and also had to add jdk.unsupported.desktop since used by javafx.swing.
-The following works fine for QPS:
-
-*** Windows ***
-
-./jdk21.0.1_12/bin/jlink --add-modules  java.base,java.compiler,java.datatransfer,java.desktop,java.instrument,java.logging,java.management,java.management.rmi,java.naming,java.net.http,java.prefs,java.rmi,java.scripting,java.se,java.security.jgss,java.security.sasl,java.smartcardio,java.sql,java.sql.rowset,java.transaction.xa,java.xml,java.xml.crypto,jdk.accessibility,jdk.charsets,jdk.crypto.cryptoki,jdk.crypto.ec,jdk.dynalink,jdk.httpserver,jdk.incubator.vector,jdk.internal.vm.ci,jdk.internal.vm.compiler,jdk.internal.vm.compiler.management,jdk.jdwp.agent,jdk.jfr,jdk.jsobject,jdk.localedata,jdk.management,jdk.management.agent,jdk.management.jfr,jdk.naming.dns,jdk.naming.rmi,jdk.net,jdk.nio.mapmode,jdk.sctp,jdk.security.auth,jdk.security.jgss,jdk.unsupported,jdk.unsupported.desktop,jdk.xml.dom,jdk.zipfs --output win-amd64-jdk-21-jre --strip-debug --no-man-pages --no-header-files --compress=zip-6
-
-*** Linux ***
-
-./amazon-corretto-jdk21.0.1_12.1-linux-x64/bin/jlink --add-modules  java.base,java.compiler,java.datatransfer,java.desktop,java.instrument,java.logging,java.management,java.management.rmi,java.naming,java.net.http,java.prefs,java.rmi,java.scripting,java.se,java.security.jgss,java.security.sasl,java.smartcardio,java.sql,java.sql.rowset,java.transaction.xa,java.xml,java.xml.crypto,jdk.accessibility,jdk.charsets,jdk.crypto.cryptoki,jdk.crypto.ec,jdk.dynalink,jdk.httpserver,jdk.incubator.vector,jdk.internal.vm.ci,jdk.internal.vm.compiler,jdk.internal.vm.compiler.management,jdk.jdwp.agent,jdk.jfr,jdk.jsobject,jdk.localedata,jdk.management,jdk.management.agent,jdk.management.jfr,jdk.naming.dns,jdk.naming.rmi,jdk.net,jdk.nio.mapmode,jdk.sctp,jdk.security.auth,jdk.security.jgss,jdk.unsupported,jdk.unsupported.desktop,jdk.xml.dom,jdk.zipfs --output lin-amd64-jdk-21-jre --strip-debug --no-man-pages --no-header-files --compress=zip-6
-
-*** Apple ***
-
-/Library/Java/JavaVirtualMachines/amazon-corretto-21.jdk/Contents/Home/bin/jlink --add-modules  java.base,java.compiler,java.datatransfer,java.desktop,java.instrument,java.logging,java.management,java.management.rmi,java.naming,java.net.http,java.prefs,java.rmi,java.scripting,java.se,java.security.jgss,java.security.sasl,java.smartcardio,java.sql,java.sql.rowset,java.transaction.xa,java.xml,java.xml.crypto,jdk.accessibility,jdk.charsets,jdk.crypto.cryptoki,jdk.crypto.ec,jdk.dynalink,jdk.httpserver,jdk.incubator.vector,jdk.internal.vm.ci,jdk.internal.vm.compiler,jdk.internal.vm.compiler.management,jdk.jdwp.agent,jdk.jfr,jdk.jsobject,jdk.localedata,jdk.management,jdk.management.agent,jdk.management.jfr,jdk.naming.dns,jdk.naming.rmi,jdk.net,jdk.nio.mapmode,jdk.sctp,jdk.security.auth,jdk.security.jgss,jdk.unsupported,jdk.unsupported.desktop,jdk.xml.dom,jdk.zipfs --output mac-amd64-jdk-21-jre --strip-debug --no-man-pages --no-header-files --compress=zip-6
-
-The above Apple command is generating the reduced JRE direct from the installed version, which works equally well.
-
-This reduces the sizes down to:
-
-Windows	326MB --> 66MB
-Linux	365MB --> 81MB, ~ 20-22% of original
-Mac     353MB --> 74MB
-
-Note that this has to be done for each machine. Worth noting that jlink generates a similar ../bin structure on all three OSs even though Mac starts off with /Contents/Home/...
-
-Also, these reduced JREs can be used as the J21 runtime when packaging with jpackage since we use --runtime-image. However, for Windows found that it reduces the 
-final packaged .msi down from 130MB to 109MB and so looks like jpackage may already be doing some stripping out of non-relevant JDK features.
-
-*** Copying ***
-
-Note that when copying the stripped down JDK on Linux/Apple, a simple copy will strip out legal licenses as they are symbolic links and so best to do the following,
-where L stands for de-reference and follow the symbol link, and R stands for recurse directory:
-
-Linux:
-cp -r -L lin-amd64-jdk-21-jre/ full_copy
-
-Mac:
-cp -LR mac-amd64-jdk-21-jre/ full_copy
-
-Also advisable to download the zipped up versions of the Corretto JDKs and work with these as opposed to copying folders from .deb/.dmg packagers.
-
-*** Permissions ***
-
-Noticed that when the Linux JRE was built and moved into the jres folder of QuarchPy that it wouldn't run and remained in the is-qis-running while loop due to a 
-permissions error. So, after running the above commands ensure to do a full rights chmod, where -R performs a recursive trace on all sub-folders and files:
-
-chmod -R 777 ./full_copy 
-
-Found that this isn't bullet proof and so added a subprocess() chmod call in the QuarchPy code specifically for Linux/Apple.
-
-*** SVN ***
-
-1) Found that if a blanket upload of the Linux JRE is committed to SVN that it doesn't like the .so lib files and excludes them from the commit.
-Ensure they are explicitly added.
-
-2) Apple is dumping its own hidden folder vieiwng attribute files .DS_Store into the directories. They shouldn't affect QuarchPy in any way but shouldn't be there
-and need to ensure they are removed.
-
-*** release File ***
-
-After the stripped down JREs have been built, a "release" file is deposited in the jre directory and is of the form:
-
-JAVA_VERSION="21.0.1"
-MODULES="java.base java.compiler ...
-
-showing the Java version and modules. This is useful as a double-check that things look correct.

quarchpy/connection_specific/jdk-j21-jres/lin-amd64-jdk-21-jre/conf/jaxp.properties

@@ -1,180 +0,0 @@
-################################################################################
-#           JAXP Configuration File
-#
-# jaxp.properties (this file) is the default configuration file for JAXP, the API
-# defined in the java.xml module. It is in java.util.Properties format and typically
-# located in the {java.home}/conf directory. It may contain key/value pairs for
-# specifying the implementation classes of JAXP factories and/or properties
-# that have corresponding system properties.
-#
-# A user-specified configuration file can be set up using the system property
-# java.xml.config.file to override any or all of the entries in jaxp.properties.
-# The following statement provides myConfigurationFile as a custom configuration
-# file:
-#     java -Djava.xml.config.file=myConfigurationFile
-################################################################################
-
-# ---- JAXP Default Configuration ----
-#
-# The JAXP default configuration (jaxp.properties) contains entries for the
-# Factory Lookup Mechanism and properties with corresponding system properties.
-# The values are generally set to the default values of the properties.
-#
-#
-# JAXP Lookup Mechanism:
-#
-# The JAXP configuration file ranks 2nd to the System Property in the precedent
-# order of the JAXP Lookup Mechanism. When the System Property is not specified,
-# a JAXP factory reads the configuration file in order to locate an implementation
-# class. If found, the class specified will be used as the factory implementation
-# class.
-#
-# The format of an entry is key=value where the key is the fully qualified name
-# of the factory and value that of the implementation class. The following entry
-# set a DocumentBuilderFactory implementation class:
-#
-# javax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-#
-#
-# Java SE and JDK Implementation Specific Properties:
-#
-# The JAXP configuration file ranks above the default settings in the Property
-# Precedence in that its entries will override the default values of the corresponding
-# properties.
-#
-# All properties that have System Properties defined in Java SE or supported
-# by the JDK Implementation can be placed in the configuration file to override
-# the default property values. The format is:
-#     system-property-name=value
-#
-# For example, the FILES property in CatalogFeatures has an associated system
-# property called javax.xml.catalog.files. An entry for the FILES property in the
-# configuration file would therefore use javax.xml.catalog.files as the key, that
-# is:
-#     javax.xml.catalog.files=strict
-#
-#
-# Extension Functions:
-#
-# This property determines whether XSLT and XPath extension functions are allowed.
-# The value type is boolean and the default value is true (allowing
-# extension functions). The following entry would override the default value and
-# disallow extension functions:
-#
-# jdk.xml.enableExtensionFunctions=false
-#
-#
-# Overriding the default parser:
-#
-# This property allows using a third party implementation to override the default
-# parser provided by the JDK. The value type is boolean and the default value is
-# false, disallowing overriding the default parser. The setting below reflects
-# the default property setting:
-#
-jdk.xml.overrideDefaultParser=false
-#
-#
-# External Access Properties:
-#
-# The External Access Properties are defined in javax.xml.XMLConstants. Their
-# system properties are javax.xml.accessExternalDTD, javax.xml.accessExternalSchema,
-# and javax.xml.accessExternalStylesheet. The values are a list of protocols separated
-# by comma, plus empty string ("") to represent no protocol allowed and the key
-# word "all" for all access. The default is "all", allowing all external resources
-# to be fetched. The followings are example of external access settings:
-#
-# allow local (file) DTDs to be retrieved
-# javax.xml.accessExternalDTD=file
-#
-# allow local (file) and remote (http) external schemas
-# javax.xml.accessExternalSchema=file, http
-#
-# reject any external stylesheets
-# javax.xml.accessExternalStylesheet=""
-#
-# allow all external stylesheets
-# javax.xml.accessExternalStylesheet="all"
-#
-#
-# Catalog Properties:
-#
-# The Catalog API defines four features: FILES, PREFER, DEFER and RESOLVE.
-# Except PREFER, all other properties can be placed in the configuration file
-# using the system properties defined for them.
-#
-# FILES: A semicolon-delimited list of URIs to locate the catalog files. The URIs
-# must be absolute and have a URL protocol handler for the URI scheme. The following
-# is an example of setting up a catalog file:
-#
-# javax.xml.catalog.files = file:///users/auser/catalog/catalog.xml
-#
-# DEFER: Indicates that the alternative catalogs including those specified in
-# delegate entries or nextCatalog are not read until they are needed. The value
-# is a boolean and the default value is true.
-#
-# javax.xml.catalog.defer=true
-#
-# RESOLVE: Determines the action if there is no matching entry found after all of
-# the specified catalogs are exhausted. The values are key words: strict, continue,
-# and ignore. The default is strict. The following setting reflects the default
-# setting.
-#
-# javax.xml.catalog.resolve=strict
-#
-#
-# useCatalog:
-# This property instructs XML processors to use XML Catalogs to resolve entity
-# references. The value is a boolean and the default value is true.
-#
-# javax.xml.useCatalog=true
-#
-#
-# Implementation Specific Properties - Limits
-#
-# Limits have a value type Integer. The values must be positive integers. Zero
-# means no limit.
-#
-# Limits the number of entity expansions. The default value is 64000
-# jdk.xml.entityExpansionLimit=64000
-#
-# Limits the total size of all entities that include general and parameter entities.
-# The size is calculated as an aggregation of all entities. The default value is 5x10^7.
-# jdk.xml.totalEntitySizeLimit=5E7
-#
-# Limits the maximum size of any general entities. The default value is 0.
-# jdk.xml.maxGeneralEntitySizeLimit=0
-#
-# Limits the maximum size of any parameter entities, including the result of
-# nesting multiple parameter entities. The default value is 10^6.
-# jdk.xml.maxParameterEntitySizeLimit=1E6
-#
-# Limits the total number of nodes in all entity references. The default value is 3x10^6.
-# jdk.xml.entityReplacementLimit=3E6
-#
-# Limits the number of attributes an element can have. The default value is 10000.
-# jdk.xml.elementAttributeLimit=10000
-#
-# Limits the number of content model nodes that may be created when building a
-# grammar for a W3C XML Schema that contains maxOccurs attributes with values
-# other than "unbounded". The default value is 5000.
-# jdk.xml.maxOccurLimit=5000
-#
-# Limits the maximum element depth. The default value is 0.
-# jdk.xml.maxElementDepth=0
-#
-# Limits the maximum size of XML names, including element name, attribute name
-# and namespace prefix and URI. The default value is 1000.
-jdk.xml.maxXMLNameLimit=1000
-#
-#
-# XPath Limits
-#
-# Limits the number of groups an XPath expression can contain. The default value is 10.
-jdk.xml.xpathExprGrpLimit=10
-#
-# Limits the number of operators an XPath expression can contain. The default value is 100.
-jdk.xml.xpathExprOpLimit=100
-#
-# Limits the total number of XPath operators in an XSL Stylesheet. The default value is 10000.
-jdk.xml.xpathTotalOpLimit=10000
-

quarchpy/connection_specific/jdk-j21-jres/lin-amd64-jdk-21-jre/conf/logging.properties

@@ -1,63 +0,0 @@
-############################################################
-#  	Default Logging Configuration File
-#
-# You can use a different file by specifying a filename
-# with the java.util.logging.config.file system property.
-# For example, java -Djava.util.logging.config.file=myfile
-############################################################
-
-############################################################
-#  	Global properties
-############################################################
-
-# "handlers" specifies a comma-separated list of log Handler
-# classes.  These handlers will be installed during VM startup.
-# Note that these classes must be on the system classpath.
-# By default we only configure a ConsoleHandler, which will only
-# show messages at the INFO and above levels.
-handlers= java.util.logging.ConsoleHandler
-
-# To also add the FileHandler, use the following line instead.
-#handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler
-
-# Default global logging level.
-# This specifies which kinds of events are logged across
-# all loggers.  For any given facility this global level
-# can be overridden by a facility-specific level
-# Note that the ConsoleHandler also has a separate level
-# setting to limit messages printed to the console.
-.level= INFO
-
-############################################################
-# Handler specific properties.
-# Describes specific configuration info for Handlers.
-############################################################
-
-# default file output is in user's home directory.
-java.util.logging.FileHandler.pattern = %h/java%u.log
-java.util.logging.FileHandler.limit = 50000
-java.util.logging.FileHandler.count = 1
-# Default number of locks FileHandler can obtain synchronously.
-# This specifies maximum number of attempts to obtain lock file by FileHandler
-# implemented by incrementing the unique field %u as per FileHandler API documentation.
-java.util.logging.FileHandler.maxLocks = 100
-java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter
-
-# Limit the messages that are printed on the console to INFO and above.
-java.util.logging.ConsoleHandler.level = INFO
-java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
-
-# Example to customize the SimpleFormatter output format
-# to print one-line log message like this:
-#     <level>: <log message> [<date/time>]
-#
-# java.util.logging.SimpleFormatter.format=%4$s: %5$s [%1$tc]%n
-
-############################################################
-# Facility-specific properties.
-# Provides extra control for each logger.
-############################################################
-
-# For example, set the com.xyz.foo logger to only log SEVERE
-# messages:
-# com.xyz.foo.level = SEVERE

quarchpy/connection_specific/jdk-j21-jres/lin-amd64-jdk-21-jre/conf/management/jmxremote.access

@@ -1,79 +0,0 @@
-######################################################################
-#     Default Access Control File for Remote JMX(TM) Monitoring
-######################################################################
-#
-# Access control file for Remote JMX API access to monitoring.
-# This file defines the allowed access for different roles.  The
-# password file (jmxremote.password by default) defines the roles and their
-# passwords.  To be functional, a role must have an entry in
-# both the password and the access files.
-#
-# The default location of this file is $JRE/conf/management/jmxremote.access
-# You can specify an alternate location by specifying a property in
-# the management config file $JRE/conf/management/management.properties
-# (See that file for details)
-#
-# The file format for password and access files is syntactically the same
-# as the Properties file format.  The syntax is described in the Javadoc
-# for java.util.Properties.load.
-# A typical access file has multiple lines, where each line is blank,
-# a comment (like this one), or an access control entry.
-#
-# An access control entry consists of a role name, and an
-# associated access level.  The role name is any string that does not
-# itself contain spaces or tabs.  It corresponds to an entry in the
-# password file (jmxremote.password).  The access level is one of the
-# following:
-#       "readonly" grants access to read attributes of MBeans.
-#                   For monitoring, this means that a remote client in this
-#                   role can read measurements but cannot perform any action
-#                   that changes the environment of the running program.
-#       "readwrite" grants access to read and write attributes of MBeans,
-#                   to invoke operations on them, and optionally
-#                   to create or remove them. This access should be granted
-#                   only to trusted clients, since they can potentially
-#                   interfere with the smooth operation of a running program.
-#
-# The "readwrite" access level can optionally be followed by the "create" and/or
-# "unregister" keywords.  The "unregister" keyword grants access to unregister
-# (delete) MBeans.  The "create" keyword grants access to create MBeans of a
-# particular class or of any class matching a particular pattern.  Access
-# should only be granted to create MBeans of known and trusted classes.
-#
-# For example, the following entry would grant readwrite access
-# to "controlRole", as well as access to create MBeans of the class
-# javax.management.monitor.CounterMonitor and to unregister any MBean:
-#  controlRole readwrite \
-#              create javax.management.monitor.CounterMonitorMBean \
-#              unregister
-# or equivalently:
-#  controlRole readwrite unregister create javax.management.monitor.CounterMBean
-#
-# The following entry would grant readwrite access as well as access to create
-# MBeans of any class in the packages javax.management.monitor and
-# javax.management.timer:
-#  controlRole readwrite \
-#              create javax.management.monitor.*,javax.management.timer.* \
-#              unregister
-#
-# The \ character is defined in the Properties file syntax to allow continuation
-# lines as shown here.  A * in a class pattern matches a sequence of characters
-# other than dot (.), so javax.management.monitor.* matches
-# javax.management.monitor.CounterMonitor but not
-# javax.management.monitor.foo.Bar.
-#
-# A given role should have at most one entry in this file.  If a role
-# has no entry, it has no access.
-# If multiple entries are found for the same role name, then the last
-# access entry is used.
-#
-#
-# Default access control entries:
-# o The "monitorRole" role has readonly access.
-# o The "controlRole" role has readwrite access and can create the standard
-#   Timer and Monitor MBeans defined by the JMX API.
-
-monitorRole   readonly
-controlRole   readwrite \
-              create javax.management.monitor.*,javax.management.timer.* \
-              unregister