Move to image-rs

https://github.com/image-rs

I'm ok with that.
GitHub doesn't allow to do that by myself though:

Transfer ownership
Organization members cannot transfer repositories

I will transfer the ownership in 24 hours, unless there are any objections.

Transferred.

Thanks. Should we also:
cargo owner -r github:pistondevelopers:publish
cargo owner -a github:image-rs:publish

I am unable to do that too.

I've added the Publish team, removed the Piston Publish team.

I'm inviting @HeroicKatora and @fintelia as owners, so there are two private owners in case anything unexpected happens when I remove myself.

Thanks.


sim3u167bgm SOC support

Introduction
GARDENA uses a sim3u167bgm module in their smart Gateway and I've ported zephyr to it. The work is already done in terms of what is needed for that product and we want to mainline this now so others can benefit from it as well.
Problem description
Support for the SOC, GARDENAs SOM and every driver it's currently using should be merged.
Proposed change
This issue serves as an overview of this port and will link to all related PRs.
Detailed RFC
In this section of the document the target audience is the dev team. Upon
reading this section each engineer should have a rather clear picture of what
needs to be done in order to implement the described feature.
HAL
The port used silab's SI32 HAL from the Precision32 IDE.
This is only used for the register definitions. The drivers are fully zephyr-native.
It might be worth taking a look at the license That's linked to in every file's copyright header.
Drivers
We currently only intend to add support for drivers that we need. See the task list for a list of which ones we wrote.
There won't be a pinctrl driver since the hardware is too limited for that(you can't change the config at runtime without temporarily disconnecting all pins), but my port allows using pinctrl devicetree nodes to define the initial configuration.
Board
The intention is to only add support for the GARDENA smart gateway. It's readily available and can be used by anyone to develop software because root access is provided by default via UART. SPI, USART0, a few GPIOs, the reset pin and SWD are connected to the Linux SoC.
If it's a hard requirement to support Silabs official development board as well we can do that but it's currently not planned.
Dependencies
None that aren't already mainline. The PRs will contain everything that's needed.
Concerns and Unresolved Questions

[ ] HAL license compatibility
[ ] do we need to support the official devkit?

Task List

[ ] add si32 HAL to hal_silabs
[ ] add AHB clock control driver
[ ] add APB clock control driver
[ ] add PLL clock control driver
[ ] add flash driver
[ ] add GPIO driver for ports 0-3
[ ] add GPIO driver for port 4 (high drive)
[ ] add USART driver
[ ] add SPI  driver
[ ] add sim3u167bgm SOC
[ ] add GARDENA board

About the license, this is the comment header from the source files:
//------------------------------------------------------------------------------
// Copyright (c) 2012 by Silicon Laboratories.
// All rights reserved. This program and the accompanying materials
// are made available under the terms of the Silicon Laboratories End User
// License Agreement which accompanies this distribution, and is available at
// http://developer.silabs.com/legal/version/v10/License_Agreement_v10.htm
// Original content and implementation provided by Silicon Laboratories.
//------------------------------------------------------------------------------

This is the "Silicon Laboratories End User License Agreement which accompanies this distribution" (Documentation/Silabs_License_Agreement.txt):
Silabs_License_Agreement.txt
This is what you can find at http://developer.silabs.com/legal/version/v10/License_Agreement_v10.htm as of today (2023-02-03):
END-USER LICENSE AGREEMENT
IMPORTANT:  READ CAREFULLY
BEFORE AGREEING TO TERMS

THIS PRODUCT CONTAINS CERTAIN COMPUTER PROGRAMS AND OTHER THIRD PARTY PROPRIETARY MATERIAL ("LICENSED PRODUCT"), THE USE OF WHICH IS SUBJECT TO THIS END-USER LICENSE AGREEMENT.    ("SILICON LABS") SHALL BE CONSTRUED AS AN INFERENCE TO THE CONTRARY. IF THESE TERMS ARE CONSIDERED AN OFFER BY SILICON LABS, ACCEPTANCE IS EXPRESSLY LIMITED TO THESE TERMS.

LICENSE AND WARRANTY: The Licensed Product and the embedded Software which is made the subject of this License is either the property of SILICON LABS or a third party from whom SILICON LABS has the authorization to distribute to you subject to the terms of this Agreement. This Licensed Product is protected by state, federal, and international copyright law. Although SILICON LABS continues to own the Licensed Product and the right to distribute the embedded third party Software, you will have certain rights to use the Licensed Product and the embedded Software after your acceptance of this License. Except as may be modified by a license addendum which accompanies this License, your rights and obligations with respect to the use of this Product and the embedded software are as follows:

1. AS APPROPRIATE WITH RESPECT TO THE LICENSED PRODUCT, YOU MAY: Use, copy, distribute and make derivative works of the Software for any purpose, including commercial applications, subject to the following restrictions: (i) The origin of this software must not be misrepresented; (ii) you must not claim that you wrote the original software; (iii) altered source versions must be plainly marked as such, and must not be misrepresented as being the original software; and (iv) any notices contained in the Software may not be removed or altered, including notices in source code versions.

2. YOU MAY NOT: (A) Sublicense, assign, rent or lease any portion of the Licensed Product or the embedded Software; or (B) Remove any product identification, copyright or other notices that appear on the Licensed Product or embedded Software.

3. Limited Use: Use of any of the Software is strictly limited to use in systems containing one or more SILICON LABS products when the Software is enabled to be functional. Any unauthorized use is expressly prohibited and will constitute a breach of this Agreement.

4. Warranty: SILICON LABS does not warrant that the Licensed Product or embedded Software will meet your requirements or that operation of the Licensed Product will be uninterrupted or that the embedded Software will be error-free. You agree that the Licensed Product is provided "AS IS" and that SILICON LABS makes no warranty as to the Licensed Product or embedded Software.

YOU MAY HAVE OTHER RIGHTS, WHICH VARY FROM STATE TO STATE.

5. Disclaimer of Damages: IN NO EVENT WILL SILICON LABS BE LIABLE TO YOU FOR ANY SPECIAL, CONSEQUENTIAL, INDIRECT, OR SIMILAR DAMAGES, INCLUDING ANY LOST PROFITS OR LOST DATA ARISING OUT OF THE USE OR INABILITY TO USE THE LICENSED PRODUCT EVEN IF SILICON LABS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES. SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.

IN NO CASE SHALL SILICON LABS' LIABILITY EXCEED THE PURCHASE PRICE FOR THE LICENSED PRODUCT. The disclaimers and limitations set forth above will apply regardless of whether you accept the Licensed Software.

6. Term and Termination: The term of this Agreement and the License granted herein shall begin upon use of the Licensed Product and continue in perpetuity unless you breach any of the obligations set out under this Agreement. Upon your breach of this Agreement by you, the license granted hereunder shall terminate immediately and you shall cease all use of the Licensed Products and return same as well as any copies of the Licensed Product and/or embedded Software to SILICON LABS immediately. Termination of this License upon your breach is only one remedy available to SILICON LABS. In addition to termination of this Agreement upon your breach, SILICON LABS shall be entitled to seek any and all other available remedies, at law or at equity, arising from your breach.

7. Export: You shall comply with all applicable federal, provincial, state and local laws, regulations and ordinances including but not limited to applicable U.S. Export Administration Laws and Regulations. You shall not export or re-export, or allow the export or re-export of the Licensed Product, any component of the Licensed Product, or any copy of the embedded Software in violation of any such restrictions, laws or regulations, or to Cuba, Libya, North Korea, Iran, Iraq, or Rwanda or to any Group D:1 or E:2 country (or any national of such country) specified in the then current Supplement No. 1 to Part 740, or, in violation of the embargo provisions in Part 746, of the U.S. Export Administration Regulations (or any successor regulations or supplement), except in compliance with and with all licenses and approvals required under applicable export laws and regulations, including without limitation, those of the U.S. Department of Commerce.

8. General: This Agreement will be governed by the laws of the State of Texas and any applicable federal laws or regulations. The waiver by either Party of any default or breach of this Agreement shall not constitute a waiver of any other or subsequent default or breach. This Agreement constitutes the complete and exclusive statement of the mutual understanding between you and SILICON LABS with respect to this subject matter herein. This Agreement may only be modified by a written addendum, which has been signed by both you and SILICON LABS. Should you have any questions concerning this Agreement, or if you desire to contact SILICON LABS for any reason, please write:

Silicon Laboratories, Inc.
400 West Cesar Chavez
Austin, Texas 78701, U.S.A.

While the distributed license is proprietary since it says things like Use only one copy of any version of the Licensed Product, the online version seems like a custom, yet permissive license with phrases like YOU MAY: Use, copy, distribute and make derivative works of the Software. That means They've updated the License behind that URL at some point even though it still has the same URL, name and version. I don't know what this means legally or what Silicon Labs' stance is on this but I guess the safest way is to assume that the shipped license has priority which would mean that we can't use the HAL.
Unless an official Silicon Labs representative steps in and gives their green light I don't think we can merge this.
I might pick up on Christian Taedckes work for generating an SVD from the reference manual instead and adjust my drivers accordingly. The change should be minimal given both the HAL and the SVD provide 1:1 register abstractions. I'd also be able to verify the results by comparing the resulting binaries.
Any comments on that?
CC: @chrta

FYI: I notified GARDENAs SiLabs FAE on 2023-03-02 about this issue. SiLabs sent a question back about the HAL version used on 2023-04-28, which we answered the same day.
Will post updates here once things progress.

I am a Silicon Labs employee.  I've checked with our legal team and it is their opinion that the newer license (linked in the header files) applies to the HAL files, and it is ok to port code with the Si32 HAL register definitions to the Zephyr OS project.  Please let me know if you have any questions.
Best regards,
Joe Stine

Thanks a lot. I've created the HAL-PR and linked it in this issues description. I've also added a link to the full code of the current port.

Hi @M1cha,
I am a Silicon Labs employee. I've checked with our legal team and they approve Gardena applying a ZLIB license to the code in the si32Hal folder for the Zephyr OS project. So you can adapt or modify the files to include the ZLIB license instead of the current license text.
Below is the ZLIB license text to use in the headers for the si32Hal folder:
Copyright 2012 (c) Silicon Laboratories Inc.
This siHAL software is provided 'as-is', without any express or implied warranty.  In no event will the authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

This notice may not be removed or altered from any source distribution.

Please let me know if you have any questions.
Best regards,
Spurthi

@github-actions I'm still working on it.

I did some work on this and created two up-to-date PRs which (hopefully) address all previous problems:

https://github.com/zephyrproject-rtos/hal_silabs/pull/66
https://github.com/zephyrproject-rtos/zephyr/pull/76677


Updated the workflow to restart the app service once the setting has changed

Description
Updated the workflow to restart the app service once the setting has changed
Ticket number (if applicable)
How Has This Been Tested?
N/A
Screenshots
N/A
Checklist:

[x] My code follows the standards used within this project
[x] I have performed a self-review of my code
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests (Unit, E2E) that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Closing as covered in https://github.com/DFE-Digital/check-an-early-years-qualification/pull/419


Support for Swift 3.0

Support for Swift 3.0

Looks good! 👍

Not sure whether @tadija is happy with the change in code style. 😄

Thanks for this, but PR#77 is more up to date, so I'll merge that one.


Glitch starter project should have all references to 'HyperDev' changed to 'glitch'

This issue is not actually in the codebase but it is part of the curriculum. The Glitch starter project should have all references to 'HyperDev' changed to 'glitch'. @QuincyLarson may have to do this one and it may not be high priority.

@Bouncey I think this should be closed and a new issue be opened on the curriculum repo?


Preprocess Datasets for Trajectron

hi @BorisIvanovic how do you preprocess the datasets? I from the mean you take the x, y, vx, vy and ax, ay (please correct me if I am wrong) but what is standard deviation(does it record the history of the pedestrian and then calculates the std deviation)?
If possible can you share the data preprocessing code as well please?

Thanks @saranshvora for the reminder! I forgot to upload it in the recent update to the codebase, and have fixed this now. You can find it here: https://github.com/StanfordASL/Trajectron/blob/master/sgan-dataset/format_data.py

Hi, @BorisIvanovic  great thank you :) no problem :)


Photos from connection not showing in matrix stream.

From @Gadget-Guru on December 6, 2013 1:6
Some connections can view the photos in their matrix stream, but some cannot.
Magic-Auth Diagnostic returns:
Local Setup returns: Array
(
[success] => 1
[url] => https://redmtx.com/post/?f=&auth=seth%40sethmartin.us&sec=f08f25468ea664e6f01863caec092bfa6aa303d1f99050bab4a02069edb495da&dest=https%3A%2F%2Fredmtx.com%2Fphoto%2F8a158fd395da35ad63a51d881b79ec79-2.jpg&version=1
[message] => token f08f25468ea664e6f01863caec092bfa6aa303d1f99050bab4a02069edb495da created for channel 1 for url https://redmtx.com
)
Remote site responded:
Copied from original issue: friendica/red#226

From @friendica on December 6, 2013 1:51
You will have to wait for redmtx to update as it doesn't yet know how to send debugging info back to you.

From @friendica on December 18, 2013 0:29
I believe this is working as designed. Other examples of magic-auth failures encountered in conversations are all reporting magic-auth success with mod_authtest. So we are probably looking in the wrong place and instead need to verify permissions.

From @Gadget-Guru on December 6, 2013 18:36
This is at the bottom of Magic-Auth Diagnostic:
Success

)

While logged in to my site, If I open a new browser tab and enter https://redmtx.com/channel/paolo, I get "Sorry, you don't have the permission to view this profile", "Permission denied" and "Requested channel is not available."
If I click on paolo's name (tuscanhobbit) from within my matrix and then click "New Window", everything is fine.

From @friendica on December 19, 2013 21:47
No this is the result of version skew. The message was changed from "Success" to "Authentication Success!" which we are looking for from the remote end. If we don't see that exact string we print "Autentication Failed!" on the local side. The string was changed because some folks have reported the '[success]' protocol strings which indicate intermediate steps were successful, but the total exchange may not be.
tazmandevil.info is using older code which just responds "Success" so it isn't string matching correctly on the other side. But the authentication was in fact successful. The hope is that the messages will be much clearer once everybody upgrades.

From @Gadget-Guru on December 19, 2013 15:49
Authtest ends a little differently for this one: https://red.tazmandevil.info/photo/0ae0545536fb6043edb39c8ddd9c663b-2.jpg
Success

)
Authentication Failed!

From @Gadget-Guru on January 16, 2014 8:21
It turns out that allowing third-party cookies is the solution. Restricted cookie management causes forbidden signs.


[ENH] Parameter optimization and TS validation

idea
This is a superb library and now i am using it more and more for my work. I would like, however, to suggest to add some functionality about hyperparameter tuning. It is extremely important I think and would significantly boost the potentials of this library.
In my case, I am using Dynamic Factor Models extensively. One problem here is the optimal setting of the number of factors. This is also relevant for HMM models.
Second, is on clustering. Here there many parameters to tune and there is no obvious way how to tune each of them for each clustering algorithm.
A third suggestion in on model selection, especially with Time Series models like Dynamic Factor models. Here there are many different specifications (e.g. number of lags, modelling of the error term etc.) that one could use.
proposed solution
In the case of Dynamic Factor models one common practice is to use the process described here. See for example section: "Determining the number of factors and shocks to the factors"
On TS clustering enhancement, it could be good to have some standard approaches like elbow method to tune the models.
On the third suggestion, one suggestion is TS cross validation to determine the optimal model.

Hi @msh855, thanks for using aeon !
Concerning TS validation, has we interface easily with Scikit-learn, you can directly use their Time Series Split in your pipeline with aeon estimators.
For parameter optimization, we don't yet have a tool to optimize the parameters of our estimators. I would advise you to look at tools such as Optuna for this purpose for now.
For model selection, you can take inspiration from the forecasting benchmarking and adapt it to your use cases with the validation scheme you want (I think it uses resamples as the classification benchmark does).

thanks very much for the suggestions @msh855. For clustering, we can show how to use the elbow method Im sure, we can improve the notebooks maybe @chrisholder. You should also be able to use the scikit learn parameter tuning/model selection tools e.g https://scikit-learn.org/stable/modules/grid_search.html
I dont know about dynamic factor models, can go take a look, thanks.


update change_log

/check-enforcer override

https://github.com/Azure/azure-sdk-for-python/issues/23480


Send the right log config to each client based on their schema version

Fixes https://github.com/zwave-js/zwave-js-server/issues/335 which includes the background behind this fix

Looks good!


Regression for the tracking on old and new networks

Run regression for the tracking to check all events from the https://github.com/gnosis/safe/wiki/Tracking on mainnet and new L2 networks
check integration with Google analytics

done by Franco after L2 networks were added


Add support for subtask in create Jira issue modal

Summary

Add support Subtask issue type is not supported while creating an issue from Create Jira Issue Modal

Steps to reproduce:

Install your Jira instance
Connect your Jira account
Run /jira issue create <Issue Name>

For further information, refer to this conversation https://github.com/mattermost/mattermost-plugin-jira/issues/993
You might need to remove the below lines as well:
https://github.com/mattermost/mattermost-plugin-jira/blob/126ad10ae9935b2fb49f115c59f1b92013444ea2/server/issue.go#L538-L540

is this dropped? can't we add "sub-task" type (Task-User Story) for the notification in Mattermost?


Cast error when sending traces through data prepper.

Describe the bug
I've got the OpenTelemetry collector sending traces to the data prepper.
I'm receiving service map data, but due to the following error the trace data isn't making it's way to my elasticsearch server,
java.lang.ClassCastException: class io.opentelemetry.proto.collector.trace.v1.ExportTraceServiceRequest cannot be cast to class java.lang.String (io.opentelemetry.proto.collector.trace.v1.ExportTraceServiceRequest is in unnamed module of loader 'app'; java.lang.String is in module java.base of loader 'bootstrap')
	com.amazon.dataprepper.plugins.prepper.StringPrepper.execute(StringPrepper.java:39) ~[data-prepper.jar:0.8.0-beta]
	com.amazon.dataprepper.pipeline.ProcessWorker.run(ProcessWorker.java:57) [data-prepper.jar:0.8.0-beta]
	java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
	java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
	at java.lang.Thread.run(Thread.java:832) [?:?]

To Reproduce
Steps to reproduce the behavior:
- Configure pipeline as follows:   OpenTelemetry Dotnet SDK -> OpenTelemetry-collector-contrib -> ALB load balancer -> Data Prepper -> AWS Elasticsearch service
- Produce traces
- View error
Expected behavior
I'm expecting that the traces will be exported to the Elasticsearch server and no errors will be in the data prepper logs .
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OpenTelemetry SDK:
Version: v1.0.1
Platform: dotnet
OpenTelemetry Dotnet SDK
Elasticsearch server:
Hosted in AWS Elasticsearch service
Version: R20210201-P2
OpenTelemetry Collector:
opentelemetry-collector-contrib
Version: 0.22.0
running within Docker on ECS
Data Prepper:
Version: 0.8.0-beta
running within Docker on ECS Fargate
Additional context
Add any other context about the problem here.

Thanks @jamiegs for the bug report. From the stacktrace it looks like an OTelTraceSource is sending data to a StringPrepper. If so then there's a runtime mismatch of source-output and prepper-input.

OTelTraceSource: outputs records containing ExportTraceServiceRequest objects
StringPrepper: expects records containing String objects

To fix the immediate issue, you'd just need to remove the StringPrepper from the pipelines yaml file. Check out trace_setup.md for a sample yaml file configured specifically for the trace analytics usecase. Since you're using Amazon Elasticsearch Service, just replace the 2 ES sink blocks with something like:
  sink:
    - elasticsearch:
        hosts: [ "https://your-domain.us-east-1.es.amazonaws.com" ]
        aws_sigv4: true
        aws_region: "us-east-1"
        trace_analytics_raw: true

and
  sink:
    - elasticsearch:
        hosts: [ "https://your-domain.us-east-1.es.amazonaws.com" ]
        aws_sigv4: true
        aws_region: "us-east-1"
        trace_analytics_service_map: true

For a mid-term fix, I'll create an issue to update the documentation regarding inputs and outputs (I can see it could definitely be improved). And for the long-term, it'd be nice if DP could parse the config file on startup and detect if there are any config issues like these.
Let me know if you're still running into issues even after updating the pipelines yaml.

@wrijeff thanks for the help. Here's my pipeline config.. the elastic search section is pretty close to what you've suggested. I'm using basic auth, but I'll change it to use the AWS IAM authentication.

Could it be the 'string_converter' that's causing the problem?
Taking a look at the trace_setup.md, my pipelines.yaml is quite different. I used the second pipelines.yaml listed on this page https://opendistro.github.io/for-elasticsearch-docs/docs/trace/data-prepper/

Ah! Thanks for the documentation link. Yeah that string_converter definitely shouldn't be there - I'll open a PR to get that removed. 😅
Try removing it from your existing pipelines yaml - it should fix the ClassCastException from above.

I removed the string_converter and now I'm getting traces..   It's fixed! So thanks for the help!
Now I need to figure out why the services list (the list above the service map) isn't working.  the service map is working fine though.


Add phly/keep-a-changelog dev dependency

Pull Request Test Coverage Report for Build 583864274

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

Totals

Change from base Build 564255081:
0.0%

Covered Lines:
24

Relevant Lines:
25

💛  - Coveralls


no hash in poetry.lock?

This may be a poetry issue, but I can only reproduce it with the boto3-stubs package.
When you poetry lock a project with boto3-stubs, the lock file has empty boto3-stubs and botocore-stubs entries that don't have a hash. It also creates several mypy-boto3-* references which do have hashes, usually. But some, like mypy-boto3-sqs, still don't have a hash.
The problem is that when exporting the lock file through poetry export, the lone boto3-stubs remains without hashes, and this causes pip install to fail. Pip doesn't allow mixing hash- and nohash- packages by design.
The workaround is to add --without-hashes when doing the poetry export, but then it kinda defeats the purpose of lock files.
pyproject.toml
[tool.poetry]
name = "bonsoir"
version = "0.1.0"
description = "..."
authors = ["..."]

[tool.poetry.dependencies]
python = "^3.9.0"

boto3-stubs = { extras = ["dynamodb", "ec2", "sqs", "secretsmanager", "ssm", "sts"] }

[build-system]
requires = ["poetry_core>=1.0.0"]
build-backend = "poetry.core.masonry.api"

last part of poetry.lock
[metadata.files]
boto3-stubs = []
botocore-stubs = []
mypy-boto3-dynamodb = [
    {file = "mypy-boto3-dynamodb-1.24.12.tar.gz", hash = "sha256:4fc6f0f84988ae3d307a43ec31930483828b199f1179cb801238c16cd8be5901"},
    {file = "mypy_boto3_dynamodb-1.24.12-py3-none-any.whl", hash = "sha256:7ad9aa9c23a9f90d0aa0018df3a975e6c1da32f76c11aef60bf1a49cfca840cc"},
]
mypy-boto3-ec2 = [
    {file = "mypy-boto3-ec2-1.24.19.tar.gz", hash = "sha256:eb650a7dc99b8c3b31652168b6a7592f329f3082584801adf2e5797737a87a2c"},
    {file = "mypy_boto3_ec2-1.24.19-py3-none-any.whl", hash = "sha256:1f68ae953212b6db95c0b166f02daeb03140bd7445065b2243858561a8732637"},
]
mypy-boto3-secretsmanager = [
    {file = "mypy-boto3-secretsmanager-1.24.11.post3.tar.gz", hash = "sha256:f153b3f5ff2c65664a906fb2c97a6598a57da9f1da77679dbaf541051dcff36e"},
    {file = "mypy_boto3_secretsmanager-1.24.11.post3-py3-none-any.whl", hash = "sha256:d9655d568f7fd8fe05265613b85fba55ab6e4dcd078989af1ef9f0ffe4b45019"},
]
mypy-boto3-sqs = []

https://github.com/python-poetry/poetry/issues/5967
Turns out that it would be a bug at pypi 🤷🏻♂


Add some output processing after running the tests

Output will look like this when no failure occurred:
Test results:
Vim Test Log: 20190518 13:04:39
Skipped: 9 Tests
Executed: 1510 Tests
Skipped:
Test_normal30_changecase(): Turkish locale not available
Test_normal35_g_cmd4(): output of g< can't be tested currently
Test_normal47_autocmd(): not possible to test cursorhold autocmd while waiting for input in normal_cmd
Test_restricted_mzscheme(): MzScheme is not supported
Test_restricted_python3(): Python3 is not supported
Test_restricted_ruby(): Ruby is not supported
Test_restricted_tcl(): Tcl is not supported
Test_term_mouse_middle_click(): No working clipboard
Test_term_gettitle(): can't get/set title
ALL DONE
However when an error occurred, it will look like this:
Test results: 20190518 13:15:57
Skipped: 9 Tests
Executed: 1510 Tests
Skipped:
Test_normal30_changecase(): Turkish locale not available
Test_normal35_g_cmd4(): output of g< can't be tested currently
Test_normal47_autocmd(): not possible to test cursorhold autocmd while waiting for input in normal_cmd
Test_restricted_mzscheme(): MzScheme is not supported
Test_restricted_python3(): Python3 is not supported
Test_restricted_ruby(): Ruby is not supported
Test_restricted_tcl(): Tcl is not supported
Test_term_mouse_middle_click(): No working clipboard
Test_term_gettitle(): can't get/set title
Failures:
From test_alot.vim:
Found errors in Test_reltime():
Run 1:
function RunTheTest[40]..Test_reltime line 5: Expected True but got 0
Run 2:
function RunTheTest[40]..Test_reltime line 5: Expected True but got 0
Flaky test failed too often, giving up
TEST_FAILURE

I like the addition of a summary!  However, three things:
(1) I think it would be better to show "Executed: N tests" above "Skipped: M tests" instead of the other way around.
(2) When no tests fail, I think it'd be better to see:
Executed: 1510 tests
Skipped:  9 tests
Failed:   0 tests

and when some tests fail, to see:
Executed: 1510 tests
Skipped:  9 tests
Failed:   2 tests

(3) I think things are easier to read (especially in a terminal that's 25 lines high) if the aforementioned  block of three counts appears at the bottom, after the list of the specific skipped and failed tests.  That's because the typical situation will involve no failures but many skips.  When the user looks at the screen just above her prompt she quickly sees just this:
Test_restricted_ruby(): Ruby is not supported
Test_restricted_tcl(): Tcl is not supported
Test_term_mouse_middle_click(): No working clipboard
Test_term_gettitle(): can't get/set title

ALL DONE

And to be honest it isn't clear from this that the listed tests were in fact skipped rather than failed.  The descriptions after the colons kind of read like problems.  ("No working clipboard?  Oh no!")

I'll have a look at making the suggested changes. Seems reasonable to me. Note regarding 3) the output is a bit indented below the Skipped: line, so it should be clear, that this belongs to the Skipped section. I did however not change the Skipped message, so that's why it may sound like a problem.
One noteworthy change (not mentioned here, because I initially tried to get rid of the Makefile logic and did not think of tiny Vims), is that for tiny Vims, this output won't be shown, since it does not have the eval feature needed to postprocess the log.

Why use  %s/^Executed\s+\zs\d+\ze\s+tests/=Count(submatch(0),'executed')/egn
Instead of a for loop over all the lines?  Would be easier to read.
call extend(output, ["Executed: ". printf("%5d", g:executed). " Tests"])
Can omit the string concatenations:  printf("Executed: %5d Tests")

Why use %s/^Executed\s+\zs\d+\ze\s+tests/=Count(submatch(0),'executed')/egn
Instead of a for loop over all the lines? Would be easier to read.

It's faster and needs less code.

Can omit the string concatenations: printf("Executed: %5d Tests")

True. will update.


Fixing tests with respect to the new API version in our last changes.

Fixing tests.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Codecov Report

:exclamation: No coverage uploaded for pull request base (restapi_auto_resourcegraph/resource-manager@eee54e7). Click here to learn what that means.
The diff coverage is 69.44%.

@@                              Coverage Diff                               @@
##             restapi_auto_resourcegraph/resource-manager    #4702   +/-   ##
==============================================================================
  Coverage                                               ?    49.5%
==============================================================================
  Files                                                  ?     6329
  Lines                                                  ?   177168
  Branches                                               ?        0
==============================================================================
  Hits                                                   ?    87706
  Misses                                                 ?    89462
  Partials                                               ?        0

Impacted Files
Coverage Δ

azure-batch/azure/batch/models/_models_py3.py
65.62% <ø> (ø)

.../azure/batch/models/_batch_service_client_enums.py
100% <100%> (ø)

azure-batch/azure/batch/models/_paged_models.py
100% <100%> (ø)

azure-batch/azure/batch/models/__init__.py
55.79% <55.82%> (ø)

azure-batch/azure/batch/custom/patch.py
85.98% <58.82%> (ø)

azure-batch/azure/batch/batch_service_client.py
95.55% <83.33%> (ø)

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 eee54e7...64e1e52. Read the comment docs.

The PR got doomed, I cherry picked the commit


Allow addition of entries with not yet collected x,y positions

Currently, the first data addition will set the row/column (or x,y) positions that are allowed for data collection. This can lead to unexpected behavior when adding new data ...

Done. Now supports different join_type options.


[CH] Memory is not released during spilling in aggregation

Backend
CH (ClickHouse)
Bug description
[Expected behavior] and [actual behavior].
2024-10-30 15:36:59.600 <Debug> AggregateDataBlockConverter: Convert bucket 54 into one block, rows: 6105, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1248702, time: 2
2024-10-30 15:36:59.603 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 604.94 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.611 <Debug> AggregateDataBlockConverter: Convert bucket 55 into one block, rows: 6213, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1242489, time: 2
2024-10-30 15:36:59.614 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.643 <Debug> AggregateDataBlockConverter: Convert bucket 56 into one block, rows: 6263, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1236226, time: 3
2024-10-30 15:36:59.646 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 606.31 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.655 <Debug> AggregateDataBlockConverter: Convert bucket 57 into one block, rows: 6096, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1230130, time: 3
2024-10-30 15:36:59.657 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.693 <Debug> AggregateDataBlockConverter: Convert bucket 58 into one block, rows: 6350, cols: 15, bytes:1.18 MiB, total bucket: 256, total rows: 1223780, time: 3
2024-10-30 15:36:59.695 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 607.06 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.705 <Debug> AggregateDataBlockConverter: Convert bucket 59 into one block, rows: 6244, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1217536, time: 3
2024-10-30 15:36:59.707 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.742 <Debug> AggregateDataBlockConverter: Convert bucket 60 into one block, rows: 6226, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1211310, time: 3
2024-10-30 15:36:59.745 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 606.00 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.753 <Debug> AggregateDataBlockConverter: Convert bucket 61 into one block, rows: 6295, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1205015, time: 3
2024-10-30 15:36:59.755 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.788 <Debug> AggregateDataBlockConverter: Convert bucket 62 into one block, rows: 6110, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1198905, time: 2
2024-10-30 15:36:59.790 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 605.00 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.798 <Debug> AggregateDataBlockConverter: Convert bucket 63 into one block, rows: 6213, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1192692, time: 2
2024-10-30 15:36:59.800 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.835 <Debug> AggregateDataBlockConverter: Convert bucket 64 into one block, rows: 6234, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1186458, time: 3
2024-10-30 15:36:59.837 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 606.06 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.846 <Debug> AggregateDataBlockConverter: Convert bucket 65 into one block, rows: 6172, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1180286, time: 3
2024-10-30 15:36:59.849 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.882 <Debug> AggregateDataBlockConverter: Convert bucket 66 into one block, rows: 6332, cols: 15, bytes:1.18 MiB, total bucket: 256, total rows: 1173954, time: 3
2024-10-30 15:36:59.884 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 606.91 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.893 <Debug> AggregateDataBlockConverter: Convert bucket 67 into one block, rows: 6169, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1167785, time: 3
2024-10-30 15:36:59.896 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.931 <Debug> AggregateDataBlockConverter: Convert bucket 68 into one block, rows: 6173, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1161612, time: 3
2024-10-30 15:36:59.934 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 605.53 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.943 <Debug> AggregateDataBlockConverter: Convert bucket 69 into one block, rows: 6197, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1155415, time: 3
2024-10-30 15:36:59.946 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.981 <Debug> AggregateDataBlockConverter: Convert bucket 70 into one block, rows: 6223, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1149192, time: 3
2024-10-30 15:36:59.983 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 605.97 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:36:59.992 <Debug> AggregateDataBlockConverter: Convert bucket 71 into one block, rows: 6203, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1142989, time: 3
2024-10-30 15:36:59.994 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:37:00.021 <Debug> AggregateDataBlockConverter: Convert bucket 72 into one block, rows: 6047, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1136942, time: 2
2024-10-30 15:37:00.023 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 604.44 KiB, max limit: 1.00 MiB, current memory usage: 1.27 GiB
2024-10-30 15:37:00.032 <Debug> AggregateDataBlockConverter: Convert bucket 73 into one block, rows: 6184, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1130758, time: 3
2024-10-30 15:37:00.034 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.40 GiB
2024-10-30 15:37:00.067 <Debug> AggregateDataBlockConverter: Convert bucket 74 into one block, rows: 6285, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1124473, time: 3
2024-10-30 15:37:00.070 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 606.50 KiB, max limit: 1.00 MiB, current memory usage: 1.40 GiB
2024-10-30 15:37:00.079 <Debug> AggregateDataBlockConverter: Convert bucket 75 into one block, rows: 6134, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1118339, time: 3
2024-10-30 15:37:00.081 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.40 GiB
2024-10-30 15:37:00.113 <Debug> AggregateDataBlockConverter: Convert bucket 76 into one block, rows: 6317, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1112022, time: 3
2024-10-30 15:37:00.115 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 606.78 KiB, max limit: 1.00 MiB, current memory usage: 1.40 GiB
2024-10-30 15:37:00.125 <Debug> AggregateDataBlockConverter: Convert bucket 77 into one block, rows: 6174, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1105848, time: 3
2024-10-30 15:37:00.127 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.40 GiB
2024-10-30 15:37:00.159 <Debug> AggregateDataBlockConverter: Convert bucket 78 into one block, rows: 6210, cols: 15, bytes:1.17 MiB, total bucket: 256, total rows: 1099638, time: 3
2024-10-30 15:37:00.162 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 605.84 KiB, max limit: 1.00 MiB, current memory usage: 1.40 GiB
2024-10-30 15:37:00.171 <Debug> AggregateDataBlockConverter: Convert bucket 79 into one block, rows: 6338, cols: 15, bytes:1.18 MiB, total bucket: 256, total rows: 1093300, time: 3
2024-10-30 15:37:00.173 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 1.18 MiB, max limit: 1.00 MiB, current memory usage: 1.40 GiB
2024-10-30 15:37:00.206 <Debug> AggregateDataBlockConverter: Convert bucket 80 into one block, rows: 6377, cols: 15, bytes:1.18 MiB, total bucket: 256, total rows: 1086923, time: 3
2024-10-30 15:37:00.208 <Debug> GraceMergingAggregatedTransform: flush pending bytes. pending_bytes: 607.28 KiB, max limit: 1.00 MiB, current memory usage: 1.40 GiB
2024-10-30 15:37:00.217 <Debug> AggregateDataBlockConverter: Convert bucket 81 into one block, rows: 6393, cols: 15, bytes:1.18 MiB, total bucket: 256, total rows: 1080530, time: 3

Spark version
None
Spark configurations
No response
System information
No response
Relevant logs
No response

The aggregate data is allocated from arena pool. Before the whole AggregatedDataVariants is destoried, the memory cannot be released


Viz: image tile pyramid builder and viewer

Use some Python package, such as zoomify or deepzoom and have seadragon or such for viewing in JS-land.
Colab allows a HTTP server, so

write pyramid files to FS,
set up HTTP server with pyramid files
JS (seadragon or such) pulls down tiles as needed

See also #58

https://scikit-image.org/docs/dev/auto_examples/transform/plot_pyramid.html

https://leafletjs.com/examples/zoom-levels/

Vizic Astronomy and Jupyter 2017

Geologist

GeoPySpark


Update msal-react ssoSilent example

Fix example to show useMsalAuthentication returns an object instead of an array, using the InteractionType enum, and how to display the logged in user.

Coverage increased (+15.7%) to 97.619% when pulling 0d436750674e6e79ce30e9d45471f0ea05035b7c on react-ssosilent-example into 7252087b80db84ffafe1cf76d48dd767277a2ae5 on dev.


Add nogutter prop to Row

Last one :)

Oh damn, I didn't push the version bump apparently... can you cut 3.0.6?

Sure!

Thanks! Types are now working great.


add generic volume handling

Appears that append-volumes assumes 9p today.  Volumes is a method for passing a generic device into the container.  ie: docker run -v /dev/vfio/17:/dev/vfio/17.
It doesn't appear to be generic today:
https://github.com/containers/virtcontainers/blob/e01ebd015f77b3e822b597088e6efc102a7e6d9a/qemu.go#L177

Yes you're right, it is not generic as it is tied to 9pfs.

example of how it should work:  $ sudo docker run --runtime=runc -v /dev/vfio/17:/dev/example -it alpine sh
/ # ls /dev/example
/dev/example
And, in the config.json, this is described as:
root@sriov-2:/home/sriov/go/src/github.com/01org/cc-oci-runtime# cat /var/run/docker/libcontainerd/7b94fe6ccdf5304b4cf74c18ebed880cfe580d421820c54b140d251a60a08a09/config.json | python -mjson.tool | grep -b10 -a10 vfio
50490-                "nodev"
50514-            ],
50529-            "source": "mqueue",
50561-            "type": "mqueue"
50590-        },
50601-        {
50611-            "destination": "/dev/example",
50654-            "options": [
50679-                "rbind"
50703-            ],
50718:            "source": "/dev/vfio/17",
50756-            "type": "bind"
50783-        },
50794-        {
50804-            "destination": "/etc/resolv.conf",
50851-            "options": [
50876-                "rbind",
50901-                "rprivate"
50928-            ],
50943-            "source": "/var/lib/docker/containers/7b94fe6ccdf5304b4cf74c18ebed880cfe580d421820c54b140d251a60a08a09/resolv.conf",
51072-            "type": "bind"

@sboeuf - can you comment on the relevance of this issue, given all the changes that are being introduced currently for Kata?

Wondering if this is relevant since the --device is handled but not through this way. I think we should not think at volumes the same way docker does. What I mean is that this method appendVolume() is the 9pfs method for qemu, which is fine since we use hotplugDevice() if we have a volume presented as a device.

@sboeuf I think it is worth handling this for volumes as well. If the volume directory is mounted ar a location that is backed by a block device, it would make sense to pass the block device and mount it to the desired location within the container.

@amshinde yes this makes sense.

After discussion with @amshinde on this issue, I think we should honor --volume option by following those steps:

Detect if the volume passed (translated as a Mount inside virtcontainers) is a simple directory, or a device.
According to the device type (we handle only BlockDevice now), we would hotplug it through the VM.
We would need to modify the Mount entry for both the Type and the Destination. The Type being used as the flag to let the agent implementation what to do with it, that is adding a new Storage in case of Kata. And the Destination being used as the mount point inside the VM.

This way, the volume would be hotplugged as a block device, then found by the block device storage handler inside the agent, and bind mounted by libcontainer into the container.
This would allow for a slightly different result than using --device for the same block device because this device would be bind mounted inside the container instead of being recreated using mknod relying on major/minor numbers.


Apostrophe Custom-Widgets is not working.

I'm using apostraphecms version 3.
I followed these steps to create a custom widget - https://v3.docs.apostrophecms.org/guide/custom-widgets.html#creating-a-widget-type
Once the configuration is done I restarted the application and checked in UI, the custom widget is not showing.
My widget folder structure is my-project/modules/two-column-widget.
index.js
//my-project/modules/two-column-widget/index.js
module.exports = {
  extend: '@apostrophecms/widget-type',
  options: {
    label: 'Two Column Widget',
  },
  fields: {
    add: {
      columnOne:{
        type: 'area',
        label: 'Column One',
        options:{
          widgets:{
            '@apostrophecms/rich-text':{}
          }
        }
      },
      columnTwo:{
        type: 'area',
        label: 'Column Two',
        options:{
          widgets:{
            '@apostrophecms/rich-text':{}
          }
        }
      }
    }
  }
};

widget.html
//my-project/modules/two-column-widget/views/widget.html

    {% area data.widget, 'columnOne' %}

    {% area data.widget, 'columnTwo' %}

app.js
require('apostrophe')({
  shortName: 'apos-app',
  modules: {
    '@apostrophecms/rich-text-widget': {
      options: {
        className: 'bp-rich-text'
      }
    },
    '@apostrophecms/image-widget': {
      options: {
        className: 'bp-image-widget'
      }
    },
    '@apostrophecms/video-widget': {
      options: {
        className: 'bp-video-widget'
      }
    },
    'two-column-widget':{},
    'product':{},
    asset: {},
    'default-page': {}
  }
});

These are the codes I have configured for custom widgets. While I run the project I don't have any errors though.
console:
apos-app % npm run dev
><EMAIL_ADDRESS>dev /Projects/apos-app
> nodemon

[nodemon] 2.0.15
[nodemon] reading config ./package.json
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 56075 to restart
[nodemon] ignoring: ./.git/**/* locales/*.json ./public/uploads/**/* public/apos-frontend/*.js ./data/**/*
[nodemon] watching path(s): app.js modules/**/* lib/**/*.js views/**/*.html
[nodemon] watching extensions: json,js,html,scss,vue
[nodemon] starting `node app.js`
[nodemon] forking
[nodemon] child pid: 56077
[nodemon] watching 28 files
(node:56077) DeprecationWarning: isConnected is deprecated and will be removed in the next major version
(Use `node --trace-deprecation ...` to show where the warning was created)
🧑💻 Building the Public-facing modern JavaScript and Sass...
👍 Public-facing modern JavaScript and Sass is complete!
🧑💻 Building the Raw CSS and JS...
👍 Raw CSS and JS is complete!
Listening at http://localhost:3000

Can anyone please help me to resolve the issue?

Thank you for the response.
Apologize once I posted the issue I noticed the section where I have put the question.
I have linked this issue under a3-boilerplate - https://github.com/apostrophecms/a3-boilerplate/issues/31
Yes, I have mentioned the new widgets in the area.
FYI
home-page/index.js
<EMAIL_ADDRESS>module.exports = {
  options: {
    label: 'Home Page'
  },
  fields: {
    add: {
      main: {
        type: 'area',
        options: {
          widgets: {
            '@apostrophecms/rich-text': {
              toolbar: [
                'styles',
                '|',
                'bold',
                'italic',
                'strike',
                'link',
                '|',
                'bulletList',
                'orderedList'
              ],
              styles: [
                {
                  tag: 'p',
                  label: 'Paragraph (P)'
                },
                {
                  tag: 'h3',
                  label: 'Heading 3 (H3)'
                },
                {
                  tag: 'h4',
                  label: 'Heading 4 (H4)'
                }
              ]
            },
            '@apostrophecms/image': {},
            '@apostrophecms/video': {},
            'two-column-widget':{},
            'columns-widget':{}
          }
        }
      }
    },
    group: {
      basics: {
        label: 'Basics',
        fields: [
          'title',
          'main'
        ]
      }
    }
  }
};

modules/default-page/index.js
//my-project/modules/default-page/index.js
module.exports = {
  extend: '@apostrophecms/page-type',
  options: {
    label: 'Default Page'
  },
  fields: {
    add: {
      main: {
        type: 'area',
        options: {
          widgets: {
            '@apostrophecms/rich-text': {
              toolbar: [
                'styles',
                '|',
                'bold',
                'italic',
                'strike',
                'link',
                '|',
                'bulletList',
                'orderedList'
              ],
              styles: [
                {
                  tag: 'p',
                  label: 'Paragraph (P)'
                },
                {
                  tag: 'h3',
                  label: 'Heading 3 (H3)'
                },
                {
                  tag: 'h4',
                  label: 'Heading 4 (H4)'
                }
              ]
            },
            '@apostrophecms/image': {},
            '@apostrophecms/video': {},
            'two-column-widget':{},
            'columns-widget':{}
          }
        }
      }
    },
    group: {
      basics: {
        label: 'Basics',
        fields: [
          'title',
          'main'
        ]
      }
    }
  }
};

Let me know If I have to provide any codes for your reference.

Try this but leave -widget off in the area configuration. So the final two lines of the widget configuration should be:
            'two-column':{},
            'columns':{}

See this section: https://v3.docs.apostrophecms.org/guide/areas-and-widgets.html#leave-widget-out-of-area-configuration

Okay, I have also tried like that. But No Response.

okay sure.

I've pushed up a pull request to implement a warning at startup if any
widget type names specified for an area field end in -widget or just plain
don't exist.
On Wed, Jan 5, 2022 at 11:39 AM Abinaya @.***> wrote:

okay sure.
—
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/apostrophe-boilerplate/issues/27#issuecomment-1005886546,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27IPI4375MCVIJNMY7TUURX3FANCNFSM5LJIHPFQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

Hey Alex, Thanks for your help. I cross-checked once I changed the widget on one page and not on another page. I just changed that. Now it's working.
Thank you so much for your time.


feat: impl complete kclvm cli

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

feat: impl complete kclvm cli

2. What is the scope of this PR (e.g. component or file name):

kclvm_cmd crate
kclvm_driver crate
kclvm_config crate

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

kclvm/cmd/src/tests.rs
kclvm/driver/src/tests.rs
kclvm/runtime/src/value/val_plan.rs

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2300

Relevant Lines:
2614

💛  - Coveralls


feat(builtin): add StringBuilder::is_empty()

Mirrored from the corresponding @buffer.T API, as required by https://github.com/moonbit-community/cmark.

Pull Request Test Coverage Report for Build 4139
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 80.838%

Totals

Change from base Build 4132:
0.003%

Covered Lines:
4493

Relevant Lines:
5558

💛  - Coveralls


Combine don't let the perfect defeat the good + learn constantly by embracing failure

These two seem pretty similar to me, particularly the "Focus on creating a workable solution that can be tested and improved" and "Making small, iterative changes allows us to test the outcomes of those changes, and then revise our approach accordingly" parts.

:+1: from me for giving this a shot.

I agree. Personally, I think the first sentence could go. Focus on creating a a workable solution seems obvious.

@bonniegee want to give this a shot and create a pull request?


Make Exposed _log Method Public?

Would you consider explicitly exposing _log?
I am using gulp-debug to inspect a vinyl-fs pipeline in a server. In this case I would rather the output be printed by debug instead of fancy-log.
Here is what I am currently doing.
var debug = require('debug')('ciq-license-server:pipeline');
var gulpDebug = require('gulp-debug');
var stream = require('stream');

if (gulpDebug._log) {
	gulpDebug._log = function() {
		debug(...arguments);
	};
} else {
	throw new Error('gulp-debug is not exposing "_log" function');
}

module.exports = function(options) {
	return debug.enabled ? gulpDebug(options) : new stream.PassThrough({objectMode: true});
};

Yeah, sure. PR welcome for a logger option. Should come with docs and a test. :)

Fixed by #43


Beta 12 - Ion Content Overflow. Content is not rendering.

Bug Report
Ionic Info
Ionic:

   ionic (Ionic CLI)          : 4.2.0 (C:\**\**\**\**\npm\node_modules\ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.12
   @angular-devkit/core       : 0.8.3
   @angular-devkit/schematics : 0.8.3
   @angular/cli               : 6.1.5
   @ionic/ng-toolkit          : 1.0.8
   @ionic/schematics-angular  : 1.0.6

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : android 7.0.0
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.1.4, (and 5 other plugins)

System:

   Android SDK Tools : 26.1.1 (C:\Android\android-sdk)
   NodeJS            : v8.11.3 (C:\Program Files\nodejs\node.exe)
   npm               : 5.6.0
   OS                : Windows 10

Describe the Bug
Content beyond viewport is not rendering inside ion-content tag.
Steps to Reproduce
Steps to reproduce the behavior:

Add *ngFor to an ion-card element inside an ion-content tag. Add a 20-25 elements in the array variable. And ionic serve .

I have my content routed to another component using:
<ion-content [forceOverscroll]="'true'" [scrollY]="true">
    <div class="ion-page">
        <ion-router-outlet></ion-router-outlet>
    </div>
</ion-content>

I have tried combinations of options and properties using the docs. But overflow content does not render.
Expected Behavior
It should render beyond the viewport and should allow scrolling along y-axis.

Thanks for your issue! Unfortunatly I don't understand what the problem is. Could you please add a repo to reproduce thie issue and add screenshots?


Add support for with option to create (saving relations)

Is support for deep saving relations currently added in v3? If not, how would you suggest we handle this?

It is available: http://www.js-data.io/v3.0/docs/relations#section-deep-creating-relations


npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
OS: Windows 10.
Installed dependence "swiper": "^6.5.0"

$ npm i is not working for me aswell.
What is this error and how can this be solved?

I worked around this by using the legacy flag...
$ npm i --legacy-peer-deps

But this is obviously not a long-term solution.

same issue. Any updates?


release-1.21: use ExtractObject to avoid panic (#51580)

Please provide a description of this PR:
Manual cherry-pick of https://github.com/istio/istio/pull/51580, fixes https://github.com/istio/istio/issues/52341

Hi @dwj300. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/ok-to-test