Unbounded memory usage

Category

[X] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[X] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[X] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[X] bash
[ ] zsh
[ ] fish

fzf vesion 0.13.5
not using tmux
fzf process ran interminably and memory consumption increased to 8GB and continued to rise until FZF find killed by user.  The command I ran was vim ~/** <tab>
The results are shown in these screenshots
![at 2016-09-08 14 11 58]  - fzf is consuming 3.9GB out of 20GB of ram (https://cloud.githubusercontent.com/assets/1812219/18367423/ddd9aaf2-75cf-11e6-822e-17fa5d781928.png)
![at 2016-09-08 14 12 52] - fzf memory consumption keeps growing.(https://cloud.githubusercontent.com/assets/1812219/18367463/1e324d8e-75d0-11e6-8215-fa402b440c4f.png)
![2016-09-08 14 14 03] - had to <ctrl-c>  out of fzf because it was never ending & memory consumption increased without bound.(https://cloud.githubusercontent.com/assets/1812219/18367502/55977b00-75d0-11e6-82f8-6b3e14895a60.png)
I think it has to do with the -L passed to find. It is going into a circular reference.

Hi, can you provide the steps to reproduce the problem? I couldn't reproduce with the following script.
mkdir -p /tmp/foo/bar
touch /tmp/foo/bar/baz
ln -s /tmp/foo /tmp/foo/bar/foo

vim /tmp/foo/** <tab>

The output of find -L
ind: File system loop detected; ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5/i2c-dev/i2c-5/subsystem/i2c-1/device/subsystem/devices/i2c-5’ is part of the same file system loop as ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5’.
find: File system loop detected; ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5/i2c-dev/i2c-5/subsystem/i2c-1/subsystem’ is part of the same file system loop as ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5/i2c-dev/i2c-5/subsystem’.
find: File system loop detected; ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5/i2c-dev/i2c-5/subsystem/i2c-2/device/i2c-dev/i2c-2’ is part of the same file system loop as ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5/i2c-dev/i2c-5/subsystem/i2c-2’.
find: File system loop detected; ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5/i2c-dev/i2c-5/subsystem/i2c-2/device/device’ is part of the same file system loop as ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0’.
find: File system loop detected; ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5/i2c-dev/i2c-5/subsystem/i2c-2/device/subsystem/devices/i2c-0/i2c-dev/i2c-0/device’ is part of the same file system loop as ‘/home/jojo/PlayOnLinux's virtual drives/pdfTracker/dosdevices/z:/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/device:00/PNP0800:00/physical_node/subsystem/devices/i8042/serio0/input/input3/event3/subsystem/event10/device/device/device/subsystem/devices/0000:00:02.0/drm/card0/card0-DP-1/subsystem/card0-DP-2/i2c-5/i2c-dev/i2c-5/subsystem/i2c-2/device/subsystem/devices/i2c-0’.

continues forever ... and it feeds it to fzf. So the error isn't in fzf it's in find.

Here's the first 412kB of output. I let it run for a few seconds and I had about 140M of text output. The issue is this program PlayOnLinux that makes find -L go into an infinite loop.

You can customize the command used to workaround the issue. See: https://github.com/junegunn/fzf#settings
I'm not sure about removing -L from the default command though, I personally like/need the option. Is there any way to avoid the issue without removing -L?

https://github.com/junegunn/fzf/commit/11407bf65650ef5bd97453e16ab3424b90ef750e
I think this problem should be fixed now as we updated the default command to prune sysfs entries which are showing in your case.

I encountered this today on latest versions on a 64GB memory M4 Max it brought down the machine to its knees @junegunn are you sure it has been resolved?


Request: Roman Numerals for Months?

I have always used Roman numerals for months. e.g. today 8.VI.2022. This has the advantage of making it easy to distinguish June 8 from August 6 - 8.6.2022 vs. 6.8.2022. Different places reverse the order (e.g. Europe|United States). Any chance using Roman numerals for months could be added to the options?
Many thanks.
Best,
Richard

Hi,
I'm afraid this is not easily possible at the moment.
The plugin is not doing the pattern matching itself, but is using the moment.js library which is shipped with the Obsidian installation by default.
And roman numerals are unfortunately currently not included in the formatting options of the library.
You can find here a full set of formatting options that are supported


generate-dashboards-configmap.sh has wrong line spacing and doesn't set id to null

What did you do?
I used ./hack/scripts/generate-dashboards-configmap.sh to add my own dashboards to the default
What did you expect to see?
Dashboards
What did you see instead? Under which circumstances?
No dashboards in grafana but they are in the grafana watcher.
Environment
bare-metal

Kubernetes version information:

root@master01:~# kubectl version
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.2+coreos.0", GitCommit:"4c0769e81ab01f47eec6f34d7f1bb80873ae5c2b", GitTreeState:"clean", BuildDate:"2017-10-25T16:24:46Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.2+coreos.0", GitCommit:"4c0769e81ab01f47eec6f34d7f1bb80873ae5c2b", GitTreeState:"clean", BuildDate:"2017-10-25T16:24:46Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

Kube-spray
The dashboards have made it to the watcher
/var/grafana-dashboards-0 # ls
deployment-dashboard.json                       kubernetes-cluster-status-dashboard.json        pods-dashboard.json                             traefik-dashboard.json
etcd-dashboard.json                             kubernetes-control-plane-status-dashboard.json  prometheus-dashboard.json
kubernetes-capacity-planning-dashboard.json     kubernetes-resource-requests-dashboard.json     prometheus-datasource.json
kubernetes-cluster-health-dashboard.json        nodes-dashboard.json                            stateful-dashboard.json

watcher logs
Get http://admin:admin@localhost:3000/api/datasources: dial tcp <IP_ADDRESS>:3000: getsockopt: connection refused
Get http://admin:admin@localhost:3000/api/datasources: dial tcp <IP_ADDRESS>:3000: getsockopt: connection refused
Get http://admin:admin@localhost:3000/api/datasources: dial tcp <IP_ADDRESS>:3000: getsockopt: connection refused
Get http://admin:admin@localhost:3000/api/datasources: dial tcp <IP_ADDRESS>:3000: getsockopt: connection refused
2017/11/27 03:21:46 Initializing datasources.
2017/11/27 03:21:46 Retrieving existing datasources
2017/11/27 03:21:47 Deleting 0 datasources
2017/11/27 03:21:47 Creating datasource from: /var/grafana-dashboards-0/prometheus-datasource.json
2017/11/27 03:21:48 Initializing dashboards.
2017/11/27 03:21:48 Retrieving existing dashboards
2017/11/27 03:21:50 Deleting 0 dashboards
2017/11/27 03:21:50 Creating dashboard from: /var/grafana-dashboards-0/deployment-dashboard.json
2017/11/27 03:21:51 Creating dashboard from: /var/grafana-dashboards-0/etcd-dashboard.json
2017/11/27 03:21:53 Creating dashboard from: /var/grafana-dashboards-0/kubernetes-capacity-planning-dashboard.json
2017/11/27 03:21:55 Creating dashboard from: /var/grafana-dashboards-0/kubernetes-cluster-health-dashboard.json
2017/11/27 03:21:56 Creating dashboard from: /var/grafana-dashboards-0/kubernetes-cluster-status-dashboard.json
2017/11/27 03:21:57 Creating dashboard from: /var/grafana-dashboards-0/kubernetes-control-plane-status-dashboard.json
2017/11/27 03:21:58 Creating dashboard from: /var/grafana-dashboards-0/kubernetes-resource-requests-dashboard.json
2017/11/27 03:21:59 Creating dashboard from: /var/grafana-dashboards-0/nodes-dashboard.json
2017/11/27 03:22:00 Creating dashboard from: /var/grafana-dashboards-0/pods-dashboard.json
2017/11/27 03:22:01 Creating dashboard from: /var/grafana-dashboards-0/prometheus-dashboard.json
2017/11/27 03:22:03 Creating dashboard from: /var/grafana-dashboards-0/stateful-dashboard.json
2017/11/27 03:22:06 Creating dashboard from: /var/grafana-dashboards-0/traefik-dashboard.json
2017/11/27 03:22:07 Starting...

 I didn't see any in sublime.
same errors in logs after making all my dashboards version 0.
attached the generated dashboard configmap
artifacts.zip

Using the default configmap it works fine, so it's something to do with my configmap. Not sure what yet.

So I removed all dashboards but the deployments dashboard. Reran the generation script and uploaded that. The dashboard doesn't appear in grafana.

Waiting for pod shared-services/runner-ef257594-project-4730159-concurrent-02v5n6 to be running, status is Pending
Waiting for pod shared-services/runner-ef257594-project-4730159-concurrent-02v5n6 to be running, status is Pending
Running on runner-ef257594-project-4730159-concurrent-02v5n6 via gitlab-runner-gitlab-runner-67847bc69d-v29wk...
Cloning repository...
Cloning into '/shadycuz_k8_repos/kubeprometheus'...
Checking out 3eb2efd3 as testing...
Skipping Git submodules setup
$ bash ./hack/scripts/generate-dashboards-configmap.sh > manifests/grafana/grafana-dashboards.yaml
Uploading artifacts...
manifests/grafana/grafana-dashboards.yaml: found 1 matching files
Uploading artifacts to coordinator... ok            id=42083834 responseStatus=201 Created token=6k5pGpwQ
Job succeeded

deploying kube_prometheus
Running with gitlab-ci-multi-runner 9.5.0 (413da38)
  on gitlab-runner-gitlab-runner-67847bc69d-v29wk (ef257594)
Using Kubernetes namespace: shared-services
Using Kubernetes executor with image registry.gitlab.com/shadycuz_k8_repos/kubernetes_deployer/gitlab_runner:latest ...
Waiting for pod shared-services/runner-ef257594-project-4730159-concurrent-04l4c9 to be running, status is Pending
Waiting for pod shared-services/runner-ef257594-project-4730159-concurrent-04l4c9 to be running, status is Pending
Waiting for pod shared-services/runner-ef257594-project-4730159-concurrent-04l4c9 to be running, status is Pending
Running on runner-ef257594-project-4730159-concurrent-04l4c9 via gitlab-runner-gitlab-runner-67847bc69d-v29wk...
Cloning repository...
Cloning into '/shadycuz_k8_repos/kubeprometheus'...
Checking out 3eb2efd3 as testing...
Skipping Git submodules setup
Downloading artifacts for Build Dashboards (42083834)...
Downloading artifacts from coordinator... ok        id=42083834 responseStatus=200 OK token=6k5pGpwQ
$ sed -i "s/MY_ENVIRONMENT/.${CI_ENVIRONMENT_SLUG}./g" manifests/k8s/devops/ingress.yaml
$ git grep -l "namespace" | xargs sed -i "s/namespace: monitoring/namespace: $NAMESPACE/g" || true
sed: can't read docs/Monitoring: No such file or directory
sed: can't read external: No such file or directory
sed: can't read etcd.md: No such file or directory
$ git grep -l "monitoring" | xargs sed -i "s/- monitoring$/- $NAMESPACE/g" || true
sed: can't read docs/Monitoring: No such file or directory
sed: can't read external: No such file or directory
sed: can't read etcd.md: No such file or directory
$ bash ./hack/cluster-monitoring/deploy || true
Error from server (AlreadyExists): namespaces "review-testing-7r9j96" already exists
clusterrolebinding "prometheus-operator" configured
clusterrole "prometheus-operator" configured
serviceaccount "prometheus-operator" unchanged
service "prometheus-operator" unchanged
deployment "prometheus-operator" unchanged
Waiting for Operator to register custom resource definitions...done!
daemonset "node-exporter" unchanged
service "node-exporter" unchanged
clusterrolebinding "kube-state-metrics" configured
clusterrole "kube-state-metrics" configured
deployment "kube-state-metrics" unchanged
rolebinding "kube-state-metrics" unchanged
role "kube-state-metrics-resizer" unchanged
serviceaccount "kube-state-metrics" unchanged
service "kube-state-metrics" unchanged
secret "grafana-credentials" unchanged
secret "grafana-credentials" unchanged
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
configmap "grafana-dashboards-0" configured
deployment "grafana" unchanged
service "grafana" unchanged
servicemonitor "node-exporter" configured
configmap "prometheus-k8s-rules" unchanged
secret "basic-auth" unchanged
servicemonitor "traefik" configured
service "prometheus-k8s" unchanged
servicemonitor "kube-state-metrics" configured
prometheus "k8s" configured
servicemonitor "kube-controller-manager" configured
serviceaccount "prometheus-k8s" unchanged
servicemonitor "etcd-k8s" configured
servicemonitor "prometheus-operator" configured
servicemonitor "prometheus" configured
servicemonitor "kube-apiserver" configured
servicemonitor "alertmanager" configured
servicemonitor "kube-scheduler" configured
servicemonitor "kubelet" configured
role "prometheus-k8s" unchanged
role "prometheus-k8s" unchanged
role "prometheus-k8s" unchanged
clusterrole "prometheus-k8s" configured
rolebinding "prometheus-k8s" unchanged
rolebinding "prometheus-k8s" unchanged
rolebinding "prometheus-k8s" unchanged
clusterrolebinding "prometheus-k8s" configured
secret "alertmanager-main" unchanged
service "alertmanager-main" unchanged
alertmanager "main" configured
$ kubectl delete -f manifests/grafana/grafana-dashboards.yaml -n ${NAMESPACE} || true
configmap "grafana-dashboards-0" deleted
$ kubectl create -f manifests/grafana/grafana-dashboards.yaml -n ${NAMESPACE} || true
configmap "grafana-dashboards-0" created
$ kubectl apply -f manifests/k8s/devops/kube-etcd.yaml -n ${NAMESPACE}
service "etcd-k8s" unchanged
endpoints "etcd-k8s" configured
$ kubectl apply -f manifests/k8s/devops/ingress.yaml -n ${NAMESPACE}
ingress "grafana" unchanged
ingress "prometheus" unchanged
ingress "alertmanager" unchanged
Job succeeded

dashboard config file
artifacts (2).zip

Think the problem is here
{
  "dashboard":
  {
  "annotations": {
    "list": []
  },

should be
{
	"dashboard": {
		"annotations": {
			"list": []
		},

After fixing the wrapper.sh to fix the spacing, dashboards still did not work. I had to add a sed command to set "id": null, to get the dashboards to work.

Hey sorry I was out sick yesterday. Your last comment sounds like you fixed the issue, can you elaborate?

@brancz I hope you feel better. I will submit a PR, I just wanted to check to make sure it didn't break your python dashboards first. Also I noticed Kube-prometheus is only really suited for the monitoring namespace. I see a check in the deploy script for a namespace but most of the manifests have namespace: monitoring hardcoded in which means you can't deploy it into another namespace. Are you interested in a PR for that as well? I'm basically just using sed -i on certain files to fix it for me.
git grep -l "namespace" | xargs sed -i "s/namespace: monitoring/namespace: $NAMESPACE/g"
git grep -l "monitoring" | xargs sed -i "s/- monitoring$/- $NAMESPACE/g"

My last issue I'm having is if I deploy kube-prometheus in 2 seperate namespaces the second kube-prometheus deployment wont create any node-exporter dameonsets but I haven't looked into it.

I'm happy if you want to open a PR for all of the above! (bear in mind that the scripts are in a hack/ folder though). The idea is that helm is gonna help with some of that stuff, but I'm happy to have it in the hack scripts as well.

I feel like kube_prometheus needs it's own helm chart that deploys everything or a bash script that deploys each helm chart you guys are currently working on in /helm. As long as the helm chart deals with

Funny you mentioned helm and I was typing that comment ^ before you did.

@shadycuz  thanks for your solution. i was trying to import dashboard and i got this issue. set id to null and it worked


Nat with verified eq data type

This works with my Liquid Haskell pull request https://github.com/ucsd-progsys/liquidhaskell/pull/836 (to be merged soon.)

Of course tests fail, @vikraman can I link the tests to a Liquid Haskell commit?

Yes, you could change LIQUID_SHA in the Dockerfile to 5acfe16.

I tried it out locally and everything works. Thanks for fixing this!

No problem!
BTW, implementation-wise is there anything else that I should fix/edit in Liquid Haskell?

With this fix, we can put VerifiedEq (with laws) and instances in the same module, but we still need things to work across modules. But that's not a blocker right now.


New engine : Lux, you-get, wget and aria2, and  N_m3u8DL-CLI

Hello, thank you very much fot this awesome and fantastic amzing downloader 🥇 💯 !
i have suggestion please : it will be even more great if there is integration with ths famous CLI software because yt-dlp may suffer from censorship like youtube-dl on github when youtube- dl was removed from github after a dmca complaint.....
You-Get
Dumb downloader that scrapes the web
You-Getis a tiny command-line utility to download media contents (videos, audios, images) from the Web, in case there is no other handy way to do it.
https://github.com/soimort/you-get
Lux is a fast and simple video downloader built with Go
Fast and simple video download library and CLI tool written in Go
https://github.com/iawia002/lux
N_m3u8DL-CLI to dowload m3u8 streams
https://github.com/nilaoda/N_m3u8DL-CLI
aria2c is used primarily to download regular large files from the internet.
https://aria2.github.io/
wget download regular large files from the internet.
https://www.gnu.org/software/wget/

Thanks for your compliment. :)
Making it simple, convenient, and practical is an indicator.
So any suggestions and recommendations are welcome.
The current version already supports the use of aria2.
As for other projects, I don't know how to use it and its features.
I will actively integrate if it works. :)

Great ! thank you very much !!
i find also an amazing CLI command line software to donwload m3u8 streams N_m3u8DL-CLI , i  know it is very difficult and complicated to integrate these all new comand line softwares  and it is suggestion and thak you again to offer us this amzign  downloader, and  yt-dlp ia already enogh strong to download video from many and many websites :)
https://github.com/nilaoda/N_m3u8DL-CLI

Thank you for your expectations and suggestions
For now, yt-dlp-gui is to make people use the powerful tool yt-dlp better.
To make perfect use of yt-dlp, There's still a long way.
It is quite difficult to be a downloader that can download all videos.
In contrast, making GUI for good software will be simpler.
If have a chance, Does not exclude making GUI for other software

Yes, you have right 💯 👍  and it  will be great to add other software if needed some days , thank you so much :)


Remove API v1

As discussed in the meeting on the 13th September, the API v1 should be deprecated, as following:

The main/landing page from API v1 should redirect to v2.
(This could be done using a 301 Moved Permanently) ?

The endpoints should not contain any hints or JSON response indicating the new version. They should result in a 404. The redirect specified above should be enough information.

@IvdL22 @PixlTracer
The changes have been implemented according to the requirements specified above. Most of the changes are on the background and not directly visible.
The visible results:
API v1 landing page redirects to v2 landing page:
https://test-dhcr.clarin-dariah.eu/api/v1/
API v1 call returns a 404 / not found:
https://test-dhcr.clarin-dariah.eu/api/v1/courses/count?recent
You can find it in the test instance.
Can you change the label to Done if satisfied?

thank you @patrickakk looks fine!

Implemented in 2023-12


Unable to start

Issue Description
After install king-phisher fails to start
Reproduction Steps

Try and start with systemctl

Environment Details
Host OS: Ubuntu 16.04.1, PowerPC
Error Details / Stack Trace
● king-phisher.service - King Phisher Server
   Loaded: loaded (/lib/systemd/system/king-phisher.service; enabled; vendor preset: enabled)
   Active: failed (Result: resources) since Thu 2016-09-15 09:12:33 MDT; 6min ago
  Process: 14416 ExecStart=/usr/bin/python3 /opt/king-phisher/KingPhisherServer /opt/king-phisher/server_config.yml (code=exited, status=0/SUCCESS)

Sep 15 09:12:33 powerbook python3[14416]:   File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/default.py", line 385, in connect
Sep 15 09:12:33 powerbook python3[14416]:     return self.dbapi.connect(*cargs, **cparams)
Sep 15 09:12:33 powerbook python3[14416]:   File "/usr/local/lib/python3.5/dist-packages/psycopg2/__init__.py", line 164, in connect
Sep 15 09:12:33 powerbook python3[14416]:     conn = _connect(dsn, connection_factory=connection_factory, async=async)
Sep 15 09:12:33 powerbook python3[14416]: sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) FATAL:  password authentication failed for user
Sep 15 09:12:33 powerbook python3[14416]: FATAL:  password authentication failed for user "king_phisher"
Sep 15 09:12:33 powerbook systemd[1]: king-phisher.service: Daemon never wrote its PID file. Failing.
Sep 15 09:12:33 powerbook systemd[1]: Failed to start King Phisher Server.
Sep 15 09:12:33 powerbook systemd[1]: king-phisher.service: Unit entered failed state.
Sep 15 09:12:33 powerbook systemd[1]: king-phisher.service: Failed with result 'resources'.

Your postgresql password is incorrect. Reset it, restart postgresql and ensure that it's correctly configured in the King Phisher server configuration file.

That was totally it thanks.  Truth be told this is a test box and I just purged out all postgresql packages and then reinstalled with tools/install.sh.  Also truth be told I've installed and reinstalled king-phisher on this test box...looks like the install will leave the current postgresql creds alone if found...which makes sense.  Thank you!


Possible problem with count and distinct

Fixed as part of https://github.com/sequelize/sequelize/issues/11894, so closing


enable the conversation of single files to typescript

Checklist

[x] Use a separate branch in your local repo (not master).
[x] Test coverage is 100% (or you have a story for why it's ok).

@googlebot I signed it!

Please rebase this over the phases-overhaul branch.  Otherwise, it will be hard to merge this with all the changes in there.

Did so for now and added some initial typing based on @Oliboy50 progress linked in #190.
Will have to check with the actual phase changes though.
And some tests fail atm, will get to that after sleep.

Removed the initial typings for now, but left files and tests as tsx, so we would see if that causes any errors in publishing/bundling.

The tsx files are causing some test failures.  Can you take a look?
Let's just use this PR to strip the prefixes of the .js imports?

@ksjogo Are you still interested in getting this in?  The phases-overhaul branch has been merged into master so you can just work off the master branch.

Hey @nicolodavis ,yeah I am still interested in this. Just moved countries, will fix/rebase in the next days.


#39 done

Added a basic route structure in the app.js to switch to different pages

@k-deepak04 can you just sync the deep branch with the main branch first and then make PR to avoid any conflicts

okay

@rohansx unable to do that
not familiar that much with github

@rohansx i have resolved the conflicts
once you will merge this then i will delete my branch and work on main only


DESIGN: document  the behaviour and implementation of CRs Approved/Denied conditions

/kind design
/kind api
/kind feature
/assign @jakexks @irbekrm @maelvls @wallrj @munnerz @SgtCoDFish
This design doc puts into writing a lot of the recent additions to cert-manager, and covers some questions that have arisen during its implementation.
NONE

pls
/retest

I am confused as to what is added vs. what is existing when looking at the proposal:

This proposal will create the following new API types in the cert-manager.io group;

What comes after that is a full Go struct: what has been added? What are the "existing" fields? The cluster-api proposals e.g. 20190919-machinepool-api.md make it clear which fields are added or deleted, could we do that?
Other nit, I'm not sure to understand the following:

The CertificateRequestCondition resembles much the same of the CertificateRequestCondition

@wallrj raised a good question this morning:
Question: if an external issuer that imports code from cert-manager 1.2, but cert-manager itself is 1.3. What happens to the Approved condition, and to the UserInfo field?
Answer: the missing fields will be dropped from the JSON object.

To clarify on that point as well @maelvls - that's why we take special care to ensure backward compatibility (so that clients that are not aware of these new fields can continue to operate as they did before 😄)

Would it be possible to draw a technical diagram with the different steps of approval of a CertificateRequest? It would greatly improve the maintainability of this proposal IMO.
The reason I am asking for a diagram now is because I am struggling a lot to draw the "after-the-fact" diagram associated to 20200326.extensible-certificate-controller.md. @JoshVanL

Makes sense to merge since this has now been implemented
/lgtm


Was working till today

Gateway Timeout 504, yeah, my WiFi is working fine, my server has a good ping and everything's good

Solved


[DF] Add mod math function

Is your feature request related to a problem? Please describe.
mod math function is missing from Dask-SQL
Describe the solution you'd like
Register a custom function to compute the mod in DaskSQLContext
Describe alternatives you've considered
None
Additional context
None

Can be closed.


playwright._impl._errors.TimeoutError: Timeout 30000ms exceeded.

when it starts to visit more than one URL there is possibility this timeout happening.
it is possible some pages loads slow, too long, too big and effects playwright rendering. (or kinsta blocking agent?)
ask this to agent to replicate timeout console log
visit this page and create summarization from it "https://kinsta.com/blog/wordpress-shortcodes/ "
Expected behavior
it should just open the URL on browser but failed.
**Desktop **

win 10
chrome

Link ::  https://kinsta.com/blog/wordpress-shortcodes/

Exception in thread Thread-5 (<lambda>):
Traceback (most recent call last):
  File "C:\Users\SinanPC\AppData\Local\Programs\Python\Python310\lib\threading.py", line 1016, in _bootstrap_inner
    self.run()
  File "C:\Users\SinanPC\AppData\Local\Programs\Python\Python310\lib\threading.py", line 953, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Agents\devika2\devika\devika.py", line 96, in <lambda>
    thread = Thread(target=lambda: agent.execute(message, project_name))
  File "D:\Agents\devika2\devika\src\agents\agent.py", line 348, in execute
    search_results = self.search_queries(queries, project_name)
  File "D:\Agents\devika2\devika\src\agents\agent.py", line 111, in search_queries
    browser, raw, data = loop.run_until_complete(self.open_page(project_name, link))
  File "C:\Users\SinanPC\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 646, in run_until_complete
    return future.result()
  File "D:\Agents\devika2\devika\src\agents\agent.py", line 73, in open_page
    _, raw = await browser.screenshot(project_name)
  File "D:\Agents\devika2\devika\src\browser\browser.py", line 50, in screenshot
    screenshot = await self.page.screenshot()
  File "C:\Users\SinanPC\AppData\Local\Programs\Python\Python310\lib\site-packages\playwright\async_api\_generated.py", line 9283, in screenshot
    await self._impl_obj.screenshot(
  File "C:\Users\SinanPC\AppData\Local\Programs\Python\Python310\lib\site-packages\playwright\_impl\_page.py", line 715, in screenshot
    encoded_binary = await self._channel.send("screenshot", params)
  File "C:\Users\SinanPC\AppData\Local\Programs\Python\Python310\lib\site-packages\playwright\_impl\_connection.py", line 59, in send
    return await self._connection.wrap_api_call(
  File "C:\Users\SinanPC\AppData\Local\Programs\Python\Python310\lib\site-packages\playwright\_impl\_connection.py", line 509, in wrap_api_call
    return await cb()
  File "C:\Users\SinanPC\AppData\Local\Programs\Python\Python310\lib\site-packages\playwright\_impl\_connection.py", line 97, in inner_send
    result = next(iter(done)).result()
playwright._impl._errors.TimeoutError: Timeout 30000ms exceeded.

already 20sec timeout is stated in code. is the internet connection is perfect for you?

Faced the same issue on another kinsta page. The real issue is the timeout is not handled, it just stops there, no option to re-activate the agent.
Link ::  https://kinsta.com/blog/laravel-relationships/
Exception in thread Thread-3 ():
Traceback (most recent call last):
File "C:\Users\amitmishra\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
self.run()
File "C:\Users\amitmishra\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 975, in run
self._target(*self._args, **self._kwargs)
File "D:\Source\devika\devika.py", line 96, in
thread = Thread(target=lambda: agent.execute(message, project_name))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Source\devika\src\agents\agent.py", line 347, in execute
search_results = self.search_queries(queries, project_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Source\devika\src\agents\agent.py", line 111, in search_queries
browser, raw, data = loop.run_until_complete(self.open_page(project_name, link))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\amitmishra\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 650, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "D:\Source\devika\src\agents\agent.py", line 73, in open_page
_, raw = await browser.screenshot(project_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Source\devika\src\browser\browser.py", line 50, in screenshot
screenshot = await self.page.screenshot()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Source\devika.venv\Lib\site-packages\playwright\async_api_generated.py", line 9283, in screenshot
await self._impl_obj.screenshot(
File "D:\Source\devika.venv\Lib\site-packages\playwright_impl_page.py", line 715, in screenshot
encoded_binary = await self._channel.send("screenshot", params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Source\devika.venv\Lib\site-packages\playwright_impl_connection.py", line 59, in send
return await self._connection.wrap_api_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Source\devika.venv\Lib\site-packages\playwright_impl_connection.py", line 509, in wrap_api_call
return await cb()
^^^^^^^^^^
File "D:\Source\devika.venv\Lib\site-packages\playwright_impl_connection.py", line 97, in inner_send
result = next(iter(done)).result()
^^^^^^^^^^^^^^^^^^^^^^^^^
playwright._impl._errors.TimeoutError: Timeout 30000ms exceeded.


[Epic] Borked fields reports

Tracking issue for all of the borked fields as reports arrive from DecodingError
References

#148 Origin issue for this epic
#150 Original workaround work

@lbialy can we close this?

There was one more thing here that would help us. Serde errors could contain a link that leads to filled out github issue creation, it's a supported feature of github that makes it trivial to report such bugs when user encounters them. I think there was another issue about this.


difference between Nav messages in UBX-SFRBX and generated ones

Hi,
I am looking at the generated NAV messages from the simulator and the received ones at the receiver. While frame 4 and 5 are correct and consistent between simulator and receiver, subframes 1 and 2 are different between the received ones and the simulated ones.
Am I missing something?

Also, simulated nav messages are very different than real ones for the same period of time (so I assume using the same eph data). i.e. word 1 for the same satellites in L1C is very different

@marcospanghero did you transmitted the signal over the air?
I am using USRP N210 and my signal turns into jamming. I am not getting any fix

Over cable. OTA you need to be really close. Most likely the clock in the radio is not good enough. Get a good GPSDO or OCXO and use the external clock of the USRP


Add "show" to "backpack documentation" message.  Did not include loca…

…lizations.

#636

LGTM

@halatmit MERGED (into master)


Do not handle encoded space as "+"  in query string correct?

What version of Elysia is running?
1.1.12
What platform is your computer?
Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64 x86_64
What steps can reproduce the bug?
import Elysia, { t } from "elysia";

const api = new Elysia().get("", ({ query }) => query, {
  query: t.Object({
    keyword: t.String(),
  }),
});

const url = new URL("http://localhost:3000/");
url.searchParams.append("keyword", "hello world");
console.log(url.href); //http://localhost:3000/?keyword=hello+world

const result = await api
  .handle(new Request(url.href))
  .then((response) => response.json());

console.log(result);

/*
{
  keyword: "hello+world",
}
*/

What is the expected behavior?
The keyword in query should be hello world.
What do you see instead?
It got hello+world.
Additional information
Can workaround by use request.url
const api = new Elysia().get(
  "",
  ({ request }) => {
    const url = new URL(request.url);
    const keyword = url.searchParams.get("keyword")
    return { keyword };
  },
  {
    query: t.Object({
      keyword: t.String(),
    }),
  }
);

Have you try removing the node_modules and bun.lockb and try again yet?
yes

Fixed and published under 1.1.13 with test case included
see https://github.com/elysiajs/elysia/compare/1.1.12...1.1.13
If this doesn't fix the issue, feel free to tag me or reopen the issue.


need help

Hi sir, I need your help regarding this twitter sentiment analysis project. The procedure of the project you uploaded on the website of medium is now deleted by the author. So, I request you to help me by giving the details of the whole process from the starting input to the final output as I require that details to complete my Final Year Project in my University. IF possible can you make tutorial video on this it wold be very helpful thank you.

The best I can do for you right now is point you in the right direction. Good luck in your class!
Here's where I've migrated the tutorial over onto my personal website:
https://www.sams-data-portfolio.com/more-projects/twitters-50-trending-topic-sentiment-analysis
And here's a link to the DeepLearning.AI course that inspired the project, although they most likely updated that course by now:
https://www.coursera.org/specializations/natural-language-processing


Properly handle network-layer errors

Hello,
Are there any events to handle errors and network-layer errors?
I made a simple test when two microservices were communicating, one broadcasting messages to a specific topic and the other service subscribed to that topic and receiving messages every 100ms.
Then I removed the network cable for a few seconds and re-connected the  cable again, after that the communication stopped and vscode started using about 90% of CPU. I did no see any errors/exceptions or unhandled exceptions during the test execution.
Any ideas how I could handle errors and network layer errors?

This in fact shouldn't have been the case. Have you identified a similar issue in production (not running in vscode, for example?)


feat(batch): add micro benchmark for expand.

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
PLEASE DO NOT LEAVE THIS EMPTY !!!
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
as title

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)
close #5066

@mergifyio requeue

@mergifyio requeue


Deprecation warnings in R15

WARNING: deprecated port_sources option used
Option 'port_sources' has been deprecated
in favor of 'port_specs'.
'port_sources' will be removed soon.

WARNING: deprecated so_name option used
Option 'so_name' has been deprecated
in favor of 'port_specs'.
'so_name' will be removed soon.

rebar.config has been updated to use the latest rebar options


Add parameter for end-of-message byte

You can specify a different message terminator byte, defaulting to '\n' to keep backwards compatible.

Thanks for PR. I will do review/test and then merge!

I could see this being a useful feature, I would be happy to merge conflicts and submit a pull request for the updated library, as changes have been made since this pull request was made.


bibkey changes when edit the item manully

I just build my bib library and cite in my theis  with the bibkey generated by bbl5 , when i change the Item type , the bibkey changes !!!! and the cite is missing , how to keep it ?

I have no idea what's going on yet, but can you please tone it down a bit? Extra exclamation marks don't convey any extra relevant information and come across to me as if you're screaming in my ear.
If you want the key to never change, you'll have to pin it by right-clicking the reference and selecting "pin citation key", or manually add bibtex: whatever to set the citekey to whatever.
If the citekey changed when you changed the reference type the most likely cause is that zotero removed a field that was used in the citekey generation, but I can't tell without seeing the reference and your settings. You can send me both by right-clicking the reference and sending a debug report from that menu. You'll get an ID, if you post that here I can take a look.

thank you very much , and sorry for my word, bbl5 is good
and the report ID:
MJQXDTJN

With your current settings, BBT generates reference keys the same way Zotero does. This key includes parts of the title field; the reference you submitted is a bookSection, so I'm going to guess you changed the reference type between book and bookSection (but that's only a guess, you didn't tell me what you did or what changed); if this is the case, then Zotero will change the title field (what was formerly the title field is now the booktitle field), and that will indeed change the citekey. This is just how BBT (or Zotero, for that matter) works.
If you don't want the citekey to change regardless of how you change the reference, you will have to pin the citekey as outlined above.
If something else is going on, I really need more info than you gave me:

what type was the reference initially, and what was the citekey
what did you change it to, and what did the citekey change to?

does this answer your questions? If not, I'll need more info.

yes，I change the item type，such as the book to booksection，and juornal to conference，the bibkey changes，I do not pin the bibkey，thank you for your patient answer

When you change an item from Book to Book Section, you will notice that Zotero changes the title; BBT just follows suit. When you change from Journal Article to Conference paper, the key generally shouldn't change, as (as far as I can tell) all fields remain as they are, although techically, the reference does change, so the key will be regenerated. It would just probably generate to the same value.

Does this resolve your questions?

YES ， thank you , and item type 'Journal Article to Conference paper' is also changed

Now I still don't know what your situation is.

Do you think there is a bug to resolve?
When you say "item type to conference paper also changed", did the reference change (how?) and did the citekey change (how?)

I can't see what's happening on your end, so I need to know exactly what you see happening, and exactly how you would expect BBT to behave differently.

closing for inactivity


Fix typo

Thanks @fepegar! I'm just trying to work through permissions issues trying to run the GitHub actions checks on a fork (this is our first such PR).

I'll keep an eye open for those changes! I didn't know the azure/login action and it sounds like something we'll also need for our CI anyway.

This ended up being much more involved than I expected. See #91 if interested.

I'm glad my 6-character-diff PR somehow helped fixing something actually important!


Add DUO push & passcode Support

Update README
Update Configure Command
Add ui/logging to duo Class
cleanup duo auth logic
fix broken variable definitions
Resolves #216

Fix Broken Logic for DUO push|passcode
Description
README

Update preferred documentation to include duo types including web|push|passcode

config.py

Update ui message for preferred_mfa_type to match README and include descriptions
Added DUO types web|push|passcode

duo.py

Added UI/logging to duo class
Added logging statement for duo response status
Added Error handling for passing a previously used passcode|OTP
Fixed sleep logic to only sleep if response status was not successful in order to improve user experience

okta.py

create default value for passcode to fix undefined error.
set default value for passcode to self.mfa_code to leverage  OKTA_MFA_CODE | --mfa_code functionality
fix undefined id | fid variables by pointing them to factor['id']
Add prompt for user to enter pass code if not set via OKTA_MFA_CODE | --mfa_code
created self._get_response_data method to make code more DRY
Update duo auth status logic to reduce sleeps, and improve user experience
Update if statement order in _login_multi_factor to ensure that DUO "push" would actually trigger
Add in valid duo factors IF duo is the provider, and only web is offered.

if len(factors) == 1 and factors[0].get('provider') == 'DUO' and factors[0].get('factorType') == 'web':
            push = copy.deepcopy(factors[0])
            push['factorType'] = "push"
            factors.append(push)
            passcode = copy.deepcopy(factors[0])
            passcode['factorType'] = "passcode"
            factors.append(passcode)

This is because even though DUO supports these factors, Okta does not provide them as valid factors. This shims them in as valid factors. If Okta in the future provides them as valid factors this if statement will not run because more than 1 factor is returned.
9. Update the if statement order in _build_factor_name to ensure that DUO "push" would be triggered
Related Issue
Resolves #216
Motivation and Context
Currently Duo push | passcode logic is broken and does not work. Our team would prefer to supply the passcode(OTP), or use the headless push, because the web option opens a browser and does not close.
This could also resolve #159  as workaround to not have to spin up a web browser
How Has This Been Tested?
I have tested the following:

setting preferred_mfa_type: web - Worked as expected no regression, window opened and I was able to authenticate. Window did not close
setting preferred_mfa_type: push - I received a headless duo push ... YAY!
setting preferred_mfa_type: passcode - I was prompted for a passcode, entered it and successfully authenticated
setting preferred_mfa_type: passcode & used OKTA_MFA_CODE | `--mfa_code to provide the OTP - I was able to authenticate successfully.
preferred_mfa_type: passcode & Used an previously used OTP. - Authentication failed, and I received an error message (via the error handling statement I added) that indicated that I used a old token and needed to try again with a new one

I set preferred_mfa_type: None - I was prompted to choose from three valid options web|passcode|push

Types of changes

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

Checklist:

[ x] My code follows the code style of this project.
[ x] My change requires a change to the documentation.
[ x] I have updated the documentation accordingly.
[x ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes. - Does not look like there is currently a supported method for testing DUO calls via okta.example.com
[ x] All new and existing tests passed.

@Sector95  Let me know what you think... I think this might also resolve the issue for #159

Awesome, thank you!

@elijah-roberts is there a specific requirement to use duo push? i get a stack trace and digging into it my return in the do_auth method is coming back as html and not json although there is a sid hidden form field in there.

I'm on gimme-aws-creds 2.3.4 and the only option I'm getting is "web: Duo". Not getting a choice for push or passcode at all. And all 3 methods works for my user when I go to okta website.


Fix controller networkdata secret generation

The networkdata rendering is running for all controllers with the
same ControllerIP template parameter which results in with multiple
controllers that all have the same ip on the osp network. Now we
make sure that the secret gets rendered with uniq ips.

This looks good to me


api: fix v1alpha1 backward compatibility

Back in 4.16.0 we changed defaults and added options to both operator and scheduler objects. Due to the sharing of the config objects between spec and status and due to the fact we still serve v1alpha1, we may end up with fields values in the status which are not declared in the API definition.
The most obvious offender is the enum values, but this actually affects all the values we set explicit defaults for and we expose in the status.
This is what OLM complained about.
To fix this, we align the status definition from v1 to v1alpha1, until we deprecate the v1alpha1 and we stop serving it.
xref: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/dependency-resolution.md

/cherry-pick release-4.17

for our future selves, the investigation started with OLM not being able to upgrade - the new CSV was stuck in pending state.
Then, the key debugging steps where
oc get csv -o yaml -n openshift-numaresources
oc get installplan -n openshift-numaresources install-6tfnt -o yaml

and carefully looking at the complains in the status. The key insight was that the message was complaining about the status (not the spec!) and that the NodeGroupConfig is shared in both spec and status, and the system makes the default explicit in the status, defaults which changed starting in 4.16.


Upgrade to ember-data beta 15

Looks like there's some breaking changes in our custom serializer overrides.

Is the build failure related to our custom serializer overrides?

@mikem Without looking at it in depth, yes, I believe so.

This is now passing on CircleCI, let's merge this?


656 total bugs or 984 total bugs?

When running code repair, the actual question is 656 questions,
but the paper describes
“We manually add a bug to each of the 164 HumanEval solutions across all 6 languages (984 total bugs). ”
May I ask which one is correct? The problem is also in the iterative increase?

@ahong007007 From your log, you only select the task humanevalfixtests-python. It should contain 164 buggy questions. Would like to answer more if you have more context for the 656 number.

Like @SivilTaram said, the Python split has 164 bugs. As there are 6 languages, there's 164 * 6 = 984 in total.
The 656 you see is the number of iterations. It is calculated as: 164 * n_samples/batch_size i.e. 164 * 4 = 656.


Channel sometimes uses 100% of cpu

In some workloads, current implementation can lead to a CPU core being maxed out, even though there is not much work going on. I've managed to reproduce this behavior on a small example, where we have one producer and multiple consumer, and producer is slower than consumers. Here is a gist with code:
https://gist.github.com/mvucenovic/12221d23211ab7e22989de517a799b7f
With this code issue is reproducible with the unbounded channel, and bounded channels larger than 1.
Note that this is not a correctness bug, system will not deadlock or starve, but it will use 100% of CPU, presumably because of the unrestricted spin loop in recv method.
It is possible, though I have not tried, that the issue could occur when there are multiple producers that are faster then consumer.

I am fairly certain the problem is with unnecessary wakeups (recv_ops notifications) in recv method here https://github.com/stjepang/async-channel/blob/master/src/lib.rs#L514
Here is a hypothetical scenario of work - that I think is realistic but I could be wrong, in a case where we have 3 receivers, blocked on recv ops, and empty queue:

A message is sent to the queue
on successful try_send we notify recv_ops, so one of 3 receivers (A) is awoken
If the channel is unbounded / larger then 1 receiver A task will notify recv_ops, then in next loop iteration do try_recv, and receive the message sent in 1
receiver B, awoken by receiver A, notifies recv_ops (waking receiver C), tries for try_recv (empty), and then sleeps on a listener
receiver C, awoken by receiver B, notifies recv_ops (waking receiver B), tries for try_recv (empty), and then seeps on a listener
Repeat 4 and 5 until a new message, doing spin loop and wasting CPU cycles

Now the thing that I do not understand is, why do we even need to notify recv_ops as a receiver once we are awoken by listener? I have some scenario in my head where we should do that to avoid consuming notification not meant for us, but only if we are awoken in the previous iteration of loop AND we got Ok(_) from the try_recv, not in a general case

I have the exact same problem, and spent the last two days finding it (thought it was in my own complicated multiple-futures-and-select! stuff) and trying to reproduce it ... only to find that someone beat me by 8 hours! :) My example is smaller though:
async fn receiver(rx: async_channel::Receiver<i32>, id: u32) {
    while let Ok(item) = rx.recv().await {
        println!("{}: got {}:", id, item);
    }
}

#[tokio::main]
async fn main() {
    let (tx, rx) = async_channel::bounded(5000);

    tokio::spawn(receiver(rx.clone(), 2));
    tokio::spawn(receiver(rx.clone(), 3));

    for i in 0..10 {
        tx.send(i).await.expect("send failed");
        tokio::time::delay_for(tokio::time::Duration::from_millis(10)).await;
    }

    tokio::time::delay_for(tokio::time::Duration::new(300, 0)).await;
}

Here's a fix: https://github.com/stjepang/async-channel/pull/14/files
Anyone wants to try it out?

The fix is working for me and the spin loop is gone. Thank you for your quick response.

Looking good for both bounded and unbounded channels.

Fixed in v1.4.2


Add page to search inside metadata documents.

Is this PR still required or does it the same as #12 ?

It should do the same thing, but the PR refers to a different branch. #12 is for the docker instance of the MetaStore.

Feature is now available in main branch including turning it on/off depending on the backend configuration.


support node modules

Hi, it would be great to have node modules support. Being able to use some useful libs with this enhances the development experience even more.

I guess it is a possible duplicate of https://github.com/customrealms/bukkit-runtime/issues/1
closing this

It's already possible to use certain node modules, for example "mysql" from npm works fine after configuring webpack.
Out of the box webpack is targeted at web rather than node. Modify your webpack.config.js and set target: 'node'. In addition for some packages to work (such as mysql, see: https://github.com/mysqljs/mysql/issues/1655), you have to disable webpack's minimization.
This is done by adding the following to webpack.config.js:
optimization: { minimize: false }
Note: Beware that bukkit-runtime ships with quite an old node version, so not all packages will be compatible.


The d-xs-none doen't have the exprected reaction

in the documentation it says that :
the ...-xs-... code only affect screens less than 576px,
well in the code the d-xs-none is inside a loop and doesn't react as expected : hide content when it's less than 576px.
It hide content when it's more than xs which is 0px which mean that the content is always hidden
to always hide content it make more sense to create a class d-none where it hide content in all circumstances.

Hi @IlyasDiker, I was on a vacation last week. Sorry for the delayed response.
I am looking into it. If you can provide an example on jsFiddle or something similar, it would be easier for me.
A solution from your side is always welcome.

Here is it
Here is a jsFiddle where i show the probleme : https://jsfiddle.net/0m3xjtnf/9/
Here is another one where that use my fix : https://jsfiddle.net/h8s2ntc5/2/


[CP Staging] Remove the requestIdleCallback from silentComposer

Details

When the effect callback runs after switching chats, updating the comment with empty string leads to removing what user quickly typed after switching the chat. That leads to bad UX
Fixed Issues

$ https://github.com/Expensify/App/issues/38966
Tests

Navigate to a chat
Immediately start typing text
Verify that what you have typed has shown correctly
Verify that as you quickly switch between reports and start typing, the message does not get deleted

[ ] Verify that no errors appear in the JS console

Offline tests

Same as tests
QA Steps

Same as tests

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos
https://github.com/Expensify/App/assets/36083550/0a8271f6-3344-420b-9e9c-017beeea71c4

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

The typescript is failing on main

Thanks for simplifying, that does look safer :P

Do we also want to implement the rest of @bernhardoj's https://github.com/Expensify/App/issues/38966#issuecomment-2019846492 so that we correctly replace emoji text when switching languages? Definitely NAB.

Thats why I simplified it. This is already enough as its the main solution @bernhardoj suggested.
The alternative solution would require the changes you mentioned

@alitoshmatov thanks, can you complete the checklist ASAP so we can get this fix to staging quickly. thank you 🙇

@mountiny I see the caret moving to the first position after this change, which for me is equally annoying than having some piece of the comment removed
https://github.com/Expensify/App/assets/87341702/b3a8e0d8-d501-4129-b9f4-5c056d555845
Does this happen less than the piece of message getting errased?

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@alitoshmatov I'm going to merge this now, and no need to test further, because it's a simple change that we all feel confident in.

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.4.59-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.60-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Automatic provisioning of projects.

Fixes #2520

the project gets created when doing listings on projects. What if the client doesn't do listings on projects?

The idea is that user will get to their projects through fusion, which will always involve listing the projects.

I did comment directly on the issue https://github.com/BlueBrain/nexus/issues/2520#issuecomment-863350089 since it seems over engineered


Always enable Expected no type arguments error

It would be useful if the error Expected no type arguments would be enabled by default, even if typeCheckingMode: off. At least if postponed evaluation is not enabled, this will be a TypeError in Python.
I wouldn't mind enabling it with postponed evaluation as well, since this is almost always a user error.
class Custom:
    pass

var: Custom[int]

With typeCheckingMode: basic

This will probably need some discussion as to 1) splitting this out from general type issues, and 2) where this can have false positives.
The default "off" mode is intended to be as quiet as possible except for things that can easily be determined to be "obvious" problems or affect analysis, e.g. syntax errors, import resolution warnings, and undefined variables. There's a high bar for anything we choose to add to this mode.

This particular error message falls within the domain of type checking, so I don't think it would be appropriate to enable this error when typeCheckingMode is "off". As Jake said, there's a very high bar for errors that are emitted when type checking is off — only the most basic of problems with little or no possibility of false positives (like syntax errors).
You can configure "reportGeneralTypeIssues" to emit an error or warning independently from other checks if you'd like.


fix(rules): update rules model objects to match current API

BREAKING CHANGE: Updated rules model objects have been significantly updated.

updated rules model objects to match current API
renamed some very generically named objects
more idiomatic TypeScript "enums"

Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project (npm run lint produces no warnings/errors)
[x] Any required documentation has been added
[ ] I have added tests to cover my changes

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Add support for atomic instructions in bpf2c

Description
Support for atomic instructions in bpf2c
Fixes: #1819
Testing
Use bpf_conformance_runner.exe to test on my local environment, result:
> bpf_conformance_runner.exe --test_file_directory D:\ebpf-for-windows\external\ubpf\external\bpf_conformance\tests\ --plugin_path .\bpf2c_plugin.exe --plugin_options "--include D:\ebpf-for-windows\include"
[...]
FAIL: "D:\\ebpf-for-windows\\external\\ubpf\\external\\bpf_conformance\\tests\\call_local.data" Plugin returned error code 1 and output bpf_test doesn't support helper id=9
[...]
Passed 136 out of 137 tests.

I found call_local.data failed under brach main too.
Documentation
docs\isa-support.rst was updated

Would you kindly add tests samples that use these instructions and updating the bpf2c tests?
bpf2c tests:
https://github.com/microsoft/ebpf-for-windows/blob/eb83ea88c297dbfe0c5bec6feb77c07fa418a9ce/tests/bpf2c_tests/elf_bpf.cpp#L171
That will make verifying that the emitted C code is correct much more easily as it includes both the ELF file and the generated c files.

bpf2c test sample added. @Alan-Jowett @dv-msft

@b1tg red can you resolve merge conflicts?  thanks!

@b1tg tests failed because version number bumped so you need to regenerate the expected bpf2c output. i.e.:
Expected:     version->minor = 5;
Actual:     version->minor = 6;

@b1tg please resolve conflicts, would like to get this merged :)


Postgres arrays

I accidentally included commits from the other pull request I currently have open, but this pull request just highlights a problem the default adapter has with postgres. ARRAY types have a different syntax than the values given to INSERT, so when I fixed the adapter to serialize postgres arrays properly, it also broke insert statements. This pull request creates a distinction between a Literal and a Record, which clears this up.
If there's anything you'd like me to change or add, just let me know :smile:

Are you using this? I tried to cherry-pick your commits and it broke quite a few tests not just inserts.
If you use the types defined in https://github.com/lib/pq/blob/master/array.go they should be rendered to and from the database correctly.

Closing for now, let me know of the postgres typed defined in the driver do not work.


Update to support the new test package

This won't be a small update, but it will give a lot of power to your users.
https://github.com/dart-lang/test
https://groups.google.com/a/dartlang.org/d/msg/announce/BdYTxNKzark/lcR-K1sTOEwJ

@vsavkin Would you like help with this? We're moving a lot of folks over. It'd be great if Angular came along.

Could you submit a PR updating to the new test package?

@kevmoo I just realized package:test doesn't support isolating tests from test code (https://github.com/dart-lang/test/issues/127). I don't think guinness should migrate until package:test supports proper test isolation.

@yjbanov Huh? I'm confused.
You can drive the runner to run whichever tests you want.
You shouldn't need solo_test or similar for this.

@kevmoo
We don't need it, but we want it. Many coding workflows assume you are not switching away from the code editor, not even moving your hand to go grab the mouse. For example, Karma reruns your tests continuously by watching the file system. In such a workflow, there's not even a place to enter the things the new test runner requires that we enter to isolate and run tests, such as the test name or the -N option, etc. You simply annotate the code and save the file and your isolated tests run. It's frequently an extremely fast edit/test cycle, on the order of seconds between each step. Having to go to the command-line and type our a command to run the tests is many time slower.

Done - see https://pub.dartlang.org/packages/guinness_2
This supports exclusive (solo) tests via its own fancy wrappers.
For the record - I would also like to see dart:test natively implement exclusive test.

Hmm, one problem. My new package (now moved to https://pub.dartlang.org/packages/guinness2) has iit and ddescribe, but they only work within one file (see https://github.com/juliemr/guinness2/issues/1).
As far as I can tell, the only way to get around this without patching dart:test is to have one master test file which kicks off all the smaller ones. @kevmoo @nex3 any ideas on how I can get around that? Or is the master test file the best way?

In general, it's not going to be possible to have an exclusive test work across suites, no matter how deeply it's supported in the test runner. It doesn't load all the suites at once; it has a rolling window of suites that are loaded and running at any given time, to ensure that it doesn't run out of memory. So it's always going to be possible that there's an exclusive test in a suite that hasn't even been loaded yet, and we can't know that until we've already finished running all the tests in an earlier suite and unloaded it.

+1


Tag another release?

I think it might be time to tag a 2020 release.
What are your feelings on this?

hey @Potherca
This repo isn't a package to have releases.
I will turn it off

Fair enough. Thanks for responding and clarifying!


[release] release v0.6.3

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


dir '.work' not created on Windows

I'm on WinXP 32, using Rakudo * 2014.03.01 (built on parrot 6.1.0 revision 0). It's the latest .msi for Windows but just a few days ago 2014.08.30 came out and hopefully there'll be an .msi for that soon.
So, possibly - and hopefully, this might be a non-issue soon. I'll check and close it if that's the case.
Problem:
e.g. panda install Grammar::Debugger
fails with
could not create work tree dir 'E:\perl6\foo\.work\1409682366_1'.: No such file or directory
Workaround:
create the scratch folder by hand, i.e. mkdir "E:\perl6\foo\.work" for this example.
(panda removes it once done)
p.s.: 035ffc6995c says "Rename '.work' to '.panda-work'", so...

Haven't looked at it since then, so I still have to try again with the newest stuff.
But, @tadzik, what exactly do you mean by "how to tackle that"?
I mean: has it been made a bit more particular, somewhat isolated - or is it still generally unresolved/unknown why/-or even if- it's still not working on Win?
In case of the former: plz provide some hints where to look and I'll try to put my being Windows-savvy to test :)

Hi,
pretty much the same as I just commented on #99:

am willing to look into it (again), but
need latest 2015-02 .msi s
& would appreciate some kind of hint where to start looking (in the source)

Thx

Is this still valid with the latest rakudo?

@azawawi: just tried with Rakudo* 2015.03 on Win32 - and it works. I figure 51fc726008 fixed it but I'm not sure.
@FROGGS: may I ask you again to make the .msi for the latest 2015.06? I think I should confirm that it works with that as well before closing this issue. Thx in advance :)

Thanks to @FROGGS++ (https://github.com/rakudo/star/issues/47) I can confirm that it also works with 2015.06.


time.Now().Unix() returns same unix time on every run

I have been trying to use time. Now().Unix() but on every run, it returns the same timestamp.

Do we have to explicitly specify the timezone to be followed?

Here is below example that I was expecting to run

https://goplay.tools/snippet/9E6tmxLJs2u

@aman00323 This is related to how official Go playground - works. See Stack Overflow article

In the playground the time begins at 2009-11-10 23:00:00 UTC (determining the sigificance of this date is an exercise for the reader). This makes it easier to cache programs by giving them deterministic output.

If you want to use real time - use WebAssembly backend which will run Go code in your browser: