Detected blocking call to load_default_certs with args

error in log.
log:
Logger: homeassistant.util.loop
Source: util/loop.py:77
First occurred: 10:22:51 (1 occurrences)
Last logged: 10:22:51

Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7fe4b40ea2d0>, <Purpose.SERVER_AUTH: _ASN1Object(nid=129, shortname='serverAuth', longname='TLS Web Server Authentication', oid='<IP_ADDRESS>.<IP_ADDRESS>.1')>) in /usr/local/lib/python3.12/ssl.py, line 713: context.load_default_certs(purpose) inside the event loop; This is causing stability issues. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_default_certs Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.12/site-packages/gardena/smart_system.py", line 190, in start_ws await self.__launch_websocket_loop(ws_url) File "/usr/local/lib/python3.12/site-packages/gardena/smart_system.py", line 227, in __launch_websocket_loop websocket = await websockets.connect(url, ping_interval=150) File "/usr/local/lib/python3.12/site-packages/websockets/legacy/client.py", line 653, in __await_impl__ _transport, protocol = await self._create_connection() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1149, in create_connection transport, protocol = await self._create_connection_transport( File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1173, in _create_connection_transport transport = self._make_ssl_transport( File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 83, in _make_ssl_transport ssl_protocol = sslproto.SSLProtocol( File "/usr/local/lib/python3.12/asyncio/sslproto.py", line 295, in __init__ sslcontext = _create_transport_context( File "/usr/local/lib/python3.12/asyncio/sslproto.py", line 55, in _create_transport_context sslcontext = ssl.create_default_context() File "/usr/local/lib/python3.12/ssl.py", line 713, in create_default_context context.load_default_certs(purpose)

Logger: homeassistant.util.loop
Source: util/loop.py:136
First occurred: 10:22:49 (2 occurrences)
Last logged: 10:22:50

Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7fe4b89f8550>,) inside the event loop by custom integration 'gardena_smart_system' at custom_components/gardena_smart_system/__init__.py, line 86: await self.smart_system.authenticate() (offender: /usr/local/lib/python3.12/site-packages/httpx/_config.py, line 147: context.load_verify_locations(cafile=cafile)), please create a bug report at https://github.com/py-smart-gardena/hass-gardena-smart-system/issues For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in _async_setup_component await asyncio.gather( File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in <genexpr> create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async_.py", line 45, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 752, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/gardena_smart_system/__init__.py", line 49, in async_setup_entry await gardena_system.start() File "/config/custom_components/gardena_smart_system/__init__.py", line 86, in start await self.smart_system.authenticate()
Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7fe4b83ea250>, '/usr/local/lib/python3.12/site-packages/pyoverkiz/overkiz-root-ca-2048.crt', None, None) inside the event loop by integration 'overkiz' at homeassistant/components/overkiz/__init__.py, line 239: return OverkizClient( (offender: /usr/local/lib/python3.12/ssl.py, line 708: context.load_verify_locations(cafile, capath, cadata)), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+overkiz%22 For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in _async_setup_component await asyncio.gather( File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in <genexpr> create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async_.py", line 45, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 752, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/overkiz/__init__.py", line 64, in async_setup_entry client = create_local_client( File "/usr/src/homeassistant/homeassistant/components/overkiz/__init__.py", line 239, in create_local_client return OverkizClient(

+1 same here
Logger: homeassistant.util.loop
Source: util/loop.py:136
First occurred: October 9, 2024 at 23:54:48 (2 occurrences)
Last logged: October 9, 2024 at 23:54:54
Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7f2ff6b5e7d0>,) inside the event loop by custom integration 'gardena_smart_system' at custom_components/gardena_smart_system/init.py, line 86: await self.smart_system.authenticate() (offender: /usr/local/lib/python3.12/site-packages/httpx/_config.py, line 149: context.load_verify_locations(cafile=cafile)), please create a bug report at https://github.com/py-smart-gardena/hass-gardena-smart-system/issues For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in async_setup_component await asyncio.gather( File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in  create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async.py", line 45, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/gardena_smart_system/init.py", line 49, in async_setup_entry await gardena_system.start() File "/config/custom_components/gardena_smart_system/init.py", line 86, in start await self.smart_system.authenticate()
Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7f2feb81afd0>,) inside the event loop by custom integration 'phyn' at custom_components/phyn/init.py, line 64: await client.mqtt.connect() (offender: /usr/local/lib/python3.12/site-packages/paho/mqtt/client.py, line 806: context.load_default_certs()), please create a bug report at https://github.com/jordanruthe/homeassistant-phyn/issues For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_default_certs Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/phyn/init.py", line 64, in async_setup_entry await client.mqtt.connect()

Same issue here with both error messages (Detected blocking call to load_verify_locations) and (Detected blocking call to load_default_certs).  However, it seems that this is one of those things that is just "ok, this will slow down your startup" rather than a true error that's going to cause issues.
Obviously it would be nice if we didn't have stuff in the home-assistant.log file but this doesn't seem to be a thing that's going to really affect actual operations--just slow down startup/restart of the component.
2024-11-26 18:27:15.123 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7fb124aec450>,) inside the event loop by custom integration 'garden For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations                                                                                Traceback (most recent call last):                                                                                File "<frozen runpy>", line 198, in _run_module_as_main                                                                                File "<frozen runpy>", line 88, in _run_code                                                                                File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>                                                                                sys.exit(main())                                                                                File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main                                                                                exit_code = runner.run(runtime_conf)                                                                                File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run                                                                                return loop.run_until_complete(setup_and_run_hass(runtime_config))                                                                                File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete                                                                                self.run_forever()                                                                                File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever                                                                                self._run_once()                                                                                File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once                                                                                handle._run()                                                                                File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run                                                                                self._context.run(self._callback, *self._args)                                                                                File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component                                                                                result = await _async_setup_component(hass, domain, config)                                                                                File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in _async_setup_component                                                                                await asyncio.gather(                                                                                File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in <genexpr>                                                                                create_eager_task(                                                                                File "/usr/src/homeassistant/homeassistant/util/async_.py", line 45, in create_eager_task                                                                                return Task(coro, loop=loop, name=name, eager_start=True)                                                                                File "/usr/src/homeassistant/homeassistant/config_entries.py", line 783, in async_setup_locked                                                                                await self.async_setup(hass, integration=integration)                                                                                File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_setup                                                                                await self.__async_setup_with_context(hass, integration)                                                                                File "/usr/src/homeassistant/homeassistant/config_entries.py", line 635, in __async_setup_with_context                                                                                result = await component.async_setup_entry(hass, self)                                                                                File "/config/custom_components/gardena_smart_system/__init__.py", line 49, in async_setup_entry                                                                                await gardena_system.start()                                                                                File "/config/custom_components/gardena_smart_system/__init__.py", line 86, in start                                                                                await self.smart_system.authenticate()
and
2024-11-26 18:27:16.438 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7fb121960150>, <Purpose.SERVER_AUTH: _ASN1Object(nid=129, shortname='s For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_default_certs                                                                                Traceback (most recent call last):                                                                                File "<frozen runpy>", line 198, in _run_module_as_main                                                                                File "<frozen runpy>", line 88, in _run_code                                                                                File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>                                                                                sys.exit(main())                                                                                File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main                                                                                exit_code = runner.run(runtime_conf)                                                                                File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run                                                                                return loop.run_until_complete(setup_and_run_hass(runtime_config))                                                                                File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete                                                                                self.run_forever()                                                                                File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever                                                                                self._run_once()                                                                                File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once                                                                                handle._run()                                                                                File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run                                                                                self._context.run(self._callback, *self._args)                                                                                File "/usr/local/lib/python3.12/site-packages/gardena/smart_system.py", line 190, in start_ws                                                                                await self.__launch_websocket_loop(ws_url)                                                                                File "/usr/local/lib/python3.12/site-packages/gardena/smart_system.py", line 227, in __launch_websocket_loop                                                                                websocket = await websockets.connect(url, ping_interval=150)                                                                                File "/usr/local/lib/python3.12/site-packages/websockets/asyncio/client.py", line 442, in __await_impl__                                                                                self.connection = await self.create_connection()                                                                                File "/usr/local/lib/python3.12/site-packages/websockets/asyncio/client.py", line 368, in create_connection                                                                                _, connection = await loop.create_connection(factory, **kwargs)                                                                                File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1149, in create_connection                                                                                transport, protocol = await self._create_connection_transport(                                                                                File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1173, in _create_connection_transport                                                                                transport = self._make_ssl_transport(                                                                                File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 83, in _make_ssl_transport                                                                                ssl_protocol = sslproto.SSLProtocol(                                                                                File "/usr/local/lib/python3.12/asyncio/sslproto.py", line 295, in __init__                                                                                sslcontext = _create_transport_context(                                                                                File "/usr/local/lib/python3.12/asyncio/sslproto.py", line 55, in _create_transport_context                                                                                sslcontext = ssl.create_default_context()                                                                                File "/usr/local/lib/python3.12/ssl.py", line 713, in create_default_context                                                                                context.load_default_certs(purpose)


Can not use InsertOrReplaceAsync method?

When I use the method InsertOrReplaceAsync , it's always throw error.
Firstly,the method throw ' parameter count mismatch',then I set an new object[] as the method pramer .
Seem like worked, but it throw with ')' with error, the Executing commandText can not worked.

Nov 2018
Xamarin.Forms app
Have noticed this call simply not returning... ever.
So no code after this is executing.  Related?


Add the auto generated der files to .gitignore

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Pushed. Thanks!


Replace OperatorPrecedenceParser with PrattParser

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (cce7fb4) 80.14% compared to head (2fc5b7e) 80.59%.

Files
Patch %
Lines

src/Escalier.Parser/Parser.fs
96.15%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #96      +/-   ##
==========================================
+ Coverage   80.14%   80.59%   +0.45%
==========================================
  Files          16       17       +1
  Lines        4981     5128     +147
  Branches      624      641      +17
==========================================
+ Hits         3992     4133     +141
- Misses        989      995       +6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[IOTDB-2502] Add query sql in error log if encountering exception

Coverage decreased (-0.004%) to 67.737% when pulling bbfd16e473db3d8a3d741236a8633c0bb0161b16 on iotdb2502 into 7844c63e0e1e20ba741ab3ba8cfb8a086e47fe03 on master.


[CONTRACTS] implement liquidity_share_request tests

The tests are already defined in src/contracts/ramps/revolut/revolut_test.cairo. You just need to write their implementation following the way the escrow tests are implemented.
These contracts will be holding funds, so it's of utmost importance that the tests cover 100% of possible use cases, are readable, easily modifiable, and consistent.
To better understand how the contracts work, please read this article How to manage liquidity in a P2P ramping app

w

can I work on this?

Hello @0xChqrles ,
Can I be assigned to this? I can tackle this issue asap.

hello @0xChqrles can i please be assigned this task?

hello @0xChqrles can i be assigned this project?

hey @0xChqrles new contributooor here, can i work on this?

@0xChqrles can i work on this

Can I work on this? :)

@0xChqrles can i work on this please?


[Windows] Windows 11 tiling menu

Starting with Windows 11, hovering the native maximize button creates a popup window that lets the user tile the window.
Since this library is providing its own implementation of the minimize, maximize and close buttons as Flutter widgets, this menu doesn't show up when hovering the button.
Another way to open this menu is to press Win+Z. This works even on customized windows and shows the menu. However, the placement is different - Windows normally tries to place the dialog centered within the maximize button, but it looks like since it can't find that button, it places it inside the window instead:
Expected

Actual:

Microsoft provides some information on how they expect people who implement custom maximize buttons to get this effect:
https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/apply-snap-layout-menu

Thanks for the reference. Added to my list.


Support for Images

Reddit has recently added in the ability to add images to DM's and Group chats. Have you started working on this implementation?
I would rather not re-invent the wheel if you are already addressing this.

chatbot.send_img() exists

chatbot.send_img() exists

better documentation is needed

chatbot.send_img() exists

better documentation is needed

i dont have the motivation to write one. though i think the code is pretty readable and self-explanatory. anyone feel free to create a pr with better documentation and i will merge it.


Report The Author Warning

WorldEdit: FastAsyncWorldEdit-391
WorldGuard  WorldGuard 7.0.7
WorldGuard Extra Flags: 4.2.1
Server: git-Purpur-1957 (MC: 1.19.4)
For old versions working correctly
Example: git-Purpur-1948 (MC: 1.19.4)

Dupe of #236


Response code 423 from pilot

Hey,
we get very often the response 423 from the pilot. Due to this nearly all installation jobs fail. However installing by hand works and the pilot seems to fill the credentials. Suggestions?

Device is on iOS 7 or 8?

It's an iPad with iOS 7.1.2

Ok, after some research today I found out how to reproduce the issue (at least with my setup):

Some installation failed. Due to this the pilot responded with a 400, probably in this line https://github.com/DiOS-Analysis/Pilot/blob/master/SBServerTweak/SBServerTweak/SBSTHTTPServer.m#L164
After this the internal state of the pilot is not updated as a request to it with /status says that a task is still running.


Warning on setState

Hey @billmalarky
Sorry for being so verbose, but I found that in the line https://github.com/billmalarky/react-native-image-cache-hoc/blob/5bca7d2a6d8b4c8463d384fe4c94ce36f1ef855d/lib/imageCacheHoc.js#L153 of imageCacheHoc file there is a setState without checking if the component is mounted. Maybe keeping a flag and setting to true in componentDidMount and false in componentDidUnmount would be a solution.
It happens of images that I show and hide real fast, I'm using it inside a chat app so this can happen. I can do a PR if you think it's a good idea.

No need to apologize, more verbose == more information which is always a
good thing.
That setState() call will only be fired if the component is already
mounted. Notice that it is contained within the componentDidMount()
lifecycle method.
If the component is mounted, then quickly unmounted before that setState()
line can be reached asynchronously, setState() will not be called because
of this line in componentWillUnmount().
https://github.com/billmalarky/react-native-image-cache-hoc/blob/5bca7d2a6d8b4c8463d384fe4c94ce36f1ef855d/lib/imageCacheHoc.js#L164
As such, we shouldn't be seeing warnings that setState() is getting called
on an unmounted component anymore.
On Tue, Dec 12, 2017 at 11:19 AM, khrizt<EMAIL_ADDRESS>wrote:

Hey @billmalarky https://github.com/billmalarky
Sorry for being so verbose, but I found that in the line
https://github.com/billmalarky/react-native-image-cache-hoc/blob/
5bca7d2a6d8b4c8463d384fe4c94ce36f1ef855d/lib/imageCacheHoc.js#L153 of
imageCacheHoc file there is a setState without checking if the component
is mounted. Maybe keeping a flag and setting to true in componentDidMount
and false in componentDidUnmount would be a solution.
It happens of images that I show and hide real fast, I'm using it inside a
chat app so this can happen. I can do a PR if you think it's a good idea.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/billmalarky/react-native-image-cache-hoc/issues/6,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxTUywp7Jfei6WBYEAHWuFP1l4uVz7Rks5s_qebgaJpZM4Q_PEr
.

It's strange because I saw a warning with the message: "Can only update a mounted or mounting component. This usually means you called setState, replaceState, or forceUpdate on an unmounted component. This is a no-op"
And the stack trace pointed to that line... 😕
I'll take a deeper look, but if you think of something, let me know. Thanks!

Hmm. You're sure you were on the latest version of
react-native-image-cache-hoc when it happened?
On Tue, Dec 12, 2017 at 11:50 AM, khrizt<EMAIL_ADDRESS>wrote:

It's strange because I saw a warning with the message: "Can only update a
mounted or mounting component. This usually means you called setState,
replaceState, or forceUpdate on an unmounted component. This is a no-op"
And the stack trace pointed to that line... 😕
I'll take a deeper look, but if you think of something, let me know.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/billmalarky/react-native-image-cache-hoc/issues/6#issuecomment-351112369,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxTU49NTdkpbYgfOx2vkGCCTD6wDQKHks5s_q7agaJpZM4Q_PEr
.

Yes, I'm on 1.3.1. But I'll do some more checkings.

Ok, finally I did more checkings. I've put a flag in the component that is set to true in componentDidMount and false in componentWillUnmount and a console.log in that line. Turns out that the line is called when the flag is false. I paste some code because my explanation sucks.
    constructor(props) {
      super(props);

      // [...]

      this.mounted = true; // <---- FLAG
    }

    // [...]

    async componentDidMount() {
      // [...]

      this.cancelLocalFilePathRequest = makeCancelable(
        this.fileSystem.getLocalFilePathFromUrl(
          traverse(this.props).get(['source', 'uri']),
          permanent,
        ),
        localFilePath => {
          console.log('Im here and the flag is: ' + this.mounted);
          this.setState({ localFilePath });
        },
        error => console.error(error), // eslint-disable-line no-console
      );
      this.mounted = true; // <--- SET flag to true
    }

    async componentWillUnmount() {
      // [...]
      this.mounted = false;
    }

And I get one console log with "I'm here and the flag is false". I've seen that the method cancelLocalFilePathRequest is called on unmounting, but as makeCancelable returns a Promise, is it possible that while the promise is being resolved some calls go through?
Sorry for the huge text 😄

The entire point of the makeCancelable() package is to prevent the "onSuccess" method from being fired if the initial this.fileSystem.getLocalFilePathFromUrl() promise takes too long to resolve and componentWillIUnmount() is fired first.
So if componentWillUnmount() is being fired before this.fileSystem.getLocalFilePathFromUrl() resolves, and STILL the "success" handler is getting fired (the part that calls setState()), that suggests to me there is a bug in the makeCancelable package.
I will have to investigate further but probably won't be able to for a few days. Shouldn't be a big deal since this is related to warnings that won't block your dev.
I'm going to try to get your PureComponent ticket handled today or tomorrow.

It's not a problem, just an annoying warning. If you want I can do some investigation and report if you point me in the right direction.

It's annoying though because I implemented the makeCancelable library specifically to resolve this issue.
Is there some way you can share code with me that would allow me to recreate it?
That is, spin up a throwaway app with react-native create, install react-native-iamge-cache-hoc and then recreate the issue you are seeing in your proprietary app and send me the code? I'm struggling to recreate this issue.
Thanks and Merry Christmas soon :-)

Ok, I'll try to do it by tomorrow.
Merry Christmas!! 🎄

I'm trying to reproduce the behaviour in a simpler app with no luck yet. I'll keep you posted.

Ok, finally! Here's the repo with the warning appearing: https://github.com/khrizt/image-cache-hoc-example Please don't look too much at the code 😋, I started adding things until I could reproduce it. If you need some clarification, please let me know.

Haha I assure you I won't judge, it would be weird if it was too good lol.
Greatly appreciate this. I Probably won't have time to fix until after Christmas but it's near the top of my todo list.

Okay I figured out the issue thanks to your test case.
The edge case occurs when componentDidMount() fires, but then execution of the function is paused while awaiting this.fileSystem.getFileNameFromUrl() to complete here.
Since the componentDidMount() function does not resume execution until the promise returned by getFileNameFromUrl() resolves, if the component is quickly unmounted after being mounted, componentWillUnmount() will fire before componentDidMount() resumes. In this scenario we end up getting to this code before we expect to, and thus not cancelling the makeCancelable() onfulfilled handler.
I'm going to rip out the makeCancelable library and just implement this logic myself.

Resolved https://github.com/billmalarky/react-native-image-cache-hoc/pull/9

Awesome man!!!! Thanks a lot! And Happy New Year!! 🎆

You too! Thanks for your help on this.
On Sat, Dec 30, 2017, 4:54 AM khrizt<EMAIL_ADDRESS>wrote:

Awesome man!!!! Thanks a lot! And Happy New Year!! 🎆
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/billmalarky/react-native-image-cache-hoc/issues/6#issuecomment-354537305,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxTUxY--yj_tCes0QtBdS7283Eb5Zi0ks5tFghwgaJpZM4Q_PEr
.


[IgnoreAntiForgeryToken] Not working in Razor Pages

Is this a Bug or Feature request?:
Bug
Steps to reproduce (preferrably a link to a GitHub repo with a repro project):
See below
Description of the problem:
Adding [IgnoreAntiForgeryToken] in a controller works as expected, however, adding it to a Razor Pages method has no effect.
Version of Microsoft.AspNetCore.Mvc or Microsoft.AspNetCore.App or Microsoft.AspNetCore.All:
2.1.0-rc1-final
Test Script
$Body = "message=PowerShell"
$Uri = "https://localhost:44387/Test"
(curl -UseBasicParsing -Uri $Uri -Body $Body -Method Post -ContentType "application/x-www-form-urlencoded").RawContent
$Uri = "https://localhost:44387/Contact"
(curl -UseBasicParsing -Uri $Uri -Body $Body -Method Post -ContentType "application/x-www-form-urlencoded").RawContent

Output
HTTP/1.1 200 OK
Pragma: no-cache
Transfer-Encoding: chunked
X-Frame-Options: SAMEORIGIN
X-SourceFiles: =?UTF-8?B?QzpcVXNlcnNcRXJpY1xTb3VyY2VcSXNzdWVzXElnbm9yZUFudGlGb3JnZXJ5VG9rZW5cVGVzdA==?=
Cache-Control: no-cache, no-store
Content-Type: text/html; charset=utf-8
Date: Sat, 19 May 2018 17:30:19 GMT
Set-Cookie: .AspNetCore.Antiforgery.oPQX9jHeIUM=CfDJ8Mtg_UjBP8dLpGAth2hE68d-IyvTEhGzHEtPh5gqWZyTAPQh1Q8Qe0L70AZE3ZBRurb7YCUuc_xEYjiNmCP12o6uVVZBVSMYacekaSn3BrlaCF7nwg4Ci7l736g3GrON7oJEgv7aiQmadaI4KmF7W
5I; path=/; samesite=strict; httponly
Server: Kestrel
X-Powered-By: ASP.NET

PowerShell

<form method="post">
    <input type="text" id="Message" name="Message" value="PowerShell" />
    <input type="submit" value="OK"/>
<input name="__RequestVerificationToken" type="hidden" value="CfDJ8Mtg_UjBP8dLpGAth2hE68cI5gq5FINEiYp098QnwwxvNGW9QT3-PsHlwEiVC1L_D1dWzfISgD1HSv3Qz-2uNfbvdMrcw_dcwDgYBnOpT6NVFhExpUd-3Rbb2WjEYHz8X4F1i2f
4XluCTCnW7h7vPWw" /></form>
curl : The remote server returned an error: (400) Bad Request.
At line:6 char:2
+ (curl -UseBasicParsing -Uri $Uri -Body $Body -Method Post -ContentTyp ...
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Dups #5863 but this keeps popping up, #6306, and I found more old issues and I followed the steps to work around it and expected it to be fixed (#5552) but now I read Order = 1000 isn't good enough but 1001 will fix it? Shouldn't this just work without having to fiddle with magic numbers?
Since this is a known issue I will not share my repro.

Thanks for contacting us, @ericwj.
@dougbu, can you please look into this? We may be missing a test for this scenario. If so, we should make sure we add some to avoid this issue going forward.

/cc @rynowak

Did you try putting the filter attribute on the class? This is one of the things that's confusing about pages and we have plans to add an analyzer.

There's a couple of interaction issues here that sort of culminate in this behavior

Both AutoValidateAntiforgeryTokenAttribute and IgnoreAntiforgeryTokenAttribute have the same filter order of 1000. If they are applied at the same scope, then their resulting order is undefined. The current implementation is basically to preserve the order in which they appear in the list.
AutoValidateAntiforgeryPageApplicationModelProvider appends AutoValidateAntiforgeryTokenAttribute to the filter list. Consequently, it's always ends up later in the list compared to a filter that's defined on a page model.
ValidateAntiforgeryTokenAuthorizationFilter picks the filter furthest away in the list of filters. If you don't mess around with the filter order, the auto one ends up being it.

The behavior is non-intuitive and it's not entirely obvious why a higher filter order should cause things to work. A couple of possible solutions to consider:

We continue relying on Order to work for us and change the value for IgnoreAntiforgeryTokenAttribute to 1001. Kinda hard to put this behind a compat flag.
Have the AutoValidateAntiforgeryPageApplicationModelProvider not insert the filter if it sees IgnoreAntiforgeryTokenAttribute has already been applied to the model. Should be easy to hide this behind a compat-switch.
Change the implementation of ValidateAntiforgeryTokenAuthorizationFilter to no-op if it sees any IgnoreAntiforgeryTokenAttribute. Essentially how IAllowAnonymousFilter works. Should be easy to hide this behind a compat flag. Kinda like this the best since the two concepts seem pretty analogous.
Do nothing and recommend setting an order.  There is also this nice feature called authorization which can help. Or alternatively a way to have a blank class and no HttpContext or ActionContext or whatever and just get a token.
Just like I would like to point some factory at my web app without any context and get an IUrlHelper which knows about the pages etc. But alas there is this decision...

The following suggestion is most appealing:

Change the implementation of ValidateAntiforgeryTokenAuthorizationFilter to no-op if it sees any IgnoreAntiforgeryTokenAttribute. Essentially how IAllowAnonymousFilter works. Should be easy to

Change the implementation of ValidateAntiforgeryTokenAuthorizationFilter to no-op if it sees any IgnoreAntiforgeryTokenAttribute. Essentially how IAllowAnonymousFilter works.

This is a no-go. We specifically rely on ordering to ensure that IgnoreAntiforgeryTokenAttribute can be overloaded. See https://github.com/aspnet/Mvc/commit/ca6c76c35883c5fa3d4d7467eb742b99e92198c1. I'm going with option B, which is pretty simple. @rynowak considers this a bug and consequently does not require a compat flag.

For 2.2.0, we'll honour IgnoreAntiforgeryTokenAttribute applied to a Razor Page model without the need to specify an order. They will not be supported per handler method but we should start producing build warnings if you attempt to do so (See https://github.com/aspnet/Mvc/issues/7684).


Authentik Documentation Improvements

Documentation updated to clarify that the URL cannot contain the trailing / that authentik automatically adds in the URL. Also many other updates to make it much easier to troubleshoot the configuration for new users. Finally screenshots to show an example working config.

Thanks you for this PR! (and sorry for the delay)


Bulk Update - Batch 1 of validation fixes for column headers.

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

File
Status
Preview URL
Details

docs/transport-agents/agent.md
:bulb:Suggestion
View
Details

docs/transport-agents/agentlist.md
:bulb:Suggestion
View
Details

docs/web-service-reference/acceptsharinginvitation.md
:white_check_mark:Succeeded
View

docs/web-service-reference/actingas.md
:white_check_mark:Succeeded
View

docs/web-service-reference/actions.md
:white_check_mark:Succeeded
View

docs/web-service-reference/actualwork.md
:white_check_mark:Succeeded
View

docs/web-service-reference/addblanktargettolinks.md
:white_check_mark:Succeeded
View

docs/web-service-reference/addnewteluricontacttogroup.md
:white_check_mark:Succeeded
View

docs/web-service-reference/address-string.md
:white_check_mark:Succeeded
View

docs/web-service-reference/addresses-arrayofaddressestype.md
:white_check_mark:Succeeded
View

docs/web-service-reference/adjacentmeetingcount.md
:white_check_mark:Succeeded
View

docs/web-service-reference/alternatemailbox-soap.md
:white_check_mark:Succeeded
View

docs/web-service-reference/altitudeaccuracy.md
:white_check_mark:Succeeded
View

docs/web-service-reference/applyconversationactionresponsemessage.md
:white_check_mark:Succeeded
View

docs/web-service-reference/appointmentstate.md
:white_check_mark:Succeeded
View

docs/web-service-reference/archivesourcefolderid.md
:white_check_mark:Succeeded
View

docs/web-service-reference/arrayofdomainresponse-soap.md
:white_check_mark:Succeeded
View

docs/web-service-reference/assigncategories.md
:white_check_mark:Succeeded
View

docs/web-service-reference/assignedtime.md
:white_check_mark:Succeeded
View

docs/web-service-reference/businessphonenumbers.md
:white_check_mark:Succeeded
View

docs/transport-agents/agent.md

Line 14, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Last modified: September 17, 2015' is duplicated in 'transport-agents/agent.md(14,14)', 'transport-agents/agentexecution.md(14,14)', 'transport-agents/agentlist.md(14,14)', 'transport-agents/configuration.md(14,14)', 'transport-agents/messagesnapshot.md(14,14)'....

docs/transport-agents/agentlist.md

Line 14, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Last modified: September 17, 2015' is duplicated in 'transport-agents/agent.md(14,14)', 'transport-agents/agentexecution.md(14,14)', 'transport-agents/agentlist.md(14,14)', 'transport-agents/configuration.md(14,14)', 'transport-agents/messagesnapshot.md(14,14)'....

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

@lindalu-MSFT, Please review and let me know if these bulk validation changes look okay. Thanks!


Add support for a configuration file

Hello,
This PR adds support for de-serializing a JSON configuration file (config.json). I chose JSON because is the only implementation that works in no-std.

[x] Add a configuration file
[x] Make it fault tolerant
[x] Write the tests
[ ] Write/Improve docs

Thanks!

Should we keep the kernel configuration as is, and use it as defaults if the config doesn't specify? In lieu of removing those options?

Also, shouldnt we load the config first? This would allow the kernel/ramdisk filenames to be set via config if desired (which i personally do desire.)
IE:

Set config to defaults.
If (config_present) load
for settings that are not set, do not set them leave defaults in place.
Load kernel, read kernel config.
For each setting not present in config file, apply kernel defaults.
load ramdisk
Continue as normal from this point.

We dont need to add the kernel/ramdisk settings now. My goal in these statements is to avoid a breaking api change when we want to add them, and preserve existing behavior.
We can probably even get away with loading the config after, so long as we keep kernel defaults and make the file optional (if it isn't already). We would then be able to refactor the config file as described above, while sticking to a minor semver bump (where as current seems major to be, since it's a breaking change)

@jasoncouture

Should we keep the kernel configuration as is, and use it as defaults if the config doesn't specify? In lieu of removing those options?

We definitely need to keep the frame buffer config in the kernel options for semver compatibility. However, we could mark it as deprecated. Removing the log-related config options is fine because they're not released yet.

Also, shouldnt we load the config first? This would allow the kernel/ramdisk filenames to be set via config if desired (which i personally do desire.)

We can do that, but I don't think that we need to do it in this PR. Loading it earlier shouldn't be a breaking change.

IE:

Set config to defaults.
If (config_present) load
for settings that are not set, do not set them leave defaults in place.
Load kernel, read kernel config.
For each setting not present in config file, apply kernel defaults.
load ramdisk
Continue as normal from this point.

I'm not sure if we should make all kernel config options overwritable. The kernel might rely on the config values, e.g. the specific address of a mapping or a minimum stack size. It's probably not a good idea to allow changing these values after compilation.

Thanks a lot!


JS arrays in INLINE_TASK are converted into objects by Nashorn

Describe the bug
I am trying to fill a JSON array dynamicTasksJSON of a FORK_JOIN_DYNAMIC task, using an IN_LINE_TASK. However the array of tasks is converted onto an object. This can be reproduced for any array in general.
The next task definition:
{
      "name": "INLINE_TASK",
      "taskReferenceName": "inline_test",
      "type": "INLINE",
      "inputParameters": {
        "evaluatorType": "javascript",
        "expression": "function scriptFun() { return [ 6, 7, 8] } scriptFun();"
      }
    },

Produces:
{
  "result": {
    "0": 6,
    "1": 7,
    "2": 8
  }
}

The expected result was:
{
  "result": [ 6, 7, 8 ]
}

Details
Conductor version: main branch at the moment of writing this ticket.
Persistence implementation: memory
Queue implementation: dynoqueue
Lock: noop
Workflow definition:

{
  "name": "test_js",
  "ownerEmail"<EMAIL_ADDRESS>  "description": "Test",
  "version": 1,
  "tasks": [
    {
      "name": "INLINE_TASK",
      "taskReferenceName": "inline_test",
      "type": "INLINE",
      "inputParameters": {
        "evaluatorType": "javascript",
        "expression": "function scriptFun() { return [ 6, 7, 8] } scriptFun();"
      }
    }
  ],
  "restartable": true,
  "workflowStatusListenerEnabled": false,
  "schemaVersion": 2
}

To Reproduce
Steps to reproduce the behavior:

register the workflow
start an instance
check the results

Expected behavior
{
  "result": [ 6, 7, 8 ]
}

Screenshots
Additional context
When trying to format the obtained result with a JQ task, I got a similar problem.

I don't know whether you can consider this a bug... it's an infortunate behaviour of nashorn. You have to cast the Array to Java arraylist. I usually do smth like "return {tasks: Java.to(tasks, 'java.util.Map[]')" when having to return Arrays of objects. Replace with java.lang.string or the type you need.
I was hoping that inline with javascript was not nashorn any longer btw...🙄

You are right is not a Conductor issue, is a dependency limitation. I am closing the ticket.  BTW your suggestion seems to work for me, and now I can feed DYN_FORK with a the of output of an INLINE task. Thank you


Impossible to read all rows: 'A non-timeout error during a read request' when SELECT without WHERE

The following query fails with Database returned an error: A non-timeout error during a read request (consistency: LocalQuorum, received: 0, required: 1, numfailures: 1, data_present: false), Error message: Operation failed for partly.entities_s - received 0 responses and 1 failures from 1 CL=LOCAL_QUORUM.
    let _ = self.session
            .query_iter("SELECT topic, id, entity FROM partly.entities_s", &[])
            .await
            .with_context(|| format!("failure to select entities_s !!!"))?;

Few observations:

I think (but I am not sure) it only fails when the table has rows spanning more than 1 partition (ie. there are at least 2 rows having different partition key values).
It works when the table is empty.
It fails for query, query_paged as as well as for prepared query via execute_iter.
It works if I add LIMIT 30000. But it still fails with the same error if I add LIMIT 100000 instead

Logs (a few lines before the query):
2022-04-01T12:13:22.597443320+00:00 TRACE scylla::transport::connection_pool: pool_state="[(0, [<IP_ADDRESS>:9042]), (1, [<IP_ADDRESS>:9042]), (2, [<IP_ADDRESS>:9042]), (3, [<IP_ADDRESS>:9042]), (4, [<IP_ADDRESS>:9042]), (5, [<IP_ADDRESS>:9042]), (6, [<IP_ADDRESS>:9042]), (7, [<IP_ADDRESS>:9042]), (8, [<IP_ADDRESS>:9042]), (9, [<IP_ADDRESS>:9042]), (10, []), (11, [<IP_ADDRESS>:9042]), (12, [<IP_ADDRESS>:9042]), (13, [<IP_ADDRESS>:9042]), (14, [<IP_ADDRESS>:9042]), (15, [<IP_ADDRESS>:9042])]"
2022-04-01T12:13:22.597481343+00:00 TRACE scylla::transport::connection_pool: [<IP_ADDRESS>] Adding connection 0x7fb8dc01f610 to shard 10 pool, now there are 1 for the shard, total 16
2022-04-01T12:13:22.597512058+00:00 DEBUG scylla::transport::connection_pool: [<IP_ADDRESS>] Pool is full, clearing 0 excess connections
2022-04-01T12:13:22.597532277+00:00 TRACE scylla::transport::connection_pool: pool_state="[(0, [<IP_ADDRESS>:9042]), (1, [<IP_ADDRESS>:9042]), (2, [<IP_ADDRESS>:9042]), (3, [<IP_ADDRESS>:9042]), (4, [<IP_ADDRESS>:9042]), (5, [<IP_ADDRESS>:9042]), (6, [<IP_ADDRESS>:9042]), (7, [<IP_ADDRESS>:9042]), (8, [<IP_ADDRESS>:9042]), (9, [<IP_ADDRESS>:9042]), (10, [<IP_ADDRESS>:9042]), (11, [<IP_ADDRESS>:9042]), (12, [<IP_ADDRESS>:9042]), (13, [<IP_ADDRESS>:9042]), (14, [<IP_ADDRESS>:9042]), (15, [<IP_ADDRESS>:9042])]"
2022-04-01T12:13:22.647284989+00:00 TRACE Executing query{node="<IP_ADDRESS>:9042"}: scylla::transport::iterator: Query failed error="Database returned an error: A non-timeout error during a read request (consistency: LocalQuorum, received: 0, required: 1, numfailures: 1, data_present: false), Error message: Operation failed for partly.entities_s - received 0 responses and 1 failures from 1 CL=LOCAL_QUORUM."
2022-04-01T12:13:22.647374904+00:00 TRACE Executing query{node="<IP_ADDRESS>:9042"}: scylla::transport::iterator: retry_decision="DontRetry"

My scylla cluster is just one host running localhost in docker in development mode.

For starters, consider marking your query as idempotent - SELECTs are generally always idempotent, as in "safe to retry".
http://rust-driver.docs.scylladb.com/stable/retry-policy/retry-policy.html#query-idempotence
I don't really know why a single node cluster would fail to return the rows, for that you'd need to inspect Scylla's logs and see what was the source of this error. In any case, marking the query as idempotent will allow Scylla to just retry extracting the failed page(s).

Thanks for suggesting to check the logs. It shows the query was unpaged, which is a surprise because the docs for execute_iter and query_iter suggest these do paging internally.
WARN  2022-04-04 08:03:53,929 [shard 1] mutation_partition - Memory usage of unpaged query exceeds soft limit of 1048576 (configured via max_memory_for_unlimited_query_soft_limit)
ERROR 2022-04-04 08:03:53,950 [shard 1] storage_proxy - Exception when communicating with <IP_ADDRESS>, to read from partly.entities_s: std::runtime_error (Maximum amount of memory for building query results is exhausted, unpaged query cannot be finished)

Ok. it turned out I needed to set page size to 10000 on the query to fix it. Is there any default page size set?

Ouch, you're right, that's a bug. We should provide a default page size for query_iter, otherwise it's really unpleasant to use. Thanks for reporting this!

driver version: scylla = "0.4.2",
scylla version: 4.5.4-0.20220220.53b0aaa4e
@piodul yes this is the case, I traced it in the code...

no worries, I am very impressed with the driver so far... great library!

release 0.4.4 contains the fix, I encourage you to omit the micro release part in Cargo.toml: `driver version: scylla = "0.4" to get these kinds of updates without having to do anything.


test: improve coverage

coverage: 97.617% (+0.8%) from 96.783% when pulling 8b4b6ce226fdfe19b6d734110f9adc0a3cfa4358 on test/improve_coverage into 873e4c24f9ca6b1e4c6e8ff94899e4c559f49f0b on master.

:tada: This PR is included in version 3.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


enhancement suggestion: choose cluster later

When you first sign up, you have to choose a cluster, but there is no information about what the clusters are. Why not let people sign up first and then choose a relevant cluster when they know what to choose. This would also give you the opportunity to highlight which clusters are most in need of volunteers.

@BillWagner Is this issue still relevant?

Thanks for reminder. I will close this as by design: volunteers will always know their cluster when registering, and will never* change it.

Well, almost never. But close enough to never that we won't add this feature.


Add basic Lark grammar and tests for string literals

Implements a basic Lark grammar for string literals and introduces a test for parsing string literals using this grammar.

Grammar Definition: Adds a new file grammar.lark that defines a basic Lark grammar capable of handling string literals, including both single and double-quoted strings.
Testing: Removes the placeholder file tests/test_dummy.py and introduces tests/test_string_literals.py. This new test file contains a function test_string_literal_parsing() that utilizes the defined grammar to parse a simple string literal and asserts the correctness of the parsing result.

For more details, open the Copilot Workspace session.

Update the assertion in test_string_literal_parsing to match the actual output format generated by the parser.

Changes the expected string in the assertion to include single quotes around string and STRING, ensuring the test passes by matching the actual output format.

For more details, open the Copilot Workspace session.


Suggestion: add django-baton

Hi,
I would like to suggest to add django-baton (https://github.com/otto-torino/django-baton) in the admin section.
Thanks.

I use it for side projects; it should be listed.

Looks good. Can you submit a PR please?


Cross linking of CNCF and CDF landscapes

In discussions between the CNCF and CDF groups with Chris, Priyanka, Tracy, and myself, we would like to provide better visibility of these two landscapes with each other since there is a lot of overlap.
We had two ideas on how to showcase this to users:

Put a box for the CDF inside of the Continuous Integration and Delivery box in the CNCF landscape (and do something similar on the CDF side)
Embed the landscape similar to how Serverless is embedded in the CNCF landscape (so a thumbnail version of the landscape that you can click on to navigate)

For reference, here are the landscapes we would like to do cross-linking on:

https://landscape.cncf.io/
https://landscape.cd.foundation/

What is the best way to accomplish this?

I moved this issue to the CNCF landscape app project instead: https://github.com/cncf/landscapeapp/issues/716


Revamp graphql API

Changes:

Add versions of everything that replaces "wallet" with "account".
Deprecate "wallet" fields
Add xAccount field for almost every field x that is a public key and deprecate x.
Two small breaking changes: change the argument name of setStaking to publicKeys and setSnarkWorker arg to publicKey.

Uses https://github.com/andreas/ocaml-graphql-server/issues/33#issuecomment-283982659 to handle the recursion in account + delegateAccount.
Diff is mostly large due to needing to rearrange some things because more stuff references accounts now.
This introduces some duplication but we should be able to remove the old stuff a couple of releases from now.

@wu-s-john I don't know if you noticed the temporary duplication being called out in the PR description.
Was more or less trying to optimize for the non-temporary state (simpler diff when we remove).
Anyway I pulled the duplicated resolvers into their own variables, but we'll ideally need to remember to put them back when we dedupe the deprecated queries.

Made the suggested docs improvments, in the interest of landing this, I'm going to leave the other ideas for later.

Was included in https://github.com/CodaProtocol/coda/commit/fff3b856476c4ac65cad48bbea15177935249f40


DiscordOAuthSession Lost access token should be preserved considering its longevity.

When the DiscordOAuthSession  instance fetches the access_token on callback, the information contained in the token is this:
{'access_token': '...', 'expires_in': 604800, 'refresh_token': '...', 'scope': ['identify', 'guilds'], 'token_type': 'Bearer', 'expires_at':<PHONE_NUMBER>.1969795}.

(tokens removed for obvious reasons).
This information is lost in the examples supplied but can be preserved in this way:
client = DiscordOAuthClient(CLIENT_ID, CLIENT_SECRET, REDIRECT_URI)
....

@app.get('/callback')
async def callback(code: str):
    async with client.session(code) as session:
        token = session._discord_token  # notice protected attribute access

The expires_in field gives the amount of seconds that the token should last before it expires, in this case its 604800 which amounts to one week.
As follows, its unreasonable that the same token information cannot be used in following requests.
The DiscordOAuthSession instance must be able to be constructed from a valid token instead of only with the code
# following the client's construction
client = DiscordOAuthClient(CLIENT_ID, CLIENT_SECRET, REDIRECT_URI)

# sessions should be able to be constructed from the exchanged code on login redirect
session = client.session(code='dhjaksdhjadskhdaskjda')
# or with a stored, valid token
session = client.session(token='dsjkdsaljdaskldas')

Aditionally, it would also be useful if there was a token_updater method that would make use of the supplied refresh_token.

I'm working on a PR to solve this issue.

I honestly wasn't aware tokens could last up to a week. From what I'd seen in the docs it was my understanding that the tokens should be discarded after use. This is also why I made the token a private attribute.
The ability to construct a session from a valid session is definitely something worth adding. Should probably add a property for accessing the token as well. I'll take a look at your PR tomorrow, I'm sure we can get something worked out.
Appreciate the help!

Fixed in most recent PR. 👌


bpf: ct: clean up redundant 0-initializiations for CT entry creation

Follow-up for https://github.com/cilium/cilium/pull/30344/commits/7abe5e7c3cdccafa97223fc0c10d70e1ef95ba55:

Note that this introduces a few additional explicit initializations of the
fields in ct_state, and we can potentially avoid some of them. But this
in-detail investigation is best done in a later patch.

Let's do this now :).

/test

(CI is still recovering from the GH outage)

/ci-aks

/ci-e2e

/ci-gke

/ci-clustermesh

/ci-integration


No templates found matching: 'blazerserver'

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/create
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
No templates found matching: 'blazerserver'

Odd. I installed .Net 3.1 Core SDK and then it worked.

Maybe it was just a typo. It's supposed to be blazorserver, not blazerserver.

Damn! I have these days the older I get! Thanks :)


0.3.0 fails to install for ia32

Trying to install release 0.3.0 from npm with node-v8.16.2-win-x86 (for which no prebuild is included) fails with Error: Cannot find module 'node-addon-api'.

Log
X:\node32test>node --version
v8.16.2

X:\node32test>node -e console.log(process.arch)
ia32

X:\node32test>npm --version
6.12.0

X:\node32test>npm install native-reg
                                                                                s\.staging\node-gyp-build-db3562f8 (1407ms)
><EMAIL_ADDRESS>install X:\node32test\node_modules\native-reg
> node-gyp-build

X:\node32test\node_modules\native-reg>if not defined npm_config_node_gyp (node "node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
module.js:550
    throw err;
    ^

Error: Cannot find module 'node-addon-api'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at [eval]:1:1
    at ContextifyScript.Script.runInThisContext (vm.js:50:33)
    at Object.runInThisContext (vm.js:139:38)
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:653:30)
    at evalScript (bootstrap_node.js:479:27)
gyp: Call to 'node -p "require('node-addon-api').gyp"' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (node_modules\npm\node_modules\node-gyp\lib\configure.js:351:16)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.18362
gyp ERR! command "node.exe" "node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd X:\node32test\node_modules\native-reg
gyp ERR! node -v v8.16.2
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open 'X:\node32test\package.json'
npm WARN node32test No description
npm WARN node32test No repository field.
npm WARN node32test No README data
npm WARN node32test No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Walther\AppData\Roaming\npm-cache\_logs\2019-12-06T07_50_47_256Z-debug.log

X:\node32test>

I can fix that by moving node-addon-api from devDependencies to dependencies in package.json. It’s a bit of a shame to have another megabyte of dependencies that is not needed in all cases, but at least it doesn’t have any subdependencies.
In addition, the following change would prebuild binaries for both 32- and 64-bit runtimes. It restricts development to environments that have compilers for both of these architectures though, so I leave it up to you whether that is worth it. (And it increases the package size by 60 kB.)
diff --git a/package.json b/package.json
index b34b1e5..f0ed6b0 100644
--- a/package.json
+++ b/package.json
@@ -32,7 +32,7 @@
     "clean": "rimraf build lib prebuilds",
     "build": "npm run build:js && npm run build:bindings",
     "build:js": "tsc -p src",
-    "build:bindings": "prebuildify --napi --target<EMAIL_ADDRESS>+    "build:bindings": "prebuildify --napi --target<EMAIL_ADDRESS>--arch x64 && prebuildify --napi --target<EMAIL_ADDRESS>--arch ia32",
     "test": "node test"
   },
   "dependencies": {

By the way, I notice that the 0.3.0 tarball on npm includes the .idea folder, even though it is not mentioned in files in package.json. Any idea what happened there?

Thanks for the excellent investigation!
Hmm I think the .idea folder thing is a yarn bug, it shows up in yarn pack but not npm pack. I'll switch back to .npmignore if that works, otherwise I guess I'm going to have to remember to use npm publish 😕.
Given that we're windows-only and N-API, we have a small, closed set of builds that are valid, ideally just the 32 and 64-bit builds, but I don't really like that the fallback doesn't work. Easy enough to add the 32 bit build for now, 60kB is not much in comparison to other packages, and just disable the post-install. If anyone wants something else (electron builds? They already have a tray API though)

Just published v0.3.1 with included 32-bit build - let me know if it works for you!

Unfortunately not, on both architectures:
X:\node64test>npm install native-reg

><EMAIL_ADDRESS>install X:\node64test\node_modules\native-reg
> using prebuildify

'using' is not recognized as an internal or external command,
operable program or batch file.
npm WARN enoent ENOENT: no such file or directory, open 'X:\node64test\package.json'
npm WARN node64test No description
npm WARN node64test No repository field.
npm WARN node64test No README data
npm WARN node64test No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `using prebuildify`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Walther\AppData\Roaming\npm-cache\_logs\2019-12-06T10_39_24_696Z-debug.log

Does that “using” mean anything to yarn or to a newer npm? It works for me when I just remove the "install": "using prebuildify", line.

🤦♂

Not having an install step would mean it would ignore the prebuilds and try build anyway, in my previous experience, but that seems to be version dependent. so I've used "install": "echo using prebuilds", just to disable the default, in the past. Missed the echo in that build.
I should not be publishing code at 11PM 😴
Just doing some last testing to make sure It's not broken again...

Ok, v0.3.2 should have this fixed for realsies now. 🤞
It seems from my testing npm checks gypfiles: false is set, but yarn ignores that, and will run node-gyp build unless scripts.install is set to a non-empty command. The simplest option is to just echo something sensible.

Ah, makes sense.
Yep, working fine now. Thanks, goodnight and have a nice weekend!


How to configure alertmanager to use a forward proxy?

Hi guys, I installed prometheus-operator on k8s 1.6.4. Outgoing traffic from the cluster goes thru a corporate proxy.
Based on this issue, it seems like alertmanager can pick up https_proxy from the environment. However, the docs don't indicate how to configure it in the alertmanager manifest.
What's your suggestion to pass the https_proxy environment vars to alertmanager? Thanks! :)

I realize this is something that is required, but IIRC it is merely a coincidence that the environment variable works for the Alertmanager. I would like to make sure that we have a lasting solution here.

I’ve scanned thru Alertmanager’s logs and nothing is mentioned about configuring a proxy. For the time being, is it possible to inject the proxy env vars into the Alertmanager manifest?

On 8 Jun 2017, at 22:06, Frederic Branczyk<EMAIL_ADDRESS>wrote:
I realize this is something that is required, but IIRC it is merely a coincidence that the environment variable works for the Alertmanager. I would like to make sure that we have a lasting solution here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/coreos/prometheus-operator/issues/399#issuecomment-307114123, or mute the thread https://github.com/notifications/unsubscribe-auth/AJjUqAnZNIwIFmt_1u_0WdI4UGbdDL2Rks5sB__mgaJpZM4Nzn2q.

The problem is that it is not clear whether the proxy should be configured via the configuration file or otherwise. Typically all Prometheus projects are only configured via configuration file, and this case that the proxy is usable via environment variable is pure coincidence, because of how the underlying http client works. I would like to avoid introducing things in the Alertmanager/Prometheus TPR that is unclear whether it may be deprecated soon. It feels like the http proxy config should be a part of the Alertmanager receiver configurations.
Luckily all maintainers of the Prometheus Operator are Alertmanger maintainers, so we can relatively easily take this upstream if necessary.

I understand the importance of doing this the right way. Do you mean that there isn’t a way to pass the env vars to Alertmanager in Prometheus-operator? I’m seeking a temporary quick fix while we work out the correct way for the long haul.

On 8 Jun 2017, at 22:47, Frederic Branczyk<EMAIL_ADDRESS>wrote:
The problem is that it is not clear whether the proxy should be configured via the configuration file or otherwise. Typically all Prometheus projects are only configured via configuration file, and this case that the proxy is usable via environment variable is pure coincidence, because of how the underlying http client works. I would like to avoid introducing things in the Alertmanager/Prometheus TPR that is unclear whether it may be deprecated soon. It feels like the http proxy config should be a part of the Alertmanager receiver configurations.
Luckily all maintainers of the Prometheus Operator are Alertmanger maintainers, so we can relatively easily take this upstream if necessary.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/coreos/prometheus-operator/issues/399#issuecomment-307126530, or mute the thread https://github.com/notifications/unsubscribe-auth/AJjUqMg7VfbcbGutBH4LuJJ_PMufO-bfks5sCAmVgaJpZM4Nzn2q.

There is currently no way to do this with the Prometheus Operator, as you can't control the StatefulSet that the Prometheus Operator creates for the Alertmanager cluster. If that is indeed something you need right away, I would suggest to not use the Prometheus Operator for that Alertmanager cluster and configure it manually right now. It is definitely something we need to address though.

Thanks for the confirmation :) I’ll open a ticket with the Alertmanager folks and see what they say.

On 8 Jun 2017, at 22:55, Frederic Branczyk<EMAIL_ADDRESS>wrote:
There is currently no way to do this with the Prometheus Operator, as you can't control the StatefulSet that the Prometheus Operator creates for the Alertmanager cluster. If that is indeed something you need right away, I would suggest to not use the Prometheus Operator for that Alertmanager cluster and configure it manually right now. It is definitely something we need to address though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/coreos/prometheus-operator/issues/399#issuecomment-307129093, or mute the thread https://github.com/notifications/unsubscribe-auth/AJjUqG_o8yMCOph5d67-inX4DIIdfflpks5sCAt_gaJpZM4Nzn2q.

Go for it! As I said pretty much the same folk as here, so talk to you there :smile:

https://github.com/prometheus/alertmanager/pull/1222

Thanks for pointing out @luisyonaldo. With that patch, this is now possible. Closing here :tada:

The latest release of prometheus-operator is v0.17.0, which uses v0.14.0 of alertmanager.
The new http_config.proxy_url functionality wasn't introduced to alertmanager until after v0.14.0 - it is present in v0.15.0-rc.0, but between those two versions of alertmanager there were non-backwards-compatible changes made to the alertmanager flags (so I can't just simply use v0.17.0 of prometheus-operator with v0.15.0-rc.0 of alertmanager). So I'm kinda feeling stuck waiting for a new version of prometheus-operator to come out.
So in the meantime...
(Regarding what @brancz  said above about how "you can't control the StatefulSet that the Prometheus Operator creates for the Alertmanager cluster", by looking at the prometheus-operator/pkg/alertmanager/statefulset.go code, I can see he's right.)
I know it would be an unsupported temporary hack to set the http_proxy environment variable in the alertmanager pod, but if anyone knows of a way to do that, could you please tell me how? I tried doing the following, but the env var only seems to actually get set (and stay set) some of the time - here's an e.g. of when it didn't work (i.e. the grep shows that http_proxy wasn't actually set):
core@myIp ~ $ kubectl -n monitoring set env statefulset/alertmanager-main --all "http_proxy=http://<IP_ADDRESS>:8080"
statefulset "alertmanager-main" env updated
core@myIp ~ $ kubectl --namespace=monitoring exec -ti alertmanager-main-0 -c alertmanager env | grep -i prox
core@myIp ~ $

Background info: The K8s cluster that I'm running kube-prometheus on is inside a "closed" cluster (which is not directly available to the internet) that can only reach out to the internet via our proxy. So in order for notifications sent from alertmanager to reach our HipChat room (via the default value of https://api.hipchat.com/ for 'hipchat_api_url'), I need to be able to tell alertmanager to use our proxy.

We are already implementing support for v0.15 for the alertmanager and a new release is around the corner, your problem will soon be solved :)

Awesome, thanks @brancz . Just curious, is there anywhere I can look online where a rough guess has been shared as to when the next release of prometheus-operator will be coming out?
In the mean time, I've found that sometimes i need to run the aforementioned kubectl set env command several times in order for it to work, but even when it does work then after some amount of time (just a guess: perhaps when the alertmanager pod restarts / or when K8s moves the pod to another node) I've noticed the environment variable will no longer be set in that pod. If by chance anyone has any suggestions for this, I'd be all ears. Though no worries if we just wait til the new release (which will introduce http_config.proxy_url).

@brancz Any hack for injecting environment variables into the pod? Also, do you have an ETA on the next release of the operator?

The latest release of the prometheus operator already supports the Alertmanager v0.15 series which supports this.

based on documentation .. inside alertmanager.yml file, we can define as below:
global:
hipchat_api_url: 'https://company.hipchat.com'
http_config:
proxy_url: 'http://(IP):3128'


Announcements page issue

On iOS the content of the Announcements page scrolls over and obscures the title bar.

I confirm the same bug on Android.

It looks like we forgot to open (and close) an issue about this but it has already been solved. I'll be on production today.

My bad, this is still not solved. Reopening.


Dolby Cinema Processor CP750 (addition to existing module dolby-cinemaprocessor v1.1.1)

Device: Dolby Cinema Processor CP750
Features to be controlled: Those already available in dolby-cinemaprocessor v1.1.1, which allows control of CP650 and CP950.  The issue is that the ASCII strings themselves are model-specific (in this case, they all begin with "CP750.sys"), so the existing module does not work.
I would like to kindly request the addition of CP750 as a third supported device. Please find attached an extract from Dolby installer manual listing the relevant commands. If it's easier, even a generic "send the following ASCII string to device" command would be very helpful, each user could customize it by just copying and pasting from the table (that is actually how digital cinema servers control Dolby processors, so most of the user base is already quite familiar with this). Thanks!

I can try to add this but will have to also convert the module to the new v3 code base. So not sure I will have any spare time for awhile unless it was a paid project.

Hello @pclarici this support will be available in v2.0.0 of the module. Have a great day


Nav mobile button moves/messes layout when clicked, to the top and left

This is the original position:

and this is what happens when clicking the button

here is the code:

		<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContentMobile" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">

		</button>

Duplicate of #32532.

I would prefer to close the other post, since I get no replies at all there.


feat: Linear programming in the standard form

[x] depends on: #9652

Alternative: #7386

Another alternative:
https://github.com/leanprover-community/mathlib4/pull/10026


use new nuget dependency solver by default

This PR inverts the nuget_dependency_solver experiment and uses the new behavior by default by always setting the environment variable UseNewNugetPackageResolver=true unless the new experimental flag nuget_legacy_dependency_solver is set, in which case the old behavior will be used.
Depends on PR github/dependabot-api#5708

🤩


FILEUPLOAD-315 - java8 improvement

Coverage decreased (-0.1%) to 78.219% when pulling 60b7e11c660b528af91e68893c5e1414df5f592a on arturobernalg:feature/FILEUPLOAD-315 into b8253237867120ec8c99ea34b68ac86c6283dbc3 on apache:master.


Cleanup after catalogsource is deleted

Issue:
The packages and bundlemetadata doesn't seem to be deleted when the catalogsource is deleted.
Steps to reproduce:

Follow the steps in the README.md.
Create a catsrc CR with image being: docker.io/anik120/community-operator-index:v4.11
Delete the catsrc CR
The packages and bundlemetadata is expected to cleanup, but it still persists.

The owner references doesn't seem to be set in the packages:
➜  catalogd git:(poc/catsrc-v2) ✗ k describe packages.core.catalogd.io zookeeper-operator
Name:         zookeeper-operator
Namespace:
Labels:       <none>
Annotations:  <none>
API Version:  core.catalogd.io/v1beta1
Kind:         Package
Metadata:
  Creation Timestamp:  2023-03-30T16:30:51Z
  Generation:          1
  Managed Fields:
    API Version:  core.catalogd.io/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:spec:
        .:
        f:catalogSource:
        f:channels:
        f:defaultChannel:
        f:description:
        f:icon:
      f:status:
    Manager:         manager
    Operation:       Update
    Time:            2023-03-30T16:30:51Z
  Resource Version:  1489
  UID:               8eab1b43-2623-46f8-b423-9e264c8c8a4f
Spec:
  Catalog Source:  catalogsource-sample
  Channels:
    Entries:
      Name:         zookeeper-operator.v0.10.3
      Name:         zookeeper-operator.v0.11.0
      Replaces:     zookeeper-operator.v0.10.3
    Name:           alpha
  Default Channel:  alpha
  Description:
  Icon:
Status:
Events:  <none>

So I think this has to do with the default image being used for the controller is quay.io/operator-framework/catalogd-controller:latest and I don't think that image has been updated to reflect the current main branch. Building the images from main and using them I was able to see the expected behavior and owner references.

@varshaprasad96 I just pushed the latest from main manually, and confirmed what @everettraven said. It did take a wee bit for garbage collection though, we'll have to think about that more (sounds like a potential for "distorted source of truth", if eg deppy resolves a request for installation in the time period between when the catsrc was deleted, and the content is GC'ed. Today's resolver has a lot of these "cache corruption" issues too).
But for now if you can confirm that, we can close this issue.

Thanks @everettraven and @anik120 for looking into this!
@anik120 That would definitely bring the problem of consistency. We would need to mark the cache stale once and re-populate it if there is any change. That way resolver knows that it is using a stale cache. But this is an issue to be discussed later and not in the scope of this one. Closing this one!


Exporting to MISP objects with relationships

Beagle is really cool. Looking at it, it could make sense to export the result of the analysis and especially a graph in MISP objects format with relationships (it's a kind of graph) into MISP. This would allow users to share investigations and discoveries.

That sounds like a good idea. I'm guessing someone wouldn't want to add a full graph. I'll try to write something that maps specific Edge or Node objects to their MISP counterparts.
This should allow someone using the library to manipulate a networkX object, then use the set of nodes and edges they have to generate MISP objects.

Indeed from the networkX object it would be the cleanest. I need to dig to see what are the missing objects in MISP objects and maybe also in the relationships to map with your existing parsers in Beagle.

I would focus on the objects in here: https://github.com/yampelo/beagle/tree/master/beagle/nodes rather than the parsers. The parser will only ever return instances of these classes (or subclasses of them)


Narrowing with a typeguard fails on condensed expression

Bug Report
🔎 Search Terms
narrowing, union, control flow analysis, type guard
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about discriminated unions

⏯ Playground Link

Playground link with relevant code
💻 Code

type StringFoo = {fooString: "string"}
type RawFoo = {fooString?: string}
type DecoratedFoo = ({isString: true} & StringFoo) | {isString: false; fooString?: string}

function isStringFoo(foo: RawFoo): foo is StringFoo {
    return foo.fooString !== undefined
}

function decorate(foo: RawFoo): DecoratedFoo {
    // try 1:
    //
    // I would expect the below commented out return statement to work,
    // since they are the same expression as the broken up ternary below it
    //
    // return {
    //     isString: isStringFoo(foo),
    //     ...foo
    // }

    // try 2:
    //
    // I thought maybe pulling out the typeguard into its own aliased discriminant
    // might make typescript realize the types, but this still fails typechecking
    //
    const isString = isStringFoo(foo)
    // return {
    //     isString,
    //     ...foo
    // }

    return isString ? {
        isString,
        ...foo
    }: {
        isString,
        ...foo
    }
}

🙁 Actual behavior
I expect condensing the ternary to a single expression to still yield the same result via control flow analysis
🙂 Expected behavior
once the ternary is condensed into a single expression as above, typescript no longer recognizes the type literals and discriminated union, even though the property assigned to the object is a type literal.

this is happening when working with our grpc library. the types generated by the protobuf compiler is loose, so we provide a discriminant key that can narrow the loose type into a stronger type. utilizing this requires writing ternary expressions that are trivially collapsible, because actually collapsing the ternary makes typechecking fail.

The implicit proposal here is that we do a combinatorial expansion of all possible types the spreaded object can have, taking into account control flow effects that one property might have on another.
It turns out people can and do write enormous spreads that look like this (shown with the spreaded expressions inlined for clarity)
return {
   ...{ a: someStringOrNumber },
   ...{ b: someStringOrNumber },
   ...{ c: someStringOrNumber },
  // dozens more
}

so producing this kind of combinatorially-exploded type is not something we can do in practice

I see, that makes sense, re: combinatorial explosion. Would typescript need to compute the combinatorial even if the type guard were aliased and therefore executed before the object spread?
Also, is there a recommended way to write these types of expressions that aren't obviously collapsible?

Normally I'd do this in such scenarios:
return isStringFoo(foo)
  ? {isString: true, ...foo}
  : {isString: false, ...foo};

Mostly because I prefer using string literals as discriminators, so if I could control the type it would be this:
return isStringFoo(foo)
  ? {stringType: 'foo', ...foo}
  : {stringType: 'other', ...foo};


Fixed NullReferenceException in RateLimitUpdater

Fixed NullReferenceException in RateLimitUpdater when rate limit information returned by GetOrCreateQueryRateLimit is null.
This commit is targeted on 1.3

Any reason why this has not been merged yet?
This problem keeps us from using tweetinvi rate limit handling at all.
Same for #547

The only reason is that I did not have time to look at Tweetinvi for the last 3 months unfortunately.
I will merge them both.
Thanks

(moved to 2.1) for reminder


Conversion to snake case should convert only case, not other characters

Let's have a string
\My\AppBundle\App\Twig\GoogleTagManagerDataLayer
I want to convert it to
my.app_bundle.app.twig.google_tag_manager_data_layer
That seems to be the exact case for string manipulation plugin. But it's currently not possible. If I call "to snake_case" on it, it creates
my_app_bundle_app_twig_google_tag_manager_data_layer
I would expect the plugin to work on case (i.e. only convert [a-z][A-Z] to \1_\2) and not touch unknown characters. Current behaviour IMO severely limits use cases. What is this behvaiour's use-case?
My other typical use case would be
Some\PHP\SubNamespace -> some/php/sub-namespace.twig (i.e. replace slashes + to hyphen-case)

No use-case, only edge case.

Sorry, I'm not sure I understand.

You asked "What is this behvaiour's use-case? " :)

Wow, thank you for speedy fix! ❤

I've just updated to the new version and it works great! Thank you 👍


fix(datepicker-inner): activeDate

When changing view on datepicker, and going left and right, selected date (activeDate) will stay the same.
Not emitting date on move action.

@edinfazlic as usual

commit name fix(datepicker): ...
Date.valueOf is slower than to string, or implicit to number conversion (please just in case check in jsperf)

Fixed commit message.
Regarding the valueOf, here is the jsperf: http://jsperf.com/date-clone-comparation
Since there is no the same constructor in ts as in js: Date(date:Date) we cannot use that fastest method.
The other two which are the same are getTime() and valueOf(), and valueOf() sounds cleaner as getTime() may make you think that you only need time.
I agree with 2nd top answer (http://stackoverflow.com/questions/1090815/how-to-clone-a-date-object-in-javascript)


Does pytorch Grad-cam support image regression as well?

In the tutorials, I saw that you could use Grad-cam for image classification tasks to visualize the important features that has led to the predictions of any present target class in ImageNet for a certain image. Could you use Grad-cam for image regression as well? For example, the model predicts someone age 58 years and I want to know where the model is looking at to decide someone is that age.

Yes.
You can just use the BinaryClassifierOutputTarget target from utils.model_targets.
BinaryClassifierOutputTarget
The name classifier can be removed from that class since it holds for regression as well.
The category it accepts will be 0 or 1.
If 1, it will show what pulls it towards higher ages.
If 0, it will show what pulls it towards lower ages.
I would start with this.


Feature request: animate when a child is displayed: none in the DOM.

It will be awesome to be able to animate when toggling display property to display: none; instead of only

u could use framer motion for that

Would be cool, but falls outside the scope of this project for now. Maybe we'll revisit this someday in the future.


Auto video  rotate not working when device rotate

@bawantha please check the latest version. kindly update us if any feedback. We are happy to help you. Thank you.


Create new application in current directory

When the following command is executed:
revel new ./NewApplication

The new project should be created in current working directory. Instead it is being created in $GOPATH/src/ directory.

Due to how Go requires packages to be inside of a $GOPATH we cannot support this request. Something related has been added to detect the current $GOPATH you are in (if any).
Thanks for offering this feature idea.

Due to how Go requires packages to be inside of a $GOPATH we cannot support this request.

I think you can: https://github.com/revel/revel/issues/1004#issuecomment-221785882.
https://github.com/revel/cmd/commit/b85dd76b3efb094a382bffac8bae1c1e9d49ec90 added support of multiple GOPATHs but not of relative paths.

@alkchr I see what you're saying. We can add some logic to allow relative paths within a $GOPATH. It seems a little bit magical, but it should work as expected.
@jeevatkm shall we reopen this for v0.14?

User mentioned:

Instead it is being created in $GOPATH/src/ directory.

I would like to clarify this, is it relative path request or request for creating a project outside $GOPATH/src?

What @tejainece mentioned...
The new project should be created in current working directory. Instead it is being created in $GOPATH/src/ directory.
Which seems a bit daft to me.

@jeevatkm It doesn't matter. It is possible to support both absolute and relative paths with multiple GOPATHs. That's all we need to know. Whether we want to implement it or not and what's the priority of this issue is another question.

Though wait, you about this issue, not #1004.

@alkchr yes this issue, not #1004

@alkchr - Thanks for clarifying. Please continue to share your thoughts on improving Revel.
@brendensoares - We are not reopening this issue.


CI: Revocation on startup

Sometimes a revocation on startup happens:
https://buildkite.com/scionproto/acceptance/builds/439#c1640b42-6fb2-49a1-8afd-776ea88680d6
This messes with the tests big time, because network is broken for 10 seconds.
We should investigate why the revocation happens in the first place

Not seen in a long time


Scrolling notes

Hi,
I like this application, but I have a problem with Springseed. If I create several notes I can't reach last notes because they are unreachable. The last notes sticking out from the window.
Version: 2.0
OS: Ubuntu 14.04 LTS
DE: Unity

Hello!
I installed version 2.0 in Ubuntu 14.04 and this bug continue. The last notes sticking out from the window.
Thanks!

Confirmed, Ubuntu 14.04 LTS, Springseed 2.0 (64-bit) downloaded from the getspringseed.com.
Can not scroll notes. The only way to get to the note that is at the bottom is to maximize window.


Update LAION-example and default value of scheduled_tasks

Changes

Update LAION-example to use threadpool_map
Change  default value of scheduled_tasks to 500

128 was still to low - at least with a timeout of 5 seconds. With this new value I am mostly limited by my internet connection.
I have also compared the speed to async_map. With the correct values (high batch_size e.g. 800 and high enough max_concurrency e.g. 64) I get similar performance - also limited by my internet connection.


NET 6 Wasm Prerendered with persist state component vs HybridBlazor

Hi, I like to know does you have plan to change solution to use new was prerender which is available in NET 6 and persist state component?
NET 6 Wasm prerendered has one disadvantage against your solution. Page is static until WASM is loaded, user can't interact.
Did you analized it is possible use new NET 6 solution and have interaction when WASM is not loaded yet?

Hi,
PersistentComponentState is used in https://github.com/jdtcn/HybridBlazor/blob/715eeb0e0d2e2a113f37fad0f9595b57299b79ae/HybridBlazor/Client/Pages/FetchData.razor#L43
Prerendering enabled too https://github.com/jdtcn/HybridBlazor/blob/715eeb0e0d2e2a113f37fad0f9595b57299b79ae/HybridBlazor/Server/Pages/_Host.cshtml#L29
In general, the whole idea of the project is to have interaction when WASM is not loaded yet.

Ok, thanks for replies.

Hi, I have one question more. When blazor is using WebAsssemblyPrerendered then PersistentComponentState avoided  execute ForecastService.GetForecastAsync when switched from static files to WASM.
In your solution PersistentComponentState works only for server mode. When page is switched to WASM then ForecastService.GetForecastAsync is invoked again.
Does it is possible to persist state with PersistentComponentState between server and wasm in your solution?

Surely this is possible, but it is hardly easy to do, I have not tried it. I don't understand why use WebAssemblyPrerendered because prerendering will already be done in ServerPrerendered mode.
You can also look towards the https://github.com/servicetitan/Stl.Fusion library if you need to manage complex state

Thanks for help. Btw. I don't want to use WebAssemblyPrerendered. I puted this as example to compare with your solution.


Can't delete links

when i click OK on the prompt, the link i deleted it is gone but when i reload the page it's still there

Did you click the save button?

The button is disabled, can't click


Import into HomeKit as Air Purifier device type?

Hi, with Homebridge, I am able to import my Winix C545 into Home.app as an 'Air Purifier' with an air quality sensor. I don't see Air Purifier listed as a device type in the HA Homekit core integration, but I know it's a support device type in Home.app. Is there a way to do this manually?
As far as the air quality sensor part goes, it looks like the Homebridge dev assigned arbitrary values to the Winix's 'good, etc.' values. It looks really nice having this sensor in Home.app, though, and I was wondering if this could be added as well?
Thanks for all your hard work!

The integration has a Device entry if the integration was added via Config Flow which doesn't happen to be the case for Winix, so all one gets are Entities. As far as I know, the Device cannot be manually created.

Understood. Thanks.

I just pushed out a new breaking release which supports config flow and should help with your setup.


404 https://oauth2-proxy.github.io/manifests

Hi,
I am getting a 404 status code when trying to access https://oauth2-proxy.github.io/manifests. Is it temporary?

I am getting this too. Seems like it is related to :
https://github.com/oauth2-proxy/manifests/actions/runs/11794657444/job/32852738030

it seems that the gh-pages branch is deleted therefore the registry is not available anymore

I tried to reenable it, but I don't know if this is the expected result. 😢

@erkannt @JoelSpeed, could you please take a look?

This repository works: oci://ghcr.io/oauth2-proxy/charts

Error: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Aoauth2-proxy%2Fcharts%3Apull&service=ghcr.io: 403 Forbidden]
But it does not seem public?

Using oci://ghcr.io/oauth2-proxy/charts as a workaround does not for me using the latest available Helm (v3.16.2):
Error: looks like "oci://ghcr.io/oauth2-proxy/charts" is not a valid chart repository or cannot be reached: object required

Theres a bug in the updated README.md file: https://github.com/oauth2-proxy/manifests/actions/runs/11795337858/job/32854843699#step:4:13
     Liquid Warning: Liquid syntax error (line 296): [:dot, "."] is not a valid expression in "{{ .Values.tplValue }}" in helm/oauth2-proxy/README.md
    Liquid Warning: Liquid syntax error (line 334): [:dot, "."] is not a valid expression in "{{.StatusCode}}" in helm/oauth2-proxy/README.md```

The pipeline should have probably failed.

I am having same issue.

The OCI registry works just fine
helm template oauth2proxy-test oci://ghcr.io/oauth2-proxy/charts/oauth2-proxy --version 7.7.29

The OCI registry works just fine
helm template oauth2proxy-test oci://ghcr.io/oauth2-proxy/charts/oauth2-proxy --version 7.7.29

This won't necessarily work for everyone, people using older versions of helm in their pipelines/tools may have issues querying for OCI tags.

I'm looking into now.

Issue has been resolved!