Fix tests and add CI

Add the packages required to use FlightSims.jl to its Project.toml
Running ] test would throw the following errors -

figures directory not being in the test directory.
integrated_environments.jl includes a non-existent file (backstepping_position_controller_static_allocator_multicopter_env.jl)  instead of backstepping_position_controller_static_allocator_multicopter.jl.

Both these issues have been fixed now.

Since there's no CI set up, there's no real way to know if any changes made to the package would break something else or not. Hence, add CI.

Note - The Xvfb - install and run step in the CI workflow is important. If this step isn't there, the following error occurs -
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: linuxfb, minimal, offscreen, vnc, xcb.

Aborted (core dumped)
connect: Connection refused
GKS: can't connect to GKS socket application

signal (11): Segmentation fault
...

@JinraeKim simply adding the CI.yml file works in this case as the CI workflow is correctly configured. It is run using Github Actions. The way it is currently set up, the CI runs every time a PR is made to master (this can be regulated by preventing first-time contributors' PRs to trigger CI runs) or a commit is pushed directly to master.

@thazhemadam Ah, I understood how I should deal with test-specific packages now (so embarrassed due to the fact that I haven't known it by now).
Thanks for your kind explanation and helpful commits!

@thazhemadam Hi, again!
I'd like to know how to pre-test the CI workflow before merging it into origin/master.
That is, is it possible to test the CI in my custom branch?

Hi, @JinraeKim! Opening a pull request from your branch to master will trigger the CI run. Once the PR is opened, the CI will also run for every commit you make to your branch subsequently.
(see here)

Thank you, @thazhemadam.
But I think that there was a miscommunication.
I mean, before adding the workflow to the branch annotated (in this case, master), can I check whether the CI will work properly?
For example, if I add the file to a branch foo and annotate it as to be tested for all PRs, it will work not even for foo != master?

@thazhemadam
I found that PR of branch foo to master with CI.yml automatically runs the github workflow.
Thanks :)


Installer hangs for ~1 minute with progress bar at 100%

Steps to reproduce
Install OpenSim-e1c6a4db-2018-05-30-win64.exe.
Expected result
Installer provides feedback to user about progress of install.
Actual result
New behavior not seen in installer from earlier today: after the progress bar reached 100%, a Windows dialog something like this appeared. After clicking OK, the Windows dialog disappeared and nothing seemed to be happening for ~1 minute—long enough that I think many users would have killed the process.

Environment and GUI version
OpenSim-e1c6a4db-2018-05-30-win64.exe

This is likely while running the redistributable (a side effect of /quiet), so maybe not quiet by default @chrisdembia ?

Thanks @aymanhab. I fixed this issue in PR #811.


Can't image.save(file=f). Also can't image.save(filename=tmp.name) with a tempfile.

I've created a test that outlines my issue in this gist:
https://gist.github.com/audiodude/277e48ffb48c378c97e611d94f8b907d
wand_test shows that when I do:
        with open('circle2.jpg', 'wb') as out_file:
          image.save(file=out_file)

I get:
wand.exceptions.MissingDelegateError: no decode delegate for this image format `' @ error/blob.c/ImageToBlob/1557

Even though I can successfully save the JPG image in the lines above if I use filename=.
I thought I could get around this by using a NamedTemporaryFile, and passing the name, but it results in a similar exception.

It's because ImageMagick can't determine what format the image is written as, whereas it can guess the format from the suffix if a filename is present.  You need to manually set its .format first.


fix(package): update jasmine to version 3.1.0

Closes #1297

same problems, fails randomly at times.


Identifiers validation failed for dataset Avifauna de la reserva de la biosfera El Cielo, Tamaulipas, México

Identifier validation failed for the dataset Avifauna de la reserva de la biosfera El Cielo, Tamaulipas, México:

Crawler attempt: 307
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 1000
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 1000 total records; 1000 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740176/step

New IDs sample:

Old IDs sample:

3060de7a4619f84c29782fc1334dbe1d
49025f8c32cbf9f6625eeb49db241e20
63092489d0df36bbe6308e520088bbf2
7e783a794e7627af62e92efec7c0519a
9fff2db8db37cb53769b23dd14cdf729
a3b286dbc14c5e349a38663be054ec34
daea6c88ed6461c4b932171ace4085cd
dea87a5a0f15dd2a723e59cff09cf37c
e1aae52dc64e5259910b39b0e6e45700
0ae0bba044ffb2ac75462d52cb68deae

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Avifauna de la reserva de la biosfera El Cielo, Tamaulipas, México : https://doi.org/10.15468/kjtk0h.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Avifauna de la reserva de la biosfera El Cielo, Tamaulipas, México:

Crawler attempt: 308
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 1000
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 1000 total records; 1000 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741110/step

New IDs sample:

Old IDs sample:

3060de7a4619f84c29782fc1334dbe1d
49025f8c32cbf9f6625eeb49db241e20
63092489d0df36bbe6308e520088bbf2
7e783a794e7627af62e92efec7c0519a
9fff2db8db37cb53769b23dd14cdf729
a3b286dbc14c5e349a38663be054ec34
daea6c88ed6461c4b932171ace4085cd
dea87a5a0f15dd2a723e59cff09cf37c
e1aae52dc64e5259910b39b0e6e45700
0ae0bba044ffb2ac75462d52cb68deae

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Avifauna de la reserva de la biosfera El Cielo, Tamaulipas, México : https://doi.org/10.15468/kjtk0h.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Avifauna de la reserva de la biosfera El Cielo, Tamaulipas, México:

Crawler attempt: 310
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 1000
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 1000 total records; 1000 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741728/step

New IDs sample:

Old IDs sample:

3060de7a4619f84c29782fc1334dbe1d
49025f8c32cbf9f6625eeb49db241e20
63092489d0df36bbe6308e520088bbf2
7e783a794e7627af62e92efec7c0519a
9fff2db8db37cb53769b23dd14cdf729
a3b286dbc14c5e349a38663be054ec34
daea6c88ed6461c4b932171ace4085cd
dea87a5a0f15dd2a723e59cff09cf37c
e1aae52dc64e5259910b39b0e6e45700
0ae0bba044ffb2ac75462d52cb68deae

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Avifauna de la reserva de la biosfera El Cielo, Tamaulipas, México : https://doi.org/10.15468/kjtk0h.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


fix: Corrected typos in documentation files

Describe changes
Fixed several typos in the documentation files for better readability and clarity.
Ticket or discussion link
N/A
Review checklist

[x] Proper documentation added
[ ] Proper tests added

Screenshots

Hey @cypherpepe, thanks for contributing. Perhaps you'd be interested in recreating https://pallad.co/docs and providing better guides for end users on using Pallad? If so, ping me on TG: marciniak or DC: schoolboytom.


Document / Feature on how to intercept namespace creation / modification

Hi,
I would like to know if there is any way or work around to intercept helm creating / modifying namespace, which means it shall be compatible with:

helm install <chart_name>
helm install <chart_name> -n <given_namespace>
helm install <chart_name> --create-namespace
helm upgrade <chart_name>
helm upgrade <chart_name> -n <given_namespace>
helm upgrade <chart_name> --create-namespace

My scenario relates to k8s v1.25+ PSP deprecation. My plan:

Add condition statement as check API version policy/v1beta1/PodSecurityPolicy exist. If not, then don't render PSP.
[TODO] Intercept namespace creation / modification and append sample policy standard as k8s documentation suggested:

apiVersion: v1
kind: Namespace
metadata:
  name: foo-baseline-namespace
  labels:
    pod-security.kubernetes.io/enforce: baseline
    pod-security.kubernetes.io/enforce-version: latest
    pod-security.kubernetes.io/warn: baseline
    pod-security.kubernetes.io/warn-version: latest

https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/security/podsecurity-baseline.yaml
I did try some hacky way, e.g. schedule a Job as "helm.sh/hook": pre-install that run kubectl to label namespace but failed (it just hangs forever). What is the right way to intercept namespace? I don't expect my hacky way would work with helm upgrade chart.
Thanks in advance.
Output of helm version:
version.BuildInfo{Version:"v3.9.3", GitCommit:"414ff28d4029ae8c8b05d62aa06c7fe3dee2bc58", GitTreeState:"clean", GoVersion:"go1.19"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.1", GitCommit:"e4d4e1ab7cf1bf15273ef97303551b279f0920a9", GitTreeState:"clean", BuildDate:"2022-09-14T19:40:59Z", GoVersion:"go1.19.1", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.8-gke.1900", GitCommit:"79209257257c051b27df67c567755783eda93353", GitTreeState:"clean", BuildDate:"2022-07-15T09:23:51Z", GoVersion:"go1.17.11b7", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
GKE, Kind, and Minikue

The only way I can think of doing this would be to use the bitnami/kubectl image in a pre-install hook Job to kubectl label the namespace.

The only way I can think of doing this would be to use the bitnami/kubectl image in a pre-install hook Job to kubectl label the namespace.

@joejulian Yes I did try that way but no luck. Here is my Job manifest under a test foo chart (hanging forever):
# foo/templates/prehook-job.yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: label-ns
  labels:
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
  annotations:
    "helm.sh/hook": pre-install,pre-upgrade,post-install,post-upgrade
    "helm.sh/hook-delete-policy": before-hook-creation,hook-succeeded
spec:
  template:
    spec:
      containers:
      - name: labeler
        image: gcr.io/google_containers/hyperkube:v1.9.7
        command:
        - kubectl
        - label
        - --overwrite
        - ns
        - {{ .Release.Namespace }}
        - pod-security.kubernetes.io/warn=baseline
      restartPolicy: Never

The only way I can think of doing this would be to use the bitnami/kubectl image in a pre-install hook Job to kubectl label the namespace.

@joejulian I got some initial success:
$ # generate sample chart "foo"
$ helm create foo

# foo/templates/pss-clusterrole.yaml
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: pss-{{ include "foo.serviceAccountName" . }}
  namespace: {{ .Release.Namespace }}
  labels:
    {{- include "foo.labels" . | nindent 4 }}
  annotations:
    "helm.sh/hook": post-install,post-upgrade
    "helm.sh/hook-weight": "1"
    "helm.sh/hook-delete-policy": hook-succeeded
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: pss-clusterrole
  annotations:
    "helm.sh/hook": post-install,post-upgrade
    "helm.sh/hook-weight": "2"
    "helm.sh/hook-delete-policy": hook-succeeded
rules:
- apiGroups: [""] # "" indicates the core API group
  resources: ["namespaces"]
  verbs: ["get", "watch", "list", "patch", "delete", "create"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: pss-clusterrolebinding
  annotations:
    "helm.sh/hook": post-install,post-upgrade
    "helm.sh/hook-weight": "3"
    "helm.sh/hook-delete-policy": hook-succeeded
subjects:
  - kind: ServiceAccount
    name: pss-{{ include "foo.serviceAccountName" . }}
    namespace: {{ .Release.Namespace }}
roleRef:
  kind: ClusterRole
  name: pss-clusterrole
  apiGroup: rbac.authorization.k8s.io

# foo/templates/pss-job.yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: {{ include "foo.fullname" . }}
  labels:
    {{- include "foo.labels" . | nindent 4 }}
  annotations:
    "helm.sh/hook": post-install,post-upgrade
    "helm.sh/hook-weight": "4"
    "helm.sh/hook-delete-policy": hook-succeeded
  namespace: {{ .Release.Namespace }}
spec:
  template:
    spec:
      serviceAccount: pss-{{ include "foo.serviceAccountName" . }}
      serviceAccountName: pss-{{ include "foo.serviceAccountName" . }}
      terminationGracePeriodSeconds: 30
      containers:
      - name: labeler
        image: gcr.io/google_containers/hyperkube:v1.9.7
        command:
        - kubectl
        - label
        - --overwrite
        - ns
        - {{ .Release.Namespace }}
        - pod-security.kubernetes.io/warn=baseline
        - pod-security.kubernetes.io/warn-version=latest
      restartPolicy: Never

Pass some of requirements:
$ helm install foo .
NAME: foo
LAST DEPLOYED: Thu Oct 20 07:54:51 2022
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=foo,app.kubernetes.io/instance=foo" -o jsonpath="{.items[0].metadata.name}")
  export CONTAINER_PORT=$(kubectl get pod --namespace default $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
  echo "Visit http://<IP_ADDRESS>:8080 to use your application"
  kubectl --namespace default port-forward $POD_NAME 8080:$CONTAINER_PORT

$ k get ns
NAME                 STATUS   AGE
default              Active   21h
kube-node-lease      Active   21h
kube-public          Active   21h
kube-system          Active   21h
local-path-storage   Active   21h

$ k get ns default -o yaml
apiVersion: v1
kind: Namespace
metadata:
  creationTimestamp: "2022-10-19T02:44:55Z"
  labels:
    kubernetes.io/metadata.name: default
    pod-security.kubernetes.io/warn: baseline
    pod-security.kubernetes.io/warn-version: latest
  name: default
  resourceVersion: "56616"
  uid: 575dbe9d-96eb-44e2-8a57-385993cd293c
spec:
  finalizers:
  - kubernetes
status:
  phase: Active

$ helm upgrade foo .
Release "foo" has been upgraded. Happy Helming!
NAME: foo
LAST DEPLOYED: Thu Oct 20 07:55:29 2022
NAMESPACE: default
STATUS: deployed
REVISION: 2
NOTES:
1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=foo,app.kubernetes.io/instance=foo" -o jsonpath="{.items[0].metadata.name}")
  export CONTAINER_PORT=$(kubectl get pod --namespace default $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
  echo "Visit http://<IP_ADDRESS>:8080 to use your application"
  kubectl --namespace default port-forward $POD_NAME 8080:$CONTAINER_PORT

$ k get sa
NAME      SECRETS   AGE
default   0         21h
foo       0         2m18s

$ k get job
No resources found in default namespace.

$

Looks ok to me. I'd still use the bitnami container (and I do). I'm surprised the 1.9 kubectl works.


Update mythrans-bible.md

Ports 3000-4000 need to be open, it uses random ports within the range. Also added ufw commands.

@lilithium-hydride Thank you very much! Your contribution has been accepted. I hope to see more contributions from you in the future.


I couldn't create a .vsix file

npm run package

<EMAIL_ADDRESS>package
webpack --mode production --devtool hidden-source-map

[webpack-cli] Compiler starting...
[webpack-cli] Compiler is using config: '/twinny/webpack.config.js'
[webpack-cli] Compiler finished

assets by status 226 KiB [cached] 1 asset
modules by path ./node_modules/ 415 KiB
javascript modules 271 KiB 61 modules
json modules 143 KiB
./node_modules/openai/package.json 470 bytes [built] [code generated]
./node_modules/mime-db/db.json 143 KiB [built] [code generated]
modules by path ./src/*.ts 4.87 KiB
./src/extension.ts 919 bytes [built] [code generated]
./src/completion.ts 3.97 KiB [built] [code generated] [3 errors]

12 modules

ERROR in /twinny/src/completion.ts
./src/completion.ts 135:12-21
[tsl] ERROR in /twinny/src/completion.ts(135,13)
TS7053: Element implicitly has an 'any' type because expression of type '0' can't be used to index type 'CreateCompletionResponseChoicesInner'.
Property '0' does not exist on type 'CreateCompletionResponseChoicesInner'.
@ ./src/extension.ts 5:21-44
ERROR in /twinny/src/completion.ts
./src/completion.ts 136:26-31
[tsl] ERROR in /twinny/src/completion.ts(136,27)
TS2339: Property 'slice' does not exist on type 'CreateCompletionResponseChoicesInner'.
@ ./src/extension.ts 5:21-44
ERROR in /twinny/src/completion.ts
./src/completion.ts 136:42-48
[tsl] ERROR in /twinny/src/completion.ts(136,43)
TS2339: Property 'length' does not exist on type 'CreateCompletionResponseChoicesInner'.
@ ./src/extension.ts 5:21-44
3 errors have detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.
webpack 5.88.2 compiled with 3 errors in 4669 ms

Thanks for the report, it seems I am using out dated openai.d.ts I will fix it.


cli e2e testing

Conduct CLI end to end testing for the core soroban support
Sub tasks :

[x] update the Quickstart docker image with the latest core release. https://github.com/stellar/go/issues/4624
[x] Run the existing integration tests against the updated quickstart docker to see if any breaking changes were introduced. https://github.com/stellar/go/issues/4625
[ ] Use the CLI to create token https://github.com/stellar/go/issues/4627
[x] Use the CLI to deploy contract https://github.com/stellar/go/issues/4628

Use Soroban Examples, Hello world : sample from soroban-example, addi32 contract

[ ] Invoke a contract using JS https://github.com/stellar/go/issues/4629
[ ] Invoke a contract using Soroban CLI @fons
https://github.com/stellar/go/issues/4630

for anyone doing e2e tasks, the latest docker image of quickstart to use for this is:
docker pull stellar/quickstart:pr-373-soroban-dev
docker run --platform linux/amd64 --rm -it -p "8000:8000" --name stellar stellar/quickstart:pr-373-soroban-dev --standalone --enable-soroban-rpc --protocol-version 20

soroban-rpc service URL entrypoint will be reachable from the locally run container at:
http://localhost:8000/soroban/rpc
Quickstart soroban dev readme
it has latest version of Horizon and Soroban-Rpc services from soroban-xdr-next branch
it has latest soroban core version - 19.4.1-1085.fc63f3a6a.focal~soroban

I'd say let's do the token thing last. A lot of stuff in core/xdr/env has changed recently, so that will likely be broken until the final builds/releases are made.

paul, to confirm then, the abbreviated e2e flow we should be testing for now looks like:

checkout soroban-examples git repo, compile hello_world contract to wasm code
chekcout soroban-cli, build it
deploy hello-world wasm contract using soroban-cli against the soroban-rpc service published from quickstart soroban-dev image (http://localhost:8000/soroban/rpc) which is running a standalone core #4628
invoke the hello-world contract using browser(node/server-side?) javascript sendTransaction against quickstart soroban-rpc http://localhost:8000/soroban/rpc #4629
confirm the contract invocation via javascript getTransactionStatus against quickstart soroban-rpc http://localhost:8000/soroban/rpc  (#4629)

then when cli is ready, we can repeat but swap out #4/#5 to be #4630 to confirm both cli and js?


Improve environment variable docs

Description
Adding more examples.

Before submitting the PR, please make sure you do the following:

[x] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[x] Update docs in this repository according to your change
[ ] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

Alright, thanks @mcvinci !


Unable to save cohort using user data

Internal Server Error: /cohorts/save_cohort/
Traceback (most recent call last):
File "/home/vmagent/app/lib/django/core/handlers/base.py", line 111, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/vmagent/app/lib/django/contrib/auth/decorators.py", line 22, in _wrapped_view
return view_func(request, *args, **kwargs)
File "/home/vmagent/app/lib/django/utils/decorators.py", line 105, in _wrapped_view
response = view_func(request, *args, **kwargs)
File "/home/vmagent/app/cohorts/views.py", line 512, in save_cohort
items = items['items']
KeyError: 'items'

THis is potentially related to issue #186

This error is an effect on the fundamental problem of filters on data not having data returned.  An data check was added to validate the data returned on filters before cohorts are created

#186 should resolve this issue


Request for 1.0.0 alpha release

Hello! I've been using the TypeScript version of Chess.js in a side project and it's working great! Since there's not currently an NPM release for this project yet, I've connected NPM to the dev branch and I've been importing Chess.js directly like this:
import { Chess } from "chess.js/src/chess";

Recently, I decided to try and turn on the noUncheckedIndexedAccess to catch some bugs in my code, but now I'm no longer able to compile the Chess.js build.
If you could build and release an alpha version of the refactor, then I'd be able to use that build instead.
Thanks for creating such a great library!

Hi @LandonSchropp.  Sorry for the radio silence - summer has been very busy.
I've pushed up an alpha release 1.0.0-alpha.0 to npm.  Please let me know if it work for you.

Hi @jhlywa! Sorry for the slowness on my end—I missed your last message.
The build you pushed up works great. Thank you!


refactor: convert everything to typescript

🧰 Changes
Converts the entire repo to typescript with some added documentation and
exported types of all http status codes that we support.
Types showing up properly in the readme.io package when linked locally

🧬 QA & Testing

Run npm run test and verify it passes
npm link the @readme/http-status-codes package from readme repo and verify imports are property typed.

@erunion Mind publishing a new release, that I can then follow-up with a package update in the main repo?


Improve memory allocation on target method

Use Map
Cache FullPath on Skeleton

CodeFactor can be ignored seeing it's only some remark about the CPU Diagnoser in the benchmarks


Add on-chain notes to the Miden client

Currently, the client can handle only off-chain notes. We want to support on-chain notes as well. That means the user can store the full note data with the Miden Node. That way, other users can consume notes way more easily.
I am not sure what we need to change in the client (not familiar with the complete client code). Things I know are (please add):

Add a new argument to the CLI to define a note as on-chain or off-chain at note creation
Add a new argument to the CLI to define a note as on-chain or off-chain at note consumption
...

This work requires https://github.com/0xPolygonMiden/miden-base/issues/403 to be completed.

Add a new argument to the CLI to define a note as on-chain or off-chain at note creation

This can be done once we have corresponding updates done in miden-base. Specifically, we'll probably modify create_note functions in miden-lib

Add a new argument to the CLI to define a note as on-chain or off-chain at note consumption

I'm not sure this will be needed. Once an input note is in the client, it doesn't matter how it got there - so, the consumption part wouldn't change.
What would change is how syncing works. There are a couple of options here:

We could modify the sync_state endpoint to return note details for every on-chain note.
We could add another endpoint - something like get_note_details which would accept a list of note IDs and would return details for these notes.

My initial though is that approach 2 is better.
cc @hackaugusto as this will also be relevant for the node.

Both approaches would work, but 2 would leak information that we tried to hide with sync_state.

but 2 would leak information that we tried to hide with sync_state.

I think this is OK in this case as we are dealing with on-chain notes and the data there is public anyway. The only exception is encrypted notes, but maybe we handle them as a special case.

Closed by #245


Strictmode

Issue #44

@beutepa can you do a code review please?

In the Initialize-ISHServerOSUserRegion.ps1 fixed the computer name parameter to be optional.
In the example script Initialize-ISHServer.ps1 fixed the flow so it will execute Initialize-ISHServerOSUserRegion.ps1 also locally and not issue the warning


Why do we need to click arrow down key before the calendar shows up?

I tried to copy this wrapper https://github.com/airbnb/react-dates/blob/master/examples/SingleDatePickerWrapper.jsx to my app but I noticed that upon on focus, there's no calendar, it only displays when I click on arrow down button.
This is the initial interface

And then displays after arrow down

I learned that arrow key will work because of this paragraph hidden inside the component

hope you can be of any help @ljharb @majapw thanks

Hi @janjanarnaldo, what is your onFocusChange callback look like? How are you maintaining focus state? It kind of looks like that's not being properly managed.

HI @majapw it is focusing if you check the component's state.

Is the DayPickerRangeController rendering in the DOM?

tried 2 ways of callbacks
onFocusChange = ({ focused }) => this.setState({ focused }) and
onFocusChange({ focused }) {
this.setState({ focused });
} // were onFocusChange is bound to .this at constructor.

No @majapw but I can see SingleDatePickerInputController

And what version of react-dates are you using?

18.3.1 @majapw

also, after clicking arrow down which shows the calendar, the DayPickerSingleDateController as you mentioned is already mounted @majapw

Can you share your entire props configuration?

sure I'll put the entire component instead
`import React, { Component } from 'react';
import 'react-dates/initialize';
import 'react-dates/lib/css/_datepicker.css';
import moment from 'moment';
import { SingleDatePicker } from 'react-dates';
class DateSelector extends Component {
static defaultProps = {
// example props for the demo
autoFocus: false,
initialDate: null,
// input related props
id: 'date',
placeholder: 'Date',
disabled: false,
required: false,
screenReaderInputMessage: '',
showClearDate: false,
showDefaultInputIcon: false,
customInputIcon: null,
block: false,
small: false,
regular: false,
verticalSpacing: undefined,
keepFocusOnInput: false,

// calendar presentation and interaction related props
renderMonthText: null,
// orientation: HORIZONTAL_ORIENTATION,
// anchorDirection: 'right',
horizontalMargin: 0,
withPortal: false,
withFullScreenPortal: false,
// initialVisibleMonth: null,
numberOfMonths: 1,
keepOpenOnDateSelect: true,
reopenPickerOnClearDate: false,
isRTL: false,
hideKeyboardShortcutsPanel: true,

// navigation related props
navPrev: null,
navNext: null,
onPrevMonthClick() {},
onNextMonthClick() {},
onClose() {},

// day presentation and interaction related props
// renderCalendarDay: undefined,
// renderDayContents: null,
enableOutsideDays: false,
isDayBlocked: () => false,
// isOutsideRange: day => !isInclusivelyAfterDay(day, moment()),0
isDayHighlighted: () => {},

// internationalization props
monthFormat: 'MMMM YYYY',
displayFormat: () => moment.localeData().longDateFormat('L'),

}
constructor(props) {
super(props);
this.state = {
focused: props.autoFocus,
date: props.initialDate,
};
}
onDateChange = date => this.setState({ date })
onFocusChange = ({ focused }) => this.setState({ focused })
render() {
const { focused, date } = this.state;
const { autoFocus, initialDate, ...props } = this.props;

return (
  <div className="DateSelector">
    <SingleDatePicker
      {...props}
      id="date_input"
      date={date}
      focused={focused}
      onDateChange={this.onDateChange}
      onFocusChange={this.onFocusChange}
    />
  </div>
);

}
}
export default DateSelector;
`

Ugh the issue is just because of styling where overflow is hidden.  Thanks for accommodating though @majapw will close now.

Glad you figured it out!

@majapw I am experiencing a similar issue, but the fix by using appendToBody gives me the following error:
Uncaught Invariant Violation: Portal.render(): A valid React element (or null) must be returned. You may have returned undefined, an array or some other invalid object.

Versions:
"react": "^16.8.6",
"react-dates": "^20.1.0",
"react-dom": "^16.8.6",
"react-with-direction": "^1.3.0",

@majapw I am experiencing a similar issue, but the fix by using appendToBody gives me the following error:
Uncaught Invariant Violation: Portal.render(): A valid React element (or null) must be returned. You may have returned undefined, an array or some other invalid object.

Versions:
"react": "^16.8.6",
"react-dates": "^20.1.0",
"react-dom": "^16.8.6",
"react-with-direction": "^1.3.0",

@majapw Just bumping this up. Would you be able to give me some more direction into this issue?


fix: circular dependency, util.ts import intersect.ts, intersect.ts import util.ts

fix a issue when use this package

thank you didnt notice it

added in v7.0.5 thank you


Configure monitoring so that metrics show data for the whole cluster

Environment

VerneMQ Version: 1.10.2
OS: Ubuntu 18.04.3 LTS
Erlang/OTP version: Erlang/OTP 22
Cluster size/standalone: 3

allow_anonymous = off
listener.tcp.default = <IP_ADDRESS>:1883
listener.ssl.default = <IP_ADDRESS>:8883
listener.ws.default = <IP_ADDRESS>:8080
listener.wss.default = <IP_ADDRESS>:8081
listener.tcp.allowed_protocol_versions = 3,4,5
distributed_cookie = ...

plugins.vmq_diversity = on
plugins.vmq_passwd = off
plugins.vmq_acl = off
vmq_diversity.auth_postgres.enabled = on
vmq_diversity.postgres.host = ...
vmq_diversity.postgres.port = 5432
vmq_diversity.postgres.user = ...
vmq_diversity.postgres.password = ...
vmq_diversity.postgres.database = ...

nodename = VerneMQ@${IP_ADDRESS}
listener.vmq.clustering = ${IP_ADDRESS}:44053
listener.vmqs.clustering = ${IP_ADDRESS}:18884

Expected behavior
Configure VerneMQ such that the metrics includes all nodes (i.e. show data for the entire cluster).
Actual behaviour
I have read the docs for Prometheus VerneMQ. For context, I have a VerneMQ cluster with 3 nodes behind a load balancer. I want to use Prometheus to scrape VerneMQ metrics, but each request to :8888/metrics only has data for one specific node at a time.

Hi @HowellTan, thanks for your input. Yes, that's how Prometheus scraping is implemented currently (and it's likely to stay like that because otherwise, Verne nodes would have to somehow forward the scrape request. Or have all the metrics replicated & ready).

@ioolkos I have the same issue, how do you suggest monitoring a vernemq cluster with multiple replicas?
For instance if I have a swarm cluster with three nodes, then prometheus scraps metrics from only one node at a time.

@tartieret @HowellTan by scraping every node and then separate metrics by node name in Grafana. You could do an aggregated view (where cluster nodes are shown in a single view), or some form of drill-down view for each node from a general pane.
I know the Grafana thing in this repo is only very basic. I've seen people building elaborated views, but no project has given back what they built so far (maybe for the reason that it seemed too specific for a use case).

@tartieret Netdata recently also added great integration for VerneMQ. You can add multiple servers in the config file too:
https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/vernemq

I guess this is answered. Feel free to comment or reopen.

@ioolkos thanks for the info!


Output of New-MarkdownAboutHelp cannot be processed by New-ExternalHelp

Steps to reproduce

New-MarkdownAboutHelp -OutputFolder . -AboutName TestThing
New-ExternalHelp -OutputPath .\en-US .\about_TestThing.md

Expected behavior
it all works
Actual behavior
Warnings and errors (see below). I think it must want me to put in some v2 schema metadata, but I think New-MarkdownAboutHelp should have done that for me.
WARNING: [New-ExternalHelp] cannot find 'external help file' in metadata for file C:\src\DbgShell_audit\markdown_docs\about_TestThing.md
WARNING: [New-ExternalHelp] .\en-US\rename-me-help.xml would be used
PlatyPS schema version 1.0.0 is deprecated and not supported anymore. Please install platyPS 0.7.6 and migrate to the supported version.
At C:\Users\danthom\Documents\WindowsPowerShell\Modules\platyPS\0.8.1\platyPS.psm1:1409 char:9
+         throw "PlatyPS schema version 1.0.0 is deprecated and not sup ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (PlatyPS schema ...ported version.:String) [], RuntimeException
    + FullyQualifiedErrorId : PlatyPS schema version 1.0.0 is deprecated and not supported anymore. Please install platyPS 0.7.6 and migrate to the supported version.

Environment data

v0.8.1

Hmm... so I tried putting in a metadata block. That got rid of the "schema version 1.0.0. is deprecated" error, and allowed it to produce output, but then there were a bunch more errors. The "external help file" metadata item seems to be ignored, but if I omit it entirely, I still get the warnings about not being able to find it and "ima use rename-me-help.xml instead".
So... I guess "about" help is not really fully implemented, or what?

I gave a full path and got expected behavior (I think – am still new to PlatyPS).. maybe we just need to update docs?
Try something like:    New-ExternalHelp -OutputPath .\en-US\TestThing.xml .\about_TestThing.md
And if that xml already exists if you are running it multiple times you can use -Force.
From: Dan Thompson<EMAIL_ADDRESS>Sent: Tuesday, August 8, 2017 8:16 PM
To: PowerShell/platyPS<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [PowerShell/platyPS] Output of New-MarkdownAboutHelp cannot be processed by New-ExternalHelp (#290)
Hmm... so I tried putting in a metadata block. That got rid of the "schema version 1.0.0. is deprecated" error, and allowed it to produce output, but then there were a bunch more errors. The "external help file" metadata item seems to be ignored, but if I omit it entirely, I still get the warnings about not being able to find it and "ima use rename-me-help.xml instead".
So... I guess "about" help is not really fully implemented, or what?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPowerShell%2FplatyPS%2Fissues%2F290%23issuecomment-321140990&data=02|01|ken.withee%40microsoft.com|88a3812907624191bbf508d4ded4e516|72f988bf86f141af91ab2d7cd011db47|1|0|636378453339480800&sdata=i%2Bu65W9IwYaeL7UiFNidlWYdL6cyLv5SKPR6%2F%2FhMtiA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAadW2AFcu8Mi27fVHRFzbOItRFIOepixks5sWSRTgaJpZM4OxicY&data=02|01|ken.withee%40microsoft.com|88a3812907624191bbf508d4ded4e516|72f988bf86f141af91ab2d7cd011db47|1|0|636378453339480800&sdata=IyFlQwS2j%2BOjEq2HHYCVUPzi4%2FUbQ5U9WLrPfSnd3Hw%3D&reserved=0.

Giving a full path does not help at all... are you using the output of New-MarkdownAboutIHelp?

Yeah, this AboutFiles piece can use some refactoring...
Try to poke around with https://github.com/PowerShell/platyPS/blob/master/src/platyPS/platyPS.psm1#L779
I bet the detection logic just doesn't recognize this md files as about topic files.
The schema stuff should be applicable only to the cmdlet documentation, not to about.


Allow publishing snapshot

For development purposes its sometimes useful to have easy access to snapshots of this library. Sonatype allows publishing snapshots which are then accessible at
        maven { url "https://oss.sonatype.org/content/repositories/snapshots/" }

As a side node: this could be useful for other libraries as well. We should consider to share certain gradle files among projects to get certain features automatically. Though we need to consider the risks as well if we do that.


Add _site dir to .gitignore file

What is this PR for?
When we execute Jekyll to build Zeppelin docs, _site directory is generated automatically. So I added _site to .gitignore file.
What type of PR is it?
Improvement
Todos

[x] - Add _site dir to .gitignore file

What is the Jira issue?
No
How should this be tested?

Execute Jekyll following as in here
Before adding _site to .gitignore, you can see that git is tracking _site directory.
After applying this PR, git doesn't track this directory anymore.

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

👍  merging if there is no more discussion


Why not compatibility with async/await and promises?

Hi,
I (and I'm sure other people too) am wondering why you couldn't rely on existing language features like:

async/await and Promises
async generators
AsyncLocalStorage (also coming to web)

Since these are built-in language features it just seems like it would be more idiomatic, and easier to integrate with existing code, if you based your framework off them.  But I'm sure you have very good reasons — I just think it'd be interesting to see the rationale/discussion around those somewhere (apologies if you already have this somewhere or if you think it's obvious).
Perhaps it'd be possible to "hook into" Effection for code bases that still use exceptions and promises?
(I think systems such as Twisted Python and Redux Sagas (JS), which are based on generators, become a bit far removed from the idiomatic way to program in those languages.)

Charles, thank you for the thorough response!  I completely agree structured concurrency is worthwhile, and Effection is a very practical way to do that.  I also agree that it's really unfortunate that supporting async seems to cause a lot of accidental complexity in the API designs.
While your approach is practical, I'm not sure I agree it's the most idiomatic possible — or otherwise why do we even have async/await when generators are enough?  As you say, other languages have better support for structured concurrency, so it's really a shame that Javascript falls short.
I was wondering if you had any thoughts on existing cancelable promises frameworks?  See comparison table for CPromise, Bluebird.js, p-cancelable — they claim to:

Make Promises cancelable without extra instrumentation — so presumably the lifetime issue you mention above can be resolved?
Support cleanup handlers — is this the only reason you want/need manual resumability?

Ideally there would be a TC39 proposal to better support (at least the primitives required) for structured concurrency, but even that would probably best be supported by some prior work or a proof of concept of sorts.  If you had a magic wand and controlled TC39, what would you do? 😀

In answer to your question of why async/await at all, I don't think there was an appreciation of the need for a general "effect" mechanism in a language. Remember all of this API design predates the dawn of the FP epoch of JavaScript, and at that time the notion that a language needed to have a general "effects" mechanism wasn't really on the radar. It certainly wasn't on mine until around 2015 or so, well after these language features had cooled into stone. I don't think, for example, that I would be satisfied with just async/await that didn't let me also read things from the context. Using the full power of delimited continuations, implementing an Algebraic Effect system was a snap https://discord.com/channels/700803887132704931/1133802900620070912/1134147067627982988
Why have a separate abstraction for that? But again, algebraic effects weren't really on most people's radar until React hooks came out in what, 2018?
The biggest problem I have with putting promises at the center of the solution is that the big idea around structured concurrency is the concept of lexical scope, and enforcing the lifetimes of processes based on it. Cancellation is the way to enforce that, but it is not something that you should really ever do explicitly. So for example, Effection tasks have a halt() method, but I find myself calling it very seldom, and whenever I do, I think "How could I have leaned on lexical scope to have solved this problem?" So solutions that focus on cancellation as an end and not a means are not optimally framed (in my book).  As for the specific promise implementations go, they need you to express all your asynchrony programmatically in order to benefit because whenever you use an async function, the runtime is going to create a non-cancelable promise of unknown provenance. I don't see how they would compose with something like say a 3rd party library that used plain native async functions.
So what would I do with a magic TC39 wand? I guess it would be to make an async function behave more like a delimited continuation. First my biggest beefs with async functions:

Every resolution must happen on the next tick of the run loop which means that other pieces of code can run. This
then/catch/finally callbacks drop context and so you have to have checks like "isDestroyed" etc...

So what would I do if I could wave my magic wand? Well this is a really rough sketch, but here goes.

new Promise() can only be called inside an async function, and whenever that async function exits, for whatever reason, the promise's finally handlers are invoked, but any then or catch handlers are silently dropped if they have not been invoked already.
An async function can neither resolve or reject, or throw until all promises created in such a fashion have had all of their finally handlers run to completion (and because finally handlers can themselves return promises, those etc..).
async functions return a Task object which extends Promise but also has a cancel() method. In addition to this, The Task object is an async iterable which returns the value of each await point, and by calling next, you can directly provide the result of
Promises are allowed to continue an async function from an await point in the same tick of the run loop. Otherwise, you have difficult things to track down like https://stackoverflow.com/questions/27081390/javascript-promises-and-race-conditions ( Example is in CoffeeScript, but the same principle applies.)

It's really cool that Effection provides primitives for both structured concurrency and effects, and I was perhaps purely focusing on the structured concurrency aspect.  To be honest, while I have done a little bit of FP, I wasn't planning to go pure-FP with my ts/js code, and so didn't have the ambition to look for an effects mechanisms/system for Javascript.  But I guess it's possible to look at the structured concurrency aspect in isolation?
My experience with this goes back to Trio/Curio (Python) — this video by Nat Smith was en eye-opener — but I've been looking at languages like Swift and Kotlin with envy as the languages started to support structured concurrency natively.
I was looking for a pragmatic way to improve the promises-hell that is the current way of JS programming, and I thought having taskgroups/nurseries and the like would be a good way to tame that.  I realize it won't be a zero-intervention solution since, as you say, async function will create a regular Promise, but I was hoping there would be a way to do structured concurrency with async/await.
Given the dynamic nature of Javascript, wouldn't this be possible to manually wrap async functions to create Tasks (even use decorators if/when those become available for regular functions), and provide a taskgroup primitive — and would that be enough?  Likewise, of the items in your magic wand wishlist, how many could be done with helpers/adapters and conventions (or linter rules/ typescript plugins) as a proof-of-concept — and if they prove the value, why not pitch it to TC39? :)

Hmm.. you might be able to cobble together a structured concurrency solution that was based on async/await. Rather than using generator functions to express your program, you could use async generator functions to express you programs, and then wrap anything you await in a special function to make sure you can get yourself "unstuck" from the await expression.
import { awaitable } from "structured concurrency";

let task = run(async function * () {
  await awaitable(new Promise(resolve => setTimeout(1000, resolve)));
});

awaitable() would read the implicit abort signal off the context, and then race the promise you're awaiting against a promise that resolves with that signal.

I've documented why async/await as it stands is not really suitable for structured concurrency. https://frontside.com/blog/2023-12-11-await-event-horizon/
I hope that if the idea gains enough traction that we could submit a proposal to TC39 down the road to "fix" async/await. But I don't see any proposal getting very far unless there is a demand for the idea.

Maybe submit the blog post to their discoure forums? https://es.discourse.group/


Max length on main mapcode pieces?

I need to figure out if there's a max length on the main mapcode pieces.
Example: ZSR and 3J in Hawaii ZSR.3J.
From looking at a bunch of codes I would guess it's minimum 2 and maximum 5. But can't be sure until I see some documentation on it.

http://www.mapcode.com/mapcode_documentation.doc. Couldn't find anything about the max length of the pieces though.

Yeah, I've previously read through that, but didn't find anything either. I've tried emailing them. Let's see if we can get an answer.

Alright, got a reply with what's needed an more. Looks like there are more things we can implement to make it even stricter: https://dl.dropboxusercontent.com/u/71884/Length and format of mapcodes.pdf


ImportError

Hi,
I am on Windows 10 with Cuda 10.2, ZED SDK 3.1.2 and python 3.8.1. I have installed the pyzed API and am able to import pyzed but when I attempt to import pyzed.sl I get the error:
ImportError: DLL load failed while importing sl: The specified module could not be found.
I have checked the module folder and see the sl.pyd file.
Has anyone else experience the same issue and how can I fix it?
Thanks

Hi I have the same exact error message. I have been banging my head trying to solve this...

Same issue here, I tried this solution and it did not work https://github.com/stereolabs/zed-python-api/issues/78 in manually building/installing the pyzed api.  As well as rolling back to CUDA 10 and ZED sdk for CUDA 10 based on this link https://github.com/stereolabs/zed-python-api/issues/69 and I still cannot import pyzed.sl in python 3.8 64bit.  I have been trying to solve on Windows 10 for the last 5 hours with no luck.
Traceback (most recent call last):   File ".\hello_zed.py", line 21, in <module>     import pyzed.sl as sl ImportError: DLL load failed while importing sl: The specified module could not be found.

Same issue.
@nesnes, @adujardin, @obraun-sl, @P-yver any suggestions?

same issue here too.

@noelquah Same with me, it worked first try with my desktop, but I keep getting the dll import error on my laptop. Laptop is using MX150 GPU, desktop is GTX 1070. All software settings (CUDA, ZED SDK, Python) were the same. Maybe there is a bug with the Python API with laptops? That is my only guess, after trying lots of different software combinations to try to get this to work with my laptop.

@mjlyons7 I actually fixed the error on my laptop but i did a couple of things and I can't pinpoint the actual cause.

I downgraded my Python from 3.8 to 3.6. I noticed that it was the difference between my 2 devices. This solution did stop this error from occurring but then another error came up saying that pyzed was not found (no longer sl).

I made a silly mistake by linking my virtual environment to my IDE - at the time, my VE's python had no pyzed installed. I linked it to the installed version and then it worked fine.

I don't know which item precedes the other, but maybe you could give these solutions a go.

Same problem here and @noelquah - installing Python 3.6 for me resolved the issue.
Does not work:
Python 3.8.5 (tags/v3.8.5:580fbb0, Jul 20 2020, 15:57:54) [MSC v.1924 64 bit (AMD64)] on win32
Works fine:
Python 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:54:40) [MSC v.1900 64 bit (AMD64)] on win32

I confirm that the Python APIs are not working with Python 3.8. When will this be fixed?

I solved the issue by copying all the dlls from
C:\Program Files (x86)\ZED SDK\bin
into Python's Script folder

It can‘t  work with Python3.9.0.I get the error:
ImportError: DLL load failed while importing sl: The specified module could not be found.

@xu-fire try the solution I suggested in my latest reply, it should work

Running on Windows. 10 , I have Cuda 11.1 and Python 3.8.6 , no luck importing pyzed.sl. Any help is much appreciated.

Running on Windows. 10 , I have Cuda 11.1 and Python 3.8.6 , no luck importing pyzed.sl. Any help is much appreciated.

Hmm, I am also encountering this issue with Python 3.8.6, ZED SDK 3.3 and CUDA 11.1 on Windows. I tried to copy the dlls in C:\Program Files (x86)\ZED SDK\bin to my venvs script folder as @A7ocin suggested, but that did not seem to fix my issue. Maybe I am missing something.

Hmm, I am also encountering this issue with Python 3.8.6, ZED SDK 3.3 and CUDA 11.1 on Windows. I tried to copy the dlls in C:\Program Files (x86)\ZED SDK\bin to my venvs script folder as @A7ocin suggested, but that did not seem to fix my issue. Maybe I am missing something.

Hi,
im on zed sdk 3.4, cuda 11.1, python 3.9 . im neither able to install the api directly by running the get_python_api file nor able to install it manually properly. When I try to install/build api manually from the source file, i get the "Unable to find vcvarsall.bat" error. Please can someone help me with the issue?
Regards

Hi @kunalkumthekar,
There might be some issues with Python versions > 3.8.
If it is possible for you, could you try reinstalling the API with a version < 3.8 ?

@qt-truong
Thank you for the quick response. Yes I did try running the entire procedure on python 3.6 as suggested above. Still no luck. Is the api installation procedure going wrong for me? Can you please tell me how you resolved this issue?

@kunalkumthekar it seems that you have an issue with your C++ compiler.
Can you try following the suggestions on this page and see if that solved your problem ?

@qt-truong Hey thank you for the help, I was able to solve the issue by updating Visual Studio to a newer version. Also, I had issues with the python version 3.9 , 3.8 so I downgraded it to 3.6 as suggested by you and others.
Regards!

I can confirm the error
Traceback (most recent call last):   File "C:\Program Files (x86)\ZED SDK\samples\svo recording\playback\python\read_svo.py", line 26, in <module>     import pyzed.sl as sl ImportError: DLL load failed while importing sl: Das angegebene Modul wurde nicht gefunden.
when running
python "C:\Program Files (x86)\ZED SDK\samples\svo recording\playback\python\read_svo.py" {FILEPATH_TO_MY_SVO_RECORDING}\HD1080_SN26393711_03-53-17.svo
on the following system: Windows 10, Python 3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:37:02) [MSC v.1924 64 bit (AMD64)] on win32
Thanks to @EliVerbrugge and @A7ocin I have copied the two DLL files "sl_ai64.dll" and "sl_zed64.dll" from the path "C:\Program Files (x86)\ZED SDK\bin" to the location at "C:\Program Files\Python38\Lib\site-packages\pyzed". After this has been done, reading the SVO file and displaying it using OpenCV works fine.
How can we contribute to fix this issue?
Kind regards,
Adam

Hmm, I am also encountering this issue with Python 3.8.6, ZED SDK 3.3 and CUDA 11.1 on Windows. I tried to copy the dlls in C:\Program Files (x86)\ZED SDK\bin to my venvs script folder as @A7ocin suggested, but that did not seem to fix my issue. Maybe I am missing something.
EDIT: I resolved this issue by copying the dlls in the bin folder to the Python\Lib\site-packages\pyzed folder. Thanks @A7ocin.

run python -m site locate the path and copy from C:\Program Files (x86)\ZED SDK\bin to site-packages\pyzed solved the issue.
im using python  3.8.9

Indeed this behavior can append with various python version (in my case it works with 3.9 but I get the error with 3.10).
The solution pointed multipled times to copy the ZED SDK DLL into the python directory is the best, as mentionned

I use conda, and this Python Path can still help it work.
Thanks.

I am using ZED SDK 3.6.5 with Python 3.10.2 and CUDA 11.5
Even after copying the dlls mentioned from BIN folder to pyzed site-packages, the issue is not being resolved.
Someone please help to resolve the issue

@hkravn
There is an issue that identical with yours confusing me.
I am also using Python 3.10.2.
I think this issue perhaps has to do with the version of Python.

@xu-fire
Thanks for your useful recommendation.
What's more, I found that reinstall ZED SDK also works within Python 3.10.2.

Hi,
I have tried SDK 4.0 with Python 3.8.6 and could not get rid of this error despite copying the DLL files. Would someone be able to help me resolve this? Thanks in advance!

@ShanMallinathan
I have tried to reinstall the SDK 3.8 with Python 3.10.2, instead of SDK 4.0.
I suggest you lower the version of SDK. This method can resolve the annoying question.
Hope this advice is useful to you！

Thanks @akawincent
I am not too sure why that did not work for me. But tried to install it in my Linux and it works without any problem

Thanks @akawincent I am not too sure why that did not work for me. But tried to install it in my Linux and it works without any problem

Perhaps something went wrong when you ran 'get_python_api.py'.

I solved the issue by copying all the dlls from C:\Program Files (x86)\ZED SDK\bin into Python's Script folder

Bro where is the "Python Script Folder"??

I solved the issue by copying all the dlls from C:\Program Files (x86)\ZED SDK\bin into Python's Script folder

Worked for me as well, using miniconda.
Python 3.9
ZED SDK 4.0.1
CUDA 11.8
Windows 11
I just copied all .dll files from C:\Program Files (x86)\ZED SDK\bin to
1 - C:\Users\user_name.conda\envs\zed\Lib\site-packages\pyzed
2 - C:\Users\user_name.conda\envs\zed\Lib\site-packages


Replace GitHub protected cached images in README files with their original uncached versions

Fixes #3339
See https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/issues/3339#issuecomment-2312379110 for more information on the fix.

I'll deploy this asap.


Us076 - Amend Variable event dates

Validation for editing non mandatory event dates

 US076: Amend Variable Event Dates []

Shouldn't go in until the design work on scheduling has been done.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f7f8bf2). Click here to learn what that means.
The diff coverage is 83.33%.

@@            Coverage Diff            @@
##             master      #50   +/-   ##
=========================================
  Coverage          ?   55.04%
=========================================
  Files             ?       34
  Lines             ?     1250
  Branches          ?      146
=========================================
  Hits              ?      688
  Misses            ?      522
  Partials          ?       40

Impacted Files
Coverage Δ

...onse/collection/exercise/service/EventService.java
100% <100%> (ø)

...llection/exercise/service/impl/EventValidator.java
84.9% <80.48%> (ø)

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 f7f8bf2...c4dcf4d. Read the comment docs.

NOT TO BE MERGED, THIS CHANGE DOESN'T AFFECT THE ACTUAL DATES WHICH GOVERN THE SYSTEM.


invite: Use handlebar template for invite-user overlay.

Fixes a part of #18794.

@timabbott this is ready for review

Merged, thanks @sahil839!


Update Tutorial.fsx

Changed slash in path specification for compatibility with Mac and Linux

Thank you very much sir!


$sample stage does not work as expected

According to the following table $sample stage in the aggregation pipeline is supported.
https://docs.microsoft.com/en-us/azure/cosmos-db/mongodb/feature-support-42#aggregation-stages
According to the MongoDb's 4.2 document: Randomly selects the specified number of documents from the input documents.
https://www.mongodb.com/docs/v4.2/reference/operator/aggregation/sample/
But the following query returns the same document every time:
db.mycollection.aggregate([{ $sample: { size: 1 } }])
$sample is the first stage of the pipeline. => yes
N is less than 5% of the total documents in the collection. => yes
The collection contains more than 100 documents. => yes

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: af11d879-8fde-3113-05b4-e59ae0f75b64
Version Independent ID: 66dbaf2e-4d6d-9e8f-0355-b13af1cc7872
Content: 4.2 server version supported features and syntax in Azure Cosmos DB API for MongoDB
Content Source: articles/cosmos-db/mongodb/feature-support-42.md
Service: cosmos-db
Sub-service: cosmosdb-mongo
GitHub Login: @gahl-levy
Microsoft Alias: gahllevy

@fkucuk Thank you for your feedback. We are reviewing this and will get back shortly.

@fkucuk, I have been testing this and can confirm that I'm seeing the same behavior. From my understanding, the $sample stage should work as it's documented in the 4.2 docs. From a Docs perspective, there's really not much we can do as it's already documented as a supported feature.
I recommend that you file a ticket with [Azure Cosmos DB Q&A}(https://learn.microsoft.com/en-us/answers/topics/azure-cosmos-db.html) so the product team can be made aware that there's a bug in this particular stage and implement a fix.
I'm sorry for the wait, it took me awhile to figure out the new mongo shell and to get a sample setup to validate that this was indeed returning the same "random" record.
#please-close


hardsuit/firesuit cleanup

-standardized low pressure resistance band
-standardized component layout
-removed heat resistance from most hardsuits, nerfed heat resistance on remaining hardsuits
-buffed firesuits heat+cold resistance so theyre more usable in space and gave firesuits better temp coefficient. atmos firesuit is spaceproof again. removed armor from firesuits helmets but gave them good temp protection coefficients.
-both salvage hardsuits have higher rad resist than before, salvage hardsuit was renamed to mining hardsuit to prevent confusion with spationaut, mining hardsuit buffed.
-blood-red hardsuit has now been equalized at half damage to everything.
-nerfed warden hardsuit (it had no slowdown?).
-RD suit is now 50 size
-jugsuit has been reworked a tiny bit, now more defensive to lasers to give it a niche and also a bit faster
-all hardsuits speeds have been standardized into a band so some are slightly faster/some are slightly slower. wont be too noticeable in gameplay.
-rounded most armor values of .05 to what made the most sense to make balancing easier
🆑

tweak: Hardsuit + Firesuit Rebalancingening.

why the juggernaut suit nerf
it's not a great pick already due to stuns being able to shut it down easily
shouldn't the laser shield be the thing that's designed for countering lasers?

mfs see a change from 0.2 to 0.3 and think its crazy

mfs see a change from 0.2 to 0.3 and think its crazy

Because it IS a big difference, it means they will take 50% more damage from blunt/slash/pierce compared to before, so the current 30 .30 rifle bullets to go crit becomes 20 .30 rifle bullets to go crit.

thats not how the math works

thats not how the math works

17x 0.2 = 3.4
100/3.4 = 29.4 so 30 bullets
17x0.3 = 5.1
100/5.1 = 19.6 so 20 bullets

thats not how the math works

10 x 0.2 is 2
10 x 0.3 is 3
3 is 50 percent more than 2
It is tho

thats not how the math works

.30 rifle bullet deals 17 pierce damage and it takes 100 damage for someone to go crit. Previous pierce multiplier was 0.2: 17 x 0.2 = 3.4 received damage. 100 / 3.4 = 29.4 bullets needed to kill. Can't shoot half bullets so round up to 30 bullets before someone is crit.
New pierce multiplier is 0.3: 17 x 0.3 = 5.1 received damage per bullet. 100 / 5.1 = 19.6 bullets needed to kill. Can't shoot half bullets so round up to 20 bullets before someone is crit.
The atmos fire suit now also has around the same resistance against being on fire as the captain's carapace, since most of the damage comes from the fire stacks and not the temperature. Someone only wearing the new iteration of the firesuit, after using the ignition smite on them, goes crit after 40 seconds while a captain only wearing his carapace goes crit after 35 seconds. With the previous iteration of the firesuit it takes 2 minutes and 15 seconds for someone to die from being on fire, which is around 3.33 times as long since 0.5(new modifier)/0.15(old modifier) = 3.33.

jugsuit was changed because its resist overall was too high and i put it more into laser niche, firesuits heat resist was dropped because we do not want heat resist on things since they make lasers in effective. thats why i gave them higher temp coefficients than before. if you are on fire just use an extinguisher or roll around. if someone is on fire for 40+ seconds they should not be alive

jugsuit was changed because its resist overall was too high and i put it more into laser niche

The laser niche does not exists because lasers already have bad dps with their low firerate, and spending 13 TC to be stronger against a weapon that 90% of the time only the captain uses while at the same time slowing you down so you can't catch him and are an easy target seems like a waste of TC.

With these current stats it should at the highest cost 8TC like the normal blood-red, and even then people won't buy it because speed is that important.
I see you have also nerfed the jugsuit already 2 months ago in #16768 making it's pierce modifier 0.2 instead of 0.1 and it's heat resistance 0.5 instead of 0.1.
So now you turn back it's heat resist to 0.2 and reduce the pierce even further to 0.3 making it now 3x less effective as 2 months ago against bullets, in exchange for a heat resist worse than it already had back then.
But I haven't seen anyone even use the jugsuit since then and also never heard complaints about it being too strong(nobody thinks it was worth it even before the nerf), so what are these balancing decisions based on?
Also calling a 50% brute effectiveness reduction and a 150% heat effectiveness increase as "jugsuit has been reworked a tiny bit" is also a bit of and understatement, it's like doubling sec armor and then saying you "lightly tweaked" it while it's a major balance change.

rounded most armor values of .05 to what made the most sense to make balancing easier

I also don't see the point in this since a lot of 0.05 values in the brute and burn category are based around breakpoints, randomly rounding them up or down means a lot of these suits will survive 1 shot less or more and I don't see how it makes balancing easier.
For example if that's from 7 shots to crit to 6 shots to crit it means the tiny 0.05 value change made that suit 14% less effective against that damage type, while if it's the other way around the suit is suddenly 16.6% more effective at winning a confrontation.

firesuits heat resist was dropped because we do not want heat resist on things since they make lasers in effective. thats why i gave them higher temp coefficients than before. if you are on fire just use an extinguisher or roll around. if someone is on fire for 40+ seconds they should not be alive

I can understand the laser part, but it still feels a bit weird to see someone wearing a firesuit still die pretty fast to the only thing it's supposed to protect against, the atmos firesuit now also has the same resistance against fire as the normal one making it's appearance and a 0.1 sprint multiplier the only difference.
Nothing in the game besides a cold environment currently does cold damage so I don't see how adding cold resistance would change it's performance in any way, the previous temperature coefficient already made you not take cold damage even at absolute  0.
By the time you started taking high temperature damage the pressure would already be so high that you would die of that and not the temperature, so the new increased temp coefficient also doesn't affect the fire suit performance at all.

if you are on fire just use an extinguisher

last time i checked these dont work when trying to extinguish yourself

a. i originally created and implemented the jug suit i am well aware of its purpose
b. laser niche does not exist due to abundance of heat resist on everything and lack of lasers overall that has been addressed by this pr by removing heat resist from most things and me mapping in more lasers on every vault. this is me flexing the suit into a role i am intentionally trying to create
c. the change is like a 5 second webedit change if it needs to be changed. i pr things to put them into the game to observe and gather data on how it plays it
d. the atmos firesuit is different than the normal one by being space proof now again, i originally implemented the atmos firesuit and am well aware of its use case. removing the heat protect on them is to see their performance and efficacy as not being laser proof body shields
you dont have to write paragraphs upon paragraphs at me in a pr because youre mad about my armor tweaks. if you have a horrific problem with these just bring it up in discord.

also i see now the last post i did was a bit aggressive that was not the intention, im just telling you i have always balanced and implemented this stuff by a throw shit at the wall and see what sticks metric. the changes are thought about but more meant to be observed in game due to the large amount of data collecting i do around this stuff. discussing with me on discord about balance is the best option for shit like this

you dont have to write paragraphs upon paragraphs at me in a pr because youre mad about my armor tweaks. if you have a horrific problem with these just bring it up in discord.

I tried to be constructive by adding data to my arguments instead of saying "me no like change" since not giving any got me a 6 word sentence dismissal telling me I was wrong.
With github not really being a fast way of communication I try to put all of it in a single message, in no way is it an indication of me "being mad" about your PR, I just wanted to start a discussion about it.

also i see now the last post i did was a bit aggressive that was not the intention, im just telling you i have always balanced and implemented this stuff by a throw shit at the wall and see what sticks metric. the changes are thought about but more meant to be observed in game due to the large amount of data collecting i do around this stuff. discussing with me on discord about balance is the best option for shit like this

To me randomly starting a discussion with someone on the discord about a PR they did gives a bigger "being mad about the PR feeling" than leaving a comment on said PR.

you dont have to write paragraphs upon paragraphs at me in a pr because youre mad about my armor tweaks. if you have a horrific problem with these just bring it up in discord.

I tried to be constructive by adding data to my arguments instead of saying "me no like change" since not giving any got me a 6 word sentence dismissal telling me I was wrong. With github not really being a fast way of communication I try to put all of it in a single message, in no way is it an indication of me "being mad" about your PR, I just wanted to start a discussion about it.

also i see now the last post i did was a bit aggressive that was not the intention, im just telling you i have always balanced and implemented this stuff by a throw shit at the wall and see what sticks metric. the changes are thought about but more meant to be observed in game due to the large amount of data collecting i do around this stuff. discussing with me on discord about balance is the best option for shit like this

To me randomly starting a discussion with someone on the discord about a PR they did gives a bigger "being mad about the PR feeling" than leaving a comment on said PR, which is why I opted on putting my thoughts here instead of on the discord.

nah im just horrific at reading tone over text i appreciate the feedback

nah im just horrific at reading tone over text i appreciate the feedback

After rereading my message I can see how some parts can be interpreted in the wrong way depending on how you read it, me just listing things I didn't agree on could also be seen as me ranting(which was not the case), so it's also my fault for not setting a clear tone and sounding too negative about your PR.
Thanks for reading my feedback, I'll try to make a smaller wall of text the next time I give some.


Hermes debugger can't connect in Windows 10/11

Edit By Maintainer: Please see the upstream Hermes + Windows Issue If you are running into this bug, please include your Expo SDK version (which tells us what React Native version you are using) and include your Podfile from running expo prebuild so that we can provide additional information to the Flipper team. :heart:
(Original report below)

I'm curious if anyone has gotten the Hermes plugin to work.
React DevTools works great but I get this when trying to pull up Hermes (which our app is using).

And this is all that's logged.

Is the Hermes plugin even expected to work?
Thanks!

If you're on windows, it looks a lot like https://github.com/facebook/flipper/issues/1520. Can you try launching with your host in localhost mode? expo start --host localhost?
If you're not in Windows, can you pass along the RN version and your plugin config?

Hi @jakobo. Thanks for the help!
Not sure if I got closer or further away. 😀
Yes, I'm on Windows.
I launched expo start --host localhost with my physical Android phone connected to the computer with USB Debugging enabled.
Flipper now shows the app & phone correctly but none of the plugins enable and I get more items in the log.

The RSockets warning particularly sticks out as websockets seems to be most peoples issue in the thread you linked.

P.S. - What hardware setup do you use? If you're using Mac and an iPhone I can switch over to that to test. I'd love to get Windows debugging working but I'd like get this memory leak in the app debugged even more. 😝
I recently got a 16' Macbook M1 Pro to play with but keep coming back to my windows machine because of the OLED display. 😀

My current setup is Windows 10 + WSL, with Android Emulator and iOS Device (SDK 44). However, I'm not currently running Hermes. This is most likely an issue with networking to WSL and networking at this point. I did a writeup about the networking woes here: https://codedrift.com/thunked/running-expo-in-windows-subsystem-for-linux-wsl2
The tl;dr of the piece is go get WSLHostPatcher https://github.com/CzBiX/WSLHostPatcher which will allow your WSL instances to listen to the parent host IP. You can then launch with expo start --host <IP_ADDRESS> to listen on all interfaces.

Same problem here, when using --localhost the only difference is that the following screen appears but the error persists

package.json
"expo": "^44.0.6",
"expo-community-flipper": "^44.0.1",
"react-devtools-core": "^4.23.0",
"react-native-flipper": "^0.137.0",

environment
Windows 10 Pro 19043.1526
Flipper Version 0.137.0

@gloredo
Yeah, I've given up at this point. I'm stuck with console logs for now.

Getting some more bandwidth to dig into what's going on here. Do you mind sharing the Podfile (with redactions if needed) generated in ios/ when you run expo build? All the plugin does is modify the Podfile which shouldn't cause an issue with Hermes.
Specifically, we should see:

:hermes_enabled => true which was set by expo with Hermes enabled
# Flipper support successfully added via expo config plugin which are lines added by this plugin

If we have those lines, then we should see if v8 can connect to Hermes outside of Flipper. Instructions. If we can connect using Chrome, then it is likely something about our Podfile setup that's needed for WSL compatibility. If we can't connect, then it's very likely a networking issue caused by WSL running in a NAT instead of a proper bridged network.

That's helpful information! Since all we're doing is modifying the Podfile, I think trying to connect the chrome debugger to hermes will be a good next step as it takes Flipper out of the picture completely and we can figure out if this is a windows networking issue or a Flipper/RN issue.

Hi, I have the same issue.
I on Win 10 Pro, Android simulator, Expo 44, Flipper client 140.
In Chrome I have this:

If I select any of them, it opens the DevTools but I get this error in the console:

DevTools failed to load source map

Something is working though, because if I pause the debugger the application stay frozen until I resume script execution.

@obasille I believe that's unrelated. The error in console is probably because in Chrome you've got automatic sourcemaps turned on. (Developer Tools => Settings => Sources => (uncheck) Enable JavaScript Sourcemaps. For the thread, how are you starting your expo app? And are you passing --host <IP_ADDRESS> as an argument?

Thanks! I'm running with expo run:android
I'm not sure I understand about  --host <IP_ADDRESS>, are you talking about starting Chrome with this argument? (it doesn't seem to a valid argument for expo run and expo start).

Sorry, the -- host <IP_ADDRESS> is a next.js issue (pulled from my wrong package.json) but stems from the same networking error. Windows isn't always good about forwarding everything along to WSL for the linux-on-windows crowd, and it seems to be equally bad with . Here's what I'd recommend. (I'll also update previous threads for newcomers to point to this comment)
WSL Users
You need to install and run WSLHostPatcher, as Windows is awful at forwarding everything along to the WSL instance. This app uses the Windows Detours framework to enable WSL listening on <IP_ADDRESS> (the everything interface). You can also manually forward things with network scripts, but it's a massive headache.
The majority of connection problems related to WSL come from expo (and react-native) binding to the local IP. When using localhost, it's unreachable from windows. When using lan, it binds to the wrong side of the NAT bridge that WSL uses. HostPatcher lets WSL use the system's localhost, allowing --host localhost to work as expected during expo start.
Non WSL Windows Users
There appears to be a few related issues for Flipper in Windows 10 and 11, which I've linked below for visibility.

https://github.com/facebook/flipper/issues/1520 using --host localhost to force an IP4 websocket URL
https://github.com/facebook/flipper/issues/3433 open issue, similar to the problem we're discussing here
https://github.com/facebook/flipper/issues/1291#issuecomment-789756412 (expo does not expose --host <IP_ADDRESS> for the react native bundler, but we can still look at http://localhost:8081/json and verify webSocketDebuggerUrl is a reachable URL

If we've exhausted these, we should either open or 👍🏻 a related issue in the Flipper repository. I'm also happy to modify the README about potential issues when using Win 10/11.

Thank you @jakobo!

Thank you @jakobo!

were you able to make it work on windows?

Nope (without using WSL)

Also not connecting on:

Mac
SDK 44
Hermes enabled
iOS simulator

@mitramejia do you mind sharing your Podfile after running expo prebuild locally? Doing so will help me understand how Flipper is being configured on your system and identify if this is a Flipper issue or an expo plugin issue. Thanks.

Same issue on Windows 7/SDK 45/Android.

@Slapbox, as mentioned above, can you share your Podfile after running expo prebuild locally? Right now, we need to figure out if this is a Flipper or plugin issue. Thanks!

For others in this thread, SDK 46 now has a better way to initialize flipper in the Podfile, and some daring souls have figured out how to launch Flipper so it can find metro (!!!) and find Hermes (!!!x2). #19 for details. I'm going to close this as fixed, but lets open a new issue if in SDK 46 people are having issues w/ the Hermes configuration.

Just crediting folks for their hard work on this.
@all-contributors please add @GollyJer for bugs (and thank you for helping work through these issues)


Fix the NPE for DISTINCT aggregation function when no record is selected

When no record is selected for the whole table, column data type will be STRING for all distinct columns (by Pinot convention)

Codecov Report

Merging #5154 into master will decrease coverage by 0.10%.
The diff coverage is 91.07%.

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

Discussed offline. Will modify the test in another pr to cover different scenarios of empty response.


Encountering "SyntaxError: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule '.f10oniif{background-color:rgba(255, 255, 255, 0.5);};}'." after updating the Edge browser to version 129.0.279.52.

Bug description
We are experiencing an issue where certain CSS styles are not functioning correctly in our web application after updating the Edge browser to version 129.0.279.52. We have identified a “SyntaxError” occurring when calling insertRule(). The error appears to be caused by a CSS rule with multiple closing braces, such as “.f143d684{width:calc(100% - 6.9rem);};}”.
System information
Edge: 129.0.279.52
@griffel/react: 1.5.25
Reproduce steps
You can reproduce this bug by downloading https://github.com/imechZhangLY/griffel-error-demo and following the instructions.

Build the project by running npm run build.
Open index.html in the dist folder using Edge version 129.0.279.52 or higher.
You will see the following error in the console. If the error does not appear immediately, try refreshing the page.

As I see, it's not related to Griffel itself. Our code generates proper CSS:

I checked the repro and it seems to be related to the used minifier (UglifyJs), as once this line is removed:
https://github.com/imechZhangLY/griffel-error-demo/blob/d036145899a49a09f4564c939779b165ae6d3ec7/webpack.config.js#L41
There are no errors anymore.

UglifyJS is no longer maintained and should not be used in production https://github.com/mishoo/UglifyJS/issues/3156#issuecomment-392943058


Ran black, updated to pylint 2.x

Won't pass pylint

@kattni The places it is failing are both rst todos (except for some trailing whitespace which I just fixed). In #6 I tried to fix them but rst was not being very nice so we decided to just leave it like it was before.


[REA] Benchmark Data Loader training from Cloud Storage

What questions are you trying to answer? Please describe.
NVTabular data loader accelerates training of TensorFlow and PyTorch models. Benchmarks are based on local disks. In production systems, data is often stored on cloud storages, such as AWS S3 or Google Cloud Storage. NVTabular data loader can asynchronously stream data and NVTabular supports AWS S3 and Google Cloud Storage.
Question:

What are the throughput of training a deep learning model?
** Data is stored on cloud storage and streamed from there?
** Data is copied to local disk and streamed from local disk?
** Compare both, AWS S3 and Google Cloud Storage
** Both frameworks: PyTorch and TensorFlow

Follow Up Question:

How to handle data sets with 500GB - 1TB dataset size? Is most efficient way to copy all data to a single machine and train? Is training directly from cloud storage preferable?

I don't have exact number, but IIRC it's much faster to download the data to local disk and train from there. If the data fits on disk on a single machine, that's the recommended approach.
We don't have a good solution for datasets that are too large to fit on one machine. Ideally the files from cloud storage would be partitioned across machines, so that each machine could download a subset of the data to local storage and train using that subset. We don't yet support that in the multi-GPU functionality of the dataloaders though. (We've only handled the multi-GPU single machine case so far.)

As the data loader can load asynchronously the data, could it not be faster to "train directly from storage" than "copying all the data without training and then start the training process?". In the case of large datasets like 100GBs to 500GBs, it should be more efficient as the training process does not idle during the copying (if only training for 1 epoch).
This question was multiple times asked. It would be great to support it with actual numbers.

That might be possible, depending on how the data is split into files in cloud storage. I don't think the dataloaders support it yet though.


FAQ about other build paths than .build

When I start using the package the server fails with the message that a given directory is not found. The error message shows that the path is expected to be in the .build directory.
I don't have the .build directory, instead I have .build-macos and .build-linux. This allows me to compile and run code side by side on macOS and on Linux without them interfering with each other. (I have a docker environment that mounts that same directory)
For now I have fixed this with creating a symlink but I would prefer to configure this in the package. Is it possible to add such configuration option which can default to .build?

I think .build is generated by swift package manager. how do you get spm to generate .build-macos and .build-linux?
My spm generates macos codes to .build/x86_64-apple-macosx, not .build-macos

By providing the --build-path parameter to swift build:
swift build --build-path "./.build-macos"

@fappelman thanks for opening an issue and for clarification.
I guess your VS Code config includes "sde.swiftBuildingParams": ["build", "--build-path", "./.build-macos"], right?
In that case we could detect the building parameter of the params.
@haifengkao thanks for your great support! Would you like to have a look on this? I'd be happy to help you getting started if you have any questions.

@vknabel As it turns out your question makes this request obsolete. I did not have those building parameters (for compilation I just used make build). After I added them, the errors are gone.
So please consider this the solution :-)

Hi @fappelman!
Nice to hear! Would be a great question for the FAQ section. Might take a while until I have the to time add it. But I guess it isn't urgent for now.

Good idea indeed.

Added to the README


building 'maskrcnn_benchmark._C' extension

❓ Questions and Help
There is an error when I run setup.py build develop, the logs are:
F:\Anaconda3\envs\driedfish\lib\site-packages\torch\lib\include\torch\csrc\api\include\torch/optim/optimizer.h(97): note: 参见“torch::optim::Optimizer”的声明
F:\Anaconda3\envs\driedfish\lib\site-packages\torch\lib\include\torch\csrc\api\include\torch/optim/sgd.h(31): note: 参见“torch::optim::SGD”的声明
F:\Anaconda3\envs\driedfish\lib\site-packages\torch\lib\include\torch\csrc\api\include\torch/optim/sgd.h(45): warning C4251: “torch::optim::SGD::momentum_buffers”: class“std::vec
tor<at::Tensor,std::allocator<_Ty>>”需要有 dll 接口由 class“torch::optim::SGD”的客户端使用
with
[
_Ty=at::Tensor
]
F:\Anaconda3\envs\driedfish\lib\site-packages\torch\lib\include\ATen/core/Type.h(224): note: 参见“std::vector<at::Tensor,std::allocator<_Ty>>”的声明
with
[
_Ty=at::Tensor
]
error: command 'F:\Microsoft Visual Studio 14.0\VC\bin\cl.exe' failed with exit status 2
Any suggestion? Thanks.

What is your PyTorch's version ?

1.0.0 + cuda10
@LeviViana

I still guess it comes from your PyTorch's version, did you try installing more recent versions? It should work with the 1.0.1.post2 version.


uninstall and system volume OSD (windows 10 anniversary)

Hi.
First of all this is a great tool, definitely a nice work.
I installed it just to try it out following a suggestion on a forum but it's not exactly what i was looking for, so i decided to uninstall.
Unfortunately i can't figure out how to get back the default system volume osd. the volume is working correctly but the osd just doesn't show up. any suggestion?

Hey KoRRo,
The uninstaller should make sure the program was terminated, but double-check by opening the task manager and ensuring 3RVX.exe isn't listed as a running task.
3RVX overrides the default OSD by hooking keyboard events at runtime, so as long as the program isn't running the normal functionality should be restored. (The app doesn't make registry edits or any sort of changes that would permanently disable the default OSD)

hey! thank you for the very quick reply.
i've tried a copule of times reinstalling and unistalling but unfortunately this doesn't work.
maybe there's something else going on, i've used your program for a while, and now that you make me think about it i actually can recall a couple of times where it was installed but not running and those times the system osd was actually working.
sorry for blaming you, it just looked like the most obvious cause since it was the only program working on audio and/or osd.


SOCKS5 unsuccessful replies

Enforce 100% test coverage
Some refactoring of address type conversions

Codecov Report

Merging #20 into master will increase coverage by 1.04%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master    #20      +/-   ##
========================================
+ Coverage   98.95%   100%   +1.04%
========================================
  Files           7      8       +1
  Lines         383    428      +45
========================================
+ Hits          379    428      +49
+ Misses          4      0       -4

Impacted Files
Coverage Δ

tests/test_utils.py
100% <100%> (ø)

socks/socks5.py
100% <100%> (+2.87%)
:arrow_up:

tests/test_socks5.py
100% <100%> (ø)
:arrow_up:

socks/utils.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@sethmlarson this is ready for re-review after rebasing with master


Version validation failed when trying to install CHIP REPL

Reproduction steps
My goal is to install and use CHIP REPL to work with customized cluster servers on my ESP32-C6 device. I am building on Ubuntu 22.04.4 LTS.
I am following the instructions as defined here : https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/python_chip_controller_building.md#building-and-installing
When I reach the following stage : scripts/build_python.sh -m platform -i separate
I get the following issue below. I'd appreciate any help with this.
Checking the environment:

20240630 12:35:37 INF Environment passes all checks!

Environment looks good, you are ready to go!

Done. Made 8187 targets from 378 files in 200ms
ninja: Entering directory `./out/python_lib'
[48/1043] ACTION //src/controller/data_model:data_model_zapgen_generate(//build/toolchain/linux:linux_x64_gcc)
FAILED: gen/src/controller/data_model/zapgen/zap-generated/access.h gen/src/controller/data_model/zapgen/zap-generated/gen_config.h gen/src/controller/data_model/zapgen/zap-generated/endpoint_config.h gen/src/controller/data_model/zapgen/zap-generated/IMClusterCommandHandler.cpp
python3 ../../third_party/pigweed/repo/pw_build/py/pw_build/python_runner.py --gn-root ../../ --current-path ../../src/controller/data_model --default-toolchain=//build/toolchain/linux:linux_x64_gcc --current-toolchain=//build/toolchain/linux:linux_x64_gcc --capture-output --python-dep-list-files gen/src/controller/data_model/data_model_zapgen_generate_metadata_path_list.txt -- ../../scripts/tools/zap/generate.py --no-prettify-output --templates /home/user/connectedhomeip/src/app/zap-templates/app-templates.json --output-dir /home/user/connectedhomeip/out/python_lib/gen/src/controller/data_model/zapgen/zap-generated --lock-file /home/user/connectedhomeip/out/python_lib/zap_gen.lock --parallel /home/user/connectedhomeip/src/controller/data_model/controller-clusters.zap
Searching for zcl file from /home/user/connectedhomeip/src/controller/data_model/controller-clusters.zap
Checking ZAP from ['/home/user/esp-matter/connectedhomeip/connectedhomeip/.environment/cipd/packages/zap/zap-cli']:
  !!! Version validation failed: required at least 2024.6.6, got 2024.3.14 instead
[57/1043] c++ obj/src/lib/support/libSupportLayer.CHIPArgParser.cpp.o
ninja: build stopped: subcommand failed.

Bug prevalence
always
GitHub hash of the SDK that was being used
28430f1364f541329fc5dd4350495d5afd9b8644
Platform
esp32
Platform Version(s)
No response
Type
Spec Compliance Issue, Platform Issue
Anything else?
No response

@pavel808 Well, what ZAP version are you using?  Are you just using the ZAP from bootstrap, or do you have a separate (older) ZAP installed that you are pointing at via the env vars?

@bzbarsky-apple Thanks for your reply. In the end, I installed it from the connectedhomeip inside the esp-matter repository after doing a git pull.
I still can't get this to work though. When I try to send a command I keep receiving this: ERROR: Avahi resolve failed
What i'm trying to do. My Node ID is 0x7293. I have a custom cluster server on my device with ID 0x131bfc00. There is a command from that cluster with ID 0x1, and I am trying to send value 0x1 there via the command.
Would you know the correct format to send such a command from CHIP REPL? Maybe i'm doing something wrong. Thanks.

I don't really know how to use the Python repl, sorry.  That said, it sounds like there are issues with DNS-SD resolution in your setup....  Hard to say more without knowing what exactly is being resolved and what is being advertised.

@bzbarsky-apple Ok thanks. It's a very difficult tool to use.
Is there any other Matter controller tool than be used to test and send commands to custom cluster server?
chip-tool only works with standard known clusters etc.
There is the ESP Matter Controller example, but it turns out that this is not supported for the ESP32-C6. I've hit a brick wall it seems:)

chip-tool only works with standard known clusters etc.

chip-tool can absolutely do custom things.  See https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/chip_tool_guide.md#using-wildcards-with-any-command which talks about wildcards, but you can just use whatever cluster/command/attribute IDs you want.
The value syntax there for commands/writes is JSON.  The built-in docs describe how those payloads work (e.g. if you run chip-tool any command-by-id the help output has a long section about the payload argument, and chip-tool any write-by-id has the same for attribute-values).

@bzbarsky-apple
My bad. I hadn't realized this. I tried it and it works great. Thanks a lot.

@pavel808 You're welcome!

Closing: issue was not having a propper zap-cli installed, which should be installed after bootstrap.


feature binding slot in order by that not show in project

Proposed changes

binding slot in order by that not show in project, such as:

SELECT c1 FROM t WHERE c2 > 0 ORDER BY c3

not check unbound when bind slot reference. Instead, do it in analysis check.

Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.79 seconds
load time: 446 seconds
storage size:<PHONE_NUMBER>4 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221108101353_clickbench_pr_41956.html