6.3.0: Changing preset will revert to other temperature ("period (0.0) min is < 5 min -> forget the regulation send")

Version of the custom_component
6.3.0
Configuration
My VTherm attributes are the following:
hvac_modes:
  - "off"
  - heat
min_temp: 17
max_temp: 25
target_temp_step: 0.5
preset_modes:
  - none
  - eco
  - comfort
  - boost
current_temperature: 22.4
temperature: 23
preset_mode: boost
is_on: true
hvac_action: null
hvac_mode: heat
type: null
is_controlled_by_central_mode: true
last_central_mode: null
frost_temp: 0
eco_temp: 19.5
boost_temp: 23
comfort_temp: 19.5
frost_away_temp: 0
eco_away_temp: 0
boost_away_temp: 0
comfort_away_temp: 0
power_temp: 13
target_temperature_step: 0.5
ext_current_temperature: 11.19341003798929
ac_mode: false
current_power: null
current_power_max: null
saved_preset_mode: boost
saved_target_temp: 20
saved_hvac_mode: null
motion_sensor_entity_id: null
motion_state: null
power_sensor_entity_id: null
max_power_sensor_entity_id: null
overpowering_state: null
presence_sensor_entity_id: null
presence_state: null
window_state: "off"
window_auto_state: "off"
window_bypass_state: false
window_sensor_entity_id: null
window_delay_sec: 120
window_auto_enabled: false
window_auto_open_threshold: null
window_auto_close_threshold: null
window_auto_max_duration: null
window_action: window_turn_off
security_delay_min: 60
security_min_on_percent: 0.5
security_default_on_percent: 0.1
last_temperature_datetime: "2024-10-02T17:58:03.418930+02:00"
last_ext_temperature_datetime: "2024-10-02T18:05:00.957734+02:00"
security_state: false
minimal_activation_delay_sec: 10
device_power: 1
mean_cycle_power: null
total_energy: 0
last_update_datetime: "2024-10-02T18:05:01.038395+02:00"
timezone: Europe/Vienna
temperature_unit: °C
is_device_active: true
ema_temp: 22.45
is_used_by_central_boiler: false
is_over_climate: true
start_hvac_action_date: null
underlying_climate_0: climate.wohnzimmer_eve_trv_thermostat
underlying_climate_1: null
underlying_climate_2: null
underlying_climate_3: null
auto_fan_mode: auto_fan_none
current_auto_fan_mode: auto_fan_none
auto_activated_fan_mode: null
auto_deactivated_fan_mode: null
auto_regulation_use_device_temp: true
friendly_name: Wohnzimmer Heizung
supported_features: 401

Describe the bug
I'm trying to:
Change the preset for a vtherm device, e.g. from comfort to boost.
And I expect:
It changes.
But I observe this ....
It jumps back to a different temperature and "none" preset after 1-2 seconds. Only the second attempt of chaging the preset works. The first never works.
Debug log
Here are logs for a single climate device, below I'll attach the log for all my devices and a 5 minute period in which I tried to change the presets.
17:57:53 - Set preset_mode: boost force=False
17:57:53 - find preset temp: boost
17:57:53 - Calling ThermostatClimate._send_regulated_temperature force=True
17:57:53 - regulation calculation will be done
17:57:53 - Regulated temp have changed to 23.0. Resend it to underlyings
17:57:53 - Sending event EventType.PRESET_EVENT with data: {'preset': 'boost'}
17:57:53 - Calling ThermostatClimate._send_regulated_temperature force=False
17:57:53 - period (0.0) min is < 5 min -> forget the regulation send
17:57:55 - Underlying climate climate.wohnzimmer_eve_trv_thermostat changed. Event.new_hvac_mode is heat, current_hvac_mode=heat, new_hvac_action=None, old_hvac_action=None
17:57:55 - Target temp in underlying have change to 20.0
17:57:55 - Set target temp: 20.0
17:57:55 - Calling ThermostatClimate._send_regulated_temperature force=True
17:57:55 - regulation calculation will be done
17:57:55 - Regulated temp have changed to 20.0. Resend it to underlyings
17:57:55 - Calling ThermostatClimate._send_regulated_temperature force=False
17:57:55 - period (0.0) min is < 5 min -> forget the regulation send
17:57:55 - Calling ThermostatClimate._send_regulated_temperature force=False
17:57:55 - period (0.0) min is < 5 min -> forget the regulation send
17:57:57 - Underlying climate climate.wohnzimmer_eve_trv_thermostat changed. Event.new_hvac_mode is heat, current_hvac_mode=heat, new_hvac_action=None, old_hvac_action=None
17:57:57 - underlying event is received less than 10 sec after command. Forget it to avoid loop
17:57:58 - Underlying climate climate.wohnzimmer_eve_trv_thermostat changed. Event.new_hvac_mode is heat, current_hvac_mode=heat, new_hvac_action=None, old_hvac_action=None
17:57:58 - underlying event is received less than 10 sec after command. Forget it to avoid loop
17:58:00 - Calling ThermostatClimate._send_regulated_temperature force=False
17:58:00 - period (0.1) min is < 5 min -> forget the regulation send
17:58:03 - Set preset_mode: boost force=False
17:58:03 - find preset temp: boost
17:58:03 - Calling ThermostatClimate._send_regulated_temperature force=True
17:58:03 - regulation calculation will be done
17:58:03 - Regulated temp have changed to 23.0. Resend it to underlyings
17:58:03 - Sending event EventType.PRESET_EVENT with data: {'preset': 'boost'}
17:58:03 - Calling ThermostatClimate._send_regulated_temperature force=False
17:58:03 - period (0.0) min is < 5 min -> forget the regulation send
17:58:04 - Underlying climate climate.wohnzimmer_eve_trv_thermostat changed. Event.new_hvac_mode is heat, current_hvac_mode=heat, new_hvac_action=None, old_hvac_action=None
17:58:04 - underlying event is received less than 10 sec after command. Forget it to avoid loop
17:58:35 - Calling ThermostatClimate._send_regulated_temperature force=False
17:58:35 - period (0.5) min is < 5 min -> forget the regulation send
17:59:00 - Calling ThermostatClimate._send_regulated_temperature force=False
17:59:00 - period (0.9) min is < 5 min -> forget the regulation send
18:00:00 - Calling ThermostatClimate._send_regulated_temperature force=False
18:00:00 - period (2.0) min is < 5 min -> forget the regulation send```

home-assistant_2024-10-02T16-00-55.234Z.log

Hello @maia ,
what happens is that, your TRV change its target alone and VTherm follows this change.
Maybe someone change the target directly on the TRV, maybe the TRV itself change this target value (is there a internal regulation mecanism in Eve TRV ?);
17:57:55 - Underlying climate climate.wohnzimmer_eve_trv_thermostat changed. Event.new_hvac_mode is heat, current_hvac_mode=heat, new_hvac_action=None, old_hvac_action=None
17:57:55 - Target temp in underlying have change to 20.0
17:57:55 - Set target temp: 20.0
17:

in the log we can see that the underlying have change to 20.0 (Target temp in underlying have change to 20.0
) and Vtherm have follow this 20.0 (Set target temp: 20.0)

Nope, that's not it. I didn't touch the TRV and it does not change its target temperature by itself. The issue seems to appear when turning off self regulation. I just tried again:

Target temperature in HA was 21.5, with vtherm self-regulation ("slow") the TRV was set to 23.5.
I turned off self-regulation in vtherm. The exact moment I saved the TRV went to a new target temperature of 20.0°C, although HA still showed "comfort 21.5°C"
I switched from comfort (21.5°C) to boost (22.5°C) in HA. The TRV lowers its target temperature instantly to 19°C (!). HA shows "preset: manual" with a target temperature of 20.5°C.

This weird behaviour shows up when disabling self-regulation.

Subscribing because of https://github.com/jmcollin78/versatile_thermostat/discussions/507

Because of @maia 's hint, I experimentally switched to enabled self regulation for one TRV group which fixed this issue for me.
But afterwards, I was not able to disable self regulation again. At first, only that one VT could no longer be set up because of a "faulty configuration". After a restart of HA, all VTs could no longer be setup. I had to uninstall all configurations and reinstall and reconfigure the VT custom integration to get it working again. Unfortunately I did capture no logs as I wanted to get everything working again as fast as possible.
So now I have a completely fresh installed VT which never had self regulation enabled, but the problem is there from the beginnig again.
While wrriting this, I notice that over night almost all VT units have gone offline again over night. The log looks like this:
2024-10-04 20:53:08.388 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Central configuration for versatile_thermostat
2024-10-04 20:53:09.571 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry WZ: Smart Thermostat for versatile_thermostat

The log also contains eintries like
2024-10-04 20:53:09.875 WARNING (MainThread) [custom_components.versatile_thermostat.base_thermostat] VersatileThermostat-SZ: Smart Thermostat - Undefined target temperature, falling back to 5.0

which is strange, because all the temperatures have been setup by the integration ui. I don't know what happened at 20:53 so mess up VT.
Moreover I wonder what the log entries like
2024-10-04 20:53:09.906 WARNING (MainThread) [custom_components.versatile_thermostat.pi_algorithm] Temporarily skipping the self-regulation algorithm while the configured sensor for room temperature is unavailable

mean, because the self regulation isn't enabled at all and the temperature sensors seem to be online.
These errors happen for all my configured VTs including the central configuration. Only one VT which has been turned off all the time and another one which has the same configuration like all others but has no "window open" detection still have no configuration error..
I then reconfigured the central configuration and switched "window open detection" from "0" to "-1" (yes, you can set this to negative values with the buttons....) and back to "0", and now all VTs are back online again.
Something strange is definitely going on with the central configuration...

ok. i will try to reproduce with your explanations.

There seem to be two problems for me, I don't know if they are related:

About once a day some of the VT units at first go rather silently offline (no sensible entries to be seen in the lovelace card, no more working temperature regulation). Then I change something in the central configuration, which leads to "configuration errors" for most of the VTs. Then I change this central configuration value once again back, and everything is fine again. This happens regardless of the self regulation settings.
The issue described here: Settings/presets can no longer be set reliably and are reset after a few seconds as long as there is no additional self regulation by VT. Once self regulation is enabled, everything works.

I grepped for Versatile in homeassistant.log for the last two days, maybe this contains helpfull information:
errors.zip

There seem to be two problems for me, I don't know if they are related:

Interestingly as you I am experiencing both those issues, so maybe they are related.

About once a day some of the VT units at first go rather silently offline (no sensible entries to be seen in the lovelace card, no more working temperature regulation). Then I change something in the central configuration, which leads to "configuration errors" for most of the VTs. Then I change this central configuration value once again back, and everything is fine again. This happens regardless of the self regulation settings.

I'm seeing this after HA restarts. I've added an automation that will reload the vtherm configuration a few minutes after restarting HA. Can you check if reloading the yaml configuration (in developer tools) get's everything back to okay for you too?

I'm seeing this after HA restarts. I've added an automation that will reload the vtherm configuration a few minutes after restarting HA. Can you check if reloading the yaml configuration (in developer tools) get's everything back to okay for you too?

Just tried it out - you're right, this way I can reproduce both the error and the workaround!

Unfortunately, only an hour later, the VT thermostats are offline again without any action ny myself.
I also noticed that suddenly the features "Power management" and "Presence detection" are enabled fot the VTs (I never enabled or used that) and can't be disabled any more...
Something is very, very wrong here :-/ ...

So... I deleted all VTs, re-installed the custom integration. and then recreated the VTs. From the very first moment the log was filled with errors like this:
errors.txt.zip
Once again this error could be resolved by changing and re-changing some settings of central configuration (probably reloading the yamls would have done the job, too).
It is as if VT has problems interpreting/writing its own configuration.

 Sorry for not being so much available for this issue.
I will try to review all your comment and see with the log what happens

I will come back to original post of @maia now.

Nope, that's not it. I didn't touch the TRV and it does not change its target temperature by itself. The issue seems to appear when turning off self regulation. I just tried again:

Target temperature in HA was 21.5, with vtherm self-regulation ("slow") the TRV was set to 23.5.
I turned off self-regulation in vtherm. The exact moment I saved the TRV went to a new target temperature of 20.0°C, although HA still showed "comfort 21.5°C"
I switched from comfort (21.5°C) to boost (22.5°C) in HA. The TRV lowers its target temperature instantly to 19°C (!). HA shows "preset: manual" with a target temperature of 20.5°C.

This weird behaviour shows up when disabling self-regulation.

If I (re) look at your logs what happens is clear:
First you change the preset:
Set preset_mode: boost
then, the regulation calculation try to send 23°:
Regulated temp have changed to 23.0. Resend it to underlyings
then, because there was already a command send to TRV in the last 5 minutes, this command is discarded:
period (0.0) min is < 5 min -> forget the regulation send
then, 2 sec later, without any command from VTherm, your TRV decide itself, alone, on its behalf to change its target temperature:
`Underlying climate climate.wohnzimmer_eve_trv_thermostat changed. Event.new_hvac_mode is heat, current_hvac_mode=heat, new_hvac_action=None, old_hvac_action=None``
then VTherm follows the new target temp from your TRV which is set to 20°:
17:57:55 - Target temp in underlying have change to 20.0
I guess EVE TRV have internal regulation algorithm than is conflicting with VTherm.
This mecanism prevent VTherm for looping due to the conflict. I will be able to do anything on this.
I would like you to confirm what I see. If yes, I will write a disclaimer on EVE TRV in the Read-me. I'm so sad about this bad news.

Thanks for the feedback, however for the time being (as I need a controllable TRV :-/ ) I have converted my setup to more simple and probably more robust templates. Maybe this is even a better solution, as I don't use that self-regulation stuff. I will continue montoring this issue, however.

then, 2 sec later, without any command from VTherm, your TRV decide itself, alone, on its behalf to change its target temperature: `Underlying climate climate.wohnzimmer_eve_trv_thermostat changed. Event.new_hvac_mode is heat, current_hvac_mode=heat, new_hvac_action=None, old_hvac_action=None``
…
I guess EVE TRV have internal regulation algorithm than is conflicting with VTherm.

I have been using these Eve TRV for a few years now and I didn't have any issues last winter with vtherm 4.x, it only appeared a few months ago when the new heating season started, I upgraded vtherm 4.x to 6.x and upgraded the Eve TRV firmware from Homekit to Matter. As you might remember, the development of the auto-regulation feature in vtherm was something I actively supported. Everything was working fine last year. That's the confusing part.
I tried to reproduce the issue right now while filming it, but didn't manage to reproduce it on the TRV I currently have access to. I had the issue with two other TRVs which I can't access tonight. I will re-check these in the next few days.
The Eve Thermo TRV has an internal PID algorithm that regulates the valve opening percentage. But I've never before seen it change the (visible) target temperature itself. I have no explanation why a switch from comfort to boost lowers the target temperature on the TRV and the vtherm device switches to "manual" and displays another temperature – and only with self-regulation turned off.
I will re-attempt to disable self-regulation for all TRVs this weekend, in case it's not too warm for heating, and will get back to you.

I have been using these Eve TRV for a few years now and I didn't have any issues last winter with vtherm 4.x, it only appeared a few months ago when the new heating season started, I upgraded vtherm 4.x to 6.x and upgraded the Eve TRV firmware from Homekit to Matter. As you might remember, the development of the auto-regulation feature in vtherm was something I actively supported. Everything was working fine last year. That's the confusing part.

Yes. This is really strange. Before 6.3, VTherm always send an interval of temperature with the target. When changing the target temp to 20°, VTherm was sending target temp to 20° and min_temp and max_temp, even if the climate doesn't support a feature name TARGET_RANGE. That is now controled by HA 2024.10 and that is what I fix in 6.3.0. Now, if you climate doesn't support the TARGET_RANGE, VTherm only send the target value (and not min_temp and max_temp). This is what was expected by HA.
I guess this change have now an impact on how the internal regulation of your TRV works.
Your TRV have this feature:
supported_features: 401 and 401 means it doesn't support the TARGET_RANGE.
Here are the code:
class ClimateEntityFeature(IntFlag):
    """Supported features of the climate entity."""

    TARGET_TEMPERATURE = 1
    TARGET_TEMPERATURE_RANGE = 2
    TARGET_HUMIDITY = 4
    FAN_MODE = 8
    PRESET_MODE = 16
    SWING_MODE = 32
    AUX_HEAT = 64
    TURN_OFF = 128
    TURN_ON = 256

401 = 256 + 128 + 8 + 1
Donc l'appel vers ton climate a maintenant changé. Avant, il y avait les 3 paramètres: target, min, max et maintenant il n'y a que target.

Maybe related to https://github.com/jmcollin78/versatile_thermostat/518
I not sure because your underlying thermostat don't use the TARGET_TEMPERATURE_RANGE but there is a 'huge' bug since this release on the same part of code.
I have done a fix https://github.com/jmcollin78/versatile_thermostat/releases/tag/6.3.4.beta2 that restore the behavior before 6.3.0 which was working well for you.
Ping @maia , @Ra72xx

This is somehow related to the other bugs I've posted too.

About once a day some of the VT units at first go rather silently offline (no sensible entries to be seen in the lovelace card, no more working temperature regulation). Then I change something in the central configuration, which leads to "configuration errors" for most of the VTs. Then I change this central configuration value once again back, and everything is fine again. This happens regardless of the self regulation settings.
The issue described here: Settings/presets can no longer be set reliably and are reset after a few seconds as long as there is no additional self regulation by VT. Once self regulation is enabled, everything works.

I also noticed those 2 behaviors yesterday.

This looks somehow related to the other bugs I've posted too.

About once a day some of the VT units at first go rather silently offline (no sensible entries to be seen in the lovelace card, no more working temperature regulation). Then I change something in the central configuration, which leads to "configuration errors" for most of the VTs. Then I change this central configuration value once again back, and everything is fine again. This happens regardless of the self regulation settings.
The issue described here: Settings/presets can no longer be set reliably and are reset after a few seconds as long as there is no additional self regulation by VT. Once self regulation is enabled, everything works.

I've also noticed those 2 behaviors yesterday.

Have you tried with the last 6.3.4 beta release ? It is fixing a huge bug around this feature: https://github.com/jmcollin78/versatile_thermostat/518

not yet, wasn't aware of it.  I will tomorrow

Hello guys,
I don't know if you have seen this, and I don't have it in mind, but a self-regulated VTherm don't follow its underlying temperature changes: https://github.com/jmcollin78/versatile_thermostat/issues/478
(because target temperature send by VTherm is NOT the desired temperture of the user).

Hello, may I close this issue ? Have you still the issue on your side ?

@jmcollin78 Thanks for asking. I've not seen the issue with recent versions, I will close it.


Deletion of segments not working properly

When Uploading segments to controller using Segment Uri Push, It is putting the segments in path
fake_job_for_testing_time_based_OFFLINE/fake_job_for_testing_time_based_OFFLINE_18597_18597_0
whereas when trying to delete the segments, it is calling exists on path
fake_job_for_testing_time_based/fake_job_for_testing_time_based_OFFLINE_18597_18597_0
which logs
Failed to find local segment file for segment

Fixed in #6445

Fixed in #6445


RATIS-1148. In NettyServerStreamRpc, each remote stream should not wait for its own previous write.

See https://issues.apache.org/jira/browse/RATIS-1148

@szetszwo Hi, we have discussed it previously in pr: https://github.com/apache/incubator-ratis/pull/250.

@runzhiwang , I might have misunderstood your previous comment since Netty uses multiple threads to call channelRead(..).  I thought you were saying that it must require the same thread submitting the calls.  Sorry.
You are right that OrderedStreamAsync will take care the async calls even if there are multithreads calling OrderedStreamAsync.


Using millisecond precision (instead of second) for @timestamp

Working on a project where we need a report every second, the current precision is giving us sometimes two events with the same timestamp. From what I see in the project, we are divising and multiplying by 1000 to have variables in seconds but at the end exporting a Date that has the ms precision.
I think it should be preferable to use directly the ms everywhere but maybe I missed something here?
(note: tried on my project, all reports are good on ELK so I can prepare a PR quickly, but I want to be sure it's not just a personal need. Thoughts?)

Closing old issues.


Vulnerability roundup 85: libjpeg-turbo-2.0.4: 1 advisory [8.1]

search, files

[x] CVE-2020-13790 CVSSv3=8.1 (nixos-unstable)

Scanned versions: nixos-unstable: 22c98819ccd. May contain false positives.
Cc @colemickens
Cc @vcunat

Patch applied in staging and staging-20.03.  GitHub should auto-close this when it hits master.


Dataview Parsing Error after lines that contain "==" or "==="

What happened?
Preconditions

None.

Steps to Reproduce

Write any line or footnote that contains either "`==`" or "`===`" (including backticks).
Switch to Reading mode.
Observe.

Expected result

The note should display properly.

Actual result

There is an unexpected Dataview Parsing Error that appears after each line or footnote that contains "`==`" or "`===`."

Notes

Please see attachments for better understanding.

Environment

Desktop

OS: Windows 11
Obsidian version: Obsidian v1.1.9
Dataview plugin version: 0.5.52

Mobile

OS: Android 11
Obsidian version: 1.4.1
Dataview plugin version: 0.5.52

Attachments
https://user-images.githubusercontent.com/113011161/211002560-af5bd3d6-e959-4baf-9b7e-3120decbc28b.mp4
https://user-images.githubusercontent.com/113011161/211002570-b2b06b11-d485-4ac7-85ec-6f5b3ba0c5c3.mp4

DQL
No response
JS
No response
Dataview Version
0.5.52
Obsidian Version
1.1.9
OS
Windows

You can disable inline queries or change the character as a workaround.

Ah, apologies. I was not aware, and was not familiar with it. 😅 Thanks so much!


Added dynamic title for all components

@spyshiv please take a look.

Fixed lint errors @spyshiv, have a look.

LGTM. Merging this


Expand message detail view to fit bounds of parent control

The message detail panel on the right-hand side scales in size with the application window. However, there is a large margin to the right and bottom of the view which could be used to inspect the message content. Please modify the control to fit the bounds of it's parent control to increase the viewable area.

What version is this? I can't get <IP_ADDRESS> or <IP_ADDRESS> to do this

It was an enhancement request – sorry if it was unclear.
From: Johan Sonesson<EMAIL_ADDRESS>Sent: 03 June 2019 19:28
To: dyster/IPTComShark<EMAIL_ADDRESS>Cc: Peter Fawcett1<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [dyster/IPTComShark] Expand message detail view to fit bounds of parent control (#14)
What version is this? I can't get <IP_ADDRESS> or <IP_ADDRESS> to do this
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdyster%2FIPTComShark%2Fissues%2F14%3Femail_source%3Dnotifications%26email_token%3DAI2APEVA5FNG2L3MLKT6NJLPYVPEXA5CNFSM4HSF6ILKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2I6OY%23issuecomment-498372411&data=02|01|ext.peter.fawcett1%40rail.bombardier.com|14ef6ec151764e76c51308d6e851466e|b0f3630de5de4172b4920cf5cd387a41|0|0|636951833098952421&sdata=BX84ysyLxQcW0002KEN6OVpP4X4jvgBEQIt3dQ0jK%2Bs%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAI2APEXDA3ZEC5QGDDDHCTDPYVPEXANCNFSM4HSF6ILA&data=02|01|ext.peter.fawcett1%40rail.bombardier.com|14ef6ec151764e76c51308d6e851466e|b0f3630de5de4172b4920cf5cd387a41|0|0|636951833098962417&sdata=q5TWdi9Iik%2Byg31oI9qnAGE6hejfj5YoAkEEJ7DkTaE%3D&reserved=0.
Please consider the environment before you print / Merci de penser à l'environnement avant d'imprimer / Bitte denken Sie an die Umwelt bevor Sie drucken
This e-mail message, and any attachments, may contain information that is confidential and/or privileged. They are intended for the exclusive use of the addressee.
Any other person is strictly prohibited from disclosure, distribution or reproduction. No waiver whatsoever is intended by sending this e-mail.
If you receive this e-mail in error please immediately inform the sender by return e-mail and delete this e-mail message along with all the attachments and destroy all copies.


fix: upgrade siwe from 2.1.3 to 2.1.4

Snyk has created this PR to upgrade siwe from 2.1.3 to 2.1.4.
See this package in npm:
See this project in Snyk:
https://app.snyk.io/org/bitcoinfinancier/project/a3da0c80-0889-47d8-b120-76e5bbb3a4eb?utm_source=github&utm_medium=referral&page=upgrade-pr
Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type

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

System Configuration
(Please delete options that are not relevant)
Runtime version(s):
Browser version(s):
Firmware version(s):
SDK version(s):
Diligence Checklist
(Please delete options that are not relevant)

[ ] This change requires a documentation update
[ ] I have included unit tests
[ ] I have updated and/or included new integration tests
[ ] I have updated and/or included new end-to-end tests
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Add the animation on the heart expression count page and tool bar badge

Verified and merged with Master

Verified and merged with the master


Failed to determine the https port for redirect.

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/run
Operating System: macOS 12.6.7
esars-Mac-mini:BlazorApp cesaravendano$ dotnet watch
dotnet watch 🔥 Hot reload enabled. For a list of supported edits, see https://aka.ms/dotnet/hot-reload.
💡 Press "Ctrl + R" to restart.
dotnet watch 🔧 Building...
Determining projects to restore...
All projects are up-to-date for restore.
BlazorApp -> /Users/cesaravendano/BlazorApp/bin/Debug/net8.0/BlazorApp.dll
dotnet watch 🚀 Started
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:5074
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: /Users/cesaravendano/BlazorApp
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
Failed to determine the https port for redirect.
dotnet watch 🛑 Shutdown requested. Press Ctrl+C again to force exit.
info: Microsoft.Hosting.Lifetime[0]

@danroth27 can you help here?

In the Properties/launchSettings.json file, move the "https" setting in the "profiles" property to the top so that it runs before the "http" setting.

The "Failed to determine the https port for redirect" warning can be safely ignored.

In the Properties/launchSettings.json file, move the "https" setting in the "profiles" property to the top so that it runs before the "http" setting.

Thank you, it worked also in my case


Subscribing to JetStream Stream on a 3 node cluster with a single offline node fails 1 in 3 times

Observed behavior
The subscription fails with a timeout about ~33% of the tries. This is unexpected because the cluster should still be functional in the case of a single node failure.
From the amount of failures and the fact that removing the server from the cluster fixes the issue, I assume that NATS Server is routing the request internally to any of the cluster nodes even if the node is reported as offline.
nats subscribe test --all --trace
16:46:01 Subscribing to JetStream Stream holding messages with subject test starting with the first message received
nats: error: context deadline exceeded

Expected behavior
I expect the subscription to work 100% of the tries since the cluster should still be functional in the case of a single node failure.
nats subscribe test --all
16:12:30 Subscribing to JetStream Stream holding messages with subject test starting with the first message received
[#1] Received JetStream message: stream: test seq 1 / subject: test / time: 2024-06-06T16:07:50+02:00
test

Server and client version
nats-server: v2.10.16
nats: v0.1.4
Host environment
No response
Steps to reproduce
Create a 3 node cluster with JetStream enabled
nats-server -js -p 4222 --server_name a --cluster nats://localhost:4248 --cluster_name test-cluster --routes nats://localhost:4249

nats-server -js -p 4223 --server_name b --cluster nats://localhost:4249 --cluster_name test-cluster --routes nats://localhost:4250

nats-server -js -p 4224 --server_name c --cluster nats://localhost:4250 --cluster_name test-cluster --routes nats://localhost:4248

Create a test stream
nats stream add test --replicas 3
? Subjects test
? Storage memory
? Retention Policy Limits
? Discard Policy Old
? Stream Messages Limit -1
? Per Subject Messages Limit -1
? Total Stream Size -1
? Message TTL -1
? Max Message Size -1
? Duplicate tracking time window 2m0s
? Allow message Roll-ups No
? Allow message deletion Yes
? Allow purging subjects or the entire stream Yes
Stream test was created

Information for Stream test created 2024-06-06 16:32:28

              Subjects: test
              Replicas: 3
               Storage: Memory

Options:

             Retention: Limits
       Acknowledgments: true
        Discard Policy: Old
      Duplicate Window: 2m0s
            Direct Get: true
     Allows Msg Delete: true
          Allows Purge: true
        Allows Rollups: false

Limits:

      Maximum Messages: unlimited
   Maximum Per Subject: unlimited
         Maximum Bytes: unlimited
           Maximum Age: unlimited
  Maximum Message Size: unlimited
     Maximum Consumers: unlimited

Cluster Information:

                  Name: test-cluster
                Leader: a
               Replica: b, current, seen 1ms ago
               Replica: c, current, seen 647µs ago

State:

              Messages: 0
                 Bytes: 0 B
        First Sequence: 0
         Last Sequence: 0
      Active Consumers: 0

Publish a test message
nats publish test test
16:33:26 Published 4 bytes to "test"

Create a subscription and observe that it always works
16:34:10 Subscribing to JetStream Stream holding messages with subject test starting with the first message received
[#1] Received JetStream message: stream: test seq 1 / subject: test / time: 2024-06-06T16:33:26+02:00
test

Stop any of the servers, create a subscription and observe a timeout
nats subscribe test --all --trace
16:46:01 Subscribing to JetStream Stream holding messages with subject test starting with the first message received
nats: error: context deadline exceeded

Sample go code would be good also - nats uses its own client library to it might be a bit weird if I have bugs hehe...but I'll look into it anyway.

Currently the meta layer requires all peers to be online to place. That information is updated async, so could be that meta layer did not process the offline state when it allows.
We have had some requests from customers that would allow for peer selection with just quorum semantics..

@derekcollison Not sure if I understand what you mean, but maybe this helps.
Here we can see that after stopping the node c, the state is correctly reported in the RAFT Meta Group Information while still being able to reproduce the issue.
╭──────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                           JetStream Summary                                          │
├────────┬──────────────┬─────────┬───────────┬──────────┬───────┬────────┬──────┬─────────┬───────────┤
│ Server │ Cluster      │ Streams │ Consumers │ Messages │ Bytes │ Memory │ File │ API Req │ API Err   │
├────────┼──────────────┼─────────┼───────────┼──────────┼───────┼────────┼──────┼─────────┼───────────┤
│ a      │ test-cluster │ 1       │ 0         │ 1        │ 24 B  │ 24 B   │ 0 B  │ 0       │ 0         │
│ b*     │ test-cluster │ 1       │ 0         │ 1        │ 24 B  │ 24 B   │ 0 B  │ 8       │ 1 / 12.5% │
├────────┼──────────────┼─────────┼───────────┼──────────┼───────┼────────┼──────┼─────────┼───────────┤
│        │              │ 2       │ 0         │ 2        │ 48 B  │ 48 B   │ 0 B  │ 8       │ 1         │
╰────────┴──────────────┴─────────┴───────────┴──────────┴───────┴────────┴──────┴─────────┴───────────╯

╭───────────────────────────────────────────────────────────────────────╮
│                      RAFT Meta Group Information                      │
├─────────────────┬──────────┬────────┬─────────┬────────┬────────┬─────┤
│ Connection Name │ ID       │ Leader │ Current │ Online │ Active │ Lag │
├─────────────────┼──────────┼────────┼─────────┼────────┼────────┼─────┤
│ a               │ GR5IGR3G │        │ true    │ true   │ 97ms   │ 0   │
│ b               │ 0ZkM0vRC │ yes    │ true    │ true   │ 0s     │ 0   │
│ c               │ k1i3jIye │        │ false   │ false  │ 19.10s │ 1   │
╰─────────────────┴──────────┴────────┴─────────┴────────┴────────┴─────╯

~/Workspace/go/src/github.com/nats-io/nats-server main* ⇣
❯
nats subscribe test --all --trace
19:09:22 Subscribing to JetStream Stream holding messages with subject test starting with the first message received
<<< Reply Subject: $JS.ACK.test.yEK7pGyN.<IP_ADDRESS>7693739474051672.0
[#1] Received JetStream message: stream: test seq 1 / subject: test / time: 2024-06-06T19:08:59+02:00
test

^C⏎

~/Workspace/go/src/github.com/nats-io/nats-server main* ⇣
❯
nats subscribe test --all --trace
19:09:26 Subscribing to JetStream Stream holding messages with subject test starting with the first message received
nats: error: context deadline exceeded

Is the stream a interest or workqueue stream?
Its trying to create a consumer and I would assume its asking for R3 and can't see all peers online.
Not sure if nats cli would accept it here, but try ``--replicas 1`.
If interest or WQ it requires same replica count. We are adding in a viewer that bypasses consumers and uses direct gets. @ripienaar has additional information and timing on that.

Only nats s view will use direct get, for sub its always a subscription.  So I think Derek has nailed the reason for this

Thanks @ripienaar and @derekcollison, it seems like we we're still using the deprecated subscribe API and in the process of trying to reproduce the bug I ended up using the nats sub which also suffers from the same issue. I can confirm that using an  ordered consumer works 100% of the time.


pulsar-admin sink command not working as expected

I try to create a sink connector with the following command.
bin/pulsar-admin sinks create --name sqs-sink-28rc3 --sink-type sqs --inputs persistent://public/default/random-data-topic --sink-config '{"awsCredentialPluginName":"","awsCredentialPluginParam":"{\"accessKey\": \"\",\"secretKey\": \"\"}","awsEndpoint":"https://sqs.cn-north-1.amazonaws.com.cn","awsRegion":"cn-north-1","queueName":"sqs-connector-test"}' --classname org.apache.pulsar.ecosystem.io.sqs.SQSSink

The result of command is Created Successfully!. But when I check in k8s, no relative pod starts. And I find function mesh operator pod is keeping restart with following logs.

After some investigation, it seems like that --auto-ack true is required here.
Maybe we can make an enhancement here to set a default value to auto-ack.

@rockybean cloud you please provide more details about this issue? like version info for both Pulsar and function mesh, thanks.


python backend version for vision AI cancer analysis

David

ImageAnalysisController.java is now translated to python, I also separated the feature calls: image detection and text detection, so you can toggle between them instead of having them commented in/out within the code.
To do: Add python dependencies


[2811] Trainee start date validation

Context
https://trello.com/c/1UQBl0LA/2811-trainee-start-date-can-be-2099
Changes proposed in this pull request
Add validation so that trainee start date cannot be more than 1 year in future (same as course start date validation)
Guidance to review
Test validation on /training-details page

 Trainee start date can be 2099

Just clarifying the intended functionality, I'm fine with the above - so we can still merge.

It's the year bit of the date that can be +1


Settings Sync Fails

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug
Settings Sync.  Sign into Microsoft account, then Sync Settings .
[2022-01-16 18:35:14.966] [settingssync] [info] Using settings sync service https://vscode-sync.trafficmanager.net/
[2022-01-16 18:35:14.966] [settingssync] [info] Auto Sync is disabled.
[2022-01-16 18:35:56.438] [settingssync] [info] Did reset the local sync state.
[2022-01-16 18:35:58.583] [settingssync] [error] LocalInvalidContent (UserDataSyncError) syncResource:settings operationId:unknown: Unable to sync settings as there are errors/warning in settings file.
at l.validateContent (vscode-file://vscode-app/c:/Users/slatteryc/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:76:103937)
at l.applyResult (vscode-file://vscode-app/c:/Users/slatteryc/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:76:100750)
at l.doApply (vscode-file://vscode-app/c:/Users/slatteryc/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:76:46724)
at async l.apply (vscode-file://vscode-app/c:/Users/slatteryc/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:76:40703)
at async s.apply (vscode-file://vscode-app/c:/Users/slatteryc/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:76:155383)
at async R.call (vscode-file://vscode-app/c:/Users/slatteryc/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:76:161410)
All completely repeatable.
Settings.json when opened is just {}
VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.87GB (8.92GB free)

Process Argv
--crash-reporter-id 78f476c8-2e6c-4ba6-abe5-6ca6e0f4fd65

Screen Reader
no

VM
0%

Extensions (26)

Extension
Author (truncated)
Version

npm-intellisense
chr
1.4.0

path-intellisense
chr
2.6.1

vscode-eslint
dba
2.2.2

java-decompiler
dgi
0.0.2

vscode-npm-script
eg2
0.3.23

search-node-modules
jas
1.3.0

csharp
ms-
1.23.17

python
ms-
2021.12.1559732655

vscode-pylance
ms-
2022.1.1

jupyter
ms-
2021.11.1001550889

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.4

powershell
ms-
2021.12.0

prettier-standard-vscode
num
0.9.2

fabric8-analytics
red
0.3.5

java
red
1.2.0

vscode-commons
red
0.0.6

vscode-xml
red
0.18.2

vscodeintellicode
Vis
1.2.15

vscode-java-debug
vsc
0.37.0

vscode-java-dependency
vsc
0.18.9

vscode-java-pack
vsc
0.20.0

vscode-java-test
vsc
0.33.1

vscode-maven
vsc
0.34.2

nodejs-extension-pack
wad
0.1.9

JavaScriptSnippets
xab
1.8.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30384386
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30421291pythonvs932:30410667
vscop804cf:30404767
vscop940:30404999
vsrem710cf:30416617
vsccppwtstudy:30421978

Unable to sync settings as there are errors/warning in settings file.

Please fix your settings file and try again.

Did you even read the comment where I said settings,json consisted just of {} ?

there are no errors in the settings file

Sorry, I missed that comment.
Are you able to turn on settings sync and if so are you seeing this error?


x/pkgsite: case sensitivity messes up docs

What is the URL of the page with the issue?
https://pkg.go.dev/github.com/pagerduty/go-pagerduty
https://pkg.go.dev/github.com/PagerDuty/go-pagerduty
What is your user agent?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:86.0) Gecko/20100101 Firefox/86.0
What did you expect to see?
The same page regardless of casing.
They both link to the same github org, just after casing was changed.
What did you see instead?
Two separate pages.

You might want to read up on the github.com/[Ss]irupsen/logrus saga.

The go.mod file at the latest version uses PageDuty, so the all-lower path is an alternative path. I think we should redirect to the correct path.

I'm familiar with it, but not sure what you want me to do about it @slrz?
I'm not the owner of these packages.

https://pkg.go.dev/github.com/pagerduty/go-pagerduty now redirects to https://pkg.go.dev/github.com/PagerDuty/go-pagerduty.

Hey all, let me know if I should open a new issue for this, but:
Given a module with canonical url github.com/go-sql-driver/mysql (ref: https://github.com/go-sql-driver/mysql/blob/master/go.mod):

https://pkg.go.dev/github.com/Go-SQL-Driver/MySQL with wrong casing works
https://pkg.go.dev/github.com/go-sql-driver/mysql with correct casing redirected to https://pkg.go.dev/github.com/Go-sqL-Driver/MySQL , but now after a few minutes of trying now the page resolves for me.

Just got an answer in slack that the wrong versions work because they're using pre-Modules versions of that package 👍🏻  (still confused about the canonical version not working initially though).


Quality setting is being ignored for formats other than JPEG

A second discovery while learning the API, and evaluating it.

tnail = get_thumbnail(testfilename, '300x300', crop='center', force=True, quality=100)
82K
tnail = get_thumbnail(testfilename, '300x300', crop='center', force=True, quality=10)
5K

tnail = get_thumbnail(testfilename, '300x300', crop='center', force=True, format="PNG", quality=10)
148K

tnail = get_thumbnail(testfilename, '300x300', crop='center', force=True, format="PNG", THUMBNAIL_FORCE_FORMAT="PNG", quality=100)
148K

Pillow does allow the setting of quality for PNG's, which I use in my library.  And I see the change in JPG format, so I'm not sure why this wouldn't be working for alternative graphic formats.

This seems weird, maybe the input to pillow should be different for jpg and png? 🤔


Some minor fixes

Fixes as follows:

fixes spelling
removes unnecessary white spaces and blank lines

Updated: I added some minor fixes.

Tested locally, passing.


[Bug] Launcher crashing when the progress bar is complete

UI or Mechanical Bug?
Is this a user Interface bug or a mechanical/operational bug?
Mechanical.
Describe the bug
A clear and concise description of what the bug is.
When installing creators.tf and the progress bar is full,the launcher crashes without reason.
Was there an error dialogue for this bug? If so please provide a screenshot/its contents here
[Error dialog if applicable]
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
For the game to install.
Launcher Logs
Please upload the logs from your launcher either here, or on a site such as pastebin.
You can find the logs in the "logs" folder in the "Config/Log Folder". Use the button in the Settings menu in launcher to find the folder.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]
Windows 7
Service Pack 1
Additional context
Add any other context about the problem here.

I will try to look into this in the coming days

I have got a new error after updating the launcher,here it is.

I have got a new error after updating the launcher,here it is.


SYN (ERC20) incorrect address

Details
@ledgerhq/cryptoassets
Describe the bug
Incorrect token address is used in data/erc20.js
["ethereum","synapse","SYN",18,"Synapse","304402205c40c4050a517fe73072153eb81ef76129b5c62df12ebaa3ceba6a5b185fc585022047891f151213c41bfd88d7dad808a274f8f2c8b2df7568614d0bfd1c79f82c6d","0x10B123FdDde003243199aaD03522065dC05827A0",true,true],

Expected behavior
Address change of 0x10B123FdDde003243199aaD03522065dC05827A0 to 0x0f2D719407FdBeFF09D87557AbB7232601FD9F29
Additional context
When looking at etherscan, compare the incorrect SYN to the correct SYN. There is a huge difference in both users and transactions.
And the correct SYN address can be verified on "Contract" on coingecko as well as their official docs here
Incorrect token:

Correct token:

hi @BlazeWasHere there is no such thing as correct or incorrect token, what issue do you see in Ledger Live please?

Hi and sorry for the delay in answering on this Github issue.
We now only use Github issues for developers topics (typically on topics that concerns our SDK, libraries,..). For questions, feature requests or Ledger Live issues, please go through our Customer Support to raise this voice and have it more prioritised: https://support.ledger.com/
Thanks


Add Database Resource for v1.0.0

Added

Added the creation_plan block in the subscription resource schema.
Added a new resource type: rediscloud_database.
Added the migration guide to help users with migrating their old Terraform configuration files to v1.0.0.
Multi-modules: Added the "modules" attribute into the creation_plan block and the database resource schema

Removed

Removed the database block from the subscription resource schema.

Re-trigger stuck the license/cla check.


Aggregration plugins not working with custom JVM Test Suites

Expected Behavior

When configuring a custom JVM Test Suite in a multi-project-build and applying the test-report-aggregation and/or jacoco-report-aggregation plugin, the custom suite should be considered for all projects.
Current Behavior

The custom JVM Test Suite is only considered in projects explicitly added to jacocoAggregation (standalone project) respectively in the application project (application/distribution project).
Context

I tried the four samples at https://docs.gradle.org/current/samples/sample_jvm_multi_project_with_code_coverage_standalone.html, https://docs.gradle.org/current/samples/sample_jvm_multi_project_with_code_coverage_distribution.html, https://docs.gradle.org/current/samples/sample_jvm_multi_project_with_test_aggregation_standalone.html and https://docs.gradle.org/current/samples/sample_jvm_multi_project_with_test_aggregation_distribution.html.
Each of those use only a test test suite. For this the behavior is as expected, as when running the check task, testCodeCoverageReport is run and therefore also :utilities:test, :list:test and :application:test are executed.
I tried to expand these samples using a custom integrationTest test suite.
But if I do so, when running the check task, integrationTestCodeCoverageReport is run, but only :application:integrationTest is executed, not utilities:integrationTest and :list:integrationTest.
This is the case for all four mentioned samples, in the reproducer below I demonstrate it for the sample https://docs.gradle.org/current/samples/sample_jvm_multi_project_with_code_coverage_standalone.html.
Steps to Reproduce

https://github.com/LarsKaulen/gradle-aggregation-reproducer
Your Environment

Tested with Gradle 7.5.1 and 7.6-rc-3

Thanks for taking a look at this!
We've made some improvements to this in master/8.0.  Could you take a look with 8.0-20221116231019+0000?
You can update with:
gradle wrapper --gradle-version=8.0-20221116231019+0000
For 7.6+, you'll need to change: implementation project to implementation project().
8.0 will be going to RC soon.

Ahh yes of course, should have tested with the most recent as well.
Looks good to me!


Bump to stable version

API seems reasonably stable enough to commit to a stable ONE-DOT-OH release.

Library needs more generics. Why am I limited to a u32?


PHOENIX-6435 Fix ViewTTLIT test flapper

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
6m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.16 Compile Tests _

+1 :green_heart:
mvninstall
15m 47s
4.16 passed

+1 :green_heart:
compile
1m 17s
4.16 passed

+1 :green_heart:
checkstyle
0m 35s
4.16 passed

+1 :green_heart:
javadoc
0m 58s
4.16 passed

+0 :ok:
spotbugs
4m  1s
phoenix-core in 4.16 has 945 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
8m  4s
the patch passed

+1 :green_heart:
compile
1m 13s
the patch passed

+1 :green_heart:
javac
1m 13s
the patch passed

+1 :green_heart:
checkstyle
0m 33s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 55s
the patch passed

+1 :green_heart:
spotbugs
4m  5s
the patch passed

_ Other Tests _

-1 :x:
unit
207m 57s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
1m 11s
The patch does not generate ASF License warnings.

256m 40s

Reason
Tests

Failed junit tests
phoenix.end2end.index.PartialIndexRebuilderIT

phoenix.monitoring.PhoenixMetricsIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1205/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1205

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux dacc09cf9bde 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.16 / 3bf2e95

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1205/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1205/1/testReport/

Max. process+thread count
4795 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1205/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Using with recursion

Hi can anyone help me making my tree recursively?
the thing is that my array starts with N objects, each is a root node, each one have inner array called children, and each one of those children might have "children"... i do not know the depth level. what would be the best way to do it?

This example shows how to do this: http://jimliu.github.io/angular-ui-tree/tree.html
The key is to create your tree, nodes, node, and use ng-include in your node to specify a template, e.g.:

(Note that you need the single quotes inside the double quotes in ng-include!)
Then you specify a recursive template:

The 'gotcha' here is that you declare ui-tree-nodes and ui-tree-node in 2 places - in your code where you declare the tree (nodes and node are for the top level of the tree), and in the template (for all the recursive children).
You don't have to worry about or code for a maximum tree depth unless you explicitly want to limit it.

Thanks you, i asked the question before looking in the demos, the unlimited nested nodes demo explained it to me.
Now I've got another question, how can i disable dropping nodes between trees? i have a few drag an drops on the same view and i don't want to allow moving nodes between trees.

You should be able to do this by implementing the accept callback in your treeOptions. Inspect the node being dragged, as well as the nodesScope in the accept event (using your debugger). You can determine the node's tree as well as the nodesScope's (drop target) trees. If they are not the same tree, return false and the drop event won't be permitted.

Closing this issue due to inactivity. See #815 for more information.
Please create a new issue is this still occurs with the current version of the component.


Fix fallout from Qiskit metapackage migration

This is an alternative to #386, in an attempt to get the "development version tests" to actually use the development version of Qiskit.

Whew, looks like the development version tests are now working as expected.


Deploy the app in AWS and navigate to the index page.

Use Linux 64-bit as your OS (Amazon Linux preferred).

I wonder if I could get away with deploying it locally to get at that secret.

Guess the answer is no.

Very clever


Incorrect usage text after mis-typed command

Description
I blundered into a command, hoping it would prompt me for the correct flags. But instead it suggested something illegal:
$ az group delete mbdev
az: error: unrecognized arguments: mbdev
usage: az [-h] [--output {json,tsv,table,jsonc}] [--verbose] [--debug]
          [--query JMESPATH]
          {group} ...

This disagrees with the correct command documentation:
$ az group delete
az group delete: error: argument --name/-n is required
usage: az group delete [-h] [--output {json,tsv,table,jsonc}] [--verbose]
                       [--debug] [--query JMESPATH] --name RESOURCE_GROUP_NAME
                       [--yes] [--no-wait]

Basically the --name parameter is required but the first usage message suggests it could be a positional argument, which is wrong.

**Outline the issue here:**
Usage text needs to be updated for this case. I'll try to PR that.

### Environment summary

**Install Method:** How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
The curl | bash script, as recommended.

**CLI Version:** What version of the CLI and modules are installed? (Use `az --version`)
2.0.8

**OS Version:** What OS and version are you using?
macOS sierra.

**Shell Type:** What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
`bash` 3.2.57

This would involve some core changes to the CLI command parsing logic. The reason is because the CLI assumes everything you submitted is part of the command name since the CLI doesn't support positional parameters.  The current logic essentially splits the command line into the "command part" which is everything to the left of the first - character, and the "arguments part", which is everything to the right of and including the first - character.

//CC: @chewong, a bit different from #3994, though related as both in regarding to a better error.

I believe this is now fixed. In version 2.0.32, I see the below. In 2.0.8 it was the error that was first reported.


imv doesn't swallowing

i have the module swallow active, but when i launch imv don't work. i tested it with mpv, timeshift and work fine

run xprop and click on the imv window, does it report PID? if not can you check if #140 fixes it?

does't report PID

welp, then that is a problem with imv and you should open an issue to have them add the PID atom, on the meantime you can use this LD_PRELOAD library https://github.com/deepfire/ld-preload-xcreatewindow-net-wm-pid that forces missbehaving windows to have a PID prop, after you compile that library you can make a wrapper script for imv like this:
#!/bin/sh
LD_PRELOAD=/path/to/ld-preload-xcreatewindow.so /full/path/to/imv $@

perhaps call it imv and have it inside ~/.local/bin/

The window swallowing module depends on the PID xproperty. We won't be able to just add support for windows that don't set that property. I'm unaware of any possibility to map window IDs to process IDs otherwise. If there is one, feel free to share it here.


ActionBar: Add stories for couple of edge cases

Closes #https://github.com/github/primer/issues/3133 and #https://github.com/github/primer/issues/3134

Changelog
Adding two stories for issues that were a problem with the webcomponent in the rails version of this component.

Thanks for the review! I should not have made the assumption that draft components don't need changesets.
But we can make larger refactors and API change in this component without needing a major right? Just a patch changeset to document the change to the component should be enough?

I should not have made the assumption that draft components don't need changesets.

I see! If it's not used anywhere yet, then I'd say it's nice to have a changeset but optional for now.

But we can make larger refactors and API change in this component without needing a major right? Just a patch changeset to document the change to the component should be enough?

patch/minor sounds good in this case :)


Mm4.2

@tejaycar can you look at the merge conflicts on this one?

Yes, I'll look Monday.  I think they're phantoms..
On Sep 22, 2017 12:40 PM, "James Hunt"<EMAIL_ADDRESS>wrote:

@tejaycar https://github.com/tejaycar can you look at the merge
conflicts on this one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry-community/mattermost-boshrelease/pull/9#issuecomment-331528494,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADqwzDxGS8IqVcvbumU7U_MGLnV8rVkDks5sk_8QgaJpZM4Pg_3Q
.

@tejaycar @jhunt helping out, I fixed the branch + merged. The release notes have the 4.1 + 4.2 notes merged together. @tejaycar can you confirm the release notes look good?

I think we just need the 4.2 notes, since the prior release had the 4.1
notes.  But either way should be fine.
On Sep 23, 2017 4:51 AM, "Dr Nic Williams"<EMAIL_ADDRESS>wrote:

@tejaycar https://github.com/tejaycar @jhunt https://github.com/jhunt
helping out, I fixed the branch + merged. The release notes have the 4.1 +
4.2 notes merged together. @tejaycar https://github.com/tejaycar can
you confirm the release notes look good?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry-community/mattermost-boshrelease/pull/9#issuecomment-331626275,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADqwzMTxMF7ypHrYm9H796sAPbDe33b-ks5slOKZgaJpZM4Pg_3Q
.

I don't think we've cut a release since you started updating the job properties https://github.com/cloudfoundry-community/mattermost-boshrelease/releases
I'll cut a release now

Ah, ok.  That's perfect.
On Sep 23, 2017 1:50 PM, "Dr Nic Williams"<EMAIL_ADDRESS>wrote:

I don't think we've cut a release since you started updating the job
properties https://github.com/cloudfoundry-community/
mattermost-boshrelease/releases
I'll cut a release now
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry-community/mattermost-boshrelease/pull/9#issuecomment-331665940,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADqwzKzeYjKPTOqWiE8BxkQgK5s-4a2jks5slWESgaJpZM4Pg_3Q
.


Default content styling

[ ] Adjust default content styles (default colors, link behavior, buttons, font size, ...) in styles.css
[ ] Add fallback font
[x] Add Favicon
[ ] Adjust media breaks, as/if required

Favicon is added as part of https://github.com/hlxsites/fonterra-fernleaf/pull/8


Addition of multiplierFESpace

This PR introduces a first development of MultiplierFESpace for the solution of constrained minimization problems. The idea is to be able to construct a MultiFESpace combining the usual finite element discretization on the one hand and Lagrange multipliers on the other. Here the Lagrange multipliers are additional unknowns and the MultiFESpace combined with MultiplierFESpace enables to assemble a global system which yields the solution of the constrained minimization problem as well as the associated Lagrange multipliers. The development is built on the constrained Poisson example.

Thanks for the review. I added a few unit tests for MultiplierFESpace. Concerning the "global" test, did you mean a test at the end of the corresponding example (with the error computation)?

Thanks for the review. I added a few unit tests for MultiplierFESpace. Concerning the "global" test, did you mean a test at the end of the corresponding example (with the error computation)?

I meant encapsulating your whole example (or a simplified version) into a @testset with some kind of test at the end (on the error for instance). Like it is done here for the Poisson DG : https://github.com/bcube-project/Bcube.jl/blob/d81437d097f86e5baa993c4eec45afca880d04fb/test/dof/test_assembler.jl#L213


DaySelectedBackgroundColor - Circle not Rendering

Describe the bug
Hi there!
Thanks for all the work you put into XCalendar!
I think I might be experiencing a bug in setting the color value for the dot that indicates the currently selected date.
Looking at the Sample Code it looks to me like it should be set on the cx:DayView - where you assign it to a Color value.
I've done that like so:
<xc:DayView
    ...
    SelectedBackgroundColor="{StaticResource DaySelectedBackgroundColor}"
    ...
    >
</xc:DayView>

And then set the resource in App.xaml like
<Application.Resources>
    ...
    <Color x:Key="DaySelectedBackgroundColor">Green</Color>
    ...
</Application.Resources>

However, the selected indicator still does not populate. Screenshot:

Are there other properties that I need to set to enable this feature?
Expected behavior
I would think there should be a green dot when selecting on a day.
Steps to reproduce OR link to code
I've uploaded my current code to this repo / branch
Xamarin Forms or .NET MAUI (If related to UI)
.NET MAUI
Additional context (Optional)
Device Info (Optional)
Device Model: samsung galaxy s20 FE
Android Version: 12, One UI version 4.1
IOS Version:
Windows Version:

When you say "Indicators", do you mean like on of the two red dots in your image? If so, there is no built in functionality for indicators. You will need to implement the logic yourself.
If you mean an actual day, the DayView has some properties you need to set in order to get the state-based properties working in different states. The Displaying Dates page lists them in the 'CalendarView' section.

When you say "Indicators", do you mean like on of the two red dots in your image? If so, there is no built in functionality for indicators. You will need to implement the logic yourself.
If you mean an actual day, the DayView has some properties you need to set in order to get the state-based properties working in different states. The Displaying Dates page lists them in the 'CalendarView' section. Usually you would just bind them to the properties of the same name from the binding context.

Also, just to confirm, is it the 'master' branch you wanted to link to for the reproduction of the issue?

Hey @ME-MarvinE  - thanks for looking into this!
I'm pretty sure I linked to the exact branch / file in the ticket - but here is the exact full link: https://github.com/johnyenter-briars/cal/blob/dev/bring_in_xcalendar/CAL/Views/CalendarPage.xaml
The UI i'm referring to is the little dot that represents which dates are currently selected:

@johnyenter-briars I was opening the link through the Mobile app which kept leading me to the 'master' branch. The links work fine on PC.
Eventually I tried using a Calendar with CalendarDay instead of EventDay and it worked.
The EventDay and Event classes in the sample app (along with other classes) use PropertyChanged.Fody to inject usage of the INotifyPropertyChanged interface into the shorthand setter ({ get; set; }) by adding the     AddINotifyPropertyChangedInterface attribute to the 'BaseObservable' classes.
This package nor the attribute is present in the project and there was no replacement for its functionality. You will need to either implement the INotifyPropertyChagedInterface' manually, or install the PropertyChanged.Fodynuget package and re-add theAddINotifyPropertyChangedInterface` attribute wherever it was removed.
I implemented the interface manually into the EventDay class and everything seemed to work correctly.

@johnyenter-briars Is your issue resolved?

@ME-MarvinE Sorry, took me a while to find the time to implement your fix. It worked as expected.
Thank you so much! Closing the issue now.


Question about inference use Llama-2-7b-longlora-8k-ft output nothing

I use code from repo and script
python inference.py  \         --base_model /data/juicefs_sharing_data/11164126/py-proj/model/Llama-2-7b-longlora-8k-ft/ft_model \         --question 'Now the material ends.Please tell me that what high-level idea the author want to indicate in this book' \         --context_size 8192 \         --max_gen_len 512 \         --flash_attn True \         --material ./test.txt
`    material = read_txt_file(args.material)
prompt_no_input = PROMPT_DICT["prompt_no_input_llama2"]
prompt = prompt_no_input.format_map({"instruction": material + "\n%s"%args.question})
output = respond(prompt=prompt)
print('this is output: ', output)

`
this is my script and code，whatever I input, only get nothing, always output nothing or many '\n', what's wrong with it?

this is terminal output
[INST] <>
Below is some content in the book. Memorize the content and answer my question after the book
<>
Title: "A Patriot's Resolve"
In a small town nestled among rolling hills, lived a man named James. He was an ordinary man, a schoolteacher by profession, with a quiet demeanor and a passion for his country that burned deep within his heart.
James grew up hearing stories of bravery and sacrifice from his grandfather, who had fought in a war to defend their homeland. Those stories had left an indelible mark on him, igniting a sense of patriotism that guided his every action.
One sunny morning, as James walked to his school, he noticed a group of children playing by the flagpole. The national flag fluttered proudly in the breeze. It was a symbol of unity, freedom, and the sacrifices made by countless patriots before him.
As James entered his classroom, he found his students eager to learn about their nation's history and the values it stood for. He taught them about the struggles and triumphs that had shaped their country, emphasizing the importance of preserving its heritage.
Outside of the classroom, James volunteered at a local veterans' association, where he listened to the stories of those who had served in the military. Their experiences, both joyful and heartbreaking, strengthened his resolve to uphold the principles his country was founded upon.
One day, news arrived of a natural disaster that had struck a neighboring town. Houses were destroyed, and families were left homeless. James organized a charity drive among his students and fellow townspeople. The outpouring of support and solidarity was overwhelming. Together, they provided aid to the affected families, embodying the spirit of patriotism and community.
Years passed, and James continued to teach, spreading the ideals of love for one's country and the importance of civic responsibility. He watched his students grow into responsible citizens who cherished their nation's values.
As James reached the twilight of his life, he reflected on his journey as a patriot. He knew that true patriotism was not just about waving the flag or singing the national anthem, but about actively contributing to the well-being of one's country and its people.
In the end, James knew that his legacy would live on in the hearts and minds of those he had inspired. He had shown them that being a patriot meant loving one's country deeply, standing up for its principles, and working together to make it a better place for all.
And so, in that small town among the rolling hills, the spirit of patriotism continued to thrive, passed down from one generation to the next, a beacon of hope and unity in a world that always needed a little more love for one's homeland.
Now the material ends.Please tell me that what high-level idea the author want to indicate in this book [/INST]

this is output:

Hi,
I think the reason is that Llama-2-7b-longlora-8k-ft has not been supervised fine-tuned or instruction tuning. Would you please try our LongAlpaca models, for example, LongAlpaca-7B-16k.

I will close this issue as it has been inactive for several days. Please feel free to reopen it if there are any others to discuss.

I will close this issue as it has been inactive for several days. Please feel free to reopen it if there are any others to discuss.

I have a question about Llama-2-7b-longlora-8k. I once merged this lora weights with Llama2-7b-hf model. Then my input is about 3k-length tokens, and my purpose is to write meeting summary. However, the output is empty. Should I use LongAlpaca-7B to test again?


Flush icache on android aarch64 and unbreak Android compilation

This is a backport of https://github.com/bytecodealliance/wasmtime/pull/5331 in the 3.0.0 branch, and it unblocks compiling on Android and FreeBSD.

Thanks for including https://github.com/bytecodealliance/wasmtime/pull/5323 too!

Would you also be up for adding some release notes here and sending that to main as well?

Ah I'll take care of that in https://github.com/bytecodealliance/wasmtime/pull/5363

I'll note though that Android/FreeBSD aren't officially supported platforms or don't have CI in any way. This sort of breakage is bound to continue happening and it would be best I think if we didn't have to do point releases after-the-fact. If @bnjbvr or others would be willing to at least add cargo check for these platforms I think that would be the best course of action.


Canal use nodes internal-ip for overlay network?

What kind of request is this (question/bug/enhancement/feature request):
Question
Steps to reproduce (least amount of steps as possible):

Install Rancher 2.2.8 on VM/bare metall
Create custom cluster with Canal as network provider

Canal now uses the nodes default route interface to create the overlay network.
Question:
Within a heterogeneous cluster where different machines with different interfaces are used:

old naming schema eg. eth0
new schema eg. ens6
nodes connected via openvpn eg. tun1

the default cluster wide config of the interface name will not really work.
Within kubernetes every workernodes gets an external (1) and internal ip (2):

Is there any way to tell Canal to just always use the interface/ip specified in the "internal ip" (2) address? Because this way it would not matter what the name if the nodes interface is.
the reason I am asking is, because I don't want my inter-cluster communication to happen on a public interface, because it may has security implications.

I have hit the same problem, I am trying to add  a node from another network that is talking on a different network. The pods can not communicate on the overlay network because flannel is bound to the external interface.

Note: in the below examples I have redacted the actual IP addresses

When I run rancher agent, I specify the desired --address <IP_ADDRESS> and --internal-address <IP_ADDRESS> options on the cli, AND for extra insurance I add the same values for -e CATTLE_ADDRESS=<IP_ADDRESS> and -e CATTLE_INTERNAL_ADDRESS=<IP_ADDRESS> as I need to use this local interface to communicate to other nodes via this secondary interface address (not default interface)
I then check the first agent container that gets launched and can confirm that all of the values get assigned as expected:
CATTLE_ADDRESS=<IP_ADDRESS> CATTLE_INTERNAL_ADDRESS=<IP_ADDRESS>
.
customConfig=map[address:<IP_ADDRESS> internalAddress:<IP_ADDRESS> roles:[etcd worker controlplane] label:map[]]
.

However, because rancher spins up an additional two agent images (total of 3 now) the third agent image it spins up doesn't honor the provided variables
Third agent container during set-up
CATTLE_ADDRESS=<IP_ADDRESS> CATTLE_INTERNAL_ADDRESS=
.
Option customConfig=map[roles:[] label:map[] address:<IP_ADDRESS> internalAddress:]"
.

The address seen in the above example is the default network/gateway interface on the node. (But not the interface I wish to use for the rancher network - as the default interface is set for other purposes)
When the agent successfully registers and finishes setting up, the rancher node GUI shows two IP addresses - just like the auther of the post.
I did some digging. When issuing the below kubectl command
 $ kubectl --kubeconfig ~/.kube/config describe node nodeNameX

... the Internal IP seems to be set to what rancher auto inspects from the server, as opposed to the provided and desired value
$ kubectl --kubeconfig ~/.kube/config describe node nodeNameX | grep -i internal

rke.cattle.io/internal-ip: <IP_ADDRESS>
  InternalIP:  <IP_ADDRESS>

It is my understanding that the Internal IP is set during registering the node to kubernetes. Despite the cattle tags clearly making into the annotations of the node configuration, is it possible to hard set the Internal IP to the provided and desired environment variables of the first agent container?
Is the fix to ensure that the environment variables propagate towards subsequent rancher agent spin ups?

@martin-kieliszek thank you for sharing you insights about how the internal IP is not correctly communicated to K8s. How, however is this related to my original post?
I think your findings are worth a seperate issue, but do not really releate to my issue.

@GameScripting thanks for your swift response
Perhaps it is worth me filing a separate issue, agreed.
RE: my initial thought process of how my comment could have been relevant to your issue:
We have a desire to control inter-cluster communication over Canal on a desired Internal IP address.
However, in hindsight, I agree, my comment focused on another topic. The topic of failing to overwrite the Internal IP AWAY from automatically being set to the node's default public interface IP.

Update: We did not end up creating the patch. Instead we are now using k3s to deploy small clusters at the edge, connecting them to our central rancher server for managment.

This would've been a really cool feature thought. As it would simplify certain deployments and firewall management


Fix and some test coverage for ResizablePanelGroup

Fixes issue where panels were not resized smaller than their content, even if the total space available cannot accommodate it. We want it to be reduced so the layout is not broken and the developer can style an element with overflow-y: auto to scroll in that case.

Before:
https://github.com/cardstack/boxel/assets/353/b2ebca4a-944b-4aff-8049-312a4a204ea8
After:
https://github.com/cardstack/boxel/assets/353/4dae429c-ce76-4cf5-bf50-0e17a29dc34b

The test failure is unrelated. I'm perplexed by what percy is showing. It seems to have extra margin/padding (prior to this PR) and I can't reproduce the shorter left column locally in either Chrome or Safari.

Not sure if this is worth handling here
https://github.com/cardstack/boxel/assets/8165111/6e9fe505-aa94-4f82-880f-d9544e3c362b


Coefficient of cubic weight is wrong

The IATA coefficient is set with value 6.0 and should be 6000.
The calculus of cubic weight is here
correios reference

Sorry, I manually calculate the posting weight and the result is correct


Clarity For: External DNS records required for Skype for Business Online

Can we verify what DNS records are actually needed for Microsoft Teams (and why)? There's also a note in there that says the records are needed especially in hybrid scenario...I think this is false because in hybrid we typically leave DNS pointed to the on-prem SfB deployment until all users have been migrated.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dce215c7-f61f-44c5-43c1-2fa1f2a39220
Version Independent ID: d65a9513-432a-d0fe-1431-da5ad2e631eb
Content: External Domain Name System records for Office 365 - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/external-domain-name-system-records.md
Service: o365-administration
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@kelleyvice-msft  Please add your comment and help us in resolving this issue. Thanks.

I'm not sure what the activity in this thread since Feb 24 means, but it looks like there hasn't been any progress.
The OP's point stands to this day. The doc saying this...
"These DNS records also apply to Teams, especially in a hybrid Teams and Skype for Business scenario, where certain federation issues could arise."
...is misleading and vague. The 4 specific ones in that section of the doc should be explicitly defined in relation to:

Teams (only): I think 0 of 4 are needed. This is the most common mode, so it should be crystal clear.
Teams (hybrid): Unclear which of the 4, if any (probably: none)
Teams (federation with SfB): Unclear which of the 4, if any (possibly: the sipfed one)

Back from leave of absence. I'll look into this with the PG.

Searching for SME to provide answers for this.

I've identified contacts and requested support to resolve these questions. I'll update the issue as soon as I have any new information.

@kelleyvice-msft please update. Thanks


KAFKA-4205; KafkaApis: fix NPE caused by conversion to array

NPE was caused by log.logSegments.toArray resulting in array containing null values. The exact reason still remains somewhat a mystery to me, but it seems that the culprit is JavaConverters in combination with concurrent data structure access.
Here's a simple code example to prove that:
import java.util.concurrent.ConcurrentSkipListMap
// Same as `JavaConversions`, but allows explicit conversions via `asScala`/`asJava` methods.
import scala.collection.JavaConverters._

case object Value
val m = new ConcurrentSkipListMap[Int, Value.type]
new Thread { override def run() = { while (true) m.put(9000, Value) } }.start()
new Thread { override def run() = { while (true) m.remove(9000) } }.start()
new Thread { override def run() = { while (true) { println(m.values.asScala.toArray.headOption) } } }.start()

Running the example will occasionally print Some(null) indicating that there's something shady going on during toArray conversion.
nulls magically disappear by making the following change:
- println(m.values.asScala.toArray.headOption)
+ println(m.values.asScala.toSeq.headOption)

The reason is simple: toArray first calls size and then iterates through the collection. This is not safe for a collection that is accessed concurrently. Maybe worth checking if there are any other cases like that?

Ah, makes sense.
Indeed there seems to be a similar problem at Log.

May be here is the same problem:
https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/log/Log.scala#L606

LGTM, except the comment from @ijuma on unit tests and zipWithIndex.

Rebased, reverted usage of zipWithIndex to indices and added a test case.

Merged to trunk and cherry-picked to 0.10.1.

Thanks for your contribution @ataraxer!
A note for the future (since this was already merged): the PR description becomes the commit message so it's good to update it if more information comes to light after the PR is posted. For example, if someone reads the commit message for this fix, it sounds like we merged something without understanding the underlying problem (which is not the case). Committers can also fix such things by using git commit --amend  before pushing.


Unable to locate Micromamba venv

Getting this on local dev with a m1 mac:
python3 pipelines/training.py --environment=pypi run
Metaflow 2.12.27 executing Training for user:kody
Project: penguins, Branch: user.kody
Validating your flow...
    The graph looks good!
Running pylint...
    Pylint is happy!
2024-11-06 11:26:14.577 Bootstrapping virtual environment(s) ...
    Pip ran into an error while setting up environment:
    Unable to locate a Micromamba managed virtual environment
    for id 4abd21d169f9804

Tried downgrading metaflow to .27 and still getting the same thing

@svpino I have the same issue when running on mac. Doesn't occur when I run on Ubuntu.

Missing curl was the reason on my clean install.
sudo apt install curl


aedes with websocket?

Perhaps a silly question, but how does one create a websocket server that
can accept aedes instance.handle() ?
There seems to be no ws analogue for
var server = require('net').createServer(aedes.handle)
Which of the numerous websocket nodejs modules is the optimal for aedes?
And thank you for great work on Mosca and now Aedes !

Ok, this seems to work:
aedes = require('aedes')()
ws=require 'websocket-stream'
server = ws.createServer({port: 8001}, aedes.handle)

That's exactly what I use! Maybe it might make sense to contribute an example with it, would you like to send a PR?

Ok, here is a minimal working mqtt+ws broker (following your mqtt-example) :
var aedes, port, server, ws, ws_port, ws_server;
aedes = require('aedes')();
ws = require('websocket-stream');
port = 1883;
ws_port = 8080;
server = require('net').createServer(aedes.handle);
ws_server = ws.createServer({

port: ws_port*
}, aedes.handle);

server.listen(port, function() {

return console.log('server listening on port', port);*
});

/ari
2016-09-25 20:11 GMT+03:00 Matteo Collina<EMAIL_ADDRESS>
That's exactly what I use! Maybe it might make sense to contribute an
example with it, would you like to send a PR?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mcollina/aedes/issues/68#issuecomment-249433533, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFphvA_LGvW3xkuZCP0_lspLieKEVObSks5qtqtMgaJpZM4KF8To
.

--
/Ari

I've added it to master.


Loading Governance dashboard fails with error about OLE DB or ODBC Error - HRESULT 0x80040E4E

I am following all the instructions to load the Governance Dashboard as per the Deployment Guide. It fails in two different computers in the same step. One computer is running Windows 11 and latest version of POWERBI Desktop, the other is running Windows 10 with latest version of POWERBI Desktop.
I need to demo this to several partners attending Landing Zones & CAF related training in a few weeks.
Any clues?
Thank you

Closing per request from @Arturo-Quiroga-MSFT


STEM investment

Is the equipment appropriate at the lower levels of school i.e. do primary students need microscopes? Do they need the same level of investment?
Is this feasable?
Is it necessary?
STEM can also be taught without a lot of investment... (in the no STEM case)

Covered in the establishment costs now


New Validation: Check for backend binaries if backend or alerting declared

Adds validation for backend, alerting and executable attributes in plugin.json
Closes https://github.com/grafana/plugin-validator/issues/174
Cases
Alerting=true and backend=false: error
backend=true and executable="": error
backend=false and executable=".+": error
backend=true, excutable=".+", binaries not found: error
backend=true, executable=".+", binaries found: correct

LGTM
Not sure if there's anything to consider for bundled plugins with a backend etc

yes. this setup is not considering bundled/nested plugins at all. I'll open a follow up PR to improve that case. I suspect it'll require more changes in the validator.


catalog-backend: fix azure ingestion default branch browser url

Hey, I just made a Pull Request!
fix azure ingestion default branch browser url
the default branch browser url does not contain branch name and is throwing error due to undefined branch being passed to API
e.g. https://dev.azure.com/{organization}/{project}/_git/{reponame}?path={path}
the full url with branch name works fine
e.g. https://dev.azure.com/{organization}/{project}/_git/reponame?path={path}&version=GBmaster
changed from source provider api to git api as source provider api does not support optional branch name
git api returns the default branch contents when no branch name is specified
this fixes #2254
:heavy_check_mark: Checklist

[x] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[x] Prettier run on changed files
[x] Tests added for new functionality
[ ] Regression tests added for bug fixes

Cool! Am I right in understanding that this works for both git and tfs repos?

Merging - we can always tweak more later


Java error

i keep geting a java error that is
Uncaught exception:
TypeError" Cannot read properly 'isFocused' of null
at WebContents.
(C:\Users\Ower\AppData\Roaming\discord\0.0.300\modules\discord_desktop_core\co...:31)
at emitOne (events.js:101:20)
at WebContents.emit (events.js:188:7)
i tried bandage and reinstaling discord, updating java and still nothing.

try running the installer on the desktop as admin

Still nothing. I rebooted my pc and discord loaded but the theme was off (by this I mean it was not loading the background photo). So I reran the bandage app on my desktop and now I am still getting the same error.

help! i have the same error! i runned discord as a admin but it the discord launched for 2 seocnds and then it showed me the error.

so i had this problem too and i fixed it with opening task manager and turning of a process called "igfxm module".

i'm having the same problem

@thesnorki It is either called "igfxm module" or "In Game Manager" in Task Manager, that fixed it for me too. Then after hitting OK discord restarted itself and booted fine.

there's no process called igfxm module in Task Manager but I still got that error. help?

nevermind. in case no igfxm module appears in Task Manager, just close any or all of the Discord processes. worked for me.

I don't know if this'll help, but I was having the same issue just a few moments ago and tried these steps, and I seem to be up and running:

Delete the 'discord' folder in your '%appdata%' folder
Delete the 'Discord' folder in your '%localappdata%' folder
Re-download the Discord installer and run it

I deleted the folders and then re-installed Discord, and I did take notice it installed some updates before crashing while trying to authenticate on my machine; however, rerunning it caused it to get another update, and now it seems to be fine for me.

Me too:
Uncaught exception: TypeError" Cannot read properly 'isFocused' of null at WebContents.  (C:\Users\Ower\AppData\Roaming\discord\0.0.300\modules\discord_desktop_core\co...:31) at emitOne (events.js:96:13) at WebContents.emit (events.js:188:7)
After restart the PC the error appears again.

this error literally caused my computer to crash and not be able to start up properly since :/


[JP] Update translation in 'basics/basics' lesson

#49

Thank you @hinamiyagk!  @3100 do you have time to take a look at this? 👍

Looks good to me :+1:

Thank you @hinamiyagk and @3100 😀


Register state update

Description
Fixes # (Updating the registration state to include Email, password, and displayName instead of userName and password.)
Type of change
Please delete options that are not relevant.

[x ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x ] This change requires a documentation update

Change Status

[ ] Complete, but not tested (no new tests yet needed)

How Has This Been Tested?
n/a - to be tested after next phase
Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[n/a ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

Changes are very straight forward. Is Jay aware of these changes? Will have problems running the app if the backend doesnt match these changes.

Changes are very straight forward. Is Jay aware of these changes? Will have problems running the app if the backend doesnt match these changes.

These changes are the ones discussed and outlined in our release canvas.


Implement bulk queries

The GSB API provides an interface for bulk URL queries using POST.
My only issue right now is if I really want to do a Vec of Vec to mirror the lookup() interface for efficiency reasons. It would mirror the gsb API itself, so that's a plus.

Done.


Update logo

Closes: #53

I'd replace the IO logo with a Lagoon one?

That's the one I used? https://github.com/uselagoon/lagoon-charts/pull/60/files#diff-cc35d4b8e796c869289176c383aa3da3

ah yes - no idea why I was getting the old IO one...
happy with either - I've been using the one with the text more often, unless the scale is too small (favicon etc)

Well I was thinking that the main place this will be seen is on helm hub and they use a square frame for the logo, so went with the square textless one. We can always replace it later if you like :slightly_smiling_face:


The navigation bar shrinks after using navigate in lovelace.

Latest version 1.6 installed, but was an issue with older versions, too.
I'm using the navigate function to other lovelace pages on some chip or mushroom cards and whenever I go back the navigation bar on the bottoms shrinks horizontally as shown in the video.
https://github.com/Nerwyn/material-rounded-theme/assets/98790344/a615f87c-46da-4ca4-985d-3bb8c94b574f
The problem shows on Chrome on Mac, Home Assistant App on Mac, Chrome on Android and Home Assistant app on Android.

Are you on the latest version of card-mod? Card-mod styles not fully applying to the toolbar was an issue before version 3.4.0 but I thought it was fixed.

Yes, 3.4.3 is installed over here.
Should I try downgrading to 3.4.0?
The bar looks correct initially but shrinks whenever navigate is used...

That's weird, I can't recreate it on any of my devices. Downgrading shouldn't be necessary since I'm also on 3.4.3.
I do see the toolbar tabs briefly left aligned before card-mod fully applies. Maybe card-mod isn't reapplying on page load for some reason? Do you have card-mod installed as a resource?

I just set card-mod as a ressource now but I don't see any difference in behaviour.
Checked ressources to make sure.

Found a workaround for Chroma and Home Assistant apps.
If I don't use the navigation to go back at the bottom (as shown in video) but rather the browser ui or phone gestures to navigate, the navigation bar will be fine.

I started intermittently running into this issue too. I think it's because card-mod is making so many style changes that they're not all applying consistently. I still have some ideas for how I might be able to mitigate this with refactors but no promises that it'll actually work.

Bad news - the idea didn't work. I'm not sure there's a fix to this unless card-mod's performance is improved.

Thinking of making these subviews regular again or putting on another dashboard instead, which also fixes the issue.

Can you try v2 beta 4 and see if it makes a difference?

Tried the latest beta, refreshed but it still shrinks after using subviews sadly

The big problem is that the entire ha-tabs/paper-tabs element gets unloaded in subviews, which causes the card-mod CSS to unload. I don't think there's a way around this without a fix to card-mod itself.

Is this issue linked to this (Bottom bar not loaded properly) ? Reloading fix the problem but it keeps appearing uncentered randomly.

Yup. Is that after viewing a sub view? It's a card mod issue where styles within a shadow-root are lost when an element unloads. I don't think there's anything I can do about it

@deezid @Jejebond can y'all try the latest v2 beta (10 at time of writing). I did some out of the box thinking (the box being the ha-tabs, paper-tabs, and paper-tab shadow-roots that weren't loading their styles properly 😁) and managed to create very similar styles for the view tabs without the shadow-roots. They seem to be applying correctly after leaving a subview and I imagine shouldn't not load anymore due to shadow-root style slowness.

@Nerwyn I'll try this out during 24h just to make sure and give you feeback tomorrow. For now on, it seems to be working.

Note - Subviews must be placed as the last view tabs on the toolbar for the view tab size calculation to be correct, otherwise they won't be skipped when counting view tabs.

Latest version indeed seems to have it fixed.
Also way less jumpiness when loading the dashboard the very first time 😀

It only happen once to me but it's much more stable ! Is it normal that the menu and 3 dot buttons are up now ? (i'm fin with this look, much better).

The fact that it happened once is concerning but I'm hoping that was a cache issue 🙃.
The menu buttons at the top is the new normal!  They've been moved to better follow the material design 3 guidelines and give more room for view tabs. These buttons are part of the top app bar and should be separate from the navigation bar. I didn't want to take even more room away from the view window so I made them overlays that disappear on scroll. Users can opt to create their own top app bar using something like markdown card button-card if they don't want them to overlay, kind of like I do in the updated screenshots.

Released v2.0.0.


Killing a deemon Can't quit in the VS Code build

Similar to #6 , I comment on that question, now I migrate these here.

I have encountered a problem that deemon cannot kill a task normally. I try to kill for a long time, but it can't end.
Its performance is that I can't recompile the web extensions and I can't kill it. The log it prints out is the last error log, which should no longer exist now, but it is still output and seems to block the entire task.
hi @joaomoreno, I would like to ask if I have encountered any similar problems ? Or if it has anything to do with this problem?
This problem appears in mac OS 12.2.1 in intel &<EMAIL_ADDRESS>

How are you killing it? Did you try Ctrl D?

How are you killing it? Did you try Ctrl D?

Ctrl D work well, It can exit at the end

Just now I found out that it may be the problem of the node process. When I can't kill the tasks started by deemon (the command line is hold on), there are many node processes in the activity monitor. When I kill them all manually, there is no problem with using deemon to start and close the commands.
One of the more embarrassing problems is that since I manually killed the task in the activity monitor, I can't reproduce it.

I'm not sure you actually have a problem or are just using deemon incorrectly. Deemon will not kill the build task if you quit using Ctrl C. That's the whole point, it's the reason for using deemon. Pressing Ctrl C will simply detatch from whatever process it spawned, so you can reconnect to it later using the same command line. If you intend to fully kill the build, then Ctrl D should be used.


Apply StyleCop to project

Apply StyleCop to project
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Going to close this one, it will be completely different when we actually make this change.