logstash listeners won't show up in 'netstat -na'

Problem description
UDP/TCP listeners won't work in logstash configuration files.  A listener works great in filebeat.  The larger problem that I have is that I cannot parse out KV pairs from the messages portion of the syslog.  I need to add a filter, which can be done in logstash. But I am sending my logs to filebeat. So I am a bit stuck.  How can I get a listener to work in logstash?
Extra information
This is the exact issue I have.
https://discuss.elastic.co/t/parse-syslog-from-syslog/168291

@ewitkop-panw could you please share your Logstash configuration? There is a TCP input enabled by default, and it definitely works, it is used in our automated tests.
By the way, netstat won't show you listening ports because Logstash is running inside a container.

I am able to get FB to connect to Logstash on 5044, but the logs don't seem to flow through the connection.
2021-09-17T23:50:48.824Z	INFO	[publisher_pipeline_output]	pipeline/output.go:143	Connecting to backoff(async(tcp://localhost:5044))
2021-09-17T23:50:48.824Z	INFO	[publisher]	pipeline/retry.go:219	retryer: send unwait signal to consumer
2021-09-17T23:50:48.824Z	INFO	[publisher]	pipeline/retry.go:223	  done
2021-09-17T23:50:48.824Z	INFO	[publisher_pipeline_output]	pipeline/output.go:151	Connection to backoff(async(tcp://localhost:5044)) established
Filebeat is installed on the host Ubuntu box.
`root@ip-192-168-45-101:~# more  /etc/filebeat/filebeat.yml
###################### Filebeat Configuration Example #########################
This file is an example configuration file highlighting only the most common
options. The filebeat.reference.yml file from the same directory contains all the
supported options with more comments. You can use it as a reference.

You can find the full configuration reference here:
https://www.elastic.co/guide/en/beats/filebeat/index.html
For more available modules and options, please see the filebeat.reference.yml sample
configuration file.
#=========================== Filebeat inputs =============================
filebeat.inputs:
Each - is an input. Most options can be set at the input level, so
you can use different inputs for various configurations.
Below are the input specific configurations.

type: log
Change to true to enable this input configuration.
enabled: false
Paths that should be crawled and fetched. Glob based paths.
paths:

/var/log/*.log
#- c:\programdata\elasticsearch\logs*

Exclude lines. A list of regular expressions to match. It drops the lines that are
matching any regular expression from the list.
#exclude_lines: ['^DBG']
Include lines. A list of regular expressions to match. It exports the lines that are
matching any regular expression from the list.
#include_lines: ['^ERR', '^WARN']
Exclude files. A list of regular expressions to match. Filebeat drops the files that
are matching any regular expression from the list. By default, no files are dropped.
#exclude_files: ['.gz$']
Optional additional fields. These fields can be freely picked
to add additional information to the crawled log files for filtering
#fields:
level: debug
review: 1
Multiline options
Multiline can be used for log messages spanning multiple lines. This is common
for Java Stack Traces or C-Line Continuation
The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
#multiline.pattern: ^[
Defines if the pattern set under pattern should be negated or not. Default is false.
#multiline.negate: false
Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
that was (not) matched before or after or as long as a pattern is not matched based on negate.
Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
#multiline.match: after

type: syslog
enabled: true
protocol.udp:
host: "<IP_ADDRESS>:514" # IP:Port of host receiving syslog traffic

#============================= Filebeat modules ===============================
filebeat.config.modules:
Glob pattern for configuration loading
path: ${path.config}/modules.d/*.yml
Set to true to enable config reloading
reload.enabled: false
Period on which files under path should be checked for changes
#reload.period: 10s
#==================== Elasticsearch template setting ==========================
setup.template.settings:
index.number_of_shards: 3
#index.codec: best_compression
#_source.enabled: false
#================================ General =====================================
The name of the shipper that publishes the network data. It can be used to group
all the transactions sent by a single shipper in the web interface.
#name:
The tags of the shipper are included in their own field with each
transaction published.
#tags: ["service-X", "web-tier"]
Optional fields that you can specify to add additional information to the
output.
#fields:
env: staging
#============================== Dashboards =====================================
These settings control loading the sample dashboards to the Kibana index. Loading
the dashboards is disabled by default and can be enabled either by setting the
options here, or by using the -setup CLI flag or the setup command.
setup.dashboards.enabled: true
The URL from where to download the dashboards archive. By default this URL
has a value which is computed based on the Beat name and version. For released
versions, this URL points to the dashboard archive on the artifacts.elastic.co
website.
#setup.dashboards.url:
#============================== Kibana =====================================
Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
This requires a Kibana endpoint configuration.
setup.kibana:
Kibana Host
Scheme and port can be left out and will be set to the default (http and 5601)
In case you specify and additional path, the scheme is required: http://localhost:5601/path
IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
#host: "localhost:5601"
host: "<IP_ADDRESS>:5601"
ssl.enabled: false
username: elastic
password: changeme
Kibana Space ID
ID of the Kibana Space into which the dashboards should be loaded. By default,
the Default Space will be used.
#space.id:
#============================= Elastic Cloud ==================================
These settings simplify using filebeat with the Elastic Cloud (https://cloud.elastic.co/).
The cloud.id setting overwrites the output.elasticsearch.hosts and
setup.kibana.host options.
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 the beat.
#-------------------------- Elasticsearch output ------------------------------
#output.elasticsearch:
Array of hosts to connect to.
hosts: ["localhost:9200"]
#ssl.verification_mode: none
Enabled ilm (beta) to use index lifecycle management instead daily indices.
#ilm.enabled: false
Optional protocol and basic auth credentials.
#protocol: "https"
#username: "elastic"
#password: "changeme"
#----------------------------- Logstash output --------------------------------
output.logstash:
The Logstash hosts
hosts: ["localhost:5044"]
timeout: 300
ssl.enabled: false
Optional SSL. By default is off.
List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/root/docker-elk/tls/kibana/elasticsearch-ca.pem"]
Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
#================================ Processors =====================================
Configure processors to enhance or manipulate events generated by the beat.
processors:

add_host_metadata: ~
add_cloud_metadata: ~

#================================ Logging =====================================
Sets log level. The default log level is info.
Available log levels are: error, warning, info, debug
#logging.level: debug
At debug level, you can selectively enable logging only for some components.
To enable all selectors use ["*"]. Examples of other selectors are "beat",
"publish", "service".
#logging.selectors: ["*"]
#============================== Xpack Monitoring ===============================
filebeat can export internal metrics to a central Elasticsearch monitoring
cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The
reporting is disabled by default.
Set to true to enable the monitoring reporter.
#xpack.monitoring.enabled: false
Uncomment to send the metrics to Elasticsearch. Most settings from the
Elasticsearch output are accepted here as well. Any setting that is not set is
automatically inherited from the Elasticsearch output configuration, so if you
have the Elasticsearch output configured, you can simply uncomment the
following line.
#xpack.monitoring.elasticsearch:
root@ip-192-168-45-101:~# `
`root@ip-192-168-45-101:~/docker-elk/logstash/pipeline# cat logstash.conf
input {
beats {
port => 5044
codec => json
ssl => false
client_inactivity_timeout => 30000
}
}
############ FILTERS ###############
#filter {
dissect { mapping => { "message" => "<%{level}>%{} %{ts} %{loglevel} %{something} - [%{kvString}" } }
date { match => [ "ts", "ISO8601" ] }
kv { source => "kvString" field_split => ";" value_split => ":" trim_key => " " }
#}
Add your filters / logstash plugins configuration here
output {
elasticsearch {
#hosts => ["https://<IP_ADDRESS>:9200"]
hosts => ["https://elasticsearch:9200"]
user => "elastic"
password => "changeme"
ecs_compatibility => disabled
ssl => true
cacert => "config/elasticsearch-ca.pem"
}
}
`

root@ip-192-168-45-101:~/docker-elk# more docker-compose.yml
version: '3.2'
services:
elasticsearch:
build:
context: elasticsearch/
args:
ELK_VERSION: $ELK_VERSION
volumes:
- type: bind
source: ./elasticsearch/config/elasticsearch.yml
target: /usr/share/elasticsearch/config/elasticsearch.yml
read_only: true
- type: volume
source: elasticsearch
target: /usr/share/elasticsearch/data
# (!) TLS certificates. Generate using instructions from tls/README.md.
- type: bind
source: ./tls/elasticsearch/elasticsearch.p12
target: /usr/share/elasticsearch/config/elasticsearch.p12
read_only: true
- type: bind
source: ./tls/elasticsearch/http.p12
target: /usr/share/elasticsearch/config/http.p12
read_only: true
ports:
- "9200:9200"
- "9300:9300"
environment:
ES_JAVA_OPTS: "-Xmx256m -Xms256m"
ELASTIC_PASSWORD: changeme
# Use single node discovery in order to disable production mode and avoid bootstrap checks.
# see: https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html
discovery.type: single-node
networks:
- elk
logstash:
build:
context: logstash/
args:
ELK_VERSION: $ELK_VERSION
volumes:
- type: bind
source: ./logstash/config/logstash.yml
target: /usr/share/logstash/config/logstash.yml
read_only: true
- type: bind
source: ./logstash/pipeline
target: /usr/share/logstash/pipeline
read_only: true
# (!) CA certificate. Generate using instructions from tls/README.md
- type: bind
source: ./tls/kibana/elasticsearch-ca.pem
target: /usr/share/logstash/config/elasticsearch-ca.pem
read_only: true
ports:
- "5044:5044"
- "5000:5000/tcp"
- "5000:5000/udp"
- "9600:9600"
environment:
LS_JAVA_OPTS: "-Xmx256m -Xms256m"
networks:
- elk
depends_on:
- elasticsearch
kibana:
build:
context: kibana/
args:
ELK_VERSION: $ELK_VERSION
volumes:
- type: bind
source: ./kibana/config/kibana.yml
target: /usr/share/kibana/config/kibana.yml
read_only: true
- type: bind
source: ./tls/kibana/elasticsearch-ca.pem
target: /usr/share/kibana/config/elasticsearch-ca.pem
read_only: true
ports:
- "5601:5601"
networks:
- elk
depends_on:
- elasticsearch
networks:
elk:
driver: bridge
volumes:
elasticsearch:
root@ip-192-168-45-101:~/docker-elk#

root@ip-192-168-45-101:~# filebeat version
filebeat version 7.14.1 (amd64), libbeat 7.14.1 [703d589a09cfdbfd7f84c1d990b50b6b7f62ac29 built 2021-08-26 09:12:57 +0000 UTC]
root@ip-192-168-45-101:~#

I am making progress. I rebooted the host and the 5044 stayed up. I changed the codec on the logstash side and I started seeing parsing errors of my firewall logs. This was good news.
Now it appears that logstash is simply not creating an index in kibana. I am trying to solve that now.

Glad to see you're making progress 👍
Logstash creates indices in Elasticsearch, not in Kibana. By default, a new index is created at the beginning of every day.
In case you meant the Kibana the index pattern, that is true, Logstash does not create it, you must do it manually by following the instructions from the README.

By the way, is there any reason why you are sending data to Logstash and not directly to Elasticsearch?
If you are not performing any filtering or data transformation in your Logstash pipeline, you may as well simplify the data flow by skipping Logstash altogether.
(If you enabled TLS, you will need to copy the CA certificate to your Beat nodes for it to work. Example)

I plan on spring filtering once this is all working.  My Palo Alto firewall
logs have all the data in Messages and they are not broken out into KV
pairs.
On Sat, Sep 18, 2021 at 6:10 AM Antoine Cotten @.***>
wrote:

By the way, is there any reason why you are sending data to Logstash and
not directly to Elasticsearch?
If you are not performing any filtering or data transformation in your
Logstash pipeline, you may as well simplify the data flow by skipping
Logstash altogether.
(If you enabled TLS, you will need to copy the CA certificate to your Beat
nodes for it to work. Example
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_deviantony_docker-2Delk_blob_15e59455b2cf54d09e471d7ef309822b42f7e9ca_extensions_metricbeat_config_metricbeat.yml-23L38-2DL39&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=_LF9KXG4zooVh9xQo7bNg93ULhQtNU_WlQ0w8TLskiQ&s=vsoxHgdJ60Lhayj8MKEZpc8VCR8ud1blQEX7MychPuk&e=
)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_deviantony_docker-2Delk_issues_624-23issuecomment-2D922253324&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=_LF9KXG4zooVh9xQo7bNg93ULhQtNU_WlQ0w8TLskiQ&s=K1y5_xTO85rPAVsqiW1c230jz2ePmllWXlUZ0iLmzTc&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMNB64C73SLKV7OBG4IAZBTUCRQP5ANCNFSM5EHC4OIQ&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=_LF9KXG4zooVh9xQo7bNg93ULhQtNU_WlQ0w8TLskiQ&s=YaejtAdlIDr00aF64RY73x_ZIWKkHtmbG8KIBRCiLg4&e=
.
Triage notifications on the go with GitHub Mobile for iOS
https://urldefense.proofpoint.com/v2/url?u=https-3A__apps.apple.com_app_apple-2Dstore_id1477376905-3Fct-3Dnotification-2Demail-26mt-3D8-26pt-3D524675&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=_LF9KXG4zooVh9xQo7bNg93ULhQtNU_WlQ0w8TLskiQ&s=FcT51y0ZUWyk7BdmmtLPLogFVLKkDzj6-mJT6mbOY8g&e=
or Android
https://urldefense.proofpoint.com/v2/url?u=https-3A__play.google.com_store_apps_details-3Fid-3Dcom.github.android-26referrer-3Dutm-5Fcampaign-253Dnotification-2Demail-2526utm-5Fmedium-253Demail-2526utm-5Fsource-253Dgithub&d=DwMCaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=bVyA4ImNgL43Q2UXlCGr3sMBg1TcSClSpBCjQ8q9PH8&m=_LF9KXG4zooVh9xQo7bNg93ULhQtNU_WlQ0w8TLskiQ&s=vcsKGrDLZTm2vaNgB9y3MRJhLzFDqtxV392Ywri0AcI&e=.

--
Erik Witkop  |  DOD Systems Engineer | PCNSE CISSP GPEN
Palo Alto Networks  |  Boston, MA |  USA
Mobile:<PHONE_NUMBER>  | www.paloaltonetworks.com
https://www.paloaltonetworks.com/
https://www.paloaltonetworks.com/
https://www.linkedin.com/company/palo-alto-networks
https://www.facebook.com/PaloAltoNetworks/
https://twitter.com/PaloAltoNtwks
The content of this message is the proprietary and confidential property of
Palo Alto Networks, and should be treated as such. If you are not the
intended recipient and have received this message in error, please delete
this message from your computer system and notify me immediately by e-mail.
Any unauthorized use or distribution of the content of this message is
prohibited.

So I can confirm that logs are coming from FB to logstash. If you change the logstash codec to JSON or something, you will see a parsing error and you can see the actual syslog message. So that part is working. And now I have logstash talking to elasticsearch. However, I don't see anything on the "Logs" page of Kibaba.
logstash_1       | [2021-09-20T13:37:19,968][INFO ][logstash.outputs.elasticsearch][main] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["//elasticsearch:9200"]}
logstash_1       | [2021-09-20T13:37:19,977][WARN ][logstash.outputs.elasticsearch][main] ** WARNING ** Detected UNSAFE options in elasticsearch output configuration!
logstash_1       | ** WARNING ** You have enabled encryption but DISABLED certificate verification.
logstash_1       | ** WARNING ** To make sure your data is secure change :ssl_certificate_verification to true
logstash_1       | [2021-09-20T13:37:20,016][INFO ][logstash.outputs.elasticsearch][main] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[https://elastic:xxxxxx@elasticsearch:9200/]}}
kibana_1         | {"type":"log","@timestamp":"2021-09-20T13:37:20+00:00","tags":["info","savedobjects-service"],"pid":952,"message":"Starting saved objects migrations"}
logstash_1       | [2021-09-20T13:37:20,648][WARN ][logstash.outputs.elasticsearch][main] Restored connection to ES instance {:url=>"https://elastic:xxxxxx@elasticsearch:9200/"}
logstash_1       | [2021-09-20T13:37:20,732][INFO ][logstash.outputs.elasticsearch][main] Elasticsearch version determined (7.13.4) {:es_version=>7}
logstash_1       | [2021-09-20T13:37:20,734][WARN ][logstash.outputs.elasticsearch][main] Detected a 6.x and above cluster: the type event field won't be used to determine the document _type {:es_version=>7}
root@ip-192-168-45-101:~/docker-elk/logstash/pipeline# more logstash.conf
input {
beats {
port => 5044
ssl => false
client_inactivity_timeout => 300
codec => plain
}
}
############ FILTERS ###############
#filter {
dissect { mapping => { "message" => "<%{level}>%{} %{ts} %{loglevel} %{something} - [%{kvString}" } }
date { match => [ "ts", "ISO8601" ] }
kv { source => "kvString" field_split => ";" value_split => ":" trim_key => " " }
#}
Add your filters / logstash plugins configuration here
output {
elasticsearch {
hosts => ["elasticsearch:9200"]
user => "elastic"
password => "changeme"
ecs_compatibility => disabled
ssl => true
cacert => "config/elasticsearch-ca.pem"
ssl_certificate_verification => false
}

It is working now!!!!!!  I need to make a few changes to my logstash.conf file.  Here are the final results.
input {
beats {
port => 5044
ssl => false
client_inactivity_timeout => 300
codec => plain
}
}
############ FILTERS ###############
#filter {
dissect { mapping => { "message" => "<%{level}>%{} %{ts} %{loglevel} %{something} - [%{kvString}" } }
date { match => [ "ts", "ISO8601" ] }
kv { source => "kvString" field_split => ";" value_split => ":" trim_key => " " }
#}
Add your filters / logstash plugins configuration here
output {
elasticsearch {
hosts => ["elasticsearch:9200"]
user => "elastic"
password => "changeme"
ecs_compatibility => disabled
ssl => true
cacert => "config/elasticsearch-ca.pem"
ssl_certificate_verification => false
data_stream => "true"
}
stdout {
codec => rubydebug
}

@ewitkop-panw try the "discover" page of Kibana instead.

@ewitkop-panw sweet! So you didn't need to configure the codec at all, right?
If this issue is solved, feel free to close it.

Filebeat is my syslog listener. Then I send logs over to logstash.


Feat: Allow to compare with current buffer

Hey there,
It would be great to be able to compare the new output when we generate code with the previous when when text is selected.
At a high level it could be an interface similar to vim fugitive:

It does not need to be as complex but I think this would help where we can decide if we want to accept some / all the chunk and compare with what we had.
Best,

Hi @zippeurfou ,
Thank you for this suggestion. It's a duplicate of https://github.com/David-Kunz/gen.nvim/issues/18, let's move the discussion there.


Is  the Table.3  accuracy tested with dequantized weights, or tested on real accelerated quantized kernels?

For the zero-shot accuracy above, is the accuracy tested on dequantized weights, or tested on real accelerated quantized kernels?
If it is tested with dequantized weights, is there any accuracy difference between dequantized weights and real hardware quantized operations? Have you validated this?
@synxlin

Hi @vovoluck, thanks for your interests in QServe and QoQ.
The accuracy is tested with dequantized weights rather than the real accelerated kernels. We have verified that there is no accuracy difference between dequantized weights and real hardware quantized operations.


v4 super easy to use spinner suggestion

Hi, really like the first and the last one
https://github.com/lukehaas/css-loaders
demo :http://projects.lukehaas.me/css-loaders/

Those are indeed nice, but not sure it would make sense as part of Bootstrap core, since it does not currently have any spinner component, and spinners are generally only useful when you're doing dynamic changes to your pages / components, which we don't really do in core (unless I missed a specific place where they would fit naturally?)

Maybe Bootstrap will have a nice spinner with this PR : https://github.com/twbs/bootstrap/pull/17822

@patrickhlauke It's on the Big Picture list for v4 https://github.com/twbs/bootstrap/pull/17021

@MrGeneric ah, good spot. @mdo ?

A lot of these animations are animating properties which cause layout repainting and the layers they belong to are uploaded to the GPU. On mobile devices this is particularly expensive because CPUs are significantly less powerful than their desktop counterparts, meaning that the painting work takes longer; and the bandwidth between the CPU and GPU is limited. You can easily see this by turning on Paint flashing in Chrome > devtools > Rendering tab:

I do think these animations can be rewritten to a version which doesn't trigger repainting.
Sources:

https://www.html5rocks.com/en/tutorials/speed/high-performance-animations/


feat: forbid write apis when resources are managed by gateway

forbid create/update/delete organzation, team, user apis when DIRECT_SHARED_RESOURCE_MANAGEMENT_ENABLED is True
AAP-24301: Update 2.5 EA EDA API to error on endpoints that correspond to gateway-managed resources

@bzwei How do these remote resources get cleaned up once they are in the EDA Database? If there is no delete would there be some system task that will do periodic checks to cleanup resources by synchronizing with the Gateway.
If the Gateway has the UI for doing a create/update/delete which effects the Gateway DB why can't we teach our UI to be getting the list of these remote objects directly listed via the gateway end point. Our list is only going to be partial based on the logged in user. Why not have all the shared resources be stored in Gateway and where we need it we store a ref to the remote object e.g. If organization is remote we should have a remote_resource attribute that stores the value as
{{ GATEWAY_HOST }}/api/v1/organization/15
So in or database we can have references to external objects and not copies. As soon as we start storing copies we have to worry about it going stale. With references we only have a link in our database.
I am guessing eventually the Credentials and Credential Types will also end up as a Remote Resource and when the UI wants to attach them to the Activation it would get the current list from the Gateway and then use a link in our database. When the workers start activation they will make a REST API call to fetch the Credential and Credential Types and do the appropriate things with it and send the data to ansible-rulebook.

@bzwei How do these remote resources get cleaned up once they are in the EDA Database?
I tested and noticed the local database is in sync with the gateway even when the deletion occurs. There is no extra code to insert/delete the local db. The underly dab module must have the logic to keep them in sync.

Link companion patch https://github.com/ansible/awx/pull/15234


pdfpc: 4.1.1 -> 4.1.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pdfpc/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 4.1.2 with grep in /nix/store/5mwaxcqfbb807ywds98xl27rrwb51nv1-pdfpc-4.1.2
directory tree listing: https://gist.github.com/5767dc3e3f368aaecb0c729b053b9209

cc @pSub for testing

Success on x86_64-linux (full log)
Attempted: pdfpc
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/5mwaxcqfbb807ywds98xl27rrwb51nv1-pdfpc-4.1.2
shrinking /nix/store/5mwaxcqfbb807ywds98xl27rrwb51nv1-pdfpc-4.1.2/bin/.pdfpc-wrapped
gzipping man pages under /nix/store/5mwaxcqfbb807ywds98xl27rrwb51nv1-pdfpc-4.1.2/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/5mwaxcqfbb807ywds98xl27rrwb51nv1-pdfpc-4.1.2/bin
patching script interpreter paths in /nix/store/5mwaxcqfbb807ywds98xl27rrwb51nv1-pdfpc-4.1.2
checking for references to /build in /nix/store/5mwaxcqfbb807ywds98xl27rrwb51nv1-pdfpc-4.1.2...
/nix/store/5mwaxcqfbb807ywds98xl27rrwb51nv1-pdfpc-4.1.2

Success on x86_64-darwin (full log)
Attempted: pdfpc
Partial log (click to expand)
/nix/store/04j5b6ydp2v18chs88yfcmznfiycswb7-pdfpc-4.1.2

Success on aarch64-linux (full log)
Attempted: pdfpc
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/c2hcrk26x5cl94karp9jznsp1rpdy7yq-pdfpc-4.1.2
shrinking /nix/store/c2hcrk26x5cl94karp9jznsp1rpdy7yq-pdfpc-4.1.2/bin/.pdfpc-wrapped
gzipping man pages under /nix/store/c2hcrk26x5cl94karp9jznsp1rpdy7yq-pdfpc-4.1.2/share/man/
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/c2hcrk26x5cl94karp9jznsp1rpdy7yq-pdfpc-4.1.2/bin
patching script interpreter paths in /nix/store/c2hcrk26x5cl94karp9jznsp1rpdy7yq-pdfpc-4.1.2
checking for references to /build in /nix/store/c2hcrk26x5cl94karp9jznsp1rpdy7yq-pdfpc-4.1.2...
/nix/store/c2hcrk26x5cl94karp9jznsp1rpdy7yq-pdfpc-4.1.2


auth0-authentication

Simple showcase of how to authenticate users with with Auth0 (RS256 tokens), serverless function (AWS Lambda and Webtask.io) and Graphcool Schema Extensions (hot new feature currently in beta)

Thanks so much, this is an awesome PR 🙌


Slow generation with vLLM?

Hey there,
Is it expected that an AWQ model running within vLLM would have lower throughput than the non-quantized version?
Here is my quantization code:
from awq import AutoAWQForCausalLM
from transformers import AutoTokenizer
import torch

model_path = "./results/run5/merged"
quant_path = "./results/run5/merged-awq"
quant_config = {"zero_point": True, "q_group_size": 128, "w_bit": 4, "version": "GEMM"}

# Load model
# NOTE: pass safetensors=True to load safetensors
with torch.device("cuda:0"):
    print("Loading model")
    model = AutoAWQForCausalLM.from_pretrained(
        model_path, **{"low_cpu_mem_usage": False}
    )
    print("Loading tokenizer")
    tokenizer = AutoTokenizer.from_pretrained(
        "mistralai/Mistral-7B-v0.1", trust_remote_code=True
    )

    print("Quantizing")
    model.quantize(tokenizer, quant_config=quant_config)

    # Save quantized model
    # NOTE: pass safetensors=True to save quantized model weights as safetensors
    print("Saving quantized model")
    model.save_quantized(quant_path, safetensors=True)
    tokenizer.save_pretrained(quant_path)

print(f'Model is quantized and saved at "{quant_path}"')

And here is my vLLM code:
from vllm import LLM, SamplingParams

llm = LLM(model="./results/run5/merged-awq", quantization="AWQ")

sampling_params = SamplingParams(
    max_tokens=500,
    temperature=0,
)

ft_outputs = llm.generate(prompts, sampling_params=sampling_params)

There are 2000 inputs, averaging 100-400 input tokens and 1 output token (classification task). I'm running on an A100-80GB and getting ~40 generations per second with the base model, but only ~10 generations per second with the quantized version. Is this expected?

This performance is as expected. Quantized models are not faster than FP16 when you try to run 2k samples through at once because it is heavily compute bound.


New train

There is nothing significant here other than allowing for a developer to develop this against api.staging.roboflow.com and bumping the npm package number that we published

Brad's got meetings so going to auto merge to push new offline improvements on top, will leave branch alive for review after


Using gem Faker to set locale by factory

Problem this feature will solve
When I am using faker to generate factory attributes I find it difficult to set the "locale" for all the attributes of the factory.
With faker you can set the locale with Faker::Config.locale = locale (by default it uses rails-i18n locale) and then, when you call the generation methods on faker it will generate the output for the right format for the locale.
Ex:
FactoryBot.define do
  factory :user do
    # ...
    name { Faker::Name.name }
    postal_code { Faker::Address.postcode }
    phone_number { Faker::PhoneNumber.phone_number }
  end
end

For the phone_number attribute, faker will use the rails-i18n key en.faker.phone_number.formats (the default locale set is en).
Desired solution
The feature or change that would solve the problem
I would like to be able to set the faker locale for a factory, maybe this would be possible if an `around hook exists, using a transient attribute.
Ex:
FactoryBot.define do
  factory :user do
    arround do
      I18n.with_locale(evaluator.locale) do
        yield
      end
    end

    transient do
      locale {  I18n.locale }
    end

    # ...
    name { Faker::Name.name }
    postal_code { Faker::Address.postcode }
    phone_number { Faker::PhoneNumber.phone_number }
  end
end

Then you can easily generate users using locale "fr" and "en-US".
attributes_for(:user, locale: "fr")
# => {
          :name => "Dr Thomas Roché",
   :postal_code => "61331",
  :phone_number => "+33 2 55 61 87 68"
}

attributes_for(:user, locale: "en-US")
# => {
          :name => "Elliott Marquardt",
   :postal_code => "29958-7969",
  :phone_number => "520-256-2473"
}

Alternatives considered
Currently, I am setting the locale in the first attribute of the factory, for nested factories, but it's not very elegant...
FactoryBot.define do
  factory :user do
    # ...
    name { Faker::Name.name }
    postal_code { Faker::Address.postcode }
    phone_number { Faker::PhoneNumber.phone_number }
  end

  factory :user_fr do
    name {
      I18n.locale = 'fr'
      Faker::Name.name
    }
  end
end

Another solution is to set the locale before calling the factory, but it makes it very verbose...
let(:user) do
  I18n.with_locale('fr') do
    create(:user)
  end
end

Additional context
I would be happy to contribute to this feature if this is something you think is worth adding to the gem. This issue is very close to the gem Faker and the fake that you can't specify the "format" you want, for that you need to base the country in the locale.

I believe you can get the behavior you are looking for by using a custom initialize_with. That should allow you to construct the object and assign the attributes all within the I18n.with_locale block:
  factory :user do
    initialize_with do
      I18n.with_locale(locale) do
        new(attributes)
      end
    end

    transient do
      locale {  I18n.locale }
    end
  end

Nice, thank you for answering, since then I switch to FFaker which does not leverage i18n directly to generate data in a specific language/geo.
I will close the issue.


onduty config

Make a config for if you need to be on duty to access job clothing rooms or not.

@og23rd Supported in v3.6.0:  https://github.com/iLLeniumStudios/fivem-appearance/releases/download/v3.5.0/fivem-appearance.zip


Add more methods to memcachedClient

Add Increment, Touch, CompareAndSwap, and FlushAll methods to the underlying Memcache client.
Include associated wrappers for the exported MemcachedClient object.
What this PR does:
Increase the number of MemcachedClient methods accessible to consumers.
Which issue(s) this PR fixes:
This pull request addresses an issue in a private repository, so it may not be directly linkable.
Checklist

[x] Tests updated
[x] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@56quarters these add the additional methods we need to the memcached client. This should allow us to get off the fork we're using that ejects the underlying *memcache.Client client so we can use the wrapper directly.

@56quarters

I don't think it's necessary to split these methods between baseClient and MemcachedClient since they're pretty Memcached specific. It's fine to just put them right in MemcachedClient
I am not sure what it means in practice. Does it mean to change the signatures of the methods to be the same? Wouldn't it be beneficial in this case to maintain some level of dependency isolation?


If it's possible, PLEAAASE add camera stabilization and rotation

With stabilization this mod would be perfect for content creation! If the camera was being smoothed by the game itself and not a post process like in videos online, it would avoid the issue of zooming and cropping losing some quality.
My head naturally sits rotated slightly to the right. It's not by much, but it comes across strongly in VR videos. I'd love to have the option to rotate it slightly left so it's more often correctly upright, again without needing to crop and zoom to hide it.

Thanks for the feedback! I’m considering stabilization for the 1.2.0 update—it would help maintain quality. I’ll also consider adding an option to adjust the camera’s rotation for better alignment.

Thanks for the feedback! I’m considering stabilization for the 1.2.0 update—it would help maintain quality. I’ll also consider adding an option to adjust the camera’s rotation for better alignment.

WOOOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Best mod developer! My latest video would have looked a lot nicer with stabilization lol. I wish this mod came out sooner.

With stabilization this mod would be perfect for content creation! If the camera was being smoothed by the game itself and not a post process like in videos online, it would avoid the issue of zooming and cropping losing some quality.
My head naturally sits rotated slightly to the right. It's not by much, but it comes across strongly in VR videos. I'd love to have the option to rotate it slightly left so it's more often correctly upright, again without needing to crop and zoom to hide it.

Done, Enjoy

Thank you so much!!!!!
If you wanna add me to your special thanks, I'd rather be credited as WaveSmash instead of WaveSmashies. I really appreciate it!


"Negreni" , "Perii Vadului" , "Podișu" , "Răstoci" , "Rogna" , "Șasa" are listed in the drop-down menu

Description:
When user writes"Negreni" , "Perii Vadului" , "Podișu" , "Răstoci" , "Rogna" , "Șasa" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Negreni"

Expected results
The location appears in the drop-down menu as "Sat Negreni, SĂLAJ (Ileanda)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Perii Vadului"

Expected results
The location appears in the drop-down menu as "Sat Perii Vadului, SĂLAJ (Ileanda)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Podișu"

Expected results
The location appears in the drop-down menu as "Sat Podișu, SĂLAJ (Ileanda)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Răstoci"

Expected results
The location appears in the drop-down menu as "Sat Răstoci, SĂLAJ (Ileanda)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Write in the search bar "Rogna"

Expected results
The location appears in the drop-down menu as "Sat Rogna, SĂLAJ (Ileanda)".

Step 10
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 11
Write in the search bar "Șasa"

Expected results
The location appears in the drop-down menu as "Sat Șasa, SĂLAJ (Ileanda)".


[el] Machine learning tips and tricks

Hello everyone!
I started a new language directory for Greek (el). I also added some translations for the ML tips & tricks cheatsheet, with more on the way.
Cheers!

Thank you for your work and your pull request @Skarfrael, looking forward to seeing the Greek version of these guides!


filtering by classifier includes projects without that classifier

Describe the bug
If I

Search for "cms"
add a filter for the classifier "FRAMEWORK :: JUPYTER :: JUPYTERLAB :: EXTENSIONS"

Then I get 406 results, the top one being cms-bluebutton-sdk, but if I click through to that project I find that it does NOT have that classifier.

Expected behavior
That project (and others that don't have the classifier) should not be included in the search results
To Reproduce
see above
My Platform
NA
Additional context
NA

Thanks for the report. It does appear something is broken when combining classifiers with search keywords (it doesn't matter what classifier it is, you get the same results: https://pypi.org/search/?q=cms&o=&c=Natural+Language+%3A%3A+Afrikaans)


Documentation Request for Time-related Internals

Is your feature request related to a problem? Please describe.
I am trying to better understand eCAL's design/approach with respect to time and timestamps.
Describe the solution you'd like
I'd like there to be a section going over the details in the documentation here: https://continental.github.io/ecal/advanced/ecal_internals.html
Describe alternatives you've considered
Searching the documentation for "time" yielded some API docs, but the big picture is missing.
Additional context
I want to understand more details about the high-level design goals of the time-related aspects of eCAL. I'd also like to understand the specific function of libecaltime-localtime.so. Does eCAL have the notion of "simulated" time?

You are probably right, that should finally be added to the documentation.
But regarding your question about simulated time: Yes, eCAL supports it. Just put ecaltime-simtime in the ecal.ini. Then replay a measurement. The eCAL Time now follows the original timestamps from the measurement and is paused, when the player is paused. You have to manually turn in back to ecaltime-localtime though to get "normal" timestamps again, as we never got around implementing an automated switching method.

Hi @FlorianReimold that sounds interesting. Can you point me to where the simulated time gets updated for each measurement? I'm curious if it's happening in the playback tool or somewhere else.
Also, are timers effected by the simulated time?

The simulation time is transported as a primitive eCAL topic __sim_time__. You can see it in the monitor:

The eCAL::Time API features a function for sim-time-based sleeping. When you e.g. call eCAL::Time::sleep_for(std::chrono::seconds(1)) but have the player at 0.5 times realtime speed the sleep will actually take 2 seconds. If you pause the player in between the sleep is also paused and will return when you eventually un-pause the Player. When your time plugin is ecaltime-localtime the sleep will be performed in realtime.


Improve ThreeJS preview window

The embedded ThreeJS preview window here is from a simple example and doesn't have all the sophistication of @donmccurdy's excellent viewer.
Don I'm wondering if you would be willing to take a look at just the ThreeJS portion of this extension and see if there are improvements that could be made here?  The bulk of the code is in threeView.js, with a tiny bit of help from an HTML and a CSS file in the same folder.
To get a dev environment going, you install VS Code, click "Open Folder" on a clone of this repo, and hit F5 to launch the extension into the debugger.  A second copy of VSCode opens with the extension running.  You may want to edit user preferences on that copy to set your default preview engine to be ThreeJS instead of Babylon or Cesium.  Load a glTF (non-GLB) model into the editor and hit ALT-G to preview.  Not sure if that keybinding is the same on a Mac, actually I don't have a Mac here to test my extension so please report any Mac-specific bugs you find.  With the preview window open, getting to DevTools is a bit tricky, but I have instructions here.  As always, code contributions require a CLA.
Totally understand if you have no time to look at this.  Thought it wouldn't hurt at least to ask 😄

Anything particular in mind? Animation controls per #39 would be nice I think... presumably you want to keep the available options consistent across each viewer?

Re-thinking this in light of recent comments on KhronosGroup/glTF#1081.  Maybe I should try to carve out the glTF previewing portion of this plugin, including the ThreeJS view, and turn them into a sub-project called gltf-viewer-widget.  The glTF viewer widget would include multiple engines for previewing, and could be included as the visualization for your web-based glTF viewer, included here for the VSCode preview window, and maybe elsewhere.  Could turn into a lot of work, we would need to be sure it's worth it to do this.

This issue is vague, but improvements are ongoing.


[Question] Launching from code.

Question
There are only exmaples of launching this project as gradio service, or launch from cli. Can you provide examples of how to launch this project inside code?

https://github.com/haotian-liu/LLaVA/blob/main/llava/serve/cli.py
This cli script can be use

@rossaai I just started to use subprocess to make cli calls from my code.


⚠ ClamAV has degraded performance

In f661d45, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 185 ms

Resolved: ClamAV performance has improved in 15a5471 after 5 minutes.


[LogBox] Add LogBox.isIgnoredLog() for expo remote logging integration

Summary
In Expo environment, we overwrite console log handlers and send logs to CLI terminal or Snack remote console. If users use LogBox.ignoreLogs() to suppress some logs, the log will suppress from LogBox but still send to CLI terminal. Toward this problem, the PR introduces a LogBox.isIgnoredLog() function for us to check whether we should ignore the log entry.
This PR will help us to unblock and fix the problem mentioned in https://github.com/facebook/react-native/issues/33557#issuecomment-1137706990. (with example included)
Changelog
[General] [Added] - Add LogBox.isIgnoredLog() function to indicate whether a log is ignored
Test Plan
Unit Test
 PASS  Libraries/LogBox/__tests__/LogBox-test.js
  LogBox
    ✓ `isIgnoredLog` returns true for ignored log (4 ms)
    ✓ `isIgnoredLog` returns true for regexp based ignored log (3 ms)
    ✓ `isIgnoredLog` returns true for any messages when `ignoreAllLogs` was called (3 ms)
    ✓ `isIgnoredLog` returns false for non-matched ignored log (4 ms)
    ✓ `isIgnoredLog` returns false when throwing exception from log parser. (1 ms)

It seems that the /rebase command is not working properly... :/
@Kudo, could you try and rebase the PR? I should have fixed the CI issues. Thank you so much!

rebased. thanks for helping the review!

there looks like a network issue from ci job. i'm rebasing again to test again.

This PR will help us to unblock and fix the problem mentioned in https://github.com/facebook/react-native/issues/33557#issuecomment-1137706990. (with example included)

I also want to call out that the fix for this issue is not to ignore the warning. See the comment I left on the post.

Hm, I think that LogBox.ignoreLogs is supposed to also silence the logs to the console. Looking at the code, it appears that we do this for console.warn but only do it for console.error if it's from the warning module.

please let me describe the problem clearly.

at first, LogBox.install() overwrites console.warn/console.error, so logs will pass to LogBox.
then in expo environment, we overwrites console.warn/console.error again for remote logging, e.g. in snack.expo.dev, we pass logs to snack remote console. we will pass logs both to original log handler (LogBox) and remote console.

for the code snippet, LogBox.ignoreLogs(['foo']); console.warn('foo');. the message will be ignored by LogBox but show in expo remote console. so i'm thinking to propose LogBox.isIgnoredLog() for us to check whether the log is explicitly ignored by developers and should not pass to remote console.
at first glance, the LogBox has some internal ignored rules as you mentioned. for instance, message starts with (ADVICE) might be ignored and message doesn't start with Warning:  will be ignored by console.error. i was thinking whether we should follow the complex logic as LogBox. what we need is to ignore the logs where developers explicitly ignore. in this case, if we think LogBox.ignoreLogs as LogBox.ignoreAdditionalLogs, then the current implementation of LogBox.isIgnoredLog is just something like LogBox.isIgnoredAdditionalLog.
hopefully this is clear to you and i am open to the implementation. let me know what's your thought and makes sense to you.

This PR will help us to unblock and fix the problem mentioned in #33557 (comment). (with example included)

I also want to call out that the fix for this issue is not to ignore the warning. See the comment I left on the post.

yep! i like your reply for deprecated-react-native-prop-types approach. the pr is not fixing the original issue. it's mainly addressing the expo remote console issue where LogBox.ignoreLogs(['foo']); console.warn('foo'); unexpectedly shown in the remote console.

Instead of overwriting higher in the stack and passing to both, can you overwrite lower in the stack (i.e. before LogBox)? Then LogBox will be able to handle all of the interpolation and filtering before it gets passed to a lower level. That's how we handle the logs in Metro and it would probably be weird for users if they see a log in Metro but not in other tools.

from https://github.com/facebook/react-native/commit/8abe737068a5 of<EMAIL_ADDRESS>LogBox.install happens in InitializeCore. that's a pretty early stage at metro getModulesRunBeforeMainModule. i am afraid something is not yet available at this stage. especially we have to access some native modules to get the remote logging endpoint to send logs.

@Kudo you have access to the bundle though right? You can inject stdio and lazily init the native modules?

@Kudo you have access to the bundler though right? You can inject stdio and lazily init the native modules?

@rickhanlonii that's achievable. it's just requiring additional setup. i may need to add an injection stdio script at metro's getModulesRunBeforeMainModule right before react-native InitializeCore. i was thinking if there're any solutions without touching metro. if there are no better solutions, i'm fine with it. do you have any idea in mind?

I think that's probably the best thing to do here since you're instrumenting the low-level stdio. That means you won't have to re-implement all of the LogBox error parsing logic, which is pretty fragile and tied to specific React/React Native versions.

I caught up with @Kudo about this on a call, and it occurred to me that we may want to keep the current behavior in Expo projects - in part because of the complexity of the workaround (configuring Metro to inject code before InitializeCore) and also because it's not clear to me to me that it's always desirable to have LogBox.ignoreLogs prevent the default behavior of console.warn. It might be more predictable and flexible to treat these outputs distinctly - so you would filter LogBox with ignoreLogs and console by wrapping calls to console methods or patching them (as you would do in any other JS environment).
What do you think? I don't want to diverge from React Native on this point - would you be open to a PR to change this behavior in React Native?

Hm, yeah good point. Let me ask @sshic, who has been working close to the error handling than I have.

I think this is related to the purpose of LogBox, specifically is it for filtering all logs for all use cases or just for adding extra functionality for logging? I don't have a definite answer, nor I know what our thoughts were when LogBox was firstly introduced. In general I would support giving users/developers more flexibility, in this case letting LogBox.ignoreLogs filters only for LogBox data makes sense to me, but I slightly worry that it can be confusing for users/developers that calling LogBox.ignoreLogs()won't ignore logs in all places and they have to find other ways (for example checking with the new API LogBox.isIgnoredLog()) to  manually achieve this. What do you think @brentvatne @Kudo ?

Yeah great questions @sshic. When I implemented ignoreLogs it was originally just to move console.ignoreYellowBox over to LogBox. When I added the filtering for console messages too, my thought process was: Developers probably don't want to configure hiding logs twice, so the LogBox method can handle both.
Thinking more about this now, I think I made a mistake, and we actually should never hide console errors and warnings. The referenced issue #33557 is a great reason why - the correct fix for this is not to ignore the errors, it's to address the deprecation / removal of the API. Allowing an easy ignoreLog method to hide the problem made this migration much more painful.
So I think the right next steps would be:

Update LogBox to never filter console methods
Do not expose which logs are filtered in LogBox
Recommend that Expo does not add console filtering either

If folks want to override console methods to filter, can't stop them but it's not recommended.
What do you think @sshic @brentvatne @Kudo

@rickhanlonii - I agree with your reasoning and proposed next steps!

@rickhanlonii @Kudo Should we then close this PR?

thanks @cipolleschi! i would close this pr.
please try to follow up the mentioned next steps when you get a chance. thank you very much!


.sortField doesn't work with remote data ?

Hi, remote data settings for tom-select does seem to corrupt original order of json response.
I am using code below:
      let options = {
	      plugins: ['change_listener'],
	      render: {}
      };

      options.sortField = 'obchodne_meno'
      options.valueField = 'obchodne_meno';
      options.labelField = 'obchodne_meno';
      options.searchField = 'obchodne_meno';
      options.load = function (query, callback) {
      let url = `${Routes.my_path()}?str=${encodeURIComponent(query)}`;
      fetch(url).then(response => response.json()).then(json => {
	      callback(json.items);
      }).catch(() => {
	      callback();
      });
      }

      new TomSelect(select, options);

sortField doesn't seem to do anything and i am not setting any order in options. What's the catch ?

Can you give me a little more to work with? Example JSON for a query along with the display you see vs the display you'd like to see?

Actually, I think this is what you're looking for
...
 fetch(url).then(response => response.json()).then(json => {
     this.clearOptions(); // <-- clear options from previous queries
     callback(json.items);
}).catch(() => {
...

Sorry, it didn't work.
Here is the example: https://jsfiddle.net/mArtinko5MB/k7nbsf5a/59/
What is expected: Write "ale" into selectbox so it starts request.
expected order is:

"Alena Tsomethingova"
"Alena Komethingova"
"Alena Zanythingá"

But it isn't ( it's Zanythingá, Komethingova, Tsomethingova).
The funny thing is that when i change values ( names ) to Tsomething, Ksomething, Zsomething and write "ale" into SB, it suddenly works and order is as expected. I have no idea what is going on. Bug is somehow connected to how string is computed in sort function.

Shoot, that's right.

Unless present, a special $score field will be automatically added to the beginning of the sort list. This will make results sorted primarily by match quality (descending).

https://tom-select.js.org/docs/#sortfield

The solution is to make sure $score is in the sortField setting:
 sortField: [{field:'name'},{field:'$score'}],

or
 sortField: [{field:'$order'},{field:'$score'}],

Great, it works. Thanks !


Add an exception to the PR signoff

This is in order to avoid holding a PR for too long. A PR can always be reverted or edited at a further date.

👍

Sure thing. :+1:


pull request

Describe your PR and link to any relevant issues.
I have:

[x] Added tests covering the bug / feature (see testing)
[x] Updated any relevant documentation (see docs)

pull request


Rotate large image on right click

Rotating through multiple images while in the large image mode would be nice. Currently, if I want to view the next image of a given tile in large image mode the sequence is as follows:

Double-click to return to the dashboard (all tiles reset to index 0)
Right-click the tile until the image desired image is visible
Double-click tile to enlarge

This is not a problem until the desired image has text to determine which image is shown (timestamp data) which is too small to read in tile form.
Example of a tile's images for 3 days of forecast information:
 [     "NOAA FORECAST",     "https://www.wpc.ncep.noaa.gov/NationalForecastChart/staticmaps/noaad1.png",     "https://www.wpc.ncep.noaa.gov/NationalForecastChart/staticmaps/noaad2.png",     "https://www.wpc.ncep.noaa.gov/NationalForecastChart/staticmaps/noaad3.png",   ]
In looking at the code, I did not see an easy way to add this. It would take either looking up the URL to determine which tile array is selected or passing a value of the given aIMG[i][aIdx[i]] when replacing the backgroundImage to know which URL to index.
Thank you for this great dashboard!

It is a good feature. Let me look into this. I will let you  know once is done. Thanks. 73

Hi Travis,
The feature you requested was added in the latest .html file. This is the only file you need to update with the github repo version.
73 de Pablo, VA3HDL


Issue with Main class not accessing roster

Summary
I have passed codecrunch level1-5, however when I try to run my Main class, the roster is correctly generated but I cannot access the data using getGrade(). Optional.empty is always returned
Since I have passed 5/6 test cases on cc, I assumed that my design is correct thus far.
Description:
Clarifications or details with respect to the issue you are facing
Code Snippets
    System.out.println(roster); //check if roster is generated correctly
    System.out.println(roster.getGrade("Jack", "CS2030", "Lab4"));

After adding all the data into the roster, I did ^ to check whether the roster was correctly generated. Output generated is below
Screenshots

Any help is appreciated, thank you!

Hi, please show how u defined your Main class and how you implemented getGrade.

Did you reassign your Roster?

roster = roster.add("Jack", "CS2040", "Lab4");

Since Roster is immutable, just performing
roster.add("Jack", "CS2040", "Lab4");

will not update roster.

I have the same issue as well. Somehow if i directly key in every single line, it works, but it just doesnt work when I use the scanner to get user input. ive tried bufferedreader as an alternative user input method, still doesnt work :(

The issue definitely lies with getGrade in your Roster if it is only returning Optional.empty for all queries. You might want to check your implementation again.

getGrade should be returning a String and not an Optional, maybe check how you are implementing getGrade again

Maybe your getGrade() is not evaluating as intended

I think you need to check your getGrade() method, since it is showing that all the records do not exist, I think there is an error in the logic behind the code.

^agree with the rest, definitely an issue with you getGrade() method as it is returning an Optional.empty for all queries and hence returning the orElse value instead

The return type of getGrade should be a string and not optional. After you change, the code should be work already

I have solved the problem, thank you all!

I think you should check your getGrade() method.
Nice to hear that you have solved it

@delulu04
You might want to close this issue since you're done with it...


feat(ast_build): implement binary operations (modulo, like, ilike. not_like, not_ilike)

Hello, implemented AST builders for Binary Operators Modulo, Like, ILike, NotLike, NotILike.
I didn't implement XOR because the test below failed when I implemented it.
let actual = (col("id").gt(num(10))).xor(col("id").lt(num(20)));
let expected = "id > 10 XOR id < 20"; // id > (10 XOR id) < 20
test_expr(actual, expected);
// thread 'ast_builder::expr::binary_op::tests::binary_op' panicked at 'assertion failed: `(left == right)`
// left: `Ok(BinaryOp { left: BinaryOp { left: Identifier("id"), op: Gt, right: Literal(Number(BigDecimal("10"))) }, op: Xor, right: BinaryOp { left: Identifier("id"), op: Lt, right: Literal(Number(BigDecimal("20"))) } })`,
// right: `Ok(BinaryOp { left: BinaryOp { left: Identifier("id"), op: Gt, right: BinaryOp { left: Literal(Number(BigDecimal("10"))), op: Xor, right: Identifier("id") } }, op: Lt, right: Literal(Number(BigDecimal("20"))) })`',

Please leave an RC if there's any problem, suggestion or conflict at main branch.
Thank you.
This PR closes #685

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

35 of 35 (100.0%)  changed or added relevant lines in 1 file are covered.
12 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.02%) to 97.857%

Files with Coverage Reduction
New Missed Lines
%

core/src/data/interval/mod.rs
1
99.74%

core/src/executor/aggregate/mod.rs
11
92.2%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
28862

Relevant Lines:
29494

💛  - Coveralls


feat: redesign tweaks

Update:

Device status badge based on "online" property instead of time

If online property not present, fallback into previous system with time (lastSeen)

Tags list to flex layout
User and Device list to flex layout with gaps
User and Device cards uses base color
classes.ts got formatted with Prettier

Removed:

Outline from User and Device cards

Screenshots of modifications:

Looks good. I'm on holiday at the moment, but I'll rev up a new version as soon as I get back and include this PR.
Note that given that headscale is introducing many breaking changes, I am also ok with the next release not being backwards compatible.


Out of memory after serveral epochs

hi ,bro . I am using you model about spGat ,but out of memory after serveral epochs .

@a519552508  hi, do you know how to solve it?


Use singular number for all feature names

features => feature
users => user
Neither of these features have yet been included in a release, so it's
ok to rename them.

Looks like rustc itself is broken for uclibc .  https://github.com/rust-lang/rust/commit/33fd73fedeb5cd61dbbb7562fd927c0b6994653a .

@asomers thanks for filing https://github.com/rust-lang/rust/issues/95866.
FYI @skrap.

Ok, I think I got CI straightened out.

bors retry


Was working properly, now isn't

I found this extension and thought it would be an easy way for my wife to disable the Pi-Hole when needed.  I installed it on my laptop to test and loved it.  I then installed on her laptop as well with identical settings and assumed everything was good to go.  Just tried to disable now from my laptop, a couple days later, and it is not working at all.  Is there a conflict when installed on multiple computers?  Both computers running Chrome browsers in Windows 10.
EDIT:
I wasn't 100% accurate in my writing before I accidentally hit submit.  The Pi-Hole does in fact disable, but the extension quickly reverts to on, giving the appearance that it is not disabled.

Hi,
this probably related to this issue: https://github.com/badsgahhl/pihole-browser-extension/issues/54
The current version of PiHole seems to have a bug and doesn't return the correct PiHole status which is then displayed wrong in the extension.

I had seen that, but thought I had a completely different problem due to the timing of my adding a second computer to control machines.  Will keep an eye out for updates.
But just to be clear--when everything is working properly, I should be able to control the Pi-Hole from either of the 2 laptops?  And the status will show properly on both?
Thank you very much!
On Saturday, January 8, 2022, 10:04:45 AM EST, Pascal Glaser @.***> wrote:
Hi,
this probably related to this issue: #54
The current version of PiHole seems to have a bug and doesn't return the correct PiHole status which is then displayed wrong in the extension.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

Same issue here: using latest version of PiHole DNS (as of today).. Extension shoes a successful connection, but toggling to On/off (either in the extension or in WebGUI) does not get reflected in the opposite side.

But just to be clear--when everything is working properly, I should be able to control the Pi-Hole from either of the 2 laptops?  And the status will show properly on both?

Yes it will be correct after the next PiHole update. The usage of multiple extensions with one PiHole should just work like you would expect.

Same issue here: using latest version of PiHole DNS (as of today).. Extension shows a successful connection, but toggling to On/off (either in the extension or in WebGUI) does not get reflected in the opposite side

See #54 for further infos.


Include regex

Hey there,
I added the option -include to provide a regex (default: .*) which has to match the container name in order to register the container.
$ /usr/local/bin/registrator -include="reg_.*" -ip dockerhost consul://consul.service.consul:8500
2015/11/03 14:52:57 Starting registrator v7-dev ...
2015/11/03 14:52:57 Forcing host IP to dockerhost
2015/11/03 14:52:57 Using consul adapter: consul://consul.service.consul:8500
2015/11/03 14:52:57 Connecting to backend (0/0)
2015/11/03 14:52:57 consul: current leader  <IP_ADDRESS>:8300
2015/11/03 14:52:57 Listening for Docker events ...
2015/11/03 14:52:57 Syncing services on 4 containers
2015/11/03 14:52:57 Container  /base_registrator_1  does not match  reg_.*
2015/11/03 14:52:57 Container  /registry_HyperRegUI_1  does not match  reg_.*
2015/11/03 14:52:57 Container  /base_consul_1  does not match  reg_.*
2015/11/03 14:52:57 Container  /registry_registry_1  does not match  reg_.*
2015/11/03 14:53:17 Container  /furious_bartik  does not match  reg_.*
2015/11/03 14:53:36 added: 743bfee00f87 registrator:reg_www:80

An additional -exclude might be cool as well.
Cheers
Christian

Maybe I should change the handed over includeRegex into a 'struct filter` to which all fields can be added. What do you guys think? I am quite fresh in go. :)

Closed in favour of #284


Upgrade AssertJ 3.25.0 -> 3.25.1

This PR contains the following updates:

Package
Type
Update
Change

AssertJ (source)
import
patch
3.25.0 -> 3.25.1

[ ] If you want to rebase/retry this PR, check this box

The Java Platform team wishes you a happy festive period. Here is the suggested commit message:
Upgrade AssertJ 3.25.0 -> 3.25.1

See:
- https://github.com/assertj/assertj/releases/tag/assertj-build-3.25.1
- https://github.com/assertj/assertj/compare/assertj-build-3.25.0...assertj-build-3.25.1

Renovate be like

Header generated and modified from Sweaterify.


Minified JS not parseable by Firefox .. webkit works :: error: SyntaxError: invalid regular expression flag r"

Minify commit/version: 2.1.7
PHP version: 5.4.24

I have a lot of JS and when I minify it, it breaks. It cannot be parsed by
Firefox anymore

the error is: "SyntaxError: invalid regular expression flag r"

---

I dont have a minimal sample yet but ill try to produce that as well

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 6 Apr 2014 at 2:09

Use a pastebin. I need the unminified source.

Original comment by<EMAIL_ADDRESS>on 7 Apr 2014 at 2:50

else{obj[atn]=atv;};});};};if(obj){obj=$.extend((txt!=''?new
String(txt):{}),obj||{});txt=(obj.text)?([obj.text||'']).concat([txt]):txt;if(tx
t)obj.text=txt;txt='';};var
out=obj||txt;if(extended){if(txt)out={};txt=out.text||txt||'';if(txt)out.text=tx
t;if(!simple)out=myArr(out);};return out;};var jsVar=function(s){return
String(s||'').replace(/-/g,"_");};function isNum(s){var
regexp=/^((-)?([0-9]+)(([\.\,]{0,1})([0-9]+))?$)/return(typeof
s=="number")||regexp.test(String((s&&typeof
s=="string")?jQuery.trim(s):''));};var
myArr=function(o){if(!$.isArray(o))o=[o];o.length=o.length;return o;};if(typeof
xml=='string')xml=$.text2xml(xml);if(!xml.nodeType)return
null;if(xml.nodeType==3||xml.nodeType==4)return xml.nodeValue;var
root=(xml.nodeType==9)?xml.documentElement:xml;var
out=parseXML(root,true);xml=null;root=null;return
out;},text2xml:function(str){return $.parseXML(str);}});})(jQuery);;var
Configuration={"locations":{"muc":{"details":{"name":"Munich","gps":{"latitude":
48.353559,"longitude":11.782019}},"rooms":{"VC-MUCDC4OskarMaria@domain.com":{"na
me":"KarlValentin","seats":20},"MUC-DC1ThereseGiehse@domain.com":{"name":"herese
 Giese (DC1)","seats":20},"MUC-DC2GabrieleMuente@domain.com":{"name":"Gabriele
Münter (DC2)","seats":20},"MUC-DC3Franzvon@domain.com":{"name":"Franz von
Lenbach (DC3)","seats":20},"VC-MUCDC4OskarMaria@domain.com":{"name":"Oskar
Maria Graf (DC4)","seats":20},"MUC-FranzMarc@domain.com":{"name":"Franz
Marc","seats":20},"MUC-SeppMoser@domain.com":{"name":"Sepp
Moser","seats":20},"MUC-KarlValentin@domain.com":{"name":"Karl
Valentin","seats":20},"MUC-CarlOrff@domain.com":{"name":"Carl
Orff","seats":20},"VC-MUCLieslKarlstadt@domain.com":{"name":"Liesl Karlstadt
(VC)","seats":20}}},"cgn":{"details":{"name":"Cologne","gps":{"latitude":50.9413
03,"longitude":6.958166}},"rooms":{"CGNAgnes@domain.com":{"name":"Agnes","seats"
:5,"has":["Screen","WiFi","Whiteboard"]},"CGNAlderaan@domain.com":{"name":"Alder
aan","preferForClients":true,"seats":3,"has":["Whiteboard","WiFi","Phone"]},"CGN
Dagobah@domain.com":{"name":"Dagobah","preferForClients":true,"seats":7,"has":["
Whiteboard","WiFi","Phone"]},"CGNEigelstein@domain.com":{"name":"Eigelstein","se
ats":7,"has":["Whiteboard","WiFi","Phone","Kicker"]},"CGNEndor@domain.com":{"nam
e":"Endor","preferForClients":true,"seats":6,"has":["Screen","mobile
Video","WiFi","Phone"]},"CGNHoth@domain.com":{"name":"Hoth","preferForClients":t
rue,"seats":6,"has":["Screen","WiFi","Phone"]},"CGNKorriban@domain.com":{"name":
"Korriban","preferForClients":true,"seats":7,"has":["Whiteboard","WiFi","Phone"]
},"CGNKwartierLataeng@domain.com":{"name":"Kwartier
<EMAIL_ADDRESS>":{"name":"Mediapark","seats":16,"has":["Phone","Screen","Video","WiFi"]},"CGNMo
sEisley@domain.com":{"name":"Mos
Eisley","preferForClients":true,"seats":40,"has":["projector
screen","wifi","mobile
video"]},"CGNSeverin@domain.com":{"name":"Severin","seats":6,"has":["Phone","Scr
een"]},"CGNYavin@domain.com":{"name":"Yavin","preferForClients":true,"seats":3,"
has":["Phone","Video","WiFi","Whiteboard"]}}}},"version":"1.1","url":"./proxy.ph
p?TARGET=https://webmail.domain.com/ews/exchange.asmx&DOMAIN=domain","startWithQ
uickbook":true,"showQuickbookButton":true,"minTime":7,"maxTime":20,"roomColors":
["#1D1D1D","#DE2728","#21ADDD"],"minColumnWidth":78,"defaultNumberOfPersons":3,"
defaultMeetingTopic":"Quickbooked","defaultMeetingOffsetMinutes":10,"defaultMeet
ingDuration":"00:30"};;function RGBColor(color_string)

Original comment by<EMAIL_ADDRESS>on 6 Apr 2014 at 2:13

[deleted comment]


SS-Kotlin incompatibility

The plugin stops working completely when used with SS-Kotlin (it's a SS-FancyDrop's dependency)
LOG: click here
How to reproduce:

1.16.x paper server
install Trhologram + SS-FancyDrops + SS-Kotlin

Idk the source of the problem so I opened the issue in both places
the issue in ss-kotlin is >HERE<

Fixed
Please download the latest actions build here https://github.com/Arasple/TrHologram/actions/runs/912113778


how can default values be set based on private attributes

I noticed that the current implementation of default values passes in self to give the Proc access to it's attributes. Since it is possible to have private attributes, how would you make defaults based on these attributes without having to reach out to send?
It would be an option to evaluate the Block in the context of the record to get direct access to the attributes.

I wrote an example spec to show illustrate the situation. Since I don't know how to reference that code in a commit from my source I added the relevant details directly:
class Page
  include Virtus

  attribute :published,    Boolean, :accessor => :private
  attribute :editor_title, String, :default => lambda { |post, attribute|
    post.published? ? post.title : "UNPUBLISHED: #{post.title}"
  }

  def initialize(published = false)
    @published = published
  end
end

describe Page do
  describe '#editor_title' do
    before { subject.title = 'Truly Awesome' }

    context 'published page' do
      subject { Page.new(true) }

      its(:editor_title) { should eql('Truly Awesome') }
    end

    context 'unpublished page' do
      subject { Page.new(false) }

      its(:editor_title) { should eql('UNPUBLISHED: Truly Awesome') }
    end
  end
end

I suppose we could use instance_exec to pass in the same arguments and evaluate it within the context of the current object.
The only downside is it's going to be slow. Maybe not quite so slow on 1.9, but in 1.8 instance_exec is emulated by backports using some hackery that will probably impact it. We should probably benchmark this if we decide to go this route.
Another option, one that I think may be cleaner, is offer the ability to specify a method name for the default as a Symbol. Then that method will be executed and responsible for returning the default value to use. It can access private methods and do whatever it needs.
Of course this may present a problem if we ever have a real Symbol type, because someone may want to specify the default value as a Symbol that doesn't correspond to a method name. I guess we'd have the same problem now if we ever added a Proc type, so perhaps we shouldn't worry about it anyway.

I really like the second option. If the default is more than a simple value using Procs gets messy very fast anyways. If the problem regarding the "real-symbol" type is eminent it would be possible to add two options:
1.) to directly set the value like: :default => 20
2.) another one to use when a callable is involved: :default_proc => :default_editor_title or :default_proc => lambda {}

I attached a sample implementation, which lets you supply a symbol to calculate the default value with a method call. This currently prevents symbol values as default values. They could still be set with the proc form :default => lambda { :offline } tough.

I like the idea of passing a method name which will return the default value. We can always perform some basic validation of this name to make sure it doesn't conflict with another attribute, for example:
class Page
  include Virtus

  attribute :title,   String
  attribute :other, String, :default => :title
end

This would throw an exception (or just display a warning) saying that :title is already defined and it's the attribute reader method. Anything else will be accepted if the object respond to the method name, obviously. Checking it from the other side will be required too - so every attribute initialization will have to check if there's no other attribute with default value set to a method name that is the same as the attribute's name.
I do plan to add Symbol type so proper validations is required here.

@emmanuel do I remember correctly that this was fixed by one of your recent refactorings?

@senny this is now supported via default value from a symbol, see here

@solnic I know this may be a bit late, but we could allow something like:
attribute :title, String, :default => method(:default_title)

That removes the conflict with Symbol defaults, and IMHO may be cleaner than just a plain Symbol. It removes some ambiguity.

That would require that the #default_title method was defined before the attribute was declared. Also, subsequent redefinition of the method would not be respected.
Just a thought.
On Feb 25, 2012, at 10:31 AM, Dan<EMAIL_ADDRESS>wrote:

@solnic I know this may be a bit late, but we could allow something like:
attribute :title, String, :default => method(:default_title)

That removes the conflict with Symbol defaults, and IMHO may be cleaner than just a plain Symbol. It removes some ambiguity.

Reply to this email directly or view it on GitHub:
https://github.com/solnic/virtus/issues/32#issuecomment-4174930

@dkubb true but given what @emmanuel wrote it wouldn't be a good solution + more typing for 'the end-user'

@emmanuel oh right, good point. I hadn't thought about that. I guess that wouldn't be the best idea then.


Lfw_Dir Error

How to set the lfw_batch_size  correctly. please Can you mention the batch_size how much i need to set?

Dear dheeru999, where can I find the lfw-pairs.txt？ did you download it from the web?

ur having it in the code itself .
https://github.com/davidsandberg/facenet/blob/master/data/pairs.txt


cmake error with "fopen_s"

Hi there,
I have recently encountered a cmake error that: "error: identifier 'fopen_s' is undefined" in the process of compiling gmpm. I didn't quite understand the cause of the error. How can I solve this problem? Thank you so much in advance
And my system info should be as: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, nvidia driver Version: 515.65.01, CUDA Version: 11.7

Might be just an include issue. Try including stdio.h in gmpm.cu.
(But you are lucky if that's the only issue, newest version is not tested agains gcc.)

#include <stdio.h>
#ifdef __unix
#define fopen_s(pFile,filename,mode) ((*(pFile))=fopen((filename),(mode)))==NULL
#endif
Try add these lines.


Warmup section in DoWorkoutScreen

Have a way to configure which first exercises are considered warmup. In NextExerciseCooldownScreen show different text (example: "Currently doing warmup exercise ...")

Categorize exercises (first section -> biceps, second section -> triceps, etc...) and show custom UI based on the sections.


Working with JSON files separating data by comma

This is suggestion, hope to be considered.
I was able to read/write JSON files using serde-json, but the issues I've is:

I can not read JSON files from other sources, where the records are separated by comma , with
StreamDeserializer we I can read only the files written by serde or the first record only if the json file is from other sources, where records are seperated by comma.

The file I can write, is not separating the records by , so I can not use it properly in some other areas here they need the elements to be separated by comma.

Thanks

Here is how I would recommend reading and writing comma separated JSON records.
#[macro_use]
extern crate serde_derive;

extern crate serde;
extern crate serde_json;

use serde::Serialize;
use std::error::Error;
use std::io::{self, Read, Write};

#[derive(Serialize, Deserialize, Debug)]
struct Record {
    id: u64,
}

fn main() -> Result<(), Box<Error>> {
    let input = br#"{"id":0}, {"id":1}, {"id":2}"#;
    let mut cursor = io::Cursor::new(input);

    let mut records = Vec::new();
    loop {
        match serde_json::Deserializer::from_reader(&mut cursor)
            .into_iter::<Record>()
            .next()
        {
            Some(record) => records.push(record?),
            None => break,
        }
        let mut comma = [0];
        if cursor.read(&mut comma)? < 1 {
            break;
        }
        if comma[0] != b',' {
            return Err("expected comma".into());
        }
    }

    println!("{:?}\n", records);

    let mut out = Vec::new();
    for record in records {
        record.serialize(&mut serde_json::Serializer::new(&mut out))?;
        write!(out, ",")?;
    }

    println!("{}\n", String::from_utf8(out)?);
    Ok(())
}


Ability to specify Jib version.

Currently, Jib builder always use the latest version of the released plugin. For consistency/reproducibility, user may want to specify a specific version of Jib.
Add JIB_VERSION argument and default to RELEASE.
In the Jib step, use plugin coordinate com.google.cloud.tools:jib-maven-plugin:${JIB_VERSON}:build

Sounds good! Will add this in

hmm, i wonder if the version here will override the actual plugin version specified by the pom?
another way of doing this to specify the plugin version in the build file. that's actually really good too.

Yea, the user can definitely specify the plugin version in the build file, but the JIB_VERSION build template argument can be made to override that (so a default empty JIB_VERSION would call com.google.cloud.tools:jib-maven-plugin::build, which would use the project-specified version).


Batarang prevents ng-blur and ng-focus working when on same element

Given this markup:
<input type="text" class="form-control" name="name"
                   ng-blur="onNameBlur()"
                   ng-focus="onNameFocus()" />

Only the first (in this case ng-blur) will fire.  If the order is reversed then only ng-focus would fire.
Disabling the extension corrects the issue.

Possibly related to #205

+1

Same here

:+1:

Spent 6 hours in debugging. This should be fixed ASAP or just workaround should be provided(like big red button to enable/disable?).

This issue is fixed in the latest Batarang. Created repro here:
http://gary-b.github.io/ng-version-test-apps/app/v3/index.html

:+1: Thanks for confirming, @gary-b


Add debug.log file

Hi,
This PR add the file wp-content/debug.log to the WP fuzzing dictionary.
🤔Workflow validation error do not seems related to my update.
Sources:

https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
https://www.acunetix.com/vulnerabilities/web/wordpress-debug-mode/

Thanks in advance 😃

thanks (as always) @righettod !


Spyder 3.0 : File Explorer not refreshing on time

I just recently updated my Spyder from 2 to 3. And I realized that the new file explorer is not as reactive as before.
What steps will reproduce the problem?

Go to any directory that have any sub folders in it
Rename the folder and press ENTER(Or Delete any folder/item )
Now you won't see the the name changed or the removed file is gone
However, if you press parent folder button on the top, now you see the changes have been updated to the file explorer

What is the expected output? What do you see instead?
I remember Spyder 2 did not have such problem. Whenever I do some renaming or deleting files , the file explorer instantly reflects my changes.
Please provide any additional information below
nan
Versions and main components

Spyder Version:3.0
Python Version:3.5
Operating system:Linux

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:

I don't see that problem. Are you using PyQt4 or PyQt5?

I'm currently using PyQt4. Just switched to PyQt5 and now the problem is gone. Thank you so much! Amazing works :)


Problem in evaluating the drivable area result.

Hi. I am trying to evaluating my drivable area result using code in evaluate.py. However, there is 'gt_id_set.remove(255)' in evaluate_segmentation. But I found there is no pixel is 255 in the ground truth map....

I think the value of pixels in the ground truth is in {0,1,2}.

The evaluation is for general segmentation. In the case of full frame segmentation, 255 exists in the label maps.


Fix details in blog post #1

(btw there's another typo: "Quotients by Idemporent Functions in Cedille" instead of "idempotent")

(btw there's another typo: "Quotients by Idemporent Functions in Cedille" instead of "idempotent")

Thanks!! I fixed it here


before_options for voice play_file/encode_file/encode_io

We have a way to provide options at the end of the ffmpeg command via the options variable, but no way to add options before the input.
Ffmpeg allows different options depending on the input file which can not be appended to the end of the command.
My suggestion is to implement a before_options variable which allows users to insert specific options before the -i input file specifier.

i want to work on this , can you assign this to me


Fixes for API breaking changes in imgui 1.74.

See:
https://github.com/ocornut/imgui/blob/master/imgui.cpp#L394
I've never used github before, so this is my first attempt at creating a pull request.

Thanks for the PR!
I think the ImGui::SetNextWindowSize() needs to go before the ImGui::Begin().
(I wasn't actually sure if the order matters, but when I tried it your way in the Fractal sample the window size came out wrong, it looks correct if the call to SetNextWindowSize() is moved above the Begin() call).
Do you want to fix this before merge? Otherwise I can also fix it "post-merge".

Woops, I'll fix it.

Thanks!


Demo uses deprecated non-ISO strings, might break soon (moment.js warning)

When running the demo, the following error pops up in the console
Deprecation warning: moment construction falls back to js Date. This is discouraged and will be removed in upcoming major release. Please refer to https://github.com/moment/moment/issues/1407 for more info.

This is caused by the "LLLL" format which is passed to valueParse.

Well, I don't plan to update Moment in the demo any time soon :smile: the demo needs an overhaul anyway. Thanks for reporting.


Install BlueGL

Includes various other cleanups:

Add READMEs for installed binaries
Don't install includes that are not useful to 3p apps

This closes #147

The install directory now looks like this:
README.md
bin
docs
    filamesh.md
    matinfo.md
    normal-blending.md
    roughness-prefilter.md
    skygen.md
    specular-color.md
include
lib


ReadDirAll

Hi,
why is it not possible to return just all files/folders when a readdir() request comes in?
It seems that many files are missing if I just return everything I know.
regards,
Dom

Hi Dom,
that's the way a filesystem is designed in the FUSE world (which matches how the Linux kernel works afaik). It can become very inefficient to always return a full list of files/folders, (e.g. if there are thousands of files), so the kernel needs a way to query a subset. The FUSE interface implements this by giving an offset to readdir and limiting the number of entries in the reply (you can see this like offset and length of a pagination).
Support for building a directory reply could be improved though, e.g. we could try to make it possible to build directory replies from various kinds of iterators.


Mention similar plugin in the README

Surprised to not see this mentioned in the Comparison or See Also section (and vice versa (cc @xtuc)). It looks similar (but less flexible): babel-plugin-transform-scala-lambda.

Hmm, after playing with them both, it appears that the scope of the other module is much more limited i.e. unlike Scala, it can't handle:
Input
foo.map(_.bar.baz)

Output
babel-plugin-transform-scala-lambda
foo.map((_2 => {
    return _2.bar;
}).baz);

babel-plugin-partial-application :+1:
foo.map(_a => {
    return _a.bar.baz;
});

But then it does support multiple arguments like Scala:
Input
foo.reduce(_ + _)

Output
babel-plugin-partial-application
foo.reduce(_ + _);

babel-plugin-transform-scala-lambda :+1:
foo.reduce((_2, _3) => {
    return _2 + _3;
});

Incidentally, while this doesn't quite work yet (with transpiled template strings):
Input
foo.map(`[ ${_} ]`)

Output
babel-plugin-transform-scala-lambda
foo.map((_2 => {
    return "[ " + _2;
}) + " ]");

babel-plugin-partial-application
foo.map("[ " + _ + " ]");

- it would be great if it could, and if this could be extended to arbitrary expressions e.g.:
Input
foo.map([ _ ])

Output
foo.map(it => [ it ])

Funny! I wasn't aware of transform-scala-lambda! I had been searching for 'partial application' so that one never popped up. My plugin does have many more features but like you mentioned doesn't support binary expressions.
I'm just not sold on the binary expressions though like _ + _. I just don't think it's very useful. I'm open to examples of where it's actually an improvement over the regular JS lambda though but it just doesn't seem like enough. Maybe it's necessary to support template strings though.

@chocolateboy added reference in the readme.
Thanks for all the well put together proposals in here by the way - really appreciate that!

Hi guys, i'm glad you mentioned my plugin :+1:
I also planned to support this:
const mapToName = _.name

console.log(mapToName({name: 'Sven'});

Since we are both missing some features, what do you think publishing a package which inherits from both?
Just FYI i'm part of Babel, I will help you with this.

@chocolateboy turns out I influenced myself on this one. I thought of a few cases where binary expressions can be useful for placeholders and implemented it last night. Made the smart-ish move and waited until this morning to verify tests & push 😆
The cases that changed my mind were:
foo.filter(_ % 2 === 0)
foo.filter(_.level > 0)
foo.filter(_.indexOf('sweet') > -1)
foo.filter(_.getName().length > 10)

... all of which are supported now and will be published in 1.1.0 soon.
@xtuc yo! no problem - we've run into a bit of co-invention! Per the above I'm not sure how that changes things for you on a new package, but I'm always down for collaboration.

Awesome! Looking forward to trying it out :+1:

Ok, you could include my plugin as dependency of yours. This would avoid some code duplications and could be simpler to maintain.
You can use the inherits feature in Babel's plugins or I will update my plugin to simplify integration.
What do you think?

@chocolateboy published as v1.1.0
@xtuc the main problem I see is transform-scala-lambda does not support nested structures like _.foo.bar, _.foo().bar === true, etc.

Yes, does your plugin support it? This was just an idea but if you don't have an advantage we can leave it there.
I can actually work on my plugin to add the support of it.

Mine does, yeah, on member expressions and binaries within members and such.
heroes.filter(_.getPower().level > 9000)

becomes
heroes.filter(_a => {
  return _a.getPower().level > 9000;
})


Add validation for push endpoint connectivity

Check push endpoint is reachable while creating the subscription

LGTM, the code coverage checks need to be taken care of.

Tested on stage. Merging the PR


fix: http2: serialize array parameters correctly

Partially fixes #480 (the "wrong queryParameters serialization" part)
I noticed that a parameter with type string[] in the Google Calendar API was not working as expecting while using google.options({ http2: true });. Specifically I was trying to use:
google.options({ http2: true });
google
  .calendar({
    version: "v3",
    auth: new google.auth.OAuth2(...),
  })
  .events.list({
    calendarId: ...,
    privateExtendedProperty: [`foo=bar`, `baz=asdf`],
  });

I found that the privateExtendedProperty parameter was being ignored by the server.
I traced the issue to this line. Unlike the gaxios request handler (reference), the http2 handler is not calling the paramsSerializer from the parameters. This function is used to define the correct serialization method for array parameters in apirequest.ts (reference).
My fix uses the paramsSerializer passed in from the parameters exactly as is done in gaxios.

@harris-m thank you for the contribution.


Include scm info

This includes the scm tag in the project parent

Closing as I will adjust the formatting.


lock icon in editors review queues shows display name of editor currently viewing the addon (bug 720007)

Earlier, there isn't a way for editors to find out who is viewing an addon in the editors review queue. They had to open the addon review page to find out who opened the addon review page first.
This patch adds a title attribute to the lock icon shown in editor queues, saying "{user's display_name} was viewing this addon first". So other editors can just mouse over the lock icon and see who opened the addon first.
Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=720007

204749c
Thanks!


a small problem with quotations

First i want to congratulate you on the great tool.
I noticed a small error with quotations when trying to run the provided examples. It runs fine if i don't put the input chemical in quotations.  Provided the details below:
E:\programs\PharmacoNet>python scoring.py -p ./examples/6OIM_model.json -s 'c1ccccc1' --num_conformers 8
*** Open Babel Error  in OpenBabel::OBSmilesParser::ParseSimple
SMILES string contains a character ''' which is invalid
Traceback (most recent call last):
File "E:\programs\PharmacoNet\scoring.py", line 43, in
score = scoring(args.smiles, model, args.num_conformers)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "E:\programs\PharmacoNet\scoring.py", line 21, in scoring
pbmol = pybel.readstring('smi', smiles)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "xxx\Programs\conda\envs\pmnet\Lib\openbabel\pybel.py", line 209, in readstring
raise IOError("Failed to convert '%s' to format '%s'" % (
OSError: Failed to convert ''c1ccccc1'' to format 'smi'

Hello @yordan-ov,
Thanks for letting me know. I am currently only running it on LINUX and MAC environments and have not checked its behavior on WINDOW environments, so I am not aware of this issue. I will add documents on different OS environments in the future.


CocoaPod

Any plans to release this as a CocoaPod?

Not at this time but I would entertain a PR to support it.


wrong description in pom.xml for bc*-jdk15on

Description: The Bouncy Castle Java API for handling the OpenPGP protocol. This jar contains the OpenPGP API for JDK 1.5 to JDK 1.8. The APIs can be used in conjunction with a JCE/JCA provider such as the one provided with the Bouncy Castle Cryptography APIs.
Instead of "JDK 1.5 to JDK 1.8" this should say something like "JDK 1.5 and up".
See the description fields in:
https://search.maven.org/artifact/org.bouncycastle/bcpg-jdk15on/1.65/jar
https://search.maven.org/artifact/org.bouncycastle/bcpkix-jdk15on/1.65/jar
https://search.maven.org/artifact/org.bouncycastle/bcprov-jdk15on/1.65/jar

Good point. I've changed the generator to say "JDK 1.5 and up". Thanks.


Something should happen when a user clicks save

On the settings page when a user makes an update to a setting and clicks "Save" they don't get any feedback to let them know that the save happened. We should do something so they know the settings were saved.
(Editing a person is broken right now so I can't see it, but I think it has the same issue.)
Also, the save button looks like it needs some styling.

@hmyers-cms I'm reopening this so you can review from a design standpoint when you get a chance. It seemed important to move ahead with something to confirm saves and report errors, especially since we don't have nice validation right now.

Heather is going to verify this, but her CMS account is locked so she didn't get the notification, she'll approve, moving to QA

Fixed!


Checkpoints reward mode

Hi, I didn't find in the doc how the checkpoints reward mode is implemented. Could you please add more infos on it ? I have really now ideas how the agent is rewarded under this mode.

The checkpoint reward is described in the Google Research Football Paper


[Question] How can I collect expert demonstrations for modified environments

Hello,
I would like to modify one of the maze environments and collect new expert trajectories.
It is my understanding that you use RL algorithms to learn, then sample the trajectories from them.
Do you have a specific implementation for this? Or a set way to collect new demonstrations?
If not, what implementation did you use?
Thank you!

We are moving all of the datasets to a new library under Farama called Minari. It also supports data collection utilities to create new datasets. There is also a tutorial available for data collection of the point maze environment https://minari.farama.org/main/tutorials/dataset_creation/point_maze_dataset/.
Note that you'll have to install Minari from source since we are expecting to make a beta release soon.

Interesting. Thanks!


build-docs fails with React 19

Hi All 👋  Thank you for the neat tool you developed 😎 I just updated my project to React 19, and the build-docs script seems to have a problem with that.
Describe the bug
build-docs fails with React 19.
To Reproduce
Steps to reproduce the behavior:

I'm not using a config file
Doesn't seem to be relevant
node_modules/.bin/redocly build-docs your-openapi-schema.yaml
Error: Objects are not valid as a React child (found: object with keys {$$typeof, type, key, props, _owner, _store}). If you meant to render a collection of children, use an array instead.

Expected behavior
Script should run without errors.
Logs
❯ node_modules/.bin/redocly build-docs schema.yaml
Found undefined and using theme.openapi options
Prerendering docs
Error: Objects are not valid as a React child (found: object with keys {$$typeof, type, key, props, _owner, _store}). If you meant to render a collection of children, use an array instead.

OpenAPI description

Redocly Version(s)

❯ node_modules/.bin/redocly --version
1.26.0

Node.js Version(s)

❯ node --version
v20.13.1

OS, environment

macOS 15.1.1 (24B91)
Additional context

I'm having this problem and I don't have React declared at all. I see now the Redocly is pulling in the latest React and that's why I'm seeing this error.

Thanks for rising this issue!
@AlexVarchuk could you check if that's a Redoc issue?

Hi @tatomyr, I think it is a React 19 issue in Redoc. We'll look into it.