Blocking call

Integration Version 1.7.0
HA: 2024.6.2
I get warnings in HA system log:
Detected blocking call to open inside the event loop by custom integration 'robonect' at custom_components/robonect/utils.py, line 123: timezone = pytz.timezone(hass.config.time_zone) (offender: /usr/local/lib/python3.12/site-packages/pytz/init.py, line 108: return open(filename, 'rb')), please create a bug report at https://github.com/geertmeersman/robonect/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self.args) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/robonect/init.py", line 96, in async_setup_entry await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2032, in async_forward_entry_setups await asyncio.gather( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2034, in  create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2081, in _async_forward_entry_setup await entry.async_setup(self.hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 134, in async_setup_entry return await component.async_setup_entry(entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 196, in async_setup_entry return await self._platforms[key].async_setup_entry(config_entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 333, in async_setup_entry return await self._async_setup_platform(async_create_setup_awaitable) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 363, in async_setup_platform awaitable = create_eager_task(awaitable, loop=hass.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/robonect/sensor.py", line 149, in async_setup_entry async_add_entities(entities) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 515, in async_schedule_add_entities_for_entry task = self.config_entry.async_create_task( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1134, in async_create_task task = hass.async_create_task_internal( File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 649, in async_add_entities await add_func(coros, entities, timeout) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 600, in _async_add_entities await coro File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 914, in _async_add_entity await entity.add_to_platform_finish() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1355, in add_to_platform_finish self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1000, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1061, in __async_calculate_state state = self._stringify_state(available) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1006, in _stringify_state if (state := self.state) is None: File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 543, in state value = self.native_value File "/config/custom_components/robonect/sensor.py", line 315, in native_value self.set_state() File "/config/custom_components/robonect/sensor.py", line 303, in set_state state = unix_to_datetime(state, self.coordinator.hass) File "/config/custom_components/robonect/utils.py", line 123, in unix_to_datetime timezone = pytz.timezone(hass.config.time_zone)
Detected blocking call to open inside the event loop by custom integration 'watchman' at custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")): (offender: /config/custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")):), please create a bug report at https://github.com/dummylabs/thewatchman/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/runner.py", line 166, in setup_and_run_hass return await hass.async_run() File "/usr/src/homeassistant/homeassistant/core.py", line 515, in async_run await self.async_start() File "/usr/src/homeassistant/homeassistant/core.py", line 568, in async_start self.bus.async_fire_internal(EVENT_HOMEASSISTANT_STARTED) File "/usr/src/homeassistant/homeassistant/core.py", line 1554, in async_fire_internal self._hass.async_run_hass_job(job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 936, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/core.py", line 1418, in call self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 939, in async_run_hass_job return self._async_add_hass_job(hassjob, *args, background=background) File "/usr/src/homeassistant/homeassistant/core.py", line 748, in async_add_hass_job task = create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/watchman/init.py", line 274, in async_on_home_assistant_started parse_config(hass, reason="HA restart") File "/config/custom_components/watchman/init.py", line 351, in parse_config entity_list, service_list, files_parsed, files_ignored = parse( File "/config/custom_components/watchman/utils.py", line 258, in parse for i, line in enumerate(open(yaml_file, encoding="utf-8")):

Hi Kim, thanks for notifying.
Could you please upload the error log with some markup? it's quite unreadable now.
Just use the "code <>" markup.

Sorry
Detected blocking call to open inside the event loop by custom integration 'robonect' at custom_components/robonect/utils.py, line 123: timezone = pytz.timezone(hass.config.time_zone) (offender: /usr/local/lib/python3.12/site-packages/pytz/__init__.py, line 108: return open(filename, 'rb')), please create a bug report at https://github.com/geertmeersman/robonect/issues Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/robonect/__init__.py", line 96, in async_setup_entry await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2032, in async_forward_entry_setups await asyncio.gather( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2034, in <genexpr> create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2081, in _async_forward_entry_setup await entry.async_setup(self.hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 134, in async_setup_entry return await component.async_setup_entry(entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 196, in async_setup_entry return await self._platforms[key].async_setup_entry(config_entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 333, in async_setup_entry return await self._async_setup_platform(async_create_setup_awaitable) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 363, in _async_setup_platform awaitable = create_eager_task(awaitable, loop=hass.loop) File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/robonect/sensor.py", line 149, in async_setup_entry async_add_entities(entities) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 515, in _async_schedule_add_entities_for_entry task = self.config_entry.async_create_task( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1134, in async_create_task task = hass.async_create_task_internal( File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 649, in async_add_entities await add_func(coros, entities, timeout) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 600, in _async_add_entities await coro File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 914, in _async_add_entity await entity.add_to_platform_finish() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1355, in add_to_platform_finish self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1000, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1061, in __async_calculate_state state = self._stringify_state(available) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1006, in _stringify_state if (state := self.state) is None: File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 543, in state value = self.native_value File "/config/custom_components/robonect/sensor.py", line 315, in native_value self.set_state() File "/config/custom_components/robonect/sensor.py", line 303, in set_state state = unix_to_datetime(state, self.coordinator.hass) File "/config/custom_components/robonect/utils.py", line 123, in unix_to_datetime timezone = pytz.timezone(hass.config.time_zone) Detected blocking call to open inside the event loop by custom integration 'watchman' at custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")): (offender: /config/custom_components/watchman/utils.py, line 258: for i, line in enumerate(open(yaml_file, encoding="utf-8")):), please create a bug report at https://github.com/dummylabs/thewatchman/issues Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/runner.py", line 166, in setup_and_run_hass return await hass.async_run() File "/usr/src/homeassistant/homeassistant/core.py", line 515, in async_run await self.async_start() File "/usr/src/homeassistant/homeassistant/core.py", line 568, in async_start self.bus.async_fire_internal(EVENT_HOMEASSISTANT_STARTED) File "/usr/src/homeassistant/homeassistant/core.py", line 1554, in async_fire_internal self._hass.async_run_hass_job(job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 936, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/core.py", line 1418, in __call__ self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 939, in async_run_hass_job return self._async_add_hass_job(hassjob, *args, background=background) File "/usr/src/homeassistant/homeassistant/core.py", line 748, in _async_add_hass_job task = create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/watchman/__init__.py", line 274, in async_on_home_assistant_started parse_config(hass, reason="HA restart") File "/config/custom_components/watchman/__init__.py", line 351, in parse_config entity_list, service_list, files_parsed, files_ignored = parse( File "/config/custom_components/watchman/utils.py", line 258, in parse for i, line in enumerate(open(yaml_file, encoding="utf-8")):

The formatting doesn't cooperate, but at least I tried :-)

It's clear now, thanks! WIll check it at the latest this weekend, but already have a solution in mind (but no access for the moment to my dev environment since I'm on a business trip)

Should be fixed with https://github.com/geertmeersman/robonect/releases/tag/v1.7.1

awesome. thanks for quick fix


TypeError: Cannot read property 'indexOf' of undefined

I cannot use any group, because every time I receive these errors:
TypeError: Cannot read property 'indexOf' of undefined
I20160827-23:48:40.094(2)?     at strContains (packages/alanning_roles/roles_common.js:713:1)
I20160827-23:48:40.095(2)?     at packages/alanning_roles/roles_common.js:708:1
I20160827-23:48:40.095(2)?     at Array.some (native)
I20160827-23:48:40.096(2)?     at Function..some..any (packages/underscore/underscore.js:233:1)
I20160827-23:48:40.098(2)?     at isMongoMixError (packages/alanning_roles/roles_common.js:707:1)
I20160827-23:48:40.098(2)?     at Object._.extend.updateUserRoles (packages/alanning_roles/roles_common.js:686:1)
I20160827-23:48:40.098(2)?     at Object..extend.addUsersToRoles (packages/alanning_roles/roles_common.js:145:1)
I20160827-23:48:40.099(2)?     at [object Object].addUsersToRoles (imports/mods/User/UserMethods.js:9:13)
I20160827-23:48:40.100(2)?     at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1711:12)
I20160827-23:48:40.100(2)?     at packages/ddp-server/livedata_server.js:711:19
Any idea what is it?

Please use the latest master branch and see if it resolves your issue.

Hm, maybe that's stupid, but I have problem with doing this. I pulled repo to package/meteor-roles folder, but I don't know how to add it to project. Before "meteor add alanning:roles" official package is downloading.

You have to put it into packages/alanning:roles.

Okay, it works, but it takes time until I find out that I must rename the roles folder, not general meteor-roles ;] Thanks for help! I have another problem now, but that's for another issue.


A problem about the weight λ of Lvlb

In the paper, λ is 0.001.  The code sets learn_sigma as True and rescale_learned_sigmas as False, so the loss type will be gd.LossType.MSE, in this loss type ,the Lvlb will not multply 0.001. Even if the loss type is gd.LossType.RESCALED_MSE,  terms["vb"] *= self.num_timesteps / 1000.0, what is self.num_timesteps, and what is its effect？
Thank you .

I am also confused about this scaling factor, have you understood that?

In my opinion, authors define L_{vlb} = L_0 + ... + L_T, not L_t.
Thus, they may calculate the vlb loss with scale factor T (self.num_timestep).

我认为，作者定义的 L_{vlb} = L_0 + ... + L_T，而不是 L_t。 因此，他们可能使用比例因子 T（self.num_timestep）来计算 vlb 损失。
Thank you for your answer, which means we use L_t * T (self. num_timestep) to approximate L_ {vlb}?

@yhy258 Thank you for your answer, so, which means we use L_t * T (self. num_timestep) to approximate L_ {vlb}?


Add -A x64 option for windows only when platform is amd64

fix to make pydis work with 32-bit Python

Hi, thanks for the fix. What system are you on where get_platform() returns 'amd64'? I added a similar change in e0e33caabec0d376a4c92186dd71c72cb84ed0b2 which should fix this. Release v0.3 also includes wheels for 32bit windows.

I'm using Windows 10 x64 build 17134.345. Actually get_platform() returns 'win-amd64' on my system. I don't remember if it was 'amd64' earlier or I just had a mistake.


Unresponsive app after hangup

Hello sir.
In a really clean, minimal Debian virtual machine installation I got Baresip "stuck" on the CALLED party at hangup.
With "stuck" I mean: I have to quit the menu by pressing "ctrl+z" and have to kill baresip with "kill -9".
Last debug line in the "stuck" console is:
alsa: stopping playback thread (default)
The CALLING instance on the second virtual machine is OK.
It's a direct call test with no registering involved, started by pressing "d" and typing<EMAIL_ADDRESS>Disabling the alsa.so module results in no audio but no "hangs".
All relevant files are attached. Thank you and merry christmas!
--- System info: ---  Machine:  x86_64/linux  Version:  0.6.5 (libre v0.6.1)  Build:    64-bit little endian  Kernel:   Linux debian 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64  Uptime:   3 secs  Started:  Sun Dec 22 05:48:26 2019  Compiler: 8.3.0
config-and-accounts.txt
install-steps.txt

it is most likely stuck here: (waiting for the thread to exit)
	/* Wait for termination of other thread */
	if (st->run) {
		debug("alsa: stopping playback thread (%s)\n", st->device);
		st->run = false;
		(void)pthread_join(st->thread, NULL);
	}

thread:
		n = snd_pcm_writei(st->write, sampv, samples);

couple of ideas:

run baresip in gdb, and after the hang get a full backtrace for all threads:

(gdb) thread apply all bt

disable or uninstall pulseaudio, reboot, and use a pure ALSA environment.

add a call to pthread_kill before pthread_join

add a call to snd_pcm_close before pthread_join

use pulseaudio.so module instead

Hello and thank you.
Can't read C code, sorry!

disable or uninstall pulseaudio, reboot, and use a pure ALSA environment.

Pulseaudio is not installed, it is pure ALSA.
Doesn't hangs on Raspberry PI 3 armv7l and Asus EeePC i386.
I'll try to debug with GDB and report back. Thank you very much.

I tried the same with Debian 9 running in VirtualBox.
The result is that the audio (ALSA) is working fine, and that the call
is hanged up fine (not stuck).
I think it is related to the audio driver and that some resource
is shared between recording and playback. When the recording thread
is stopped first, it does something in the driver that blocks the
playback thread from returning (just a hunch).
You can try to use different names for audio_source and audio_player,
for example:
audio_source alsa,plughw:0,0
audio_player alsa,plughw:0,1

some more questions for you:

which VM software are you using ?

can you get the output of arecord -l

you can also try to swap the order of stop_tx/rx in:
void audio_stop(struct audio *a)
{
	if (!a)
		return;

	stop_tx(&a->tx, a);
	stop_rx(&a->rx);
}

VM software is Virtualbox 6.0.14. It provides 3 emulated audio controllers which I all tried out without success while dealing with this glitch:

ICH AC97 (dafault)
Intel HD Audio
Soundblaster 16

With suggested audio_source and audio_player I get:
alsa: could not open auplay device 'plughw:0,0' (Device or resource busy)
audio: start_player failed (alsa.plughw:0,0): Unknown error -16
arecord -l returns:
**** List of CAPTURE Hardware Devices ****
card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: I82801AAICH [Intel 82801AA-ICH], device 1: Intel ICH - MIC ADC [Intel 82801AA-ICH - MIC ADC]
  Subdevices: 1/1
  Subdevice #0: subdevice #474
Many thanks.

my device was only
an example :)
you should use the
correct alsa device, try all
until it works
are you really sure
there is no pulseaudio involved?
Debian uses pulse and you
said «clean install»
i am waiting for
the gdb bt from you

Hello sir.
Since Virtual machine was used only for testing and on physical machines the issue is not present I am closing this.
In debian-10.2.0-amd64-netinst Pulseaudio is not present.
Thank you very much for helping out and happy new year!
closing.txt

I tested again with Debian 10 on VM and Physical machine:

VM (VirtualBox) -- hangs
Physical machine -- no hang

in anycase a workaround is to call snd_pcm_drop before pthread_join.

Thank you. Sorry, the workaround have to be made in alsa.c or main.c?
Cheers


Metrics Server not working

According to https://aws.amazon.com/blogs/opensource/horizontal-pod-autoscaling-eks/, Metrics Server should  work. In my case, it is failing. I'm probably missing something but I'm not sure what that is.

W0925 22:40:00.447678       1 authentication.go:210] cluster doesn't provide client-ca-file in configmap/extension-apiserver-authentication in kube-system, so client certificate authentication to extension api-server won't work.
[restful] 2018/09/25 22:40:00 log.go:33: [restful/swagger] listing is available at https://:443/swaggerapi
[restful] 2018/09/25 22:40:00 log.go:33: [restful/swagger] https://:443/swaggerui/ is mapped to folder /swagger-ui/
I0925 22:40:00.503815       1 serve.go:96] Serving securely on [::]:443

kubectl top nodes

Error from server (NotFound): the server could not find the requested resource (get services http:heapster:)

kubectl version --output=yaml

clientVersion:
  buildDate: 2018-09-10T11:44:36Z
  compiler: gc
  gitCommit: a4529464e4629c21224b3d52edfe0ea91b072862
  gitTreeState: clean
  gitVersion: v1.11.3
  goVersion: go1.11
  major: "1"
  minor: "11"
  platform: darwin/amd64
serverVersion:
  buildDate: 2018-05-28T20:13:43Z
  compiler: gc
  gitCommit: 2bba0127d85d5a46ab4b778548be28623b32d0b0
  gitTreeState: clean
  gitVersion: v1.10.3
  goVersion: go1.9.3
  major: "1"
  minor: "10"
  platform: linux/amd64

Console shows that the cluster uses platform version eks.2.

@vfarcic As the deployment note in the helm chart suggests, try checking your metrics.k8s.io api directly using kubectl get --raw "/apis/metrics.k8s.io/v1beta1/nodes"
kubectl top node can use both APIs, in your log line it's clear that kubectl is looking for heapster, not the metrics API. See more here

My bad for not stating in the initial message that I tried retrieving raw data as well.
kubectl get --raw "/apis/metrics.k8s.io/v1beta1/nodes"

Error from server (ServiceUnavailable): the server is currently unable to handle the request

It might be useful to note that I tried the same steps in Docker For Desktop and minikube and they worked. My initial thought it that EKS needs something "special".
Since I guess that it was tested before it was released a month ago, I guess there must be some explanation on how to set it up. I'd be more than happy to switch from deploying Helm chart to any other way to set up HPA and Metrics Server in EKS. I'd appreciate if you could provide a hint how to proceed. The only info I found it https://aws.amazon.com/blogs/opensource/horizontal-pod-autoscaling-eks/ but it only states that HPA recently become available but there is no other info I could find.

I'm having the exact same experience as you are right now.

So, apparently you need to also allow port 443 to the nodes from the cluster control pane. (https://github.com/kubernetes-incubator/metrics-server/issues/45). I'm testing this now and will report back.

That worked for me. Adding port 443 to the allowed communication ports was all I needed to do.

I got the security groups configured as per the above discussion:
kubectl get --raw "/apis/metrics.k8s.io/v1beta1/nodes" works fine . But I still see "ScalingActive  False   FailedGetResourceMetric  the HPA was unable to compute the replica count: missing request for cpu on container"  and also "unable to fetch pod metrics for pod"

Hi @jithinjose2004 even I'm also facing with the same issue ! Did you find any solution ?

@VinayVanama  nothing yet. I see metrics-server is working as expected . But HPA is not able to pull the cpu usage details . I still get "horizontal-pod-autoscaler  failed to get cpu utilization"

I can confirm that deploying metric server makes HPA work on EKS platform version 2. We have just tested. Thanks https://aws.amazon.com/blogs/opensource/horizontal-pod-autoscaling-eks/
and people who have discussed this here.
`
root@DESKTOP-1RJC2SJ:~/nodejs-sample-app-kubernetes# kubectl get all -n nodejs
NAME                                   READY   STATUS    RESTARTS   AGE
pod/node-deployment-588c4b8679-jtbv5   1/1     Running   0          6m
pod/node-deployment-588c4b8679-xpm6l   1/1     Running   0          6m
NAME                  TYPE       CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
service/nodeapp-svc   NodePort   <IP_ADDRESS>           80:31180/TCP   13d
NAME                              DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/node-deployment   2         2         2            2           6m
NAME                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/node-deployment-588c4b8679   2         2         2       6m
NAME                                                  REFERENCE                    TARGETS   MINPODS   MAXPODS   REPLICAS   AGE
horizontalpodautoscaler.autoscaling/node-deployment   Deployment/node-deployment   0%/30%    2         6         2          5m
`

From what I have experienced in a test EKS.2 cluster it is not working if you have Private DNS disabled in your VPC. Even if you set "--kubelet-preferred-address-types" to InternalIP it won't work:
[restful] 2018/12/03 13:36:41 log.go:33: [restful/swagger] https://:443/swaggerui/ is mapped to folder /swagger-ui/
E1203 13:37:53.710664       1 reststorage.go:129] unable to fetch node metrics for node "ip-yyy.eu-west-1.compute.internal": no metrics known for node
E1203 13:37:53.710688       1 reststorage.go:129] unable to fetch node metrics for node "ip-yyy.eu-west-1.compute.internal": no metrics known for node
E1203 13:37:53.710695       1 reststorage.go:129] unable to fetch node metrics for node "ip-yyy.eu-west-1.compute.internal": no metrics known for node
E1203 13:38:15.309381       1 reststorage.go:144] unable to fetch pod metrics for pod xxx: no metrics known for pod
E1203 13:38:41.891378       1 manager.go:118] unable to save metrics: duplicate pod xxx received
E1203 13:38:45.316283       1 reststorage.go:144] unable to fetch pod metrics for pod xxx: no metrics known for pod
PS C:\Users\pedro\Documents\Basecone-Operations-MailServer\Kubernetes\4.amavis> helm del --purge metrics-server;

From what I have experienced in a test EKS.2 cluster it is not working if you have Private DNS disabled in your VPC. Even if you set "--kubelet-preferred-address-types" to InternalIP it won't work:
[restful] 2018/12/03 13:36:41 log.go:33: [restful/swagger] https://:443/swaggerui/ is mapped to folder /swagger-ui/
E1203 13:37:53.710664 1 reststorage.go:129] unable to fetch node metrics for node "ip-yyy.eu-west-1.compute.internal": no metrics known for node
E1203 13:37:53.710688 1 reststorage.go:129] unable to fetch node metrics for node "ip-yyy.eu-west-1.compute.internal": no metrics known for node
E1203 13:37:53.710695 1 reststorage.go:129] unable to fetch node metrics for node "ip-yyy.eu-west-1.compute.internal": no metrics known for node
E1203 13:38:15.309381 1 reststorage.go:144] unable to fetch pod metrics for pod xxx: no metrics known for pod
E1203 13:38:41.891378 1 manager.go:118] unable to save metrics: duplicate pod xxx received
E1203 13:38:45.316283 1 reststorage.go:144] unable to fetch pod metrics for pod xxx: no metrics known for pod

From what I have experienced in a test EKS.2 cluster it is not working if you have Private DNS disabled in your VPC. Even if you set "--kubelet-preferred-address-types" to InternalIP it won't work:

Bam.  Experienced this same problem and enabling DNS hostnames for the VPC fixes it.
If you are using Terraform to build your EKS cluster, add the following to your aws_vpc resource:
   enable_dns_hostnames = true

You can apply this change and don't have to rebuild the VPC or cluster or anything.  It will take a few minutes for the hostnames to start resolving, so be patient and watch the metrics-server log.  When it stops scrolling with errors, kubectl top pod should work once more.

Another note for anyone who finds this thread. I had strict control on both Inbound and Outbound rules for my masters. Make sure everything is symmetrical: node allows 443 inbound from master, and master allows 443 outbound to node. It took me a while to notice that my masters did not have outbound to 443 allowed.
You may end up in the same boat if you follow the recommendations. https://docs.aws.amazon.com/eks/latest/userguide/sec-group-reqs.html

EKS seem to not install by default the Kubernetes Metrics Server
https://docs.aws.amazon.com/eks/latest/userguide/metrics-server.html


Install fails with go 1.4.1

I attempted to install on an old version of go and got:
$ go version
go version go1.4.1 darwin/amd64
$ go get -u github.com/xenolf/lego
# golang.org/x/net/context/ctxhttp
Documents/go/src/golang.org/x/net/context/ctxhttp/ctxhttp.go:35: req.Cancel undefined (type *http.Request has no field or method Cancel)

Upgrading to 1.6.2 resulted in a good install. Reporting so that if nothing else someone searching for this error sees that a simple upgrade should fix it.

Thank you for reporting :)
I've decided to only support the last two releases of go because it is kinda dictated from google libraries like you just experienced. For anyone hitting this issue, please look at the versions in our CI, these are the ones we currently support.


Preprocessor Support Utilizing The Ember-CLI Pipeline

This is going to be a bit long, so bear with me.
I broke up index.js into several smaller files, just to make everything easier to work with.
Inside package.json you can see that I added a specifier to make sure we run "before" ember-cli-sass. I think this will serve a two-fold purpose in the future: ensure that we run at the correct point in the pipeline and act as a sort-of "approved" plugins list.
Okay, now for the meaty stuff:
Inside ComponentCssPreprocessor, we no longer return the tree generated by BrocComponentCssPreprocessor but return that merged back in with the original tree. This is because we were effectively only returning pod-lookup.json and pod-styles.css before. This will cause issues with anything that runs afterward, because it won't find the files needed. Thus we return the original tree with the additional files from our processor. Let me know if this doesn't make sense.
Inside BrocComponentCssPreprocessor, I use a simple test to see if we're dealing with a standard .css file or a file that needs to be preprocessed. Some things that came up while thinking about this aspect:
First: do we want to allow users to mix extensions? In other words, should users be allow to have .css and .scss files in the same project? Or should we assume they will only use one extension? I think the latter option makes more sense and will be a cleaner solution. The issue would then be that we need a way for the user to specify what extension we look for.
Second: are we assuming that the "wrap & passthrough" approach will be used with all preprocessors? For example, I think there may be issues with .sass files (could be wrong though).
The post-processor didn't really change, except for the following:
You'll notice a pod object being passed around (I know, horrible name), this had to be done because we need a reference to podLookup and podStyles (which are generated during the pre-processing) during the post-processing, but those files were getting filtered out by the ember-cli-sass portion. So, rather than trying to find a way to force the files through, I just moved that data to be in a JS object that is referenced by the various parts. This is not an approach I am not super fond of as it feels kind of brittle, but I couldn't think of a better way currently to do it. So suggestions welcome.
TL;DR: broke up index.js, got ember-cli-sass working, and I have questions/issues that I'd like input on.

Does this remove the support for plain CSS? I think we're going to need the old Broccoli filter for plain CSS and a new one for the "wrap and passthrough" approach with other preprocessors.
It also seems like we need conditional behavior for the generation of pod-styles.<original extension>

@ebryn this still supports vanilla CSS; does a simple if check on the extension.
The conditional behavior goes along with my first question above. If we force a single file-type, how should we go about doing that? By checking the other installed CSS plugins? Or having them set a configuration option?

We don't force a single type, I think we just appropriately handle based on the file extension used in the pod directories. Is it more complex than that?

Maybe my thinking is a bit contrived, but what if we encounter two different extensions? E.g., .scss and .sass? Which extension do we use for pod-styles?

Ah, I see what you mean. I think in that particular case it doesn't matter, we could default to scss since the includes will work for either?

On both this branch and master, I find the addon blows up on a vanilla app with any version of ember-cli newer than 0.2.0-beta.1 when any other CSS preprocessors are registered :(
I've traced the problem to ComponentCssPreprocessor not getting the files it expects in the tree passed to toTree (same error as mentioned in this comment) but haven't yet tracked down why that's happening. Hoping to have some time to dig in over the weekend, but if either of you have any hunches on what might be going on, I'd love to touch base.
@trentmwillis it's awesome to see this PR come together, and I don't think there's any reason not to go ahead and land it, but it may be hard for a lot of people to use it until that bug is tracked down.

@dfreeman I expect that is because of something getting funneled improperly within the monkeyPatch function as that tree is what initially gets passed to the toTree in ComponentCssPreprocessor.
I hope to revise this into a shippable form this weekend. Stay tuned.

It's quite likely the monkeypatching code is no longer necessary

@trentmwillis In narrowing down which funnel was the culprit, I actually killed the monkey patch completely and still saw the same error. No definite conclusions, but it seems possible this could be inconsistent behavior in Ember CLI, since I there have been many common use cases for having multiple registered CSS preprocessors before now.

@ebryn @dfreeman I think this is about good to go. It now determines which extension to use based on the first file it processes. I also bumped the Ember-CLI version to the current release as the specific branch being referenced before didn't seem to add anything.

@trentmwillis Any idea why the build is failing?

@ebryn It looks like the Travis build has the wrong version of a couple dependencies (despite running npm install) so the tests are refusing to run. As the repo owner, you may be able to re-kick the build with a cleared cache and see if that does the trick.

What @dfreeman said

Merged! :heart_eyes:


Support commander 2.x

Updated the types, still need to add more tests

Running through PRs and following up: Looks like this one is just waiting on some $ExpectErrors

Should be good to go


Preload response

I get this error in console and in network, I see that a Preload request was canceled to my app shell page.
The service worker navigation preload request was cancelled before 'preloadResponse' settled. If you intend to use 'preloadResponse', use waitUntil() or respondWith() to wait for the promise to settle.

What sort of thing is this caused by?

@mastercoms you should ask/check these questions on workbox repo: https://github.com/GoogleChrome/workbox/issues/2178

I mean, is there any config this is related to? globPatterns? manifest entries?

I'm not using a custom sw.js, just the one generated by this plugin, which is why I ask.

@mastercoms I need some repro or your pwa plugin configuration: it seems you've a navigation preload and maybe blacklist entry configured
You can try to add sourcemap, don't minify the build then take a look the sw generated by workbox, check the linked issue if it is the same problem, it can be a bug on workbox

https://github.com/mastercomfig/comfig-app/blob/develop/astro.config.mjs

@mastercoms this is a copy of my PR on astro (I need to change a few things)?
Anyway, the problem can be related to https://github.com/antfu/vite-plugin-pwa/pull/306, since the workbox generatedSW call doesn't include the claims stuff, check this entry on îles to solve it:
https://github.com/ElMassimo/iles/blob/main/packages/pwa/src/pwa.ts#L37


Do not log on expected http errors

When using this.assert and this.throw, I don't think it is appropriate to log the http error since it is a completely expected error. For example, 400 client errors (missing username and such) are things I would like the client to know about, but I definitely don't want it to be included in my logs. Checking the expose property allows filtering of expected errors, but still maintains error logs for errors that one might be interested in like actual code errors or other 500 errors.

LGTM

391650518f877e7a2631f38b4dc8659a1d1fbb8c

FWIW Express 5.0 is destined to make the same change.


Posts not showing up under "Recent Posts"

[X] This is a question about using the theme.
[ ] This is a feature request or enhancement.
[ ] I believe this to be a bug with the theme.
[ ] I am using the latest version of the theme.
[X] I have updated all gems with bundle update.
[X] I have tested locally with bundle exec jekyll build.

Environment informations

Minimal Mistakes version: Newest (>4)
Jekyll version: 3.6.2
GitHub Pages hosted: yes
Operating system: MacOS

Expected behavior
Posts appears under "recent posts" on the home page

Steps to reproduce the behavior
https://github.com/sliuu/hciproject/
Downloaded the theme, unzipped, added to repository
Customized _config.yml, added some navbar and author links, added front page image
Created a post under _posts/
Built, and served with jekyll

Looks like you got this working as I see your latest post on the home page.

It does seem to show up, but the formatting for the post itself isn't what I expected and it doesn't show up on my local... any idea why?

That's because you don't have the layout for the post at correctly. Should be layout: single not default.

Is there any reason why the "recent posts" section would show up on the website but not on my local?

Yeah. You probably don't have the pagination gem installed properly. GitHub Pages does all that for you when they host the site. You need to do the same locally.
https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/

Thanks so much for all your help! Also turns out the reason my posts weren't showing up locally is because I set the date in the future (stuff's due tomorrow). Didn't think about that.

You can use the --future flag when building your Jekyll site, to force publish and future dated posts.

I seem to have the same problem that @sliuu was facing. I have pushed my changes to the page over at www.havesomeleeway.com but nothing is showing up on my recent posts
What I have now:

_posts with a file named 2018-02-20-test.md
layout of post is set to single

This file is your problem.
https://github.com/havesomeleeway/havesomeleeway.github.io/blob/master/_pages/home.md
As noted in the docs, a home page that is paginated can't be a markdown file. For whatever reason jekyll-paginate requires it to be named index.html and in the root of your repo.
Rename it and move it out of _pages.

@mmistakes thanks a lot, it works now.

For people finding this on Google, and as me, had everything configured correctly:
Think about your timezone on the post...
I created a post one hour in the future (didn't think about summer<>wintertime) and therefore, the post didn't show up, as I was expecting. Half an hour waisted, and fixed by moving the post one hour.
To... Hopefully I can save your time ;) ...
😆 ....


Add minor changes to user guide

Codecov Report

Merging #76 (ce49c79) into master (fef196d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #76   +/-   ##
=========================================
  Coverage     71.25%   71.25%
  Complexity      400      400
=========================================
  Files            73       73
  Lines          1242     1242
  Branches        125      125
=========================================
  Hits            885      885
  Misses          320      320
  Partials         37       37

Continue to review full report at Codecov.

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


Add "Restore NuGet packages" build step to README.md

Visual Studio seems to get cranky if you don't restore packages before
opening src/MSBuild.sln, so tell users how to do that.
I'm not sure this is the best approach, but at least it seems to work.
A similar change is also needed to https://github.com/Microsoft/msbuild/wiki/Building-Testing-and-Debugging, but unfortunately github wikis do not support pull requests, so someone with write access to the wiki will have to take care of that.
Er, wait, your wiki is actually wiki, unlike most github wikis, so I made the wiki edit already!  Hooray for the broken link in RebuildWithLocalMSBuild.cmd, which made me notice this (by virtue of presenting me with a big fat edit box instead of an error message).

@SamB, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

Looks good, thanks for updating the doc.


New download folder destination

To prevent issues like #61 or #55

Can @luispereira @tazesk or @krokyze can try this branch to see if it fixes your problem?
I don't own any windows machine

yes, you fix it !!! thank you.

it's already on version 0.8.1

hi, I use Windows. And I have this issue too. My dryrun verison is 0.8.1, but I still encounter this problem. Is something I did wrong？Thanks for your help anyway...
C:\Users\thinkpad>dryrun https://github.com/ksoichiro/Android-ObservableScrollView.git
Searching for devices...
Killing adb, there might be an issue with it...
No devices attached, but I'll run anyway
======================================================
Something went wrong while executing this:
$ git clone --depth 1 https://github.com/ksoichiro/Android-ObservableScrollView.git C:/Users/thinkpad/AppData/Local/Temp/dryrun/ksoichiro/Android-ObservableScrollView
======================================================

works great on OSX, @luispereira can you try it on your windows machine?

I also have the issue, although this is an issue regarding the project itself and not dryrun.
I believe the gradle wrapper has some custom functionalities which does not support Windows System, such as "tr".

Yeah, it's a BSD tool, it's not on windows
TR(1)                     BSD General Commands Manual                    TR(1)

NAME
     tr -- translate characters


Allow injecting the GRANFALLOON_TOKEN in alternative parts of the request

This includes injection into the Authorization header with alternative formats, as well as offering a X-Granfalloon-... header when Granfalloon is hosted behind a proxy


[WFLY-11085]:  Updating jboss metadata to 12.0.0.Final

Fixing packages renamed
Fixing distribution test

Jira: https://issues.jboss.org/browse/WFLY-11085
https://issues.jboss.org/browse/WFLY-10685

@ehsavoie Does the old 'wrong' way still work in 12.0.0.Final? As in the comments in https://github.com/wildfly/wildfly/pull/11408/files#diff-8cffe2f0aee67a4d67e591b1d91b12d8

@kabir yes :)


reconstruct_measured_data bugs

!sed -i.bak2 -e "s#\(!name of data file:=\)#\\1${data_path}/#" umap.v.hdr
!sed -i.bak2 -e "s#\(!name of data file:=\)#\\1${data_path}/#" norm.v.hdr

to
!sed -i.bak2 -e "s#\(!name of data file:=\)#\\1{data_path}/#" umap.v.hdr
!sed -i.bak2 -e "s#\(!name of data file:=\)#\\1{data_path}/#" norm.n.hdr

Unfortunately I'd found and fixed these but didn't stage after testing


Default to AzCopy with option to install it

Currently we are defaulting to using WebClient to download images. It can take a long time to download images with WebClient and can also time out.
This PR makes AzCopy the default option for downloading images. It is faster and has check-pointing builtin.
Exception calling "DownloadFile" with "2" argument(s): "The operation has timed out."
At C:\AzureStack-Tools-master\Syndication\AzureStack.MarketplaceSyndication.psm1:586 char:17
+                 $wc.DownloadFile($source, $tmpDestination)
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : WebException

https://docs.microsoft.com/en-us/dotnet/api/system.net.webclient?view=netframework-4.8#remarks
_

We don't recommend that you use the WebClient class for new development. Instead, use the System.Net.Http.HttpClient class.

_

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: easyveazie sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

This was addressed in a separate commit. Closing.
https://github.com/Azure/AzureStack-Tools/commit/1d613b654b2b310f0ceae40a4f4bb290dc47c1c4#diff-9e1b89c3d17e3691cc05dd0ac4f74500


Fix docker compose command v2 when not using moby

It's not working because it's not getting installed. :)

Ah interesting - it used to be there by default.  Thanks!

Puedo saber que están haciendo dentro de mi cuenta y mis datos personales
Enviado desde mi iPhone

El jul. 15, 2022, a la(s) 14:50, Chuck Lantz @.***> escribió:

Ah interesting - it used to be there by default. Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.


resource limits lose efficacy for containers in v0.17.0

RC configuration with limits:
 resources": {
                                            "limits": {
                                                "memory": "2Gi"
                                            }
                                        },

But show unlimited in cAdvisor:
Memory
Limit unlimited
Swap Limit unlimited

And cAdvisor show this POD used 2.37GiB memory which exceeds "2Gi" in resource limits we config. It should be killed.

What version of Docker are you running? There was an issue with the API in Docker 1.6+ which we fixed in #8491 but that was not in 0.17.0. It should be in the build this week.

I am closing this one as dup of #8814


PLD80-89 fix

noticed in MtGulg that it would keep spamming confiteor under requiescat after it was used once
so i added a stack check for requiescat so that it would only call it when theres 4 stacks of requiescat hence stopping the spam and correctly using holy circle / spirit
however after that fix i noticed that once again for lvl90+ it wasn't using the blade combo, after some checks i've came to understand it doesnt use the blade skills but was only spamming confiteor, so i added another stack check specifically for lvl90+

this should fix issue#49
 PLD lv80 rotation broken #49

and this issue as well
https://github.com/FFXIV-CombatReborn/RebornRotations/issues/53


[TACHYON-1393] Have FileSystemContextTest check for deadlocks

https://tachyon.atlassian.net/browse/TACHYON-1393

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7153/
Test PASSed.

Thanks for the fix. Could you also update BlockStoreContextTest?

@yupeng9 Updated, thanks!

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7155/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7156/
Test PASSed.

Thanks for adding this test, I left one comment

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7157/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7158/
Test PASSed.

LGTM


Support Svelte 5 Runes mode

This pull request provides support for Svelte 5 runes mode. It is not backwards compatible for Svelte 4.
Summary of changes:

Dependencies have been upgraded to support Svelte 5.
Compiler has been set to Runes mode.
Code updated to use runes.

Closes #48

cc @metonym

@metonym can we get a new release and this merged? Is there anything else that should be updated like Dayjs?

Nice work, thanks both.
Will review – I think one thing that'll need updating is the demo, for which it breaks entirely for Svelte 5. It could be a nice opportunity to switch to Vite instead of Rollup.

@metonym can we get this merged and that gets followed up on?


Add menu for installed mods

Summary

Adds a menu to the title screen to view installed mods. It's only one part of the feature to integrate the mod system with the UI.
Adds a few more metadata fields to mod.hcl.
Adds a field in the mod manager to enable/disable mods. Currently all mods are enabled (as before).

Closing in favor of #1265.


Updated "Learn More" link for error handling

I believe that the Learn More link for error handling may be wrong
It currently links to loading ui while I think linking it to error handling may be more appropriate

@vaishnav-mk that does make more sense. 😅 Thanks for the fix!


Publishment to the official ZeppOS store

Are there any schedules or thoughts of uploading this app to the official store?
I hadn't came up with the idea of this 2FA code app before seeing this repo, and I think this is the great use of ZeppOS platform.
It is awesome if everyone can get this without searching Github. (cause most users won't even think about developing the app, and not seeing Github too.)

I think it is time to upload to the official store after #5 merges to main branch. I will do some research.

Thanks!

It seems like it need to provide some information to submit the app.
Submit an application | Zepp OS Developers Documents

Preparation Items
Description

Country and region
You need to determine in advance the country and region where the application will be published.

Privacy Statement
Providing the text content of this application's privacy policy helps users understand how you handle sensitive user data and device data. The privacy policy must fully describe how your application collects, uses and shares user data.

Work Statement
Statement that the work complies with the requirements of relevant national laws and regulations and does not infringe on the legal rights of any third party.

Since it is my first time to do this, do you have any idea about "Work Statement"?

Hmm. Idk about your country's regulations, but I think we should write that this app is not against the privacy law.
Where do you live?

I confirmed that Zepp app won't save side service's storage on cloud, so I think we can write something like
"this app only save data on local storage and not sending anywhere, so there's no violation of legal rights."

Where do you live?
I live in Taiwan.

I have ask some people about Work Statement, we can simply reference to this repo.
I might polish the code recently before submitting the app.

Sorry for being late!
I see.
Maybe we should make some improvements on sync function to be interactive, because on current code, user will lose their 2FA token when they reinstalled Zepp app on their phone or changed their phone.

Actually, as long as user doesn't reset the watch, it will sync back to the new phone. But it is good to have some sort of backup/restore feature.

Sorry for being late. I've been quite busy recently.
Do you mean Zepp app will automatically sync back the data of mini apps when the user changed their phone?

Hi,
did you guys ever submit it to the store?
I now have a Watch with Zepp OS 2 and can't see it on the appstore.

Idk but I think he hasn't done it yet.
@ZoLArk173 hi! How're you going. Do you have time to work at this?

Hi,
did you guys ever submit it to the store?
I now have a Watch with Zepp OS 2 and can't see it on the appstore.

That sounds nice!

I updated the readme with screenshots. If i don't find any bug tomorrow i think i will submit it.

Since the repo is licensed under MIT license, @manujedi you may submit to store as you want.
I have take a look your repo, it looks completely different. Thanks for mentioning me.

Alright, thanks for your comments.

@ZoLArk173 I fixed a simple typo so plz take a look at it before the publishment.

Finally my version was approved after three revisions (icon had no background, icon was missing on gts4). Submission is simply and the feedback what is wrong is good and clear.

Great! Your app must be used by many users.
I love your version's revamped ui and clean, tidy codes.


Bootstrap file

WHY
So the developer doesn't need to modify the core to set some global vars etc..
WHAT
When booting the system let the developer add in a bootstrap file from their config directory

Not needed, we use the app.js in the app directory


EPIC: Basic CRUD setup for Pilots and Mechs

Description
Epic to cover this use case:
As a battletech player
I need a way to interact with my pilots and mechs
so that I can see which models are usable in our campaign
Acceptence Criteria

Implement Create functionality for Pilot and Mechs
Implement Read functionality for Pilot and Mechs
Implement Update functionality for Pilot and Mechs
Implement Delete functionality for Pilot and Mechs

Dependencies
Any dependencies or prerequisites required for the completion of the Epic.

Working basic Repo

repo change to https://github.com/bovinehero/mech-manager as original repo static content required a rework to function on heroku


added non-human animal neoplasm terms from NCIT

Addresses #5252

@matentzn
This PR adds new non-human animal neoplasm terms from NCIT.
I use "MONDO:equivalentTo" because these terms in Mondo are equivalent to the NCIT terms (ie the NCIT terms are actual diseases). However, these are not in the "human disease" hierarchy.
Do you think it is the correct annotation? Or should we use "MONDO:otherHierarchy" like we did for the AML terms? (There might be other consequences to not use "MONDO:equivalentTo", but I'll way for your feedback before getting there)
Thank you!

@sabrinatoro I think equivalentTo is correct - AML was different - they were not really diseases. :)

note: I will normalize after this PR is accepted

This looks good to me. @sabrinatoro do you want to merge? Sounds like you want to run make norm first?


[META] Derived Fields

Please describe the end goal of this project
"Schema on reads" is a mechanism where query result data can be defined at runtime of the query. This is useful for users who may not be aware of the structure of the data and want to explore its usage before choosing what and how to index it. More simply, this allows users to have additional attributes to query upon post-ingest. Derived fields are an enhancement to OpenSearch that provides this "schema on read" functionality.
Supporting References
The RFC for this feature request can be found here https://github.com/opensearch-project/OpenSearch/issues/1133
Issues

[ ] https://github.com/opensearch-project/OpenSearch/issues/12506
[ ] https://github.com/opensearch-project/OpenSearch/issues/12507
[ ] https://github.com/opensearch-project/OpenSearch/issues/12508
[ ] Aggregation support
[ ] Scoring support
[ ] Sorting support

I will update this section with created issues with more details. For the time being I wanted to create the META issue for tracking.

[Triage - attendees 1 2 3 4 5 6 7 8]
@qreshi Thanks for filing, it would be useful to to create subtasks with additional details for some of those items, looking forward to seeing progress here.

List of all tasks associated -

[x] Derived fields building blocks: DerivedFieldQuery, DerivedFieldScript and DerivedFieldValueFetcher - https://github.com/opensearch-project/OpenSearch/pull/12746
[x] Derived fields supported field types implementation - boolean, keyword, long, double, ip, geo_point, date - https://github.com/opensearch-project/OpenSearch/pull/12808
[x] Derived fields Mapper definition and integration through index mapping way - https://github.com/opensearch-project/OpenSearch/pull/12569
[x]  Support for adding multiple values from derived field scripts - https://github.com/opensearch-project/OpenSearch/pull/12837
[x] Support defining derived field through search requests and rest client. Also adds support for derived fields in fetch and highlight phase  - https://github.com/opensearch-project/OpenSearch/pull/12850
[ ] Support for object type in derived fields - https://github.com/opensearch-project/OpenSearch/issues/13143
[ ] Documentation - https://github.com/opensearch-project/documentation-website/issues/6943


Generation fails on 2.3.0

I have my migrations laid out as part files which are used inside a broader migrations.dart file.
After upgrading from 2.1.0 to 2.3.0 the code generation fails because the part files are now analyzed as Dart library.
It still works with 2.2.0.
[SEVERE] drift_dev:not_shared on lib/db/migrations/17_fix_table.dart:

Asset [my_app|lib/db/migrations/17_fix_table.dart] is not a Dart library. It may be a part file or a file without Dart source code.

Technically this shouldn't be a problem since drift still generates sources for the main database (at least that's what I hope?).  I've improved the UX for these cases in dafa07a88a6d05e21218c6a53cb38582c23d0eea.


subclass of list and BaseModel causes: "TypeError: multiple bases have instance lay-out conflict"

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
See code below. You can run this and produce the same error.
I'd like to inherit both list and BaseModel so I can have a list with additional validated args. Maybe there is a workaround for this I am not aware of.
Example Code
from pydantic import BaseModel

class PydanticListItem(BaseModel):
    li1: int
    li2: int

class PydanticList(list[PydanticListItem], BaseModel):
    i1: int
    i2: int

Python, Pydantic & OS Version
pydantic version: 2.4.2
        pydantic-core version: 2.10.1
          pydantic-core build: profile=release pgo=false
                 install path: C:\Users\BAREB\AppData\Local\Programs\Python\Python311\Lib\site-packages\pydantic
               python version: 3.11.3 (tags/v3.11.3:f3909b8, Apr  4 2023, 23:49:59) [MSC v.1934 64 bit (AMD64)]
                     platform: Windows-10-10.0.19045-SP0
             related packages: mypy-0.982 typing_extensions-4.8.0

Nevermind I should have been using the pydantic dataclass. My apologies!


Fixing auth source filter and minor measurable index bug

#3244

This pull request introduces 1 alert when merging d370a0219d3710863b3d72d8fe32c4451ab9c0d5 into b654f566fcce518472fc444abe47917a66a68be2 - view on LGTM.com
new alerts:

1 for Unused variable

Comment posted by LGTM.com


Arrow keys don't let you browse through previously sent messages

If I send "foo", then use up arrow, "foo" should pop up in the type field.

Duplicate of #41

Now they do :)


Option to default flag the 'Use Pre-shared Key' when creating a new profile

Currently, the option/flag to 'Use Pre-shared Key' is unticked when creating a new profile.
Would be great to flag this by default or make it a setting in the WG Dashboard

Seems like this can be achieved by adding:
checked="{checked}"
to line 219 in /wgdashboard/src/templates/configuration.html
                                   <input class="form-check-input" type="checkbox" id="enable_preshare_key" name="enable_preshare_key" value="enable_psk" checked="{checked}">

that work now, you can close the ticket


All USB cameras are not working anymore after librealsense-dkms update

Required Info

Camera Model
{ D400 }

Firmware Version
(2.38.1)

Operating System & Version
{Linux (Ubuntu 16)

Kernel Version (Linux Only)
(4.4.0-189-generic)

Platform
PC

Issue Description
Hi, after last update of librealsense-dkms all my usb cameras are not working anymore (internal webcam as well as any other USB camera including Intel D435). I have both USB2 and USB3 ports. Cameras are listed under lsusb but programs like cheese/skype/etc. cannot find them, there are no /dev/video* ...
My issue is similar to https://github.com/IntelRealSense/librealsense/issues/5868#issue-566598151
If I uninstall librealsense-dkms, everything works as expected (cameras works again), but this is not an option. Maybe at the time of update secure boot was enabled (sometimes windows update re-enable it, I have a dual boot), but now is disabled. Re-installing the package again does not produce any improvement and breaks the usb cameras again..
sudo apt-get install librealsense2-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  librealsense2-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 7.826 kB of archives.
After this operation, 61,8 MB of additional disk space will be used.
Get:1 http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial/main amd64 librealsense2-dkms all 1.3.12-0ubuntu1 [7.826 kB]
Fetched 7.826 kB in 47s (164 kB/s)
Selecting previously unselected package librealsense2-dkms.
(Reading database ... 362883 files and directories currently installed.)
Preparing to unpack .../librealsense2-dkms_1.3.12-0ubuntu1_all.deb ...
Unpacking librealsense2-dkms (1.3.12-0ubuntu1) ...
Setting up librealsense2-dkms (1.3.12-0ubuntu1) ...
Loading new librealsense2-dkms-1.3.12 DKMS files...
First Installation: checking all kernels...
Building only for 4.4.0-189-generic
Building initial module for 4.4.0-189-generic
Secure Boot not enabled on this system.
Done.

uvcvideo:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-189-generic/updates/dkms/

videodev.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-189-generic/updates/dkms/

hid-sensor-accel-3d.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-189-generic/updates/dkms/

hid-sensor-gyro-3d.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-189-generic/updates/dkms/

depmod....

DKMS: install completed.

Loading the modified modules into kernel... complete
Current status:
librealsense2-dkms, 1.3.12, 4.4.0-189-generic, x86_64: installed
mod: videodev 			 version: realsense2-dkms
mod: uvcvideo 			 version: 1.1.2.realsense-1.3.12
mod: hid_sensor_gyro_3d 	 version: realsense2-dkms
mod: hid_sensor_accel_3d 	 version: realsense2-dkms

I already tried to uninstall / reinstall everything using:
dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge
But nothing changes.. when librealsense is installed, all USB cameras are not working (Intel D435, integrated camera, USB webcam..)
Any help ?

Hi @roccopietrini   Does it make any difference if you update the udev rules after installing the librealsense packages, please?
Refresh the local packages cache.
sudo apt-get update
Update udev rules
sudo apt-get upgrade/install librealsense2-udev-rules

Hi,
I just tried to uninstall/reinstall librealsense2-udev-rules and update the udev rules with
udevadm control --reload-rules ; udevadm trigger
but nothing changes..

Thank you for trying the rule update.  May I confirm that when you are doing a clean package installation after having uninstalled packages from a previous attempt with a purge, you are installing only the two packages below and no others:
sudo apt-get install librealsense2-dkms
sudo apt-get install librealsense2-utils

Yes, I've just tried this..
Uninstall everything first:
 dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge
USB Cameras (except realsense of course) are working now, but then when I do the following:
sudo apt-get install librealsense2-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libatk-bridge2.0-dev libepoxy-dev libgmp-dev libgmpxx4ldbl libgtk-3-dev nettle-dev
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  librealsense2-udev-rules
The following NEW packages will be installed:
  librealsense2-dkms librealsense2-udev-rules
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/7.833 kB of archives.
After this operation, 61,8 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package librealsense2-dkms.
(Reading database ... 362700 files and directories currently installed.)
Preparing to unpack .../librealsense2-dkms_1.3.12-0ubuntu1_all.deb ...
Unpacking librealsense2-dkms (1.3.12-0ubuntu1) ...
Selecting previously unselected package librealsense2-udev-rules:amd64.
Preparing to unpack .../librealsense2-udev-rules_2.38.1-0~realsense0.3377_amd64.deb ...
Unpacking librealsense2-udev-rules:amd64 (2.38.1-0~realsense0.3377) ...
Setting up librealsense2-dkms (1.3.12-0ubuntu1) ...
Loading new librealsense2-dkms-1.3.12 DKMS files...
First Installation: checking all kernels...
Building only for 4.4.0-189-generic
Building initial module for 4.4.0-189-generic
Secure Boot not enabled on this system.
Done.

uvcvideo:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-189-generic/updates/dkms/

videodev.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-189-generic/updates/dkms/

hid-sensor-accel-3d.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-189-generic/updates/dkms/

hid-sensor-gyro-3d.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-189-generic/updates/dkms/

depmod.........

DKMS: install completed.

Loading the modified modules into kernel... complete
Current status:
librealsense2-dkms, 1.3.12, 4.4.0-189-generic, x86_64: installed
mod: videodev 			 version: realsense2-dkms
mod: uvcvideo 			 version: 1.1.2.realsense-1.3.12
mod: hid_sensor_gyro_3d 	 version: realsense2-dkms
mod: hid_sensor_accel_3d 	 version: realsense2-dkms
Setting up librealsense2-udev-rules:amd64 (2.38.1-0~realsense0.3377) ...

USB cameras KO.

I have not personally encountered this particular problem with librealsense before.  Your kindly provided log confirms Secure Boot not enabled on this system though.
The final line of the log is Setting up librealsense2-udev-rules:amd64 (2.38.1-0~realsense0.3377) ..., after which you report that the USB cameras are all disabled.  That would seem to throw suspicion back on the librealsense udev rules, if there is nothing else in your log after that point
@ev-mp is more experienced with the inner workings of udev than I am, so I will refer the question to them.
Hi @ev-mp do you think it is possible that an issue with udev could be causing all the USB cameras to become undetectable, given that the log provided in this case confirms that secure boot is disabled?

@roccopietrini , please attach the kernel log to review plug/unplug devices scenario - there is probably a conflicting driver/kernel issue

Here you are, thanks
kernel_log.txt

@roccopietrini , thank t you for the input - there is an error in several kernel modules reported.
Please disconnect cameras, restart the PC and provide a fresh log from boot till camera plugin

No.. I installed Ubuntu 16.04 LTS 4 years ago alongside win10 on a brand new laptop.
Uname produce
Linux rocco 4.4.0-189-generic #219-Ubuntu SMP Tue Aug 11 12:26:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
I want to add that everything was working fine couple of months ago. I have been using realsense for the last year without any problem..

In addition, I just tried to boot with kernel 4.4.0-187-generic and everything works as expected, so something happened with kernels 188 or 189..

Hi @roccopietrini   If you are able to boot successfully with kernel 4.4.0-187-generic, is it possible to use librealsense with that previous kernel, please?

Yes, this can be a workaround at the moment.. but I guess there is anyway a problem somewhere since looking online there are other user affected by this issue.. Thanks

@roccopietrini   I did further careful research, but it seems that this case and the non-RealSense forum that you linked to in the above comment are the only RealSense users that have reported being affected by this problem.
It may be worth re-testing later with subsequent kernel releases to see whether the problem fixes itself.  This was a strategy that worked in the days when Windows updates would stop RealSense cameras from working, only for them to work again when a new build of Windows was later released.

Thank you @MartyG-RealSense for the support! Let's see what happen with the new kernels, I'll keep you updated.

@MartyG-RealSense
I meet the same problem. Realsense camera used to work fine with 2.32 version.
Now with the new 2.38.1, realsense can't be detected by realsense-viewer.
Required Info |
-- | --
Camera Model | { D435 }
Firmware Version | (2.38.1)
Operating System & Version | {Linux (Ubuntu 16)
Kernel Version (Linux Only) | (4.4.0-190-generic)
Platform | PC
dmesg.log
Here's that part of dmesg log when I unplug-replug the camera
[  776.115131] usb 8-4: new SuperSpeed USB device number 2 using xhci_hcd
[  776.131548] usb 8-4: New USB device found, idVendor=8086, idProduct=0b3a
[  776.131555] usb 8-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  776.131559] usb 8-4: Product: Intel(R) RealSense(TM) Depth Camera 435i
[  776.131563] usb 8-4: Manufacturer: Intel(R) RealSense(TM) Depth Camera 435i
[  776.131567] usb 8-4: SerialNumber:<PHONE_NUMBER>11
[  776.132327] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[  776.132330] ------------[ cut here ]------------
[  776.132342] WARNING: CPU: 8 PID: 130 at /build/linux-UNiqWp/linux-4.4.0/drivers/media/media-device.c:380 __media_device_register+0xf0/0x140 [media]()
[  776.132344] Modules linked in: xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs overlay binfmt_misc nvidia_uvm(OE) skx_edac edac_core x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek(OE) snd_hda_codec_generic(OE) coretemp i915_bpo kvm_intel kvm hid_sensor_gyro_3d(OE) hid_sensor_accel_3d(OE) hid_sensor_trigger industrialio_triggered_buffer uvcvideo(OE) kfifo_buf videobuf2_vmalloc snd_hda_codec_hdmi(OE) industrialio videobuf2_memops videobuf2_v4l2 videobuf2_core hid_sensor_iio_common v4l2_common videodev(OE) intel_ips media irqbypass i2c_algo_bit crct10dif_pclmul crc32_pclmul snd_hda_intel(OE)
[  776.132409]  joydev snd_hda_codec(OE) snd_hda_core(OE) ghash_clmulni_intel snd_seq_midi snd_hwdep snd_seq_midi_event snd_rawmidi aesni_intel snd_pcm snd_seq dell_wmi sparse_keymap dcdbas video aes_x86_64 lrw gf128mul dell_smm_hwmon xillybus_pcie xillybus_core snd_seq_device 8250_fintek glue_helper snd_timer ablk_helper cryptd input_leds mei_me snd serio_raw wmi mei ioatdma shpchp soundcore mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_sensor_custom uas usb_storage hid_sensor_hub hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm nvidia(POE) psmouse ipmi_msghandler igb(OE) e1000e dca ptp ahci pps_core pata_acpi libahci fjes
[  776.132488] CPU: 8 PID: 130 Comm: kworker/8:1 Tainted: P        W  OE   4.4.0-190-generic #220-Ubuntu
[  776.132490] Hardware name: Dell Inc. Precision 7920 Tower/0RN4PJ, BIOS 1.8.0 08/17/2018
[  776.132500] Workqueue: usb_hub_wq hub_event
[  776.132503]<PHONE_NUMBER>000286 bc8e0fc833aa6547 ffff88084520f710 ffffffff8140edbb
[  776.132509]<PHONE_NUMBER>000000 ffffffffc17f1380 ffff88084520f748 ffffffff810864b2
[  776.132514]  ffff88084f4bf870 ffff88084f4bf870 ffff88072460b000 ffff88084f4bf800
[  776.132519] Call Trace:
[  776.132529]  [<ffffffff8140edbb>] dump_stack+0x6d/0x92
[  776.132539]  [<ffffffff810864b2>] warn_slowpath_common+0x82/0xc0
[  776.132544]  [<ffffffff810865fa>] warn_slowpath_null+0x1a/0x20
[  776.132550]  [<ffffffffc17efa40>] __media_device_register+0xf0/0x140 [media]
[  776.132559]  [<ffffffffc18bcb0b>] uvc_probe+0x48b/0x2a70 [uvcvideo]
[  776.132566]  [<ffffffff81649a9d>] usb_probe_interface+0x11d/0x300
[  776.132574]  [<ffffffff8157d752>] driver_probe_device+0x1c2/0x4b0
[  776.132579]  [<ffffffff8157db44>] __device_attach_driver+0x74/0xa0
[  776.132585]  [<ffffffff8157dad0>] ? __driver_attach+0x90/0x90
[  776.132590]  [<ffffffff8157b499>] bus_for_each_drv+0x69/0xb0
[  776.132596]  [<ffffffff8157d48c>] __device_attach+0xdc/0x170
[  776.132601]  [<ffffffff8157dbb3>] device_initial_probe+0x13/0x20
[  776.132607]  [<ffffffff8157c735>] bus_probe_device+0x95/0xa0
[  776.132612]  [<ffffffff8157a23e>] device_add+0x3de/0x640
[  776.132617]  [<ffffffff81647956>] usb_set_configuration+0x516/0x8e0
[  776.132622]  [<ffffffff8165294e>] generic_probe+0x2e/0x80
[  776.132627]  [<ffffffff81649948>] usb_probe_device+0x38/0x70
[  776.132632]  [<ffffffff8157d752>] driver_probe_device+0x1c2/0x4b0
[  776.132638]  [<ffffffff8157db44>] __device_attach_driver+0x74/0xa0
[  776.132643]  [<ffffffff8157dad0>] ? __driver_attach+0x90/0x90
[  776.132648]  [<ffffffff8157b499>] bus_for_each_drv+0x69/0xb0
[  776.132653]  [<ffffffff8157d48c>] __device_attach+0xdc/0x170
[  776.132659]  [<ffffffff8157dbb3>] device_initial_probe+0x13/0x20
[  776.132664]  [<ffffffff8157c735>] bus_probe_device+0x95/0xa0
[  776.132668]  [<ffffffff8157a23e>] device_add+0x3de/0x640
[  776.132675]  [<ffffffff81541900>] ? add_device_randomness+0x90/0x150
[  776.132681]  [<ffffffff8163c547>] usb_new_device+0x277/0x4b0
[  776.132686]  [<ffffffff8163dd27>] hub_port_connect+0x5e7/0xaf0
[  776.132692]  [<ffffffff8163e901>] hub_event+0x6d1/0xb20
[  776.132698]  [<ffffffff810a0d5b>] process_one_work+0x16b/0x4e0
[  776.132702]  [<ffffffff810a111e>] worker_thread+0x4e/0x590
[  776.132706]  [<ffffffff810a10d0>] ? process_one_work+0x4e0/0x4e0
[  776.132712]  [<ffffffff810a7857>] kthread+0xe7/0x100
[  776.132719]  [<ffffffff81864a41>] ? __schedule+0x301/0x810
[  776.132724]  [<ffffffff810a7770>] ? kthread_create_on_node+0x1e0/0x1e0
[  776.132729]  [<ffffffff81869da5>] ret_from_fork+0x55/0x80
[  776.132734]  [<ffffffff810a7770>] ? kthread_create_on_node+0x1e0/0x1e0
[  776.132737] ---[ end trace 0182a722d7593f0e ]---
[  776.133265] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[  776.133268] ------------[ cut here ]------------
[  776.133275] WARNING: CPU: 8 PID: 130 at /build/linux-UNiqWp/linux-4.4.0/drivers/media/media-device.c:380 __media_device_register+0xf0/0x140 [media]()
[  776.133278] Modules linked in: xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs overlay binfmt_misc nvidia_uvm(OE) skx_edac edac_core x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek(OE) snd_hda_codec_generic(OE) coretemp i915_bpo kvm_intel kvm hid_sensor_gyro_3d(OE) hid_sensor_accel_3d(OE) hid_sensor_trigger industrialio_triggered_buffer uvcvideo(OE) kfifo_buf videobuf2_vmalloc snd_hda_codec_hdmi(OE) industrialio videobuf2_memops videobuf2_v4l2 videobuf2_core hid_sensor_iio_common v4l2_common videodev(OE) intel_ips media irqbypass i2c_algo_bit crct10dif_pclmul crc32_pclmul snd_hda_intel(OE)
[  776.133329]  joydev snd_hda_codec(OE) snd_hda_core(OE) ghash_clmulni_intel snd_seq_midi snd_hwdep snd_seq_midi_event snd_rawmidi aesni_intel snd_pcm snd_seq dell_wmi sparse_keymap dcdbas video aes_x86_64 lrw gf128mul dell_smm_hwmon xillybus_pcie xillybus_core snd_seq_device 8250_fintek glue_helper snd_timer ablk_helper cryptd input_leds mei_me snd serio_raw wmi mei ioatdma shpchp soundcore mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_sensor_custom uas usb_storage hid_sensor_hub hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm nvidia(POE) psmouse ipmi_msghandler igb(OE) e1000e dca ptp ahci pps_core pata_acpi libahci fjes
[  776.133393] CPU: 8 PID: 130 Comm: kworker/8:1 Tainted: P        W  OE   4.4.0-190-generic #220-Ubuntu
[  776.133396] Hardware name: Dell Inc. Precision 7920 Tower/0RN4PJ, BIOS 1.8.0 08/17/2018
[  776.133402] Workqueue: usb_hub_wq hub_event
[  776.133404]<PHONE_NUMBER>000286 bc8e0fc833aa6547 ffff88084520f710 ffffffff8140edbb
[  776.133409]<PHONE_NUMBER>000000 ffffffffc17f1380 ffff88084520f748 ffffffff810864b2
[  776.133414]  ffff88084f4bf870 ffff88084f4bf870 ffff88072460a400 ffff88084f4bf800
[  776.133419] Call Trace:
[  776.133425]  [<ffffffff8140edbb>] dump_stack+0x6d/0x92
[  776.133431]  [<ffffffff810864b2>] warn_slowpath_common+0x82/0xc0
[  776.133437]  [<ffffffff810865fa>] warn_slowpath_null+0x1a/0x20
[  776.133443]  [<ffffffffc17efa40>] __media_device_register+0xf0/0x140 [media]
[  776.133449]  [<ffffffffc18bcb0b>] uvc_probe+0x48b/0x2a70 [uvcvideo]
[  776.133455]  [<ffffffff81649a9d>] usb_probe_interface+0x11d/0x300
[  776.133461]  [<ffffffff8157d752>] driver_probe_device+0x1c2/0x4b0
[  776.133467]  [<ffffffff8157db44>] __device_attach_driver+0x74/0xa0
[  776.133472]  [<ffffffff8157dad0>] ? __driver_attach+0x90/0x90
[  776.133477]  [<ffffffff8157b499>] bus_for_each_drv+0x69/0xb0
[  776.133482]  [<ffffffff8157d48c>] __device_attach+0xdc/0x170
[  776.133488]  [<ffffffff8157dbb3>] device_initial_probe+0x13/0x20
[  776.133493]  [<ffffffff8157c735>] bus_probe_device+0x95/0xa0
[  776.133497]  [<ffffffff8157a23e>] device_add+0x3de/0x640
[  776.133502]  [<ffffffff81647956>] usb_set_configuration+0x516/0x8e0
[  776.133507]  [<ffffffff8165294e>] generic_probe+0x2e/0x80
[  776.133511]  [<ffffffff81649948>] usb_probe_device+0x38/0x70
[  776.133517]  [<ffffffff8157d752>] driver_probe_device+0x1c2/0x4b0
[  776.133522]  [<ffffffff8157db44>] __device_attach_driver+0x74/0xa0
[  776.133527]  [<ffffffff8157dad0>] ? __driver_attach+0x90/0x90
[  776.133532]  [<ffffffff8157b499>] bus_for_each_drv+0x69/0xb0
[  776.133537]  [<ffffffff8157d48c>] __device_attach+0xdc/0x170
[  776.133542]  [<ffffffff8157dbb3>] device_initial_probe+0x13/0x20
[  776.133547]  [<ffffffff8157c735>] bus_probe_device+0x95/0xa0
[  776.133552]  [<ffffffff8157a23e>] device_add+0x3de/0x640
[  776.133556]  [<ffffffff81541900>] ? add_device_randomness+0x90/0x150
[  776.133562]  [<ffffffff8163c547>] usb_new_device+0x277/0x4b0
[  776.133567]  [<ffffffff8163dd27>] hub_port_connect+0x5e7/0xaf0
[  776.133573]  [<ffffffff8163e901>] hub_event+0x6d1/0xb20
[  776.133578]  [<ffffffff810a0d5b>] process_one_work+0x16b/0x4e0
[  776.133582]  [<ffffffff810a111e>] worker_thread+0x4e/0x590
[  776.133586]  [<ffffffff810a10d0>] ? process_one_work+0x4e0/0x4e0
[  776.133591]  [<ffffffff810a7857>] kthread+0xe7/0x100
[  776.133595]  [<ffffffff81864a41>] ? __schedule+0x301/0x810
[  776.133600]  [<ffffffff810a7770>] ? kthread_create_on_node+0x1e0/0x1e0
[  776.133604]  [<ffffffff81869da5>] ret_from_fork+0x55/0x80
[  776.133609]  [<ffffffff810a7770>] ? kthread_create_on_node+0x1e0/0x1e0
[  776.133612] ---[ end trace 0182a722d7593f0f ]---
[  776.191007] hid-sensor-hub 0003:8086:0B3A.0005: No report with id 0xffffffff found
[  776.191661] hid-sensor-hub 0003:8086:0B3A.0005: No report with id 0xffffffff found
[  776.247091] hid-sensor-hub 0003:8086:0B3A.0005: No report with id 0xffffffff found
[  776.247911] hid-sensor-hub 0003:8086:0B3A.0005: No report with id 0xffffffff found

Hi @gachiemchiep   Does the Depth Quality Tool function okay on your computer in 2.38.1 please?

Hello @MartyG-RealSense .
Unfortunately, I switch back to 2.32.1 so I couldn't check that.
As I remember, realsense-viewer couldn't detect any connected camera so I think the Depth Quality Tool will not work

Also for me with kernel 4.4.0-190-generic problem is still there, looking in dmseg I find this on boot:
[   17.665824] videodev: loading out-of-tree module taints kernel.
[   17.665912] videodev: module verification failed: signature and/or required key missing - tainting kernel
[   17.668273] Linux video capture interface: v2.00
[   18.271345] uvcvideo: Found UVC 1.00 device HP Truevision HD (064e:930b)
[   18.271348] ------------[ cut here ]------------
[   18.271352] WARNING: CPU: 1 PID: 412 at /build/linux-UNiqWp/linux-4.4.0/drivers/media/media-device.c:380 __media_device_register+0xf0/0x140 [media]()
[   18.271354] Modules linked in: uvcvideo(OE+) videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev(OE) kvm media irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel arc4 rtl8188ee aesni_intel rtl_pci aes_x86_64 rtlwifi lrw mac80211 gf128mul glue_helper ablk_helper snd_hda_codec_realtek snd_hda_codec_hdmi cryptd cfg80211 snd_hda_codec_generic joydev snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm input_leds serio_raw snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq intel_pch_thermal snd_seq_device snd_timer shpchp snd soundcore processor_thermal_device int340x_thermal_zone int3400_thermal intel_soc_dts_iosf acpi_thermal_rel mei_me mei hp_wireless lpc_ich acpi_pad mac_hid parport_pc ppdev lp parport autofs4 hid_generic usbhid amdkfd amd_iommu_v2
[   18.271392]  i915 radeon i2c_algo_bit ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops ahci libahci r8169 drm mii wmi video i2c_hid hid fjes
[   18.271403] CPU: 1 PID: 412 Comm: systemd-udevd Tainted: G           OE   4.4.0-190-generic #220-Ubuntu
[   18.271404] Hardware name: HP HP Notebook/80C2, BIOS F.30 12/24/2019
[   18.271406]<PHONE_NUMBER>000286 8d36a01b1c62b7c1 ffff88024ff579b0 ffffffff8140edbb
[   18.271408]<PHONE_NUMBER>000000 ffffffffc07ce380 ffff88024ff579e8 ffffffff810864b2
[   18.271410]  ffff88008e26f870 ffff88008e26f870 ffff88008e26f800<PHONE_NUMBER>000003
[   18.271412] Call Trace:
[   18.271417]  [<ffffffff8140edbb>] dump_stack+0x6d/0x92
[   18.271420]  [<ffffffff810864b2>] warn_slowpath_common+0x82/0xc0
[   18.271423]  [<ffffffff810865fa>] warn_slowpath_null+0x1a/0x20
[   18.271425]  [<ffffffffc07cca40>] __media_device_register+0xf0/0x140 [media]
[   18.271429]  [<ffffffffc0871b30>] uvc_probe+0x490/0x2aa0 [uvcvideo]
[   18.271432]  [<ffffffff81649a9d>] usb_probe_interface+0x11d/0x300
[   18.271436]  [<ffffffff8157d752>] driver_probe_device+0x1c2/0x4b0
[   18.271438]  [<ffffffff8157dac7>] __driver_attach+0x87/0x90
[   18.271440]  [<ffffffff8157da40>] ? driver_probe_device+0x4b0/0x4b0
[   18.271443]  [<ffffffff8157b3c2>] bus_for_each_dev+0x72/0xc0
[   18.271445]  [<ffffffff8157cf6e>] driver_attach+0x1e/0x20
[   18.271447]  [<ffffffff8157caa2>] bus_add_driver+0x1e2/0x280
[   18.271449]  [<ffffffff8157e3e0>] driver_register+0x60/0xe0
[   18.271451]  [<ffffffff81648454>] usb_register_driver+0x84/0x140
[   18.271453]  [<ffffffffc0888000>] ? 0xffffffffc0888000
[   18.271456]  [<ffffffffc0888024>] uvc_init+0x24/0x1000 [uvcvideo]
[   18.271459]  [<ffffffff810021f5>] do_one_initcall+0xb5/0x200
[   18.271462]  [<ffffffff811fbca5>] ? kmem_cache_alloc_trace+0x185/0x1f0
[   18.271465]  [<ffffffff81199cf5>] do_init_module+0x5f/0x1cf
[   18.271468]  [<ffffffff81113dfa>] load_module+0x16aa/0x1c50
[   18.271470]  [<ffffffff811102f0>] ? __symbol_put+0x60/0x60
[   18.271472]  [<ffffffff81224c10>] ? kernel_read+0x50/0x80
[   18.271475]  [<ffffffff811145e4>] SYSC_finit_module+0xb4/0xe0
[   18.271477]  [<ffffffff8111462e>] SyS_finit_module+0xe/0x10
[   18.271481]  [<ffffffff8186991b>] entry_SYSCALL_64_fastpath+0x22/0xd0
[   18.271482] ---[ end trace b32dc362b885a90d ]---

any idea?

@roccopietrini @gachiemchiep  So the problem seems to be that the 4.4 kernel works okay up to  4.4.0-187 but does not work in kernel releases in the 4.4 series that come after that (188, 189, 190).
Do either of your projects have the option of using the RSUSB backend method of building librealsense that is not dependent on kernel patches?

I don't know much of this method.. can you give me some details about pros/cons and how to do it ? Thank you

Details of this method for building with the source-code folder using RSUSB can be found at the link below:
https://github.com/IntelRealSense/librealsense/issues/6368#issuecomment-636316279
The link below discusses the advantages and disadvantages of using the backend method compared to kernel patching. Scroll down the comment to the section of it headed What are the advantages and disadvantages of using libuvc vs patched kernel modules?
https://github.com/IntelRealSense/librealsense/issues/5212#issuecomment-552184604

Hi @roccopietrini   Do you still require assistance with this case, please?   Thanks!

Hi @MartyG-RealSense .. I didn't tried the RSUSB backend method, I would rather prefer to solve my issue in a canonical way, given the fact that I'm running a supported kernel and I am not the only one experiencing this problem. You can close at the moment, we'll see what happens with new kernels.

Okay, thank you very much @roccopietrini - good luck!

Just wanted to add that installing hwe and going to kernel 4.15.0-120-generic solved my problem! Thank you

I have the same problem with kernel 5.15.0-69-generic. what should I do to let my usb webcam work again?

Hi @matbord   Which RealSense SDK version are you using, please?  Support for kernel 5.15 was only added in SDK version 2.53.1.
If you are experiencing a possible kernel related conflict then you could build the SDK from source code with the RSUSB backend installation method, which bypasses the kernel.  This makes an RSUSB build of the SDK not dependent on Linux versions or kernel versions.

Hello, these are the version I installed:
$ dpkg -l | grep realsense
librealsense2-dkms                           1.3.19-0ubuntu1                     all          Modified kernel modules for librealsense2
librealsense2-udev-rules:amd64             2.53.1-0~realsense0.8250            amd64        Intel(R) RealSense(tm) Camera Capture API - udev rules
Moreover where can I find the RSUSB backend installation method?

You are using SDK 2.53.1.  Thanks very much for the confirmation.
Instructions for an RSUSB backend source code build of the SDK can be found at https://github.com/IntelRealSense/librealsense/issues/9931#issuecomment-964289692


Ensure that iOS and Android FFI interfaces are at feature parity

Notable inconsistencies:

in zcash-light-client-ffi, the a newly generated unified spending key is passed back across the FFI as a binary value; in zcash-android-wallet-sdk it is passed via its string encoding. The behavior in zcash-light-client-ffi is a bit odd, because everywhere that the USK is provided as an argument to a FFI method, it is passed as a string that is then decoded in the same fashion is done in the Android FFI, but I don't see where the encoding is implemented. Not a blocker for deployment, just a puzzling inconsistency.
In zcash-android-wallet-sdk, a methods are provided to directly derive both UFVKs and UAs from the wallet seed, whereas in zcash-light-client-ffi the UFVK is derived from the spending key, and the only methods provided for UA derivation rely upon the internal state of the wallet database. Essentially, the Android API exposes key and address derivation in ways that the iOS sdk does not; an incautious user of the Android API could potentially derive addresses from keys that are not used for scanning by the wallet. We should consider removing the derivation tool from Android as it was previously removed from the Swift API.
zcash-light-client-ffi exposes WalletWrite::get_next_available_address; the Android SDK does not provide any comparable method.
zcash-light-client-ffi provides zcashlc_get_typecodes_for_unified_address_receivers and zcashlc_get_address_metadata; the Android SDK does not provide comparable methods.
zcash-android-wallet-sdk provides a isValidSpendingKey method; the iOS SDK does not provide this method.
zcash-light-client-ffi provides is_valid_sapling_extended_spending_key, whereas the Android SDK does not. This might be a legacy API that should be removed?
zcash-light-client-ffik provides is_valid_unified_full_viewing_key; the Android SDK does not. We should investigate the uses of this method.
zcash-light-client-ffi provides zcashlc_get_verified_transparent_balance (which operates per-address) and zcashlc_get_verified_transparent_balance_for_account; the Android SDK does not. We should investigate this discrepancy.
zcash-light-client-ffi provides zcashlc_get_total_transparent_balance_for_account; the Android SDK does not (total balance is provided at the address level only.) We should investigate this discrepancy.
zcash-light-client-ffi can retrieve binary memos with zcashlc_get_memo; the Android SDK appears to only be able to return UTF-8 memos using getMemoAsUtf8.
zcash-light-client-ffi provides zcashlc_get_seed_fingerprint; the Android SDK doesn't appear to provide this.
In zcash-light-client-ffi, two separate methods are used to insert subtree root data; in the Android SDK a single putSubtreeRoots method is used.
In both SDKs, use of ZIP 317 fees is still optional. The SDKs should migrate to always using ZIP 317 fees.
zcash-light-client-ffi provides support for proposing a transaction based on a ZIP 321 URI; the Android SDK does not yet provide this method.


Hidden Tilemaps affects Shadows

Godot version:

3.2.3 Stable Official
OS/device including version:

Windows 10, RTX 2070, for both GLES2 and GLES3
Issue description:

Hidden tilemaps affects Light Occlusion. Don't know if this is the intended behaviour, but the only way to hide and disable shadows on tilemaps is by tweaking Tilemap's Occluder's Light Mask.
Steps to reproduce:

Create two tilemaps
Use the same tileset on both
Add Occluder to tiles
Hide one of the Tilemaps
Create a Light2D and turn on it's shadows

Minimal reproduction project:

hidden_tilemap_light_occlusion.zip

@groud What's your opinion on this?

@groud What's your opinion on this?

Looks lit a bug yes. A hidden tilemap should not have visible occluders I suppose.

Fixed by #54435.


Add an option allowing use without a multiprocessing pool

[Spleeter] - Add an option allowing use without a multiprocessing pool
This PR adds a keyword argument allowing a Separator to be used asynchronously within a multiprocessing-created subprocess (by bypassing its multiprocessing.Pool and doing its work in the main process). Without this option enabled, attempting to do so will fail with an error "AssertionError: daemonic processes are not allowed to have children."
How this patch was tested
I'm working on a tool that calls separate_to_file using Pool.apply_async. Prior to this patch it failed with the AssertionError above. After applying the patch and passing multiprocess=False to the Separator constructor the separation works as expected.
Documentation link and external references
Info about the exception in the Python docs: https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Process.daemon
Here's a SO example of someone encountering the same exception in a similar scenario: https://stackoverflow.com/questions/51485212/multiprocessing-gives-assertionerror-daemonic-processes-are-not-allowed-to-have
It seems that this problem could also be avoided by using a ThreadPool but I understand spleeter to be fairly CPU-bound so threads aren't a great solution. However if spleeter does most of its heavy lifting in its own subprocesses, it might work to use a ThreadPool instead. I'm willing to try it if you'd prefer.

Hi @valrus  and thanks for the patch.
The CI seems to be stuck in some way that we need to investigate. In the mean time I'll take a look at the code itself. I think having an argument to force synchronous execution is meaningful in itself but just to know, why would you need the parallelism to occur at the higher level than the Separator class ?

Hi @mmoussallam, there's certainly no rush merging this PR. I'm using my fork in the meantime.
I need to use Separator in a subprocess because I'm running it as a background task for a web server and I don't want the splitting process to block the server while it's running.

Hi @valrus thanks that makes sense :)


Define feature gates centrally and document relevance for components

How to categorize this PR?

/area dev-productivity documentation
/kind cleanup
/merge squash
What this PR does / why we need it:
As described in https://github.com/gardener/gardener/issues/5486#issuecomment-1060379518.
Which issue(s) this PR fixes:
Fixes #5486
Release note:

The [feature gate documentation](https://github.com/gardener/gardener/tree/master/docs/deployment/feature_gates.md) does now contain information about which of the feature gates are relevant for which Gardener components.

Generally, my feeling is that feature gates should simply be configured in all components consistently (i.e. enabled everywhere or not at all) and no one should think or care about which of them has handling for it or not.
WDYT?

@timebertt We discussed your concerns beginning of this week but agreed on this solution (ref https://github.com/gardener/gardener/issues/5486#issuecomment-1060379518).

How do we make sure to prevent such programmer errors, which are easy to miss?
We still don't, but I also don't think that this is a huge problem (not even a small one, actually). Did we ever hit such case? Such programmer errors will easily reveal during development/testing, or?

We still don't, but I also don't think that this is a huge problem (not even a small one, actually). Did we ever hit such case?

True, we have not hit such a case yet – I think.

Such programmer errors will easily reveal during development/testing, or?

Hmm, at least only during manual testing. Unit tests typically mutate the feature gates map. If you forget to adapt the component's features gate map, this will only be revealed during manual tests.
But ok, I'm fine to continue like this, if you have already agreed on this approach 👍