ArangoXEcto.aql_query insert

ArangoXEcto version
1.2.0
Elixir and OTP version
1.13.4
Ecto version
3.7.2
ArangoDB version
3.10.2
Steps to Reproduce
ArangoXEcto.aql_query(Repo, "insert {name: \"name\"} into users")
Expected Behavior
To insert the document into user collection
Observed Behavior
{:error,  %Arangox.Error{    endpoint: "http://localhost:8529",    error_num: 1652,    message: "AQL: unregistered collection used in transaction: users [write] (while parsing)",    status: 400  }
Additional Context
ArangoXEcto.aql_query/4 only works when  reading from the database. however it fails when doing any write operations such as insert or update.

You need to pass the :write argument to the ArangoXEcto.aql_query/4 function for any write operations. I have added some documentation to the function to clarify it.


Convert to multisig -> add cosigner -> error when pasting an address

When you convert an account to multisig and add a cosigner, there is an error if you paste an address from clipboard. It is suggested to "Just use" the address, but that address is cut off:
http://s13.postimg.org/l5zh9mxg7/add_cosigner_error.png
I don't see a reason in that "Just use" suggestion at all. It is fine how it is at "Send XEM".

There is a bug when pasting address with "-", as ui also tries to add, them. Hence invalid result.

But it works perfectly at the "Send XEM" popup window...


Reactions must not be empty when saving settings

Describe the bug
When I try to send settings I see the message - "reactions must not be empty". I am unable to save settings.
Steps to reproduce

Go to settings
Change any item
press save

The version of Memos you're using.
0.23.0
Screenshots or additional context

There is a migrations script that creates and backdates reactions for previous version users (e.g. 0.22.5 -> 0.23). it does not look like the migration scrip runs for users starting at version 0.23
@towarisch this is the default list of reactions 👍👎💛🔥👏😂👌🚀👀🤔🤡❓. Add the ones you want one at a time

Hello,
thank you for your answer. Unfortunately I can't add any reactions. When I press the button, there is no possibility to select a reaction. I can only assume it is because I try to react to my own memo?
How do I add a reaction then?

When you went to settings -> memo you couldnt save because you did not have a value for reactions

add some reactions from the list above, save and then they will show up when you try to react on a memo

Thank you it worked!

Am 27.10.2024 um 07:53 schrieb RoccoSmit @.***>:
👍


Data loader for tabular files

Create a registry object for ingesting data files that are e.g. csv, txt, etc. This will require either

Creating a new YAMLLoader class to deal with non-fits styled data, or
Extending the current YAMLLoader to also deal with the tabular data.

See here for details on current implementation.

This is a bit too cryptic. Exactly what kind of file formats are you expecting? Is it possible to use any existing parser, say, from JWST pipeline? We have to be careful not to re-invent the wheel here.

Okay. Well, since we're generally leveraging the astropy library for most all our functionality, I think we ought to stay within that realm.
For instance, tabular data is easily read into an astropy table object. From there, it's possible to export the normalized object as an ndarray that can be used in the creation of the Data object we use in Pyfocal.
The associated yaml file should contain definitions for how to ingest that data, e.g.
--- !CustomLoader
name: Generic Table
extension: [csv, txt]
data:
  col: 0
  unit: "Jy"
dispersion:
  col: 1
  unit: "Angstrom"
uncertainty:
  col: 2
meta:
  author: "Nicholas Earl"

That's fine for now, but keep in mind that sooner or later, this tool will have to support JWST data products.

this tool will have to support JWST data products

I'm not sure what you mean by this. The idea is to make loaders generic enough that either we can include ones ourselves in the registries for any standardized jwst data, or have users easily create their own.

So, let's say I have my calibrated spectrum file from JWST or HST pipeline, how do I ingest it into pyfocal? Maybe it is just a matter of documentation.

Maybe it is just a matter of documentation.

I agree. Under the hood, it's using astropy io registries. That is, the interfaces is a collection of functions that are registered to the astropy io registry. When data comes in, I'm relying on the registry to determine to which function the data file gets passed. That function should be responsible for converting the incoming data file into data objects that pyfocal can deal with. The yaml files are there to help with that by e.g. giving the hdu of the data, or by determining the type of uncertainty.
This particular issue was opened because right now, only fits files have a registered function within the registry. A couple of the scientists talk about how they often have csv files or txt files. Currently, there aren't functions registered that deal with converting those files into pyfocal objects.

Obviously, a lot of stuff that's happening in, for example, the fits file reader, can be put into a generic function that can be called by many of the registry functions.

It might be good to have one built-in ascii format that we can give people as an example, and then they don't have to build a YAML file for themselves if they put their data in that format. I don't know offhand if any of the ASCII file formats that astropy supports includes units, but if they do, then we could provide a reader  that reads in columns labeled wavelength, flux and (optionally) uncertainty and their units.

There are some options here -- http://astropy.readthedocs.org/en/latest/io/ascii/index.html#id1

It might be good to have one built-in ascii format that we can give people as an example, and then they don't have to build a YAML file for themselves

Definitely. I think this is the goal, too. We'll have "default" loaders that can be leveraged without writing anything, but if a user is so inclined, they can make and their own loader as well.

The IPAC format supports units, so maybe that's the one to recommend for ASCII inputs.

If no one is working on this yet, I can take a stab today and see what happens. But if someone is already working on this, please stop me so we don't duplicate effort. Thanks.

@nmearl , @hcferguson , does #42 satisfy this requirement? If so, we can close this.

Indeed it does. Thanks @pllim!


Cuda

Hello,
I am using Ubuntu which has Cuda 10.1 installed. I checked that torch is working with it.
However, when I run pytest tests, I get the following Cuda error
RuntimeError: CUDA error: no kernel image is available for execution on the device
__________________________________ ERROR collecting tests/datasets/test_usdfile.py
what should I do?

Could I ask for more details on your setup? Specifically, the type of GPU you're on, and it's "compute capability"?

I use Titan X black on Ubuntu 18.04. The cuda version is 10.1.
On Sun, Nov 17, 2019 at 2:37 PM Krishna Murthy<EMAIL_ADDRESS>wrote:

Could I ask for more details on your setup? Specifically, the type of GPU
you're on, and it's "compute capability"?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NVIDIAGameWorks/kaolin/issues/17?email_source=notifications&email_token=ANZR6GUP7LUZLOHEPI4FK6LQUHBRVA5CNFSM4JOLX73KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIYEAI#issuecomment-554795521,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZR6GSWXPLI7IJVPZ4FIQ3QUHBRVANCNFSM4JOLX73A
.

Hello,
It seems that I have pytorch correctly installed but the Kaolin is not
working:
(kaolin) csverma@blackhole:$ python
Python 3.6.7 | packaged by conda-forge | (default, Nov  6 2019, 16:19:42)
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import torch
torch.cuda.is_available()
True

On Sun, Nov 17, 2019 at 3:18 PM SherSingh Soni<EMAIL_ADDRESS>wrote:

I use Titan X black on Ubuntu 18.04. The cuda version is 10.1.
On Sun, Nov 17, 2019 at 2:37 PM Krishna Murthy<EMAIL_ADDRESS>wrote:

Could I ask for more details on your setup? Specifically, the type of GPU
you're on, and it's "compute capability"?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NVIDIAGameWorks/kaolin/issues/17?email_source=notifications&email_token=ANZR6GUP7LUZLOHEPI4FK6LQUHBRVA5CNFSM4JOLX73KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIYEAI#issuecomment-554795521,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZR6GSWXPLI7IJVPZ4FIQ3QUHBRVANCNFSM4JOLX73A
.

@krrish94, Is Kaolin only support CUDA10.1?When I use cuda10.0 assertionError occur and it said NVIDIA driver on my system is too old(found version 10000). My GPU is TelsaM40


Added name field to avoid conflicts since all pull from the same spac…

…edock
file
Removed toolbar dependency

#rebuild

Currently VesselViewer CANNOT be installed because these two files were missing the name fields, therefore the CKAN.exe was getting confused as to the mod names, etc.


How I can change color of the Song Time Bar - Puntuation (Event)

Describe your problem here.
Title says all of that
pls don't say: just put a lua file and txt file, then put the lua stuff
:(
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No

setProperty('timeBar.color', hex color)

this issue should be closed

Wait, this is in script


How to acquire intensity and angle when using LiDAR?

Platform : CARLA 0.9.15
Question :
I am currently researching how to generate point cloud data using Carla. I attempted to acquire [x, y, z, intensity, angle].However, after reading the sensor reference section of the CARLA document, I found out that the semantic LiDAR output does not include intensity and the LiDAR output does not include angle.
Is there a way to acquire intensity and angle when using  LiDAR?
Any answer is welcome!

As defined here, the intensity value provided by CARLA's lidar sensor (which is more or less just a function of object distance) is different from the intensity value reported by a real-world lidar, which depends on the reflectance of objects hit by lidar beams and the incidence angle. A potential solution might be doing what's done in #3826 , or you can use the semantic lidar and try to approximate the intensity for each point based on its object class and incidence angle.


Update dependencies

According to David.dm

What about using the David badge in README.md?

Already happened ;)

True. I was irritated because the David badge was added with a direct commit to master branch instead of using a PR.


Package 'PowerShell 6.2.2' has a package type 'DotnetTool' that is not supported by project 'myProject'.

Hi!
I have a recently created C# win forms application using .Net Framework 4.7.2.
When I try to install Powershell NuGet I get the following error
"Package 'PowerShell 6.2.2' has a package type 'DotnetTool' that is not supported by project 'myProject'."
Nothing added to this project yet (no other NuGets, libraries, etc...)

PowerShell 6.2.2 isn't supported under .NET Framework -- it's built, tested, and runs on .NET Core 2.x; you cannot use PowerShell versions 6.x and above with .NET Framework, to my understanding. 🙂

@johnykes the package you're linking to is the PowerShell dotnet global tool, which isn't designed for use in projects -- it's a global tool for the dotnet CLI (unfortunately they require a NuGet package like this to consume).
If you're targeting only Windows PowerShell (version 5.1) you might be looking for https://www.nuget.org/packages/Microsoft.PowerShell.5.ReferenceAssemblies/. Otherwise, if you want your application to target PowerShell 7 as well, you should retarget your application to .NET Standard 2.0 and depend on https://www.nuget.org/packages/PowerShellStandard.Library/.

I have another project c# win forms application using .NET Framework 4.6.1 and NuGet "PowerShell" by Nasim

I can't find anymore this NuGet (by Nasim)

But using https://www.nuget.org/packages/Microsoft.PowerShell.5.ReferenceAssemblies/
I can use powershell like in the stackoverflow example
https://stackoverflow.com/questions/19601043/how-do-i-run-powershell-command-in-windows-form-application
Thanks!


Remove a transpose that should be a bug

Left to do: Add a test that failed before, but runs fine now.

Codecov Report

Merging #201 (0469b33) into main (6ca30a4) will not change coverage.
 Consider uploading reports for the commit 4808aaf to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #201   +/-   ##
=======================================
  Coverage   60.59%   60.59%
=======================================
  Files          26       26
  Lines         982      982
=======================================
  Hits          595      595
  Misses        387      387

Impacted Files
Coverage Δ

src/filtering/smooth.jl
76.31% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


the table "contract_info" is Empty

Hello，I refer to the official demo ：
https://github.com/WeBankBlockchain/Data-Export-Demo
and export all the transaction data on the chain, but I find that the data in the table "contract_info" is empty, although other tables can be synchronized normally.
As a result, the name, ABI and bin values of the contract cannot be obtained.
Can it be solved?

Hi,
we need to configure the contract of abi and bin information, contract_info will have data, reference: https://github.com/WeBankBlockchain/Data-Export-Demo/blob/main/src/main/java/com/webank/blockchain/data/export/sdk/demo/ContractDataExportDemo.java
The ABI and BIN of the contract can be obtained by compiling Java files from the Fisco console or the SDK


Manual copy/paste social network should not be different to other social networks

Manual copy/paste social network should not be different to other social networks. In particular, myInstance should be defined in the same way for both (it is currently undefined for manual networks).
However, I think there's a bigger issue here which I've suggested in passing a few times, and which probably warrants more discussion...
I think our data-structures are currently social-network centric. If we instead start from a notion of roster, then a user would be able to organize contacts/instances into groups, it avoids having to have cross-dependencies between users and social networks, and it removes redundancy w.r.t. key-management.
The resulting data structure would be approximately:
Roster : { [uniqueUserId:string] : User }

User : {
  name : string, # defaults to one from a social network in a remote instance, but is user-editable
  publicKey : PublicKey,
  instances : RemoteInstance
}

RemoteInstance : {
  ...
  socialNetwork : {
   id : string
   profile : SocialNetworkProfile
   clientState : ClientState
 }
}

SocialNetworks : {
  id: string
  freedomSocialProvider : FreedomSocialProvider
}

We're removing one-time connections.


[openlane] Cell exclude list

Made the exclude lists configurable.
Separated the exclusion lists to no_synth.cells and drc_exclude.cells.
The merging of the two lists will be used in synthesis.
Only the drc_exclude.cells will be used in optimizations.
Aggressively reduced the don't-use list.

More documentation will be added to the openlane side to explain the usage of both.

@RTimothyEdwards: Do you prefer a clean rebase (without the merge commits), or will you be able to merge this pull request?

@agorararmard :  I would prefer a clean rebase.  I am unable to merge this.

@RTimothyEdwards: I will submit a fresh one shortly.


ingress gateway can not be installed well using istio v1.9.0

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
use istioctl to install  and find ingress gateway can not be installed. the below is info.
istioctl install --set profile=demo
This will install the Istio 1.9.0 demo profile with ["Istio core" "Istiod" "Ingress gateways" "Egress gateways"] components into the cluster. Proceed? (y/N) y
✔ Istio core installed
✔ Istiod installed
✔ Egress gateways installed
✘ Ingress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istio-ingressgateway
- Pruning removed resources                                                    Error: failed to install manifests: errors occurred during operation

kubectl get pod -n istio-system
NAME                                   READY   STATUS    RESTARTS   AGE
istio-egressgateway-65b9c8b54f-srhmk   1/1     Running   0          9m5s
istio-ingressgateway-56d9b7fdb-5sn5v   0/1     Running   0          9m5s
istiod-89dc6db9c-6jcgm                 1/1     Running   0          9m10s

kubectl describe pod -n istio-system istio-ingressgateway-56d9b7fdb-5sn5v
Name:         istio-ingressgateway-56d9b7fdb-5sn5v
Namespace:    istio-system
Priority:     0
Node:         <IP_ADDRESS>/<IP_ADDRESS>
Start Time:   Wed, 10 Feb 2021 21:22:49 +0800
Labels:       app=istio-ingressgateway
              chart=gateways
              heritage=Tiller
              install.operator.istio.io/owning-resource=unknown
              istio=ingressgateway
              istio.io/rev=default
              operator.istio.io/component=IngressGateways
              pod-template-hash=56d9b7fdb
              release=istio
              service.istio.io/canonical-name=istio-ingressgateway
              service.istio.io/canonical-revision=latest
              sidecar.istio.io/inject=false
Annotations:  prometheus.io/path: /stats/prometheus
              prometheus.io/port: 15020
              prometheus.io/scrape: true
              sidecar.istio.io/inject: false
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/istio-ingressgateway-56d9b7fdb
Containers:
  istio-proxy:
    Container ID:  docker://17f446a96893cb1c97c710a18438c0350ade0685dc11e3a668bcfdd1ba52d2bc
    Image:         docker.io/istio/proxyv2:1.9.0
    Image ID:      docker-pullable://istio/proxyv2@sha256:286b821197d7a9233d1d889119f090cd9a9394468d3a312f66ea24f6e16b2294
    Ports:         15021/TCP, 8080/TCP, 8443/TCP, 31400/TCP, 15443/TCP, 15090/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP
    Args:
      proxy
      router
      --domain
      $(POD_NAMESPACE).svc.cluster.local
      --proxyLogLevel=warning
      --proxyComponentLogLevel=misc:error
      --log_output_level=default:info
      --serviceCluster
      istio-ingressgateway
    State:          Running
      Started:      Wed, 10 Feb 2021 21:22:49 +0800
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     2
      memory:  1Gi
    Requests:
      cpu:      10m
      memory:   40Mi
    Readiness:  http-get http://:15021/healthz/ready delay=1s timeout=1s period=2s #success=1 #failure=30
    Environment:
      JWT_POLICY:                   third-party-jwt
      PILOT_CERT_PROVIDER:          istiod
      CA_ADDR:                      istiod.istio-system.svc:15012
      NODE_NAME:                     (v1:spec.nodeName)
      POD_NAME:                     istio-ingressgateway-56d9b7fdb-5sn5v (v1:metadata.name)
      POD_NAMESPACE:                istio-system (v1:metadata.namespace)
      INSTANCE_IP:                   (v1:status.podIP)
      HOST_IP:                       (v1:status.hostIP)
      SERVICE_ACCOUNT:               (v1:spec.serviceAccountName)
      CANONICAL_SERVICE:             (v1:metadata.labels['service.istio.io/canonical-name'])
      CANONICAL_REVISION:            (v1:metadata.labels['service.istio.io/canonical-revision'])
      ISTIO_META_WORKLOAD_NAME:     istio-ingressgateway
      ISTIO_META_OWNER:             kubernetes://apis/apps/v1/namespaces/istio-system/deployments/istio-ingressgateway
      ISTIO_META_UNPRIVILEGED_POD:  true
      ISTIO_META_ROUTER_MODE:       standard
      ISTIO_META_CLUSTER_ID:        Kubernetes
    Mounts:
      /etc/istio/config from config-volume (rw)
      /etc/istio/ingressgateway-ca-certs from ingressgateway-ca-certs (ro)
      /etc/istio/ingressgateway-certs from ingressgateway-certs (ro)
      /etc/istio/pod from podinfo (rw)
      /etc/istio/proxy from istio-envoy (rw)
      /var/lib/istio/data from istio-data (rw)
      /var/run/secrets/istio from istiod-ca-cert (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from istio-ingressgateway-service-account-token-n5sbf (ro)
      /var/run/secrets/tokens from istio-token (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  istiod-ca-cert:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      istio-ca-root-cert
    Optional:  false
  podinfo:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.labels -> labels
      metadata.annotations -> annotations
      limits.cpu -> cpu-limit
      requests.cpu -> cpu-request
  istio-envoy:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  istio-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  istio-token:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  43200
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      istio
    Optional:  true
  ingressgateway-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-ingressgateway-certs
    Optional:    true
  ingressgateway-ca-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-ingressgateway-ca-certs
    Optional:    true
  istio-ingressgateway-service-account-token-n5sbf:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-ingressgateway-service-account-token-n5sbf
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  10m                   default-scheduler  Successfully assigned istio-system/istio-ingressgateway-56d9b7fdb-5sn5v to <IP_ADDRESS>
  Normal   Pulled     10m                   kubelet            Container image "docker.io/istio/proxyv2:1.9.0" already present on machine
  Normal   Created    10m                   kubelet            Created container istio-proxy
  Normal   Started    10m                   kubelet            Started container istio-proxy
  Warning  Unhealthy  9m26s (x22 over 10m)  kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:15021/healthz/ready": dial tcp <IP_ADDRESS>:15021: connect: connection refused
  Warning  Unhealthy  8s (x268 over 9m2s)   kubelet            Readiness probe failed: HTTP probe failed with statuscode: 503

kubectl logs -n istio-system istio-ingressgateway-56d9b7fdb-5sn5v
2021-02-10T13:22:49.997617Z     info    FLAG: --concurrency="0"
2021-02-10T13:22:49.997660Z     info    FLAG: --domain="istio-system.svc.cluster.local"
2021-02-10T13:22:49.997664Z     info    FLAG: --help="false"
2021-02-10T13:22:49.997667Z     info    FLAG: --log_as_json="false"
2021-02-10T13:22:49.997669Z     info    FLAG: --log_caller=""
2021-02-10T13:22:49.997681Z     info    FLAG: --log_output_level="default:info"
2021-02-10T13:22:49.997683Z     info    FLAG: --log_rotate=""
2021-02-10T13:22:49.997685Z     info    FLAG: --log_rotate_max_age="30"
2021-02-10T13:22:49.997688Z     info    FLAG: --log_rotate_max_backups="1000"
2021-02-10T13:22:49.997691Z     info    FLAG: --log_rotate_max_size="104857600"
2021-02-10T13:22:49.997693Z     info    FLAG: --log_stacktrace_level="default:none"
2021-02-10T13:22:49.997707Z     info    FLAG: --log_target="[stdout]"
2021-02-10T13:22:49.997712Z     info    FLAG: --meshConfig="./etc/istio/config/mesh"
2021-02-10T13:22:49.997714Z     info    FLAG: --outlierLogPath=""
2021-02-10T13:22:49.997716Z     info    FLAG: --proxyComponentLogLevel="misc:error"
2021-02-10T13:22:49.997719Z     info    FLAG: --proxyLogLevel="warning"
2021-02-10T13:22:49.997722Z     info    FLAG: --serviceCluster="istio-ingressgateway"
2021-02-10T13:22:49.997725Z     info    FLAG: --stsPort="0"
2021-02-10T13:22:49.997728Z     info    FLAG: --templateFile=""
2021-02-10T13:22:49.997737Z     info    FLAG: --tokenManagerPlugin="GoogleTokenExchange"
2021-02-10T13:22:49.997751Z     info    Version 1.9.0-b63e1966c245924b10a0915a671a656540ed7a45-Clean
2021-02-10T13:22:49.998033Z     info    Apply mesh config from file accessLogFile: /dev/stdout
defaultConfig:
  discoveryAddress: istiod.istio-system.svc:15012
  proxyMetadata: {}
  tracing:
    zipkin:
      address: zipkin.istio-system:9411
enablePrometheusMerge: true
rootNamespace: istio-system
trustDomain: cluster.local
2021-02-10T13:22:49.999401Z     info    Effective config: binaryPath: /usr/local/bin/envoy
concurrency: 0
configPath: ./etc/istio/proxy
controlPlaneAuthPolicy: MUTUAL_TLS
discoveryAddress: istiod.istio-system.svc:15012
drainDuration: 45s
parentShutdownDuration: 60s
proxyAdminPort: 15000
proxyMetadata: {}
serviceCluster: istio-ingressgateway
statNameLength: 189
statusPort: 15020
terminationDrainDuration: 5s
tracing:
  zipkin:
    address: zipkin.istio-system:9411

2021-02-10T13:22:49.999428Z     info    Proxy role      ips=[<IP_ADDRESS>] type=router id=istio-ingressgateway-56d9b7fdb-5sn5v.istio-system domain=istio-system.svc.cluster.local
2021-02-10T13:22:49.999433Z     info    JWT policy is third-party-jwt
2021-02-10T13:22:49.999451Z     info    Pilot SAN: [istiod.istio-system.svc]
2021-02-10T13:22:49.999455Z     info    CA Endpoint istiod.istio-system.svc:15012, provider Citadel
2021-02-10T13:22:49.999512Z     info    Using CA istiod.istio-system.svc:15012 cert with certs: var/run/secrets/istio/root-cert.pem
2021-02-10T13:22:49.999656Z     info    citadelclient   Citadel client using custom root cert: istiod.istio-system.svc:15012
2021-02-10T13:22:50.052196Z     info    ads     All caches have been synced up in 60.846719ms, marking server ready
2021-02-10T13:22:50.052662Z     info    sds     SDS server for workload certificates started, listening on "./etc/istio/proxy/SDS"
2021-02-10T13:22:50.052692Z     info    xdsproxy        Initializing with upstream address "istiod.istio-system.svc:15012" and cluster "Kubernetes"
2021-02-10T13:22:50.052711Z     info    sds     Start SDS grpc server
2021-02-10T13:22:50.052922Z     info    Starting proxy agent
2021-02-10T13:22:50.053416Z     info    Opening status port 15020
2021-02-10T13:22:50.053509Z     info    Received new config, creating new Envoy epoch 0
2021-02-10T13:22:50.053590Z     info    Epoch 0 starting
2021-02-10T13:22:52.066003Z     info    Envoy command: [-c etc/istio/proxy/envoy-rev0.json --restart-epoch 0 --drain-time-s 45 --parent-shutdown-time-s 60 --service-cluster istio-ingressgateway --service-node router~<IP_ADDRESS>~istio-ingressgateway-56d9b7fdb-5sn5v.istio-system~istio-system.svc.cluster.local --local-address-ip-version v4 --bootstrap-version 3 --log-format %Y-%m-%dT%T.%fZ     %l       envoy %n        %v -l warning --component-log-level misc:error]
2021-02-10T13:22:52.103172Z     warning envoy runtime   Unable to use runtime singleton for feature envoy.http.headermap.lazy_map_min_size
2021-02-10T13:22:52.103218Z     warning envoy runtime   Unable to use runtime singleton for feature envoy.http.headermap.lazy_map_min_size
2021-02-10T13:22:52.103614Z     warning envoy runtime   Unable to use runtime singleton for feature envoy.http.headermap.lazy_map_min_size
2021-02-10T13:22:52.103650Z     warning envoy runtime   Unable to use runtime singleton for feature envoy.http.headermap.lazy_map_min_size
2021-02-10T13:23:10.000643Z     warn    ca      ca request failed, starting attempt 1 in 107.3067ms
2021-02-10T13:23:10.108295Z     warn    ca      ca request failed, starting attempt 2 in 181.132123ms
2021-02-10T13:23:10.297099Z     warn    ca      ca request failed, starting attempt 3 in 372.666262ms
2021-02-10T13:23:10.670356Z     warn    ca      ca request failed, starting attempt 4 in 817.16055ms
2021-02-10T13:23:12.150383Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:23:20.045900Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: no such host"
2021-02-10T13:23:20.046657Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: no such host"
2021-02-10T13:23:20.705047Z     warn    ca      ca request failed, starting attempt 1 in 95.570152ms
2021-02-10T13:23:20.801305Z     warn    ca      ca request failed, starting attempt 2 in 196.926088ms
2021-02-10T13:23:21.002854Z     warn    ca      ca request failed, starting attempt 3 in 402.446857ms
2021-02-10T13:23:21.406325Z     warn    ca      ca request failed, starting attempt 4 in 760.56648ms
2021-02-10T13:23:40.699388Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:23:41.770736Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:23:42.527011Z     warn    ca      ca request failed, starting attempt 1 in 94.445788ms
2021-02-10T13:23:42.621815Z     warn    ca      ca request failed, starting attempt 2 in 207.243132ms
2021-02-10T13:23:42.829360Z     warn    ca      ca request failed, starting attempt 3 in 379.321207ms
2021-02-10T13:23:43.226298Z     warn    ca      ca request failed, starting attempt 4 in 769.843591ms
2021-02-10T13:23:43.996496Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:23:50.712832Z     warn    ca      ca request failed, starting attempt 1 in 103.653069ms
2021-02-10T13:23:50.713483Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: no such host"
2021-02-10T13:23:50.817696Z     warn    ca      ca request failed, starting attempt 2 in 219.157174ms
2021-02-10T13:23:51.042762Z     warn    ca      ca request failed, starting attempt 3 in 433.77698ms
2021-02-10T13:23:51.477092Z     warn    ca      ca request failed, starting attempt 4 in 734.533964ms
2021-02-10T13:23:52.212460Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: no such host"
2021-02-10T13:23:54.045986Z     warn    ca      ca request failed, starting attempt 1 in 96.959079ms
2021-02-10T13:23:54.143492Z     warn    ca      ca request failed, starting attempt 2 in 207.633553ms
2021-02-10T13:23:54.352485Z     warn    ca      ca request failed, starting attempt 3 in 416.872575ms
2021-02-10T13:23:57.352149Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:23:59.345060Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:01.360069Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:03.349459Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:05.350996Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:07.358265Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:09.346218Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:11.344436Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:12.725649Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:24:13.359481Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:14.534477Z     warn    ca      ca request failed, starting attempt 4 in 771.533435ms
2021-02-10T13:24:15.307190Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:24:15.347018Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:17.344953Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:18.916230Z     warn    ca      ca request failed, starting attempt 1 in 103.391505ms
2021-02-10T13:24:19.024420Z     warn    ca      ca request failed, starting attempt 2 in 204.909132ms
2021-02-10T13:24:19.230368Z     warn    ca      ca request failed, starting attempt 3 in 389.575427ms
2021-02-10T13:24:19.347370Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:19.627636Z     warn    ca      ca request failed, starting attempt 4 in 757.891607ms
2021-02-10T13:24:20.386527Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:24:21.349013Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:22.730900Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: no such host"
2021-02-10T13:24:23.346367Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:24.654682Z     warn    ca      ca request failed, starting attempt 1 in 95.626605ms
2021-02-10T13:24:24.750828Z     warn    ca      ca request failed, starting attempt 2 in 196.412913ms
2021-02-10T13:24:24.952684Z     warn    ca      ca request failed, starting attempt 3 in 394.792997ms
2021-02-10T13:24:25.353579Z     warn    ca      ca request failed, starting attempt 4 in 820.015204ms
2021-02-10T13:24:25.358000Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:26.175162Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: no such host"
2021-02-10T13:24:27.348604Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:29.344889Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:31.361510Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:32.237040Z     warn    ca      ca request failed, starting attempt 1 in 102.472176ms
2021-02-10T13:24:32.341088Z     warn    ca      ca request failed, starting attempt 2 in 209.167229ms
2021-02-10T13:24:32.550913Z     warn    ca      ca request failed, starting attempt 3 in 426.442713ms
2021-02-10T13:24:32.977831Z     warn    ca      ca request failed, starting attempt 4 in 720.08221ms
2021-02-10T13:24:33.349841Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:33.702607Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: no such host"
2021-02-10T13:24:35.345881Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:37.354361Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:39.345281Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:41.344715Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:43.345381Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:45.345168Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:47.344087Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:49.346576Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:51.347778Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:53.346060Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:53.812418Z     warn    ca      ca request failed, starting attempt 1 in 101.796683ms
2021-02-10T13:24:53.918612Z     warn    ca      ca request failed, starting attempt 2 in 215.12047ms
2021-02-10T13:24:54.145229Z     warn    ca      ca request failed, starting attempt 3 in 396.675398ms
2021-02-10T13:24:54.542893Z     warn    ca      ca request failed, starting attempt 4 in 816.026495ms
2021-02-10T13:24:55.347684Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:55.364292Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:24:55.736390Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:24:57.350998Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:24:59.346735Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:01.352453Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:02.297679Z     warn    ca      ca request failed, starting attempt 1 in 102.835685ms
2021-02-10T13:25:02.400728Z     warn    ca      ca request failed, starting attempt 2 in 189.898664ms
2021-02-10T13:25:02.591055Z     warn    ca      ca request failed, starting attempt 3 in 373.892467ms
2021-02-10T13:25:02.965734Z     warn    ca      ca request failed, starting attempt 4 in 814.8198ms
2021-02-10T13:25:03.344663Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:03.781097Z     warn    sds     failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:25:05.347731Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:07.347369Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:09.344704Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:11.363259Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:13.355563Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:15.347321Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:17.344652Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:19.345347Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:21.345559Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:23.350154Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:25.350776Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:27.345038Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:27.407813Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2021-02-10T13:25:29.345918Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:31.362666Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:33.345475Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2021-02-10T13:25:35.346454Z     warn    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected

[ ] Docs
[ X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Expected behavior
to be installed well.
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
[root@master istio-1.9.0]# istioctl version --remote
client version: 1.9.0
control plane version: 1.9.0
data plane version: 1.9.0 (1 proxies)

[root@master istio-1.9.0]# kubectl version --short
Client Version: v1.20.2
Server Version: v1.20.2

How was Istio installed?
istioctl install --set profile=demo

Environment where the bug was observed (cloud vendor, OS, etc)
os = centos7
kernel = Linux 5.4.96-1.el7.elrepo.x86_64
k8s
[root@master istio-1.9.0]# kubectl get node
NAME           STATUS                     ROLES    AGE    VERSION
<IP_ADDRESS>   Ready,SchedulingDisabled   master   2d6h   v1.20.2
<IP_ADDRESS>   Ready                      node     2d6h   v1.20.2
<IP_ADDRESS>   Ready                      node     2d6h   v1.20.2
<IP_ADDRESS>   Ready                      node     2d6h   v1.20.2
<IP_ADDRESS>   Ready                      node     2d6h   v1.20.2

Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

sorry, I should ask it in discuss.istio.io


Missing endpoint for GET projects/:id/events

clients/event.rb has a bug for getting back the visible project events related to project IDs.

  def project_events(project, options = {})
    get("/#{url_encode project}/events", query: options)
  end

The projects keyword is missing before the /#{url_encode project}

I have worked that out, so maybe I can create a pull-request for the issue sometime soon?

I have worked that out, so maybe I can create a pull-request for the issue sometime soon?

Yes, please.

@NARKOZ PR submitted with this fix.
Happy Hacktoberfest!

#418


Is UI support on your roadmap?

Thank you creating this fantastic Workflow open source project!
Definitely, UI is very important for end users, I understand that currently UI is not a part of the project, but will it be on your roadmap? If yes, do you have any idea about "when"?
In addition, when this project is ready to shift from "experimental" phase to "product" phase?

If by "product" you mean when is CoreWF going to be used in a product, it already is. If you're asking when will we publish a package with a version number that doesn't include the date and build number, I don't have an answer for that yet.
Most people I talk to that are interested in using CoreWF want the rehostable workflow designer. It didn't make sense in early .NET Core but now with Avalonia and MAUI it's technically possible. It would be a lot of effort to build and maintain. I don't know if there's enough demand out there to be worth the effort.

Thanks @dmetzgar
If there is no UI support, a consumer wouldn't be able to create a new workflow, s/he wouldn't be able to visualize any existing workflow, which IMO is a big limitation. Being able to run a pre-defined workflow is quite useful, but not everyone knows how to manually edit a xaml file.
BTW, when you mentioned "rehostable workflow designer", did you mean a designer which is hostable on multi-platforms like desktop, web and mobile?

Is there a chance of Microsoft donating WPF-based rehostable designer from .NET Framework? Even though it's Windows-only, it would be a big win for existing users.


Enable both ingest plugin in a future release

Now we have 2 plugins:
the Logging plugin: normalize the time and log field from incoming logs, which is needed for the dashboard. It also detects Json objects in the logs.
the AIOps plugin: do some extra preprocessing that needed for the AI services + sending logs to Nats.
Ideally, if the Logging backend is enabled but AIOps not enabled , only the Logging plugin should be installed: and if AIOps got enabled, both plugin should be installed in the pipeline.

Initial pass we will just enable both plugins when logging is enabled.  If AIOps isn't enabled there should be no queue groups so the NATs messages will just get blackholed.


Code refactoring

Made some code refactorings on profile.js to improve the codebase

Just for future reference, when you see a function being redefined (in this case OnResponseVoteUp) it's because the original function is code from a js file on Steam Community. The code does look pretty ugly sometimes but I try and keep it as similar as possible so in case something breaks in the future, or Steam changes the function, I can compare the code I have to the new function on Steam Community and see what changes they've made!


Widget does not work properly with formsets (existing values are not displayed)

A javascript function containing the picker_id in its name is dynamically generated for each widget (widget.html, line 19).
In a formset, Django dynamically generates identifiers for each form in a formset in the format 'id_table-number-Field'. Thus, the picker_id contains a hyphen which must not be part of a function name in JavaScript. This causes an error when the page is loaded. The picker does not display an existing field value.
A simple solution would be to replace any hyphen in the picker_id by an underscore.

Ah, good catch! Unfortunately, the tests didn't catch this, nor did my actual tests, as the defer didn't happen. Trying to figure out a good way to test this, but your solution seems good. I'll get it in place.

This has been fixed and published in version <IP_ADDRESS>. Thank you!


config-linux: Drop the default-filesystem section

Users who need these mounts would have to explicitly set them up in their configuration (as runtime-tools continues to do) if they wanted to guarantee their presence.  Users who don't need them can omit them from their configuration.  I don't see how keeping a SHOULD-strength runtime requirement helps either of those workflows.
This is one of the possible approaches I'd floated in #666.

This section still looks useful to me.

This section still looks useful to me.

So do you prefer #679?  Or do you like master how it is?
If you like master, do you read the current master wording as a suggestion to runtime authors or as a suggestion to config authors?

I prefer the master version

I prefer the master version

And I'm citing your earlier comment for the “this is advice to config authors” interpretation.  Is that actually your interpretation?  Do you think the master wording is clearly not advice to runtime authors (it's not clear to me)?  It might be easier to talk about this if we talk over how SHOULD validation will work.  Will this SHOULD be checked by runtime-tools' validate package (aimed at validating configuration JSON) or runtime-tools' runtimetest command (aimed at validating runtime implementations)?

Closing as this section is marked as SHOULD and is found useful by multiple maintainers.


Can not build Android 7 xamarin apps

I upgraded to Complie using Android 7
Then the VSTS build failed
C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets (569, 2)
C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(569,2): Error XA0000: Could not determine API level for $(TargetFrameworkVersion) of 'v7.0'.
Process 'msbuild.exe' exited with code '1'.

The hosted build VMs do not have Xamarin.Android 7.0 support though the Android SDK 24 is installed. We will be updating them early next year after the holidays.
Sorry for the inconvenience.
Thanks,
Madhuri

If this hasn't been done yet, why not keep the issue open? That way we can get updated when it's actually fixed for us.

@shortstuffsushi : We have a couple of other issues related to Android 7 with Xamarin on hosted build. A new version of the VM is available which has Android SDK 24 on it, so you shouldn't see this particular error. Can you please follow this issue instead: https://github.com/Microsoft/vsts-tasks/issues/3237?

Sure. Linking issues is fine, as long as we've got somewhere to watch.

I have this issue too. I'm new to android, and so this is stopping me in my tracks this morning.

@chris1248: The issue was resolved and closed. If you are seeing a similar error now, please open a new issue with build log and details on which agent queue you are using.


Proposal: Istio Envoy mTLS Private Key Protection with HSM

Istio Envoy mTLS Private Key Protection with HSM
Envoy uses boringssl for tls communication, and the enabling of mTLS can also protect the connection between services from being attacked and tampered, but there’s still vulnerabilities within the private key management in Envoy, as the private key is exposed as clear text data inside the memory. The proposal is to provide a selectable choice to enable the PKCS#11 standard inside Envoy together with Hardware Security Module (HSM) to serve better security for key management within Envoy.
Background
Current workflow
Currently, the istio-proxy container runs the Envoy Proxy either in router mode, for ingress gateway or in sidecar mode when running as a proxy alongside the application. In sidecar mode the init container sets up all the required iptable rules and the control plane builds all the necessary listeners, routes, cluster and endpoint configurations and pushes them to the proxies.
And the use of mTLS protocol can provide a more secure and reliable connection. The flow diagram shows the current communication mode between sidecars and where the certificate will be used in this mesh.

In the current workflow, the certificate which is used for mTLS connection between sidecars was generated by Istio-Agent and issued to the sidecar, and the TLS private key is exposed as clear text data inside the memory of the pod. Although Istio's authentication policy can avoid most malicious third-party attacks, once a pod is compromised, the communication packages between the sidecar and other sidecars might be tampered with, which may lead to security vulnerabilities in the cluster.

In order to provide a way where the cluster can benefit from a pluggable third-party HSM backend and the envoy proxy can be extended to perform as a private key provider, we came up with this proposal. This design works for most use cases and provides an option that customers can choose to enable this option according to their needs. The workflow is shown in the diagram below.
Our changes are mainly in the process of generating CSR and key pair in Istio-Agent. The key point is to enable a selectable choice that the CSR and key pair can be generated in Envoy and protected by HSM backend. We introduced a global variable to enable the usage of external private key providers and in order to give customers a more flexible choice to adapt to all situations, if the external provider does not exist, the certificate and key pair will be generated by default flow.
Design
This proposal tends to increase the security level of cryptographic operations and key management inside Envoy. It involves modifying Istio-Agent and Envoy to provide an advanced-level security to save the secrets (Istio-Agent mTLS private key) securely inside HSM (SoftHSM as sample) based on the PKCS#11 standard.
Control plane
The workflow of control plane is shown in the diagram below.

The main changes of workflow are shown by the blue arrows.
1.2 1.3 The SDS request no longer requires Istio-Agent to generate keypair and CSR. And the SDS response sent to envoy does not directly contain the private key, but config to generate HSM private key provider. A kind of protobuf definition of SDS response is shown below.
message Config {
   string hsm_library = 1;
   string key_label = 2;
   string usr_pin = 3;
   string so_pin = 4;
   string token_label = 5;
   string rsa_key_size = 6;
   // csr_config is a string composed of various configuration items
   // provided to envoy, which are used to generate CSR by openssl
   string csr_config = 7;
}

1.4 1.5 Then HSM private key provider will init HSM context once, and generate rsa keypair in HSM and CSR by openssl cmdline with PKCS#11 engine.
1.6 Since envoy’s SDS does not support CSR type resources, we use gRPC instead. CSR will be sent to Istio-Agent by gRPC request.
1.13 After Istio-Agent receives the signed certificate, it will be sent to envoy through gRPC response and saved in Boringssl config.
Data plane
The workflow of data plane is shown in the diagram below.

2.3 When Boringssl perform TLS handshake in HTTPS connection, it will call signing/decryption function in HSM Private Key Provider.
2.4 2.5 2.6 And HSM will execute signing or decryption and return the result to HSM Private Key Provider.
2.7 Finally HSM Private Key Provider will return the result to Boringssl
Key generation
Two new approaches are provided for private key generation corresponding to the current.
A.    Envoy will by default try to load the pre-conducted private key and save it into SoftHSM.
B.    While there's no pre-conducted key ready, Istio-Agent will deliver all configuration and call Envoy to generation the CSR, and Envoy can call the PKCS#11 APIs implemented inside the HSM(SoftHSM as sample) to generate the signing key.
For both cases, the output returned is a key handle instead of the plain-text key.
Key retrieval
While following the PKCS#11 standard, id and label are used as the identifiers to fetch the private key. Either of them is usable to fetch the identical key. And the key that was retrieved is a handle instead of the plain-text data block.
We also raise a proposal in istio community: https://github.com/istio/istio/issues/36296.
@lizan @ggreenway @asraa

Can you please close this and open a new issue with just the Envoy side change(s) you are requesting? Thank you!

It's helpful to understand the context of what you're trying to do in istio, but I agree that you'll need to make a concrete proposal of what you plan to change in Envoy.
Also, this isn't the first time HSM support has come up. See #1106.

Can you please close this and open a new issue with just the Envoy side change(s) you are requesting? Thank you!

OK, I will modify the proposal later. Thanks!

It's helpful to understand the context of what you're trying to do in istio, but I agree that you'll need to make a concrete proposal of what you plan to change in Envoy.
Also, this isn't the first time HSM support has come up. See #1106.

OK, I will modify the Istio part of this proposal and add more details about Envoy part. Thanks!

Hi! I create a new issue to show more details about our proposal.
https://github.com/envoyproxy/envoy/issues/19217
Looking forward to your comments and suggestions. Thanks!
@lizan @ggreenway @mattklein123 @asraa


Add g:loaded_lsp variable for easy detection

Useful to detect if the plugin was loaded before doing things in, for example, .vim/after/plugin/lsp.vim by doing:
if !get(g:, 'loaded_lsp') | finish | endif

So it looks like it's a bad idea to bail out in the way it's done in #122. Either use vimscript9 noclear or just set the global variable without bailing out.
:h vim9-reload

						*vim9-reload* *E1149* *E1150*
When loading a legacy Vim script a second time nothing is removed, the
commands will replace existing variables and functions, create new ones, and
leave removed things hanging around.

When loading a Vim9 script a second time all existing script-local functions
and variables are deleted, thus you start with a clean slate.  This is useful
if you are developing a plugin and want to try a new version.  If you renamed
something you don't have to worry about the old name still hanging around.

If you do want to keep items, use: >
	vim9script noclear

You want to use this in scripts that use a `finish` command to bail out at
some point when loaded again.  E.g. when a buffer local option is set to a
function, the function does not need to be defined more than once: >
	vim9script noclear
	setlocal completefunc=SomeFunc
	if exists('*SomeFunc')
	  finish
	endif
	def SomeFunc()
	....

Issues with bailing out early. See https://github.com/yegappan/lsp/issues/122#issuecomment-1348762412.


Can't download CSDTK4.2 CoolWatcher

Hello, i can't download the folder CSDTK4.2 and Icant find the coolwatcher to upload my code.

Check this https://github.com/Ai-Thinker-Open/GPRS_C_SDK/issues/412

Thanks a lot, so this means borad discutinued?

I don't think so. I've recently purchases one.
However, it's a 2G board, and https://en.wikipedia.org/wiki/GSM#Discontinuation
The SDK hasn't seen updates for a couple of years now. It may be considered to be feature-complete, though.

Thank you very much for the information, now it is clear to me

Closed


Provide a Couchbase Docker image

Happy to send a PR once I know the process :)

You can for this repo, and then make a PR back into it. We are storing dockerfile sample here: Windows Container Samples.
Also happy to take a look at it when some time opens up.
neilp

Starting work at https://github.com/arun-gupta/docker-images/blob/master/couchbase-windows/Dockerfile

I am running into this bug https://issues.couchbase.com/browse/MB-19615 after getting docker file to work on Windows against CB 4.5 builds

Hi @arun-gupta, is there anything else we can do to resolve this issue?

@enderb-ms I'm no longer working on this.
@suravarjjala or @Laurafautley should be able to provide an update.

Hi @enderb-ms, If you're checking the status of that issue https://issues.couchbase.com/browse/MB-19615 its already fixed in Couchbase Server 4.6.0 and (newest) Couchbase Server 5.0. Can you give it try?
One thing feel free to create JIRA issue  if there any issues running Couchbase on Windows Container.

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Flask 0.12 incompatible with Google App Engine?

A very simple boilerplate Google App Engine example using Flask fails when upgrading from 0.10 to 0.12.  The problem is something cryptic relating to module path resolution.
The straight-off-the-web GAE Flask Hello World example works fine when deployed to a live GAE project.  The reason why this works ok is that it is so simple that it makes no use of third-party libraries outside of those that are natively installed along with Flask as a standard 'pip' install.
But when I extended this example to make the simplest use of the Google Cloud Datastore, then when the code is deployed, and a GET request is made, it fails with the following stack traceback:

Traceback (most recent call last):
File "/google/google-cloud-sdk/platform/google_appengine/google/appengine/runtime/wsgi.py", line 240, in Handle
handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
File "/google/google-cloud-sdk/platform/google_appengine/google/appengine/runtime/wsgi.py", line 299, in _LoadHandler
handler, path, err = LoadObject(self._handler)
File "/google/google-cloud-sdk/platform/google_appengine/google/appengine/runtime/wsgi.py", line 85, in LoadObject
obj = import(path[0])
File "/home/cinchent/flask-skel/main.py", line 8, in
from google.cloud import datastore
ImportError: cannot import name datastore

Digging deeper into this, I tried to use the GAE development application server on my local Windows box, and lo! then even the stock Hello World example fails: Flask is unable to even successfully import the native Python 'msvcrt' module from within its own Click initializer.  Here's the traceback from that:

Traceback (most recent call last):
File "C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\platform\google_appengine\google\appengine\runtime\wsgi.py", line 240, in Handle
handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
File "C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\platform\google_appengine\google\appengine\runtime\wsgi.py", line 299, in LoadHandler
handler, path, err = LoadObject(self.handler)
File "C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\platform\google_appengine\google\appengine\runtime\wsgi.py", line 85, in LoadObject
obj = import(path[0])
File "C:\CINCH\Freewave\GCP\appengine-flask-skeleton\main.py", line 8, in
from flask import Flask
File "C:\CINCH\Freewave\GCP\appengine-flask-skeleton\lib\flask_init.py", line 21, in
from .app import Flask, Request, Response
File "C:\CINCH\Freewave\GCP\appengine-flask-skeleton\lib\flask\app.py", line 26, in
from . import json, cli
File "C:\CINCH\Freewave\GCP\appengine-flask-skeleton\lib\flask\cli.py", line 17, in
import click
File "C:\CINCH\Freewave\GCP\appengine-flask-skeleton\lib\click_init.py", line 18, in
from .core import Context, BaseCommand, Command, MultiCommand, Group,
File "C:\CINCH\Freewave\GCP\appengine-flask-skeleton\lib\click\core.py", line 7, in
from .types import convert_type, IntRange, BOOL
File "C:\CINCH\Freewave\GCP\appengine-flask-skeleton\lib\click\types.py", line 4, in
from ._compat import open_stream, text_type, filename_to_ui,
File "C:\CINCH\Freewave\GCP\appengine-flask-skeleton\lib\click_compat.py", line 164, in
import msvcrt
File "C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\platform\google_appengine\google\appengine\tools\devappserver2\python\sandbox.py", line 964, in load_module
raise ImportError('No module named %s' % fullname)
ImportError: No module named msvcrt

GAE runs the Flask webapp within a sandbox, but it provides the proper module paths to the installed modules, provided those obey a somewhat orthodox Python path resolution technique, but whatever exotic technique Flask now uses in 0.12 fails within that sandbox.  (Other third-party libraries can be imported from within the sandbox just fine.)
These problems are completely absent in Flask 0.10.  (Once you're past the problem of importing 'protobuf', that is, a separate but known incompatibility with GAE's internal use, which has a workaround.)
I've googled high and low for any information about what I may be missing in the Flask initialization recipe -- surely I must not be the only person to have encountered this! -- but have turned up nothing.

In the enclosed 'main.py', setting the DATASTORE_EXAMPLE global to False causes it to behave as the stock GAE Hello World example app, and setting it to True extends that app to attempt use of the Cloud Datastore.
bundle.zip

I'm no Flask/GAE expert, but here is my quick diagnosis:

msvcrt is not available on Linux (or rather: it is only available on Windows)
since the GAE development server tries to simulate Linux (since in production your application runs on Linux), it disallows importing msvcrt
unfortunately click detects that it's on Windows and tries to use the windows specific functionality: https://github.com/pallets/click/blob/master/click/_compat.py#L166

I don't see any good workaround besides try/catching the import in click and not doing anything if running under GAE (and perhaps logging a warning?)

Yes, it appeared to me as well that integration of 'cllck' is implicated in this problem, at least as pertains to the development application server.  That module was not present in the 0.10 version, which works fine.  However, the problem is not confined only to the DAS; it also manifests after code is deployed onto on the real GAE cloud server, which the first traceback attests to.
I had to freeze on flask==0.10 for my GAE app to be deliverable, and that's ok for now -- there's nothing in v0.12 I can't live without.  I was simply making the creators aware of having left GAE behind in the wake of intervening version(s), in case they care.  (And I presume they do...)

This probably needs to be reported against Click, not Flask.

@davidism - reported here: https://github.com/pallets/click/issues/711

Well, inasmuch as flask uses click, it's certainly applicable here.  Also,
I'm not convinced the problem is solely with the user of click -- witness
the same problem manifesting in the development server with other modules.
On Jan 5, 2017 10:41 PM, "Attila-Mihaly Balazs"<EMAIL_ADDRESS>wrote:
@davidism https://github.com/davidism - reported here: pallets/click#711
https://github.com/pallets/click/issues/711
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pallets/flask/issues/2139#issuecomment-270835879, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEQgSlf3FKKCoiRn8JRHljKX6vBjbVToks5rPdQcgaJpZM4LZLnh
.

I'm pretty sure it's a click issue. Click 6.7 is out, please try.

Any news regarding this topic? On Windows the same error persist using click-6.7

It continues to be an issue with Click then. Did you report it?

I just reported it again
https://github.com/pallets/click/issues/711


Refactor combiner

Description
Refactor to be as close as possible to Signer
Doesn't implement the countes

should this be based on master so that the changes can also be reflected on gen1?


Make some pydocstyle rules respect line continuation character

Currently, pydocstyle rules produce many false positives on code bases that use continuation characters in docstrings. This PR tries to make some pydocstyle rules respect line continuation character.
Progress so far

[] fix D205 and add one more auto fix

Need to respect stringescapeseq

After a quick look, I plan to investigate the following rules as they may have the same problem.

[ ] D200 (empty first line + content -> no report)
[ ] D209
[ ] D210 (?)
[ ] D400
[ ] D415

Do you know if pydocstyle itself treats continuations in this way? As in, would we be intentionally deviating from pydocstyle by merging this? Or does Ruff currently differ from pydocstyle here?

As far as I know, pydocstyle treats continuations in this way. When I run pydocstyle crates/ruff/resources/test/fixtures/pydocstyle/D205.py --select D205, it prints
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:13 in public function `f3`:
D205: 1 blank line required between summary line and description (found 0)
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:30 in public function `f5`:
D205: 1 blank line required between summary line and description (found 0)
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:42 in public function `f6`:
D205: 1 blank line required between summary line and description (found 3)

But when I run ruff check rates/ruff/resources/test/fixtures/pydocstyle/D205.py --select D205 (without this PR), it produces 3 false positives:
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:2:5: D205 1 blank line required between summary line and description
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:7:5: D205 1 blank line required between summary line and description
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:13:5: D205 1 blank line required between summary line and description
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:19:5: D205 1 blank line required between summary line and description
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:30:5: D205 1 blank line required between summary line and description
crates/ruff/resources/test/fixtures/pydocstyle/D205.py:42:5: D205 1 blank line required between summary line and description

@charliermarsh Considering how Python escape string literals, I think we can provide a function in crates/ruff_python_ast/src/str.rs to unescape strings. After that, we can easily handle line continuation and newlines. What do you think?

Going to close in the interest of keeping the PR list up-to-date. Can always re-open if we choose to revisit!


SCSS or LESS original files.

I discovered this project today and i fell in love.
I want to know if we can access to the styles core in order to modify, remove or extend the styles according to our needs.
Thanks.

Hey @SalahAdDin we don't yet use the original SCSS files in the react library, we're just using the built .css file. It might make sense for this to change, happy to take a PR if you would like to work on it?
You can find the core SCSS files here in the main Tabler repository.

@jonthomp Ok, i will do it in the comming weeks.


Replace main_content block with mainContent

Ticket: https://trello.com/c/d3sJhHq8/221-replace-pagetitle-maincontent-block-with-pagetitle-maincontent-in-buyer-frontend
Required for #969

WFM


Decide GWSS methods

Issue to discuss which GWSS methods to run.

Initial proposal would be to run H12, G123 and possibly also IHS for all cohorts.
Although H12 and G123 are very similar, having both allows for confirmation that we are not getting false positive or negative signals in H12 because of phasing errors or artifacts.
Possibly worth adding IHS because, although it is generally a bit gappy, and signals are broader so targeting is not so good, it is possibly more sensitive to incomplete sweeps at an earlier stage, where haplotype under selection is at lower frequency.
Because we'll need to run GWSS across more than 100 cohorts, we'll want to avoid using methods that require selection of comparison populations, such as XPEHH and PBS.

Closing here as we've decided to go with H12, G123 and IHS initially.


Diffing animation of adding new chart

Awesome library! I'm working on replacing https://github.com/PhilJay/MPAndroidChart with it, and so far it's been a breeze!
I'm wondering if it's possible to dynamically add a new chart to ComposedChartEntryModelProducer while only animating the newly added Chart. Currently when adding a new one, you have to recreate ComposedChartEntryModelProducer and it will animate both charts again.

Hi @BartNijland91,
It's not possible currently, but this is definitely something we can add in future versions.


Video frame frozen for some users

In a 20+ people meeting, I am audible to everyone.
But for some ( 4 to 5 participants) , my video frame is frozen forever (some cases, it recovers after very long gap).
I am able to speak to these 4/5 people, I can also see their video properly.
While this was happening, I tried to pause my camera video and resumed it back - yet they were still seeing my stuck frame.
This is really bringing the meeting experience down.
What is the solution for this?
Thanks in advance.

Additional input:
When the frame is frozen, the advance mode shows STLCurrent both as empty.
When it gets restored to a value, it does start showing stream again.

This means you are bandwidth constrained. We need to handle this case.


Add NewlineAbove command

Check for existing issues

[X] Completed

Is your feature request related to a problem?

Describe the solution you'd like
We have a NewlineBelow, we should add a NewlineAbove
If applicable, add mockups / screenshots to help present your vision of the feature
No response

I use NewlineAbove A LOT in other editors

Looked for this. Would love this feature too. I'm always typing shift-cmd-enter in vscode.

We are working on this. It's almost ready, minus a couple of integration tests.

This is merged and should ship soon.


support BibLaTeX extended name format

Description
BibLaTeX extended name format is currently incorrectly parsed. It seems enabled by default in the zotero better biblatex plugin  so I'd expect quite a few people run into this.
Steps to reproduce
.bib file:
@inproceedings{Hasselt2016,
  author    = {family=Hasselt, given=Hado P., prefix=van useprefix=false and Guez, Arthur and Hessel, Matteo and Mnih, Volodymyr and Silver, David},
  title     = {Learning Values across Many Orders of Magnitude},
  booktitle = {Advances in Neural Information Processing Systems},
  date      = {2016},
  pages     = {4287--4295},
  url       = {http://papers.nips.cc/paper/6076-learning-values-across-many-orders-of-magnitude},
  urldate   = {2017-06-07}
}

.typ file:
Citation: #cite("Hasselt2016")

#bibliography("test.bib", style: "apa")

Output:

Reproduction URL
No response
Operating system
Linux
Typst version

[ ] I am using the latest version of Typst

Needs to be fixed in https://github.com/typst/biblatex

I implemented support for the default nameparts (given, family, prefix, and suffix) in typst/biblatex#48.
It seems to work well from my limited testing. I'd be happy to further refine the implementation if needed, I'm not particularly good at Rust.


Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT

Hi, I'm trying to connect websocket on real application server, but I stuck. Websocket and the web content is in the same place. I don't get it actually where is the problem. My browser saying ERR_CONNECTION_TIMED_OUT in console log. Screen shot in the below. What am i doing wrong ?

My Laravel Echo config:
window.Echo = new Echo({
    broadcaster: 'pusher',
    key: process.env.MIX_PUSHER_APP_KEY,
    wsHost: window.location.hostname,
    wsPort: 6001,
    wssPort: 6001,
    disableStats: true,
    encrypted: true,
    enabledTransports: ['ws', 'wss'],
});

My NGINX config file looks like:
map $http_upgrade $type {
  default "web";
  websocket "ws";
}

server {
        # Listen HTTP
        listen 80;
        listen [::]:80;

        # Server Name
        server_name hidden-domain.com;

        # Redirect to HTTPS
        return 301 https://hidden-domain.com$request_uri;
}

server {
        # Listen SSL
        listen 443 ssl http2 deferred;
        listen [::]:443 ssl http2 deferred;

        # SSL Certificates
        ssl_certificate /etc/nginx/ssl/app.pem;
        ssl_certificate_key /etc/nginx/ssl/app.key;

        # SSL Config
        include h5bp/ssl/ssl_engine.conf;
        include h5bp/ssl/policy_intermediate.conf;

        # Include the basic h5bp config set
        include h5bp/basic.conf;

        # Root
        root /var/www/app/public;

        # Start Files
        index index.html index.php;

        # Server Name
        server_name hidden-domain.com;

        # Root directory
        location / {
                try_files /nonexistent @$type;
        }

        location @web {
                try_files $uri $uri/ /index.php?$query_string;
        }

        location @ws {
                proxy_pass             http://<IP_ADDRESS>:6001;
                proxy_set_header Host  $host;
                proxy_read_timeout     60;
                proxy_connect_timeout  60;
                proxy_redirect         off;
                # Allow the use of websockets
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection 'upgrade';
                proxy_set_header Host $host;
                proxy_cache_bypass $http_upgrade;
        }

        # PHP FPM
        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
                fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
        }

        # Deny htaccess
        location ~ /\.ht {
                deny all;
        }
}

broadcasting.php
'pusher' => [
            'driver' => 'pusher',
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            'app_id' => env('PUSHER_APP_ID'),
            'options' => [
                'cluster' => env('PUSHER_APP_CLUSTER'),
                'encrypted' => true,
                'host' => '<IP_ADDRESS>',
                'port' => 6001,
                'scheme' => 'https',
            ],
        ],

websockets.php
'ssl' => [
        /*
         * Path to local certificate file on filesystem. It must be a PEM encoded file which
         * contains your certificate and private key. It can optionally contain the
         * certificate chain of issuers. The private key also may be contained
         * in a separate file specified by local_pk.
         */
        'local_cert' => '/etc/nginx/ssl/app.pem',

        /*
         * Path to local private key file on filesystem in case of separate files for
         * certificate (local_cert) and private key.
         */
        'local_pk' => '/etc/nginx/ssl/app.key',

        /*
         * Passphrase for your local_cert file.
         */
        'passphrase' => null,
    ],

@ovunckesici did you solve this ERR_CONNECTION_TIMED_OUT console message?.
I'm getting this error too.

So I´ve been trying to fix this error for 3 day and finally I came up with a solution. I hope it helps. First of all, go and watch this video.
If you did everything like that guy and you are still getting ERR_CONNECTION_TIMED_OUT, you probably have eighter problem with your SSL certificate - or (like me) closed port you are using for websockets.
I strongly recommend checking your SSL certificate paths (accesibilty) and your server firewall. Just to save you a few google searches - enter
sudo ufw status verbose in your linux server and you can see the list of opened ports. If your websockets port is missing in that list, type sudo ufw allow YOUR_WEBSOCKETS_PORT_NUMBER/tcp and voila, there it is. You can check if your websockets are running by entering http(s)://your.website.running.websockets:WEBSOCKETS_PORT. You should successfully connect with OK message.
This helped me solve my mysterious ERR_CONNECTION_TIMED_OUT problem and I hope it helps you too. Happy coding!


Support for Angular 1.3

Hi.
Are there any plans to support AngularJS 1.3 ?
Regards

I've ran into an error where eventSources were undefined, which was due to a late assignment of $scope.eventSources. There should probably be a measure against that, perhaps just  $scope.eventSources = []; in uiCalendarController, otherwise it's up to the user to initialize it with an empty array.
Other than that it works fine for me with Angular 1.3.6. Cheers

Hi, anyone knows what I'm doing wrong in my example: http://plnkr.co/edit/4wTDO04c9gkcPgqzWux8?p=preview
I'm able to add events through the ng-model but all the click events like when clicking on a day or existing event don't work...(not to speak about drag&drop on events).
Does anyone have an idea? Thx

two reasons @juristr, you were not passing in the options to the calendar correctly, and you were assigning the vm.clickFunctions, as variables, after they were being set on the options object. Here is a fix, which sets the functions as a function and not a variable, allowing for the runtime context to contain its information, by the time you set it on the options. http://plnkr.co/edit/dn1c9f8M2kM0p5hDR1fR?p=preview
Closing this now, as the calendar supports AngularJS 1.3.x

@joshkurz Ya, have figured it out meanwhile. Silly mistake on my side. Anyway, thx for the Plunker.

@joshkurz if it is indeed supported why does the bower.json requires 1.2.x? here


added LuaPairsIterable extension

This adds the LuaPairsIterable extension type which indicates that a type can be iterated when passed to Lua's pairs function.
LuaTable now extends this type so it can be iterated using for...of.
This is the 2nd suggested implementation of #1023
Closes #1023

been waiting for this for a long time, thank you very much tom!


[Breaking] Refactor Backend Names

This refactor aims to improve the clarity of Burn when selecting a backend. Also, it aims to make it easier to create new backends without having to deal with unreadable associative types through the use of type aliases (FloatTensor, IntTensor, BoolTensor, FloatElem, IntElem, and Device).
There are breaking changes, but only for the naming. The type aliases don't break anything but simplify the process of creating new backends!

The description lacks mention of the fundamental rules or principles being followed. Please summarize all changes in terms of rules or principles, so others can easily follow and review your changes. This request stems from the fact that many people are accustomed to the previous convention, so adapting to the new changes will require a shift in both mindset and the code/APIs.

The description lacks mention of the fundamental rules or principles being followed. Please summarize all changes in terms of rules or principles, so others can easily follow and review your changes. This request stems from the fact that many people are accustomed to the previous convention, so adapting to the new changes will require a shift in both mindset and the code/APIs.

Agreed! I'm still working on it after an earlier self-review. More descriptions and changes are expected to better follow the Rust naming conventions!


Update governance, maintainers and create subprojects

As discussed at meetings and here, we are restructuring governance and creating subprojects.

Notation. Signatures in registries
TUF. Full TUF registry native implementation

We are also removing the inactive maintainers. We thank them for their contributions and are proud to have them in our alumni.
As this is a governance change it should be approved by 2/3 of maintainers.

LGTM

LGTM

How were these original maintainers chosen? I'm kind of surprised to not see Marina or Brandon Mitchell in the org maintainers, they've been by far the most active for the longest period of time.

LGTM.  Thanks for the long overdue change!

LGTM!

Approved by @justincormack @cyli @diogomonica @HuKeping @endophage @ecordell which is 6/8 maintainers so this passes as 2/3 supermajority as required.
@mnm678 happy to tweak project name afterwards
@JustinCappos we can go ahead and add new maintainers under the new procedures

FYI this repo has been moved over to github.com/notaryproject as part of the governance updates

post-facto LGTM


Add support for HTTP/2 Server push

A new Response class should be implemented that can be used to push resources to a client: https://asgi.readthedocs.io/en/latest/extensions.html#http-2-server-push

Added in commit: f9751932c6d4f0d8f0a6edaef511bb517f6d1595

Added in commit: f3554db56ddff177021acd61c7162400b7dda4e6


Review discoverability of API inside column selection DSL in IDE

Just putting it here to not forget to have a look at it using completion. There are new functions, new overloads, plus fixes for ColumnSet based functions
public fun SingleColumn.nameContains(text: CharSequence): ColumnSet<*> = cols { it.name.contains(text) }
public fun  ColumnSet.nameContains(text: CharSequence): ColumnSet = cols { it.name.contains(text) }

depends on https://github.com/Kotlin/dataframe/pull/372


GetxService onInit in an error GetLifeCycle

GetxService onInit in an error GetLifeCycle
The problem is that in GetLifeCycleBase, onInit is a FutureFunctional(), but it is executed synchronously. So the completion status of onInit CANNOT be obtained after Get.put is completed outside
the code is at there GetLifeCycleBase

mixin GetLifeCycleBase {
  // Internal callback that starts the cycle of this controller.
  void _onStart() {
    if (_initialized) return;
    onInit(); // <--- The problem here is that in GetLifeCycleBase,
    _initialized = true;
  }
}

example:
class DbService extends GetxService {
  Future<DbService> onInit() async { /// onInit is Future<dynamic> Function()
    print('$runtimeType delays 2 sec');
    await 2.delay();
    print('$runtimeType ready!');
    return this;
  }
}

void main() {
  TestWidgetsFlutterBinding.ensureInitialized();

   group('FimberLoggerService', () {
    setUpAll(() async {
      // Get.putAsync(DbService());
      /// ⬆ The signature and usage of this function do not match the documentation https://github.com/jonataslaw/getx/blob/master/README.md#getxservice
      /// The argument type 'DbService' can't be assigned to the parameter type 'Future<dynamic> Function()'.

      /// must to
      Get.put(DbService());
      /// or
      Get.putAsync(() async => DbService());

    })

    test("Get DbService", () {
      DbService db = Get.find(); // <--- onInit not finish
    })
}

To Reproduce
run the test case
Expected behavior
Get.putAsync may get the onInit finish OR just like doc call onInit MANUAL
Now this code can work, but it is very cumbersome
class DbService extends GetxService {
  Future<DbService> onInit() async {
    if(_initialized) return this;

    print('$runtimeType delays 2 sec');
    await 2.delay();
    print('$runtimeType ready!');
    return this;

    _initialized = true;
  }

  bool _initialized = false;
}

// in test group
  setUpAll(() async {
    await Get.putAsync(() async {
      GetxService service = GetxService();
      await service.onInit();
      return service;
    });
  })

Getx Version:
dependencies:
  get: ^4.6.6

Describe on which device you found the bug:
In test case

this code is work for me but not elegant:
import 'package:get/get.dart';
import 'package:flutter_test/flutter_test.dart';

abstract class AppService<T extends GetxService> extends GetxService {
  @override
  Future<T> onInit() async {
    if (_initialized) return this as T;

    super.onInit();
    await init();

    _initialized = true;
    return this as T;
  }

  Future<void> init() async => throw UnimplementedError();
  bool _initialized = false;
}

class DBService extends AppService {
  @override
  Future<void> init() async {
    /// do sth. only called once
  }
}

void main() {
  setUpAll(() async {
    await Get.putAsync(() => DBService().onInit());
  	DBService db = Get.find();
		// Todo: sth.
  });
}

relate issue https://github.com/jonataslaw/getx/issues/3154

Thanks for opening this issue, and you're absolutely right!
This is an architectural problem that I didn't think about at the time I created putAsync, to be honest, I used exactly the code you sent (I believe you've seen something like this on discord) for many years.
About a year ago I created a Wrapper that allows me to do this in a more elegant way, I believe I can insert it into the package.


Support GHC 9.2

Thanks.
I won't merge this until release candidates are out though.

https://hackage.haskell.org/package/hashable-<IP_ADDRESS> is released


Docket network fails to start

https://github.com/iotaledger/iota-core/tree/develop/tools/docker-network
./run.sh fails with
# github.com/iotaledger/iota-core/pkg/testsuite/mock
../../pkg/testsuite/mock/wallet_transactions.go:104:38: w.Node.Protocol.MainEngineInstance undefined (type *protocol.Protocol has no field or method MainEngineInstance)
../../pkg/testsuite/mock/wallet_transactions.go:120:38: w.Node.Protocol.MainEngineInstance undefined (type *protocol.Protocol has no field or method MainEngineInstance)

Fixed by https://github.com/iotaledger/iota-core/pull/609


Add IngressClass to manifests to be (un)installed

What this PR does / why we need it:
closes #10643
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[X] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

Hi @hickeyma.  With the new "Distributed responsibility for picking" of HIP 0010, you can go ahead and cherry-pick this commit into the release-3.8 branch right away.  This will allow the release branch to be ready when it is time to cut the next maintenance release.

@marckhouzam Good idea. Cheery picked this and others that needed picking.


Preliminary Debian 10 support

The Vagrant box breaks the tests, installing the zfs-dkms package results in the zfs kernel module erroring with "exec format error". Updating the kernel to a later version fixes this but is impractical as part of the beaker framework.
Fixes #21

Newer version of Vagrant box is available, tests might pass now.

Coverage remained the same at ?% when pulling c3ddab57fe24573b3d36fa06f0e3ab90575a6017 on debian-10 into 15f7752a17f1cb592cf15cdaccf75fe3e81d63c6 on master.


builder.build_engine - RuntimeError: Driver error with onnx_to_tensorrt.py

When running python3 yolo_to_onnx.py -m yolov4-416 from https://github.com/jkjung-avt/tensorrt_demos#demo-5-yolov4
I get these errors around the builder.build_engine lines:

Traceback (most recent call last):
File "onnx_to_tensorrt.py", line 195, in
main()
File "onnx_to_tensorrt.py", line 183, in main
engine = build_engine(
File "onnx_to_tensorrt.py", line 154, in build_engine
engine = builder.build_engine(network, config)
RuntimeError: Driver error:

Linux Ubuntu 20.04 LTS on Windows 10 WSL 2
Cuda 11-1
Cuda compilation tools, release 11.1, V11.1.105 Build cuda_11.1.TC455_06.29190527_0
Cudnn <IP_ADDRESS>
Tensorrt <IP_ADDRESS>
Python 3.8 system install default
Mentioned here too as I saw the same error there :https://github.com/NVIDIA/TensorRT/issues/875#issuecomment-749066732

I'm not sure whether CUDA and TensorRT would work correctly in a Ubuntu on WSL2 environment.  Could you try out a couple of the official TensorRT samples on your system first?

I add some references here:

CUDA on WSL User Guide
CUDA on Windows Subsystem for Linux (WSL) - Public Preview

As of today, the CUDA driver/toolkit on WSL is still a Public Preview release.  So I won't be surprised to see if there are some problems running it on certain platforms...

I'll close this issue for now as I don't fully need Tensorrt, if I need it I will install it on my windows main partition (if I can)


Question: Use where clause on JOIN

Hi, gotta say first you have a great library, I have a quick question is it possible to use where clause in populate
For example:
const author = await em.findOne(AuthorSchema, { ... }, ['books']);
I would like to add also where clause so that it gets executed like:
INNER JOIN Books ON Book.authorId = Author.id AND Book.Name = 'Lord of the rings' )

Try
const author = await em.findOne(AuthorSchema, { books : { name: 'Lord of the rings' } }, ['books']);

More info here: https://mikro-orm.io/docs/query-conditions

To adjust the on condition you'd have to use a QB, if you are fine with where condition, then what Kevin is saying is the way to go.

@B4nan @thekevinbrown
Thank you for ansering


Effect for class instantiation

Is it possible to instantiate a class (new Class()) through an effect?
The closest I got to it was:
class Foo {
    constructor(public num: number) {}
}

function create<T>(SomeClass: new (...args) => T, ...args) {
    return new SomeClass(...args);
}

function* theSaga() {
    const foo = yield call(create, Foo, 3);
    console.log(foo);
}

While I'm not too opposed to the extra create helper method, it'd be nice if I could achieve this without it:
yield call(Foo, 3); // call overload (my personal preference)
yield create(Foo, 3); // new effect

you could also wrap this like this:
export const create = (someClass, ...args) => call(() => new someClass(...args))

that way you would be able to use create as an effect, although ofc it needs to be imported from the other place than those which are built-in
I prefer not adding this to the core, it doesnt seem useful for everybody and its easily implementable on the user's side. That being said I would like to explore possibilities of being able to register ur own effects in the future, so stay tuned.

@Andarist Would you explain how to use the create wrapper ? I do not understand the purpose of call for calling arrow function ?
Why not export const create = (someClass, ...args) => { return new someClass(...args) }


use inverse midpoint precondition for H matrices with Hansen-Bliek-Rohn

there can be cases where numerical instability occurs also for H-matrices, see example in juliacon talk

Codecov Report

Merging #55 (3f880d2) into main (123f0d5) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #55      +/-   ##
==========================================
- Coverage   96.66%   96.62%   -0.04%
==========================================
  Files          10       10
  Lines         270      267       -3
==========================================
- Hits          261      258       -3
  Misses          9        9

Impacted Files
Coverage Δ

src/solvers/solve.jl
100.00% <ø> (ø)

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 123f0d5...3f880d2. Read the comment docs.

maan codecov is such a joy...


add documentation for custom features

Add doc and example json file for add custom features and analysis

In the second commit:

Refine doc
For ComboCountAnalysis, the json file only takes list but in the code it takes tuple. Add a type casting in analysis.py pass features as a tuple.