Hide hoverstate while typing in PowerToys Run

Description of the new feature / enhancement
Hiding the mouse cursor while typing in PowerToys Run would make it easier to identify which item will be activated when pressing Enter.
Currently, it is not immediately clear which of the query's result items will be activated if the mouse cursor happens to be at the position of the second item (or 3rd, etc) when PowerToys Run is invoked. This is particularly annoying when using the Window Walker extension. See video:
https://github.com/microsoft/PowerToys/assets/5112281/d0f57e30-304c-4e41-95f1-4ccf7c52ec7e
In this example, I have two Firefox windows open. When PowerToys Run opens, my mouse cursor happens to hover the second result, which highlights it, while the first result (the one selected by my typed query) is also highlighted. Even though I know the first item will be activated when I press Enter, this sometimes causes confusion, especially when there are more than two windows open.
Hiding the mouse cursor while typing (until the user moves it, of course) would prevent this.
Scenario when this would be used?
This would make it easier to select one result amongst many, in particular while using the Window Walker extension.
Supporting information
No response

Hiding the mouse cursor while typing

That's a setting you can find win Windows Mouse settings.

Thanks for the answer. I indeed have this enabled :

However PowerToys Run doesn't respect this setting. Have you tried it?

I see. Is PT Run the only exception? I can reproduce this for Windows Search, and the search bar in Windows Settings, too...

If hiding the mouse cursor isn't feasible, removing the highlight caused by the mouse hover (while typing) would also work.

If hiding the mouse cursor isn't feasible, removing the highlight caused by the mouse hover (while typing) would also work.

Or emphasizing the selected state so there is visually more differentiation between the hover and selected state?

That would work as well in my opinion!

@niels9001 think it could be a framework issue?

@niels9001 there is a color difference in WSB which would be the closest example to us but very minor.  It is "brighter" for mouse hover verse the item selected

#32763


Support Python 3.12

cascade should support Python 3.12 (and probably drop support for version less than 3.10). I think all that need to be done is to add Python 3.12 to the CI tests.

Fixed with #41.


Laravel 6 requires laravel/helpers

str_contains() and other helpers are now optional in Laravel 6. Could simply update the docs to say laravel/helpers is required for v6+.
"All str_ and array_ helpers have been moved to the new laravel/helpers Composer package and removed from the framework. If desired, you may update all calls to these helpers to use the Illuminate\Support\Str and Illuminate\Support\Arr classes. Alternatively, you can add the new laravel/helpers package to your application to continue using these helpers:
composer require laravel/helpers"
https://laravel.com/docs/6.x/upgrade#helpers

I ran into the same issue, would be good to add a notice in the documentation.
Moreover, i don't know is this could be reliable but maybe proxiing the used functions so, if Illumintate\Support\(Str|Arr) is available we use that, if not we use str_contains,...
I could submit a PR.

laravel/helpers is now included in the package as of v1.2!


Link var added

📝Changed routes:

/

(view full size)

Commit 8dba07745fbb87e00762c79a58b561c5bd489f60 (https://thelocalhost-git-feature-add-theme-switch.spences10.now.sh).


Add Global Spline Fit model

Hi, first off: Sorry again for pushing to main.
I implemented the GlobalSplineFit primary model by Dembinski et. al. Proceeding for the model can be found here and an overview of the model as well as the data can be found here.
This model is, as far as I understand it, the state-of-the-art model right now and is actually fited with real data.
Unfortunately, the model is not yet publicly available, yet, since the developers are still working on the paper. Once the paper is released, they will also release a python package. The best thing to do right now (according to Hans Dembinski) is to download the tabulated data and interpolate between the values.
Of course, this raises questions for this pull request, as it is unclear how to distribute these tabulated values and how the copyright on that will work (that's also why the Pre-Commit tests will fail).
I think shipping the .txt file with the source code is okay for now. Sadly, the website does not seem to have an api, which would permit downloading the table in an install script. The other option I can think of is to upload the table in an release as an asset and downloading that asset in the install script.
To interpolate I use scipy.interpolate.CubicSpline. Since I did not want to bloat the nice and short dependency list, I added it as an optional dependency and raise an error if scipy is not found.
Anyway, please let me know what you think about this and how I can improve this PR.
Context
For our prompt-muon analysis this model will be very interesting to test, since it does seem to produce the highest prompt-muon fluxes compared to other models.

Codecov Report
Patch coverage: 77.77% and project coverage change: +2.28 :tada:

Comparison is base (1e75f01) 97.13% compared to head (2906485) 99.42%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
+ Coverage   97.13%   99.42%   +2.28%
==========================================
  Files          12       12
  Lines         699      700       +1
==========================================
+ Hits          679      696      +17
+ Misses         20        4      -16

Impacted Files
Coverage Δ

src/simweights/_fluxes.py
95.83% <77.77%> (+16.88%)
:arrow_up:

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

@kjmeagher From my side this is ready for review. As said, the pre-commit is failing, since I do not know how to give the right license to the GSF data table.

Hi Ludwig, btw IceCube internally should have the GSF model code already.
For public code, it is an acceptable compromise to use the public tables, as you do. The tables themselves are not under any license, they are not source code. Perhaps I should nevertheless clarify under what permissions one can use the tables.
I hereby declare that the tables are available under CC BY 4.0 https://creativecommons.org/licenses/by/4.0/. Please add a license file to the package and indicate that the tables fall under that license. Scipy is a good example on how to handle code/data licensed under compatible licenses, see e.g. https://github.com/scipy/scipy/blob/main/LICENSES_bundled.txt

@HDembinski Thanks for the reply! I added the license, although I'm not sure how to give details about compatibility.
@kjmeagher Pre-commit is now failing because of the large scipy dependency, what can we do about that?

CC BY 4.0 is compatible with BSD 2-clause, in the sense that both give you similar distribution and modification rights. I chose CC BY 4.0 mainly because it guarantees attribution.


Auto generate new log file with old file backup when reaching to limit size

We should support 3 modes:

Just roll  out as current feature
When file reach to limit size, auto generate new file (old file kept)
Periodically files. Example, 1 file per day

Please have a look at these three links (two samples and doc)
https://github.com/easylogging/easyloggingpp#log-file-rotating - Log rotate by size
https://github.com/easylogging/easyloggingpp/blob/master/samples/STL/logrotate.cpp (based on std::thread) - Log rotate by time
https://github.com/easylogging/easyloggingpp/blob/master/samples/STL/logrotate-pthread.cpp (based on posix-thread)- Log rotate by time
Please let us know if you need any help or if it doesn't answer your question.

Also note, because easylogging++ is single header based, we have limitations in terms of adding support of log rotate, but we have previously considered it and provided generic functionalities so that user can do more stuffs (as oppose to just log rotate) as well as log rotate (as per samples provided in comment above)


[occm] Add version check for lb flavors support

What this PR does / why we need it:
I previously created #1160
There a version check was missing to find out if the used octavia version supports flavors already.
This would cause the controller to throw an error if a user specified a flavor-id on a loadbalancer with an old octavia version (< v2.6).
This pr creates a version check so that the flavor-id option gets ignored if the octavia version is too old
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Thank you @lingxiankong for pointing out how to create a version check.
Release note:

NONE

/assign @lingxiankong

/ok-to-test

/retest

/lgtm
/approve
Thanks!


Support DaemonSet and StatefulSet in discovery and decoration

Missing documentation (in another PR).
Addresses bug https://github.com/grafana/beyla/issues/562
We were assuming that instrumented applications were only deployed as Deployments, while they can be plain replicasets, or daemonsets or statefulsets.
This adds the following metadata fields: k8s.statefulset.name, k8s.daemonset.name and the following discovery arguments: k8s_owner_name, k8s_statefulset_name,  k8s_daemonset_name (to be documented).

Codecov Report
Attention: 30 lines in your changes are missing coverage. Please review.

Comparison is base (7c37178) 45.02% compared to head (f6fca33) 45.00%.
Report is 3 commits behind head on main.

Files
Patch %
Lines

pkg/internal/kube/owner.go
64.10%
13 Missing and 1 partial :warning:

pkg/internal/discover/watcher_kube.go
71.42%
6 Missing :warning:

pkg/internal/export/prom/prom.go
0.00%
6 Missing :warning:

pkg/internal/transform/k8s.go
81.25%
1 Missing and 2 partials :warning:

pkg/internal/kube/informer.go
88.88%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #571      +/-   ##
==========================================
- Coverage   45.02%   45.00%   -0.03%
==========================================
  Files          67       68       +1
  Lines        5664     5711      +47
==========================================
+ Hits         2550     2570      +20
- Misses       2964     2987      +23
- Partials      150      154       +4

Flag
Coverage Δ

unittests
45.00% <67.03%> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


AC devices not found :(

Hi,
I have generatesd an API token with all rights for the devices. Added it to the access token field, but it seems not to find any devices..
Am I missing something? It looks fool proof.. but it aint working (have several other plugins that do work like Adguard button, shelly etc.
no errors in the logs
{
"name": "Smartthings Plug (IK)",
"BaseURL": "https://api.smartthings.com/v1/",
"AccessToken": "1aa53268-******",
"GarageDoorMaxPoll": 40,
"platform": "HomeBridgeSmartThings"
}

Plugin Version: latest
Homebridge Version:  1.4.1
Operating System: Raspbian

Just make sure you have the access token correct.  That's all you need to do.  You can do the config from the plugin UI too to make sure you don't make a mistake.  Try using a capital 'N' for "Name".  If that doesn't work, clear your logs, set debug mode on restart Homebridge and send me the logs.

Aha while reading through the readme again... there is no support yet for AC : )
Thanks anyway!!

Hi,
Ok i'll give it a shot, though this plugin kinda worksedout-of-the-box (used the same API key)
https://github.com/0x4a616e/homebridge-smartthings-ac
I'll try yours once more and edit the capital N!

6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] Pushing Airconditioner bureau
[6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] Pushing Airconditioner Bentje
[6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] Pushing Airconditioner woonkamer
[6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] Pushing Airconditioner master bedroom
[6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] Stored all devices.
[6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] DEVICE DATA: {"deviceId":"2ac99e48-84da-6ff7-5d85-5891a1a142dc","name":"[room a/c] Samsung","label":"Airconditioner bureau","manufacturerName":"Samsung Electronics","presentationId":"DA-AC-RAC-000003","deviceManufacturerCode":"Samsung Electronics","locationId":"7d4d40c9-9f41-480f-b1e6-d25ebe3565dd","ownerId":"4b1fcb1e-d04e-b986-bf5d-98418233fad2","roomId":"17c8cad1-9688-4e79-9842-ad5583e84275","deviceTypeName":"Samsung OCF Air Conditioner","components":[{"id":"main","label":"main","capabilities":[{"id":"ocf","version":1},{"id":"switch","version":1},{"id":"airConditionerMode","version":1},{"id":"airConditionerFanMode","version":1},{"id":"fanOscillationMode","version":1},{"id":"temperatureMeasurement","version":1},{"id":"thermostatCoolingSetpoint","version":1},{"id":"relativeHumidityMeasurement","version":1},{"id":"airQualitySensor","version":1},{"id":"odorSensor","version":1},{"id":"dustSensor","version":1},{"id":"veryFineDustSensor","version":1},{"id":"audioVolume","version":1},{"id":"remoteControlStatus","version":1},{"id":"powerConsumptionReport","version":1},{"id":"demandResponseLoadControl","version":1},{"id":"refresh","version":1},{"id":"execute","version":1},{"id":"custom.spiMode","version":1},{"id":"custom.thermostatSetpointControl","version":1},{"id":"custom.airConditionerOptionalMode","version":1},{"id":"custom.airConditionerTropicalNightMode","version":1},{"id":"custom.autoCleaningMode","version":1},{"id":"custom.deviceReportStateConfiguration","version":1},{"id":"custom.energyType","version":1},{"id":"custom.dustFilter","version":1},{"id":"custom.veryFineDustFilter","version":1},{"id":"custom.deodorFilter","version":1},{"id":"custom.electricHepaFilter","version":1},{"id":"custom.doNotDisturbMode","version":1},{"id":"custom.periodicSensing","version":1},{"id":"custom.airConditionerOdorController","version":1},{"id":"custom.ocfResourceVersion","version":1},{"id":"custom.disabledCapabilities","version":1},{"id":"samsungce.deviceIdentification","version":1},{"id":"samsungce.dustFilterAlarm","version":1},{"id":"samsungce.driverVersion","version":1},{"id":"samsungce.softwareUpdate","version":1},{"id":"samsungce.selfCheck","version":1},{"id":"samsungce.individualControlLock","version":1}],"categories":[{"name":"AirConditioner","categoryType":"manufacturer"}]}],"createTime":"2021-05-12T13:26:19.417Z","profile":{"id":"11fb1fee-8d52-3ce0-895c-bd2264ecbb1b"},"ocf":{"ocfDeviceType":"oic.d.airconditioner","name":"[room a/c] Samsung","specVersion":"core.1.1.0","verticalDomainSpecVersion":"res.1.1.0,sh.1.1.0","manufacturerName":"Samsung Electronics","modelNumber":"ARTIK051_PRAC_20K|10217841|60010514001411010200001000000000","platformVersion":"DAWIT 2.0","platformOS":"TizenRT 1.0 + IPv6","hwVersion":"ARTIK051","firmwareVersion":"ARTIK051_PRAC_20K_11220503","vendorId":"DA-AC-RAC-000003","vendorResourceClientServerVersion":"ARTIK051 Release 2.211222.1","lastSignupTime":"2021-05-12T13:26:11.715551Z"},"type":"OCF","restrictionTier":0,"allowed":[]}
[6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] DEVICE DATA: {"deviceId":"bbdb8eaa-c244-4109-743f-c18eebd24110","name":"[room a/c] Samsung","label":"Airconditioner Bentje","manufacturerName":"Samsung Electronics","presentationId":"DA-AC-RAC-000003","deviceManufacturerCode":"Samsung Electronics","locationId":"7d4d40c9-9f41-480f-b1e6-d25ebe3565dd","ownerId":"4b1fcb1e-d04e-b986-bf5d-98418233fad2","roomId":"89f45eab-dcce-4ac1-a74f-5574e5d3cb8b","deviceTypeName":"Samsung OCF Air Conditioner","components":[{"id":"main","label":"main","capabilities":[{"id":"ocf","version":1},{"id":"switch","version":1},{"id":"airConditionerMode","version":1},{"id":"airConditionerFanMode","version":1},{"id":"fanOscillationMode","version":1},{"id":"temperatureMeasurement","version":1},{"id":"thermostatCoolingSetpoint","version":1},{"id":"relativeHumidityMeasurement","version":1},{"id":"airQualitySensor","version":1},{"id":"odorSensor","version":1},{"id":"dustSensor","version":1},{"id":"veryFineDustSensor","version":1},{"id":"audioVolume","version":1},{"id":"remoteControlStatus","version":1},{"id":"powerConsumptionReport","version":1},{"id":"demandResponseLoadControl","version":1},{"id":"refresh","version":1},{"id":"execute","version":1},{"id":"custom.spiMode","version":1},{"id":"custom.thermostatSetpointControl","version":1},{"id":"custom.airConditionerOptionalMode","version":1},{"id":"custom.airConditionerTropicalNightMode","version":1},{"id":"custom.autoCleaningMode","version":1},{"id":"custom.deviceReportStateConfiguration","version":1},{"id":"custom.energyType","version":1},{"id":"custom.dustFilter","version":1},{"id":"custom.veryFineDustFilter","version":1},{"id":"custom.deodorFilter","version":1},{"id":"custom.electricHepaFilter","version":1},{"id":"custom.doNotDisturbMode","version":1},{"id":"custom.periodicSensing","version":1},{"id":"custom.airConditionerOdorController","version":1},{"id":"custom.ocfResourceVersion","version":1},{"id":"custom.disabledCapabilities","version":1},{"id":"samsungce.deviceIdentification","version":1},{"id":"samsungce.dustFilterAlarm","version":1},{"id":"samsungce.driverVersion","version":1},{"id":"samsungce.softwareUpdate","version":1},{"id":"samsungce.selfCheck","version":1},{"id":"samsungce.individualControlLock","version":1}],"categories":[{"name":"AirConditioner","categoryType":"manufacturer"}]}],"createTime":"2021-05-12T13:28:19.525Z","profile":{"id":"11fb1fee-8d52-3ce0-895c-bd2264ecbb1b"},"ocf":{"ocfDeviceType":"oic.d.airconditioner","name":"[room a/c] Samsung","specVersion":"core.1.1.0","verticalDomainSpecVersion":"res.1.1.0,sh.1.1.0","manufacturerName":"Samsung Electronics","modelNumber":"ARTIK051_PRAC_20K|10217841|60010514001411010200001000000000","platformVersion":"DAWIT 2.0","platformOS":"TizenRT 1.0 + IPv6","hwVersion":"ARTIK051","firmwareVersion":"ARTIK051_PRAC_20K_11220503","vendorId":"DA-AC-RAC-000003","vendorResourceClientServerVersion":"ARTIK051 Release 2.211222.1","lastSignupTime":"2021-05-12T13:28:15.762084Z"},"type":"OCF","restrictionTier":0,"allowed":[]}
[6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] DEVICE DATA: {"deviceId":"ccc769ab-97e6-4da8-d133-40b24bbcb54d","name":"[room a/c] Samsung","label":"Airconditioner woonkamer","manufacturerName":"Samsung Electronics","presentationId":"DA-AC-RAC-000003","deviceManufacturerCode":"Samsung Electronics","locationId":"7d4d40c9-9f41-480f-b1e6-d25ebe3565dd","ownerId":"4b1fcb1e-d04e-b986-bf5d-98418233fad2","roomId":"f2f0eebc-5cd6-4b90-8bb6-c42e0d3204da","deviceTypeName":"Samsung OCF Air Conditioner","components":[{"id":"main","label":"main","capabilities":[{"id":"ocf","version":1},{"id":"switch","version":1},{"id":"airConditionerMode","version":1},{"id":"airConditionerFanMode","version":1},{"id":"fanOscillationMode","version":1},{"id":"temperatureMeasurement","version":1},{"id":"thermostatCoolingSetpoint","version":1},{"id":"relativeHumidityMeasurement","version":1},{"id":"airQualitySensor","version":1},{"id":"odorSensor","version":1},{"id":"dustSensor","version":1},{"id":"veryFineDustSensor","version":1},{"id":"audioVolume","version":1},{"id":"remoteControlStatus","version":1},{"id":"powerConsumptionReport","version":1},{"id":"demandResponseLoadControl","version":1},{"id":"refresh","version":1},{"id":"execute","version":1},{"id":"custom.spiMode","version":1},{"id":"custom.thermostatSetpointControl","version":1},{"id":"custom.airConditionerOptionalMode","version":1},{"id":"custom.airConditionerTropicalNightMode","version":1},{"id":"custom.autoCleaningMode","version":1},{"id":"custom.deviceReportStateConfiguration","version":1},{"id":"custom.energyType","version":1},{"id":"custom.dustFilter","version":1},{"id":"custom.veryFineDustFilter","version":1},{"id":"custom.deodorFilter","version":1},{"id":"custom.electricHepaFilter","version":1},{"id":"custom.doNotDisturbMode","version":1},{"id":"custom.periodicSensing","version":1},{"id":"custom.airConditionerOdorController","version":1},{"id":"custom.ocfResourceVersion","version":1},{"id":"custom.disabledCapabilities","version":1},{"id":"samsungce.deviceIdentification","version":1},{"id":"samsungce.dustFilterAlarm","version":1},{"id":"samsungce.driverVersion","version":1},{"id":"samsungce.softwareUpdate","version":1},{"id":"samsungce.selfCheck","version":1},{"id":"samsungce.individualControlLock","version":1}],"categories":[{"name":"AirConditioner","categoryType":"manufacturer"}]}],"createTime":"2021-05-12T13:23:20.840Z","profile":{"id":"11fb1fee-8d52-3ce0-895c-bd2264ecbb1b"},"ocf":{"ocfDeviceType":"oic.d.airconditioner","name":"[room a/c] Samsung","specVersion":"core.1.1.0","verticalDomainSpecVersion":"res.1.1.0,sh.1.1.0","manufacturerName":"Samsung Electronics","modelNumber":"ARTIK051_PRAC_20K|10217841|60010532001411010200001000000000","platformVersion":"DAWIT 2.0","platformOS":"TizenRT 1.0 + IPv6","hwVersion":"ARTIK051","firmwareVersion":"ARTIK051_PRAC_20K_11220503","vendorId":"DA-AC-RAC-000003","vendorResourceClientServerVersion":"ARTIK051 Release 2.211222.1","lastSignupTime":"2021-05-12T13:23:13.762060Z"},"type":"OCF","restrictionTier":0,"allowed":[]}
[6/17/2022, 6:20:01 PM] [HomeBridgeSmartThings] DEVICE DATA: {"deviceId":"19035907-cc3c-4857-bd41-4568cebe9ffa","name":"[room a/c] Samsung","label":"Airconditioner master bedroom","manufacturerName":"Samsung Electronics","presentationId":"DA-AC-RAC-000003","deviceManufacturerCode":"Samsung Electronics","locationId":"7d4d40c9-9f41-480f-b1e6-d25ebe3565dd","ownerId":"4b1fcb1e-d04e-b986-bf5d-98418233fad2","roomId":"34cededf-3f89-4fe9-939a-d9fd42736a3f","deviceTypeName":"Samsung OCF Air Conditioner","components":[{"id":"main","label":"main","capabilities":[{"id":"ocf","version":1},{"id":"switch","version":1},{"id":"airConditionerMode","version":1},{"id":"airConditionerFanMode","version":1},{"id":"fanOscillationMode","version":1},{"id":"temperatureMeasurement","version":1},{"id":"thermostatCoolingSetpoint","version":1},{"id":"relativeHumidityMeasurement","version":1},{"id":"airQualitySensor","version":1},{"id":"odorSensor","version":1},{"id":"dustSensor","version":1},{"id":"veryFineDustSensor","version":1},{"id":"audioVolume","version":1},{"id":"remoteControlStatus","version":1},{"id":"powerConsumptionReport","version":1},{"id":"demandResponseLoadControl","version":1},{"id":"refresh","version":1},{"id":"execute","version":1},{"id":"custom.spiMode","version":1},{"id":"custom.thermostatSetpointControl","version":1},{"id":"custom.airConditionerOptionalMode","version":1},{"id":"custom.airConditionerTropicalNightMode","version":1},{"id":"custom.autoCleaningMode","version":1},{"id":"custom.deviceReportStateConfiguration","version":1},{"id":"custom.energyType","version":1},{"id":"custom.dustFilter","version":1},{"id":"custom.veryFineDustFilter","version":1},{"id":"custom.deodorFilter","version":1},{"id":"custom.electricHepaFilter","version":1},{"id":"custom.doNotDisturbMode","version":1},{"id":"custom.periodicSensing","version":1},{"id":"custom.airConditionerOdorController","version":1},{"id":"custom.ocfResourceVersion","version":1},{"id":"custom.disabledCapabilities","version":1},{"id":"samsungce.deviceIdentification","version":1},{"id":"samsungce.dustFilterAlarm","version":1},{"id":"samsungce.driverVersion","version":1},{"id":"samsungce.softwareUpdate","version":1},{"id":"samsungce.selfCheck","version":1},{"id":"samsungce.individualControlLock","version":1}],"categories":[{"name":"AirConditioner","categoryType":"manufacturer"}]}],"createTime":"2021-05-12T13:24:50.410Z","profile":{"id":"11fb1fee-8d52-3ce0-895c-bd2264ecbb1b"},"ocf":{"ocfDeviceType":"oic.d.airconditioner","name":"[room a/c] Samsung","specVersion":"core.1.1.0","verticalDomainSpecVersion":"res.1.1.0,sh.1.1.0","manufacturerName":"Samsung Electronics","modelNumber":"ARTIK051_PRAC_20K|10217841|60010514001411010200001000000000","platformVersion":"DAWIT 2.0","platformOS":"TizenRT 1.0 + IPv6","hwVersion":"ARTIK051","firmwareVersion":"ARTIK051_PRAC_20K_11220503","vendorId":"DA-AC-RAC-000003","vendorResourceClientServerVersion":"ARTIK051 Release 2.211222.1","lastSignupTime":"2021-05-12T13:24:43.635030Z"},"type":"OCF","restrictionTier":0,"allowed":[]}

I don't support airconditioners.  Sorry.  I'll look to add it later.

Closing


fix(stack) normalize stack name EE-1701

I still think Portainer should not silently normalize-and-deploy. This is a classic input validation scenario where the user should be told that her stack name does not comply with Docker's accepted names and try again, and not deploy the stack.
I can foresee users getting angry (me included) at not noticing that their stacks are silently being renamed and not knowing why. Is very bad user experience :(


Use action-rs Actions instead

I don't know why but having most up-to-date Rust toolchain addressed #6.
This PR makes it so that we use actions-rs/toolchain@v1 which always installs the latest stable versions.
The code is mostly copied from https://github.com/marketplace/actions/rust-cargo.

Thanks for looking into this and providing a workaround @xiaochuanyu.


feat(Topology/ContinuousFunction/CompactlySupported) bundle the class of compactly supported continuous functions

give definitions of the class of compactly supported continuous functions and prove basic properties.
Motivation: This class is most natural for the domain of the Riesz-Markov-Kakutani theorem #12290
I copied Mathlib.Topology.ContinuousFunction.ZeroAtInfty and am trying to adapt it to compactly supported functions.

I removed all instance names as suggested, except those that are used later. I guess the mathlib convention has been recently changed? (I copied the most of instance names from ZeroAtInfty)

I removed the porting note on HasCompactSupport.is_zero_at_infty
"-- Porting note: move to src/topology/support.lean once the port is over", as indeed I moved it.

@sgouezel thanks to you for reviewing and guiding me! I learnt a lot in this PR.
@j-loreaux thanks for your time! Please let me know about the naming of coe_smulc above.

@yoh-tanimoto, when you're done with the comments, you should set the PR back to awaiting-review, as otherwise it doesn't show up on the queue and people won't comment on it.

Let's get this in. Thanks!
bors r+


Draggability

Alternate to #12 ...maybe:
https://github.com/desandro/draggabilly
Cool, regardless.

Used Draggabilly for in page item dragging.


For review

Versions I'm more or less happy with & willing to share [fizzbuzz, grid_printer & series]

Mailroom WIP. Donor Report working - onto new donor & Thank You form

Aha! I see how this works now. Chris - you'll see comments in Slack as well, but Mailroom is going great but still a WIP. I'm hoping to have a working version before your office hours tomorrow, storm willing.

Your mailroom seemed to be working and looked great!


Help needed: access rights issue on Synology Nas, permission denied

Hello Guys,
I  need help solving an issue with docker/handbrake on my Synology NAS 716+.
Until 3 weeeks ago docker/handbrake worked very fine on my Nas. Then I upgraded the DSM Version of the NAS to the latest build of DSM 6.1 and starting from that day I observered access rights issues in the mapped folder (the folder I linked towards handbrake from the DSM). In the meantime I upgraded again towards DSM 6.2 RC, the issue remains.
The Docker Container Handbrake iseems start normal, but as soon as I want to open a file from the mapped folder, the following error message appears:
"Could not read the contents of handbrake, Error opening directory /storage/handbrake".

The docker container is configured on the Synology DSM as follows:

The mapped folder /Volume1/NZBD has the following access rights:
(German language: "Lesen/Schreiben" = Read/Write):

I'm logged in on the Synology as "admin" to start handbrake.
What I have configured wrong and what I need to change to make handbrake work again on the Synology?
Any help would be much appreciated! Thank you.
BR, rako123

It's probably a permission mismatch.  Under which user the container is running (i.e. what is the value of USER_ID and GROUP_ID environment variables)?

Hi jlesage,
thank you for the container and your help. Very much appreciated!
The container runs under user_ID 1000 and group-ID 1000.
My used account "admin" has: (output from ssh session)
admin@DS716plus:~$ id admin
uid=1024(admin) gid=100(users) groups=100(users),101(administrators)
Best regards, rako123

So you should change the variables to match a user on Synology.  For example, if you want HandBrake to run as admin, you need to set USER_ID to 1024 and GROUP_ID to 100.

Hi jlesage,
life could be so easy.....
I found the UI in DSM/Docker where I could change the "environment" for handbrake.
With setting the uid and the gid to the user admin (1024 uid and 101 gid) it's working fine.
Thank you very much!!! Really appreciated.
BR and greetings from Germany, rako123

Great, glade to see that it's now working :)

For the next person that sees this.. I had to use these USER_ID = 1026 and GROUP_ID = 101 when my user info was:
$ id myuser
uid=1026(myuser) gid=100(users) groups=100(users),101(administrators)


this removes the "double send" of metrics.

once hwkmetrics 83 is fixed, we need to incorporate this in the release

HWKAGENT-83 is resolved, we can remove the "two messages per metric" from the agent now


Issue with uploading file using API call with Python

I am using the code provided to upload a file on dev.hume.ai, on using the UI I am able to successfully upload a file, but on copying the same code and executing it in Google colab returns Error:500.
Code:
import requests
Upload file (POST /files/upload)
response = requests.post(
"https://api.hume.ai/v0/registry/files/upload",
headers={
"X-Hume-Api-Key": apikey,
"Content-Type": "multipart/form-data"
},
files={
'file': ('test_video.mp4', open('/content/test_video.mp4', 'rb')),
},
)
print(response.json())
Entire error:
{'timestamp': '2024-04-17T10:20:33.523+00:00', 'status': 500, 'error': 'Internal Server Error', 'path': '/files/upload'}

Thanks for your question. The registry API is not currently supported by the Hume Python SDK, but the issue you are running into is related to how you set the content type in your headers. There are some content type restrictions enforced by the requests Python library.
For a workaround I would recommend following this minimal example that uses the httpx library.
import httpx

url = "https://api.hume.ai/v0/registry/files/upload"
headers = {"X-Hume-Api-Key": "<your-api-key-here>"}
files = [("file", ("test_video.mp4", open("test_video.mp4", "rb")))]
response = httpx.post(url, headers=headers, files=files)
print(response.json())


Widget value is lagging behind the actual URL

Hi, widgets need two clicks to update, the get state is lagging behind. Minimum example below, after the second selection change the selection is always one step behind.
import streamlit as st
import streamlit_permalink as stp

with st.sidebar:
    page = stp.selectbox("Page", ["a", "b", "c"], index=0, help="Select page", url_key="page")
st.write(f"Selected page: {page}")

Versions streamlit 0.1.20 streamlit-permalink 0.3.0
Currently I am solving this by keeping a "live" version of the get state in st.session_state and only actually using the get parameters on reload, instead of using streamlit-permalink.

I encountered this same issue, where I change an input value, other states are lost from the URL.
initial url = localhost:8501
* change input a
url = localhost:8501/?a=foo
* change input b
url = localhost:8501/?b=bar (expected localhost:8501/?a=foo&b=bar)

Here's a minimal working code taking radio component as an example:
import streamlit as st

def get_url(key):
    qp = st.experimental_get_query_params()
    qv = qp.get(key, None)
    if qv:
        return qv[0]
    else:
        return None

def update_url(key):
    qp = st.experimental_get_query_params()
    qp[key] = st.session_state[key]
    print('on_change:', qp[key])
    st.experimental_set_query_params(**qp)

def url_radio(label, options, key, *args, **kwargs):
    def on_change():
        update_url(key)

    qv = get_url(key)

    if key in st.session_state:
        qi = options.index(st.session_state[key])
        print('get ss:', qi)
    elif qv:
        qi = options.index(qv)
        print('get qv:', qi)
    else:
        qi = 0
        print('get def:', qi)

    return st.radio(label=label, options=options, key=key, index=qi, on_change=on_change, *args, **kwargs)

r = url_radio('My radio', ['Me', 'Mine', 'Myself'], key='myradio')

st.write(f"{r=}")

It seems streamlit==1.21.0 fixes this regression.


Single-quoted strings with [ ] in Laravel Log interpreting escape characters (\r \n)

Laravel Version
11.30.0
PHP Version
8.3.13 64bit TS
Database Driver & Version
No response
Description
When logging with single-quoted ' strings that containing escape characters like \r  and [ ], they are being interpreted in the log output. This results in unexpected behavior, such as \r being converted to a carriage return, even though single-quoted strings in PHP treat backslashes as literal characters.
Using Illuminate\Support\Facades\Log
With default logging configuration.
Steps To Reproduce
1- Download and create a Laravel 11 application project. (https://laravel.com/docs/11.x)
2- In any route, controller, or model file, log a string using single-quotes with a backslash \r and bracket [ ].
Example:
Log::info('[MyNamespace\routes\non-web\application]');
3- Check the Laravel log file.
Expected output

local.INFO: [MyNamespace\routes\non-web\application]

Actual output

local.INFO: [MyNamespace
outes
on-web\application]

I think the issue here is caused by this: https://github.com/Seldaek/monolog/blob/32e515fdc02cdafbe4593e30a9350d486b125b67/src/Monolog/Formatter/LineFormatter.php#L241
If the first character in the log is [ or { then it replaces those substrings with "\n"

Since the formatting is handled by Monolog, I don't see anything we can do on our end here. Closing this for now.

I just tested Monolog 3.8 and 3.0, and it works like a charm.
It seems some wrappers in Laravel or other libraries are affecting the logging mechanism.


llama-cpp: 2050 -> 2074

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for llama-cpp is: Port of Facebook's LLaMA model in C/C++
meta.homepage for llama-cpp is: https://github.com/ggerganov/llama.cpp/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2074 in filename of file in /nix/store/72idmdcdljl5nhnv2r866yl4awijl40a-llama-cpp-2074

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
llama-cpp
ollama

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/72idmdcdljl5nhnv2r866yl4awijl40a-llama-cpp-2074 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A llama-cpp https://github.com/r-ryantm/nixpkgs/archive/27398a3fe2be9dd665710bcc9e7b1f7966830afa.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/27398a3fe2be9dd665710bcc9e7b1f7966830afa#llama-cpp

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/72idmdcdljl5nhnv2r866yl4awijl40a-llama-cpp-2074
ls -la /nix/store/72idmdcdljl5nhnv2r866yl4awijl40a-llama-cpp-2074/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

llama-cpp
ollama

Maintainer pings
cc @dit7ya @elohmeier for testing.

Result of nixpkgs-review pr 286595 run on aarch64-darwin 1

2 packages built:

llama-cpp
ollama


Bluetooth: Cannot establish security and discover GATT when using Split LL

Describe the bug
When connecting nrf_desktop Bluetooth Peripheral and Central I noticed the following error log (on Central):
[07095681] <err> bt_keys: Failed to save keys (err -5)
After the log Central was unable to establish security and complete GATT discovery.
To Reproduce

Use nrf_desktop (application from NordicPlayground/fw-nrfconnect-nrf repository - the application uses nrf Zephyr fork).
Build and flash firmware for Central (pca10059) and Peripheral (pca10056) with Split LL selected.
Turn on the devices.
Central will automatically try to connect to Peripheral.
Observe the problems.

Expected behavior
Split LL should work without issues (like other LL).
Impact
Split LL cannot be used for Bluetooth Central (Peripherals using split LL work fine with other hosts - tested with Windows10)
Screenshots or console output
Console logs (Central):
[06327395] <inf> ble_scan: Scan started
[06327398] <inf> event_manager: e: led_event led_id:1 effect:0x3b5e4
[06327400] <inf> event_manager: e: ble_peer_search_event active
[06327404] <inf> event_manager: e: led_event led_id:1 effect:0x3b5f4
[06327407] <inf> event_manager: e: led_ready_event led_id:1 effect:0x3b5e4
[06346154] <inf> ble_scan: Filters matched. fd:cc:ef:f5:a3:68 (random) connectable
[06346163] <inf> ble_scan: Scan stopped
[06346173] <inf> event_manager: e: ble_peer_search_event inactive
[06346176] <inf> event_manager: e: led_event led_id:1 effect:0x3b5e4
[06346184] <inf> ble_scan: Connecting done
[06346189] <inf> event_manager: e: led_ready_event led_id:1 effect:0x3b5e4
[06348553] <inf> ble_state: Connected to fd:cc:ef:f5:a3:68 (random)
[06348565] <inf> event_manager: e: ble_peer_event id=0x200029bc CONNECTED
[06348569] <inf> event_manager: e: led_event led_id:1 effect:0x3b5ec
[06348574] <inf> event_manager: e: led_ready_event led_id:1 effect:0x3b5ec
[06351803] <wrn> bt_ctlr_hci: type: 0x14
[06360014] <inf> ble_state: Security with fd:cc:ef:f5:a3:68 (random) level 2
[06360021] <inf> event_manager: e: ble_peer_event id=0x200029bc SECURED
[06360026] <inf> event_manager: e: led_event led_id:1 effect:0x3b5ec
[06360030] <inf> event_manager: e: led_ready_event led_id:1 effect:0x3b5ec
[06360461] <inf> ble_state: MTU exchange done
[07095681] <err> bt_keys: Failed to save keys (err -5)
[07255841] <inf> ble_scan: Discovery in progress

Environment (please complete the following information):

Zephyr commit hash: 40175fd3bdc2771b688d67d6f29dcc7a574c30ed

Additional context

enabling ticker compatibility mode seems to solve the issue

Looks like a controller-flash access coexistence issue? -5 is -EIO and it's being returned from the settings subsystem.

@carlescufi FYI


Add feature to bind all system properties and koin properties

Add the capability to load properties defined in System.Properties() and from koin.properties file if found in classpath.
Automatic system properties binding can be disabled like this :
startContext(modulesList, false)

but by default the properties will be bond into the context

Hi @Baresse!
Why you want the library to have this?
IMHO, the library needs to stay small and focused, and all that can be easily done by hands in one place of your app have not to be included in it to save the size and the main mission of the library.

Hi @Jeevuz
Exactly for the reason you are pointing out.
The changes are really small and still focused on the library need for the properties part of the library. You will see in near future an article explaining why Koin properties are so important especially for Android developers.
Why should any Koin users have to write by hands on every projects this kind of snippet ? If you have a look at SpringBoot or micro frameworks such as Spark Java, Ktor, etc. ; everything was not that hard to write by hands, but the real magic is there is already plenty of things right out-of-the-box.
I agree with you Koin should not include too much things, but should provide as much facilities as possible around its two main features which are :

Bean injection (with a given and well mastered life-cycle) intended for Logic or services
Property binding (with a more "static" life-cycle) intended for DTO or data

For me the magic of Koin is that this is the smallest and easiest library, not all-out-of-the-box library. In fact the main reason I switched to this from dagger2 is that dagger adding more and more useless for me features. I know many devs who really need only simple injection from а DI-framework. Properties is really nice addition, it solves some problems (don't need to create separate models (in MV* meaning) for passing data or assisted injection without factories or separate scopes).
My point that many developers so tired from this all-in-one DI-frameworks, that they want something simple and focused. Me either. That is why I asking why to add this to the library.
I agree that property binding is one of main features of the library, but disagree that binding concrete properties is related to this functionality.

@Baresse check the 0.6.0 branch
@Jeevuz Binding properties is one of the last mission of Koin - we have several way to do it (system, from external files or directly from dsl)
The core system must stay simple, but properties just can be only written in DSL :/
Stay tunned

@arnaudgiuliani
I did a rebase of all the commits and change my mind for default value for SystemPropertiesBinding.
It's false by default. This way, nothing will be change for current users of Koin library.

@arnaudgiuliani after the last commit the following chain is setup :
"=>"  means "can be overridden by"
DSL props  => startContext given props => koin.properties props => System props

Ok. I put in 0.6.0


[TM] add spec for PlatformConstants

Summary
part of #24875.
Changelog
[General] [Added] - add TM spec for PlatformConstants
Test Plan
Tests + flow pass

I didn't realise when picking this up @jarvisluong It looks like it might it might have been better if I'd picked up the ios part of PlatformConstants too since its all the same module .

@sattaman right, that is fine too!

@fkgozali I've updated as requested


Deprecate older roadmap in favor of the new one

The kubescape project currently has two roadmaps:

the old one: https://github.com/kubescape/kubescape/blob/master/docs/roadmap.md
the new one: https://github.com/kubescape/project-governance/blob/main/ROADMAP.md

Recommend removal of the old roadmap or replace its content to reference the new one. It is probable that other heritage files may still exist on the primary project repo which were moved to project-governance that should be reviewed to completeness.

I forgot to remove that :(


test(e2e): added cypress and first basic test

Closes #112
Signed-off-by: Lukas Mertens<EMAIL_ADDRESS>
Stack:

#124
#121
#120
#119
#117
#113 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #124


how to create HDwallet in python for ton blockchain?

Hi!
I think you can use this modification.
https://github.com/tonfactory/tonsdk/pull/24


Multiple-assign bug in playground

This code brings up the "bug" popup in the playground:
a = b = 1
a, b = b, a

Crystal 0.19.4

Following up: I think this piece of code works now

@petehuang Nope, it gives an error. Did you try it in the playground? (crystal play)


Add a label to trigger daily CI in PR

Search before asking

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

Motivation
We could add a label like need-daily-CI, and when the label is applied to a PR, all jobs of daily CI will join in the checking sequence of this PR.
Solution
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

cc @Xuanwo IIRC you have the knowledge to implement this requirement. Would you like to take over this issue or help on sharing knowledge need to implement this feature?

Actually since we already trigger daily CI if workflow file changed, I'm thinking of whether we can implement this as simple as adding a comment line in the workflow file and change that line to trigger it in PR.
# This line is to trigger CI in pull request by changing the digest to any other random value; digest: 1096

cc @GoGim1

Actually since we already trigger daily CI if workflow file changed, I'm thinking of whether we can implement this as simple as adding a comment line in the workflow file and change that line to trigger it in PR.
# This line is to trigger CI in pull request by changing the digest to any other random value; digest: 1096

cc @GoGim1

I think it is more like a workaround rather than a solution 🤣

Fair enough. It's possible to implement this feature with label changed.


[Enhancement]: more responsive component readiness check

Is there an existing issue for enhancement?

[X] I have checked the existing issues.

What would you like to be added ?
Currently, component readiness check is executed in poll style with a poll interval, which would result a readiness delay. A watch based readiness check would be more responsive.
Why is this needed ?
No response
Additional information
No response

closed via #397


Is this project unmaintained?

Is this project no longer maintained? There are a number of pull requests and issues with no response.

It's maintained when the maintainer has time. Is there a specific issue or pull request you want resolved?

Ah! Sorry for the test for life. I was curious about #166 and #167 but they are currently failing because of an unrelated memcached issue that is causing the build to fail. That memcached issue appears to affect a couple other issues. Do you have a preferred method to resolve the build issue?

I'll take a look at the memcached issue this week. If it's easy to solve, I'll fix it, unless you have a fix already. Either way, I'll take a look at and merge your pull requests, since they are unlikely to be related to the memcached issue.

Great. Thanks. I am happy to help after you take a look. Let me know.

Memcached on TravisCI fixed with d20365b6f23a8a9ac42e66b021180c6ac2c6de2a
Looking into other pull requests now.


Practice feedback collection

I'm going to try using this issue to collect feedback for the (as of now still upcoming) "practice" tutorial.
In order to keep this compact, use reactions on the comments only. For freeform response, open a new issue.

Create a practice area

Installation

Create a project

Set up a Git repository

Open the project's website

Grant access

Check the logs

Pull the code

Fix the error reporting

Deploy the change

Open the project's website, take two

Add your name

Open the project's website, take three


git.openssl.org seems to be down.

I have been using the documented git.openssl.org method for cloning openssl into a project.
This seems to have stopped working.
The README.md still has it listed as an option:
https://github.com/openssl/openssl?tab=readme-ov-file#for-testing-and-development

A local copy of the Git Repository can be obtained by cloning it from the original OpenSSL repository using
git clone git://git.openssl.org/openssl.git

However the connection times out:
$ git ls-remote git://git.openssl.org/openssl.git HEAD
fatal: unable to connect to git.openssl.org:
git.openssl.org[0: <IP_ADDRESS>]: errno=Operation timed out
git.openssl.org[1: 2404:6800:4006:814::2013]: errno=Operation timed out

The alternative GitHub link is still working:
$ git ls-remote https://github.com/openssl/openssl.git HEAD
ca112fccdd34a8538f14ddf8c3569b8331eae357	HEAD

Do you know if the git.openssl.org link is just temporary down, or is the recommendation to switch to the GitHub link from now on?

ouch, apologies, thats old.  git.openssl.org redirects to github.com/openssl/openssl now.  that url likely hasn't been used in some time, thank you for catching it.
Will use this to update the readme


Generating icons script throws an issue

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior

Once I tried to run the generate-icons the following error appears in the terminal:

C:\Users\bened\test\node_modules\@ngneat\svg-generator\tree.js:49
                    svgContent: (0, svgo_1.optimize)(svgContent, { plugins, path: svgPath }).data,
                                                    ^

TypeError: (0 , svgo_1.optimize) is not a function
    at createTree (C:\Users\bened\test\node_modules\@ngneat\svg-generator\tree.js:49:53)
    at generateSVGIcons (C:\Users\bened\test\node_modules\@ngneat\svg-generator\generator.js:19:47)
    at Object. (C:\Users\bened\test\node_modules\@ngneat\svg-generator\index.js:9:34)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47

Expected behavior
Generate icon ts files to the expected folder.

Minimal reproduction of the problem with instructions
Generated a new angular application. Run the following command: ng add @ngneat/svg-icon
it added the following dependencies to the package.json:

{
  "dependencies": {
    "@ngneat/svg-icon": "^4.1.0",
  },
  "devDependencies": {
    "@ngneat/svg-generator": "^2.0.0"
  }
}

What is the motivation / use case for changing the behaviour?

Once I manually upgraded the svg-generator to version 4.0.0 the problem disappeared. Shouldn't the schematic install the 4.0.0 by default?
Environment

Angular version: 13.3.0

For Tooling issues:
- Node version: v16.14.2
- Platform:  Windows

Others:
- Npm version: 8.5.5

^^^
Almost carbon copy error on

Ubuntu 21
Angular version 13.2
Node version: 16.14.2
Npm version: 8.5.0

Same error :

MacOS 12.3
Angular 13.3
Node 14.17.6
NPM 7.24.0


이채윤님 커피챗2, 2024-09-12

오후 11시, google meet

사전 멘토링 discussions and answers

https://github.com/chaeyoon-lee-rae/mentoring-discussion/discussions/1


[feauture] reset cursor position

Have i nice day!
I migrated from telescope and i like behaviour, when cursor position is reset is i type something in prompt.
Will be great if i could set this ability via config.
Thank you!

This would be controlled by fzf (the binary) and not fzf-lua, you can probably do that by adding an fzf bind for change, read man fzf and see if there is an action that does what you want, you can then add it with fzf_args=--bind=change:…

This seems to do what you want:
:= require"fzf-lua".files { fzf_args = "--bind=change:first" }

You can add  fzf_args to the original setup call:
:= require"fzf-lua".setup { fzf_args = "--bind=change:first" }

Nice, it works. I tried to add this to fzf_opts. Thank you!

Nice, it works. I tried to add this to fzf_opts. Thank you!

fzf_opts["--bind"] gets overidden by when generating the bind string from keymap.fzf, technicaly you could add:
require("fzf-lua").setup({
  keymap = { fzf = ["change"] = "first" }  },
})

But since keymap.fzf doesn't merge with the defaults you'd need to add all the default binds as well.


Simplifies resolvers and updates dependencies

Many resolvers are not needed, or scoped globally, but only used for a
couple projects. In any case, the configuration was complex. This
starts over, adding the minimal repositories to get the build to pass.
This also updates certain dependencies, which in some cases makes them
available in standard repositories. These dependencies were checked to
ensure they work on JRE 7.

@abesto @jamescway @rtyler PTAL the build is still failing, but we've strangled the maven resolvers to allow it to fail faster and without twitter's repo serving up stuff already on central

:+1:
Removed code, cleaner resolvers, jcenter, me likes. I don't see any issues.


Fix autoincrement

In the current implementation, AUTO_INCREMENT on simple attributes does not work on postgres.
This PR fixes that.

Just had a look to sqlite doc, it seems auto increment is supported only on primary key columns, so gorm already supports it as mush as possible.


Add config file for interleaved frequency channels

This interleaves channels such that each physical server processes a chunk of the lower half of the observation band + a chunk of the upper half, rather than a contiguous chunk.
Updates have been made on the GPU pipeline side to (try to) ensure that output data packets are indexed with a pipeline_id which reflects this new mapping. Channel numbers are also in Xeng/beamformer output packets, and should automatically be correct, but I believe these need to be augmented with pipeline_ids for the data recorders to function correctly.

@yupinghuang if you felt the urge to recreate the test vector test with data-recorder output it would be comforting if this still comes out right, (Or, if someone teaches me how to interrogate the recorded .ms files I can try and do this)

Do the beamformer delay update code need updating? The calibration apply code will probably be fine but it's worth checking @jaycedowell
I can recreate the test vec test in 24 hours, but if you feel like it, log in as the pipeline user on calim, activate the datarecorder environment, go to /data<i>/slow/ where <i> is the calim node number, find the latest ms file, pull up ipython, and then
from casacore.tables import table
with table('<ms_file_name>') as t:
    data = t.getcol('DATA')
    autocorr = t.query('ANTENNA1=ANTENNA2').getcol('DATA')

data is a (n_baseline, n_chan, n_corr) array. so data[:,:,0] and data[:,:,3] should give you XXs and YYs for all channels.
and autocorr should be the autocorrs (n_ant, n_chan, n_corr) should anything goes wrong.

This pull request just got really serious.

Good question -- i'm guessing that the delay update and calibration loading code might need changing, but it depends if the code polls each pipeline to figure out which band it is processing, or just infers the numbers from server ID. Given that no changes were made when the band of the whole system was shifted, I'm a tiny bit optimistic everything might Just Work


Replace console.log

Is your feature request related to a problem? Please describe.
We need an alternative to console.log in the project so we don't have to repeat the code.
Describe the solution you'd like
Generate 2 new methods:

stdout - to output to console
logs - to save to file, Prometheus or OpenTelemetry

I can look at it

We could add something like this.
https://github.com/empirical-run/appwright/blob/main/src/logger.ts
For the stdout

If we use log4ts, should we store the configuration in playwright.config or in a separate file?

Yep that looks pretty cool 👍 @Niklas-Back

In fact we could handle all logging with this, we just need to add appenders

I'll start with this based on your concept in pr #88  as soon as the branch of csvtuda is merged

Cool
A sexta, 13/12/2024, 08:03, Niklas-Back @.***> escreveu:

I'll start with this based on your concept in pr #88
https://github.com/inluxc/playwright-xray/pull/88 as soon as the branch
of csvtuda is merged
—
Reply to this email directly, view it on GitHub
https://github.com/inluxc/playwright-xray/issues/84#issuecomment-2540821647,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEOX24SWTJM5SAC7GF3Q332FKIFJAVCNFSM6AAAAABSAZO7YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQHAZDCNRUG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


trace-cmd-setup fails on i915/perf_stream_paranoid file not found

On master branch running trace-cmd-setup.sh the following error is reported:
sysctl: cannot stat /proc/sys/dev/i915/perf_stream_paranoid: No such file or directory
I tried to set USE_I915_PERF to 0 and 1.
Checking out one commit before 812c8a5f43a0ffe8446494cb53fbbdcc575bc49e the script works again.
System is kernel 5.6.18-1-MANJARO, AMD GPU and Intel i7, KWinFT Wayland session.

I added a --ignore flag to sysctl in commit 0d234c6. Fixed it on my Debian Testing box, but let me know if that doesn't work for you. Thanks!

Thanks, works! :+1:


fix(action.move): moving folders

vim.fs.basename("/foo/bar/) returns an empty string. This behavior differs from the unix basename program which returns bar.
Just need to accommodate for this.

related #342 #343


Support custom header buttons layouts

Closes https://github.com/PolyMeilex/sctk-adwaita/issues/27
In this MR I've generalized the button structure and it is now possible to have custom layouts in window headers similar to what you can have in Gnome apps or classic Xorg WMs.
Obvious use case for this would be to have buttons moved to the left side (like Unity):

But other possible layout combinations should work, too:

or even something crazy like

Also should be extendable if we will (ever) have an app menu button.
I didn't have any experience in rust so far, thus feedback is more than welcomed.

found few things to improve during self review, will move to draft for a short moment

It's ready for checking now!

@PolyMeilex
Thanks for the feedback! I've made changes to the MR, should be good to go

Ok, looks great now, just one more comment that I noticed, and some more testing and this should be good to go!

Might I suggest utilizing Settings from the ashpd crate?

Sadly ashpd with zbus would probably pull in more dependencies then this whole crate. Which is a big blocker, for small decorations crate. It would probably be better fitted in winit where we could integrate it with event loop, and update settings on the fly rather than once on startup, but I'm not sure if heavy deps like zbus are welcome in winit either (I actually don't know, haven't asked around).

Thank you!


Fix compatibility variable naming

The abbreviation gt is commonly used for greater than (>), whereas greater than or equal (>=) is commonly abbreviated as ge. Libraries following this naming convention include

Python Standard Library's operator (https://docs.python.org/3/library/operator.html#operator.ge)
pandas (https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.ge.html)
numpy (https://numpy.org/doc/stable/reference/generated/numpy.ndarray.ge.html)

I suggest that we follow this naming convention.

[x] Tests added / passed
[x] Passes pre-commit run --all-files

@crusaderky: I'll simplify the code in a follow-up as suggested by @fjetter.


Dynamic Replication

Is your feature request related to a problem? Please describe.
Static replication can consume too much memory.
Currently CNR/NR set-up the replication factor at data-structure instantiation and doesn't allow it to change which is sub-optimal: as the workload changes a program might want to invest less memory in replication (at the cost of read-performance) but instead use the memory for something else.
Describe the solution you'd like
Varying replicas
[random thoughts in no-particular order of how this should be implemented]
Remove replica

Get the combiner lock on the replica (no more readers)
Make sure any future operations from threads registered with the replica we remove are going to another replica from now on

This might need an indirection table in the NodeReplicated<> struct
We also need to make sure that the Replica<> struct uses the right Context<> since the thread id that context uses are “replica-local”

Maybe the right way to do this is to have all Context allocated in the NodeReplicated<> struct in a flat array, then hand an iterator<Context> to the replicas which yields the right contexts based on current thread assignment?
Alternative: think of it as as thread re-registration (addition, removal of thread to replica)

“Deregister” the replica from the log
Deallocate the data-structure
Maybe: Drop the Replica struct itself (seems harder as there can be reader threads accessing its members simultaneously); maybe it’s actually easier to keep the replica struct if we ever want to add it again?

This would mean we need to know the max. amount of replicas upfront; easy to just set to #nodes (doesn’t make sense to have more in most cases)…
For example a thread might notice that replica is behind while we’re in the process of dropping it and call sync on it (sync will try to acquire the combiner lock if it happens after replica is dropped, should probably just return)

There might be outstanding operations in the context buffer of the threads (I think this is fine we just keep them there and apply them on the new replica we’re redirected to)
We’ll have cases where a thread is no longer local to the NUMA node but it might become the combiner and do allocation on behalf of the data-structure. Ideally these allocations should be NUMA local

We can use the existing AffinityChange interface to notify when threads have to change affinity

As an optimization: if only one replica is left, we can avoid using the log until we have a replica again
Even more optimization: if only one replica is left with one thread registered, we can just route execute and execute_mut to Dispatch directly, no need to FC or use the log…

Nice because then we’re back to single-threaded DS with no atomics in the path

Add a new replica:

We need to get a quiescent copy of the DS of some existing replica in the system

Should be fine if we hold the combiner lock
We need to make sure we remember where in the log this replica is at when we do the copy
We need to make sure we copy to memory of the right NUMA affinity

We already require Clone on the DS
Copying the DS might be very expensive (which is fine as a first

One option: While copying keep a single DS and share it between two replicas

Maybe: Log operations again between the two shared replicas

We could use copy-on-write for the data-structure (e.g., Cow<> in rust)
Might be copy on read instead too (lazy replication)?

Harder, if not impossible because we don’t have a mutable reference on reads

We need to register the replica with the log

And set our ctail to the same index of the replica we’ve copied from
We should also ensure no wrap-around in the log meanwhile / e.g., once we set the ctail the log needs to wait for the replica we’re in process of adding (and respect its ctail when deciding when it’s safe to overwrite log entries)
Dynamic membership (removing and adding replicas) with the log is a bit tricky since the log is not designed for this

It has a single atomic next field that tracks registration
The “next” field is used to check for to find the minimum completed tail (by iterating from 0..next)

Such functions now need an additional check if the replica is active or not
Maybe keep an atomic bitmask in addition to next?

Need to figure out when it’s safe to change this mask as almost all log functions are fully concurrent and code needs to vetted for new assumption that a replica might disappear/appear at any time

We need to route certain threads to the new replica

One question is do we allow registration of threads dynamically too or do keep as is where we expect all threads to register up-front

I think we can expect no new threads, then it’s just a matter of deciding which ones to re-route to the new replica
Again need to make sure the replica has the right thread contexts

API pseudo-code: adding and removing replicas
NodeReplicated {
  max_replicas: 4 // #NUMA nodes
  active: Vec<usize> // currently active replicas
  routing: HashMap<tid, rid> // maps threads to replicas
}

fn add_replica(rid: usize) -> Result {
  assert(rid < max_replicas);
  assert(!active.contains(rid), “not already active”);

  // possible thread routing policy:
  // migrates tids that were originally registered to `rid` back to execute against `rid`
  ensures(active.contains(rid));
}

fn remove_replica(rid: usize, new_tid_affinity: usize) {
  assert(rid < max_replicas);
  assert(new_tid_affinity < max_replicas);
  assert(active.contains(rid));
  assert(active.contains(new_tid_affinity));

  // route all threads registered with rid to `new_tid_affinity`
  // should it be possible to do more complex assignment?
  // then maybe we can provide a function that implements a routing
  // policy and assigns them or provide a HashMap with tid->new_rid mappings
  // and a default?

  ensures(!active.contains(rid));
  ensures(active.contains(new_tid_affinity));
  ensures(!routing.values.contains(rid));
  ensures(routing.len == old(routing).len);
}

How do we show it works
NR micro-benchmarks: measure mem consumption and read-tput, vary replicas over time
Integration with network and IO
(this is mostly future work to connect IO + network once we have these mechanism in place)

Socket for each replica:

Spawn up a new receive path each time to add a new replica
Route request to right replica
Similar framework to NR for network
Seastar: shared nothing, dpdk queue per-core

Similar but optimize for request ingress

Shuffle from IO to NR

Becomes a bottleneck if NIC is not smart about routing

FLOEM/FlexNIC from antoine

Describe alternatives you've considered
Alternative approaches

We could stop the world, delete the whole NR instance, extract the DS from the replicas and reconstruct a new NR instance

Additional context
No response

I've started work on this issue in this branch: nr-dymanic-replication


Unify centering/alignment behavior with alignment shared property

Currently:

panel uses alignment
image uses center
text uses centered

They should all use alignment and support the same values

This is mostly done - they all use alignment though not all values are supported in the same exact way. If any of these need to be fixed new issues can be open case by case


ippeveprinter on Windows converts lf to crlf

as per #181 building on Windows changes spool file line endings from lf to crlf.  This bug still there for ippeveprinter.

[master 3bbd6a1] Fix ippeveprinter on Windows (Issue #235)


feat: Add search box only view for popup mode

Coverage increased (+0.03%) to 26.354% when pulling f9161561b484495e5e2d4ff7820b942824d929c2 on simple-page into bad0d29b8b0940f2c64e9b84cf18824f59e37e3a on master.


Small fixes for advanced course

Here are the fixes we discovered during the autumn 2023 lectures of the advanced course.

For the last change (ADL stuff), I also did it in #499 and I prefer my version (looks more precise to me). Can you review it and if you're happy with it, drop yours ? Alternatively modify mine with yours of course