Kong will not start after upgrade to 0.10.1: ssl plugin is in use but not enabled

Summary
After upgrading from 0.9.2 to 0.10.1, kong fails to start
Steps To Reproduce

Create 0.10.1 node based off of official 0.10.1 Dockerfile, but change CMD directive to ["/bin/sleep", "infinity"] so that kong does not connect to a database
Run aforementioned docker container and connect via bash
On the node, set up a configuration file that points to a database used by a kong cluster v0.9.2. (mine is populated with several proxy apis, consumers, and plugins)
kong migrations up -c <the previously created config file>
kong start -c <the previously created config file> -vv

Result:
2017/04/25 01:34:10 [verbose] could not start Kong, stopping services
Error:
/usr/local/share/lua/5.1/kong/cmd/start.lua:34: /usr/local/share/lua/5.1/kong/cmd/start.lua:23: nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/kong.lua:138: ssl plugin is in use but not enabled
stack traceback:
	[C]: in function 'assert'
	/usr/local/share/lua/5.1/kong.lua:138: in function 'init'
	init_by_lua:4: in main chunk

stack traceback:
	[C]: in function 'error'
	/usr/local/share/lua/5.1/kong/cmd/start.lua:34: in function 'cmd_exec'
	/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:88>
	[C]: in function 'xpcall'
	/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:45>
	/usr/local/bin/kong:5: in function 'file_gen'
	init_worker_by_lua:40: in function <init_worker_by_lua:38>
	[C]: in function 'pcall'
	init_worker_by_lua:47: in function <init_worker_by_lua:45>

Additional Details & Logs

Kong version: 0.9.2 -> 0.10.1
Kong migration logs:

[root@upgrade-kong kong]# kong migrations up -c /etc/kong/upgrade-kong.conf
migrating core for database kong
core migrated up to: 2016-09-05-212515_retries
core migrated up to: 2016-09-16-141423_upstreams
core migrated up to: 2016-12-14-172100_move_ssl_certs_to_core
core migrated up to: 2016-11-11-151900_new_apis_router_1
core migrated up to: 2016-11-11-151900_new_apis_router_2
core migrated up to: 2016-11-11-151900_new_apis_router_3
core migrated up to: 2016-01-25-103600_unique_custom_id
core migrated up to: 2017-01-24-132600_upstream_timeouts
core migrated up to: 2017-01-24-132600_upstream_timeouts_2
migrating cors for database kong
cors migrated up to: 2017-03-14_multiple_orgins
migrating oauth2 for database kong
oauth2 migrated up to: 2016-12-22-283949_serialize_redirect_uri
oauth2 migrated up to: 2016-09-19-oauth2_api_id
oauth2 migrated up to: 2016-12-15-set_global_credentials
migrating basic-auth for database kong
basic-auth migrated up to: 2017-01-25-180400_unique_username
14 migrations ran

Kong debug-level startup logs:

[root@upgrade-kong bin]# kong start -c /etc/kong/upgrade-kong.conf -vv
2017/04/25 01:34:08 [verbose] Kong: 0.10.1
2017/04/25 01:34:08 [debug] ngx_lua: 10007
2017/04/25 01:34:08 [debug] nginx: 1011002
2017/04/25 01:34:08 [debug] Lua: LuaJIT 2.1.0-beta2
2017/04/25 01:34:08 [verbose] reading config file at /etc/kong/upgrade-kong.conf
2017/04/25 01:34:08 [debug] KONG_PG_PASSWORD ENV found with "******"
2017/04/25 01:34:08 [debug] KONG_LOG_LEVEL ENV found with "debug"
2017/04/25 01:34:08 [debug] KONG_PG_DATABASE ENV found with "kong"
2017/04/25 01:34:08 [debug] KONG_PG_HOST ENV found with "******"
2017/04/25 01:34:08 [debug] KONG_PG_USER ENV found with "kong"
2017/04/25 01:34:08 [debug] KONG_DATABASE ENV found with "postgres"
2017/04/25 01:34:08 [debug] admin_listen = "<IP_ADDRESS>:8001"
2017/04/25 01:34:08 [debug] admin_listen_ssl = "<IP_ADDRESS>:8444"
2017/04/25 01:34:08 [debug] admin_ssl = true
2017/04/25 01:34:08 [debug] anonymous_reports = true
2017/04/25 01:34:08 [debug] cassandra_consistency = "ONE"
2017/04/25 01:34:08 [debug] cassandra_contact_points = {"<IP_ADDRESS>"}
2017/04/25 01:34:08 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
2017/04/25 01:34:08 [debug] cassandra_keyspace = "kong"
2017/04/25 01:34:08 [debug] cassandra_lb_policy = "RoundRobin"
2017/04/25 01:34:08 [debug] cassandra_port = 9042
2017/04/25 01:34:08 [debug] cassandra_repl_factor = 1
2017/04/25 01:34:08 [debug] cassandra_repl_strategy = "SimpleStrategy"
2017/04/25 01:34:08 [debug] cassandra_ssl = false
2017/04/25 01:34:08 [debug] cassandra_ssl_verify = false
2017/04/25 01:34:08 [debug] cassandra_timeout = 5000
2017/04/25 01:34:08 [debug] cassandra_username = "kong"
2017/04/25 01:34:08 [debug] cluster_listen = "<IP_ADDRESS>:7946"
2017/04/25 01:34:08 [debug] cluster_listen_rpc = "<IP_ADDRESS>:7373"
2017/04/25 01:34:08 [debug] cluster_profile = "wan"
2017/04/25 01:34:08 [debug] cluster_ttl_on_failure = 3600
2017/04/25 01:34:08 [debug] custom_plugins = {}
2017/04/25 01:34:08 [debug] database = "postgres"
2017/04/25 01:34:08 [debug] dns_hostsfile = "/etc/hosts"
2017/04/25 01:34:08 [debug] dns_resolver = {}
2017/04/25 01:34:08 [debug] log_level = "debug"
2017/04/25 01:34:08 [debug] lua_code_cache = "on"
2017/04/25 01:34:08 [debug] lua_package_cpath = ""
2017/04/25 01:34:08 [debug] lua_package_path = "?/init.lua;./kong/?.lua"
2017/04/25 01:34:08 [debug] lua_socket_pool_size = 30
2017/04/25 01:34:08 [debug] lua_ssl_trusted_certificate = "/etc/ssl/certs/rds-combined-ca-bundle.pem"
2017/04/25 01:34:08 [debug] lua_ssl_verify_depth = 20
2017/04/25 01:34:08 [debug] mem_cache_size = "128m"
2017/04/25 01:34:08 [debug] nginx_daemon = "on"
2017/04/25 01:34:08 [debug] nginx_optimizations = true
2017/04/25 01:34:08 [debug] nginx_worker_processes = "auto"
2017/04/25 01:34:08 [debug] pg_database = "kong"
2017/04/25 01:34:08 [debug] pg_host = "******"
2017/04/25 01:34:08 [debug] pg_password = "******"
2017/04/25 01:34:08 [debug] pg_port = 5432
2017/04/25 01:34:08 [debug] pg_ssl = true
2017/04/25 01:34:08 [debug] pg_ssl_verify = true
2017/04/25 01:34:08 [debug] pg_user = "kong"
2017/04/25 01:34:08 [debug] prefix = "/usr/local/kong/"
2017/04/25 01:34:08 [debug] proxy_listen = "<IP_ADDRESS>:8000"
2017/04/25 01:34:08 [debug] proxy_listen_ssl = "<IP_ADDRESS>:8443"
2017/04/25 01:34:08 [debug] serf_path = "serf"
2017/04/25 01:34:08 [debug] ssl = true
2017/04/25 01:34:08 [debug] upstream_keepalive = 60
2017/04/25 01:34:08 [verbose] prefix in use: /usr/local/kong
2017/04/25 01:34:08 [verbose] preparing nginx prefix directory at /usr/local/kong
2017/04/25 01:34:08 [verbose] saving serf identifier to /usr/local/kong/serf/serf.id
2017/04/25 01:34:08 [debug] searching for OpenResty 'resty' executable
2017/04/25 01:34:08 [debug] /usr/local/openresty/bin/resty -V: 'nginx version: openresty/<IP_ADDRESS>'
2017/04/25 01:34:08 [debug] found OpenResty 'resty' executable at /usr/local/openresty/bin/resty
2017/04/25 01:34:08 [verbose] saving serf shell script handler to /usr/local/kong/serf/serf_event.sh
2017/04/25 01:34:08 [verbose] SSL enabled, no custom certificate set: using default certificate
2017/04/25 01:34:08 [verbose] generating default SSL certificate and key
2017/04/25 01:34:09 [verbose] Admin SSL enabled, no custom certificate set: using default certificate
2017/04/25 01:34:09 [verbose] generating admin SSL certificate and key
2017/04/25 01:34:09 [verbose] running datastore migrations
2017/04/25 01:34:09 [verbose] migrations up to date
2017/04/25 01:34:09 [verbose] serf agent not running, deleting /usr/local/kong/pids/serf.pid
2017/04/25 01:34:09 [debug] searching for 'serf' executable
2017/04/25 01:34:09 [debug] serf version: 'Serf v0.7.0'
2017/04/25 01:34:09 [debug] found 'serf' executable at serf
2017/04/25 01:34:09 [debug] starting serf agent: nohup serf agent -profile 'wan' -bind '<IP_ADDRESS>:7946' -log-level 'err' -rpc-addr '<IP_ADDRESS>:7373' -event-handler 'member-join,member-leave,member-failed,member-update,member-reap,user:kong=/usr/local/kong/serf/serf_event.sh' -node '******_<IP_ADDRESS>:7946_03dc2d80b6dc4c5a95b5305f0cfdc1dc' > /usr/local/kong/logs/serf.log 2>&1 & echo $! > /usr/local/kong/pids/serf.pid
2017/04/25 01:34:09 [verbose] waiting for serf agent to be running
2017/04/25 01:34:09 [debug] sending signal to pid at: /usr/local/kong/pids/serf.pid
2017/04/25 01:34:09 [debug] kill -0 `cat /usr/local/kong/pids/serf.pid` >/dev/null 2>&1
2017/04/25 01:34:09 [verbose] serf agent started
2017/04/25 01:34:09 [verbose] auto-joining serf cluster
2017/04/25 01:34:09 [verbose] no other nodes found in the cluster
2017/04/25 01:34:09 [verbose] registering serf node in datastore
2017/04/25 01:34:09 [verbose] cluster joined and node registered in datastore
2017/04/25 01:34:09 [debug] searching for OpenResty 'nginx' executable
2017/04/25 01:34:09 [debug] /usr/local/openresty/nginx/sbin/nginx -v: 'nginx version: openresty/<IP_ADDRESS>'
2017/04/25 01:34:09 [debug] found OpenResty 'nginx' executable at /usr/local/openresty/nginx/sbin/nginx
2017/04/25 01:34:09 [debug] starting nginx: /usr/local/openresty/nginx/sbin/nginx -p /usr/local/kong -c nginx.conf
2017/04/25 01:34:10 [verbose] could not start Kong, stopping services
2017/04/25 01:34:10 [verbose] leaving serf cluster
2017/04/25 01:34:10 [verbose] left serf cluster
2017/04/25 01:34:10 [verbose] stopping serf agent at /usr/local/kong/pids/serf.pid
2017/04/25 01:34:10 [debug] sending signal to pid at: /usr/local/kong/pids/serf.pid
2017/04/25 01:34:10 [debug] kill -15 `cat /usr/local/kong/pids/serf.pid` >/dev/null 2>&1
2017/04/25 01:34:10 [verbose] serf agent stopped
2017/04/25 01:34:10 [verbose] stopped services
Error:
/usr/local/share/lua/5.1/kong/cmd/start.lua:34: /usr/local/share/lua/5.1/kong/cmd/start.lua:23: nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/kong.lua:138: ssl plugin is in use but not enabled
stack traceback:
	[C]: in function 'assert'
	/usr/local/share/lua/5.1/kong.lua:138: in function 'init'
	init_by_lua:4: in main chunk

stack traceback:
	[C]: in function 'error'
	/usr/local/share/lua/5.1/kong/cmd/start.lua:34: in function 'cmd_exec'
	/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:88>
	[C]: in function 'xpcall'
	/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:45>
	/usr/local/bin/kong:5: in function 'file_gen'
	init_worker_by_lua:40: in function <init_worker_by_lua:38>
	[C]: in function 'pcall'
	init_worker_by_lua:47: in function <init_worker_by_lua:45>

Kong error logs

[root@upgrade-kong logs]# cat error.log
2017/04/25 01:34:09 [debug] 98#0: [lua] globalpatches.lua:9: installing the globalpatches
2017/04/25 01:34:09 [debug] 98#0: [lua] kong.lua:57: load_plugins(): Discovering used plugins
2017/04/25 01:34:09 [error] 98#0: init_by_lua error: /usr/local/share/lua/5.1/kong.lua:138: ssl plugin is in use but not enabled
stack traceback:
	[C]: in function 'assert'
	/usr/local/share/lua/5.1/kong.lua:138: in function 'init'
	init_by_lua:4: in main chunk

Kong configuration File (All defaults except database and lua_ssl_trusted_certificate):

# -----------------------
# Kong configuration file
# -----------------------
#
# The commented-out settings shown in this file represent the default values.
#
# This file is read when `kong start` or `kong compile` are used. Kong
# generates the Nginx configuration with the settings specified in this file.
#
# All environment variables prefixed with `KONG_` and capitalized will override
# the settings specified in this file.
# Example:
#   `log_level` setting -> `KONG_LOG_LEVEL` env variable
#
# Boolean values can be specified as `on`/`off` or `true`/`false`.
# Lists must be specified as comma-separated strings.
#
# All comments in this file can be removed safely, including the
# commented-out properties.
# You can verify the integrity of your settings with `kong check <conf>`.

#------------------------------------------------------------------------------
# GENERAL
#------------------------------------------------------------------------------

#prefix = /usr/local/kong/       # Working directory. Equivalent to Nginx's
                                 # prefix path, containing temporary files
                                 # and logs.
                                 # Each Kong process must have a separate
                                 # working directory.

#log_level = notice              # Log level of the Nginx server. Logs are
                                 # found at <prefix>/logs/error.log
# Note: See http://nginx.org/en/docs/ngx_core_module.html#error_log for a list
# of accepted values.

#custom_plugins =                # Comma-separated list of additional plugins
                                 # this node should load.
                                 # Use this property to load custom plugins
                                 # that are not bundled with Kong.
                                 # Plugins will be loaded from the
                                 # `kong.plugins.{name}.*` namespace.

#anonymous_reports = on          # Send anonymous usage data such as error
                                 # stack traces to help improve Kong.

#------------------------------------------------------------------------------
# NGINX
#------------------------------------------------------------------------------

#proxy_listen = <IP_ADDRESS>:8000     # Address and port on which Kong will accept
                                 # HTTP requests.
                                 # This is the public-facing entrypoint of
                                 # Kong, to which your consumers will make
                                 # requests to.
# Note: See http://nginx.org/en/docs/http/ngx_http_core_module.html#listen for
# a description of the accepted formats for this and other *_listen values.

#proxy_listen_ssl = <IP_ADDRESS>:8443 # Address and port on which Kong will accept
                                 # HTTPS requests if `ssl` is enabled.

#admin_listen = <IP_ADDRESS>:8001     # Address and port on which Kong will expose
                                 # an entrypoint to the Admin API.
                                 # This API lets you configure and manage Kong,
                                 # and should be kept private and secured.

#admin_listen_ssl = <IP_ADDRESS>:8444 # Address and port on which Kong will accept
                                 # HTTPS requests to the admin API, if
                                 # `admin_ssl` is enabled.

#nginx_worker_processes = auto   # Determines the number of worker processes
                                 # spawned by Nginx.

#nginx_daemon = on               # Determines wether Nginx will run as a daemon
                                 # or as a foreground process. Mainly useful
                                 # for development or when running Kong inside
                                 # a Docker environment.

#mem_cache_size = 128m           # Size of the in-memory cache for database
                                 # entities. The accepted units are `k` and
                                 # `m`, with a minimum recommended value of
                                 # a few MBs.

#ssl = on                        # Determines if Nginx should be listening for
                                 # HTTPS traffic on the `proxy_listen_ssl`
                                 # address. If disabled, Nginx will only bind
                                 # itself on `proxy_listen`, and all SSL
                                 # settings will be ignored.

#ssl_cert =                      # If `ssl` is enabled, the absolute path to
                                 # the SSL certificate for the
                                 # `proxy_listen_ssl` address.

#ssl_cert_key =                  # If `ssl` is enabled, the absolute path to
                                 # the SSL key for the `proxy_listen_ssl`
                                 # address.

#admin_ssl = off                 # Determines if Nginx should be listening for
                                 # HTTPS traffic on the `admin_listen_ssl`
                                 # address. If disabled, Nginx will only bind
                                 # itself on `admin_listen`, and all SSL
                                 # settings will be ignored.

#admin_ssl_cert =                # If `admin_ssl` is enabled, the absolute path
                                 # to the SSL certificate for the
                                 # `admin_listen_ssl` address.

#admin_ssl_cert_key =            # If `admin_ssl` is enabled, the absolute path
                                 # to the SSL key for the `admin_listen_ssl`
                                 # address.

#upstream_keepalive = 60         # Sets the maximum number of idle keepalive
                                 # connections to upstream servers that are
                                 # preserved in the cache of each worker
                                 # process. When this number is exceeded, the
                                 # least recently used connections are closed.

#------------------------------------------------------------------------------
# DATASTORE
#------------------------------------------------------------------------------

# Kong will store all of its data (such as APIs, consumers and plugins) in
# either Cassandra or PostgreSQL.
#
# All Kong nodes belonging to the same cluster must connect themselves to the
# same database.

database = postgres             # Determines which of PostgreSQL or Cassandra
                                 # this node will use as its datastore.
                                 # Accepted values are `postgres` and
                                 # `cassandra`.

pg_host = ******            # The PostgreSQL host to connect to.
pg_port = 5432                  # The port to connect to.
pg_user = kong                  # The username to authenticate if required.
pg_password = ******                  # The password to authenticate if required.
pg_database = kong              # The database name to connect to.

pg_ssl = on                    # Toggles client-server TLS connections
                                 # between Kong and PostgreSQL.

pg_ssl_verify = on             # Toggles server certificate verification if
                                 # `pg_ssl` is enabled.
                                 # See the `lua_ssl_trusted_certificate`
                                 # setting to specify a certificate authority.

#cassandra_contact_points = <IP_ADDRESS>  # A comma-separated list of contact
                                       # points to your cluster.

#cassandra_port = 9042           # The port on which your nodes are listening
                                 # on. All your nodes and contact points must
                                 # listen on the same port.

#cassandra_keyspace = kong       # The keyspace to use in your cluster.

#cassandra_timeout = 5000        # Defines the timeout (in ms), for reading
                                 # and writing.

#cassandra_ssl = off             # Toggles client-to-node TLS connections
                                 # between Kong and Cassandra.

#cassandra_ssl_verify = off      # Toggles server certificate verification if
                                 # `cassandra_ssl` is enabled.
                                 # See the `lua_ssl_trusted_certificate`
                                 # setting to specify a certificate authority.

#cassandra_username = kong       # Username when using the
                                 # `PasswordAuthenticator` scheme.

#cassandra_password =            # Password when using the
                                 # `PasswordAuthenticator` scheme.

#cassandra_consistency = ONE     # Consistency setting to use when reading/
                                 # writing to the Cassandra cluster.

#cassandra_lb_policy = RoundRobin  # Load balancing policy to use when
                                   # distributing queries across your Cassandra
                                   # cluster.
                                   # Accepted values are `RoundRobin` and
                                   # `DCAwareRoundRobin`.
                                   # Prefer the later if and only if you are
                                   # using a multi-datacenter cluster.

#cassandra_local_datacenter =    # When using the `DCAwareRoundRobin` load
                                 # balancing policy, you must specify the name
                                 # of the local (closest) datacenter for this
                                 # Kong node.

#cassandra_repl_strategy = SimpleStrategy  # When migrating for the first time,
                                           # Kong will use this setting to
                                           # create your keyspace.
                                           # Accepted values are
                                           # `SimpleStrategy` and
                                           # `NetworkTopologyStrategy`.

#cassandra_repl_factor = 1       # When migrating for the first time, Kong
                                 # will create the keyspace with this
                                 # replication factor when using the
                                 # `SimpleStrategy`.

#cassandra_data_centers = dc1:2,dc2:3  # When migrating for the first time,
                                       # will use this setting when using the
                                       # `NetworkTopologyStrategy`.
                                       # The format is a comma-separated list
                                       # made of <dc_name>:<repl_factor>.

#cassandra_schema_consensus_timeout = 10000  # Defines the timeout (in ms) for
                                             # the waiting period to reach a
                                             # schema consensus between your
                                             # Cassandra nodes.
                                             # This value is only used during
                                             # migrations.

#------------------------------------------------------------------------------
# CLUSTERING
#------------------------------------------------------------------------------

# In addition to pointing to the same database, each Kong node must be
# reachable by the other nodes in the cluster.
#
# Kong's clustering works on the IP layer (hostnames are not supported, only
# IPs) and expects a flat network topology without any NAT between the
# datacenters.
#
# A common pattern is to create a VPN between the two datacenters such that
# the flat network assumption is not violated.
#
# See the clustering reference for more informations:
# https://getkong.org/docs/latest/clustering/

#cluster_listen = <IP_ADDRESS>:7946   # Address and port used to communicate with
                                 # other nodes in the cluster.
                                 # All other Kong nodes in the same cluster
                                 # must be able to communicate over both
                                 # TCP and UDP on this address.
                                 # Only IPv4 addresses are supported.

#cluster_listen_rpc = <IP_ADDRESS>:7373  # Address and port used to communicate
                                      # with the cluster through the agent
                                      # running on this node. Only contains
                                      # TCP traffic local to this node.

#cluster_advertise =             # By default, the `cluster_listen` address
                                 # is advertised over the cluster.
                                 # If the `cluster_listen` host is '<IP_ADDRESS>',
                                 # then the first local, non-loopback IPv4
                                 # address will be advertised to other nodes.
                                 # However, in some cases (specifically NAT
                                 # traversal), there may be a routable address
                                 # that cannot be bound to. This flag enables
                                 # advertising a different address to support
                                 # this.

#cluster_encrypt_key =           # base64-encoded 16-bytes key to encrypt
                                 # cluster traffic with.

#cluster_keyring_file =          # Specifies a file to load keyring data from.
                                 # Kong is able to keep encryption keys in sync
                                 # and perform key rotations. During a key
                                 # rotation, there may be some period of time
                                 # in which Kong is required to maintain more
                                 # than one encryption key until all members
                                 # have received the new key.

#cluster_ttl_on_failure = 3600   # Time to live (in seconds) of a node in the
                                 # cluster when it stops sending healthcheck
                                 # pings, possibly caused by a node or network
                                 # failure.
                                 # If a node is not able to send a new
                                 # healthcheck ping before the expiration,
                                 # other nodes in the cluster will stop
                                 # attempting to connect to it.
                                 # Recommended to be at least `60`.

#cluster_profile = wan           # The timing profile for inter-cluster pings
                                 # and timeouts. If a `lan` or `local` profile
                                 # is used over the Internet, a high rate of
                                 # failures is risked as the timing contraints
                                 # would be too tight.
                                 # Accepted values are `local`, `lan`, `wan`.

#------------------------------------------------------------------------------
# DNS RESOLVER
#------------------------------------------------------------------------------

#dns_resolver =                  # Comma separated list of nameservers, each
                                 # entry in `ipv4[:port]` format to be used by
                                 # Kong. If not specified the nameservers in
                                 # the local `resolv.conf` file will be used.
                                 # Port defaults to 53 if omitted.

#dns_hostsfile = /etc/hosts      # The hosts file to use. This file is read
                                 # once and its content is static in memory.
                                 # To read the file again after modifying it,
                                 # Kong must be reloaded.

#------------------------------------------------------------------------------
# DEVELOPMENT & MISCELLANEOUS
#------------------------------------------------------------------------------

# Additional settings inherited from lua-nginx-module allowing for more
# flexibility and advanced usage.
#
# See the lua-nginx-module documentation for more informations:
# https://github.com/openresty/lua-nginx-module

lua_ssl_trusted_certificate = /etc/ssl/certs/rds-combined-ca-bundle.pem  # Absolute path to the certificate
                                 # authority file for Lua cosockets in PEM
                                 # format. This certificate will be the one
                                 # used for verifying Kong's database
                                 # connections, when `pg_ssl_verify` or
                                 # `cassandra_ssl_verify` are enabled.

lua_ssl_verify_depth = 20        # Sets the verification depth in the server
                                 # certificates chain used by Lua cosockets,
                                 # set by `lua_ssl_trusted_certificate`.
                                 # This includes the certificates configured
                                 # for Kong's database connections.

#lua_code_cache = on             # When disabled, every request will run in a
                                 # separate Lua VM instance: all Lua modules
                                 # will be loaded from scratch. Useful for
                                 # adopting an edit-and-refresh approach while
                                 # developing a plugin.
                                 # Turning this directive off has a severe
                                 # impact on performance.

#lua_package_path =              # Sets the Lua module search path (LUA_PATH).
                                 # Useful when developing or using custom
                                 # plugins not stored in the default search
                                 # path.

#lua_package_cpath =             # Sets the Lua C module search path
                                 # (LUA_CPATH).

#lua_socket_pool_size = 30       # Specifies the size limit for every cosocket
                                 # connection pool associated with every remote
                                 # server

Operating System: CentOS (the official Kong Docker image)

I had similar problem a year ago upgrading on different release and plugin(I believe it was runscope). If my memory is correct, What i ended up doing was going into Cassandra docker and in DB plugin table deleting the offending plugin, then restart and add it again. Either that or I manually enabled the plugin in conf of Kong docker.

The SSL plugin isn't distributed with Kong 0.10, so I do believe the proper behavior will be to manually clear the entry from the datastore.

Sadly, we did not include a migration to take care of this change... Sorry about that.

Yikes. So, to be clear to migrate these records, I must:

Log into my postgres db and DELETE FROM plugins WHERE name='ssl';
Issue requests to /certificates for each api whose ssl plugin record was deleted

Is that correct? Will there be downtime for my 0.9.x cluster during the switchover or are the certificates cached on each node? I am looking to upgrade a production cluster, so of course I want a clean upgrade.

Correct. The certificates should be cached on each node of your 0.9.x cluster though (if they were previously hit).

Verified that this workflow works.


[v9] Remove CDTs and use regular conda packages for OpenGL support

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

This change will remove the need for users to manually add libegl in their conda dependencies when using gz-rendering from conda-forge.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge-webservices/actions/runs/11134422306.


The mxroyale HelloWorld example is not working properly

The x and y properties of the mx:Label component in the HelloWorld example seem to be ignored:
<mx:Label text="Hello World" x="20" y="20" />
Can this be fixed?
Regards,
Piotr

Hi, just check the example from a fresh build and I see is fully working

I just installed apache-royale-0.9.8-bin-js-swf.zip built 20201024. The
"Hello World" shows in the top left corner of the screen. Have tried
several browsers with the same result - 'x' and 'y' are ignored.
Running build in VSCode shows one warning:
WARNING:
e:/Dev/Royale/HelloRoyale/bin/js-debug/mx/core/UIComponent.js:3242: WARNING

Suspicious code. This code lacks side-effects. Is there a bug?
} else if ((this.mx_core_UIComponent__toolTip == null ||
this.mx_core_UIComponent__toolTip == "") &&
this.mx_core_UIComponent__toolTipBead != null) {

Carlos, do you get the same warning?
When you say "is fully working", the label is offsetted as expected,
correct?
On Sat, Oct 24, 2020 at 4:13 AM Carlos Rovira<EMAIL_ADDRESS>wrote:

Hi, just check the example from a fresh build and I see is fully working
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/royale-asjs/issues/924#issuecomment-715878757,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARM6PRMJDFST7D3P7AYG2GDSMKEA7ANCNFSM4S5BO4EA
.

Hi,
I don't get any warning. I must say that I'm not following emulation development, so maybe others doing that work should respond here. Just say that looking at the code un hello world and the result in screen all seems ok to me. The label is positioned absolutely at x = 20, y = 20 as expected from the code


Stream has already been listended to.

Same problem

same with me, how to resolve it?

Calling EasyGeofencing.getGeofenceStream() multiple times, from multiplaces gives this.

Hi there guys thanks for reporting the issue i am looking into this will sooner update this to null safety and also with the reported issues solution

Made below changes in easy_geofencing.dart and it worked for me.
static stopGeofenceService() {     print(_positionStream);     if (_positionStream != null) {       _positionStream!.cancel();       _positionStream = null;     }   }
And when calling Geofence service and Geofence Stream multiple time, stop the geofence service and cancel the stream before changing the route.
geofenceStatusStream?.cancel(); EasyGeofencing.stopGeofenceService();

Made below changes in easy_geofencing.dart and it worked for me. static stopGeofenceService() { print(_positionStream); f (_positionStream != null) { _positionStream!.cancel();  _positionStream = null;  } }
And when calling Geofence service and Geofence Stream multiple time, stop the geofence service and cancel the stream before changing the route. geofenceStatusStream?.cancel(); EasyGeofencing.stopGeofenceService();

i did what you told, but gives  Parse value===>false and fence service doesnt start

Hello everyone, I will not be selfish and will share with you how I fixed it myself.
You should make changes to the library itself
version 0.2.0
_static stopGeofenceService() {
if (_positionStream != null) {
_positionStream!.cancel();
positionStream = null;
}
}
_wherever there is an add function, add a sink
controller.sink.add(GeofenceStatus.enter);
well, the most important thing is to add broadcast ()
static StreamController _controller =
StreamController.broadcast();
Well, now it's up to you, call stop() and start()
Since this is a stream, we don’t forget that the previous stream loses all data, there can always be only 1 stream, well, or correct me, thanks to Putler kaput, Ukraine wins


Fix global properties setters and add global skew for node2d

The introduction of the skew makes the setter of global properties false in some cases.

For example, a parent has local skew of 45° and scale of (1,1), and a child with local skew of -45° and scale of (1,1).
The child will have a global scale of (1,a). If we want to put global scale of (1,1), the current global method will set the local scale with new_global_scale/parent_global_scale so (1,1)/(1,1) = (1,1). So the global scale will stay (1,a).
with a = ]0,1[

Same wrong behavior can be reproduced with the rotation. So fixed the setters of global rotation and scale.
Also added global skew property and added const when possible.

Do you have any reproduction project where the wrong behavior can be easily observed?

Do you have any reproduction project where the wrong behavior can be easily observed?

Hey @KoBeWi, sure, please try this code
func _ready():
	var parent_sprite:=Sprite2D.new()
	parent_sprite.skew=PI/4
	parent_sprite.texture=preload("res://icon.png")
	add_child(parent_sprite)
	var child_sprite:=Sprite2D.new()
	child_sprite.texture=preload("res://icon.png")
	parent_sprite.add_child(child_sprite)
	child_sprite.skew=-PI/5
	child_sprite.position=Vector2.ONE*64
	print(child_sprite.global_scale)
	child_sprite.global_scale=Vector2.ONE
	print(child_sprite.global_scale)

In current godot 4 ver, the global scale will not be (1,1).

What is 'current Godot 4 ver'? Alpha 6? Some hash off master?

I tried the snippet with the current master #3b57c2c
func _ready():
	var parent_sprite:=Sprite2D.new()
	parent_sprite.skew=PI/4
	add_child(parent_sprite)

	var child_sprite:=Sprite2D.new()
	child_sprite.skew=-PI/4
	parent_sprite.add_child(child_sprite)

	print(child_sprite.global_scale) #  output : (1, 0.541196)
	child_sprite.global_scale=Vector2.ONE
	print(child_sprite.global_scale) # output : (1, 0.541196)

After this PR
	print(child_sprite.global_scale) #  output : (1, 0.541196)
	child_sprite.global_scale=Vector2.ONE
	print(child_sprite.global_scale) # output : (1, 1)

Applied the renaming of the variable and aligned in the other global setters. If everything is ok I will squash the commits.

Commits squashed, all should be good now. I tried to make a test but impossible to let it works.

Thanks!


Is it possible somehow register a serviceWorker in development?

I understand that in most cases it's superfluous but I have a slightly non-standard case)
My application is mostly placed on the third party's api. This API works slowly, and has a limit for requests. On development (when you often load and reload page many times), the page I create a lot of requests to this api, it slows down my work and exhausts all the limits.
I see a service worker as a good solution to this problem.
In production are all great. Network requests to the third party API use the CacheFirst strategy. This is accelerating the work of the application and reduces the load on the remote server.
I have no need to take over about actual of data and I would like to apply the same caching strategy for development too.

@cawa-93 Why are you trying to cache ui with remote data instead adding a proxy/middleware (abstraction layer) serving for example mock json files simulating remote api service calls?.
I use this approach for html ppl that does not have access to backend, including CRUD operations (just a mock server with express accessing local json files).
You can use a proxy and provide a url to fetch data and using process.env with .local variants changing it on development on some profile.
For example, using SERVICE_API_CALL on process.env files, just change it to use localhost on some profile, then on development use this profile, addind a server to your environment, then add mapping on the node/express server to mock via json files (you must create them) and you are done.
Once tested you can do a real test using another profile, where SERVICE_API_CALL just point to the real service api.

@userquin  Because

I'm working on a serverless desktop application.
I do not cache static files ui at all.

The service worker performs this task: he works as a proxy to the third-party API and caches successful requests. And only requests to third party APIs are cached, nothing more. Actually, this is all that in my case requires a service worker. I don't think it makes sense to run a local proxy server that will do exactly the same thing as a service worker.

Despite being recommended against, you can achieve this by registering the service worker yourself.
For example add the following snipped to you code (e.g., main.ts or src/App.vue)
import { Workbox } from "workbox-window";

const serviceWorkerPath = '/sw.js';

if ('serviceWorker' in navigator) {
  const wb = new Workbox(serviceWorkerPath);
  wb.register()
    .then(() => {
      // registered
    })
    .catch((error) => {
      // error :-(
    });
}

If you need more functionally of the module (e.g., registerSW), you can try to copy bits from https://github.com/antfu/vite-plugin-pwa/blob/master/src/client/build/register.ts#L12.

@cawa-93 so you only need the service worker to intercept api calls, no? I'll try (ASAP) to make a special service worker here for that purpose that will work also in development.
Maybe we should open a discussion...
If you have some sugestions don't hesitate to contact me here or on Discord (Joaquín#7667).

I have a new branch on local to allow test service worker on development only for third party libraries (in general if runtimeCaching is configured on workbox entry) and only for generateWS strategy. In development only the runtimeCaching is generated (also registered) excluding manifest file and all routes and assets from the generated service worker.
I have it working on vue-router example, I have added a few buttons to change the source of an image on App.vue using https://http.cat/
You can see in action here: https://github.com/userquin/vite-plugin-pwa/tree/feat/third-party-cache-api-sw.
To run the demom from the root folder: pnpm run example:router:dev => don't forget to run pnpm install && pnpm run build before.
You can also start the build demo pnpm run example:router:start

Unfortunately we have made the decision not to include this behavior, since it's just another big maintaining surface.
I'll keep the branch on my fork a few days if you want to clone/download it.

@cawa-93 development support added on 0.11.13 version


Dragon ability UI issues

Description
There is no cursor indication when the Dragon has it's Bite or Fire Breath ability selected.
There isn't even a hotbar indication for when Fire Breath is selected. If you forget whether you really clicked the button, the ONLY way to check is "will it launch a fireball when I click in the world", or toggle Devour twice

I think this is solvable in yaml by just setting the action image types, but I'm not 100% sure.


Unexpected end of JSON input while parsing

Instructions
i found some error with install fcl by npm
Problem
➜  nft git:(main) ✗ npm i -S @onflow/fcl @onflow/types
npm ERR! Unexpected end of JSON input while parsing near '...browserslist","versio'

i found how to solve it .


Disallow overlapping of two time slots.

I have written this code in controller to disallow overlapping of any two time slots. I dont know if this library has any option to disallow overlapping.
The code does not work with all test cases.
The method eventTimesChanged is called when an event is dragged and dropped or resized into a different date / time on the calendar. What if I resize an existing event? It shifts any event coming in its way to right side

Any ideas?
Please have a look at my code too. I have passed calendarNewEventStart and calendarNewEventEnd
from html page itself.
		vm.calendar.eventTimesChanged = function(calendarEvent,calendarNewEventStart,calendarNewEventEnd) {
//			console.log(vm.calendar.events.length);

			for (var i = 0; i < vm.calendar.events.length; i++) {
				var oneEvent = vm.calendar.events[i];
				if(oneEvent === calendarEvent)
				{
					console.log("i found that event");
				}
				else
				{
					//console.log("this is not at all equal" + oneEvent);
					if(calendarNewEventStart >= oneEvent.startsAt && calendarNewEventStart < oneEvent.endsAt)
					{
						//start is between the time range  of another event
//						console.log("start is overlapping");
						alert('start is overlapping', calendarEvent);
					}
					else if(calendarNewEventEnd > oneEvent.startsAt && calendarNewEventEnd <= oneEvent.endsAt)
					{
						//end is between the time range  of another event
//						console.log("end is overlapping")
//						alert('end is overlapping', calendarEvent);
					}
					else
					{
						alert('perfect', calendarEvent);
						calendarEvent.startsAt = calendarNewEventStart;
						calendarEvent.endsAt = calendarNewEventEnd;
					}

					console.log("not eq " + oneEvent);
					break;
				}

There isn't any option to disallow overlapping events, the calendar purposefully gives you all the hooks so you can implement this yourself. You might want to try using the calendarHelper.eventIsInPeriod helper function for what you're trying to accomplish:
https://github.com/mattlewis92/angular-bootstrap-calendar/blob/master/src/services/calendarHelper.js#L61
If you still need more help you can put the code that's failing into a plunker and I can try and fix it for you :smile:

Hello @mattlewis92 ,
Please have a look at http://plnkr.co/edit/WYJdXcax0m8ISUJKsB20?p=preview
It does not work for overlapping as desired.
Also, events are disappearing .

You didn't check the event against any of the other events which was why it wasn't working, here's your plunker fixed: http://plnkr.co/edit/JW6JpLQrRBOQwys1Kw79?p=preview

I checked the plunker , but now resize does not work and gives alert of event overlapping.Also, I cannot push one 15min event between two events with space of 15 mins. You may try it in plunker.

You were passing the event end date as the start date which was why it was broken. I've fixed that and added a check if the event is not the dragged / resized event which should fix your problem.


Consider removing slim semantic databases

Since 1.8.0, our semantic databases come in two variations - fat (including the original code) and slim (not including the source code). Both approaches have their pros and cons, so I hoped to provide both variations simultaneously - with a particular implementation strategy hidden behind a common API.
It turns out, however, that it's not that simple. For example, slim databases need a sourcepath for deserialization (they don't include source code per se - just relative paths of source files), which fat databases don't.
I suggest that we take an especially good look at user feedback in this area, and then try to pick just one standard and roll with it.  In the meanwhile, let's support both with fat dbs are default.

@olafurpg Would you like to do the honors and change the default to fat?

The default is not fat. I'm not yet convinced it's a good idea to remove slim. I have a feeling that once we start embedding semanticdb files into sources jars then it will be wasteful to embed the file contents in the semanticdb files.

This is nearly a special case of fatDb though isn’t it?  I mean in the case of embedding into a jar with sources it seems easy to find the sources, we still don’t need to ask the users anything.  Maybe if slim goes away we end up with fat and virtualFat which looks like a fatDb in every way except it is loaded from a jar and the sources are beside the db instead of inside of it.  A slight tweak to the packaging process could have the sources stripped out on insertion into the jar.

That is a good observation @ShaneDelmore I agree, .semanticdb files inside -sources.jar may as well considered fat since there's no need for custom --sourcepath from the user.

We're one step away from releasing Scalameta 2.0, and after 2.0 compatibility will become a huge deal. As a result, I'll be closing tickets that would be nice to have, but don't warrant potential associated breakages. This ticket is one of them.


socket.timeout: timed out

Any ideas to fix this one?
Scanning...
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/pool.py", line 121, in worker
result = (True, func(*args, **kwds))
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
return list(map(*args))
File "gitfinder.py", line 25, in findgitrepo
with urlopen(''.join(['http://', domain, '/.git/HEAD']), timeout=5) as response:
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1345, in http_open
return self.do_open(http.client.HTTPConnection, req)
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1320, in do_open
r = h.getresponse()
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1336, in getresponse
response.begin()
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 306, in begin
version, status, reason = self._read_status()
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 267, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/socket.py", line 589, in readinto
return self._sock.recv_into(b)
socket.timeout: timed out
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "gitfinder.py", line 90, in
main()
File "gitfinder.py", line 86, in main
pool.map(fun, domains)
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/pool.py", line 268, in map
return self._map_async(func, iterable, mapstar, chunksize).get()
File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/pool.py", line 657, in get
raise self._value
socket.timeout: timed out

Add something like this to gitfinder:
except OSError:
    return

Sorry for the delay.
It's fixed with https://github.com/internetwache/GitTools/commit/762e412c213f22df7f5ae3194383b2a8176e01cb now!


shell: optimize history storage a bit

When padding is added to "fill" the gap in order to wrap to the
beginning of the ring buffer, such padding is attributed to the
current item being added. Let's attribute it to the previous entry
instead so it'll be freed along with that entry and make the space
available one entry sooner, increasing the chances for keeping the
current entry around longer.

Rebased on top of latest ring_buf changes, and optimized yet a bit more.


Allow installShellCompletion to read from stdin or program output

As I already mentioned in https://github.com/NixOS/nixpkgs/pull/65211#issuecomment-602305583, I would like to propose changing installShellCompletion to be able to somehow read the completions from the output of a program.
In kitty the code for installing the completions looks something like this:
mkdir -p "$out/share/"{bash-completion/completions,fish/vendor_completions.d,zsh/site-functions}
"$out/bin/kitty" + complete setup zsh > "$out/share/zsh/site-functions/_kitty"
"$out/bin/kitty" + complete setup fish > "$out/share/fish/vendor_completions.d/kitty.fish"
"$out/bin/kitty" + complete setup bash > "$out/share/bash-completion/completions/kitty.bash"

It could currently be rewritten as
mkdir 'completions'
"$out/bin/kitty" + complete setup zsh > 'completions/_kitty'
"$out/bin/kitty" + complete setup fish > 'completions/kitty.fish'
"$out/bin/kitty" + complete setup bash > 'completions/kitty.bash'

installShellCompletion --zsh 'completions/_kitty'
installShellCompletion --fish 'completions/kitty.fish'
installShellCompletion --bash 'completions/kitty.bash'

to use installShellCompletion. This is much more verbose than before. I propose adding the possibility of making installShellCompletion read stdin. The above code could then be written as follows for example:
"$out/bin/kitty" + complete setup zsh | installShellCompletion --zsh --name _kitty -
"$out/bin/kitty" + complete setup fish | installShellCompletion --fish --name kitty.fish -
"$out/bin/kitty" + complete setup bash | installShellCompletion --bash --name kitty.bash  -

@lilyball proposed something like this instead:
installShellCompletion \
  --zsh --name _kitty --exec “$out/bin/kitty + complete setup zsh” \
  --fish --name kitty.fish --exec “$out/bin/kitty + complete setup fish” \
  --bash --name kitty.bash --exec “$out/bin/kitty + complete setup bash”

I don't really care which of the two ways might be implemented.

Closing, as #83630 was merged.


Implements transitive maven jar repository rule.

This pull request provides an initial implementation of the transitive_maven_jar rule. The repository rule self hosted and generated the generate_workspace.bzl found in this CL.
Design considerations and additional slated functionality is discussed in this design document.
Provides a working solution for the upgrade problem discussed in #20
@kchodorow

Can one of the admins verify this patch?

@kchodorow I resolved the issue of constantly downloading the generate_workspace tool by adding the deploy jar in the transitive_maven_jar directory.
It works, but by no means is it optimal. I would rather not check a binary into the repository. However, this approach allows us to point users to an http_archive of just the transitive_maven_jar repository rule. That is, without leaking any information of how the tool resolves dependencies. The only annoyance is on our end with maintaining the jar. On that front, Alpha suggested creating a regular old rule to package that directory into a zip file.

I'd rather have the generate_workspace deploy jar be downloaded. Other than that, this looks good to go.

I'd rather have the generate_workspace deploy jar be downloaded.

Why is that? At least from a user's perspective, packaging them together is preferable. The two general approaches we could take for downloading would be to download from within the repository rule as I did before or to have the user use a http_archive. The first is obviously bad. The second is very clunky

I was thinking it would be better to have it be separate, so it would be easy to swap out a different version. However, I'm willing to merge it in as-is and see how it goes.
But: I was thinking about having //generate_workspace depend on transitive_maven_jar which runs generate_workspace and that seems like a bad idea.  It'll be annoying to bootstrap that if any step breaks.  Thus, please revert the WORKSPACE to using plain ol' generate_workspace.bzl.

But: I was thinking about having //generate_workspace depend on transitive_maven_jar which runs generate_workspace and that seems like a bad idea. It'll be annoying to bootstrap that if any step breaks. Thus, please revert the WORKSPACE to using plain ol' generate_workspace.bzl.

Done.

Jenkins, test this please.


Sending base64 images through Http Trigger

Is your question related to a specific version? If so, please specify:
What language does your question apply to? (e.g. C#, JavaScript, Java, All)
Python
Question
I am making use python face-recognition module, when i send base64 images to the my function app on azure larger than 5mb in total, the request fails
it doesn't when i use smaller images
i know the limit for http trigger is 100mb, please what might be the issue and how do i solve this problem

Hello, is this issue still occurring? If so, could you provide more information about what errors you're seeing from this?


Custom Telemetry_Endpoints with Statsd consumer

Environment

Telemetry Streaming Version: 1.16
BIG-IP Version: <IP_ADDRESS>

Summary
Unable to get "Telemetry_Endpoints" to send data to a Statsd "Telemetry_Consumer".
Steps To Reproduce
Steps to reproduce the behavior:

Submit the following declaration:

{
  "class": "Telemetry",
  "Endpoints_Profiles": {
    "class": "Telemetry_Endpoints",
    "basePath": "/mgmt/tm/sys",
    "items": {
      "cpuProfiles": {
        "name": "cpuProfiles",
        "path": "cpu/stats"
      },
      "memProfiles": {
        "name": "memProfiles",
        "path": "sys/memory/stats"
      }
    }
  },
  "Custom_System": {
    "class": "Telemetry_System",
    "systemPoller": [
      "Custom_System_Poller1",
      {
        "interval": 60
      }
    ]
  },
  "Custom_System_Poller1": {
    "class": "Telemetry_System_Poller",
    "interval": 60,
    "endpointList": "Endpoints_Profiles"
  },
  "Default_System": {
    "class": "Telemetry_System",
    "systemPoller": {
      "interval": 60
    }
  },
  "Statsd_Consumer": {
    "class": "Telemetry_Consumer",
    "type": "Statsd",
    "host": "<IP_ADDRESS>",
    "protocol": "tcp",
    "port": 8125,
    "allowSelfSignedCert": true
  }
}

Expected Behavior
We expected to receive "cpuProfiles" and "memProfiles" on our Telegraf Statsd collector.
We also tested removing "Default_System\Telemetry_System" section and received no metrics.
Actual Behavior
We are only seeing the default metrics created by "Default_System\Telemetry_System".

telemetryServiceInfo
sslCerts
clientSslProfiles
serverSslProfiles
networkTunnels
system
pools
httpProfiles
iRules
virtualServers

Extra sys in memProfiles path was causing this not to work.
Should be:
"name": "memProfiles",
        "path": "memory/stats"


NLog Exceptions don't get logged in NLog diagnostics

When throwExceptions="true" is set on the NLog node, we could see the following:
System.AggregateException: One or more errors occurred. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> NLog.NLogRuntimeException: Exception occurred in NLog ---> System.ArgumentException: The specified string is not in the form required for a subject.
   at System.Net.Mail.Message.set_Subject(String value)
   at NLog.Targets.MailTarget.SetupMailMessage(MailMessage msg, LogEventInfo logEvent)
   at NLog.Targets.MailTarget.ProcessSingleMailMessage(List`1 events)
   --- End of inner exception stack trace ---
   at NLog.LoggerImpl.<>c__DisplayClass1.<Write>b__0(Exception ex)
   at NLog.Internal.SingleCallContinuation.Function(Exception exception)
   at NLog.Targets.MailTarget.ProcessSingleMailMessage(List`1 events)
   at NLog.Targets.MailTarget.Write(AsyncLogEventInfo[] logEvents)
   at NLog.Targets.Target.WriteAsyncLogEvent(AsyncLogEventInfo logEvent)
   at NLog.LoggerImpl.WriteToTargetWithFilterChain(TargetWithFilterChain targetListHead, LogEventInfo logEvent, AsyncContinuation onException)
   at NLog.LoggerImpl.Write(Type loggerType, TargetWithFilterChain targets, LogEventInfo logEvent, LogFactory factory)

However, with nLog set to the following:
 <nlog autoReload="true" internalLogFile="nlog.log" internalLogLevel="Trace">

You don't see any error occurring at all in the log file. I'd have expected an Error to be logged here?

@Xharze your advise please.
I See in the code:
      catch (Exception exception)
            {
                if (exception.MustBeRethrown())
                {
                    throw;
                }

                InternalLogger.Error(exception.ToString());

So if exception.MustBeRethrown == true, it's never logged. Is this intended behavior?

I can understand the reasoning for not logging the exception when it's
thrown, but I also think it would be nice to log the error in the internal
log. It will make it easier to locate issues when just looking at the log
file.

In case of exception is a StackOverflowException or ThreadAbortException or OutOfMemoryException, it should be rethrown as soon as possible, because doing some other calls in such extreme conditions can cause other exceptions to be thrown, which in the catch block will effectively mask the original exception and make it hard to diagnose the cause of it.

This has been fixed in MailTarget with commit https://github.com/NLog/NLog/commit/0601c07ac298dc82408597af8c4ffb928a3eaa15

this is structural fixed in #1143


Update condor version and build new wmagent release

Just talked to Dirk (who talked to Brian), we need to update the condor.spec file to 8.5.4:
https://github.com/cms-sw/cmsdist/blob/comp_gcc493/condor.spec
and then build a new wmagent rpm and make sure it works (mainly PyCondorPlugin).

We need to either adjust or remove the patch to the package since it doesn't work anymore with 8.5.4
https://github.com/cms-sw/cmsdist/blob/comp_gcc493/cms-htcondor-build.patch
@bbockelm can you take a look at the patch and see if we still need it ?

Ok, you can't completely remove the patch either, fails to build. Will try to adjust and just remove the sections that can't be used...

Adjusted the patch and it applies clean, but the build still fails. @bbockelm , I am stuck now.

The action "build-external+condor+8.5.4" was not completed successfully because Failed to build condor. Log file in /build/hufnagel/w/BUILD/slc6_amd64_gcc493/external/condor/8.5.4/log. Final lines of the log file:

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables PACKAGE_DEP_CFLAGS
and PACKAGE_DEP_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
configure: error: ./configure failed for gsi/openssl_error/source
make[3]: *** [externals/bundles/globus/6.0/globus-prefix/src/globus-stamp/globus-configure] Error 1
make[3]: Leaving directory /build/hufnagel/w/BUILD/slc6_amd64_gcc493/external/condor/8.5.4/condor-8.5.4' make[2]: *** [externals/bundles/globus/6.0/CMakeFiles/globus.dir/all] Error 2 make[2]: Leaving directory /build/hufnagel/w/BUILD/slc6_amd64_gcc493/external/condor/8.5.4/condor-8.5.4'
make[1]: *** [CMakeFiles/externals.dir/rule] Error 2
make[1]: Leaving directory `/build/hufnagel/w/BUILD/slc6_amd64_gcc493/external/condor/8.5.4/condor-8.5.4'
make: *** [externals] Error 2
error: Bad exit status from /build/hufnagel/w/tmp/rpm-tmp.5D7EN3 (%build)
RPM build errors:
Bad exit status from /build/hufnagel/w/tmp/rpm-tmp.5D7EN3 (%build)

@hufnagel - can you format that comment so it's readable?  Also, can you send me the build machine you use above so I can poke around at log files?

Better ? Build machine is vocms022, build is in /build/hufnagel/w/

Ok, I could fake a pkginfo file for openssl, but only by putting full expanded paths into it (couldn't find a way to put environment variables into a package file). Even with that I get build errors:
'''

The action "build-external+condor+8.5.4" was not completed successfully because Failed to build condor. Log file in /build/hufnagel/w/BUILD/slc6_amd64_gcc493/external/condor/8.5.4/log. Final lines of the log file:
if ( (method_bitmask & CAUTH_KERBEROS) && Condor_Auth_Kerberos::Initialize() == false ) {
^
/build/hufnagel/w/BUILD/slc6_amd64_gcc493/external/condor/8.5.4/condor-8.5.4/src/condor_io/authentication.cpp: In member function 'int Authentication::handshake_continue(MyString, bool)':
/build/hufnagel/w/BUILD/slc6_amd64_gcc493/external/condor/8.5.4/condor-8.5.4/src/condor_io/authentication.cpp:1039:45: error: 'Condor_Auth_Kerberos' has not been declared
if ( (shouldUseMethod & CAUTH_KERBEROS) && Condor_Auth_Kerberos::Initialize() == false ) {
^
/build/hufnagel/w/slc6_amd64_gcc493/external/cmake/2.8.5-comp/bin/cmake -E cmake_progress_report /build/hufnagel/w/BUILD/slc6_amd64_gcc493/external/condor/8.5.4/condor-8.5.4/CMakeFiles 50
[ 52%] make[2]: *** [src/condor_utils/CMakeFiles/condor_utils.dir/__/condor_io/authentication.cpp.o] Error 1
'''

That indeed looks like a bug in HTCondor - looks like they broke conditionally disabling Kerberos.
Still exists in master.  Will put together a patch.

Try this:
--- a/src/condor_io/authentication.cpp
+++ b/src/condor_io/authentication.cpp
@@ -997,7 +997,12 @@ int Authentication::handshake(MyString my_methods, bool non_blocking) {
         dprintf (D_SECURITY, "HANDSHAKE: handshake() - i am the client\n");
         mySock->encode();
                int method_bitmask = SecMan::getAuthBitmask(my_methods.Value());
-               if ( (method_bitmask & CAUTH_KERBEROS) && Condor_Auth_Kerberos::Initialize() == false ) {
+#if defined(HAVE_EXT_KRB5)
+               if ( (method_bitmask & CAUTH_KERBEROS) && Condor_Auth_Kerberos::Initialize() == false )
+#else
+               if (shouldUseMethod & CAUTH_KERBEROS)
+#endif
+               {
                        dprintf (D_SECURITY, "HANDSHAKE: excluding KERBEROS: %s\n", "Initialization failed");
                        method_bitmask &= ~CAUTH_KERBEROS;
                }
@@ -1047,7 +1052,12 @@ Authentication::handshake_continue(MyString my_methods, bool non_blocking)
        dprintf ( D_SECURITY, "HANDSHAKE: client sent (methods == %i)\n", client_methods);

        shouldUseMethod = selectAuthenticationType( my_methods, client_methods );
-       if ( (shouldUseMethod & CAUTH_KERBEROS) && Condor_Auth_Kerberos::Initialize() == false ) {
+#if defined(HAVE_EXT_KRB5)
+       if ( (shouldUseMethod & CAUTH_KERBEROS) && Condor_Auth_Kerberos::Initialize() == false )
+#else
+       if (shouldUseMethod & CAUTH_KERBEROS)
+#endif
+       {
                dprintf (D_SECURITY, "HANDSHAKE: excluding KERBEROS: %s\n", "Initialization failed");
                shouldUseMethod &= ~CAUTH_KERBEROS;
        }

Had to adjust the patch a bit, didn't apply and also was functionally wrong (you had a copy&paste error on the first chunk where you referenced shouldUseMethod  when it should be method_bitmask).
In addition there were was one more place where they forgot to wrap with HAVE_EXT_KRB5 conditionals, so I had to fix them too. See vocms022:/build/hufnagel/cmsdist/cms-htcondor.patch for the changes.
The package builds now. Unfortunately I can't really make a pull request for review due to the hack with the openssl package file. If I don't get feedback in HN on that I'll bring it up in the release planning meeting on Friday.

Tested new package with PyCondorPlugin in a Tier0 replay, seems to work. Doesn't mean everything works though, I am bit suspicious about the openssl package info hack and how it affects binaries. We don't use any binaries from the condor package in the agent though AFAIK.

Have a self-contained recipe to build this now, up to @BrunoCoimbra to decide how we want to deal with this (we either change the openssl build to create a pkginfo file or create a fake one inside the condor spec). To be followed up on in HN.

Pull request is in
https://github.com/dmwm/WMCore/issues/7127

I built 1.0.19.patch2 wmagent tag with the new condor PR (as provided by Dirk) and ran all the DMWM/Integration tests using PyCondorPlugin.

job priority change looks good
job removal by id looks good
jobs removal by request name looks good
all the rest looks good.

From my side, we can upgrade condor version. Is Marco taking care of this for CRAB3? Should we ping someone else to carry this validation on the analysis land?

New condor 8.5.4 is available in the official repo. Closing this issue.


community: create_sql_agent Resolve BadRequestError for API requests with pre-filled assistant

Description:
Fixes the issue where API requests with a pre-filled assistant message in the final position were causing a BadRequestError with code 400. The error message indicated that pre-filling the assistant response is not supported when using tools. The changes in this commit ensure that API requests no longer include an assistant message in the final position, allowing the API to handle the request correctly and prevent the invalid request error from occurring. With this fix, users can now make API requests smoothly without encountering the BadRequestError, improving the overall user experience and reliability of the API.

which model is this causing an error for?

ChatAnthropic caused a problem.

I made the suggested changes in the PR and it seems to be the solution to the same error I experienced in one of my projects.

I made the suggested changes in the PR and it seems to be the solution to the same error I experienced in one of my projects.

Alternatively, if I do not set the agent_type parameter , it works just fine.

+1 having this issue with ChatAnthropic

Hey team! Could you file an issue with a reproducable example (ideally the direct call of ChatAnthropic)? I think this PR won't solve the root issue
Alternatively could add a unit test showing what this fixes

this is ultimately a prompting issue, and our prompting strategy isn't compatible with ChatAnthropic. That being said, this isnt the best solution - the previous AI message is writen from the perspective of the assistant, so just putting it as a human message doesnt make sense
we are moving less and less towards built in prompts, so id recommend just passing in a prompt here


Bump to rulinalg 0.4

Thanks for doing this! If we merge we need to do a bump to 0.6 due to breaking changes (we reexport much of rulinalg). Because of this I'll try to get some of the other pending PRs in first.

I'm in a tricky situation with this PR. We have a few other big PRs pending (as you can see, you authored many of them!). I would like to get this merged in first, but it puts pressure on other PRs to accommodate the breaking changes.
What do you think of this? If you think we should get this in first then I am happy to make the changes to this PR myself and get it merged.

Closing in favour of #174


Custom validation error handler.

Hi, thanks for this package. I am trying to validate using the code below.
public async login(@Body(new JoiPipe({ group: 'TEST' })) loginRequest: LoginRequest): Promise<AuthResponse> {         console.log('Request validated'); }
The validation fails when proper input is not given, but I am not able to send a custom error code. It is throwing a default 400 BAD REQUEST error but I want to throw a custom error and handle it as a separate error and return it using an exception filter.
Please let me know if that can be done.

It should be possible to use an exception filter to check if a BadRequestException has been thrown (the one in https://github.com/whefter/nestjs-joi/blob/dc0a01476c9bdb6f2f857ef44785ca292abac86d/src/internal/joi.pipe.ts#L128), perhaps check for the beginning of the error message. Let me know if that works for you.

Yes I am using it like that. I am using an exception filter and tracking if the code is BAD REQUEST with validation error and parsing it. It should be good to allow user to configure how an error is thrown.
Thanks.

I'll give some thought to an option to configure the thrown error. But this seems to me to be an edge case that can be covered by the method described above.

It can be handled using a custom exception filter. Plus do you think you can split the core logic as a joi-core and Nest JS modules as separate module? I have forked your repo and I am using the core concept to use decorators to set schema for a type for Angular. Reason I am doing joi validation on angular too is just to make sure both front end and server side does the same validation on the objects. If you have any idea for that, splitting out to a core module, could help reusing that code across different implementations.

I added an option for this in v1.3.0, see: https://github.com/whefter/nestjs-joi#pipe-options-pipeopts
If you're in injection-enabled mode, see this for how to pass options to JoiPipeModule or to an inline constructor:

https://github.com/whefter/nestjs-joi#joipipemodule
https://github.com/whefter/nestjs-joi#defining-pipeopts-in-injection-enabled-mode

Let me know if this works for your use case.

Concerning your idea for splitting out the schema generation: it's an idea that I've had myself. Unfortunately I haven't had the time, especially since from what I can see it might involve reconfiguring the project as a monorepo with multiple packages. Though perhaps two separate repos would be best, but that makes testing interdepence somewhat more difficult.

Looks good. Like the implementation. It can be later extended to get custom exception as input as well.
I can try to make changes, but I have not contributed to open-source before. Will try to create a PR for that and see next week.

I do believe making a core module will help. But as you said, it has to be a separate module for core and separate packages for other frameworks. Personally I'm using it in one of my projects to easily perform same validations in both front end and api.

Thanks. Closing this issue for now.

FYI: I got around to splitting off the core logic into joi-class-decorators. That should make it easier to use in frontend apps without having to install all the NestJS dependencies.


Add note about how to allow local texture files in chrome and firefox

When I was first using the texture functionality, I couldn't get it to work without using a wikimedia image. I think it would be useful to include a note about how to allow local file access. I'll be submitting a pull request to that end by midnight tonight. Please don't make this change before me, as this is a required assignment for me.

Yeah this is a really good point


Custom pages label uses key

Upgrading to 3.3.1 from 3.2.5 causes custom page labels to use the untranslated key from the options (usually camel case). It looks like previously translateLabel was used, and could be fixed by being added to https://github.com/SoftwareBrothers/admin-bro/blob/master/src/frontend/components/app/sidebar/sidebar-pages.tsx#L32
I can work around it by changing the keys be appropriately cased using square bracket notation but I suspect this wasn't intentional. I also noticed the docs (https://adminbro.com/AdminBroOptions.html#pages) make reference to using a label option which doesn't seem to be implemented.

Same problem here. Example:
pages: {
customPage: {
label: "Custom page",
handler: async (request, response, context) => {
return {
text: 'I am fetched from the backend',
}
},
component: AdminBro.bundle("./reactjs/components/dashboard/Dashboard.tsx"),
},
anotherPage: {
label: "TypeScript page",
component: AdminBro.bundle("./reactjs/components/dashboard/Dashboard.tsx"),
}
},

@JSRossiter how did you solve it? I've the same problem with pages label translations.

@JSRossiter how did you solve it? I've the same problem with pages label translations.

Is there a solution to this? Label prop on pages doesn't work at the moment

Closing because the issue is old. If you still need help, please reopen.


Styling of tooltips

I'm trying your plugin with monokai.pro , but it seems the tooltips have their own color definitions. Unfortunately, some colors in the tooltips are quite unreadable. Is there any functionality to provide custom colors?

@atabel Did we end up making this configurable? I can't find any such mechanism in the code. Might also be useful to choose colors that work in both dark and light themes.

we can use variable colours, they are documented at https://www.sublimetext.com/docs/3/minihtml.html#variables
this is how it looks with default schemes:


Fix missing exported C function declarations with cimport_from_pyx enabled

Related to #5072.
This pull request attempts to fix the compilation errors that happen when the Cython compiler fails to generate the declarations of unused exported functions from pyx files with the cimport_from_pyx option on.

Looks good thanks @garychia


com.google.cloud.logging.LoggingException: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Write requests' and limit 'Write requests per minute' of service 'logging.googleapis.com'

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":

Search the issues already opened: https://github.com/googleapis/java-logging/issues
Check for answers on StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform

If you are still having issues, please include as much information as possible:
Environment details

Specify the API at the beginning of the title. For example, "BigQuery: ...").
General, Core, and Other are also allowed as types
OS type and version:
Java version:
version(s):

Steps to reproduce

?
?

Code example
// example

Stack trace
Any relevant stacktrace here.

External references such as API reference guides

?

Any additional information below
Following these steps guarantees the quickest resolution possible.
Thanks!

Are there any optimizations that can be explored for the above error. We tried batching as mentioned here
https://github.com/googleapis/java-logging#controlling-the-batching-settings

The error details indicate you're hitting a quota. You can learn more about quotas for Cloud Logging here: https://cloud.google.com/logging/quotas Specifically, for write requests, you'd be bumping up against the API limit, described here: https://cloud.google.com/logging/quotas#api-limits although you'd need to look in your project to see if which limit (or both) is causing the issue. You can request changes to your quota here: https://cloud.google.com/logging/quotas#api-limits. There might be ways to optimize your batching as well, but without knowing how you currently have it configured, it's difficult to provide specific guidance. Typically, the guidance is to increase the size of the batch to reduce the volume of writes. There's additional guidance here: https://cloud.google.com/java/docs/reference/gax/latest/com.google.api.gax.batching.BatchingSettings
I hope this helps!


Not overwriting channel name if recording object has the property

While I was working with a spikelgx conversion I realize that our current implementation of add_electrodes overwrites the property of channel name if this is available in the recording object (it always assign it to channel_ids.astype("str")).
I modified the logic so this does not happen and added a new test.
I also did other two things in this PR:

corrected a small bug that was showing up in warnings.
Split one of the unit tests in two as it was testing two different things in one function.
Added more descriptive names to the unittests.

While I was working with a spikelgx conversion I realize that our current implementation of add_electrodes overwrites the property of channel name if this is available in the recording object (it always assign it to channel_ids.astype("str")).

@h-mayorquin Aha, good catch


IE deprecation link forbidden

The Link "FAQ: Internet Explorer 11 deprecation for Dynamics 365 and Microsoft Power Platform Products" https://aka.ms/IEsupportDeprecationBAG returns a 403 error after logging in.

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

ID: 1a241829-ba79-0d2e-d061-cedb8978fbeb
Version Independent ID: 867a90ce-0a3e-0a82-0458-acf7e783e961
Content: Important changes (deprecations) coming in Power Apps, Power Automate and customer engagement apps - Power Platform
Content Source: power-platform/important-changes-coming.md
Service: power-platform
GitHub Login: @KumarVivek
Microsoft Alias: kvivek

@darshSWL
Please check your credentials. I tested and was able to sign in.

Why does this information require a login at all?
My credentials are okay, the login is successful, but I don't have access to this resource.


HDFS-16702. MiniDFSCluster should report cause of exception in assert…

Description of PR
When the MiniDFSClsuter detects that an exception caused an exit, it should include that exception as the cause for the AssertionError that it throws.  The current AssertError simply reports the message "Test resulted in an unexpected exit" and provides a stack trace to the location of the check for an exit exception.  This patch adds the original exception as the cause of the AssertError.
How was this patch tested?
This was used in local unit test runs during debugging.  The updated exception was particularly useful in CI unit test reports.
For code changes:

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
13m 33s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m 34s

trunk passed

+1 :green_heart:
compile
1m 45s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 40s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 26s

trunk passed

+1 :green_heart:
mvnsite
1m 51s

trunk passed

+1 :green_heart:
javadoc
1m 27s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m 49s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 41s

trunk passed

+1 :green_heart:
shadedclient
23m  3s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 22s

the patch passed

+1 :green_heart:
compile
1m 28s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 28s

the patch passed

+1 :green_heart:
compile
1m 19s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 19s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  4s

the patch passed

+1 :green_heart:
mvnsite
1m 30s

the patch passed

+1 :green_heart:
javadoc
0m 58s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m 30s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 20s

the patch passed

+1 :green_heart:
shadedclient
22m 45s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
240m 55s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m  6s

The patch does not generate ASF License warnings.

365m 28s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4680/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4680

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux de5f67e69f53 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 423ab02564c6203204709a684544e52c416232d3

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4680/1/testReport/

Max. process+thread count
3420 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4680/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m 29s

trunk passed

+1 :green_heart:
compile
1m 44s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 37s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 26s

trunk passed

+1 :green_heart:
mvnsite
1m 46s

trunk passed

+1 :green_heart:
javadoc
1m 24s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 44s

trunk passed

+1 :green_heart:
shadedclient
22m 59s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 23s

the patch passed

+1 :green_heart:
compile
1m 26s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 26s

the patch passed

+1 :green_heart:
compile
1m 21s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  1s

the patch passed

+1 :green_heart:
mvnsite
1m 28s

the patch passed

+1 :green_heart:
javadoc
0m 58s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m 31s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 19s

the patch passed

+1 :green_heart:
shadedclient
22m 34s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
237m 43s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m 15s

The patch does not generate ASF License warnings.

348m 50s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4680/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4680

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 7c8a58f67762 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 46ebe2ee0097ff476d32c14f5d2837fad54bd312

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4680/2/testReport/

Max. process+thread count
3025 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4680/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

I looked into the 2 failed unit tests, and they don't appear to be related to the change.

Merged to trunk, thanks @snmvaughan .


persistent TabView error

'package:flutter/src/rendering/box.dart': Failed assertion: line 320 pos 12: 'width > 0.0': is not true.
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case,
please help here ....

Hi @Stylacs
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


cog push error

Pushing image 'r8.im/naist4869/vits'...
Using default tag: latest
The push refers to repository [r8.im/naist4869/vits]
f2c84538b1b6: Layer already exists
......
cdd7c7392317: Layer already exists
received unexpected HTTP status: 500 Internal Server Error
https://r8.im/v2/naist4869/vits/manifests/latest
HTTP/1.1 500 Internal Server Error
Date: Mon, 28 Aug 2023 09:09:31 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 77
Connection: close
Via: 1.1 google
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v3?s=hidcyyk36sF9T2nRikzyFiOGsbYg26Ww5jdBgy2ksB9cVEreNOR42zTsuv0bdki0PZl4h3t8BXX7nr50izQTvDOONKnnB6Xs1pgfa8xicl9bDsb2XA39eUtEl3zMI3zY%2F80a"}],%22group%22:%22cf-nel%22,%22max_age%22:604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 7fdb6a77a9bb8f1d-IAD
{"errors":[{"code":"UNKNOWN","message":"Internal error. Please try again!"}]}
cog --version                                                                                 system 08:14:35
cog version 0.8.6 (built 2023-08-07T23:02:15+0000)
docker -v                                                                                 system 08:14:41
Docker version 20.10.23, build 7155243

Could anyone help me?

latest.txt


creating backend that holds spotify connection "infinitely"

Ok, so basically I'd like to achieve similar functionality as e.g. last.FM has (one time user account - spotify account tie)
From what I've read the way to do it is to use Authorization code without PKCE.
Can anyone point me any further? I have firebase authentication in my app. Should I put anything what comes from spotify into user firestore databse and then use it?

You could look into using firebase functions: https://github.com/firebase/functions-samples/tree/main/spotify-auth


Security question

I want to use s3 and I see that airflow works well with aws (ec2, s3). But s3 mean that I will have data outside. What do you have for security in airflow?

Hi @glodus,
s3 can be locked pretty tightly so that it is only readable with an access_key and a secret_key and not to the rest of the world (You would have to define the appropriate security policy for the resource (bucket, or subdirectory)). This is the setup we use. Airflow is also equipped to handle IAM roles, if your setup permits.
Let me know if you have more questions about this!

I was more thinking about what I would put on the airflow server, about the "worklow", "pipeline" or dags. It could be very unfortunate that someone understood it.
Not really related, but still a question: Do you handle LDAP authentification or perhaps flask_login already handle it ?

From our perspective security is almost an all-or-nothing as far as executing pipelines. If you do have access to an Airflow box, you pretty much have full access to all the systems Airflow interfaces with. We spoke internally about using Airflow for more sensitive datasets that not all engineers should have access to, and the solution there would be to setup an alternate Airflow environment for that purpose.
The UI is mostly a read-only UI, and there are different level of access there. It's possible to create a limited access where people can just look at pipeline definitions and how they progress.
The flask_login backdoor should allow you to do pretty much anything in terms of authentication. Our setup has a reverse proxy that takes care of ssl and ldap authentication that squeezes http headers in the request, and our airflow_login module just look for the headers to grant the right level of access. Using flask_login and ldap is probably fairly well documented. A temporary setup can be achieved with privileged users using an ssh tunnel.

Thanks.


Next release?

I'm an author of a language binding + game toolkit that incorporates both Raylib and Raygui. The README says that the master branches remain aligned, so I was wondering if that also applies to tagged releases. Since you just released Raylib 4.5, will there be a Raygui release as well?

@shelvick Yeah, I plan to release raygui 3.5 soon but I'm working in too many things and I don't know when that soon will be...
I'd like to review for raygui 3.5 the GuiSlider*(), GuiScrollBar() and GuiTextBox().


chore: bump GW API to v0.8.1

What this PR does / why we need it:
Bump Gateway API to 0.8.1
PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

@pmalek Please run also manually generating conformance report (it uses a new experimental conformance suite) to ensure that the update does not break it

@programmer04 https://github.com/Kong/kubernetes-ingress-controller/actions/runs/6253142813 has passed


materialboxed image cannot be centered

The following 3 column images ...

... will be flush left, despite their container having the center class. Removing materialboxed centers them again (but loses the materialbox). Adding this css ...
    .materialboxed{ display: inline-block; }

... lets me use materialbox while centering the images correctly, however the enlargement animation jumps in a strange way. From looking at all the different materialboxed js issues, most of which are quite basic, this code clearly could benefit from some attention.

Our center class is only a text-align: center, so if you want to use it for anything other than text like block elements you will need to add inline-block.
As for the animation, I tried doing this locally and i'm not seeing any strange jumps. Could there be anything else that is causing this issue?

it only does the weird animation for images with a small width, when u click it pushes to the left before zooming.
for larger width images its barely visible and looks almost normal.

it only does the weird animation for images with a small width, when u click it pushes to the left before zooming.
for larger width images its barely visible and looks almost normal.

I've been playing with this classes and found this issue.  Adding display: inline-block in .materialboxed does this weird animation.  I added this css to solve this.
.center .materialboxed,
.center-align .materialboxed {
    margin: 0 auto; position: relative !important;
}


Add custom-codecs to list of bundled plugins

Description
Adds the new custom-codecs plugin to the list of bundled plugins
Issues Resolved
Related #4832
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@kolchfa-aws - Can you please take a look?


Remove longer or less used aliases

What was changed

removed alias for --context-timeout
Why?

shouldn't be used much, cleaner --help output
Checklist

Closes

How was this tested:

Any docs updates needed?

I would leave only these obvious ones:
n
wid -> w
rid -> r
t
i
q
f

All the rest is non-obvious and actually very rarely used.

I would leave only these obvious ones:
n
wid -> w
rid -> r
t
i
q
f

All the rest is non-obvious and actually very rarely used.

updated


Publish new version

Can we release a new version? There have been lots of improvements since the last release.

@divyenduz We are patiently waiting for the v0.1.4 release.

I am sorry about the delay, I will do it today evening.

Couldn't get to it yesterday, today evening it is 🙏

0.2.2 is published, sorry about the delay 🙏


[PE-D][Tester A] Unclear error message for tag names

First i keyed in:  student n/John Doe id/A0123456X p/98765432<EMAIL_ADDRESS>a/311, Clementi Ave 2,  t/2, #02-25 t/friends t/owesMoney
The t/2 within the address parameter was meant to be an 'uninteded' typo by the user or a slim chance it is part of the address name.
Hence, I do not think the error message presented is the most appropraite as the user, I checked that my t/friends and t/owesMoney met the criteria.

Labels: severity.Low type.FunctionalityBug
original: jeremychiaaaaa/ped#4

As tags are required to be non empty and only alphanumeric with no spaces, we could include that under the specifications of the tag in the company and student sections.
Not sure about handling the t/ being in the address input though, as it would be considered as a tag, and fails due to the comma. Even if the comma is excluded, the space between the t/2 and the rest of the address would make AdmiNUS think a tag t/2 REST_OF_ADDRESS is being added which would similarly trigger the same error message.

I think can ignore the t/ handling in address inputs since rarely have addresses with t/


Rename 'sql' command to 'db'

All the operations supported by 'wp sql' are actually referring to the WordPress database, not to the SQL language. So, I think 'db' would be a more appropriate name:
wp db connect
wp db dump
wp db cli
wp db query

I only noticed this after reading this comment: https://github.com/andreascreten/wp-cli/issues/44#issuecomment-3330593

We can keep 'sql' as an alias, to preserve backwards compatibility.


State transition update for 0.9.0

Goal

Close #529

Progress

[x] Update state transition
[x] Unit tests
[x] e2e tests
[x] Fix current spec tests
[x] Add new spec tests

@mpetrunic regarding

Think you forgot to delete transfer stuff in db
I deleted transfer.ts insidedb/**/repositories. Is it enough? Can't find any "transfer" inside db/**/repositories anyway.


Discrepancy between CameraSensor and DepthCameraSensor

When creating a CameraSensor and DepthCameraSensor with the same properties the depth image and point cloud do not appear to be correct when comparing against the RGB Image from the CameraSensor or the scene. Each of the cylinders start at z=0 and are 1m tall with a rail on top. Eveything in the depth camera appears to be scaled and shifted up.  Any idea why the issue might be?

In addition the point cloud is not colored.


fix: allow parent() on parent()

I also fixed the index.d.ts to also export the parent() definition.
Fix #65.
Possibly fix #64.

Thanks for this PR, and I'm so sorry it went so long without review. I ported most of the changes from this PR into #73, so I will close this PR in favor of #73. Thanks for your help though, this was very helpful, and we will make sure to give you credit in our changelog.