AnalyticalBinding/AnalyticalTable: Missing section/lines in subtree after paging

OpenUI5 version:
1.96.9
Browser/version (+device/version):
Version 103.0.5060.134 (Official Build) (32-bit) (Windows 10)
Any other tested browsers/devices(OK/FAIL):
-/-
URL (minimal example if possible):
https://analytics-issue.cfapps.sap.hana.ondemand.com/analyticaltable/webapp/index.html
User/password (if required and possible - do not post any confidential information here):
Not required.
Steps to reproduce the problem:

have an AnalyticalTable with numberOfExpandedLevels > 0, autoExpandMode = Bundled
have enough data for pagination to be required
scroll down in table to load additional lines

What is the expected result?

What happens instead?

Any other information? (attach screenshot if possible)
I traced the issue down, the issue was caused by empty array entries in this.mKeyIndex for the parent node (groupID "/D1-16/D2-0/"). This is caused by the iStartIndex being >0.

So, I could work around the issue by monkey patching this additional line
oGroupMembersRequestDetails.iStartIndex = 0;
into this:
https://github.com/SAP/openui5/blob/445e7a4029d1886b66981ec6a2f19206c102f143/src/sap.ui.core/src/sap/ui/model/analytics/AnalyticalBinding.js#L3383-L3384
With my limited understanding, this would make sense looking at the similar case a few lines later, doing the same thing:
https://github.com/SAP/openui5/blob/445e7a4029d1886b66981ec6a2f19206c102f143/src/sap.ui.core/src/sap/ui/model/analytics/AnalyticalBinding.js#L3385-L3392
@ThomasChadzelek
I see you did change these lines of code last time (git blamed, but not blaming you 😏):
https://github.com/SAP/openui5/commit/05a8e9ff5d368ab7ffa24af40deb59a6254ad789
https://github.com/SAP/openui5/commit/6b20872b42a64e23eb424b678cb33fc1480be4cd
If you could help me validate if my workaround is actually a valid solution, that would be a huge help!

@ThomasChadzelek moved on to other topics, so support from another source would be required 🙂

Hello @nils
In order to process this issue to the responsible team I would need some more information or example so I can debug and forward to responsible team (Core team or Tables team or other?).
Could you please assist?
Regards,
Martin
(Github Dispatcher)

Hi @nils,
Thanks for the findings, the proposed fix and the example. I am just preparing a fix for this issue.
Best Regards,
Sven

The fix is submitted and will be part of 1.107.

Fixed by https://github.com/SAP/openui5/commit/3f3b2dc1ef17cbdb7189cdda76949656a53ed8ab


Codelab Erratum "firebase-get-to-know-flutter#6"

The part related to casting a String into a dynamic object causes "argument_type_not_assignable" error. The code is fixed in the repo but the guide is not.
link to guide
In the codelab the following part causes the error:
GuestBookMessage(
                name: document.data()['name'],
                message: document.data()['text'],
              ),

The correction is as follows:
GuestBookMessage(
                name: document.data()['name'] as String,
                message: document.data()['text'] as String,
              ),

Hi @rashidotm thank you for filing this issue, it is reproducible.

cc @domesticmouse


'Style "Default" Links' is not a pro tip

You suggest to use a[href]:not([class]) for a-Tags without an href-attribute. But why?
a is everything you need to style for this case. Heck, you can use a:link, a:visited if that floats your boat but adding two different type of selectors ([attribute], :not()) is in no way a pro tip.

a (and a:link, a:visited) matches all links, whether they have a class attribute or not.
a[href]:not([class]) matches only links with no class attribute. This is preferable because you can assign specific styles for those “ordinary” links without having to then override those styles to remove them from your “specialized” (classed) link styles.
For example, if you wanted your class-less links to be bold, but your classed links to be normal, you could write:
a { font-weight: bold; }
a.someclass { font-weight: normal; }
a.anotherclass { font-weight: normal; }
a.thirclass { font-weight: normal; }

…or you could just write this one rule:
a[href]:not([class]) { font-weight: bold; }

Mind giving some real examples and not some constructed, theoretical stuff?
If dropping IE < 9 support is considered a "pro tip", then I happily stay non-pro.
And I just don't get the whole reasoning behind this collection of tips.
Reducing multiple resets to "default"-styles is the only justification for this "tip" to be valid; while the lobotomized owl selector forces you to reset the top margin all the time if you don't need it. That's just inconsistent reasoning.


Add tool to perform typescript regression checks as part of CI and update documented typescript version

What

Add tool (check-typescript-regression) that runs our lowest supported version of typescript over our package.
Update supported typescript version in storybook from 3.7.0 to 3.8.3 as that is the actual lowest version that works (fluent package breaks 3.7)

Why
We never know if we've broken this, now we do!
How Tested
Verified that adding types that only newer typescript supports to our public API breaks this build and hence breaks CI.

How long does it take to do a check here?

How long does it take to do a check here?

As much as 4seconds locally

So the idea of this check is to see if we still support 3.8.3 while other packages is still using 4+
That's a good idea, maybe more compatibility checker should be added if that is possible

Yep! I was thinking the same, things like webpack, react etc. would also be useful


Make sure generated CLI docs are always up to date

should we include the  bash completion file in etc/bash as well? Another option is to just remove it since we can just generate it when needed - https://github.com/projectriff/riff/blob/master/Getting-Started.adoc#riff-cli-bash-completion

Holding off on the completion stuff (as I also want to deal with zsh, although it doesn't work).
BUT, my understanding is that you don't deal with it as a file anyway.
You
source <(riff completion)

or tomorrow
source <(riff completion [bash|zsh])

right, riff completion generates a file and I just saved it in /etc/bash - we should remove it

the bash completion doesn't work that great either

Arf, you missed a last minute change I think.
Let's wait for travis to fail (./riff instead of riff), I'll push a commit afterwards

Oops, I wish git would warn you that there are additional commits.
I added an additional commit using ./$(OUTPUT) including the same doc changes so still looks good


Polyfill broken in V1.1.X

This polyfill is broken for e.g. Safari 10 since Version 1.1.X.
Please fix this!
JS error from console:
this.searchParams._fromString is not a function.

Could you provide an example + a stack trace please ?
The tests are running fine on safari 12.0, I guess you have an older version but I don't have access to a previous one. Thanks

I'm trying to get an error stack but unforunately without luck.
All i can see is:
this.searchParams._fromString is not a function. (In 'this.searchParams._fromString(this.search)', 'this.searchParams._fromString' is undefined)

Did you download 1.1.3 ?

You should release the latest version to npm. I'm still getting version 1.1.0 which has the issue obviously.


Updates

Category

[X ] Content fix

Docs Build status updates of commit 1a065f7:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 1a065f7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/defining-a-power-platform-environment-strategy.md
:white_check_mark:Succeeded
View

Community/glossary.md
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario01-Personal-Productivity.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario02-DepartmentEnvironments.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario03-ApplicationEnvironments.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario04-Multi-Tenant.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


feat: support resource query in context module

#4450

Summary

Test Plan

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

Thank you. It seems that the use case of issue-7778 needs to wait until oxc_resolver is upgraded to 1.5.0 (#5644). This PR can be merged first.
I will follow up on this use case in the future. In addition, it seems that the generated artifacts of rspack are different from those of webpack, and I will try to align them.

The import_scanner.rs seems not working, I don't find any place use this module


Media notification not showing in webview..i am running site that show media notification on browser but in webview media notification not appear.

Media notification API is not available on Android WebView. See:

https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API
https://stackoverflow.com/a/61524847/4637638
https://developer.mozilla.org/en-US/docs/Web/API/Navigator#Browser_compatibility (mediaSession is not supported)


[Feature Request]: Support for Apple Silicon Mac

Is there an existing issue for the same feature request?

[X] I have checked the existing issues.

Is your feature request related to a problem?
Hi.
It looks like the docker image and instructions are for Linux. I tried to run the docker compose on my M2 Mac, but I do get errors related to MySQL.

! mysql The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

 runtime: failed to create new OS thread (have 2 already; errno=22)

### Describe the feature you'd like

Apple Silicone support and clear instructions how to install in Mac

### Describe implementation you've considered

I tried to add     `platform: linux/amd64` to MySQL image deofinition in docker compose, but this didn't help.

### Documentation, adoption, use case

_No response_

### Additional information

_No response_

M

M

@hxf829 Thanks. That helped.
However I get now some issue with starting MySQL. Missing permission.
Entrypoint] Starting MySQL 8.0.32-1.2.11-server ragflow-mysql   | 2024-04-10T08:28:05.436873Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead. ragflow-mysql   | 2024-04-10T08:28:05.442115Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead. ragflow-mysql   | 2024-04-10T08:28:05.442322Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.32) starting as process 1 ragflow-mysql   | mysqld:  ragflow-mysql   | File './binlog.index' not found (OS errno 13 - Permission denied) ragflow-mysql   |  ragflow-mysql   |  ragflow-mysql   | 2024-04-10T08:28:05.455909Z 0 [ERROR] [MY-010119] [Server] Aborting ragflow-mysql   | 2024-04-10T08:28:05.457529Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.32)  MySQL Community Server - GPL. ragflow-mysql exited with code 1 ragflow-mysql   | [Entrypoint] Starting MySQL 8.0.32-1.2.11-server ragflow-mysql   | 2024-04-10T08:28:06.548380Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead. ragflow-mysql   | 2024-04-10T08:28:06.550551Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead. ragflow-mysql   | 2024-04-10T08:28:06.550634Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.32) starting as process 1 ragflow-mysql   | mysqld: File './binlog.index' not found (OS errno 13 - Permission denied) ragflow-mysql   | 2024-04-10T08:28:06.562618Z 0 [ERROR] [MY-010119] [Server] Aborting ragflow-mysql   | 2024-04-10T08:28:06.567073Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.32)  MySQL Community Server - GPL. ragflow-mysql exited with code 1 ragflow-mysql   | [Entrypoint] Starting MySQL 8.0.32-1.2.11-server ragflow-es-01   |  ragflow-es-01   |  ragflow-es-01   | ERROR: Elasticsearch exited unexpectedly, with exit code 137 ragflow-mysql   | 2024-04-10T08:28:08.193320Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead. ragflow-mysql   | 2024-04-10T08:28:08.199096Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead. ragflow-mysql   | 2024-04-10T08:28:08.199287Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.32) starting as process 1 ragflow-mysql   | mysqld: File './binlog.index' not found (OS errno 13 - Permission denied) ragflow-mysql   | 2024-04-10T08:28:08.215373Z 0 [ERROR] [MY-010119] [Server] Aborting ragflow-mysql   | 2024-04-10T08:28:08.216843Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.32)  MySQL Community Server - GPL. dependency failed to start: container ragflow-es-01 is unhealthy

Have a look at #329

Having trouble running ragflow on M3 Silicon Mac or even building the docker:
docker build --no-cache -t infiniflow/ragflow:dev -f Dockerfile.arm .
Output:
Dockerfile.arm:7
--------------------
   6 |     COPY requirements_arm.txt /ragflow/requirements.txt
   7 | >>> RUN pip install -i https://mirrors.aliyun.com/pypi/simple/ --default-timeout=1000 -r requirements.txt &&\
   8 | >>> python -c "import nltk;nltk.download('punkt');nltk.download('wordnet')"
   9 |
--------------------
ERROR: failed to solve: process "/bin/sh -c pip install -i https://mirrors.aliyun.com/pypi/simple/ --default-timeout=1000 -r requirements.txt &&python -c \"import nltk;nltk.download('punkt');nltk.download('wordnet')\"" did not complete successfully: exit code: 1

View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/fvay1k2wtt4fzbb2yijrj0r2t

Having trouble running ragflow on M3 Silicon Mac or even building the docker: docker build --no-cache -t infiniflow/ragflow:dev -f Dockerfile.arm .
Output:
Dockerfile.arm:7
--------------------
   6 |     COPY requirements_arm.txt /ragflow/requirements.txt
   7 | >>> RUN pip install -i https://mirrors.aliyun.com/pypi/simple/ --default-timeout=1000 -r requirements.txt &&\
   8 | >>> python -c "import nltk;nltk.download('punkt');nltk.download('wordnet')"
   9 |
--------------------
ERROR: failed to solve: process "/bin/sh -c pip install -i https://mirrors.aliyun.com/pypi/simple/ --default-timeout=1000 -r requirements.txt &&python -c \"import nltk;nltk.download('punkt');nltk.download('wordnet')\"" did not complete successfully: exit code: 1

View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/fvay1k2wtt4fzbb2yijrj0r2t

install==1.3.5 to pip-install==1.3.5

modify docker-compose-base.yml  mysql: image: mysql/mysql-server:latest

works for me, Apple M2 Pro

Latest main has changed mysql from 5.7 to 8.0.
I've verify it work on linux/arm64.


can't compile 0.6.3 (No i don't want 0.7.1h)

Describe your bug here.
yeah so uhm, I'm trying to compile 6.3 but i get this amount of errors

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

then you can cry about it

yea cry about it

ill help for one part, ummm, just go to source/flixel, then make a folder called sound, then put all code in system to sounds folder

install this libraries with the sepecific version on the picture
(if this dosen't work then idk)


Provide HierarchyPointNode representation for custom node render

#349

Shipped in v3.1.0 🚀 Thanks for your help dude!
Side note in case this is something you'd want:
You may have to add your git email to your GH account for the contribution to show up correctly, doesn't seem to reference back to your account currently.

Shipped in v3.1.0 🚀 Thanks for your help dude!
Side note in case this is something you'd want:
You may have to add your git email to your GH account for the contribution to show up correctly, doesn't seem to reference back to your account currently.

Thanks. Don't worry about it.


Improvements for 32-bit systems

Here's a branch with correct formatting and another minor optimization:
https://github.com/nwellnhof/sort/commits/optimize-timsort-merge
Here's a different approach that works directly on pointers when traversing the runs.
https://github.com/nwellnhof/sort/commit/a5245cc0dae89d2e8a5f49100f15622572bbb884
With simple sort functions, I get another 15% speed up on the register-starved x86-32 architecture. It makes the code harder to understand, though. Let me know which approach you prefer.


joh/unfortunate anaconda

update distro to cccacb6f3a46905720a0310105a94d0aed864938

This is for https://github.com/microsoft/vscode/issues/175601


Enhanced click from Element should be extended to be called from other classes

Functions like the select from dropdown call the selenium click, which is not as safe as the sentinel click:
private void setSelected(WebElement option, boolean select) {
    if (option.isSelected() != select) {
      option.click();
    }
  }

I would like to be able to call the Sentinel click by default in all of these scenarios.
This will likely require the casting of a selenium element as a sentinel Element, possibly with a copy constructor?

Writing our own findElement() for sentinel Element could also solve this issue, since these are really coming from child element issues.


Reporting of PM's leads to error screen

See https://www.elkarte.net/community/index.php?topic=5711 for details

in PersonalMessage.controller.php find
if (empty($modSettings['enableReportPM']) || empty($this->_req->query->pmsg))
and replace it with
if (empty($modSettings['enableReportPM']) || empty($this->_req->post->pmsg))


Mail Flow Test gives WinRM error.

I have 2 Exchange 2016 CU 10 servers in a DAG running on 2012 R2, and when I run the script on one server, the mail test for the other fails.
This is the powershell output for the failed Mail flow item (everything else passes successfully)
MAPI connectivity: Success
Mail flow test: WARNING: Connecting to remote server OTHERSERVER.DOMAIN.com failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination  computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
WARNING: Cannot validate argument on parameter 'Session'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
Remove-PSSession : Cannot validate argument on parameter 'Id'. The argument is null. Provide a valid value for the argument, and then try running the command again.
At C:\HealthReportLogs\Test-ExchangeServerHealth.ps1:452 char:22

Remove-PSSession $session.Id

                 ~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [Remove-PSSession], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.RemovePSSessionCommand

Fail
If I run the script from the other server, I receive the same failure, except on the opposite server.

As an update, I was able to track this down to a problem in our IIS security configuration!
With this fixed everything works!! Thanks!!!!


sorting by checked rows

Hi there!
Q1: Is there any way to sort data table every time the row's checkbox is checked or rowsSelected props change?
That is, display the selected rows first?
Q2:  Is there any way to disable some rows checkboxes? (by list of rows indexes).
Thank you very much !!!

Your Environment

Tech
Version

Material-UI
4.11

MUI-datatables
3.7.1

React
16.13.1

@noylevy12
A1. using sortOrder
ref : https://github.com/gregnb/mui-datatables/issues/1437
A2. using isRowSelectable

Name
Type
Default
Description

isRowSelectable
function

Enable/disable selection on certain rows with custom function. Returns true if not provided. function(dataIndex: number, selectedRows: object(lookup: {dataindex: boolean}, data: arrayOfObjects: {index, dataIndex})) => boolean.

@noylevy12
A1. using sortOrder
ref : https://github.com/gregnb/mui-datatables/issues/1437
A2. using isRowSelectable

Name
Type
Default
Description

isRowSelectable
function

Enable/disable selection on certain rows with custom function. Returns true if not provided. function(dataIndex: number, selectedRows: object(lookup: {dataindex: boolean}, data: arrayOfObjects: {index, dataIndex})) => boolean.

Sets the column to sort by and its sort direction. To remove/reset sorting, input in an empty object. The object options are the column name and the direction: name: string, direction: enum('asc', 'desc') Example
@wdh2100
First of all, thanks for the quick reply
Regarding Answer 1: I saw it, can you tell me what I should put in the column name? That is, what is the "column name" of the "checkboxes column"?
Regarding Answer 2: I saw it too - and did not quite understand, I need to return Boolean variable- if I return a false then all the checkboxes become disabled and not just selected as I intended :(

Sets the column to sort by and its sort direction. To remove/reset sorting, input in an empty object. The object options are the column name and the direction: name: string, direction: enum('asc', 'desc') Example
@wdh2100
First of all, thanks for the quick reply
Regarding Answer 1: I saw it, can you tell me what I should put in the column name? That is, what is the "column name" of the "checkboxes column"?
Regarding Answer 2: I saw it too - and did not quite understand, I need to return Boolean variable- if I return a false then all the checkboxes become disabled and not just selected as I intended :(

@noylevy12
A1. using sortOrder
Name	Type	Default	Description
sortOrder	object	{}	Sets the column to sort by and its sort direction. To remove/reset sorting, input in an empty object. The object options are the column name and the direction: name: string, direction: enum('asc', 'desc') Example
ref : #1437
A2. using isRowSelectable
Name	Type	Default	Description
isRowSelectable	function	 	Enable/disable selection on certain rows with custom function. Returns true if not provided. function(dataIndex: number, selectedRows: object(lookup: {dataindex: boolean}, data: arrayOfObjects: {index, dataIndex})) => boolean.

@wdh2100
First of all, thanks for the quick reply
Regarding Answer 1: I saw it, can you tell me what I should put in the column name? That is, what is the "column name" of the "checkboxes column"?
Regarding Answer 2: I saw it too - and did not quite understand, I need to return Boolean variable- if I return a false then all the checkboxes become disabled and not just selected as I intended :(

@noylevy12
A1. using sortOrder
Name	Type	Default	Description
sortOrder	object	{}	Sets the column to sort by and its sort direction. To remove/reset sorting, input in an empty object. The object options are the column name and the direction: name: string, direction: enum('asc', 'desc') Example
ref : #1437
A2. using isRowSelectable
Name	Type	Default	Description
isRowSelectable	function	 	Enable/disable selection on certain rows with custom function. Returns true if not provided. function(dataIndex: number, selectedRows: object(lookup: {dataindex: boolean}, data: arrayOfObjects: {index, dataIndex})) => boolean.

@wdh2100
First of all, thanks for the quick reply
Regarding Answer 1: I saw it, can you tell me what I should put in the column name? That is, what is the "column name" of the "checkboxes column"?
Regarding Answer 2: I saw it too - and did not quite understand, I need to return Boolean variable- if I return a false then all the checkboxes become disabled and not just selected as I intended :(

@wdh2100 thank you !

@wdh2100 thank you !


Add libcrypto and libssl to Dockerfile

See https://github.com/Senzing/stream-loader/issues/270

Blocked by https://github.com/Senzing/g2-sdk-python/issues/104

Pull requests:

https://github.com/Senzing/docker-init-container/pull/144


Support for footer on table

Apologies if this has been raised, or if there is a published roadmap/plan, but I couldn't find it.
Overview of the problem
I'd like to add a (totals) footer onto my table and can't see a way to do it currently.
Buefy version: 0.4.5
Vuejs version: 2.4.1
OS/Browser: Google Chrome Mac 59.0.3071.115 (Official Build) (64-bit)
Description
I guess I could try adding it as a row and customise the sort to always leave it at the bottom (including when paginated) and add custom styling etc. but having support for a custom footer directly would be very useful.
Potentially, just a named slot for footer content would allow me to keep going.
And later could come components for <b-table-column-footer> or an extension to <b-table-column> to add a footer slot in it etc.
Steps to reproduce
n/a
Expected behavior
n/a
Actual behavior
n/a

I second that a footer slot would be neat to have

Me too.

+1


doc(docker): add comments for minio disk full issue

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Since this issue has been met for two times and usually takes time to figure out the cause, it's worthwhile to note it down.
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Will also add this to our doc.


security: fix use-after-free in PyCapsule implementation

Thanks to @saethlin for alerting me to this issue.
The current implementation of PyCapsule::new does not require a specific lifetime on the name: &CStr argument. This is a fundamental flaw; the argument is converted to a pointer and handed over to CPython, which simply stores the pointer.
This means that as soon as PyCapsule::new is complete, current implementations can deallocate the name and any subsequent calls to PyCapsule_GetName will read from freed memory (including our safe PyCapsule::name wrapper).
A snippet as simple as this is enough to achieve this:
let capsule: Py<PyCapsule> = Python::with_gil(|py| {
    let name = CString::new("foo").unwrap();
    PyCapsule::new(py, 5usize, &name).unwrap().into()
});

Python::with_gil(|py| {
    let name = capsule.as_ref(py).name();  // <-- Reading from freed memory previous to this PR's fix
});

The fix without any API change is to take a copy of the name as a CString and store that where we place the rest of the capsule data. We can then pass CPython the pointer from there, which guarantees that the name will outlive the capsule.

Given this is a reasonably clear-cut soundness error, I think we should file a RustSec advisory and also yank versions 0.16.0 -> 0.16.5 (after publishing this as a 0.16.6).

For 0.17.0, we might want to change name to Option<&str> as the Python seems to accept NULL as well as a pointer to a null-terminated string. Taking &CStr seems unnecessary when we allocate a new buffer in any case. Alternatively, we might want to take Option<CString> so calling can pass ownership of an existing null-terminated string.

It isn't visible in the diff here, but I while reviewing that, I was wondering whether the closure type F should have a Send bound like the value T since it is potentially called on a different thread than the one that created the capsule?

It isn't visible in the diff here, but I while reviewing that, I was wondering whether the closure type F should have a Send bound like the value T since it is potentially called on a different thread than the one that created the capsule?

Yes, I think you are correct. This is arguably also a soundness issue so I'm now wondering whether to also backcourt that to 0.16, however it is also breaking so that's a bit of a disaster.

For 0.17.0, we might want to change name to Option<&str> as the Python seems to accept NULL as well as a pointer to a null-terminated string. Taking &CStr seems unnecessary when we allocate a new buffer in any case. Alternatively, we might want to take Option<CString> so calling can pass ownership of an existing null-terminated string.

Arrgh that's a great point and means that in PyCapsule::name we also can convert a null-pointer to CStr.
I see three possible choices for the name argument:

Option<&str> and we take a copy always
Option<CString> and we take ownership
Option<Cow<'static, CStr>> and we can then allow to reuse static data to avoid allocating

Think the Cow is probably overkill for something that's not going to be in a hot loop. IMO Option<&str> is very attractive for simplicity for users, although I guess we would have to raise an error if they passed an internal NUL. Which choice do you prefer? (Or something else?)

Which choice do you prefer? (Or something else?)

After musing about it, I'd prefer Option<CString>: Working with capsules is pretty low-level to begin with which is why I'd prefer exposing the CString stored in the CapsuleData as directly as possible instead of going for the convenience of Option<&str>. The Cow-based version looks like too much to me, especially since our capsule wrapper will allocate in any case (for boxing and for the capsule on the Python heap).

This is arguably also a soundness issue so I'm now wondering whether to also backcourt that to 0.16, however it is also breaking so that's a bit of a disaster.

So we have three pending changes now:

PyCapsule::new needs to ensure ownership of name.
The destructor F needs a Send bound.
PyCapsule::name needs to handle the name pointer being NULL.

I think the third problem could also be fixed in a backward-compatible manner by returning a static reference to the empty string b"\0" instead, but at this point we might want to bite the bullet and break the interface to go for name: Option<CString> and -> Option<&CStr> in addition to fixing the Send bound?

print warning and return early without running the F destructor if not on the same thread as the one in which the PyCapsule was created

👍🏽 This sounds reasonable as a soundness fix to me.

To keep the capsule rework separate from this sanitiser, I'm going to merge this now and open up follow-up PRs.


ADD fzf & fzf-tabs

These are great tools, lets add them:
https://github.com/Aloxaf/fzf-tab

Are these gonna go in the student images?

They already are. You can try it out on playgrounds now. It makes a really big difference to autocomplete


Static Assets Database

@ArnoMac @Subrat75 (I created this issue so we can test how to interact via GitHub. Issues allow us to discusse about a single topic and keep track on the progress being made)
I think we should define what it will be the static database. If I understood well this will be the data used to train and fine tune the models.
Thanks to the Binance notebook @ArnoMac provided we should be able to download this data for a few assets, BTCUSDT for example. These are TimeSeries, so I guess that we can set a limit date (12/12/2023 ?) and say that data before that will be used for training/validation and data after will be considered as "new data" (for retraining or monitoring in the scope of our mlops project). Of course in reality for training our models we would like to have the most up to date data.
Once a limit date is fixed, we should transform the notebook into a make_assets_data.py script, within the "src/data/" directory, containing functions that when called, download the historic price data for a given asset (until the limit date) and store it into the "./data/raw" directory.

Not sure to fully understand why we should set a limit date ?
In my mind, the idea was to have the following database:

raw data from binance
processed data ; ready for modeling

For the training/validation, I think we can use the complete historical data and split the data with something like TimeSeriesSplit (from sklearn.model_selection); resulting in a set of data for training and a set for validation.

We are not forced to set a "limit date" in advance per se. I think what you propose works fine too... What I meant is that we should all have ( in our github repos ) the same dataset for the training phase (in this case the limit date will be the last date of this dataset).
The model will be trained a first time once, and then the saved model will be called by the API multiple times to do predictions. Even if there is new data available to download after a couple days, the training set should not change every time we connect to the github. We will probably monitor the performance on this model, predictions after predictions, on new data but this new data will not be added rigth away to the csv file containing the training dataset.
Only when we detect a drop in the model performance the training dataset will be updated with the binance API and the model retrained again.
For the moment, It is good to have the  make_dataset.py script that creates the raw data dataset at the correct location


Do not sort when sort is set to false.

We cannot rely on () => {} as a no-op for sorting.

For the most part, this should be backwards compatible unless you were setting sort: false and happen to be encoding parameters that were susceptible to this issue.

anything else you'd like me to tackle for this?


Select drop down menus duplicate

The HTML seletc drop down menus duplicate every time the Settings modal window is open or an option is selected. Only the latest menu refreshes to the correct value.
This is a Materialize issue, as it does not have a way to actualize the HTML elements without creating a new menu.

Fixed in https://github.com/carlosperate/ardublockly/commit/a04b38e2287191c971eb78ab6a868beeac5f7d62


There might be a section on using Content Collections in Endpoints

📚 Subject area/topic
Guides, Core concepts
📋 Page(s) affected (or suggested, for new content)
Page I suggest editing: https://docs.astro.build/en/core-concepts/endpoints/
📋 General description or bullet points (if proposing new content)
I re-approached Astro after a longer period of not being up to date with latest new things and I was pleased to see since 2.0.x where I reviewed the docs a log of new things appeared. Kudos!
Among the useful things I will definitely use in following days there are static endpoints. They work like a charm, but after exploring them along yesterday I ended up in having something done, but I got stuck at "where to hold my data". I don't have a headless CMS and I wanted to keep the data as static JSON files.
I was a bit surprised that I can't use Astro.glob in Endpoint. Today I approached the problem again and I discovered Content Collections. They do exactly what I wanted and what I needed, but they're not mentioned at all on Endpoints page today. I propose to introduce a section on using Content Collections in Endpoints. Especially the type: 'data' and especially with mentioning that if one was accustomed to Astro.glob for expressing "I want all that…" then getCollection and getEntry are the replacements
🖥 Reproduction in StackBlitz (if reporting incorrect content or code samples)
n/a

Thanks, this sounds like a very helpful addition indeed, @jrencz !
Is this something you'd be interested in making a PR for? Maybe something on the Endpoints page directly, then a link to it on the Content Collections page where appropriate? What do you think?

Closed due to inactivity


Providing state to mrb_run invocations

What is the recommended way of providing custom state (such as a C pointer) when invoking a struct RProc* via mrb_run such that C functions can access that state?
These are the options I considered:
Option 1: (With 1.1.0 and higher only) Set the mrb_state's 'ud' member:
mrb->ud = pointer;
mrb_run(mrb, proc, mrb_top_self(mrb));

Then, a C function could access 'ud' from the mrb_state directly.
mrb_value function(mrb_state* mrb, mrb_value self)
{
    void* pointer = mrb->ud;

This could work with 1.0.0 but only if a custom allocator is not being used. (1.1.0 was when 'ud' was repurposed and a separate 'allocf_ud' was added).
Option 2: (Is this defined behavior?) Set the top_self's data pointer:
mrb_value o = mrb_top_self(mrb);
DATA_PTR(o) = pointer;
mrb_run(mrb, proc, o);

Then, a C function could access the data pointer:
mrb_value function(mrb_state* mrb, mrb_value self)
{
    void* pointer = DATA_PTR(self);

Option 3: Set a constant with the C pointer:
mrb_value v = mrb_cptr_value(mrb, pointer);
mrb_const_set(mrb, mrb_obj_value(module), mrb_intern_lit(mrb, "Constant"), v);
mrb_run(mrb, proc, mrb_top_self(mrb));

Then access that constant in the C function:
mrb_value function(mrb_state* mrb, mrb_value self)
{
    mrb_value v = mrb_const_get(mrb, mrb_obj_value(module), mrb_intern_lit(mrb, "Constant");
    void* pointer = mrb_cptr(v);

This seems like the least efficient route.
Are there better ways?

Thanks; I'll go with the option 3. To protect the constant from ruby code access/modification (and only allow access/modification from C code) I suppose I can just choose a literal that isn't a valid Ruby identifier for a constant.

In that case, you can use instance variables instead of constants. TT_OBJECT including top_self can reference a cptr object via instance variables. You can use functions such as mrb_iv_get() and mrb_iv_set().


FlowGroupDisplayBinding is not working

When I upgrade my 2.0.7 installation to 2.0.9 the FlowGroupDisplayBinding is not working anymore (I guess it does no longer bind to a peroperty of the collection?).

@daniel-luberda this is still present with 2.0.10. Will this be fixed in the future? It's not possible to to use Grouping if we are not able to use bindings for the Group Text.

I'm also having this issue. As a workaround, if I set my display name variable as "Key" in my data model and if I don't set the "FlowGroupDisplayBinding" in the xaml, it works.


"user strict" should be "use strict"

https://github.com/sematext/logsene-js/blob/1ccf7de6f141c5bdbe82f96deb559ff6d7951bdc/index.js#L18
I'll fix this as a separate PR to keep them clean.

Thanks, @antony


Implement Support for Dialog-Based Forms

Summary
It would be great to add support for dialog-based forms. The DialogProvider already accommodates payload, prompt, and other types of dialogs. However, displaying forms in a dialog box is a common use case. By enhancing this functionality and possibly implementing a JSON configuration file to define fields that support multiple types—such as autocomplete and select—similar to the colDef in the DataGrid, we could significantly improve the user experience.
Examples

Motivation
Enhance the use case for the DialogProvider to make it more developer-friendly by enabling the use of dialog-based forms without requiring developers to manually implement all the form and validation logic.
Search keywords: dialogprovider form

Forms and json based forms are definitely concepts we like to have on our roadmap. I see this feature request as a natural combination of those concepts with the dialog provider 👍
it won't be there tomorrow, but fits fully within the scope of toolpad core.

@Janpot, awesome! I'm looking forward to this feature—it'll definitely help simplify my application and reduce boilerplate code. I imagine the JSON/JS file being similar to what's already in place for DataGrid, with methods like getValue, render, etc.


1.18.2 support?

Just curious to see if there's a timeline at all or if its just 'yall are lucky I got it to 1.18.1'. No pressure.

1.19 is the next version I plan to support, sorry for any inconveniences but it comes out in like 2 weeks and I plan to just wait.


Unexpected vault name with plugin Hider hiding vault name

Compatibility measure for hider plugin will be improved later. Currently, you can hide the vault name through style settings：


[Linux] Rename github/hub repo

Description
Repository github/hub was recently moved to mislav/hub. This PR addresses that change.
Ref: https://github.com/mislav/hub/discussions/3326
Related issue: -
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

Closing in favor of https://github.com/actions/runner-images/issues/8362


Impossible to set corner colors

It is impossible to set corner colors such #ffffff #000000 or rgb(255,0,0) by moving the cursor over the saturation selector.
You get colors near them, but not exactly those. For example for black I am getting rgba(1, 0, 1, 1) instead of rgba(0, 0, 0, 1)

FYI, this isn't an issue on my end. Get 0,0,0 and 255,255,255 just fine.


Automated cherry pick of #2305: Fix wrong types and missing field selectors in legacy APIs

Cherry pick of #2305 on release-1.1.
#2305: Fix wrong types and missing field selectors in legacy APIs
For details on the cherry pick process, see the cherry pick requests page.

Codecov Report

Merging #2313 (68a4985) into release-1.1 (51c6ba9) will decrease coverage by 20.62%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           release-1.1    #2313       +/-   ##
================================================
- Coverage        61.94%   41.32%   -20.63%
================================================
  Files              276      139      -137
  Lines            21178    17249     -3929
================================================
- Hits             13119     7128     -5991
- Misses            6695     9492     +2797
+ Partials          1364      629      -735

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
41.32% <ø> (-0.02%)
:arrow_down:

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


Upgrade authentication SDKs and samples references to work IS-5.11.0

[ ] Test and Update the documentation references
[ ] Update the setup scripts
[ ] Update the image references

SDK samples and documentation are now up to date with 5.11


DDMathParser failing to tokenize solitary plus character

Using DDMathStringTokenizer, while something like 2 + 4 tokenizes fine into 3 tokens (with the second being the + operator and the first and third being numbers), if I pass over a + alone, it fails to return it as a token.
This does not hold true for every other operator I've tried, such as / * - etc.
I can probably force this somehow but how can I get DDMathStringTokenizer to tokenize the + correctly?
To reproduce the issue: The following will return an array with no objects. If you change the string value to another operator character it will return a valid array.
NSError *error = nil; NSString *string = @"+"; DDMathOperatorSet *opSet = [DDMathOperatorSet defaultOperatorSet]; DDMathStringTokenizer *tokenizer = [[DDMathStringTokenizer alloc] initWithString:string operatorSet:opSet error:&error]; NSLog(@"Tokens:%@", [tokenizer allObjects]);
Note: This was originally posted here: http://stackoverflow.com/questions/30822751/ddmathparser-failing-to-tokenize-solitary-plus-character

Interesting....
This is actually the tokenizer trying to be nice for you. When it sees +, it correctly identifies it as an operator, but since it's ambiguous (it could be unary or binary), it marks it as needing to be disambiguated.
Since this is the first token in the stream, the tokenizer correctly interprets it as a unary + operator.
However, the -[DDMathStringTokenizer _processToken:withError:] method drops all unary + operators on the floor, because they're pointless operators; they don't actually affect the evaluation of the result. Thus, it doesn't appear in the final array of tokens.
This should be better on the 1.1 branch, because there I separated the concepts of tokenizing and token interpretation, so on that branch the tokenizer will give you the + token, but it won't know that it's a unary + until after it passes through the token interpreter.

Yeah I was thinking the same (in comments on SO) that it was ambiguous so it decided to just return nil. Will the 1.1 branch make the tokenType property settable (to make forcing this one way or another easier)? I am already wrapping your tokens with my own but it would still be useful to simplify the wrapping.

This is fixed on the 2.0 branch, which will be merged in to master soon.

Excellent! Thanks Dave.

On Aug 25, 2015, at 1:36 PM, Dave DeLong<EMAIL_ADDRESS>wrote:
This is fixed on the 2.0 branch, which will be merged in to master soon.
—
Reply to this email directly or view it on GitHub https://github.com/davedelong/DDMathParser/issues/104#issuecomment-134710967.


IndentationRule: fix wrong indentation in named arguments

Fixes #964

thanks for fixing those issues, please rebase this one after your previous PR has been merged


Wrap text in UILabel

Is your feature request related to a problem? Please describe.
Currently, when the char limit is exceeded, text is just hung off the side.
Describe the solution you'd like
Text is wrapped when char limit is exceeded
Describe alternatives you've considered
I could manually do it with the Python textwrap module and whatever sequence you use to make a new line in a UILabel, but I don't know what that sequence is

Or, if you could just tell me how to get a new line in a UILabel I'll close this issue and do it myself with textwrap

Have you tried the UITextBox?
https://pygame-gui.readthedocs.io/en/latest/theme_reference/theme_text_box.html
It is essentially a UILabel but with word wrapping, though there are a few feature disparities between the two that I hope to eliminate in the next text refactor.

@MyreMylar thanks! I'm looking into the UITextBox. Is there a way to dynamically update the UITextBox text? When I use set_text(text) PyCharm tells me that UITextBox has no attribute set_text.

Maybe I could manually set the box.html_text attribute?

The text box isn't the fastest for changing the text in the box at the minute, that's one of the things I hope to improve in the big text refactor in version 0.6.0.
That said I think if you change what is in box.html_text and then call box.rebuild it should work.
If you are trying to build something like a console, or terminal then there are a couple of other issues complaining about difficulties with that and it is one of the target examples for 0.6.0.

Cool, that seems to work. Do you have an ETA for 0.6.0?

Do you have an ETA for 0.6.0?

Nope. Other than it is currently planned to be the release after 0.5.7 (which is the next one - we are on 0.5.6 publicly right now). Then again I didn't intend to do 0.5.7 really, I just got pulled into a rabbit hole chasing some bugs and issue reports and suddenly there was a bunch of new code that needs releasing.
I'll tentatively estimate 'this year' but it could be a lot sooner or later in the year depending on how things shake out with the pandemic/other projects/etc

You can look at the project board for 0.6.0 here:
https://github.com/MyreMylar/pygame_gui/projects/2
But it's not very exciting yet because nothing has started.


Bug on Note 4

Hi.
I'm using you library.
In some cellphones like  Samsung Note 4 when I use front camera it dose not work with this Log:
15726-23967/com.google.android.cameraview.demo W/LegacyRequestMapper: convertRequestMetadata - control.awbRegions setting is not supported, ignoring value
15726-23967/com.google.android.cameraview.demo W/LegacyMetadataMapper: convertAfModeToLegacy - ignoring unsupported mode 4, defaulting to fixed
15726-23967/com.google.android.cameraview.demo W/LegacyRequestMapper: convertRequestMetadata - control.awbRegions setting is not supported, ignoring value
15726-23967/com.google.android.cameraview.demo W/LegacyMetadataMapper: convertAfModeToLegacy - ignoring unsupported mode 4, defaulting to fixed

I got the same problem. is this going to be fixed ?

+1 Help please

did any of you solved this issue?? thanks!


Auth repo-relative headers

Public headers use module syntax and others are repo-relative.
#no-changelog

Thanks @wilhuff. I'd prefer to have this PR be a pure translation to repo-relative headers along with subsequent style sorting, and g3 synchronization - and address your comments in the next PR

@wilhuff Running clang-format with IncludeBlocks: Regroup addresses most of the concerns. I also made the unit test headers repo-relative and removed the redundant import in FirebaseAuth.m.


Drop virtctl create instancetype and preference functests and refactors unit tests

What this PR does
Drop the functional tests of virtctl create instancetype and virtctl
create preference because all tests cases are already covered by the
unit tests of the commands. The functional tests do not provide any
additional value.
Cleanup the virtctl create instancetype unit tests by:

Reorganizing tests
Adding missing test cases
Removing redundant table entry arguments

Cleanup the virtctl create preference unit tests by:

Reorganizing tests
Removing redundant table entry arguments

Valdidate the specs of created instancetypes and preferences by calling
ValidateInstanceTypeSpec and ValidatePreferenceSpec, which are also
used by the validating admitters.
The goal of this and further PRs is to reduce the amount of unnecessary uses of
virtctl in the e2e tests to stabilize tests, to reduce the number of flakes and to
remove redudant tests.
Before this PR:
The same virtctl create preference tests are run in unit and functests.
After this PR:
virtctl create preference tests run only in unit tests.
Fixes #

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

None

FWIW I don't think you need another PR for this, just add fab232efb5ccb6a23f0a77a675d24ae1b60d24ef and 099ce2632c4d0131be25bf66d083b2764f4f32af to https://github.com/kubevirt/kubevirt/pull/12752/

Addressing @lyarwood's suggestion in #12752: This PR now contains changes for both virtctl commands.

/test pull-kubevirt-e2e-k8s-1.31-sig-operator

/approve


Hello! About ActivityNet-1.3

Hello! When would you release the code or  strategy about ActivityNet-1.3？

We will release anchor-free method for ActivityNet-1.3 soon.


Queue: AccessDenied to resource https://sqs.us-east-1.amazonaws.com

Description
After deploying, sending a message always throws an access denied error (error: AccessDenied: Access to the resource https://sqs.us-east-1.amazonaws.com/ is denied):
Full error:
{ value: { error: AccessDenied: Access to the resource https://sqs.us-east-1.amazonaws.com/ is denied. at Request.extractError (/opt/nodejs/node_modules/aws-sdk/lib/protocol/query.js:50:29) at Request.callListeners (/opt/nodejs/node_modules/aws-sdk/lib/sequential_executor.js:106:20) at Request.emit (/opt/nodejs/node_modules/aws-sdk/lib/sequential_executor.js:78:10) at Request.emit (/opt/nodejs/node_modules/aws-sdk/lib/request.js:686:14) at Request.transition (/opt/nodejs/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/opt/nodejs/node_modules/aws-sdk/lib/state_machine.js:14:12) at /opt/nodejs/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/opt/nodejs/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/opt/nodejs/node_modules/aws-sdk/lib/request.js:688:12) at Request.callListeners (/opt/nodejs/node_modules/aws-sdk/lib/sequential_executor.js:116:18) { code: 'AccessDenied', time: 2022-06-28T16:37:44.889Z, requestId: '09a7e81d-722b-56b8-8601-b32842b3e67a', statusCode: 403, retryable: false, retryDelay: 91.4007833446157 } } }

How to Reproduce
serverless.yml
functions:
  - ${file(./src/handlers/handlers.yml)}

constructs:
  queueTest:
    type: queue
    fifo: true
    worker:
      handler: ./src/handlers/processQueueHandler.processQueueHandler

handlers.yml
publisherHandler:
  handler: src/handlers/handlers/publisherHandler.publisherHandler
  iamRoleStatements:
    - Effect: 'Allow'
      Action:
        - 'lambda:InvokeFunction'
        - 'lambda:InvokeAsync'
      Resource: 'arn:aws:lambda:us-east-1:xxxxxxxxxxxxx:function:some-function'
  environment:
    QUEUE_URL: ${construct:assetsToAddQueueStaging.queueUrl}
  events:
    - httpApi:
        path: /api/publishToQueue
        method: post

Please note that publisherHandler also invoke another lambda, thus the iam role there
publisherHandler.ts
const sqs = new SQS({
    apiVersion: 'latest',
    region: process.env.AWS_REGION
});

await sqs.sendMessage({
  QueueUrl: process.env.QUEUE_URL,
  MessageBody: JSON.stringify({
    key: 'value'
  })
}).promise();

Additional Information

Serverless 3.17.0
Serverless-lift 1.19.0
QueueUrl has the right value in the publisher handler
I did not set any specific IAM permissions since the doc didn't say so
when looking at my publisher lambda Permissions, only the one I specifically set shows up. There is no SQS permission.

There is obviously a permission issue, but I can't figure out what.

I ended up setting the IAM Role Statement directly on the publish handler definition:
publisherHandler:
  handler: src/handlers/handlers/publisherHandler.publisherHandler
  iamRoleStatements:
    - Effect: 'Allow'
      Action:
        - 'sqs:SendMessage'
      Resource: ${construct:queueTest.queueUrl}

First I thought that the existing IAM Role Statement on the publish handler was overwriting the SQS one, but even when commenting the whole iamRoleStatements block I'm still getting the AccessDenied issue.
It's working now, but it would be interested to figure out why the permission are not set automatically, as specified in the doc.


add bundles section to version catalog [#918]

Closing this. Please reopen with my comment addressed above. Thanks


Fix compatibility issues with Hugo 0.55

The new Hugo release brings some breaking changes:

WARN 2019/04/18 00:34:11 Page's .Hugo is deprecated and will be removed in a future release. Use the global hugo function.
WARN 2019/04/18 00:34:11 Page's .RSSLink is deprecated and will be removed in a future release. Use the Output Format's link, e.g. something like:
{{ with .OutputFormats.Get "RSS" }}{{ .RelPermalink }}{{ end }}.

And rssLimit requires update RSS template. Update to satisfy the compiler.

@xianmin haven't you force-pushed the repo lately? I thought I saw these changes live and then they are not there and I got a notification about the one-year-old commit.

Merged. Thank you guys!


Directives override

As Angular community grows, and the number of libraries that extend it, the issue of directive override becomes more relevant. As of now, there is only support for 'priority', which doesn't override, rather combines directives according to the priority. And when needed a plain override isn't straightforward at all.
It would be nice that such a mechanism was provided in a simple way. For example, add attribute 'override:boolean' that would work in combination with 'priority', so the override happens according to the priority, i.e. higher priority can thus override an already registered directive as opposed to extending it by default.
Also, right now if a directive is registered twice, there is no meaningful error being logged. I'm getting the following error: Uncaught TypeError: undefined is not a function
The most typical scenario is as follows:
You are using a library where you have found a bug in one of the directives. And you do not have the time and/or desire of going through GitHub and the community to get the fix out. With a simple override in place you just copy the directive locally, fix the bug and declare it as an override - fast and simple fix, until the day the fix is finally released in that library. Patching otherwise the source is a very dangerous approach which way too often results in changes lost over automatic code updates and project re-installations.

I think npm link and bower link both tackle this use case better.
Both of these tools also support installing from a github repo (e.g. npm install btford/my-directive) or from a zip/tar.
It's also possible to use decorators to patch just part of a module.
I wouldn't be opposed to adding a thereCanBeOnlyOne:bool flag to the directive definition that throws if another directive with the same name is registered. But I'm worried that adding a flag that changes which directives are used is going to result in a system that's difficult to reason about.

I would suggest that such feature never make into AngularJS. It does not put emphasis on good design.
That does exists for instance in ExtJS. I don't see that as a good approach. You never know if the next version corrects the original problem, it could be too much code to compare. But if you fork and install off of it, its way better I think. Its not a patch.
In practice, most of the time I was able to create another directive to extend the original directive.

If you really need this feature, you can use a decorator to modify the directives before they are applied.


Creative home page design(Gssoc'23)

I would like to make the home page creative and more interesting.

I'll make the home page a bit more creative and interesting. Plz assign it to me and label it as Gssoc'23.

Hey @Bharatpathak08 !! Use the template to raise an issue !!
according the changes you want to make !!!

Hey @Bharatpathak08 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


add optional targetFieldName argument to forwardTo()

This makes the app bindings to a prismafied legacy graphcool framework
schema easier:
allPosts: forwardTo('db', 'posts')

Working with this more, it turns out to really only help in trivial cases, where on the client we query { allPosts } without any filter.  Even with the change to forwardTo the client code does need to change from { allPosts(filter: { title: 'Foo' }) } to { allPosts(where: { title: 'Foo' }) }.

In this case we should hold back with this PR until these non-trivial cases are implemented as well or until there is further progress in #62.

@schickling agreed, I am not using this on my end anymore, I think we can close it.


Font Size Problem in Vertical Buttons Card

Hi
thanks for this nice template!
I got an issue where the font size is not applied to the h1 text in the vertical buttons card. Both, the  the upper text (supposed to be 20px) and the smaller text (supposed to be 15 px) have 28px, which is a default I guess. Tested with firefox and chromium. Also the font is Roboto, not Helvetica.

I am not sure where the problem is. Apparently the style is not directly applied to ha-card, but is a card-mod element on the same html level:

latest button-card.js and card-mod.js is installed.
corresponding yaml code:
              - content: >
                  # There are  {% if is_state('sensor.lights_on', '0') %}
                  currently no  {% else %}  {{states('sensor.lights_on')}}  {%
                  endif %} lights on
                style: |
                  ha-card {
                  --paper-card-background-color: 'rgba(11, 11, 11, 0.00)';
                  box-shadow: 2px 2px rgba(0,0,0,0.0);
                     }
                  h1 {
                    font-size: 15px;
                    font-weight: thin;
                    font-family: Helvetica;
                    letter-spacing: '-0.01em';
                  }
                type: markdown

Hmm... Have you tried turning it off and on again?
(reload the tab)

Yes also restart home-assistant, I could also ask at the card-mod repo. Maybe they have an idea.

Hi @Rikorose, this is a known issue with card-mod and HA 0.111. For more info, see here. A fix is on the way.

This is the new code that would be updated soon, @KTibow would you mind testing if this would work on 0.110 or lower. Thanks!
# Example entry
# Enter what you want to display
content: |
  # Enter what you want to display here
style:
  .: |
    ha-card {
      --paper-card-background-color: none !important;
      box-shadow: none !important;
      height: 50px;
    }
  ha-markdown:
    $: |
      h1 {
        font-size: 15px;
        font-weight: thin;
        font-family: Helvetica;
        letter-spacing: '-0.01em';
      }
type: markdown

Maybe fix: https://github.com/thomasloven/lovelace-card-mod/issues/52#issuecomment-644767155

Yes, that's what I meant. "Fix" as in an update for this repo 👍

@N-l1 do you know of any plans to fix this without changing the whole config? I did a little poking around and couldn't find anything.

No, unfortunately to my knowledge the markdown styling config has to be updated for 0.111.

This issue has been fixed as part of commit 36ba05c

Note: The style wasn't applying for me, even after doing the fix. I fixed it by changing:
style: |

to
style:


Issue from slack [Moderate]

rj134a [8:16 AM]
I'm trying to send sia coins from my 0.3.0 wallet to an address on the updated 0.3.2. I'm sending over 2 million and says error transaction too large
rj134a [8:17 AM]
Yet the balance reflects the 2 million coins being taken out
rj134a [8:17 AM]
when i restart the client the 2 million are back

We discussed this in the slack, but the problem is that the wallet currently doesn't check if the transaction it is creating has exceeded the 16kb transaction size limit set by the IsStandard() rules.
If it is, there will be an error and the wallet will be seemingly helpless. The fix is to have the wallet make multiple transactions, and then combine the outputs using a final transaction. This isn't a simple fix.
I'll try to have this finished by the June 7th release.

:'( never got to it


ECDSAInputSignature & SchnorrInputSignature

InputSignature will become a new base class with current functionality split into a ECDSAInputSignature subclass and functionality for Schnorr signatures into SchnorrInputSignature.

Completed


STRINGIFY implemented

STRINGIFY implemented

SIMDJSON_THREADS_ENABLED is now def/undef. It was hash defined to 1
This now aligns with usage elsewhere.
As an example see int JsonStream::json_parse(ParsedJson &pj); implementations. Before these change  SIMDJSON_THREADS_ENABLED code was always compiled in.

Now that I have SIMDJSON_THREADS_ENABLED actually undef'd, the #else code in int JsonStream::json_parse(ParsedJson &pj);  implementation, kicks-the-bucket  or flips-the-tables

on line 2337 -- this is my amended single header simdjson.cpp

I will merge this. If there is an issue, please report it as an actual issue, so we can track it. Please don't report potential bugs as mere comments... if you think that it is a bug, please make a genuine issue out of it.

... have opened two projects here on two monitors .. compiled/debug is happening on the single header repo I made from SJ single header folder ... that is very fast and comfortable using VS Code, but then going back to SJ fork on the second monitor to match the findings ...
As you know jsonstream was "funny" let me do that one and open the pull request ...


Can not upgrade to v2.1.0 in HA Mode

rancher/rancher:v2.1.0
Steps to reproduce

Step up Rancher HA follow https://rancher.com/docs/rancher/v2.x/en/installation/ha/rke-add-on/layer-7-lb/
Add a cluster into Rancher
Upgrade Rancher by using kubectl set image

Results:
The cluster state become unavailable in Rancher UI. But everything works well with kubectl
Workaround:
A workaround is changing the value of /v3/settings/peer-service from rancher (or maybe it is empty string) to cattle-service
And need to restart all pods for rancher/rancher .
I think we need to add it in the release note or document

@loganhz  i have update the setting,but it is not useful.

@jiuchongxiao jiu You need to restart all pods for rancher/rancher .

yes ,i had restart docker,so that the all pods restart,and the error always, is it relate with the kubernets version?

@jiuchongxiao jiu can you find me via wechat howl6616, please?

Linked to https://github.com/rancher/docs/issues/869

Direct upgrade from rancher installed via rke addon to HA in 2.1 is not supported. Following steps should be done and tested:

upgrade rke addon install to helm prior to 2.1 upgrade
upgrade to 2.1 using helm (from helm chart to helm chart)

Following needs to be documented:

release note it in the github and forums
update the docs (indicate that migration to helm needs to occur before upgrading to 2.1)

We have decided that we no longer support v2.1 install using the RKE add-on methods. We only support/work with the helm chart install.
This is now documented as expected.
https://github.com/rancher/rancher/issues/16033
Also, our QA team has tested using  RKE add-on install and using our docs to migrate to a helm chart install for 2.1:
If you are currently using the RKE add-on install method, see Migrating from a RKE add-on install for details on how to move to using the helm chart.

@deniseschannon Ok, but RKE will still be used to setup the k8s cluster right? Or do you drop rke alltogether?
And another thing I noted while upgrading: I also upgraded the k8s cluster itself with rke, and noticed that rke is still running the deploy job even so I removed everything from the yaml of the addon section. Does that interfere somehow with the helm installation or is that just fine?

@wzrdtales Yes, RKE is still being used as how to setup your k8s cluster, but using the RKE addon method of installing Rancher is no longer supported.
We just added notes into the docs of migration on how to clean up the addon itself:
https://rancher.com/docs/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/#remove-addons-section-from-rancher-cluster-yml
Did you eliminate the whole addons section or did you leave the addons directive but clear it out? I think you need to do the latter for RKE to realize that there are explicitly no addons and what to remove.

@deniseschannon Yes, I compeltely deleted it, just the server config is there.

Basically just asking if the things that rke still executes in the deploy step collide. As far as I have seen these are setting up the network stack.

Most things also seem to work, except when logging in it is throwing failed to find schema resourceQuotaTemplates: undefined, so something went wrong there, just noticed now.

@wzrdtales that's actually a UI caching error: https://github.com/rancher/rancher/issues/15981


feat: upgrade to Angular 10

Hi,
With this PR the Angular dependency and file structure will be updated to latest (ATM of writing) to latest versions.
I reproduce the structure for the new json introduced in version 10, I mean tsconfig.base.json.
Still a warning (not due to this PR) with angular-hmr... it cause with the version 2.1.3
the common warning
CommonJS or AMD dependencies can cause optimization bailouts.

I made a PR to "solve" this warning with latest angular version https://github.com/PatrickJS/angular-hmr/pull/87
Tested with Angular + Material and Bootstrap as UI
Hope it help
Cordially
Fabio

i published the hmr fixes as 3.0.0

i published the hmr fixes as 3.0.0

Thx PatrickJS

BTW, if you update <preference name="android-minSdkVersion" value="19"/> to <preference name="android-minSdkVersion" value="22"/> in __cordova._config.xml it should fix the CI for the mobile builds.

Change made.

Thanks! Expect a new release with your changes soon 🎉

:tada: This PR is included in version 9.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cascader load-more 开启懒加载之后要怎么回显数据？

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome<IP_ADDRESS>

同问


Run-time manifest type support (e.g. schema1/schema2) autodetection re-vendor + integration tests

This vendors in https://github.com/containers/image/pull/264 and adds integration tests for it.
See the individual commit messages for more details.
Note that the added integration test currently tests OpenShift with acceptschema2:{true,false}; a test against upstream docker/distribution registries (with the s2 and s1 versions already built by Dockerfile) exists, but is disabled because it fails—not on the s2→s1 conversion, but on s1→s1 copies: the s1-only registry requires updating the tag value, which we currently don’t do.
Updating the tag in s1 uploads is actually ready in  https://github.com/containers/image/pull/88 , but it breaks other integration tests (which incorrectly assume that s1 uploads don’t change the manifest) fairly badly, so we will need to update the other tests to support https://github.com/containers/image/pull/88 , and then we can enable the disabled tests in this PR.

@runcom Final version ready for review.

just a question, LGTM otherwise


Feature/split plot

plot -> plot map and add region outlines
plot_regions add region outlines to existing map
Closes #31 and #32

Codecov Report

Merging #41 into master will increase coverage by 0.8%.
The diff coverage is 98.91%.

@@            Coverage Diff            @@
##           master      #41     +/-   ##
=========================================
+ Coverage   97.38%   98.19%   +0.8%
=========================================
  Files          15       15
  Lines         879      940     +61
=========================================
+ Hits          856      923     +67
+ Misses         23       17      -6

Impacted Files
Coverage Δ

regionmask/core/regions.py
91.42% <100%> (+0.08%)
:arrow_up:

regionmask/test/test_plot.py
100% <100%> (ø)
:arrow_up:

regionmask/test/test_Region_cls.py
100% <100%> (+12.82%)
:arrow_up:

regionmask/core/plot.py
98.27% <94.44%> (+1.84%)
:arrow_up:

Continue to review full report at Codecov.

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


AKS - scaling up fails first then recoveries

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

Run Rancher 2.2.0-rc9
add an AKS cluster with k8s v1.11.7 and only 1 node
after the cluster is active, edit it to scale up to 3 nodes

Result:

At first, The aks cluster will show the upgrade fails in the UI
Azure console shows the cluste is scaling and eventually succeeds
after a while, in my case about 15 mins, the AKS goes back to active and show all 3 nodes.

Other details that may be helpful:

This also happens on v.2.1.7
The k8s version should not be a factor becuase in another test upgraing only the k8s version produces the same error

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.2.0-rc9
Installation option (single install/HA): HA

related: https://github.com/rancher/rancher/issues/19115

not new. moving out


Add top delegate weights endpoint

This PR adds an endpoint for exposing the top delegate weights
See GET /api/analytics/top/delegates

PR-Codex overview
The focus of this PR is to add functionality to fetch and return the top delegate weights for analytics.
Detailed summary

Added getTopDelegateWeights function to fetch delegate weights
Implemented caching for delegate weights
Exposed GET function to return delegate weights as JSON
Utilized Prisma for querying delegate weights

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Questions for Reviewers

Do we want to supply the token supply in this same endpoint?  Or a different one?
Any recommendation on the URL? I'm trying to forecast other analytics we might one day expose, and possibly make things parametrized.


Swift 3

compatibility with swift 3

Duplicate of https://github.com/MailOnline/ImageViewer/issues/43


Better determine concurrency from host environment to use for JavaTestRunner

JavaTestRunner can use too high a concurrency based purely on CPU count, if such a host has insufficient memory it can cause memory starvation and Jenkins channel failures.
This PR based off the logic used in openjdk/openjdk.mk, optimises the concurrency to min(CPUs,MemInGb)
Signed-off-by: Andrew Leonard<EMAIL_ADDRESS>

Test Grinders on various hosts:
160 core 512Gb Aarch64 Linux:
11:32:38  ../jck.mk:147: Jck concurrency determined from host environment OS=Linux, CPUs=160, Memory=501 Gb. Using concurrency=160

@andrew-m-leonard , Hi Andrew, thanks for this improvement. Could we please run a test on Windows to ensure all is well there?

@andrew-m-leonard , Hi Andrew, thanks for this improvement. Could we please run a test on Windows to ensure all is well there?

Thanks, just doing that now...

Tested on Windows, looks fine:
11:07:54  ../jck.mk:151: Jck concurrency determined from host environment OS=CYGWIN_NT-10.0, CPUs=8, Memory=15 Gb. Using concurrency=8

@Mesbah-Alam so interesting the memory size calc fails on Windows, which is odd as I copied it from openjdk.mk, then realized it doesn't work there anyway ! https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_hs_sanity.openjdk_x86-64_windows/697/consoleFull

I'll try and fix both...

@Mesbah-Alam should be fixed, also fixed openjdk.mk and added missing AIX logic there too:
openjdk tests:
Windows: https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_hs_sanity.openjdk_x86-64_windows/698/
AIX: https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk11_j9_sanity.openjdk_ppc64_aix/490/
Running jck test as well

Can this still be overridden when you run the job in jenkins? Have we seen a failure due to this on any machines other than the Skytap AIX ones, and have we looked to see if it's really an out of memory situation or is that just a guess at present? If we can't utilise all the cores we have we should consider adjusting the specification of the machines accordingly.
Could one process for every 512Mb of RAM be used instead (1Gb seems generous to me) this making a 32-core 8Gb system use concurrency=16 by default
(Also as an aside I'm a bit worried that we're duplicating quite a lot of logic between here and other places where such a detection occurs)

Yes, can be overridden
Suspicion yes, but i've done multiple tests with lower concurrency and failures have not occurred, so seems likely on AIX.
I have suspicion on other platforms too, Alpine one mentioned earlier.

@sxa Some tests do need a lot of memory, some of the compiler tests especially.

@andrew-m-leonard , Interestingly, it worked at my end on x64 Windows before you updated the PR, Grinder_JCK/979:
11:07:52  ../jck.mk:36: Running under cygwin, looking for Windows perl on path
11:07:53  ../jck.mk:41: Found perl in /cygdrive/c/Strawberry/perl/bin/perl.exe
11:07:54  ../jck.mk:151: Jck concurrency determined from host environment OS=CYGWIN_NT-10.0, CPUs=8, Memory=15 Gb. Using concurrency=8
11:07:55
11:07:55  ===============================================
11:07:55  Running test jck-compiler-api-javax_annotation_0 ...
11:07:56  ===============================================
11:07:57  jck-compiler-api-javax_annotation_0 Start Time: Fri Dec  9 08:07:21 2022 Epoch Time (ms):<PHONE_NUMBER>491
11:07:57  variation: NoOptions
11:07:57  JVM_OPTIONS:

Thanks for fixing it at your end!

The reporting of 32 processors on AIX using the lcpu value is probably not a good one to use. The machine that threw up the problem we're looking to resolve here has 4 CPUs with 8 threads/CPU (SMT8) which shows as 32 lcpus. While the optimal number is potentially somewhere between 4 and 32, I would suggest that perhaps we should only override this for AIX, and either use the real number of processors (Ideally plus one) or some other combination which takes into account the threading multiplier.
To get the number of CPUs on AIX use: lparstat -i | awk '/Online Virtual CPUs/{print$NF}'
We should probably also change this wherever the test harness decides on it it instead of exclusively for the JCK since the autodetected value is probably not optimal for highly threaded processors.

@sxa it's worth bearing in mind the JTreg openjdk tests are even more generous:
https://github.com/adoptium/aqa-tests/blob/61596d279e5f443c524aa0688cb2ddf371c33921/openjdk/openjdk.mk#L47
So an 32cpu 8Gb machine would use concurrency=4 for openjdk jtreg tests.
I do think some of the intermittent jck problems are because the higher concurrency obviously consumes more resource, but also lines up the higher chance of some of the high memory/longer running individual tests coinciding with other high memory ones.
I'd like us to give back some more generous room, so as to see the affect, hopefully a positive one. If we just ease back a little, we will probably still see those issues, and dismiss this as the problem.

The reporting of 32 processors on AIX using the lcpu value is probably not a good one to use. The machine that threw up the problem we're looking to resolve here has 4 CPUs with 8 threads/CPU (SMT8) which shows as 32 lcpus. While the optimal number is potentially somewhere between 4 and 32, I would suggest that perhaps we should only override this for AIX, and either use the real number of processors (Ideally plus one) or some other combination which takes into account the threading multiplier.
To get the number of CPUs on AIX use: lparstat -i | awk '/Online Virtual CPUs/{print$NF}'
We should probably also change this wherever the test harness decides on it it instead of exclusively for the JCK since the autodetected value is probably not optimal for highly threaded processors.

@sxa As you say those AIX nodes seem more than 4 CPU capable, I would hope the 32 lcpu value is representable of its capability, otherwise what's the point of that value?

The reporting of 32 processors on AIX using the lcpu value is probably not a good one to use. The machine that threw up the problem we're looking to resolve here has 4 CPUs with 8 threads/CPU (SMT8) which shows as 32 lcpus. While the optimal number is potentially somewhere between 4 and 32, I would suggest that perhaps we should only override this for AIX, and either use the real number of processors (Ideally plus one) or some other combination which takes into account the threading multiplier.
To get the number of CPUs on AIX use: lparstat -i | awk '/Online Virtual CPUs/{print$NF}'
We should probably also change this wherever the test harness decides on it it instead of exclusively for the JCK since the autodetected value is probably not optimal for highly threaded processors.

I'm tempted to leave it base on the AIX lcpu, since it gives a concurrency of 8, which I think is about right ?

We should probably also change this wherever the test harness decides on it it instead of exclusively for the JCK since the autodetected value is probably not optimal for highly threaded processors.
@sxa As you say those AIX nodes seem more than 4 CPU capable, I would hope the 32 lcpu value is representable of its capability, otherwise what's the point of that value?

That's a long complex processor architecture question and it depends on the workload :-) I would be very surprised if there was any point in running 32 but in the interests of finding out:
Grinders 2183 through 2186 are running the sanity suite on the machine with concurrencies set to default (32), 16, 8 and 4 respectively.

Grinders 2183 through 2186 are running the sanity suite on the machine with concurrencies set to default (32), 16, 8 and 4 respectively.

@sxa the time variation might be interesting. I can only elude to which might be high memory tests, a number of the compiler tests use deep recursion scenarios, but they are mainly extended suite.

Grinders 2183 through 2186 are running the sanity suite on the machine with concurrencies set to default (32), 16, 8 and 4 respectively.

Those disappeared, so I'll post the results of another test with a couple of suites to give an idea of the difference caused by different concurrency values on a Skytap 4-core, SMT8 system:

concurrency
Execution time

35 (default)
34m09

16
40m06

8
52m58

5
1h07

4
1h13

Dropping from a concurrency value of 35 to 8 would give a 50% increase in runtime under this scenario.

Grinders 2183 through 2186 are running the sanity suite on the machine with concurrencies set to default (32), 16, 8 and 4 respectively.

Those disappeared, so I'll post the results of another test with a couple of suites to give an idea of the difference caused by different concurrency values on a Skytap 4-core, SMT8 system:
concurrency 	Execution time
35 (default) 	34m09
16 	40m06
8 	52m58
5 	1h07
4 	1h13
Dropping from a concurrency value of 35 to 8 would give a 50% increase in runtime under this scenario.

Interesting thanks @sxa
So i'd err on the side of not thrashing the machine at the risk of causing failures or crippling the machine or agent, so 16 or 8 would be my suggested target, probably 8 to try and ensure consistent Green runs

@sxa going to keep log of expected process termination/errors here...

https://ci.eclipse.org/temurin-compliance/job/Test_openjdk8_hs_extended.jck_ppc64_aix/51/console:
16:18:33  testsuite "/home/jenkins/jck_root/JCK8-unzipped/JCK-runtime-8c";
16:18:33  workDirectory -create -overwrite /home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/workdir;
16:18:33  tests api/java_util;
16:18:33  concurrency 33;
16:18:33  timeoutfactor 4;
16:18:33  keywords !interactive;
16:18:33  set jck.env.testPlatform.os "other";
16:18:33  set jck.env.testPlatform.fileSep "/";
16:18:33  set jck.env.testPlatform.pathSep ":";
16:18:33  set jck.env.runtime.testExecute.cmdAsString "/home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/openjdkbinary/j2sdk-image/bin/java";
16:18:33  set jck.env.runtime.testExecute.otherOpts "   -Djava.ext.dirs=/home/jenkins/jck_root/JCK8-unzipped/JCK-runtime-8c/lib/extensions:/home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/openjdkbinary/j2sdk-image/jre/lib/ext -Djava.security.properties=/home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/security.properties ";
16:18:33  set jck.excludeList.customFiles "/home/jenkins/jck_root/JCK8-unzipped/JCK-runtime-8c/lib/jck8c.jtx   /home/jenkins/jck_run/jdk8/aix/temurin.jtx  ";
16:18:33  runTests;
16:18:33  writeReport -type xml /home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/report;
16:18:33  <<<<<<<<
16:18:33  Starting sub-process: com.sun.javatest.agent.AgentMain
16:18:33  Full command: [/home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/openjdkbinary/j2sdk-image/bin/java, -Djavatest.security.allowPropertiesAccess=true, -Djava.security.policy=/home/jenkins/jck_root/JCK8-unzipped/JCK-runtime-8c/lib/jck.policy, -classpath, /home/jenkins/jck_root/JCK8-unzipped/JCK-runtime-8c/lib/javatest.jar:/home/jenkins/jck_root/JCK8-unzipped/JCK-runtime-8c/classes, com.sun.javatest.agent.AgentMain, -passive]
16:18:33  Starting sub-process: tnameserve
16:18:33  Full command: [/home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/openjdkbinary/j2sdk-image/bin/tnameserv, -ORBInitialPort, 9876]
16:18:33  Running JCK in multijvm way with Agent off
16:18:33  Starting sub-process: jck
16:18:33  Full command: [/home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/openjdkbinary/j2sdk-image/bin/java, -jar, /home/jenkins/jck_root/JCK8-unzipped/JCK-runtime-8c/lib/javatest.jar, -config, /home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/../jck/jtrunner/config/jck8c/runtime.jti,  @/home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/JTB/generated.jtb]
16:18:33  Initial Naming Context:
16:18:33  IOR:000000000000002b49444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e30000000000001000000000000009a000102000000000e32302e36312e3133362e32313300269400000045afabcb0000000020000f424000000001000000000000000200000008526f6f74504f41000000000d544e616d65536572766963650000000000000008000000010000000114000000000000020000000100000020000000000001000100000002050100010001002000010109000000010001010000000026000000020002
16:18:33  TransientNameServer: setting port for initial object references to: 9876
16:18:33  Ready.
16:18:36  Dec 10, 2022 4:18:35 PM Harness starting test run with configuration "jck_runtime"...
16:20:44  gmake[1]: *** Waiting for unfinished jobs....
16:20:44  gmake[2]: *** Waiting for unfinished jobs....
16:20:44  gmake[4]: *** Waiting for unfinished jobs....
16:20:44  gmake[3]: *** Waiting for unfinigmake: *shed job** Waitis....
16:20:44  ng for u[thread 515 also had an error]
16:20:44  [thread 1543 also had an error]
16:20:44  [thread 772 also had an error]
16:20:44  nfinished jobs....
16:20:44  #
16:20:44  # A fatal error has been detected by the Java Runtime Environment:
16:20:44  #
16:20:44  #  SIGDANGER (0x21) at pc=0x090000000052c8c4, pid=5243026, tid=0x0000000000000203
16:20:44  #
16:20:44  # JRE version: OpenJDK Runtime Environment (8.0_362-b05) (build 1.8.0_362-b05)
16:20:44  # Java VM: OpenJDK 64-Bit Server VM (25.362-b05 mixed mode aix-ppc64 compressed oops)
16:20:44  # Problematic frame:
16:20:44  # C  [libpthread.a+0xffffffff]  _event_sleep+0x584
16:20:44  #
16:20:44  # Core dump written. Default location: /home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/core or core.5243026
16:20:44  #
16:20:44  #
16:20:44  # A fatal error has been detected by the Java Runtime Environment:
16:20:44  #
16:20:44  #  SIGDANGER (0x21) at pc=0x0900000000530a44, pid=10813640, tid=0x0000000000000304
16:20:44  #
16:20:44  # JRE version: OpenJDK Runtime Environment (8.0_362-b05) (build 1.8.0_362-b05)
16:20:44  # Java VM: OpenJDK 64-Bit Server VM (25.362-b05 mixed mode aix-ppc64 compressed oops)
16:20:44  # Problematic frame:
16:20:44  # C  [libpthread.a+0xffffffff]  _sigsetmask+0xe4
16:20:44  #
16:20:44  # Core dump written. Default location: /home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/core or core.10813640
16:20:44  #
16:20:44  #
16:20:44  # A fatal error has been detected by the Java Runtime Environment:
16:20:44  #
16:20:44  #  SIGDANGER (0x21) at pc=0x090000000052c8c4, pid=17563792, tid=0x0000000000000203
16:20:44  #
16:20:44  # JRE version: OpenJDK Runtime Environment (8.0_362-b05) (build 1.8.0_362-b05)
16:20:44  # Java VM: OpenJDK 64-Bit Server VM (25.362-b05 mixed mode aix-ppc64 compressed oops)
16:20:44  # Problematic frame:
16:20:44  # C  [libpthread.a+0xffffffff]  _event_sleep+0x584
16:20:44  #
16:20:44  # Core dump written. Default location: /home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/core or core.17563792
16:20:44  #
16:20:44  # An error report file with more information is saved as:
16:20:44  # /home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/hs_err_pid17563792.log
16:20:44  #
16:20:44  # A fatal error has been detected by the Java Runtime Environment:
16:20:44  #
16:20:44  #  SIGDANGER (0x21) at pc=0x090000000052c8c4, pid=21692638, tid=0x0000000000000203
16:20:44  #
16:20:44  # JRE version: OpenJDK Runtime Environment (8.0_362-b05) (build 1.8.0_362-b05)
16:20:44  # Java VM: OpenJDK 64-Bit Server VM (25.362-b05 mixed mode aix-ppc64 compressed oops)
16:20:44  # Problematic frame:
16:20:44  # C  [libpthread.a+0xffffffff]  _event_sleep+0x584
16:20:44  #
16:20:44  # Core dump written. Default location: /home/jenkins/workspace/Test_openjdk8_hs_extended.jck_ppc64_aix/aqa-tests/TKG/output_16706762027040/jck-runtime-api-java_util_0/core or core.21692638
16:20:44  #

23:30:43  testsuite "/home/jenkins/jck_root/JCK11-unzipped/JCK-compiler-11";
23:30:43  workDirectory -create -overwrite /home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/aqa-tests/TKG/output_16706959873197/jck-compiler-lang-EXPR-group3_0/workdir;
23:30:43  tests lang/EXPR/expr138 lang/EXPR/expr139 lang/EXPR/expr140 lang/EXPR/expr142 lang/EXPR/expr143 lang/EXPR/expr144 lang/EXPR/expr146 lang/EXPR/expr148 lang/EXPR/expr149 lang/EXPR/expr150 lang/EXPR/expr151 lang/EXPR/expr152 lang/EXPR/expr153 lang/EXPR/expr154 lang/EXPR/expr155 lang/EXPR/expr156 lang/EXPR/expr157 lang/EXPR/expr158 lang/EXPR/expr159 lang/EXPR/expr160 lang/EXPR/expr161 lang/EXPR/expr162 lang/EXPR/expr163 lang/EXPR/expr164 lang/EXPR/expr165 lang/EXPR/expr166 lang/EXPR/expr167 lang/EXPR/expr168 lang/EXPR/expr169 lang/EXPR/expr170 lang/EXPR/expr171 lang/EXPR/expr172 lang/EXPR/expr173 lang/EXPR/expr174 lang/EXPR/expr175 lang/EXPR/expr176 lang/EXPR/expr177 lang/EXPR/expr178 lang/EXPR/expr179 lang/EXPR/expr180 lang/EXPR/expr181 lang/EXPR/expr182 lang/EXPR/expr183 lang/EXPR/expr184 lang/EXPR/expr185 lang/EXPR/expr186 lang/EXPR/expr187 lang/EXPR/expr188 lang/EXPR/expr189 lang/EXPR/expr190 lang/EXPR/expr191 lang/EXPR/expr192 lang/EXPR/expr193 lang/EXPR/expr194 lang/EXPR/expr195 lang/EXPR/expr196 lang/EXPR/expr197 lang/EXPR/expr198 lang/EXPR/expr199 lang/EXPR/expr200 lang/EXPR/expr201 lang/EXPR/expr202 lang/EXPR/expr203 lang/EXPR/expr204 lang/EXPR/expr205 lang/EXPR/expr206;
23:30:43  concurrency 3;
23:30:43  timeoutfactor 4;
23:30:43  keywords compiler;
23:30:43  set jck.env.testPlatform.os "other";
23:30:43  set jck.env.testPlatform.fileSep "/";
23:30:43  set jck.env.testPlatform.pathSep ":";
23:30:43  set jck.env.compiler.testCompile.testCompileAPImultiJVM.cmdAsString "/home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/openjdkbinary/j2sdk-image/bin/java";
23:30:43  set jck.env.compiler.testCompile.otherOpts "-source 11 ";
23:30:43  set jck.env.compiler.compRefExecute.cmdAsString "/home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/openjdkbinary/j2sdk-image/bin/java";
23:30:43  set jck.env.compiler.compRefExecute.otherOpts "   ";
23:30:43  set jck.excludeList.customFiles "/home/jenkins/jck_root/JCK11-unzipped/JCK-compiler-11/lib/jck11.jtx   /home/jenkins/jck_run/jdk11/linux/temurin.jtx  ";
23:30:43  runTests;
23:30:43  writeReport -type xml /home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/aqa-tests/TKG/output_16706959873197/jck-compiler-lang-EXPR-group3_0/report;
23:30:43  <<<<<<<<
23:30:43  Running JCK in multijvm way with Agent off
23:30:43  Starting sub-process: jck
23:30:43  Full command: [/home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/openjdkbinary/j2sdk-image/bin/java, -jar, /home/jenkins/jck_root/JCK11-unzipped/JCK-compiler-11/lib/javatest.jar, -config, /home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/aqa-tests/TKG/../jck/jtrunner/config/jck11/compiler.jti,  @/home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/aqa-tests/TKG/output_16706959873197/jck-compiler-lang-EXPR-group3_0/JTB/generated.jtb]
23:30:47  Dec 10, 2022, 11:30:46 PM Harness starting test run with configuration "jck_compiler"...
23:33:18  make[4]: *** [autoGen.mk:425: jck-compiler-lang-EXPR-group3_0] Terminated
23:33:18  make[3]: *** [/home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/aqa-tests/TKG/../TKG/settings.mk:356: extended.jck-compiler.lang] Terminated
23:33:18  make[2]: *** [/home/jenkins/workspace/Test_openjdk11_hs_extended.jck_x86-64_alpine-linux/aqa-tests/TKG/../TKG/settings.mk:356: extended.jck-jck] Terminated
23:33:18  make[1]: *** [settings.mk:356: extended.jck-..] Terminated
23:33:18  make: *** [makefile:50: _extended.jck] Terminated
23:33:18  Terminated

Do we want/need this PR, or close it?

JTRunner currently only uses CPU number as the basis of concurrency, we are happy that given a correctly configured infrastructure that using just that works.


redux-form 6.1.0 Warning: Unknown prop meta on

when I run the example of react-widgets , It has warnings, since I found the same issue has fixed ^ 6.1.0 ?  but I when I run still found this...
warning.js:36 Warning: Unknown prop `meta` on <div> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in div (created by Widget)
    in Widget (created by DropdownList)
    in DropdownList (created by Uncontrolled(DropdownList))
    in Uncontrolled(DropdownList) (created by renderDropdownList)
    in renderDropdownList (created by ConnectedField)
    in ConnectedField (created by Connect(ConnectedField))
    in Connect(ConnectedField) (created by Field)
    in Field (created by ReactWidgetsForm)
    in div (created by ReactWidgetsForm)
    in form (created by ReactWidgetsForm)
    in ReactWidgetsForm (created by Form(ReactWidgetsForm))
    in Form(ReactWidgetsForm) (created by Connect(Form(ReactWidgetsForm)))
    in Connect(Form(ReactWidgetsForm)) (created by ReduxForm)
    in ReduxForm
    in div (created by b)
    in div (created by b)
    in div (created by b)
    in div (created by b)
    in b
    in Provider

something wrong with my version?

Not a real solution but manually modifying node_modules/react-widgets/lib/Widget.js (line 46) and adding meta prop fixed the warning for me.
var props = _objectWithoutProperties(_props, ['meta', 'className', 'tabIndex', 'open', 'dropUp', 'disabled', 'readOnly', 'focused']);
"react": "15.3.2",
"react-widgets": "3.4.4",
"redux-form": "6.1.0",

I changed function:
  const renderDropdownList = ({ input, meta, ...rest }) =>
      <DropdownList {...input} {...rest} />

@gustavohenke I tried using the updated example as you have linked to and still received the same error message. However that disappeared when I tried @n0ne 's solution. Just a heads up

Will fix this in the docs.

@erikras, while looking at the examples in order to fix this, I discovered that the code is very different to what is shown in the docs.
See:

https://github.com/erikras/redux-form/blob/v6.5.0/examples/react-widgets/src/ReactWidgetsForm.js
http://redux-form.com/6.5.0/examples/react-widgets/

I'm getting the same warning, but not doing anything related to react-widgets. Should I open a new issue and post my code there?

It seems like this was really fixed in earlier versions of the docs.


[CELEBORN-1292] Remove APP level metrics since it cause heavy performanc issue

What changes were proposed in this pull request?
Remove APP level metrics since it cause heavy performanc issue
Why are the changes needed?
Remove APP level metrics since it cause heavy performanc issue
Does this PR introduce any user-facing change?
Remove app level metrics
How was this patch tested?

@AngersZhuuuu, could you describe the performance problem in description? BTW, why revert application level metrics of master and worker? Did you have performance problem in worker?


Edge compatibility

Because of the spread operator, the whole project breaks on Edge. It only represents 2% of the browsers used, but I think this simple change should be made for compatibility.

The change is up and running.
Thanks for your contribution.


Interoperability with "new" ST app?

Any testing with the "new" ST App everyone is being forced to migrate to?

ya, the testing is fubar.  Samsung's new and improved app has added nothing new, but broke a lot of things that did work, like this one.

btw, didn't mean the code owners testing, I met the results from my testing of it after being forced onto the new smartthings...it went all fubar :(

So it definitely doesn't work with the new? I had this working but I couldn't remember how I got it to actually work. Now I just think I'm spinning in circles

Any thoughts here @sgupta999 or have you really moved on from this project?

I don’t really know if it works or not - like I said my whole environment is down. Some of the other device handlers have some features that work and some that don’t.
I haven’t looked at anything for a while
Sent from my iPhone

On Nov 12, 2020, at 11:58 PM, Josh Bernstein<EMAIL_ADDRESS>wrote:

Any thoughts here @sgupta999 or have you really moved on from this project?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm not sure entirely how yet. But I can comment that this codebase does seem to be working with the new Smartthings (ST) app

@sgupta999 I think this issue at least can be closed

agreed. I think it can be closed. But I think perhaps you forgot to close it @sgupta999