Add podman pod prune

podman system prune would leave pods be, and not prune them if they were stopped.
Fix this by adding a podman pod prune command that prunes stopped pods similarly to containers.
Signed-off-by: Peter Hunt<EMAIL_ADDRESS>

Note: I am debating adding a pod state called OnlyInfra or something indicating the only running container in the pod is the infra container. If every other container in the pod is stopped then it may be worth also pruning those. WDYT

code LGTM, could you fix the man pages?

do i read the code correctly that you wired it for the remote client but didn't actually implement it?

@baude yeah that's correct. It seems containers prune is also not implemented, so I figured pods prune not being implemented would be okay

@baude yeah that's correct. It seems containers prune is also not implemented, so I figured pods prune not being implemented would be okay

We just havent gotten to containers prune.  So please do the pods prune. Much appreciated.  I'm available for help and questions.

5 hours later.... remote pod prune exists :) ptal @baude @jwhonce

/lgtm

/approve


team_communication: automatically detect target ip address

Summary
Automatically detect the target address for team communication from the wifi interface using netifaces.
In case of any problem, the default address configured is used.
Related issues
Closes #578.
Checklist

[ ] Run colcon build
[ ] Write documentation
[ ] Test on your machine
[ ] Test on the robot
[ ] Create issues for future work
[ ] Triage this PR and label it

What's the state with this PR? @timonegk

It is still relevant but the reviews must be addressed and it has to be tested


[Snyk] Security upgrade @rollup/plugin-commonjs from 21.0.1 to 26.0.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

packages/node/base/package.json
packages/node/base/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116
  631

Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818
  479

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

Checkmarx One – Scan Summary & Details – c15abce8-1072-46a5-8bc2-b55f2e2d1f69
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2024-27351
Python-Django-1.2
Vulnerable Package

CVE-2024-29180
Npm-webpack-dev-middleware-5.2.1
Vulnerable Package

CVE-2024-4068
Npm-braces-2.3.2
Vulnerable Package

CVE-2024-4068
Npm-braces-3.0.2
Vulnerable Package

Cx37f28a21-b2a7
Npm-angular-1.8-1.8.2
Vulnerable Package

Cx94a5c81d-63b1
Npm-angular-1.8-1.8.2
Vulnerable Package

Cx9eb96c9b-eb45
Npm-angular-mocks-1.8-1.8.2
Vulnerable Package

Cxcf770dcb-fd21
Npm-angular-1.8-1.8.2
Vulnerable Package

Sensitive Port Is Exposed To Entire Network
/ec2.tf: [118](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/ec2.tf# L118)
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Sensitive Port Is Exposed To Entire Network
/ec2.tf: [118](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/ec2.tf# L118)
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Unpinned Actions Full Length Commit SHA
/pull_request.yaml: [14](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//.github/workflows/pull_request.yaml# L14)
desc

Unpinned Actions Full Length Commit SHA
/semgrep.yml: [14](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//.github/workflows/semgrep.yml# L14)
desc

Unpinned Actions Full Length Commit SHA
/build.yaml: [15](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//.github/workflows/build.yaml# L15)
desc

CVE-2024-28849
Npm-follow-redirects-1.14.6
Vulnerable Package

CVE-2024-28863
Npm-tar-6.1.11
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.19
Vulnerable Package

CVE-2024-29041
Npm-express-4.17.1
Vulnerable Package

CVE-2024-4067
Npm-micromatch-3.1.10
Vulnerable Package

CVE-2024-4067
Npm-micromatch-4.0.4
Vulnerable Package

IAM Access Analyzer Not Enabled
/iam.tf: [1](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/iam.tf# L1)
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/ecr.tf: [1](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/ecr.tf# L1)
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/rds.tf: [1](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/rds.tf# L1)
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/s3.tf: [1](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/s3.tf# L1)
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

Fixed Issues

Severity
Issue
Source File / Package

Cx37f28a21-b2a7
Npm-angular-1.8-1.8.2

Cx94a5c81d-63b1
Npm-angular-1.8-1.8.2

Cx9eb96c9b-eb45
Npm-angular-mocks-1.8-1.8.2

Cxab55612e-3a56
Npm-braces-3.0.2

Cxab55612e-3a56
Npm-braces-2.3.2

Cxca84a1c2-1f12
Npm-micromatch-3.1.10

Cxca84a1c2-1f12
Npm-micromatch-4.0.4

Cxcf770dcb-fd21
Npm-angular-1.8-1.8.2

S3 Bucket SSE Disabled
/ec2.tf: [306](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/ec2.tf# L306)

S3 Bucket SSE Disabled
/s3.tf: [42](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/s3.tf# L42)

S3 Bucket SSE Disabled
/s3.tf: [65](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/s3.tf# L65)

S3 Bucket SSE Disabled
/s3.tf: [89](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/s3.tf# L89)

S3 Bucket SSE Disabled
/s3.tf: [1](https://github.com/demolab1/TerraformWebgoat/blob/snyk-fix-fe6e69738b864cc95d475169e96c0835//terraform/aws/s3.tf# L1)

CVE-2007-2379
Npm-jquery-3.6.0

CVE-2014-6071
Npm-jquery-3.6.0


migrate to gradle

We can add gradle, but the project still has to work with maven. We did for the library application: https://github.com/tipsy/spark-basic-structure

OK. it's trivial to just keep the pom.xml in that case.
But maven is a security risk for those who will try this example, because it downloads dependencies over plain http by default, and it seems there's no obvious way to change that…


Switch to using nanoJson

This parser claims to adhere exactly to the spec and it's passed every test case I've thrown at it so far.

Nice -- thanks for digging so deep on this one.

Great - agreed excellent improvement, thank you!
(Note I fixed up the changelog - it's easy in these merges for the change to end up under the previous release version - and also updated Toolbox to put it back to hoist-core 7.0-SNAPSHOT so we can get the new behavior in use.)


Download Data UI

Thanks guys for putting this up - it is great.
A few comments on the UI and functionality:

We should not include all forms or just show all raw data for download. It won't make any sense to anyone except us! For now, we just need to show the Case Report as available for download but can use other data downloads in future e.g. mhGAP, IMCI etc.
Please can we remove the "Just download the default attributes." option and simply display all variables using the multiple select box as the initial view.
Please can we remove all variables from the multiple select except for the basic set that are currently selected.
Could we include a single "All variables" option, just as we do with "All Alerts" to select all these basic variables or to select just a sub-selection
I realise it may need to come later, but would be also good to have a further filter window of option boxes to further filter to the data e.g just CD, NCD and for certain time periods too

I hope this makes sense? Please let me know if any clarifications are needed.

Incidentally - I don't think we should share with MOH until the initial revisions are made as it will be confusing for them.

"Avilable Attributes" header is mis-spelt. Please can we name as "Variables to Download"

I disagree with point 1. I think as a matter of principle we should let people download all the raw data and I really don't think it is that confusing. We can show the Case Report form as the first form in the list if we want.
2-5 is fine.
We should discuss what we want to do about 6 at a later stage.

The case report form contains innumerable within form calculations, which appear as separate variables include icd1_code, icd2_code, icd3_code, icd4_code etc not to mention all the calculations for CD, IMCI and mhGAP that are included.
These have nothing to do with ICD, IMCI or mhGAP itself and is simply what we use internally to enable the skip logic algorithms and ensure the various modules are integrated together.

My proposal is as follows:
We keep the dropdown box for all the forms, but display the Case Report form as the default choice. Then we display the box to select variables by default. This box will be default only include the default variables, but with a button at the bottom to show all available attributes. This way everything is available, but it should be very easy to just get the default variables.

ok sounds good. Thanks Gunnar - I do agree with the principle everything should be transparent and available.

Incidentally - the refugee data will need differential access, as many more partner will need to download this data but not have access to the other data. I hope this is possible.

We will work something out

I'll try and make these changes this morning.

This is done and pushed to master.


add *-unknown-linux-musl to travis

Not sure how the whole thing works, but I saw this in the fd repo.
Should possibly fix #214

@meain Just for my own education (I'm trying to learn more advanced Github, CI, etc.), is it Travis that builds the releases on projects? Or is it Appveyor? Or do you have to manually add them?

@mathomp4 You could use either Travis or Appveryor to do it automatically.


Enable spilling support for partial aggregation

Resolves https://github.com/facebookincubator/velox/issues/7930, also be related to https://github.com/facebookincubator/velox/issues/7511
Partial aggregation currently relies on following options to reduce memory usage:

kMaxPartialAggregationMemory
kMaxExtendedPartialAggregationMemory

The PR adds the following one to enable flushing on partial aggregation:

kPartialAggregationSpillEnabled (default value: false)

When kPartialAggregationSpillEnabled is set to true, partial aggregation will try spilling data to disk just like final aggregation can do. At the same time, flushing will be disabled.
Also, when spilling has been triggered, code path of abandoning partial aggregation will be disabled.

@mbasmanova @xiaoxmeng Would you like to review? Thanks!

@mbasmanova @xiaoxmeng Hi, would you please help review? Thanks!

@xiaoxmeng

Hi @mbasmanova @xiaoxmeng , should we continue the review? Thanks!

@mbasmanova Thanks

Hi @mbasmanova I've addressed current comments. Would you please take another look? Thank you.

@mbasmanova @xiaoxmeng Do we need two separate spill-enable flags if our goal is to support spilling for aggregation in all equivalent query plans? WDYT?

@zhztheplayer This PR is crucial to batch / ETL queries, 👍 . Perhaps we could add some test cases in the AggregationTest.

Thanks @duanmeng . I've added some tests to AggregationTest.

@mbasmanova @xiaoxmeng Do we need two separate spill-enable flags if our goal is to support spilling for aggregation in all equivalent query plans? WDYT?

Let's keep them separate for the initial version? Spilling for partial aggregation should be turned off by default since it disables flushing. While for regular aggregation spilling is on by default.

@mbasmanova @xiaoxmeng @duanmeng
After going through some history about partial aggregation and companion functions (especially https://github.com/facebookincubator/velox/issues/4412 and https://github.com/facebookincubator/velox/pull/4566), I am feeling that the topic is on the wrong direction. So I am about to close this.
Reason:
Spark's partial aggregation actually doesn't support flushing so ideally in Gluten we should not use Velox (probably Presto also)'s PartialAggregation. Velox's FinalAggregation + Companion functions is better for Gluten to choose. Since final aggregation already supports spilling so no extra effort is needed in my opinion.
PartialAggregation in Velox as a concept should consist of optimizations when a regular aggregation doesn't have to emit full-aggregated data. Spark doesn't have a plan type mapping to this functionality yet.

Closing. Please reopen if anyone thinks it's still needed.

@zhztheplayer Thank you for the update. It comes as a bit of surprise, but I guess it makes sense. Would you also comment on the 2 related issues and close these?

Resolves https://github.com/facebookincubator/velox/issues/7930, also be related to https://github.com/facebookincubator/velox/issues/7511

@zhztheplayer Curious, what prompted you to take another look and go "through some history about partial aggregation and companion functions".

@zhztheplayer Curious, what prompted you to take another look and go "through some history about partial aggregation and companion functions".

One of Gluten's users reported an issue that expression count(distinct l_orderedkey) returns wrong result in Gluten. Spark generated the following plan:
+- HashAggregate(keys=[], functions=[count(distinct l_orderkey#114L)])
   +- Exchange SinglePartition, ENSURE_REQUIREMENTS, [plan_id=140]
      +- (Partial) HashAggregate(keys=[], functions=[partial_count(distinct l_orderkey#114L)])    // <- node 2
         +- (Partial) HashAggregate(keys=[l_orderkey#114L], functions=[])   // <- node 1
            +- Exchange hashpartitioning(l_orderkey#114L, 100), ENSURE_REQUIREMENTS, [plan_id=136]
               +- HashAggregate(keys=[l_orderkey#114L], functions=[])
                  +- FileScan

The plan node I marked as node 2 is using node 1's  output as distinct input to do partial_count. However since node 1 is now mapped to Velox's PartialAggregation, it may flush intermediate data at any time. That makes node 2 output wrong count result.
Looks to be that the user's issue is related to incorrect mapping from Spark's Aggregation + partial function to Velox's PartialAggregation. If we correct the mapping as from Spark's Aggregation + partial function to Velox's FinalAggregation + partial companion function, then we can solve this count+distinct issue and don't have to add spilling support to partial aggregation either. I'm still working with @rui-mo to try to do some refactors to Gluten to use the new mapping, but anyway I think this topic can be closed since it was driven by issue related to Gluten's non-optimal design.


Login attempt failed. Attempted to login 4 times.

What's the cause of this? I'm with REST API's. Thank you and God Bless.
--EDIT
Yes I know now what's the cause of this but how does the user authorize the use of their Google account's data to be used within a website?

Hello, this just happen to me. Did you find a solution?
Thanks


php7 and mssql database driver - mssql extension dropped from php7 core

I'm not sure if there's plans to support PHP7, but if there is...
The MSSQL extension has been voted out of the core (see https://wiki.php.net/rfc/removal_of_dead_sapis_and_exts).  This means that the mssql database driver will not work with php7.  Other frameworks sql server extension wraps the sqlsrv (for when its running on windows) and dblib (for when its running on linux).  If sql server is to be supported with php7, it appears that this methodology will have to be adopted.

We're aware of this, and it's irrelevant to CI.

CI3 already has a sqlsrv driver and a dblib sub-driver for the pdo driver.

thanks - i didn't realize it was through the PDO driver.


changelog crashes the application

See : https://github.com/gabrielemariotti/changeloglib/issues/28
work in progress on their side

fixed by updating appcompat to 23.2.1


Understand and Document the Risks Associated with Administering GitHub

User Need
As a GitHub Administrator,
I want to comprehensively understand the risks associated with administering GitHub and have them documented publicly in our runbooks,
so that the wider team, stakeholders, and any interested parties can be aware of the risks, the measures we've taken, and can provide feedback or insights for further improvement.
Value
Publicly documenting the risks and our approaches to managing them not only promotes transparency but also enables collective knowledge sharing. By being open about the challenges and solutions, we can foster trust among users, stakeholders, and the broader community and benefit from collective wisdom to enhance our GitHub administration.
Functional Requirements:

Conduct a thorough risk assessment of GitHub administration, identifying potential threats, vulnerabilities, and exposures.
Categorise the risks into those that are inherent and those that can be mitigated.
Develop a comprehensive report of the findings.
Document the findings, along with recommended or implemented mitigation strategies, in our Risk Register.

Non-Functional Requirements:

The risk assessment process should be exhaustive, encompassing both technical and human-centric aspects of GitHub administration.
The public documentation in the runbooks should be clear, structured, and easily accessible for the intended audience.
Any sensitive or confidential information must be redacted or generalized to prevent unintended exposure while maintaining the document's usefulness.
Mob as a team exercise

Acceptance Criteria:

[ ] A detailed risk assessment for GitHub administration has been carried out.
[ ] The findings, along with any recommended or implemented measures, are documented in our risk register.

Notes:
While the aim is transparency, care must be taken to ensure that no sensitive information, which could be exploited by malicious actors, is made public.

We will use our risk process to document and track risks.

Date for review set

We surfaced a lot of potential risks in teh first session that we require more analysis. Closing this story and will raise new stories for further sessions. Risks to be added to risk register.


Proof Sources

http://content-guide.apps.staging.digital.gov.au/sources

Closing as covered at #95


Adds support for Rosé Pine Dawn and Rosé Pine

Adds support for Rosé Pine Dawn and Rosé Pine and allow users to pick their favourite accent colour as well as changes the setting menus and some colours around.

@mimishahzad Wouldn't let me add you as a reviewer so feel free to look over the PR and let me know if there is any changes you may want.


regression-test support Non concurrent mode in branch-2.0

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


goto declaration crashes...

@yongkangchen
running latest version of atom, my ctags file is 14mb and atom just stops responding... tried rebuilding tags... reinstalling the module but nothing seems to help... alt click on symbol seems to work... any ideas?
dev tools show a constant stream of symbol-generator script running it just never finishes
https://www.dropbox.com/s/ndzjdtmgt4oevnn/Screenshot 2016-04-01 14.25.05.png?dl=0

There was a conflict with the goto package -> https://atom.io/packages/goto
uninstalling it fixed things...


Destroying persistent store with iOS 9 NSPersistentStoreCoordinator method.

New issue checklist

[x] I have read the README and docs.
[x] I have reviewed the contributing guidelines.
[x] I have searched existing issues and this is not a duplicate.

General information

Library version(s): 6.0.1

As of iOS 9 Apple provides destroyPersistentStore(at:ofType:options:) method for NSPersistentStoreCoordinator.  Would you consider conditionally replacing following methods(https://github.com/jessesquires/JSQCoreDataKit/blob/develop/Source/CoreDataStack.swift#L166-L167) with the new one?
Something like
if #available(iOS 9, tvOS 9, *) {
    try model.removeExistingStore()
    try storeCoordinator.remove(store)
} else {
    try storeCoordinator.destroyPersistentStore(...)
}

Thanks @DenHeadless ! 👍
Sounds good to me 😊

However, I think you have your if and else mixed up 😄

Ouch, sorry =) I'll try to make PR tomorrow =)


[Scheduled] dart pub upgrade --null-safety

Auto-generated by create-pull-request
See: https://github.com/peter-evans/create-pull-request/blob/master/docs/concepts-guidelines.md#triggering-further-workflow-runs

Codecov Report

Merging #155 (f3dab43) into main (6d5db71) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #155   +/-   ##
=======================================
  Coverage   75.83%   75.83%
=======================================
  Files         115      115
  Lines        1254     1254
=======================================
  Hits          951      951
  Misses        303      303

Impacted Files
Coverage Δ

lib/src/service/entities/media_attachment.dart
100.00% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Config node 4 enhancements

Some speculative changes as discussed in #14. This PR supersedes #14 if it is deemed acceptable.
Changes to Matryoshka were done against the old tests. The sole breakage is that Matryoshka can no longer created without using new. Since this was unused behaviour I went ahead and used a class.
Following those changes, I trashed most of the tests and rewrote them in a more structured way. Hopefully it makes the intended behaviour clearer.

Very clean, thanks! LGTM


TSTL printer plugins do not work if luaBundle compiler flag is enabled

The following is a "hello world" style TSTL plugin:
import * as tstl from "typescript-to-lua";

const plugin: tstl.Plugin = {
    printer(program, emitHost, fileName, ...args) {
        const result = new tstl.LuaPrinter(emitHost, program, fileName).print(...args);
        result.code = `-- Plugin\n${result.code}`;
        return result;
    },
};

// eslint-disable-next-line import/no-default-export
export default plugin;

It works fine on a normal TSTL project, but doesn't do anything if the luaBundle compiler flag is turned on.

This is actually expected behavior: Bundling does not bundle the code fields of result, but instead it bundles result.sourceMapNode, which is not modified in the example we list in the documentation. You will get expected behavior when using the following printer plugin:
import { SourceNode } from "source-map";
import * as tstl from "../../../src";

const plugin: tstl.Plugin = {
    printer(program, emitHost, fileName, ...args) {
        const result = new tstl.LuaPrinter(emitHost, program, fileName).print(...args);
        result.sourceMapNode = new SourceNode(null, null, null, [`-- Plugin : ${fileName}\n`, result.sourceMapNode]);
        return result;
    },
};

// eslint-disable-next-line import/no-default-export
export default plugin;

I think that this is just a bad example from our docs, I will update our docs and tests to use a more realistic printer plugin.

Thank you Perry!

See #1173


Add process registry fields

Looks good to me. You might need to provide maybe some examples of use cases for new fields. And we are good to go. I will raise this PR for discussions in our otel meetings as soon as you will create it in otel repo. We have them Mondays


Immutable.setIn doesn't account for shared object referencing from multiple parents.

I sort of expected this would happen. Is this normal?
I just wished Immutable.setIn(...) was intelligent enough to keep track of cases where multiple parents reference the same object reference within the map tree, and update it along multiple paths up multiple parent chains. Unfortunately, this isn't the case.
http://jsfiddle.net/xryk992o/1/

This won't be expected behaviour as it goes against how persistent data structures work.
There's two problems with the example you provided; The first one is that fromJS just goes through an object or array recursively and converts it to an Immutable.js structure. This means that d will be already duplicated to begin with.
The second problem is that even if d in your structure would be the same shared Map, it would not update when setIn is called on one of its paths.
Consider what happens when you update a value in a persistent Map:
It will get the value at the specified key, then change that data, then set it on the Map, yielding a new instance of Map. Even though that d Map is shared, setIn will go down your path, it will create a new Map, then it will update the parent Maps. At no point does it know about the shared value. This happens because it's persisted, so we are not actually mutating it in-place.

Great answer by @philpl

Is there another library that takes care of shared objects?

@stavalfi if you need shared objects I would recommend using plain JS objects and arrays, using utilities like lodash if necessary. “Shared” objects implies mutability, defeating much of the purpose of keeping values immutable

no mutability here. I use redux to maintain graph changes and I tried to find a library which can update the graph by creating a new graph.
How lodash can help me out here?


After changing email in AppCenter, I can still use my previous email to login

Steps to reproduce:

Create account in https://appcenter.ms/
Change email to another email under you account settings
Logout and login with your new email
Logout and login with your previous email

Expected Result:

Should prevent login with old email and only login with new email

Observed Result:

Successfully logged in and you can use both emails to login to the same account. This is security vulnerability.

*Tried on 3 different PCs and with another user account
Here is video showing how to reproduce.
https://1drv.ms/v/s!AiUG8l584Bi2kihsnZ3jgpM4tMfe?e=ouyaiN

Thanks for the detailed report @androideveloper ! What you're experiencing is a bit unintuitive but currently expected behavior.
Once an App Center account is associated with a given SSO provider's account (i.e. a Google, Facebook, Microsoft, or GitHub account), there is currently no manually way of changing that association.
When you're changing the email address in the App Center user settings, you're simply changing the email address that could in the past be directly used for email & password login to App Center.

@ScottArbeit I've looked through other open issues but didn't find a good match. Better management of linked SSO accounts has been something I wished for for a long time, maybe we want to capture that separately as a feature request?

Thanks for the detailed report @androideveloper ! What you're experiencing is a bit unintuitive but currently expected behavior.
Once an App Center account is associated with a given SSO provider's account (i.e. a Google, Facebook, Microsoft, or GitHub account), there is currently no manually way of changing that association.
When you're changing the email address in the App Center user settings, you're simply changing the email address that could in the past be directly used for email & password login to App Center.

@lumaxis Thanks for the feedback on this issue. Besides being unintuitive I think this is a security vulnerability, because potentially you can change your email many times under the settings and in that case, every new email can be used for signing in to AppCenter later, even if you removed that under the settings.

@androideveloper That's not exactly how this works. Only the currently set email address could be used to directly log in to App Center with a password.
Each SSO account is linked to exactly one App Center account at a time.

@lumaxis In this case we get many SSO to one AppCenter linking. Please find the video showing how to reproduce here https://1drv.ms/v/s!AiUG8l584Bi2kihsnZ3jgpM4tMfe?e=ouyaiN

@androideveloper That's correct and currently by design, as I mentioned. You can have multiple SSO accounts linked to a single App Center account but each SSO account can only be linked to one App Center account and each App Center account only to one Google, Facebook, GitHub, or Microsoft account at a time.
Additionally, what you're showing in the last part of the video is another functionality where, when you login with a given SSO account for the first time, we look up that SSO account's email address in the App Center database and link it to an existing App Center account if it exists with that email address.

New activity, please don't close it bot


Interface raises warning during compilation

 WARNING  Compiled with 1 warning                                     8:01:13 AM

 warning  in<EMAIL_ADDRESS>
Critical dependency: Accessing import.meta directly is unsupported (only property access is supported)

Has been fixed by switching to custom elements in https://github.com/EOX-A/elements/pull/85


Gradle task get stuck trying to acquire a lock

Hi @passy.
We are applying the git-versioner.gradle into our project, and we are facing a problem.
When we run some gradle tasks that makes a call to version.gradle, the build get stuck trying to acquire a lock.
We run the task with the --debug option, I'm sending attached the debug tail, and the exact point the build stops.
Are we doing something wrong? Any clue will be very helpful.
Regards,
Fernando Cesar.
buildLock.txt

@passsy We are also facing the same issue as @fcesar77. For us its Windows. I happened to notice that two git.exe processes are started in the task manager.

It seems it's a gradle problem. What gradle version are you running?
Alternatively see the new plugin. Support for this script will be dropped


Shortcut to copy item for import in PoB, like in trade macro

It would be very nice to have this feature. You press CTRL+C on an item and it copies text ready for import as a custom item in PoB.

Hi, I'm not the dev, but the CTRL + C thing is not a feature from trade macro, is a POE thing. You can do this without any macro or overlay.


[release-4.12] Bug 2172832: CNV-23494 Ssh select load balancer

📝 Description
manual cherry-pick of three prs
https://github.com/kubevirt-ui/kubevirt-plugin/pull/1036
https://github.com/kubevirt-ui/kubevirt-plugin/pull/1043
https://github.com/kubevirt-ui/kubevirt-plugin/pull/1052
Ticket with its two bugs

Ticket with its two bugs

@upalatucci which 2 bugs are related to this PR? Or can you, please, provide the links of all the related tickets/bugs explicitly in the description of the PR? As there is no any clear number in the title. Thanks in advance! :)

#1036 is the feature
#1043 is a second pr that fixes a bug but I've considered it as part of the feature
#1052 is the bug https://bugzilla.redhat.com/show_bug.cgi?id=2168032

@upalatucci Note that we need a BZ ticket to 4.12, if we want to backport a fix done in 4.13 to 4.12.

Okay. The bug was created by the actual feature that I implemented. So backporting the feature means backporting also the bug. I  didn't think about that. But if we need to do that, I'll do it

the bugzilla ticket for the bug backport is this: https://bugzilla.redhat.com/show_bug.cgi?id=2172832

/lgtm

/cherry-pick release-4.11


Leetcode bypass crome extension is not working

Leetcode bypass chrome extension is not working in my chrome browser

#99


README build instructions failed

$ go build -o $GOPATH/bin/rtr
main.go:13:2: cannot find package "github.com/cloudfoundry-incubator/cf-lager" in any of:
	/usr/local/Cellar/go/1.5.3/libexec/src/github.com/cloudfoundry-incubator/cf-lager (from $GOROOT)
	/Users/drnic/Projects/gopath/src/github.com/cloudfoundry-incubator/cf-lager (from $GOPATH)
main.go:14:2: cannot find package "github.com/cloudfoundry-incubator/routing-api" in any of:
	/usr/local/Cellar/go/1.5.3/libexec/src/github.com/cloudfoundry-incubator/routing-api (from $GOROOT)
	/Users/drnic/Projects/gopath/src/github.com/cloudfoundry-incubator/routing-api (from $GOPATH)
commands/list.go:5:2: cannot find package "github.com/cloudfoundry-incubator/routing-api/db" in any of:
	/usr/local/Cellar/go/1.5.3/libexec/src/github.com/cloudfoundry-incubator/routing-api/db (from $GOROOT)
	/Users/drnic/Projects/gopath/src/github.com/cloudfoundry-incubator/routing-api/db (from $GOPATH)
main.go:17:2: cannot find package "github.com/cloudfoundry-incubator/trace-logger" in any of:
	/usr/local/Cellar/go/1.5.3/libexec/src/github.com/cloudfoundry-incubator/trace-logger (from $GOROOT)
	/Users/drnic/Projects/gopath/src/github.com/cloudfoundry-incubator/trace-logger (from $GOPATH)
commands/list.go:6:2: cannot find package "github.com/cloudfoundry-incubator/uaa-token-fetcher" in any of:
	/usr/local/Cellar/go/1.5.3/libexec/src/github.com/cloudfoundry-incubator/uaa-token-fetcher (from $GOROOT)
	/Users/drnic/Projects/gopath/src/github.com/cloudfoundry-incubator/uaa-token-fetcher (from $GOPATH)
main.go:20:2: cannot find package "github.com/pivotal-golang/clock" in any of:
	/usr/local/Cellar/go/1.5.3/libexec/src/github.com/pivotal-golang/clock (from $GOROOT)
	/Users/drnic/Projects/gopath/src/github.com/pivotal-golang/clock (from $GOPATH)

I found the following worked for me:
go get ./...

Did you run ./scripts/update under cf-routing-release before building RTR?

Closing due to inactivity.
@drnic let us know if the instructions are not clear enough on the point that this repo should no be cloned on its own, but as a submodule of cf-routing-release.


ADC Continuous Mode Fails with Mixed Attenuation Values SDK 5.2.2 [BUG] [URGENT] (IDFGH-13072)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Issue: ADC Continuous Mode Fails with Mixed Attenuation Values
Description
I am experiencing a failure when configuring the ADC Continuous Mode using the ESP-IDF. The issue occurs when using two or more different attenuation values in the adc_digi_pattern_config_t pattern array to feed the adc_continuous_config_t configuration. Specifically, the call to ESP_ERROR_CHECK(adc_continuous_config(handle, &dig_cfg)); fails with an error.
Steps to Reproduce
Define a pattern array with multiple ADC channels, each having different attenuation values.
Configure the ADC continuous mode using this pattern array.
Observe that ESP_ERROR_CHECK(adc_continuous_config(handle, &dig_cfg)); fails.
Example Code
`static void continuous_adc_init(adc_continuous_handle_t *out_handle)
{
int EXAMPLE_READ_LEN = 256;
adc_continuous_handle_t handle = NULL;
adc_continuous_handle_cfg_t adc_config = {
    .max_store_buf_size = 1024,
    .conv_frame_size = EXAMPLE_READ_LEN,
};
ESP_ERROR_CHECK(adc_continuous_new_handle(&adc_config, &handle));

adc_continuous_config_t dig_cfg = {
    .sample_freq_hz = 20 * 1000,
    .conv_mode = ADC_CONV_SINGLE_UNIT_1,
    .format = ADC_DIGI_OUTPUT_FORMAT_TYPE1,
};

adc_digi_pattern_config_t adc_pattern[16] = {0};
// Example pattern with different attenuation values
adc_pattern[0].atten = ADC_ATTEN_DB_0;
adc_pattern[0].channel = ADC_CHANNEL_3;
adc_pattern[0].unit = ADC_UNIT_1;
adc_pattern[0].bit_width = SOC_ADC_DIGI_MAX_BITWIDTH;

adc_pattern[1].atten = ADC_ATTEN_DB_2_5;
adc_pattern[1].channel = ADC_CHANNEL_6;
adc_pattern[1].unit = ADC_UNIT_1;
adc_pattern[1].bit_width = SOC_ADC_DIGI_MAX_BITWIDTH;

dig_cfg.pattern_num = 2;
dig_cfg.adc_pattern = adc_pattern;

ESP_ERROR_CHECK(adc_continuous_config(handle, &dig_cfg));
*out_handle = handle;

}
`
Expected Behavior
The adc_continuous_config function should successfully configure the ADC continuous mode even when using different attenuation values in the pattern array.
Actual Behavior
The ESP_ERROR_CHECK(adc_continuous_config(handle, &dig_cfg)); call fails, resulting in an ESP_ERR_INVALID_ARG error.
Environment
ESP-IDF Version: v5.2
Development Kit: [e.g., ESP32-DevKitC]
Module or chip used: [e.g., ESP32-WROOM-32]
Compiler version: [e.g., xtensa-esp32-elf-gcc (crosstool-NG esp-2021r2) 8.4.0]
Operating System: [e.g., Windows/Linux/macOS]
Power Supply: [e.g., USB]
Additional Context
This issue severely limits the use of the ADC continuous mode with channels that require different attenuation settings. It would be helpful to understand if this is a known limitation or if there is a workaround to allow mixed attenuation values in the configuration.
LOG
ESP_ERROR_CHECK failed: esp_err_t 0x102 (ESP_ERR_INVALID_ARG) at 0x400dddbd
0x400dddbd: continuous_adc_init at   main/include/timer_adc_read.c:106 (discriminator 1)
file: "./main/include/timer_adc_read.c" line 106
func: continuous_adc_init
expression: adc_continuous_config(handle, &dig_cfg)
abort() was called at PC 0x40092eb3 on core 1
0x40092eb3: _esp_error_check_failed at C:/Espressif/frameworks/esp-idf-v5.2/components/esp_system/esp_err.c:50
Backtrace: 0x40081b2a:0x3ffcc420 0x40092ebd:0x3ffcc440 0x40099f85:0x3ffcc460 0x40092eb3:0x3ffcc4d0 0x400dddbd:0x3ffcc500 0x40101e33:0x3ffcc590 0x40093b16:0x3ffccf10
0x40081b2a: panic_abort at C:/Espressif/frameworks/esp-idf-v5.2/components/esp_system/panic.c:466
0x40092ebd: esp_system_abort at C:/Espressif/frameworks/esp-idf-v5.2/components/esp_system/port/esp_system_chip.c:93
0x40099f85: abort at C:/Espressif/frameworks/esp-idf-v5.2/components/newlib/abort.c:38
0x40092eb3: _esp_error_check_failed at C:/Espressif/frameworks/esp-idf-v5.2/components/esp_system/esp_err.c:50
So, the Attenuation is not working at all for multiples continous reading at different channel settings.

https://github.com/espressif/esp-idf/blob/master/components/esp_adc/adc_continuous.c#L490-L494
For the same ADC unit, the channels should use the same attenuation config.

https://github.com/espressif/esp-idf/blob/master/components/esp_adc/adc_continuous.c#L490-L494
For the same ADC unit, the channels should use the same attenuation config.

Make no sense, if we need to read it each channel wise, the continous reading doenst work at all, only for a fixed setup unit, so the document shall make this clear.

The driver is not very well designed. The options to set are awkward and do not align with the intended functionality of the requested fields. It seems either the ADC was broken and not properly fixed, or the idea was abandoned before the task was complete.
If the adc_digi_pattern_config_t has a specific field for attenuation for each item added, this makes no sense at all again!


[Bug]: Channel is not usable despite me using the channel multiple times

Describe the bug
this is the status for both CJIT and Regular channels
JC mentioned that it can be due to my connection, since some of the paykit payments we did (to contacts) didn't work from the first time
Reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots / Recording
bitkit_ldk_logs_1716548147054.zip
Operating system
Graphene OS Pixel 6A
Bitkit version
v118
Log output
No response

bitkit_ldk_logs_1716911604567.zip

Note: This error also appears when Bitkit isn't into the background.

Chatting to spiral about this. Peer is not connected which makes the channel unusable. Trying to debug that/

Can't reproduce it with new fix


Creating texture arrays doesn't occur on the CPU, causing the textures to fail to save.

The texture creator uses Graphics.CopyTexture() to perform the copy operation. However, this operation is GPU based and therefore doesn't copy any actual pixel data. Upon restarting Unity, the textures are simply black. This should be fixed.

Fixed in 45adcc82b20b3750e817854232de2cbd68f85e84


prompt_for_user_token parses url incorrectly

When I run this:
import spotipy.util as util
token = util.prompt_for_user_token('MU_USERNAME', scope='user-library-read', client_id='MY_CLIENT_ID',                                    client_secret='MY_CLIENT_SECRET', redirect_uri='http://localhost/')
and insert the url from the browser into the prompt, it incorrectly parses it. The url only had the code value, and not whatever is supposed to come after the &. It worked after I added an & to the end of my url, and I am not sure if this is unique to me, but it seems like this is an error.
I found the url is parsed in oauth2.py line 188, and this is caused because it tries remove everything before the code, and everything after the & (including it), but there was no &.

Idem for me, will try to find another way.

Have the same issue


Add forward ref support

Updates react-docgen to version 4 which has support for forwardRefs. Also added test and modification to actualNameHandler - which I'm hopeful is correct, but not 100% sure.

Let me test this and release. I haven't touched this in a while so I think I will probably bundle some dependency upgrades with this release as well.


 I accidentally implemented Invoke-TraverseDirectory as mirror directory by mistake. Just abort this (but keep the other supporting functions), and start again.

The include parameter of Get-ChildTems is for files only not directories so you'll need to use the filter parameter instead; even given the limitation of only being able to specify a single filter in a single invoke; (which is the reason why I was trying to use include/exclude in the first place)

There's no punt in trying to implement include/exclude functionality, because the condition parameter allows you to perform all the filtering logic you want.

Index logic is flawed, here is the output of the tests in it's current state:
The count is incremented in the test function script block and is correct (except that because its a counter, it is 1 greater that the correct index).
---> Invoke-TraverseDirectory, path: C:\Users\Plastikfan\dev\github\PoSh\Loopz\Elizium.Loopz\Tests\Data\traverse\
  [-] Directory: 'traverse', count: 1, index: '0'
===> Running adapter for 'Audio', _index: 1, PT-INDEX: 1
===> recurseTraverseDirectory, directory: Audio
  [-] Directory: 'Audio', count: 2, index: '1'
===> Running adapter for 'GOTHIC', _index: 1, PT-INDEX: 1
===> recurseTraverseDirectory, directory: GOTHIC
  [-] Directory: 'GOTHIC', count: 3, index: '1'
===> Running adapter for 'Fields Of The Nephilim', _index: 1, PT-INDEX: 1
===> recurseTraverseDirectory, directory: Fields Of The Nephilim
  [-] Directory: 'Fields Of The Nephilim', count: 4, index: '1'
===> Running adapter for 'Earth Inferno', _index: 1, PT-INDEX: 1
===> recurseTraverseDirectory, directory: Earth Inferno
  [-] Directory: 'Earth Inferno', count: 5, index: '1'
===> Running adapter for 'Mourning Sun', _index: 2, PT-INDEX: 2
===> recurseTraverseDirectory, directory: Mourning Sun
  [-] Directory: 'Mourning Sun', count: 6, index: '2'
===> Running adapter for 'The Nephilim', _index: 3, PT-INDEX: 3
===> recurseTraverseDirectory, directory: The Nephilim
  [-] Directory: 'The Nephilim', count: 7, index: '3'
===> Running adapter for 'MINIMAL', _index: 6, PT-INDEX: 6
===> recurseTraverseDirectory, directory: MINIMAL
  [-] Directory: 'MINIMAL', count: 8, index: '6'
===> Running adapter for 'FUSE', _index: 6, PT-INDEX: 6
===> recurseTraverseDirectory, directory: FUSE
  [-] Directory: 'FUSE', count: 9, index: '6'
===> Running adapter for 'Dimension Intrusion', _index: 6, PT-INDEX: 6
===> recurseTraverseDirectory, directory: Dimension Intrusion
  [-] Directory: 'Dimension Intrusion', count: 10, index: '6'
===> Running adapter for 'Train Trac', _index: 7, PT-INDEX: 7
===> recurseTraverseDirectory, directory: Train Trac
  [-] Directory: 'Train Trac', count: 11, index: '7'
===> Running adapter for 'Plastikman', _index: 9, PT-INDEX: 9
===> recurseTraverseDirectory, directory: Plastikman
  [-] Directory: 'Plastikman', count: 12, index: '9'
===> Running adapter for 'Arkives', _index: 9, PT-INDEX: 9
===> recurseTraverseDirectory, directory: Arkives
  [-] Directory: 'Arkives', count: 13, index: '9'
===> Running adapter for 'Consumed', _index: 10, PT-INDEX: 10
===> recurseTraverseDirectory, directory: Consumed
  [-] Directory: 'Consumed', count: 14, index: '10'
===> Running adapter for 'EX', _index: 11, PT-INDEX: 11
===> recurseTraverseDirectory, directory: EX
  [-] Directory: 'EX', count: 15, index: '11'
===> Running adapter for 'Musik', _index: 12, PT-INDEX: 12
===> recurseTraverseDirectory, directory: Musik
  [-] Directory: 'Musik', count: 16, index: '12'
===> Running adapter for 'Sheet One', _index: 13, PT-INDEX: 13
===> recurseTraverseDirectory, directory: Sheet One
  [-] Directory: 'Sheet One', count: 17, index: '13'
===> Running adapter for 'Richie Hawtin', _index: 15, PT-INDEX: 15
===> recurseTraverseDirectory, directory: Richie Hawtin
  [-] Directory: 'Richie Hawtin', count: 18, index: '15'
===> Running adapter for 'From My Mind To Yours', _index: 15, PT-INDEX: 15
===> recurseTraverseDirectory, directory: From My Mind To Yours
  [-] Directory: 'From My Mind To Yours', count: 19, index: '15'

The problem might be because of recurseTraverseDirectory inside of which we perform the function invoke without incrementing the index, which is in contrast to foreachFsItem, which does the invoke then increments. This disjointness needs to be resolved.

The solution proposed in the previous comment, fixed the issue.


Support for new diffuser: flux1.schnell

@sayakpaul
Hello,
I am looking for support for saving and loading the flux1.schnell model from Blackforest.
Following your code from the "Bonus" here
Saving
from diffusers import PixArtTransformer2DModel
from optimum.quanto import QuantizedPixArtTransformer2DModel, qfloat8

model = PixArtTransformer2DModel.from_pretrained("PixArt-alpha/PixArt-Sigma-XL-2-1024-MS", subfolder="transformer")
qmodel = QuantizedPixArtTransformer2DModel.quantize(model, weights=qfloat8)
qmodel.save_pretrained("pixart-sigma-fp8")

Loading
from optimum.quanto import QuantizedPixArtTransformer2DModel
import torch

transformer = QuantizedPixArtTransformer2DModel.from_pretrained("pixart-sigma-fp8")
transformer.to(device="cuda", dtype=torch.float16)

I am looking for a similar option to save and load the two quantized models in this repo here,
see line 38,45,46
transformer = FluxTransformer2DModel.from_pretrained(bfl_repo, subfolder="transformer", torch_dtype=dtype, revision=revision)
quantize(transformer, weights=qfloat8)
freeze(transformer)

and 35,48,49.
text_encoder_2 = T5EncoderModel.from_pretrained(bfl_repo, subfolder="text_encoder_2", torch_dtype=dtype, revision=revision)
quantize(text_encoder_2, weights=qfloat8)
freeze(text_encoder_2)

If I'm correctly understanding this, there would need to be somethin like
from optimum.quanto import QuantizedFluxTransformer2DModel for the transformer
and
from optimum.quanto import T5EncoderModel for the text_encoder_2
to be able to save and load the quantized models for the transformer and encoder. Is that correct? Or is tehre another possibility which avoids importing the quantized version of a model from optimum.quanto?
Thank you!
@sayakpaul

Thanks for the quick answer!
Did it like this:
class QuantizedFlux2DModel(QuantizedDiffusersModel):
    base_class = FluxTransformer2DModel

class QuantizedT5Model(QuantizedTransformersModel):
    auto_class = T5EncoderModel

Do you know if that's the correct way to use it? Or is an additional freeze step necessary between quantization and saving?
# quantizing
print("start loading transformer...")
transformer = FluxTransformer2DModel.from_pretrained(bfl_repo, subfolder="transformer", torch_dtype=dtype)#, revision=revision)
print("start quantizing...")
qtransformer = QuantizedFlux2DModel.quantize(transformer, weights=qint4, exclude=["proj_out", "x_embedder", "norm_out", "context_embedder"])
print("...end quantizing")

# NECESSARY?
freeze(qtransformer)

# saving
print("start saving...")
qtransformer.save_pretrained(f"{bfl_repo}/q_transformer")
print("...end saving")

# loading
qtransformer = QuantizedFlux2DModel.from_pretrained(f"{bfl_repo}/q_transformer")
qtransformer.to(device="cpu", dtype=dtype)

After you quantize, it's not necessary to freeze as you can see it happens within the quantize() call:
https://github.com/huggingface/optimum-quanto/blob/601dc193ce0ed381c479fde54a81ba546bdf64d1/optimum/quanto/models/diffusers_models.py#L114
Rest looks good to me.


Created Testimonial V1 component

Added new HTML & TailwindCSS component mentioned in #160
Preview:

Make the file name testimonials-v1.2.html to avoid conflicts. @udoyhasan

@Rajdip019 done.

Good job @udoyhasan
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


How to install phaser library into this project

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
I am on Mac OSX

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.18
node: 5.11.1
os: darwin x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
it's fresh project generate by CLI, I did

npm install phaser --save
when I do npm install @types/phaser --save-dev, it says
404 Not found : @types/phaser
npm ERR! 404
npm ERR! 404  '@types/phaser' is not in the npm registry.

I want to be able to use Phaser in this project.
The log given by the failure.

Normally this include a stack trace and some more information.
File '/Users/xima40/code/phaser-game/node_modules/Phaser/typescript/typings.json' has unsupported extension.

Mention any other details that might be useful.
Phaser is an html5 game engine

Thanks! We'll be in touch soon.

Can you make a public repo with example proj of this error? That will help narrow down the issue. Also debugging questions may get a faster response if you ask in the https://gitter.im/angular/angular-cli
Thanks! :)

@xinrui-ma you'll have to ask this on gitter or stack overflow. The trouble you're having is with a specific library, and it doesn't seem like it's a CLI bug.

Hi, did you manage to include this library ?

I have not been able to figure this out, other than ejecting webpack and then doing it from there.


fix: #1121 breadcrumb component not routing

Fixed breadcrumb component not routing.

The breadcrumb component now receives the home as a prop, in the primevue breadcrumb component documentation has exemples using the name "route" for the the path but the component it self expects "item.url". Tried using "route" and "path" as the routeItems object key but it did not work, "url" worked though.
https://primevue.org/breadcrumb/

Hi Jota, I think there is an example in the primevue documentation https://primevue.org/breadcrumb/#router, we can follow that. So change the route item "path" to "route".  Also need to change all the places is using ".path"

And update the Breadcrumb component in the frontend/src/components/common/PageTitle.vue file to something like below, it should work. Then we don't have to add additional home props.

Hi Jota, I think there is an example in the primevue documentation https://primevue.org/breadcrumb/#router, we can follow that. So change the route item "path" to "route". Also need to change all the places that is using ".path"
And update the Breadcrumb component in the frontend/src/components/common/PageTitle.vue file to something like below, it should work. Then we don't have to add additional home props. Just a reminder, in this example we might don't need all of it, like some classname, let's just add what we need. Thanks so much!!

route will work if we use the template, but it might broke some styling. I need to check to be sure

Hi Jota, I think there is an example in the primevue documentation https://primevue.org/breadcrumb/#router, we can follow that. So change the route item "path" to "route". Also need to change all the places that is using ".path"
And update the Breadcrumb component in the frontend/src/components/common/PageTitle.vue file to something like below, it should work. Then we don't have to add additional home props. Just a reminder, in this example we might don't need all of it, like some classname, let's just add what we need. Thanks so much!!

"route" or "path" will work using the template , but it will break styling. I need to check to be sure

using the template sintax works with "path" as the routeItems key but will break the styling. Should I make the change and focus on the styling?

Just add a note here, seems like Primevue breadcrumb can get the item.url and make the link works, so we changed "path" to be "url": https://github.com/primefaces/primevue/commit/ad9b437003e0d3ae26047d2cfd1a6a6ecc9037d7#diff-33bf4bb142b615a34557b44002c2eb3ac4393bd3fa4099aede38fabbf4e5527f

Hi Jota, I think there are two more places is using ".path", we have to change them, otherwise like the sidebar navigation is not working

Hi Jota, please check the comment I put in the pr in the common repo, https://github.com/bcgov/nr-theme/pull/155#pullrequestreview-1869058420. We don't need to add these extra custom class, let's remove them, and upgrade to the latest theme package. Thanks!!

Approve. Just wondering if the addition of "$light-focus" in .scss is intended or is a left over?

thanks Ian, just removed


Error connecting to ICOS

Getting below error while connecting to ICOS :
{"message":"read ECONNRESET","stack":"Error: read ECONNRESET\n    at _errnoException (util.js:1022:11)\n    at TLSWrap.onread (net.js:615:25)","code":"NetworkingError","errno":"ECONNRESET","syscall":"read","region":"us-east-1","hostname":"diabos-logo-storage1.s3.eu-gb.cloud-object-storage.appdomain.cloud","retryable":true,"time":"2019-05-16T13:29:07.458Z"}
This works well from local and cloud foundry app but fails when app is deployed on the Kubernetes cluster.

https://cloud.ibm.com/status?selected=status has the status for public cloud issues. It looks like COS hasn't
Are you on an IBM Cloud Kubernetes cluster? If so, you may want to check https://cloud.ibm.com/docs/containers?topic=containers-object_storage for setting up connectivity to COS and also IAM for authentication.
Let me know if you have any more issues.

Yes the services are on Kubernetes and we have the secret created for the object storage service. Also, i forgot to mention that the issue is being seen only for node js based services which used this sdk. The Spring boot and Python implementations are working fine. Issue seems to be with the config object params may be . Config Object details for your reference :
Config Object : ICOS CONFIG : Service { config: Config { credentials: Credentials { expired: false, expireTime: null, serviceInstanceId: 'crn:v1:bluemix:public:cloud-object-storage:global:a/f5ff61f69c044fa6bXXXXXXXXXX7c6d1ac4df575b-1343-488e-8734-7d27625fcc55::', authCallback: undefined, tokenManager: undefined, ibmAuthEndpoint: 'https://iam.ng.bluemix.net/oidc/token', accessKeyId: undefined, sessionToken: undefined, httpOptions: undefined }, credentialProvider: CredentialProviderChain { providers: [Array], resolveCallbacks: [] }, region: 'us-east-1', logger: null, apiVersions: {}, apiVersion: null, endpoint: 's3.eu-gb.cloud-object-storage.appdomain.cloud', httpOptions: { timeout: 120000 }, maxRetries: undefined, maxRedirects: 10, paramValidation: true, sslEnabled: true, s3ForcePathStyle: false, s3BucketEndpoint: false, s3DisableBodySigning: true, computeChecksums: true, convertResponseTypes: true, correctClockSkew: false, customUserAgent: null, dynamoDbCrc32: true, systemClockOffset: 0, signatureVersion: null, signatureCache: true, retryDelayOptions: { base: 100 }, useAccelerateEndpoint: false, apiKeyId: 'Wg_GVf4L8WXXXXXXXXXXXX9HpzaILDn7eV0', ibmAuthEndpoint: 'https://iam.ng.bluemix.net/oidc/token', serviceInstanceId: 'crn:v1:bluemix:public:cloud-object-storage:global:a/f5ff61f69c044XXXXXXXXXXXX75b-1343-488e-8734-7d27625fcc55::' }, endpoint: Endpoint { protocol: 'https:', host: 's3.eu-gb.cloud-object-storage.appdomain.cloud', port: 443, hostname: 's3.eu-gb.cloud-object-storage.appdomain.cloud', pathname: '/', path: '/', href: 'https://s3.eu-gb.cloud-object-storage.appdomain.cloud/' }, _clientId: 1 }

Your configuration looks correct to me. I would go through and double-check your Kubernetes connection settings.
We'll see if we can find anything in the meantime.

Thanks! Bryan..Probably comparing with what is done in Java/Python SDK might help.
Error mentions TLS wrap, so may be related to SSL or something ?

With node version 10.15.1 and npm version 6.8.0 iam now getting the below error -
[2019-05-17T06:02:37.517] [ERROR] ContentManagement-API-Logger - error uploading logo to icos{"message":"read ECONNRESET","stack":"Error: read ECONNRESET\n    at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)","errno":"ECONNRESET","code":"NetworkingError","syscall":"read","region":"us-east-1","hostname":"diabos-logo-storage1.s3.eu-gb.cloud-object-storage.appdomain.cloud","retryable":true,"time":"2019-05-17T06:02:37.516Z"}

Bryan, the issue is resolved now by creating a wildcard service entry for ICOS in the Istio Kubernetes.
However it would be worth comparing the sdks as to why Java/Python works and Node JS doesnt.
Thanks!

Yep. We'll take a look.
If your issue is resolved, would you mind closing this issue?

Okay, closing the issue.

Closing the issue.


Missing initWithCoder: for Storyboard Layout

It would be nice if initWithCoder: was available then it could be included in storyboards. This is related to one of the last comments in issue #2.
Quick gist: https://gist.github.com/semireg/f8168fe7b336723fd406
Also, note the tintColor needs to be set back to nil in viewDidLoad to remain the default blue.

@semireg if you wouldn't mind implementing this in a feature branch and then opening a pull request, that would be awesome.

Fixed with #29.


Updates to JwtSecurityTokens and added unit test

Stop using a temporary table and move to JObject

I can't seem to see the differences. Something is not quite right in this pull request. Could you try again? It's hard to see the differences you want to make.

The last four functions all need to be [External].  I have also removed "Standard Text" as a temporary table (it will not work in all cases) and use JObject instead as the temporary storage for the token claims.

Your suggestions have functions, which have .NET parameters. Those, as you know, cannot be used from V2 extensions. I could not see any other improvements over the code we have in repo. I'm hence closing this pull request without making any changes. Feel free to correct your code and reopen this pull request for further processing.

There are exceptions and this in one of them. This dotnet object has been mapped to AL type and in json management this dotnet type is already external and accessible by Extension V2
Kveðja/Kind regards,
Gunnar Þór Gestsson

From: Jesper Schulz-Wedde<EMAIL_ADDRESS>Sent: Tuesday, October 10, 2017 9:25:56 AM
To: Microsoft/cal-open-library
Cc: Gunnar Gestsson; Author
Subject: Re: [Microsoft/cal-open-library] Updates to JwtSecurityTokens and added unit test (#12)
Your suggestions have functions, which have .NET parameters. Those, as you know, cannot be used from V2 extensions. I could not see any other improvements over the code we have in repo. I'm hence closing this pull request without making any changes. Feel free to correct your code and reopen this pull request for further processing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/cal-open-library/pull/12#issuecomment-335490203, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWd6jQDsDKNIl5ANyFahTNy0As7jWgc3ks5sq35zgaJpZM4Pog69.

I see! Case re-opened :-) We will have to re-triage it! Thanks for clarifying!

Keep in mind that new AL types are not really "mapped" to .NET types. You should treat them as completely new AL types. It will not be possible to call the methods from C/AL Open Library that have DotNet types as part of the signature even though similar types might exist in AL.

Based on Stan's comment, I will close the pull request again, as the suggested code changes won't work for V2 extensions. Feel free to refactor and we'll reconsider! Thanks for all your contributions! They are very much appreciated!

I will refactor and submitt another pull request.  But I suggest you take a look at Codeunit 5459 that has external function using DotNet variable.

 We have a lot of external functions in that codeunit with .NET parameters! That is a mistake! I will investigate how those got there. We probably have to make those functions internal or refactor. Thanks for pointing that out!


Add contributions guidelines

https://github.com/claudiodangelis/qr-filetransfer/blob/master/CONTRIBUTING.md


Add run configuration for all tests

A very simple change, which adds a 'All Tests' run config option for all developers who want to contribute to dartx (and use IntelliJ):

Sure, why not :)


Persistance of position relocations moved to other events to fix issue #1209

This PR fixes issue #1209. Please refer this issue to understand the background of this patch.

I have added an unit test for issue #1209
Moved the persistance of position relocations from onFlush event, which is called before database transaction started, to the first call of postPersist, preUpdate or preRemove. So that the update query is executed within the transaction and if errors happen during queries the position changes will be rolled back.
The synchronization of the objects has been separated from the database persistance, so that it will happen only if all queries were successfully executed (in postFlush).

The only thing I don't like with this solution is, that it will only work with entities that have identifiers. I am not sure if this is a problem.
I had to use these because the INSERTs are executed before the UPDATE query for the relocation of the positions. And that will manipulate the positions of inserted records. But I cannot use another event in this case.
Doctrine lacks an event which is fired between the beginning of a transaction and the inserts :-( This would have made the patch much simpler.

Testing on a live system showed that the shouldSyncPositionAfterDelete did not test if the positions have been persisted correctly. So I have extended the test in 79544ff57c3243843f7969de83eb2f6fa23e9276.
Further I had to move the call to relocation persistance from preRemove to the postRemove event, because preRemove is executed right after calling $em->remove($entity) and not in flush.
I hope it's okay, that I have done that in multiple commits.

Testing on a live system showed that the shouldSyncPositionAfterDelete did not test if the positions have been persisted correctly. So I have extended the test in 79544ff57c3243843f7969de83eb2f6fa23e9276.
Further I had to move the call to relocation persistance from preRemove to the postRemove event, because preRemove is executed right after calling $em->remove($entity) and not in flush.
I hope it's okay, that I have done that in multiple commits.

thanks, that was very useful


Issue #3 fixed

_ No description provided. _

Looks good @Rishav13773  but make submit button aliegn with input field .......but  I am merging it , you can create new PR for one more contribution ....Thank You for contribution  Please give the star to repository


Allow specifying a timezone that :at parameters should be interpreted as

Allows using set :timzone, '' in the configuration file to specify that times in :at should be interpreted as being in the specified timezone and then converted to localtime for writing to cron

require 'active_support/all'

Allows @JamesCropcho 's fix to work for me.

I agree that it makes better sense for scheduled jobs use server time zone, not Rails time zone.
However it's unnecessarily confusing since there's no mention of this in the README, and the examples use Rails time helpers every 1.day, :at => '4:30 am' do to describe scheduling (sort of implying the times will be interpreted per usual Rails implementation.).
I suggest adding a one-liner to the README to say this is how it works.  (And an added benefit is that it might prevent more issues being opened on this same topic.)

This is my schedule.rb which works around the timezone issue, my server is in UTC, my users in CET (with daylight saving time):
require "tzinfo"

env :PATH, ENV["PATH"]

def local(time)
  TZInfo::Timezone.get("Europe/Amsterdam").local_to_utc(Time.parse(time))
end

every :sunday, at: local("7:00 am") do
  rake "make:stuff:happen"
end

every 1.day, at: "1:00 am" do
  command "whenever --update-crontab"
end

nice @jankeesvw, so basically put this somewhere in schedule.rb
require "tzinfo"
def local(time); TZInfo::Timezone.get("US/Pacific").local_to_utc(Time.parse(time)); end

then use:
every 1.hour, at: local('5:30 am') do
  # awesome things here
end

Yes that should work @nathantsoi, but I would rather keep it readable though :sparkles:.

No disrespect to the folks who have kindly shared their solutions, they're certainly better than nothing, but they are really not sufficient for robust time zone support. Take, for example:
require "tzinfo"
def local(time); TZInfo::Timezone.get("US/Pacific").local_to_utc(Time.parse(time)); end
every :sunday, at: local("10 pm") do
  # Start the week
end

This adjusts the time but not the day in cron:
0 5 * * 0 /bin/bash ...

Meaning it now runs at 5am Sunday UTC, which is 10pm Saturday Pacfic. Oops.

Using Rails, you can load the environment:
require File.expand_path('../config/environment', __dir__)

And than get the Rails zone:
every :day, at: Time.zone.parse('04:56am').localtime do
  runner 'My::Job.method'
end


Dev test: molarity 1.5.0-dev.23 (a11y instrumentation)

@zepumph, @emily-phet, @Matthew-phet, @terracoda, @ariel-phet molarity/1.5.0-dev.23 is ready for dev testing.
This sim has been instrumented with sound and PDOM accessibility features.
Document issues in https://github.com/phetsims/molarity/issues and link to this issue.
Assigning @ariel-phet for prioritization.

General Dev Test

What to Test

Click every single button.
If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
If there is a console available, check for errors and include them in the Problem Description.
Rung through the string tests on at least one platform, especially if it is about to go to rc.

General Dev Test Platforms

[ ] Latest macOS, Chrome and Safari
[ ] Latest iOS, Safari
[ ] Windows 10, all browsers
[ ] Latest Chrome OS, Chrome

Link(s)

Simulation

Accessibility (a11y) Dev Test

What to Test

Specific instructions can be found below.
Make sure the a11y feature testing doesn't negatively affect the sim in any way.
Load the a11y view and make sure that interacting with all elements in the simulation updates the appropriate descriptions in the PDOM.

Link(s)

a11y View
Simulation

Screen Readers
This sim supports screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to screen readers. If you simply need a refresher on screen readers, please consult the QA Book, which should have all of the information you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

[ ] Windows 10 + Latest Chrome + Latest JAWS
[ ] Windows 10 + Latest Firefox + Latest NVDA
[ ] macOS + Safari + VoiceOver
[ ] iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in this Google Document. If you find a screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a screen reader.
Final Requests

[ ] If this sim is being tested for a11y we may want to do some testing on Talkback to check on latest behavior of that screen reader. Please comment in the issue asking if Talkback should be tested. See https://github.com/phetsims/a11y-research/issues/144.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Bit confused about this part of the description:

concentration readout range for this solution 0 to 2.250 molar

This information isn't usually available, especially when the sim doesn't have solution values checked, which it doesn't by default.  Can you explain this decision?

@KatieWoe Thanks for the question! I am not sure about this choice, but @terracoda, @Matthew-phet and/or @emily-phet can probably give more insight.

If I could make a suggestion, instead of giving numbers that aren't originally available you could say something like "concentration readout range is very small/moderately sized/large etc."

@KatieWoe, yes, thank you for this question.
@Matthew-phet, @emily-phet and I have discussed how best to describe the concentration readout range several times. And I agree that it does seem odd to include the values when Solution Values is not checked for this single detail. That said, we have considered many aspects of teh descriptions.
We felt we would have to describe a lot of detail about the Solution Concentration bar itself before we would be able to then describe that the coloured section of that bar is a different size for each solute - an in addition describe it in a way that makes sense to a non-visaul user. We felt a big description of the Solution Concentration bar would draw too much attention to it. Playing with the sliders, hearing the provided alerts, and understanding that the solution in the beaker is changing are much more important details.
The learning goals of the sim are to develop an understanding of concentration (molarity), and also discover that each solute has a saturation point.
The description, "concentration readout range for this solution 0 to 0.500 molar" describes the exact range for the potassium permanganate solute without actually calling the max value "0.500 molar" the saturation point. We do not feel we are giving away an answer.
We came to a consensus that it might be more straight forward for a non-visual learner to compare actual numbers in this case. For example, a learner doing a deep exploration might put together that the readout range for Colbalt(II) chloride which is 0 to 4.350 molar is much greater than the readout range for potassium permanganate. That might help them make sense of why they can move the solute slider more before they hear the tinkle sounds and the "Solution saturated" alert.
Our goal, I think, in this case, is to provide an equivalently strong representation of the concept. The concept being that each solute has a different range between zero concentration and max concentration.
Another practice we try to follow in our description designs is to provide the most important or most recently changed information first, wherever possible.
For example, in the Beaker description we provide all the details of the solution first:

volume
solute name
colour
solute amount (and solute name again)
saturation state (when relevant)
concentration level
chemical formula
readout range

It is only at the very end that we provide the readout range.
Another thing to consider is how this description is accessed or delivered to users. The "State Descriptions" are only accessed on-demand while the user is reading. The actual readout range is never provided during interaction. This description is meant to provide the most useful information a user may need if they choose read the entire description of the beaker description.
I hope that puts the description in context a little better.
We could, at some point, provide the concentration readout range information differently, as you have suggested, but I think for now we will stick the numbers.
This description was, indeed, one of our big challenges for this sim.

@KatieWoe Thanks for the good question!
I concur with @terracoda - we spent a lot of time trying negotiate the challenges brought up by the concentration readout...and we settled on the current solution (as @terracoda describes).

Some lag on chromebook, especially on the left slider when particles are involved.  Not too bad.

QA is done

Can this be closed since it is in rc @zepumph


[BUG] We're linking to the old readthedocs docs in several places

Some lightning errors point users to look at a link that doesn't exist anymore (the old docs).
We should change the link in the errors to the appropriate links in the new docs.
Here are several instances referencing readthedocs.
It includes two links to the old installation link in two errors.
These should be changed to this link instead: https://docs.pennylane.ai/projects/lightning/en/stable/dev/installation.html
It also includes the old link in the issue template:

For general technical details check out our documentation:
https://pennylane-lightning.readthedocs.io/

This should be changed to this link instead: https://docs.pennylane.ai/projects/lightning/en/stable

Ahh, thanks @CatalinaAlbornoz for catching these old links!


kubectl diff command output diff informations when patch is failed for statefulset

What would you like to be added?
when statefulset patch is failed, kubectl output the the patch informations, not just output something like
updates to statefulset spec for fields other than 'replicas', 'template', 'updateStrategy' and 'minReadySeconds' are forbidden

Why is this needed?
some  patch information may help user to understand why patch is failed, it is useful when the actual diff is not so obvious

Could you please explain the steps you took to reproduce this?

@Ithrael Hi, here is the example sts, I just change the labels on the volumeClaimTemplates. Apply a1.yaml, and then use kubectl diff -f a1.yaml
a1.yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: myapp
spec:
  selector:
    matchLabels:
      app: myapp
  serviceName: myapp
  replicas: 2
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: myapp
        image: registry.k8s.io/nginx-slim:0.8
        ports:
        - containerPort: 80
          name: web
        volumeMounts:
        - name: www
          mountPath: /usr/share/nginx/html
  volumeClaimTemplates:
  - metadata:
      name: www
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 1Gi

a2.yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: myapp
spec:
  selector:
    matchLabels:
      app: myapp
  serviceName: myapp
  replicas: 2
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: myapp
        image: registry.k8s.io/nginx-slim:0.8
        ports:
        - containerPort: 80
          name: web
        volumeMounts:
        - name: www
          mountPath: /usr/share/nginx/html
  volumeClaimTemplates:
  - metadata:
      name: www
      labels:
        app: myapp
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 1Gi


Add support for barTintColor in NavigatorIOS component. Fixes #387.

Another pull request pending #318 with more stuff.


OCPBUGS-37222: extract rhel9 MCO binaries for rhel8 based MCO images

Dynamically use rhel9 MCO binaries for rhel8 based MCO images
xref https://github.com/openshift/machine-config-operator/pull/4476

/test e2e-aws

/lgtm

/cherry-pick release-4.16 release-4.15 release-4.14


CSV import with creating table

Hi all,
I am re-opening this issue which someone has raised out in year 2017. See [here(https://github.com/dbeaver/dbeaver/issues/2415).
Note that this is not a duplicate of #130
This is to suggest a feature, where dbeaver can import a CSV file, and able to create a new table from it, and automatically import the data in the CSV file into the new table.  It would really be a awesome feature to have.

Hi @hanct ,
this feature is already implemented.
You could choose Import data in context menu e.g. for Table folder (not for a table) and then import CSV to a new table.

Hi, thanks. Maybe know which version implement this? Mine has all the menu items (except import data) based on your screenshot when I right click. I am using dbeaver 6.1.4

it is implemented in 7.2.x version. You could try the recent version - 7.2.3


[Proposal]Doris UNIQUE table supports UPDATE syntax

Background
The current Doris table does not support the update operation, but there are many scenarios where the data needs to be updated. Due to the batch delete function we implemented before, it paved the way for the update.
Syntax
We only support single table update
UPDATE table_name
    SET assignment_list
    [WHERE where_condition]
    [ORDER BY...]
    [LIMIT row_count]

value:
    {expr | DEFAULT}

assignment:
    col_name = value

assignment_list:
    assignment [, assignment].

Design
There are two kinds of updates involved here, one that only contains the value column, and the other that contains the key column.

Include and update of value column
This method is relatively simple. You only need to plan the update statement into a query plan like select * from table insert into table during query planning, and you need to add an update node to modify the data to the updated value, or plan Into a statement similar to select a, b,'xx','xx1' from table insert into table and hand it directly to the tableSink node

Contains the update of the key column
This kind of relatively complicated, we need to divide the query into two parts, and need to use the MERGE semantics in the batch delete, first plan it into a query plan similar to select * from table insert into table, and then generate it first for the modification of the key column One piece of data that needs to be deleted, and then replace the value of the key column to generate new data that needs to be added, mainly generating two pieces of imported data from one piece of original data. Need update node to have the ability to repeat data

Subtasks

Add index to unique table value column to speed up data scanning
FE supports update statements and generates corresponding query plans. Be implements update node, which can be divided into two parts here

Support updates that only contain the value column
Support the update of the key column

背景
当前 Doris 表不支持 update 操作，但是有很多场景需要对数据进行更新，由于我们之前实现的批量删除功能，为实现update 铺平了道路。
语法
我们只支持单表更新
UPDATE table_name
    SET assignment_list
    [WHERE where_condition]
    [ORDER BY ...]
    [LIMIT row_count]

value:
    {expr | DEFAULT}

assignment:
    col_name = value

assignment_list:
    assignment [, assignment] .

设计方案
这里涉及两种更新，一种使只包含value 列的更新， 一种是包含key列的更新

包含及value 列的更新
这种方式比较简单，只需要查询规划时将update 语句规划成类似 select * from table insert into table  的查询规划，并且需新增一个update node，用于修改数据为更新后的值， 或者 规划成 类似 select a, b, 'xx', 'xx1' from table insert into table 的语句，直接交给 tableSink 节点

包含key列的更新
这种相对复杂一点，我们需要将查询分成两部，并且需要用到 批量删除里的MERGE 语义，先规划成类似 select * from table insert into table  查询规划， 之后针对key列的修改，先生成一条需要删除的数据，再替换key列值后生成需要新增的数据，主要将一条原始数据生成两条导入数据。需要update node 有数据重复的能力

子任务

unique 表 value 列加索引，加快数据扫描速度
FE 支持 update 语句，并生成相应的查询规划，be实现update node， 这里可以分为两部

支持只包含value 列的更新
支持包含key列的更新

Great features。
There is another scenario. For example, when using bitmap to calculate UV, it is only cumulative at present. For example, if 100 people have paid the order, UV should be equal to 100. But if 10 people cancel the order, UV should be equal to 90. In this case, bitmap needs to support the reset operation of a bit. This kind of scenario can be considered later to design.

Great features。
There is another scenario. For example, when using bitmap to calculate UV, it is only cumulative at present. For example, if 100 people have paid the order, UV should be equal to 100. But if 10 people cancel the order, UV should be equal to 90. In this case, bitmap needs to support the reset operation of a bit. This kind of scenario can be considered later to design.

Great features。
There is another scenario. For example, when using bitmap to calculate UV, it is only cumulative at present. For example, if 100 people have paid the order, UV should be equal to 100. But if 10 people cancel the order, UV should be equal to 90. In this case, bitmap needs to support the reset operation of a bit. This kind of scenario can be considered later to design.

The need for bitmap update does exist, but what you said may not be a simple syntax like update set bitmap=xxx where xxx.
Is that true?
bitmap 的更新需求确实是一个很重要的场景。不过你说的这类场景并不是 update 语句可以支持的。因为update支持的是列整体的更新，而不是列的数据的局部更新。
或者你知道有哪些其他的系统是支持这个功能的吗？我可以调研一下

Great features。
There is another scenario. For example, when using bitmap to calculate UV, it is only cumulative at present. For example, if 100 people have paid the order, UV should be equal to 100. But if 10 people cancel the order, UV should be equal to 90. In this case, bitmap needs to support the reset operation of a bit. This kind of scenario can be considered later to design.

The need for bitmap update does exist, but what you said may not be a simple syntax like update set bitmap=xxx where xxx.
Is that true?
bitmap 的更新需求确实是一个很重要的场景。不过你说的这类场景并不是 update 语句可以支持的。因为update支持的是列整体的更新，而不是列的数据的局部更新。
或者你知道有哪些其他的系统是支持这个功能的吗？我可以调研一下


Enable Kerberos authentication option in API template

This is listed in the Templating epic with questionmark, so not sure what exactly needs to happen here or how important it is to get it done in 3.0.
There is also tooling impact here. There is no such option in the New Project Dialog UI
This work depends on https://github.com/aspnet/AspNetCore/issues/8897

Talked to @blowdart regarding this. We aren't going to load templates with this. Rather there will be just docs covering enabling this.

Don't forget to enable anti-forgery for the API calls.


Ghasem :student-bio

Student Bio PR
Write a short bio for yourself using Markdown and add it to your class
repository using Local/Remote workflows. Just a little intro so your classmates
can get to know you.

Checklists
General Checks

[ ] the branch is up to date with main/master
[ ] the code works when pulled and run locally
[ ] All CI checks pass
[ ] all conflicts are resolved (if any)
[ ] PR has a descriptive title
[ ] PR has appropriate labels and milestones for easy identification
[ ] PR it is assigned to the owner
[ ] reviewers are assigned
[ ] the PR contributes only one focused change
[ ] It is in the appropriate column in the project board (if necessary)
[ ] has short and clear description
[ ] is linked to an issue (if it is related)
[ ] feedback is addressed (if any and if it is appropriate feedback.)

Markdown

[ ] the markdown source is formatted
[ ] spelling and grammar is correct in all text
[ ] The markdown looks correct when you preview the file
[ ] all links and images work
[ ] any embedded code snippets are formatted

hi @QasemMousavi your md file is empty. you need to write a short bio for yourself. You can use markdown cheatsheet to add headers, links, images, tables etc. Also you can add emojies from here.  after writing your md file and doing format check,you can push to the same branch. Your pull request will update your changes automatically.

Hi, you should practice markdown, while you have added just a title, which is not enough. Maybe this can help you? https://www.youtube.com/watch?v=HUBNt18RFbo

Thank you I will watching the video 🙏


Running with User Seed is Failed

Warning:  Database seeding is turned on
MEAN.JS - Development Environment
Environment:			development
Port:				3000
Database:				mongodb://localhost/jydz-dev
App version:			0.4.1
MEAN.JS version:			0.4.1
Failed to add local user
Failed to add local admin

@blueflagbj Thanks for the bug report! See PR #909. Could you let me know if that fixes your issue?


Many warnings in multiFileOutput

Would it be acceptable to filter them, or is that hiding important information?
if (this._finishedFiles.has(filename) && !this._options.multiFileOutput) {
instead of
https://github.com/glideapps/quicktype/blob/55dc6a7912715b7db45419958bf89d00637cd4cd/packages/quicktype-core/src/Renderer.ts#L308

Hi @relet , could you provide some context on what specific warnings you are seeing ?

The warning mentioned in the code
            `[WARNING] Tried to emit file ${filename} more than once. If performing multi-file output this warning can be safely ignored.`

I don't remember exactly what I was seeing, but if you explicitly select multi-file output, it would be sufficient to show it once (if there really is anything to warn about) or suppress it if it can be ignored.


Users can create, read, update, and delete data for a pizza's comment in the database

As a user, I want to be able to see what pizza has been created on the site and how many existing comments it has

As a user, I want to be able to leave a comment on a pizza that has been created

CRUD for comments complete


Implement a simple ODE solver

The last implementation detail is an ODE solver to solve our differential equation.
Goal:

Implement an ODE solver that takes various parameters and propagates a given state for a well-defined time step.
Ideally, the solver is adaptive.
Implement a propagation scheme that takes an initial state, an equation, a from and to time and works as a generator similar to range, returning the wave function at the individual time steps.

Not sure how inefficient the current scheme is; the scipy integrator takes quite a bit of massaging.
Added time-dependence, as this was already a lot of work now and would only become worse
added a simple logging function that outputs some data about the wave function


CommandSystem: free all commands on shutdown

Partiall frees some cvar leaks:

https://github.com/DaemonEngine/Daemon/issues/885

It looks like all cvars spawn a command, those commands are never freed.
This only partially fixes the problem because:

I assume the engine will not free commands created from cvars created by games between each game restart.
We may have to track down all game-created cvars to free all of them between games.
Cvar code is still leaking a lot beacause CvarProxy code is leaking a lot too.

This doesn't help. The command map is already freed by global destructors. And still nothing is done to free the commands themselves.

Neither cvar commmands nor VM commands, nor old-style engine commands actually allocate a new command object. So few if any commands should be leaked.

Then why valgrind and heapusage reports me thousands of leaks for those?

This patch divides by 2 the size of the heapusage log: from 12M it goes down to 6M. File size is a bad metric, but with such obvious difference there should be something going on.

Are you setting common.pedanticShutdown? Global destructors don't run unless you set that.

Are you setting common.pedanticShutdown? Global destructors don't run unless you set that.

Yes, looking for leaks without it would be impossible otherwise.

Maybe your toolchain has a bug with not destroying function-local static variables.

My test process is the following:
$ ( heapusage ./daemon -set common.pedanticShutdown on 2>&1 ) | tee "heapusage-$(date '+%Y%m%d-%H%M%S').log"
] devmap plat23
] quit
$ vim $( ls -t heapusage-*.log | head -n 1 )
/heapusage

Unlike valgrind, heapusage puts the summary and the highest leak at the top.
I build and run a Debug build with nexe vms (to not be polluted by possible game leaks).

 This:
static CommandMap* commands = new CommandMap();

Ought to be this:
static CommandMap commands;

So in conclusion there is no real memory leak. It's just a pedantic cleanup issue, which you could fix by making the above change.

I get the same with GCC 12.2.0 and Clang 15.0.7.

static CommandMap commands;

This seems to work.


Spacing issue with search bar

I'm submitting a ...

[X] bug report
[ ] feature request

What is the current behavior?
There is an unneeded spacing between the bottom of the search bar and the top of the search suggestions.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Type in the search bar and look how far down the search suggestions are

What is the expected behavior?

There should be no unneeded spacing between the two elements.

Please tell us about your environment:

Version: Current Commit 25e4b0223b062c0ca59a916f593d8e7580408997
Browser: All
Date: 8/29/23

Possible Solution

javascript and fix it underneath the search bar.

Fixed bb3fca476ed625db152b4fd450acf59c03a28a26


Certificate Signing Request Issuer CA

What this PR does / why we need it:
This PR adds an optional CertificateSigningRequest CA issuer. The controller is only enabled if it is explicitly done so via the --feature-gates flag (i.e. --feature-gates=ExperimentalCertificateSigningRequestControllers=true)
This begins the work to integrating kubernetes CertificateSigningRequests as part of cert-manager. (ref #3646).
Users who request a certificate referencing a namespaced issuer, must have permissions to do so in the following form:
group: cert-manager.io
resource: signers
verb: reference
namespace: <referenced signer namespace>
name: <either the name of the signer or '*' for all signer names in that namespace>

A SubjectAccessReview is performed during processing to check whether the user has sufficient permissions to reference the Issuer encoded into the signer name.
Special notes for your reviewer:
This work is based on the design in #3646
Release note:

Adds an option for a Kubernetes CertificateSigningRequest controller to implement the CA Issuer.

/cc @munnerz

flake
/retest

/test pull-cert-manager-e2e-v1-21

Thanks @SgtCoDFish @irbekrm
I have addressed your comments in the latest commit or responded. Good for another review and (hopefully) merge :slightly_smiling_face:

/assign @irbekrm @SgtCoDFish

/test pull-cert-manager-e2e-v1-21


Clean up confirmation code in unsubscribe and email change pathways.

Merged, after tweaking it to remove the unnecessary zulip_login_required.


[8.x] Register macros with Mail::fake() in tests

Hi! This PR adds the functionality for macros to be re-registered for the MailFake class during tests.
I've added this because I have a macro that is registered for my Mail in the AppServiceProvider. But it seems that when I was trying to write a test that involved the macro being used, the test kept failing with the following message:
Error : Call to undefined method Illuminate\Support\Testing\Fakes\MailFake::myMacro()

With this PR, when we call Mail::fake(), any of the macros already registered for the Mail facade will be re-registered. Hopefully, this means that we can then write the rest of the test as normal to assert that an email was sent.
Apologies if I've approached this from a completely wrong angle and there's a better way to solve it :)

What does your macro do? I worry this will really not be a permanent solution to this problem because your macro could interact with protected properties of the mailer that are not present on the MailFake class.

Yeah that's a fair point, I had a feeling that might have been the case. I don't think I can send over the snippet of code that's being used because it's from a project I'm working on for another company. So, I don't want to risk breaching any non-disclosure agreements; because the code was already in there before I started working on the project.
But I can tell you that the macro is changing the domain on the SwiftMailer. So you could run something like:
Mail::domain('my-domain-here')
   ->to('email-here)
   ->send(new MailableHere());

The macro's using $this->getSwiftMailer(), but I've just had a quick look and it looks like that would fail with my changes; like you say.
Maybe I just need to change my approach to the tests and mock the facade instead of using the assertions in the MailFake?

Possibly... or, what I would probably do is put all that mail interaction behind some other class... let's just pretend it's App\Services\InvoiceMailService... have a method on there like sendInvoiceNotification. Then, just mock and inject App\Services\InvoiceMailService and make assertions against the methods that were called on it.

Yeah that makes sense actually and would probably be the easier solution in the long run. Thanks for the suggestion, appreciate it!
😄


Http Content-type header field missing on *.mjs files

Should be the same as in *.js files (eg application/javascript; charset=UTF-8).
The content-length field is missing as well.

The former is an issue for mime@1 https://github.com/jfhbrook/node-ecstatic/blob/master/package.json#L29 . Also, you should be able to add your own content-types with the mimeTypes option.
The second would be a pretty egregious but unrelated bug which really really should not be happening--and if it were, it would be a specific edge case most likely not related to mime types. You should investigate this further and send a separate bug report if you can suss this out for sure.

The mjs type is already registered: https://github.com/broofa/node-mime/blob/v1.4.0/types.json

ok, well, this should definitely work then, same as any other content type. Something much stranger is going on.

What command are you running? Do you have a repro case I can try to stand up locally?

I am using https://www.npmjs.com/package/http-server

OK, I don't support http-server.
If you can get this to reproduce with ecstatic's included cli command, then we can re-open.

With the CLI I get content-type:application/octet-stream on one file (my .mjs module), but content-type:application/javascript; charset=UTF-8 on my main.mjs

The module loaded via import ... from './....mjs'; has the wrong content type. .mjs files loaded via script tag do not.

@jfhbrook

I need a full repro case. I need actual files with actual path locations and a cli command for spinning up ecstatic.


Python training and test example

@KaimingHe
thanks for putting this repo and repo together. its great to see this coming along quickly.
my request is if you could please post a simple Python example script for running training and testing on a sample mini data set (say 5 object classes of 50 images each), it would be really great to get going.
this would straightaway help address all the unknowns with setting the right parameters for training.
also if you could publish a train_val.prototxt, it would help.

I'm also looking for a train_val.prototxt -- thanks!


[4.2] Clarify that LightmapGI is not supported in compatibility renderer

https://github.com/godotengine/godot/pull/88406 but targeted at the 4.2 branch

The documentation currently does not mention that LightmapGI rendering is not supported in the compatibility renderer. It only states the fact that baking it is not supported (thus it is possible to make an assumption that rendering it is supported, while baking isn't).

And I am to assume this could be cherrypicked to 4.1 as well?

Thanks!

Cherry-picked for 4.1.4.


Add bookmark indexes to breaking changes docs

Fixes #15995

Close/reopen.

Humm, build doesn't seem to link the anchors


Perf: only log latest commit

This limits the output of git log to only show 1 commit instead of the entire history of commits. In my unscientific testing, this resulted in a 33% performance increase on a very large site (10,000+ pages)

please accept pull request asap - this is a small but great improvement

Thanks!


FATAL Flags parsing error: Unknown command line flag 'db_preset'. Did you mean: preset ?   i need help

run:
python3 run_docker.py --fasta_paths=test.fasta --max_template_date=2021-11-01 --data_dir=/mnt/rhd/database/data_set
err:
/opt/conda/lib/python3.7/site-packages/absl/flags/_validators.py:206: UserWarning: Flag --preset has a non-None default value; therefore, mark_flag_as_required will pass even if flag is not specified in the command line!
'command line!' % flag_name)
FATAL Flags parsing error: Unknown command line flag 'db_preset'. Did you mean: preset ?
Pass --helpshort or --helpfull to see help on flags.

There was the recent API change where the preset flag in run_docker.py was split into db_preset and model_preset.
Is there a possibility that you are running v2.0.0 version of the model with v2.1.0 version of the Docker scripts?
We would suggest making sure that you are updated to the latest release, and then passing db_preset and model_preset flags following the README or run_docker documentation (they have sensible defaults too): https://github.com/deepmind/alphafold/blob/be37a41d6f83e4145bd4912cbe8bf6a24af80c29/docker/run_docker.py#L59-L67

I will close the issue now, but please feel free to re-open it if this did not help!


Correctly detect array access and binary operator side effects

Closes #981 (expression never executed if it was in a return statement of a generic function when the result was not stored anywhere)

Cool, well done.