Build errors on changing nthreads to a specific number in dot.c

Hi,
I have enabled SMP(multithreading) in dot.c code and trying to change nthreads to a specific number(2 in the below case). Build is failing with accuracy errors for many BLAS functions(error screenshot attached below). Kindly advise:
Code - dot.c
#if defined(SMP)
nthreads= 2;
// if (inc_x == 0 || inc_y == 0 || n <= 10000)
// 	nthreads = 1;
// else
// 	nthreads = num_cpu_avail(1);
if (nthreads == 1) {
dot = dot_compute(n, x, inc_x, y, inc_y);
} else {
int mode, i;
char result[MAX_CPU_NUMBER * sizeof(double) * 2];
RETURN_TYPE *ptr;
Error:
DTRSV  PASSED THE TESTS OF ERROR-EXITS
******* FATAL ERROR - COMPUTED RESULT IS LESS THAN HALF ACCURATE *******
EXPECTED RESULT   COMPUTED RESULT
1       0.00000           0.00000
2      0.117383          0.135833
******* DTRSV  FAILED ON CALL NUMBER:
62: DTRSV ('U','T','N',  2, A,  3, X, 1)                     .
DTBSV  PASSED THE TESTS OF ERROR-EXITS
******* FATAL ERROR - COMPUTED RESULT IS LESS THAN HALF ACCURATE *******
EXPECTED RESULT   COMPUTED RESULT
1       0.00000           0.00000
2      0.916583          0.659984
******* DTBSV  FAILED ON CALL NUMBER:
254: DTBSV ('U','T','N',  2,  1, A,  3, X, 1)
Build command used: make BUFFERSIZE=20 DYNAMIC_ARCH=1 USE_OPENMP=1 NUM_THREADS=80 TARGET=NEOVERSEV1 INTERFACE64=1

Are you sure that dot.c is the only file you changed in the branch you are working with ? (git status and git diff should tell)

Yes, sharing the output of both the commands:
git status
On branch develop
Your branch is up to date with 'origin/develop'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified:   kernel/arm64/dot.c
no changes added to commit (use "git add" and/or "git commit -a")
$ git diff
diff --git a/kernel/arm64/dot.c b/kernel/arm64/dot.c
index 4607ebc59..9068f80d8 100644
--- a/kernel/arm64/dot.c
+++ b/kernel/arm64/dot.c
@@ -38,6 +38,7 @@ USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#endif
#endif
#endif
+#define SMP 1
#ifdef USE_SVE
#include "dot_kernel_sve.c"
@@ -85,10 +86,11 @@ RETURN_TYPE CNAME(BLASLONG n, FLOAT *x, BLASLONG inc_x, FLOAT *y, BLASLONG inc_y
RETURN_TYPE dot = 0.0;
#if defined(SMP)

  if (inc_x == 0 || inc_y == 0 || n <= 10000)

          nthreads = 1;

  else

          nthreads = num_cpu_avail(1);

  nthreads = 2;

  // if (inc_x == 0 || inc_y == 0 || n <= 10000)

  //      nthreads = 1;

  // else

  //      nthreads = num_cpu_avail(1);

  if (nthreads == 1) {
          dot = dot_compute(n, x, inc_x, y, inc_y);

Hmm, I don't have time to look now, but can you try leaving the "use nthreads=1 for incx=0 or incy=0" intact ?

I tried with the below code, build works this time but I also wanted to experiment for different values of nthreads when n <=10000.
#if defined(SMP)
if (inc_x == 0 || inc_y == 0 || n <= 10000)
nthreads = 1;
else
nthreads = 4;
Also if I try to change the condition from n <= 10000 to n <= 1, build is again stuck.

nust move that n<10000 part to new if() It is 2 conditionals merged together.

Hi @martin-frbg , Sorry for reverting back late.  moving n<10000 part to new if()  didn't help, gives the same initial accuracy errors:
#if defined(SMP)
if (inc_x == 0 || inc_y == 0)
nthreads = 1;
else if ( n <= 10000)
{
nthreads = 6;
}
else
nthreads = 6;

Also when nthreads>1, I see almost all the cores used. Is there a way to verify that only nthreads are being used.

OpenBLAS does not control more threads than nthreads computed for particular call.
You got your clarification on how to not break algorithm modifying threading threshold.
If you want to calibrate threading threshold you can use benchmarks included, and set the config overrides in Makefile.rule then try to point to good direction, like doubling/halving that 10k, then measure speeds at least 10x back/forth from that break point.
If you want to tune for your hardware you need to describe your hardware and at least show some benchmark results that seem illogical/ are worse than arm hpc blas/blis/atlas etc.
Neither of 2 is to do with initial correction.

Thank you @brada4. Can you please elaborate on which config to override in Makefile? So, currently I am using the benchmark to check the performance of dot with different number of threads.  I am modifying the kernel/arm64/dot.c code only to change the nthreads value I want to experiment with.  I am unable to change the 10k condition as I get test case failures on accuracy issues.

Build command used: make BUFFERSIZE=20 DYNAMIC_ARCH=1 USE_OPENMP=1 NUM_THREADS=80 TARGET=NEOVERSEV1 INTERFACE64=1

Just add make variables in separate lines by end of file.

Strange issue - apart from the obvious corner cases like n<=1 I would not expect hangs or  serious accuracy issues from multithreading "too early". Does the problem go away when you do not override the default BUFFERSIZE ? And are you actually running the code on Neoverse V1 or something else ?


Make debugs logs suck less.

closes #10245
ping @crosbymichael

there are also a line in archive/archive.go where the byte gets put in the logs like:
"[tar autodetect] n: [31 139 8 0 0 9 110 136 0 255] <--- idk who this is helping
but I know that is @unclejack's territory so I didn't touch it :)

@dmcgowan @jlhawn how do you guys feel about is not logging this json string

"[tar autodetect] n: [31 139 8 0 0 9 110 136 0 255] is definitely not helping me.
LGTM

@vieux I figured you could read bytes :smile:

LGTM

@jfrazelle @vieux Thanks, I'll take care of that now.


Why Connection closed 1006

Can you try running it locally?
I'm going to improve the error messages on the hosted version but right now, there's minimal logging on the hosted version. Or you can buy an access code. That will work.

i run it from github project and run backend on 7001 and frontend on 5173 port .. and still same proplem with run on docker or the main website ...

i have subscription and 5 dollars credit free not usage yet

Some times it takes a few minutes for the credits to update but I assume it's been a while.
Can you share backend logs when you run it locally?

that's logs in console log in chrome and terminal in vscode

As you can see on the last line, your api key doesn't have access to vision. I'm not sure but I would double check all the steps outlined here: https://github.com/abi/screenshot-to-code/blob/main/Troubleshooting.md

I also have the same problem.

connection closed 1000
the code is not completed

Can yall please share you backend and front end logs from your terminal? That will help me debug the issue.

Feel free to re-open if there are still issues. We have improved the error messages quite a bit so it should tell you what the issue is with your API key


Change filled star to black

Changed CSS colour to black #000

Can one of the admins verify this patch?

ok to test


[SPARK-31357][SQL][WIP] Catalog API for view metadata

What changes were proposed in this pull request?

View catalog interface
View resolution rules
View SQL DDL implementations

In this PR, "view" stands for persisted view by default.
These view SQL DDLs will be done in follow-up PRs:

SHOW TBLPROPERTIES
SHOW VIEWS

Why are the changes needed?
Support view catalog in DataSourceV2. Details in SPIP.
Does this PR introduce any user-facing change?

View SQL DDLs
DataFrame.table("catalog.db.view")

How was this patch tested?
TODO: new unit tests
Regression

DDLParserSuite
PlanResolutionSuite
DataSourceV2SQLSuite

Test build #120941 has started for PR 28147 at commit b253954.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25633/
Test PASSed.

Test build #120941 has finished for PR 28147 at commit b253954.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public final class ViewReservedProperties
 public static class Updater
 case class ViewSubstitution(sqlParser: ParserInterface) extends Rule[LogicalPlan]
trait ViewDescription
case class CatalogViewDescription(metadata: CatalogTable) extends ViewDescription
case class V2ViewDescription(
case class CreateView(
case class DropView(
case class AlterView(
case class RenameView(
case class DescribeView(desc: V2ViewDescription, isExtended: Boolean) extends Command
case class ShowCreateView(desc: V2ViewDescription) extends Command
case class ShowViewProperties(
case class CreateViewAnalysis(
case class AlterViewExec(
trait CatalystRowHelper
case class CreateViewExec(
case class DescribeViewExec(
case class DropViewExec(
case class RenameViewExec(
case class ShowCreateViewExec(output: Seq[Attribute], desc: V2ViewDescription)
case class ShowViewPropertiesExec(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120941/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25645/
Test PASSed.

Test build #120954 has started for PR 28147 at commit cd00319.

Test build #120954 has finished for PR 28147 at commit cd00319.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ShowTablePropertiesStatement(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120954/
Test FAILed.

Test build #120987 has started for PR 28147 at commit 32ec893.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25678/
Test PASSed.

Test build #120987 has finished for PR 28147 at commit 32ec893.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120987/
Test PASSed.

Test build #120997 has started for PR 28147 at commit 3435379.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25688/
Test PASSed.

Test build #120997 has finished for PR 28147 at commit 3435379.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120997/
Test FAILed.

Test build #121096 has started for PR 28147 at commit 44678b1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25786/
Test PASSed.

Test build #121096 has finished for PR 28147 at commit 44678b1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121096/
Test PASSed.

@cloud-fan @dongjoon-hyun @brkyvz Could you comment on this WIP PR? Go or no-go? Need more clarifications? Even though it is labeled as WIP, the code is pretty stable and in production for over 6 months.


Bump Pydantic

To Be Supported:

Pydantic V1

Pydantic V2

Python 3.7 - 3.11

Beanie and Bunnet

Funding

You can sponsor this specific effort via a Polar.sh pledge below
We receive the pledge once the issue is completed & verified

You can pledge behind and help support this effort using Polar.sh


quick way to get first column to be sticky?

Wondering if currently there is a way to get the first column ( y-axis if you're doing 2 dimensional data) to be a sticky column so that if you have a large table with scroll you can see the categories?
I'm doing a time series as column headers and sometimes the table has a hundred columns so when the user scrolls they wouldn't see the first column that holds the list of metrics - forcing them to keep scrolling back to the first column.
Cheers

Sticky columns are not yet supported. But we will add your request to our
discussions on future features :)
On Tue, Apr 11, 2017 at 8:08 PM Ali Yazdani<EMAIL_ADDRESS>wrote:

Problem Description
Wondering if currently there is a way to get the first column ( y-axis if
you're doing 2 dimensional data) to be a sticky column so that if you have
a large table with scroll you can see the categories?
I'm doing a time series as column headers and sometimes the table has a
hundred columns so when the user scrolls they wouldn't see the first column
that holds the list of metrics - forcing them to keep scrolling back to the
first column.
Cheers
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerlinsley/react-table/issues/190, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFUmCVZl_Nne1nMeBox9ASLNNetnvZYVks5rvDIjgaJpZM4M63O6
.


Import Harvester 1.2.1 in Rancher 2.8 both single node problem

Hello,
just wanted to experiment with Harvester and Rancher integration.
I have installed Harvester 1.2.1 on single node (virtual machine) through PXE.
Dashboard accessible on mgmt ip after setting up the new password and all seems ok.
In console I see "Ready" for both Harvester Cluster and Node.
BTW: in Dashboard --> settings the cluster-registration-url is empty
Do I have to put here anything?
I have installed Rancher 2.8 on single node (virtual machine), installing Ubuntu 22.04 through PXE, then installing docker (version 24.0.7 community edition), then running the docker install command as describe here:
https://ranchermanager.docs.rancher.com/v2.8/pages-for-subheaders/rancher-on-a-single-node-with-docker
docker run -d --restart=unless-stopped
-p 80:80 -p 443:443
--privileged
rancher/rancher:latest
Dashboard accessible after setting up the new password and all seems ok.
Now I would like to import the Harvester cluster and experiment the integration part. But I don't find correspondence between doc pages and other links and what I see.
BTW: when imported through rancher will I be able to run also containers in my harvester cluster creating them from within rancher, or the harvester cluster will be confined to run only VM workloads?
If I select "Virtualization Management" in GLOBAL APPS section I'm proposed to "Import Existing". If I click the button I get a page where I only have to input a "cluster name"
See screenshot here:
https://drive.google.com/file/d/1v1a6qJtai9sUXUerzvKKxEUvIKQJZTsT/view?usp=sharing
but any name I put there I get a "Network Error" message:
https://drive.google.com/file/d/1MYLb95eD8qSqGjeIZtIW5yUgDMNG2BtF/view?usp=sharing
Does it depend on rancher being inside docker? Any further setting to do?
It seems that:
. from inside the rancher docker container I'm able to reach port 6443 of the Harvester mgmt ip.
. from inside the harvester server I'm able to reach port 443 of rancher ip
Thanks for any suggestion or link with documentation.
Gianluca

@gcecchi I would suggest if you're experimenting with Harvester with Rancher, use Rancher v2.7 as per the support matrix.

BTW: in Dashboard --> settings the cluster-registration-url is empty

Initially, the url is empty because it is not registered with Rancher yet, you'll need to edit it and save the url provided by Rancher. Steps are here

Thanks for the reply.
You are right, my fault. With 2.7.9 all went fine in importing harvester 1.2.1.
Rethinking about my steps, I did go through the support matrix. But then when searching the requirements to install rancher as single node I didn't put enough attention to the "latest" wording and so Rancher 2.8 was pulled/installed.
I have to say  that also the version specific link:
https://ranchermanager.docs.rancher.com/v2.7/pages-for-subheaders/rancher-on-a-single-node-with-docker
contains "latest" in the docker run command, while probably it should contain "v2.7.9", to avoid confusion.
After using "latest" I didn't consider that 2.8 was pulled in and forgot the support matrix, my bad.
Questions: from command line I can create pods/deployments in Harvester. Can i manage them from within Rancher GUI after importing it? i don't see how. Or harvester k8s can only managed by GUI for kubevirt VM workloads?
Also, can I use the Rancher local k8s env to manage containers workloads from gui? Or is it only intended to be used for its mgmt capabilities and I have to import another k8s cluster to manage deployments and pods?
Thanks,
Gianluca

@gcecchi We would like to know your use case in details to understand what's your requirement exactly. I have put some doc reference to answer your questions, hope that helps.
If you are using Rancher to manage k8s cluster running on VMs in Harvester, docs explains the steps, the page also contains the details for Baremetal container workload support.
If you are looking for Rancher Manager as a workload on the underlying Harvester cluster, the details are here
Note: Baremetal container workload support and Rancher manager on underlying Harvester cluster are experimental features at this moment.

Thanks for your reply and the doc references. My use case at the moment is basically to familiarize with the features of Rancher and Harvester and have an idea of the possible implementation scenarios based on different needs.
Based on the docs it seems to me that:
. when you import Harvester in Rancher, you can manage by default only its kubevirt based VMs, through:
Hamburger  --> Virtualization Manager. It works for me
. when enabling experimental features you mentioned above, from within Rancher you can also manage the containers' workloads inside the Harvester cluster, through:
Hamburger --> harvester-assigned-name that appears now in the "EXPLORE CLUSTER" section. It works for me
. when you import a generic k8s cluster (in my test case a K3S installed on a separate SLES 15 VM with  K3s_VERSION="v1.26.12+k3s1"), from within Rancher you can manage it in the "EXPLORE CLUSTER" section, where its name appears after a successful import phase. It works for me
Let me know if I understood correctly, please.
The only doubt remained is about the Rancher "local" k8s cluster itself that I see in "EXPLORE CLUSTER" section: is it meant to be used as a regular normal k8s cluster with its workloads without particular limitations, or should I leave it dedicated to internal Rancher logics?
Thanks again,
Gianluca

The local cluster is the Kubernetes cluster that is running the Rancher server workloads, it is not recommended to use it for general purposes but you can if needed.

Closing this now. @gcecchi feel free to reopen if you have further doubts.


Enum plus struct

Codecov Report
Patch coverage: 48.20% and project coverage change: -0.92 :warning:

Comparison is base (1b5ed5f) 55.63% compared to head (a42622d) 54.72%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #341      +/-   ##
==========================================
- Coverage   55.63%   54.72%   -0.92%
==========================================
  Files          32       32
  Lines        4984     5082      +98
==========================================
+ Hits         2773     2781       +8
- Misses       2211     2301      +90

Impacted Files
Coverage Δ

zingocli/tests/integration_tests.rs
80.88% <ø> (ø)

zingolib/src/commands.rs
0.00% <0.00%> (ø)

zingolib/src/wallet.rs
63.47% <0.00%> (ø)

zingolib/src/wallet/traits.rs
51.26% <0.00%> (-0.81%)
:arrow_down:

zingolib/src/wallet/transactions.rs
60.88% <0.00%> (+1.47%)
:arrow_up:

zingolib/src/wallet/data.rs
47.97% <14.28%> (-5.92%)
:arrow_down:

zingolib/src/lightclient.rs
55.67% <53.28%> (-2.62%)
:arrow_down:

zingolib/src/blaze/fetch_full_transaction.rs
78.29% <100.00%> (ø)

... and 4 files with indirect coverage changes

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

Superceded


Openblas installation points to generic BLAS/LAPACK

Hi,
I installed `libopenblas-dev' using apt-get on my Ubuntu 16.04 system. At the end of installation, the update-alternatives sets the following
update-alternatives: using /usr/lib/openblas-base/libblas.so to provide /usr/lib/libblas.so (libblas.so) in auto mode update-alternatives: using /usr/lib/openblas-base/liblapack.so to provide /usr/lib/liblapack.so (liblapack.so) in auto mode
But the libraries it is poitning to, doesn't contain any OpenBLAS specific functions such as openblas_get_num_threads as it gives not found in cmake.
I also verified this by doing
readelf -Ws /usr/lib/liblapack.so >> res.txt
grep "openblas" res.txt
And the output was none, same for libblas.so
the file '/usr/lib/libopenblas.so" however contains all the openblas specific functions.
Any reason why is it so?

You will probably need to ask the Ubuntu folks who packaged openblas. The standard build of OpenBLAS will contain all functions (including BLAS and LAPACK) in a single libopenblas.so file that may have to be symlinked to the libblas, liblapack names for compatibility with other programs if you want to switch implementations at will. There is some background discussion in issue #296

See also https://github.com/xianyi/OpenBLAS/wiki/Faq#debianlts - what comes with Ubuntu 16.04 is probably a bit old (0.2.18 from early last year I guess)

libblas.so that gcc -lblas reads is nrtlib reference blas to keep peoples code portable.
you can update that alternative to point to openblas, but probably you need to do -lopenblas instead.
me being author of particular FAQ paragraph - I intentionally left that part out to keep it working like debian packagers intended.

What debian does is it creates a libblas.so.3 which links against libopenblas.so, but exports only the symbols from the blas API. So, when you do -lblas you are linking against a library which in turn links against libopenblas. If you want openblas symbols, use -lopenblas

@vermashresth can you close the issue? We dont maintain that package and 'ubuntu-support-status' on my 16.04 says vendor does not either.

@brada4 Sure, sorry for late reply.  It does seem to be an issue from package side because it worked fine on Ubuntu 14.04 and @isuruf 's answer works too. Thanks for the help!


missing yml files

Could you please upload the yml files?

https://github.com/NVlabs/intrinsic3d/tree/master/data


Edge Device vs Edge Module twin

Can you please clarify the difference between Edge Device and Edge Module Twin? I understand the purpose of Edge Module Twin but it is not clear who is supposed to interact with Edge Device Twin and why. thanks

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

ID: 539283ad-ccdb-02bc-4178-f6cee6173319
Version Independent ID: 4dec5ce6-d4c8-55d3-f2d4-323e331d3dd4
Content: Learn how modules run logic on your devices - Azure IoT Edge
Content Source: articles/iot-edge/iot-edge-modules.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@smoms Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @smoms Thanks for reaching out! The twin is a representation of the device "state" and a backend application can interact with it to induce changes in the device state that IoT hub will communicate to the physical device.  You can use the "state" of the twin to change logic in the device itself.
Please see this tutorial: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-node-node-twin-getstarted

@Alberto-Vega-MSFT thanks. I know what is a Twin. My question is rather focused on the use of device twin for Edge devices. I haven't see any example. All twins for Edge are implemented through module twin. Again, how would you use device twin concretely? Both the Edge runtime and apps have already their module twins. Would you write another module that is going to manage both module and device twin?

Hello @smoms, IoT Edge Device Twin should be treated as a normal Device Twin with the difference being that iotEdge capability is set to true:
"capabilities": {     "iotEdge": true   }
For example, on an IoT Edge deployment the target condition interacts with tags defined on IoT Edge Device Twin. See here.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Confirm the Maximum nested conditionals count of Azure policy rule on Azure China(https://portal.azure.cn)

Hi colleague,
Our customer encounter the following issue when creating azure policy in Azure China portal(https://portal.azure.cn):
Name: Creating policy assignment failed

Actually, we check the Azure Policy limits and find it describe the Maximum count equal to 512.
https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-policy-limits

Could you please help to confirm the following our concerns?
Q1: the Maximum count of Azure policy on Azure China.
Q2: Can we submit request to raise the Maximum count on https://support.azure.cn/support/support-azure/ when necessary ?
Q3: If the customer's policy count is bigger than the Maximum count of Azure China configuration, Is there any advice to meet this requirement?
Best Regards,
Edward Chen

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

ID: 36f49a06-90b1-cbe1-3853-2c38277b79f8
Version Independent ID: 02ff6f6c-3ef6-b48f-060d-b290419e0aba
Content: Azure subscription limits and quotas - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/azure-subscription-service-limits.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@rockboyfor Thank you for your query . We will surely help you with this issue .

@shashishailaj , Would you please share us any progress or schedule on this issue? Our customers are anxious to resolve this issue that have compacted the deployment on Azure China Cloud.

@rockboyfor Apologies for the delayed response on this. I have reached out to our internal product team to answer your questions. Will keep you updated as I hear more information.

Update: Currently the limit is 4096 for the ‘if’ condition and 128 for existence condition regardless of which Azure cloud type. We are working on updating the documentation.

@KrishnaG-MSFT,
Appreciate your great help!
Would you please help to confirm the other questions, Q2 and Q3 listed in the beginning of this thread?
Best Regards,

Update: We normally don’t increase the limits on number of conditions in a policy definition. If you are hitting the limit, we would likely want to assess the goal of the policy definition. Happy to discuss more offline if needed and loop in appropriate program manager in the conversation. If needed, send an email at<EMAIL_ADDRESS>

At this point it appears that there's no edits or updates needed for the referred Azure documentation so closing this issue for now. If there are further questions regarding this matter or feedback on the referred Azure documentation, please do let us know and we will gladly continue the discussion.


Can't access camera from VMware Fusion VM on MacOS

| Camera Model                        | D415
| Firmware Version                    | v2.40.0
| Operating System & Version | MacOS
| Kernel Version (Linux Only)  | Ubuntu 20.04
| Platform                                  | ?
| SDK Version                           | 2
| Language                               |  Python
| Segment.     			          | ?
I'm not able to see the device on either my MacOS or my VMware VM. Does anyone have any troubleshooting suggestions?
https://communities.vmware.com/t5/VMware-Fusion-Discussions/USB3-camera-is-not-recognized-on-OSX/m-p/2310098
I followed these steps but I'm still not able to see it in either location... ideally, I'd be able to use it on my VM.

https://kb.vmware.com/s/article/57195
This ended up helping, so at least I see the device on lsusb. It doesn't yet show up on realsense-viewer for me.

I needed to change the settings to use USB 3.1 instead of 2.0 on VMware. You can see on dmesg -Tw that this was causing an issue with connecting. Shows up on lsusb now.


pythonPackages.pysonos: init at 0.0.11

pysonos package provides ability to control sonos media player using python. The original need was to use it with the home-assistant package, specifically the "sonos" component.

Why did you remove the standard checkboxes from the PR message?
Please squash the commits. Hint: Use rebase instead of merge when you want to update your private branch.

Please delete this. I mess it.

new attempt in #60853


tablecloth/dataset does not throw in case of not existing input file

(tablecloth.api/dataset "not-existing.csv")

does not throw exception, but returns a dataset with some information of error.
Is this on purpose ?
(tech.v3.dataset/->dataset "not-existing.csv")

throws file-not-found exception , as I would have expected.

TC allows to create a singleton dataset (one row and column) just from the value. It was done only when other ->dataset cases failed.
It has been discussed somewhere in the past already (on Zulip, probably with jsa). After this, some options were introduced: https://github.com/scicloj/tablecloth/blob/master/src/tablecloth/api/dataset.clj#L60
I see this can be a little bit unfortunate, maybe stack-trace? option should be true by default?

I find it scary,  that it does not throw an exception,  if file not found. So maybe we can handle FileNotFoundException differently

Good idea.


Graphql @auth rules - Fails on nested relationship data when using an groupsField of a ID Indexed attribute.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v20.3.0
Amplify CLI Version
12.2.1
What operating system are you using?
Windows WSL Ubuntu
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
Project Overview

I am building an onboarding website using React, NextJS, and Amplify.
The application uses cognito to manage users. I have a group called Admin and then each accounts id is a group in cognito. When a cognito user is created a custom attribute is added called accountID. In addition there is a dynamoDB table called AuthUser that is a mirror of the cognito user so that I can create a relationship between the Account table and the AuthUsers in a 1 to many relationship.
The objective is to limit users who are not admins to only be able to query and mutate data based on their accountID.

Issue
While signed into a user that is not an Admin and the app queries a table with nested relationships the query fails.
GraphQL Schema
type Account @model @searchable @auth(rules: [
  {allow: groups, groups: ["Admin"], operations: [read, create, update, delete]},
  {allow: groups, groupsField: "id", operations: [read, update]}
  ]) {
  id: ID!
  account_name: String!
  products: AWSJSON
  authUsers: [AuthUser] @hasMany(indexName: "byAccount", fields: ["id"])
  locations: [Location] @hasMany(indexName: "byAccount", fields: ["id"])
  devices: [Device] @hasMany(indexName: "byAccount", fields: ["id"])
  users: [AccountUser] @hasMany(indexName: "byAccount", fields: ["id"])
  dids: [PhoneNumber] @hasMany(indexName: "byAccount", fields: ["id"])
  stage: String,
  locked: Boolean
}

type AuthUser @model @auth(rules: [
  {allow: groups, groups: ["Admin"], operations: [read, create, update, delete]},
  {allow: groups, groupsField:"accountID", operations: [read, update]}
  ]) {
  id: ID!
  accountID: ID! @index(name: "byAccount")
  last_name: String
  first_name: String
  email: AWSEmail
}

GraphQL Query:
query GetAccount($id: ID!) {
    getAccount(id: $id) {
        id
        account_name
        stage,
        locked,
        products,
        authUsers {
            items {
                id,
                email,
                first_name,
                last_name,
            }
            nextToken
        },
    }
}

Expected behavior
Troubleshooting 1

When logged in as a user that is in the group Admin everything works.
When logged in as a user that is not an admin the query fails.

Troubleshooting 2
- I started to remove attributes from the query statement and noticed that any nested attribute that has a relationship with another table would fail. If I remove all attributes that reference another table the query would work.

When logged in as a user I tried to query Auth User (not nested) and it returns I tested querying Account(nested via Auth User) and it fails. If I remove the nested data from the query it succeeds.

Example of Failed Query
query GetAccount($id: ID!) {
    getAccount(id: $id) {
        id
        account_name
        stage,
        locked,
        products,
        authUsers {
            items {
                id,
                email,
                first_name,
                last_name,
            }
            nextToken
        },
    }
}

Example of Successful Query
query GetAccount($id: ID!) {
    getAccount(id: $id) {
        id
        account_name
        stage,
        locked,
        products,
    }
}

The Error Message
After successfully testing with an Admin group user I am 100% sure my schema and types are correct. I am curtain that the issue has something to do with the groupFields in Account when trying to query AuthUser. And if I just query AuthUser it works just fine.
Reproduction steps
Reference my schema and try to query Account with a nested table AuthUsers whos groupField value is of type ID! and indexed.
Project Identifier
bd5885134c410bd1c722a5e7e4f301d4
Log output
Browser Error

next-dev.js:20 Error: One or more parameter values were invalid: Condition parameter type does not match schema type (Service: DynamoDb, Status Code: 400, Request ID: 73NAQRPLFNSKFITFSRH0G2MNRNVV4KQNSO5AEMVJF66Q9ASUAAJG)
    at Object.eval [as queryFn] (fetcher.ts:20:19)
window.console.error @ next-dev.js:20
onError @ query.mjs:294
reject @ retryer.mjs:63
eval @ retryer.mjs:122
Promise.catch (async)
run @ retryer.mjs:106
createRetryer @ retryer.mjs:149
fetch @ query.mjs:307
executeFetch @ queryObserver.mjs:168
setOptions @ queryObserver.mjs:86
eval @ useBaseQuery.mjs:42
commitHookEffectListMount @ react-dom.development.js:23150
commitPassiveMountOnFiber @ react-dom.development.js:24926
commitPassiveMountEffects_complete @ react-dom.development.js:24891
commitPassiveMountEffects_begin @ react-dom.development.js:24878
commitPassiveMountEffects @ react-dom.development.js:24866
flushPassiveEffectsImpl @ react-dom.development.js:27039
flushPassiveEffects @ react-dom.development.js:26984
eval @ react-dom.development.js:26769
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533

CloudWatch API Error Log

{
    "logType": "ResponseMapping",
    "path": [
        "getAccount",
        "authUsers"
    ],
    "fieldName": "authUsers",
    "resolverArn": "arn:aws:appsync:us-west-2:527661105615:apis/***********/types/Account/resolvers/authUsers",
    "functionName": "AccountAuthUsersDataResolverFn",
    "requestId": "97b83bd4-f9ce-4a48-a87b-20d5e25e9d07",
    "context": {
        "arguments": {},
        "source": {
            "createdAt": "2023-02-17T21:28:32.044Z",
            "stage": "new",
            "__typename": "Account",
            "account_name": "Audian",
            "id": "0cced1b5-e4d1-4ecd-918b-5056486fb90e",
            "locked": false,
            "products": {
                "seats": {
                    "total": 12,
                    "available": 10,
                    "inService": 0
                },
                "softphones": {
                    "total": 2,
                    "available": 4,
                    "inService": 0
                },
                "faxboxes": {
                    "total": 1,
                    "available": 2,
                    "inService": 0
                }
            },
            "updatedAt": "2023-03-21T20:25:21.869Z"
        },
        "prev": {
            "result": {}
        },
        "stash": {
            "authRole": "arn:aws:sts::527661105615:assumed-role/***********-101447-authRole/CognitoIdentityCredentials",
            "conditions": [],
            "connectionAttributes": {
                "id": [
                    "0cced1b5-e4d1-4ecd-918b-5056486fb90e"
                ]
            },
            "fieldName": "authUsers",
            "hasAuth": true,
            "metadata": {
                "dataSourceType": "AMAZON_DYNAMODB",
                "apiId": "*********m3ve"
            },
            "tableName": "AuthUser-*******3ve-dev",
            "typeName": "Account",
            "unauthRole": "arn:aws:sts::527661105615:assumed-role**********-101447-unauthRole/CognitoIdentityCredentials"
        },
        "error": {
            "message": "One or more parameter values were invalid: Condition parameter type does not match schema type (Service: DynamoDb, Status Code: 400, Request ID: 2AIVH5RKMA2EMTQJ9673KND3O3VV4KQNSO5AEMVJF66Q9ASUAAJG)",
            "type": "DynamoDB:DynamoDbException"
        },
        "outErrors": []
    },
    "fieldInError": true,
    "errors": [
        "CustomTemplateException(message=One or more parameter values were invalid: Condition parameter type does not match schema type (Service: DynamoDb, Status Code: 400, Request ID: 2AIVH5RKMA2EMTQJ9673KND3O3VV4KQNSO5AEMVJF66Q9ASUAAJG), errorType=DynamoDB:DynamoDbException, data=null, errorInfo=null)"
    ],
    "parentType": "Account",
    "graphQLAPIId": "********m3ve",
    "functionArn": "arn:aws:appsync:us-west-2:527661105615:apis/*********3ve/functions/k*******76tkq"
}

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hello, so I tried using owner instead of group as seen below and this resolved my issue. I am still curious why groups doesn't work the way it should.
type Account @model @searchable @auth(rules: [
  {allow: groups, groups: ["Admin"], operations: [read, create, update, delete]},
  {allow: owner, ownerField:"id", identityClaim:"custom:group", operations: [read, update]}
  ]) {
  id: ID!
  account_name: String!
  products: AWSJSON
  authUsers: [AuthUser] @hasMany(indexName: "byAccount", fields: ["id"])
  locations: [Location] @hasMany(indexName: "byAccount", fields: ["id"])
  devices: [Device] @hasMany(indexName: "byAccount", fields: ["id"])
  users: [AccountUser] @hasMany(indexName: "byAccount", fields: ["id"])
  dids: [PhoneNumber] @hasMany(indexName: "byAccount", fields: ["id"])
  stage: String,
  locked: Boolean
}

Hey @dklein1211, We appreciate you bringing up the issue and sharing the effective workaround you've found. We will look into the problem from our end and keep you informed of our investigation progress.

Hi @dklein1211 Good to know that you're now using owner based Auth since your setup with dynamic group Auth is not supported since the groupField is not of type String or [String]. Also, storing group names as primary keys is not scalable as you would then need to create different groups for each user. I've tested a couple of variations of this schema and did not run into this error. Closing this issue. Thanks.


Fat Experience Orbs

Mod name
[Fabric] Fat Experience Orbs
Curseforge link
https://www.curseforge.com/minecraft/mc-mods/fat-experience-orbs
Modrinth link
N/A
Other link
N/A
What it does
This mod makes it so that nearby experience orbs merge together, when installed on the client this mod allows experience orbs to merge in single player. When installed on a dedicated server no client is required to have the mod.
Why should it be in the modpack
No lag In XP Farms
Why shouldn't it be in the modpack
Mods will go without support of any kind, simple updates to new versions is still a possibility.
Categories

[x] Performance optimization
[ ] Graphics optimization
[ ] New feature
[ ] Optifine parity
[ ] Fixes a bug/dependency
[ ] Replaces an existing mod

Additional details
N/A

Current thoughts:

changes vanilla behavior a bit too much, defying expectations
only in singleplayer is a shame
I wonder how often/significantly it actually helps with FPS

As someone who uses a rough equivalant to this feature: Carpet's combineXPOrbs

When designing/using overkill XP farms, this 100% helps with lag.
Users that need this feature will likely have carpet installed themselves, so don't need a mod for it.

nice thx for a new alternative of this mod

may i add carpet to issues

as mod request i think people will like this and i will close this


Need have version information for irqstat

Currently, irqstat doesn't define any version information.
Could we define a version/release information?
How about add irqstat -v or --version option as well?

Versioned, tagged, and released.
To get version info:
irqstat -v
or
irqstat --version
Please use this release:
https://github.com/lanceshelton/irqstat/releases/tag/v1.0.0
It is available for download as a .tar:
https://github.com/lanceshelton/irqstat/releases/download/v1.0.0/irqstat-v1.0.0.tar
Let me know if that is good enough for now.

Thanks for your prompt response.
It looked good to me.


JSON_Parser_BUG

What version of Go are you using (go version)?
gol.19.10

$ go version
go version go1.19.10 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
linux fedora
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/infernus01/.cache/go-build"
GOENV="/home/infernus01/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/infernus01/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/infernus01/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/lib/golang"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.10"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/infernus01/Downloads/json-parser-main/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build812051444=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.19.10 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.19.10
uname -sr: Linux 6.4.4-100.fc37.x86_64
/lib64/libc.so.6: GNU C Library (GNU libc) stable release version 2.36.
gdb --version: GNU gdb (GDB) Fedora Linux 13.2-2.fc37

What did you do?

What did you expect to see?
What did you see instead?

Related Issues and Documentation

some issues here ! #39105 (closed)
s #48271 (closed)
go fix #42243 (closed)
juan #51096 (closed)
Update funny #60279 (closed)
go fix #51512 (closed)
rs_bug #44374 (closed)
go bug #67882 (closed)
go build #51949 (closed)
go version go1.21.5 linux/amd64 #67008 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


Update HOW_TO_INSTALL.md

As it came up via https://www.reddit.com/r/NextCloud/comments/1ggi873/nextcloud_assistant_in_talk/

It's probably better to merge it with #9 as the HOW_TO_INSTALL.md text will be moved into README.md and the info.xml app description, feel free to suggest the changes there instead.


Update creating-a-github-pages-site-with-jekyll.md

Why:
The previous instructions for installing the github-pages gem via the Gemfile were confusing. If you search for could not find gem github-pages in your favorite search engine, you'll find that the instructions caused people to do one or more of the following things:

they didn't uncomment the # gem "github-pages" line
they tried to run `bundle update github-pages
they replaced VERSION with the version of jekyll listed on the Dependency versions page instead of the github-pages version.

Examples of people who got stuck:

https://talk.jekyllrb.com/t/how-to-install-github-pages-with-jekyll/3510
https://talk.jekyllrb.com/t/why-cant-i-install-the-github-pages-plug-in-when-i-set-up-jekyll/3743

This is my attempt to make things clearer by being more specific step by step. By pointing to the Rubygems page for github-pages, it removes any ambiguity that the previous dependency page introduced since it lists a bunch of different gems, and it's not absolutely clear which version you're supposed to look for, as evidenced by the person who pinned the github-pages gem to a version number for the jekyll gem.
Here's the issue I created for this PR: https://github.com/github/docs/issues/2177
What's being changed:
Instead of an image containing the confusing suggestion to run bundle update github-pages, I rephrased the instructions in the image so that they can be followed step by step, and added a step to run bundle update, since that is what is needed to install the github-pages gem, and the previous instructions did not mention that.
I also updated Step 7 because it was both confusing and incorrect. Running jekyll 3.9.0 new . does not work. 3.9.0 is being interpreted as a subcommand, and it is not a valid subcommand. Also, the Bundler section is more confusing than helpful because for bundle exec to work, a Gemfile must exist in the directory, but the instructions don’t mention that. Furthermore, if we did create a Gemfile by running bundle init for example, it would cause an error when running bundle exec jekyll new . because Jekyll expects the directory to be empty. Jekyll creates its own Gemfile so it doesn't make sense to start a new Jekyll site with Bundler.
To avoid all of this confusion, I simplified step 7 to just jekyll new ., which will create the Jekyll site using whatever version of Jekyll is currently installed (most likely 4.2.0).
In step 8, they are told to comment out the jekyll gem, so it doesn't matter if they used a more recent version of jekyll to create the site initially. What matters is that after they save the Gemfile, they need to run bundle update because github-pages only supports jekyll 3.9.0 currently. Running bundle install results in dependency issues.
Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[X] For content changes, I have reviewed the localization checklist
[X] For content changes, I have reviewed the Content style guide for GitHub Docs.

@monfresh Thanks so much for opening a PR! I'll get this triaged for review ⚡

Commenting to prevent this PR from being closed on Monday.

Thanks for the suggestions, @BenWhetton. I've accepted them.

Thanks for the suggestions, @BenWhetton. I've accepted them.

@hubwriter Thanks for the suggestions. I accepted them.

@monfresh & @BenWhetton - many thanks for contributing to the GitHub documentation. Much appreciated. 🙇♂


Pass content-type header to fix filters

I was implementing this library using the a Guzzle7 http client. When trying to do a request to companies.list with a filter, the filter did not seem to be applied.
By changing my own Guzzle Client to always pass the Content-Type header, this was fixed. This shouldn't be necessary to configure on the outside though since the library itself knows that it always sends JSON bodies. Let's thus adapt the API Client itself so that custom http clients don't have to add this header themselves.

Any chance of getting this merged and released?


Config with static.json like in other buildpacks?

Hey guys,
how do I configure nginx with this buildpack? I know in other buildpacks, they use a file called static.json where you can configure your Nginx set-up like this
 {
   "https_only": true,
   "max_body_size": "10m"
 }

Is there any way to do this in this buildpack as well? I couldn't find anything in the documentation and issues.

Hi @lggwettmann :-)
The Language buildpacks typically don't ship with nginx/apache (with the exception of the PHP buildpack), since most languages typically have their own more specialised web server (eg gunicorn in the case of Python), and with the Heroku router fronting them with a reverse proxy is not normally necessary.
However if you'd like to use nginx, you can add an additional buildpack alongside the Python buildpack (docs for multiple buildpacks), such as:

heroku-buildpack-static (simpler config via a static.json file, but slightly less customisable, and the buildpack isn't as maintained as the one below)
heroku-buildpack-nginx

That said, depending on your use-case it something other than nginx might be preferable, for example if using Django then I would recommend WhiteNoise - see:
https://devcenter.heroku.com/articles/django-assets
Could you explain a bit more about the use-case?

Hey @edmorley,
thanks so much for your kind and detailed answer. I'm using this heroku-buildpack to run a Django project in a Dokku instance. I only need to change the max body size of upload and deactivate HTTP routing, so writing a complete sigil-template for a new Nginx config would be a bit overkill, but doable.
I just started using Dokku to deploy at some point and specified this buildpack only and it works great. We're serving static-files through Amazon S3, so no need for whitenoise. I'm not sure why or if we're using Nginx and gunicorn to be honest.
I guess I was just looking for an easier and more DRY way to config our Nginx server - and assumed it was possible with such a config file too. Looks like I'll have to take a closer look at what Dokku is doing and how to do the Nginx config there.
Thanks for your time!

@lggwettmann you're welcome! Thank you for the extra context.
I'll close this out for now, but feel free to reopen if you have any follow-up questions :-)


New version: CMDimData v0.2.0

Registering package: CMDimData
Repository: https://github.com/ma-laforge/CMDimData.jl
Created by: @ma-laforge
Version: v0.2.0
Commit: 2dff7f35ee022d5ece661f9b3c49eb82c1cce42c
Reviewed by: @ma-laforge
Reference: https://github.com/ma-laforge/CMDimData.jl/commit/2dff7f35ee022d5ece661f9b3c49eb82c1cce42c#commitcomment-41645527
Release notes:

Restructure EasyPlot interface & handle multiple y-strips.
Also:
Clean up/fix code, add documentation, ...
Add "parametric_sin.jl".
Add Live-Slice example.

Hi,
PR has been in queue for 10 days.
I tried tagging the next release to get something going:
-> https://github.com/JuliaRegistries/General/pull/19595
But that automerge also failed because this particular PR we are in right now is still not merged.
Could I have created a new PR to overwrite this one (changed some code - specifically add dependency information)?
I would have normally cancelled this PR, and created a new one - but that does not appear to be an option.

PR has been in queue for 10 days.

You could have fixed the complaint 10 days ago. Do you not intend to fix it? If so you have to request a manual merge.

@fredrikekre: You could have fixed the complaint 10 days ago.

I could? How do I do this?
If I push a fix to my repo, it doesn't "fix" this PR - And any change I do to my Project.toml changes the associated Git SHA.
->so I tried releasing my "next" version with the fixes on bounds instead (v0.2.1: https://github.com/JuliaRegistries/General/pull/19595)
Obviously what I did was not useful (potentially dangerous?), so I decided to stop & wait.
Question
Should I have simply re-issued a "@JuliaRegistrator register" command with the same version number?
If so, I will do it right now (and it would be nice if someone could cancel PR https://github.com/JuliaRegistries/General/pull/19595 for me)
But if that's not possible
Then yes: I request a manual merge.  I did not know we had to request manual merges. I thought someone just did it after 3+ days or so.

Aaaaah, sorry. I saw that the email sent out when we register tells us what we can do (I still have mine for v0.2.1:
Also, note the warning: Version 0.2.1 skips over 0.2.0
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

But it would be nice if that were also written by the github-actions bot, in the comment above. I'll open a bug for that.

I could? How do I do this?

https://github.com/JuliaRegistries/General#my-pull-request-was-not-approved-for-automatic-merging-what-do-i-do

Should I have simply re-issued a "@JuliaRegistrator register" command with the same version number?

Yes.

But it would be nice if that were also written by the github-actions bot, in the comment above. I'll open a bug for that.

It is: https://github.com/JuliaRegistries/General/pull/19595#issuecomment-674445317

is because I added comments without [noblock] earlier on

Yes, you can edit them to add it.

Many thanks! I was not aware of this.


Allow the main navigation hamburger menu to be used (in lieu of tabs) on any size display -- xs, sm, md, lg, or all of them

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change

This enhancement allows portal adopters to specify a property -- org.apereo.portal.layout.useTabsSize -- that determines at what display size (and above) the main navigation hamburger menu will switch to tabs.  Before this change, the menu is always hamburger at or below @screen-sm-max and always tabs at @screen-sm-min or above.
The options (for this property) are:

sm
md
lg
none

If none is specified, the main navigation menu will always be hamburger style.
The property is optional;  the default behavior is the same as before the change.

@cousquer -- it looks like at one time you wanted to refactor the navigation.less file.

This PR includes a tiny but important fix to the OidcUserInfoController, so I'm going to merge it slightly sooner than I normally would.

Hello @drewwills [post merged comment - apologies for the delay,]
Drew,
Due to -well, [you know and can imagine my context, Time Zone, etc.]... (I've been also working on uPortal Summit Paris Feedback Document in English the all day.)
This PR should fix a lot of my three years ago imperfect code. As usual, Many thanks.
I will take time one hour tomorrow to test this PR. and will send you feedbacks.

A simple comment. this is a massive visual, logical and end user Experience change.
My only Request may be that this should be communicate to the community as one of the two first idems (in strong, bold) in the changelog.
/cc @ChristianMurphy @drewwills @jgribonvald

@cousquer -- Covering this new capability in the change logs is a great idea.
The default behavior of navigation in Respondr is unchanged by this PR.


Missing PodSecurityPolicy for startup API check job

Describe the bug:
Helm chart 1.5.0 fails to install (or upgrade) in a cluster with PSP enforced.
Steps to reproduce the bug:
Deploy a new helm release with jetstack/cert-manager version 1.5.0, using a configuration that enables PSP as shown below:
global:
  rbac:
    create: true
  podSecurityPolicy:
    enabled: true
    useAppArmor: false
securityContext:
  runAsNonRoot: true
  fsGroup: 1000
  runAsUser: 1000
webhook:
  securityContext:
    runAsNonRoot: true
    fsGroup: 1000
    runAsUser: 1000
cainjector:
  securityContext:
    runAsNonRoot: true
    fsGroup: 1000
    runAsUser: 1000
startupapicheck:
  securityContext:
    runAsNonRoot: true
    fsGroup: 1000
    runAsUser: 1000

The Helm install failure seems to be related to the startup API check job:
add-ons       2m40s       Warning   FailedCreate              job/cert-manager-startupapicheck                                 Error creating: pods "cert-manager-startupapicheck-" is forbidden: unable to validate against any pod security policy: []

Looking at the templates, it's the only pod that doesn't have a PSP and associated RBAC resources.
Anything else we need to know?:
Environment details::

Kubernetes version: 1.17
Cloud-provider/provisioner: AWS EKS
cert-manager version: 1.5.0
Install method: helm

/kind bug

Thanks @ndegory
I'll ask @inteon to take  a look at the PR. I keep hearing that PSP is deprecated, and I don't know much about them. But since there are already PSPs included in the Helm chart, this seems consistent.
Is there any way to turn on the same PSP enforcement in our E2E tests so that we get early warning of these sort of problems in the future?
We already install kyverno, which I thought would have picked up this sort of thing.
https://github.com/jetstack/cert-manager/blob/54c66769bc253f4f786fe92cded132dab9de65fb/devel/setup-e2e-deps.sh#L34-L35

@wallrj , although PSP are deprecated since Kubernetes 1.21, they won't be removed before 1.25, and by then they should be replaced by Pod Security Standards and a new built in PodSecurity admission controller, which is still in alpha stage.
PodSecurity looks relatively close from PSP and should cover the basic requirement, with a small migration effort.
As far as I know, Kyverno is an external admission controller that can also be used in favor PSP, but it's not built in and can't be used to validate legacy PSP.
I see many official Helm chart continue to support PSP, but because of the deprecation I don't think it would be a good idea at this stage to change the e2e tests to enforce PSP in the CI.

So this breaks installation with Helm when you use --wait flag.
As a workaround, you can disable the check, which of course is not ideal. This can be done by adding the following snippet to your values:
startupapicheck:
  enabled: false


Drop support for oVirt /api, always use /ovirt-engine/api

Versions of oVirt 3.4 and older only supported the /api path for access to the
API. Since version 3.5 /ovirt-engine/api is supported as well, and /api is
deprecated. In version 4.0 /api was removed completely. The provider has
supported both paths, which caused confusion and problems during upgrades. As
we no longer need to support oVirt 3.4 or older, that support can now be
removed. That is what this patch does. The path will be still saved to the
'path' column of the 'endpoints' table, but not used at all.
https://bugzilla.redhat.com/1427653

@borod108 @masayag @pkliczewski @durandom please review.

Note that the relevant changes are only in the api_integration.rb file. The rest is needed to change the hundreds of places where /api needs to be replaced by /ovirt-engine/api in the VC .yml files.

@miq-bot add-labels bug providers/rhevm

Addressed the Rubcop issues and the offending string issues.

 Bug 1427653 - Rhev inventory refresh fails after rhev upgrade from 3.6 to 4.0

Removed the DEFAULT_PATH constant.

Note that this should be fine/yes and euwe/yes, in my opinion.

LGTM.
And yes @durandom , we are aware as for the supported versions.

@miq-bot assign @blomquisg
@miq-bot add_label fine/yes, euwe/yes
@blomquisg please merge

Fine backport details:
$ git log -1
commit 919c52497b7845a902a525ac14d9525a234ee212
Author: Greg Blomquist<EMAIL_ADDRESS>Date:   Thu Apr 6 16:17:14 2017 -0400

    Merge pull request #14469 from jhernand/drop_support_for_multiple_ovirt_paths

    Drop support for oVirt /api, always use /ovirt-engine/api
    (cherry picked from commit ac8b311ff4ca26b6258f8962302784135fef1032)

@jhernand It seems this PR depends on https://github.com/ManageIQ/manageiq/pull/14159 (which isn't currently marked as euwe/yes).  Also, there are a few conflicts.. Can you please create an Euwe PR?

Yes @simaishi , I am preparing the backport.

@simaishi the euwe backport is here:
[EUWE] Drop support for oVirt /api, always use /ovirt-engine/api
ManageIQ/manageiq#14786

Backported to Euwe via https://github.com/ManageIQ/manageiq/pull/14786


Refactor/update test on device

This PR updates the existing test to use the new nodelet and removes the tango_ros_node package.
Fixes #233.

@mcopejans Thanks, I added the missing tests.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix PauliOp.adjoint()

Summary

Resolve #9433
Add test for PauliOp.adjoint()

Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.925%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
66707

Relevant Lines:
78548

💛  - Coveralls


Chore: Hide New Read-Only TAP Admin Field

This PR adds a new read-only field to the Admin Review stage of the TAP application. This new field prevents Admin from submitting an application without completing the required fields, but only if the application is approved.

@karenhawkinson thanks for the guidance! It's been a minute since I had to make CSS changes 🙂 I think it's done correctly now


md5 reported in list_path is wrong for files on S3 uploaded as multipart

What happened?
rohmu assumes the Etag reported by S3 listObjectV2 is an MD5, this is false if the
file was uploaded as multipart, or for some cases of server side encryption:
https://docs.aws.amazon.com/AmazonS3/latest/API/API_Object.html#AmazonS3-Type-Object-ETag
https://github.com/aiven/rohmu/blob/8ae24adf491f26b676ed1ae0339aaa2dd87d96ae/rohmu/object_storage/s3.py#L248

I believe @fingon knew this very well when adding this. He chose to use md5 for "hash" because it was already used by other backends. The local backend reports the sha256 hash in the md5 field as an other example...
And swift is the only one using a generic hash key instead of md5 (which I'm not sure how it is computed).
We could probably review this handling..


Upgrade Dependency management plugin to 0.6.1.RELEASE

Some Spring projects have moved to Gradle 3, and the current version of IO plugin doesn't work in such setup OOTB due to spring-gradle-plugins/dependency-management-plugin#87, so manual upgrade of the Dependency management plugin is required.

Thanks for the PR. I've upgraded to 1.0.0.RC1 in https://github.com/spring-gradle-plugins/spring-io-plugin/commit/e78272cf82d6c501d659d9d6177e3f2181328e36. I'll probably wait for 1.0.0.RELEASE and the release a new version of this plugin.


Home Page UI (Issue #1068)

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

Kindly mention issue number

hello @codervivek5 ,
i have made home page  in  Front with-React-js folder. (According to new figma design )
Can you checkout this pull request : https://github.com/codervivek5/VigyBag/pull/1105#issue-2304760733

Thankyou for your contribution 🤗

@dhruv389 we have make some changes for more information join today's meeting at 10pm


Cleanup README and add official IRC channel and mailing list.

General update of the README.

Slighty rewrote the commit in this pull request (changed the commit message to match the standard JerryScript format), the new commit is at https://github.com/Samsung/jerryscript/commit/372a2bb40b031e796f9d9a0214ef23b74a4e1293
Apologies in advance to any downstream users who will see conflicts the next time they update! I have no further plans to rewrite the history of JerryScript and will strictly follow the process in the future :)

@tilmannOSG ,  even documents, expecting review before merge next time. :)

@lemmaa I promise to follow the process more closely in the future, still learning how all of this actually works on GitHub :)


Support for Kernel 3.16.x?

Hi,
Hardkernel recently released a new image for their ODROID C2, based on Ubuntu 18.04 with Kernel version 3.16.x . In terms of support, this Kernel is not bad, because it is an LTS version with support until 2020.
So do you think that we could get piVCCU running on that kernel somehow? Or is it just too far away from mainline?
Greetings

You can try it, but I will not officially support it, as it is to far away from mainline (not only the version, the patches of Hardkernel as well).
Same goes for the Device Tree Overlays. As far as I remember, they are not supported with the FEX Bootloader of Hardkernel.

Ok, thanks for the info, I will give it a shot.


Running Dexie with MS Edge on a real mobile device :  OpenFailedError: UnknownError occurred when opening database

Running the official sample drom DexieJS, all works fine on Edge browser.
However I'm using it to run inside an appContainer (Hosted Web App). Works good on Desktop, but not on a real device (tried with a Lumia 1520).
I'm getting an error:
Uncaught Promise: OpenFailedError: UnknownError UnknownError occurred when opening database FriendDatabase. OpenFailedError: UnknownError UnknownError occurred when opening database FriendDatabase
at Anonymous function (http://<IP_ADDRESS>/phc2/Dexie.js:2459:45)
at doResolve (http://<IP_ADDRESS>/phc2/Dexie.js:741:13)
at Promise (http://<IP_ADDRESS>/phc2/Dexie.js:585:13)
at Anonymous function (http://<IP_ADDRESS>/phc2/Dexie.js:2457:25)
at Promise.newPSD (http://<IP_ADDRESS>/phc2/Dexie.js:862:13)
at _promise (http://<IP_ADDRESS>/phc2/Dexie.js:2453:17)
at transactionPromiseFactory (http://<IP_ADDRESS>/phc2/Dexie.js:1327:17)
at resume (http://<IP_ADDRESS>/phc2/Dexie.js:1315:29)
at Anonymous function (http://<IP_ADDRESS>/phc2/Dexie.js:1280:17)
at Array.prototype.forEach (native code)
Dexie.js (892,9)
Have a repro ready to share if needed.

Which version of Dexie?

Have you tried this fiddle from your device?
Don't know if there are any special conditions related to running inside an appContainer though. Generally, IE (and probably Edge) doesnt allow accessing indexedDB when page is served from local hard drive. But if you host your web app from a local web server on the device this shouldnt be a problem.

Just tried it with 1.3.6, and the exact same error.

I'm also checking it out with Microsoft, to check if it is any edgeHTML/Chakra issue when running on mobile.
The scenario actually is running not from local content (inside app package), but actually from a remote web server.

Just tan the fiddle you mentioned, and I have exact same error:
Using Dexie v1.3.6
UnknownError: UnknownError occurred when opening database MyFriendDB

Strange. I ran it from a Windows phone 8.1 device on Browserstack with ie11.

Maybe double check that there's nothing wrong with the particular device you're testing on?

That's the difference. WP81. uses mshtml (IE web engine). W10Mobile uses edgeHTML (MSEdge web engine)

Yes, but still strange that indexedDB fails to open mobile Edge browser while it's working fine on Windows 10 desktop's edge browser.

Exactly. Will bring some insights from Edge team.

I once managed to make my edge browser corrupt and fail with UnknownError on open. Could reproduce the issue. Only a system reboot after deleting the db made it finally recover from the unstable state.
https://gist.github.com/dfahlander/5a39328f029de18222cf2125d56c38f7
Probably this is not the case with your device but just wanted to tell in case your device would be in a bad state.

@dfahlander , just to give some feedback.
Edge team, has confirmed it was an issue/bug and has already been corrected in w10 mobile. It will reach fast ring deployments quite soon. I'll provide further feedback when I test it on my device.
Thanks for the help.

Aha, thanks for sharing 👍

Closing to clean up.


Upgrade OpenZeppenlin contract versions

We should upgrade OpenZeppenlin contract versions (from 4.5.0 to the latest 5.0.0) and adapt the new changes, for example, the deprecated ERC1155Receiver mentioned in this PR.

If we bump @openzeppelin/contracts from 4.9.2 to 5.0.0, there would be some changes:

ReentrancyGuard moved from security to utils
Contracts require Solidity 0.8.20 or later

Update foundry.toml (tests)
Update hardhat.config.ts (deployment)

New _initialOwner parameter added to Ownable constructor

Update Authority constructor
Update CartesiDApp constructor

Removed PaymentSplitter (impacts the to-be-added Quorum)


resource_manager_flush_context returns TSS2_RC_SUCCESS instead of Tpm2Response pointer

The function resource_manager_flush_context has the following prototype:
Tpm2Response*
resource_manager_flush_context (ResourceManager *resmgr,
                                Tpm2Command     *command)

but returns   TSS2_RC_SUCCESS in some cases.
Is it desired to return a NULL pointer in these cases?
or would it be better to return a status word. (and not a pointer)
clang of course complains
src/resource-manager.c:460:16: error: expression which evaluates to zero treated as a null pointer constant of type 'Tpm2Response *'
      (aka 'struct _Tpm2Response *') [-Werror,-Wnon-literal-null-conversion]
        return TSS2_RC_SUCCESS;
               ^~~~~~~~~~~~~~~
/usr/local/include/sapi/tss2_common.h:149:49: note: expanded from macro 'TSS2_RC_SUCCESS'
#define TSS2_RC_SUCCESS                         ((TSS2_RC)0)
                                                ^~~~~~~~~~~~

I don't know what is the desired way to fix this.

Me either. Will queue this one up for tomorrow. Thanks for digging into the clang stuff.

Was a bit slow getting around to this one ...
Took a look just now and this check can just go away. The function is only called internally and the same check is already made by the caller (https://github.com/01org/tpm2-abrmd/blob/master/src/resource-manager.c#L819). I guess it would be equally valid to create a response object for the RC in this case like we do here: https://github.com/01org/tpm2-abrmd/blob/master/src/resource-manager.c#L485.
I'll see how these look in practice.

I've looked at this from a few different angles and IMHO the right thing to do is just return NULL here. PR is https://github.com/01org/tpm2-abrmd/pull/64. Will be merging shortly.


CORE-41 Graceful destruction of SpitfireRtc and RtcConductor instances

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

BTW where do you see m80? I can only see m79 there

BTW where do you see m80? I can only see m79 there

https://chromiumdash.appspot.com/branches shows all the branches. It is currently just unnamed at 3987

BTW where do you see m80? I can only see m79 there

https://chromiumdash.appspot.com/branches shows all the branches. It is currently just unnamed at 3987

Nice, I hope to remember this link because once in a while it will be useful again.


#879 backup restore

Hi, here's another contribution

Hi, here's another contribution

Sorry, I made this pull request to master instead to develop.
I will create a new one.


public nadeko give wrong .time

publict nadeko currently gives the wrong time at least when doing  .time denmark it's 2 hours behind. my self hosted one that havent been updated since july 15. still gives the correct time

Tested it out with Amsterdam and denmark. If i would believe Google, it seems to be proper working.
Can you give us some more details about wich platform you host on? Wich version you are (maybe on both)?


1084 data changes

Built on top of #1203 (review/merge that one first)
This PR modifies the RawData object to reflect the changes in the DB. It also fixes the tests for the RawData object.
All the other tests are still expected to fail.

1 minor comment so :+1:

Very minor comments, should be good to go after.

Comments should be addressed @antgonza @ElDeveloper

Got it, thanks! :+1: ready for merge.
On (May-27-15|16:03), josenavas wrote:

Comments should be addressed @antgonza @ElDeveloper

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/pull/1204#issuecomment-106104256


Hire page carousel content

New images need added

I'm guessing this is the FAC Cohort images. @nogainbar can I just pick some from the assets folder on the drive or do they need a special tint first?

Actually just realised the cohort images are #63 - Is this for the quotes carousel?
The company logos carousel is issue #67
Man there is a LOT of carousels! 😆

@developess we don't have the images for that page sorted yet. For now could you use a placeholder?

working on it @developess! will keep you posted! :)


Progress bars fixes

I'll fix the documentation in the morning
Also brings a portion of cpu_shorthand into this branch, shouldn't cause issues? Need to set defaults too

Also, didn't we agree on changing the flags to X_display instead of X_info_bar?

Thanks again. :)

All fixed! Apparently I write my best code at midnight when I'm about to fall asleep :P

All good! :+1:


PP: data model for exhibitions

Exhibitions need a data model in the same way that events has a data model

Exhibitions now has a (very lightweight) data model (wellcometrust/wellcomecollection-content-model#3).


feat: add proxy list for change agent to bypass google "TooManyRequestsError"

hi, i have new feature for this package

Hi @abolfazlakbarzadeh ,
Thank you for your awesome contribution😍. Tested it, and works fine✔.
I creating a new release now with it.


Add LB Health endpoint with TLS support

A short explanation of the proposed change:

An explanation of the use cases your change solves

Instructions to functionally test the behavior change using operator interfaces (BOSH manifest, logs, curl, and metrics)

Expected result after the change

Current result before the change

Links to any other associated PRs

[ ] I have viewed signed and have submitted the Contributor License Agreement

[ ] I have made this pull request to the main branch

[ ] I have run all the unit tests.

[ ] (Optional) I have run Routing Acceptance Tests and Routing Smoke Tests

[ ] (Optional) I have run CF Acceptance Tests

This requires routing-release 0.285.0


new | shorthand syntax article

The purpose of this PR is to move the Azure/azure-cli doc's article on shorthand syntax into MicrosoftDocs/azure-docs-cli.  We have well over 2k mentions of "Support shorthand-syntax, json-file and yaml-file. Try "??" to show more." in our autogenerated reference content. Yet we don't have a single mention in conceptual content of shorthand syntax.
I suggest adding to the autogen sentence "See <new short link to "use-azure-cli-successfully-shorthand.md"> to learn more."
@bebound, Is shorthand syntax still in preview?

@bebound, Is shorthand syntax still in preview?

@kairu-ms for confirmation.

@bebound, Is shorthand syntax still in preview?

@kairu-ms for confirmation.

It's ready for GA

Merging with @kairu-ms's approval.


⭐📄 [OPTIMIZATION_HARDENING][BE][QG][QG4][DOCUMENTATION][ARC42] Elaboration of Chapter "Deployment view"

As a project contributor in FOSS context
I want to have a quick and lean introduction to the project
so that I can manage the onboarding to the project and my contribution to the project self-managed
Hints / Details

Good practice: https://eclipse-tractusx.github.io/item-relationship-service/docs/arc42/introduction-goals/index.html
arc42 Examples - arc42

Acceptance Criteria

[ ] - Additional 10% of the ARC42 is elaborated, and additional documentation can be offered to external contributors

Out of Scope

won't do


MM-25434 Fix switch team badge cut off

Summary
The overflow hidden added to prevent the Cancel button to be displayed in the search bar on iOS while in landscape cause this little regression
Ticket Link
https://mattermost.atlassian.net/browse/MM-25434
Screenshots

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/6184
https://circleci.com/gh/mattermost/mattermost-mobile/6183

Artifact links:
https://6184-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.apk
https://6183-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.ipa


bindTexture doesn't seem to work if the TextureView doesn't have a surface yet

I tried debugging the problem a bit. The RxCameraInternal.surfaceCallback is registered with the TextureView but the RxCameraInternal object is not registered as the SurfaceCallback's listener (I don't see SurfaceCallback.setSurfaceListener being called anywhere).
I'm using verion 0.0.2.
Below is my code (very similar to the example). It is called in my Activity's onResume().
private Observable<RxCamera> initCamera(final TextureView view) {
    RxCameraConfig config = RxCameraConfigChooser.obtain().
            useBackCamera().
            setAutoFocus(true).
            setPreferPreviewFrameRate(15, 30).
            setPreferPreviewSize(new Point(1920, 1080)).
            setHandleSurfaceEvent(true).
            get();
    return RxCamera.open(this, config).flatMap(new Func1<RxCamera, Observable<RxCamera>>() {
        @Override
        public Observable<RxCamera> call(RxCamera rxCamera) {
            currentCamera = rxCamera;
            return rxCamera.bindTexture(view);
        }
    }).flatMap(new Func1<RxCamera, Observable<RxCamera>>() {
        @Override
        public Observable<RxCamera> call(RxCamera rxCamera) {
            return rxCamera.startPreview();
        }
    });
}

Ah, I see this is already addressed on master (reset() sets the listener).


bench doc

documentation markdown for benchmark

Great, thanks!
Btw, I thought there were way more files you were going to commit?


What about multi Aurelia apps under /src or a nested app e.g. /src/nested

Hey, I'm seeing a scenario that one could have a nested Aurelia app for example /src/nested/main.js along the main app /src/main.js. Regarding the webpack config, how would the entry config look like? So far, the most popular way of specifying an entry is simply like entry: { main: "aurelia-bootstrapper" }. In this nested app case, how would we define the entry for it? How we can instruct the plugin to use for example /src/nested/main as the app entry point?

The simplest solution is to use 2 separate webpack.config / compilations.
If you don't want to do that, there's some specific configuration steps you have to take,
I haven't tried myself but the following should work:

Make your entry points based on this model:

// main1.js
import "aurelia-polyfills"; // unless you don't need them
import "aurelia-loader-webpack";
import "aurelia-bootstrapper";

export function configure(aurelia) {...};

Avoid doing more than that in this file because manipulating Aurelia before it's initialized leads to problems.
Of course aurelia-app in your html starting points must be set accordingly.

Pass noWebpackLoader: false option to AureliaPlugin

This setup does not support Webpack DLL

If you use CommonsChunkPlugin to move shared code (like libs) in their own chunk, do not move aurelia-loader-webpack out of the entry chunks.  This one is special and it has to be in the Webpack entry chunk(s).

Thanks for the FLASH response, @jods4 rocks!
I tried and chose the two compilations approach. I kept the entry point for the nested app simply as: nested: "aurelia-bootstrapper", in the AureliaPlugin options, i give it an app name like nested/main, also in the app.html. The last trick seems to be that in the nested main.js, the setRoot call has to use the same nested/app as well.
Hope this helps for someone else with a similar use case.

Shall we close this issue then?

@jods4  Hmm so if I simply create 2 compilations in this case, there's no way to share common code between the those right? No way to use CommonsChunksPlugin and such things?
Because I think I will go with the 2 compilations solution for now, until I understand these things better.
Also are there any plans to add multiple entry points support like this to work with the plugin? As I understand it now, the plugin is designed for the use case where Aurelia is a "one page app", right?
I'm all new to webpack, aurelia and most of this so sorry if I'm asking obvious questions. Thank you

@netrounds-joakim You are correct, the plugin API is designed for single entry point (SPA) first.
With steps from that other comment, I see no reason why multiple entry points would not work, but it's hard to figure that out on your own without a deep understanding of how Aurelia+Webpack+the plugin work together.
If this is common enough, maybe I should think about adding simpler support for multiple entry points. (There's no plan right now, but why not?)
Using 2 compilations will be simpler at the moment, for sure. Because a Webpack config is just javascript you can easily extract the common part, then just change the entry point in each. That's really easy stuff with no code duplication.
Sharing common code is slightly harder. Using a webpack DLL can achieve that. You'll have 3 compilations then: the shared part (DLL) + each entry point.
The Webpack DLL plugin is something that Aurelia plugin does support, more info:
https://github.com/jods4/aurelia-webpack-build/wiki/Using-Webpack-DLL

@jods4 thank you for the quick reply :)

If this is common enough, maybe I should think about adding simpler support for multiple entry points. (There's no plan right now, but why not?)

You have on vote from me at least! And maybe @jack4it ?

Using 2 compilations will be simpler at the moment, for sure. Because a Webpack config is just javascript you can easily extract the common part, then just change the entry point in each. That's really easy stuff with no code duplication.

Ok yea I assumed something like that would be possible so then I know that plan of mine will work.

Sharing common code is slightly harder. Using a webpack DLL can achieve that. You'll have 3 compilations then: the shared part (DLL) + each entry point.

Ok thank you for that pointer. I had seen mentions of DLL but did not fully understand what they were for, but that makes sense.
Thanks!

Shortly, a Webpack "DLL" is a separate Webpack compilation unit that produces a re-usable bundle that other Webpack compilations can reference.
Without this, each Webpack compilation is totally autonomous and distinct.

Ok thanks for the clarification :)

@jods4 I would super love to be able to support multiple Aurelia apps from a single webpack config. I've spent probably more than a dozen hours trying to make it work (with the DLL plugin, of course), and can't seem to get anywhere.
I can't be the only person who needs multiple Aurelia apps in the same application. dotnet new Aurelia is a fantastic starting point, but it seems like developers who are coming from a more traditional ASP.NET development experience are going to be more comfortable having Aurelia within individual pages, at least in the beginning. For example, a customer area might be entirely different from an admin area.
That's one thing that makes Vue so enticing -- You include a reference to Vue.js in a page, and you're practically up and running.
Is there not some way of including multple AureliaPlugins and using various combinations of aureliaapp and entry? Or is it always going to add everything to the first aurelia-bootstrapper chunk?
You don't have to give a long winded reply... I've just spent a lot of time on this and I'd love to know that I'm not crazy.

@alexdresko Have your tried the steps in my first answer?
If you follow them you should be able to create a single webpack config with multiple entry points (one for each of your page).

@jods4 Well, no, because you said "This setup does not support Webpack DLL" and I've already got that in place and working great. If you think it'll work with DLL, I'll give it a try.
Thanks for replying. I don't feel alone in this anymore. :)

So you want multiple DLL compilations + multiple entry points in your main config?
Out of curiosity, what's your motivation for that setup?
Currently the code in AureliaPlugin would not support multiple entry points with DLLs.
Note that AureliaPlugin itself is only a (large) collage + configuration of many other smaller dedicated plugins. If you're hardcore you could redo that collage yourself with an appropriate configuration for multiple DLLs... I'm not advising you to, it's hard. 😅

@alexdresko I've reviewed the RC3 config and I believe it now could work with DLL (not in the DLL producing config of course but a multi-entry point Aurelia config should also work when consuming DLLs, provided you configure everything properly).
I have updated my answer above with some corrections if you want to try.

I have a DLL for Aurelia and a DLL for Bootstrap et al. That seems to work well with a single Aurelia entry point. It also works well for standard Razor pages that just need the latter DLL and their page-specific script.
Where I'm stuck is creating a second Aurelia entry point. I don't know enough about the plugin, but I'm fairly confident that the current version of the plugin is the source of my problems. I probably could reverse engineer the plugin, but then I might be missing out on future enhancements/fixes.
Also, I'm surprised I made it this far. I feel I'm living inside a very fragile house here.

Awesome! I'll give it a go in the next day or two! Is worth a try if you have at least some suspicion that it might work.

Let me know how it goes.

Hi @jods4  I folow your steps to cofigure two app with a single config file but it dosn´t work. When I set the noWebpackLoader: true I get this error No PLATFORM.Loader is defined and there is neither a System API (ES6) or a Require API (AMD) globally available to load your app.  throw by aurelia-bootstrapper.
In my entry file I set the imports but it cand not configure the Loader propertly because the loader must be configured before to load the entry point.

I experienced the same problem a few weeks ago when I tried the instructions but didn't say anything because I figured I was just following the instructions correctly. Thanks for validating my attempt. Was going to try again, but procrastination wins this round!

To be sure: did you use the prolog above in each of your entry point modules?
They should include import "aurelia-loader-webpack", see above.
Let me know if that helps or not.

@jods4 Tried again tonight. You can see my full attempt, including the steps I ran through here: https://github.com/alexdresko/multiautest
Everything was working fine until I attempted to follow the instructions (https://github.com/alexdresko/multiautest/commit/2de492b819a7ca62435f6e262f71efdc4acae537)
At the end of the steps I detailed, you can see the error message I'm getting. Not sure if that's because of how I configured the entry point in webpack.config.js.

Error: Unable to find module with ID: bootFirst
at WebpackLoader. (aurelia-loader-webpack.js:187)
at step (aurelia-loader-webpack.js:36)
at Object.next (aurelia-loader-webpack.js:17)
at aurelia-loader-webpack.js:11
at new Promise ()
at 55.__awaiter (aurelia-loader-webpack.js:7)
at WebpackLoader.55.WebpackLoader._import (aurelia-loader-webpack.js:152)
at WebpackLoader. (aurelia-loader-webpack.js:252)
at step (aurelia-loader-webpack.js:36)
at Object.next (aurelia-loader-webpack.js:17)

I tried to be as thorough as possible with my repro.
Note that the repro should be running against the latest version of everything.
@danielmeza Given @jods4 is a busy man, it might be helpful if you could take a look and see where I went wrong.

@alexdresko I believe Aurelia tries to load bootFirst when starting up because it's in the aurelia-app attribute here:
https://github.com/alexdresko/multiautest/blob/master/Views/Home/Index.cshtml#L5
And that's exactly what aureliaApp option in the Webpack plugin takes care of.
I have edited my checklist above to indicate how to adjust for that in a multi entrypoint situation.

@jods4 I've run out of time to work on this during my lunch break, but I did have some great success!  4a worked great. I updated the repo if anyone wants to see what I did, though I wouldn't exactly recommend it as a "best practices" example. Anyone who is truly curious what steps need to be taken should review the commit log, as I tried to use that as a way to document the process.
I'm even using the common chunks plugin in the example.
I do want to go back and do some analysis on the webpack output, though. It seems like the common.js is too big... it's practically as big as the vendor.js, which doesn't seem right.
4b didn't work for me.  I assume this is what you meant by the instructions

I presume that was the only change I needed to make since I was already calling setRoot... unless you wanted me to use a different module in set root?
With that change, I would always get this error:

And if I totally removed the aurelia-app attribtue from the html, the page would just sit at "loading..."

I really meant remove it completely. You can pass the DOM element into which Aurelia should inject to app to setRoot instead.

@jack4it @alexdresko  Hi guis, sorry for my delay, I'm to busy to. I will send my feedback this weekend, cause I  tried many configurations.

I am posting a working example of multiple entry points with webpack 4.
Warning: Custom changes are needed to html-webpack-plugin, as is in this PR.


Add a test to ensure #2712 doesn't regress

SQL^2 compiler test ensuring ordering by a projected flattened field doesn't use a synthetic sort key.
Should have been included in #2714, but I forgot. Thanks @alissapajer for pointing this out!

@alissapajer I also verified that this test fails on the commit prior to the merge of #2714.