zha: osram lightify bulb not responding

Home Assistant release (hass --version):
0.50.0.dev0
Python release (python3 --version):
3
Component/platform:
zha
Description of problem:
One paired light not working, the other is.
Expected:
Both lights working together
Problem-relevant configuration.yaml entries and steps to reproduce:
groups.yaml
Living Room Ambient Light:
  entities:
    - light.osram_lightify_a19_rgbw_00078b80_3
    - light.osram_lightify_a19_rgbw_0008c14f_3

Turn on group of lights
Change color, brightness, temp of lights

Traceback (if applicable):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 99, in async_turn_on
    duration
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:12:59 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 99, in async_turn_on
    duration
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:13:02 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 90, in async_turn_on
    duration,
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:13:05 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 99, in async_turn_on
    duration
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:13:07 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 99, in async_turn_on
    duration
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:13:13 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 99, in async_turn_on
    duration
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:13:19 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 90, in async_turn_on
    duration,
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:13:20 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 90, in async_turn_on
    duration,
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:13:23 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/src/app/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/light/__init__.py", line 279, in async_handle_light_service
    yield from light.async_turn_on(**params)
  File "/usr/src/app/homeassistant/components/light/zha.py", line 76, in async_turn_on
    temperature, duration)
  File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 261, in request
    v = yield from send_fut
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED
2017-07-23 00:13:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification
2017-07-23 00:13:27 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-07-23 00:13:27 WARNING (MainThread) [bellows.zigbee.zcl] [0x3934:1:0x0019] No handler for cluster command 1

Additional info:
Not sure if it's related, but seems brightness on the working light seems to drop when changing  color or temp. Touching the brightness brings it back up.

This is not limited to osram. Cree and Sengled bulbs exhibit the same symptoms. I think the issue is that multiple bulbs of different models work fine while identical bulbs have issues. You can register two, but only the last registered works. The other throws EmberStatus.DELIVERY_FAILED.

It's an interesting bug. I'm also noticing HA thinks one bulb is off, however still sends changes in color to both, and sometimes both respond and update. Sometimes just the "on" one. Change the temp and they both respond again.

@jkl1337 has identified the problems described in your "Additional info" and described them in #9234
If I could get debug logs of the working bulb and the failing bulb, I'd probably have enough information to do something with this report.

I confirm it's not a hass but but a bellows one

@rcloran hope this is can help
bellows -d /dev/ttyUSB1  -v DEBUG zcl  -D /zigbee.db  AA:AA:AA:AA:AA:AA: 25 513 read_attribute `python -c 'print(0x0000)'`
debug: Using selector: EpollSelector
debug: Loading application state from /opt/homeassistant/zigbee.db
debug: Sending: b'1ac038bc7e'
debug: RSTACK Version: 2 Reason: RESET_SOFTWARE frame: b'c1020b0a527e'
debug: Send command version
debug: Sending: b'004221a850ed2c7e'
debug: Data frame: b'0142a1a8502805e67f627e'
debug: Sending: b'8160597e'
debug: Application frame 0 (version) received
debug: Send command setConfigurationValue
debug: Sending: b'7d314321fb582815c3277e'
debug: Data frame: b'1243a1fb54fb737e'
debug: Sending: b'82503a7e'
debug: Application frame 83 (setConfigurationValue) received
debug: Send command setConfigurationValue
debug: Sending: b'224021fb592f15226f7e'
debug: Data frame: b'2340a1fb54c6107e'
debug: Sending: b'83401b7e'
debug: Application frame 83 (setConfigurationValue) received
debug: Send command setConfigurationValue
debug: Sending: b'334121fb792b15a2d77e'
debug: Data frame: b'3441a1fb54d32a7e'
debug: Sending: b'8430fc7e'
debug: Application frame 83 (setConfigurationValue) received
debug: Send command setConfigurationValue
debug: Sending: b'444621fb7d5e291514417e'
debug: Data frame: b'4546a1fb5435d07e'
debug: Sending: b'8520dd7e'
debug: Application frame 83 (setConfigurationValue) received
debug: Send command setConfigurationValue
debug: Sending: b'554721fb4d2815713f7e'
debug: Data frame: b'5647a1fb54a9ec7e'
debug: Sending: b'8610be7e'
debug: Application frame 83 (setConfigurationValue) received
debug: Send command setConfigurationValue
debug: Sending: b'664421fb55d515b18f7e'
debug: Data frame: b'6744a1fb54948f7e'
debug: Sending: b'87009f7e'
debug: Application frame 83 (setConfigurationValue) received
debug: Send command setConfigurationValue
debug: Sending: b'774521fb4a2b1524a97e'
debug: Data frame: b'7045a1fb5481b57e'
debug: Sending: b'8070787e'
debug: Application frame 83 (setConfigurationValue) received
debug: Send command setConfigurationValue
debug: Sending: b'004a21fb629e15b2107e'
debug: Data frame: b'014aa1fb63a4387e'
debug: Sending: b'8160597e'
debug: Application frame 83 (setConfigurationValue) received
debug: Send command networkInit
debug: Sending: b'7d314b21bf676c7e'
debug: Data frame: b'124ba5bf5463787e'
debug: Sending: b'82503a7e'
debug: Application frame 23 (networkInit) received
debug: Data frame: b'224bb1b1c450837e'
debug: Sending: b'83401b7e'
debug: Application frame 25 (stackStatusHandler) received
debug: Send command getNetworkParameters
debug: Sending: b'2348218038017e'
debug: Data frame: b'3348a180542bb3965ab9e24747cd4413944127abedce677302c16e257e'
debug: Sending: b'8430fc7e'
debug: Application frame 40 (getNetworkParameters) received
debug: Send command setPolicy
debug: Sending: b'344921fd517a9c837e'
debug: Data frame: b'4449a1fd54e1c97e'
debug: Sending: b'8520dd7e'
debug: Application frame 85 (setPolicy) received
debug: Send command setPolicy
debug: Sending: b'454e21fd524b884a7e'
debug: Data frame: b'554ea1fd541eef7e'
debug: Sending: b'8610be7e'
debug: Application frame 85 (setPolicy) received
debug: Send command setPolicy
debug: Sending: b'564f21fd542b307f7e'
debug: Data frame: b'664fa1fd548a677e'
debug: Sending: b'87009f7e'
debug: Application frame 85 (setPolicy) received
debug: Send command getNodeId
debug: Sending: b'674c218fb1437e'
debug: Data frame: b'774ca18f542ad5747e'
debug: Sending: b'8070787e'
debug: Application frame 39 (getNodeId) received
debug: Send command getEui64
debug: Sending: b'704d218edcd87e'
debug: Data frame: b'004da18eb68b3cb959fb4725990b7e'
debug: Sending: b'8160597e'
debug: Application frame 38 (getEui64) received
debug: Send command sendUnicast
debug: Sending: b'0152219c54b5ccb65895483cb31593499c4f26aeedcf678bfdc1df7e'
debug: Data frame: b'1152a19c542cb68a7e'
debug: Sending: b'82503a7e'
debug: Application frame 52 (sendUnicast) received
debug: Data frame: b'2152b19754b5ccb65895483cb31592499c4826cded85bf7e'
debug: Sending: b'83401b7e'
debug: Application frame 63 (messageSentHandler) received
Traceback (most recent call last):
  File "/tmp/bellows/env/bin/bellows", line 11, in <module>
    load_entry_point('bellows', 'console_scripts', 'bellows')()
  File "/tmp/bellows/env/lib/python3.6/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/tmp/bellows/env/lib/python3.6/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/tmp/bellows/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/tmp/bellows/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/tmp/bellows/env/lib/python3.6/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmp/bellows/env/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/tmp/bellows/env/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/tmp/bellows/bellows/cli/util.py", line 72, in inner
    loop.run_until_complete(async_inner(*args, **kwargs))
  File "/usr/lib/python3.6/asyncio/base_events.py", line 467, in run_until_complete
    return future.result()
  File "/tmp/bellows/bellows/cli/util.py", line 59, in async_inner
    yield from f(ctx, *args, **kwargs)
  File "/tmp/bellows/bellows/cli/application.py", line 241, in read_attribute
    v = yield from cluster.read_attributes([attribute], allow_cache=False)
  File "/tmp/bellows/bellows/zigbee/zcl/__init__.py", line 192, in read_attributes
    result = yield from self.read_attributes_raw(to_read)
  File "/tmp/bellows/bellows/zigbee/zcl/__init__.py", line 159, in read_attributes_raw
    v = yield from self.request(True, 0x00, schema, attributes)
  File "/tmp/bellows/bellows/zigbee/application.py", line 284, in request
    v = yield from send_fut
bellows.zigbee.exceptions.DeliveryError: Message send failure: EmberStatus.DELIVERY_FAILED

@rcloran do you need more logs? Is there a way I can log through HA what's going on between restarts? Happy to provide if I can.

Has there been any resolution to this?  I'm finding just 1 of my Cree Connected bulbs.
I have 4 Cree bulbs, 3 OSRAM, and an outlet in my zigbee.db.  Only 1 of these devices struggles.
I've tried deleting out the Cree bulb and resetting/syncing it.  I still get the same errors reported in this issue.

I'm getting this error as well with 2 Sengled bulbs. They both work as expected until homeassistant gets restarted, then the bulbs have to be power-cycled before they will work again

@rcloran do you think broadcast support and group support will fix this?

This is still an issue for me:
light.ledvance_a19_rgbw_00022f53_1: Unable to turn the light off: Message send failure: EmberStatus.DELIVERY_FAILED

I'm seeing this today on 0.84.2 after rebooting, light does not respond
This began after moving my config from Hass on Pi 3b to Hass on an Asus Tinker Board
I removed my old config and reconfigured ZHA through config->integrations, factory reset the fan/light and called zha.permit into a new zigbee database. The only solution I've found is power cycling the light by wall switch where it will reconnect to HA after powering on. This is a Hampton Bay/Wink fan & light control module. I'm using an Elelabs Zigbee USB adapter.
Messages in log after rebooting:
2018-12-14 23:37:45 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification
2018-12-14 23:38:01 ERROR (MainThread) [homeassistant.components.switch.zha] switch.zha_0020d3f4_1_6: Unable to turn the switch on: Message send failure: EmberStatus.DELIVERY_FAILED
Messages in log after power cycling and toggling light in HA:
2018-12-14 23:59:47 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved Traceback (most recent call last):`
File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/service.py", line 277, in _handle_service_platform_call     await getattr(entity, func)(**data)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/switch/zha.py", line 96, in async_turn_on     _LOGGER.debug("%s: turned 'on': %s", self.entity_id, res[1])
TypeError: bool object is not subscriptable

Today the “Unable to turn the light off: Message send failure: EmberStatus.DELIVERY_FAILED" error messages are back. I'm losing this light/fan in as little as 2 hours. Sometimes power cycling the switch brings it back online, sometimes I have to reboot HA and power cycle switch. I might move ZHA only config back to my Pi and see if it goes back to normal.

If it is just an reception problem fine, however I have experienced, that the firmware of soled zigbee devices can be very old (like years). I thus always update the firmware of each new device I get. Sadly most of the times firmware updates only work with the "original" zigbee hub, that is supposed to be used with the IOT device, defeating some of the interoperability power of zigbee

@cybergrimes

Another day and still up, I've found rebooting will not cause an issue but if I turn the HA device off completely that I do need to toggle power at the wall switch to bring it back online.

Wink Fan module is a Zigbee End device, meaning it does require a parent device for communicating with other Zigbee devices. Currently the coordinator (elelabs zigbee controller) is going to be a parent device for Wink Fan, so if you completely turn off HA and the coordinator, then it looses its parent and it is could take a while to resync when it is brought back online. (Don't know why they  implemented it as an end device, because it is always powered on and always powered on devices are usually routers.) Powercycling the fan triggers find and rejoin network after it looses its parent. So your findings are correct:

leaving antenna outside, improves connection stability as Wink fan can communicate only with coordinator and having any other Zigbee router doesn't improve the situation
Turning off Elelabs Zigbee Controllers removes the only point of Wink fan communication. Powercycling it expedites the "find and rejoin" process, but if you leave it, eventually it should find the network on its own

I'm having similar issues with Wink Fan, after HASS restart it could take up to 30min for Wink Fan to become controllable again by hass.

@ianhyzy Enable debug logging, collect the logs reproducing the problem and post logs or link to logs.

Closing in favor of #21423 as they’re the same.


Fix example file generation script to adapt for macOS

Must work on Linux, too, due to BSD compatibility

If you want to make the mkfiles.sh script macOS compatible then you need to utilize uname to do the correct thing given a particular os.

@Jimbo4350 I think these changes are compatible with GNU/Linux, too, since GNU utilities are compatible with the BSD interface. I'll double-check.

It works correctly on both linux and macOS

bors merge


When debugging on Nubia devices, flutter gets stuck at "Waiting for VM Service port to be available..."

Steps to reproduce

Create new flutter app in VS Code.
Attempt to debug on physical Android 14 device.

Expected results
App should start and be debuggable.
Actual results
App never gets past starting splash screen, log stuck at "Waiting for VM Service port to be available..."
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MainApp());
}

class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: Scaffold(
        body: Center(
          child: Text('Hello World!'),
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshot
Screenshot_20240312_110526

Logs
Logs
Log File

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.19.2, on Microsoft Windows [Version 10.0.22631.3155], locale en-US)
    • Flutter version 3.19.2 on channel stable at C:\Tech\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (2 weeks ago), 2024-02-27 16:51:22 -0500
    • Engine revision 04817c99c9
    • Dart version 3.3.0
    • DevTools version 2.31.1

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\1099996508.adm\AppData\Local\Android\sdk
    • Platform android-34-2, build-tools 34.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0--11185874)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.8.2)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.8.34322.80
    • Windows 10 SDK version 10.0.22000.0

[✓] Android Studio (version 2023.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0--11185874)

[✓] VS Code, 64-bit edition (version 1.87.0)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.84.0

[✓] Connected device (4 available)
    • NX769J (mobile)   • FY23328102EA • android-arm64  • Android 14 (API 34)
    • Windows (desktop) • windows      • windows-x64    • Microsoft Windows [Version
      10.0.22631.3155]
    • Chrome (web)      • chrome       • web-javascript • Google Chrome 121.0.6167.86
    • Edge (web)        • edge         • web-javascript • Microsoft Edge 122.0.2365.80

[✓] Network resources
    • All expected network resources are available.

• No issues found!

NX769J (mobile)   • FY23328102EA

@Anti049 What device is this ? Can you provide make and model ?
Also, could you confirm if this only happens when you use "Debug" (and not "Run"), or occurs with both options and also try capturing a log (please remove anything sensitive before sharing):
Run the Dart: Capture Debugging Logs command
Reproduce the issue
Click Cancel on the logging notification to stop logging and open the log
Remove anything sensitive from the log
Attach the log here, in a gist,

The device is a Nubia REDMAGIC 9 Pro.
Issue still occurs when running without the debugger, as seen here.

I am unable to replicate this on Android 14 device which isn't similar to the one mentioned above.
Based on the report, I'll keep the issue open for team's input / attention.
There's a similar issue open but it is for ios https://github.com/flutter/flutter/issues/129246
/cc @DanTup for thoughts.

Issue still occurs when running without the debugger, as seen here.

Setting "dart.allowFlutterForcedDebugMode": false in your settings might fix this for Run (not Debug), at least temporarily. In order to support some functionality, we now default to attaching a debugger even in Run mode (which means a failure to attach a debugger affects both modes). That flag opts-out of this behaviour.
As for the original issue, this feels like something that came up in the past when the logcat output wasn't being captured correctly (for example in one case the VM Service URL was being censored by manufacturer tweaks and in another it only worked when called through a shell).
It may be useful to run adb logcat and capturing the output when trying to launch the app to see whether there's any useful output there (I don't think the log captured above includes everything). I believe the app should print something like "VM Service listening on " and Flutter would detect that.

Setting that setting to false in VS Code DOES allow me to run without debugging, but couldn't find anything like that in the logcat (found 3 lines relating to VM Service, but all just say either "sarting" or "success"). Please see the logcat output below.
Logcat Output

@Anti049 was this log captured while you tried to launch in debug mode? Oddly, there is no mention of Dart or Flutter in the whole log. There are a few mentions of "VM Service" but it's not clear to me whether that's the Dart VM Service or an unrelated program ("D<EMAIL_ADDRESS>TrustedUI-VM service starting." - I don't know what TrustedUI is).
Out of interest, if you run from the terminal with flutter run, does it print a VM Service URL ("A Dart VM Service on Windows is available at") and can you hot reload with r?

I got this log by running adb shell -x logcat from the terminal and then running in debug mode from VS Code. Is there another way to capture the log you're looking for?
Running flutter run from the terminal directly launches the app on the device as it should, but the terminal is still stuck on "Waiting for VM Service port to be available...", and that's the only mention of VM Service in the whole output.

Thanks, I suspect that would be the case (and confirms it's not specific to how VS Code is starting the app).
Running that same command here (on a Pixel 4a) does work as expected, in the output I can see:
03-14 14:47:25.127  9725  9785 I flutter : The Dart VM service is listening on http://<IP_ADDRESS>:39177/wQC1nUoLATg=/

It's possible that it not showing up in the logs is the cause of this problem - the flutter tool is scanning those logs to find the VM Service URL, but it's not finding it.
Unfortunately I don't know a lot about logcat/Android so this might need input from someone that knows more in this area. https://github.com/flutter/flutter/issues/82520 was caused by a manufacturer filtering out URLs in the logcat output - it's possible this is something similar (but maybe they're filtering the whole row instead of just replacing the URL with asterisks), but I had a quick search and wasn't able to find any other complaints of this nature.
Also - it's a long shot, but it may be worth looking through Debugging settings on the phone (presumably where you enabled USB Debugging) to see if there are any options that seem to be related to logs that might be filtering them.

No luck with the developer settings, unfortunately.

When using flutter3.16.7, the same problem occurs even with an empty flutter project on Nubia Z50Ultra on Android 14, but runs fine on Android 13.

I have a red magic 8 pro on android 14 and I face the same issue.

FYI @reidbaker, this is something we should probably keep an eye on

I have the same issue

Currently having the same issue

Currently having the same issue

i want to add that I have a Redmagic 8S Pro (NX729J), and that this problem arrived just after i upgraded to Android 14

I have Android 12 and I have same issue and I just recently used java 21 as well as downgraded my flutter version

I have Android 12 and I have same issue and I just recently used java 21 as well as downgraded my flutter version

I'm also looking for solutions but it looks like a recent problem

@Jemina15 may I ask what device you are running into this issue with? I am curious whether this issue is only affecting Nubia devices.

@Jemina15 and @SawyerGuo, may I ask what device you are running into this issue with? I am curious whether this issue is only affecting Nubia devices.

yes, Nubia

Nubia devices

I use Honor X6

To summarize, I'm guessing the tool is getting stuck here
https://github.com/flutter/flutter/blob/80042124ad461548fcd518e7d41557d59cc5405b/packages/flutter_tools/lib/src/android/android_device.dart#L705-L711
which would mean the flutter tool never sees a line in the device log matching this pattern
https://github.com/flutter/flutter/blob/c9d4c749b54e7411f9a8f2fe6060e66383db734a/packages/flutter_tools/lib/src/globals.dart#L297
As @DanTup pointed out earlier, it's possible that either 1) this line is not appearing in the device logs at all; or 2) it is appearing, but its contents are being tampered with by the OS. To try to figure out which of these is the case, I'd like to see more examples of device logs after running flutter run (similar to what @Anti049 provided earlier).

If anyone experiencing this issue would like to help, you can produce your own logs by following these steps:

Run adb logcat -c to clear the log buffer
Run adb logcat > out.txt to stream the device's log buffer to a file
flutter run to start the app (or do so through VS Code)
Once the app is running, copy the contents from out.txt into a GitHub gist (or some other text sharing tool) and provide a link to it in this issue thread. It would also be ideal if the device model, Android version, and output from flutter doctor -v is also provided.

For example, I did this with an emulator and got this from logcat. I see
05-13 12:17:22.260 15613 15696 I flutter : The Dart VM service is listening on http://<IP_ADDRESS>:35595/XOCg3_e_sG4=/

This is mainly happening on Nubia devices[^1], and I don't have a good understanding of how popular these devices are (and how critical it is to be able to debug Flutter apps on them). As a result, I do not consider this issue to be high enough priority for me to obtain one of these devices and troubleshoot it myself.
[^1]: We have a report of this happening on an Honor X6, but I want at least one more report of this happening on an Honor device before thinking of this as a confirmed issue on Honor devices.

logcat gist
@andrewkolos

definitly is a problem with android 14, i tried my program with another phone, a oneplus 7 pro with android 12, it works

flutter doctor -v, physical device, and logcat output
This is my first time using gist and logcat, so I had a hard time figuring out things HEHEHEHE.

Unable to provide logs, but I have a user reporting a black screen for a Red Magic 7 Pro (NX709J) running Android 13

Hi, I have the same issue. Developing on a Linux host (Linux Mint 21) against a Redmagic 9 pro phone.

Potentially related https://github.com/flutter/flutter/issues/148402

Please, is there any update on this issue?.
Or any hack we can use for now.

same problem "nubia red magic 8 pro" [android 14]

I believe I have the same issue with my Honor MagicPad 2, but I can only reproduce it running the app from VSCode or Android Studio, while connected to the device via wireless debug. See my case here #156437.
Log evidence:
VSCode run logcat output
VSCode run verbose output
Android Studio run logcat output
CLI run logcat output

If anyone experiencing this issue would like to help, you can produce your own logs by following these steps:

Run adb logcat -c to clear the log buffer
Run adb logcat > out.txt to stream the device's log buffer to a file
flutter run to start the app (or do so through VS Code)
Once the app is running, copy the contents from out.txt into a GitHub gist (or some other text sharing tool) and provide a link to it in this issue thread. It would also be ideal if the device model, Android version, and output from flutter doctor -v is also provided.

For example, I did this with an emulator and got this from logcat. I see
05-13 12:17:22.260 15613 15696 I flutter : The Dart VM service is listening on http://<IP_ADDRESS>:35595/XOCg3_e_sG4=/

This is mainly happening on Nubia devices[^1], and I don't have a good understanding of how popular these devices are (and how critical it is to be able to debug Flutter apps on them). As a result, I do not consider this issue to be high enough priority for me to obtain one of these devices and troubleshoot it myself right now.
[^1]: We have a report of this happening on an Honor X6, but I want at least one more report of this happening on an Honor device before thinking of this as a confirmed issue on Honor devices.

I followed these instructions on @andrewkolos ' comment

@tomassasovsky thanks - in that case I'm not sure why it looks like only errors were showing, but I do wonder if that may be the problem. I don't know a lot about logcat though so maybe @andrewkolos will have some ideas.

Waiting for VM Service port to be available...
for Redmagic and nubia phones（Android 14 and 15）, please operate according to the following methods:
method 1: run "adb shell setprop log.tag I"  (invalid after reboot)
methed 2: setiings ==》About phone ==》Feedback ==》Click the settings button at the top right corner ==》opne  "Log always on"

This worked @hustchcheng . Thank you very much.

Waiting for VM Service port to be available... for Redmagic and nubia phones（Android 14 and 15）, please operate according to the following methods: method 1: run "adb shell setprop log.tag I" (invalid after reboot) methed 2: setiings ==》About phone ==》Feedback ==》Click the settings button at the top right corner ==》opne "Log always on"

I couldn't find the Feedback option, but the ADB method worked for me.
I see a "logging" option when I use the search bar in the settings screen, but it closes immediately when I select it.


When comletion item 'mainEdit' is a deletion, it is silently converted to an insertion

This is an example of the kind of item that triggers this behavior:
{
   "label":"foo.nested.bar.bar",
   "kind":"Field",
   "detail":"String",
   "sortText":"00000",
   "filterText":"foo.nested.bar.bar",
   "insertTextFormat":"Snippet",
   "textEdit":{
      "range":{
         "start":{
            "line":5,
            "character":0
         },
         "end":{
            "line":5,
            "character":16
         }
      },
      "newText":""
   },
   "additionalTextEdits":[
      {
         "range":{
            "start":{
               "line":3,
               "character":10
            },
            "end":{
               "line":5,
               "character":0
            }
         },
         "newText":"\n      bar: \nother:"
      }
   ],
   "command":{
      "title":"Move Cursor",
      "command":"sts.vscode-boot.moveCursor",
      "arguments":[
         "file:/tmp/workingcopy7749208753331224087.yml",
         {
            "line":4,
            "character":11
         }
      ]
   },
   "data":"1"
}

I think the salient detail is that in the main textEdit we have this:
"newText":""

I.e. the 'newText' field is set to a empty string.
Instead of deleting the text, as I would expect in this case, instead the completion label is being inserted. This ends up adding unwanted junk.
PS: You may be wonder why we are making 'strange' completions like this one. We have the restriction discussed here https://github.com/Microsoft/language-server-protocol/issues/92 to blame for that. Particularly our attempt to workaround it are described in one of the recent posts. If you really want to know, you can read it there: https://github.com/Microsoft/language-server-protocol/issues/92#issuecomment-395598448 Unfortunately, the workaround doesn't even work because the language client misinterprets a deletion edit and turns it into an insertion.

This just a guess on my end, but I think something is probably checking the newText for 'falsyness' in the usual javascript way. So when the text is empty string it counts as 'false'. This 'theory' is confirmed by a workaround that I use. I have changed the deletion by something that inserts as space instead. We don't really want to insert a space (so this is still unwanted 'junk') but at least the junk is 'almost invisible' so the user isn't as likely to notice and be annoyed by it. The workaround works so this pretty strong evidence that the reason it behaves this way is precisely because the newText is "" (since everything else about the completion item is exactly the same).

PS: I filed the bug with the client, but it is also possible the 'bug' is actualy in vscode. I couldn't really determine exactly who is the blame here (I tried debugging it a bit and also did some searching in both vscode and the client source code on github but after about an hour I gave up because I wasn't getting anywhere).

I need to craft an example to see why this is failing. One idea might be that the main and additional edits are touching.

Would it help if I provide a .vsix file with version of our extension that creates these 'weird' completion items? (Along with some instructions to invoke so it does indeed produce it) That wouldn't be too hard for me to do. Just need to checkout the right branch and build it.

I'll just assume the answer to 'would it be helpful' above is yes.
This is the .vsix file. (Note I renamed it to .zip because github wouldn't take the attachement otherwise).
vscode-spring-boot-0.3.1.vsix.zip
Unfortunately there are a few steps to setup enough context to invoke the completion. First you need a simple spring-boot project. To save some hassles. I've created one and zipped it up. It also includes the a sample application.yml ready for you to invoke the CA engine:
hello-world-service.zip
Unzip this archive. Then open vscode with the archive folder as 'workspace root'. Open the 'application.yml' file which should have this contents:
server:
  port: 6666
spring:
  application:
    name: bork
servad
#Put cursor at end of line before this one and invoke CTRL-space select first completion (server.address).

You will notice junk gets inserted right after the word 'bork'.
If no completions come, you may need to wait for the extension to obtain classpath information (from maven which may take a bit of time, depending on the state of your maven cache).

IMO the conversion code does the right thing. I added a test here: https://github.com/Microsoft/vscode-languageserver-node/blob/master/client-tests/src/converter.test.ts#L752
@kdvolder can you please explain what you would expect?

I would expect that the text in the given example 'servadd' is deleted because the 'newText' in the textEdits is the empty string (so the text in the range should be replace with nothing.
When I filed this bug, that was not happening, instead the text is replaced by the completion's label.
It is possible that somehow this bug already got fixed. Let me try to reproduce in a more recent vscode release.

Bug still is reproducible with the artefacts I attached. But I guess though I am using a current version of vscode :
Version: 1.39.2
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:33:40.634Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.15.0-66-generic

That is still using an old vscode-language-server client.  So I should find some time to try an upgraded client somehow. That is unfortunately a bit more involved as I have to upgrade our extension's ls client version. I will add this to my todo list and try to get to it soon.
BTW: I looked at your test case but I don't see where it is checking the result of applying the edit to the document.
To give you an idea of what I saw going wrong is... editor starts with this contents:
server:
  port: 6666
spring:
  application:
    name: bork
servad

We invoke content assist at the end of servad and select the completion with label server.address.
What we get after the completion is applied is:

server:
port: 6666
address:
spring:
application:
name: borkserver.address

Notice that the label text was inserted after `bork`. No text should have been inserted there because the completions textEdit is the empty string. So instead the result should have been:

server:
port: 6666
address:
spring:
application:
name: bork

I found the code that hit this bug in a 1.5 year old branch that was never merged to master (partially because of this bug really standing in the way of it working properly).
Unfortunately I cannot easily get this code to compile as is at the moment and so reproducing this bug is really rather hard for me.
Basiscally, the feature we were trying to implement in that branch was eventually implemented in another way so that it works properly only in Eclipse. Essentially we return a main edit that encompasses all document edits and uses snippet place holders to indicate cursor position target.
In vscode it doesn't work because of the restriction on the main edit range being completly inside the 'current line'. I think you might remember us having discussions about this a long time ago.
Anyhow, as far this issue is concerned, I have no easy way today, after 1.5 years of no repsonse, to verify if it still occurs. And I don't also care that much anymore since we essentially have long given up on making the affected feature work on vscode and have instead settled for just making it work in eclipse.
I am guessing this bug does probably still occur but as I can't really try it to confirm this, feel free to close this ticket if you don't want to spend more effort on it yourself.

Looking at this again the only problem I can see right now is the fact the the insertion format is snippet with an empty string. I have the feeling that this might cause problem when trying to delete text. Will invest into a standalone sample.

Actually the snippet delete works as expected:
// The module 'vscode' contains the VS Code extensibility API
// Import the module and reference it with the alias vscode in your code below
import * as vscode from 'vscode';

// this method is called when your extension is activated
// your extension is activated the very first time the command is executed
export function activate(context: vscode.ExtensionContext) {

	vscode.languages.registerCompletionItemProvider({ language: 'plaintext' }, {
		provideCompletionItems: () => {
			let result: vscode.CompletionItem = new vscode.CompletionItem('Snippet Delete');
			result.range = new vscode.Range(0, 0, 0, 10);
			result.insertText = new vscode.SnippetString('');
			return [result];
		}
	});
}

// this method is called when your extension is deactivated
export function deactivate() {
}

Actually there is something wired since this is not working as expected:
connection.onCompletion(
	(_textDocumentPosition: TextDocumentPositionParams): CompletionItem[] => {
		// The pass parameter contains the position of the text document in
		// which code complete got requested. For the example we ignore this
		// info and always provide the same completion items.
		return [
			{
				label: 'Snippet Delete',
				textEdit: {
					range: { start: { line: 0, character: 0 }, end: { line: 0, character: 0 } },
					newText: ''
				}
			}
		];
	}
);

However I have no idea why this fails since this code works as expected:
	const p2c = createConverter();

	vscode.languages.registerCompletionItemProvider({ language: 'plaintext' }, {
		provideCompletionItems: () => {
			let result = p2c.asCompletionResult([{
				label: 'Snippet Delete',
				textEdit: {
					range: { start: { line: 0, character: 0 }, end: { line: 0, character: 10 } },
					newText: ''
				}
			}]);
			return result;
		}
	});

which calls the same conversion code :-(

There is clearly something broken.

I found it. This only happens if the server provides a resolve completion handler. When we convert the VS Code completion item back into a protocol completion item we loose information. I guess a wrong interpretation of a falsy value (e.g. '')

Code that makes it fail:
export function activate(context: vscode.ExtensionContext) {

	const p2c = createProtocolConverter();
	const c2p = createCodeConverter();

	vscode.languages.registerCompletionItemProvider({ language: 'plaintext' }, {
		provideCompletionItems: () => {
			let result = p2c.asCompletionResult([
				{
					label: 'Snippet Delete',
					textEdit: {
						range: { start: { line: 0, character: 0 }, end: { line: 0, character: 10 } },
						newText: ''
					}
				}
			]);
			return result;
		},
		resolveCompletionItem: (item) => {
			return p2c.asCompletionItem(c2p.asCompletionItem(item));
		}
	});
}


Re-examining fields in NXDistortion

[ ] Suggestion:The field, 'field', that currently takes in two 2-d arrays to handle separately, the rdeform_field and cdeform_field.
[ ] The fields 'original points_x' and 'original points_y' to merged into a single field, 'original points' ?

I generated a new version of NXdistortion in the gitlab repository, please update the config file correspondingly.

Done. The converter doesn't break (in my newly cloned forked repo) if the new base classes aren't present in the definitions folder. For ex: even if there is no NXDistortion in the definitions folder, it works smoothly. Something that I don't understand.

Do you maybe use the same venv? chec what the location of your installed parser-nexus installation is. The definitions are pulled relative to this installation, not from where you call the convert.py (it includes the parser-nexus package, and that is pulled from a different place potentially).

Sorry, missed this.
I see. Yes, I am using the same venv wherein I have the nexusparser installed. It is also using the main repository's helper.py etc. Is it then needed to have a new venv?

Either that or you re-install the nexusparser package or your new branch/checkout in the venv with pip install -e . [all]


jenssegers/mongodb v3.1.0 requires mongodb/mongodb ^1.0.0, what does it mean?

Hi! I want install the package, however I can't because I don't cover all requeriments for that:

Problem 1
- jenssegers/mongodb v3.1.0 requires mongodb/mongodb ^1.0.0 -> satisfiable by mongodb/mongodb[1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.1.1].

If I check
mongodb --version
it shows that my current version is 3.2,so what's going on?
Thanks!

Nevermind I just put the mongodb extension in my php.ini and then the installation was successfully,


What changes are needed for web api connectionString from development to publishing?

I created a simple aspnetcore application with user authentication (so all the Entity Framework has been preloaded into the web app template). It is connecting to my database with the connectionString that is located in my appsettings.json file, with data source = {computerName}\\{serverName}" setup. The database instance and Visual Studio are located on the same machine. This works fine in returning data to the web api while within development and debugging mode. When I publish it and try to go to the site from a domain name it does allow me to view the webpages that are not needing database connection but the rest that need data from the database returns pages like this:

Error.
An error occurred while processing your request. Development Mode Swapping to Development environment will display more detailed information about the error that occurred.
Development environment should not be enabled in deployed applications, as it can result in sensitive information from exceptions being displayed to end users. For local debugging, development environment can be enabled by setting the ASPNETCORE_ENVIRONMENT environment variable to Development, and restarting the application.

Solutions I have tried from reading other posts is:
I have tried to change the Environment Variables for ASPNETCORE_ENVIRONMENT from Development to Production to no success.
I have tried adding "appsettings.Production.json" to publishOptions in my project.json file, even though there is no file appsettings.Production.json, and this did not help. dotnet publish
Adding the environment variable in the web.config file did not work Deployment development
I have tried reading through documentations intended to teach and explain how to create applications and more but this has not help me resolve my issue. The only last thing I can think of is that maybe I am incorrect in how I understand the connection string. If the web api uses the connection string to connect to the database from the server-side then it should work just fine like it does when in development calling to http://localhost:port# since its all on the same  machine. BUT if the database string needs to be based on a client-side call then it would have to be with domain names and IP addresses.
Can someone tell me which one it is? Is there any help to be received from experts out there in getting a basic web api to display data from a database outside of the internal network?

The only thing else that comes to mind is that there is something I am not doing, and need to do, inside of IIS Manager. I see connect string there as well but unsure what that is for our does since the connection string is inside the application. Also maybe I am suppose to give the app some kind of authorization to communicate with the database server even though they are on the same machine???


MdDialog not opening on iOS Safari

Bug, feature request, or proposal:
Bug
What is the expected behavior?
The dialog should Open
What is the current behavior?
The dialog doesn't open and stop progress when reopen dialog
https://material.angular.io/components/dialog/examples had same problem now.
CodePen and steps to reproduce the issue:
CodePen Demo which shows your issue:
https://stackblitz.com/angular/pxglmmxpyejr?file=app%2Fdialog-overview-example.ts
Detailed Reproduction Steps:
on Safari or Chrome with iOS
Step1. click Pick one button
Step2 . close dialog
Step3. click Pick one button
What is the use-case or motivation for changing an existing behavior?
Which versions of AngularJS, Material, OS, and browsers are affected?

Angular: 5.2.7
Material: 5.2.4
OS: iOS 10.3
Browser: Safari and Chrome

Is there anything else we should know? Stack Traces, Screenshots, etc.

Hi, I just tested the stackblitz code and it seems to be working on iOS. However, I cannot open dialogs when building with prod yarn run ng build--prod with<EMAIL_ADDRESS>related to the new Directionality service where the Injector can't seem to locate the service at run-time. This only happens on prod builds.
I'm trying to debug it at the moment and post an update if I can find the solution.

This one is very odd. I wasn't able to reproduce it on a couple of iOS 11 devices, but I did manage to get it on a few rare occasions when running an iOS 10 device through the simulator. What's weird is that I could only get it through the Stackblitz and our docs site, but not in the demo app that's running against master. Furthermore, it seems like the element is in the DOM and it gets the proper styles (in this case transform: none and opacity: 1), but the browser decides not to render it for some reason. If I trigger a style recalculation manually (e.g. by toggling the box-shadow through the dev tools) it ends up displaying, but it's hard to know whether doing something like that from Material would fix it since I can't reproduce it consistently.

@crisbeto I have iphone5 that ios latest version last v10.3.3. so I was reproduce aways.
and i found other odd one. See the this movie
https://youtu.be/W1f8NrrlKb0

That's what I was getting as well. The interesting thing is that if you switch to another tab and then switch back, the dialog will show up.

@crisbeto And I wasn't able to reproduce When  I was added an style attribute display: block to '.cdk-overlay-container',

How did you add it @insanehong? Was it through the dev tools after the dialog is opened, or through a stylesheet? If it's the former, you saw the dialog, because you triggered a style recalculation manually which caused the dialog to be repainted. Otherwise setting the container to display: block shouldn't make a difference, because it's a div which is a block by default.

Same for me with iPhone iOS 11.3
Capture on iOS:
https://drive.google.com/open?id=1MfI1x8O5mtInDLgnNYfrqPeqpO5kpLPd

I found the solution, uncomment what you need in the file "polyfill.ts", I had completely forget that this file existed

I have the same issue on iOS 10.2.1 and 10.3.3 (but cannot reproduce it on iOS 11). Dialog shows up when I trigger style recalculation in dev tools or switch to another tab and switch back.
@yacineblr It seems that you have problem with closing dialog, not with opening. Polyfills haven't solve this for me.

Same problem. I can open dialog window but can't close it. This bug appears on IPhone 7 with IOS 11.3. On 10.1.1 works fine.
P.s Polyfills haven't solve this for me as well.

This is really odd, but all my safari problems are gone after

Removing import 'web-animations-js' polyfill
Providing NoopAnimationsModule instead of BrowserAnimationsModule in app.module.ts

What's even more puzzling is that all the animations actually work on Chrome an ios too..

I solved this by adding pointer-events: auto; to .cdk-overlay-container.

Same problem on iPad Pro ios 10.3, dialog doesnt shown. @swftvsn and @raimonfuns advices not work for me.

@swftvsn I also fixed it with this way but some animations are broken on Safari desktop.

Has anyone been able to sort this? I'm still having this issue and haven't found a way to get around it (apart from creating my own modal service using Angular Portals).

So, I've spent the better part of my working day (5 hours!!) trying to fix (what I thought) was an issue with Angular Material. Fortunately, I don't think there's an issue with Material, but I do think that there is an issue with the older versions of webkit that are used on iOS 11 and downwards.
Like @crisbeto said, the modal gets added to the DOM and everything seems to be correct up until the point where it comes to displaying it. As we all know, this is not Angular's job but the rendering engine.
To fix this, I simply force a re-render of the cdk-overlay-container by changing the CSS text after the modal opens and then changing it back to the original again.
const dialogRef = this.dialog.open(MyComponent);
dialogRef.afterOpen().subscribe(() => {
    const elements: any = document.getElementsByClassName('cdk-overlay-container');
    elements[0].style.cssText += ';-webkit-transform: rotateZ(0deg) !important';
    elements[0].style.cssText += ';-webkit-transform: none !important';
});

I haven't seen any issues because of this yet.
cc interested parties: @rkajbaf @mezhik91 @raimonfuns @marcinbialkowski @insanehong

@elsyms I tried your solution on a virtual device running iOS 10.3.2 and 10.3.3 but it didn't work. I unfortunately don't have access to a real device to confirm this is working.

I figured out, that

 is not added to the DOM on iOS 12.1.4. Even adding this div manually to the index.html does not solve the issue, as no child element is added when clicking on the menu trigger button. I tried several workarounds from github, but none did work for me.
The menu will popup normally, when the body height is > than 100vh. If the height is smaller than 100vh the menu is not shown on iOS Safari. But just adding min-height: 100vh; does not have an effect.

Closing since I can't reproduce it anymore and the description is pointing to a very old iOS version.


[MM-13160] Add infinite scroll to Select Teams screen

Summary
MM-13160 - Add infinite scroll to Select Teams screen
Ticket Link
https://mattermost.atlassian.net/browse/MM-131605

Thanks @AGMETEOR, how is this going, can we provide any guidance?

@esethna I have delayed because I was traveling to the US... but I am basically remaining with writing tests and then I can seek some guidance

@esethna I am getting docker-build: blocked but all other pipeline checks are passing. I don't know what the issue is there.

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

@AGMETEOR Just did a quick review and it looks great  🎉. Thanks. Let us know if you have any questions

Thanks @AGMETEOR is this PR fully functional and ready for testing?

New commit detected. SpinWick upgrade will occur after the build is successful.

@esethna I have just implemented @sudheerDev 's feedback. It should be ready for testing now and subject to more feedback

Spintmint test server creation failed. See the logs for more information.

New commit detected. SpinWick upgrade will occur after the build is successful.

Spintmint test server creation failed. See the logs for more information.

New commit detected. SpinWick upgrade will occur after the build is successful.

Spintmint test server creation failed. See the logs for more information.

Hi, @esethna build docker stage has been hanging since yesterday evening.

@hanzei any ideas on how to get the build passing?

@esethna Updated the build

Spinmint test server destroyed

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Thanks @sudheerDev

@AGMETEOR just an FYI, we are working on putting some test teams on this server so we can get a QA and PM pass on this PR

@enahum Can we get someone on our team to insert the test data? https://community-daily.mattermost.com/core/pl/nf5uamjy9pfqfeg6ys8oku1iqw

New commit detected. SpinWick upgrade will occur after the build is successful.

Spintmint test server creation failed. See the logs for more information.

Spinmint test server destroyed

@AGMETEOR just an FYI, we are working on putting some test teams on this server so we can get a QA and PM pass on this PR

@esethna thank you for the update

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Spinmint test server destroyed

@esethna the pipeline still fails on build-docker, it says "unauthorized"

@AGMETEOR I've restarted the build. Should be fine now.

@AGMETEOR I've restarted the build. Should be fine now.
Thank you @hanzei

@hanzei, unfortunately, build-docker is still blocked :(

@hanzei, unfortunately, build-docker is still blocked :(

Build is fine now

@AGMETEOR Changes look to me. Just one comment about the third param. I don't know if it on our API end but as we are not consuming it can we remove that?
@esethna Changes look good to me i added teams to the spinmint as long as we dont kill it we should be good for testing.

Test server creation failed. See the logs for more information.

Test server creation failed. See the logs for more information.

Creating a new SpinWick test server using Mattermost Cloud.

Test server creation failed. See the logs for more information.

Creating a new SpinWick test server using Mattermost Cloud.

Test server creation failed. See the logs for more information.

Test server creation failed. See the logs for more information.

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

New commit detected. SpinWick will upgrade if the updated docker image is available.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

Test server creation failed. See the logs for more information.

@AGMETEOR PR looks good to me. Would you be able to merge master into this so i can have a spinmint up for @esethna to test?
This isn't an easy PR to work on and we really appreciate the help here.

@AGMETEOR PR looks good to me. Would you be able to merge master into this so i can have a spinmint up for @esethna to test?
This isn't an easy PR to work on and we really appreciate the help here.

I appreciate all the feedback to make this PR better. Dedicated to seeing it through.

New commit detected. SpinWick will upgrade if the updated docker image is available.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

Test server creation failed. See the logs for more information.

Test server destroyed

Creating a new SpinWick test server using Mattermost Cloud.

Test server creation failed. See the logs for more information.

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

@sudheerDev @AGMETEOR let me know if there are questions on the above feedback or when it's ready for re-review?

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei

Thanks!

When the "Join Another Team" menu item is clicked, the page seems to load all available teams rather than loading one page and loading more while scrolling:
If I refresh, it loads only one page of teams which is good, but it seems to make the call to get more teams too late. I almost have to be at the very bottom before it pulls in the new teams. Im guessing we should make the call for more teams when the user is ~15 (Sudheer feel free to offer other suggestions) rows from the bottom to make it a smoother experience.

Loading indicator is off-screen as ST mentioned

Hello @esethna ,
Thank you for the review.
1 > Looks like when a user joins a team, a call is made to redux to fetch all the teams and thus they're added to the teams entities. I have made a modification that should now be a workaround this behavior
2 > I have changed a props valuebufferValue to a larger number such that more teams are loaded much earlier
3 > I think because we start loading more teams before the user reaches the bottom, and then hide the loader as soon as the loading is done, it's possible on a fast network the loader disappears very fast. I tried on a slow network and when I reach the bottom the loader shows.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit e9b7168b378768239ab8c64b33d71a1aad9690ec.
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Can someone please add test data? Also, if it's not too much to ask, please add steps on how to add test data, as I would like to know how to do this in the future.
Thank you.

Removing from the v5.18 milestone as it's still under review.
@sudheerDev can you help add the test teams >200?

@AGMETEOR I also found an issue where the scroll bar appears when unnecessary and allows minor scrolling:

Removing from the v5.18 milestone as it's still under review.
@sudheerDev can you help add the test teams >200?
@AGMETEOR I also found an issue where the scroll bar appears when unnecessary and allows minor scrolling:

Let me work on fixing that...

Can someone please add test data? Also, if it's not too much to ask, please add steps on how to add test data, as I would like to know how to do this in the future.
Thank you.

i added the teams here. I have this script https://gist.github.com/hmhealey/5329fa5852b66952f2e22f46b00e7e93 to make teams. You would need go to run this. Mention me if you need teams on it. I can do it for you

@AGMETEOR let us know if you need any help and when it's ready for re-review?

Hi @esethna sorry I had sort of forgotten about this. Let me make changes and get back

New commit detected. SpinWick will upgrade if the updated docker image is available.

Removing from the v5.18 milestone as it's still under review.
@sudheerDev can you help add the test teams >200?
@AGMETEOR I also found an issue where the scroll bar appears when unnecessary and allows minor scrolling:

Hi @esethna , worked on the scroll bar issue.

Test server creation failed. See the logs for more information.

Test server destroyed

Creating a new SpinWick test server using Mattermost Cloud.

Test server creation failed. See the logs for more information.

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei

/update-branch

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

@sudheerDev Can you help add test teams >200 on the above test server?

@jasonblais Done adding teams

Hey, There is one request i made previously as well. i don't know if you missed it. Can we add the loader to the list as a default and remove it if it is not needed.
The way it works as of now is that you scroll to the bottom of the list we start the API call and add loader and the remove it when the API returns.
Can we add loader as default and only remove it if a subsequent API cann has not teams? That way loader is always at the bottom and it does not exist if there are no new teams that can be added

@esethna Apart from my one comment above. I am good with the PR. I suggest we make a separate ticket and have appteam or @AGMETEOR adreess it in a separate PR. Thoughts?

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei

FWIW this screen doesn't look or work great when browser height is limited. Here's what it looks like at 680px high. Only three rows show:

Test server destroyed

@AGMETEOR will spark up another test server for me review, it was destroyed yesterday. Thanks 😄

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

New commit detected. SpinWick will upgrade if the updated docker image is available.

FWIW this screen doesn't look or work great when browser height is limited. Here's what it looks like at 680px high. Only three rows show:

@adamjclarkson thanks for the review. I made a small rework of that screen and I think it's much better now.

Test server creation failed. See the logs for more information.

Awesome thanks @AGMETEOR !

@AGMETEOR will you add a bunch of teams for me to test the infinite scrolling. I tried using the /test commands but it keeps failing for both sysadmin and user-1 users.

I've created 20 teams by hand.
The /test command doesn't work currently. I've filled https://mattermost.atlassian.net/browse/MM-21732 to track this.

@AGMETEOR will you add a bunch of teams for me to test the infinite scrolling, I only see one team. I tried using the /test commands but it keeps failing for both sysadmin and user-1 users. Thanks 😄

Added 200 teams+,
@hanzei You can use https://gist.github.com/hmhealey/5329fa5852b66952f2e22f46b00e7e93 for this, makes it easier

@sudheerDev Thanks for linking it. I also ended up writing a go script to do this :wink:

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit c052f7daf2a1f9ad177df3df1c3e1cae830a7bad.
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

Hello @andrewbrown00 , thanks for reviewing. With the help of some core team members teams have been added for your review.

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei

Hey @devinbinnie and @sudheerDev - kind reminder to help with a PR review :)

/update-branch

Error trying to update the PR.
Please do it manually.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit 5bf4b90204460238a53400785a08b7096a8448e8.
Access here: https://mattermost-webapp-pr-3165.test.mattermost.cloud

/update-branch

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server destroyed

Test server creation failed. See the logs for more information.


deb package creation and dependency based on node 4

based on PR https://github.com/RackHD/docs/pull/286,
@RackHD/corecommitters @benbp @jlongever @heckj

:+1:

:+1:


Make CODAP Flow

Changes

Remove update buttons
Make created tables always update

We need to figure out what to do with errors. Currently, any errors during updates crash the plugin. We need to figure out how to present errors to the user.

I added error handling, but the error messages are quite long.

There's also the question of what to do on multiple errors. We need a better way to indicate errors than the one place where some error message might appear.

Wooo! This is great. I think we should discuss what to do about errors at the next meeting, or maybe even ask Emmanuel at some point.
This looks great, and if the errors are verbose at least they give enough info to solve the problem. One thing I do notice though is if I run into an error, then fix the problem (add back in a deleted attribute, etc), the message persists, even though the tables update successfully. It would be nice to have the error get cleared somehow

if I run into an error, then fix the problem (add back in a deleted attribute, etc), the message persists, even though the tables update successfully. It would be nice to have the error get cleared somehow

The latest commit should fix this. I'm a little worried about errors overriding each other, but we can discuss that later.


feat: allow csv files for forecasting

Notes:
Fixing a bug in the summarizer where the calculator, if passing a number through, cast it to an integer and not a float.


Hashing should use mod q not mod q-1

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Today: hash.py is computing its result modulo q-1. This is an unusual choice but for the most part doesn't really matter, except when it does. With the HACL library, used in electionguard-cpp, the function Hacl_Bignum256_mod() has the constraint that it requires the modulus to be an odd number. q is odd. q-1 is even.
The "obvious" solution here is to just replace q-1 with q. This will have no meaningful impact on security or anything else, but will make implementations of ElectionGuard using HACL much easier to build correctly.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response

For the C++ code, Matt and I have already checked and this is not a problem.


Update SMTP Server docs

As #3398
Now the Admin Email field can support Username too, please update it.

Good. Will check this. It is relevant for those apps right?

discourse
taiga
gitea
mattermost

Please lmk if there's more.

@samaradel made a simple PR based on the discussion in #3398.
LMK if it's sufficient or if we need more changes.

@Mik-TF Perfect! let's apply it to the rest apps docs.

Done. Please review if possible the PR #649


[Feature] Support erasure code

Support erasure code:

The implementation idea of EC client, we refer to https://issues.apache.org/jira/browse/HDFS-7285.
Support for reading EC files.
Supports writing or appending to EC files.
Fix some bugs for functions complete, addBlock and abandonBlock.

Performance test results:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 3 committers have signed the CLA.:white_check_mark: M1eyu2018:x: liubingxing:x: tomscutYou have signed the CLA already but the status is still pending? Let us recheck it.

@alexey-milovidov  do you guys have time to review this PR?  Supporting erasure code is an very important feature for those clickhouse users who read data from HDFS.

We almost missed this PR. Let's fix the conflicts and continue.

We almost missed this PR. Let's fix the conflicts and continue.

@alexey-milovidov We have integrated intel isa-l to do EC related computation with higher performance, just check this PR https://github.com/ClickHouse/libhdfs3/pull/43. And we will close this PR later. Thanks.

We almost missed this PR. Let's fix the conflicts and continue.

@alexey-milovidov We have integrated intel isa-l to do EC related computation with higher performance, just check this PR #43. And we will close this PR later. Thanks.

I will close this PR.


SetMainViewport breaks Interaction with In-Editor GUI

Hey there,
I am currently working with v5.1.0 and Godot 4.2.2-stable, and I am having a problem while creating In-Editor GUIs. It seems that setting the Main Viewport breaks Input/Interaction.
To illustrate my problem, here's a simple In-Editor Tool.
@tool
extends Node2D

var show_gui: bool = false

func _ready() -> void:
    if Engine.is_editor_hint():
        show_gui = ImGuiGD.ToolInit()

func _process(_delta: float) -> void:
    if show_gui:
        ImGui.Begin("Example Tool")
        ImGui.Text("Lorem Ipsum")
        ImGui.End()

This correctly displays the GUI, and it's visible and interactable across the entire Editor including the 2D, 3D, and Script Views (Which i think is expected?).

However, I want the GUI to appear exclusively in the 2D Viewport.
To achieve this, I tried to use SetMainViewport() as following:
# in _ready()
ImGuiGD.SetMainViewport(EditorInterface.get_editor_viewport_2d())

Now the GUI only appears in the 2D View as desired, but It's not interactable.

Here is a project that shows this problem:
ToolProject.zip

Hey, thanks for including a project that reproduces the issue.
I should have documented this better, but using SetMainViewport with a SubViewport means that the user is responsible for pushing inputs to the SubViewport. Normally in 2D this would be handled automatically by a SubViewportContainer, but that's not working here. I'll try to figure it out when I have the time. Not sure if there's any good way to make it work, I don't want to mess with the editor internals.
This is a little kludgy because Godot doesn't seem to provide an easy way to check which main screen is active, but you could do something like this:
@tool
extends Node2D

var show_gui: bool = false
var button_2d: Button

func _ready() -> void:
    if Engine.is_editor_hint():
        show_gui = ImGuiGD.ToolInit()
        var title_bar := EditorInterface.get_base_control().find_child("@EditorTitleBar*", true, false)
        button_2d = title_bar.find_child("2D", true, false)

func _process(_delta: float) -> void:
    if show_gui and button_2d.button_pressed:
        ImGui.Begin("Tool")
        ImGui.Text("Lorem Ipsum")
        ImGui.End()

Your ImGui windows won't stay confined to the 2D viewport, but otherwise I think it solves the problem.

Thank you for the response/solution! What you provided is working great, and I will use this.
Ideally, I would like to have it confined to the viewport, but it's not a big deal. As you mentioned, it seems that Editor-Viewports handle inputs differently than usual SubViewports. Pushing inputs via an EditorPlugin also does not work, apparently.


Do not overwrite default linker flags so that LDFLAGS environment variable is considered

This fix is similar to https://github.com/osrf/gazebo/pull/2922, but in this case the problem also affected the CXXFLAGS variable.

Mind signing DCO, @traversaro ? Thanks!

Sure (I always forget). Done!

Mind signing DCO, @traversaro ? Thanks!

Sure (I always forget). Done!


Modernize Repository (First Pass)

[x] Reorganize Package Structure
[x] Packages Directly Reference Each other
[x] Format Code
[x] Update to Rust 2021 Standard
[x] Fix Various Package Incompatibilities
[x] Apply Clippy Auto-Fixes
[x] Fix Spelling Errors
[x] Basic Testing Workflow

ACK 196a87ae9f481b24be2cc6fa6a8bef44fae56835


OpenAPI: do not require artifactType

Fixes artifactType being required on model_artifact routes.
Description

How Has This Been Tested?

Merge criteria:

All the commits have been signed-off  (To pass the DCO check)

[ ] The commits have meaningful messages; the author will squash them after approval or in case of manual merges will ask to merge with squash.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work.
[ ] Code changes follow the kubeflow contribution guidelines.

If you have UI changes

[ ] The developer has added tests or explained why testing cannot be added.
[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Verify that UI/UX changes conform the UX guidelines for Kubeflow.

superseeded by https://github.com/kubeflow/model-registry/pull/538


Page layout mapping: define and implement model to define section emphasis of a section and/or vertical column

Done


Common settings/ Proxy-Server auto-scheduling / Scheduling greyed out

I included the file name .ps1 in the script location and now that part of the tool is not selectable.
We have tried uninstalling and deleting all file yet this is still an issue.
Thank you in advance.

After 15 minutes I was able to go to task schedule and deleted the DAT event to fix this.


Minor issue: Protocol missing from jquery qunit links

In the generated ...fsharp.head.js for a single-page application, the script tag pointing to jquery starts with http:// but the ones pointing to qunit-1.18.0.js and qunit-1.18.0.css begin with // with no protocol. This causes errors to show up in my console when browsing the html with the file: protocol.

I respectfully disagree. Allow me to offer a counterpoint:
Every external library should be referenced via protocol-relative URLs.
(you know... bold text wins arguments ;) )
My head.html/.js currently is
<script src="http://code.jquery.com/jquery-1.11.2.min.js" type="text/javascript" charset="UTF-8">

</script><!--[if lte IE 7.0]>
<![endif]-->
<!--[if lte IE 9.0]>
<![endif]-->
<script src="//code.jquery.com/qunit/qunit-1.18.0.js" type="text/javascript" charset="UTF-8">

</script><link type="text/css" rel="stylesheet" href="//code.jquery.com/qunit/qunit-1.18.0.css" />
<!--[if lte IE 9.0]>
<![endif]-->

The first line (link to jquery-1.11.2.min.js) would surely cause problems when served by HTTPS, for example. It should be protocol-relative, like the other two references to qunit (.js and .css)
@psfblair I understand you point. OTOH, please note that this would be just ONE of several glitches you would encounter when serving your application via file: protocol. The "recommended" way is to just serve it from a webserver. I surely can imagine you have you own reasons to not want this and just use the html file directly (been there, done that). But please mind some things would just not work as expected.
@intellifactory That said, WHY do we need an unit test library (qunit?) in the generated application?

I am closin this issue, as the splitting off of WebSharper.Testing means that QUnit is not included anymore.
On the topic of URLs, I agree with @fdcastel: external libraries should be referenced via protocol-relative URLs, and I will look into applying this for the JQuery link. If you need to browse your website via file: protocol, you can override the default URL in your application config file as explained here.


Feature Request: Curtain3 Support

Problem
I'm trying to add a Curtain3 device and I'm getting an error message saying Device: Right with Device Type: Curtain3, is currently not supported.
Solution
Add support for Curtain3 devices.
Alternatives
No response
Additional context
No response

I will get this into the next release.

I will get this into the next release.

Awesome to hear! Thanks!

Can you try the latest beta:

Click here to find out how to install Beta


pandas.StringDtype's optional argument is reported by pyright as not optional

Describe the bug
If I instantiate pd.StringDtype without args, pyright is complaining that it's missing an arg.
To Reproduce
import pandas as pd
d = pd.StringDtype()  # pyright says missing the storage arg, but that arg is optional
Please complete the following information:
Windows
pyright
pandas-stubs-<IP_ADDRESS>203

Thanks for the report.
Need to change https://github.com/pandas-dev/pandas-stubs/blob/b76dbb6952f661c6e8314bd8c1dfefeda181125d/pandas-stubs/core/arrays/string_.pyi#L10 to be  storage: Literal["python", "pyarrow"] | None = None with appropriate tests added to https://github.com/pandas-dev/pandas-stubs/blob/b76dbb6952f661c6e8314bd8c1dfefeda181125d/tests/test_dtypes.py#L127


Merge Sort algorithm :infinity: in any programming language :computer:

Merge Sort algorithm :infinity: in the relevant language folder :file_folder: in the main branch.
if language folder doesn't exist you can make folder :file_folder: and add your program in it.
You can find new languages in this Programming Language List.
Give star :star: to this repository.

can i do it in c and cpp

I'm Manasi Deshmukh
I have solution code in java
please assign this issue to me
@paradocx96

Hey, this is Ansh Charak, 4th Year UG at IIT Bombay
I can implement this in C++ and Python. Kindly assign this issue to me @paradocx96

Guys give star ⭐ to this repository.
@AnshCharak @shreya2663 @ManasiGDeshmukh @Pakeetharan

please assign this issue to me

Hey I am Hey I would like to add this algo in javaScript.
Would you please assign this to me?

Please assign this to me


[google_sign_in] Adds support for serverAuthCode.

Adds missing support for serverAuthCode in google_sign_in packages. Without this fix, it's not possible to do server-side authentification with Google sign-in.
This module has very limited tests. It's also very hard to test this fix automatically as it would include talking with Google's API:s, having access to API keys, and doing non-Flutter actions such as signing in through native code.
Fixes:
https://github.com/flutter/flutter/issues/57712
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [relevant style guides] and ran [the auto-formatter]. (Note that unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the [CLA].
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
[x] I updated CHANGELOG.md to add a description of the change.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[x] All existing and new tests are passing.

This module has very limited tests.

https://github.com/flutter/flutter/wiki/Plugin-Tests#faq-do-i-need-to-add-tests-even-if-the-part-of-the-code-im-changing-isnt-already-tested

It's also very hard to test this fix automatically as it would include talking with Google's API:s, having access to API keys, and doing non-Flutter actions such as signing in through native code.

An end-to-end test might be difficult, but unit testing each section to make sure the arguments are being passed thorough correctly should not be very difficult, and would prevent a type of bug we have had in the past.

Fixes:
flutter/flutter#57712

I don't see any Android changes here. Was this already fixed for Android?

I checked, serverAuthCode is retrieved correctly now. @stuartmorgan what prevents you from merging it?

@stuartmorgan what prevents you from merging it?

The unaddressed comments and questions in the comment directly above yours.

@karthik-js Please read https://github.com/flutter/flutter/wiki/Tree-hygiene#getting-a-code-review. Approving PRs is reserved for contributors; approving a PR as a non-contributor serves no purpose, and causes confusion for people following the state of the PR.


Add solhint support

Add support for solhint, a linter for the Solidity language.

@w0rp Is the last commit what you suggested?


Look into moving Google Analytics into a separate project

We certainly don't need it in forkable code.

Why do you want to move it?

Initially, we wanted to make forking the Saleor codebase easier but now that we have preliminary support for plugins this could easily become a plugin.


OU-446: Support FIPS

This PR looks to add FIPS support to the troubleshooting-panel. It updates the go version to 1.22, and uses recommended FIPS compliant images and tags. Due to some of the recommended images not being available publicly a Dockerfile.dev is added to the repo as a way to build and test images locally.

Downgraded to rhel8 to match COO rhel version in the most recent commit

/lgtm


Not support symbol status code

I expect to use rails status code.
send :ok when expected 200 but return 0.
Is webmock going to adapt rails status code?
stub_request(:get, url).to_return(status: 200, body: 'response')

status code: https://gist.github.com/mlanett/a31c340b132ddefa9cca

@4geru do you mean allowing for stub_request(:get, url).to_return(status: :ok, body: 'response') ? Would it make much difference?

I think it would make difference in a Rails project. Because I would use :ok for 200, :created for 201, etc. everywhere for readability.


config for initial vector providers

What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CLA Signed: DataStax CLA

The changes have been added to #1048


Possible improvement for the OrtEngine

Description
I think it would be interesting to add support for onnx models to disable session threadpools by using a shared global thread pool.
As far as my understanding of DJL goes, when we create one predictor of different models for each thread, we end up running several onnx sessions in parallel.
In my benchmarks being able to control the threadpool when multiple onnx sessions are run in parallel offers slightly better performance and better resource utilisation for some models.
Will this change the current api? How?
I thought about passing the option disablePerSessionThreads as a setter,  such as done for the other options from SessionOptions.
However It would also require to pass global thread pool settings through the OrtEnvironment.ThreadingOptions
The part where I got really stuck was because the method OrtEnvironment.getEnvironment() is called both in OrtEngine and OrtNDManager implementations. According to the Onnxruntime java API, there is no way to guarantee that the environment has the appropriate thread pool configuration. So if I pass ThreadingOptions to an environment and then retrieve it again, I will get an IllegalStateException.
I hacked a bit here
Who will benefit from this enhancement?
This benefits the use case in which more than one model instance is being used in parallel (for example, if we load a ZooModel  each in one GPU and do that for 4 GPUs).

@andreabrduque
OrtEnvironment use a global singleton. If you want to customize ThreadingOptions, you can call before DJL is loaded:
OrtEnvironment.getEnvironment(OrtLoggingLevel.ORT_LOGGING_LEVEL_WARNING, "ort-java", threadOptions);

DJL will pick the initialized OrtEnvironment.

Hey frank, thanks for the reply.
The problem with is that I need to be able to set [OrtSession.SessionOptions.disablePerSessionThreads()](https://javadoc.io/static/com.microsoft.onnxruntime/onnxruntime/1.7.0/ai/onnxruntime/OrtSession.SessionOptions.html#disablePerSessionThreads()) for the ThreadingOptions to make an effect, and those settings are passed through DJL.
I can make a PR to add that setter, but if users try to use the disablePerSessionThreads() without passing the global threading options, they will get an exception, but I can add a section to the docs to warn that.


Create a transportable media

Expected Behavior
We have a media which can "transport" a brix. This means: We print a Brix into TransportMedia, and then we can use BxTransported(data) to make a brix out of it again.
Data format should be XML.
Actual Behavior
Mention any other details that might be useful
Steps to reproduce the behavior
The log given by the failure.

Note: This is not the fastest way to transport a brix. Reconstructing from XML might be slow (plz evaluate) and for performance reasons, we could consider making the reconstruction fast by implementing it using raw bytes for transport instead of printing to a XNode.

Note: This is not the fastest way to transport a brix. Reconstructing from XML might be slow (plz evaluate) and for performance reasons, we could consider making the reconstruction fast by implementing it using raw bytes for transport instead of printing to a XNode.