[WIP][SPARK-27943][SQL] Add new feature create table could specify column with default constraint

What changes were proposed in this pull request?
Default constraint with column is ANSI standard.
Hive 3.0+ has supported default constraint ref:https://issues.apache.org/jira/browse/HIVE-18726
But Spark SQL implement this feature not yet.
This PR is related to https://github.com/apache/spark/pull/24372. If this PR finish, unselected target column can be inserted into the default value, while running insert into.
After this PR,  I will continue open other PR about default constraint, like alter table, desc table.
There exists some issue in this PR:
First, how to check a number specified by somebody compliance with the accuracy and scope of the data type, like float, double.
Second, some code looks not very elegant, I hope to improve it with your suggestions.
How was this patch tested?
UT

Can one of the admins verify this patch?

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/testing-k8s-prb-make-spark-distribution-unified/11399/
Test PASSed.

Test build #106146 has started for PR 24792 at commit 0dd717e.

Test build #106146 has finished for PR 24792 at commit 0dd717e.

This patch fails Scala style tests.
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/106146/
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/testing-k8s-prb-make-spark-distribution-unified/11400/
Test PASSed.

Test build #106147 has started for PR 24792 at commit 1c5ea5c.

Test build #106147 has finished for PR 24792 at commit 1c5ea5c.

This patch fails to build.
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/106147/
Test FAILed.

retest this please

Test build #106148 has started for PR 24792 at commit 1c5ea5c.

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/testing-k8s-prb-make-spark-distribution-unified/11401/
Test PASSed.

Test build #106148 has finished for PR 24792 at commit 1c5ea5c.

This patch fails to build.
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/106148/
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/testing-k8s-prb-make-spark-distribution-unified/11404/
Test PASSed.

Test build #106151 has started for PR 24792 at commit 1d9f701.

Test build #106151 has finished for PR 24792 at commit 1d9f701.

This patch fails to generate documentation.
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/106151/
Test FAILed.

Retest this please.

Test build #106153 has started for PR 24792 at commit 1d9f701.

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/testing-k8s-prb-make-spark-distribution-unified/11407/
Test PASSed.

Test build #106153 has finished for PR 24792 at commit 1d9f701.

This patch fails to generate documentation.
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/106153/
Test FAILed.

Test build #106156 has started for PR 24792 at commit a91bf42.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11409/
Test PASSed.

Test build #106156 has finished for PR 24792 at commit a91bf42.

This patch fails Spark unit tests.
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/106156/
Test FAILed.

Test build #106180 has started for PR 24792 at commit e7a387c.

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/testing-k8s-prb-make-spark-distribution-unified/11432/
Test PASSed.

Test build #106180 has finished for PR 24792 at commit e7a387c.

This patch fails Spark unit tests.
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/106180/
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/testing-k8s-prb-make-spark-distribution-unified/11436/
Test PASSed.

Test build #106185 has started for PR 24792 at commit 3a9aa1e.

Test build #106185 has finished for PR 24792 at commit 3a9aa1e.

This patch fails Spark unit tests.
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/106185/
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/testing-k8s-prb-make-spark-distribution-unified/11445/
Test PASSed.

Test build #106195 has started for PR 24792 at commit a203a8c.

Test build #106195 has finished for PR 24792 at commit a203a8c.

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/106195/
Test PASSed.

@gatorsmile Thanks for your review. As you said, this is not a small work. I created a parent jira SPARK-27943 and described the design simply. I created four sub jira used to each task. If I find other sub task, I will add new sub jira.

@wangyum Help me review this PR, thanks!

I don't feel confident enough to review changes to the SQL language support here

I don't feel confident enough to review changes to the SQL language support here

It doesn't matter, thanks.

@beliefer Before submitting PRs, could we first start it with a design doc? Ping me if the design doc is ready to review. Thanks!

@beliefer Before submitting PRs, could we first start it with a design doc? Ping me if the design doc is ready to review. Thanks!

@gatorsmile I get it. But I want what format is required to design the document? If the design doc is  ready, how I pass it to you?

@beliefer Before submitting PRs, could we first start it with a design doc? Ping me if the design doc is ready to review. Thanks!

@gatorsmile Thanks for your reply. The design doc is ready, how I pass it to you?

Test build #106401 has started for PR 24792 at commit a912b87.

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/testing-k8s-prb-make-spark-distribution-unified/11646/
Test PASSed.

Test build #106401 has finished for PR 24792 at commit a912b87.

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/106401/
Test PASSed.

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/testing-k8s-prb-make-spark-distribution-unified/11659/
Test PASSed.

Test build #106415 has started for PR 24792 at commit 9b600a3.

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/testing-k8s-prb-make-spark-distribution-unified/11660/
Test PASSed.

Test build #106416 has started for PR 24792 at commit 3bf06af.

Test build #106415 has finished for PR 24792 at commit 9b600a3.

This patch fails Spark unit tests.
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/106415/
Test FAILed.

Test build #106416 has finished for PR 24792 at commit 3bf06af.

This patch fails Spark unit tests.
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/106416/
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/testing-k8s-prb-make-spark-distribution-unified/11662/
Test PASSed.

Test build #106418 has started for PR 24792 at commit 545bba0.

Test build #106418 has finished for PR 24792 at commit 545bba0.

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/106418/
Test PASSed.

Hi, @beliefer . For the umbrella issue, the subtask JIRA ID is enough.

Hi, @beliefer . For the umbrella issue, the subtask JIRA ID is enough for the title.

OK. Thanks for your reminder.

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/testing-k8s-prb-make-spark-distribution-unified/11694/
Test PASSed.

Test build #106451 has started for PR 24792 at commit 9931eb6.

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/testing-k8s-prb-make-spark-distribution-unified/11695/
Test PASSed.

Test build #106452 has started for PR 24792 at commit 46c12d8.

Test build #106451 has finished for PR 24792 at commit 9931eb6.

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/106451/
Test PASSed.

Test build #106452 has finished for PR 24792 at commit 46c12d8.

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/106452/
Test PASSed.

@gatorsmile  The design doc of default constraint is ready.

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/15685/
Test PASSed.

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/18510/
Test PASSed.

Test build #113627 has started for PR 24792 at commit 48c8b1e.

Test build #113627 has finished for PR 24792 at commit 48c8b1e.

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/113627/
Test PASSed.

@gatorsmile The design doc of default constraint is ready.

what's the progress of this pr?  As https://issues.apache.org/jira/browse/SPARK-29119 also associate with this pr.
I think this will be a useful function for users to handle default value or computed columns;
@beliefer You can put your design doc on the Google Docs for more details and add comparisons with other engines, eg:

Oracle: https://docs.oracle.com/javadb/<IP_ADDRESS>/ref/rrefsqlj30540.html#rrefsqlj30540__sqlj64478
Postgres: https://issues.apache.org/jira/browse/SPARK-29119
Mysql: https://dev.mysql.com/doc/refman/5.6/en/constraints.html
Cockroach: https://www.cockroachlabs.com/docs/stable/default-value.html


Add barebones code for operator

This is not a working version of the operator yet, just the initial code to enable parallel development.
Some files under ./assets are outdated, please ignore.
CC @openshift/storage

/lgtm
/approve

/approve
(OWNERS file was added)


Write a mission statement for devrel

It's important for us to have a mission statement so we never spend time on things that doesn't help us achieve our goals. Keep in mind that, even if our job may positively impact the adoption of a paid service/product, devrel should never be tied to paid conversions or sales metrics.
Here is my first draft:

We help developers be successful by nurturing a healthy and open source community around MeiliSearch. This means listening, inspiring, educating and supporting our community by any means necessary.

Comment? Suggestion? Insult?

Mission accomplished... https://github.com/meilisearch/devrel/blob/main/README.md
See what I did there 🤣

Mission accomplished... https://github.com/meilisearch/devrel/blob/main/README.md
See what I did there 🤣


Review classification of protestware

@piergiorgioladisa and @serenaponta We already discussed several times how to classify the peacenotwar protestware. Right now, it is assigned to the node Develop malicious package from scratch, which in its current definition assumes that the attacker planned from the very beginning to misuse the package at some point in time for delivering malware. It somehow does not cover the case of a benign attacker turning malicious (for whatever reasons).
Looking at the attack tree, there are at least three ways to better reflect protestware:

Update existing attack vector Develop malicious package from scratch,
Update existing vector Bribe or blackmail legitimate user to something like Legit user is politicized, blackmailed or bribed (but that somehow mixes internal and external motivations), or
Create new attack vector Contribute as maintainer > Change ethos, which can be formulated in such a way that it covers both intrinsic and extrinsic motivations for somebody to change his attitude or ethos and misuse an existing legitimate package as malware (for expressing political opinions or other reasons).

What do you think?

@henrikplate among the three proposals, I would be more in favor of the third one. In particular:

I would leave the meaning of the AV Develop malicious package from scratch as it is, and I would not mix meanings since this would create more confusion than clarity IMHO
For the same reason as above, I would not put multiple AVs into one. So this why I prefer to rather add a sibling to Bribe or blackmail legitimate user so that it will be repeated below all the parents Inject Into Sources of Legitimate Package, ..Build etc.. and that would represent all viable options for a disgruntled maintainer

@serenaponta also prefers the 3rd option. Since we all agree, I will add this new attack vector later today.


Getting 404 when trying to download Chart.bundle.js

Getting 404 for the following URL:
https://raw.githubusercontent.com/chartjs/Chart.js/master/dist/Chart.bundle.js
Please take a look and advise

You can download it from here for now:
https://cdnjs.com/libraries/Chart.js

We have restructured the repository so that there is no longer a dist folder. Please access that code with a CDN or by downloading from the releases(https://github.com/chartjs/Chart.js/releases) page.

Closing as @zachpanz88 is correct

Someone ought to update the samples, which still reference "../dist/Chart.bundle.js"

@lseltzer the samples work as expected if you install via npm or bower or download a specific tagged release. It's only when cloning that they don't.

@lseltzer Adding on to @etimberg's response, if you clone the library you can run gulp build to generate the dist files.


Make packages publicly available

Current packages hub-toolbox and hub-toolbox-gcp-cloud-shell need to make public.

To confirm that both packages have been made public. 👍🏼


docs: Add --yes to npx commands

When setting up a new repo using these instructions, I was initially confused because the Tailwind css wasn't being updated when started with make live. Hitting Ctrl+C was also hanging due to the same wait.
Adding the --yes flag allowed the commands to proceed if installation was required. I didn't add any additional explanation, but happy to include some elaboration if preferred.

Thanks, you're right. The commands work OK if you already have a package.json and have run npm i, but not if you're starting from scratch, and that isn't clear in the docs.


Add global configuration for Klocwork tool

Won't do. At least for now. Customer who requested that got it implemented locally. No need for sharing


Groups/Permissions management section

Add a groups and permissions management page to the PMP plugin.  Includes:

[x] Ability to create/modify groups (list with docs?profile=group&writeable=true)
[x] Ability to add/remove users to groups you can write to
[x] Set the default group for new posts

Looks good to me.  Captured one bug (#47) and two enhancements (#46 #48) out of this.


Sync eng/common directory with azure-sdk-tools for PR 2352

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/2352  See eng/common workflow

/azp run python - core - ci


fontWeight applied with className props won't work for specific values

Describe the bug
When passing custom className to a react CVA component, some classNames won't take precedency against variants values.
To Reproduce
Steps to reproduce the behavior:

Create a react component using CVA;
Receive custom className as props;
Pass a valid tailwind-css prop that should override some tailwind-css class being used with base cva function, in this case the prop being passed is font-bold, that should translate to font-weight: 700. But the font-semibold of the base component won't be override.
See error

Expected behavior
The final css should be font-weight: 700
Screenshots
CVA setup

Component being instantiated and the font-bold props being passed;

CSS that wont work

When passing other props, it works

Desktop (please complete the following information):

OS: Mac OS Ventura 13.1
Browser Arc Browser
Version Arc 0.100, Chromium 112.0.5615.137

Smartphone (please complete the following information):

Device: iPhone 13 pro max
OS: iOS 16.4.1
Browser safari
Version latest

Check out https://cva.style/docs/installation#handling-style-conflicts 😊


Consolidate and improve the code quality linters

This PR expands the use of code quality linters to include checking Dockerfiles and GitHub Actions. I've also updated the Contribution Guide to include not only documentation about the linters, but also to fix some broken formatting and to update a few of the golden rules to be more current.
I've also added scripts/lint which is designed to be run locally by a developer to check their changes pass all the linter rules before opening a PR. It uses a container to run, and the script checks for both docker and podman so it should run on most operating systems.
Signed-off-by: Avi Miller<EMAIL_ADDRESS>

@AmedeeBulle @gvenzl @mriccell @rjeberhard any chance of a review of this, please?


Add support for async predictors

Rebase of #1752 and #1512

Closing this for now, until it has an owner to pull it over the line.


model training process setup

Hi , thanks for your great job! I have done all the work mentioned in readme. I also start to train the model, however, the car moves very slowly in rviz and gazebo , and does not run smoothly as in the example ,even needs to wait a minute before changing positon. Is this because of my computer's poor performance?

my computer and environment as follows:

cpu : 13700k i7
no NVIDIA Graphics Card
Windows WSL2 & Ubuntu20.04  ROS noetic

the following two pictures are 1 minute apart

the terminal belike 👇

Hi,
I have deployed this model on i5 and i3 cpus without cuda so the training part where episode is collected is not that resource intensive. If it takes a minute to change a single (or even a couple) step it does not seem normal to me. However, it does seem you are using a virtual machine, and it either might not have enough resources or not configured correctly. So I would suggest checking if any other ros application works there, and if it does not run smoothly, you could know where the problem lies. In any case, this seems more of a hardware issue and I don't think I can help you much there.

Thank you for your reply. Does that situation mean running the program successfully? I want to debug this program to learn the connection between DRL and ROS&gazebo simulation, and then I could work on my own project.

From what I can see, the software is launched properly.

Hi there, I want to know how to judge whether the trained model is convergent? This is my first contact with RL training. So  what metrics that I need to check? loss curve like DL model? or reward value reaches a stable value?
The following is my terminal information during the training .
-- training start

-- epoch increase

I find that with the increase of epoch, its average rewards becomes negative . Looking forward to your reply.

Hi,
Better indicator would be curves in tensorboard. Evaluation in the beginning in your case probably places the goals really close to the robot so it randomly "collects" them. As training goes on, the goal distance gets increased and situations become more complex to the robot.
Loss is not a good indicator and you can see more on the topic here:
https://github.com/reiniscimurs/DRL-robot-navigation/issues/89#issuecomment-1837966443
Generally I would look for the convergence of the maxQ reward on tensorboard.

Many thanks for your kind help and share.


Educator verification

Step 2 seems out of place on the following page -
https://github.com/Microsoft/pxt/blob/master/docs/github-teacher-verification.md
Can we confirm these steps to ensure they are getting this screen?

Galen, it looks like GitHub changed their account sign-up flow - can you remove Step 2 from this page?  https://makecode.com/github-teacher-verification


Feature request: reflect referenced members of a ByteAddressBuffer

Given the following HLSL shader:
typedef uint Texture2DIndex_t;

struct MaterialData_t
{
	float4 g_vTest;
	float2 g_vTest2;
	float3 g_vTest3;
	Texture2DIndex_t g_tTexture1;
	Texture2DIndex_t g_tTexture2;
	bool g_bTest1;
	bool g_bTest2;
};

static MaterialData_t _g_MaterialData;

ByteAddressBuffer g_MaterialData : register ( t4 , space1 )  ;

struct Payload_t
{
	float2 vTest;
	bool bTest;
	Texture2DIndex_t tTest;

};

struct PayloadShadow_t
{
	float m_flVisibility;
};

[ shader ( "closesthit" ) ]
void ClosestHit0 ( inout Payload_t payload , in BuiltInTriangleIntersectionAttributes attrs )
{
	_g_MaterialData = g_MaterialData.Load<MaterialData_t>( InstanceIndex() );

    payload.vTest = _g_MaterialData.g_vTest2;
	payload.bTest = _g_MaterialData.g_bTest1;
	payload.tTest = _g_MaterialData.g_tTexture1;

}

[ shader ( "anyhit" ) ]
void AnyHit1 ( inout PayloadShadow_t payload , in BuiltInTriangleIntersectionAttributes attrs )
{
	_g_MaterialData = g_MaterialData.Load<MaterialData_t>( InstanceIndex() );

    {
        payload . m_flVisibility = 0.0 ;
        AcceptHitAndEndSearch ( ) ;
    }
}

I would like to be able to use spirv-reflect to determine which members of g_MaterialData are statically referenced (the same as I would want to do for a cbuffer).  Currently that is not possible.
This shader can be lowered to spir-v using slang with:
slangc.exe byte_address_buffer_reflection.hlsl -o byte_address_buffer_reflection_slang.spv -profile lib_6_4 -entry ClosestHit0

Or with DXC:
dxc.exe -spirv -T lib_6_4 byte_address_buffer_reflection.hlsl -fspv-target-env=vulkan1.2 -Fo byte_address_buffer_reflection_dxc.spv

I've attached the HLSL and slang and dxc-generated SPIR-V to the bug.  Ideally spirv-reflect would work with shaders from either backend (DXC or slang).
byte_address_buffer_reflection.zip

So looking into this a few things

I have noticed the only way I can ever tell this is the ByteAddressBuffer is because it is both an Input variable and the only thing with OpDecorate BuiltIn InstanceId ... I am not sure if this, along side the fact it is Ray Tracing stages, is enough to always know we should "start looking" for this

The most information we are going to be able to get you is the offset into the struct that were accessed, from there you will need to map that to the original struct

Where things get strange is the values I get for slang are [4, 5, 9, 11] but I get [4, 5, 11, 13] for dxc

the slang offsets makes sense
float4      g_vTest;     [0-3]
float2      g_vTest2;    [4-5] // accessed
float3      g_vTest3;    [6-8]
uint        g_tTexture1; [9]   // accessed
uint        g_tTexture2; [10]
bool        g_bTest1;    [11]  // accessed
bool        g_bTest2;    [12]

but for dxc I was only able to figure out there was some implicit padding from looking at the early IR (byte_address_hlsl_passes.txt)
... I don't know how to determine why it decided on adding the 2 bytes of padding here
float4      g_vTest;     [0-3]
float2      g_vTest2;    [4-5]  // accessed
       PAD               [6-7]
float3      g_vTest3;    [8-10]
uint        g_tTexture1; [11]   // accessed
uint        g_tTexture2; [12]
bool        g_bTest1;    [13]   // accessed
bool        g_bTest2;    [14]

Providing the offsets would be sufficient.  The reason for the buffer offset differences is that I think by default DXC is using scalar block layout and slang is using std430.  So it is correct that the offsets would be different.  We have some compile option to use std430 layout for SSBOs on DXC so don't worry about those differences, it means it is doing the right thing.  If you can report back the offset information I think I can work it out from there.  Thanks!!

@danginsburg do you find the use of ByteAdressBuffer is only used with Ray Tracing stages or you feel this is something you would want for all stages?

@danginsburg do you find the use of ByteAdressBuffer is only used with Ray Tracing stages or you feel this is something you would want for all stages?

The current need is for Ray Tracing stages, but ultimately it would be nice if it worked in all stages.

prototype https://github.com/KhronosGroup/SPIRV-Reflect/pull/236
ok so spending more time into this, I realize the way slang does this is breaking all my assumption I had before from the DXC output
slang breaks the struct up into 3 variables (float only, uint only, and bool only) so you end up with 3 variables
the other issue is if there are ever 2 ByteAdresssBuffer in a shader, you won't have a good way (outside of hoping OpName is there) to match up which OpVariable points to which ByteAdresssBuffer
I will look into what it would take to add Non-semantic decorations we could put on the ByteAddressBuffer (maybe something we can add ontop of NonSemantic.Shader.DebugInfo)

the other issue is if there are ever 2 ByteAdresssBuffer in a shader, you won't have a good way (outside of hoping OpName is there) to match up which OpVariable points to which ByteAdresssBuffer

If the client side code knows what the corresponding binding / register are up to, it should be sufficient. If the use case is full reflection where the client code is building out descriptor set layouts, then you are correct - the information that SPIRV-Reflect provides will be underconstrained.

The issue is even if the client knows which binding/register, spirv-reflect will still have to attempt to find this information for every OpAccessChain which is very invasive, if it is known which variable is the ByteAddressBuffer it makes things  more simpler and robust
@chaoticbob mentioned to me how some non-semantic info is optimized out (and experienced similar issue and hence why SPV_GOOGLE_user_type was created), but looking more, the SPV_KHR_non_semantic_info also doesn't get optimized away
the biggest issue I am finding and I am not sure how to make sure this info can be set down with both the DXC and slang front-end path

DXC already writes out the decorations for SPV_GOOGLE_user_type when -fspv-reflect is used. See below.
I would favor the SPV_GOOGLE_user_type approach for type decoration since that's what it was intended for.
Example shader:
ByteAddressBuffer   InData  : register(t0);
RWByteAddressBuffer OutData : register(u0);

[numthreads(1, 1, 1)]
void csmain(uint3 tid : SV_DispatchThreadID)
{
	OutData.Store(tid.x, InData.Load(tid.x));
}

Output:
$ dxc -spirv -fspv-reflect -T cs_6_0 -E csmain user_type.hlsl
; SPIR-V
; Version: 1.0
; Generator: Google spiregg; 0
; Bound: 25
; Schema: 0
               OpCapability Shader
               OpExtension "SPV_GOOGLE_hlsl_functionality1"
               OpExtension "SPV_GOOGLE_user_type"
               OpMemoryModel Logical GLSL450
               OpEntryPoint GLCompute %csmain "csmain" %gl_GlobalInvocationID
               OpExecutionMode %csmain LocalSize 1 1 1
               OpSource HLSL 600
               OpName %type_ByteAddressBuffer "type.ByteAddressBuffer"
               OpName %InData "InData"
               OpName %type_RWByteAddressBuffer "type.RWByteAddressBuffer"
               OpName %OutData "OutData"
               OpName %csmain "csmain"
               OpDecorate %gl_GlobalInvocationID BuiltIn GlobalInvocationId
               OpDecorateString %gl_GlobalInvocationID UserSemantic "SV_DispatchThreadID"
               OpDecorate %InData DescriptorSet 0
               OpDecorate %InData Binding 0
               OpDecorate %OutData DescriptorSet 0
               OpDecorate %OutData Binding 0
               OpDecorate %_runtimearr_uint ArrayStride 4
               OpMemberDecorate %type_ByteAddressBuffer 0 Offset 0
               OpMemberDecorate %type_ByteAddressBuffer 0 NonWritable

               OpDecorate %type_ByteAddressBuffer BufferBlock
               OpDecorateString %InData UserTypeGOOGLE "byteaddressbuffer"
               OpMemberDecorate %type_RWByteAddressBuffer 0 Offset 0
               OpDecorate %type_RWByteAddressBuffer BufferBlock
               OpDecorateString %OutData UserTypeGOOGLE "rwbyteaddressbuffer"

       %uint = OpTypeInt 32 0
     %uint_2 = OpConstant %uint 2
     %uint_0 = OpConstant %uint 0
%_runtimearr_uint = OpTypeRuntimeArray %uint
%type_ByteAddressBuffer = OpTypeStruct %_runtimearr_uint
%_ptr_Uniform_type_ByteAddressBuffer = OpTypePointer Uniform %type_ByteAddressBuffer
%type_RWByteAddressBuffer = OpTypeStruct %_runtimearr_uint
%_ptr_Uniform_type_RWByteAddressBuffer = OpTypePointer Uniform %type_RWByteAddressBuffer
     %v3uint = OpTypeVector %uint 3
%_ptr_Input_v3uint = OpTypePointer Input %v3uint
       %void = OpTypeVoid
         %16 = OpTypeFunction %void
%_ptr_Uniform_uint = OpTypePointer Uniform %uint
     %InData = OpVariable %_ptr_Uniform_type_ByteAddressBuffer Uniform
    %OutData = OpVariable %_ptr_Uniform_type_RWByteAddressBuffer Uniform
%gl_GlobalInvocationID = OpVariable %_ptr_Input_v3uint Input
     %csmain = OpFunction %void None %16
         %18 = OpLabel
         %19 = OpLoad %v3uint %gl_GlobalInvocationID
         %20 = OpCompositeExtract %uint %19 0
         %21 = OpShiftRightLogical %uint %20 %uint_2
         %22 = OpAccessChain %_ptr_Uniform_uint %InData %uint_0 %21
         %23 = OpLoad %uint %22
         %24 = OpAccessChain %_ptr_Uniform_uint %OutData %uint_0 %21
               OpStore %24 %23
               OpReturn
               OpFunctionEnd


[WIP] Open API Docs #2

Description
Reworking of URLs and REST Docs
This PR fixes #3047 fixes #3044 fixes #3046

@navendu-pottekkat Could you check the server.go file here, I replaced too many routes from the Endpoint excel sheet, I think I should revoke those changes, so need your feedback on which ones I should.
plus Should I replace the rest of the urls in whole project(I mean in mesheryctl commands too)?

It is always best to handle 1 item in a PR unless there is a strong reason to do otherwise.
All the changes in the routes should be accompanied by changes in the clients, the UI and mesheryctl.
This PR is difficult to review and merge as there are multiple things being handled here. The swagger update should be a PR and each of the endpoints changes should be in separate PR.
There is a reason why we split the reworking of API endpoints into separate issues. And it was done so because for each set of APIs, it would require changes to both server and client and that would make it easy to test and merge.
So, please consider these changes and modify the PR.

I revoked most of the changes, and now on I'll cover this slowly slowly as each commit contains hundreds of lines of changes.

@kumarabd can you provide guidance on ensuring we're sourcing from https://github.com/layer5io/service-mesh-performance protos?

@leecalcote @kumarabd Can we merge this?

@kumarabd will you give this a final review?


fix config builder erroring when passed partial config

when you pass create a builder with a partial config, then there might be some required fields left empty and methods will fail because of this.
const builder = new ConfigBuilder({ publish: { allow_offline: true } })
builder.addUplink(/* ....*/) // <= This will fail. Since we're passing in a config, it is assign to `this.config` and it doesn't have this.config.uplinks yet.

Thanks @ItamarGronich I took the liberty to add more stuff :) but good catch your patch It will arrive on 5.x, 6.x and next soon.

Thanks @juanpicado appreciate the help.
Howver, now that i think of it i think the tests you added don't cover the edge case that i've run into.
I'll add a test.


TypeError: L(...).finish is not a function

Hello.
As I mentioned before, this is a great project, but now I bumped into an error that I cannot sort out after quite a few attempts.
TypeError: L(...).finish is not a function   jquery.crellyslider.min.js:11:14965
f()             jquery.crellyslider.min.js:11
r()             jquery.crellyslider.min.js:11
i/</e<()    jquery.crellyslider.min.js:11
I mention the website runs WP and jquery v1.8.3 (loaded by the theme)
I hope you have an idea about what is going on...

I'm sorry if I answer so late, I was abroad last week. Are there any other javascript errors in the console?

I have the same error on a website and it work on another web site.

Probably you jQuery version is very old. I would suggest to update it and finish() will work

I can't update, it break other client site script. but the stop worked for me.


as.environment() statements moved outside of iterations

moved the calls to as.environment outside of lapply/for iterations

Thanks.


https://github.com/google/material-design-lite/tree/mdl-1.x

@hinoryu What's the issue, Can You Provide a description?


upgrade(installer): Add docker reload stderr to error

What does this PR do?
When this fails we only have "exit code 1" and no other debug, this PR adds the stderr to the trace & error message.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


[BugFix][cherry-pick][branch-2.5] Set ColocateGroupSchema bucketNum to the calculated num (#27086)

The main branch pull request is #27086

[FE PR Coverage Check]
:disappointed: fail : 2 / 4 (50.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/ColocateTableIndex.java
2
4
50.00%
[174, 175]


Feature Case for exunit

We should include a feature exunit test type. Having a custom type will allow us to capture more information and use that information to create better screenshot names and capture screenshots on assertion failures.

@keathley,
Last night I took a stab at implementing this, but I think I may need some guidance.
Some problems I ran into:

Calling Ecto and Phoenix functions in the test case
How to know the name of the user's project (e.g., translate MyApp.Repo into .Repo>

I think I understand what information would be captureable to to enhance screenshots, but I'm curious what other info you had in mind.
Regarding 1), we could forgo the phoenix and ecto bits, which would at minimum stop the user from always needing to create an exunit case themself, but would still require it if they wanted the ecto sandboxing stuff.
Thanks

@mhanberg Can you open up a draft PR for this? I can try to take a look at the code and see what's going on. I'm not sure why a custom case would break our ability to call phoenix and ecto functions.


callback on still activity

Is it possible to have a callback when a still activity is detected?
It would be very usefull as the plugin does it very well and there would be no need in another plugin.

COULD NOT INSTALL THE PLUG-IN Telerik SHOW ME TO INSTALL ERROR

Mauron85, any feedback on this question?

will be added in the next version

will be added in the next version
Thank you!

Notice: this issue has been closed because it has been reported for branch 2.x or later. It could be already fixed in v3 or is not relevant anymore. You may reopen this issue if it has been closed in error.


docs: fix documentation site showing 404 error

Fix documentation site so it can actually load the github repo's README in production as intended
Fix watch-docs gulp task to make sure it runs once initially

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ SceneTime has degraded performance

In add6a05, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2745 ms

Resolved: SceneTime performance has improved in 7e10f7b after 7 minutes.


Correction to image tag - appsody-quarkus:latest

Correction to image tag - appsody-quarkus:latest; not default:latest
For "appsody build" command on "quarkus" stack, the image is tagged as "appsody-quarkus:latest"
...
...
[Docker] Successfully tagged appsody-quarkus:latest
...
...
Running "docker run...." command for "default:latest" yields
"Unable to find image 'default:latest' locally
docker: Error response from daemon: pull access denied for default, repository does not exist or may require 'docker login': denied: requested access to the resource is denied." `
Hence, creating PR to update GitHub documentation from "default:latest" to appsody-quarkus:latest
Checklist:

[ ] Read the Code of Conduct and Contributing Guidelines.

[ ] Followed the commit message guidelines.

[ ] Stack adheres to Appsody stack structure.

Modifying an existing stack:

[ ] Updated the stack version in stack.yaml

Contributing a new stack:

Describe how application dependencies are managed:

Explain how Appsody file watcher is utilized:

Describe other Appsody environment variables defined by the stack image:

Describe any limitations and known issues:

Related Issues:

 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.

Thank you for raising this PR! The appsody build command tags the image with the name of the project directory. So in this case, the image name would actually be my-project:latest

Thanks. Should I resubmit the PR after making the above change?

https://stackoverflow.com/questions/58614083/docker-run-i-rm-p-80808080-defaultlatest-fails-for-appsody-quarkus-stack


Make SetIfDifferent no longer check if a key is mutable.

This would cause issues when updating an installation. By forcing removal of a key using an operation, we no longer check for children who override IsMutableForKey.
Fixes #40, and probably several others.
cc @grantland @hallucinogen

PR updated.

Perfecto


Feature/61 adding/editing wallets transactions

Seems like UI for datepicker is broken, it looks differently on angular material page:


WIP: Fix the shape displacement for periodic meshes

Previously, the shape displacement grid function was H1 even if the underlying mesh was periodic, and therefore had an L2 nodal grid function. This ensures consistency between the two fields.

After thinking about this, the shape fields should be in H1 even for periodic meshes. I'm closing this for now.


let output format customizable

It works like this.  CC #67.
Welcome to evcxr. For help, type :help
>> :help
:vars             List bound variables and their types
:opt [level]      Toggle/set optimization level
:fmt [format]     Set output formatter (default: {:?}).
:explain          Print explanation of last error
:clear            Clear all state, keeping compilation cache
:dep              Add dependency. e.g. :dep regex = "1.0"
:sccache [0|1]    Set whether to use sccache.
:version          Print Evcxr version
:preserve_vars_on_panic [0|1]  Try to keep vars on panic

Mostly for development / debugging purposes:
:last_compile_dir Print the directory in which we last compiled
:timing           Toggle printing of how long evaluations take
:last_error_json  Print the last compilation error as JSON (for debugging)
:time_passes      Toggle printing of rustc pass times (requires nightly)
:internal_debug   Toggle various internal debugging code

>> #[derive(Debug, Clone, Default)] struct Foo { bar: i32 }
>> Foo::default()
Foo { bar: 0 }
>> :fmt {:#?}
Output foramt: {:#?}

>> Foo::default()
Foo {
    bar: 0,
}
>> :fmt {}
Output foramt: {}

>> Foo::default()
   ^^^^^^^^^^^^^^ `Foo` cannot be formatted with the default formatter
`Foo` doesn't implement `std::fmt::Display`
help: the trait `std::fmt::Display` is not implemented for `Foo`
>> 1
1
>> "hogehoge"
hogehoge
>> :fmt 0x{:x}
Output foramt: 0x{:x}

>> 32
0x20
>>

@googlebot I signed it!

I'm not sure how useful it is to do this in this format. In #67 I suggested there be a list of fallbacks, so that setting the format to {:x} wouldn't mean that only things that impl std::fmt::LowerHex could be used... Unless I'm mistaken that's a drawback of the current setup.
That said, I guess as-is it could still be useful for e.g. setting the default to {:#?} or something

Thanks. Being able to use {:#?} seems like a good use-case for this change. Happy to merge this. Will wait a bit to give you a change to fix the typo that @bjorn3 noticed. Also happy to just merge and then I can follow up with a fix for the typo.


Project broken following upgrade from 4.0.3 - "Parser Error: Identifier not found: (x)" error on all child classes from a global script class

Godot version
4.1 Stable
System information
Linux Mint 21.1 - Godot 4.1 Stable - Vulkan (Forward+) - i7-12700K - RTX 2060
Issue description
Hi folks!
My project worked back on Godot 4.0.3 but since upgrading to 4.1 the project instantly crashes when testing, with the parser reporting that it was unable to find pretty much all inherited members with the following error:
Parser Error: Identifier not found: [variable name here]
My characters are currently made up of three classes, starting with Actor_Base inheriting from CharacterBody3D, then two child classes named Actor_Simple and Actor_Player_NPC inheriting from Actor_Base, which can be found in the project’s Scripts/Actors folder.
To explain the problem, two members inherited from Actor_Base that first manifested this problem in my child classes after upgrading were “ActorActive” and “ActorAlive”, both of which appear to be correctly recognised as inherited members from Actor_Base in child scripts by the editor’s script parser, but no longer seem to be detected as inherited members by the in-game script parser, instantly causing a crash.
Commenting out each now-offending variable call revealed it appears to have a problem with pretty much every member inherited from my custom parent class. Putting “self.” at the start of each call appeared to work around the issue, but this meant that another script/node that instances these actors broke as it was unable to access and set the inherited “ActorDefinition” resource member.
As even the editor’s script parser can’t find any issues with these scripts, I am at a loss for what’s happened here.
Unfortunately as I can’t guarantee that I can reproduce the same symptoms for the same reasons on a minimal project, I have included the entire project as the Minimal Reproduction Project.
To reiterate, the project worked just fine back on 4.0.3, but has completely broken since the upgrade, with this issue backporting to 4.0.3 and thus leaving me stranded. I have also tried to start a new project and copy the original files in, which produced the same results.
Any help is greatly appreciated!
-CFR
Steps to reproduce
Run test on included project
Minimal reproduction project
TPAction_Broken_GH.zip

I can reproduce the issue with that project in 4.0.3.stable and 4.1.stable. It's pretty weird indeed.
Clearing the .github folder to force recreating the .godot/global_script_class_cache.cfg doesn't seem to fix it.

As mentioned by @anvilfolk on Rocket.chat, this might be the same issue as #78146.

I believe we can confirm this as a duplicate of #78146 since #79205 also fixes it :)


typescript definitions

In v3.3.10 typescript definitions were added to Systemic. This PR is intended to also add definitions the Systemic Azure bus component.

@teunmooij - this library came along after I left guidesmiths. The key ones I still have an interest in are rascal, systemic (plus runners + early components such as systemic-express, systemic-pg, systemic-redis and systemic-mongodb), confabulous (plus loaders), marv (plus drivers), whoosh, groundhog-day, outstanding, adbock-plus-crx, block-sequence (plus drivers), mr.robot, request-token, prepper & stashback.


Remove almost empty line at top of editor which contains redundant information of file name

This is related to the breadcrumb feature.
users can remove it from preferences


Add list of scripts with descriptions and links to the contrib readme

Quick pass at making useful summary of scripts for the contrib directory readme. Used the Discord #euro-pi scripts channel by @roryjamesallen for most of the content. I also added new scripts in the directory along with descriptions based on their documentation .md files. Also added links to the documentation and script.
Eventually this should be generated programatically, but I don't have those skills yet and wanted to get something out here to test formatting.

One more thing I think would be great to include attribution to the original script author and any contributors of bug fixes/improvements to those scripts. You should be able to find that in the header or md file associated with each script.
Another factor to consider is how we want to approach maintaining this list. Is this intended to be comprehensive of all scripts or a "glimpse into some of the interesting scripts available". Personally, I'm leaning to the latter and in favor of omitting some of the smaller, more PoC scripts like CoinToss, HelloWorld, Diagnostics and Scope.
We did mention the idea automating the generation of a list of scripts, but I think having a manual curation of scripts is an excellent first step. Thanks for putting this together!

Thanks for the feedback!
My thought with getting this list together was so that users wouldn't have to click through each of the .md files to figure out what a script did. For that use case I think it's useful to have the proof of concept scripts in there (esp since they show up in the menu.py).
On the other hand, it does clutter up the list, and maybe they should be relegated to a different area at the bottom of the page (I'm embarrassingly unfamiliar with markdown, so I'm not sure if there's a way to show/hide content). I'll look into that.
I'll work on adding attribution for the scripts. I had also considered adding the self-reported categories, but didn't want to clutter it up too much. I'll see what I can do.

Finished adding contributors and labels to each entry. Also moved the utility/example scripts to a collapsible section at the bottom.
For contributors, I listed all listed contributors to the .py or .md file, in order of contribution.
For labels, I used the self-reported labels with no changes. Eventually we should probably normalize the labels.
I think the automatic generation of this kind of list is a great end goal, and will require some consistent formatting in the script documentation files. Another possible final state could be a mobile-friendly html page that will allow people to search for, review, select, and get instructions for the scripts.

This looks great, it's a much nicer way of looking at all the scripts than the Discord channel (to be honest I think I will delete the channel once this is merged as it is much less reliable when it comes to version control, whereas this can be lumped with the release steps.
Having a separate section for proof of concept scripts is really neat, and it pushes the interesting ones to the top which is what we want for first time viewers!
LGMT, unless anyone else has comments or changes I'm happy to merge now!

One last comment - I like how the script authors have been added, but I'm having second thoughts about the additional "contributors". I feel like the script author should receive the majority of attribution and listing the additional contributors feels like its taking away from that.
Would you mind removing the contributors and only listing the author for each script?
With that change, LGTM! Thanks for adding this!


Attempt at modularising/improving code legibility

Closes #41 , #34

I've just ran pre-commit to make the review easier. See https://pre-commit.com/#automatically-enabling-pre-commit-on-repositories to enable it always

I've added a new CI for pre-commit, would be good if this could pass it before merging (but that is easier than it sounds) https://github.com/brainglobe/cellfinder-napari/pull/58

Codecov Report

Merging #54 (2c7235e) into main (5d4218c) will decrease coverage by 0.20%.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##            main     #54      +/-   ##
========================================
- Coverage   1.37%   1.16%   -0.21%
========================================
  Files          7       8       +1
  Lines        363     428      +65
========================================
  Hits           5       5
- Misses       358     423      +65

Impacted Files
Coverage Δ

cellfinder_napari/curation.py
0.00% <0.00%> (ø)

cellfinder_napari/detect.py
0.00% <0.00%> (ø)

cellfinder_napari/detect_utils.py
0.00% <0.00%> (ø)

cellfinder_napari/plugins.py
0.00% <0.00%> (ø)

cellfinder_napari/train.py
0.00% <ø> (ø)

cellfinder_napari/utils.py
0.00% <0.00%> (ø)

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 5d4218c...2c7235e. Read the comment docs.

FYI I've disabled the sonar cloud summary bot in a bid to reduce the amount of spam from PRs in this repo.

FYI I've disabled the sonar cloud summary bot in a bid to reduce the amount of spam from PRs in this repo.

thank you! 😆


ngx-monaco-editor inputs and outputs not typed

The inputs and outputs for the ngx-monaco-editor component are not typed
@Input('options')
set options(options: any) {
...
@Output() onInit = new EventEmitter<any>();

The output appears to be an monaco.editor.IStandaloneCodeEditor and the input looks to be some kind of custom interface.
Would it be possible to type these and export the types so that I can add some type safety to my app (rather than using any)

Same problem for me.
Had to use skipLibCheck on tsconfig.json to make it work.

Types would be very helpful to understand what can be used here.


Update oss-fuzz CI workflow

Previously ci-fuzz was triggered on almost any changes to the tree, but
the signal to noise ratio did not make it helpful for most developers.
It also takes longer than 15m to run, which is our goal for smoke tests.
So it's been disabled for a while. However, this has allowed breakage to
be introduced into the tree.
Reduce the filter for pull requests to only run on changes to the fuzz
tests themselves. While this won't catch all regressions, it will at
least allow developers to make changes to the fuzzers and validate that
the new changes may build and not detect new issues.
In order to make these results more accessible, run them once a week and
allow developers to manually trigger the workflow through the GitHub UI.
This PR also fixes the fuzzer build after a breakage in https://github.com/cilium/cilium/pull/36056 .

/test


How to start contributing

Great work
Great work! This is what I have been looking for a long time.

Vim like Modal editing
VSCode like UI, Extension System, LSP
Fast (No Chromium)

Want to contribute
I am developer new to rust. I would really like to contribute to both development and documentation. Please someone give me contribution guideline. I would like to know the prerequisites.

I'm an engineer with zero knowledge of Rust language. I'm comfortable in others. So I may not be able to immediately help as a dev but I'd like to contribute to the docs or QA. please let me know if there's something I can contribute

Some codebase specific docs would be great - but if you're getting started with Rust my first recommendation is reading The Book. It's free, and the best source of learning the fundamentals :)
After that point you can find more specialized textbooks. My favourite has been "Microservices In Rust", "Functional Programming in Rust", and "Zero to Production in Rust"/
Best of luck!

https://github.com/lapce/lapce/blob/master/CONTRIBUTING.md Added now.
Please let me know if it's missing anything.


create react app windows

Is this a bug report?
(write your answer here)

Did you try recovering your dependencies?

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

(paste the output of the command here)
Steps to Reproduce

(Write your steps here:)

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Please add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

It looks like this was opened mistakenly. If you are having a problem please open a new issue and fill out the issue template.


Fetch single event

(Note for later : this handle the organizer when fetching a single event from Google).
Thanks @rgazelot


Add preflight package (#149)

Preflight package implements should implement
all preflight functionality per one Module.
Current commit will only implement image verification: image presence and correct kernel version
MGMT-11438

Upstream PR for cherry-pick:
https://github.com/kubernetes-sigs/kernel-module-management/commit/0e84a4e812a4e2fca0e80a18168207c1660277c5

/lgtm


Use out deprecated template_file terraform API

Hey folks,
I'm seeing a crash on OSX due to the use of an old API, see: https://github.com/hashicorp/terraform-provider-template/issues/85
This is unlikely to cause big issues for customers today, but might in the future. It would be good to migrate to the new/preferred API

Hello Robert,
Thank you very much for the report!
Please let me fix it.
Thank you!


[1.8.9] Invulnerability ticks data has surprising behaviour.

Tested on SpongeForge : d3c31faa86dad12fd69cf494d0a3974ade985a4e
Setting Invulnerability ticks to Integer.max lets people 1 hit entities, rather then blocking the damage.
Either I'm missing some data that needs setting, or the processor for Invulnerability ticks should probably set whatever needs setting to prevent damage from occuring.

Does this occur in 1.10.2?


Make dynamic option platform

Issue Type

[ ] Bug Report
[x] Feature Request
[ ] Other

Please make folder dynamic here: https://github.com/nwutils/nw-builder/blob/7ca5a28f40078ab179aab72cf0f3260ef5f118f2/src/bld.js#L138C1-L150C6
From:
for (let file of files) {
    await fs.promises.cp(
      file,
      path.resolve(
        outDir,
        platform !== 'osx'
          ? 'package.nw'
          : 'nwjs.app/Contents/Resources/app.nw',
        file,
      ),
      { recursive: true, verbatimSymlinks: true },
    );
  }

To:
  // filesFolder - is option for build type options
  for (let file of files) {
     await fs.promises.cp(
       file,
       path.resolve(
         outDir,
         filesFolder,
         file,
       ),
       { recursive: true, verbatimSymlinks: true },
     );
   }

If you don't place the files in the correct directory, NW.js is unable to read them. Could you explain how the fileFolder option will be used?

Closing until more feedback/clarification can be given


Code quality

PR description
Fixed Issue(s)

Changelog

[ ] I thought about the changelog and included a changelog update if required.

Codecov Report

Merging #812 (4845e45) into main (2002aa2) will decrease coverage by 5.05%.
The diff coverage is n/a.

:exclamation: Current head 4845e45 differs from pull request most recent head 37a37d3. Consider uploading reports for the commit 37a37d3 to get more accurate results

@@            Coverage Diff             @@
##             main     #812      +/-   ##
==========================================
- Coverage   69.27%   64.21%   -5.06%
==========================================
  Files         410      528     +118
  Lines       21308    32260   +10952
==========================================
+ Hits        14761    20717    +5956
- Misses       5792    10597    +4805
- Partials      755      946     +191

Flag
Coverage Δ

integration
64.21% <ø> (+17.69%)
:arrow_up:

unittests
64.21% <ø> (+0.21%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/toolkit/integration-test/utils.go
77.27% <0.00%> (ø)

...rvices/api/store/postgres/migrations/migrations.go
100.00% <0.00%> (ø)

...i/store/postgres/migrations/16_add_chain_labels.go
76.92% <0.00%> (ø)

pkg/engine/testutils/handler.go
100.00% <0.00%> (ø)

...ces/tx-sender/tx-sender/use-cases/mocks/crafter.go
100.00% <0.00%> (ø)

...i/store/postgres/migrations/20_deprecated_orion.go
80.64% <0.00%> (ø)

...ices/tx-sender/tx-sender/use-cases/mocks/signer.go
66.66% <0.00%> (ø)

pkg/broker/sarama/mock/consumer_group.go
81.37% <0.00%> (ø)

pkg/toolkit/app/metrics/mock/metrics.go
92.30% <0.00%> (ø)

pkg/toolkit/tcp/metrics/mock/mock.go
76.00% <0.00%> (ø)

... and 113 more


TimerTrigger Example not working

I followed the instructions at https://learn.microsoft.com/en-us/azure/azure-functions/functions-scenario-database-table-cleanup#add-a-timer-triggered-function but the parameters in Run "TimerInfo myTimer, ILogger log" seem to have changed as "TimerInfo" was not found. Is this the "MyInfo" now? When I start the function, I always get an error:
Exception: System.AggregateException: One or more errors occurred. (Value cannot be null. (Parameter 'logger'))
Removing line log.LogInformation($"{rows} rows were updated"); and replacing "TimerInfo" with "MyInfo" fixed the problem, but would be great to update the example. Many thanks!

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

ID: e4785005-a130-a392-7b4a-c8c6d36bad37
Version Independent ID: 6beb58e0-167c-c08d-46ff-13f72ddbaf31
Content: Use Azure Functions to perform a database clean up task
Content Source: articles/azure-functions/functions-scenario-database-table-cleanup.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@K232
Thanks for your feedback! We will investigate and update as appropriate.


Alpine docker compilation error sh: xtensa-lx106-elf-g++: not found

Error compiling ESP8266 code:
--------------------------------------------------------------------------------
HARDWARE: ESP8266 80MHz, 80KB RAM, 1MB Flash
Dependency Graph
|-- ESP8266WiFi @ 1.0
|-- ESP8266mDNS @ 1.2
Compiling .pioenvs/garage-door-fan/src/esphome/components/api/api_connection.cpp.o
sh: xtensa-lx106-elf-g++: not found
Compiling .pioenvs/garage-door-fan/src/esphome/components/api/api_frame_helper.cpp.o
*** [.pioenvs/garage-door-fan/src/esphome/components/api/api_connection.cpp.o] Error 127
sh: xtensa-lx106-elf-g++: not found
*** [.pioenvs/garage-door-fan/src/esphome/components/api/api_frame_helper.cpp.o] Error 127
========================== [FAILED] Took 2.27 seconds ==========================

Reproduced with PIO and Alpine.
Following ESPHome PR to switch to HA Alpine base and see how/if it works.

Alpine works when adding gcompat, but sticking with Debian based build for now.


[Bug Report] Can't make shape [1]  tensor with bfloat16 dtype and ROW_MAJOR layout

Describe the bug
A clear and concise description of what the bug is.
Can't make size 1 ROW_MAJOR layout tensor.
To Reproduce
Steps to reproduce the behavior:
    any_cpu = torch.ones((1))
    any = ttl.tensor.Tensor(any_cpu, ttl.tensor.DataType.BFLOAT16).to(device)

    Always | FATAL    | Buffer size and page size should be larger than 0 bytes!

E       RuntimeError: TT_FATAL @ tt_metal/impl/buffers/buffer.cpp:31: size != 0 and page_size != 0
E       info:
E       Buffer size and page size should be larger than 0 bytes!
E       backtrace:
E        --- tt::tt_metal::Buffer::Buffer(tt::tt_metal::Device*, unsigned long, unsigned long, tt::tt_metal::BufferType, tt::tt_metal::TensorMemoryLayout, std::optional<tt::tt_metal::ShardSpecBuffer>)
E        --- tt::tt_metal::tensor_impl::detail::allocate_interleaved_buffer_on_device(unsigned int, tt::tt_metal::Device*, tt::tt_metal::Shape const&, tt::tt_metal::DataType, tt::tt_metal::Layout, tt::tt_metal::MemoryConfig const&)
E        --- tt::tt_metal::tensor_impl::allocate_buffer_on_device(unsigned int, tt::tt_metal::Device*, tt::tt_metal::Shape const&, tt::tt_metal::DataType, tt::tt_metal::Layout, tt::tt_metal::MemoryConfig const&, std::optional<tt::tt_metal::ShardSpecBuffer>)

Running the above code produces the error message mentioned above.
I think probelm is https://github.com/tenstorrent-metal/tt-metal/blob/main/tt_eager/tensor/tensor_impl.hpp#L127
because packed_buffer_sze_bytes return 0, and the variable size in the following code is set to 0.
TT_FATAL(size != 0 and page_size != 0, "Buffer size and page size should be larger than 0 bytes!");
Expected behavior
A clear and concise description of what you expected to happen.
The Python code above should be executable.
Screenshots
If applicable, add screenshots to help explain your problem.
Please complete the following environment information:

OS: [e.g. Ubuntu 20.04]
Version of software (eg. commit) 6e4828ac123cee0ce97d7e155a29a9d01736273a

Additional context
Add any other context about the problem here.

tagging it as a feature


Worker & app on different servers

Hello @ricardclau,
Thanks a lot for ansistrano.
I have a somewhat more complex setup because my app and worker are on two separate servers and both use a common code base for some functions.
So when I deploy a new version of my app, I need to deploy both at the same time.
To maximize the use of the workers, the ideal steps would be:

Push both worker & app new releases to servers
Stop and drain workers then symlink app code
Symlink worker code then restart nginx/php/queues to apply new code

I would need to stop & drain worker before worker symlink step, but run worker symlink only once app symlink step has been done. It seems it is not possible to nest ansistrano deploy unfortunatly.
Is ansistrano intended to be used for this use case or should I just use some ansistrano tasks and chain them in the order I need?
Thanks

Hi @trompx
Yeah, that is a limitation and I don´t think there is an easy way to overcome that
What I would do would be:

Create a somewhat more complex playbook with multiple plays

1st play -> target your workers servers, stop your workers (outside of ansistrano, as in, run your own tasks) and deploy the new code with ansistrano (but don´t restart the workers)
2nd play -> target your app servers and deploy the code
3rd play -> target the workers again and just run again your task to restart them

I know this is a bit cumbersome but Ansible can work fairly well as an orchestrator joining multiple plays in a playbook and Ansistrano is a tool to deploy applications
Hope this makes sense!

Wow that was fast @ricardclau.
Thanks a lot for your input, I had exactly that kind of steps in mind but thought it had to be a better way. But I guess I will follow this worflow 👍

You were lucky I found some time to answer issues and merge a long time standing PR ;)
Let me know if you need any help joining all this tasks in a single playbook targetting different hosts in multiple plays!

Really appreciate :) I will let you know if I am stuck but it should be alright.


send email after website is generated

Signed-off-by: Arnav Gupta<EMAIL_ADDRESS>

addresses issue #509

Current coverage is 50.41% (diff: 21.42%)

Merging #553 into development will decrease coverage by 1.66%

@@           development       #553   diff @@
=============================================
  Files                4          5     +1
  Lines              457        484    +27
  Methods             45         47     +2
  Messages             0          0
  Branches            63         63
=============================================
+ Hits               238        244     +6
- Misses             219        240    +21
  Partials             0          0

Powered by Codecov. Last update 707e2f8...0df1e86

@championswimmer can you add some tests here as we are going down in 1.66% coverage with this.

@aayusharora
We have gone down a lot in the last week. Will make separate PR for adding more tests.
Btw here is screenshot of this PR working on my local deployment

Ok @championswimmer Sucessfully get the email with Live Preview and zip to download  Merging this thanks :)


[FZ Editor] device-id is null

Settings parsing error
'zones-settings.json' contains malformed data.
Data:
{
"devices": [
{
"device-id": null,
"active-zoneset": {
"uuid": "{88099980-A199-405D-9DB8-CECA1ECF53BB}",
"type": "custom"
},
"editor-show-spacing": true,
"editor-spacing": 2,
"editor-zone-count": 3,
"editor-sensitivity-radius": 20
},
{
"device-id": "FancyZones#MultiMonitorDevice_7680_2160_{00000000-0000-0000-0000-000000000000}",
"active-zoneset": {
"uuid": "{4121A095-512D-4983-8F59-465BA16B1C85}",
"type": "priority-grid"
},
"editor-show-spacing": true,
"editor-spacing": 16,
"editor-zone-count": 3,
"editor-sensitivity-radius": 20
},
{
"device-id": "AUS28B1#5\u00261f2823f3\u00260\u0026UID4353_3840_2160_{00000000-0000-0000-0000-000000000000}",
"active-zoneset": {
"uuid": "{B9DD5143-CF10-47E9-9502-32C51FAFCEAA}",
"type": "columns"
},
"editor-show-spacing": true,
"editor-spacing": 16,
"editor-zone-count": 3,
"editor-sensitivity-radius": 20
},
{
"device-id": "SAM0B81#4\u002684959fc\u00260\u0026UID198147_3840_2160_{00000000-0000-0000-0000-000000000000}",
"active-zoneset": {
"uuid": "{838D2A9C-A169-4809-B6CB-9B0957B0A59D}",
"type": "priority-grid"
},
"editor-show-spacing": true,
"editor-spacing": 16,
"editor-zone-count": 3,
"editor-sensitivity-radius": 20
},
{
"device-id": "FancyZones#MultiMonitorDevice_3840_2160_{00000000-0000-0000-0000-000000000000}",
"active-zoneset": {
"uuid": "{44BA1076-F0B2-4E84-9985-BCFCA045327A}",
"type": "priority-grid"
},
"editor-show-spacing": true,
"editor-spacing": 16,
"editor-zone-count": 3,
"editor-sensitivity-radius": 20
},
{
"device-id": "FancyZones#MultiMonitorDevice_1920_1080_{00000000-0000-0000-0000-000000000000}",
"active-zoneset": {
"uuid": "{0FCB179E-E22B-43D9-9A24-7CACAC8C56E0}",
"type": "priority-grid"
},
"editor-show-spacing": true,
"editor-spacing": 16,
"editor-zone-count": 3,
"editor-sensitivity-radius": 20
}
],
"custom-zone-sets": [
{
"uuid": "{88099980-A199-405D-9DB8-CECA1ECF53BB}",
"name": "MAGLayout",
"type": "grid",
"info": {
"rows": 2,
"columns": 4,
"rows-percentage": [
5106,
4894
],
"columns-percentage": [
2500,
2500,
2500,
2500
],
"cell-child-map": [
[
0,
1,
2,
3
],
[
4,
1,
2,
5
]
],
"show-spacing": true,
"spacing": 2,
"sensitivity-radius": 20
}
}
],
"templates": [
{
"type": "blank",
"show-spacing": false,
"spacing": 0,
"zone-count": 0,
"sensitivity-radius": 0
},
{
"type": "focus",
"show-spacing": false,
"spacing": 0,
"zone-count": 3,
"sensitivity-radius": 20
},
{
"type": "columns",
"show-spacing": true,
"spacing": 2,
"zone-count": 4,
"sensitivity-radius": 20
},
{
"type": "rows",
"show-spacing": true,
"spacing": 16,
"zone-count": 3,
"sensitivity-radius": 20
},
{
"type": "grid",
"show-spacing": true,
"spacing": 16,
"zone-count": 3,
"sensitivity-radius": 20
},
{
"type": "priority-grid",
"show-spacing": true,
"spacing": 16,
"zone-count": 3,
"sensitivity-radius": 20
}
]
}
]
}

@escuridao
thank you for reporting the issue. The same problem has been reported in https://github.com/microsoft/PowerToys/issues/9478 (but for lack of activity it might get closed, so I'll keep this one open).
The configuration file has some invalid data, we don't know what may have caused it.
Did you noticed the problem after a PowerToys update or after editing some layouts or changing FZ settings?
Do you always keep this option on or to you switch it time to time?

The quick workaround would be to delete the zones-settings.json file and recreate you custom layouts.

Thank you for answer. I am using two 4k monitor so check Allow zones option. Uninstall after then re install but still get same error.

@escuridao
uninstalling doesn't delete the configuration file.
You can do the following:

quit PowerToys
open the Command Prompt and execute:

> del %localappdata%\Microsoft\PowerToys\FancyZones\zones-settings.json

Don't change. This error get only custom layout.

@enricogior, do we have a fix for this?

Improved with the update that came in thank you

@escuridao to be sure, you're saying 0.33 fixed it for you?


Doesnt show extra options applied on Table

Altering table with extra options on a table is not shown anywhere. e.g. autovacuum_vacuum_threshold
,autovacuum_analyze_threshold etc which can be applied like this :
alter table entitlements.reference set (autovacuum_vacuum_threshold=1000000);
This can be seen using psql client though with command :
\d+ entitlements.reference

Thanks for noticing.
Will add them in 5.1.2.


etebase-server: 0.11.0 -> 0.13.1

Description of changes
Removes the dependency on Django 3, noted in #262907. The upstream has a slight issue in their package specifier for Django, so I've patched this and will be submitting a fix upstream. There are no breaking changes, so I haven't updated the release notes.
Edit: The above is obsolete as my patch has been merged into an upstream patch release and I've updated this package to match that version. No further changes are included.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build etebase-server


Cannot find documentation on template variables... (showRssFeed, showToggleTheme, etc)

I'm brand new to Astro. I'm not new to development. I found your template and it is what made me decide to check out Astro for these projects I'm working on. I love the work and effort you have put into this. I look forward to AstroWind v2. I am happy to create a PR to add some documentation about using some of these more advanced boolean flags. I tried to go through the code and figure out how to use/pass them through. I'm sure if I understood more about Astro, I probably would know the answer, but since I don't, I would love to learn and then help this project by getting it into some documentation!
So... I'll track through what I've found. What I would really like is to remove the RSS button next to the CtA button in the top right of the index.astro page. I figured out that the Header.astro is what contains showRssFeed variable. This is passed in through the PageLayout.astro. I haven't figured out where that page gets it's variables. There is another two variables getting passed into the <Header> tag ... isSticky and showToggleTheme. I've also not been able to find those. I assume this means they are Astro variables that I would need to put into a configuration somewhere.
If someone can direct me where I should put those, I would greatly appreciate it. I would be happy to make a PR and get some examples into the documentation. I believe since AstroWind is a popular template, you will get a lot of Astro newbies. The more examples we can get into your documentation the faster we'll all get up to speed.
One other small thing I noticed. I couldn't figure out how to "download" the template to use it. It was much easier once I put the Astro docs to use... I used npm create astro@latest -- --template onwidget/astrowind which made it quite easy. I had to try a couple of times to get that working properly, but that line got me going immediately.

Just putting some other ideas in here that I feel I should document when I submit my PR...
flat-color-icons ... it took me a while to find how to include additional icons from this set. I was able to work my way backwards, but some links in the documentation would have helped me go faster. I tried searching in this repository, but it wouldn't pull up anything other than the files that were using the icons. Not the configuration file astro.config.mjs where I needed to input those additional icons I wanted.
Thanks again for such a great template to work with! It has been a pleasure even with these hiccups. I'm used to having to dig... :)


CloudFront Function Already Exists when deploy NextJS page

Issue Description
I encountered an issue while deploying my SST application to the staging environment. The deployment fails with the following error:

Steps to Reproduce

Deploy the SST application to the staging environment.
Observe the deployment failure with the error message indicating that the CloudFront function already exists.

Expected Behavior
The deployment should succeed without errors, even if the CloudFront function already exists.
Actual Behavior
The deployment fails with a FunctionAlreadyExists error.
Environment

SST version: 3.3.44
AWS region: ap-southeast-1
Deployment stage: staging

Here is the relevant code snippet from my sst.config.ts:
new sst.aws.Nextjs("MyNextJS", {
  ...(["production", "staging"].includes(app.stage)
    ? {
      domain: `${app.stage === 'staging' ? 'staging.' : ''}mydomain.com`,
    }
    : {})
}); ```

Hmm that looks okay to. We'll try it out.

@jayair  @fwang I think when creating a new site Next.js, it automatically sets up a CloudFront function. However, when removing it, the associated CloudFront distribution isn't deleted. This might be due to links with certain distributions.

@dtduong30 just to clarify, have you previously deployed to staging and removed the stage? And you got this error when deploying to the staging stage again?


Django + Sentry, Sentry Doesn't Work in deployment.

Context
Django does not send Sentry error after deployment. (only appear in zappa tail console) In the local environment, the Sentry and console normally display an error.
Expected Behavior
I hope there will be an error in Sentry.
Actual Behavior
It appears only in the console. zappa tail
Your Environment
Zappa==0.48.2
Python 3.6
This is my Production Requirements.txt
## Django ##
pytz==2018.9
sqlparse==0.3.0
Django==2.2

## Django Envrion ##
django-environ==0.4.5

## Hash ##
argon2-cffi==19.1.0
cffi==1.12.2
pycparser==2.19

## DATABASE ##
psycopg2-binary==2.8

## Sentry ##
sentry-sdk==0.7.9

## Django Storages ##
django-storages==1.7.1

## Anymail ##
django-anymail==6.0

zappa_settings.json
{
    "dev": {
	"aws_region": "ap-northeast-2",
        "django_settings": "config.settings.production",
        "profile_name": "zappa",
        "project_name": "django-lambda",
        "runtime": "python3.6",
        "s3_bucket": "django-lambda-t10",
        "vpc_config": {
          "SubnetIds": [
            "subnet-ca3e7686"
          ],
          "SecurityGroupIds": [
            "sg-0e7e40174acf63810"
          ]
        }
	}
}

Log Setting
# LOGGING
# ------------------------------------------------------------------------------
# https://docs.djangoproject.com/en/dev/ref/settings/#logging
# See https://docs.djangoproject.com/en/dev/topics/logging for
# more details on how to customize your logging configuration.
LOGGING = {
    "version": 1,
    "disable_existing_loggers": True,
    "formatters": {
        "verbose": {
            "format": "%(levelname)s %(asctime)s %(module)s %(message)s"
        }
    },
    "handlers": {
        "console": {
            "level": "DEBUG",
            "class": "logging.StreamHandler",
            "formatter": "verbose",
        }
    },
    "loggers": {
        "django.db.backends": {
            "level": "ERROR",
            "handlers": ["console"],
            "propagate": False,
        },
        # Errors logged by the SDK itself
        "sentry_sdk": {"level": "ERROR", "handlers": ["console"], "propagate": False},
        "django.security.DisallowedHost": {
            "level": "ERROR",
            "handlers": ["console"],
            "propagate": False,
        },
    },
}

# Sentry
# ------------------------------------------------------------------------------
SENTRY_DSN = env("SENTRY_DSN")
SENTRY_LOG_LEVEL = env.int("DJANGO_SENTRY_LOG_LEVEL", logging.INFO)

sentry_logging = LoggingIntegration(
    level=SENTRY_LOG_LEVEL
)

sentry_sdk.init(dsn=SENTRY_DSN, integrations=[sentry_logging, DjangoIntegration()])

I think you might need the AwsLambdaIntegration too. This is what I have...
# 3rd-party
import sentry_sdk
from sentry_sdk.integrations.aws_lambda import AwsLambdaIntegration
from sentry_sdk.integrations.django import DjangoIntegration

# ----------------------------------------------------------------------------
# Error logging and tracking with Sentry
#
sentry_sdk.init(
    dsn=config.sentry_dsn,
    environment=config.sentry_environment,
    integrations=[AwsLambdaIntegration(), DjangoIntegration()],
)
# ----------------------------------------------------------------------------

Having the same issue here. My guess is the vpc configuration for external connections. I wish zappa would handle the configuration described at this section  for the end user

Having the same issue here. My guess is the vpc configuration for external connections. I wish zappa would handle the configuration described at this section  for the end user


Release v2.3.0

Pull Request Test Coverage Report for Build 788

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

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/quantum/task_registry.ex
0
1
0.0%

Totals

Change from base Build 787:
0.0%

Covered Lines:
335

Relevant Lines:
403

💛  - Coveralls

👍


Stuck on step 2

I am going through the course (attempting happy path) and I got stuck during step 2.
I was able to create the Azure Subscription, and find the ID. But, I get stuck when I try to run the command in my terminal with the ID, I get an error message.
Here are the instructions I'm on - I'm getting hung up on step 6.
I should also note in step 5, I get a lot of info back, for subscriptions that I was previously unaware of. That may be irrelevant.
The output that I'm trying to use from step 5:
  {
    "cloudName": "AzureCloud",
    "homeTenantId": "7*******-8***-****-****-***********7",
    "id": "2*******-3***-****-****-***********0",
    "isDefault": true,
    "managedByTenants": [],
    "name": "Pay-As-You-Go",
    "state": "Enabled",
    "tenantId": "7*******-8***-****-****-***********7",
    "user": {
      "name"<EMAIL_ADDRESS>      "type": "user"
    }

What I type in step 6:
az ad sp create-for-rbac --name "GitHub-Actions" --role contributor \
                          --scopes /subscriptions/2*******-3***-****-****-***********0 \
                          --sdk-auth

Terminal output:
Changing "GitHub-Actions" to a valid URI of "http://GitHub-Actions", which is the required format used for service principal names
Found an existing application instance of "7*******-****-****-****-***********a". We will patch it
Insufficient privileges to complete the operation.

Note: The referenced ID in the output is a brand new ID and I have no idea where it came from.

cc @hectorsector @mattdavis0351 @lmkeston @mjcastner because I think you all were able to make it past this step and you may see what I'm doing wrong 👀

@brianamarie are you using a newly created Azure account? Or your GitHub-provided creds? You should create a new account -- we could put it in the course instructions but I think this really only applies to Hubbers. Maybe we can make a quick note just in case others have work accounts they want to use and run into similar issues.

@hectorsector Thank you! That's definitely what I did wrong. I do think a message may be helpful, but it also may only apply to a small set of users. 🤷♂ I will try this again later this week (probably Friday). I'm sorry I couldn't get through it before the ship date, but I know when I go through it and it's public it will also be awesome. 😊


june hb start

July Heartbeat
Publish Date: July 15th.

[ ] There are no grammatical errors, jargon, or obvious stylistic issues. (for reviewer to check)
[x] Have images been run through tiny.png?
[x] Are all lines 80 characters or less?
[x] Are Oxford commas observed?
[x] Content Creator has done a complete review for typos/language after taking a break from content
links checked in the piece
[x] Have reviewed what the piece looks like on your own [machine using yarn develop](https://dvc.org/doc/user-guide/contributing/docs#development-environment)

There's definitely more I could put in here, but it's already 16 minutes long to read.  Will save for next month.

@jendefig What's status on this?

@jendefig What's status on this?

The status is I couldn't get it done and it will turn into July Heartbeat.  It is not ready for review.

@rogermparent @yathomasi I started this branch before we changed from master to main so there is an issue and I don't know how to fix this.  Also see the issue regarding the wrapping awesome image that isn't wrapping.  I don't know why.  Could you help me?  I'm out of office today at my daughter's college orientation, but I will check back in.

I'll try to set the PR right on my end, and let you know if any action on your end is needed.

I've merged main into this branch so we can be sure it's up-to-date! I can't be 100% on what the state of your system is, but I think the most you'll have to do is run git pull (technically git fetch, but pull runs fetch and it's more likely you've used pull before).
We don't really push to main, so I don't think you'll be very affected. When you want to bring any PR up-to-date with the latest changes, just run git pull origin main.
I'm not sure if you're running any interface for Git, if you do and these instructions don't translate we can try to figure it out.

I was having issues getting things to sync in here.  So I'm closing this and I opened a new branch for this blog piece.
Closing this one.


dbcon wrapper

@kdebrab, @saroele I was able to take a look at Karel's code, to find out it works fine! Well done!
I did run in to some JsonDecodeError's in the beginning, when I was furiously adding, removing and syncing sensors, but this was behaviour I had also encountered sometime in the past so I don't think it has anything to do with what we're doing right now. I decided to start fresh: deleted my .tmpo-folder, pip-uninstalled tmpo so I could import directly from the branch.
Doing a houseprint.init_tmpo() works fine (which creates a tmpo session and adds all sensors), doing houseprint.sync_tmpos() also works fine. Fetching data works just as you'd expect.
I was able to init_tmpo on two separate houseprints in two separate notebooks, without getting the database locked errors. I can fetch data in one notebook, then go to the other one and fetch data too. No problems. The really cool part is I was able to run get_data() simultaneously in two separate notebooks!
Could you guys check it out too?

haha, it looks like @kdebrab did not have such a wasted evening after all :-)  Well done Karel!
I hope to find some time tomorrow, not sure though. Work is absorbing me atm.

Hmmm,  tested it now, but I still get OperationalError: database is locked  sometimes.  I have the impression though that the problem occurs less often.
To get more grip on the behaviour, I created a quick and dirty test.  With the old tmpo, this test fails, with the new it works.  Can you also try this? Here's the code:
import os
import tmpo
print(tmpo.__file__)

tmpo1 = tmpo.Session(os.getcwd())
tmpo1.add('key', 'token')
tmpo2 = tmpo.Session(os.getcwd())
tmpo2.add('key', 'token')

print("Test successful")

Indeed. This doesn't work on version 0.2.0, but it does on 0.2.1.
I would argue to move on and merge this. As far as I've tested the code it doesn't create any new issues, but it solves many. Granted there are still some other issues...


Updated Evernote color

Wanted to update the Evernote primary color! We recently changed some colors and haven't updated it everywhere but wanted to pay it forward :) See our marketing color palette
https://evernote.com/brand/color-palette/
Oh and let me know if the Evernote logo needs to be reordered to be somewhere else since the green has a little more blue now but I'm actually not sure how to approximate where in the list it should be. Might be worth considering a tool that calculates what the order is based on hex value?

@augbog Thanks very much! It’s great to have the Evernote colour up to date.
The web page is built using a Node.js script (which I’ve just run and pushed). The script takes the icon definitions from the JSON file you edited, calculates hues from the hex values, sorts the list, then outputs the web page and Sass/LESS files.

oh sweet thanks :)


I am using netless/fastboard-react in library and I encountered this error, ./node_modules/remitter/dist/remitter.mjs 3:5 Module parse failed: Unexpected token (3:5) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file.

As soon as I comment my fastboard, it will work fine.

It looks like your bundler either cannot recognize .mjs files (which are javascript files) or cannot parse the "class field" syntax (ES2022):
// source code of remitter.mjs
var Remitter = class {
  _l = /* @__PURE__ */ new Map(); // <- failed to parse this code

This means that your bundler (or loader) is too old to work with some libraries that fastboard is depending on. I'd recommend you to use a more modern bundler like esbuild or vite to continue.

I'm closing it as it seems not an issue with fastboard, but with the bundler.


Test Issue created at Fri, 19 Nov 2021 11:48:52 GMT

Test issue body  Fri, 19 Nov 2021 11:48:52 GMT

Comment on issue at Fri, 19 Nov 2021 11:48:54 GMT


Unable to find type [System.IO.Compression.ZipFile

Getting this error: Unable to find type [System.IO.Compression.ZipFile
Dumps from PS:
Exporting UserReport: Completed 78,906 in 00:13:31
Loading groups in lookup cache
Exporting NotificationsEmailsReport: Completed 85 in 00:00:06
Loading administrative units in lookup cache
Loading applications in lookup cache
Loading service principals in lookup cache
Exporting RoleAssignmentReport: Completed 1,232 in 00:00:15
Exporting AppCredentialsReport: Completed 18,856 in 00:02:36
Exporting ConsentGrantReport: Completed 49,738 in 00:05:36
WARNING: The export package has not been generated
WARNING: If you are working with microsoft or a provider on the assessment please warn them
WARNING: Please check GitHub issues and fill a new one or reply on existing ones mentionning the errors seen
WARNING: https://github.com/AzureAD/AzureADAssessment/issues
Unable to find type [System.IO.Compression.ZipFile].
Any solution for this?

@Dsrygaard which version are you using? can you get latest version and try Install-Module -Name AzureADAssessment -AllowPrerelease

Solved by adding Add-Type -AssemblyName System.IO.Compression.FileSystem before running the script

I found the cause for this. It was only happening on Windows PowerShell but has been fixed now.


Update the v2 extension cert checks to use util::Status

Fix the v2 redaction and name constrained intermediate CA checking to use util::Status, update tests etc.

LGTM

Although my usual comment about checking util::Status in tests apply. :wink:

Sorry, totally forgot about EXPECT_OK in all these PRs. I've fixed this one. Will merge if build passes.


Improve Debug Description for TriviaPieces

Print out the kind and number of trivia pieces instead of a "TriviaPiece"
placeholder. This makes debugging failures involving trivia a touch easier.

@swift-ci test

Great minds think alike!


Error when using Login_Mobile_Automatic and Login_Mobile_Button as login page on localhost with MakeItNative app

Hi,
When using Login_Mobile_Automatic or Login_Mobile_Button as the login page for a native app, the MakeItNative app gives an error. The error I get is a missing module and the build failes.
StudioPro <IP_ADDRESS>938
The error log is:
[Output] error: Error: Unable to resolve module react-native-inappbrowser-reborn from C:\Users***********\javascriptsource\oidc\actions\JS_OpenAuthURL.js: react-native-inappbrowser-reborn could not be found within the project or in these directories:
[Output]   ....\javascriptsource\oidc\actions\node_modules
Is this a know issue or am I doing something wrong?
Thanks!
Kind regards,
Lourens/VDS

Hello,
I don't believe this is a known issue, nor is it a common error documentation has an easy fix for. Could you please contact our Support department and provide these details to them?
If there is a documentation update required after your Support ticket is resolved, I'll be happy to handle it then.
Thank you,
Connor

Thanks, will do!


chore(deps): update terraform github.com/terraform-ibm-modules/terraform-ibm-landing-zone to v5.24.6

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-landing-zone
module
patch
v5.24.5 -> v5.24.6

Release Notes

terraform-ibm-modules/terraform-ibm-landing-zone (github.com/terraform-ibm-modules/terraform-ibm-landing-zone)
v5.24.6
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.18.3 (#821) (4feb90e)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v1.4.11

Your semantic-release bot :package::rocket:


Diagonal gradients are not working

Hi everyone, i'm trying to make a gradient start at bottom left and end at top right. I think my code is right after reading some similar issues but the results is just an horizontal gradient from left to right on both Android & iOS :( I'am missing something ?
<LinearGradient         style={styles.gradient}         colors={["#42A2CD", "#5CCC81"]}         start={{ x: 0, y: 1 }}         end={{ x: 1, y: 0 }}       >         <Text style={styles.title}>{children}</Text>       </LinearGradient>
Result:

Expected:

Hi.. If you still have this issue, the props you're passing are for horizontal gradients. You need extra properties like useAngle={true} locations=[..., ...., ...] angle={***} as illustrated at the bottom of the readme file.

Hi guys, did you managed to get diagonal gradient.

Hi.. If you still have this issue, the props you're passing are for horizontal gradients. You need extra properties like useAngle={true} locations=[..., ...., ...] angle={***} as illustrated at the bottom of the readme file.

I'm using Expo but this useAngles props doesn't work. Yeah, it's in the docs but if you look at the file definitions there is no useAngle angle etc. props! So @pixelize did you figure it out how to implement diagonal gradient?

Hi! I'm trying to figure this one out too. Any updates?

Haven't try the solution proposed by @eazzyLEE, i will give a try asap and let you know ;)

I actually realized that I had an old version of this package. Once I updated, the instructions on the readme worked (just like @eazzyLEE pointed out)! I needed 3 colors, so I needed 3 locations
<LinearGradient     style={...}     colors={["", "", ""]}     locations={[0, 0.5, 1]}     useAngle={true}     angle={45}     angleCenter={{ x: 0.5, y: 0.5 }}   />


batch requests ff removal templates

removing in back end so removing the code that handles toggling it on/off.
has already been removed in internal

Good to go assuming the flag is already 'globally enabled' supposing that's also a thing for templates.

yeah it's globally enabled and has been removed on the internal repo for a while