Kismatic hangs at Validate kubernets Control Planel validation

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
I'm trying to setup a cluster with 2 master, 3 etcd and 1 workers in proxmox.
There are two issues

Kube-apiserver is not runing
kubectl get cs returing

NAME                 STATUS      MESSAGE                                                                                ERROR
scheduler            Healthy     ok
controller-manager   Healthy     ok
etcd-2               Unhealthy   Get https://k8s-etcd03:2379/health: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
etcd-1               Unhealthy   Get https://k8s-etcd02:2379/health: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
etcd-0               Unhealthy   Get https://k8s-etcd01:2379/health: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

there is no files in etc/cni/net.d. log from master

cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
kubelet.go:2125] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not read
etc

What you expected to happen:
K8s cluster should be up and running
How to reproduce it (as minimally and precisely as possible):
Setup vms in proxmox and run the kismatic.
Anything else we need to know?:
It is possible to connect to etcd cluster from master
curl --key etcd-client-key.pem --cacert ca.pem --cert etcd-client.pem https://k8s-etcd01:2379/v2/keys
{"action":"get","node":{"dir":true}}

Environment:

Kismatic version (use kismatic version):

Kismatic:
  Version: 1.11.1
  Built: Wed May 30 20:47:57 UTC 2018
  Go Version: go1.9.4

Plan file Gist (remove sensitive information if any):

cluster:
  name: k8s

  # Kubernetes cluster version (supported minor version "v1.10.x").
  version: v1.10.2

  # Set to true if the nodes have the required packages installed.
  disable_package_installation: false

  # Set to true if you are performing a disconnected installation.
  disconnected_installation: false

  # Networking configuration of your cluster.
  networking:

    # Kubernetes will assign pods IPs in this range. Do not use a range that is
    # already in use on your local network!
    pod_cidr_block: <IP_ADDRESS>/16

    # Kubernetes will assign services IPs in this range. Do not use a range
    # that is already in use by your local network or pod network!
    service_cidr_block: <IP_ADDRESS>/16

    # Set to true if your nodes cannot resolve each others' names using DNS.
    update_hosts_files: true

    # Set the proxy server to use for HTTP connections.
    http_proxy: ""

    # Set the proxy server to use for HTTPs connections.
    https_proxy: ""

    # List of host names and/or IPs that shouldn't go through any proxy.
    # All nodes' 'host' and 'IPs' are always set.
    no_proxy: ""

  # Generated certs configuration.
  certificates:

    # Self-signed certificate expiration period in hours; default is 2 years.
    expiry: 17520h

    # CA certificate expiration period in hours; default is 2 years.
    ca_expiry: 17520h

  # SSH configuration for cluster nodes.
  ssh:

    # This user must be able to sudo without password.
    user: admin

    # Absolute path to the ssh private key we should use to manage nodes.
    ssh_key: /home/admin/.ssh/id_rsa
    ssh_port: 22

  # Override configuration of Kubernetes components.
  kube_apiserver:
    option_overrides: {}

  kube_controller_manager:
    option_overrides: {}

  kube_scheduler:
    option_overrides: {}

  kube_proxy:
    option_overrides: {}

  kubelet:
    option_overrides: {}

  # Kubernetes cloud provider integration.
  cloud_provider:

    # Options: 'aws','azure','cloudstack','fake','gce','mesos','openstack',
    # 'ovirt','photon','rackspace','vsphere'.
    # Leave empty for bare metal setups or other unsupported providers.
    provider: ""

    # Path to the config file, leave empty if provider does not require it.
    config: ""

# Docker daemon configuration of all cluster nodes.
docker:

  # Set to true if docker is already installed and configured.
  disable: false
  logs:
    driver: json-file
    opts:
      max-file: "1"
      max-size: 50m

  storage:

    # Leave empty to have docker automatically select the driver.
    driver: ""
    opts: {}

    # Used for setting up Device Mapper storage driver in direct-lvm mode.
    direct_lvm_block_device:

      # Absolute path to the block device that will be used for direct-lvm mode.
      # This device will be wiped and used exclusively by docker.
      path: ""
      thinpool_percent: "95"
      thinpool_metapercent: "1"
      thinpool_autoextend_threshold: "80"
      thinpool_autoextend_percent: "20"

# If you want to use an internal registry for the installation or upgrade, you
# must provide its information here. You must seed this registry before the
# installation or upgrade of your cluster. This registry must be accessible from
# all nodes on the cluster.
docker_registry:

  # IP or hostname and port for your registry.
  server: ""

  # Absolute path to the certificate authority that should be trusted when
  # connecting to your registry.
  CA: ""

  # Leave blank for unauthenticated access.
  username: ""

  # Leave blank for unauthenticated access.
  password: ""

# A set of files or directories to copy from the local machine to any of the nodes in the cluster.
additional_files: []

# Add-ons are additional components that KET installs on the cluster.
add_ons:
  cni:
    disable: false

    # Selecting 'custom' will result in a CNI ready cluster, however it is up to
    # you to configure a plugin after the install.
    # Options: 'calico','weave','contiv','custom'.
    provider: calico
    options:
      calico:

        # Options: 'overlay','routed'.
        mode: overlay

        # Options: 'warning','info','debug'.
        log_level: info

        # MTU for the workload interface, configures the CNI config.
        workload_mtu: 1500

        # MTU for the tunnel device used if IPIP is enabled.
        felix_input_mtu: 1440

        # Used to detect the IPv4 address of the host.
        ip_autodetection_method: first-found

      weave:

        # Used by Weave for network traffic encryption.
        # Should be reasonably strong, with at least 50 bits of entropy.
        password: ""

  dns:
    disable: false

    # Options: 'kubedns','coredns'.
    provider: kubedns
    options:
      replicas: 2

  heapster:
    disable: false
    options:
      heapster:
        replicas: 2

        # Specify kubernetes ServiceType. Defaults to 'ClusterIP'.
        # Options: 'ClusterIP','NodePort','LoadBalancer','ExternalName'.
        service_type: ClusterIP

        # Specify the sink to store heapster data. Defaults to an influxdb pod
        # running on the cluster.
        sink: influxdb:http://heapster-influxdb.kube-system.svc:8086

      influxdb:

        # Provide the name of the persistent volume claim that you will create
        # after installation. If not specified, the data will be stored in
        # ephemeral storage.
        pvc_name: ""

  # Metrics Server is a cluster-wide aggregator of resource usage data.
  metrics_server:
    disable: false

  dashboard:
    disable: false
    options:
      service_type: ClusterIP

  package_manager:
    disable: false

    # Options: 'helm'.
    provider: helm
    options:
      helm:
        namespace: kube-system

  # The rescheduler ensures that critical add-ons remain running on the cluster.
  rescheduler:
    disable: false

# Etcd nodes are the ones that run the etcd distributed key-value database.
etcd:
  expected_count: 3

  # Provide the hostname and IP of each node. If the node has an IP for internal
  # traffic, provide it in the internalip field. Otherwise, that field can be
  # left blank.
  nodes:
  - host: "k8s-etcd01"
    ip: "<IP_ADDRESS>"
    internalip: "<IP_ADDRESS>"

  - host: "k8s-etcd02"
    ip: "<IP_ADDRESS>"
    internalip: "<IP_ADDRESS>"

  - host: "k8s-etcd03"
    ip: "<IP_ADDRESS>"
    internalip: "<IP_ADDRESS>"

# Master nodes are the ones that run the Kubernetes control plane components.
master:
  expected_count: 2

  # If you have set up load balancing for master nodes, enter the FQDN name here.
  # Otherwise, use the IP address of a single master node.
  load_balanced_fqdn: "<IP_ADDRESS>"

  # If you have set up load balancing for master nodes, enter the short name here.
  # Otherwise, use the IP address of a single master node.
  load_balanced_short_name: "<IP_ADDRESS>"
  nodes:
  - host: "k8s-master01"
    ip: "<IP_ADDRESS>"
    internalip: "<IP_ADDRESS>"
    labels: {"master01"}
    taints: []

  - host: "k8s-master02"
    ip: "<IP_ADDRESS>"
    internalip: "<IP_ADDRESS>"
    labels: {"master02"}
    taints: []

# Worker nodes are the ones that will run your workloads on the cluster.
worker:
  expected_count: 1
  nodes:
  - host: "k8s-workers02"
    ip: "<IP_ADDRESS>"
    internalip: "<IP_ADDRESS>"
    labels: {"worker02"}
    taints: []

# Ingress nodes will run the ingress controllers.
ingress:
  expected_count: 0
  nodes: []

# Storage nodes will be used to create a distributed storage cluster that can
# be consumed by your workloads.
storage:
  expected_count: 0
  nodes: []

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):

NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Kernel (e.g. uname -a):

Linux infra-exec 4.4.0-127-generic #153-Ubuntu SMP Sat May 19 10:58:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Check the logs for the api-server, ssh onto the master and use docker logs on the api-server to see why its failing.

The CNI is not yet setup until the api-server is running.

Thank you @dkoshkin for replying. I figured out the issue - it was network connectivity issue.
For reference
I am using Ubuntu 16.04 and it comes with Dnsmasq. This Dnsmasq was not reading from /etc/hosts. I also had a dnsservers record in my /etc/network/interfaces. I installed Dnsmasq and used following configurations
domain-needed
bogus-priv

domain=k8.com
expand-hosts
local=/k8.com/

listen-address=<IP_ADDRESS>
bind-interfaces

server=<IP_ADDRESS>
server=<IP_ADDRESS>

after that kismatic was able to install the k8s without any issue.


Inconsistent styling on the final header of the assessment form, 'completion'

Background:
https://trello.com/c/OKqXslp4/151-inconsistent-styling-on-the-final-header-of-the-assessment-form-completion
Solution:

Changed panel header class to contain left arrow

 Inconsistent styling on the final header of the assessment form, 'completion'


Support goinstall

goinstall allows you to auto-install github repos.  I'm new to Go so I'm not sure what the underlying problem is.  This would make it easy for noobs like me to install and use your project quickly.
http://golang.org/cmd/goinstall/
> goinstall -u github.com/alphazero/Go-Redis
goinstall: github.com/alphazero/Go-Redis: package has no files

Hi Mike,
Thanks, I'll look into it.
/R
On Tue, 27 Dec 2011 21:29:18 -0800, Mike Perham wrote:

goinstall allows you to auto-install github repos.  I'm new to Go but
I believe it just requires a top-level Makefile to build the project.
This would make it easy for noobs like me to install and use your
project quickly.
http://golang.org/cmd/goinstall/

Reply to this email directly or view it on GitHub:
https://github.com/alphazero/Go-Redis/issues/6


Obsoletion request: RNA polyadenylation

Please provide as much information as you can:
Once https://github.com/geneontology/go-ontology/issues/24921
is done we can begin to obsolete
GO:0043631   RNA polyadenylation
GO:0006378    mRNA polyadenylation
GO:1900364    negative regulation of mRNA polyadenylation
GO:1900365    positive regulation of mRNA polyadenylation
GO:1900363    regulation of mRNA polyadenylation
GO:0043629    ncRNA polyadenylation
(I will make sure there are direct  replacements for all of these)
GO:0043630    ncRNA polyadenylation involved in polyadenylation-dependent ncRNA catabolic process
replace by -> GO:0043634  polyadenylation-dependent ncRNA catabolic process
GO:0071050    sno(s)RNA polyadenylation ->
replace by GO:0071051    polyadenylation-dependent snoRNA 3'-end processing
Rehouse:
GO:0097222    mitochondrial mRNA polyadenylation
GO:0140235   RNA polyadenylation at postsynapse (this could probably move under cytoplasmic polyadenylation, need to check)
GO:0039698    polyadenylation of viral mRNA by polymerase stuttering (this is something completely different nd ned rehoming)

GO term ID and Label

Reason for deprecation Put an x in the appropriate box:

[x] The reason for obsoletion is that this term represents a molecular function.

"Replace by" term (ID and label)
If all annotations can safely be moved to that term

"Consider" term(s) (ID and label)
Suggestions for reannotation

Are there annotations to this term?

How many EXP:

Are there mappings and cross references to this term? (InterPro, Keywords; check QuickGO cross-references section)

Is this term in a subset? (check the AmiGO page for that term)

Any other information

Checklist for ontology editor
Check term usage and metadata in Protégé

[ ] check term usage in the ontology
[ ] check internal mappings: RHEA, EC, MetaCyc
[ ] check subset usage
[ ] check taxon constraints

Check annotations

[ ] create Annotation Review spreadsheet

Annotation Review template: https://docs.google.com/spreadsheets/d/1izV3q1jnq_Ybg5MJ53O_b5BCTkGtjl_Fi-cOg3-7eBE/edit#gid=0

Instructions: https://wiki.geneontology.org/Annotation_Review_Request

[ ] create annotation review ticket: https://github.com/geneontology/go-annotation/issues/new?assignees=&labels=annotation+review&template=annotation-review-for-obsoletion.md&title=Review+annotations+to+[INSERT+GO+TERM]
[ ] find external mappings (via IEAS), include in obsoletion notice
[ ] tag curators in Annotation Review ticket. Responsible annotator for each group: https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv

Notification

[ ] create obsoletion announcement
[ ] announce to GO friends<EMAIL_ADDRESS>[ ] paste the text in the ontology ticket

waiting for terms in
https://github.com/geneontology/go-ontology/issues/24921
to appear

we had 5 ISS all changed or deleted.

FOr now I moved
GO:0039698 polyadenylation of viral mRNA by polymerase stuttering  under 'viral process'
and
GO:0140235 RNA polyadenylation at postsynapse
under RNA processing

GO:0006378
is still present and has  79 EXP annotations

GO:0006378
is still present and has 78 EXP annotations
I wonder if this term somehow got excluded from the spreadsheet so I will create another one to finish this off.

GO:1900364   negative regulation of mRNA polyadenylation
is also remaining but this can be obsoleted with the parent
GO:0031441   negative regulation of mRNA 3'-end processing
as direct replacement

I'm reopening this because some terms are still present. Will review and open a new ticket for the rest.

I remember now I hadn't done
GO:0006378  mRNA polyadenylation (depending whether nuclear of cytosolic)
because it was more complicated.
I  planned to keep  GO:0180011   cytoplasmic polyadenylation
in the short term because there appear to be a couple of pathways and  there is no good replacement yet (related to stability which needs to b e addressed separately.
SO I'll close this and open a ticket for "mRNA polyadenylation"


[component] add osquery

Problem description
add osquery - https://osquery.io/ - https://github.com/facebook/osquery

[ ] add to registry
[x] add version crawler to updater

possible version scraping pages:

https://chocolatey.org/packages/osquery
https://github.com/facebook/osquery/releases/latest

download url: https://osquery-packages.s3.amazonaws.com/choco/osquery-'.$version.'.zip

[ ] add to installers as new component

update installer registries of next version to include the component
archive type: zip
extraction path = install path = bin/osquery

Added to registry:

https://github.com/WPN-XM/registry/commit/c04c4c3b36098c93684eb06a79004c4517d82b68
https://github.com/WPN-XM/registry/commit/1da6c0f5ae5107624ac62e604c2b450dc52d294a


Rest API

Hello Guys,
We are trying to expose the powershell apis into the external world, but all operations are getting slower, specially on creating a session.
Is there a way to keep a reference of the session?
Are there any rest apis for skype endpoints? Like the result we get from Get-CsOnlineUsers ?
Thanks!

@officedocsbot assign @yogkumgit

Hello @PlayMa256 Matheus
How are you? Hope you are doing good.
Is there an specific article that you see needs a correction?
Can you please share the link to the article?
About REST API, the recommendation now is going for the Graph API, have you checked it?
Thank you

Hello @get-itips
I'm doing fine and you?
So i asked the same question on https://github.com/microsoftgraph/msgraph-sdk-javascript/issues/266#event-3007264011 and they told me to get here!
Also, we are having performance issues, some fetch operations take like, 2 minutes to complete. How can we decrease the performance?
And how can we keep track of sessions created? is there a pool of sessions?

Hello @PlayMa256 again 👍
Here, we are limited to address issues in documentation, like typos or wrong information.
So specifically about issues like performance I need to kindly request you to open a support ticket on your tenant.
I am not sure about the other question because I would need the link of the Docs article that brought you here to read and understand better.
Thank you


Copyright violation

Hi @Cj-Malone
I found this app on the Google Play Store. This guy just took your source code, added some ads in it and put it on the Store, without warning this is free software...
As you are the owner of the source code, feel free to open a request to google here to remove the false app from the Store, if it's your wish ;)
Don't forget to tell Google that:

The app is licensed under BSD 2-clause "Simplified" License and this guy is violating it;
He is falsely claiming he made the app;
Provide screenshots of your own app and a link to this repo.

Thanks, I've reached out to them<EMAIL_ADDRESS>and I'll see if I get a response.
But I think, if they add the licence details they are free to continue doing this? And there is the possibility that they, or both of us will be removed from Google Play soon anyway.

Hum I'm not a big expert regarding the BSD 2-clause "Simplified" License. In my opinion, the best license is GNU GPL v3 for this kinf of work, but that's just my opinion...
Yes I'm aware of the article you provide in your response, that's really a shame...
This is where F-Droid will make sense!

The app has been removed. Please report here if you find other copies 👍


Make forceY([0]) optional for line chart and stacked area chart

I think we should be good closing this one, as it is part as #312

@catap can you close this one?


Links in Ballerina community page are not working

Description:

All these links are not working. All of them give 404.

Fixed with #1607


Minor Improvements to LoadingNotificationCommand and IdentifiedWebView

Add the possibility to apply a command to a span
Add the possibility to display a custom view on the loading notification of the interaction interpreter

Coverage decreased (-0.02%) to 99.975% when pulling 8fc6eb46279818a146ebdccb08100623fb83b955 on Minor-Improvements into 9a385ef3b6b0f3b8cc33854069b36958a0b29977 on master.


Broken Pipe Error Between Peer and external Chaincode.

Description
Hello,
When i try to invoke chaincode with below command. I am getting Broken Pipe error in Peer logs.
When the Peer try to connect with Chaincode, TLS handshake happens and then I get broken pipe error.
The Setup is deployed on OCP cluster (Kuberenetes v1.27). There is no connectivity issues as they are in same network.
I have also created Headless service for chaincode deployment.
ERROR:
2024-07-15 09:04:35.602 UTC [grpc] WarningDepth -> DEBU 38e [core] [Channel #134 SubChannel #135] grpc: addrConn.createTransport failed to connect to {
"Addr": "chaincode1-service:9000",
"ServerName": "chaincode1-service:9000",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}. Err: write tcp <IP_ADDRESS>:56446-><IP_ADDRESS>:9000: write: broken pipe
2024-07-15 09:04:35.602 UTC [grpc] InfoDepth -> DEBU 38f [core] [Channel #134 SubChannel #135] Subchannel Connectivity change to TRANSIENT_FAILURE
2024-07-15 09:04:35.602 UTC [grpc] InfoDepth -> DEBU 390 [core] pickfirstBalancer: UpdateSubConnState: 0xc00227c140, {TRANSIENT_FAILURE write tcp <IP_ADDRESS>:56446-><IP_ADDRESS>:9000: write: broken pipe}
2024-07-15 09:04:35.602 UTC [grpc] InfoDepth -> DEBU 391 [core] [Channel #134] Channel Connectivity change to TRANSIENT_FAILURE
2024-07-15 09:04:35.602 UTC [grpc] InfoDepth -> DEBU 392 [core] [Channel #134] Channel Connectivity change to SHUTDOWN
2024-07-15 09:04:35.602 UTC [grpc] InfoDepth -> DEBU 393 [core] [Channel #134 SubChannel #135] Subchannel Connectivity change to SHUTDOWN
2024-07-15 09:04:35.602 UTC [grpc] InfoDepth -> DEBU 394 [core] [Channel #134 SubChannel #135] Subchannel deleted
2024-07-15 09:04:35.602 UTC [grpc] InfoDepth -> DEBU 395 [core] [Channel #134] Channel deleted
2024-07-15 09:04:35.602 UTC 38e6 DEBU [chaincode] Launch -> stopping due to error while launching: write tcp <IP_ADDRESS>:56446-><IP_ADDRESS>:9000: write: broken pipe
failed to create new connection
github.com/hyperledger/fabric/internal/pkg/comm.ClientConfig.Dial
/internal/pkg/comm/config.go:151
github.com/hyperledger/fabric/core/chaincode/extcc.(*ExternalChaincodeRuntime).createConnection
/core/chaincode/extcc/extcc_handler.go:33
github.com/hyperledger/fabric/core/chaincode/extcc.(*ExternalChaincodeRuntime).Stream
/core/chaincode/extcc/extcc_handler.go:45
github.com/hyperledger/fabric/core/chaincode.(*RuntimeLauncher).Launch.func1
/core/chaincode/runtime_launcher.go:90
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1598
error creating grpc connection to chaincode1-service:9000
error cannot create connection for asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5
connection to asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5 failed
2024-07-15 09:04:35.602 UTC 38e7 DEBU [chaincode] Launch -> launch complete
2024-07-15 09:04:35.602 UTC 38e8 DEBU [chaincode] Deregister -> deregister handler: asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5
2024-07-15 09:04:35.602 UTC 38e9 INFO [endorser] callChaincode -> finished chaincode: asset-transfer-basic_9 duration: 5ms channel=mychannel1 txID=ffb61445
2024-07-15 09:04:35.602 UTC 38ea ERRO [endorser] simulateProposal -> failed to invoke chaincode asset-transfer-basic_9, error: write tcp <IP_ADDRESS>:56446-><IP_ADDRESS>:9000: write: broken pipe
failed to create new connection
github.com/hyperledger/fabric/internal/pkg/comm.ClientConfig.Dial
/internal/pkg/comm/config.go:151
github.com/hyperledger/fabric/core/chaincode/extcc.(*ExternalChaincodeRuntime).createConnection
/core/chaincode/extcc/extcc_handler.go:33
github.com/hyperledger/fabric/core/chaincode/extcc.(*ExternalChaincodeRuntime).Stream
/core/chaincode/extcc/extcc_handler.go:45
github.com/hyperledger/fabric/core/chaincode.(*RuntimeLauncher).Launch.func1
/core/chaincode/runtime_launcher.go:90
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1598
error creating grpc connection to chaincode1-service:9000
error cannot create connection for asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5
connection to asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5 failed
could not launch chaincode asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5
github.com/hyperledger/fabric/core/chaincode.(*ChaincodeSupport).Launch
/core/chaincode/chaincode_support.go:87
github.com/hyperledger/fabric/core/chaincode.(*ChaincodeSupport).Invoke
/core/chaincode/chaincode_support.go:203
github.com/hyperledger/fabric/core/chaincode.(*ChaincodeSupport).Execute
/core/chaincode/chaincode_support.go:161
github.com/hyperledger/fabric/core/endorser.(*SupportImpl).Execute
/core/endorser/support.go:126
github.com/hyperledger/fabric/core/endorser.(*Endorser).callChaincode
/core/endorser/endorser.go:120
github.com/hyperledger/fabric/core/endorser.(*Endorser).simulateProposal
/core/endorser/endorser.go:187
github.com/hyperledger/fabric/core/endorser.(*Endorser).ProcessProposalSuccessfullyOrError
/core/endorser/endorser.go:409
github.com/hyperledger/fabric/core/endorser.(*Endorser).ProcessProposal
/core/endorser/endorser.go:350
github.com/hyperledger/fabric/internal/pkg/gateway.(*EndorserServerAdapter).ProcessProposal
/internal/pkg/gateway/gateway.go:41
github.com/hyperledger/fabric/internal/pkg/gateway.(*Server).Evaluate.func1
/internal/pkg/gateway/evaluate.go:64
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1598
failed to execute transaction ffb614459129997724ec2e805100d8a063ed8d7f464a981c63fb3f7dc57cadf4
github.com/hyperledger/fabric/core/chaincode.processChaincodeExecutionResult
/core/chaincode/chaincode_support.go:167
github.com/hyperledger/fabric/core/chaincode.(*ChaincodeSupport).Execute
/core/chaincode/chaincode_support.go:162
github.com/hyperledger/fabric/core/endorser.(*SupportImpl).Execute
/core/endorser/support.go:126
github.com/hyperledger/fabric/core/endorser.(*Endorser).callChaincode
/core/endorser/endorser.go:120
github.com/hyperledger/fabric/core/endorser.(*Endorser).simulateProposal
/core/endorser/endorser.go:187
github.com/hyperledger/fabric/core/endorser.(*Endorser).ProcessProposalSuccessfullyOrError
/core/endorser/endorser.go:409
github.com/hyperledger/fabric/core/endorser.(*Endorser).ProcessProposal
/core/endorser/endorser.go:350
github.com/hyperledger/fabric/internal/pkg/gateway.(*EndorserServerAdapter).ProcessProposal
/internal/pkg/gateway/gateway.go:41
github.com/hyperledger/fabric/internal/pkg/gateway.(*Server).Evaluate.func1
/internal/pkg/gateway/evaluate.go:64
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1598 channel=mychannel1 txID=ffb61445
2024-07-15 09:04:35.602 UTC 38eb DEBU [lockbasedtxmgr] Done -> Done with transaction simulation / query execution [ffb614459129997724ec2e805100d8a063ed8d7f464a981c63fb3f7dc57cadf4]
2024-07-15 09:04:35.602 UTC 38ec WARN [endorser] ProcessProposal -> Failed to invoke chaincode channel=mychannel1 chaincode=asset-transfer-basic_9 error="error in simulation: failed to execute transaction ffb614459129997724ec2e805100d8a063ed8d7f464a981c63fb3f7dc57cadf4: could not launch chaincode asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5: connection to asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5 failed: error cannot create connection for asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5: error creating grpc connection to chaincode1-service:9000: failed to create new connection: write tcp <IP_ADDRESS>:56446-><IP_ADDRESS>:9000: write: broken pipe"
2024-07-15 09:04:35.602 UTC 38ed DEBU [gateway] func1 -> Evaluate call to endorser failed chaincode=asset-transfer-basic_9 channel=mychannel1 txID=ffb614459129997724ec2e805100d8a063ed8d7f464a981c63fb3f7dc57cadf4 endorserAddress=fabric-peer1-service:7061 endorserMspid=Org6MSP error="error in simulation: failed to execute transaction ffb614459129997724ec2e805100d8a063ed8d7f464a981c63fb3f7dc57cadf4: could not launch chaincode asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5: connection to asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5 failed: error cannot create connection for asset-transfer-basic_9:8fda7b2f506305775ba682399d4a421f7d598ce98ce198734b86a2a72c8d6fb5: error creating grpc connection to chaincode1-service:9000: failed to create new connection: write tcp <IP_ADDRESS>:56446-><IP_ADDRESS>:9000: write: broken pipe"
2024-07-15 09:04:35.602 UTC 38ee INFO [comm.grpc.server] 1 -> unary call completed grpc.service=gateway.Gateway grpc.method=Evaluate grpc.request_deadline=2024-07-15T09:06:35.573Z grpc.peer_address=<IP_ADDRESS>:45798 error="rpc error: code = Aborted desc = failed to evaluate transaction, see attached details for more info" grpc.code=Aborted grpc.call_duration=7.12576ms
2024-07-15 09:04:35.613 UTC [grpc] InfoDepth -> DEBU 396 [transport] transport: loopyWriter.run returning. connection error: desc = "transport is closing
Steps to reproduce
No response

the resason of " write: broken pipe“ is alawys two points:
1.The server's host has exceeded the maximum number of connections.
2.The client disconnects before receiving a response from the server.

For the "Broken Pipe" error, you can take the following solutions:
Gracefully Handle Connection Closures:
When writing network applications, ensure that you can gracefully handle connection closures. For example, catch "Broken Pipe" exceptions when attempting to write data and appropriately clean up resources (such as closing sockets).
Add Retry Logic:
For "Broken Pipe" errors that may be caused by network issues, add retry logic to your application. This can help recover communication after brief network interruptions.
Adjust Timeout and Idle Connection Settings:
If the issue is due to timeouts or idle connection closures, try adjusting relevant system or application settings. For example, increase connection timeout times or disable idle connection closure features.
Check System Resources:
Ensure that system resources (such as the number of file descriptors) are sufficient and have not reached their limits. If resources are insufficient, you may need to increase resource limits or optimize the application's resource usage.
Log and Analyze Logs:
By logging and analyzing the logs of network applications, you can better understand the circumstances and causes of "Broken Pipe" errors. This helps identify and resolve underlying issues.
Use a More Stable Network:
If the issue is due to an unstable network, consider using a more stable network connection or adding network redundancy to improve the reliability of communications.


Added missing fields to Institutions

Fixes #4

tests passed for me locally one the second run (after the verified data was updated)... I checked in the updated verified data so not sure why it's failing

oh... I missed a test.


Refactor justify/align to use start/end

Initially, we want to add support for using start/end to match the css properties more closely.
We don't want to break backwards compatibility, so we should keep the old values, but show a deprecation notice that support will be removed in the next breaking change.
These should be warnings that can be silenced using the log level.
This will also unlock the ability to more simply add flex-direction: column to Grid (if we want to go that direction)

This has been added to the next branch


Ampersand symbol issue in unsafe mode of url util function ParseURL()

Current Behavior
The ampersand symbol disappears if it was placed in the end of URL. http://<IP_ADDRESS>/abc/start.xml?===& transforms to http://<IP_ADDRESS>/abc/start.xml?=== in unsafe mode of ParseURL function. The same behavior is observed in safe mode, so there is no difference between two modes in such case.
Expected Behavior
Ampersand in the end of URL should't be deleted during parsing in unsafe mode.
Steps To Reproduce
Run this code:
    package main

    import (
	"fmt"

	urlutil "github.com/projectdiscovery/utils/url"
    )

    func main() {
        URL := "http://<IP_ADDRESS>/abc/start.xml?===&"
	fmt.Println("URL:", URL)
	ParsedURL, _ := urlutil.ParseURL(URL, true)
	fmt.Println("ParsedURL:", ParsedURL)
    }

Output:
URL: http://<IP_ADDRESS>/abc/start.xml?===&
ParsedURL: http://<IP_ADDRESS>/abc/start.xml?===

Environment

OS: Windows 10
Go: go1.22.3 windows/amd64
github.com/projectdiscovery/utils: v0.2.8

This issue relates to another issue

Closing this, see the discussion https://github.com/orgs/projectdiscovery/discussions/5620#discussioncomment-10590747


WordPress rules include WordPress-VIP

I'm getting VIP errors when I use what I assume to be the base WordPress standards.
% phpcs -s --standard=WordPress hooks.php

FILE: .../hooks.php
----------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 3 LINES
----------------------------------------------------------------------
 24 | ERROR | [ ] get_page_by_path is prohibited, please use
    |       |     wpcom_vip_get_page_by_path() instead.
    |       |     (WordPress.VIP.RestrictedFunctions.get_page_by_path)
 26 | ERROR | [x] Concat operator must be surrounded by a single
    |       |     space (Squiz.Strings.ConcatenationSpacing.PaddingFound)
 43 | ERROR | [ ] get_page_by_path is prohibited, please use
    |       |     wpcom_vip_get_page_by_path() instead.
    |       |     (WordPress.VIP.RestrictedFunctions.get_page_by_path)
----------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY

If I use the WordPress-Core standards, it doesn't try to convince me to use wpcom_vip_ functions.
% phpcs -s --standard=WordPress-Core hooks.php

FILE: .../hooks.php
----------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------
 26 | ERROR | [x] Concat operator must be surrounded by a single
    |       |     space (Squiz.Strings.ConcatenationSpacing.PaddingFound)
----------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------

% phpcs -s --standard=WordPress-VIP hooks.php

FILE: .../hooks.php
----------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 3 LINES
----------------------------------------------------------------------
 24 | ERROR | [ ] get_page_by_path is prohibited, please use
    |       |     wpcom_vip_get_page_by_path() instead.
    |       |     (WordPress.VIP.RestrictedFunctions.get_page_by_path)
 26 | ERROR | [x] Concat operator must be surrounded by a single
    |       |     space (Squiz.Strings.ConcatenationSpacing.PaddingFound)
 43 | ERROR | [ ] get_page_by_path is prohibited, please use
    |       |     wpcom_vip_get_page_by_path() instead.
    |       |     (WordPress.VIP.RestrictedFunctions.get_page_by_path)
----------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------

I'm not developing WordPress Core, so I presume I should use the WordPress standards.
I would assume that WordPress-VIP would include WordPress, not the other way around. Am I approaching this wrong?

Your assumption is wrong. See: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards#standards-subsets

Well, let me just close this then. Thank you.


Add first-tier support for ThreadSanitizer

We nominally support TSan instrumentation, and even test basic stacktrace parsing.
However:

Our support for TSan logs is probably missing many cases
We support, but don't help configuration of a known-good external symbolizer (e.g. TSAN_OPTIONS=external_symbolizer_path=/onefuzz/bin/llvm-symbolizer)
We don't test any flags

Add this, for platforms with TSan support.

NOTE: TSan is not integrated with LibFuzzer. See the discussion here.
Fuzzing with TSan will be slow and noisy, with lots of false positives and negatives, and require setting the TSan option halt_on_error=1.
For now, the best use of TSan is via the special builds of the target used with the regression task.


[🐞] qwik new component Error

Which component is affected?
Starters / CLI
Describe the bug
In Utilities section on project structure page, it says by running this command:
pnpm qwik new button
It throws an error:
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
I checked the source code. In my local running environment, (cli.cjs)at line 3034template.relative is undefined.
when i specify template.relative value, A new error has appeared:
(cli.cjs)at line 3049: await import_node_fs7.default.promises.writeFile(fileOutput, templateOut, { encoding: "utf-8" });
Error: EISDIR: illegal operation on a directory, open 'D:\xxx\qwik-xxx\src\components\button'

Then I modified the code from fileOutput to ${fileOutput}/index.tsx and the error disappeared.
I also tried changing the dependency package version
I don’t know if it’s due to my local operating environment, incompatible versions of dependent packages, or other reasons
Reproduction
https://github.com/l6037600/qwik-cli-new-component-error
Steps to reproduce
Run pnpm qwik new button
System Info
System:
    OS: Windows 11
    CPU: Intel(R) Core(TM)
    Memory: 6.00 GB / 12.00 GB
    Shell: PowerShell
  Binaries:
    Node: 20.8.1 - C:\Program Files\nodejs\node.exe
    npm: 8.19.2 - C:\Users\Administrator\AppData\Roaming\npm
    pnpm: 8.9.2 - C:\Users\Administrator\AppData\Roaming\pnpm
  Browsers:
    Edge: 118.0.2088.46
  npmPackages:
    @builder.io/qwik: 1.2.13
    @builder.io/qwik-city: 1.2.13
    undici: 5.22.1
    vite: 4.4.7

Additional Information
No response

I am unable to reproduce this on a clean npm create qwik@latest Need better repro instructions.

I am unable to reproduce this

hi! i have the same problem
pnpm qwik new my-button

https://github.com/Neschadin/qwik-empty

@Neschadin can you try with Qwik 1.2.15 pls?

@Neschadin您可以尝试使用 Qwik 1.2.15 吗？

I still get the same error

I have the same error, the problem seems to be at parseTemplatePath in qwil/cli.cjs
the "relative" attribute is undefined, because the split fails.
I changed it to this, and it works:
function parseTemplatePath(path3, type) {
  console.log("PARSE TEMPLATE PATH:",path3, type);
  // const parts = path3.split(`/${type}/`);
  const parts = path3.split(type);
  return {
    absolute: path3,
    relative: parts[1]
  };
}

@Neschadin can you try with Qwik 1.2.15 pls?

the same

@Neschadin this happens with pnpm only?

@Neschadin this happens with pnpm only?

yeap

@alex-bluetrain you found the right place to modify. Would you like to drop a PR for that pls?


Allow editor to populate the identify popup template

<EMAIL_ADDRESS>

solid MVP implementation; we may look at future enhancements to generate the attribute name population and generate logic


Fixed formatting in Jupyter notebooks for agents and adding markdown …

…files in docs folder
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@isingh09 - Hello, made the changes requested, please review. Thanks.

Please re do this PR following the new layout and the process for creating the required file . We request all files to have a presence on the Cookbook / Recipes Website which is fronting this github repo now. Some of the mandatory sections of the notebook need to include

Overview.
What are we demonstrating .
What use case .
What will you learn.
What is the architectural pattern and why we select this. With a diagram
What are the libraries to install
What model did we choose and why this model
Every cell needs to have a markup


Want features for data annotation

Please bring features to share common data annotations between each entity or model.  I will be no need to define separate separate data annotations for each properties of each entity.
It would be more easy and bring code reusablity more if one can declare common data annotations of different properties because we see that common data annotation is like max length 50, int,  required etc. Are used to once and common for all entities.

This issue was moved to dotnet/corefx#24738


Improper Privilege Management vulnerability in shelljs package

Hi,
git-rev-sync has a dependency on shelljs package version 0.8.4.
Snyk has identified this vulnerability : https://security.snyk.io/vuln/SNYK-JS-SHELLJS-2332187 and the fix is now available .
Remediation : Upgrade shelljs package to version 0.8.5.
Would it possible to upgrade this package please

FYI - this has been resolved in this PR:
https://github.com/kurttheviking/git-rev-sync-js/pull/66

Thank you. :)


Cell's content doesn't move when it swiped

I inserted code:

   static NSString *MyIdentifier = @"MyReuseIdentifier";
      SWTableViewCell *cell = (SWTableViewCell*)[tableView dequeueReusableCellWithIdentifier:MyIdentifier];
     if (cell == nil) {

     cell = [[SWTableViewCell alloc] initWithStyle:UITableViewCellStyleDefault  reuseIdentifier:MyIdentifier];
     cell.rightUtilityButtons = [self rightButtons];
     cell.delegate = self;

But Utility Button overlays cell's content and not move it

@lususvir I am running into the same issue. Did you find a fix?

I didn't find a fix for it. I think I just hid the accessory disclosure indicator and put an icon there so that it moved with the rest of the content.

Thanks for the response!
That's basically what I've settled on as well.

I'm having the same issue as @lususvir. It's just the disclosure indicator that doesn't move. Also, the bottom separators of the cells are having some right margin, which I didn't set.

Just found out that programmatically setting the accessoryType works fine. The problem only occurs when the accessoryType has been set in nib/storyboard (tried both).

Interesting. I'm not using nibs but I do have this issue. I set the accessoryType programmatically but before setting utility buttons.

I faced this same issue, and it had to do with adding subviews manually in the code.
I solved it by creating the elements in the xib/storyboard and then connect them with outlets in the class. It helps also adding auto layout constraints to the elements from the cell.

If you are subclassing SWTableViewCell, pragmatically creating your view, add it to self, use autolayout, this behavior exists as well. It's kind of a hacky solution right now, but I was able to get past it by adding my subviews to self.subview[0].subview[0] and set my constraints around this as the superview. This work because the scrolling piece hooks on to self.subview[0].subview[0] if I'm not mistaken.


Custom resolution of outcome video do not work!

Hi,
I want to share camera with different resolutions by changing width, height and frameRate according to below code:
final Map<String, dynamic> mediaConstraints = {
      'audio': true,
      'video': {
        'width: <width>,
        'height': <height>,
        'frameRate': <frameRate (10-60)>,
        'facingMode': 'user',
        'optional': [],
      }
};
MediaStream stream = await navigator.mediaDevices
        .getUserMedia(mediaConstraints)
        .catchError((e) {
      Log.error("An error occurred while trying to open a webcam stream: '$e'");
});

but it not work!
How to share camera width different resolutions?

As I recall we tried that as well, but it seems to be ignored no matter what values are passed there. It may be either a problem with flutter_webrtc or with BBB itself, but we had no time to research there.


Can write to environment variable?

Hi, I have a requirement that need use environment variable as parameter input to start an application.On other way, we can rewrite the application to accept the config file to solve it but sometimes the application is not owned by us unfortunately. So I need find another way to set env to accomplish it. So does confd support writing to env variable? I can't find any infos in docs.Thanks.

I find out getenv which works for me,thx.

of course! Sure
If u read docs carefully, you will see getenv to retrive env parameters

Cool, so how to write the value to env directly in toml file?? For example:
[template]
src = "hosts.tmpl"
dest = "$env_name"
keys = [
  "/env",
]

Thanks

@yangjunsss .toml configs are not templated by confd, so you can't embed environment variables in them. You can try to template them using sed command in your entrypoint script.

@yangjunsss there is no way to set environment parameters using confd, it was intended to be used to template files.
I suggest the following workaround:

Run confd to template a file (e.g., test.env) in .env format, e.g.

KEY1=VALUE1
KEY2=VALUE2

Run source test.env before running your app to set environment variables from a file.

Closing the issue for now. Please, reopen if the workaround will not help.


Hangs infinitely if body is empty

If you try to make an empty POST request it will hang infinitely. Probably something wrong with this line:
https://github.com/talentlessguy/parsec/blob/1940b6b12aa0849b35b43988e1c65b06f214396f/src/index.ts#L14
for test:
import { App } from '@tinyhttp/app'
import { form } from 'body-parsec'

const app = new App()

app.use(form()).use((req, res) => res.send(req.body)).listen(3000)

curl -X POST localhost:3000

I'm still getting this issue with
app.use(json)
However, if I add parantheses:
TS2322: Type '(req: ReqWithBody, _res: ServerResponse, next: NextFunction) => Promise<void>' is not assignable to type 'Handler<Request, Response<any>>'.   Type '(req: ReqWithBody, _res: ServerResponse, next: NextFunction) => Promise<void>' is not assignable to type 'AsyncHandler<Request, Response<any>>'.     Types of parameters 'next' and 'next' are incompatible.       Type 'NextFunction | undefined' is not assignable to type 'NextFunction'.         Type 'undefined' is not assignable to type 'NextFunction'.

I can't parse any json, always hang when post a json.

@xpader  could you please show the code?


Update commonmark spec to 0.24

I guess that should be updated together with good/bad files to be useful. If not 100% of tests pass, it's better to create issue instead of pr

i see, i'm not familiar with the good and bad files, i just use spec.txt. I'll look into it.

@rlidwka please update spec.

0.24 is out now, so I've updated this PR. How are the good.txt and bad.txt files derived? I don't see them in commonmark.js's test tools: https://github.com/jgm/commonmark.js/tree/master/test

How are the good.txt and bad.txt files derived?

They're generated with specsplit.js, so you can run:
~/markdown-it$ ./support/specsplit.js good /path/to/spec.txt

To generate good.txt, and specsplit.js bad to generate other one. I think they should be named passing.txt and failing.txt really, and first one contains spec tests that markdown-it parses correctly and second one contains the rest. Ideally, we'd not have any failing CM tests (i.e. bad.txt would be 0 size), but sometimes we do.
Unfortunately, the format of tests was changed recently, so it has a showball's chance in hell of working properly. So we'll need to update markdown-it-testgen to understand that format.
P.S.: Travis build passes 'cause tests are run on good.txt which wasn't updated.

Closing, since change is inconsistent.

Small errata: turns out, changing markdown-it-testgen isn't really necessary.
Updated spec in https://github.com/markdown-it/markdown-it/commit/ab36c448647bea4d5d1c1792206ebb24d4af82ab, thanks for the reminder.


Update sql-database-elastic-query-overview.md

Hi @stuartozer, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (stuarto). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Approved via mail from Stuart to me and Sidney.

Made another to update the title!
Date: Mon, 1 Jun 2015 11:27:54 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [azure-content] Update sql-database-elastic-query-overview.md (#3664)
Merged #3664.
—
Reply to this email directly or view it on GitHub.


Add deep_text method to Node

Added deep_text method and doctest

I don't think that this is a good idea. Text processing rules in XML are absurd and in most cases this function will return invalid/unexpected results. For example, it doesn't care about xml:space.
Another example is SVG, which has it's own whitespaces processing rules.

Good point. Also if someone (like myself) really needs something this, it is possible for them to add their own function for their own use case, since this only uses the public api. I will close this. Thanks for the feedback!


What prompts can I use for layout-aware t2i generation

What prompts can I use for layout-aware t2i generation to reproduce the same result in your paper?

Layouts are generated in the early stages of generation, corresponding to lower-numbered prompt.
Please try to add the token embedding of the input image in the 1st, 2nd and 3rd prompt position
e.g.
prospect_words = ['strawberry cup cakes',  # 10 generation ends\
                       'strawberry cup cakes',  # 9 \
                       'strawberry cup cakes',  # 8 \
                       'strawberry cup cakes',  # 7 \
                       'strawberry cup cakes',  # 6 \
                       'strawberry cup cakes',  # 5 \
                       'strawberry cup cakes',  # 4 \
                       'strawberry cup cakes',  # 3 \
                       '*',  # 2 \
                       '*',  # 1 generation starts\
                      ], \

and thanks for your question, I have also improved the README:)


Jewel VirtualComboBox only recognises itemRenderers assigned via className

Those set through property "itemRenderer" in the mxml tag are not recognised.
It can be checked in the TDJ. If we change the mapping of the ItemRenderer in the VirtualComboBox of the VirtualListsPlayGround.mxml view from className to itemRenderer tag.
This is how it is now:

The result is:

If we change it to:

The result is:

I have located the problem in VirtualComboBoxPopUpView by overriding the function "get list". When creating the List associated to the dropdown/popup the itemRenderer assigned to the VirtualCombobox must be mapped to it.
(I have replicated the same function of ComboBoxPopUpView)
Are the modifications correct?
Thx.

Hi,
After further debugging the code, I believe that the patched code should be moved to "get list()", as it is in the ComboBoxPopUpView.as
In the "set strand", it first executes the assignment in the parent class, "super.strand = value" which references "list" in several lines and each time it does the "get list()" it creates _list (new VirtualList()). I don't know why it doesn't save the value of _list from one call to another...

The code would look like this:

I have found that with this implementation the _list variable takes effective value on the first call.
What do you think?
Hiedra

I have added the proposed modifications in the PR #1154


Support for gcode_macro

Add (incomplete) support for G-Code macros.
Some architecture notes:

The template environment is provided by minijinja. Unfortunately Klipper decided to use non-standard notation for expressions (single braces { expr } instead of the normal double braces {{ expr }}), necessitating an additional regex replace step.
The printer object is exposed using the struct PrinterObj utilizing minijinja's dynamic object support. I previously simply serialized the printer object as local context for template evaluation, but since the configuration can be a little large this made macro evaluation relatively slow. Still perfectly adequate in terms of runtime, but why not improve performance a little. So I decided to expose the printer attributes using PrinterObj.
The Moonraker configuration support was moved to another file for clarity. The settings can't be deserialized directly because the macros have unpredictable keys like gcode_macro foobar.

TODOs (should definitely be fixed):

[ ] lib_klipper shouldn't depend on serde_json
[ ] Support for local JSON configuration is disabled for simplicity atm, but should be an easy fix
[ ] Re-enable line number support (was disabled since it interferes with certain macro names)
[ ] Some random clippy fixes made their way into the PR, I'll remove those later to keep the PR self-contained

Known limitations:

replace_existing is not supported
Dynamic attributes of the printer object (i.e. attributes not set in the configuration) need to be exposed/translated manually. Currently only a commonly used subset of attributes are exposed (toolhead.position, toolhead.axis_maximum and toolhead.homed_axes - the latter is always set to "xyz")
Certain filters are not available in minijinja by default, float, int, min, and max are implemented atm
The abs filter in minijinja does not work for unsigned integers which are automatically used in some cases, throwing unnecessary errors - this is an upstream bug (?), but perhaps it can be fixed locally
There is no limitation on stack depth - during macro evaluation, the generated G-Code is simply parsed and executed immediately. This could of course cause issues if macros call themselves recursively or perform other shenanigans.

Hi @hesiod
Are you still working on this?
Best regards,
Lasse

@dalegaard Actually I was waiting for some initial feedback (on whether you're interested in this feature in principle) before I worked on it any further 🙂
FYI, there is one known issue with the PR currently: I misunderstood how Klipper's macro variables (gcode_variable etc.) are supposed to work. They are currently set in the wrong scope, but I can't remember the details atm. But it shouldn't be a big deal to fix this.

Hi @hesiod
That's my bad, I hadn't considered you were looking for feedback at this stage. Sorry about that.
I'm very interested in supporting this feature if it can be demonstrated to work well in real world use cases. Supporting every possible macro under the sun isn't an objective, but e.g. the FastGyroidInfill of #33 seems like it could be supported pretty well.
I haven't done any code checks at this point, but I'll try to take a look over things tonight.
Best regards,
Lasse


[FLINK-24813][table-planner]Improve ImplicitTypeConversionITCase

What is the purpose of the change
delete the test file ImplicitTypeConversionITCase and union them into the ImplicitConversionEqualsFunctionITCase to have the same code style with CastFunctionITCase
Brief change log

delete the unused codes
*union the test cases to the current test cases *

Verifying this change
Test cases have been added to verify this change.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving):no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented?

Thx for taking care of this: @xuyangzhong
I'd like to suggest some changes for those tests.

The validity of implicit tests is tested in LogicalTypeCasts and we should try and separate the test of if an implicit cast is valid to the actual cast conversion itself which is already testing in CastFunctionITCase.
If there are any new cases that deserve extra tests, those can be added directly in the main method allTypesBasic, or in a new method that tests corner cases similar to CastFunctionITCase#numericBounds

Hi, thanks for you to review my code, @matriv :) .I want to do some responses to your review.

LogicalTypeCasts  seems useless in the case "SELECT 1 = '1' FROM xxx" because the case doesn't call the function CAST, so the CAST doesn't work, and can't detect this bad pattern. However, "SELECT 1 = '1' FROM xxx" is always "false", that is what I want to avoid and to throw an exception to remain users.

Please bear with me, maybe I'm still missing the whole context. Can we just test that SELECT x = y produces the correct implicit cast under the scenes, and then just make sure that this implicit cast is supported in LogicalTypeCasts?

The Flink's default type coercion is off now. And in order to solve the wrong result in SELECT int = varchar, maybe we should open the option, but it is a big work that needs full discussion. So avoid to cause the wrong result, I forbid this kind of SQL by throwing an exception. Aim to make sure "=" between other types work correctly, I write these test cases in ImplicitConversionEqualsFunctionITCase that you can see, because only  SELECT int = varchar finds this bug currently.
This prohibited behavior is only a temporary solution to this bug. To solve the bug fundamentally, we will do just what you say:

SELECT x = y produces the correct implicit cast under the scenes, and then just make sure that this implicit cast is supported in LogicalTypeCasts (in Table API).

@flinkbot run azure

@flinkbot run azure

@xuyangzhong @godfreyhe Is this good to go?
@xuyangzhong Can you please rebase with master to resolve the conflicts?

close it with: superseded by #17962

@flinkbot run azure


Curtain service not work

Describe the error
I have 5 Zemismart motors, 3 shutters, 2 cornices. 4 work perfectly, and the 5th displays the status correctly, but does not respond to opening and closing commands, as well as with percentage opening
Expected Behavior
response to buttons open close, open by %
I got the Device Debugging curtain with these options does not work
    mach_operate Enum

{
"range": [
"ZZ",
"FZ",
"STOP"
]
}
opposite Boolean
"{true,false}"
position Integer
{
"unit": "%",
"min": 0,
"max": 100,
"scale": 0,
"step": 1
}
This curtain works perfectly
control Enum
{
"range": [
"open",
"stop",
close
]
}
percent_control Integer
{
"unit": "%",
"min": 0,
"max": 100,
"scale": 0,
"step": 1
}

Hi, Could you provide some details of the working curtain and not working curtain ? category, product_id, device functions, device status. I'm going to rewrite curtain class.

Got it. I will try.

@xrust83 Please try 1.6.0-beta.11, should be fixed


[DOCFIX] Improve docs for HDFS and Mapreduce

@apc999 @calvinjia

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10006/
Test PASSed.

@ifcharming  can you reopen this PR to branch-1.1 instead of master? thanks


Change port in config.toml

Is there a possibility to change the port of redactedhook in the config.toml? I have a seedhost shared seedbox and there  I get the error:
FTL Failed to start server error="listen tcp <IP_ADDRESS>:42135: bind: address already in use" Maybe there is someone else on the same box using it or something.
I can't use docker to build.

Hi! Yes it will be possible in the next version. There is a PR up with that feature in it. I should merge that soon. Will let you know!

Thanks for the answer. How soon do you think it will be? I'm asking because I've bought this seedbox for 30 days. Should I cancel it?

Thanks for the answer. How soon do you think it will be? I'm asking because I've bought this seedbox for 30 days. Should I cancel it?

I'll try to make a new release for you tonight👍

This would be amazing, thanks!

New release published. Hopefully no bugs 😄 I can't dedicate time to fix those right now.

Thanks for the super quick fix. Last question how to config this in the config.toml.
host = "<IP_ADDRESS>"
port = "42316"
Does not work.

2024-06-01 18:42:38 DBG Config file read: config.toml
2024-06-01 18:42:38 INF Starting server on <IP_ADDRESS>:42136
2024-06-01 18:42:38 INF Version: 0.5.0, Commit: 2ca8a0cb6da4e82bffa27733f1e87aea5f309623, Build Date: unknown
This worked. Thanks so much.

Awesome! Happy to help👍


Possibility of getting this working with nftables

I've been using docker-ipv6nat for a while on my old server and am pretty happy with it. On a new server I intended to use nftables, which is basically working fine, using this guide.
The problem I have is that I can't use static assigned IP addresses, since this isn't supported in docker-compose. (at least in version 3 files, version 2 apparently works)
This kind of forces me to fall back to "the old way" and let Docker handle the IP assignment, but then I can't put in static nftables rules for the exposed containers.
I'm fine with running this workaround again, but it obviously only supports iptables. I don't really know Go and a quick check of the code made my head spin, so I'd like to use this issue as a discussion if nftables support is even possible for this project.
The only thing that needs to happen is to create a forward rule when a container comes up, nothing else. The rest of the setup is already handled in the configured nftables config (as far as I can see). This is pretty much the same thing docker-ipv6nat is already doing, just with other commands.
There are iptables-compat tools that use the old iptables syntax but creates nftables rules, but I don't know if this could work with docker-ipv6nat.

I'd like to keep docker-ipv6nat as close to Docker as possible, as far as functionality. I'm not sure if Docker supports nftables and I don't have any experience with nftables myself.
If you could replace your ip6tables command with a wrapper that uses iptables-compat, shouldn't it work, without modifying docker-ipv6nat?

I'm not sure if Docker supports nftables and I don't have any experience with nftables myself.

It actually doesn't (https://github.com/moby/moby/issues/26824). While thinking a bit more about this I realized that docker-ipv6nat would have to set IPv4 forward rules in this case too, since you (have to?) disable iptables in Docker completely so it doesn't mess with nftables.

If you could replace your ip6tables command with a wrapper that uses iptables-compat, shouldn't it work, without modifying docker-ipv6nat?

After creating the issue I checked out the go-iptables library docker-ipv6nat is using and realized it simply calls iptables instead of using some API. I already played around with a special debian Docker container that replaces iptables with iptables-nftables-compat, but didn't put much more time into it due to the general missing nftables support described above.
I guess for docker-ipv6nat it only makes sense to wait for Docker itself to support nftables and then implement support for it, in case Docker doesn't include some kind of IPv6 NAT itself then. (https://github.com/docker/libnetwork/pull/2023)
Especially considering that the guide I linked in the original issue is actually about disabling the Docker NAT magic and controlling it manually – kind of defeats the purpose getting docker-ipv6nat in the mix. The main problem is docker-compose not supporting static IPs in compose file version 3+.

nftables is also no longer considered a modern solution, with the advent of bpfilter https://marc.info/?l=linux-netdev&m=151878844503670&w=2

Eh, I don't think so? At least not for this reason. nftables is stable and ready to use in Debian Stretch. Who knows when bpfilter will turn up in stable distributions. I mean, just read the first sentence in the linked mailing list thread:

This is a very rough and early proof of concept that implements bpfilter.

LWN has an article on it dated Feb 19 that states in conclusion:

The end result is that we'll probably not see bpfilter in the mainline kernel in the immediate future. Given the developers who have worked on it, though, bpfilter is clearly a serious initiative that is firmly aimed at getting into the mainline eventually. If it truly proves to be a better solution to the network packet-filtering problem, those developers seem likely to prevail eventually.

Regarding closing this issue: I'm usually against having open issues that only document a specific edge case since wiki entries are in most cases superior in those situations, but this issue nonetheless may help people researching how to get IPv6 working in Docker. It does that while being closed too, though. So I'd say go ahead, close the issue, but for other reasons than bpfilter ;)
I've been running the "manual" nftables setup for a while now, by the way. Works really great, though having to add each new subnet to the nftables rules can get tedious, otherwise containers in new networks won't be able to connect to the outside world. Doesn't happen often on my server and is just a quick edit of the nftables.conf, so I'm completely fine with it.

Thanks for the extended explanation! I'll close this then, since it's out-of-scope for this project.

@Strayer https://lkml.org/lkml/2018/5/21/1178


Configuration init doesn't accept "access_token"

Is there any other way to init the configuration?
The following example shown in the readme doesn't seem to work as the argument 'access_token' isn't accepted from the Configuration Class.
configuration = phasetwo.Configuration(
    host = "https://app.phasetwo.io/auth/realms"
    access_token = keycloak_admin.token()
)

Thank you.

Good catch. Looks like this got accidentally clobbered in a recent update. Will add it back.

5fbdfb1


patch: better render of functions

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Improve e2e environment setup

Use loopback IP instead of hostname
This uses a subdomain-less configuration in the Maps API to avoid resolving the subdomain. See https://github.com/CartoDB/carto-vl/pull/1091 for more details.
Pass extra arguments from the parent script
Allowing, for instance, to grep specific tests.
Future improvements

Being able to use a different Maps API branch than master.
Bind to an unused port to avoid conflicts when starting the Maps API application.

@rochoa not sure why, but even rebuilding the docker image, I get this error  with 'undefined-geometry-type' test

Part of this PR is superseded by #1091. Specifically, we will no longer validate the hostname as it will use a lookback IP instead of a hostname.

This is now the continuation of https://github.com/CartoDB/carto-vl/pull/1091. Instead of validating the hostname, it uses an IP and a different configuration mechanism for the Maps API.


WIP: Kubernetes discovery service

First try of kubernetes discovery service

This change is

Coverage increased (+0.01%) to 53.465% when pulling 0de605d07ff73219e6634a89493cca33f5f42605 on kubernetes-discovery into 97dbb002a69e45deaa5557ad8537d0e23a90f28d on master.


Userspace conversion fails on large image (48GB)

What happened in your environment?
Trying to convert a large image (48GB) in the userspace:
/opt/overlaybd/snapshotter/convertor -r my.registry.com/project/repo -u user:password -i 0.1 --overlaybd 0.1_obd

The conversion always fails with an error ERRO[2451] failed to build overlaybd: failed to convert layer 17: failed to overlaybd-apply: 2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll.
Output:
INFO[0016] layer 15 uploaded
INFO[0122] downloaded layer 17
INFO[1225] downloaded layer 16
INFO[2139] layer 16 committed, uuid: c0d9066d-6668-3d07-c7b7-17aa5d37f7be, parent uuid: 9fcac1fb-2ab9-586c-7039-782bfc7790ee
INFO[2141] layer 16 converted
ERRO[2451] failed to build overlaybd: failed to convert layer 17: failed to overlaybd-apply: 2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/build/_deps/photon-src/io/signal.cpp:265|sync_signal_init:signalfd initialized
2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/src/image_service.cpp:169|read_global_config_and_set:using config /etc/overlaybd/overlaybd.json
2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/src/image_service.cpp:183|read_global_config_and_set:set audit_path:/var/log/overlaybd-audit.log
2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/src/image_service.cpp:195|read_global_config_and_set:[global_conf.logConfig().logPath()=/var/log/overlaybd.log]
2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/src/image_service.cpp:209|read_global_config_and_set:set log_level: 1
2023/09/11 15:24:27|INFO |th=000055B14C24B120|/src/src/image_service.cpp:212|read_global_config_and_set:set log_path: /var/log/overlaybd.log, log_size: 10485760, log_num: 3
failed to extract
: exit status 255

The layer 17 mentioned in the error is the largest layer of the image which is ~45GB.
{
  "schemaVersion": 2,
  "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  "config": {
    "mediaType": "application/vnd.docker.container.image.v1+json",
    "size": 10904,
    "digest": "sha256:37aacfb983164414c15b13feff9dd015f502f1f498c26ba5f3f1fbfa9a27d6c3"
  },
  "layers": [
    .........
    {
      "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
      "size":<PHONE_NUMBER>0,
      "digest": "sha256:f4e8336fc6f74e49e99d3de5a6de2dd3e7093cb15fc705ba17f0189aaa5d204c"
    },
    {
      "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
      "size":<PHONE_NUMBER>,
      "digest": "sha256:76775a8b477ab2c7283cac2d570756525ec86a1ba3e0cb9a91fd27b30ab1ab86"
    },
  ]
}

What did you expect to happen?
Conversion should succeed.
How can we reproduce it?
I haven't found a way to repro it with a random image I built with a 45GB layer.

Ubuntu 20.04
Are you willing to submit PRs to fix it?

[ ] Yes, I am willing to fix it.

Please let me know if there are steps I can follow to collect the relevant logs.

It looks that auto-expansion is needed.

https://github.com/containerd/accelerated-container-image/blob/ddba7a33cbd9198cfe7004b9a8c13a7f85106479/cmd/convertor/builder/overlaybd_builder.go#L292C17-L292C17
func (e *overlaybdBuilderEngine) create(ctx context.Context, dir string) error {
	return utils.Create(ctx, dir, "-s", "64")
}

currently, it is a 64GB hard code for overlaybd device size, you can change it to temporarily avoid this problem

https://github.com/containerd/accelerated-container-image/blob/ddba7a33cbd9198cfe7004b9a8c13a7f85106479/pkg/snapshot/storage.go#L654C1-L661C2
func (o *snapshotter) prepareWritableOverlaybd(ctx context.Context, snID string) error {
	// TODO(fuweid): 256GB can be configurable?
	args := []string{"64"}
	if o.writableLayerType == "sparse" {
		args = append(args, "-s")
	}
	return utils.Create(ctx, o.blockPath(snID), args...)
}

"64" (64GB) is default size, you can modify it for POC.

An option could be added to config overlaybd device size after release v1.0.0

Thanks for the responses. To confirm, for userspace conversion, I can change it in overlaybd_builder.go to work around. And for obdconv, I can change pkg/snapshot/storage.go. Is that correct?

Thanks for the responses. To confirm, for userspace conversion, I can change it in overlaybd_builder.go to work around. And for obdconv, I can change pkg/snapshot/storage.go. Is that correct?

Yes, that is it.

Made the changes and tried. It fixed obdconv but not userspace conversion.
Steps I did

Make the changes and run make.
Run mv bin/* /opt/overlaybd/snapshotter
Restart systemctl restart overlaybd-snapshotter, and also systemctl restart overlaybd-tcmu.

Verify

Convert with obdconv and it worked

/opt/overlaybd/snapshotter/ctr obdconv large-image:0.1 large-image:0.1_obd

Convert in userspace and it failed with the same error

/opt/overlaybd/snapshotter/convertor -r my.registry.com/project/repo -u user:password -i 0.1 --overlaybd 0.1_obd

INFO[0151] layer 13 committed, uuid: 245daafe-aa32-31b7-7c10-d18dcbf9895e, parent uuid: 076fb541-99fc-ce35-9782-e3b35fbd6bac
INFO[0152] layer 13 converted
INFO[0169] layer sha256:723afa92c821479af9243dbb6b21b69694a0e3ae66bdf874396b0be38c53028d exists
INFO[0169] layer 13 uploaded
INFO[2051] downloaded layer 14
ERRO[2613] failed to build overlaybd: failed to convert layer 14: failed to overlaybd-apply[native]: 2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/build/_deps/photon-src/io/signal.cpp:265|sync_signal_init:signalfd initialized
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:169|read_global_config_and_set:using config /etc/overlaybd/overlaybd.json
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:183|read_global_config_and_set:set audit_path:/var/log/overlaybd-audit.log
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:195|read_global_config_and_set:[global_conf.logConfig().logPath()=]
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:209|read_global_config_and_set:set log_level: 1
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:212|read_global_config_and_set:set log_path: /var/log/overlaybd.log, log_size: 10485760, log_num: 3
failed to extract
: exit status 255

Made the changes and tried. It fixed obdconv but not userspace conversion.
Steps I did

Make the changes (I updated to 256) and run make.
Run mv bin/* /opt/overlaybd/snapshotter
Restart systemctl restart overlaybd-snapshotter, and also systemctl restart overlaybd-tcmu.

Verify

Convert with obdconv and it worked

/opt/overlaybd/snapshotter/ctr obdconv large-image:0.1 large-image:0.1_obd

Convert in userspace and it failed with the same error

/opt/overlaybd/snapshotter/convertor -r my.registry.com/project/repo -u user:password -i 0.1 --overlaybd 0.1_obd

INFO[0151] layer 13 committed, uuid: 245daafe-aa32-31b7-7c10-d18dcbf9895e, parent uuid: 076fb541-99fc-ce35-9782-e3b35fbd6bac
INFO[0152] layer 13 converted
INFO[0169] layer sha256:723afa92c821479af9243dbb6b21b69694a0e3ae66bdf874396b0be38c53028d exists
INFO[0169] layer 13 uploaded
INFO[2051] downloaded layer 14
ERRO[2613] failed to build overlaybd: failed to convert layer 14: failed to overlaybd-apply[native]: 2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/build/_deps/photon-src/io/signal.cpp:265|sync_signal_init:signalfd initialized
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:169|read_global_config_and_set:using config /etc/overlaybd/overlaybd.json
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:183|read_global_config_and_set:set audit_path:/var/log/overlaybd-audit.log
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:195|read_global_config_and_set:[global_conf.logConfig().logPath()=]
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:209|read_global_config_and_set:set log_level: 1
2023/09/12 21:29:48|INFO |th=0000555F24695800|/src/src/image_service.cpp:212|read_global_config_and_set:set log_path: /var/log/overlaybd.log, log_size: 10485760, log_num: 3
failed to extract
: exit status 255

Let me know if I missed anything.

You may try pulling the latest commit, #222 . add --mkfs flag for convertor.

You may try pulling the latest commit, https://github.com/containerd/accelerated-container-image/pull/222 . add --mkfs flag for convertor.

Tried it but got the same error:
/opt/overlaybd/snapshotter/convertor -r my.registry.com/project/repo -u user:password -i 0.1 --mkfs --overlaybd 0.1_obd

INFO[0140] downloaded layer 13
INFO[0140] layer 13 converted
INFO[0156] layer sha256:723afa92c821479af9243dbb6b21b69694a0e3ae66bdf874396b0be38c53028d exists
INFO[0156] layer 13 uploaded
INFO[1950] downloaded layer 14
ERRO[2522] failed to build overlaybd: failed to convert layer 14: failed to overlaybd-apply[native]: 2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/signal.cpp:265|sync_signal_init:signalfd initialized
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:169|read_global_config_and_set:using config /etc/overlaybd/overlaybd.json
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:183|read_global_config_and_set:set audit_path:/var/log/overlaybd-audit.log
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:195|read_global_config_and_set:[global_conf.logConfig().logPath()=]
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:209|read_global_config_and_set:set log_level: 1
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:212|read_global_config_and_set:set log_path: /var/log/overlaybd.log, log_size: 10485760, log_num: 3
failed to extract
: exit status 255

You may try pulling the latest commit, #222 . add --mkfs flag for convertor.

Tried it but got the same error:
/opt/overlaybd/snapshotter/convertor -r my.registry.com/project/repo -u user:password --mkfs -i 0.1 --overlaybd 0.1_obd

INFO[0140] downloaded layer 13
INFO[0140] layer 13 converted
INFO[0156] layer sha256:723afa92c821479af9243dbb6b21b69694a0e3ae66bdf874396b0be38c53028d exists
INFO[0156] layer 13 uploaded
INFO[1950] downloaded layer 14
ERRO[2522] failed to build overlaybd: failed to convert layer 14: failed to overlaybd-apply[native]: 2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/signal.cpp:265|sync_signal_init:signalfd initialized
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:169|read_global_config_and_set:using config /etc/overlaybd/overlaybd.json
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:183|read_global_config_and_set:set audit_path:/var/log/overlaybd-audit.log
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:195|read_global_config_and_set:[global_conf.logConfig().logPath()=]
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:209|read_global_config_and_set:set log_level: 1
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:212|read_global_config_and_set:set log_path: /var/log/overlaybd.log, log_size: 10485760, log_num: 3
failed to extract
: exit status 255

for convertor, more logs is output to /var/log/overlaybd.log. Please check this log for more information.

You may try pulling the latest commit, #222 . add --mkfs flag for convertor.

Tried it but got the same error:
/opt/overlaybd/snapshotter/convertor -r my.registry.com/project/repo -u user:password --mkfs -i 0.1 --overlaybd 0.1_obd

INFO[0140] downloaded layer 13
INFO[0140] layer 13 converted
INFO[0156] layer sha256:723afa92c821479af9243dbb6b21b69694a0e3ae66bdf874396b0be38c53028d exists
INFO[0156] layer 13 uploaded
INFO[1950] downloaded layer 14
ERRO[2522] failed to build overlaybd: failed to convert layer 14: failed to overlaybd-apply[native]: 2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/signal.cpp:265|sync_signal_init:signalfd initialized
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/build/_deps/photon-src/io/epoll.cpp:289|new_epoll_engine:Init event engine: epoll
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:169|read_global_config_and_set:using config /etc/overlaybd/overlaybd.json
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:183|read_global_config_and_set:set audit_path:/var/log/overlaybd-audit.log
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:195|read_global_config_and_set:[global_conf.logConfig().logPath()=]
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:209|read_global_config_and_set:set log_level: 1
2023/09/13 05:35:15|INFO |th=0000561DA5F1A8C0|/src/src/image_service.cpp:212|read_global_config_and_set:set log_path: /var/log/overlaybd.log, log_size: 10485760, log_num: 3
failed to extract
: exit status 255

64 is still need to change to larger number. did you change it?

Yes I changed to 256.
cmd/convertor/builder/overlaybd_builder.go
func (e *overlaybdBuilderEngine) create(ctx context.Context, dir string, mkfs bool) error {
        opts := []string{"-s", "256"}
        if mkfs {
                opts = append(opts, "--mkfs")
        }
        return utils.Create(ctx, dir, opts...)
}

pkg/snapshot/storage.go
func (o *snapshotter) prepareWritableOverlaybd(ctx context.Context, snID string) error {
        // TODO(fuweid): 256GB can be configurable?
        args := []string{"256"}
        if o.writableLayerType == "sparse" {
                args = append(args, "-s")
        }
        return utils.Create(ctx, o.blockPath(snID), args...)
}

@tianouya-db please pull commit #225 and retry.
If it still fails, please check /var/log/overlaybd.log for more details, and let me know.

@yuchen0cc it seems to work now. Thanks for the fix! Meanwhile, will there be a change to increase 64 to a larger number, e.g. 256?

An option --vsize is added to convertor to custamize overlaybd virtual block device size.


Send announcements only to valid permits

Description
Send announcements only to valid permits
Context
PV-764
How Has This Been Tested?
Manually.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a87e9a7) 84.25% compared to head (077031c) 84.28%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #478      +/-   ##
===========================================
+ Coverage    84.25%   84.28%   +0.03%
===========================================
  Files          160      160
  Lines         9830     9849      +19
===========================================
+ Hits          8282     8301      +19
  Misses        1548     1548

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


test/K8sServices: re-enable IPv4 fragment tests on kernel 4.19

The test for fragment tracking support got a fix with commit 0e772e7a1e73 ("test: Fix fragment tracking test under KUBEPROXY=1"), where the pattern for searching entries in the Conntrack table accounts for DNAT not happening if kube-proxy is present.
Following recent changes in the datapath and tests for the Linux 4.19 kernel, DNAT is now used even with kube-proxy, provided bpf_sock is in use. This led to CI failures, and the test was disabled for 4.19 kernels with commit 1120aed4144c ("test/K8sServices: disable fragment tracking test for kernel 4.19").
Now that complexity issues are fixed (see #11977 and #12045), let's enable the test on 4.19 again. Ignore DNAT only if kube-proxy is present and bpf_sock (host-reachable services) is not in use. This is also the case for net-next kernels (this didn't fail in CI before because we do not test with kube-proxy on net-next).
Note that (as far as I know) both 4.19 and net-next always use bpf_sock in CI runs, so the check on hostReachableServices is currently superfluous. Let's have it all the same, in case something changes in the future, to avoid unexpected breakage.

test-me-please

Coverage increased (+0.03%) to 37.118% when pulling 8f04915e0542a1424d2d61d8c20484fed72ed1a8 on pr/qmonnet/fragtest_4-19 into f949c1b1c5d8cc6582c8f0354c4cc242792d4126 on master.

retest-runtime


Documentation steps not working and no hopes of improvement and clarity on documentation ever become good

What is this documentation ? All steps followed exactly mentioned in this article but still getting error and stuck. This is the reason people go for google search than your documentation :(
Severity	Code	Description	Project	File	Line	Suppression State
Error	DT1001	Service webapp has neither an image nor a build context specified. At least one must be provided.	docker-compose	C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Sdks\Microsoft.Docker.Sdk\build\Microsoft.VisualStudio.Docker.Compose.targets	201
Also you mentioned docker-compose.yml is to be little tweaked. deleting everything from that and keep only port details you mean ?
If Microsoft is not doing documentation properly and make the dev community comfortable, everyone shift to other technologies that will curse you. Think seriously and do better job.

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

ID: 95aa8619-2154-00fb-5994-09b7a9673e03
Version Independent ID: 182cacc8-12d1-70ac-6005-71d4f6f420d5
Content: Build ASP.NET Core applications deployed as Linux containers into AKS/Kubernetes clusters
Content Source: docs/architecture/containerized-lifecycle/design-develop-containerized-apps/build-aspnet-core-applications-linux-containers-aks-kubernetes.md
Product: dotnet-architecture
Technology: containerized-lifecycle
GitHub Login: @nishanil
Microsoft Alias: nanil

Hi @nareshnaidug5git, for reference you can refer to the source code present on github repo https://github.com/dotnet-architecture/explore-docker. We are reviewing the documentation and update it accordingly.

The PR has been merged to update the document, the issue can be closed now.

Fixed by #31925


Fixed hover tooltips for Curve and Path types

Currently dimensions that shouldn't be are appearing in the hover tooltips. Additionally on CurvePlot the NdOverlay dimension information isn't supplied at all. I've also made various fixes to make color and alpha option work correctly in batched mode.

Looks good to me, and would be very welcome!

There is a real bokeh notebook test failure because the previous data included wrong hover label. Will have to rebuild. I've also added various unit tests to check the correct hover information is set.

Looks good to me too and the tests have passed. Ready to merge?

Yep, go ahead.


Broken for players served over HTTPS  (e.g. Google Music)

On Chrome 36 (Linux, but probably doesn't matter), KeySocket is broken by new security limitations:
[blocked] The page at 'https://play.google.com/music/listen?u=1#/all' was loaded over HTTPS, but ran insecure content from 'ws://localhost:1337/': this content should also be loaded over HTTPS.
It's possible that just changing the scheme to "wss" will solve this, but I don't know if all of the server implementations which KeySocket uses automatically support secure connections.

HTTPs doesn't have anything to do with this. Closing


windows glob sorting

Stuff relies on getting things from glob in alphabetical order. Posix sorts glob results. Does my windows glob implementation?

Fixed in #58


No overlapping error is thrown when booking a leave within another leave date range.

Hello, thank you first for this application which is very useful,
I found a problem in the application and also within the cloud hosted app, it concerns the overlapping of leaves, assuming we have two leaves of types 'holiday' and 'sick leave' both with x days in limit and both are using allowance, for example, when your book a leave for type 'holiday' let says for start_date 08/02/2021 to end_date 12/02/2021 it get inserted.
Then when your book a leave for any type 'holiday' or 'sick leave' let says for start_date 09/02/2021 to end_date 11/02/2021 or any dates between those dates it get also inserted and no overlapping error is thrown, after many test i found that booking leaves is possible between the second day of the start date of the previous request and before last day of the end date of that request. (The algorithm is checking only the start_date and the end_date not the days between)
I don't know if this policy is part of the system or a bug, but logically it doesn't make sense to accept a leave request within another leave date range.
Please correct me if misunderstand something.
Note: using allowance or not doesn't change anything about this problem also the status  (whether the request is approved or still open)

Hello everyone,
For all the people who are considering this problem, and looking for a solution, this is how i managed to solve it :
In lib/model/mixin/user/absence_aware.js ( From line 122) this is the changes :
In the validate_overlapping function,
var this_user = this;

var start_date_filter = {
  $lte : moment.utc(new_leave_attributes.to_date).add(1,'days').format('YYYY-MM-DD'),
};

var end_date_filter = {
  $gte : new_leave_attributes.from_date
};

// Where condition : (`Leave`.`date_start` <= date_end AND `Leave`.`date_end` >= date_start)
return this_user.getMy_leaves({
  logging: console.log,
  where : {
    $and : [
      { status : { $ne : sequelize.models.Leave.status_rejected() } },
      { status : { $ne : sequelize.models.Leave.status_canceled() } },
      { date_start : start_date_filter },
      { date_end : end_date_filter },
    ],
  },
})

.then(function(overlapping_leaves){

  // Check there are overlapping leaves
  if (overlapping_leaves.length === 0){
      return Promise.resolve(1);
  }

  //Deactivate fit_with_leave_request check
  //var overlapping_leave = overlapping_leaves[0];
  //if (overlapping_leave.fit_with_leave_request(
  //      new_leave_attributes
  //)){
  //    return Promise.resolve(1);
  //}

  // Otherwise it is overlapping!
  var error = new Error('Overlapping booking!');
  error.user_message = 'Les dates choisis se chevauchent avec d\'autres dates!';
  throw error;

});


Instance on private subnets

Hi everyone,
Is there any reason for not deploying indexer and search head instances into a private subnets and only put the LoadBalancer into public ?
Sorry for my dummy question and thx for your answers.

It's possible to do it this way, but you wouldn't have access to the search head if you didn't deploy a search head cluster (SHC).  The ELB for search heads is only created if SHC is enabled.  You'd also lose any ability to send data to the indexers from subnets that weren't local to the indexers and you weren't peering to.
Essentially, the Splunk QuickStart is intended as a baseline that works for most situations 'out of the box', but you're free to edit it in any manner you'd like to fit your specific need.


Data table class method refactoring

Correct DataTable._condition_to_jcolumn and DataTable._dict_to_jmap usage and convert both from @classmethod to @staticmethod
Closes #801

cc @dennyglee

Hi there, could you please provide your email address? We need to use a valid email address in the commit.

I am not sure if I understand the issue @allisonport-db .


[mitmweb] Add hover menu to FlowRow

Description
I added a "quick actions" menu, which appears when hovering each row.
The menu can add an interception filter corresponding to the host and IP address of the flow.
Checklist

[x] I have updated tests where applicable.
[ ] I have added an entry to the CHANGELOG.

I applied your suggested changes.
It seems that your changes affected the test failure.
I don't know how to solve it.