Update weaver-cats, weaver-scalacheck to 0.7.6

Updates

com.disneystreaming:weaver-cats
com.disneystreaming:weaver-scalacheck

from 0.7.4 to 0.7.6.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.disneystreaming" } ]

labels: library-update, semver-patch

Codecov Report

Merging #82 (43d4d50) into master (2f64d9b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #82   +/-   ##
=======================================
  Coverage   85.71%   85.71%
=======================================
  Files           2        2
  Lines           7        7
=======================================
  Hits            6        6
  Misses          1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 107565d...43d4d50. Read the comment docs.


cannot load state data from Alarm.com

Is the issue below normal? My alarm still operates via my automations but curious if I'm missing something that needs to be configured to remove the error.
WARNING (MainThread) [homeassistant.helpers.entity] Update of alarm_control_panel.alarm_com is taking over 10 seconds
ERROR (MainThread) [pyalarmdotcomajax.pyalarmdotcomajax] Can not load state data from Alarm.com

Oddly I saw the same error yesterday evening, after which I was unable to set the alarm state.
Restarting HA restored the ability to set the alarm state, however I'm seeing this in the log:
Logger: pyalarmdotcomajax.pyalarmdotcomajax
Source: /usr/local/lib/python3.8/site-packages/pyalarmdotcomajax/pyalarmdotcomajax.py:135
First occurred: 8:31:54 AM (295 occurrences)
Last logged: 10:59:24 AM
Unable to extract system id from Alarm.com
===========
Logger: pyalarmdotcomajax.pyalarmdotcomajax
Source: /usr/local/lib/python3.8/site-packages/pyalarmdotcomajax/pyalarmdotcomajax.py:181
First occurred: 1:41:56 AM (296 occurrences)
Last logged: 10:59:24 AM
Unable to extract state data from Alarm.com
===========
Update for alarm_control_panel.alarm_com fails
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pyalarmdotcomajax/pyalarmdotcomajax.py", line 166, in async_update
self.sensor_status = json["data"]["attributes"]["needsClearIssuesPrompt"]
KeyError: 'data'
===========
I haven't debugged it yet, but I updated the plugin to the latest and HA to 5.13 a few days ago. I suspect one of those maybe the culprit.

@SkyHyperV this is the same as what was asked in #35. It's quite normal to see this message a handful of times a day, but any more than that and I would look into connectivity problems on your HA machine.
@aechelon have you enabled 2fa and updated your config with the cookie? Just yesterday my portal finally prompted me to use 2fa. Only clicking skip would probably result in errors like what you are seeing.

@uvjustin, thanks for the heads up.  Although the Brinks site has a 2FA setup option, it hasn't prompted with the nag screen yet.
Would you recommend setting it up even if it's not prompting for it?

@aechelon I would just go ahead and do it since it only takes a minute or two and it seems like eventually all the portals will nag for 2fa.

@uvjustin yep, that was it, thanks!

@aechelon Should we add some kind of notice/troubleshooting section to tell users to try 2FA if they encounter errors?
Regarding the "Can not load state data" message, I will probably lower the log level to Warning or even Debug. I think most people will have the occasional connection error from time to time and Error messages seem to freak people out. Any thoughts on that?


enable/disable no longer possible after update to 2024.6.1

Alarmo Version
v1.10.0
HA Version
2024.6.1
Bug description
After updating to 2024.6.1 its no longer possible to enable or disable the alarm.
Not via a control panel in the browser gui or android app and also not via sonoff nspanel (esphome).
If you need further information, let me know.
Thanks a lot!
Steps to reproduce
Try to enable or disable the alarm.
The attached error message is shown.

Relevant log output
2024-06-10 08:24:29.910 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dwd_pollenflug which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.913 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration stadtreinigung_hamburg which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.916 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.919 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pfsense_gateways which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.922 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dreame_vacuum which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.923 ERROR (SyncWorker_0) [homeassistant.loader] Version v1.0.3 of custom integration 'dreame_vacuum' crashes Home Assistant and was blocked from loading, please create a bug report at https://github.com/Tasshack/dreame-vacuum/issues
2024-06-10 08:24:29.934 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration zha_toolkit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.938 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration skodaconnect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.942 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration easee which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.945 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration homematicip_local which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.949 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alarmo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.952 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xiaomi_miio_airpurifier which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:24:29.957 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration deutschebahn which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-10 08:25:14.882 ERROR (MainThread) [homeassistant.helpers.translation] Validation of translation placeholders for localized (de) string component.easee.device_automation.condition_type.error_pen_fault failed: (set() != {'entity_name'})
2024-06-10 08:25:14.883 ERROR (MainThread) [homeassistant.helpers.translation] Validation of translation placeholders for localized (de) string component.easee.device_automation.trigger_type.error_pen_fault failed: (set() != {'entity_name'})
2024-06-10 08:25:16.652 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2024-06-10 08:25:30.076 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds.
2024-06-10 08:25:30.225 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /os/info request
2024-06-10 08:25:30.228 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /network/info request
2024-06-10 08:25:30.228 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /core/info request
2024-06-10 08:25:30.229 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /resolution/info request
2024-06-10 08:25:30.229 ERROR (MainThread) [homeassistant.components.hassio.issues] Failed to update supervisor issues: HassioAPIError()
2024-06-10 08:25:30.233 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /host/info request
2024-06-10 08:25:30.233 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /info request
2024-06-10 08:25:30.234 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/options request
2024-06-10 08:25:30.235 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /store request
2024-06-10 08:25:30.236 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/info request
2024-06-10 08:25:30.244 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /ingress/panels request
2024-06-10 08:25:30.244 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can't read panel info:
2024-06-10 08:25:30.249 WARNING (MainThread) [homeassistant.components.hassio] Can't read Supervisor data:
2024-06-10 08:25:36.547 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for update.home_assistant_supervisor_update (<class 'homeassistant.components.hassio.update.SupervisorSupervisorUpdateEntity'>) took 1.435 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+hassio%22
2024-06-10 08:25:37.486 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('hassio', 'a3e77c30516f7499dfa6869bad86d581'): 1470.026980743}
2024-06-10 08:27:02.816 WARNING (MainThread) [homeassistant.setup] Setup of stream is taking over 10 seconds.
2024-06-10 08:27:29.284 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('mqtt', '5d1faff9180f26ad3d968dda980e09a2'): 1582.052099341, ('shopping_list', 'ec8de7b5d388812b679fea3656f4b600'): 1582.053114308, ('dwd_pollenflug', '1c8ff16c83d2dce09e8cdcec21a7daec'): 1582.129156708, ('co2signal', 'f649a9fb75e8e1e14f479c6813af10f7'): 1582.321420592, ('hue', 'f25d5ad6e645b799c2a63a56219d096f'): 1583.803073117, ('dlna_dmr', 'd54973172d30ed4e75b94c08b9ec98cc'): 1584.064204338, ('androidtv_remote', '366564a279ddfc6512b35759d8617bd2'): 1586.607967957}
2024-06-10 08:27:57.060 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-06-10 08:28:32.622 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('mqtt', '5d1faff9180f26ad3d968dda980e09a2'): 1582.052099341, ('shopping_list', 'ec8de7b5d388812b679fea3656f4b600'): 1582.053114308, ('dwd_pollenflug', '1c8ff16c83d2dce09e8cdcec21a7daec'): 1582.129156708, ('co2signal', 'f649a9fb75e8e1e14f479c6813af10f7'): 1582.321420592, ('hue', 'f25d5ad6e645b799c2a63a56219d096f'): 1583.803073117, ('dlna_dmr', 'd54973172d30ed4e75b94c08b9ec98cc'): 1584.064204338, ('androidtv_remote', '366564a279ddfc6512b35759d8617bd2'): 1586.607967957, ('denonavr', 'c491be0f63a45821bd8f38f3dfd5fe49'): 1592.83399082, ('met', '1ab59c748c69365c2e07bf56e2ecf8a6'): 1593.094399646, ('google_translate', 'df89738250bb9c08d7f353e4fe86b7c9'): 1593.151610712, ('webostv', 'bbcdf2b448008f6a0a2b8402dc97af85'): 1600.67386404, ('hacs', '3e22301cabb6727e8cf997f7492f0799'): 1615.290084438, ('xiaomi_miio', 'd7c37c8be987878aa82faf67224c954b'): 1634.99798039, ('xiaomi_miio', '4ad8a616b69a7391e24ab2736bc872a4'): 1634.998846451, ('frontier_silicon', 'ab079f90000008827031d2f474d5b93c'): 1635.332240721, ('brother', 'b9ef06fb52e6a7b255de9dc7f21937d0'): 1643.177558913}
2024-06-10 08:29:05.531 WARNING (SyncWorker_0) [homeassistant.components.homematic.sensor] Sensor (Sirene ARMSTATE) entity description is missing. Sensor state (ARMSTATE) needs to be maintained
2024-06-10 08:29:05.532 WARNING (SyncWorker_0) [homeassistant.components.homematic.sensor] Sensor (Sirene Keller ARMSTATE) entity description is missing. Sensor state (ARMSTATE) needs to be maintained
2024-06-10 08:29:15.483 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform homematic is taking over 10 seconds.
2024-06-10 08:29:15.516 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform homematic is taking over 10 seconds.
2024-06-10 08:29:23.154 WARNING (SyncWorker_9) [homeassistant.helpers.frame] Detected that custom integration 'alarmo' calls `async_track_state_change` instead of `async_track_state_change_event` which is deprecated and will be removed in Home Assistant 2025.5 at custom_components/alarmo/sensors.py, line 175: self._state_listener = async_track_state_change(, please report it to the author of the 'alarmo' custom integration
2024-06-10 08:29:23.860 ERROR (SyncWorker_1) [homeassistant.util.logging] Exception in async_watch_sensor_states when dispatching 'alarmo_state_updated': (None, None, 'disarmed')
Traceback (most recent call last):
  File "/config/custom_components/alarmo/sensors.py", line 172, in async_watch_sensor_states
    self._state_listener()
  File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 390, in _remove_listener
    callbacks[key].remove(job)
ValueError: list.remove(x): x not in list

2024-06-10 08:31:51.674 WARNING (ImportExecutor_0) [homeassistant.const] DEVICE_CLASS_TIMESTAMP was used from stadtreinigung_hamburg, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.TIMESTAMP instead, please report it to the author of the 'stadtreinigung_hamburg' custom integration
2024-06-10 08:32:43.072 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from deutschebahn, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'deutschebahn' custom integration
2024-06-10 08:32:44.605 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
2024-06-10 09:34:56.610 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140620879064816] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 959, in entity_service_call
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity alarm_control_panel.erdgeschoss does not support this service.
2024-06-10 09:35:27.135 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140620879064816] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 959, in entity_service_call
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity alarm_control_panel.erdgeschoss does not support this service.
2024-06-10 09:36:01.101 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140620879064816] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 959, in entity_service_call
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity alarm_control_panel.erdgeschoss does not support this service.

You should call the service "alarmo.disarm" from now on and not alarm_control_panel.alarm_disarm

Hi Omrizn,
thanks for getting back on this!
How can I do this?
The control panel currently has this code for example:
states:
  - arm_away
type: alarm-panel
entity: alarm_control_panel.erdgeschoss

Also, if I have a look on my entities, they are still called like before
Dachgeschoss  alarm_control_panel.dachgeschoss
Erdgeschoss     alarm_control_panel.erdgeschoss
Keller                 alarm_control_panel.keller
Haus                  alarm_control_panel.haus

So what do I have to change to use alarmo.disarm on my different zones?
Also, was this change in the release notes and I've overseen it?
Thank you again and cheers

Please share a screenshot of the mode settings for the ‘erdgeschoss’ area in alarmo and a screenshot of the properties of the corresponding alarm_control_panel entity in the Developer Tools - states panel.

Same problem here :
"No se pudo llamar al servicio alarm_control_panel/alarm_disarm. AlarmoBaseEntity.async_alarm_disarm() takes 1 positional argument but 2 were given"

Hi Nils,
also thanks to you for supporting me here. Hopefully this is what you are looking for?

Hi Nils,
I've put this to disabled this morning as I was not able to deactivate the alarm. I was hoping this would help and forgot to enable this again.
But even when I have this on enabled again, I still have trouble with disabling the alarm.
See my screenshot and the attached log.

2024-06-10 14:47:05.100 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140620861735120] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 959, in entity_service_call
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity alarm_control_panel.dachgeschoss does not support this service.
2024-06-10 14:48:26.727 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140620861735120] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/alarm_control_panel/__init__.py", line 207, in async_handle_alarm_disarm
    await self.async_alarm_disarm(self.code_or_default_code(code))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: AlarmoBaseEntity.async_alarm_disarm() takes 1 positional argument but 2 were given
2024-06-10 14:48:41.528 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140620861735120] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/alarm_control_panel/__init__.py", line 207, in async_handle_alarm_disarm
    await self.async_alarm_disarm(self.code_or_default_code(code))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: AlarmoBaseEntity.async_alarm_disarm() takes 1 positional argument but 2 were given
2024-06-10 14:51:39.889 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140620861735120] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/alarm_control_panel/__init__.py", line 207, in async_handle_alarm_disarm
    await self.async_alarm_disarm(self.code_or_default_code(code))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: AlarmoBaseEntity.async_alarm_disarm() takes 1 positional argument but 2 were given

@TheChosenOne1984 you can fix that issue yourself by updating alarmo. I don’t spend time on bug issues from users who use outdated versions.

@nielsfaber ,
sorry for the noise. I'm still new to the game and I forgot to look for available updates in HACS. I only checked in HA settings.
In fact, you supported me, and I'm really thankful you did.
So, sorry again and thank you!


Incorporate semi-discrete investment sizes

In the report (2019-05-i2cner-report.pdf)
2019-05-i2cner-report.pdf some discussion is had about errors that are introduced due t odiscrete installed capacity installation/investment sizes for generation.
All DSCINV files must include semi-discrete installed capacity installation sizes for consistency.

Unnecessary in current models.


Can not format textField of type date in the form 'DD/MM/YYYY'

Can not format textField of type date in the form 'DD/MM/YYYY'. The options for type are limited. Why not have a format field

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
TextField should have a format prop that will help format date in any format. eg.
<TextField
                onChange={onDateChange}
                id="date"
                label="Date Received"
                type="date"
                format={'DD/MM/YYYY'}
                value={dateRecieved}
                className={classes.textField}
                margin="normal"
                InputLabelProps={{
                  shrink: true
                }}
/>

Current Behavior
Currently the type options doesn't allow to format in DD/MM/YYYY form.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.32

React
3.7.2

browser
chrome

etc

Don't miss the notice note on the documentation page section: https://material-ui-next.com/demos/pickers/. The format is implemented by the native <input> element. The issue isn't on our end. Also, consider the documented alternative third-party libraries.

So one strange thing I noticed related to this is that I was seeing the same issue, where dates were formatted MM/DD/YYYY and since I'm in an international environment, that just won't do. However, when I went to the 'pickers' page that @oliviertassinari linked above, everything was in YYYY-MM-DD. So I deleted everything in my node_modules directory and reinstalled and now everything is in YYYY-MM-DD.
The only thing I can think of is that I upgraded from the old material-ui into the beta?

Its strange.. it takes the local machine's date time format.

Its strange.. it takes the local machine's date time format.

Any Solution for this?

@yuvraj88 You have two options:

Use @material-ui/pickers
Use a custom inputComponent implementation. It would probably only work well on mobile

https://codesandbox.io/s/zq89ym8v74
import React from "react";
import { makeStyles } from "@material-ui/core/styles";
import TextField from "@material-ui/core/TextField";

const useStyles = makeStyles(theme => ({
  root: {
    position: "relative"
  },
  display: {
    position: "absolute",
    top: 2,
    left: 0,
    bottom: 2,
    background: "white",
    pointerEvents: "none",
    right: 50,
    display: "flex",
    alignItems: "center"
  },
  input: {}
}));

function InputComponent({ defaultValue, inputRef, ...props }: any) {
  const classes = useStyles();
  const [value, setValue] = React.useState(() => props.value || defaultValue);

  const handleChange = event => {
    setValue(event.target.value);
    if (props.onChange) {
      props.onChange(event);
    }
  };

  return (

{value}

      <input
        className={classes.input}
        ref={inputRef}
        {...props}
        onChange={handleChange}
        value={value}
      />

  );
}

function DatePickers() {
  return (
    <TextField
      id="date"
      label="Birthday"
      type="date"
      InputProps={{
        inputComponent: InputComponent
      }}
      defaultValue="2017-05-24"
      InputLabelProps={{
        shrink: true
      }}
    />
  );
}

export default DatePickers;

<DateTimePicker
 label="Date Time
 value="2020-03-31T18:30:00.000Z"
 format="yyyy-MM-dd HH:mm:ss"
 onChange={(date:Date|null)=>form.setFieldValue(props.name,String(date))}
 />

Actually i am using the datetime picker in formik i want the output format as yyyy-MM-dd HH:mm:ss but it is coming like Wed Apr 22 2020 00:00:00 GMT+0530 (India Standard Time) and also it doesn't support UTC time.can you anyone help?

FWIW, if you're having trouble formatting a plain old date to the material date input. Try...
date.toISOString().substring(0,10);

@karthikjagadeeswaran You can use a library-like moment to convert to your required format in onChange.
onChange={(newValue) => {             setDateOfBirth(moment(newValue).format(INPUT_YOUR_FORMAT));           }}


Implement Reflect for Box

Objective
Closes #3392
Solution
Used code snippet from @Davier and made a few changes on DynamicList for the type checker to work.

Awesome, thank you. This is a nice addition, and your test looks nice :)

@cart do your concerns from #2505 apply here?

Yup "boxing boxes" is definitely a concern here, although the scope of the problem is different because in core bevy apis we aren't implicitly boxing T: Reflect parameters that might later be retrieved and passed back in (at least to my knowledge).
However Box<dyn Reflect> is used/returned in a number of places (Reflect::clone_value(), scenes, etc), so this feels risky to me.
Thaaaat being said, having reflection work for "everything", including Boxed reflect types, does seem like it could be valuable. Can we outline specific "real world" scenarios that need this (that can't be resolved in other ways?). So far I've only seen that a user wants to do this, which isn't enough context to evaluate the need here.

Note that any impl Trait for Box<dyn Trait> opens the door to double-boxing (nested boxing) and especially to silently doing so by mistake. Coincidentally we're hitting this in 🍃Bevy Tweening with djeedai/bevy_tweening#27. See discussion highlighting a few important points:

even rustlang/futures-rs struggles with this, it's a hard issue, that trait specialization will solve once it's stable, but until then is hard to fix.
you don't need to not have that impl in the current crate for the problem to be avoided with any public trait, because any crate could add that impl for you, and your back to square one.
incidentally 2. makes it harder to work around double boxing.
there's some runtime workaround via Any::try_downcast() that was suggested to me on the Rust Discord, but it's a runtime check not a build time guarantee.

Given all of that I think it's reasonable to still add the impl, and thoroughly document places where nested boxing might occur by mistake. And consider adding that runtime check as a guard.

Here's the runtime workaround : https://discord.com/channels/442252698964721669/443150878111694848/981137955773095936 (I didn't try it yet)

Use this function:

fn try_downcast<T, K>(k: K) -> Result<T, K>
where
    T: 'static,
    K: 'static,
{
    let mut k = Some(k);
    if let Some(k) = <dyn std::any::Any>::downcast_mut::<Option<T>>(&mut k) {
        Ok(k.take().unwrap())
    } else {
        Err(k.unwrap())
    }
}

like so:

fn box_trait<T: 'static + Trait>(val: T) -> Box<dyn Trait> {
    try_downcast::<Box<dyn Trait>, _>(val)
        .unwrap_or_else(|val| Box::new(val))
}

as a real-world example; working on my editor I've stumbled across this. I want to send messages over network between the editor and the game client, and those messages are serialized into yaml (could be anything, picked arbitrarily) via reflection. In order to send reflected types, I sometimes need to send a Box (serialized components), but it's not Reflect so I ended up implementing a ReflectObject newtype around it.

Adding the S-Adopt-Me tag.
@franciscoaguirre let us know if you'd rather continue working on this yourself and I'll remove it! :)

@MrGVSV Yeah I can work on this. There was so much debate that I got lost :joy: and I wasn't having much time. I have more time now so I can get it done

@franciscoaguirre Are you still intending to work on this?

@rdrpenguin04 I've been heavily caught in finishing university. Now that I'll soon graduate I'll have time for open source and I'd love to contribute to Bevy. That said, I can only work on it in January, since the holidays are coming up. I've seen people requesting this PR to be merged so if you need it before holidays I don't mind you taking the torch. If not, I can work on it in January :)

@rdrpenguin04 I got around to rebasing and updating the code with the latest on main :smile:
@PROMETHIA-27 Is this PR okay now with your change to the Reflect trait?
@alice-i-cecile Is this issue still relevant?

@franciscoaguirre FYI you have at least one test panicking, looks like it's directly related to your change.

Yep, fixed it.
The thing is, I was implementing DynamicTypePath on Box<dyn Reflect> which lets me use self to forward the call to the inner value, but I needed to implement TypePath for the type and having both implementations resulted in conflicts.
I think it's more useful to get the type of the inner value, maybe not? Is there a way I can accomplish that?

I have no idea, I don't have enough domain knowledge to answer whether we should implement the dynamic version or not. My gut feeling is that TypePath would be more useful, but I really don't have a backing argument sorry. Maybe @alice-i-cecile or @MrGVSV can help here?

Maintainers: What are we doing with this PR? It's been S-Ready-For-Final-Review for a while now

Deferring to the Reflection SMEs. I'll bring it up on Discord.

Maintainers: What are we doing with this PR? It's been S-Ready-For-Final-Review for a while now

Sorry to everyone that's been waiting on this :/
I'm currently looking into a possible alternative approach that aims to avoid the double-boxing issue by going through remote reflection. However, if that doesn't work out or it runs into the same problems, then we'll probably move forward with this PR.
I'll keep experimenting and return with details soon!
Either way, I'd like to get something in for Box<dyn Reflect> and Box<dyn PartialReflect> for 0.15.

I've just pushed #14776 if anyone wants to give it a look!
The TL;DR is that we can avoid the risk of double-boxing by adding a separate ReflectBox type (that users can't construct—otherwise we'd have the same problem) and using remote reflection to reflect it:
use bevy_reflect::boxed::ReflectBox;

#[derive(Reflect)]
#[reflect(from_reflect = false)]
struct Player {
    #[reflect(remote = ReflectBox<dyn Reflect>)]
    weapon: Box<dyn Reflect>,
}

The main consideration is that this ReflectBox approach comes with many limitations. Some are the same as this PR (i.e. doesn't work with FromReflect, can't be used in enums), but some are unique to remote reflection (i.e. difficulty using ReflectBox as a type parameter).
So the question becomes, do we go for the more flexible PR (this one) or the more conservative PR (#14776)?
I'm leaning towards starting out conservative to see how far that can take us. We can then revisit this PR in the future if necessary.
However, I'm more than happy to hear alternative perspectives or even other ideas!

Also, I wanted to point out that another cool benefit to ReflectBox is its ability to work with any type T that can be converted to a dyn PartialReflect (using a couple traits). This includes other trait objects like dyn MyCoolTrait.
If we do end up going with this PR, it might be worthwhile trying to get that behavior to work as well (possibly using a similar approach as ReflectBox). Either in this PR or a followup one.

Closing in favor of #14776.


Compute S^z and S^2

Summary
After multiple fixes in Qiskit Nature, this PR now also adds support for computing S^z and S^2 in the PySCFGroundStateSolver.
Details and comments
Supporting the correct AngularMomentum with taking the alpha-beta overlap into account during the QiskitSolver is currently not possible because of the API workflow. In other words: the kernel method is not provided the information from which we can reconstruct this overlap matrix during the construction of the AngularMomentum property.
We also cannot really compute it up-front and inject it into the QiskitSolver as an attribute, because this would require a-priori knowledge of the active MOs (which we do not have at that point).
This will need to be sorted together with the PySCF team, once I have raised the problem discussed here to them, since this affects their UCASCI and UCASSCF methods, too.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

26 of 26 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.6%) to 80.571%

Totals

Change from base Build<PHONE_NUMBER>:
2.6%

Covered Lines:
141

Relevant Lines:
175

💛  - Coveralls


Can't connect to Kafka, kafkacat works

Hi.
Using the code
const kafka = require('kafka-node')
const Consumer = kafka.Consumer

const client = new kafka.Client('<IP_ADDRESS>:9092')

const consumer = new Consumer(
  client,
  [
    { topic: 'test', partition: 0 },
  ]
)

consumer.on('message', (message) => {
  console.log(`MESSAGE: ${message}`)
})

I can't seem to connect to the running Kafka service.
When I run kafkacat -b <IP_ADDRESS>:9092 -t test -C on the commandline it works. I get 5 test messages (that I put in using -P)

You need to pass in the zookeeper host instead.
Sent from my iPhone

On Feb 19, 2017, at 4:45 PM, Tom Wieland<EMAIL_ADDRESS>wrote:
Hi.
Using the code
const kafka = require('kafka-node')
const Consumer = kafka.Consumer
const client = new kafka.Client('<IP_ADDRESS>:9092')
const consumer = new Consumer(
client,
[
{ topic: 'test', partition: 0 },
]
)
consumer.on('message', (message) => {
console.log(MESSAGE: ${message})
})
I can't seem to connect to the running Kafka service.
When I run kafkacat -b <IP_ADDRESS>:9092 -t test -C on the commandline it works. I get 5 test messages (that I put in using -P)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Okay
I've tried <IP_ADDRESS>:2181, <IP_ADDRESS>:2181, <IP_ADDRESS>:2181 (hostname -i)
All with the same results.


Fix typo

Fix typo
coloour -> colour

As noted in the comment in this function, this bit of code is auto-generated. In future please open an issue or email me to add any tips or make any suggestions so I can ensure it's updated at the source properly.
For this time since it's a small change, I've made it myself and I'll accept this PR directly.

I used 'git grep -n coloour' to find the code of this typo line and only one line was found. I guess that the source of the auto-generated code is not in the repository.

Yes it's stored outside this repository to allow the tips to stay in sync between the web version and the code.


Correct definition, alt terms for OBI_0000650 differential expression analysis data transformation

Correct defintion
FROM:
A differential expression analysis data transformation is a data transformation that has objective differential expression analysis and that consists of
TO:
A  differential expression analysis data transformation is a data  transformation that has objective of differential expression analysis,

@DanBerrios Can you propose a better definition for the term? Thanks

A differential expression analysis data transformation is a data transformation that has an objective of achieving a differential expression analysis (determining which biological entities or set of entities are
likely to have different expression of which genes across one or more conditions).  Typically this involves combining or summarizing gene expression values within entity subgroups and comparing them using statistics.

I think this can be closed, no?


redirectUrl not working correctly

Hi
I have a heroku app setup at https://steamlevels.herokuapp.com/ and have the custom domain http://www.steamlevels.com/ setup for the app.
The user can use the site fully at http://www.steamlevels.com/, however when they login, they are redirected back to https://steamlevels.herokuapp.com/ (http://i.imgur.com/WmfjxZN.png) even with the 'redirectUrl' enabled. When i created a new app to test this, redirectUrl did not work either.
Meteor.loginWithSteam({                redirectUrl: 'http://steamlevels.com/'           });
Any help would be greatly appreciated

I see you closed this without additional comment. Is this still an issue?

Nope - just a case of setting heroku's root url. My bad

In this case, the redirect URL wouldn't have helped anyway.


Persist begun transactions in db

from time to time persist (mark persisted in local cache, sync on change or mark invalid locally to be synced again next iteration)
On application start load persisted states from db
Do final sync on SIGTERM and SIGKILL: https://gist.github.com/uudashr/3cf820e3ba902d3c6387abc82c815e66

Dockerfile: depend bot service on db to help Docker in ordering app restarts

reduce cache time, store and retrieve from db instead


Fix: Split wide pages

Fixes  #479
Apache Commons Compress archives do not support mark and reset, this causes problems when functions like "Split wide pages" are used, that rely on these functions working. More info in  #479.
I fixed it by loading the images into a ByteArray instead of reading them directly from file.
Someone should test the performance in Long strip mode before merging this PR, because my emulator is too laggy too tell whether or not this approach degrades reader performance.

what if we turn it into a BufferedInputStream

what if we turn it into a BufferedInputStream

If you mean using something like BufferedInputStream() or .buffered(), that does not work, is there another way to turn an InputStream into a BufferedInputStream?

A BufferedInputStream adds functionality to another input stream-namely, the ability to buffer the input and to support the mark and reset methods.

Excert from https://developer.android.com/reference/java/io/BufferedInputStream
You can do BufferedInputStream(existingInputStream) to make a new one

Y

A BufferedInputStream adds functionality to another input stream-namely, the ability to buffer the input and to support the mark and reset methods.

Excert from https://developer.android.com/reference/java/io/BufferedInputStream
You can do BufferedInputStream(existingInputStream) to make a new one

Yes but that will still consume the backing InputStream:
So the Buffer size needs to be set to a value that is always larger then the file you are reading.
Tested it with:
BufferedInputStream(zip.getInputStream(entry), 8192) -> does not load
BufferedInputStream(zip.getInputStream(entry), 9000000) -> does load

Closed in favor of #485


ARROW-5930: [FlightRPC][Python] Disable Flight test causing segfault in Travis

Looks like all Flight TLS tests are flaky in Python, I will continue investigating - so far I can't reproduce this locally (using a Xenial VM).

Rebased (sorry, this slipped off my radar)

Thanks @lihalite -- let's merge this but leave the JIRA open until this can be fixed

I've managed to reproduce it once within docker:
$ docker-compose build cpp
$ docker-compose build python
$ docker-compose run python bash
# /arrow/ci/docker_build_and_test_python.sh

diff --git a/ci/docker_build_python.sh b/ci/docker_build_python.sh
index 98be2b401..0b7d4a960 100755
--- a/ci/docker_build_python.sh
+++ b/ci/docker_build_python.sh
@@ -21,6 +21,9 @@ set -e
 source_dir=${1:-/arrow/python}
 build_dir=${2:-/build/python}

+export ARROW_TEST_DATA=/arrow/testing/data
+export PARQUET_TEST_DATA=/arrow/cpp/submodules/parquet-testing/data
+
 export PYARROW_CXXFLAGS=$CXXFLAGS
 export PYARROW_CMAKE_GENERATOR=Ninja
 export PYARROW_BUILD_TYPE=${PYARROW_BUILD_TYPE:-debug}
@@ -30,6 +33,7 @@ export SETUPTOOLS_SCM_VERSION_WRITE_TO_PREFIX=$build_dir
 export PYARROW_WITH_ORC=${PYARROW_WITH_ORC:-1}
 export PYARROW_WITH_PARQUET=${PYARROW_WITH_PARQUET:-1}
 export PYARROW_WITH_PLASMA=${PYARROW_WITH_PLASMA:-1}
+export PYARROW_WITH_FLIGHT=${PYARROW_WITH_FLIGHT:-1}

 # Build pyarrow
 pushd ${source_dir}

But it seems flaky, the error has only occurred once out of multiple reruns of the flight tests:
pytest -r s -v -m "flight" --pyargs pyarrow

@kszucs thanks for the instructions, I'll give it a try when I get a chance. I guess there's some race in tearing down the Flight server.


Wallet: "Pick an asset" for send to external account causes error

List of available assets only includes XLM when there should be more available.
Error: ERROR CODE 218 - base32 decode failed: illegal base32 data at input byte 0 in method stellar.1.local.getTrustlinesLocal at new s
my log id: e4d7b2cca4702fa07fc85d1c

Nice


Data source[Doc][Module Name] Documentation bug or improvement

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
dolphinscheduler连接doris数据源时，需要的数据源插件是什么，怎么在dolphinscheduler中使用，为什么直接在可视化界面配置报错。
Documentation Links
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

hi @chineseliu32  Please provide error information


[soci] build failure: vcpkg install soci[postgresql]. Shared libraries not built

Host Environment

OS:  Linux (wsl2) (Ubuntu 20-04)
Compiler: clang version 15.0.0

# clang --version
Ubuntu clang version 15.0.0-++20220214053039+00cd6c04202a-1~exp1~20220214173130.159
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

To Reproduce
Steps to reproduce the behavior:
./vcpkg install soci[postgresql]
Failure logs
The build successfully ends but it doesn't build any shared libraries.
# ./vcpkg install soci\[postgresql\]
Computing installation plan...
A suitable version of cmake was not found (required v3.21.1). Downloading portable cmake v3.21.1...
Downloading cmake...
  https://github.com/Kitware/CMake/releases/download/v3.21.1/cmake-3.21.1-Linux-x86_64.tar.gz -> /home/hanejun/samples/packages/vcpkg/downloads/cmake-3.21.1-linux-x86_64.tar.gz
Extracting cmake...
The following packages will be built and installed:
  * libpq[core,openssl,zlib]:x64-linux -> 12.9#1
  * openssl[core]:x64-linux -> 1.1.1m#2
    soci[core,postgresql]:x64-linux -> 4.0.2
  * vcpkg-cmake[core]:x64-linux -> 2022-01-19
  * vcpkg-cmake-config[core]:x64-linux -> 2022-02-06
  * zlib[core]:x64-linux -> 1.2.11#13
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-linux...
A suitable version of ninja was not found (required v1.10.2). Downloading portable ninja v1.10.2...
Downloading ninja...
  https://github.com/ninja-build/ninja/releases/download/v1.10.2/ninja-linux.zip -> /home/hanejun/samples/packages/vcpkg/downloads/ninja-linux-1.10.2.zip
Extracting ninja...
Restored 2 packages from /home/hanejun/.cache/vcpkg/archives in 10.82 ms. Use --debug to see more details.
Starting package 1/6: vcpkg-cmake:x64-linux
Installing package vcpkg-cmake[core]:x64-linux...
Elapsed time for package vcpkg-cmake:x64-linux: 1.075 ms
Starting package 2/6: vcpkg-cmake-config:x64-linux
Building package vcpkg-cmake-config[core]:x64-linux...
-- Installing: /home/hanejun/samples/packages/vcpkg/packages/vcpkg-cmake-config_x64-linux/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake
-- Installing: /home/hanejun/samples/packages/vcpkg/packages/vcpkg-cmake-config_x64-linux/share/vcpkg-cmake-config/vcpkg-port-config.cmake
-- Installing: /home/hanejun/samples/packages/vcpkg/packages/vcpkg-cmake-config_x64-linux/share/vcpkg-cmake-config/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /home/hanejun/.cache/vcpkg/archives/ec/ec70fe4d6a9b9c514c1a0dd4bf87f0b25c3e3980e52a665c198424a5b4ca28ec.zip
Installing package vcpkg-cmake-config[core]:x64-linux...
Elapsed time for package vcpkg-cmake-config:x64-linux: 23.04 ms
Starting package 3/6: openssl:x64-linux
Building package openssl[core]:x64-linux...
-- Downloading https://www.openssl.org/source/openssl-1.1.1m.tar.gz;https://www.openssl.org/source/old/1.1.1/openssl-1.1.1m.tar.gz -> openssl-1.1.1m.tar.gz...

Elapsed time for package openssl:x64-linux: 2.403 min
Starting package 4/6: zlib:x64-linux
Installing package zlib[core]:x64-linux...
Elapsed time for package zlib:x64-linux: 3.269 ms
Starting package 5/6: libpq:x64-linux
Building package libpq[core,openssl,zlib]:x64-linux...
-- Downloading https://ftp.postgresql.org/pub/source/v12.9/postgresql-12.9.tar.bz2 -> postgresql-12.9.tar.bz2...
-- Extracting source /home/hanejun/samples/packages/vcpkg/downloads/postgresql-12.9.tar.bz2
-- Applying patch patches/windows/install.patch
-- Applying patch patches/windows/win_bison_flex.patch
-- Applying patch patches/windows/openssl_exe_path.patch
-- Applying patch patches/windows/Solution.patch
-- Applying patch patches/windows/MSBuildProject_fix_gendef_perl.patch
-- Applying patch patches/windows/msgfmt.patch
-- Applying patch patches/windows/python_lib.patch
-- Applying patch patches/windows/fix-compile-flag-Zi.patch
-- Applying patch patches/linux/configure.patch
-- Applying patch patches/windows/MSBuildProject-static-lib.patch
-- Applying patch patches/windows/Mkvcbuild-static-lib.patch
-- Applying patch patches/windows/minimize_install.patch
-- Using source at /home/hanejun/samples/packages/vcpkg/buildtrees/libpq/src/tgresql-12-5e12ab542a.clean
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Installing x64-linux-dbg
-- Building x64-linux-rel
-- Installing x64-linux-rel
-- Installing: /home/hanejun/samples/packages/vcpkg/packages/libpq_x64-linux/share/libpq/usage
-- Installing: /home/hanejun/samples/packages/vcpkg/packages/libpq_x64-linux/share/libpq/copyright
-- Fixing pkgconfig file: /home/hanejun/samples/packages/vcpkg/packages/libpq_x64-linux/lib/pkgconfig/libpq.pc
-- Fixing pkgconfig file: /home/hanejun/samples/packages/vcpkg/packages/libpq_x64-linux/debug/lib/pkgconfig/libpq.pc
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /home/hanejun/.cache/vcpkg/archives/6e/6eca618a5d308919ae349e96c54ac9d43a349b7db06e93af6e83af292aeb65b2.zip
Installing package libpq[core,openssl,zlib]:x64-linux...
Elapsed time for package libpq:x64-linux: 3.691 min
Starting package 6/6: soci:x64-linux
Building package soci[core,postgresql]:x64-linux...
-- Downloading https://github.com/SOCI/soci/archive/99e2d567161a302de4f99832af76e6d3b75b68e6.tar.gz -> SOCI-soci-99e2d567161a302de4f99832af76e6d3b75b68e6.tar.gz...
-- Extracting source /home/hanejun/samples/packages/vcpkg/downloads/SOCI-soci-99e2d567161a302de4f99832af76e6d3b75b68e6.tar.gz
-- Applying patch fix-dependency-libmysql.patch
-- Applying patch export-include-dirs.patch
-- Applying patch fix-mysql-feature-error.patch
-- Using source at /home/hanejun/samples/packages/vcpkg/buildtrees/soci/src/d3b75b68e6-17246bde8d.clean
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
CMake Warning at installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:487 (message):
  The following variables are not used in CMakeLists.txt:

      MYSQL_INCLUDE_DIR
      WITH_

  Please recheck them and remove the unnecessary options from the
  `vcpkg_cmake_configure` call.

  If these options should still be passed for whatever reason, please use the
  `MAYBE_UNUSED_VARIABLES` argument.
Call Stack (most recent call first):
  ports/soci/portfile.cmake:36 (vcpkg_cmake_configure)
  scripts/ports.cmake:145 (include)

-- Building x64-linux-dbg
-- Building x64-linux-rel
-- Installing: /home/hanejun/samples/packages/vcpkg/packages/soci_x64-linux/share/soci/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /home/hanejun/.cache/vcpkg/archives/42/422033e197bc3b2936f44c33913403391b3dd9ed8ce659229cd538dff540d64c.zip
Installing package soci[core,postgresql]:x64-linux...
Elapsed time for package soci:x64-linux: 57.87 s

Total elapsed time: 7.341 min

The package soci provides CMake targets:

    find_package(SOCI CONFIG REQUIRED)
    target_link_libraries(main PRIVATE SOCI::soci_core_static SOCI::soci_empty_static SOCI::soci_postgresql_static)

Additional context
I listed 'libsoci' but was not able to find any shared libraries like libsoci_core.so.4.0.0.
# fd libsoci --no-ignore
vcpkg/installed/x64-linux/lib/libsoci_empty.a
vcpkg/installed/x64-linux/lib/libsoci_core.a
vcpkg/installed/x64-linux/lib/libsoci_postgresql.a
vcpkg/packages/soci_x64-linux/lib/libsoci_empty.a
vcpkg/packages/soci_x64-linux/lib/libsoci_core.a
vcpkg/packages/soci_x64-linux/lib/libsoci_postgresql.a
vcpkg/installed/x64-linux/debug/lib/libsoci_empty.a
vcpkg/installed/x64-linux/debug/lib/libsoci_core.a
vcpkg/installed/x64-linux/debug/lib/libsoci_postgresql.a
vcpkg/packages/soci_x64-linux/debug/lib/libsoci_empty.a
vcpkg/packages/soci_x64-linux/debug/lib/libsoci_core.a
vcpkg/packages/soci_x64-linux/debug/lib/libsoci_postgresql.a
vcpkg/buildtrees/soci/x64-linux-rel/lib/libsoci_empty.a
vcpkg/buildtrees/soci/x64-linux-rel/lib/libsoci_core.a
vcpkg/buildtrees/soci/x64-linux-rel/lib/libsoci_postgresql.a
vcpkg/buildtrees/soci/x64-linux-dbg/lib/libsoci_empty.a
vcpkg/buildtrees/soci/x64-linux-dbg/lib/libsoci_core.a
vcpkg/buildtrees/soci/x64-linux-dbg/lib/libsoci_postgresql.a

on linux packages are only build static. see https://github.com/microsoft/vcpkg/blob/master/triplets/x64-linux.cmake .
You need to make a custom triplet to enable shared libraries on linux. But you might run into RPATH problems afterwards.

Now I understand.
I was able to build my test application with soci libraries built by vcpkg but the test program showed error message at runtime like below.
# ./test
soci error: Failed to find shared library for backend postgresql

They says:
CMake build produces set of shared and static libraries for SOCI core and backends separately.
Bottom of the Instration page.
And I posted the same thing to soci section but I got a message from soci person, below:
If vcpkg really doesn't build shared libraries but still builds the core library to use them, it's a bug in the package and will need to be fixed there.
(https://github.com/SOCI/soci/issues/904#issuecomment-1047133259)

Hence I thought there to be something problem in the vcpkg soci package and posted it here.
Thank you.

I think you need to look at the usage of static plugins. soci provides the cmake targets SOCI::soci_postgresql_static, SOCI::soci_sqlite3_static etc.
See https://github.com/SOCI/soci/issues/497 for an explanation.
What it basicly saying is:
use soci::session(soci::postgresql,...) instead of soci::session("postgresql",...)

Thank you very much @mathisloge. I'll try this.

It's me that was wrong. I didn't think I would like to have used shared libraries.
I have read the explanation and was able to find my mistake. I didn't know the way to write session function parameters to find the module statically. I changed my code according to above and I got the problem solved.
      // This is my mistake. This searches shared libraries.
      // soci::session s("postgresql://dbname=testdb port=5432 host=localhost user=postgres password=password"s);
      //
      // To use soci static library, the parameter should have been like below.
      soci::session s(soci::postgresql, "dbname=testdb port=5432 host=localhost user=postgres password=password"s);

Thank you very much again, @mathisloge.


[WebView] additional options for media

WebView should have properties added for media support:

allowsInlineMediaPlayback
mediaPlaybackRequiresUserAction

For example I added this to RCTWebView.m to autoplay videos and play them inline:
    - (instancetype)initWithEventDispatcher:(RCTEventDispatcher *)eventDispatcher
    {
      if ((self = [super initWithFrame:CGRectZero])) {
        super.backgroundColor = [UIColor clearColor];
        _automaticallyAdjustContentInsets = YES;
        _contentInset = UIEdgeInsetsZero;
        _eventDispatcher = eventDispatcher;
        _webView = [[UIWebView alloc] initWithFrame:self.bounds];
        _webView.delegate = self;
        _webView.allowsInlineMediaPlayback = YES;
        _webView.mediaPlaybackRequiresUserAction = NO;
        [self addSubview:_webView];
      }
      return self;
    }

Maybe someone can do a PR for this? :)

@yamill take a look at this PR I did: https://github.com/facebook/react-native/pull/1631
I'm pretty sure it can help you to make this pull request by yourself :shipit:
Let me know if I can help you with something.

@alvaromb awesome thanks that's really helpful! will take a shot at making the pull request :+1:

Closing because this is stale :)

Closing because this is stale :)


How to set starting number for serial counter?

Hi, I'm generating serial number using this configuration :
{   field: 'ticketNumber',   prefix: 'ZSP',   separator: '-',   initCounter: 12405,// experimental won't work   digits: 5, }
and output is something like this : ZSP-00001, and I want it to start from a specific number instead of 0 and output be like : ZSP-12405
How can I achieve this formatting option?

Hi @namipsg
As mentioned in the readme, the initCount argument sets how frequently to initialize count value to 1 , daily, monthly or yearly.
The initial value always starts with 1, currently there's no option to set the count starting value.

I think it's a good feature to have. If more people are interested to have this feature implemented. We would be happy to see any PR submissions.

@amustaque97 PR request submitted.


Auth plugin gives internal type errors

Hi, I'm getting following errors from pothos internally:
node_modules/@pothos/plugin-scope-auth/src/global-types.ts:36:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'scopeAuth' must be of type 'PothosScopeAuthPlugin<Types>', but here has type 'PothosScopeAuthPlugin<Types>'.

36       scopeAuth: PothosScopeAuthPlugin<Types>;
         ~~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:7:13
    7             scopeAuth: PothosScopeAuthPlugin<Types>;
                  ~~~~~~~~~
    'scopeAuth' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:40:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'scopeAuthOptions' must be of type 'ScopeAuthPluginOptions<Types> | undefined', but here has type 'ScopeAuthPluginOptions<Types> | undefined'.

40       scopeAuthOptions?: ScopeAuthPluginOptions<Types>;
         ~~~~~~~~~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:10:13
    10             scopeAuthOptions?: ScopeAuthPluginOptions<Types>;
                   ~~~~~~~~~~~~~~~~
    'scopeAuthOptions' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:45:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'runAuthScopes' must be of type '(context: Types["Context"], scopes: Merge<BuiltInScopes<Types> & Partial<Types["AuthScopes"]>>, unauthorizedError?: ((result: ForbiddenResult) => string | Error) | undefined) => MaybePromise<...>', but here has type '(context: Types["Context"], scopes: Merge<BuiltInScopes<Types> & Partial<Types["AuthScopes"]>>, unauthorizedError?: ((result: ForbiddenResult) => string | Error) | undefined) => MaybePromise<...>'.

45       runAuthScopes: (
         ~~~~~~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:14:13
    14             runAuthScopes: (context: Types['Context'], scopes: AuthScopeMap<Types>, unauthorizedError?: (result: ForbiddenResult) => Error | string) => MaybePromise<void>;
                   ~~~~~~~~~~~~~
    'runAuthScopes' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:141:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'authField' must be of type '<Args extends InputFieldMap, Type extends TypeParam<Types>, Scopes extends FieldAuthScopes<Types, ParentShape, InputShapeFromFields<Args>>, ResolveShape, ResolveReturnShape, Nullable extends FieldNullability<...> = Types["DefaultFieldNullability"]>(options: Normalize<...>) => FieldRef<...>', but here has type '<Args extends InputFieldMap, Type extends TypeParam<Types>, Scopes extends FieldAuthScopes<Types, ParentShape, InputShapeFromFields<Args>>, ResolveShape, ResolveReturnShape, Nullable extends FieldNullability<...> = Types["DefaultFieldNullability"]>(options: Normalize<...>) => FieldRef<...>'.

141       authField: <
          ~~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:54:13
    54             authField: <Args extends InputFieldMap, Type extends TypeParam<Types>, Scopes extends FieldAuthScopes<Types, ParentShape, InputShapeFromFields<Args>>, ResolveShape, ResolveReturnShape, Nullable extends FieldNullability<Type> = Types['DefaultFieldNullability']>(options: Normalize<Omit<FieldOptionsFromKind<Types, ParentShape, Type, Nullable, Args, Kind, ResolveShape, ResolveReturnShape>, 'resolve'> & {
                   ~~~~~~~~~
    'authField' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:177:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'withAuth' must be of type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => QueryFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>', but here has type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => QueryFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>'.

177       withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(
          ~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:60:13
    60             withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => QueryFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>;
                   ~~~~~~~~
    'withAuth' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:186:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'withAuth' must be of type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => MutationFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>', but here has type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => MutationFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>'.

186       withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(
          ~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:63:13
    63             withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => MutationFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>;
                   ~~~~~~~~
    'withAuth' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:195:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'withAuth' must be of type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => SubscriptionFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>', but here has type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => SubscriptionFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>'.

195       withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(
          ~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:66:13
    66             withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => SubscriptionFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>;
                   ~~~~~~~~
    'withAuth' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:204:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'withAuth' must be of type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => ObjectFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>', but here has type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => ObjectFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>'.

204       withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(
          ~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:69:13
    69             withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => ObjectFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>;
                   ~~~~~~~~
    'withAuth' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:213:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'withAuth' must be of type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => InterfaceFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>', but here has type '<Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => InterfaceFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>'.

213       withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(
          ~~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:72:13
    72             withAuth: <Scopes extends FieldAuthScopes<Types, ParentShape, Record<string, unknown>>>(scopes: Scopes) => InterfaceFieldBuilder<ReplaceContext<Types, ContextForAuth<Types, Scopes> & object>, ParentShape>;
                   ~~~~~~~~
    'withAuth' was also declared here.

node_modules/@pothos/plugin-scope-auth/src/global-types.ts:229:7 - error TS2717: Subsequent property declarations must have the same type.  Property 'Context' must be of type 'ContextForAuth<Types, Scopes>', but here has type 'ContextForAuth<Types, Scopes>'.

229       Context: ContextForAuth<Types, Scopes>;
          ~~~~~~~

  node_modules/@pothos/plugin-scope-auth/dts/global-types.d.ts:78:13
    78             Context: ContextForAuth<Types, Scopes>;
                   ~~~~~~~
    'Context' was also declared here.

Found 10 errors in the same file, starting at: node_modules/@pothos/plugin-scope-auth/src/global-types.ts:36

when trying to import following type:
import type { AuthFailure } from "@pothos/plugin-scope-auth/src/types";

You shouldn't import things from nested files like this.  This should be exported directly form the plugin.
The issue is that the types used for the package are imported from @pothos/plugin-scope-auth/dts/* not from src.  I'm not 100% sure why these are incompatible, but generally importing from somewhere that isn't included in the exports list in package.json is likely to cause issues.  I'd personally recommend setting moduleResolution to node16 or nodeNext in tsconfig so that you are warned about these kinds of imports

Ok, thanks! This is what IntelliJ auto imports when accessing that specific type via going to the related definition, that's why it's accessed like that. I would imagine similar mistake to happen for other IntelliJ users as well. Maybe also for vscode users if it resolves types in similar manner.
Anyways, importing like import type { AuthFailure } from "@pothos/plugin-scope-auth did the trick 👍


bootstrap 4.1.2 support

Seems bootstrap <4.1.1 has security vulnerabilities. Would you please make it aligned with bootstrap 4.1.2

Hi.
Bootstrap v4.1.3 was realise recently, it would be great to update the package 😉

@seanCodes dibs.

Finally got some time to get this updated (thanks for pinging me @calvinjuarez)

v0.5.0 aligns with Bootstrap 4.1.3 (the latest)
v0.4.0 aligns with Bootstrap 4.1.2 (in case anyone needs it)

Thanks everyone for your patience!

Thank you!


Klass.count returns 0 but Klass.where({}).count returns correct count

This happens only when connected to DynamoDB on AWS.
We don't face this issue with local DynamoDB running in a docker container.
Dynamoid Version: 3.5.0
DynamoDB Local: Latest amazon/dynamodb-local image
DynamoDB AWS
irb(main):005:0> PushNotification.count
=> 0
irb(main):006:0> PushNotification.where({}).count
=> 1004
irb(main):007:0> PushNotification.create!(title: "Test 1")
=> #<PushNotification:0x2133b712 @_touch_record=nil, @changed_attributes={}, @associations={}, @previously_changed={"title"=>[nil, "Test 1"], "created_at"=>[nil, Thu, 23 Apr 2020 15:02:42 +0000], "updated_at"=>[nil, Thu, 23 Apr 2020 15:02:42 +0000], "id"=>[nil, "e7c406b5-0ddb-4e7d-9682-10e7ead1270d"]}, @attributes={:title=>"Test 1", :created_at=>Thu, 23 Apr 2020 15:02:42 +0000, :updated_at=>Thu, 23 Apr 2020 15:02:42 +0000, :id=>"e7c406b5-0ddb-4e7d-9682-10e7ead1270d"}, @new_record=false, @validation_context=nil, @attributes_before_type_cast={:title=>"Test 1", :created_at=>Thu, 23 Apr 2020 15:02:42 UTC +00:00, :updated_at=>Thu, 23 Apr 2020 15:02:42 UTC +00:00, :id=>"e7c406b5-0ddb-4e7d-9682-10e7ead1270d"}, @errors=#<ActiveModel::Errors:0x5ca4c88a @messages={}, @base=#<PushNotification:0x2133b712 ...>, @details={}>>
irb(main):008:0> PushNotification.where({}).count
=> 1005
irb(main):009:0> PushNotification.count
=> 0
irb(main):010:0>

class PushNotification
  include Dynamoid::Document

  table name: :push_notifications

  # fields declaration
  field :title, :string

  field :body, :string

  field :payload
end

Thank you for the question.
Actually it's an expected behavior, but looks like not documented properly.
Model.count method returns an approximated value based on AWS DynamoDB internal statistic. Internally Dynamoid makes DescribeTable API call and returns ItemCount value.
Model.where(...).count is implemented in different way. It returns accurate value actually "reading" all the items using either Query or Scan operations. Internally it doesn't load all the items from the DynamoDB but only size of items which satisfy the filtering conditions. It's done with Select option with value COUNT.
So these methods differ in both accuracy and cost. DescribeTable call is almost free but Query/Scan can be very expensive in terms of throughput and money.
Hope I answered your question.  The documentation will be updated to prevent such confusing.

Thank for the quick revert @andrykonchin .
So this is not an issue with locally runnning dynamodb. This happens only when we connect to DynamoDB tables on aws cloud.
Is that also expected?

It seems to me this is expected. According to the documentation for ItemCount:

DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.

So the AWS DynamoDB has this limitation but emulation with dynamodb-local doesn't have it.

Thanks for the explanation. Closing this.


Cannot debug dotnetcore app in docker

Issue Type: Bug
I am trying to debug my dotnetcore app which is deployed in a docker container. But after attaching the remote process, only following message appears in the debug console and the debug symbols have not been loaded.

My dockerfile looks like the following:
FROM mcr.microsoft.com/dotnet/core/sdk:2.2
RUN apt update && \
    apt install unzip && \
    curl -sSL https://aka.ms/getvsdbgsh | /bin/sh /dev/stdin -v latest -l /vsdbg
WORKDIR /app

COPY ./bin/Debug/netcoreapp2.2/ /app/
ENTRYPOINT ["dotnet", "Sun.dll"]

And I also added a new configuration in the launch.json file:
{
    "name": ".NET Core Docker Attach",
    "type": "coreclr",
    "request": "attach",
    "processId": "${command:pickRemoteProcess}",
    "pipeTransport": {
        "pipeProgram": "docker",
        "pipeArgs": [ "exec", "-i", "test_cont" ],
        "debuggerPath": "/vsdbg/vsdbg",
        "pipeCwd": "${workspaceRoot}",
        "quoteArgs": false
    },
    "sourceFileMap": {
        "/app": "${workspaceRoot}"
    }
}

VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:30:08.229Z)
OS version: Linux x64 5.0.0-29-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4600M CPU @ 2.90GHz (2 x 2893)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: disabled_offnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: unavailable_offviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 1, 1

Memory (System)
3.83GB (0.16GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
18%

Extensions (8)

Extension
Author (truncated)
Version

vscode-docker
ms-
0.8.1

azure-account
ms-
0.8.4

csharp
ms-
1.21.3

azure-iot-edge
vsc
1.17.0

azure-iot-toolkit
vsc
2.10.0

azure-iot-tools
vsc
0.3.0

vscode-iot-device-cube
vsc
0.1.1

vscode-iot-workbench
vsc
0.10.13

Please file for https://github.com/OmniSharp/omnisharp-vscode


Desktop Attributes

Adding in the capability to load/create and edit track attributes within the desktop version.
TestData: https://viame.kitware.com/#/viewer/6006e01cf751cc24d135ec2b - has attributes on track #1 I believe.  Remember that on web version you won't see attributes unless they are added to the global list of attributes.  This isn't required for the desktop version.
Explanation:

Process CSV import data to determine track attributes.  Currently done outside of the actual CSV importation which isn't the most performant but is organized a bit better.  I essentially took advantage of the outside loop used to process the TrackData[] into a MultiTrackRecord.  Let me know if you feel strongly about this being injected directly into the parser.  I like how the parser returns a clean Array right now.
The AttributeProcessor is a function used to iterate through the TrackData[] and gather up the used attributes as well as their values and number of times those values occur.  It does a secondary pass of the attributes to try to determine the attribute type.  It cascades from number to boolean to text based on attempting to covert all of the possible set values for that attribute.  Finally it counts the number of occurrences of the value and if it is text and all values are used at least twice it will infer that it is a set of discrete values.
When we have the ability to load the meta.json that will override any settings that are calculated with the csv/json file itself.
Modified the API for attributes to include the datasetId.  This is necessary for desktop to access the proper metadata file to update it when attributes are edited.  Note these are typically one time things that occur when adding/editing/deleting an attribute from the system or on mount for the TrackDetailsView.  The web version ignores this data, but in the future will be used to directly modify the metadata attributes field utilizing the same endpoints instead of storing it globally in girder.

Questions:

Should parsing for attributes be moved into CSV Parser or left with the TrackData[] -> MultiTrackRecord conversion?
Should I remove the inferring of type and leave all items as text?
Should the attributeProcessor.ts be it's own thing or moved into utils.ts?

TODO (Future PR):

Setting/Updating/Deleting attributes both for the web version and the desktop version affect the displaying of attributes in the editor but not the source data of the track JSON.  Technically deleting an attribute should search all of the tracks and remove the attribute wherever it is set in the JSON field.  I'm wondering if that should be implemented.  This is an expensive task based on the number of detections and attributes in the system.  May want to have a discussion on how to implement this.

Should parsing for attributes be moved into CSV Parser or left with the TrackData[] -> MultiTrackRecord conversion?

I like it how it is.

Should I remove the inferring of type and leave all items as text?

Type inference seems handy, but if it turns out to be unreliable, we can remove it.

Should the attributeProcessor.ts be it's own thing or moved into utils.ts?

I like it in its own file.

Should parsing for attributes be moved into CSV Parser or left with the TrackData[] -> MultiTrackRecord conversion?

I like it how it is.

Should I remove the inferring of type and leave all items as text?

Type inference seems handy, but if it turns out to be unreliable, we can remove it.

Should the attributeProcessor.ts be it's own thing or moved into utils.ts?

I like it in its own file.

Did the comment updates and I created a useDatasetId to provide the datasetID to the track-details.  This is much better.

Did the comment updates and I created a useDatasetId to provide the datasetID to the track-details.  This is much better.

Something weird is going on.
Track and detection attributes seem to erase each other.
https://user-images.githubusercontent.com/4214172/106312338-78d55380-6234-11eb-910c-8083ce070b56.mp4

Something weird is going on.
Track and detection attributes seem to erase each other.
https://user-images.githubusercontent.com/4214172/106312338-78d55380-6234-11eb-910c-8083ce070b56.mp4

Something weird is going on.
Track and detection attributes seem to erase each other.

Wasn't thinking right.  On girder the _id is provided for you when you create a new attribute hence you could get conflicts with the same name.  So it wasn't setting the _id properly.

Something weird is going on.
Track and detection attributes seem to erase each other.

Wasn't thinking right.  On girder the _id is provided for you when you create a new attribute hence you could get conflicts with the same name.  So it wasn't setting the _id properly.

Looks great.
One last thing: can we change the default visibility mode to always show the editable fields? Its fine that you can have the nice condensed view, but if you create a new attribute, it doesn't show up until you hit the eye, which I don't think it a good default.
This optimization should be opt-in rather than opt-out.

I agree that after adding a new attribute it should be immediately available.  I think we can change it so that if you add a new attribute it will swap to show all the fields after adding it.  The main concern I have is that there is a difference between viewing attributes and actively editing them.  Some of my test datasets have 10-15 track and then another 10-15 detection attributes.  They would all be displayed in the list by default meaning that it's difficult to view the data because of the sparseness especially if flipping through tracks or frames.  I'm open to any other alternatives if you think of any, maybe the eye should be something else?

I'm just sort of looking at the risks:
"too busy, hard to parse, I'm overwhelmed" vs "I think this is broken it's not working I'm frustrated"
seems like we shoud choose the first risk. It's a hard problem and I can't come up with a solution that will work for everyone.

There's always the "show more" / "show less" option at the end of the list.  Those are pretty ubiquitous, might be more intuitive than the eye, but I still think "show more" is a better default.


Question: how to import to Android-Studio?

What are you having trouble with, specifically?  Please re-open when you have actionable information.

Why do you close it before I have a chance to reply?
The issue is that I can't import it.
When I try, it makes the entire OS super slow, and never ends building. I've waited for more than 7 minutes, on a quite capable laptop, and it still doesn't finish. This is not acceptable.
Here's a screenshot:

I will try it at home too, on a brand new PC that I've bought, if you wish.

Which version of Android Studio are you using?

Actually, something was wrong just today with this laptop, as I tried Toshiba's "eco" mode. Made whole OS super slow. Not related to the repo.
I've disabled it, and now it works fine. Should have some stuff updated in the gradle files though:

Wonder what was the exact issue I had when I reported about this.

The build tools version will be upgraded in the next release.  The gradle version and build tools are rev'ing a lot right now with Android Studio.

reving?

Revisioning.  The versions are changing quite rapidly right now because of the work being done to go from Android Studio 2.x to Android Studio 3.x.  So Gradle versions and build tools versions will fall behind frequently for a while.

oh ok


Update module docs: efficiently handle compressed files

I've seen all sorts of custom groovy code dealing with compressed files in modules. Most of them could be handled by a simple zcat -f with the additional benefit of never writing the uncompressed files to disk.
Even the slightly more complicated cases can be handled by named unix pipes most of the time.

Nice! Have we got a feel for which modules are rubbing your pet peeve up the wrong way?

Many of my recent ones have used groovy logic. I too would prefer these suggestions and adding this to the docs will be super helpful for guidance
@grst  I'll start reviewing them and see if zcat -f or named pipes will work.

Nice! Note that in order for it to work on Mac OS, it has to be zcat -f < $input.  This is because zcat on Macs still expects the old .Z file suffix that was used at the time of the compress command.

@charles-plessy, good catch!
Would gzip -cdf behave more consistently on mac? On linux it's the exact equivalent of zcat.

Would gzip -cdf behave more consistently on mac? On linux it's the exact equivalent of zcat.

Nice! It works well on my Mac and the intent is much clearer than with zcat -f <.


Modal prevent Form Submit

I want to submit an HTML form and display a modal during the reload timer. The reload timer is necessary because the transmitted values are checked and saved by the Webserver during this time.
Without the "modal-trigger" class, the HTML form works as expected. But not with the class. The modal is displayed but the HTML form is not submitted.
Expected Behavior
Form should be submitted and Modal should be displayed
Steps to Reproduce (for bugs)
https://codepen.io/jens1985/pen/VwXrNKQ
Remove the "modal-trigger" Class on Line 19 and it works fine.

thanks for submitting the issue. Btw, can you try to reproduce this with version 1.1?

I tried for several days.
Now I found the error. I forgot a "#" in the href.
Sorry for wrong reporting.

Hey, yes, I was already using the latest version.

Hello, sorry for the reply delay
Looks an expected behavior for me. In most cases, the modal trigger may be an anchor or a button, so I believe the original devs puts some event.preventDefault() in the code.
There are multiple ways to solve it, but there is my solution :
HTML remains same
<form action="/get" target="hidden-form">
  <input type="text" name="ID" value="%ID%">
  <input type="submit" value="Submit" class="btn modal-trigger" href="#modal1">
</form>

    Daten werden gespeichert...

document.addEventListener('DOMContentLoaded', function() {
  var modal = document.querySelectorAll('.modal');
  var instancesModal = M.Modal.init(modal, {
    // since materialize prevent us submitting the form
    // why not executing a function that will do the job ?
    // Here, I defined the onOpenEnd callback to call
    // the below handleOpenEnd function
    onOpenEnd: handleOpenEnd
  });
});

// Nice ! Materialize provide us two parameters :
// First one is the DOM element of the modal's div
// Second one is the DOM element of the modal's trigger button (input submit here)
function handleOpenEnd(_modalElement, submitElement) {
  // <input type="submit"> always have a .form property, which point to the
  // form's DOM element.
  const form = submitElement.form;
  if (form) {
    // we submit the form.
    form.submit();
  }
}

Please close this issue if my solution solved your problem

This worked for me. Thanks :)


Select what roles/users should be able to use what commands

Using some kind of permission level system.

This can easily be done with a permissions DB table and using the @commands.check() decorator from discord.py


How to switch between multiple browser tabs

Hello, I was trying to learn to automate workflows using tagui. It is as a great platform indeed.
I stumbled across a issue where I need to switch to a different window as part of the workflow. How do I do it.
Eg: I go to this link "https://www.google.com/intl/en-GB/gmail/about/#" and click on the "Sign in" link.
This is taking me to a new Browser tab where I have enter my user credentials.
How do I switch my control to the parent window to this new tab. Really appreciate your help in this regard.

Thanks
Prashanth

Check out the popup step.
popup signin
type xxxx as yyyy
click zzzz

Thanks for the quick reply, It works..Thanks once again.


Provide a way to print package version

Perhaps pulasr.__version__ as the idiom.

@tisonkun i believe we can close this now, as this has been merged in already. Thanks!

Thank you @erichare! Maybe you can ask for assign the next time so we can cross-refer the effort :)

I’ll try to remember to do that yep :) Thanks!

On Feb 15, 2023, at 4:32 PM, tison @.***> wrote:
Thank you @erichare https://github.com/erichare! Maybe you can ask for assign the next time so we can cross-refer the effort :)
—
Reply to this email directly, view it on GitHub https://github.com/apache/pulsar-client-python/issues/27#issuecomment-1432225705, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFK6S4FLTKBIOZZENWXFKLWXVRSRANCNFSM6AAAAAARWXO6AI.
You are receiving this because you were mentioned.


consuming packages with stricter ABI checks

⚠ Just to trigger CI

Based on my reading from:

https://docs.conan.io/en/latest/versioning/lockfiles/introduction.html#locking-dependencies
https://blog.conan.io/2019/09/27/package-id-modes.html
https://docs.conan.io/en/latest/creating_packages/define_abi_compatibility.html#versioning-schema
https://docs.conan.io/en/latest/creating_packages/define_abi_compatibility.html#changing-the-default-package-id-mode

getting lost working on https://github.com/conan-io/docs/issues/1904

C3i uses the default methods so obviously the "stricter" package_id's are not available!


file_manager: trap the exception if the claim is not a stream

If claim is not a stream, the line claim.stream.source.bt_infohash will raise a ValueError exception because claim.stream does not contain a valid object.
This will happen if we try to download a claim that is in fact a collection (a playlist).
lbrynet get lbry://@something#e/My-New-List#f

Since at the moment we don't trap this exception, it prints the entire trace of the exception.
Traceback (most recent call last):
  File "/opt/git/lbry-sdk/lbry/file/file_manager.py", line 117, in download_from_uri
    if claim.stream.source.bt_infohash:
  File "/opt/git/lbry-sdk/lbry/schema/claim.py", line 55, in stream
    return Stream(self)
  File "/opt/git/lbry-sdk/lbry/schema/claim.py", line 108, in __init__
    self.message = self.claim.get_message(self.claim_type)
  File "/opt/git/lbry-sdk/lbry/schema/claim.py", line 46, in get_message
    raise ValueError(f'Claim is not a {type_name}.')

Therefore we trap this ValueError to avoid showing the entire trace.
We don't do anything with the exception, we just raise it again so that it is handled by the calling code daemon.jsonrpc_get.
Then it will show an appropriate message.
WARNING  lbry.extras.daemon.daemon:1106: Error downloading lbry://@something#e/My-New-List#f: Claim is not a stream.

I'd suggest fixing the code in File "/opt/git/lbry-sdk/lbry/file/file_manager.py", line 117, in download_from_uri to guard the access by first checking that the claim actually has a stream.

Okay, I thought so too, but that's a more involved solution, and at the moment I don't know the code that well, so that's what I decided to just trap ValueError. As it produces a simple explanation (Claim is not a stream.) I thought that was enough.

@belikor what's next here? does it need another review?

@belikor what's next here? does it need another review?

No. I haven't touched this at all. Lex mentioned a few steps to try but I haven't tested that.

Okay, I updated the pull request. Now we raise ResolveError if claim.is_collection or if not claim.is_stream before accessing claim.stream.source.bt_infohash.
We trap it later in the code so we don't have the entire traceback printed to the terminal.
This also helps in case we try to download a channel, which raises the same error.
lbrynet get '@something#e'

WARNING  lbry.file.file_manager:254: Failed to download @something#e: Failed to resolve 'cannot download a channel claim, specify a /path'.
WARNING  lbry.extras.daemon.daemon:1106: Error downloading @something#e: Failed to resolve 'cannot download a channel claim, specify a /path'.

Coverage remained the same at 67.979% when pulling 215115d10f7c758b306732d23571ad233d3550bb on belikor:fix-claim-not-stream into 268decd6556619625151c574890eba9f8dc2c90d on lbryio:master.

Now we don't use ResolveError, we use InvalidStreamURLError. This pull request now follows from #3403.
It traps those claims that are not streams such as reposts and collections, as well as channels.
lbrynet get collection-music
lbrynet get LUKAS-LION---1984:a
lbrynet get @lbry

WARNING  lbry.file.file_manager:258: Failed to download collection-music: Invalid LBRY stream URL: 'collection-music'
WARNING  lbry.extras.daemon.daemon:1114: Error downloading collection-music: Claim is not a stream.
WARNING  lbry.file.file_manager:258: Failed to download LUKAS-LION---1984:a: Invalid LBRY stream URL: 'LUKAS-LION---1984:a'
WARNING  lbry.extras.daemon.daemon:1114: Error downloading LUKAS-LION---1984:a: Claim is not a stream.
WARNING  lbry.file.file_manager:258: Failed to download @lbry: Invalid LBRY stream URL: '@lbry'
WARNING  lbry.extras.daemon.daemon:1114: Error downloading @lbry: Invalid LBRY stream URL: '@lbry'

@belikor looks like you made some changes? do you want another review? if so, click the "Re-request review" button next to @eukreign 's name on the right side. this will also automatically assign him.
in general, our process is that whoever the issue is assigned to, they are responsible for taking the next step.

Okay, now it's rebased.

this PR conflicts with your other PR, let's get that one merged first, then you can rebase this one

Using #3403


[Design]: Changes to improve performance

Track disposables in a list with lock instead of a concurrent bag
Allocate a single _createServiceAccessor instead of one per instance
Removed syncObject and just locked the _resolvedServices

Measurements on the way...
/cc @rynowak @halter73 @pranavkm @lodejard @benaadams

This halves allocations for DI

overall looks good - main point here seems to be assuming that the service provider is low-contention and we can do simpler/lighter things because of that.

788k -> 384k (-51%)
If you didn't want to go full pooling, but were ok with partial pooling, you could pool the dictionary and list and clear them up in the disposable; which would trim it to 144k but limit the scope for the pooling.
788k -> 144k (-82%)
Though likely with that you'd need to return to an object for locking and add bool for dispose check

updated.
Going to try a few more things:

Don't allocate disposables until required.

@benaadams New changes for ya.

Looks :shipit:  to me. Will wait for @benaadams's numbers though.

Improved:

And down overall for the module/dll:

Merged


bug: Cron CI judgment logic problem

Current Behavior
error code line link
The cron CI should not use the logical OR condition, as it can cause the CI to run every time. Instead, it should use the logical AND condition.
Expected Behavior
This is a timed CI and should not be run every CI.
Error Logs
No response
Steps to Reproduce

Run the CI And u will got this error.

Environment

APISIX Ingress controller version (run apisix-ingress-controller version --long)
Kubernetes cluster version (run kubectl version)
OS version if running APISIX Ingress controller in a bare-metal environment (run uname -a)

Thanks!

#1850 has been merged, I will close this one, thanks


PURCHASE-1511 PURCHASE-1512 Fix conditions-of-sale sublinks

https://artsyproduct.atlassian.net/browse/PURCHASE-1511
https://artsyproduct.atlassian.net/browse/PURCHASE-1512
I'm not sure about the ramifications of this change. While it fixes the problem and doesn't seem to break other webviews, I don't understand why new pages were originally being pushed onto the top level navigation stack rather than the one that the web view is currently in. Any ideas @ashfurrow ?
Also I noticed that this conditions-of-sale web view doesn't have a back button because it's a modal and it was opened from within a modal. So to go 'back' after visiting a sublink you have to dismiss the modal, going back to a different modal, and then tap back into the conditions of sale modal. We should really rethink these funky navigation flows as part of the mobile experience team.
#trivial

See: https://github.com/artsy/eigen/pull/1435

@ashfurrow this should be 🍏 now


A way to modify request before routing

Is there any way I could modify the request, the url for example, before it gets routed?

Does not work for me :(
package main

import (
	"fmt"
	"net/http"
	"github.com/julienschmidt/httprouter"
)

// Middleware bla bla bla
type Middleware struct {
    h http.Handler
}

// Implement the ServerHTTP method on our new type
func (m Middleware) ServeHTTP(w http.ResponseWriter, r *http.Request) {
    // You can modify the request here ...
	fmt.Fprintf(w, "test one")
    m.h.ServeHTTP(w, r)
    // ... and the response here
}

func index(w http.ResponseWriter, r *http.Request, _ httprouter.Params) {
	fmt.Fprintf(w, "test two")
}

func main() {
	router := httprouter.New()
	router.GET("/", index)
	m := &Middleware{router}
	http.Handle("/", m)
}

Result:
404 page not found


Booting time is more 1 seconds after installation

Lunar version: 1.0.0-beta.3
Laravel Version: 11.1
PHP Version: 8.2.23
Database Driver & Version:

Expected Behaviour:
Application booting time before instalation of Lunar package is 15ms.
Actual Behaviour:
Application booting time after Lunar package installation is about 1-2 seconds.
Steps To Reproduce:
I have a low performing VPS with several Laravel applications running perfectly.
After installing this package the entire application becomes non-functional as response times increase from a few ms to 1-2 seconds.
This is unacceptable since any change to a Livewire component takes seconds.
According to Debugbar the booting time exceeds 15 ms. to 2 seconds.
After removing the package everything is back to normal.

Please can you provide detailed steps to reproduce. What do you mean by application? If you turn off the debugbar, do you get the same speed issue?

Hi  @glennjacobs

I hire a "High Performance" instance on Vultr VPS (the cheapest one; 1GB of Memory; 1 virtual core)
I uploaded a e-commerce built with Laravel: https://tienda.modacora.es/ but WITHOUT Lunar package installed
The interaction with my website Livewire components is inmediate. If I click the button "Activar" then the coupon discount modal is openeded immediately
I installed Lunar package following https://docs.lunarphp.io/core/installation.html
Then my website working slow. When I click the button "Activar" on my website the coupon modal component is opened 1 second later because ALL requests on my website are very very slow
If I uninstall the Lunar package everything returns to normal

I fixed the problem:
https://stackoverflow.com/questions/74073036/why-does-this-laravel-package-increase-boot-process-by-3-seconds
Lunar installs the blade-icons package and the boostrapping time is fixed executing artisan icons:cache

I see. I believe this is related to Filament.


#672 Error where multiple timestamp filters are registered in a multi data source

Description
멀티 데이터소스에서 타임스탬프 필터 중복해서 등록되는 현상이 있습니다.
Related Issue : #672

How Has This Been Tested?

대시보드를 생성합니다.
대시보드 편집화면에서 필터 패널을 엽니다.
중복된 필터없이 정상적으로 필터가 표시되는지 확인합니다.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project. it will be added soon
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document. it will be added soon
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Additional Context

run build
deploy to 2