text:
Postgresql password

Hi, am pretty new to Saltcorn, thanks for the great Program!
I made an Application on a virtual machine with Ubuntu... i had to do a manual install, since that was
the only thing that worked for me... I have one qestion regarding the Postgres Database though:
since it was created automatically, and i would like to to certain CLI operations.  What is the password
or if it is random... how would i find out?
Thanks for every bit of help!

Hi, I think Potgress doesn't have any password to access the admin by CLI. You type psql into the terminal and it takes you into the administrator

I'm always typing:
sudo -u postgres psql

Thanks for the answers… I was thinking when the saltcorn-cli is installed in will ask for a password to connect to an instance. I have to try it
Thanks again

repo: saltcorn/saltcorn


text:
Python ImportError due to incorrect zeromq dependency in the SaltStack-provided python-zmq package

Summary
The SaltStack-provided python-zmq package should depend on the SaltStack-provided zeromq package.  Otherwise, YUM thinks zeromq3 from EPEL satisfies python-zmq's dependencies in scenarios where one is upgrading from the EPEL-provided Salt packages to the SaltStack-provided ones.
Steps to Reproduce

Perform a minimal installation of the latest CentOS 7 release.

Enable EPEL (yum -y install epel-release).

Install the Salt Minion from EPEL (yum -y install salt-minion && systemctl start salt-minion).

Accept the minion key on the Salt Master and apply the salt.pkgrepo SLS from salt-formula.

Upgrade the system (yum -y upgrade); this will replace python-zmq 14.3.1-1.el7 from EPEL with python-zmq 15.3.0-2.el7 from the SaltStack repo.  It will not upgrade zeromq3 from EPEL, nor will it install zeromq from the SaltStack repo.

Check the minion-master connection (salt-call test.ping), which will fail with the following error:

unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
[ERROR   ] An un-handled exception was caught by salt's global exception handler:
ImportError: libzmq.so.5: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/bin/salt-call", line 11, in <module>
    salt_call()
  File "/usr/lib/python2.7/site-packages/salt/scripts.py", line 400, in salt_call
    client.run()
  File "/usr/lib/python2.7/site-packages/salt/cli/call.py", line 47, in run
    caller = salt.cli.caller.Caller.factory(self.config)
  File "/usr/lib/python2.7/site-packages/salt/cli/caller.py", line 79, in factory
    return ZeroMQCaller(opts, **kwargs)
  File "/usr/lib/python2.7/site-packages/salt/cli/caller.py", line 291, in __init__
    super(ZeroMQCaller, self).__init__(opts)
  File "/usr/lib/python2.7/site-packages/salt/cli/caller.py", line 102, in __init__
    self.minion = salt.minion.SMinion(opts)
  File "/usr/lib/python2.7/site-packages/salt/minion.py", line 793, in __init__
    lambda: self.eval_master(self.opts, failed=True)
  File "/usr/lib64/python2.7/site-packages/tornado/ioloop.py", line 444, in run_sync
    return future_cell[0].result()
  File "/usr/lib64/python2.7/site-packages/tornado/concurrent.py", line 214, in result
    raise_exc_info(self._exc_info)
  File "/usr/lib64/python2.7/site-packages/tornado/gen.py", line 230, in wrapper
    yielded = next(result)
  File "/usr/lib/python2.7/site-packages/salt/minion.py", line 697, in eval_master
    pub_channel = salt.transport.client.AsyncPubChannel.factory(self.opts, **factory_kwargs)
  File "/usr/lib/python2.7/site-packages/salt/transport/client.py", line 161, in factory
    import salt.transport.zeromq
  File "/usr/lib/python2.7/site-packages/salt/transport/zeromq.py", line 36, in <module>
    import zmq.error
  File "/usr/lib64/python2.7/site-packages/zmq/__init__.py", line 56, in <module>
    from zmq import backend
  File "/usr/lib64/python2.7/site-packages/zmq/backend/__init__.py", line 40, in <module>
    reraise(*exc_info)
  File "/usr/lib64/python2.7/site-packages/zmq/backend/__init__.py", line 27, in <module>
    _ns = select_backend(first)
  File "/usr/lib64/python2.7/site-packages/zmq/backend/select.py", line 27, in select_backend
    mod = __import__(name, fromlist=public_api)
  File "/usr/lib64/python2.7/site-packages/zmq/backend/cython/__init__.py", line 6, in <module>
    from . import (constants, error, message, context,
ImportError: libzmq.so.5: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/bin/salt-call", line 11, in <module>
    salt_call()
  File "/usr/lib/python2.7/site-packages/salt/scripts.py", line 400, in salt_call
    client.run()
  File "/usr/lib/python2.7/site-packages/salt/cli/call.py", line 47, in run
    caller = salt.cli.caller.Caller.factory(self.config)
  File "/usr/lib/python2.7/site-packages/salt/cli/caller.py", line 79, in factory
    return ZeroMQCaller(opts, **kwargs)
  File "/usr/lib/python2.7/site-packages/salt/cli/caller.py", line 291, in __init__
    super(ZeroMQCaller, self).__init__(opts)
  File "/usr/lib/python2.7/site-packages/salt/cli/caller.py", line 102, in __init__
    self.minion = salt.minion.SMinion(opts)
  File "/usr/lib/python2.7/site-packages/salt/minion.py", line 793, in __init__
    lambda: self.eval_master(self.opts, failed=True)
  File "/usr/lib64/python2.7/site-packages/tornado/ioloop.py", line 444, in run_sync
    return future_cell[0].result()
  File "/usr/lib64/python2.7/site-packages/tornado/concurrent.py", line 214, in result
    raise_exc_info(self._exc_info)
  File "/usr/lib64/python2.7/site-packages/tornado/gen.py", line 230, in wrapper
    yielded = next(result)
  File "/usr/lib/python2.7/site-packages/salt/minion.py", line 697, in eval_master
    pub_channel = salt.transport.client.AsyncPubChannel.factory(self.opts, **factory_kwargs)
  File "/usr/lib/python2.7/site-packages/salt/transport/client.py", line 161, in factory
    import salt.transport.zeromq
  File "/usr/lib/python2.7/site-packages/salt/transport/zeromq.py", line 36, in <module>
    import zmq.error
  File "/usr/lib64/python2.7/site-packages/zmq/__init__.py", line 56, in <module>
    from zmq import backend
  File "/usr/lib64/python2.7/site-packages/zmq/backend/__init__.py", line 40, in <module>
    reraise(*exc_info)
  File "/usr/lib64/python2.7/site-packages/zmq/backend/__init__.py", line 27, in <module>
    _ns = select_backend(first)
  File "/usr/lib64/python2.7/site-packages/zmq/backend/select.py", line 27, in select_backend
    mod = __import__(name, fromlist=public_api)
  File "/usr/lib64/python2.7/site-packages/zmq/backend/cython/__init__.py", line 6, in <module>
    from . import (constants, error, message, context,
ImportError: libzmq.so.5: cannot open shared object file: No such file or directory

Workaround
Either downgrade the python-zmq package, which reverts to the version provided by EPEL, or install the zeromq package from the SaltStack repo.
Supplementary Information
Salt Version Report Post-Upgrade
This is without either of the above workarounds applied:
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
unable to execute gcc: No such file or directory
Salt Version:
           Salt: 2018.3.2

Dependency Versions:
           cffi: 1.6.0
       cherrypy: Not Installed
       dateutil: 1.5
      docker-py: Not Installed
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: Not Installed
         Jinja2: 2.7.2
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: 0.28.2
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.5.6
   mysql-python: Not Installed
      pycparser: 2.14
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: Not Installed
         Python: 2.7.5 (default, Jul 13 2018, 13:06:57)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: Not Installed
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: Not Installed

System Versions:
           dist: centos 7.5.1804 Core
         locale: UTF-8
        machine: x86_64
        release: 3.10.0-862.9.1.el7.x86_64
         system: Linux
        version: CentOS Linux 7.5.1804 Core

python-zmq Package Details
The SaltStack version of python-zmq appears to be correctly installed:
Name        : python-zmq
Version     : 15.3.0
Release     : 2.el7
Architecture: x86_64
Install Date: Fri 03 Aug 2018 06:02:52 PM EAT
Group       : Development/Libraries
Size        : 1535098
License     : LGPLv3+ and ASL 2.0 and BSD
Signature   : RSA/SHA1, Thu 21 Jun 2018 09:25:08 PM EAT, Key ID 0e08a149de57bfbe
Source RPM  : python-zmq-15.3.0-2.el7.src.rpm
Build Date  : Thu 21 Jun 2018 09:07:15 PM EAT
Build Host  : 3fb2f9acdd3e477286bbd24e01b64ddb
Relocations : (not relocatable)
URL         : http://www.zeromq.org/bindings:python
Summary     : Software library for fast, message-based applications
Description :
The 0MQ lightweight messaging kernel is a library which extends the
standard socket interfaces with features traditionally provided by
specialized messaging middle-ware products. 0MQ sockets provide an
abstraction of asynchronous message queues, multiple messaging
patterns, message filtering (subscriptions), seamless access to
multiple transport protocols and more.

This package contains the python bindings.
/usr/lib64/python2.7/site-packages/pyzmq-15.3.0-py2.7.egg-info
/usr/lib64/python2.7/site-packages/pyzmq-15.3.0-py2.7.egg-info/PKG-INFO
/usr/lib64/python2.7/site-packages/pyzmq-15.3.0-py2.7.egg-info/SOURCES.txt
/usr/lib64/python2.7/site-packages/pyzmq-15.3.0-py2.7.egg-info/dependency_links.txt
/usr/lib64/python2.7/site-packages/pyzmq-15.3.0-py2.7.egg-info/not-zip-safe
/usr/lib64/python2.7/site-packages/pyzmq-15.3.0-py2.7.egg-info/top_level.txt
/usr/lib64/python2.7/site-packages/zmq
/usr/lib64/python2.7/site-packages/zmq/__init__.py
/usr/lib64/python2.7/site-packages/zmq/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/auth
/usr/lib64/python2.7/site-packages/zmq/auth/__init__.py
/usr/lib64/python2.7/site-packages/zmq/auth/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/auth/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/auth/base.py
/usr/lib64/python2.7/site-packages/zmq/auth/base.pyc
/usr/lib64/python2.7/site-packages/zmq/auth/base.pyo
/usr/lib64/python2.7/site-packages/zmq/auth/certs.py
/usr/lib64/python2.7/site-packages/zmq/auth/certs.pyc
/usr/lib64/python2.7/site-packages/zmq/auth/certs.pyo
/usr/lib64/python2.7/site-packages/zmq/auth/ioloop.py
/usr/lib64/python2.7/site-packages/zmq/auth/ioloop.pyc
/usr/lib64/python2.7/site-packages/zmq/auth/ioloop.pyo
/usr/lib64/python2.7/site-packages/zmq/auth/thread.py
/usr/lib64/python2.7/site-packages/zmq/auth/thread.pyc
/usr/lib64/python2.7/site-packages/zmq/auth/thread.pyo
/usr/lib64/python2.7/site-packages/zmq/backend
/usr/lib64/python2.7/site-packages/zmq/backend/__init__.py
/usr/lib64/python2.7/site-packages/zmq/backend/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/__init__.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/_cdefs.h
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/_cffi.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/_cffi.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/_cffi.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/_poll.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/_poll.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/_poll.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/_verify.c
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/constants.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/constants.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/constants.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/context.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/context.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/context.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/devices.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/devices.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/devices.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/error.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/error.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/error.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/message.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/message.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/message.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/socket.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/socket.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/socket.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/utils.py
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/utils.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cffi/utils.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cython
/usr/lib64/python2.7/site-packages/zmq/backend/cython/__init__.py
/usr/lib64/python2.7/site-packages/zmq/backend/cython/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/cython/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/backend/cython/_device.so
/usr/lib64/python2.7/site-packages/zmq/backend/cython/_poll.so
/usr/lib64/python2.7/site-packages/zmq/backend/cython/_version.so
/usr/lib64/python2.7/site-packages/zmq/backend/cython/checkrc.pxd
/usr/lib64/python2.7/site-packages/zmq/backend/cython/constant_enums.pxi
/usr/lib64/python2.7/site-packages/zmq/backend/cython/constants.pxi
/usr/lib64/python2.7/site-packages/zmq/backend/cython/constants.so
/usr/lib64/python2.7/site-packages/zmq/backend/cython/context.pxd
/usr/lib64/python2.7/site-packages/zmq/backend/cython/context.so
/usr/lib64/python2.7/site-packages/zmq/backend/cython/error.so
/usr/lib64/python2.7/site-packages/zmq/backend/cython/libzmq.pxd
/usr/lib64/python2.7/site-packages/zmq/backend/cython/message.pxd
/usr/lib64/python2.7/site-packages/zmq/backend/cython/message.so
/usr/lib64/python2.7/site-packages/zmq/backend/cython/socket.pxd
/usr/lib64/python2.7/site-packages/zmq/backend/cython/socket.so
/usr/lib64/python2.7/site-packages/zmq/backend/cython/utils.pxd
/usr/lib64/python2.7/site-packages/zmq/backend/cython/utils.so
/usr/lib64/python2.7/site-packages/zmq/backend/select.py
/usr/lib64/python2.7/site-packages/zmq/backend/select.pyc
/usr/lib64/python2.7/site-packages/zmq/backend/select.pyo
/usr/lib64/python2.7/site-packages/zmq/decorators.py
/usr/lib64/python2.7/site-packages/zmq/decorators.pyc
/usr/lib64/python2.7/site-packages/zmq/decorators.pyo
/usr/lib64/python2.7/site-packages/zmq/devices
/usr/lib64/python2.7/site-packages/zmq/devices/__init__.py
/usr/lib64/python2.7/site-packages/zmq/devices/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/devices/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/devices/basedevice.py
/usr/lib64/python2.7/site-packages/zmq/devices/basedevice.pyc
/usr/lib64/python2.7/site-packages/zmq/devices/basedevice.pyo
/usr/lib64/python2.7/site-packages/zmq/devices/monitoredqueue.pxd
/usr/lib64/python2.7/site-packages/zmq/devices/monitoredqueue.py
/usr/lib64/python2.7/site-packages/zmq/devices/monitoredqueue.pyc
/usr/lib64/python2.7/site-packages/zmq/devices/monitoredqueue.pyo
/usr/lib64/python2.7/site-packages/zmq/devices/monitoredqueue.so
/usr/lib64/python2.7/site-packages/zmq/devices/monitoredqueuedevice.py
/usr/lib64/python2.7/site-packages/zmq/devices/monitoredqueuedevice.pyc
/usr/lib64/python2.7/site-packages/zmq/devices/monitoredqueuedevice.pyo
/usr/lib64/python2.7/site-packages/zmq/devices/proxydevice.py
/usr/lib64/python2.7/site-packages/zmq/devices/proxydevice.pyc
/usr/lib64/python2.7/site-packages/zmq/devices/proxydevice.pyo
/usr/lib64/python2.7/site-packages/zmq/error.py
/usr/lib64/python2.7/site-packages/zmq/error.pyc
/usr/lib64/python2.7/site-packages/zmq/error.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop
/usr/lib64/python2.7/site-packages/zmq/eventloop/__init__.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/future.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/future.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/future.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/ioloop.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/ioloop.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/ioloop.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/__init__.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/concurrent.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/concurrent.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/concurrent.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/ioloop.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/ioloop.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/ioloop.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/log.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/log.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/log.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/__init__.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/auto.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/auto.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/auto.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/common.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/common.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/common.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/interface.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/interface.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/interface.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/posix.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/posix.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/posix.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/windows.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/windows.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/platform/windows.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/stack_context.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/stack_context.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/stack_context.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/util.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/util.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/minitornado/util.pyo
/usr/lib64/python2.7/site-packages/zmq/eventloop/zmqstream.py
/usr/lib64/python2.7/site-packages/zmq/eventloop/zmqstream.pyc
/usr/lib64/python2.7/site-packages/zmq/eventloop/zmqstream.pyo
/usr/lib64/python2.7/site-packages/zmq/green
/usr/lib64/python2.7/site-packages/zmq/green/__init__.py
/usr/lib64/python2.7/site-packages/zmq/green/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/green/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/green/core.py
/usr/lib64/python2.7/site-packages/zmq/green/core.pyc
/usr/lib64/python2.7/site-packages/zmq/green/core.pyo
/usr/lib64/python2.7/site-packages/zmq/green/device.py
/usr/lib64/python2.7/site-packages/zmq/green/device.pyc
/usr/lib64/python2.7/site-packages/zmq/green/device.pyo
/usr/lib64/python2.7/site-packages/zmq/green/eventloop
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/__init__.py
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/ioloop.py
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/ioloop.pyc
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/ioloop.pyo
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/zmqstream.py
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/zmqstream.pyc
/usr/lib64/python2.7/site-packages/zmq/green/eventloop/zmqstream.pyo
/usr/lib64/python2.7/site-packages/zmq/green/poll.py
/usr/lib64/python2.7/site-packages/zmq/green/poll.pyc
/usr/lib64/python2.7/site-packages/zmq/green/poll.pyo
/usr/lib64/python2.7/site-packages/zmq/log
/usr/lib64/python2.7/site-packages/zmq/log/__init__.py
/usr/lib64/python2.7/site-packages/zmq/log/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/log/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/log/handlers.py
/usr/lib64/python2.7/site-packages/zmq/log/handlers.pyc
/usr/lib64/python2.7/site-packages/zmq/log/handlers.pyo
/usr/lib64/python2.7/site-packages/zmq/ssh
/usr/lib64/python2.7/site-packages/zmq/ssh/__init__.py
/usr/lib64/python2.7/site-packages/zmq/ssh/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/ssh/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/ssh/forward.py
/usr/lib64/python2.7/site-packages/zmq/ssh/forward.pyc
/usr/lib64/python2.7/site-packages/zmq/ssh/forward.pyo
/usr/lib64/python2.7/site-packages/zmq/ssh/tunnel.py
/usr/lib64/python2.7/site-packages/zmq/ssh/tunnel.pyc
/usr/lib64/python2.7/site-packages/zmq/ssh/tunnel.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar
/usr/lib64/python2.7/site-packages/zmq/sugar/__init__.py
/usr/lib64/python2.7/site-packages/zmq/sugar/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar/attrsettr.py
/usr/lib64/python2.7/site-packages/zmq/sugar/attrsettr.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/attrsettr.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar/constants.py
/usr/lib64/python2.7/site-packages/zmq/sugar/constants.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/constants.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar/context.py
/usr/lib64/python2.7/site-packages/zmq/sugar/context.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/context.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar/frame.py
/usr/lib64/python2.7/site-packages/zmq/sugar/frame.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/frame.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar/poll.py
/usr/lib64/python2.7/site-packages/zmq/sugar/poll.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/poll.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar/socket.py
/usr/lib64/python2.7/site-packages/zmq/sugar/socket.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/socket.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar/tracker.py
/usr/lib64/python2.7/site-packages/zmq/sugar/tracker.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/tracker.pyo
/usr/lib64/python2.7/site-packages/zmq/sugar/version.py
/usr/lib64/python2.7/site-packages/zmq/sugar/version.pyc
/usr/lib64/python2.7/site-packages/zmq/sugar/version.pyo
/usr/lib64/python2.7/site-packages/zmq/utils
/usr/lib64/python2.7/site-packages/zmq/utils/__init__.py
/usr/lib64/python2.7/site-packages/zmq/utils/__init__.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/__init__.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/buffers.pxd
/usr/lib64/python2.7/site-packages/zmq/utils/compiler.json
/usr/lib64/python2.7/site-packages/zmq/utils/config.json
/usr/lib64/python2.7/site-packages/zmq/utils/constant_names.py
/usr/lib64/python2.7/site-packages/zmq/utils/constant_names.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/constant_names.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/garbage.py
/usr/lib64/python2.7/site-packages/zmq/utils/garbage.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/garbage.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/getpid_compat.h
/usr/lib64/python2.7/site-packages/zmq/utils/interop.py
/usr/lib64/python2.7/site-packages/zmq/utils/interop.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/interop.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/ipcmaxlen.h
/usr/lib64/python2.7/site-packages/zmq/utils/jsonapi.py
/usr/lib64/python2.7/site-packages/zmq/utils/jsonapi.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/jsonapi.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/monitor.py
/usr/lib64/python2.7/site-packages/zmq/utils/monitor.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/monitor.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/pyversion_compat.h
/usr/lib64/python2.7/site-packages/zmq/utils/sixcerpt.py
/usr/lib64/python2.7/site-packages/zmq/utils/sixcerpt.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/sixcerpt.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/strtypes.py
/usr/lib64/python2.7/site-packages/zmq/utils/strtypes.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/strtypes.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/win32.py
/usr/lib64/python2.7/site-packages/zmq/utils/win32.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/win32.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/z85.py
/usr/lib64/python2.7/site-packages/zmq/utils/z85.pyc
/usr/lib64/python2.7/site-packages/zmq/utils/z85.pyo
/usr/lib64/python2.7/site-packages/zmq/utils/zmq_compat.h
/usr/lib64/python2.7/site-packages/zmq/utils/zmq_constants.h
/usr/share/doc/python-zmq-15.3.0
/usr/share/doc/python-zmq-15.3.0/README.md
/usr/share/doc/python-zmq-15.3.0/examples
/usr/share/doc/python-zmq-15.3.0/examples/LICENSE
/usr/share/doc/python-zmq-15.3.0/examples/README_PY3K
/usr/share/doc/python-zmq-15.3.0/examples/asyncio
/usr/share/doc/python-zmq-15.3.0/examples/asyncio/coroutines.py
/usr/share/doc/python-zmq-15.3.0/examples/bench
/usr/share/doc/python-zmq-15.3.0/examples/bench/benchmark.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/jsonrpc_client.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/jsonrpc_server.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/latency.png
/usr/share/doc/python-zmq-15.3.0/examples/bench/msgs_sec.png
/usr/share/doc/python-zmq-15.3.0/examples/bench/msgs_sec_log.png
/usr/share/doc/python-zmq-15.3.0/examples/bench/msgs_sec_ratio.png
/usr/share/doc/python-zmq-15.3.0/examples/bench/plot_latency.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/pyro_client.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/pyro_server.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/pyzmq_client.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/pyzmq_server.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/xmlrpc_client.py
/usr/share/doc/python-zmq-15.3.0/examples/bench/xmlrpc_server.py
/usr/share/doc/python-zmq-15.3.0/examples/chat
/usr/share/doc/python-zmq-15.3.0/examples/chat/display.py
/usr/share/doc/python-zmq-15.3.0/examples/chat/prompt.py
/usr/share/doc/python-zmq-15.3.0/examples/device
/usr/share/doc/python-zmq-15.3.0/examples/device/device.py
/usr/share/doc/python-zmq-15.3.0/examples/eventloop
/usr/share/doc/python-zmq-15.3.0/examples/eventloop/asyncweb.py
/usr/share/doc/python-zmq-15.3.0/examples/eventloop/coroutines.py
/usr/share/doc/python-zmq-15.3.0/examples/eventloop/echo.py
/usr/share/doc/python-zmq-15.3.0/examples/eventloop/echostream.py
/usr/share/doc/python-zmq-15.3.0/examples/eventloop/web.py
/usr/share/doc/python-zmq-15.3.0/examples/gevent
/usr/share/doc/python-zmq-15.3.0/examples/gevent/poll.py
/usr/share/doc/python-zmq-15.3.0/examples/gevent/reqrep.py
/usr/share/doc/python-zmq-15.3.0/examples/gevent/simple.py
/usr/share/doc/python-zmq-15.3.0/examples/heartbeat
/usr/share/doc/python-zmq-15.3.0/examples/heartbeat/heart.py
/usr/share/doc/python-zmq-15.3.0/examples/heartbeat/heartbeater.py
/usr/share/doc/python-zmq-15.3.0/examples/heartbeat/ping.py
/usr/share/doc/python-zmq-15.3.0/examples/heartbeat/pong.py
/usr/share/doc/python-zmq-15.3.0/examples/logger
/usr/share/doc/python-zmq-15.3.0/examples/logger/zmqlogger.py
/usr/share/doc/python-zmq-15.3.0/examples/mongodb
/usr/share/doc/python-zmq-15.3.0/examples/mongodb/client.py
/usr/share/doc/python-zmq-15.3.0/examples/mongodb/controller.py
/usr/share/doc/python-zmq-15.3.0/examples/monitoring
/usr/share/doc/python-zmq-15.3.0/examples/monitoring/simple_monitor.py
/usr/share/doc/python-zmq-15.3.0/examples/poll
/usr/share/doc/python-zmq-15.3.0/examples/poll/pair.py
/usr/share/doc/python-zmq-15.3.0/examples/poll/pubsub.py
/usr/share/doc/python-zmq-15.3.0/examples/poll/reqrep.py
/usr/share/doc/python-zmq-15.3.0/examples/pubsub
/usr/share/doc/python-zmq-15.3.0/examples/pubsub/publisher.py
/usr/share/doc/python-zmq-15.3.0/examples/pubsub/subscriber.py
/usr/share/doc/python-zmq-15.3.0/examples/pubsub/topics_pub.py
/usr/share/doc/python-zmq-15.3.0/examples/pubsub/topics_sub.py
/usr/share/doc/python-zmq-15.3.0/examples/security
/usr/share/doc/python-zmq-15.3.0/examples/security/asyncio-ironhouse.py
/usr/share/doc/python-zmq-15.3.0/examples/security/generate_certificates.py
/usr/share/doc/python-zmq-15.3.0/examples/security/grasslands.py
/usr/share/doc/python-zmq-15.3.0/examples/security/ioloop-ironhouse.py
/usr/share/doc/python-zmq-15.3.0/examples/security/ironhouse.py
/usr/share/doc/python-zmq-15.3.0/examples/security/stonehouse.py
/usr/share/doc/python-zmq-15.3.0/examples/security/strawhouse.py
/usr/share/doc/python-zmq-15.3.0/examples/security/woodhouse.py
/usr/share/doc/python-zmq-15.3.0/examples/serialization
/usr/share/doc/python-zmq-15.3.0/examples/serialization/serialsocket.py
/usr/share/doc/python-zmq-15.3.0/examples/win32-interrupt
/usr/share/doc/python-zmq-15.3.0/examples/win32-interrupt/display.py
/usr/share/doc/python-zmq-15.3.0/examples/win32-interrupt/prompt.py
/usr/share/licenses/python-zmq-15.3.0
/usr/share/licenses/python-zmq-15.3.0/COPYING.BSD
/usr/share/licenses/python-zmq-15.3.0/COPYING.LESSER

@xenophonf Thanks for bring this to the packaging teams attention.  It should be resolved in the next point release, see https://github.com/saltstack/salt-pack/issues/575.
FYI - Packaging issues are tracked in salt-pack for Python 2, and salt-pack-py3 for Python 3.

Closing this since a couple of point releases have been made since the fix was introduced into the code base.  Please reopen if this is unsatisfactory.

source: gharchive/issue

repo: saltstack/salt-pack

license_type: permissive

license_source: bigquery


text:
Add CMake

The Makefile was removed

Also added to the aur, but until this is merged it will use my fork because CMake.

I'm not an experienced C programmer- what advantage does cmake have over regular make, especially for a project as small as this?

CMake is a build system generator. It can be used for more than making Makefiles.
https://stackoverflow.com/questions/25789644/difference-between-using-makefile-and-cmake-to-compile-the-code

Would you mind also updating the README to reflect the changed installation process?

ok

I appreciate your taking interest in my project, but I'm still not convinced there's much to gain from using CMake, versus what I perceive to be the added complexity. Considering that the source code consists of 1 file, and that this change will make it harder for me to maintain this in the future, I don't think I'm going to merge this at this time.

can this pull request be re-opened?

source: gharchive/pull-request

authors: Titaniumtown otreblan sam-barr

repo: sam-barr/paleofetch

license: MIT

license_source: github-api


text:
Exception calling "Replace"  with "2" argument(s): "The RegEx engine has timed out while trying to match a pattern to an input string'

Issue
When this task is run within an Azure DevOps pipeline a Windows agent the following error is sometimes seen

##[error]Import-Json : Import failed for
'E:\Agent_work\92\s\Src\Expenses\BlackMarble.ISS.Bicep\ARMOutput\RootTemplate-Main.json': Exception calling "Replace"
with "2" argument(s): "The RegEx engine has timed out while trying to match a pattern to an input string. This can
occur for many reasons, including very large inputs or excessive backtracking caused by nested quantifiers,
back-references and other factors." Exception calling "Replace" with "2" argument(s): "The RegEx engine has timed out
while trying to match a pattern to an input string. This can occur for many reasons, including very large inputs or
excessive backtracking caused by nested quantifiers, back-references and other factors." Exception calling "Replace"
with "2" argument(s): "The RegEx engine has timed out while trying to match a pattern to an input string. This can
occur for many reasons, including very large inputs or excessive backtracking caused by nested quantifiers,

I suspect the issue is down to the complexity of the ARM template being analyzed
Analysis
If I RDP onto my on prem self hosted agent VM I can get the same error if I follow the following process
From Command Prompt with PowerShell

Open a Command Prompt (CMD)
Run the command powershell.exe E:\Agent\_work\_tasks\RunARMTTKTestsXPlat_cb27e003-8534-4da9-aaa0-35ca8756ae29\1.2.2\powershell\ps-runner.ps1 -templateLocation E:\Agent\_work\92\s\Src\Expenses\BlackMarble.ISS.Bicep\ARMOutput\* -resultLocation E:\Agent\_work\92\s -recurse
The same error as seen in a pipeline run is seen

From Command Prompt with PowerShell Core

Open a Command Prompt (CMD)
Run the command pwsh.exe E:\Agent\_work\_tasks\RunARMTTKTestsXPlat_cb27e003-8534-4da9-aaa0-35ca8756ae29\1.2.2\powershell\ps-runner.ps1 -templateLocation E:\Agent\_work\92\s\Src\Expenses\BlackMarble.ISS.Bicep\ARMOutput\* -resultLocation E:\Agent\_work\92\s -recurse
The script runs as expect (I do have ARM TTK issue with the file under test)

From PowerShell 5 Prompt

Open a PowerShell 5 Prompt
Run the command E:\Agent\_work\_tasks\RunARMTTKTestsXPlat_cb27e003-8534-4da9-aaa0-35ca8756ae29\1.2.2\powershell\ps-runner.ps1 -templateLocation E:\Agent\_work\92\s\Src\Expenses\BlackMarble.ISS.Bicep\ARMOutput\* -resultLocation E:\Agent\_work\92\s -recurse
The script fails  as expected

From PowerShell 7 Prompt

Open a PowerShell 7 Prompt
Run the command E:\Agent\_work\_tasks\RunARMTTKTestsXPlat_cb27e003-8534-4da9-aaa0-35ca8756ae29\1.2.2\powershell\ps-runner.ps1 -templateLocation E:\Agent\_work\92\s\Src\Expenses\BlackMarble.ISS.Bicep\ARMOutput\* -resultLocation E:\Agent\_work\92\s -recurse
The script runs as expected (I do have ARM TTK issue with the file under test)

Suggestion
The issue appears to be the use of the PowerShell 5 (powerhell.exe) as opposed to PowerShell 7 (pwsh.exe).  I think the best option is to give the user the choice to force the use of PWSH, whilst leaving the current default behavior as it is
I will create a PR with this change

Note: This maybe replaced to the problem (arm-ttk-extension #10)[https://github.com/sam-cogan/arm-ttk-extension/issues/10)

Just looked that the source and realized usePSCore already exists, once set to true this fixed the parsing problem.
# Generate the ARM from the Bicep
 - task: BicepBuild@0
    inputs:
      process: 'multiple'
      sourceDirectory: '$(Build.SourcesDirectory)\Src\Bicep\RootTemplate-*.bicep'
      stdout: false
      outputDirectory: '$(Build.SourcesDirectory)\Src\Bicep\ARMOutput' # Only when 'stdout' is false or not defined

 # Good practice to version your ARM
  - task: VersionJSONFile@2
    inputs:
      Path: '$(Build.SourcesDirectory)\Src\Bicep\ARMOutput'
      recursion: true
      VersionNumber: '$(Build.BuildNumber)'
      useBuildNumberDirectly: False
      VersionRegex: '\d+\.\d+\.\d+\.\d+'
      versionForJSONFileFormat: '{1}.{2}.{3}.{4}'
      FilenamePattern: '\w+.json'
      Field: 'contentVersion'
      OutputVersion: 'OutputedVersion'

  - task: RunARMTTKTestsXPlat@1
    displayName: 'Run ARM-TTK on all ARM templates'
    inputs:
      templatelocation: '$(Build.SourcesDirectory)\Src\Bicep\ARMOutput\*'
      resultLocation: '$(Build.SourcesDirectory)'
      usePSCore: true
    continueOnError: true

 - task: PublishTestResults@2
    displayName: 'Publish ARM-TTK test results'
    inputs:
      testResultsFormat: 'NUnit'
      testResultsFiles: '$(Build.SourcesDirectory)\*-armttk.xml'
      testRunTitle: 'Run_$(Build.BuildNumber)'
      failTaskOnFailedTests: true

Hopefully save some other people some time if they hit this issue

repo: sam-cogan/arm-ttk-extension-xplatform


text:
Support code-first AppSync

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-appsync-alpha-readme.html#code-first
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-appsync-alpha-readme.html#code-first-schema
api.addQuery(...)

This is done right? Closing.

authors: sam-goodwin thantos

repo: sam-goodwin/functionless


text:
Set mount path permissions

Patch to set the permissions on the mount point of the smbshare to 0700 by default using the initialize-share-perms permissiona handler. Accompanying this change is the integration test to check if the permissions handler was run against the mount path.

Error:
Error:      	Received unexpected error:
too many pods match selector (opts: {Namespace:samba-operator-system LabelSelector:samba-operator.samba.org/service=tshare1 MaxFound:1 MinFound:0}; pods: [])
Looks like it is waiting on some cleanup. Unlikely to be caused by permission changes. The corresponding tests on the CentosCI have passed.
Let me try kicking this off again.

All clear now :)

OK, cool. I guess I just had bad luck.

authors: phlogistonjohn spuiuk

repo: samba-in-kubernetes/samba-operator


text:
Are there any plans to support reactive programming with generics

Are there any plans to support reactive programming with generics?

Yes, stay tuned ;)

authors: TongChia samber

repo: samber/mo


text:
Log in failure

Can not log in. Credentials are fine, checked on regular Skype client. Here is what I keep getting:
Message: While logging in (400 Bad Request)
ResponseCode: 400
ResponseMessage: Bad Request
StackTrace:

com.samczsun.skype4j.exceptions.ConnectionException: While logging in (400 Bad Request) at com.samczsun.skype4j.internal.ExceptionHandler.generateException(ExceptionHandler.java:50) at com.samczsun.skype4j.internal.Endpoints$EndpointConnection.connect(Endpoints.java:372) at com.samczsun.skype4j.internal.Endpoints$EndpointConnection.connect(Endpoints.java:302) at com.samczsun.skype4j.internal.Endpoints$EndpointConnection.post(Endpoints.java:282) at com.samczsun.skype4j.internal.client.FullClient.login(FullClient.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at coldfusion.runtime.StructBean.invoke(StructBean.java:508) at coldfusion.runtime.CfJspPage._invoke(CfJspPage.java:3159) at coldfusion.runtime.CfJspPage._invoke(CfJspPage.java:3066) at cfSkypeClient2ecfc502157160$funcINIT.runFunction(D:\ACDDProjects\ACDD\trunk\src\Lighthouse\components\skype\SkypeClient.cfc:22) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:492) at coldfusion.runtime.UDFMethod$ReturnTypeFilter.invoke(UDFMethod.java:425) at coldfusion.runtime.UDFMethod$ArgumentCollectionFilter.invoke(UDFMethod.java:388) at coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:95) at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:339) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:234) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:650) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:439) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:409) at coldfusion.runtime.CFPage.___createObjectInternal(CFPage.java:11629) at coldfusion.runtime.CFPage._createObject(CFPage.java:11596) at cfskypebot2ecfm681899910.runPage(D:\ACDDProjects\ACDD\trunk\src\lighthouse\scheduled\hourly\skypebot.cfm:54) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:251) at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:736) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:572) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.IpFilter.invoke(IpFilter.java:45) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:479) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:43) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:142) at coldfusion.filter.LicenseFilter.invoke(LicenseFilter.java:30) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:94) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:60) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62) at coldfusion.CfmServlet.service(CfmServlet.java:219) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at coldfusion.inspect.weinre.MobileDeviceDomInspectionFilter.doFilter(MobileDeviceDomInspectionFilter.java:121) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:532) at org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:874) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:673) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1500) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1456) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745)

Are you using the latest version of Skype4J?

Yes. This is only an issue with recent versions of Skype4j, it does not occur with 0.1.5-SNAPSHOT.

Will take a look tomorrow

Yup, compiled the lastest

If that helps, a couple months ago it was working just fine, and this time the same compilation started failing with this error. Maybe Microsoft changed something on their side?

I wasn't able to reproduce it last time. I can try again but without knowing more details like you username and password (which is what is posted to that particular endpoint) there's not much testing I can do

Can confirm, it has happened when I tried on a different skype account.

Username: lighthouse.pro
Password: TestPassword

I'll be able to debug in an hour or so. If you like drop me an email at skype4j.88@samczsun.com with a different password ;)

Yep, definitely noticing the login issue now. Is that a Skype account or a Microsoft account?

@Orimay So I tried it using the command line and I got this as the response:
{
  "status": {
    "code": 40121,
    "text": "Too many failed authentication attempts with given username or IP."
  }
}

authors: Orimay camdenorrb pangeacake samczsun vemacs


text:
Error start up on Openshift 4.1

Hi,
I used to run sameersbn/redmine on Openshift 3.X without any issue.
But when i deploy on a new Openshift 4.1 cluster. The pod could not startup and got following log:
Initializing logdir...
Initializing datadir...
Generating OpenSSH client keys...
sudo: unable to send audit message: Operation not permitted
/etc/docker-redmine/runtime/functions: line 48:    46 Segmentation fault      sudo -HEu ${REDMINE_USER} "$@"

The deploy config are same. I also try different version of redmine images with no lucky.
Thanks

I'm not familiar with Openshift.  And I'm not sure how the host system can cause sudo to fail within the container :(
Seems like this might be an openshift bug.

its not a bug its expected behavior of openshift openshift does not support root containers! At Last by default.
OpenShift is Red Hat's container platform, built on Kubernetes, Red Hat Enterprise Linux, and OCI containers, and it has a great security feature: By default, no containers are allowed to run as root. An admin can override this, otherwise all user containers run without ever being root

Hi,
I know the issue is long closed.
Root containers can be allowed.
The error message is still there :

sudo: unable to send audit message: Operation not permitted

You could set DEBUG=true in the environment variables to see what command is causing the failure.  Then you could try opening a shell in the container and poke around to see why the command fails.

repo: sameersbn/docker-redmine

license: mit


text:
Better project site http://shapelogicscala.org

Created real project site:
http://shapelogicscala.org
Populate from wiki pages

This is starting to work well, update project site on new releases works well

repo: sami-badawi/shapelogic-scala


text:
websocket user socket

Hello,
I have an issue regarding the websocket:
Just a simple code:
def process_message(msg):
	print (msg)

def initiate():
	client = Client('key', 'secret')
	bm = BinanceSocketManager(client)
	conn_key = bm.start_user_socket(process_message)
	bm.start()

initiate()

but if i run this code the system returns no values. I've tried another socket e.g. start_ticket_socket it will work as intended.
Am I doing something wrong?
Thanks in advance!

Have you tried placing an order or cancelling one, e.g. from the web interface? The user socket doesn't return anything until there's something to return.

Hi,
I faced this issue as well. Even I m placing order while running subscript websocket, but nothing response back.

any news on the topic? cause i'm having the same...

Hi, change     STREAM_URL = 'wss://stream.binance.com:9443/'
to  'wss://stream.binance.us:9443/' would work if your account is on binance.us

I'm having an issue as well.  I'm running this socket and placing orders, there is no response through the socket.
Are any additional parameters/conditions needed to return a response?  Other than (1) having the start_user_socket() socket open and (2) placing orders?

from binance.client import Client
from binance.websockets import BinanceSocketManager
def process_message(msg):
print (msg)
def initiate():
client = Client('public', 'secret')
bm = BinanceSocketManager(client)
conn_key = bm.start_user_socket(process_message)
bm.start()
salir = ''
while salir != 'q':
salir = input("'q' for exit: ")

binance_example.txt

from binance.client import Client
from binance.websockets import BinanceSocketManager

def process_message(msg):

print (msg)

def initiate():

client = Client('public', 'secret')
bm = BinanceSocketManager(client)
conn_key = bm.start_user_socket(process_message)
bm.start()

salir = ''
while salir != 'q':

salir = input(" 'q' for exit: ")

repo: sammchardy/python-binance


text:
Codepen doesn't have preview thumbnails but plyr.io demo does

https://codepen.io/pen?template=bKeqpr
No preview thumbnails
https://plyr.io/
Has preview thumbnails
How do I see the code of an example with preview thumbnails implemented?

https://codepen.io/mayeaux/pen/rNmRXzm
Unless there's a good argument against it I'd recommend adding it

repo: sampotts/plyr


text:
iOS/iPhone 15.2.1 reports navigator.platform as MacIntel

Expected behaviour
plyr correctly determines if it's running on iPhone/iOS 15.2.1
Actual behaviour
plyr doesn't realize it's using the iPhone/iOS
Steps to reproduce
call browser.isIPhone on an iPhone running iOS 15.2.1
Environment

Browser: Safari
Version: 15.2.1
Operating System:15.2.1
Version:15.2.1

Console errors (if any)
Link to where the bug is happening
browser.js

As a note, hls.js detects an iPhone because it's missing the MediaSource extensions. iPad/iOS and MacOS both support MediaSource, making it a convenient way of determining the platform.

Just noting that the iPhone only identifies itself as MacOS if the user has requested the desktop version of the website and browser.isIos still works in this mode (although it can't differentiate from iPads).


text:
mbsubmit: cleanup and completion

Glad to see a new release has been made!
I'm getting back to work on beets after a few days away from the computer, hopefully bringing issue #1689 to a close eventually. As hinted on the previous discussion, this pull request is intended to take care of the mbsubmit plugin cleanup, now that the underlying pieces are in place.
I have modified a bit the behaviour, making the decision of appending the "Print tracks" choice depend solely on task.rec. The default behaviour is to only append the choice to matches where the recommendation is equal or lower than Recommendation.medium, which hopefully covers the most obvious choices (albums with no matches, albums with weak-ish matches) and the original request by @awesomer, and also avoids polluting the prompt in the cases where the match is strong. A config option has been added that allows the user to modify this settings (extra-picky users might find it useful to always be able to print tracks for fixing spelling mistakes, other users might only want it on albums with no matches, etc).
Other than that, a configuration option for setting the format string has been added as well - I can't think of a case where this might come in handy currently, but maybe more creative users might find it useful.
A couple of notes:

currently, the plugin makes no effort of nicely formatting items that might be lacking some of the required fields. Would it be useful to add some extra checks and fall back to printing the filename (or something more advanced with the help of fromfilename, etc) in those cases?
there might be some problems on some combination on options: for example, if the user sets the threshold to strong, but launches the importer in non-timid mode, the prompt will not actually be displayed. Would a note on the (upcoming) documentation suffice, as handling this case probably requires some changes that seem to be a bit out of the scope of the plugin?

As usual, any comments and input are more than welcome!

Awesome; this looks perfect. Feel free to merge at will.
On those questions:

I'd say we shouldn't worry about missing fields. Here's my reasoning: this plugin is about situations where you already have good metadata (or better metadata than MB). So while picking up tags from filenames à la fromfilename would be nifty, it's out of scope for this initial version.
I see what you're saying—yeah, let's document this.

Thanks for the quick turnaround, and commenting on the questions - sounds like a reasonable compromise. I will work on the documentation during tomorrow and hopefully everything should be ready for a merge soon!

Fixed the style issues, and added some pretty basic documentation and a changelog entry. As usual, double checking the documentation would be more than welcome!

Fixed the style issues (the extra ticks were for making it more evident that they were referring to the names of the button/elements on MusicBrainz site, and the choice of mb_format for the configuration was to avoid any confusion with the format flag - but I'm happy to drop both)!
I have also merged upstream/master, solving the tiny conflict on changelog.rst.

And merged, after the checks seemed ok!

Woohoo!

repo: sampsyo/beets


text:
want to add toast.

i want to add toast instead of window alert .
please assign this issue under hacktoberfeast 2023 tag.

Ok ... You can start work


text:
database/sql: prevent conn reuse on new conn request

This ports https://github.com/golang/go/pull/32656 to our local version
to address https://github.com/golang/go/issues/32530

To check the time performance, I whipped up a little performance comparison (code below).
It seems like channel operations are about 10 times slower than the equivalent list operation, retrieving from a channel takes ~40ns compared to the list grab taking ~4ns.
Although a large multiplier, I think the scale of the constant factor is small enough that this is unlikely to have a major impact overall. Especially considering this makes the system less likely to have to retry connection attempts in the first place.
package main

import (
	"fmt"
	"math/rand"
	"time"
)

type Thing struct {
	Open bool
}

func NewThing() *Thing {
	return &Thing{Open: rand.Float64() > 0.3}
}

const times = 10000
const poolSize = 200

func listPoolClean(pool []*Thing) {
	// clean pool
	for i := 0; i < len(pool); i++ {
		t := pool[i]
		if !t.Open {
			last := len(pool) - 1
			pool[i] = pool[last]
			pool[last] = nil
			pool = pool[:last]
			i--
		}
	}
}

func timeListPoolClean(times int) time.Duration {
	pools := make([][]*Thing, times)
	for i := 0; i < times; i++ {
		newPool := make([]*Thing, poolSize)
		for j := 0; j < poolSize; j++ {
			newPool[j] = NewThing()
		}
		pools[i] = newPool
	}

	start := time.Now()
	for i := 0; i < times; i++ {
		listPoolClean(pools[i])
	}
	return time.Since(start)
}

func chanPoolClean(pool chan *Thing) {
	// clean pool
	poolSize := len(pool)
	for i := 0; i < poolSize; i++ {
		t := <-pool
		if t.Open {
			pool <- t
		}
	}
}

func timeChanPoolClean(times int) time.Duration {
	pools := make([]chan *Thing, times)
	for i := 0; i < times; i++ {
		newPool := make(chan *Thing, poolSize)
		for j := 0; j < poolSize; j++ {
			newPool <- NewThing()
		}
		pools[i] = newPool
	}

	start := time.Now()
	for i := 0; i < times; i++ {
		chanPoolClean(pools[i])
	}
	return time.Since(start)
}

func main() {
	listTime := timeListPoolClean(times)
	listTimeNPO := float64(listTime/time.Nanosecond) / float64(times*poolSize)
	chanTime := timeChanPoolClean(times)
	chanTimeNPO := float64(chanTime/time.Nanosecond) / float64(times*poolSize)
	slowdown := float64(chanTime) / float64(listTime)
	fmt.Printf(
		"list: %s / %d / %d -> %fns\nchan: %s / %d %d -> %fns\nslowDownFactor: %f\n",
		listTime,
		poolSize,
		times,
		listTimeNPO,
		chanTime,
		poolSize,
		times,
		chanTimeNPO,
		slowdown,
	)
}

repo: samsarahq/golang-go


text:
Fresh MacOS Maestral install never gets past "Connecting..." and therefore never syncs.

Describe the bug

A fresh install of Maestral never gets past the "Connecting..." step, even after successfully linking to a Dropbox account (I can see my name and profile picture in the Preferences window). The "show sync issues" option shows no sync issues. Running maestral log show just shows it stopping at "Connecting...", which is also what maestral status shows.
Here's what I've tried without success:

Running the daemon via the terminal and the GUI.
Rebuilding the index
Restarting the app
Restarting my computer
Unlinking/relinking my Dropbox account
Reinstalling the app
Connecting to different internet access points and connecting/disconnecting from different VPN servers

To Reproduce

Install Maestral from latest stable package downloaded from GitHub
Run setup as usual
Successfully connect to Dropbox account
The app status says "Connecting..." and never continues.

Expected behaviour

Maestral progresses past the "Connecting..." step and starts syncing files with my Dropbox account.
System:

Maestral version: 1.5.2
Python version: 2.7.16 and 3.7.2
OS: MacOS 12.1

Additional context

When I run the suggested python3 -c "from PyQt5.Qt import PYQT_VERSION_STR; print(PYQT_VERSION_STR)" command, I get the following error:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'PyQt5'

I ran brew install python to make sure my Python3 was installed/up-to-date, but it hasn't helped.
Activity Monitor shows almost no disk activity from the Maestral processes.
My Dropbox is a bit over 35GB of data.
I have moved all the (synced) files from my default Dropbox folder to the Dropbox (Maestral) folder.
The regular Dropbox app has no difficulty connecting or syncing.

@Fleckeri, thanks for the report. This is certainly surprising and your trouble shooting steps were already quite exhaustive. In principle, Maestral should work well with both VPNs and Proxies but there might be some corner cases which I have not considered. Do you have any Proxies configured in System Preferences or otherwise?
Unfortunately, Maestral currently does not log why a connection cannot be established. Could you check if Dropbox servers are reachable via curl in the command line?
$ curl -I "http://www.dropbox.com"

If this works, next step would be to install the requests package with pip3 install requests and try the following from a Python prompt:
import requests

res = requests.head("http://www.dropbox.com", timeout=2)
print(res)

proxies = requests.session().proxies
print(proxies)

This reproduces exactly the connection check that Maestral is doing. If this request returns <Response [301]>, all is well. If raises a ReadTimeout error, you can try to increase the the timeout  2 sec and see if this helps. Any other would also be useful to know! It would be also interesting to see what requests.session().proxies returns.
The PyQt5 version is only relevant for Linux, Maestral uses a native user interface on macOS.

$ curl -I "http://www.dropbox.com"
If this works [...]

What could be the reason for this not to work? (curl works in general, of course.)
I can rule out general network issues or corner cases since it is working on another device with the same connection configuration.
Maybe a lack of server-side authorization of this specific device is causing this?
Is it necessary to have installed and used the Dropbox client at least once ont he device before? That would be great to avoid on a new machine with a fresh install if possible.
Thanks a lot for the great work!

I can rule out general network issues or corner cases since it is working on another device with the same connection configuration.

Well, something in the configuration will likely be different, even if it is a bit hidden. This could for example be environment variables with proxy settings that don't affect all programs.

Maybe a lack of server-side authorization of this specific device is causing this?

Unlikely. The connection issues which you are seeing happens before Maestral tries to do anything for which it needs authentication.

Is it necessary to have installed and used the Dropbox client at least once ont he device before?

Not necessary.
At the moment, the best shot at figuring this out is to run the Python code which I have posted in my previous comment, if you are comfortable installing Python packages and running some code. Otherwise, the next release will include better debug output for connection issues.

@Fleckeri, thanks for the report. This is certainly surprising and your trouble shooting steps were already quite exhaustive. In principle, Maestral should work well with both VPNs and Proxies but there might be some corner cases which I have not considered. Do you have any Proxies configured in System Preferences or otherwise?

I checked the my MacOS proxies, and none of the proxies are checked on. Passive FTP mode (PASV) is checked, though, and a couple local domains bypass the (non-active) proxies.

Unfortunately, Maestral currently does not log why a connection cannot be established. Could you check if Dropbox servers are reachable via curl in the command line?
$ curl -I "http://www.dropbox.com"

Oddly enough, this doesn't work for me. The command simply stalls indefinitely until I cancel out of it. I tried a different command $ curl https://www.gnu.org/gnu/gnu.html and it worked immediately, so I tried $ curl -I https://dropbox.com and that instantly returned all the headers. Running a curl on the non-HTTPS domain just doesn't work for me for some reason (VPN off or on).

If this works, the next step would be to install the requests package with pip3 install requests and try the following from a Python prompt:
import requests

res = requests.head("http://www.dropbox.com", timeout=2)
print(res)

This reproduces exactly the connection check that Maestral is doing. If this request returns <Response [301]>, all is well. If raises a ReadTimeout error, you can try to increase the the timeout 2 sec and see if this helps.

I ran the above commands in Python3, and it simply timed out. I increased the timeout to 30 seconds, and it still timed out.
Here's part of the error:
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/requests/adapters.py", line 507, in send
    raise ConnectTimeout(e, request=request)
requests.exceptions.ConnectTimeout: HTTPConnectionPool(host='www.dropbox.com', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f7e9dbd1860>, 'Connection to www.dropbox.com timed out. (connect timeout=30)'))

I ran the command again using https://www.dropbox.com and it returned a <Response [200]>.

Any other would also be useful to know! It would be also interesting to see what requests.session().proxies returns.

This simply returns {}.

It seems like my installation really doesn't like the non-HTTPS version of the base Dropbox URL, and I'm not sure why. I must have screwed with my settings somewhere, but I'm not sure what it would be.

It seems like my installation really doesn't like the non-HTTPS version of the base Dropbox URL, and I'm not sure why. I must have screwed with my settings somewhere, but I'm not sure what it would be.

That is very strange. The HTTP version of the URL should just respond with a redirect header to the HTTPS version. In fact, the next release will no longer check the connectivity using http://www.dropbox.com but will use https://api.dropboxapi.com instead. This should fix the problems which you are seeing 🤞

It seems like my installation really doesn't like the non-HTTPS version of the base Dropbox URL, and I'm not sure why. I must have screwed with my settings somewhere, but I'm not sure what it would be.

That is very strange. The HTTP version of the URL should just respond with a redirect header to the HTTPS version. In fact, the next release will no longer check the connectivity using http://www.dropbox.com but will use https://api.dropboxapi.com instead. This should fix the problems which you are seeing 🤞

I appreciate it! I'll wait for the next version and report back here.

Confirming Maestral version 1.5.3 has fixed this issue. Closing the issue now.

authors: Fleckeri boettges samschott

repo: samschott/maestral


text:
Promote Facts as a datatype

Facts can be handles as separate objects, both real facts and almost facts. Real Facts are usually  evaluated to true and other Facts to false. But while executing on a certified Trump device all facts will be evaluated to true for performance gain.

See a76f078

authors: epatel samshadwell

repo: samshadwell/TrumpScript


text:
Error when trying to use .original in slots

Here's the error:
api_1            | TypeError: Cannot use 'in' operator to search for 'original' in undefined
api_1            |     at Object.strict (/usr/src/app/node_modules/handlebars/lib/handlebars/runtime.js:74:17)
api_1            |     at Object.eval (eval at createFunctionContext (/usr/src/app/node_modules/handlebars/lib/handlebars/compiler/javascript-compiler.js:236:23), <anonymous>:3:64)
api_1            |     at main (/usr/src/app/node_modules/handlebars/lib/handlebars/runtime.js:152:32)
api_1            |     at ret (/usr/src/app/node_modules/handlebars/lib/handlebars/runtime.js:155:12)
api_1            |     at ret (/usr/src/app/node_modules/handlebars/lib/handlebars/compiler/compiler.js:513:21)
api_1            |     at compiledResponse (/usr/src/app/lib/services/agent/agent.converse-compile-response-templates.service.js:14:36)
api_1            |     at arrayMap (/usr/src/app/node_modules/lodash/lodash.js:639:23)
api_1            |     at Function.map (/usr/src/app/node_modules/lodash/lodash.js:9554:14)
api_1            |     at AgentService.map (/usr/src/app/lib/services/agent/agent.converse-compile-response-templates.service.js:7:29)
api_1            |     at AgentService.apply [as converseCompileResponseTemplates] (/usr/src/app/lib/services/agent.services.js:257:55)

Here is the conversation:

here is the export:
https://gist.github.com/wrathagom/90cc0446151554fc3d844c79ed430e9c

The slotName is date you are using slots.data... in the response
{
      "actionName": "Hours",
      "slots": [
        {
          "slotName": "date",
          "uiColor": "#009688",
          "keyword": "sys.duckling_time",
          "keywordId": 0,
          "isList": false,
          "isRequired": false,
          "textPrompts": []
        }
      ],
      "responses": [
        {
          "textResponse": "{{slots.data.original}} we are open from 11Am until 11PM.",
          "actions": []
        },
        {
          "textResponse": "We are open from 11AM until 11PM tomorrow.",
          "actions": []
        },
        {
          "textResponse": "We're open everyday from 11AM to 11PM.",
          "actions": []
        }
      ],
      "useWebhook": false,
      "usePostFormat": false,
      "creationDate": "1549420321000",
      "modificationDate": "1549421231000"
    }

Please let me know if that is the issue

Doh

authors: dcalvom wrathagom

repo: samtecspg/articulate


text:
2: Add test_package to ensure that the generator is properly exercised

Add test_package. This will generate sphinx documentation and print out the head of index.html if it was created successfully.
Update ci config to add a windows build
Update documentation

Closes #2

[ ] Blocked on https://github.com/samuel-emrys/python-virtualenv/issues/4.

repo: samuel-emrys/cmake-python-deps


text:
Android: 2022 Redesign

It's time for this year's design changes. There's a good number of them.
You can see the redesign on beta.newsblur.com.

Story titles changed the most

There's now a lot more margin and spacing between title, content, and date/author
Author moved from inline with title to next to date, losing color differences
Read stories are now bold, so unread and read story titles take the same space
Unread indicator and feed favicon switched positions

All new icons. 100% SVGs, all found under media/icons/nouns/* on the pro branch
Missing favicon icon also replaced (world.png -> world.svg)
Almost all uppercase is now in regular, sentence case. Exceptions can and should be made, but buttons and such are now "Sentence case".
Feed title background colors are slightly different to match each other better
All feed favicons now have a border radius
Blurblogs move to below a user's own feeds
All menu icons (site menu, feed menu, folder menu, story menu) were replaced
New icons in Feed Options popover (top style menu)
Difference between Comfortable / Compact was further emphasized
Borders between feeds, folders, and story titles were removed and deemphasized
Story content header has fewer borders and more space
Feed header bar no longer has borders, just the gradient
Story action buttons at the bottom of each story are slightly different too
Highlighted feeds have a border radius and margin to them now

I uploaded a whole bunch of screenshots of the before and after from the web for convenience, but realized it would be easier for you to just switch back and forth between beta.newsblur.com and www.newsblur.com. That should help guide the relative changes since it won't be a 1-for-1 with mobile.

Since we'll be deep in story title layout for this ticket, let's fix this screenshot. There needs to be more padding between elements when the font size goes up. We do this on the web and while it's a lot of work, the results are clearly better.

@samuelclay The redesign changed we're pushed to the main repo and are ready for your initial live review.
The padding issue with enlarged font might have been fixed by the new padding between elements.

Sorry that took so long! I've been on infrastructure all week and it's been eating into my nighttime hours by quite a bit. But I finally released a big change last night that seems to be having a good impact.

@samuelclay Thanks for the detailed list with photos. The branch is ready for another UI review.

Great work! Few more notes:
Feed list

Let's match the three background colors on the web for saved stories, shared stories, and saved searches
The All/Unread/Focus/Saved control in the bottom should have the text next to the icon if there's room. If not, successively remove from the right (saved goes first, then focus, then unread, then all). The web does this nicely, just resize the feed list width.
Font size of top level folders is a point too small. On the web we have a letter-spacing of 0.5px which slightly widens it
The left justification for top level folders and feed folders are off by a pixel or two

Story list

Lighten the bottom and top border to match the web. Those borders should be nearly invisible
Tiny bit more margin (~1-2px) above story title in Comfortable spacing
Tiny bit more margin (~2-4px) above and below in Compact spacing
There's too much space on story titles that have no story content but story content preview is enabled

Story content

Remove the border for the colored feed favicon bar

@samuelclay Ready for another test drive.

This is so, so good. I'm loving this new design with all of its increased space. Few notes:
Story titles list

The search icon looks weird, can we switch that to the new icon? Or is this the new icon? I'd like to have a cleaner icon there
Increase the right-side padding by ~8px. It should be comfortably far from the edge of the screen
Hyphenation is happening at the character level. Let's switch that to word level.

Story detail

There's some extra right padding on story tags

I'm delighted by the new design as well! Dark mode is nicer without the gradients and borders.
The search icon was new but I replaced it with a standard Android one which should do the job. On older devices these SVGs might be rendered a bit weird.
I worked on getting the hyphenation by word but the results weren't consistent for some reason. I suspect the returned measured text width is somehow incorrect. I won't continue on this due to the web having the same hyphenation rules but let me know if you want me to spend more time and give it another try.

Yeah, let's see what we can do about that hyphenation. It's bizarre and feels broken.

Feels broken on the web too! Ok then, ignore it for now and let's see if it bothers me later.

I'll get back to you with notes tomorrow, I want to let it sit for a day.

Perfect, last issue is that there's some extra right padding on story tags.

@samuelclay Could you post a picture with the padding on story tags? I wasn't sure last time either if I was making the right change.

Available in v12.0.0

authors: samuelclay sictiru

repo: samuelclay/NewsBlur


text:
iOS: support for iOS and iPadOS 16, and Xcode 14

Please note that the iOS app project now requires Xcode 14 or later.
I have updated the project for Swift 5.7, and for compatibility with iOS and iPadOS 16.
I don't think there are any iOS 16 improvements that we need to adopt in NewsBlur at this stage. Things like lock-screen widgets aren't that useful for this app.
(This issue is assigned to both of us to give you a heads-up; feel free to close it once you've updated.)

Working fine for me, and I'm running Xcode 14.0.2.

authors: Dejal samuelclay


text:
Images not showing for certain feed

I'm not seeing any issues in this RSS feed but it's not showing any images. It shows fine on feedly but now in NewsBlur. Any ideas? Is there a way to customize the feed before NewsBlur renders it?
Here is a sample of the feed:
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CG Persia</title>
	<atom:link href="https://cgpersia.com/feed" rel="self" type="application/rss+xml" />
	<link>https://cgpersia.com</link>
	<description></description>
	<lastBuildDate>Mon, 06 Feb 2023 22:01:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>

	<item>
		<title>Udemy – 3ds Max & Corona Renderer: An In-Depth Guide for Beginners.</title>
		<link>https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html</link>
					<comments>https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html#respond</comments>

		<dc:creator><![CDATA[Diptra]]></dc:creator>
		<pubDate>Mon, 06 Feb 2023 22:01:50 +0000</pubDate>
				<category><![CDATA[2D]]></category>
		<category><![CDATA[CG Releases]]></category>
		<category><![CDATA[Downloads]]></category>
		<category><![CDATA[Learning]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Videos]]></category>
		<category><![CDATA[3ds Max]]></category>
		<category><![CDATA[corona render]]></category>
		<category><![CDATA[Udemy]]></category>
		<guid isPermaLink="false">https://cgpersia.com/?p=188225</guid>

					<description><![CDATA[Duration 2h 24m Project Files Included MP4 Title: Udemy – 3ds Max & Corona Renderer: An In-Depth Guide for Beginners. Info: Unleash Your 3D Design Potential with 3ds Max & Corona Renderer: A Comprehensive Course for Beginners What you’ll learn The basics of 3ds Max and Corona Renderer, including interface navigation and essential tools. Techniques […]]]></description>
										<content:encoded><![CDATA[

Duration 2h 24m Project Files Included MP4

]]></content:encoded>

					<wfw:commentRss>https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>

			</item>
	</channel>
</rss>

That feed looks valid and feedparser is able to parse it:
>>> import feedparser
>>> fp = feedparser.parse("""<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
...     xmlns:content="http://purl.org/rss/1.0/modules/content/"
...     xmlns:wfw="http://wellformedweb.org/CommentAPI/"
...     xmlns:dc="http://purl.org/dc/elements/1.1/"
...     xmlns:atom="http://www.w3.org/2005/Atom"
...     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
...     xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
...     >
...
... <channel>
...     <title>CG Persia</title>
...     <atom:link href="https://cgpersia.com/feed" rel="self" type="application/rss+xml" />
...     <link>https://cgpersia.com</link>
...     <description></description>
...     <lastBuildDate>Mon, 06 Feb 2023 22:01:50 +0000</lastBuildDate>
...     <language>en-US</language>
...     <sy:updatePeriod>
...     hourly</sy:updatePeriod>
...     <sy:updateFrequency>
...     1</sy:updateFrequency>
...
...     <item>
...             <title>Udemy – 3ds Max & Corona Renderer: An In-Depth Guide for Beginners.</title>
...             <link>https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html</link>
...                                     <comments>https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html#respond</comments>
...
...             <dc:creator><![CDATA[Diptra]]></dc:creator>
...             <pubDate>Mon, 06 Feb 2023 22:01:50 +0000</pubDate>
...                             <category><![CDATA[2D]]></category>
...             <category><![CDATA[CG Releases]]></category>
...             <category><![CDATA[Downloads]]></category>
...             <category><![CDATA[Learning]]></category>
...             <category><![CDATA[Tutorials]]></category>
...             <category><![CDATA[Videos]]></category>
...             <category><![CDATA[3ds Max]]></category>
...             <category><![CDATA[corona render]]></category>
...             <category><![CDATA[Udemy]]></category>
...             <guid isPermaLink="false">https://cgpersia.com/?p=188225</guid>
...
...                                     <description><![CDATA[Duration 2h 24m Project Files Included MP4 Title: Udemy – 3ds Max & Corona Renderer: An In-Depth Guide for Beginners. Info: Unleash Your 3D Design Potential with 3ds Max & Corona Renderer: A Comprehensive Course for Beginners What you’ll learn The basics of 3ds Max and Corona Renderer, including interface navigation and essential tools. Techniques […]]]></description>
...                                                                             <content:encoded><![CDATA[

...
Duration 2h 24m Project Files Included MP4

...

]]></content:encoded>
...
...                                     <wfw:commentRss>https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html/feed</wfw:commentRss>
...                     <slash:comments>0</slash:comments>
...
...                     </item>
...     </channel>
... </rss>""")
>>> fp.bozo
False
>>> fp
{'bozo': False, 'entries': [{'title': 'Udemy – 3ds Max & Corona Renderer: An In-Depth Guide for Beginners.', 'title_detail': {'type': 'text/plain', 'language': None, 'base': '', 'value': 'Udemy – 3ds Max & Corona Renderer: An In-Depth Guide for Beginners.'}, 'links': [{'rel': 'alternate', 'type': 'text/html', 'href': 'https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html'}], 'link': 'https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html', 'comments': 'https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html#respond', 'authors': [{'name': 'Diptra'}], 'author': 'Diptra', 'author_detail': {'name': 'Diptra'}, 'published': 'Mon, 06 Feb 2023 22:01:50 +0000', 'published_parsed': time.struct_time(tm_year=2023, tm_mon=2, tm_mday=6, tm_hour=22, tm_min=1, tm_sec=50, tm_wday=0, tm_yday=37, tm_isdst=0), 'tags': [{'term': '2D', 'scheme': None, 'label': None}, {'term': 'CG Releases', 'scheme': None, 'label': None}, {'term': 'Downloads', 'scheme': None, 'label': None}, {'term': 'Learning', 'scheme': None, 'label': None}, {'term': 'Tutorials', 'scheme': None, 'label': None}, {'term': 'Videos', 'scheme': None, 'label': None}, {'term': '3ds Max', 'scheme': None, 'label': None}, {'term': 'corona render', 'scheme': None, 'label': None}, {'term': 'Udemy', 'scheme': None, 'label': None}], 'id': 'https://cgpersia.com/?p=188225', 'guidislink': False, 'summary': 'Duration 2h 24m Project Files Included MP4 Title: Udemy – 3ds Max & Corona Renderer: An In-Depth Guide for Beginners. Info: Unleash Your 3D Design Potential with 3ds Max & Corona Renderer: A Comprehensive Course for Beginners What you’ll learn The basics of 3ds Max and Corona Renderer, including interface navigation and essential tools. Techniques […]', 'summary_detail': {'type': 'text/html', 'language': None, 'base': '', 'value': 'Duration 2h 24m Project Files Included MP4 Title: Udemy – 3ds Max & Corona Renderer: An In-Depth Guide for Beginners. Info: Unleash Your 3D Design Potential with 3ds Max & Corona Renderer: A Comprehensive Course for Beginners What you’ll learn The basics of 3ds Max and Corona Renderer, including interface navigation and essential tools. Techniques […]'}, 'content': [{'type': 'text/html', 'language': None, 'base': '', 'value': '

\n
Duration 2h 24m Project Files Included MP4
\n

'}], 'wfw_commentrss': 'https://cgpersia.com/2023/02/udemy-3ds-max-corona-renderer-an-in-depth-guide-for-beginners-188225.html/feed', 'slash_comments': '0'}], 'feed': {'title': 'CG Persia', 'title_detail': {'type': 'text/plain', 'language': None, 'base': '', 'value': 'CG Persia'}, 'links': [{'href': 'https://cgpersia.com/feed', 'rel': 'self', 'type': 'application/rss+xml'}, {'rel': 'alternate', 'type': 'text/html', 'href': 'https://cgpersia.com'}], 'link': 'https://cgpersia.com', 'subtitle': '', 'subtitle_detail': {'type': 'text/html', 'language': None, 'base': '', 'value': ''}, 'updated': 'Mon, 06 Feb 2023 22:01:50 +0000', 'updated_parsed': time.struct_time(tm_year=2023, tm_mon=2, tm_mday=6, tm_hour=22, tm_min=1, tm_sec=50, tm_wday=0, tm_yday=37, tm_isdst=0), 'language': 'en-US', 'sy_updateperiod': 'hourly', 'sy_updatefrequency': '1'}, 'headers': {}, 'encoding': 'utf-8', 'version': 'rss20', 'namespaces': {'content': 'http://purl.org/rss/1.0/modules/content/', 'wfw': 'http://wellformedweb.org/CommentAPI/', 'dc': 'http://purl.org/dc/elements/1.1/', '': 'http://www.w3.org/2005/Atom', 'sy': 'http://purl.org/rss/1.0/modules/syndication/', 'slash': 'http://purl.org/rss/1.0/modules/slash/'}}

Feel free to re-open this ticket if you can point to the changes you'd like to see in the code.

authors: NylonDiamond samuelclay


text:
Send different types of email updates to different types of ticket holders

Add options for sending different emails to different types of ticket holders. To increase character limit and Rich Text. For both Admin and Host users.

Does this option apply to donors too (people who donate)?

The update system only send to ticket holders.
There's an open issue for adding donation updates -> #310

I've tested several times but no update email was received. Can you please recheck?

This was due to to the email template being marked as "inactive" in the dashboard.

authors: pro-Nate roselukas

repo: samuelcolvin/nosht


text:
"Field constraints are set but not enforced" with generics

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug
             pydantic version: 1.8.2
            pydantic compiled: False
                 install path: C:\Users\seragiottoc\Miniconda3\envs\domino-prototype\Lib\site-packages\pydantic
               python version: 3.9.7 | packaged by conda-forge | (default, Sep 29 2021, 19:15:42) [MSC v.1916 64 bit (AMD64)]
                     platform: Windows-10-10.0.18363-SP0
     optional deps. installed: ['typing-extensions']

from typing import Generic, TypeVar

from pydantic import Field
from pydantic.generics import GenericModel

T = TypeVar("T")

class A(GenericModel, Generic[T]):
    t: list[int] = Field(..., min_items=1)

A[int](t=[1])
...

…
ValueError: On field "t" the following field constraints are set but not enforced: min_items.
For more details see https://pydantic-docs.helpmanual.io/usage/schema/#unenforced-field-constraints

This is a duplicate of #2581 Although there is seems to be no activity since July 2021. It's still better to close this issue.

authors: MaratBR clo-vis

repo: samuelcolvin/pydantic


text:
change ValidationError.errors()

The errors() function should change its signature to errors(full=False). With full=True the output should be the same as present.
With full=False, the output should be simplied to:

loc should be a dot delimited string
ctx should be removed.

So with full=True:
[
    {
        'loc': ('b',),
        'msg': 'ensure this value has at least 1 characters',
        'type': 'value_error.any_str.min_length',
        'ctx': {'limit_value': 1},
    }
]

with full=False:
[
    {
        'loc': 'b',
        'msg': 'ensure this value has at least 1 characters',
        'type': 'value_error.any_str.min_length',
    }
]

Feedback welcome, otherwise i'll do before the next release.

Can you please describe why you want to change current behavior? Plus as I remember, decision to return loc as tuple was yours :) And it's a backward incompatible change...

Can you please describe why you want to change current behavior?

Because I think it will be more elegant and easier for new users. Plus in most cases ctx is completely irrelevant, it really shouldn't be in the public API.

Plus as I remember, decision to return loc as tuple was yours :)

Yes, it was a mistake, I've been regretting it since.

And it's a backward incompatible change...

I know, but we should aim to get it right and not be afraid of breaking changes.

Understand, just one moment, dot delimited string isn't good, because of possible dots in dict keys:
➜ python
Python 3.7.1 (default, Nov  6 2018, 18:46:03)
[Clang 10.0.0 (clang-1000.11.45.5)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from pydantic import BaseModel
>>> from typing import Dict
>>> class Model(BaseModel):
...     k: Dict[str, int]
...
>>> Model.parse_obj({'k': {'a.b.c': 'd'}})
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/ng/.virtualenvs/tmp-5e251d8d098bcac/lib/python3.7/site-packages/pydantic/main.py", line 262, in parse_obj
    return cls(**obj)
  File "/Users/ng/.virtualenvs/tmp-5e251d8d098bcac/lib/python3.7/site-packages/pydantic/main.py", line 190, in __init__
    self.__setstate__(self._process_values(data))
  File "/Users/ng/.virtualenvs/tmp-5e251d8d098bcac/lib/python3.7/site-packages/pydantic/main.py", line 360, in _process_values
    return validate_model(self, input_data)
  File "/Users/ng/.virtualenvs/tmp-5e251d8d098bcac/lib/python3.7/site-packages/pydantic/main.py", line 533, in validate_model
    raise ValidationError(errors)
pydantic.error_wrappers.ValidationError: 1 validation error
k -> a.b.c
  value is not a valid integer (type=type_error.integer)
>>>