Investigate AWS integration test issues

waiting for privilege escalation prompt
15/16..  Configure Kubernetes DNS
- Running task: verify kubernetes-dns service is running
  ip-10-0-3-225 Timeout (12s) waiting for privilege escalation prompt:          [ERROR]
error installing: error running playbook: error running ansible: exit status 2

• Failure [2451.920 seconds]
Happy Path Installation Tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:194
  Installing with private Docker registry
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:193
    Using a 1/1/1 CentOS 7 layout
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:192
      Using a custom registry provided by the user
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:191
        should result in a working cluster [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

Validating==========================================================================
Reading installation plan file "kismatic-testing.yaml"                          [OK]
Validating installation plan file                                               [OK]
1/2....  Configure Cluster Prerequisites                                        [OK]
2/2....  Run Cluster Pre-Flight Checks                                          [OK]
error running preflight: error running playbook: error running ansible: exit status 2

• Failure [301.722 seconds]
kismatic install validate tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/validate_test.go:38
  Targeting AWS infrastructure
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/validate_test.go:37
    Running validation with package installation disabled
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/validate_test.go:36
      using a Minikube CentOS 7 layout
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/validate_test.go:35
        should succeed if and only if all packages are installed on the node [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

Installed:
  kismatic-docker-engine.x86_64 0:1.11.2-1.el7.centos

Dependency Installed:
  libtool-ltdl.x86_64 0:2.4.2-21.el7_2

Complete!
Connection to <IP_ADDRESS> closed.

STEP: Installing Master:
2016/11/07 19:28:09 failed to install the master over SSH: timed out running commands on nodes
[]

• Failure [629.656 seconds]
Happy Path Installation Tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:194
  Installing with package installation disabled
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:154
    Targeting AWS infrastructure
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:153
      Using a 1/1/1 CentOS 7 layout
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:152
        Should result in a working cluster [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

        failed to install the master over SSH

        /var/snap-ci/src/github.com/apprenda/kismatic/integration/install.go:203

Happy Path Installation Tests Installing with package installation enabled Targeting AWS infrastructure using a 1/1/1 layout with Ubuntu 16.04 LTS
  should result in a working cluster
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

STEP: Provisioning nodes
AWS NODE "i-0e65bac5a83984725" MUST BE CLEANED UP MANUALLY

• Failure [10.245 seconds]
Happy Path Installation Tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:194
  Installing with package installation enabled
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:93
    Targeting AWS infrastructure
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:92
      using a 1/1/1 layout with Ubuntu 16.04 LTS
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:75
        should result in a working cluster [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

        Expected error:
            <*awserr.requestError | 0xc420376690>: {
                awsError: {
                    code: "InvalidInstanceID.NotFound",
                    message: "The instance ID 'i-0e65bac5a83984725' does not exist",
                    errs: nil,
                },
                statusCode: 400,
                requestID: "29729994-4cfb-404a-ba4e-6cc4268f010d",
            }
            InvalidInstanceID.NotFound: The instance ID 'i-0e65bac5a83984725' does not exist
            	status code: 400, request id: 29729994-4cfb-404a-ba4e-6cc4268f010d
        not to have occurred

        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:39

Happy Path Installation Tests Installing with package installation enabled Targeting AWS infrastructure using a 3/2/3 layout with CentOS 7
  should result in a working cluster
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

STEP: Provisioning nodes
..

• Failure [23.342 seconds]
Happy Path Installation Tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:194
  Installing with package installation enabled
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:93
    Targeting AWS infrastructure
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:92
      using a 3/2/3 layout with CentOS 7
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:91
        should result in a working cluster [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

        Expected error:
            <*awserr.requestError | 0xc420323b00>: {
                awsError: {
                    code: "MissingParameter",
                    message: "The request must contain the parameter InstanceId",
                    errs: nil,
                },
                statusCode: 400,
                requestID: "5061efcb-960f-49a3-ba2e-7d865e90ac2d",
            }
            MissingParameter: The request must contain the parameter InstanceId
            	status code: 400, request id: 5061efcb-960f-49a3-ba2e-7d865e90ac2d
        not to have occurred

        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:39

Installing Cluster==================================================================
1/16...  Configure Cluster Prerequisites                                        [OK]
2/16...  Install Kismatic packages
- Running task: install kubernetes worker package
  ip-10-0-3-186 '/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold"     install 'kismatic-kubernetes-node=1.4.5-1'' failed: E: There were unauthenticated packages and -y was used without --allow-unauthenticated
                                                                                [ERROR]
---- STDOUT ----
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  bridge-utils kismatic-docker-engine kismatic-kubernetes-networking libltdl7
  socat
The following NEW packages will be installed:
  bridge-utils kismatic-docker-engine kismatic-kubernetes-networking
  kismatic-kubernetes-node libltdl7 socat
0 upgraded, 6 newly installed, 0 to remove and 97 not upgraded.
Need to get 225 MB of archives.
After this operation, 686 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  kismatic-docker-engine kismatic-kubernetes-networking
  kismatic-kubernetes-node

---- STDERR ----
E: There were unauthenticated packages and -y was used without --allow-unauthenticated

---------------
error installing: error running playbook: error running ansible: exit status 2

• Failure [285.813 seconds]
Happy Path Installation Tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:194
  Installing with package installation enabled
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:93
    Targeting AWS infrastructure
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:92
      using a 1/1/1 layout with Ubuntu 16.04 LTS
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:75
        should result in a working cluster [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

        Expected error:
            <*exec.ExitError | 0xc42037a040>: {
                ProcessState: {
                    pid: 37602,
                    status: 256,
                    rusage: {
                        Utime: {Sec: 23, Usec: 303784},
                        Stime: {Sec: 9, Usec: 703213},
                        Maxrss: 33332,
                        Ixrss: 0,
                        Idrss: 0,
                        Isrss: 0,
                        Minflt: 963379,
                        Majflt: 0,
                        Nswap: 0,
                        Inblock: 0,
                        Oublock: 12552,
                        Msgsnd: 0,
                        Msgrcv: 0,
                        Nsignals: 0,
                        Nvcsw: 1013237,
                        Nivcsw: 1342,
                    },
                },
                Stderr: nil,
            }
            exit status 1
        not to have occurred

        /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:72
------------------------------

13/16..  Install Kubernetes Kubelet on Worker Nodes
- Running task: kubelet : verify kubelet is running
  ip-10-0-3-174                                                                 [ERROR]
---- STDOUT ----
● kubelet.service - Kubernetes Kubelet
   Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Mon 2016-11-07 05:44:26 UTC; 758ms ago
     Docs: https://github.com/GoogleCloudPlatform/kubernetes
  Process: 10988 ExecStart=/usr/bin/kubelet --allow-privileged=true --api-servers=${MASTER_LIST} --cloud-provider= --cluster-dns=${CLUSTER_DNS} --cluster-domain=cluster.local --configure-cbr0=true --container-runtime=docker --docker=unix:///var/run/docker.sock --hostname-override=${HOSTNAME} --kubeconfig=${KUBECONFIG} --pod-infra-container-image=${INFRA_IMG} --register-schedulable=${REGISTER_SCHEDULABLE} --serialize-image-pulls=false --tls-cert-file=${CERT_FILE} --tls-private-key-file=${KEY_FILE} --network-plugin=cni --network-plugin-dir=${NETWORK_PLUGIN_DIR} --v=2 (code=killed, signal=TERM)
 Main PID: 10988 (code=killed, signal=TERM)

Nov 07 05:44:26 ip-10-0-3-174 kubelet[10988]: I1107 05:44:26.220342   10988 kubelet_node_status.go:356] Recording NodeHasSufficientDisk event message for node ip-10-0-3-174
Nov 07 05:44:26 ip-10-0-3-174 kubelet[10988]: I1107 05:44:26.220361   10988 kubelet_node_status.go:356] Recording NodeHasSufficientMemory event message for node ip-10-0-3-174
Nov 07 05:44:26 ip-10-0-3-174 kubelet[10988]: I1107 05:44:26.220393   10988 kubelet_node_status.go:356] Recording NodeHasNoDiskPressure event message for node ip-10-0-3-174
Nov 07 05:44:26 ip-10-0-3-174 kubelet[10988]: I1107 05:44:26.220405   10988 kubelet_node_status.go:73] Attempting to register node ip-10-0-3-174
Nov 07 05:44:26 ip-10-0-3-174 kubelet[10988]: I1107 05:44:26.291343   10988 kubelet_node_status.go:76] Successfully registered node ip-10-0-3-174
Nov 07 05:44:26 ip-10-0-3-174 kubelet[10988]: I1107 05:44:26.322124   10988 kubelet_network.go:306] Setting Pod CIDR:  -> <IP_ADDRESS>/24
Nov 07 05:44:26 ip-10-0-3-174 kubelet[10988]: I1107 05:44:26.484136   10988 container_bridge.go:81] CBR0 doesn't exist, attempting to create it with range: <IP_ADDRESS>/24
Nov 07 05:44:26 ip-10-0-3-174 kubelet[10988]: I1107 05:44:26.515900   10988 manager.go:293] Recovery completed
Nov 07 05:44:26 ip-10-0-3-174 systemd[1]: Stopping Kubernetes Kubelet...
Nov 07 05:44:26 ip-10-0-3-174 systemd[1]: Stopped Kubernetes Kubelet.
---------------
error installing: error running playbook: error running ansible: exit status 1

• Failure [514.386 seconds]
Happy Path Installation Tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:194
  Installing against a minikube layout
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:125
    Targeting AWS infrastructure
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:113
      Using Ubuntu 16.04 LTS
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:112
        should result in a working cluster [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

This looks like a networking/Calico issue with intermittently not working and this was fixed in the newest version.
Running Smoke Test==================================================================
1/2....  Configure Cluster Prerequisites                                        [OK]
2/2....  Smoke test Master Nodes                                                [OK]
3/2....  Smoke test Master Nodes
- Running task: run smoke test checks using Kuberang
  ip-10-0-3-195                                                                 [ERROR]
---- STDOUT ----
Configured kubectl exists                                                       [OK]
Nginx service does not already exist                                            [OK]
BusyBox service does not already exist                                          [OK]
Nginx service does not already exist                                            [OK]
Issued BusyBox start request                                                    [OK]
Issued Nginx start request                                                      [OK]
Both deployments completed successfully within timeout                          [OK]
Issued expose Nginx service request                                             [OK]
Grab nginx pod ip addresses                                                     [OK]
Grab nginx service ip address                                                   [OK]
Grab BusyBox pod name                                                           [OK]
Accessed Nginx service at <IP_ADDRESS> from BusyBox                           [OK]
Accessed Nginx service via DNS kuberang-nginx-1478488562787114955 from BusyBox  [OK]
Accessed Nginx pod at <IP_ADDRESS> from BusyBox                               [OK]
Accessed Nginx pod at <IP_ADDRESS> from BusyBox                                [ERROR]
Accessed Nginx pod at <IP_ADDRESS> from BusyBox                                [ERROR]
Accessed Nginx pod at <IP_ADDRESS> from BusyBox                                  [ERROR]
Accessed Nginx pod at <IP_ADDRESS> from BusyBox                               [ERROR]
Accessed Google.com from BusyBox                                                [ERROR IGNORED]
Accessed Nginx service via DNS kuberang-nginx-1478488562787114955 from this node[ERROR IGNORED]
Accessed Nginx pod at <IP_ADDRESS> from this node                             [ERROR IGNORED]
Accessed Nginx pod at <IP_ADDRESS> from this node                              [ERROR IGNORED]
Accessed Nginx pod at <IP_ADDRESS> from this node                              [ERROR IGNORED]
Accessed Nginx pod at <IP_ADDRESS> from this node                                [ERROR IGNORED]
Accessed Nginx pod at <IP_ADDRESS> from this node                             [ERROR IGNORED]
Accessed Google.com from this node                                              [OK]
Powered down Nginx service                                                      [OK]
Powered down Busybox deployment                                                 [OK]
Powered down Nginx deployment                                                   [OK]
---- STDERR ----
Error running command: One or more required steps failed
---------------
error during smoke test: error running smoketest: error running playbook: error running ansible: exit status 2

• Failure [1186.082 seconds]
Happy Path Installation Tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:194
  Installing with package installation enabled
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:93
    Targeting AWS infrastructure
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:92
      using a 3/2/3 layout with CentOS 7
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/install_test.go:91
        should result in a working cluster [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

S3 repo issue?
STEP: Prepping nodes for the test
<IP_ADDRESS>: Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (35) Encountered end of file
Connection to <IP_ADDRESS> closed.

2016/11/07 01:35:00 Failed to prep repo on the node: error running command on node
[]

• Failure [133.241 seconds]
kismatic install validate tests
/var/snap-ci/src/github.com/apprenda/kismatic/integration/validate_test.go:38
  Targeting AWS infrastructure
  /var/snap-ci/src/github.com/apprenda/kismatic/integration/validate_test.go:37
    Running validation with package installation disabled
    /var/snap-ci/src/github.com/apprenda/kismatic/integration/validate_test.go:36
      using a Minikube CentOS 7 layout
      /var/snap-ci/src/github.com/apprenda/kismatic/integration/validate_test.go:35
        should succeed if and only if all packages are installed on the node [It]
        /var/snap-ci/src/github.com/apprenda/kismatic/integration/framework.go:16

        Failed to prep repo on the node

        /var/snap-ci/src/github.com/apprenda/kismatic/integration/install.go:203

Closed as all issues were addressed.


[UI/UX] Dropdown for language and style.

Describe the issue/behavior that seems buggy

On homepage snippet box ^1, both language and style links should have dropdown. It's not a bug but inconvenient.
Sample Code or Instructions to Reproduce

Visit https://highlightjs.org
Click on either language or style
It change language/style instead of showing dropdown

Expected behavior

It would be great to have a dropdown button for both options.
Additional context

On second thought, adding a dropdown button on the right side of it could also a better option.  I'm interested to contribute.

Please see #3611.  Any feedback on the website should be addressed to the new version, not the old.


Feature request: Add Java highlighting

C++ and Java have much common keywords. Modifying the C++ Highlighter we can build a Java highlighter. C/C++, Java and Python are most commonly used languages and for a code editor to have three support will be good. Currently it highlights C/C++ and Python. Java is the only missing piece.

Any updates @Megaxela ?

Addressed in #38

@ouuan You might need to pull this to your QCodeEditor, It will be good to have Actual Java Syntax highlighting in 6.0 for us.


[1.18, Bug] Teleporting Dragon Eggs can get stuck in the Air

dragon egg issues seem to have to do with the lack of heightmap info


[HW] Vinod Kumar K P

Name: Vinod Kumar K P
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/vinod-kumar-k-p/
Attach the homework screenshots below for both step II and step III:
Step II

Step II

Nice job Vinod, thank you. Here's your badge -> https://api.badgr.io/public/assertions/GzXQEBe2QEuBA0K6z5ZlMw?identity__email=vinodkumar.kp.1985%40gmail.com


The AutocompleteTable disappears when device is Bent (Flipped)

When using autoCompleteTableAppearsAsKeyboardAccessory = true. The autoCompleteView disappears when device is rotated or bent (as in moved or rotated on x-axis or flipped half even way).
The property autoCompleteTableViewHidden = false is still false. So changing the property has no effect.

Pod Version: 'MLPAutoCompleteTextField', '~> 1.5'
Xcode Version: Version 7.3.1 (7D1014)

Solved 👍 Looks like I was using
NSNotificationCenter.defaultCenter().addObserver(self, selector: #selector(ElavatorBankTableViewCell.rotated), name: UIDeviceOrientationDidChangeNotification, object: nil)
When using autoCompleteTableAppearsAsKeyboardAccessory = true I removed the suggested rotation workaround.


Flatcar Grabs 2 ip addresses at boot time

Description
While migrating from CoreOS to Flatcar, we have encountered a bug which during the boot up process grabs at least 2 ip addresses are obtained from the DHCP server, almost always one of the temporary leased ip addresses are used.
Impact
This issue is causing over allocation of ip addresses in the K8S vlans.
Environment and steps to reproduce

Set-up: Flatcar is running on a VM on top of VMware using infoblox as the DNS provider within a VM, also we are using flannel as the network layer.
Task:  In order to reproduce the issue, we would need to have a similar environment.
Action(s):  Setup nodes in VMware
a.  Use Flatcar VMs, it is relevant to mention that we are using client identifier for the  ens192 interface.

[Match]
Name=en*
[Network]
DHCP=yes
LinkLocalAddressing=no
IPv6AcceptRA=no
[DHCP]
UseMTU=true
UseDomains=true
ClientIdentifier=mac
b.  Login to the node, and by using journalctl search for the interface ens192.
c.  In our environment appears in several nodes three different ips.

Error:

Jun 29 18:00:47 localhost systemd-networkd[648]: ens192: DHCPv4 address XX.YYY.ZZ.AA/24 via XX.YYY.>
Jun 29 18:00:47 localhost systemd-networkd-wait-online[659]: ignoring: lo
Jun 29 18:00:47 localhost systemd-networkd-wait-online[659]: ignoring: lo
Jun 29 18:00:47 localhost systemd-networkd[648]: ens192: Configured
Jun 29 18:02:40 localhost ntpd[727]: Listen normally on 3 ens192 XX.YYY.ZZ.AA:123
Jun 29 18:02:40 localhost ntpd[727]: 29 Jun 18:02:40 ntpd[727]: Listen normally on 3 ens192 XX.YYY.>
Jun 29 18:02:40 localhost ntpd[727]: Listen normally on 4 lo [::1]:123
Jun 29 18:02:40 localhost ntpd[727]: 29 Jun 18:02:40 ntpd[727]: Listen normally on 4 lo [::1]:123
Jun 29 18:02:40 localhost ntpd[727]: 29 Jun 18:02:40 ntpd[727]: Listening on routing socket on fd #>
Jun 29 18:02:40 localhost ntpd[727]: Listening on routing socket on fd #21 for interface updates
Jun 29 21:47:43 localhost systemd-networkd[658]: ens192: DHCPv4 address XX.YYY.ZZ.AA/24 via XX.YYY.>
Jun 29 21:47:43 localhost systemd-networkd-wait-online[682]: ignoring: lo
Jun 29 21:47:43 localhost systemd-networkd[658]: ens192: Configured
Expected behavior
This should be something I would expect:
Jun 29 21:47:43 localhost systemd-networkd[658]: ens192: DHCPv4 address  XX.YYY.ZZ.AA/24 via XX.YYY.>
Jun 29 21:47:43 localhost systemd-networkd[658]: ens192: Configured
Additional information
The idea here would be to let the machine only grab a single IP while booting up, initially we thought we had a pre-ignition issue, but after looking at the logs it appears that it is part of the OS/Kernel services. It can be potentially related to https://github.com/coreos/fedora-coreos-config/issues/58. Also, here is more documentation in regards to VMware and flatcar https://docs.flatcar-linux.org/os/booting-on-vmware/.

Hi!
Thanks for your report.  Unfortunately the problem you're reporting is not clear from the redacted logs. The logs you showed, show a 3.5 hour gap between one DHCP message and the other and because of the redacted IPs I don't know if this was the same IP or a different one. This looks like a normal DHCP renewal to me and it's definitely not "grabbing 2 IP addresses at boot time"
The lines in the middle are about NTP, not DHCP and they also don't look like it's about grabbing two IPs, but rather just listening on the ens192 interface as well as the localhost one.
Maybe you can try to paste logs that are a little bit less redacted so that we can actually understand the problem? Thanks!

Hi,
The best way to replicate this issue would be to download the actual image https://stable.release.flatcar-linux.net/amd64-usr/current/flatcar_production_vmware_ova.ova, once the instance is up try searching for DHCPv4. In our environment this becomes a big deal since we have a limited set of ip addresses  in a given vlan, imagine having 200+ pods registering those ip addresses leased with DNS, it makes the cleanup process extremely tedious.
If you should need further information, please let me know

Hello,
we would like to but that means to set up the DHCP server software you used but by default VMware uses static IP addresses which we also do in our test instance.
If you have this problem at the first boot, you should know that the networkd default for ClientIdentifier is duid which will be used in the initramfs. Your network config is applied for the real system, not the initramfs, which may cause the DHCP server to give a new IP address to the real system because you set mac as ClientIdentifier.
https://www.freedesktop.org/software/systemd/man/systemd.network.html#ClientIdentifier=
But I still don't understand why this would be a problem in your case because the first IP address should marked as free if the initramfs networkd stops (SendRelease is on by default).
https://www.freedesktop.org/software/systemd/man/systemd.network.html#SendRelease=
Without proper logs we don't know when this all happens and if it is related to the initramfs or not.

Hello Pothos,
I have tried adding in ignition Clientidentifier=duid, and we are still getting the same issue dual ip address, please find the logs below related to IP:
Jul 06 18:28:59 localhost systemd-networkd[293]: ens192: DHCPv4 address <IP_ADDRESS>/24 via <IP_ADDRESS>
Jul 06 18:29:10 localhost systemd-networkd[293]: ens192: DHCP lease lost
Jul 06 18:29:10 localhost systemd[1]: systemd-networkd.service: Succeeded.
Jul 06 18:29:10 localhost systemd[1]: Stopped Network Service.
Jul 06 18:29:20 dev-mike-etcd-lx03.amdc.mckinsey.com systemd-networkd[752]: ens192: DHCPv4 address <IP_ADDRESS>/24 via <IP_ADDRESS>
Jul 06 18:29:20 dev-mike-etcd-lx03.amdc.mckinsey.com systemd-networkd[752]: ens192: Configured
This causes lots of issues, since every time an IP is issued by the DHCP server it will automatically register with the DNS server, and once the ip is lost, the record will remain on the DNS server. Hopefully the issue would be clear now.

Looks like the first entries are in the initramfs. This is only on first boot, right? Then we know that the initramfs gets a different IP address.
DHCP lease lost seems to indicate that the DHCP server gets to know that the address is free - but it can't delete your DNS entries and that's causing the problem for you? Would be good to know why the DHCP server gives a new IP address out (maybe you could inspect the logs there or sniff the network traffic).
Does it also happen when you don't specify Clientidentifier=?

Based on my environment, I do not believe I can make changes on the DHCP/DNS server. This is something, we would need to co-exist. Thank you for your input.


Decode mappings

There's some issue with bundle. Don't have ideas yet how to fix.

Addressed the same need with https://github.com/Rich-Harris/magic-string/pull/134


Add functional test runs to the CI builds

We should run the functional tests in the CI builds to prevent test regressions.

Functional tests are running as part of all builds.


Firebase Analytics: Send app settings info so that we can understand what kind of bg scanning settings users use, for example

fixed in 1.4.5


Add batched migration script

Changes
Add batched migration script

@Arkatufus needs a rebase

Rebased to recent dev in #168


Minor syntax/dependency changes

-added missing 'end' in pointsify
-fixed keyword argument syntax errors in optimal_periods, periodogram, and flatten
-added export pointsify, flatten, scrambled_periodogram, movingstd
-added using Optim

What version of Julia are you using?  That should be the correct syntax for default values.  E.g. optimal_periods (which should probably be named something else, maybe loguniform_grid), can be called as
optimal_periods()
optimal_periods(5)
optimal_periods(5, 50)
optimal_periods(5, 50, n=6)
optimal_periods(n=6)

but not as
optimal_periods(pmin=5)

because that isn't a keyword argument.
Anyway, this isn't a huge deal, since the keyword syntax is also fine, but I think for some methods the default value syntax is cleaner.
What do you think?  You probably have more insight than me into what is confusing, since I wrote the code.

I'm on Julia 0.6.4.
My bad, I thought it was keyword argument syntax because in the sample code given the readme it was called like optimal_periods(pmin=0.25, pmax=50). Yeah, I agree that it's clearer with the default value syntax

Just fixed the README.  Thanks.

Did you introduce a typo at the end of pointsify?
end -> endop
?

Yeah my bad lol I fixed it in the next commit


Help ! ArticleList onPress to Good Article

Hi,
I would like to navigate on the article pressed in a article list.
However, in : containers/layouts/articles/articleList1/articleList1.container.tsx
this.props.navigation.navigate('Article 1'); ------> go always to Article 0
Because, in : containers/layouts/articles/article1/article1.container.tsx
public state: State = {
article: articles[0],
};
So, to to pass or bind the good article ?
Thx for your help ...
Regards,

This is not a framework issue, but it's more related to Kitten Tricks application
You should learn more about passing parameters to a route.


Merge master branch to prTesting1_202011041917 branch

Docs Build status updates of commit 9898729:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Revert "Remove package:image dependency"

Reverts flutter/flutter#115674
I forgot to remove the ci.yaml targets.

All pre-submits green except luci-flutter, not sure why autosubmit didn't merge it, so manually merging to fix the tree


GC: Backup: OneDrive: Drives M365 Object encapsulation not used when retrieving data

At this time, Drive folders are not saved within Corso. Therefore, certain information such as whether or not the drive is Shared is not saved. This information changes how items within these types of directories can/should be restored.

@dadams39 - we will have a placeholder for metadata for DriveItems with the work @meain is doing for persisting permission metadata. Let's look into that.
Removing tech-debt label - let's track this as part of feature work where it's needed.


Remove shadow from theme selector box

The reason is explained here.

Done, I update the last release because the changes are minor


How to include this class as standalone?

Just for testing purposes and benchmarks I'd like to include this class into a project.
How to do that without composer? Thanks.

Hi,
To include any project without composer you need to require/load all
project files/classes manualy.
Why wouldn not you use composer? It will do it for you automatically, and
it is very easy to use and learn.
Best,
Muhammed
On Sat, May 26, 2018 at 10:42 AM rotate4all<EMAIL_ADDRESS>wrote:

Just for testing purposes and benchmarks I'd like to include this class
into a project.
How to do that without composer? Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mmamedov/page-cache/issues/17, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADnp5dZ_Zsa5f0O1BXrkI-2tOXtu2DPGks5t2RV6gaJpZM4UO1iG
.

"file could not be downloaded: allow_url_fopen must be enabled in php.ini "... that's why.

You are having troubles installing composer?
Google it up to solve, you can pass arguments to php cli via -d flag, to
enable allow_.. flag to install composer.
On Sun, May 27, 2018 at 9:10 PM rotate4all<EMAIL_ADDRESS>wrote:

"file could not be downloaded: allow_url_fopen must be enabled in php.ini
"... that's why.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mmamedov/page-cache/issues/17#issuecomment-392357665,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADnp5aqeOqdRyl88Oxs0t5TjZ4bF_HJ-ks5t2voQgaJpZM4UO1iG
.


Poetry export should use per-package --index-url instead of single --extra-index-url

[x] I am on the latest Poetry version.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: macOS Mojave 10.14.6
Poetry version: 1.1.3 with python-poetry/poetry#3251 fix

Issue

This issue is a follow-up to the problem identified in python-poetry/poetry#3238:

But... there's one more thing. I've also run:
poetry@3251 export -f requirements.txt -o requirements.txt --without-hashes --with-credentials
and the first line of the output file is:
--extra-index-url http://repository.intranet.foobar.com/artifactory/api/pypi/pypi-virtual/simple
When using default = true we get then:
--index-url http://repository.intranet.foobar.com/artifactory/api/pypi/pypi-virtual/simple
At first sight it seems okay, but we have to remember about the issue with pip and --extra-index-url:
https://pydist.com/blog/extra-index-url
https://github.com/pypa/pip/issues/5045
I assume it's already handled by Poetry itself, but to make it error-prone when exporting the requirements.txt file imho we should also keep the approach of specifying individual index per each package, e.g.:
--index-url http://repository.intranet.foobar.com/artifactory/api/pypi/pypi-virtual/simple anyconfig==0.9.11
PS Of course there should be also --trusted-host flag in any of these scenarios due to http, but there was another PR for that, afair - already merged, just not released yet.

@abn has already confirmed the validity of the issue, but also provided one concern:

@jaklan appreciate the input on that. I'd suggest we raise that as a new issue. I agree that a per package index is better for the extra-index case. One worry, however, is that people seem to be attached to the current export format because some do text processing of the output it for various reasons.

So we also have to consider how to introduce such a change not to break any existing workflows.

It seems that settings from pyproject.toml aren't getting pulled into requirements.txt either.
[[tool.poetry.source]]
name = "myprivate"
url = "https://myprivate/simple/"
default = true

[[tool.poetry.source]]
name = "default"
url = "https://pypi.org/simple"
secondary = true

Should create a requirements.txt with
--index-url https://myprivate/simple
--extra-index-url https://pypi.org/simple

Closing as wontfix given that this is a limitation of the format and not up to Poetry. @henrytseng's issue is different and already fixed.


See if PugiXML's XPath support can be used to implement identity constraints

PugiXML supports a subset of XPath 1.0.
XSD 1.0 has very useful identity constraint tags which work with XPath 1.0. Look if they are compatible and if so, cobble together at least some form of support for <xs:key>, <xs:keyref> and <xs:unique>.

I would say this is a "nice to have". Lets get everything else working first.


Same issue as #1699 but i am using latest whatsapp-js version  (v3.0.0) but it' not working at all.

Code injected successfully and also WPP variable is their but when i call any function from injected  file its throwing error
Environment

Web WhatsApp version: 2.3000.1012082673 (joined beta)
WA-JS version(s): 3.0.0
Browser: Chrome 122.0.6261.113 (Official Build) (64-bit)
OS: Windows

same

my WhatsApp version is 2.3000, but in WhatsApp 2.24 version, there is no errors at all

The same issue has been encountered by me as well, and I would appreciate your assistance in resolving it.

I've encountered the same issue, do you have any solutions?

I've encountered the same issue as well. I'm unsure of the current progress made by the developers or if there's any iteration plan in place.

Last week I also encountered a similar issue , do you have any effective solutions?

Guys, could you check the value of WPP.isInjected and WPP.isReady?
The error 'reading m' is caused by to try running some code before the injection

Guys, could you check the value of WPP.isInjected and WPP.isReady?
The error 'reading m' is caused by to try running some code before the injection

This problem is currently an occasional problem on my plugin, and it is true that WPP.isReady and WPP.isInjected are false when there is an error, it is normal to refresh the page multiple times, but this is only in WhatsApp version 2.30, I tried repeatedly on version 2.24 of WhatsApp, and the same set of code will not have similar errors

Guys, could you check the value of WPP.isInjected and WPP.isReady?
The error 'reading m' is caused by to try running some code before the injection

This problem is currently an occasional problem on my plugin, and it is true that WPP.isReady and WPP.isInjected are false when there is an error, it is normal to refresh the page multiple times, but this is only in WhatsApp version 2.30, I tried repeatedly on version 2.24 of WhatsApp, and the same set of code not have similar errors

How can u roll back to WhatsApp version 2.24? Or it can't?

Guys, could you check the value of WPP.isInjected and WPP.isReady?
The error 'reading m' is caused by to try running some code before the injection

This problem is currently an occasional problem on my plugin, and it is true that WPP.isReady and WPP.isInjected are false when there is an error, it is normal to refresh the page multiple times, but this is only in WhatsApp version 2.30, I tried repeatedly on version 2.24 of WhatsApp, and the same set of code not have similar errors

How can u roll back to WhatsApp version 2.24? Or it can't?

Whatsapp version cannot be rolled back. The phenomenon I have here is that some devices have not been updated, so they are version 2.24. As mentioned above, I also have problems with some accounts in the same 2.30 version. Not all 2.30 versions have problems, but 2.24 There were no problems overall.

Guys, could you check the value of WPP.isInjected and WPP.isReady?
The error 'reading m' is caused by to try running some code before the injection

when WPP.isInjected is false, how can i reload WPP util WPP.isInjected is true

I've encountered the same issue as well. I'm unsure of the current progress made by the developers or if there's any iteration plan in place.

What's the way you're injecting? Playwright or extension?
Could you provide the code you use for injection to be able to replicate the errors here and solve this?

What's the way you're injecting? Playwright or extension? Could you provide the code you use for injection to be able to replicate the errors here and solve this?

I also encountered this problem.
I tested manually injecting the wajs code in chrome console, the steps are:

Login Whatsapp scanning QR code (whatsapp version > 2.3000)  (incognito mode, without other extensions)
Copy&Past wajs in console

WPP.isInjected return False
It seems that the script wrongly set WPP.webpack.loaderType = "webpack" (webpackChunkwhatsapp_web_client)  instead of  new "meta"

Hi, please test https://github.com/wppconnect-team/wa-js/pulls

I will mark this issue as resolved, as I have already received feedback on other issues. Please reopen it if it has not been resolved.


Twitter logo in docs should not be colored

Twitter is the only colored icon on our docs website:

It should be gray like all the other icons.

This is inherited from the website theme. In the latest version of the theme the twitter icon color goes away (but that's actually a bug in the theme due to changing the icon from the "square" version to just the bird, but not changing the associated CSS selector). The theme also defines brand-appropriate colors for GitLab and Bitbucket. Github is grey because that's their brand.
In our MNE-Python CSS, we actually define colors for the discord icon:
https://github.com/mne-tools/mne-python/blob/b1329c3ae59d0da3646b0c667441e12ee0f7bd8d/doc/_static/style.css#L9
as well as light and dark variant colors for discourse, github, and mastadon icons, e.g.:
https://github.com/mne-tools/mne-python/blob/b1329c3ae59d0da3646b0c667441e12ee0f7bd8d/doc/_static/style.css#L46-L48
but for some reason they aren't getting used, so that's also a bug.
Finally, one might argue we should change the twitter logo to an X logo (but that should probably happen at the theme level).
With all that said: do you still think they should be all grey, or should we try to fix the broken color display of the other icons?

Thanks for investigating @drammock! Either way is fine with me, although I have a slight preference for using color.


Release nodejs-googleapis-common v0.2.1

This pull request was generated using releasetool.

Release is at https://github.com/googleapis/nodejs-googleapis-common/releases/tag/v0.2.1


Test with Go 1.20, use revive

Switch from golint to revive,
and test against Go 1.19 and 1.20.

Current dependencies on/for this PR:

main

PR #20   👈

This comment was auto-generated by Graphite.


add export for useSWR hook

Hi!
In my opinion, it's a good practice not to use default exports.
In that case, I wondered if it would be a good idea to add a separated export for useSWR.
With this code, It is going to be possible to use separated export in our applications (better auto import and cleaner syntax):
import { useSWR } from "swr";

Sounds like a nice thing to have to me! Only concern is should we allow both at the same time? Does that confuse people?

Having both is acceptable to avoid a breaking change.

Having both is acceptable to avoid a breaking change.

Once either of me needs to be removed that gonna be a breaking change 😂

You can find most of use cases here:
Avoid Export Default
Avoid ES6 default exports
Google Developer Guides
I would like to add some more:

The most of big tech companies have enabled eslint rule -import/no-default-export
Destructuring assignment is a huge trend in the world of React and Typescript these days, which goes with named exports due to similar syntax.
It looks wierd when all your code is imported in curly brackets and one library doesn't in production code.

In the most of big tech companies, they have enabled eslint rule - import/no-default-export
I don't feel like because of the existence of this eslint rule so that we should give up the convenient feature of this language. And there're tons of libraries providing default export, if everybody enables this rule then the code will become a disaster with handling eslint rules. I also can't be confident saying that most of companies have already started using it.

we didn't receive many issues reporting that they're having issues with default import, most of work are handled by bundler and framework, so that users don't need to worry about the imports.
Introducing this also will confuse users that there're 2 exports for 1 hook, and we don't have a strong reason to deprecate the exisiting one. Users will still complain that why I can't directly import it or why the name is useSWR but not useSwr.
IMO those kinds of eslint rules are bit helpful when learn js with unawaring of more specific languages charateristics, but it shouldn't become a blocker of using basic language features. I'd prefer to keep as it is right now to avoid more changes driven by eslint rules personally.

IMHO, besides ESLint rules, there are a few more reasons why named imports/ exports are practically more useful thus becomes more preferred for many of us which also explains why ESLint rule recommends avoid default exports. While default exports are part of the JS features, this leads to a few concerns I have from time to time and at some point I do think they slowly evolved to actual problems during development regardless of whether or not you are using bundlers:

VSCode does not support importing default exports (not sure about other IDE but VSCode does not support that by default. CMIIW).
As a user who relies on auto import feature by just typing the name of a variable, type, or function I want, VSCode will automatically detect and auto-suggest me a list of modules that could match. This is useful because I don't have to type the full path myself.
Even if VSCode or some IDEs support importing default exports, exporting a number of default exports without its own unique name in a project causes confusion to the users.
When every export is a default export without its own name when it should, you are basically seeing a list of defaults from the auto-suggestion from code editors and you will have no idea which one is which unless you look at the full path which works but still annoying.
It does not support re-exports well
Re-exports using index.ts is quite a common pattern while this does not seem to be an issue in swr. Re-exports a list of modules with each containing only its own default export is problematic, e.g.// This works too.
export { default as useSwr } from 'swr';
export { default as useSwrMutation } from 'swr/mutation';

// This works but looks more aesthetically elegant
export { useSwr } from 'swr';
export { useSwrMutation } from 'swr/mutation';

// Default exports is problematic when re-exports with types.
import useSwr from 'swr';
import useSwrMutation from 'swr/mutation';

export type { Arguments, BareFetch } from 'swr';
export { useSwr, useSwrMutation };

// Named exports makes things much easier and
// it does help ensure all your exports are uniquely named within a project,
// e.g. no more than 1 useSwr, or co-existent useSwr or useSWR.
// Also, auto imports works without issues!
export * from 'swr';

Again, please take these with a grain of salt as default imports/ exports might not be an issue within vercel and that's totally fine. One thing to take away is that swr is a public project and hope that one day you will find named imports/ exports a more DX friendly option. Have a good one.

+1 for this, can be workaround for https://github.com/vercel/swr/issues/2208

Is there any update?
Renaming _default in core/dist/index.d.ts in published swr package to useSWR will improve VSCode support. Could you consider about this workaround if there is no plan to merge this pr?


Rename TestRunner to TestScheduler

Summary
I'm refactoring some bits and pieces in the TestRunner and it makes more sense going forward to rename it to TestScheduler. It doesn't actually run the tests, it just tells other parts of Jests which ones to run, in which order and how (in-band or parallel).
Test plan
jest

fyi I kept types/TestRunner the same because I'll be adding more types there and it'll make sense going forward.

this class currently

Creates and manages aggregatedResult
Sets up all the reporting and manages reporter events by passing them to the correct reporte API metods
Manages snapshot state
Exits the process in case of test failures
Formats errors and throws errors based on test runtime result
Cancels the run in watch mode

I think if we leave it as is and call it Scheduler, it might become confusing.

Codecov Report

Merging #4218 into master will not change coverage.
The diff coverage is 25%.

@@           Coverage Diff           @@
##           master    #4218   +/-   ##
=======================================
  Coverage   60.13%   60.13%
=======================================
  Files         191      191
  Lines        6756     6756
  Branches        6        6
=======================================
  Hits         4063     4063
  Misses       2690     2690
  Partials        3        3

Impacted Files
Coverage Δ

packages/jest-cli/src/run_jest.js
0% <0%> (ø)
:arrow_up:

packages/jest-cli/src/jest.js
0% <0%> (ø)
:arrow_up:

packages/jest-cli/src/test_scheduler.js
28.46% <100%> (ø)

Continue to review full report at Codecov.

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


CELEBORN-1354 Followup: split rpc_app into rpc_app_lifecyclemanager and rpc_app_client

What changes were proposed in this pull request?
Based on review feedback here, split rpc_app module into two internal transport modules - rpc_app_lifecyclemanager and rpc_app_client.
These are not directly configured by users - but internally allow us to differentiate between lifecycle manager and executor
Why are the changes needed?
auto ssl is to be configured only at lifecycle manager - doing it at executors is beneign, but not very useful (it results in creation of local files, etc).
Avoid this by handling it specifically only for lifecyclemanager.
This is based on review feedback.
Does this PR introduce any user-facing change?
No, the modules are all internal and not user visible.
How was this patch tested?
Unit tests were updated

+CC @waitinfuture

Codecov Report
Attention: Patch coverage is 77.77778% with 10 lines in your changes are missing coverage. Please review.

Project coverage is 40.68%. Comparing base (121395f) to head (1350264).
Report is 8 commits behind head on main.

Files
Patch %
Lines

...cala/org/apache/celeborn/common/CelebornConf.scala
68.43%
4 Missing and 2 partials :warning:

.../scala/org/apache/celeborn/common/util/Utils.scala
66.67%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2471      +/-   ##
==========================================
+ Coverage   40.17%   40.68%   +0.51%
==========================================
  Files         218      219       +1
  Lines       13742    13903     +161
  Branches     1214     1235      +21
==========================================
+ Hits         5520     5655     +135
- Misses       7905     7922      +17
- Partials      317      326       +9

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

Thanks for the reviews @SteNicholas, @waitinfuture !


[Feature Request]: Sponsors Section

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Add a new "Sponsors" section to the website/application to acknowledge and thank sponsors who contribute to the project. This section will help showcase the support the project receives from individuals and organizations.
Use Case
As a user of the website/application, I want to see a dedicated "Sponsors" section so that I can recognize and appreciate the organizations and individuals who support the project.
Benefits
Recognize and thank sponsors for their support.
Encourage more sponsorships by showcasing current sponsors.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@PSS2134  please assign me this feature
Thank you!

What sponsors will you be adding @Sharmaji513

we can consider reaching out to brands similar to those we had last year, as shown in the attached image. This includes companies like Quine, Vercel, Taskade, .xyz, and BlueLearn. The image highlights our previous sponsors and hiring partners, which we can use as a reference for potential new sponsors.

But we dont have sponsors for careerZunction @Sharmaji513


CIOEC GCcode presentation

Related to #289

Can you also use your Jekyll magic to change _includes/listPresentations.md?
It currently has hardcoded only the mandate.md one

Right, that is hardcoded.  Let's create an issue to see if we can list them using Jekyll.  I think I tried and it was easier to hardcode, but we should look again

@remyb2canada j'ai ajouté la boucle qui affichera les présentations avec Jekyll :smile:

Closes #345


[test] Add DV component for AES masking off test, add it to the testplan

This PR adds the AES masking off test to the testplan. As the masking itself is transparent to software, a DV component is added to probe into AES and verify that 1) all prerequisites are met to switch off the masking and 2) that the second share of the state as well as mask input and output of SubBytes are all zero, i.e., masking is indeed switched off.
This is related to lowRISC/OpenTitan#14240.

Note that for this test to actually compile and work, #15641 first needs to be merged.

Thanks @engdoreis and @andreaskurth for your reviews! I've fixed the typo in the comment and repushed. I am merging immediately as CI passed already before to move forward.


Adds a mask slot and moves adminPDA to new ID slot for aghost

About the PR

adds mask slot to aghost
removes Admin PDA from aghost backpack, and puts it in a newly added ID slot for aghost

Why / Balance
Multiple admins have wished for a mask slot since the hat slot update, and having the PDA outside the backpack, readily available, is much nicer and more efficient for admins.

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
Should be none. As the concerns expressed with the previous closed aghost PR, nothing extra is added into the backpack, and there should be no problems in relation to the concern of mapping. We already have a hat slot, so a mask slot shouldn't break anything.
Changelog
:cl: Sphiral
ADMIN:

tweak: Took the AdminPDA from the backpack and gave it it's own slot on aghosts!


Change arrow of selectMenu component

Description
Good morning team,
I would like change icon arrow defualt of component selectMenu to a custom
Example:
I want change icon default for icon orange

which is CSS of component selectMenu i should change?
Thanks!

You can achieve this through the ui prop: <USelectMenu :ui="{ icon: { base: 'text-orange-500 dark:text-orange-400' } }" /> or by using the #trailing slot:
<USelectMenu>
  <template #trailing>
    <UIcon name="i-heroicons-chevron-down-20-solid" class="w-5 h-5 text-orange-500 dark:text-orange-400" />
  </template>
</USelectMenu>


Add optional access to PSR-3 logger in strategies

what are you looking for for this ticket? just getters and setters for a property?

Already implemented for next major, hopefully release in the next couple of weeks
Sent from ProtonMail Mobile
On Thu, Feb 20, 2020 at 13:56, Derek Stephen McLean<EMAIL_ADDRESS>wrote:

what are you looking for for this ticket? just getters and setters for a property?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Looking forward to it! Will the next major have many BC breaks, or be fairly trivial to upgrade?

Minimal breaks, but there are a couple, it’s not a rewrite in any way though so should be a trivial upgrade
Sent from ProtonMail Mobile
On Thu, Feb 20, 2020 at 13:59, Derek Stephen McLean<EMAIL_ADDRESS>wrote:

Looking forward to it! Will the next major have many BC breaks, or be fairly trivial to upgrade?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


keyword collisions in Python 3 (3.5+)

Describe the bug
amuse/rfi/core.py line 126 defines an "async" function. In Python 3.5+, async is a reserved keyword (https://www.python.org/dev/peps/pep-0492/). We may need to rename this function to prevent "invalid syntax" errors.

I don't think its a big problem since the async are class methods??
(there are other collisions in the code..)

we can maybe gather those here?

we can maybe gather those here?

good idea. I'll rename the issue.

new option for async as keyword argument to function calls (#339 )

ok, asyncawait was introduced in 3.5 and 3.6 but 3.7 makes it reserved..so will change

After discussing with Inti, I like the following:

change the async function keyword to return_request
change the .async() method to .asynchronous()
encourage use of the function argument over the method since this allows wrapping the interface function

sounds good to me.

async is fixed (4b48747)


Add public_annotations group on package installation

public_annotation group should be present in db when users migrate.

Implemented using migrations.

Implemented in this commit


etcdserver: use Counter for proposals_failed_total

It only ever goes up.
https://github.com/coreos/etcd/pull/6112#discussion_r73725578

lgtm


Fix returning argument types from methods.

A tiny fix: method_copyArgumentType() didn't account for the fact that the return type is the first element in the method signature.

Does method_getArgumentType need the same fix?

It did indeed.

And please can we have a test case?

Included now.

Good idea, thanks. Fixed now.


HDDS-11329. Update Ozone images to Rocky Linux-based runner

What changes were proposed in this pull request?
Use new, Rocky Linux-based image for existing Ozone releases.  These are currently published with new tags, e.g. apache/ozone:1.4.0-rocky, to avoid disruption to existing users due to different OS.
How was this patch tested?
CI:
https://github.com/adoroszlai/ozone/actions/runs/11071010566

Thanks @smengcl for the review.


Convert non-UTF8 encodings to UTF8

Loading v2script files currently does not convert the encoding to a common standard encoding which can display weird on some systems. It is necessary that v2script files produce a standard encoding so the file loading pipeline will produce consistent results, and alongside this we must support encodings like ASCII, Windows-1252, Windows-1251, and UTF8, so it makes the most sense then to convert non-UTF8 encodings to UTF8, which means we need to detect each particular encoding and then provide a kind of conversion database to UTF8, since for now we only plan to support Windows-1252 and Windows-1251 of the non-UTF8 compatible encodings, it is likely easier and cheaper for us to manage conversion on our own instead of seeking for a third-party library, however if the expectation is to support many more encodings instead of flatly rejecting them on detection, then it may become necessary to pull more from hsivonen/chardetng instead. will become necessary instead to integrate unicode/icu. (See icu4c)
See

#40
#41
#42

With a reduced C++ version hsivonen/chardetng implemented for #46, some encodings require more complex conversion strategies then simple character replacement, our current conversion implementation is wholly incapable of any Chinese or Japanese character conversions, (or similar encodings) thankfully these encodings seem to be unexpected and unlikely to work for Victoria 2 regardless so chances of such are functionally impossible. For other alphabetic encodings are still trivial to detect and convert based on hsivonen/chardetng but the chance we'll need more is generally considered low in priority as it is itself unlikely for Openvic to need to support any other encodings.


Config shouln't be case sensitive

My yaml file contains the following:
issue-labels-include:
- Breaking change
- Bug
- New Feature

but my GitHub labels are lower case. For instance: "new feature", "bug", etc.
As a result of this case sensitivity issue, GitReleaseManager will generate release notes like this instead of the expected notes that should look like this.

@gep13 looks like there's already an issue for this.

Related issue #92

@mrahhal thanks for the heads up.

@gep13  I also think that the produced text should be auto capitalized in all cases (so that we don't have to needlessly specify label aliases).

@mrahhal once this issue is resolved, Label Aliases shouldn't be required at all.  It would take what is in the yml file as the header.

Yup, I've come to that conclusion directly after I hit comment. Nice!

@Jericho I am not sure if this is still an issue or not, but going to add it to the upcoming release to verify if this is still a problem or not, and if so, get it fixed.

I have verified that this is no longer a problem.  Everything is now case insensitive.


Non-validating peer shows many "not enough seals to seal block" messages during sync

Non-validating peer shows many "not enough seals to seal block" messages during sync
Description
After migrating to v0.6.0, we've observed  there to be many of the following WARN messages:
Nov 30 23:23:58 ip-172-31-41-130 main[758992]: 2022-11-30T23:23:58.963Z [WARN]  polygon.syncer: failed to complete bulk sync with peer, try to next one: peer ID=error 16Uiu2HAmJUVAsjJwd6ah9JC1xHtwKREwzQHmQMLpoi6pdd4pf5bF="unable to verify block, failed to verify the header: not enough seals to seal block"

Your environment

OS and version. Ubuntu 20
The version of the Polygon Edge.   v0.6.0
The branch that causes this issue. develop
Locally or Cloud hosted (which provider). AWS ec2

Steps to reproduce

Spin up chain with 6 validators and 1 non-validator peer
Observe that although the peer syncs to the current block, we see many instances of WARN messages:

unable to verify block, failed to verify the header: not enough seals to seal block"

Expected behavior
I expect non-validating peers to behave as they did prior to v0.6.0.

Hi @dankostiuk
Can you confirm from which version and branch did you upgrade from?
Also, can you provide me with the debug logs as well in order to check them completely.

Hey @dankostiuk did you switch to BLS after upgrading to v0.6.0?

We kept the genesis.json the same, so using ECDSA as I believe that is the default.
Update - I took a backup of a validator's data-dir and restored directly onto the non-validating peer and the issue seemed to go away. I am no longer seeing the not enough seals to seal block either. It seems the non-validating peer's snapshot assumed there to be 9 validators total, so it's own snapshot was not updated for some reason. For now things to be working fine though so feel free to close this. Thanks @laviniat1996 .


Configuration Simplified

Version 2 of old PR #9
The configuration for webapp, store, harvest agent h3 and h1 has been heavily simplified.

wct-webapp, wct-das, wct-agent properties files removed
application-local.properties removed for agents and store
application-local+.properties now only has db settings
all other settings now in application.properties
spring profile overrides still work as normal.

You will need to check property names in any application-local profiles you are using, as they might not match naming in application.properties. @hannakoppelaar found this in old PR with fileArchive.archiveRepository in Store.

Made in error, will recreate


Example app notification with custom sound does not work with android API 29

Tested the example app on emulator with android API 29 and the custom sound did not work.

For Android 8+ the sound are defined by channels and can only be set once. What you can try is to do no set any sound on channel and set it later by custom sound.

Same issue. Custom sound is working fine on ios but not in android. Already setting the custom sound in create notification method.

Also notification buttons do not work on android 12, I have not tested this thoroughly though, because I stopped using this plugin.

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!


Bug: sftp does not work

I have a ubuntu server. In other apps sftp with him works perfectly. But in acode i get this error while opening folder:

Device: Redmi 10
Android: 11
Acode version: 1.10.3 (950)

Update your app


Dataset Invalidations not propagated to files

While analyzing Rucio and DBS inconsistencies, the DM team discovered many valid files whose datasets were declared as invalid or access type deleted.
Is there any reason for this behavior?
Some examples are
+-------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------+---------------+------------------+------------------------+
|f_logical_file_name                                                                                |d_dataset                                                                                |f_is_file_valid|d_is_dataset_valid|d_dataset_access_type_id|
+-------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------+---------------+------------------+------------------------+
|/store/mc/2007/10/9/CSA07-rs1gg_750GeV_c01-2840/0006/CAF9ADDB-0C8B-DC11-9D12-0019B9E4F84F.root                                                         |/rs1gg_750GeV_c01/CMSSW_1_6_0-CSA07-2840/GEN-SIM-DIGI-RAW                                  |1              |1                 |81
|/store/mc/GEM2019Upg14DR/DYToTauTau_M-20_TuneZ2star_14TeV-pythia6-tauola/GEN-SIM-RECO/Age500CaloPU50_U19_500FB_V1A-v1/60000/D8731F82-1F48-E511-884C-0025B3E05D50.root|/DYToTauTau_M-20_TuneZ2star_14TeV-pythia6-tauola/GEM2019Upg14DR-Age500CaloPU50_U19_500FB_V1A-v1/GEN-SIM-RECO|1              |0                 |2                       |
|/store/mc/GEM2019Upg14DR/DYToTauTau_M-20_TuneZ2star_14TeV-pythia6-tauola/GEN-SIM-RECO/Age500CaloPU50_U19_500FB_V1A-v1/60000/BE83C7D5-1E48-E511-BAD3-002590A83190.root|/DYToTauTau_M-20_TuneZ2star_14TeV-pythia6-tauola/GEM2019Upg14DR-Age500CaloPU50_U19_500FB_V1A-v1/GEN-SIM-RECO|1              |0                 |2                       |
|/store/mc/RunIIWinter15wmLHE/TT_13TeV-powheg/LHE/MCRUN2_71_V1_ext4-v1/30000/9A880A75-366D-E511-BFDB-38EAA7A6DBA0.root                                                |/TT_13TeV-powheg/RunIIWinter15wmLHE-MCRUN2_71_V1_ext4-v1/LHE                                                |1              |0                 |2                       |
|/store/mc/RunIIWinter15wmLHE/TT_13TeV-powheg/LHE/MCRUN2_71_V1_ext4-v1/30000/C211E47B-366D-E511-8A45-001E673D21B9.root                                                |/TT_13TeV-powheg/RunIIWinter15wmLHE-MCRUN2_71_V1_ext4-v1/LHE                                                |1              |0                 |2                       |

You may look at DNs and timestamps of these datasets and raise your concern with the data-ops team. But I doubt this issue is relevant for this repository.

In data-ops, we have noticed many cases where PnR invalidates datasets[1], and the files stay valid. The update of these inner files can be done on our side, but it would be more straightforward to do it directly on DBS when invalidating the dataset, at least for future cases.
[1] https://cmsweb.cern.ch/das/request?input=dataset%3D%2FMuon%2FRun2022D-HcalCalIterativePhiSym-27Jun2023-v1%2FALCARECO&instance=prod/global

hi @amanrique1 so far it has always been the responsibility for the people who invalidate the files  in the data management system, to take the relevant actions in the book keeping system as well. In the past  it was  mostly done by PnR. I agree we may benefit a lot from a system where we can automate this process and keep the two system better in sync, but if it is not supposed to be done in the tools used by the relevant team to do the invalidation in parallel and this functionality requirement gets pushed upstream to the server side, then the project is much bigger than just automating an action. Ad may even involve cross database checks between Rucio and DBS ... This has been discussed in the past and is in our radar for sure.

Hi @todor-ivanov, I think I didn't explain myself well. The idea of this ticket is to get internal DBS consistency. If PnR invalidates a dataset, all its files get invalid as well.
In Data Ops, we are working on a separate project for the Rucio-DBS sync.


perforce.editOnFileSave appears to be successful, but error message is still shown

OS: Linux Mint 18.1
vscode: Version 1.11.2
vscode-perforce: 2.0.1
Other extensions: ms-vscode.cpptools, msjsdiag.debugger-for-chrome, dbaeumer.vscode-eslint, eg2.tslint
I have "perforce.editOnFileSave": true and when I make a simple modification (like adding a newline) into a file that is not checked out, it will be checked out into the default changelist as expected. I can see the change I made when I check the diff.
However, vscode still shows a message saying the file is write-protected:

cc @jel-massih

"perforce.editOnFileSave": true also gives me an error but the operation is NOT successful.
For now, a workaround is to use "perforce.editOnFilemodified": true

Yeah I think something might have changed in a recent update, I am getting this occasionally.
It might be a bit before I can take a look at this, have been pretty swamped lately.

Close as duplicate of #110


[BugFix] Fix CTE exchange deserialize error

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

For SQL:
MySQL td> set enable_exchange_pass_through=false;
Query OK, 0 rows affected
MySQL td> with xx as (select * from t0) select * from (select v1 from xx) x1 join (select v2 from xx) x2;
(1064, 'build chunk meta error')

Each CTEConsume will create new tuples because each CETConsume output columns may be different, but when the output has same column, will produce two tuple and the slot id is same.
ExchangeNode will deserialize column by tuple descipter when sender send columns by network way, then exchange node will find two slotId and report error

[FE PR Coverage check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/plan/PlanFragmentBuilder.java
2
2
100.00%


Enable Embedding API in watsonx.ai

Enable embedding api in watsonx.ai module.

Closes: #494

Cool!
@jmartisk care to review?

I also have in mind to write some end-to-end tests of the BAM and watsonx.ai module, but that is something for another PR.

I tried logging in with my Red Hat email and it has been saying

Your account setup is in progress, but we can't complete it right now. Log out for now and try again in a few minutes.

For 40 minutes. I'll try again tomorrow.


Fixing DP Predicate Test and improving performance 1300X times

Fixed the DP predicate test. It now correctly succeeds for all the DP equations and fails for the buggy implementation injected. More importantly, shortened its run time from 13 seconds for 10K iterations and 10K records to 0.01 seconds (1300X faster) for same iterations and same set of records. Did this by doing the exact aggregation once and adding vectorized noise 10K times instead of using loop for generating samples.

Finishing this merge as I have new changes in master branch to support evaluation of Burdock on same files and some new ones. Please review those set of commits.


RetrieveUserProxyAgent, use context_max_tokens from retrieve_config if provided

Why are these changes needed?
ragproxyagent = RetrieveUserProxyAgent(
    name="ragproxyagent",
    human_input_mode="NEVER",
    max_consecutive_auto_reply=3,
    retrieve_config={
        "task": "qa",
        "docs_path": ["mypath.md"],
        "chunk_token_size": 500,
        "context_max_tokens": 2000,
        "client": docdb,
        "embedding_model": "all-mpnet-base-v2",
        "get_or_create": True,
    },
    code_execution_config=False,  # set to False if you don't want to execute the code
)

RetrieveUserProxyAgent ignores the retrieve_config["context_max_tokens"] and always uses the default of self._max_tokens * 0.8. This is in conflict with the documented use:
- context_max_tokens (Optional, int): the context max token size for the retrieve chat.
    If key not provided, a default size `max_tokens * 0.8` will be used.

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Thanks for the PR! Cc @thinkall


Error retrieving credentials / ECR Registry

I am getting a bunch of errors like this:
time="2024-05-04T08:04:25Z" level=error msg="Error retrieving credentials" error="ecr: Failed to get authorization token: operation error ECR: GetAuthorizationToken, get identity: get credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, request canceled, context deadline exceeded"

E0504 08:04:25.125601       1 archfilter.go:167] "failed to get image architectures" err=<
	GET https://....dkr.ecr.eu-west-2.amazonaws.com/v2/.../manifests/latest: unexpected status code 401 Unauthorized: Not Authorized

I realize this is a kops / AWS specific issue, but still curious if someone knows the process to setup the permissions.

It seems like you need to enable IMDSv2 on your EC2 nodes, or allow your AWS role to use IMDS to begin with. It's an AWS issue, I mean you have to ensure your role has access to what it complains about until it's solved


KAFKA-3983 - Add additional information to debug

Add additional information to Acceptor debug message upon connection acceptance

Thanks for the PR, LGTM.

Merged to trunk and 0.10.0 branches.


Upgrade vale to v3

Vale has introduced a new major version v3. This release has some breaking changes requiring us to refactor some configuration in our repos. For more details see: https://github.com/errata-ai/vale/releases/tag/v3.0.0

Closed by: https://github.com/coopnorge/engineering-docker-images/pull/1992


ETIMEDOUT when trying to start sleepy_brattain container from Kitematic

im using Windows 8 and after executing "docker run nginx" for the first time, i see that there more containers in the kitematic app (left column).  i tried opening sleepy_brattain and got this error

This is somewhat the expected behavior - The docker run command you've pointed out doesn't name the container or specify how it should run - See the hub documentation for the proper flags:
https://hub.docker.com/_/nginx/
Instead of the command line, use kitematic directly to get your containers created. There's an official 'hello-world-nginx' image that you can spin up to see the proper behavior.

Closing as this isn't really an issue but confusion on usage. Feel free to re-open if needed.


Update API LEVEL 18

Description
Please provide a detailed description of what was done in this PR.
(And mention any links to an issue docs)
Changes include

[x] Bugfix (non-breaking change that solves an issue)
[x] New feature (non-breaking change that adds functionality)
[x] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

Breaking changes
Includes breaking change from https://github.com/LedgerHQ/ledger-secure-sdk/pull/581
Not a problem as this API LEVEL does not target a released version of Stax yet.

Codecov Report
Attention: Patch coverage is 50.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 59.66%. Comparing base (a566922) to head (f1a0a89).
Report is 1 commits behind head on API_LEVEL_18.

Files
Patch %
Lines

lib_nbgl/src/nbgl_fonts.c
50.00%
1 Missing :warning:

Additional details and impacted files
@@               Coverage Diff                @@
##           API_LEVEL_18     #597      +/-   ##
================================================
+ Coverage         59.65%   59.66%   +0.01%
================================================
  Files                12       12
  Lines              1678     1676       -2
================================================
- Hits               1001     1000       -1
+ Misses              677      676       -1

Flag
Coverage Δ

unittests
59.66% <50.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

and this one  also (once it's merged)  ;-)


[CRITICAL] New sign-ups redirected from OldDot have two workspaces created on completion of the onboarding modal.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.66-8
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation (hyperlinked to channel name): #convert thread.
Action Performed:

Go to expensify.com
Click “Manage my expenses for a small team (1-9)”
Enter an email address > click “Get Started”
Redirected to NewDot
Observe a workspace has been created.
Complete the accounting step to close the onboarding modal
Observe another workspace is created.

Expected Result:
Only one workspace should be created in the onboarding flow.
Actual Result:
A second workspace is created on completion of the last step of the onboarding flow.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos
https://github.com/user-attachments/assets/255aa9e2-8c0f-421d-91be-be7ee9eb5d02
View all open jobs on GitHub
Issue OwnerCurrent Issue Owner: @rayane-djouah

https://expensify.slack.com/archives/C02NK2DQWUX/p1732761149927579 - asking the C+ team for eyes on the problem here as this is pretty bad in the onboarding journey.

Possible leads:

https://github.com/Expensify/App/issues/52894
https://github.com/Expensify/App/issues/50758
https://github.com/Expensify/App/issues/51750

In fact, @FitseTLT for #52894. One PR is merged, then there's another PR  with exactly the same title that's not merged. What's going on there, and is that going to fix this? CC: @mountiny

@FitseTLT original solution did not work on desktop and one other platform so thats why there is one more fix

Cool, would be helpful to name the PRs a bit differently 😅
That said, this bug above is on web production. I don't need to refresh or close/reopen etc. Is that PR going to fix it?

I am not sure, @FitseTLT @rayane-djouah Are you able to reproduce based on the instructions from the OP?

yeah this will solved by the recent PR @mountiny Let's just hold this for it. And also @mountiny bump for your review on that PR. Thx

I think we need to CP that to staging to test and hopefully go with today's app deploy to production. This is borderline a fire in my mind, creating two workspaces for every sign-up is rough.

Linking for posterity: https://github.com/Expensify/App/pull/53093
We can probably close this now.


certificate error with elliptic curve

I got a new certificate by global sign that uses ecc. I get the following error. How do I enable ecc support? Is this netty related or do I need to update java with something?
Dec 12 14:29:55 dls-rbg-mb-10 java: Exception in thread "Thread-1" java.lang.IllegalArgumentException: File does not contain valid private key: /etc/pki/tls/private/app_dls-gmbh_biz.key.pem
Dec 12 14:29:55 dls-rbg-mb-10 java: at io.netty.handler.ssl.SslContextBuilder.keyManager(SslContextBuilder.java:251)
Dec 12 14:29:55 dls-rbg-mb-10 java: at io.netty.handler.ssl.SslContextBuilder.keyManager(SslContextBuilder.java:206)
Dec 12 14:29:55 dls-rbg-mb-10 java: at io.netty.handler.ssl.SslContextBuilder.forServer(SslContextBuilder.java:49)
Dec 12 14:29:55 dls-rbg-mb-10 java: at de.konsultaner.wamp.peer.Router.run(Router.java:144)
Dec 12 14:29:55 dls-rbg-mb-10 java: at java.lang.Thread.run(Thread.java:745)
Dec 12 14:29:55 dls-rbg-mb-10 java: Caused by: java.security.NoSuchAlgorithmException: EC KeyFactory not available Dec 12 14:29:55 dls-rbg-mb-10 java: at java.security.KeyFactory.<init>(KeyFactory.java:138)
Dec 12 14:29:55 dls-rbg-mb-10 java: at java.security.KeyFactory.getInstance(KeyFactory.java:172)
Dec 12 14:29:55 dls-rbg-mb-10 java: at io.netty.handler.ssl.SslContext.getPrivateKeyFromByteBuffer(SslContext.java:947)
Dec 12 14:29:55 dls-rbg-mb-10 java: at io.netty.handler.ssl.SslContext.toPrivateKey(SslContext.java:918)
Dec 12 14:29:55 dls-rbg-mb-10 java: at io.netty.handler.ssl.SslContextBuilder.keyManager(SslContextBuilder.java:249)
Dec 12 14:29:55 dls-rbg-mb-10 java: ... 4 more

This error might be related to #8149
Netty version
4.1.20
JVM version (e.g. java -version)
openjdk version "1.8.0_91"
OpenJDK Runtime Environment (build 1.8.0_91-b14)
OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
OS version (e.g. uname -a)
Linux 3.10.0-327.18.2.el7.x86_64 #1 SMP Thu May 12 11:03:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I could send you the key as email. I would like to use it in production and github is not the right place share a private key 😅

Cant I just use openssl to generate a self-signed one that reproduce it somehow ?

On 14. Dec 2018, at 09:33, Richard<EMAIL_ADDRESS>wrote:
I could send you the key as email. I would like to use it in production and github is not the right place share a private key 😅
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/netty/netty/issues/8657#issuecomment-447253609, or mute the thread https://github.com/notifications/unsubscribe-auth/AAa0Qmx4jsZV9aZhwBWMxAkn5ipDRAXKks5u42JpgaJpZM4ZTFHQ.

@konsultaner ^^

@normanmaurer sorry, I didn't create any of those. I'm still having problems with other people involved to give you material to work on this issue. As soon as I have everything I will post it here.

@normanmaurer  this is the old cert: cert.zip
I will send you the password as email.

I think this due your openjdk version you use. Please use a more recent version.
There are also multiple bug-reports against RHEL / centos related to this. Like: https://bugzilla.redhat.com/show_bug.cgi?id=1245810
Please report back one you did the upgrade and re-open if you still have the problem.
Caused by: java.security.NoSuchAlgorithmException: EC KeyFactory not available

Is thrown because the JDK does not support EC.


Delete lifetime dependence mangling

Mangling this information for future directions like component lifetimes becomes complex and the current mangling scheme isn't scalable anyway.
Deleting this support for now.
rdar://131556007

@swift-ci test

@swift-ci test

@swift-ci test windows platform

Merge conflict. Testing again..

@swift-ci smoke test

@swift-ci test

@swift-ci smoke test macOS platform


Adds human controls (Linux only) and simplify code

Tested on Linux

we need human controls on windows~

I'm stuck on this interface. Normally, I should be asked to configure the buttons, but I pressed anything and there was no response


ciao/README.md: Update instructions

Specify ansible requirements for managed nodes and control machine
add --ignore-certs to ansible-galaxy command to sort proxy issues
Specify passwordless sudo is required in deployment machine and managed nodes

Fixes #37
Signed-off-by: Alberto Murillo<EMAIL_ADDRESS>

@markdryan can u review this one before I close https://github.com/clearlinux/clear-config-management/issues/37

I dont need --ignore-certs anymore. so I'm removing this

Does it even work for you when using a proxy without --ignore-certs?

It is working on my ubuntu machines but not in my clearlinux machines (all behind proxy)
so this must be an issue with outdated ca certificates.
I better open a new issue to track this

@albertomurillo I still need to specify --ignore-certs on my machine. I'm doing a --force.

@markdryan
#37 Was asking to cover different things so I have it broken down into #49 and #47
I think this PR fixes what remains of #37 now.

@albertomurillo Where are the first items in #37 covered?

My bad. I just added the comments on the original issue.
https://github.com/clearlinux/clear-config-management/issues/37#issuecomment-248663466


Issue 233 with lindat common

This is a replacement of https://github.com/ufal/lindat-dspace/pull/361
fixes #233 and #361

Updated to releases branch of lindat common - I hope it's correct


[Offtopic] Adding BedrockEconomy support in the SellAll fork

Sorry for commenting here but it won't let me open an issue in a fork.
I would like to know if you can add support for BedrockEconomy in the SellAll fork you have created. EconomyAPI has become quite outdated in many aspects and I wanted to know if you were planning to add it and upload it to appear in Poggit.

Please create an issue in SellAll repository


ARTEMIS-2985 - don't block netty threads for mqtt protocol actions

I am still working on an intermittent test failure, more eyes welcome
MQTTQueueCleanTest.testQueueCleanWhenConnectionSynExeConnectAndDisconnect

the test failure was the result of adding a consumer without being fully initialised.
server == null
see: https://github.com/apache/activemq-artemis/pull/3336/files#diff-b56a3b568eccf7ca40814304ea1776eae27b1a4a2e5273cc2403470eae6414a3R257


How can I test for multiple inputs

How stress test if there multiple inputs like graph of n nodes a array permutation of n nodes and Binary string of of length n
2.How can I see failed test case when I use qt cmp ?

Sorry, I've only just seen your message.
If you wish to view the failed test cases, you can attempt adding the --diff flag, similar to this
qt cmp -t main.cpp --c correct.cpp -g gen.cpp --diff

Here I leave the documentation of the command, in case it is required.
Cmp Docs

Hey thanks I will look into this


[feat] Make doge accept everywhere like google pay or make doge payment gateway

Feature Request
Describe the Feature Request

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

We're pushing ahead with stability of the codebase to help adoption by payment processors, but ultimately the decision to adopt Dogecoin is theirs, we're just trying to encourage them.


set DefaultSnifferEnabled false

These days, many people use docker, so we use Elasticsearch on Docker.
In this Elasticsearch client, many people encount error no active connection found.
I am also one of them and wasted a few hours trying to resolve.
I want to change Default value!

@olivere How about this idea? If ok, I fix unit test to pass.

We had the same discussion before v7, and decided against it. The main reason was that while it might be helpful for new users, it would change the defaults for all existing users--in the worst possible way.
If we'd change it, we can only do so with a major version change.


MAINT: Only do nightly full builds

Now that we are paying for CircleCI builds, it would be nice to cut down our usage a bit. One way to do this is to only build dev and maint/0.24 nightly, and only if they have changed. So this PR:

Makes it so that each build creates a _build/html/_version.txt that contains the SHA of the commit.
It quits on non-PR builds if it sees that it's not a scheduled build, unless there is a [circle deploy] in the commit line (hopefully we will only rarely need this, but it could come in handy around release time)
If it is a scheduled build, compares https://mne.tools/stable/_version.txt or https://mne.tools/dev/_version.txt (I put dummy ones in there manually for now) to the current commit number, and quits if the version numbers match.
Gets rid of "interactive_test", we don't really use it, and when we need something like it, it's probably easy enough to SSH in and venv manually now.
Fixes a failure due to pick_channels deprecation

For now I have the schedule actually set to every hour in order to allow me to debug more easily. Once it this is merged, I'll push directly to main to make it work, then reset to "0 0 * * *" to make it nightly rather than hourly. Then I'll backport to maint/0.24, and hopefully things will work smoothly from there!
EDIT:
Post-merge tasks:

[x] Make sure [circle deploy] starts a full build, then cancel it
[X] Make sure 20-after-the-hour scheduled build runs due to SHA difference: https://app.circleci.com/pipelines/github/mne-tools/mne-python/11705/workflows/b29212ba-ff32-4973-bad0-adbd052e8272/jobs/39134
[ ] Make sure it completes (manually canceling any other on-the-hour runs that pop up in the meantime)
[ ] Restore as actually nightly build on the cron line, make sure it doesn't cause a build (because not scheduled and no [circle deploy] line)
[ ] git cherry-pick 05f0358 7999f86 2259226 f8d8719 ... to maint/0.24

should we close #10006 after this is merged?

should we close #10006 after this is merged?

I went ahead and closed it already since it's technically fixed even without this PR. This PR should just help keep our bills smaller :)

... when I merge this, I'm going to tag it with [circle deploy] just to see if it gets recognized properly, then cancel the build. Then on the hour, hopefully the schedule kicks in and starts a build for us! (Hopefully the current changes-only PR run will return before the turn of the hour so that we don't have to wait...)

It timed out after 3h during the artifact uploading stage (argh!). Slowest ones:
computation time summary:
    - ../tutorials/clinical/30_ecog.py:                                       261.95 sec    513.9 MB
    - ../tutorials/intro/70_report.py:                                        229.07 sec    363.0 MB
    - ../tutorials/preprocessing/40_artifact_correction_ica.py:               187.72 sec    649.4 MB
    - ../examples/inverse/mixed_norm_inverse.py:                              162.41 sec    394.9 MB
    - ../tutorials/clinical/10_ieeg_localize.py:                              153.59 sec    917.8 MB
    - ../tutorials/inverse/40_mne_fixed_free.py:                              140.15 sec    508.7 MB
    - ../examples/time_frequency/source_power_spectrum_opm.py:                119.01 sec    617.0 MB
    - ../tutorials/forward/30_forward.py:                                     114.05 sec    571.3 MB
    - ../tutorials/inverse/60_visualize_stc.py:                               111.43 sec    552.7 MB
    - ../tutorials/clinical/20_seeg.py:                                       108.13 sec    365.9 MB
    - ../examples/inverse/covariance_whitening_dspm.py:                       102.94 sec    877.8 MB
    - ../tutorials/inverse/50_beamformer_lcmv.py:                             102.33 sec    827.8 MB
    - ../tutorials/preprocessing/30_filtering_resampling.py:                  100.92 sec    820.9 MB

I'll probably make a PR to try to reduce these. For now I also tried setting the resource class to large, but it would be better if we didn't have to make that switch.

Even with the large machine class we still timed out. So I think we'll need to get it to build in < 3h to make things work. I think it's probably worth doing this anyway, 3h is a long time to build the docs. It seems like not too long ago it only took ~1.5h, perhaps we need to be more careful about how long examples and tutorials take going forward.


plasma: 5.11.3 -> 5.11.4

Motivation for this change
@adisbladis, @ttuegel
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks 👍


Release/mainnet v1.0.0 candidate

Purpose
Mainnet candidate v1.0.0

For me it seems like easier would be just force push master with this changes, because that PR looks unreal to review and useless because of that :)

I agree, lets just force push this.  Nothing to review really.

prnet cleaned-up successfully


Supporting nullable data types for float data, Float32 and Float64

pandas experimentally starts to support nullable data types for float data, Float32 and Float64 from pandas 1.2.
The difference from the existing float32 and float64 as below.
# the default NumPy float64 dtype
In [11]: s1 = pd.Series([1.5, None])

In [12]: s1
Out[12]:
0    1.5
1    NaN
Length: 2, dtype: float64

In [13]: s1 > 1
Out[13]:
0     True
1    False
Length: 2, dtype: bool

# the new nullable float64 dtype
In [14]: s2 = pd.Series([1.5, None], dtype="Float64")

In [15]: s2
Out[15]:
0     1.5
1    <NA>
Length: 2, dtype: Float64

In [16]: s2 > 1
Out[16]:
0    True
1    <NA>
Length: 2, dtype: boolean

I'm investigating them as well as Int64, Int32, etc. or boolean, string types.

I'm investigating them as well as Int64, Int32, etc. or boolean, string types.


Develop - members section

Add members sections/cards along with focus and hobbies

Great job! Removed spacing for section end comments and removed contact section.


[v1.0] Small fix in the README and DENAS NLP demo

This PR is updated with the followings:

Small word fix in the general readme.
Update the DENAS NLP training parameters in the demo.

Please help review this PR. Thx. @xuechendi @Jian-Zhang

@tianyil1 , @Jian-Zhang , I saw pics in demo page is a quite blue, how about we use white backgroud?

@tianyil1 , highlight line replace '-recursive' to '--recursive'

@tianyil1 , path change in demo is not changed accordingly

Thanks for your suggestions. I have fixed the above issues. @xuechendi


Building Ubuntu VM setup locally

Hi, I found instructions on how to build a VM on Azure but I'd like to set it up locally so that I can easily test all my config before pushing to the repository. Would you mind helping out with that? Ideally, it would be nice if there was a docker image one can download, or at least some kind of script setting up the environment, installing packages, etc. Without that, it's rather difficult to guess what will or will not work, and I end up making changes, pushing, then fixing, then pushing... you get the idea.
I would very much appreciate some help with setting it up or finding other resources that could help me.

Hello @elshize,
There was a separate project in the past, where it was possible to build separate agent in docker image for local testing. Currently, in order to build local machine with pre-installed software on your own, I see only one way:

Take installation scripts for windows/linux
Perform commands one by one, according to configuration files:
Ubuntu 16
Ubuntu 18
Windows 2019
Windows 2016
Also, it is possible to build your own image using Packer and how you have already mentioned, you can use separate virtual machine with pre-installed software and perform all required tests in it.

Thanks @Darleev, this helps a lot. Just to clarify, since I'm not familiar with Packer, this can be used to set up a VM outside of cloud, as in my local desktop for instance?

@elshize for local testing, you can use the following approaches:
VMware
Hyper-V
VirtualBox
In other words, need to build image for one of these virtual environments and deploy as virtual machine locally.

Thanks, sounds good. I should be able to take it from here. I appreciate you taking the time to help, thanks a bunch!

@elshize I'm going to close the issue.
In case of any questions, please let us know.

@Darleev Thanks again for your help!


No module named 'fastapi'

There seems to be a missing entry for fastapi in our requirements.txt:
======================================================================
ERROR: test_dataset_manager_collection (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: test_dataset_manager_collection
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/unittest/loader.py", line 154, in loadTestsFromName
    module = __import__(module_name)
  File "/home/runner/work/DMOD/DMOD/python/services/dataservice/dmod/test/test_dataset_manager_collection.py", line 13, in <module>
    from .test_required_data_checks_manager import MockDataset, MockDatasetManager
  File "/home/runner/work/DMOD/DMOD/python/services/dataservice/dmod/test/test_required_data_checks_manager.py", line 8, in <module>
    from ..dataservice.service import ActiveOperationTracker, RequiredDataChecksManager
  File "/home/runner/work/DMOD/DMOD/python/services/dataservice/dmod/dataservice/service.py", line 23, in <module>
    from fastapi.websockets import WebSocket
ModuleNotFoundError: No module named 'fastapi'

======================================================================
ERROR: test_required_data_checks_manager (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: test_required_data_checks_manager
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/unittest/loader.py", line 154, in loadTestsFromName
    module = __import__(module_name)
  File "/home/runner/work/DMOD/DMOD/python/services/dataservice/dmod/test/test_required_data_checks_manager.py", line 8, in <module>
    from ..dataservice.service import ActiveOperationTracker, RequiredDataChecksManager
  File "/home/runner/work/DMOD/DMOD/python/services/dataservice/dmod/dataservice/service.py", line 23, in <module>
    from fastapi.websockets import WebSocket
ModuleNotFoundError: No module named 'fastapi'

Fastapi probably just needs to be added to the requirements.txt file, but this is breaking the unit tests.

For some reason this happens spuriously and it has to do with the environment caching we do in the update individual packages step. I cleared the runner caches and re-ran the Testing and Validation jobs on master and they all passed. Im going to close this for now.