Problems with deployment on W2008R2

Hi there
I found this jewel, and decided to test it, and on my PC it worked fine using the local server tied internally to Visual Studio 2013, then I set it up on a local W2008R2 server, in a webApp directory:
/chat
Initially it did not work, but after renaming the start of the 3 sentences, that includes the whole .js code in the original html, it started to show the little chat-popup on the right bottom.
But, all the admin stuff did not work, I tried it once, on my computer,
As I did the deployment to the server, using VS 2013 automated deployment, the encrypted passwords file was copied, but the pages did not accept any pwd, and hence I did put the correct passwords there!
The I deleted the password file, (and reading the code) it should re-create it,
But it still kept asking for the password, and not the re-registration procedure.
May be I am not too familiarized with MVC4 ¿could this have been kept in the server's cache?
I tried to debug the code, and set breakpoints, and the code never reached the .CS code section on login ¿am I doing something wrong?
I believe I am a skilled programmer, used to VS2010 until now,
I was heavily using .aspx web-forms, internal code (algorithms, AI, etc.) used old-fashion and complicated remoting and appdomain schema, but did only some minor ALAX code using JQuery never (until now) met SignalIR as a multi-protocol code-proxysm nor AngularJS and the other quirks used here.
I was using a W2003R2 server, adn had to upgrade, because it does not support ASP.NET 4.5, (only until 4.0) WTF!
¿any clue?
.

Maybe the app does not have permission to write to the file? If everything else is working and not the admin part, that's the reason I could see.

The app does have permission, but it never goes trough the proxy's part on the server, I did setup breakpoints under VS and for a reason I could not establish it worked on the development, but not on the server, I checked and the app can write on the file, also there is no way to reissue the password, based on the actual app demo. May be a cache or just a problem with the subdirectory addressing part of the .js and/or some part of the app. I could not check it.
Yesterday I saw a JS component called  "function hasStorage()" which always returns null on the VS and may be return something else on the server test. I don't know how to intercept this on debugging with VS, may be on the browser debugger.. I have to check!
Remember the server test is located inside a directory which contains the WebApp (the deployment was done with VS2013)

I'm closing this since LCSK is changing to a more robust customer communication app.
Thank you for your interests in LCSK and I hope Parle will be ready soon so you can have a look at it.


cant delete entries on the integration

System Health details
System Information

version
core-2024.7.0

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.4

os_name
Linux

os_version
6.6.29-haos

arch
x86_64

timezone
Africa/Johannesburg

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4952

Installed Version
1.34.0

Stage
running

Available Repositories
1392

Downloaded Repositories
35

HACS Data
ok

AccuWeather

can_reach_server
ok

remaining_requests
29

Home Assistant Cloud

logged_in
true

subscription_expiration
January 1, 2018 at 2:00 AM

relayer_connected
false

relayer_region
null

remote_enabled
true

remote_connected
false

alexa_enabled
true

google_enabled
true

remote_server
null

certificate_status
null

instance_id
33111abc566c409eb120782a2d406de9

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 12.3

update_channel
stable

supervisor_version
supervisor-2024.06.2

agent_version
1.6.0

docker_version
25.0.5

disk_total
58.3 GB

disk_used
12.8 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization
kvm

board
ova

supervisor_api
ok

version_api
ok

installed_addons
Terminal & SSH (9.14.0), Studio Code Server (5.15.0), File editor (5.8.0), Music Assistant (2.0.3), Samba share (12.3.1), Node-RED (18.0.1), ESPHome (2024.6.6)

Dashboards

dashboards
7

resources
27

views
17

mode
storage

Recorder

oldest_recorder_run
June 27, 2024 at 12:02 PM

current_recorder_run
July 7, 2024 at 10:11 PM

estimated_db_size
173.41 MiB

database_engine
sqlite

database_version
3.45.3

Sonoff

version
3.7.3 (e240aaf)

cloud_online
14 / 14

local_online
12 / 12

Spotify

api_endpoint_reachable
ok

Checklist

[X] I have read the FAQ to see if there is a known solution to my problem.
[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[ ] This issue is not a duplicate issue of currently previous issues..

Describe the issue
i cannot delete entries on powercalc integration i wanted to start over with my power measurement and reinstall the integration and cannot get rid of entries thus integration is not being deleted instead it swaps to not loaded.
i went into the config of every entry and changed the config to disable Create energy sensor and Create utility meters but it still sets to not loaded.
Reproduction steps
1.not sure of to reproduce this error
2.
3.
...
Debug logs
2024-07-07 22:11:32.417 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sonoff 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-07-07 22:11:32.418 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mass 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-07-07 22:11:32.419 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration truenas 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-07-07 22:11:32.420 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-07-07 22:11:32.420 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartlife 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-07-07 22:11:32.421 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya 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-07-07 22:11:32.421 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ui_lovelace_minimalist 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-07-07 22:11:32.422 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration powercalc 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-07-07 22:11:32.423 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media 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-07-07 22:11:34.813 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] CURRENT_HVAC_HEAT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.HEATING instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.815 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] CURRENT_HVAC_IDLE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.IDLE instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.816 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] HVAC_MODE_AUTO was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.AUTO instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.818 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] HVAC_MODE_HEAT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.819 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] HVAC_MODE_OFF was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.OFF instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.820 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] SUPPORT_PRESET_MODE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.PRESET_MODE instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.822 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.824 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE_RANGE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE_RANGE instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.825 WARNING (ImportExecutor_0) [homeassistant.const] TEMP_CELSIUS was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.827 WARNING (ImportExecutor_0) [homeassistant.const] TEMP_FAHRENHEIT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.FAHRENHEIT instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.831 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_CLOSE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.CLOSE instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.832 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_OPEN was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.OPEN instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.833 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_SET_POSITION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.SET_POSITION instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.835 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_STOP was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.STOP instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.836 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_CLOSE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.CLOSE instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.837 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_OPEN was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.OPEN instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.839 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_SET_POSITION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.SET_POSITION instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.849 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_STOP was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.STOP instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.863 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_DIRECTION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.DIRECTION instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.868 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.873 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_SET_SPEED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.SET_SPEED instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.877 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_DIRECTION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.DIRECTION instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.881 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.886 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_SET_SPEED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.SET_SPEED instead, please report it to the author of the 'localtuya' custom integration
2024-07-07 22:11:34.921 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'localtuya' accesses hass.helpers.service. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from service directly at custom_components/localtuya/__init__.py, line 164: hass.helpers.service.async_register_admin_service(, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-07-07 22:11:36.236 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration, localtuya with title: localtuya and entry_id: e5d44ac72d6ef0a04a49cac4ad8d27d5, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2099, in async_forward_entry_setup
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-07-07 22:11:36.247 ERROR (MainThread) [custom_components.ui_lovelace_minimalist.base] HACS Integration repo "browser mod" is not installed!
2024-07-07 22:11:36.249 ERROR (MainThread) [custom_components.ui_lovelace_minimalist.base] HACS Frontend repo "light-entity-card" is not installed, See Integration Configuration.
2024-07-07 22:11:36.249 ERROR (MainThread) [custom_components.ui_lovelace_minimalist.base] HACS Frontend repo "mini-media-player" is not installed, See Integration Configuration.
2024-07-07 22:11:36.249 ERROR (MainThread) [custom_components.ui_lovelace_minimalist.base] HACS Frontend repo "simple-weather-card" is not installed, See Integration Configuration.
2024-07-07 22:11:36.250 ERROR (MainThread) [custom_components.ui_lovelace_minimalist.base] HACS Frontend repo "lovelace-state-switch" is not installed, See Integration Configuration.
2024-07-07 22:11:36.250 ERROR (MainThread) [custom_components.ui_lovelace_minimalist.base] HACS Frontend repo "weather-radar-card" is not installed, See Integration Configuration.
2024-07-07 22:11:36.254 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'ui_lovelace_minimalist' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/ui_lovelace_minimalist/cards", "/config/custom_components/ui_lovelace_minimalist/cards", True)])`; This function will be removed in 2025.7 at custom_components/ui_lovelace_minimalist/base.py, line 366: self.hass.http.register_static_path(, please create a bug report at https://github.com/UI-Lovelace-Minimalist/UI/issues
2024-07-07 22:11:36.430 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.house_power_dayly (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('power') it is using; expected None or one of 'measurement'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22
2024-07-07 22:11:37.924 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/frontend", "/config/custom_components/hacs/hacs_frontend_experimental", False)])`; This function will be removed in 2025.7 at custom_components/hacs/frontend.py, line 49: hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 22:11:37.965 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/iconset.js", "/config/custom_components/hacs/iconset.js", True)])`; This function will be removed in 2025.7 at custom_components/hacs/frontend.py, line 57: hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 22:11:37.974 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-07-07 22:11:37.980 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles", "/config/www/community", True)])`; This function will be removed in 2025.7 at custom_components/hacs/base.py, line 1162: self.hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 22:11:49.036 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 642: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 22:12:22.056 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 95, in delete
    result = await hass.config_entries.async_remove(entry_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1729, in async_remove
    del self._entries[entry.entry_id]
        ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1546, in __delitem__
    self._unindex_entry(entry_id)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1540, in _unindex_entry
    del self._domain_unique_id_index[domain][unique_id]
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
KeyError: 'powercalc'
2024-07-07 22:16:25.135 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to walk with args ('/config/custom_components/sonoff',) inside the event loop by custom integration 'sonoff' at custom_components/sonoff/core/xutils.py, line 14: for root, dirs, files in os.walk(path): (offender: /config/custom_components/sonoff/core/xutils.py, line 14: for root, dirs, files in os.walk(path):), please create a bug report at https://github.com/AlexxIT/SonoffLAN/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#walk
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/system_health/__init__.py", line 89, in get_integration_info
    data = await registration.info_callback(hass)
  File "/config/custom_components/sonoff/system_health.py", line 45, in system_health_info
    "version": f"{integration.version} ({xutils.source_hash()})",
  File "/config/custom_components/sonoff/core/xutils.py", line 14, in source_hash
    for root, dirs, files in os.walk(path):

2024-07-07 22:16:25.141 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to scandir with args ('/config/custom_components/sonoff',) inside the event loop by custom integration 'sonoff' at custom_components/sonoff/core/xutils.py, line 14: for root, dirs, files in os.walk(path): (offender: <frozen os>, line 366: ?), please create a bug report at https://github.com/AlexxIT/SonoffLAN/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#scandir
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/system_health/__init__.py", line 89, in get_integration_info
    data = await registration.info_callback(hass)
  File "/config/custom_components/sonoff/system_health.py", line 45, in system_health_info
    "version": f"{integration.version} ({xutils.source_hash()})",
  File "/config/custom_components/sonoff/core/xutils.py", line 14, in source_hash
    for root, dirs, files in os.walk(path):

2024-07-07 22:16:25.148 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open with args ('/config/custom_components/sonoff/__init__.py', 'rb') inside the event loop by custom integration 'sonoff' at custom_components/sonoff/core/xutils.py, line 20: with open(path, "rb") as f: (offender: /config/custom_components/sonoff/core/xutils.py, line 20: with open(path, "rb") as f:), please create a bug report at https://github.com/AlexxIT/SonoffLAN/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#open
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/system_health/__init__.py", line 89, in get_integration_info
    data = await registration.info_callback(hass)
  File "/config/custom_components/sonoff/system_health.py", line 45, in system_health_info
    "version": f"{integration.version} ({xutils.source_hash()})",
  File "/config/custom_components/sonoff/core/xutils.py", line 20, in source_hash
    with open(path, "rb") as f:

2024-07-07 22:20:27.418 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 95, in delete
    result = await hass.config_entries.async_remove(entry_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1729, in async_remove
    del self._entries[entry.entry_id]
        ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1546, in __delitem__
    self._unindex_entry(entry_id)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1540, in _unindex_entry
    del self._domain_unique_id_index[domain][unique_id]
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
KeyError: 'powercalc'
2024-07-07 22:20:29.909 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 95, in delete
    result = await hass.config_entries.async_remove(entry_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1729, in async_remove
    del self._entries[entry.entry_id]
        ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1546, in __delitem__
    self._unindex_entry(entry_id)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1540, in _unindex_entry
    del self._domain_unique_id_index[domain][unique_id]
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
KeyError: 'powercalc'

Diagnostics dump or YAML config
No response

very strange. Never seen this error before, some internal HA core code which goes wrong it seems.
Not sure how to reproduce.
Did you try restarting HA already?

i did try yea multiple times i dono what happened but it started making more and more of that lights entries by itself its siting on number 51 i deleted the statistics data of them in dev tab and the entities connected to them but the powercalc ones are still staying.

i have added sum screenshots hope this helps

Very strange. Could you please click three dots and "Dowload diagnostic" for some of these config entries and share here?

of course here u go
config_entry-powercalc-66ed46be0668c50457b0941e8971be84 5.json
config_entry-powercalc-2a1197b74d079c014f2e4f8affeb6285 4.json
config_entry-powercalc-71b4bfc3e58c4592a1db6929598e9215 3.json
config_entry-powercalc-f4ba9f28ac40a35c0d822f59da248ca0 2.json
config_entry-powercalc-4c84f70eaf242967c3efdac3e8a6068d 1.json

100% will give this a try and report back here things a lot

hmm I see, did you set lights as group when creating a virtual power sensor? Than powercalc creates a new group and corresponding config entry. This is a relatively new feature. However seems to be a bug down the road somewhere which causes powercalc to keep creating this same group, maybe after each startup, which causes you to have 51 of them now.
They all have the same unique_id "lights", and this causes the HA interface to error when trying to delete the config entry.
I don't have time to deep dive into this atm, but probably will find some time in a couple of days.
When you are a littlebit tech savy you can fix it by editing config/.storage/core.config_entries. Backup the file before editing. Next remove all json entries for powercalc with the name lights. Make sure it's valid JSON and restart HA afterwards.
Hope this helps.

oky this solved the isue for me thangs so much

I have found the bug why same group entry was created again and again.
Fixed with #2375, and included in v1.13.2 release which I just issued.
You probably need to cleanup the entries once more when you have more than 1 of them.


adds $search for regex-based queries

👍 thanks @alvin! Anyone on @feathersjs/core-team have any objection to using $match instead of $search or $like? I actually prefer $match. If not, I'll merge and cut a new minor.

Oops, the commit msg should read $match, not $select :)
On Sat, Apr 23, 2016 at 10:16 AM, Eric Kryski<EMAIL_ADDRESS>wrote:

👍 thanks @alvin https://github.com/alvin! Anyone on
@feathersjs/core-team https://github.com/orgs/feathersjs/teams/core-team
have any objection to using $match instead of $search or $like? I
actually prefer $match. If not, I'll merge and cut a new minor.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/feathersjs/feathers-query-filters/pull/11#issuecomment-213789313

@alvin no problem.  The other two pieces are:

add a test to the common service tests
and actually implement the usage in the db adapters (we can roll these out over time)

I'm working on a $match implementation in the rethinkdb adapter, but
thought I'd throw this little PR out first to see what the appetite for
moving this way in core is, vs moving my implementation to an extension.
If someone from core was willing to create a test for a regex matching
method, then I could ensure my rethink fork passes (feels like that might
be useful for QA given this would be a new core feature).
Thoughts?
On Sat, Apr 23, 2016 at 10:49 AM, Eric Kryski<EMAIL_ADDRESS>wrote:

@alvin https://github.com/alvin no problem.  The other two pieces are:

add a test to the common service tests
and actually implement the usage in the db adapters (we can roll
these out over time)

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/feathersjs/feathers-query-filters/pull/11#issuecomment-213796311

Yes this was definitely on the roadmap, so good timing. We called it $search but we'll wait a day to see if anyone else has an opinion on the naming.
We had also documented it in a few of the database repos, like feathers-mongoose.

I think one of us can add a test and bump the version over the next few days. Would be sweet to get this squared away early in the release. 😄

Sounds good. I'm a-okay with "$search" too... factors to consider seem to
be:

How many target databases use a method named $match vs. $search?
Conversely, "$search" is a simpler/broader abstraction, perhaps that
is better for an abstraction layer?
Would the future include a situation where a simple wildcard/text
match for "$search" wants to co-exist alongside a regex-powered "$match"?

On Sat, Apr 23, 2016 at 12:33 PM, Eric Kryski<EMAIL_ADDRESS>wrote:

I think one of us can add a test and bump the version over the next few
days. Would be sweet to get this squared away early in the release. 😄
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/feathersjs/feathers-query-filters/pull/11#issuecomment-213816662

Related to #12

How many target databases use a method named $match vs. $search?

Not sure. Probably doesn't matter too much as we'll just map it. We do that for all the special query params already.

Conversely, "$search" is a simpler/broader abstraction, perhaps that is better for an abstraction layer?

That's sort of why I proposed it, because $match sort of implies regex (at least to me) whereas we depending on the database type we might utilize other mechanisms (iLike, full text search, etc.).

Would the future include a situation where a simple wildcard/text match for "$search" wants to co-exist alongside a regex-powered "$match"?

Possibly, and somewhat related to my answer above. We'll probably just start with regex but it might evolve into more database specific constructs based on performance/matching requirements.

Closing. Sorry for not merging this but after some discussion in https://github.com/feathersjs/feathers/issues/334#issuecomment-260834107 we decided to leave search up to the individual database adapters.


Discussions can't be replied to and commits were incorrect applied

Currently both discussions are locked to collaborators only.
The commits I made you also didn't apply instead you copied them so they're both now attributed to you even though I wrote the changes.

Currently both discussions are locked to collaborators only.

That is correct. As I have stated no less than 4 times now, open a new discussion and share what you're trying to do.

The commits I made you also didn't apply instead you copied them so they're both now attributed to you even though I wrote the changes.

I was unable to merge your PR because it contained multiple unrelated changes, only some of which I wanted to apply. I did credit you in each of those commits.
Additionally please do not use the issue tracker for non-bug-related reports. Discussions exist for a reason, please use them.


Symbol ⊴

This is a symbol that is commonly used in Algebra to represent normal subgroup. I think it makes sense to add it to the symbol list

Agree. Typst is like a baby. Here is a workaround
#let subgroup = text[\u{22B4}]

$ subgroup $


Returned full (original) picture in place of cropped one, after migrated from from ArthurHub/Android-Image-Cropper

After the suggestions given in  this issue , after migrating from ArthurHub/Android-Image-Cropper, the camera and gallery is open properly and I can crop the imagen, but when the process ends the "original image" is returned, in place of the cropped one (I guess the full image is saved into temp_file  file).
I'm using the same code that I have in the old plugin and everything woks fine but this final step.
I call the camera/gallery with this (old) code
CropImage.activity()
    .setFixAspectRatio(true)
    .setGuidelines(CropImageView.Guidelines.ON)
    .start(this);

And then, in "activityResult" the code is this one  (resultUri returns the full image, not cropped like in old plugin) -
The ***  line is the only one that I had to change  because "the old "val resultUri =  result.uri" seems not to be supported anymore, using one or other option for Android version to work properly.
  public override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent?) {
        super.onActivityResult(requestCode, resultCode, data)
        if (requestCode == CropImage.CROP_IMAGE_ACTIVITY_REQUEST_CODE) {
            if (resultCode == Activity.RESULT_OK) {

*************
                var resultUri = CropImage.getPickImageResultUriContent(this, intent)
                if (Build.VERSION.SDK_INT>28) {
                     resultUri = CropImage.getPickImageResultUriFilePath(this, intent).toUri()
              }
*************
             // **** here shows the original image, not the cropped one *****
             avatar_configuracion.setImageURI(resultUri)
                // upload cropped picture to server
                subir_imaxe(resultUri)
            } else if (resultCode == CropImage.CROP_IMAGE_ACTIVITY_RESULT_ERROR_CODE) {
                toast(“Error message to user")
            }
        }
    }

I try to use “the new code" that is in the wiki but I can't made it to work... only using the "old code" works in both camera and gallery, but doesn't return the cropped image.
I don't know if anyone can help me to discover what the problem is, or if I'm totally wrong keeping the old code ;)
Thanks in advance ;)

Fixed!
It understood bad the instructions, and I was “asking for the original picture” 🤦♂.
If anyone has the same problem, here is the code that finally works for me: (in bold the afected lines)
public override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent?) {
        super.onActivityResult(requestCode, resultCode, data)
        if (requestCode == CropImage.CROP_IMAGE_ACTIVITY_REQUEST_CODE) {
            if (resultCode == Activity.RESULT_OK) {
                **val result: CropImage.ActivityResult = CropImage.getActivityResult(data)!!
                var resultUri: Uri = result.uriContent!!
                var resultFilePath: String = result.getUriFilePath(this, true).toString()**
                // upload cropped picture to server
                avatar_configuracion.setImageURI(resultUri)
             subir_imaxe(resultUri, resultFilePath)
            } else if (resultCode == CropImage.CROP_IMAGE_ACTIVITY_RESULT_ERROR_CODE) {
                toast("Houbo un erro ó cargar o arquivo. Asegúrate de que se trata dunha imaxe e téntao de novo")
            }
        }
    }


Update pyarrow version to 0.17.0

Update recipe, code and docs.

Blocked by:
test_series_value_counts_no_unboxing (sdc.tests.test_series.TestSeries) ... LLVM ERROR: out of memory
Fatal Python error: Aborted

Linux failed with:
File "setup.py", line 28, in
from setuptools import setup, Extension, find_packages, Command
File "/home/vsts/miniconda3/envs/sdc_env/conda-bld/sdc_1588945713648/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/lib/python3.7/site-packages/setuptools/init.py", line 19, in
from setuptools.dist import Distribution, Feature
File "/home/vsts/miniconda3/envs/sdc_env/conda-bld/sdc_1588945713648/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/lib/python3.7/site-packages/setuptools/dist.py", line 36, in
from setuptools import windows_support
File "/home/vsts/miniconda3/envs/sdc_env/conda-bld/sdc_1588945713648/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/lib/python3.7/site-packages/setuptools/windows_support.py", line 2, in
import ctypes
File "/home/vsts/miniconda3/envs/sdc_env/conda-bld/sdc_1588945713648/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/lib/python3.7/ctypes/init.py", line 7, in
from _ctypes import Union, Structure, Array
ImportError: libffi.so.7: cannot open shared object file: No such file or directory


Fix wallet sync starting on app launch

closes #107
kind of wanted to give a shot at this, all of the wallet sync code is in wallet_selector_page.go, would it make sense to split it out or would a hacky fix like this be suitable?

It is better to split the code, move the sync startup logic to home page. Calling wallet selector's navigation function while on home page will potentially introduce bugs in future, devs will assume that OnNavigatedTo() and  OnNavigatedFrom() are called only when the page is created and destroyed.

@CPunch please fix branch conflicts

Looks good, you can update the title.

@CPunch you have branch conflicts


Add linestring viz

Create a new Viz class tyle, LinestringViz, that allows a user to create a line map from a geojson source or a vector tile source.  Follow the same techniques used to make the Choropleth Viz.  https://github.com/mapbox/mapboxgl-jupyter/pull/40
Example:

Agree with color and width being the two major features to control, @akacarlyann.  It's similar to the Choropleth, just Choropleth uses color and height, while Linestring uses color and width.  Obviously excited to review a PR, if you have one!

Great @akacarlyann.  We can open up a separate PR to address the utils function sprawl before the next release.  Agree we need to keep the utils functions as generic and re-usable across visualizations as possible.

Closed in https://github.com/mapbox/mapboxgl-jupyter/pull/92


Upload it on Heroku ?

I tried uploading this repo to Heroku but it didn't work. It is working on local Host though. Please can you guide me with proper steps to upload the repo ?  Which files should I upload ?

What part of this repo are you intending to send to Heroku?

Hi,sir. How to host the project to Firebase or Google Cloude Platform. if I choose your repo as my template,what part of this repo I need to insert to my project which should be uploaded to Firebase or Google Cloud Platorm?

The smart-home-provider contains all the code that one's cloud needs to run as well as a frontend for creating and changing virtual devices.


Address the deprecation warnings from the logger

This PR https://github.com/rails/rails/pull/45976 has deprecated the optional argument for the color method in the Active Support:: LogSubscriber, and the graphql-client gem depends on the deprecated interface in the
lib/graphql/client/log_subscriber.rb. As a result, the following deprecation warning would appear when used with Rails 7.1.
DEPRECATION WARNING: Bolding log text with a positional boolean is deprecated and will be removed in Rails 7.2. Use an option hash instead (eg. ).

This PR updates the code to be compatible with both the latest rails and the older ones.
cc @erikdstock @jonallured

Thanks for this fix!


Help please.

If current OpenXR runtime is SteamVR:
As a normal OpenXR application, it works fine.
But with OpenXR-OverlayLayer  doesn't, see log:
Log:
[Info] [SK info] Startup
[Info] [SK info] Couldn't create an OpenXR session, no MR device attached/ready? [XR_ERROR_INITIALIZATION_FAILED]
[Error] [SK error] Couldn't initialize StereoKit in MixedReality mode!
[Error] [SK error] System Platform failed to initialize!

If current OpenXR runtime is Oculus:
As a normal OpenXR application, it works fine.
But with OpenXR-OverlayLayer  doesn't:
System.AccessViolationException
HResult=0x80004003
Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Source=Cannot evaluate the exception source
StackTrace: Cannot evaluate the exception stack trace

What could I have done wrong?

Sorry I should have been clear that this project is not ready for end users. OpenXR-OverlayLayer is full of bugs, and I never got it to work cross-platform. It only seems to work on WMR.

Yes this project is currently dead, and looking into other ways to make overlays work instead.


Rewrite block::tests::generate as proptest strategies.

As noted in 64d9d5599298d63a03f47d4ca038a4645ca265fc, the existing generate functionality would be better expressed as a collection of proptest strategies, so that it's composable with other test code.
These strategies should be exposed as part of the crate API in test mode, so that they can be used by other crates (particularly zebra_consensus.

This is not required, and there is a TODO in the code.


#155 basic disqus integration

I've added the basic code for disqus integration, but it won't load yet
(Our disqus site is: anyway-feedback.disqus.com, using the gmail feedback account credentials)
might be a localhost issue, but my staging env. is not working after all recent changes...
Any ideas? @daonb ?

Thanks

@ahik please refer to this pull request for the work done so far.


IAuthorizationService somehow incomplete

I think the actual definition of IAuthorizationService is somehow incomplete, since the AuthorizeAsync method handles properly just  in-memory resources. More specifially, if the resource has already been loaded in memory from a DB it may give an answer to all needed authorization queries, but what if one would like to load and page from a DB  just all resources the current user has the permission to read?
An in-memory test would be inadequate, since it would force loading uneusefull resources in memory(also the ones the user can't read), and would interfere with a LinQ skip/take paging.
Accordingly, the developer would be forced to spread authorization rules all over the DB queries instead of encapsulating them only into IAuthorizationHandler implementations! In other word with the actual implementation the user is forced to break IAuthorizationHandler  encapsulation, loosing most of modularity-related advantages of the IAuthorizationService/IAuthorizationHandler  framework.
The problem I sketched shortly might be solved by adding a new method to IAuthorizationService , say something like:
Expression<Func<T, bool>> AuthorizePredicate<T>(ClaimsPrincipal user, IEnumerable<IAuthorizationRequirement> requirements)
That would return a LinQ predicate the developer may insert in a LinQ Where to filter out all not authorized resources. Clearly, also the IAuthorizationHandler should be enriched properly to give the devolper the possibility to define all needed predicates. The predicate returned by AuthorizePredicate should be the "logical or" of all predicated provided in all relevant IAuthorizationHandlers.

Accordingly, the developer would be forced to spread authorization rules all over the DB queries instead of encapsulating them only into IAuthorizationHandler implementations! In other word with the actual implementation the user is forced to break IAuthorizationHandler encapsulation, loosing most of modularity-related advantages of the IAuthorizationService/IAuthorizationHandler framework.

Can you show some examples of what type of logic you want to write int your IAuthorizationHandler? Returning a predicate seems awfully coupled to LINQ (which we don't really do in services at this level in the stack). What if you were using a repository or a queries that weren't LINQ based? How does the IAuthorizationHandler produce filters for an arbitrary T?

@davidfowl ,
Actually, the problem is just for authorization on resources. Thus IAuthorizationHandler  can't contain a method specific for any T since it doesn't contain any generic. It should contain something like: Task HandlePredicateAsync(PredicateAuthorizationHandlerContext context).  The abstract class AuthorizationHandler<TRequirement, TResource> that already contains a generic for the resource type should contain something specific for TResource:
HandleRequirementAsync(PredicateAuthorizationHandlerContext context,
                                   OperationAuthorizationRequirement requirement,
                                   TResource resource)

Then the developer should provide a concrecte class WITHOUT generics(ie with all generics instantiated) that is specific for a single concrete resource.
On the other side IAuthorizationService can contain a  AuthorizePredicate method with a generic T that  basically performs just a a cast of an expression that contains all constraints specific for the concrete  type passed as T.

What if you were using a repository or a queries that weren't LINQ based?

Expression<Func<T, bool>> is not specific for LinQ. It is just a "meta-description" of the code that computes a predicate. It may be used to create a retrieval procedure for any envirnoment. It might be also parsed to get an elastic search json snippet.
However, one might think also to a different way to encode a predicate, such as the one used by the OData library.
I admit the overall idea is not very "elegant". However, resource handlers should encapsulate all logics to verify authorization, but in all pratical applications resource are contained in store external to the program (db, not sql dbs, redis, etc.) so the authorization framework should somehow contain logics to interact also with external data structures. Otherwise, the overall authorization logics can't be encapsulated in the authorization framework, which, in turn, would make the part of the authorization framework that is specific for resources, quite uneusefull: "partial encapsulations" usually do not offer valuable advantages.
The solution I propose is not necessarely the best one but the problem I raise exists and should be adressed somehow.
In a few days I'll provide a pratical  example of what I have in mind.

Maybe, the difficulty of encapsulating completely Authorizations on a resource in a presentation layer framework depends on resource authorizatins being business layer stuffs.
Maybe, Authorization on resources in asp.net is not an useful stuff. Developer should handle authorizations on resources in the business layer with the same tools they use to interact with the persistence layer. The presentation layers should receive DTO already containing information on the allowed operations for the current user.

Moving this to discussions. We generally recommend policies and authorization to be done below the UI/presentation layer, aside from just basic visibility logic, but leaving this issue open to monitor discussions about more concrete examples.


odo dev

description by @kadel:
odo dev
Running the application on the cluster for development (inner loop)
The result of successful execution of odo dev is Devfile component deployed in inner loop mode.
By default command deletes all resources that it created before it exits.
When users runs command with --cleanup=false there will be no cleanup before existing. The message "Press Ctrl+c to exit and clean up resources from cluster." will be only "Press Ctrl+c to exit."
If user executed odo dev --cleanup=false and then run this command again. The first line of the output should display warning: "Reusing already existing resources".
When there is no devfile in the current directory and no flags were provided command starts in interactive mode to guide user through the devfile selection.
When some flags were provided and there is no devfile in the current directory command exits with error:
No devfile.yaml in the current directory. Use `odo create component` to get devfile.yaml for your application."

When devfile exists in the current directory deploy application in inner loop mode using the information form devfile.yaml in the current directory.
Flags

-o (string) output information in a specified format (json).
--watch (boolean) Run command in watch mode. In this mode command is watching the current directory for file changes and automatically sync change to the container where it rebuilds and reload the application.
By default, this is true (--watch=true). You can disable watch using --watch=false
--cleanup (boolean). default is true when user presses ctrl+c it deletes all resource that it created on the cluster.

--watch and --cleanup flags will be added later. v3.0.0-alpha1 won't have those flags.
Interactive mode
$ odo dev
There is no devfile.yaml in the current directory.

Based on the files in the current directory odo detected
Language: Java
Project type: SpringBoot

? Is this correct? Yes

Current component configuration:
Opened ports:
- 8080
- 8084
Environment variables:
- FOO = bar
- FOO1 = bar1

? What configuration do you want change?  [Use arrows to move, type to filter]
> NOTHING - configuration is correct
  Delete port "8080"
  Delete port "8084"
  Add new port
  Delete environment variable "FOO"
  Delete environment variable "FOO1"
  Add new environment variable

⠏ Downloading "java-quarkus". DONE
Starting your application on cluster in developer mode ...
⠏ Waiting for Kubernetes resources ... DONE
⠏ Syncing files into the container ... DONE
⠏ Building your application in container on cluster ... DONE
⠏ Execting the application ... DONE
Your application is running on cluster.
You can access it at https://example.com

⠏ Watching for changes in the current directory ... DONE
Change in main.java detected.
⠏ Syncing files into the container ... DONE
⠏ Reloading application ... DONE
⠏ Watching for changes in the current directory ...

Press Ctrl+c to exit and clean up resources from cluster.

<ctrl+c>

⠏ Cleaning up ... DONE

Questions and their behavior is the same as for odo deploy command

WIP

Do we need adapters in the code anymore? I admit to never having understood them well in the first place.
What run modes to focus on? Only Run? Both Run and Debug?
Code for odo watch can be re-used, but needs to be trimmed to remove cases/flags we don't want to cover.
Port forwarding instead of using Ingress/Routes.

I'll start creating a "design document" as a part of the work on this issue. It will be a living document where we explain in plain English what a command would do in various scenarios.

What's done so far (#5441):

odo dev pushes to the Kubernetes cluster and watches for code changes.

What's remaining:

Integration tests
Documentation
Cleanup some hard coded items from the draft PR.

All issues/stories in acceptance criteria are addressed.
/close


Filtering UnionArray Changes DataType

Describe the bug
When filtering a UnionArray the output will only include the types that had at least one value selected by the filter. I think this is a bug, as I would not expect a filter to mutate the schema of the input
Expected behavior
This test should pass
let mut builder = UnionBuilder::new_dense(4);
builder.append::<Int32Type>("A", 1).unwrap();
builder.append::<Float64Type>("B", 3.2).unwrap();
let array = builder.build().unwrap();
let filter_array = BooleanArray::from(vec![true, false]);
let c = filter(&array, &filter_array).unwrap();

assert_eq!(array.data_type(), c.data_type())

The code runs fine for me. Perhaps it got fixed in #1589 or #1632?


Fix links

What this PR solves / how to test
Fixed several links. Tested and they all looked good to me
Author has addressed the following

Tests

[ ] TODO (before merge)
[ ] Included
[x] Not necessary because: Only fixed links

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required / Maybe required
[x] Not required because: Only fixed links

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[ ] Included
[x] Not necessary because: Only changed links

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s): https://github.com/cloudflare/cloudflare-docs/pull/...
[x] Not necessary because: Only changed links

hi @KPCOFGS,
Thank you so much for creating this PR and fixing those links <3. I left a couple of suggestions, but LGTM otherwise. As soon as my comments are addressed we're good to merge this 🌟

thank you s much @KPCOFGS for your contribution ❤ !! Merging...


Added the VOX extension chunks and corresponding IVoxLoader methods

Also, adds a new method to be compatible with "Resource" assets on Unity and their wonky load method.

Hey!
I'm away from home for the week, and won't be able to check that until sunday


8GB of models downloading every time I launch app.py

Every time I run app.py it needs to redownload all 8GBs of models. Could it not just reuse the models it already downloaded?
I've tried manually downloading diffusion_pytorch_model.bin, instant_mesh_base.ckpt, instant_mesh_large.ckpt, instant_nerf_base.ckpt and instant_nerf_large.ckpt and copied them to the ckpts folder, but it seems like they're being disregarded entirely.

Did you solve it ? I have the same issue...


Fix crash when writing $. in the editor

Fixes #49764 and fixes #50259
When writing $. in the editor, the analyzer expect an expression like object.attribute, but in this case, object is $, which is a get_node on nothing, so converted to nullptr, making the base null.
This PR only adds a check on nullptr to avoid the crash.

There's another PR open from last year which may also fix this, but it seems to have been limboed
https://github.com/godotengine/godot/pull/44667

There's another PR open from last year which may also fix this, but it seems to have been limboed
#44667

This PR fixed the issue in the parser, before the analyzer, which maybe makes it better than the current one.

Thanks!


XNOR-popcount

Hello,
I have a basic question to the implementation of the dot product. I try to comprehend the XNOR-popcount operation on an example.
1 -1  1 -1  1  1
1  1 -1  1  1 -1
The result should be -2. By simply using XNOR and popcount I get a result of 2.
I found the formel
2*p-N
which gives exactly the expected -2 with the XNOR-popcount result. Did I overlook something in the FINN-Paper? I could not find an explanation in the paper. Maybe I misunderstood something completely.
Thank you for your help
Kind regards

This is due to the fact that we represent -1 values using a zero bit (i.e. unset bits represent -1). Popcount simply counts the number of set bits (1s) in a bit vector, hence it will always return a nonnegative number. To convert the XNOR-popcount result into the dot product result, we take advantage of the fact that the bit vector can only contain set bits or unset bits: the number of set bits plus the number of unset bits will always be equal to the vector length.
In slightly more mathematical form: after we have performed XNOR, let p be the number of set bits in the bit vector (i.e. popcount result),  let n be the number of unset bits in the bit vector, and N be the vector length. We know that p+n=N, and would like to compute the dot product result p-n (since each unset bit will contribute -1, they contribute -n in total). Knowing only p and N, we can substitute n=N-p, so p-n = p - (N-p) = 2*p -N

Thank you very much for the explanation.

Hello,
I have the same questions. I understood what Mr. maltanar said.
However, the HLS source code appears to have no subtraction of unset bits from accumulation except for the first layer. From the second layer, XnorMul type is used. In the mul function (mac.hpp), the * operator of that type only performs a simple XNOR operation. In mac function (mac.hpp), only accumulation is performed with + = operation. After that, thresholding is done with activate function (mvau.hpp).
In the FINN article, I think that the threshold is also scaled by the (th + S) / 2 operation because the accumulation value is between 0 and S, where the negative is not taken into consideration. I wonder if the 2 * p-N operation mentioned by Mr. maltanar is applied to the HLS code.
Thank you.

You are right, we don't explicitly do the 2*p - N but instead exploit the flexibility of the thresholds to compensate for this. When doing code generation at the output of a bipolar-by-bipolar (meaning both operands are +-1) FC or conv layer, this is what gets called:
https://github.com/Xilinx/FINN/blob/master/FINN/backend/fpga/layers_fpga.py#L222
..which calls the makePositiveThresholds function here:
https://github.com/Xilinx/FINN/blob/master/FINN/backend/fpga/utils.py#L40
which is doing (th + fan-in) / 2 as you said.

Thank you for your quick response.
XNOR (1,0 representation) and popcount cause accumulation value to be between 0 and fanin.
And the (th+fan-in)/2 operation changes the threshold to the same scale.
Accumulation and activation can be done with popcount and makePositiveThresholds without having to do 2*p-N as you said.
I understand.
Thank you.

Hellow.
I have one more question.
In the source code of the link below, when the threshold is negative, you have replaced the threshold with fanin.
https://github.com/Xilinx/FINN/blob/e6d44508b4f7c6ac8e2c6929f2ffa85ea5761708/FINN/backend/fpga/utils.py#L58
I wonder why you replaced it with fan-in instead of zero.
In my opinion, if the threshold is negative, it should all be activated.
Thanks in advance for your reply.


Bump ember from 3.24.0 to 3.25.0

TODO:

Confirm log output acceptable
Test
Once new ember-api-store available use it (instead of yarn link'ed version)
Test
Remove logs from PR

https://github.com/rancher/ui/pull/5156


GETTING RID OF THE richard hendriks details

I am unable to get rid of the descriptions regarding richard hendriks

This is described in the README: Remove the Sidebar

yeah I did that as instructed, but it doesn;t remove the sidebar

It works if you place it in data/json_resume/en.json.
See https://github.com/schnerring/schnerring.github.io/tree/de5dcb7ffcc141e036179c2aefb641806acdfea6/data/json_resume


load /etc/rentpath/environment.cfg into ENV

Currently, every app has a copy of this file:
https://github.com/rentpath/ag/blob/dev/config/env.rb
Why not put it here?

environs is open source and has a single purpose. Putting it in this repo would introduce domain specific knowledge into it.
Another approach is to create a new repo with shared environment/deployment code. There's capistrano setup/methods we can use there too. Maybe call it rentpath_environment or something similar?

What @c0 said. This gem is used outside of RentPath.

Oh, hey @colinrymer ! How's it going? :smile:
I like @c0 's idea of a new repo for shared environment/deployment code.

@mpelzsherman life's good; got a 1-month old so sleeping when I can, but otherwise things are great.
I had been working on something similar to @c0's idea with putting the deployment code in the rentpath gem, but never got things finished up with that. If you did that, you could do something like require 'rentpath/capistrano' in the Capfile and something similar for the env.rb file.

Nice!
I can't find a "rentpath" repo.

doh, try rentpath/primedia. :grin:


Feature Request: Allow paymentTimeoutSeconds to be configurable in lncli

Background
Right now paymentTimeoutSeconds is hardcoded in the cli to 60 seconds for sendpayment. I am requesting that it's configurable as I would like to increase this value, unless there's a non obvious reason why it's limited.
https://github.com/lightningnetwork/lnd/blob/1bd211a7228d2f13ecaf514f611738837c057d94/cmd/lncli/cmd_pay.go#L31
https://github.com/lightningnetwork/lnd/blob/1bd211a7228d2f13ecaf514f611738837c057d94/cmd/lncli/cmd_pay.go#L339

Ohhh super quick, thanks @carlaKC!!


The "Annex focus has an improper available

When running the test conversions, I got an error in the annex focus from addAbsolutistEmpireNationalFocuses(). Specifically "Invalid trigger 'PHI' in common/national_focus/JAP_NF.txt line : 2793". This was from the Bhutan test save.
The relevant line is (currently) 2989 in HoI4FocusTree.cpp. I look a quick look and compared to other such lines and it seems like it should be fine. So I'm unsure what's wrong.

Apparently PHI is a special tag for HoI4 and must always be wrapped in quotes.

I tested this and apparently either I fixed it at some point or other changes fixed it. In any case, I no longer get this error.


Updated OSSpinLock for Sierra

While trying to build hyperkit on Sierra (beta 3) - it would throw on OSSpinLock - and the error messages suggested it should be replaced with os_unfair_lock. So, I replaced the OSSpinLock with the os_unfair equivalents  - commented out the OS_SPINLOCK_INIT methods, and  It passed the test and works. Here's the  os API for reference (doesn't say anything).
Docker is unusable without disabling the ntpd daemon - sudo launchctl unload /System/Library/LaunchDaemons/org.ntp.ntpd.plist - after that it works perfectly. So I thought that the vmnet / xhyve layer wasn't able to communicate with the system clocks. While testing hyperkit, it has this error message:
ACPI Error: Could not enable RealTimeClock event ....
ACPI Warning: Could not enable fixed event - RealTimeClock ....

It seems like ACPI  is already a known issue - and the test ended with PASS. But while researching why OSSpinLock was depreciated, I ran into. a few articles that made me think it should be replaced and may even be contributing to poor network performance on 10.10+. Webkit wrote a blogpost about why they replaced all spinlocks and os-provided-mutexes:

Compared to OS-provided locks like pthread_mutex, WTF::Lock is 64 times smaller and up to 180 times faster. Compared to OS-provided condition variables like pthread_cond, WTF::Condition is 64 times smaller. Using WTF::Lock instead of pthread_mutex means that WebKit is 10% faster on JetStream, 5% faster on Speedometer, and 5% faster on our page loading test.

I mentioned it in this issue - and it was pretty simple to implement - but this pull request is meant to raise awareness. I don't know if this method is backwards compatibility < 10.12 - or if they're going to patch 10.10+ to implement this - so it shouldn't be pulled into the main branch. I have not been able to confirm  whether or not OSSpinLock is  potentially effecting the entire hypervisor app - but I haven't seen this discussed anywhere in relation to docker - just wanted to bring it someone's attention.

Thanks for the patch!  We should restore build compatibility first with 10.12 and ensure correct operation, and then do the performance profiling.  I've got a patch in avsm/hyperkit@a9bdc65549ddabdc15c507341d8549f45f73f313 that checks for presence of the new functionality and uses it if the minimum version of MacOS X compatibility required is 10.12 or higher.
The minimum version capability is activated by setting the MACOSX_DEPLOYMENT_TARGET environment variable to 10.10 (which we need to do in Docker for Mac), at which point the build will break with deprecation warnings if compiled on 10.12.  We can fix this either by:

disabling -Werror if MACOS_DEPLOYMENT_TARGET is lower than 10.12 (a big hammer)
specifically disabling deprecation warnings, or at least not making them error. Need to look up the clang flags that allow this level of precision.

Any thoughts on this @ijc25 @djs55?

@RnbWd to make this suitable for merging, if you could pull in my patch, remove the whitespace changes from your diff, and create a single commit with a Signed-off-by: line, that would progress things.

-10 on disabling -Werror :)

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "os_unfair_lock" git@github.com:RnbWd/hyperkit.git somewhere
$ cd somewhere
$ git rebase -i HEAD~3
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@avsm there's more files that need to be patched, which I attempted to do based on your patch, but there's one more variable that throws an error if it's included in 10.12 beta. This is the error being thrown:
rc/vmm/vmm.c:217:5: error: use of undeclared identifier 'OS_SPINLOCK_INIT'
    vcpu_lock_init(vcpu);
    ^
src/vmm/vmm.c:97:39: note: expanded from macro 'vcpu_lock_init'
#define vcpu_lock_init(v) (v)->lock = OS_SPINLOCK_INIT;

I couldn't find an equivalent method in the os API - but I don't know that much about spinlocks so before finalizing the merge (which I can reduce into a single commit) - I want to make sure that the init function is handled properly. I commented it out so that it would compile - but it's only used once in each file where it's defined.

@GordonTheTurtle thanks - I will do that for the next push - but I need help / review to finish to finalized the change

I think my commit was rebased properly, although my last commit was not the most descriptive - I attempted to write a fix by using #ifndef XHYVE_USE_OSLOCKS - and it compiles on my machine locally, but I am not that experienced with C - so. I hope I patched it correctly. The failure now appears to be in located in platform_locks.h where <os/lock.h> is included

Hi @RnbWd, sorry for the delay responding I was offline for a long weekend. Anyway, thanks for bringing this to our attention.
I'm a little bit wary of using this undocumented new lock type, but I'm rather more wary of splitting the platform testing base into 2 (<10.12 and >=10.12) through the use of ifdef in this proposed fix (as it stands the newer code wouldn't be tested in CI either).
I think a preferable approach would be to switch unconditionally to using a pthread mutex. Hyperkit already extensively uses pthread's and pthread mutexes extensively in other contexts and I'm unsure what the motivation for using a platform-specific spinlock in this particular context is[0].
Would you be OK with reworking to use pthread mutexes? Don't worry if not, I can try and find someone to take a look.
[0] I suspect (just guessing) that it is something inherited from bhyve where spinlock vs mutex can make a difference when the code is running in kernel context, which is not something hyperkit needs to concern itself with since it is entirely in userspace.

I suspect (just guessing) that it is something inherited from bhyve where spinlock vs mutex can make a difference when the code is running in kernel context, which is not something hyperkit needs to concern itself with since it is entirely in userspace.

I've looked at the locks and can't see any reason why a pthread_mutex wouldn't suffice.  There are actually mutexes right beside the use of the spinlock in the vapic structures, so there's ample precedent...

@ijc25 I agree, I just learned about  all of this while attempting to compile hyperkit a few days ago, so I probably can't contribute much more at this time (until I  learn more). I just was curious as to why OSSpinLock was deprecated and the os_unfair_lock is still beta - but after researching OSSpinLock - it sounded pretty bad. I think having a branch for testing 10.12 would be interesting - but I think a compatible replacement for OSSpinLock makes sense.

@RnbWd thanks, I took a stab at the conversion and am therefore closing this issue in favour of #49 which implements the switch to pthread mutexes.


x/y lat/lon component values

I'd like to calculate slope and curvature from a geographic DEM (raster dimensions are in degrees). I'd like to do this without retrojecting the DEM. I think the only way to do this is to calculate component values (slope/curvature along lat/lon) then to scale each component by the local meters per degree lat/lon. Given this, would it make sense to add an option to relevant functions to return component values?

Yeah, this is something we need. A weighting factor for the y/x could be provided, probably as a matrix of the same size as the dem?

Ya, a row to column scaling would work. This could be a scalar (rectangular cells) or matrix the same size as the DEM (geographic).

should we introduce slope components (x and y) as a new function (maybe slopexy) of do we add a kwarg to slope?
do we adopt the convention that slope across columns to be x_slope and slope across rows to be y_slope?

Hmm. I was thinking of passing a x/y ratio as an argument to most methods. It can be a single value, or a column, or a matrix. The value and columns should be converted to a matrix so it can be used in the calculation.
Ideally, we can automatically set these things, if we have a trait for geographic stuff in GeoInterface. Let me whip up a PoC.

That sounds good to me and would be the use case for most users. For my workflows I will still need slope in x and slope in y, and curvature in x and curvature in y. I could back out slope x/y from slope and azimuth but I suspect it's faster just to compute them directly. But i think it will be strait forward to add those after the geographic stuff is implemented.
The idea of automating this sounds like a dream.

Will do... we could add a "dims" kwarg to slope


Support for HBase Data Source

I've been looking for a way to connect to HBase through SparklyR but I can't find any examples. Is it right so far, the only thing to do is to export the hbase tables to hdfs files?

https://github.com/hortonworks-spark/shc

Should be able to use sparklyr with something like this: https://therinspark.com/data.html#cassandra
But instead of connecting to Cassandra, you would use the Spark-HBase connector from Hortonworks: https://github.com/hortonworks-spark/shc
Something like the following might just work...
sc <- spark_connect(master = "local", version = "2.3", config = list(
  sparklyr.connect.packages = "com.hortonworks:shc-core:1.1.1-2.1-s_2.11",
  sparklyr.shell.repositories = "http://repo.hortonworks.com/content/groups/public/",
  sparklyr.shell.files = "/etc/hbase/conf/hbase-site.xml"))

spark_read_source(
  sc,
  name = "emp",
  source = "org.apache.spark.sql.execution.datasources.hbase",
  options = list(“HBaseTableCatalog.tableCatalog” = “<catalog>"),
  memory = FALSE)


Broken certificate renewal process on version 2.9

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I've let Traefik manage the certificate renewal process via ACME automatically, however this seems to be broken after the upgrade from version 2.8.8 to 2.9.5.
What did you see instead?
I've been observing issues in the log files with renewing the certificate. It seems that there is an unsupported DNS name ('\\100.') while generating the resource recordset configuration towards AWS Route 53, however the Traefik configuration hasn't changed at all.
After several attempts to find the root cause, I've ultimately downgraded Traefik to version 2.8, and immediately starts renewing the certificate successfully.
What version of Traefik are you using?
2.9.5
What is your environment & configuration?
      - "--certificatesresolvers.letsencrypt.acme.dnschallenge=true"
      - "--certificatesresolvers.letsencrypt.acme.dnschallenge.provider=route53"
      - "--certificatesresolvers.letsencrypt.acme.dnschallenge.delaybeforecheck=10"
      - "--certificatesresolvers.letsencrypt.acme.dnschallenge.resolvers=<IP_ADDRESS>:53,<IP_ADDRESS>:53"
      -<EMAIL_ADDRESS>      - "--certificatesresolvers.letsencrypt.acme.storage=/letsencrypt/acme.json"

      - "--entrypoints.websecure.address=:443"
      - "--entrypoints.websecure.http.tls.certresolver=letsencrypt"
      - "--entrypoints.websecure.http.tls.domains[0].main=services.notarealdomain.com"

If applicable, please paste the log output in DEBUG level
Unable to obtain ACME certificate for domains \"services.notarealdomain.com\"" routerName=sonarqube@docker rule="Host(`services.notarealdomain.com`) && (Path(`/codequality`) || PathPrefix(`/codequality/`))" providerName=letsencrypt.acme ACME CA="https://acme-v02.api.letsencrypt.org/directory" error="unable to generate a certificate for the domains [services.notarealdomain.com]: error: one or more domains had a problem:\n[services.notarealdomain.com] [services.notarealdomain.com] acme: error presenting token: route53: failed to change record set: InvalidChangeBatch: [RRSet with DNS name \\100. is not permitted in zone services.notarealdomain.com.]\n\tstatus code: 400, request id: ***\n

Hi @jbdoumenjou, thanks for the reply.
I was using a wildcard domain too indeed, but I've removed the wildcard domain out of the equation in order to find the root cause. Unfortunately with only a single, non-wildcard, domain it still doesn't work and yielded the error in the log excerpt in the issue report above.

Wildcard CNAME is not wildcard domain.
CNAME is a specific DNS record.
Have you a CNAME that redirects to another domain?

My mistake. No, I have no CNAME's on services.notarealdomain.com.
However I have some on the root domain notarealdomain.com, although I'm not requesting certificates on this root domain, solely on a subdomain (in this example services.notarealdomain.com).
The thing what strikes me the most is the fact that the logging seems to indicate that the update of the Route 53 Resource RecordSet contains a unknown DNS name i.e. RRSet with DNS name \\100. is not permitted in zone services.notarealdomain.com.

The \\100 is @ which would tend to be a clue of a wildcard CNAME issue.
Could you test with the last version of Traefik (v2.9.6)?
It embeds a more recent version of lego that adds an info log https://github.com/go-acme/lego/blob/master/challenge/dns01/dns_challenge.go#L208 that will help us to check that assumption.

Just to add my 2c.
I was in the process of trying to get Traefik set up using whatever is currently at tag v2.9 on Dockerhub (which would probably be here I guess? https://hub.docker.com/layers/library/traefik/v2.9/images/sha256-0f22b9ca5a3bacd50c43ca193e1970d825fe2320ffc6222fec1e2e81b9a23393?context=explore)
I was on a Raspberry Pi 2B.
The behaviour was weird. If I tail -f the log, it gets to the part about renewing certs and then CPU usage just rockets to 100% for the one core that traefik is running on, and stays there.
It still seemed to be working, the services were getting reverse-proxied, but no actual certificates were being gotten.
Rolling back to v2.8 seemed to resolve the issue. I haven't had the time to check for more recent tags (i.e. 2.9.6 as suggested) but I thought I'd mention in case anyone else sees something similar. Will report back later today.

can you try to set the env var LEGO_DISABLE_CNAME_SUPPORT to true?

can you try to set the env var LEGO_DISABLE_CNAME_SUPPORT to true?

Switching back to :v2.9 and with that environment variable, that seems to have solved the problem. Works for me now.
Thanks!

can you try to set the env var LEGO_DISABLE_CNAME_SUPPORT to true?

Switching back to :v2.9 and with that environment variable, that seems to have solved the problem. Works for me now. Thanks!

Update: It worked for the labels that I already had in place, but adding a new container (and new rule which would have made use of the wildcard domain that I have) caused the same breakage: traefik CPU usage spikes to 100% and doesn't manage to get a cert for the domain. Rolling back to 2.8 seems to do the trick.
I'll play around a bit more and see what does and doesn't break things.  But it's a pity that something which used to work now doesn't.


Add kafka stat library.

Fixes #
Proposed Changes

kafka_manager in separate module_utils file.
Add kafka stat library.

Hey,
Thank you for this PR, I really like it: splitting the lib in several modules is a great idea since the main one started to be huge. The addition of lag calculation is also a great feature.
Do you know how we can resolve the {"msg": "Could not find imported module support code for kafka_lib.  Looked for either generate_ssl_context.py or ssl_utils.py"} error?

Molecule problem resolved , I've override an ansible variable to define where molecule (ansible) can find module support code. (check .travais file)

lgmt

@StephenSorriaux?

Sorry, I was busy on other projects lately... I will review & test this before the end of the week.

After further testing I took the liberty to rewrite some lines and fix others, and also to add a test to check everything is running as expected. Thanks again for your time, I hope everything goes well on your side.

Many thanks Stephen for your improvements, it's now much robuste with python style


Disable telemetry in Development environment

Is there an official and easy way to disable AppInsights telemetry in Development environment?

Not that I'm aware of. I keep it on but use a Dev App Insights instance so that alerts don't trigger. Additionally, you could use an adblocker.

Quite from https://docs.microsoft.com/en-us/azure/azure-monitor/app/javascript#telemetry-initializers

The input argument to addTelemetryInitializer is a callback that takes a ITelemetryItem as an argument and returns a boolean or void. If returning false, the telemetry item isn't sent, else it proceeds to the next telemetry initializer, if any, or is sent to the telemetry collection endpoint.

Looks like telemetryInitializer may return false and disable telemetry.
We can add property to TelemetryItem, for example
public bool SendTelemetry {get; set} = true;

that control this behaviour during initialisation.
p.s. solution found on StackOverflow

This is now supported in v3.


OKD Installer workspace. Blank repo

There is an invalid link on the OKD Installer Workspace page which leads to an empty repository. Please correct it.
@GingerGeek @vrutkovs

@GingerGeek are you maintaining the workspace project anymore? If not, we'll remove the referencing page from the OKD documentation repo.
@valumar Please don't tag volunteers specifically on documentation issues. We need to share the responsibilities and make sure no particular person burns out. Thank you.


Short-term roadmap for this implementation

Previous discussion: https://github.com/apache/arrow-datafusion/issues/4707
Though the ORC format is not as widely used as parquet in arrow-rs and datafusion related projects, there are still some (growing, to my feelings) interesting and requirements on this format. As @Jefffrey said here, a noticeable and viable milestone for this project is it can be merged into arrow-rs. This draft roadmap is raised to help us discuss, arrange and take our efforts toward that milestone.
Given the ORC format is less complex than parquet, there are still many work to do in various aspects. Here is a list of functionalities need to be done if we consider making ORC files queriable from datafusion as the primary use case on this stage. Please feel free to add/remove/set priorities to them. It's likely that we can't finish all of them in a short term, thus marking what are going to be done is also important.

[ ] primitive data types
[ ] common compress methods
[ ] user metadata

And belows are also related but with lower priorities

[ ] encryption
[ ] compond data types
[ ] index

Then something I'm not sure about. Looking for more information. Also feel free to change previous two lists.

[ ] other encodings
[ ] file metadata and statistics

Thanks for writing this here.
Just to preface, I'm no expert in ORC nor do I technically have a usecase for it, so can take my thoughts with a grain of salt. With that said:

Encryption can probably be placed lowest priority, probably into the longer-term roadmap. Even parquet in arrow-rs doesn't yet support encryption
We can probably bump the encodings to highest priority. I assume you're referring to the V1 encodings, which should be simpler to implement than V2 which seems to already be present
I haven't looked into statistics and indexes much, but they do seem important for stuff like predicate pushdown, so can be medium priority or so

I'll create more issues based on this roadmap

BTW some potentially relevant documents in case anyone is interested:
A Deep Dive into Common Open Formats for Analytical
An Empirical Evaluation of Columnar Storage Formats

BTW some potentially relevant documents in case anyone is interested:
A Deep Dive into Common Open Formats for Analytical
An Empirical Evaluation of Columnar Storage Formats

Thanks for these, will definitely give a read!

What is missing from this roadmap which is required to allow this library be added to the datafusion (and arrow-rs, polars?)
I would be interested in helping with this effort as we have orc files which we would like to query.

hey @klangner thanks for the interest!
For DataFusion there is an issue for it: https://github.com/datafusion-contrib/datafusion-orc/issues/63
Right now it lacks support for projection, not to mention the code is sequestered in an example instead of being code as part of the library.
For arrow-rs it's basically just... all features needed for supporting read use cases (sorry if this is too vague :sweat_smile: )
I'm not familiar with polars so I can't say on that front.
For now I'm imagining enhancing the API for RecordBatch reading (akin to what parquet provides in arrow-rs) and also creating the necessary impl's to allow DataFusion to read from ORC files using this library.


Edit data in table after query --

Table should show what data set is being viewed/edit
Table should have a default sort order.
In multi-page tables, screen should show what page we are on ( 1 of 47 etc)
Sort should sort the ENTIRE table, not just the displayed page.

all complete


Sidebar header disappears with no sidebarContent prop

Describe the bug
With no sidebarContent the (left) sidebar header disappears and timeline header is misplaced.
To Reproduce
Provide no sidebarContent prop. Setting it to e.g. <div/> will solve the issue.
Screenshots

Library Version
0.20.0
Desktop (please complete the following information):

OS: macOS
Browser Chrome
Version 69.0

I have the same issue. Did you find a fix?

Nevermind. Re-read the comment. Thanks for the fix.

this will be fixed wuth #391


Support for handling all types of JavaScript Alerts

Is your feature request related to a problem?
The scenarios which have Alerts.
Description
Support for handling all types of JavaScript Alerts (Normal, Confirm and prompt).
Additional context
N/A

@MahmoudElSharkawy any hope for a PR to close this one? 😀

linked to #472


Add a #:string: parser

Would've been useful for fraya's DOT share: https://play.opendylan.org/shared/034b4318d2a01602

Obsoleted by multi-line string literal syntax.


another way of fit

I'm progressing on the way you suggested to modify the fit and M-step of the fit, but here is my suggestion.
I appended all the concentrations of lineages of a drug as a new population and fitted the model for 3 and 4 states (lapatinib and gemcitabine, respectively). This way I found the common transition and initial prob. matrices and used them as constant (list_of_fT and list_of_fpi) to find the emissions in populations of different concentrations.
The results make sense to me, but if you prefer that the BW part of the model to be modified, I will discard this and continue working on my other branch. @aarmey

The issue is that the emissions have to be concentration dependent. In this setup I’d bet that high concentrations just all end up as states that aren’t found at all in the control.

The emissions are concentration-dependent. I just calculated the T and pi and used it to fit those separate populations.
Or maybe I don't understand your point. Do you mean this way of calculating T and pi interferes with the way the emissions are calculated afterward?

But estimating T and pi requires estimating the emissions correctly for the same cells.

Oh... I see. Ok, thank you. I will resume working on the other branch.


audio preprocessing

Audio Preprocessing for Bird Call Extraction and Spectrogram Conversion
1. Bird Call Extraction
Goal:
🔸Isolation of the audio fragments from files that contain just the bird calls.
2. Zero Padding for Uniform Length
Goal:
🔸 Ensure all audio clips have a uniform length for model compatibility.
implementation: finding the longest call duration and apply zero padding for others to make them same length

why?
learning models like CNNs or RNNs, which expect inputs of fixed size

3. Spectrogram Conversion
Goal:
🔸Convert the processed audio clips into spectrograms for model input
Expected result:
🔸spectrograms of bird calls input with zero padding in .npy format in folder /data/preprocessed with exact names as a videofiles from which they was extracted.

The file has been uploaded to isolate the audio file using two parameters: start_cut and end_cut from the main.py file.

The padding with the zeros has been created. After creating the spectrogram values, they have been saved in the mentioned path with the name corresponding to the actual file name. They saved in *.npy file. The mentioned folder provide the example of the output data. The whole data of *.npy needs to be transfer via SSD ;)

From the file name main.py, all the parameters might be changed.


Revert "chromium: 45.0.2454.101 -> 46.0.2490.71"

This reverts commit 0ad0fbdf8aebeb01b10d71117eab7aaccbe01849.
See https://github.com/NixOS/nixpkgs/issues/10555

cc @wkennington @domenkozar

IMHO, it's good style to explain why the revert is needed (in the commit message).

@bjornfor: fixed, thanks.

@aszlig

Merging for now, hangouts are important feature for most of us.

Just note we are now vulnerable to multiple flash vulnerabilities and
potentially others.
On Thu, Oct 29, 2015 at 2:55 AM Domen Kožar<EMAIL_ADDRESS>wrote:

Merging for now, hangouts are important feature for most of us.
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/10562#issuecomment-152131790.

Didn't Chrome dump flash?

No, they dumped npapi but they bundle pepper flash as part of the chromium
release.
On Thu, Oct 29, 2015 at 9:27 AM obadz<EMAIL_ADDRESS>wrote:

Didn't Chrome dump flash?
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/10562#issuecomment-152235416.

Sigh. Do we have an upstream issue for hangouts?

@obadz: actually, I only use chromium for some flash stuff, as it's the only real way to get a recent version of flash on Linux. Some things do not work with the older one.

@domenkozar I put some upstream info here: https://github.com/NixOS/nixpkgs/issues/10555#issuecomment-152549786


',' expected.

app/app.component.ts(94,9): error TS1005: ',' expected.
app/app.component.ts(129,7): error TS1005: ',' expected.
app/app.component.ts(130,7): error TS1005: ',' expected.
Three lines are missing commas.

Hi John,
  Thanks for your review.  ',' added in app/app.component.ts


You are trying to call the setup function of Indent-blankline version 2 but you have version 3 installed

Describe the bug
The message "You are trying to call the setup function of Indent-blankline version 2 but you have version 3 installed" appears after adding the init file.
To Reproduce

Install Nvim
Add init file in nvim folder
open Nvim

Desktop

OS: Ubuntu(WSL)
Terminal:

Neovim Version

v0.9.2

see also https://github.com/nvim-lua/kickstart.nvim/pull/443
Probably better to make it work with V3 than to pin in to V2


PoE - Trade

🐞 bug report
Describe the bug
PoE - Trade isn't showing when people whispers me an offer, but when i send them an offer it appear normally.
To Reproduce

🌍  Your Environment

PoE: 3.11.0/e English

Somehow it began to work normally. Thank you.