video and image issue using self signed certificate with nginx

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version): 0.48.1
Python release (python3 --version): Python 3.4.2
Component/platform: mjpeg
Description of problem:
I'm using nginx in reverse proxy with a require client certificate authentication to reach my hass. I'm using too, a reverse proxy in my internal network to use my camera with last ssl directive as my camera has old ssl . So I can use my camera with ssl whereas they provide actually http. My internal proxy for camera don't use client authentication.
I Follow many posts without success about my problem. The only clue I find is:
https://github.com/home-assistant/home-assistant/issues/1258
I can't see image of cameras, if i click on the first camera I can see video on the second one not. I do internal test and can see video from both camera without using hass.
Expected: See camera image and video if using a reverse proxy as nginx and selmf signed certificate
Additional info:*
first camera log (work with video but no static image)
2017-07-08 11:35:54 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy_stream/camera.camera_entree to <IP_ADDRESS> (auth: False)
2017-07-08 11:35:54 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.camera_entree to <IP_ADDRESS> (auth: False)
2017-07-08 11:35:54 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 345, in _make_request
    self._validate_conn(conn)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 844, in _validate_conn
    conn.connect()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 326, in connect
    ssl_context=context)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/ssl_.py", line 325, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.4/ssl.py", line 364, in wrap_socket
    _context=self)
  File "/usr/lib/python3.4/ssl.py", line 577, in __init__
    self.do_handshake()
  File "/usr/lib/python3.4/ssl.py", line 804, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 438, in send
    timeout=timeout
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 630, in urlopen
    raise SSLError(e)
requests.packages.urllib3.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/homeassistant/.homeassistant/deps/aiohttp/web_protocol.py", line 422, in start
    resp = yield from self._request_handler(request)
  File "/home/homeassistant/.homeassistant/deps/aiohttp/web.py", line 306, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/http/ban.py", line 58, in ban_middleware_handler
    return (yield from handler(request))
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 424, in handle
    result = yield from result
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/__init__.py", line 338, in get
    response = yield from self.handle(request, camera)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/__init__.py", line 358, in handle
    image = yield from camera.async_camera_image()
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/mjpeg.py", line 92, in async_camera_image
    self.camera_image)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/mjpeg.py", line 120, in camera_image
    req = requests.get(self._mjpeg_url, stream=True, timeout=10)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 72, in get
    return request('get', url, params=params, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 518, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 639, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 512, in send

The second one (no image, no video)
Traceback (most recent call last):
  File "/home/homeassistant/.homeassistant/deps/aiohttp/web_protocol.py", line 422, in start
    resp = yield from self._request_handler(request)
  File "/home/homeassistant/.homeassistant/deps/aiohttp/web.py", line 306, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/http/ban.py", line 58, in ban_middleware_handler
    return (yield from handler(request))
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 424, in handle
    result = yield from result
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/__init__.py", line 338, in get
    response = yield from self.handle(request, camera)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/__init__.py", line 358, in handle
    image = yield from camera.async_camera_image()
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/mjpeg.py", line 92, in async_camera_image
    self.camera_image)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/mjpeg.py", line 120, in camera_image
    req = requests.get(self._mjpeg_url, stream=True, timeout=10)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 72, in get
    return request('get', url, params=params, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 518, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 639, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 512, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)
2017-07-08 11:38:12 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy_stream/camera.camera_piscine to <IP_ADDRESS> (auth: False)
2017-07-08 11:38:12 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.camera_piscine to <IP_ADDRESS> (auth: False)
2017-07-08 11:38:12 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 345, in _make_request
    self._validate_conn(conn)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 844, in _validate_conn
    conn.connect()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 326, in connect
    ssl_context=context)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/ssl_.py", line 325, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.4/ssl.py", line 364, in wrap_socket
    _context=self)
  File "/usr/lib/python3.4/ssl.py", line 577, in __init__
    self.do_handshake()
  File "/usr/lib/python3.4/ssl.py", line 804, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 438, in send
    timeout=timeout
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 630, in urlopen
    raise SSLError(e)
requests.packages.urllib3.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/homeassistant/.homeassistant/deps/aiohttp/web_protocol.py", line 422, in start
    resp = yield from self._request_handler(request)
  File "/home/homeassistant/.homeassistant/deps/aiohttp/web.py", line 306, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/http/ban.py", line 58, in ban_middleware_handler
    return (yield from handler(request))
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 424, in handle
    result = yield from result
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/__init__.py", line 338, in get
    response = yield from self.handle(request, camera)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/__init__.py", line 358, in handle
    image = yield from camera.async_camera_image()
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/mjpeg.py", line 92, in async_camera_image
    self.camera_image)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/mjpeg.py", line 120, in camera_image
    req = requests.get(self._mjpeg_url, stream=True, timeout=10)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 72, in get
    return request('get', url, params=params, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 518, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 639, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 512, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

Tell me if you need more explanations or files.
Thank you ,
Sellig28

Hi,
I know it's summer, but some one have a look at my issue ?
Thank you .
Sellig28

Hi,
I've got better result if I use only one proxy, the same as HASS for camera. Now I've got My front camera working but my rear camera only show image but no video.
Some clues ?
Sellig28

Hello
With the last version I have an equivalent issue
`Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.6/site-packages/requests/packages/urllib3/connectionpool.py", line 345, in _make_request
self._validate_conn(conn)
File "/usr/local/lib/python3.6/site-packages/requests/packages/urllib3/connectionpool.py", line 844, in validate_conn
conn.connect()
File "/usr/local/lib/python3.6/site-packages/requests/packages/urllib3/connection.py", line 326, in connect
ssl_context=context)
File "/usr/local/lib/python3.6/site-packages/requests/packages/urllib3/util/ssl.py", line 325, in ssl_wrap_socket
return context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/local/lib/python3.6/ssl.py", line 407, in wrap_socket
_context=self, _session=session)
File "/usr/local/lib/python3.6/ssl.py", line 814, in init
self.do_handshake()
File "/usr/local/lib/python3.6/ssl.py", line 1068, in do_handshake
self._sslobj.do_handshake()
File "/usr/local/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/requests/adapters.py", line 438, in send
timeout=timeout
File "/usr/local/lib/python3.6/site-packages/requests/packages/urllib3/connectionpool.py", line 630, in urlopen
raise SSLError(e)
requests.packages.urllib3.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/app/homeassistant/components/device_tracker/init.py", line 148, in async_setup_platform
platform.get_scanner, hass, {DOMAIN: p_config})
File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in iter
yield self  # This tells Task to wait for completion.
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/device_tracker/ubus.py", line 31, in get_scanner
scanner = UbusDeviceScanner(config[DOMAIN])
File "/usr/src/app/homeassistant/components/device_tracker/ubus.py", line 71, in init
self.password)
File "/usr/src/app/homeassistant/components/device_tracker/ubus.py", line 177, in _get_session_id
password=password)
File "/usr/src/app/homeassistant/components/device_tracker/ubus.py", line 150, in _req_json_rpc
res = requests.post(url, data=data, timeout=5)
File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 112, in post
return request('post', url, data=data, json=json, **kwargs)
File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 58, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 518, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 661, in send
history = [resp for resp in gen] if allow_redirects else []
File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 661, in
history = [resp for resp in gen] if allow_redirects else []
File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 214, in resolve_redirects
**adapter_kwargs
File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 639, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.6/site-packages/requests/adapters.py", line 512, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)
`
It would be great to have a config to remove certificate verification as lots of old device have self signed certificates


sampling is implemented incorrectly

This client sends a sample rate over the wire, but doesn't sample the packets sent. One bad result of this is that e.g. calling count('foo', 1, 0.5) causes foo to be double-counted.
See PR 33, which fixes this issue.

is this project dead?


Document Project Parameters

There are many options available in the Project Editor, and its not clear what the implications
of each option is. For example - Tile Layers can be exported with IDs or Coords. What does that mean? We should try to document those.

closing this as we have a dedicated repo for documentation.


desired_lrps.run_info too small when using MySQL as BBS db backend

We've recently switched from etcd to mysql on our bbs backend, and noticed that it is not possible anymore to run apps on Diego if they have a lot of service bindings and started experience various app restage / push failures.
Tracking down the problem we found out that the table column desired_lrps.run_info is too small on MySQL.
The migration runs the create table statement for desired_lrps regardless of DB with
run_info TEXT NOT NULL

, which on PostgreSQL translates to (almost) unlimited length, but only 65,535 characters on MySQL! 😨
This can easily be filled with apps that have a lot of service bindings for example.
Example output from bbs logfile:
{"timestamp":"1470924426.977551937","source":"bbs","message":"bbs.desired-lrp-handler.desire-lrp.failed-inserting-desired","log_level":2,"data":{"error":"Error 1406: Data too long for column 'run_info' at row 1","process_guid":"ad86073d-a2fb-482f-832b-d3ae5b7834b0-f62a8b72-8190-495a-b653-c2ae5f554d0b","session":"7.62920"}}

diego-release used: 0.1481.0
A possible solution for this problem could be to use different table create statements for PostgreSQL and MySQL, with at least using MEDIUMTEXT as column type for run_info.
Or running an additional migration afterwards (if db==mysql) with an ALTER TABLE desired_lrps MODIFY COLUMN run_info MEDIUMTEXT NOT NULL; or similar.

Closing, as this is fixed in Diego v0.1483.0.
Best,
Eric


Add UI Benchmarks

Part 1 of https://github.com/flutter/flutter/pull/138481
Cherry picking @ignatz work.

Reason for revert: Failing post-submit, see https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8755531866181499153/+/u/run_microbenchmarks/stdout


When detecting "Time Gaps", records without timestamps are flagged.

Scenario:

IsFlagged
Timestamp
Comment

true
1:22:30

true
1:22:40

true
(none)
This record is flagged when it shouldn't be.

true
1:23:00

Implementation Details

This is not a bug, per say.
The real question is: what does it mean if a record does not have a timestamp?

For now we will pretend as though the record does not exist, and continue along with the Time Gap analysis.


Can't get hive database by presto jdbc

Steps

add presto-jdbc-0.217.jar to "lib" dir;
restart davinci;
add datasource and test connect ok;
add view and select 'presto datasource', there is no schema list .

How can I solve this problem

How can I solve this problem


ERROR: Unable to determine second key 'virtual_machine' for virtual machine interface 'None', got: None

Hello,
Thank you for this script which works very well,
I am just ending up with some issues which seems to be marginal but still, would like to get to the bottom of it:
2020-11-19 17:59:02,479 - ERROR: Unable to determine second key 'virtual_machine' for virtual machine interface 'None', got: None
2020-11-19 17:59:02,479 - ERROR: This could cause serious errors and lead to wrongly assigned object relations!!!
2020-11-19 17:59:02,480 - ERROR: Unable to determine second key 'virtual_machine' for virtual machine interface 'None', got: None
2020-11-19 17:59:02,480 - ERROR: This could cause serious errors and lead to wrongly assigned object relations!!!
2020-11-19 17:59:02,480 - ERROR: Unable to determine second key 'virtual_machine' for virtual machine interface 'None', got: None
2020-11-19 17:59:02,480 - ERROR: This could cause serious errors and lead to wrongly assigned object relations!!!
2020-11-19 17:59:02,480 - ERROR: Unable to determine second key 'virtual_machine' for virtual machine interface 'None', got: None
2020-11-19 17:59:02,481 - ERROR: This could cause serious errors and lead to wrongly assigned object relations!!!
2020-11-19 17:59:02,481 - ERROR: Unable to determine second key 'virtual_machine' for virtual machine interface 'None', got: None
2020-11-19 17:59:02,481 - ERROR: This could cause serious errors and lead to wrongly assigned object relations!!!
2020-11-19 17:59:02,481 - ERROR: Unable to determine second key 'virtual_machine' for virtual machine interface 'None', got: None
2020-11-19 17:59:02,481 - ERROR: This could cause serious errors and lead to wrongly assigned object relations!!!
2020-11-19 17:59:02,488 - ERROR: Unable to determine second key 'device' for interface 'None', got: None
2020-11-19 17:59:02,488 - ERROR: This could cause serious errors and lead to wrongly assigned object relations!!!

Thank you for testing.
I just merged the latest cahnges to main.
can you test it again?

Hello,
The issue is gone. Note that after the merge, I had to rollback the settings file because the new one gives me this error:
2020-11-20 11:09:44,356 - INFO: Starting NetBox Sync
HTTPSConnectionPool(host='<IP_ADDRESS>%0a%0aport%20=%20443%0a%0a%0avalidate_tls_certs%20=%20false', port=443): Max retries exceeded with url: /api/ (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f5d1456e240>: Failed to establish a new connection: [Errno -2] Name or service not known',))
I did reflect all the parameters to the new file but unfortunately, it does not work. The previous settings file works fine with the new commit.

Please check your line endings in the configuration.
You are using "\r" but it should be "\n".
can you have a look at this?
Thank you

You are correct, sorry.
Thank you
On Fri, Nov 20, 2020 at 11:10 PM Ricardo<EMAIL_ADDRESS>wrote:

Please check your line endings in the configuration.
You are using "\r" but it should be "\n".
can you have a look at this?
Thank you
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bb-Ricardo/netbox-sync/issues/7#issuecomment-731259284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARZ52GUQMGHY763KDKT6RWDSQ2IGHANCNFSM4T3IAPQA
.

No problem.
Just wondering: How did you eddited the file? Any idea how the different line endigs ended up in your settings file?

Hi Ricardo,
I think it is because I replaced some of the # by space instead of deleting
them... I basically deleted all the spaces and empty lines and the script
went through.
On Mon, 23 Nov 2020, 19:38 Ricardo<EMAIL_ADDRESS>wrote:

No problem.
Just wondering: How did you eddited the file? Any idea how the different
line endigs ended up in your settings file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bb-Ricardo/netbox-sync/issues/7#issuecomment-732136721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARZ52GTMJDBOHXEM22TUPBLSRJJVFANCNFSM4T3IAPQA
.

Thank you for letting me know. I checked and found the issue. The config parser treats indented lines as multi line config.
changed config parser behavior and settings-example.ini

Thanks!!
On Mon, 23 Nov 2020, 20:36 Ricardo<EMAIL_ADDRESS>wrote:

Thank you for letting me know. I checked and found the issue. The config
parser treats indented lines as multi line config.
changed config parser behavior and settings-example.ini
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bb-Ricardo/netbox-sync/issues/7#issuecomment-732165896,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARZ52GU3QQSZVQSEP5I4PM3SRJQMRANCNFSM4T3IAPQA
.


Signature of Register…Server in generated files

Hey @jsmouret, cool stuff!
Sorry if I'm overlooking something obvious, but in your repo, the generated function signatures, e. g., in https://github.com/jsmouret/grpc-over-webrtc/blob/master/server/protos/echo/echo.pb.go#L595, expect an interface { RegisterService(*grpc.ServiceDesc, interface{}) }. When I try to generate code, the same function expects a *grpc.Server, which of course isn't helpful if I want to pass a WebRTC proxy instead. Did you change the generated file by hand, or am I missing something obvious in the generator options?
Thanks!


Added some messaging and meta info

Coverage decreased (-0.1%) to 82.196% when pulling dfd134ce897a52cf108cf8d076b5dff76e1d89c5 on dev into 6c798a9048b5f1ae949ac4055f9ea31620eeb012 on master.


Made "Type" and "Probability" first-class citizens on a TiledMapTile

This way, one can access them by both tile.getProperties().get("type") and tile.getType(). This is closer to the truth given the following .tmx snippet:
<tileset firstgid="1" name="grass-tiles-2-small" tilewidth="32" tileheight="32" tilecount="72" columns="12">
  <image source="grass-tiles-2-small.png" width="384" height="192"/>
  <tile id="13" type="Grass" probability="0.5"/>
</tileset>

As already discussed in #6464 this is not a workable solution. As any class with "Tiled" is a generic tilemap and therefore unrelated to Tiled (tmx). So adding interface variables to that is not good and accessing them via .getProperties() is the intended way.

@lyze237 Totally get that they are too Tiled-specific, which is not intended... But there should be a way to read out type from the .tmx file (just as there will be one to read out probability).
Is this something that we should generalize, for example: looping over all XML properties and adding them to the MapProperties e.q.:
<tile id="13" type="Grass" probability="0.5"/>

would yield properties id = 13, type = "Grass" and probability = "0.5"
This, of course, on top of the existing functionality:
<tile id="13" type="Grass" probability="0.5">
   <properties>
    <property name="myProperty" value="Hello there"/>
   </properties>
</tile>


minimal check for import V3

Branched from #3152.
As it is discussed with @hoytak, @TobyRoseman, and @nickjong in #3156, I provide a simpler version for minimal package lazy import in order to lower the maintenance cost.

update 07/05/2020
This PR aims to provide some instructions to users who install the minimal package but somehow wind up using some ML functionalities.
For example, minimal pkg doesn't have TF installed as its dependency. When a user uses ML toolkit that relies on TF, he/she should see the instruction to install the full package's dependency.
Traceback (most recent call last):
...
ModuleNotFoundError: No module named 'tensorflow'. This is a minimal package for SFrame only, without tensorflow pinned as a dependency. You can try to install all required packages by installing the full package by:
**pip install turicreate==6.2**

Instead of letting them install each package individually, let them install turicreate==VERSION to rely on the full package's requirement list to install all required dependencies.

for 3 files (drawing, activity, and style), at top-level, I wrap
    import tensorflow.compat.v1 as _tf
    # This toolkit is compatible with TensorFlow V2 behavior.
    # However, until all toolkits are compatible, we must call `disable_v2_behavior()`.
    _tf.disable_v2_behavior()

into,
def _lazy_import_tensorflow():
    _tf = minimal_package_import_check("tensorflow.compat.v1")
    # This toolkit is compatible with TensorFlow V2 behavior.
    # However, until all toolkits are compatible, we must call `disable_v2_behavior()`.
    _tf.disable_v2_behavior()
    return _tf

and only for the sound classifier, I wrap
    _utils.suppress_tensorflow_warnings()
    import tensorflow.compat.v1 as _tf
    # This toolkit is compatible with TensorFlow V2 behavior.
    # However, until all toolkits are compatible, we must call `disable_v2_behavior()`.
    _tf.disable_v2_behavior()

into
def _lazy_import_tensorflow():
    # Suppresses verbosity to only errors
    _utils.suppress_tensorflow_warnings()

    _tf = minimal_package_import_check("tensorflow.compat.v1")
    # This toolkit is compatible with TensorFlow V2 behavior.
    # However, until all toolkits are compatible, we must call `disable_v2_behavior()`.
    _tf.disable_v2_behavior()

    return _tf

These should not be considered as the duplicate of code because each tool may have its own settings on tf. Leaving it at the beginning of the file will allow people to know what's the tf configuration more clearly. I only add 2 more lines around. I don't believe that these 2 more lines are considered as the liability I shouldn't put here since people may not be able to maintain it because these 2 lines increase the mental burden on them so that they can't understand it.
Second, if this is considered as the duplicate of code, we wrap all common imports into on function to remove duplicate of import tensorflow orimportosorimport sys`.
@hoytak how do you think?

passed internal tests (112066).

from #3180:

core implementation for lazy import (including comments): 392 lines added
client adoption code: 48 lines added

from this PR:
core implementation for lazy import (including comments): 103 lines added
client adoption code: 165 lines added
The team favors later one is reasonable.

@hoytak @TobyRoseman updated in https://github.com/apple/turicreate/pull/3175/commits/ed670ffe74dd901cf414fe32e95d97c232b440ea, the version of turicreate is also modified to resolve the complaint that,
ERROR: <package> has requirement turicreate==6.1.1+minimal, but you'll have turicreate 6.1.1 which is incompatible.

this https://github.com/apple/turicreate/pull/3175/commits/6d80701e18ffdfc1e37250ce573817f73f4111fe will trim the "+minimal" from local version (the downstream version) to prompt the upstream version to user if they use any ML toolkits from the minimal version.

Good work!  Ready to go.


TRIDENT-18002 - MSSP dashboards

Purpose of this pull request
This pull request (PR) creates a beta article:
https://help.sumologic.com/docs/integrations/sumo-apps/mssp
Issue number: TRIDENT-18002

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

This PR is in draft for SME review.

I'm closing this PR because there is no forward action on MSSP consolidated dashboards. We can always reopen it if needed.


Update mssql driver

Update the mssql-jdbc driver to the latest version (6.1.7.jre8-preview).
Checklist

[x] Unit test all changes
[x] Update README.md if applicable
[x] Add [WIP] to the pull request title if it's work in progress
[x] Squash commits that aren't meaningful changes
[x] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

Does this fix issue with failing build?

https://github.com/getquill/quill/pull/787/files
Look at this one and please update contribution.md

@mentegy Let's keep those changes as separate PR. We will merge it as soon as you will reopen it and update description and comment.

@mxl it doesn't, just updating the driver. Still trying to figure what is the build problem.

@mxl works for me


Fix reliance on static factory [Issue #84]

Addresses https://github.com/spatie/laravel-binary-uuid/issues/84
Fixes reliance on Uuid static factory

Boots a singleton OrderedTimeCodec in service provider
Resolves an instance of the codec for en/decoding UUID
to/from optimised binary

Also change some type comparisons of Uuid objects from Uuid to UuidInterface

This package has been abandoned. Alternatives: https://github.com/michaeldyrynda/laravel-efficient-uuid & https://github.com/michaeldyrynda/laravel-model-uuid


[csrng] implement context-switching capability

Description
Currently CSRNG has a single context. This practically allows only atomic mode of operation:

Instantiate CSRNG in required mode (full entropy or software-only)
Run key generation
Instantiate CSRNG from entropy source (to discard key specific use).

This single context makes impossible to use CSRNG in multi context environment -- you can't rely on the CSRNG state, when use for key gen it can't be used for anything else, but more importantly in current firmware design DRBG objects are used as a common denominator for key generation. These DRBG objects seeded either using live entropy, hw-backed key or with data from software (entropy stored on flash for deterministic key gen), at different time - DRBG mixes in additional data at one time, and used for key generation at some time later, with 2-3 DRBGs being used at the same time.
One approach to separate CSRNG from key gen in time is to use fully software DRBG to mix in all key inputs, including derivations from hw_backed keys, and implement cascading DRBG, where randoms from software DRBG will seed CSRNG just before the key gen using software-only inputs.  This approach an issue that DRBG state is unprotected in software,  and more complicated than it can be.
Proposal: implement load/store of CSRNG context in a blinded form, may be bundled with integrity checking via checksum or some other light method. This way software can read out CSRNG content, and restore it, but won't be able to actually interpret it or modify it.
There is no need to make context reloadable after power cycle of OT -- some volatile key can be used for encryption.

The root issues is described in #21936. Need for context switching will depend on its resolution.

@vogelpi: This requires making the status registers writeable without an area impact. The change can be applied to just the software instance.
Moving to M3 for triaging and implementation target.
@moidx This change will simplify integration with use cases potentially dropping the requirement for a SW based DRBG.

it seems CSRNG already supports contexts for applications and EDNs, but they are implicit. If it would be possible to add 1-3 application contexts and make instantiate/generate/reseed command to refer which one to use - this would address the need.

Adding more hardware contexts is unfeasible for production, from an area, implementation and verification point of view. What could be feasible is to allow software extracting and writing the context of the software instance. Extracting the data is already possible for KATs. Making it writable seems doable.
Everything else is not realistic. This also includes adding context switch capability to the hardware contexts. Because software has no control over when hardware requests updates to these instances.