Can't connect to azure event hub kafka interface

Describe the bug

We wanted to monitor our azure event hub, which we mainly use as a kafka server.
The kafka interface works and our backend services can communicate with the kafka interface
Monitoring also works with kafka-tool/offset-explorer
But kafka-ui fails to connect to the hub with this error message:
2022-08-12 14:27:25,701 ERROR [parallel-6] c.p.k.u.s.MetricsService: Failed to collect cluster prod-event-hub info
java.lang.IllegalStateException: Error while creating AdminClient for Cluster prod-event-hub
        at com.provectus.kafka.ui.service.AdminClientServiceImpl.lambda$createAdminClient$3(AdminClientServiceImpl.java:45)
        at reactor.core.publisher.Mono.lambda$onErrorMap$31(Mono.java:3733)
        at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onError(FluxOnErrorResume.java:94)
        at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onError(FluxMapFuseable.java:140)
        at reactor.core.publisher.MonoFlatMap$FlatMapMain.secondError(MonoFlatMap.java:192)
        at reactor.core.publisher.MonoFlatMap$FlatMapInner.onError(MonoFlatMap.java:259)
        at reactor.core.publisher.MonoPublishOn$PublishOnSubscriber.run(MonoPublishOn.java:187)
        at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)
        at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:830)
Caused by: org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition.

The kafka UI has full admin rights on the assigned user
Set up

Kafka-UI is setup with a standard docker compose:
version: '2.7'

services:
  kafka-ui:
    image: provectuslabs/kafka-ui
    container_name: kafka-ui
    ports:
      - "8085:8080"
    restart: always
    environment:
      - KAFKA_CLUSTERS_0_NAME=prod-event-hub
      - KAFKA_CLUSTERS_0_PROPERTIES_SECURITY_PROTOCOL=SASL_SSL
      - KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS=***.servicebus.windows.net:9093
      - KAFKA_CLUSTERS_0_PROPERTIES_SASL_MECHANISM=PLAIN
      - KAFKA_CLUSTERS_0_PROPERTIES_SASL_JAAS_CONFIG=org.apache.kafka.common.security.plain.PlainLoginModule required username='$$ConnectionString' password='***;

Expected behavior

A functioning connection with the azure event hub

Hey, thanks for reaching out. We'll take a look

Hi,
Im interested on the connection to Azure Events Hub too.
Thanks!!

Seems like they don't care  that much about implementing describeConfigs.
TODO: look for a workaround

Thanks for the feedback @Haarolean !

@Haarolean I would like to ask current kafka ui version whether have supported to connect Azure Eventhub?

@hueiyuan thanks for the reminder
Might be doable now considering #3376,
@iliax PTAL

@Haarolean Thanks for your reply. so maybe can I connect eventhub in release 0.5.0?
By the way, also please @iliax to confirm it. thank you.

@hueiyuan no you can't since this issue is still open.

The same problem here with MSK(AWS) Kafka 1.1.1.

@robsonpeixoto MSK (even serverless) is fully supported. Try master-labeled docker image and if it doesn't work, raise a new issue/discussion.

I'm having the same issues, and using the master tagged Docker image doesn't help.
The same UnknownTopicOrPartitionException: This server does not host this topic-partition error keeps popping up unfortunately.

@WizzardMaker @FireDrunk @hueiyuan hey guys, can you please verify it works for you on master - tagged docker image?

Can confirm that it works with the newest master branch image

@iliax @WizzardMaker
After verifying, my kafka ui does not connect eventhub. Could you give connect example of docker-compose.yaml ? My error message is below:
kafka-ui  | 2023-03-27 01:02:12,188 WARN  [kafka-admin-client-thread | kafka-ui-admin-1679878922-2] o.a.k.c.NetworkClient: [AdminClient clientId=kafka-ui-admin-1679878922-2] Connection to node -1 (<my-eventhub-namespace>.servicebus.windows.net/<IP_ADDRESS>:9093) could not be established. Broker may not be available.

I also provide my docker-compose.yaml for your reference:
version: '3'

services:
  kafka-ui:
    image: provectuslabs/kafka-ui:master
    container_name: kafka-ui
    ports:
      - "8080:8080"
    restart: always
    environment:
      - KAFKA_CLUSTERS_0_NAME=prod-event-hub
      - KAFKA_CLUSTERS_0_PROPERTIES_SECURITY_PROTOCOL=SASL_SSL
      - KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS=<my-eventhub-namespaces>.servicebus.windows.net:9093
      - KAFKA_CLUSTERS_0_PROPERTIES_SASL_MECHANISM=PLAIN
      - KAFKA_CLUSTERS_0_PROPERTIES_SASL_JAAS_CONFIG=org.apache.kafka.common.security.plain.PlainLoginModule required username='$ConnectionString' password='Endpoint=sb://<my-eventhub-namespaces>.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=<my-key>';

@iliax @WizzardMaker After verifying, my kafka ui still does not connect eventhub. Could you give connect example of docker-compose.yaml ? My error message is below:
kafka-ui  | 2023-03-27 01:02:12,188 WARN  [kafka-admin-client-thread | kafka-ui-admin-1679878922-2] o.a.k.c.NetworkClient: [AdminClient clientId=kafka-ui-admin-1679878922-2] Connection to node -1 (<my-eventhub-namespace>.servicebus.windows.net/<IP_ADDRESS>:9093) could not be established. Broker may not be available.

I also provide my docker-compose.yaml for your reference:
version: '3'

services:
  kafka-ui:
    image: provectuslabs/kafka-ui:master
    container_name: kafka-ui
    ports:
      - "8080:8080"
    restart: always
    environment:
      - KAFKA_CLUSTERS_0_NAME=prod-event-hub
      - KAFKA_CLUSTERS_0_PROPERTIES_SECURITY_PROTOCOL=SASL_SSL
      - KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS=<my-eventhub-namespaces>.servicebus.windows.net:9093
      - KAFKA_CLUSTERS_0_PROPERTIES_SASL_MECHANISM=PLAIN
      - KAFKA_CLUSTERS_0_PROPERTIES_SASL_JAAS_CONFIG=org.apache.kafka.common.security.plain.PlainLoginModule required username='$ConnectionString' password='Endpoint=sb://<my-eventhub-namespaces>.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=<my-key>';

That error message looks more like a general connection problem, and not the problem discussed in this issue.
Are you sure, that your at all able to connect to your event hub at that address? (What is <my-eventhub-namespaces>? Make sure that this is the name of the Azure resource - Check your "Host name" Property of the Event Hub Resource)

@WizzardMaker
<my-eventhub-namespaces> just is a namespace of eventhub. You can image this is a variable which can be replaced. Because I do not want to paste complete host name here. Based on this reason, I have confirm my host name of eventhub is correct. So I not sure and want to confirm this configure of docker-compose.yaml whether have incorrect setting.

The configuration looks correct.
Is the network of your docker container restricted in any way? Can you open a shell on the container and ping to the internet (ping google.com for example)?

@WizzardMaker
ping google.com this command is work. but container still does not show [AdminClient clientId=kafka-ui-admin-1679904082-4] Connection to node -1 (xxxxxx.servicebus.windows.net/<IP_ADDRESS>:9093) could not be established. Broker may not be available

@WizzardMaker
ping google.com this command is work. But currently status is changed as timeout related issues:
INFO  [kafka-admin-client-thread | kafka-ui-admin-1679907761-1] o.a.k.c.NetworkClient: [AdminClient clientId=kafka-ui-admin-1679907761-1] Disconnecting from node -1 due to socket connection setup timeout

Do you have a idea about processing this problem?

@WizzardMaker @iliax
I have below error message, could you give some idea to solve it for me? Thank you.
[AdminClient clientId=kafka-ui-admin-1680100319-1] Connection to node -1 (xxxx.servicebus.windows.net/<IP_ADDRESS>:9093) terminated during authentication. This may happen due to any of the following reasons: (1) Authentication failed due to invalid credentials with brokers older than 1.0.0, (2) Firewall blocking Kafka TLS traffic (eg it may only allow HTTPS traffic), (3) Transient network issue.

Worked like a charm for me. Great job, Thanks!


Bump version for next release

Bump version for next release

Codecov Report

Merging #1048 into develop will not change coverage by %.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop    #1048   +/-   ##
==========================================
  Coverage      36.27%   36.27%
  Complexity       537      537
==========================================
  Files            103      103
  Lines           4430     4430
  Branches         683      683
==========================================
  Hits            1607     1607
  Misses          2684     2684
  Partials         139      139

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 ebe67e0...6794b64. Read the comment docs.


core extension missing in: hapi-fhir-validation-resources-dstu3 ?

During the Validation of Profiles (StructureDefinitions) against a HAPI-JPA server i get several INFORMATION issues because of unknown core-extensions (e.g. http://hl7.org/fhir/StructureDefinition/elementdefinition-translatable).
As far as i can see - core extensions are not included in the hapi validation packages, it would be nice to have them included, or have another package containing these.
At the moment i have to upload all the used core extension to our hapi server(s) in order to get a usable validation.

implemented, Commits:

730d02b7c6c7745d148feaaacad4532fdf8b8b89
b4d2fcfc68824a2d4895f2e5160bd1b6076f12bb


error of installation in ubuntu 18.04.1 and php7.4

I'm currently using ubuntu 18.04 and php 7.4

And at last I end with this problem.

Option not supported for this linux distribution and version.
Is this unsovlable for now?
Thank you very much

Hi,
Latest version of Ubuntu is unfortunately not supported at the moment. If someone can add that version to the installer, just create a PR and I will review and merge it.


Hide the paging when there is less than a page of disks on one resource group editor

Storage Explorer Version: 1.10.0
Build: 20190909.2
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 19.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Expand 'Disks' node -> Open an empty resource group.
Check the bottom-right of the opened editor.

Expect Experience:
There is no paging.
Actual Experience:
The paging shows but it is disabled.

I'm not able to reproduce this. Verify again once we create a new version of the managed disks package.


[ci] release

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Patch Changes

#864 b84aff2 Thanks @mehalter! - Optimize UI icon SVG paths

size-limit report 📦

Path
Size

/index.html
5.13 KB (0%)

/_astro/*.js
19.27 KB (0%)

/_astro/*.css
9.63 KB (0%)


Cross compilation improvements

My goal for cross compilation was to get mustang targets working (which is successful with this patch). This differs a bit from standard nixpkgs cross compilation as it only needs to pass --target to rustc (non rust targets do not need to be cross compiled). Thus, the goal of these changes is to make cross compilation less reliant on the inner workings of nixpkgs build stages.

The platform target now wholly relies on the stdenv passed in through calling Cargo.nix and acts similarily to buildRustCrate.
mkBuiltByPackageIdByPkgs is now aware if it is a build dependency (or proc-macro) and can act accordingly.
a. It uses a tiny patch to build-rust-crate for an argument to disable cross compilation. Cross compilation gets disabled for build dependencies
b. A new argument, extraDepsIsBuild is provided as an override to .build. This lets you add the sysroot crates only to non build dependencies.

While it works for my use case not sure if it breaks other uses or if there is a better way to achieve this.
An example (albeit a bit messy) is seen here and the sysroot is here. Special thanks to alamgu for providing some guidance.

The rest of the changes I am not so sure about. So let's do the vendor stuff first and separately.
It sounds like the thing you are trying to avoid with doing it all Nixpkgs's way is building rustc itself? There are solutions to that that don't involve breaking with Nixpkgs so much.

It sounds like the thing you are trying to avoid with doing it all Nixpkgs's way is building rustc itself? There are solutions to that that don't involve breaking with Nixpkgs so much.

The reason for the changes is from my understanding the stdenv provided to the buildRustCrate function seems to stay constant whether it is a build or normal dependency. A different buildRustCrate isn't used for build and normal dependencies. (I may have missed something but this is my understanding of the code). I approached cross compilation by overriding the stdenv of the buildRustCrate function with the cross stdenv. Thus, all the build dependencies were getting cross compiled when they shouldn't have.
I tried to to approach it the alamgu way but it was failing to work at all with the oxalica's rust overlay.

Was able to figure out how to get it working the nixpkgs way. And the vendor was moved into its own PR.


Loosen rules to prevent breaking builds

Want to kick off a discussion about how strict we want to be in enforcing rules.
Setting rules to "error" will cause builds to break, slowing down work in progress and cluttering PRs.
Would be nice to strike a better balance between enforcing practices and productivity. I'd propose we go for "warn" on rules that are "cosmetic" and don't present a bug.

Interesting idea! Guess for me the first thing that comes to mind is that currently all rules that we enforce with the error are auto linted. So in theory none should actually block a build? Simply running an npm run fix (alongside lint on save) should solve all issues relating to the linter (par the new enum rule that is)?

Interesting idea! Guess for me the first thing that comes to mind is that currently all rules that we enforce with the error are auto linted. So in theory none should actually block a build? Simply running an npm run fix (alongside lint on save) should solve all issues relating to the linter (par the new enum rule that is)?

We get braking builds in feature PRs on bezier. No override build command set, just the regular next build. So my guess is next runs the linter during it's build process, unless I'm missing something big 😃

Interesting idea! Guess for me the first thing that comes to mind is that currently all rules that we enforce with the error are auto linted. So in theory none should actually block a build? Simply running an npm run fix (alongside lint on save) should solve all issues relating to the linter (par the new enum rule that is)?

We get braking builds in feature PRs on bezier. No override build command set, just the regular next build. So my guess is next runs the linter during it's build process, unless I'm missing something big 😃

Yeahh, next builds run next lint under the hood on all builds. So only ESLint rules are picked up for select files that Next decided. Even though we often include md etc files in our custom linting rules they're ignored by the build.
In any case and in theory: If you have lint on save setup and working, you should mostly never get linting breaking your builds. With that said the main exception that I often run across that breaks builds is when I accidentally push up console.log to the build. Do you have other examples of when you run across linting issues frequently?

Yeah interesting, I'd say ideally you'd have different behaviour;

In the editor you'd want warnings/errors but on save I don't want these things to be fixed automatically. While working on things I'd prefer to not have my just added import removed that I still needed to implement
But pre-commit I do want it to clean up my mess

Not sure if this is feasible though. If not I'd say we'd probably need to add husky with a nice pre-commit lint:fix to our next template

Yeah interesting, I'd say ideally you'd have different behaviour;

In the editor you'd want warnings/errors but on save I don't want these things to be fixed automatically. While working on things I'd prefer to not have my just added import removed that I still needed to implement
But pre-commit I do want it to clean up my mess

Not sure if this is feasible though. If not I'd say we'd probably need to add husky with a nice pre-commit lint:fix to our next template. And then I just need to not save that often while working 😄

Yeahh would be a nice option if you could auto fix things on commit. Sadly from experience I find pre-commit hooks like Husky just slow things down. If it was instant - great, but having to wait for a script to run just becomes tedious on every commit.

Now that we are using a more complex eslint setup + typescript, my mac likes to slow down so much that it starts queuing eslint tasks which chokes the live server. At that point i usually have to restart my laptop.
I'd rather wait a second and reduce some load during saves.
But that might just be a problem of an older breed still on the Intel macs. 🤓

Now that we are using a more complex eslint setup + typescript, my mac likes to slow down so much that it starts queuing eslint tasks which chokes the live server. At that point i usually have to restart my laptop.
I'd rather wait a second and reduce some load during saves.
But that might just be a problem of an older breed still on the Intel macs. 🤓

Very frustrating. I've experienced that before and still do from time to time. I'm actually not sure if this is even really down to a more complex setup as much as it is just ESLint being slow from time to time. Small tip: I find that restarting the ESLint server usually solves the issue for me: CMD + P then ESLint: Restart ESLint Server.

Nice one! I'll try next time.

Yeah I agree with Moritz on this one. If we have a strict setup, disable the eslint on save action and setup a pre-commit hook we'd have the situation that I described earlier;

VSCode gives comments about me being sloppy
Won't be annoying on save unless I want it to run: cmnd/shift + p -> Eslint: all auto-fixable Problems
Pre-commit it will auto align everything on my staged changes

Sounds like a good implementation to me 🦦

Yeah I agree with Moritz on this one. If we have a strict setup, disable the eslint on save action and setup a pre-commit hook we'd have the situation that I described earlier;

VSCode gives comments about me being sloppy
Won't be annoying on save unless I want it to run: cmnd/shift + p -> Eslint: all auto-fixable Problems
Pre-commit it will auto align everything on my staged changes

Sounds like a good implementation to me 🦦

Think this is very much a personal preference thing tbh. I quite like the experience of getting linting on save given it's instant 🤷 My coding style is very much; push little but often and find Husky slows down the process personally. Whenever I've used Husky it's just become more of an hindrance.
For the type of experience your looking for, I reckon there is probably ways you could achieve that?

Disable lint on save in your own VSCode settings
Find a way to run a pre-commit hook outside of a fixed package.json change?

Let's move this conversation to the boilerplate since it's more relevant on the config there 👍

It's been great lads, let's carry this on "over there".


docker build failing due to bunch install issue

https://github.com/cjkrolak/ThermostatSupervisor/actions/runs/3414654172/jobs/5682890653
#22 [linux/amd64 4/5] RUN pip3 install -r requirements.txt
#22 3.349 Collecting bunch>=1.0.1
#22 3.393   Downloading bunch-1.0.1.zip (11 kB)
#22 3.402   Preparing metadata (setup.py): started
#22 4.393   Preparing metadata (setup.py): finished with status 'error'
#22 4.409   error: subprocess-exited-with-error
#22 4.409
#22 4.409   × python setup.py egg_info did not run successfully.
#22 4.409   │ exit code: 1
#22 4.409   ╰─> [7 lines of output]
#22 4.409       Traceback (most recent call last):
#22 4.409         File "", line 2, in
#22 4.409         File "", line 34, in
#22 4.409         File "/tmp/pip-install-yovzzhv_/bunch_bbdae4c93a6544209182806454c0d8f8/setup.py", line 11, in
#22 4.409           package_file = open(join(HERE, 'bunch/init.py'), 'rU')
#22 4.409                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#22 4.409       ValueError: invalid mode: 'rU'
#22 4.409       [end of output]
#22 4.409
#22 4.409   note: This error originates from a subprocess, and is likely not a problem with pip.
#22 4.412 error: metadata-generation-failed
#22 4.412
#22 4.412 × Encountered error while generating package metadata.
#22 4.412 ╰─> See above for output.
#22 4.412
#22 4.412 note: This is an issue with the package mentioned above, not pip.
#22 4.412 hint: See above for details.
#22 4.547
#22 4.547 [notice] A new release of pip available: 22.3 -> 22.3.1
#22 4.547 [notice] To update, run: pip install --upgrade pip
#22 ERROR: process "/bin/sh -c pip3 install -r requirements.txt" did not complete successfully: exit code: 1

this issue has been failing since 11/7/22. Last passing run does not have a log anymore for comparison.

bunch 1.0.1 is incompatible with python 3.11, set python version in Dockerfile to 3.10 to mitigate the issue.


Real-world testing

Get this set up on dedicated hardware and in the hands of myself and a few other people.
Try using it for a while, see what complaints show up, and try to address them.
Blocked by:

#3
#4
Probably others (TODO: complete this list)

I'd like to be able to use it in the real world, even if it's still rough enough that I prefer Proloquo (my current go-to), sometime in the next few months.


Implement a kubetest2 tester for e2e-framework

This is a marker issue to indicate that this project should have a Kubetest2  tester implemented. Kubetest2 can stand up an environment and/or lunch tests. It has several providers implemented including kind, gce, etc.
Adding a kubetest2 tester would allow this project to delegate environment startup/tear down to kubetest2 and reuse existing providers.  I propose that the implementation be contributed to the kubetest2 project to make it easy to build/run.
Test writers who are looking to adopt kubetest2 can use this project to write tests and use the kubetest2 binary to launch the test similar to the following:
kubetest2 kind -v 2 \
  --up \
  --down \
  --test=e2e-framework \
  --assess='boombap'
  --skip-assessment='network'

This would be super nice. We are currently looking for an end-to-end test framework to test our k8s setup. How far up the road would you guess this feature is? Is there currently a workaround for this?

Hi @tyxeron  there is currently no one immediately working on this. It's mostly a nice to have since the e2e framework provides its own programmatic way of managing test lifecycles including the ability to launch external environments.
Please take a look at the examples for ways of running end-to-end tests using code that can launch kind as part of the test lifecycle. While kind is the only env that is inherently supported, the api is easy to support any env.
Hope that helps

/remove-lifecycle stale

See https://github.com/kubernetes-sigs/kubetest2/pull/218

/remove-lifecycle stale


chore: bump field-editor-date version to 1.2.0

Doesn't seem to be, do I need to do anything to kick it off?


Testing the action on GitHub-hosted ubuntu runners

Closes #38
Summary
The PR adds jobs to test.yml to run the action on GitHub ubuntu runners.
Updated the README with instructions. Also added a note about the ubuntu-24.04 being a beta version.

@j-rivero I have not changed the workflow for the pre-release and nightly jobs.  Do you want me make similar changes there too?

@j-rivero I have not changed the workflow for the pre-release and nightly jobs.  Do you want me to make similar changes there too?

Thanks for the PR ! This confirms that we don't need to modify any single line of code of the setup-gazebo (the typescript and command instructions). So only the consumer of that package (the yaml code of the user of setup-gazebo, in this case test.yml)  need to specify if it want to use containers or not.
Said this, I think that would be a good idea to have in the README:

As the very basic use case: no containers at all
After this, show how can someone run it in a container (like we currently have it)

Another question is: how do we want to create our tests, that is actually a consumer of the setup-gazebo action. Given that there is no benefit for us on having the tests running on the bare metal runner, it is probably a good idea to the main tests (basic, nightly and prerelease) keep them running on containers and maybe add a test that runs on bare-metal to be sure that there is nothing in that use case that is broken.
So summarizing:

I would not change the test.yml code just add a new test running on bare metal.
Change README so the first use case for the user is the simple use of the action on bare-metal runners. Keeping the current use case below as an alternative for them to use containers.

Sounds good to you @sauk2 ?

Sounds good to you @sauk2 ?

Thanks. Sounds great!!

Minor changes suggested and we are good to go 🚀

Thanks for your feedback! I have made the changes you suggested. All check pass, ready for merge :rocket:


Gke feature flag

Description

Type of change

[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] New feature / enhancement (non-breaking change which adds functionality)
[ ] Security fix
[ ] Bug fix (non-breaking change which fixes an issue)

Checklist:

[ ] Add changelog entry following the contributing guide
[ ] Documentation has been updated
[ ] This change requires changes in testing:

[ ] unit tests
[ ] E2E tests

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

The new common-library helper is located on: https://github.com/newrelic/helm-charts/pull/1178

I've been attempting to write unit test, but it doesn't like nil values.  Keep running into, i can use a bit of help to fix that.
executing "newrelic.common.gkeAutopilot" at <.Values.global.gkeAutopilot>: nil pointer evaluating interface {}.gkeAutopilot


fluidd: 1.30.4 -> 1.30.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cadriel/fluidd/releases.
meta.description for fluidd is: Klipper web interface
meta.homepage for fluidd is: https://docs.fluidd.xyz
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.30.5 with grep in /nix/store/7wm0h2a0djkr9q98n549awn2sv8wp6c3-fluidd-1.30.5
found 1.30.5 in filename of file in /nix/store/7wm0h2a0djkr9q98n549awn2sv8wp6c3-fluidd-1.30.5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

fluidd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7wm0h2a0djkr9q98n549awn2sv8wp6c3-fluidd-1.30.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fluidd https://github.com/r-ryantm/nixpkgs/archive/d17b5e240e5eb3075abfa8d694a87a33f5a97d76.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d17b5e240e5eb3075abfa8d694a87a33f5a97d76#fluidd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7wm0h2a0djkr9q98n549awn2sv8wp6c3-fluidd-1.30.5
ls -la /nix/store/7wm0h2a0djkr9q98n549awn2sv8wp6c3-fluidd-1.30.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

fluidd

Maintainer pings
cc @zhaofengli for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 349937

x86_64-linux

:white_check_mark: 1 package built:

fluidd


Why Use Ortelius

Under Agentless Delivery:
"Ubantu, Redhat, SuSe, Debina" should be "Ubuntu, Redhat, SuSe, Debian"

Hi @boucains Can you please guide me through what is to be done? Your help will be much appreciated : )

Moving issue over to ortelius/ortelius repo to keep everything in one place.


fix(bookmark tile menu)#89

able to click anywhere on page to close the drop down menus that removed bookmark or gets help.

@tonyalletag @wski @SOAP1914 @clarkjefcoat

investigate trying this
componentDidMount: function() {
  $('document').click(function() {
    this.closeMenu(this.refs.checkbox);
  });

  $(this.refs.checkbox).click(function(event) {
      event.stopPropagation();
  });
},

closeMenu: function(el) {
  $(el).checked('checked', false);
},

If this doesn't work I think your method is fine for now, but mapping the click to x,y is a bit scary in the case that some css hacks take place, or things reorder. This would also drop the need for the id's
Also as a side note make sure you add ESLint with google style preset to check spacing for code readability.
UPDATE: I've added the close menu function that should work.


TypeError: pop expected at most 1 argument, got 2

Summary
Traceback (most recent call last):
    response = session.get("/dataservice/admin/resourcegroup")
  File "/home/user/env/lib/python3.8/site-packages/vmngclient/session.py", line 126, in get
    return vManageResponse(super().get(url, *args, **kwargs))
  File "/home/user/env/lib/python3.8/site-packages/requests/sessions.py", line 600, in get
    return self.request("GET", url, **kwargs)
  File "/home/user/env/lib/python3.8/site-packages/vmngclient/session.py", line 184, in request
    self.logger.debug(self.response_trace(response, None))
  File "/home/user/env/lib/python3.8/site-packages/vmngclient/__init__.py", line 22, in wrapper
    wrapped = method(*args, **kwargs)
  File "/home/user/env/lib/python3.8/site-packages/vmngclient/response.py", line 91, in response_history_debug
    response_debugs += [response_debug(response, request)]
  File "/home/user/env/lib/python3.8/site-packages/vmngclient/response.py", line 61, in response_debug
    json.pop("header", None)
TypeError: pop expected at most 1 argument, got 2

Logs and external information
Request was not logged in vmngclient.log due to the exception. The response json does not have a "header"/"data" key like other responses.
I added this print statement to log the response
# python3.8/site-packages/vmngclient/response.py

        try:
            json = response.json()
            print(request_debug["url"], json) <--------------------------------
            json.pop("header", None)
            response_debug.update({"json": json})
        except JSONDecodeError:
            if response.encoding is not None:
                if len(response.text) <= 1024:

/dataservice/admin/resourcegroup

[{'id': '0:RESOURCE_GROUPNode:1641915164240:2', 'name': 'global', 'desc': 'System defined group for global network resources managed by global netadmins and readonly to all users.', 'siteIds': [], 'siteIdsIncludeShared': [...

Other responses:
/dataservice/client/server

{'header': {'generatedOn':<PHONE_NUMBER>037}, 'data': {'server': 'vManage1', 'tenancyMode': 'SingleTenant', 'userMode': 'tenant', 'VSessionId': 'ZGVmYXVsdA==',....}

Reproduction script
    response = session.get("/dataservice/admin/resourcegroup")

On what platform(s) does it occur?
Linux
Issue Severity
Low: It annoys me

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/issues/236


Widget values now use value formatter

Currently the values displayed in the slider widget text box and dropdown menu are derived from the raw value (with some rounding applied). However as suggested in #548 the widgets should also use the dimensions value formatter if specified. This allows timestamps to be formatted correctly, for example, ensuring that you don't get mismatching labels between the title and the widget. The only issue with this approach is that the formatted version can often be longer and therefore become unreadable. Before merging I'd like to brainstorm a little bit about what we can do for very long labels. Here is an example:

Note I also reindented the jinja template because it was a mess.

I think that even if it's longer, it's better to have it show a meaningful value.  Right justifying it would help a bit, since the fastest-changing bit is typically on the right.  I guess we could auto-size (at least, auto-increase) the widget based on the first value's width plus a tiny extra margin?  And/or allow the user to specify the width as a style option?

I'd prefer not to adjust the widget width as screen real-estate is important and allocating more than 25% of the screen width to the widget seems excessive. In future when designing more customizable widgets we should definitely keep this in mind though.
For now I'm playing with solutions that automatically adjusts the size of the font. Something like this works reasonably well:
if (txt.val().length > 10) {
    text.css('font-size', 100-Math.min(text.val().length*2.4, 50)+'%');

Adjusting the fonts seems fine for now.
The text boxes on the right display the values make it conceivable that values could be edited and then set directly. For other values such as the dates, textual editing wouldn't be particularly easy so I can imagine a different type of slider that takes up the full width that only shows the value when you hover or drag the slider bar. I suppose the problem with that idea is you wouldn't be able to see the selected value immediately (e.g after exporting the notebook).
Anyway, this is a good usability improvement and I'm happy to merge if we agree changing the font size is the best thing for now.

It seems like there is always going to be a tension between readability and width on the page, with the layout above.  Is it not possible to use a more compact layout, like:

That was what the widgets looked like originally. We moved away from that deliberately due to alignment issues and because it only works well for short dimension names.

Previously, did the space for the value automatically spread to cover the space remaining after the dimension name?  The dimension names are up to the user to choose, and so it seems like they can decide to favor having long names or more room to edit values, and as long as they don't demand both at once for the same dimension, everything would fit into less space.

Previously, did the space for the value automatically spread to cover the space remaining after the dimension name?

No you're right that wasn't the case before, the question remains what happens if the name is so long it squashes the text area entirely. I guess you could limit it to a 80/20 or similar and truncate the dimension name if it doesn't fit in that space.
I think we should revisit this once we have decided on what we want to do about widgets in general. Getting the UI right is fiddly and will take time I don't want to commit at the moment. Since we already depend on jquery-ui we could however allow some basic resizing. By adding a few lines I was able to get something working, you can see the behavior here: https://sendvid.com/pngy9ip0

Resizing would be very useful...

@philippjfr That looks pretty good!
That seems like a nice improvement for now. The reason I suggested showing values on hover because then long dimension names and long value names wouldn't be competing for space.

Sure, those limits sound reasonable.  Yes, hovering does help avoid competition between long names and long values, but both of them are important to have as a record and a manifest of what's being shown in the plot, so one would really like both of them to be onscreen at all times.  I would hope that with the above re-organization plus the ability to drag the area to make it bigger, we wouldn't get many complaints about unusable widgets anymore...

I've restricted the functionality a little bit since that demo because there was lots of potential for strange behavior. Here's what it looks like now: https://sendvid.com/o251s606
I think that gives sufficient control to actually see the values if they are really long and we can work out better solutions for sizing, moving and otherwise improving the widgets once we've decided what libraries we should build it on.

Sounds good for now.

@jlstevens if you agree this is ready to merge now.

Ok great! Merging...


chore: New NS icon

Updated extension logo from old one to the new logo rendered from the one available at Nativescript/artwork repo

Thanks! Just thought about this yesterday with @vallemar!

Hehe no problem! These things always catch my eye and it's just an easy fix! 😄

@guillemc23  Thanks!!!


update() function stopped working

Hello there !
I've configured time interval parameter in begin() function to 1500 ms and I've noticed that every time my sensor after some time stopped responding.
I did some investigation with debug messages and I've discovered that this line has to be changed, otherwise the state machine of yours inside update() function never escapes state "waitingNextReading".
I've initialized your wrapper like this:
// DS18B20
//Initialize the sensor passing the resolution, unit of measure and reading interval [milliseconds]
sensorDs18b20.begin(NonBlockingDallas::resolution_12, NonBlockingDallas::unit_C, TIME_INTERVAL);
//Callbacks
sensorDs18b20.onIntervalElapsed(handleIntervalElapsed);
sensorDs18b20.onTemperatureChange(handleTemperatureChange);

And I'm using sensorDs18b20.update(); function inside in my main.
I believe that this check is not correct:
if(_lastReadingMillis != 0 && (millis() - _lastReadingMillis < _tempInterval - _conversionMillis)) return;

Correct me if I'm wrong but at some point I end up having this message at the debug (I've added some custom Serial.prints):

_lastReadingMillis= 2315064
_conversionMillis= 20024
_tempInterval - _conversionMillis=<PHONE_NUMBER>
if case: (_lastReadingMillis != 0 && (millis() - _lastReadingMillis < _tempInterval - _conversionMillis))= 1
if case: (_lastReadingMillis != 0)=  1
if case: (boolean)(millis() - _lastReadingMillis < _tempInterval - _conversionMillis)= 1
sensor state 1

This led me to think that you should simply check if time interval has passed and not to check all the above sections. I found no guard that guaranties that _conversionMillis wont get higher value of _tempInterval. Probably there is some blocking code in my program that causes the problem. I can't imagine how else this could end up wrong.
In order to fix this I've changed your if case to this:
if(millis() - _lastReadingMillis < _tempInterval) return;
_lastReadingMillis= millis();
requestTemperature();

And I've commended out _lastReadingMillis = millis(); inside function readSensors()
I will try this tonight and see tomorrow if the error persists.
Kind regards,
kif

Hello @K-IF
Removing this condition _lastReadingMillis != 0 you will have to wait for time interval to elapse before getting the very first reading of the sensor. It is not convenient especially in case interval is very high (i.e. 30 minutes or more)
And I've commended out _lastReadingMillis = millis(); inside function readSensors()

How are you supposed to save the time then? The reading of the sensor will be always triggered regardless of time interval.
The value of _conversionMillis that I can see from your debug is too high, it shouldn't be more than 750ms. I have the feeling that there is some other issue in your sketch.
I am not sure how you are using the library but I would suggest not to add too much code in the body of the callbacks to avoid blocking the execution.

Good morning @Gbertaz .
I'm sorry for the late response.
Regarding the update of _lastReadingMillis variable, I'm reading the value of millis right after passing the if statement at waitNextReading function.
Library's waitNextReading function:
void NonBlockingDallas::waitNextReading(){ 	if(_lastReadingMillis != 0 && (millis() - _lastReadingMillis < _tempInterval - _conversionMillis)) return; 	requestTemperature(); }
The change that I've done:
void NonBlockingDallas::waitNextReading(){ 	if( (_lastReadingMillis != 0) && ((millis() - _lastReadingMillis) < _tempInterval) )          {              return;         } 	_lastReadingMillis= millis(); 	requestTemperature(); }
I agree on using the (_lastReadingMillis != 0) condition. I didn't think of the first reading issue for longer time intervals. Usually I'm using an init flag for such things.
Regarding the second part of your answer I believe that either the wifi handler or the MQTT connection handler is stalling the program that ends up the increase of _conversionMillis variable. In my case I just removed conversionMillis from the conditional statement and I have no more issue there. If you think it is an action that occurs every X time interval + almost a fixed conversionMillis delay.
Thank you for your time and for the great wrapper that you've developed !

Glad to know you solved the problem @K-IF.
I will consider adding a fix to avoid the same problem in future. Thank you for using the library.


|                                      100th percentile latency |                            system/syslog/lens/no_minimized_roundtrips |  18775.8         |  19003           |     227.236   |     ms |   +1.21% |
|                                  50th percentile service time |                            system/syslog/lens/no_minimized_roundtrips |   8756.87        |   8766.46        |       9.5918  |     ms |   +0.11% |
|                                  90th percentile service time |                            system/syslog/lens/no_minimized_roundtrips |   9013.91        |   9038.98        |      25.0754  |     ms |   +0.28% |
|                                 100th percentile service time |                            system/syslog/lens/no_minimized_roundtrips |   9040.54        |   9078.23        |      37.6865  |     ms |   +0.42% |
|                                                    error rate |                            system/syslog/lens/no_minimized_roundtrips |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                                                       mysql/dashboard |      0.00224876  |      0.00224875  |      -0       |  ops/s |   -0.00% |
|                                               Mean Throughput |                                                       mysql/dashboard |      0.00864329  |      0.00864334  |       0       |  ops/s |    0.00% |
|                                             Median Throughput |                                                       mysql/dashboard |      0.00846034  |      0.00846033  |      -0       |  ops/s |   -0.00% |
|                                                Max Throughput |                                                       mysql/dashboard |      0.0148343   |      0.0148342   |      -0       |  ops/s |   -0.00% |
|                                       50th percentile latency |                                                       mysql/dashboard |    642.542       |    653.067       |      10.5246  |     ms |   +1.64% |
|                                       90th percentile latency |                                                       mysql/dashboard |   1170.79        |   1143.03        |     -27.7575  |     ms |   -2.37% |
|                                      100th percentile latency |                                                       mysql/dashboard |   1187.74        |   1159.72        |     -28.0231  |     ms |   -2.36% |
|                                  50th percentile service time |                                                       mysql/dashboard |    601.837       |    618.986       |      17.1494  |     ms |   +2.85% |
|                                  90th percentile service time |                                                       mysql/dashboard |    994.745       |   1081.43        |      86.6859  |     ms |   +8.71% |
|                                 100th percentile service time |                                                       mysql/dashboard |   1186.03        |   1138.47        |     -47.556   |     ms |   -4.01% |
|                                                    error rate |                                                       mysql/dashboard |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                               mysql/dashboard/no_minimized_roundtrips |      0.00220735  |      0.00220774  |       0       |  ops/s |   +0.02% |
|                                               Mean Throughput |                               mysql/dashboard/no_minimized_roundtrips |      0.00821147  |      0.00820956  |      -0       |  ops/s |   -0.02% |
|                                             Median Throughput |                               mysql/dashboard/no_minimized_roundtrips |      0.00824718  |      0.00824547  |      -0       |  ops/s |   -0.02% |
|                                                Max Throughput |                               mysql/dashboard/no_minimized_roundtrips |      0.0138337   |      0.0138294   |      -0       |  ops/s |   -0.03% |
|                                       50th percentile latency |                               mysql/dashboard/no_minimized_roundtrips |  41705.4         |  42098.7         |     393.279   |     ms |   +0.94% |
|                                       90th percentile latency |                               mysql/dashboard/no_minimized_roundtrips |  68860           |  69221.8         |     361.802   |     ms |   +0.53% |
|                                      100th percentile latency |                               mysql/dashboard/no_minimized_roundtrips |  71226.1         |  71594.7         |     368.523   |     ms |   +0.52% |
|                                  50th percentile service time |                               mysql/dashboard/no_minimized_roundtrips |   8784.74        |   8845.94        |      61.2022  |     ms |   +0.70% |
|                                  90th percentile service time |                               mysql/dashboard/no_minimized_roundtrips |   9188.74        |   9225.84        |      37.1081  |     ms |   +0.40% |
|                                 100th percentile service time |                               mysql/dashboard/no_minimized_roundtrips |   9928.44        |   9916.53        |     -11.9111  |     ms |   -0.12% |
|                                                    error rate |                               mysql/dashboard/no_minimized_roundtrips |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                                                                 redis |      0.00954254  |      0.0095418   |      -0       |  ops/s |   -0.01% |
|                                               Mean Throughput |                                                                 redis |      0.040223    |      0.039069    |      -0.00115 |  ops/s |   -2.87% |
|                                             Median Throughput |                                                                 redis |      0.0420558   |      0.040707    |      -0.00135 |  ops/s |   -3.21% |
|                                                Max Throughput |                                                                 redis |      0.0676705   |      0.0676668   |      -0       |  ops/s |   -0.01% |
|                                       50th percentile latency |                                                                 redis |    840.329       |    796.431       |     -43.898   |     ms |   -5.22% |
|                                       90th percentile latency |                                                                 redis |   1446.57        |   1546.12        |      99.5558  |     ms |   +6.88% |
|                                      100th percentile latency |                                                                 redis |   1618.49        |   1711.29        |      92.8014  |     ms |   +5.73% |
|                                  50th percentile service time |                                                                 redis |    816.534       |    784.275       |     -32.26    |     ms |   -3.95% |
|                                  90th percentile service time |                                                                 redis |   1411.01        |   1495.77        |      84.7587  |     ms |   +6.01% |
|                                 100th percentile service time |                                                                 redis |   1617.44        |   1710.43        |      92.9899  |     ms |   +5.75% |
|                                                    error rate |                                                                 redis |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                                         redis/no_minimized_roundtrips |      0.00932912  |      0.00932597  |      -0       |  ops/s |   -0.03% |
|                                               Mean Throughput |                                         redis/no_minimized_roundtrips |      0.0247162   |      0.0246727   |      -4e-05   |  ops/s |   -0.18% |
|                                             Median Throughput |                                         redis/no_minimized_roundtrips |      0.0265476   |      0.0264838   |      -6e-05   |  ops/s |   -0.24% |
|                                                Max Throughput |                                         redis/no_minimized_roundtrips |      0.0337785   |      0.0337583   |      -2e-05   |  ops/s |   -0.06% |
|                                       50th percentile latency |                                         redis/no_minimized_roundtrips | 140943           | 142227           |    1283.94    |     ms |   +0.91% |
|                                       90th percentile latency |                                         redis/no_minimized_roundtrips | 416567           | 418330           |    1762.55    |     ms |   +0.42% |
|                                      100th percentile latency |                                         redis/no_minimized_roundtrips | 462866           | 464780           |    1913.88    |     ms |   +0.41% |
|                                  50th percentile service time |                                         redis/no_minimized_roundtrips |   9260.73        |   9340.36        |      79.6367  |     ms |   +0.86% |
|                                  90th percentile service time |                                         redis/no_minimized_roundtrips |  49804.1         |  50125           |     320.907   |     ms |   +0.64% |
|                                 100th percentile service time |                                         redis/no_minimized_roundtrips |  50371.7         |  50384.7         |      13.0156  |     ms |   +0.03% |
|                                                    error rate |                                         redis/no_minimized_roundtrips |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                                                            mysql/lens |      0.00675143  |      0.00675148  |       0       |  ops/s |    0.00% |
|                                               Mean Throughput |                                                            mysql/lens |      0.0272501   |      0.0272527   |       0       |  ops/s |    0.01% |
|                                             Median Throughput |                                                            mysql/lens |      0.028152    |      0.0281533   |       0       |  ops/s |    0.00% |
|                                                Max Throughput |                                                            mysql/lens |      0.0446939   |      0.044699    |       1e-05   |  ops/s |   +0.01% |
|                                       50th percentile latency |                                                            mysql/lens |    834.051       |    924.114       |      90.0637  |     ms |  +10.80% |
|                                       90th percentile latency |                                                            mysql/lens |   1321.22        |   1699.11        |     377.894   |     ms |  +28.60% |
|                                      100th percentile latency |                                                            mysql/lens |   1636.91        |   1814.86        |     177.943   |     ms |  +10.87% |
|                                  50th percentile service time |                                                            mysql/lens |    831.162       |    880.972       |      49.8101  |     ms |   +5.99% |
|                                  90th percentile service time |                                                            mysql/lens |   1184.03        |   1513.22        |     329.192   |     ms |  +27.80% |
|                                 100th percentile service time |                                                            mysql/lens |   1320.03        |   1813.85        |     493.819   |     ms |  +37.41% |
|                                                    error rate |                                                            mysql/lens |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                                    mysql/lens/no_minimized_roundtrips |      0.00673111  |      0.00673078  |      -0       |  ops/s |   -0.00% |
|                                               Mean Throughput |                                    mysql/lens/no_minimized_roundtrips |      0.0208024   |      0.020778    |      -2e-05   |  ops/s |   -0.12% |
|                                             Median Throughput |                                    mysql/lens/no_minimized_roundtrips |      0.0216333   |      0.0216105   |      -2e-05   |  ops/s |   -0.11% |
|                                                Max Throughput |                                    mysql/lens/no_minimized_roundtrips |      0.025004    |      0.0250027   |      -0       |  ops/s |   -0.01% |
|                                       50th percentile latency |                                    mysql/lens/no_minimized_roundtrips | 103588           | 103805           |     216.727   |     ms |   +0.21% |
|                                       90th percentile latency |                                    mysql/lens/no_minimized_roundtrips | 227607           | 228834           |    1227.14    |     ms |   +0.54% |
|                                      100th percentile latency |                                    mysql/lens/no_minimized_roundtrips | 234501           | 235173           |     672.156   |     ms |   +0.29% |
|                                  50th percentile service time |                                    mysql/lens/no_minimized_roundtrips |  49329.4         |  49459.6         |     130.152   |     ms |   +0.26% |
|                                  90th percentile service time |                                    mysql/lens/no_minimized_roundtrips |  49831.8         |  50041.4         |     209.647   |     ms |   +0.42% |
|                                 100th percentile service time |                                    mysql/lens/no_minimized_roundtrips |  50063.9         |  50301.5         |     237.637   |     ms |   +0.47% |
|                                                    error rate |                                    mysql/lens/no_minimized_roundtrips |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                                                   postgresql/overview |      0.00512419  |      0.00512465  |       0       |  ops/s |    0.01% |
|                                               Mean Throughput |                                                   postgresql/overview |      0.0541027   |      0.0541052   |       0       |  ops/s |    0.00% |
|                                             Median Throughput |                                                   postgresql/overview |      0.0578911   |      0.0578943   |       0       |  ops/s |    0.01% |
|                                                Max Throughput |                                                   postgresql/overview |      0.0810353   |      0.0810387   |       0       |  ops/s |    0.00% |
|                                       50th percentile latency |                                                   postgresql/overview |   1209.5         |   1215.48        |       5.97931 |     ms |   +0.49% |
|                                       90th percentile latency |                                                   postgresql/overview |   1920.59        |   1866.42        |     -54.177   |     ms |   -2.82% |
|                                      100th percentile latency |                                                   postgresql/overview |   2555.11        |   2589.5         |      34.3867  |     ms |   +1.35% |
|                                  50th percentile service time |                                                   postgresql/overview |   1201.81        |   1206.74        |       4.92297 |     ms |   +0.41% |
|                                  90th percentile service time |                                                   postgresql/overview |   1528.56        |   1567.04        |      38.4787  |     ms |   +2.52% |
|                                 100th percentile service time |                                                   postgresql/overview |   2012.8         |   2106.23        |      93.4314  |     ms |   +4.64% |
|                                                    error rate |                                                   postgresql/overview |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                           postgresql/overview/no_minimized_roundtrips |      0.00504411  |      0.00504038  |      -0       |  ops/s |   -0.07% |
|                                               Mean Throughput |                           postgresql/overview/no_minimized_roundtrips |      0.0345048   |      0.0344581   |      -5e-05   |  ops/s |   -0.14% |
|                                             Median Throughput |                           postgresql/overview/no_minimized_roundtrips |      0.0365461   |      0.0364971   |      -5e-05   |  ops/s |   -0.13% |
|                                                Max Throughput |                           postgresql/overview/no_minimized_roundtrips |      0.0536954   |      0.0536251   |      -7e-05   |  ops/s |   -0.13% |
|                                       50th percentile latency |                           postgresql/overview/no_minimized_roundtrips | 164970           | 165752           |     782.703   |     ms |   +0.47% |
|                                       90th percentile latency |                           postgresql/overview/no_minimized_roundtrips | 226444           | 228138           |    1693.72    |     ms |   +0.75% |
|                                      100th percentile latency |                           postgresql/overview/no_minimized_roundtrips | 289993           | 291873           |    1880.34    |     ms |   +0.65% |
|                                  50th percentile service time |                           postgresql/overview/no_minimized_roundtrips |   6146.43        |   6172.06        |      25.6338  |     ms |   +0.42% |
|                                  90th percentile service time |                           postgresql/overview/no_minimized_roundtrips |  35582.7         |  35681.5         |      98.8133  |     ms |   +0.28% |
|                                 100th percentile service time |                           postgresql/overview/no_minimized_roundtrips |  36643.7         |  36545.1         |     -98.6133  |     ms |   -0.27% |
|                                                    error rate |                           postgresql/overview/no_minimized_roundtrips |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                                                   postgresql/duration |      0.0220715   |      0.0220712   |      -0       |  ops/s |   -0.00% |
|                                               Mean Throughput |                                                   postgresql/duration |      0.0680291   |      0.0678929   |      -0.00014 |  ops/s |   -0.20% |
|                                             Median Throughput |                                                   postgresql/duration |      0.065871    |      0.0658679   |      -0       |  ops/s |   -0.00% |
|                                                Max Throughput |                                                   postgresql/duration |      0.135703    |      0.135682    |      -2e-05   |  ops/s |   -0.02% |
|                                       50th percentile latency |                                                   postgresql/duration |    598.22        |    619.522       |      21.3022  |     ms |   +3.56% |
|                                       90th percentile latency |                                                   postgresql/duration |   1280.44        |   1360.09        |      79.6508  |     ms |   +6.22% |
|                                      100th percentile latency |                                                   postgresql/duration |   1600.27        |   1478.88        |    -121.392   |     ms |   -7.59% |
|                                  50th percentile service time |                                                   postgresql/duration |    526.065       |    543.846       |      17.7815  |     ms |   +3.38% |
|                                  90th percentile service time |                                                   postgresql/duration |    939.438       |   1202.5         |     263.061   |     ms |  +28.00% |
|                                 100th percentile service time |                                                   postgresql/duration |   1598.66        |   1380.72        |    -217.941   |     ms |  -13.63% |
|                                                    error rate |                                                   postgresql/duration |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                           postgresql/duration/no_minimized_roundtrips |      0.0220556   |      0.022057    |       0       |  ops/s |    0.01% |
|                                               Mean Throughput |                           postgresql/duration/no_minimized_roundtrips |      0.0519331   |      0.0517551   |      -0.00018 |  ops/s |   -0.34% |
|                                             Median Throughput |                           postgresql/duration/no_minimized_roundtrips |      0.0522277   |      0.0520396   |      -0.00019 |  ops/s |   -0.36% |
|                                                Max Throughput |                           postgresql/duration/no_minimized_roundtrips |      0.0750403   |      0.0749224   |      -0.00012 |  ops/s |   -0.16% |
|                                       50th percentile latency |                           postgresql/duration/no_minimized_roundtrips |  87629.3         |  88870           |    1240.75    |     ms |   +1.42% |
|                                       90th percentile latency |                           postgresql/duration/no_minimized_roundtrips | 287538           | 289331           |    1792.72    |     ms |   +0.62% |
|                                      100th percentile latency |                           postgresql/duration/no_minimized_roundtrips | 297789           | 300573           |    2783.66    |     ms |   +0.93% |
|                                  50th percentile service time |                           postgresql/duration/no_minimized_roundtrips |   4987.65        |   4934.97        |     -52.686   |     ms |   -1.06% |
|                                  90th percentile service time |                           postgresql/duration/no_minimized_roundtrips |  49897           |  50095.2         |     198.211   |     ms |   +0.40% |
|                                 100th percentile service time |                           postgresql/duration/no_minimized_roundtrips |  50407           |  50442.1         |      35.0273  |     ms |   +0.07% |
|                                                    error rate |                           postgresql/duration/no_minimized_roundtrips |      0           |      0           |       0       |      % |    0.00% |
|                                                Min Throughput |                                                            field-caps |      0.187197    |      0.187198    |       0       |  ops/s |    0.00% |
|                                               Mean Throughput |                                                            field-caps |      0.204705    |      0.204621    |      -8e-05   |  ops/s |   -0.04% |
|                                             Median Throughput |                                                            field-caps |      0.206076    |      0.205877    |      -0.0002  |  ops/s |   -0.10% |
|                                                Max Throughput |                                                            field-caps |      0.230659    |      0.230666    |       1e-05   |  ops/s |    0.00% |
|                                       50th percentile latency |                                                            field-caps |     95.9513      |     96.7132      |       0.76198 |     ms |   +0.79% |
|                                       90th percentile latency |                                                            field-caps |    118.829       |    102.555       |     -16.2741  |     ms |  -13.70% |
|                                       99th percentile latency |                                                            field-caps |    256.81        |    312.394       |      55.5838  |     ms |  +21.64% |
|                                      100th percentile latency |                                                            field-caps |    527.575       |    374.385       |    -153.19    |     ms |  -29.04% |
|                                  50th percentile service time |                                                            field-caps |     93.7208      |     94.4387      |       0.71795 |     ms |   +0.77% |
|                                  90th percentile service time |                                                            field-caps |    116.646       |     99.3151      |     -17.3314  |     ms |  -14.86% |
|                                  99th percentile service time |                                                            field-caps |    255.537       |    265.41        |       9.87331 |     ms |   +3.86% |
|                                 100th percentile service time |                                                            field-caps |    524.801       |    317.032       |    -207.768   |     ms |  -39.59% |
|                                                    error rate |                                                            field-caps |      0           |      0           |       0       |      % |    0.00% |

-------------------------------
[INFO] SUCCESS (took 0 seconds)
-------------------------------

I also tested the many-shards-snapshots challenge, and lucky I did because I found a bug and fixed a TODO :-)

@elasticmachine run rally/it-python38

I also tested the many-shards-snapshots challenge, and lucky I did because I found a bug and fixed a TODO :-)

Great to see this tech debt item fixed as well via this PR/upgrade.

|                                                Min Throughput |                     wait-for-snapshots |      0.000216738 |      0.00017935  |     -4e-05   |  ops/s |  -17.25% |
|                                               Mean Throughput |                     wait-for-snapshots |      0.000216738 |      0.00017935  |     -4e-05   |  ops/s |  -17.25% |
|                                             Median Throughput |                     wait-for-snapshots |      0.000216738 |      0.00017935  |     -4e-05   |  ops/s |  -17.25% |
|                                                Max Throughput |                     wait-for-snapshots |      0.000216738 |      0.00017935  |     -4e-05   |  ops/s |  -17.25% |
|                                      100th percentile latency |                     wait-for-snapshots |      4.61386e+06 |      5.5757e+06  | 961844       |     ms |  +20.85% |
|                                 100th percentile service time |                     wait-for-snapshots |      4.61386e+06 |      5.5757e+06  | 961844       |     ms |  +20.85% |
|                                                    error rate |                     wait-for-snapshots |      0           |      0           |      0       |      % |    0.00% |

I doubt that the 20% increase in the how long we wait for the snapshots to complete is due to https://github.com/elastic/rally/pull/1669/commits/b9808fc7950e1f2fd5e514a29455ef4bf1e1b0e5 and switching to the native API call es.snapshot.get(index_names=false).
We need to keep an eye on the results in https://elasticsearch-benchmarks.elastic.co/#tracks/many-shards-snapshots/nightly/default/90d after merging. Unfortunately we've been hitting some random unexplainable variability lately.


Upgrade to OpenSSL 3.0 - request

While building the UUU tool locally we've found that this repository still relies on old OpenSSL 1.1 version and we just want to know is the upgrade to OpenSSL 3 in pipeline? When can we expect the update, if so?
Thanks in advance.

CC @tkmozhi

I have not force openssl to 1.1 at https://github.com/nxp-imx/mfgtools/blob/master/libuuu/CMakeLists.txt


Failed to create alert rule Azure Portal Signin from another Azure Tenant

Hello Team,
I am facing below while creating the Analytic rule in Microsoft Sentinel. I have tried in multiple Log Analytics Workspace and regions still facing the same issue. Can someone please help me on this. Thanks in advance.
Below is the error screenshot for reference.

Hi @Rahulg485,
Looks like your file name is not valid anymore. The latest one should be ServiceTags_Public_20220627.json.
Please try again with the updated URL (it worked on my end).
Thanks

Hi Jeremy,
Thanks for the quick help, I have modified the same in KQL query in my test lab which worked 😊.  Will reach you in case any help needed.
Regards,
Rahul Gattadi
Consultant | Microsoft Services
<EMAIL_ADDRESS>[A close up of a logo  Description automatically generated]
From: Jeremy Tan @.>
Sent: Friday, July 1, 2022 2:27 PM
To: Azure/Azure-Sentinel @.>
Cc: RAHUL GATTADI @.>; Mention @.>
Subject: Re: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483)
Hi @Rahulg485https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRahulg485&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=dZkigewDgwl9QPvNZQhhFSoGXXgDp0y84H6obwykirM%3D&reserved=0,
Looks like your file name is not valid anymore. The latest one should be ServiceTags_Public_20220627.json.
Please try again with the updated URL (it worked on my end).
Thanks
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Sentinel%2Fissues%2F5483%23issuecomment-1172109504&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=GMdXbw%2F0fhe12rZ9eLHXyrBpBv4QmoB9tF9mPIKqQvg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZ2RNGUIQVPSZGMCWBYN3G3VR2XHRANCNFSM52BWDSDQ&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Vc0C%2FsyLzo402tX3Z96zJgGpgRmXGeAgKXeKKcDpWhs%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi Jeremy,
We are trying to create the rule in Prod, however we see storage path doesn’t exist even after changing it to ServiceTags_Public_20220627.json. Coud you please check and provide us the updated storage link?
@.***
Regards,
Rahul Gattadi
Consultant | Microsoft Services
<EMAIL_ADDRESS>[A close up of a logo  Description automatically generated]
From: RAHUL GATTADI
Sent: Friday, July 1, 2022 3:25 PM
To: Azure/Azure-Sentinel @.>; Azure/Azure-Sentinel @.>
Cc: Mention @.>; Sanchu Sankar @.>; Vinayak Latthe @.>; Benjamin Kovacevic @.>
Subject: RE: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483)
Hi Jeremy,
Thanks for the quick help, I have modified the same in KQL query in my test lab which worked 😊.  Will reach you in case any help needed.
Regards,
Rahul Gattadi
Consultant | Microsoft Services
<EMAIL_ADDRESS>[A close up of a logo  Description automatically generated]
From: Jeremy Tan<EMAIL_ADDRESS>Sent: Friday, July 1, 2022 2:27 PM
To: Azure/Azure-Sentinel<EMAIL_ADDRESS>Cc: RAHUL GATTADI<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483)
Hi @Rahulg485https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRahulg485&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=dZkigewDgwl9QPvNZQhhFSoGXXgDp0y84H6obwykirM%3D&reserved=0,
Looks like your file name is not valid anymore. The latest one should be ServiceTags_Public_20220627.json.
Please try again with the updated URL (it worked on my end).
Thanks
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Sentinel%2Fissues%2F5483%23issuecomment-1172109504&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=GMdXbw%2F0fhe12rZ9eLHXyrBpBv4QmoB9tF9mPIKqQvg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZ2RNGUIQVPSZGMCWBYN3G3VR2XHRANCNFSM52BWDSDQ&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Vc0C%2FsyLzo402tX3Z96zJgGpgRmXGeAgKXeKKcDpWhs%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi Jeremy and Team,
Could you please help us on this? We need to enable the rule on client Production.
Regards,
Rahul Gattadi
Consultant | Microsoft Services
<EMAIL_ADDRESS>[A close up of a logo  Description automatically generated]
From: RAHUL GATTADI
Sent: Saturday, September 3, 2022 3:49 AM
To: 'Azure/Azure-Sentinel' @.>; 'Azure/Azure-Sentinel' @.>
Cc: 'Mention' @.>; Sanchu Sankar @.>; Vinayak Latthe @.>; Benjamin Kovacevic @.>; Madhur Shukla @.***>
Subject: RE: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483)
Hi Jeremy,
We are trying to create the rule in Prod, however we see storage path doesn’t exist even after changing it to ServiceTags_Public_20220627.json. Coud you please check and provide us the updated storage link?
@.***
Regards,
Rahul Gattadi
Consultant | Microsoft Services
<EMAIL_ADDRESS>[A close up of a logo  Description automatically generated]
From: RAHUL GATTADI
Sent: Friday, July 1, 2022 3:25 PM
To: Azure/Azure-Sentinel<EMAIL_ADDRESS>Azure/Azure-Sentinel<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Sanchu Sankar<EMAIL_ADDRESS>Vinayak Latthe<EMAIL_ADDRESS>Benjamin Kovacevic<EMAIL_ADDRESS>Subject: RE: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483)
Hi Jeremy,
Thanks for the quick help, I have modified the same in KQL query in my test lab which worked 😊.  Will reach you in case any help needed.
Regards,
Rahul Gattadi
Consultant | Microsoft Services
<EMAIL_ADDRESS>[A close up of a logo  Description automatically generated]
From: Jeremy Tan<EMAIL_ADDRESS>Sent: Friday, July 1, 2022 2:27 PM
To: Azure/Azure-Sentinel<EMAIL_ADDRESS>Cc: RAHUL GATTADI<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483)
Hi @Rahulg485https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRahulg485&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=dZkigewDgwl9QPvNZQhhFSoGXXgDp0y84H6obwykirM%3D&reserved=0,
Looks like your file name is not valid anymore. The latest one should be ServiceTags_Public_20220627.json.
Please try again with the updated URL (it worked on my end).
Thanks
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Sentinel%2Fissues%2F5483%23issuecomment-1172109504&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=GMdXbw%2F0fhe12rZ9eLHXyrBpBv4QmoB9tF9mPIKqQvg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZ2RNGUIQVPSZGMCWBYN3G3VR2XHRANCNFSM52BWDSDQ&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Vc0C%2FsyLzo402tX3Z96zJgGpgRmXGeAgKXeKKcDpWhs%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi Jeremy and Team, Could you please help us on this? We need to enable the rule on client Production. Regards, Rahul Gattadi Consultant | Microsoft Services<EMAIL_ADDRESS>[A close up of a logo Description automatically generated] From: RAHUL GATTADI Sent: Saturday, September 3, 2022 3:49 AM To: 'Azure/Azure-Sentinel' @.>; 'Azure/Azure-Sentinel' @.> Cc: 'Mention' @.>; Sanchu Sankar @.>; Vinayak Latthe @.>; Benjamin Kovacevic @.>; Madhur Shukla @.> Subject: RE: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483) Hi Jeremy, We are trying to create the rule in Prod, however we see storage path doesn’t exist even after changing it to ServiceTags_Public_20220627.json. Coud you please check and provide us the updated storage link? @. Regards, Rahul Gattadi Consultant | Microsoft Services<EMAIL_ADDRESS>[A close up of a logo Description automatically generated] From: RAHUL GATTADI Sent: Friday, July 1, 2022 3:25 PM To: Azure/Azure-Sentinel<EMAIL_ADDRESS>Azure/Azure-Sentinel<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Sanchu Sankar<EMAIL_ADDRESS>Vinayak Latthe<EMAIL_ADDRESS>Benjamin Kovacevic<EMAIL_ADDRESS>Subject: RE: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483) Hi Jeremy, Thanks for the quick help, I have modified the same in KQL query in my test lab which worked 😊. Will reach you in case any help needed. Regards, Rahul Gattadi Consultant | Microsoft Services<EMAIL_ADDRESS>[A close up of a logo Description automatically generated] From: Jeremy Tan<EMAIL_ADDRESS>Sent: Friday, July 1, 2022 2:27 PM To: Azure/Azure-Sentinel<EMAIL_ADDRESS>Cc: RAHUL GATTADI<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/Azure-Sentinel] Failed to create alert rule Azure Portal Signin from another Azure Tenant (Issue #5483) Hi @Rahulg485https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRahulg485&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=dZkigewDgwl9QPvNZQhhFSoGXXgDp0y84H6obwykirM%3D&reserved=0, Looks like your file name is not valid anymore. The latest one should be ServiceTags_Public_20220627.json. Please try again with the updated URL (it worked on my end). Thanks — Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Sentinel%2Fissues%2F5483%23issuecomment-1172109504&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=GMdXbw%2F0fhe12rZ9eLHXyrBpBv4QmoB9tF9mPIKqQvg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZ2RNGUIQVPSZGMCWBYN3G3VR2XHRANCNFSM52BWDSDQ&data=05|01|rahulgattadi%40microsoft.com|eff4ef85c4be4e4a6c6108da5b3fb9be|72f988bf86f141af91ab2d7cd011db47|1|0|637922626545592449|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Vc0C%2FsyLzo402tX3Z96zJgGpgRmXGeAgKXeKKcDpWhs%3D&reserved=0. You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
@Rahulg485 this should be the updated one ServiceTags_Public_20220905.json
From this link: https://azservicetags.azurewebsites.net/


release notes for v12.8

lists bug fixes and changes to twb format for extensions.

Just going ahead and adding the release notes for v12.8.


Possible subscript typo for GATConv formula

I think there may be a small typo in the GATConv formula in the first term where I believe the x vector should refer to the features of the current node i, and j is not yet defined.

Yes, thank you :)


South Kirkby WRY

There is a duplicate entry for South Kirkby WRY. Please move all search records and remove the duplicate entry from the Gazetteer.
Geoff

Done


Allow to accept sync function forMaybe/andThenAsync

We close this once by https://github.com/option-t/option-t/issues/1683#issuecomment-1456004819.
We'll reopen this when we conclude about #1683.
If you have some opinions, please comment to #1683


In the tables for unpubublished data, does the study_tag need to be unique for all rows?

In the tables for unpublished data, e.g. UNPUBLISHED_STUDY and UNPUBLISHED_ANCESTRY, do the values for STUDY_TAG need to be unique in the table? In the submission form, my understanding is that the study_tag value needs to be unique in the submission form. Does this unique constraint also need to be added for these database tables? How does the code handle loading "unpublished data" with respect to using the study_tag as a key for the data?

The only constraint imposed by both UNPUBLISHED_STUDY and UNPUBLISHED_ANCESTRY on the STUDY_TAG field is Non-NULL. On import, the code checks for duplicates in the DB using the GCST - which makes sense, since if it's a Publication submission, the GCSTs exist by default and if it's a BoW submission, GCSTs are minted by the Deposition App.
/cc @twhetzel

Looks like the methods syncUnpublishedStudies, getSamples, and addSummaryStatsData use the study tag within the context of a submission or a publication so seems ok that the study tag does not have a unique constraint.
Closing


Unintentional termination of the complete program by a simple click.

Describe the bug
When I run the program code below, the program counts up from 0 to 99 every second and displays that respectively. If you "click" in the window or press a key during the count-up, the program terminates itself directly.
I'm not sure, if this a bug or a feature...?
To Reproduce
use std::time::Duration;
use cursive::view::Nameable;
use cursive::views::{Dialog, TextView};
use cursive::Cursive;
use std::{thread};

fn main() {
    let mut siv = cursive::default();
    siv.add_layer(
    	Dialog::around(TextView::new("Text 1"))
		.button("continue", display_text)
    	.with_name("text")
    	);
    siv.run();
}

fn display_text(siv: &mut Cursive) {
	let cb_sink = siv.cb_sink().clone();
	thread::spawn(move || {
		for number in 0..100 {
			cb_sink.send(Box::new(move |s| {
				s.call_on_name("text", |view: &mut Dialog| {
					view.clear_buttons();
					view.set_content(TextView::new(number.to_string()))
				});
			})).unwrap();
			thread::sleep(Duration::from_millis(1_000));
		}
	});
}

Expected behavior
The program does not exit automatically when clicked.
Environment

Operating system used: Gentoo Linux
Backend used: termion
Current locale: "de_DE.utf8"
Cursive version: crates.io, 0.16.3

Additional context
nothing

Hi, and thanks for the report!
Indeed, the Dialog focus was not properly updated after removing the buttons, leading to a panic. Should be fixed with the latest commit.
Thanks again!

Works. Thank you.


NPC Aggro lines are not hidden after recent update

Type
Incorrect behavior
Operating System
None
OS Version
N/A
Bug description
Ever since this commit the NPC Aggression Timer plugin doesn't hide when leaving an area.
This applies when the configuration is:

Always active: false
NPC Names: something defined
Hide when out of combat: false
Show on slayer task: false

What used to happen was when you entered an area that had a matching NPC name, the plugin appeared (lines and timer), then when you left the area then it disappeared/deactivated.
Now, once you enter an area that has a matching NPC name once in a session, the plugin is active forever as it never automatically turns off.
Screenshots or videos
No response
RuneLite version
RuneLite Version: 1.10.22
Logs
No response

This broke because the plugin uses the full npc scans to set active=false. I've reverted it in a45b983113d0c4932e42b2da53b296ee5a65f918. For good measure I tried to avoid some of the scanning in 020e8a200057d078839504ea523ada962110dad7 when it isn't necessary. Maybe it won't break again.


Review conformance to Go standard project layout

https://github.com/golang-standards/project-layout

We could start by creating (and using) a top-level pkg directory. There's one proposed entry in #631. What else might we include? I think the names package is a good candidate and also the top-level yaml package that's proposed in #629. Others?

We'll just want to be very careful about package structure, names, and contents as we'd be implicitly declaring that this shouldn't break - at least between major versions.


500 Error<EMAIL_ADDRESS>

The URL<EMAIL_ADDRESS>is returning a 500 error.

Hmmm... it wasn't in the cache for some reason and was failing to load.  Hitting the endpoint on my local machine took a while, but then generated that data.  It did feel like it took along time to load the module though.  🤷  Now going to the URL doesn't result in a 500.


Issue opening capture link

Hi,
Thanks for open sourcing this software.  It's actually hopefully answered a need for me right now while trying to diagnose some strange network issues with a microservice type app.
I've been able to run edgeshark and open the interface, both service containers are running and everything looks good in the interface.  Wireshark is installed and in $PATH.  NPCap latest is installed too.  This is on Windows 11.
The issue is when I click the the capture button, nothing happens.  I can see this link is:
packetflix:ws://localhost:5001/capture?......
Am I missing something?  Is there another step to compete before this works?
Thanks,
Joe

Hi @joseph-holland glad you find Edgeshark interesting and hopefully get you happy! Did you also install the separate Wireshark extcap? That's a little bit hidden, need to make that more clear in the quick start...
You can download it from https://github.com/siemens/cshargextcap/releases/tag/v0.9.1
As you're seemingly on Windows, please download the win amd64 zip. It contains an innately exe that you'll need to run to install the capture plugin.
After instalation, your browser should pick up the new handler for packetflix, at least chrome does so.  Clicking the fin button should then ask for confirmation.
Unfortunately, there doesn't seem to be a way to check in the Browser that the plugin is registered.

Hi @thediveo,
Yes that worked!
Many thanks,
Joe

linking here a similar question but on a Mac. There is no installer besides the wireshark plugin and I struggle to find how to register the custom URL handler https://github.com/siemens/cshargextcap/issues/14


[stable] macOS: Set Window appearance to fix missing white border

What does the pull request do?
On macOS Avalonia windows do not have a light border like other windows.
Sets the window's appearance on macOS to enable this light border.
This PR targets the stable branch as this should be handled better for 11.0 (see #9913)
Not 100% sure of the details of why/how this works. @danwalmsley could you share some details here?

This appears to not actually have fixed the issue, it just moved the issue from the dark theme to the light theme, so reverted on the stable branch.


Application removed from Google Play?

https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard

F-Droid link for the meantime: https://f-droid.org/en/packages/org.pocketworkstation.pckeyboard/

Of course, since 1's reading this on GitHub anyway, https://github.com/klausw/hackerskeyboard/releases

https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard

No luck there:
We're sorry, the requested URL was not found on this server.
Trying to install this keyboard on a new android device.

Hopefully there will be a solution soon.

I wonder what made the app removed from the store.

http://apps-me.store.aptoide.com/app/market/org.pocketworkstation.pckeyboard/1039003/22325340/Hacker's+Keyboard

I really would like to know why it was removed...
I mean, other than the name, it has nothing special, there are quite a few other keyboards with function keys & ctrl & alt & stuff, and you can use literally any bluetooth keyboard and get the same functionality...(though imo, hacker's keyboard is still the best of the "full keyboard functionality" keyboards)...

@klausw Any comments here?

The app got delisted due to allegedly violating the deceptive ads policy. I've asked for clarification since it's unclear to me why this would be the case, especially considering that the keyboard doesn't show any ads.

Thank you for the support, but I think a petition isn't likely to help at
this point. While I'm still not sure what the alleged violation is, I'm
suspecting that it is interpreting the "Get Dictionaries" button as an
undisclosed ad since it opens a Play Store search. I've appealed but
haven't heard back yet.

While I'm tempted to restyle the button with garish colors and borders to
make it look more ad-like, I suspect that this would then lead to a
requirement to mark the app as "contains ads". I'll see if my appeal is
successful, if not I'll look into adding an interstitial with explanations
and/or removing the Play Store link entirely.

Maybe reword as "Get Dictionaries (always free!)"?  Besides, don't most keyboards have downloadable dictionaries?   Even GBoard has them, as internal downloads, which I'd think are riskier than such from the Play Store.

Thank you for clarification, Klaus.  In the meantime, the workaround I've employed is to back up from one tablet, share to my google drive, and then sideload to new devices from there.  I'm also investigating building from source, which would be a good exercise as a step toward learning to program for Android.

Thanks!
Here's an idea for your Play Store "ads" issue, maybe just remove the links
to the dictionaries?
It's easy enough in the Play Store to select other apps by the same author,
so maybe you just mention that the dictionaries exist, in the description,
and mention that they can be downloaded separately.
On Wed, Oct 24, 2018 at 2:42 PM Klaus Weidner<EMAIL_ADDRESS>wrote:

@apgodshall https://github.com/apgodshall While I don't want to
discourage your building-from-source experience, you could also simply
download the APK from https://github.com/klausw/hackerskeyboard/releases
:-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/klausw/hackerskeyboard/issues/668#issuecomment-432833364,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMcDAkGhW6rF6wjE6bHYhAzqCa6HTqks5uoNp2gaJpZM4XTWny
.

--
Best Regards.
This is unedited.
This message came out of me
via a suboptimal keyboard.

It's easy enough in the Play Store to select other apps by the same author,

Not always true; it depends on the phase of Play Store design:  currently easy, previously impossible, previous to that reasonably ok, &c.  However, as mentioned, maybe just moving the link to the Play description would suffice?

Whew! I downloaded the English pack without looking at the logo properly. Thanks @xenotropic for the APK. @klausw , have not fear, you are still "the man".😄

Is there any connection between the removal of the app and the app crashing in kitkat 4.4.1?  Or is it a "Loose nut behind the screen" problem? Or do I need to open a issue?
Thanks...especially tthanks for the keyboard program!

I already read a lot of story in reddit about apps being banned eventhough there is  no ads in it. Thats what happen when they use robot to banned and filter all the apps.

@klausw this is a typical situation when it comes to "hacking" or "hackers". It could be just a coincident but I'm not surprised that the best "hackers" keyboard got taken down. It's a shame because it will definitely drive down the amount of people that will benefit from the keyboard. Most dont feel comfortable to download apk... But if there is anything we can do to help let us know and please update with any news from Gplay. Thanks man

Sorry about the delay. I did get human responses also, but they insisted that the "Get Dictionaries" button has to be changed. Unfortunately I can't just upload a minimal change to do this since there's a new rule requiring all updates to use target API level 26 (Android 8.0 / Oreo). The app is currently targeting API level 19 (Android 4.4 / Kit Kat), and I'll need to make sure that this change doesn't break anything.
The minimum API level is separate from the target API level and that's what determines if the APK is compatible with a given device. The current minimum API level is 8 (Android 2.2 / Froyo), but I may also need to change that in case of incompatibilities with the new target API level.

After many frustrating hours, I've gotten a build generated and uploaded to Play Store, and it's allegedly published. It may take a few hours to show up.
This involved a major source restructuring to make it Gradle compliant, and ditching the old Ant build files in favor of the new system. This isn't quite equivalent, for example I haven't integrated the auto versioning support yet for the debug info page, but overall seems to work including binary dictionary support via JNI.
Let me know if this works for you, it's only very lightly tested.

Fair warning, the minimum APK level is now 14 (Android 4.0 Ice Cream Sandwich), which apparently excludes 5.9% of the current install base. The original level 8 was incompatible with the default libraries I got via Android Studio / Gradle.

Thank you Klaus for all the hard work to get it back! We (your users) appreciate it very much!