Reporting build scan could be optional

I just started to use the plugin and found that the build scan link appears each time after a build. It's a warning message.
I think this could be optional. It will generate less buzz on the reports page especially that build scan are used mostly in situations when something is wrong with the build (code or configuration)

Thank you. Fixed in https://github.com/burrunan/gradle-cache-action/pull/30

@vlsi when do you have plan to make a public release ?

This has been included in v1.6 or feb985ecf49f57f54f31920821a50d0394faf122 (see https://github.com/burrunan/gradle-cache-action/pull/31#issuecomment-740635745 )

Works like a charm. Thanks for great work!


Q: using zoom's native recording feature

@kastldratza I'm looking into using zoom's native recording feature instead of ffmpeg to record the screen. Before I go down that rabbithole I was curious if you have tried this and IF you did whether you abandoned it in favor of ffmpeg?

It's definitely possible if zoomrec supported user/pw params in order to log in with an account that has recording privileges.


Adding ssh-config to vagrant plugin autocomplete. Was missing

A command I personally end up having to use in my day-to-day. I thought maybe others could benefit from it. I found that ssh-config was not autocompleting the list of available vagrant machines. Found it was missing from the list of supported autocomplete commands in the _vagrant script.

Thank you.


add participant settings

This PR is not yet finished, but I have already opened it so that we can start a discussion about how we integrate the client setting in the client/participant and in the sdk.

@Robert-Steiner I just rebased against the updated master!


style: have git ignore test database

In the suggested developer environment setup described by CONTRIBUTING.md
a test database is created in test/db. After creating it, git status
continuously will show it as an untracked file, avoid this for all
developers following this setup.

Just an idea to make the life of Sailor developers easier. I am sure right now most of them have added this line to their .gitignore, so might as well have it done automatically since I don't think anybody wants git to track anything inside that directory.

Great idea! Thank you! :dancers:

Thanks Etiene!
I will submit little things I see while I play and learn with Sailor and it's code. If you don't mind :)

Please go ahead! I'm so glad! 🎉🍰💖


Compressor locks files

When I build the project the compressor (msbuild specifically) keeps a lock on the DLLs used. If I try to build the project again I get an error because of the lock. I have to close Visual Studio and re-open.
Thanks,
Jason

In order to stop visual studio from reusing msbuild nodes you can set an environment (user or system, up to you) variable as such: MSBUILDDISABLENODEREUSE=1. Note that it will affect visual studio globally (on that user/system), but I haven't had any problems whatsoever with it so give it a go.
Also restart visual studio after you've set the variable in order for it to take effect.

Is there anyway to pass this to the compressor as a parameter (i.e., /nr:false)? I saw the article stefan posted but I'm not sure how to pass that along to the RequireCompressorTask.
-J

Ignore that article, there's nothing to send to the task. Visual Studio needs to receive that variable value, so set it as you would any other environment variable: here's an example. Just add a new one with the key MSBUILDDISABLENODEREUSE and a value of 1


Reset footprint can be reduced

In Section 5.2, "Reset behavior", it is not necessary for reset to zero all of registers cqcsr, fqcsr, and pqcsr.
In cqcsr, only bits cqen, cie, cqon, and busy need to be zeroed on reset.
In fqcsr, only bits fqen, fie, fqon, and busy need to be zeroed on reset.
In pqcsr, only bits pqen, pie, pqon, and busy need to be zeroed on reset.

This was done to actually minimize the reset foot print. Reset of the error bits (8 bits) avoided needing to specify a reset of the larger MSI configuration table state. The MSI configuration table may have X after a reset if the error bits are not reset they may lead to a memory write being trigger to unknown/unexpected memory locations.

We could constrain software including random tests to not enable interrupts.
fctl can also be removed from the list.
PR #129

if the error bits are not reset they may lead to a memory write being trigger to unknown/unexpected memory locations.

How is that possible if cqcsr.cie, fqcsr.fie, and pqcsr.pie are all set to zeros on reset?  (See again my list above.)

See also #137.


IHSN country names differ from geo_tags country names

IHSN uses commas in country names (e.g. Egypt, Arab. Rep.). The googlespreadsheet uses commas to separate between different countries.
some names vary (e.g. Ivory Coast / Côte d'Ivoire, Sao Tome e Principe / São Tomé e Princìpe, Macedonia / Macedonia (Northern),....)
Thus, list of countries (derived from Geotags) does not correspond to the now existing number of countries and could be therefore related to issue #8.

Solved. Tibble with name conversion implemented


Bug fixes

Ok, not a bug fix (since you already fixed it)... but a few things that have been sitting in my branch.


Memory-safety proofs for aws_priority_queue functions

Signed-off-by: Felipe R. Monteiro<EMAIL_ADDRESS>Description of changes:
Adds invariant for aws_priority_queue structure and proof harnesses for the following functions:

aws_priority_queue_init_dynamic
aws_priority_queue_init_static
aws_priority_queue_clean_up
aws_priority_queue_top
aws_priority_queue_size
aws_priority_queue_capacity

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@karkhaz I addressed all your comments, thanks!


Release 1.5.21

This PR updates the version to 1.5.21.
This includes updating to the latest config, upgrading to the latest Spine libraries, and eliminating deprecated API usage.

@armiol, PTAL.


capitalize ID

Based on consistency of the other template function names changed Id to ID.

Ah shoot yeah you're right, but can't change that now since it will break custom commands that uses it, instead make a duplicate with the correct version, for now atleast anyways.
I could think up some system to migrate custom commands when things like this does happen, hm.


wrong link for sauce connect

Description

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@aliciakrebs API Testing requires a different configuration for Sauce Connect therefore makes more sense to add the link to that document instead of the "generic" one


Cannot connect to remote zookeeper cluster

I'm having trouble connecting to the zookeeper node(s). It's not a connection problem, the zookeeper cli can connect fine
ubuntu@sandpit-logstash:/usr/bin$ /usr/lib/zookeeper/bin/cli_mt <IP_ADDRESS>:2181
Watcher SESSION_EVENT state = CONNECTED_STATE
Got a new session id: 0xa539ebf7debfeba
bye

However, if I try to connect with confd (freshly downloaded confd-0.11.0-linux-amd64) I can't connect
ubuntu@sandpit-logstash:~$ ./confd-0.11.0-linux-amd64 -onetime -backend zookeeper -log-level=debug -node=<IP_ADDRESS>
2016-03-29T10:20:24Z sandpit-logstash ./confd-0.11.0-linux-amd64[12150]: INFO Backend set to zookeeper
2016-03-29T10:20:24Z sandpit-logstash ./confd-0.11.0-linux-amd64[12150]: INFO Starting confd
2016-03-29T10:20:24Z sandpit-logstash ./confd-0.11.0-linux-amd64[12150]: INFO Backend nodes set to <IP_ADDRESS>
2016-03-29T10:20:24Z sandpit-logstash ./confd-0.11.0-linux-amd64[12150]: DEBUG Loading template resources from confdir /etc/confd
2016-03-29T10:20:24Z sandpit-logstash ./confd-0.11.0-linux-amd64[12150]: DEBUG Loading template resource from /etc/confd/conf.d/test.toml
2016-03-29T10:20:24Z sandpit-logstash ./confd-0.11.0-linux-amd64[12150]: DEBUG Retrieving keys from store
2016-03-29T10:20:24Z sandpit-logstash ./confd-0.11.0-linux-amd64[12150]: DEBUG Key prefix set to /
2016-03-29T10:20:24Z sandpit-logstash ./confd-0.11.0-linux-amd64[12150]: ERROR zk: node does not exist

zookeeper is version 3.4.6.  Doesn't work if I add the port either (:2181)   What am I doing wrong?

@elisehuard You are connected.
ERROR zk: node does not exist -> You have to create the keys in zookeeper before connecting.
If you have the following config file:
[template]
src = "myconfig.conf.tmpl"
dest = "/tmp/myconfig.conf"
keys = [
    "/myapp/database/url",
    "/myapp/database/user",
]

then you have to set some values for /myapp/database/url and /myapp/database/user:
[zk: localhost:2181(CONNECTED) 1] create /myapp ""
[zk: localhost:2181(CONNECTED) 2] create /myapp/database ""
[zk: localhost:2181(CONNECTED) 3] create /myapp/database/url "db.example.com"
[zk: localhost:2181(CONNECTED) 4] create /myapp/database/user "rob"

Take a look at the quickstart_guide for some more examples: https://github.com/kelseyhightower/confd/blob/master/docs/quick-start-guide.md

Thank you for this, but I did create the keys beforehand:
ubuntu@sandpit-logstash:~$ /usr/lib/zookeeper/bin/cli_mt <IP_ADDRESS>:2181
Watcher SESSION_EVENT state = CONNECTED_STATE
Got a new session id: 0xa539ebf7dec0653
ls /myapp/database
time = 1 msec
/myapp/database: rc = 0
	user "rob"
	url "db.example.com"
time = 1 msec

so the tree is there
(although my zk cli doesn't like creating branch nodes with "" values, so I did without them. it only accepts values for leaf nodes)
Error stays the same ...

The zookeeper integration tests run with version 3.4.8 so it's not a incompatibility issue, I'd assume.
From grepping mailing lists it sounds like this is a client-side issue when communicating with a cluster. I'm not sure how this would occur but perhaps someone with more knowledge on communicating with a zookeeper cluster would know more.
ping @sheepkiller, any ideas on this one?

It seems to work when I use the standard zkCli.sh.  I'm happy to close this, since it really seems to be linked to my handling of zookeeper.

Hello @elisehuard
I 've got a same problem, I use Zookeeper 3.4.10 and the zkCli.sh.
Please, How had you solve it ?

@choco1992 please, share your confd template and config.

Hello @okushchenko,
thank for answering
There is my conf :
/etc/confd/conf.d
[root@otvmi580s conf.d]# cat /etc/confd/conf.d/myconfig.toml
[template]
src = "myconfig.conf.tmpl"
dest = "/tmp/myconfig.conf"
keys = [
    "/myapp/database/url",
    "/myapp/database/user",
]
[root@otvmi580s conf.d]# cat /etc/confd/templates/myconfig.conf.tmpl
[myconfig]
database_url = {{getv "/myapp/database/url"}}
database_user = {{getv "/myapp/database/user"}}
and there is the log error
[root@otvmi580s conf.d]# confd -onetime -backend zookeeper -log-level=debug  -node localhost:2181 -watch
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: INFO Backend set to zookeeper
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: INFO Starting confd
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: INFO Backend nodes set to localhost:2181
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: DEBUG Loading template resources from confdir /etc/confd
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: DEBUG Found template: /etc/confd/conf.d/myconfig.toml
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: DEBUG Loading template resource from /etc/confd/conf.d/myconfig.toml
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: DEBUG Retrieving keys from store
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: DEBUG Key prefix set to /
2017/08/01 13:37:35 Connected to <IP_ADDRESS>:2181
2017/08/01 13:37:35 Authenticated: id=98402608016785427, timeout=4000
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: ERROR zk: node does not exist
2017-08-01T13:37:35+02:00 otvmi580s confd[28489]: FATAL zk: node does not exist
Is it Ok ?
Don't hesitate if you want more informations .

Please, run these commands from zkCli.sh and copy the ouput:
ls /myapp
ls /myapp/database
get /myapp/database/url
get /myapp/database/user

Hi @okushchenko ,
Sorry, for beeing late, I saw my mistake
There is the result of that you asked:
[zk: localhost:2181(CONNECTED) 17] ls /myap
[database]
[zk: localhost:2181(CONNECTED) 17] ls /myap/database
[user, url]
...
In fact, I just putted  "myap" instead of "myapp" and the zookeeper was crying, I didn't see ...
I deleted all the tree and built a new tree from scratch, and it work's good without error.
[zk: localhost:2181(CONNECTED) 17] ls /myapp
[database]
[zk: localhost:2181(CONNECTED) 17] ls /myapp/database
[user, url]
[zk: localhost:2181(CONNECTED) 17] get /myapp/database/url
test.exple.com
cZxid = 0x3000000b8
ctime = Tue Aug 01 15:39:28 CEST 2017
mZxid = 0x3000000b8
mtime = Tue Aug 01 15:39:28 CEST 2017
pZxid = 0x3000000b8
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 14
numChildren = 0
[zk: localhost:2181(CONNECTED) 17] get /myapp/database/user
test
cZxid = 0x3000000b9
ctime = Tue Aug 01 15:41:21 CEST 2017
mZxid = 0x3000000b9
mtime = Tue Aug 01 15:41:21 CEST 2017
pZxid = 0x3000000b9
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 4
numChildren = 0
I relaunch the confd command and it's ok :
[root@otvmi580s zookeeper-3.4.10]# confd -onetime -backend zookeeper -log-level=debug  -node localhost:2181 -watch
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: INFO Backend set to zookeeper
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: INFO Starting confd
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: INFO Backend nodes set to localhost:2181
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Loading template resources from confdir /etc/confd
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Found template: /etc/confd/conf.d/myconfig.toml
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Loading template resource from /etc/confd/conf.d/myconfig.toml
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Retrieving keys from store
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Key prefix set to /
2017/08/01 15:50:57 Connected to <IP_ADDRESS>:2181
2017/08/01 15:50:57 Authenticated: id=98402608016785441, timeout=4000
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Using source template /etc/confd/templates/myconfig.conf.tmpl
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Compiling source template /etc/confd/templates/myconfig.conf.tmpl
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Comparing candidate config to /tmp/myconfig.conf
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: INFO /tmp/myconfig.conf has md5sum 8e76340b541b8ee29023c001a5e4da18 should be 8b78c28c375618fe50141161c7b304ea
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: INFO Target config /tmp/myconfig.conf out of sync
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: DEBUG Overwriting target config /tmp/myconfig.conf
2017-08-01T15:50:57+02:00 otvmi580s confd[3406]: INFO Target config /tmp/myconfig.conf has been updated
my /tmp/myconfig.conf file has been updated
-rw-r--r-- 1 root root 62 Aug  1 15:50 /tmp/myconfig.conf
A big thank for your help @okushchenko  and verry sorry  to had disrupt you
I would be more attentive the next time
Best regards.

@choco1992 all good, I'm glad I was able to help.


Domain Intents

This issue has to define the task domain for the natural language understanding model built on Rasa.
Supported tasks are:

Sending e-mail
CRUD operations on To-Do list
Weather (If API are free, check https://openweathermap.org/current)

This is a references list only for the main task. In the next step, maybe, we should improve the number and variance of the domain.

Adding a default response @giovanniPi997

Verified.


robust restoreconfig

restoring should not barf on any one item, but should emit a diagnostic and continue loading the rest of the stuff.

also, missing dict entries should be handled gracefully.

fixed in fb4


Unable to sign in to published title

I've recently published my game to the Xbox Marketplace. When I try to launch the game it just hangs when authenticating the player. I am able to sign in when in the test environment. Any help will be greatly appreciated.

This issue has been resolved


🤦 [WIP] blueprints: drop unsued returns

This drops unsued returns in the function which could not be covered the way it's written now.

I am currently investigating mock as an option to overcome this and test it the way it's written now.

I can't find the PR with the panic() in it for some reason, I know I saw it earlier though.
I think panic() is fine in this case, since the types guarantee they should always be able to marshal/unmarshal any error is going to be very unusual.
If you use the panic then there is no reason to return an error, so that could be dropped.
(In general you shouldn't use panic, but I think this is one of the exceptions since we likely have no control over whatever could make it actually fail).

This is obsolete now, closing.


Add Keep-Alive and Proxy-Connection to Headers

From implementing hyperium/hyper#1555, do you think it's worth adding KEEP_ALIVE, and PROXY_CONNECTION headers to the http::header module?

I think Keep-Alive is uncommon, and the only place I ever see it mentioned is sometimes in MDN docs. I don't think it appears often enough to add it as a variant in the internal match. Proxy-Connection I can't really say either way, I haven't read up much on it.

As part of some triage, I noticed this is a duplicate of #142, so closing.


files with .jsx extensions is not being scanned to export

Hi,
I'm trying to export the labels, using:
./node_modules/.bin/i18nliner export

there is a way to configure which file type you want to scan file to extract the translatable labels?
I guess I need to add it in .i18nrc file, but I didn't found any example of it.
Regards.

There's not currently an .i18nrc setting --- this pull request is one approach, but I think I want to do something more flexible that supports multiple processes, e.g. js vs hbs
In the meantime, it can be accomplished with a custom i18nliner plugin... basically create a file i18nliner-jsx.js like so:
module.exports = function(i18nliner) {
  var JsProcessor = i18nliner.processors.JsProcessor;
  JsProcessor.prototype.defaultPattern = ["*.js", "*.jsx"];
};

Then add the plugin to your .i18nrc like so:
{
  "plugins": [
    "react-i18nliner",
    "../../../../relative/path/to/i18nliner-jsx"
  ],
  "directories": ["jsapp"]
}

Unfortunately the "../../../.." is currently necessary, since it's resolved relative to node_modules/i18nliner/dist/lib/i18nliner.js

Thank you @jenseng I will try it!


feat: remove public /permissions/me usage

Description
This PR removes the hardcoded request to /developers/me/permissions and instead makes a request to a new endpoint that is more specifically targeted for controlling access to a given product.

@Mierenga you should see reduced calls now, but there's still some improvements to be made in the router side of things.

Saw an oddity when testing locally.
On this branch when navigating to an API Product from the catalog, both versions are shown as selected

On main, it appears as I would expect

Note I don't see this if refreshing the whole page while viewing an API Product, just when navigating from the catalog.

@Mierenga bug in kongponents, have a PR up now https://github.com/Kong/kongponents/pull/1843
Will update dependencies when that gets published.


[Bug] Increase CPU load average when exclude url added

Hi Pinpointer.
I'm ChangHun from NHN Entertainment.
First of all, I want give you thanks for this great project. I've installed Pinpoint last week for my project, then I got whole server status and request time at a glance. So, I can fix weak point of my service by pinpoint's favor.
However, I added exclude url for avoiding catch tomcat status monitoring request, at last weekend. The problem happened that CPU load and memory usage was increased. Because tomcat's threads was explosive increased. I don't know why this problem happened. I attached screenshot below for helping your understand. Please check it out.

I did change profiler.tomcat.excludeurl=/monitor/l7check.html to profiler.tomcat.excludeurl=/monitor/l7check.html,/managerAgent/getInfo of pinpoint.config file. I installed pinpoint 1.0.3.
Best regards,
ChangHun

Thank you for your reporting.
Did not find problems in filtering code.

ExcludeUrlFilter.java

Perhaps the application bug...
This issue is discussed in the company(nhn ent) e-mail

I made a mistake on my pinpoint settings. Thank you for your kindly response.

Hello ChangHun
We find bug for timer thread leak when agent could not connect continuously collector server.
We will fix bug in the near future.
thank you.
minwoo jung

This issue is known issue.
we was fixed bug already 1.0.4-SNAPSHOT.
I close this issue.


Issue verifying ldp whit did:web

When I generate an LDP_VC and enter the 'verificationMethod' as did:web in the 'proof', it is resolved but not interpreted correctly. I understand that it tries to obtain the 'verificationMethod' directly from the did.json, but it retrieves the web's structure and generates an error as it cannot obtain the key: 'Verification error(s)., getKeyPairForType does not support type: undefined.' However, the 'type' does exist but within the 'verificationMethod' of the LD.

Given it is closed I am assuming it is resolved.
I am also guessing that the issue is that you really need an assertionMethod as verificationMethod relationship, as that needs to be checked when verifying a VC from an Issuer, but would be good to know what the issue was.

I'm just facing the same issue - "Verification error(s)., getKeyPairForType does not support type: undefined." in an OIDC4VCI scenario where issuer uses web did. The same did.json works perfectly well in the OIDC4VP scenario.
@shagamd did you solve the issue? Can you share the experience how?

What is the did:web you're using? Could you share the did (or share an obfuscated did document)?
Is the verificationMethod both included in authentication and assertionMethod?

This is the example of the did:web document. I can check it has been fetched by the wallet.
{
    "@context": [
        "https://www.w3.org/ns/did/v1",
        "https://w3id.org/security/suites/jws-2020/v1"
    ],
    "id": "did:web:vcvalidator-test-client.azuremicroservices.io",
    "verificationMethod": [
        {
            "id": "did:web:vcvalidator-test-client.azuremicroservices.io#CW1kgkCiNefC",
            "type": "JsonWebKey2020",
            "controller": "did:web:vcvalidator-test-client.azuremicroservices.io",
            "publicKeyJwk": {
                "kty": "OKP",
                "crv": "Ed25519",
                "x": "JYCAGl6C7gcDeKbNqtXBfpGzH0f5elifj7L6zYNj_Is"
            }
        }
    ],
    "authentication": [
        {
            "id": "did:web:vcvalidator-test-client.azuremicroservices.io#CW1kgkCiNefC",
            "type": "JsonWebKey2020",
            "controller": "did:web:vcvalidator-test-client.azuremicroservices.io",
            "publicKeyJwk": {
                "kty": "OKP",
                "crv": "Ed25519",
                "x": "JYCAGl6C7gcDeKbNqtXBfpGzH0f5elifj7L6zYNj_Is"
            }
        }
    ],
    "assertionMethod": [
        {
            "id": "did:web:vcvalidator-test-client.azuremicroservices.io#CW1kgkCiNefC",
            "type": "JsonWebKey2020",
            "controller": "did:web:vcvalidator-test-client.azuremicroservices.io",
            "publicKeyJwk": {
                "kty": "OKP",
                "crv": "Ed25519",
                "x": "JYCAGl6C7gcDeKbNqtXBfpGzH0f5elifj7L6zYNj_Is"
            }
        }
    ],
    "keyAgreement": []
}

And the proof looks like this:
   "proof": {
     "type": "JsonWebSignature2020",
     "created": "2024-02-05T12:08:57Z",
     "proofPurpose": "assertionMethod",
     "verificationMethod": "did:web:vcvalidator-test-client.azuremicroservices.io#CW1kgkCiNefC",
     "jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..mbo1K4VN9p8_5B7fD3hiFN3yVAKgn5cSaArAM4_ibsJaV9hijHhUu8SiG6g_YPHBec0eWyHDdqHasB2H0GqXDA"
     }

However, I just discovered, that it's not an issue with did:web method, I got the same result when using JsonWebSignature2020 also with did:jwk and did:key.

Could you provide a bit more context?
Which version of the wallet are you using? Also what are you using on the VCI side?
We know that current released store version of the wallet has an issue with did:web. We will be releasing a new version of the wallet soon, which has many fixes. If you can point me to a VCI issuer, where this is happening, I can test with a development version to see if it is resolved.

@ejossev
In my case, I managed to solve it by modifying my DIDDocument. I was using JsonWebKey2020, and I changed it to Ed25519VerificationKey2018. I did this by examining the functioning of the DID resolver. When I received a did:key, it generated the following structure for me:
{
    "@context": [
        "https://www.w3.org/ns/did/v1",
        "https://w3id.org/security/suites/ed25519-2018/v1"
    ],
    "id": "did:key:z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ",
    "verificationMethod": [
        {
            "id": "did:key:z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ",
            "type": "Ed25519VerificationKey2018",
            "controller": "did:key:z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ",
            "publicKeyBase58": "3bri2zM45auXyW6WvgJXZ1ydJvmzfD6xgMBt5HNqPy22"
        }
    ],
    "assertionMethod": [
        "did:key:z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ#z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ"
    ],
    "authentication": [
        "did:key:z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ#z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ"
    ],
    "capabilityInvocation": [
        "did:key:z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ#z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ"
    ],
    "capabilityDelegation": [
       "did:key:z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ#z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ"
    ]
}

So, I modified the structure of my did:web to use Ed25519VerificationKey2018.
then i modify my did:web to
{
    "@context": [
        "https://www.w3.org/ns/did/v1",
        "https://w3id.org/security/suites/ed25519-2018/v1"
    ],
    "id": "did:web:example.com:identity:legalentity",
    "verificationMethod": [
        {
            "id": "did:web:example.com:identity:legalentity#key-0",
            "type": "Ed25519VerificationKey2018",
            "controller": "did:key:z6Mkh47kdEbVR8Q15zwDcFGNQ7Xd8W3r56MKNN6ouZLrKBoQ",
            "publicKeyBase58": "3bri2zM45auXyW6WvgJXZ1ydJvmzfD6xgMBt5HNqPy22"
        }
    ],
    "assertionMethod": [
        "did:web:example.com:identity:legalentity#key-0"
    ],
    "authentication": [
        "did:web:example.com:identity:legalentity#key-0"
    ],
    "capabilityInvocation": [
        "did:web:example.com:identity:legalentity#key-0"
    ],
    "capabilityDelegation": [
        "did:web:example.com:identity:legalentity#key-0"
    ]
}

@shagamd: Okay that explains why it worked for you, given the issue indeed is in JWK handling, specifically for did:web
@ejossev: If you could send an e-mail to nklomp [at] sphereon . com, then I am happy to have a look at it. We can probably also give you access to a development build somewhere this week

@nklomp Sent.


Fix missing merge commit from #14773

PR #14773 was missing a merge commit from rampup. This PR changes no files, just appropriately merges the commit history into berkeley

!ci-build-me

!approved-for-mainnet


NATS

Continuation of https://github.com/binwiederhier/ntfy/issues/19#issuecomment-1002769688

Just a discussion of it NATS is a good option for nfty.

Just a discussion of it NATS is a good option for nfty.

The pure GRPC basis is definitely a nice option.

You got it!
Although you know this - just repeating to ensure we are all on the same page: due to GRPC, it's automatic to use ANY language as the pub-sub nodes.
For example, Tyler and his team focuses on Go, and we are a Python shop.
However, because of GRPC, we are easily able to use Python with LIftbridge.

Does LIftbridge has the ability for the client to automatically connect to nearest server and then fail over to nearest etc ?

It does and more (it really does a good job of HA replication - something that's critical for prod workloads)
Just ask and confirm with them:
Tyler and his team is fantastic and has OSS the very product he is building his company on.
Just drop by on their Slack to ask any questions you have - no matter how basic 👍

The pure GRPC basis is definitely a nice option.

You got it!
Although you know this - just repeating to ensure we are all on the same page: due to GRPC, it's automatic to use ANY language as the pub-sub nodes.
For example, Tyler and his team focuses on Go, and we are a Python shop.
However, because of GRPC, we are easily able to use Python with LIftbridge.

Does LIftbridge has the ability for the client to automatically connect to nearest server and then fail over to nearest etc ?

It does and more (it really does a good job of HA replication - something that's critical for prod workloads)
Just ask and confirm with them:
Tyler and his team is fantastic and has OSS the very product he is building his company on.
Just drop by on their Slack to ask any questions you have - no matter how basic 👍

Hey @gc-ss
Are you using it in production ?
What gotchas have you found in your usage ?
I ask because I tried it a while ago ( maybe 8 months ago ) and it had some issues. I think the Raft replication was a little buggy if I recall.
Also nats Jetstream is designed as a message hub with publishers and consumers of streams decoupled at compile time . So at runtime you can hook a consumer up to a publishers stream and subject .
I don’t think ( but it’s been a while ) that Liftbridge supports this type of decoupled functionality. Not everyone needs that of course though.

Yes, it's being used in production. The biggest gotchas have been due to us using Python while LIftbridge documentation often assumes a Go context. Since they don't seem to be a Python shop, they are not as interested in reproducing Python issues.
However, for core Liftbridge issues, I've obtained responses and fixes (when needed) within days without a commercial contract

a message hub with publishers and consumers of streams decoupled at compile time . So at runtime you can hook a consumer up to a publishers stream and subject

That's exactly the usecase I have for Liftbridge in production.
You might be interested in reading up why Liftbridge was designed even though nats Jetstream exists.
Feel free to drop by on their Slack to ask any questions you have - I use Liftbridge in a very niche way (strongly decoupled, multi environment (language/OS/onpremise/cloud) node data mesh) - they can answer these Liftbridge specific questions much better than I can 👍

… and yes, your initial proposal to @binwiederhier that ntfy would be drastically simplified and scaled is correct using LiftBridge/NATS which is why I joined the conversation.
In this case, the publisher and consumer are the phone apps or webservice, as the case may be.
LiftBridge/NATS is the hosted message bus.
Very simple yet powerful cloud native (that can be hosted on a laptop if needed) architecture.

If your open to it would be nice to compare notes offline . I have never had an in-depth discussion about Liftbridge as I just used nats and before that Tibco rendezvous ( a commercial produce that does pretty much what nats Jetstream does ).

If your open to it would be nice to compare notes offline

Sure. If you have a calendly link, feel free to share. Otherwise I can put a temp. email here that you can email to
let me know

I have a telegram link on my GitHub profile ..  do you use telegram ?
I am in Berlin, Germany btw, so gmt +1

do you use telegram

I dont. If you don't mind sending me a quick email to:
<EMAIL_ADDRESS>I will get back to you and we can setup a meeting from there :)

I am reading up on the latest release . It seems to have most of the architectural features now.
I use GRPC heaps and so it’s interesting to use Liftbridge since it’s just more GRPC.
I was looking for security stuff like NATS Jetstream had so that streams can be restricted by user / roles. It looks like with Liftbridge you have to do this yourself

I was looking for security stuff like NATS Jetstream had so that streams can be restricted by user / roles. It looks like with Liftbridge you have to do this yourself

Sure, since I already use oso or opa for Authz, I prefer using those for this as well instead of yet another different thing NATS Jetstream offers.
I am interested to know how you find the latest Liftbridge

I know OPA. OSO  is new one to me…

I was gonna just close this ticket, but I do think I owe you guys the courtesy of fully understanding what you'd want to use NATS for in ntfy.
I think I understand what it is (a pub sub system), and I think I understand what you'd want me to do (replace the guts of ntfy with NATS), but what I don't understand is why? What's the use case you see or want to support that needs NATS. Why would I do weeks of work to implement NATS? It feels like a pointless refactor at this point. I'd add complexity for features I don't want to need, no?

@binwiederhier
I can really see your point !!
At the moment i love the fact that you have SSE, WS, CURL, etc ways of interacting with the system.  its really a PITA to do that with NATS but you have already done it.
If you put NATS behind everything and ONLY used it for the Federation aspects it would be useful ? Maybe.. It used RAFT under the hood to do its HA, Clustering.
Happy to explore this with you if you want...

but what I don't understand is why? What's the use case you see or want to support that needs NATS. Why would I do weeks of work to implement NATS? It feels like a pointless refactor at this point. I'd add complexity for features I don't want to need, no?

This is a very strategic question, the answer to which is a long scenarios and requirements spec.
Before writing that out, let me share my usecase for ntfy.
ntfy to me is a prototype event sharing producer-consumer system.
The current ntfy prototype has proven to us that:

There's a huge demand for such an event sharing producer-consumer system - i.e., you have addressed the Market risk (people are interested in this as it solves a problem they have).
There's proof that such an event sharing producer-consumer system can be built - i.e., you have addressed the Product risk (you have the ability to build a product that solves the problem)

The next steps are to build out the product more and there's one big gaping hole in the current ntfy prototype: Reliability.
Reliability has to be the cornerstone of an event sharing producer-consumer system.
As people build out and start depending on ntfy for their event sharing needs, reliability will start to rear its ugly head.
Some things/reports we will see based off my experience in event sharing producer-consumer systems:
i. Messages sent weren't received by all consumers
ii. Duplicate messages were received by consumers
iii. Messages were thought to be sent weren't received by any consumers
iv. A temporary spike in events from certain producers overwhelmed the single ntfy service and made it crash, losing state/events and there's no ability to "scale out" the system
v. Certain popular topics that are important, but fire only occasionally, have an overwhelming number of consumers and the resource overhead of idle connections are "too much" for one server (it would be awesome to pause/resume these topics on demand to efficiently utilize compute resources)
These will show up as ntfy becomes popular.
These are all usecases well solved by LiftBridge/NATS and we haven't even discussed HA needs yet as @gedw99 has pointed out some scenarios (which I would classify as the second phase of reliability).

here is a good video demo by the main Lead developer of NATS showing how it does real time failover.
https://nats.io/blog/kv-cli/
NATS or LIftbridge give similar things BTW for Nfty. Nats and Liftbridge do have differences though.
I am going to answer the follow queries presuming your using NATS.
Yes its a 2nd phase thing !!
yes most of those things you mentioned are fixed by NATS and LiftBridge:
i. Messages sent weren't received by all consumers

Yep this is solved by both.

ii. Duplicate messages were received by consumers

They are both at least once.

iii. Messages were thought to be sent weren't received by any consumers

They both support ACK ( acknowledgement ) from the client if you use it.

iv. A temporary spike in events from certain producers overwhelmed the single ntfy service and made it crash, losing state/events and there's no ability to "scale out" the system

They both support runs as a cluster.
Nats does automatic load balancing an can do it just over http ( if you want ). This video really shows the off the geo load balancing: https://www.youtube.com/watch?v=qZ7fww7_s7A. In this case its using Caddy http roundtripper to do it: https://github.com/ripienaar/nats-roundtripper

v. Certain popular topics that are important, but fire only occasionally, have an overwhelming number of consumers and the resource overhead of idle connections are "too much" for one server (it would be awesome to pause/resume these topics on demand to efficiently utilize compute resources)

You can tag topics to have priority.  Via the nats cli you can test this out.
You can also split the traffic.
Also you can orchestrate upgades of NATS. Say you had 3 nats clusters in EU, and also a cluster in US and Asia. If you wanted to upgrade them all you can take each cluster offline, and the clients will failover automatically to the nearest other cluster with no disruption to the client.  Then you upgrade it, and then do the same for the other 2 clusters.
I can supply some scripts that do this for you. It just uses the NATS CLI to do it.

Security is built into NATS too. You can create users and roles and they propagate to all the clusters.
I hope this answers all these questions ???

Yep I do . It’s for the bet


Chore/update dependencies

Update dependencies

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


update 'kpod images' and 'kpod rmi' commands

add more flags to kpod images and kpod rmi, and write tests

bot, add author to whitelist

bot, test pull request

@14rcole Sign your image.  This is a patch for buildah not kpod, so change the title.

@14rcole tests are crashing.

My most recent addition to this PR should resolve #133

@14rcole tests crashing.

LGTM
@nalind PTAL

@14rcole Please rebase.

Rebasing didn't update my PR.  Do I need to trigger something manually?

Never mind, it seems to have just been delayed

@rhatdan is there a way to manually re-trigger the checks?  It looks like an internal error occurred on the Red Hat CI

@14rcole I usually just do a
git commit -a --amend -s
git push rhatdan --force

@nalind you ok with merging?

@14rcole you need to update buildah.md and README.md with these new commands.

@rhatdan The commands were already listed in buildah.md and README.md, and I updated both buildah-images.md and buildah-rmi.md to include the flags I added.  Is there something else in those files that needs to be changed?

Ok Sorry I thought they were missing.

I am going to merge...
@rh-atomic-bot r+ c7c207b


Can it support Neovim?

This plugin works in vim but not in neovim?  even can not find the commands.

I'm refactoring this project, After that I'll support neovim.


[Snyk] Security upgrade python from 3.9.5-buster to 3.10-buster

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

Dockerfile

We recommend upgrading to python:3.10-buster, as this image has only 457 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

714
Buffer Overflow SNYK-DEBIAN10-OPENSSL-1569403
No Known Exploit

614
Out-of-bounds Read SNYK-DEBIAN10-OPENSSL-1569406
No Known Exploit

678
Loop with Unreachable Exit Condition ('Infinite Loop') SNYK-DEBIAN10-OPENSSL-2426310
No Known Exploit

778
OS Command Injection SNYK-DEBIAN10-OPENSSL-2807585
No Known Exploit

614
Use After Free SNYK-DEBIAN10-SUBVERSION-2635642
No Known Exploit

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
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

bumped to python:3.11-buster hence closing this pr


yarn build

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Error: Get config: Unable to establish a connection to query-engine-node-api library
Prisma CLI Version : 3.15.2
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "build-db-client" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "build-db" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
You may need to install some additional packages for your OS. See https://github.com/prisma/prisma/issues/13717.
 Replaced three computers. gradually collapse

You need to provide more information. OS, node version, etc. What did you try, what did you install?


User setup form failing

Describe the bug
User is met with requirements of the form to be valid even though they are, making the user not able to progress with the setup System.
To Reproduce
Steps to reproduce the behavior:

Sign up on the website
User is met with the Setup interface, and fills it up with the appropriate fields.
User is met with 'Avatar, Display Name and Bio Required' even though they are in the fields.

Screenshots

The issue seems to be caused by the EmailService.

The issue seems to be caused by the EmailService.

Turns out this is due to having an incomplete appsettings.json file.

The bug seems to be due to a migration error and will be fixed in the next PR.


Java Launcher?

as this game is in Java why isn't there a .jar launcher for mac and linux users like me?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36278670-java-launcher?utm_campaign=plugin&utm_content=tracker%2F715506&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F715506&utm_medium=issues&utm_source=github).

Hi @DanHolli123 :-)
Check out /bin for a Linux style script. You can also simply launch via java -jar lib/TerasologyLauncher.jar on command line from the root of the extracted launcher zip

thx


Jump to Top or  Way of Moving to Next Housing Type

At bottom of section, add a way to jump to the next typology without needing to scroll back to the top of the section.
Related to #3

Closing this issue as a section exists. Additional tweaks in #64 and more types #13 in own issues


torch_scatter.scatter_cpu issue.

📚 Installation

Environment

OS: Linux
Python version: 3.6
PyTorch version:1.4
CUDA/cuDNN version: 9.1
GCC version: 7.4.0
How did you try to install PyTorch Geometric and its extensions (pip, source): pip
Any other relevant information:

Checklist

[x] I followed the installation guide.
[x] I cannot find my error message in the FAQ.
[x] I set up CUDA correctly and can compile CUDA code via nvcc.
[ ] I have cloned the repository and tried a manual installation from source.
[] I do have multiple CUDA versions on my machine.
[x] I checked if the official extension example runs on my machine.
[x] The offical extension example runs on my machine.

Additional context

I have installed pytorch_geometric, but I had the following error.
Traceback (most recent call last):
File "/home/USER/PycharmProjects/pytorch_geometric/main.py", line 8, in
from torch_geometric.data import Data
File "/home/USER/.local/lib/python3.6/site-packages/torch_geometric/init.py", line 2, in
import torch_geometric.nn
File "/home/USER/.local/lib/python3.6/site-packages/torch_geometric/nn/init.py", line 2, in
from .data_parallel import DataParallel
File "/home/USER/.local/lib/python3.6/site-packages/torch_geometric/nn/data_parallel.py", line 5, in
from torch_geometric.data import Batch
File "/home/USER/.local/lib/python3.6/site-packages/torch_geometric/data/init.py", line 1, in
from .data import Data
File "/home/USER/.local/lib/python3.6/site-packages/torch_geometric/data/data.py", line 7, in
from torch_sparse import coalesce
File "/home/USER/.local/lib/python3.6/site-packages/torch_sparse/init.py", line 2, in
from .coalesce import coalesce
File "/home/USER/.local/lib/python3.6/site-packages/torch_sparse/coalesce.py", line 2, in
import torch_scatter
File "/home/USER/.local/lib/python3.6/site-packages/torch_scatter/init.py", line 3, in
from .mul import scatter_mul
File "/home/USER/.local/lib/python3.6/site-packages/torch_scatter/mul.py", line 3, in
from torch_scatter.utils.ext import get_func
File "/home/USER/.local/lib/python3.6/site-packages/torch_scatter/utils/ext.py", line 2, in
import torch_scatter.scatter_cpu
ImportError: /home/USER/.local/lib/python3.6/site-packages/torch_scatter/scatter_cpu.cpython-36m-x86_64-linux-gnu.so: undefined symbol: _ZN6caffe26detail37_typeMetaDataInstance_preallocated_29E

I have the same problem.


Update the OnPremisesInstanceTagFilters parameter for AWS::CodeDeploy::DeploymentGroup

CloudFormation expects the OnPremisesInstanceTagFilters parameter of the AWS::CodeDeploy::DeploymentGroup resource to be a list of objects and not a single object, as seen in the documentation. This PR fixes that.
I would also like to change the codedeploy.OnPremisesInstanceTagFilters to codedeploy.OnPremisesInstanceTagFilter (singularis), but not sure how you usually go about doing things like that since it's breaking. If you think it's a good idea, let me know how you usually do it and I will fix it.

Thanks! Actually the name should be "TagFilter". I wish I could have better historical documentation to show why I named things like I did at the time. lol


Line 807, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-PartnerApplication'.
Line 808, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-SettingOverride'.
Line 809, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AccessToCustomerDataRequest'.
Line 810, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ApplicationAccessPolicy'.
Line 811, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AuthConfig'.
Line 812, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AuthenticationPolicy'.
Line 813, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AuthServer'.
Line 814, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-CmdletExtensionAgent'.
Line 815, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ExchangeAssistanceConfig'.
Line 816, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ExchangeServer'.
Line 817, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ExchangeSettings'.
Line 818, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-Notification'.
Line 819, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-OrganizationConfig'.
Line 820, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-PartnerApplication'.
Line 821, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-PerimeterConfig'.
Line 822, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-SettingOverride'.
Line 823, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-ApplicationAccessPolicy'.
Line 824, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-OAuthConnectivity'.
Line 825, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-SystemHealth'.
Line 826, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-ExchangeHelp'.
Line 859, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Install-UnifiedCompliancePrerequisite'.
Line 860, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-ActivityAlert'.
Line 864, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-JournalRule'.
Line 865, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-Label'.
Line 867, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-MessageClassification'.
Line 868, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-OrganizationSegment'.
Line 869, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-OutlookProtectionRule'.
Line 870, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-ProtectionAlert'.
Line 871, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-SupervisoryReviewPolicyV2'.
Line 873, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-TransportRule'.
Line 874, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ActivityAlert'.
Line 875, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AutoSensitivityLabelPolicy'.
Line 876, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AutoSensitivityLabelRule'.
Line 877, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-InformationBarrierPolicy'.
Line 878, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-JournalRule'.
Line 879, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-Label'.
Line 880, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-LabelPolicy'.
Line 881, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-MessageClassification'.
Line 882, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-OrganizationSegment'.
Line 883, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-OutlookProtectionRule'.
Line 884, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ProtectionAlert'.
Line 885, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-RecordLabel'.
Line 886, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-SupervisoryReviewPolicyV2'.
Line 887, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-TransportRule'.
Line 888, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ActivityAlert'.
Line 889, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AutoSensitivityLabelPolicy'.
Line 890, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AutoSensitivityLabelRule'.
Line 891, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-InformationBarrierPolicy'.
Line 892, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-JournalRule'.
Line 893, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-Label'.
Line 894, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-LabelPolicy'.
Line 895, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-MessageClassification'.
Line 896, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-OrganizationSegment'.
Line 897, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-OutlookProtectionRule'.
Line 898, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ProtectionAlert'.
Line 899, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-SupervisoryReviewPolicyV2'.
Line 900, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-SupervisoryReviewRule'.
Line 901, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-TransportRule'.
Line 902, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Start-InformationBarrierPoliciesApplication'.
Line 903, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Stop-InformationBarrierPoliciesApplication'.
Line 904, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-ArchiveConnectivity'.
Line 914, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-AdminAuditLogSearch'.
Line 915, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-AuditConfigurationPolicy'.
Line 916, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-AuditConfigurationRule'.
Line 917, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-MailboxAuditLogSearch'.
Line 918, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-UnifiedAuditLogRetentionPolicy'.
Line 919, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AuditConfigurationPolicy'.
Line 920, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AuditConfigurationRule'.
Line 921, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UnifiedAuditLogRetentionPolicy'.
Line 922, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Search-AdminAuditLog'.
Line 923, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Search-MailboxAuditLog'.
Line 924, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Search-UnifiedAuditLog'.
Line 925, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AdminAuditLogConfig'.
Line 926, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AuditConfig'.
Line 927, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AuditConfigurationRule'.
Line 928, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-MailboxAuditBypassAssociation'.
Line 929, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UnifiedAuditLogRetentionPolicy'.
Line 930, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Write-AdminAuditLog'.
Line 937, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Invoke-ComplianceSearchActionStep'.
Line 940, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-ComplianceSecurityFilter'.
Line 941, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-MailboxSearch'.
Line 942, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ComplianceSearch'.
Line 943, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ComplianceSearchAction'.
Line 944, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ComplianceSecurityFilter'.
Line 945, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-MailboxSearch'.
Line 946, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ComplianceSearch'.
Line 947, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ComplianceSearchAction'.
Line 948, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ComplianceSecurityFilter'.
Line 949, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-MailboxSearch'.
Line 950, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Start-ComplianceSearch'.
Line 951, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Start-MailboxSearch'.
Line 952, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Stop-ComplianceSearch'.
Line 953, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Stop-MailboxSearch'.
Line 976, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-DataClassification'.
Line 977, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-DlpCompliancePolicy'.
Line 978, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-DlpComplianceRule'.
Line 987, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ClassificationRuleCollection'.
Line 988, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DataClassification'.
Line 989, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DlpCompliancePolicy'.
Line 990, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DlpComplianceRule'.
Line 991, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DlpEdmSchema'.
Line 992, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DlpKeywordDictionary'.
Line 993, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DlpPolicy'.
Line 994, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DlpPolicyTemplate'.
Line 995, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DlpSensitiveInformationType'.
Line 996, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DlpSensitiveInformationTypeRulePackage'.
Line 997, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-PolicyTipConfig'.
Line 998, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ClassificationRuleCollection'.
Line 999, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DataClassification'.
Line 1000, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DlpCompliancePolicy'.
Line 1001, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DlpComplianceRule'.
Line 1002, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DlpEdmSchema'.
Line 1003, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DlpKeywordDictionary'.
Line 1004, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DlpPolicy'.
Line 1005, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DlpSensitiveInformationType'.
Line 1006, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DlpSensitiveInformationTypeRulePackage'.
Line 1007, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-PolicyConfig'.
Line 1008, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-PolicyTipConfig'.
Line 1009, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-DataClassification'.
Line 1010, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-TextExtraction'.
Line 1020, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-CaseHoldPolicy'.
Line 1023, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-CaseHoldPolicy'.
Line 1024, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-CaseHoldRule'.
Line 1025, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ComplianceCase'.
Line 1026, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ComplianceCaseMember'.
Line 1027, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-eDiscoveryCaseAdmin'.
Line 1028, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-CaseHoldPolicy'.
Line 1029, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-CaseHoldRule'.
Line 1030, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ComplianceCase'.
Line 1031, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-ComplianceCaseMember'.
Line 1032, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-eDiscoveryCaseAdmin'.
Line 1064, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-AppRetentionCompliancePolicy'.
Line 1075, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-HoldCompliancePolicy'.
Line 1078, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-ManagedFolder'.
Line 1080, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-RetentionCompliancePolicy'.
Line 1082, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-RetentionPolicy'.
Line 1083, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-RetentionPolicyTag'.
Line 1084, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AppRetentionCompliancePolicy'.
Line 1085, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AppRetentionComplianceRule'.
Line 1086, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ComplianceRetentionEventType'.
Line 1087, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ComplianceTag'.
Line 1088, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-FilePlanPropertyAuthority'.
Line 1089, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-FilePlanPropertyCategory'.
Line 1090, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-FilePlanPropertyCitation'.
Line 1091, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-FilePlanPropertyDepartment'.
Line 1092, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-FilePlanPropertyReferenceId'.
Line 1093, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-FilePlanPropertySubCategory'.
Line 1094, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-HoldCompliancePolicy'.
Line 1095, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-HoldComplianceRule'.
Line 1096, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ManagedContentSettings'.
Line 1097, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ManagedFolder'.
Line 1098, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ManagedFolderMailboxPolicy'.
Line 1099, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-RetentionCompliancePolicy'.
Line 1100, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-RetentionComplianceRule'.
Line 1101, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-RetentionPolicy'.
Line 1102, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-RetentionPolicyTag'.
Line 1103, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AppRetentionCompliancePolicy'.
Line 1104, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AppRetentionComplianceRule'.
Line 1105, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ComplianceRetentionEventType'.
Line 1106, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ComplianceTag'.
Line 1107, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-FilePlanPropertyAuthority'.
Line 1108, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-FilePlanPropertyCategory'.
Line 1109, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-FilePlanPropertyCitation'.
Line 1110, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-FilePlanPropertyDepartment'.
Line 1111, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-FilePlanPropertyReferenceId'.
Line 1112, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-FilePlanPropertySubCategory'.
Line 1113, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-HoldCompliancePolicy'.
Line 1114, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-HoldComplianceRule'.
Line 1115, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ManagedContentSettings'.
Line 1116, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ManagedFolder'.
Line 1117, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ManagedFolderMailboxPolicy'.
Line 1118, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-RecordReviewNotificationTemplateConfig'.
Line 1119, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-RegulatoryComplianceUI'.
Line 1120, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-RetentionCompliancePolicy'.
Line 1121, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-RetentionComplianceRule'.
Line 1122, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-RetentionPolicy'.
Line 1123, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-RetentionPolicyTag'.
Line 1124, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Start-ManagedFolderAssistant'.
Line 1125, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Start-RetentionAutoTagLearning'.
Line 1126, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Stop-ManagedFolderAssistant'.
Line 1127, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Validate-RetentionRuleQuery'.
Line 1145, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-MyAnalyticsFeatureConfig'.
Line 1146, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UserBriefingConfig'.
Line 1147, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-VivaInsightsSettings'.
Line 1188, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Get-ReportExecutionInstance'.
Line 1214, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Get-RoleGroupMember'.
Line 1215, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-ManagementRole'.
Line 1216, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-ManagementRoleAssignment'.
Line 1217, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-ManagementScope'.
Line 1218, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-RoleAssignmentPolicy'.
Line 1220, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ManagementRole'.
Line 1221, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ManagementRoleAssignment'.
Line 1222, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ManagementRoleEntry'.
Line 1223, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ManagementScope'.
Line 1224, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-RoleAssignmentPolicy'.
Line 1225, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-RoleGroup'.
Line 1226, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-RoleGroupMember'.
Line 1227, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ManagementRoleAssignment'.
Line 1228, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ManagementRoleEntry'.
Line 1229, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ManagementScope'.
Line 1230, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-RoleAssignmentPolicy'.
Line 1231, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-RoleGroup'.
Line 1232, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-RoleGroupMember'.
Line 1246, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Get-ThrottlingPolicy'.
Line 1249, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-AvailabilityReportOutage'.
Line 1250, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-ThrottlingPolicy'.
Line 1251, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AvailabilityReportOutage'.
Line 1252, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-GlobalMonitoringOverride'.
Line 1253, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ServerMonitoringOverride'.
Line 1254, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-ThrottlingPolicy'.
Line 1255, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AvailabilityReportOutage'.
Line 1256, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-EventLogLevel'.
Line 1257, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ServerComponentState'.
Line 1258, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ServerMonitor'.
Line 1259, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ThrottlingPolicy'.
Line 1260, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-ThrottlingPolicyAssociation'.
Line 1261, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-ServiceHealth'.
Line 1285, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-OrganizationRelationship'.
Line 1286, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-PublicFolder'.
Line 1290, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-SiteMailboxProvisioningPolicy'.
Line 1291, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-SyncMailPublicFolder'.
Line 1292, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AvailabilityAddressSpace'.
Line 1293, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-AvailabilityConfig'.
Line 1294, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-OrganizationRelationship'.
Line 1295, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-PublicFolder'.
Line 1296, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-PublicFolderAdministrativePermission'.
Line 1297, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-PublicFolderClientPermission'.
Line 1298, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-PublicFolderDatabase'.
Line 1299, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-SharingPolicy'.
Line 1300, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-SiteMailboxProvisioningPolicy'.
Line 1301, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-SyncMailPublicFolder'.
Line 1302, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Resume-PublicFolderReplication'.
Line 1303, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-AvailabilityConfig'.
Line 1304, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-MailPublicFolder'.
Line 1305, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-OrganizationRelationship'.
Line 1306, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-PublicFolder'.
Line 1307, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-PublicFolderDatabase'.
Line 1308, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-SharingPolicy'.
Line 1309, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-SiteMailbox'.
Line 1310, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-SiteMailboxProvisioningPolicy'.
Line 1311, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Suspend-PublicFolderReplication'.
Line 1312, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-OrganizationRelationship'.
Line 1313, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-SiteMailbox'.
Line 1314, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-PublicFolder'.
Line 1315, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-PublicFolderHierarchy'.
Line 1316, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-PublicFolderMailbox'.
Line 1317, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-SiteMailbox'.
Line 1347, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Get-UmServer'.
Line 1348, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Get-UMService'.
Line 1350, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-UMAutoAttendant'.
Line 1351, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-UMCallAnsweringRule'.
Line 1352, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-UMDialPlan'.
Line 1353, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-UMHuntGroup'.
Line 1354, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-UMIPGateway'.
Line 1355, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-UMMailboxPolicy'.
Line 1356, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UMAutoAttendant'.
Line 1357, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UMCallAnsweringRule'.
Line 1358, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UMDialPlan'.
Line 1359, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UMHuntGroup'.
Line 1360, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UMIPGateway'.
Line 1361, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UMMailboxPolicy'.
Line 1362, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMAutoAttendant'.
Line 1363, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMCallAnsweringRule'.
Line 1364, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMCallRouterSettings'.
Line 1365, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMDialPlan'.
Line 1366, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMIPGateway'.
Line 1367, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMMailbox'.
Line 1368, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMMailboxPIN'.
Line 1369, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMMailboxPolicy'.
Line 1370, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UmServer'.
Line 1371, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UMService'.
Line 1372, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Test-UMConnectivity'.
Line 1396, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Get-UnifiedGroupLinks'.
Line 1397, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Get-User'.
Line 1400, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-EOPDistributionGroup'.
Line 1401, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-EOPMailUser'.
Line 1402, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-MailContact'.
Line 1403, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-MailUser'.
Line 1404, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.New-UnifiedGroup'.
Line 1405, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DistributionGroup'.
Line 1406, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DistributionGroupMember'.
Line 1407, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-DynamicDistributionGroup'.
Line 1408, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-EOPDistributionGroup'.
Line 1409, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-EOPMailUser'.
Line 1410, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-MailContact'.
Line 1411, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-MailUser'.
Line 1412, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UnifiedGroup'.
Line 1413, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Remove-UnifiedGroupLinks'.
Line 1414, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-Contact'.
Line 1415, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DistributionGroup'.
Line 1416, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-DynamicDistributionGroup'.
Line 1417, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-EOPDistributionGroup'.
Line 1418, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-EOPGroup'.
Line 1419, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-EOPMailUser'.
Line 1420, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-EOPUser'.
Line 1421, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-Group'.
Line 1422, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-LinkedUser'.
Line 1423, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-MailContact'.
Line 1424, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-MailUser'.
Line 1425, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-UnifiedGroup'.
Line 1426, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Set-User'.
Line 1427, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Undo-SoftDeletedUnifiedGroup'.
Line 1428, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-DistributionGroupMember'.
Line 1429, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Update-EOPDistributionGroupMember'.
Line 1430, Column 5: [Warning: xref-not-found] Cross reference not found: 'ExchangePowerShell.Upgrade-DistributionGroup'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 076cc70:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@chrisda, This PR is ready to check-in

Docs Build status updates of commit 6dc9d38:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9b9d99a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Update docs for kubedb/operator@960d2f93

Signed-off-by: 1gtm<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: 1gtm:x: kodiakhq[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


Best approach to redirect user if is authenticate

Hi! I need to check auth on some custom pages, for example, I created a custom LoginPage and I'd like to redirect the user if he tries to access login page already authenticated.
componentWillMout() {
  if (myHelper.isUserLogged()) {
   // redirect to dashboard
 }
}

In my opinion, the correct approach for handle this should be on Route config, following this example (https://reacttraining.com/react-router/web/example/auth-workflow):
<Route {...rest} render={props => (
    fakeAuth.isAuthenticated ? (
      <Component {...props}/>
    ) : (
      <Redirect to={{
        pathname: '/login',
        state: { from: props.location }
      }}/>
    )
  )}/>

The problem is I'm not using custom Login route because the original config for login is like:
<Route exact path="/login" render={({ location }) => createElement(loginPage || Login, {
  location,
  title,
  theme,
})} />

This route is using some props defined in Admin.js.
Any idea or opinion about what would be the best way to do this?
Thanks!

We don't provide support through GitHub issues. If you need advice on using or debugging your own project based on admin-on-rest, please use StackOverflow.


Proposal for a source-code cleanup with flake8

In order to follow pep8 guidelines.

Looks good, thanks!


Refactor Build container images page

Proposed changes
Review the docker-images page on the official documentation. Add link to the official docker images. Fix issues with existing commands.
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[ ] I have read the CONTRIBUTING document
[ ] I have run make install-tools and have attached any dependency changes to this pull request
[ ] If applicable, I have added tests that prove my fix is effective or that my feature works
[ ] If applicable, I have checked that any relevant tests pass after adding my changes
[ ] If applicable, I have updated any relevant documentation (README.md)
[ ] If applicable, I have tested my cross-platform changes on Ubuntu 22, Redhat 8, SUSE 15 and FreeBSD 13

I have hereby read the F5 CLA and agree to its terms

This all looks good. One thing for the "Run the NGINX Agent container" section. Should we give another command so an end user knows how to mount an nginx-agent.conf file?
When running docker run --name nginx-agent -d nginx-agent Agent has default config
Could provide this command to mount a user's nginx-agent.conf file
  -v /path/to/your/nginx-agent.conf:/etc/nginx-agent/nginx-agent.conf \
  nginx-agent


Pytorch interface, AnnDataLoader class

@flying-sheep , hi, i'm working on the interface using this pr as an example.

@flying-sheep Yes this is experimental for now, Phil. A lot of work is needed to make a good API out of this early draft.

Just closing for the time being. Can reopen soon!


How to expand context menu?

Hello I was wondering if anyone has a demo on how to expand the options of the context menu from a grid (the one that comes out when you right click the table)?
I've read the docs on modifying the context menu in the official AgGrid website in javascript/typescript but I don't know how to insert the js/ts code to get the desired behaviour in my streamlit app.
Any help/guidance is appreciated :)

Hey sorry, how are this issue and #180 completed? @PablocFonseca


fix: correct spelling mistakes in docs and readme

Thanks!

Thank you for such an awesome plugin!


Update the Readme file of the project.

The readme file of the project is blank and needs to be updated.

Hey, I am interested in fixing this issue.
Assign to me

Is this issue still active?
Interested to  work on it

@amiii123malviya  nah Its not active


Android and IOS Port

What feature do you want to get added on the base engine?
If this is possible make a Android and iOS port!

i dont think he will

there is a fanmade android port being made already, https://github.com/jigsaw-4277821/Psych-Engine-Android-Port/issues
apk: https://drive.google.com/file/d/1PI69tmcBK6IPdSmfwaRD7n7wBri8WDdM/view

just add mouse compatability and and export to android/ios lmao


Remove dart source dependency from the Fuchsia tree

Mirror of fxb/51910

All dependencies have been removed, just need to update the rollers to not reference them anymore.


Can't add Let's Encrypt to Domain

I had never problems since several months with the plugin, I have almost 30 domains with the certificate but after two weeks I can't install certificates anymore, I got this:

Error: Let's Encrypt SSL certificate installation failed: Challenge marked as invalid. Details: Could not connect to hmt.pt

Checking the logs: AH01909: RSA certificate configured for hmt.pt:443 does NOT include an ID which matches the server name

I  have made no changes on the server unless the regular Plesk Updates....

Seems yet another IPv6 issue... see #171
https://www.ssllabs.com/ssltest/analyze.html?d=hmt.pt&latest - also reports "Unable to connect to the server"

Yes I've removed ipv6, connected Let's Encrypt and added ipv6 again, not sure what's wrong with those settings as it worked before. Will check with the hosting. Thanks.

Take into account that DNS has TTL and your changes are not applied immediately.
Let us know if the problem is solved or not.

I've disabled the IPV6, activated Let's Encrypt successfully and enabled again IPV6. The hosting guys are investigating if something wrong with out IPV6 but they say no but it appears otherwise, Still waiting for their answer.


Update project for K1 usage

Subsystem
Compiler plugins, Gradle configurations
Problem Description
While implementing K2, some temporary adjustments were made, disabling K1 compilation, while making K2 development process easier.
Solution
Enable K1 back (via KSP), but now alongside with K2

It's TC config problems, will address soon


Gradle not hiding captured output when running in parallel

Based on this issue: https://discuss.gradle.org/t/logging-capturestandardoutput-does-not-capture-all-stdout-when-running-in-parallel/1147 which leads to this issue: https://issues.gradle.org/browse/GRADLE-3000, I decided to file this issue on Gradle's github. I am not sure if this plugin is using the correct API to capture standard output or there is a bug in Gradle for parallel builds.
Expected Behavior
Gradle task should capture log output when running in parallel. See this Github issue: https://github.com/apollographql/apollo-android/issues/549 and the PR to try and fix this issue: https://github.com/apollographql/apollo-android/pull/323. The "fix" is using getLogging().captureStandardOutput(LogLevel.INFO);. Should the plugin be using https://github.com/gradle/gradle/blob/master/design-docs/features/composite-build/tooling-api/capture-output.md#overview?
Current Behavior
Gradle task log output is shown when running in parallel.
Context
When the output from the task is shown, they show up as errors in the IDE.
Steps to Reproduce (for bugs)
Set up plugin and run your build with --parallel

Maybe we can start by reproducing the issue with a simple example? The issue seems to surface in a relatively complex environment: A plugin applying another plugin, that plugin calls of to Node and then the error showing up in Android Studio. It's somewhat hard to follow what's going on here.

The "fix" is using getLogging().captureStandardOutput(LogLevel.INFO);.

Is this working? I believe what happens is that any standard output will only be rendered when you run the build with INFO log level. I believe you'll just run into https://issues.gradle.org/browse/GRADLE-3000 which needs fixing.

Should the plugin be using https://github.com/gradle/gradle/blob/master/design-docs/features/composite-build/tooling-api/capture-output.md#overview?

Sorry, I am not familiar with that spec or the functionality but I don't think you'll want to use the tooling API for that purpose.

@bmuschko You are right about the complex example. getLogging().captureStandardOutput(LogLevel.INFO); seems to only work if I turn off Gradle's parallel compilation.
I also believe you are correct about https://issues.gradle.org/browse/GRADLE-3000. I am not sure if the new spec is implemented or not. Should I make a new issue for Gradle-3000 or is there already one on Github for it?

I'd suggest we try to see if the underlying issue is the one described in GRADLE-3000 and then change this issue accordingly.

@bmuschko I believe it is that issue. However, after upgrading to Gradle 4.1-rc-1, here is all that I am seeing:
> Task :yammer-data:installApolloCodegen
<EMAIL_ADDRESS>/Users/jaburrow/repo/android2/yammer-data/build/apollo-codegen
`--<EMAIL_ADDRESS>
https://github.com/apollographql/apollo-android/issues/549#issuecomment-317815580

Any updates here? We're seeing the same on cloudbees-jenkins builds with a lot of logging getting suppressed.