text:
Smart socket only updating electrical stats at HomeAssistant if I keep my Tuya app opened

Describe the bug
Starting a few days ago, my Tuya-local managed smart socket only updates its electrical information (power consumption, current, voltage) into Home Assistant if I open the "Electric" tab for this device inside the Tuya App in my phone.
To Reproduce
No updates in power consumption, current, voltage in the last 10 minutes in Home Assistant.
At the moment I open the "Electric" tab in my Tuya app for this smart socket, values for these entities start updating every 5 seconds.
The updates stop again after closing the "Electric" tab.
Expected behavior
The socket should keep sending periodic updates, no matter if the "Electric" tab of the app is opened or not.
Additional context
Add any other context about the problem here.
If the bug involves a device, then please include device diagnostics from
Settings / Devices & Services / Tuya Local (your device) / "1 device"
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2024.7.0",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.12.4",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Madrid",
    "os_name": "Linux",
    "os_version": "6.6.28-haos-raspi",
    "supervisor": "2024.06.2",
    "host_os": "Home Assistant OS 12.3",
    "docker_version": "25.0.5",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "pvpc_hourly_pricing": {
      "documentation": "https://github.com/azogue/ha-pvpc-custom",
      "version": "1.2.1",
      "requirements": [
        "aiopvpc>=4.3.1"
      ]
    },
    "smartthinq_sensors": {
      "documentation": "https://github.com/ollo69/ha-smartthinq-sensors",
      "version": "0.39.2",
      "requirements": [
        "pycountry>=23.12.11",
        "xmltodict>=0.13.0",
        "charset_normalizer>=3.2.0"
      ]
    },
    "google_home": {
      "documentation": "https://github.com/leikoilja/ha-google-home",
      "version": "1.11.1",
      "requirements": [
        "glocaltokens==0.7.1"
      ]
    },
    "asterisk": {
      "documentation": "https://github.com/TECH7Fox/Asterisk-integration",
      "version": "1.0.4",
      "requirements": [
        "asterisk-ami==0.1.6"
      ]
    },
    "battery_notes": {
      "documentation": "https://andrew-codechimp.github.io/HA-Battery-Notes/",
      "version": "2.3.9",
      "requirements": []
    },
    "tplink_easy_smart": {
      "documentation": "https://github.com/vmakeev/tplink_easy_smart",
      "version": "0.3.0",
      "requirements": [
        "json5==0.9.10"
      ]
    },
    "tuya_local": {
      "documentation": "https://github.com/make-all/tuya-local",
      "version": "2024.6.0",
      "requirements": [
        "tinytuya==1.14.0",
        "tuya-device-sharing-sdk==0.1.9"
      ]
    },
    "watchman": {
      "documentation": "https://github.com/dummylabs/thewatchman",
      "version": "0.6.3",
      "requirements": [
        "prettytable==3.10.0"
      ]
    },
    "browser_mod": {
      "documentation": "https://github.com/thomasloven/hass-browser_mod/blob/master/README.md",
      "version": "2.3.0",
      "requirements": []
    },
    "hacs": {
      "documentation": "https://hacs.xyz/docs/configuration/start",
      "version": "1.34.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "mass": {
      "documentation": "https://music-assistant.io",
      "version": "2024.6.2",
      "requirements": [
        "music-assistant==2.0.6"
      ]
    },
    "midea_dehumidifier_lan": {
      "documentation": "https://github.com/nbogojevic/homeassistant-midea-air-appliances-lan/blob/main/README.md",
      "version": "0.9.4",
      "requirements": [
        "midea-beautiful-air==0.10.5"
      ]
    },
    "powercalc": {
      "documentation": "https://github.com/bramstroker/homeassistant-powercalc",
      "version": "v1.12.13",
      "requirements": [
        "numpy>=1.21.1"
      ]
    },
    "tapo_control": {
      "documentation": "https://github.com/JurajNyiri/HomeAssistant-Tapo-Control",
      "version": "5.4.26",
      "requirements": [
        "pytapo==3.3.23"
      ]
    },
    "custom_templates": {
      "documentation": "https://github.com/PiotrMachowski/Home-Assistant-custom-components-Custom-Templates",
      "version": "v1.4.0",
      "requirements": []
    },
    "presence_simulation": {
      "documentation": "https://github.com/slashback100/presence_simulation",
      "version": "4.8",
      "requirements": []
    },
    "balance_neto": {
      "documentation": "https://github.com/MiguelAngelLV/balance_neto",
      "version": "0.1.0",
      "requirements": []
    },
    "edge_tts": {
      "documentation": "https://github.com/hasscc/hass-edge-tts",
      "version": "0.0.1",
      "requirements": [
        "edge-tts==6.1.12"
      ]
    },
    "bodymiscale": {
      "documentation": "https://github.com/dckiller51/bodymiscale",
      "version": "2024.6.0",
      "requirements": [
        "cachetools==5.3.0"
      ]
    },
    "reversotts": {
      "documentation": "https://github.com/rt400/ReversoTTS-HA",
      "version": "1.0.2",
      "requirements": [
        "pyttsreverso==0.4"
      ]
    },
    "localtuya": {
      "documentation": "https://github.com/rospogrigio/localtuya/",
      "version": "5.2.1",
      "requirements": []
    },
    "tplink_deco": {
      "documentation": "https://github.com/amosyuen/ha-tplink-deco",
      "version": "3.6.2",
      "requirements": [
        "pycryptodome>=3.12.0"
      ]
    },
    "multiscrape": {
      "documentation": "https://github.com/danieldotnl/ha-multiscrape",
      "version": "7.0.0",
      "requirements": [
        "lxml>=4.9.1",
        "beautifulsoup4>=4.12.2"
      ]
    },
    "fontawesome": {
      "documentation": "https://github.com/thomasloven/hass-fontawesome",
      "version": "2.2.1",
      "requirements": []
    },
    "favicon": {
      "documentation": "https://github.com/thomasloven/hass-favicon",
      "version": "10.4",
      "requirements": []
    },
    "meross_lan": {
      "documentation": "https://github.com/krahabb/meross_lan",
      "version": "5.2.2",
      "requirements": []
    },
    "google_photos": {
      "documentation": "https://github.com/daanoz/ha-google-photos",
      "version": "v0.6.3",
      "requirements": [
        "google-api-python-client>=2.71.0",
        "pillow"
      ]
    },
    "frigate": {
      "documentation": "https://github.com/blakeblackshear/frigate",
      "version": "5.2.0",
      "requirements": [
        "pytz"
      ]
    },
    "gas_station_spain": {
      "documentation": "https://github.com/MiguelAngelLV/gas_station_spain",
      "version": "0.8.0",
      "requirements": []
    },
    "scheduler": {
      "documentation": "https://github.com/nielsfaber/scheduler-component",
      "version": "v0.0.0",
      "requirements": []
    },
    "ble_monitor": {
      "documentation": "https://github.com/custom-components/ble_monitor",
      "version": "12.12.1",
      "requirements": [
        "pycryptodomex>=3.19.1",
        "janus>=1.0.0",
        "aioblescan>=0.2.14",
        "btsocket>=0.2.0",
        "pyric>=0.1.6.3"
      ]
    },
    "tuya_ble": {
      "documentation": "https://www.home-assistant.io/integrations/tuya_ble",
      "version": "0.1.8",
      "requirements": [
        "tuya-iot-py-sdk==0.6.6",
        "pycountry>=22.3.5"
      ]
    },
    "ideenergy": {
      "documentation": "https://github.com/ldotlopez/ha-ideenergy",
      "version": "2.1.2",
      "requirements": [
        "ideenergy>=2.0.0rc1",
        "homeassistant-historical-sensor==2.0.0rc5"
      ]
    },
    "sonoff": {
      "documentation": "https://github.com/AlexxIT/SonoffLAN",
      "version": "3.7.3",
      "requirements": [
        "pycryptodome>=3.6.6"
      ]
    },
    "chime_tts": {
      "documentation": "https://nimroddolev.github.io/chime_tts",
      "version": "v1.1.3",
      "requirements": [
        "pydub"
      ]
    },
    "wasp_sensor": {
      "documentation": "https://github.com/dlashua/hass-wasp_sensor",
      "version": "0.0.3",
      "requirements": []
    },
    "goodwe": {
      "documentation": "https://github.com/mletenay/home-assistant-goodwe-inverter",
      "version": "0.9.9.27",
      "requirements": [
        "goodwe==0.4.7"
      ]
    },
    "open_epaper_link": {
      "documentation": "https://github.com/jonasniesner/open_epaper_link_homeassistant",
      "version": "0.1.4",
      "requirements": [
        "qrcode[pil]==7.4.2",
        "requests_toolbelt==1.0.0",
        "websocket-client==1.7.0"
      ]
    }
  },
  "integration_manifest": {
    "domain": "tuya_local",
    "name": "Tuya Local",
    "codeowners": [
      "make-all"
    ],
    "config_flow": true,
    "dependencies": [],
    "documentation": "https://github.com/make-all/tuya-local",
    "integration_type": "device",
    "iot_class": "local_push",
    "issue_tracker": "https://github.com/make-all/tuya-local/issues",
    "requirements": [
      "tinytuya==1.14.0",
      "tuya-device-sharing-sdk==0.1.9"
    ],
    "version": "2024.6.0",
    "is_built_in": false
  },
  "setup_times": {
    "null": {
      "setup": 7.914700000810626e-05
    },
    "2285ed40190af80003d7e363957d39bd": {
      "wait_import_platforms": -5.404931796999989,
      "config_entry_setup": 10.013534222000004
    }
  },
  "data": {
    "name": "Enchufe lavadora",
    "type": "smartplugv2_energy",
    "device_id": "**REDACTED**",
    "device_cid": "",
    "local_key": "**REDACTED**",
    "host": "**REDACTED**",
    "protocol_version": 3.3,
    "tinytuya_version": "1.14.0",
    "api_version_set": 3.3,
    "api_version_used": 3.3,
    "api_working": true,
    "status": {},
    "cached_state": {
      "updated_at": 1720418970.4496028,
      "1": true,
      "9": 0,
      "18": 530,
      "19": 824,
      "20": 2397,
      "21": 1,
      "22": 533,
      "23": 27459,
      "24": 14742,
      "25": 1416
    },
    "pending_state": {},
    "connected": true,
    "force_dps": [],
    "home_assistant": {
      "name": "Enchufe lavadora",
      "name_by_user": null,
      "disabled": false,
      "disabled_by": null,
      "entities": [
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": "problem",
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "binary_sensor.enchufe_lavadora_error",
            "state": "off",
            "attributes": {
              "device_class": "problem",
              "friendly_name": "Enchufe lavadora"
            },
            "last_changed": "2024-07-07T20:44:06.683831+00:00",
            "last_reported": "2024-07-07T20:45:00.920205+00:00",
            "last_updated": "2024-07-07T20:44:06.683831+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": "min",
          "state": {
            "entity_id": "number.enchufe_lavadora_timer",
            "state": "0.0",
            "attributes": {
              "min": 0.0,
              "max": 1440.0,
              "step": 1.0,
              "mode": "auto",
              "unit_of_measurement": "min",
              "friendly_name": "Enchufe lavadora Temporizador"
            },
            "last_changed": "2024-07-07T20:44:06.692905+00:00",
            "last_reported": "2024-07-07T20:45:00.943740+00:00",
            "last_updated": "2024-07-07T20:44:06.692905+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": null,
          "device_class": null,
          "original_device_class": "outlet",
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "switch.enchufe_lavadora",
            "state": "on",
            "attributes": {
              "test_bit": 1,
              "device_class": "outlet",
              "friendly_name": "Enchufe lavadora"
            },
            "last_changed": "2024-07-07T20:44:06.683196+00:00",
            "last_reported": "2024-07-07T20:45:00.914537+00:00",
            "last_updated": "2024-07-07T20:44:06.683196+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "switch.enchufe_lavadora_overcharge_cutoff",
            "state": "unknown",
            "attributes": {
              "icon": "mdi:battery-charging",
              "friendly_name": "Enchufe lavadora Overcharge cutoff"
            },
            "last_changed": "2024-07-07T20:44:06.683527+00:00",
            "last_reported": "2024-07-07T20:45:00.919755+00:00",
            "last_updated": "2024-07-07T20:44:06.683527+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "lock.enchufe_lavadora_child_lock",
            "state": "unknown",
            "attributes": {
              "friendly_name": "Enchufe lavadora Bloqueo infantil",
              "supported_features": 0
            },
            "last_changed": "2024-07-07T20:44:06.673063+00:00",
            "last_reported": "2024-07-07T20:45:00.910264+00:00",
            "last_updated": "2024-07-07T20:44:06.673063+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "select.enchufe_lavadora_initial_state",
            "state": "unknown",
            "attributes": {
              "options": [
                "On",
                "Off",
                "Last State"
              ],
              "icon": "mdi:toggle-switch",
              "friendly_name": "Enchufe lavadora Initial state"
            },
            "last_changed": "2024-07-07T20:44:06.673431+00:00",
            "last_reported": "2024-07-07T20:45:00.910627+00:00",
            "last_updated": "2024-07-07T20:44:06.673431+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "select.enchufe_lavadora_light",
            "state": "unknown",
            "attributes": {
              "options": [
                "State",
                "Position",
                "Off",
                "On"
              ],
              "icon": "mdi:circle-double",
              "friendly_name": "Enchufe lavadora Light"
            },
            "last_changed": "2024-07-07T20:44:06.680609+00:00",
            "last_reported": "2024-07-07T20:45:00.910892+00:00",
            "last_updated": "2024-07-07T20:44:06.680609+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": "Wh",
          "state": {
            "entity_id": "sensor.enchufe_lavadora_energy",
            "state": "unknown",
            "attributes": {
              "calibration": 1416,
              "unit_of_measurement": "Wh",
              "friendly_name": "Enchufe lavadora Energy"
            },
            "last_changed": "2024-07-07T20:44:06.684293+00:00",
            "last_reported": "2024-07-07T20:45:00.920636+00:00",
            "last_updated": "2024-07-07T20:44:06.684293+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": "current",
          "icon": null,
          "unit_of_measurement": "mA",
          "state": {
            "entity_id": "sensor.enchufe_lavadora_intensidad_de_corriente_2",
            "state": "530",
            "attributes": {
              "state_class": "measurement",
              "calibration": 27459,
              "unit_of_measurement": "mA",
              "device_class": "current",
              "friendly_name": "Enchufe lavadora"
            },
            "last_changed": "2024-07-08T06:08:01.757896+00:00",
            "last_reported": "2024-07-08T06:08:01.757896+00:00",
            "last_updated": "2024-07-08T06:08:01.757896+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": "voltage",
          "icon": null,
          "unit_of_measurement": "V",
          "state": {
            "entity_id": "sensor.enchufe_lavadora_voltaje_2",
            "state": "239.7",
            "attributes": {
              "state_class": "measurement",
              "calibration": 533,
              "unit_of_measurement": "V",
              "device_class": "voltage",
              "friendly_name": "Enchufe lavadora"
            },
            "last_changed": "2024-07-08T06:07:56.752345+00:00",
            "last_reported": "2024-07-08T06:08:01.760736+00:00",
            "last_updated": "2024-07-08T06:07:56.752345+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": "power",
          "icon": null,
          "unit_of_measurement": "W",
          "state": {
            "entity_id": "sensor.enchufe_lavadora_consumo",
            "state": "82.4",
            "attributes": {
              "state_class": "measurement",
              "calibration": 14742,
              "unit_of_measurement": "W",
              "device_class": "power",
              "friendly_name": "Enchufe lavadora"
            },
            "last_changed": "2024-07-08T06:08:01.759099+00:00",
            "last_reported": "2024-07-08T06:08:01.759099+00:00",
            "last_updated": "2024-07-08T06:08:01.759099+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": null,
          "device_class": null,
          "original_device_class": "energy",
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "sensor.lavadora_energy_counter",
            "state": "38.41",
            "attributes": {
              "state_class": "total_increasing",
              "status": "collecting",
              "last_period": "0",
              "last_valid_state": "38.41",
              "last_reset": "2022-12-22T06:32:26.381604+00:00",
              "unit_of_measurement": "kWh",
              "device_class": "energy",
              "friendly_name": "LAVADORA Energy Counter"
            },
            "last_changed": "2024-07-08T06:05:30.373712+00:00",
            "last_reported": "2024-07-08T06:05:30.373712+00:00",
            "last_updated": "2024-07-08T06:05:30.373712+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": null,
          "device_class": null,
          "original_device_class": "energy",
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "sensor.lavadora_energy",
            "state": "38.41",
            "attributes": {
              "state_class": "total",
              "source": "sensor.enchufe_lavadora_consumo",
              "unit_of_measurement": "kWh",
              "device_class": "energy",
              "friendly_name": "LAVADORA Energy"
            },
            "last_changed": "2024-07-08T06:05:30.373452+00:00",
            "last_reported": "2024-07-08T06:05:30.493219+00:00",
            "last_updated": "2024-07-08T06:05:30.373452+00:00"
          }
        }
      ]
    }
  }
}

Please check if there are messages from Tuya Local in the Home
Assistant log (Settings / System / Logs), and include those too.
Detected blocking call to open with args ('/config/custom_components/tuya_local/devices/smartplugv2_energy.yaml',) inside the event loop by custom integration 'tuya_local' at custom_components/tuya_local/helpers/device_config.py, line 101: self._config = load_yaml(filename) (offender: /usr/src/homeassistant/homeassistant/util/yaml/loader.py, line 226: with open(fname, encoding="utf-8") as conf_file:), please create a bug report at https://github.com/make-all/tuya-local/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/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/http/decorators.py", line 81, in with_admin return await func(self, request, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 262, in post return await super().post(request) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper return await method(view, request, data, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 77, in post return await self._post_impl(request, data) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl result = await self._flow_mgr.async_init( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 343, in async_init result = await self._async_handle_step(flow, flow.init_step, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 518, in _async_handle_step result: _FlowResultT = await getattr(flow, method)(user_input) File "/config/custom_components/tuya_local/config_flow.py", line 548, in async_step_init return await self.async_step_user(user_input) File "/config/custom_components/tuya_local/config_flow.py", line 581, in async_step_user cfg = get_config(config[CONF_TYPE]) File "/config/custom_components/tuya_local/helpers/device_config.py", line 998, in get_config return TuyaDeviceConfig(fname) File "/config/custom_components/tuya_local/helpers/device_config.py", line 101, in __init__ self._config = load_yaml(filename)

If applicable, add screenshots to help explain your problem.

This is a common behaviour of Tuya smart sockets, not a bug in the integration.

Maybe I don't know if this is a bug or not, but until a few days ago this was fully working (receiving local data every 5 seconds or so).
And since then the automations I had with this integration became totally useless. I've had to replace my locally-controlled Tuya smart plug with another one.

Nothing changed in the integration in the past few days.  Did the device's firmware update?

No. No firmware updates in the plug.
If somehow I was enjoying a non-standard behaviour, that got cancelled (maybe from Tuya cloud), in that case maybe the integration could send some kind of message to the smartplug so it enters in the state to report data every X seconds...

authors: davefx make-all

repo: make-all/tuya-local


text:
Using with react container components  ?

I'm using react-redux connect for isolating view component and state management.
Can any one suggest me the best way to handle use that along with @asyncConnect ?

use asyncConnect instead of connect whenever you need your container to have async state resolved on SSR, besides that nothing changes. Make sure your container is resolved after react-router's match

If I no need to use connect then what is the alternate for mapStateToProps and mapDispatchToProps ?

https://github.com/makeomatic/redux-connect/blob/master/modules/containers/decorator.js#L41-L50

Ho I'm sorry I haven't found this doc before https://github.com/makeomatic/redux-connect/blob/master/docs/API.MD Now I'm reading it.

@sagar12861 Here's a basic example that might be useful for you: https://github.com/LaborWorks/react-redux-training/blob/master/04-redux-todolist-typescript/src/app/containers/TodoList/index.tsx

Thanks @AVVS and @altayaydemir I'm able to understand and working now.

source: gharchive/issue

authors: AVVS altayaydemir sagar12861 sagarrayudu

repo: makeomatic/redux-connect

license: mit

license_type: permissive

license_source: bigquery


text:
Align the Any base to any base convertor

Describe the bug
Currently, the 'Any base to any base convertor' is in the top left corner of the screen. Align it to the center of the screen.

Hey, Can you please help me in finding the 'any base to any base calculator' that is located in which part?

It's in Binary section

you need to put it in the center?
On Tue, 10 Aug 2021 at 13:17, Rizwan Shaikh @.***>
wrote:

It's in Binary section
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/makesmatheasy/makesmatheasy/issues/5381#issuecomment-895808049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALU5M4RSQICPGT5L4Z62GOTT4DKPRANCNFSM5AS6NKEQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Please assign it to me.

Go ahead. Make sure that you submit the PR by end of date for it to be considered for LGMSoC.

What is the end date for LGMSoC?

Hey, Rizwan is this okay, or totally need to be in the center?
On Tue, 10 Aug 2021 at 13:31, Sumit Singh @.***> wrote:

you need to put it in the center?
On Tue, 10 Aug 2021 at 13:17, Rizwan Shaikh @.***>
wrote:

It's in Binary section
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/makesmatheasy/makesmatheasy/issues/5381#issuecomment-895808049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALU5M4RSQICPGT5L4Z62GOTT4DKPRANCNFSM5AS6NKEQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Please check the mail where I sent you the screenshot.

Check this too.
On Tue, 10 Aug 2021 at 15:02, Sumit Singh @.***> wrote:

Hey, Rizwan is this okay, or totally need to be in the center?
On Tue, 10 Aug 2021 at 13:31, Sumit Singh @.***> wrote:

you need to put it in the center?
On Tue, 10 Aug 2021 at 13:17, Rizwan Shaikh @.***>
wrote:

It's in Binary section
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/makesmatheasy/makesmatheasy/issues/5381#issuecomment-895808049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALU5M4RSQICPGT5L4Z62GOTT4DKPRANCNFSM5AS6NKEQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Please make a PR with the relevant changes so that the team can review and suggest the necessary changes.

authors: Rizwan-S Sin-Sumit

repo: makesmatheasy/makesmatheasy

license: MIT

license_source: github-api


text:
Show steps for calculation of Joint Probability

Is your feature request related to a problem? Please describe.

Showing steps for calculation of Joint Probability

Describe the solution you'd like

Adding required functionality to code base

Kindly assign this issue to me @sairish2001

Go ahead
Deadline 10 April,2021 11:59 PM IST

Can i work on this @sairish2001  ?

@sairish2001 ?


text:
Image output still same when running Nodejs

I have same output remove from first session, but when I restart my NPM script, it will read the new file like normally

This problem has fixed when I'm using different naming for the file

repo: makifoxgirl/rembg-node


text:
Interact with uuid4

Today your plugin interact t with uuid4 "3dbc2fbb-676d-4d10-ae09-4d9c7c960560".
I think it is not the goal but I like and use it.
But: The color is coming from The 6 first characters (of course you are looking for color codes).
The requested feature:
Generate a color from an uuid4 string considering the entire string (by computing a hash of the string for sample)
In more general way,
The plugin would interact with any pattern that match a custom regex, and a the color will be generated from hash computation of the matched string.

I have this kind of behavior too : one of my values is "dead"
the pattern "xxxx" matches and it is lightened with teal blue !! so weird
that don't carry any sense, more over later in the code "dead" is associated to dark red components ...
It could be nice to be able to modify the regex (one or more)

repo: mallowigi/color-highlighter


text:
Add 'clear all' group action

Allows easy clearing of the delegate list:

Actions (clear all)

[x] Tested on macOS
[x] State is saved when the application is restarted

Hey @meme ,
Thanks for the contribution! This looks all good to go, though I might fiddle around with the styling. As for the coding style, don't worry about it - that's something that I should work on when I have some time. Thank you for helping out with Fair Chair!

source: gharchive/pull-request


text:
prevent overwriting existing versions on dockerhub

I had to make the experience that an image build where we had based from (tagged) 0.19.1 started to fail later, because the image on dockerhub with that tag changed.
I haven't checked whether you have now already checks in place, but in case not, I would like to encourage you to never "move" tags of versions, with "latest" being the exception.

Hi @C-nit . Thank you for you interest in micromamba.
I'd suggest you use sha image digests in your Dockerfile FROM line instead of tags. This is generally considered a best practice and is recommended in our documentation.
The change you are requesting would require a significant change in our development model. Currently we allow updates to the main branch of this repo independent of the micromamba executable release schedule. The requested change would require only releasing changes to the image when a new version of the micromamba executable is released.  I'm open to moving to such a development model in the future, but it might be awhile until I get around to implementing the required changes.

@C-nit, while not cryptographically guaranteed to be immutable like SHA digests, we expect the Git-based Docker tags should in theory never change.

Now that micromamba has reached v1.0, I will be aiming to only commit changes to the image build process when new major or minor versions of the micromamba program are released. This change was implemented for the v1.3.0 release of micromamba, where I reworked the build to support alpine linux. The changes for alpine and the addition of an alpine-based image were merged along with the bump to v1.3.0 of micromamba.
However, I want to be clear that this project will continue to use 'rolling tags' so that we can incorporate upstream security fixes from the base images we build on top of.  If you want to ensure that you will always get the exact same image, you should use SHA digests or one of our tags containing "git".

@wholtz, how will the release workflow work now? Will we wait for the next micromamba release before merging non-critical PRs into main? Should we remove https://github.com/mamba-org/micromamba-docker/blob/6aa1f7c707562edb9f8dc9005d12cf6a39e8f0b4/.github/workflows/push_latest.yml#L5-L7
so that merging doesn't automatically trigger a rebuild?

Changes that can still use the old workflow:

bumping versions of existing base images
removing a base image that is no longer supported
documentation enhancements
testing changes
security updates

For everything else, we now have a dev branch,  which is protected. New work should start as new branches off dev and then generate PRs to merge into dev.  When a new micromamba version comes out, I'll run update.sh to bump the version numbers on dev and then merge dev into main.
While documentation enhancements can go through the old workflow, documentation for new features should be committed to dev along with the code for the feature.
As always, let me know if you have feedback @maresb.
I'll work on getting this info into the Development section of the README.md.

authors: C-nit maresb wholtz

repo: mamba-org/micromamba-docker


text:
start the app

Hi,
The app does not work for me, I have this :

Nothing happens when pressing the two buttons "elecronjs.org" and "local.html"
Can you help me to make it work
thanks

Thank you for your report. I had the same issue when running on Windows 10. After resizing the window, the content was displayed. I'll look it up.

Thank you for your reply, it actually works by resizing the window...

@Devhercule
Fixed on #3

authors: Devhercule kondoumh


text:
runit: add sys/select.h patch

this patch is to be included until upstream picks up on it in the mailing list

Thank you for the PR. Let's see if this patch is merged upstream.

authors: ArsenArsen avdgrinten

repo: managarm/bootstrap-managarm


text:
Track VSCode issue with JDK 13

https://github.com/redhat-developer/vscode-java/issues/1073

More relevant links:

https://github.com/microsoft/vscode-java-debug/issues/681
https://github.com/junit-team/junit5/issues/1906

repo: manastalukdar/learning-computer-science


text:
time/span: add / and * methods

Allows you to multiplay and divide a Time::Span by a number.

In which scenario you'd need to multiply or divide a time span?

I struggled first too, but I can see it's useful. Let's say you're splitting or merging video files for example, you have the duration and need the duration of the target (for display or whatever).
snippet_duration = duration / pieces

I for one multiply time spans in code (have my own implementation still, but soon it might be ditchable :) )

I added this in part to make it more compatible with Ruby because Ruby treats times like raw numbers.
x = Time.now
sleep 4
y = Time.now
diff = y - x #=> A float representing the number of seconds between y and x, so approx 4
diff * 2     # Just regular arithmetic

I added the versions that don't take arguments following the example of addition and subtraction, but I'm not sure we need them. Why are they there for addition and subtraction?

The "addition" and "substraction" overloads are actually the prefix operators, +@ and -@ in Ruby respectively. They get called when you do a = +duration or a = -duration for example.

Oh cool. So they're unnecessary for multiplication/division?

Since @asterite didn't respond with any counter arguments, let's add this.

authors: asterite jbaum98 jhass ozra

repo: manastech/crystal


text:
Create StateSpace.scala

added breeze mcmc using markov chain

Current coverage is 0.00% (diff: 100%)

Merging #46 into master will not change coverage

@@           master   #46   diff @@
===================================
  Files         127   127
  Lines         135   135
  Methods         0     0
  Messages        0     0
  Branches        2     2
===================================
  Hits            0     0
  Misses        135   135
  Partials        0     0

Powered by Codecov. Last update 78f3dff...1ab8a02


text:
🛑 crackrepack is down

In 28e0677, crackrepack (https://www.crackrepack.xyz/) was down:

HTTP code: 429
Response time: 603 ms

Resolved: crackrepack is back up in 9253548 after 50 minutes.


text:
[Bug]: Error Occurred While Predicting on AgroTech AI

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When uploading an image for sugarcane disease recognition, the system fails to provide predictions. Instead, an error message saying "An error occurred while predicting" is shown in a popup. This issue prevents the user from obtaining any disease diagnosis for the uploaded image.
Expected behavior

After uploading a sugarcane plant image, the system should analyze the image and return potential disease predictions.
If the image doesn't meet the required criteria, the user should receive a clear validation message such as: "Invalid image format" or "No disease detected."

Add ScreenShots

On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

hi @shreyasparaj we havent deployed backend yet..we are already workinig on it

authors: manikumarreddyu shreyasparaj

repo: manikumarreddyu/AgroTech-AI


text:
Creating a DOM tree is missing XML declaration

Any XML declaration gets lost when parsing XML. Also, a ROOT type node is never created when using
the DOM handler.
As I understand it, the first tree node should be of type ROOT and when present should have the XML declaration as a child node under the DECL type. The first start element would then be the second child.
This is easy to fix in xmlhandler/dom.lua in the function dom:decl() by adding:
if self.root == nil then
self.root = self.current
end
before or after the table.insert.
On reflection, I think it is even better to always have a ROOT node in the DOM handler, so that top-level comments are also preserved as its children. This can be achieved by setting root=curent in the init() function.

I've seen https://github.com/manoelcampos/xml2lua/compare/master...Tekenlight:xml2lua:master which may be a similar fix.

yes, I've noticed that at well. Also any DTD node is lost with the DOM handler.
I've fixed that in my branch https://github.com/doj/xml2lua/tree/dom-fixes where I do create a ROOT node, which would contain the DECL node, DTD node and the root ELEMENT node.

Hello guys. I'm not being able to maintain this project and I'm looking for a maintainer that can take over it.

authors: doj geert56 manoelcampos


text:
Feature: add a loader for next and submit action

Ref:
https://github.com/manojadams/mui-forms/issues/93

Tested with 4.0.6

repo: manojadams/metaforms-core


text:
Fix aggs and expressions in SearchRequest

Edit: After further testing, it turns out, that some types (i tried to use) are incorrect - here are failing test cases:
describe('Search Api Tests', () => {
  it('should aggregate by field', async function () {
    try {
      const query: Manticoresearch.SearchRequest = {
        index: 'test',
        query: {
          match_all: {},
        },
        aggs: [
          {
            name: 'cat',
            field: 'cat',
          },
        ],
      };

      const result = await searchApi.search(query);
      expect(result).to.deep.nested.property('hits.total', 5);
    } catch (err) {
      const errorResponse = err instanceof Manticoresearch.ResponseError ? await err.response.json() : err;
      console.error('Error response:', JSON.stringify(errorResponse, null, 2));
      expect(err).to.be.null;
    }
  });
});

which results in this error on manticoresearch 6.2.12:
{
      "total": 0,
      "warning": "",
      "error": "\"aggs\" property should be an object\""
}

According to the documentation, the schema should look like this instead:
"aggs": {
    "group name" : {
        "terms" : {
            "field":"attribute name",
            "size": 1000
      },
      "sort": [ {"attribute name": { "order":"asc" }} ]
  }
}

cc @sanikolaev - is there a documentation for the complete json-api schema?
While creating these test cases i've also stumbled upon some issues (or at least "you have to know"s) when migrating from the javascript library:
utilsApi.sql('drop table if exists test');

works in the javascript library, but throws this error in typescript:
{
  "error": "only SELECT queries are supported"
}

because the rawResponse option defaults to true in javascript, but false in typescript.
I'd be happy to contribute to this library (e.g. creating a PR with the updated types for aggs and expressions and updating the test cases) but there seems to be a lot of things not being right yet. The PR #2 of @mannol tidies up some things though.
Let me know what are your thoughts on this, if you accept PRs and how to contribute.
I want to order a facet result by the document counts to get my "most used buckets" like its described here: https://manual.manticoresearch.com/Searching/Faceted_search#Ordering-in-facet-result
Currently the Aggregation-Type only has name, field and size.

cc @sanikolaev - is there a documentation for the complete json-api schema?

Please see https://manual.manticoresearch.com/Openapi#OpenAPI-specification

Let me know what are your thoughts on this

Calling @Nick-S-2018 to advise on this.

I'd be happy to contribute to this library (e.g. creating a PR with the updated types for aggs and expressions and updating the test cases) but there seems to be a lot of things not being right yet. The PR https://github.com/manticoresoftware/manticoresearch-typescript/pull/2 of @mannol tidies up some things though.

Sure thing we accept PRs. Any contribution will be highly appreciated.

Thanks @sanikolaev for pointing to the OpenAPI specs which actually pointed me to the whole OpenAPI-based client generation repo (https://github.com/manticoresoftware/openapi) - so PRs should probably go there?!
anyway, it seems the OpenAPI spec itself is incorrect, specifying aggs and expressions as an array:
https://github.com/manticoresoftware/openapi/blob/master/manticore.yml#L625-L632

so PRs should probably go there?!

Yes.

anyway, it seems the OpenAPI spec itself is incorrect, specifying aggs and expressions as an array:

I'll check with the team on this.

authors: sanikolaev schwarmco


text:
Speedup twice orderByDistance

Speed up 'orderByDistance' function, tested on 10k spots :
from Requests per second:    3.16 [#/sec]
to Requests per second:    5.39 [#/sec]

I was doing Object.create for a some good reason here :wink:
First of all - the main reason is your version modifies existing arrays of coord objects while the existing solution creates a copy of each coordinate, without modifying existing coordinate objects, which might otherwise lead to some unwanted side effects.
Second reason is, coords[coord] is not necessarily a coordinate object. I allowed [longitude, latitude] as coordinate format some time ago to make working with GeoJSON coordinates easier. So setting a distance and a key property on an array is technically possible but not the most elegant solution :simple_smile:

Thx for you super fast response. You have right! but maybe this speed up is worth is risk.
Adiitionaly this risk can be mitigate by let`s say more uniq name for key and distance eg: __key or __distance

You might be right. I'm currently working on Geolib v3. Maybe I will introduce it as breaking change. Definitely worth a try. Thanks!

Also consider use a https://github.com/mourner/rbush-knn or implement own.
It give such big performance improvement for my case
up to Requests per second: 700.10 [#/sec]

This function will be rewritten from the ground up in v3 which I will release shorty. So I'm closing this one!

repo: manuelbieh/Geolib


text:
🛑 Manuel Deutsch is down

In 5220470, Manuel Deutsch (https://www.manuel-deutsch.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Manuel Deutsch is back up in 21c7243 after 6 minutes.

repo: manueldeutsch/upptime


text:
migrate to Swift 2.0

@harlanhaskins took a stab at this in https://github.com/mapbox/MapboxDirections.swift/pull/7, which also per #6 gets rid of SwiftyJSON, which I think is ok.
We should review that PR and/or otherwise migrate to Swift 2.0.

Separated this out into removing SwiftyJSON in https://github.com/mapbox/MapboxDirections.swift/commit/9c2194eb4f5b9343db2bcb53b5ad066fdd8ff304 and moving to Swift 2.0 in https://github.com/mapbox/MapboxDirections.swift/commit/f836dc10026214b60569b8b4d63483cd225779c3 for easier tracking/possible reversion.

license: ISC


text:
bump maki version to newest release

:bulb:

@flippmoke Can you take a look at the failing Travis test here? It's looking like maybe something related to whatever version of Mapnik this project is using.

This looks like a problem related to installing two different versions of mapnik at the same time.
blend@1.0.2
│ └─┬ mapnik@3.2.0
Blend is pulling in a different version.

@flippmoke how to resolve?

Resolved this issue with https://github.com/mapbox/node-blend/pull/60. Merging.

authors: flippmoke lyzidiamond

repo: mapbox/makizushi


text:
Add automated resource loading of icon-images

See https://github.com/mapbox/mapbox-plugins-android/pull/1000#issuecomment-506776713 and @fabian-guerra's subsequent comment.
Because we use a delegate method to handle this we'd need to either:

add an object that can intercept and forward delegate methods
or add hooks to the SDK (either at the core or iOS level) that an extension could use to provide this behavior.

I favor the latter - and this could be considered as a part of a larger extension integration effort, though it would be straight-forward to add a custom delegate object (and even easier just to add something to the SDK).
Another interesting option in the mean-time might be to use class_addMethod to add default functionality to an existing class/delegate - and this could be done via an extension. Though this might be a bit too "magic".

Closing as stale.

repo: mapbox/mapbox-annotation-extension


text:
Use minimum supported node version for Electron 7

Not sure if this change is right, but wondering if this is the reason the CI was failing with Electron 7.
Looks like the minimum supported node version for Electron 7 is Node 8

@kewde any idea why some Travis jobs failed when I ran them from my repo but worked fine from this PR? (using the same commit)
For example:
https://travis-ci.org/mapbox/node-sqlite3/jobs/615116333
https://travis-ci.org/EmilioCristalli/node-sqlite3/jobs/615105993
It's like the one from my repo was missing xvfb, but can't figure out why, since it should be using the same Travis config

Thank you for the contribution.
The appveyor errors are unrelated, will merge after the osx checks are done.

authors: EmilioCristalli kewde


text:
pod install failed for iOS

Following the readme file to run the example project, I found that:

there is a typo for "npm i or yarn instal", which should be "npm i or yarn install"
I got the following error for "pod install" for iOS:
Analyzing dependencies
Fetching podspec for ViroKit from ../node_modules/react-viro/ios/dist/ViroRenderer/
[!] No podspec found for ViroKit in ../node_modules/react-viro/ios/dist/ViroRenderer/

Please review and comment.

I figured it out by initializing the project using: react-viro init ViroSample --verbose
However, there is one library is still missing which is named as RNMapboxARDemo/node_modules/react-native-vector-icons

Having the same issue here!
pod install could not be run, with the following error:

[!] No `Podfile' found in the project directory.

I tried to do pod init, the installation went fine. But there was a problem in building the project in Xcode afterward.
attached a screenshot

@jafar-albadarneh Could you confirm you were in the RNMapboxARDemo/ios folder

authors: jafar-albadarneh pushian virtualLast

repo: mapbox/react-native-mapbox-ar


text:
getting tests running on node v0.11/windows

Node v0.11.x works on linux but not windows. For a rainy day:
C:\projects\tilelive-vector\node_modules\tape\index.js:75
        throw err
              ^
Error: ENOENT, open 'C:\projects\tilelive-vector\%5Cprojects%5Ctilelive-vector%5Ctest%5Cfixtures%5Ctm2z%5Cproject.tm2z'
    at Error (native)

https://ci.appveyor.com/project/Mapbox/tilelive-vector/build/1.0.92/job/74msxxwu1gkwlm4w

Stale: tests are passing and node 0.11 has been dropped.

authors: BergWerkGIS springmeyer

repo: mapbox/tilelive-vector


text:
how to include more than one property while using --include?

I want to use --include option to include only two properties from geojson while creating mbtiles. As of now I am doing --include="property1,property2" . But that's not working?
Any suggestions?

You can use multiple --include options to include multiple properties. If you do tippecanoe --include=property1 --include=property2 it will include them both.

authors: agaase ericfischer

repo: mapbox/tippecanoe


text:
Can't build xcframework success

I want to build iOS xcframework, but it's fail with following error message
❌  ld: library not found for -lmbgl-core
❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)
The following build commands failed:
Ld maplibre/platform/ios/build/ios/ArchiveIntermediates/dynamic/IntermediateBuildFilesPath/ios.build/RelWithDebInfo-iphoneos/dynamic.build/Objects-normal/armv7/Binary/Mapbox normal armv7 (in target 'dynamic' from project 'ios')
I have tried several Xcode version(14.1, 13.4.1, 13.1), but it doesn't work.
My Mac OS version is "Monterey 12.6.1"
Xcode version is "14.1"
And my Mac is M1 chip
The build command I inputed was

cd platform/ios
make iproj CI=1
make xcframework BUILDTYPE=Release

Thanks for the report. I am able to reproduce this locally.

I am also able to reproduce on Big Sur with Xcode 13.2.1.  The scheme that builds for UI Tests, iosapp, builds and works fine.
Looking at the log file, within.cpp fails to build.  In a Slack chat @louwers mentioned GitHub Actions that build the XCFramework.  I went to check those and release hasn't ran for a month and pre-release hasn't ran for a couple of years on GitHub.
I just kicked off both of those manually to see what they will yield.   Here is where the GitHub Actions can be verified.

https://github.com/maplibre/maplibre-gl-native/actions

These are the two actions to be monitored when there status is updated at GitHub:

[ ] ios-release
[ ] ios-pre-release

 failure in target 'mbgl-core' src/mbgl/style/expression/within.cpp
** ARCHIVE FAILED **

The following build commands failed:
	CompileC /Users/roblabs/Library/Caches/XCSBuilder/Bots/0a0160914c83b73de4c77f2f650006b1/Source/maplibre-gl-native/platform/ios/build/ios/build/mbgl-core.build/Debug-iphonesimulator/Objects-normal/i386/within.o /Users/roblabs/Library/Caches/XCSBuilder/Bots/0a0160914c83b73de4c77f2f650006b1/Source/maplibre-gl-native/src/mbgl/style/expression/within.cpp normal i386 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'mbgl-core' from project 'Mapbox GL Native')
(1 failure)

# print Mac OS X operating system version information
sw_vers
ProductName:	macOS
ProductVersion:	11.7.1
BuildVersion:	20G918

# Print operating system name
uname -a
Darwin nullisland.local 20.6.0 Darwin Kernel Version 20.6.0: Thu Sep 29 20:15:11 PDT 2022; root:xnu-7195.141.42~1/RELEASE_X86_64 x86_64

# Xcode version & path
/usr/bin/xcodebuild -version
Xcode 13.2.1
Build version 13C100

@roblabs ios-release runs though it seems (only fails because the tag has already been released).

mbgl/style/expression/within.cpp is defined once in the CMake files.   That seems fine.  My other guess would be to investigate if or when the CMake files were last refactored.

https://github.com/search?q=repo%3Amaplibre%2Fmaplibre-gl-native+within.cpp+language%3ACMake&type=code&l=CMake

I tried a lot of things to fix this, including increating the minimum deployment target to iOS 12, removing and re-adding the libraries to link in Xcode (Stack overflow reported that this sometimes helps), set "build active active architecture only" to NO. All to no avail.
Just tried again on the macOS runner which is using macOS Montery (12.5.1) and Xcode 14.2. Selecting the dynamic scheme and "Any iOS Device" as target, then selecting Product > Archive works (as well as creating an archive through xcodebuild).

OK I think I finally found the issue: CMake 3.24 works while CMake 2.35 does not.

Switching cmake versions worked locally for me as well.  We'll have to decide on either creating a dependency for cmake@3.24.3 or fixing up due to the changes in the link above.
Good catch @louwers

The policies can be set conditionally as you know which version of CMake you run with. So I'd set the policy accordingly for the versions of CMake when it appeared (or fix our config that the policy is not needed).
It seems though that they reverted it in 3.36, but we should not rely on that.

I tried setting the policy but that did not fix the issue for me.

Did you do a full rebuild?

I can investigate but not before the weekend.

Note that it is still possible to create an XCFramework with Bazel. #806
I am not very happy with the setup of CMake + checked in Xcode files + Makfile + scripts + xcodebuild on the iOS side. The Bazel setup seems much cleaner, in part thanks to much better iOS support.

I will be a bit provocative and say, why not CMake-only 😊
I think we should really aim in that direction.

Because CMake support for iOS is lacking. It cannot build XCFrameworks for example.

Really? You still generate the Xcode project and then you can do anything with it. Do XCFrameworks require some very special configuration to be made?

Generating the entire Xcode project with CMake and getting rid of the checked in Xcode files is probably a big improvement already. But I am not sure if it is feasible. I have to look more into it #737

We have overhauled the build config.
Please try out build instructions in the pre-release thread.

authors: crablife louwers ntadej roblabs

repo: maplibre/maplibre-gl-native


text:
make ios error: WorkspaceSettings.xcsettings

Describe the bug
I used the make ios command, and this error appeared, it seems that in ios there is no platform folder like before.
To Reproduce
cd platform/ios
make ios
Error: make: *** No rule to make target platform/ios/WorkspaceSettings.xcsettings', needed by platform/ios/ios.xcworkspace/xcuserdata/sangnguyen.xcuserdatad/WorkspaceSettings.xcsettings'.  Stop.

Please follow the updated build instructions: https://github.com/maplibre/maplibre-native/blob/main/platform/ios/README.md#developing

repo: maplibre/maplibre-native


text:
Fix the issue that the empty polyline cannot be updated

An example code to reproduce the issue is
Polyline line = mapLibreMap.addPolyline(new PolylineOptions());
// Anything to update the polyline will fail
line.setPoints(...);
line.setColor(...);

The reason is that PolylineContainer will ignore the empty polyline the first time.

Hmm, I wonder why that check was there in the first place...
Did you test what happens if you add an empty polyline and don't add any points/colors etc later in the code?

Thanks for the PR!!
We should probably make this behavior consistent across other types of containers. For example:
https://github.com/maplibre/maplibre-native/blob/06fb1816a6c400af051a0ec2605d0eff25eb1f12/platform/android/MapLibreAndroid/src/main/java/org/maplibre/android/maps/PolygonContainer.java#L30-L35
Also there is a AnnotationManagerTest.kt where a test can be added.

Hmm, I wonder why that check was there in the first place...
Did you test what happens if you add an empty polyline and don't add any points/colors etc later in the code?

This issue was found by our developer during map integration, nothing will happen with empty point, but cannot update the polyline later since it's not really added into the map

Thanks for the PR!!
We should probably make this behavior consistent across other types of containers. For example:
https://github.com/maplibre/maplibre-native/blob/06fb1816a6c400af051a0ec2605d0eff25eb1f12/platform/android/MapLibreAndroid/src/main/java/org/maplibre/android/maps/PolygonContainer.java#L30-L35
Also there is a AnnotationManagerTest.kt where a test can be added.

Hi louwers, I checked all the containers including PolygonContainer, PolylineContainer, MarkerContainer, AnnotationContainer, and ShapeAnnotationContainer, only PolygonContainer and PolylineContainer have this kind of logic, so made changes to these two classes and UT as well

authors: grab-liyanjin hactar louwers


text:
tests to verify fix for DRILL-4862

Hello Abhishek,
I have added tests to verify fix for DRILL-4862
You should look at framework/resources/Functional/convert/drill_4862*.q tests
Please review and merge, I have a clean run where my new test have passed, there are other unrelated failures in that run. I will share the link to that pre-commit run.
Thanks,
Khurram

HEy Khurram,
Looks like there are over 10 commits in here. Can you please do the following:

add mapr/master as a remote, if you haven't done so already
git remote add mapr git@github.com:mapr/drill-test-framework.git
create a new branch
`git checkout -b BRANCH_NAME
rebase it over mapr/master
git rebase mapr/master
add files part of this check-in
git add FILE_NAME
commit them
git commit -m "MESSAGE"
push them to a new branch
git push origin BRANCH_NAME
create a PR from this branch via Github

Those others commits that are showing up were the ones we already merged in an earlier PR. Those were tests for null equality join support.
I think the HEAD got changed/messed up somehow on my machine, while I was trying to build different versions of Drill.
Is it not possible that we can fix the HEAD on my current repo on my machine ? That will save me some time.
I have never had this kind of issue before, only after the HEAD was changed I have started to see these issues.
Thanks,
Khurram

If you already have them committed in your fork and you think your master is messed up,
To clean up master on your fork:

add mapr/master as a remote, if you haven't done so already
git remote add mapr git@github.com:mapr/drill-test-framework.git
fetch or pull mapr
git pull mapr master
rebase your master over mapr/master
git rebase mapr/master

Since you have new commits, before you raise a PR,

create a new branch from your updated master branch
git checkout -b BRANCH_NAME
rebase it again interactively and squash all related commits into one.
git rebase -i HEAD~10
Assuming after rebase over master you have 10 new commits in your branch. Retain 'pick' on the earliest and most relevant commit. Change 'pick' to 's' on each line for a related commit. Save it. Then once rebase starts, edit the commit message to remove all messages above the instructions, except for the most relevant message.
force push this to your new branch
git push -f origin BRANCH_NAME

However, we see this message when I did a compare of the two branches, " Able to merge. These branches can be automatically merged."
So I would assume that it is safe to merge, given that there are no conflicts & we have a clean pre-commit run.
Thanks,
Khurram

authors: Agirish kfaraaz

repo: mapr/drill-test-framework


text:
ID mess

Can somebody explain to me how task IDs are supposed to work? The numbers I see in the admin task list don't seem to correspond to the numbers that /api/v2/challenge/:id/tasks reports.

They match for me. Perhaps I'm misreading you. Can you provide an example?

I can't reproduce this now myself. Looks okay. I remember seing IDs and/or names with totally different numbers. Will close this now and reopen if I can reproduce this again.

authors: joto mvexel


text:
OS Open Zoomstack

Added the Ordnance Survey Open Zoomstack to the data sources and the related styles.
Demo: https://797-84182601-gh.circle-artifacts.com/0/artifacts/build/index.html#5.87/52.601/-1.963
Note: It is currently missing thumbnail images

@orangemug looks great! Did you sign up to the 3-month trial?

Hey, @pathmapper. So I've just been at the OS open zoomstack masterclass event. Hosted by @charleyglynn and Oliver Snowden, they both said they'd be happy for the styles and source to be in the editor (a big thankyou to @gregorywolanski for the introduction)
It was a great event, where the whole room was using Maputnik to style the OS Open Zoomstack data source. Pretty cool to see 😄

Note: It is currently missing thumbnail images (note: thumbnails are 600x400px)

Proposal for thumbnails: https://github.com/maputnik/maputnik.github.io/pull/17

I'm excited about this too @orangemug !
Have you started drafting words for a blog post? - I'm confident that this will be well received. I can start to chat with Joss and the team on Monday.
Another huge thanks for your efforts on this. We really appreciate it and can't wait to see people using it!

Have you started drafting words for a blog post?

No I haven't yet. I'm not much of a blogger to be honest, @charleyglynn got any words of wisdom on what would make a good post for this kind of thing? I assume you might have written a few "look at the new [insert product here]" posts in your time 😄

authors: charleyglynn orangemug pathmapper

repo: maputnik/editor


text:
source vector tile service docs from real repo

source vector tile service docs from real repo, woo!
upgrade assumptions in Makefile

hey @louh, do these doc source file changes look OK? @nvkelso and I did them together with your readme docs.
I have some other doc site updates to get to dev and prd this week, so we can include these, too.

Sorry about leaving this in limbo for so long, @nvkelso and @rmglennon. Merging now!

authors: louh nvkelso rmglennon

repo: mapzen/mapzen-docs-generator


text:
attribution from options overwrites Mapzen & OSM attribution

When user passes the attribution inside of options object, mapzen.js overwrites the attribution, getting rid of Mapzen attribution. I wonder it would be better to keep the Mapzen attribution and just add the attribution (as a prefix) that user passes. Any idea? @rfriberg ? @louh ?

Good question.  We intentionally left the attribution overwrite-able, but there is an argument to be made that we have a responsibility to OSM to make sure they are attributed properly, as well as a responsibility to our users to make it as easy as possible to follow our own attribution requirements.
So, I'm OK with making our attribution harder to remove.
We should also take this opportunity to review how we're handling attribution within individual components.  @hanbyul-here - it looks like you have an open PR to remove the specific geocoder attribution -- thank you; I think that's the right move (at least until such time that we allow a geocoder w/o map).
We are also allowing specific attribution via tangramOptions, which gets appended to the end of the attribution.  This is an artifact from allowing all Tangram and Leaflet options to pass through tangramOptions.
Example:
      var map = L.Mapzen.map('map', {
        tangramOptions: {
          attribution: 'attribution via tangramOptions'  // appended after Leaflet attribution
        },
        attribution: 'attribution via options'  // Overwrites our existing Mapzen attribution
      });

I'm inclined to leave that one for now, because it's not overwriting anything (and is unlikely to even be used due to lack of documentation/examples).
Moving forward, I propose we use one of the following formats for attribution that is passed in via the options object:
© Mapzen, OpenStreetMap, and others | Leaflet | User-provided attribution
or
User-provided attribution | © Mapzen, OpenStreetMap, and others | Leaflet
(Assume those have the appropriate links ☝)   Any preferences?

Technically, Leaflet isn't required: https://groups.google.com/forum/#!topic/leaflet-js/fA6M7fbchOs

Oh, that's a good reminder.  Because mapzen.js is built on Leaflet and passes Leaflet options, you can also turn off the attributionControl entirely:
      var map = L.Mapzen.map('map', {,
        attributionControl: false
      });

I think User-provided attribution | © Mapzen, OpenStreetMap, and others | Leaflet  is the format what I expect to see when I pass the attribution. I left this comment on the closed pr too, but I think it is good not to encourage users to use each of component's attribution control? since the order of each attribution can be mixed and confusing?

authors: hanbyul-here rfriberg rmglennon

license: isc


text:
Pictures are missing from Wiki

Hi,
It seems all pictures are missing from the Wiki on FLAME.

Hi,
Pictures should be up now.
If not, just comment on this thread.
There was an issue with wrong permissions and sources.
Thank you for flagging this error!

Hi Marabouboy,
Pictures are online now - thank you for your swift action!

authors: marabouboy ulbivin

repo: marabouboy/FLAME


text:
[Feature Request] Custom Hash-function

I found that hashing all my repository files takes approx. two minutes. I think I can make it much faster if I use hash that git has already computed using git hash-object. But now I can't do that because lib doesn't provide option for that.
Please add option for custom hash functions

Hello @gzaripov,
I'm not sure I fully understand your use case: If you have already checked all the files into git, then why don't you use git to get all necessary information?
Git already stores everything in a tree structure, and parsing the results from there should be a better idea than reading the dir content recursively in node.js and then retrieving each hash from git separately.
So the starting point would be according to the documentation
$ git cat-file -p main^{tree}

[...]
100644 blob d630eaf136b09ad2f0acb23c74acde2866433fba	CHANGELOG.md
100644 blob ac123679c1a6a1b984df89c0b163155c0733a678	README.md
040000 tree 16511c817968e5e04dda7aa9d6e8cef9b3d07323	bin
040000 tree dd350d245efb452615e2463bf6e1ae18cb8640f8	docs
[...]

And then parse the lines and recursively get information from the other trees.
If you are not limited to git, you might want to try fossil scm (the tool written to develop sqlite), which is supposed to have better APIs and might make querying easier.

I'm closing this issue because I still think it would be best to avoid duplicate work and not only retrieve hashes from git, but rather query the whole tree structure.


text:
latest node-mongodb-native version prevents connection

node-mongodb-native 0.9.7-2-1 prevents mongolian from creating a database connection.

The latest npm published version 0.1.14 is broken. A version bump to npm would be appreciated. Thanks.

Ignore last comment, I was mistaken. Thanks for the fix.

license: Zlib


text:
🛑 Grafana-test is down

In b8dd0df, Grafana-test (https://grafana-test.bojko.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Grafana-test is back up in 01a5bf8 after 6 minutes.

repo: marcinbojko/upptime


text:
🛑 Video Call is down

In dc98f78, Video Call (https://jitsi01.diversolatam.com/test) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Video Call is back up in f8918ba.

repo: marcoadasilvaa/health


text:
🛑 Video Call is down

In 6266b3a, Video Call (https://jitsi01.diversolatam.com/test) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Video Call is back up in ed3d916.


text:
🛑 Video Call is down

In 6219db7, Video Call (https://jitsi01.diversolatam.com/test) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Video Call is back up in 2656e3a.


text:
Feature Request: Slug override

Possibility to override post slug (and destination).
For example IMDb movie reviews, you could specify "slug: /reviews/movies/0379217" for review of Coffee and Cigarettes -review on your site.
Other use cases: automatically generated entries, twitter timeline mirroring ("slug: /twitter/[tweet id]").
You could check if the output folder has the entry.

Interesting idea. Keep in mind that the way the document root is structured, the only ways to do this would be:

Add a Redirect to .htaccess for every custom slug, which is probably not a good idea.
Actually generate the folders and files to correspond to the custom slugs. So there would actually be a file in the document root at /reviews/movies/0379217, with all of the parent folders created as well.

I don't love either solution, but I guess the second would probably have fewer problems.

The second solution would be more like what I had in mind.
It would be important to be able to check does a specific entry exist. Wouldn't want to overwrite changes.
Current output naming scheme prevents reliable testing.

authors: ivuorinen marcoarment

repo: marcoarment/secondcrack


text:
Builds on TravisCI hang right after successful completion

I have to say that locally all tests pass and the test does not hang at the end.

Fixed with commit a917f61ac3e93548bd97556d46d3935a618dedc4.


text:
Thumbnail entity not automatically renamed

After renaming a device (printer), HA asks if you want to rename the associated entities to reflect the new device name. From what I can tell, all of the entities are renamed other than the thumbnail entity.
Can we also automatically rename the thumbnail entity when prompted?

I wasn't able to replicate the issue I saw yesterday so I'll say it was a weird one-off occurrence. I'll go ahead and close the ticket.

@marcolivierarsenault I stumbled upon the cause of the issue. When you first add a device, the thumbnail sensor does not show up in the sensors list, if you then refresh the browser, it then shows up.
The issue is (very very minor one) if you update the name of the device immediately after adding and before refreshing, the thumbnail sensor is exclude because it is invisible in the sensors list. Once you refresh, the original device name shows up and you then have to manually rename the sensor.
See attached video for the issue:
https://drive.google.com/file/d/1hN4i8cSPz28wUVpuIpR5IbdifODtbKK2/view?usp=sharing

@marcolivierarsenault It's related to the fact that we add some entity (camera and thumbnail) after the initial setup of the other entity. We will have the same problem with the sensors from #47.

@cashew22 any idea how to fix that one?

@marcolivierarsenault We need to find a way to return from _setup_async after all the pending jobs related to entities are done


text:
DatabaseGPT for Postgres (and more?)

DatabaseGPT currently supports only scenarios where we have SqlServer databases. It doesn't currently support the case of a different SQL DBMS like Postgres, SQLite, MySql, etc... The major difference between all these DBMS is mainly the dialect of the SQL language used in the database and the required drivers themselves.
Since a user who is interested in using DatabaseGPT to query a SqlServer might not be interested in having the drivers also for another DBMS, it is preferrable to not include all the possible database drivers in a single package.
I suggest then the refactor of the solution as follows:

DatabaseGPT: this will be the package that contains all the logic independently from the DBMS. (The actual requests to the OpenAI endpoints should be handled here)
DatabaseGPT.Core: this will contain the definition of the interfaces and the basic classes required by the database specific implementations. (For example, the definition of an interface IDatabaseProvider)
DatabaseGPT.SqlServer: this will contain the SqlServer specific logic
DatabaseGPT.Npgsql: this will contain the Postgres specific logic
DatabaseGPT.MySql (future)
DatabaseGPT.SQLite (future)

If the idea is valid and interesting, I can start to design a more detailed refactoring plan and the database-specific implementations for SqlServer and Postgres.

The idea is definitely interesting. I have some consideration about your suggestion:

Use Gpt instead of GPT for the project name
Instead of DatabaseGpt.Core, I would prefer DatabaseGpt.Abstractions, using the same naming convention that is adopted by Microsoft
With this refactoring, the current DatabaseGptConsole project should be moved to a samples folder.

I have assigned the task to you @nicolaparo, thank your for collaboration!

authors: marcominerva nicolaparo

repo: marcominerva/DatabaseGPT


text:
Improve README content rendering and styles

For some gems on gem.sh the show page renders very weird and broken looking READMEs, we should look into what's causing it and see if there might be a more relaxed Markdown parser which can also better recover from a malformed markdown file.
It might also be that some of our styles are leaking into the rendered markdown content, maybe we need to better scope the selectors.
Example: https://gem.sh/gems/activerecord/v7.0.6

One such issue seems to be related to code blocks with a language specified. I was reviewing a simple gem I wrote and found the readme was looking in disarray.
For example, when the following codeblocks specifying ruby are encountered:

it renders as

and

Link to my example:

https://gem.sh/gems/output_attributes/v1.0.1
https://github.com/ttilberg/output_attributes/

I believe the ActiveRecord is currently suffering the same issue. Fixing the language detection for code blocks might go a long way to resolving the output.

@ttilberg improved this a bit in #44, but I think there are still some thing we can improve, like:

the character escaping mentioned in #44
code highlighting in code blocks
styles of the stylesheet itself

Also some more advanced features could be cool:

the ability to copy code from code blocks and the
Auto-reference constants to the docs page when they are mentioned in the README

authors: marcoroth ttilberg


text:
Please add a year to the calandar view

What would you like to be added?
Thinking of a grid where each cell is a month.  The items can then be listed in each month.
Use Case;  I have a project that contains all my projects.  The new "year" view can be used for planning projects for each for the year or individual quarters.  Simple drag-drop to move a project do a different month.
Something like this:

  |       January      |      February     |      March      |

Q1 |                         |                         |                     |
|   Project 1        |    Project 2        |                      |
  |       April           |      May            |      June        |

Q2 |                         |                         |                     |
|                         |                        |                      |
  |       July            |      August        |  September   |

Q3 |                         |                         |                     |
|                         |   Project 3        |                     |
  |     October       |   November      |   December   |

Q4 |                         |                         |                     |
|                         |                         |                     |
Why is this needed?
To help with managing and planning projects for the long term and to create a calendar driven road map.

I'd +1 this request

Glad to implement this. Providing a year view allows easiar navigation and a wide range of project management. I'll put down some thoughts here to reach a more detailed design.
Problems:

As we're indicating the item belonging using a date field, in the format of YYYY-MM-DD, if we change an event's date by dnd or just create a new note by dblclick on the month cell, what would be written into the date field? Don't like other view ranges that can access the date directly, date assignment of the year view should be treated carefully.

Example: Nov cell 2023-11-20 to Dev cell 2023-12-20
Newly created: assign the first day of the month.
Edge case: 2024-03-31 -> 2024-02-29 (the last date of determined month)

Ideally we would need a way to zoom in to the target month and easily back to the year view.

Zoom in will have an easier implementation, by clicking on the target month.
A call stack that remembers the previous calendar level year 2023 or November, 2023, ect. Provide a backwards button to navigate. (like iOS calendar)
Ctrl + Scroll  and multi touch for different levels (Y-M-D or Y-M-W-D)

A static year panel, or a scrollable one?

authors: Acylation aubreyz mtiowl

repo: marcusolsson/obsidian-projects


text:
fix ios11

Before your create your PR:
Please add tests for any new or changed functionality!

Edit Tests/WebViewJavascriptBridgeTests/BridgeTests.m
Create a new test which demostrates your changes.
Run make test and make sure your test is passing
That's it!

Thanks for improving WebViewJavascriptBridge!
Cheers,
@marcuswestin

fix iOS11

repo: marcuswestin/WebViewJavascriptBridge


text:
Module not found: Error: Can't resolve 'store'.

v2.0.0
I build bundle via WebPack.
Code:
import store from 'store';

I've switched to 1.3.20 - everything smooth and nice.

Should be fixed in 2b6cf4de50bb5 and v2.0.1. Apologies for the broken build!

Just verified that this works with v2.0.1:
test.js
import store from 'store'
store.set('foo', 'bar')
console.log(store.get('foo') == 'bar')

> webpack test.js test.out.js && node test.out.js
Let me know if anything else isn't right for you!
Cheers,
Marcus

Working! Thank you :-)

authors: amino-studio marcuswestin


text:
No src folder

Hi - I am using NPM latest release via webpack and the src folder doesn't exist in node_modules folder? This was working with no change on previous projects, am I missing something?

Hi,
you're not missing anything - with a change of the build infrastructure, the src folder is no longer present - please use files from the dist folder - there are both minified and unminified versions there.

But the package.json in the NPM 1.2.0 is referencing the entry point main file with the src folder in the path not the dist folder?

{
  "name": "imagelightbox",
  "version": "1.2.0",
  "description": "Image Lightbox, Responsive and Touch‑friendly",
  "homepage": "https://marekdedic.github.io/imagelightbox",
  "license": "MIT",
  "repository": "https://github.com/marekdedic/imagelightbox.git",
  "main": "./src/imagelightbox.js",
  "style": "./src/imagelightbox.css",
  "types": "./types/imagelightbox.d.ts",
  "files": [
    "dist",
    "docs",
    "types",
    "CHANGELOG.md"
  ],
  "dependencies": {
    "jquery": ">=1.12.4 <4.0.0"
  },
  "devDependencies": {
    "@types/jquery": "^3.3.31",
    "@typescript-eslint/eslint-plugin": "^5.32.0",
    "@typescript-eslint/parser": "^5.32.0",
    "chai": "^4.2.0",
    "csslint": "^1.0.5",
    "eslint": "^8.21.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-compat": "^4.0.2",
    "eslint-plugin-deprecation": "^1.3.2",
    "eslint-plugin-prettier": "^4.2.1",
    "express": "^4.17.1",
    "gulp": "^4.0.2",
    "gulp-autoprefixer": "^8.0.0",
    "gulp-clean-css": "^4.2.0",
    "gulp-concat": "^2.6.1",
    "gulp-connect": "^5.7.0",
    "gulp-rename": "^2.0.0",
    "gulp-typescript": "^5.0.1",
    "gulp-uglify": "^3.0.2",
    "mocha": "^10.0.0",
    "npm-run-all": "^4.1.5",
    "puppeteer": "^16.0.0",
    "stylelint": "^14.9.1",
    "stylelint-no-unsupported-browser-features": "^5.0.3",
    "typescript": "^4.7.4"
  },
  "keywords": [
    "jquery",
    "lightbox"
  ],
  "scripts": {
    "build": "gulp",
    "start": "gulp dev",
    "test": "mocha --recursive test/src",
    "lint:css:csslint": "csslint src/imagelightbox.css",
    "lint:css:stylelint": "stylelint --color 'src/**/*.css'",
    "lint:css": "run-p -c --aggregate-output lint:css:*",
    "lint:ts:eslint": "eslint --color 'src/**/*.ts' 'gulpfile.js'",
    "lint:ts": "run-p -c --aggregate-output lint:ts:*",
    "lint": "run-p -c --aggregate-output lint:*",
    "prepack": "npm run build"
  },
  "browserslist": [
    "cover 95%",
    "not < 0.1%",
    "Firefox ESR",
    "IE >= 9",
    "Android >= 2.3",
    "not OperaMini all"
  ]
}

Oh, then that's a bug in the main field, thanks for spotting that!

Should be fixed in 2.0

authors: jranby marekdedic

repo: marekdedic/imagelightbox


text:
Added support for GFM

Closes #5

[ ] Add support for tables
[x] Add support for task list items
[x] Add support for strikethrough
[ ] Add support for extended autolinks
[ ] Add support for filtered raw HTML

Codecov Report
Attention: Patch coverage is 49.41176% with 43 lines in your changes are missing coverage. Please review.

Project coverage is 80.61%. Comparing base (ae3a271) to head (8dd1279).
Report is 4 commits behind head on master.

:exclamation: Current head 8dd1279 differs from pull request most recent head 31366f0. Consider uploading reports for the commit 31366f0 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
- Coverage   85.97%   80.61%   -5.36%
==========================================
  Files          20       23       +3
  Lines         499      583      +84
  Branches       42       55      +13
==========================================
+ Hits          429      470      +41
- Misses         70      104      +34
- Partials        0        9       +9

Files
Coverage Δ

src/syntax-extensions/ListItemExtension.ts
100.00% <100.00%> (ø)

src/syntax-extensions/StrikethroughExtension.ts
95.23% <95.23%> (ø)

src/GFMExtension.ts
0.00% <0.00%> (ø)

src/syntax-extensions/TaskListItemExtension.ts
34.69% <34.69%> (ø)

... and 8 files with indirect coverage changes

Pull Request Test Coverage Report for Build 9038157905
Details

28 of 79 (35.44%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-10.6%) to 79.31%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/syntax-extensions/StrikethroughExtension.ts
12
13
92.31%

src/GFMExtension.ts
0
8
0.0%

src/syntax-extensions/TaskListItemExtension.ts
14
56
25.0%

Totals

Change from base Build 9038146823:
-10.6%

Covered Lines:
322

Relevant Lines:
406

💛  - Coveralls

authors: codecov-commenter coveralls marekdedic

repo: marekdedic/prosemirror-remark


text:
Layered drawing.

Rendering currently only displays the things in order they are drawn, but this is sometimes inconvenient. For example:
BeginWindow("WindowA")
  //...
BeginWindow("WindowB")
  //...
BeginWindow("WindowC")
  //...

The windows will be drawn in order of A B and C, but if we drag the window A on top, it will still be rendered behind window B and C because it appears before them in code.
This currently can be worked around with a draw command system, where the drawing code is deferred and then actually rendered. But it's not very useful to have draw commands for every single thing you want to draw. There's an alternative workaround, rendering windows with callback:
BeginWindow("WindowA", fn(data: interface{}) {

}, data)

I currently know of 2 ways to work with this: access to depth buffer, sorting draw calls into layers.

I never planned for something like this to be included in tophat. For me the callback idea is much better than adding more features to the engine, although Umka's lack of closures might make it harder to work with.

Definitely. I'll go with the callbacks for now, but i can see the appeal for maybe having access to the depth buffer

As for the callback idea. The problem struck with nested callbacks. In the end I decided against that idea since everything was completely out of order.

Currently I'm going with a draw command buffer idea, and it's working somewhat. I pass in an interface to add custom drawing functions

Closing thus far as it's pretty vague. But would love to have layered drawing of some kind. In my opinion this would be especially important once we can maybe get cached renderer to work.

.

authors: marekmaskarinec skejeton

repo: marekmaskarinec/tophat


text:
Problem running example

Hi @mrousavy , tried to run the example that is in the repository, but I get the following error:
yarn run v1.22.4
$ react-native run-android
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 984 file(s) to forward-jetify. Using 8 workers...
info JS server already running.
info Installing the app...

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/Username/Desktop/react-native-graph/example/android/app/build.gradle' line: 151

* What went wrong:
A problem occurred evaluating project ':app'.
> Could not get unknown property 'nativeArchitectures' for BuildType_Decorated{name=debug, debuggable=true, testCoverageEnabled=false, jniDebuggable=false, pseudoLocalesEnabled=false, renderscriptDebuggable=false, renderscriptOptimLevel=3, minifyEnabled=false, zipAlignEnabled=true, signingConfig=SigningConfig_Decorated{name=debug, storeFile=/Users/Username/Desktop/react-native-graph/example/android/app/debug.keystore, storePassword=android, keyAlias=androiddebugkey, keyPassword=android, storeType=jks, v1SigningEnabled=true, v2SigningEnabled=true, enableV1Signing=null, enableV2Signing=null, enableV3Signing=null, enableV4Signing=null}, embedMicroApp=false, mBuildConfigFields={}, mResValues={react_native_dev_server_port=com.android.builder.internal.ClassFieldImpl@99240943, react_native_inspector_proxy_port=com.android.builder.internal.ClassFieldImpl@44d408ec}, mProguardFiles=[], mConsumerProguardFiles=[], mManifestPlaceholders={}} of type com.android.build.gradle.internal.dsl.BuildType.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/Username/Desktop/react-native-graph/example/android/app/build.gradle' line: 151

* What went wrong:
A problem occurred evaluating project ':app'.
> Could not get unknown property 'nativeArchitectures' for BuildType_Decorated{name=debug, debuggable=true, testCoverageEnabled=false, jniDebuggable=false, pseudoLocalesEnabled=false, renderscriptDebuggable=false, renderscriptOptimLevel=3, minifyEnabled=false, zipAlignEnabled=true, signingConfig=SigningConfig_Decorated{name=debug, storeFile=/Users/Username/Desktop/react-native-graph/example/android/app/debug.keystore, storePassword=android, keyAlias=androiddebugkey, keyPassword=android, storeType=jks, v1SigningEnabled=true, v2SigningEnabled=true, enableV1Signing=null, enableV2Signing=null, enableV3Signing=null, enableV4Signing=null}, embedMicroApp=false, mBuildConfigFields={}, mResValues={react_native_dev_server_port=com.android.builder.internal.ClassFieldImpl@99240943, react_native_inspector_proxy_port=com.android.builder.internal.ClassFieldImpl@44d408ec}, mProguardFiles=[], mConsumerProguardFiles=[], mManifestPlaceholders={}} of type com.android.build.gradle.internal.dsl.BuildType.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s

    at makeError (/Users/Username/Desktop/react-native-graph/example/node_modules/execa/index.js:174:9)
    at /Users/Username/Desktop/react-native-graph/example/node_modules/execa/index.js:278:16
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async runOnAllDevices (/Users/Username/Desktop/react-native-graph/example/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:109:5)
    at async Command.handleAction (/Users/Username/Desktop/react-native-graph/example/node_modules/@react-native-community/cli/build/index.js:192:9)
info Run CLI with --verbose flag for more details.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I had to change the gradle version from gradle-6.2-all to gradle-6.7.1-all, because before I got the following error:
yarn run v1.22.4
$ react-native run-android
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 984 file(s) to forward-jetify. Using 8 workers...
info JS server already running.
info Installing the app...

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/Username/Desktop/react-native-graph/example/android/app/build.gradle' line: 1

* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin [id 'com.android.internal.version-check']
   > Minimum supported Gradle version is 6.7.1. Current version is 6.2. If using the gradle wrapper, try editing the distributionUrl in /Users/Username/Desktop/react-native-graph/example/android/gradle/wrapper/gradle-wrapper.properties to gradle-6.7.1-all.zip

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/Username/Desktop/react-native-graph/example/android/app/build.gradle' line: 1

* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin [id 'com.android.internal.version-check']
   > Minimum supported Gradle version is 6.7.1. Current version is 6.2. If using the gradle wrapper, try editing the distributionUrl in /Users/Username/Desktop/react-native-graph/example/android/gradle/wrapper/gradle-wrapper.properties to gradle-6.7.1-all.zip

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5s

    at makeError (/Users/Username/Desktop/react-native-graph/example/node_modules/execa/index.js:174:9)
    at /Users/Username/Desktop/react-native-graph/example/node_modules/execa/index.js:278:16
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async runOnAllDevices (/Users/Username/Desktop/react-native-graph/example/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:109:5)
    at async Command.handleAction (/Users/Username/Desktop/react-native-graph/example/node_modules/@react-native-community/cli/build/index.js:192:9)
info Run CLI with --verbose flag for more details.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

What am I doing wrong?

@mrousavy : Could you test it and let me know?

If by chance the project works for you by running it on an android device.

It doesn't, that's what I was saying. I extracted this component from a private production app, it works there.

When I try to disable the gesture, the app crashes and I get the following error:

I know, RNGH bug.

If by chance the project works for you by running it on an android device.

It doesn't, that's what I was saying. I extracted this component from a private production app, it works there.

When I try to disable the gesture, the app crashes and I get the following error:

I know, RNGH bug.

Maybe it should be mentioned somewhere that as-is, the package isn't working on Android.

Hello guys, any solution for Android so far?

This package doesn't work at all on Android. You guys should state that somewhere. Even the example app cannot be started, having the same issue. Extremely disappointing, such a great package yet it doesn't work.

This package doesn't work at all on Android. You guys should state that somewhere. Even the example app cannot be started, having the same issue. Extremely disappointing, such a great package yet it doesn't work.

I just ran yarn android in example/ and it built fine:

I am also using react-native-graph in a client app for Android and it works fine.

Most toggles are not working on Android. Maybe I do something wrong?

authors: Angelk90 ChimiChumi Dmitrylolo Jaserto Noitham mrousavy

repo: margelo/react-native-graph


text:
Problème d'affichage de ventes multiples pour une parcelle

Lors de la sélection d'une parcelle ayant eu plusieurs vente sur la période donnée, toutes les ventes s'affichent avec les mêmes valeur en prix d'achat et date de vente. Les surfaces des biens semblent correctes quand il y a différents bien vendus dans cette parcelle.

Bonjour Naxxos, et après avoir vidé le cache ? Normalement ça devrait fonctionner. Merci

C'est bon !

authors: Naxxos marion-paclot

repo: marion-paclot/DVF


text:
2.0.0

Moved Backbone and underscore to peerDependencies and bumper semver range.

:+1:

👍


text:
Search for TAGs

Hi,
Any chance to add a search for the filter box?
Would be useful for really big timelines with a huge amount of tags.
Thanks in advance!

Done, can you try it out and let me know if it works ok?
I would be interested in seeing some of your markwhen documents if you wouldn't mind sharing them! It would be helpful to me to see what heavy users are using it for/how performance is for really big timelines etc. I can only come up with contrived examples.

authors: kochrt pitecantropo

repo: mark-when/markwhen


text:
Added support to take an screenshot of an specific Vaadin Component

A implementation suggestion for the Feature request #1

Hey Eduardo, I haven't seen another commit come through. Have you completed the suggestions I made yet?

Hi Mark. I'm sorry. Unfortunatelly I had some problens yesterday and I ran
out of time to work on your suggestions.
I will work on it tonight, and open another feature request to convert the
addon to an extension.
Eduardo Frazão
2015-11-19 12:58 GMT-02:00 Mark Thomas notifications@github.com:

Hey Eduardo, I haven't seen another commit come through. Have you
completed the suggestions I made yet?
—
Reply to this email directly or view it on GitHub
https://github.com/markathomas/vaadin-screenshot/pull/2#issuecomment-158081536
.

Hey Eduardo, I went ahead and committed your changes and made the style changes myself.  I'll upload it shortly after verifying everything.  By the way, the versioning should be 0.4.1.x where x can change.  0.4.1 is the base version of html2image so i'm sticking with that for the root version of the add-on.  Thanks.

authors: EduFrazao markathomas

repo: markathomas/vaadin-screenshot


text:
Error: Namespace 'LinkifyIt' has no exported member 'LinkifyIt'

Error: node_modules/@types/markdown-it/lib/index.d.ts:151:33 - error TS2694: Namespace 'LinkifyIt' has no exported member 'LinkifyIt'.
151     readonly linkify: LinkifyIt.LinkifyIt;
When i try build package i get this error. I think is related with last update (05/01/2024)

https://github.com/DefinitelyTyped/DefinitelyTyped/issues/69526

I ran pnpm i @types/linkify-it@3.0.5 and it fixed the type safety issue. Not really a great solution, but at least I can build 😀.

repo: markdown-it/linkify-it


text:
fix: apply fixes and updates to make it working again

This will update the code base to make it functional again as it 5 years old code with many deprecated and obsolete dependencies
Major fixes and updates are:
Replacing request package with axios
Switching code exploiting request package to axios
Update Node version from 4.* to 14.*
Add .nvmrc file
Add package lock file
Update tableau WDC library
Reference #1092

@farhansaed In my opinion, we shouldn't be merging dodgy code without in approval. You should undo merging this PR, fix the issues raised by me and Ellis and re-merging. Unfortunately, I don't have an authority to make you do that. But I'll try to get help from somebody who does.

Thanks for the suggestions @ozmoroz.  Justt to highlight it's not an existing marketplacer repo it's an external repo suggested in issue 1092 and been forked after approval.
As per your suggestion above that's the potential way-forward in mind after this merge.
This code is not hooked up to marketplacer github account yet.
This forked-repo (code) is under investigation as a potential candidate and since upstream unfortunately is not maintained at all and repo was totally dead, current changes are merely done as first kickoff in development environment so that subsequent investigations can be done if deemed necessary.
It's investigation in progress and not as one off final fix.
Hope this clarifies things.

Native fetch API is much better option than Axios. It is supported by both browsers and Node.js (via node-fetch).

authors: farhansaed ozmoroz

repo: marketplacer/github-data-connector