Tests in test_pageserver_layer_rolling.py are flaky because of busy asyncio event loop

Tests, contained in test_pageserver_layer_rolling.py, fail from time to time due to timeout errors, e.g.:
test_idle_checkpoints:
https://neon-github-public-dev.s3.amazonaws.com/reports/pr-9364/11918318765/index.html#/testresult/aec5a540569b483a
asyncio.exceptions.TimeoutError
Duration 1m 17s (11/19/2024 20:47:59 – 20:49:17)
2024-11-19 17:47:59.656 INFO [paths.py:171] test_output_dir is /tmp/test_output/test_idle_checkpoints[debug-pg17]-1
...
2024-11-19 17:48:13.796 INFO [neon_cli.py:72] Running command "/tmp/neon/bin/neon_local endpoint create --tenant-id d6de2907d8d32165210733931d2c22f6 --branch-name main --pg-version 17 --pg-port 30036 --http-port 30037 ep-1"
...
2024-11-19 17:49:15.538 INFO [neon_cli.py:72] Running command "/tmp/neon/bin/neon_local endpoint create --tenant-id e17b85bc8079ae87038b1843b713d615 --branch-name main --pg-version 17 --pg-port 30054 --http-port 30055 ep-10"
2024-11-19 17:49:15.580 INFO [neon_cli.py:72] Running command "/tmp/neon/bin/neon_local endpoint start --safekeepers 1 ep-10"
    ### starting 10 endpoints (see run_worker_for_tenant()) took a minute, then the timeout occurred, and now all endpoints stopping because of that
2024-11-19 17:49:16.81  INFO [neon_cli.py:72] Running command "/tmp/neon/bin/neon_local endpoint stop --mode=fast ep-1"

https://neon-github-public-dev.s3.amazonaws.com/reports/pr-9190/11125343633/index.html#/testresult/f1f3c162de6020a
asyncio.exceptions.TimeoutError
Duration: 1m 17s  (10/1/2024 16:00:38 – 16:01:55)
2024-10-01 13:00:38.89  INFO [neon_fixtures.py:4742] get_test_output_dir is /tmp/test_output/test_idle_checkpoints[release-pg14]
...
2024-10-01 13:00:47.48  INFO [neon_fixtures.py:3993] Starting postgres endpoint ep-1
...
2024-10-01 13:01:49.729 INFO [neon_fixtures.py:1475] Running command "/tmp/neon/bin/neon_local endpoint start --safekeepers 1 ep-10"
2024-10-01 13:01:50.161 INFO [neon_fixtures.py:4172] Postgres startup took 0.47530436515808105 seconds
2024-10-01 13:01:50.165 INFO [neon_fixtures.py:1475] Running command "/tmp/neon/bin/neon_local endpoint stop --mode=fast ep-1"

test_pageserver_small_inmemory_layers:
https://neon-github-public-dev.s3.amazonaws.com/reports/pr-9778/12118589434/index.html#/testresult/aafab3d237d86203
TimeoutError
Duration: 1m 18s (12/2/2024 15:29:36 – 15:30:55)
2024-12-02 12:29:51.844 INFO [neon_cli.py:68] Running command "/tmp/neon/bin/neon_local endpoint start --safekeepers 1 ep-1"
...
2024-12-02 12:30:53.149 INFO [neon_cli.py:68] Running command "/tmp/neon/bin/neon_local endpoint start --safekeepers 1 ep-10"
2024-12-02 12:30:53.596 INFO [neon_fixtures.py:4134] shared_buffers = 1MB
2024-12-02 12:30:53.613 INFO [neon_fixtures.py:4134] neon.max_file_cache_size = 0
2024-12-02 12:30:53.617 INFO [neon_fixtures.py:4134] neon.file_cache_size_limit = 0
2024-12-02 12:30:53.618 INFO [neon_cli.py:68] Running command "/tmp/neon/bin/neon_local endpoint stop --mode=fast ep-1"

test_total_size_limit:
https://neon-github-public-dev.s3.amazonaws.com/reports/pr-9190/11125343633/index.html#/testresult/419df8a960461fd6
asyncio.exceptions.TimeoutError
Duration: 1m 14s (10/1/2024 16:00:24 – 16:01:38)
2024-10-01 13:00:24.82  INFO [neon_fixtures.py:4742] get_test_output_dir is /tmp/test_output/test_total_size_limit[release-pg14]
...
2024-10-01 13:00:31.419 INFO [neon_fixtures.py:3993] Starting postgres endpoint ep-1
...
2024-10-01 13:01:32.338 INFO [neon_fixtures.py:1475] Running command "/tmp/neon/bin/neon_local endpoint start --safekeepers 1 ep-10"
2024-10-01 13:01:32.670 INFO [neon_fixtures.py:4172] Postgres startup took 0.34891724586486816 seconds
2024-10-01 13:01:32.677 INFO [neon_fixtures.py:1475] Running command "/tmp/neon/bin/neon_local endpoint stop --mode=fast ep-1"

With debug logging added:
@@ -28,7 +27,11 @@ async def run_worker_for_tenant(
         offset = 0

     with env.endpoints.create_start("main", tenant_id=tenant) as ep:
+        log.info(f"!!!worker_for_tenant: {tenant}, connecting...")
+        t0 = time.time()
         conn = await ep.connect_async()
+        dur = time.time() - t0
+        log.info(f"!!!worker_for_tenant: {tenant}, connect duration: {dur}")
         try:

and asyncio logging enabled, plus PYTHONASYNCIODEBUG=1, I could see the following:
2024-12-03 14:24:39.216 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: 7dd3823d2f5032a1a5319a52cee1a320, connecting...
2024-12-03 14:24:39.219 DEBUG [base_events.py:881] Get address info localhost:15014, type=<SocketKind.SOCK_STREAM: 1>
2024-12-03 14:24:39.220 DEBUG [base_events.py:891] Getting address info localhost:15014, type=<SocketKind.SOCK_STREAM: 1> took 0.152ms: [(<AddressFamily.AF_INET6: 10>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('::1', 15014, 0, 0)), (<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('<IP_ADDRESS>', 15014))]
...
2024-12-03 14:24:45.173 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: 40051c2401fcc51e53b6eade16f85f36, connecting...
...
2024-12-03 14:25:33.501 INFO [neon_cli.py:68] Running command ".../target/debug/neon_local endpoint start --safekeepers 1 ep-10"
...
2024-12-03 14:25:33.912 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: d049fcf58970ae31f5e0c34c55c00724, connecting...
2024-12-03 14:25:33.914 DEBUG [base_events.py:881] Get address info localhost:15037, type=<SocketKind.SOCK_STREAM: 1>
2024-12-03 14:25:33.914 WARNING [base_events.py:1982] Executing <Task pending name='Task-11' coro=<run_worker() running at .../test_runner/regress/test_pageserver_layer_rolling.py:50> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.12/asyncio/futures.py:387, Task.task_wakeup()] created at /usr/lib/python3.12/asyncio/base_events.py:449> cb=[gather.<locals>._done_callback() at /usr/lib/python3.12/asyncio/tasks.py:767] created at /usr/lib/python3.12/asyncio/tasks.py:420> took 6.566 seconds
2024-12-03 14:25:33.914 DEBUG [base_events.py:891] Getting address info localhost:15037, type=<SocketKind.SOCK_STREAM: 1> took 0.232ms: [(<AddressFamily.AF_INET6: 10>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('::1', 15037, 0, 0)), (<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('<IP_ADDRESS>', 15037))]
2024-12-03 14:25:33.930 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=15, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 43844), raddr=('<IP_ADDRESS>', 15014)> connected to localhost:15014: (<_SelectorSocketTransport fd=15 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x788297e537d0>)
    ### all connections are established only after all endpoints have been started
2024-12-03 14:25:33.931 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=18, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 43226), raddr=('<IP_ADDRESS>', 15018)> connected to localhost:15018: (<_SelectorSocketTransport fd=18 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x788297e53d70>)
2024-12-03 14:25:33.931 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=19, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 45038), raddr=('<IP_ADDRESS>', 15022)> connected to localhost:15022: (<_SelectorSocketTransport fd=19 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x7882979948f0>)
2024-12-03 14:25:33.931 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=20, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 38838), raddr=('<IP_ADDRESS>', 15025)> connected to localhost:15025: (<_SelectorSocketTransport fd=20 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x7882979950a0>)
2024-12-03 14:25:33.931 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=21, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 60164), raddr=('<IP_ADDRESS>', 15027)> connected to localhost:15027: (<_SelectorSocketTransport fd=21 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x788297995c40>)
2024-12-03 14:25:33.931 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=22, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 36356), raddr=('<IP_ADDRESS>', 15029)> connected to localhost:15029: (<_SelectorSocketTransport fd=22 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x7882979969f0>)
2024-12-03 14:25:33.932 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=23, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 42750), raddr=('<IP_ADDRESS>', 15031)> connected to localhost:15031: (<_SelectorSocketTransport fd=23 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x7882979973e0>)
2024-12-03 14:25:33.932 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=24, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 45192), raddr=('<IP_ADDRESS>', 15033)> connected to localhost:15033: (<_SelectorSocketTransport fd=24 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x788297997f20>)
2024-12-03 14:25:33.932 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=25, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 34736), raddr=('<IP_ADDRESS>', 15035)> connected to localhost:15035: (<_SelectorSocketTransport fd=25 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x788297997e90>)
2024-12-03 14:25:33.932 DEBUG [base_events.py:1157] <asyncio.TransportSocket fd=26, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 37492), raddr=('<IP_ADDRESS>', 15037)> connected to localhost:15037: (<_SelectorSocketTransport fd=26 read=polling write=<idle, bufsize=0>>, <asyncpg.connect_utils.TLSUpgradeProto object at 0x788297e72b10>)
2024-12-03 14:25:33.948 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: d049fcf58970ae31f5e0c34c55c00724, connect duration: 0.03528285026550293
2024-12-03 14:25:33.962 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 376927272e16752dacc1245463a83468, connect duration: 24.719107627868652
2024-12-03 14:25:33.963 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 6dd0dc13dbd404c58e062ea5b1a45f65, connect duration: 36.82561278343201
2024-12-03 14:25:33.964 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 20dd747fbb7d2365779056a1eba39254, connect duration: 30.77692198753357
2024-12-03 14:25:33.965 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 7dd3823d2f5032a1a5319a52cee1a320, connect duration: 54.74954867362976
    ### thus, connecting to ep-1 took almost 60 seconds (default connect() timeout)
2024-12-03 14:25:33.966 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 6aa265b5930f48ee1c5faa1993c49f6f, connect duration: 18.712903022766113
2024-12-03 14:25:33.966 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: b91fca3398230e31af37ea7b42b10b85, connect duration: 12.674139261245728
2024-12-03 14:25:33.967 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 40051c2401fcc51e53b6eade16f85f36, connect duration: 48.79380750656128
2024-12-03 14:25:33.968 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 8c3d2a15dae2b506b007a327a6bb501e, connect duration: 42.824520111083984
2024-12-03 14:25:33.969 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 92a66eb8f2025c817259d4d72b4391a8, connect duration: 6.623116731643677

So maybe it would make sense to increase the timeout or switch to synchronous connect(), e.g. as below (I'm not sure whether this hurts the test, but it passes):
     with env.endpoints.create_start("main", tenant_id=tenant) as ep:
-        conn = await ep.connect_async()
+        conn = ep.connect()
         try:
-            await conn.execute("CREATE TABLE IF NOT EXISTS t(key serial primary key, value text)")
-            await conn.execute(
+            cur = conn.cursor()
+            cur.execute("CREATE TABLE IF NOT EXISTS t(key serial primary key, value text)")
+            cur.execute(
                 f"INSERT INTO t SELECT i, CONCAT('payload_', i) FROM generate_series({offset},{entries}) as i"
             )
         finally:
-            await conn.close(timeout=10)
+            conn.close()

which gives the following.
2024-12-03 15:17:03.777 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: 9f4cc386eb978a3b96586c11302c6bb4, connecting...
2024-12-03 15:17:03.796 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 9f4cc386eb978a3b96586c11302c6bb4, connect duration: 0.018440723419189453
2024-12-03 15:17:10.701 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: b68e4ed4e6b806a87d2573943b3320ed, connecting...
2024-12-03 15:17:10.723 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: b68e4ed4e6b806a87d2573943b3320ed, connect duration: 0.022357463836669922
2024-12-03 15:17:17.630 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: 8a9c0c0a12e14228adaa8b0e1dfafc79, connecting...
2024-12-03 15:17:17.648 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 8a9c0c0a12e14228adaa8b0e1dfafc79, connect duration: 0.01814436912536621
2024-12-03 15:17:24.723 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: 1c6459f47abfc82206acfcb654436166, connecting...
2024-12-03 15:17:24.735 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 1c6459f47abfc82206acfcb654436166, connect duration: 0.012577533721923828
2024-12-03 15:17:31.976 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: 480df83fd5df0a0af689591f9b8eb180, connecting...
2024-12-03 15:17:31.994 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 480df83fd5df0a0af689591f9b8eb180, connect duration: 0.017352819442749023
2024-12-03 15:17:39.825 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: f8df05de8d0f00844b6b4a4472217d90, connecting...
2024-12-03 15:17:39.841 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: f8df05de8d0f00844b6b4a4472217d90, connect duration: 0.01585102081298828
2024-12-03 15:17:46.624 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: dd901b88fc97f13b100b663a370ef9ca, connecting...
2024-12-03 15:17:46.642 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: dd901b88fc97f13b100b663a370ef9ca, connect duration: 0.018539905548095703
2024-12-03 15:17:53.565 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: 0130205aadb9395984fabbf71d70afa2, connecting...
2024-12-03 15:17:53.576 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 0130205aadb9395984fabbf71d70afa2, connect duration: 0.01091456413269043
2024-12-03 15:18:01.210 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: b7cfd2376ee0d10215f32c8a5e41a5d1, connecting...
2024-12-03 15:18:01.231 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: b7cfd2376ee0d10215f32c8a5e41a5d1, connect duration: 0.020678997039794922
2024-12-03 15:18:08.189 INFO [test_pageserver_layer_rolling.py:30] !!!worker_for_tenant: 4d2060b9b8d2add8b01fcc6c65dbf729, connecting...
2024-12-03 15:18:08.210 INFO [test_pageserver_layer_rolling.py:34] !!!worker_for_tenant: 4d2060b9b8d2add8b01fcc6c65dbf729, connect duration: 0.020700454711914062

Chi suggests: we're mixing sync and async and something is blocking the 1 executor thread that python has.
Christian: possible we're hitting some connection count limit?
Christian: could be waiting for LSN to arrive on pageserver during the select, and that's blocking other stuff?

There's a blocking call:
        last_flush_lsn = Lsn(ep.safe_psql("SELECT pg_current_wal_flush_lsn()")[0][0])


Fixes #3212 - WhiskConfig should close the property file source

Close the source instance with try-finally usage

Thanks for the fix. I feel a bit uneasy about the testcase though. Seems rather low-level. In this case I could as well live without a testcase.
Thoughts? @rabbah

+1, can live without a test for this - since we're not checking that we're leaking a file resource anywhere else. We could enable resource leak checks more generally.

Okie would update PR with test case removed


Expose JS API for PPX rewriting

Expose a jsxv2 object with a rewrite method to transform OCaml+JSX to pure OCaml, that can be used by JS playgrounds.

This PR aligns reactjs_jsx_ppx_v2.ml in this repository. It contains the changes described in Bucklescript/bucklescript#2151.

Thanks!


Add Visual Element extensions

Documentation added for .NET MAUI Community Toolkit proposals:

[Proposal] Behaviors VisualElement extension https://github.com/CommunityToolkit/Maui.Markup/issues/29

Docs Build status updates of commit 853e13d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/markup/extensions/visual-element-extensions.md
:white_check_mark:Succeeded
View

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

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

File Change Percent
This PR contains file(s) with more than 20% file change.

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

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/markup/extensions/absolute-layout-extensions.md
:white_check_mark:Succeeded
View

docs/maui/markup/extensions/visual-element-extensions.md
:white_check_mark:Succeeded
View

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

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

File Change Percent
This PR contains file(s) with more than 20% file change.

Docs Build status updates of commit 39a8069:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/markup/extensions/absolute-layout-extensions.md
:white_check_mark:Succeeded
View

docs/maui/markup/extensions/visual-element-extensions.md
:white_check_mark:Succeeded
View

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

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

File Change Percent
This PR contains file(s) with more than 20% file change.

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

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/markup/extensions/absolute-layout-extensions.md
:white_check_mark:Succeeded
View

docs/maui/markup/extensions/visual-element-extensions.md
:white_check_mark:Succeeded
View

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

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

File Change Percent
This PR contains file(s) with more than 20% file change.


[v1] Part 3: Great Composed Component Refactor

Description
Part 3: delete ComposedComponent and move all logic to PositionComponent.
Fixes # (issue number, if there is one)
Type of change
Please delete options that are not relevant.

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update (possibly!)

About the toZeroRect name, @spydon and @erickzanardo, I agree it's confusing, I'm bad at naming. the suggestions are, it seems: toAbsoluteRect/toRelativeRect, toRect/toOriginRect and I thought of toRect/toDimensionRect (or toSizeRect) as well. I really don't have any strong preferences, I guess trying to thing as an outsider I would say toOriginRect is the clearest, what do you guys think (origin for me is much more (0, 0) than the anchor)? Open to other suggestions as well from folks.

About the toZeroRect name, @spydon and @erickzanardo, I agree it's confusing, I'm bad at naming. the suggestions are, it seems: toAbsoluteRect/toRelativeRect, toRect/toOriginRect and I thought of toRect/toDimensionRect (or toSizeRect) as well. I really don't have any strong preferences, I guess trying to thing as an outsider I would say toOriginRect is the clearest, what do you guys think (origin for me is much more (0, 0) than the anchor)? Open to other suggestions as well from folks.

I like toOriginRect, but for my "web developer mind", I think toRelativeRect is a little more clearer, but I prefer toOrginRect over toZeroRect

About the toZeroRect name, @spydon and @erickzanardo, I agree it's confusing, I'm bad at naming. the suggestions are, it seems: toAbsoluteRect/toRelativeRect, toRect/toOriginRect and I thought of toRect/toDimensionRect (or toSizeRect) as well. I really don't have any strong preferences, I guess trying to thing as an outsider I would say toOriginRect is the clearest, what do you guys think (origin for me is much more (0, 0) than the anchor)? Open to other suggestions as well from folks.

I like toOriginRect, but for my "web developer mind", I think toRelativeRect is a little more clearer, but I prefer toOrginRect over toZeroRect

Wouldn't the relative part there be thought as relative to the anchor?

yeah that is my fear as well with relative, relative to what? I think personally origin makes it more clear. but again, no strong opinions. @renancaraujo @wolfenrain any thoughts?
otherwise I will go with toRect/toOriginRect and merge

Remember to make prepareCanvas private.


cast from Nil to Crystal::GenericInstanceType+ failed at src/compiler/crystal/types.cr:1361

I mistakenly typed Channel.new(Int32) instead of Channel(Int32).new and got this:
Code:
class Bar
  @bork = Channel.new(Int32)
end

Execution:
 ± crystal doh.cr
cast from Nil to Crystal::GenericInstanceType+ failed, at /private/tmp/crystal-lang-20170420-38199-6yf8tg/crystal-0.22.0/src/compiler/crystal/types.cr:1361
0x10c557cf1: *raise<TypeCastError>:NoReturn at ??
0x10d3144b0: *Crystal::TypeParameter#solve<Crystal::NonGenericClassType>:Crystal::ASTNode+ at ??
0x10d3153e0: *Crystal::GenericInstanceType+@Crystal::GenericInstanceType#replace_type_parameters<Crystal::NonGenericClassType>:Crystal::Type+ at ??
0x10d30fd06: *Crystal::TypeDeclarationProcessor#process_owner_guessed_instance_var_declaration<Crystal::Type+, String, Crystal::TypeDeclarationProcessor::InstanceVarTypeInfo>:(Crystal::MetaTypeVar | Crystal::TypeDeclarationProcessor::Error | Nil) at ??
0x10d2d51e4: *Crystal::TypeDeclarationProcessor#process<Crystal::ASTNode+>:Tuple(Crystal::ASTNode+, Crystal::TypeDeclarationProcessor) at ??
0x10d19d108: *Crystal::Program#top_level_semantic<Crystal::ASTNode+>:Tuple(Crystal::ASTNode+, Crystal::TypeDeclarationProcessor) at ??
0x10d199ca2: *Crystal::Program#semantic<Crystal::ASTNode+, Bool>:Crystal::ASTNode+ at ??
0x10dcd9735: *Crystal::Compiler#compile<Array(Crystal::Compiler::Source), String>:Crystal::Compiler::Result at ??
0x10dd7f8a9: *Crystal::Command#run_command<Bool>:Nil at ??
0x10c59b903: *Crystal::Command#run:(Bool | Crystal::Compiler::Result | IO::FileDescriptor | Nil) at ??
0x10c562b9d: main at ??

Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

Environment:
 ± crystal -v
Crystal 0.22.0 (2017-04-20) LLVM 4.0.0

I can reproduce this.
The correct error would be
can't infer the type parameter T for the generic class Channel(T). Please provide it explicitly

Duplicate of #4604


Create ability to ignore default PII scanning patterns

As a user, I want to be able to stop secureli from scanning for the default PII patterns
AC

Add item to .secureli.yaml called ignore-pii-patterns
ignore-pii-patterns can only accept 'email', 'ssn', 'phone'
if one of these items is included in the secureli congif, ignore that category  when the PII scan runs
a. if there are any items in ignore-pii-patterns beyond the acceptable list, throw an error.
add ability to put new items into config via cli, either with a new flag on an existing command or a new command
a. confirm user's input fits acceptable items, throw an error if it does not
Add note in documentation to notify users of functionality

This was completed in https://github.com/slalombuild/secureli/issues/558.


Fix broken export

Fix #167 and clean up the deprecated code and unused ws websocket library.

As I've removed the deprecated code, this is a breaking change which needs a major version bump.


[Ollama AI] When using a command (for example change tone to professional), with advanced settings/keep alive, error missing unit in duration

Extension
https://www.raycast.com/massimiliano_pasquini/raycast-ollama
Raycast Version
1.76.1
macOS Version
14.5
Description
in the advanced settings, parameter "keep alive". The information icon writed that, for keeping the model in memory indefinitely, one should input "-1". But when doing so, get error : missing unit in duration
Steps To Reproduce

select ollama change tone to professional
click advanced parameters
set keep alive to -1
see error in red at bottom of window

Current Behaviour
No response
Expected Behaviour
No response

@raycastbot assign me

I @lstep, thanks for opening this issue. Ollama now use golang Time.Duration format for keep_alive so unit are required even for negative or zero values. I have fixed this issue on #13047

Pull request #13047 merged

@raycastbot close this issue

Thanks, it has been corrected, except on the "Create Custom Command", still with the old invalid syntax.

Thanks, it has been corrected, except on the "Create Custom Command", still with the old invalid syntax.

I have missed that 😅, fixed on #13069 moving keep_alive info and validation function on a separate file.


Register

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.0 already exists and points to a different commit"

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.1 already exists and points to a different commit"

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.1 already exists and points to a different commit"

Error while trying to register: "Tag with name v0.1.1 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/73911
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" 2b355eddb507d3bf3039079ce04ddc00f1d92106
git push origin v0.1.2

Also, note the warning: This looks like a new registration that registers version 0.1.2.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/74052
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" 1b8f9b8c92f1acd3a13e0cb226f46a8cf235a749
git push origin v0.1.1

@JuliaRegistrator register
Changes

Return OrderedDict from OrderedCollections.jl instead of Dict
Exposing HTTP proxies of HTTP.jl

Fixes:

get_Fundamentals() does now return a timestamp

Docs

Added Documentation for the proxy settings
Added an Example Section:

Convert Price data to a DataFrame, TimeSeries.TimeArray, TSFrames.TSFrame
Examples of plotting some data exposed by YFinance.jl with PlotlyJS.jl

Added a version change log

New Dependencies

Base64

Needed for http proxy authentication

OrderedCollections.jl

Provides Ordered Dictionaries. Eases workflow with data because column order is not arbitrary and changing between calls.

Registration pull request created: JuliaRegistries/General/74992
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" 27a21f7435d3fe21537eac882058c7ead4dd4dbe
git push origin v0.1.2

@JuliaRegistrator register
Patch notes:
Changes

Return OrderedDict from OrderedCollections.jl instead of Dict
Exposing HTTP proxies of HTTP.jl

Fixes:

get_Fundamentals() does now return a timestamp

Docs

Added Documentation for the proxy settings
Added an Example Section:

Convert Price data to a DataFrame, TimeSeries.TimeArray, TSFrames.TSFrame
Examples of plotting some data exposed by YFinance.jl with PlotlyJS.jl

Added a version change log

New Dependencies

Base64

Needed for http proxy authentication

OrderedCollections.jl

Provides Ordered Dictionaries. Eases workflow with data because column order is not arbitrary and changing between calls.

Registration pull request updated: JuliaRegistries/General/74992
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" 089a78117f1c0b4f7e5bdce73f6c7acfab8a3cf5
git push origin v0.1.2

@JuliaRegistrator register
Patch notes:
Bug Fix

get_prices would error when autoadjust=true for some tickers when Yahoo returns nothing for some observations in the price time series. The update now does not error in this cases and returns NaN for the missing datapoints. NaN is used instead of Missing because of performance improvements and the ability to integrate YFinance.jl with TimeSeries.jl. (#5)

Thank you RaSi96 for reporting this bug and helping me sort it out!

Docs

Improved documentation for get_prices (#5)

When the range keyword is used instead of startdt and enddt the specified interval is not observed by Yahoo at longer ranges. To enforce the specified interval use startdt and enddt instead.
Data points that yahoo returns as nothing are returned as NaN. It seems like Yahoo thinks it should have price information for these timestamps but does not have them and thus returns nothing.

Other

Added a test case for the stock "ADANIENT.NS". The time series of the stock prices contains the nothing values mentioned in the Bug Fix. (#5)

Registration pull request created: JuliaRegistries/General/80353
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.3 -m "<description of version>" 9095629ddf12b4d856cdbf47228d71cf000c794c
git push origin v0.1.3

@JuliaRegistrator register
Patch Notes:
Bug Fix

get_prices now returns dictionaries containing price vectors of type Array{Float64} rather than Array{ Union{Nothing,Float64}} (#7)

Improvements

get_prices now runs faster than before.

New Functionality

get_symbols allows the user to search for yahoo finance symbols from (partial) company/security names
get_all_symbols exposes all tickers from the NASDAQ, AMEX, and NYSE exchanges (#8)
search_news now allows for news searches

Docs

Added documentation for the new functionality
Added a clarification statement in the Readme.md and Docs that YFinance uses API endpoints to access data and does not suffer from decryption issues (#6)

Registration pull request created: JuliaRegistries/General/82302
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.4 -m "<description of version>" eb64e2a62c7e48b310f7d634c6be195a850bb532
git push origin v0.1.4

@JuliaRegistrator register
Patch Notes:
Bug Fix

Implemented Cookies and Crumbs to fix get_quoteSummary() and all functions depending on it (#14)

Registration pull request created: JuliaRegistries/General/102126
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.5 -m "<description of version>" 5385e351e0982bcdf16d6dc6072cde254ecc2e25
git push origin v0.1.5

@JuliaRegistrator register
Patch Notes:
Improvements

get_prices can now return dividends and splits (#11, #18)
get_prices can now directly return TimeArrays (TimeSeries.jl) and TSFrame (TSFrames.jl). Julia 1.9 is required and the respective packages need to be loaded
added some precompilation for get_prices (this will require a valid internet connection when the package is loaded first/installed)

New Functionality

get_splits returns stock split information
get_dividends returns dividend information
sink_prices_to allows for easy conversion to TimeArrays (TimeSeries.jl) and TSFrame (TSFrames.jl). Julia 1.9 is required and the respective packages need to be loaded

Registration pull request created: JuliaRegistries/General/112593
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.6 -m "<description of version>" 35d238dc40a2559f67923d6b1670e68bbfb54212
git push origin v0.1.6

@JuliaRegistrator register
Patch Notes:
Bug Fix/Improvement

get_prices, get_splits, get_dividends now error more nicely when there is no data for the selected date range. (#19)

Registration pull request created: JuliaRegistries/General/113023
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.7 -m "<description of version>" 58064585e3c7f92774f3639915e5d5abbe09e12d
git push origin v0.1.7

@JuliaRegistrator register
Patch Notes:
Bug Fix/Improvement

get_prices indexing error when divsplits=true  (#22)

Registration pull request created: JuliaRegistries/General/115023
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.8 -m "<description of version>" a78aa7fabcbc5c754818113f973290efe4aad1ba
git push origin v0.1.8

@JuliaRegistrator register
Patch Notes:
Bug Fix/Improvement

Disable Precompilation. Experienced precompilation hangs in Julia 1.10 and 1.11 (warning not error) but precompilation errors if a proxy is required or Yahoo cannot be reached for other reasons (#23). For precompilation please install v0.1.8 instead.

Registration pull request created: JuliaRegistries/General/116308
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.9 -m "<description of version>" c0c2881f396b68d387f904b7fc1aaa51ae8d16bf
git push origin v0.1.9

@JuliaRegistrator register
Patch Notes:
Improvements

get_prices now supports the retrieval of minute level data for periods longer than 7 days. This is facilitated by making multiple requests and stitching the responses together (minute data still needs to be within the last 30 days - this is a limit set by Yahoo)
get_prices now allows startdt and enddt to be of different types (e.g., startdt="2024-01-01", enddt=today() is now valid)
The range argument in get_prices has been reworked to convert to startdt and enddt #21  . Previously, this parameter was simply passed to the Yahoo API. The new way brings multiple improvements:

more flexible range inputs
specified intervals are now observed

Significant code refactoring for improved maintainability and readability of the get_prices function
get_prices now returns a OrderedDict{String, Union{String,Vector{DateTime},Vector{Float64}}} rather than OrderedDict{String,Any}
Added precompilation for the response processing part of the get_prices function only

Registration pull request created: JuliaRegistries/General/116692
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.10 -m "<description of version>" cd4c9d80fb8889b69da32cc4f1900b08358de09e
git push origin v0.1.10


chore: bug template update

v14.0.2 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


[core] implement our own CaseInsensitiveDict

Right now, our current implementation relies on either having the requests or aiohttp library installed. Instead, we want to implement our own case insensitive dict, so we can get rid of this dependency

We can close this one because of #25074 right ?

yep, closing now


Latest news on the main page

A section with latest news about Django, perhaps taking the RSS syndication from the Django Project webpage.

I still would love to see this on the main page.


Gradle task assembleDebug issue resolved & set min API level to 16

issue : #7  #5  #18 #bug
#7 Gradle build fails due to Kotlin gradle saying The Android Gradle plugin supports only Kotlin Gradle plugin version 1.3.10 and higher is now resolved. Accept the Pull the request please .
#5 min sdk Version is set to API level 16.

Thanks for contributing. I'll review the PR this week.

Hi, Does this PR also resilve the #6 and #13 ?


Remove GTAvaCrypt Support; Outdated.

GTAvaCrypt is deprecated and was passed on to me. Shader support is now dynamic based on interpretive injection. Due to this, support does not need added by a shader dev. The setup you have here also would negatively break the randomization.
I will add support for liltoon injection wise soon.
Note to pay attention when removing the support, as it seems you over-embedded it.

New: https://github.com/PlagueVRC/AntiRip

Do reply to me here once this is done so I can add support for lilToon. <3

I plan to remove GTAvaCrypt in the future, but this is a breaking change and I will proceed with caution.

GTAvaCrypt before had major bugs that made it borderline un-usable, and the userbase will be less than 5 for it at max.
I am the developer of it now, now called Kanna Protecc. As long as the old support is in your shader, I can't implement support for your shader as it will clash.

Evidence I am the new official developer is found on the orig repo: https://github.com/rygo6/GTAvaCrypt/
I was also a main contributor to the original, as you see.
As long as this outdated support exists, i cannot add support without clashing.
Not to mention, embedding the decode cginc means no randomized shader code, making the random shadercode part of the encryption useless in terms of protection. It is important this is automated.

Bump


chat time resetting

conversation times do not properly save. once putting my computer to sleep and refreshing the page on return i was greeted with this
 rather than the 10:41 that the conversation took place in

Duplicate of #6


Remove PHP 5.4 from travis builds

PHP 5.4 has reached end of life I don't understand why the travis run for PHP 5.4 is still required. See https://travis-ci.org/doctrine/doctrine2/jobs/135986241
It currently breaks travis builds for new PRs, i.e. the UnitOfWorkTest is using the Country::class notation which was introduced in PHP 5.5 (which will actually reach EOL very soon, too).
Not sure if making UnitOfWorkTest use get_class() for now, or just remove PHP 5.4 from the travis build.
$ php -v
PHP 5.4.40-1~dotdeb+wheezy.1 (cli) (built: Apr 22 2015 06:50:56)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
    with Xdebug v2.3.2, Copyright (c) 2002-2015, by Derick Rethans
    with Zend OPcache v7.0.3-dev, Copyright (c) 1999-2013, by Zend Technologies
$ ./vendor/bin/phpunit tests/Doctrine/Tests/ORM/UnitOfWorkTest.php
PHP Parse error:  syntax error, unexpected 'class' (T_CLASS), expecting identifier (T_STRING) or variable (T_VARIABLE) or '{' or '$' in /vagrant/libs/doctrine2/tests/Doctrine/Tests/ORM/UnitOfWorkTest.php on line 343
PHP Stack trace:
PHP   1. {main}() /vagrant/libs/doctrine2/vendor/phpunit/phpunit/phpunit:0
PHP   2. PHPUnit_TextUI_Command::main() /vagrant/libs/doctrine2/vendor/phpunit/phpunit/phpunit:47
PHP   3. PHPUnit_TextUI_Command->run() /vagrant/libs/doctrine2/vendor/phpunit/phpunit/src/TextUI/Command.php:100
PHP   4. PHPUnit_Runner_BaseTestRunner->getTest() /vagrant/libs/doctrine2/vendor/phpunit/phpunit/src/TextUI/Command.php:123
PHP   5. PHPUnit_Runner_BaseTestRunner->loadSuiteClass() /vagrant/libs/doctrine2/vendor/phpunit/phpunit/src/Runner/BaseTestRunner.php:67
PHP   6. PHPUnit_Runner_StandardTestSuiteLoader->load() /vagrant/libs/doctrine2/vendor/phpunit/phpunit/src/Runner/BaseTestRunner.php:123
PHP   7. PHPUnit_Util_Fileloader::checkAndLoad() /vagrant/libs/doctrine2/vendor/phpunit/phpunit/src/Runner/StandardTestSuiteLoader.php:39
PHP   8. PHPUnit_Util_Fileloader::load() /vagrant/libs/doctrine2/vendor/phpunit/phpunit/src/Util/Fileloader.php:38

I'd say "go on and make a PR". Dropping 5.4 was indeed gonna happen :-)

Handled via #5863


Support for try-catch block with "bhai tension mat le(try) - tera bhai hai naa(catch)"

Description
Add support for try/catch block with above names!!
I have already started working on it. Assign this to me.
Domain
Bhai Lang
Type of Contribution
Enhancement
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of bhai-lang.

No current plans to add this feature in this language as this will lead to more complexities in this toy language.


Update migrate-support-matrix-vmware.md

adding ubuntu 22.04 to depmap analysis

@Vikram1988
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off

@MicrosoftDocs/public-repo-pr-review-team
This PR has been signed off, but it is not merged yet. Can you look into this please?


Inbox links point to wrong URL

Reported by Raphaëlle via Mastodon.
See e.g. https://skohub.io/dini-ag-kim/hochschulfaechersystematik/heads/master/w3id.org/kim/hochschulfaechersystematik/n1.html
"Inbox" links to a URL at skohub.lobid.org, should be skohub.io.

These were build at  May  8 10:26 back when the server was named skohub.lobid.org.
I could rewrite all those files, but not sure of consequences.
I assume the servers name will be correct for all newer vocabs, right?
Question is, if you rather want to rebuild it - is this even possible?

Ah, ok. I triggered a rebuild. It is fixed now in Hochsculfaechersystematik. However,  Raphaëlle  pointed to another vocab that was built yesterday, see e.g. https://skohub.io/hbz/vocabs-edu/heads/master/w3id.org/class/esc/n03.html. I also rebuit that one but it still points to skohub.lobid.org. Strange.

Yeah, you're right: in the .env it's said: BUILD_URL=https://skohub.lobid.org/build/.
Changed that, please rebuild @acka47 .

Now it is fixed, see inbox links at https://w3id.org/class/esc/n06 & https://w3id.org/kim/hochschulfaechersystematik/n1. Closing.


Can't install this after git clonning

I am following this link and want to use Yolo_mark to find these parameters <x><y><width><height>
<x> = <absolute_x>/<width_of_image>
<y>=<absolute_y>/<height_of_image>
<width> = <width_of_object>/<width_of_image>
<height> = <height_of_object>/<height_of_image>
so after git clone link I get into the folder of yolo_mark  and now followed the instructions that is
cmake .
CMake Error at CMakeLists.txt:3 (find_package):
  By not providing "FindOpenCV.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "OpenCV", but
  CMake did not find one.

  Could not find a package configuration file provided by "OpenCV" with any
  of the following names:

    OpenCVConfig.cmake
    opencv-config.cmake

  Add the installation prefix of "OpenCV" to CMAKE_PREFIX_PATH or set
  "OpenCV_DIR" to a directory containing one of the above files.  If "OpenCV"
  provides a separate development package or SDK, be sure it has been
  installed.

-- Configuring incomplete, errors occurred!

Please help me, to come to this problem , I want to use this `yolo_mark` finally to detect objects in the image

Do you have installed library OpenCV?

yes i do have with version 2

yolo_mark.cmd  is not running but I can use yolo_mark 's  interface for finding <x><y><width><height>. Will there be any problem in it ?

There is no problem.
yolo_mark.cmd - only for Windows OS.

https://github.com/AlexeyAB/Yolo_mark#yolo_mark

To test, simply run

on Windows: x64/Release/yolo_mark.cmd
on Linux ./linux_mark.sh

Ok thanks a lot .


BUG: Can't change branch of repo from master to main

name: Bug report
about: Create a report to help us improve
title: 'BUG: Can't change branch of repo from master to main'
labels: 'node,github'
assignees: ''

Describe the bug
A clear and concise description of what the bug is.
Link to the blitz that caused the error
https://stackblitz.com/edit/http-server-m8vf6v
To Reproduce
Steps to reproduce the behavior:

Go to 'editor'
Click on 'repo select'
Scroll down to 'main'
See that nothing happens

Expected behavior
The selector should change to 'main', and the files should switch to that branch
Version of webcontainer
Hash: 7286dbe8d47d3473cde7be488b7d048fb59b05f2
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Browser name  = Chrome
Full version  = 90.0.4430.212
Major version = 90
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36
performance.memory = {
totalJSHeapSize: 62182718,
usedJSHeapSize: 57563038,
jsHeapSizeLimit:<PHONE_NUMBER>
}
Additional context
Add any other context about the problem here.

Hi!
There are some issues with are current Git implementation. This is def a bug.
We'll be releasing a completely reworked version of this in the next week that should resolve this.

This is also happening to me with a private repo. I even tried to do a workaround my making a new branch called master. This hack allows for the files to be imported but when I try to switch to any branch then it just loads forever.

Hi there, is this still open? Any updates on progress?


Totient function code in sieve

I can add totient function code in sieve because it's an important algorithm to know and can also describe it's time complexity

Please assign this issue to me. I can add totient function code in sieve

If it's open I would like to take it up!


IE (Internet Explorer) Error 💩

Running a simple page that references nothing other than React within Next.js on IE9...11 causes the following error:

This occurs with both next.js version 1.2.3 and 2.0.0-beta.0.
An example of this on IE9 can be seen here (courtesy of @arunoda):
https://www.browserling.com/browse/win/vista/ie/9/https%3A%2F%2F37a02b6c.ngrok.io%2Fabout
The code which is throwing the error seems related to stylesheets:
Object.assign(StyleSheet.prototype, {
  getSheet: function getSheet() {
    return sheetForTag(last(this.tags));
  },
  inject: function inject() {
    var _this = this;

    if (this.injected) {
      throw new Error('already injected stylesheet!');
    }
    if (isBrowser) {
      this.tags[0] = makeStyleTag();
    } else {
  ...

Object.assign is not in ES5 and so this is perhaps a babel related problem where an external library has been referenced that has not been transpiled.
This will not be showing up as an error in Chrome/Firefox (and all the other "big boy browsers") as they have started to implement some of the ES6 spec natively.

TEMPORARY HACK.  To work around this until this is fixed, you can add:
    <script
      type='text/javascript'
      src='https://cdnjs.cloudflare.com/ajax/libs/babel-polyfill/6.20.0/polyfill.min.js' />

to the page.

Here's the source of the issue: https://github.com/threepointone/glamor/issues/155

I think polyfills should be added manually if the dev needs to support old browsers

@luisrudge actually it's a problem of glamor. It's not doing babel transpiling properly.

@luisrudge I agree with @arunoda.  Object.assign transpiles via babel just fine when used within a consuming project.  But it's the NextJS bundle itself which is delivering some un-transpiled code within it.

@philcockfield I already send a PR for glamor and I hope they'll accept it and cut a new release.
See: https://github.com/threepointone/glamor/pull/166

Rock and roll @arunoda!  Awesome 💯

@arunoda next.js is using Object.assign.  It's under the utils function https://github.com/zeit/next.js/blob/master/lib/utils.js#L20, the #513 fixes this with just adding a simple transform.
I do believe this fix #513 is better instead of adding the whole babel-polyfill as a dependency.  babel-polyfill is actually pretty big, and adding that should be on the userland instead of the library.
This same fix applies in glamor, instead of adding babel-polyfill, its better to add this transform.

@thisguychris yes Next.js Object.assign and many other ES2015+ features.
Actually, babel's transform runtime is pretty clever and it doesn't include the whole shims/polyfills.
Check the transpiled code of the above mentioned utils.js
So, the issue is not in the Next.js code base and our use of babel-runtime is pretty efficient. If glamor didn't fix this issue, we may need to hot fix it.

@arunoda oh that's good to know! looks like they fixed it in v6 and up, Our app is still in v5 😂

Guys, now glamor has a fix for this issue.
We've bumped the glamor version in master and it should work properly.
But Next.js apps only work on IE9+ versions only.
That's because of our use of history API.

I hope we could close this now.
See^^^

👍


Enable LTO support for clang-like compiler when using feature "bundled" in libsqlite3-sys

This PR enables LTO support in libsqlite3-sys when the compiler is clang-like.
I've tested that it all tests inside libsqlite3-sys passed by adding:
[dev-dependencies]
libsqlite3-sys = { path = ".", features = ["bundled"] }

to libsqlite3-sys/Cargo.toml and run cargo test --release.
I've also run the test inside rusqlite with features = ["bundled"] for libsqlite3-sys.
Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

There's more to this that's likely needed for it to actually LTO the Rust with the C. https://doc.rust-lang.org/rustc/linker-plugin-lto.html
But either way, IDT we want to do this — it will generally come with the downside that clang and rustc be compiled with the same version of LLVM, which sometimes is easy, and sometimes massively inconvenient.

Thanks for the feedback!
I think I can add the -C linker-plugin-lto flags to .cargo/config and check for llvm version used by cargo and the llvm version used by clang by running the compiler with the —version flag.
I will have a try and update the PR if succeeded.

.cargo/config isn't replicated for users of the crate via crates.io, so it wouldn't help outside this crate.
I think LTO is too finicky to be worth trying to integrate with the bundled feature. Again, it requires matching versions of LLVM used by clang and rustc, which can be quite tricky. I think if you want LTO, you probably should manually build and link.

I also don't expect it to help in this case — I'm guessing you're hoping for it to devirtualize the stuff in vtable.rs, but I don't think in practice you'll see that, given the way that virtual tables happen internally for sqlite.

.cargo/config isn't replicated for users of the crate via crates.io, so it wouldn't help outside this crate.
I think LTO is too finicky to be worth trying to integrate with the bundled feature. Again, it requires matching versions of LLVM used by clang and rustc, which can be quite tricky. I think if you want LTO, you probably should manually build and link.

It looks like it is better to just compile sqlite3 with LTO manually and then use PKG_CONFIG_PATH to inject the manually writen .pc file though.
I think I can do this :D

I also don't expect it to help in this case — I'm guessing you're hoping for it to devirtualize the stuff in vtable.rs, but I don't think in practice you'll see that, given the way that virtual tables happen internally for sqlite.

Wait, doesn’t LTO mean that it is possible to perform optimization accross the object files?
I thought the compiler is smart enough to devirtualize C-style function pointers, but I can be wrong.
Last time I heard, devirtualizing C style function pointers isn’t as simple as vtable in C++ and rust due to the mutability, lack of type information and the fact that it is coded by the programmer.

Wait, doesn’t LTO mean that it is possible to perform optimization accross the object files?

Yes.

I thought the compiler is smart enough to devirtualize C-style function pointers, but I can be wrong.

It depends on the case. It usually requires the compiler to be able to conclusively identify the thing thats being called. What Sqlite does ends up with the virtual table being put into a data structure, and then looked up later when preparing the statement, and then the functions are called when stepping the statement.
This is too indirect to be reliable for compilers. I'd be very surprised if it could manage something like that. Maybe in the future, but it seems a ways off...
Also note that the function call overhead, even an indirect function call like this, is probably pretty small compared to a lot of what SQLite does.

Also note that the function call overhead, even an indirect function call like this, is probably pretty small compared to a lot of what SQLite does.

Indeed, SQLite does a lot than vtable.rs, which is simply a random generator, the overhead of calling into it might as well be shadowed by the interpreter in SQLite and memory allocation.
Though I do think linking with SQLite using LTO can throw away many unused function and reduce the overhead of setting Values, which might not make a difference at all xD.
Speaking of which, the vtab isn’t easy to implement and took me some time to look at the SQLite doc to understand the API.
rusqlite::vtab::VTab::best_index is the most confusing method, with IndexInfo mixing the input parameters and the required output parameters and the idx_num not being super clear at first.
Maybe I can submit a PR later on that part, which I think do need improvements.


Questions about class registration and resolution in desktop apps for external plug-ins

I am working on project which uses c++/winrt custom components and loads them into a c# desktop (non-uwp) app. I have a requirement to handle this for compile time dependencies and runtime discovered plug-ins. As far as I know for this to work I must use manifests on the main executable where the all the runtime classes and their source libraries are listed - something which I obviously want to avoid for plug-ins. Currently I put the app into a Desktop Bridge packaging project - but I also provide a non-packaged option for docker.
My questions are:

As I understand WinMD files describe all the runtime classes of a library - among other types, which together with the activation factory in the DLL provide enough info for these classes to be instantiated. Also a .Net assembly referring to such types contains the types full name. Why then I need these manifests? Couldn't the .Net runtime just locate these classes by full-name using reflection on the WinMD files?
Is there an API where I could register runtime classes at runtime? (Based on runtime reflection, or worst case an external list of DLL name - classname pairs.)

I have seen there is an API for COM activation contexts which allows me to specify the manifest to use dynamically, however for me this looks more complicated than it needs to be, since I do not intend to switch between contexts manually all the time, but rather create some solution which uses the right context automatacally when a runtime class is created. Although I assume I could generate a manifest at runtime, and use it for everything using this API.
I am also considering creating some custom build tool which would generate manifests based on dependent winMDs, something which the c++/winrt build system could also do.

Or do you have another suggestion for handling this problem for external plug-ins? - which cannot be in the main manifest of the executable.

Hi Péter, these questions go well beyond the scope of C++/WinRT. Your best bet is to pose the questions on Stack Overflow. I just don't know enough about .NET, manifests, packages and all that.


Fix SET=DEFAULT syntax

Index Issue: pingcap/tidb#11486
These are bad (incompatible) SQL cases:
insert into t set a = default;
replace t set a = default;
update t set a = default;

Claim this subtask based on the comments below this issue.

Let me fix it


i18n extraction -op (--output-path) option not working in CLI 1.4.2

Bug Report or Feature Request (mark with an x)
- [ X] bug report -> please search issues before submitting
- [ ] feature request

Versions.
@angular/cli: 1.4.2
node: 8.3.0
os: win32 x64
@angular/animations: 5.0.0-beta.7
@angular/cdk: 2.0.0-beta.10
@angular/common: 5.0.0-beta.7
@angular/compiler: 5.0.0-beta.7
@angular/core: 5.0.0-beta.7
@angular/forms: 5.0.0-beta.7
@angular/http: 5.0.0-beta.7
@angular/material: 2.0.0-beta.10
@angular/platform-browser: 5.0.0-beta.7
@angular/platform-browser-dynamic: 5.0.0-beta.7
@angular/router: 5.0.0-beta.7
@angular/cli: 1.4.2
@angular/compiler-cli: 5.0.0-beta.7
typescript: 2.4.2
Repro steps.
ng xi18n -f xlf -l en-US -op src/locale -of untranslated-messages.xlf --progress
The log given by the failure.
XLF file is generated at the path  /out-tsc/app/untranslated-messages.xlf
Desired functionality.
XLF file is generated at the path /src/locale/untranslated-messages.xlf
Mention any other details that might be useful.
/tsconfig.json
{
  "compilerOptions": {
    "baseUrl": "src",
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "noUnusedLocals": true,
    "noUnusedParameters": false,
    "allowUnreachableCode": false,
    "lib": [
      "es2017",
      "dom"
    ],
    "mapRoot": "./",
    "module": "es2015",
    "moduleResolution": "node",
    "outDir": "./dist/out-tsc",
    "sourceMap": true,
    "target": "es5",
    "typeRoots": [
      "../node_modules/@types",
      "./typings.d.ts"
    ],
    "types": [
      "node"
    ]
  }
}

src/tsconfig.app.json
{
  "extends": "../tsconfig.json",
  "compilerOptions": {
    "outDir": "../out-tsc/app",
    "module": "es2015",
    "baseUrl": "",
    "types": []
  },
  "exclude": [
    "test.ts",
    "**/*.spec.ts"
  ]
}

I'm wondering if this issue will be fixed by https://github.com/angular/angular-cli/pull/7702?
When testing this same command on a test Angular 4.1.3 app using CLI 1.1.1 the file is written to the correct location.
Thanks!

Support of Angular v5 is in CLI 1.5.0 (currently in beta) and the fix you're looking for is merged in this PR #7702


feat(property): Allow user/data curator to specify the avatar initials for organizations

Contributes to #1481
Changelog

update the API description of the organization service to add the property Organization.acronym
update the data model of the organization service (SQL)

Notes

The acronym feature has been added as a property of organization service. Future development may include acronym optimization using the organization name being compared to the available acronym.

Preview
The organization service now returns Organization.acronym
The motivation for this change is that the challenge search page will use the organization acronym in the ChallengeSearchQuery object to filter challenges by organization. This will serve as a secondary organization identifier and will eliminate the use of a shortName descriptor.
Addition of the property to the project description
type: object
description: An organization
properties:
  name:
    type: string
    example: Example organization
  email:
    $ref: Email.yaml
  login:
    $ref: OrganizationLogin.yaml
  description:
    type: string
    example: A description of the organization.
  avatarUrl:
    type: string
    format: url
    example: https://via.placeholder.com/300.png
    nullable: true
  websiteUrl:
    type: string
    format: url
    example: https://example.com
  challengeCount:
    type: integer
    format: int32
    minimum: 0
    example: 10
  createdAt:
    type: string
    format: date-time
    example: '2022-07-04T22:19:11Z'
  updatedAt:
    type: string
    format: date-time
    example: '2022-07-04T22:19:11Z'
  acronym:
    type: string
    example: 'OC'
required:
  - name
  - email
  - login
  - description
  - avatarUrl
  - websiteUrl
  - createdAt
  - updatedAt

Addition of acronym to all SQL queries.
CREATE TABLE `organization` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) NOT NULL,
  `email` varchar(255) NOT NULL,
  `login` varchar(64) NOT NULL UNIQUE,
  `avatar_url` varchar(255) DEFAULT NULL,
  `website_url` varchar(255) DEFAULT NULL,
  `description` varchar(280) DEFAULT NULL,
  `challenge_count` int,
  `created_at` DATETIME DEFAULT CURRENT_TIMESTAMP,
  `updated_at` DATETIME DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `acronym` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`id`),
  CONSTRAINT login_check CHECK (char_length(login) >= 2)
);

INSERT INTO organization (
    id,
    name,
    email,
    login,
    avatar_url,
    website_url,
    description,
    challenge_count,
    acronym
  )

@mdsage1 In the Original Post (OP), could you add a section named "Preview" that shows an example of Organization object returned by the organization service to illustrate this contribution?

The VALUES have not been updated in the INSERT INTO organization query. They will be updated soon.

@mdsage1 The current snippet of code in the section Preview is not required because reviewers can see these changes under the tab Files changed. What I suggested was to show the JSON response returned by the organization service. This proves that the implementation works. You can get this response from the Swagger UI or from the file requests.http that lives in the project folder of the microservices.

The requested change has been implemented and pushed to this repo


RbVmomi::Fault: machine[testevm] (vsphere::provision line 56) had an error: RbVmomi::Fault:  InvalidArgument: A specified parameter was not correct.

Hi All,
Does anyone know What can kind of problem could be the following ? It´been happing intermittently , It always happen at the second time I tried to provision a new VM  template based.
RbVmomi::Fault
InvalidArgument: A specified parameter was not correct.
LicenseFilePrintData
The recipe being used:
ENV['http_proxy'] = 'http://<IP_ADDRESS>:3128'
with_chef_server "https://palencia/organizations/ACME",
:client_name => Chef::Config[:node_name],
:signing_key_filename => Chef::Config[:client_key],
:machine => 'testevm'
chef_gem 'chef-provisioning-vsphere' do
  action :install
  compile_time true
end

require 'chef/provisioning/vsphere_driver'

with_vsphere_driver host: '<IP_ADDRESS>',
  insecure: true,
  user:     'ilegra_fribeiro@ACME',
  password: '@ACME123'

machine_options = {
:bootstrap_options => {
:start_timeout => 60,
:create_timeout => 60,
:name => 	'testevm',
    :num_cpus =>        '2',
    :memory_mb =>       '4096',
:datacenter =>		'ALPHAVILLE',
:resource_pool =>	'CORP-DEVOPS',
    :datastore =>          'VNX-DT-07',
    :template_name =>      'Template_sql2003_devops',
    :customization_spec => {
      :ipsettings => {
        :ip => '<IP_ADDRESS>',
        :subnetMask => '<IP_ADDRESS>',
        :gateway => ['<IP_ADDRESS>'],
        :dnsServerList => ['<IP_ADDRESS>','<IP_ADDRESS>']
      },
      :domain => 'local',
      :domainAdmin => 'Administrator',
      :domainAdminPassword => '@ACME123',
      :org_name => 'ACME',
      :product_id => 'MT3V3-HVKB8-GKYJJ-YVVJJ-922M6',
      :win_time_zone => 4
    },
    :ssh => {
      :user => 'Administrator',
      :password => '@ACME123',
      :paranoid => false
    },
    :convergence_options => {
     :ssl_verify_mode => :verify_none
    }
  }
}

machine 'testevm' do
	machine_options machine_options
	action :ready
	retries 0
	retry_delay 6
end

thanks in advance
Cesar

Hi Cesar,
I think you're looking for this gem. This gem, knife-vsphere, is similarly named but only works for ad-hoc commands.

Hi swalberg,
Thanks for your reply. I just raised an issue in the following link
https://github.com/CenturyLinkCloud/chef-provisioning-vsphere/issues/80


'Error=INVALID_PARAMETERS'. It is missing 'token' field.

Potentially related to https://github.com/firebase/firebase-ios-sdk/issues/5970
Environment

Xcode version: 12.3
Firebase SDK version: 6.33.0
Installation method: CocoaPods
Firebase Component: Messaging

[REQUIRED] Problem
We get Invalid registration response :'Error=INVALID_PARAMETERS'. It is missing 'token' field. when we try to register to a topic.
Relevant Logs:
2021-01-02 05:26:54.937529+0200 Runner_dev[56092:5378014] Metal API Validation Enabled
2021-01-02 05:26:54.996240+0200 Runner_dev[56092:5378215] 6.33.0 - [Firebase/Core][I-COR000005] No app has been configured yet.
2021-01-02 05:26:54.996556+0200 Runner_dev[56092:5378215] 6.33.0 - [Firebase/Core][I-COR000001] Configuring the default app.
2021-01-02 05:26:54.996629+0200 Runner_dev[56092:5378215] 6.33.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2021-01-02 05:26:54.998412+0200 Runner_dev[56092:5378218] 6.33.0 - [GoogleUtilities/AppDelegateSwizzler][I-SWZ001011] App Delegate Proxy is disabled.
2021-01-02 05:26:54.998571+0200 Runner_dev[56092:5378014] [Firebase/Crashlytics] Version 4.6.2
2021-01-02 05:26:54.999013+0200 Runner_dev[56092:5378218] 6.33.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics] Running on iPhone13,2, 14.3.0 (18C66)
2021-01-02 05:26:54.999720+0200 Runner_dev[56092:5378218] 6.33.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Settings] No settings were cached
2021-01-02 05:26:55.008106+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash:Reports:Event] Registered Firebase Analytics event listener
2021-01-02 05:26:55.008218+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Crashlytics][I-CLS000000] Automatic data collection is enabled.
2021-01-02 05:26:55.008331+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Crashlytics][I-CLS000000] Unsent reports will be uploaded at startup
2021-01-02 05:26:55.009972+0200 Runner_dev[56092:5378241] 6.33.0 - [Firebase/Messaging][I-FCM002000] FIRMessaging library version 4.7.1
2021-01-02 05:26:55.010232+0200 Runner_dev[56092:5378241] 6.33.0 - [GULReachability][I-REA902003] Monitoring the network status
2021-01-02 05:26:55.062208+0200 Runner_dev[56092:5378221] 6.33.0 - [GULReachability][I-REA902003] Monitoring the network status
2021-01-02 05:26:55.062241+0200 Runner_dev[56092:5378221] 6.33.0 - [GULReachability][I-REA902003] Monitoring the network status
2021-01-02 05:26:55.062263+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS024000] Debug mode is on
2021-01-02 05:26:55.062285+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS005000] The AdSupport Framework is not currently linked. Some features will not function properly. Learn more at http://goo.gl/9vSsPb
2021-01-02 05:26:55.062307+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60803000 started
2021-01-02 05:26:55.062395+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS023008] To disable debug logging set the following application argument: -noFIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2021-01-02 05:26:55.062670+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS023009] Debug logging enabled
2021-01-02 05:26:55.062797+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS023207] To enable verbose logging set the following application argument: -FIRAnalyticsVerboseLoggingEnabled (see http://goo.gl/RfcP7r)
2021-01-02 05:26:55.063005+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS025036] App Delegate Proxy is disabled
2021-01-02 05:26:55.166043+0200 Runner_dev[56092:5378234] flutter: Observatory listening on http://<IP_ADDRESS>:51883/9RmHJHjCSwk=/
2021-01-02 05:26:55.255386+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS002002] APMExperimentAlarm scheduled to fire in approx. (s): 12164.78763198853
2021-01-02 05:26:55.348074+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2021-01-02 05:26:55.348428+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS029014] Successfully parsed a configuration. Version:<PHONE_NUMBER>798113
2021-01-02 05:26:55.348909+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS023016] Analytics is ready to receive events
2021-01-02 05:26:55.446264+0200 Runner_dev[56092:5378237] 6.33.0 - [Firebase/Crashlytics][I-CLS000000] Failed to download settings Error Domain=FIRCLSNetworkError Code=-5 "(null)" UserInfo={status_code=404, type=2, request_id=, content_type=text/html; charset=utf-8}
2021-01-02 05:26:55.448304+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS032003] iAd framework is not linked. Search Ad Attribution Reporter is disabled.
2021-01-02 05:26:55.449173+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2021-01-02 05:26:55.449205+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2021-01-02 05:26:55.449252+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS023220] Analytics screen reporting is enabled. Call +[FIRAnalytics logEventWithName:FIREventScreenView parameters:] to log a screen view event. To disable automatic screen reporting, set the flag FirebaseAutomaticScreenReportingEnabled to NO (boolean) in the Info.plist
2021-01-02 05:26:55.572487+0200 Runner_dev[56092:5378238] 6.33.0 - [GULReachability][I-REA902004] Network status has changed. Code:2, status:Connected
2021-01-02 05:26:55.572563+0200 Runner_dev[56092:5378238] 6.33.0 - [GULReachability][I-REA902004] Network status has changed. Code:1, status:Disconnected
2021-01-02 05:26:55.572626+0200 Runner_dev[56092:5378238] 6.33.0 - [GULReachability][I-REA902004] Network status has changed. Code:2, status:Connected
2021-01-02 05:26:55.579406+0200 Runner_dev[56092:5378240] 6.33.0 - [Firebase/Auth][I-AUT000011] Provisioning profile has specifically provisioned devices, most likely a Dev profile.
2021-01-02 05:26:55.579553+0200 Runner_dev[56092:5378240] 6.33.0 - [Firebase/Auth][I-AUT000012] APNS Environment in profile: development
2021-01-02 05:26:55.579601+0200 Runner_dev[56092:5378240] 6.33.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2021-01-02 05:26:55.579673+0200 Runner_dev[56092:5378237] 6.33.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:55.597823+0200 Runner_dev[56092:5378237] 6.33.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, screen_view (_vs), {
    ga_event_origin (_o) = auto;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) = -2495601682029743000;
}
2021-01-02 05:26:55.598447+0200 Runner_dev[56092:5378240] 6.33.0 - [Firebase/Analytics][I-ACS023073] Debug mode is enabled. Marking event as debug and real-time. Event name, parameters: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) = -2495601682029743000;
}
2021-01-02 05:26:55.601381+0200 Runner_dev[56092:5378240] 6.33.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) = -2495601682029743000;
}
2021-01-02 05:26:55.602636+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 0.9762150049209595
2021-01-02 05:26:55.846242+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Firestore][I-FST000001] Initializing. Current user: 0JaBFEdrWVSTRd8dRwH4DADdeQw2
2021-01-02 05:26:55.846284+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Firestore][I-FST000001] Using full collection scan to execute query: Query(canonical_id=env/dev/users/0JaBFEdrWVSTRd8dRwH4DADdeQw2|f:|ob:__name__asc)
2021-01-02 05:26:55.846310+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) start
2021-01-02 05:26:55.846359+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Auth][I-AUT000002] Token auto-refresh enabled.
2021-01-02 05:26:55.846380+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Auth][I-AUT000004] Token auto-refresh scheduled in 17:43 for the new token.
2021-01-02 05:26:55.846397+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Firestore][I-FST000001] Creating Firestore stub.
2021-01-02 05:26:55.859037+0200 Runner_dev[56092:5378223] flutter: locale.languageCode: en
2021-01-02 05:26:56.104979+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.105086+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.105548+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.105953+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.106143+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.106827+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.106876+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.106895+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.125365+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.125405+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.125466+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.146705+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) headers (whitelisted): date: Sat, 02 Jan 2021 03:26:56 GMT
2021-01-02 05:26:56.146751+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) response: <ListenResponse 0x16ec0e650>: {
  target_change {
    target_change_type: ADD
    target_ids: 2
  }
}
2021-01-02 05:26:56.191668+0200 Runner_dev[56092:5378223] flutter: subscribeToTopic: 0JaBFEdrWVSTRd8dRwH4DADdeQw2
2021-01-02 05:26:56.196360+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) headers (whitelisted): date: Sat, 02 Jan 2021 03:26:56 GMT
2021-01-02 05:26:56.199775+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) headers (whitelisted): date: Sat, 02 Jan 2021 03:26:56 GMT
2021-01-02 05:26:56.199810+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) response: <ListenResponse 0x16ec0e650>: {
  target_change {
    target_change_type: CURRENT
    target_ids: 2
    resume_token: "\n\t\010\314\247\264\356\246\374\355\002"
    read_time {
      seconds:<PHONE_NUMBER>
      nanos: 201676000
    }
  }
}
2021-01-02 05:26:56.199852+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) headers (whitelisted): date: Sat, 02 Jan 2021 03:26:56 GMT
2021-01-02 05:26:56.199885+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) response: <ListenResponse 0x16ec0e650>: {
  target_change {
    resume_token: "\n\t\010\314\247\264\356\246\374\355\002"
    read_time {
      seconds:<PHONE_NUMBER>
      nanos: 201676000
    }
  }
}
2021-01-02 05:26:56.200089+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2021-01-02 05:26:56.200176+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2021-01-02 05:26:56.200211+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Messaging][I-FCM017000] Topic subscription request: sender=cyl-5UqSbkEYv2maOWAChY:APA91bG17lCa7nIXl04sWQX7nxG3lTMI-mqaphhZlQlSPZJObMW0_0bnTimaHHzDrWSRnHRvbsB3gUWOexvZ5t9LKt61Ul06HocWRQ86MIwUugWRe17UnkfZroR3hwfr6SEh7-LZE9GV&app=io.supy.app&device=5179847106474540389&app_ver=0.1.56&X-gcm.topic=/topics/0JaBFEdrWVSTRd8dRwH4DADdeQw2&X-scope=/topics/0JaBFEdrWVSTRd8dRwH4DADdeQw2
2021-01-02 05:26:56.419717+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Messaging][I-FCM017002] Invalid registration response :'Error=INVALID_PARAMETERS'. It is missing 'token' field.
2021-01-02 05:26:56.419883+0200 Runner_dev[56092:5378014] FLTFirebaseMessaging: An error occurred while calling method Messaging#subscribeToTopic, errorOrNil => {
    NSLocalizedFailureReason = "Invalid registration response :'Error=INVALID_PARAMETERS'. It is missing 'token' field.";
}
2021-01-02 05:26:56.420186+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Messaging][I-FCM004001] Failed to subscribe to topic Error Domain=com.google.fcm Code=0 "Invalid registration response :'Error=INVALID_PARAMETERS'. It is missing 'token' field." UserInfo={NSLocalizedFailureReason=Invalid registration response :'Error=INVALID_PARAMETERS'. It is missing 'token' field.}
2021-01-02 05:26:56.424420+0200 Runner_dev[56092:5378223] [VERBOSE-2:ui_dart_state.cc(177)] Unhandled Exception: type '_InternalLinkedHashMap<dynamic, dynamic>' is not a subtype of type 'String' in type cast
#0      new LinkedHashMap.from.<anonymous closure> (dart:collection/linked_hash_map.dart:89:26)
#1      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:377:8)
#2      new LinkedHashMap.from (dart:collection/linked_hash_map.dart:88:11)
#3      platformExceptionToFirebaseException (package:firebase_messaging_platform_interface/src/method_channel/utils/exception.dart:26:9)
#4      convertPlatformException (package:firebase_messaging_platform_interface/src/method_channel/utils/exception.dart:15:10)
#5      MethodChannelFirebaseMessaging.subscribeToTopic (package:firebase_messaging_platform_interface/src/method_channel/method_channel_messaging.dart:365:13)
<asynchronous suspension>
2021-01-02 05:26:56.667173+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS002001] Measurement timer fired
2021-01-02 05:26:56.667390+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2021-01-02 05:26:56.669156+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) = -2495601682029743000;
}
2021-01-02 05:26:56.678533+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 465
2021-01-02 05:26:56.679123+0200 Runner_dev[56092:5378239] 6.33.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 10,<PHONE_NUMBER>578
2021-01-02 05:26:56.698484+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>697, <APMPBMeasurementBatch: 0x2838b8ff0>
2021-01-02 05:26:56.703803+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2021-01-02 05:26:56.720103+0200 Runner_dev[56092:5378221] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.746618+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.746692+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.746728+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.746812+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.746879+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.746964+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.747042+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.747121+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -2495601682029743000
2021-01-02 05:26:56.849484+0200 Runner_dev[56092:5378238] 6.33.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2021-01-02 05:26:56.909283+0200 Runner_dev[56092:5378240] 6.33.0 - [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, -1
2021-01-02 05:26:56.912984+0200 Runner_dev[56092:5378219] 6.33.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): -0.3347909450531006
2021-01-02 05:26:56.916533+0200 Runner_dev[56092:5378219] 6.33.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2021-01-02 05:27:36.357237+0200 Runner_dev[56092:5378226] [VERBOSE-2:profiler_metrics_ios.mm(203)] Error retrieving thread information: (os/kern) invalid argument
2021-01-02 05:27:41.235098+0200 Runner_dev[56092:5378536] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) headers (whitelisted): date: Sat, 02 Jan 2021 03:26:56 GMT
2021-01-02 05:27:41.235193+0200 Runner_dev[56092:5378536] 6.33.0 - [Firebase/Firestore][I-FST000001] WatchStream (2806acc18) response: <ListenResponse 0x16ec9a650>: {
  target_change {
    resume_token: "\n\t\010\376\302\357\203\247\374\355\002"
    read_time {
      seconds:<PHONE_NUMBER>
      nanos: 212030000
    }
  }
}

Your client seems not getting a FCM registration token properly. Can you try with a fresh install and if still not working, attach me the debugLog with first run after installation?

Your client seems not getting a FCM registration token properly. Can you try with a fresh install and if still not working, attach me the debugLog with first run after installation?

Hi guys, I'm having this exact issue here to.
I'm using an flutter application and it was working nice until I've ported this app to another apple account, after that it loses the apn, certs and everything else on apple, I thing the migration tools doesn't work as it should.  So I've do all the process again and changed the apn in firebase console, change the certificates and everything else, upgrade my firebase messaging migrate the old commands to the new ones for the new api and run, so when I try to subscribe to topic it gives me that error.
Any tips on what can be happening ?

Hi guys, I'm having this exact issue here to.
I'm using an flutter application and it was working nice until I've ported this app to another apple account, after that it loses the apn, certs and everything else on apple, I thing the migration tools doesn't work as it should.  So I've do all the process again and changed the apn in firebase console, change the certificates and everything else, upgrade my firebase messaging migrate the old commands to the new ones for the new api and run, so when I try to subscribe to topic it gives me that error.
Any tips on what can be happening ?

@diegomgarcia Your case seems quite different since you made significant changes to Apple credentials. Can you file a new issue so the discussion here is not redirected on the credential part.

@diegomgarcia Your case seems quite different since you made significant changes to Apple credentials. Can you file a new issue so the discussion here is not redirected on the credential part.


[CONTRACTS] add event emission on registration

The event should contain all the necessary data to index the registrations offchain.

(Will prolly be assigned to @chachaleo)

@0xChqrles please can I work on this

Thank you yes I'd love to take it and continue working on this! :)


React app installed but both npm start and yarn start failed

Is this a bug report?
(write your answer here)
Yes

Did you try recovering your dependencies?

(Write your answer here.)
npm --version
6.4.1
yarn --version
1.15.2
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
I am a little confused about the definition of "the TERM I searched for guide". So at the very beginning, I searched "how to create react app" to get started, and I found and followed the steps in the instructions in this link https://github.com/facebook/create-react-app. After bunch of ERRs, I also searched how to use yarn to create react app. And I followed steps in https://yarnpkg.com/lang/en/docs/cli/create/.
After 24 hours of googling and even asking my instructors and TAs for help, no progress at all. So I turned to yarn, which I have been using for angular development.
Environment

(paste the output of the command here)
Environment Info:

  System:
    OS: macOS 10.14.1
    CPU: x64 Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz
  Binaries:
    Node: 10.15.3 - /usr/local/bin/node
    Yarn: 1.15.2 - ~/.yarn/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 73.0.3683.86
    Safari: 12.0.1
  npmPackages:
    react: ^16.8.6 => 16.8.6
    react-dom: ^16.8.6 => 16.8.6
    react-scripts: 2.1.8 => 2.1.8
  npmGlobalPackages:
    create-react-app: 2.1.8

Steps to Reproduce

(Write your steps here:)
note: Errors occurred so many times both the time I am using npm init react-app my-app, npm start and yarn create react-app my-app, yarn start, but I think the ERRs referred to the same problem. And personally, I tend to use yarn for reactJS development, but nonetheless, neither one works :(.
With npm/nxm:

npx create-react-app my-app
cd to my-app
npm start

With yarn:

yarn global add create-react-app
create-react-app my-app
cd to my-app
yarn start

Expected Behavior

(Write what you thought would happen.)
In (about) 15 seconds,  the app should load into browser.
Actual Behavior

(Write what happened. Please add screenshots!)
With npm:

With yarn:

Seems like they pointing to the same problem?
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)
I don't know if there is a point to this, unlike everybody else, I am actually stuck at the very beginning of creatign the react app. So if I were to provide an example project, that would be simply running create-react-app my-app in your terminal :(.
Personally, I tried both npx create-react-app xxxxxx and  create-react-app xxxxxxx methods, and it seems like I have successfully create this app with no problem?:

 Try echo $HOST in your terminal and see what it spits out. My guess is you'll see x86... as the message in your screenshot shows.
See https://facebook.github.io/create-react-app/docs/advanced-configuration for more info about the environment variables we read from.

The errors are hinting to you that you have the HOST environment variable set in your shell. Try echo $HOST in your terminal and see what it spits out. My guess is you'll see x86... as the message in your screenshot shows.
See https://facebook.github.io/create-react-app/docs/advanced-configuration for more info about the environment variables we read from.

YES! And I just solved it by running one line: unset HOST!


remove deprecated normalized argument in from_quat signature

Changes
update for scipy deprecations
Related Issues
Checks

[x] updated CHANGELOG.md
[x] updated tests
[x] updated doc/
[x] update example/tutorial notebooks

should be fixed now for scipy<1.6 at least @vhirtham

should be fixed now for scipy<1.6 at least @vhirtham

It's curious why the Windows pytest run is passing even with the error.. Any idea @vhirtham ?

It's curious why the Windows pytest run is passing even with the error.. Any idea @vhirtham ?

It's curious why the Windows pytest run is passing even with the error.. Any idea @vhirtham ?
@CagtayFabry  working on it. I am currently installing everything on my private Ubuntu system to test it

It's curious why the Windows pytest run is passing even with the error.. Any idea @vhirtham ?
@CagtayFabry  working on it. I am currently installing everything on my private Ubuntu system to test it

I say we leave it at that for now @vhirtham ?
Can you do a quick review?

I say we leave it at that for now @vhirtham ?
Can you do a quick review?


[all] Proguard test rules

Hello,
When looking at the proguard rules I noticed that the proguard-rules.pro file contains a rules which keeps all the app classes and methods. Because some methods are only called from tests this is of course required but for release builds this seems unneeded to me. Is there a specific reason for this rule to be in the proguard-rules.pro file and not in the proguardTest-rules.pro file?

No, I don't think that was implemented.

Keep The Good is required for steady fundamentals from zilch:to-connectedSSL from beginning i guess

Axually weird issue
On 01/12/2017, Michiel Scoonderbeek (Remco van Ginneke)
<EMAIL_ADDRESS>wrote:

Keep The Good is required for steady fundamentals from zilch:to-connectedSSL
from beginning i guess
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/googlesamples/android-architecture/issues/306#issuecomment-348457796