K8SPXC-530 recovery part added

Test name
Status

haproxy
passed

upgrade-haproxy
failed

storage
failed

recreate
passed

scaling
passed

big-data
passed

init-deploy
failed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
failed

limits
failed

demand-backup
passed

scheduled-backup
failed

self-healing
passed

self-healing-advanced
failed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
failed

auto-tuning
failed

demand-backup-encrypted-with-tls
failed

operator-self-healing
failed

upgrade-proxysql
failed

proxysql-sidecar-res-limits
failed

smart-update
failed

users
failed

upgrade-consistency
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

storage
failed

haproxy
passed

scaling
passed

recreate
passed

upgrade-haproxy
failed

big-data
passed

init-deploy
failed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
failed

limits
failed

demand-backup
passed

self-healing
passed

scheduled-backup
failed

self-healing-advanced
failed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
failed

auto-tuning
failed

upgrade-proxysql
failed

operator-self-healing
failed

demand-backup-encrypted-with-tls
passed

proxysql-sidecar-res-limits
failed

smart-update
failed

users
failed

upgrade-consistency
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

storage
failed

big-data
passed

upgrade-haproxy
failed

scaling
passed

haproxy
passed

recreate
passed

init-deploy
failed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
failed

limits
failed

demand-backup
passed

scheduled-backup
failed

self-healing
passed

self-healing-advanced
failed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
failed

auto-tuning
failed

demand-backup-encrypted-with-tls
passed

operator-self-healing
failed

upgrade-proxysql
failed

smart-update
failed

proxysql-sidecar-res-limits
failed

upgrade-consistency
failed

users
failed

tls-issue-self
failed

tls-issue-cert-manager
failed

tls-issue-cert-manager-ref
failed

Test name
Status

scaling
passed

haproxy
passed

big-data
passed

storage
failed

upgrade-haproxy
failed

recreate
passed

scaling-proxysql
passed

init-deploy
failed

security-context
failed

limits
failed

restore-to-encrypted-cluster
passed

self-healing
passed

self-healing-advanced
failed

demand-backup
passed

scheduled-backup
failed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
failed

auto-tuning
failed

operator-self-healing
failed

upgrade-proxysql
failed

demand-backup-encrypted-with-tls
passed

proxysql-sidecar-res-limits
failed

smart-update
failed

users
failed

upgrade-consistency
failed

tls-issue-self
failed

Test name
Status

haproxy
passed

upgrade-haproxy
failed

recreate
passed

scaling
passed

big-data
passed

storage
passed

init-deploy
failed

scaling-proxysql
passed

self-healing
failed

restore-to-encrypted-cluster
passed

upgrade-proxysql
failed

security-context
failed

smart-update
passed

demand-backup
passed

limits
failed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
failed

monitoring-2-0
passed

scheduled-backup
passed

affinity
passed

upgrade-consistency
passed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
failed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

storage
passed

upgrade-haproxy
failed

haproxy
passed

recreate
passed

big-data
passed

scaling
passed

upgrade-proxysql
failed

init-deploy
failed

self-healing
failed

smart-update
failed

scaling-proxysql
passed

restore-to-encrypted-cluster
failed

upgrade-consistency
passed

security-context
failed

limits
failed

demand-backup
failed

self-healing-advanced
passed

monitoring
failed

operator-self-healing
failed

monitoring-2-0
failed

scheduled-backup
failed

affinity
passed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
failed

users
failed

tls-issue-self
failed

tls-issue-cert-manager
failed

Test name
Status

haproxy
passed

scaling
passed

big-data
passed

upgrade-haproxy
failed

recreate
passed

storage
passed

scaling-proxysql
passed

self-healing
failed

init-deploy
failed

upgrade-proxysql
failed

restore-to-encrypted-cluster
passed

security-context
failed

smart-update
passed

limits
failed

demand-backup
passed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
failed

monitoring-2-0
passed

affinity
passed

scheduled-backup
passed

one-pod
failed

auto-tuning
passed

upgrade-consistency
passed

proxysql-sidecar-res-limits
passed

users
failed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

big-data
passed

scaling
passed

upgrade-haproxy
failed

recreate
passed

haproxy
passed

storage
passed

init-deploy
failed

scaling-proxysql
passed

upgrade-proxysql
failed

restore-to-encrypted-cluster
passed

security-context
failed

self-healing
failed

limits
failed

smart-update
passed

demand-backup
passed

monitoring
passed

self-healing-advanced
passed

monitoring-2-0
passed

affinity
passed

operator-self-healing
failed

one-pod
failed

scheduled-backup
failed

auto-tuning
passed

upgrade-consistency
failed

proxysql-sidecar-res-limits
passed

users
failed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

haproxy
passed

recreate
passed

storage
passed

upgrade-haproxy
failed

big-data
passed

scaling
passed

init-deploy
failed

self-healing
failed

scaling-proxysql
passed

upgrade-proxysql
failed

restore-to-encrypted-cluster
failed

security-context
failed

limits
failed

smart-update
passed

demand-backup
failed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
failed

monitoring-2-0
passed

scheduled-backup
failed

affinity
passed

one-pod
failed

auto-tuning
passed

upgrade-consistency
passed

proxysql-sidecar-res-limits
passed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

big-data
passed

storage
passed

recreate
passed

haproxy
passed

upgrade-haproxy
failed

scaling
passed

init-deploy
failed

self-healing
failed

scaling-proxysql
passed

upgrade-proxysql
failed

restore-to-encrypted-cluster
failed

security-context
failed

smart-update
passed

limits
failed

demand-backup
failed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
failed

scheduled-backup
failed

monitoring-2-0
passed

affinity
passed

one-pod
failed

auto-tuning
passed

upgrade-consistency
passed

proxysql-sidecar-res-limits
passed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

big-data
passed

haproxy
passed

scaling
passed

recreate
passed

upgrade-haproxy
failed

self-healing
failed

init-deploy
failed

scaling-proxysql
passed

security-context
failed

restore-to-encrypted-cluster
failed

upgrade-proxysql
failed

limits
failed

smart-update
passed

demand-backup
failed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
failed

monitoring-2-0
passed

scheduled-backup
failed

affinity
passed

one-pod
failed

auto-tuning
passed

upgrade-consistency
passed

proxysql-sidecar-res-limits
passed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

haproxy
passed

recreate
passed

scaling
passed

big-data
passed

upgrade-haproxy
failed

self-healing
failed

init-deploy
failed

scaling-proxysql
passed

security-context
failed

upgrade-proxysql
failed

restore-to-encrypted-cluster
failed

limits
failed

smart-update
failed

demand-backup
failed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
failed

monitoring-2-0
passed

scheduled-backup
failed

affinity
passed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
failed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

haproxy
passed

storage
passed

scaling
passed

recreate
passed

big-data
passed

upgrade-haproxy
failed

init-deploy
failed

self-healing
failed

scaling-proxysql
passed

restore-to-encrypted-cluster
failed

upgrade-proxysql
failed

security-context
failed

limits
failed

smart-update
passed

demand-backup
failed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
failed

monitoring-2-0
passed

scheduled-backup
failed

affinity
passed

one-pod
failed

auto-tuning
passed

upgrade-consistency
passed

proxysql-sidecar-res-limits
passed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

scaling
passed

haproxy
passed

upgrade-haproxy
passed

storage
passed

big-data
passed

recreate
passed

init-deploy
failed

self-healing
passed

scaling-proxysql
passed

security-context
failed

restore-to-encrypted-cluster
failed

upgrade-proxysql
passed

self-healing-advanced
passed

limits
passed

smart-update
passed

operator-self-healing
passed

demand-backup
failed

monitoring
passed

monitoring-2-0
passed

affinity
passed

scheduled-backup
failed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
passed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

haproxy
passed

init-deploy
failed

recreate
passed

restore-to-encrypted-cluster
failed

upgrade-haproxy
passed

scaling
passed

storage
passed

scaling-proxysql
passed

self-healing
passed

security-context
failed

self-healing-advanced
passed

operator-self-healing
passed

big-data
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
failed

demand-backup
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
failed

scheduled-backup
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

haproxy
passed

recreate
passed

big-data
passed

upgrade-haproxy
passed

scaling
passed

self-healing
passed

init-deploy
failed

scaling-proxysql
passed

restore-to-encrypted-cluster
failed

security-context
failed

upgrade-proxysql
passed

limits
passed

monitoring
passed

smart-update
passed

demand-backup
failed

self-healing-advanced
passed

monitoring-2-0
passed

operator-self-healing
passed

affinity
passed

scheduled-backup
failed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
failed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

big-data
passed

scaling
passed

recreate
passed

haproxy
passed

upgrade-haproxy
passed

storage
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

security-context
failed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

monitoring
passed

demand-backup
passed

smart-update
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

scaling
passed

upgrade-haproxy
passed

big-data
passed

recreate
passed

storage
passed

haproxy
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

security-context
failed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

monitoring
passed

smart-update
passed

demand-backup
passed

operator-self-healing
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

haproxy
passed

storage
passed

upgrade-haproxy
passed

big-data
passed

scaling
passed

recreate
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
failed

upgrade-proxysql
passed

limits
passed

monitoring
passed

demand-backup
passed

self-healing-advanced
passed

smart-update
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

operator-self-healing
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

demand-backup-encrypted-with-tls
passed

validation-hook
passed

Test name
Status

scaling
passed

big-data
passed

storage
passed

haproxy
passed

recreate
passed

upgrade-haproxy
passed

self-healing
passed

init-deploy
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
failed

upgrade-proxysql
passed

limits
passed

monitoring
passed

demand-backup
passed

smart-update
passed

monitoring-2-0
passed

self-healing-advanced
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

demand-backup-encrypted-with-tls
passed

validation-hook
passed

Test name
Status

recreate
passed

haproxy
passed

big-data
passed

storage
passed

scaling
passed

upgrade-haproxy
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
failed

security-context
failed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

monitoring
passed

demand-backup
failed

smart-update
passed

operator-self-healing
passed

monitoring-2-0
passed

affinity
passed

one-pod
failed

scheduled-backup
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed


Fix: Remove duplicate font-awesome fonts

This PR

[x] removes duplicate fonts

💁♂ They are required in package.json, and running
$ yarn install
$ yarn run production

will install them the node_modules/, and then copy them to /web/assets/fonts/ (where they are still checked in, probably for those folks who cannot run either of these commands during deployment).
❓ Do we really want to check in build artefacts?

Thank you, @chartjes!


Is there anyway to sign different theme to different rss sources

Like if I am reading Japanese articles, I want my page to render in Japanese font. When I am reading Chinese articles, I want my page to render in Chinese font.
Is that possible?

Do you have the URL of a feed where that’s not true?

Chinese and Japanese both use Kanji (Japanese way to say 'Chinese character') in their writing system. But some of the same Kanji characters are having different ways to be written in the two writing system.
Like in Chinese. 天, meaning sky, have the upper line shorter than the lower line.(https://bkimg.cdn.bcebos.com/pic/bf096b63f6246b600c3307d744b20d4c510fd9f90477?x-bce-process=image/watermark,image_d2F0ZXIvYmFpa2UxMTY=,g_7,xp_5,yp_5)
In Japanese, 天，also meaning sky, have the upper line longger than the lower line. (https://www.google.com/url?sa=i&url=https%3A%2F%2Fkanji.jitenon.jp%2Fkanji%2F061.html&psig=AOvVaw0HbyTVTNG3OHOkoQ7R7tl1&ust=1669272099885000&source=images&cd=vfe&ved=0CBAQjRxqFwoTCMCSsqbZw_sCFQAAAAAdAAAAABAE)
But in the Unicode, 天 as A CJK(Chinese,Japanese,Koeran) character, is set as u5929. So if your system is set as Chinese-Simplified or Chinese-Traditional, u5929 will render in the Chinese way. If your system is set as Japanese, u5929 will render in the Japanese way. Same to a lot of CJK unicode character.
Back to the rss feed. If my system is set to Chinese, all of the CJK character, in default will be render in the Chinese way. No matter what languages the feed is in. So if i am reading a Japanese aritical, The characters will look very weird.
To slove this is very easy. Let feed in Chinese to render in Chinese way and Japanese feed to render in Japanese way. Here is where font kick in. If i can set a specific feed to a specific theme, i can set which font i want my feed to be showed in. So if the feed is in Chinese, i can just set a Chinese-font to the feed. If it's in Japanese, i can set a Japanese-font to the feed.
I hope my awful English can delivere the meaning that i want to say. Thank you for your time.

I understand. Good lesson! I didn’t know about this issue.
Would you reply with the URL of a Chinese feed and of a Japanese feed that you read? I’d like to be able to see if it’s possible to detect the language.

Chinese feed: https://www.ifanr.com/feed
Japanese feed: https://www.nhk.or.jp/rss/news/cat6.xml

It looks like RSParser is already handling the language element in various formats. It just looks like we overlooked persisting and using it in the ArticlesDatabase. We need to add it there and to the Article type. We can then substitute it into page.html as below which will correct the issue.
<html dir="auto" lang="ja-jp">

@Marvinjee The NHK link you provided doesn't supply the necessary language RSS element, so even after we fix this, that particular feed won't work any different for you.

Understand. Thank you very much.
From: Maurice Parker @.>
Date: Tuesday, November 29, 2022 at 10:53 AM
To: Ranchero-Software/NetNewsWire @.>
Cc: Marvinjee @.>, Mention @.>
Subject: Re: [Ranchero-Software/NetNewsWire] Is there anyway to sign different theme to different rss sources (Issue #3757)
It looks like RSParser is already handling the language element in various formats. It just looks like we overlooked persisting and using it in the ArticlesDatabase. We need to add it there and to the Article type. We can then substitute it into page.html as below which will correct the issue.

@Marvinjeehttps://github.com/Marvinjee The NHK link you provided doesn't supply the necessary language RSS element, so even after we fix this, that particular feed won't work any different for you.
—
Reply to this email directly, view it on GitHubhttps://github.com/Ranchero-Software/NetNewsWire/issues/3757#issuecomment-1330006520, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APLIWH7H5JRIOOPLHE2GK53WKVVZZANCNFSM6AAAAAASIPEY74.
You are receiving this because you were mentioned.Message ID: @.***>


Tip for README Episode 7

Hey Jeff. Thanks for all the awesome work! I'm a big fan.
I ran into a problem wiht the Dockerfile that was generated but the oprator-sdk that I thought you may want to mention for anyone following along.
The generated dockerfile references
FROM quay.io/operator-framework/ansible-operator:v1.4.1
but as at today, there is only 1.4.0 available here https://quay.io/repository/operator-framework/ansible-operator?tab=tags
The upshot is the make step will fail at the docker-build step complaining that the image wasn't found. A quick manual modification to that line to change it to 1.4.0 fixes the problem.
Hope you're getting at least a little sleep with the new baby!

Weird! I wonder if they pulled 1.4.1...

Not stale.


v1.10.2_w-o_sec_validation with security upgrades

Supersedes https://github.com/plotly/postgres-operator/pull/2 and #4
Part of https://github.com/plotly/dekn/issues/6666
This PR brings the upstream changes into our master branch.
In particular, we want to add commit https://github.com/plotly/postgres-operator/commit/409e4c78344f397d2c771129bcfb6968f84c1972 which fixes CVE-2023-44487! Unfortunately, this commit is not part of v1.10.1 release (the latest). I called this branch v1.10.2_w-o_sec_validation since it can be considered a patch release. We already have an image named v1.10.1_w-o_sec_validation which we should keep intact IMO.
To make this PR, I:

started a branch off the latest change from zalando:master to get 409e4c78344f397d2c771129bcfb6968f84c1972
cherry-picked @x3rus's modifications from https://github.com/plotly/postgres-operator/pull/3/commits/4e25ab88fb1f386cd1ed0c002f9ebc7c61494548

Finally, I pushed the image built from this branch to quay.io/plotly/postgres-operator:v1.10.2_w-o_sec_validation !

Hi @namgk , I think from my memory this image was built locally on my laptop.
We were in rush mode and I simply used the docker/Dockerfile.
Have a nice day all :wave:

@antoinerg how did you build the image?

I concur with @x3rus: I'm pretty sure we built this locally...

Have a nice day all 👋

To you too! I hope you're well @x3rus and thanks for replying :)


NETOBSERV-330 Provide a way to filter Kubernetes-related flows

Added Traffic Scope query options:

Infrastructure
Applications
Both

It uses regex (kube-|openshift-).* with matches / does not matches operators on both SrcNamespace and DstNamespace

what about traffic from infra to apps, or from apps to infra? I dont' know if it should be included in the "apps" traffic... thoughts? cc @stleerh @eranra
That being said, maybe it's not as easy as implement as it sounds, in logQL... not sure

I think anywhere that 'app' appears should be included as "apps" traffic.  Otherwise, you will miss the router -> app.

I think anywhere that 'app' appears should be included as "apps" traffic.  Otherwise, you will miss router -> app.

Exactly, we're missing ingress traffic coming to the application, that's the main issue with this approach I think

I think anywhere that 'app' appears should be included as "apps" traffic.  Otherwise, you will miss router -> app.

Ok I'm digging in that direction now and see a lot of noise coming from kubernetes API (default namespace).
Should we filter openshift related content that uses API ? It's a nonsense for me to see it here.

@stleerh @jotak @eranra I would suggest to add a configurable regex that match ingress namespace. Default value: .*-ingress$
With that we can force these to appear in the application view:

@stleerh @jotak @eranra I would suggest to add a configurable regex that match ingress namespace. Default value: .*-ingress$

Good idea :)

thanks @jpinsonneau
/lgtm

/approved


MegaMerge font display issue

I'm not font-savvy so if the answer to my question is glaring I do apologize.
When loading the fonts\\NotoSans\\full\\variable-ttf\\NotoSans[wdth,wght].ttf file I get the following:

However when I load the megamerge\\NotoSansLiving-Regular.ttf file I get this:

Important to note that I am loading both fonts the exact same way.
I saw that on the megamerge README, the following is stated

Vertical metrics are removed.

Is that what's causing the behavior showed above?
And if so is there I way to fix this?

fontTools.merger, used by the megamerge script, sets the vertical metrics of the output font to be the highest and deepest values of all the fonts used for merging. This is arguably the correct behaviour; if you set the vertical metrics to make the Latin part of Noto Sans Living look the same as Noto Sans LGC, it will create overlaps between lines when tall and deep characters are used.
So the way to fix this is to make the font size bigger. :-)

@simoncozens
That's interesting, because I am looking for a one-size fits all solution when it comes to fonts.
I want to let the user pick their language, without having to load and unload different files.
Do you believe it would be possible to detect, through mathematical formulas what the font size should be based on the character set being used?
Example let's say the english language was picked, would it be possible to calculate what the font size should be so that it looks correct (referencing the pictures on my post above)?

I don't know enough about what you're doing (browser? app? some kind of programming framework?) to give detailed advice, but you need to understand how your environment handles font vertical metrics. This article together with the links in the bibliography would be a good place to start learning. In CSS there is a font-size-adjust property which does what you are thinking of, but I would suggest understanding the vertical metrics problem in more depth before starting to fiddle.

@simoncozens
It's a c++ desktop application using ImGUI and rendered with DX12.
So web-related utilities aren't particularly accessible

Okay, I'm well out of my depth here. Consult your ImGUI manual for details of how it sizes fonts based on their vertical metrics.

@simoncozens
Alright, thank you for time, appreciate it.


CRDs to access CNPG from vCluster [Feature]:

Is there an existing issue already for this feature request/idea?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?
Currently, Postgres inside a vCluster is not able to talk to CNPG of the parent cluster and we get below error on deploying Postgres in such scenario:
resource mapping not found for name: "pgcluster" namespace: "pgcluster" from "pgcluster.yaml": no matches for kind "Cluster" in version "postgresql.cnpg.io/v1"
ensure CRDs are installed first

Therefore, this new feature will allow a Postgres in a vCluster to access CNPG on the parent cluster. Adding this feature will allow end-users to deploy only Postgres in the vCluster without having to deploy CNPG. It also saves extra workload for the whole cluster (parent and vCluster).
Describe the solution you'd like
I want CNPG be able to monitor and manage Postgres clusters inside vCluster(s) as it watches Postgres' in each namespace.
Describe alternatives you've considered
If this feature is not provided by CNPG, then sysadmins who wants to have above mentioned facility need to create their own CRDs which would be more difficult to maintain than creating - especially with each upgrade etc.
Additional context
In addition to this section above: "I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated", I have also posted this question on slacks, but haven't got any helpful answer.
Backport?
Yes
Are you willing to actively contribute to this feature?
No
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @retrogaming457
Isn't part of the whole idea here that the vCluster is completed isolated from the parent one?Therefore, there's any documentation about vCluster allowing this? because I wasn't able to find one.
Regards,


Feature Request: Adapt tray Icon to desktop theme

This is how the new tray icon currently looks like on a radiance themed Ubuntu desktop:

Hard to see isn't it? Would be great if the tray icon color could adapt to the desktop theme just like the dropbox icon does for instance.

Is that OS X or Linux? I know the Linux icon is white under i3.

It's Ubuntu. But this feature could be useful for OS X aswell.

@Chinney Thats cool. Looks like OS X in many ways.
The image for the OS X icon is dark because the default menu bar is white. The image for the Linux status bar is white because most Linux status bars are dark colors.
OS X dark mode icons appear to be handled internally because the TrayStore only handles loading the image.

There are two major Ubuntu themes: Radiance (light) and Ambiance (dark). For both themes there is an icon theme (mono-dark and mono-white) which not only alters the native tray icons but also the dropbox icon for instance.
Maybe you could give two alternative icons for linux users (since linux user love to customize)? Or just leave it to us to adjust the color of the tray icon by delivering the raw image as a separate file?
See that slack icon in my screenshot? I made it myself since slack comes with a light icon aswell.

@Chinney That's really cool. I use i3 so I could customize many parts of it if I wanted to. The images N1 uses are loaded into the asar archive for speed at launch time. I don't know of any current way to override images.

In slack the images are located in the app.asar.unpacked folder.

Hey guys, same wish here.
@Chinney I tried looking into the asar.unpacked folder but there's no icons there.
Found the source images at master/internal_packages/system-tray/assets/linux but these files do not exist on my Ubuntu machine.
Another way would be to override the icon with an icon theme, by dropping a svg file to the [icontheme]/22x22/panel dir. Works for basically any programm with a tray icon if you know how to name it properly. I tried creating one, naming it 'nylas', 'nylas-panel', 'nylas-n1', 'ic-systemtray-nylas@2x' but all with no effect.
@mbilker Could you tell us where the images are loaded from or what the nylas panel-icon name would be?

The images are loaded from inside the app.asar file which is not difficult
to modify, but not the most elegant process.
On Fri, Feb 12, 2016, 4:38 PM Felix Cornelius<EMAIL_ADDRESS>wrote:

Hey guys, same wish here.
@Chinney https://github.com/Chinney I tried looking into the
asar.unpacked folder but there's no icons there.
Found the source images at
master/internal_packages/system-tray/assets/linux
https://github.com/nylas/N1/tree/master/internal_packages/system-tray/assets/linux
but these files do not exist on my Ubuntu machine.
Another way would be to override the icon with an icon theme, by dropping
a svg file to the [icontheme]/22x22/panel dir. Works for basically any
programm with a tray icon if you know how to name it properly. I tried
creating one, naming it 'nylas', 'nylas-panel', 'nylas-n1',
'ic-systemtray-nylas@2x' but all with no effect.
@mbilker https://github.com/mbilker Could you tell us where the images
are loaded from or what the nylas panel-icon name would be?
—
Reply to this email directly or view it on GitHub
https://github.com/nylas/N1/issues/588#issuecomment-183497267.

May I ask how this issue got fixed? For myself, I can't see any tray icon anymore since the latest update.

@Chinney This issue is not fixed. This issue is for adapting the tray icon to the dark theme in OS X, which worked even in the latest update.

+1

+1

+1


目录结构调整

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

desc/bitmap/bitmap.go
100.00% <ø> (ø)

desc/set/set.go
100.00% <ø> (ø)

desc/slice/list.go
100.00% <ø> (ø)

desc/tire/tire.go
100.00% <ø> (ø)

desc/union_find/union_find.go
100.00% <ø> (ø)


Windows Compatibility - File Name Issue

Description
When attempting to check out the repository on Windows systems, the following error occurs:
error: invalid path 'python/streamlit-multipage-chat-azure-blob-feed/pages/9_Need_Help?.py'
fatal: unable to checkout working tree

Issue
Some files contains a question mark (?), which is a restricted character in Windows filesystems. Windows does not allow the following characters in file names:  \ / : * ? " < > |
Maybe do change this, to allow more local developers to use this sample repository. I usually work on a MacBook, but sometimes im forced to work on windows, so it is not a great experience for starters ;)

Good point, Streamlit uses the file name for displaying in the menu, and we'd developed these using WSL2 on Windows.
I'll see if there's a better way to handle that.

Now fixed, just removed the ? from the filenames.


Add Nicholas to aboutUs.md

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@626cdbb). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #30   +/-   ##
=========================================
  Coverage          ?   68.62%
  Complexity        ?      399
=========================================
  Files             ?       72
  Lines             ?     1294
  Branches          ?      133
=========================================
  Hits              ?      888
  Misses            ?      373
  Partials          ?       33

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Added AZU027 Synapse Workspace should have managed virtual network en…

Added AZU027 Synapse Workspace should have managed virtual network enabled, the default is disabled.

@owenrumney Somethings is not right. I perform a go build on the cmd\tfsec grab the exe and paste it in my example code folder. I run it and it passes when its a string.  I am stumped.
Check 1
[GEN003][WARNING] Block 'azurerm_synapse_workspace.example' includes a potentially sensitive attribute which is defined within the project.
C:\Users\jaiperez\Documents\VS Code\TFSEC\TestingTFSEC\main.tf:7
   4 |   location                             = azurerm_resource_group.example.location
   5 |   storage_data_lake_gen2_filesystem_id = azurerm_storage_data_lake_gen2_filesystem.example.id
   6 |   sql_administrator_login              = "sqladminuser"
   7 |   sql_administrator_login_password     = "H@Sh1CoR3!"
   8 |   managed_virtual_network_enabled      = "false"
   9 |   aad_admin {
  10 |     login     = "AzureAD Admin"

See https://tfsec.dev/docs/general/GEN003/ for more information.
times
disk i/o             999.6µs
parsing HCL          0s
evaluating values    0s
running checks       307.3µs
counts
files loaded         1
blocks               1
evaluated blocks     1
modules              0
module blocks        0
ignored checks       0
1 potential problems detected.

Well I'm pretty confused now - I've just pulled you branch onto a windows box to may sure it wasn't that I was missing something with OS.
Steps
1. gh pr checkout 710
2. git pull
3. go build cmd/tfsec
4. tfsec.exe example\710

In my example\710 folder I have a single file with the one resource from the bad example and it works fine
PS C:\Users\Owen\go\src\github.com\tfsec\tfsec> .\tfsec.exe .\example\710\

Check 1

  [AZU027][WARNING] Resource 'azurerm_synapse_workspace.bad_example' should have managed_virtual_network_enabled set to true, the default is false.
  C:\Users\Owen\go\src\github.com\tfsec\tfsec\example\710\main.tf:8

       5 |   storage_data_lake_gen2_filesystem_id = azurerm_storage_data_lake_gen2_filesystem.example.id
       6 |   sql_administrator_login              = "sqladminuser"
       7 |   sql_administrator_login_password     = "H@Sh1CoR3!"
       8 |   managed_virtual_network_enabled         = "false"
       9 |   aad_admin {
      10 |     login     = "AzureAD Admin"
      11 |     object_id = "00000000-0000-0000-0000-000000000000"

   See https://tfsec.dev/docs/azure/AZU027/ for more information.

Check 2

  [GEN003][WARNING] Block 'azurerm_synapse_workspace.bad_example' includes a potentially sensitive attribute which is defined within the project.
  C:\Users\Owen\go\src\github.com\tfsec\tfsec\example\710\main.tf:7

       4 |   location                             = azurerm_resource_group.example.location
       5 |   storage_data_lake_gen2_filesystem_id = azurerm_storage_data_lake_gen2_filesystem.example.id
       6 |   sql_administrator_login              = "sqladminuser"
       7 |   sql_administrator_login_password     = "H@Sh1CoR3!"
       8 |   managed_virtual_network_enabled         = "false"
       9 |   aad_admin {
      10 |     login     = "AzureAD Admin"

   See https://tfsec.dev/docs/general/GEN003/ for more information.

  times
  ------------------------------------------
  disk i/o             812.8µs
  parsing HCL          0s
  evaluating values    0s
  running checks       724.9µs

  counts
  ------------------------------------------
  files loaded              1
  blocks                      1
  evaluated blocks     1
  modules                   0
  module blocks        0
  ignored checks       0

2 potential problems detected.

@owenrumney I do not know what the issue was. I deleted my local repo copy redownloaded, made the change you suggested again and it worked flawlessly!
Summiting a new commit with the change now.

hey @jpmicrosoft , check in latest release 0.39.27


[AKS] added PATCH endpoint for updating tags

Adds the new AKS PATCH endpoint for updating tags to the swagger spec. This should resolve the final ARM violation in that API.
cc: @ifeoluwaokunoren @ravbhatnagar @vladimirjoanovic
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[X] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] The spec follows the guidelines described in the Swagger checklist document.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go


Name attributes on dev.sync and dev.port configurations

Is your feature request related to a problem?
Yes. Currently, when using profile patch paths to specify a dev.sync or dev.ports item to remove, only fragile array indexes can be used. Because there is no "root level" property on these items, robust property selectors cannot be used.
Example (with array indexes):
...
dev:
  ports:
  - labelSelector:
      service: web
    forward:
      - port: 3000
        remotePort: 3000
  sync:
    - labelSelector:
        service: web
      excludePaths: []
profiles:
  - name: disable-web
    patches:
      - op: remove
        path: dev.ports[0]
      - op: remove
        path: dev.ports[0]

Which solution do you suggest?
Adding a new property, like name to the dev.sync and dev.ports configuration. This would allow the above example to be expressed in a robust way:
...
dev:
  ports:
  - name: web
    labelSelector:
      service: web
    forward:
      - port: 3000
        remotePort: 3000
  sync:
    - name: web
      labelSelector:
        service: web
      excludePaths: []
profiles:
  - name: disable-web
    patches:
      - op: remove
        path: dev.ports.name=web
      - op: remove
        path: dev.ports.name=web

Which alternative solutions exist?
N/A
Additional context
We are using profiles more heavily to control dynamic configuration in our cloud development environments. The ability to safely and reliably combine multiple profiles will be important for us.

@noizwaves thanks for creating this issue! Yes that makes sense, this would also help with hooks (like after initial sync) where names can be used to select the specific sync or port forwarding configuration

works with v5.16.0


Release indexer verifier tool [phab:D426]

Created by schroederc at 2015-07-24 20:19:18:

zarko commented inline (context lost during migration) at 2015-07-24 20:35:09:
existent

zarko accepted this revision at 2015-07-24 20:35:09

schroederc wrote at 2015-07-27 15:45:16:
Typo

schroederc closed via commit 120449cd60158cfc72e381af592845a52b3e1966 at 2015-07-27 15:45:27


Allow custodian to filter on if certain strings are in userdata

I did some basic custodian schema searches but didn't find this.  Let me know if it is already there..

Like:
hardcoding passwords.   search for string "password".
pointing to company specific services they shouldn't (ex: wrong proxy, old artifact management system, etc.).  Search for a particular hostname
So I want to filter on a regex string I provide.  If it matches on the userdata, I want to take some action (notify, terminate, etc.)

its not currently. for large fleets i would have concern on doing it as a periodic vs a config rule, as it requires a per instance api call to retrieve user data.

agreed.  it could only be cloudtrail / event based.


Uniqueness check should only be skipped if the field is blank

Default behaviour for the uniqueness validator is to skip over a field if it is allowed to be blank or nil.  It should only skip those fields if they are also set to blank, otherwise uniqueness errors can occur.  Attached is a fix and an updated spec.

@dkubb Wondering if there's any specific reason if this was closed?  I'd be willing to fix any merge issues if you still would like the PR :)

@pnomolos it was probably closed because the release-1.2 branch was removed. I didn't intentionally set out to close this PR. If you want to reopen a PR against the master branch we can look at testing it and merging it in. One requirement is that the build continue to pass (or if it is failing, not for there to be a regression where more tests fail than before). We'll have all the builds passing shortly that aren't.
The main reason for the release-1.2 branch removal was simply because we wanted to get all dev being done against the master branch and not fragment development further.


Swagger : Problems in installing swagger and containers are in 'restarting' state

If you are reporting a problem, please make sure the following information are provided:
1)Version of docker engine and docker-compose
2)Config files of harbor, you can get them by packaging "Deploy/config" directory
3)Log files, you can get them by package the /var/log/harbor/
Environment

Docker Engine 1.12.1
Docker Compose 1.8.1
Python Version 2.7.5
CentOS 7.2
Harbor server 0.4.1 (http://<IP_ADDRESS>)
Swagger on <IP_ADDRESS>

Problem
Followed this guide to test swagger, had to do some tweaks (first three lines below) before docker-compose build, otherwise it was throwing errors for env files not found; like these  ERROR: Couldn't find env file: /root/harbor/Deploy/config/ui/env.
# cat templates/ui/env > config/ui/env
# mkdir config/db && cat templates/db/env > config/db/env
# cat templates/jobservice/env > config/jobservice/env
# docker-compose build
# docker-compose up -d

And, containers deploy_jobservice_1 and deploy_registry_1 keeps going in restarting state. Probably there is some issue(s) with the variables defined in env files.

Logs files are here
2016-10-06.tar.gz

Have you started up Harbor successfully before you enabled Swagger? It looks like you didn't run the ./prepare script.

Hello @hainingzhang Yes, my Harbor was running well for box88 (<IP_ADDRESS>) and I did ran the prepare-swagger.sh script.

Hi @vikas027  ,
What I meant was that you should install and run Harbor correctly first. From the logs, Harbor has not been correctly configured. Please read the below installation and configuration guide here first:
https://github.com/vmware/harbor/blob/master/docs/installation_guide.md
After you successfully install and run Harbor, you can then follow the Swagger configure guide to set up Harbor for Swagger.

@hainingzhang I already have a running Harbor on the other server http://<IP_ADDRESS> which I had installed through the tar ball harbor-offline-installer-0.4.1.tgz.  I can pull/push repos to/from it, thus I am assuming it is good.
I think Swagger and Harbor needs to be running at the same server. These are the complete steps which worked for me, hopefully will help someone else.
## For Harbor
root@box87:~# git clone https://github.com/vmware/harbor.git
root@box87:~# cd harbor/Deploy
root@box87:~/harbor/Deploy# sed -i 's/reg.mydomain.com/<IP_ADDRESS>/' harbor.cfg
root@box87:~/harbor/Deploy# ./prepare

## For Swagger
root@box87:~/harbor/Deploy# cd ../docs/
root@box87:~/harbor/docs# sed -i 's/reg.mydomain.com/<IP_ADDRESS>/' prepare-swagger.sh
root@box87:~/harbor/docs# ./prepare-swagger.sh

root@box87:~/harbor/docs# cd ../Deploy/
root@box87:~/harbor/Deploy# vi docker-compose.yml (added last two lines)
  ui:
    build:
      context: ../
      dockerfile: Deploy/ui/Dockerfile
    env_file:
      - ./config/ui/env
    restart: always
    volumes:
      - ./config/ui/app.conf:/etc/ui/app.conf
      - ./config/ui/private_key.pem:/etc/ui/private_key.pem
      - ../static/vendors/swagger-ui-2.1.4/dist:/go/bin/static/vendors/swagger
      - ../static/resources/yaml/swagger.yaml:/go/bin/static/resources/yaml/swagger.yaml

root@box87:~/harbor/Deploy# docker-compose build
root@box87:~/harbor/Deploy# docker-compose up -d

Now, Harbor is available at http://<IP_ADDRESS>
and Swagger is available at http://<IP_ADDRESS>/static/vendors/swagger/index.html

Thanks for the update.
Yes, Harbor and Swagger must run on the same server. We will update the document for this.


'maxBytesInMemory' tuningConfig introduced for ingestion tasks

Currently a config called 'maxRowsInMemory' is present which affects how much memory gets
used for indexing. If this value is not optimal for your JVM heap size, it could lead
to OutOfMemoryError sometimes. A lower value will lead to frequent persists which might
be bad for query performance and a higher value will limit number of persists but require
more jvm heap space and could lead to OOM.
'maxBytesInMemory' is an attempt to solve this problem. It limits the total number of bytes
kept in memory before persisting.

The default value is 1/6(Runtime.maxMemory())
To maintain the current behaviour set 'maxBytesInMemory' to -1
If both 'maxRowsInMemory' and 'maxBytesInMemory' are present, both of them
will be respected i.e. the first one to go above threshold will trigger persist

Thanks @surekhasaharan! I left some review comments.
One of them suggested changing the default maxRowsInMemory to 1000000 (the idea being we'll rely a lot more on maxBytesInMemory) although we can also discuss whether or not that is a good idea. There are some pros and cons. I guess the biggest con would be that there is potential for a well-tuned setup with the current scheme to be thrown out of whack somehow. But I think it's worth it if these defaults are better for the majority of cases.
Marked this "release notes" due to the potential change in behavior.

Tagged design review due to changing of defaults of important parameters like maxRowsInMemory.

I'll finish my review tomorrow.

Runtime.maxMemory

why it's 1/6 of  Runtime.maxMemory

Runtime.maxMemory

why it's 1/6 of Runtime.maxMemory

@jihoonson @gianm @surekhasaharan

@hellobabygogo there is a comment in the code about this here. Some more details, while analyzing the heap dump on OOMEs, we found that two OnheapIncrementalIndex instances roughly took 2/3 of retained heap, with each instance roughly taking 1/3 of heap. So we realized that our original default which was 1/3(jvm mem) may be too aggressive, since rows or bytes in memory trackers track only the active index, but not the one being flushed to disk. So the total used memory could be upto double of what is being tracked (as there's always one active index and potentially one being flushed to disk).


fix(nuxt): async transform for inline middleware

🔗 Linked issue
resolves https://github.com/nuxt/nuxt/issues/18459
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
We were not transforming inline middleware, meaning that the nuxt instance would be lost after an await.
We might also consider an option to add*Plugin to accept an options argument for unshift/push/etc.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

I think having options of unshift/push would be great!


Pangoro >Pangolin after registered, the Collateral Balance and quote didn't update.

Pangoro >Pangolin after getting registered, the Collateral Balance and quotes didn't update.

It looks fine

I tried it, and it will automatically update the data after registering


Switched client pop to mp3, closes #512

mp3 is more universally supported - see https://en.wikipedia.org/wiki/HTML5_Audio#Supported_audio_coding_formats

MP3 might be more supported, but it is also not an open format, and the restrictions apply to us. I am not 100% sure, but it might not be the case for AAC. While AAC codec developers require a patent, it is free to use (unlike MP3).
If this happens to not be true, it seems like OGG defaulting to WAV is our best option, granted it will not work for IE.

2 interesting links: http://www.html5gamedevs.com/topic/7095-best-audio-format-to-use-mp3-wav-or-ogg/ and https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats#Browser_compatibility

Is there really a benefit to shipping ogg and wav? Why not just use wav and save shipping an extra file?

Yeah I'm dum-dum. Let me rephrase: OGG with fallback to AAC if there are any licensing issues (it looks like there shouldn't be) for maximum compatibility, or only WAV otherwise and we acknowledge no support for IE.

OGG with fallback to AAC

That seems to be the way to go from looking at caniuse.com.


Intermittent build failures due to timing issues in cruise.statemachine.test.DoActivityTest

My effort to commit little changes to the server is unsuccessful. The following is an excerpt from the log. Hope this can  help fix the issue. On my machine, nothing fails but building via travis is always failing.
[junit] Running cruise.statemachine.test.DoActivityTest
[junit] Tests run: 8, Failures: 0, Errors: 1, Time elapsed: 36.854 sec

BUILD FAILED
/home/travis/build/umple/umple/build/build.testbed.xml:144: The following error occurred while executing this line:
/home/travis/build/umple/umple/build/build.testbed.xml:158: Tests failed

have you opened the QA page? It should tell you more. I have seen this test randomly fail in the past, however. WHen you say 'always failing', have you tried rerunning it? How about creating a pull request

I just ran Travis again ... it passed fine now. This is an intermittent (relatively rare). I already ignored a couple of similar cases See #757

This will be challenging to fix given that it seems to occur rarely, but more commonly when the CPU is heavily loaded. Try to load down your machine to reproduce.

This is happening about 1/6 of the time on travis. If somebody wants to try analysing it or maybe running it 100 times with some kind of logging to see if we can detect the cause, it would be helpful.

This issue is happening less often now. And it doesn't affect end-users, so I an downloading its priority a bit


Adding support for SOS SaveModule.

I am trying to create an open-source ClrMD extension which is the equivalent to the SOS !SaveModule command. I'd be happy to contribute the result either to this repo if there's interest, or publish it as a separate ClrMD Extensions project.
The problem is, while I've been able to write my own code that partially works (it gets this right for some DLLs, but fails on others), there are a lot of unknowns in terms of how !SaveModule works internally. Unfortunately, after looking through https://github.com/dotnet/coreclr/tree/master/src/ToolBox/SOS/Strike it appears the code for !SaveModule is not publicly available as per https://github.com/dotnet/coreclr/issues/8363 .
Is there any way to get access to the source code of !SaveModule, or a resource that explains how it works?

Cool. I'd be very interested in that feature. Would make a perfect addition to https://github.com/Dynatrace/superdump.

Hi Omer,
!savemodule has nothing to do with .NET, it is related to debug api.
I implemented it here:
https://github.com/rodneyviana/netext/blob/master/ClrMemDiagExt/Module.cs
Search for:
public bool SaveToStream(Stream ModuleStream)
Thanks,
Rodney
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Omer<EMAIL_ADDRESS>Sent: Tuesday, February 27, 2018 8:13 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Subject: [Microsoft/clrmd] Adding support for SOS SaveModule. (#95)
I am trying to create an open-source ClrMD extension which is the equivalent to the SOS !SaveModule command. I'd be happy to contribute the result either to this repo if there's interest, or publish it as a separate ClrMD Extensions project.
The problem is, while I've been able to write my own code that partially works (it gets this right for some DLLs, but fails on others), there are a lot of unknowns in terms of how !SaveModule works internally. Unfortunately, after looking through https://github.com/dotnet/coreclr/tree/master/src/ToolBox/SOS/Strike it appears the code for !SaveModule is not publicly available as per dotnet/coreclr#8363https://github.com/dotnet/coreclr/issues/8363 .
Is there any way to get access to the source code of !SaveModule, or a resource that explains how it works?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/clrmd/issues/95, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKVY1aKU3Doa_EA5LDn27_eT9D9wd6Dqks5tZA2fgaJpZM4SU_5h.

Hi @lasherer,
Did you test your code with ngend modules?
I ask because I also wrote code that do the same but it not completely work for ngend modules (mscorlib.ni.dll for example). My exported assembly looks similar but not same as the required.

It copies and rebases PE directories. It is equivalent to sos/psscorX !savemodule.
It is easy for you to test, download the extension and use:
!wmodule /name mscorlib* /saveto c:\modules
And compare to sos output.
Sent from my mobile phone
On Mar 1, 2018, at 11:57 AM, Dudi Keleti <notifications<EMAIL_ADDRESS>wrote:
Hi @lashererhttps://github.com/lasherer,
Did you test your code with ngend modules?
I ask because I also wrote code that do the same but it not completely work for ngend modules (mscorlib.ni.dll for example). My exported assembly looks similar but not same as the required.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/clrmd/issues/95#issuecomment-369675744, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKVY1T49sz5-ObY0ixE0PFA6moNqIcFSks5taDZ1gaJpZM4SU_5h.

I'll try it after weekend and I'll update you. Thanks.

I fixed a bug in save module to adjust the RVAs for memory stream only images (like generated serialization assemblies) not mapped to disk. Also adjusted issues with CLR headers
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Rodney Viana<EMAIL_ADDRESS>Sent: Thursday, March 1, 2018 11:31:45 PM
To: Microsoft/clrmd
Cc: Microsoft/clrmd; Mention
Subject: Re: [Microsoft/clrmd] Adding support for SOS SaveModule. (#95)
It copies and rebases PE directories. It is equivalent to sos/psscorX !savemodule.
It is easy for you to test, download the extension and use:
!wmodule /name mscorlib* /saveto c:\modules
And compare to sos output.
Sent from my mobile phone
On Mar 1, 2018, at 11:57 AM, Dudi Keleti <notifications<EMAIL_ADDRESS>wrote:
Hi @lashererhttps://github.com/lasherer,
Did you test your code with ngend modules?
I ask because I also wrote code that do the same but it not completely work for ngend modules (mscorlib.ni.dll for example). My exported assembly looks similar but not same as the required.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/clrmd/issues/95#issuecomment-369675744, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKVY1T49sz5-ObY0ixE0PFA6moNqIcFSks5taDZ1gaJpZM4SU_5h.


Incorrect input shape when reading .png files

Using run_vision_chat.sh with a .PNG image results in
jax.errors.SimplifiedTraceback: For simplicity, JAX has removed its internal frames from the traceback of the following exception. Set JAX_TRACEBACK_FILTERING=off to include these.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/ubuntu/miniconda3/envs/lwm/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/ubuntu/miniconda3/envs/lwm/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/mnt/vol_f/LWM/lwm/vision_chat.py", line 254, in <module>
    run(main)
  File "/home/ubuntu/miniconda3/envs/lwm/lib/python3.10/site-packages/absl/app.py", line 308, in run
    _run_main(main, args)
  File "/home/ubuntu/miniconda3/envs/lwm/lib/python3.10/site-packages/absl/app.py", line 254, in _run_main
    sys.exit(main(argv))
  File "/mnt/vol_f/LWM/lwm/vision_chat.py", line 250, in main
    output = sampler(prompts, FLAGS.max_n_frames)[0]
  File "/mnt/vol_f/LWM/lwm/vision_chat.py", line 228, in __call__
    batch = self.construct_input(prompts, max_n_frames)
  File "/mnt/vol_f/LWM/lwm/vision_chat.py", line 123, in construct_input
    vision = self._read_process_vision(prompt['input_path'], max_n_frames)
  File "/mnt/vol_f/LWM/lwm/vision_chat.py", line 102, in _read_process_vision
    enc = jax.device_get(self.vqgan.encode(v))[1].astype(int)
  File "/mnt/vol_f/LWM/lwm/vqgan.py", line 53, in encode
    return self._encode(pixel_values)
  File "/mnt/vol_f/LWM/lwm/vqgan.py", line 35, in fn
    return self.model.apply(
  File "/mnt/vol_f/LWM/lwm/vqgan.py", line 122, in encode
    hidden_states = self.encoder(pixel_values)
  File "/mnt/vol_f/LWM/lwm/vqgan.py", line 155, in __call__
    hidden_states = nn.Conv(self.config.hidden_channels, [3, 3])(pixel_values)
  File "/home/ubuntu/miniconda3/envs/lwm/lib/python3.10/site-packages/flax/linen/linear.py", line 429, in __call__
    kernel = self.param('kernel', self.kernel_init, kernel_shape,
flax.errors.ScopeParamShapeError: Initializer expected to generate shape (3, 3, 3, 128) but got shape (3, 3, 4, 128) instead for parameter "kernel" in "/encoder/Conv_0". (https://flax.readthedocs.io/en/latest/api_reference/flax.errors.html#flax.errors.ScopeParamShapeError)

when number of channels in the input is > 3 (if transparency is present).

Thanks!


zstrs don't pad in format!()

Adding padding to a fmt definition doesn't lead to a zstr being padded, as happens for str. The relevant code for str is:
#[stable(feature = "rust1", since = "1.0.0")]
impl Display for str {
    fn fmt(&self, f: &mut Formatter<'_>) -> Result {
        f.pad(self)
    }
}

so I guess this could probably be resolved by changing
https://github.com/chuckcscccl/fixedstr/blob/45e84432ded726c9dd019bc862c7508d3bab2d83/src/zero_terminated.rs#L611
to:
  f.pad(self.to_str())

Change has been made in version 0.5.4 to zstr (and other types)


Telescope doesn't show preview for diff_commit_file

Hello. Thanks for this plugin! :heart:
I'm running
:Telescope advanced_git_search diff_commit_file

However, getting
fatal: path 'app-config/nvim/lua/plugins.lua' exists, but not 'lua/plugins.lua'

in telescope's preview on the file.
Screenshot:

Also, when I select a commit and hit "enter", it opens an empty buffer

Thanks for reporting this bug!
I could reproduce the issue by opening neovim in a subdirectory of a git repo. The expanded paths are not computed correctly with respect to the root of the git repo, so the git command fails.
I'll open a PR as soon as possible to fix the issue.
In the meantime, a temporary solution is to open nvim at the root of your git repository, this should resolve the problem.


No remotes match the current setting.

Extension version: 0.15.0
VSCode Version: 1.44
OS: Mac OSX 10.15.3
Git: version 2.23.0

Steps to Reproduce:

Install VS Code, point to github (I'm using GH Enterprise)
Install vscode-pull-request
Go to Extension icon on the left-hand side.
Observe the message 'No remotes match the current setting.'

What should happen:

Should see github auth attempt.

With output:
[Debug 276269s 78ms] No remote with name 'origin' found. Please update your 'githubPullRequests.remotes' setting.
[Debug 276269s 78ms] PullRequestManager> Displaying configured remotes: origin
[Debug 276269s 81ms] No GitHub remotes found

Even though I get from the project directory:
git remote -v
origin	git@github.<my-corp>:<MyCorp>/<my-project>.git (fetch)
origin	git@github.<my-corp>:<MyCorp>/<my-project>.git (push)

And that's it. No auth popup. Nothing. No matter what I tried.

I'm experiencing a similar error, but only one some repositories, and I'm not on enterprise.

Same issue, GH enterprise.
OS: Mac OSX 10.15.5

Same

Just installed in VSCode. No auth attempt, can't sign in anywhere. Just says "no remotes match current settings". MacOS Catalina 10.15.5

I gather this extension doesn’t work with github enterprise.
On Wed, Jul 29, 2020 at 6:33 PM Matt Healy<EMAIL_ADDRESS>wrote:

Just installed in VSCode. No auth attempt, can't sign in anywhere. Just
says "no remotes match current settings". MacOS Catalina 10.15.5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-pull-request-github/issues/1618#issuecomment-665964972,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABL523LE673DZM3ZKVYVBCDR6CPVFANCNFSM4MHJ62UA
.

--
Josh Guptill
317-506-3507

Same issue, non-enterprise.

I've identified https://github.com/microsoft/vscode-pull-request-github/issues/1656 as a possible cause

I think the issue is the Github Pull Request does not work with SSH remotes.

Agreed, but would think that all Github repositories are on SSH

If you change your remote to point to the HTTPS tag then it should work instantly

What does that mean?
How do you "change your remote to point to the HTTPS tag"?
You mean try and change remote to HTTP?

(Although this is quite a fail that you cannot use the SSH version which is sad)
Agree!

https://github.com/microsoft/vscode-pull-request-github/issues/1656#issuecomment-689207926

Is there a limit for Github Enterprise which is supported? Our organisation is hosting quite an old onprem version, and I'm encountering this issue.

We have discontinued support for GitHub Enterprise. https://github.com/microsoft/vscode-pull-request-github/wiki#2-is-github-enterprise-supported

We have discontinued support for GitHub Enterprise. https://github.com/microsoft/vscode-pull-request-github/wiki#2-is-github-enterprise-supported

That's very short sighted in my opinion with the large growing adoption of git within enterprise customers, why was this done?

We have discontinued support for GitHub Enterprise. https://github.com/microsoft/vscode-pull-request-github/wiki#2-is-github-enterprise-supported

That's very short sighted in my opinion with the large growing adoption of git within enterprise customers, why was this done?


Sending openssl connect request to same web server from two different clients using the session ticket generated from a client

I am using the openssl below command to generate and store the session ticket:
openssl s_client -sess_out cdn77_out -connect cdn77.com:443  -tls1_3 -servername www.cdn77.com
openssl s_client -sess_in cdn77_out -sess_out cdn77_out1 -connect cdn77.com:443  -tls1_3 -servername www.cdn77.com
i am transfering the session ticket i got from the above command to a different client and expecuting the below command:
openssl s_client -sess_in cdn77_out -sess_out cdn77_out1 -connect cdn77.com:443  -tls1_3 -servername www.cdn77.com
Connection is going as Reused. My expectation is it should be a new connection because it is a different client with different ip.
Please let me know if i am missing something.

There is no such requirement. You could have for example changed your dynamic IP address due to network disconnection/reconnection. There is no point in disallowing it. By using the sess_in/sess_out you are making the second client to act fully as the first client just with the IP address changed.


A copy of the main camera from the 3D scene needs to be prefabbed into the main UnityStarterProject folder

Preferably the camera in that scene should stay a child of the anchor's prefab


how to run the agent?

It'd be nice to have the Agent registered as a service and enabled for centos 7.
I also added couple lines to make it more usable (centos 6)
FROM centos:6
MAINTAINER Kevin He<EMAIL_ADDRESS>ENV AGENT_VERSION "01.00.11"
ENV ORG_NAME "partneretics"
RUN curl --silent -O "https://$ORG_NAME-admin.okta.com/static/agents/ProvisioningAgent/OktaProvisioningAgent-$AGENT_VERSION.x86_64.rpm"
RUN yum localinstall -y "OktaProvisioningAgent-$AGENT_VERSION.x86_64.rpm";
rm "OktaProvisioningAgent-$AGENT_VERSION.x86_64.rpm"
RUN chkconfig OktaProvisioningAgent on
RUN echo "https://$ORG_NAME.okta.com" | /opt/OktaProvisioningAgent/configure_agent.sh`

I suggest creating the docker image after the OPP configuration is performed and use it. In this case, we will will avoid manual steps required after promoting, but required different image for each container we promote.


Add New Mexico Junior College scraper

http://www.nmjc.edu/academics/courseschedule.aspx
Fairly straightforward.  Scraper takes a long time to download files and uses up a lot of computer resources processing requests, but seems to be functioning as intended.

@HarrisonGregg I changed the behavior of extract_links around to fix the anchor issue, and used your trick to simplify things.


Passed Element to mpl ElementPlot._finalize_axis

In debugging another issue I found that matplotlib plots are not correctly handling DynamicMaps of overlays as ElementPlots are not passing the currently displayed Element to the _finalize_axis method. This means that the method does an additional lookup which fails when the data comes from a DynamicMap returning Overlays.

Is this PR ready to review/merge?

Yes, ready.

Looks good and the tests are passing. Merging.


Custom polling error handler

It is not immediately obvious what should happen when an exception is thrown during polling of the database. Currently we retry when encountering an SQLTransientException, and we stop the Queue Worker in all other cases.
This makes sense when the Queue Worker is run as the only process in the JVM, that is, the lifecycle of the Queue Worker is identical with that of the JVM. Then, when an error is encountered, the process will exit and can be restarted by the relevant supervisor mechanism. This is a simple and well understood operational model.
But when the Queue Worker is but one of several processes in a JVM, we should have more control over what happens when polling errors occur. Maybe the error is transient (a DB restart, network problems etc.). In these cases we should ignore (but log!) the error, so that the poller might retry and recover when the error condition is no longer present.

Released in https://github.com/msolli/proletarian/releases/tag/v1.0.68-alpha


Addition of JSON Dump for consumption as an API

Interesting addition! I've been using the pyVesync tool to pull data and dump it into a JSON format, which I then push into InfluxDB(using Telegraf) and display in Grafana. This addition could make my script a bit easier, because I wouldn't need to do the JSON translation myself.
I'd suggest removing the kwh/watts/minutes/etc text from the data output. For power and voltage, just output a number. This will make it easier for external systems to make use of the data.
Thanks for all the updates to this awesome tool!

Good idea @jlboygenius - I was on the fence about this, but if it's more than just me using this functionality, happy to oblige 👍


Not getting type errors on missing operators that are used in code

RxJS version:
5.2
Code to reproduce:
Expected behavior:
To get type errors on missing operator
Actual behavior:
No type errors
Additional information:
I'm using Typescript and VS Code and I'm importing the Observable class just as usual:
import { Observable } from 'rxjs/Observable';
And then later I'm trying to use the filter function on an observable:
someObservable$.filter(...)
This fails at runtime as expected with:
TypeError: someObservable$.filter is not a function
This is sad. Do I really have to find this out at runtime? Can't I get the type checker to figure this out for me at write time?

You should import operators as well as you imported bare observable only. Please refer readme.

Yes. I am aware of that. I take no issue with that. This isn't about that.
I am hoping to get type errors if I forget to do that. Is that not intended?

There is no way to achieve those as it's behavior of typescript compiler and language service when type is augumented.

Inside filter.d.ts that is imported by doing import 'rxjs/add/operator/filter'; we see:
import { filter } from '../../operator/filter';
declare module '../../Observable' {
    interface Observable<T> {
        filter: typeof filter;
    }
}

Isn't this where filter is added to the Observable class? So why does my VS Code and my Typescript compiler already think that filter exists on Observable before I import the filter operator?
Because I am getting type completion of filter on Observable inside VS Code, without importing the filter operator. How do VS Code and Typescript know anything about there being a filter method on Observable without me importing it first?

yes, that's type of operator and important thing is it is augumented so type is added only if you already imported it. what you asked in original issue is check type prior to augument its type into compiler which is not possible cause at the moment it is not augumented there's no information to infer.
the way vs code works cannot be compared to compiler 1:1, cause it's language service does aggresive infer under all node modules. for example, it even provides type intellisense when you write javascript code. that's not compiler only job, vs code does its own.

So you're saying that even if I explicitly type import { Observable } from 'rxjs/Observable';, which imports the Observable type without the filter operator, that VS Code will still use the full Observable with the filter operator on it when doing intellisense?

While I can only guess it, I can't confirm internals of its behavior. I'd suggest take this issue to TS/VS code for its details, as this isn't Rx side questionsm

Its a little more nuanced than what's been said.
My guess is that you have a library that depends on rxjs, but has its own
instance of rxjs. Ie it depends on 5.0 and you depends on 5.1. in the node
world this causes two instances of rxjs to be loaded. Once with filter and
one without.
There isn't anything the typescript compiler can solve on its own as it
only knows enough. This is why angular marks rxjs as a peer dependency.
On Thu, Jun 29, 2017 at 9:57 AM OJ Kwon<EMAIL_ADDRESS>wrote:

While I can only guess it, I can't confirm internals of its behavior. I'd
suggest take this issue to TS/VS code for its details, as this isn't Rx
side questionsm
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ReactiveX/rxjs/issues/2710#issuecomment-311974501,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNdpY05p3lbe41iEqatxyrbzR4CCRaSks5sI61WgaJpZM4OJRKC
.

--
Thanks,
David

@david-driscoll so you are saying that I should in fact be seeing a type checking error when using someObservable$.filter without having done import 'rxjs/add/operator/filter'; before hand? But you are speculating that the reason I am not is because there might be some other rxjs package imported from somewhere else?
I am only seeing one version of rxjs in my node_modules folder. And I have grep'ed my whole project for both 'rxjs' and 'rxjs/Rx', and removed all instaces of those, so I can't see where this complete package of rxjs is coming from.

So I decided to be thorough and do my due diligence and test this properly myself, so I tried making a brand new folder with just these two files:
package.json
{
  "dependencies": {
    "rxjs":"5.4.2"
  }
}

index.ts
import 'rxjs/add/operator/filter';
import 'rxjs/add/observable/of';
import { Observable } from 'rxjs/Observable';

let test$ = Observable.of('banana');
test$.filter((val) => typeof val === 'string');

Then ran yarn and voila. This simple project did in fact limit the type of Observable to only have of and filter on it. VS Code intellisense gives no other options. And the compiler complains if I try to use anything else.
So I there must be something borked in my main project. Something somewhere must be importing 'rxjs' or 'rxjs/Rx' right? Some dependency, because I can find this in my own files.

Yeah, there is something, either a file in the project, or a dependency that is importing all the extra operators.

Awesome. I found the culprit in my node_modules. We had a package that imported 'rxjs', that was being required into our node_modules by another package, but that wasn't being included in our actual webpack bundle output, and I guess that VS Code then still used that typing for all files. I got proper limited rxjs type imports for the whole project, when I made that import a limited one.
Thanks for the great help guys :)

We have also encountered these runtime errors (TypeError: ...debounceTime is not a function) after upgrading from rxjs 5.4.2 to 5.5.1 last week.
Given the static analysis considers the Observable type on a per-app basis, I am no longer convinced the advice to import rxjs piecemeal on a per-file basis is good advice.
One alternative would be simply to bring the whole thing in.  Rx.min.js is 146KB but zips down to 31KB and a well configured web-server would perform similar compression.
It might be preferable to create a module containing just the bits of rxjs that the app as a whole uses then only ever import rxjs via that module.  Then Observable would always refer to exactly the same type, thus no harm should come of TypeScript's static analysis interpreting what an Observable is in the broadest sense it is ever used.
However:

I have no idea how to actually create such a module (Angular is good for modularizing stuff, so I'll mention we're using 4.4.6)
Other people probably have different ideas on what constitutes best practice for importing rxjs in TypeScript?

Apparently, yes it is possible to avoid the risk of encountering these runtime errors without having to import the whole of rxjs.
https://christianliebel.com/2017/07/import-rxjs-correctly/

@Antony74 I think that method of doing imports is already out of date, as the new rxjs version 5.5 introduced lettable versions of all operators, which should make rxjs imports work better: https://github.com/ReactiveX/rxjs/blob/master/doc/lettable-operators.md

@samal84 Thanks.  Yes I agree - at the point of 5.5 adoption, putting all the imports in once place becomes a question of taste rather than necessity.


[infra-proxy-read-only] fixed the console error on cookbook details content tab

Signed-off-by: Vinay Sharma<EMAIL_ADDRESS>:nut_and_bolt: Description: What code changed, and why?
While click on content tab getting console error

:chains: Related Resources
https://github.com/chef/automate/issues/4631
:+1: Definition of Done
I have added changes to fix the console error for the cookbook details content tab.
:athletic_shoe: How to Build and Test the Change
if you have sample data for the infra servers than
go to >> infrastructure tab >> click on Chef server on left side navigation bar >> click to any server where you can see the list of orgs >> click to any of org >> where you can see the multiple tabs (the first tab is cookbooks) >> see the list of cookbooks >> click to any of cookbook >> you can see the 2 tabs content tab and details tab >> click to the content tab and open the browser console.

@vinay033 What is the error that appeared before the fix?
Please change your instructions in the PR preamble so that it is not all on one really, really long line.
Thanks!

@vinay033 What is the error that appeared before the fix?
Please change your instructions in the PR preamble so that it is not all on one really, really long line.
Thanks!

@msorens
please check the attached screenshot.

@msorens
please check the attached screenshot.


D455 - Dynamic Calibration cannot be finished/Inaccurate deprojection values

Required Info

Camera Model
D455

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10 / Linux (Ubuntu18)

Platform
PC/NVIDIA Jetson

SDK Version
2.48.0

Language
python/opencv/unity

Segment
AR

Issue Description
Hello, I have an issue with one of my D455 modules. I use 3 cameras to retrieve 3D position of a point in space. All of them use same python script on Jetson XAVIER NX module. I use rs.rs2_deproject_pixel_to_point function to get its 3D position. That data afterwards is being sent to different world coordinate system to visualize object translation. 2 of my cameras are working fine, I do not see any major deprojection or depth error, although one of them started to giving me bad results, with exponentially growing error on object movement. First thing I did was checking all of my cameras with Depth Quality Tool, but I did not see any big difference of RMS error between any of them. Next thing I tried was to run them all through Dynamic Calibrator tool. 2 cameras which are working fine were able to go through the calibration process fairly quickly and without any hassle, but the one which seems to have a defect could not finish the calibration. It is the moment where you have to fit marker (displayed on my mobile) within blue square regions. Every time I am about to finish the calibration process, new blue regions appear in different places. It goes on and on forever making the calibration impossible to finish and raising timeout exception.
I would highly appreciate any feedback.
Also, I am wondering if there is a way to detect these kind of anomalies outside of Dynamic Calibrator tool? Thank you in advance.

Hi @powellsky  Could you try resetting the affected camera to its factory-new default calibration in the RealSense Viewer using a procedure at https://github.com/IntelRealSense/librealsense/issues/10182#issuecomment-1019854487 please?  Thanks!

Hi @powellsky Could you try resetting the affected camera to its factory-new default calibration in the RealSense Viewer using a procedure at #10182 (comment) to see whether it corrects the problem, please? Thanks!
Instead of using the Dynamic Calibration tool, you can also re-calibrate depth and receive a 'health check score' feedback for the camera's calibration using the On-Chip Calibration tool that is built into the RealSense Viewer. It can be found under the More option of the RealSense Viewer.

Full details of the On-Chip calibration tool can be found in Intel's white-paper guide at the link below.
https://dev.intelrealsense.com/docs/self-calibration-for-depth-cameras

Thank you, it worked! I have managed to finish calibration procedure after following your steps. Also, self-calibration routine is exactly what I needed for my program, and On-Chip Calibration seems a better and less tedious alternative to Dynamic Calibrator.
Sorry for duplicating an issue.

That's great to hear, @powellsky - thanks very much for the update!  Don't worry about duplication, as the librealsense forums have such a large history that it is natural that an existing solution may be missed.

@MartyG-RealSense Again thank you for solving the issue regarding calibration. However, I mentioned how originally my issue occurred, which was noticing exponential error on depth value for tracked object. To be sure, I re-calibrated all of my cameras, and suddenly I experienced similar behavior on all of them (it could be complete coincidence to be honest that this happened after calibration, and issue may be lying somewhere else). I had to make sure that RS Viewer gives me same results as the software we wrote and results were identical, plus I did some manual measurements to confirm it. The measurements are:
~57cm to target in reality is ~57cm to target in Software (After 60cm, measurements are getting worse)
~70cm to target in reality is ~72cm to target in Software
~86cm to target in reality is ~91cm to target in Software
I would highly appreciate any help in the matter. If you need anything regarding to the software we wrote, I am happy to provide with more details.

There are a range of lighting and environmental factors in a scene that can have a negative impact on depth measurement accuracy.  Would it be possible to provide an RGB image of the scene that the camera is observing in order to identify possible elements that may be causing disruption please?

There are a range of lighting and environmental factors in a scene that can have a negative impact on depth measurement accuracy. Would it be possible to provide an RGB image of the scene that the camera is observing in order to identify possible elements that may be causing disruption please?
Having said that, if you are obtaining correct measurement at 60 cm then the issue is likely to be related to the observed object / surface rather than the wider environment and lighting around it. The RGB image will help to identify that.

Of course. Here is RBG preview of what camera is seeing

:
To be more specific, I will also attach preview of how depth and infrared are seen. During our detection, we do not use RGB camera, only Infrared, and the only depth position we measure is center of IR diodes:

Thanks very much for the images.  It looks as though your D455's IR emitter is disabled.  If the emitter was enabled then there would be a semi-random pattern of dots projected onto the scene and visible on the infrared image, like this:

The dot pattern may be absent in the Viewer if (a) the Emitter Enabled drop-down menu in the Viewer's options-side panel is set to 'Off' instead of 'Laser; or (b) if the Laser Power option is set to '0', which automatically disables the IR emitter.
When the IR emitter is disabled or the value of Laser Power is minimized, the infrared image will darken and the dot pattern projection will not be visible on the infrared image.  The amount of detail on the depth image may also significantly reduce and resemble your depth image above.  This is because the camera uses the dot pattern projected onto surfaces in the scene as a 'texture source' to analyze the surfaces for depth detail if the surface is a material that has low texture or no texture (such as a desk, door or wall).
If a scene is well lit then the camera can alternatively use ambient light in the scene to analyze surfaces for depth detail instead of using the dot pattern.

Thanks very much for the images. It looks as though your D455's IR emitter component is disabled. If the emitter (which is a separate component from the left and right IR sensors) was enabled then there would be a semi-random pattern of dots projected onto the scene and visible on the infrared image, like this:

Because the IR emitter is a separate component from the IR imagers, the infrared stream can continue to be used when the IR emitter is inactive.
The dot pattern may be absent in the Viewer if:
(a) the Emitter Enabled drop-down menu in the Viewer's options-side panel is set to 'Off' or 'Auto' instead of 'Laser;
(b) if the Laser Power option is set to '0', which automatically disables the IR emitter;
(c) the IR emitter is set to 'Laser' and the Laser Power is set to its default values but some issue is preventing the pattern from being visible on the IR image.
When the IR emitter is disabled or the value of Laser Power is minimized, the infrared image will darken and the dot pattern projection will not be visible on the infrared image, resulting in an infrared image resembling the one that you provided above.
The amount of detail on the depth image may also significantly reduce and resemble your depth image above. This is because the camera uses the dot pattern projected onto surfaces in the scene as a 'texture source' to analyze the surfaces for depth detail if the surface is a material that has low texture or no texture (such as a desk, door or wall).
If a scene is well lit then the camera can alternatively use ambient light in the scene to analyze surfaces for depth detail instead of using the dot pattern.
I would add that if your goal is to sense the object held by the tripod and your project has the option of changing camera models then the new RealSense D405 camera model would be a good choice. It specializes in accurate close-range depth sensing at an ideal range of 7 cm to 50 cm, enabling the camera to be placed closer to an object / surface than any previous RealSense camera model.

Thank you very much for your insightful reply. We are highly aware of laser dot pattern and its powerful appliance. We did plenty of tests with or without it. In our case it highly improves jitter of depth accuracy, and as you said, because of its illumination and texture; it gives wider spectrum of depth and less 0 depth pixels. Since we are only interested in that one small region and its high accuracy, we saw there is a profile on RS viewer called High Accuracy, which we modified a little for our environments needs. IR emitter in our tests (On/Off) showed that distance inaccuracy is persistent (still few centimeters off), as said before emitter helps with jitteriness a lot, but this is not that big of a problem for us as we have an algorithm to smooth out the result, and main distance error stays the same. We also noticed that IR diodes constellation we use (shown on the second picture in my previous reply) creates itself a recognizable pattern for solving depth in that region, although, correct me if I am wrong please :)
Regarding to your advice about D405, which I appreciate a lot; in our case it is important to have good accuracy in the range of 0.7 - 1 meter. We can deal with millimeters error, but when error goes in the range of couple centimeters, things are getting little out of control for us.

Recognizable patterns do matter with algorithms used by stereo depth cameras such as the 400 Series.  In the link below. Intel has an introductory Depth from Stereo tutorial guide that discusses stereo depth principles such as calculating depth by estimating disparities between matching key-points in the left and right images:
https://github.com/IntelRealSense/librealsense/blob/master/doc/depth-from-stereo.md
Some visual patterns detected in a scene by the camera can also have negative implications for depth measurement.  If there are horizontal or vertical rows of similar looking 'repetitive patterns' such as a horizontal row of fence posts or tree tops, or a vertical stack of window blind slats, then the camera can become confused and generate depth error or 'ghost noise' areas of depth on the image that do not represent objects in the real world scene.
The Intel guides at the links below provide advice about reducing the impact of repetitive patterns.
https://dev.intelrealsense.com/docs/depth-map-improvements-for-stereo-based-depth-cameras-on-drones#section-v-incorrect-depth-values
https://dev.intelrealsense.com/docs/mitigate-repetitive-pattern-effect-stereo-depth-cameras

Recognizable patterns do matter with algorithms used by stereo depth cameras such as the 400 Series. In the link below. Intel has an introductory Depth from Stereo tutorial guide that discusses stereo depth principles such as calculating depth by estimating disparities between matching key-points in the left and right images:
https://github.com/IntelRealSense/librealsense/blob/master/doc/depth-from-stereo.md
Some visual patterns detected in a scene by the camera can also have negative implications for depth measurement. If there are horizontal or vertical rows of similar looking 'repetitive patterns' such as a horizontal row of fence posts or tree tops, or a vertical stack of window blind slats, then the camera can become confused and generate depth error or 'ghost noise' areas of depth on the image that do not represent objects in the real world scene.
The Intel guides at the links below provide advice about reducing the impact of repetitive patterns.
https://dev.intelrealsense.com/docs/depth-map-improvements-for-stereo-based-depth-cameras-on-drones#section-v-incorrect-depth-values
https://dev.intelrealsense.com/docs/mitigate-repetitive-pattern-effect-stereo-depth-cameras

I am grateful for your help as I think we finally got to the source of the problem. After reading documents you referenced I did more testing. Because the object we are tracking is quite small, even though we have 4 Infrared diodes attached to it, that is not enough to solve invalid depth pixels. First case is that the little box we are using for detection has plain color on it and no texture. Additionally, IR emitter can miss, or have very few (1 or 2) diodes on it depends on the angle and distance. I did tests with highly detailed object on the similar distance and results proved the theory. In the picture bellow, B references our small object with infrareds, while B is bigger, more detailed cube on the same height and very similar distance. After doing manual measurements, B was correct:

It turns out for me that invalid depth values are always further than they actually are.

A RealSense team member recommends in a case about sensing small objects at https://github.com/IntelRealSense/librealsense/issues/4175#issuecomment-507448389 that an object's size be at least 9 pixels on the image in order to be trackable.

Hi @powellsky  Do you require further assistance with this case, please?  Thanks!

Hi @powellsky Do you require further assistance with this case, please? Thanks!

Sorry for late reply. We noticed various depths depending on complexity of background. Therefore, hypothetically, the more complex is our background, the better detection goes. Me and my co-worker tested detection on the same object and distances with same camera settings but with different environments (IR Projector ON). In my case, detection was various depending on where in the room is my object, while my co-worker had no issues. One of the tricks that solved my issue was placing highly textured object behind desired object for detection.

It's great to hear that you found a solution that worked for you!
If you are satisfied with the outcome of this case, please feel free to close it with the Close Issue button under the comment writing box.  If you have further questions though then I will be pleased to help.  Thanks again!


asking for longer prompts triggers - Request processing failed: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "http://localhost:11434/api/chat": timeout

Hello,  I see that there was a possible duplicate of this but it was closed as  not having provided enough info
Bug description
i have tried to use phi3, llama3.2:1b, llama3.2:latest...
i have asked questions with wordy answers inside the terminal and i get a response every time.
However, with the spring ai project, every time i ask a question that should generate a somewhat longer answer, i get the above error;
if i ask plain things like 'count to 10' - i get a response; If i ask 'count to 100' - error above followed by 'Socket closed '
Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "http://localhost:11434/api/chat": timeout] with root cause

java.net.SocketException: Socket closed
	at java.base/sun.nio.ch.NioSocketImpl.endRead(NioSocketImpl.java:253) ~[na:na]
	at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:332) ~[na:na]
	at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:355) ~[na:na]
	at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:808) ~[na:na]
	at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966) ~[na:na]
	at okio.InputStreamSource.read(JvmOkio.kt:93) ~[okio-jvm-3.6.0.jar:na]
	at okio.AsyncTimeout$source$1.read(AsyncTimeout.kt:128) ~[okio-jvm-3.6.0.jar:na]
	at okio.RealBufferedSource.indexOf(RealBufferedSource.kt:430) ~[okio-jvm-3.6.0.jar:na]
	at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.kt:323) ~[okio-jvm-3.6.0.jar:na]

Environment
<properties>
        <java.version>17</java.version>
        <spring-ai.version>1.0.0-M3</spring-ai.version>
   </properties>
<dependency>
                <groupId>org.springframework.ai</groupId>
                <artifactId>spring-ai-bom</artifactId>
                <version>${spring-ai.version}</version>
                <type>pom</type>
                <scope>import</scope>
</dependency>

i run an amazon Linux EC2 with processor:
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
16GB RAM
-- could these limited resources be problematic?
Steps to reproduce
created a plain spring boot project with spring-ai-bom;
added a plain ChatController with contents
private final ChatModel chatModel;
public ChatController(ChatModel chatModel) {
this.chatModel = chatModel;
}
@GetMapping("/ask")
public String askQuestion(@RequestParam(value = "message") String message) {
    return chatModel.call(message);
}

Expected behavior
i expect a response from the model which is as large as its output context (1024 chars for ex for llama3.2:1b)
Minimal Complete Reproducible example
setup as above and ask to provide a long description;

You might need to increase the default timeout value.
If you're using Spring Boot 3.3, then you can use a RestClientCustomizer.
@Bean
RestClientCustomizer restClientCustomizer() {
      return restClientBuilder -> {
          restClientBuilder
                  .requestFactory(new BufferingClientHttpRequestFactory(
                          ClientHttpRequestFactories.get(ClientHttpRequestFactorySettings.DEFAULTS
                                          .withConnectTimeout(Duration.ofSeconds(60))
                                          .withReadTimeout(Duration.ofSeconds(120))
                          )));
      };
}

In Spring Boot 3.4, you can customise that via configuration properties:
spring:
  http:
    client:
      connect-timeout: 30s
      read-timeout: 120s

There is a feature request to make these timeouts more easily configurable for Spring AI: https://github.com/spring-projects/spring-ai/issues/512

thanks a lot for the quick reply - indeed this works - amazing help; to me this issue can be closed.

@vzR happy to help! I'm glad that fixed the problem. I think you have the option down here to close the issue.

thanks for the quick help! closing the issue.

You might need to increase the default timeout value.
If you're using Spring Boot 3.3, then you can use a RestClientCustomizer.
@Bean
RestClientCustomizer restClientCustomizer() {
      return restClientBuilder -> {
          restClientBuilder
                  .requestFactory(new BufferingClientHttpRequestFactory(
                          ClientHttpRequestFactories.get(ClientHttpRequestFactorySettings.DEFAULTS
                                          .withConnectTimeout(Duration.ofSeconds(60))
                                          .withReadTimeout(Duration.ofSeconds(120))
                          )));
      };
}

In Spring Boot 3.4, you can customise that via configuration properties:
spring:
  http:
    client:
      connect-timeout: 30s
      read-timeout: 120s

There is a feature request to make these timeouts more easily configurable for Spring AI: #512

If I use springboot3.2，what I should do?


Master

Docs Build status updates of commit 0666957:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/DocsLegal-pr.de-CH, working directory: W:\hvsn-s, target branch: HEAD, target branch commit: c3f495e4cc26d3d6ffa72fc3f7a7a50dca43bfa5, source commit:<PHONE_NUMBER>060bdb6d640384312c74f6601f1b31.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Björn's Blogpost regarding Joomla BPMNViewer Plugin

This is Björn's Blogpost regarding Joomla BPMNViewer Plugin and is ready for review.

I am closing this for now, pending further discussion with @jakobfreund.
We can always re-open it


GH-2: Introduce Apache 2.0 license headers per @rljohnsn

Fixes 8x8Cloud/fiql-elasticsearch#2

yo @rljohnsn, you mind merging this please? When you do I'll pull back into my fork and do some stuff w/ Travis and possibly Bintray/Maven Central

Lets put an Apache 2.0 header.

I took a quick look, and the license itself says that you're required to add the header to all source files. It looks like there are two approaches to this:

Do what the license explicitly says, including all XML/build artifacts (Gradle, Maven etc)
Do not attach a license header to source files

I suggest that if we're going to do the first option, that we follow the spirit of the agreement. I'll add the headers to the OWASP/POM files in accordance. I'll skip the things that are required by the ASF governing board as this is not (yet) part of an Apache project. Might be good to at least donate the expression -> expression translator.