Moving an element only for a part of it.

Could you make the element move only for its part?
For example: moveheight = "10" - The item can be moved only if you take it over the top 10 picks.

@YuriySimakov like window header?


Launching a native app fails on Windows

PS D:\Git\dummy\native_app> flutter-tizen run
Launching lib\main.dart on Tizen rpi3 in debug mode...
Exception: tizen-manifest.xml could not be found.

Launch fails due to a bug in the archive package.
Related to https://github.com/flutter-tizen/flutter-tizen/issues/121.

The bug was fixed in archive 3.3.7 but flutter_tools still depends on 3.3.2. The workaround (#200) should be removed once the dependency is updated.


Library not available on npm

As I read the readme, it should be available under @hyperjump/json-schema-bundler, however, there exists no such library.

Sorry the README is misleading. I have not published yet. That's what I plan to call it when I am ready to publish. I got most of what I wanted to get done before publishing done yesterday. I just have one more thing I want to work out before I'm ready. I hope to have v0.1.0 out soon.

Guess we can close this now 😄


Azure Synapse Serverless support

Which version and edition of Flyway are you using?
7.7.3 (latest as of current)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using? (Type & version)
Azure Synapse Serverless/On-Demand Analytics (NOT Synapse Dedicated Server/PDW)
Version is current version.
Which operating system are you using?
Debian GNU/Linux 10 (buster)
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
Tried to run migrations using
flyway -url=jdbc:sqlserver://{synapse_ondemand_hostname}:1433;databaseName={dbname} -user={username} -password={password} -locations=filesystem:/app/synapse -mixed=true -connectRetries=60 migrate
Migrations are stored locally in /app/synapse
What did you expect to see?
Migrations to start running
What did you see instead?
Flyway stdout: b'Flyway Community Edition 7.7.3 by Redgate\n'
Flyway stderr: b'ERROR: java.lang.IllegalArgumentException: Unknown SQL Server engine edition: 11\n'

I believe the current flyway support is for the Synapse Analytics Dedicated Server version. I am trying to migrate the Synapse Serverless version. More details about this DB is here.

Hi guys, any progress with this?
Would be good to have support for Azure Synapse Serverless SQL Pool here.
I'm using Flyway Community Edition 9.0.1 by Redgate and still there same error:

ERROR: java.lang.IllegalArgumentException: Unknown SQL Server engine edition: 11

@MikielAgutu any progress on this?


Allow layout manager replacement for existing layout types

MAUI in .NET 7 introduces a static layout manager factory that users can configure in their app, to handle creating layout managers.
Layout managers are used to handle the measure/arrange logic for a layout type.
https://github.com/dotnet/maui/issues/9010
https://github.com/dotnet/maui/pull/9980

This is covered in the custom layout doc.


Actually document in the docstrings

lol

If we have a working example for one function we can split the work and chip away at the rest.

Sounds like a plan! I'll start on this next week.

There might have been an error in pol2car until I noticed it while writing docstrings: https://github.com/gotten/backtracks/commit/80cd611745f2c26487582395fb5d82c87854a3cf
Can you comment on this @wbalmer? Probably had the biggest impact for GRAVITY errors that can have a big ratio between axes.

Ah, looks like that is an error, yes, the order should be x1, x2, x1_err, x2_err. could  have affected some of our gravity runs slightly. we can merge that asap and push that and our recent changes to pypi early next week.

I'll close this for now since each function has a docstring! We will continue to revise and improve them for clarity as we update the package.


Webstorm integration fails

When upgrading from 3.3.2 to 3.4.1, Webstorm is unable to lint. It shows the following message:
ESLint failed: Cannot parse checkstyle XML

The output of checkstyle output:
The react/jsx-quotes rule is deprecated. Please use the jsx-quotes rule instead.
<?xml version="1.0" encoding="utf-8"?><checkstyle version="4.3"><file name="/home/edo/some-file.js"></file></checkstyle>

I believe the deprecation warning is the problem here.

Oh, I see the patch was a fix of another issue. And I realize it would be fixed by actually fixing the deprecated rule. Thing is, I'm extending the eslint-config-airbnb-es5 configuration. So this would mean that my Webstorm eslint integration would fail everytime one of the eslint-config-airbnb-es5 rules becomes deprecated.
Do you think there'd be another way of notifying about deprecation, while keeping the checkstyle output valid XML?


How LNURL can work with this standard?

Related:
https://github.com/fiatjaf/lnurl-rfc/issues/177

Yes I also wonder. The QR code would be much smaller if we can just create a payrequest.

As I mentioned here in the LUDS conversation, there is nothing to stop anyone who wants to add an LNURL parameter to a BIP21. BIP21 is already flexible enough to support this. Getting wallets to be compatible with this is another discussion entirely.
I'm going to close this issue since it's a little outside the scope of this website's aims.


cilium, lb: fix/improve backend selection

https://cilium.slack.com/archives/C1MATJ5U5/p1567426411053100

https://github.com/cilium/cilium/commit/c85648b24a089b2923aedc5c022017229edaeac4


Rename unsaved file should still keep the file content

VSCode Version: 1.5.3
OS Version: Windows 10

Steps to Reproduce:

Open VS Code, Create a new file name foo.js without saving file.
Type some content to the file.
Right-click on file name, choose Rename and rename it to foo.js.ts or bar.js.
The dialog box appeared warning that "Your changes will be lost".
Click Rename.
File renamed and all typed text has gone.

What I expect is the content of unsaved file should not lost in this scenario.
I don't expect any different of typing in unsaved foo.js and unsaved foo.js.ts.
It is make sense to confuse especially for Visual Studio user
that also has a warning dialog box when renaming file extension too.
But it's asking about file may unusable, so it is automatic for me to accept the
confirmation box in Visual Studio Code too.

Dialog box when rename unsaved file in Visual Studio Code 1.5.3

Dialog box when rename (saved) file in Visual Studio 2015
Note that rename saved file in Visual Studio Code does not ask for anything.

Oh. I just see that this is duplicate to #11997 .


As a developer I want to add a new satellite to the radix stack

Acceptance criteria

[Criteria 1]
[Criteria 2]

In order to ensure good quality we should (Keep the ones we need for this US)

[ ] Perform integration testing
[ ] Perform functional testing
[ ] Extra focus on usability
[ ] Test for portability
[ ] Test for accessibility
[ ] Create automated acceptance test/smoke test
[ ] Perform performance and load test
[ ] Perform user testing
[ ] Perform security testing

I think we need more information on this issue @fernandolucchesi.

Is this issue the satellites.json file you worked on @fernandolucchesi?

this issue was created before we had a clear view on how the satellites would work with radix. I'd suggest we close this since we now have #712


Following list with integers

Following list with integers:
We have implemented logic of chirp project:

A logged in user can follow and unfollow authors
A logged in user  can't follow themselves
Authors have a list of followers, this is being used to maintain following, and displayed cheeps from followers
A logged in user' s private timeline displays the user's own cheeps and the cheeps from the authors they are following
Another user's usertimeline only displays their cheeps (fx user A click on user B's timeline, only user B's cheeps is now displayed)

Amazingly written! Such grace

it looks good


Remove cli from podman compose file

I removed the cli entry from the podman-compose-test-net.yaml file.
This PR closes #1258.

It looks like this change was missed from PR #1186, which removed the CLI container from the Docker version of these files, so seems like a good change to me.


ESP32_S2 light sleep enable reboot  (IDFGH-3416)

Environment

Development Kit:      [ESP32-S2-Saola-1]
Kit version: [v1.2]
Module or chip used:  [ESP32-S2-WROOM]
IDF version (run git describe --tags to find it):  v4.2-dev-1660-g7d7521367
Build System:         [idf.py]
Compiler version (run xtensa-esp32-elf-gcc --version to find it): xtensa-esp32-elf-gcc (crosstool-NG esp-2020r1) 8.2.0
Operating System:     [Linux]
Using an IDE?: [No]
Power Supply:         [USB]

Problem Description
When running the example 'esp-idf/examples/wifi/power_save' the ESP32_S2 will boot as normal, connect to a Wi-Fi AP successfully and then reboot moments after (Less than 2 seconds) with a reset cause rst:0x10 (RTCWDT_RTC_RST). This reboot loop is continuous.
The example 'esp-idf/examples/wifi/getting_started/station' works just fine (connecting and stay connecting) proving the hardware is fine.
Expected Behavior
ESP32_S2 to enter into light sleep mode
Actual Behavior
ESP32_S2 reboots with cause rst:0x10 (RTCWDT_RTC_RST). This reboot loop is continuous.
Steps to reproduce

idf.py set-target esp32s2
idf.py menuconfig
The only settings changed are: (SSID/Password)
idf.py build

I have tried changing SSID/Passwords, WiFi listen Interval (1 and 3), all cause this issue.
Code to reproduce this issue
The line that causes the issue
#if CONFIG_FREERTOS_USE_TICKLESS_IDLE
            .light_sleep_enable = true
#endif
    };

Changing the following prevents the ESP32_S2 from rebooting, but will not allow low power mode.
 .light_sleep_enable = false

Debug Logs
After reboot
ESP-ROM:esp32s2-rc4-20191025
Build:Oct 25 2019
rst:0x10 (RTCWDT_RTC_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3ffe8100,len:0x4
load:0x3ffe8104,len:0x180c
load:0x40050000,len:0x14b0
load:0x40054000,len:0x210c
entry 0x400502dc
I (46) boot: ESP-IDF v4.2-dev-1660-g7d7521367 2nd stage bootloader
I (47) boot: compile time 20:03:00
I (47) boot: chip revision: 0
I (50) boot.esp32s2: SPI Speed      : 80MHz
I (55) boot.esp32s2: SPI Mode       : DIO
I (59) boot.esp32s2: SPI Flash Size : 2MB
I (64) boot: Enabling RNG early entropy source...
I (69) boot: Partition Table:
I (73) boot: ## Label            Usage          Type ST Offset   Length
I (80) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (88) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (95) boot:  2 factory          factory app      00 00 00010000 00100000
I (103) boot: End of partition table
I (107) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f000020 size=0x16968 ( 92520) map
I (135) esp_image: segment 1: paddr=0x00026990 vaddr=0x3ffc8b30 size=0x03334 ( 13108) load
I (139) esp_image: segment 2: paddr=0x00029ccc vaddr=0x40024000 size=0x00404 (  1028) load
0x40024000: _WindowOverflow4 at /home/wpeacock/esp/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730

I (142) esp_image: segment 3: paddr=0x0002a0d8 vaddr=0x40024404 size=0x05f40 ( 24384) load
I (157) esp_image: segment 4: paddr=0x00030020 vaddr=0x40080020 size=0x6b4f0 (439536) map
0x40080020: _stext at ??:?

I (251) esp_image: segment 5: paddr=0x0009b518 vaddr=0x4002a344 size=0x0e7e8 ( 59368) load
0x4002a344: vRingbufferReturnItem at /home/wpeacock/esp/esp-idf/components/esp_ringbuf/ringbuf.c:1269 (discriminator 2)

I (278) boot: Loaded app from partition at offset 0x10000
I (278) boot: Disabling RNG early entropy source...
I (279) cache: Instruction cache 	: size 8KB, 4Ways, cache line size 32Byte
I (286) cpu_start: Pro cpu up.
I (290) cpu_start: Application information:
I (295) cpu_start: Project name:     power_save
I (300) cpu_start: App version:      1
I (305) cpu_start: Compile time:     Jun  2 2020 20:02:28
I (311) cpu_start: ELF file SHA256:  3c8a130725baa4e7...
I (317) cpu_start: ESP-IDF:          v4.2-dev-1660-g7d7521367
I (323) cpu_start: Single core mode
I (327) heap_init: Initializing. RAM available for dynamic allocation:
I (334) heap_init: At 3FFD1628 len 0002A9D8 (170 KiB): DRAM
I (341) heap_init: At 3FFFC000 len 00003A10 (14 KiB): DRAM
I (347) cpu_start: Pro cpu start user code
I (407) spi_flash: detected chip: generic
I (408) spi_flash: flash io: dio
W (408) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (418) cpu_start: Starting scheduler on PRO CPU.
I (431) pm_esp32s2: Frequency switching config: CPU_MAX: 80, APB_MAX: 80, APB_MIN: 10, Light sleep: ENABLED
I (451) wifi:wifi driver task: 3ffda024, prio:23, stack:6656, core=0
I (451) system_api: Base MAC address is not set
I (451) system_api: read default base MAC address from EFUSE
I (461) wifi:wifi firmware version: 517093f
I (461) wifi:wifi certification version: v7.0
I (461) wifi:config NVS flash: enabled
I (471) wifi:config nano formating: disabled
I (471) wifi:Init dynamic tx buffer num: 32
I (471) wifi:Init data frame dynamic rx buffer num: 32
I (481) wifi:Init management frame dynamic rx buffer num: 32
I (481) wifi:Init management short buffer num: 32
I (491) wifi:Init static rx buffer size: 1600
I (491) wifi:Init static rx buffer num: 10
I (501) wifi:Init dynamic rx buffer num: 32
I (671) phy: phy_version: 303, c1e745d, Apr 11 2020, 14:22:04, 0, 2
I (671) wifi:enable tsf
I (671) wifi:mode : sta (7c:df:a1:00:3d:5d)
I (671) power_save: esp_wifi_set_ps().
I (671) wifi:Set ps type: 1

I (791) wifi:new:<6,0>, old:<1,0>, ap:<255,255>, sta:<6,0>, prof:1
I (791) wifi:state: init -> auth (b0)
I (811) wifi:state: auth -> assoc (0)
I (831) wifi:state: assoc -> run (10)
I (861) wifi:connected with Torah, aid = 9, channel 6, BW20, bssid = 78:8a:20:5d:7a:e9
I (861) wifi:security type: 3, phy: bgn, rssi: -46
I (861) wifi:pm start, type: 1

I (921) wifi:AP's beacon interval = 102400 us, DTIM period = 1

device reboots here
ESP-ROM:esp32s2-rc4-20191025
Build:Oct 25 2019
rst:0x10 (RTCWDT_RTC_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3ffe8100,len:0x4
load:0x3ffe8104,len:0x180c
load:0x40050000,len:0x14b0
load:0x40054000,len:0x210c
entry 0x400502dc
I (46) boot: ESP-IDF v4.2-dev-1660-g7d7521367 2nd stage bootloader
I (47) boot: compile time 20:03:00
I (47) boot: chip revision: 0
I (50) boot.esp32s2: SPI Speed      : 80MHz
I (55) boot.esp32s2: SPI Mode       : DIO
I (59) boot.esp32s2: SPI Flash Size : 2MB
I (64) boot: Enabling RNG early entropy source...
I (69) boot: Partition Table:
I (73) boot: ## Label            Usage          Type ST Offset   Length
I (80) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (88) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (95) boot:  2 factory          factory app      00 00 00010000 00100000
I (103) boot: End of partition table
I (107) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f000020 size=0x16968 ( 92520) map
I (135) esp_image: segment 1: paddr=0x00026990 vaddr=0x3ffc8b30 size=0x03334 ( 13108) load
I (139) esp_image: segment 2: paddr=0x00029ccc vaddr=0x40024000 size=0x00404 (  1028) load
0x40024000: _WindowOverflow4 at /home/wpeacock/esp/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730

I (142) esp_image: segment 3: paddr=0x0002a0d8 vaddr=0x40024404 size=0x05f40 ( 24384) load
I (157) esp_image: segment 4: paddr=0x00030020 vaddr=0x40080020 size=0x6b4f0 (439536) map

Thanks

https://esp32.com/viewtopic.php?f=10&p=56361
Wi-Fi with automatic light sleep — Not supported (WIFI-2305)

Many thanks chegewara, I missed that!

Good day
I've noticed a while ago that automatic light-sleep for WiFi has been fixed on July 10th,  according to the ESP32-S2 support status document: https://esp32.com/viewtopic.php?f=10&p=56361
Wi-Fi with automatic light sleep — Supported
And today I noticed some fresh commits so I made a fresh clone of esp-idf and rebuilt and ran the power_save example, but the ESP32s2 still reboots when light-sleep is set to true.
May I kindly ask if there is a date for when this fix will make it into the master branch?
Thank you very much in advance.
Felix

Hi @felmue, I ran the power_save example with the latest master branch locally, and didn't meet this issue. Could you please open a new issue and provide the information requested in the issue template, so that we can troubleshoot this?

Hi @igrr, thank you for replying. I appreciate it. I opened a new issue as you suggested: https://github.com/espressif/esp-idf/issues/5692
Thanks
Felix


Cannot get token

I'me trying to set up GDO, but:
$google-drive-ocamlfuse -debug googledrive
Starting application setup (label=default, base_dir=/home/user/.gdfuse).
Opening log file: /home/user/.gdfuse/default/gdfuse.log

And it hangs here, 10mn, and then
Cannot get token. Quitting.
Also tried
https://github.com/astrada/google-drive-ocamlfuse/wiki/Troubleshooting
and
https://github.com/astrada/google-drive-ocamlfuse/wiki/Authorization#alternative-authorization-mode

If you check the log file, you should see if the connection is timing out. If it's so, you can raise connect_timeout_ms in config.

gdfuse.log
[2.525512] TID=0: BEGIN: Getting tokens from GAE proxy
[2.954983] TID=0: END: gettokens not found, retrying
[2.956799] TID=0: Retrying (1/10) get_tokens after exception: Not_found
[6.034922] TID=0: END: gettokens not found, retrying
[6.036159] TID=0: Retrying (2/10) get_tokens after exception: Not_found
[8.779751] TID=0: END: gettokens not found, retrying
[8.781396] TID=0: Retrying (3/10) get_tokens after exception: Not_found
[15.293283] TID=0: END: gettokens not found, retrying
[15.294374] TID=0: Retrying (4/10) get_tokens after exception: Not_found
[23.723090] TID=0: END: gettokens not found, retrying
[23.724388] TID=0: Retrying (5/10) get_tokens after exception: Not_found
[42.361741] TID=0: END: gettokens not found, retrying
[42.363074] TID=0: Retrying (6/10) get_tokens after exception: Not_found
[75.629484] TID=0: END: gettokens not found, retrying
[75.630969] TID=0: Retrying (7/10) get_tokens after exception: Not_found
[141.235163] TID=0: END: gettokens not found, retrying
[141.236632] TID=0: Retrying (8/10) get_tokens after exception: Not_found
[270.322169] TID=0: END: gettokens not found, retrying
[270.323568] TID=0: Retrying (9/10) get_tokens after exception: Not_found
[528.547025] TID=0: END: gettokens not found, retrying
[528.548310] TID=0: Retrying (10/10) get_tokens after exception: Not_found
[1043.486967] TID=0: END: gettokens not found, retrying
[1043.488102] TID=0: Error during get_tokens after 10 attempts: Not_found

curl.log
[1042.837111] curl: header out: GET /gettokens?requestid=MC3JdiiUrUr0m82EKdJM8HMNz2915qbmbuy-xUuaG2I HTTP/1.1
User-Agent: google-drive-ocamlfuse (0.5.25) gapi-ocaml/0.2.13/Unix
Host: gd-ocaml-auth.appspot.com
Accept: */*
Accept-Encoding: identity

[1043.475475] curl: header in: HTTP/1.1 200 OK
[1043.475515] curl: header in: Cache-Control: no-cache
[1043.475525] curl: header in: Content-Type: text/plain
[1043.475534] curl: header in: X-Cloud-Trace-Context: c94fa718797f90f647197d87db4dc6a8;o=1
[1043.475541] curl: header in: Date: Tue, 06 Dec 2016 17:50:05 GMT
[1043.475561] curl: info: Server Google Frontend is not blacklisted
[1043.475568] curl: header in: Server: Google Frontend
[1043.475576] curl: header in: Content-Length: 9
[1043.475582] curl: header in: Alt-Svc: quic=":443"; ma=2592000; v="35,34"
[1043.475588] curl: header in:
[1043.475595] curl: data in: Not_found
[1043.475608] curl: info: Connection #10 to host gd-ocaml-auth.appspot.com left intact

If you are using your own client_id/client_secret you should specify them on the command line, otherwise, my app will try to connect to the standard authorization proxy and will not find any token.

Ok thanks @astrada, i've followed the Headless instructions, writed requires values on config file, but since 10mn it only shows Warning: Unexpected leaf: name=modified data_type=Scalar in GapiDriveV2Model.Labels.parse repeatedly...

Yes, that's just a warning you can ignore. It should go away with the next update, I'm going to publish in the next days.

Ok, PPA version is 0.5.25, will it be update to 0.6.x?

Yes, correct.

I had the same issue. I opened the "gdfuse.log" file, copied the long "https:/accounts.google.com/..." URL into Chrome, and was asked by Google to accept a connection to "gdfuse". Things worked from there!

I also had the same issue, with version 0.7.6.
andreas-lenze's work-around worked for me.


Ignite SqlBuilder

I want to make useful methods when I have object with unnecessary parameters (if age == null). I want to make fast and easy ignite sql query.
Add test for SqlBuilderSelfTest. refactoring - in test need to have Only test, not one of something unknown. assert need to have in testMethod, not in other class method. move SqlSelfTest in sql package for easy to find and use
example
SqlBuilder.create().more("age",10).build(PersonTest.class)

God please, you see this "pull request" and please merge in "master" branch.
Amen.


release_process: describe the tagging on different branches

Add a description of the tag naming for the release made on a few branches.

Hi @rshym,
I don't have any objections regarding this change.

Acks are added.


Cluster Interface Spec

Basic api
CreateCluster
DeleteClusters
UpgradeCluster
RollbackCluster
ResizeCluster
AddClusterNodes
DeleteClusterNodes
UpdateClusterEnv
DescribeClusters
DescribeClusterNodes
StopClusters
StartClusters
RecoverClusters
CeaseClusters

Details

"..." means any optional params

CreateCluster
params:

appId: app id
appVersion: app version
conf: conf entered by user
advanced_params: optional json params, such as env

response:

clusterId: the new create cluster id
jobId: the job id

DeleteClusters
params:

clusterIds: the cluster ids who need to be deleted
advanced_params: optional json params, such as force
response:
clusterIds: the to be deleted cluster ids
jobIds: the job ids

UpgradeCluster
params:

clusterId: the cluster id who need to be upgraded
appVersion: the new version
advanced_params: optional params
response:
clusterId: the new create cluster id
jobId: the job id

RollbackClusters
params:

clusterId: the cluster id who need to be rollback
advanced_params: optional params
response:
clusterIds: the to be rollback cluster ids
jobIds: the job ids

ResizeCluster
params:

clusterId: the cluster id who need to be resize
role: the cluster role
cpu: the cpu resource
memory: the memory resource
advanced_params: optional params, such as gpu
response:
clusterId: the resize cluster id
jobId: the job id

AddClusterNodes
params:

clusterId: the cluster id who need to be scale
role: the cluster role
nodes: the role replica num
advanced_params: optional params
response:
clusterId: the add nodes cluster id
jobId: the job id

DeleteClusterNodes
params:

clusterId: the cluster id who need to be scale
role: the cluster role
nodes: the role node ids or role replica num
advanced_params: optional params
response:
clusterId: the delete nodes cluster id
jobId: the job id

UpdateClusterEnv
params:

clusterId: the cluster id who need to be update env
env: values changed from default.
advanced_params: optional params
response:
clusterId: the update env cluster id
jobId: the job id

DescribeClusters
params:

clusterIds: the cluster ids who need to be describe
advanced_params: optional params

DescribeClusterNodes
params:

clusterNodeIds: the cluster node ids who need to be describe
advanced_params: optional params

StopClusters
params:

clusterIds: the cluster ids who need to be stoped
advanced_params: optional params, such as force
response:
clusterIds: the to be stopped cluster ids
jobIds: the job ids

StartClusters
params:

clusterIds: the cluster ids who need to be started
advanced_params: optional params
response:
clusterIds: the to be started cluster ids
jobIds: the job ids

RecoverClusters
params:

clusterIds: the cluster ids who need to be recovered
advanced_params: optional params
response:
clusterIds: the to be recovered cluster ids
jobIds: the job ids

CeaseClusters
params:

clusterIds: the cluster ids who need to be ceased
advanced_params: optional params
response:
clusterIds: the to be ceased cluster ids
jobIds: the job ids

Helm runtime Details

bold means required params, italic means optional params

CreateCluster: use helm api: InstallRelease to implement
DeleteClusters: use helm api: DeleteRelease to implement
UpgradeCluster: use helm api: UpgradeRelease to implement
RollbackClusters: use helm api: RollbackRelease to implement

RollbackClusters can rollback all UpgradeRelease operation, such as ResizeCluster, ScaleCluster, UpgradeCluster and UpdateClusterEnv
revision: the revision that need to be rollback(optional), default last operate revision

ResizeCluster: use helm api: UpgradeRelease to implement

If there are resources(may be other key) defined in Values.yaml, then this function is supported, should check from template to ensure which deployment has defined resources
Here should change resource limit automatically.

AddClusterNodes: use helm api: UpgradeRelease to implement

If there are replicas(may be other key) defined in Values.yaml, then this function is supported, should check from template to ensure which deployment has defined replicas

DeleteClusterNodes: use helm api: UpgradeRelease to implement

If there are replicas(may be other key) defined in Values.yaml, then this function is supported, should check from template to ensure which deployment has defined replicas

UpdateClusterEnv: use helm api: UpgradeRelease to implement

Shows other values defined in Values.yaml except from resources and replicas.

DescribeClusters: use kubernetes api to implement
DescribeClusterNodes: use kubernetes api to implement
StopClusters: use helm api: DeleteRelease to implement
StartClusters: use helm api: InstallRelease to implement
RecoverClusters: use helm api: InstallRelease to implement
CeaseClusters: Update status to ceased and not able to recover.

we should use helm to deploy release in order to make sure the status in tiller is consistent with the one in db.  If the chart developer provide an externalized parameter for replicate set number, the end user can scale the cluster by modifying the configuration.  And we should not support scaling if the replicate set can't be changed.

We will externalize the parameters defined in values.yaml by design and replicas should be listed in environment section if it is mutable.So I think we should remove ResizeCluster AddClusterNodes DeleteClusterNodes and invoke UpdateClusterEnv to update configuration of helm release.


Long compilation time of plutus scripts

Summary
Compilation of scripts that have many variables in scope takes a lot of time.
Steps to reproduce
Compile the following minting policy. Having more variables in scope (l20, l21 etc) causes the compilation time to double.
mkPolicy _ ctx =
  let l = length $ Ledger.txInfoInputs $ Ledger.scriptContextTxInfo ctx
      l1 = l + 1
      l2 = l + 2
      l3 = l + 3
      l4 = l + 4
      l5 = l + 5
      l6 = l + 6
      l7 = l + 7
      l8 = l + 8
      l9 = l + 9
      l10 = l + 19
      l11 = l + 11
      l12 = l + 12
      l13 = l + 13
      l14 = l + 14
      l15 = l + 15
      l16 = l + 16
      l17 = l + 17
      l18 = l + 18
      l19 = l + 19
   in -- l20 = l + 20
      l == 0
        && l1 == 0
        && l2 == 0
        && l3 == 0
        && l4 == 0
        && l5 == 0
        && l6 == 0
        && l7 == 0
        && l8 == 0
        && l9 == 0
        && l10 == 0
        && l11 == 0
        && l12 == 0
        && l13 == 0
        && l14 == 0
        && l15 == 0
        && l16 == 0
        && l17 == 0
        && l18 == 0
        && l19 == 0
-- && l20 == 0

Expected behavior
Fast compilation - non dependent on number of variables.
System info:

OS: Ubuntu
Version 21.04
plutus version: 58c093a49eb7a369865e361179d649264fc817a4

Additional context
That's a minimal scenario. Not really sure if number of variables in scope or && operator or sth else is a culprit here.
Measurements:
number of variables / compilation time
variables up to l10 uncommented  - 4s
variables up to l15 uncommented  - 17s
variables up to l16 uncommented  - 30s
variables up to l17 uncommented  - 60s
variables up to l18 uncommented  - 110s
variables up to l19 uncommented  - 230s

Any update on this one?

The fix is in progress.

Well, we're investigating a possible fix.


FormItem can add default For behavior

Generally speaking, the Reuqired and Label displayed by FormItem should be the same as the Bind property of the internal component, so it can be added as an implicit For.
一般来说FormItem显示的Reuqired和Label应当和内部组件所Bind的属性是同一个,因此可以添加为隐式For.

Please make examples with mock code to get your expectations


[DRAFT]: Add Qwik example

Added a simple Qwik example as to: https://github.com/aspect-build/bazel-examples/issues/347
The app and lib are both plain generation from the examples provided by Qwik.
The app is connected to the lib with a link in the monorepo and uses the library components.
I have not added tests yet, from what I have seen they are just using vite test for the front end tests, I suppose a UI test is needed? I am asking as the tests will be the same as a generic Vitest on the build side at least.
The dev cycle is slow at the moment or not working OK, due to: https://github.com/vitejs/vite/issues/8619
There is a start command that works, but is slow (>5s per update).
Also there is a fast (<1s)  command "devserver" that works well only for 1 library update.
For this to be resolved it seems some work on Vite is needed.

Changes are visible to end-users: no
Test plan

Covered by existing test cases

FYI @shairez in case you missed Bazel 😉

Great job guys!
Added a few comments


Blockchain Netmon

Child of: #29
The blockchain (netmon?) view is empty in my case. It should show the netmon or we choose to remove it and put the netmon on a webpage.

Already handled in detail in #29


Unnecessary destructured property reassignment causes an invalid reference

Describe the bug
Since version 1.2.136, some destructured properties from function parameters are assigned different names. When those variables are referenced later, the original name is used rather than the newly assigned name, causing a reference error at runtime.
Input code
const MyComponent = ({
  foo = new Set<string>(),
  bar
}) => {
  console.log(bar)
}

Config
{
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "tsx": true
    },
    "target": "es5",
    "loose": false,
    "minify": {
      "compress": false,
      "mangle": false
    },
    "transform": {
      "react": {
        "development": false
      }
    }
  },
  "module": {
    "type": "es6"
  },
  "isModule": true,
  "env": {
    "targets": "Chrome >= 90 or Edge >= 90 or Firefox >= 90 or Safari >= 14 or iOS >= 14 or ChromeAndroid >= 90"
  }
}

Playground link
https://play.swc.rs/?version=1.2.136&code=H4sIAAAAAAAAA0vOzysuUfCtdM7PLcjPS80rUbBV0KjmUlBIy88HMvNSyxWCU0tsikuKMvPS7TQ0dYBSSYlFXLWaCrZ2CiCFyUAT8nNS9XLy0zWAMppctQCu8HnJVAAAAA%3D%3D&config=H4sIAAAAAAAAA01OTWvDMAz9K0HnHDboCgtsUMZ6Kzv0F4hYzjxiy0huaQj577PSlez2vvT0ZvjRHroZMoqSGNIpFbxBB2XKpL2EXKCFolUqcqGlYpSBSk2QvlRrZFaCzuOo1EIMKfjJinqOWUh1szAN4yNpPYJJPUu0tBD2xYCjK42cI6XyiC41HNld7Hhed63P91D1oKc%2Fx9a1QOm6htaN9Td8fAtHat7fmtenhqX5dMM%2FdgxCnm%2BbcEaPEow%2F74yHr%2FNG7l2H5ISDu9%2FAsvwCIinN0UUBAAA%3D
Expected behavior
bar should not be reassigned to bar1, or future references should correctly reference the new assignment.
Actual behavior
bar is reassigned to bar1 and incorrectly referenced later:
const MyComponent = (param)=>{
    let { foo =new Set() , bar: bar1  } = param;
    console.log(bar);
};

Version
1.2.36
Additional context
This bug may be specific to TypeScript source-code. Only destructured properties that follow another property with a default value, when the default value uses a type argument, are reassigned. In other words, when replacing new Set<string>() with new Set() in the example code above, bar is not reassigned.

Closing as a duplicate of https://github.com/swc-project/swc/issues/3660


ci(all): Enforce using Conventional Commits

Description
Enforces the use of Conventional Commits on all PRs.
This ensures that all work can be managed using melos version, as it requires following Conventional Commits strictly.
Also makes reading PR changes easier.
Related Issues
None
Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[x] No, this is not a breaking change.

I think we need to move this check into a separate workflow, because all_plugins runs not for all commits (see ignored-paths), while we would want to be sure in all incoming commits.
Also, I see that the referenced workflow uses https://github.com/marketplace/actions/semantic-pull-request action and I would just use it directly.

@vbuberen I have addressed your points. I am unable to check if this really works as it doesn't seem to trigger if it is in a branch and not on main, so we would have to wait until merged to see it in action.

This is great


Index search results outside bbox in some cases

Index search on test data countries.fgb with bbox { minX: 112, minY: -44, maxX: 154, maxY: -11 } should result in only Australia, but includes Fiji.
First observed at https://github.com/geotools/geotools/pull/4710.

Cannot reproduce with ogrinfo, i.e ogrinfo countries.fgb countries -spat 112 -44 154 -11 only results in one feature representing Australia.


🔢 Map objects according to selected objects geometric state

Add support for the conversion of Sketchup faces to Floors, Ceiling, Roof, Wall, Topography in Revit.
Geometries should be detected as horizontal, vertical or slanted to be able to assign correct mapping method.

[x] Floor #289
[x] Default Floor #285
[x] Wall #294
[x] Default Wall #294
[ ] Ceiling
[ ] Default Ceiling
[ ] Roof
[ ] Default Roof
[ ] Column
[ ] Default Column
[ ] Beam
[ ] Default Beam

Closing this ticket as we are already tracking the Mapper issues separately.


Hello from Skopelos (Greece)!

just a hi!

Ahah! Hi! I read "Washington DC, and Skopelos"?
That looks like a great life plan :)


no predictions created

Hi,
i managed to install sleap, label,train. when visualizing during training and validation i can see good labeling, but no predictions are created. the output simple says predicted "0" frames successfully.
if run inference. it says all frames were predicted. but no new labels are created.
this was ran using linux and python.
the python version is much easier to work with, but looks like it's doing something else than the MATLAB version with the PCA and clustering. it also accepts non .h5 movies.
is there a difference between the matlab/python versions? which is the updated one?

Hi @WeissShahaf,
I'd recommend you check out the successor of LEAP -- SLEAP, available at https://sleap.ai and https://github.com/murthylab/sleap.
You'll be able to do everything you could with LEAP and more.
Cheers!


Revert "Revert "SCSS - run an update of dependencies, move to modern API""

Reverts BabylonJS/Babylon.js#15876
And fixes the css naming issue

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Reviewer - this PR has made changes to one or more package.json files.

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15884/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15884/merge/testResults/webgl2playwright/index.html

Reviewer - this PR has made changes to one or more package.json files.

This is ready to be merged, but moving to draft to allow a few more tests

Will merge this PR once playground testing and snapshots are working

Reviewer - this PR has made changes to one or more package.json files.

Reviewer - this PR has made changes to one or more package.json files.


Change the "Master" nomenclature

Description
Replace master by leader in the context of master node and by main in the context of master git branch when applicable.
Warning: Causes breaking changes in the API _cat/master => _cat/leader and cluster configuration parameters
Needs discussion and validation for these breaking changes.
Issues Resolved
Solves #472
Check List

[ x ] New functionality includes testing.

[ x ] All tests pass

[ x ] New functionality has been documented.

[ x ] New functionality has javadoc added

[ x ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I am 100% behind this PR. I know this issue was discussed prior to being made public - I thought there was even an associated issue although I can't find it.

The only concern I have with this change is that is breaks some APIs. In a perfect world, this would be a deprecation warning first, and then at a later date, after all the libraries are caught up, the change is made.
If 1.0.0 has API compatibility with Elasticsearch, it lowers the barrier of adoption for folks coming from Elasticsearch and Elasticsearch libraries. These APIs are probably not involved in many of the customers hot paths, but Elasticsearch was really good about backwards compatibility, deprecation, and I think that improves the developer experience.
Maybe there is a way to rewrite the parameter names from old to new, with deprecation warnings, and for the rest handlers, perhaps adding support for both paths, with the intent of removing in a future version.

+1 on the spirit of this PR, but I do think we should preserve backward compatibility, what's involved in doing that here?

I think a middle ground might be to have two user facing APIs: one with new terminology and the other as a deprecated terminology similar to what @dansimpson is saying. By, say, 2.0 the 'm' word is gone fully from APIs.
We document the new terminology so anyone starting off with OpenSearch never starts using the 'm' word.
Mark internal facing uses of the 'm' as a future change and no new code should contain the old terminology. Attack internal changes as the code modified.
(These are my views as a white dude in Canada - other voices are welcome to disagree and tell me I'm flat out wrong)

I agree, breaking things directly is not a good idea, Java class and variable renaming is not a problem, but we should handle both configuration options and APIs.
What's involved is duplicating the API endpoints and adding more tests to check both terminologies, and adding some warning for deprecation in the server logs when a deprecated configuration parameter is used.
So you see anything else?

Apart from my personal opinions about this very stupid policically-correct change which I already wrote here - leader is totally wrong here. ES master is not "leader" of anything. Master is meant do to some job, not lead other nodes to do something.

The master node is responsible for lightweight cluster-wide actions such as creating or deleting an index, tracking which nodes are part of the cluster, and deciding which shards to allocate to which nodes. It is important for cluster health to have a stable master node.

Please read documentation first (and context that it's used in!)  before even trying to do such stupid changes.

@sharp-pixel The configuration options are a good point. I imagine the will need to be a startup deprecation notice. My understanding that providing an alternate route for external facing APIs is not a heavy lift.

stupid -> unnecessary or incorrect or something else
I am sympathetic to @morsik saying that leader/follower may not be the right nomenclature for OpenSearch; do we have any thoughts on primary and secondary?

To me the existing nomenclature and technical utility have the following characteristics:

Authoritative decision maker
Allocation of data storage
System meta-state storage

I am sympathetic to @morsik saying that leader/follower may not be the right nomenclature for OpenSearch; do we have any thoughts on primary and secondary?

Primary comes close (1, 2) - but I have trouble separating its ties to systems where the data storage is on the primary.  It can mislead the underlying architecture since all data is on the nodes.

Leader, Governor, Delegator, Controller, Manager - All function highly on (1, 2)
Allocator, Assigner, Router - Good performance around (2), with some (3)

The problem I run into with all of these terms is that they are often used so they become suffixes to the name, {Domain}{Suffix} e.g. "HttpRequestRouter", "ThreadDelegator", "ScenarioTestLeader"
ClusterManager lands the best for me on all (1,2,3).  I think the term works for single node clusters, as a bonus.

Primary comes close (1, 2) - but I have trouble separating its ties to systems where the data storage is on the primary. It can mislead the underlying architecture since all data is on the nodes.

That's a very good point.

Technically, there is a leader election (so it is definitely 'leading' the leader eligible nodes) and it may be ok to call it leader. However, I agree the functionality of master is not well represented in that and also if we have different approach in future to decide the leader rather than election, the name leader will become inappropriate. Internally, java classes and docs around master responsibilities are named as 'cluster coordination'. So it might be best to call it 'ClusterCoordinator'? I would have preferred it to be one word, but calling it just 'Coordinator' is conflicting with coordinator nodes which is responsible for fanout.

Hi @sharp-pixel, we have got a plan to replace the non-inclusive term "master" (https://github.com/opensearch-project/OpenSearch/issues/472#issuecomment-960298995), could you please take a look at the plan and modify your PR?
To sum up,

Could you use clustermanager to replace master? We think it describes the responsibility for the "master" node.
We would like to resolve the issue #1548 as the first step, so please split your PR to have one that only replacing the "master" where the backwards compatibility won't be impacted, and those without touching APIs or settings.
Then resolving the issue #1549 as the next step to make duplicate APIs to keep the backwards compatibility.

Look forward to hearing from you soon. Thank you! 👍

Hi, I will start working on proposed changes. Thanks for constructive
input!
On Tue, Nov 23, 2021 at 7:50 PM Tianli Feng @.***>
wrote:

Hi @sharp-pixel https://github.com/sharp-pixel, we have got a plan to
replace the non-inclusive term "master" (#472 (comment)
https://github.com/opensearch-project/OpenSearch/issues/472#issuecomment-960298995),
could you please take a look at the plan and modify your PR?
To sum up,

Could you use clustermanager to replace master? We think it
describes the responsibility for the "master" node.
We would like to resolve the issue #1548
https://github.com/opensearch-project/OpenSearch/issues/1548 as the
first step, so please split your PR to have one that only replacing the
"master" where the backwards compatibility won't be impacted, and those
without touching APIs or settings.
Then resolving the issue #1549
https://github.com/opensearch-project/OpenSearch/issues/1549 as the
next step to make duplicate APIs to keep the backwards compatibility.

Look forward to hearing from you soon. Thank you! 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opensearch-project/OpenSearch/pull/564#issuecomment-977010393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDXIE3L3AHFUMIID3ZHRXTUNPPARANCNFSM4275X4CA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi @sharp-pixel. could you please share any plan or progress on this issue?


Mavlink logging refactor

This contains the code from mavlink-logging-ack-timeout-increased branch. Commits are squashed and cherry-picked on top of latest main.
Functionality verified: https://ssrc.atlassian.net/wiki/spaces/DRON/pages/811761775/Indoor+Test+Memo#14.3.2024-Misc-Testing

Verified local Saluki-v2 LMC (against pre-release 10.0.5). 3/3 logs were successfully visible in flight review tool.


Add heading level one to applicant facing program details page.

Description
This bumps up the existing h2 heading to an h1. Manually verified UI is not affected. Also enabled the accessibility test for this page.
Release notes:
Add heading level one to program details page for a11y.
Checklist

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[x] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
Fixes #3016

Codecov Report

Merging #3064 (1990fcd) into main (62f6ab6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #3064   +/-   ##
=========================================
  Coverage     77.94%   77.94%
  Complexity     2155     2155
=========================================
  Files           274      274
  Lines          8582     8582
  Branches        582      582
=========================================
  Hits           6689     6689
  Misses         1676     1676
  Partials        217      217

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


jsonschema import does not interpret defaults for objects

Bug Report
1. Minimal reproduce step (Required)
Given the following schema.json:
{
  "type": "object",
  "properties": {
    "foo": {
      "type": "object",
      "properties": {
        "bar": {
          "type": "string",
          "default": "baz"
        }
      },
      "required": ["bar"]
    }
  },
  "required": ["foo"]
}

kcl import schema.json --mode jsonschema generates:
"""
This file was generated by the KCL auto-gen tool. DO NOT EDIT.
Editing this file might prove futile when you re-run the KCL auto-gen generate command.
"""

schema Schema:
    r"""
    Schema

    Attributes
    ----------
    foo : SchemaFoo, required
    """

    foo: SchemaFoo

schema SchemaFoo:
    r"""
    SchemaFoo

    Attributes
    ----------
    bar : str, required, default is "baz"
    """

    bar: str = "baz"

And create a main.k of
Schema{}

2. What did you expect to see? (Required)
kcl run main.k schema.k produces
foo:
  bar: baz

and the contents of schema.k to be
"""
This file was generated by the KCL auto-gen tool. DO NOT EDIT.
Editing this file might prove futile when you re-run the KCL auto-gen generate command.
"""

schema Schema:
    r"""
    Schema

    Attributes
    ----------
    foo : SchemaFoo, required
    """

    foo: SchemaFoo = SchemaFoo{}

schema SchemaFoo:
    r"""
    SchemaFoo

    Attributes
    ----------
    bar : str, required, default is "baz"
    """

    bar: str = "baz"

Note the line
foo: SchemaFoo = SchemaFoo{}

where we instantiate the default version of the sub schema. If anything in the sub schema is required but has no default, the standard error will continue to throw. A suitable fix for me would be to make the default behaviour of the jsonschema import to create an instance of a schema as the default value for all schemas in a schema. Otherwise, it is not possible to use this import for creating nested structures with default values.
3. What did you see instead (Required)
kcl run main.k schema.k produces
attribute 'foo' of Schema is required and can't be None or Undefined

4. What is your KCL components version? (Required)
❯ kcl version
0.10.9-linux-amd64

First of all, I don't think it's a good idea to give any schema a default value directly. This may lead to inconsistencies: some types have a default value (schema), and some don't (other base types)
Such as bar in this example，If we remove default value, but generate a default value  for foo,
{
  "type": "object",
  "properties": {
    "foo": {
      "type": "object",
      "properties": {
        "bar": {
          "type": "string",
           # "default": "baz"  # romove this
        }
      },
      "required": ["bar"]
    }
  },
  "required": ["foo"]
}

like the following
"""
This file was generated by the KCL auto-gen tool. DO NOT EDIT.
Editing this file might prove futile when you re-run the KCL auto-gen generate command.
"""

schema Schema:
    r"""
    Schema

    Attributes
    ----------
    foo : SchemaFoo, required
    """

    foo: SchemaFoo = SchemaFoo{}

schema SchemaFoo:
    r"""
    SchemaFoo

    Attributes
    ----------
    bar : str, required, default is "baz"
    """

    bar: str

It still some error:
EvaluationError
--> /Users/zz/code/test/kcl/test1/schema.k:10:1
|
10 |     foo: SchemaFoo = SchemaFoo{}
|  attribute 'bar' of SchemaFoo is required and can't be None or Undefined
I think we need a more sound solution.

I would argue your example is the correct behaviour since "foo" is a required property and therefore the sub schema should also be adhered to. If "foo" wasn't required, then the example gets a bit more difficult because then a choice needs to be made between instantiating the default schema or not. In which case I suppose it would make sense not to.
So if a property is required and is of type object, the resulting subschema should be instantiated.
Otherwise if the behaviour needs to be opt-in, some command-line flag (and SDK option) could be given to give this behaviour.
Alternatively giving SDK access to programtically building an AST and rendering that to file would also be immensely helpful.


Default quantity unit purchase

Hi Anrolosia!
Another enhancement suggestion that i would appreciate greatly: The possibility to use "Default quantity unit purchase" instead of "Quantity unit stock" in the shopping list. For example for some items like flour i have "grams" as the stock unit and "package" as the purchase unit. That's impractical  in the shopping list as i might have 200g (one package) in the shopping list... What do you think?

Hey @anha7196
I might misunderstand something... The default quantity unit purchase is always used by default when a product is added to the shopping list (I just tested that). So in your case, you will not add 200x your flour, but only once for a package.
Could you clarify please?

I'm talking about whats viewed in the shopping list, or in the list_X_qty and sensor amount. If i add one package of flour in the grocy web shopping list, there will 500 in the shopping list in Hass as the plugin views the grams, not the packages. In the Grocy web view it will be viewed as 1 package.
Maybe this is somethoing that should be solved in the dashboard ui, but this is an example sensor in my HA now:
This is a nice example as there is two packages of coffee in one list (2) and one on another (7).
As you can see, the amounts is in grams. It would be great to have the packages available as well. And maybe the unit as well.
Kaffe
	2125 	group: Dryck
list_2_note:
list_2_qty: 1275
list_2_shop_list_id: 2475
list_7_note:
list_7_qty: 850
list_7_shop_list_id: 804
list_count: 2
location: Skafferi
product_id: 71
product_image:  [cut]
qty_in_stock: 903568
topic: shopping-list-with-grocy/products/shopping_list_with_grocy_product_v1_71/state
icon: mdi:cart
friendly_name: Kaffe

Hope this makes it clearer and that i did not miss something obvious.

Ok, got it! Let me see what I can do :)

Wow, amazingly quick!
I only had time now for a quick check, but it seems to work as intended! I'll try it out more during the weekend.

Awesome! I'll close that ticket, feel free to open a new one if you find a bug. Cheers!


Is it possible to suppoer some of markdown grammar?

Hi! Thank you for providing this fantastic program which did help me a lot on my study.
When I'm writing with markdown, I unconciously use those grammars to make my file look neater. Like using html label <font> to change face, color and size to emphasis the important. And also sometimes I need to add some graphs for easier understanding using![graph](path) .
I'm wondering if it is possible to support those features. If so, it would be great and powerful.
Thanks again for your contribution!

Raw HTML (e.g. <font>...</font>) is not supported because it is so flexible and unpredictable that may lead to incorrect node extraction. For example, it's hard to decide how the nodes wrapped in some raw HTML should be rendered.
As for graphs, do you mean to create graph nodes? I think I can expose an extensive way to extract nodes in the future.

Technically, it is not Markdown grammar, it is HTML, and an obsolete one! (<font> hand been deprecated for a long time).
Apparently, simple Markdown is supported, as show in the playground: **inline** ~~text~~ *styles* --> inline text styles
One note, though, to @gera2ld: you style the <strong> tag with a font-weight: bolder; style, but it goes from 300 to 400, and the difference is not visible, at least on Firefox and Chrome in Windows.
I suggest to use a simple font-weight: bold; instead.

HTML is already supported.


Added s2s policy for Event Notifications

Description
The auth policy isn't to be needed to configure the event notifications integration, however without it, events won't flow to the instance.
Git Issue: https://github.com/terraform-ibm-modules/terraform-ibm-scc/issues/197
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

Opened provider issue: https://github.com/IBM-Cloud/terraform-provider-ibm/issues/5890


Incoming references / foreign keys

See issue in docs
When you use an external resource, you're creating a dependency on a system that's out of your control. That external system could change the resource, remove it... Anything. In Atomic Data, these links can be very important. Part of dealing with this problem, is using IPFS #66, but that doesn't really work for data that changes over time.
Some usecases:

Before I delete a Resource, I want to know which external systems depend on this.
When I delete or edit a Resource I want external systems to be notified of this. #77

We now already have the first usecase: see which resources are referencing another one. I'll remove it from the 1.0.0 milestone since it's less urgent to actually do this in the back-end now.


Add the ability to rename/filter instances

Before using InfluxDB I was using graphite, and a powershell script to send data to graphite.
One of the useful feature this tool has was the ability to rename and filter counters based on regular expressions.
See an example in StatsToGraphite.xml, in elements <MetricsCleaning> and <Filtering>
I am facing a problem that requires the kind of same functionality on capacitor.
The problem arise when collecting IIS and ASP.NET counters, in categories W3SVC_W3WP and WAS_W3WP: the instance name is composed of the pid and the application pool name (see this doc).
So instances names varies when processes are started/recycled. So, it is impossible to filter by instance name, and we can not send this instance name as a tag, because the value will change too often.
Basically two features are needed:

the ability to filter instances based on a regular expression (better than the actual wildcard)
the ability to rename instances to remove the varying part (the pid)

My idea for now is:
Add a new <InstanceFilters> element under <CounterGroup>. Within this element, you can add multiple <Filter> element.
Each <Filter> must define a Pattern attribute with a regular expression, and an optional Replacement pattern.
During counter reading, each filter is applied to the instances returned by the performance counter.

If the filter only defines the Pattern property, then the instance name is matched against it. If it matches, then the function returns the instance name unchanged. If it doesn't it returns null.
If the filter defines both Pattern and Replacement, then the replacement is executed and the result is returned.
Each filter is executing, using the instance name returned from the previous, until all have been applied or until a filter returns a null value.)

If an instance name is null after the filters pass, the counter is ignored. Otherwise, the value is read and the process continue.
The new instance name is used when sending the value to the collector.
Configuration example:
<InstanceFilters>
  <!-- this filter will exclude all instance names where ".NET" is not present in the instance name -->
  <Filter Pattern="\.NET" />
  <!-- this filter will remove all pids from instance names for IIS apps. "1879_.NET v4.5" => ".NET v4.5" -->
  <Filter Pattern="^\d+_(.*)$" Replacement="$1" />
  <!-- this filter will replace ".NET v4.5" by "net45" -->
  <Filter Pattern="\.NET v4\.5" Replacement="net45" />
</InstanceFilters>

Possible enhancements:

possibility to share filter groups with other counter groups
possibility to define filter to specific counters
possibility to simplify the pattern when we want to match a simple string (remove the necessary \ before dots)

Do you think this feature could fit the project ? I have some prototype already, but I prefer to be sure that I am not missing anything or that I am going in the right direction.

This feature seems like a good idea, and might be good for cleaning unusual instance names, but I wouldn't use it in the use-case that you identified.
In this specific use-case, what would happen if you have multiple processes in the same apppool? For example, you have multiple instances like:
1879_.NET v4.5
1921_.NET v4.5
1922_.NET v4.5
When the data is collected, they will all be sent as the same series in Influxdb, so you will get the last-arriving value overwriting the first one. The last value could be any of the three as well. That's definitely not what you want! The correct approach would be to collect all values, and then sum/average them in Influxdb, using a continuous query.

You are right. Even if duplicates instances is often only a transition state (when app pools are recycled), I prefer not to miss them. Perhaps some code could make instances names unique again after filters have been processed, adding a counter suffix when necessary.

I am still working on this. Nothing to share yet, but still on tracks :)


fix for building on OSX against Node 6.2.2 / Julia 0.4.6

this is my fix to build NJ against latest Node/Julia releases on Mac

It looks like there is a problem with Julia 0.5, but it's likely to be an aspect of a change to Julia; I can work on that.  LGTM otherwise.  I'm interested in the effect you found of changing delete [] to delete as well.  I'm going to check how to deal with Julia 0.5 first and then merge shortly after.

So far I just confirmed npm test all passed after changing delete[], haven't go deeper in using NJ. BTW I read Julia is using uv too, and a different version than Node.js' uv are bundled together (perhaps with isolation?). I'm curious if they can be compiled with a same uv copy (so does the version), then Julia code can run cooperatively with other Node's threaded parts like fs etc. I'm new to Julia, but very delighted by its strength on computing power, to help overcome Node's shortcoming in this area, while I believe async is even more powerful to handle big data floating around. I'm really excited by the possibility that data be async-ly arranged get async-ly computed on and deducted, with no redundant copies in RAM, which NJ is offering.

I forgot to mention, I changed delete to delete[] due to a warning during build:
  CXX(target) Release/obj.target/nj/src/Call.o
../src/Call.cpp:165:10: warning: 'delete' applied to a pointer that was allocated with 'new[]'; did you mean 'delete[]'? [-Wmismatched-new-delete]
         delete jl_args;
         ^
               []
../src/Call.cpp:157:33: note: allocated with 'new[]' here
         jl_value_t **jl_args = new jl_value_t*[numArgs];
                                ^
1 warning generated.

I do think the compiler is correct so did the change. For your reference.

Your change removed the delete warning, however the following error still persists
error: cannot cast from type 'union jl_typemap_t' to
      pointer type 'jl_value_t *' (aka '_jl_value_t *')
         if(val && jl_is_function(val)) filteredNames.push_back(*s);
                   ^~~~~~~~~~~~~~~~~~~
../src/Import.cpp:14:28: note: expanded from macro 'jl_is_function'
#define jl_is_function(v) ((jl_value_t*)jl_gf_mtable(v)->defs != jl_nothing)
                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


drivers: dai: intel: ssp: Only setup mclk/bclk when it is needed by role

When SSP is consumer for FS and BCLK then it does not needs MCLK as the shifting and rate is derived form the I2S bus directly. When SSP provides FS only then the BCLK setup is not needed. When SSP provides BCLK only then both MCLK and BCLK setup is needed.
In hardware multiple SSPs share the same MCLK source, in case of one SSP port is used as clock provider while other is used as clock consumer then the consumer SSP should not need to depend on the provider SSP configuration, the ports can run in different clock rates.
In this example the consumer SSP should not try to configure and lock the MCLK frequency to some arbitrary rate (as it does not need MCLK at all) which might be different than the frequency needed by the provider port.

@kv2019i can you take a look please?

Reviews are now fine. This is now pending the two required CI checks @ujfalusi  . @nashif please comment if this is wrong.

Changes since v1:

Rebased on main

@ujfalusi needs rebase

Changes since v2:

rebased on main


add KubeCon Talks blog

Signed-off-by: Bill Mulligan<EMAIL_ADDRESS>

Still missing the keynote from Thomas


chore: reduce optimize runs

the current optimization runs is very large and results in very large contracts. i think the default should be a more reasonable number, suggesting 200 to match hardhat/truffle defaults

all fair points. fine with either direction tbh


rememberSnapFlingBehavior does not snap on desktop when using a scroll wheel

Describe the bug
rememberSnapFlingBehavior does not snap items to the center of the LazyColumn when scrolling via scroll wheel on desktop.
Affected platforms

Desktop

Versions

Kotlin version*: 1.9.0
Compose Multiplatform version*: 1.4.3
OS version(s)* (required for Desktop and iOS issues): Linux 6.4.6-100.fc37.x86_64
OS architecture (x86 or arm64): x86
JDK (for desktop issues): corretto-18.0.2

To Reproduce
Wrap this in a composable function
    val itemHeight = 48.dp
    val itemHeightModifier = modifier.height(itemHeight)
    LazyColumn(
        state = lazyListState,
        flingBehavior = rememberSnapFlingBehavior(lazyListState = lazyListState),
        modifier=itemHeightModifier.fillMaxWidth()
    ){
        items(
            5,
            key = { it }
        ){
            Text(it.toString(), modifier=itemHeightModifier)
        }
    }

Expected behavior
When scrolling through the LazyColumn and then stopping the scrolling, I expect the flingBehavior to snap the closest item to the center of the LazyColumn.
I can test this on Windows 10 later.

reproduced on Ubuntu (I guess the behaviour is OS independent).
it's likely related: https://github.com/JetBrains/compose-multiplatform/issues/3447
Here is a screen recording. Desktop is on the left (scrolling using a mouse wheel), and android is on the right (using touch gestures: dragging).
simplescreenrecorder-2023-08-04_10.29.15.webm

In the other referenced similar issue #3447 I posted a workaround that works with a pager, it can probably be adapted for your use case as well.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


How to contribute the doc

Is it enough to fix the docs/cita or need some other operations?
The #49 did not work.

It's enough. CI will deploy the website automatically.


Fix typecheck errors

Coverage remained the same at 16.272% when pulling 7154514ead5e1b320ac73af563b0357dde3feb3e on develop into 4c01d35789aa699e2916148ca9a5d6e1fd081434 on master.

Coverage decreased (-0.07%) to 16.202% when pulling 3c09d08598988feba12a12daaa03353bcb4f098a on develop into 4c01d35789aa699e2916148ca9a5d6e1fd081434 on master.


Added the 3d Portfolio

Add a three.js mini project(portfolio Website)
Please merge this pr under gssoc with particular level and level
@MohitGupta121  @pranjay-poddar
Close #3000
Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

assigned label and level under gssoc @MohitGupta121


⚠ Bofrost.fr has degraded performance

In fa6347e, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1335 ms

Resolved: Bofrost.fr performance has improved in 5ae042c after 42 minutes.


GM9 .cia dosen't work 100% of the time.

Issue
Most of the time, when you launch the .cia for GM9, it will sometimes go to a black screen after giving you the GM9 warning.
Issue present on
O2DS - Luma 8.1.1 + 11.6 (My Setup)
O2DS - Luma 8.1.1 + 11.2 (Setup of brunocar on reddit)
N3DS - Luma 8.1.1 + 11.6  (Setup of MEGA_theguy on reddit)
Release that issue originates from
Userland-1.0-GM9v1.4.3

Did you grab the chainloader from chainloader-1.0?

Yes, I have.

I think I found the cause. It tries to execute the bootloader after giving the warning. If you open the menu at the right time, then press 'Resume Godmode9'. This will actually open GodMode9

Fixed with commit 278ecd466adfd49530270f5fb52edceec9137ac7

This new commit has indeed fixed the issue.


Need more detail about format for submissions

I have something to submit, but there’s no guidance about how to format entries, and no examples yet to follow.
When people come to look at the Scribble Cookbook, what do you envision that they should see? Are they seeing all the “recipes” as code and screenshots directly in the README?
Ideally, shouldn’t the cookbook itself be a Scribble document? Perhaps also published on the package server / rendered at docs.racket-lang.org? This makes submissions a little more trouble to create and format, but also possibly easier to use.
If the latter is something you are open to, I could do a PR setting up the Scribble doc, structure, instructions etc.

Yes please!

Ideally yes, the cookbook should be a Scribble document. But how that would work is tough question since a scribble program might output any number of things ... anything from a website to a PDF document to a nice string (for other documents to incorporate).
Building those outputs might require some setup, too.
Still, any infrastructure would be better than nothing!
The easy starting point is to put each new example in its own directory with a README containing build instructions & sample output.
A shared README with screenshots is a great intermediate step.

The initial idea I had for a contribution involves not just scribble but an auxiliary CSS file (ideally a TeX file too) for style additions. So having a way to bundle all the associated files for an example is kind of a minimal requirement (which of course the sub folder + Readme approach would cover).

The initial idea I had for a contribution involves not just scribble but an auxiliary CSS file (ideally a TeX file too) for style additions. So having a way to bundle all the associated files for an example is kind of a minimal requirement (which of course the sub folder + Readme approach would cover).

That is awesome.
It would be nice to be able to embed racket code like slideshow, perhaps using Racketscript.

I'll probably submit when there's more of a skeleton of a thing to add on to. I haven’t had time to create everything from scratch in order to make a submission.


UI glitch when hovering "Stage Changes" 'plus' button

VSCode Version: 1.19.0-insider 2017-11-21
OS Version: Fedora 27 on Gnome 3.26

Steps to Reproduce:

edit a file that has no git changes so it gets added to the list of files with changes
hover the "plus" button to stage changes
see glitch

This just happens the first time you hover, if you revert the changes and add changes again you can reproduce again.

(Sorry for photo, clicking my screenshot buttons would unfocus the mouse and remove the hover)
I know this is very minor and not at all annoying but I just thought I should report.

https://github.com/Microsoft/vscode/issues/8901

Sure this is related to #8901? This seems related to https://bugs.chromium.org/p/chromium/issues/detail?id=442111


[stable/external-dns] Provider independent CA

What this PR does / why we need it:
Many organisations have their own internal CA. This chart previously only supported adding a CA chain to the ConfigMap for OpenStack Designate.
This PR makes the CA chain independent of any provider.
Which issue this PR fixes

fixes #20796

Special notes for your reviewer:
Each provider still needs it's own configuration to use the certificate, but now no longer needs CA certs mounted outside of the chart.
Checklist

[ ] DCO signed
[ ] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Thanks for the contribution, before continue, you need to sign your existing commits, you can find custom instructions in the “Details” link from the below DCO check, also you should increment the chart version in the Chart.yml according to semver:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Sorry for the wait - trying to get the branch cleaned up and a whole bunch of OpenStack Designate changes have come in and complicated things that I'm trying to simplify.

@juan131 @prydonius would you like to merge this, or close it?

/assign @sameersbn

@sameersbn @juan131 @prydonius
Shall I just close the PR?

Hi @NickLarsenNZ
Sorry I've been out a few weeks and I missed this. This chart has been deprecated and moved to https://github.com/bitnami/charts/tree/master/bitnami/external-dns. Any contribution must be done in the new repository instead.
Find more information at https://github.com/helm/charts/tree/master/stable/external-dns#this-helm-chart-is-deprecated


Add method ArrayHelper::setValue() Writes a value to the array at the specified path

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
no

Fixed issues
#6644

Writes a value to the array at the specified path.
If the array key specified path is missing, then it will be created and it is assigned an appropriate value.
If the key exists, then it will be overwritten.

you can add support for both options

Please do.

Looks good to me in general. Have you considered passing the array by reference?
Using it like this might be more useful:
$array = [ ... ];
ArrayHelper::setValue($array, 'components.db', [ ... ]);
ArrayHelper::setValue($array, 'components.cache', [ ... ]);
// ...

compared to:
$array = [ ... ];
$array = ArrayHelper::setValue($array, 'components.db', [ ... ]);
$array = ArrayHelper::setValue($array, 'components.cache', [ ... ]);
// ...

or are there good reasons/use cases where you'd want to keep the original array?

Check description on the docs/guide-ru/helper-array.md if everything is OK then I translate it in English

Merging since @cebe comments were addressed.

Merged. Thank you!

Do you think this should work for objects, as getValue does?
I've put in a dirty fix, which works on ActiveRecords, checking whether the $array has an attribute for the first $keys
//...
if (is_object($array) && $array instanceof \yii\db\ActiveRecord && $array->hasAttribute($keys[0]))
//...

Obviously could be a lot better, just wondering whether you think the core should handle it?

Not sure about it. What's use case?

Don't know. Let's wait till it's asked for i.e. when it's really required for a project.


TypeError: Cannot read property 'type' of undefined

All I am doing is this.store.findAll('mymodel') and it just throws an error.  It's a pretty basic app.  Any thoughtS

Never mind.  I had a serializers/application.js that was extending the JSON serializer and was breaking the code.


feat: add support for proper tracking in a speculative pre-rendering context

Properly wrapping sampleRUM initialization behind prerendering events.
Related Issue
Fix #101
How Has This Been Tested?
Tested against petplace.com
Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Makes sense. Thanks @ramboz.

I think this is wrong. Pageviews that are only pre-rendered, but not actually seen should be excluded in reporting, not in collection.
In addition, if we wanted to implement this behavior, it should go into rum-js, and should not be the responsibility of the site to call sampleRUM conditionally.


Tipper Done

My app is complete. Please review. Thank you for your time and consideration. /cc @codepathreview

Nice work! This pre-work is a preview of our weekly project process. Generally, weekly projects take between 5-10 hours to complete the required features and an additional 5-10 hours to complete the optional features. In general, we've seen that the more hours you log, the quicker you improve your proficiency with iOS.
The purpose of this project was to begin to explore Xcode and to get a broad overview of iOS development using Swift. For example, in this project, we explored the following concepts:

Code styling in Swift. You can find some code styling guides here:

Ray Wenderlich Swift Style Guide
Github Swift Style Guide

Views are created in Storyboard, Interface Builder, or programmatically, but they have the same goal: instantiate, initialize, and layout view objects. We use IBOutlets to give names to view objects, similar to giving unique ids to divs in HTML.
We registered for touch events, which can be done programmatically or via IBActions.
We explored NSUserDefaults, one of the four persistence strategies in iOS.
View controllers have a set of methods that are called when it loads, appears, or disappears. These are called view controller lifecycle methods.
Do your views look good on iPhone 4, 5, and 6? We will cover in class how to use Auto Layout to robustly design your views for different screen sizes and OS versions.
After this assignment, you should understand the purpose of IBOutlets and IBActions as well as the basics of designing views and programmatically interacting with the views from the controller.

The next step is a brief phone conversation with the teaching team here which we'll be scheduling as it gets closer to the start of the bootcamp.
During the phone call, we'll ask you a few simple language questions that may include things like: strong vs weak properties, optionals, blocks/closures, and categories/extensions. We'll also ask you about why you want to learn iOS and what apps you're interested in building.
Feel free to continue making improvements to the app before we schedule the phone call. We'll check it one more time right before the call. We give priority to people that demonstrate that they are willing to put a lot of time into this class. Check out these past excellent submissions.


fix Crash (file not found)

Hi @nicogbg, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


Kubernetes upgrade is stalling with rancher 2.4.3 in the UI

After upgrading from rancher 2.3.6 to 2.4.3 kubernetes upgrade is stalling and not completing.

Useful
Info

Versions
Rancher v2.4.3 UI: v2.4.22

Route
undefined

@richyta , Could you provide the exact steps that was done after rancher server was upgraded to 2.4.3 .
Were you attempting to add a worker node to an existing cluster?

No not adding a new node just upgrading the existing one to the lastest kubernetes version.

Can you provide the k8s versions prior to upgrade and the version you were upgrading to ? Is this a custom cluster ?

1.17.4

@sangeethah @richyta I did an upgrade in a Rancher single install.
Custom cluster in v2.3.6 with k8s version v1.17.4-rancher1-2
Upgrade to v2.4.3 wait for the agents to be upgraded.
Upgrade K8s in the cluster to v1.17.5-rancher1-1

Upgrade was successful and the cluster Active.

I am running this in a 3 node HA environment so maybe different in a single rancher instance install verses an HA environment.

@richyta cool thanks I will try HA, I assumed this was a single install.

No this was done on 3 node HA not single install.

Most companies that I am aware of will have an HA environment and not a single node instance install. I primarily use single node install to perform testing and not ran in production.

We have a replicated HA testing environment that we use to perform upgrades prior to pushing it to dev, staging and production environments.

Thanks for testing  izaac. Look to hearing how it goes for you.

What's the current state of the cluster at the moment? As I wasn't able to reproduce the issue in an HA setup either.
Would you be able to share the logs of your setup?
Thanks @richyta

Cluster has no issue that I can tell at the moment. As for the logs I would need to check with our team.

So the cluster has 3 master nodes that has all the roles on them and 3 worker nodes running. Just FYI.

I will try deploying another worker node with the new setup and see if that deploys or not to test.

@richyta I will try again the HA upgrade with the Custom cluster 3 nodes all roles. Thanks for the info.

Interesting so even when I go to add a new cluster I am having issues creating it.

@richyta Could you share your rancher server logs ? In case of new cluster creation , what is the exact behavior you are seeing ?

Can you provide info on how to grab the logs for rancher?

@richyta Could you capture the actual api call made by UI and see if there are any console errors you are seeing when this action is peformed?

At this point its really not usable rancher 2.4.3. So we will stay with 2.3.6 until the bugs are fixed.

Based on the original comment, it seems as if the problem is in the UI is stuck with the button as Saving which is not directly associated with the stability of the downstream cluster. Since you take the Docker command and apply it to your cluster, whatever happens in the UI is not correlated to the downstream clsuter.
@izaac Did you test clicking on Save on the UI to see that it can go back to the clusters page?
@richyta Did you apply the docker command to your downstream cluster? Did the cluster become active? Is the complaint that the UI is stuck in Saving?

Got this from the user this is what the UI shows in console when clicking Save after selecting the K8s version to upgrade.

I'm guessing that the user doesn't have the cisscanconfig schema in their current cluster and scheduledClusterScan is enabled.
To get the cluster unstuck try disabling "Scheduled CIS Scan Enabled" and saving. More than likely it has nothing to do with the upgrade and if you attempted to save anything it would fail.

The issue seemed to be that in Richard's setup the Scheduled CIS  Scan Enabled option was unselected.

@maggieliu So I sent out a PR which should allow the user to still save even if they run into this issue.
Unfortunately I haven't been able to reproduce this with any kind of consistency. The one time I reproduced this issue it appeared that the cisscanconfig schema wasn't present. Though my change should stop the bleeding I think the proper fix will need to be a backend change.

Reproduced reliably with the following steps:

Create a custom data.json for rke-metadata-config that does not have the CIS Config Params or CIS Benchmark Version Info
Install Rancher with the environment variable for RKE metadata config pointing to that data.json: sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -e "CATTLE_RKE_METADATA_CONFIG={\"refresh-interval-minutes\":\"144000\",\"url\":\"https://raw.githubusercontent.com/rancher-max/rke-data/master/data.json\"}" rancher/rancher:master-head
Attempt to create a cluster. It will fail with all the errors mentioned above:

Null selection in Advanced Options > Scheduled CIS Scan Enabled
After clicking "Create", it just spins for ever with "Saving"
Same error in console as mentioned above

Validated in both master-head and v2.4-head using UI index latest2 and latest-2.4 respectively

Default value is set to No for Scheduled CIS Scan Enabled

Creating cluster does not stall. Creates successfully

Upgrading cluster is successful

No error occurs in console logs

NOTE: This fixes cluster creation/upgrade, but the error of having no CIS Scan Profiles is still present. #27005 will address that.


Older/Newer block links broken because of commas

It seems that the commas in the block heights make the Older and Newer link on /explorer go to the wrong block range.
For example, with "169,685" as the top block in the table, Older takes you to /explorer?height=168&rows=1 and Newer takes you to /explorer?height=188&rows=20

Will be addressed when PR https://github.com/dcrdata/dcrdata/pull/181 merges


Concordance and grammar improvements.

X     I have read freeCodeCamp's contribution guidelines.
X    My pull request has a descriptive title (not a vague title like Update index.md)
X    My pull request targets the master branch of freeCodeCamp.
X    None of my changes are plagiarized from another source without proper attribution.
X    My article does not contain shortened URLs or affiliate links.
If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

[X ] I have read freeCodeCamp's contribution guidelines.
[ X] My pull request has a descriptive title (not a vague title like Update index.md)
[X ] My pull request targets the master branch of freeCodeCamp.
[X ] None of my changes are plagiarized from another source without proper attribution.
[X ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Just that word change actually made it less clear of what the attribute does.
We look forward for more PR from you in the future.


Fix for HADOOP_CLASSPATH is missing in docker container

To close https://github.com/oap-project/cloudtik/issues/347


Expected behavior
Brickrail should still be connected to the other hubs when one is disconnected and turned off in Brickrail.
The hub that disconnected should be set to off in Brickrail automatically when batteries are removed etc.
or when the Hub is turned off in Brickrail, when trying to reconnect, it should turn off, not have a BLE error.
Screenshots

Logs
brickrail.log
ble-server_2023-09-03_17.15.09.log

Thanks for reporting! The server definitely shouldn't crash there. Unfortunately the exception is apparently not printed to the ble-server log, so I should work on that.
A hub suddenly losing disconnecting for some reason should probably only trigger emergency stop. For now I recommend disconnecting the hub in brickrail before turning it off.

Should be fixed now. Unexpected disconnects should now lead to emergency stop with an appropriate error message and you should be able to reconnect the hub if it turns on.


Ensure seed capacity for resources requested by shoots is not exceeded

How to categorize this PR?
/area robustness
/kind enhancement
/priority normal
What this PR does / why we need it:
Ensure seed capacity for resources requested by shoots is not exceeded, as described in GEP-13 (see #3017).

Introduce resources requested by shoots via the new resourceRequirements field in the shoot spec.
Validate resourceRequirements.requests (it is immutable).
During scheduling, filter out candidates that don't have available capacity for any resource requested by the shoot.

Which issue(s) this PR fixes:
Fixes #2938
Special notes for your reviewer:

Based on #3075
The new field in the shoot spec is named resourceRequirements rather than resources since there is already a resources field used for something else.
A new ResourceRequirements Gardner type is introduced rather than using corev1.ResourceRequirements, since the scheduler is only interested in resource requests, but not limits. It is unclear whether resource limits could be useful in our case.

Release note:
Shoots can requests resources via the new `resourceRequirements` field in the shoot spec. The scheduler ensures that only candidate seeds with available capacity for any resource requested by the shoot are considered during scheduling.

Do we have concrete use-cases for allowing end-users to specify resource requirements for their shoots? The GEP states

For example, if a shoot requests (via a resourceRequirements field) a certain number of persistent volumes, but the seed's allocatable amount of persistent volumes minus the number of persistent volumes already requested by other shoots scheduled onto that seed is lower, the shoot can't be scheduled onto that seed.

End-Users don't know/care what we do in the seed, i.e., they should not have the ability to configure anything like this on their shoots.
Still, I get the underlying motivation: Staying with the example of PVCs: a shoot needs a certain number of volumes in the seed, and we should ensure that it only gets scheduled when the max number of volumes the seed can handle is not exceeded, but isn't this rather something that is derived out of the concrete implementation how a shoot is brought up, hence, should not be configureable from outside (as it won't help anyways)?

@rfranzke

Do we have concrete use-cases for allowing end-users to specify resource requirements for their shoots?

I simply implemented partly the more advanced use case described in the GEP.

End-Users don't know/care what we do in the seed, i.e., they should not have the ability to configure anything like this on their shoots.

I must admit I find this actually convincing. It's interesting that it's brought up here, while neither you nor anybody else objected in the GEP yet (neither in the comments, nor in the team discussion), even though this was there from the very beginning. Is it because it's easier to review code than documents? :-)
Could you please raise the same objection in the GEP? If no actual use-cases are brought up, then this should simply be dropped from the GEP I guess and this PR should be abandoned.

Is it because it's easier to review code than documents? :-)

Sure, definitely! Just kidding, I think this boils down to https://github.com/gardener/gardener/pull/3017#discussion_r515927004. The GEP covers a lot of topics, some more detailed than others, and it's somewhat hard to grasp the whole e2e story with the many details at once. As stated in this linked comment: I like that we can have an overview document which highlights all the use-cases and topics related to automatic seed management, but it will be much easier for everybody if these use-cases will be split into smaller sub-topics (that either deserve their own GEP with more details, or at least an issue with more details (depending on your preference) where we can discuss the details (ideally, before we start the implementation).

Closing as discussed above.


docs: deploy docs to github pages

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.743%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
1010

Relevant Lines:
1044

💛  - Coveralls


ssh_pw bin path for SOL logging

the SOL logging works well on 2 conditions

Export the bin/ path  and execute python -m robot
run via tox

To remove dependencies for explicit exporting from the command line, this fix is required

https://gerrit.openbmc-project.xyz/#/c/5019/


ScrollBar: fix hover/pressed hc color for arrow buttons.

Description

This PR updates the hover/pressed arrow button colors in HC.
Motivation and Context

Previous HC colors didn't pass the HC contrast requirements.
How Has This Been Tested?

Manually.

/azp run


CAPSTONE PROJECT

In this Project, I:

Set up Linters for HTML, CSS, and JavaScript
Implemented correct use of GitHub flow
Followed best practices for HTML, CSS, and JavaScript
Implemented the design from the original version
Built the home page and about page using HTML, pure CSS, and Javascript
Made the pages responsive to both mobile and desktop versions
Implemented a Navigation menu bar at the header section of the page
Implemented a mobile menu
Stored the data about the judges in objects inside an array
Created the featured Judges section dynamically using Javascript
Here is a video link of this project with a graphic and more detailed description of this Capstone Project

Thanks for the Approval 👍


feature: Add setting to block all external network communication

Feature scope
Other
Description
Per @dingobar's request on Slack: https://meltano.slack.com/archives/C01TCRBBJD7/p1663137839450139

I was originally thinking it might be useful to use unshare or some other low-level trick to block the network access, but that would just cause unwanted network access to fail, rather than preventing it in the first place. Also unshare only works on Linux. In a similar vein we could patch Python's networking stdlib functions, but that still causes failures instead of preventing the attempt in the first place.
To prevent attempted external network access before it occurs, we'll need to assemble a list of every place within Meltano that might attempt external network access, and then update them all. We should try to be granular with this. Just because some small relatively unimportant part of a feature attempts to access the external network doesn't mean that the whole feature should be skipped.
A context manager that can only be entered when external network access is permitted can be used for this. It can optionally be provided an exception to raise if it could not be entered, with the default behaviour being to log that it was skipped (including what specifically was skipped because of the setting), and then skip the enclosed block.

I used to set MELTANO_DISCOVER_URL=false in order to stop meltano from talking to the discovery document in the past. Not sure if that still holds true after moving from the discovery yaml doc to the Hub API.

@cwegener - This is a great call-out. I hadn't considered this myself. But, yes, as you say, the discover_url=false behavior is one way to achieve the goals of this feature.
Expanding on this a bit, if a feature flag named something like block_external_network equals true, we likely could internally implement as equivalent to forcing hub_api_root=false and discovery_url=false.

docs.meltano.com/reference/settings#hub_api_root
docs.meltano.com/reference/settings#discovery_url

Expanding on this a bit, if a feature flag named something like meltano_network_access_disabled equals true, we likely could internally implement as equivalent to forcing hub_api_root=false, discovery_url=false, and send_anonymous_usage_stats=false. Maybe there are other things to restrict as well, but this would likely get us pretty far!

I couldn't think of anything else myself.
Btw. a good way to validate this manually is via the repro steps I provided in this bug report: #7298  by visually inspecting the http traffic via mitmproxy (I use mitmproxy as part of my local debugging and development efforts quite often)

Still relevant


Bulk deletion of form submissions

This pull request replaces the exsting deletion interface for form submissions (implemented in #1528) with one that allows deleting multiple submissions at the same time.
Motivation
Some of our clients have a lot of form submissions and would like to delete them all to comply with data protection. It is very time consuming to have to do this one at a time. There is also a problem with the action buttons being on the right, which makes them difficult to get to for forms that have many fields.
Solution
Each submission now has a checkbox to the left of it. When a checkbox is checked a delete button appears at the top. Clicking the delete button takes the user to the "confirm delete" view. It's possible to select multiple submisssions and delete them together.
It also has a gmail-like select/deselect all button at the very top to speed up mass-deletions.
Screenshot
The "delete selected submissions" button only appears when one or more submissions have been selected

LGTM

@gasman
Thanks for the review, this is now ready for another look!

Merged in 4f1d3509ff0f8958adb288ec53945fde76c31260 - thanks!


HOSTEDCP-1709: hack/test: remove timeouts

The top-level go test timeout does nothing beneficial for us - we need to be well-formed in the face of SIGTERM from the test platform anyway, and we need to time out within our tests, not from the top-level, as this will give us sensible test failure output (e.g. a specific assertion failed) versus the current panic output which makes it impossible to generate jUnit.
/assign @sjenning

/area testing
/approve
/lgtm

/retest


do not require that main.py is executable

fixes #112

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (58f05c6) 70.57% compared to head (5055582) 70.57%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #113   +/-   ##
=======================================
  Coverage   70.57%   70.57%
=======================================
  Files          72       72
  Lines        4336     4336
=======================================
  Hits         3060     3060
  Misses       1276     1276

Flag
Coverage Δ

unittests
70.57% <100.00%> (ø)

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.

@magland  I tested the action with this branch and now it works!
merging


"cd.." command not found

https://github.com/diegoulloao/install-ioquake3-mac/commit/d349777134cd0d01b2a2a301c683181346f670b2#diff-20488634e978ccd1f9f7c7daf1e75300R19
Should be cd ...

Solved. Thanks!


Error during installing dependencies

Env
I'm using a Nvidia official docker image as the base image on my 4090 Graphics card.
Problems
tiny-cuda-nn
During installing tiny-cuda-nn, an error occurred:
...
[DreamMat/modules/tiny-cuda-nn/dependencies/fmt/src/format.cc](ninja: error: 'PATH/DreamMat/modules/tiny-cuda-nn/dependencies/fmt/src/format.cc', needed by 'PATH/DreamMat/modules/tiny-cuda-nn/bindings/torch/dependencies/fmt/src/format.o', missing and no known rule to make it)
...

Can be solved according to https://github.com/NVlabs/tiny-cuda-nn/issues/447.
raytracing
And also, there got a Eigen/Dense: No such file or directory installing raytracing.
I checked that there is no such package in my env:
root@path# dpkg -s libeigen3-dev
dpkg-query: package 'libeigen3-dev' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.

so I install it:
apt update
apt install libeigen3-dev

In case someone may meet the same problem.


[fix] [broker] [Branch-2.10] Upgrade rocksDB version to <IP_ADDRESS> to keep in sync with BookKeeper's RocksDB version

…cksDB version

Fixes #xyz

Master Issue: #xyz

PIP: #xyz

Motivation
Ugrade the RocksDB's version to <IP_ADDRESS> to keep in sync with BookKeeper's RocksDB version
Modifications

Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Since the merge of this some of our Pulsar 2.10 integration tests are failing these include errors like:


/say messages not showing

I am sending /say messages from the server console and they do not show.

Got this working in dev