[stable/kibana] Unable to setup X-Pack login with kibana

Is this a request for help?:
YES
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Helm Version:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

Kubernetes Version:
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
kibana/stable
What happened:
After setting xpack enable value, I am still not able to see the login page while opening dashboard. In fact, it is not asking for username:password at all.
What you expected to happen:
After enabling xpack security setting, the kibana UI should open a login page where we can login with username & password.
How to reproduce it (as minimally and precisely as possible):
Install kibana with helm.
values.yaml file:
image:
  repository: "docker.elastic.co/kibana/kibana"
  tag: "6.5.1"
  pullPolicy: "IfNotPresent"

commandline:
  args: []

env: {}
  # All Kibana configuration options are adjustable via env vars.
  # To adjust a config option to an env var uppercase + replace `.` with `_`
  # Ref: https://www.elastic.co/guide/en/kibana/current/settings.html
  #
  # ELASTICSEARCH_URL: http://elasticsearch-client:9200
  # SERVER_PORT: 5601
  # LOGGING_VERBOSE: "true"
  # SERVER_DEFAULTROUTE: "/app/kibana"

files:
  kibana.yml:
    ## Default Kibana configuration from kibana-docker.
    server.name: kibana
    server.host: "0"
    elasticsearch.url: http://elasticsearch-client:9200

service:
  type: ClusterIP
  externalPort: 443
  internalPort: 5601

  annotations: {}
    # Annotation example: setup ssl with aws cert when service.type is LoadBalancer
    # service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:us-east-1:EXAMPLE_CERT
  labels: {}
    ## Label example: show service URL in `kubectl cluster-info`
    # kubernetes.io/cluster-service: "true"
  ## Limit load balancer source ips to list of CIDRs (where available)
  # loadBalancerSourceRanges: []

ingress:
  enabled: true
  hosts:
    - kibana.xyz.net
  annotations:
    kubernetes.io/ingress.class: nginx
    kubernetes.io/tls-acme: "true"
  tls:
    - secretName: efk-secret
      hosts:
        - kibana.xyz.net

serviceAccount:
  # Specifies whether a service account should be created
  create: false
  # The name of the service account to use.
  # If not set and create is true, a name is generated using the fullname template
  # If set and create is false, the service account must be existing
  name:

livenessProbe:
  enabled: false
  initialDelaySeconds: 30
  timeoutSeconds: 10

readinessProbe:
  enabled: false
  initialDelaySeconds: 30
  timeoutSeconds: 10

# Enable an authproxy. Specify container in extraContainers
authProxyEnabled: false

extraContainers: |
# - name: proxy
#   image: quay.io/gambol99/keycloak-proxy:latest
#   args:
#     - --resource=uri=/*
#     - --discovery-url=https://discovery-url
#     - --client-id=client
#     - --client-secret=secret
#     - --listen=<IP_ADDRESS>:5602
#     - --upstream-url=http://<IP_ADDRESS>:5601
#   ports:
#     - name: web
#       containerPort: 9090
resources: {}
  # limits:
  #   cpu: 100m
  #   memory: 300Mi
  # requests:
  #   cpu: 100m
  #   memory: 300Mi

priorityClassName: ""

podAnnotations: {}
replicaCount: 1
revisionHistoryLimit: 3

# To export a dashboard from a running Kibana 6.3.x use:
# curl --user <username>:<password> -XGET https://kibana.yourdomain.com:5601/api/kibana/dashboards/export?dashboard=<some-dashboard-uuid> > my-dashboard.json
# A dashboard is defined by a name and a string with the json payload or the download url
dashboardImport:
  timeout: 60
  xpackauth:
    enabled: true
    username: www-admin
    password: xxxxxxxx
  dashboards: {}

# List of plugins to install using initContainer
# NOTE : We notice that lower resource constraints given to the chart + plugins are likely not going to work well.
plugins:
  # set to true to enable plugins installation
  enabled: false
  # set to true to remove all kibana plugins before installation
  reset: false
  # Use <plugin_name,version,url> to add/upgrade plugin
  values:
    # - elastalert-kibana-plugin,1.0.1,https://github.com/bitsensor/elastalert-kibana-plugin/releases/download/1.0.1/elastalert-kibana-plugin-1.0.1-6.4.2.zip
    # - logtrail,0.1.30,https://github.com/sivasamyk/logtrail/releases/download/v0.1.30/logtrail-6.4.2-0.1.30.zip
    # - other_plugin

persistentVolumeClaim:
  enabled: true
  existingClaim: false
  annotations: {}

  accessModes:
    - ReadWriteOnce
  size: "5Gi"
  storageClass: "gp2"

# default security context
securityContext:
  enabled: false
  allowPrivilegeEscalation: false
  runAsUser: 1000
  fsGroup: 2000

Anything else we need to know:
No

So, should take it as "Not possible with helm charts"? Because I tried changing image in elasticsearch as well. But after adding xpack.security.enabled = true, the elasticsearch deployment was causing issue with authentication. I believe it was looking for the appropriate credentials like username:password which I couldn't find in the elasticsearch helm charts either (or maybe I will double-check this).

For anyone down the line who comes across this...
I'm using an Elasticsearch operator, non-oss, version 6.8.0. TLS + Username/Password auth is required when xpack.security: enabled with the basic license.
I'm able to use version 3.0.0 of the [stable/kibana]. Kibana's values.yaml (excerpt and not-for-prod):

Get the password for the elastic user (change secret name as-needed):

echo $(kubectl get secret elastic-user -o=jsonpath='{.data.elastic}' | base64 --decode)

Use those credentials here to create the user and assign it to kibana_system role:

 curl -ks -X PUT "https://elastic:password@elasticsearch:9200/_security/user/svc_kibana" -H 'Content-Type: application/json' -d'
{
  "password" : "PASSWORD_HERE",
  "roles" : [ "kibana_system" ],
  "full_name" : "",
  "email" : ""
}'

Set the credentials in Kibana:

files:
  kibana.yml:
    elasticsearch.hosts: "https://elasticsearch-client:9200"
    elasticsearch.username: svc_kibana
    elasticsearch.password: PASSWORD_HERE
    elasticsearch.ssl.verificationMode: "none"


Choose preferred worker from worker list

What changes are proposed in this pull request?
Chooses a preferred worker from worker list to fetch files

alluxio-bot, merge this please


Add docs about needed cluster roles for e2e operator tests

Description of the change:
Add docs about the needed permissions for running e2e operator tests.
Motivation for the change:
As discussed in #1082 this is useful information for users in environments where they might not be running as cluster-admin by default.
Closes #1082

are changes to /website supposed to be done manually? I submitted a previous docs PR that didn't fail the travis build.

Hi @jberkhahn,
The docs in a transition period. Temporary, we need to copy to keep both equals. So, yes. For we are able to move forward and it passes in the CI you need to perform the same changes in website/content/en/docs/test-framework/writing-e2e-tests.md. Could you please do that?

/retest

this should be good to go?


Rancher masters used outdated certificates

Rancher versions:
rancher/server or rancher/rancher: v2.0.8
rancher/agent or rancher/rancher-agent: v2.0.8
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable): v1.11.2
Docker version: (docker version,docker info preferred) 1.13.1
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
3.10.0-514.16.1.el7.x86_64
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Bare-metal
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA RANCHER
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
When creating a worker cluster with multiple masters (say 3), some of masters have to old kube-apiserver.pem that only contains one domain in the X509v3 Subject Alternative Name rather than 3 domains.
Results:
Because of outdated kube-apiserver certificate in some kube masters, when users run kubectl exec -it <pod-name> sh, or kubectl get pod, etc. k8s requests from rancher server hit these masters, it returns 500 and error messages like:
unable to upgrade connection: error dialing backend: x509: certificate is valid for 10.x.y.z, <IP_ADDRESS>, <IP_ADDRESS>, not 10.x.y.t

Workaround fix: manually synchronize kube-apiserver.pem between master nodes and restart kube-apiserver container.

I just encountered the exact same issue on one of my clusters : kube 1.11.2 deployed on custom nodes by rancher 2.0.8.
Updated rancher to 2.1.0 and updated the cluster in the GUI to trigger provisionning, issue still present.
@canhnt workaround works though 👍

Please provide steps to reproduce the issue, if not, all the details available in the setup you have encountered it that we can use to run tests/reproduce. How many nodes with what roles are in the cluster and did it start happening on creation of a new cluster or after adding nodes, and if the latter, what node with what role was added.

@superseb Here's what I can recall :

Rancher 2.0.8, create new cluster with custom nodes, kube 1.11.2
Add node "A" master,worker,etcd and specify internal IP "IP1"
Add node "B" master,worker,etcd and specify internal IP "IP2"
Add node "C" master,worker,etcd and specify internal IP "IP3"

Everything goes green, except kubectl port-forward ... on a pod running on C gives one of the following errors 2/3 of times :
unable to upgrade connection: error dialing backend: x509: certificate is valid for IP1 ... not IP3
unable to upgrade connection: error dialing backend: x509: certificate is valid for IP1, IP2 ... not IP3

Inspection of kube-apiserver.pem on the 3 nodes shows the following :

Node A :

X509v3 Subject Alternative Name:
  DNS:..., IP Address: *IP1*, ...

Node B :

X509v3 Subject Alternative Name:
  DNS:..., IP Address: *IP1*, IP Address: *IP2*, ...

Node C :

X509v3 Subject Alternative Name:
  DNS:..., IP Address: *IP1*, IP Address: *IP2*, IP Address: *IP3*, ...

After copying kube-apiserver.pem from node C to node A and B, the issue disapeared.
Versions :

OS: Ubuntu 16.04
Kernel: 4.15.0-36
Docker: 17.03.2-ce

The issue started happening a few days after the cluster was created. In the interval, we :

migrated to rancher 2.1.0.
restarted the nodes

A consequence of the restart could be that the Pod migrated from node A to node C, which I guess could have made the issue visible.
Hope that helps !

Same exact issue here and the work around fixed it for now. Our test cluster is 3 nodes so it was exactly as described in the previous comment where the earlier nodes did not have the newest nodes in the SAN of the cert.

We have the same issue with our newly created 2.1.1 cluster, with on-prem nodes.
As we add new control plane nodes, the old ones do not get updated certificates.
To add some more information:
We added 3 nodes, you can find the nodes below with the time they were added to the cluster and the Subject Alternative Names content of the local /etc/kubernetes/ssl/kube-apiserver.pem certificate.
cetxcosv005 <IP_ADDRESS>
    Added to cluster at 2018-11-06T11:52:49.178279948Z
    Subject Alternative Names: cetxcosv005, localhost, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>

cetxcosv003 <IP_ADDRESS>
    Added to cluster at 2018-11-06T11:56:56.751949062Z
    Subject Alternative Names: cetxcosv003, cetxcosv005, localhost, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>

cetxcosv004 <IP_ADDRESS>
    Added to cluster at 2018-11-06T11:59:15.920508236Z
    Subject Alternative Names: cetxcosv004, cetxcosv003, cetxcosv005, localhost, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>

We used the creation date of the share-mnt container to determine the time at they were added to the cluster.

We get the same issue. We spotted it because Jenkins kubernetes plugin return the error:
hudson.remoting.ProxyException: io.fabric8.kubernetes.client.KubernetesClientException: error dialing backend: x509: certificate is valid for x.x.x.x ,.x.x.x.x, x.x.x.x not y.y.y.y
This happened after we add a second master node and try to run a build using Jenkins master and slaves from that node.
I check the /etc/kubernetes/ssl/kube-apiserver.pem of kube-apiserver container on the first master node and I found that the certificate is not updated with the new node. So i copied the kube-apiserver.pem from new node to the old one like @dalsh and all works.
For who have the same problem in Jenkins a fast fix is to disable https check. This configuration could be check on Jenkins Kubernetes plugin config: Disable https certificate check

Possible root cause here is:
apiEndpoint in API for cluster is set to IP of a node with the controlplane role. This could be the one thats hit or is routed to another when its unavailable. The request made to the kube-apiserver is using the node IPs but the connection is made to the apiEndpoint IP, long story short, the IP of the apiEndpoint of the cluster has to be in the certificate, and due to the certificates not being refreshed, it might hit a certificate with that IP not being present.
I've seen this when standing up clusters and having nodes join randomly (based on boot time and Docker install time), and then break after stopping the kube-apiserver on one or more controlplane nodes while running while true; do kubectl -v9 get nodes; sleep 1; done and seeing:
"message": "Error: 'dial tcp IP_OF_NODE2:6443: connect: connection refused'\nTrying to reach: 'https://IP_OF_API_ENDPOINT:6443/api/v1/nodes?limit=500'"

Indicating it tries to connect to apiEndpoint IP but actually connects to IP_OF_NODE2.
After some time, you will see:
"Error: 'x509: certificate is valid for x, x, <IP_ADDRESS>, <IP_ADDRESS>, not x'\nTrying to reach: 'https://x:6443/api/v1/namespaces/default/pods?limit=500'"
      }
    ]

Because controlplane nodes are targeted randomly, and the apiEndpoint only changes when the node is deleted from the cluster, it is not immediately noticeable as it requires changes with nodes in the cluster. There might also be a trigger when multiple nodes are added simultaneously but I don't have a solid reproducer yet.

Steps to reproduce are in https://gist.github.com/superseb/36919dba64a18cb40951228254660f03

Can be tested with rancher/rancher:v2.2.3-rc2

➤ Sowmya commented:
Validated the issue on rancher:v2.2.2

Deployed a cluster with 1 etcd, 1 ctrl, 1 worker nodes. (control plane#1)
scaled up the number of control plane nodes to 2(add control plane#2)
After the cluster becomes Active scale up the number of Control plane nodes to 3. (add control plane #3)

exec into the control plane nodes, and exec into kube-apiserver container*.*
Observations:
On control Plane#1:
DNS:sowmya-test-ctrl-1, DNS:localhost, DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>
On Control Plane#2:
DNS:sowmya-test-ctrl-1, DNS:sowmya-test-ctrl-2, DNS:localhost, DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>
On Control Plane#3:
DNS:sowmya-test-ctrl-1, DNS:sowmya-test-ctrl-3, DNS:sowmya-test-ctrl-2, DNS:localhost, DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:x.x.x.x, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>

validated this issue.
In rancher:v2.2.2 - steps taken:

Created a custom cluster - 1etcd, 1 control plane (Control Node#1) , 1 worker node.
Scale the number of control planes to 10 nodes - automation provisioning.
Wait until the cluster comes to Active state
Executed the steps mentioned in -
https://gist.github.com/superseb/36919dba64a18cb40951228254660f03#run-commands-to-retrieve-info
Output received - $ip is GOOD on certificate.
Verified that Control Node#1 did not have certificate for kube-apiserver with all names and IPs of each controlplane node added in step 2.
Executed steps - 1 to 6, 4 to 5 times.

In rancher:v2.2.3-rc3 - steps taken:

Created a custom cluster - 1etcd, 1 control plane (Control Node#1) , 1 worker node.
Scale the number of control planes to 10 nodes - automation provisioning.
Wait until the cluster comes to Active state
Executed the steps mentioned in -
https://gist.github.com/superseb/36919dba64a18cb40951228254660f03#run-commands-to-retrieve-info
Output received - $ip is GOOD on certificate.
Verified that Control Node#1 had certificate for kube-apiserver with all names and IPs of each controlplane node added in step 2. Also verified the other control nodes had certificate for kube-apiserver with all names and IPs of each controlplane node.
Executed steps - 1 to 6, 2 - 3 times.


No clippy on macOS CI

Partial workaround for https://github.com/target/lorri/issues/258.
Overview

Cachix does not work on macOS (https://github.com/cachix/cachix/issues/228) and Hydra does not successfully build clippy (https://github.com/NixOS/nixpkgs/pull/77327, https://github.com/NixOS/nixpkgs/issues/77358). As a result, in order to run clippy, we build it from scratch on every CI run on macOS. This adds about 20 minutes of build time.
There is no need to run clippy both on macOS and on Linux. So to circumvent this issue, this PR changes the CI setup slightly so that lints (including clippy) are only run on Linux.
Checklist

[x] Updated the documentation (code documentation, command help, ...)
[x] Tested the change (unit or integration tests)
[ ] Amended the changelog in release.nix (see release.nix for instructions)

PTAL. The effect of this is to reduce the time  nix-build -A allBuildInputs shell.nix > ./shell-inputs takes on macOS from 1244 seconds (20 minutes) to 95 seconds (1.5 minutes).

before: https://travis-ci.org/target/lorri/jobs/634125087#L559 (roughly - this is from a different PR, but we don't seem to be running CI on master so this is as good a comparison as I can find right now)
after: https://travis-ci.org/target/lorri/jobs/635266664#L558

@Profpatsch @grahamc PTAL

Go ahead and rebase to resolve conflicts, regenerate the .yml and merge.


Issue with the header nav under Documentation tab

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
Navigate from the home page of the website to Documentation which will land you over here.

One can observe extra padding under the navigation tabs. But it's the not same when you navigate to the Setup/ any other tab other than Home. Refer the below screenshot.

Proposed Solution:
Navbar padding (Home tab) must be consistent with other tabs.
Page to Update:
https://kubernetes.io/docs/home/

https://kubernetes.io/docs/home/

/good-first-issue

I wanted to show a sample of how you wanted it to be.

Is this ok??

/cc

/remove-lifecycle stale


Pre release cleanup

Purpose
Last few changes before publishing the first release.
What the code is doing

Set the initial version number to 0.1.0 and update minimum python to 3.8
create the initial root directory entry so the package works on an empty blob storage container
some minor refactoring I was planning to use for additional improvements but didn't pan out

Testing
Re ran test.py
Time estimate
5 min

Once this is merged I will push the v0.1.0 git tag to trigger the pypi release. Might have some badge updates after that.


using os.PathListSeparator as separator between

- What I did
Replace separator ':' in cli cp with os.PathListPeparator. in api/client/cp.go.
Change separator ':' for os.PathListSeparator in integration-cli/docker_cli_cp_test.go.
- How I did it
- How to verify it
testcase in docker_cli_cp_test.go modified accordly for testing
- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)
containerID and path location in cp command
for enhancement #9932
Signed-off-by: Lin Lu<EMAIL_ADDRESS>modify separator char in cli cp testcase
Signed-off-by: Lin Lu<EMAIL_ADDRESS>

I don't think this is righy. container:/path/to/ is not a list of path ; it has a meaningthe path inside the container).

I kind of agree with @vdemeester, the API should be the same across platforms.The client just needs to special case driver letter handling (which it already does for the -v flag, btw.)

I see where you're coming from, and agree that the current choice of using : isn't ideal, but changing this would be too much of a breaking change, so I don't think we should do this.
Thanks so much for contributing though, it's really appreciated


Disable the Consent-related API endpoints if EB's consent feature is off

Makes behaviour more explicit and does not expose code paths that are not needed.

It seemed so simple but it appears I broke the tests of the existing api feature flags... but why? @MKodde any idea?

Nice addition!
The test breaks because of the disableConsentApiFeatureFor and disableRemoveConsentApiFeatureFor methods that need to take into account the existance of the eb.feature_enable_consent feature flag. The test only knows about the feature flags that are explicitly configured in test. The controller actions that where tested in the failing tests referenced to feature flags that where not configured.

Build only fails on security (non)vulnerability in deps

Build only fails on security (non)vulnerability in deps

Fixing that in #1190

@tbeekman Makes sense?


[CWS] Specify accepted types for set action value field

What does this PR do?
Add missing type information for the set action value field.
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge

/merge


⚠ Universität Osnabrück has degraded performance

In 8a3a691, Universität Osnabrück (https://www.uni-osnabrueck.de) experienced degraded performance:

HTTP code: 200
Response time: 3550 ms

Resolved: Universität Osnabrück performance has improved in 23406e1.


New calendar view

new request for #470 that fits into master

I had some new ideas, that i will implement:

use same filters like the board and save selection (localstorage)
a button to reset all filters
refresh calander periodically like the board

Removed Merge conflicts, added the things i wanted, now its your turn ;)

For people reviewing, this is an implementation of https://github.com/fguillot/kanboard/issues/383
@BlueTeck - I think it's usually best to commit unrelated changes in separate PRs. It's easier for people to review that way. In this instance, the swimlane colour option is probably great, but in a separate PR, people would be able to make suggestions :)

@oparoz the swimlane color option is a filter in the calendar view, so its correct here ;)

Ah, cool :)

cool, give me the week to review and test that.

I merged and improved your pull-request. Let me know if there is any issue.

:thumbsup: nice code enhancements :)


Fixed 'finish' button label, that changed due to PF4 upgrade

Signed-off-by: Vanessa<EMAIL_ADDRESS>

@enmasse-ci run tests testcase=common.console.**


chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.26.3

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.26.2 -> v1.26.3

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.26.3
Compare Source
Bug Fixes

deps: update gomod (#736) (c30411a)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline


Updated +page.svelte

Added Pranjal Kumar( @pranjal-barnwal ) in the contributors list for contributing in FavIcon Generator

Also FavIcon generator hasn't been yet added.
Team: 77
Repo: pranjal-barnwal/developerstar

@pranjal-barnwal We haven't added the Favicon Generator yet. Possible for you to create a new branch and add the relevant code from your repo to this? Otherwise, will have to wait to be included in the next release.


RFP - arduino-cli

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL :https://github.com/arduino/arduino-cli
Direct download URL for the software / installer : https://arduino.github.io/arduino-cli/installation/#use-the-install-script
Software summary / short description: arduino command line interface

Package submitted: https://chocolatey.org/packages/arduino-cli/0.9.0


[2.2.2-patch]Support helm install with app info

Inject cluster name, project name and default registy parameters as
extra answers values when helm installing.
We are no longer storing them in app answers like the old default
registry parameter.

Closing this PR because we have same commit in master and release/v2.2 branches. Have small fixes of above comments in separate PRs.


it doesn't import in Google Colab

Hello dear Kira
I'm working on your seg_grad cam code but unfortunately when I want to import Seggradcam libraries it doesn't work, I face this error:
`---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
 in ()
----> 1 import seggradcam.metrics
3 frames
/usr/local/lib/python3.7/dist-packages/keras/backend.py in ()
35 from tensorflow.python.distribute import distribute_coordinator as dc
36 from tensorflow.python.distribute import distribute_coordinator_context as dc_context
---> 37 from tensorflow.python.eager.context import get_config
38 from tensorflow.python.framework import config
39 from keras import backend_config
ImportError: cannot import name 'get_config' from 'tensorflow.python.eager.context' (/usr/local/lib/python3.7/dist-packages/tensorflow/python/eager/context.py)

NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.
To view examples of installing some common dependencies, click the
"Open Examples" button below.
---------------------------------------------------------------------------`
DO you have any idea?
Thanks

I get it please instead of using from keras import backend as K
use :
from tensorflow.keras import backend as K

@rezadarooei we might have different tensorflow versions. I didn't test the code in Colab.


Bug in unless with conditional assignment

Something like:
unless foo ||= bar
    baz()

...is compiled as:
if (!foo || (foo = bar)) {
    baz();
}

...which is not applying the 'not' operator to the entire result.
I was expecting this:
if (!(foo || (foo = bar))) {
    baz();
}

The below examples all have a falsy condition result, but swap the assignment result and position of the conditional assignment. I believe the last example is incorrect. This is on master (ef0cb46b at the time of writing) and 1.2.0.
# coffee -s
foo = null
foo ||= no
unless foo
  console.log('yay')
^D
yay

# coffee -s
foo = null
unless foo ||= no
  console.log('yay')
^D
yay

# coffee -s
foo = null
foo ||= yes
unless foo
  console.log('boo')
^D

# coffee -s
foo = null
unless foo ||= yes
  console.log('boo')
^D
boo

Yep, it looks like ||= isn't being negated properly. We're not adding the necessary parentheses.


inherit_trait_points_from = BIOLOGICAL works

but cwtools marks it as error
in Archetypes

Can you edit archetypes.cwt and add.this?

Cool, you can close the issue


Check bazel packages integrity.

Something along these lines, @veblush.

This is for securing #22149 after merging it.


Update .gitignore to ignore .pdf files

What do you think about this?
I added .pdf files to the gitignore. Then when we work on all these branches and only pass LaTeX code between branches and not .pdf files. When we merge to Master we can then generate a .pdf file and upload it manually using the browser.
It will make the syncing faster but it requires that we are remember to update all .pdfs effected. What do you think?
Comment below and if both of you agree, then the second to agree and merge the PR.

I think it makes sense to not sync the PDFs. The only problem would be if someone couldn't compile the TeX files in their own computer -- that happened to you at some point, didn't it, @kbjarkefur? But I don't think anyone who's working on this project has that problem anymore.

true, but we would have fixed that at that computer if it hadn't been the case that I was about to get a new computer.
@mrimal , feel free to merge the branch if you agree


Add snake game to 404 error page

I have idea for a new feature for jQuery Terminal
The game was created for pre tag it would be nice to add to 404 page
https://codepen.io/jcubic/pen/YzwoaBv

Game added.


Existing Schema retriveing One to Many from Legacy Database

HI guys,
I am struggling with associating two entities with golang's gorm library.
I am practicing with an old wordpress db i have attached the ERD to this thread.
I have defined a Post and an Author model, but i can't seem to figure out the right combination for associating them.
Currently i return the post without any authors.. they are return as am empty object.
My definition is as follows.
// Author model
type Author struct {
	Id       int64  `gorm:"column:ID;primary_key:yes"json:"id"`
	Name     string `gorm:"column:display_name"json:"name"`
	NickName string `gorm:"column:user_nicename"json:"nickname"`
	Email    string `gorm:"column:user_email"json:"email"`
	URL      string `gorm:"column:user_url"json:"url"`
	Post     []Post `gorm:"foreignkey:post_author;"json:"-"`
}

// TableName Method
func (a Author) TableName() string {
	return "wp_users"
}

package models

// Post model
type Post struct {
	Id            int64        `gorm:"column:ID; primary_key:yes"json:"id"`
	Type          string       `gorm:"column:post_type"json:"type"`
	Slug          string       `gorm:"column:post_name"json:"slug"`
	URL           string       `gorm:"column:guid"json:"url"`
	Status        string       `gorm:"column:post_status"json:"status"`
	Title         string       `gorm:"column:post_title"json:"title"`
	Content       string       `gorm:"column:post_content"json:"content"`
	Excerpt       string       `gorm:"column:post_excerpt"json:"excerpt"`
	Date          string       `gorm:"column:post_date"json:"created_at"`
	Modified      string       `gorm:"column:post_modified"json:"modified_at"`
	Categories    []Category   `json:"categories"`
	Tags          []Tag        `json:"tags"`
	Author        Author       `gorm:"foreignkey:ID;"json:"author"`
	Comments      []Comment    `json:"comments"`
	Attachments   []Attachment `json:"attachments"`
	CommentCount  string       `gorm:"column:comment_count"json:"comment_count"`
	CommentStatus string       `gorm:"column:comment_status"json:"comment_status"`
	Thumbnail     string       `sql:"-"json:"-"`
	CustomFields  string       `sql:"-"json:"-"`
}

// TableName Method
func (p Post) TableName() string {
	return "wp_posts"
}

Thanks
See WP ERD diagram here http://i.stack.imgur.com/LF0fR.png

Hello @ikennaokpala
Gorm won't query relations but you need to query it by yourself with
db.Model(&post).Related(&post.Comments)

I tried it and it did not add the comments to the results that was returned.

Please checkout https://github.com/jinzhu/gorm#preloading-eager-loading to see if it could resolve your issue, please reopen it if it still doesn't work.

Thanks i will check it out..
On Wed, Feb 11, 2015 at 11:52 AM, Jinzhu<EMAIL_ADDRESS>wrote:

Closed #321 https://github.com/jinzhu/gorm/issues/321.
—
Reply to this email directly or view it on GitHub
https://github.com/jinzhu/gorm/issues/321#event-233869208.

--
Ikenna


Support configuring TLS min/max version and elliptic curves

Describe the feature request
Some companies have very strict security policies for the TLS settings they use in their systems. These policies applies also to SDS and webhook listeners exposed by istiod, but currently it's possible to configure only TLS ca, cert, key and cipher suites.
There is no option to specify TLS min/max version and elliptic curves, so I would like to add 3 additional arguments for these parameters: --tls-min-version, tls-max-version and tls-ecdh.
This may be important especially for users who need Support For Extended TLS Settings.
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

I'm closing as we decided on the community call today.


Cannot validate response with empty body if there is a default response with a body.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce

Create a schema with the following responses:

    responses:
      201:
        description: Resource is successfully created
      default:
        description: Unexpected error
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Error'

Call the validate()method of the RequestValidator with arguments Response, Path, Operator. The response has status 201, body null, and no Content-Type header (complying with the schema above).

Validation fails with message: Invalid response. [Body content type cannot be determined. No 'Content-Type' header available. (code: 202)]

Expected behavior
201 must have no body (and no Content-Type). All other responses must have a body with Content-Type application/json and match the schema.

Hi and welcome,
In fact, the only required field is description for any response Object.
I'll check this in few hours. Scanning source code on mobile phone isn't really efficient ;)

Hey, thanks for the quick response and fix. I confirm this solves the issue. Cheers, Fabio.


Compilation error on openSUSE Tumbleweed

backscrub used to build just fine on my system, and it does not any more. Since Tumbleweed is tumbling ahead, I can't really go back to the working state.
This is the end of the compilation, the full  output is attached.
[ 11%] Building CXX object _deps/flatbuffers-build/CMakeFiles/flatbuffers.dir/src/idl_parser.cpp.o
In file included from /home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/base.h:217,
                 from /home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/idl.h:24,
                 from /home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/src/idl_parser.cpp:23:
/usr/include/absl/strings/string_view.h:52:26: error: ‘string_view’ in namespace ‘std’ does not name a type
   52 | using string_view = std::string_view;
      |                          ^~~~~~~~~~~
/usr/include/absl/strings/string_view.h:52:21: note: ‘std::string_view’ is only available from C++17 onwards
   52 | using string_view = std::string_view;
      |                     ^~~
/usr/include/absl/strings/string_view.h:693:8: error: ‘string_view’ does not name a type
  693 | inline string_view ClippedSubstr(string_view s, size_t pos,
      |        ^~~~~~~~~~~
/usr/include/absl/strings/string_view.h:704:11: error: ‘string_view’ does not name a type
  704 | constexpr string_view NullSafeStringView(const char* p) {
      |           ^~~~~~~~~~~
/home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/base.h:219:23: error: ‘string_view’ in namespace ‘absl’ does not name a type
  219 |         typedef absl::string_view string_view;
      |                       ^~~~~~~~~~~
In file included from /home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/idl.h:25:
/home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/flatbuffers.h:561:16: error: ‘string_view’ in namespace ‘flatbuffers’ does not name a type
  561 |   flatbuffers::string_view string_view() const {
      |                ^~~~~~~~~~~
/home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/flatbuffers.h:1487:44: error: ‘flatbuffers::string_view’ has not been declared
 1487 |   Offset<String> CreateString(flatbuffers::string_view str) {
      |                                            ^~~~~~~~~~~
/home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/flatbuffers.h: In member function ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateString(int)’:
/home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/flatbuffers.h:1488:29: error: request for member ‘data’ in ‘str’, which is of non-class type ‘int’
 1488 |     return CreateString(str.data(), str.size());
      |                             ^~~~
/home/oscar/Apps/teams-cam/backscrub/build/flatbuffers/include/flatbuffers/flatbuffers.h:1488:41: error: request for member ‘size’ in ‘str’, which is of non-class type ‘int’
 1488 |     return CreateString(str.data(), str.size());
      |                                         ^~~~
make[2]: *** [_deps/flatbuffers-build/CMakeFiles/flatbuffers.dir/build.make:76: _deps/flatbuffers-build/CMakeFiles/flatbuffers.dir/src/idl_parser.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:4023: _deps/flatbuffers-build/CMakeFiles/flatbuffers.dir/all] Error 2
make: *** [Makefile:156: all] Error 2
/home/oscar/Apps/teams-cam

buildlog.zip

Which version of GCC are you using?
This looks like a problem with the 3rd-party flatbuffers library. Have a look at their bug tracker too if you can find any reports about similar issues.

gcc version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,ada,go,d,jit --enable-offload-targets=nvptx-none,amdgcn-amdhsa, --enable-offload-defaulted --without-cuda-driver --enable-host-shared --enable-checking=release --disable-werror --with-gxx-include-dir=/usr/include/c++/12 --enable-ssp --disable-libssp --disable-libvtv --enable-cet=auto --disable-libcc1 --enable-plugin --with-bugurl=https://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --with-slibdir=/lib64 --with-system-zlib --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-libphobos --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function --program-suffix=-12 --without-system-libunwind --enable-multilib --with-arch-32=x86-64 --with-tune=generic --with-build-config=bootstrap-lto-lean --enable-link-mutex --build=x86_64-suse-linux --host=x86_64-suse-linux
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.1.1 20220629 [revision<PHONE_NUMBER>aa7e31c3939b859bbfa2e16919639f] (SUSE Linux)

I did a testbuild of flatbuffers. Version 2.0.6 fails with a very similar error.
master compiles without any issues.

Okay, looks like we'll need to try to get this dependency updated somehow then …

OK, the dependency chain we have currently:
backscrub -> tensorflow/v2.8.0 -> flatbuffers/v1.12.0 (see <~TFLITE>/tools/cmake/modules/flatbuffesr.cmake).
Shifting our dependency to tensorflow/v2.9.0 might fix, as that depends on flatbuffers/v2.0.5: @oshikore can you please test compile flatbuffers @ v2.0.5?
If we need to go newer, then our only option at present is to pull flatbuffers/master ourselves and convince TFLITE cmake not to, since tensorflow @ master depends on the known broken flatbuffers v2.0.6. I'll take a look at this just in case...

Run cmake:
> cmake . -D FLATBUFFERS_CXX_FLAGS="-Wno-error"
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Warning at CMake/Version.cmake:22 (message):
  git describe failed with exit code: 128
Call Stack (most recent call first):
  CMakeLists.txt:13 (include)

-- Proceeding with version: <IP_ADDRESS>
-- extend CXX_FLAGS with -Wno-error
-- CMAKE_CXX_FLAGS:  -std=c++0x -Wall -pedantic -Werror -Wextra -Werror=shadow -faligned-new -Werror=implicit-fallthrough=2 -Wunused-result -Werror=unused-result -Wunused-parameter -Werror=unused-parameter -fsigned-char -Wno-error
-- `tests/monster_test.fbs`: add generation of C++ code with '--no-includes;--gen-compare'
-- `tests/monster_test.fbs`: add generation of binary (.bfbs) schema
-- `tests/namespace_test/namespace_test1.fbs`: add generation of C++ code with '--no-includes;--gen-compare;--gen-name-strings'
-- `tests/namespace_test/namespace_test2.fbs`: add generation of C++ code with '--no-includes;--gen-compare;--gen-name-strings'
-- `tests/union_vector/union_vector.fbs`: add generation of C++ code with '--no-includes;--gen-compare;--gen-name-strings'
-- `tests/optional_scalars.fbs`: add generation of C++ code with '--no-includes;--gen-compare'
-- `tests/native_type_test.fbs`: add generation of C++ code with ''
-- `tests/arrays_test.fbs`: add generation of C++ code with '--scoped-enums;--gen-compare'
-- `tests/arrays_test.fbs`: add generation of binary (.bfbs) schema
-- `tests/monster_test.fbs`: add generation of C++ embedded binary schema code with '--no-includes;--gen-compare'
-- `tests/monster_extra.fbs`: add generation of C++ code with '--no-includes;--gen-compare'
-- `samples/monster.fbs`: add generation of C++ code with '--no-includes;--gen-compare'
-- `samples/monster.fbs`: add generation of binary (.bfbs) schema
-- Configuring done
-- Generating done
-- Build files have been written to: /home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5

Run build:
> make
[  1%] Building CXX object CMakeFiles/flatbuffers.dir/src/idl_parser.cpp.o
In file included from /home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/base.h:237,
                 from /home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp:23:
/usr/include/absl/strings/string_view.h:52:26: error: ‘string_view’ in namespace ‘std’ does not name a type
   52 | using string_view = std::string_view;
      |                          ^~~~~~~~~~~
/usr/include/absl/strings/string_view.h:52:21: note: ‘std::string_view’ is only available from C++17 onwards
   52 | using string_view = std::string_view;
      |                     ^~~
/usr/include/absl/strings/string_view.h:693:8: error: ‘string_view’ does not name a type
  693 | inline string_view ClippedSubstr(string_view s, size_t pos,
      |        ^~~~~~~~~~~
/usr/include/absl/strings/string_view.h:704:11: error: ‘string_view’ does not name a type
  704 | constexpr string_view NullSafeStringView(const char* p) {
      |           ^~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/base.h:239:23: error: ‘string_view’ in namespace ‘absl’ does not name a type
  239 |         typedef absl::string_view string_view;
      |                       ^~~~~~~~~~~
In file included from /home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:29,
                 from /home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffers.h:27,
                 from /home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/idl.h:26,
                 from /home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp:24:
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/string.h:31:16: error: ‘string_view’ in namespace ‘flatbuffers’ does not name a type
   31 |   flatbuffers::string_view string_view() const {
      |                ^~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/string.h:57:28: error: ‘string_view’ in namespace ‘flatbuffers’ does not name a type
   57 | static inline flatbuffers::string_view GetStringView(const String *str) {
      |                            ^~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:494:44: error: ‘flatbuffers::string_view’ has not been declared
  494 |   Offset<String> CreateString(flatbuffers::string_view str) {
      |                                            ^~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:56: error: ‘string_view’ in namespace ‘flatbuffers’ does not name a type
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                                                        ^~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h: In member function ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateString(int)’:
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:495:29: error: request for member ‘data’ in ‘str’, which is of non-class type ‘int’
  495 |     return CreateString(str.data(), str.size());
      |                             ^~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:495:41: error: request for member ‘size’ in ‘str’, which is of non-class type ‘int’
  495 |     return CreateString(str.data(), str.size());
      |                                         ^~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h: In member function ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(int)’:
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:550:35: error: request for member ‘data’ in ‘str’, which is of non-class type ‘const int’
  550 |     return CreateSharedString(str.data(), str.size());
      |                                   ^~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:550:47: error: request for member ‘size’ in ‘str’, which is of non-class type ‘const int’
  550 |     return CreateSharedString(str.data(), str.size());
      |                                               ^~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp: In member function ‘flatbuffers::CheckedError flatbuffers::Parser::ParseString(flatbuffers::Value&, bool)’:
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp:1047:59: error: no matching function for call to ‘flatbuffers::FlatBufferBuilder::CreateSharedString(std::__cxx11::basic_string<char>&)’
 1047 |     val.constant = NumToString(builder_.CreateSharedString(s).o);
      |                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const char*, size_t)’
  522 |   Offset<String> CreateSharedString(const char *str, size_t len) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note:   candidate expects 2 arguments, 1 provided
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(int)’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:68: note:   no known conversion for argument 1 from ‘std::__cxx11::basic_string<char>’ to ‘int’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const flatbuffers::String*)’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:51: note:   no known conversion for argument 1 from ‘std::__cxx11::basic_string<char>’ to ‘const flatbuffers::String*’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                                     ~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp: In member function ‘void flatbuffers::Parser::Serialize()’:
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp:3542:58: error: no matching function for call to ‘flatbuffers::FlatBufferBuilder::CreateSharedString(std::string)’
 3542 |       const auto filename__ = builder_.CreateSharedString(
      |                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~^
 3543 |           RelativeToRootPath(opts.project_root, f->first));
      |           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const char*, size_t)’
  522 |   Offset<String> CreateSharedString(const char *str, size_t len) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note:   candidate expects 2 arguments, 1 provided
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(int)’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:68: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘int’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const flatbuffers::String*)’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:51: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘const flatbuffers::String*’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                                     ~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp:3545:61: error: no matching function for call to ‘flatbuffers::FlatBufferBuilder::CreateSharedString(std::string)’
 3545 |         included_files.push_back(builder_.CreateSharedString(
      |                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~^
 3546 |             RelativeToRootPath(opts.project_root, *i)));
      |             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const char*, size_t)’
  522 |   Offset<String> CreateSharedString(const char *str, size_t len) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note:   candidate expects 2 arguments, 1 provided
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(int)’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:68: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘int’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const flatbuffers::String*)’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:51: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘const flatbuffers::String*’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                                     ~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp: In member function ‘flatbuffers::Offset<reflection::Object> flatbuffers::StructDef::Serialize(flatbuffers::FlatBufferBuilder*, const flatbuffers::Parser&) const’:
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp:3615:50: error: no matching function for call to ‘flatbuffers::FlatBufferBuilder::CreateSharedString(std::string&)’
 3615 |   const auto file__ = builder->CreateSharedString(decl_file_in_project);
      |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const char*, size_t)’
  522 |   Offset<String> CreateSharedString(const char *str, size_t len) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note:   candidate expects 2 arguments, 1 provided
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(int)’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:68: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘int’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const flatbuffers::String*)’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:51: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘const flatbuffers::String*’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                                     ~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp: In member function ‘flatbuffers::Offset<reflection::Service> flatbuffers::ServiceDef::Serialize(flatbuffers::FlatBufferBuilder*, const flatbuffers::Parser&) const’:
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp:3746:50: error: no matching function for call to ‘flatbuffers::FlatBufferBuilder::CreateSharedString(std::string&)’
 3746 |   const auto file__ = builder->CreateSharedString(decl_file_in_project);
      |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const char*, size_t)’
  522 |   Offset<String> CreateSharedString(const char *str, size_t len) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note:   candidate expects 2 arguments, 1 provided
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(int)’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:68: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘int’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const flatbuffers::String*)’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:51: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘const flatbuffers::String*’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                                     ~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp: In member function ‘flatbuffers::Offset<reflection::Enum> flatbuffers::EnumDef::Serialize(flatbuffers::FlatBufferBuilder*, const flatbuffers::Parser&) const’:
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/src/idl_parser.cpp:3784:50: error: no matching function for call to ‘flatbuffers::FlatBufferBuilder::CreateSharedString(std::string&)’
 3784 |   const auto file__ = builder->CreateSharedString(decl_file_in_project);
      |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const char*, size_t)’
  522 |   Offset<String> CreateSharedString(const char *str, size_t len) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:522:18: note:   candidate expects 2 arguments, 1 provided
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(int)’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:549:68: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘int’
  549 |   Offset<String> CreateSharedString(const flatbuffers::string_view str) {
      |                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:18: note: candidate: ‘flatbuffers::Offset<flatbuffers::String> flatbuffers::FlatBufferBuilder::CreateSharedString(const flatbuffers::String*)’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                  ^~~~~~~~~~~~~~~~~~
/home/oscar/Apps/teams-cam/testing/flatbuffers-2.0.5/include/flatbuffers/flatbuffer_builder.h:580:51: note:   no known conversion for argument 1 from ‘std::string’ {aka ‘std::__cxx11::basic_string<char>’} to ‘const flatbuffers::String*’
  580 |   Offset<String> CreateSharedString(const String *str) {
      |                                     ~~~~~~~~~~~~~~^~~
make[2]: *** [CMakeFiles/flatbuffers.dir/build.make:76: CMakeFiles/flatbuffers.dir/src/idl_parser.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:96: CMakeFiles/flatbuffers.dir/all] Error 2
make: *** [Makefile:146: all] Error 2

As I suspected, the earlier tag isn't useful, so we'll need to force a specific checkout beyond the last tagged release. I have a PR (#147) that contains the CMake changes for us.
Unfortunately trying to use the latest HEAD from flatbuffers fails to complete configuration against the remainder of Tensorflow. By application of bisection, I have determined that the newest commit hash that seems not to break Tensorflow is: 20aad0c41e1252b04c72111c3eb221280a9c2009 on April 6th.
@oshikore - can you please try another test compile of flatbuffers at this commit version please?
I'll continue to check that backscrub still actually works too :smile:

Hmmn. Tensorflow v2.8.0 as we are currently using does not compile against flatbuffers v2.0.6, so we must upgrade Tensorflow before we can upgrade flatbuffers... unfortunately the latest Tensorflow (v2.9.1) only supports flatbuffers v2.0.5 (trying v2.0.6 or anything later fails to build Tensorflow).
This looks like an issue that needs to be taken downstream, as we cannot fix Tensorflow :disappointed:  Apologies.

@phlash thanks for the effort in any case.
I'll keep an eye on the project, I hope tensorflow will get sorted out eventually.


Disable warnings 'warning: ignoring ‘#pragma mark ’'

#pragma mark is used througout the codebase for XCode.
They should be removed or ignored when compiling with gcc.
/home/bart/src/maplibre-gl-native/src/mbgl/map/transform.cpp:46: warning: ignoring ‘#pragma mark ’ [-Wunknown-pragmas]
   46 | #pragma mark - Map View
      |
/home/bart/src/maplibre-gl-native/src/mbgl/map/transform.cpp:68: warning: ignoring ‘#pragma mark ’ [-Wunknown-pragmas]
   68 | #pragma mark - Camera
...

We can change them into comments.
https://www.avanderlee.com/xcode/xcode-mark-line-comment/
But I don't think adding/keeping IDE specific comments or pragma's to the core is a good idea.

But I don't think adding/keeping IDE specific comments or #pragmas to the core is a good idea.

Not sure I agree with that. I think the most commonly used IDEs could be supported, as long as they do not cause issues in general. So we should remove the pragmas, but keeping comments would be useful.


fix agent process return

Description
Fixes the issues related to the agent process endpoint on python 3.8
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] ~Attached issue to pull request~
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master in be136f7346ac57c60b11bcd249b5312428c39824


jasmine doesn't seem to run

Hey guys,
I followed the instructions to setup gulp-jasmine but it kind of doesn't work for me.
here's my gulpfile.js
const gulp = require('gulp');
const jasmine = require('gulp-jasmine');
const reporters = require('jasmine-reporters');

const jasmineOptions = {
    'verbose' : true,
    'includeStackTrace' : true,
    'reporter' : new reporters.JUnitXmlReporter()
}

gulp.task('default', () => {});

gulp.task('test', () => {
    gulp.src('tests/test.js')
        .pipe(jasmine(jasmineOptions))
        .on('jasmineDone', () => {
            console.log("jasmine done...");
        })
});

And this is my testfile test.js:
describe("A suite", function() {
    it("contains spec with an expectation", function() {
        expect(true).toBe(true);
    });
});

when I run gulp test I receive following output:

[07:32:41] Using gulpfile ~/Workspace/Development/JavaScript/CM-Divisions-Game/cm-divisions-game/gulpfile.js
[07:32:41] Starting 'test'...
[07:32:41] Finished 'test' after 52 ms
jasmine done...

even tho the jasmine had failed on some case - I wonder why the verbose option or stacktrace did not gave me any informations.

Sorry I did not realized that the reporter exported to a file ....


www: implement api login & password reset

@adamsoffer This is ready for an initial review. If you use the top-level yarn run dev, you should be able to get at everything with http://localhost:3004/. Thoughts:

Is there anything I'm doing with sx properties that should get added to the theme instead?
I like how useApi() works in the components... const {user, logout} = useApi() feels very nicely decoupled. I don't at all like the implementation of useApi, where I'm adding a bunch of functions onto a useState object to create the context. Aside from it being generally messy, I'm pretty sure it can cause all sorts of data inconsistencies because there's no guarantee that the context doesn't change in the middle of async functions. Yuck. If you have a better idea/library for implementing the same pattern, I'm super open to it.
"Forgot password" doesn't do anything yet, but we'll wire that up before going live.
This includes a different solution for https://github.com/livepeer/livepeerjs/pull/609 using min-height: 100vh.
This pattern will be very common, and should probably get its own useLoggedIn() hook to avoid duplication:

  const router = useRouter();
  const { token } = useApi();
  useEffect(() => {
    if (!token) {
      router.replace("/login");
    }
  }, [token]);

I threw a little space for the error text between the form and the button, but we should probably do something more prominent than a little line of text there
We gotta do something about nav on mobile, it's all squooshed and the logo is off the page now. Hamburger time?
Still needs some sort of localStorage implementation to persist the API token across reloads

Sweet. I'm going to make a couple of the changes I described to the hooks API and merge to staging. Hamburgers can be another PR off of that.


[Feature request] Add a feature to allow users to upload their profile pictures.

This should be done both in the signup page, and the profile update page.
We can discuss the implementation details here.

Please assign this to me. I'll take this up.

Can you please assign this to me?

@Piyush3436 You can take this one as you commented first.
@Ayushgup85 you can pick other issues, like #156

Can I work on this issue?

@Piyush3436 any updates on this?
If you are not working on it, we can assign it to @Gautam-Arora24

@pranshukharkwal I've mentioned the issue being faced in the slack channel. If the changes are permitted in the controller I can work over it. If @Gautam-Arora24 can resolve it any other way, I've no problem with the issues being assigned to him.

@Piyush3436 @Gautam-Arora24 You both can maybe discuss the best possible solution over slack, and then one of you (or you both) could work on it.

@pranshukharkwal Actually I have debugged a lot and found the appropriate solution for it. Now what I need is the dummy data for a problem

@Gautam-Arora24 why do you need dummy data for problem for this issue?

@pranshukharkwal Sorry, I commented on the wrong issue


[Question/Bug] zap cannot find Wezterm nightly

Hello and thanks for the great software piece! I have a question. I´m trying to install Wezterm AppImage from the nightly release, which is the very first release here: https://github.com/wez/wezterm/releases/tag/nightly.
However, zap does not find it, if the link above is used, also with direct link to the AppImage, and if I´m trying to select the nightly among released returned by zap, the one I need (nightly) is not among them, since the number of returned releases is limited.
Now, am I doing something wrong? Is there a flag to list all the releases that I´m not aware of? Is the link I´m using wrong? If not, is there a fix possible?
Thanks!

As a workaround, command without --github flag works.


Chop the tests up

The test modules were getting huge, and some of its functions were
actually a huge amount of code due to macros, causing tests to take a
long time just to compile.  They are now separated into a few different
tests, and the scalar macros especially are now expanded more sparingly
in just a few check() functions.
Test compile times for me went from about 25 seconds to 1.5s in debug
mode, and from 300 seconds (!) to about 8s in release mode.

bors r+


[v2]Uncaught (in promise) missing Origin header

i use this code to show a window:
import {WebviewWindow} from "@tauri-apps/api/webviewWindow";
async function handleKeydown(){
  const appWindow = WebviewWindow.getByLabel('tool')
  console.log(appWindow);
  console.log(appWindow?.window);
  console.log(await appWindow?.isVisible())
  // await appWindow?.show()
}

but encounter some problem:
_WebviewWindow {label: 'tool', listeners: {…}}
POST http://ipc.localhost/plugin%3Awindow%7Cis_visible 400 (Bad Request)
:1420/#/CandleChart:1  Uncaught (in promise) missing Origin header

I am a beginner in the front-end, and I am not sure if it is because tauri is not properly configured or just because of a front-end issue.
I have reviewed the documentation and issue, but did not find any similar issues, so how should I solve them?

Could you also post the output of the tauri info command please? Your code looks correct so this is either a bug on our side, or the webview is confused and prints an incorrect error.

Could you also post the output of the tauri info command please? Your code looks correct so this is either a bug on our side, or the webview is confused and prints an incorrect error.

ok，this is output
[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 123.0.2420.81
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.77.0 (aedd173a2 2024-03-17)
    ✔ cargo: 1.77.0 (3fe68eabf 2024-02-29)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.11.1
    - pnpm: 8.15.3
    - yarn: 1.22.19
    - npm: 10.2.4

[-] Packages
    - tauri [RUST]: 2.0.0-beta.14
    - tauri-build [RUST]: 2.0.0-beta.11
    - wry [RUST]: 0.39.0
    - tao [RUST]: 0.27.0
    - tauri-cli [RUST]: 1.4.0
    - @tauri-apps/api [NPM]: 2.0.0-beta.7
    - @tauri-apps/cli [NPM]: 2.0.0-beta.12

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite

The IPC requests are failing since they are not sending a Origin header.
From what I can tell it's because of this PR

Example request

The IPC requests are failing since they are not sending a Origin header.
From what I can tell it's because of this PR, more specifically this line.
The browser is not sending the header by default for whatever reason, and it's not being explicitly added in the request code
Example request

emm,It looks a little complicated. So how can I solve this problem，manually sending a Origin header(how can this be achieved)? Do you have any suggestions?Thank you very much for your reply.

The IPC requests are failing since they are not sending a Origin header.
From what I can tell it's because of this PR, more specifically this line.
The browser is not sending the header by default for whatever reason, and it's not being explicitly added in the request code
Example request

emm,It looks a little complicated. So how can I solve this problem，manually sending a Origin header(how can this be achieved)? Do you have any suggestions?Thank you very much for your reply.

downgrade your tauri until they fix the bug

downgrade your tauri until they fix the bug

I tested that both tauri 2.0.0 beta and 2.0.0 alpha cannot function properly. Can we only downgrade to tauri 1.0?

Can someone upload a minimal reproduction (this means, reproduce the error in a new app created with create-tauri-app and upload that to github).
Also, do you have a system proxy configured?

Can someone upload a minimal reproduction (this means, reproduce the error in a new app created with create-tauri-app and upload that to github).
Also, do you have a system proxy configured?

hi,i  have identified the cause, beacuse i face the problem:
 xxx from origin 'http://localhost:1420' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'https://echarts.apache.org' that is not equal to the supplied origi

i search the isssue and try many wrokaround but this is effective:https://github.com/tauri-apps/tauri-docs/issues/26#issuecomment-1909861413, but the problems encountered above will occur.
If  "additionalBrowserArgs": "--disable-web-security"  is removed from windows config, the above problem disappeared, but the CORS problem reappeared.
So do you still need a minimal reproduction? How can I solve this series of problems?

Ahhh, okay i understand.
For CORS issues we generally recommend using tauri's fetch instead of the browser's one which ignores CORS because it executes the requests on the Rust side. Or if possible, write the rust code yourself. This is basically required if you need macOS or Linux support because they don't have that browser argument.
@lucasfernog tldr: The --disable-web-security flag clashes with this https://github.com/tauri-apps/tauri/pull/9100/files#diff-d6ec24d524b77014e2aa13eec678a5032904ddc820664b1c000866cc006cc71aR403 (or well, the inner Wry logic). Having a fallback is probably unsafe but just forbidding the flag (if tauri's ipc is used) may also not be nice because it's used more often than we'd like, so i don't really know what to do here tbh.

I have tried tauri's fetch, it also face the CORS problem(Or something else, I can't remember clearly? Anyway, it won't work properly),  so i have use reqwest to get http data. Now it can work normally. Thanks.


Support custom Docker images in the JDBC URL

Make it possible to specify a full docker image name in the JDBC URL and/or custom docker registries, and these might be necessary to allow teams to use their own privately managed images.

I was looking into this yesterday - would be keen to get your thoughts and the ideas from folks in your team.
Right now, I think if you have a custom container class with image name of the form hostname:port/image:tag then docker will be able to pull from a private registry (assuming the user has already authenticated). This seems like a nice zero-effort solution to me, though I need to test it actually works.
An alternative would be a way to provide private registry hostname/credentials in some way, but this either needs to be encoded in the JDBC URL (getting busy) or as environment variables (less discoverable; requires more documentation).
What do you think?

@outofcoffee, @haines, any thoughts?

I think adding more JDBC URL query string parameters is ok for this purpose.

I guess it depends on where the private registry is and how they implement authentication. I know with docker, you can authenticate via the command line:
docker login -e $DOCKER_EMAIL -u $DOCKER_USER -p $DOCKER_PASS
Then you can docker push or pull

I think this is sufficiently complex that we should leave it for a little
while and prioritise other things first.
On Fri, Jun 26, 2015 at 9:17 AM, gusohal<EMAIL_ADDRESS>wrote:

I guess it depends on where the private registry is and how they implement
authentication. I know with docker, you can authenticate via the command
line:
docker login -e $DOCKER_EMAIL -u $DOCKER_USER -p $DOCKER_PASS
Then you can docker push or pull
—
Reply to this email directly or view it on GitHub
https://github.com/rnorth/test-containers/issues/4#issuecomment-115438147
.

Would like to see if @rnorth's suggestion works - if so, this seems like a sensible (and standard AFA Docker syntax is concerned) solution.

We need to try this out - sometime soon!

This may need further work before it is ready, see #70:

Thank you very much for the fix. Unfortunately it does seem to break support for local registries.
If I understand #4 correctly, the current proposed solution for using custom local image registries is to specify the image name like this: registryHost:port/imageName.
If I specify something like localhost:5000/my-image as image name, the build repeatedly pulls the image (similar behaviour as posted by buckett).
If I use localhost:5000/my-image:latest it says "No image tag was specified in docker image name etc.".

This is now implemented - see #99

@SaschaJohn Sorry for the slow reply.  I've been struggling getting the dependencies working.

The testcontainers documentation for jitpack are incorrect (contrast with the instructions on the jitpack site)
I am unable to update all testcontainer dependencies to the same PR version; I got funky errors when only adding the testcontainers-java dep, and leaving junit-jupiter and postgresql deps at version 12.5

I'm still poking at it.

This is how we solved it for postgres:
Added docker.registry.url=my.custom.registry to src/test/resources/testcontainers.properties
Extended testcontainers postgres container with external registry support that handles our custom postgresqlext db types:
package my.package.postgresext;

import org.apache.commons.lang3.StringUtils;
import org.testcontainers.containers.PostgreSQLContainer;
import org.testcontainers.utility.TestcontainersConfiguration;

public class ExternalRegistryPostgreSQLContainer<SELF extends ExternalRegistryPostgreSQLContainer<SELF>> extends PostgreSQLContainer<SELF> {

    public ExternalRegistryPostgreSQLContainer(final String dockerImageName) {
        super(getRegistryUrl() + dockerImageName);
    }

    private static String getRegistryUrl() {
        String registryUrl = (String) TestcontainersConfiguration.getInstance().getProperties().get("docker.registry.url");
        if (StringUtils.isEmpty(registryUrl)) {
            return StringUtils.EMPTY;
        }
        return StringUtils.appendIfMissing(registryUrl, "/");
    }
}

package my.package.postgresext;

import org.testcontainers.containers.JdbcDatabaseContainer;
import org.testcontainers.containers.PostgreSQLContainer;
import org.testcontainers.containers.PostgreSQLContainerProvider;

public class ExternalRegistryPostgreSQLContainerProvider extends PostgreSQLContainerProvider {

    private static final String NAME = "postgresqlext";

    @Override
    public boolean supports(String databaseType) {
        return NAME.equals(databaseType);
    }

    @Override
    public JdbcDatabaseContainer newInstance(String tag) {
        return new ExternalRegistryPostgreSQLContainer(PostgreSQLContainer.IMAGE + ":" + tag);
    }

}

Added that container class to src\test\resources\META-INF\services\org.testcontainers.containers.JdbcDatabaseContainerProvider
my.package.ExternalRegistryPostgreSQLContainerProvider
And then just declare your DB url with postgresqlext: jdbc:tc:postgresqlext://localhost/testdb

@jyrno FYI something like that soon will be natively supported by Testcontainers. See #2599 for an example of how it is proposed to be done for R2DBC

any updates regarding azure-sql-edge so far ?


batch_get_pelvis_orient

Could you please explain the mathematical principle of this function batch_get_pelvis_orient?

Engineers found usable solution without knowing how it works.


Missing ./selectors.js in react-router-redux

Version
5.0.0-alpha.7
Test Case
Running mocha unit tests.
Expected Behavior
Tests run.
Actual Behavior
Tests fail on error: Error: Cannot find module './selectors' (react-router-redux/index.js:6:18)
Works in 5.0.0-alpha.6.
Attaching screenshot of react-router-redux module directory, which is clearly missing the ./selectors.js file.

same issue "react-router": "^3.0.0"

@adomrockie wouldn't that allow upgrades?

@adomrockie
Use "react-router-redux": "5.0.0-alpha.6" in your package.json. Having ^ says you are targeting any compatible with.


[GSSOC'23] Added table of content in README.md

#41
added table of content

@sahil-sagwekar2652 I have resolved merge conflict you can review and merge this PR.


M2 billboarding should be a vertex shader

Currently, M2 billboarding is done with expensive CPU operations (matrix and vector math) on each tick of the render loop. There's no reason, as far as I know, that this can't be done in the vertex shader for M2Material.
I've taken a few stabs at this and failed. It's not clear to me why the basic approaches to vertex shader billboarding found on Google don't seem to work.
Things to keep in mind:

THREE's lookAt method doesn't work because billboarded bones are typically children of rotated/translated parents.
Even if THREE's lookAt method did work, it's still expensive on the CPU compared to doing this in a vertex shader on the GPU.
The vertex shader probably needs to account for the skinning applied to the billboard before it billboards the vertex. In other words, the logic should probably exist toward the very end of main() in the vertex shader.

Yep, agreed! :+1:

I wish you a luck doing these kind of transformations in vertes shader.
Keep in mind that bones form a tree structure. And some root bone is marked as "billboarded" - all it's childs will be affected by it.
Generally papers cover case, where the whole model is billboarded, not some bone.

@Deamon87 That's a very good point. I'll have to ponder this for a while.


Build fixes

Coverage decreased (-0.007%) to 71.749% when pulling 5199592bea9afa6ac91f4ca8c151d13af8f1a342 on MichalKononenko:BuildFixes into 8118ab7adaf0bd82ea39577a08f2ad3b71bca1ae on QInfer:master.

Coverage decreased (-0.007%) to 71.749% when pulling 5199592bea9afa6ac91f4ca8c151d13af8f1a342 on MichalKononenko:BuildFixes into 8118ab7adaf0bd82ea39577a08f2ad3b71bca1ae on QInfer:master.

Coverage decreased (-0.007%) to 71.749% when pulling 5199592bea9afa6ac91f4ca8c151d13af8f1a342 on MichalKononenko:BuildFixes into 8118ab7adaf0bd82ea39577a08f2ad3b71bca1ae on QInfer:master.

Coverage decreased (-0.007%) to 71.749% when pulling 5199592bea9afa6ac91f4ca8c151d13af8f1a342 on MichalKononenko:BuildFixes into 8118ab7adaf0bd82ea39577a08f2ad3b71bca1ae on QInfer:master.

It's pretty critical to have qinfer.__version__ defined in released builds, so I'd like to figure out how to either fix the builds or fail gracefully if version.py isn't properly created by setup.py. (Possibly both.) For instance, we may be able to modify __init__.py similar to the following:
try:
    from qinfer.version import version as __version__
except ImportError:
    __version__ = '<unknown>'

That would break a few things based on version comparisons, but if one uses distutils.version.LooseVersion, that should still at least give somewhat sensible answers:
>>> LooseVersion('<unknown>') < LooseVersion('1.0')
False
>>> LooseVersion('<unknown>') > LooseVersion('1.0')
True

As for build breakages, I'm seeing some builds failing due to QuTiP 4.1 now requiring a C++ compiler, such that we do need to fix those builds, but is there a specific build that you saw break due to version.py?


⚠ Bofrost.lu has degraded performance

In e976147, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1017 ms

Resolved: Bofrost.lu performance has improved in 2aacfea after 10 minutes.


improve error logging

We need to make it obvious if an error is local or remote.

Codecov Report

Merging #1816 into master will not change coverage.
The diff coverage is 50%.

@@           Coverage Diff           @@
##           master    #1816   +/-   ##
=======================================
  Coverage   86.87%   86.87%
=======================================
  Files          95       95
  Lines        6466     6466
=======================================
  Hits         5617     5617
  Misses        607      607
  Partials      242      242

Impacted Files
Coverage Δ

session.go
75.75% <50%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Why not to use string instead of int?

https://github.com/HewlettPackard/PacketRusher/blob/578563bb2f32925a5178c8f5c17d5ba723c7dd48/config/config.go#L86
I tried to use helm chart to deploy Packet Rusher to Kubernetes Cluster. The type of  gnodeb.slicesupportlist.sst in config.yml is string while ue.snssai.sst is integer. This make entrypoint.sh hard to replace ENV variable to integer, can you modify the type to string?

Hi @brianchennn,
I think the rationale to use int instead of string was to enforce that SST was mandatory while SD was not. Though it's stupid (especially since slicesupportlist and snssai should have the same format), and we need a proper configuration validator instead.
We indeed need to fix that!
By the way, you may also want to take a look at Gradiant's PacketRusher Helm Chart which does not use our entrypoint and instead just generate a config.yml out of a template: https://github.com/Gradiant/5g-charts/tree/main/charts/packetrusher
Cheers,
Valentin


Code errors persist after fixes

What happened?

I was typing a simple program on DartPad. Issues appear while I'm writing the program, on the code as red underlines and banners at the bottom right.
When I fix the issues, the banner errors on the bottom right disappear while the red underlines still persist.

Steps to reproduce the problem
Type a program on the Dart Pad ;-)

Additional info
Browser
Browser: Chrome
Version: Version 103.0.5060.114 (Official Build) (64-bit)
Are you using any extensions/plugins that affect website behavior
(particularly those that affect iframes, such as ad blockers)? No
Are there any warnings or errors in your browser's JavaScript console?
If so, paste them below:
[paste warnings or errors here]

Machine
Operating system: Linux Mint
Version:
Your code
What code was in the editor, if any, when the failure occurred? You
can paste it in below:
// Paste code here.

DartPad's output
Did DartPad print anything to the console pane? If so, paste it below:
[paste console output here]

If you were running Flutter code, you can also paste an image of the
Flutter output directly into this bug report.

The same 'issues' here, where aren't. The code is underlined where it shouldn't. Temporary fix is to press Format button, it wipes away the underlines, though typing code again gives them back. I tried to press Reset, clear the local storage and cookies, even open the dartpad incognito in Chrome but it didn't help. Also I noticed that import of rxdart does not work any more:
Error: Not found: 'package:rxdart/rxdart.dart' import 'package:rxdart/rxdart.dart';


Adding information how to configure EMC XtremeIO inside rpc-openstack

Adding example configuration for EMC XtremeIO storage

I really like this idea, though I'm wondering if it would be more helpful upstream. Is there anything specific to Rackspace's deployment that I'm not aware of in here?

Yeah I figured it's easier to contribute here, in context with Rackspace.
Although it's not specific to rpc-openstack. I'm happy to bring it into the OSA project

Nicely done! However I agree with @nrb, this probably belongs in upstream.


One html file

Fixes #241 for local html report resources to be aggregated into the output file
Fixes #264 for application not working for html format when run from Nuget CLI install

Allows user to specify an output file path now since dependencies are addressed and file can be located anywhere.

Cool I'll take a look at that option and get back to you.  Hey you should have dropped that in one the related issues for me earlier to save me time haha but thanks and sounds like a better approach!

Sorry I didn't think to mention it earlier :P.
My recommendation is as follows.  This eliminates all dependency on external files being present on the disc, everything will be in the binary.

Use webpack either pre-build or as part of the pre-build build tasks to compile all your js and css assets.  It sounds like your html is also one file too, which is great.
Embed those into your binary.  Set the build task to EmbeddedResource in visual studio.
Have a simple test to ensure that the embeds are there.
At runtime access the embedded files like here in attack surface analyzer https://github.com/microsoft/AttackSurfaceAnalyzer/blob/5932999bf4b9cc4fd521aee1f84c0dcbc71de9a4/Lib/Objects/RuleFile.cs#L78-L108
Write the embedded files to disc where the user has selected.

If you're not already, you should also embed your default rules, so the binary will be completely independent of any runtime data needed to operate.

While the webpack does help consolidate js and cs files and removes the internet dependency for the files and attendant download time, the goal is to output a single file, not a reduced set of files.  Therefore, the application still needs to add the content into the index.html file to make it truly transportable without any additional local files that have to be included to zip up etc. which is my goal.  I see therefore the logic needed to achieve that merge as still necessary even with a proposed WebPack addition, with the change only improving the download performance which is negligible and do not have a goal for offline use -typical policy is most people have an active connection.  At the same time, the change represents a chunk of work and added depending on NPM, config, build and testing.  Looking at effort to value I'm thinking this is a refactor option in the near future but not necessary for the present and I need to get the CLI app working again asap for those that are unable to use it at present.  I ran this staged approach past management and have agreement to add this as a suggested engineering enhancement.  Thanks for the tip!


Inconsistent handling of invalid variable values in SampleSet

>>> import dimod
>>> dimod.__version__
'0.8.15'
>>>
>>> bqm = dimod.BQM.from_ising({}, {'ab': 1})
>>> ss = dimod.SampleSet.from_samples_bqm([{'a': 1, 'b': 1}, {'a': -1, 'b': -20}], bqm)
>>> print(ss)
   a  b energy num_oc.
0 +1 +1    1.0       1
1 -1 -1   20.0       1
['SPIN', 2 rows, 2 samples, 2 variables]

Note how -20 for b in the second sample is out of allowed {1, -1} set, yet when printed it's rounded down to -1. Energy stays incorrect though (calculated for b = -20).

The energy is correct, it's calculated from a*b*J_ab so -1*-20*1. The problem is that the sampleset does not check that the input samples are actually correct so sampleset.record.sample in this case would be [[1, 1], [-1, 20]]. It is the print function, not the construction that is rounding b down.
We can change it so that the sample set enforces the samples to be the correct vartype, would you prefer an exception or rounding? There is a performance hit that comes with that, so maybe I can add a permissive=True flag or something.

Yes, I'm aware of that. I guess I forgot to write my expected behaviour:

if invalid variable values are accepted in constructor, and actually stored in the SampleSet, then print function should not round them down - it should stay as close to actual sample set data as possible.
but I don't think invalid values should ever be stored in the SS (since vartype is a non-optional parameter!). I like the idea of permissive flag, and I would expect that permissive=False raises an exception (default), and permissive=True rounds values.


csv fixed length between delimiter

i want to add fixed length between delimiters when exporting like this :
hello    |    every|                    one|
some   |      thing|           hereeeee|
bla        |        bla|                      bla|

If you don't need the actual delimiter character, the PRN output type lines up the columns:
var i = "hello,every,one\nsome,thing,hereeeee\nbla,bla,bla";
var wb = XLSX.read(i, {type:"binary"});
var prn = XLSX.write(wb, {bookType:"prn", type:"string", sheet:"Sheet1"});

And the output looks like:
hello      every     one
some       thing     hereeeee
bla        bla       bla

For more advanced work, you could write a JS function to post-process the DSV output.  After using sheet_to_csv to convert with the option FS:"|", you can manually split and walk the array of arrays:
var dsv = XLSX.utils.sheet_to_csv(wb.Sheets.Sheet1, {FS:"|"});
var arr = dsv.split("\n").filter(r => r).map(r => r.split("|"));
var C = Math.max.apply([], arr.map(r => r.length));
for(var i = 0; i < C; ++i) {
  var w = Math.max.apply([], arr.map(r => (r[i]||"").length));
  for(var R = 0; R < arr.length; ++R) arr[R][i] = (arr[R][i]||"").padEnd(w+1, " ");
}
var out = arr.map(r => r.join("|")).join("\n");

which will look like:
hello |every |one
some  |thing |hereeeee
bla   |bla   |bla

(to right-align, use padStart rather than padEnd)


Pokedex Game info of all Pokemons

Signed-off-by: Ankit Srivastava<EMAIL_ADDRESS>Description
Pokedex Webpage, using Pokedex API to gather all pokemon information
Fixes #470
Addition
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

@Ayush7614 This is a HacktoberFest-2021 PR, Kindly add the required labels.


kubelet agent

First stab at the kubelet agent to restart and update the kubelet.

@aaronlevy PTAL I tried to streamline the logic a bit, and rewrote some of the comments. Should have addressed most things. I could use you to double check the logic in getVersionFromNode to make sure i'm actually understand when its ok to signal a temporary error.

Closing this in hopes of taking this work upstream in some form.

@pbx0 hmm, is there a concrete place to follow along for that? excited to see this, but "hopes" sounds a little vague ;-)