Entity standby power still counting event when calculation_enabled_condition is false

System Health details
System Information

version
core-2024.8.3

installation_type
Home Assistant Container

dev
false

hassio
false

docker
true

user
root

virtualenv
false

python_version
3.12.4

os_name
Linux

os_version
5.10.60-qnap

arch
x86_64

timezone
Europe/Zurich

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

HACS Data
ok

GitHub API Calls Remaining
5000

Installed Version
2.0.0

Stage
running

Available Repositories
1399

Downloaded Repositories
28

Dashboards

dashboards
3

resources
17

views
13

mode
storage

Recorder

oldest_recorder_run
July 29, 2024 at 00:25

current_recorder_run
August 27, 2024 at 21:30

estimated_db_size
3489.00 MiB

database_engine
postgresql

database_version
15.8

Checklist

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

Describe the issue
I have the following configuration for an office LCD display:
powercalc_meters:
  powercalc:
    sensors:
      - entity_id: sensor.pedros_macbook_pro_m1_max_primary_display_name
        name: "Pedro's Office Display"
        unique_id: "PedrosOfficeDisplay_Powercalc"
        manufacturer: "Dell"
        model: "G3223Q"
        calculation_enabled_condition: "{{ is_state('device_tracker.office_ethernet_hub', 'home') }}"
        standby_power: 4
        fixed:
          states_power:
            DELL G3223Q: 44

My goal is for the power consumption to be considered as 44W when the computer is using the display, 4 when the display is in standby, and 0 when the USB hub is off (meaning the display will also be off. However, even when {{ is_state('device_tracker.office_ethernet_hub', 'home') }} evaluates to false (confirmed in Developer Tools/Template), the power entity is still at 4W, and the energy sensor is increasing every few minutes:

Reproduction steps
Configure an energy sensor as mentioned in the description above.
Debug logs
2024-08-27 21:30:23.201 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.202 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration places which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.202 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration healthchecksio which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.203 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.203 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration adaptive_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.204 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration retry which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.205 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration king_smith which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.205 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pyscript which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.206 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration icloud3 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:23.207 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration powercalc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-08-27 21:30:24.918 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'adaptive_lighting' calls async_forward_entry_setup for integration, adaptive_lighting with title: Escritório and entry_id: 8894303d4e20e42239a3c9daeafd7f62, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/adaptive_lighting/__init__.py, line 69: hass.async_create_task(, please create a bug report at https://github.com/basnijholt/adaptive-lighting/issues
2024-08-27 21:30:25.550 ERROR (MainThread) [homeassistant.components.sensor] swiss_hydrological_data: Error on device update!
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 727, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1302, in async_device_update
    await hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/swiss_hydrological_data/sensor.py", line 161, in update
    self._state = self._data["parameters"][self._condition]["value"]
                  ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
KeyError: 'temperature'
2024-08-27 21:30:26.399 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'healthchecksio' calls `async_add_job`, which is deprecated and will be removed in Home Assistant 2025.4; Please review https://developers.home-assistant.io/blog/2024/03/13/deprecate_add_run_job for replacement options at custom_components/healthchecksio/__init__.py, line 76: hass.async_add_job(, please create a bug report at https://github.com/custom-components/healthchecksio/issues
2024-08-27 21:30:26.407 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration, healthchecksio with title: home.pombei.ro and entry_id: 5fa45ebc12a645b4a9263b529d5c4ff9, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead. Please report this issue.
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2138, in async_forward_entry_setup
    report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
    _LOGGER.warning(msg, stack_info=True)
2024-08-27 21:30:33.002 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mobile_app does not generate unique IDs. ID<PHONE_NUMBER>98a1c5ebf27ec9fdbe3972c9489b8e already exists - ignoring device_tracker.pedro_s_garmin_venu_3
2024-08-27 21:30:36.641 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp32-bluetooth-proxy-bac9f0 @ <IP_ADDRESS>: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='<IP_ADDRESS>', port=6053))]: [Errno 113] Connect call failed ('<IP_ADDRESS>', 6053) (SocketAPIError)
2024-08-27 21:30:43.803 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Notify when Pedro's watch is charged' trigger: In 'numeric_state' condition: unknown entity sensor.pedro_s_garmin_venu_3_battery_level
2024-08-27 21:32:28.878 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall light.turn_on (c:01J6AN63T6:al:KF2W:ntrv:01): entity_id=['light.parental_room_ceiling_light'], params=transition=45.0, color_temp=299, color_temp_kelvin=3340>
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/zha/zigbee/cluster_handlers/__init__.py", line 66, in wrap_zigpy_exceptions
    yield
  File "/usr/local/lib/python3.12/site-packages/zha/zigbee/cluster_handlers/__init__.py", line 84, in wrapper
    return await RETRYABLE_REQUEST_DECORATOR(func)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/util.py", line 136, in retry
    return await func()
           ^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/zcl/__init__.py", line 377, in request
    return await self._endpoint.request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/endpoint.py", line 265, in request
    return await self.device.request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 339, in request
    await send_request()
  File "/usr/local/lib/python3.12/site-packages/zigpy/application.py", line 833, in request
    await self.send_packet(
  File "/usr/local/lib/python3.12/site-packages/bellows/zigbee/application.py", line 825, in send_packet
    raise zigpy.exceptions.DeliveryError(
zigpy.exceptions.DeliveryError: Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074>

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/helpers.py", line 1289, in handler
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/light.py", line 181, in async_turn_on
    await self.entity_data.entity.async_turn_on(
  File "/usr/local/lib/python3.12/site-packages/zha/application/platforms/light/__init__.py", line 389, in async_turn_on
    result = await self._level_cluster_handler.move_to_level_with_on_off(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zha/zigbee/cluster_handlers/__init__.py", line 83, in wrapper
    with wrap_zigpy_exceptions():
  File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__
    self.gen.throw(value)
  File "/usr/local/lib/python3.12/site-packages/zha/zigbee/cluster_handlers/__init__.py", line 75, in wrap_zigpy_exceptions
    raise ZHAException(message) from exc
zha.exceptions.ZHAException: Failed to send request: Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074>

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2783, in _run_service_call_catch_exceptions
    await coro_or_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 2806, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/adaptive_lighting/hass_utils.py", line 62, in service_func_proxy
    await existing_service.job.target(call)
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 999, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1071, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 626, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/usr/src/homeassistant/homeassistant/components/zha/helpers.py", line 1291, in handler
    raise HomeAssistantError(err) from err
homeassistant.exceptions.HomeAssistantError: Failed to send request: Failed to deliver message: <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074>
2024-08-27 21:40:33.249 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.office_energy: Recalculate, current value: 2.7156
2024-08-27 21:40:33.249 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] delta for entity sensor.pedro_s_macbook_pro_m1_max_energy: 0.0001, prev=0.8673, cur=0.8674
2024-08-27 21:40:33.249 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.office_energy: New value: 2.7157
2024-08-27 21:40:33.251 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.office_energy: Recalculate, current value: 2.7157
2024-08-27 21:40:33.251 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] delta for entity sensor.pedro_s_office_display_energy: 0.0007, prev=0.8934, cur=0.8941
2024-08-27 21:40:33.251 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.office_energy: New value: 2.7164
2024-08-27 21:40:33.278 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.office_energy: Recalculate, current value: 2.7164
2024-08-27 21:40:33.278 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] delta for entity sensor.parental_room_ceiling_light_energy: 0.0017, prev=0.0539, cur=0.0556
2024-08-27 21:40:33.278 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.office_energy: New value: 2.7181
2024-08-27 21:40:33.286 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.living_room_lights_energy: Recalculate, current value: 0.7310
2024-08-27 21:40:33.286 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] delta for entity sensor.dining_room_lamp_light_energy: 0.0010, prev=0.0778, cur=0.0788
2024-08-27 21:40:33.287 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.living_room_lights_energy: New value: 0.7320
2024-08-27 21:40:33.287 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.living_room_lights_energy: Recalculate, current value: 0.7320
2024-08-27 21:40:33.287 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] delta for entity sensor.living_room_ceiling_light_energy: 0.0001, prev=0.0210, cur=0.0211
2024-08-27 21:40:33.287 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.living_room_lights_energy: New value: 0.7321
2024-08-27 21:40:33.289 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.living_room_lights_energy: Recalculate, current value: 0.7321
2024-08-27 21:40:33.290 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] delta for entity sensor.living_room_lamp_light_energy: 0.0017, prev=0.1108, cur=0.1125
2024-08-27 21:40:33.290 DEBUG (MainThread) [custom_components.powercalc.sensors.group.custom] sensor.living_room_lights_energy: New value: 0.7338
2024-08-27 21:43:44.032 WARNING (MainThread) [custom_components.places.sensor] (Diogo's Geocoded location) Tracked Entity (person.diogo) Latitude/Longitude is not set or is not a number. Not Proceeding with Update.

Diagnostics dump or YAML config
powercalc_meters:
  powercalc:
    sensors:
      - entity_id: sensor.pedros_macbook_pro_m1_max_primary_display_name
        name: "Pedro's Office Display"
        unique_id: "PedrosOfficeDisplay_Powercalc"
        manufacturer: "Dell"
        model: "G3223Q"
        calculation_enabled_condition: "{{ is_state('device_tracker.office_ethernet_hub', 'home') }}"
        standby_power: 4
        fixed:
          states_power:
            DELL G3223Q: 44

calculation_enabled_condition only has effect on the selected strategy in this case fixed. It won't effect standby_power, that will still apply.
I suggest to just use a single template to evaluate the resulting power.
Something like this, untested.
Also note I omitted the manufacturer and model, as this is only needed when selecting a particular profile from the library. They are ignored when you configure manually using fixed.
powercalc_meters:
  powercalc:
    sensors:
      - entity_id: sensor.pedros_macbook_pro_m1_max_primary_display_name
        name: "Pedro's Office Display"
        unique_id: "PedrosOfficeDisplay_Powercalc"
        fixed:
          power: >
            {% if is_state('device_tracker.office_ethernet_hub', 'home') %}
              {{ iif(is_state('sensor.pedros_macbook_pro_m1_max_primary_display_name', 'DELL G3223Q'), '44', '4') }}
            {% else %}
              0
            {% endif %}

Thanks for the suggestion, @bramstroker - having access to templates in this context is really powerful!
By the way, the reason I'm adding manufacturer and model is more as a reminder regarding which device I calibrated the readings on (could absolutely just use a comment for that).


Getting Websock error

I am logging the following error with my ElasticBean Mattermost instance on AWS:
websocket connect err: websocket: could not find connection header with token 'upgrade
as far as I can tell there is no nginx configuration and I think I have traced the problem to the instance being automatically setup for load balancing (which AWS service may not support websockets). Is there a tweak to the Dockerrun.aws.json that could override this issue?

Well, I think you don't need a load balancer because mattermost app doesn't support scaling. Is it possible to disable the load balancer?

It came with the elasticbean installation - I just followed the setup here: https://docs.mattermost.com/install/docker-ebs.html.  Disabling the load balancer has taken Mattermost offline

@mastreips have you solved this issue?

I close this issue since it seems to have not been updated in months.
@mastreips If you still have any troubles, feel free to reopen :slightly_smiling_face:


Add link to login from sign up page or automatically generate token in sign up and then go straight to profile

completed


Mono: Adding a autoload script outputs error in console "does not inherit a Node"

Godot version:
3.1 beta1
OS/device including version:
Windows 10
Issue description:
spits this error in the console when I add a script
 Script does not inherit a Node: res://Core/Game.cs
 editor/editor_autoload_settings.cpp:448 - Condition ' !info->node ' is true. Continuing..:

Steps to reproduce:

Add a autoload script
Look at error

Comments
Script still works, error is just spit out in console
ThumbCTRL.zip - just remove and readd the Core/Game.cs as an autoload script

I can confirm the issue on 3.1 beta 7.
Since the error doesn't seem to break the functionality, I'll move it to the next milestone.

Does this happen if you build your project just before doing this?

Does this happen if you build your project just before doing this?

Indeed, if I build the project before adding the AutoLoad, there's no error.

I will have to think what to do with this. The problem is that there is no way to check the validity of the script before building the project, so we can't check if it inherits Node.

Couldn't you do the check after the build process and just error out during that process?

@akien-mga
No script does not work on 3.1 as autoload if extends Node is not present.
the autoload name is null at runtime, sometimes i don't see error on the console either.
Steps to reproduce:

Have a global script with extends Node
Have another global script without extends Node
run

Result:
Script without the extends Node will not load

Seems fixed in 3.2 beta 5 Mono.

I got this error when exporting to windows or html.
in the console => "Script does not inherit a Node".
But my script inherits Node ....
I'm using 3.2.3

Same problem when exporting to web.
I'm using GodotRx (which has the autoload script).

Still seeing this when loading my project in 3.3.stable.mono.official
And my autoload class does extend Node class.

Please continue the discussion there: https://github.com/godotengine/godot/issues/36787


Adding playlist to library

Add playlist to library button stays enabled even after the playlist is added to library. That button should be removed after the playlist is added to library.

Thanks for the report. Unfortunately there is no indication from the API if it's in your library or not, which is what would be needed to make this feature best.
A temporary measure could be to hide it after it's added to your library. But once you click away and come back, it'll be back.


File size bug

Found bug in utils.file_size giving wrong results with compressed files, resulting in dataframe.read_csv truncating bz2 and xz compressed files.
My easy fix is not efficient for bz2 and only efficient with using libaffi for xz (#1096) support.

Did revert the StringIO change and added version-check instead

8362329 would get the checks out of the test and report them as skips. But I don't know if you like global fixtures for the myopen, compression pairs (at least they get reused in two tests).
I also could use parameter lists again and only mark xz-items for skipping, but have to pull out the annotation through the product, reducing the readability a bit.

@mrocklin, @jcrist any opinon on weather to use global fixtures 8362329 or skipif inside parameters 28c0cf5?

@mrocklin, @jcrist any opinon on weather to use global fixtures 8362329 or skipif inside parameters 28c0cf5?

I like the skipif inside parameters (didn't even know you could do that). Once the checks inside the tests are removed and commits are squashed, this looks good to me.

Thanks!


cookie_secure setting looks unnecessary

Affected Version
at least 4.4
Description
I would expect to see the "Secure" cookie flag set by default for https connections, however without cookie_secure: true in the config it doesn't happen. It's not described in the documentation and the only way to know it is to look at the code
For example, instead of
Set-Cookie: PHPSESSID=<sessionid>; expires=Mon, 29-Oct-2018 21:38:08 GMT; Max-Age=3600; path=/; HttpOnly

I expect to see
Set-Cookie: PHPSESSID=<sessionid>; expires=Mon, 29-Oct-2018 21:38:08 GMT; Max-Age=3600; path=/; Secure; HttpOnly

If I set cookie_secure: true, it renames the default cookie name to SECSESSID, which as a non-standard name can be accidentally exposed, for example in Sentry:

So to make it correct I have to add another setting that renames the cookie back:
SilverStripe\Control\Session:
  cookie_secure: true
  cookie_name_secure: 'PHPSESSID'

The above mechanism of renaming the cookie claims it adds another layer of security

This uses the session_name SECSESSID for https connections instead of the default PHPSESSID. Doing so adds an extra layer of security to your session cookie since you no longer share http and https sessions.

however, with "Secure" flag set, cookies won't be shared between http/https without any extra configuration / code.
Steps to Reproduce
As an example, look at https://www.silverstripe.org/Security/login?BackURL=%2Fadmin%2Fpages which has https but doesn't have "Secure" flag on the cookie.
Proposed solution
Deprecate the setting, change the line
to
$secure = Director::is_https($request)

It will make the default installation more secure and remove the code that weakens security (by renaming the session cookie).

I'm thinking maybe it's time for us to adopt an HTTPS-first approach and treat HTTP as the exception.
At first glance and not having looked at the underlying code, the suggestion sounds sensible. Although, I'm not sure if we can implement it in the 4 branch without breaking things for some users.

Agree, that would be a breaking change for the existing installations.
However, I believe it's worth doing for the next major release (Silverstripe CMS 5).
I'd also say it's rather impact/high since it affects all https installations.

I think there are two parts here:

One is related to "Secure" flag to the session cookie. Can we make it non-dependable on cookie_secure: true? I can't think of any example when it might break something for non-HTTPS websites, but it needs more thinking.
Deprecation of cookie_secure setting. If people depend on the cookie name SECSESSID , renaming it back will definitely break something. However, it would be nice to deprecate it now, if possible, and add the following to the documentation of v4 (until the point one has been implemented):

cookie_secure: true # sets Secure flag on the cookie
cookie_name_secure: 'PHPSESSID' # leaves the default name because many tools hide PHPSESSID cookie value but don't do it for custom names

It's just because right now default installations are insecure: without cookie_secure: true the Secure flag is not set, so the cookie might leak, and with cookie_secure: true the cookie is renamed to a custom name, and the value might leak to logs / error tracking software.

One is related to "Secure" flag to the session cookie. Can we make it non-dependable on cookie_secure: true?

I think the whole point of cookie_secure parameter is to control this flag. I'm not sure if we should make session cookie independent, but it's definitely worth making it true by default (IMO).
A different story is the cookie name. I believe we may want to make it PHPSESSID by default, but we should be careful with that. The problem we might face is that PHP usually controls that cookie record on its own and exposes some settings through php.ini. I think we should learn better how exactly it works across the different PHP versions before we make this change.

BUMP. To me, it it would be really good that a vanilla install of Silverstripe is super secure, and then you can make it less secure, if needed.


Ruby: Make version matcher match google-gax version macher

Now matches this regex: https://github.com/googleapis/gax-ruby/blob/master/lib/google/gax/util.rb#L34

Codecov Report

Merging #1475 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master   #1475      +/-   ##
===========================================
+ Coverage        87%     87%   +<.01%
  Complexity     4063    4063
===========================================
  Files           391     391
  Lines         16378   16379       +1
  Branches       1787    1787
===========================================
+ Hits          14249   14250       +1
  Misses         1661    1661
  Partials        468     468

Impacted Files
Coverage Δ
Complexity Δ

...ain/java/com/google/api/codegen/ruby/RubyUtil.java
80% <100%> (+5%)
3 <1> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Support React

Hello, it would be very interesting if it could support react.
Currently the property xlink:href is not natively supported by react so it has to be converted to xlinkHref.

Similar issue here #50


Module require an old version of puppetlabs-inifile

The last version for it will be 6.0.0. So it fails with:
Warning: Module 'puppetlabs-inifile' (v6.0.0) fails to meet some dependencies:
  'puppet-systemd' (v4.2.0) requires 'puppetlabs-inifile' (>= 1.6.0 < 6.0.0)

In the git master it is fixed, so please release an new version. Thanks.


Implementation of Install API

Exposed install, upgrade, list via HTTP
added basic service HTTP test for install

Sorry for the PR, it was meant to be on our fork.
@hickeyma Our usecase needs deployment via HTTP api calls. we deploy helm charts everyday for users. After helm3 we could have built a service using this library. since, this seems like widely needed feature helm-web-api and seen other blogs.
We could create a proposal, and if accepted we can contribute. I'm thinking of working of fork and if accepted will work on merging it to helm.
Please share your suggestions/thoughts.

@devdinu I think if you have the project already then that's ok. My question was more related to whether you wanted to push this PR into core.


⚠ ClamAV has degraded performance

In d4208e5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 54 ms

Resolved: ClamAV performance has improved in 4388081.


Roadmap to v0.1

Things to polish/finish prior to release:
Usage

[x] Streamline how boundary conditions are passed to the LevelSetEquation constructor. Example that should work: #35

bc = (PeriodicBC(), (NeumannBC(), DirichletBC()))
bc = PeriodicBC()
bc = NeumannBC()

Example that should error:
bc = ((PeriodicBC(), DirichletBC), ...) # error

[x] Decide on what a boundary condition means when indices are out of bounds in more than one dimension #35

Documentation

[x] General section on package usage, overview, etc @maltezfaria #36
[x] A section on LevelSetTerm

[x] Pour la courbure on peux se servir de la spirale #37
[x] Advection term (done in #38)

[x] Time integrators (done in #39)
[x] Boundary conditions
[x] Extensions

[x] Makie
[x] MMG #37

[x] Examples

[x] Zalesak circle (WENO vs. upwind)
[x] Shape optimisation #37
[ ] Maybe Eikonal solver using reinitialisation (v0.2.0)
[ ] Shape optimisation using integral equations for Laplace problem (v0.2.0)

Polish

[ ] Remove dead code using Codecov once docs are written and coverage is setup to track docs
[x] Clean export
[x] Modify Makie recipe to use contourf to distinguish inside/outiside
[x] Write the _normalize_bc function #35

Features

[x] Utility to compute volume and perimeter of LevelSet #37

Registration PR can be found here:
https://github.com/JuliaRegistries/General/pull/119346


Fix // in path in  README.md

Example command includes a // in the url

Actually, I may be mistaken, that may the proper path, reviewers please let me know

I was mistaken: // is the proper syntax

https://github.com/hashicorp/go-getter
Comes from hashicorp's golang file getter


VSCode inferredParser: "php"

Hi, I just installed this plugin, but it doesn't appear to work with VSCode. I had it working a couple of weeks ago, but it suddenly stopped. Prettier is using the wrong parser, I think? It's using the php parser instead of the blade parser?
["INFO" - 3:14:23 PM] Formatting completed in 0.012ms.
["INFO" - 3:14:31 PM] Formatting file:///home/ryan/code/maintenance/resources/views/livewire/procedures/form.blade.php
["INFO" - 3:14:31 PM] Using config file at '/home/ryan/code/maintenance/package.json'
["INFO" - 3:14:31 PM] Using ignore file (if present) at /home/ryan/code/maintenance/.prettierignore
["INFO" - 3:14:31 PM] File Info:
{
  "ignored": false,
  "inferredParser": "php"
}
["INFO" - 3:14:31 PM] Detected local configuration (i.e. .prettierrc or .editorconfig), VS Code configuration will not be used
["INFO" - 3:14:31 PM] Prettier Options:
{
  "filepath": "/home/ryan/code/maintenance/resources/views/livewire/procedures/form.blade.php",
  "parser": "php",
  "useTabs": false,
  "tabWidth": 4,
  "endOfLine": "lf",
  "phpVersion": "7.4",
  "printWidth": 120,
  "singleQuote": true,
  "wrapAttributes": "force-aligned"
}
["INFO" - 3:14:31 PM] Formatting completed in 0.039ms.

As a temporary workaround, I've gotten it to work by adding this to my package.json
    "prettier": {
        "phpVersion": "7.4",
        "printWidth": 120,
        "singleQuote": true,
        "wrapAttributes": "force-aligned",
        "sortTailwindcssClasses": true,
        "overrides": [
            {
                "files": "*.blade.php",
                "options": {
                    "parser": "blade"
                }
            }
        ]
    },


Portable Crafting Module has no texture

https://www.dropbox.com/s/metleovql3ftoo7/Screenshot 2015-01-05 23.14.09.png?dl=0
That should be enough. Also, the tool section with the Shrinking Module also cannot be accessed. It instead points to the modifiers.

Huh, another issue that I noticed in testing but forgot to make a note of. Thanks, I'll get right on this.
As for the tool section with the Shrinking Module... There is an odd bug (which I'm currently working on and haven't really come up with a solution yet) that skews the mouse cursor coordinates in the MuseUI screen(s)... Have you tried clicking right below the Shrinking Module? Though the section with the diamond drill addon also was inaccessible because of this bug... But as such, the second section of this report seems to be a duplicate of #12

Crafting module fixed in internal build. I had changed the modid to be inserted through gradle's Minecraft block and removed the "modid" variable. Seems more than I thought was dependant on that variable, which is now also set by gradle.

Fixed in this release.


Wpm calculation

Created new function get_string_till_space to get ExpectedInput string snippet till the space present at or after 'len' argument inputted
created a function to compare input and expected input snippet and return number correctly typed words
added tests for both
changed implementation of the wpm calculation to calculate based on number of correct words typed

Closes #5

@radlinskii can you review this?

Hey, Thank you for your contribution, I'm sorry @MercMayhem but I think I won't merge it, and close the issue. I've added the hacktoberfest-label already.
I started to think that this change is just not needed, and might be confusing.
If we were to add this change then we would need to update the colorising of words to display the whole word to some red color to show that the whole word is invalid and won't be counted.
Plus I think changes you made to computing the WPM, are obsolete, we should still count each word as 5 characters. So it would be more like how many characters were typed in the valid words, divided by 5, and that's how many valid "words" were typed.

No problem @radlinskii :) . Loved working on donkeytype. Will definitely be following this project post Hacktoberfest.


⚠ ClamAV has degraded performance

In f4f71e6, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 580 ms

Resolved: ClamAV performance has improved in 3255b93 after 12 minutes.


Java file version bump not working on non default branches

We have am embedded java file that release please increments the version on for each release. It seems to work fine on the default branch:
https://github.com/googleapis/java-bigtable/pull/893/files#diff-872c3c6b3fd52460b8f485ffa56921b841e02c4a563598aad8ad1be186292625R23
But not on a branch release:
https://github.com/googleapis/java-bigtable/pull/831/commits/0c8a4248d92501a2e0545f6d843244ce44255b0c

CC @igorbernstein2

extraFiles option is a per-branch configuration - in your .github/release-please.yml, extraFiles are configured at the root (for the default branch), but not on the 1.22.0-sp branch


fix(apps/gcp/prow): add post cron jobs

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve

/review default


[FEATURE] Add Warnings for Alpha Version Functionalities

Description
#42
This pull request introduces warnings within the HypEx library documentation and codebase to inform users about the alpha version status of certain features. These features include multitarget matching, feature selection in matching, and validation in matching, which, while offering significant potential benefits, come with certain considerations and limitations that users need to be aware of.
Changes Made

Added documentation warnings for multitarget matching, feature selection, and validation to guide users on their experimental nature and to exercise caution.
Implemented runtime warnings for the specified features to alert users during code execution about their alpha status.
Enhanced documentation to provide detailed examples and scenarios where caution should be exercised.

Related Issues

None.

Additional Notes
These changes aim to ensure users are well-informed about the functionalities that are still in the experimental phase and to encourage thorough review and testing before their application in production environments.
Testing and Validation

The added warnings and documentation updates have been reviewed for clarity and completeness.
No direct testing applicable to documentation changes, but runtime warnings have been tested to ensure they are triggered appropriately.

Performance Considerations

The changes introduced have minimal to no impact on the performance of the HypEx library as they are primarily documentation and warning messages.

Breaking Changes

No breaking changes introduced. The functionality of the HypEx library remains unchanged, with added warnings for specific features.

Dependencies

No new dependencies were introduced as part of this pull request. The changes are confined to documentation and runtime warnings.

Merge Request Checklist

[x] Code follows project coding guidelines.
[x] Documentation reflects the changes made.
[x] Unit tests cover new or changed functionality (where applicable).
[x] Performance and breaking changes have been considered.

would like to request that warnings be added, with links to the documentation for each function affected by this PR. It's important that these warnings clarify the potential issues or considerations that users should be aware of when using these functions. Additionally, please ensure that the docstrings for each function include a description of these warnings for easy reference.
Could we also make sure that links to relevant documentation or GitHub pages are included in the README file? This would help users find detailed information about these functions and understand the context and limitations of their usage.
@VasilievaKA


Feedback given flag should be in the '.azure' config not '.azure-shell'

Description
Outline the issue here:

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here:
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:
OS Version: What OS and version are you using?
Answer here:
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here:

@derekbekoe as fyi to be aware that this PR is coming.


[Feature Request] Import existing mask for continued editing

First of all, I'd like to express my sincere gratitude to the author and contributors of IOPaint. This project is truly impressive and has been incredibly helpful for me.
Is your feature request related to a problem? Please describe.
Currently, when working on complex inpainting projects, there's no way to save progress mid-way and resume editing later. This can be frustrating when dealing with intricate masks that require multiple editing sessions.
Describe the solution you'd like
I would like to request a feature that allows users to import previously created and locally saved masks back into IOPaint. This would enable us to continue refining and modifying existing work without starting from scratch each time.
The ideal workflow would be:

Create a mask in IOPaint
Save the mask locally
Close the project
Later, reopen IOPaint and import the saved mask
Continue editing and refining the mask

Additional context
This feature would be particularly useful for complex projects that require multiple editing sessions or collaborative work. It would also help in situations where users need to take a break from editing but want to preserve their progress.
Thank you for considering this feature request. I believe it would greatly enhance the usability and flexibility of IOPaint for many users.

You can use -mask-dir to start the service, and you can select the mask from that directory.
https://www.iopaint.com/file_manager


 Probably something wrong with config.
I launch it using the Marian library. For example:
 echo "привет" | ./marian-decoder -c /path/to/opus_models/opus-2019-12-05-ru-en/decoder.yml

So what can be wrong?
Probably I somehow should do preprocessing and postprocessing?

You need to preprocess the string first using the provided sentence piece model of the source language. Our models don;t support internal sentence piece segmentation. This needs to be done before piping input to the decoder.


Fix kingpin module path and add go.mod/go.sum

Fix build with current Go.

I ran into this today. Would be good to get it fixed.

could you please merge this PR?


Appending Python Path

Finding external Python packages requires python path to be appended within the "command" call for a given package inside service-config.yaml.
Current workaround based off Das' previous implementation when using qcr-env.bash bringup method..
Within /etc/qcr/qcr-env.bash, add the following line:
export PYTHONPATH=/home/qcr/.local/lib/python3.8/site-packages:$PYTHONPATH
Then, sourcing the above bash script when running/launching the applicable node within service-config.yaml:
command: source /etc/qcr/qcr-env.bash && rosrun usb4000 spectra.py

Proposed Solution:
At the top of a service configuration file have the following:
append_to_pythonpath: <desired_path>

Then when creating the systemd service files the value of the command key is concatanated with the value of the proposed append_to_pythonpath key. Hence the ExecStart part of the systemd file would become:
ExecStart=/bin/bash -c "export PYTHONPATH=<value of append_to_pythonpath key>:$PYTHONPATH && <value of command key>"

Does that work?


Fix "all" repetitions

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

/modeltest
num_repetitions: 2
include:
 - dataset: ["all"]
   config: ["all"]


Disable interaction with top bar and navigation during test trade

Reason: accidentally clicking the nav takes the user out of the test trade which we don't want. Exiting test trade should be done via the x button top right

done. closing


Auto-indentation problem with promise blocks

From @lumaxis on August 12, 2016 0:7

VSCode Version: 1.5.0-insider (666ed83a2d465257201cdac215a553ddee3cccbe)
OS Version: 10.11.6

Steps to Reproduce:

Create a Typescript file and start writing code using promises
Auto-indent file using Shift+Alt+D Shift+Alt-F

Expected Result:
return output
.then((result: ControllerResponse) => {
  return res
  .status(result.statusCode)
  .json(result.payload);
})

Actual Result:
return output
  .then((result: ControllerResponse) => {
    return res
    .status(result.statusCode)
    .json(result.payload);
  })

Description:
The problem with the current way is that it leads to a strange indentation on the closing braces:
    });
}

Here, the closing curly braces and parentheses for the .then() block are indented 4 spaces instead of 2 spaces as they should be.
Copied from original issue: Microsoft/vscode#10453

From @waderyan on August 12, 2016 15:0
Thank you for opening this issue. We appreciate your feedback greatly.
Couple questions.

Do you mean Format Code when you say auto-indent? I cannot find the command auto-indent.

The keybinding for Format Code is cmd+shift+f. Did you change your keybinding to cmd+shift+d?

What is your spacing / tab preferences? (lower bottom right corner)

Here I have copied your code sample and ran format code with spaces set at 4. I have repeated the same test with no issues for spaces preference set to 2 and set to tabs.

From @lumaxis on August 12, 2016 15:41

Ah, yes of course. I've ever only used the keyboard shortcut as I was always searching for a command containing "auto" or "indent" but never found Format Code.
You're of course right, it's actually alt+shift+f.
2 spaces

From @waderyan on August 12, 2016 19:52
Ok. Unfortunately, I can repo your issue. Is there anything else you can think of the makes your setup different than me?
I'm on the same OS and same Insiders build... I have tried with all spaces / tabs configuration but cannot see the behavior you described.
@dbaeumer - I can't repo. Do you have any ideas?

From @lumaxis on August 12, 2016 21:23
@waderyan But I can see the issue repro in your gif. I'll try to give a clearer example:
Correctly formatted code:
function doStuff() {
  new Promise(function () {
    return "some string";
  })
  .then((something: string) => {
    something.split(" ");
  });
}

After VS Code "Format Code":
function doStuff() {
  new Promise(function () {
    return "some string";
  })
    .then((something: string) => {
      something.split(" ");
    });
}

Notice how the .then() block is indented two more spaces although the scope did not go one level deeper.

From @waderyan on August 12, 2016 21:31
Thank you for clarifying. Yes I see the issue and was able to repo.
I agree with your preference.

This is the tsserver formatting the code that way.
@waderyan to see whether something is a tsserver bug you can enable message tracing by setting "typescript.tsserver.trace": "verbose". Doing so and formatting the above code returns the following response from the tsserver:
Response received: format (3). Request took 47 ms. Success: true
Result: [
    {
        "start": {
            "line": 5,
            "offset": 1
        },
        "end": {
            "line": 5,
            "offset": 3
        },
        "newText": "    "
    },
    {
        "start": {
            "line": 6,
            "offset": 1
        },
        "end": {
            "line": 6,
            "offset": 5
        },
        "newText": "      "
    },
    {
        "start": {
            "line": 7,
            "offset": 1
        },
        "end": {
            "line": 7,
            "offset": 3
        },
        "newText": "    "
    }
]

Which changes the two spaces to four. Moving to the TS team.

Isn't this by design? I thought property accesses are being indented intentionally.
foo
  .bar
  .baz

@SaschaNaz If that is the case it's imo a very questionable decision that at least would need an option to be able to change it.
The biggest problem with the current behavior, as mentioned in my original issue, is the inconsistent indentation of closing curly braces and parentheses:
          });
      });
    });
});

I'd like to take a stab at this but as someone new to this codebase, it's pretty hard to figure out where to start or how to debug a change to the server like this.
Can someone point me to the right files/link me to some documentation? Thanks!

any news on this?
This is still happening in the last version!

Still no resolution?

And still nothing?


Employee has to be somehow added to EasyCLA V1 database before adding him/her as CLA Manager

Company Admin creation

Launch LFX Portal
Create an user account
Assign company admin role for a company to the user in IAM

Contributor creation

Launch LFX Portal
Create an user account
Assign contributor role for a company and project to the user in IAM

Add CLA Manager flow

Launch LFX Portal
Login as contributor created above
Click on the project that has not signed CLA
Complete the Signing process (There is a bug where cla-manager role is not assigned to user after signing CLA from LFX portal. So after CLA is signed add CLA Manager role for the user in IAM)
Now Try to add the company admin created above as CLA Manager
Request is sent for the company admin to create LFID even if the user already exists in user service.
As a workaraound I logged with the company admin credentials in V1 corporate console for the user to get added to users table in V1 database, and after this I am able to add company admin as cla manager

@wanyaland added to current sprint.

@nirupamav Will add user to the CLADB table for users. But that wasnt a workaround as the user-service that checks for users does not need EasyCLA Database. It just checks lfxUsers. I corrected that check with email search in the PR that has been merged so you could test this workflow just to clarify .

@wanyaland is this fix pushed to DEV? Can we move this to QA review for @nirupamav

Yes @dealako  this is in Dev

Verified and observed that the issue is resolved


DeviceManageabilityCSP issue for ConfigMgr clients

We pre-provision devices with SCCM and then enroll them in Intune manually. How can we stop ConfigMgr from making itself the MDM in the registry of a device that just completed a task sequence. The ConfigMgr client has to be scrubbed and the DeviceManageabilityCSP registry key deleted, or the enrolled devices show up as "See/ConfigMgr" in Intune, and are not manageable. We do not do co-management or hybrid join.
Is there a way to stop SCCM from making itself the MDM Authority even though we have no connector setup, and no co-management.

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

ID: 9b82df45-3900-c15c-5838-6983b6a862f5
Version Independent ID: 86ff67a2-f224-096b-7905-ec5d6523c4bd
Content: Change your MDM authority to Intune - Configuration Manager
Content Source: sccm/mdm/deploy-use/migrate-change-mdm-authority.md
Product: configuration-manager
Technology: configmgr-hybrid
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @PrinceMarkieD for taking the time to share this with the Configuration Manager documentation team. I’m sorry that you’re having problems, and I want to make sure it gets to the right people that can help. There are a couple of options available to provide the best level of support for this:

Post on Configuration Manager forums. These are moderated by our community MVPs who are very experienced, knowledgeable, and helpful.
Use Microsoft Support to search for the issue, or open a case with professional support.
Contact your Microsoft Premier team, such as a Premier Field Engineer or Technical Account Manager.

I'm closing this issue as there's nothing actionable for docs at this time.
Note: Version 1806 + hotfix or 1810 should not have this issue.

Thank you, we are on 1810 and still see the issue with the Piloting client. Maybe on 1902 we will not. we are going 1902 tonight. Thanks.

If you're still seeing the issue, please file a frown or open a case with support.


Bug 2094495: Descheduler modal has same text in two lines

📝 Description
checkbox label and description are the same in the descheduler modal.
🎥 Demo
before:

after:

Signed-off-by: Aviv Turgeman<EMAIL_ADDRESS>

LGTM


Report the duration of API calls

Following a team discussion on 2022-03-25, we determined that it would be helpful for API clients, including the data services API, to report the time taken by API calls as part of the Prometheus monitoring.
To support this, we need to extend the ActiveSupport Notifications emitted by the data services API to include the duration.
We will also change the event namespace to api.

Done


Fix the EKS networking example

This example doesn't compile. Unfortunately, the AWSX VPC constructor
appears to require an args bag, even though all properties of it are
optional. Also, the way you pass subnets seems to have changed in the
EKS class -- or maybe this was always a bug -- but the examples I
found in the EKS repo itself suggested this is the right way to do it.
Fixes #325.

Ahhh, I thought I was going crazy thinking that this used to work 😄


Feature Request: find all kustomization.yaml files and iterate datree kustomize test on each one

Similar to what I have done in my Jenkins library here:
https://github.com/HariSekhon/Jenkins/blob/master/vars/datree.groovy#L81
I think this would be a handy thing for this action to do and would be better handled inside the action than having to call the action a bunch of times incurring build overheads each time.
I also think that it may be between difficult to impossible to do a for loop on found kustomization.yaml files and call the action for each one with a different path, which is why I thought his might be better handled inside the action.
This would allow dynamically finding and scanning all the kustomization.yaml in a single github actions workflow.
Otherwise adding hardcoded explicit steps calling the action for each kustomization.yaml is impractical and difficult to maintain, and almost certainly going to fall out of sync with repo contents.

We heard similar feedback also regarding helm:
https://github.com/datreeio/helm-datree/issues/40
If I have 5 kustomization.yaml files in a dir, should Datree provide one output for 5 kustomization.yaml files or 5 outputs, each for one kustomization.yaml file?

I think it should probably be one unified output, because this will result in less boilerplate output and may reduce pushing earlier kustomization's results off of the screen.
The end summary stats would also make more sense to be combined into one result if scanning several kustomizations together.
If you wanted them individually, you could still target each kustomization individually with separate runs.

Thinking out loud here - so what we can do is to find all kustomization.yaml files in a dir and create a temp file that will be assembled from all the manifests we generated. We can then pass this temp file to Datree, and this will provide the user the option to scan multiple kustomization.yaml files in one dir with a single output.
The only thing that I don't like about it is that when I think about the DX when a rule will fail.
It will be really hard for the user to understand which kustomization.yaml should be fixed.

Yeah I'm not keen on that idea because when it trips, I'll be left scratching my head where that broken yaml is and grepping.
Ideally a tool should pinpoint for you automatically so you can go straight to the root cause, this is part of key criteria of automation to save human time, which compounds over time.
It would be better for datree run against each kustomization.yaml and keep track of which issues were generated in which kustomization run, so it can aggregate stats, but keep direct pointer references to the offending kustomization.yaml... I appreciate this will probably be more coding work and almost certainly require changes to datree itself.
In the short term in this action it'd be fine to just iterate each kustomization.yaml and live with scrolling the longer output because at least when you see the problem, the kustomization.yaml path should be printed next to it.
Just have to make sure that any non-zero exit status for a datree run is captured and reset to error exit code at the end.

I gave it some more thinking, and I think I have a good solution for this one.
We are always trying to balance what is expected to be supported by Datree and what should be solved as a workaround by our users.
In this case (also apply for Helm), the balance is tricky because I understand the need, but on the other hand, this behavior is NOT supported by the templating tools themself.
Therefore, I think the best way to solve it is by making the temp file that is already generated by Datree (when using Kustomize or Helm) accessible and customized:

accessible - we will not delete the temp file after running datree test so the user will be able to review it
customized - the user can choose where to save the file and how to name it

This way, the user can iterate over a dir, pass relvent helm chart dir/kustomize.yaml files to Datree (with this new flag that will also generate and keep the manifest itself), and capture the status code (like you suggested).
Datree's output will show the user the file name as it was set by him, so he can still easily trace back which resource cause the failure.
Becasue my solution requires some extra scripting, we also provide the basic bash script example for iterting over a dir and extarcting files that will be passed to Datree, together with capturing exit code.
I think this solution is the right balance.

It'd be better from a usability perspective to list the path to the original kustomization - trawling a huge temp file is not as convenient.
I'd output the kustomization source before the results so the user could determine where to go in his actual git tree to fix it, without having to trawl the temp file and then grep for where that resource came from.

I just rustled a script up quickly to solve this:
https://github.com/HariSekhon/DevOps-Bash-tools/blob/master/datree_kustomize_all.sh

@HariSekhon the script works great and seems to provide a good solution for the issue raised here 👍🏼
One thing though - the script has dependencies on other files in your repo (for example the function check_env_defined). If users will try to copy it as it and use it - it will not work.
Do you mind removing the dependencies? Alternatively, we can copy the script and remove them ourselves, and of course give you credit in every place we post it (docs, github action repo, etc.)
Thanks:)

Yes that repo is designed to be cloned whole and run from within the project - it has a bunch of script libraries that are shared between many scripts for some of the more advanced shared functionality.
You can just copy line 47 onwards to avoid the --help and other frills if you want to copy/paste it with no dependencies.

@HariSekhon great, thank you:)

added to docs:
https://hub.datree.io/integrations/kustomize-support#testing-multiple-kustomizations


TODO - Create Files

Create "master.txt"
Create "ordinary.txt"

I committed some code to create the Master and Ordinary files. You'll need to pull and run it to see if the software works on hardware. All i could do is compile.


[Bug] java-agent 8.7+,TraceContext.traceId() can't get traceId in ServerInterceptor

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
Java Agent (apache/skywalking-java)
What happened
with skywalking-agent 8.7+ ,  TraceContext.traceId() can't get traceId in ServerInterceptor
skywalking-agent 8.6 ok

skywalking-agent 8.7  tid:"N/A"

What you expected to happen
with skywalking-agent 8.7、8.8+ ,  TraceContext.traceId() can get traceId in ServerInterceptor
How to reproduce
-javaagent:/Users/bj89089ml/Documents/sky-agent/apache-skywalking-apm-bin-es7-8.7/agent/skywalking-agent.jar
-Dskywalking.agent.service_name=test
-Dskywalking.collector.backend_service=<IP_ADDRESS>:11800
-Dskywalking.logging.output=CONSOLE
maven dependency apm-toolkit-trace version 8.7.0+
grpc-scenario
code in org.apache.skywalking.apm.testcase.grpc.provider.interceptor.ProviderInterceptor
Anything else
no
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The upstream doesn't guarantee all plugins' behaviors didn't change from version to version. We also don't think this is a bug. The current version is on 8.11, there are several changes that happened for the gRPC plugin, you should track them to see what changed.


We should not need to call .apply on our functional.finufft_type* functions

Need to look up how torch.nn.functional handles this.
I don't think it's __call__=apply, because this would be the __call__ of the meta class, which is usually a call to the constructor ...

Based on the Extending Pytorch docs, it seems like the recommended way to do this is to just define a new function which does what we want.
This seems nice because we could also then pass true kwargs.
They give the example:
class MyCube(torch.autograd.Function):
    # forward, backward omitted
    pass

# Wrap MyCube in a function so that it is clearer what the output is
def my_cube(x):
    result, dx = MyCube.apply(x)
    return result

So we could write
def finufft_type1(points, values,  output_shape, **finufftkwargs):
    return FinufftType1.apply(points, values, output_shape, finufftkwargs)


question about __builtin_nontemporal_load

In some GPU kernels, the builtin function is called. Could you comment on a workaround when a compiler does not support the function ? Thanks.

All our compilers support this builtin function.


Type Error in Fields.ts (src/validation)

When running project by yarn dev it gives me Type Error from src/validation/fields.ts line 29

I am still having this issue on Windows OS, not Linux.

Can you post some log from the console?

src/validation/fields.ts
the error is ValidationError requires type
{
            message,
            path: ['password'],
           type: 'password'
}

Where exactly do you see this error?
What are the steps to reproduce this issue?

One of my team members using Windows OS tried to install the project on his machine and got this error.
He was using pnpm.

Good news your colleague hasn't got errors anymore. Closing for now. If happens again please give us the steps to reproduce and we'll reopen the issue.


cocotb and RTL that uses altsyncram

I am trying to get a testbench going with RTL that uses altsyncram block RAM. But it does not seem to work.
The makefile: Makefile_altera
The output: output.log
I am using modelsim that is delivered with Quartus Prime Lite 17.1; cocotb is installed from pypi with pip.
Anybody ideas to get it working ?
(I am actually porting the RTL to use of generic RAM but would like test that the two implementation behave the same).

I got some progress, I added line
vmap altera_mf vmap altera_mf /home/verhaegs/software/no-stow/intelFPGA_lite/17.1/modelsim_ase/altera/verilog/altera_mf

to runsim.do and run vsim manually, see output2.log
The simulation seems to start but actually not do much, testbench:
import cocotb
from cocotb.triggers import Timer
from cocotb.utils import get_sim_steps
from cocotb.binay import BinaryValue

@cocotb.coroutine
def clk_cycle(clk, quartperiod, cycles=1):
    for i in range(cycles):
        clk <= 0
        yield quartperiod
        clk <= 1
        yield quartperiod
        yield quartperiod
        clk <= 0
        yield quartperiod

@cocotb.test()
def test01_reset(dut):
    """
    Just test reset
    """

    # Simulate @ 1MHz
    clk_period = get_sim_steps(1, "us")
    quartperiod = Timer(clk_period/4)

    dut._log.info("Reset")

    dut.reset_n <= 0
    dut.An_write_enable <= 0
    dut.Dn_write_enable <= 0
    dut.micro_pc <= 0

    yield clk_cycle(dut.clock, quartperiod, 3)
    dut.reset_n <= 1
    yield clk_cycle(dut.clock, quartperiod, 1)
    assert dut.usp == 0

    dut._log.info("Finished")

Can you add some log statements to see where things are getting to?

From: Staf Verhaegen<EMAIL_ADDRESS>Sent: Friday, 4 May 2018 7:45:04 AM
To: potentialventures/cocotb
Cc: Subscribed
Subject: Re: [potentialventures/cocotb] cocotb and RTL that uses altsyncram (#611)
I got some progress, I added line
vmap altera_mf vmap altera_mf /home/verhaegs/software/no-stow/intelFPGA_lite/17.1/modelsim_ase/altera/verilog/altera_mf
to runsim.do and run vsim manually, see output2.loghttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpotentialventures%2Fcocotb%2Ffiles%2F1972720%2Foutput2.log&data=02|01||49e64673e26345aaba7108d5b13f2236|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636609807065802613&sdata=d3q5MssqHnReF7PFQHiku%2Bsh9WmkacFu3mqc7E06VCU%3D&reserved=0
The simulation seems to start but actually not do much, testbench:
import cocotb
from cocotb.triggers import Timer
from cocotb.utils import get_sim_steps
from cocotb.binay import BinaryValue
@cocotb.coroutine
def clk_cycle(clk, quartperiod, cycles=1):
for i in range(cycles):
clk <= 0
yield quartperiod
clk <= 1
yield quartperiod
yield quartperiod
clk <= 0
yield quartperiod
@cocotb.test()
def test01_reset(dut):
"""
Just test reset
"""
# Simulate @ 1MHz
clk_period = get_sim_steps(1, "us")
quartperiod = Timer(clk_period/4)

dut._log.info("Reset")

dut.reset_n <= 0
dut.An_write_enable <= 0
dut.Dn_write_enable <= 0
dut.micro_pc <= 0

yield clk_cycle(dut.clock, quartperiod, 3)
dut.reset_n <= 1
yield clk_cycle(dut.clock, quartperiod, 1)
assert dut.usp == 0

dut._log.info("Finished")

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpotentialventures%2Fcocotb%2Fissues%2F611%23issuecomment-386447014&data=02|01||49e64673e26345aaba7108d5b13f2236|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636609807065958862&sdata=axNakCFdT1PUGjCvrovid6nrBW2VxwmW3%2FkGE8zd5Zk%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGwyoylZK3RLkmz7cTCI_PVh5kkdcVPYks5tu3pggaJpZM4TxzXY&data=02|01||49e64673e26345aaba7108d5b13f2236|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636609807065958862&sdata=q14VRrQe8uMHTA31PIRkmtfC9Y20DxOdROSqFBzHfyc%3D&reserved=0.

In the python code above there are log statements but as you can see from the output2.log they are not printed. The simulation just seems to immediately go to $finish.

Your test isn't getting loaded correctly.
From output2.log:
#   0.00ns CRITICAL cocotb.regression                         regression.py:120  in initialise                      Failed to import module test
Your command line has:
MODULE=test TESTCASE=
Is that correct?

Yes that is correct. A little more debugging it seems that the failing is due the presence of an instance altsyncram is the problem. With a dut without an instance if altsyncram cocotb run OK.
I'll see if I can make a test case.

Looking at the log file, it seems modelsim has found some unconnected ports in memory_registers_altera.v. You probably want to check the instantiation of altsyncram and set any unused input ports to an appropriate value (eg. '0).
I have also checked my local modelsim.ini and it looks like altera_mf_ver is mapped to the verilog version of the libs and altera_mf is mapped to the vhdl version of the libs. You can try changing your makefile to:
VSIM_ARGS := -L altera_mf_ver

'VSIM_ARGS := -L altera_mf_ver' solved the problem to get the code to compile. The other problem was a typo error in the test.py file:
from cocotb.binay import BinaryValue

overlooked it a few times... :(


EnterprisePolicyAsCode module - Check minimum required version of Az modules

Is your feature request related to a problem? Please describe.
Same example as #581
EnterprisePolicyAsCode could check what version of required Az modules is imported and see if they are recent enough.
Describe the solution you'd like
Add check for minimum required version of required Az modules.
Describe alternatives you've considered
None yet.
Additional context
#581

This has been added to the development environment and will be available in the next minor version

Where was this added? Seems it was added to the psd1, but then removed again, like here:

https://github.com/Azure/enterprise-azure-policy-as-code/commit/63a8fcd20be8381de73da2eb930a0ba5bd078bad

It would be good if the issue remained open until a version with this feature actually has been published.

It caused the build process to fail so we had to revert the changes. Will fix next week.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Olav Rønnestad Birkeland @.>
Sent: Saturday, April 27, 2024 1:32:33 AM
To: Azure/enterprise-azure-policy-as-code @.>
Cc: Comment @.>; Assign @.>; State change @.>; Subscribed @.>
Subject: Re: [Azure/enterprise-azure-policy-as-code] EnterprisePolicyAsCode module - Check minimum required version of Az modules (Issue #582)
Where was this added? Seems it was added to the psd1, but then removed again, like here:

63a8fcdhttps://github.com/Azure/enterprise-azure-policy-as-code/commit/63a8fcd20be8381de73da2eb930a0ba5bd078bad

It would be good if the issue remained open until a version with this feature actually has been published.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/enterprise-azure-policy-as-code/issues/582#issuecomment-2079623572 or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACWCJVVXKJYIEV2MK5S4MHTY7JXRDBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDOMRVHE4DSNBYGOSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJTGM3TCNRSHAZTRAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMRVHEZTOMJQGAZIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZDOMRVHE4DSNBYGOTXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Ok. For inspiration: AzOps does it in psd1 too, but with RequiredVersion instead:

https://www.powershellgallery.com/packages/AzOps/2.6.2/Content/AzOps.psd1

While Az.Resources does it in ps1m:

https://www.powershellgallery.com/packages/Az.Resources/6.16.1/Content/Az.Resources.psm1

@anwather
As the OP says, export policies failed with Az.Accounts v2.9.1. So I don't get why EPAC specifies that as a working minimum version in the psd1.


pygit2: implement libgit2/pygit2 remote callbacks

Adds implementation for libgit2/pygit2 remote callbacks

Progress is now reported the same way as gitpython/dulwich (using standard Git sideband progress string parsing)
HTTP auth via credential helpers is now supported in pygit2 backend

Closes #197
Closes #190

Codecov Report
Patch coverage: 55.26% and project coverage change: -1.31 :warning:

Comparison is base (5a33e65) 81.88% compared to head (cfdb44d) 80.58%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #219      +/-   ##
==========================================
- Coverage   81.88%   80.58%   -1.31%
==========================================
  Files          25       26       +1
  Lines        3643     3677      +34
  Branches      641      646       +5
==========================================
- Hits         2983     2963      -20
- Misses        559      600      +41
- Partials      101      114      +13

Impacted Files
Coverage Δ

src/scmrepo/git/backend/pygit2/callbacks.py
53.33% <53.33%> (ø)

src/scmrepo/git/backend/pygit2/__init__.py
75.90% <62.50%> (ø)

... and 5 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add optional libclang implementation

includegraph.py is trivial to implement, if you give up some requirements:

standard library only dependencies
detect circular dependencies

related: generate the graph that the source code defines, not the graph that was actually followed by the preprocessor (because of header guards)

Or perhaps just use cpp -H?


verilog: cleanup & test

Motivation for this change
Independently from #97513, I was working on cleaning up the package for ZHF, and didn't see that PR before merging.
This cleans up the derivation and adds self-tests along the lines of what is done in CI. https://github.com/steveicarus/iverilog/blob/07bbf4ce0f1aeb6dcfbabe239514c55822779fd9/.travis.yml
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Diff LGTM. Maybe this should be 2 commits, though: verilog: cleanup, and verilog: add tests or something.

Fair. That's what I'd originally had but decided to squash it. Oh well. Will do

Looks like build is failing on aarch64 due to floating point issues. Trying to get failure log. I think it's probably down to floating point errors in the br1029[a,b] tests: https://github.com/steveicarus/ivtest/commit/8ef8d1c42baf0366c7d59fe30660bffcfdf42984#diff-c4613803e21f6123e3fc555f27a80c13

@GrahamcOfBorg build verilog

Failing on OfBorg due to OfBorg not evaluating due to not having #97807. Once OfBorg has that, I can track down the aarch64 build failure b/c I don't have a system to test that on.

You could try asking for access to https://github.com/nix-community/aarch64-build-box (instructions in the README) -- unfortunately, ofborg deployment has been broken for a while, and we need Graham to fix it (who is unavailable on account of having a newborn to help take care of).

Ok, my workaround is to disable the failing tests on aarch64. We'll see if OfBorg passes, but then we should be good to merge.

@GrahamcOfBorg build verilog

@veprbl are you saying you want me to backport these tests to the release-20.09 branch. That wasn't my original intention since it's building fine on that channel currently.

@drewrisinger I thought we would want to run tests on release-20.09 as well, this would be nice if we need to do any fixes for verilog there.


Fix footer and add cross button in chatbot

Related Issue

Closes: #140
Description of Changes
Fix footer and add cross button in chatbot

Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] My changes have not introduced any new warnings.

Screenshots

@apoorvaron Got your point, will fix this.

@apoorvaron I've made the chat closing effect smooth but there is conflict in this URL.
All changes done kindly merge this PR and label also.

@MisterMickey Nice work🎉

@apoorvaron I've added new button which enhances the functionality which comes under level2, Will you please tell me why is it labelled as level1?

@MisterMickey it's a small fix , because you give sufficient time , i am upgrading it to level 2


feat: remember manual opt-ins and opt-outs per site

This PR improves the way we handle manual opt-out performed per site by the user by storing both opt-out and opt-in decisions made by the user.
Changes
Explicit opt-in and opt-out lists in Preferences

Preferences screen now has separate list for opt-outs and opt-ins:

In the past we only had opt-out list named noIntegrationsHostnames.

Items from the old list are automatically migrated to the new one named disabledOn.

If for some reason item is present on both lists, opt-out takes a priority.

Menu toggle adds/moves hostname between lists

The above lists can be modified by hand on Preferences screen,
however the expectation is that most of the time users will not touch them.

Instead, user will be toggling integrations for current website via browser action menu:

Overriding implicit default per website
Short term (this PR)

In this PR we are adding proto.school to opt-out list if it was not already present on either of lists.

This way we are able to tweak implicit default per website while respecting  preexisting user choices.
Also, in the future we may run opt-in metrics  that compare lengths of both lists to gain better insight into user's behavior.

We also include app.fleek.co – https://github.com/ipfs-shipyard/ipfs-companion/pull/929#pullrequestreview-509501401  (does not work from local gateway atm due to stripe.com limitation)

Long term (separate PR)
We will be looking into supporting opt-out based on HTTP header, so any IPFS-powered website can change the implicit behaviour to opt-out. Tracked in https://github.com/ipfs-shipyard/ipfs-companion/issues/930
Closes #921 cc @terichadbourne @jessicaschilling

@jessicaschilling merged your  suggestions, but removed "URI" from preference label 853099b (#929) – we only support hostnames.  Would that be acceptable?

I'm going to ship this to Beta soon, so we can dogfood it more,
hopefully shipping to Stable next week.


MacOSX support?

Hello any chance you provide microk8s, for MacOSX through brew or custom installer?

Closing this one.  Tracking it here.
https://github.com/ubuntu/microk8s/issues/861


supernode disk gc

Supernode does not currently have disk cleanup capabilities。
when this function can be ready?

Supernode does not currently have disk cleanup capabilities。
when this function can be ready?

I will finish it ASAP. 😄


Shadow tokens are not correct.

They are defined with double shadows and they don't flip to dark mode properly

Example from Shoelace that could work for us.
--sl-shadow-x-small: 0 1px 2px hsl(240 3.8% 46.1% / 6%);
--sl-shadow-small: 0 1px 2px hsl(240 3.8% 46.1% / 12%);
--sl-shadow-medium: 0 2px 4px hsl(240 3.8% 46.1% / 12%);
--sl-shadow-large: 0 2px 8px hsl(240 3.8% 46.1% / 12%);
--sl-shadow-x-large: 0 4px 16px hsl(240 3.8% 46.1% / 12%);


Expression parsed error when using hidden trait

Version
0.5.6
Reproduction JSON schema
{
  "version": "sunmao/v1",
  "kind": "Application",
  "metadata": {
    "name": "some App"
  },
  "spec": {
    "components": [
      {
        "id": "button2",
        "type": "chakra_ui/v1/button",
        "properties": {
          "text": {
            "raw": "text",
            "format": "plain"
          },
          "isLoading": false,
          "colorScheme": "blue"
        },
        "traits": [
          {
            "type": "core/v1/event",
            "properties": {
              "handlers": [
                {
                  "type": "onClick",
                  "componentId": "isHidden",
                  "method": {
                    "name": "setValue",
                    "parameters": {
                      "key": "value",
                      "value": "false"
                    }
                  },
                  "disabled": false,
                  "wait": {
                    "type": "delay",
                    "time": 0
                  }
                }
              ]
            }
          }
        ]
      },
      {
        "id": "box1",
        "type": "chakra_ui/v1/box",
        "properties": {
          "w": 40,
          "h": 40,
          "minW": "",
          "maxW": "",
          "minH": "",
          "maxH": "",
          "m": "",
          "p": "",
          "overflow": "",
          "bg": "",
          "bgColor": "",
          "opacity": "",
          "bgGradient": "",
          "bgClip": "",
          "bgImage": "",
          "bgSize": "",
          "bgPosition": "",
          "bgRepeat": "",
          "bgAttachment": "",
          "boxShadow": "",
          "border": "1px solid black",
          "borderRadius": ""
        },
        "traits": [
          {
            "type": "core/v1/style",
            "properties": {
              "styles": []
            }
          },
          {
            "type": "core/v1/hidden",
            "properties": {
              "hidden": "{{isHidden.value}}"
            }
          }
        ]
      },
      {
        "id": "input1",
        "type": "chakra_ui/v1/input",
        "properties": {
          "variant": "outline",
          "placeholder": "{{input1.value}}",
          "size": "md",
          "focusBorderColor": "",
          "isDisabled": false,
          "isRequired": false,
          "defaultValue": ""
        },
        "traits": [
          {
            "type": "core/v1/slot",
            "properties": {
              "container": {
                "id": "box1",
                "slot": "content"
              }
            }
          }
        ]
      },
      {
        "id": "isHidden",
        "type": "core/v1/dummy",
        "properties": {},
        "traits": [
          {
            "type": "core/v1/state",
            "properties": {
              "key": "value",
              "initialValue": "true"
            }
          }
        ]
      }
    ]
  }
}

Steps to reproduce

Click the button.

What is expected?
The expression parsed correctly.
What is actually happening?
The expression parsed error and the input display a wrong placeholder at a moment when it shows.

What is the expected behavior?

What is the expected behavior?

The component's states should be inited before the component is mounted.

Maybe in this situation visually hidden is the correct solution?

Using the visually could avoid this error from happening, but doesn't fix the problem totally, because it isn't only happening in the hidden trait. If some components render their slots components depending on some conditions, it also would happen. Thus I think we should fix the problem in the runtime.

The component's states should be inited before the component is mounted.

But what should be init if a component should not render at all? Actually, we don't have a init process for component. A component's logic only run when it is going to render.

Now if a component is hidden, its id will no longer exist in store.


End to end tests for critical user journeys

[ ] Create Account
[ ] Approve App-specific Key
[ ] Send Money
[ ] Recover Account

Closing in favor of #505


E
E           This typically means that you attempted to use functionality that needed
E           the current application. To solve this, set up an application context
E           with app.app_context(). See the documentation for more information.
.tox/py37/lib/python3.7/site-packages/werkzeug/local.py:513: RuntimeError

Test-only, +1

I am closing this in favor of #78.  Thank you for the PR anyway!


fix pretraining_ on odd datasets

Description
I'm interested in using axolotl to pretrain and then finetune on a dataset which I have on HF.

Fixes an issue I experienced because the training script expects pretraining to have a split named "train" and single column named "text". I propose adding split and name to the PretrainingDataset parser and a new text_column field.

The load_dataset(path, streaming=True) used in pretraining currently returns features: None or features: Unknown, so I propose retrieving the first record to get column names (this is later passed to remove_columns).

As an alternative config change, I could see using SFTDataset and removing the separate PretrainingDataset type
How has this been tested?
Output YAML, ran training script in CoLab notebook
Sample dataset with one column named "Comment"
pretraining_dataset:
  - path: urkopa/comments-lv
    split: train
    text_column: Comment
    type: pretrain

My dataset where each split has a different schema so I need to specify split and name
pretraining_dataset:
  - path: monsoon-nlp/greenbeing-proteins
    split: pretraining
    text_column: sequence
    name: pretraining
    type: pretrain

Hm, is it possible to add unit tests for this?


fix: downgrade to spark3.1

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

/azp run

Codecov Report

Merging #1646 (ba79a4e) into spark3.1 (7abf839) will decrease coverage by 83.92%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           spark3.1   #1646       +/-   ##
============================================
- Coverage     85.83%   1.91%   -83.93%
============================================
  Files           272     272
  Lines         14230   14230
  Branches        767     767
============================================
- Hits          12215     272    -11943
- Misses         2015   13958    +11943

Impacted Files
Coverage Δ

...m/src/main/scala/com/microsoft/lightgbm/SWIG.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...cala/org/apache/spark/ml/NamespaceInjections.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/com/microsoft/azure/synapse/ml/stages/udfs.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...m/microsoft/azure/synapse/ml/vw/VectorZipper.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...rg/apache/spark/injections/BlockManagerUtils.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...m/microsoft/azure/synapse/ml/codegen/CodeGen.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

.../microsoft/azure/synapse/ml/io/binary/Binary.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

.../microsoft/azure/synapse/ml/param/ModelParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

.../microsoft/azure/synapse/ml/param/UDPyFParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...microsoft/azure/synapse/ml/codegen/Wrappable.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 252 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion?


Upgrade dependencies

Towards https://github.com/giantswarm/giantswarm/issues/21301

Tested on ginger


New version: UweSieber.UsbTreeView version 4.0.6

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Resolve https://github.com/microsoft/winget-pkgs/issues/144927

Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！


After ver1.7.0 ndt_localizer desn't run on GPU

In ver.1.6.3,  ndt_localizer runs on GPU.
But after version 1.7.0 ndt_localizer doesn't run on the GPU.
CUDA version is 8.0 and 9.2 .
How can it run on GPU?
This screenshot is ver.1.10.0 .

This is ver.1.6.3

Thanks for using Autoware and for your bug report.
Your report does not give us enough information to reproduce the bug. If we cannot reproduce it, we will be unable to find the cause and fix it. We ask that you please follow our support guidelines when making a bug report: https://github.com/autowarefoundation/autoware/wiki/Support-guidelines. Please pay particular attention to the information we ask you to provide.
If you think that this may not be a bug but is instead a problem in your use of Autoware, then consider closing this bug report and opening a topic on the Autoware Discourse category requesting help. This may get you past your problem faster. Link to your new topic from this issue so we know where to continue the discussion.

Thank you for your reply.
Information to repruduce:

Ubuntu 16.04
ROS kinetic
CUDA 8.0 and 9.2 (CUDA 10.1 could not be built)
Autoware version 1.10.0, 1.7.0 (1.6.3 is OK)

I can provide the additional information if you need.
Please provide information that this is restriction of Autoware or not.
Because I can’t judge whether this is bug or not.

Please also upload your ndt_gpu and lidar_localizer build logs.
Located in the log/latest directory.

log/latest/ndt_gpu

command.log
stderr.log
stdout.log
stdout_stderr.log
streams.log

There is no lidar_localizer directry.

Thanks. I confirmed ndt is being compiled with GPU support.
Can you please tell me

How are you compiling?
Can you please also show the output of the Autoware terminal after you launch ndt from runtime manager?

Thanks

This is screenshot after starting Localization.
The Localization is matching. I confirmed by RViz.

THanks

I couldn't test in Autoware 1.11.0, because of this issue #2202 .

Information to repruduce

Ubuntu 16.04
ROS kinetic
CUDA 8.0 and 9.2 (CUDA 10.1 could not be built)
Autoware version 1.10.0, 1.7.0 (1.6.3 is OK)

Please provide the information that this is restriction of Autoware or not.
(I can’t jduge this is bug or not)

@andoh104 This is not a bug.
The default method is CPU.
You'll need to set to GPU the NDT method.
https://github.com/autowarefoundation/autoware/blob/master/ros/src/computing/perception/localization/packages/lidar_localizer/launch/ndt_matching.launch#L4
I recommend not to use "quick start" launch files.

@amc-nu
Thank you. I understand default setting.
Could you show me how to set to GPU,  Is this OK ?
 <arg name="method_type" default="3" /> <!-- pcl_generic=0, pcl_anh=1, pcl_anh_gpu=2, pcl_openmp=3 -->
I tried this, but it seems not to run on GPU.

Thanks for using Autoware and for your question. However the issue tracker is for posting confirmed bugs and feature requests.
We ask that you please ask questions on the Autoware Discourse category following our support guidelines: https://github.com/autowarefoundation/autoware/wiki/Support-guidelines. Please pay particular attention to the information we ask you to provide.

@gbiggs
Thank you.
I found this topic on the Autoware Discourse category .
https://discourse.ros.org/t/ndt-mapping-method-types-and-parameters/8482/3
I think that since  NDT localizer on GPU has not been supported and not tested since  v1.6 , so this issue is not a bug.
Is this my understanding correct ?


Add promise.catch to Promise implementation

Would be great to have promise.catch.
see here
This is maybe somewhat related to #228

Yeah, it's related. Making promises follow ES6 means we would also have access to Promise.prototype, which can be extended for tap, value, spread, etc, but as I mentioned there, it's a breaking change.
I'll make a note there about catch


Update the visual editor wording

Update the visual text on the empty Pipeline state.
https://issues.redhat.com/browse/RHODS-8373

/lgtm


Reproducing Segmentation Results

Hi!
I am trying to reproduce the results on POTSDAM using the example command you provided:
export CUDA_VISIBLE_DEVICES=0,1,2,3 && nohup python -m code.scripts.segmentation.segmentation_twohead --mode IID --dataset Potsdam --dataset_root /home/khalil/Documents/IIC/datasets/POTSDAM --model_ind 544 --arch SegmentationNet10aTwoHead --num_epochs 4800 --lr 0.000001 --lamb_A 1.0 --lamb_B 1.0 --num_sub_heads 1 --batch_sz 60 --num_dataloaders 1 --output_k_A 36 --output_k_B 6 --gt_k 6 --input_sz 200 --half_T_side_sparse_min 0 --half_T_side_sparse_max 0 --half_T_side_dense 5  --include_rgb --no_sobel --jitter_brightness 0.1 --jitter_contrast 0.1 --jitter_saturation 0.1 --jitter_hue 0.1 --use_uncollapsed_loss --batchnorm_track > gnoded2_gpu0123_m544_r1.out &

I keep running into variations on the following output:
only got 0.44026533 4th, restarting
1.) I've tried multiple times to see if I get lucky enough to pass this catch, but every time the accuracy is too low. I understand that the initialization probably matters a lot, so is it better to restart than to continue training? Or should I comment out this check and just train for longer? How many times should I expect to have to rerun the script to be able to reproduce the results?
2.) Did you by any chance experiment with doing segmentation with more classes? The results in the paper seem to be for relatively few ground truth classes, and I was wondering if there is any hope in using this method for a dataset with 16+ ground truth classes.
Thanks for your time, and this is really superb work!

I think you have an old version of the code, that check was removed a while back.
I regret only giving point estimates in the results tables, but you should be able to run the code a few times and get close to the reported performance. In fact 45.4 was reported for that model, so 44.0 is reasonably close.
Theoretically there is no reason why it shouldn't scale to more ground truth classes. The paper was a proof of concept so we opted for fairly simple dataset settings.

Hi @khalilsarwari ,
Is your segmentation score (0.44026533) reproduced on POTSDAM stable? Can different initializations get similar scores? Will this score be obtained in the first five epochs of the experiment?
I got very fluctuating segmentation scores under different initializations.
Thanks,
Li


DBZ-3456 Timezone difference not considered in LagFromSourceInMilliseconds calculation

https://issues.redhat.com/browse/DBZ-3456

Looks like this also needs a rebase after the recent merge of PRs in the same code areas.

Looks like this also needs a rebase after the recent merge of PRs in the same code areas.

I will do it. Is it okay to force push on PRs or how do you deal with this? Also asking because I usually work with fixup commits.

Is it okay to force push on PRs or how do you deal with this?

Yes, it generally is ok to force-push to PR branches in a case like this. The only exception is the case when someone else already has pushed another commit to this PR (e.g. I sometimes do this to quickly do a small fix myself instead of commenting first). Then force-pushes should be avoided to avoid accidentally losing any work.

Also asking because I usually work with fixup commits.

+1, that's generally preferred over reworking commits and force-pushing those, as it then is easier to re-review that fix-up. We still may end up squashing into one or a smaller number of commits, on a case-by-case basis.

Squashed and applied. Thx a lot, @TAregger!