Why is VSCode uploading every HTTP request to Microsoft servers?

VSCode Version: 1.13.1
OS Version: Linux x64

Having noted a lot of entries in my firewall log, it seems that every http.get() executed in my extension results in the full URL being uploaded to Microsoft via ApplicationInsights.
This happens, even when all extensions are disabled, the following Telemetry options turned off in Settings and VSCode restarted:
"telemetry.enableTelemetry": false,
"telemetry.enableCrashReporter": false

Example code:
const http = require('http');
http.get('http://<IP_ADDRESS>/some/path?with=data', r => {});

Results in the following ApplicationInsights log file being created in /tmp/appInsights-node/ (shortened for brevity)
{"ver":1,"name":"Microsoft.ApplicationInsights....RemoteDependency","time":"2017-06-26T19:03:13.374Z","sampleRate":100,"tags":{"ai.application.ver":"0.0.1","ai.device.id":"","ai.cloud.roleInstance":"**my_machine_name**","ai.device.osVersion":"**my_os_version**","ai.device.osArchitecture":"x64","ai.device.osPlatform":"linux","ai.internal.sdkVersion":"node:0.18.0","undefined":""},"data":{"baseType":"Microsoft.ApplicationInsights.RemoteDependencyData","baseData":{"ver":2,"success":true,"properties":{},"measurements":{},"type":"Http","target":"<IP_ADDRESS>","name":"GET /some/path","data":"**http ://<IP_ADDRESS>/some/path?with=data**", "duration":"00:00:00.168","resultCode":"200"}},"appVer":"0.0.1","iKey":"AIF-...","os":"Linux","osVer":"my_os_version","seq":"..."}

As you can see highlighted in bold, the full URL and data is included along with my machine name (the resolved <IP_ADDRESS> IP).
All of this appears to be uploaded to vortex.data.microsoft.com
Can you explain why Microsoft needs to log every single http request and how to turn this off?

We had "fixed" the problem on April 18th with https://github.com/Microsoft/vscode-extension-telemetry/commit/186b03f818d13c6debde3054c178496e7fe151b8. However, the npm module we uploaded did not contain the fix.... The latest version of vscode-extension-telemetry - that's version 0.0.8 - has the fix in it and we upgraded to the new version in 3f8bd163f4a9f33000e075515b4555159edec871.
If you own extensions, you would need to update to 0.0.8 as well and republish them.


Code review for ohtwo

Thought I'd take a look around ohtwo.  Creating an issue here to track my thoughts, related issues, any minor commits I make, etc.

ohtwo is master now, and more of the team is getting a chance to review.  I think this issue is good to close.


Invalid condition for non-string user objects

In the constructor of TreeNode, the check for the type of userObject (is it string or an object with a toString function) is wrong.
Currently if the userObject is a string, it checks if it has a toString function (it does).
If the userObject is not a string, it errors, without checking the toString function.
 I'll fix it asap. Thanks!


Proposal: Proxy http requests via node in dev.

@mkitt @rynbyjn I started digging into https://www.pivotaltracker.com/story/show/144530371, however with our sophisticated (read: complicated & clever) gateway code handling CORs there also was going to be difficult and verbose.
This is a proposal to handle the CORS issue an alternative way: don't use CORS in dev. The browser can hit the dev server (localhost:6660) and have requests proxied by node to the appropriate API. This would allow us to remove all CORS code across Mothership and Apex.
What do you think?

BTW, I just sorta hacked it in here to get it working in dev, but if you guys are good with this idea we can discuss the approach.

I dunno why the iso tests are failing.

@alanpeabody just needed to stub out one more variable and the tests were good to go!

OHHH. I thought those were stubbing the process env vars, which shouldn't be required. Thanks Jay.
@mkitt @rynbyjn any other changes you would like to see on this?

Looks good to me.


Darwin audio hal

This is not meant to be merge ready, this is only here for initial feedback -

Adds initial audio hal implementation for darwin
Adds (very poorly implemented) darwin_player.go
Links the audio callback from C to Go (the most important part)

TODOs - get decent audio playing (the commented out Float Sin wave does work and has 0 glitches)
@hajimehoshi @faiface please let me know your initial thoughts.

Other Todo:
Discuss and decide where to implement Circular buffer. ALSA provides this functionality as part of its implementation but AudioHAL does not. We have two options - we can implement it in Go or we can implement it in C. https://github.com/michaeltyson/TPCircularBuffer is a respected buffer written in C that was written specifically for working with audio, and I've experimented a bit with it already, but that doesn't mean we have to use it. It introduces more C dependencies, so I'm wary of doing that right now.

Hi @alistanis , if you are busy, I'll take over this PR. Thanks.

Outdated.


Text stays black on dark mode

At some point, the text stopped beeing displayed white when dark mode is activated. Now the text blends in the background and is not readable:

This is fixed in the latest update (v0.12.0)


Isn't Power BI missing in the list of supported services?

Hi,
according to this article (https://learn.microsoft.com/en-us/power-bi/enterprise/service-admin-power-bi-security-lockbox) Power BI can be used with Customer Lockbox for Azure. But in the list of supported services by Customer Lockbox, Power BI is missing. Is it supported or not?
Best regards,
Martin
[Enter feedback here]

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

ID: 985eab9b-60f7-480a-c649-1fd7c6105646
Version Independent ID: 4d5bbc09-fa5a-c67e-b4b8-75a5229506c0
Content: Customer Lockbox for Microsoft Azure
Content Source: articles/security/fundamentals/customer-lockbox-overview.md
Service: information-protection
Sub-service: aiplabels
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@obungimartin
I've delegated this to @msmbaldwin, a content author, to review and share their valuable insights.

We sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Nginx Ingress Option not accepting traffic

When deploying nginx as a ingress controller, and creating a ingress resource, traffic the traffic is not avaiable.
To Reproduce, deploy a cluster with nginx ingress controller

@kubernetes/ingress-nginx#9601

to resolve, add the following value (on bold) to the post deploy.  Need to do more testing
helm upgrade --install ${nginx_helm_release_name} ingress-nginx/ingress-nginx
--set controller.publishService.enabled=true
--set controller.metrics.enabled=true
--set controller.service.annotations."service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path"=/healthz
--namespace ${nginx_namespace}

I can't seem to repro, but it looks like an easy addition to post deploy.

I think this is more workload related,  because the standard dotnet new webapi doesnt respond on the root path / the nginx controller SLB heath check endpoint is '/' so the traffic is not getting through.
I'll close this, but its good for a reference.


Add support for commonjs ?

Please do if you need it, i don't even know how it works.

It works, but i have some troubles with Color Thief. When i tried to move crop area, i've got next error:
angular.min.js?6335:118 ReferenceError: ColorThief is not defined
    at getDominantColor (eval at <anonymous> (vendor.js:9), <anonymous>:2979:34)
    at updateResultImage (eval at <anonymous> (vendor.js:9), <anonymous>:3182:38)
    at eval (eval at <anonymous> (vendor.js:9), <anonymous>:3300:21)
    at eval (eval at <anonymous> (vendor.js:9), <anonymous>:3229:29)
    at m.$eval (eval at <anonymous> (vendor.js:2), <anonymous>:145:347)
    at m.$apply (eval at <anonymous> (vendor.js:2), <anonymous>:146:52)
    at m.$delegate.__proto__.$apply (<anonymous>:855:30)
    at eval (eval at <anonymous> (vendor.js:9), <anonymous>:3228:31)
    at eval (eval at <anonymous> (vendor.js:2), <anonymous>:158:494)
    at e (eval at <anonymous> (vendor.js:2), <anonymous>:45:444)

But app doesn't crash.

@IuriiKryventsov ColorThief is not export for commonjs !

I'm trying to use ngImgCrop with browserify but everytime I try to inject I got a "Unknown provider: ngImgCropProvider <- ngImgCrop"

I thought there was/is no provider.
I do think your DI is wrong.

How do you compile your node modules? If you are using webpack there is a solution to this problem. I've notice that there is a problem on exporting/importing the ColorThief module on ng-img-crop module. I think the problem is that ColorThief rely on global variables like $ or this being the window object. If you use webpack you can fix this by using the import loaders and add this to your webpack.config.js on your loaders config.
{
  test: require.resolve('ng-img-crop-full-extended'),
  loader: 'imports?define=>false,exports=>false,this=>window'
}

The package is compiled with Gulp. It smashes all JavaScript together to a desired package.
I would like to hear about why we should use webpack. At a company where i work we also investegated Webpack

I have tried webpack, never liked it.

This repo is dead.
Please move to the other project:
https://github.com/CrackerakiUA/ui-cropper


Standardize Logging in the SMA

The System Mgmt Agent should use the standard Logging Client that all EdgeX services use and not utilize log.Println or log.Printf. An example of how to accomplish this is provided here:
https://github.com/tsconn23/edgex-go/tree/issue_763_tsc

The one-and-only reason why Go's built-in (overly-rudimentary) logging (viz. log.Fatal()) was used in the first place has to do with how the package structuring that was not allowing the import of the clients/logging package.
Looking forward to addressing this issue 👍


Fix obfuscation type, download link

https://github.com/rancher/rancher/issues/6619

https://github.com/rancher/rancher/issues/6468


Test the CustomLoginPage example for functionality

Test the CustomLoginPage example for functionality

Tested CustomLoginPage and found errors. Details in #9


Add podDistruptionBudget resource for controller pods

Objective
This PR add a podDistruptionBudget resource to the helm chart in order to better run the controller pods in HA. I chose to add both the minAvailable and maxUnavailable fields, though the later does required k8s 1.7+. Lastly I bumped the chart version by a patch version.
Testing Done
Deployed on local cluster and ensured labels matched up correctly.

@mumoshu I'd love a review on this if you get the chance!

Could you add this for the webhook server also?


WIP: Added code to get company name and server version.

Description
[Please describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]
Check List

[ ] New functionality includes tests
[ ] All buildkite tests pass
[ ] Full omnibus build and tests in buildkite pass
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/main/CONTRIBUTING.md#developer-certification-of-origin-dco
[ ] PR title is a worthy inclusion in the CHANGELOG

Adhoc: https://buildkite.com/chef/chef-chef-server-main-omnibus-adhoc/builds/6469

@sreepuramsudheer  Looking for sql changes for postgres table changes. Any other PR to be reviewed for these sql changes?

@sreepuramsudheer Needs to add tests.

Automate pipeline : Green
https://buildkite.com/chef/chef-automate-main-verify-private/builds/35288


deprecation warnings on node 10.13.0

$ npm i sleep

><EMAIL_ADDRESS>install /private/tmp/some/node_modules/sleep
> node-gyp rebuild

  CXX(target) Release/obj.target/node_sleep/sleep.o
In file included from ../sleep.cc:2:
In file included from ../../nan/nan.h:222:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:340:28: warning: 'New' is deprecated [-Wdeprecated-declarations]
  return v8::StringObject::New(value).As<v8::StringObject>();
                           ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8.h:5052:3: note: 'New' has been explicitly marked deprecated here
  V8_DEPRECATED("Use Isolate* version",
  ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8config.h:327:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated))
                            ^
In file included from ../sleep.cc:2:
../../nan/nan.h:1066:44: warning: 'ToString' is deprecated [-Wdeprecated-declarations]
      v8::Local<v8::String> string = from->ToString();
                                           ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8.h:2454:10: note: 'ToString' has been explicitly marked deprecated here
  inline V8_DEPRECATED("Use maybe version", Local<String> ToString() const);
         ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8config.h:327:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated))
                            ^
In file included from ../sleep.cc:2:
../../nan/nan.h:1080:27: warning: 'WriteUtf8' is deprecated [-Wdeprecated-declarations]
        length_ = string->WriteUtf8(str_, static_cast<int>(len), 0, flags);
                          ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8.h:2658:3: note: 'WriteUtf8' has been explicitly marked deprecated here
  V8_DEPRECATED("Use Isolate* version",
  ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8config.h:327:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated))
                            ^
../sleep.cc:81:19: warning: 'Uint32Value' is deprecated [-Wdeprecated-declarations]
  _sleep(info[0]->Uint32Value() * 1000000);
                  ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8.h:2477:3: note: 'Uint32Value' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", uint32_t Uint32Value() const);
  ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8config.h:327:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated))
                            ^
../sleep.cc:94:19: warning: 'Uint32Value' is deprecated [-Wdeprecated-declarations]
  _sleep(info[0]->Uint32Value());
                  ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8.h:2477:3: note: 'Uint32Value' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", uint32_t Uint32Value() const);
  ^
/Users/takumakoge/.node-gyp/10.13.0/include/node/v8config.h:327:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated))
                            ^
5 warnings generated.
  SOLINK_MODULE(target) Release/node_sleep.node
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 2 packages from 9 contributors and audited 2 packages in 4.975s
found 0 vulnerabilities

refs https://github.com/nodejs/nan/pull/811

I don't want to just add a flag to ignore all deprecation warnings. This is an issue in NAN and should be fixed there.


merge branch master of MoienTajik/Specification with ardalis/Specification

Fixed some typos and applied some rename refactorings
Removed unused using statements from project
Updated test projects to .NET Core 3.1
Upgraded test projects packages
Migrated IntegrationTest's EF underlying provider from SqlServer to in-memory database
And some little enhancements ...

Thanks for the PR @MoienTajik. I prefer to keep protected fields prefixed with _ even though I know that doesn't correspond with  official guidance, which uses the same format for public and protected. protected is much closer to private than it is to public. Constants also should be ALL_CAPS. This got old so there are conflicts (my fault -sorry). If you want to resolve them, pull in the latest master, and stick to the conventions I'm using, I'd take the PR. If not I understand. Thanks!


Consider using exposeFunctions for injected scripts

https://github.com/GoogleChrome/puppeteer/blob/v1.13.0/docs/api.md#pageexposefunctionname-puppeteerfunction

Will not work as only a function can be exposed


"Distance by boat" statistic doesn't increment

Using tfc boats doesn't count towards this statistic, it probably should

I'll look into it!


a bigger "show output" ?

as show in below picture, possible to have the show ouptup extended to all empty section in bottom? just to utilize the display output.

and how it would work when you have not one but many transfers and let's say you expand two outputs and scroll the list?

i guess, perhap when you show MountA, it automatically hide MountB?
another scroll seems make very messy, scroll inside scroll? maybe not a good idea.

yes it is definitely doable in some way but I don't see real benefit. Most people probably look at it sporadically or in case of troubleshooting.

if somebody considers it important I am happy to accept PR

so let's keep it on enhancements list - maybe somebody will do it

yeap thanks man, i am aware this only useful for debug purpose looking at the log with rclone -vv.

I am working on next release with a lot of new features - if you would like to try latest pre-release link is in the first post in #93 thread


Invalid authentication

Hey,
no sure if this is actually an issue or something else.
I tried to configure/connect to "Moj Elektro", but I always get Invalid Authentication response.
I did write simple python script or trying Moj Elektro Testing page, both works fine, using same Token and meter device ID.
Anyone facing same issues?
Thanks,
Rok

It could be related on you specific meter. Please use this code in configuration.yaml:
logger:
  logs:
    custom_components.mojelektro: debug

Restart and then try to setup integration. After that track logger in home-assistant.log file and post log regarding mojelektro here. Please hide any meter id info!

HA_mojelektro.txt
Seems like integration reads some data, but not sure what is reason for authentication failure.
Rok

It seems it's related to this issue: https://github.com/frlequ/homeassistant-mojelektro/issues/39
Please update to the latest version, which resolves this issue: https://github.com/frlequ/homeassistant-mojelektro/releases

Yes, I can confirm, after update works OK. Thanks for your help


Cloud9 failing to reconnect to instance

After a Cloud9 timeout it is no longer possible to  reconnect to the Cloud9 instance.
Appears to be related to a move to SSM for connecting to instances, which requires the correct IAM permissions (specifically the managed policy AmazonSSMManagedInstanceCore) to be included in the EC2 instance IAM role.
Note: Cloud9 now attaches a role with this policy this by default, but we are replacing this default role with the gitops-workshop role plus a restricted set of permissions.

Cleaning-up issues; this is addressed as part of PR: https://github.com/aws-samples/eks-multi-cluster-gitops/pull/68.


twitter bot: Links not showing up in echoed tweets?

This tweet: https://twitter.com/zulip/status/895473932278431744

shows up as the following on https://chat.zulip.org/#narrow/stream/twitter/subject/zulip/near/265158

Namely, the chat.zulip.org version doesn't have the docs.google.com link.
I'm also not sure why it has the https://twitter.com/i/web/status/895473932278431744 link .. is that the link to the attached image?

@HarshitOnGitHub is this something you can look into?  Now that I understand the issue a bit better, it's clearly going to be on the Bugdown side of things.

@timabbott This one seems to be interesting! Looking into it. Retweets of the mentioned tweet are rendering properly:
https://chat.zulip.org/#narrow/stream/test.20here/subject/long.20links/near/265858
https://chat.zulip.org/#narrow/stream/test.20here/subject/long.20links/near/265859

I digged into this a little bit and results are a bit perplexing. I fetched the tweet data for the mentioned tweet and a retweet for checking out what's going. The urls key in the fetched data had different urls for tweet and retweet. Further the rendered tweet seemed to be in accordance to what was given to the bugdown processor so to me this seems to be a quirk on twitter's side. I think we can safely close this @timabbott.
For reference here is the urls key from data for the two tweets:
Original tweet:
    "urls": [
      {
        "url": "https:\/\/t.co\/k4uBodrNwg",
        "expanded_url": "https:\/\/twitter.com\/i\/web\/status\/895473932278431744",
        "display_url": "twitter.com\/i\/web\/status\/8\u2026",
        "indices": [
          105,
          128
        ]
      }
    ]

A random retweet:
      "urls": [
        {
          "url": "https:\/\/t.co\/EEFwXCwGEX",
          "expanded_url": "https:\/\/docs.google.com\/forms\/d\/e\/1FAIpQLSd-atYzq0o4cygxtntXgYHt21Cjte2xGjxXlMcLuBUuhybNXg\/viewform?usp=sf_link",
          "display_url": "docs.google.com\/forms\/d\/e\/1FAI\u2026",
          "indices": [
            115,
            138
          ]
        }
      ]

Hmm, OK, yeah, sounds like a bug on Twitter's end.  Thanks for investigating!


Error:java: NullAway is not a valid checker name in IntelliJ

Mac OS X Mojave
OpenJDK 10.0.1
Error Prone 2.3.2
Error Prone Gradle Plugin 0.6
Nullaway 0.6.0
IntelliJ IDEA 2018.2.4
Error Prone IntelliJ IDEA Plugin 182.3911.36(Error Prone 2.3.1)

plugins {
    id("net.ltgt.errorprone") version "0.6"
}

apply plugin: 'java'

sourceCompatibility = 10

repositories {
    mavenCentral()
}

dependencies {
    compileOnly "com.google.code.findbugs:jsr305:3.0.2"
    errorprone group: 'com.google.errorprone', name: 'error_prone_core', version: '2.3.2'
    annotationProcessor group: 'com.uber.nullaway', name: 'nullaway', version: '0.6.0'
}

import net.ltgt.gradle.errorprone.CheckSeverity

tasks.withType(JavaCompile) {
    options.errorprone {
        check("NullAway", CheckSeverity.ERROR)
        option("NullAway:AnnotatedPackages", "src")
    }
}

Gradle's compileJava task works fine!
but IntelliJ IDEA's Javac with error-prone compiler not works.
-XDcompilePolicy=byfile -Xep:NullAway:ERROR -XepOpt:NullAway:AnnotatedPackages=src

Error:java: NullAway is not a valid checker name
How can I fix it?

@perfectacle did this ever work for you inside IntelliJ, or is this the first time you are trying?  I wonder if IntelliJ is not setting the processor path correctly.  @tbroyer any ideas here?

@msridhar It is first time
-XDcompilePolicy=byfile

It works fine (without any checker)

IntelliJ doesn't automatically configures the processor path from Gradle builds. There's an open issue on JetBrains side (https://youtrack.jetbrains.com/issue/IDEA-187868), but for now you'd have to configure the processor path manually (suggested workarounds wouldn't work for Error Prone custom checks).
Fwiw, I simply delegate build/run actions to Gradle, specifically so that I'm sure I don't have different configurations between the IDE and the actual build.

Ok, I'm going to close as this is an IntelliJ issue

Fwiw, I simply delegate build/run actions to Gradle, specifically so that I'm sure I don't have different configurations between the IDE and the actual build.

Could you elaborate? How can I do this too?

See https://www.jetbrains.com/help/idea/gradle.html#delegate_build_gradle

Okay, I tried that and now I just realized it's only failing for my unit tests, and it still fails even for gradle command line builds for my android project.
Should I open a new issue for this?
Some more information:
My build.gradle
./gradlew --version

------------------------------------------------------------
Gradle 5.2.1
------------------------------------------------------------

Build time:   2019-02-08 19:00:10 UTC
Revision:     f02764e074c32ee8851a4e1877dd1fea8ffb7183

Kotlin DSL:   1.1.3
Kotlin:       1.3.20
Groovy:       2.5.4
Ant:          Apache Ant(TM) version 1.9.13 compiled on July 10 2018
JVM:          10 ("Oracle Corporation" 10+46)
OS:           Mac OS X 10.14 x86_64

./gradlew testDevDebugUnitTest
> Task :app:compileDevDebugUnitTestJavaWithJavac FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDevDebugUnitTestJavaWithJavac'.
> NullAway is not a valid checker name

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.2.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 1s
37 actionable tasks: 1 executed, 36 up-to-date

You're adding NullAway only to annotationProcessor, but applying NullAway options to every JavaCompile tasks, including those for tests, which won't have NullAway in their processor path.
Either add NullAway to the errorprone configuration (instead of annotationProcessor) to have it available everywhere; or change your build to only configure NullAway for the main variant (no idea how to do this though, I don't know the Android Gradle Plugin much)

ah okay, that makes sense. Thanks.
For now I'll remove it for tests following the sample gradle instruction:
tasks.withType(JavaCompile).configureEach {
    if (!name.toLowerCase().contains("test")) {
        // add for test only
        options.errorprone {
            // ...
        }
    }
}

This is good for now. I'll revisit later.


MINOR: Change groupInstanceId type from Optional to String in ConsumerGroupMetadata and GroupRebalanceConfig

There is Optional groupInstanceId field in ConsumerGroupMetadata class and GroupRebalanceConfig class and that is one of the Optional anti-patterns so I changes to String and use getter method to return Optional type.
Add new ConsumerGroupMetadata constructor for if groupInstanceId not used.

Thanks @il-kyun for the patch. I looked into it and I don't think that the change is worth it. Using Optional here seems fine to me. I am going to close it for now. Feel free to reopen if needed.


Welcome Grab, a new KEDA user!

Signed off by Karan Kamath -<EMAIL_ADDRESS>FYI @dttung2905

@zroubalik This is what I mentioned about the other day. Could you help to review it ?
Thanks Thang for helping with the PR 😜

You can see the steps to fix DCO in the check link:

Thank you both for the guidance 🙏 I have fixed the DCO check. There is one last required check that has been stuck for quite some time Mixed content - keda, is there anything I can do to fix it?

@zroubalik This is what I mentioned about the other day. Could you help to review it ?
Thanks Thang for helping with the PR 😜

Awesome! 🚀

Thank you both for the guidance 🙏 I have fixed the DCO check. There is one last required check that has been stuck for quite some time Mixed content - keda, is there anything I can do to fix it?

Ignore it :)

Thank you :)

❤


Add: Let’s Encrypt support

It would be great to have a fully automated support of Let’s Encrypt.
That would ease HTTPS management a little bit more.

Checkout https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion
If someone could figure out how to get it all connected in a compose file and write something up.

Usually people use the let's encrypt on the edge nginx instances, which usually proxy through the request.
So in my opinion this is not needed in this project.

I quite agree with that. Maybe it could simply be a small how to included into the documentation.

@Maescool thats right but this should also run indipendent as we bundle nginx.

@frank-dspeed I'm with @Glideh.  If we can find a way to do this using a separate, preferably existing, container and just provide an example.  I think that would be best but I'm not sure of the complexity of the different options.

@Glideh @jcormier this is related to a lot of other issues will keep you informed in this issue about that simply give me some time :)

It's actually pretty simple using docker-gen and docker companion example: https://gitlab.intra.glego.be/docker/redmine-nginx-letsencrypt

@glego i don't like the jswilder image.

How do I use docker-gen and docker companion example: https://github.com/glego/redmine-nginx-letsencrypt/ as a template for the sameersbn/docker-redmine image?

Closed due to old age

For Redmine and LetsEncrypt(Certbot) only without external nginx: https://github.com/sameersbn/docker-redmine/issues/197#issuecomment-1846622553


Add support for supportsHtml on markdown strings

VS Code is getting a flag on MarkdownString to say whether (some basic subset of) HTML can be rendered in addition to markdown:
https://github.com/microsoft/vscode/issues/40607
I think it would be useful to support in LSP for the same reason it makes sense there. Some languages let users write their docs in Markdown and they might also include some HTML, but right now it renders literally in the tooltips which is unexpected.

Note also that both the very original Markdown invention and the CommonMark spec (the de-facto Markdown standard) clearly allow HTML within Markdown, it's a core part of the idea behind Markdown. I.e. this is not a non-standard syntax "extension".

https://daringfireball.net/projects/markdown/syntax#html
https://spec.commonmark.org/0.30/#html-blocks

It does make sense to add this to LSP. However a client needs to announce the list of supported HTML tags. For VS Code they are defined here: https://github.com/microsoft/vscode/blob/6d2920473c6f13759c978dd89104c4270a83422d/src/vs/base/browser/markdownRenderer.ts#L296

PR welcome.

Implemented and added to the spec.

@dbaeumer how does this support work? In 14f7c980e35717cdcaf7dce8dd5d2df0881d1e11 I see the client can advertise which tags it supports, but I don't see a way of passing supportsHtml on the MarkdownString to VS Code. Does it require changes in the LSP Client to set this?

For VS Code this is handled the same way as isTrusted. You specify whether this is supported via a setting in the client options. See https://github.dev/microsoft/vscode-languageserver-node/blob/e22c9bdd485d36b77cdf70fd4b34e6928822ebfe/client/src/common/client.ts#L579

Ah, got it - thanks!

@dbaeumer I don't suppose there's an approx ETA for 3.17? I thought I saw it noted in previous VS Code release notes as being published, but the site still shows 3.16 as current.

It is not publish. We did publish new next releases with proposed support for notebooks.

The plan is to have a new 3.17 release the next ~ 2 month

Got it, thanks! :)

Just to check as a user who wants to consume documentation that uses inline HTML, when the new release comes out in 2 months, tags should no longer disappear in VSCode Intellisense results?
I'm having trouble finding my original issue, but I came here from https://github.com/microsoft/vscode/issues/40607 -- that was resolved last year but hasn't fixed the rendering problem; I think it was only part of the puzzle.

Thanks for the link.  Do you know (or know how to tell) when that lands in a VSCode release?  I'm just trying to figure out when the symptom (large portions of some docs are completely removed) is going to be resolved for end users, without getting passed around between the Language Service people and the VSCode people and the TypeScript people.

@thw0rted As far as I can see, the typescript-language-features extension doesn't even use the LSP client. The issue you're describing would be with that bundled extension and possibly extends to the TypeScript language service it uses. It's not an issue with the LSP spec or that LSP client.

@dbaeumer

The plan is to have a new 3.17 release the next ~ 2 month

We're approaching 2mo from this comment - is the plan still to publish 3.17 in the near future? (not after a commitment, but a rough estimate will help me plan, there are a few things in 3.17 that would help with some things I'm working on). Thanks :)

Yes, still the plan. I am waiting for 2 APIs to be finalized in VS Code (which already happened in insider) and then I am good to go beginning of Mai..

Great, thanks!


fix: rewrite transformer(OOXML->CiceroMark)

Signed-off-by: K-Kumar-01<EMAIL_ADDRESS>This PR deals with rewriting the current OOXML transformer so that it supports nesting.
Changes
Major changes will be as follows:

Use DFS to traverse nodes
Generate node using the properties stored.
compare adjacent nodes for common properties(first n) and nest the second one into the common depth.

Author Checklist

[x] Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
[x] Vital features and changes captured in unit and/or integration tests
[x] Commits messages follow AP format
[ ] Extend the documentation, if necessary
[ ] Merging to master from fork:branchname

@algomaster99 @dselman
I have made the commit for OOXML Transformer. The tests will fail as of now.
The PR is made so that I can get a review on the logic used.

If the tests fail, there must be something wrong with the logic. Let the tests speak for your code. That's why I stress on rigorous testing. The more unique test cases you add, the better your code becomes.

If the tests fail, there must be something wrong with the logic. Let the tests speak for your code. That's why I stress on rigorous testing. The more unique test cases you add, the better your code becomes.

By test fail, I mean that the current transformation is not complete, so for that the test fail. For the conversion text-and-emphasis, it passes.

@algomaster99 @dselman
Requesting your reviews. The rewriting of the transformer is completed. It passes the previous tests and also the nesting.json test which was added in the PR

@algomaster99
Updated the changes.

@algomaster99
I apologize. I understood the wrong case. This test is for the line 195.
As for the above-mentioned, previously it was done as I did currently. Hence, I did not change. Should I change it?

@algomaster99
Made the naming changes. Let me know if there are any changes required.

As for the above-mentioned, previously it was done as I did currently. Hence, I did not change. Should I change it?

Didn't get you. Could you please be more clearer?

As for the above-mentioned, previously it was done as I did currently. Hence, I did not change. Should I change it?

Didn't get you. Could you please be more clearer?

I mean you also checked for the name, variable and type and then only defined that as variable.

I mean you also checked for the name, variable and type and then only defined that as variable.

Well, you are here to improve the code, right? If the justification of your change is "Aman has done like that", you won't be able to improve it much. I wrote a broken transformer last year but take inspiration from it and please question things if they are now necessary or not.

I mean you also checked for the name, variable and type and then only defined that as variable.

Well, you are here to improve the code, right? If the justification of your change is "Aman has done like that", you won't be able to improve it much. I wrote a broken transformer last year but take inspiration from it and please question things if they are now necessary or not.

Sure, but I also have a doubt regarding this. Let's say anyone who used docx first and then he wanted to convert to ciceroMark.
Also, he/she didn't gave any name or type. Then will it be a variable?

he/she didn't give any name or type

That's only possible when someone is writing the entire OOXML on their own. Or generating it and purposefully deleting its attribute. In both cases, it's the client's fault and we cannot do anything about it.

@algomaster99
Let me know if any changes are required.

@algomaster99
Tried renaming the files.
I tried using should-parse but later gave up as it unnecessarily made the text file long.


Discussion: Make hawck-input user a system user

I've noticed that newly created user gets its own entry in login manager, and was wondering if creating user as system user, rather than normal one without home, is both viable and secure for use-cases that this app introduces.

This is definitely a bug, the hawck-input user should have its shell set to /bin/nologin, I'll be updating the install scripts to do this.

Should be resolved as of 4fff45c2de8115da5f51dcd5d27f55490f9ae921 in the AUR and 2eded86867df31013d00b0a7b6692f7a01472bba which updates the AUR submodule in this repo.

I installed this recently on KDE Neon, and this still happened to me. I assume I got the latest version, so this might not be fixed properly.

@rbits0 Can you post the output of grep hawck /etc/passwd?

// grep hawck /etc/passwd
hawck-input:x:1001:1001::/var/lib/hawck-input:/bin/nologin

I second this. I installed this on KDE and it created a new login user.


Update the store without re-rendering elements

Thank you for the project.
I have a HTML text area and I store its contents in the store every time the value changes. The re-rendering for every character causes visible lag.

  <CodeMirror
    value={store.code}
    options={{
      mode: "xml",
      lineNumbers: true
    }}
    onChange={(editor, data, value) => {
      store.code = value;
    }}
  />

How do I go about preventing the re-rendering using react-recollect?

If you want to use an input where the contents don't come from props (or state), that's called an 'uncontrolled component'.  https://reactjs.org/docs/uncontrolled-components.html
For example, if you only want to write the data to the store once the input loses focus, something like this works:
const App = ({ store }) => {
  const ref = useRef();
  return (

      <textarea
        ref={ref}
        onBlur={e => {
          store.code = ref.current.value;
        }}
      />

{JSON.stringify(store, null, 2)}

  );
};

CodeSandbox: https://codesandbox.io/s/recollect-issue-90-3i9v9

Thank you for getting back to me. This is a text area that has a default value from the state- but this value changes when the user switches tabs. I've created pull request #91 that attempts to solve this.

How do I go about preventing the re-rendering using react-recollect?

As discussed in pull request #91 this feature would do more harm than help.

FYI @Kycermann I've been checking out CodeMirror to see if there's any compatibility issues in general, and all looks OK. Performance is great with this setup (controlled component), including external changes updating the code.
import React from 'react';
import { Controlled as CodeMirror } from 'react-codemirror2';
import 'codemirror/lib/codemirror.css';
import 'codemirror/theme/material.css';
import 'codemirror/mode/javascript/javascript';
import { collect, initStore } from 'react-recollect';
import './styles.css';

initStore({
  value: `const foo = 'bar'`
});

const App = ({ store }) => (
  <React.Fragment>
    <button
      onClick={() => (store.value = `// This is a comment\n${store.value}`)}
    >
      Prepend comment
    </button>

    <CodeMirror
      options={{
        mode: 'javascript',
        theme: 'material'
      }}
      value={store.value}
      onBeforeChange={(editor, data, value) => {
        store.value = value;
      }}
    />
  </React.Fragment>
);

export default collect(App);

https://codesandbox.io/s/codemirror-example-1r1u6


unexpected failure updating Kong  configuration: route 'e3a45d7e-6c' does not have a name. decK needs routes to be named.

I have a problem, I hope you can help me solve it.  please!
shell > kubectl logs kong-ingress-controller-df98bfddb-kkhz9 -n kong ingress-controller

E0604 00:52:28.572669       7 controller.go:117] unexpected failure updating Kong     configuration:
route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
W0604 00:52:28.572698       7 queue.go:113] requeuing kube-system/kube-dns, err route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
E0604 00:52:31.906827       7 controller.go:117] unexpected failure updating Kong configuration:
route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
W0604 00:52:31.906856       7 queue.go:113] requeuing kube-system/kubernetes-dashboard, err route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
E0604 00:52:35.230292       7 controller.go:117] unexpected failure updating Kong configuration:
route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
W0604 00:52:35.230321       7 queue.go:113] requeuing kube-system/kube-dns, err route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
E0604 00:52:38.573080       7 controller.go:117] unexpected failure updating Kong configuration:
route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
W0604 00:52:38.573109       7 queue.go:113] requeuing kube-system/kubernetes-dashboard, err route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
E0604 00:52:41.900031       7 controller.go:117] unexpected failure updating Kong configuration:
route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
W0604 00:52:41.900060       7 queue.go:113] requeuing kong/kong-proxy, err route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
E0604 00:52:45.229800       7 controller.go:117] unexpected failure updating Kong configuration:
route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
W0604 00:52:45.229830       7 queue.go:113] requeuing guanwei/guanwei-sys-mvc, err route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
E0604 00:52:48.572557       7 controller.go:117] unexpected failure updating Kong configuration:
route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.
W0604 00:52:48.572584       7 queue.go:113] requeuing default/kubernetes, err route 'e3a45d7e-6c08-4305-868a-f512aad6ecc6' does not have a name. decK needs routes to be named.

It seems like you upgraded from Kong Ingress Controller 0.3.0 to 0.4.0. You need a fresh Kong cluster for the upgrade as the older and newer version of the Ingress Controller are not compatible due to the breaking changes that are made between the two versions.


Makes most special characters be replaced with a dash

closes #4782

Still achieves the same goal of stripping out reserved characters
Changes from removal to replacement
This helps keep word separators from being removed
Apostrophes (') are unaffected

Hi @claydiffrient, sorry for letting this sit for such a long time. I think the order in which things are done needs to be addressed, as currently the £ handling is going to cause an issue with any title which contains the letters PS - you can see that this test will fail.
I recommend switching it back to doing character handling before unicode handling?

Hi @claydiffrient, if you don't have time to update this then I'll fix it up and get it merged. Thought I'd drop one more message before I do JIC :wink:

Hey @ErisDS I'm so sorry that I've not done this yet.  I keep putting it off.  I'll fix it up tonight or tomorrow.  If it's not done by Wednesday, I give you leave to take it :)

Understood :grinning:

@ErisDS I've got commits in that fix everything.  I think the one failure on that one build is a transient failure. All the other builds worked just fine, and I wouldn't expect this code to affect that portion.  I also cannot get it to fail locally. I can't retrigger the build on Travis for some reason, I'm assuming because I'm not a collaborator on the project.  I think it would be safe to override and do the merge, but perhaps retriggering would be best to get the green check from Travis.
Sorry it took me so long to get this done.

Hey @claydiffrient I restarted that failing build and it's all green now :) One last thing, could you please squash those commits? Thanks :+1:

@ErisDS Done.  Sorry, I can't believe I didn't do that beforehand.  I hate getting several commits in PRs personally.

I'm sorry for the to-ing and fro-ing on this, but I think the most recent change to account for £ has re-introduced other issues.
I believe the £ needs to be handled first and separately, then unidecode, and then the other character replacements. The reason being that unidecode happening after will result in some characters not being substituted correctly. If you turned the example from the unidecode readme into a test I think you'd see:
に間違いがないか、再度確認してください。再読み込みしてください。
gets converted to
niJian Wei iganaika, Zai Du Que Ren sitekudasai. Zai Du miIp misitekudasai.
Which introduces new commas, full stops, and a space at the end which would not be handled. We may even need to move the call to .trim() ?

@ErisDS I added the unicode test and made sure it passes.  I also went ahead and moved the call to trim just to be safe.  I couldn't figure out a test that would cause it to have problems running at the beginning, but figured maybe there was something that it would fail with somewhere out there.  Anyways, hopefully this works in all cases now :)

@claydiffrient not sure if you saw but this PR is currently failing on a linting error :(

@ErisDS I actually didn't notice.  If fixed the problem it was hung up on and everything seems to be good locally.    Hopefully this will be the end of it :)

Merged! I actually thought I had done this already :confused:


fix Collection.get method

wrong comparison between object and number

'data' (in that line of code) is actually a local variable pointing to idIndex, which is an array of integers.
If you go to : Loki Sandbox page , you can click on 'Object Inspector' to drill down into all the properties (like) idIndex to see what kinds of data they store.

Oh I see. Sorry for wrong pull request.
But still don't understand why not use idIndex as a dictionary instead to make this possible idIndex[someLokiIndex] -> get some data by id.

No problem.   Refactoring of idIndex will be left to a 2.0 version change since this would break serialized file compatability.
Performance is better with collection.by() than collection.get() but not by so large a margin that it can't wait for a 2.0 version (or at least minor version with autoupgrade logic).


Plan9FileSystem hogging external USB drive with open handle

Version
WSL version: <IP_ADDRESS> Kernel version: <IP_ADDRESS> WSLg version: 1.0.30 Windows version: 10.0.22000.434
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
Don't know exactly how to reproduce, but right now there is a dllhost.exe having an open handle on D:\ (which is an external USB drive) and preventing it from ejecting.
It was started with the commandline C:\WINDOWS\system32\DllHost.exe /Processid:{DFB65C4C-B34F-435D-AFE9-A86218684AA8}, a registry search pointed to HKEY_CLASSES_ROOT\CLSID\{AFC7B6DE-D642-41B7-AB0C-A01019510741} which has an entry named Plan9FileSystem so it's probably WSL2 related.

The handle is still open after wsl --shutdown.
Expected Behavior
WSL2 file system bridge should not prevent external drives from ejecting
Actual Behavior
External drives cannot be ejected
Diagnostic Logs
No response

I just ran into this as well:
The application \Device\HarddiskVolume6\Windows\System32\dllhost.exe with process id 26064 stopped the removal or ejection for the device USB\VID_1058&PID_25A3\575837324437314644415045.
Process command line: C:\WINDOWS\system32\DllHost.exe /Processid:{DFB65C4C-B34F-435D-AFE9-A86218684AA8}
List of affected devices:

WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.30
Windows version: 10.0.22538.1010

I also have this problem. The DLLHost. With Proccessid {DFB65C4C-B34F-435D-AFE9-A86218684AA8} locks my external drive, even this drive have NEVER been used by WSL.
Win 10 21H2: 19044.2006
WSL Kernel: 5.10.16
Also why are you (WSL devs) running this under a dllhost.exe, it seems like a bad approach.  When I need to troubleshoot my PC, I do not want to go lookup GUIDs in the hunt of the actual problem in context of a dllhost.
What is the reason for this?

Is a fix for this in the horizon? Right now I have to keep killing dllhost.exe, then executing it again after ejecting the drive, and then I need to reboot WSL for it to get back access to Window's filesystem.

same issue on win11
DllHost.exe /Processid:{DFB65C4C-B34F-435D-AFE9-A86218684AA8}
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.49
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1265

You can try the following: open \\wsl.localhost\<linux_dist>\etc\wsl.conf and add the following:
[automount]
enabled = false

Reference: https://learn.microsoft.com/en-us/windows/wsl/wsl-config#automount-settings
But is doesn't work for me, because Docker Desktop rewrite wsl.conf after restart, and I don't know where I can adjust appropriate Docker setting to disable automount.

This is incredibly annoying. Shutting down WSL allowed me to safely remove the drive though.

System Particulars
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.2314

Distro: Ubuntu 22.04

The
[automount]
enabled=false

doesn't work for me on any of the external drives. The problem also impacts mounted drives:
DllHost.exe /Processid:{DFB65C4C-B34F-435D-AFE9-A86218684AA8}
grabs onto them and keeps a death grip until all of my distros are completely shut down.
Also, after disabling automount, I am unable to attach to my Ubuntu distro with VS Code. it gives errors similar to the following:

<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\WINDOWS
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\WINDOWS
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\WINDOWS
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\WINDOWS
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\WINDOWS
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Program
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Program
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Program
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Program
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Program
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Program
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Users\Ro
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Users\Ro
<3>WSL (272) ERROR: UtilTranslatePathList:2852: Failed to translate C:\Users\Ro

This is a really, really poor experience for those of us who use external and/or mounted drives.


Pressing the keyboard shortcut when the output window has focus creates a new console window

Bug description
See title.
To Reproduce

Press ctrl+shift+T to open a console window.
Write some random code, e.g. echo mt_rand(1, 100);
Press ctrl+shift+T to render the output
Press ctrl+shift+T again

Expected behavior
I would expect the code from my console window (which was already open, just not in focus) to be run again.
What actually happens
Instead, a new console window is opened.

You're right. The last executed code feature in 1.1.1 could come in handy with this.

Closed this by accident


[BUG] Server starts up with bad metadata collection: cohort membership

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
During testing for another issue, I attempted to start a server with an invalid metadata collection id - and in this case to join a cohort named 'xxx'
OMRS-COHORT-REGISTRY-400-002 was reported in the errorlog during server startup
Wed Jun 08 16:25:16 BST 2022 mds1 Exception OMRS-AUDIT-0006 Configuration error detected while connecting to cohort xxx, exception org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSConfigErrorException was caught with error message: OMRS-COHORT-REGISTRY-400-002 The Open Metadata Repository Cohort xxx is not available to server mds1 because the local metadata collection id has been changed from b7db5a0e-291e-410b-b2f2-83020685d244 to e4cdf735-d555-4022-b3bc-a5367551001a since this server registered with the cohort.

Ok so this suggests that mds1 will not participate in the cohort, as there is some suspicion about the local metadata collection id - seems reasonable...
We then get an exception of
OMRSRuntimeException{reportedHTTPCode=400, reportingClassName='org.odpi.openmetadata.repositoryservices.metadatahighway.cohortregistry.OMRSCohortRegistry', reportingActionDescription='validateLocalMetadataCollectionId()', reportedErrorMessage='OMRS-COHORT-REGISTRY-400-002 The Open Metadata Repository Cohort xxx is not available to server mds1 because the local metadata collection id has been changed from b7db5a0e-291e-410b-b2f2-83020685d244 to e4cdf735-d555-4022-b3bc-a5367551001a since this server registered with the cohort.', reportedErrorMessageId='OMRS-COHORT-REGISTRY-400-002', reportedErrorMessageParameters=[xxx, mds1, b7db5a0e-291e-410b-b2f2-83020685d244, e4cdf735-d555-4022-b3bc-a5367551001a], reportedSystemAction='The system is unable to connect with other members of the cohort while this incompatibility exists.', reportedUserAction='If there is no reason for the change of local metadata collection id (this is the normal case) change the local metadata collection id back to its original valid in the server configuration. If the local metadata collection Id must be changed (due to a conflict for example) then shutdown the server, restart it with no local repository configured and shut it down normally once the server has successfully unregistered with the cohort. Then re-establish the local repository configuration.Restart the server once the configuration is correct.', reportedCaughtException=null, reportedCaughtExceptionClassName='null', relatedProperties=null, errorMessage='OMRS-COHORT-REGISTRY-400-002 The Open Metadata Repository Cohort xxx is not available to server mds1 because the local metadata collection id has been changed from b7db5a0e-291e-410b-b2f2-83020685d244 to e4cdf735-d555-4022-b3bc-a5367551001a since this server registered with the cohort.'}

This provides more information, and confirms the above - either the admin needs to

restore the metadata collection id to the default (via config file, or REST API)
deregister from cohort, and restart the server without a metadata collection

That also seems to make sense - two possible recovery actions. Both require access to admin APIs
with a stacktrace of
	at org.odpi.openmetadata.repositoryservices.metadatahighway.cohortregistry.OMRSCohortRegistry.validateLocalMetadataCollectionId(OMRSCohortRegistry.java:156)
	at org.odpi.openmetadata.repositoryservices.metadatahighway.cohortregistry.OMRSCohortRegistry.initialize(OMRSCohortRegistry.java:223)
	at org.odpi.openmetadata.repositoryservices.metadatahighway.OMRSCohortManager.initialize(OMRSCohortManager.java:187)
	at org.odpi.openmetadata.repositoryservices.metadatahighway.OMRSMetadataHighwayManager.connectToCohort(OMRSMetadataHighwayManager.java:229)
	at org.odpi.openmetadata.repositoryservices.metadatahighway.OMRSMetadataHighwayManager.initialize(OMRSMetadataHighwayManager.java:100)
	at org.odpi.openmetadata.repositoryservices.admin.OMRSOperationalServices.initializeCohorts(OMRSOperationalServices.java:890)
	at org.odpi.openmetadata.repositoryservices.admin.OMRSOperationalServices.initializeCohortMember(OMRSOperationalServices.java:478)
	at org.odpi.openmetadata.adminservices.OMAGServerOperationalServices.activateWithSuppliedConfig(OMAGServerOperationalServices.java:320)
	at org.odpi.openmetadata.adminservices.OMAGServerOperationalServices.activateWithStoredConfig(OMAGServerOperationalServices.java:150)
	at org.odpi.openmetadata.adminservices.spring.OperationalServicesResource.activateWithStoredConfig(OperationalServicesResource.java:60)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:577)
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205)
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:150)
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:117)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:895)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:808)
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1067)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:963)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
	at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909

The indication that the server will not participate in the cohort makes sense - we don't want to respond to federated queries in this state, or share metadata in other ways.
A question arises...
However in addition, what about regular queries against this server? Should in fact this server be in some kind of 'failed' or 'recovery' state where functionality is limited. That may be hard to determine without more context, but should it at least report it's state as such so that an orchestration engine or admin can take admin action?
From the log it then seems as if cohort initialization does continue - this seems to different to what the message suggests will happen (though there may be further controls elsewhere) since startup then continues
Wed Jun 08 16:25:16 BST 2022 mds1 Startup OMRS-AUDIT-0007 The Open Metadata Repository Services (OMRS) has initialized
Wed Jun 08 16:25:16 BST 2022 mds1 Startup OMRS-AUDIT-0031 The xxx cohort inbound event manager is starting with 0 type definition event consumer(s) and 0 instance event consumer(s)
Wed Jun 08 16:25:16 BST 2022 mds1 Startup OMRS-AUDIT-0026 Initializing listener for cohort xxx
Wed Jun 08 16:25:16 BST 2022 mds1 Startup OMRS-AUDIT-0019 An OMRS Topic Connector has registered with an event bus connector for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.registration
Wed Jun 08 16:25:16 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0001 Connecting to Apache Kafka Topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.registration with a server identifier of ecff2eda-7940-4363-983a-8f4a89804fb1
Wed Jun 08 16:25:16 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0015 The local server is attempting to connect to Kafka brokers at localhost:9092 [ attempt 1 of 5 ]
Wed Jun 08 16:26:16 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0015 The local server is attempting to connect to Kafka brokers at localhost:9092 [ attempt 2 of 5 ]
Wed Jun 08 16:27:16 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0015 The local server is attempting to connect to Kafka brokers at localhost:9092 [ attempt 3 of 5 ]
Wed Jun 08 16:28:16 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0015 The local server is attempting to connect to Kafka brokers at localhost:9092 [ attempt 4 of 5 ]
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0003 10 properties passed to the Apache Kafka Consumer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.registration
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0002 10 properties passed to the Apache Kafka Producer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.registration
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0010 The Apache Kafka producer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.registration is starting up with 0 buffered messages
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0020 An OMRS Topic Connector is ready to send and receive events on topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.registration
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0019 An OMRS Topic Connector has registered with an event bus connector for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0001 Connecting to Apache Kafka Topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types with a server identifier of ecff2eda-7940-4363-983a-8f4a89804fb1
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0015 The local server is attempting to connect to Kafka brokers at localhost:9092 [ attempt 1 of 5 ]
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0003 10 properties passed to the Apache Kafka Consumer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0002 10 properties passed to the Apache Kafka Producer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0010 The Apache Kafka producer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types is starting up with 0 buffered messages
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0020 An OMRS Topic Connector is ready to send and receive events on topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0019 An OMRS Topic Connector has registered with an event bus connector for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.instances
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0001 Connecting to Apache Kafka Topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.instances with a server identifier of ecff2eda-7940-4363-983a-8f4a89804fb1
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0015 The local server is attempting to connect to Kafka brokers at localhost:9092 [ attempt 1 of 5 ]
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0015 The listener thread for an OMRS Topic Connector for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types has started
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0015 The listener thread for an OMRS Topic Connector for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types has started
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0003 10 properties passed to the Apache Kafka Consumer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.instances
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0002 10 properties passed to the Apache Kafka Producer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.instances
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0010 The Apache Kafka producer for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.instances is starting up with 0 buffered messages
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0020 An OMRS Topic Connector is ready to send and receive events on topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.instances
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0015 The listener thread for an OMRS Topic Connector for topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.instances has started
Wed Jun 08 16:29:03 BST 2022 mds1 Cohort OMRS-AUDIT-0062 Requesting registration information from other members of the open metadata repository cohort xxx
Wed Jun 08 16:29:03 BST 2022 mds1 Event OMRS-AUDIT-8009 The Open Metadata Repository Services (OMRS) has sent event of type Registry Event to the cohort topic egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.registration
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0031 The local repository outbound event manager is starting with 0 type definition event consumer(s) and 0 instance event consumer(s)
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMRS-AUDIT-0032 The local repository outbound event manager is sending out the 901 type definition events that were generated and buffered during server initialization
Wed Jun 08 16:29:03 BST 2022 mds1 Startup OMAG-ADMIN-0004 The mds1 server has successfully completed start up.  The following services are running: [Open Metadata Repository Services (OMRS)]

At this point the server looks normal. I've not yet tested multiple cohort members, but the local info is:
{
    "class": "CohortConfigResponse",
    "relatedHTTPCode": 200,
    "config": {
        "class": "CohortConfig",
        "cohortName": "xxx",
        "cohortRegistryConnection": {
            "class": "Connection",
            "headerVersion": 0,
            "connectorType": {
                "class": "ConnectorType",
                "headerVersion": 0,
                "type": {
                    "class": "ElementType",
                    "headerVersion": 0,
                    "elementOrigin": "LOCAL_COHORT",
                    "elementVersion": 0,
                    "elementTypeId": "954421eb-33a6-462d-a8ca-b5709a1bd0d4",
                    "elementTypeName": "ConnectorType",
                    "elementTypeVersion": 1,
                    "elementTypeDescription": "A set of properties describing a type of connector."
                },
                "guid": "108b85fe-d7a8-45c3-9f88-742ac4e4fd14",
                "qualifiedName": "Egeria:CohortRegistryConnector:File",
                "displayName": "File-based Cohort Registry Store Connector",
                "description": "Connector supports storing of the open metadata cohort registry in a file using JSON format.",
                "connectorProviderClassName": "org.odpi.openmetadata.adapters.repositoryservices.cohortregistrystore.file.FileBasedRegistryStoreProvider"
            },
            "endpoint": {
                "class": "Endpoint",
                "headerVersion": 0,
                "address": "./data/servers/mds1/cohorts/xxx.registrystore"
            }
        },
        "cohortOMRSRegistrationTopicConnection": {
            "class": "VirtualConnection",
            "headerVersion": 0,
            "connectorType": {
                "class": "ConnectorType",
                "headerVersion": 0,
                "connectorProviderClassName": "org.odpi.openmetadata.repositoryservices.connectors.omrstopic.OMRSTopicProvider"
            },
            "embeddedConnections": [
                {
                    "class": "EmbeddedConnection",
                    "headerVersion": 0,
                    "position": 0,
                    "displayName": "xxx OMRS Topic for registrations",
                    "embeddedConnection": {
                        "class": "Connection",
                        "headerVersion": 0,
                        "connectorType": {
                            "class": "ConnectorType",
                            "headerVersion": 0,
                            "type": {
                                "class": "ElementType",
                                "headerVersion": 0,
                                "elementOrigin": "LOCAL_COHORT",
                                "elementVersion": 0,
                                "elementTypeId": "954421eb-33a6-462d-a8ca-b5709a1bd0d4",
                                "elementTypeName": "ConnectorType",
                                "elementTypeVersion": 1,
                                "elementTypeDescription": "A set of properties describing a type of connector."
                            },
                            "guid": "3851e8d0-e343-400c-82cb-3918fed81da6",
                            "qualifiedName": "Egeria:OpenMetadataTopicConnector:Kafka",
                            "displayName": "Apache Kafka Open Metadata Topic Connector",
                            "description": "Apache Kafka Open Metadata Topic Connector supports string based events over an Apache Kafka event bus.",
                            "supportedAssetTypeName": "KafkaTopic",
                            "expectedDataFormat": "PLAINTEXT",
                            "connectorProviderClassName": "org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataTopicProvider",
                            "connectorInterfaces": [
                                "org.odpi.openmetadata.frameworks.connectors.Connector",
                                "org.odpi.openmetadata.repositoryservices.connectors.openmetadatatopic.OpenMetadataTopic",
                                "org.odpi.openmetadata.frameworks.auditlog.AuditLoggingComponent"
                            ],
                            "recognizedConfigurationProperties": [
                                "producer",
                                "consumer",
                                "local.server.id",
                                "sleepTime"
                            ]
                        },
                        "endpoint": {
                            "class": "Endpoint",
                            "headerVersion": 0,
                            "address": "egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.registration"
                        },
                        "configurationProperties": {
                            "producer": {
                                "bootstrap.servers": "localhost:9092",
                                "bring.up.minSleepTime": "60000",
                                "bring.up.retries": "5"
                            },
                            "local.server.id": "ecff2eda-7940-4363-983a-8f4a89804fb1",
                            "consumer": {
                                "bootstrap.servers": "localhost:9092",
                                "bring.up.minSleepTime": "60000",
                                "bring.up.retries": "5"
                            }
                        }
                    }
                }
            ]
        },
        "cohortOMRSTypesTopicConnection": {
            "class": "VirtualConnection",
            "headerVersion": 0,
            "connectorType": {
                "class": "ConnectorType",
                "headerVersion": 0,
                "connectorProviderClassName": "org.odpi.openmetadata.repositoryservices.connectors.omrstopic.OMRSTopicProvider"
            },
            "embeddedConnections": [
                {
                    "class": "EmbeddedConnection",
                    "headerVersion": 0,
                    "position": 0,
                    "displayName": "xxx OMRS Topic for types",
                    "embeddedConnection": {
                        "class": "Connection",
                        "headerVersion": 0,
                        "connectorType": {
                            "class": "ConnectorType",
                            "headerVersion": 0,
                            "type": {
                                "class": "ElementType",
                                "headerVersion": 0,
                                "elementOrigin": "LOCAL_COHORT",
                                "elementVersion": 0,
                                "elementTypeId": "954421eb-33a6-462d-a8ca-b5709a1bd0d4",
                                "elementTypeName": "ConnectorType",
                                "elementTypeVersion": 1,
                                "elementTypeDescription": "A set of properties describing a type of connector."
                            },
                            "guid": "3851e8d0-e343-400c-82cb-3918fed81da6",
                            "qualifiedName": "Egeria:OpenMetadataTopicConnector:Kafka",
                            "displayName": "Apache Kafka Open Metadata Topic Connector",
                            "description": "Apache Kafka Open Metadata Topic Connector supports string based events over an Apache Kafka event bus.",
                            "supportedAssetTypeName": "KafkaTopic",
                            "expectedDataFormat": "PLAINTEXT",
                            "connectorProviderClassName": "org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataTopicProvider",
                            "connectorInterfaces": [
                                "org.odpi.openmetadata.frameworks.connectors.Connector",
                                "org.odpi.openmetadata.repositoryservices.connectors.openmetadatatopic.OpenMetadataTopic",
                                "org.odpi.openmetadata.frameworks.auditlog.AuditLoggingComponent"
                            ],
                            "recognizedConfigurationProperties": [
                                "producer",
                                "consumer",
                                "local.server.id",
                                "sleepTime"
                            ]
                        },
                        "endpoint": {
                            "class": "Endpoint",
                            "headerVersion": 0,
                            "address": "egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.types"
                        },
                        "configurationProperties": {
                            "producer": {
                                "bootstrap.servers": "localhost:9092",
                                "bring.up.minSleepTime": "60000",
                                "bring.up.retries": "5"
                            },
                            "local.server.id": "ecff2eda-7940-4363-983a-8f4a89804fb1",
                            "consumer": {
                                "bootstrap.servers": "localhost:9092",
                                "bring.up.minSleepTime": "60000",
                                "bring.up.retries": "5"
                            }
                        }
                    }
                }
            ]
        },
        "cohortOMRSInstancesTopicConnection": {
            "class": "VirtualConnection",
            "headerVersion": 0,
            "connectorType": {
                "class": "ConnectorType",
                "headerVersion": 0,
                "connectorProviderClassName": "org.odpi.openmetadata.repositoryservices.connectors.omrstopic.OMRSTopicProvider"
            },
            "embeddedConnections": [
                {
                    "class": "EmbeddedConnection",
                    "headerVersion": 0,
                    "position": 0,
                    "displayName": "xxx OMRS Topic for instances",
                    "embeddedConnection": {
                        "class": "Connection",
                        "headerVersion": 0,
                        "connectorType": {
                            "class": "ConnectorType",
                            "headerVersion": 0,
                            "type": {
                                "class": "ElementType",
                                "headerVersion": 0,
                                "elementOrigin": "LOCAL_COHORT",
                                "elementVersion": 0,
                                "elementTypeId": "954421eb-33a6-462d-a8ca-b5709a1bd0d4",
                                "elementTypeName": "ConnectorType",
                                "elementTypeVersion": 1,
                                "elementTypeDescription": "A set of properties describing a type of connector."
                            },
                            "guid": "3851e8d0-e343-400c-82cb-3918fed81da6",
                            "qualifiedName": "Egeria:OpenMetadataTopicConnector:Kafka",
                            "displayName": "Apache Kafka Open Metadata Topic Connector",
                            "description": "Apache Kafka Open Metadata Topic Connector supports string based events over an Apache Kafka event bus.",
                            "supportedAssetTypeName": "KafkaTopic",
                            "expectedDataFormat": "PLAINTEXT",
                            "connectorProviderClassName": "org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataTopicProvider",
                            "connectorInterfaces": [
                                "org.odpi.openmetadata.frameworks.connectors.Connector",
                                "org.odpi.openmetadata.repositoryservices.connectors.openmetadatatopic.OpenMetadataTopic",
                                "org.odpi.openmetadata.frameworks.auditlog.AuditLoggingComponent"
                            ],
                            "recognizedConfigurationProperties": [
                                "producer",
                                "consumer",
                                "local.server.id",
                                "sleepTime"
                            ]
                        },
                        "endpoint": {
                            "class": "Endpoint",
                            "headerVersion": 0,
                            "address": "egeria.omag.openmetadata.repositoryservices.cohort.xxx.OMRSTopic.instances"
                        },
                        "configurationProperties": {
                            "producer": {
                                "bootstrap.servers": "localhost:9092",
                                "bring.up.minSleepTime": "60000",
                                "bring.up.retries": "5"
                            },
                            "local.server.id": "ecff2eda-7940-4363-983a-8f4a89804fb1",
                            "consumer": {
                                "bootstrap.servers": "localhost:9092",
                                "bring.up.minSleepTime": "60000",
                                "bring.up.retries": "5"
                            }
                        }
                    }
                }
            ]
        },
        "cohortOMRSTopicProtocolVersion": "V1",
        "eventsToProcessRule": "ALL"
    }
}

It seems as if the server is in a bad state which needs one of two actions performing. It is 'risky' for it to participate in a cohort, but it is unclear how this is known to callers or cohort members
@mandy-chessell  ?
Expected Behavior
see above
Steps To Reproduce
No response
Environment
- Egeria:
- OS:
- Java:
- Browser (for UI issues):
- Additional connectors and integration:

Any Further Information?
No response

@planetf1 I had a look at the code and found the problem - its a one line change - I can do it - but I wondered if you want to do it - particulaly if it is holding you up?
The problem is in OMRSCohortManager in the initialize method.  The catch statement at line 279 is outputting AudiitLog message OMRS-AUDIT-0006 and returning - it should rethrow the error after it has output the audit log message.

I'll do the PR. thanks


watchnot triggered

I have a use case where I'm watching files and writing a lcov file with NYC on the fly. However this doesn't trigger an update. If I'm not watching the files and exit the process it works. It might be connected to this

@stoffeastrom Thanks for the issue and the research! I will take a look at this next weekend probably and see where I get too.

@ryanluker I've been doing some more investigation and it seems like I can't get the correct coverage when I'm watching and generate a new coverage file on the fly from NYC. It might not be an issue with this plugin at all.

@ryanluker I solved my problem. However using multi root one of the vscode processes is using 100% cpu. Will do some more investigation!
It's super cool to get live coverage in a file though :)

I will make another issue regarding multi root


[Feature Request]: add a workspace Cargo.toml at the root of project folder

The Rust analyzer often fails to start with the error can not discover workspace.
Can we add a Cargo.toml file with src-tauri as its member, to the templates?

What template did you encounter this with? rust-analyzer works fine for me with all templates, there is no need for a root Cargo.toml file.

What template did you encounter this with? rust-analyzer works fine for me with all templates, there is no need for a root Cargo.toml file.

Thanks I am currently using the Solid template.

I have tested theses templates multiple times with rust-analyzer and vscode and they work fine. It sounds to me like a bug in rust-analyzer.

I have tested theses templates multiple times with rust-analyzer and vscode and they work fine. It sounds to me like a bug in rust-analyzer.

You're right, maybe related to https://github.com/rust-lang/rust-analyzer/issues/14477


Prezto unable to load theme

Description
I installed Prezto and setup theme but it is not loading. Tried searching through many resources but did not get it working.
I'm able to see all the listed themes after running command prompt -l. I can even check my current theme using prompt -c and set some theme using example prompt pure command however nothing happens the terminal remains the same.
Expected behavior
Able to load theme
Actual behavior
Theme is not loading
Steps to Reproduce

Running command prompt <theme_name> does not do anything

Versions

Prezto commit: current
ZSH version: zsh 5.8.1 (x86_64-apple-darwin21.0)
OS information: macOS Monterey 12.6

TBH, this is almost impossible for anyone other than you to debug at least with the information given.
It all works fine on my machine.
If you can dig further and get to a point where you have something reproducible then maybe someone can help you.

Have you made sure the sub modules are loaded? If you cd to prezto's directory and run git submodule update --init it will make sure all sub modules are updated and loaded for your next shell load.

 It would help if you could use the official runcoms for debugging.

Hi,
Yes, when I initially cloned, I included —recursive option.
Mark
Mark Jaffe
@.***
http://markie.info
https://github.com/Jaff
408-807-2093 (cell)
On May 9, 2023 at 8:59 AM -0700, Mark Jaffe @.***>, wrote:

This is also an issue for me; zsh 5.9 (x86_64-apple-darwin22.0)
prezto installed from GitHub yesterday (commit info:
@.*** .zprezto % git rev-parse HEAD
3c002f7
Zpresto issues.txt
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

git submodule update --init


View controller: Add API for cancelling an ongoing selection

In the Spotify app, we want to cancel ongoing selections when a custom gesture recognizer is triggered.

Current coverage is 92.42% (diff: 0.00%)

No coverage report found for master at 9f9fc83.

Powered by Codecov. Last update 9f9fc83...c78238d


Update cargo crate to allow mutable transmutes

The latest commit adding #[allow(mutable_transmutes)] to allow mutable transmutes is missing in the current cargo crate version causing an error when trying to compile.
Please update the crate version to include this commit, thanks.

Should be good in a few minutes. Travis automatically publishes the package.


Bumping lodash version to maintain security

Hello 👋🏾
We'd like to update that version of lodash to 4.17.21 to resolve outstanding security issue. Is this something that can be looked at? @fabulousduck We can open a PR and resolve this for you if you'd like.
cc @meltingice @fabulousduck
edit: Created a pr with the update here: https://github.com/meltingice/psd.js/pull/225

@MgenGlder With regards to the NPM situation, I don't have the credentials to update it myself, @meltingice will have to do that. But he has been MIA from this project for a long time now so I would not get my hopes up. If he does however want to bump this repo to the npm repo, that would be great :).
As for your PR, the testing of a PR is for the creator of the PR to do. So once you can confirm to me that you have tested your change and does not break anything, I will be more than happy to merge the PR you have linked.

@fabulousduck Fair enough, I can confirm we've tested the PR to the best of our ability. I was running into issues running the compilation scripts, I'm thinking it's because of how outdated the buildscripts/configuration are with the latest coffeescript compiler.I also noticed that the source controlled repo doesn't seem to match the latest version in NPM. As far as I'm aware the PR is good to go.
Do you have any context on this?
It seems the latest version of psd.js available on npm doesn't match what's shown in the releases in this repo.
After a fresh install I see this:

@fabulousduck Managed to figure it out! There's a very similarly named package psd.js which seems to be forked and is authored by an entirely separate party. We have to be careful and have people understand this package represents psd and not any of the forks like psd.js etc.

Seems like bumping the version introduces a small regression. _.any no longer exists, we can use _.some instead.

@fabulousduck 👋🏾 Going to go ahead and merge this guy. I've verified the PSD rendering functionality still works. Should be a good win in getting this project out of security vulnerability pergatory.


adapt config handling (GDEV-402)

Title and squash and merge:
adapt config handling  (GDEV-402)

Description and squash and merge:
- store dev config in `.devcontainer/.dev_config.yaml` inject config yaml via env var
- configs passed via constant `CONFIG` variable instead of `get_config` function
- `get_config` function only for dependency injection into FastAPI app
- include all Base configs from the ghga_service_chassis_lib
- configure FastAPI app with CORS params and essential base paths
- set CONFIG_YAML env var in CI workflows that need it

Depends on #52.

Codecov Report

Merging #53 (5ee0322) into dev (c61ac29) will increase coverage by 2.78%.
The diff coverage is 100.00%.

:exclamation: Current head 5ee0322 differs from pull request most recent head bf5d91a. Consider uploading reports for the commit bf5d91a to get more accurate results

@@            Coverage Diff             @@
##              dev      #53      +/-   ##
==========================================
+ Coverage   61.79%   64.58%   +2.78%
==========================================
  Files          13       14       +1
  Lines          89       96       +7
==========================================
+ Hits           55       62       +7
  Misses         34       34

Impacted Files
Coverage Δ

my_microservice/api/deps.py
100.00% <100.00%> (ø)

my_microservice/api/main.py
100.00% <100.00%> (ø)

my_microservice/config.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c61ac29...bf5d91a. Read the comment docs.

Codecov Report

Merging #53 (bf5d91a) into dev (c61ac29) will increase coverage by 2.78%.
The diff coverage is 81.25%.

@@            Coverage Diff             @@
##              dev      #53      +/-   ##
==========================================
+ Coverage   61.79%   64.58%   +2.78%
==========================================
  Files          13       14       +1
  Lines          89       96       +7
==========================================
+ Hits           55       62       +7
  Misses         34       34

Impacted Files
Coverage Δ

my_microservice/__main__.py
0.00% <0.00%> (ø)

my_microservice/api/deps.py
100.00% <100.00%> (ø)

my_microservice/api/main.py
100.00% <100.00%> (ø)

my_microservice/config.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c61ac29...bf5d91a. Read the comment docs.

Already merged as part of other PR.


chore/package: Version change to v0.8.0

Coverage remained the same at 91.857% when pulling cc837533864791884730612b192457c09ac78034 on bochaco:version-change-to-v0.8.0 into a1fcc74e04eb2cfd9fe22a231a9f51f52818da4a on maidsafe:master.


Image bust of Ted Bundy

Have the serial killer in a type of shadow that changes as the days pass.  But never really reveals as it's a exaggerated bust.