APM agent queue/buffers increased

Describe the bug
A clear and concise description of what the bug is.
APM Server goes down for While. APM agent queue/buffers increased.please suggest,how to free that Queue From all APM Agent. I have 15 different APM Agent to only one APM Server.
Using elastic-apm-agent-1.8.0.jar, elasticapm.properties files to tomcat bin and added following to setenv.bat:CATALINA_OPTS="$CATALINA_OPTS -javaagent:/home/tomcat/elastic-apm-agent-1.8.0.jar -Delastic.apm.service_name=P_24_CA -Delastic.apm.server_url=http://IP -Delastic.apm.environment=PR -Delastic.apm.capture_body=all"

The agent will keep these events in queue until connection to the APM server is restored. The advantage of that is not losing data during short connectivity failures.
What is your concern? If it is about the amount of memory occupied by the buffer in such cases, you can reduce their size through the max_queue_size configuration.
What would be the alternative/additional feature/behaviour you wished you had?

Hi eyalkoren, my concern is to APM server is working. but in elasticsearch Apm is not created. Apm server logs getting 503 and 202 responses. Please suggest what i do now. I have more then 15 Agent configure on that APM server.
command
./apm-server test output
elasticsearch: http://IP
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: <IP_ADDRESS>
dial up... OK
TLS... WARN secure connection disabled
talk to server... OK
version: 7.3.0
elasticsearch: http://IP..
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: <IP_ADDRESS>
dial up... OK
TLS... WARN secure connection disabled
talk to server... OK
version: 7.3.0

Hi eyalkoren,
my concern is to APM server is working. but in elasticsearch Apm is not created. Apm server logs getting 503 and 202 responses. Please suggest what i do now. I have more then 15 Agent configure on that APM server.
command
./apm-server test output
elasticsearch:  http://ip/ http://IP
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: IP
dial up... OK
TLS... WARN secure connection disabled
talk to server... OK
version: 7.3.0
elasticsearch:  http://ip/ http://IP..
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: IP
dial up... OK
TLS... WARN secure connection disabled
talk to server... OK
version: 7.3.0
Thanks & Regards,
Vikas Sharma | Software Engineer | Managed Services
https://kmp.digispice.com/images/dsmail.png
https://www.digispice.com www.digispice.com
https://www.digispice.com Spice Mobility Limited
D-91, Industrial Area, Phase 7, Mohali-160055, India
Mobile: +91 96466 09361
Tel: +91
Email<EMAIL_ADDRESS>From: eyalkoren<EMAIL_ADDRESS>Sent: Sunday, August 18, 2019 6:29 PM
To: elastic/apm-agent-java
Cc: vikassharma12345; Author
Subject: Re: [elastic/apm-agent-java] APM agent queue/buffers increased (#798)
The agent will keep these events in queue until connection to the APM server is restored. The advantage of that is not losing data during short connectivity failures.
What is your concern? If it is about the amount of memory occupied by the buffer in such cases, you can reduce their size through the  https://www.elastic.co/guide/en/apm/agent/java/current/config-reporter.html#config-max-queue-size max_queue_size configuration.
What would be the alternative/additional feature/behaviour you wished you had?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/elastic/apm-agent-java/issues/798?email_source=notifications&email_token=AM5XHO4VRKDWVCZWKZIBVTDQFFBRVA5CNFSM4IMSTUK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4Q7RYQ#issuecomment-522320098 , or mute the thread https://github.com/notifications/unsubscribe-auth/AM5XHO5IZBGVXUCC7ZYFI3LQFFBRVANCNFSM4IMSTUKQ .  https://github.com/notifications/beacon/AM5XHOYXAOE26O2D63KQBE3QFFBRVA5CNFSM4IMSTUK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4Q7RYQ.gif

@vikassharma12345 this is the java agent repo. If you think there is a bug or you want to make a feature/enhancement request regarding the java agent- this is the proper place.
If this is the case, please try to make sure this is indeed a bug and not a setup problem, and if it is, make sure you provide clearer description of the problem.
So far, I didn't understand whether this is a bug or a request and even whether it is a problem with the APM server or agent...
If this is neither a bug report nor an enhancement request, but only a request for assistance, please use our forum. There, as well, we will not be able to assist if you don't provide clear description of the problem, including what setup you are using, and at least logs from APM server/agent.

ElasticSearch Index
green open .kibana                            qcymOwbiR-agbnGCO0ytEg 1 1      4 0  66.3kb  36.4kb
green open metricbeat-7.3.0-2019.08.18-000001 J-IdzmtMSnKMXPiLTG6cPw 1 1 125852 0  98.6mb  33.1mb
green open .monitoring-es-7-mb-2019.08.18     oLvxrPRlTf-IJF1zuWll5w 1 1     72 0 689.5kb 259.5kb
green open .monitoring-beats-7-2019.08.18     whVMQcOXT8C0ZqoD84bCJw 1 1     94 0 612.5kb 307.1kb
APM Server logs
2019-08-18T19:04:26.749+0530    INFO    instance/beat.go:614    Beat ID: 73f22b2d-91e7-4472-a4b2-268e415fcf25
2019-08-18T19:04:26.750+0530    INFO    [index-management]      idxmgmt/std.go:178      Set output.elasticsearch.index to 'apm-server-7.3.0' as ILM is enabled.
2019-08-18T19:04:26.750+0530    INFO    elasticsearch/client.go:170     Elasticsearch url: http://IP:9200
2019-08-18T19:04:26.750+0530    INFO    elasticsearch/client.go:170     Elasticsearch url: http://IP:9201
2019-08-18T19:04:26.754+0530    INFO    elasticsearch/client.go:743     Attempting to connect to Elasticsearch version 7.3.0
2019-08-18T19:04:26.798+0530    INFO    elasticsearch/client.go:743     Attempting to connect to Elasticsearch version 7.3.0

################### APM Server Configuration #########################
############################# APM Server ######################################
apm-server:
Defines the host and port the server is listening on.  use "unix:/path/to.sock" to listen on a unix domain socket.
host: "<IP_ADDRESS>:8200"
Maximum permitted size in bytes of a request's header accepted by the server to be processed.
#max_header_size: 1048576
Maximum idle time until the server closes a connection.
#idle_timeout: 45s
Maximum permitted duration for reading an entire request.
#read_timeout: 30s
Maximum permitted duration for writing a response.
#write_timeout: 30s
Maximum duration in seconds before releasing resources when shutting down the server.
#shutdown_timeout: 5s
Maximum allowed size in bytes of a single event
#max_event_size: 307200
#--
Maximum number of new connections to accept simultaneously (0 means unlimited)
max_connections: 0
Authorization token to be checked. If a token is set here the agents must
send their token in the following format: Authorization: Bearer .
It is recommended to use an authorization token in combination with SSL enabled,
and save the token in the apm-server keystore.
#secret_token:
Enable secure communication between APM agents and the server. By default ssl is disabled.
#ssl:
#enabled: false
# Configure a list of root certificate authorities for verifying client certificates
#certificate_authorities: []

# Path to file containing the certificate for server authentication
# Needs to be configured when ssl is enabled
#certificate: ''

# Path to file containing server certificate key
# Needs to be configured when ssl is enabled
#key: ''

# Optional configuration options for ssl communication

# Passphrase for decrypting the Certificate Key.
# It is recommended to use the provided keystore instead of entering the passphrase in plain text.
#key_passphrase: ''

# List of supported/valid protocol versions. By default TLS versions 1.1 up to 1.2 are enabled.
#supported_protocols: [TLSv1.1, TLSv1.2]

# Configure cipher suites to be used for SSL connections
#cipher_suites: []

# Configure curve types for ECDHE based cipher suites
#curve_types: []

# Configure which type of client authentication is supported.
# Options are `none`, `optional`, and `required`. Default is `optional`.
#client_authentication: "optional"

rum:
# To enable real user monitoring (RUM) support set this to true.
enabled: false
#event_rate:

  # Defines the maximum amount of events allowed to be sent to the APM Server RUM
  # endpoint per IP per second. Defaults to 300.
  #limit: 300

  # An LRU cache is used to keep a rate limit per IP for the most recently seen IPs.
  # This setting defines the number of unique IPs that can be tracked in the cache.
  # Sites with many concurrent clients should consider increasing this limit. Defaults to 1000.
  #lru_size: 1000

#-- General RUM settings

# Comma separated list of permitted origins for real user monitoring.
# User-agents will send an origin header that will be validated against this list.
# An origin is made of a protocol scheme, host and port, without the url path.
# Allowed origins in this setting can have * to match anything (eg.: http://*.example.com)
# If an item in the list is a single '*', everything will be allowed
#allow_origins : ['*']

# Regexp to be matched against a stacktrace frame's `file_name` and `abs_path` attributes.
# If the regexp matches, the stacktrace frame is considered to be a library frame.
#library_pattern: "node_modules|bower_components|~"

# Regexp to be matched against a stacktrace frame's `file_name`.
# If the regexp matches, the stacktrace frame is not used for calculating error groups.
# The default pattern excludes stacktrace frames that have a filename starting with '/webpack'
#exclude_from_grouping: "^/webpack"

# If a source map has previously been uploaded, source mapping is automatically applied
# to all error and transaction documents sent to the RUM endpoint.
#source_mapping:

  # Source maps are always fetched from Elasticsearch, by default using the output.elasticsearch configuration.
  # A different instance must be configured when using any other output.
  # This setting only affects sourcemap reads - the output determines where sourcemaps are written.
  #elasticsearch:
    # Array of hosts to connect to.
    # Scheme and port can be left out and will be set to the default (http and 9200)
    # In case you specify and additional path, the scheme is required: http://localhost:9200/path
    # IPv6 addresses should always be defined as: https://[2001:db8::1]:9200
    # hosts: ["localhost:9200"]

    # Optional protocol and basic auth credentials.
    #protocol: "https"
    #username: "elastic"
    #password: "changeme"

  # The `cache.expiration` determines how long a source map should be cached before fetching it again from Elasticsearch.
  # Note that values configured without a time unit will be interpreted as seconds.
  #cache:
    #expiration: 5m

  # Source maps are stored in a separate index.
  # If the default index pattern for source maps at 'outputs.elasticsearch.indices'
  # is changed, a matching index pattern needs to be specified here.
  #index_pattern: "apm-*-sourcemap*"

If set to true, APM Server augments data received by the agent with the original IP of the backend server,
or the IP and User Agent of the real user (RUM requests). It defaults to true.
#capture_personal_data: true
golang expvar support - https://golang.org/pkg/expvar/
#expvar:
# Set to true to expose expvar
#enabled: false
# Url to expose expvar
#url: "/debug/vars"

Instrumentation support for the server's HTTP endpoints and event publisher.
#instrumentation:
# Set to true to enable instrumentation of the APM Server itself.
#enabled: false
# Environment in which the APM Server is running on (eg: staging, production, etc.)
#environment: ""
# Remote hosts to report instrumentation results to.
#hosts:
#  - http://remote-apm-server:8200
# Remote apm-servers' secret_token
#secret_token:
A pipeline is a definition of processors applied to documents when writing them to Elasticsearch.
Using pipelines involves two steps:
(1) registering a pipeline
(2) applying a pipeline during data ingestion (see output.elasticsearch.pipelines)

You can manually register pipelines, or use this configuration option to ensure
pipelines are loaded and registered at the configured Elasticsearch instances.
Automatic pipeline registration requires
* output.elasticsearch to be enabled and configured.
* having the required Elasticsearch Processor Plugins installed.
APM Server default pipelines require you to have the Ingest User Agent Plugin installed.
Find the default pipeline configuration at ingest/pipeline/definition.json.

#register.ingest.pipeline:
# Registers pipeline definitions in Elasticsearch on APM Server startup. Defaults to false.
#enabled: false
# Overwrites existing pipeline definitions in Elasticsearch. Defaults to true.
#overwrite: false

When ilm is set to true the APM Server will take care of ILM setup.
Configurations in output.elasticsearch.index and output.elasticsearch.indices sections will be ignored
ilm can only be enabled for output.elasticsearch
#ilm:
#enabled: false
#================================ General ======================================
Internal queue configuration for buffering events to be published.
#queue:
Queue type by name (default 'mem')
The memory queue will present all available events (up to the outputs
bulk_max_size) to the output, the moment the output is ready to server
another batch of events.
#mem:
# Max number of events the queue can buffer.
events: 5120
# Hints the minimum number of events stored in the queue,
# before providing a batch of events to the outputs.
# The default value is set to 2048.
# A value of 0 ensures events are immediately available
# to be sent to the outputs.
flush.min_events: 2048

# Maximum duration after which events are available to the outputs,
# if the number of events stored in the queue is < min_flush_events.
flush.timeout: 1s

Sets the maximum number of CPUs that can be executing simultaneously. The
default is the number of logical CPUs available in the system.
#max_procs:
#============================== Template =====================================
A template is used to set the mapping in Elasticsearch
By default template loading is enabled and the template is loaded.
These settings can be adjusted to load your own template or overwrite existing ones.
Set to false to disable template loading.
setup.template.enabled: true
Template name. By default the template name is "apm-%{[observer.version]}"
The template name and pattern has to be set in case the elasticsearch index pattern is modified.
#setup.template.name: "apm-%{[observer.version]}"
Template pattern. By default the template pattern is "apm-%{[observer.version]}-*" to apply to the default index settings.
The first part is the version of apm-server and then -* is used to match all daily indices.
The template name and pattern has to be set in case the elasticsearch index pattern is modified.
#setup.template.pattern: "apm-%{[observer.version]}-*"
Path to fields.yml file to generate the template
#setup.template.fields: "${path.config}/fields.yml"
Overwrite existing template
setup.template.overwrite: false
Elasticsearch template settings
setup.template.settings:
A dictionary of settings to place into the settings.index dictionary
of the Elasticsearch template. For more details, please check
https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html
index:
number_of_shards: 4
codec: best_compression
number_of_routing_shards: 30
mapping.total_fields.limit: 2000
#============================= Elastic Cloud ==================================
These settings simplify using APM Server with the Elastic Cloud (https://cloud.elastic.co/).
The cloud.id setting overwrites the output.elasticsearch.hosts option.
You can find the cloud.id in the Elastic Cloud web UI.
#cloud.id:
The cloud.auth setting overwrites the output.elasticsearch.username and
output.elasticsearch.password settings. The format is <user>:<pass>.
#cloud.auth:
#================================ Outputs =====================================
Configure what output to use when sending the data collected by apm-server.
#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
Array of hosts to connect to.
Scheme and port can be left out and will be set to the default (http and 9200)
In case you specify and additional path, the scheme is required: http://localhost:9200/path
IPv6 addresses should always be defined as: https://[2001:db8::1]:9200
hosts: ["<IP_ADDRESS>:9200","<IP_ADDRESS>:9201"]
Boolean flag to enable or disable the output module.
enabled: true
Set gzip compression level.
#compression_level: 0
Optional protocol and basic auth credentials.
#protocol: "https"
#username: "elastic"
#password: "changeme"
Dictionary of HTTP parameters to pass within the url with index operations.
#parameters:
#param1: value1
#param2: value2
Number of workers per Elasticsearch host.
#worker: 1
By using the configuration below, apm documents are stored to separate indices,
depending on their processor.event:
- error
- transaction
- span
- sourcemap

The indices are all prefixed with apm-%{[observer.version]}.
To allow managing indices based on their age, all indices (except for sourcemaps)
end with the information of the day they got indexed.
e.g. "apm-6.3.0-transaction-2018.03.20"

Be aware that you can only specify one Elasticsearch template.
In case you modify the index patterns you must also update those configurations accordingly,
as they need to be aligned:
* setup.template.name
* setup.template.pattern
#index: "apm-%{[observer.version]}-%{+yyyy.MM.dd}"
#indices:
- index: "apm-%{[observer.version]}-sourcemap"
when.contains:
processor.event: "sourcemap"

- index: "apm-%{[observer.version]}-error-%{+yyyy.MM.dd}"
when.contains:
processor.event: "error"

- index: "apm-%{[observer.version]}-transaction-%{+yyyy.MM.dd}"
when.contains:
processor.event: "transaction"

- index: "apm-%{[observer.version]}-span-%{+yyyy.MM.dd}"
when.contains:
processor.event: "span"

- index: "apm-%{[observer.version]}-metric-%{+yyyy.MM.dd}"
when.contains:
processor.event: "metric"

- index: "apm-%{[observer.version]}-onboarding-%{+yyyy.MM.dd}"
when.contains:
processor.event: "onboarding"
A pipeline is a definition of processors applied to documents when writing them to Elasticsearch.
APM Server comes with a default pipeline definition, located at ingest/pipeline/definition.json.
Pipelines are disabled by default. To make use of them you have to:
(1) ensure pipelines are registered in Elasticsearch, see apm-server.register.ingest.pipeline
(2) enable the following:
#pipelines:
#- pipeline: "apm"
Optional HTTP Path
#path: "/elasticsearch"
Custom HTTP headers to add to each request
#headers:
X-My-Header: Contents of the header
Proxy server url
#proxy_url: http://proxy:3128
The number of times a particular Elasticsearch index operation is attempted. If
the indexing operation doesn't succeed after this many retries, the events are
dropped. The default is 3.
#max_retries: 3
The maximum number of events to bulk in a single Elasticsearch bulk API index request.
The default is 50.
bulk_max_size: 5120
The number of seconds to wait before trying to reconnect to Elasticsearch
after a network error. After waiting backoff.init seconds, apm-server
tries to reconnect. If the attempt fails, the backoff timer is increased
exponentially up to backoff.max. After a successful connection, the backoff
timer is reset. The default is 1s.
#backoff.init: 1s
The maximum number of seconds to wait before attempting to connect to
Elasticsearch after a network error. The default is 60s.
#backoff.max: 60s
Configure http request timeout before failing an request to Elasticsearch.
#timeout: 90
Enable custom SSL settings. Set to false to ignore custom SSL settings for secure communication.
#ssl.enabled: true
Optional SSL configuration options. SSL is off by default, change the protocol option if you want to enable https.
Configure SSL verification mode. If none is configured, all server hosts
and certificates will be accepted. In this mode, SSL based connections are
susceptible to man-in-the-middle attacks. Use only for testing. Default is
full.
#ssl.verification_mode: full
List of supported/valid TLS versions. By default all TLS versions 1.0 up to
1.2 are enabled.
#ssl.supported_protocols: [TLSv1.0, TLSv1.1, TLSv1.2]
List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
Optional passphrase for decrypting the Certificate Key.
It is recommended to use the provided keystore instead of entering the passphrase in plain text.
#ssl.key_passphrase: ''
Configure cipher suites to be used for SSL connections
#ssl.cipher_suites: []
Configure curve types for ECDHE based cipher suites
#ssl.curve_types: []
Configure what types of renegotiation are supported. Valid options are
never, once, and freely. Default is never.
#ssl.renegotiation: never
#----------------------------- Console output ---------------------------------
#output.console:
Boolean flag to enable or disable the output module.
#enabled: false
Configure JSON encoding
#codec.json:
# Pretty-print JSON event
#pretty: false
# Configure escaping HTML symbols in strings.
#escape_html: false

#----------------------------- Logstash output ---------------------------------
#output.logstash:
Boolean flag to enable or disable the output module.
#enabled: false
The Logstash hosts
#hosts: ["localhost:5044"]
Number of workers per Logstash host.
#worker: 1
Set gzip compression level.
#compression_level: 3
Configure escaping html symbols in strings.
#escape_html: true
Optional maximum time to live for a connection to Logstash, after which the
connection will be re-established.  A value of 0s (the default) will
disable this feature.

Not yet supported for async connections (i.e. with the "pipelining" option set)
#ttl: 30s
Optional load balance the events between the Logstash hosts. Default is false.
#loadbalance: false
Number of batches to be sent asynchronously to Logstash while processing
new batches.
#pipelining: 2
If enabled only a subset of events in a batch of events is transferred per
group.  The number of events to be sent increases up to bulk_max_size
if no error is encountered.
#slow_start: false
The number of seconds to wait before trying to reconnect to Logstash
after a network error. After waiting backoff.init seconds, apm-server
tries to reconnect. If the attempt fails, the backoff timer is increased
exponentially up to backoff.max. After a successful connection, the backoff
timer is reset. The default is 1s.
#backoff.init: 1s
The maximum number of seconds to wait before attempting to connect to
Logstash after a network error. The default is 60s.
#backoff.max: 60s
Optional index name. The default index name is set to apm
in all lowercase.
#index: 'apm'
SOCKS5 proxy server URL
#proxy_url: socks5://user:password@socks5-server:2233
Resolve names locally when using a proxy server. Defaults to false.
#proxy_use_local_resolver: false
Enable SSL support. SSL is automatically enabled if any SSL setting is set.
#ssl.enabled: false
Optional SSL configuration options. SSL is off by default.
Configure SSL verification mode. If none is configured, all server hosts
and certificates will be accepted. In this mode, SSL based connections are
susceptible to man-in-the-middle attacks. Use only for testing. Default is
full.
#ssl.verification_mode: full
List of supported/valid TLS versions. By default all TLS versions 1.0 up to
1.2 are enabled.
#ssl.supported_protocols: [TLSv1.0, TLSv1.1, TLSv1.2]
List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
Optional passphrase for decrypting the Certificate Key.
It is recommended to use the provided keystore instead of entering the passphrase in plain text.
#ssl.key_passphrase: ''
Configure cipher suites to be used for SSL connections
#ssl.cipher_suites: []
Configure curve types for ECDHE based cipher suites
#ssl.curve_types: []
Configure what types of renegotiation are supported. Valid options are
never, once, and freely. Default is never.
#ssl.renegotiation: never
#------------------------------- Kafka output ----------------------------------
#output.kafka:
Boolean flag to enable or disable the output module.
#enabled: false
The list of Kafka broker addresses from where to fetch the cluster metadata.
The cluster metadata contain the actual Kafka brokers events are published
to.
#hosts: ["localhost:9092"]
The Kafka topic used for produced events. The setting can be a format string
using any event field. To set the topic from document type use %{[type]}.
#topic: beats
The Kafka event key setting. Use format string to create unique event key.
By default no event key will be generated.
#key: ''
The Kafka event partitioning strategy. Default hashing strategy is hash
using the output.kafka.key setting or randomly distributes events if
output.kafka.key is not configured.
#partition.hash:
# If enabled, events will only be published to partitions with reachable
# leaders. Default is false.
#reachable_only: false
# Configure alternative event field names used to compute the hash value.
# If empty `output.kafka.key` setting will be used.
# Default value is empty list.
#hash: []

Authentication details. Password is required if username is set.
#username: ''
#password: ''
Kafka version libbeat is assumed to run against. Defaults to the "1.0.0".
#version: '1.0.0'
Configure JSON encoding
#codec.json:
# Pretty print json event
#pretty: false
# Configure escaping html symbols in strings.
#escape_html: true

Metadata update configuration. Metadata do contain leader information
deciding which broker to use when publishing.
#metadata:
# Max metadata request retry attempts when cluster is in middle of leader
# election. Defaults to 3 retries.
#retry.max: 3
# Waiting time between retries during leader elections. Default is 250ms.
#retry.backoff: 250ms

# Refresh metadata interval. Defaults to every 10 minutes.
#refresh_frequency: 10m

The number of concurrent load-balanced Kafka output workers.
#worker: 1
The number of times to retry publishing an event after a publishing failure.
After the specified number of retries, the events are typically dropped.
Set max_retries to a value less than 0 to retry
until all events are published. The default is 3.
#max_retries: 3
The maximum number of events to bulk in a single Kafka request. The default
is 2048.
#bulk_max_size: 2048
The number of seconds to wait for responses from the Kafka brokers before
timing out. The default is 30s.
#timeout: 30s
The maximum duration a broker will wait for number of required ACKs. The
default is 10s.
#broker_timeout: 10s
The number of messages buffered for each Kafka broker. The default is 256.
#channel_buffer_size: 256
The keep-alive period for an active network connection. If 0s, keep-alives
are disabled. The default is 0 seconds.
#keep_alive: 0
Sets the output compression codec. Must be one of none, snappy and gzip. The
default is gzip.
#compression: gzip
Set the compression level. Currently only gzip provides a compression level
between 0 and 9. The default value is chosen by the compression algorithm.
#compression_level: 4
The maximum permitted size of JSON-encoded messages. Bigger messages will be
dropped. The default value is 1000000 (bytes). This value should be equal to
or less than the broker's message.max.bytes.
#max_message_bytes: 1000000
The ACK reliability level required from broker. 0=no response, 1=wait for
local commit, -1=wait for all replicas to commit. The default is 1.  Note:
If set to 0, no ACKs are returned by Kafka. Messages might be lost silently
on error.
#required_acks: 1
The configurable ClientID used for logging, debugging, and auditing
purposes.  The default is "beats".
#client_id: beats
Enable SSL support. SSL is automatically enabled if any SSL setting is set.
#ssl.enabled: false
Optional SSL configuration options. SSL is off by default.
Configure SSL verification mode. If none is configured, all server hosts
and certificates will be accepted. In this mode, SSL based connections are
susceptible to man-in-the-middle attacks. Use only for testing. Default is
full.
#ssl.verification_mode: full
List of supported/valid TLS versions. By default all TLS versions 1.0 up to
1.2 are enabled.
#ssl.supported_protocols: [TLSv1.0, TLSv1.1, TLSv1.2]
List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
Optional passphrase for decrypting the Certificate Key.
It is recommended to use the provided keystore instead of entering the passphrase in plain text.
#ssl.key_passphrase: ''
Configure cipher suites to be used for SSL connections
#ssl.cipher_suites: []
Configure curve types for ECDHE based cipher suites
#ssl.curve_types: []
Configure what types of renegotiation are supported. Valid options are
never, once, and freely. Default is never.
#ssl.renegotiation: never
#================================= Paths ======================================
The home path for the apm-server installation. This is the default base path
for all other path settings and for miscellaneous files that come with the
distribution.
If not set by a CLI flag or in the configuration file, the default for the
home path is the location of the binary.
#path.home:
The configuration path for the apm-server installation. This is the default
base path for configuration files, including the main YAML configuration file
and the Elasticsearch template file. If not set by a CLI flag or in the
configuration file, the default for the configuration path is the home path.
#path.config: ${path.home}
The data path for the apm-server installation. This is the default base path
for all the files in which apm-server needs to store its data. If not set by a
CLI flag or in the configuration file, the default for the data path is a data
subdirectory inside the home path.
#path.data: ${path.home}/data
The logs path for an apm-server installation. If not set by a CLI flag or in the
configuration file, the default is a logs subdirectory inside the home path.
#path.logs: ${path.home}/logs
#================================ Logging ======================================

There are three options for the log output: syslog, file, stderr.
Under Windows systems, the log files are per default sent to the file output,
under all other system per default to syslog.
Sets log level. The default log level is info.
Available log levels are: error, warning, info, debug
#logging.level: info
Enable debug output for selected components. To enable all selectors use ["*"]
Other available selectors are "beat", "publish", "service"
Multiple selectors can be chained.
#logging.selectors: [ ]
Send all logging output to syslog. The default is false.
#logging.to_syslog: true
If enabled, apm-server periodically logs its internal metrics that have changed
in the last period. For each metric that changed, the delta from the value at
the beginning of the period is logged. Also, the total values for
all non-zero internal metrics are logged on shutdown. The default is false.
#logging.metrics.enabled: false
The period after which to log the internal metrics. The default is 30s.
#logging.metrics.period: 30s
Logging to rotating files. Set logging.to_files to false to disable logging to
files.
#logging.to_files: true
#logging.files:
Configure the path where the logs are written. The default is the logs directory
under the home path (the binary location).
#path: /var/log/apm-server
The name of the files where the logs are written to.
#name: apm-server
Configure log file size limit. If limit is reached, log file will be
automatically rotated
#rotateeverybytes: 10485760 # = 10MB
Number of rotated log files to keep. Oldest files will be deleted first.
#keepfiles: 7
The permissions mask to apply when rotating log files. The default value is 0600.
Must be a valid Unix-style file permissions mask expressed in octal notation.
#permissions: 0600
Enable log file rotation on time intervals in addition to size-based rotation.
Intervals must be at least 1s. Values of 1m, 1h, 24h, 724h, 3024h, and 365*24h
are boundary-aligned with minutes, hours, days, weeks, months, and years as
reported by the local system clock. All other intervals are calculated from the
Unix epoch. Defaults to disabled.
#interval: 0
Set to true to log messages in json format.
#logging.json: false
#================================ HTTP Endpoint ======================================

apm-server can expose internal metrics through a HTTP endpoint. For security
reasons the endpoint is disabled by default. This feature is currently experimental.
Stats can be access through http://localhost:5066/stats . For pretty JSON output
append ?pretty to the URL.
Defines if the HTTP endpoint is enabled.
http.enabled: true
The HTTP endpoint will bind to this hostname or IP address. It is recommended to use only localhost.
http.host: <IP_ADDRESS>
Port on which the HTTP endpoint will bind. Default is 5066.
http.port: 5066
#============================== X-pack Monitoring ===============================
APM server can export internal metrics to a central Elasticsearch monitoring
cluster.  This requires x-pack monitoring to be enabled in Elasticsearch.  The
reporting is disabled by default.
Set to true to enable the monitoring reporter.
monitoring.enabled: true
Most settings from the Elasticsearch output are accepted here as well.
Note that these settings should be configured to point to your Elasticsearch monitoring cluster.
Any setting that is not set is automatically inherited from the Elasticsearch
output configuration. This means that if you have the Elasticsearch output configured,
you can simply uncomment the following line.
monitoring.elasticsearch:
Optional protocol and basic auth credentials.
#protocol: "https"
#username: "apm_system"
#password: ""
Array of hosts to connect to.
Scheme and port can be left out and will be set to the default (http and 9200)
In case you specify and additional path, the scheme is required: http://localhost:9200/path
IPv6 addresses should always be defined as: https://[2001:db8::1]:9200
hosts: ["<IP_ADDRESS>:9200","<IP_ADDRESS>:9201"]
Set gzip compression level.
#compression_level: 0
Dictionary of HTTP parameters to pass within the URL with index operations.
#parameters:
#param1: value1
#param2: value2
Custom HTTP headers to add to each request
#headers:
X-My-Header: Contents of the header
Proxy server url
#proxy_url: http://proxy:3128
The number of times a particular Elasticsearch index operation is attempted. If
the indexing operation doesn't succeed after this many retries, the events are
dropped. The default is 3.
#max_retries: 3
The maximum number of events to bulk in a single Elasticsearch bulk API index request.
The default is 50.
#bulk_max_size: 50
The number of seconds to wait before trying to reconnect to Elasticsearch
after a network error. After waiting backoff.init seconds, apm-server
tries to reconnect. If the attempt fails, the backoff timer is increased
exponentially up to backoff.max. After a successful connection, the backoff
timer is reset. The default is 1s.
#backoff.init: 1s
The maximum number of seconds to wait before attempting to connect to
Elasticsearch after a network error. The default is 60s.
#backoff.max: 60s
Configure HTTP request timeout before failing an request to Elasticsearch.
#timeout: 90
Enable custom SSL settings. Set to false to ignore custom SSL settings for secure communication.
#ssl.enabled: true
Optional SSL configuration options. SSL is off by default, change the protocol option if you want to enable https.
Configure SSL verification mode. If none is configured, all server hosts
and certificates will be accepted. In this mode, SSL based connections are
susceptible to man-in-the-middle attacks. Use only for testing. Default is
full.
#ssl.verification_mode: full
List of supported/valid TLS versions. By default all TLS versions 1.0 up to
1.2 are enabled.
#ssl.supported_protocols: [TLSv1.0, TLSv1.1, TLSv1.2]
List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
Optional passphrase for decrypting the Certificate Key.
It is recommended to use the provided keystore instead of entering the passphrase in plain text.
#ssl.key_passphrase: ''
Configure cipher suites to be used for SSL connections
#ssl.cipher_suites: []
Configure curve types for ECDHE based cipher suites
#ssl.curve_types: []
Configure what types of renegotiation are supported. Valid options are
never, once, and freely. Default is never.
#ssl.renegotiation: never
#metrics.period: 10s
#state.period: 1m

Sorry, I am not able to assist.
Please describe a problem and add only errors from APM server and agent logs in the forum.
Closing this issue.

Hi eyalkoren,
Concern

Apm server is creating index in  ElasticSearch.
Apm server logs getting 503 and 202 responses with error Queue is Full from APM agent.
Without ElasticSearch index not get APM in Kibana.

Apm server is creating index in ElasticSearch.
Apm server logs getting 503 and 202 responses with error Queue is Full from APM agent.
Without ElasticSearch index not get APM in Kibana.

Thanks & Regards,
Vikas Sharma | Software Engineer | Managed Services
https://kmp.digispice.com/images/dsmail.png
https://www.digispice.com www.digispice.com
https://www.digispice.com Spice Mobility Limited
D-91, Industrial Area, Phase 7, Mohali-160055, India
Mobile: +91 96466 09361
Tel: +91
Email<EMAIL_ADDRESS>From: eyalkoren<EMAIL_ADDRESS>Sent: Sunday, August 18, 2019 8:08 PM
To: elastic/apm-agent-java
Cc: vikassharma12345; Mention
Subject: Re: [elastic/apm-agent-java] APM agent queue/buffers increased (#798)
Sorry, I am not able to assist.
Please describe a problem and add only errors from APM server and agent logs in the forum.
Closing this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/elastic/apm-agent-java/issues/798?email_source=notifications&email_token=AM5XHO73AMQYLI3HV2PXY6DQFFNFHA5CNFSM4IMSTUK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4RBLGY#issuecomment-522327451 , or mute the thread https://github.com/notifications/unsubscribe-auth/AM5XHO4IMENBJI23BHKUVO3QFFNFHANCNFSM4IMSTUKQ .  https://github.com/notifications/beacon/AM5XHO4T6FIUHAKJK5IVHADQFFNFHA5CNFSM4IMSTUK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4RBLGY.gif


fix: solve type errors in ui lib

I was trying to help solve the type issues which I didn't however I think these updates should be made to help banish dist-all

I'll include anything I missed from here in my branch.


Pre-fill dictionary transforms with keys=['image', 'label']

Logic is: it is easier to remove this, then to add. What should be added is less intuitive then what should be removed.

Force push does a plain rebase.

I just did another plain rebase.


Feature | Add Symbols Particles to the Main Page

Add some awesome symbols particles to the main home page.
What to do:

Make sure to have different symbols particles and choose the best color combination or white.
Can use the particles.js library for this, which is already added in /js/libraries directory.
Create a particles.app.js file for the configuration of the particles js and use this file for awesome customization.
Make the particles div below of every content and fixed its position while scrolling.
And make other necessary changes that fit in and make UI be good.

I want to work on this issue under JWOC

Go for it @vish-han

I want to work under JWOC

Thank @imniladri for assigning me the issue

@vish-han Are still working on it. Please comment on discord.


Install MSSQL on php-worker + fixes smb error

Description
Mssql wasn't provided with php worker
Smb install had a duplicate on apt-get install
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue).
[x] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Relates #3047
Sorry for the inconvenience @dqfan2012

#3048 does it another way.
I'm using my config in a personnal project and is working fine

I also added Mongo db username + password which wasn't provided

@bestlong I saw you merged the other version of php-worker MSSQL, do you want to adapt this one to remove php worker MSSQL ?


Update references to XMLDOM?

Not an issue, but a question/suggestion
xpath documentation and dependencies refer to older, unmaintained XMLDOM version 0.1.19 from
https://github.com/jindw/xmldom
But XMLDOM development proceeds on new location, currently version 0.4.0
https://github.com/xmldom/xmldom
I know xpath is engine agnostic, but maybe it would make sense to update references and dependencies to active xmldom. Any known issues?

Thanks!


fix: reset stale unmountedRef in suspense

Fix #1836

key changes from foo to ''
https://github.com/vercel/swr/blob/01e05946e22edbfbfd63eff9b8617d7c6283992c/src/use-swr.ts#L461
Then key changes from '' to bar
In suspense mode,
https://github.com/vercel/swr/blob/01e05946e22edbfbfd63eff9b8617d7c6283992c/src/use-swr.ts#L433
would not be executed
So fetcher will not have chance to update the cache
https://github.com/vercel/swr/blob/01e05946e22edbfbfd63eff9b8617d7c6283992c/src/use-swr.ts#L134-L141

Makes total sense, thank you!


Show message if we try to edit a non-existent object

(not sure if this is core or datatable or formbuilder ?)
Example: If you call
administration/owners/1034240/edit
you get an empty screen. It would be better if you get a message and you get redirected to last / overview screen?
Second question (was to reason to find this error):

It would be nice if we can to something like this:

public function edit(Owner $owner, OwnerForm $form)
    {
        if ($owner.xx != yy) {
            // return redirect to table and show message
        }
        return ['form' => $form->edit($owner)];
    }

I could not manage this?

it's related to the errorHandler. I will take care of it.

thx, can you check my second question for a second pls?

Please open a new ticket on formbuilder and give me some details about what you're trying to achieve and what the context is. There might be already something in place that you can use for this.


Fix SubFlow state properties

Signed-off-by: Tihomir Surdilovic<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please specify parts this PR updates:

[ x] Specification
[ ] Schema
[ ] Examples
[ ] Extensions
[ ] Roadmap
[ ] Use Cases
[ ] Community
[ ] TCK
[ ] Other

What this PR does / why we need it:
Fixes SubFlow state properties descriptions
Special notes for reviewers:
Additional information (if needed):

@mswiderski fixes :)

this is actually a bug in our current documentation, so it needs to be fixed and also backported to 0.6.x as well
i will go ahead and merge as this is pretty bad error


[hotfix] Run schema coordinator logic asynchronously to avoid blocking the main thread

This tweaks SchemaRegistry coordinator to let it handle requests / trigger checkpoints in background threads to avoid blocking the main thread.
This also adds E2e test case running on various parallelisms.

@loserwang1024 Would you like to review this PR when you have time ?


[File Locksmith] Add Windows11 (tier1) context menu

Summary of the Pull Request

PR Checklist

[x] Closes: #21648
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

Does this PR introduces a new appx package? What is the package name?

Does this PR introduces a new appx package? What is the package name?

Yes - FileLocksmithContextMenuPackage. If you are thinking of PowerToys prefix missing to all appx packages, I'll open a PR to fix that :) I forgot about that :)

The tier 1 context menu doesn't react to the "show in extended menu only" setting, like the tier 1 powerrename entry does.

Fixed

It doesn't appear on right-clicking a drive in File Explorer like the old context menu does.

According to docs https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/integrate-packaged-app-with-file-explorer#register-the-shell-extension and https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-desktop4-itemtype this is not possible. ItemType could be either specific extension, All file types (*) or Directory/Directory background. We already use * for all file types and directory.

Does this PR introduces a new appx package? What is the package name?

Yes - FileLocksmithContextMenuPackage. If you are thinking of PowerToys prefix missing to all appx packages, I'll open a PR to fix that :) I forgot about that :)
Edit: I'm talking about actual msix file names. Package name is already prefixed

If you feel the msix file names are important you can do this. For me only the Package names are important.


[CLEANUP] Normalize the composer.json with composer-normalize

coverage: 38.622%. remained the same
when pulling 891f0b91c80f4bb9ddfad222d50355f78c7e0f76 on cleanup/normalize
into 23f406137633e5b3a9fbfb640bd51c872966cf2d on main.


[serverless-apollo-contentful] Final cleanup based on demo feedback

Description
After our demo of the kit, there are a few minor items of cleanup that need to take place. They are as follows:

[x] Change name to "Serverless Framework"
[ ] Change name consistently to "Apollo Server"
[x] Remove double quotes from .env file AWS credentials
[x] Update README to include the fact that both migrations exist
[x] Change Docker commands to be reduced from 4 down to 3 Docker commands (up, pause, down)
[ ] Does the Contentful system not return pagination by their API? If pagination isn't available, note in README. If so, refactor to use it.
[x] Check and confirm that the mutations (update) are working correctly. There was a potential bug during the demo.
[x] In the graphql.ts file, SLS deploy use --stage flag for Serverless Framework
[x] Remove line 32
[x] pnpm run format changes files
[x] Update tests so no errors are returned

Apollo doesn't seem to prefer Relay-based pagination when working with offsets. The documentation mentions to do the implementation as is so it plays nicely with Apollo-client.
It would not be impossible to change the structure as Contentful does allow us to read the total amount of entries available. A PoC would be needed to see if Apollo client plays nicely with Relay-based pagination and offsets.
@kenslachtajr , what are your thoughts on this?

@mbicknese, it appears that we have our answer after the demo today.


filter the jobs table by some key then run "simple" pipeline- ui craches

in the search field of the jobs page, filter the table by some word, "simple"
than go to pipelines page and run the simple pipeline (it only occurs with the simple pipeline, maybe becouse its last i dont sure)
after running the pipeline go back to the jobs page and the page craches

From the error, you hadn't a connection on trying to running a pipeline,
I couldn't reproduce the error.


update theming docs to be more clear about how to structure your theme file to be usable across custom components

If I took this code https://github.com/angular/material2/blob/master/docs/theming.md#defining-a-custom-theme and put it into _custom-theme.scss and included it in my main styles file and then imported it into my components like as shown here https://github.com/angular/material2/blob/master/docs/theming-your-components.md#using-colors-from-a-pallete
it would generate unnecessary(since they are already in the main file) classes, like elevation, inside my components's encapsulated css.. which is bad.
The way I see it, your _custom-theme.scss should import and contain something along these lines
@import '@angular/material/core/theming/theming';

$custom-color-primary: md-palette($md-blue);
$custom-color-accent:  md-palette($md-pink, A200, A100, A400);
$custom-color-warn:    md-palette($md-red);

$custom-theme: md-light-theme($color-primary, $color-accent, $color-warn);

the main style file should have
@import '@angular/material/core/theming/all-theme';

@include md-core();

@import './custom-theme';

@include angular-material-theme($custom-theme);

thanks to this, you'd be able to import _custom-theme.scss anywhere and be able to use palette functions as well as your variables without it generating any duplicated material classes

This is fixed here: https://material.angular.io/guide/theming. This guide is really easy and I got started in 60 seconds.
Happy holidays!

why builder say 'No mixin named md-core'?

You need to update to the latest version, and put a scss file in your src dir, not @angular/material. Make sure to add the sass file to angularcli.json
On Feb 8, 2017, 11:04 PM -0500, 김동욱<EMAIL_ADDRESS>wrote:

why builder say 'No mixin named md-core'?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/angular/material2/issues/1786#issuecomment-278541475), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIEnGoXQ_3-SoSKl-2x1ty8V-8P-mKks5rapA-gaJpZM4KthhC).

i am on latest of master branch, and it seemes that the prefiex of names are changed from 'md' to 'mat'

/* angular material theming */
@import '~@angular/material/core/theming/all-theme';
@include mat-core();

$app-primary: mat-palette($mat-blue, A400, A100, A700);
$app-accent:  mat-palette($mat-pink, A200, A100, A400);
$app-warn:    mat-palette($mat-red);
$app-theme: mat-light-theme($app-primary, $app-accent, $app-warn);
@include angular-material-theme($app-theme);

now it works!

Interchangeable
On Feb 8, 2017, 11:08 PM -0500, 김동욱<EMAIL_ADDRESS>wrote:

i am on latest of master branch, and it seemes that the prefiex of names are changed from 'md' to 'mat'
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/angular/material2/issues/1786#issuecomment-278541951), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIElAWzShhC4MUA2JgP5z3URtTQC3Nks5rapEvgaJpZM4KthhC).

really? thank you for your help!

Whatever works.
Wilson Hobbs
CEO/Founder/Developer at Canal
11th Grade at The Lovett School
Personal Information
E-mail<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Website: www.wilsonhobbs.com (https://www.wilsonhobbs.com)
Twitter/Instagram/Facebook: @wbhob
Canal Information
E-mail<EMAIL_ADDRESS>Web: www.getcanal.com (https://www.getcanal.com/)
Twitter/Instagram/Facebook: @getcanal
On Feb 8, 2017, 11:08 PM -0500, 김동욱<EMAIL_ADDRESS>wrote:

/* angular material theming */ @import '~@angular/material/core/theming/all-theme'; @include mat-core(); $app-primary: mat-palette($mat-blue, A400, A100, A700); $app-accent: mat-palette($mat-pink, A200, A100, A400); $app-warn: mat-palette($mat-red); $app-theme: mat-light-theme($app-primary, $app-accent, $app-warn); @include angular-material-theme($app-theme);
now it works!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/angular/material2/issues/1786#issuecomment-278542024), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIEitWt2Qnr8p5hFC-75v7-YenFtaBks5rapFZgaJpZM4KthhC).

For me mat-* does not work, but md-* does

That's because beta.1 still uses md-*, only the latest *-builds releases have mat-*.

Also @wbhob no, it's not "fixed", still if you took the code from https://material.angular.io/guide/theming and put it in _my-theme.scss and then tried importing it in your custom component, I would generate the whole angular theme encapsulated for the said component, that's like 30kb of styles inside EACH of your components.

@fxck Yeah, we are all waiting for @angular to cut a new version. Their tests are passing, and they haven't released a new beta in TWO MONTHS. I, personally, am getting pretty furious at the lack of transparency.

Trust me, the situation is amazing compared to what it was couple of months ago. Also now you have the material2-builds repo, which helps a ton. https://github.com/angular/material2/issues/3075#issuecomment-279359148

I updated to beta-2 and md-* is not working anymore, had to use mat-*.

That is correct and by design.

I feel like I'm really missing something here and I can't figure it out. Can someone please help me?
I have a dialog with a form in it with material inputs.
login-dialog.component.html
<form (ngSubmit)="login()" #loginForm="ngForm">

        <md-input-container class="full-width">
          <input placeholder="Email" type="email" name="email" id="email"
          mdInput
          md-input
          required
          [(ngModel)]="email">
        </md-input-container>

        <md-input-container class="full-width">
          <input placeholder="Password" type="password" name="password" id="password"
          mdInput
          md-input
          required
          [(ngModel)]="password">
        </md-input-container>

      <button type="submit" class="button button-gray">Submit</button>

  </form>

style.css:
@import '~https://fonts.googleapis.com/icon?family=Material+Icons';
@import<EMAIL_ADDRESS>
angular-cli.json:
"styles": [
        "styles.css",
        "custom-app-theme.scss"
      ],

custom-app-theme.scss
@import '~@angular/material/core/theming/all-theme';
// Plus imports for other components in your app.

// Include the base styles for Angular Material core. We include this here so that you only
// have to load a single css file for Angular Material in your app.
@include mat-core();

// Define the palettes for your theme using the Material Design palettes available in palette.scss
// (imported above). For each palette, you can optionally specify a default, lighter, and darker
// hue.
$candy-app-primary: mat-palette($mat-indigo);
$candy-app-accent:  mat-palette($mat-pink, A200, A100, A400);

// The warn palette is optional (defaults to red).
$candy-app-warn:    mat-palette($mat-red);

// Create the theme object (a Sass map containing all of the palettes).
$candy-app-theme: mat-light-theme($candy-app-primary, $candy-app-accent, $candy-app-warn);

// Include theme styles for core and each component used in your app.
// Alternatively, you can import and @include the theme mixins for each component
// that you are using.
@include angular-material-theme($candy-app-theme);

None of the styling is changing on any of the input fields though. What am I missing?

The tilde ~ represents the path and doesn't actually work. You'll have to build in the absolute path (./node_modules/@angular/...). Also, I don't think remote origins are supported, so just include them in index.htnl.
Finally, this is not the place for support requests, please post on stack overflow or elsewhere @sumnercreations

Closing this as it's drifted a bit off-topic.
AFAIK the two guides on theming on the docs site should provide decent guidance on custom theming and for theming your own components. Feel free to open a new issue if there are any specific problems.

@jelbourn I still think it's misleading and wrong, and unnecessarily increasing people's bundle sizes, the specific problem I initially described still stands
if I follow the directions of https://material.angular.io/guide/theming, that is:

create my theme.scss, with this content

@import '~@angular/material/theming';
// Plus imports for other components in your app.

// Include the base styles for Angular Material core. We include this here so that you only
// have to load a single css file for Angular Material in your app.
@include mat-core();

// Define the palettes for your theme using the Material Design palettes available in palette.scss
// (imported above). For each palette, you can optionally specify a default, lighter, and darker
// hue.
$candy-app-primary: mat-palette($mat-indigo);
$candy-app-accent:  mat-palette($mat-pink, A200, A100, A400);

// The warn palette is optional (defaults to red).
$candy-app-warn:    mat-palette($mat-red);

// Create the theme object (a Sass map containing all of the palettes).
$candy-app-theme: mat-light-theme($candy-app-primary, $candy-app-accent, $candy-app-warn);

// Include theme styles for core and each component used in your app.
// Alternatively, you can import and @include the theme mixins for each component
// that you are using.
@include angular-material-theme($candy-app-theme);

import it in my component's scss file with @import

// or whatever is the path to my theme
@import '../../assets/theme';

now I do not need to do literally anything else, just this single line is gonna generate all the general m2 styles (elevation, ripple, cdk stuff)

and this is gonna happen for every single component you import your theme in!!

Youll notice that the elevations classes are all actually different, and this is generated to create the elevation effect. It is not applied to every component, just available as a class when you need it.
Wilson Hobbs
CEO/Founder/Developer at Canal
11th Grade at The Lovett School
Personal Information
E-mail<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Website: www.wilsonhobbs.com (https://www.wilsonhobbs.com)
Twitter/Instagram/Facebook: @wbhob
Canal Information
E-mail<EMAIL_ADDRESS>Web: www.getcanal.com (https://www.getcanal.com/)
Twitter/Instagram/Facebook: @getcanal
On Apr 10, 2017, 4:34 AM -0400, Aleš<EMAIL_ADDRESS>wrote:

@jelbourn (https://github.com/jelbourn) I still think it's misleading and wrong, and unnecessarily increasing people's bundle sizes, the specific problem I initially described still stands
if I follow the directions of https://material.angular.io/guide/theming, that is:
create my theme.scss, with this content
@import '~@angular/material/theming'; // Plus imports for other components in your app. // Include the base styles for Angular Material core. We include this here so that you only // have to load a single css file for Angular Material in your app. @include mat-core(); // Define the palettes for your theme using the Material Design palettes available in palette.scss // (imported above). For each palette, you can optionally specify a default, lighter, and darker // hue. $candy-app-primary: mat-palette($mat-indigo); $candy-app-accent: mat-palette($mat-pink, A200, A100, A400); // The warn palette is optional (defaults to red). $candy-app-warn: mat-palette($mat-red); // Create the theme object (a Sass map containing all of the palettes). $candy-app-theme: mat-light-theme($candy-app-primary, $candy-app-accent, $candy-app-warn); // Include theme styles for core and each component used in your app. // Alternatively, you can import and @include the theme mixins for each component // that you are using. @include angular-material-theme($candy-app-theme);
import it in my component's scss file with @import
// or whatever is the path to my theme @import '../../assets/theme';
now I do not need to do literally anything else, just this single line is gonna generate all the general m2 styles (elevation, ripple, cdk stuff)
and this is gonna happen for every single component you import your theme in!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/angular/material2/issues/1786#issuecomment-292884190), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIEjp-b9Muuq1mu8qEdCK8N8ikmw9iks5ruemJgaJpZM4KthhC).

No, that is not true.
I have two empty components generated with ng-cli, FooComponent, BarComponent,
import { Component, OnInit } from '@angular/core';

@Component({
  selector: 'app-foo', // bar-foo
  templateUrl: './foo.component.html', // bar.component.html
  styleUrls: ['./foo.component.scss'] // bar.component.scss
})
export class FooComponent implements OnInit { // BarComponent

  constructor() { }

  ngOnInit() {
  }

}

*.component.scss only includes this line @import '../../assets/theme';
theme.scss is c&p from themeing guide
@import '~@angular/material/theming';
// Plus imports for other components in your app.

// Include the base styles for Angular Material core. We include this here so that you only
// have to load a single css file for Angular Material in your app.
@include mat-core();

// Define the palettes for your theme using the Material Design palettes available in palette.scss
// (imported above). For each palette, you can optionally specify a default, lighter, and darker
// hue.
$candy-app-primary: mat-palette($mat-indigo);
$candy-app-accent:  mat-palette($mat-pink, A200, A100, A400);

// The warn palette is optional (defaults to red).
$candy-app-warn:    mat-palette($mat-red);

// Create the theme object (a Sass map containing all of the palettes).
$candy-app-theme: mat-light-theme($candy-app-primary, $candy-app-accent, $candy-app-warn);

// Include theme styles for core and each component used in your app.
// Alternatively, you can import and @include the theme mixins for each component
// that you are using.
@include angular-material-theme($candy-app-theme);

both are printed in the root component

since I've removed all other ng-cli styles (the default app.component.css and styles.css), there are only two

You shouldn't have to import he style sheet into every component... it's just globally applied when you put it into your style sheet included in angular-cli.json
Wilson Hobbs
CEO/Founder/Developer at Canal
11th Grade at The Lovett School
Personal Information
E-mail<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Website: www.wilsonhobbs.com (https://www.wilsonhobbs.com)
Twitter/Instagram/Facebook: @wbhob
Canal Information
E-mail<EMAIL_ADDRESS>Web: www.getcanal.com (https://www.getcanal.com/)
Twitter/Instagram/Facebook: @getcanal
On Apr 10, 2017, 6:54 AM -0400, Aleš<EMAIL_ADDRESS>wrote:

No, that is not true.
I have two empty components generated with ng-cli, FooComponent, BarComponent,
import { Component, OnInit } from '@angular/core'; @Component({ selector: 'app-foo', // bar-foo templateUrl: './foo.component.html', // bar.component.html styleUrls: ['./foo.component.scss'] // bar.component.scss }) export class FooComponent implements OnInit { // BarComponent constructor() { } ngOnInit() { } }
*.component.scss only includes this line @import '../../assets/theme';
theme.scss is c&p from themeing guide
@import '~@angular/material/theming'; // Plus imports for other components in your app. // Include the base styles for Angular Material core. We include this here so that you only // have to load a single css file for Angular Material in your app. @include mat-core(); // Define the palettes for your theme using the Material Design palettes available in palette.scss // (imported above). For each palette, you can optionally specify a default, lighter, and darker // hue. $candy-app-primary: mat-palette($mat-indigo); $candy-app-accent: mat-palette($mat-pink, A200, A100, A400); // The warn palette is optional (defaults to red). $candy-app-warn: mat-palette($mat-red); // Create the theme object (a Sass map containing all of the palettes). $candy-app-theme: mat-light-theme($candy-app-primary, $candy-app-accent, $candy-app-warn); // Include theme styles for core and each component used in your app. // Alternatively, you can import and @include the theme mixins for each component // that you are using. @include angular-material-theme($candy-app-theme);
both are printed in the root component
since I've removed all other ng-cli styles (the default app.component.css and styles.css), there are only two

........... that's the whole point, you need to import your theme.scss, if you want to utilise ANY material2 sass helper functions, color palettes
https://material.angular.io/guide/theming-your-components

if you do this, where @import 'src/unicorn-app-theme.scss' is this

you are gonna 28kb of unnecessary styles (after minification) included in your component

the guide should say that you should define your theme in theme.scss, but instead doing @include angular-material-theme($candy-app-theme); in the same file, your should import this theme.scss in your main/global style and call the angular-material-theme function there, only then you can safely import your theme.scss in any component without it generating duplicated files

I don't understand why you need it in each component, it's all already globally available
Wilson Hobbs
CEO/Founder/Developer at Canal
11th Grade at The Lovett School
Personal Information
E-mail<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Website: www.wilsonhobbs.com (https://www.wilsonhobbs.com)
Twitter/Instagram/Facebook: @wbhob
Canal Information
E-mail<EMAIL_ADDRESS>Web: www.getcanal.com (https://www.getcanal.com/)
Twitter/Instagram/Facebook: @getcanal
On Apr 10, 2017, 7:06 AM -0400, Aleš<EMAIL_ADDRESS>wrote:

........... that's the whole point, you need to import your theme.scss, if you want to utilise ANY material2 sass helper functions, color palettes
https://material.angular.io/guide/theming-your-components
if you do this, where @import 'src/unicorn-app-theme.scss' is this
you are gonna 28kb of unnecessary styles (after minification) included in your component
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/angular/material2/issues/1786#issuecomment-292918675), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIEpk3dZjraR6u6G3mNhWpHb0ATG1Bks5rug0lgaJpZM4KthhC).

Oh that makes sense, still don't see why you need to use functions in individual components, just perform them globally.
Wilson Hobbs
CEO/Founder/Developer at Canal
11th Grade at The Lovett School
Personal Information
E-mail<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Website: www.wilsonhobbs.com (https://www.wilsonhobbs.com)
Twitter/Instagram/Facebook: @wbhob
Canal Information
E-mail<EMAIL_ADDRESS>Web: www.getcanal.com (https://www.getcanal.com/)
Twitter/Instagram/Facebook: @getcanal
On Apr 10, 2017, 7:08 AM -0400, Aleš<EMAIL_ADDRESS>wrote:

the guide should say that you should define your theme in theme.scss, but instead doing @include angular-material-theme($candy-app-theme); in the same file, your should import this theme.scss in your main/global style and call the angular-material-theme function there, only then you can safely import your theme.scss in any component without it generating duplicated files
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/angular/material2/issues/1786#issuecomment-292919211), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIEvL5UIFBfrOwsPioiUkFB1XKT0IOks5rug3LgaJpZM4KthhC).

I don't understand why are you commenting if you don't understand. :)
If you use webpack (or ng-cli), there's no such thing as globally available sass functions and/or variables, you HAVE to @import them in every single component you need them.
https://github.com/webpack-contrib/sass-loader/issues/211
https://github.com/webpack-contrib/sass-loader/issues/218
and million other issues

@fxck thank you so much!!! Same functionality
Old

New


Typo in tutorial keptn-multistage-qualitygates

Hello, on this page : https://tutorials.keptn.sh/tutorials/keptn-multistage-qualitygates-09/index.html?index=..%2F..index#9
the commands to add ressources are bad
We created a service named helloserver, and in the keptn add-resource we specify a service named helloservice
Bad:
keptn add-resource --project=pod-tato-head --stage=hardening --service=helloservice --resource=jmeter/load.jmx --resourceUri=jmeter/load.jmx
keptn add-resource --project=pod-tato-head --stage=hardening --service=helloservice --resource=jmeter/jmeter.conf.yaml --resourceUri=jmeter/jmeter.conf.yaml

Good:
keptn add-resource --project=pod-tato-head --stage=hardening --service=helloserver --resource=jmeter/load.jmx --resourceUri=jmeter/load.jmx
keptn add-resource --project=pod-tato-head --stage=hardening --service=helloserver --resource=jmeter/jmeter.conf.yaml --resourceUri=jmeter/jmeter.conf.yaml

Wait...
Maybe it would be easier to switch all the helloserver references to helloservice since it's the name of the pod-tato-head (ie https://github.com/cncf/podtato-head/blob/main/delivery/keptn/helm-charts/helloserver/templates/service.yaml)

@christian-kreuzberger-dtx Can this be closed?

Don't think it's needed any longer, I'm closing it.


fail to create new game after deleting tool source

When I executed the ‘amethyst new’ command, the tool successfully created a new folder, but the creation of the new game project failed, the details are as follows：
lws@lws-deepin:/tool/project/games$ RUST_BACKTRACE=1 amethyst new pong -a 0.10.0
thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', libcore/result.rs:1009:5
stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
1: std::sys_common::backtrace::print
at libstd/sys_common/backtrace.rs:71
at libstd/sys_common/backtrace.rs:59
2: std::panicking::default_hook::{{closure}}
at libstd/panicking.rs:211
3: std::panicking::default_hook
at libstd/panicking.rs:227
4: std::panicking::rust_panic_with_hook
at libstd/panicking.rs:476
5: std::panicking::continue_panic_fmt
at libstd/panicking.rs:390
6: rust_begin_unwind
at libstd/panicking.rs:325
7: core::panicking::panic_fmt
at libcore/panicking.rs:77
8: core::result::unwrap_failed
9: std::sync::once::Once::call_once::{{closure}}
10: std::sync::once::Once::call_inner
at libstd/sync/once.rs:397
11: amethyst_cli::templates::deploy
12: amethyst_cli::new::New::execute
13: amethyst::main
14: std::rt::lang_start::{{closure}}
15: std::panicking::try::do_call
at libstd/rt.rs:59
at libstd/panicking.rs:310
16: __rust_maybe_catch_panic
at libpanic_unwind/lib.rs:102
17: std::rt::lang_start_internal
at libstd/panicking.rs:289
at libstd/panic.rs:392
at libstd/rt.rs:58
18: main
19: __libc_start_main
20: _start

I encountered the same error message, and fixed it by running cargo install -f amethyst_tools again. amethyst binary contained an old path where its source directory no longer exists as I have cleaned up ~/.cargo/registry/src.

This is a old issue that we've resolved in a newer version, so I'm going to close this.

Are you sure @Xaeroxe? It seems like we're still loading the templates at run-time, assuming they are in the source directory. Isn't that something we ought to fix?

I've tested this recently by installing it from crates and it is working. Though I do see a reference to CARGO_MANIFEST_DIR in the source. Also, @sinkuu reported they fixed the problem by installing the latest version.

Ok, so it seems we're dependent on our source directory in the final compiled version. That's the bug. I'll update the issue title to reflect that.

Can someone provide steps to reproduce this issue and elaborate more on these:

It seems like we're still loading the templates at run-time, assuming they are in the source directory. Isn't that something we ought to fix?

Ok, so it seems we're dependent on our source directory in the final compiled version. That's the bug. I'll update the issue title to reflect that.

Yes.
Reproduction

Clone this repo
Build the amethyst binary
Try running a command (should work)
Move the cloned repo, and try again (this should fail)

The reason for that is that we encode the location of the source directory into the binary, which is incorrect.
Instead, the templates should have been included into the binary, which was the case previously (but was changed at some point I believe).

I've been looking into this the past couple of days. The best solution I've come up with is using a build script to generate a file that creates a tuple for the file name and include_str call to the file name. Then use include to parse said tuple from said generated file. This solution also allows for version detection during compilation, so the liquid renderings are the only file operations during runtime.
I want to get other opinions on how to resolve this, as the implementation I suggested seems quite heavy-handed.

Instead, the templates should have been included into the binary, which was the case previously

This also leads me to believe my suggestion is overly complicated.

No, that sounds good. It's pretty similar to what I did in my original rewrite.


K8s deploys nuclio problem

I executed the following command：
SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
nuctl deploy --project-name cvat
--path $SCRIPT_DIR/openvino/dextr/nuclio
--namespace nuclio
--kubeconfig /etc/kubernetes/admin.conf
--verbose
--platform kube
The following log is printed：
20.11.30 16:56:43.055                     nuctl (D) Saving deployment logs
20.11.30 16:56:43.065    nuctl.platform.updater (I) Updating function {"name": "openvino-dextr"}
Error - NuclioFunction in unhealthy state:
Error - context deadline exceeded
.../platform/kube/controller/nucliofunction.go:148
Call stack:
Failed to wait for function resources to be available
.../platform/kube/controller/nucliofunction.go:148
/nuclio/pkg/platform/kube/deployer.go:264

Call stack:
NuclioFunction in unhealthy state:
Error - context deadline exceeded
.../platform/kube/controller/nucliofunction.go:148
Call stack:
Failed to wait for function resources to be available
.../platform/kube/controller/nucliofunction.go:148
/nuclio/pkg/platform/kube/deployer.go:264

Failed to wait for function readiness.
Pod logs:

nuclio-openvino-dextr-55cf7cbcd8-pmq9f
Failed to read logs: container "nuclio" in pod "nuclio-openvino-dextr-55cf7cbcd8-pmq9f" is waiting to start: trying and failing to pull image

Warning events:
Failed to pull image "cvat/openvino.dextr:latest": rpc error: code = Unknown desc = Error response from daemon: pull access denied for cvat/openvino.dextr, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Error: ErrImagePull
Error: ImagePullBackOff
/nuclio/pkg/platform/kube/deployer.go:177
Failed to deploy function
...//nuclio/pkg/platform/abstract/platform.go:175
You have new mail in /var/spool/mail/root

I want to know how to solve

We don't currently provide any Kubernetes templates for CVAT deployment, so I cannot reproduce your issue. I guess the reason is pull access is denied for cvat / openvino.dextr, the repository does not exist, or a" docker login "might be required: denied: The requested resource access is denied, make sure the image can be pulled.
If you are working on deploying K8s, may I ask you to contribute this feature to the mainstream repository, improving the existing PR https://github.com/openvinotoolkit/cvat/pull/1962 by adding nuclio support?


(pyCFTrackers) C:\Users\wangy\Desktop\pyCFTrackers-master\lib\eco\features>python setup.py build_ext --inplace running build_ext No module named 'numpy.distutils._msvccompiler' in numpy.distutils; trying from distutils

No description provided.

did you resolve this problem ?


Update googlemusic.js

new id for current track, tested dec 10 - chrome

Note: this duplicates #848.

+1. Please merge & update the extension.

Should by resolved by duplicate PR #848


Test refactors

Coverage increased (+2.8%) to 87.171% when pulling 016d8028154723f0e5872da813409a5e4aecc4c9 on test-refactors into 771d9e2ad360a07bbb357f3f7da82a4c99b328c5 on master.

Coverage increased (+2.8%) to 87.171% when pulling 016d8028154723f0e5872da813409a5e4aecc4c9 on test-refactors into 771d9e2ad360a07bbb357f3f7da82a4c99b328c5 on master.


Reshape using row major layout

reshape currently doesn't work properly in tile major layout, thus we want to
convert input tensor to row major layout and to execute reshape.
Implemented solution uses pass which adds necessary ops which are needed in order to convert
input tensor from tile to row and back.

We create empty op which will have the same mem_layout/mem_space and
grid size as original input tensor
We call to_layout and we pass input tensor as first operand and empty
op from 1 as second operand (dps).
We create new empty tensor which will be used as dps operand for
reshape
We invoke reshape with first operand from 2 and second operand 3
(dps).
We invoke to_layout again on reshape result and we pass in original dps operand.

Other approach was to change reshape op in mlir rt, and convert input tensor to row layout if needed.
This approach is more clear (see b409044a792bbfc5fee8fb4f47fdb0004c0f539c) but downside is
it doesn't cover emitc.
One more thing I tried is to squeeze changes into ttir->ttnn lowering of reshape op but this meant
I had to copy bunch of code from different places (toLayout lowering/empty op). Also it didn't make
sense to me to create ttnn ops (like empty/tolayout) which have their ttir equivalents inside reshape rewriter.
Misc:

Fixed bug where we added ToDevice op in Layout lowering for tensors which are already on device

@mtopalovicTT would it make sense to convert to row major layout only if the last two dimensions are not multiples of tile dimensions? AFAIK ttnn reshape ops should work correctly if we have height and width dimensions that are divisble by the tile size.

@jnie-TT Problem is reshape in tile on metal doesn't produce right results even if you supply padded tensor. You would have to be careful how you place data inside the tensor for reshape to work in tile. Check this issue: https://github.com/tenstorrent/tt-metal/issues/12866

@nvukobratTT We wanted to have some workaround until they fix reshape, we didn't know timeline ahead of time...
If they are sure it's EOW and there is nothing blocking uplifting metal version we don't need this PR. On other side if we merge, rolling this back would be trivial.

@nvukobratTT We wanted to have some workaround until they fix reshape, we didn't know timeline ahead of time... If they are sure it's EOW and there is nothing blocking uplifting metal version we don't need this PR. On other side if we merge, rolling this back would be trivial.

Thanks for the details! is it okay to wait until Monday for TTNN feedback? If this will take more time, we can probably go with workaround, but please create issues to revert the change latter if needed.
@tt-mpantic let us know if you have more details around progress on this reshape, or should we ping them once again :))

https://github.com/tenstorrent/tt-metal/issues/12866

Its fine with me.

Its fine with me.

Seems like there is open PR for it :)) 🤘

Okay, looks like they merged the change, I've added item to test and uplift metal version. Once everything is good I will close this PR.

Closing this since reshape should be fixed with metal uplift that joca is driving with #870


http/2 for public gateways

Use http/2 for public gateways.
Benefits:

avoiding stalls by hitting browser connection limit - 6 per domain (amplified by unresolvable resources on the page)
avoiding RTT and TLS handshakes (amplified by random gateway selection - latency)
lowering overhead of TCP (socket) context switching on loaded gateways
faster loading time of mixed/small content, performance parity for large
less CPU on both sides

nginx supported with module
caddy has support built in

our nginx has accidentally supported http/2 for a while now :+1:


Checking which key is duplicate, in case of a ErrDuplicateKey error

Your Question
Is there a way to check which key was duplicate, in case of a ErrDuplicateKey error?
The document you expected this should be explained

Gorm error handling docs

Currently not supported, you can convert errors by yourself without using ErrDuplicateKey
https://github.com/go-gorm/postgres/pull/162#discussion_r1138089642


Support for OS X 10.10

We are using CleanroomLogger in our project which has target set to OS X 10.10 (about 15% of our clients still using OS X 10.10, so we need to support it). But after updating CleanroomLogger to the latest version 5.1.0 (because of migrating to Swift 3.1 / Xcode 8.3) our app fails to build - CleanroomLogger now requires minimum target 10.11.  So, my question is - is there any way how to use the latest version of CleanroomLogger in projects targeting OS X 10.10 (e.g. by disabling some features not supported in OS X 10.10)?

Hello,
If you update to the latest version (5.1.1), the problem should be resolved.
Sorry for the trouble,
E.


Add dependabot for github actions

What does this PR do?
This PR configures Dependabot to also watch GH Actions and allows it to open a PR if we're using old versions of Actions
How should this be tested?
Nothing to test. After merge, this will begin to watch the repo for out of date actions. This can be seen here: tylerauerbeck/charts-3#1

@sabre1041 Merge this?


Replace "elm" by "localRuntime" in JS files

Like this?

Yeah, added some comments on the merge though.
Some modules do this trick where values get attached to Elm instead of just localRuntime. I generally think this is not a great idea, and I'm not sure of the benefits really. I'd be curious if there's some decisive way to know the right thing on that.

Concerning the latter point, I have no idea when to prefer attaching values to Elm. Is the default attaching them to localRuntime, and whenever the alternative is better in your judgement, you will do it yourself?

When a module needs to call setTimeout or notify or attach event listeners, then it definitely needs to use localRuntime. You don't want to be able to accidentally notify different Elm modules in crazy ways.
When the module is stateless, it can be attached to Elm in theory. That should work for stuff like Array and List, but I have been bitten before by a module that used a guid in some indirect and surprising way that led to bugs. So it works, but it can lead to crazy bugs. Overall, it's not clear that this is a worthwhile thing to ever do.


Add API to get languages

Add API in back-nest app
Add getAllLanguages method to challenge service
Create challenge controller and add the api route
Route should be `/api/challenges/languages
Route should return array of strings

done


spacedrop chat let me back in

Hi, Ive had to reset my account. Is there a way to get
spacedrop chat to let me back into it, please?

Wrong repo sorry!


Generate DevTools deep links for layout errors

Currently, deep links are only supported for renderflex overflow errors. We'd like to support deep links for all layout errors where possible.

@kenzieschmoll Do you need help from the framework team for this? If so, could you provide some details on what would need to be implemented?

This work is no longer a priority. We can reopen this issue if we decide to do this in the future.


[BUG] TypeError: issubclass() arg 1 must be a class

Traceback (most recent call last):
File "/home/VivatGrunwald/bot.py", line 1, in
from instagrapi import Client
File "/home/VivatGrunwald/.local/lib/python3.10/site-packages/instagrapi/init.py", line 7, in
from instagrapi.mixins.account import AccountMixin
File "/home/VivatGrunwald/.local/lib/python3.10/site-packages/instagrapi/mixins/account.py", line 8, in
from instagrapi.extractors import extract_account, extract_user_short
File "/home/VivatGrunwald/.local/lib/python3.10/site-packages/instagrapi/extractors.py", line 6, in
from .types import (
File "/home/VivatGrunwald/.local/lib/python3.10/site-packages/instagrapi/types.py", line 13, in
class Resource(BaseModel):
File "pydantic/main.py", line 197, in pydantic.main.ModelMetaclass.new
File "pydantic/fields.py", line 506, in pydantic.fields.ModelField.infer
File "pydantic/fields.py", line 436, in pydantic.fields.ModelField.init
File "pydantic/fields.py", line 552, in pydantic.fields.ModelField.prepare
File "pydantic/fields.py", line 668, in pydantic.fields.ModelField._type_analysis
File "/usr/local/lib/python3.10/typing.py", line 1157, in subclasscheck
return issubclass(cls, self.origin)
TypeError: issubclass() arg 1 must be a class
Why does this error happen I can't find an answer to it for hours, adw0rd, maybe you know more about this?

I also have python 3.10 everywhere, but there are no such problems. And judging by the traceback, this is a problem with pydantic. I don't know how to reproduce it

is there a workaround this problem, the problem only exists in pythonanywhere but not on my local machine

I don't know, write them a question

I don't know, write them a question


The problem with tf.compat.v1.disable_v2_behavior

Description
When importing some tensorflow_v2 modules, the subsequent TF2 functions cannot work properly.
I found out that some modules call the tensorflow.disable_v2_behavior function when they are imported. It will disable the subsequent TF2 behaviors.
cd submarine-sdk/pysubmarine/submarine

$ grep -rnH 'disable_v2_behavior'
ml/tensorflow_v2/layers/core.py:20:tf.compat.v1.disable_v2_behavior()
utils/tf_utils_v2.py:26:    tf.compat.v1.disable_v2_behavior()
utils/tf_utils_v2.py:57:        tf.compat.v1.disable_v2_behavior()

Furthermore, without the tensorflow.disable_v2_behavior, the tests still work as usual. Maybe the disable_v2_behavior is not necessary to the tf2 modules.
In summary, We should remove the tf.compat.v1.disable_v2_behavior statements to avoid the similar problem.
How to reproduce the TF2 error
Create Python venv.
cd submarine-sdk/pysubmarine
python3 -m venv .venv
source .venv/bin/activate
python3 -m pip install -e .[tf2]

Create demo.py and copy the following Python code into it.
# demo.py
import tensorflow as tf

from submarine.ml.tensorflow_v2.model import DeepFM   # call `tf.compat.v1.disable_v2_behavior` function

class LinearNNModel(tf.keras.Model):
    def __init__(self):
        super().__init__()
        self.dense1 = tf.keras.layers.Dense(1, activation=tf.nn.relu)  # One in and one out

    def call(self, x):
        y_pred = self.dense1(x)
        return y_pred

model = LinearNNModel()
input_arr = tf.random.uniform((1, 5))
model(input_arr)

model.save('sample-model')

Running the Python code. the error message shows that the TF2 function cannot work properly.
$ python3 demo.py

...
Traceback (most recent call last):
  File "/home/tom/huang06/submarine/submarine-sdk/pysubmarine/demo.py", line 21, in <module>
    model.save('sample-model')
  File "/home/tom/huang06/submarine/submarine-sdk/pysubmarine/.venv/lib/python3.10/site-packages/keras/utils/traceback_utils.py", line 67, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/home/tom/huang06/submarine/submarine-sdk/pysubmarine/.venv/lib/python3.10/site-packages/keras/saving/save.py", line 142, in save_model
    raise NotImplementedError(
NotImplementedError: Saving the model to HDF5 format requires the model to be a Functional model or a Sequential model. It does not work for subclassed models, because such models are defined via the body of a Python method, which isn't safely serializable. Consider saving to the Tensorflow SavedModel format (by setting save_format="tf") or using `save_weights`.

@featherchen
Hi~ There are some questions about the tf part of the codes that we need your help to answer, please. Hope you can help us when you have time.
Thanks!


[port to lts] Routerlicious doc service telemetry (#12807)

Cherry-pick of #12807 to the lts branch

npm run lint:fix to fix the lint issues.


Issue with docker

/opt/nvidia/nvidia_entrypoint.sh: line 67: exec: autotrain: not found
Any idea how to resolve it

too less information to give any suggestions or solutions

I tried installing the docker file, after installation and formation of image, i used this command to start the conatiner:
docker run --gpus all -p 8883:7860 --name autotrain_cont autotrain_llm:1.3 autotrain api --port 7860 --ip <IP_ADDRESS>
But getting the above error

we dont recommend using docker container this way. please use the hugging face space.

That's because conda env is not activated yet. You could follow this:
docker run --gpus=all huggingface/autotrain-advanced conda run --no-capture-output -p /app/env autotrain --help


bug

Recently i added demodal addon  https://www.curseforge.com/wow/addons/demodal which is assisting in moving windows of UI. Now i am getting this error .Since  Outfitter options window is slightly moved out of its usually position that results in this error. I can click again and it works then but on first try it drops this error.
Message: ...tter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua line 1422:
Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: LibDropdownFrame1:SetPoint.
Debug:
[string "=(tail call)"]: ?
[string "=(tail call)"]: ?
[string "=[C]"]: ?
[string "=[C]"]: SetPoint()
[string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1422: Show()
[string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1558: ToggleMenu()
[string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1504:
...tter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua:1503
Locals:
(*temporary) = "LeftButton"
(*temporary) = false

What this fix one time fix or do you plan to fix this addon in future since no response for like few months?


feat: mos plugin data ingest

Support MOS plugins running in the UI as a way to ingest data.
Awaiting Release 21.

Codecov Report

Merging #62 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #62   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           20        20
  Branches         5         5
=========================================
  Hits            20        20

Continue to review full report at Codecov.

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


[HUDI-5824] Fix: do not combine if write operation is Upsert and COMBINE_BEFORE_UPSERT is false

Change Logs
Fix shouldCombine, take into account the situation where the write operation is UPSERT but  COMBINE_BEFORE_UPSERT is false.
Currently, Hudi always combines records on UPSERT, and option COMBINE_BEFORE_UPSERT is not honored.
Impact
Fixes user-facing option COMBINE_BEFORE_UPSERT
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[x] CI passed

@hudi-bot run azure

GH actions tests failed but I don't see why, it passed before.
Azure failed on TestHoodieDeltaStreamerWithMultiWriter, rather unrelated and it also passed it on the first run. Looks like some flaky tests causing issues.

There seem to be a bug with non-strict insert mode
when using spark datasource it can insert duplicates only in overwrite mode or append mode when data is inserted to the table for the first time, but if I want to insert in append mode for the second time it deduplicates the dataset as if it was working in upsert mode.

opt_insert = {
    'hoodie.table.name': 'huditbl',
    'hoodie.datasource.write.recordkey.field': 'keyid',
    'hoodie.datasource.write.table.name': 'huditbl',
    'hoodie.datasource.write.operation': 'insert',
    'hoodie.sql.insert.mode': 'non-strict',
    'hoodie.upsert.shuffle.parallelism': 2,
    'hoodie.insert.shuffle.parallelism': 2,
    'hoodie.combine.before.upsert': 'false',
    'hoodie.combine.before.insert': 'false',
    'hoodie.datasource.write.insert.drop.duplicates': 'false'
}

df = spark.range(0, 10).toDF("keyid") \
  .withColumn("age", expr("keyid + 1000"))

df.write.format("hudi"). \
options(**opt_insert). \
mode("overwrite"). \
save(path)

spark.read.format("hudi").load(path).count() # returns 10

df = df.union(df) # creates duplicates
df.write.format("hudi"). \
options(**opt_insert). \
mode("append"). \
save(path)

spark.read.format("hudi").load(path).count() # returns 10 but should return 20

Hi Hudi devs, I would appreciate a review, thanks!

@hudi-bot run azure

@bvaradar CI is green, could you please take a look at it again? thanks

@hudi-bot run azure

@kazdy : Can you remove the draft status if you think it is ready.


Fix onnx_dynamo-fallback

Codecov Report
Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 70.09%. Comparing base (b104dcd) to head (232da06).

Files with missing lines
Patch %
Lines

...experiment/torch_bench/_bash_bench_model_runner.py
66.66%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #255      +/-   ##
==========================================
- Coverage   70.09%   70.09%   -0.01%
==========================================
  Files         160      160
  Lines       23211    23213       +2
==========================================
+ Hits        16269    16270       +1
- Misses       6942     6943       +1

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


More mimetypes

Since it supports many image formats, I suggest to include them in the mimetypes list of the .desktop file (if im not wrong, this will make the filemanagers or other applications being able to show Entice as an option or tool to open the files with)
Actually it only includes:

MimeType=image/jpeg;image/png;image/gif

Example:

~ ❯❯❯ file --mime-type /tmp/foo.webp
/tmp/foo.webp: image/webp

Indeed, that is something i wanted to do and i forget it... thanks for the reminder

tell me if it's better, now. If it's ok, please close the issue


feat: enable v3 documentation rendering

Description
This PR enables documentation for v3 documents
Related issue(s)
Blocked by https://github.com/asyncapi/studio/pull/796
Blocked by https://github.com/asyncapi/parser-js/pull/861
Blocked by https://github.com/asyncapi/asyncapi-react/pull/808
Fixes https://github.com/asyncapi/studio/issues/790

Thanks @KhudaDad414 👍

/rtm


Brew formula is outdated

Hey, I have a problem installing approf:
% brew install approf

appr    Warning: No available formula with the name "approf". Did you mean apprise?
==> Searching for similarly named formulae and casks...
==> Formulae
apprise

To install apprise, run:
  brew install apprise

Looks like steps from README are not valid anymore.
Thanks for the tool btw.

@cristaloleg Thanks for you interest in this project!
https://formulae.brew.sh/cask/approf#default
I just tried installing approf using brew install approf, and it worked fine on my macbook.
Since approf needs macOS 14.0 or later, could you check your OS version?

I'm on macOS 14.5. The problem with README is that it suggests brew install approf without --cask.
Anyway, with --cask it doesn't work either:
% brew install --cask approf
Warning: Cask 'approf' is unavailable: No Cask with this name exists.
==> Searching for similarly named casks...
Error: No casks found for approf.

🤷

That's odd🤔. I need some time to figure out what's happening.
In the meantime, you can download the app from: https://github.com/moderato-app/approf/releases/tag/v14.1.3

Could you check the git revision of your brew repo with this command?
git -C $(brew --repo homebrew/cask) log -n 5

homebrew-cask-versions % git log -n 5
commit 057d1202c4ac9d4059909260af8d13e20fbf8cab (HEAD -> master, origin/master, origin/HEAD)
Merge: 082412cf30 b2602d2509
Author: Miccal Matthews<EMAIL_ADDRESS>Date:   Fri May 3 04:42:57 2024 +0800

    Merge pull request #20219 from Homebrew/deprecate

    Deprecate repository

commit b2602d2509f8839e8fd11618091d4e082627e161
Author: Patrick Linnane<EMAIL_ADDRESS>Date:   Thu May 2 11:09:16 2024 -0700

    Deprecate repository

    Signed-off-by: Patrick Linnane<EMAIL_ADDRESS>
commit 082412cf30083b63e7734e8c676a7827b0082c25
Merge: 877bb10b71 8d33e587a9
Author: Razvan Azamfirei<EMAIL_ADDRESS>Date:   Thu May 2 20:41:26 2024 +0300

    Merge pull request #20218 from Homebrew/migrate-semeru-jdk

commit 877bb10b7164df1ea309cd7038f862ab9f72e102
Merge: 5880bf59a6 1c1c153bc7
Author: Patrick Linnane<EMAIL_ADDRESS>Date:   Thu May 2 10:37:23 2024 -0700

    Merge pull request #20213 from Homebrew/deprecate-daedalus

commit 5880bf59a626b3592602f26cabbc2ea844015587
Merge: 2885a3bd13 4b7a83a737
Author: Patrick Linnane<EMAIL_ADDRESS>Date:   Thu May 2 10:28:30 2024 -0700

    Merge pull request #20217 from Homebrew/migrate-parallels15

A friend of mine confirmed that brew install approf works on their MacBook.
Looks like your brew hasn't been updated for 4 months. That might be causing some issues. Can you give brew update a shot and then run brew install approf?

How to stop Homebrew auto update on mac terminal

@cristaloleg did you manage to run brew install approf?  I’m still curious about what caused the issue.

no updates, closing this

Yes, everything is fixed. Forgot to answer earlier, thanks!


Fixes for firebase-storage typo comments, refer to __putString method and supress log message

:bow:

anybody check my tiny fixes?

@howking will check on it in a bit. :)

@tjmonsi Thanks a lot !!

@howking Thanks too for catching those bugs :)