I can't break out styles into composable functions

instead of {style = Animation.style [ Animation.left (px 0.0) ]} I want to break but styles into helper functions. I need to do this in order to dynamically style each element so I set up a function like this:
layoutStyles : ElementId -> Animation a
layoutStyles id =
    Animation.style [ Animation.left (0 * id |> px) ]

initModel id =
    {style = layoutStyles id}

but I get the following error:
Cannot find type `Animation`

25| layoutStyles : Maybe Int -> Animation a
                               ^^^^^^^^^

And when I try Animation.State I get a type mismatch. Because Elm infers that it's looking for Animation.Model.Animation a and I have no way of getting to that type as far as I know.

Hello!
Animation a is an internal type .  Your type signature should be ElementId -> Animation.State or ElementId -> Animation.Messenger.State Msg if you're using the messaging feature.


Excluding Security Hotspots During SonarQube API Vulnerability Import into Defect Dojo

Hello,
I've been able to exclude bugs and code smells when importing SonarQube vulnerabilities with API into Defect Dojo, which is great. However, I'm encountering difficulty in excluding security hotspots. Is there a way to exclude them as well? Thank you for your assistance.

Have you followed the instructions https://defectdojo.github.io/django-DefectDojo/integrations/parsers/api/sonarqube/ ?

Yes, In the documentation. I could not see anything about security hotspot exclusion.

Yes, In the documentation. I could not see anything about security hotspot exclusion.

I have to dive into the code, I was implementing it 2 year ago :)

Any Update on this?

Hi @KarthikY18, Security Hotspots are generally of low severity. When importing issues please choose minimum severity=medium, Security Hotspots will not be included. If you need to include low severity issues, there is currently no solution for that. You will see security hotspots.

Thank you @sametr35, this helps me.


Request: Fluid width embeds

Please consider implementing fluid width embeds so that embeded video nicely fits the document width. Heres a few examples of how this can be achieved, including a vanilla javascript version
PS> thanks for the great plugin. #Loop feature makes me so happy :)

merged to #11


Operator access for jryans

I am actively working on the Stylo project. @Manishearth suggested that I ask for operator access so that I can more easily land changes that have already been reviewed in Bugzilla.
(I am a Mozilla employee with L3 access to Gecko.)
cc @larsbergstrom

This change is

Thanks for the pull request, and welcome! The Servo team is excited to review your changes, and you should hear from @aneeshusa (or someone else) soon.

@bors-servo r+

:pushpin: Commit b24a2ec has been approved by Manishearth

:hourglass: Testing commit b24a2ec93e5ab58a605c95b555785452815334ff with merge a8891903869deba475402d0fd7d5af0d93593917...

:sunny: Test successful - status-travis
Approved by: Manishearth
Pushing a8891903869deba475402d0fd7d5af0d93593917 to master...


Create an example track that uses data streams

It would be useful if the docs included an example of a track with a static data set that uses data streams. My inclination would be to extend the track tutorial, but there could be other ways to structure it.
cc @dliappis and @DJRickyB

Extending the track tutorial makes sense if we use a new section or just use data streams by default. Why? I believe it's important to make sure the tutorial does not become too confusing

use a new section

That's what I had in mind, too. I wouldn't want the example track to use both indices and data streams, as I agree that it would become too confusing, especially for new users who are the intended audience.


Register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/59143
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.0.1 -m "<description of version>" 07d844cb6e25cc606fa6fa0f6b5dcb410d740bca
git push origin v0.0.1


Pico-8 bonsai or garden procedural generation

Generate trees artificially, add some parameters to control their difference etc.

closing in favor of #244


Fix postgresql certificate path

https://github.com/concourse/concourse-bosh-release/blob/1b8953a55b20c5d377fc8ae8b4f2170c6ef49e0c/jobs/web/spec#L778-L782
The opsfile was missing the certificate part of the path.
cc @sophiewigmore @yaelharel

It's actually correct as-is - it expects postgres_ca_cert to be provided as a var which itself contains a certificate field. In our case we have it stored in CredHub.
A similar discussion/confusion played out in https://github.com/concourse/concourse-bosh-deployment/pull/139 - maybe there's some way we can make this more obvious. :thinking:

@vito Yup, you're totally right. We changed our postgres_ca_cert var to have a certificate field and the ops-file works.
Thanks!


Adjustable Memory Allocation Functions

Hi, mini MP4 was works as expected for me, and I adopt this instead old and harder to intergerate libmp4v2 to generate h264 encoded stream in MP4 container. But could I have adjustable malloc functions to custom functions? My reasons is beacuse I'm prefer to use another memory allocator (e.g mimalloc) than the CRT default one, but I think it will somewhat useful for task including custom memory tracing functions, etc. I mean, like the miniaudio has adjustable macros for MA_MALLOC, MA_REALLOC and MA_FREE. Thanks!

Hi) That's a good idea. Will do it at some point.


Delete form

Add the controller for deleting a project. Also complete form routes

claim

Assigned to @Vishesh-Vijay


config.json is not ignored nor tracked

The new version saves the configuration to config.json, which is not .gitignore'd nor tracked.
It's not causing any problem but better to be ignored i think as .env* were.

@kukyakya, yes git is not tracking config.json and this is by purpose.
Firstly, it ensures that your own config.json is not overwritten when you update the application code next time you update your application (hence your configuration settings will be kept)
Secondly, it ensures your own config.json is not uploaded to github if you use a fork of the application.
Unless you add the config.json manually to git (which you shouldn't do), it doesn't necessarily need to be added to .gitignore (but it doesn't hurt if it is - so I can add it when I upgrade the app version).

config.json added to .gitignore starting with version 1.1.0


Update to Videolab 1.3.2!

https://github.com/teenageengineering/videolab/releases
I'll get to this eventually.

Completed with #3


Weights link is no longer working

Hi, it seems the link to download the weights is down.
Is there a way to upload to a new link or make it working again?
linking from this issue here for code for our paper as it relies on the S3D pre-trained weights :') https://github.com/sumedh7/RoboCLIP/issues/4

Same issue here

I found it and uploaded it myself, see here:
https://drive.google.com/file/d/1p_CMGppAQk3B0_Z0i1r2AN_D1FM3kUFW/view?usp=sharing
https://drive.google.com/file/d/1DN8t1feS0t5hYYTfXQfZd596Pu9yXJIr/view?usp=sharing


Kong 0.10.1 migrations failed

Summary
I experienced an issue when starting up Kong 0.10.1 for the very first time. Executing migrations got broken and I could only fix it by executing kong migrations reset and kong migrations up multiple times.
Steps To Reproduce

Start up 3 instances of Cassandra 2.2.9
Start up Kong 0.10.1 ==> Sometimes it fails with the errors listed below.
kong migrations reset && kong migrations up ==> Sometimes it fails with below errors.

Additional Details & Logs

Kong version 0.10.1
Cassandra 2.2.9 (three instances)

Kong debug-level startup logs ($ kong start --vv)
migrating core for keyspace kong
Error: /usr/local/share/lua/5.1/kong/cmd/start.lua:21: [cassandra error] Error during migration 2015-01-12-175310_init_schema: [Invalid] No column definition found for column request_host

^ Over and over.
Kong Migrations (manually)
[root@d8744e46dea5 /]# kong migrations reset --conf /usr/local/kong/.kong_env
> Are you sure? This operation is irreversible. [Y/n] Y
Schema successfully reset
[root@d8744e46dea5 /]# kong migrations up --conf /usr/local/kong/.kong_env
migrating core for keyspace kong
core migrated up to: 2015-01-12-175310_skeleton
core migrated up to: 2015-01-12-175310_init_schema
core migrated up to: 2015-11-23-817313_nodes
core migrated up to: 2016-02-25-160900_remove_null_consumer_id
core migrated up to: 2016-02-29-121813_remove_ttls
core migrated up to: 2016-09-05-212515_retries_step_1
core migrated up to: 2016-09-05-212515_retries_step_2
core migrated up to: 2016-09-16-141423_upstreams
core migrated up to: 2016-12-14-172100_move_ssl_certs_to_core
core migrated up to: 2016-11-11-151900_new_apis_router_1
core migrated up to: 2016-11-11-151900_new_apis_router_2
core migrated up to: 2016-11-11-151900_new_apis_router_3
core migrated up to: 2017-01-24-132600_upstream_timeouts
core migrated up to: 2017-01-24-132600_upstream_timeouts_2
migrating request-transformer for keyspace kong
request-transformer migrated up to: 2016-03-10-160000_req_trans_schema_changes
migrating rate-limiting for keyspace kong
rate-limiting migrated up to: 2015-08-03-132400_init_ratelimiting
rate-limiting migrated up to: 2016-07-25-471385_ratelimiting_policies
migrating hmac-auth for keyspace kong
hmac-auth migrated up to: 2015-09-16-132400_init_hmacauth
migrating jwt for keyspace kong
jwt migrated up to: 2015-06-09-jwt-auth
jwt migrated up to: 2016-03-07-jwt-alg
migrating response-ratelimiting for keyspace kong
response-ratelimiting migrated up to: 2015-08-21_init_response-rate-limiting
response-ratelimiting migrated up to: 2016-08-04-321512_response-rate-limiting_policies
migrating ip-restriction for keyspace kong
ip-restriction migrated up to: 2016-05-24-remove-cache
migrating cors for keyspace kong
cors migrated up to: 2017-03-14_multiple_orgins
migrating galileo for keyspace kong
galileo migrated up to: 2016-04-15_galileo-import-mashape-analytics
migrating acl for keyspace kong
acl migrated up to: 2015-08-25-841841_init_acl
migrating basic-auth for keyspace kong
basic-auth migrated up to: 2015-08-03-132400_init_basicauth
migrating oauth2 for keyspace kong
oauth2 migrated up to: 2015-08-03-132400_init_oauth2
oauth2 migrated up to: 2015-08-24-215800_cascade_delete_index
oauth2 migrated up to: 2016-02-29-435612_remove_ttl
Error: [cassandra error] Error during migration 2016-04-14-283949_serialize_redirect_uri: could not prepare query: [Invalid] unconfigured table oauth2_credentials

  Run with --v (verbose) or --vv (debug) for more details

Kong error logs (<KONG_PREFIX>/logs/error.log)
2017/04/13 18:58:19 [warn] 12448#0: *145 [lua] cluster.lua:745: execute(): [lua-cassandra] Aggregation query us
ed without partition key, context: ngx.timer
2017/04/13 18:58:22 [notice] 12424#0: *340 [lua] cluster.lua:688: execute(): [lua-cassandra] SELECT COUNT(*) FR
OM nodes was not prepared on host <IP_ADDRESS>, preparing and retrying, context: ngx.timer
2017/04/13 18:58:22 [error] 12424#0: *340 [lua] cluster.lua:20: log(): [cluster] [cassandra error] could not pr
epare query: [Invalid] unconfigured table nodes, context: ngx.timer
2017/04/13 18:58:46 [error] 12437#0: *1518 [lua] cluster.lua:20: log(): [cluster] could not retrieve nodes from
 datastore: [cassandra error] could not prepare query: [Invalid] unconfigured table nodes, context: ngx.timer
2017/04/13 18:59:16 [error] 12455#0: *3013 [lua] cluster.lua:20: log(): [cluster] could not retrieve nodes from
 datastore: [cassandra error] could not prepare query: [Invalid] unconfigured table nodes, context: ngx.timer
2017/04/13 18:59:46 [error] 12441#0: *4509 [lua] cluster.lua:20: log(): [cluster] could not retrieve nodes from
 datastore: [cassandra error] could not prepare query: [Invalid] unconfigured table nodes, context: ngx.timer
2017/04/13 19:00:16 [error] 12455#0: *6005 [lua] cluster.lua:20: log(): [cluster] could not retrieve nodes from
 datastore: [cassandra error] could not prepare query: [Invalid] unconfigured table nodes, context: ngx.timer
2017/04/13 19:01:16 [notice] 12455#0: *8998 [lua] cluster.lua:688: execute(): [lua-cassandra] SELECT * FROM nod
es WHERE name = ? ALLOW FILTERING was not prepared on host <IP_ADDRESS>, preparing and retrying, context: ngx.t
imer
2017/04/13 19:02:16 [notice] 12455#0: *11989 [lua] cluster.lua:688: execute(): [lua-cassandra] SELECT * FROM no
des WHERE name = ? ALLOW FILTERING was not prepared on host <IP_ADDRESS>, preparing and retrying, context: ngx.
timer

Kong configuration (registered APIs/Plugins & configuration file)
Default values except for:

anonymous_reports = off
nginx_daemon = off
ssl = off
admin_ssl = off
cluster_profile = lan

- Operating System
CentOS 7 in a Docker container.

By the way. After fixing this issue running kong migrations reset && kong migrations up multiple times, I started 2 extra instances of Kong, and then saw the same problem again:
Error: /usr/local/share/lua/5.1/kong/cmd/start.lua:21: [cassandra error] Error during migration 2015-01-12-175310_init_schema: [Invalid] No column definition found for column request_host

When trying to run migrations manually:
[root@1aa3c8a1deb2 /]# kong migrations up --conf /usr/local/kong/.kong_env
migrating core for keyspace kong
Error: [cassandra error] Error during migration 2015-01-12-175310_init_schema: [Invalid] No column definition found for column request_host

  Run with --v (verbose) or --vv (debug) for more details

Could it be a race condition?

Here's something I found in errors.log in another Kong's node:
2017/04/13 20:07:36 [error] 32869#0: init_by_lua error: /usr/local/share/lua/5.1/kong.lua:134: [cassandra error
] Error during migration 2016-09-05-212515_retries_step_1: [Invalid] Invalid column name retries because it con
flicts with an existing column

It really looks like a race condition.

Should be fixed in the upcoming 0.10.2. As always, make sure you are always running your migrations from a single Kong node. No 2 Kong nodes can be started at the same time on a fresh Cassandra cluster.

Thanks @thibaultcha. Any idea when I'll be able to run migrations with multiple Kong nodes?

Probably never, due to the distributed nature of Cassandra.

I am running into this same error with Kong 0.10.2. I'll debug and report back.

@mprimeaux thanks, please report back when you get an insight. I reproduced it consistently with multiple nodes and that is considered as a known issue. I did see a problem like yours but at that point I couldn't guarantee that it was a problem with Kong itself or if it was our data centers. After that, I couldn't reproduce it anymore.
Please, let us know if you see something interesting.

Here's what I can confirm at this point in time.
This error...
Error: [cassandra error] Error during migration 2016-11-11-151900_new_apis_router_3: [Invalid] Index 'apis_request_host_idx' could not be found in any of the tables of keyspace 'api_gateway'.

...only occurs the very first time a Kong cluster is initialised. All attempts to reproduce the same error after the initial failure using the same Kong cluster are unsuccessful. Even stopping Kong, dropping the target Cassandra keyspace, rebooting the node and attempting to run `kong start' completes execution of all migrations successfully.
Running kong migrations reset immediately after the initial failure does allow kong start to start as expected.
Oddly enough, the only reference to "apis_request_host_idx" I can find is contained within postgres.lua, which is clearly not the configured durable storage provider.

@mprimeaux thanks for reporting back. Were you able to consistently (or, at least, multiple times) reproduce this issue? In other words, did you completely remove the Kong cluster (which, based on your previous message, is a 1-node cluster), install it again, and see this issue?

I am able to reproduce this issue consistently. I'm using Ubuntu Server 16.04 LTS. One warning I did notice when starting Kong is a message to increase ulimit to at least 4096. I'd like to investigate that next to rule it out.

Excellent, thanks for your responses. Let's wait to see what @thibaultcha and the other folks say about it.

Unfortunately, ensuring ulimit was at 4096 didn't correct the issue.
ubuntu@ip-172-31-0-104:~$ ulimit -n 4096
ubuntu@ip-172-31-0-104:~$ ulimit
unlimited
ubuntu@ip-172-31-0-104:~$ ulimit -n
4096
ubuntu@ip-172-31-0-104:~$ kong start
migrating core for keyspace pulse_1_api_gateway
core migrated up to: 2015-01-12-175310_skeleton
core migrated up to: 2015-01-12-175310_init_schema
core migrated up to: 2015-11-23-817313_nodes
core migrated up to: 2016-02-25-160900_remove_null_consumer_id
core migrated up to: 2016-02-29-121813_remove_ttls
core migrated up to: 2016-09-05-212515_retries_step_1
core migrated up to: 2016-09-05-212515_retries_step_2
core migrated up to: 2016-09-16-141423_upstreams
core migrated up to: 2016-12-14-172100_move_ssl_certs_to_core
core migrated up to: 2016-11-11-151900_new_apis_router_1
core migrated up to: 2016-11-11-151900_new_apis_router_2
Error: /usr/local/share/lua/5.1/kong/cmd/start.lua:21: [cassandra error] Error during migration 2016-11-11-151900_new_apis_router_3: [Invalid] Index 'apis_request_host_idx' could not be found in any of the tables of keyspace 'pulse_1_api_gateway'

  Run with --v (verbose) or --vv (debug) for more details
ubuntu@ip-172-31-0-104:~$

As you can see, the ulimit warning doesn't appear but I still experience the error.  I'll wait to hear from @thibaultcha and will continue to debug in the interim.  Please let me know if you'd like me to try anything on my end.

When I saw this issue, I was running Kong 0.9.7 and Kong 0.10.1. If you have some time and want to try with 0.10.1, it'd be great because the Kong's folks introduced some changes regarding running migrations on Cassandra.

I can confirm that I experienced this exact same error with Kong 0.10.1, which is what brought me to this thread.

...more information with kong start --vv.
ubuntu@ip-172-31-0-90:~$ kong start --vv
2017/05/03 21:26:35 [verbose] Kong: 0.10.2
2017/05/03 21:26:35 [debug] ngx_lua: 10007
2017/05/03 21:26:35 [debug] nginx: 1011002
2017/05/03 21:26:35 [debug] Lua: LuaJIT 2.1.0-beta2
2017/05/03 21:26:35 [verbose] reading config file at /etc/kong/kong.conf
2017/05/03 21:26:35 [debug] admin_listen = "<IP_ADDRESS>:8001"
2017/05/03 21:26:35 [debug] admin_listen_ssl = "<IP_ADDRESS>:8444"
2017/05/03 21:26:35 [debug] admin_ssl = true
2017/05/03 21:26:35 [debug] anonymous_reports = true
2017/05/03 21:26:35 [debug] cassandra_consistency = "ONE"
2017/05/03 21:26:35 [debug] cassandra_contact_points = {"<IP_ADDRESS>"}
2017/05/03 21:26:35 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
2017/05/03 21:26:35 [debug] cassandra_keyspace = "pulse_1_api_gateway"
2017/05/03 21:26:35 [debug] cassandra_lb_policy = "RoundRobin"
2017/05/03 21:26:35 [debug] cassandra_password = "******"
2017/05/03 21:26:35 [debug] cassandra_port = 9042
2017/05/03 21:26:35 [debug] cassandra_repl_factor = 1
2017/05/03 21:26:35 [debug] cassandra_repl_strategy = "SimpleStrategy"
2017/05/03 21:26:35 [debug] cassandra_schema_consensus_timeout = 10000
2017/05/03 21:26:35 [debug] cassandra_ssl = false
2017/05/03 21:26:35 [debug] cassandra_ssl_verify = false
2017/05/03 21:26:35 [debug] cassandra_timeout = 5000
2017/05/03 21:26:35 [debug] cassandra_username = "pulse_api_gateway"
2017/05/03 21:26:35 [debug] cluster_listen = "<IP_ADDRESS>:7946"
2017/05/03 21:26:35 [debug] cluster_listen_rpc = "<IP_ADDRESS>:7373"
2017/05/03 21:26:35 [debug] cluster_profile = "wan"
2017/05/03 21:26:35 [debug] cluster_ttl_on_failure = 3600
2017/05/03 21:26:35 [debug] custom_plugins = {}
2017/05/03 21:26:35 [debug] database = "cassandra"
2017/05/03 21:26:35 [debug] dns_hostsfile = "/etc/hosts"
2017/05/03 21:26:35 [debug] dns_resolver = {}
2017/05/03 21:26:35 [debug] latency_tokens = true
2017/05/03 21:26:35 [debug] log_level = "notice"
2017/05/03 21:26:35 [debug] lua_code_cache = "on"
2017/05/03 21:26:35 [debug] lua_package_cpath = ""
2017/05/03 21:26:35 [debug] lua_package_path = "?/init.lua;./kong/?.lua"
2017/05/03 21:26:35 [debug] lua_socket_pool_size = 30
2017/05/03 21:26:35 [debug] lua_ssl_verify_depth = 1
2017/05/03 21:26:35 [debug] mem_cache_size = "128m"
2017/05/03 21:26:35 [debug] nginx_daemon = "on"
2017/05/03 21:26:35 [debug] nginx_optimizations = true
2017/05/03 21:26:35 [debug] nginx_worker_processes = "auto"
2017/05/03 21:26:35 [debug] pg_database = "kong"
2017/05/03 21:26:35 [debug] pg_host = "<IP_ADDRESS>"
2017/05/03 21:26:35 [debug] pg_port = 5432
2017/05/03 21:26:35 [debug] pg_ssl = false
2017/05/03 21:26:35 [debug] pg_ssl_verify = false
2017/05/03 21:26:35 [debug] pg_user = "kong"
2017/05/03 21:26:35 [debug] prefix = "/usr/local/kong/"
2017/05/03 21:26:35 [debug] proxy_listen = "<IP_ADDRESS>:8000"
2017/05/03 21:26:35 [debug] proxy_listen_ssl = "<IP_ADDRESS>:8443"
2017/05/03 21:26:35 [debug] serf_path = "serf"
2017/05/03 21:26:35 [debug] server_tokens = true
2017/05/03 21:26:35 [debug] ssl = true
2017/05/03 21:26:35 [debug] upstream_keepalive = 60
2017/05/03 21:26:35 [verbose] prefix in use: /usr/local/kong
2017/05/03 21:26:35 [verbose] preparing nginx prefix directory at /usr/local/kong
2017/05/03 21:26:35 [verbose] saving serf identifier to /usr/local/kong/serf/serf.id
2017/05/03 21:26:35 [debug] searching for OpenResty 'resty' executable
2017/05/03 21:26:35 [debug] /usr/local/openresty/bin/resty -V: 'nginx version: openresty/<IP_ADDRESS>'
2017/05/03 21:26:35 [debug] found OpenResty 'resty' executable at /usr/local/openresty/bin/resty
2017/05/03 21:26:35 [verbose] saving serf shell script handler to /usr/local/kong/serf/serf_event.sh
2017/05/03 21:26:35 [verbose] SSL enabled, no custom certificate set: using default certificate
2017/05/03 21:26:35 [verbose] generating default SSL certificate and key
2017/05/03 21:26:36 [verbose] Admin SSL enabled, no custom certificate set: using default certificate
2017/05/03 21:26:36 [verbose] generating admin SSL certificate and key
2017/05/03 21:26:36 [verbose] running datastore migrations
2017/05/03 21:26:36 [info] migrating core for keyspace pulse_1_api_gateway
2017/05/03 21:26:36 [info] core migrated up to: 2015-01-12-175310_skeleton
2017/05/03 21:26:39 [info] core migrated up to: 2015-01-12-175310_init_schema
2017/05/03 21:26:39 [info] core migrated up to: 2015-11-23-817313_nodes
2017/05/03 21:26:39 [info] core migrated up to: 2016-02-25-160900_remove_null_consumer_id
2017/05/03 21:26:39 [info] core migrated up to: 2016-02-29-121813_remove_ttls
2017/05/03 21:26:39 [info] core migrated up to: 2016-09-05-212515_retries_step_1
2017/05/03 21:26:39 [info] core migrated up to: 2016-09-05-212515_retries_step_2
2017/05/03 21:26:40 [info] core migrated up to: 2016-09-16-141423_upstreams
2017/05/03 21:26:41 [info] core migrated up to: 2016-12-14-172100_move_ssl_certs_to_core
2017/05/03 21:26:42 [info] core migrated up to: 2016-11-11-151900_new_apis_router_1
2017/05/03 21:26:42 [info] core migrated up to: 2016-11-11-151900_new_apis_router_2
2017/05/03 21:26:42 [verbose] could not start Kong, stopping services
2017/05/03 21:26:42 [verbose] leaving serf cluster
2017/05/03 21:26:42 [verbose] left serf cluster
2017/05/03 21:26:42 [verbose] stopping serf agent at /usr/local/kong/pids/serf.pid
2017/05/03 21:26:42 [debug] sending signal to pid at: /usr/local/kong/pids/serf.pid
2017/05/03 21:26:42 [debug] no pid file at: /usr/local/kong/pids/serf.pid
2017/05/03 21:26:42 [verbose] serf agent stopped
2017/05/03 21:26:42 [verbose] stopped services
Error:
/usr/local/share/lua/5.1/kong/cmd/start.lua:34: /usr/local/share/lua/5.1/kong/cmd/start.lua:21: [cassandra error] Error during migration 2016-11-11-151900_new_apis_router_3: [Invalid] Index 'apis_request_host_idx' could not be found in any of the tables of keyspace 'pulse_1_api_gateway'
stack traceback:
	[C]: in function 'error'
	/usr/local/share/lua/5.1/kong/cmd/start.lua:34: in function 'cmd_exec'
	/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:88>
	[C]: in function 'xpcall'
	/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:45>
	/usr/local/bin/kong:5: in function 'file_gen'
	init_worker_by_lua:38: in function <init_worker_by_lua:36>
	[C]: in function 'pcall'
	init_worker_by_lua:45: in function <init_worker_by_lua:43>
ubuntu@ip-172-31-0-90:~$

I'll continue to investigate and report back.

Unfortunately, I've got nothing new to report. I'll continue my investigation at some point this week. Any help or insight is greatly appreciated.


fstab syntax not workign

Hey, when trying to moutn via fstab I'm getting an error:
root@vodnl:~# mount /mnt/cephfs
error: The following required arguments were not provided:
    <mountpoint>

USAGE:
    catfs <from> <to> <mountpoint> -o <option>...

FStab line :
catfs#/mnt/cephfs_real#/mnt/storage/cephfs_cache        /mnt/cephfs         fuse    allow_other,--uid=1001,--gid=1001,--free=1%,_netev,noatime   0       0

what catfs version are you using?

I installed the pre-built binary 0.8.0 and I'm also seeing this error:
$ sudo mount /mnt/album-cache
error: The following required arguments were not provided:
    <mountpoint>

USAGE:
    catfs <from> <to> <mountpoint> -o <option>...

For more information try --help
$

This is the line in my fstab:
catfs#/mnt/album#/var/lib/album-cache	/mnt/album-cache	fuse	noauto,noatime	0	0

it's in HEAD but not in a released version yet


fix: ftp incorrectly called AB#8045

@gulfaraz You should be able to run the pipeline for Zambia non-mock again. (Keep in mind that early in the morning though today's data might not be there yet. To test in that case I usually set CURRENT_DATE in settings.py to yesterday)


[QnAMaker] QnAMaker Action schema

QnAMaker Action schema
Single turn dialog

@trojenguri - are you missing the .schema file?
@tomlm; @carlosscastro can you please review and help point @trojenguri to what's needed to get the component schema in?


Question: scanning and connecting

Hi all,
Question about scanning types and connecting.
Currently by default, I start a 'new' scan (i.e. pass 0 into continuation) every time.
I start a new scan after connect() and every time a scan ends (20s scans by default).
I then store MACs of things I hear adverts from, and discard those I don't want.
So, the question:
If I try to connect to a device, is there any advantage to it being in the current scan results?  i.e. is me restarting the scan from scratch every time making it harder for the subsystem to connect to devices (longer connection times, etc...)?
If I did do a continuation every time, I imaging the memory building over time - especially with lots of random addresses from phones, etc.
Should I modify the code to do continuation scans, but to explicitly delete the macs that I am ignoring?  Or maybe periodically go through all the scan results and remove ones I'm not interested in?
So basically, is there an advantage to using continuation, and if so how to control memory usage?
best,
Simon

If I try to connect to a device, is there any advantage to it being in the current scan results? i.e. is me restarting the scan from scratch every time making it harder for the subsystem to connect to devices (longer connection times, etc...)?

No advantage to keeping it, the erase method is there for this. There is no effect on connections when scanning.

If I did do a continuation every time, I imaging the memory building over time - especially with lots of random addresses from phones, etc.

You can limit this with pScan->setMaxResults(xx). Also you can add macs to the ignore list so you won't see them.

thankyou;  I just wondered if it kept anything useful like rf frequencies for connection, etc.  But if not, then I'm not doing anything wrong :).

You're welcome, hope the project is going well over there.

we still have restarts - uptimes between 1 hour and 2 days.  Has anyone produced a simple reproduction of the stall issue?
I also still see 'lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)' in serial logs regularly.  I feel this is related to the device I'm connecting to - like BLE receiving two of something during connection rather than one, or it sending a notify packet at connect.


Pairwise image labeling only allows right selection

Problem
When trying pairwise image comparison on the playground, only the right image can be selected.
Minimal example of the labeling config
<View>
  <Pairwise name="pw" toName="txt-1,txt-2" />
  <Image name="txt-1" value="$text1" />
  <Image name="txt-2" value="$text2" />
</View>

Or in the playground using this link
Anyone any idea what could be the cause of this and how it could be solved? Thanks!

@rvandevijver The playground uses a very ancient version of LS. In the LS 1.4 I couldn't reproduce this bug.

Feel free to re-open if you can reproduce it in LS 1.4.


Reproduce results on the test split

Thanks for your great work.
However, I have some confusion in “Reproduce results on the test split”. If I understand correctly, the inputs to the model are 2D bounding boxes which located in “../resources/test_boxes” and the outputs should be 3D bounding boxes which placed in “../output/submission/data”. However, the results I got were not 3D bounding boxes, as follows:

The results do not contain 3D information. Is it because I made a mistake somewhere?

Thanks for your great work.
However, I have some confusion in “Reproduce results on the test split”. If I understand correctly, the inputs to the model are 2D bounding boxes which located in “../resources/test_boxes” and the outputs should be 3D bounding boxes which placed in “../output/submission/data”. However, the results I got were not 3D bounding boxes, as follows:

The results do not contain 3D information. Is it because I made a mistake somewhere?

Hi, the current inference script only updates the vehicle orientation from the input boxes. If the input boxes does not have 3D location and dimension attributes, the output will be like this. This result is ready for submission for evaluating AOS. If you want to submit other attributes as well, you can use any detector that predicts 3D attributes. You can also solve for 3D location following Deep3DBox given the orientation predicted by EgoNet.

感谢您的杰出工作。
但是，我对“在测试拆分上重现结果”有些困惑。如果我理解正确，模型的输入是位于“../resources/test_boxes”中的 2D 边界框，输出应该是位于“../output/submission/data”中的 3D 边界框。但是，我得到的结果不是 3D 边界框，如下所示：
结果不包含 3D 信息。是因为我在某个地方犯了错误吗？

您好，当前的推理脚本仅从输入框中更新车辆方向。如果输入框没有3D位置和维度属性，输出会是这样。此结果已准备好提交以评估 AOS。如果您还想提交其他属性，您可以使用任何预测 3D 属性的检测器。根据 EgoNet 预测的方向，您还可以在 Deep3DBox 之后求解 3D 位置。

OK, Thanks for your reply!


Allow disabling rate limiting and setting redis key

Do you think max bursts is something that should be configurable? otherwise, LGTM.


Application Gateway url-path-map rule create expands /* to files and directories

Describe the bug
On Linux only url-path-map rule create --paths will expand /* if passed from a PowerShell variable to az.
To Reproduce
$paths = @('/*')
az network application-gateway url-path-map rule create -g $resourceGroupName --gateway-name $gatewayName --path-map-name $name -n $ruleName --address-pool $pool --http-settings $settings --paths $paths

Expected behavior
The rule should be created mapping the path /* to the target/settings. Instead on Linux I end up with a rule mapping paths /bin,/boot,/dev,/etc,/home,/lib,/lib32,/lib64,/libx32,/media,/mnt,/opt,/proc,/root,/run,/sbin,/snap,/srv,/sys,/tmp,/usr,/var,/init.
Environment summary
{
  "azure-cli": "2.25.0",
  "azure-cli-core": "2.25.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {
    "front-door": "1.0.14"
  }
}

$ uname -a
Linux DESKTOP-KBOT7AU 4.4.0-19041-Microsoft #488-Microsoft Mon Sep 01 13:43:00 PST 2020 x86_64 x86_64 x86_64 GNU/Linux

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.1.3
PSEdition                      Core
GitCommitId                    7.1.3
OS                             Linux 4.4.0-19041-Microsoft #488-Microsoft Mon Sep 01 13:43:00 PST 2020
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Additional context
The same code on Windows does not expand the /*.

network

FWIW I am also seeing this problem with az network front-door routing-rule create, specifically on the --patterns argument. If I pass /* I end up with /bin, /boot, /dev etc.

Please use  $paths = @('"/*"')

@kairu-ms this devivates from the behaviour on Windows - plus it is not documented.
Just to be clear: I am invoking az from a Powershell session not from bash so this is clearly a bug in either the az code or documentation.
My hunch is that PS passes the variable correctly to az but the * is expanded in either a bash sub-process or in Python.

@kairu-ms this devivates from the behaviour on Windows - plus it is not documented.
Just to be clear: I am invoking az from a Powershell session not from bash so this is clearly a bug in either the az code or documentation.
My hunch is that PS passes the variable correctly to az but the * is expanded in either a bash sub-process or in Python.

This is not cli bug. /* will automatically be expanded as arguments before az parse them. I’ve tried that both in bash and powershell.

@kairu-ms Powershell does not expand *!
craig@debian:~$ pwsh
PowerShell 7.1.3
Copyright (c) Microsoft Corporation.

https://aka.ms/powershell
Type 'help' to get help.

PS /home/craig> Write-Host *
*

Ergo az is expanding the *, or am I missing something here?

@kairu-ms ok, so I see the problem:
$ file $(whereis az)
az::                         cannot open `az:' (No such file or directory)
/usr/bin/az:                 Bourne-Again shell script, ASCII text executable

Calling a bash script (see above) from PS causes bash to expand the args before the script gets invoked. IMHO this breaks the contract since in PS land I should not have to care about how az is implemented.
For example if I'm running a Azure DevOps pipeline on a Windows agent and switch to a Linux agent I'll see totally unexpected behaviour even tho I'm using the same Powershell and az on both. I could even mistakenly add security vulns by adding paths I don't want to expose, ouch.
TBH I'd rather just invoke python directly rather than going via this:
#!/usr/bin/env bash
bin_dir=`cd "$(dirname "$BASH_SOURCE[0]")"; pwd`
AZ_INSTALLER=DEB "$bin_dir"/../../opt/az/bin/python3 -Im azure.cli "$@"

Hi @jiasli, could you help to check this issue?

This issue is not relevant to the fact that az is actually a Bash script at /usr/bin/az. It is a behavior of Bash and PowerShell on Linux.
You will see the /* expansion behavior in Bash even without az and the /usr/bin/az Bash script:
$ python3 -c "import sys; print(sys.argv)" /*
['-c', '/bin', '/boot', '/dev', '/etc', '/home', '/init', '/lib', '/lib32', '/lib64', '/libx32', '/lost+found', '/media', '/mnt', '/opt', '/proc', '/root', '/run', '/sbin', '/snap', '/srv', '/sys', '/tmp', '/usr', '/var']

$ python3 -c "import sys; print(sys.argv)" "/*"
['-c', '/*']

When running the same command from PowerShell on Linux:
> python3 -c "import sys; print(sys.argv)" /*
['-c', '/bin', '/boot', '/dev', '/etc', '/home', '/lib', '/lib32', '/lib64', '/libx32', '/lost+found', '/media', '/mnt', '/opt', '/proc', '/root', '/run', '/sbin', '/snap', '/srv', '/sys', '/tmp', '/usr', '/var', '/init']

> python3 -c "import sys; print(sys.argv)" "/*"
['-c', '/*']

> $paths = @('/*')

> python3 -c "import sys; print(sys.argv)" $paths
['-c', '/bin', '/boot', '/dev', '/etc', '/home', '/lib', '/lib32', '/lib64', '/libx32', '/lost+found', '/media', '/mnt', '/opt', '/proc', '/root', '/run', '/sbin', '/snap', '/srv', '/sys', '/tmp', '/usr', '/var', '/init']

> python3 -c "import sys; print(sys.argv)" "$paths"
['-c', '/*']

As shown above, if you want a consistent behavior between PowerShell on Windows and PowerShell on Linux, use double quotes around $paths as "$paths".

In PowerShell on Linux:
> Write-Host *
*
> Write-Host /*
/*

These commands doesn't expand * and /* because Write-Host is PowerShell cmdlet and * and /* don't go out of PowerShell to the underlying Linux system, so the expansion doesn't take place.
Meanwhile, az is a Bash script and python3 is an executable, so * and /* goes out of PowerShell to the underlying Linux system, where the expansion occurs.


Mixed case-json keys not recognized in Redshift SUPER

Describe the bug
I am trying to parse a Redshift SUPER column that contains a json-struct where the keys are in mixed cases. I am supplying sql_header="SET downcase_delimited_identifier TO FALSE;" in the model's config but the value is not being picked up in the model.  It seems that the sql-header is not having any effect.
Steps To Reproduce
I am able to reproduce the bug following the Redshift documentation on querying Super.
I create a model downcase_bug.sql like this:
{{ config(
    materialized='table',
    sql_header="SET downcase_delimited_identifier TO FALSE;"
) }}

SELECT json_table.data."ITEMS"."Name",
       json_table.data."price"
FROM
  (SELECT json_parse('{"ITEMS":{"Name":"TV"}, "price": 345}') AS data) AS json_table

The table being created looks like this:

name
price

NULL
345

If I run this query in my sql client:
SET downcase_delimited_identifier TO FALSE;
SELECT json_table.data."ITEMS"."Name",
       json_table.data."price"
FROM
  (SELECT json_parse('{"ITEMS":{"Name":"TV"}, "price": 345}') AS data) AS json_table

The output is:

Name
price

"TV"
345

Expected behavior
I expect the model being created to look like this:

Name
price

"TV"
345

Screenshots and log output
Creation statement from running with --debug:
2021-04-23 08:32:49.359486 (Thread-1): On model.my_datamart.downcase_bug: /* {"app": "dbt", "dbt_version": "0.19.1", "profile_name": "dwh_developer", "target_name": "developer", "node_id": "model.my_datamart.downcase_bug"} */
SET downcase_delimited_identifier TO FALSE;

  create  table
    "dev"."dbt_karlanka_prototyping"."downcase_bug__dbt_tmp"

  as (

SELECT json_table.data."ITEMS"."Name",
       json_table.data."price"
FROM
  (SELECT json_parse('{"ITEMS":{"Name":"TV"}, "price": 345}') AS data) AS json_table
  );

System information
Which database are you using dbt with?

[ ] postgres
[x] redshift
[ ] bigquery
[ ] snowflake
[ ] other (specify: ____________)

Detailed version: PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.25599
The output of dbt --version:
installed version: 0.19.1
   latest version: 0.19.1

Up to date!

Plugins:
  - bigquery: 0.19.1
  - postgres: 0.19.1
  - redshift: 0.19.1
  - snowflake: 0.19.1

The operating system you're using:
OS Name	Microsoft Windows 10 Enterprise
Version	10.0.18363 Build 18363

The output of python --version:
Python 3.7.5

@karlanka It seems the session parameter must be set in separate query that runs prior to the SUPER-using query. It cannot be run together (semicolon-delineated) in the same query. I was able to confirm this with a local SQL-running tool.
For that reason, sql_header will not work for this purpose, but pre_hook will:
{{ config(
    materialized='table',
    pre_hook="SET downcase_delimited_identifier TO FALSE"
) }}

SELECT json_table.data."ITEMS"."Name",
       json_table.data."price"
FROM
  (SELECT json_parse('{"ITEMS":{"Name":"TV"}, "price": 345}') AS data) AS json_table

Name
price

"TV"
345


Laravel 5.2

Your dependencies are causing Laravel 5.2 to error out on composer update. Specifically the tijsverkoyen/css-to-inline-styles requires symfony/css-selector 2.x and Laravel 5.2 has symfony/css-selector 3.x.
Composer update fails with: Your requirements could not be resolved to an installable set of packages.

Sorry I won't support 5.2 until it at least goes alpha.
You can better go over to css-to-inline and request a version bump.

@rakmaster  You can resolve the conflict like so...
"require" : {
  "symfony/css-selector" : "3.0.0 as 2.0.0"
}

Change 3.0.0 and 2.0.0 as needed to reflect the actual version you want and what it's required by this package.


Fix outcome printer for locally abstract types

before
'ae<'a> => 'a

after
'a. e<'a> => 'a

@amiralies this is great! Thank you.
Would it be possible to add a test? You have to add an example cas in https://github.com/rescript-lang/syntax/blob/master/tests/oprint/oprint.res Make sure it type checkes (outcome printer runs on type checked trees), and the run ./lib/test.exe -update-snapshot

I also ran into this, great to see it fixed!

@IwanKaramazow  looks like the test is printing outcome signature which does not include local type information.
for example this snippet
type rec poly<'a>

let f: type a. poly<a> => int = _ => 2

is being printed like this
type rec poly<'a>
let f: poly<'a> => int

in the expected output

Ok, I'll merge 👍  Thanks again for the fix. Appreciate the effort.

(Will take care of adding your fix with your name in the changelog)


choose-gui: init 1.3.1

Description of changes
Adds choose, a fuzzy finder for MacOS
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Both commits needs to be reworded.

maintainers: add heywoodlh

Should be first commit.
Second commit should be:

choose-gui: init 1.3.1

Notice: init is after :.

@superherointj I believe I've resolved the issues you have raised, please let me know if there's anything else you need from me.

@superherointj I believe I've resolved the issues you have raised, please let me know if there's anything else you need from me.

I have provided you general advice.
I don't have a Darwin host so I can't test this package myself.
I suggest you to forward it for review by darwin maintainers.

choose-gui commit message body is missing:

Release: https://github.com/chipsenkbeil/choose/releases/tag/1.3.1

(Whenever adding a new package, add the release link to the commit message. This is used by reviewers.)

heywoodlh, don't get discouraged if you are having a rough start here at nixpkgs.
What happens is, you don't know the format of things yet. So you get these endless review loops and delays.
Once you get the hang of things, you start getting instant merges (which is often happens with me).
Also, once you start helping you get back and forth reviews from contributors that are alike (same ecosystem).
So things flow faster.
I multi-task over many unrelated tasks, so the feedback you are going to get might vary.
Whenever someone thinks your code is good, they're very likely to merge it.
We don't like open PRs/issue. We strive to close them all.
It is just too much for not that many contributors.
Anyway, my point is, I expect your improve to improve over time.
Just keep going. And don't mind the delays.
I recommend having a personal nixpkgs fork (for cherry-picking commits) and a nix overlay (for doing experiments and being a limbo for nixpkgs).

@superherointj I really appreciate the encouragement, it's very helpful, especially for a noob like myself! :smile:

choose-gui commit message body is missing

I'm not sure I'm following. Can you provide me an example of how this looks in another package for me to replicate?

I suggest you to forward it for review by darwin maintainers.

How do you suggest I do this?

choose-gui commit message body is missing

I'm not sure I'm following. Can you provide me an example of how this looks in another package for me to replicate?

Git commits have a title and a body. You just have to add to the body of commit message the line:

Release: https://github.com/chipsenkbeil/choose/releases/tag/1.3.1

Try:

git rebase -i HEAD~2

Alter from pick to reword the commit you want to edit the message, save+exit editor, this will re-open editor for editing the commit message.
The title of commit message is already right. You just have to paste the missing line to the next line, which is the 'body' of commit message.

I suggest you to forward it for review by darwin maintainers.

How do you suggest I do this?

There isn't a perfect recipe.
To find reviewers:

There is a darwin channel at Matrix. You can ask for reviews there.

Seek people in nixpkgs that have merged/builds darwin PRs.

Find contributors using "git history" (At GitHub interface is easy) at darwin packages.

Remember active contributors for each ecosystem. Forward requests to those people.

How to proceed:
Add one person at a time with interval (1/day is good) until your issue is sorted.
If you were to ping too many people at once, you'd warn people unnecessarily.
As we don't know who is available, we just keep adding people until someone answers.
As you are not a contributor yet you can't add 'users' for review yet. But you can message tagging. Like:

@username Review, please?

I'll ask @wegank to review this PR since I know he is a darwin user and very active.
We should never forward the same person too many PRs, or else they get annoyed/bogged down.
Once I forwarded 200 PRs to SuperSandro2000. Poor Sandro. S2
TL-DR: Use your good sense.

@superherointj I really appreciate the encouragement, it's very helpful, especially for a noob like myself! 😄

I've been there. And it's never easy, it gets better but some challenges remain, like dealing with people? But still, it is worth to keep going. The correct/ideal way of using Nix is upstreaming. If you don't, you have debt (code drifts) and lose upkeep from others. The process of upstreaming becomes easier over time. But people are still people. I should write a blog post on this. (I just need to find the time for it.)

Result of nixpkgs-review pr 288931 run on aarch64-darwin 1

1 package built:

choose-gui

The binary works, it's just a bit sad that it's not built from source...

The binary works, it's just a bit sad that it's not built from source...

@wegank my most recent push fixes that! :smile: Was fun dive into MacOS build tooling for me.
This PR is currently failing on this check: "This PR does not cleanly list package outputs after merging."
How do I fix that? I can't seem to find a clear explanation of this.

"This PR does not cleanly list package outputs after merging."
How do I fix that? I can't seem to find a clear explanation of this.

There's an error:

error: evaluation aborted with the following error message: 'lib.customisation.callPackageWith: Function called without required argument "system" at /home/intj/.cache/nixpkgs-review/pr-288931-2/nixpkgs/pkgs/by-name/ch/choose-gui/package.nix:1, did you mean "mystem", "systemc" or "systemd"?'

Emphasis on:
Function called without required argument "system"
You need to use stdenv.hostPlatform.system (or other options there).

This PR is currently failing on this check: "This PR does not cleanly list package outputs after merging."

It's recommended to use nixpkgs-review to validate PRs.
You can catch problems early before submitting for review.

On formatting:

Use nixfmt-rfc-style formatter.
Order items by alphabetical order whenever possible. (Attrs and Lists)

On formatting:
Use nixfmt-rfc-style formatter.

Just updated my vim flake to use nixfmt-rfc-style with ALE instead of nixfmt classic :smile:
Is there something specific in the styling I should add? I'm not seeing any complaints from nixfmt-rfc-style in my vim setup.

RFC has chosen nixfmt-rfc-style.
Avoid alejandra or nixfmt(-classic).
nixfmt-rfc-style is available from 24.05 or unstable. 23.11 is missing it.
Use it manually and check. I think the difference will be clear. Particularly on parameters.

Let me know if there's anything else 😄

I'm mostly happy with package now.
I have provided you with the most advice/input I could to advance things.
Now you just need a darwin maintainer to have it merged. I suggest to re-ping our friend wegank to check if he approves/merges this.

ping @heywoodlh

Result of nixpkgs-review pr 288931 run on aarch64-darwin 1

1 package built:

choose-gui

@heywoodlh Your contributions will get easier over time as you learn the patterns. You'll see.
Nixpkgs is a harsh place, but eventually you'll learn how to endure it better. :-)
Welcome to the jungle nixpkgs!


Performance issue when a MDM tab is open

When I have no MDM tab (Table view | Fileclass fields | Fileclass settings) open, performance in Obsidian is great. As soon as I have one MDM tab (Table view | Fileclass fields | Fileclass settings) open, the performance becomes terrible. Editor hangs and can't keep up with my typing.
Version 0.6.5 (not sure if this was also happening in earlier version)

Hi. I can be due to the building of the table.
Each time there's a modification in a file, dataview trigger a refresh of their queries, and therefore this triggers a refresh of the table that can consume a lot of CPU due to the numerous cells and buttons...
One thing you can try is to limit the number of rows per page. Start small (10 rows or so) and see if it improves the performance
This limit can be set globally in the plugin settings or per fileClass (if you have only some specific fileClass that has tons of fields and many matched files)

Thanks, that helps a great deal.

Each time there's a modification in a file, dataview trigger a refresh of their queries, and therefore this triggers a refresh of the table that can consume a lot of CPU due to the numerous cells and buttons...

Would it possible to only trigger the refresh of dataview queries when a tab or window is in front?

I also found that the typing performance is significantly worse when mapping a folder to a fileclass instead of manually adding the fileclass onto every file.

Thanks, that helps a great deal.

Each time there's a modification in a file, dataview trigger a refresh of their queries, and therefore this triggers a refresh of the table that can consume a lot of CPU due to the numerous cells and buttons...

Would it possible to only trigger the refresh of dataview queries when a tab or window is in front?

This should now be the case since 0.6.11.
I'm closing this issue. Don't hesitate to reopen one if you experience slowness in other situations


update smoove path for quay image

The quay image has smoove installed at /usr/local/bin/smoove brentp's image had it installed at /usr/bin/smoove. This PR updates the cwl command to match the docker image.

I'm unable to get the the quay docker image to actually succeed in running smoove. I've tried tags 0.2.6--0, 0.2.6--h9ee0642_1, 0.2.7--h9ee0642_0 from quay
I keep getting an error about missing libraries
[smoove]:([E]lumpy-filter) 2021/07/02 18:24:05 lumpy_filter: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

I'm going to make a new PR to go back to the working brentp docker image and upgrade to v0.2.7


pyscf: backport of h5py fixes

Motivation for this change
Backport of h5py fixes, which make the latest stable PySCF and h5py releases compatible.
Closes #138127
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 138130 at 59409701 run on x86_64-linux 1

2 packages built successfully:

python38Packages.pyscf
python39Packages.pyscf

1 suggestion:

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/python-modules/pyscf/default.nix:16:15:
   |
16 |   patches = [ ./h5py.patch ];
   |               ^

@GrahamcOfBorg build python3Packages.pyscf


Compress Linux release

Currently only the Windows release is compressed, it seems odd that the Linux release is only tar'd, normally you'd see that either gunzip'd or xz'd.
Any reason for why the Linux release isn't compressed?

Simple answer really. I compile these releases on windows and use 7zip to create the tar files.
I plan on setting up GitHub build actions to generate our releases for us in the future and these will probably be tar.gz


Update App.js

Added col

This change is

@-gooroo.dev/

@gooroo-dev review

@gooroo-dev please review


WebView2 does not work with WindowsAppSdk and Windows 1809

Describe the bug
We're using WebView2 with the WindowsAppSdk but on Windows 1809 (Version 17763) it crashes since EnsureCoreWebView2Async fails
It works on later versions of Windows and it works using the WebView2 Preview for WinUI2.
It's a clean set up machine with the WebView2 Standalone Runtime and Microsoft Edge installed
The error in the event log says:
Activation context generation failed for "C:\Users\user\AppData\Local\Packages.....\LocalCache\Local\Microsoft\EdgeWebView\Application\96.0.1054.62\msedgewebview2.exe". Dependent Assembly 96.0.1054.62,language="*",type="win32",version="96.0.1054.62" could not be found. Please use sxstrace.exe for detailed diagnosis.
Steps to reproduce the bug
Create a new WindowsAppSdk project
Add Webview2 to the view
Call "EnsureCoreWebView2Async" on the WebView
The CoreWebView2 prperty will still be null and there will be an erro in the event viewer
Expected behavior
It works on other versions of windows so I'd expect it to work on 1809 as well
Screenshots
No response
NuGet package version
1.0.0
Packaging type
Packaged (MSIX)
Windows version
Windows 10 version 1809 (17763, October 2018 Update)
IDE
Visual Studio 2022-preview
Additional context
No response

Reopening for investigation.

Is there any news on this?


Ticket 465876 - markers not shown over association

Created a bugfix branch, waiting for feedback from the client to test this

Merged, closing issue


Test PR - disregard

 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.

Coverage increased (+1.3%) to 92.261% when pulling 546ca142aa08c8459cc78cfe98241d46e1f92e5b on develop into abcee41324b5f1f8a16bd5aa9115db9addf5718e on master.


Compile error

After adding the lib using cargo, i'm getting the following error:
compile_error!(
    "one of the features ['runtime-actix-native-tls', 'runtime-async-std-native-tls', \
     'runtime-tokio-native-tls', 'runtime-actix-rustls', 'runtime-async-std-rustls', \
     'runtime-tokio-rustls'] must be enabled"
);

Sounds like you haven't selected an async runtime yet. Welds is built as a wrapper around sqlx and sqlx really wants you to specify exactly what async runtime to use.
I think you just need to add a couple more dependencies to your Cargo.toml file
something like this if you want to use async-std
async-std = { version = "1", features = ["attributes"] }
sqlx = { version = "0.6", features = [ "runtime-async-std-rustls",  "macros"] }
welds = { version = '0.1', features=["sqlite", "detect", "check"] }

or like this if you like tokio
tokio = { version = "1", features = ["rt", "macros"]}
welds = { version = '0.1', features = ["sqlite", 'detect', 'check']  }
sqlx = { version = "0.6", features = [ 'runtime-tokio-rustls',  "macros"] }

of course you will want to enable the feature for the DB type you want to use (sqlite, postgres, mysql, mssql)

I missed the runtime feature in sqlx. thanks for the help ☺


Integrated terminal with zsh on macOs Catalina starts with incorrect CWD

Using zsh on the latest macOs (Catalina) results in a different initial working directory than the one seen in Mojave.
Expected cwd:
/Users/{user}/project
Actual cwd:
/System/Volumes/Data/Users/{user}/project

VSCode Version: 1.36.0-insider
OS Version: macOs 10.15 Beta (Catalina)

Steps to Reproduce:

Open a project folder
Open integrated terminal with zsh shell
Run pwd command

Does this issue occur when all extensions are disabled?: N/A

Is /System/Volumes/Data/Users a symlink to /Users? Can you share your settings.json file?

Not a symbolic link, but rather a "firm link", something Apple came up with, and is new to the new system volume in Catalina.
My settings.json.

Related: https://github.com/microsoft/vscode/issues/59291

@Tyriar this issue seems related too: https://github.com/eamodio/vscode-gitlens/issues/800#issuecomment-516682411

@misolori do you see this issue?

@Tyriar nope


Error: Pipeline issues when execute azd pipeline config .

Describe the issue:
Running azd pipeline config reports errors, as follows:

Configure Azure Developer Pipeline: Build and test - jobs: ubuntu and macos latest /Node.js v20

Configure Azure Developer Pipeline: Build and test - jobs: windows latest /Node.js v20

Configure Azure Developer Pipeline: Build and test - jobs:  build_test_all

Configure Azure Developer Pipeline: Deploy to Azure

Repro Steps:

azd init --template llama-index-python
azd auth login
azd pipeline config

Environment:

azd version: 1.9.5 (commit cd2b7af9995d358aab33c782614f801ac1997dde)
OS: Windows11, Dev containers, Codespace

Expected Behavior:
azd pipeline config runs successfully.
@marlenezw and @hemarina for notification.

Github actions is now working as expected with pipeline config


Failed to distributedLoad data

Alluxio Version:
alluxio version -r
2.4.1-2-bfff8c6881e5cb045fd1d84c59acba26078bb4d9
Describe the bug
Failed to distributedLoad.
bash-4.4# alluxio fs mount
https://mirrors.bit.edu.cn/apache/spark  on  /spark  (web, capacity=-1B, used=-1B, read-only, not shared, properties={})
/underFSStorage                          on  /       (local, capacity=0B, used=0B, not read-only, not shared, properties={})
bash-4.4# alluxio getConf |grep alluxio.job.master.finished.job.retention.time
alluxio.job.master.finished.job.retention.time=30sec
bash-4.4# alluxio getConf |grep alluxio.job.master.job.capacity
alluxio.job.master.job.capacity=100000

Run distributedLoad, and only 73% is cached
bash-4.4# alluxio fs du -sh /
File Size     In Alluxio       Path
2779.78MB     0B (0%)          /
bash-4.4# time alluxio fs distributedLoad /spark
/spark/spark-3.1.1/SparkR_3.1.1.tar.gz loading
/spark/spark-3.1.1/spark-3.1.1-bin-without-hadoop.tgz loading
/spark/spark-3.1.1/pyspark-3.1.1.tar.gz loading
/spark/spark-3.1.1/spark-3.1.1.tgz loading
/spark/spark-3.1.1/spark-3.1.1-bin-hadoop2.7.tgz loading
/spark/spark-3.1.1/spark-3.1.1-bin-hadoop3.2.tgz loading
/spark/spark-3.0.2/spark-3.0.2.tgz loading
/spark/spark-3.0.2/pyspark-3.0.2.tar.gz loading
/spark/spark-3.0.2/spark-3.0.2-bin-hadoop2.7-hive1.2.tgz loading
/spark/spark-3.0.2/spark-3.0.2-bin-hadoop2.7.tgz loading
/spark/spark-3.0.2/spark-3.0.2-bin-hadoop3.2.tgz loading
/spark/spark-3.0.2/SparkR_3.0.2.tar.gz loading
/spark/spark-3.0.2/spark-3.0.2-bin-without-hadoop.tgz loading
/spark/spark-2.4.7/pyspark-2.4.7.tar.gz loading
/spark/spark-2.4.7/SparkR_2.4.7.tar.gz loading
/spark/spark-2.4.7/spark-2.4.7.tgz loading
/spark/spark-2.4.7/spark-2.4.7-bin-hadoop2.7.tgz loading
/spark/spark-2.4.7/spark-2.4.7-bin-hadoop2.6.tgz loading
/spark/spark-2.4.7/spark-2.4.7-bin-without-hadoop.tgz loading
/spark/spark-2.4.7/spark-2.4.7-bin-without-hadoop-scala-2.12.tgz loading
Attempt 1 to load /spark/spark-3.0.2/spark-3.0.2-bin-hadoop3.2.tgz failed because: Task execution failed: Failed to allocate 268435456 bytes on BlockStoreLocation{TierAlias=MEM, DirIndex=<Any>, MediumType=<Any>} to create blockId 134217728 (GrpcDataWriter{request=type: ALLUXIO_BLOCK
id: 134217728
tier: 0
medium_type: ""
pin_on_create: false
space_to_reserve: 268435456
, address=WorkerNetAddress{host=<IP_ADDRESS>, containerHost=, rpcPort=20011, dataPort=20011, webPort=20012, domainSocketPath=, tieredIdentity=TieredIdentity(node=<IP_ADDRESS>, rack=null)}})
Successfully loaded path /spark/spark-3.0.2/SparkR_3.0.2.tar.gz after 1 attempts
Successfully loaded path /spark/spark-2.4.7/SparkR_2.4.7.tar.gz after 1 attempts
Attempt 1 to load /spark/spark-2.4.7/spark-2.4.7-bin-without-hadoop.tgz failed because: Task execution failed: Failed to allocate 268435456 bytes on BlockStoreLocation{TierAlias=MEM, DirIndex=<Any>, MediumType=<Any>} to create blockId 251658240 (GrpcDataWriter{request=type: ALLUXIO_BLOCK
id: 251658240
tier: 0
medium_type: ""
pin_on_create: false
space_to_reserve: 268435456
, address=WorkerNetAddress{host=<IP_ADDRESS>, containerHost=, rpcPort=20011, dataPort=20011, webPort=20012, domainSocketPath=, tieredIdentity=TieredIdentity(node=<IP_ADDRESS>, rack=null)}})
Successfully loaded path /spark/spark-3.1.1/SparkR_3.1.1.tar.gz after 1 attempts
Attempt 1 to load /spark/spark-3.0.2/spark-3.0.2-bin-without-hadoop.tgz failed because: Task execution failed: Failed to allocate 268435456 bytes on BlockStoreLocation{TierAlias=MEM, DirIndex=<Any>, MediumType=<Any>} to create blockId 184549376 (GrpcDataWriter{request=type: ALLUXIO_BLOCK
id: 184549376
tier: 0
medium_type: ""
pin_on_create: false
space_to_reserve: 268435456
, address=WorkerNetAddress{host=<IP_ADDRESS>, containerHost=, rpcPort=20011, dataPort=20011, webPort=20012, domainSocketPath=, tieredIdentity=TieredIdentity(node=<IP_ADDRESS>, rack=null)}})
Attempt 1 to load /spark/spark-2.4.7/pyspark-2.4.7.tar.gz failed because: Task execution failed: Failed to allocate 268435456 bytes on BlockStoreLocation{TierAlias=MEM, DirIndex=<Any>, MediumType=<Any>} to create blockId 285212672 (GrpcDataWriter{request=type: ALLUXIO_BLOCK
id: 285212672
tier: 0
medium_type: ""
pin_on_create: false
space_to_reserve: 268435456
, address=WorkerNetAddress{host=<IP_ADDRESS>, containerHost=, rpcPort=20011, dataPort=20011, webPort=20012, domainSocketPath=, tieredIdentity=TieredIdentity(node=<IP_ADDRESS>, rack=null)}})
Successfully loaded path /spark/spark-3.0.2/spark-3.0.2.tgz after 1 attempts
Successfully loaded path /spark/spark-3.1.1/spark-3.1.1.tgz after 1 attempts
Successfully loaded path /spark/spark-2.4.7/spark-2.4.7.tgz after 1 attempts
Successfully loaded path /spark/spark-3.1.1/pyspark-3.1.1.tar.gz after 1 attempts
Successfully loaded path /spark/spark-3.0.2/spark-3.0.2-bin-hadoop2.7.tgz after 1 attempts
Successfully loaded path /spark/spark-2.4.7/spark-2.4.7-bin-without-hadoop-scala-2.12.tgz after 1 attempts
Successfully loaded path /spark/spark-2.4.7/spark-2.4.7-bin-hadoop2.7.tgz after 1 attempts
Successfully loaded path /spark/spark-2.4.7/spark-2.4.7-bin-hadoop2.6.tgz after 1 attempts
Successfully loaded path /spark/spark-3.1.1/spark-3.1.1-bin-without-hadoop.tgz after 1 attempts
Successfully loaded path /spark/spark-3.0.2/spark-3.0.2-bin-hadoop2.7-hive1.2.tgz after 1 attempts
Successfully loaded path /spark/spark-3.0.2/pyspark-3.0.2.tar.gz after 1 attempts
Successfully loaded path /spark/spark-3.1.1/spark-3.1.1-bin-hadoop2.7.tgz after 1 attempts
Successfully loaded path /spark/spark-3.1.1/spark-3.1.1-bin-hadoop3.2.tgz after 1 attempts

real	1m1.188s
user	0m12.984s
sys	0m2.422s
bash-4.4# alluxio fs du -sh /
File Size     In Alluxio       Path
2779.78MB     2047.52MB (73%)  /

To Reproduce
Steps to reproduce the behavior (as minimally and precisely as possible)
Expected behavior
A clear and concise description of what you expected to happen.
Urgency
Describe the impact and urgency of the bug.
Additional context
Add any other context about the problem here.

Check alluxio logs
diagnose_fluid_1614917197.tar.gz
tar -xvf diagnose_fluid_1614917197.tar.gz
cd tmp/diagnose_fluid_1614917197/pods-default/

The properties:
  alluxio.fuse.cached.paths.max: "1000000"
  alluxio.fuse.debug.enabled: "false"
  alluxio.fuse.jnifuse.enabled: "true"
  alluxio.fuse.logging.threshold: 1000ms
  alluxio.fuse.shared.caching.reader.enabled: "true"
  alluxio.fuse.user.group.translation.enabled: "true"
  alluxio.job.master.finished.job.retention.time: 30sec
  alluxio.job.master.rpc.port: "20013"
  alluxio.job.master.web.port: "20014"
  alluxio.job.worker.data.port: "20017"
  alluxio.job.worker.rpc.port: "20015"
  alluxio.job.worker.threadpool.size: "164"
  alluxio.job.worker.web.port: "20016"
  alluxio.master.journal.folder: /journal
  alluxio.master.journal.log.size.bytes.max: 500MB
  alluxio.master.journal.type: UFS
  alluxio.master.metadata.sync.concurrency.level: "128"
  alluxio.master.metadata.sync.executor.pool.size: "128"
  alluxio.master.metadata.sync.ufs.prefetch.pool.size: "128"
  alluxio.master.metastore: ROCKS
  alluxio.master.metastore.inode.cache.max.size: "10000000"
  alluxio.master.mount.table.root.ufs: /underFSStorage
  alluxio.master.rpc.executor.core.pool.size: "128"
  alluxio.master.rpc.executor.max.pool.size: "1024"
  alluxio.master.rpc.port: "20009"
  alluxio.master.security.impersonation.root.groups: '*'
  alluxio.master.security.impersonation.root.users: '*'
  alluxio.master.web.port: "20010"
  alluxio.security.authorization.permission.enabled: "false"
  alluxio.security.stale.channel.purge.interval: 365d
  alluxio.underfs.object.store.breadcrumbs.enabled: "false"
  alluxio.user.block.avoid.eviction.policy.reserved.size.bytes: 2GB
  alluxio.user.block.master.client.pool.gc.threshold: 2day
  alluxio.user.block.master.client.threads: "1024"
  alluxio.user.block.size.bytes.default: 256MB
  alluxio.user.block.worker.client.pool.min: "512"
  alluxio.user.block.write.location.policy.class: alluxio.client.block.policy.LocalFirstAvoidEvictionPolicy
  alluxio.user.client.cache.enabled: "false"
  alluxio.user.direct.memory.io.enabled: "true"
  alluxio.user.file.create.ttl.action: FREE
  alluxio.user.file.master.client.threads: "1024"
  alluxio.user.file.passive.cache.enabled: "false"
  alluxio.user.file.readtype.default: CACHE
  alluxio.user.file.replication.max: "1"
  alluxio.user.file.writetype.default: MUST_CACHE
  alluxio.user.local.reader.chunk.size.bytes: 256MB
  alluxio.user.logging.threshold: 1000ms
  alluxio.user.metadata.cache.enabled: "true"
  alluxio.user.metadata.cache.expiration.time: 2day
  alluxio.user.metadata.cache.max.size: "6000000"
  alluxio.user.metrics.collection.enabled: "true"
  alluxio.user.streaming.data.timeout: 300sec
  alluxio.user.streaming.reader.chunk.size.bytes: 256MB
  alluxio.user.ufs.block.read.location.policy: alluxio.client.block.policy.LocalFirstPolicy
  alluxio.user.update.file.accesstime.disabled: "true"
  alluxio.user.worker.list.refresh.interval: 2min
  alluxio.web.ui.enabled: "false"
  alluxio.worker.allocator.class: alluxio.worker.block.allocator.MaxFreeAllocator
  alluxio.worker.block.master.client.pool.size: "1024"
  alluxio.worker.file.buffer.size: 320MB
  alluxio.worker.network.reader.buffer.size: 256MB
  alluxio.worker.rpc.port: "20011"
  alluxio.worker.web.port: "20012"

same issue: https://github.com/fluid-cloudnative/fluid/issues/633


Update tests to pass.

Looks like because of https://github.com/defunctzombie/zuul/issues/86 PRs that are not by Seth are not going to to get tested properly via Travis and SauceLabs.
Instead we'll have to detect when tests are being run on Travis and use headless testing, probably via electron.  Leaving this example here for reference: https://github.com/feross/webtorrent/blob/master/bin/test.js


[SPARK-45109][SQL][CONNECT][FOLLOWUP] Fix log function in Connect

What changes were proposed in this pull request?
This is a follow-up PR to https://github.com/apache/spark/pull/42863, the 1 argument log function should also point to ln.
Why are the changes needed?
Bugfix.
Does this PR introduce any user-facing change?
No, these Spark Connect functions haven't been released.
How was this patch tested?
Exsiting UTs.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @zhengruifeng, @xuanyuanking, @HyukjinKwon

For some reasons, it can't find the build. The build is here: https://github.com/peter-toth/spark/actions/runs/6143939836/job/16668358616

For some reasons, it can't find the build. The build is here: https://github.com/peter-toth/spark/actions/runs/6143939836/job/16668358616

Yeah I notivced that and force pushed a new commit so test are running now.
But I've run into this issue a few times, it happened here too: https://github.com/apache/spark/pull/42863#issuecomment-1712779217

3.4 PR: https://github.com/apache/spark/pull/42872


ionic resources didn't generate 83.5x83.5@2x app icon for iPad Pro

From @MrBokeh on March 27, 2016 4:47
Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
Short description of the problem:
ionic resources command didn't generate 83.5x83.5@2x app icon for iPad Pro
What behavior are you expecting?
ionic resources command to generate 83.5x83.5@2x app icon for iPad Pro
Steps to reproduce:

put icon.psd to resources folder
run ionic resources
warning on the xcode prpoject says it's missing the 83.5x83.5@2x app icon

ionic resources

Which Ionic Version? 1.x or 2.x
1.x and 2.x
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.0.0
Ionic Version: 2.0.0-beta.3
Ionic CLI Version: 2.0.0-beta.22
Ionic App Lib Version: 2.0.0-beta.12
ios-deploy version: 1.8.5
ios-sim version: 5.0.6
OS: Mac OS X El Capitan
Node Version: v5.9.0
Xcode version: Xcode 7.3 Build version 7D175
Copied from original issue: driftyco/ionic#5955

Hello! Thanks for opening an issue with us! As this issue is related to the ionic-cli and not the framework i  will be moving this issue to that repo. Thanks again!

Similarly, the 40pt@3x icon (iPhone Spotlight) is not being created


Adds check about ssh bypass

https://redmine.openinfosecfoundation.org/issues/4508
Suricata PR to come

Merged. Thanks.


GetProjects stats

Codecov Report

Merging #158 into develop will decrease coverage by 6.57%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##           develop     #158      +/-   ##
===========================================
- Coverage    47.82%   41.25%   -6.58%
===========================================
  Files           11       11
  Lines           69       80      +11
  Branches         8        9       +1
===========================================
  Hits            33       33
- Misses          34       44      +10
- Partials         2        3       +1

Impacted Files
Coverage Δ

src/models/Project/index.js
0% <0%> (ø)
:arrow_up:

src/models/Stats/index.js
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Next steps for replaying offline analytics

Background
Hey all—there are a number of outstanding open issues related to workbox-google-analytics, as well as questions and issues from folks who are planning to move to Google Analytics 4. We thought it would be helpful to take a step back and reevaluate our original decision to ship "offline Google Analytics" as a core module in Workbox.
What does workbox-google-analytics currently do?
workbox-google-analytics's functionality can be broken down into a few parts:

It registers runtime caching routes to match requests for the CDN-served JavaScript files needed to use the Google Analytics runtime, and handles those with a network-first strategy. This ensures that if you're offline, the necessary JavaScript can still be loaded.
It registers runtime caching routes for the actual Google Analytics data collection requests, using a network-only strategy along with a properly configured instance of the BackgroundSyncPlugin.
That BackgroundSyncPlugin is configured to attempt to modify the qt parameter, if present, when replaying failed data collection requests in order to reflect the original time the request was attempted. If there was a failed request that then successfully resent via background sync after, say, two hours, the modified qt parameter will tell Google Analytics that the event actually happened two hours ago.

And that's about it.
Problems with the current approach
First off, there are other similar platforms to Google Analytics, but Workbox has never shipped an "official" module for any of them. This might have given the false impression that using Google Analytics was required if you wanted offline analytics, when in fact it was just a question of mixing together the right runtime caching and background sync logic for your analytics platform of choice.
Second, we've historically had to play catch-up with Google Analytics as they're rolled out new URLs for loading the runtime libraries and new data collection endpoints. This doesn't happen too often, but having workbox-google-analytics paper over the underlying URLs that are supported can be confusing to folks who need to use a specific, newer interface, and are confused why it doesn't work.
Third, there is no officially supported Google Analytics 4 equivalent to the qt parameter, which the BackgroundSyncPlugin uses to indicate the time at which the event originally occurred. Automatically setting this parameter was one of the main benefits that workbox-google-analytics offered, and that benefit will no longer be relevant.
The plan moving forward
Given all that, our current plan is to cease new development of workbox-google-analytics and mark the module as deprecated. Until you upgrade to Google Analytics v4, you should be able to continue using it, but we're not likely to add in any additional functionality and may not address all the open issues.
Instead, what we'd like to do is take a "recipes" approach to enabling offline analytics, similar to how we've previously offered guidance for other use cases, like serving cached media files.
We will create new copy-and-pasteable documentation that shows how to mix bits of workbox-routing, workbox-strategies, and workbox-background-sync together to get the similar functionality for legacy Google Analytics, Google Analytics 4 (without the ability to adjust the original event timestamp), as well similar documentation for any other analytics platforms that people would like to contribute.
If members of the community would like to take these snippets of Workbox code and package them up into an unofficial module, they're more than welcome to do so—we love seeing folks build and release third-party enhancements to Workbox!
If there's sufficient demand, we may also package up these recipes and release them as part of the workbox-recipes module, which would then roughly serve the same purpose of the current workbox-google-analytics. I'm not clear how important that is to the community vs. having the usage outlined in our documentation. Please let us know if you feel strongly about it!

@jeffposnick any plans to release recipes for GA4? Thanks.

CC: @tropicadri, who is the new lead for Workbox, to see whether there is any update on that front.

How fare is this plan? Is there a roadmap? :)

Looking to update... any updates on this?

Any updates on this? @jeffposnick

https://github.com/GoogleChrome/workbox/issues/3149#issuecomment-1368923167
CC: @tropicadri

Hi there,
Workbox is moving to a new engineering team within Google. As part of this move, we're declaring a partial bug bankruptcy to allow the new team to start fresh. We realize this isn't optimal, but realistically, this is the only way we see it working. For transparency, here're the criteria we applied:

For PRs, we closed everything that doesn't target the current v7 branch.
For Issues, we closed everything that was created before 2024.

Thanks, and we hope for your understanding!
The Workbox team


2022031202

Adding miners from Issue #2180, see that same isseu for the proof of the ones i add.
Seems like the denylist is sort of a mess as windows sorting does it differently then Linux command.
This PR includes the miners from #2340  as that one is signed by mulitple signers.
Edit: sorry if something went wrong, first time doing something with Github

let's see if we can land each one separately. hopefully enough signers come through on the first one.

let's see if we can land each one separately. hopefully enough signers come through on the first one.

I have done the serial to 02 at the end and this one already includes all the miners from the other PR, so if that one comes through (it already has 3 signers, isnt that enough?) this can follow up right away.

let's see if we can land each one separately. hopefully enough signers come through on the first one.

I have done the serial to 02 at the end and this one already includes all the miners from the other PR, so if that one comes through (it already has 3 signers, isnt that enough?) this can follow up right away.

Yup. It should apply cleanly then once 01 merges.

let's see if we can land each one separately. hopefully enough signers come through on the first one.

I have done the serial to 02 at the end and this one already includes all the miners from the other PR, so if that one comes through (it already has 3 signers, isnt that enough?) this can follow up right away.

Yup. It should apply cleanly then once 01 merges.

Ok thx, hope the other actually gets pulled.
Giving a error now although it has 3 signatures.

@abhay Will appeals like this still be handled?

+2,153 −2,121
So an addition addition of around 30 hotspots (changes in the sig also count).
Would be good if you could at least post some of the new ones, so we can do some checks.  It's pretty impossible now to find what's new since I can't find how to filter out your additions (since you changed the sorting....).

this will need to be rebased and sorted @Miniterror


Update README.md

Possible API change that was missed?

Ah, yeah, must have missed that when merging the universe macros branch. You've missed the s from the end of setSystems in your update though.

woops fixed!


Documentation: missing instructions if setupTests.js is added after an eject

initializing-test-environment  doesn't explain that
"setupTestFrameworkScriptFile": "<rootDir>/src/setupTests.js",
needs to be added to package.json if src/setupTests.js is created after the app has been "ejected" as createJestConfig only adds this configuration if the file is present (makes sense).
Standard template being:
{
  …
  "jest": {
    "setupFiles": [
      …
    ],
    "setupTestFrameworkScriptFile": "<rootDir>/src/setupTests.js",

Docs says that "At this point you’re on your own." (After eject).

@josmardias so you want to punish them for that? 😜 @gaearon if it was code-related I would have PRed but as it’s text, I don’t feel safe.

@diligiant
Not at all, I wish them all the luck on the universe.
The problem is: I'm not sure if there is a category of post-eject situations that we should cover on docs, while ignoring all the rest.
The solution adopted on this project (correct me if I'm wrong) is to simply don't cover any of them.
But maybe we can solve this case without docs: on eject create an empty setupTests.js if there isn't one,  so we can always add this configuration on package.json.
What you think?

Creating setupTests.js should work just fine without eject (has been my experience at least) or editing package.json.

You mean create a placeholder right before L17 in createJestConfig.js? That would do.
I can't remember if placeholders are a genuine practice in this project though and I wonder if we're not adding complexity for "nothing".
I agree about the "you're on your own" part but there is an eject, ie things work as usual if you don't touch anything - it's just frozen at that point. But this isn't true of this setup feature as it is not dynamically evaluated by the test script but statically once by the eject script.

I'm stepping on this issue to help the community avoid adding complexity :smile:
So, I agree with you. We should carefully evaluate before about adding complexity.
Unfortunately, I don't feel I'm the one to judge that.
What I think is: if something should be done at all about this issue, I prefer to solve it adding code complexity over docs complexity. Placeholders just for post-eject situations seems fair to me. So we can continue avoiding docs for post-eject and thinks just works.
I think maintainers are willing to accept a PR for this :smiley:

I believe this has came up before and I don't think we'd want to create an empty src/setupTests.js.
I think we just need to add a line in the docs that this needs to be manually configured after ejecting.
No need for a long winded explanation either, we can just link to some Jest doc -- anyone ejecting should know how to configure a test setup file, so we just need to let them know it's not done automatically.

Seems like I was wrong :wink:

Just happened to me, and this question was my solution. So :+1: for adding it into docs.

I didn't run eject and my App doesn't pick up the setupTests.js
//src/setupTests.js

import Enzyme from 'enzyme';
import Adapter from 'enzyme-adapter-react-16';

Enzyme.configure({ adapter: new Adapter() });

I still get this error when I add the code above to setupTests.js:
Enzyme Internal Error: Enzyme expects an adapter to be configured, but found none....
If I add the code to the test file itself, it works fine.
I tried adding the following to the package.json but it still didn't work...
"jest": {
    "setupTestFrameworkScriptFile": "<rootDir>/src/setupTests.js"
}

Any tips?

I have the same problem as Doug.
src/setupTests.js and it doesn't work.
Yet if I place the code in the test files themselves, it works.

@dreadrocksean
Please, send here a link to a repro so we can see for ourselves and debug.

Same here! react-create-app makes me want to cry! haha

Same here! It simply does not work for me when placing setupTests.js in src/

Same here ... well you need a repo to reproduce the bug ... I'll try to find the time to do it ...

I ended up just adding the --setupFiles flag to the package.json test command:
react-scripts-ts test --env=jsdom --setupFiles ./src/setupTests.js


Android, 2048x1024 HLS/MP4 does not play

Hello guys,
we have tried to play HLS/MP4 with resolutions like 2048x1024 and up to UHD/4k and they do not play, have got following exception:
com.google.android.exoplayer2.mediacodec.MediaCodecRenderer$DecoderInitializationException: Decoder init failed: OMX.qcom.video.decoder.avc, Format(null, null, video/avc, -1, null, [2048, 1024, -1.0], [-1, -1])
We have checked the same stream on the same device in Chrome and it's playable there.
Curious, what Exoplayer version do you use?
What resolutions have you successfully tested on Android?
Thanks.

Hey @newbot23, currently we are targeting the an older exoplayer version (exoplayer:r2.2.0). We've successfully tested resolutions like 1920x1080. As such I'm wondering if this issue can be resolved by upgrading to a later release.
To help with the diagnosis, could you provide:

A sample HLS/MP4 link with a 2048x1024 and UHD/4k resolution that we can verify and confirm with the bug with?
The Device model, and it's Android OS version the bug occurs on, and it's screen size (if possible).

hi @dthian, thanks for your promt reply.

Here are the links:
https://static-vrticket.cdnvideo.ru/vrticket/bbb_3840x1920.mp4
https://static-vrticket.cdnvideo.ru/vrticket/bbb_2880x1440.mp4
https://static-vrticket.cdnvideo.ru/vrticket/bbb_2048x1024.mp4

Devices:
Redmi 4X, Android 7.1.2
Redmi 4A, Android 6.0.1
Nexus 7, Android 6.0.1
htc one, android 5.0

let me know please if you need anything else

Thanks @newbot23, unfortunately I'm not able to reproduce the crash yet with the links above. Could you send me the full crash stack trace?

Thanks @dthian, will provide the full crash stack trace und build.gradle tomorrow.
Would you please tell me, do the links play normally?

@newbot23, yup the 3 links above plays normally on our devices.
I've tested so far on an S6 and a Pixel 2 device and verified that the video plays as expected.

@dthian here are the details
full stack trace
11-27 14:49:43.463 2945-3287/com.example.viro E/ExoPlayerImplInternal: Renderer error.    com.google.android.exoplayer2.ExoPlaybackException        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.throwDecoderInitError(MediaCodecRenderer.java:376)        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.maybeInitCodec(MediaCodecRenderer.java:363)        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.onInputFormatChanged(MediaCodecRenderer.java:770)        at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.onInputFormatChanged(MediaCodecVideoRenderer.java:341)        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.readFormat(MediaCodecRenderer.java:501)        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:484)        at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:464)        at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:300)        at android.os.Handler.dispatchMessage(Handler.java:98)        at android.os.Looper.loop(Looper.java:154)        at android.os.HandlerThread.run(HandlerThread.java:61)        at com.google.android.exoplayer2.util.PriorityHandlerThread.run(PriorityHandlerThread.java:40)     Caused by: com.google.android.exoplayer2.mediacodec.MediaCodecRenderer$DecoderInitializationException: Decoder init failed: OMX.qcom.video.decoder.avc, Format(null, null, video/avc, -1, null, [2048, 1024, -1.0], [-1, -1])        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.maybeInitCodec(MediaCodecRenderer.java:363)         at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.onInputFormatChanged(MediaCodecRenderer.java:770)         at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.onInputFormatChanged(MediaCodecVideoRenderer.java:341)         at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.readFormat(MediaCodecRenderer.java:501)         at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:484)         at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:464)         at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:300)         at android.os.Handler.dispatchMessage(Handler.java:98)         at android.os.Looper.loop(Looper.java:154)         at android.os.HandlerThread.run(HandlerThread.java:61)         at com.google.android.exoplayer2.util.PriorityHandlerThread.run(PriorityHandlerThread.java:40)      Caused by: android.media.MediaCodec$CodecException: Error 0xfffffff4        at android.media.MediaCodec.native_configure(Native Method)        at android.media.MediaCodec.configure(MediaCodec.java:1778)        at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.configureCodec(MediaCodecVideoRenderer.java:327)        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.maybeInitCodec(MediaCodecRenderer.java:352)        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.onInputFormatChanged(MediaCodecRenderer.java:770)         at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.onInputFormatChanged(MediaCodecVideoRenderer.java:341)         at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.readFormat(MediaCodecRenderer.java:501)         at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:484)         at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:464)         at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:300)         at android.os.Handler.dispatchMessage(Handler.java:98)         at android.os.Looper.loop(Looper.java:154)         at android.os.HandlerThread.run(HandlerThread.java:61)         at com.google.android.exoplayer2.util.PriorityHandlerThread.run(PriorityHandlerThread.java:40)
build.gradle:
def enableProguardInReleaseBuilds = false
android {
    compileSdkVersion 23
    buildToolsVersion "23.0.1"
    dexOptions {
        jumboMode true
    }
    defaultConfig {
        multiDexEnabled true
        applicationId "com.example.viro"
        minSdkVersion 21
        targetSdkVersion 25
        versionCode 34
        versionName "1.0.34"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86"
        }
    }
    productFlavors {
        gvr {
            resValue 'string', 'app_name', 'VR Ticket'
            buildConfigField 'String', 'VR_PLATFORM', '"GVR"'
        }
        ovr {
            resValue 'string', 'app_name', 'ViroCodeSamples-ovr'
            applicationIdSuffix '.ovr'
            buildConfigField 'String', 'VR_PLATFORM', '"OVR_MOBILE"'
        }
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a":1, "x86":2]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}

dependencies {
    compile project(':react-native-camera')
    compile project(':react-native-orientation')
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:25.0.0'
    compile 'com.facebook.react:react-native:+'
    compile project(':arcore_client')
    compile project(':gvr_common')
    compile project(path: ':react_viro')
    compile project(path: ':viro_renderer')
    compile 'com.google.android.exoplayer:exoplayer:r2.2.0'
    compile 'com.google.protobuf.nano:protobuf-javanano:3.0.0-alpha-7'
    compile 'com.amazonaws:aws-android-sdk-core:2.2.+'
    compile 'com.amazonaws:aws-android-sdk-ddb:2.2.+'
    compile 'com.amazonaws:aws-android-sdk-ddb-mapper:2.2.+'
    compile 'com.amazonaws:aws-android-sdk-cognito:2.2.+'
    compile 'com.amazonaws:aws-android-sdk-cognitoidentityprovider:2.2.+'
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

Hi @newbot23, can you also provide the js files representing the 3D scene with the videos that you are trying to view that causes the crash? (Just in case we missed something). Also, were you able to test the video on devices that did work (did play)?
After doing a bit of digging through online, it sounds like the crash may be caused natively by the ExoPlayer itself. There is currently an open github Exoplayer issue that contains the same error code as the ones you have provided in the stack trace (CodecException: Error 0xfffffff4).
In that situation, it looks like the user is attempting to play multiple video streams on certain Android device models, that results in that error. This is also further explained in this and this github exoplayer issue as well.
Interesting comments from these issues are:

not many devices support multiple hardware decoders simultaneously.
You may consider software decoder.

device
chipset
work

Samsung tab 2 7
TI OMAP 4430
o

Samsung S3
Exynos 4412 Quad
o

Nexus 7 2nd
Qualcomm S4Pro
x

Nexus 6
Qualcomm 805
x

and also:

It sounds like this device does not allow more than one player to be instantiated at a time. In general Android devices don't have to support playing more than one video at a time, and whether it works can also depend on the input videos' formats.

The Android M CDD (and older versions) do not require compatible devices to support playing more than one video at a time, and I don't think there are any CTS tests that fail if using two video decoders at a time doesn't work.

Thus, can you confirm:

If you have multiple ViroVideos in your scene that are streaming videos simultaneously (may cause the error).

You've mentioned previously that you've also attempted to play the same video in your chrome browser to verify the video. As such, I wonder if you could be in a situation where more than one exo player is being instantiated as well, causing the issue. Can you confirm if this is the case by killing any application that is stream your video except for the viroSample and see if the error still occurs.

Hi @dthian, thanks for your feedback and thorough investigations.
We use almost identical version of your: https://github.com/viromedia/viro/blob/master/js/ViroMediaPlayer/Viro360Theatre.js
So don't think there is a problem with that.

No, there is no other streams.
Chrome was closed before our test.
We have activated transcoding for the HLS streams in 1920x1080, and our devices play them normally. So I think it's rather a device connected issue.
Don't know whether chrome is using Exoplayer and what version exactly, but higher resolution are still playable there.
Do you have have other test devices, so you could reproduce the issue on your side?

"We have activated transcoding for the HLS streams in 1920x1080, and our devices play them normally. So I think it's rather a device connected issue."

Can you further explain what you mean from the above by activated transcoding for HLS streams? - Does it work for all your videos then once you activated it (the bug no longer repros)?
Why do you think it is a device connected issue again?

Unfortunately we were not able to reproduce your issue on our side yet. I've also tried a Nexus 5 with a similar Snap Dragon + Adreno chipset, but cannot reproduce.

Hi @dthian,

we have activated backend transcoding, so 4k stream was transcoded to 1080p stream
we have not tested with all available videos, cause they all use the same codec and settings
we think it's device connected issue because we have changed only the source and we have got different results. I agree, that it could be code related issue (because the same videos are playable in other players, e.g. chrome browser), but we don't think that it's connected with the code that we are able to change.

We have prepared a Viro Media based test player, with different resolutions, just for testing purposes:
https://www.dropbox.com/s/fp3oyoiao6gx9ds/vr-test-app.apk?dl=0 with following resolutions:

1920x960
1920x1080
2048x1024
2880x1440
3840x1920

1920x960, 1920x1080 does work on our devices (nexus 7, htc one, redmi 4x), higher resolutions - don't.

Hi, @newbot23, thanks for uploading the APK. Unfortunately, I am still unable to reproduce the issue - am still able to play the high resolution videos (3840x1920 / 2880x1440) on our devices (Nexus 5 and S6 phones here).
From the above, as the video playback works without any changes to the ViroPlatform, you are right in saying that it may be an network / video transmission issue. Thus, it sounds like the root cause of your issue is mainly due to the format of which your 4k video is transcoded and then transmitted in, and if your targeted mobile phones has supported hardware/software decoders to preview these video formats of such quality / resolutions. That is, those devices may not support decoding higher resolution videos, at least with ExoPlayer
ExoPlayer itself mentions:

By default ExoPlayer uses Android’s platform decoders. Hence the supported sample formats depend on the underlying platform rather than on ExoPlayer. Sample formats supported by Android devices are documented here. Note that individual devices may support additional formats beyond those listed.".

As such it doesn't sound like a ViroPlatform issue, but instead a limitation of the hardware on a certain Android devices.


Insufficient funds

Hello,
I've been getting the error message "Insufficient funds" for a long time when I try to use Dex or liquidity.
I reinstalled the app and rebuilt the blockchain.
The error message remains.
I need help because I don't know what to do next.
app logs.zip
Best regards Jörg

Hi @778010 , it’s likely that you've insufficient utxoDFI balance (min. 1 DFI) — which is required to perform swap and all other functions. DFI exist in 2 forms; utxoDFI and tokenDFI. utxoDFI is used to pay for transactions fees while rewards received from liquidity mining (for example) are in tokenDFI. You can freely convert between the 2 anytime — at a 1:1 ratio. To convert tokenDFI to utxoDFI, the simplest way would be via DeFi Wallet app.
Firstly, check via CLI:

getbalance — utxoDFI
gettokenbalances — tokenDFI
From your output
gettokenbalances
[
  "3.123456768@0", — tokenDFI
  "XXXXXXXXXX@2",
  "XXXXXXXXXX@5"
]

Send 1 tokenDFI to yourself:

Copy your address (the one that you're planning to use to add liquidity)
Click send DFI
Input 1 DFI
Paste the address (step 1)
Try the function again

By sending to yourself, you're converting your tokenDFI to utxoDFI. utxoDFI is used for transaction fees.
Regarding the issue Unable to add liquidity, we can further discuss on the issue there should your issue persist. We would like to keep same issues in one thread. Thank you.


Metadescription always shows 'This is meta description'

The rendered HTML always shows 'this is meta description' . This should be updated to either a PnP meta description to fall back to, and use the twitter:description that is currently used.

Seems to be solved in the posts but not on the homepage; will submit a new PR with fixes for homepage as well.