WIP: [MM-42068] Adding source query param to team and channel group endpoints

Summary
Adding group_source to the query parameters in order to filter out custom groups
Ticket Link
https://mattermost.atlassian.net/browse/MM-42068
https://mattermost.atlassian.net/browse/MM-42070
Release Note

Fixes a bug where custom groups were appearing in the UI when linking groups to channels/teams

Should a test case be added to verify that custom groups are no longer included in the response?

There's a test on server to verify that the endpoint returns groups based on that query param, so I think we're good

Discovered an issue so need to add another part to this

@mkraft & @mylonsuren This needs a re-review, had to adjust the redux selectors

/cherry-pick release-6.5


fix(bigquery): use default values

Default values of these fields are empty strings.
BQ API doesn't accept empty strings, according to documentation these fields are enums.
location is not enum according to documentation, but it works similar - only valid location is accepted.

This change is

/gcbrun

/gcbrun

I fixed one unit test, so I hope now all checks should pass.

/gcbrun

I fixed formatting.

/gcbrun

I close this PR as it fixes the issue only partially.
Full fix (making the library smart enough to populate json with only required values) is going to take too much time. It can be done in future.


align with Python for Scicomp

https://aaltoscicomp.github.io/python-for-scicomp/
add link to this lesson

much alignment probably not needed, but refer to parts of scicomp material as good preparatory material for this material

maybe we use https://aaltoscicomp.github.io/python-for-scicomp/ as prerequisites


upup: unusual bug when deleting ASG

autoscaling-group:kubernetes.master.eu-west-1a.kubernetes-e2e-upup-aws.awsdata.com      error deleting resource, will retry: error deleting autoscaling group "kubernetes.master.eu-west-1a.kubernetes-e2e-upup-aws.awsdata.com": ValidationError: AutoScalingGroup name not found - AutoScalingGroup 'kubernetes.master.eu-west-1a.kubernetes-e2e-upup-aws.awsdata.com' not found

I guess this is the "already deleted" message.

Also it then looped seemingly infinitely...

Should have been fixed by #101


Hack: split from PHP, use LSP

hh_client and hackfmt do not operate on PHP files; Hack should be considered a separate language
hh_client now has lsp support (hh_client lsp) and is the preferred way to integrate with editors; this includes code formatting support, so the separate hackfmt support might not be neccessary
HHAST 3.27.2+ have LSP support, providing additional linting for Hack files; vendor/bin/hhast-lint --mode lsp --from w0rp/ale (https://github.com/PranayAgarwal/vscode-hack/blob/master/src/LSPHHASTLint.ts for a full implementation - that prompts for user confirmation first, so that opening the editor doesn't execute project-supplied code)

From what I've seen, I think filetype is still set to php for Hack, so the filetype is appropriate. What might work is only running Hack linters on PHP code when the file extension matches known extensions for Hack files.
Feel free to create pull requests for all of the above.


Hotfixes for some SonarQube issues

In particular, I fixed the issues introduced by the MapReduce tests I added (and the changes to the MapReduce implementation I made). I also fixed the outstanding blocking and critical issues because they were trivial to fix.
@mihaic, what triggers SonarQube? I can see a "delta since previous analysis", can we also get this delta between arbitrary points in time?

SonarQube is triggered by the Jenkins job that tests commits to the master branch.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.tribler.org//job/Graphalytics_pull_request_tester/20/
Test PASSed.


Add real-esrgan ncnn and real-cugan

Great idea this project!
I was wondering if it's possible to add also real-esrgan ncnn and real-cugan ncnn?
What do you think?

I'm planning to write similar bindings for real-cugan. Might as well write them for real-esrgan.
These bindings will probably be added as a separate repo


How to append many2many in a bulk update using a loop

I'm trying to add a user to thousands of accounts.
assoc := db.Debug().Model(&m).Association("Accounts")
assoc.Append(accounts)

..this failed due to the number of place holders being exceeded.
So I made a loop to iterate over the accounts and chunk update them:
func (m *User) AddAccounts(db *gorm.DB, accounts []*Account) {
	chunkSize := 100
	for i := 0; i < len(accounts); i += chunkSize {
		end := i + chunkSize
		if end > len(accounts) {
			end = len(accounts)
		}
		assoc := db.Debug().Model(&m).Association("Accounts")
		assoc.Append(accounts[i:end])
	}
}

I have two issues:

the accounts are being readded to the DB even tho the models were pulled from gorm
the data in each loop is being appended to the last chunk.  So the updates get bigger and bigger:

1st iteration
[1.619ms] [rows:200] INSERT INTO `accounts_users` (`user_id`,`account_id`) VALUES (148,50),(148,51),(148,52),(148,53),(148,54),(148,55),(148,62),(148,63),(148,2571),(148,2572),(148,2573),(148,2574),(148,2575),(148,2576),(148,2577),(148,2578),(148,2579),(148,2580),(148,2581),(148,2582),(148,2583),(148,2584),(148,2585),(148,2586),(148,2587),(148,2588),(148,2589),(148,2590),(148,2591),(148,2592),(148,2593),(148,2594),(148,2595),(148,2596),(148,2597),(148,2598),(148,2599),(148,2600),(148,2601),(148,2602),(148,2603),(148,2604),(148,2605),(148,2606),(148,2607),(148,2608),(148,2609),(148,2610),(148,2611),(148,2612),... etc

2nd iteration
[1.619ms] [rows:200] INSERT INTO `accounts_users` (`user_id`,`account_id`) VALUES (148,50),(148,51),(148,52),(148,53),(148,54),(148,55),(148,62),(148,63),(148,2571),(148,2572),(148,2573),(148,2574),(148,2575),(148,2576),(148,2577),(148,2578),(148,2579),(148,2580),(148,2581),(148,2582),(148,2583),(148,2584),(148,2585),(148,2586),(148,2587),(148,2588),(148,2589),(148,2590),(148,2591),(148,2592),(148,2593),(148,2594),(148,2595),(148,2596),(148,2597),(148,2598),(148,2599),(148,2600),(148,2601),(148,2602),(148,2603),(148,2604),(148,2605),(148,2606),(148,2607),(148,2608),(148,2609),(148,2610),(148,2611),(148,2612),...etc

I'd expect the 2nd iteration to start from the second set of values and not include the first iteration data.
I have tried using Omit to stop the account being created, but this doesn't do anything and also used transactions to encapsulate the association but this fails to work.
How do I stop the accounts being added and also get the chunking to work?
This is fairly easy to reproduce:
Create a function which iterates an array of models and appends them to the model.

Use Append with slice
assoc := db.Debug().Model(&m).Association("Accounts")
assoc.Append(accounts)


Create test cases

This task is a component of User Story #37
Description
Package some of the generic tool methods into the test suite

Started creating more test cases on July 2nd when package was exported to PyPi

This issue should have been closed with #57


Missing overlay (like in qr_code_scanner)

It would be nice to have the possibility to customize the view with an overlay, like in the predecessor package

If you're just looking for an UI overlay, you can add one yourself like so:
            child: Stack(
              children: [
                MobileScanner(
                  allowDuplicates: false,
                  controller: controller,
                  onDetect: onDetect,
                ),
                //overlays a semi-transparent rounded square border that is 60% of screen width
                Center(
                  child: Container(
                    width: MediaQuery.of(context).size.width * 0.6,
                    height: MediaQuery.of(context).size.width * 0.6,
                    decoration: BoxDecoration(
                      color: Colors.transparent,
                      border: Border.all(color: Colors.white38, width: 4.0),
                      borderRadius: const BorderRadius.all(Radius.circular(24.0)),
                    ),
                  ),
                ),
              ],
            ),

Temp Solution https://github.com/juliansteenbakker/mobile_scanner/issues/250#issuecomment-1209723708

This is now possible with version 3.0.0. Please see the example app for an example.


Need to know what Data Entity has the information indicating if a worker is a time registration worker or not

[Enter feedback here]
Please provide the Data Entity that contains this time registration status (Yes/No? Something else?) Need to load thousands of records and need to know what Data Entity and what Field holds the information to indicate if a worker is time registration worker or not.

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

ID: a5dba412-dd58-e872-f935-71d0f3edf5c1
Version Independent ID: edfaef7a-1b8e-a0a3-ee25-d0c307711970
Content: Time and attendance registration overview - Supply Chain Management | Dynamics 365
Content Source: articles/supply-chain/production-control/time-attendance-registrations.md
Service: dynamics-365-supply-chain
Product: ****
Technology: ****
GitHub Login: @johanhoffmann
Microsoft Alias: johanho

Please contact Microsoft Support for your issue. To contact Support, consider one of the options described here: Support contact options.


chore(deps): use caret for restify and redis versions

The current version doesn't allow for use with the latest restify and fails to install on node 0.12.x
This pr uses caret versions for restify and redis.

Thank you. Now available on npm as 1.1.1 version.


Add method to generate string of all 1st order relations within class that aggregates relations

This will be used to display first order relations in person card.
e.g.

Caribou (UUID)
Address: ...
Number: ...
Relations (1st order):
father of Bob
friend of Bob
child of Bob

Closing as this will be part of UI update


TictacAAE fullsync - need for further safety measures

In part related to https://github.com/basho/riak_kv/issues/1765.  When testing of intra-cluster AAE with very large vnodes, and large deltas (either due to genuine deltas or false deltas when awaiting cache repairs) then the behaviour of Tictac AAE was neither efficient or sufficiently conservative.
Some of the measures related to intra-cluster AAE, will also lead to improvement in inter-cluster AAE (such as active pruning of the AAE runner queue).  However, there still exists the risk that inter-cluster AAE behaviour may not be predictable, conservative or efficient in the face of large deltas with large stores.
Following changes proposed:

Update the NextGenREPL doc to make the explicit the potential need for operator intervention to use aae_fold repl_keys_range to resolve large deltas, rather than wait for this to be resolved via fullsync. Currently this fullsync method is optimised for reconciliation (i.e. confirming no deltas) and resolving small deltas.  Deltas of <10K may take an unexpected length of time to resolve.

Update the NextGenREPL doc to make explicit that the participate_in_coverage option should be used when recovering a crashed node, if using TictacAAE fullsync.  by disabling coverage participation for a crashed node until the tree caches have been built - it will prevent excessive work due to false deltas before the cache rebuilds have completed.

Allow the max_results and scan_timeout on AAE exchanges to be configurable for those prompted by inter-cluster AAE, just as they are for intra-cluster AAE.

Backoff further in the riak_kv_ttaaefs_manager gen_server when a previous exchange completes but ends in the state waiting_all_results (the state is returned to the gen_server via the reply function), given that this state as a final state indicates that the exchange did not complete (and probably due to timeout).

Change the default configurations to be more friendly to repair than reconciliation (e.g. in large clusters reconciling every 15 minutes per node is fine, but repairing at that frequency is likely to lead to backlogs).

After further investigation, some issues have arisen.

There is a fundamental bug in the per-bucket full-sync.  There is conflicting view in Riak between the external and internal clients on the format of a modified range - {date, Low, High} or {Low, High}.  This isn't handled correctly in riak_kv_ttaaefs_manager, and so the modified range was being ignore on the local client.

The behaviour of fetch_clocks for clock_compare is different between full fullsync (e.g. nval based) and partial fullsync (e.g. bucket based).  This difference isn't an immediate problem, but perhaps increases the potential for confusion in the long term.  Currently nval fetch_clocks will use the aae_runner for each vnode query, and attempt to re-write the segments (potentially correcting) in the tree cache as it runs through the query.  the per-bucket alternative uses the AF3_QUEUE riak_core node_worker_pool, and does not re-write/repair segments.

The nextgenrepl_ttaaefs_manual riak_test has been extended to catch (1) - https://github.com/basho/riak_test/pull/1352.  A fix has been tested, as well as a switch to control the behaviour for (2) - https://github.com/basho/riak_kv/pull/1776.

If the intention is not to repair tree caches as part of fetch_clocks when running full ttaaefs fullsync, then it becomes easier to consider supporting a schedule that includes hour and day syncs.
In an hour or day sync, a complete comparison would be made between the AAEtree caches, but in the hour sync it will assume any delta was in the last hour of changes (by modified date).  likewise the day sync will assume any delta is in the last day of changes.
These fetch_clocks queries can then be run with a last-modified-date range, and on very large stores this will be much faster than a full nval compare.

https://github.com/basho/riak_kv/pull/1776


Create Swap two numbers

Swapping two numbers

Sure it will
On Sun, 4 Oct 2020, 13:49 Vishruth Subramanian<EMAIL_ADDRESS>wrote:

Closed #62 https://github.com/Vishruth-S/CompetitiveCode/pull/62.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Vishruth-S/CompetitiveCode/pull/62#event-3837333119,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARH2YYLKRLXJ5KWXIBVV6PDSJAVXZANCNFSM4SDPO3CQ
.


Vouching dynamics discussion

This is an issue for discussing vouching-related matters
1- How do we feel toward someone vouching for their own version? Is it expected to happen, something we want to incentivise...?
2- Given a user that is locked on a version that "just works" for him, what are his incentives to move his vouching onto a new, better version, so development moves forward and is promoted?
3- Is there any chance for a malicious player to propose different versions in a progressive manner, making people stake their ZEP in different ones to “divide and conquer”, allowing this player to send a final version and stake his now-majority of tokens?

1-I don't think this is a problem per se. I would just assume that anyone with confidence in their proposal will stake their own.
2-Security I think is the primary incentive, but it may be wise to assume that not many are qualified to assess security. Could you maybe delegate your stake to someone else? I.e. I could initially delegate my stake to Zeppelin as I trust them to ensure the system works properly. A "subscription" also solves this to a degree I think.
3-This could be an issue, but it does assume that a) they have managed to lock up a majority of tokens and b) no one moves their stake to this new proposal. In general, how are you guys thinking about the time delay from staking? Even if a was true, over time tokens would probably move to the newest proposal, so when is a proposal actually "accepted"?

A malicious actor might be incentivized to do that in a bad version if they've found a vulnerability in the OS that they can exploit where the collective value of the vulnerability of all the things built on top is worth much more than the amount required to stake (could be the entire supply of ZEP theoretically if the OS becomes big enough such that many ecosystems are built on top). This problem needs to be solved, but I agree with Teemu above given typically the collective should move things along much faster.

I think you might actually have the opposite free rider problem where most people prefer to delegate their stake to a more knowledgeable authority so it's not decentralized, because there is a cost to making a judgement on which version is better, and if you delegate your vote, you get to minimize your cost while still piggybacking off of the benefits. An interesting mechanism might be to charge someone to delegate their vote rather than letting them do it for free, that might also have negative impacts on adoption of staking in general, so maybe it's something you do tied to a certain condition.

People should be able to see how much that person has staked proportionate to all these different versions no?

I think this is okay and expectable. It happens in open-source.

I don't think this is a scenario that will happen. A user who's only interest is in using the platform and not taking part in the governance process won't be vouching for the version he's using in the first place, given that it can be used for free. I don't think artificially incetivizing users to take part in governance when they wouldn't do so organically would yield high quality decision making.

I think the amount of capital required to achieve this in the master branch would be significant enough that this won't be an issue. Smaller forks won't do as well though.


RFC: killing and un-killing safety procedure

Describe the solution you'd like
We're about to merge #172 where to arm the throttle stick needs to be down. Now as we fly, if we panic and kill it and then land, the throttle stick will be not at the zero position. Then, to fly again we'll un-kill it and... boom! At the same time, if while flying, we kill it by mistake we want to be able to un-kill immediately - without start-up routines. Here's an idea: we introduce a timer (~3s) and once killed for 3s, the throttle stick has to be at zero to un-kill.

@jamie-54 I guess this can be addressed in Python, right? We shouldn't have to change anything in the ESP32 code.

At the minute part of its addressed on the ESP32 if you are free I can show you


HortonWorks Cloudbreak default HDFS as Azure WASB tries rebalancing datanode data to HDFS (0% capacity) on decommissioning and fails

Configured Azure WASB storage as a default HDFS location through Cloudbreak, which had made Hadoop local HDFS capacity as 0 in Ambari (100 % utilized). I have default replication as 1 but now when I am trying to decommission a node, datanode tries to rebalance some 28KB of data to another available datanode. However, our HDFS has 0 capacity and therefore, decommissioning fails with below given error:
New node(s) could not be removed from the cluster. Reason Trying to move '28672' bytes worth of data to nodes with '0' bytes of capacity is not allowed
Getting the information on cluster shows that default local HDFS is still used for some KB space which is getting rebalanced whereas available capacity is 0:

CBD Version: 1.16.x
HDP Stack: 2.5
Hadoop Version: 2.7.3
"CapacityRemaining" : 0,
 "CapacityTotal" : 0,
 **"CapacityUsed" : 131072,**
 "DeadNodes" : "{}",
 "DecomNodes" : "{}",
 "HeapMemoryMax" :<PHONE_NUMBER>,
 "HeapMemoryUsed" : 147668152,
 "NonDfsUsedSpace" : 0,
 "NonHeapMemoryMax" : -1,
 "NonHeapMemoryUsed" : 75319744,
 "PercentRemaining" : 0.0,
 "PercentUsed" : 100.0,
 "Safemode" : "",
 "StartTime" :<PHONE_NUMBER>502,
 "TotalFiles" : 1,
 "UpgradeFinalized" : true,

There is an ambari decommissioned jar used by Cloudbreak to check, if local HDFS space is running out of space. Can we look into this and have a fix, if default FS is not local HDFS.
if (remainingSpace < safetyUsedSpace) {
    throw new BadRequestException(
            String.format("Trying to move '%s' bytes worth of data to nodes with '%s' bytes of capacity is not allowed", usedSpace, remainingSpace)
    );
}

HDP default configuration had calculated non-HDFS reserved storage "dfs.du.datanode.reserved" (approx 3.5 %) on total disk for the lowest storage configured for a datanode (among the compute config groups) which had three drives and one drive was in TBs. Our default configuration to store data on datanode "dfs.datanode.data.dir" was pointing to a drive with lowest capacity (around 3 % of overall DN storage). This 3 % < 3.5 % had made HDFS capacity as 0% and our existing datanode storage had some supporting directories and files in KBs which had resulted in marking negative KB capacity of the datanode. To fix the downscaling issue, either, we need to lower down non hdfs reserved capacity (lower than 3 %) or point our datanode to higher disk capacity (greater than 3.5 %).


Layout of primal networks incorrect

Any ideas how to fix this @wangzhao0217 and @anisotropi4?

See issue rendered here: https://nptscot.github.io/networkmerge/paper.html#fig-knots
Source code:
https://github.com/nptscot/networkmerge/blob/a37df483a922345e06f165fa0329dfc1e4472ac7/paper.qmd#L924-L934

You may be able to fix this by combining the two statements into one chunk prefixed with
#| layout-ncol: 2

or however those comments are formatted

Will give it a go, thanks Josiah..


issue #7671 : Updated main.go new.go

Notes for Reviewers
This PR fixes #
Signed commits

[x] Yes, I signed my commits.

Hello  @RickDeb2004 would like to know what you are working

@RickDeb2004 Can you update this open PR to tell us what does this PR do?
While we can see the files changes, we want to ensure that whomever is reviewing can gain some understanding of what they are reviewing on this PR.
Also can you update your PR to fix the lint errors as well?

yes I will

review : #7746
here I have given a brief description
@Philip-21 @nebula-aac

@RickDeb2004 Refer https://github.com/meshery/meshery/pull/7746#issuecomment-1567373400
Closing PR due to an absence of relevant changes. Feel free to open another one


The links to download the Object Detection Models are broken

When selecting the 'Model' option from the Model Zoo (Faster RCNN and RetinaNet), all options say 404 - File not found

您的邮件已经收到。我会及时做出回复。


Alternative hosting to bintray for art-conpose

JFrog have announced bintray is going away
I currently upgrade Artifactory Pro using this script
https://bintray.com/jfrog/run/art-compose
Where will this script be found after bintray is no longer available?

This version of Docker Compose (for 6.x) has been deprecated for a while. I would recommend upgrading to the Docker Compose for  7.x (https://jfrog.com/download-jfrog-platform/). If you need to stay on 6.x, you can still do that, you can find that exact script in this GitHub repository. You may need to modify the compose.yml to reference the new location for images ( releases-docker.jfrog.io/jfrog/artifactory-pro:) but otherwise the new location has no actual impact on how this script works.


How to make a readonly property in service?

I am trying to implement the MPRIS interface, and some of the properties have to be marked as readonly. How can I do this?
In this example, a property is defined as readonly by whether it has just a getter, or a getter and setter function, but it is using a different dbus library (Shouqun's), which requires libdbus. Is there a similar method in your library?

Hi! The code that handles Get/Set property is here - https://github.com/sidorares/node-dbus/blob/master/lib/stdifaces.js#L110-L120 ( note that the code here is not very finished )
I think what you need is ability to report properties in introspection data. Currently it is generated automatically and the code is here: https://github.com/sidorares/node-dbus/blob/master/lib/stdifaces.js#L152-L192
Note that properties are always readwrite atm. What do you think would be the best way to express this when you describe object?

in https://github.com/sidorares/node-dbus/blob/master/examples/service/server2.js#L26
Could be
 var exampleIface = {
    name: 'com.example.service',
    methods: {
        doStuff: ['s', 's'],
        timesTwo: ['d', 'd'],
        respondWithDouble: ['s', 'd']
    },
    signals: {
        testsignal: [ 'us', 'name1', 'name2' ]
    },
    properties: {
       TestProperty: 'y',  // default: readwrire
       ReadProperty: [ 's', 'read' ], // if array, second argument is access as per http://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format
       WriteProperty: [ 's', 'write' ] // first parameter is property signature
    }
};

wdyt?

That was what I was thinking. It seems like the only way to avoid breaking
too many things. I'm thinking that there should also be support for saying
"readwrite", even if that is the default, and redundant. e.g
testproperty: ['y', 'readwrite'].
I know that often I like to explicitly define things like this, even if
there is an implicit option. The code is more readable, and I and others
could understand it more easily when looking over it later
On Thu, Jul 16, 2015 at 7:33 PM Andrey Sidorov<EMAIL_ADDRESS>wrote:

in
https://github.com/sidorares/node-dbus/blob/master/examples/service/server2.js#L26
Could be
var exampleIface = {
name: 'com.example.service',
methods: {
doStuff: ['s', 's'],
timesTwo: ['d', 'd'],
respondWithDouble: ['s', 'd']
},
signals: {
testsignal: [ 'us', 'name1', 'name2' ]
},
properties: {
TestProperty: 'y',  // default: readwrire
ReadProperty: [ 's', 'read' ], // if array, second argument is access as per http://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format
WriteProperty: [ 's', 'write' ] // first parameter is property signature
}
};
wdyt?
—
Reply to this email directly or view it on GitHub
https://github.com/sidorares/node-dbus/issues/89#issuecomment-122144201.

--
--Abe White

That was what I was thinking. It seems like the only way to avoid breaking
too many things. I'm thinking that there should also be support for saying
"readwrite", even if that is the default, and redundant. e.g
testproperty: ['y', 'readwrite'].
I know that often I like to explicitly define things like this, even if
there is an implicit option. The code is more readable, and I and others
could understand it more easily when looking over it later

I'd prefer to keep it backwards compatible if possible and I'll leave 'signature' to be the same as ['signature', 'readwrite' ] though I agree with you
I'll try to make those changes over weekend ( feel free to look at the code and try to change it as well )

Sure I agree with that. I'm just saying that the default will still be readwrite, but you can also explicitly say that, using the new format. Everything would stay backwards compatible, you just have two ways of  saying readwrite, one explicit, one implicit.
e.g
testproperty: 'y'    //still works, is readwrite
and
testproperty: ['y', 'readwrite']     //functionally the same, just more verbose


Added 'unique' option to make items in Sortable list unique

Revised version of earlier PR, merged to Dev.

Alas, I will not accept it.
It looks like a "crutch/hack" and overall not clear why it is needed.

Hey there.
I have two lists of items, List A and List B. List A contains a master list (eg. A list of users) and List B is a group to which said users might be long. When pulling a user from List A to List B, I want to make sure that there is no chance of duplication, as it makes no sense to have the same user/userID exist multiple times within the list. This PR makes it possible to make sure that the user is unique and that it doesn't have unexpected visual effects when dragging and dropping the same user a second time. Where this is particularly important is when you have multiple groups listed at the same time, so List C, List D and List E are all groups as well, and so I can't just disable the user in List A.
Does this make sense?

You can filter the list by using the events:
  - start
  - move
  - end
  - add
  - update
  - sort
  - remove
This is enough to solve your problem.


[2510] - Add Request ID support to MCBE

Context
When a request comes in, add the value of the X-Request-ID to the logs, and ensure this value gets sent to the MCBE. This so we can track a requests journey through the system.
Changes proposed in this pull request

Add RequestStore gem to store the request id safely (in a manner that is thread-safe)
Log the request id
Add the request id to the headers when making backend API requests

NB: Pull request on the back end is required to make this work
Kibana-rama
You can see the request id is now being tracked across the front and back end.

Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Add Request ID support to MCFE

 Add Request ID support to MCFE


Sign pdf with password may corrupt file

Hi
edit: I did a test with a non-empty password and I got the same result. Checking now endesive-2.0.5
edit2: Probably related to: pdf signing will not work correctly when only owner password is set for the pdf and the permission settings will be ignored by cms.sign
I use your nice library to sign automatically generated pdfs. Unfortunately sometime I run into problems.

The pdf is gererated using enscript and ps2pdf
Then I use qpdf --encrypt "" "" 128 --extract=n --accessibility=n --modify=none to apply some restrictions but without any password
Then I use your pdf-sign-cms.py script to sign the pdf

The unfortunate outcome is that sometimes my pdf reader asks for a password, even none is set. pdfcrack told me that the password is ''. But this works only for qpdf with the option --password-is-hex-key.
x:~$ qpdf --decrypt --password="" --password-is-hex-key /media/sf_shared_folder/TEST_encr-signed-cms.pdf x.pdf
WARNING: /media/sf_shared_folder/TEST_encr-signed-cms.pdf (offset 458): error decoding stream data for object 3 0: stream inflate: inflate: data: incorrect header check
WARNING: /media/sf_shared_folder/TEST_encr-signed-cms.pdf (offset 458): stream will be re-processed without filtering to avoid data loss
qpdf: operation succeeded with warnings; resulting file may have some problems

Attached are the files for the steps above:

TEST_unsec.pdf
TEST_encr.pdf
TEST_encr-signed-cms.pdf

The used version is endesive-2.0.2.tar.gz

Test procedure:
To reproduce the strange behaviour the following sh script may help.

generation of a dummy ps file
loop until decrypt failed
create pdf from ps --> the pdf files differ from step to step, timestamp?
use qpdf for encryption
sign pdf
try to decrypt file with given password

#!/bin/sh
set -e

enscript SignTest.txt  -o SignTest.ps

RESULT=0
counter=0
while [ $RESULT -eq 0 ]
do
  ps2pdf SignTest.ps SignTest_unsec_${counter}.pdf
  qpdf --encrypt "" "" 128 --extract=n --accessibility=n --modify=none  \
          -- SignTest_unsec_${counter}.pdf SignTest_encr_${counter}.pdf

  python3 pdf-sign-cms.py SignTest_encr_${counter}.pdf

  qpdf --decrypt --password="" SignTest_encr_${counter}-signed-cms.pdf /tmp/test.pdf
  RESULT=$?
  echo "decrypt result ${RESULT}"
  counter=$((counter+1))
  echo "Loop counter ${counter}"
done

My run stops after #4. #3 was still valid.
SignTest_unsec_3.pdf
SignTest_encr_3.pdf
SignTest_encr_3-signed-cms.pdf
SignTest_unsec_4.pdf
SignTest_encr_4.pdf
SignTest_encr_4-signed-cms.pdf
Does anyone have an idea??

I don't know what to do about it, pdf with blank password is not supported by pdfreader and PyPDF used in endesive does not support this situation.

It's not restricted to blank password! I just replaced the blank passwords in the script above and pdf-sign-cms.py with '1234' and it still fails.

#!/bin/sh
set -e
#enscript SignTest.txt  -o SignTest.ps
cp pdf.pdf
SignTest.pdf
SignTest_encr_0.pdf
SignTest_encr_0-signed-cms.pdf
SignTest.pdf
RESULT=0
counter=0
while [ $RESULT -eq 0 ]
do
#ps2pdf SignTest.ps SignTest_unsec_${counter}.pdf
cp SignTest.pdf SignTest_unsec_${counter}.pdf
qpdf --encrypt "1234" "1234" 128 --extract=n --accessibility=n --modify=none
-- SignTest_unsec_${counter}.pdf SignTest_encr_${counter}.pdf
vpython3 pdf-sign-cms.py SignTest_encr_${counter}.pdf
qpdf --decrypt --password="1234" SignTest_encr_${counter}-signed-cms.pdf /tmp/test.pdf
RESULT=$?
echo "decrypt result ${RESULT}"
counter=$((counter+1))
echo "Loop counter ${counter}"
done
decrypt result 0
Loop counter 1
decrypt result 0
Loop counter 2
decrypt result 0
Loop counter 3
decrypt result 0
Loop counter 4
decrypt result 0
Loop counter 5
decrypt result 0
Loop counter 6
decrypt result 0
Loop counter 7
decrypt result 0
Loop counter 8
decrypt result 0
Loop counter 9
decrypt result 0
Loop counter 10
decrypt result 0
Loop counter 11
decrypt result 0
Loop counter 12
Everything looks fine  with "1234" as password

Not on my side
$ sh test.sh
[ 1 page * 1 copy ] left in SignTest.ps
SignTest_encr_0.pdf
decrypt result 0
Loop counter 1
SignTest_encr_1.pdf
decrypt result 0
Loop counter 2
SignTest_encr_2.pdf
decrypt result 0
Loop counter 3
SignTest_encr_3.pdf
decrypt result 0
Loop counter 4
SignTest_encr_4.pdf
decrypt result 0
Loop counter 5
SignTest_encr_5.pdf
SignTest_encr_5-signed-cms.pdf: invalid password

$ sh test.sh
[ 1 page * 1 copy ] left in SignTest.ps
SignTest_encr_0.pdf
decrypt result 0
Loop counter 1
SignTest_encr_1.pdf
decrypt result 0
Loop counter 2
SignTest_encr_2.pdf
decrypt result 0
Loop counter 3
SignTest_encr_3.pdf
decrypt result 0
Loop counter 4
SignTest_encr_4.pdf
decrypt result 0
Loop counter 5
SignTest_encr_5.pdf
decrypt result 0
Loop counter 6
SignTest_encr_6.pdf
SignTest_encr_6-signed-cms.pdf: invalid password

$ sh test.sh
[ 1 page * 1 copy ] left in SignTest.ps
SignTest_encr_0.pdf
decrypt result 0
Loop counter 1
SignTest_encr_1.pdf
decrypt result 0
Loop counter 2
SignTest_encr_2.pdf
decrypt result 0
Loop counter 3
SignTest_encr_3.pdf
decrypt result 0
Loop counter 4
SignTest_encr_4.pdf
decrypt result 0
Loop counter 5
SignTest_encr_5.pdf
decrypt result 0
Loop counter 6
SignTest_encr_6.pdf
decrypt result 0
Loop counter 7
SignTest_encr_7.pdf
decrypt result 0
Loop counter 8
SignTest_encr_8.pdf
decrypt result 0
Loop counter 9
SignTest_encr_9.pdf
decrypt result 0
Loop counter 10
SignTest_encr_10.pdf
SignTest_encr_10-signed-cms.pdf: invalid password

???
decrypt result 0
Loop counter 34
^CTraceback (most recent call last):
KeyboardInterrupt
What is your endesive version?
Please try the git version.

$ pip3 list
Package                Version
---------------------- --------------------
...
endesive               2.0.5
...

And the used pdf-sign-cms.py:
#!/usr/bin/env python3
# *-* coding: utf-8 *-*
import sys
import datetime
from cryptography.hazmat import backends
from cryptography.hazmat.primitives.serialization import pkcs12

from endesive.pdf import cms

# from endesive.pdf import cmsn as cms

# import logging
# logging.basicConfig(level=logging.DEBUG)

def main():
    date = datetime.datetime.utcnow() - datetime.timedelta(hours=12)
    date = date.strftime("D:%Y%m%d%H%M%S+00'00'")
    dct = {
        "aligned": 0,
        "sigflags": 3,
        "sigflagsft": 132,
        "sigpage": 0,
        "sigbutton": True,
        "sigfield": "Signature1",
        "sigandcertify": True,
        "signaturebox": (567, 703, 517, 785),
        "signature_img": "document-certificate.png",
        "contact": "xxxx",
        "location": "xxxx",
        "signingdate": date,
        "reason": "Test signing",
        "password": "1234",
    }
    with open("SignTestCrt.p12", "rb") as fp:
        p12 = pkcs12.load_key_and_certificates(
            fp.read(), b"1234", backends.default_backend()
        )
    fname = "x.pdf"
    if len(sys.argv) > 1:
        fname = sys.argv[1]
    print(fname)
    datau = open(fname, "rb").read()
    datas = cms.sign(datau, dct, p12[0], p12[1], p12[2], "sha256")
    fname = fname.replace(".pdf", "-signed-cms.pdf")
    with open(fname, "wb") as fp:
        fp.write(datau)
        fp.write(datas)

main()

And the Subject/Issuer Names in the p12 file contain unicode characters (ä/&/...).

Aha, saw the difference. Try to run it with ps2pdf inside the loop. I noticed that ps2pdf generates every time a different pdf file.

https://www.pdf-online.com/osa/validate.aspx - shows that everything is ok
https://demo.verapdf.org/ - shows errors
:( I have mixed feelings


Fix MPI for multi-threading

In conda-forge, scotch has been compiled with SCOTCH_PTHREAD, so either MPI_Init() must be called with MPI_THREAD_MULTIPLE, or MPI_Init_thread() must be called. At import time, mpi4py initializes the MPI execution environment calling MPI_Init_thread(). mpi4py must be imported before petsc4py otherwise petsc4py initializes MPI with MPI_Init().


Raise destroy events for trains

I found an issue with another mod (described here: https://github.com/robot256/MultipleUnitTrainControl/issues/13) which led me to notice that this one doesn't raise events when a train is destroyed. Hence this quick little PR :)
No sure if it's worth raising the destroy event elsewhere. My sense of the rules is you call destroy when:

Destroying an entity you didn't create
Destroying an entity that you created with raise_built

but I don't actually know :smile:

The docs don't explicitly say, but I found a forum thread that indicates that scripts don't raise on_destroyed by default. It seems a weird decision to me but it is what it is. https://forums.factorio.com/viewtopic.php?p=437433#p437433


Remove version check, as we depend on LiberTEM v0.11+ anyways

Contributor Checklist:

[ ] I have added or updated my entry in the creators.json file
[ ] I have added a changelog entry for my contribution
[ ] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases

Reviewer Checklist:

[ ] /azp run libertem.libertem-live-data passed

/azp run libertem.libertem-live-data


Holoscan SDK Response-Time Analysis

Scripts and paper artifact for timing analysis of Holoscan applications.


Fixing moving file to folder

Hi,
This PR fix a bug that create sub-folders when you move a file to a another folder.
Case: "I want to move the image to dealerships folder."
Image and actual folder:

Destination:

Explaining actual action
This action will create a folder called 'planilhas' and inside of this folder will create 'dealerships' folder, then it will move the file to this directory, therefore, the path of image will be '/planilhas/planilhas/dealerships/image.png/'. But, the correct should be '/planilhas/dealerships/image.png/'. As we can see on images below:
The folder 'planilhas' created:

The image's final path:

After applying this PR:
Correct image path:

So, as we can see on breadcrumb, the path of image after this PR is '/planilhas/dealerships/image.png' as showed on the select option (second image).
Anything else, I'm available to answer.

This works for me and I can't detect any problem!

@fletch3555 Any news?

I'm still not really liking that path, but if it works, I'll allow it.  I fully expect it to cause some kind of issue once released.

@fletch3555 but this path: /.//l7a0l6M2OU99o25Ey2kMMGTESVH4spJNA92Y5968.jpeg is generated by the voyager code, not by my change.

I understand that, which is why I'm merging it.

@fletch3555 oh ok, thanks for that.


Allow authorised users to change an investment project to any stage

Description of change
This PR adds a new investment project permission can_change_to_any_stage_investmentproject and a new endpoint v3/investment/<uuid:pk>/update-stage. Users with this permission will be able to update the stage of the investment project freely, so can move from any one stage to any other stage, through a patch request to this endpoint. This request will bypass any field validation checks.
The status of the project is also be updated if the current or new stage is 'won'.
Currently the investment verification team can change a project's stage in Django admin, whereas this change will allow them to make these changes in the front end and reduce the number of people who need access to Django admin.
There is currently a permission can_change_stage_to_won which allows only the verification team to move an investment project from verify win -> won. Once this change is released, and the relevant users have been assigned the new permission, can_change_stage_to_won will no longer be needed and will be removed.
Checklist

[x] If this is a releasable change, has a news fragment been added?

Explanation
A news fragment is required for any releasable change (i.e. code that runs in or affects production) so that a corresponding changelog entry is added when releasing.
Check changelog/README.md for instructions.

[ ] Has this branch been rebased on top of the current develop branch?

Explanation
The branch should not be stale or have conflicts at the time reviews are requested.

[x] Is the CircleCI build passing?

General points

Other things to check

Make sure fixtures/test_data.yaml is maintained when updating models
Consider the admin site when making changes to models
Use select-/prefetch-related field lists in views and search apps, and update them when fields are added
Make sure the README is updated e.g. when adding new environment variables

See docs/CONTRIBUTING.md for more guidelines.

@reupen I've made the changes requested, let me know what you think.


Advanced Mapping: Enable & Convert to Advanced Mapping

Super quick how to turn on AM. This is the info on doing the mapping: #81
https://powerofus.force.com/s/article/NPSP-Enable-Convert-Advanced-Mapping#ariaid-title2
https://docs.google.com/document/d/1cCGTlVmfKIv_BFGNM8A7oewHXMK4CWz7Z-OKdj1iTn0/edit?usp=sharing

@Billflorio instead of combining this with setting up the mapping (#81), how about adjusting this script to be more:

Intro about AM (https://powerofus.force.com/s/article/NPSP-Advanced-Mapping-Overview)
Enabling AM (https://powerofus.force.com/s/article/NPSP-Enable-Convert-Advanced-Mapping)
When to Customize Advanced Mapping (https://powerofus.force.com/s/article/NPSP-Map-Using-Advanced-Mapping#ariaid-title2).
Lead into the next video about customizing AM.


Questions about Rancher Service Discovery + Labels

Hello,
I just prepared an initial release of Cowhand, a Rancher Catalog integration of Prometheus, InfluxDB, Grafana, and Alertmanager. It comes with cadvisor & node-exporter to provide monitoring of nodes.
For that, I created prom-rancher-sd, a service discovery bridge to allow Prometheus to autodiscover Rancher services which should be monitored.
I've got some questions about the Rancher metadata service:

Is this the best interface for me to use to get this data? One reason I am thinking something better might be available is that I am polling the interface. Is there a Consul-like 'long lived request' notion so changes can be pushed? Right now between my polling interval (30s) and Prometheus' polling interval (30s) it could be up to a minute from the time a service shows up in the interface to the time the service is monitored.

How expensive are rancher metadata requests, and how distributed is the load of those requests? Would polling more frequently be (in)advisable?

What are the consistency semantics and how will this interface behave under various failure conditions? For instance, during a network split, will I continue to see services on the other side of the split? The thing with combining Monitoring + automatic service discovery is that it's important to understand when a service might automatically stop being monitored.

Currently a service registers to be monitored by providing a com.danieldent.cowhand.prom.port label on the service. The service is automatically labelled with the instance set to the 'hostname' parameter, and the stack, service, and instance name are assigned labels as well.

Things I'm currently thinking about:

Providing an additional label where people can specify key-value pairs for labels they want added to the monitoring.
Automatically adding the host labels from the host a service is running on.
Making use of other container/service/stack labels.

I'd appreciate your feedback on what would might make sense to implement, as well as any other suggestions you could offer.

We will probably add a push method but polling metadata is fine.  There is a value at GET /2015-12-19/version which changes when the metadata does, so you can poll that and only look at other stuff when you see it change (rather than watching many different keys).  There is also the regular API and a WebSocket socket that sends a frame every time a resource changes if you want to subscribe to the firehose instead of polling.

You're talking to a process in the Network Agent on the same host as the requesting container and it has all the metadata in memory.  Our external-dns service polls the version every second.

Metadata changes are pushed from the rancher/server to the host agents.  So agents that are no longer connected to the server won't see any changes.  Service health checks are run on 3 hosts (different ones than the target container is on, if $num_hosts >= 4) and pushed to the server, which would then update metadata when the health state changes.

I don't think there's a great answer for how to tell if you're on the wrong side of a split, because metadata won't be getting updated anymore and there's not a key for anything like the last time it was known to be current.  You might be better off talking to the API directly here and watching host/service/container state and healthState.

Thanks for the detailed answer, this is extremely helpful!

@DanielDent If you have more questions, please open a new issue!


Create tada.php

What does the program do ?
Breaks a string by delimiter and joins back to get the string without delimiter
In what programming language it is written?
PHP

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


ERROR: No matching distribution found for manopth==0.0.1

when I try to create a env by env.yaml， I occurred the following error:
`Installing pip dependencies: - Ran pip subprocess with arguments:
['/home/jishengyin/anaconda3/envs/minimal-hand-torch/bin/python', '-m', 'pip', 'install', '-U', '-r', '/home/jishengyin/Minimal-Hand-pytorch/condaenv.fk2wa14o.requirements.txt', '--exists-action=b']
Pip subprocess output:
Collecting git+https://github.com/hassony2/manopth.git (from -r /home/jishengyin/Minimal-Hand-pytorch/condaenv.fk2wa14o.requirements.txt (line 10))
Cloning https://github.com/hassony2/manopth.git to /tmp/pip-req-build-slgj4_k1
Collecting art==3.7
Using cached art-3.7-py2.py3-none-any.whl (485 kB)
Collecting chumpy==0.70
Using cached chumpy-0.70.tar.gz (50 kB)
Collecting coverage==4.5.3
Using cached coverage-4.5.3-cp37-cp37m-manylinux1_x86_64.whl (204 kB)
Collecting einops==0.3.0
Using cached einops-0.3.0-py2.py3-none-any.whl (25 kB)
Pip subprocess error:
Running command git clone -q https://github.com/hassony2/manopth.git /tmp/pip-req-build-slgj4_k1
ERROR: Could not find a version that satisfies the requirement manopth==0.0.1
ERROR: No matching distribution found for manopth==0.0.1
failed
CondaEnvException: Pip failed
`
my computer is ubuntu 22.04 LTS , pip version is 24.0
Could you tell me the reason to my problem?Thanks

it come from this repo. check if your could fix the bug with offical guide


(GH-442) Eliminated Whitespace across all files

A couple files also had mixed CR/LF and LF, I defaulted these to use
the Windows default

@gep13 thanks for your contribution :+1:


[Assembly] Better asm parsing.

Implement improved asm parsing and error messages.

Currently, there is a need for push instructions that accept integers, doubles , ptrs and labels but, this makes them a very different type of instruction from all the others. In any case, this is actually needed and needs to be implemented preferably using an 'elegant' solution.

Done. Closing.


fix: custom rfox reward address display

Description
If you add a custom reward address to rfox, it's not displayed
Since we introduced a copy button, we know see an empty copy button:

We should display the actual address instead

Issue (if applicable)

closes #7694
Risk
Low

High Risk PRs Require 2 approvals

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

Testing
On rFOX:

Try with a native wallet to see if you have the multi account selector
Add a custom address, it should be replaced by the address chosen
Add an address from one of the owned account, the select account component should be back
Try with metamask with snap
Try with a SAFE wallet through wallet connect

If you add a custom address, you should see the address as a badge and with an ellipsis:

Engineering
n/a

Operations
n/a

[ ] :checkered_flag: My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)
https://jam.dev/c/a1d58a21-bce8-4e00-985d-70fc4946a9cb

Tested locally, confirmed this does what it says on the box:
https://jam.dev/c/7b79745e-b9db-4c29-b9d0-e7632a7fd598
Noticed two bugs while testing this however:

When having a custom RUNE rewards address, it is impossible to continue without manually inputting said address again. This is confirmed to be a bug against develop, though safer, as the previous behaviour for multi-accounts was automagical <AccountDropdown /> select, which would change the user's reward addy
When having a custom RUNE rewards address, the <AccountDropdown /> does not display for multi-accounts wallet, neither in Stake nor Change Address. We should let the users toggle between Use Custom Address or Use Wallet Account (though happy to have this one done in a follow-up)

Talked with the product team:
If a user already has a stake:

On the stake view, show the reward address as readonly mode, change the "Use custom address" link to "Change address" and redirect to the change address tab on click
-- On the change address tab, let the dropdown displayed as usually and custom address input, we don't care anymore about the preselected address

If the user didnt stake yet, show the actual component


Cache-Control no-store Returns Excessive Resources In Response with _include and _revinclude URL Params

When searching for an EpisodeOfCare resource by specifying _id=<ID> and also including _include=* and _revinclude=* as search parameters, along with the header "Cache-Control":"no-store", the Server is returning all of the EpisodeOfCare resources in the Server, rather than just the one that was specified by id.
When issuing the same search, but without the header "Cache-Control":"no-store", only the 1 requested EpisodeOfCare resource is returned, and this is the expected behaviour with the first search as well.
To reproduce the problem, run the test:
ca.uhn.fhir.jpa.provider.dstu3.ResourceProviderDstu3Test.testUrlSearchWithNoStoreHeader()

The first query - without the header - returns the following info in the logs:
2021-05-21 14:31:03.718 [main] INFO  c.u.f.r.c.i.LoggingInterceptor [LoggingInterceptor.java:82] Client request: GET http://localhost:56355/fhir/context/EpisodeOfCare?_id=ECC19005O3&_include=*&_revinclude=*&_format=json HTTP/1.1
2021-05-21 14:31:15.597 [qtp88492568-25] INFO  c.u.f.j.search.builder.SearchBuilder [SearchBuilder.java:918] Loaded 0 _revincludes in 1 rounds and 2 ms for search 20c7421d-2395-41e0-a274-14c365dc198c
2021-05-21 14:31:15.598 [qtp88492568-25] INFO  c.u.f.j.search.builder.SearchBuilder [SearchBuilder.java:918] Loaded 3 _includes in 1 rounds and 1 ms for search 20c7421d-2395-41e0-a274-14c365dc198c

The second query - with the additional header - enters a different area of the code in the class ca.uhn.fhir.jpa.search.SearchCoordinatorSvcImpl.executeQuery(), where it adds a large number of additional PIDs to be retrieved (see Line 537). It returns the following in the logs:
2021-05-21 14:31:51.492 [main] INFO  c.u.f.r.c.i.LoggingInterceptor [LoggingInterceptor.java:82] Client request: GET http://localhost:56355/fhir/context/EpisodeOfCare?_id=ECC19005O3&_include=*&_revinclude=*&_format=json HTTP/1.1
2021-05-21 14:35:00.769 [qtp88492568-26] INFO  c.u.f.j.search.builder.SearchBuilder [SearchBuilder.java:918] Loaded 3 _includes in 1 rounds and 1 ms for search (synchronous)
2021-05-21 14:35:01.719 [qtp88492568-26] INFO  c.u.f.j.search.builder.SearchBuilder [SearchBuilder.java:918] Loaded 30 _revincludes in 1 rounds and 3 ms for search (synchronous)

When issuing the first query, the loadSynchronousUpTo on Line 326 is null, so the code bypasses that if block and continues down to the bottom of this method.
In the second query example, the presence of the header "Cache-Control":"no-store" causes the if block mentioned above to be entered (because loadSynchronousUpTo is now set to 100) and the call to executeQuery() on Line 328 is executed instead.

Query 1 returns 1 EpisodeOfCare resource.
Query 2 returns 34 EpisodeOfCare resources.
The ONLY difference between Query 1 and Query 2 is the presence of the header "Cache-Control":"no-store" in Query 2.
The expectation is that Query 2 would also return 1 EpisodeOfCare resource.
Sample Query 1:
curl -X GET "http://localhost:8000/EpisodeOfCare?_id=ECC19005O3&_include=*&_revinclude=*&_count=300"
Sample Query 2:
curl -X GET -H "Cache-Control: no-store" "http://localhost:8000/EpisodeOfCare?_id=ECC19005O3&_include=*&_revinclude=*&_count=300"


bug(mat-sidenav): focus trapping is too aggressive under certain conditions

Reproduction
This issue seems to manifest under the following conditions:

Sidenav is open in over or push mode (does not happen in side mode).
Backdrop is disabled (this is necessary to be able to click in the content area of a over or push sidenav.
App is using the ConfigurableFocusTrap (does not happen with the deprecated FocusTrap).

Steps to reproduce:
https://stackblitz.com/edit/angular-avy29p?file=src%2Fmain.ts

click to focus the "Content" input

Expected Behavior
"Content" input remains focused.
Actual Behavior
"Drawer" input immediately steals focus.

For the record: much conversation took place on https://github.com/angular/components/pull/21962 related to this issue


Warning being triggered for cases unrelated to referenced C++ Core Guideline

The referenced guideline advises against:
void f(int n)
{
    auto p = new Gadget{n};
    // ...
    delete p;
}

Because it can simply be achieved by:
void f(int n)
{
    Gadget g{n};
    // ...
}

Yet the warning is being triggered by the following (the example in the doc):
void unpack_and_send(const frame &f)
{
    auto buffer = std::make_unique<char[]>(f.size()); // C26414
    f.unpack(buffer.get());
    // ...
}

This makes no sense, because applying the guideline here means doing something the language doesn't support:
void unpack_and_send(const frame &f)
{
    char buffer[f.size()];
    f.unpack(buffer);
    // ...
}

Furthermore, if the example is meant to trigger C26414, why doesn't the following (which is even closer to the guideline's example) trigger it?
void unpack_and_send(const frame &f)
{
    auto buffer = new char[f.size()];
    f.unpack(buffer.get());
    // ...
}

The above instead triggers C26409 which explicitly advises using std::make_unique for dynamic array allocation. But if we do that, we get C26414. It's like a bad joke.
When all that's required is an array whose size is known only during runtime, a dynamically allocated array is the most appropriate and std::make_unique is simply used as a convenient means to delete the array automatically. The recommended solution of using std::vector is not appropriate because not only is it like using a sledgehammer on a thumbtack, it gives the false impression that the code would be changing the array's size - why else would it use a vector instead of a simple dynamic array?
I think this warning should make an exception for the use of std::make_unique with dynamic arrays just like it did for new.

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

ID: 8b46dcf5-a093-93d6-d5d6-e7abdacbbb99
Version Independent ID: f963e84d-05f9-9ddc-7766-50a4578f4f38
Content: C26414
Content Source: docs/code-quality/c26414.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@wmjdgla
Thanks for the comments. This could either be read either as a bug report or a suggestion for a product behavior change. As it's not really something we can address with a documentation change, I'm closing it. It's no reflection on the merits of your idea. Just a recommendation that you post it where it will get the attention it deserves. To put the idea in front of the analysis team, I recommend you make your case on Developer Community. Best of luck.


[Bug Report] two layer loop nested form elements, edit the latter element, delete the previous elements will lead to the value of the latter element reset

Element UI version
1.3.7
OS/Browsers version
win7 chrome最新版
Vue version
2.3.4
Reproduction Link
https://jsfiddle.net/Alexee/h9xL99pe/
Steps to reproduce

添加步骤
2.上下选择不一样的步骤
操作下面步骤的输入框或者checkbox，然后删除上面的步骤，下面的修改会被重置

What is Expected?
已经修改的表单值不被重置
What is actually happening?
位于数组后方已经修改的表单值会被重置，已经使用原生vue测试过，非vue的问题

The demo seems a little verbose and your description is kinda vague, so I don't quite get what your problem is. Please elaborate the problem and prepare a clearer demo.

the demo clearly demonstrates the problem，

you dynamicly add step（click ‘添加步骤’），
at step2  you then select different option，edit the input or checkbox below，
then delete the step1，you will find that everything you edit on step2 reset to the default value.

This is caused by Select emitting change event whenever its value changes. Ideally change event doesn't fire when the value updates programmatically, which will solve this problem here. We'll work on that in the next major version.

This problem is because your loop without the key prop, please checkout the fixed demo here.https://jsfiddle.net/h9xL99pe/8/


upgrade: actix-web, actix-http and actix-files

Resolves https://github.com/0xB10C/miningpool-observer/security/dependabot/3

rebased on #43 and ran cargo fmt


Molecules check assert bugfix

Fixes #283

An alternative fix would be to eliminate the assert statement here https://github.com/uber/deck.gl/blob/ea0e58d8fc64c45bbe65fcd7f472e4dcf0e9c066/modules/core/src/lib/layer.js#L886
and assign to clear the state variables right above the assert statement like this:
this.state = null;
this.initialState = null;

though it is not clear why the assert statement is needed. It is possible that deck.gl assumes that any layers passed will have never been rendered previously and therefore should have a null state.
Also note that here the layer manager tries to "transfer layer state" which may be related https://github.com/uber/deck.gl/blob/ea0e58d8fc64c45bbe65fcd7f472e4dcf0e9c066/modules/core/src/lib/layer-manager.js#L330

This is slow enough that there really needs to be some user feedback... and if it's just a stopgap, I'd hesitate to invest even more time here.
Have you already run across this post on github? Is that approach useful for us?
Closing without merge for now, but not the end of the story...


adding additional CNAME records

First of all thx for providing dnsdock, it's a nice tool to add simple dns/service discovery inside docker.
For my use case I would like to add multiple hostname/aliases to a single running container. For this reason I'd like to be able to add "arbitrary" CNAME records into dns.
Does this sound like a valid use case for dnsdock?
Is this something that is supported by dnsdock already or something you could imagine to add?

You can add aliases or arbitrary responses with the HTTP server but A records are only supported. I'm ok to adding CNAME if you are willing to maintain it. But maybe then it would make sense to make a separate project that has the DNS/HTTP server logic and is included as a package by dnsdock that adds the docker specific features.

Just spotted a fork of this project that seems to have some alias functionality. https://github.com/t0mk/dnscock

thx for your quick response. Actually CNAME is not my main concern, so additional A-records are probably fine as well. The most important is probably the ease of maintenance vi ENV varibles like DNSDOCK_ALIAS or similar. This seems to be a good a idea.

Since #16 has been merged, this issue can be closed :)


add on lazy resolution on the graphs

with the current mongo setup perform just the .skip() function

nope


[Feature] Please share any examples of control bridge with python and also controller in python

Feature description
...
Python matter sdk is not usable without any examples
No clear documentation and paths to follow and build for devices
Please share any examples of control bridge and controller in python sdk
Platform
python
Platform Version(s)
No response
Anything else?
No response

Why are these existing examples so fricking garbage not documentation or comments or anything
For Whom are these examples made for.


ADLSFileReader - Fixed issues when reading non-partitioned parquet and deltalake

…nd deltalake files
Please include answers to these questions as part of your pull request
In the GitHub webUI, use the Write tab to modify the Markdown text that is part of the pull request. For each question simply place an X inside the square brackets, [X], that represents your answer. Make sure there are no blanks inside the brackets, otherwise MarkDown doesn't render properly. Using the Preview tab while editing this form, you can see the formatted/rendered version of the message.

Q1: Confirm that you have the right to submit the code that is being contributed. Please consider the origin of your code and confirm you have the appropriate rights to make the submission subject to the Apache 2.0 license that applies to everything in this repository of custom steps. If so, follow the instructions for the Contributor Agreement (which is based on the industry-standard Developer Certificate of Origin (DCO)).

[X] Yes, I have the right to submit the contributed code on behalf of myself, my company, or any other owner of the code. I have also attached my signed copy of the DCO to this message.
[ ] No

Q2: Confirm that your contribution does not include any personally identifiable information (PII), for example, in any examples used in your README file.

[X] My contribution does NOT include PII data
[ ] My contribution includes PII data

Q3: Confirm your contribution does not include any encryption or other export-controlled technology.

[X] My contribution does NOT contain encryption or other export-controlled technology
[ ] My contribution includes encryption or other export-controlled technology

ContributorAgreement.txt

@AlfredoLorie, sorry haven't had time to look at this till now. Noticed that the README.md has an updated version and release date, but the About tab of the custom step wasn't updated. As you know, user-written custom steps are released independent of SAS Studio itself, therefore its important for the About tab to reflect version info properly and would be needed when users want to ask questions or report issues with it. So could you please update the About tab?

Added missing CS file with the code and the new version reflected in the about tab

SAS Internal Due Diligence Review - COMPLETED on 05MAY2023.


Switch Maria IP to internal

Use internal MariaDB address for data transfer during adoption to prevernt any possible security leaks
Closes: OSPRH-6584

Thanks, i'll merge this ahead of the CI changes, we need to be moving in this direction anyway.


Notice: preset number of characters per line is exceeded

If the preset number of characters per line is exceeded the editor issues a warning.
The numbers on the right of every subtitle describe the maximum number of characters per line (37) and the actual number of characters (04).
If the maximum number of characters ist exceeded, the numbers are marked in red.
If the number of characters is ok, it is marked in green and there is no text line.

If values do not meet the configured requirements there is a red light on the right side and an error message. If there are more than one errors a "+" appears. The user can click on the "+" and all error messages appear.

The requested functionality is implemented. UI will be implemented at a later stage, therefore the issue is kept open.

The UI part of this issue has moved to https://github.com/IRT-Open-Source/imsced/issues/109. Otherwise, the core requirement of this issue has been met and it can be closed.


Documentation

Jira-Issue: GER-25

Go through the scripts and add documentation where needed

@Thyrexx please check documentation for:

Behavior-Tree-Scripts (so everything in res://resources/entity/enemy/behaviorTree/)
Anything else you might thing has lack luster documentation rn


Include business platform ID in bugsnag info

WHY are these changes introduced?
Fixes #0000

WHAT is this pull request doing?

How to test your changes?

Post-release steps

Measuring impact
How do we know this change was effective? Please choose one:

[ ] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[ ] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[ ] I've considered possible documentation changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5137
#5136  👈 (View in Graphite)
#5120
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


[HOLD Web-E #40444] Display searched users outside of 'Recent' & 'Contact' sections

Details

We added some changes in the backend that should start returning personal details of any searched user that has an account in our system. But since these users will be stored in Onyx's personalDetails key, they will also be shown in the Recent or Contact section even if we only searched for them without opening a chat. This PR handles displaying them outside of any section, the same as any optimistic option we create when searching for a new user.
The backend searches works this way:

User enters input
Backend searches for reports matching the input, if reports are found, we return them and don't send back any personal details.
If no reports are found, and the email is valid, we search for personal details of the supplied email.
We return them along an extra prop isServerSearchResult=true.
From the search page, or any page that searches for reports/users (NewChatPage, MoneyRequestParticipantsSelector), once you tap on the searched user, we'll clear the isServerSearchResult to allow the searched user to show up later in 'Recent' and 'Contact' sections.

We then use this prop to display them outside of the 'Contact' & 'Recent' sections. Once we select the user and the report is opened, the prop is deleted and they can now appears in the sections aforementioned.
Fixed Issues

$ https://github.com/Expensify/Expensify/issues/328013
$ https://github.com/Expensify/App/issues/34353
PROPOSAL:
Tests

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[ ] I linked the correct issue in the ### Fixed Issues section above
[ ] I wrote clear testing steps that cover the changes made in this PR

[ ] I added steps for local testing in the Tests section
[ ] I added steps for the expected offline behavior in the Offline steps section
[ ] I added steps for Staging and/or Production testing in the QA steps section
[ ] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[ ] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[ ] I included screenshots or videos for tests on all platforms
[ ] I ran the tests on all platforms & verified they passed on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[ ] I followed proper code patterns (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[ ] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I followed the guidelines as stated in the Review Guidelines
[ ] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] I verified that if a function's arguments changed that all usages have also been updated correctly
[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

PR is off hold, I will resume working on it on Monday.

Will get back to this PR soon, this is a polish item, the original issue is fixed.