Strange error

Sentry has reported this error to me, but I think this error is the result of sentry-sdk itself failing to report another error!
Stack (yes sorry its cut off):
    return self.request_encode_body(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 171, in request_encode_body
    return self.urlopen(method, url, **extra_kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/poolmanager.py", line 330, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 719, in urlopen
    retries = retries.increment(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/util/retry.py", line 400, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/packages/six.py", line 734, in reraise
    raise value.with_traceback(tb)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 665, in urlopen
    httplib_response = self._make_request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 421, in _make_request
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 416, in _make_request
    httplib_response = conn.getresponse()
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/integrations/stdlib.py", line 102, in getresponse
    rv = real_getresponse(self, *args, **kwargs)
  File "/usr/lib/python3.8/http/client.py", line 1322, in getresponse
    response.begin()
  File "/usr/lib/python3.8/http/client.py", line 303, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python3.8/http/client.py", line 272, in _read_status
    raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2020-04-03 06:15:06,961: Sending event, type:null level:error event_id:1e1b73402bf5435dbb9270782cd9c753 project:1799955 host:sentry.io
2020-04-03 06:25:06,340: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)'))': /api/1799955/store/
2020-04-03 06:25:07,140: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)'))': /api/1799955/store/
2020-04-03 06:30:07,103: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)'))': /api/1799955/store/
2020-04-03 06:39:52,314: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)'))': /api/1799955/store/
2020-04-03 06:44:51,994: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)'))': /api/1799955/store/
2020-04-03 07:04:52,103: Internal error in sentry_sdk
Traceback (most recent call last):
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 665, in urlopen
    httplib_response = self._make_request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 376, in _make_request
    self._validate_conn(conn)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 994, in _validate_conn
    conn.connect()
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connection.py", line 386, in connect
    self.sock = ssl_wrap_socket(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/util/ssl_.py", line 370, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.8/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib/python3.8/ssl.py", line 1040, in _create
    self.do_handshake()
  File "/usr/lib/python3.8/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1108)
**NO MATCH**
During handling of the above exception, another exception occurred:
**NO MATCH**
Traceback (most recent call last):
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 296, in send_event_wrapper
    self._send_event(event)
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 215, in _send_event
    self._send_request(
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 163, in _send_request
    response = self._pool.request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 79, in request
    return self.request_encode_body(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 171, in request_encode_body
    return self.urlopen(method, url, **extra_kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/poolmanager.py", line 330, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 719, in urlopen
    retries = retries.increment(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='sentry.io', port=443): Max retries exceeded with url: /api/1799955/store/ (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)')))
2020-04-03 07:10:05,243: Sending event, type:null level:error event_id:10c7f22e0ee24002a41a4876fcff2c91 project:1799955 host:sentry.io
2020-04-03 07:19:52,067: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)'))': /api/1799955/store/
2020-04-03 07:24:51,071: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)'))': /api/1799955/store/
2020-04-03 07:34:51,204: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)'))': /api/1799955/store/
2020-04-03 07:59:51,108: Internal error in sentry_sdk
Traceback (most recent call last):
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 665, in urlopen
    httplib_response = self._make_request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 376, in _make_request
    self._validate_conn(conn)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 994, in _validate_conn
    conn.connect()
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connection.py", line 386, in connect
    self.sock = ssl_wrap_socket(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/util/ssl_.py", line 370, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.8/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib/python3.8/ssl.py", line 1040, in _create
    self.do_handshake()
  File "/usr/lib/python3.8/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1108)
**NO MATCH**
During handling of the above exception, another exception occurred:
**NO MATCH**
Traceback (most recent call last):
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 296, in send_event_wrapper
    self._send_event(event)
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 215, in _send_event
    self._send_request(
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 163, in _send_request
    response = self._pool.request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 79, in request
    return self.request_encode_body(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 171, in request_encode_body
    return self.urlopen(method, url, **extra_kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/poolmanager.py", line 330, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 719, in urlopen
    retries = retries.increment(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='sentry.io', port=443): Max retries exceeded with url: /api/1799955/store/ (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)')))
2020-04-03 07:59:51,131: Sending event, type:null level:error event_id:97a7e51264ed43848b3ee88a373211b9 project:1799955 host:sentry.io
2020-04-03 08:20:06,178: Internal error in sentry_sdk
Traceback (most recent call last):
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 665, in urlopen
    httplib_response = self._make_request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 421, in _make_request
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 416, in _make_request
    httplib_response = conn.getresponse()
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/integrations/stdlib.py", line 102, in getresponse
    rv = real_getresponse(self, *args, **kwargs)
  File "/usr/lib/python3.8/http/client.py", line 1322, in getresponse
    response.begin()
  File "/usr/lib/python3.8/http/client.py", line 303, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python3.8/http/client.py", line 272, in _read_status
    raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
**NO MATCH**
During handling of the above exception, another exception occurred:
**NO MATCH**
Traceback (most recent call last):
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 296, in send_event_wrapper
    self._send_event(event)
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 215, in _send_event
    self._send_request(
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 163, in _send_request
    response = self._pool.request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 79, in request
    return self.request_encode_body(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 171, in request_encode_body
    return self.urlopen(method, url, **extra_kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/poolmanager.py", line 330, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 719, in urlopen
    retries = retries.increment(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/util/retry.py", line 400, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/packages/six.py", line 734, in reraise
    raise value.with_traceback(tb)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 665, in urlopen
    httplib_response = self._make_request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 421, in _make_request
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 416, in _make_request
    httplib_response = conn.getresponse()
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/integrations/stdlib.py", line 102, in getresponse
    rv = real_getresponse(self, *args, **kwargs)
  File "/usr/lib/python3.8/http/client.py", line 1322, in getresponse
    response.begin()
  File "/usr/lib/python3.8/http/client.py", line 303, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python3.8/http/client.py", line 272, in _read_status
    raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2020-04-03 08:25:06,138: Internal error in sentry_sdk
Traceback (most recent call last):
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 665, in urlopen
    httplib_response = self._make_request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 376, in _make_request
    self._validate_conn(conn)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 994, in _validate_conn
    conn.connect()
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connection.py", line 386, in connect
    self.sock = ssl_wrap_socket(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/util/ssl_.py", line 370, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.8/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib/python3.8/ssl.py", line 1040, in _create
    self.do_handshake()
  File "/usr/lib/python3.8/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1108)
**NO MATCH**
During handling of the above exception, another exception occurred:
**NO MATCH**
Traceback (most recent call last):
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 296, in send_event_wrapper
    self._send_event(event)
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 215, in _send_event
    self._send_request(
  File "/home/reece/backend/lib/python3.8/site-packages/sentry_sdk/transport.py", line 163, in _send_request
    response = self._pool.request(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 79, in request
    return self.request_encode_body(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/request.py", line 171, in request_encode_body
    return self.urlopen(method, url, **extra_kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/poolmanager.py", line 330, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 747, in urlopen
    return self.urlopen(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/connectionpool.py", line 719, in urlopen
    retries = retries.increment(
  File "/home/reece/backend/lib/python3.8/site-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='sentry.io', port=443): Max retries exceeded with url: /api/1799955/store/ (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1108)')))

This just looks like a network failure. I don't think the SDK did anything wrong here?

But the network error is connecting to sentry

So I guess the only idea I have is: 1) network failure on your end 2) broken version of urllib3 or openssl.
Do you get events into sentry at all?

I did

Can you post the output of pip freeze in that environment? I wonder whether you use some async library like gevent etc

Here you go:
aiohttp==3.6.2
appdirs==1.4.3
area4==3.6.0
async-timeout==3.0.1
attrs==19.3.0
black==19.10b0
cchardet==2.1.6
certifi==2019.11.28
chardet==3.0.4
click==7.1.1
Deprecated==1.2.7
discord-sentry-reporting==2.0.3
discord.py==1.3.2
entrypoints==0.3
factdata==2.0.0
filehandlers==2.12.1
flake8==3.7.9
idna==2.9
isort==4.3.21
iss-api==1.1
jedi==0.16.0
mccabe==0.6.1
multidict==4.7.5
mypy==0.770
mypy-extensions==0.4.3
numpy==1.18.2
parso==0.6.2
pathspec==0.7.0
prompt-toolkit==3.0.5
ptpython==3.0.1
pycodestyle==2.5.0
pyflakes==2.1.1
PyGithub==1.47
Pygments==2.6.1
PyJWT==1.7.1
regex==2020.2.20
requests==2.23.0
reverse-geocoder==1.5.1
scipy==1.4.1
sentry-sdk==0.14.3
slots==1.3
SQLAlchemy==1.3.15
toml==0.10.0
typed-ast==1.4.1
typing-extensions==<IP_ADDRESS>
unittest-xml-reporting==3.0.2
urllib3==1.25.8
wcwidth==0.1.9
websockets==8.1
wrapt==1.12.1
yarl==1.4.2

do you perhaps use a HTTP proxy of some sort? either configured via environment variables or explicitly

cc @gpjt since this is on PA

@RDIL hi, did you find anything out?

I thought about what you said and realized I don't think its worth investigating.

okay, do you have an estimated failure rate of some sort? like, how many events do you get fully saved into sentry and how often do you see this urllib3 error

It usually happens on ~ 1/4 errors, but it makes it to sentry eventually

In response to the question about the proxy earlier -- free accounts on PythonAnywhere need to go via a Squid proxy server, but the proxy settings are in the http_proxy and https_proxy environment variables, which I think urllib3 will pick up...?  requests certainly does.
However, the account whose username is in @RDIL's stacktrace above is a paid account, which has direct unproxied Internet access, so that won't matter in this case.  The packets that the code is generating are just being sent out to the network unmodified.  Maybe it could be some kind of rate-limiting at sentry.io, or something like that?

Our rate limiting is generally supposed to return proper 429 HTTP
responses, not just drop the TCP connection. We have load balancer rate
limits but you would have to send 100/s from a single IP and even there you
should get a 429
On Wed, Apr 8, 2020, 16:32 Giles Thomas<EMAIL_ADDRESS>wrote:

In response to the question about the proxy earlier -- free accounts on
PythonAnywhere need to go via a Squid proxy server, but the proxy settings
are in the http_proxy and https_proxy environment variables, which I
think urllib3 will pick up...? requests certainly does.
However, the account whose username is in @RDIL https://github.com/RDIL's
stacktrace above is a paid account, which has direct unproxied Internet
access, so that won't matter in this case. The packets that the code is
generating are just being sent out to the network unmodified. Maybe it
could be some kind of rate-limiting at sentry.io, or something like that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/getsentry/sentry-python/issues/665#issuecomment-610994229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGMPRMHW466DBNZFI7U323RLSDGXANCNFSM4L36FRPA
.

our sentry stopped working 3 days ago, and was reporting this exact error on all events

Did it get resolved
I am also getting similar error
gunicorn: urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='<IP_ADDRESS>', port=9000): Max retries exceeded with url: /api/8/envelope/ (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7facc6f5dc88>: Failed to establish a new connection: [Errno 111] Connection refused',))

urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='sentry.iap.hh-d.cn', port=443): Max retries exceeded with url: /api/1/envelope/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fdc7ebf8f70>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
06:55:42 [ERROR] sentry_sdk.errors: Internal error in sentry_sdk
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connection.py", line 174, in _new_conn
conn = connection.create_connection(
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/util/connection.py", line 72, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/local/lib/python3.8/socket.py", line 918, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connectionpool.py", line 703, in urlopen
httplib_response = self._make_request(
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connectionpool.py", line 386, in _make_request
self._validate_conn(conn)
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connectionpool.py", line 1042, in _validate_conn
conn.connect()
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connection.py", line 358, in connect
self.sock = conn = self._new_conn()
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connection.py", line 186, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7fdc7e7c8220>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/sentry/../sentry_sdk/transport.py", line 470, in send_envelope_wrapper
self._send_envelope(envelope)
File "/usr/local/lib/python3.8/site-packages/sentry/../sentry_sdk/transport.py", line 387, in _send_envelope
self._send_request(
File "/usr/local/lib/python3.8/site-packages/sentry/utils/sdk.py", line 268, in patched_send_request
return _send_request(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/sentry/../sentry_sdk/transport.py", line 230, in _send_request
response = self._pool.request(
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/request.py", line 78, in request
return self.request_encode_body(
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/request.py", line 170, in request_encode_body
return self.urlopen(method, url, **extra_kw)
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/poolmanager.py", line 376, in urlopen
response = conn.urlopen(method, u.request_uri, **kw)
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connectionpool.py", line 815, in urlopen
return self.urlopen(
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connectionpool.py", line 815, in urlopen
return self.urlopen(
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connectionpool.py", line 815, in urlopen
return self.urlopen(
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/connectionpool.py", line 787, in urlopen
retries = retries.increment(
File "/usr/local/lib/python3.8/site-packages/sentry/../urllib3/util/retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='sentry.iap.hh-d.cn', port=443): Max retries exceeded with url: /api/1/envelope/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fdc7e7c8220>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
06:56:59 [ERROR] sentry_sdk.errors: Internal error in sentry_sdk

I was getting this error running sentry-sdk 1.25.1 but updated to 1.28.1 and it seemed to have corrected whatever was going wrong.
The error that made it into the log I was looking at was similar to:
2023-07-20 04:04:45,202 [raven-sentry] [WARNI] [urllib3.connectionpo]  Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1007)'))': /api/[numbers]/envelope/


How to display wizard by dot(formio) style rather than page

We'd like to keep they way form.io present wizard( dot style rather than page header). NgForm 2.x using template to formatting it. But it was gone from 3.x.
How we do similar things in angular-formio?
Thanks.

Customizing our wizard will be available in our 4x branch which we hope to release soon


Version handling

Is your feature request related to a problem? Please describe.
It is only possible to install one atta version in the computer right now, which can be bad if we have projects that were developed in different versions.
Feature description
Now we can only install one version of atta, but we should be able to install multiple versions in the same machine because they may be incompatible between each other, and we may want to install another version to run a specific project.
Tasks

[x] Install atta with version

[x] /usr/local/include/atta-<IP_ADDRESS>/
[x] /usr/local/include/atta-<IP_ADDRESS>/extern
[x] /usr/local/share/atta-<IP_ADDRESS>/
[x] /usr/local/bin/atta-<IP_ADDRESS> and /usr/local/bin/atta

[x] Be able to select atta version to link to the project with cmake. Eg: find_package(atta <IP_ADDRESS> REQUIRED)
[ ] UI see current version (Help menu)
[ ] Uninstall versions
[ ] Install different atta versions from the atta application (download and install from could)
[ ] Change default atta version from the atta application (/usr/bin/atta-<IP_ADDRESS> to /usr/bin/atta)
[ ] Restart atta with correct atta version
[ ] Should suggest options to restart atta with another version if trying to open project made with another version

To install multiple version, files are installed to:

resources: /usr/local/share/atta-X.X.X.X/
libs: /usr/local/lib/atta-X.X.X.X/
includes: /usr/local/include/atta-X.X.X.X/atta/
ext_includes: /usr/local/include/atta-X.X.X.X/extern/
binaries

/usr/lib/bin/atta
/usr/lib/bin/atta-X.X.X.X
/usr/lib/bin/atta_test
/usr/lib/bin/atta_test-X.X.X.X

This way the default atta program will be the last installed (overwriting atta executable), but it is also possible to run older versions


Scope and time scheduling of the meeting for calling of recently implemented dynamic systems (issue #864 related)

The goal is to schedule the meeting in Teams calendar on 2024.08.18 at 20:15.

Meeting is scheduled for 2024.08.18 at 20:15 in Teams.


Fix building shared object on macOS

PR #10 helped with several things, but the command to compile the shared object is still slightly problematic, in that it leaves out some flags, and it assumes gcc is being used rather than clang. This PR adds the necessary flags to that command, and detects the compiler to adjust it accordingly.
If you could make a v1.1.2 release after merging this, that would be great.

Note: I've also updated the name of the binaries to libtabixpp.a and libtabixpp.so.1 (rather than merely libtabix) — this is both more accurate and enables vcflib to correctly locate tabixpp, whereas it was not before.

Note that building .so on macOS is likely not what you really want. Instead, it should be a dylib and follow platform conventions as libtabixpp.1.dylib (instead of libtabixpp.so.1). In general libtool will help with these platform specific differences vs trying to detect the correct behavior in a Makefile.

@jonchang Yeah quite possibly. I believe so files are perfectly legal on macOS, but non-standard as you say. If someone can help with a patch here, that would be great.


doc: Intended usage on a construct library?

Describe your issue?
We are developing a library of constructs for CDK. This library does not instantiate any apps or stacks, it serves only to export constructs. What is the expected way to test a construct library like this?
I tried adding Aspects to a unit test like this: https://github.com/aws-samples/aws-cdk-examples/blob/9c88ce300037bd0fbc25b900cae8f28a2863046f/typescript/s3-kms-cross-account-replication/test/s3-replication.test.ts#L54
However this did not work. There are no cdk-nag warnings or errors printed during the unit test.
What is the intended way to run cdk-nag on a library of constructs that does not initialize any stacks or apps?

This method seems to work: https://github.com/cdklabs/cdk-nag/issues/728

@mvs5465  I gather that this is for a construct library that is meant for a wide audience.
In that case I would advise not putting suppressions in the actual construct code and only in the unit tests (example). Putting suppressions in the actual code for constructs intended for a general audience is bad practice as that makes decisions for consumers


tpl: Add a delimiter parameter to lang.NumFmt

The original implementation of NumFmt did not take into account that the
options delimiter (a space) could be a valid option.  Adding a delim
parameter seems like the simplest, safest, and most flexible way to
solve this oversight in a backwards-compatible way.
Fixes #5260

Can you also update the docs that go along with this PR?

I was waiting to see if this approach would be acceptable.  It looks like @bep agrees with your comment, so I'll add docs to this PR.  👍


v3.0.2 throws "Cannot read property 'replace' of undefined"

After upgrading to 3.0.2, I can't seem to be able to get JSCS to work. Running the jscs CLI returns this error:
TypeError: Cannot read property 'replace' of undefined
    at renderLine (/Users/test/my_project/node_modules/jscs/lib/errors.js:266:16)
    at Object.Errors.explainError (/Users/test/my_project/node_modules/jscs/lib/errors.js:197:13)
    at /Users/test/my_project/node_modules/jscs/lib/reporters/console.js:16:36
    at Array.forEach (native)
    at /Users/test/my_project/node_modules/jscs/lib/reporters/console.js:14:35
    at Array.forEach (native)
    at Object.module.exports [as writer] (/Users/test/my_project/node_modules/jscs/lib/reporters/console.js:9:22)
    at /Users/test/my_project/node_modules/jscs/lib/cli.js:149:18
    at Array.<anonymous> (/Users/test/my_project/node_modules/vow/lib/vow.js:712:56)
    at Immediate.callFns [as _onImmediate] (/Users/test/my_project/node_modules/vow/lib/vow.js:23:35)

My .jscsrc is:
{
	"excludeFiles": [
		"html/build/**",
		"html/js/examples/**",
		"html/test/jasmine-2.4.1/**"
	],

	"disallowKeywords": ["with"],
	"disallowMultipleLineStrings": true,
	"disallowNamedUnassignedFunctions": true,
	"disallowNewlineBeforeBlockStatements": true,
	"disallowOperatorBeforeLineBreak": ["."],
	"disallowQuotedKeysInObjects": "allButReserved",
	"disallowSpaceAfterPrefixUnaryOperators": ["++", "--", "+", "~"],
	"disallowSpaceBeforeBinaryOperators": ["!"],
	"disallowSpacesInsideArrayBrackets": "all",
	"disallowSpacesInsideBrackets": true,
	"disallowSpacesInsideObjectBrackets": "all",
	"disallowTrailingComma": true,
	"disallowTrailingWhitespace": true,
	"requireAnonymousFunctions": true,
	"requireCapitalizedConstructors": true,
	"requireCommaBeforeLineBreak": true,
	"requireCurlyBraces": ["for", "try", "catch"],
	"requireLineBreakAfterVariableAssignment": true,
	"requireOperatorBeforeLineBreak": ["?", "=", "+", "-", "/", "*", "==", "===", "!=", "!==", ">", ">=", "<", "<="],
	"requirePaddingNewLinesAfterUseStrict": true,
	"requirePaddingNewLinesBeforeExport": true,
	"requireParenthesesAroundIIFE": true,
	"requireSpaceAfterKeywords": ["do", "for", "else", "switch", "case", "void", "while", "with", "typeof", "function"],
	"requireSpaceBeforeKeywords": ["else", "while"],
	"requireSpaceBeforeObjectValues": true,
	"requireSpacesInConditionalExpression": {
		"afterTest": true,
		"beforeConsequent": true,
		"afterConsequent": true,
		"beforeAlternate": true
	},
	"requireSpacesInForStatement": true,
	"requireSpacesInFunctionDeclaration": {
		"beforeOpeningRoundBrace": true,
		"beforeOpeningCurlyBrace": true
	},
	"requireSpacesInNamedFunctionExpression": {
		"beforeOpeningCurlyBrace": true
	},
	"safeContextKeyword": ["self", "_this"],
	"validateAlignedFunctionParameters": {
		"lineBreakAfterOpeningBraces": true,
		"lineBreakBeforeClosingBraces": true
	},
	"validateIndentation": "\t",
	"validateParameterSeparator": ", "
}

I thought we fixed this one @mdevils?

I have the same issue in react-starter-kit after upgrading to 3.0.2

3.0.3 doesn't fix it, take a look https://travis-ci.org/kriasoft/react-starter-kit/builds/123586977

@hzoo I though so
Will take a look soon

This has been happening for me for any version 3.0.x
I went through my codebase and ran jscs on each file until I discovered which file was causing the error to occur, and then through each function inside that file until I narrowed down the root cause. It seems that this object destructuring assignment inside of a function parameter causes the error: https://github.com/tangrams/tangram-play/blob/master/src/js/map/map.js#L80
This is valid ES6 and has been addressed before.
I created a very minimal test case so you can duplicate the error: https://gist.github.com/louh/0b2e74228c141afc4a34b70d3e944254

still happening in 3.0.3

I have same problem use with react

Same error for static property definition (in  jscs 3.0.3)
class Bar {
    static test = {
        foo: 'bar'
    };
}

That seems to be valid code
TypeError: Cannot read property 'replace' of undefined
    at renderLine (/var/www/test/node_modules/jscs/lib/errors.js:266:16)
    at Object.Errors.explainError (/var/www/test/node_modules/jscs/lib/errors.js:197:13)
    at /var/www/test/node_modules/jscs/lib/reporters/console.js:16:36
    at Array.forEach (native)
    at /var/www/test/node_modules/jscs/lib/reporters/console.js:14:35
    at Array.forEach (native)
    at Object.module.exports [as writer] (/var/www/test/node_modules/jscs/lib/reporters/console.js:9:22)
    at /var/www/test/node_modules/jscs/lib/cli.js:149:18
    at Array.<anonymous> (/var/www/test/node_modules/vow/lib/vow.js:712:56)
    at Immediate.callFns [as _onImmediate] (/var/www/test/node_modules/vow/lib/vow.js:23:35)

I got the same error when using esnext bind expression, which doesn't seem to be supported in cst used by jscs 3.0. Whenever there is a parse error (error.rule === "parseError"), the error has no line number.
The fixed I applied temporarily to my jscs install was this, which a least prints the underlying reason for the parse error. I'm not sure if that's the best place for the fix or if it should be as soon as the parse error is detected.
explainError: function(error, colorize) {
  if (typeof error.line === 'undefined') {
    //probably a parseError, so include the rule name
    return formatErrorMessage(error.rule + ': ' + error.message, this.getFilename(), colorize);
  }
  //... the rest
}

There is lot of different errors here and they about different things, like
export function myFunction ({ foo = false, bar = null } = {}) {
    console.log(foo, bar);
}

Is https://github.com/cst/cst/issues/118
static properties is about - https://github.com/cst/cst/issues/112
And so on.
After https://github.com/cst/cst/pull/116 and with https://github.com/jscs-dev/node-jscs/commit/729db94f86902496f3962a4a97bdd91a75ab5514, errors will be outputted in a friendly manner

pulling in the latest changes from master fixed this issue for me:
"devDependencies": {
  ...
  "jscs": "git:github.com/jscs-dev/node-jscs.git",
  ...
}

This is enough:
"devDependencies": {
  ...
  "jscs": "jscs-dev/node-jscs",
  ...
}

@zxqfox cool, thanks!

For me problem still occurs. Even on the jscs-dev/node-jscs version. It's hard for me to paste example code because project is too large.

Reporting in the same. Version 3.0.3. May move to ESLint as suggested though on the blog. For now I'm using the fix people have suggested.

We gonna publish 3.0.4 in a few days with a fix (we hope). Can you please try master branch?

I will try it on Monday (just finished work;)
On 20 May 2016 4:06 pm, "Alexej Yaroshevich"<EMAIL_ADDRESS>wrote:

We gonna publish 3.0.4 in a few days with a fix (we hope). Can you please
try master branch?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/jscs-dev/node-jscs/issues/2219#issuecomment-220615013

Unfortunatly, I still get 'replace' of undefined error. :(
On Fri, May 20, 2016 at 4:17 PM Sebastian<EMAIL_ADDRESS>wrote:

I will try it on Monday (just finished work;)
On 20 May 2016 4:06 pm, "Alexej Yaroshevich"<EMAIL_ADDRESS>wrote:

We gonna publish 3.0.4 in a few days with a fix (we hope). Can you please
try master branch?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/jscs-dev/node-jscs/issues/2219#issuecomment-220615013

Most basic example to get the error:
var m = require('mori');

function getTrNid(trNid, saveRes) {
  return trNid < 0
		? m.getIn(saveRes, [parseInt(trNid), 'nid'])
		: trNid;
};

module.exports = getTrNid;

Results in:
~/delme/node-jscs/bin/jscs -x --preset airbnb src/js/model/FlightListLeg/getTrNid.js
validateIndentation: Invalid indentation character:      at src/js/model/FlightListLeg/getTrNid.js :
     3 |function getTrNid(trNid, saveRes) {
     4 |  return trNid < 0
     5 |  ? m.getIn(saveRes, [parseInt(trNid), 'nid'])
--------^
     6 |  : trNid;
     7 |};

validateIndentation: Invalid indentation character:      at src/js/model/FlightListLeg/getTrNid.js :
     4 |  return trNid < 0
     5 |  ? m.getIn(saveRes, [parseInt(trNid), 'nid'])
     6 |  : trNid;
--------^
     7 |};
     8 |

TypeError: Cannot read property 'replace' of undefined
    at renderLine (/home/dflt/delme/node-jscs/lib/errors.js:267:16)
    at Object.Errors.explainError (/home/dflt/delme/node-jscs/lib/errors.js:198:13)
    at /home/dflt/delme/node-jscs/lib/reporters/console.js:16:36
    at Array.forEach (native)
    at /home/dflt/delme/node-jscs/lib/reporters/console.js:14:35
    at Array.forEach (native)
    at Object.module.exports [as writer] (/home/dflt/delme/node-jscs/lib/reporters/console.js:9:22)
    at /home/dflt/delme/node-jscs/lib/cli.js:149:18
    at Array.<anonymous> (/home/dflt/delme/node-jscs/node_modules/vow/lib/vow.js:712:56)
    at Immediate.callFns [as _onImmediate] (/home/dflt/delme/node-jscs/node_modules/vow/lib/vow.js:23:35)


External Output: Add scrolling list view

As mentioned by @ivanov in https://github.com/nteract/hydrogen/pull/825#issuecomment-304947011 it would be nice to have a single page where output is appended at the bottom. Somehow I forgot to follow up on this idea 😉
This PR allows users of the external output panel to switch between two modes. One can either flip back and forth between outputs or have a single page where output is appended at the bottom and scrolled into view:

Love it!

We shouldn't merge before #954 to not cause more rebase pain.

Rebased onto  #954


Fix an Axelrod version

@marcharper I'm finally coming back to this.
Should we re run all the results with a fixed Axelrod version? Say 1.16? (That's the latest one)
I'll throw a requirements.txt file together for this repo.

I had missed strategies.py so I see you have fixed the strategies. Still happy with those?

Agreed on fixing the version.
I excluded some strategies because they are time consuming to generate data for, but we can certainly revisit the list.

I excluded some strategies because they are time consuming to generate data for, but we can certainly revisit the list.

I'm happy with the current list, I guess the main thing would be to check that we aren't missing out any recent additions that are particularly interesting.

I'll take a look. There are some cheap strategies that have been added recently; I think we should try to get MetaHunter, my new ensemble, and maybe a few others in the final set. But let's fine tune the other parameters on the faster to generated collection and then see where we're at.


Installation Issue

I've tried latest back through to older docker tags and I can't get this running. Run as image pull and direct on the Dockerfile also.
Primary issue continually seems to be:
api_1    | error TypeError: strapi.models.core_store.forge is not a function
api_1    |     at Object.get (/usr/local/lib/node_modules/strapi/lib/core/store.js:55:47)
api_1    |     at module.exports (/usr/src/api/strapi-app/plugins/content-manager/config/functions/bootstrap.js:229:42)
api_1    |     at Promise (/usr/local/lib/node_modules/strapi/lib/Strapi.js:285:13)
api_1    |     at new Promise (<anonymous>)
api_1    |     at execBootstrap (/usr/local/lib/node_modules/strapi/lib/Strapi.js:273:11)
api_1    |     at Promise.all.Object.values.map.x (/usr/local/lib/node_modules/strapi/lib/Strapi.js:312:44)
api_1    |     at Array.map (<anonymous>)
api_1    |     at Strapi.bootstrap (/usr/local/lib/node_modules/strapi/lib/Strapi.js:312:35)
api_1    |     at Strapi.start (/usr/local/lib/node_modules/strapi/lib/Strapi.js:107:18)
api_1    |     at <anonymous>
api_1    | (node:15) UnhandledPromiseRejectionWarning: TypeError: strapi.models.core_store.forge is not a function
api_1    |     at Object.get (/usr/local/lib/node_modules/strapi/lib/core/store.js:55:47)
api_1    |     at module.exports (/usr/src/api/strapi-app/plugins/settings-manager/config/functions/bootstrap.js:17:26)
api_1    |     at Promise (/usr/local/lib/node_modules/strapi/lib/Strapi.js:285:13)
api_1    |     at new Promise (<anonymous>)
api_1    |     at execBootstrap (/usr/local/lib/node_modules/strapi/lib/Strapi.js:273:11)
api_1    |     at Promise.all.Object.values.map.x (/usr/local/lib/node_modules/strapi/lib/Strapi.js:312:44)
api_1    |     at Array.map (<anonymous>)
api_1    |     at Strapi.bootstrap (/usr/local/lib/node_modules/strapi/lib/Strapi.js:312:35)
api_1    |     at Strapi.start (/usr/local/lib/node_modules/strapi/lib/Strapi.js:107:18)
api_1    |     at <anonymous>
api_1    | (node:15) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
api_1    | (node:15) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
api_1    | [2018-08-28T10:16:02.269Z] warn Bootstrap is taking unusually long to execute its callback 3500 miliseconds).
api_1    | [2018-08-28T10:16:02.271Z] warn Perhaps you forgot to call it?

Node @ v9 on the Strapi API
/usr/src/api/strapi-app # node -v v9.11.1
"dependencies": {
    "lodash": "4.x.x",
    "strapi": "3.0.0-alpha.13.1",
    "strapi-hook-mongoose": "3.0.0-alpha.13.1"
  },

The image installation via Dockerfile is OK.
root@strapi:~/strapi-docker# docker-compose up
Building api
Step 1/10 : FROM node:9.11.1-alpine
9.11.1-alpine: Pulling from library/node
605ce1bd3f31: Already exists
7cc38010b685: Already exists
88a635599bc5: Already exists
Digest: sha256:f8f6c69cce180a9a7c9fa685c86671b1e1f2ea7cc5f9a0dbe99d30cc7a0b6cbe
Status: Downloaded newer image for node:9.11.1-alpine
 ---> 9cc7800b3f3c
Step 2/10 : LABEL maintainer="Luca Perret<EMAIL_ADDRESS>     org.label-schema.vendor="Strapi"       org.label-schema.name="Strapi Docker image"       org.label-schema.description="Strapi containerized"       org.label-schema.url="https://strapi.io"       org.label-schema.vcs-url="https://github.com/strapi/strapi-docker"       org.label-schema.version=latest       org.label-schema.schema-version="1.0"
 ---> Running in 06747ceeb7e9
Removing intermediate container 06747ceeb7e9
 ---> ba15448a1d0e
Step 3/10 : WORKDIR /usr/src/api
Removing intermediate container d60f419808c2
 ---> 8a03bb768927
Step 4/10 : RUN npm install -g<EMAIL_ADDRESS> ---> Running in 455e0c7dca8c
npm WARN deprecated<EMAIL_ADDRESS>The sprintf package is deprecated in favor of sprintf-js.
npm WARN notice [SECURITY] deep-extend has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=deep-extend&version=0.2.11 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
npm WARN notice [SECURITY] lodash has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=lodash&version=3.10.1 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
npm WARN notice [SECURITY] debug has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=debug&version=2.6.1 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
npm WARN notice [SECURITY] lodash has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=lodash&version=4.17.4 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
/usr/local/bin/strapi -> /usr/local/lib/node_modules/strapi/bin/strapi.js
+<EMAIL_ADDRESS>added 391 packages in 21.617s
Removing intermediate container 455e0c7dca8c
 ---> 37bafa272a09
Step 5/10 : COPY strapi.sh ./
 ---> e10df39a92d4
Step 6/10 : RUN chmod +x ./strapi.sh
 ---> Running in 10889a82b0ac
Removing intermediate container 10889a82b0ac
 ---> 20e89447b146
Step 7/10 : EXPOSE 1337
 ---> Running in 65ef7067ed7a
Removing intermediate container 65ef7067ed7a
 ---> 8a5167500fdc
Step 8/10 : COPY healthcheck.js ./
 ---> 8d3dbb4f7d28
Step 9/10 : HEALTHCHECK --interval=15s --timeout=5s --start-period=30s       CMD node /usr/src/api/healthcheck.js
 ---> Running in 0162f62e4435
Removing intermediate container 0162f62e4435
 ---> 265493a76158
Step 10/10 : CMD ["./strapi.sh"]
 ---> Running in 51fafe469c68
Removing intermediate container 51fafe469c68
 ---> 09be8dd339ff
Successfully built 09be8dd339ff
Successfully tagged strapidocker_api:latest

Hi @ouchiko, could you try with the last image (3.0.0-alpha.14) and if it don't work, report this issue in the core Strapi's repository ?


Improve the cookbook about creating a fixer

use relative links so that it links to the code of the same version than the doc being displayed
update coding standards so that code snippets pass the CS fixing done by Travis if they were to be submitted as a PR.

@keradus I intentionally submitted it to 1.4 because I think documentation updates make sense in branches to be released.

@keradus updated

:+1: but i'd prefer this to go into 1.5. It's not a bug fix, and is excluded from the actual release downloads.

@GrahamCampbell The goal is to have it for people reading the online doc in the right way, i.e. for the same version than the code they are using.

@stof The 1.4 branch will be deleted shortly.

There will never be a 1.4.1 release. Only 1.4.0 and 1.5.0.

@GrahamCampbell this does not prevent people from reading the doc for the 1.4.0 tag

Yeh, but 1.4 is meant to be closed for cosmetic changes like this.

Infact, most people will fall into the trap of reading the master branch and think it applies to 1.3...

If there were some bug etc in docs - yeah, merge it into 1.4.
Here - it... may be consider as bug, currently one switch to old version (tagged or not), and have a link for files at master.
It's not a feature or refactoring, just fixing docs, no regression needed.
Set milestone as 1.4
:+1:

Thank you @stof.


Spark SQL support

@KoopaKing @krousey
A minimum set of tasks to start with:

[ ] support deployment of the Thrift JDBC/ODBC server on Kubernetes
[ ] support specification and execution of SQL queries through Kubernetes custom resources

Hi guys,
I'm wondering what's the status of this ticket, is it still ongoing?

@liyinan926 Any update on the support for Thrift JDBC/ODBC server on Kubernetes?

I would also be interested in this.

Same here, a JDBC/ODBC support would be cool! :+1: I didn't dig it yet but I'm ready to help!

How do I use a shell script to submit a Spark Sql task, you can give an example


Allow overriding ctrl manager graceful shutdown timeout

Overriding the default GracefulShutdownTimeout option given to the controller manager with a default of 0 (no timeout) since the helm operations are sensitive to interruption and can lead to leaving the HelmRelease in a bad state.
This will also allow users to override the option via a CLI flag -graceful-shutdown-timeout how much time to wait before forcibly exiting.

I've added a commit to remove the readinessProbe as well since without this change graceful shutdown won't work anyway.
The alternative would be to adjust its failureThreshold so it allows the container to run for a longer period of time (needing to match the terminationGracePeriodSeconds which we have set to 600 by default) before being terminated, but I don't think this is quite the right solution.
All in all, I don't really think there's much value in having the readinessProbe configured because the helm-controller does not expose a service endpoint and thus readiness doesn't quite make sense anyway in its runtime lifecycle context.

Sorry for the late reply, was floored by COVID the past couple of days.
I am concerned about the readiness probe being removed for scenarios in which someone has configured multiple replicas, as this would report the non-elected Pod as being Ready while it is not actually handling reconciliation requests. Which does touch the runtime lifecycle context without it exposing a Service endpoint.

I don't think we should remove readiness in this PR. Id we decided to do this, it should be done across all controllers which don't have ClusterIP services like KC, IRC, IAC.

Sorry for the late reply, was floored by COVID the past couple of days.

No worries, I'm sorry to hear that, hope you're feeling better now!
Thanks for the feedback. I agree with both of your assessments. I think ideally this problem should be addressed somehow at the level of the controller-runtime, having the behavior changed so the probes are not shut down during graceful termination.
Going to remove the second commit.


Any way to skip files/folders from parsing?

I use Visual Studio Code to work with WordPress projects. My workspaces are usually within the WordPress root folder. This problem with this setup is that the language server parses all the files inside the workspace.
Is there a way to exclude some of these files or folders from the parser?

Duplicate of #159


Adding a timer to delay ui server startup

Checklist:

[ ] The code follows our code conventions.
[ ] Important principle changes have been documented in the wiki.
[ ] The new code is covered by unit tests with assertions.
[x] The behaviour node and UI have been manually tested and is as expected.
[ ] The squash commit message follows our conventions.

work done within https://github.com/my-cloud/ruthenium/pull/186


"OBJC_CLASS$_RNGoogleSignin", referenced from:  objc-class-ref in AppDelegate.o

Error:
"_OBJC_CLASS_$_RNGoogleSignin", referenced from:  objc-class-ref in AppDelegate.o

This is happening during the end of the iOS build process.
Header Search Paths:

Link Binary with Libaries:

Podfile:
pod 'GoogleSignIn'
Environment
Please provide the version of your

react-native: 0.50.4
react-native-google-signin: 0.12.0
react: 16.0.0-alpha.12

please follow the automatic configuration guide or linking manual linking causes issues also your link binaries should look like this

You should either use pods or link the GoogleSignIn manually. Do not use both.

Closing due to inactivity, please re-open if this issue still persists.


Release notes formatter

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #907

[x] Tests for the changes have been added (for bug fixes / features)
[x] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)

[x] Link to issue (:issue:number) and pull request (:pull:number) has been added.

[ ] bumpversion patch has been called on this branch
[x] The relevant author information has been added to .zenodo.json

What kind of change does this PR introduce?

Fixes various existing issues in the release notes (missing spaces, subsection formatting)
Addd a helper function under formatters for generating release notes
Adds a CLI utility for generating RST- or markdown-formatted release notes

Does this PR introduce a breaking change?
No.
Other information:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 32 (28.13%)  changed or added relevant lines in 2 files are covered.
18 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.3%) to 90.092%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

xclim/cli.py
7
17
41.18%

xclim/core/formatting.py
2
15
13.33%

Files with Coverage Reduction
New Missed Lines
%

xclim/core/locales.py
1
90.2%

xclim/core/units.py
1
89.8%

xclim/indices/fwi.py
1
96.11%

xclim/indices/run_length.py
1
94.61%

xclim/core/indicator.py
2
96.53%

xclim/core/utils.py
12
68.44%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
12612

Relevant Lines:
13999

💛  - Coveralls

@aulemahal I'm running tests over the CLI API, but coverage isn't registering it. Am I missing something?

Well, I'm not sure... If it counts the other cli calls, why not the new one? I do remember having issues with this, but the memory is fuzzy...


chore(deps) Dependency Bumps [chain-chores]

Generated with chain-chores
Changes:

tendermint/tendermint v0.34.15 -> tendermint/tendermint v0.34.23

@Reecepbcups @faddat We have these on our develop branch for our next on-chain release.


[Added] create and joinRoom UI

wahh bete moj kardi :)
On Sat, Sep 18, 2021 at 2:07 PM Prince Lakhani @.***>
wrote:

Merged #2 https://github.com/krishnan-tech/ChatCode/pull/2 into main.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/krishnan-tech/ChatCode/pull/2#event-5322705023, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANIAN2BZQUH7MPWECQKAOATUCRFT5ANCNFSM5EI67X2A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


WIP : reorganize and fix tests

@munozariasjm - I'm rewriting tests in a way that makes them suitable for interactive debugging. I hope you are ok with that.
I will now also try to fix CI

hah! found the culprit!!!

This is great!


Feature Request: Add Virtual Representation of Algorithms

added images to the algorithms
solved issue(No):https://github.com/NebulaTris/routeviz/issues/5

The program doesn't work like this , so these images are not apt for visual representation.
A novel idea though.
If you run this program and then add those pictures , I would accept the PR


Kitematic won't list images/containers created manually

On Windows
Do not start Kitematic
Start the VM by docker-machine start default
Pull a container by docker pull
Start Kitematic

The image will not be listed in Kitematic. If I create a container from that image, it won't be listed in Kitematic either.
It would be nice to be able to see those manually created containers in Kitematic.

There's a PR in progress for this - Be on the lookout for future release changelog


Add test to check whether the samplebuilder drops data

This test is successful with v3.0.27.  In v3.0.31, it reports large numbers of dropped packets.
Related to #1839 and #1870.

There's an issue with this test. The buffers will hold back because it cannot tell if the first packet in the sequence is truly the first packet. Only once the packet count holdback is exceeded then the packets will release (and there will always be a hold back until the end because there's no 'flush' mechanism to say EOF on the stream).

That's what the partitionHeadChecker is for.

Just because it's the first packet that arrived is a partition head doesn't mean there isn't a packet that might arrive later / in front of the current head that is also a head. Every audio sample is a "head" for example.

I added your test and made it pass. The issue is during the wrap around which someone else reported not consistently retaining a backlog of packets. You can cancel this PR.

That's great news! Thanks @robin-raymond :)


Is it possible to customize the page count separator message? (i18n)

Hi,  am using the rows-per-page-message prop to change the language. Would it be possible to change the page count separator as well?

I want to change the "of" text to something in a different language
Thanks

@dieguezz Please update to the latest version 1.5.5 then you can use prop rows-of-page-separator-message to customize.


Cmorize 3D variables for MERRA2

I need help in reading and processing 3D variables for the MERRA2 reanalysis. Also any suggestions for CMORIZING ERA5, CFSR and JRA-55 would be very helpful.

To get started with this, maybe @glpotter could create a draft pull request with the updated esmvaltool/cmorizers/data/cmor_config/MERRA2.yml (so it contains the extra variables) and then @valeriupredoi could change the CMORizer code in the same branch so it runs?
@glpotter How experienced are you with Git and GitHub, do you think this could work?

cheers @bouweandela - that's a good idea! @glpotter could you do that? I'd be able to help along the way. As a starting point you can have a look at the ERA-Interim cmorizer, that does do some fixing on the pressure axis https://github.com/ESMValGroup/ESMValTool/blob/main/esmvaltool/cmorizers/data/formatters/datasets/era_interim.py

Some previous work on adding more variables to the MERRA2 CMORizer script has been done in #1865.

Hi @glpotter
You mentioned at the monthly meeting that you had trouble making the esmvaltool data command find your updated MERRA2.yml file, right? Could you check what the output of the command
python -c 'import esmvaltool; print(esmvaltool.__path__[0])'

is? This should point to the GitHub repository with the ESMValtool source code in it. If there is a directory called site-packages somewhere in the path, than you may have forgotten to run the pip install --editable '.[develop]' step in the installation from source instructions.
If this doesn't work, maybe you could set up a meeting with @valeriupredoi to see if you can debug if together?

I thought I submitted a comment to this issue. I'll try it again.
MERRA2.yml.zip
Note the group of commented variables at the end of the .yml file. We need to be able to calculate the differences between several of the fluxes to get the appropriate variable in the Amon table.
Once this is added to the recipe, I can add the 3D variable needed to complete the CMIP5 set.

@glpotter cheers muchly! I am attaching the file in a format that can be opened from the browser. About derived vars eg rsus is a derived var we have in our derivation library - it's also a CMIP5 Amon var, so are rsut, and rsutcs - unless we need a custom derivation for those too, that is. I will set up a PR with this yaml config, and then we can take it from there :beer:
MERRA2.yml.txt


Continuous Integration for Tests

I'd like to have this eventually. Right now though, as I'm the only developer, I've set up a pre-commit script that links to the pre-commit-hook.py script and runs it to make sure all tests pass.

In my fork where I currently port lily to Visual C++ 2015 I use Travis to make sure I don't break Linux too hard: https://github.com/TyRoXx/lily/blob/34ae63e0af83bca83156d47810a7ba3c639e8735/.travis.yml
I also use Appveyor, but I have not gotten pre-commit-hook.py to work on Windows yet. I can run lily.exe tests individually and they succeed usually, but with Python the child process just prints some generic "file not found" Windows error message to stderr.

Wow! I've been wanting Lily to be ported to Windows for a while now, but simply haven't gotten around to it. That alone is going to be a great help! Truth be told, I can't remember if I ever tested Lily on Windows, so I'm not surprised that the pre-commit-hook.py script is failing.
I'm currently in the process of setting up a development environment on my Windows machine. If I run into the same problem and can figure it out, then I'll send you a PR. You mention that Lily tests pass 'usually', and I'd like to get to the bottom of that as well.

The tests are fine, they to not fail spuriously or something. There was only one failure due to a different behaviour of the VC++ compiler.
I had to change this:
#define lily_move_double(target, raw) \
lily_move(target, (lily_raw_value)raw, VAL_IS_DOUBLE)

Into this:
#define lily_move_double(target, raw) \
lily_move(target, (lily_raw_value){.doubleval = raw}, VAL_IS_DOUBLE)

Otherwise the value would be wrong. I did not analyze this issue further as my quick fix made the test pass. It looks like VC++ cast the double into an integer (the first field of the union) while GCC seems to find the correct field to initialize.

After some trial and error, I managed to get the pre-commit-hook.py script to work. It turns out that shell=True was causing the majority of problems. The rest was a lot of os.sep needing to be peppered in the right places. I've pushed a commit wherein the script runs on my Windows machine and on *nix box too.
Unfortunately, running the script on Windows is troublesome. About a dozen tests are crashing, and one (an importing test) is hanging. My next move is to start combing through the tests and smash any invalid reads/writes/etc. Hopefully fixing those will get the Windows tests to pass.
I've pushed the fix, along with some other fixes. Hopefully you'll be able to merge them into your fork smoothly (I assume that's how it works, but let me know if there's something else I should have done instead).

As of 8d65f8f, both Travis and Appveyor are now building successfully!


Disabling auto-read doesn't seem to work?

I am using 4.1.0.Final from Maven central.
In my application, I disable auto-read after a certain point like this:
channel.config().setIsAutoRead(false);
I do not make any calls to read, yet my application still reads. In my pipeline there is only one ByteToMessageDecoder, and my (sharable) initializer is my server bootstrap's child handler.
Why is this? Can auto-read not be disabled on-the-fly? Is this a bug?
StackOverflow Question: http://stackoverflow.com/questions/37535482/netty-disabling-auto-read-doesnt-work

I will need more infos to help... All I can say is that it works here with the provided info

Am 31.05.2016 um 03:20 schrieb Thomas Nappo<EMAIL_ADDRESS>Reopened #5328.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Answered on stack overflow... please reopen if you think there is a bug


Feat: ng-[event]-prepare class for structural animations (ngIf etc)

A fix / workaround for #12969
We currently don't have any place in the docs that documents the classes ngAnimate adds. At least I can't find it .:o I think it got lost during 1.4. We should add it back so people can find this feature easier.
Idea by @matsko

@petebacondarwin This is a feature that is needed as a workaround for an ngAnimate issue that can't currently be solved in another way. Should we try to get it in before 1.5.0?

Can we include links in the commit messages to the issues and other commits that this is fixing or related to?
If it a fix to a bug then it is fine to put it in 1.5.0.
It is not clear from the tests how this solve the issue in #12969 - we should have some test or at least a description of the issue and how this PR fixes that in the code and/or commit message. (Or am I just missing that?)

It's not a direct fix, more of a workaround.
Basically, you provide a style (e.g. opacity:0) for ng-enter-prepare that makes sure the element is hidden before the animation actually starts. We cannot directly test this, because the flicker does not always appear.

@petebacondarwin I've added an example to the issue https://github.com/angular/angular.js/issues/12969#issuecomment-160612044

OK, so we also need docs for this feature, especially explaining how it can be used to fix problems that might appear like #12969.

I'll add some docs for it tomorrow

@petebacondarwin I've added docs, fancy taking a look?

Will do. Later today

LGTM

@matsko I've noticed that the prepare classes aren't applied to $animateCss based animations. I guess this expected, as they run outside of the animationQueue?


doc: only link the Swagger files that we actually need

Only link the Swagger files that we actually need to reduce
the size of the documentation output.
Signed-off-by: Ruth Fuchss<EMAIL_ADDRESS>

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.9788/

There seems to be something wrong when expanding /1.0/resources - but that isn't due to this change but also occurs in the master docs.
It does NOT seem to be happening on https://linuxcontainers.org/lxd/api/master/ though.
Any ideas?

Yeah, got the same issue here...

@ru-fu I wonder if it's because we're using a different version of the javascript? The one on /lxd/api/master/ must be quite a bit older than the shiny one we have in the PRs.

Running it locally I actually seem to be getting into a javascript loop instead...

I think I know what's going on, we indeed have a loop in our model, but I don't know how to avoid it...
Basically we have ResourcesGPUCard which has a SRIOV member which has a VFs member that's itself a list of ResourcesGPUCard, so that creates a potential loop. In practice it doesn't because a VF will never itself have a VF so SRIOV will always be null on a VF, but I can see how their parser isn't necessarily smart enough :)
What's odd is that it used to work fine and also that our example value put on the VFs entry is null, presumably to avoid such issues in the first place.
@ru-fu any chance you can try older versions of swagger-ui to try and figure out when that may have broken?
They seem to have been doing releases/tags.


Continuous integration

We have a test.py, why not add some CI? Will help us when we have more contributors.

@elsehow Apparently only a repo administrator can do the initial setup for Travis. How do you want to proceed?

I added enabled the repo in Travis's UI. It looks like .travis.yml should handle everything else

Closed by a314082ece3b00618e5022806df19b8476591db1


Remove warnings about redux-react (it's gone)

https://www.npmjs.com/package/redux-react -> 404
https://github.com/cgarvis/redux-react -> 404

:+1:


Possible convergence for URLs for redis with sentinel

Hi,
we've recently started using  https://github.com/dealertrack/celery-redis-sentinel
which has a different syntax for pointing to a redis with sentinel : https://github.com/dealertrack/celery-redis-sentinel#usage
Any thoughts on that syntax ? Maybe we could get the projects to converge towards a common syntax ?

Have you tried discussing your schema syntax with the authors/maintainers of https://github.com/andymccurdy/redis-py  ?

Hi @arthurlogilab,
CC @antirez, @miki725
we can definitely define a common syntax for redis sentinel connection strings if there is enough interest. There is also https://www.iana.org/assignments/uri-schemes/prov/redis that might be updated as a result.
I see you also created https://github.com/dealertrack/celery-redis-sentinel/issues/17. Might be good idea to move this discussion to the redis mailing list. I'm in a hurry now, so replying here instead.
The URL (or connection string) scheme in this package was defined so that there is only a single connection string to specify the sentinel hosts instead of having to specify the sentinels separately (as is the case in celery-redis-sentinel), similarly to MongoDB connection strings.
It is worth considering also redis-sentinel instead of redis+sentinel as the scheme because:

Celery strips the redis+ part from redis+sentinel:// URLs and matches only redis as backend, so if using redis+sentinel:// scheme, you need to replace/monkey-patch the internal redis celery backend
Celery also sanitizes the result backend URL internally, so the URL specified in CELERY_RESULT_BACKEND must be real valid URL and can only contain a single host:port pair (or just host), so if using multiple host:port pairs, the url must be specified in a separate configuration variable in this case

Personally, I like the redis+sentinel variant slightly more, as it is similar to specifying transports in git urls, for example.


Commercial usage

Is this model available for commercial use ?
https://learnopencv.com/yolo-nas/  This portal mentions non Comm but license Apache 2 says commercial.

@BloodAxe @ofrimasad @jonathan-sha @spsancti

Hi!
You can use SuperGradients' source code to train your own YOLO-NAS from scratch for commercial use, as SuperGradients is under Apache license.
You cannot, however, use our pretrained YOLO-NAS weights for commercial use as they are under a different license.
https://github.com/Deci-AI/super-gradients/issues/901

*Note that besides YOLO-NAS, our other pre-trained models (YoloX, PPYoloE, ... ) are available for commercial use (see model zoo)

If we use the pre-trained models for knowledge distillation to pre-train the Yolo-NAS from scratch, we're not strictly using the weights. In this case, can we get round the licence ?

@NeovMs this is not a legal advice, you should talk to real lawyers, but for my perspective KD still uses pretrained weights and this training regime still falls under license listed here.


DO NOT MERGE - testing

Release note:

This change is

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
ab6dc645e6836b1af757e7331b78f74b37da1c0f
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

Awesome!

/test mixer-e2e-smoketest

/test all
check if new e2e cluster works

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
ab6dc645e6836b1af757e7331b78f74b37da1c0f
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
ab6dc645e6836b1af757e7331b78f74b37da1c0f
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
ab6dc645e6836b1af757e7331b78f74b37da1c0f
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Working as intented!

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
ab6dc645e6836b1af757e7331b78f74b37da1c0f
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Missing license file headers

JIRA Ticket: N/A
What does this Pull Request do?
Add missing license file headers.
How should this be tested?
N/A
Test coverage
N/A
Interested parties
@cvicary

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.667%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
148

Relevant Lines:
150

💛  - Coveralls


The bounds calculcation is failing for sliders

Seen
Max value of AirTankers is 21...
Expected
Max value should be 5 (see graph)

Think this is working correctly. The maximum value is 27


⚠ API - Lens has degraded performance

In a498073, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 315 ms

Resolved: API - Lens performance has improved in 73ea74a after 6 minutes.


Add flake8-pie single_starts_ends_with

Check for things like:
url.startswith("http") or url.startswith("ftp")

which can be simplified to:
url.startswith(("http", "ftp"))

rel: https://github.com/charliermarsh/ruff/issues/1543

Thanks!


Dun goofed. I deleted the master branch on my repo. Didnt know it would cancel the pull request. On to the next try

I reiterated the changes and pushed it to feature/upstream. I still have to check if it works, but maybe you can check that as well.

Merged. Thanks!


Promise misconfigured with Webpack

Guys, why???
When upgraded do 1.3, I got

Which is this line

Then I tried to fix my webpack config, so now, it's purely requiring it
export { default as ldb } from 'localforage';
I have defined Promise with webpack ProvidePlugin

And when debbuging:

Promise has two values, Promise.Promise seems to be the one I defined...
How can I fix this?
Thanks!

Just to be clear, you're including dist/localforage.js?
I would have thought to include localforage you'd want:
import { default as ldb } from 'localforage';

Maybe I'm confused; sorry not super skilled with webpack yet :worried:

Hey, yes, I checked that 'localforage' is resolved to dist/localforage.js
Thanks!

Oh, did that solve the problem?

No, sorry! I meant that I've checked it before...
I cant tell if webpack is messing up with the polyfill included on the dist file with the one that I defined, or it is having problems defining it inside the code.
I'll try to debug it a little more...

Because localForage includes its own polyfill it might be a bit confused.
I wonder if importing src/localforage.js instead might work if you’re defining your own webpack config? If it does I can update the docs to say so…
If you try that let me know. Sorry about the error!

To use the src/localforage.js I would have to allow it to use babel, and also all the files which it includes, so I think that I should instead figure out some way of validating this issue and help you wrap the loader
I'll be updating this!

So, I dont think that the Promise polyfill can be used the way it is defined, could you confirm that to me?
https://github.com/mozilla/localForage/blob/master/dist/localforage.js#L690
They are in different scopes and different packaging machanisms.
Not that it would resolve my problem, but I think you should remove the "concat" part of the build (to create the promise polyfill) and require it manually at src/localforage.js.
This way, webpack would automatically include the copy on the dist/localforage.js.
In this case, the Promise variable that I am able to use is the one I defined, which is misconfigured.
Unfortunately, even defining the Promise variable manually, the code breaks and gives me "No available storage method found.(…)" when I try to use it.

Hi there @TCMiranda
If you're defining your own promise polyfill in your configuration, then how about targeting the .nopromises.js dist file? Requiring localforage with the webpack script loader plugin might also be a secondary solution for your problem.
In 1.3 we stopped requiring the promise polyfill inside the code since requiring polyfills is often criticised as an antipattern and should be avoided (the code should not be coupled with a polyfill, we have tooling for that). So, for the simple use case of the library ("drop it in and it should work") we are using concat to prepend the promise polyfill and prepare the exexution environment before actually defining localforage.
That way, we also allow people to repack the src files using a different or no polyfill.
Waiting for your feedback!

Hi @thgreasi
I Managed to solve my problem when requiring localforage via script-loader after defined Promise globally, not by ProvidePlugin.
Thanks for the help!

Great! Glad to hear that!
On Sat, Oct 10, 2015, 23:14 Tiago de Carvalho Miranda <
<EMAIL_ADDRESS>wrote:

Hi @thgreasi https://github.com/thgreasi
I Managed to solve my problem when requiring localforage via script-loader
after defined Promise globally, not by ProvidePlugin.
Thanks for the help!
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/localForage/issues/465#issuecomment-147122303
.

--
Thodoris Greasidis
Computer, Networking &
Communications Engineer


Open files in read-only mode in packviews

That's what we originally did, but I believe @manasdk had a specific reason to also open in write mode.
Apparently if you don't open it in write mode you can't read metadata (modified time, etc.). I personally haven't verified / tested that.

We can revert it if that's the case, but I want us to hit and investigate the problem once again since it's important for https://github.com/StackStorm/st2-packages/issues/99. If write permissions are required, we don't really have a choice.

https://stackstorm.slack.com/archives/stackstorm/p1454449537004428


Go to definition inconsistent behavior

Environment data

Language Server version: <IP_ADDRESS>
OS and version: Ubuntu 18.04
Python version (& distribution if applicable, e.g. Anaconda): Anaconda python 3.7.4

Go to definition behavior is inconsistent.
I am reading detectron2 code.
In detectron2/tools/train_net.py, Go to Definition can jump to source code of  "default_argument_parser" , but jump to import statement of "launch"

Expexted  Behavior
I appreciate Go to Definition could jump to the source code other than import statement.

It seems to be in source in https://github.com/facebookresearch/detectron2/blob/master/detectron2/engine/launch.py


(wip) yjdh-649: fix dockerfile on platta

don't use lerna
Hardcode $HOME to /app, as yarn will need to put some stray files inside $HOME
Allow minimal writes to get the frontend server running

Description :sparkles:
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #1596 (4d40e01) into develop (5f932b6) will decrease coverage by 30.30%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop    #1596       +/-   ##
============================================
- Coverage    65.40%   35.09%   -30.31%
============================================
  Files         1044      728      -316
  Lines        28533    14041    -14492
  Branches      2972     2972
============================================
- Hits         18661     4928    -13733
+ Misses        9421     8662      -759
  Partials       451      451

Impacted Files
Coverage Δ

...c/__tests__/utils/components/get-index-page-api.ts
99.24% <0.00%> (ø)

backend/kesaseteli/applications/models.py

backend/benefit/common/localized_iban_field.py

...shared/shared/audit_log/migrations/0001_initial.py

...seteli/applications/tests/test_applications_api.py

backend/benefit/messages/models.py

...ator/migrations/0003_changes_for_calculator_api.py

...efit/applications/tests/test_application_status.py

...d/benefit/applications/services/csv_export_base.py

...ns/migrations/0010_update_summer_voucher_fields.py

... and 307 more

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


Accessing web portal on different route

I'd like it to live alongside my other projects on localhost/adsbwebportal for example... Is there an easy way to make that? Thanks!

You could configure lighttpd run your other project as a virtual host.
Do a search for "setup virtual host on lighttpd" using your favorite search engine to find out how.


Explicitly require barcode type (barby no longer does this by default)

Barby no longer requires the various symbology types by default, meaning that we need to explicitly require the type as part of the configuration. Following your lead, I've required the type in the same fashion that you've required the outputter. Pretty straight forward.
Also, I updated the read me to explain why this is a good gem to use with heroku. I actually tried a few options before arriving at has_barcode. I think this little addition would be helpful.
Thanks for building this!
Cory

Added another commit. It appears support or code_128 had broken. If you have a look at the most recent version of barby, you'll notice that you now need to pass a second argument specifying a type (either A, B, or C).
Honestly, I didn't bother to understand the subtly between the three types. Defaulting to A seems to do the trick.

Thanks for your patch! This all looks awesome but I'm not sure SVG is a reasonable default. While it suits heroku, I would expect a GIF on PNG as default, no?
This lib is old an could use some love. Maybe a railtie setup or something - what version of Rails are you running it on if you don't mind me asking?
Best,
Dan

Glad you're still maintaining it. I was a bit worried there'd be no response since it hadn't been active in a while. In response to your questions:

I'm not suggesting that svg be the default. It makes sense for heroku and I think it's nice to give heroku users a heads up that svg is a good fit given the file system constraints. But as for the default, I really don't care. Whatever you think is best.
I'm using Rails 3.0.10 and Ruby 1.8.7 (heroku stack bamboo-ree-1.8.7).

Also, I agree. It's a good little library but it's age shows in some places. For example, I didn't mess with the tests because not having a Gemfile made tracking down the dependencies too much work. (Honestly, it probably would have been easy. I was just being lazy.) That said, I found the code easy to understand. Either way, a little TLC would be nice.
Also, maybe you should fork barby and edit the readme to give a mention to this gem. barby needs something like has_barecode. Powerful as it may be, the API seems weird and more obscure than it should be. has_barcode fixes that.

thanks so much for your feedback! I'll try to carve out some time to make some of the adjustments and issue a pull request on barby to update his readme like you suggested!
Glad you found the lib useful!


After change file .js (import (css, less, scss)), webpack result is error.

This is my project: https://gitlab.com/EricAdonis/webpack-cra
Can someone help me. I really need help. I thank you very much if you support me.

Do you want to request a feature or report a bug?

report a bug.

What is the current behavior?

I'm working on a project boilerplate with webpack (optimized for bundler) but I have a very strange error in during installation.

If the current behavior is a bug, please provide the steps to reproduce.

step 1: yarn
step2: yarn start (it work)
step3: change file app.js (it not work)
step4: change file app.js (it not work)
I'm working on a project boilerplate with webpack (optimized for bundler) but I have a very strange error in during installation.
After the first run, it work.

But after i changed file app.js, hot reload worked and reloaded, but it thrown an error as below.

And so on, after each change file *.js, it thrown an error

What is the expected behavior?
After hot reload applied, js,css bundler file built successfully.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
webpack version: lts
Node.js version: 10.16.2
Operating System: Ubuntu
MyConfig:

const path = require('path')
const webpack = require('webpack')
const { CleanWebpackPlugin } = require('clean-webpack-plugin')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const TerserPlugin = require('terser-webpack-plugin')
const OptimizeCSSAssetsPlugin = require('optimize-css-assets-webpack-plugin')
const cssnano = require('cssnano')
const AutoDllPlugin = require('autodll-webpack-plugin')

const postcssLoader = {
  loader: 'postcss-loader',
  options: {
    ident: 'postcss',
    plugins: [
      require('autoprefixer')
    ]
  }
}

const pluginsOfProc = [
  new MiniCssExtractPlugin({
    filename: 'static/css/[name].[hash].css',
    chunkFilename: 'static/css/chunk/[id].[hash].[contenthash].chunk.css',
    ignoreOrder: false
  }),
  new OptimizeCSSAssetsPlugin({
    cssProcessor: cssnano,
    cssProcessorOptions: {
      discardComments: {
        removeAll: true
      }
    }
  }),
  new AutoDllPlugin({
    inject: true,
    filename: '[id].[hash].dll.js',
    path: 'static/dll',
    entry: {
      vendor: [
        'react',
        'react-dom'
      ]
    }
  })
]

const _default = isDev => ({
  cache: true,
  mode: isDev ? 'development' : 'production',
  entry: path.resolve(__dirname, '../src/index.js'),
  output: {
    path: path.resolve(__dirname, '../dist'),
    filename: 'static/js/[name].[hash].js',
    chunkFilename: 'static/js/chunk/[id].[hash].[contenthash].chunk.js',
    publicPath: '/'
  },
  module: {
    rules: [
      {
        oneOf: [
          {
            test: /\.css$/,
            use: [
              { loader: isDev ? 'style-loader' : MiniCssExtractPlugin.loader },
              { loader: 'css-loader', options: { importLoaders: 1 } },
              {...postcssLoader}
            ]
          },
          {
            test: /\.scss$/,
            use: [
              { loader: isDev ? 'style-loader' : MiniCssExtractPlugin.loader },
              { loader: 'css-loader' },
              {...postcssLoader},
              { loader: 'sass-loader' }
            ]
          },
          {
            test: /\.less$/,
            use: [
              { loader: isDev ? 'style-loader' : MiniCssExtractPlugin.loader },
              { loader: 'css-loader' },
              {...postcssLoader},
              { loader: 'less-loader' }
            ]
          }
        ]
      },
      {
        test: /\.(js|jsx)$/,
        exclude: /(node_modules)/,
        use: [
          {
            loader: 'thread-loader',
            options: {
              workers: require('os').cpus(),
              workerParallelJobs: 2
            }
          },
          {
            loader: 'babel-loader',
            options: {
              cacheDirectory: true,
              presets: [
                '@babel/preset-env',
                '@babel/preset-react'
              ],
              plugins: [
                'react-hot-loader/babel',
                [
                  '@babel/plugin-proposal-decorators',
                  { legacy: true }
                ],
                [
                  '@babel/plugin-proposal-class-properties',
                  { loose: true }
                ],
                '@babel/plugin-transform-runtime'
              ]
            }
          }
        ]
      },
      {
        test: /\.png$/,
        use: [
          {
            loader: 'url-loader',
            options: {
              mimetype: 'image/png'
            }
          }
        ]
      },
      {
        test: /\.svg$/,
        use: 'file-loader'
      },
      {
        test: /\.html$/,
        use: [
          {
            loader: 'html-loader',
            options: {
              minimize: true
            }
          }
        ]
      }
    ]
  },
  resolve: {
    modules: [
      path.resolve(__dirname, '../src'),
      path.resolve(__dirname, '../node_modules')
    ],
    extensions: ['.js', '.jsx'],
    alias: {
      'react-dom': '@hot-loader/react-dom'
    }
  },
  devtool: isDev ? 'cheap-module-eval-source-map' : '',
  devServer: {
    port: 10000,
    contentBase: path.resolve(__dirname, 'dist'),
    historyApiFallback: true,
    hot: true,
    hotOnly: true,
    compress: true,
    inline: true
  },
  plugins: [
    new CleanWebpackPlugin(),
    new HtmlWebpackPlugin({
      template: path.resolve(__dirname, '../public/index.html'),
      inject: true
    }),
    new webpack.optimize.MinChunkSizePlugin({
      minChunkSize: 512
    }),
    ...(isDev ? [
      new webpack.AutomaticPrefetchPlugin(),
      new webpack.HotModuleReplacementPlugin()
    ] : pluginsOfProc)
  ],
  optimization: {
    moduleIds: 'hashed',
    runtimeChunk: 'single',
    splitChunks: {
      cacheGroups: {
        vendor: {
          test: /[\\/]node_modules[\\/]/,
          name: 'vendors',
          chunks: 'all'
        }
      }
    },
    ...(isDev && {
      usedExports: true
    }),
    ...(!isDev && {
      minimizer: [
        new TerserPlugin({
          cache: true,
          parallel: true
        })
      ]
    })
  }
})

module.exports = { _default }

What is the expected behavior?

Why you ignore this?

If the current behavior is a bug, please provide the steps to reproduce.

Why you ignore this? Issue was closed again, if you don't fix this. Where example of configuration? Files what you have? Other information? How we should help you?

I have to link my repo "https://gitlab.com/EricAdonis/webpack-cra" in issues and image of steps to reproduce.

Could you try removing the AutomaticPrefetchPlugin?

Could you try removing the AutomaticPrefetchPlugin?

I love you, thanks you very much. But you can gave me know the reason.

Looks like a bug. AutomaticPrefetchPlugin should not allow to apply loaders via config to the requests. I think it could be fixed by changing:
https://github.com/webpack/webpack/blob/c841887afd8371f327a52e96c6a96f900a7252bc/lib/AutomaticPrefetchPlugin.js#L47
- new PrefetchDependency(m.request),
+ new PrefetchDependency(`!!${m.request}`),

Thanks you @sokra .

Send a PR

bump

@EricAdonis friendly ping, can you create reproducible test repo?

https://github.com/webpack-contrib/css-loader/issues/1243#issue-777455402
How Do We Reproduce?
git clone https://github.com/Talent30/Test
npm i
npm run dev

https://github.com/webpack-contrib/css-loader/issues/1243#issue-777455402
How Do We Reproduce?
git clone https://github.com/Talent30/Test
npm i
npm run dev

remove the AutomaticPrefetchPlugin from config

remove the AutomaticPrefetchPlugin from config

There is a PR that fixes the problem: https://github.com/webpack/webpack/pull/9492
Unfortunately it was never finished...

There is a PR that fixes the problem: https://github.com/webpack/webpack/pull/9492
Unfortunately it was never finished...

@sokra Maybe we can finish it themselves

@sokra Maybe we can finish it themselves

yep, i'll do that

yep, i'll do that


route: Add support of static route in kernel mode

Support add and remove static routes in kernel mode, these are not
supported yet:

route table ID bigger than 255
route weight
route type
route cwnd(congestion window)

Integration test case included.
Resolves: https://issues.redhat.com/browse/RHEL-37665

Please resolve the conflict, I tested the patch, no problem found.

Rebased


Parse JSON of custom response with new version of package

Hello everyone,
For a week, I updated your swift-SDK to match my application with your technology and I develop a version on my application with IBM Watson.
Prior to this update, I analyzed the custom JSON response on my dialog box and it worked fine until the update.
Now I can not parse the JSON response returned by the system because it returns a complex architecture.
You will find my old and new code used below.

Hi @WestFR,
Sorry for the delayed response, I've been on vacation for the Thanksgiving holiday.
The new approach to JSON parsing published with v0.19.0 should be more robust and type-safe than the previous implementations. But I can understand your frustration with the change.
Let me provide an example that may help.
Let's assume that the message response from the service includes the following JSON values.
{
  "context": {
    "custom-string": "this is a string",
    "custom-array": [1, 2, 3],
    "custom-object": { "x": 1 }
  }
}

Then these additional properties can be parsed with the following Swift code.
conversation.message(workspaceID: workspaceID, request: request, failure: failure) {
    response in
    let additionalProperties = response.context.additionalProperties
    guard case let .string(customString) = additionalProperties["custom-string"]! else { return }
    guard case let .array(customArray) = additionalProperties["custom-array"]! else { return }
    guard case let .int(customArray0) = customArray[0] else { return }
    guard case let .int(customArray1) = customArray[1] else { return }
    guard case let .int(customArray2) = customArray[2] else { return }
    guard case let .object(customObject) = additionalProperties["custom-object"]! else { return }
    guard case let .int(x) = customObject["x"]! else { return }
}

Hope that helps!


Space missing before company of speakers

On the tracks and rooms page there is a space missing in front of each speakers company. It should be:
Speaker Name (Speaker Company). Right now it is: Speaker Name(Speaker Company).

@mariobehling  I saw that the tracks.hbs and rooms.hbs has note that not to modify those files. What do I need to change in order to make changes in those templates?

@sumedh123 You will have to change the tracks.hbs and rooms.hbs files. Just add a space between {{name}}{{#if organisation}}({{organisation}}) name and if statement. :)

can I do this?

@mariobehling  Fixed this. PR got merged.

@sumedh123 Thanks. Closing this :)


fix: windows issues

There are multiple issues on windows:

https://github.com/bazelbuild/bazel-skylib/pull/527
https://github.com/cgrindel/bazel-starlib/issues/448
https://github.com/cgrindel/bazel-starlib/issues/449
https://github.com/cgrindel/bazel-starlib/issues/447
https://github.com/cgrindel/bazel-starlib/issues/450

Issues 2-5 above are all fixed by this PR
Test results (windows)
(still filling in these results)
Before
--enable_runfiles 332 failures
--noenable_run
With buildifier_prebuilt update only
--enable_runfiles 116 failures
--noenable_run 154 failures + skips
With this PR only
--enable_runfiles 34 failures
--noenable_runfiles 122 failures + skips
With this PR and https://github.com/bazelbuild/bazel-skylib/pull/527
--enable_runfiles 0 failures
--noenable_runfiles 85 failures
Future activity
Note: most of the --noenable_runfiles failures are of this form. It seems that bzlformat_lint_test.sh is designed to require runfiles.
INFO: From Testing //tests/shlib_tests/lib_tests/files_tests:bzlformat_lint_test:
==================== Test output for //tests/shlib_tests/lib_tests/files_tests:bzlformat_lint_test:
D:/udu/b/356umzpb/execroot/_main/bazel-out/x64_windows-fastbuild/bin/tests/shlib_tests/lib_tests/files_tests/bzlformat_lint_test.sh: line 14: tests/shlib_tests/lib_tests/files_tests/bzlformat_lint_test_BUILD.bazel.sh: No such file or directory
tests/shlib_tests/lib_tests/files_tests/bzlformat_lint_test_BUILD.bazel.sh failed with 127.
1 lint tests failed.
================================================================================

Look into this:
INFO: From Action tests/bzlrelease_tests/rules_tests/generate_workspace_snippet_tests/archive_sha256:
which: no shasum in (/usr/bin:/usr/bin:/bin:/c/WINDOWS:/c/WINDOWS/System32:/c/WINDOWS/System32/WindowsPowerShell/v1.0)

@cgrindel thanks for your review. It looks like a bunch of CI checks failed with an API key error, could you help with that?


feat: allow authz granters to specify forwarding info for token transfer

Description
Apologies for the noise, I made a mess with git and this was the easiest way to recover :)

closes: #6589

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Looks great! Maybe one additional test case we can add is for for hops and allocation hops to have all the same entries, but for a different order.
e.g.
{PortId: ibctesting.MockPort, ChannelId: "channel-1"},
{PortId: ibctesting.MockPort, ChannelId: "channel-2"},

// and
{PortId: ibctesting.MockPort, ChannelId: "channel-2"},
{PortId: ibctesting.MockPort, ChannelId: "channel-1"},

Otherwise looks great, just a few small questions and nits, nice work!

Great idea, added!