Scroll to leaf nodes instead of the branches to avoid janky scrolling behavior

We're evaluating the use of react-accessible-treeview for Sourcegraph and one issue that stood out for us that happens primarely when we're dealing with very large nested lists is that this library relies on focus() of the branch lists to move content into the viewport. Since branches can be very long (possibly longer than the total viewport height), this causes some unexpected jumping when using arrow keys to navigate as the user agent is trying to move as much of the node that was focused into the viewport as possible.
You can recreate this problem easily on the react-accessible-treeview preview page, here's a video recording from the storybook to demo the issue:
https://user-images.githubusercontent.com/458591/213458970-3330301a-af68-4bed-99dd-ef705097e955.mov
You can see in the video above that sometimes the leaf that is highlight is in the middle of the viewport and the next leaf is clearly within the viewport as well when the unexpected scrolling happens.
To fix this, I've made some changes so that in addition to the tabbable nodes (the one that the focus should move to), we're also keeping track of all leaf nodes. We can then use focus({ preventScroll: true }) and manually scroll to the leaf node.
Note that I have put the focus after the scrolling so that in the case of preventScroll being unsupported, the behavior is unchanged.
The test is a bit awkward as jsdom doesn't seem to implement scrollIntoView so we have to spy on focus() and stub scrollIntoView(). I’m happy to make changes if you have other ideas though :)
Test plan
https://user-images.githubusercontent.com/458591/213458273-19f33539-16bc-43e2-a0ac-d6180fd8b949.mov

@mellis481 given that the recreation scenario is likely one that is similar to our flagship product’s scenarios (ie large size of items) this seems to be a fix that we would also want to take advantage of. So can you bring in UIEN-3615 into our current support queue and get it assigned to literally anyone on our team? This is a good opportunity to share knowledge of this library with someone who hasn’t been made familiar yet. My expectation is that they fully understand the well described problem (thanks @philipp-spiess) and then evaluates if the test properly recreates that problem and accurately proves it is fixed. One way to do that is to remove the fix and see that the test fails. I would also expect them to verify that no external props/interfaces have changed without the author seeking prior approval.
thanks again @philipp-spiess for the contribution

@philipp-spiess Sorry for the delay in reviewing your PR. Can you please update your branch, resolving all conflicts, and we'll get this PR merged? Thanks!


Add @andreyvelich to kubeflow-ci members

I will help with maintaining common CI/CD infra.
/assign @jlewi

/lgtm
/approve


Correctly detect words when c-escapes are used

foo\nbar will look like foo and nbar without special handling.

Dup: #3


Integrate TALNet sound event classifier

Integrate Yun's best TALNet sound event classifier that can recognize 500+ categories (rather than just 17 or so)

Pointer to repository with this tool: https://github.com/srvk/537cls

Some more clarification on this might be in order; let me try to list tasks

some of this falls under the task to refactor all of: TALNet, Yunitator, Noisemes into one code base. I might benefit from some help from someone with better Python chops
write a Launcher script to call TALNet in the "DiViMe Way"
add TALNet to the Vagrantfile (for now this is the fastest way to get it into the VM, but will become obsolete as part of the first point)


Custom Domain for GitHub Pages: clarify what values to use for DNS records (ALIAS etc., CNAME)

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site
What part(s) of the article would you like to see updated?
Docs imply the Host value for CNAME records is www.example.com. For example "create a CNAME record that points www.example.com to <user>.github.io". But the correct Host value is www. Instead "create a CNAME record that points www to <user>.github.io." could be better (also notice the . I added after <user>.github.io).
Similarly "To create an ALIAS or ANAME record, point your apex domain to the default domain for your site." implies the Host value is the apex domain but actually the Host value should be @.
Additional information
The docs already recommend the user to check their DNS providers documentation for details on setting up DNS records. Since the specific Host values could differ from provider to provider.
However I think the docs could be better if the wrong Host values were not implied, either by stating the correct values inline or clearly showing the values of the DNS records, for example:

ALIAS record
value

Host
@

Target
<user>.github.io.

.

@alzafacon
Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:

We appreciate you taking the time to write up this issue and provide all the relative information. ✨
I’ve spoken with our team. We kept the language here fairly general since it is different for each provider. The ultimate goal is a CNAME that points www.example.com  at .github.io , so we will not be changing the documentation around it.
Thank you again for your passion in improving GitHub Docs! 💖


Make it compatible with package managers.

make it compatible with es6 modules / commonJs/ amd and other names that i don't what means but the cool js kids like them.

i'll [try this] https://stackoverflow.com/questions/37912857/exporting-a-class-with-webpack-and-babel-not-working

closed by #12


unused variables

An unused variable seems to exist for the _ execute function.

Description:
Couldn't unused variables affect readability?

@henjun ... while you're right and these variables are unused, for type safety reasons, TypeScript will not build with this change. I appreciate the effort, but I'm going to need to close this PR.
Thank you for your time, @henjun! I hope this doesn't put you off from contributing again!


does not work out of the box

When I clone your git and follow your instructions, I am getting a lot of errors, with just the default configuration. The only modification I have done is to adjust the NGINX location in the .env to "./" because I can't figure out where you are trying to have this point to. Maybe this is the problem? I don't have an NGINX installed because it wasn't a prerequisite of this docker.
Here is what I'm seeing:
# ./start.sh
Error response from daemon: network with name webproxy already exists
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16288  100 16288    0     0   171k      0 --:--:-- --:--:-- --:--:--  172k
Pulling nginx-web (nginx:latest)...
latest: Pulling from library/nginx
Digest: sha256:31b8e90a349d1fce7621f5a5a08e4fc519b634f7d3feb09d53fac9b12aa4d991
Status: Image is up to date for nginx:latest
Pulling nginx-gen (jwilder/docker-gen:latest)...
latest: Pulling from jwilder/docker-gen
Digest: sha256:f86c5374c3384b7de37c221e7fa450df357d2bf473db3eedd0375cf39288d9cc
Status: Image is up to date for jwilder/docker-gen:latest
Pulling nginx-letsencrypt (jrcs/letsencrypt-nginx-proxy-companion:latest)...
latest: Pulling from jrcs/letsencrypt-nginx-proxy-companion
Digest: sha256:3181bf5c683c647c4d53526706ca5bce56b37ff7d8c610bd70e194026d174a9a
Status: Image is up to date for jrcs/letsencrypt-nginx-proxy-companion:latest
Starting nginx-web ...
Starting nginx-gen ...
Starting nginx-web
Starting nginx-gen
Starting nginx-letsencrypt ...
Starting nginx-gen ... error

Starting nginx-letsencrypt ... error

Starting nginx-web ... error

ERROR: for nginx-web  Cannot start service nginx-web: Bind mount failed: '/volume1/docker/docker-compose-letsencrypt-nginx-proxy-companion/html' does not exists

ERROR: for nginx-web  Cannot start service nginx-web: Bind mount failed: '/volume1/docker/docker-compose-letsencrypt-nginx-proxy-companion/html' does not exists

ERROR: for nginx-gen  Cannot start service nginx-gen: Bind mount failed: '/volume1/docker/docker-compose-letsencrypt-nginx-proxy-companion/certs' does not exists

ERROR: for nginx-letsencrypt  Cannot start service nginx-letsencrypt: Bind mount failed: '/volume1/docker/docker-compose-letsencrypt-nginx-proxy-companion/certs' does not exists
ERROR: Encountered errors while bringing up the project.

Hello @thayneq,
Thanks for your message.
Could you paste your .env file?

it's exactly the same as the default, just with:
NGINX_FILES_PATH=./

@thayneq
I asked if you could post your .env not this line only...
but ok... try to set some other path to this variable such as:
NGINX_FILES_PATH=/home/user/webproxy

and try again...
The error as your logs says it binding your volume...
'/volume1/docker/docker-compose-letsencrypt-nginx-proxy-companion/html'

more errors.
`# ./start.sh
Error response from daemon: network with name webproxy already exists
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 16288  100 16288    0     0   174k      0 --:--:-- --:--:-- --:--:--  176k
Pulling nginx-web (nginx:latest)...
latest: Pulling from library/nginx
Digest: sha256:31b8e90a349d1fce7621f5a5a08e4fc519b634f7d3feb09d53fac9b12aa4d991
Status: Image is up to date for nginx:latest
Pulling nginx-gen (jwilder/docker-gen:latest)...
latest: Pulling from jwilder/docker-gen
Digest: sha256:f86c5374c3384b7de37c221e7fa450df357d2bf473db3eedd0375cf39288d9cc
Status: Image is up to date for jwilder/docker-gen:latest
Pulling nginx-letsencrypt (jrcs/letsencrypt-nginx-proxy-companion:latest)...
latest: Pulling from jrcs/letsencrypt-nginx-proxy-companion
Digest: sha256:3181bf5c683c647c4d53526706ca5bce56b37ff7d8c610bd70e194026d174a9a
Status: Image is up to date for jrcs/letsencrypt-nginx-proxy-companion:latest
Removing nginx-web
Removing nginx-gen
Removing nginx-letsencrypt
Recreating 189c6b8d89ab_nginx-gen ...
Recreating 1d48c84469e2_nginx-web ...
Recreating 1d48c84469e2_nginx-web
Recreating 189c6b8d89ab_nginx-gen
Recreating 473a18abd193_nginx-letsencrypt ...
Recreating 1d48c84469e2_nginx-web ... error
ERROR: for 1d48c84469e2_nginx-web  Cannot start service nginx-web: driver failed programming external connectivity on endpoint nginx-web (c3a17ec46b9478af833c21a06904ec1805f8e674be993493b5d8bc63309cRecreating 189c6b8d89ab_nginx-gen ... error
Recreating 473a18abd193_nginx-letsencrypt ... error
ERROR: for 473a18abd193_nginx-letsencrypt  Cannot start service nginx-letsencrypt: Bind mount failed: '/volume1/docker/blah/conf.d' does not exists
ERROR: for nginx-web  Cannot start service nginx-web: driver failed programming external connectivity on endpoint nginx-web (c3a17ec46b9478af833c21a06904ec1805f8e674be993493b5d8bc63309c7ac9): Bind for <IP_ADDRESS>:443 failed: port is already allocated
ERROR: for nginx-gen  Cannot start service nginx-gen: Bind mount failed: '/volume1/docker/blah/html' does not exists
ERROR: for nginx-letsencrypt  Cannot start service nginx-letsencrypt: Bind mount failed: '/volume1/docker/blah/conf.d' does not exists
ERROR: Encountered errors while bringing up the project.`

here is my .env as you requested:
`# cat .env

docker-compose-letsencrypt-nginx-proxy-companion

A Web Proxy using docker with NGINX and Let's Encrypt
Using the great community docker-gen, nginx-proxy and docker-letsencrypt-nginx-proxy-companion

This is the .env file to set up your webproxy enviornment

Your local containers NAME

NGINX_WEB=nginx-web
DOCKER_GEN=nginx-gen
LETS_ENCRYPT=nginx-letsencrypt

Set the IP address of the external access Interface

IP=<IP_ADDRESS>

Default Network

NETWORK=webproxy
If you want to customize the created network, use the following variable
#NETWORK_OPTIONS="--opt encrypted=true"

Service Network (Optional)

In case you decide to add a new network to your services containers you can set this
network as a SERVICE_NETWORK

[WARNING] This setting was built to use our start.sh script or in that special case
you could use the docker-composer with our multiple network option, as of:
docker-compose -f docker-compose-multiple-networks.yml up -d

#SERVICE_NETWORK=webservices
If you want to customize the created network, use the following variable
#SERVICE_NETWORK_OPTIONS="--opt encrypted=true"

NGINX file path

NGINX_FILES_PATH=/volume1/docker/blah

NGINX use special conf files

In case you want to add some special configuration to your NGINX Web Proxy you could
add your files to ./conf.d/ folder as of sample file 'uploadsize.conf'

[WARNING] This setting was built to use our start.sh.

[WARNING] Once you set this options to true all your files will be copied to data
folder (./data/conf.d). If you decide to remove this special configuration
you must delete your files from data folder ./data/conf.d.

#USE_NGINX_CONF_FILES=true

Docker Logging Config

This section offers two options max-size and max-file, which follow the docker documentation
as follow:

logging:
driver: "json-file"
options:
max-size: "200k"
max-file: "10"

#NGINX_WEB_LOG_DRIVER=json-file
#NGINX_WEB_LOG_MAX_SIZE=4m
#NGINX_WEB_LOG_MAX_FILE=10
#NGINX_GEN_LOG_DRIVER=json-file
#NGINX_GEN_LOG_MAX_SIZE=2m
#NGINX_GEN_LOG_MAX_FILE=10
#NGINX_LETSENCRYPT_LOG_DRIVER=json-file
#NGINX_LETSENCRYPT_LOG_MAX_SIZE=2m
#NGINX_LETSENCRYPT_LOG_MAX_FILE=10`

here is my .env:
# cat .env
#
# docker-compose-letsencrypt-nginx-proxy-companion
#
# A Web Proxy using docker with NGINX and Let's Encrypt
# Using the great community docker-gen, nginx-proxy and docker-letsencrypt-nginx-proxy-companion
#
# This is the .env file to set up your webproxy enviornment

#
# Your local containers NAME
#
NGINX_WEB=nginx-web
DOCKER_GEN=nginx-gen
LETS_ENCRYPT=nginx-letsencrypt

#
# Set the IP address of the external access Interface
#
IP=<IP_ADDRESS>

#
# Default Network
#
NETWORK=webproxy

# If you want to customize the created network, use the following variable
#NETWORK_OPTIONS="--opt encrypted=true"

#
# Service Network (Optional)
#
# In case you decide to add a new network to your services containers you can set this
# network as a SERVICE_NETWORK
#
# [WARNING] This setting was built to use our `start.sh` script or in that special case
#           you could use the docker-composer with our multiple network option, as of:
#           `docker-compose -f docker-compose-multiple-networks.yml up -d`
#
#SERVICE_NETWORK=webservices

# If you want to customize the created network, use the following variable
#SERVICE_NETWORK_OPTIONS="--opt encrypted=true"

#
# NGINX file path
#
NGINX_FILES_PATH=/volume1/docker/blah

#
# NGINX use special conf files
#
# In case you want to add some special configuration to your NGINX Web Proxy you could
# add your files to ./conf.d/ folder as of sample file 'uploadsize.conf'
#
# [WARNING] This setting was built to use our `start.sh`.
#
# [WARNING] Once you set this options to true all your files will be copied to data
#           folder (./data/conf.d). If you decide to remove this special configuration
#           you must delete your files from data folder ./data/conf.d.
#
#USE_NGINX_CONF_FILES=true

#
# Docker Logging Config
#
# This section offers two options max-size and max-file, which follow the docker documentation
# as follow:
#
# logging:
#      driver: "json-file"
#      options:
#        max-size: "200k"
#        max-file: "10"
#
#NGINX_WEB_LOG_DRIVER=json-file
#NGINX_WEB_LOG_MAX_SIZE=4m
#NGINX_WEB_LOG_MAX_FILE=10

#NGINX_GEN_LOG_DRIVER=json-file
#NGINX_GEN_LOG_MAX_SIZE=2m
#NGINX_GEN_LOG_MAX_FILE=10

#NGINX_LETSENCRYPT_LOG_DRIVER=json-file
#NGINX_LETSENCRYPT_LOG_MAX_SIZE=2m
#NGINX_LETSENCRYPT_LOG_MAX_FILE=10

I guess my question is, are you requiring that I have nginx installed at some other location? If so, why don't you include it in your compose? I do not have the USE_NGINX_CONF_FILES set, so I'm just confused why it's set up this way. Any help is appreciated.

nginx is not a requirement.
About the USE_NGINX_CONF_FILES you should use only if you want some special rules set for the nginx in the webproxy.

What do you have in this /volume1 ?
Please, once again, try to use your home dir where you are sure you have write access to it.

/volume1 is the default volume of the synology NAS that I'm using. I put all my docker projects in /volume1/docker. I am running as root and have write access. I'll try again with my home dir, which is in /volume1/homes/user/
I don't expect that to change the output, but here goes anyway:
Recreating 189c6b8d89ab_189c6b8d89ab_189c6b8d89ab_nginx-gen ... error

Recreating 473a18abd193_473a18abd193_473a18abd193_nginx-letsencrypt ... error

Recreating 1d48c84469e2_1d48c84469e2_1d48c84469e2_nginx-web ... error

ERROR: for 1d48c84469e2_1d48c84469e2_1d48c84469e2_nginx-web  Cannot start service nginx-web: Bind mount failed: '/volume1/homes/user/blah/htpasswd' does not exists

ERROR: for nginx-web  Cannot start service nginx-web: Bind mount failed: '/volume1/homes/user/blah/htpasswd' does not exists

ERROR: for nginx-gen  Cannot start service nginx-gen: Bind mount failed: '/volume1/homes/user/blah/certs' does not exists

ERROR: for nginx-letsencrypt  Cannot start service nginx-letsencrypt: Bind mount failed: '/volume1/homes/user/blah/html' does not exists
ERROR: Encountered errors while bringing up the project.

I do not have "ss" so this command does not work.

/volume1 is the root directory that is created when you make a filesystem with synology NAS. I don't want to share the output of this command because it lists a lot of private directories that don't apply to this problem. Is there something specific about /volume1 that you want to know?

# uname -a
Linux hughes 4.4.59+ #23824 SMP PREEMPT Fri Oct 12 18:31:48 CST 2018 x86_64 GNU/Linux synology_denverton_1618+

based on the errors, it appears start.sh is expecting some nginx files to appear in the NGINX_FILES_PATH, which is just an empty directory I created, so I'm not surprised this error is happening. Should I install nginx into this directory?

@thayneq
Once again you don´t need nginx installed in the host... please read some docker docs first.
You are trying to use docker in a synology nas... this is the issue you should look for...
Try to run a hello world container for the docker documentation and see if it works, the issue is not related to this script. You must be able to create and bind volumes, you might will need to add some required libs to you linux before you get through this.
Hope you can solve it.

I run a lot of dockers on synology, as do many other people. I suggest you look a bit closer before closing this issue. What makes you think this is related to synology? I am able to run the non-compose version of these packages just fine.

I disagree with you calling this invalid.

@thayneq
I did not mean to offend you or anything... sorry if you misunderstand my words.

ok. I guess I'll go look at https://github.com/buchdag/letsencrypt-nginx-proxy-companion-compose
thanks for trying!

I too am running on Synology, and I now have this running. It's been a while since I set it up on my production (Ubuntu) server but it seems like Synology does not work same way with rights - and does not created folder automatically.
Anyway my secret was to run the commands below to create the data directory and set the permissions correctly.
mkdir -p data/certs
mkdir data/htpasswd
mkdir data/conf.d
mkdir data/vhost.d
mkdir data/html
chgrp -R 101 data
chmod -R g+rwx data
Another issue I was facing was that Synology apparently insists on running a HTTP listener no matter what you enable but I have solved that by mapping external ports 80/443 to Synology 81/444 and made the script configureable. I'll create a PR once I have tested and documented this properly (in a few days I hope).

I had the same issue with the same error turned out that docker installs from snap causes this.
solved it by removing docker entirely and reinstalling it again.
https://stackoverflow.com/a/54492532/5641227


"Kotlin 1.5 has a breaking change to reflection" message

Description
I just restarted Teku 22.3.0 and saw the following message in the log.
2022-03-07 09:25:01.364 WARN  - Kotlin 1.5 has a breaking change to reflection - the OpenAPI plugin will not work properly. Please visit https://github.com/tipsy/javalin/issues/1193 if you want to help fix this issue.

We should fix something... either OpenAPI or the warning message.

this has been present since we upgraded to new javalin (6 months maybe?)
We can try to update again and see if we can get rid of it...

We have the latest version javalin with #5235 and looking at the original issue, it was not solved yet

Still present in Teku 22.5.2; seems like no prospect of it being fixed at the Javalin end. Is there nothing we can do to suppress this message?

we could probably suppress it, my understanding was it's just during startup?
Potentially we can change how swagger is used and remove the need for the dependency once the endpoints are all migrated...

We've migrated the rest APIs now. :tada:


SubNav.Links not available in TypeScript

👋 I'm getting an error trying to follow the example on https://primer.style/components/SubNav which includes a <SubNav.Links> element:

I'm using @primer/components version 19.1.1.

Thanks for the heads up! I'll fix this next week!

@emplums May I take this one?

whoops @pavelkeyzik just saw this! I just pushed up a PR to fix this, but thank you!

@emplums No worries 😄


ag fails to run if git is not installed

Line 442 of src/options.c (a popen of git) assumes the executable is available on every machine "ag" is run. Every invocation fails with a "sh: git: command not found" if the executable is not found on the user's path.

Is there a fix for this? You still can't use The Silver Searcher without Git in Ubuntu.

Maybe Ubuntu ships an old version of ag? The latest version definitely works without git.

So the issue should be closed?

The version in the debian repository runs even if git is not installed, but it prints "sh: 1: git: not found" to stderr.
To reproduce:

Create an ubuntu 14.04 VM, or find an ubuntu machine without git.
Run apt-get install silversearcher-ag
run echo "aaasssdddfff" > ./here
run ag aaasssdddfff

Yeah, this seems like an issue for Debian or Ubuntu packaging people. It's been two years nice it was fixed in ag.
Sorry I can't do anything else about this.


fix horizontal over position

fix over position in top and bottom titles

Please tell me more about it.

sorry just replied
i will give result about it
Before

After

in this case i need value highest and value lowest but if the value at first value or last value the titles verticals will over position like pic number one so i fixed
sorry my english is bad hope you undrastand

Can you give me your reproducible code?

sure,but i need time.


Fix/autosave

Coverage decreased (-0.4%) to 45.275% when pulling 9ce5f4b5e8e8bde06fb95f1acb15a64e1c9323c9 on fix/autosave into a712bb35905a4f91d42824ff55fbe6149f384a6b on master.

Coverage decreased (-0.4%) to 45.275% when pulling 9ce5f4b5e8e8bde06fb95f1acb15a64e1c9323c9 on fix/autosave into a712bb35905a4f91d42824ff55fbe6149f384a6b on master.


[ChatGPT] ...

Extension
https://www.raycast.com/abielzulio/chatgpt
Description

Error:
Error: Worker terminated due to reaching memory limit: JS heap out of memory

NodeError:errors:393:5
[kOnExit]:worker:277:26
Worker.<computed>.onexit:worker:199:20

Steps To Reproduce

Open the ChatGPT extension
Continue a conversation
Error appears.

Current Behaviour
No response
Expected Behaviour
No response

@raycastbot close this issue.
Closing this issue due to a future fix that will be available on the next update.


Demo page: drop down menu shows up at top of screen.

Chrome Version 60.0.3112.78 (Official Build) (64-bit)
-View AppNav in horizontal format
-Click on Assets
-Drop down shows up at the top of the screen under the grey bar
Screenshot:

Still trying to figure out exactly how to replicate it, but I keep seeing this:

Potentially related to the above issue

Still happening.


PALETTE TOWN

(maps.js line 82)
Palette is funnier, but not sure if you did it on purpose

http://bulbapedia.bulbagarden.net/wiki/Pallet_Town

Intentional typo I think.


TTL Mailbox queue

After discussions with @DenizPiri, it would be useful to have a mailbox, that measures how long a message have been in the mailbox, and removes messages where the TTL has expired
It could be implemented with a custom mailbox queue, which contains an envelope that has a timestamp.
when the mailbox pulls a message to push it into the actor, we check current time minus placed on mailbox time.
if this is greater than X timespan, we send the message to deadletter instead

What are the use cases for this functionality? I wonder if TTL mailbox covers them all.

what if the message was sent over the network and spent some time in transit - should this time be included?
what if the TTL should be measured as a total of all hops between multiple actors?
what if the TTL is not measured from the moment the message is posted to the mailbox, but rather some event in the outside world (e.g. moment when a device posted the message)?
what if the TTLed messages should go to alternative processing path instead of deadletter?

I think the users have a lot of flexibility currently to implement these scenarios with receive middleware.

@rogeralsing @DenizPiri any input on the above questions?

@marcinbudny I agree that the TTL mailbox wouldn't cover all the scenarios. Especially the ones you mentioned.
As for our use cases, we don't have any inter-actor communication. We usually have centric singleton actors we send requests to as a result of the client requests. So, currently, in our case, if the actor stalls for a while on a single message, let's say 10 secs, the client request side gets timed out; however, the actor has no awareness of this and continues to process the queued-up messages, which causes more lagging for the new client requests and causes those to time-out as well.
You are right, this is doable with a receive middleware. But, a simpler set-and-forget solution would be a lot more ideal I believe.
I think the core problem I am having is that actors have no built-in good mechanisms to deal with back-pressure and throttling. Our needs for a back-pressure solution are super simple, but I believe there would be clients there that would have much more complicated needs (as @marcinbudny laid out, messages hopping between multiple actors, all being a part of a single soon-to-be-timed-out request).
Maybe we can rename the title to "Mailbox Backpressure Brainstorming" and discuss more generic solutions.


ts strict part 5: misc 1

Please see https://github.com/keybase/client/pull/18383 for an overview

@keybase/react-hackers this is ready


🐛 Bug Report: Permission client throws an ZodError if "anyOf" used.

📜 Description
We are trying to use playlist plugin in our backstage environment where we enabled the permissions. We are passing the ServerPermissionClient to playlist backend as required and getting the policy rules described as in repository:
https://github.com/backstage/backstage/tree/master/plugins/playlist-backend
We are getting an error:

Click to expand error
[
{
  "code": "invalid_union",
  "unionErrors": [
    {
      "issues": [
        {
          "code": "invalid_union",
          "unionErrors": [
            {
              "issues": [
                {
                  "code": "invalid_literal",
                  "expected": "ALLOW",
                  "path": [
                    "items",
                    0,
                    "result"
                  ],
                  "message": "Invalid literal value, expected 'ALLOW'"
                }
              ],
              "name": "ZodError"
            },
            {
              "issues": [
                {
                  "code": "invalid_literal",
                  "expected": "DENY",
                  "path": [
                    "items",
                    0,
                    "result"
                  ],
                  "message": "Invalid literal value, expected 'DENY'"
                }
              ],
              "name": "ZodError"
            }
          ],
          "path": [
            "items",
            0,
            "result"
          ],
          "message": "Invalid input"
        }
      ],
      "name": "ZodError"
    },
    {
      "issues": [
        {
          "code": "invalid_union",
          "unionErrors": [
            {
              "issues": [
                {
                  "code": "invalid_union",
                  "unionErrors": [
                    {
                      "issues": [
                        {
                          "code": "invalid_union",
                          "unionErrors": [
                            {
                              "issues": [
                                {
                                  "code": "invalid_type",
                                  "expected": "string",
                                  "received": "undefined",
                                  "path": [
                                    "items",
                                    0,
                                    "conditions",
                                    "rule"
                                  ],
                                  "message": "Required"
                                },
                                {
                                  "code": "invalid_type",
                                  "expected": "string",
                                  "received": "undefined",
                                  "path": [
                                    "items",
                                    0,
                                    "conditions",
                                    "resourceType"
                                  ],
                                  "message": "Required"
                                },
                                {
                                  "code": "invalid_type",
                                  "expected": "object",
                                  "received": "undefined",
                                  "path": [
                                    "items",
                                    0,
                                    "conditions",
                                    "params"
                                  ],
                                  "message": "Required"
                                }
                              ],
                              "name": "ZodError"
                            },
                            {
                              "issues": [
                                {
                                  "code": "invalid_union",
                                  "unionErrors": [
                                    {
                                      "issues": [
                                        {
                                          "code": "invalid_union",
                                          "unionErrors": [
                                            {
                                              "issues": [
                                                {
                                                  "code": "invalid_union",
                                                  "unionErrors": [
                                                    {
                                                      "issues": [
                                                        {
                                                          "code": "invalid_type",
                                                          "expected": "object",
                                                          "received": "undefined",
                                                          "path": [
                                                            "items",
                                                            0,
                                                            "conditions",
                                                            "anyOf",
                                                            1,
                                                            "params"
                                                          ],
                                                          "message": "Required"
                                                        }
                                                      ],
                                                      "name": "ZodError"
                                                    },
                                                    {
                                                      "issues": [
                                                        {
                                                          "code": "invalid_type",
                                                          "expected": "array",
                                                          "received": "undefined",
                                                          "path": [
                                                            "items",
                                                            0,
                                                            "conditions",
                                                            "anyOf",
                                                            1,
                                                            "anyOf"
                                                          ],
                                                          "message": "Required"
                                                        }
                                                      ],
                                                      "name": "ZodError"
                                                    }
                                                  ],
                                                  "path": [
                                                    "items",
                                                    0,
                                                    "conditions",
                                                    "anyOf",
                                                    1
                                                  ],
                                                  "message": "Invalid input"
                                                }
                                              ],
                                              "name": "ZodError"
                                            },
                                            {
                                              "issues": [
                                                {
                                                  "code": "invalid_type",
                                                  "expected": "array",
                                                  "received": "undefined",
                                                  "path": [
                                                    "items",
                                                    0,
                                                    "conditions",
                                                    "anyOf",
                                                    1,
                                                    "allOf"
                                                  ],
                                                  "message": "Required"
                                                }
                                              ],
                                              "name": "ZodError"
                                            }
                                          ],
                                          "path": [
                                            "items",
                                            0,
                                            "conditions",
                                            "anyOf",
                                            1
                                          ],
                                          "message": "Invalid input"
                                        }
                                      ],
                                      "name": "ZodError"
                                    },
                                    {
                                      "issues": [
                                        {
                                          "code": "invalid_union",
                                          "unionErrors": [
                                            {
                                              "issues": [
                                                {
                                                  "code": "invalid_union",
                                                  "unionErrors": [
                                                    {
                                                      "issues": [
                                                        {
                                                          "code": "invalid_union",
                                                          "unionErrors": [
                                                            {
                                                              "issues": [
                                                                {
                                                                  "code": "invalid_type",
                                                                  "expected": "object",
                                                                  "received": "undefined",
                                                                  "path": [
                                                                    "items",
                                                                    0,
                                                                    "conditions",
                                                                    "anyOf",
                                                                    1,
                                                                    "not"
                                                                  ],
                                                                  "message": "Required"
                                                                }
                                                              ],
                                                              "name": "ZodError"
                                                            },
                                                            {
                                                              "issues": [
                                                                {
                                                                  "code": "invalid_type",
                                                                  "expected": "object",
                                                                  "received": "undefined",
                                                                  "path": [
                                                                    "items",
                                                                    0,
                                                                    "conditions",
                                                                    "anyOf",
                                                                    1,
                                                                    "not"
                                                                  ],
                                                                  "message": "Required"
                                                                }
                                                              ],
                                                              "name": "ZodError"
                                                            }
                                                          ],
                                                          "path": [
                                                            "items",
                                                            0,
                                                            "conditions",
                                                            "anyOf",
                                                            1,
                                                            "not"
                                                          ],
                                                          "message": "Invalid input"
                                                        }
                                                      ],
                                                      "name": "ZodError"
                                                    },
                                                    {
                                                      "issues": [
                                                        {
                                                          "code": "invalid_type",
                                                          "expected": "object",
                                                          "received": "undefined",
                                                          "path": [
                                                            "items",
                                                            0,
                                                            "conditions",
                                                            "anyOf",
                                                            1,
                                                            "not"
                                                          ],
                                                          "message": "Required"
                                                        }
                                                      ],
                                                      "name": "ZodError"
                                                    }
                                                  ],
                                                  "path": [
                                                    "items",
                                                    0,
                                                    "conditions",
                                                    "anyOf",
                                                    1,
                                                    "not"
                                                  ],
                                                  "message": "Invalid input"
                                                }
                                              ],
                                              "name": "ZodError"
                                            },
                                            {
                                              "issues": [
                                                {
                                                  "code": "invalid_type",
                                                  "expected": "object",
                                                  "received": "undefined",
                                                  "path": [
                                                    "items",
                                                    0,
                                                    "conditions",
                                                    "anyOf",
                                                    1,
                                                    "not"
                                                  ],
                                                  "message": "Required"
                                                }
                                              ],
                                              "name": "ZodError"
                                            }
                                          ],
                                          "path": [
                                            "items",
                                            0,
                                            "conditions",
                                            "anyOf",
                                            1,
                                            "not"
                                          ],
                                          "message": "Invalid input"
                                        }
                                      ],
                                      "name": "ZodError"
                                    }
                                  ],
                                  "path": [
                                    "items",
                                    0,
                                    "conditions",
                                    "anyOf",
                                    1
                                  ],
                                  "message": "Invalid input"
                                }
                              ],
                              "name": "ZodError"
                            }
                          ],
                          "path": [
                            "items",
                            0,
                            "conditions"
                          ],
                          "message": "Invalid input"
                        }
                      ],
                      "name": "ZodError"
                    },
                    {
                      "issues": [
                        {
                          "code": "invalid_type",
                          "expected": "array",
                          "received": "undefined",
                          "path": [
                            "items",
                            0,
                            "conditions",
                            "allOf"
                          ],
                          "message": "Required"
                        }
                      ],
                      "name": "ZodError"
                    }
                  ],
                  "path": [
                    "items",
                    0,
                    "conditions"
                  ],
                  "message": "Invalid input"
                }
              ],
              "name": "ZodError"
            },
            {
              "issues": [
                {
                  "code": "invalid_union",
                  "unionErrors": [
                    {
                      "issues": [
                        {
                          "code": "invalid_union",
                          "unionErrors": [
                            {
                              "issues": [
                                {
                                  "code": "invalid_union",
                                  "unionErrors": [
                                    {
                                      "issues": [
                                        {
                                          "code": "invalid_type",
                                          "expected": "object",
                                          "received": "undefined",
                                          "path": [
                                            "items",
                                            0,
                                            "conditions",
                                            "not"
                                          ],
                                          "message": "Required"
                                        }
                                      ],
                                      "name": "ZodError"
                                    },
                                    {
                                      "issues": [
                                        {
                                          "code": "invalid_type",
                                          "expected": "object",
                                          "received": "undefined",
                                          "path": [
                                            "items",
                                            0,
                                            "conditions",
                                            "not"
                                          ],
                                          "message": "Required"
                                        }
                                      ],
                                      "name": "ZodError"
                                    }
                                  ],
                                  "path": [
                                    "items",
                                    0,
                                    "conditions",
                                    "not"
                                  ],
                                  "message": "Invalid input"
                                }
                              ],
                              "name": "ZodError"
                            },
                            {
                              "issues": [
                                {
                                  "code": "invalid_type",
                                  "expected": "object",
                                  "received": "undefined",
                                  "path": [
                                    "items",
                                    0,
                                    "conditions",
                                    "not"
                                  ],
                                  "message": "Required"
                                }
                              ],
                              "name": "ZodError"
                            }
                          ],
                          "path": [
                            "items",
                            0,
                            "conditions",
                            "not"
                          ],
                          "message": "Invalid input"
                        }
                      ],
                      "name": "ZodError"
                    },
                    {
                      "issues": [
                        {
                          "code": "invalid_type",
                          "expected": "object",
                          "received": "undefined",
                          "path": [
                            "items",
                            0,
                            "conditions",
                            "not"
                          ],
                          "message": "Required"
                        }
                      ],
                      "name": "ZodError"
                    }
                  ],
                  "path": [
                    "items",
                    0,
                    "conditions",
                    "not"
                  ],
                  "message": "Invalid input"
                }
              ],
              "name": "ZodError"
            }
          ],
          "path": [
            "items",
            0,
            "conditions"
          ],
          "message": "Invalid input"
        }
      ],
      "name": "ZodError"
    }
  ],
  "path": [
    "items",
    0
  ],
  "message": "Invalid input"
}
]"

👍 Expected behavior
The permission client should not throw a validation error if a conditional statement is returned.
👎 Actual Behavior with Screenshots
Permission client throws a validation. (ZodError)
👟 Reproduction steps

Integrate playlist plugin (be and fe)
Enable permissions and pass permission client to playlist
Go to Playlist page
You will get a validation error (ZodError)

📃 Provide the context for the Bug.
We can not enable playlist plugin with using the permission framework.
The following code paths are important to analyse:
I think we need to extend this permission schema where nothing about "any" defined, see below why it is important.
https://github.com/backstage/backstage/blob/master/plugins/permission-common/src/PermissionClient.ts#L58
Playlist plugin defines a policy with anyOf:
https://github.com/backstage/backstage/blob/master/plugins/playlist-backend/src/permissions/DefaultPlaylistPermissionPolicy.ts#L70
but permission client does not have any kind of definition about anyOf If I follow the permission-common package correctly.
🖥 Your Environment
OS:   Darwin 22.1.0 - darwin/x64
node: v14.19.0
yarn: 3.2.3
cli:  0.20.0 (installed)
backstage:  1.7.2
Dependencies:
@backstage/app-defaults                               1.0.7
@backstage/backend-app-api                            0.2.2
@backstage/backend-common                             0.15.2
@backstage/backend-plugin-api                         0.1.3
@backstage/backend-tasks                              0.3.6
@backstage/backend-test-utils                         0.1.29
@backstage/catalog-client                             1.1.1
@backstage/catalog-model                              1.1.2
@backstage/cli-common                                 0.1.10
@backstage/cli                                        0.20.0
@backstage/config-loader                              1.1.5
@backstage/config                                     1.0.3
@backstage/core-app-api                               1.1.1
@backstage/core-components                            0.11.2
@backstage/core-plugin-api                            1.0.7
@backstage/dev-utils                                  1.0.7
@backstage/errors                                     1.1.2
@backstage/integration-react                          1.1.5
@backstage/integration                                1.3.2
@backstage/plugin-api-docs                            0.8.10
@backstage/plugin-auth-backend                        0.17.0
@backstage/plugin-auth-node                           0.2.6
@backstage/plugin-badges-backend                      0.1.31
@backstage/plugin-badges                              0.2.34
@backstage/plugin-bazaar-backend                      0.2.0
@backstage/plugin-bazaar                              0.1.25
@backstage/plugin-catalog-backend-module-github       0.1.8
@backstage/plugin-catalog-backend                     1.5.0
@backstage/plugin-catalog-common                      1.0.7
@backstage/plugin-catalog-graph                       0.2.22
@backstage/plugin-catalog-import                      0.9.0
@backstage/plugin-catalog-node                        1.2.0
@backstage/plugin-catalog-react                       1.2.0
@backstage/plugin-catalog                             1.6.0
@backstage/plugin-code-coverage                       0.2.3
@backstage/plugin-explore-react                       0.0.22
@backstage/plugin-explore                             0.3.41
@backstage/plugin-github-actions                      0.5.10
@backstage/plugin-github-deployments                  0.1.41
@backstage/plugin-github-pull-requests-board          0.1.4
@backstage/plugin-graphiql                            0.2.42
@backstage/plugin-home                                0.4.26
@backstage/plugin-jenkins-backend                     0.1.27
@backstage/plugin-jenkins-common                      0.1.9
@backstage/plugin-jenkins                             0.7.9
@backstage/plugin-kafka                               0.3.10
@backstage/plugin-lighthouse                          0.3.10
@backstage/plugin-org                                 0.5.10
@backstage/plugin-permission-backend                  0.5.12
@backstage/plugin-permission-common                   0.6.4, 0.7.0
@backstage/plugin-permission-node                     0.7.0
@backstage/plugin-permission-react                    0.4.6
@backstage/plugin-playlist-backend                    0.2.0
@backstage/plugin-playlist-common                     0.1.1
@backstage/plugin-playlist                            0.1.1
@backstage/plugin-proxy-backend                       0.2.31
@backstage/plugin-scaffolder-backend                  1.7.0
@backstage/plugin-scaffolder-common                   1.2.1
@backstage/plugin-scaffolder                          1.7.0
@backstage/plugin-search-backend-module-elasticsearch 1.0.3
@backstage/plugin-search-backend-node                 1.0.3
@backstage/plugin-search-backend                      1.1.0
@backstage/plugin-search-common                       0.3.4, 1.1.0
@backstage/plugin-search-react                        1.2.0
@backstage/plugin-search                              1.0.3
@backstage/plugin-shortcuts                           0.3.2
@backstage/plugin-sonarqube-backend                   0.1.2
@backstage/plugin-sonarqube                           0.4.2
@backstage/plugin-stack-overflow                      0.1.6
@backstage/plugin-tech-radar                          0.5.17
@backstage/plugin-techdocs-backend                    1.4.0
@backstage/plugin-techdocs-module-addons-contrib      1.0.5
@backstage/plugin-techdocs-node                       1.4.1
@backstage/plugin-techdocs-react                      1.0.5
@backstage/plugin-techdocs                            1.3.3
@backstage/plugin-user-settings-backend               0.1.1
@backstage/plugin-user-settings                       0.5.0
@backstage/release-manifests                          0.0.6
@backstage/search-common                              0.3.4
@backstage/test-utils                                 1.2.1
@backstage/theme                                      0.2.16
@backstage/types                                      1.0.0
@backstage/version-bridge                             1.0.1
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

I did a quick test by adding:
    z.any(z.object({
      result: z.literal(AuthorizeResult.CONDITIONAL),
      pluginId: z.string(),
      resourceType: z.string(),
      conditions: permissionCriteriaSchema,
    })),

to queryPermissionResponseSchema in PermissionClient and I don't get any validation error.

Hi @nodify-at, I believe this was fixed in https://github.com/backstage/backstage/pull/14236 which should go out with v1.8 of Backstage expected to be released tomorrow

@kuangp I'm afraid, it will not fix this issue. I can do a quick test by patching this class provided by you and re-run the application. I think this problem is related to the schema definition at : queryPermissionResponseSchema in https://github.com/backstage/backstage/blob/master/plugins/permission-common/src/PermissionClient.ts#L58
Here it expects an object with result etc. But https://github.com/backstage/backstage/blob/master/plugins/playlist-backend/src/permissions/DefaultPlaylistPermissionPolicy.ts#L70 this decision returns an object with anyOf which is invalid.

@nodify-at the createPlaylistConditionalDecision creates this conditional decision with the result as AuthorizeResult.CONDITIONAL, which you can see in the test here. anyOf is a valid condition, similar to allOf (and these can be infinitely nested).
I'll also take a closer look at this in a little bit, but by looking at the error above my initial hunch is that @kuangp is right and that it's the same issue and should be resolved with the new release.

Also mentioning that the release was published just now.

Thanks for your help :) Let me try with the latest version but I think they're different validation error. I will send the results here in 15 min :)

I can confirm it fixes this error and I can explore the playlists if permission framework is enabled. Thanks for your help and support! I will check the code to understand the permission schema better :)


Arrow down not a function..

This is my setup ..  Typing and searching works. But clicking on the button-down arrow gives me :

TypeError: $(...).parent(...).find(...).inputpicker is not a function

function doTokenSetup(){  $('#tokener2').inputpicker({  placeholder: 'Choose..', url: 'example-districts.json', fields: ['id', 'name', 'hasc'] , fieldText: 'name', fieldValue: 'id', filterOpen: true, selectMode: 'creatable', multiple: true, headShow: true }); }

Also .. when using the above setup it looks like some CSS styling is missing. e.g. the border around the input text field is gone. So its hard to see where you can start typing.

Hi @Designburo ,
I am unable to reproduce the issue according to the desc. Can you please provide more details about the issue? It would be great if you could upload your source code to https://jsfiddle.net/ . Thanks a lot.


fix: merge frame url and frame url fragment for getting full url

This Pr :

Retrieve full url by adding url fragment to url when trying to call url function from a frame.

@googlebot I signed it!

@googlebot I fixed it.

@googlebot I fixed it.

Thanks for the patch. Two requests:

In the commit message, please explain what problem this is fixing.
Please add a test

Thanks for the patch. Two requests:

In the commit message, please explain what problem this is fixing.
Please add a test

Done 😄

@mjzffr FYI, the CI has been unhappy lately, with Firefox launch failing. Does this ring any bells?

Ah, this is still #5673. Will post there


Beam Search

Is there anything in place supporting this yet? Wanted to ask before I implement my own.

I'd probably encourage you to write a C++-based beam search instead of trying to do it with graph ops.  That said, we will likely provide some sort of specialized self-contained beam search for CTC with the CTC loss.  Additionally there's a PriorityQueue in the works which, when completed, will provide the ability to sort groups of Tensors.  Not sure if this would help you.  Another good project to look at for implementing a beam search is OpenFST, which was coincidentally partly developed within Google Research :)

so what's the verdict? I am using the python API now, should I do it in python?
i.e. is beam-search even possible in the graph ops, if it's not possible then clearly there's no option, but if it is possible is the issue of being inefficient or more difficult to implement than its worth?

@evanthebouncy, see #654

Marking this as a duplicate of #654  cause it seems like that's what you want to do.

@ebrevdo Can you provide a pointer to how to do beam search using the C++ API?

Do you mean CTC beam search specifically?

@ebrevdo I'd like to see an example of a CTC beam search

I've frozen a model that has as last node ctc beam search. Now I want to use this .pb file in C++ but I don't know exactly how to process the output tensor in order to get the final sequence of labels. Anyone with previous experience in this kind of issue?


chore: update viem bench

Updating Viem's benchmarks. Removed Viem from the summary to avoid underemphasising the improvements in performance to the Thirdweb SDK.

PR-Codex overview
This PR updates viem to version 2.8.14, improving encode transfer benchmark performance significantly.
Detailed summary

Updated viem to version 2.8.14
Improved encode transfer benchmark performance
Updated @babel/core to version 7.24.1

The following files were skipped due to too many changes: pnpm-lock.yaml

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Thanks, will take a look tonight or tomorrow. I think we'll have to update some things to make the latest viem version work outside of benchmarks.

@jxom I did some more perf work and incorporated these updates as part of #2520 - the new pattern in viem is still a bit faster than what we can hit for pure encode, I kept it in the benchmarks all the same (showing viem is faster in pure encode performance)

Cool! Could use prepareEncodeFunctionData in your prepare utils? I kind of nerd sniped myself to add that into Viem this morning. Open to feedback if there’s something missing there.

Cool! Could use prepareEncodeFunctionData in your prepare utils? I kind of nerd sniped myself to add that into Viem this morning. Open to feedback if there’s something missing there.

possible, I haven't looked to deep yet but at initial glance it basically does the same thing as what I did in my prepareMethod call, there's a couple of small differences but yeah likely I can align it

@jxom closing this since benchmarks are updated already - I'm going to start looking into removing some of the hand-written stuff that now exists in viem and will provide u feedback on those if I run into things separately
as always, appreciate the work you do and the discussions we have!


IDS: API 'settings/get' response incomplete

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
I am currently working on implementing the IDS API as Ansible modules.
The issue I'm running into is:
In all other API endpoints the get (api/ids/settings/get) returns the data of all sub-endpoints. This is very useful as external integrations need this information for linking config-objects.
To Reproduce
Steps to reproduce the behavior:

Log-in on your Firewall
Open https://<YOUR-FW>/api/ids/settings/get
Open https://<YOUR-FW>/api/monit/settings/get
Compare the responses

Expected behavior
Examples:

As expected - monit
Response:
{"monit": {
  "general": {...},
  "alert": {...},
  "service": {...},
  "test": {...}
}}

IDS
{"ids": {
  "general": {...}
}}

IDS expected
{"ids": {
  "general": {...},
  "rules": {...},
  "policies": {...},
  "userDefinedRules": {...},
  "files": {...},
  "fileTags": {...}
}}

Describe alternatives you considered
I am aware that one COULD implement it the same way the WebUI does.
Example:

Call searchPolicy to get a list of UUIDs
Call getPolicy FOR EACH ITEM to get the details (maybe even in async)

But this can get time-intensive as every HTTP request takes a few hundred MS. This may not sound like much, but it does not scale well.
Also: In my opinion an API should share the same behavior between endpoints.
Environment
OPNsense 23.7.10_1-amd64
FreeBSD 13.2-RELEASE-p7
OpenSSL 1.1.1w
Common KVM processor (6 cores, 6 threads) [PVE]
8GB RAM

It's more likely other get()  actions return less content in the future as these actions are intended to be used for the non nested items. Returning all for a form offering only a selection of data is far from optimal, which is why https://github.com/opnsense/core/issues/4123 exists.
When trying to build ACL's for partial applications returning all content on get() is also a (minor) security concern, although these situations currently don't exist (and should safeguard the setter as well).  We could consider adding an endpoint specifically for integration purposes at some point.

@AdSchellevis Thank you for the quick response and important information.
It might be good if it would be mentioned in the documentation when such API-endpoints are known-to-be-deprecated. This would save a lot of time and work for projects that implement your APIs (:
Specific endpoints for 'external' integrations might make sense - at least for pulling all entries of one kind.
As the search + get combination is very UI-specific.
Example:

api/ids/settings/searchPolicy
{
 "rows": [
     {
         "uuid": "1d587b04-ebcb-41bd-9a19-e144c88b679e",
         "enabled": "1",
         "prio": "0",
         "description": "test1"
     },
     {
         "uuid": "e1cdc774-053f-4236-9835-929a001ea1ff",
         "enabled": "1",
         "prio": "0",
         "description": ""
     }
 ],
 "rowCount": 2,
 "total": 2,
 "current": 1
}

api/ids/settings/getPolicy/<UUID>
{
 "policy": {
     "enabled": "1",
     "prio": "0",
     "action": {
         "disable": {
             "value": "Disabled",
             "selected": 0
         },
         "alert": {
             "value": "Alert",
             "selected": 0
         },
         "drop": {
             "value": "Drop",
             "selected": 0
         }
     },
     "rulesets": {
         "01cb5c91-14e7-4e9d-898f-ca96fa9f3aee": {
             "value": "drop.rules",
             "selected": 0
         }
     },
     "content": {
         "affected_product.Any": {
             "value": "Any",
             "selected": 0
         },
         "attack_target.Any": {
             "value": "Any",
             "selected": 0
         },
         "classtype.misc-attack": {
             "value": "misc-attack",
             "selected": 0
         },
         "deployment.Perimeter": {
             "value": "Perimeter",
             "selected": 0
         },
         "signature_severity.Minor": {
             "value": "Minor",
             "selected": 0
         },
         "tag.Dshield": {
             "value": "Dshield",
             "selected": 0
         }
     },
     "new_action": {
         "default": {
             "value": "Default",
             "selected": 0
         },
         "alert": {
             "value": "Alert",
             "selected": 1
         },
         "drop": {
             "value": "Drop",
             "selected": 0
         },
         "disable": {
             "value": "Disable",
             "selected": 0
         }
     },
     "description": "test1"
 }
}

This totally makes sense for the UI - as the row-view only needs very limited information and the 'detail' view needs them all.
But if you want/need to get the details of all entries - one needs perform loads of API-calls.

@ansibleguy  Well, the endpoints are not being deprecated at all, but contents may change (as with all api's in all products). The intend of this specific endpoint might have been misunderstood, which I can understand, but realistically this issue isn't really solvable  from the documentation. Often our ticket system helps in finding some longer standing issues which are not pressing, but we expect to change at some point.
Please keep in mind our API's are developed for our ui in the first place, by making sure these endpoints are actively being used we also automatically increase test coverage, which is more problematic for specific endpoints. Our general rule of thumb is to prevent adding endpoints without consumers on our end as issues on these can not be replicated from the ui.
As the code behind all of this is quite consistent, I don't mind adding one endpoint in the base class which does expose the "raw" model (which is what get() is currently doing), we should just think of a proper name to avoid more confusion.
If your product actively uses the current get in multiple places, it might make sense to implement this new endpoint first and postpone changing the getters on our end for a bit longer to ease the transition on your end. There's no real rush in implementing https://github.com/opnsense/core/issues/4123, but it is very likely new components don't automatically include all data when get is being called.

@AdSchellevis Thank you for the response.
Deprecated may be the wrong word. But I would think such a major change of the response of an API endpoint should be transparent as it might break existing integrations.
I understand.
The current implementation of my 'product' uses the get endpoint for most modules - yes.
I would appreciate it, if there would be another endpoint that could be used.
I get the point that access to the raw model might not be the cleanest approach .
In my opinion it would also be enough to enable the getX endpoints to list all existing entries. (by making the UUID optional?)
Example:

query one: api/ids/settings/getPolicy/<UUID>
query all: api/ids/settings/getPolicy/ or  api/ids/settings/getPolicyAll/

Just brainstorming - I'm not sure what design would make more sense.

The "context aware" ones will be difficult to implement in a generic way other than what's already available, in most cases you can just use the implemented getItem() and searchItem().  The search actions (as GET) without parameters will already return all available items for that section by the way, which is more or less the same as your example above.
When seeking a way to fetch all items from a model (with possibly more containers inside), the current get usually works, but has a high risk of future breakage. That's something we can solve at some point as the pattern doesn't need any context.

The only problem I got with the GET searchX endpoint, is that they do only return few attributes of an item.
That totally makes sense if they are rendered in an UI, but if an external tool needs/wants the full information of all items, many consecutive GET getX calls need to be performed.
Just wanted to inform you that this is not optimal from an 'outside perspective'.
I can make it work either way with some 'workarounds' on the client-side.. (;
Could you tell me when it's planned that the get endpoints are changed? (https://github.com/opnsense/core/issues/4123)
Just so I can plan the migration.

nothing is planned yet, so we do have time to look for alternatives which works for both. Maybe it's also an option to change the default behavior of the searchBase() action to return all fields when none is specified and change the callers. In most cases it's not problematic to return all fields per record as the set itself is limited anyway.

@ansibleguy returning all fields for a search endpoint is likely easy to change for most of them, as they use searchBase(). I've changed the IDS ones so you can easily try this on your end as well, you need https://github.com/opnsense/core/commit/2d45b78f744059089078d56b3c108765b2d23608 and https://github.com/opnsense/core/commit/fb2a9b839159333f3b9b918310c93dfa144b673f, next you can query all policies using:
https://x.x.x.x/api/ids/settings/searchPolicy
To install using opnsense-patch, use:
opnsense-patch 2d45b78 fb2a9b8

If this helps you out, I don't mind changing the endpoints in core to return all fields available.

Thank you - I'll try it out 👍🏼

Sorry for the delay..
Your patch looks promising.
If it's that easy to implement this on your side, in my opinion - it would make sense to implement it. This could immensely simplify the API usage for external integrations.
For the record:
Before:
{"rows":[{"uuid":"978afa0f-6491-421a-bc6a-d709611d1552","enabled":"1","prio":"2","description":"ANSIBLE_TEST_1_1"}],"rowCount":1,"total":1,"current":1}
After applying 8855fd8:
{"rows":[{"uuid":"978afa0f-6491-421a-bc6a-d709611d1552","enabled":"1","prio":"2","action":"Alert,Drop","rulesets":"drop.rules","content":"Minor,Dshield","new_action":"Alert","description":"ANSIBLE_TEST_1_1"}],"rowCount":1,"total":1,"current":1}
The only drawback I could think of, is that each client will have to fetch & process (a little) more data on the OPNSense WebUI table views. This could be noticeable if the table entry-count is set to a few hundred. I tested it with searchinstalledrules and noticed a little more lag. (mainly JS)

This should be in 24.1.6 already. Close?

@ansibleguy in some cases returning all might not be the best idea, but in most cases the extra fields don't matter that much. Let's assess this per case, if you miss data on a controller, just open a ticket for us to remove the static field choices.
@fichtner let's close indeed.


TypeError: t is not a constructor

I'm getting a TypeError when adding the plugin to the extraPlugins array of the editor. I'm using the ckeditor5 react package with a custom build. I was able to install the puff-puff package and write the plugin just like in the example. When putting it all together the plugin is unable to load.
import { CKEditor } from '@ckeditor/ckeditor5-react';
import Editor from 'ckeditor5-custom-build/build/ckeditor';
import { CloudinaryUnsigned } from 'puff-puff/CKEditor';

const imagePluginFactory = (editor) => {
    editor.plugins.get('FileRepository').createUploadAdapter = (loader) => new CloudinaryUnsigned(loader, 'xxxx', 'xxxx', [160, 500, 1000, 1052]);
};

const config = {
    extraPlugins: [imagePluginFactory],
    toolbar: ['heading', '|', 'bold', 'italic', 'underline', 'blockquote', 'link', '|', 'alignment:left', 'alignment:center', 'alignment:right', 'alignment:justify', '|', 'imageupload', 'mediaembed', '|', 'bulletedList', 'numberedList', '|', 'undo', 'redo'],
};

const TextEditor = () => {
    const [text, setText] = useState('');

    return (

            <CKEditor
                editor={Editor}
                config={config}
                data={text}
                onChange={(event, editor) => {
                    const data = editor.getData();
                    setText(data);
                }}
                onError={(error) => {
                    console.log(error);
                }}
            />

{text}

    );
};

Hi @AnthonyMagnus,
I am sorry I am responding to your issue a bit late, I missed the notification. Is this still an issue that requires addressing? If it is, are you using TypeScript for this project?

I changed the code from the config object to the editor object and now it's working.
I'm using Javascript.
Code:
<CKEditor
    editor={Editor}
    config={config}
    data={text}
    onChange={(event, editor) => {
        const data = editor.getData();
        setText(data);
    }}
    onError={(error) => {
        console.log(error);
    }}
    onReady={(editor) => {
        editor.plugins.get('FileRepository').createUploadAdapter = (loader) => new CloudinaryUnsigned(loader, 'xxxx', 'xxxx');
    }}
/>


Toggling search viewlet is showing different search results

Not different results - one has an exclude. But this is because they don't share state. https://github.com/Microsoft/vscode/issues/44491

@roblourens But if you see the gif, search viewlet in side bar is showing inconsistent results

I think they share some model object but not the view. Probably related but I'll leave it open.

I don't really know of an issue here besides what #44491 covers


load minimum of classes from app classloader

Only load the classes needed for reflection, seems to basically equate to the various classes that we might reference directly in the reflection code around contract execution, as that could lead to weird mismatches between the reference in code and the object being worked on that is loaded from the MemoryClassLoader (i.e. inspecting an annotation on a class/function or casting a function result to a Message)
Seems to allow the los validation contracts using an external Validator object to work properly

Codecov Report

Merging #43 (ce29390) into main (7f95979) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #43   +/-   ##
=========================================
  Coverage     80.00%   80.00%
  Complexity      137      137
=========================================
  Files            19       19
  Lines          1110     1110
  Branches        123      123
=========================================
  Hits            888      888
  Misses          157      157
  Partials         65       65

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 7f95979...ce29390. Read the comment docs.


KAFKA-10056; Ensure consumer metadata contains new topics on subscription change

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@hachikuji Thanks for the review, merging to trunk and older branches where KAFKA-9181 was applied.


Add the wallet kit to the top bar

This is needed for the CLI (#674) and it's common for web3 ux

This prioritize to unblocked https://github.com/stellar/stellar-cli/issues/674

Wallet Kit Designs


Release and tags

Working with dev-master is complicated and dangerous.
@kasperbasse  You can create a tag or release? Even a pre-release helps a lot.

:+1:

:+1:

@kasperbasse ?

Hello, i will try to take a look at that, i am not strongest in git yet.  ;)
But thank you for the tip @vinicius73. :)

Hi @vinicius73
I have now created a new release with version number:
"kbwebs/multiauth": "~1.0", is it like you want it to be :)

thanks!


nixos/documentation: silence man-db cache warnings

Motivation for this change
Fix issue #100288
Things done

[x] Tested via programs.fish.enable in a NixOS VM
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

20.09 backport: ba06414bd7c


fix: changed php into<EMAIL_ADDRESS>

After the release of php 8.0<EMAIL_ADDRESS>needs to be defined otherwise it won't be installed.
And if installed wil give an port already in use error.

@wimvdputten Haha, je ticket was<EMAIL_ADDRESS>(correct), maar de code had php7.4 (incorrect). Inmiddels aangepast


Progress bar and current % of download (useful for big files)

Any tips on how to use progress bar or % for the download (very useful for big files)?

Created PR https://github.com/kevva/download/pull/228 which addresses the current issue

For big files, it may be useful to use a progress bar. You must install also module progress.
const download = require('download')
const ProgressBar = require('progress')

const writeStream = fs.createWriteStream('http://unicorn.com/foo.zip')
const readStream = download('dist/foo.zip')
readStream.on('response', function (res) {
  const len = parseInt(res.headers['content-length'], 10)
  const bar = new ProgressBar('  downloading [:bar] :rate/bps :percent :etas', {
    complete: '=',
    incomplete: ' ',
    width: 20,
    total: len
  })
  readStream.on('data', function (chunk) {
    writeStream.write(chunk)
    bar.tick(chunk.length)
  })
  readStream.on('end', function () {
    console.log('Download done with success\n')
    writeStream.end()
  })
})

For big files, it may be useful to use a progress bar. You must install also module progress.
const download = require('download')
const ProgressBar = require('progress')

const writeStream = fs.createWriteStream('http://unicorn.com/foo.zip')
const readStream = download('dist/foo.zip')
readStream.on('response', function (res) {
  const len = parseInt(res.headers['content-length'], 10)
  const bar = new ProgressBar('  downloading [:bar] :rate/bps :percent :etas', {
    complete: '=',
    incomplete: ' ',
    width: 20,
    total: len
  })
  readStream.on('data', function (chunk) {
    writeStream.write(chunk)
    bar.tick(chunk.length)
  })
  readStream.on('end', function () {
    console.log('Download done with success\n')
    writeStream.end()
  })
})

Isn't the create write stream to be the download path while the first parameter in the download function is the URL?

No, it might seem strange but I am almost sure the code is correct, I tested myself.

I had to switch it to work fine tho .


training for classification does not converge

I tried to train the classification models for alexnet and inception, with the hyperparameters in train.py (    'learning_rate_decay_type': 'exponential', 'learning_rate': '0.01', 'learning_rate_decay_factor': '0.1'), but the loss fluctuates around 6 and 11 respectively for the two models. I tried to tune the learning rate in the range from 1e-5 to 0.1, but the training still shows no sign of convergence (even after 10,000 steps). Could you inform me of the hyperparameters chosen for the training of the classification models in order to reproduce the results, and the final values of the cross-entropy loss?

Thanks! The loss did drop down to around 2 after 5 epochs of training.


[SPARK-6618][SQL] HiveMetastoreCatalog.lookupRelation should use fine-grained lock

JIRA: https://issues.apache.org/jira/browse/SPARK-6618

Test build #29443 has started for   PR 5281 at commit b3a9625.

Test build #29443 has finished for   PR 5281 at commit b3a9625.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29443/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29447/
Test FAILed.

test this please

Test build #29454 has started for   PR 5281 at commit 591b4be.

Test build #29454 has finished for   PR 5281 at commit 591b4be.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29454/
Test PASSed.

LGTM. Merging to master and 1.3.


Training

Hi,
I have some general question regarding training the module:

Can I train the module in GPU ?If yes, what will be the procedure ?

Can I train a new data-set along with your pre trained module or I have to train the module with all the data-set again ?

Can This module can be run at Nvidia Jetson embedded devices?? What will be the performance ?

Yes it can. See Tensorflow GPU Guide. You probably want to Upgrade to Tensorflow 2.1.0 to get better performance out of the GPU (since Tensorflow 2.0.0 the optimized Nvidia implementation is used automatically).

Yes, you can. Use the tool provided in #79 to create the keras model from the c sources. Modify rnn_train.py to load the trained model.

Probably not. You need a lot of RAM and because of the deep backpropagation caused by a big sequence size, CPU tend to outperform small graphic cards on this task.

@Zadagu This is the Specification of Nvidia Jetson Nano:
GPU | 128-core Maxwell
CPU | Quad-core ARM A57 @ 1.43 GHz
Memory | 4 GB 64-bit LPDDR4 25.6 GB/s
How much ram needed to inference the module ??

@Zadagu I want to train the module which is trained with various noises i want to add some datasets and i want to keep the previous one also is that possible?

After some modification of the training script my PC consumes about 20GB of RAM during training. If you use the script as it is, you will need around 35GB.

Training will be done in other environment. I want to implement the library for my application to work with Nvidia Jetson Devices.

RNNoise is very lightweight in execution. But you should note, that the RNNoise Binary doesn't use GPU acceleration at all. See the RNNoise paper for complexity analysis https://jmvalin.ca/papers/rnnoise_mmsp2018.pdf

@Zadagu
Thanks for the information.

@Zadagu There are two files with same name as "rnn_train.py". One is ithe src directory another is in training directory. Which one to be replaced with keras code? Can youb help me with this ??

RNNoise is very lightweight in execution

It's not. Max complexity Opus encoding is 2-3 times faster on arm, and I've seen the core load dangerously close to 100% on low-end Android phones because of that, not to mention the battery impact. I'd love to see it optimized, at this point I'm even considering to land the existing trained network on some highly efficient C/C++ NN framework to see if I can make it run faster

RNNoise is very lightweight in execution
I should make this more clear.
I meant that the RNNoise Algorithm is in comparison to other NN based denoising algortithms lightweight in computational complexity during execution.


How can i show 2 images per slide?

You can try to set up it in default.js on node module

You can supply a custom _renderItem-function and design your slides just as you see fit. Remember that the slides-prop takes an array of any types of object.


Refacto and Manage the Auto complation

This pull request does...
Why ?
it manage the auto completion to help user when adding news ratings
How ?
while user type value he becomes suggestion on Company names, cities and job title
** Screenshots (optional)
https://user-images.githubusercontent.com/49993443/156038971-68d1ea0e-cce7-44c3-ac51-c9642552ab83.mp4

if the PR got merged, @Asam237  should work on css part

For some reason the Comments section on this page became smaller than it was before.

I fixed it here #150


Fix json.load() in client.request

Fixes #3

I adopted this fix to work with both 2.7/3, so closing the PR. Also added an example API request (examples/schedules.py) for easier integration testing.
Much obliged for the bug reports and contributions!


Vue3 + Typescript source map is not the original SFC's one

Version
3.2.26
Reproduction link
vue3-ts-source-map
Steps to reproduce
$ vue -V
    @vue/cli 4.5.15
$ vue create vue3-ts-source-map
    ? Please pick a preset: Default (Vue 3) ([Vue 3] babel, eslint)
$ cd vue3-ts-source-map
$ vue add typescript
    ? Use class-style component syntax? Yes
    ? Use Babel alongside TypeScript (required for modern mode, auto-detected polyfills, transpiling JSX)? Yes
    ? Use TSLint? Yes
    ? Pick lint features: Lint on save
    ? Convert all .js files to .ts? Yes
    ? Allow .js files to be compiled? No
    ? Skip type checking of all declaration files (recommended for apps)? Yes
$ echo "module.exports = {
  configureWebpack() {
    return {
      devtool: 'source-map'
    };
  }
};" > vue.config.js
$ npm install
$ npm run serve

What is expected?
Chrome devtool -> Sources -> webpack://./src/App.vue shows original SFC sourcode like
<template>
  <img alt="Vue logo" src="./assets/logo.png">
  <HelloWorld msg="Welcome to Your Vue.js + TypeScript App"/>
</template>

<script lang="ts">
import { Options, Vue } from 'vue-class-component';
import HelloWorld from './components/HelloWorld.vue';

@Options({
  components: {
    HelloWorld,
  },
})
export default class App extends Vue {}
</script>

<style>
#app {
  font-family: Avenir, Helvetica, Arial, sans-serif;
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale;
  text-align: center;
  color: #2c3e50;
  margin-top: 60px;
}
</style>

What is actually happening?
App.vue shows some of source codes related to <script> only
import { Options, Vue } from 'vue-class-component';
import HelloWorld from './components/HelloWorld.vue';

@Options({
  components: {
    HelloWorld,
  },
})
export default class App extends Vue {}

I would say it's expected behavior, where and why do you need this?

I want to see the original SFC style source code in the Chrome devtool to debug with it. Just like when it working without typescript.
I'm really confusing this issue will be fixed or not.
In https://github.com/vuejs/vue-cli/issues/2978, there no more progress to solve this kind of issue but,
one of the blog posts, he got the original source code what I expected(but not able to debug without additional source map settings).
And the latest version of vue-cli shows the same result with https://github.com/vuejs/vue-cli/issues/2978 again.

It seems about vue-cli, I tried it by vite that all is well.🤷

Okay,
It is just expected behavior at least in vue-next project.
vue-cli may handle kind of source map things. But, not sure cause it is a different project, right?
Thank you for answer!


docs: update manifest with current solution properties

Description
There has been some changes since we first discussed a couple of properties in the manifest file.
"is_full_stack" is now "install_type" and has a value of "extension" or "fullstack".
Also the property "product_kind" with a value of "solution" (which denotes a deployable architecture) was added.
This is step 1 and the barest minimum changes needed for the manifest file.
The catalog milestone that delivers on April 4th uses the above properties and more.
Types of changes in this PR
No release required

[ ] Examples or tests (addition or updates of examples or tests)
[ x] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[ ] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[ ] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content
Replace this text with information that users need to know about the bug fixes, features, and breaking changes. This information helps the merger write the commit message that is published in the release notes for the module.

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

:tada: This PR is included in version 3.1.0 :tada:
The release is available on:

GitHub release
v3.1.0

Your semantic-release bot :package::rocket:


Not generating code correctly? bootscaf (0.1.7)

Hello there - your Gem looks awesome, perfect for something I just whipped up using scaffolds. I am not sure if it is something unique to my setup, or if I have done something stupid, or if this is a bug.. but the generated content repeats for about 400+ lines in the views, and doesn't look like the generated code is valid. Something could be horribly wrong in my setup as I get:
uninitialized constant Bootscaf::VERSION when I run 'bootscaf version'.
Any ideas?
Thanks!
(Below is the generated code)
<% unless @s.any? %>

No s created yet.

<% end %>
<% @s.each do || %>

<% unless @s.any? %>

No s created yet.

<% end %>
<% @s.each do || %>

<% unless @s.any? %>

No s created yet.

<% end %>
<% @s.each do || %>

<% unless @s.any? %>

No s created yet.

<% end %>

How did you run it?  E.g. bootscaf update foobars ?

bootscaf update foobars and also bootscaf update --all
Both produced the same results.
On Sun, Apr 12, 2015 at 11:15 PM, Matthew Moore<EMAIL_ADDRESS>wrote:

How did you run it? E.g. bootscaf update foobars ?
—
Reply to this email directly or view it on GitHub
https://github.com/thrivesmart/bootscaf/issues/1#issuecomment-92057992.

Hrm, I can't duplicate.  What OS are you on?  Bootscaf uses sed, so performance may vary across different flavors...

I am running Arch linux, sed definitely installed, however, I feel like this could be a systemic issue with the asset pipeline in my environment: I've attempted to create a new bare bones app with just a single scaffold, and this still fails. Do you have an example with just a single scaffold created that I ciould checkout and then test this theory?

Hm, I'm running on Mac, not Linux, which may result in my differences.  Are you willing to run a raw sed  command from the cli.rb to see what you get?  Maybe the one on this line? https://github.com/thrivesmart/bootscaf/blob/master/lib/bootscaf/cli.rb#L63

That seemed to work fine:

<%= yield :page_title %>Bootscaf
On Thu, Apr 16, 2015 at 11:27 PM, Matthew Moore<EMAIL_ADDRESS>wrote:

Hm, I'm running on Mac, not Linux, which may result in my differences. Are
you willing to run a raw sed command from the cli.rb to see what you get?
Maybe the one on this line?
https://github.com/thrivesmart/bootscaf/blob/master/lib/bootscaf/cli.rb#L63
—
Reply to this email directly or view it on GitHub
https://github.com/thrivesmart/bootscaf/issues/1#issuecomment-93733717.

Closing because of the age of this issue.  Feel free to re-open on a newer version of the gem.


Governance

Possible sub-topics:

Consensus building vs voting
How do you make decisions in a distributed, asynchronous way?
How does everyone get heard?
Code of conduct: Adoption and enforcement. For example, NumFOCUS code of conduct.

Happened 2022-09-22 1:30 pm


AndroidRuntime 	at libNatML.NMLModelPredict(NMLModelPredict:296)

I have upgraded Natml,Nathub and Natdevice as your advice.
I changed only the deprecated commands and didn't modify the rest, but what was working fine is now not working with an error.
It works on Windows, but on Android I get an error like below.
logcat_android_error.txt

I upgraded Natdevice, Nathub and Natml as your advice.
I only changed the deprecated instructions and didn't modify the rest, but what was working fine is now not working with an error.
It works on Windows and gives the error below on Android, I haven't checked IOS yet.
My code
`
void Start(){
var query = new MediaDeviceQuery(MediaDeviceCriteria.FrontCamera);
cameraDevice = query.current as CameraDevice
cameraDevice.StartRunning(previewTextureOutput);
model = await MLEdgeModel.Create("@natsuite/movenet");
predictor = new MoveNetPredictor(model, smoothing);
}
private void Update(){
var previewTexture = previewTextureOutput.texture;
var inputFeature = new MLImageFeature(previewTexture.GetRawTextureData(), previewTexture.width, previewTexture.height);
(inputFeature.mean, inputFeature.std) = model.normalization;
// Detect
var pose = predictor.Predict(inputFeature);
// Visualize
visualizer.Render(previewTexture, pose);
}
`

I even verified that it works on IOS.
Error occurs on only android.

@acttoz can you share the full, unfiltered logs from app start to crash? Feel free to DM it to me on Discord if there is private info you would like to protect.

This should be fixed in NatML 1.1.2.


adding cupti_wrapper error solution

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Create Posts “music-monday-the-voidz-dare-i-care-live-on-le-gran-journal-french-tv”

Automatically generated by Netlify CMS

👷 Deploy Preview for benevolent-muffin-215770 processing.

Name
Link

🔨 Latest commit
383ddbc2ff36f82bce37cdcc86ece19c376ec4a6

🔍 Latest deploy log
https://app.netlify.com/sites/benevolent-muffin-215770/deploys/62842ab560aacb000851554f