pypodman doesn't able to list the images on the remote machine.

Is this a BUG REPORT or FEATURE REQUEST?:
kind bug
Description
pypodman not able to list the images on the remote instance which is running podman.
Steps to reproduce the issue:
Remote Machine
[prkumar@local bin]$ ./minishift ip
<IP_ADDRESS>
[prkumar@local bin]$ ./minishift ssh
Last login: Thu Oct  4 01:36:40 2018 from <IP_ADDRESS>
[docker@minishift ~]$ cat /etc/redhat-release
Fedora release 28 (Twenty Eight)
[docker@minishift ~]$ podman images
REPOSITORY                                 TAG      IMAGE ID       CREATED       SIZE
docker.io/openshift/origin-control-plane   latest   1e2472e9634b   5 hours ago   836MB
docker.io/library/fedora                   latest   c582c1438f27   3 weeks ago   264MB
[docker@minishift ~]$ sudo systemctl status io.podman.socket
Failed to dump process list, ignoring: No such file or directory
* io.podman.socket - Podman Remote API Socket
   Loaded: loaded (/usr/lib/systemd/system/io.podman.socket; enabled; vendor preset: disabled)
   Active: active (listening) since Thu 2018-10-04 01:32:12 EDT; 15min ago
     Docs: man:podman-varlink(1)
   Listen: /run/podman/io.podman (Stream)
   CGroup: /system.slice/io.podman.socket

Oct 04 01:32:12 minishift systemd[1]: Listening on Podman Remote API Socket.
[docker@minishift ~]$ podman version
Version:       0.9.1
Go Version:    go1.10.4
OS/Arch:       linux/amd64
[docker@minishift ~]$ podman info
host:
  Conmon:
    package: podman-0.9.1-3.gitaba58d1.fc28.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 1.12.0-dev, commit: 1d75f1d54e9e123a97e7f505e38df7ab7192cfa7-dirty'
  MemFree: 192327680
  MemTotal:<PHONE_NUMBER>
  OCIRuntime:
    package: runc-1.0.0-51.dev.gitfdd8055.fc28.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.0'
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 2
  hostname: minishift
  kernel: 4.18.10-200.fc28.x86_64
  os: linux
  uptime: 44m 25.54s
insecure registries:
  registries: []
registries:
  registries:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ContainerStore:
    number: 0
  GraphDriverName: vfs
  GraphOptions: []
  GraphRoot: /home/docker/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 2
  RunRoot: /run/user/1000/run

Host Machine
[prkumar@local ~]$ pypodman --version
pypodman v. 0.9.1

[prkumar@local ~]$ pypodman --user docker --host <IP_ADDRESS> -i ~/.minishift/machines/minishift/id_rsa images
2018-10-04 11:07:46 IST | CRITICAL | [Errno 104] Connection reset by peer
[prkumar@local ~]$ pypodman --user docker --host <IP_ADDRESS> -i ~/.minishift/machines/minishift/id_rsa --log-level DEBUG images
2018-10-04 11:08:05 IST | DEBUG    | Logging initialized at level DEBUG
2018-10-04 11:08:05 IST | DEBUG    | Opening tunnel "unix:/run/user/1000/pypodman/podman.socket", cmd "ssh -fNT -v -L /run/user/1000/pypodman/podman.socket:/run/podman/io.podman -i /home/prkumar/.minishift/machines/minishift/id_rsa<EMAIL_ADDRESS>OpenSSH_7.8p1, OpenSSL 1.1.0i-fips  14 Aug 2018
debug1: Reading configuration data /home/prkumar/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
debug1: Connecting to <IP_ADDRESS> [<IP_ADDRESS>] port 22.
debug1: Connection established.
debug1: identity file /home/prkumar/.minishift/machines/minishift/id_rsa type 0
debug1: identity file /home/prkumar/.minishift/machines/minishift/id_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.8
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.8
debug1: match: OpenSSH_7.8 pat OpenSSH* compat 0x04000000
debug1: Authenticating to <IP_ADDRESS>:22 as 'docker'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm<EMAIL_ADDRESS>debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher<EMAIL_ADDRESS>MAC: <implicit> compression: none
debug1: kex: client->server cipher<EMAIL_ADDRESS>MAC: <implicit> compression: none
debug1: kex<EMAIL_ADDRESS>need=32 dh_need=32
debug1: kex<EMAIL_ADDRESS>need=32 dh_need=32
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:T3U1d+C6S1+WUWW+WhULT/E6gW5rmHrZT0B3SjSvhdY
debug1: Host '<IP_ADDRESS>' is known and matches the ECDSA host key.
debug1: Found key in /home/prkumar/.ssh/known_hosts:263
debug1: rekey after<PHONE_NUMBER> blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after<PHONE_NUMBER> blocks
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,null>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
No Kerberos credentials available (default cache: KEYRING:persistent:1000)

debug1: Unspecified GSS failure.  Minor code may provide more information
No Kerberos credentials available (default cache: KEYRING:persistent:1000)

debug1: Next authentication method: publickey
debug1: Offering public key: RSA SHA256:LA7hDAKHZ2ihRodkiaiVcRIf7UjwT4lEFb6BMpyyLR8 /home/prkumar/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Offering public key: RSA SHA256:iMTILq7fl6TnilwshALRHFrovMrE3OQHew4v+qlGteQ prkumar@local
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Offering public key: RSA SHA256:bevNzxxYkuf8TyYDZf+bysQVMPQwhWgSGdHop1d2aL0 centos-ci
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Offering public key: RSA SHA256:/Nj0lcaNzCuuUAGr0WR+4Ml7iA5af0lJUv6+XvcoEu4 /home/prkumar/.minishift/machines/minishift/id_rsa
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug1: Authentication succeeded (publickey).
Authenticated to <IP_ADDRESS> ([<IP_ADDRESS>]:22).
debug1: Local connections to /run/user/1000/pypodman/podman.socket:-2 forwarded to remote address /run/podman/io.podman:-2
debug1: Local forwarding listening on path /run/user/1000/pypodman/podman.socket.
debug1: channel 0: new [unix listener]
debug1: Requesting<EMAIL_ADDRESS>debug1: forking to background
debug1: Entering interactive session.
debug1: pledge: network
debug1: Connection to port -2 forwarding to /run/podman/io.podman port -2 requested.
debug1: channel 1: new<EMAIL_ADDRESS>debug1: client_input_global_request: rtype<EMAIL_ADDRESS>want_reply 0
debug1: Remote: /home/docker/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug1: Remote: /home/docker/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
channel 1: open failed: connect failed: open failed
debug1: channel 1: free<EMAIL_ADDRESS>listening port -2 for /run/podman/io.podman port -2, connect from  port 0 to /run/user/1000/pypodman/podman.socket port 0, nchannels 2
2018-10-04 11:08:05 IST | DEBUG    | Closing tunnel "unix:/run/user/1000/pypodman/podman.socket"
debug1: channel 0: free: unix listener, nchannels 1
Transferred: sent 4000, received 2896 bytes, in 0.3 seconds
Bytes per second: sent 13937.6, received 10090.8
debug1: Exit status 0
2018-10-04 11:08:05 IST | CRITICAL | [Errno 104] Connection reset by peer
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/pypodman/main.py", line 58, in main
    returncode = getattr(obj, args.method)()
  File "/usr/lib/python3.6/site-packages/pypodman/lib/actions/images_action.py", line 56, in list
    self.client.images.list(),
  File "/usr/lib/python3.6/site-packages/pypodman/lib/action_base.py", line 72, in client
    identity_file=self.identity_file)
  File "/usr/lib/python3.6/site-packages/podman/client.py", line 175, in __init__
    if not System(self._client).ping():
  File "/usr/lib/python3.6/site-packages/podman/libs/system.py", line 38, in ping
    with self._client() as podman:
  File "/usr/lib/python3.6/site-packages/podman/client.py", line 125, in __enter__
    self._iface = self._client.open(self._context.interface)
  File "/usr/lib/python3.6/site-packages/varlink/client.py", line 550, in open
    self.get_interface(interface_name, socket_connection=connection)
  File "/usr/lib/python3.6/site-packages/varlink/client.py", line 590, in get_interface
    desc = _service.GetInterfaceDescription(interface_name)
  File "/usr/lib/python3.6/site-packages/varlink/client.py", line 84, in _wrapped
    return self._call(method.name, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/varlink/client.py", line 141, in _call
    (message, more) = self._next_varlink_message()
  File "/usr/lib/python3.6/site-packages/varlink/client.py", line 102, in _next_varlink_message
    message = next(self._next_message())
  File "/usr/lib/python3.6/site-packages/varlink/client.py", line 244, in _next_message
    data = self._connection.recv(8192)
ConnectionResetError: [Errno 104] Connection reset by peer
2018-10-04 11:08:05 IST | INFO     | Review connection arguments for correctness.
2018-10-04 11:08:05 IST | DEBUG    | Closing tunnel "unix:/run/user/1000/pypodman/podman.socket"

Describe the results you received:
Not able to show the images.
Describe the results you expected:
Should able to show the images.

@jwhonce PTAL

@praveenkumar "channel 1: open failed: connect failed: open failed" is the issue.  For some reason the ssh channel dropped.  Can you successfully ssh from the Host to the minishift instance?  For testing with VM's I had to setup iptable rules to forward packets from the host to the VM.

For some reason the ssh channel dropped. Can you successfully ssh from the Host to the minishift instance?

@jwhonce yes I can ssh from host to minishift VM without any issue and even execute the commands. In the logs you can see following.
$ ./minishift ssh  => this is able to execute and ssh to VM without any issue.
Last login: Thu Oct  4 01:36:40 2018 from <IP_ADDRESS>

[docker@minishift ~]$ cat /etc/redhat-release  => able to execute any commands on the VM
Fedora release 28 (Twenty Eight)

[docker@minishift ~]$ podman images
REPOSITORY                                 TAG      IMAGE ID       CREATED       SIZE
docker.io/openshift/origin-control-plane   latest   1e2472e9634b   5 hours ago   836MB
docker.io/library/fedora                   latest   c582c1438f27   3 weeks ago   264MB

@praveenkumar Can you ssh without using the minishift command or give that command the ssh verbose option so that I may see the ssh login sequence.  Thank you.

Can you ssh without using the minishift command or give that command the ssh verbose option so that I may see the ssh login sequence

@jwhonce here you go, let me know if you need anymore debug stuff.
$ ssh -vvv -i ~/.minishift/machines/minishift/id_rsa<EMAIL_ADDRESS>OpenSSH_7.8p1, OpenSSL 1.1.0i-fips  14 Aug 2018
debug1: Reading configuration data /home/prkumar/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line 52: Including file /etc/ssh/ssh_config.d/05-redhat.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug3: /etc/ssh/ssh_config.d/05-redhat.conf line 2: Including file /etc/crypto-policies/back-ends/openssh.config depth 1
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug3: gss kex names ok: [gss-gex-sha1-,gss-group14-sha1-]
debug3: kex names ok: [curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1]
debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
debug2: resolve_canonicalize: hostname <IP_ADDRESS> is address
debug2: ssh_connect_direct
debug1: Connecting to <IP_ADDRESS> [<IP_ADDRESS>] port 22.
debug1: Connection established.
debug1: identity file /home/prkumar/.minishift/machines/minishift/id_rsa type 0
debug1: identity file /home/prkumar/.minishift/machines/minishift/id_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.8
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.8
debug1: match: OpenSSH_7.8 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to <IP_ADDRESS>:22 as 'docker'
debug3: hostkeys_foreach: reading file "/home/prkumar/.ssh/known_hosts"
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes256-cbc,aes128-gcm@openssh.com,aes128-ctr,aes128-cbc
debug2: ciphers stoc: aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes256-cbc,aes128-gcm@openssh.com,aes128-ctr,aes128-cbc
debug2: MACs ctos: hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512
debug2: MACs stoc: hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes256-cbc,aes128-gcm@openssh.com,aes128-ctr,aes128-cbc
debug2: ciphers stoc: aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes256-cbc,aes128-gcm@openssh.com,aes128-ctr,aes128-cbc
debug2: MACs ctos: hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512
debug2: MACs stoc: hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512
debug2: compression ctos<EMAIL_ADDRESS>debug2: compression stoc<EMAIL_ADDRESS>debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm<EMAIL_ADDRESS>debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher<EMAIL_ADDRESS>MAC: <implicit> compression: none
debug1: kex: client->server cipher<EMAIL_ADDRESS>MAC: <implicit> compression: none
debug1: kex<EMAIL_ADDRESS>need=32 dh_need=32
debug1: kex<EMAIL_ADDRESS>need=32 dh_need=32
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:qh30isDafzvEyqTtC1yYdigKwO/Z2TkWwjuuhQeGceQ
debug3: hostkeys_foreach: reading file "/home/prkumar/.ssh/known_hosts"
The authenticity of host '<IP_ADDRESS> (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is SHA256:qh30isDafzvEyqTtC1yYdigKwO/Z2TkWwjuuhQeGceQ.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after<PHONE_NUMBER> blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after<PHONE_NUMBER> blocks
debug2: key: /home/prkumar/.minishift/machines/minishift/id_rsa (0x55b863deace0), explicit
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,null>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup gssapi-keyex
debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_is_enabled gssapi-keyex
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug2: we did not send a packet, disable method
debug3: authmethod_lookup gssapi-with-mic
debug3: remaining preferred: publickey,keyboard-interactive,password
debug3: authmethod_is_enabled gssapi-with-mic
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
Server<EMAIL_ADDRESS>not found in Kerberos database

debug3: send packet: type 50
debug2: we sent a gssapi-with-mic packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug2: we did not send a packet, disable method
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: RSA SHA256:yx8emMhwn1jXbNKCym8mYmUAte4zt26dZKJtkMhHAog /home/prkumar/.minishift/machines/minishift/id_rsa
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug2: input_userauth_pk_ok: fp SHA256:yx8emMhwn1jXbNKCym8mYmUAte4zt26dZKJtkMhHAog
debug3: sign_and_send_pubkey: RSA SHA256:yx8emMhwn1jXbNKCym8mYmUAte4zt26dZKJtkMhHAog
debug3: sign_and_send_pubkey: signing using rsa-sha2-512
debug3: send packet: type 50
debug3: receive packet: type 52
debug1: Authentication succeeded (publickey).
Authenticated to <IP_ADDRESS> ([<IP_ADDRESS>]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Requesting<EMAIL_ADDRESS>debug3: send packet: type 80
debug1: Entering interactive session.
debug1: pledge: network
debug3: receive packet: type 80
debug1: client_input_global_request: rtype<EMAIL_ADDRESS>want_reply 0
debug3: receive packet: type 4
debug1: Remote: /home/docker/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug3: receive packet: type 4
debug1: Remote: /home/docker/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: ssh_packet_set_tos: set IP_TOS 0x48
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug3: send packet: type 98
debug1: Sending environment.
debug3: Ignored env QTINC
debug1: Sending env LC_ALL = en_US.utf-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env LS_COLORS
debug3: Ignored env SSH_CONNECTION
debug3: Ignored env MODULES_RUN_QUARANTINE
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env HISTCONTROL
debug3: Ignored env GUESTFISH_RESTORE
debug3: Ignored env HOSTNAME
debug3: Ignored env QTDIR
debug3: Ignored env EDITOR
debug3: Ignored env PATH_modshare
debug3: Ignored env LOADEDMODULES_modshare
debug3: Ignored env GUESTFISH_INIT
debug3: Ignored env XDG_SESSION_ID
debug3: Ignored env MODULES_CMD
debug3: Ignored env USER
debug3: Ignored env ENV
debug3: Ignored env GUESTFISH_PS1
debug3: Ignored env GOPATH
debug3: Ignored env SELINUX_ROLE_REQUESTED
debug3: Ignored env PWD
debug3: Ignored env SSH_ASKPASS
debug3: Ignored env HOME
debug1: Sending env LC_CTYPE = UTF-8
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env SSH_CLIENT
debug3: Ignored env SELINUX_LEVEL_REQUESTED
debug3: Ignored env BASH_ENV
debug3: Ignored env XDG_DATA_DIRS
debug3: Ignored env _LMFILES__modshare
debug3: Ignored env LOADEDMODULES
debug3: Ignored env SSH_TTY
debug3: Ignored env MAIL
debug3: Ignored env QTLIB
debug3: Ignored env TERM
debug3: Ignored env SHELL
debug3: Ignored env SELINUX_USE_CURRENT_RANGE
debug3: Ignored env SHLVL
debug3: Ignored env MODULEPATH
debug3: Ignored env LOGNAME
debug3: Ignored env DBUS_SESSION_BUS_ADDRESS
debug3: Ignored env XDG_RUNTIME_DIR
debug3: Ignored env MODULEPATH_modshare
debug3: Ignored env PATH
debug3: Ignored env _LMFILES_
debug3: Ignored env GUESTFISH_OUTPUT
debug3: Ignored env MODULESHOME
debug3: Ignored env HISTSIZE
debug3: Ignored env CVS_RSH
debug3: Ignored env LESSOPEN
debug3: Ignored env BASH_FUNC_module%%
debug3: Ignored env BASH_FUNC_switchml%%
debug3: Ignored env BASH_FUNC_scl%%
debug3: Ignored env BASH_FUNC__moduleraw%%
debug3: Ignored env _
debug3: Ignored env OLDPWD
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
-bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf-8)
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf-8)
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf-8)
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.utf-8)

The machine that you successfully log into is <IP_ADDRESS> while the failed one is <IP_ADDRESS>.  I would suspect something in the setup/configuration.  I cannot recreate the issue on my local machines.

I am going to close this since I think this is a configuration issue.


[$500]  Workspace - LHN sorted by WS displays irrelevant Report

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: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4314321
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
Action Performed:

Open https://staging.new.expensify.com/
Log into an HT account where there are many correspondences
Create a new Workspace
Click on the Chats icon next to FAB

Expected Result:
If you choose to sort by Workspace, only reports associated with that Workspace should be displayed in the LHN
Actual Result:
LHN sorted by WS displays irrelevant Report
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/cf2ce4ba-fb00-4a01-8172-555d648c41a3
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~012baa25c08b0391cd
Upwork Job ID:<PHONE_NUMBER>580828672
Last Price Increase: 2024-02-14

We think that this bug might be related #wave6-collect-submitters
CC @greg-schroeder

Looks like these are task reports? Doesn't seem to be a blocker

Proposal
Please re-state the problem that we are trying to solve in this issue.
The LHN shows unrelated reports with the workspace-filtered result.
What is the root cause of that problem?
We filter the report here whether it's related to the workspace or not
https://github.com/Expensify/App/blob/634f7666b049aced9f6ac2ae5565508ec07d813e/src/libs/SidebarUtils.ts#L175-L177
If the report is not a policy report, it compares the report participant array with the policy participant array.
https://github.com/Expensify/App/blob/634f7666b049aced9f6ac2ae5565508ec07d813e/src/libs/ReportUtils.ts#L917
So, any report that has the same participant will be shown. However, the policy participant array shouldn't include the current user.
https://github.com/Expensify/App/blob/634f7666b049aced9f6ac2ae5565508ec07d813e/src/pages/home/sidebar/SidebarLinksData.js#L137
But the accountID is undefined because we didn't subscribe to session onyx data.
What changes do you think we should make in order to solve the problem?

Connect with session onyx data
What alternative solutions did you explore? (Optional)
We use withCurrentUserPersonalDetails HOC but I see we don't use the props, maybe the intention is to use currentUserPersonalDetails instead of session, so we can use it instead.
currentUserPersonalDetails?.accountID

Proposal
Please re-state the problem that we are trying to solve in this issue.
Workspace - LHN sorted by WS displays irrelevant Report
What is the root cause of that problem?
The SidebarLinksData component is using the WithCurrentUserPersonalDetails HOC.
https://github.com/Expensify/App/blob/6fb924e9f8f8adc80d3eda2153da5e2f2d409009/src/pages/home/sidebar/SidebarLinksData.js#L303
However, the SidebarLinksData component uses the prop keyword session instead of currentUserPersonalDetails  as the WithCurrentUserPersonalDetails HOC expects.
https://github.com/Expensify/App/blob/6fb924e9f8f8adc80d3eda2153da5e2f2d409009/src/components/withCurrentUserPersonalDetails.tsx#L31-L36
Hence the accountID is empty and policyMemberAccountIDs ends up containing the currentUsetId due to the fact hasParticipantInArray is true.
https://github.com/Expensify/App/blob/6fb924e9f8f8adc80d3eda2153da5e2f2d409009/src/pages/home/sidebar/SidebarLinksData.js#L137
There, the doesReportBelongToWorkspace function forces the task report to be displayed.
https://github.com/Expensify/App/blob/6fb924e9f8f8adc80d3eda2153da5e2f2d409009/src/libs/ReportUtils.ts#L919
What changes do you think we should make in order to solve the problem?

In the  SidebarLinksData component, switch the word session with currentUserPersonalDetails.

Hmm I don't see how the changes in the PR are related to this bug

withCurrentUserPersonalDetails HOC was never providing full session object, only accountID

@hoangzinh can you please take a look?

@hoangzinh my proposal suggested to change the name session to currentPersonalDetails.
We are using the wrong prop name.
Could you kindly confirm?

PR is ready
cc: @hoangzinh

@bernhardoj $500 sent and contract ended!

@hoangzinh $500 sent and contract ended!

All set!


@prisma/client version 2.16.x spams [dotnev][DEBUG] logs

Bug description
After upgrading to version 2.16.x [dotenv][DEBUG] logs started spamming the console with "did not match key" and "overwrite" warnings
[dotenv][DEBUG] did not match key and value when parsing line 32:
[dotenv][DEBUG] did not match key and value when parsing line 37:
[dotenv][DEBUG] did not match key and value when parsing line 40:
[dotenv][DEBUG] did not match key and value when parsing line 43:
[dotenv][DEBUG] did not match key and value when parsing line 47:
[dotenv][DEBUG] "NODE_ENV" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "BUILD_TARGET" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "PORT" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "LOG_LEVEL" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "LOG_DIFFERENCE" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "DEBUG" is already defined in `process.env` and will not be overwritten
...many more

How to reproduce
Upgrade from 2.15.0 to 2.16.x
Have existing DEBUG env variable set to unrelated namespace
Logs spam during nexus schema generation and logs spam during server start
// .env

DEBUG="app*"

Expected behavior

No logs
Prisma information

"prisma": "2.16.1",
"@prisma/client": "2.16.1",
// or
"prisma": "2.16.0",
"@prisma/client": "2.16.0",

Environment & setup

OS:
Database:
Node.js version:
Prisma version:

I can confirm the current spamming, I'll check with my colleague what we want to do 👍

@Jolg42 This is causing log spam (see #5562) because any truthy value causes the dotenv debug to show. I know they use the env DEBUG as an example for setting the config option but it should really be DOTENV_CONFIG_DEBUG=true to enable internal logging... that will allow those of us using the debug package to use the DEBUG env without triggering dotenv logs.
See dotenv environmental config recommendations here: https://github.com/motdotla/dotenv/blob/master/README.md#preload
Please consider changing:
https://github.com/prisma/prisma/blob/19783dc0d381e79d36a68f5f07a50c63abebfde7/src/packages/sdk/src/utils/tryLoadEnvs.ts#L136
to
debug: Boolean(process.env.DOTENV_CONFIG_DEBUG) || undefined,

Thanks @danielmahon, so I just changed the logic to enbable dotenv debug only if process.env.DEBUG.startsWith('prisma') or process.env.DEBUG === '*'
That should get rid of the spam ✔


"Decrypting" an empty string returns encrypted text, instead of plain text empty string.

The following excerpt from the README works fine, so long as the string is not ''
$ dotenvx set HELLO World --encrypt
$ echo "console.log('Hello ' + process.env.HELLO)" > index.js

$ dotenvx run -- node index.js
[dotenvx] injecting env (2) from .env
Hello World

Here is where it goes wrong:
$ dotenvx set HELLO '' --encrypt
$ dotenvx run -- node index.js
HELLO encrypted:46HKO5...<big_long_ciphertext>...Q18Vb

Bash zero strings are impossible, I think, its just zero input? I'm not sure how .env is supposed to handle it, but I assume we do want zero strings to be possible. I don't actually need this. It's just something i noticed and thought you would want to know. I'm using 0.44.0

good catch. yes we definitely want zero strings. will patch up as soon as possible. until then just manually modify.
On Sun, May 26, 2024, at 7:49 AM, happyjamstack wrote:

The following excerpt from the README works fine, so long as the string is not ''
$ dotenvx set HELLO World --encrypt
$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
$ dotenvx run -- node index.js
[dotenvx] injecting env (2) from .env
Hello World
Here is where it goes wrong:
$ dotenvx set HELLO '' --encrypt $ dotenvx run -- node index.js HELLO=encrypted:46HKO5...Q18Vb
Bash zero strings are impossible, I think, its just zero input? I'm not sure how .env is supposed to handle it, but I assume we do want zero strings to be possible.
—
Reply to this email directly, view it on GitHub https://github.com/dotenvx/dotenvx/issues/234, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA6CCFNUIQ5OOZ3MDDHTLZEHZAVAVCNFSM6AAAAABIJ3RUP6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYTONZUHA3DGNI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

https://github.com/dotenvx/dotenvx/pull/236
going out as 0.44.1


Documentation maintenance [ci skip]

Fixing minor spacing stuff and code consistency

Changes Unknown when pulling 836061236cfccb99499811602689bcc250324ba7 on tejashah88:master into ** on alexa-js:master**.

Merged, thanks.


Minor comment and doc updates for 2.2

Overview
Updates some comments and docs that I've been updating as I see them.
Also updates a test icon.

/azp run


Fix crash with race condition of playerPool

There is a race condition crash with issue #58.
I added synchronized scope with operations of [self playerPool]
Since ReactNative's bridge always executes codes in asynchronous mode, this should fix the issue.

Nice!

Yes I've tested this in our app.

I've merged this into unstable.
I will release it at the end of the month.

We're also waiting for this fix :)

This is currently our 2nd most frequent crash: https://sentry.io/share/issue/e4075aec0f8b44d5b48e8d94492f2715/

#476 was about fixing a key value, but also made some changes related to these, which involve running @synchronized(self) around releasing. I think these changes can be made additively to those, though I also want to be careful of deadlocks. I wonder if it would be better to centralize on a single lock object (self) rather than using both.


SAK-30934 Mobile - Clicking on dropdown causes dropdown to appear at top

of screen with white space at bottom
This also solves SAK-30937 "Add" in Folder/item missing top padding

Great!


🐛 [OFFICIAL] Generated Issue: ConnectionTimeoutException

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The API has returned an error:
MongoDB\Driver\Exception\ConnectionTimeoutException
Status code: 13053
Message: No suitable servers found (`serverSelectionTryOnce` set): [connection timeout calling hello on '<IP_ADDRESS>:27017']
Trace: /var/www/jikan-rest/vendor/mongodb/mongodb/src/functions.php on line 487
Expected Behavior
The API should have returned a successful response with data.
Steps To Reproduce
Http Request: `GET /v4/top/anime?page=1
Return error 500
Environment
Brower : Chrome Version 121.0.6167.161 (Build officiel) (64 bits)

Anything else?

Resolved, thanks for reporting. Please re-open the ticket if it occurs again.


Omnichannel Security Roles - Recordings and Transcriptions

This page does not make it clear that any user with the "Omnichannel agent" role can access and view call recordings/transcriptions for the entire organisation. This has information security consequences e.g. GDPR so should be called out clearly in the "Understand roles and their privileges" table.
Effectively any "Omnichannel agent" can listen to any call recording within the environment (if call recording is enabled). This is something I expect only the "Omnichannel supervisor" should be capable of doing by default. It would of course be useful to be able to simply customise the "Omnichannel agent" role to remove recording/transcription read permission however it is not possible to do so.

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

ID: a472ee3d-4ca4-bfcf-2008-4e376203f493
Version Independent ID: 156e001b-25c6-7380-3956-c3b46111585c
Content: Assign roles, enable users for Omnichannel for Customer Service
Content Source: ce/customer-service/add-users-assign-roles.md
Service: dynamics-365-customerservice
GitHub Login: @neeranelli
Microsoft Alias: nenellim

Hello @Dan-Newton, thank you for raising this issue regarding permissions to recordings and transcripts. I am waiting for feedback from the assigned stakeholders and will get back soon as I get to know the action items.
Best regards,
Neeraja


Merge release

This is needed to convince git describe --tags --abbrev=8 to add the 0.3.10 tag. Before this PR HEAD on develop reported
v0.3.9-849-gdf706670, after this merge it reports v0.3.10-493-g0eda7ac2.
Merging the release back into the develop branch would be helpful after each release for downstream packagers like numpy: note the file name is openblas-v0.3.9-452-g349b722d even though it is built off a commit after the 0.3.10 release.

I am not entirely convinced this would work without messing up the develop branch shortly before 0.3.11 :(

Sorry, feel free to close it then, or maybe leave it open as a reminder to merge the release branch back to develop shortly after the release?

Most likely that is just another git feature that I am not really familiar with... but I see we have been there before (#645) with some arguing that only the hash itself should be considered significant when building from develop

In that issue there is this comment, which is an opinion I only partially agree with

Yes you are right, this bug should be closed. In v0.2.9.rc1-679-ga96a4cb only a96a4cb is meaningful, that's how git and git describes works.

That may be how git describe works, but it is not how your users expect git describe --tags to work. After a release, I would expect the active branch to continue after the tag. Is it is a big ask to merge the release branch back into develop for the convenience of downstream packagers after the release is tagged? This PR changes no actual files, it only changes the appearance of tags on branches.

I'm ok with merging back after the release, and I would merge your PR if I had a clear idea how the history of the develop branch would look after its application (i.e. what hash would get tagged as 0.3.10 retroactively, and if git log would still show the expected sequence of commits). With 0.3.9 I am pretty sure the mergeback of the tag must have happened as a side effect of a trivial merge conflict resolution - differing version strings in the (c)makefiles or something like that)

cool thanks. I will close this and try to remember to make sure it is done after the upcoming release. I hope it goes smoothly.


update price Identifier from symbol to new file

See if the token corresponds to the same price as extension or Android

@zhouxl
The price is different with extension 2.6.3.The price of FUSD is different.

It's the same price on API, maybe android and extension are wrong.
https://lilico.app/api/prices

cc: @jaymengxy Please check this issue.
Let's use the API response instead
The hardcode is out of date


Fix PRNGKeyArray.broadcast_to with scalar shape

Should I add a test directly use PRNGKeyArray? Or just test with PRNGKey(will not use PRNGKeyArray unless config set custom prng key, while CI doesn't set this.)

I would probably add the test somewhere near here: https://github.com/google/jax/blob/f8d796939212fd2b3651c10c5e00f2f7503453c2/tests/random_test.py#L1550-L1555
I don't think we test custom_prng on github CI, but we have other test coverage for that that will catch it (and eventually custom_prng will be on by default)


Deprecate/Remove jBullet

We don't have the sourcecode at hand (it's hard to come by) and even then we have noone willing to fix it and improve it. The only worth it has currently is to double check if this is a user problem or a library problem.
Another benefit is that it runs everywhere, where native bullet is compiled for android and desktop, but not for iOS and not for potential web content.

This should be the src: https://github.com/normen/jbullet
But i still agree. it is old and should be deprecated.

Oh, you are right. Then normen managed to find and upload the sourcecode. Then that's correct.

Actually when thinking about web platforms jbullet gains more importance again, there is ammo.js but that would entail writing a complete jme3-bullet wrapper just for that.


BackgroundEstimator Analysis Parameter Class

This introduces an analysis parameter class that plugs into RadClass: BackgroundEstimator. This small class processes gross count rates for each integrated time interval and sorts the set in ascending order of gross count rate magnitude. It then saves to a .csv file a percentage of the smallest count rates with corresponding timestamps.
A few notes:

I have two "less-than-ideal" ways of writing the results to file. One way uses the class destructor __del__ to write to file. This way, the file always is written at the end of an analysis script even if the script crashes. This does, however, require the class to be destructed if it is to be written and analyzed in the same script (something I noticed when trying to write a test case). The alternative is to create a write() method which must be called manually by a user script in order to be reviewed later. Which is better or should both be left in?
The method save_all currently does not work but should be considered. The idea would be to save the timestamps and the spectra rather than the gross count rate. This way, the smallest (in gross count rate terms) spectra could be reviewed in post-analysis.

Did I accidentally rebase incorrectly? There are some files that are listed as "changed" in this PR but main already has those changes adopted...

There is definitely something tangled in the commit history, but it may not matter...

It probably is only an issue because it makes review harder.  We can discuss how to fix this perhaps...


[uart] Increase NCO width

We should increase the NCO width of the uart.
It looks like right now, when the uart is clocked at 24MHz, we are unable to configure the NCO for 2mbps baudrate.
It would be good to enlarge the NCO by another 2~4b, it would give us a bigger range.  (I haven't checked if there would be error rate issues at that value).

I think this already resolved. Closing issue.


Update fastutil to 8.5.12

Updates it.unimi.dsi:fastutil from 8.3.1 to 8.5.12.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "it.unimi.dsi", artifactId = "fastutil" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "it.unimi.dsi", artifactId = "fastutil" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #214.


Continuous Updating of PRF Compatibility Readme for Various Operating Systems and Browsers

I propose that we establish a process for continuously updating the PRF Compatibility section of our README to reflect the compatibility status with various Operating Systems and web browsers. This will help us and users stay informed about the functionality of our project across different OS and browser environments.

Hi. Great product. Is it possible to detect and show the user whether the browser and authenticator are supported?

Thank you very much for your inquiry.
Here you can find all information https://github.com/wwWallet/wallet-frontend#prf-compatibility
First, if you are asking additional information or a new table is included in the README, the answer is we have split the information into two tables: one for OS-browsers and another for OS-authenticators.
If you have seen something that doesn't work or if you've noticed something else, please let us know. We always appreciate feedback and insights that can help us improve our service and documentation.

And yes, there is also a compatibility warning shown if the browser appears to be incompatible.
It is also possible to check if the authenticator is compatible, but the frontend currently doesn't do that. Also, this check can only be done by inspecting the result of creating the passkey (to see if getClientExtensionResults().prf.enabled is present), it cannot be done before creating the passkey.


RuntimeError: GET was unable to find an engine to execute this computation

when run this script
python -W ignore llava/eval/run_vila.py \
    --model-path Efficient-Large-Model/VILA1.5-3b \
    --conv-mode vicuna_v1 \
    --query "<video>\n Please describe this video." \
    --video-file "demo.mp4"

with disable #from tf_utils import flatten, shape_list in VILA/llava/model/multimodal_encoder/image_processor.py
Got the following error:

/envs/vila/lib/python3.10/site-packages/torch/nn/modules/conv.py", line 459, in _conv_forward
    return F.conv2d(input, weight, bias, self.stride,
RuntimeError: GET was unable to find an engine to execute this computation

why do you disable #from tf_utils import flatten, shape_list ?

close due to inactivity. feel free to re-open when necessary.


Preview/1.0.0

:white_check_mark: Build TheIdServer 1.0.2-preview.1+14.build.777 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/3ceeee904c by @aguacongas)


About passing in elasticsearch_config argument for export_table_to_elasticsearch() method

To avoid the Elasticsearch node running in a docker container to publish the container's IP address (which will cause an error because it is not accessible from outside), It may be required to add an Elasticsearch config {'es.nodes.wan.only': 'true'}. Is it possible to add an optional argument elasticsearch_config to export_table_to_elasticsearch()?
https://github.com/broadinstitute/hail-elasticsearch-pipelines/blob/e2a7e08b356ce70af314507908c7df4a9f128d7b/hail_scripts/v02/utils/elasticsearch_client.py#L26

Closing because elasticsearch will be deprecated.


Bump cardano-ledger-specs to include a fix on non-myopic member reward ordering

Issue Number

Overview

[x] I have bumped cardano-ledger-specs to include a fix on non-myopic member reward ordering

Comments

As requested by Darko / Daedalus.

I thought it was cardano-node that needed to have the fix, not us?

You're probably right. It'll likely mess up with the whole build actually... because there would be two different versions in cardano-node and cardano-wallet.

But we could probably fork the node from 1.14.2, fork cardano-ledger-specs from here https://github.com/input-output-hk/cardano-node/blob/1.14.2/stack.yaml#L62, cherry-pick in the fix, and target the resulting cardano-node from the wallet

bors r+

@KtorZ what about also to update matrix in README ?

bors r+

Unfortunately stack-to-nix does not support recursive snapshot URLs

:cry: :disappointed:

bors retry

bors r+

bors r+

bors r+

bors try


NavigationMode in 1.1.13p Branch

@JerryNixon -- I was testing the Hamburger project with 13p codebase and noticed that NavigationMode detection is incorrect on Back navigation.
Test scenario

Run the project in debug mode (refs to Template10 Library and Template10.Mobile projects, i.e., delete 1.1.12 NuGet package ref);
Navigate to another page (Settings or DetailPage);
Set a Break in OnNavigatedToAsync nav event handler in MainPageViewModel.cs to observe the value for mode;
Navigate back to the MainPage/Home page.

Expected value:  Back
Actual value:      New

I was not able to reproduce this in our app with current 1.1.13p bits. Is it still reproduceable on your code, @dg2k ?

Had similar problems with 1.1.13p in my project:

mode was "New" instead of "Back"
but also the "parameter" was wrong: I use a string there, but what I got instead of my expected string was
{"Type":"System.String, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a","Data":"\"EXPECTED_STRING\""}

going back to 1.1.12 solved the problem. But I had to delete the 1.1.13p nuget package manually - as long as it was there the problem persisted even when referencing only 1.1.12.

Thankyou


url show 'undefind' , when preview

When using  'vuese serve --open'  command, the address bar address is  'http://<IP_ADDRESS>:5000/#/undefind'.
I found that in the function which is getFirstPath , the reduce method of the array has no return value.So firstRoute is  undefind.

@yujiaqi
This error is usually due to the . /website does not generate a components directory

Check the ./website/components directory under your project to see if it's empty or doesn't exist at all
Provide a screenshot of the vuese gen execution in your project

Normally, when you execute vuese gen
.
├── src
│   ├── components
│   │   └── main.js
│   └── lib
└── website
    ├── components
    │   └── MyComponent2.md
    └── index.html

Then run vuese serve ,  it will output this 👇  in terminal
✨ Server running at http://<IP_ADDRESS>:5000/#/components/MyComponent2

Then it will open the link  like this


Add Motionsense DetectionMode

Motion Sense has to do with detecting creatures that moved in the previous round, which isn't something the system tracks. It's less potent that simply being able to detect anything and everything.

Fair enough. Let's close this then.


Cannot search in :tools gui

You cannot search in the :tools gui, it's not directly an issue, but it's inconvenient in places with lots of tools.

Would be nice if tools would also list all the tools the player currently has?

No, there's a :viewtools command specifically for that. The :tools gui just shows ones that can be given to the player using :give

I'll think about adding a search to it, currently there isn't one because the code for the gui isn't in its own module, instead it's sent from the server (in the command function) over to the client as a list of things to generate and the events to attach to them for the window gui.


[nl] add exporting charts for nl

allow downloading svg and csv data for each chart in a tile

some bug fixes along the way:

fix data fetch for bivariate tile (param was missing a plural)
fix "download chart image" only showing up the second time the export button is clicked (here and place charts)

will merge this in first -- we can fix in followups!


Deploy on a non-local architecture

This could be a k8s cluster, remote box, or multiple remote machines

This has also gone away in #172


arrange text diagonally

Hello can i arrange a text diagonally

similar to this is jack in the image

Look at the demo page for some examples:
examples/pptxgenjs-demo.html

Also see the rotate option for Shapes and Lines.
Shape Options


Make queries pause()able

It should be possible to pause an incoming data stream, e.g. the query object should cease emitting row/field/whatever events and the tcp connection to the mysql server should be put on hold too.
Case: a project I'm working on has a database with >800k filenames that I need to walk through and perform some file operations on those files. Because file and db operations are asynchronous, node-mysql will spit out a new row while the file operations associated with previous rows are still running. So I end up with way too may callbacks/stacks floating around, which causes out-of-memory errors and extreme slowness.
Currently I'm using a hack that 'just' pauses the underlying tcp stream; that works, but after I pause the tcp stream I still receive 500-some row events before it gets silent. I guess those rows must be buffered up somewhere.
I think the most elegant solution would be to have a pause() and a resume() method on Query objects. A caveat would be that when doing something like ...
var q1 = client.query('SELECT something');
var q2 = client.query('SELECT something');
q2.pause();

... q1 should not be paused, so bluntly pausing the tcp stream when q2.pause() is called is not the way to go.
(IMHO it would be even cooler if we could pause the tcp stream automatically when appropriate, but I don't think there currently is a reliable way to measure stack / event loop pressure within node)

felixge: Are you still working on that feature?

felixge: Are you still working on that feature?

Yes, two awesome companies (HolidayExtras and newscope Gmbh) are sponsoring me to work on my refactoring from March 7 - 14, after that pausing should be possible.


Update CORS settings for referer headers in README

If you have a serviceWorker for example that's doing the request you need to have the referer attribute in the CORS headers.

Thanks!


Add the ability to return a path by template type-checking-exempt-modules

Add the ability to return a path by template
type-checking-exempt-modules = apps.*.choices, *.choices

For development, we use Django, which consists of several applications. For convenience and to reduce cyclic imports, choices were moved to a separate module, as a result of which the project structure turned out to be something like this:
...
apps
 +-  app_1
        +-  ...
        +- choices.py
        +- typengs.py
        +-...
 +-  app_2
        +-  ...
        +- choices.py
        +- typengs.py
        +-...
...

And now you have to register each module separately.
type-checking-exempt-modules =
   ...
   apps.app_1.choices,
   apps.app_2.choices,
   apps.app_1.typengs,
   apps.app_2.typengs,
   ...

But it should look like this.
type-checking-exempt-modules =
   ...
   apps.*.choices,
   apps.*.typengs,
   ...

I think it can be done like this.
if (
    isinstance(node, ast.Import)
    and any(
         {exempt_module for exempt_module in self.exempt_modules if re.match(name_node.name, exempt_module)}
    )
):
     return

I've also seen fnmatch used for this - not sure which is better yet, but just remembered :slightly_smiling_face:
I think this would be a nice feature to add. Would you be interested in creating a PR for it?

#155

That was fast @KozyrevIvan! Thanks :clap:


BUGFIX: in-page navigation links continue showing over header.

Changes in this PR:
So, this turned out to be a horrible non-deterministic thing, so it took a while both to replicate and to track down. We use IntersectionObservers to test whether either the page header or footer is visible in the viewport, and hide the in page navigation links when that is the case. However, by using two seperate observers, we opened the door to a concurrency bug whereby if the 'footer' observer was called after the 'header' one, the links would be set to 'show', over the top of the header. Thankfully, IntersectionObservers can apply to multiple elements, so i've refactored to use a single observer on both elements which fixes the problem.
Trello card / Rollbar error (etc)
https://trello.com/c/NSGBXPgT/1041-back-to-top-skip-to-end-navigation-covers-banner-after-you-use-back-to-the-top-navigation-at-the-end-of-the-document

Codecov Report

Merging #400 (29adeab) into main (1502200) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #400   +/-   ##
=======================================
  Coverage   76.40%   76.40%
=======================================
  Files          12       12
  Lines         589      589
  Branches       38       38
=======================================
  Hits          450      450
  Misses        128      128
  Partials       11       11

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


"report" subcommand on CLI?

This tool has been extremely useful, thanks! By far the simplest to get working tool for the instrument-coverage (I had some trouble getting grcov to work)
One thing I think could be improved is the command line args - mainly about generating reports (where quite a lot of the arguments are mutually exclusive, e.g --no-run and any of the arguments like --lib, --html and --output-file`)
I think to steal some ideas from coverage.py could work, specifically to have a report subcommand.
Main downside of this is obviously a common "run tests and open report" usage becomes two commands, so instead of just cargo llvm-cov --html --open it would become cargo llvm-cov && cargo llvm-cov html --open.
However the upsides are:

the available options become smaller and more organised
maybe be a tiny bit more intuitive to use (e.g first few times I accidentally reran my testsuite because I assumed cargo llvm-cov --open would only open the report)
If gathering and reporting are two separate actions, it would be (if it's not already?) possible to gather coverage from multiple runs and report on them in one - e.g cargo llvm-cov test && cargo llvm-cov run --append-cov && cargo llvm-cov run --example blah --append-cov && cargo llvm-cov html which would run the tests and two executable, and generate a report of the combined coverage

I imagine the help output could look something like:

Example help output
$ cargo llvm-cov --help
cargo-llvm-cov

Cargo subcommand to easily use LLVM source-based code coverage (-Z instrument-coverage).

Use -h for short descriptions and --help for more details.

USAGE:
    cargo llvm-cov [OPTIONS] [-- <ARGS>...] [SUBCOMMAND]

ARGS:
    <ARGS>...
            Arguments for the test binary

GLOBAL OPTIONS:
    -h, --help
            Print help information

    -V, --version
            Print version information

    -v, --verbose
            Use verbose output

            Use -vv (-vvv) to propagate verbosity to cargo.

    --color <WHEN>
            Coloring [possible values: auto, always, never]

    --manifest-path <PATH>
            Path to Cargo.toml

    --frozen
            Require Cargo.lock and cache are up to date

    --locked
            Require Cargo.lock is up to date

    --offline
            Run without accessing the network

    -Z <FLAG>...
            Unstable (nightly-only) flags to Cargo

SUBCOMMANDS:
    clean
            Remove artifacts that cargo-llvm-cov has generated in the past

    help
            Print this message or the help of the given subcommand(s)

    report
        --ignore-filename-regex <PATTERN>
            Skip source code files with file paths that match the given regular expression

        --no-report
            Run tests, but don't generate coverage report

        --no-run
            Generate coverage report without running tests

        json <optional output file>
            Export coverage data in "json" format

            If output file is not specified, the report will be printed to stdout.

            This internally calls `llvm-cov export -format=text`. See
            <https://llvm.org/docs/CommandGuide/llvm-cov.html#llvm-cov-export> for more.

        lcov <optional output file>
            Export coverage data in "lcov" format

            If output file is not specified, the report will be printed to stdout.

            This internally calls `llvm-cov export -format=lcov`. See
            <https://llvm.org/docs/CommandGuide/llvm-cov.html#llvm-cov-export> for more.

        text <optional output directory>
            Generate coverage report in "text" format

            This internally calls `llvm-cov show -format=text`. See
            <https://llvm.org/docs/CommandGuide/llvm-cov.html#llvm-cov-show> for more.

        html <optional target directory>
            Generate coverage report in "html" format

            This internally calls `llvm-cov show -format=html`. See
            <https://llvm.org/docs/CommandGuide/llvm-cov.html#llvm-cov-show> for more.

        summary
            Display only summary information for each file in the coverage data

    run
        --bin <NAME>...
            Test only the specified binary

    test
        --doctests
            Including doc tests (unstable)

            This flag is unstable. See <https://github.com/taiki-e/cargo-llvm-cov/issues/2> for
            more.

        --no-fail-fast
            Run all tests regardless of failure

        -q, --quiet
            Display one character per test instead of one line

        --lib
            Test only this package's library unit tests

        --bins
            Test all binaries

        --example <NAME>...
            Test only the specified example

        --examples
            Test all examples

        --test <NAME>...
            Test only the specified test target

        --tests
            Test all tests

        --bench <NAME>...
            Test only the specified bench target

        --benches
            Test all benches

        --all-targets
            Test all targets

        --doc
            Test only this library's documentation (unstable)

            This flag is unstable because it automatically enables --doctests flag. See
            <https://github.com/taiki-e/cargo-llvm-cov/issues/2> for more.

        -p, --package <SPEC>...
            Package to run tests for

        --workspace
            Test all packages in the workspace [aliases: all]

        --exclude <SPEC>...
            Exclude packages from the test

        -j, --jobs <N>
            Number of parallel jobs, defaults to # of CPUs

        --release
            Build artifacts in release mode, with optimizations

        --profile <PROFILE-NAME>
            Build artifacts with the specified profile

        --features <FEATURES>...
            Space or comma separated list of features to activate

        --all-features
            Activate all available features

        --no-default-features
            Do not activate the `default` feature

        --target <TRIPLE>
            Build for the target triple

            When this option is used, coverage for proc-macro and build script will not be displayed
            because cargo does not pass RUSTFLAGS to them.

Thanks for the suggestion!

Main downside of this is obviously a common "run tests and open report" usage becomes two commands, so instead of just cargo llvm-cov --html --open it would become cargo llvm-cov && cargo llvm-cov html --open.

I think it would be okay to add a report subcommand for users who want to perform various actions on the report, but there is no need to break the existing one.

where quite a lot of the arguments are mutually exclusive, e.g --no-run and any of the arguments like --lib, --html and --output-file

Most of the mutual exclusivity issues should be fixed in https://github.com/taiki-e/cargo-llvm-cov/issues/60

If gathering and reporting are two separate actions, it would be (if it's not already?) possible to gather coverage from multiple runs and report on them in one

This is already available. readme says:

You can merge the coverages generated under different test conditions by using --no-report and --no-run.
cargo llvm-cov clean --workspace # remove artifacts that may affect the coverage results
cargo llvm-cov --no-report --features a
cargo llvm-cov --no-report --features b
cargo llvm-cov --no-run --lcov

Added in 0.5.0.


Add context menu item - run now

In cases the auto search doesn't find the HTML elements that are part of modular popup
having the option to run the search again manually from the context menu will be very helpfull

Checkout manual mode https://getautoclicker.com/docs/4.x/config-settings/start/

@github-rashelbach ,
Can you provide your use case with example so we can work on it.


Privacy page not complete

On the privacy page of the doc of Gateway (for team),
you explain how long you kept Data but not why and if you do something with it :
Cloudflare Gateway logs are stored for a varying period of time based on the service used:

DNS logs corresponding to DNS filtering: up to six months
HTTP logs corresponding to HTTP traffic filtering: up to 30 days
Teams Free users will have the visibility into the last 24 hours of DNS activity logs. Teams Standard and Enterprise users have 30 days of visibility into both DNS and HTTP activity logs.

source : https://developers.cloudflare.com/gateway/privacy

hi @Macqael, thank you for raising this. We're working to improve the Analytics section of our new Cloudflare for Teams documentation, so keep an eye on this page for upcoming improvements. Thanks again!

hi @Macqael, thank you for raising this. We're working to improve the Analytics section of our new Cloudflare for Teams documentation, so keep an eye on this page for upcoming improvements. Thanks again!


Fix for Issue #800

@halatmit
#800
When ActivityStarter is called without any action information, the intent is pointed to an action that requires permission and is denied that permission. It results in a runtime error which gives little information for users.

I added another error message that replaces this runtime error to inform the user that no information was found in ActivityStarter. It seems that the default action is android.intent.action.MAIN if no information was enter in the Action properties for the ActivityStarter.
AIA and APK to reproduce error.

LGTM

@chenglonkhin MERGED into UCR


YT2009 patched apps do not work on older android (5.x and earlier) for no apparent reason.

@ftde0
These don't work on older android versions. NO REASON WHY.
https://www.reddit.com/r/oldyoutubelayout/comments/1boflcm/my_244_youtube_patch_doesnt_work_on_44_android/
Update it to support older android. No sites will be affected. Not even the apps.

how are they supposed to work if the instance used doesn't work in the first place?

oops, wrong instance. What I meant is that it didn't work because it is by the browser agent (from android).

a well configured yt2009 instance along with a good patch do work on older android versions. that was also taken into consideration when working on mobile app support.
consider setting ALL urls you change to HTTP, or use a proxy to see whether the requests are made correctly.
following screenshots are from android 2.3.5.

Thanks for the tip!


Update AbstractReport.java

Don't change JVM Locale
Fix for https://issues.jenkins-ci.org/browse/JENKINS-15736 based on evernat suggested fix

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


gitlab: read GITLAB_LOG_PATH in json_logger too

Description of changes
Fixes #264392.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

I've updated to a more recent version of gitlab (*cough* security vulnerabilities) and this appears to not be necessary anymore. Very weird.


Tab completion for VM extension names is incorrect

Actual output:
$ az vm extension show -g derek1 --vm-name dvmencrypt -n <TAB>
dvmencrypt/AzureDiskEncryptionForLinux               dvmencrypt/VMBackupForLinuxExtension                 swarm-master-80E5A796-0/linuxdiagnostic
dvmencrypt/Microsoft.Insights.VMDiagnosticsSettings  swarm-master-80E5A796-0/configuremaster

Expected output:
$ az vm extension show -g derek1 --vm-name dvmencrypt -n <TAB>
AzureDiskEncryptionForLinux               VMBackupForLinuxExtension                 linuxdiagnostic
Microsoft.Insights.VMDiagnosticsSettings  configuremaster

The completer for the vm_extension_name parameter of vm extension command is defined as completer=get_resource_name_completion_list('Microsoft.Compute/virtualMachines/extensions') which looks correct.
However, ARM returns vm extension names prefixed by the vm name (see below) which causes tab completion to show results in the format <vm_name>/<extension_name>.
$ az resource list -g derek1 --query "[?type=='Microsoft.Compute/virtualMachines/extensions'].{name:name, type:type}"
[
  {
    "name": "dvmencrypt/AzureDiskEncryptionForLinux",
    "type": "Microsoft.Compute/virtualMachines/extensions"
  },
  {
    "name": "dvmencrypt/Microsoft.Insights.VMDiagnosticsSettings",
    "type": "Microsoft.Compute/virtualMachines/extensions"
  },
  ...
]

Possible solution, don't use the generic get_resource_name_completion_list method for this completer and instead create a method that removes the vm name prefix.

I believe that the root cause cause is that the instance of the extension associated with the VM does in fact have a name. Consider the ability to apply the script extension multiple times.


New version: Unity.Unity.CN.2021 version 2021.3.44f1c1

Created by 🥟 Dumplings in workflow run #8840.

Log
Updated: 2021.3.43f1c1 → 2021.3.44f1c1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

This package installs and launches normally in a Windows 10 VM.


Trouble installing and getting stuff running

hello, I have been trying to install pajbot. I think I got everything working. the local ip for the bot goes to Nginx but when added bot_login it wont work or error 502

Link to the nginx/site-enabled file https://gist.github.com/jkalter24/0ea42fcb20ba8da8ab9a8f813be99a30
I may just try reinstalling tommorow.

Hi, thanks for providing those details. Could you also post the output of journalctl -efu pajbot-web@thecyberzone, e.g. as a GitHub Gist. This would include the reason as to why the web service exited with an error code.

https://gist.github.com/jkalter24/44d58b4e76ab806552267a178ad2c2b2

Have you run the ./scripts/venvinstall.sh script when you cloned the repo?

Yes im pretty sure

Have you run the ./scripts/venvinstall.sh script when you cloned the repo?

Yes I think I did

Have you run the ./scripts/venvinstall.sh script when you cloned the repo?

Yes I think I did

Can you try running it again? One of the errors
Failed to locate executable /opt/pajbot/venv/bin/uwsgi: No such file or directory
says it can't find the binary in your virtual environment directory. This should be installed if you've run ./scripts/venvinstall.sh in the /opt/pajbot directory

I ran it again

Try these commands in this order:
sudo systemctl restart pajbot@thecyberzone
sudo systemctl restart pajbot-web@thecyberzone

if that doesn‘t get things running, i‘d be interested in the journalctl logs of pajbot@thecyberzone as well as pajbot-web@thecyberzone.

for the pajbot@thecyberzone https://gist.github.com/jkalter24/c19c9182aad7d67e3940d803e210b2a2
for pajbot-web@thecyberzone https://gist.github.com/jkalter24/42c3c80a24e261839f6c3817f73f5d7c

Try these commands in this order:
sudo systemctl restart pajbot@thecyberzone
sudo systemctl restart pajbot-web@thecyberzone

if that doesn‘t get things running, i‘d be interested in the journalctl logs of pajbot@thecyberzone as well as pajbot-web@thecyberzone.

for the pajbot@thecyberzone https://gist.github.com/jkalter24/c19c9182aad7d67e3940d803e210b2a2
for pajbot-web@thecyberzone https://gist.github.com/jkalter24/42c3c80a24e261839f6c3817f73f5d7c

From the logs you posted, it looks like you missed this step: https://github.com/pajbot/pajbot/tree/master/install-docs
and no, I don‘t think you need a full reinstall. Try doing that linked step/command above, then restart both in that order again and if things don‘t work i‘d be interested in the log outputs again.

From the logs you posted, it looks like you missed this step: https://github.com/pajbot/pajbot/tree/stable/install-docs#create-a-database-schema
and no, I don‘t think you need a full reinstall. Try doing that linked step/command above, then restart both in that order again and if things don‘t work i‘d be interested in the log outputs again.

ERROR:  schema "pajbot1_thecyberzone" already exists

sudo systemctl restart pajbot-web@thecyberzone

https://gist.github.com/jkalter24/be5947c0d2ab8de45e309c961a9cf745

From the logs you posted, it looks like you missed this step: https://github.com/pajbot/pajbot/tree/stable/install-docs#create-a-database-schema
and no, I don‘t think you need a full reinstall. Try doing that linked step/command above, then restart both in that order again and if things don‘t work i‘d be interested in the log outputs again.

https://gist.github.com/jkalter24/be5947c0d2ab8de45e309c961a9cf745 the log the for the pajbot@thecyberzone
https://gist.github.com/jkalter24/1bbfc27ce4a321c777b0f10ecafe7297 pajbot-web@thecyberzone

What does it say under db = in your configs/thecyberzone.ini?

it was still set to streamer_name and I just changed it Still wont start
pajbot@thecyberzone is  https://gist.github.com/jkalter24/bc193a920f492fd3b27c7c95e858b89a
and pajbot-web@thecyberzone is https://gist.github.com/jkalter24/68222bcdba81e7fe7c146de68314b885

What does it say under db = in your configs/thecyberzone.ini?

When running the ngix check command https://gist.github.com/jkalter24/5827d00174e3e8cc9a5d482e6c5785f8
when running the log for pajbot@thecyberzone I get this https://gist.github.com/jkalter24/9ce45e5fa6087a9d107ac4b08514011e

Do you perchance have more than one file in /etc/nginx/sites-enabled?

Do you perchance have more than one file in /etc/nginx/sites-enabled?
(If not - I couldn‘t see anything wrong with the nginx file you posted above)

It appears there are 3 there. oops how should I proceed

Depends on which domain you want the bot website to run on - bot.thecyberzone.online or thecyberzone.online? Delete the one that you don't want. If you want one of them to redirect to the other, I can help you set that up later.
Afterwards, sudo nginx -t should say the config is okay, hopefully - you should then restart nginx (sudo systemctl restart nginx) and I'm hoping your website will work then. You can then do the authorization step from the instructions and then your bot should come online in chat as well.

Still no luck. The domain is not working. I get this error for pajbot@thecyberzone https://gist.github.com/jkalter24/b05093e89caadef2004443cc24b8edeb

Yes, that error is normal and will keep appearing until you get the website running and authorize the bot. I was hopeful the website would start since the pajbot-web logs showed no error.
And now, do you want the bot to run on bot.thecyberzone.online or thecyberzone.online. If it‘s the former, you‘re missing a DNS CNAME entry for that. If it‘s the latter, we have some kind of misconfiguration making it so i get infinite redirects when i visit that site. Let me know if you need help with any of these things.

Yes, that error is normal and will keep appearing until you get the website running and authorize the bot. I was hopeful the website would start since the pajbot-web logs showed no error.
And now, do you want the bot to run on bot.thecyberzone.online or thecyberzone.online. If it‘s the former, you‘re missing a DNS CNAME entry for that. If it‘s the latter, we have some kind of misconfiguration making it so i get infinite redirects when i visit that site. Let me know if you need help with any of these things.

I want it to be bot.thecyberzone.online I want to use the main domain to redirect to my twitch or my website

Yes, in that case, would you mind going to CloudFlare and taking a screenshot of your DNS entries and posting that here? You can just paste images into the text box or use the image upload button above the textbox.

Yes, in that case, would you mind going to CloudFlare and taking a screenshot of your DNS entries and posting that here? You can just paste images into the text box or use the image upload button above the textbox.

Add a CNAME for bot that points to thecyberzone.online.

Add a CNAME for bot that points to thecyberzone.online, similar to how there‘s one for www already

What's the output of sudo systemctl status nginx? Is sudo nginx -t okay now?

sudo systemctl status nginx output
and yes nginx -t shows up that its ok

Do I need to point my ip to anything or portfoward? or did I mess something up in a config

Can you go ahead and temporarily disable the orange cloud (proxying) in the DNS section of CloudFlare for all the three entries that have it? I'm trying to figure out why your server is responding with a 404 Not Found even though from the things you've shown me I'd expect the pajbot website to show up.

From what I can tell you've got port 443 blocked in a firewall or, if you're using your home internet, it's not port-forwarded. The server is responding on port 80 but on port 443 the connection is refused.

From what I can tell you've got port 443 blocked in a firewall or, if you're using your home internet, it's not port-forwarded. The server is responding on port 80 but on port 443 the connection is refused.

I just port fowarded 443

I'm not able to access the website via https://bot.thecyberzone.online, with the same error as before (connection refused).  However since you seem to be able to access it yourself you should now be able to perform the authorization step (visit https://bot.thecyberzone.online/bot_login)

I'm not able to access the website via https://bot.thecyberzone.online, with the same error as before (connection refused). However since you seem to be able to access it yourself you should now be able to perform the authorization step (visit https://bot.thecyberzone.online/bot_login) - see also https://github.com/pajbot/pajbot/tree/master/install-docs#authenticate-the-bot

Done. Should I try doing this again? https://github.com/pajbot/pajbot/blob/master/install-docs/certbot-with-cloudflare/README.md

Some thing you can do to double-check your setup is correct:

Visit https://ipinfo.io/ - is the IP address shown there identical to the one you set in CloudFlare?
Is the port forward in your router pointing to the correct local IP adress (i.e. you should have a TCP port forward for port 80 and 443 pointing to the same local IP that you're entering into your browser to access the website).

Yes, you'll have to change that A record then. I'm hopeful that this was the problem and your website will be reachable afterwards.

Yes, you'll have to change that A record then. I'm hopeful that this was the problem and your website will be reachable afterwards.

Changed the record no luck.

Pajbot used to have a song request system, but we removed it because better alternatives exist (e.g. streamelements songrequest, https://www.queup.net/ , streamlabs probably has an equivalent as well, etc.), and because nobody wanted to invest the work to keep it updated and make it good.
Since your website appears to be working now, you can try re-enabling the orange cloud/CloudFlare proxying in the CloudFlare DNS settings page.
It sounds like you also managed to get the bot working in chat then? Does it respond to commands? In that case I‘d like to close this issue.


Show the iOS version in the app settings

Anytime has an About page with details about the app. This is pretty useful, and it would be great to bring this to Bookmarks.

Done in #247.


Join airdrop please

I'm trying to join the Stellar airdrop for Keybase, and when I get to the screen with 3 checkmarks it says I qualify, but when I click through, it says I am not qualified.

I'm hoping to resolve this before the Nov 15 airdrop, please let me know if there is something else I need to complete or do in order to qualify.
my log id: 7862ad60487067732cc4ed1c
Thanks!!

I have the same problem. Any Idea on how to solve it?

I have the same problem too. I don't know how to solve this please help me solve this before 15 Nov.